killhdinitrd 0.9.x Support Thread

[alldeadhomiez]

This is all i get via serial. I'm not that familiar with bash over serial so maybe i'm not getting all the info. basically this is a freshly restored image (bootpage is not altered at all). All i did was run the killhdinitrd (which worked) and stick the drive in the tivo. If this isn't all the info do i need to add any other lines to the boot params? I seem to recall a few other entries in there dsscon, upgradesoftware etc.

What PROM version are you running?

I suspect the unaligned load from -2464($gp) = -2464 + 0x4a224051 could be raising an exception:

    80179d24:   54296234        bnel    at,t1,0x801925f8
    80179d28:   9f89f660        lwu     t1,-2464(gp)

Maybe $gp's contents vary from one PROM version to the next, or are based on other factors.

According to your register dump, $s6 is word-aligned and apparently points into the shadowed PROM image (harmless to overwrite), so you might want to try entry_addr_new 0x80173240, bootstrap_addr 0x80192660:

    80173240:   10637d07        beq     v1,v1,0x80192660
    80173244:   f6cb72ce        sdc1    $f11,29390(s6)

[Fletch319]

What PROM version are you running?

I suspect the unaligned load from -2464($gp) = -2464 + 0x4a224051 could be raising an exception:

    80179d24:   54296234        bnel    at,t1,0x801925f8
    80179d28:   9f89f660        lwu     t1,-2464(gp)

Maybe $gp's contents vary from one PROM version to the next, or are based on other factors.

According to your register dump, $s6 is word-aligned and apparently points into the shadowed PROM image (harmless to overwrite), so you might want to try entry_addr_new 0x80173240, bootstrap_addr 0x80192660:

    80173240:   10637d07        beq     v1,v1,0x80192660
    80173244:   f6cb72ce        sdc1    $f11,29390(s6)

I'm not don't know a whole lot about the prom so i'm not sure how to get the version etc... MuscleNerd talked about the prom password. how does one enable a password so you can see the beginning part of the boot process as he described?

I can give the new "entry_addr_new" idea a shot but only if someone posts a recompiled test version. I don't currently have a way to build my own mips binaries. Maybe this will finally motivate me to setup a permanent linux machine so i can build my own binaries

[RKone]

This is all i get via serial.

My 4.0 kernel raises nearly the same error, the only difference is my badaddr=fdfbe65f.

My PROM is 1.18.

[nsysblh]

I've been experimenting trying to get monte to load a second kernel on the heels of the 3.1.1c kernel by putting some commands in /test.conf to read the new kernel out of the root filesystem.

Important saftety tip: Don't use a kernel as the input to monte that has been touched by killhdinitrd. It is not enough to use the -R to reverse it. You gotta go back to an original kernel. Riley expressed this warning before. Just thought I'd confirm that it won't work. Nothing weird happens, it just does a boot using the stuff in the bootpage instead of the monte parms. I'm assuming it does a real reset instead of passing control the the loaded kernel.

Now I'm off to trash it with a lba48 kernel.

I originally wanted to find an original 3.1.5 kernel. Since the entry point to get a copy is $999, and no one seems to post those things anymore, I'm just going to go with one of the non-signed ones.

[RKone]

My 4.0 kernel raises nearly the same error, the only difference is my badaddr=fdfbe65f.

With ADH's new entry/bootstrap addresses, I get this:

general exception
cause = 9000802c epc = 80173240 status  = 00510002 badaddr = 10003410
@epc-2 = 59fa8522 @epc-1 = 5f4bcdc8 @epc = 10637d07 @epc+1 = f6cb72ce
r00 00000000  81dd0000  80173240  000000ea
r04 81dd1f34  00000cea  5469566f  81dbfdd0
r08 0000004d  80004000  00000000  81dbe858
r12 81dbe708  fffffffc  2b797e9c  00000000
r16 00000cea  81dbfdc8  81dd1f34  00000000
r20 00000064  81dbfe28  81dbfdc8  00000000
r24 e61c0bce  00000001  bfc00000  a1fe0000
r28 80cec000  81dbfb90  fffbffff  81dc1308

[alldeadhomiez]

With ADH's new entry/bootstrap addresses, I get this:

general exception
cause = 9000802c epc = 80173240 status  = 00510002 badaddr = 10003410
@epc-2 = 59fa8522 @epc-1 = 5f4bcdc8 @epc = 10637d07 @epc+1 = f6cb72ce
r00 00000000  81dd0000  80173240  000000ea
r04 81dd1f34  00000cea  5469566f  81dbfdd0
r08 0000004d  80004000  00000000  81dbe858
r12 81dbe708  fffffffc  2b797e9c  00000000
r16 00000cea  81dbfdc8  81dd1f34  00000000
r20 00000064  81dbfe28  81dbfdc8  00000000
r24 e61c0bce  00000001  bfc00000  a1fe0000
r28 80cec000  81dbfb90  fffbffff  81dc1308

cause is 9000802c = 10010000000000001000000000101100

According to the vr5432 manual on tivoutils, part 1, pdf page 121, code 0xb means "coprocessor unusable exception." The error on the original 2.4.18/4.0 code was "address error on load or fetch." Obviously we are having these problems because there is no way to avoid executing the (junk) instruction in the branch delay slot.

Can anyone else think of a way to jump past the end of the signature in some 4.x series kernel?

[Fletch319]

Due to the nature of the work being discussed not to mention 3 different conversations mixed all together I would like to humbly suggest the 4.0 kernel stuff be moved over tot he development thread. The support thread just doesn't seem to be the right place for discussing kernel patching considering it's over the top of 99% of most people's head here (or just mine

[phil1995]

I have sucessfully upgraded my disk to a 200 Gig. I am no looking to add the hacks. It is my understanding that I should use the Killhiinitrd software instead of the Monte. Where do I obtain the software, and where do I find a list of commands I must run on the Tivo after the hard drive has been re-installed post Killhinitrd.

Thanks, any help you could give me would be greatly appreciated.

[arob]

It can be found here:

http://www.dealdatabase.com/forum/sh...ad.php?t=36692

[phil1995]

Thanks, I now have the killhdinitrd0.9.0 software but am still uncertain as to how to use it. It is my understanding that I need to boot my system with a 3.1.5 kernel.

Can someone lead me to some instructions on how to proceed from this point. I am mainly looking to get Telnet and FTP working. Does this procedure load the FTP and Telnet files and other hacks like the monte, or do I use the monte in conjunction with this somehow?

Any help would be greatly appreciated.

[lenroc]

Uh, no... no extra programs are installed. You'll need to copy them onto the drive yourself. It's really trivial.

Nothing is installed automatically with a "monte" either. The only way that hacks are automatically installed is with Sleeper's TivoScripts...

[psxboy]

Yeah... you've got a lot of work ahead of you. The ONLY thing that the killhdinitrd program does is keep the Tivo from deleting any "unauthorized" software at boot time. The rest is up to you... ie. installing the telnet & ftp daemons, disabling encryption, Tivoweb, mfs-ftp, etc. etc.

You might want to take apart Sleeper's Tivoscripts ISO and see what it installs in order to get an idea of what you need/want to install on your box. Other than that, you just need to start reading through the various threads on this forum and go from there.

-psxboy

[arob]

PtvUpgrade.com is promising an announcement soon that will make doing this easy, probably booting a cd and following instructions. They'll probably bundle it with the sale of a USB adapter and/or drive upgrade kit. Not sure when soon is but I'm not brave enough and rich enough to screw up my HR10 so I'm waiting. In the meantime I'm reading all I can..

[patriot]

Has anyone taken Sleeper's Tivoscripts ISO apart yet and revamped it?

I am looking at the one I have v1.02 and not being a linux expert, I would need help as to what file is the one that runs all the options on the cd. How I could replace the killinitrd with the current killhdinitrd.

btw, is the default harddrive option (Backup Original Tivo Drive to C Drive) on sleepers iso ok to use to backup my current HD Tivo Harddrive to a 40GB FAT Harddrive? My HD Tivo has only booted once just to see that it worked. There are no shows recorded on it.

patriot

[whackit]

okay... I'm a noob again. forgive me. trying to get this working on my hdr10-250. I have read as much as I can and now I'm into the beer so it looks as though my evening is done. Here is my process, if anyone could please enlighten me as to what I may have ommitted/done incorrectly i would be in your debt.

1. backup and test original drive.

2. install killhdinitrd, dialogue suggests succesful install

3. create rc.sysinit.author in /etc/rc.d asuming I need only do this on 1 partition since it is a backup restore (7 in my case). Cannot access the second partion (specify filesystem).

4. write rc.sysinit.author file as follows:

#! /bin/bash

#install usb and ethernet drives for Linksys USB200M
insmod /lib/modules/usbcore.o
insmod /lib/modules/hcd.o
insmod /lib/modules/ehci-hcd.o
insmod /lib/modules/ax8817x.o

#configure ethernet
ifconfig eth0 192.168.0.199 broadcast 192.168.0.255 netmask 255.255.255.0

#telnet
tnlited 23 /bin/bash -login &

#ftp
/var/hack/tivoftpd.mips

5. make rc.sysinit.author executable.

6. create hack dir on Partition 9

7. copy tivoftpd.mips and make executable.

8. reinstall drive and reboot tivo.

No lights on Linksys USB200M, no ping, no telnet. I pulled drive and checked everything out again. It had switched the active partition. Interesting but not sure what to make of that.

I'm a bit lost and a bit tired, as always, any help is greatly appreciated.