Wired usb controllers not recognized after update

the_loaf

The other day my Pi 4 had an issue with emulationstation crashing upon booting. I ran the updater to update all the packages which allowed me to get all the way into ES

Now, though, no wired USB controllers are recognized. I have a wireless usb keyboard which works, and a wireless usb controller is recognized

I’ve attached a powered USB hub thinking it may be a power issue, but through that only the wireless items will work still

Any ideas what may be happening? Not sure which logs to share that may shed light on it or which config file affects this. I cleared the ES controller config, so it only has the settings for my keyboard now

Pi Model or other hardware: 4
Power Supply used: 5V 3A
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.7.18?
Built From:
USB Devices connected: powered 7port usb hub, sandisk thumb drive
Controller used: hori fighting commander switch, 8bitdo arcade stick, 8bitdo sn30pro+ (one at a time) - connected to pi directly or through hub
Error messages received: no controllers connected message when emulationstation starts. Jstest shows “broken pipe”

Verbose log (if relevant):

Attachment of config files: (PLEASE USE PASTEBIN.COM FOR LARGE LOGS)

How to replicate the problem:

windg

i think you are effected from the latest update of xpad driver that cause some problems. Read this topic , and if you want follow the instructions to downgrade the driver.

the_loaf

@windg ah thank you I’ll give that a try

the_loaf

So when I downgrade per that thread, my emulationstation crashes on startup again

mitu

@the_loaf Then it's not -entirely - the same issue. Looking at the original topic you opened, it happened before the update, so there's must be something else that's happening. Let's continue on your original topic.

EDIT: sorry, this is the original topic, I got it confused with the xpad problems topic.

ES may crash if one of the controllers may disconnect during initialization. Can you check with dmesg if the controller disconnects, after ES crashes to the terminal ? Running dmesg | tail should get you the last system messages, which should contain any disconnect messages.

the_loaf

This post is deleted!

the_loaf

This post is deleted!

the_loaf

@mitu sorry had a couple bad pastes initially with weird characters appearing

Thank you for checking - hopefully this was gathered correctly

[12131.031202] input: Microsoft X-Box 360 pad as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0/input/input3462
[12132.324786] usb 1-1.1.4: USB disconnect, device number 48
[12132.325126] xpad 1-1.1.4:1.0: xpad_try_sending_next_out_packet - usb_submit_urb failed with result -19
[12132.842246] usb 1-1.1.4: new full-speed USB device number 49 using xhci_hcd
[12133.093183] usb 1-1.1.4: New USB device found, idVendor=045e, idProduct=028e, bcdDevice= 1.14
[12133.093205] usb 1-1.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[12133.093224] usb 1-1.1.4: Product: Controller
[12133.093242] usb 1-1.1.4: Manufacturer: 8BitDo[12133.093259] usb 1-1.1.4: SerialNumber: 157F8F8
[12133.100276] input: Microsoft X-Box 360 pad as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0/input/input3463

mitu

I reformatted the log to be more readable.
Looks like the gamepad does disconnect and then reconnects again. The log only shows the last disconnect/connect cycle, but judging by the device number 49 shown on connection this may have happened again.
Did you change anything in your configuration recently ? Overclocking settings ? Can you post your /boot/config.txt file ?

the_loaf

@mitu it is overclocked, but that was done well over a year ago. I havent made any changes recently.

I’ll have to share the config.txt in a bit. Thanks

the_loaf

sorry for the delay

here is the config.txt

https://pastebin.com/3Fzt9mnD

mitu

Apart from the overclocking, I don't see anything special - the configuration seems ok. You may try a larger over_voltage value, but if you're using a powered hub that shouldn't be necessary.
Can you try removing any non-default values and reboot ? Comment out the following lines from the file:

over_voltage=6
arm_freq=2000
gpu_freq=600
v3d_freq=750

the_loaf

@mitu emulationstation is still crashing after making this change

Could some rom folder or emulator be causing this?

the_loaf

Update on this

I just put the overclocking settings back to normal and reinstalled the newest xpad, and I have joystick capability again

I can now control things with my 8bitdo arcade stick like before

Thanks again for looking into this

raspberry79

@the_loaf
I noticed in the script above about
(usb_submit_urb failed with result
I have that problem. When it installing, i guess the emulates, at the end of the scripts on the tv screen
i notice "usb_submit_urb failed with result-2"
what is that and how to fixed that