SA 2.5 'upgrate'

[ircbob]

so, i get up this morning, and plan on watching some tivo b4 goign to work.. i turn it on and i see a friendly 'you will be receiving the fall 2001 upgrade in the next few days' message. i look at the sys info, and its pending restart. i debate going back to an older backup but i figure, ah, what the hell. i restart the system.

so im looking at a screen that is now:

2.5.1.G3.01-1-000 on my SA single drive tivo, mod'd to 91 hours.

I try to do a forced test call via tivonet, and well, nada. i try to ping/telnet, nada either. (i guess i expected it).

ill try tonight and poke 'round and see what was changed and try to re add my rc.tivonet scripts and report then.

has anybody else gone thru this yet? im curious to hear any success/ failure stories w/ 2.5.

i assume this 2.5 is out in the public now, cuz i dont remember signing up or requesting to be on a beta program.

[Fugg]

thanks for the warning!!

[TroyCarpenter]

Well, a few weeks ago I finally upgraded from 2.0.1-001 to -002 (resolution fix). I noticed after the upgrade I could not access the box via my ppp connection, let alone use Tivoweb or ftp.

When I got into the boot prom, I noticed that hda7 was the new active partition. When I set hda4 as the partition and rebooted, I got everything back. The answer, obviously, is that none of my changes were on the newly active partition. So I changed the appropriate files on hda7 to renable my hacks, rebooted into hda7 and everything worked fine.

I expect the same thing will happen when the upgrade goes from 2.0.1 to 2.5. It will install onto hda4, overwriting that partition with the unhacked software. After the reboot, no hacks will be active. It should be a simple matter to renable the easy ones, like bash prompt (I say "simple matter", but it is really likely to be a pain in the butt involving pulling drives and all).

I would guess TiVoweb will need to be modified for database changes. My Tivonet card arrives today, and I don't have 2.5 either. If 2.5 uses the same libc libraries, then a reinstall of Tivonet may be all that's required.

Note that I am not speaking from first-hand experience with 2.5, just from what I experienced in my minor update. In my case, it helped that the software on hda4 and hda7 were so much alike that I could make the changes from hda4 and not have to pull the drive. I am guessing that unless you catch the update before the reboot, you will at least need to pull the drive to renable the bash prompt.

In short, I would have expected what was reported here. I too am interested to see if ircbob's reinstallation of Tivonet works, but it sounds like he also needs to get the basic bash capability back as well.

Troy

[ircbob]

hmm i noticed yesterday that i spelled upgrade wrong. i couldnt find a way to correct it :-(

anyhow, as expected, tivonet is still working.. there's some new modules compiled for 2.5.. i updated my rc.sysinit to call rc.tivonet, changed the route, and modified the TClient.itcl to drop the ppp dialup.

i havent tried the ExtractStream nor tivoweb, but my primary usage of tivonet was using the lan to get guide data, and that is all good :-)

if you need the link for the new modules,

2.5 modules (http://www.dyslexia.nu/tivo/tivonet/modules/2.5.1/)

[KenNashua]

Does anyone know if it's safe to boot off the alternate partion (2.0) after the 2.5 upgrade, modify the rc.sysinit file and then restore the default boot partition?

I know this was a no-no as I just spent the afternoon recovering my TiVo from a backup after accidentally munging the rc.sysinit file on my 2.0 partition and then trying to boot off of of the 1.3 partition.

[Fugg]

Ken,

Since no one else is responding I’ll give it a shot.

“I just spent the afternoon recovering my TiVo from a backup after accidentally munging the rc.sysinit file on my 2.0 partition and then trying to boot off of the 1.3 partition.”

The reason, I believe, you could not boot and use the version 1.3 partition after upgrading (and booting at least once) to version 2.0 on the other partition is that when the box upgraded to 2.0, it made changes to the MFS region. When you tried to boot to 1.3 after booting to 2.0, 1.3 could not “see” the MFS region properly.

From what I understand, 2.5 makes no major changes to the MFS region. So, in theory, you should be able to boot to 2.0 after upgrading to 2.5.

As I don’t yet have 2.5, this is all just guess work on my part. If 2.5 makes any other changes to other partitions, all bets are off.

I’m sorry if this doesn’t help much, but I know it sucks when you post a question that no one answers!

[KenNashua]

Thanks for the post. Apparently, though, running 1.3 on a 2.0 MFS partition does permanent damage as I fixed my rc.sysinit file and restored the default boot partion to my 2.0 partition with the same results...

[kronos80]

What one can do is go into the diag mode and set the boot params to the other partition: 4->7, or 7->4; and follow that with runmyworld=false. This will prevent the software from fully starting. You can then edit the rc.sysinit to do a bash prompt and then reset the boot params back. Then just reboot and get into the bash prompt from 2.5 and make the rest of the changes.

I know that you can do all of your changes from 2.1 but I didn't want to be in 2.1 more than necessary.

Hope that helps someone.

Shawn

P.S. TivoNet drivers from 2.1 work on 2.5 as well as telnetd and ftpd, but tivoweb and any other program accessing MFS does not.

[Fugg]

Originally posted by KenNashua
Thanks for the post. Apparently, though, running 1.3 on a 2.0 MFS partition does permanent damage ...

from my post above:

"when the box upgraded to 2.0, it made changes to the MFS region. "

when you attemped to go back to 1.3, it wrote to the mfs region as it normally would, hosing up the 2.0 modifications to the point nethier one could use it.

[Saturn]

I just had a runaround last night with trying to boot my 2.0.1 partition after upgrading to 2.5.1. Couldn't get it to go. Tried the standard boot parameters to disable myworld (runmyworld=false, upgradesoftware=false, handcraft=true), but the rc.sysinit was still trying to load momstart (myworld). It was located under where it says "starting Event Handler" or something. There's no "if not handcraft=true" around it, so myworld was started anyway. This made the tivo reboot about 1 minute after starting my PPP connection. That 1 minute was just enough for me to get into my rc.sysinit and cut it off, and munge it up so I had to take out my hard drive to get my scripts onto my 2.5.1 partition.

Just a warning - booting into 2.0.1 after upgrading to 2.5.1 isn't as easy as the 2.0.1/1.3 combination.

Note that no permanent damage was done to my MFS partition (that I know of, haven't been running >24h yet), but I did notice that when I booted into 2.5.1, it said "updating database, this will take a long time", even though it had done that once before, when I first booted into 2.5.1
immediately after the upgrade.


So, if you are smart, you'll customize your 2.0.1 rc.sysinit before it upgrades to 2.5.1 so you can get back into it safely.