-
-
Notifications
You must be signed in to change notification settings - Fork 288
RPi4 4GB: unable to enumerate USB device #605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It was a bug in RPI kernel, this will be fixed in next kernel (I hope...) |
Thanks! Just found a newer release at https://www.openmptcprouter.com/release/4.19/rpi4/targets/brcm2708/bcm2711/ which also seems to support wireless. The error is also gone with that build. |
It's a pre-release, I'm testing it. |
Looks like the RPi4 upstream kernel is still buggy in terms of DNA access unrelated to OpenMPTCProuter: I used the pre-release mentioned above, upgraded all packages with opkg (fixes the lua error), successfully connected to my OpenMPTCProuter VPS install. I've then connected my Macbook through eth0, a Huawei E5573 via USB (eth1) and added my existing wifi as upstream. As soon as I max out the bandwidth using speedtest.net, the wifi connection drops, showing dmesg:
I'm pretty sure this is an open kernel issue for Raspberry Pi 4 and related to raspberrypi/linux#3120 and raspberrypi/linux#3032 |
True, should be fixed but doesn't seems to be the case yet... |
Uh oh!
There was an error while loading. Please reload this page.
Expected Behavior
no dmesg output
Actual Behavior
After boot, dmesg is collecting the following error
(over and over again).
No USB device is connected. I assume this error targets the default on-board USB hub?
Steps to Reproduce the Problem
openmptcprouter-v0.51.5-r010518-6d61fcfa9e-brcm2708-bcm2711-rpi-4-ext4-factory.img.gz
to SDdmesg
via sshSpecifications
v0.51.5-r010518-6d61fcfa9e-brcm2708-bcm2711-rpi-4-ext4-factory.img.gz
The text was updated successfully, but these errors were encountered: