PDA

View Full Version : Turbonet won't work in Sony SA TiVo I


haroldpga
04-27-2005, 02:44 PM
I am having a problem with installing a turbonet in a standalone TiVo.

The unit is a Sony SVR-2000. It was upgraded several years ago from the original 30 Gb drive to Two 80 Gb Maxtor drives, and has been working fine since the upgrade.

The current software level is 3.0.1.A1.01.1.010. The machine is registered for product lifetime service, and takes input from the RF cable, with no box.

About six months ago, a thunderstorm took out the the internal modem. I found the procedures on the network to use an external modem and everything continued just fine.

Last week, I ordered a turbonet adapter from 9th tee. I got it, and installed it in the TiVo. Changed the dialing prefix to ,#401 and the tivo connected over the internet just fine. It downloaded the latest program information and was running fat, dumb and happy.

My DHCP server shows a lease has been issued to a machine with a MAC address of 00:0B:AD:26:55:b2. I could ping the TiVo at the address 192.168.1.10.

Now the problems began. I removed the "A" drive from the Tivo and put it in a pc. Using Steve Jenkins TiVO Network Hack How-To guide (http://tivo.stevejenkins.com/network_cd.html)
I downloaded his CDROM image, burned a copy, and booted the pc with it. Following his instructions, I was unable to mount the three necessary partitions.

First problem! Something in the back of my mind was bugging me as to why the linux startup messages showed the drive as only having 10 Gb instead of the 80 Gb it should have. Remembered about unlocking the drive. Downloaded a copy of QUNLOCK.EXE, created a DOS boot floppy, put the QUNLOCK.EXE file on it, and ran it against the drive. Now I can mount it.

Following Steve's instructions, I created the /mnt9/hack (actually /var/hack) and copied the three files to it.

I then created /mnt4/etc/rc.d/rc.sysinit.author. It contains only two lines:

#!/bin/bash
/sbin/tnlited /bin/bash -login &

I made it executable, and verified that tnlited actually did exist in the directory /mnt4/sbin.

I then copied this file from here to the directory /mnt7/etc/rc.d

I unmounted all of the partitions, halted the system, removed the drive, and returned it to the TiVo.

I powered the TiVo on, and lo and behold, not only could I not telnet to the address assigned to the TiVo, I couldn't even ping this address. I used the TiVo remote to make a test call. It failed with:
Preparing (Done)
Dialingcc (Done)
Connecting (Failed, Service Unavailable.)

OK, I'm backing up here. This was working before I tried to turn on telnet.

Took the drive out and put it back in the PC. Had to run QUNLOCK.EXE again! What's with this? Is the TiVo locking the drive? OK, I can live with having to unlock the drive EVERY TIME I WANT TO UPDATE IT!

Everything looks the same on the drive. More reading of FAQs... Could it be I need to run kill_initrd ?? Steve's FAQ says it is only necessary to run it on a DTiVo, not a regular SA TiVo.

OK, let's give it a try. I ran "/kill_initrd/kill_initrd info" and got the following:

Detecting TiVo hard drive...
Found TiVO hard drive - /dev/hdc (Secondary Master).
Detecting TiVo partitions...
Active kernel partition = /dev/hdc3.
Inactive kernel partition = /dev/hdc6.
Active root partition = /dev/hdc4.
Inactive root partition = /dev/hdc7.
Var partition = /dev/hdc9.

Determining software version...
Sony SA running 3.0.1.A1-01-1-010

Scanning for initrd...
initrd found to be active

So, I used kill_initrd to turn it off...

Checked my files I had created above, and they all looked OK. Put the drive back in the TiVo, and nothing has changed. Still no ping, no telnet, and no program data updates via the ethernet.

Just to be sure, I unplugged the ethernet cable, and put it in my laptop. Sure enough, it works fine.

Just it case it turned out to be a problem with the DHCP server, I renamed rc.net to rc.net.orig and created a new rc.net containing the following:

#!/bin/bash
/sbin/ifconfig eth0 192.168.1.10 netmask 255.255.255.0 up
/sbin/route add default gw 192.168.1.1

put drive back in TiVO, powered up, and no change... Still doesn't work... :mad:

Moved drive back to the PC... Tried to out everything back the way it was. Removed rc.sysinit.author. Put back the original rc.net. Now the /etc/rc.d directory looks the same as when I started. I didn't remove the /var/hack directory since I can't picture how that makes any difference.

Back to the TiVo one more time... Nothing has changed. Where do I go from here???

It was working, and now it's broke...

Help!

Harold

eastwind
04-28-2005, 02:05 PM
Tried re-installing the drivers from silicon dust? Or rebooting your router?

ew

haroldpga
04-28-2005, 04:07 PM
Tried re-installing the drivers from silicon dust? Or rebooting your router?

ew

I'm not sure how to re-install the drivers. I'm using the built-in drivers included in v3 of the TiVo software. I didn't have to install them in the first place when the turbonet was working before I started trying to configure telnet.

The router is a linksys 16 port switched hub. I power-cycled it and it didn't make any difference. The Firewall is a linux box running Fedora Core 3 and ipchains. Everything else is working fine, so I don't think it is a problem. Anyway, I can't see the TiVo from inside the firewall.

I set up ethereal to filter on the mac address of the Tivo (Obtained when it was initially working) and don't see any packets to or from the unit when I powered it off and back on.

I decided to try something else. I disconnected the ethernet cable, and removed the turbonet adapter from the TiVo. Powered it on, and allowed it to boot. Tried to dial using the modem. No dial tone. (I knew this, since the internal modem was fried in a thunderstorm over a year ago.) Then, I re-installed the turbonet and connected the ethernet cable. Power on again, and try to dial using the network. IT WORKS!!!

I've decided it's magic.

Now to try removing the drive and configuring telnet again. Wish me luck. I'll report back here when I get telnet working...

Thanks for the suggestions

Harold :)

eastwind
04-28-2005, 04:25 PM
Sounds like the board might've gotten a bad seat. Mine stopped working after years of sevice and I was pulling my hair out trying to figure it out. Turns out it wasn't seated properly.

If you use the install program from silicon dust I believe it will load and enable ftp and telnet.

ew

haroldpga
04-28-2005, 10:50 PM
I can believe it. Kicking the tires often seems to fix these sort of problems.

It is working fine now. I have installed all the usual binaries and everything is working. TyTool's server works, and I was able to exstract a .ty file.

Now I just have to figure out what to do with it...

Thanks to everyone who helped.

I'm going to declare this thread closed. No more responses are needed.

Harold :)