Lose network connectivity when updating to 6.2

[jmbaker]

This may have already been asked and answered somewhere, but I absolutely couldn't find it. I have an HDVR2 that I put 4.0.1b on (with killhdinitrd). Just today I finally figured out how to apply the update to 6.2. I followed all the necessary steps in terms of putting the DirecTV loopsets on and loading the slices for 6.2. I ran the update and everything went well. Before I rebooted, I made sure to put the killhdinitrd'd 3.1.5 kernel in the boot partition, move my hacks over, patch tivoapp to prevent CSO encryption, and modify the iptables as suggested by ADH and mentioned in the 6.2 upgrade thread

http://www.dealdatabase.com/forum/showthread.php?t=42325

Everything seemed to go well, except that after rebooting it didn't seem to recognize my USB-Ethernet adapter. It is a D-Link DSB-H3ETX which (I believe) uses the Pegasus chipset. As I recall, when I first plugged this adapter in under 4.0.1b it was recognized immediately, where here it is not (when I plug it into my TiVo nothing happens). I'm not sure if I did something incorrectly or forgot to do something, but I sure could use some guidance. Thanks very much in advance...

[AhoyMatey]

There's no support (just like 3.1.1x) for networking in 6.2 by default. Look at the two threads on 6.2 in the Series 2 Support forum for ways to get it working again.

[Thinkdiff]

rename the file "netfilter-enable" in the /etc folder to anything else. That will fix your problem.

[AhoyMatey]

You'd still want to rather install Jamie and alldeadhomiez USB drivers.

[PlainBill]

There's no support (just like 3.1.1x) for networking in 6.2 by default. Look at the two threads on 6.2 in the Series 2 Support forum for ways to get it working again.
Actually, that's wrong. 3.1.1 (and 3.1.5) have (outdated) usb-ethernet drivers included, but they were never loaded on a stock unit. 6.2 has a full set of drivers, and will install them if a supported adapter is plugged in (much like 4.x). It even has a dhcp client (like 4.x).

PlainBill

[AhoyMatey]

Actually, that's wrong. 3.1.1 (and 3.1.5) have (outdated) usb-ethernet drivers included, but they were never loaded on a stock unit. 6.2 has a full set of drivers, and will install them if a supported adapter is plugged in (much like 4.x). It even has a dhcp client (like 4.x).

PlainBillI stand corrected. :o

[jmbaker]

Actually, that's wrong. 3.1.1 (and 3.1.5) have (outdated) usb-ethernet drivers included, but they were never loaded on a stock unit. 6.2 has a full set of drivers, and will install them if a supported adapter is plugged in (much like 4.x). It even has a dhcp client (like 4.x).

PlainBill
So then if I'm understanding correctly, the issue is that my adapter is not supported? I know that it's not one of the adapters that they advertise as working (and it is only a USB 1.1 adapter, so maybe an upgrade is called for), but it had worked plug-and-play under 4.0.1b so I had assumed it would do the same here...

[eastwind]

This may have already been asked and answered somewhere, but I absolutely couldn't find it. I have an HDVR2 that I put 4.0.1b on (with killhdinitrd). Just today I finally figured out how to apply the update to 6.2. I followed all the necessary steps in terms of putting the DirecTV loopsets on and loading the slices for 6.2. I ran the update and everything went well. Before I rebooted, I made sure to put the killhdinitrd'd 3.1.5 kernel in the boot partition, move my hacks over, patch tivoapp to prevent CSO encryption, and modify the iptables as suggested by ADH and mentioned in the 6.2 upgrade thread

http://www.dealdatabase.com/forum/showthread.php?t=42325

Everything seemed to go well, except that after rebooting it didn't seem to recognize my USB-Ethernet adapter. It is a D-Link DSB-H3ETX which (I believe) uses the Pegasus chipset. As I recall, when I first plugged this adapter in under 4.0.1b it was recognized immediately, where here it is not (when I plug it into my TiVo nothing happens). I'm not sure if I did something incorrectly or forgot to do something, but I sure could use some guidance. Thanks very much in advance...
Did you try rebooting the TiVo with the adapter plugged in? Do you have a serial cable to help with troubleshooting?

ew

[Thinkdiff]

if it worked under 4, it will (should) work under 6.

--ignore--Did you rename that netfilter-enable file? Do you turn on telnet in rc.sysinit?---

edit:

I see now, I haven't run 6.2 yet, but I don't believe it has GUI support for networking, such as dialing into directv over the network. If that's what you're looking for, it might not happen. Please correct me if I am wrong (installing 6.2 later tonight)

[PlainBill]

I would have thought if it worked natively in 4.0.1, it would have worked with 6.2. (Shows that my thoughts are not always correct). 3.1.x does not have native network support. 4.0.1 does, including dhcp client and manual ip address optional (but as AhoyMatey says, can benefit from Jamie's backported drivers). 6.2 DOES load drivers, but the ip address is set by a dhcp client.

Given that you state the adapter is not activated, it would appear TiVo took something OUT of this release.

PlainBill

[jmbaker]

Did you try rebooting the TiVo with the adapter plugged in? Do you have a serial cable to help with troubleshooting?

ew
I haven't rebooted the TiVo since I first rebooted it to install the 6.2 software. The adapter was plugged in during this process, but I suppose it may be worth a shot to try rebooting again (can't hurt anything...).

Unfortunately I don't have a serial cable. I have been getting along okay so far without one, but the more involved I get in all of this, the more apparent it becomes that I'm going to need one. Maybe I'll order one...
if it worked under 4, it will (should) work under 6.

--ignore--Did you rename that netfilter-enable file? Do you turn on telnet in rc.sysinit?---

edit:

I see now, I haven't run 6.2 yet, but I don't believe it has GUI support for networking, such as dialing into directv over the network. If that's what you're looking for, it might not happen. Please correct me if I am wrong (installing 6.2 later tonight)
I didn't rename netfilter-enable, but I did rename dhclient to dhclient.orig and I set the IP and networking info (gatway, subnet, broadcast, etc) in my rc.sysinit.author file. I also started telnet and ftp in that file. If it's true that there's no GUI for setting up networking in this release (I had assumed that there was, but this was more for a "why wouldn't there be?" reason than anything based on knowledge) then that *may* explain it, except that I'm not able to ping the IP that I set for the TiVo (nor am I able to telnet or ftp to it).

[Jamie]

As far as I can tell from examining the tivo linux kernel source for 4.0 and 7.1, this device should be recognized in both versions. The tivo linux kernel source for 6.2 hasn't been posted yet.

It's kind of a strange device: a combined usb 1.1 hub and eth NIC. I'm not sure, but it seems that that hub and the NIC may identify themselves with different ids: link (http://www.qbik.ch/usb/devices/search_res.php?pattern=DSB-H3ETX).

The 0x7a6:0x986 id seems to be in all versions of the pegasus driver I examined, being labeled as 'ADMtek AN986 "Pegasus" USB Ethernet (evaluation board)'.

Suggestion: spend $20 and get a ax8817x based usb2 device. You'll be happier.

[jmbaker]

As far as I can tell from examining the tivo linux kernel source for 4.0 and 7.1, this device should be recognized in both versions. The tivo linux kernel source for 6.2 hasn't been posted yet.

It's kind of a strange device: a combined usb 1.1 hub and eth NIC. I'm not sure, but it seems that that hub and the NIC may identify themselves with different ids: link (http://www.qbik.ch/usb/devices/search_res.php?pattern=DSB-H3ETX).

The 0x7a6:0x986 id seems to be in all versions of the pegasus driver I examined, being labeled as 'ADMtek AN986 "Pegasus" USB Ethernet (evaluation board)'.

Suggestion: spend $20 and get a ax8817x based usb2 device. You'll be happier.
Thanks Jamie. I kind of get what you're saying, especially the last part (about buying a new adapter). One of my coworkers gave me the D-Link a few months back when I first started monkeying with my TiVo because I didn't want to buy an adapter until I saw how useful it would be (and he said that it should work since it's based on the Pegasus chipset). I'll pick up a USB200M at some point (since everyone seems to be loving this adapter) and see what happens...

[Jamie]

I'll pick up a USB200M at some point (since everyone seems to be loving this adapter) and see what happens...The love for the usb200m isn't universal. The biggest complaint is that it is fragile. I have 3 and haven't had one break yet, but YMMV. The xterasys works just as well and is cheaper and less fragile. mrtechus (http://store.mrtechus.com/xtusb2010fae.html) or newegg (http://www.newegg.com/app/ViewProductDesc.asp?description=33-147-011&depa=0).

[PlainBill]

The love for the usb200m isn't universal. The biggest complaint is that it is fragile. I have 3 and haven't had one break yet, but YMMV. The xterasys works just as well and is cheaper and less fragile. mrtechus (http://store.mrtechus.com/xtusb2010fae.html) or newegg (http://www.newegg.com/app/ViewProductDesc.asp?description=33-147-011&depa=0).

I'd like to add my two bits here. I was a strong advocate of the Netgear FA-120 (about $30 + tax). Then someone mentioned the Xterasys. It's as rugged, has a longer usb cable, and cost about $18 delivered from mrtechus.

PlainBill