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
FS#2473 - Usb not working on fonera 2.0n (ramips/rt305x) #7916
Comments
ilvalle: Tested against trunk with the same result. |
ilvalle: The usb is powered, I charged a simple phone. Any hint ? |
adrianschmutzler: Please narrow down which commit between 18.06.1 and 18.06.2 is causing the problem. |
bsvif: I have the same issue usb workin only in 18.06.1 |
adrianschmutzler: So, kernel broke it? Then it should be fixed in kernel. If it is already fixed there, it will come automatically with the corresponding kernel bump. |
sdv: It's working in upstream and with other hardware platforms. |
adrianschmutzler: Okay, then we still need to find the commit breaking it between 18.06.1 and 18.06.2 ... |
adrianschmutzler: From the two referenced kernel commits, the second one is rather old and has been in 4.14 from the beginning. The first one has been backported to 4.14 in 4.14.67, which has been added to OpenWrt here: That would actually be between 18.06.1 and 18.06.2. Since 19.07 uses the same kernel, it would be affected, too. So, next job would be to build with the referenced commit and it's parent and check whether it really is the source of the problem. Despite, it would be helpful to test with master, maybe stuff has been fixed with later kernels already ... |
odmdas: Please, try this patch [0] for your device. Did this help? |
sdv: Yes, I can confirm that:
Board: Asus RT-N13U. |
nik2208: Sorry guys, I'm missing something. This bug is labeled as solved but the latest release is still affected. |
sdv: It's fixed in trunk after this commit: And this fix should be included in 19.07.4. |
nik2208: I can confirm it is fixed in 19.07.4 |
ilvalle:
On openwrt 18.06.4 usb is no longer working. I've tried with 18.06.02 built by my own with the same result. With 18.06.1 everything was working correctly.
The text was updated successfully, but these errors were encountered: