I must be retarded. What am I doing wrong?

[BuckwheatTheCat]

I have a Stand-Alone Series 2 TCD240040. It was never hacked and it's updated to software version 7.2.0-oth-01-2-140. Here's what I've done so far using the enhanced PTVupgrade LBA48 CD with MFStools (I'm a sucker for supporting sponsors):

Backup the original 40GB drive with no recordings on it:
The original TiVo drive is mounted as HDC:
mfsbackup -f 9999 -6so /mnt/dos/tivo.bak /dev/hdc

Remove original drive and place in static free bag for storage. Install new 40GB drive as HDC (a permanent larger drive will be used later once I get the steps down to perfection):
mfsrestore -s 127 -bzpi /mnt/dos/tivo.bak /dev/hdc

mkdir /mnt4
mkdir /mnt7
mkdir /mnt9
mkdir /ptvcd

mount -t ext2 /dev/hdc4 /mnt4 (doesnt exist)
mount -t ext2 /dev/hdc7 /mnt7
mount -t ext2 /dev/hdc9 /mnt9
mount /dev/hdb /ptvcd

I then converted and copied the 3.1.5 killhdinitrd modified kernel on the PTVupgrade CD to the 3 & 6 partitions (yeah I know it was lazy to do this but it's 12:45 AM and I'm getting the DealDatabase version of highway hypnosis from all the reading I've done).
dd if=/mnt7/packages/vmlinux.px of=/dev/hdc3
dd if=/mnt7/packages/vmlinux.px of=/dev/hdc6

I updated the boot parameters:
bootpage -P "root=/dev/hda7 dsscon=true console=2,115200" -C /dev/hdc

I modified tivoapp to disable scrambling. (Can someone please doublecheck that my math was correct with the offset digits I used for the 7.2.0-oth-01-2-140 software):
cd /mnt/tvbin
cp tivoapp tivoapp.old
echo -ne "\x3C\x02\x00\x00" | dd conv=notrunc of=tivoapp bs=1 seek=5805024
chmod +x tivoapp

Created rc.sysinit.author file:
cd /mnt7/etc/rc.d
joe re.sysinit.author

I then typed in the following:
#load usb network drivers for a Linksys USB100TX
insmod /lib/modules/usbcore.o
insmod /lib/modules/usb-ohci.o
sleep 5
insmod /lib/modules/rtl8150.o
sleep 5
#static IP settings
ifconfig eth0 192.168.13.23 netmask 255.255.255.0
route add default gw 192.168.13.254 netmask 0.0.0.0 metric 1
#!/bin/bash
tnlited 23 /bin/bash
#serial bash
/bin/bash < /dev/ttyS2 >& /dev/ttyS2 &

I hit CTRL + K and then X to close. I then typed chmod +x rc.sysinit.author to make it executable.

I umounted everything and shut down the PC. After installing the new drive, the TiVo boots up just fine. However, no telnet or bash via the network or a serial cable (I used the serial cable that came with the TiVo plus a null modem adapter). I rebooted the TiVo a few times, removed the hard drive and hooked it back up to a PC. the rc.sysinit.author file is still there, so I'm guessing the 3.1.5 killhdinitrd modified kernel is still there. I feel like I am missing something very obvious. Any and all help and feedback is appreciated. Thanks!!

[cheer]

First, I don't think you should be insmod'ing the USB drivers -- Tivo should load them automagically.

Second, check your rc.sysinit file and make sure it has [ ! -f /etc/rc.d/rc.sysinit.author ] || /etc/rc.d/rc.sysinit.author in it somewhere.

Third, you probably don't need to set the IP address in rc.sysinit.author either -- you should be able to do it from the Tivo interface.

I realize you don't get bash via serial, but what about console output? You should get that -- if you do, perhaps add a couple of "echo" commands to your rc.sysinit.author to make sure it is being executed.

[PlainBill]

Strange things are happening here, I'm not sure just what they are. IIRC, you cannot use the 3.1.5 kernel with 7.2 without making other modifications. The usual result is rolling reboots. Jamie referenced this (http://www.dealdatabase.com/forum/sh...les#post204669) post recently.

On the other hand, the fact that rc.sysinit.author is not deleted would indicate you DID replace the kernel.

Do NOT insmod the drivers nor set the ip address in rc.sysinit.author - that's 3.1.1 stuff. You ARE missing an important first line from it: #!/bin/bash - this tells the TiVo to use the bash interpretor to execute the file.

When troubleshooting these problems it is helpful to add echos (echo beginning rc.sysinit.author) to the file so you can see what is happening.

I can't say this often enough: ALWAYS run bootpage -p first! Find out what partitions are active. It is true that if only one root partition mounts, that is probably the active one.

Lastly, backing up using -f 9999 on a series 2 system will probably result in missing backgrounds for the menus. Hinsdale recommends -f 19999; I've found -l 20 works better.

PlainBill

[Jamie]

Strange things are happening here, I'm not sure just what they are. IIRC, you cannot use the 3.1.5 kernel with 7.2 without making other modifications. The 3.1.5 kernel works fine until you try to disable the netfilter/iptables firewall the "old" way. Then you get the rolling reboots. Since the OP didn't disable the firewall at all yet, he's ok, for now.

This (http://www.dealdatabase.com/forum/showthread.php?p=204669#post204669) post describes the right way to disable the firewall with 7.x. Until you do this, you won't be able to get in with telnet and ftp.

[PlainBill]

The 3.1.5 kernel works fine until you try to disable the netfilter/iptables firewall the "old" way. Then you get the rolling reboots. Since the OP didn't disable the firewall at all yet, he's ok, for now.

This (http://www.dealdatabase.com/forum/showthread.php?p=204669#post204669) post describes the right way to disable the firewall with 7.x. Until you do this, you won't be able to get in with telnet and ftp.
Thanks for clearing that up, Jamie.

PlainBill

[BuckwheatTheCat]

Thanks guys. I'm going to get the original hard drive out of the anti-static bag and run another backup with PlainBill's suggestion of -l 20. Just an FYI: I did run the bootpage -p first and forgot to write that I did. It said partition 7 was the active one.

P.S. Bill, my wife is disappointed your avatar no longer has baby food on it's chin :-)

[PlainBill]

P.S. Bill, my wife is disappointed your avatar no longer has baby food on it's chin :-)

Yes, that was cute. But Vikings don't have baby food on their chin.

PlainBill

[cheer]

Yes, that was cute. But Vikings don't have baby food on their chin.
Though if Culpepper takes many more hits...seriously, someone needs to start blocking! I mean, I hate the Vikings an all, but as a humanitarian...

[PlainBill]

Though if Culpepper takes many more hits...seriously, someone needs to start blocking! I mean, I hate the Vikings an all, but as a humanitarian...
You missed last Sunday's game. They have started blocking.

PlainBill

[Igorian]

I've got the TCD24004A with 7.2. I'd loaded what I thought was the already 'killed' kernel 3.5.1, but it wouldn't go past the "Welcome Powering up" screen. I'd noticed another thread saying that he had to run 'killhdinitrd' on what he thought too was already 'killed' due to the same issue. I did the same and got it to boot just fine. But the network device doesn't work any longer. Something about the 3.5.1 kernel broke the networking.

The TCD24004A has built in USB drivers and was previously already working on the network, now it's not. I've been around and around in circles trying to find a more cut and dry process. Everything I found has been bits and pieces. I feel I can get up and going, save one step. How to regain the regular network now that I've loaded a different kernel? Thanks much in advance.

Edited SA version. When I started my hacks, it was 7.1.b, now it's 7.2. Good thing it wasn't too much different.

[Jamie]

How to regain the regular network now that I've loaded a different kernel? Thanks much in advance.Use a fixed IP address instead of dhcp. dhcp doesn't work on 7.x with the 3.1.5 kernel unless you have the af_packet.o module loaded. Since af_packet.o doesn't come with 7.x, if you want to use dhcp, you'll have to find a 2.4.20 af_packet.o somewhere else, e.g. from 6.2. It's easier to just use a fixed ip.

[Igorian]

Use a fixed IP address instead of dhcp. dhcp doesn't work on 7.x with the 3.1.5 kernel unless you have the af_packet.o module loaded. Since af_packet.o doesn't come with 7.x, if you want to use dhcp, you'll have to find a 2.4.20 af_packet.o somewhere else, e.g. from 6.2. It's easier to just use a fixed ip.

In my own troubleshooting I noticed that too. Just by chance. If I'd have check the DDB sooner I would have gotten there quicker. Your tip came before I got it on my own. I had a ping going contineously until I saw it working. Great that did it.

So my whole point was to at least get telnet. I guess I'm back to the drawing board. Thanks for that last tip. That explains it.

Any tip for getting telnet? I know I'm fishing. Thanks again. (Edit - just saw the link about disabling the firewall. Checking ;) )

I forgot to mention, the next thing I did towards telnet is make a rc.sysinit.author file as below. Found on the DSmooths site.

#!/bin/bash

#load usb and ethernet modules
insmod /lib/modules/usbcore.o
insmod /lib/modules/ehci-hcd.o
insmod /lib/modules/ax8817x.o
sleep 15

#configure Linksys USB200M
ifconfig eth0 192.168.0.10 broadcast 192.168.0.255 netmask 255.255.255.0
sleep 60

#start telnetd
tnlited 23 /bin/bash -login &

#start ftpd
/var/hack/tivoftpd.mips

[PlainBill]

I forgot to mention, the next thing I did towards telnet is make a rc.sysinit.author file as below. Found on the DSmooths site.

#!/bin/bash

#load usb and ethernet modules
insmod /lib/modules/usbcore.o
insmod /lib/modules/ehci-hcd.o
insmod /lib/modules/ax8817x.o
sleep 15

#configure Linksys USB200M
ifconfig eth0 192.168.0.10 broadcast 192.168.0.255 netmask 255.255.255.0
sleep 60

#start telnetd
tnlited 23 /bin/bash -login &

#start ftpd
/var/hack/tivoftpd.mips
DON'T insmod the modules when using 7.x!!! The TiVo loads them for you.

Don't put your hacks in /var unless you want to join the dozens of people asking "Why did my hacks in /var disappear?"

PlainBill

[Igorian]

DON'T insmod the modules when using 7.x!!! The TiVo loads them for you.

Don't put your hacks in /var unless you want to join the dozens of people asking "Why did my hacks in /var disappear?"

PlainBill

PlainBill, I've read many of your answers to others. As always you are a 'stand up' kind of guy. I realized that after finding out that I need to use a static IP instead of DHCP (after killhdinitrd), that I could take out those lines. Since they weren't doing any help anyway. Regarding the /var/hack, good one. Makes perfect sense.

BTW, dumying the iptables is what made my telnet start working. Didn't do anything else after that. :)

[PlainBill]

Thanks. I had a similar problem way back in the dark ages with 4.0.1b on an HDVR2. I wasn't getting anywhere with the network until some kind soul mentioned 'netfilter-enable'.

PlainBill

[BuckwheatTheCat]

ok. so here's what I've done so far with Cheer's, Jamie's, and PlainBill's suggestions:

Backup the original 40GB drive with no recordings on it:
The original TiVo drive is mounted as HDC:
mfsbackup -l 20 -6so /mnt/dos/tivo.bak /dev/hdc

Remove original drive and place in static free bag for storage. Install new 40GB drive as HDC (a permanent larger drive will be used later once I get the steps down to perfection):
mfsrestore -s 127 -bzpi /mnt/dos/tivo.bak /dev/hdc

mkdir /mnt4
mkdir /mnt7
mkdir /mnt9
mkdir /ptvcd

mount -t ext2 /dev/hdc4 /mnt4 (doesnt exist)
mount -t ext2 /dev/hdc7 /mnt7
mount -t ext2 /dev/hdc9 /mnt9
mount /dev/hdb /ptvcd

I then converted and copied the 3.1.5 killhdinitrd modified kernel on the PTVupgrade CD to the 3 & 6 partitions:
dd if=/mnt7/packages/vmlinux.px of=/dev/hdc3
dd if=/mnt7/packages/vmlinux.px of=/dev/hdc6

bootpage -P /dev/hdc showed partition 7 was the active one (4 doesnt exist)

I updated the boot parameters:
bootpage -P "root=/dev/hda7 dsscon=true console=2,115200" -C /dev/hdc

I then replaced the IP tables:
cd /mnt7/sbin (corrected)
mv iptables iptables.old
echo -e '#!/bin/bash\nexit 0' > iptables
chmod 755 iptables

I created the rc.sysinit.author file:
cd /mnt7/etc/rc.d
joe re.sysinit.author

I then typed the following in the rc.sysinit.author file:
#!/bin/bash
tnlited 23 /bin/bash
#serial bash
/bin/bash < /dev/ttyS2 >& /dev/ttyS2 &

export PATH=$PATH:/hack

[ ! -f /etc/rc.d/rc.sysinit.author ] || /etc/rc.d/rc.sysinit.author

echo Turning off firewall ... >& /dev/console
[ -x /etc/netfilter-disable ] && /etc/netfilter-disable


I hit CTRL + K and then X to close. I then typed chmod +x rc.sysinit.author to make it executable.

I umounted everything and shut down the PC. After installing the new drive, the TiVo goes into a rolling infinite reboot loop. I probably missed something in the thread Jamie suggested

[eastwind]

I then replaced the IP tables:
cd /sbin
mv iptables iptables.old
echo -e '#!/bin/bash\nexit 0' > iptables
chmod 755 iptables
Did you really do this just like this? I think you might need to cd to /mnt7/sbin if you want to work on the TiVo's files.
I created the rc.sysinit.author file:
cd /mnt7/etc/rc.d
joe re.sysinit.author

I then typed the following in the rc.sysinit.author file:
#!/bin/bash
tnlited 23 /bin/bash
#serial bash
/bin/bash < /dev/ttyS2 >& /dev/ttyS2 &

export PATH=$PATH:/hack

[ ! -f /etc/rc.d/rc.sysinit.author ] || /etc/rc.d/rc.sysinit.author

echo Turning off firewall ... >& /dev/console
[ -x /etc/netfilter-disable ] && /etc/netfilter-disable


And this will keep calling /etc/rc.d/rc.sysinit.author over and over recursively (at least it looks like it will). And never touch the last lines. I don't know if either of these things would cause a reboot loop, however.

ew

[BuckwheatTheCat]

Did you really do this just like this? I think you might need to cd to /mnt7/sbin if you want to work on the TiVo's files.
ew

NO, ew. That was a just typo on my part. I really did go into /mnt7/sbin to replace the IP tables. I have to stop typing after midnight :-)

[sirsycho]

Hey guys...

I am having a similar problem as buck...

I'm running a 3.1.5 "rev e" and I used the PTV S2 kernel. It boots fine, but my USB200M nor my FA120 ever get any lights at all. So it looks like my

insmod /lib/modules/usbcore.o isn't working...

I pulled the drive back out and mounted it on my pc... looked at:
/mnt/hdc9/log/kernel
and see all of my insmods are telling me that the modules aren't compatible with my kernel (modules = 2.4.18... kernel = 2.4.20). I downloaded the modules from the tivoutils.sourceforge.net and still no luck.

Do I have to compile my own modules, or are there some already tested and confirmed out there (or am I just doing something wrong)?

Thanks for the help.
:confused:

[PlainBill]

Hey guys...

I am having a similar problem as buck...

I'm running a 3.1.5 "rev e" and I used the PTV S2 kernel. It boots fine, but my USB200M nor my FA120 ever get any lights at all. So it looks like my

insmod /lib/modules/usbcore.o isn't working...

I pulled the drive back out and mounted it on my pc... looked at:
/mnt/hdc9/log/kernel
and see all of my insmods are telling me that the modules aren't compatible with my kernel (modules = 2.4.18... kernel = 2.4.20). I downloaded the modules from the tivoutils.sourceforge.net and still no luck.

Do I have to compile my own modules, or are there some already tested and confirmed out there (or am I just doing something wrong)?

Thanks for the help.
:confused:

You need 2.4.20 modules. Check this (http://www.dealdatabase.com/forum/showthread.php?t=44114) thread for Jamie's backported drivers. IIRC, the modules included on the HR10-250 support the FA-120.

PlainBill

[sirsycho]

Thanks a lot... I found that thread after I posted... Now I can feel like an ass.

:)

thanks for the quick response though, you guys are most helpful.

Cheers!!

[BuckwheatTheCat]

Ok. So, I now have a partial success thanks to your help. I found that if I performed all the steps I listed above but eliminated the [ ! -f /etc/rc.d/rc.sysinit.author ] || /etc/rc.d/rc.sysinit.author line from rc.sysinit.author, the unit no longer goes into an infinite loop.

I am then able to get a bash!! WOOOOOHOOOOOO!!!

Now, here's where I am confused and it's probably very easy - something stupid I overlooked. When I try to change directories and poke around and see what is there, there's nothing. I know I cant use the "ls" command yet, but I tried to change directories into folders I know should exist, but the reply was that those folders do not exist. Hmmmmmm....So, I decided to create a directory just for the hell of it and see where it's located. I created the directory "Buckwheat", shut down my tivo, removed the hard drive, connected the hard drive back to my PC and powered up. On partition 7 everything looked normal. All the folders containing my hack software are where I left them, etc, but no Buckwheat folder. I then switch to partition 9. Low and behold in a tmp directory is my Buckwheat folder. Can someone please explain to me what happened, why that is, what I did, how can I remedy it, etc so I can understand more? Thanks!!!

[eastwind]

Ok. So, I now have a partial success thanks to your help. I found that if I performed all the steps I listed above but eliminated the [ ! -f /etc/rc.d/rc.sysinit.author ] || /etc/rc.d/rc.sysinit.author line from rc.sysinit.author, the unit no longer goes into an infinite loop.

I am then able to get a bash!! WOOOOOHOOOOOO!!!

Now, here's where I am confused and it's probably very easy - something stupid I overlooked. When I try to change directories and poke around and see what is there, there's nothing. I know I cant use the "ls" command yet, but I tried to change directories into folders I know should exist, but the reply was that those folders do not exist. Hmmmmmm....So, I decided to create a directory just for the hell of it and see where it's located. I created the directory "Buckwheat", shut down my tivo, removed the hard drive, connected the hard drive back to my PC and powered up. On partition 7 everything looked normal. All the folders containing my hack software are where I left them, etc, but no Buckwheat folder. I then switch to partition 9. Low and behold in a tmp directory is my Buckwheat folder. Can someone please explain to me what happened, why that is, what I did, how can I remedy it, etc so I can understand more? Thanks!!!
Your telnet session's "home" is /var/tmp--that's where you start when you telnet/bash into the tivo.

ew