Some thoughts:
My current gut feeling is that it's either a power problem or a problem with the hub. We know the hub doesn't meet the USB spec in one way so I wouldn't be surprised if it failed to do so in other ways too. That the controllers "work fine" when directly connected to the Pi also points at the hub being the problem.
What works and doesn't on x86 doesn't really help us on ARM.
- It appears from your images that you are relying on the USB hub to back power the Pi via the USB connection. That this works means that the hub violates the USB spec. Downstream devices should not be sending power via their upstream facing ports.
- What's the current rating of the supply you are using for the USB hub?
- What's the per device current requirement?
- What's the total current requirement of all connected USB devices including the hub?
- uname -a is not enough. Which OS are you running? Raspberry Pi OS or something else?
- Which release? Bookworm, Bullseye, Buster, etc.?
- Lite or desktop?
- Booting to desktop or command line?
- With or without automatic login?
- Which application, program, command, or script are you using to test whether the devices are functional?
- On your lsusb log:
- There are a lot of "Couldn't open device, some information will be missing" messages. Was that log produced as a normal user or as root/with sudo?
If the former, try again as root/with sudo. - Please also post the output of
Code:
lsusb -t
- There are a lot of "Couldn't open device, some information will be missing" messages. Was that log produced as a normal user or as root/with sudo?
My current gut feeling is that it's either a power problem or a problem with the hub. We know the hub doesn't meet the USB spec in one way so I wouldn't be surprised if it failed to do so in other ways too. That the controllers "work fine" when directly connected to the Pi also points at the hub being the problem.
What works and doesn't on x86 doesn't really help us on ARM.
Statistics: Posted by thagrol — Sat Jun 22, 2024 4:43 pm