NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS Duo V2 - USB 3.0 Devices Only Work @ USB 2.0 Speeds
I've read through the forums and I understand this device was just released last month but having big problems/reservations with this unit. There basically is no HCL for USB storage on the Duo V2. All...
The new unit is not much better. This is a xhci_hcd driver issue.
After initial setup on the new V2 I see the following in dmesg
This is what you see in dmesg on the new Duo V2 when attaching a USB 3.0 drive.
The exact same problem is present in various distros most of which were resolved in the first or second quarter of 2011. I'd be able to work with it more if the driver was a module. As is, there's no way to unload the driver except via shutdown as a reboot breaks it.
Here's the exact same bug on Ubuntu in May 2011 - https://bugs.launchpad.net/ubuntu/+sour ... bug/775543
Same behavior down to how you plug in devices and multiple attempts to get drives recognized.
Duo V2 lspci -v
The Duo V2 has the same NEC controller as in that bug report with a different revision.
After shutting down and rebooting at least 6 times the drive was finally recognized. Still can't reboot and be able to use USB3.0. Speeds were immediately in the proper range though. Since no Jedi has responded I will initiate a trouble ticket for engineering at Netgear.
After initial setup on the new V2 I see the following in dmesg
xhci_hcd 0000:01:01.0: xHCI Host Controller
xhci_hcd 0000:01:01.0: new USB bus registered, assigned bus number 2
xhci_hcd 0000:01:01.0: irq 9, io mem 0xe0000000
xhci_hcd 0000:01:01.0: Failed to enable MSI-X
xhci_hcd 0000:01:01.0: failed to allocate MSI entry
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
xhci_hcd 0000:01:01.0: xHCI Host Controller
xhci_hcd 0000:01:01.0: new USB bus registered, assigned bus number 3
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
This is what you see in dmesg on the new Duo V2 when attaching a USB 3.0 drive.
xhci_hcd 0000:01:01.0: Timeout while waiting for a slot
hub 3-0:1.0: couldn't allocate port 2 usb_device
xhci_hcd 0000:01:01.0: Timeout while waiting for a slot
hub 3-0:1.0: couldn't allocate port 1 usb_device
The exact same problem is present in various distros most of which were resolved in the first or second quarter of 2011. I'd be able to work with it more if the driver was a module. As is, there's no way to unload the driver except via shutdown as a reboot breaks it.
Here's the exact same bug on Ubuntu in May 2011 - https://bugs.launchpad.net/ubuntu/+sour ... bug/775543
Same behavior down to how you plug in devices and multiple attempts to get drives recognized.
Duo V2 lspci -v
01:01.0 USB Controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04) (prog-if 30)
Flags: bus master, fast devsel, latency 0, IRQ 9
Memory at e0000000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [50] Power Management version 3
Capabilities: [70] MSI: Enable- Count=1/8 Maskable- 64bit+
Capabilities: [90] MSI-X: Enable- Count=8 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] #1033
Kernel driver in use: xhci_hcd
The Duo V2 has the same NEC controller as in that bug report with a different revision.
After shutting down and rebooting at least 6 times the drive was finally recognized. Still can't reboot and be able to use USB3.0. Speeds were immediately in the proper range though. Since no Jedi has responded I will initiate a trouble ticket for engineering at Netgear.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
