killhdinitrd 0.9.x Support Thread

[w2kr]

My HD TiVo just upgraded to 3.1.5d breaking my ftp/telnet access of course. I still have the /var/hack stuff and I copied rc.sysinit.author and .profile over from the other partitions but killhdinitrd choked with unsupported kernel. Is there an upgrade comming up for killhdinitrd to allow 3.1.5d's kernel to be hacked ? (and maybe 4.01b?).

Thanks,
Peter

I believe I read in another post that you can use your 3.1.5c kernel that will hillhdinitrd'd with the 3.1.5d software.

[mrblack51]

I believe I read in another post that you can use your 3.1.5c kernel that will hillhdinitrd'd with the 3.1.5d software.

there is no such thing as 3.1.5c that i have ever seen in the wild. there is a 3.1.1c and a 3.1.0c, but not a 3.1.5c.

[shstevens]

My HD TiVo just upgraded to 3.1.5d breaking my ftp/telnet access of course. I still have the /var/hack stuff and I copied rc.sysinit.author and .profile over from the other partitions but killhdinitrd choked with unsupported kernel. Is there an upgrade comming up for killhdinitrd to allow 3.1.5d's kernel to be hacked ? (and maybe 4.01b?).

Thanks,
Peter

Read this post 14 Peter.
http://www.dealdatabase.com/forum/sh...0&postcount=14

Shawn

[w2kr]

there is no such thing as 3.1.5c that i have ever seen in the wild. there is a 3.1.1c and a 3.1.0c, but not a 3.1.5c.

Sorry, I thought the HD-TiVo has already running some version of a 3.1.5 release. I thought 3.1.5c had preceded 3.1.5d.

[mrblack51]

Sorry, I thought the HD-TiVo has already running some version of a 3.1.5 release. I thought 3.1.5c had preceded 3.1.5d.

hdtivos run 3.1.5-01-2 by default

[pbolya]

Read this post 14 Peter.
http://www.dealdatabase.com/forum/sh...0&postcount=14

Shawn

Thanks Shawn,
At the time when I wrote the letter I already copied everything over to the new partitions. All I needed was to hack the kernel. Since that failed I was just merely wondering if I should wait for a fix or should I try to copy the old kernel over and see what happens. I guess I got my answer.

It is too bad too because the new kernel speed my TiVo up a lot. I copied the old kernel over the new one and the TiVo is back to being slow again. Well... Better hacked than fast that is for sure.

By the way sorry for the cross posting I couldn't decide which one to post as it was not really a support question but more like an inquire about futute development. Also I was suprised that neither talked about 3.1.5d

Thanks,
Peter

[AbMagFab]

For anyone looking for the following kernels i have made them available via ftp. They are the stock tivo kernels (so hopefully tivo won't bother me as they are GPL).

Stock means orginal kernel off of the tivo image (no killhdinitrd - you need to do that yourselves)

3.1.1c
3.1.5
4.01a

Ftp - tivo.edidas.com
port:21
user:tivo
pass:tivo

max 10 connections at once.

Hey - the size of these files are smaller than 4MB (the partition size). How did you back them up? If the restore just a normal dd?

Thanks!

[mrblack51]

Hey - the size of these files are smaller than 4MB (the partition size). How did you back them up? If the restore just a normal dd?

Thanks!

all the tivo kernels i have seen should fit into a 2mb kernel partition. you should be able to use a normal dd, but limit the number of blocks so you get 2mb instead of the full 4mb.

[pbolya]

For anyone looking for the following kernels i have made them available via ftp. They are the stock tivo kernels (so hopefully tivo won't bother me as they are GPL).

Stock means orginal kernel off of the tivo image (no killhdinitrd - you need to do that yourselves)

3.1.1c
3.1.5
4.01a

Ftp - tivo.edidas.com
port:21
user:tivo
pass:tivo

max 10 connections at once.

Fletch319,
Thanks for the 4.0.1a kernel. I restored all my backups and looked at the other partitions of my 4.0.1b drive but that is also 4.0.1b so it helps me out a lot to get the 4.01a kernel from you. However I can not seem to find out why it does not work for me. I am sure that I am doing something horribly wrong (go easy on me). This is what I do:
- Backup current 4.0.1b SVR-3000 2 disk setup.
- Restore to a temp 160 GB as original 80 hours and validate it works by puting it into the tivo.
- Check boot kernel partition which is partition 3
- Copy the image to partition 3 with: dd if=/mnt/dos/vmlinux.px of=/dev/hdc3
- Validate that it boots in tivo: stuck in almost there.
- Restore and copy the image again and run killhdinitr /dev/hdc3 gives me:

Orig blocks = c83
Orig image size = 1907e0
Extended image size = 190fe0
Kernel + initrd = 190593
Kernel + initrd crc32 = e5067b1f
No exploit found

I also tried adding bs=4M conv=sync,notrunc etc I get the same result.

Could you or anybody else who had success loading these kernels give me a hand? I aprritiate it.

Thanks,
Peter

[Jamie]

Could you or anybody else who had success loading these kernels give me a hand? I aprritiate it.

I downloaded the 4.0.1a kernel and verified that killhdinitrd 0.9.2 works on it:

orig blocks = 00000c83
orig image size = 001907e0 (excludes header)
extended image size = 00190fe0
kernel+initrd length = 00190593 (excludes sig)
kernel+initrd crc32 = e5067b1f
identified kernel: 2.4.18 from TiVo OS 4.0.1a
new blocks = 00000c85
new image size = 00190be0 (excludes header)
Finished!

Our output from killhdinitrd looks similar, but is not identical. Are you using the 0.9.2 version of killhdinitrd? I don't think the earlier version supported this kernel.

I don't actually use that kernel. I boot a killhdinitrd'd 3.1.1c kernel, then monte into a homebuilt 2.4.18 kernel (built from 4.0 sources with lba48 and fpa patches).

[pbolya]

I downloaded the 4.0.1a kernel and verified that killhdinitrd 0.9.2 works on it:



Our output from killhdinitrd looks similar, but is not identical. Are you using the 0.9.2 version of killhdinitrd? I don't think the earlier version supported this kernel.

I don't actually use that kernel. I boot a killhdinitrd'd 3.1.1c kernel, then monte into a homebuilt 2.4.18 kernel (built from 4.0 sources with lba48 and fpa patches).

Wow,
I can not believe I just did that. Even though I downloaded the 0.9.2 I was following a how to thread and looks like that one has 0.9.1 linked. It worked for the HR10-250 but obviously does not work with the SVR-3000. I copied that one to the floppy and worked like a charm.

Thanks a lot,
Peter


PS. It was strange that the tivo did not load with the 4.0.1a until I run killhdinitr on it (I am sure this is normal it just threw me off track). By the way both versions of killhdinitrd says public beta 0.9.0 0.9.2 is just a little bit smaller.

[rc3105]

a killhdinitrd'd 3.1.1c kernel will boot any s2 short of the humax models, then you can monte into 3.1.5, 3.1.5d, 3.1.1d, 3.1.1e, 5.2, 5.2.1a, homebrew or <whatever floats your boat> kernel using a bogus rc.sysinit like this

[darylhuff]

I read all the advice on "enhancing" my dtivo box including waiting until after the initial phone call to start the upgrade process. This phone call updated the software release on my Hughes SD-DVR40 to 3.1.1d. When I try and run the latest killhdinitrd on this kernel (/dev/hda3 on my system) I get:

orig blocks = 00000db1
orig image size = 001b63e0 (excludes headers)
extended image size = 001b6be0
kernel+initrd length = 001b60ed (excludes sig)
kernel+initrd crc32 = 5ace553c
fatal: no exploit found for this kernel

I've also tried /dev/hd6, but from the partion map I'm pretty sure that 3 is the right one:

Partition map (with 512 byte blocks) on '/dev/hda'
#: type name length base ( size )
1: Apple_partition_map Apple 63 @ 1
2: Image Bootstrap 1 1 @ 75132992
3: Image Kernel 1 8192 @ 75132993 ( 4.0M)
4: Ext2 Root 1 262144 @ 75141185 (128.0M)
5: Image Bootstrap 2 4096 @ 75403329 ( 2.0M)
6: Image Kernel 2 4096 @ 75407425 ( 2.0M)
7: Ext2 Root 2 262144 @ 75411521 (128.0M)
8: Swap Linux swap 131072 @ 75673665 ( 4.0M)
9: Ext2 /var 262144 @ 75804737 (128.0M)
10: MFS MFS application region 1048576 @ 76066881 (512.0M)
11: MFS MFS media region 32142336 @ 42990656 ( 15.3G)
12: MFS Second MFS application region 1048576 @ 77115457 (512.0M)
13: MFS Second MFS media region 42990592 @ 64 ( 20.5G)
14: MFS New MFS Application 1024 @ 78164033
15: MFS New MFS Media 156270592 @ 78165057 ( 74.5G)
16: Apple_Free Extra 5999 @ 234435649 ( 2.9M)
Device block size=512, Number of Blocks=234441648 (111.8G)
DeviceType=0x0, DeviceId=0x0

I'm able to mount /dev/hda4 and that does look like my root. /dev/hda7 does not mount (see http://www.dealdatabase.com/forum/sh...t=37965&page=2) so I'm even more certain that /dev/hda3 is my active kernel.

Any idea when 3.1.1d will be supported by killhdinitrd?

[NutKase]

Why don't you just killhdinitrd a 3.1.1c kernel as stated in the post above and try it with no monte and see if it works.

If not you can always monte from 3.1.1c into 3.1.1d.


NutKase

[pbolya]

This phone call updated the software release on my Hughes SD-DVR40 to 3.1.1d. When I try and run the latest killhdinitrd on this kernel (/dev/hda3 on my system) I get:

I'm able to mount /dev/hda4 and that does look like my root. /dev/hda7 does not mount (see http://www.dealdatabase.com/forum/sh...t=37965&page=2) so I'm even more certain that /dev/hda3 is my active kernel.

Any idea when 3.1.1d will be supported by killhdinitrd?

If you used killhdinitrd before on your 3.1.1c than it is probably still sitting in /dev/hda6. Try :

dd if=/dev/hda6 of=/dev/hda3

This assumes that you had a 3.1.1c killhdinitrd'd kernel on hda6 and your new kernel in hda3.

If I where you I would put a dos disk in as hda-primary master and put your a drive to hdc-secondary master and back up the current kernel before you change anything with the following command:

mkdir /mnt/dos
mount /dev/hda1 /mnt/dos
dd if=/dev/hda3 of=/mnt/dos/tivokernel_3.1.1d.bak