hr10 250 diffivulty

[xats3]

new 6/2006 hr10 250. succesfull drive copy for back up which boots up fine
unsuccesfull network implementation using killhdinitrd
when i put the drive back in the pc the files which i wrote are gone such as .profile and rc.sysinit.author
killhdinitrd gives a meesage which appears succesfull althogh i do not know what the message means

can soeone tell me how tofind the working kernel version? and tivo hadware version as a beguining

[cheer]

Um, could you post the message? The one that you don't know what it means?

In any case...you might consider getting the $5 ptvupgrade boot CD which has a 3.1.5 kernel that's already had killhdinitrd run on it.

Also...how did you determine which partition to add rc.sysinit.author, etc., to?

[xats3]

i used the http://www.imbetterthanyou.com/hr10-250/hr10-250_body.html
guide

Mount the floppy that we copied tivoftpd.mips and killhdinitrd onto:
mount /dev/fd0 /floppy

Run killhdinitrd from the floppy. All of the new HR10-250's use partition 6 as the active kernel partition.
/floppy/killhdinitrd /dev/hdc6

Mount the HR10-250's var partition to copy over the ftpd:
mkdir /mnt/var
mount /dev/hdc9 /mnt/var
mkdir /mnt/var/hack
cp /floppy/tivoftpd.mips /mnt/var/hack
chmod 755 /mnt/var/hack/tivoftpd.mips
mkdir /mnt/var/hack/bin
mkdir /mnt/var/hack/lib
mkdir /mnt/var/hack/root


Now unmount the floppy and the var partition and shutdown the pc:
umount /mnt/floppy
umount /mnt/var
halt

Create a mount point for the partition and mount it:
mkdir /mnt/mnt7
mount /dev/hdc7 /mnt/mnt7

Change to the directory that will house rc.sysyinit.author
cd /mnt/mnt7/etc/rc.d

Edit rc.sysinit.author:
pico rc.sysinit.author

Create the file as follows, except substitute the correct IP address, broadcast address and netmask for your network. When you are done editing the file, hit ctrl-x and pico will prompt you to save it.
#!/bin/bash

#load usb and ethernet modules
insmod /lib/modules/usbcore.o
insmod /lib/modules/ehci-hcd.o
insmod /lib/modules/ax8817x.o
sleep 15

#configure Linksys USB200M
ifconfig eth0 192.168.1.100 broadcast 192.168.1.255 netmask 255.255.255.0
sleep 60

#start telnetd
tnlited 23 /bin/bash -login &

#start ftpd
/var/hack/tivoftpd.mips


After saving the file, make it executable:
chmod 755 rc.sysinit.author

Now switch to the root dir of the mount point
cd /mnt/mnt7

Edit .profile
pico .profile

Create the file as follows, then ctrl-x and follow the prompts to save it.
export PATH=/tivo-bin/:$PATH":"/var/hack/bin/:/var/mfs_ftp:/var/hack:
export LD_LIBRARY_PATH=/var/hack/lib/":"$LD_LIBRARY_PATH
export HOME=/var/hack/root

Unmount the directory and halt the PC:
cd /
umount /mnt/mnt7
halt

[xats3]

i used pvtvupgrade $20 boot cd

[PlainBill]

The guide you followed was written for 3.1.5. You probably have 3.1.5f. Also, the guide has an error: All of the new HR10-250's use partition 6 as the active kernel partition. I suggest using bootpage to determine the true active partition, and it would be a good idea to determine which software version you have. Killhdinitrd will not work with the kernel supplied with 3.1.5f

PlainBill

[cheer]

Run killhdinitrd from the floppy. All of the new HR10-250's use partition 6 as the active kernel partition.
/floppy/killhdinitrd /dev/hdc6
This is a very good example of why guides suck.

First, as PlainBill points out, this guide assumes that you are running 3.1.5. That's hideously outdated -- you're almost certainly running, as he said, 3.1.5f. Killhdinitrd won't work directly on a 3.1.5f kernel (or 3.1.5e or any 3.1.5x version other than 3.1.5 itself); you have to replace the kernel with a 3.1.5 kernel.

Next, as PB also pointed out, the active kernel partition could easily be either 3 or 6. Boot up off of the PTVUpgrade boot CD and use "bootpage -p /dev/hd#" -- replace # with the device ID of your Tivo hard drive (you used c above so I presume you connected it as secondary master). That will tell you which is root, 4 or 7. The active kernel is one less (3 or 6).

[xats3]

ok if lazzy means 8 hrs of reading and similar time attempting the hack i will accept the opinion

so how do i write over the 3.1.5f kernel with the 3.1.5 kernel on the upgrade cd

for purposes of work ethic i have lloked for this for several hrs

thanks for the help

[cheer]

ok if lazzy means 8 hrs of reading and similar time attempting the hack i will accept the opinion If you think 8 hours is a lot of reading for Tivo hacking, you're wrong. I did about three to four weeks of reading (at least 4 hrs per day, and often more) before I attempted my first. No sympathy.
so how do i write over the 3.1.5f kernel with the 3.1.5 kernel on the upgrade cd I will give you the general steps.
Cable your Tivo hard drive up to your PC
Boot up off of the PTV Enhanced Boot CD
Mount the CD so you can access it ("mkdir /cdrom" "mount /dev/hd% /cdrom" -- replace "%" with the proper identifier for your cdrom drive)
Use bootpage to figure out which is your active boot and root ("bootpage -p /dev/hd#" -- replace "#" with the proper identifier for your Tivo hard drive) -- root will very likely be either 4 or 7, and the boot is one less (3 or 6)
Mount the root partition ("mkdir /tivo" "mount /dev/hd#@ /tivo" -- replace "#" with the identifier for your Tivo drive, and "@" with the number of the active root partition)
Make a directory on the Tivo drive to use as temporary space
Copy the kernel from the CD to your new temporary directory
Gunzip the kernel -- you should end up with a file called something like VMLINUX_
Use dd to copy the kernel to your boot partition. This is the most dangerous step, so be absolutely certain about everything before you proceed. Triple-check partition numbers and drive assignments. Make sure you understand what you've done in each step -- don't just blindly type things in. The command would be something like "dd if=/path/to/VMLINUX_ of=/dev/hd#&" -- replace "/path/to" with the actual path to the kernel that you gunzipped. If the filename is different, change that too. Replace "#" with the identifier for your Tivo drive and "&" with the number of the boot partition.And, believe it or not, all of that information is already here on the forum. Searching can be tricky on vbulletin until you get the hang of it. Always select Posts instead of Threads -- that helps a lot.

[xats3]

thanks a bunch
this worked well
however tcp/ip was only up temporarily thus could not telnet or ftp to hr10 250
looked at the drive
/dev/hdc7/ and rc.sysinit.author is gone as well as rc.sysinit
system was up and running with ability to record and view

will not be able to work on the drive due to vacation
thanks