Official Slicer Discussion Thread

[SilentBob]

...had just originally run the PTVNet CD to open it up and upgrade the hard drive a couple of years ago.

not Zipper, PTVNet CD

[rbautch]

not Zipper, PTVNet CD

That's okay, you just need to perform a few additional steps. First thing to do is grab the network.tcl script that's included in the zip file here. Transfer the file to your tivo using your serial cable and a file transfer protocol called zmodem. It's easier than it sounds. Do a search on TCF or DDB to find instructions on how to do it. It might be simpler to pull the drive and rerun PTVnet on it, but you'll find that knowing how to use a serial cable is an extremely valuable tool for troubleshooting down the road.

[park_ridge_dave]

Hi:

I have 2 HR10-250's my primary (in family room) was having a "re-boot" problem (random when viewing and at about 9:00pm every night) I checked and it was still running 6.3d but with 6.3e in the "on-deck". So I sliced it and it stopped re-booting. I would like to do the same to my second receiver, but, it has not received the 6.3e software download yet. (I had this box in my RV so it was not hooked up to a dish at all times).

I now have the second box hooked up at home and wondered how long it will be until I get the 6.3e download? I will search again on this forum, but, so far, I haven't found a way to "force" a download. Is there anyway to do this?
Or do I just keep checking my system files everyday?
( I seem to recall the download comes from the satellite and that it gets activated by the "phone call" or by using slicer etc.)

OBTW both boxes originally "hacked" using PTVnet and Instantcake. Until the last three weeks or so no problems (none not caused by me, that is ) whatsoever.

Thanks,

Park_Ridge_Dave

[Lou Jacob]

You can try using the -d option on the unit that hasn't yet received the slices; no guarantees, but I tested it on a newly upgraded unit and it worked fine.

[rbautch]

I used the -d option and it worked just fine on my HR10-250 to download the new slices. I ran the Slicer with this format:

./slicer 6.3e-01-2-357 -d

If you're not experiencing reboots on the second tivo, I wouldn't upgrade from 6.3d to 6.3e.

[park_ridge_dave]

I used the -d option and it worked just fine on my HR10-250 to download the new slices. I ran the Slicer with this format:

./slicer 6.3e-01-2-357 -d

If you're not experiencing reboots on the second tivo, I wouldn't upgrade from 6.3d to 6.3e.

Lou (when do you sleep?) and Rbautch thanks! I'll watch box #2 to see if it develops the "re-boots" until then, "I won't fix it if it ain't broke!"

Dave

[Lou Jacob]

Very rarely, indeed.

Good luck and please report back with your results (if you end up slicing).

[SilentBob]

That's okay, you just need to perform a few additional steps. First thing to do is grab the network.tcl script that's included in the zip file here. Transfer the file to your tivo using your serial cable and a file transfer protocol called zmodem. It's easier than it sounds. Do a search on TCF or DDB to find instructions on how to do it. It might be simpler to pull the drive and rerun PTVnet on it, but you'll find that knowing how to use a serial cable is an extremely valuable tool for troubleshooting down the road.

Ok...well I ran into a bit of a delay building my serial cable, but I now have that built and functioning. However, something definitely seems to be wrong.

The console cable works, and I have bash access. However, when I try to run the network.tcl file, it bombs and reboots the tivo.

After it failed the first time, I ran it again, while logging the console in Hyperterminal. Attached is the output of the console log that includes the failure as well as the subsequent boot messages.

Where do I need to go from here?

[SilentBob]

Ok..I've been playing around with this a bit more, trying to figure out what is going on.

So everything is in place and it is attempting to start networking with DHCP when it boots.

I have tracked everything through rc.sysinit.author and see all of the different scripts that are being called.

It is barfing when it tries to run dhclient.

Running it manually it responds:

bash-2.02# dhclient
Internet Software Consortium DHCP Client 2.0
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.

Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html

socket: Address family not supported by protocol
Make sure to set CONFIG_PACKET=y and CONFIG_FILTER=y in your kernel configuratio
n!
exiting.

I then attempted setting the correct static IP information in rc.sysinit.author and then changed the flags in /init/ptv_flags so that it uses STATIC vs DHCP. After the reboot, the eth0 is configured as I asked for it to be, however, I am still not able to ping the default gateway (and I have verified that the network link is good by removing the cat5 cable from the tivo and plugging it in to my laptop)

So something is definitely wrong with the Tivo networking.

after booting, typing ifconfig eth0 gives me:

bash-2.02# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:0F:B5:FB:FE:1C
          inet addr:192.168.1.200  Bcast:192.168.1.255  Mask:255.255.255.0
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:54 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:504 dropped:12 overruns:0 carrier:0 coll:0

I'm pretty sure that 504 errors on TX is not a good thing.

Also, once the Tivo has been up for a few minutes, I am no longer able to pass network traffic through the switch that the Tivo is plugged into (my laptop in another port on the switch is unable to communicate with my router) as soon as I unplug the cat5 link to the tivo, my laptop is able to communicate just fine again.

Thoughts?

[rbautch]

Ok...well I ran into a bit of a delay building my serial cable, but I now have that built and functioning. However, something definitely seems to be wrong.

The console cable works, and I have bash access. However, when I try to run the network.tcl file, it bombs and reboots the tivo.

After it failed the first time, I ran it again, while logging the console in Hyperterminal. Attached is the output of the console log that includes the failure as well as the subsequent boot messages.

Where do I need to go from here?

The FsAllocateFunction errors are caused by not having the following in your author file:

export TIVO_ROOT=
export MFS_DEVICE=/dev/hda10

Also, when you run the network script, you need to enter your IP address and default gateway as arguments, like this:

 ./network.tcl 192.168.1.106 192.168.1.1