TiVo Community Forums Archives - TurboNet broken after 3.0 upgrade

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

TurboNet broken after 3.0 upgrade
(Click here to view the original thread with full colors/images)

Posted by: philcruz

I had successfully installed the TurboNet card/drivers on my SA HDR312 v2.5. I was able to ping and telnet. It immediately made a daily call and after restart it was at v3.0. I set the dialing prefix to ,#401 but it can't make a successful call anymore. My ethernet hub is a Watchguard SOHO that has DHCP. The DHCP says that it has not leased any IPs and I can't ping Tivo. My gateway IP is 192.168.111.1 and the net mask is 255.255.255.0. Is the Tivo expecting the gateway/DHCP server at 192.168.1.1 and it can't get an IP?

Any ideas what to do from here?

-Phil

Posted by: dsmdriver

Did you reboot after the ,#401? Tivo only grabs a DHCP address on boot. Make sure it's hooked up to a router with a DHCP server and then reboot it.

Posted by: philcruz

quote:
Originally posted by dsmdriver
Did you reboot after the ,#401? Tivo only grabs a DHCP address on boot. Make sure it's hooked up to a router with a DHCP server and then reboot it.

Yes, I unplugged the unit to power it down. I also tried System restart from the tivo menu. No effect. I have a link light on the TurboNet card. I confirmed the DHCP works because it will assign an IP to my PC on the network. Tivo just doesn't seem to be grabbing an IP.

How can I troubleshoot from here?

-Phil

Posted by: jafa

Hi,

Take a look at the kernel log and see what it says regarding 'ax88796'.

To access the log file from a boot CD:

mkdir /mnt/tivo
mount /dev/hdc9 /mnt/tivo
cat /mnt/tivo/log/kernel

Nick

Posted by: philcruz

quote:
Originally posted by jafa
Hi,

Take a look at the kernel log and see what it says regarding 'ax88796'.

To access the log file from a boot CD:

mkdir /mnt/tivo
mount /dev/hdc9 /mnt/tivo
cat /mnt/tivo/log/kernel

Nick

Here's what my log file says. It mentions setting the ip to 192.168.1.84 which is strange because my network is 192.168.111.x...then it shows the drive installation failed. What now?

-Phil

Jan 1 00:00:14 (none) kernel: Starting update ...
Jan 1 00:00:14 (none) kernel: Look for debug board ...
Jan 1 00:00:14 (none) kernel: setting ipaddr to 192.168.1.84
Jan 1 00:00:14 (none) kernel: setting macaddr to 0004ace30054
Jan 1 00:00:14 (none) kernel: SIOCSIFHWADDR: Operation not supported by device
Jan 1 00:00:14 (none) kernel: SIOCSIFADDR: Operation not supported by device
Jan 1 00:00:14 (none) kernel: eth0: unknown interface.
Jan 1 00:00:14 (none) kernel: Enabling local route...
Jan 1 00:00:14 (none) kernel: Setting TCP keepalive parameters...
Jan 1 00:00:14 (none) kernel: Starting logging daemons...
Jan 1 00:00:14 (none) kernel: Check for PROM update ...
Jan 1 00:00:14 (none) kernel: Updating system clock UID=0
Jul 11 08:23:59 (none) kernel: Time set to: Thu Jul 11 08:23:59 2002
Jul 11 08:23:59 (none) kernel: Have a nice day.
Jul 11 08:23:59 (none) kernel: Configuring network...
Jul 11 08:23:59 (none) kernel: Loading 8390 driver
Jul 11 08:23:59 (none) kernel: Probing for Ethernet card
Jul 11 08:23:59 (none) kernel: NE*000 ethercard probe at 0x300
Jul 11 08:23:59 (none) kernel: not found (not an 8390).
Jul 11 08:23:59 (none) kernel: tivone.c: No NE*000 card found at i/o = 0x300
Jul 11 08:23:59 (none) kernel: /lib/modules/tivone.o: init_module: Device or resource busy
Jul 11 08:23:59 (none) kernel: ax88796: updated tlb entry 2 to 1M
Jul 11 08:23:59 (none) kernel: ax88796: NIC not found at 0xf4000000
Jul 11 08:23:59 (none) kernel: ax88796: driver installation failed
Jul 11 08:23:59 (none) kernel: /lib/modules/ax88796.o: init_module: Device or resource busy
Jul 11 08:23:59 (none) kernel: No card found

Posted by: sumdude2

Take a look at the link I sent and read all of it. Could be your problem is related to one of these.

http://www.silicondust.com/turbonet...procedures.html