8.1 and my NIC

[jasch]

I received the upgrade to 8.1, manually upgraded and replaced the kernel and startup files...

My TiVo boots and work, and I have bash.... but if I plugin my NIC (tried three different: FA-120, Linksys or Wireless) the TiVo reboots. If the NIC is inserted while loading, it keeps restarting.

So... any ideas? It's a TCD5400. Perhaps the kernel is not compatible with 8.1?

This is my bash output:


hub.c: port 1, portstatus 501, change 1, 480 Mb/s
hub.c: port 1, portstatus 501, change 0, 480 Mb/s
hub.c: port 1, portstatus 501, change 0, 480 Mb/s
hub.c: port 1, portstatus 501, change 0, 480 Mb/s
hub.c: port 1, portstatus 501, change 0, 480 Mb/s
hub.c: port 1, portstatus 511, change 0, 480 Mb/s
hub.c: port 1, portstatus 511, change 0, 480 Mb/s
hub.c: port 1, portstatus 503, change 10, 480 Mb/s
usb.c: USB device 2 (vend/prod 0x846/0x1040) is not claimed by any active driver.
hub.c: port 2, portstatus 100, change 0, 12 Mb/s
Unable to handle kernel paging request at virtual address 00000090, epc == c012af78, ra == c012af
68
Oops in fault.c::do_page_fault, line 213:
$0 : 00000000 00000000 000000c2 811fe806 811fe876 ffffffff 00000000 812b4620
$8 : 00000004 8011858c 00002222 dd6fef22 801d4260 0000001f ffffffff 8085db94
$16: c012b69c 00000000 811fe800 815dcae0 8138e400 80c789e0 00000000 c0114210
$24: 00000000 ffffffff 8085c000 8085dd58 c0103138 c012af68
Hi : 00000000
Lo : 00000800
epc : c012af78 Tainted: P
Status: 90008403
Cause : 0080000c
Process insmod (pid: 188, stackpage=8085c000)
Stack: 90008403 00800400 80146148 00000081 00000000 8085de20 00000000
00000000 801f7840 0000102d 801d5400 ffffffea c012bcd8 c012bad8 815dcae0
c012bcf8 00000000 8138e400 c0103478 800455a4 801f7840 80553c20 00000000
80070e8c 8138e428 00000000 c01032f4 00000000 8138e400 c0102ff4 00000060
8066e000 100149b0 815dcdc0 00000006 c0103078 c01032f4 00000000 8138e600
c0102ff4 ...

Trace: c012af78 c0103478 c0103078 c01030b4 c01021a8 c010210c c012b458 80028344
8001ef24 020d8f4c
Code: 00409021 8c51006c 240200c2 <ae220090> 262300c8 262400d4 262500e0 3c02c013 2442a004
Kernel panic: Die called

[Jamie]

So... any ideas? It's a TCD5400. Perhaps the kernel is not compatible with 8.1?I don't know what kernel you are using, but it's possible the stock 8.1 usb and/or network modules are not compatible with your kernel. I know on the dual tuner SA model, the stock bcmemac.o is not compatible with a kernel compiled with NETFILTER turned off.

I would suggest you either use the stock kernel (via replace_initrd) with the stock modules or see if the backport usb/network modules will work with the kernel you are using. A little experimentation via a serial console and a bare bash (nothing loaded or running yet) should lead you to a workable combination of kernel and modules pretty quickly.

[davidblack]

no problem getting 8.1 working ok here with my netgear card with the 7.2.2-OTH-K1 kernel

Cheers
David

[jasch]

I had old kernel (3.1.5). I am trying with the 8.1 kernel with the replace_initrd as Jamie suggested...

[jasch]

I was unable to replace_initrd the Kernel sucessfully

After doint it, I get this on startup:


Scan /mnt
Scan /mnt/lost+found
...
...
Scan /mnt/initrd
Scan /mnt/dev
The filesystem seems to be OK


The files I modified, were nuked. Which is strange... I also tried with the 7.2.2-OTH-K1 kernel straigth from PTVUpgrade's $5 CD.

Somehow it seems the Kernel is still doing the checksum on the files...

According to replace_initrd, the kernel was copied, the init_rd was located and the kernel was replaced back...

[Jamie]

I was unable to replace_initrd the Kernel sucessfully

After doint it, I get this on startup:


Scan /mnt
Scan /mnt/lost+found
...
...
Scan /mnt/initrd
Scan /mnt/dev
The filesystem seems to be OK


The files I modified, were nuked. Which is strange... I also tried with the 7.2.2-OTH-K1 kernel straigth from PTVUpgrade's $5 CD.

Somehow it seems the Kernel is still doing the checksum on the files...

According to replace_initrd, the kernel was copied, the init_rd was located and the kernel was replaced back...Looks to me like you are not booting the kernel you think you are.

[jasch]

I managed to get it working now. But still my NIC card makes the Tivo reboot. Funny thing is that it worked with the virgin 8.1 kernel. The replaced_initrd 8.1 kernel gives me the error...

The only different thing is the iptables file which I moved from 7.3

[jasch]

Nope. Same thing as with my old, trusted kernel...


Running boot Stage E_PreApplication scripts
Checking for database conversions
No upgrade to load
Not upgrading software
Scanning for phase3 repair scripts
Running boot Stage F_ApplicationLaunch scripts
Starting Services.
ehci_hcd EHCI-Direct: illegal capability!
hub.c: port 1, portstatus 100, change 0, 12 Mb/s
hub.c: port 2, portstatus 501, change 1, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 511, change 0, 480 Mb/s
hub.c: port 2, portstatus 511, change 0, 480 Mb/s
hub.c: port 2, portstatus 503, change 10, 480 Mb/s
usb.c: USB device 2 (vend/prod 0x846/0x1040) is not claimed by any active driver.
Unable to handle kernel paging request at virtual address 00000090, epc == c012af78, ra == c012af
68
Oops in fault.c::do_page_fault, line 213:
$0 : 00000000 00000000 000000c2 8133b406 8133b476 ffffffff 00000000 8131bc20
$8 : 00000004 8011858c 00002033 a1a9ebd4 801d4260 0000001f ffffffff 803f1b94
$16: c012b69c 00000000 8133b400 8161ba60 814e1400 811159e0 00000000 c0114210
$24: 00000000 ffffffff 803f0000 803f1d58 c0103138 c012af68
Hi : 00000000
Lo : 00000400
epc : c012af78 Tainted: P
Status: 90008403
Cause : 0080000c
Process insmod (pid: 179, stackpage=803f0000)
Stack: 00000001 00000d84 80146148 00000081 00000000 801982bc 802ab05c
8000e720 802933e0 10017000 00000001 00000004 c012bcd8 c012bad8 8161ba60
c012bcf8 00000000 814e1400 c0103478 800455a4 4672619f 0877c629 80020fac
80070e8c 814e1428 00000000 c01032f4 00000000 814e1400 c0102ff4 00000060
80e23000 100149b0 8161bd40 00000006 c0103078 c01032f4 00000000 814e1600
c0102ff4 ...

Trace: c012af78 c0103478 c0103078 c01030b4 c01021a8 c010210c c012b458 80028344
8001ef24 020d8f4c
Code: 00409021 8c51006c 240200c2 <ae220090> 262300c8 262400d4 262500e0 3c02c013 2442a004
Kernel panic: Die called

[jasch]

I will try with the backport drivers, will let you know in 5 minutes.

[mrpenguin]

FYI - I had this happen to my sd-h400 as well. upgraded to 8.1 manually like I always have. It started rebooting and never came up untill I unplugged the usb nic. I was using the 3.1.5 kernel I have used since I removed sleeper. Looking into what is going on now.

[dcahoe]

Just wanted to chime in with a similar experience. I manually took the 8.1 update on my TCD240 and it also will not boot with my wired NIC plugged in.

It it will boot with my wireless NIC plugged in, but it doesn't initialize nor work. If I try to go to network settings it won't let me see or change any settings because it says no network card detected.

My wired NIC is a DLink DUB-E100 and my wireless is a DLink DWL-G122. I also have a wired Netgear FA120, but havn't tried it yet.

[jasch]

Not related to 8.1, but my wireless NIC (Linksys USB) also stopped working since 7.2 ot 7.3. Since I went wired I tough it was something on my end. Same simptoms, TiVo says there's no network card detected, etc. Now I see I am not the only one, hehe.

[mrpenguin]

got mine to work. used the backport drivers (http://www.dealdatabase.com/forum/showthread.php?p=262633#post262633) (as I did before upgrade). I didn't have to update the hotplug file, it already had the nic in it. I think the new kernel may have the needed things for the nics.

[cheer]

I also tried with the 7.2.2-OTH-K1 kernel straigth from PTVUpgrade's $5 CD.
Maybe I'm missing something, but aren't the kernels on that CD S2 kernels? Your original post said the unit was a TCD540, so I'm thinking you need an S2.5 kernel.

[jasch]

They've worked before.

[jasch]

Confirmed. With backported drivers the unit works fine with my NIC.

[ScanMan]

For those keeping score, I just upgraded to 8.1 using the 3.1.5 killhdinitrd kernel and I did use the backport 'usbnet.o' for my FA120, not wanting to take any chances after reading this thread. With the backport driver, no reboots, no problems...

[stevevm]

I just spent the last couple of hours wrestling with my tivo trying to rehack it after getting 8.1. I can't say for sure if my problem was the same as mentioned here but I suspect it is. In the process of trying to restore things I ran into the additional problem of having my iptables disappear as described in this thread, http://dealdatabase.com/forum/archive/index.php/t-43050.html. I managed to restore it from the previous version on hda4 and got myself working again.

Does using the back port drivers simply consist of replacing a single .o file with the one for your particular usb adapter? In my case I have a Dlink DUB-E100, can someone suggest which driver is used for it?

[ScanMan]

<snip>
Does using the back port drivers simply consist of replacing a single .o file with the one for your particular usb adapter? In my case I have a Dlink DUB-E100, can someone suggest which driver is used for it?Yes, and also sometimes editing the /etc/hotplug/usb.map file (actually a symlink to /platform/etc/hotplug/usb.map). The DUB E-100 uses the same 'usbnet.o' so copy the backport one over your tivo's standard one in /lib/modules.

If you have the "revision B1" version of the DUB E-100 you'll definitely need to edit the 'usb.map' file; check out the "usb.map.additions" in Jamie's release file.

Caveat-> the foregoing assumes a DIY hacked tivo; if you used any 3rd party vendor products or "other" installation scripts, you may have to do some sleuthing to figure out how and where the usb drivers are loaded...

[brianmay27]

Ok i am stuck. i spent all last night trying to get a hacked kernel on the same modle and version. what did you use?

[lennier]

Yeah same here. If one of you scholarly gentleman can publish your methods to hack an 8.1 install and have the NIC working I'd really appreciate it...

[jasch]

Nothing out of the ordinary. Replace the kernel, install the backported drivers, replace init_rd and boot. Same as it allways been, except you can't even connect the NIC with the standard drivers or the tivo reboots.

Pull the drive to install the backported drivers, or do it via serial bash

[ScanMan]

Depends on your adapter but in general, just copy the backport driver (found here (http://www.dealdatabase.com/forum/showthread.php?p=262633#post262633)) into /lib/modules.

If you don't know which driver to use, look at the /etc/hotplug/usb.map file on your tivo and look for your device listed.

[bdjohns1]

I'll throw my <aol>me too</aol> in here too. I did the manual upgrade to 8.1 using the 3.1.5 kernel, and I was in a reboot loop until I installed the backport drivers.

Lennier, without doing one of those guide thingies that people don't seem to like around here ;) , here's what I'd do:

1) Do the usual manual install of the upgrade, preventing the reboot from happening.
2) Mount your NEW root (ie, if your root is on hda4, mount hda7) and copy the backport drivers into the /lib/modules folder on your new root.
3) Do all the other stuff you'd normally do to prep for the upgrade (iptables kill, rc.sysinit, move your hacks.
4) reboot and enjoy.

[Jamie]

We can get to the bottom of this once the 8.1 linux sources are posted. It might help if someone files a formal GPL request for source. There are instructions on where to send it at http://www.tivo.com/linux.

[lennier]

For installing the backport driver, how do I know which version I use? 2.4.4, 2.4.18, or 2.4.20? Do I also need to install the host driver as well? (usbcore.o)?

[jasch]

Check your kernel version.


bash# uname -a
Linux (none) 2.4.20 #3 Sat Oct 30 15:38:51 CDT 2004 mips unknown

[lennier]

Check your kernel version.


bash# uname -a
Linux (none) 2.4.20 #3 Sat Oct 30 15:38:51 CDT 2004 mips unknown


Duh me.
Thanks. I'll give all of this a try next weekend. Thanks for putting up with all my questions, everyone! Hopefully there are no more to come :D

[shutterfriend]

Well it has been a busy week. I just upgraded my first TiVo to 8.1 and hit this issue. I updated my usbnet.o, usbcore.o and usb-ohci.o with the backport drivers. It works with a wired usb adapter but does not detect my Netgear Wireless WG-111 usb adapter. Any ideas please?

[mrpenguin]

I had to use serial bash and copy over a few files (backport link earlier in this thread). I had to update them in the /platform/lib/modules for usbcore, usb-ohci and ehci-hcd, also updated usbnet in the /lib/modules and added symlink from ax8817->usbnet, not sure if that last part was needed. also, check your /etc/hotplug/usbmap. make sure your device is in there properly.

[shutterfriend]

I had to use serial bash and copy over a few files (backport link earlier in this thread). I had to update them in the /platform/lib/modules for usbcore, usb-ohci and ehci-hcd, also updated usbnet in the /lib/modules and added symlink from ax8817->usbnet, not sure if that last part was needed. also, check your /etc/hotplug/usbmap. make sure your device is in there properly.

I copied the usbnet.o, usbcore.o and usb-ohci.o and this allowed my wired network adapter to work but my wireless Netgear WG-111 adapter is not detected. I checked the usb.map file and my wireless adapter is in there under both CM????? and isl???? (can't remember full name). Do I need ehci-hcd and ax8817 or does this not matter?

Any help would be appreciated.

[shackeh]

Well it has been a busy week. I just upgraded my first TiVo to 8.1 and hit this issue. I updated my usbnet.o, usbcore.o and usb-ohci.o with the backport drivers. It works with a wired usb adapter but does not detect my Netgear Wireless WG-111 usb adapter. Any ideas please?

This is my problem as well I assume. I have a series 2 (240) box with the 2.4.20 kernel. I copied the usbcore.o and usb-ohci.o from the obj\hosts\2.4.20_Series2 directory of the backport archive to the /lib/modules directory on my TiVo. Then I copied usbnet.o from the obj\drivers\2.4.20 directory to /lib/modules. The rebooting stopped but the wireless nic is not detected. I checked the usb.map and there is an entry for that nic. Is there anywhere else I can check?
Thanks!

[Jamie]

The wireless support in the backport package is minimal. AFAIK, no 802.11g adapters are supported. So you may want to stick with the stock tivo modules. To do that, you need to boot the stock kernel. The only way to boot the stock kernel on a hacked tivo without a prom mod is to replace the initrd with a null initrd and monte to it.

Perhaps someone can examine the 8.1 kernel to see if the killhdinitrd exploit can be applied to it.

[ScanMan]

The "Netgear WG111" is under the "device CNXTSPDriver" of the wireless section of the usb.map file. However there are specific serial numbers that are supported for this NIC by tivo and listed at their website; if it's not listed, it's not supported and AFAIK there is currently no backport driver for this NIC.

[shutterfriend]

ScanMan,

I have been using this wireless adapter since 7.3 and it is in the range of serial numbers supported. The issue is since I upgraded to 8.1 it continuously reboots if that usb wireless device is installed and I don't have the backport drivers installed. Since I installed the backport drivers I can have the wireless adapter inserted and it does not reboot but it does not detect it.

Shutterfriend

[ScanMan]

As Jamie alluded to, it appears something is perhaps present in the stock 8.1 kernel that's missing. See if the "CNXTSPDriver.o" in /lib/modules is a different size in 8.1 vs. 7.3.1. You could maybe try the old 7.3.1 module and see if that works. Also, I would download the "7.2.2.-oth-K1" kernel that drez linked in the image begging thread, run killhdinitrd 0.9.3 on it and see if it changes anything. Perhaps the newer kernel will solve your problem versus the old 3.1.5 kernel.

[shutterfriend]

ScanMan,

Thanks for your help. Jamie is currently working with me to resolve the issue. I believe we are going to just monte the new 8.1 kernel that has been null initd'd and go back to the original stock usb drivers to see if it works. Just waiting on Jamie to get back to me now.

I will let you know the outcome.

Shutterfriend

[shackeh]

I have tried going to the 7.2 kernel posted in the slice thread with no success. I will try grabbing the driver from 7.3.

[Jamie]

don't know why I didn't think of that: you should be able to use the tivo supplied 7.3.1 drivers for the devices not supported by the backport drivers.

[shutterfriend]

I tried just replacing the isl38sm.o, CNX....o and p80211autojoin.o which is indicated in the usb.map to be used by my adapter but it still reboots. Should I try replacing the usbcore.o, usb-ohci.o and usbnet.o also?

[shutterfriend]

I also replaced usb-ohci, usbnet, usbcore and ehci-hcd and still continuously reboots.

[Jamie]

I also replaced usb-ohci, usbnet, usbcore and ehci-hcd and still continuously reboots.Kernel log?

We know the 7.3.1 modules work with the previous kernels we've used in the past, so this should work if you've done everything right.

[shutterfriend]

Jamie,

I can get on the Tivo now because I switched back to backport drivers at least so I can connect with wired adapter as I am in the process of switching to 3.1.1c kernel with 8.1 kernel monte'd.

So the file you want is the kernel file in the /var/log directory, right?

[shutterfriend]

Jamie,

Okay what files do you want me to copy over specifically and I will do that and then start TiVo and let you know the results. If you keeps rebooting I get the logs for you.

Shutterfriend

[Jamie]

Jamie,

Okay what files do you want me to copy over specifically and I will do that and then start TiVo and let you know the results. If you keeps rebooting I get the logs for you.

ShutterfriendA serial console kernel log is the standard debugging tool for debugging startup problems.

[shutterfriend]

Sorry about that. Yes I will get you the serial console log after I recopy the files over.

I am copying the following files from 7.3.1:

/lib/modules - CNXTSPDriver.o, isl38sm_usb.o, old-p80211.o, old-prism2_usb.o, p80211.o, p80211autojoin.o, pegasus.o, rtl8150.o, usb-cdc.o, usb-storage.o, usbnet.o and vnetusba.o

/platform/lib/modules - ehci-hcd.o, usb-ohci.o and usbcore.o

I will post the serial console log as soon as I can.

[shutterfriend]

Hi,

It successfully booted up and I am able to access the network with my wireless network adapter again. Please see previous post of all the files that I copied from the 7.3.1 lib/modules and platform/lib/modules.

Jamie, Thanks for pushing me to try again. I obviously was missing some of the drivers.

[brianmay27]

Ok i need help. i have a linksys wusb11 V. 2.8. i have been trying to get it work but failed. please help me pry my face way from the screen

[brianmay27]

also (yes i know i am stupid) i deleted old-prism2 file is this bad? also it did not help before

[shackeh]

Hi,

It successfully booted up and I am able to access the network with my wireless network adapter again. Please see previous post of all the files that I copied from the 7.3.1 lib/modules and platform/lib/modules.

Jamie, Thanks for pushing me to try again. I obviously was missing some of the drivers.

This seems to have fixed me up as well. Thanks everyone!!

[Mr2001]

I copied the 7.3.1 modules over and that solved the crashing and non-detection of my TiVo brand wireless adapter... however, with this setup it doesn't support WPA, which is one of the main selling points of 8.1!

I get to choose a security mode (WEP, WPA, WPA2, None), but when I select WPA, I get this error:

"Wpa Not Supported

To use WPA, you must have a TiVo Wireless G USB Network Adapter. Try one of the following:

* Set your router to use a different type of wireless security that is supported by your network adapter.
* Use the TiVo Wireless G USB Network Adapter. See www.tivo.com/adapters for more information."

Of course, that's the one I have. :mad:

I backed up the original modules, so I can restore them when I get a hacked 8.1 kernel, but I hacked this kernel so long ago that I have no idea how to do it anymore.

[Mr2001]

OK, it seems that what I need to do is replace the initrd in the stock kernel and then monte to it... after a lot of searching, I found replace_initrd.c and compiled it, then used it on a copy of my stock 8.1 kernel.

However, monte isn't working. I can insmod kmonte.o, extract a copy of the kernel I'm using (a killhdinitrd'd 2.4.20 kernel from some 7.x version), and monte it no problem. The grey "powering up" screen appears immediately. If I try this with the 8.1 kernel, however--which also seems to be 2.4.20--then the box just freezes, and several minutes later it reboots into my installed 7.x kernel.

[Jamie]

OK, it seems that what I need to do is replace the initrd in the stock kernel and then monte to it... after a lot of searching, I found replace_initrd.c and compiled it, then used it on a copy of my stock 8.1 kernel.

However, monte isn't working. I can insmod kmonte.o, extract a copy of the kernel I'm using (a killhdinitrd'd 2.4.20 kernel from some 7.x version), and monte it no problem. The grey "powering up" screen appears immediately. If I try this with the 8.1 kernel, however--which also seems to be 2.4.20--then the box just freezes, and several minutes later it reboots into my installed 7.x kernel.Try monteing from the 3.1.1c killhdinitrd kernel with the 2.4.4 kmonte.o. It's more reliable.

[ScanMan]

OK, it seems that what I need to do is replace the initrd in the stock kernel and then monte to it... after a lot of searching, I found replace_initrd.c and compiled it, then used it on a copy of my stock 8.1 kernel.

However, monte isn't working. I can insmod kmonte.o, extract a copy of the kernel I'm using (a killhdinitrd'd 2.4.20 kernel from some 7.x version), and monte it no problem. The grey "powering up" screen appears immediately. If I try this with the 8.1 kernel, however--which also seems to be 2.4.20--then the box just freezes, and several minutes later it reboots into my installed 7.x kernel.
Serial console output is critical in troubleshooting these types of problems...

[brianmay27]

does any one know if ndiswrapper works in tivo? and if the driver will work

[dcahoe]

Just thought I would report back in with my findings. I also reported 8.1 NIC problems after updating. My wired adapters went into a reboot loop and my wireless was not detected but did not cause a reboot loop.

I tried Jamie's backport drivers and was able to get my wired adapters to work (I have a Netgear FA120 and a DLink DUB-E100 which both use the usbnet.o driver). But my wireless adapter was still not detected and still would not work.

So I tried Shutterfriend's method of copying the 7.3.1 drivers over the 8.1 drivers. I have a DLink DWL-G122 rev.A2 wireless adapter so I only copied the isl38sm_usb.o, p80211.o, p80211autojoin.o and usbnet.o drivers (along with usbcore.o, usb-ohci.o and ehci-hcd.o)

I am happy to report total success. Now my wired and wireless work with 8.1 and my killhdinitrd modified kernel and my telnet and NCID is good to go.

[brianmay27]

Where do you get the 7.3.1 drivers. tryed the tivo/linux online download but did not find some of the drivers. can you help me out

[Mr2001]

Serial console output is critical in troubleshooting these types of problems...
OK, here's what I get:

tivo:/var/tmp$ cd /var/monte
tivo:/var/monte$ ls
8.1-kernel-null kmonte.o old-kernel-null
hda6.kernel monte
kernel-null-linuxrc old-kernel-killed
tivo:/var/monte$ insmod kmonte.o
monte: MuscleNerd (MIPS version), Erik Arjan Hendriks (x86 version)
tivo:/var/monte$ bootpage -p /dev/hda
root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false
tivo:/var/monte$ ./monte 8.1-kernel-null "root=/dev/hda4 dsscon=true console=2,1
15200 upgradesoftware=false"
monte: loaded kernel image (target load_addr=0x80001fe0, len=0x1a9fdf) at 0x8057
dfe0
monte: total pages used: 428 for image, 2 for indirect tables, 1 for reload code

CPU revision is: 00005430
FPU revision is: 00005410
Primary instruction cache 32kb, linesize 32 bytes.
Primary data cache 32kb, linesize 32 bytes.
Linux version 2.4.20 (build@buildmaster59) (gcc version 3.3.4) #1 Thu Oct 26 01:
35:03 PDT 2006
Determined physical RAM map:
memory: 01e2b000 @ 001d5000 (usable)
Initial ramdisk at: 0x80187000 (316399 bytes)
On node 0 totalpages: 8192
zone(0): 8192 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware
=false
Monotonic time calibrated: 81.01 counts per usec
Calibrating delay loop... 161.79 BogoMIPS
Contiguous region 1: 1048576 bytes @ address 0x81900000
Contiguous region 2: 524288 bytes @ address 0x81a00000
Contiguous region 8: 5767168 bytes @ address 0x81a80000
Contiguous region of 7340032 bytes total reserved at 0x81900000.
Memory: 23364k/30892k available (1228k kernel code, 7528k reserved, 69k data, 64
k init, 0k highmem)
Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Checking for 'wait' instruction... unavailable.
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
ttyS00 at iomem 0xb4100100 (irq = 79) is a 16550A
ttyS00 at port 0xbc010000 (irq = 133) is a unknown
ttyS00 at iomem 0xb4100140 (irq = 81) is a 16550A
ttyS00 at iomem 0xb4100120 (irq = 80) is a 16550A
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en
abled
ttyS00 at 0xb4100100 (irq = 79) is a 16550A
ttyS01 at 0xbc010000 (irq = 133) is a unknown
ttyS02 at 0xb4100140 (irq = 81) is a 16550A
ttyS03 at 0xb4100120 (irq = 80) is a 16550A
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hda: Maxtor 6Y120P0, ATA DISK drive
ide0 at 0x400-0x407,0x438 on irq 87
hda: 240121728 sectors (122942 MB) w/7936KiB Cache, CHS=238216/16/63
Partition check:
hda:<6>fpga_ide: lost IRQ
hda: lost interrupt
fpga_ide: DMA error status
hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
hda: status timeout: status=0xd0 { Busy }
hda: DMA disabled
hda: re-enabled DMA
hda: drive not ready for command
ide0: reset: success
fpga_ide: lost IRQ
hda: lost interrupt
fpga_ide: DMA error status
hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
hda: status timeout: status=0xd0 { Busy }
hda: DMA disabled
hda: re-enabled DMA
hda: drive not ready for command
ide0: reset: success
...
It just keeps repeating everything after "fpga_ide: lost IRQ" for a few minutes, then gives up and restarts:hda: lost interrupt
fpga_ide: DMA error status
hda: dma_intr: status=0x58 { DriveReady SeekComplete DataRequest }
end_request: I/O error, dev 03:00 (hda), sector 6
unable to read partition table
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
Software Watchdog Initialized
Kernel Panic Logger registered
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 2048 bind 4096)
ip_conntrack version 2.1 (256 buckets, 2048 max) - 152 bytes per conntrack
ip_tables: (C) 2000-2002 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 308k freed
VFS: Mounted root (romfs filesystem) readonly.
hda4: bad access: block=2, count=2
end_request: I/O error, dev 03:04 (hda), sector 2
EXT2-fs: unable to read superblock
hda4: bad access: block=0, count=2
end_request: I/O error, dev 03:04 (hda), sector 0
romfs: unable to read superblock
Kernel panic: VFS: Unable to mount root fs on 03:04
Core of 0 bytes written
Rebooting in 1 seconds..

[ocntscha]

OK, here's what I get:

It just keeps repeating everything after "fpga_ide: lost IRQ" for a few minutes, then gives up and restarts:Sorry Mr2001 but that sure looks like a failing hard drive to me. I think its probably just a coincidence that you are encountering that problem in the midst of experimenting with monte.


I monte into an 8.1 kernel I've run replaceinitrd on and and my console log looks identical to yours right up until the point where you get that hda:<6>fpga_ide: lost IRQ error. Also, I have encountered that DriveReady SeekComplete error before not on a Tivo but on i386 Linux boxes and it definately signified hard ware problems. One time a drive that was going bad / another time I was using a 3 foot IDE cable that was the culprit.

[Jamie]

Sorry Mr2001 but that sure looks like a failing hard drive to me. I think its probably just a coincidence that you are encountering that problem in the midst of experimenting with monte.


I monte into an 8.1 kernel I've run replaceinitrd on and and my console log looks identical to yours right up until the point where you get that hda:<6>fpga_ide: lost IRQ error. Also, I have encountered that DriveReady SeekComplete error before not on a Tivo but on i386 Linux boxes and it definately signified hard ware problems. One time a drive that was going bad / another time I was using a 3 foot IDE cable that was the culprit.It's also possible that it is a problem with the kernel, or with hardware re-initialization in the monte. If it works reliably (except for networking) with the 7.2.2-oth.K1 or 3.1.5 killhdinitrd kernels, without ide errors, I'd still leave the option that it is a monte problem open.

What hardware are you on? If it is identical to ocntscha's and your "from" and "to" kernels are the same, that would tend to reinforce the theory that it is a hard disk problem.

[Mr2001]

It's a 240 series with a Maxtor drive that I installed about two years ago. I wouldn't write off the possibility that the drive is failing--three Maxtors I bought around that time all died--but my money is still on monte causing some drive reinitialization problem:

First, because the unit has been working fine for all this time, booting the 7.x kernel flawlessly. (I forget which version that kernel came from, but I know I ran killhdinitrd on it - does that mean it has to be 7.2.2-oth.K1?)

Second, because I installed the 3.1.1c kernel last night and I've now got monte loading the 8.1 kernel with no problems. After putting the 8.1 modules back, I can finally use WPA on my network instead of sticking with WEP just for TiVo.

I didn't want to try that at first because it meant setting up a working boot sequence all at once (rather than just logging in and running monte by hand to see if it works), and pulling the drive every time I screw that up is a pain.. but I only had to do it twice last night. ;)

[ScanMan]

<snip>...rather than just logging in and running monte by hand to see if it works...<snip>I'm not sure you can "run monte by hand" which is what I suspected you were doing in looking at your log. Anyway, glad you got it all working.

[Jamie]

I'm not sure you can "run monte by hand" which is what I suspected you were doing in looking at your log. Anyway, glad you got it all working.You can. I do that whenever I'm testing a new combination of from/to kernels before committing to it. I always do it from a bare bash, without tivo software running. I'm not sure how well it works if you have a bunch of kernel modules loaded and processes running. I seem to remember if barfs if you monte with the usb modules loaded.

[ScanMan]

You can. I do that whenever I'm testing a new combination of from/to kernels before committing to it. I always do it from a bare bash, without tivo software running. I'm not sure how well it works if you have a bunch of kernel modules loaded and processes running. I seem to remember if barfs if you monte with the usb modules loaded.Thanks for clarifying Jamie; I wasn't sure...it's a good thing to know.:D

[fishbate]

Which kernel are you using, dcahoe? I've got the same wireless adapter and tried copying the 7.3.1 usb drivers but no go. I'm using a killed 3.1.5 kernel and debating whether to try the 7.2.2-oth-k1 kernal. Thanks.



Just thought I would report back in with my findings. I also reported 8.1 NIC problems after updating. My wired adapters went into a reboot loop and my wireless was not detected but did not cause a reboot loop.

I tried Jamie's backport drivers and was able to get my wired adapters to work (I have a Netgear FA120 and a DLink DUB-E100 which both use the usbnet.o driver). But my wireless adapter was still not detected and still would not work.

So I tried Shutterfriend's method of copying the 7.3.1 drivers over the 8.1 drivers. I have a DLink DWL-G122 rev.A2 wireless adapter so I only copied the isl38sm_usb.o, p80211.o, p80211autojoin.o and usbnet.o drivers (along with usbcore.o, usb-ohci.o and ehci-hcd.o)

I am happy to report total success. Now my wired and wireless work with 8.1 and my killhdinitrd modified kernel and my telnet and NCID is good to go.

[dcahoe]

Which kernel are you using, dcahoe? I've got the same wireless adapter and tried copying the 7.3.1 usb drivers but no go. I'm using a killed 3.1.5 kernel and debating whether to try the 7.2.2-oth-k1 kernal. Thanks.

I am using a 2.4.20 kernel.

[cheer]

I think he was asking *which* 2.4.20 kernel...the 3.1.5 or the 7.2.2-oth-k1?

[dcahoe]

Definitely not the 3.1.5.

[Jamie]

It shouldn't matter. The backport drivers will work with either one.

[mmiller2]

Second, because I installed the 3.1.1c kernel last night and I've now got monte loading the 8.1 kernel with no problems. After putting the 8.1 modules back, I can finally use WPA on my network instead of sticking with WEP just for TiVo.

I didn't want to try that at first because it meant setting up a working boot sequence all at once (rather than just logging in and running monte by hand to see if it works), and pulling the drive every time I screw that up is a pain.. but I only had to do it twice last night. ;)

Can you advise me how to monte load the 8.1 kernel? I have the TiVo wireless adapter and also need to use WPA.

I know how to replace the 8.1 kernel with the killhdinitrd'ed 3.1.1c kernel, and modify /sbin/iptables, but what is the next step?

[Mr2001]

Can you advise me how to monte load the 8.1 kernel? I have the TiVo wireless adapter and also need to use WPA.

I know how to replace the 8.1 kernel with the killhdinitrd'ed 3.1.1c kernel, and modify /sbin/iptables, but what is the next step?
Save a copy of your 8.1 kernel, and replace the initrd in it with the null image. If you haven't done this already, search the forums for replace_initrd.c, and in a really old thread you'll find the source code and the image you need.

Now make a directory to store your monte files. I called mine /boot, and inside it I have:

kmonte-2.4.4.o (the kernel module)
monte (the executable)
8.1-kernel-null (my modified kernel)
rc.monte (my monte startup script)

Here's my startup script, although you can find similar ones all over the forums:#!/bin/bash

bootparm=`/sbin/bootpage -p /dev/hda`
module=/boot/kmonte-2.4.4.o
target=/boot/8.1-kernel-null

echo "/boot/rc.monte: shell='$shell' sp='$sp'"

if [ "$shell" == "true" ]; then
# open a shell immediately
echo "Entering emergency shell..."
export PATH=.:/usr/local/sbin:/sbin:/usr/local/bin:/bin:/tivobin:/tvbin:/etc/rc.d
export TERM=xterm
export PS1='\h:\w$ '
/bin/bash</dev/ttyS2&>/dev/ttyS2
fi

if [ "$sp" != "true" ]; then
# first pass - monte the 8.1 kernel
echo "MONTE STARTING: new kernel is $target, boot params='$bootparm sp=true'"
/sbin/insmod $module
/boot/monte $target "$bootparm sp=true"
# if we get here, monte didn't work
echo "MONTE FAILED! Here's a shell, you're on your own..."
export PATH=.:/usr/local/sbin:/sbin:/usr/local/bin:/bin:/tivobin:/tvbin:/etc/rc.d
export TERM=xterm
export PS1='\h:\w$ '
/bin/bash</dev/ttyS2&>/dev/ttyS2
else
# second pass
echo "MONTE OK! Hopefully, this is $target"
fiMake sure the script is executable (chmod a+x /boot/rc.monte) and then add this to your /etc/rc.sysinit to invoke it, before the "starting rc.sysinit" line:echo "Checking for monte"

if [ -x /boot/rc.monte ]; then
/boot/rc.monte
fiNow you should be ready (someone please let me know if I missed a step). Leave all your 8.1 modules in place, install the 3.1.1c kernel, reboot, and monte should work its magic.

If you use this script and you have a serial cable hooked up, then you can use the PROM menu to add shell=true to the boot params if anything goes wrong, and the script will drop you to a shell so you can fix it without pulling out the drive.

[fishbate]

I've got a D-Link DWL-122, and a 3.1.5 killed kernel. Haven't had wireless working since the 8.1 upgrade. I tried the backport drivers, but the TiVo still doesn't recognize the wireless adapter. This is the first time I've tried the backport drivers, so I'm probably missing something. Specifically, I copied the files from obj/drivers/2.4.20 to the /lib/modules, then I copied from obj/hosts/2.4.20_Series2 to /platform/lib/modules, and then ifonfig to /sbin.

Do a reboot, plug in the adapter and get

usb.c: USB device 2 (vend/prod 0x2001/0x3700) is not claimed by any active driver.
init_module: prism2_usb.o: 0.1.14-pre6-tivo Loaded
init_module: dev_info is: prism2_usb
hfa384x_drvr_setconfig: Called from within soft interrupt context.
hfa384x_drvr_setconfig: Called from within soft interrupt context.
prism2sta_mlmerequest: Unknown mgmt request message 0x00000143<3>hfa384x_drvr_setconfig: Called from within soft interrupt context.


It looks to me like it can't find the driver for my adapter...

[mmiller2]

Many thanks Mr2001! I have everything setup to go, except that I'm not sure where I'm supposed to insert this code:

echo "Checking for monte"

if [ -x /boot/rc.monte ]; then
/boot/rc.monte
fi

My /etc/rc.d/rc.sysinit doesn't have a line that says "starting rc.sysinit." Am I supposed to be using some sort of custom rc.sysinit file?

[ocntscha]

Many thanks Mr2001! I have everything setup to go, except that I'm not sure where I'm supposed to insert this code:

echo "Checking for monte"

if [ -x /boot/rc.monte ]; then
/boot/rc.monte
fi

My /etc/rc.d/rc.sysinit doesn't have a line that says "starting rc.sysinit." Am I supposed to be using some sort of custom rc.sysinit file?

Put it between the first and second lines of you rc.sysinit. If your rc.sysinit is like mine then following Mr2001's excellent instructions you'd end up with..

#!/bin/bash
echo "Checking for monte"

if [ -x /boot/rc.monte ]; then
/boot/rc.monte
fi
##############################################################################
#
# File: /etc/rc.d/rc.sysinit
#
# Description: System startup script, run once at boot time
#
# Copyright (c) 2003 TiVo Inc.
#
#############################################################################

[drez]

Alternatively, you can make a test.conf file in root (/test.conf) and put that in there.

(you know how to edit/make files in vi/joe right... also i would chmod 755 every file just in case)

[Mr2001]

Many thanks Mr2001! I have everything setup to go, except that I'm not sure where I'm supposed to insert this code:

echo "Checking for monte"

if [ -x /boot/rc.monte ]; then
/boot/rc.monte
fi

My /etc/rc.d/rc.sysinit doesn't have a line that says "starting rc.sysinit." Am I supposed to be using some sort of custom rc.sysinit file?
I put mine near the bottom of the script. I thought that "starting rc.sysinit" line was there originally, but maybe I added it...echo "Checking for monte"

if [ -x /boot/rc.monte ]; then
/boot/rc.monte
fi

echo "Starting rc.sysinit"

for SysinitStage in A_PreKickstart \
B_PostKickstart \
C_MediaInitialization \
D_PreMfs \
E_PreApplication \
F_ApplicationLaunch \
G_PostApplication ; do
RunStage $SysinitStage
done

echo "rc.sysinit is complete"

[zobetron]

Begging for original 8.1-01-2-240 version of:

usbnet.o

I overwrote it without thinking...

PM Me

Thanks

[overdone]

first of all, thanks for all the great info in this thread.

I finally got around to installing the 8.1 update last night.
everything went fine (apparently) but when I rebooted I got a kernel error. So I had to pull out my HD and recopied over the original 8.1 kernel and replace_initrd'd it again and then it worked fine... except that it would hang with my NIC plugged in (I have a wired Linksys USB200M which I'm not sure what version it is). So I unplugged the NIC and rebooted it and everything works fine.

All my hacks work fine, everything except for the NIC makes it reboot when plugged in.

I originally put the usbnet.o from the backport drivers linked on this page into the lib/modules folder and left it at that: I didn't edit any files nor copy anything else. but that caused the TiVo to hang when booting.

I then used Teraterm over the serial bash to send another copy of usbnet.o to the TiVo and tried that one but then the TiVo got stuck in a reboot loop.

My questions are two-fold:

1) What files should I be transferring over to get my NIC to work? I see different reports in this thread using different combos of files. Should I be using the backport drivers or my 7.3 drivers which I saved?

2) Is the Teraterm serial bash method an okay way to transfer files?
I perform the 'rz' command on the tivo and then use zmodem to send the file over. It seems to work fine but I'm concerned because the zmodem'd file gave different results than the one I ftp'd over before the update.

Any answers or advice are welcome. Thanks for making this a great board.

[Narf54321]

Tivo should include a driver for the linksys USB200M. There's already been a report of a USB200M v2.1 which does not work (yet) on Tivo. Get telnet working with the Tivo before replacing the drivers.

Its been awhile since I used rz, but it should work. You need to absolutely make sure that TeraTerm is set to binary mode before sending the file over.

[overdone]

Tivo should include a driver for the linksys USB200M. There's already been a report of a USB200M v2.1 which does not work (yet) on Tivo. Get telnet working with the Tivo before replacing the drivers.


don't I need the NIC to be working to use telnet?


Its been awhile since I used rz, but it should work. You need to absolutely make sure that TeraTerm is set to binary mode before sending the file over.

I did set it to binary mode so it should be working. Thanks!

[Narf54321]

don't I need the NIC to be working to use telnet?

I mean that Tivo should include a working USB driver themselves. Its 'slow' compared to Jamie's backported drivers, but works. You need to disable iptables firewall and set up tnlited to accept connections.

I did set it to binary mode so it should be working. Thanks!

It may be that usbnet.o module you're trying to use either doesn't work on 8.1 software, or isn't being loaded properly.

If you can somehow validate the usbnet.o file, that would help determine if its corrupted. MD5 would work, if AlphaWolf's all-in-one utilities are installed on your Tivo:

My_Tivo# md5sum /lib/modules/usbnet.o
867affce526337416a94d5b25a28ccd4 /lib/modules/usbnet.o

Worst case, you take the Tivo apart again, and pull the drive to copy all the extra stuff to it.

[overdone]

I mean that Tivo should include a working USB driver themselves. Its 'slow' compared to Jamie's backported drivers, but works. You need to disable iptables firewall and set up tnlited to accept connections.

Do I need to copy more than just usbnet.o for it to work properly?
I don't "need" the extra speed but it'd sure be nice since I transfer alot of files to my computer.


If you can somehow validate the usbnet.o file, that would help determine if its corrupted. MD5 would work, if AlphaWolf's all-in-one utilities are installed on your Tivo.

I do have AlphaWolf's utils installed so I'll validate the file when I get home tonight.

[Jamie]

I mean that Tivo should include a working USB driver themselves. Its 'slow' compared to Jamie's backported drivers, but works. You need to disable iptables firewall and set up tnlited to accept connections.


...Narf, I'm not sure you are in touch with what is going on in this thread.

The tivo supplied usb/network modules that ship with 8.1 do not work with any of the kernels supported by killhdinitrd. Any attempt to use the stock 8.1 usb/network modules with the current killhdinitrd'd supported kernels will result in a kernel panic. Your choice is to either: Monte to a replace_initrd'd stock 8.1 kernel and use the 8.1 usb/network modules. Use the tivo supplied 7.3.1 usb/network modules with a 3.1.5 or 7.2.2-oth.K1 killhdinitrd'd kernel. Use the backport usb modules with a 3.1.5 or 7.2.2-oth.K1 killhdinitrd'd kernel.For option 2 and 3, I would replace /platform/lib/modules{ehci*,usb*}.o and /lib/modules/usbnet.o , assuming your dongle uses that driver.

Now that the 8.1 kernel sources are out we might be able to sort out what is going on. I did a quick diff against the 7.3.1 kernel sources, and nothing obvious jumped out at me.

[overdone]

Your choice is to either:[list=*] Monte to a replace_initrd'd stock 8.1 kernel and use the 8.1 usb/network modules.

So because I used the stock kernel w/ replace_initrd, I could put the stock 8.1 usb/modules back in and that should work?

[Jamie]

So because I used the stock kernel w/ replace_initrd, I could put the stock 8.1 usb/modules back in and that should work?Yes, if you are truely running that kernel. If you are, you must either have a PROM mod, a chainload (monte) setup, or you know some other way to break the chain of trust to allow you to boot a modified kernel.

[overdone]

Yes, if you are truely running that kernel. If you are, you must either have a PROM mod, a chainload (monte) setup, or you know some other way to break the chain of trust to allow you to boot a modified kernel.

I have a prom mod on a series 2.5

i'll try the 8.1 drivers when i get home tonight.

[overdone]

tried to put all the backport drivers in place but couldn't get it to work without starting a reboot loop...

now i'll try the original 8.1 drivers that I luckily backed up.

[overdone]

8.1 drivers still didn't work... it causes a kernel error... (which causes a reboot loop)

anyone have any other ideas?

[Jamie]

8.1 drivers still didn't work... it causes a kernel error... (which causes a reboot loop)

anyone have any other ideas?Post the kernel log. If it is still the driver problem, then you didn't properly restore the stock drivers. Post the md5sum's of /platform/lib/modules/*.o and /lib/modules/usbnet.o and we can verify. The other possibility is iptables.

[overdone]

weirdest thing...

now I booted without the NIC plugged in and it booted fine, then I plugged it in and it worked. I connect over telnet to test it and it worked fine.

now i'll reboot and see if it hangs again...

[overdone]

well it works now... and i'm not sure why...
the only thing i changed was i added a "iptables -F" line to my rc.sysinit.author file. but that shouldn't have been a problem since my iptables file only had an exit 0 call in it.

the only thing that still concerns me (aside from my lack of understanding how I got it to work) is this part of the log coming over the serial bash:


Running boot Stage F_ApplicationLaunch scripts
Starting Services.
ehci_hcd EHCI-Direct: illegal capability!
hub.c: port 1, portstatus 100, change 0, 12 Mb/s
hub.c: port 2, portstatus 501, change 1, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 511, change 0, 480 Mb/s
hub.c: port 2, portstatus 511, change 0, 480 Mb/s
hub.c: port 2, portstatus 503, change 10, 480 Mb/s
usb.c: USB device 2 (vend/prod 0x77b/0x2226) is not claimed by any active driver
.
Logger not initialized! Logging to stdout:
TmkLogger: <133>Jan 18 06:13:41 TmkServer[200]: Enabling port 5353, protocol udp


anyone know what the deal is with the "illegal capability" part and the
USB device 2 not being claimed by any active driver???

Thanks again for all the help by everyone in the thread, especially Jamie and Narf.

[Jamie]

anyone know what the deal is with the "illegal capability" part and the
USB device 2 not being claimed by any active driver???Both are normal and nothing to worry about.

[overdone]

Both are normal and nothing to worry about.

cool. thanks.

[blickdot]

I have a 2.5 (T800) running 8.1 / 2.4.20 (replace_initrd )

In choosing a network adapter, would I not possibly be better off with a Tivo brand WirelessG interface?
Since the transfer rate is less due to the 2.5 processor, and (from what I've read) the Tivo hands off some of the processing to the Tivo Wireless G.
I've also read that the most I could expect out of a wired adapter on a 2.5 would be maybe 3-4MB/sec mentioned here (http://www.dealdatabase.com/forum/showpost.php?p=229083&postcount=51) my Jamie.

I'm thinking that with the added proceeding power of the adapter I might come out ahead. Has anyone had any experience with this?

I haven't seen much on the thru-put of the Tivo WirelessG.

I'm just not sure if it would be worth the extra cost for a Tivo WirelessG?

[Jamie]

I have a 2.5 (T800) running 8.1 / 2.4.20 (replace_initrd )

In choosing a network adapter, would I not possibly be better off with a Tivo brand WirelessG interface?
Since the transfer rate is less due to the 2.5 processor, and (from what I've read) the Tivo hands off some of the processing to the Tivo Wireless G.
I've also read that the most I could expect out of a wired adapter on a 2.5 would be maybe 3-4MB/sec mentioned here (http://www.dealdatabase.com/forum/showpost.php?p=229083&postcount=51) my Jamie.

I'm thinking that with the added proceeding power of the adapter I might come out ahead. Has anyone had any experience with this?

I haven't seen much on the thru-put of the Tivo WirelessG.

I'm just not sure if it would be worth the extra cost for a Tivo WirelessG?If you are going wireless, by all reports I've seen, you'll be better off with the tivo branded adapter compared to anything else. There is the option of a wired adapter and a wireless bridge, which might work as well or better, but may not be any cheaper.

I suspect a wired connect would still beat eather of these options, but I haven't really compared closely.

[Narf54321]

I have one S2 Tivo with the Tivo wireless adapter. It works well.

Since I am using Jamie's backport drivers on the other machines, I'm getting about 2.2 to 2.4MB downloads on 'wired' connections. The wireless adapter runs at about 1.1MB, about half the speed.

A further comparison, 1MB is about on par with the default drivers Tivo gives you with Tivo-to-Go.

[overdone]

A further comparison, 1MB is about on par with the default drivers Tivo gives you with Tivo-to-Go.

is this with the backport drivers or the 8.1 drivers?

[blickdot]

I have one S2 Tivo with the Tivo wireless adapter. It works well.

Since I am using Jamie's backport drivers on the other machines, I'm getting about 2.2 to 2.4MB downloads on 'wired' connections. The wireless adapter runs at about 1.1MB, about half the speed.

A further comparison, 1MB is about on par with the default drivers Tivo gives you with Tivo-to-Go.

Narf54321

Is that with the Tivo brand wireless adapter or a regular 802.11b wireless?

is this with the backport drivers or the 8.1 drivers?

I don't believe the TivoWirelessG adapter is a USB 2.0 device though I'm not entiely sure.

I don't think it uses drivers in the normal way.

I plugged one in today and it works but I get this on start up (using stock drivers):
------------------------------------------------------------------------
hub.c: port 1, portstatus 100, change 0, 12 Mb/s
hub.c: port 2, portstatus 501, change 1, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 511, change 0, 480 Mb/s
hub.c: port 2, portstatus 511, change 0, 480 Mb/s
hub.c: port 2, portstatus 503, change 10, 480 Mb/s
usb.c: USB device 2 (vend/prod 0xa5c/0xbd11) is not claimed by any active driver.
hub.c: port 1, portstatus 100, change 0, 12 Mb/s
hub.c: port 2, portstatus 501, change 1, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 501, change 0, 480 Mb/s
hub.c: port 2, portstatus 511, change 0, 480 Mb/s
hub.c: port 2, portstatus 503, change 10, 480 Mb/s
-------------------------------------------------------
But it works just fine?

------------------------------------------
ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:d9:34:A2:d9
inet addr:192.168.0.200 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:316 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:20451 (19.9 Kb)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:102 errors:0 dropped:0 overruns:0 frame:0
TX packets:102 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7392 (7.2 Kb) TX bytes:7392 (7.2 Kb)
---------------------------------------------------------------
telnet, FTP TWP working!

[Jamie]

...

I don't believe the TivoWirelessG adapter is a USB 2.0 device though I'm not entiely sure.It is.

I don't think it uses drivers in the normal way.
It does. It uses the usb-cdc driver. See /etc/hotplug/usb.map.

I plugged one in today and it works but I get this on start up (using stock drivers):
------------------------------------------------------------------------
hub.c: port 1, portstatus 100, change 0, 12 Mb/s
...
That's all normal and not specific to the tivo Wireless-G adapter.

[blickdot]

I stand corrected :o

The TivoWirelessG is a USB 2.0 device and it uses the usb-cdc driver.

From usb.map:
---------------------------------------------------
device usb-cdc
product 0a5c bd11 CDC Downloader
product 0a5c 0cdc CDC Proto board
product 150a 1010 TiVo Wireless G
product 150a 1011 TiVo Wireless G
product 150a 1012 TiVo Wireless G
---------------------------------------------------
So what is a good base line to clock transfer rate?

[Narf54321]

is this with the backport drivers or the 8.1 drivers?

That's with the standard Tivo 7.3.1-oth-01-2-140 drivers. Haven't updated to 8.1 yet.

Again, I get about 1MB/sec downloads using the Tivo brand wireless dongle off a TCD240xxx unit, thru a Linksys WRT54GS (802.11g) hub. The TCD240's are reputedly better at handling network tasks over the TCD540 nightlight models, so I dunno if it makes a difference to others out there.

A further comparison, 1MB is about on par with the default drivers Tivo gives you with Tivo-to-Go.

Sorry I should have been more clear. In the past I've recorded a "wired" connection (via Linksys USB200M) and stock Tivo drivers at around 1MB/sec. This would've been around system software 4.0.1 or so. Also, some of the TCF folks report similar numbers with Tivo-To-Go. Jamie's drivers provided a much needed speed boost on my TCD240 units to a max of about 2.4MB/sec. I haven't tried system software 8.1 yet to see if Tivo has improved it.

[blickdot]

Not that I ever doubted Jamie's recommendations about using a wire adapter.
But I had a chance to try this out and was wondering how well it would work with the 8.1 update. I was hoping for something more out of the added processing power from the WirelessG.

I haven't had much time lately but I did a quick test transferring a 49.7MB file to and from my Tivo's /var directory (w/ Tivo WirelessG) and my wired PC using FileZilla.
Connected via my D-Link DI-624.

The results are not to impressive:

Upload from Tivo ~480KB/sec.
Download to Tivo ~710KB/sec.

This is with a stock driver setup and MTU-1500 no tweaks.

Now to see if I can find a good buy on a wired adapter.

[ercdvs]

Not to bump an old thread with stupid info, but all of this is still valid on a non direct tv stand alone series 2 ?

Since I don't have a serial port cable, I need to pull the drive to write the backport drivers in .. I have the proper files for my kernel (2.4.20)..

Are there any special tips or lookouts for 8.1a on a tivo series 2 vs a directivo ?

I guess its time to invest in a serial cable... if I could find one.

[uafd]

Experiencing a reboot loop with a Netgear WG111 USB after upgrading to 8.1.

Like a bonehead I overwrote the 7.3 drivers on the old partition which seems to have resolved this problem for other folks.

Does anyone have a copy of the 7.3 files in /lib/modules/ and /platform/lib/modules for a 2.4.20 Series2 SA? I couldn't find them posted anywhere.

[ScanMan]

Does anyone have a copy of the 7.3 files in /lib/modules/ and /platform/lib/modules for a 2.4.20 Series2 SA? I couldn't find them posted anywhere.You don't necessarily need the 7.3, you could always use the backport drivers. (http://www.dealdatabase.com/forum/showthread.php?t=44114)

[nocturno]

Need some help here. Ok I try first the 3.1.5 kernel with 8.1 soft my DWL-122 not recognized. Then I try the 7.2.2 kernel with 8.1 soft same problem. Then I copy the whole /lib/modules and /platform/lib/modules from 7.3 soft to 8.1 soft with the 7.2.2 kernel and the tivo see my wireless device but no signal. Then I use the 7.22 kernel with backport drivers on 8.1 soft and same problem see the wireless device but no signal. I know the device is working fine because as soon as i returned to the original configuration 7.3 soft with 7.2.2 kernel it work fine. I'm out of ideas any clue any help or maybe something I'm missing?
usb.c: USB device 2 (vend/prod 0x2001/0x3700) is not claimed by any active driver.
init_module: prism2_usb.o: 0.1.14-pre6-tivo Loaded
init_module: dev_info is: prism2_usb
hfa384x_drvr_setconfig: Called from within soft interrupt context.
hfa384x_drvr_setconfig: Called from within soft interrupt context.
prism2sta_mlmerequest: Unknown mgmt request message 0x00000143<3>hfa384x_drvr_setconfig: Called from within soft interrupt context.

this is my console log when i get the tivo to see the wireless device but no signal

[fishbate]

8.1 doesn't work with the DWL-122. I had the exact same USB device and tried everything without any luck. Finally broke down and bought a Tivo brand 802.11G USB adapter, and everything works fine. I'm using the 7.2.2 kernel and copied over the 7.3 modules below (as per shutterfriend's instructions)

/lib/modules - CNXTSPDriver.o, isl38sm_usb.o, old-p80211.o, old-prism2_usb.o, p80211.o, p80211autojoin.o, pegasus.o, rtl8150.o, usb-cdc.o, usb-storage.o, usbnet.o and vnetusba.o

/platform/lib/modules - ehci-hcd.o, usb-ohci.o and usbcore.o

From what I read, you could use the backport drivers just as well. I think your best bet for future compatibility is probably to stick with Tivo brand USB devices. You'll also get a nice boost in download speed with this adapter.

[id10t]

Please excuse my ignorance on all things Tivo hacking, and the fact that I am a complete and total noob.
I am using the 7.2.2-oth.K1 kernel on my 24004A unit.
With the backport drivers and an old usb-cdc.o I still cannot get it to recognize my Tivo brand wireless G adapter.
I am running 8.3 software and a wired connection is not a problem.
Any suggestions (other than wishing I had more knowledge)?

[tivo4mevo]

The stock drivers (used for wireless devices) changed between 7.2x and 8.x. Thus, the 7.2.2-oth-K1 kernel can't properly work with the 8.x network drivers. To get a wireless adapter to work, you might try replacing your 7.x kernel with a custom 8.x kernel. Jamie posted a suitable one in the Files Forum (http://dealdatabase.com/forum/showthread.php?t=54047).

[id10t]

I did actually place that custom 8.x kernel since my post.
I replaced my pegasus.o and usbnet.o with the ones in usbobj2.4.27-20070328.tar.bz2 - 2.4.20-8 as well as using the backport ehci-hcd.o, usb-ohci.o and usbcore.o. Using my usb-cdc.o that was there when I upgraded my hard drive this past Wednesday.
My Tivo is still not recognizing the adapter.

[tivo4mevo]

I'm confused as to whether the "that was there when I upgraded my hard drive" is a 8.x version of usb-cdc.o or a 7.x version, but I would suggest reverting to all stock drivers. You can thereby ensure that the tivo-G adapter works and then replace the drivers one by one.

Did you see any performance boost when using the backported drivers with Tivo-G adapater? I didn't think that the backported drivers provided any performance boost to wireless adapters?

[id10t]

The software that I was whatever comes stock on 8.3.
I haven't seen any performance at all, since I have yet to have the adapter be recognized by my Tivo with the backports. On the 7.2. kernel it would detect the adapter with the original drivers, but then throw it into the reboot loop once it connected to my network. Never recognized the adapter otherwise.
I now have the custom 8.x kernel on there, with all of the backport drivers, other than my original usb-cdc.o, because that's what I was told to do.

Summary of what I'm currently running:
Tivo: TCD24004A
Software: 8.3
NIC: Tivo brand wireless G
Kernel: Jamie's custom Series 2 8.1
USB Drivers: pegasus & usbnet.o from 2.4.20-8
ehci-hcd, usb-ohci and usbcore.o from 2.4.20
usb-cdc.o from my stock 8.3 running original Tivo drive.

I can get a bash through a wired connection with no problem.
If the stock drivers will not cause a reboot loop in 8.x, then obviously that's the way to go, I will try replacing them shortly.
Let me apologize in advance for being a stupid newbie.

[Narf54321]

Something doesn't add up here, id10t. AFAIK, Jamie's custom kernel doesn't have the Tivo digital signature.

First you say you're using the 7.2.2 kernel, then the 8.1 custom, but the Tivo still boots?

Are you using a PROM-modded TCD240 unit?
Or are you using a monte to boot the custom kernel? (I don't think monte works well with the system 8 software).
Are you sure you're modifying the active boot/root partition(s), or the alternate ones?

[id10t]

It's not PROM modded, AFAIK, it's not something that is required for this unit.
I am using a monte to boot the 8.1 custom kernel.
I was originally running 7.2.2, but changed to the monte due to the adapter not showing up.
I'm sure that I'm modifying the active partition (or as sure as a stupid newbie can be...bootpage told me it's /dev/hda4). Since I just upgraded the hard drive this past Wednesday, and haven't had any software upgrades, I don't think that hda7 even exists right now.

For my monte (which is my latest attempt to get things running) this is what I did, briefly:
put init.tar into my root directory (/), unpacked it (tar -xvf) which made /chainload.
Renamed vmlinux-Series2.px (from Series2.tar.bz2) to just vmlinux.px, put in /chainload along with the files that were unpacked there.
put the pegasus and usbnet.o from 2.4.20-8 in /lib/modules
left the ehci-hcd, usb-ohci and usbcore.o from 2.4.20 in /platform/lib/modules
put my original usb-cdc.o in /lib/modules
ran a cat test.conf to check for ^M, etc...didn't find any
Rebooted Tivo, which still isn't seeing my adapter.

I can establish a bash connection via wired connection, and can use the wired connection to connect to Tivo's service. Wireless still goes unrecognized (for those familiar with the Tivo brand adapter, the left side light lights up, the right side which indicates a communication attempt, does not.) Tivo reports it as no network adapter detected.

[Jamie]

You really need serial console output to debug network problems. If you don't have a serial console cable, you can build one, or buy one from 9thtee.

I don't have a tivo wireless adapter, but when I try to load the 8.3 usb-cdc.o with the backport usbcore, I get:
/lib/modules/usb-cdc.o: /lib/modules/usb-cdc.o: unresolved symbol usb_hub_power_toggleso it appears to me you probably need to use the tivo supplied host modules (usbcore/ehci-hcd/usb-ohci) rather than those from the backport package.

Perhaps eventually I'll look at adding the missing symbols to the backport. In the meantime, stick with ALL stock tivo drivers rather than trying to mix and match between the backport and stock tivo drivers.

[id10t]

Excellent...the stock drivers got it to recognize the adapter and not send it into a reboot loop.
For some reason, now I can't seem to get it to connect to my network...here's a cut and paste of a message I just posted at tivo.com:


Tivo: TCD24004A
Adapter: Tivo brand Wireless G Adapter
Router: Linksys WRT54G w/ DD-WRT

"I am attempting to connect my Tivo brand wireless G adapter to my network.
It finds my SSID just fine, the right side light is solid...the SSID shows up under Settings > Network and generally has 72-90% or so signal strength, but for some reason it is not receiving a DHCP address.
My router's DHCP Server is enabled, my WPA2 PreShared Key is entered correctly into the Tivo...I tried disabling it, no connection...I disabled my MAC Filter (which has the adapter's MAC correctly entered to allow), no luck...tried disabling my SPI Firewall, no luck. Just a world full of N24 errors.
What do I need to do here? Apparently it's some advanced form of rocket science."

Anybody here got any thoughts? I remember problems getting it to connect when I first set it up as well, but can't remember what I did.

[Jamie]

Anybody here got any thoughts? I remember problems getting it to connect when I first set it up as well, but can't remember what I did.Does it work if you use a fixed IP address instead of dhcp? That would give you a clue if it is just a dhcp problem, or something else. There are some issues with dhcp on some software versions, depending on what kernel you use. I don't think that should be an issue here, and you did say it all worked with a wired connection, though perhaps you didn't test that with your current kernel/driver config.

It's probably not reasonable to ask on tivo.com unless you are using stock hardware and software. If it turns out to be your hacking problem, you've wasted their time, and they may choose to repay you by blacklisting your TSN.

[id10t]

Sweet, setting the fixed IP worked, probably should have figured that one out on my own.
Thanks a lot for everybody's help, each one of you can consider yourself the man.
The only problem I've noticed are that there has been 2 random reboots...once while I was trying to figure out the network settings, I left the Tivo sitting for a few minutes, came back, pushed a button on the remote and it rebooted. Once at the end of the first recorded show I watched, it rebooted (there was still about 30 seconds of show left).
I'm sure that nobody will be able to randomly guess what caused that, since I don't have the serial output.
Thanks again, everybody...I'm happy to have things mostly running well.

[dcrayman]

Anyone having any luck running Linksys WUSB11 v2.6 with sw 8.3 and a killed 7.2.2-oth-k1.px? Do I have to monte to get it to work? So far I have had no luck with the backport drivers and it works well with a standard sub with no hacks.

Thanks for any help, ray.

[jt1134]

Anyone having any luck running Linksys WUSB11 v2.6 with sw 8.3 and a killed 7.2.2-oth-k1.px? Do I have to monte to get it to work? So far I have had no luck with the backport drivers and it works well with a standard sub with no hacks.

Thanks for any help, ray.

I've used it with 8.3 using monte to an 8.1 kernel and the stock 8.3 drivers, or by using an older version of the driver (7.2.2 I believe).

[ogre73]

I would very much like to try what shutterfriend did in post #46 & #47, but I can not find the 7.3 drivers anywhere! I have searched everywhere I can think of, but can not find them. Would someone please tell me where to find them, or send them to me? Thanks.
Jim

[shutterfriend]

I would very much like to try what shutterfriend did in post #46 & #47, but I can not find the 7.3 drivers anywhere! I have searched everywhere I can think of, but can not find them. Would someone please tell me where to find them, or send them to me? Thanks.
Jim

Jim,

Here are the usb drivers from 7.3.1.

[koolkat1973]

Jim,

Here are the usb drivers from 7.3.1.

What wireless adapter were you using? I have the DWL-122 and its no longer working after upgrading to software version 9.1. Please help. Thanks.

Kiet

[jt1134]

What combination of kernel/drivers are you using? I'd bet stock 9.1 drivers and monte'ing to a 9.1 kernel would work.