3.1 Upgrade Has Locked Me Out and NoScramble Issues

[rpongett]

My system upgraded to 3.1.0 last night.

I now can Ping it (though I have to use DHCP now), but can't get a Bash prompt.

The reason I posted on this (extraction) forum is that it also won't show any of my prior recorded programs. I think because they were recorded with noscramble. It will play a program it recorded this morning (the upgrade likely disabled noscramble). I think that can be fixed with AlphaWolf's noscramble kernal patch.

What do I do to get bash access back?

Once I have it back, will AlphaWolf's noscramble kernal patch make it like it was before?

[mrblack51]

1) if it upgraded on its own, then you will need to kill the initrd checks so you can mess with the files on the drive (assuming you have already hacked the prom previously with something, such as 25xtreme). kill_initrd on the turbonet install cd does a great job of this

2) programs recorded with noscramble will not play back on a scrambled system. as such, you will need to apply the noscramble patch to your kernel. the one alphawolf posted will do just fine

3) to get bash access, after doing the two above kernel hacks, you should be able to obtain bash/telnet/ftp/whatever using the same methods as before. many howtos exist on how to do that.

[rpongett]

Originally posted by mrblack51
1) if it upgraded on its own, then you will need to kill the initrd checks so you can mess with the files on the drive (assuming you have already hacked the prom previously with something, such as 25xtreme). kill_initrd on the turbonet install cd does a great job of thisI have not installed 25xtreme. I only used the Turbonet Install CD image nic_cd_20020728.iso to get Turbonet up and running. It does require that you "flash" the prom when installing.

Given that, can I get a bash prompt/ftp, etc . . . by just pluggin in my TIVO drive to an IDE port, booting the Tivo Boot CD and running kill_initrd off of a floppy?

If not, what do I need to do to get a bash prompt, ftp access, etc . . . so I can continue extracting again.

Thanks in advance for any info.

[mrblack51]

to get bash via telnet, add the following to the bottom of rc.sysinit

/sbin/tnlited 23 /bin/bash -login &

to get bash via serial, add:

/bin/bash </dev/ttyS3 >& /dev/ttyS3 &

to get ftp, you will need to grab the tivo-bin dir from the old install. assuming your current version is running on hda7:
mount /dev/hda4 /mnt
mkdir /tivo-bin
cp /mnt/tivo-bin/* /tivo-bin
umount /mnt

then add the following to rc.sysinit:
/tivo-bin/tivoftpd

if you want more info, please read the various how-tos posted throughout the forum, they give you all the info you need

[rpongett]

Aren't those already on my Tivo directory from teh first install (I was using them until last night "upgrade" to 3.1).

If so, do I need to install them again after I kill_initrd?

[bmm64]

This is probably redundant for all you experts, but these are my notes for rebuilding DTivo after it got upgraded to 3.1...

[zeek]

I'm still having a problem with NowShowing.tcl...
I've followed all the directions I can find, done multiple searches etc.

My NowShowing script is executing, but am receiving the following error:

============================
% ./tserver_mfs5
Doing the Lowest PriorityFix...
Priority set...
Waiting for an incomming connection!
SERVER: We got a message! buf = 'SHOWING'
invalid attribute: TimeZone
while executing
"dbobj $setup get TimeZone"
("uplevel" body line 5)
invoked from within
"uplevel $body"
invoked from within
"transaction {uplevel $body}"
(procedure "RetryTransaction" line 5)
invoked from within
"RetryTransaction {
set setup [db $db open /Setup]

# set defrecquality [dbobj $setup get RecordQuality]
set setuptz [dbobj $setup ..."
(procedure "init_db" line 45)
invoked from within
"init_db"
(file "./NowShowing.tcl" line 455)
Waiting for an incomming connection!
=============================


I've got a DirecTiVo with 3.1 no Extreme, no Kraven- totally legal box with both TiVo and DirecTV.



TIA for any insights...

zeek

[mrblack51]

nowshowing looks like it is trying to access a variable that has been moved to a different place in the mfs. this is one of those minor changes needed for 3.x software over 2.x. im sure it will be updated soon