What's new

N66U 3.0.0.4.374.39_0 - USB hubs/cardreaders still do not work

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

amigohd

Regular Contributor
As with the 3.0.0.4.374.38' versions my usb card readers connected to an usb hub do not work. If I go back to RT-N66U_3.0.0.4_374.35_4 it works without any modifications.

OScam errors:
2014/02/03 14:24:36 56E4C8 r sky [smartreader] usb bulk write failed : ret = -7
2014/02/03 14:24:36 56C7C8 r orf [smartreader] usb bulk write failed : ret = -7
2014/02/03 14:24:36 522E58 r srg [smartreader] usb bulk write failed : ret = -7
2014/02/03 14:24:46 56E4C8 r sky [smartreader] usb bulk write failed : ret = -7
2014/02/03 14:24:46 56C7C8 r orf [smartreader] usb bulk write failed : ret = -7
2014/02/03 14:24:46 522E58 r srg [smartreader] usb bulk write failed : ret = -7
2014/02/03 14:24:48 56E4C8 r sky [smartreader] Error activating card.
2014/02/03 14:24:48 56C7C8 r orf [smartreader] Error activating card.
2014/02/03 14:24:48 522E58 r srg [smartreader] Error activating card.
2014/02/03 14:24:49 56E4C8 r sky [smartreader] init card at 369 mhz
2014/02/03 14:24:49 56C7C8 r orf [smartreader] init card at 369 mhz
2014/02/03 14:24:49 522E58 r srg [smartreader] init card at 369 mhz
2014/02/03 14:24:59 56E4C8 r sky [smartreader] usb bulk write failed : ret = -7
2014/02/03 14:24:59 56C7C8 r orf [smartreader] usb bulk write failed : ret = -7
2014/02/03 14:24:59 522E58 r srg [smartreader] usb bulk write failed : ret = -7

lsusb:
admin@router:/tmp/home/root# lsusb
Bus 001 Device 009: ID 0403:6001
Bus 001 Device 008: ID 0403:6001
Bus 001 Device 007: ID 0403:6001
Bus 001 Device 006: ID 05e3:0608
Bus 001 Device 005: ID 058f:6366
Bus 001 Device 004: ID 0718:0618
Bus 001 Device 003: ID 05e3:0608
Bus 001 Device 002: ID 058f:6254
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0002

dmesg:
option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
option 1-1.1.3.4:1.0: device disconnected
option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
option 1-1.1.4:1.0: device disconnected
option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
option 1-1.1.3.1:1.0: device disconnected

my argolis smargo smartreader are recognized as modems?
still the new builds, as the .38 previous do have some failures. 3.0.0.4_374.35_4 do recognize my cardreaders properly.
 
this is the correct output on 3.0.0.4_374.35_4 of dmesg.

dmesg:
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
drivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
usbcore: registered new interface driver asix
usb 1-1: new high speed USB device using ehci_hcd and address 2
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver rndis_host
usbcore: registered new interface driver zaurus
usb 1-1.1: new high speed USB device using ehci_hcd and address 3

and all this is missing in .38 and .39 builds. I guess some core usb modifications on the kernel.
 
Last edited:
Nobody using usb hubs? Nobody having problems?

The two hard disks I tested with my old USB hub worked fine.

Results will vary depending on the HUB used and which devices you connect to it most likely.

Make sure it's a powered hub. A self-powered one might not provide enough power to work reliably.
 
The two hard disks I tested with my old USB hub worked fine.

Results will vary depending on the HUB used and which devices you connect to it most likely.

Make sure it's a powered hub. A self-powered one might not provide enough power to work reliably.

well, the hub is powered. it does work anywhere else. and it does work with previous builds I mentioned. So there has to be a big change in the kernel code since the .38 release as with the .35_4 it still works like a charm.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top