weird IP problems after killhdinitrd upgrade

[gbonawitz]

I just did the killhdinitrd upgrade, which, in a nutshell for me, was..
1) from bootpage, found that parition 4 was currently active.
2) downloaded virgin 4.0.1.a kernel, ran killhdinitrd on it
3) dd'd killhdinitrd kernel to parition 3
4) updated rc.sysinit.author on partition 4 in /etc/rc.d (regarding ip configuration, set it to use IP address 192.168.1.169) and also start tnlited and tivoftpd
5) chmod'd the rc.sysinit.author file.
6) copied over and chmod'd tivoftpd

Now, whenever TiVo start, my router and TiVo both say that it's using IP 192.168.1.100, but I cannot ping it. I can ping, however, 192.168.1.169 (although it does not show up in my DHCP tables).

Any idea what's going on or what I could investigate? BTW - I cannot get telnet nor FTP to work.

I should add some info about how my TiVo boots. From a cold boot, it will automatically reboot a little bit after reaching "Just a few minutes more", the next time go to GSOD, and the third time reboot perfectly (and work). If I do a soft reboot, it works perfecty all the time (no auto reboot or GSOD). After I orignially did the MFStool upgrade, this behavior has always happened but I don't lose any recordings or any other settings - it works fine.

[PlainBill]

Was the system previously hacked, and if so, how?

Also, if 4.x software detects an ethernet adapter, it enables DHCP and gets an IP address that way. The ip address can be set manually from the phone and network setup menu.

PlainBill

[gbonawitz]

Yes, it was hacked before (should've had that fact in the original post). I did the MFSTools upgrade to add a 2nd drive. It was since that upgrade that I started having the weird boot up, but it was working fine so I never looked into resolving it.

[PlainBill]

Yes, it was hacked before (should've had that fact in the original post). I did the MFSTools upgrade to add a 2nd drive. It was since that upgrade that I started having the weird boot up, but it was working fine so I never looked into resolving it.

And I believe I know the answer to this, but HOW was it hacked?

PlainBill

[gbonawitz]

Let's see...that was a while back...I believe I used MFSTools to create a backup from my original 40 GB drive. Then, I restored that image to a new 120 GB drive. Lastly, I used MFS to add the original 40 GB drive as a second drive. I'm sorry if that is not detailed enough, but that's all I remember. (It was over a year ago).

Yes, I probably should've asked then about the problem! :rolleyes:

I used version 2.0 of MFS tools

[PlainBill]

Let's see...that was a while back...I believe I used MFSTools to create a backup from my original 40 GB drive. Then, I restored that image to a new 120 GB drive. Lastly, I used MFS to add the original 40 GB drive as a second drive. I'm sorry if that is not detailed enough, but that's all I remember. (It was over a year ago).

Yes, I probably should've asked then about the problem! :rolleyes:

I used version 2.0 of MFS tools

Rats!!! My idea seems to be wrong. OK, the best way to start to figure out what is happening is to build, borrow, or buy a serial cable, enable the console in boot parameters (dsscon=true console=2,115200), capture the output with a terminal program as the system boots, and attach it to this thread.

PlainBill

[gbonawitz]

OK...hopefully I can do that within the next day or so.

[gbonawitz]

PlainBill-

OK - I made a serial cable and have confirmed with multimeters the following pin out...
stereo pin DB9
tip-----------Pin 2
Ring ---------Pin 3
sleeve--------Pin 5

I am plugging this DB9 directly into my machine. I am assume that "ring" means the area b/t the 2 black circles on the stereo pin shaft and "sleeve" is the base of the shaft (i.e. opposite of the tip).

1) I booted up from the PTV disk, with the TiVo drive on secondary master.
2) I ran bootpage -p /dev/hdc, which yeilded "root=/dev/hda4"
3) I ran bootpage -P "root=dev/hda4 dsscon=true console=2,115200 upgradesoftware=false" /dev/hdc.
4) I again ran bootpage -p /dev/hdc, which still yeilds root=/dev/hda4. Shouldn't it return the other parameters too, e.g. dsscon and console?

I have thus far been unable to get the output from TiVo when booting up and the cables connected. I have HyperTerminal running with 9600,8,N,1, and no flow control. :confused:

[gbonawitz]

OK...think I figured it out...I added -C to the bootpage -P command, and now see the console and dsscon regurgitated to meet with bootpage -p. Let me go try this sucker out.

[PlainBill]

PlainBill-

OK - I made a serial cable and have confirmed with multimeters the following pin out...
stereo pin DB9
tip-----------Pin 2
Ring ---------Pin 3
sleeve--------Pin 5

I am plugging this DB9 directly into my machine. I am assume that "ring" means the area b/t the 2 black circles on the stereo pin shaft and "sleeve" is the base of the shaft (i.e. opposite of the tip).

1) I booted up from the PTV disk, with the TiVo drive on secondary master.
2) I ran bootpage -p /dev/hdc, which yeilded "root=/dev/hda4"
3) I ran bootpage -P "root=dev/hda4 dsscon=true console=2,115200 upgradesoftware=false" /dev/hdc.

Try:
bootpage -P "root=dev/hda4 dsscon=true console=2,115200 upgradesoftware=false" -C /dev/hdc

4) I again ran bootpage -p /dev/hdc, which still yeilds root=/dev/hda4. Shouldn't it return the other parameters too, e.g. dsscon and console?

Yes, it should. See above.

I have thus far been unable to get the output from TiVo when booting up and the cables connected. I have HyperTerminal running with 9600,8,N,1, and no flow control. :confused:

Try 115200,8,N,1, no flow control.

PlainBill

[gbonawitz]

OK, with that change I'm almost there. The password is supposed to be "factory", correct? It's not working.

One step forward, one step back!!! :o

[PlainBill]

OK, with that change I'm almost there. The password is supposed to be "factory", correct? It's not working.

One step forward, one step back!!! :o

The password is set to an arbitrary value. You must reset it - but no big deal. Simply do not hit any key until AFTER you start getting output.

PlainBill

[gbonawitz]

OK...here we go.
"TiVo1 - formatted" shows the output during the first boot after cold restart -> the system will automatically reboot after reach "Almost there"

"TiVo2 - formatted" shows the next boot, which goes to GSOD.

"TiVo3 - formatted" shows the last boot, which occurs without any problem.

Again, if I were to soft boot now, everything would boot up fine. Some "fix" is getting held in powered memory.

[PlainBill]

OK...here we go.
"TiVo1 - formatted" shows the output during the first boot after cold restart -> the system will automatically reboot after reach "Almost there"

"TiVo2 - formatted" shows the next boot, which goes to GSOD.

"TiVo3 - formatted" shows the last boot, which occurs without any problem.

Again, if I were to soft boot now, everything would boot up fine. Some "fix" is getting held in powered memory.


Strange. I have no idea what is happening.

PlainBill

[RavenStL]

Does your DHCP start at .100 ? Maybe Tivo initially sets up by DHCP, gets one, then attempts to use the fixed one? The DHCP server / switch may be confused and require a Reboot to pick up the manual address and ensure the routing tables are accurate. Just a thought.

Once booted the third time, can you go in and set it manually using your remote?

[gbonawitz]

Let me bounce one thought off of you...i

I was comparing the 1st and 2nd boot logs, and noticed that the first boot log does not show my second disk. Perhaps this is because it's looking for it before the 2nd drive starts (I have one of those PTV things inline b/t the 2nd drive and power supply - delays startup so the power supply doesn't get shot).

The second boot shows it's seeing the 2nd drive - maybe the disk has enough momentum on a warm reboot plus the lower voltage level the PTV thing is allowing through so that it can be seen. However, it needs to do some work on the zone buddymaps. Do the buddy maps tie the 2nd drive to the first?

Maybe the first boot (where is doesn't see the drive at all) resets something regarding the link to the second drive (buddymaps), but then the second boot sees the drive but the link has been messed up by the work done during the first boot???....the third boot would have the corrected buddymaps, and like the 2nd boot not having the 2nd drive start from zero rpms, hence it can see it when looking for it?

I don't know...this is just a SWAG...hoping maybe this idea may turn on a lightbulb with someone who knows more details.

[gbonawitz]

RavenSTL - Yea, the address range starts at 192.168.1.100. However, I've been having this reboot problem well before I started entering in a IP manally in rc.sysinit.author with the hacks I'm trying to do now.

I can go in after the 3rd boot and change it to any IP address I want, but same results - I cannot telnet or FTP to it.

QUESTION: should I see reference to rc.sysinit.author in the data showing up in HyperTerminal on the 3rd reboot...I don't see anything...It is my understanding that rc.sysinit automatically calls rc.sysinit.author - is this correct, or do I need to add a line to rc.sysinit to do this? Actually...that's probably not right ... I can ping whatever address I set in rc.sysinit.author, so it must be being looked at.

[gbonawitz]

Wait a second...I think I have the SmartStart hooked up to the wrong drive :o Let me switch and try again.

[gbonawitz]

Wait a second...I think I have the SmartStart hooked up to the wrong drive :o Let me switch and try again.

Duh on me!!! OK, so now I no longer have the multiple boot problem...go figure -reading the directions correctly does make a difference.

Ok...if people are still with me....my original/recent problem...I cannot get the killhdinitrd hack to work after killhdinitrd'ing the kernal on the active image partition and editing rc.sysinit.author file. Should I be seeing anything in this log file that I'm not?

[NutKase]

It appears the you haven't disabled netfilter by editing rc.sysinit or renaming /etc/netfilter-enable to something else.

Does your telnet (via ethernet) and ftp work?

Also, with 4.x, delete any ip, ifconfig, or insmod wireless driver lines from your rc.sysinit.author and set them up via the tivo setup menus.

You'll only need insmod lines if you choose to use an adapter not supported by your version of 4.x tivo software.

In that case, you can always update the drivers themselves in /lib/modules and still let the tivo deal with it like I do though.


NutKase

[gbonawitz]

I went in and renamed netfilter-enable to netfiter-enable.old. I also edited the rc.sysinit.author file as you suggested. Still not able to telnet or ftp in. I can ftp and telnet via ethernet to Internet sites, so it is not a filtering issue on my network. I have echo'd comments at the begnning and end of the sections of rc.sysinit.author where I [try to] enable telnet and ftp, and I can see via the serial console that it gets to and through those sections (although there is no direct confirmation that telnet and ftp start). Ho hum....

Stupid question: should I be removing the dsscon=true from the boot parameters - with that on does it direct all output to the serial connection?

[NutKase]

Stupid question: should I be removing the dsscon=true from the boot parameters - with that on does it direct all output to the serial connection?

Naw, leave the bootpage as you've got it: dsscontrue is fine.

I've got a question. I sse you used a 4.0.1a killhdinitrd compatible kernel. What software version does you tivo say in the tivo information screen?


NutKase

[gbonawitz]

It's showing 4.0.1b..... Hmm...shouldn't it be showing 4.0.1a.....? (I'd typed in the exact version before bring the drive and my laptop back upstairs to my desktop, and I lost the original reply I'd started with that exact version nunber. However, I remember that it was a "b" version)

Here's exactly what I did to move the kernal over
1) boot from PTVcd
2) ran bootpage -p /dev/hdc -> root=/dev/hda4 dsscon=true console=2,115200 upgradesoftware=false
3) ran zcat /cdrom/s2_kernels/4.0.1a/vmlinux.px.gz | dd of=/dev/hdc3 -> 0+9 records in 1+1 records out (this looked odd, so I ran it again and got 1+1 records in, 1+1 records out)
4) ran bootpage -b /dec/hdc -> Boot Partition: 4

I'm going to give this one more shot tonight, and then hold off for a day ... getting rammy move the HDD around so much over the last few days and I don't want to break anything. :mad:

[gbonawitz]

hey, I got in via Telnet and FTP!!! I'd noticed that I'd use serial port 3 on the command to enable bash in rc.sysinit (copied from another post), but I went and changed it to serial port 2, and now I can get in (not sure why'd that affect getting in via Telnet via ethernet....)

I also now get the bash prompt via serial which I wasn't before. I also re-dd'd the PTVkernal over, but am still showing version 4.0.1b-02-2-240. I guess it's supposed to show that?...

Anyway, thanks to everyone for helping me through this.