DUB-E100 problem

[jwciv]

Hi - I bought a DUB-E100 to network a tivo and cannot get it to work. To troubleshoot I did the following:
1. I put it on my PC and it functioned fine
2. I have another DUB-E100 that I plugged into the Tivo and it worked fine.

Is there a way to diagnose a USB network adaptor to see why it would work on a PC but not in a tivo?

Thanks

[Jamie]

Hi - I bought a DUB-E100 to network a tivo and cannot get it to work. To troubleshoot I did the following:
1. I put it on my PC and it functioned fine
2. I have another DUB-E100 that I plugged into the Tivo and it worked fine.

Is there a way to diagnose a USB network adaptor to see why it would work on a PC but not in a tivo?

ThanksIt could be a revision of the model that isn't suported by the drivers you are using. Unfortunately, the vendors of these devices have the habit of changing the hardware and drivers without changing the model number.

Look for a version number printed on the device. Failing that, knowing the vendor/product id's of the device would probably help. I'm guessing that your two dub-e100's have different id's. You can get the id's out of the kernel log on the tivo. They are also in the windows driver .inf file.

There are at least 5 versions of that device: link (http://www.dlink.com/products/support.asp?pid=133). I know the backport drivers support both the A and B versions. Apparently the tivo stock drivers don't support some of them link (http://tivosupport2.instancy.com/TivoCollection/d263b68c-3df2-43a2-b7d5-fb0fae1ea86d/ins_content.html).

[jwciv]

It could be a revision of the model that isn't suported by the drivers you are using. Unfortunately, the vendors of these devices have the habit of changing the hardware and drivers without changing the model number.

Look for a version number printed on the device. Failing that, knowing the vendor/product id's of the device would probably help. I'm guessing that your two dub-e100's have different id's. You can get the id's out of the kernel log on the tivo. They are also in the windows driver .inf file.

There are at least 5 versions of that device: link (http://www.dlink.com/products/support.asp?pid=133). I know the backport drivers support both the A and B versions. Apparently the tivo stock drivers don't support some of them link (http://tivosupport2.instancy.com/TivoCollection/d263b68c-3df2-43a2-b7d5-fb0fae1ea86d/ins_content.html).

Thanks for the info Jamie. I have two versions at A4 that work, the one that does not work for me is A3. I did find this link (http://www.dealdatabase.com/forum/showthread.php?p=285412&highlight=A4#post285412) that shows that it does work, so it must be my set-up with the backport drives, I'll have to double check it.

[jwciv]

...so it must be my set-up with the backport drives, I'll have to double check it.


Been a while since I installed the backport drivers. I followed these steps, then rebooted and I still cannot get it to work. Further thoughts?

1. created a backup directory, /lib/modules/backup
2. moved the drivers to the backup directory:
mv /lib/modules/pegasus.o /lib/modules/backup
mv /lib/modules/usbcore.o /lib/modules/backup
mv /lib/modules/usb-ohci.o /lib/modules/backup
mv /lib/modules/usbnet.o /lib/modules/backup
mv /lib/modules/ax8817x.o /lib/modules/backup3. used SmartFTP and copied over pegasus, usbcore, usb_ochi and usbnet to /lib/modules
simlinked: ln -s /lib/modules/usbnet.o /lib/modules/ax8817x.o

Note I had a typo earlier: the A4 works for me, the A3 does not

[Jamie]

Been a while since I installed the backport drivers. I followed these steps, then rebooted and I still cannot get it to work. Further thoughts? ...Do you do this part (from the README):
...
/etc/hotplug/usb.map:

Newer tivo software versions (6.x, 7.x) use a text file,
/etc/hotplug/usb.map to determine what driver should be used for a
give usb vendor/product id. The entries from ./usb.map.additions can
be added to your usb.map to support additional devices. For 6.x,
these go in the ax8817x section. For 7.x, they go in the usbnet
section.
...

[jwciv]

Do you do this part (from the README):

No, I did not. The pid/vid for both A3 and A4 is 2001 1a00 which is already in the usb.map under the ax8817x section.

[Jamie]

So, time to break out your serial console cable. Is the driver getting loaded as it should be? If not, it indicates a problem in your usb.map. Is the device getting an IP address, e.g. check with ifconfig. If not, you probably need to set the network settings from the tivo menus. Are you getting any errors in /var/log/messages?

[jwciv]

So, time to break out your serial console cable. Is the driver getting loaded as it should be? If not, it indicates a problem in your usb.map. Is the device getting an IP address, e.g. check with ifconfig. If not, you probably need to set the network settings from the tivo menus. Are you getting any errors in /var/log/messages?

Here's my Kernel log from the HR10-250. It was working with an A4 plugged in. I cleared the kernel log, unplugged the A4 then plugged in the A3, then unplugged the A3 and plugged the A4 back in.
This unit is configured to use a static IP
There are no errors in var/log/messages
when the working adaptor is plugged in, ifconfig gives
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:0.0.0.0 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:148 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:10029 dropped:148 overruns:0 carrier:0 coll:0

eth0 Link encap:Ethernet HWaddr 00:80:C8:37:8B:7B
inet addr:192.168.0.120 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:673 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:160515 dropped:672 overruns:0 carrier:0 coll:0

Kernel Log:
Log cleared on Mon Nov 05, 2007 by TivoWebPlus
Nov 6 02:02:41 (none) kernel: hub.c: port 1, portstatus 100, change 3, 12 Mb/s
Nov 6 02:02:41 (none) kernel: usb.c: USB disconnect on device 00:0d.2-1 address 2 Nov 6 02:02:41 (none) kernel: eth0: unregister usbnet usb-00:0d.2-1, DLink DUB-E100 USB Ethernet
Nov 6 02:02:41 (none) kernel: hub.c: port 2, portstatus 100, change 0, 12 Mb/s
Nov 6 02:02:41 (none) kernel: hub.c: port 3, portstatus 100, change 0, 12 Mb/s
Nov 6 02:02:41 (none) kernel: hub.c: port 4, portstatus 100, change 0, 12 Mb/s
Nov 6 02:02:41 (none) kernel: hub.c: port 5, portstatus 100, change 0, 12 Mb/s
Nov 6 02:02:46 (none) kernel: usb.c: deregistering driver usbnet
Nov 6 02:03:30 (none) kernel: hub.c: port 1, portstatus 501, change 1, 480 Mb/s
Nov 6 02:03:30 (none) kernel: hub.c: port 1, portstatus 501, change 0, 480 Mb/s
Nov 6 02:03:30 (none) last message repeated 3 timesNov 6 02:03:30 (none) kernel: hub.c: port 1, portstatus 511, change 0, 480 Mb/s
Nov 6 02:03:30 (none) kernel: hub.c: port 1, portstatus 511, change 0, 480 Mb/s
Nov 6 02:03:30 (none) kernel: hub.c: port 1, portstatus 503, change 10, 480 Mb/s
Nov 6 02:03:30 (none) kernel: hub.c: new USB device 00:0d.2-1, assigned address 3
Nov 6 02:03:30 (none) kernel: usb.c: USB device not responding, giving up (error=-71)
Nov 6 02:03:31 (none) kernel: hub.c: port 1, portstatus 503, change 10, 480 Mb/s Nov 6 02:03:31 (none) kernel: hub.c: new USB device 00:0d.2-1, assigned address 4
Nov 6 02:03:31 (none) kernel: usb.c: USB device not accepting new address=4 (error=-71)
Nov 6 02:03:31 (none) kernel: hub.c: port 2, portstatus 100, change 0, 12 Mb/s N
Nov 6 02:03:31 (none) kernel: hub.c: port 3, portstatus 100, change 0, 12 Mb/s
Nov 6 02:03:31 (none) kernel: hub.c: port 4, portstatus 100, change 0, 12 Mb/s
Nov 6 02:03:31 (none) kernel: hub.c: port 5, portstatus 100, change 0, 12 Mb/s
Nov 6 02:04:45 (none) kernel: hub.c: port 1, portstatus 100, change 1, 12 Mb/s
Nov 6 02:04:45 (none) kernel: hub.c: port 2, portstatus 100, change 0, 12 Mb/s
Nov 6 02:04:45 (none) kernel: hub.c: port 3, portstatus 100, change 0, 12 Mb/s
Nov 6 02:04:45 (none) kernel: hub.c: port 4, portstatus 100, change 0, 12 Mb/s
Nov 6 02:04:45 (none) kernel: hub.c: port 5, portstatus 100, change 0, 12 Mb/s
Nov 6 02:04:54 (none) kernel: hub.c: port 1, portstatus 100, change 0, 12 Mb/s
Nov 6 02:04:54 (none) kernel: hub.c: port 2, portstatus 501, change 1, 480 Mb/s
Nov 6 02:04:54 (none) kernel: hub.c: port 2, portstatus 501, change 0, 480 Mb/s
Nov 6 02:04:54 (none) last message repeated 3 times
Nov 6 02:04:54 (none) kernel: hub.c: port 2, portstatus 511, change 0, 480 Mb/s
Nov 6 02:04:54 (none) kernel: hub.c: port 2, portstatus 511, change 0, 480 Mb/s
Nov 6 02:04:54 (none) kernel: hub.c: port 2, portstatus 503, change 10, 480 Mb/s
Nov 6 02:04:54 (none) kernel: hub.c: new USB device 00:0d.2-2, assigned address 5
Nov 6 02:04:55 (none) kernel: usb.c: USB device 5 (vend/prod 0x2001/0x1a00) is not claimed by any active driver.
Nov 6 02:04:55 (none) kernel: hub.c: port 3, portstatus 100, change 0, 12 Mb/s
Nov 6 02:04:55 (none) kernel: hub.c: port 4, portstatus 100, change 0, 12 Mb/s
Nov 6 02:04:55 (none) kernel: hub.c: port 5, portstatus 100, change 0, 12 Mb/s
Nov 6 02:04:57 (none) kernel: usb.c: registered new driver usbnet
Nov 6 02:04:57 (none) kernel: eth0: register usbnet usb-00:0d.2-2, DLink DUB-E100 USB Ethernet
Nov 6 02:05:03 (none) kernel: ApgManager Transition from state ACQUIRE_MARKER to ACQUIRE_MARKER
Nov 6 02:10:56 (none) kernel: ApgManager Transition from state ACQUIRE_MARKER to ACQUIRE_MARKER
"...USB device not responding, giving up (error=-71)" maybe time to spend the $20 on a new adapter :)