RE: (no subject)

Ellis:

I'm guessing that you compiled something the kernel needs to boot as a module 
but you didn't make the initrd.  Try this:

mkinitrd /boot/initrd-2.4.22.img 2.4.22

after you build the kernel (I'm assuming you built version 2.4.22, if not you 
just need to select the correct version).  This will build the 
initrd-version.img file which is a ramdisk image containing the modules.

Then modify the grub entry as :

title Red Hat Linux (2.4.22)
        root (hd0,0)
        kernel /vmlinuz-2.4.22 ro root=/dev/hda6 hdd=ide-scsi
        initrd /initrd-2.4.22.img

This example has the /boot partition on /dev/hda1 (partition 0 ide disk 0) and 
the / partition is /dev/hda6

>===== Original Message From "Ellis D. Cooper" <[email protected]> =====
>1.
> > reinvention, reengineering, mutation, and original design are all good
>things and easily accomplished when GPL'd
> > software is the basis.
>
>Biological evolution produces things that survive, not things that are
>necessarily "good". There are some pretty ugly animals out there. Just
>because someone designs something doesn't mean that it is well-designed,
>and if it becomes part of the system, it may eventually get fixed up, but
>if there is no standard of excellence, no schedule, and multiple
>duplication of effort you just end up with a leaderless bunch of hackers
>having fun.
>
>2. I am terrifically annoyed about the fact that I built a box just for
>Linux, installed Red Hat 8.0, can go online, etc. But I did this so I could
>learn about how the kernel works by playing around with it, so I have to be
>able to recompile it. So, I recompiled it, and the new entry appears in
>GRUB, but that just stalls with the message:
>
>"EXT2-fs warning (device ide0(3,1)): ext 2_read_super: mounting ext3
>filesystem as ext2
>VFS: Mounted root (ext2 system) read only.
>Freeing unused kernel memory: 108 k freed
>Warning: unable to open an initial console.
>Kernel panic: no init found. Try passing init= option to kernel."
>
>I have put this message to at least half a dozen "gurus" and "experts" and
>I have done grep and locate all over my system, trying to find out the
>exact cause (insofar as it can be determined) of this particular message.
>(I used grep
>because I thought I would try to find the sourcecode that produces the
>message.) Nobody seems to be able to tell me the exact meaning of this
>message, and the exact thing to do to get rid of it. I am not interested in
>going Debian or something else. I want to know what is going on from an
>authority who can explain every line of this message. Not being able to
>find an authority leaves me very annoyed.
>
>EDC
>
>
>_______________________________________________
>annoyances mailing list
>[email protected]
>http://michelangelo.renaissoft.com/mailman/listinfo/annoyances

Lawrence MacIntyre     865.574.8696     [email protected]
                Oak Ridge National Laboratory
High Performance Information Infrastructure Technology Group