TiVo Community Forums Archives - TiVo is unhacking my TiVoNet hacks!

TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.

Pages:1

TiVo is unhacking my TiVoNet hacks!
(Click here to view the original thread with full colors/images)

Posted by: uFu

Just got my TiVoNet today from Mark at 9thtee. The install into my 2.5 Sony SA went fine, but it failed the ping test (carrier lights are fine on the board and hub).

I put the A drive back in my PC, and the hacks were gone from partition 4. They were still present on partition 7. (The log files indicate that it booted off 4).

In another thread on this board, Nick Kelsey/jafa was helping someone with the same problem while trying to install a *TurboNet* board. He suggested running "kill_initrd/killinitrd" on partitions 3 & 6 (not 4 & 7).

Do I need to do this? Is there any risk (other than usual ones associated with TiVo hacking)?

Thanks,
John

Posted by: stormsweeper

Yes. The kill_initrd method is actually safer than the old way, which if you mistyped could be very, very bad. What you're seeing is file protection, and the same issue will crop up with any modification.

Since you have a standalone, you don't need to flash the PROM, just use the kill_initrd utility.

Posted by: uFu

Stormsweeper,

Thanks for the quick reply. One further question: Is it correct to run this on partitions 3 & 6 (I don't know what those are), and not the root partitions on 4 & 7?

John

Posted by: stormsweeper

Yes, because you're modifying the kernel, which is on the partition before its respective root partition. In your case, you only need to run it on 3, but it won't hurt anything to do it on 6.

Posted by: rbiro

I got the TivoNet board a while ago and plugged it into my Sony Tivo but never got around to installing the TivoNet 2.5 hacks. I done both hard-drives, but never bothered to install the TivoNet software.

Now that 3.0 is here, I though I should be able to enable the ,#401 code and go.

I can see from my DHCP router that when the Tivo boots up, the net card requests an IP: 192.168.1.100. And the nice pretty light onth e front of my router is lit.

But if I ping my Tivo, I get no reply. After setting the dialing prefix, if fails on the "test call".
Preparing succeeds. Dialing succeeds. Connecting takes 3-4 minutes and then fails.

Am I missing anything? Didn't the 3.0 upgrade wipe out everything from 2.5?

Posted by: stormsweeper

try rebooting your Tivo. and, yes, your 3.0 install has nothing from your 2.5 install. Tivo uses 2 sets of partitions, and only 1 is ever active. When it "upgrades" it's really installing the new software onto the inactive partitions.

Posted by: rbiro

I tried rebooting with no change.
I also made sure the backdoor mode was enabled.

Posted by: xmajic

I too had Tivonet working with 2.5. After 3.0, the calls failed. I have never been able to get the serial cable hack working, so I cannot get to the logs at this point. One thing I noticed is that backdoors are not enabled, which is telling me that the 3.0 upgrade is not seeing my Tivonet board or NIC for some reason. Anyone else have this problem and a fix for it?

Posted by: stormsweeper

3.0 doesn't enable backdoors with a TivoNet board present, unlike 2.0/2.5 systems.

Posted by: rbiro

Has anybody gotten a TivoNet board to work with a Sony SVR-2000 under 3.0?

Posted by: gizmomkr

I also reciently had my tivo take the 3.0 upgrade, and lost all my mod's.

My TivoNET moduels were removed, shell access through serial port disabeled, and Tivoweb gone :(

I have a prety firm grasp on the whole alternating booting of partitions, so it makes sence that all of that died, but when I tried to mount the drive in the pc again, mount returns a "Please specify FS type" It was really late, and I had been up for 48 hrs , so im not ruling out temporary insanity as the cause.

But I thought I had all my /dev/hdx's striaght.... Ill play with it more later this week, in the meantime....

Has anyone else had similar experience ?

Posted by: xmajic

Soundz like you installed the drive as a primary-master drive, aka /dev/hda.
Try installing it as primary-slave, aka /dev/hdb.

Posted by: xmajic

I got mine to work a few days ago. You'll have to yank your drive and put it in the PC. Don't run the Tivonet script though, it will actually disable routing and whatnot. Here's what I did:

1) Use kazymyr's boot cd.
2) Since 2.5.1 was still on partiton 4, I mounted it on /mnt/4 and 3.0 was on 7, mounted it on /mnt/7.
3) I copied the relevent last lines of the old rc.sysinit to the end of the new rc.sysinit.

tail -n 18 /mnt/4/etc/rc.d/rc.sysinit >> /mnt/7/etc/rc.d/rc.sysinit

For me this grabbed the last 18 lines of the old rc.sysinit script that handled loading the Tivonet drivers, set up telnet, bash on serial, tivoweb, etc. Do what works for you.
4) Make sure you change route.tivo to just route in the new rc.sysinit.