Help with TurboNet Install...

[TRILIGHT]

Facts to consider:

1) System is running 25xtreme successfully.
2) System has been upgraded via Kraven's update successfully.
3) Bash prompt obtained via serial port with no problems.
4) Link lights for TiVo unit show up just fine.
5) Cable is a known-good cable.
6) Port used is a known-good port.

Problem:

No matter what I do, I do not seem to be able to see the TiVo (SAT-T60) unit on my network. First, I tried letting the Kraven update grab an IP address via DHCP like it says it will. It never happened.

Next, I tried following the Kraven instructions to set a static IP address. Still nothing.

Next, I tried following the directions of ScanMan0 on this How-To page. (http://www.dealdatabase.com/forum/showthread.php?s=&threadid=5827&pagenumber=3) I still get nothing.

Can someone please point me in the right direction for getting this up and running via the serial bash prompt I currently have? I know that there is a boot CD for download that *HOPEFULLY* would do the trick, but that would require tearing down my systems again just to do this. Surely there is a better way and someone will share it with me. Thanks!!!

[BubbleLamp]

Need more data. Are you connecting directly to a PC, or through a hub? What are the IP address and subnet mask settings for each? What is the default gateway set to? Post your lines in the init file so we can look. Is the telnet daemon running on the Tivo? Lots of potential potholes, gotta eliminate them one by one.

[TRILIGHT]

As for the network params (IP, gateway, mask, etc.) I can assure you all of that is correct. I run my own network at home and I am very familiar with these settings. It has to lie somewhere in the way things are loading up I would imagine. Here is the first thing I tried which, according to the Kraven readme update, should be in the rc.remote-login file:


ifconfig net0 192.168.0.50 netmask 255.255.255.0 up
route.tivonet delete default 2> /dev/null
route.tivonet add default gw 192.168.0.1 netmask 0.0.0.0 dev net0

When that did not work, I tried the manual method that ScanMan0 suggested in the link I provided. I entered the following lines at the bottom of my rc.sysinit file:


insmod -f /lib/modules/ax88796.o macaddr=010203 timing=5
ifconfig eth0 192.168.0.50 netmask 255.255.255.0 up
route.tivo add default gw 192.168.0.1

Trying either method, when I attempt to ping the IP address 192.168.0.50, I get no response.

[captain_video]

You might try downloading the TurboNet software and running it manually. I don't think I ever got mine running after installing Kraven's update until I installed the software from scratch even though the drivers are supposed to be included in the update. This also allows you to set up a static IP address on the DTivo. The install only takes a couple of minutes and worked perfectly first time, every time (I've already set up several TurboNets on DTivos). I've never had to use scanman's procedure or anyone else's by going this route.

[BubbleLamp]

Your first example, the netmask for the gateway is wrong.

Your second example should work. Why don't you try entering those commands via the bash prompt and see if they execute properly.

[TRILIGHT]

Thank you both for your advice and help! I just wanted to post here for anyone who may have the same problem and might not be totally familar with Linux.

First thing that will help you out a LOT (and this is also listed in the "tips" post located on this forum), is to set your Tera Term to Terminal Setup to 80 x 25. It defaults to 80 x 24. I got kind of good at editing in the screwed up default way but I highly recommend you switch to 80 x 25! hehe ;) You could seriously screw a file up if you're not careful.

Next, I finally got this working by placing my entries in the rc.sysinit file. The problem was (and I guess Linux gurus all know this without a problem) is that I placed my entries at the very end of the file. This did not work for me. I had to place my entries BEFORE the "exec < /dev/ttyS3 >& /dev/ttyS3; bash --login" line. After I moved my entries BEFORE this line, I was up and running fine!

I'm still rather curious why the entries in the rc.remote-login file did nothing at all. Is this file not run at all on startup? If not, why was it recommended this is where I should put them? When is this file used?

[BubbleLamp]

Originally posted by TRILIGHT
I'm still rather curious why the entries in the rc.remote-login file did nothing at all. Is this file not run at all on startup? If not, why was it recommended this is where I should put them? When is this file used?


rc.sysinit loads rc.arch. rc.arch loads the ethernet drivers. Later in rc.sysinit it calls rc.net. rc.net looks like it does a check to use DHCP, then calls rc.remote.login, which loads ftp, nfs, fixsub, noscramble, and others.

Why does it do all that the way it does, ask KRaveN! :D