NanoPI R4S second USB not working


Go to solution Solved by Werner,

Recommended Posts

Armbianmonitor:

The second USB port of NanoPI R4s is not working -- the logs were created with a USB disk inserted in port 2.

 

# lsusb -t

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

    |__ Port 1: Dev 3, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M

 

If I remove and swap the USB devices:

 

# lsusb -t

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M

    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

 

Other users are reporting the same problem, including that it works with FriendlyCore and FriendlyWRT. I can test if needed to confirm the port is not dead.

 

Link to post
Share on other sites
Donate and support the project!

17 hours ago, Werner said:

You can use the armbian-config tool. Check System -> Other

Perfect, thank you.

 

# uname -a

Linux zen 5.11.18-rockchip64 #21.05.1 SMP PREEMPT Thu May 6 22:15:36 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

 

# lsusb -t

/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M

/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtl88x2bu, 480M

/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M

/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M

    |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=pl2303, 12M

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-platform/1p, 12M

/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M

Link to post
Share on other sites

Unfortunately, I was a little euphoric about getting the second USB port working with the newer kernels. Today, after a lot of reboots and three days uptime, I noticed that my second USB port was not working any more. I do not know if it simply stopped working or was not available from the last boot. At least, rebooting brought it back again. I also did a lot of testing with moving the system to an USB SSD which also failed or succeeded to boot randomly (power issue excluded). So, be aware that my proposed solution to use kernel 5.11.18 or 5.12.6 is only a workaround and might not be stable.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...