[lug] LILO and LIes

[John Starkey]

> > -rw-r--r--    1 root     root       461047 Jan 30 20:03 System.map
> [snip]
> > -rw-r--r--    1 root     root       438386 Jan 30 21:38 initrd-2.4.0.img
> [snip]
> > -rw-r--r--    1 root     root       995573 Jan 30 22:04 vmlinuz-2.4.0
> [snip]
> > lrwxrwxrwx    1 root     root           16 Jan 30 19:48 vmnew.img ->
> 
> This probably means nothing - but it looks like you did "make install"
> (install kernel and run lilo) after you created the initrd img.  Are you
> sure they're from the same compile?

The cron of this is:

1 make menuconfig
2 make dep
3 make
4 make bzImage
5 make modules
6 make modules_install
7 cp'd bzImage and System.map over
8 ln -s everything
9 mkinitrd
10 edit lilo.conf 
11 run lilo
12 repeat steps 10-11 (with variations) several times and reboot each tiem
13 hail mary :}

One wierd issue. I was using a symlink from System.map to the new one and
RH kept changing that symlink back to the 2.x kernel. That was freaky.

> so, after "make dep bzImage modules" you did:
> 
> make modules_install
> mkinitrd -f /boot/initrd-2.4.0.img 2.4.0
> make install

make install at the end? See above. I've done it like above everytime and
it worked. Is 2.4 different? Or doens't it matter. make install and mkinit
aren't related until reboot right?

> If after all that it didn't work, I guess I'd try compiling the
> necessary drivers into the kernel, rather than as modules, to see if it
> works if one totally skips the "initrd" bit.

K. Will do.

Thanks again,

John