PDA

View Full Version : Need Clarification



NMVD
10-14-2003, 09:18 AM
HDVR2 120GB 3.1.0-01-2-151

Thanks to logandros I have been up and running for almost 6 months. I have been thinking about doing the Monte hack so I can use the newest software as it becomes available.

After starting to read Cobelli's Guide I have become totally confused on the Monte hack. In the introduction it states you need the bashable software 3.1.u5 and to download the newest software 3.1.0-01-2-151 which is what I'm using.

So now I'm lost. ((Since I'm already running 3.1.0-01-2-151))

Is 3.1.0-01-2-151 the newest software?

Did logandros and his method do the same as monte (I don't think so because I still use hackinit to load all my hacks and I'm not booting additional kernels)?

Did logandros figure out a new way to hack the unit without doing a monte or a prom hack (if so why did he never post it)?

Someone please point out at what point I'm totally missing the bus!

NMVD

mrblack51
10-14-2003, 11:03 AM
the newest software is 3.1.1b for the s2 dtivos, 3.1.0b for the s1 dtivos. 3.1.u5 and 3.1.0 on the s2 dtivos are identical except for the kernel image (well, actually just the initrd). many people have been monte'ing into 3.1.0 for a while to prevent their units from trying to upgrade every night.

NMVD
10-14-2003, 12:14 PM
Ok well that clears it up a little, hopefully my question now is a little more structered.

If I'm to understand you correctly:

Why are people using 3.1.u5(bashable) to load 3.1.151(bashable)? What would be the sense of using the monte method for that? I would think that you would use 3.1.u5(bashable) to load 3.1.1b(non-bashable). I know this is a stupid question since no one else is asking it. Which means I'm missing something obvious. Can you please point out what I'm misunderstanding?

Thank you

Juppers
10-14-2003, 12:35 PM
3.1.u5 is the only bashable kernel. The differences between it and 3.1 are just some kernel edits to stop bashenv from working. Using a u5 kernel, with the 3.1 filespace works fine. Now that 3.1.1b is here though, the U5 kernel may not work with the 3.1.1b userspace. Specifically, the U5 kernel initrd will most likely delete a few key apps that have been bugfixed, giving you an unusable unit. Luckily, people had the foresight to see that eventually an update would come down, and something more future proof was needed. This brings us to monte. Using the U5 kernel, you chain load a netuered 3.1.1b or 3.1 kernel image that has its initrd altered. The bios is happy, because the U5 kernel passes the signature check, and with your altered 3.1 or 3.1.1b initrd, you can be free to change the filespace as you wish. I think this should explain everything well enough.

NMVD
10-14-2003, 03:47 PM
"3.1.u5 is the only bashable kernel."

That is the part that is throwing me .. somehow logandros is bashing 3.1.0-01-2-151.

I have no clue how he did it .. but if I can give anyone any info from my tivo that will shed any light on whats actually allowing me to do this, Id be happy to!

And there is no way that any monte trick is being used here.

ronnythunder
10-14-2003, 03:53 PM
you can do a prom (hardware) hack that lets you run whatever you want. the u5 kernel *is* the only one that's "bash-able", however.

ronny

NMVD
10-14-2003, 05:08 PM
There is no prom mod on my HDVR2. I can dump whatever information you need to help either prove or find why my unit is bashable with 151.

David Bought
10-14-2003, 05:28 PM
Originally posted by NMVD
There is no prom mod on my HDVR2. I can dump whatever information you need to help either prove or find why my unit is bashable with 151.

151 is not a valid version number. All HDVR2 software releases end in -151.

As mrblack51 pointed out, the 3.1.0 kernel image is identical to the 3.1u5 kernel image with the exception of the initrd. Since the inird does not affect the unit's operation, the 3.1.0 software will run correctly with a 3.1u5 kernel image and no monte.

NMVD
10-14-2003, 05:32 PM
Yet .. and again


I am not using monte nor am I using a hacked prom. And the version Im running (again) is 3.1.0-01-2-151. I'm not trying to say I figured out something new. I'm trying to figure out how/why I'm running this. Or why my unit (may) be running 3.1u5 but displays on the system information screen 3.1.0-01-2-151.

David Bought
10-14-2003, 06:03 PM
Originally posted by NMVD
Yet .. and again


I am not using monte nor am I using a hacked prom. And the version Im running (again) is 3.1.0-01-2-151. I'm not trying to say I figured out something new. I'm trying to figure out how/why I'm running this. Or why my unit (may) be running 3.1u5 but displays on the system information screen 3.1.0-01-2-151.

I just answered your question. In fact it has been answered about 4 different ways in this thread. Even Juppers answered your question. You're running the 3.1.0 userland software (hda4/hda7) with the 3.1u5 kernel image (hda3/hda6). Simple. The only tricky part is that the initrd might be checking an extra copy of the 3.1u5 root partition, but that isn't strictly necessary on 3.1.0 so it was probably omitted.

NMVD
10-14-2003, 08:35 PM
OK, thanks ... it just sounded so much like I was doing a monte the way you guys were explaining it .. I think I got it now ..

Thanks

I would take offense to your attitude David Butt but the more I read you seem to not be able to get along with anyone ,, so no offense taken here

:D