[Novalug] I NOW HAVE A WORKING INITRD IMAGE FILE

[Jay Hart]

The moral of Ken's story:  When Jay tells Ken he thinks the script has a bug,
Ken should listen to Jay.

Wow, what a couple of days.

Jay

> The moral of the story: Jay breaks machines - don't let him touch your box.
>
> :)
>
> K
>
> On Jan 14, 2008 8:33 PM, Jay Hart <jhart at kevla.org> wrote:
>
>> Just for shits and grins, i copied the mkinitrd script over from a
>> opensuse
>> 10.2 box to my broken 10.3 box, named it mkinitrd.102, put it in /sbin,
>> and
>> ran it.
>>
>> Version of mkinitrd from 10.2 box is 1.374, version from 10.3 box is 1.386
>> .
>>
>> Know what happened?????  Guess, no, really, take a guess!!!!
>>
>> It worked, it freaking worked, the whole time I've been up against a
>> script
>> error.
>>
>> It loaded a initrd file in /boot, setup the initrd link, and...
>>
>> I BOOTED UP.  Hell yes, I'm pumped.
>>
>> Now, only need to figure out why I only boot into runlevel 3...
>>
>> Oh, if someone wants to look at the diffs between the mkinitrd scripts,
>> I'll
>> post them to my website.
>>
>> EVERYONE, thanks for your help.
>>
>> Jay
>>
>> > That is a long shot.  Very long shot.  Very very long shot.  Incredibly
>> long
>> > shot.
>> >
>> > But hey -- if you can fix it, feel free to do so. :)
>> >
>> > K
>> >
>> > On Jan 14, 2008 7:14 PM, Jay Hart <jhart at kevla.org> wrote:
>> >
>> >> I know this might be a long-shot, but I have a feeling that the
>> mkinitrd
>> >> script has a bug.
>> >>
>> >> Jay
>> >>
>> >> > Interesting.  My man pages says otherwise.
>> >> >
>> >> > Ken
>> >> >
>> >> > On Jan 14, 2008 5:49 PM, Jay Hart <jhart at kevla.org> wrote:
>> >> >
>> >> >> Negative ghostrider...
>> >> >>
>> >> >> Jay
>> >> >>
>> >> >> > Perhaps the command has a verbose (-v) option you can leverage.
>> >> >> >
>> >> >> > K
>> >> >> >
>> >> >> > On Jan 14, 2008 4:58 PM, Jay Hart <jhart at kevla.org> wrote:
>> >> >> >
>> >> >> >> >
>> >> >> >> > Downloaded 2.6.17.8 kernel from
>> >> >> >> > www.kernel.org/pub/linux/kernel/v2.6/
>> >> >> >> > make oldconfig, then     set FDINITRD flag = 1
>> >> >> >> > in linux/arch/i386/boot/Makefile
>> >> >> >> > make clean; make ; make modules; make install; make
>> >> modules_install/
>> >> >> >> > NO INITRD!
>> >> >> >>
>> >> >> >> I'm repeating this process, with a new configuration file.
>> >> >> >>
>> >> >> >> I modified the FDINITRD param (set it to 1) in the Makefile prior
>> to
>> >> >> this.
>> >> >> >>
>> >> >> >> Let's see what happens...
>> >> >> >>
>> >> >> >> Jay
>> >> >> >>
>> >> >> >> > Downloaded 2.7.17.6 and repeated procedure.
>> >> >> >> > STILL NO INITRD!
>> >> >> >> >
>> >> >> >> > A simple mkinitrd from the command line makes all non-existing
>> >> >> initrds.
>> >> >> >> >
>> >> >> >> > ...
>> >> >> >> >
>> >> >> >> > Checked previous working disk - there is an initrd in /boot for
>> >> the
>> >> >> >> 2.6.17
>> >> >> >> > kernel.
>> >> >> >> > This is referenced by the menu.lst.
>> >> >> >> >
>> >> >> >> > mkinitrd -k /boot/vmlinuz-2.6.17.6-smp -i /boot/initrd-
>> >> 2.6.17.6-smp
>> >> >> >> > Creates new initrd in proper location!
>> >> >> >> > Edit /boot/grub/menu.lst to include the initrd file, and it
>> boots!
>> >> >> >> > There is joy in Mudville!
>> >> >> >> >
>> >> >> >> > The FDINITRD flag might help, but that's my best guess right
>> now.
>> >> >> >>
>> >> >> >>
>> >> >> >> _______________________________________________
>> >> >> >> Novalug mailing list
>> >> >> >> Novalug at calypso.tux.org
>> >> >> >> http://calypso.tux.org/cgi-bin/mailman/listinfo/novalug
>> >> >> >>
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >
>>
>>
>> _______________________________________________
>> Novalug mailing list
>> Novalug at calypso.tux.org
>> http://calypso.tux.org/cgi-bin/mailman/listinfo/novalug
>>
>