Help! 3.1b broke my DTivo!

[AbMagFab]

Okay, let me calm down. I've got a 9thTee ethernet card (hardwired), and I hacked tivoweb, and autoscramble.

Now, nothing is working! My DTivo (SAT-T60) got patched last night with 3.1b, and I can't telnet in anymore, and my new programming is scambled, and I can't see any of the programming that was recorded unscrambled!

I haven't unplugged the drives yet to mount and check the rc.sysinit, but has anyone else seen this behavior? Any ideas on how to fix it?

HELP!

[GREEK]

you wiped out your var hack directory probably. You shouldnt take ANY updates on a hacked box, only do them manually with a hacked image...........

[AbMagFab]

Phew! Okay, for anyone who is curious...

I have a standard kernel, but I hacked in the 9thTee ethernet card, along with TivoWeb and AutoScramble.

It looks like the 3.1b patch blew away my rc.sysinit. But strangely, when I plugged the drives into my PC, the rc.sysinit had the couple of lines for the 9thTee ethernet card. I didn't test it, but the patch might have just reset the driver to all dhcp (I had fixed IP address/gateway).

Anyway, I re-ran nic_install, put the drives back in my Tivo, and then added the tivoweb and autoscramble lines to the rc.sysinit.

I also had to recreate .profile in the root.

All is back to normal now! /var/hack was fine, it was just the rc.sysinit (and .profile) that got slightly nailed by the patch.

Phew!

[David Bought]

Originally posted by AbMagFab
Phew! Okay, for anyone who is curious...

I have a standard kernel, but I hacked in the 9thTee ethernet card, along with TivoWeb and AutoScramble.

It looks like the 3.1b patch blew away my rc.sysinit. But strangely, when I plugged the drives into my PC, the rc.sysinit had the couple of lines for the 9thTee ethernet card. I didn't test it, but the patch might have just reset the driver to all dhcp (I had fixed IP address/gateway).

Anyway, I re-ran nic_install, put the drives back in my Tivo, and then added the tivoweb and autoscramble lines to the rc.sysinit.

I also had to recreate .profile in the root.

All is back to normal now! /var/hack was fine, it was just the rc.sysinit (and .profile) that got slightly nailed by the patch.

Phew!

AbMabFag,

/var is generally not affected by upgrades unless it gets purged due to filesystem errors or excessive disk usage.

Your old .profile and rc.sysinit should still be on the inactive root partition, either hda4 or hda7 - whichever one is not mounted.

[AbMagFab]

So during any official upgrade, it copies the old .profile and rc.sysinit to an inactive partition?

Any idea why my Turbonet drivers managed to get re-added to the rc.sysinit when nothing else did?

[mrblack51]

Originally posted by AbMagFab
So during any official upgrade, it copies the old .profile and rc.sysinit to an inactive partition?

Any idea why my Turbonet drivers managed to get re-added to the rc.sysinit when nothing else did?

during an official upgrade, it simply switches the root from 4 to 7 (or the other way around as appropriate). as such, any hacks that were on the root are not active, and the stuff on /var should still be there, but is simply not accessed. you have to re-hack your kernel image to disable the initrd, then re-apply any hacks that were done to the root partition.

as for why the turbonet drivers are there, its because tivo started including them as of version 3.0

[AbMagFab]

So now that I have a modified rc.sysinit and .profile on both 4 and 7 (presumably, since I rehacked last night and it's working after a reboot), will I not have this problem anymore? Or will they rewrite the rc.sysinit each time they switch active partitions?

[mrblack51]

every time new software is installed, the filesystem that it is being installed to is wiped and then the new files are put on there. as such, you need to re-apply hacks after every upgrade (hence why upgrades arent always a good thing)

[oviTyonS]

My SAT-T60 got the upgrade today and I put the A drive in My PC and tried to run nic_install via "/nic_install/nic_install tubonet" from the 9th_tee CD but it faild with Determining Software Version... Error unable to access MFS.

I then did the following command: "/nic_install/nic_install tubonet --force 3.1.0b-02-1-011" and it worked

I hope this helps anyone that gets the same error.

Kevin

[jmhenry5150]

Guys help!

The same thing happened to me!

Lost:
- FTP
- Telnet
- Everything

Here's the deal - I am a very computer literate but a dummy when it comes to the TiVo and Linux...

What steps can I take?

If you guys can get me back up, I would really appreciate it...

I have a DSR6000 (DirecTivo) with the newest software update (duh!)

Thanks in advance!

[AbMagFab]

Just re-hack the way you did the first time. And do what I did this time - document it! I kind of forgot the hacks and had to research, again, what I did last time.

Just a note, if you have a dhcp server, it's possible that your nic drivers are working fine, you just have a DHCP'd IP address instead of the fixed IP address you assigned. I'm not sure, but I think that would have saved me a lot of time re-hacking TurboNet.

[gobsmack]

Francesco at TCF fixed this one nicely -- just do this to re-copy your hacks back...

here (http://www.tivocommunity.com/tivo-vb/showthread.php?s=&threadid=139861)

[invader zog]

I had a similar panic attack this morning.

Thanks for the advice. My system is back in action now. :)

[AbMagFab]

Well, it patched my second SAT-T60 DTivo, and it doesn't look like the TurboNet drivers are actually running.

So you need to pop out the drives and re-hack everything, starting with nic_install.

At least it all still works!