TiVo Community Forums Archives - Powering up.. Reboot loop

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

Powering up.. Reboot loop
(Click here to view the original thread with full colors/images)

Posted by: AussieOwner

Config:

DirecTivo Sony t60
2 x 120GB WD Caviar Drives
TurboNet
OS 3.1

=====================================================
This DirecTivo was upgraded successfully over a year ago
when it was running 2.5. Recently it was autoupgraded to
3.1 from DirecTV. My quest was to get my TurboNet and hacks
all working again with 3.1.

- Put disks in PC
- booted off turbonet cd
- ran nic_install

put disk back in tivo and booted..

everything is working fine

===================

telnet'd in to get TivoWeb, tytools and noscramble working again

downloaded the newest TivoWeb and ftp'd it to tivo
installed it and it worked fine

===================

downloaded the newest tytools and ftp'd it to tivo
Got an error in NowShowing.tcl
Looked at the code for NowShowing.tcl and fixed the following line:

if { [PrefixMatches "3.0" $tivoswversion] } {

updated to:

if { [PrefixMatches "3." $tivoswversion] } {

since im at 3.1, this function was returning a "0" for the variable Version3

After this update, this worked fine.

Interesting sidenote:
I downloaded a stream using tytools. In the past (2.5), when i downloaded a stream that had been recorded without noscramble turned on, the result was a "zero" length file. This time, the result was a small file. This file actually plays. I would have thought that if the stream were scrambled that it would have been completely scrambled. Anyway, just interesting.

===================

Now i, set my sights on getting noscramble working again. I download the newest copy (just to be safe) and ftp it to the tivo.

I run insmod noscramble.o. Everything seems to be OK.
However, i did not actually download a recorded stream to verify noscramble.o was working.

I was so confidient at this point, that i put the PC back together and booted it back up.

My last task was to get TivoWeb and tytools to start automatically. Now this is where i guess i screwed something up. In the past, i just put the cmdline in the rc.sysinit file. However, in some research i did, i read about the rc.sysinit.author file. This seemed simple enough.

In the procedure that i found for this (from tivo.stevejenkins.com), it said that the partitions 4 and 7 are (by default) mounted read-only. I didnt think that this was true because i had already created a /.profile. If the / partition were RO i could not have created this file. Nonetheless, didnt
think there was any harm in following the procedure so i executed:

mount -o remount,rw /

Then went to the /etc/rc.d dir and created my rc.sysinit.author file.

#!/bin/bash
/var/hack/tivoweb-tcl/tivoweb &
/var/hack/tytools/tserver_mfs6 &

did a "chmod 755 rc.sysinit.author"

thought i would give this a test so i executed:

./rc.sysinit.author

Worked fine, or so it seemed. Every time i executed the tytools exe on the PC side, i got an error on the Tivo side saying "Could not find file NowShowing.tcl"

It must be because i dont have /var/hack/tytools in my path. No worries, i will just kill the process and add it to my .profile.

Ok, so lets get the process id and kill it. Execute the ps command to get the process id. ARG!! There is no ps command. No worries, i will just comment out the tytools from the rc.sysinit.author file and reboot.

ARRRRGGGGG!!! Now im in a "powering on.." loop.

Put the A-Drive back into the pc and booted from CD. Removed the rc.sysinit.author file all together.

I also checked the timestamp on the rc.sysinit file and it matches that of the rc.net file. Thus i can verify that nothing has changed on the rc.sysinit file since the TurboNet driver was installed. Thus there is nothing wrong with this rc.sysinit file. It has not been modified.

I also want to point out that i believe this to be a software problem, not hardware. I have read thru many thread and they mostly talk about hardware problems. This system was working fine prior to performing
a restart.

Any suggestions/comments/prayers?