a little help please

[dopelogic]

ok guys, let me start for apologizing for cluttering up the forum with a noob post. im having some trouble applying a killhdinitrd'd kernel to my drive.
my fat32 drive is hda drive letter G
my tivo drive is hdb
my active kernel is 3
i have a ptvupgrade disk with the killhdinitrd'd kernels on it.

so far i have tried to pull the file directly from the cd and apply it using:

zcat /cdrom/s2-kernels/4.0.1a/vmlinux.px.gz l dd of =/dev/hdb3

and by copying the file onto my g drive on my fat32 drive and then copying it over using:

mkdir /gdrive
mount -t vfat dev/hda1/gdrive
dd if=/gdrive/g/vmlinux.px of =/dev/hdb3

both of these result in the same:
l.gz: no such file or directory found
dd.gz no such file or directory found
of=/dev/hdb3.gz no such file or directory found

after examining the ptv cd via winrar i noticed that the path to the file was actually: S2_KERNE/4_0.1A/VMLINUX_.GZ/vmlinux.px

i tried to adjust the two above commands with the new path but the results were the same.

im an extreme noob to linux commands (only now starting to learn them)
if anyone could tell me where im messing up and mabey a short discription of why, i'd appreciate it. i really want to learn what some of these commands are and a basic knowledge of the structure of a linux system.
so far my knowledge is limited to l, zcat, dd, mount, unmount, and basic paths
thanks in advance for any help.

[mackaframa]

ok guys, let me start for apologizing for cluttering up the forum with a noob post. im having some trouble applying a killhdinitrd'd kernel to my drive.
my fat32 drive is hda drive letter G
my tivo drive is hdb
my active kernel is 3
i have a ptvupgrade disk with the killhdinitrd'd kernels on it.

so far i have tried to pull the file directly from the cd and apply it using:

zcat /cdrom/s2-kernels/4.0.1a/vmlinux.px.gz l dd of =/dev/hdb3

and by copying the file onto my g drive on my fat32 drive and then copying it over using:

mkdir /gdrive
mount -t vfat dev/hda1/gdrive
dd if=/gdrive/g/vmlinux.px of =/dev/hdb3

both of these result in the same:
l.gz: no such file or directory found
dd.gz no such file or directory found
of=/dev/hdb3.gz no such file or directory found


I think this may be part of your problem the command to mount the drive should look like this

mount -t /dev/hda /gdrive

I don't know that the drive letter of the fat32 drive is even relevant, it's not for me....the only thing that is needed to mount the drive is know which linux assigned "hdx" it is.

hda = primary master
hdb = primary slave
hdc = secondary master
hdd = secondary slave

in fact, I don't even know what the -t option does. I have used it only when mounting cd drives, and leave it off when mounting the fat32 drives

[PlainBill]

ok guys, let me start for apologizing for cluttering up the forum with a noob post. im having some trouble applying a killhdinitrd'd kernel to my drive.
my fat32 drive is hda drive letter G
my tivo drive is hdb
my active kernel is 3
i have a ptvupgrade disk with the killhdinitrd'd kernels on it.

so far i have tried to pull the file directly from the cd and apply it using:

zcat /cdrom/s2-kernels/4.0.1a/vmlinux.px.gz l dd of =/dev/hdb3

Try zcat -d /cdrom/s2-kernels/4.0.1a/vmlinux.px.gz | dd of =/dev/hdb3 Note that the character between the 'gz' and 'dd' is the pipeline symbol.

Do a little searching; I recall seeing this approach once.


and by copying the file onto my g drive on my fat32 drive and then copying it over using:

mkdir /gdrive
mount -t vfat dev/hda1/gdrive
dd if=/gdrive/g/vmlinux.px of =/dev/hdb3
Which partition is the FAT32 partition. USUALLY if it was the first partition on the primary master it would be drive C in DOS / Windows. Also, the mount command would be.
mount -t vfat dev/hda1 gdrive

ALSO I did not see you extracting the kernel.

Suggestion: Break it down into tiny steps.

Boot from the cd. Make the mount point and mount the FAT32 drive. Check it's directory {ls /gdrive}

Change to the proper directory on the cdrom, checking the directory each step of the way.

{cd /cdrom}
{ls}
{cd s2-kernels} (or whatever the exact directory is)

etc, etc.
Copy the kernel to the FAT32 drive

{cp vlinux.px.gz /gdrive}

Unpack it

{gzip -d vmlinux.px.gz}

copy it to the proper partition.

dd if=vmlinux.px of=/dev/hdb3 bs=1024

This way, when something goes wrong, you know where it was.


both of these result in the same:
l.gz: no such file or directory found
dd.gz no such file or directory found
of=/dev/hdb3.gz no such file or directory found

after examining the ptv cd via winrar i noticed that the path to the file was actually: S2_KERNE/4_0.1A/VMLINUX_.GZ/vmlinux.px

i tried to adjust the two above commands with the new path but the results were the same.

im an extreme noob to linux commands (only now starting to learn them)
if anyone could tell me where im messing up and mabey a short discription of why, i'd appreciate it. i really want to learn what some of these commands are and a basic knowledge of the structure of a linux system.
so far my knowledge is limited to l, zcat, dd, mount, unmount, and basic paths
thanks in advance for any help.

The idea is: Take baby steps until you are ready to run.

PlainBill

[ronrico51]

[QUOTE=dopelogic]

so far i have tried to pull the file directly from the cd and apply it using:

zcat /cdrom/s2-kernels/4.0.1a/vmlinux.px.gz l dd of =/dev/hdb3

QUOTE]

Not sure if you have a typo or not but it is "s2_kernels" not "s2-kernels" on the PTVUpgrade cd that I have.

Rick

[skcusdd]

ALSO I did not see you extracting the kernel.


zcat is cat with gunzip built in.

That is like doing cat file | gunzip | dd.

[dopelogic]

ok guys i will try your sugestions. unfourtunatlly i got called in to the office for a while so it will have to wait till i get home. i'll keep you updated. thanks agian.

[eastwind]

ok guys i will try your sugestions. unfourtunatlly i got called in to the office for a while so it will have to wait till i get home. i'll keep you updated. thanks agian.
Tell them to wait--that you're busy hacking your TiVo and you have to get it back up and running or you'll miss (whatever comes on Friday night). ;)
ew

[PlainBill]

Tell them to wait--that you're busy hacking your TiVo and you have to get it back up and running or you'll miss (whatever comes on Friday night). ;)
ew

This works quite well if you're the boss. Not so well when you're the top man on the 'call in an emergency' list.

PlainBill

[dopelogic]

plainbill,
i took your advice and i believe i have found the problem. when i go as far as to mount my fat32 drive then change the directory to my cd rom i get the no such file or directory error when i try to access my kernel. this leads me to believe that i have entered the path incorrectly. previously i have only checked the path by examining the file through winrar (c/ptvupgrade/S2_KERNE/4_0.1A/vmlinux.px). how would i determine what the path is on the cdrom via linux? i am almost certian this is my problem. if the path im entering is incorrect this will explain why my zcat command is not working either right? thanks,

[PlainBill]

plainbill,
i took your advice and i believe i have found the problem. when i go as far as to mount my fat32 drive then change the directory to my cd rom i get the no such file or directory error when i try to access my kernel. this leads me to believe that i have entered the path incorrectly. previously i have only checked the path by examining the file through winrar (c/ptvupgrade/S2_KERNE/4_0.1A/vmlinux.px). how would i determine what the path is on the cdrom via linux? i am almost certian this is my problem. if the path im entering is incorrect this will explain why my zcat command is not working either right? thanks,

Follow my directions in post #3 above, beginning with "break it down into tiny steps".

PlainBill

[dopelogic]

ok guys i read up some and i got a little further. i was able to extract and copy over my killhdinitrd kernel using:
zcat /cdrom/s2_kernels/4.0.1a/vmlinux.px.gz | dd of=/dev/hdc3

copied over 28 files

i then flipped the boot page using

bootpage -f -c /dev/hdc

then reset the boot parameters using

bootpage -P "root=/dev/hda3 upgradesoftware=false disscon=true console=2,115200" /dev/hdc

i got no errors so....

i popped the drive back in the tivo and checked my system settings but it still said that my software version was 4.0.1b.
the only difference i noticed is that now my hmo seems to be missing
(listed as inactive in the settings menu)

not sure what im missing here but id like to figure it out.

thanks,

[The Only Druid]

i popped the drive back in the tivo and checked my system settings but it still said that my software version was 4.0.1b.
the only difference i noticed is that now my hmo seems to be missing
(listed as inactive in the settings menu)

not sure what im missing here but id like to figure it out.

thanks,
I don't know how many times its been explained, but the kernel is NOT the same as the OS. The software version reported in the menus is the OS, not the kernel.

I'm beginning to think we should compile a list of posts mentioning these often-asked points, so that instead of just saying "search", we can show just precisely why we're tired of answering it.

[NutKase]

bootpage -P "root=/dev/hda3 upgradesoftware=false disscon=true console=2,115200" /dev/hdc

I got no errors so....

Well if you really received no errors when you typed the command above your tivo wouldn't be working. /dev/hda4 would be correct if your active kernel is in 3.

Accuracy is vital in this 'sport'. I hate to diss you but you've also entered 'dsscon=true' incorrectly.

You entered the above command while the drive was in your windows pc, and you received no errors because the command was never actually written to the drive because you didn't use the -C option to write it. Note the -C isn't required if you're updating your bootpage command while in the tivo through serial or telnet.


bootpage -P "root=/dev/hda4 upgradesoftware=false dsscon=true console=2,115200" -C /dev/hdc

This information is all over the place. You should spend your time reading and answering your questions by learning from others' posts instead of having me spend my time again typing an answer to your problem that I've probably typed for someone else.


I popped the drive back in the tivo and checked my system settings but it still said that my software version was 4.0.1b.

What software version did you expect? Please don't say 4.0.1a.


NutKase

[eastwind]

i then flipped the boot page using

bootpage -f -c /dev/hdc

then reset the boot parameters using

bootpage -P "root=/dev/hda3 upgradesoftware=false disscon=true console=2,115200" /dev/hdc


Unless you're using a different bootpage, the command you used won't write to the drive with a -C before the /dev/hdc. To verify:
bootpage -b /dev/hda ;tells you which boot partition will be used
bootpage -p /dev/hda ;tells you what the parameters are right now
bootpage -P .... ;lets you change the parameters.

Always check with -p after a -P to make sure you got what you want.

ew

[dopelogic]

ok guys sorry, i will read more. im trying here, really i am. i only became aware it was possible to hack a tivo about a week ago and my linux knowledge is limited to this experience alone. sorry if im asking questions that have been answered before but im really not even sure what questions i need to be asking let alone the answers im looking for, this makes using the search function a bit tricky. agian i apologize, i will read more......

[dopelogic]

ok so i cleaned up some commands and started over, but im still having trouble.
first i restored an image of my original drive via mfstools using:
mkdir /mnt/dos
mount /dev/hda1 /mnt/dos
mfsrestore -s 127 -bzpi /mnt/dos/tivo.bak /dev/hdc
unmounted the drive using
umount -f -a -r
then exited out of mfs tools, pulled the drive and placed it in the tivo for verification that the image is good. it was so i proceeded to boot up my ptvupgrade disc with the killhdinitrd kernels.

i then check my bootpage using
bootpage -p /dev/hdc
and find out my active root and kernel are 3/4

i then extract and copy my killhdinitrd kernel to the drive using
zcat /cdrom/s2_kernels/4.0.1a/vmlinux.px.gz | dd of=/dev/hdc3
i get conformation that this is done, so i move on to flipping the bootpage using
bootpage -f -C /dev/hdc
i get a conformation of this (says done) so i move on to reseting the boot parameters using
bootpage -P "root=/dev/hda4 upgradesoftware=false dsscon=true console=2,115200" -C /dev/hdc
i get a conformation that this is finished
then i check the bootpage agian via
bootpage -p /dev/hdc
and it shows up that the changes have written
i then exit out of the ptv cd and remove the drive and switch the jumper for testing
once the drive is in the tivo it goes to the welcome powering up screen then after a few moments the video reboots (screen goes black and a line goes from the top of the screen to the bottom) then the screen pops back up with the welcome powering up screen agian.

i appreciate any help here, im really trying to learn what im doing here but i know im missing something. i'd gladly do a search for the answers for these questions but as i stated above im not sure what my problems are. anyway if anyone could help me i would try to return the favor some how. thanks,

[dopelogic]

ok so after some more reading im starting to wonder if im really capable of doing this. i thought i had a pretty good idea of what was involved but.......
i have a basic understanding of the partition structure and how the tivo boots, 2 partition sets etc, etc, now i know that there is a difference between the software version and kernel version, but im still at a loss over alot of the other basic ideas behind this. from what i have read it looks like if i do get the killhdinitrd kernel to run, and get the bootpage set correctly, i will still need to edit an rcinitauthor file..... what makes my hacks run.... i dont even know what this is. and speaking of hacks i quess i need to make a directory off of the root for them to go in (dont know how to make a directory in linux) then make them executable via a chmod or something like that..... im really getting lost. this site is great for anyone looking for any detials on tivo hacking but for someone like me with no linux experience its not a great place for finding a basic understanding. i commend all of you that have gotten your systems hacked but this is taking over my life, (my live in girl friend is ready to throw the tivo and the computer out). i would love to do this but im in desperate need of some help or a basic overview of whats going on, on both the linux and tivo fronts. if anyone wants to trade info i am great at xbox, gcube, and playstation hacking and would be more than willing to help in anyway possible, i would even mod an xbox or gcube for someone if they would take the time to help me get through this. im not asking anyone to do it for me, but i need someone who can answer some basic questions for me (i suck and filtering info that ive searched for) all im really wanting to do is get ccxstream running on my tivo so i can view my recordings on an xbox or two in other rooms. guys im sorry for posting so much useless info in these forums but i am really asking for help. i have really tried and im getting really frustrated. i never claimed to be the brightest bulb on the tree but this is something i would really like to do. i've been working at it for about a week and a half now and i just dont know where to go from here.

[eastwind]

If you killed the boot3 and it was the active boot partition, why did you flip it?
How did you verify that 3 was the active? -p will not tell you this information.

ew

[PlainBill]

If you killed the boot3 and it was the active boot partition, why did you flip it?
How did you verify that 3 was the active? -p will not tell you this information.

ew

Yeeeh? Well, if he verified a newly restored image was working, I'll claim it's safe to assume the boot partition is one less that the root partition. Bootpage -p DOES report the root partition.

However, you have certainly identified the problem. I'm sure the cause of this is SOMEONES guide on removing TiVoScripts (aka Sleeper's iso). We really need a Newbie guide explaining how a TiVo boots normally, the partition setup, and how the old style Monte worked. Then maybe we could add a paragraph on killhdinitrd.

PlainBill

[ronrico51]

I have done all the steps you listed above in post #10 a number of times, works fine, except don't flip the bootpage. Why do you do this? Just restore the image, determine your boot/root partitions, and dd the kernel to the boot partition. Change your bootpage parameters just the way you did, and you should have a tivo ready for your hacks.

Rick

[eastwind]

Yeeeh? Well, if he verified a newly restored image was working, I'll claim it's safe to assume the boot partition is one less that the root partition. Bootpage -p DOES report the root partition.

However, you have certainly identified the problem. I'm sure the cause of this is SOMEONES guide on removing TiVoScripts (aka Sleeper's iso). We really need a Newbie guide explaining how a TiVo boots normally, the partition setup, and how the old style Monte worked. Then maybe we could add a paragraph on killhdinitrd.

PlainBill
I guess different versions of bootpage tell you different things. I can (sadly) say from experience that bootpage -P is not enough to change the boot partition. I've booted from hda3 with hda7 as my root partition...that's why I asked.

ew

[dopelogic]

ok guys, im not getting something.
after booting from my ptvupgrade disc, i enter the command:
bootpage -p /dev/hdc
and get a result of:
root=/dev/hd7
so do i need to killhdinitrd the kernel on hd6 or on hd3?
also, after i do that which do i need to change my boot parameters on.
thanks,

[PlainBill]

ok guys, im not getting something.
after booting from my ptvupgrade disc, i enter the command:
bootpage -p /dev/hdc
and get a result of:
root=/dev/hd7
so do i need to killhdinitrd the kernel on hd6 or on hd3?
also, after i do that which do i need to change my boot parameters on.
thanks,
Rant mode ON. dopelogic, this is not directed ONLY at you, but at everyone who is asking for help: Linux is very demanding; a -f in the wrong place can ruin your whole day. Adding or dropping a character can have a drastic change on the result. In the example above, it's a minor error - if the result is 'root=/dev/hd7', the system will not boot; I'm assuming this was a working drive, and the actual result was root=/dev/hda7. Rant mode OFF.

Dopelogic: Refer to this. (http://dealdatabase.com/forum/showpost.php?p=195432&postcount=4)

Apparently the drive was not hacked. 'bootpage -b /dev/hdc' will tell you which partition is the boot partition; UNLESS someone has been screwing with the drive, it will be 6 (the broken version of bootpage will return 7). Killhdinitrd the kernel on /dev/hdc6. The command to use to update the boot parameters is: bootpage -P "root=/dev/hda7 dsscon=true console=2,115200 upgradesoftware=false" -C /dev/hdc

PlainBill