Boot after kernel recompile

Andre Costa acosta at ar.microlink.com.br
Sun Sep 5 12:38:22 UTC 2004


Hi Juan,

On Sun, 05 Sep 2004 12:53:21 +0200
"Juan L. Pastor" <seguridadlinux at yahoo.es> wrote:

> On Sun, 2004-09-05 at 09:47, James Wilkinson wrote:
> 
> > Juan L. Pastor asked:
> > > Where does the /boot/initrd-2.6.6-1.435.2.3custom.img file and the
> > > line initrd /initrd-2.6.6-1.435.2.3custom.img
> > > enter in this story? Are they not supposed to make the translation
> > > of the label name into the real filesystem?
> > 
> > They're made by mkinitrd.
> > 
> > As the name suggests, they need to be custom-made for the kernel
> > you're running. Is that really the kernel you're running? (Any
> > reason why you're not on 2.8.1?) Otherwise they won't work...
> 
> [jlpastor at kalimotxo jlpastor]$ ll /boot/
> total 5304
> -rw-r--r--  1 root root   46375 May  8 15:21 config-2.6.5-1.358
> drwxr-xr-x  2 root root    1024 Aug 31 09:19 grub
> -rw-r--r--  1 root root  289645 Aug 22 20:08 initrd-2.6.5-1.358.img
> -rw-r--r--  1 root root  197261 Aug 31 09:19
> initrd-2.6.6-1.435.2.3custom.img
> drwx------  2 root root   12288 Aug 22 22:06 lost+found
> lrwxrwxrwx  1 root root      32 Aug 31 09:19 System.map ->
> System.map-2.6.6-1.435.2.3custom
> -rw-r--r--  1 root root  239593 May  8 15:21 System.map-2.6.5-1.358
> -rw-r--r--  1 root root  702528 Aug 31 09:19
> System.map-2.6.6-1.435.2.3custom
> -rw-r--r--  1 root root  658171 Aug 25 09:07
> System.map-2.6.6-1.435.2.3custom.old
> lrwxrwxrwx  1 root root      29 Aug 31 09:19 vmlinuz ->
> vmlinuz-2.6.6-1.435.2.3custom
> -rw-r--r--  1 root root 1199031 May  8 15:21 vmlinuz-2.6.5-1.358
> -rw-r--r--  1 root root 1065172 Aug 31 09:19
> vmlinuz-2.6.6-1.435.2.3custom
> -rw-r--r--  1 root root  984930 Aug 25 09:07
> vmlinuz-2.6.6-1.435.2.3custom.old
> [jlpastor at kalimotxo jlpastor]$ uname -a
> Linux kalimotxo.euskal.net 2.6.6-1.435.2.3custom #1 Tue Aug 31
> 08:50:03 CEST 2004 i686 athlon i386 GNU/Linux
> 
> They were created when I recompiled the kernel, that's why I don't
> understand that it doesn't translate the LABEL=/ into /dev/hdc2, like
> 2.6.5-1.358 kernel.
> 
> I'm not working with 2.8.1 kernel yet because I didn't have time to
> download it.

I've been bitten by this in the past, too -- back on the (not too
distant) 2.4.x days. On my case, enabling RAM disk support for my
custom kernel allowed LABELs to be properly understood (I've been doing
it this way since then). My bet is that it would help you too. WARNING:
you might need to compile it as a built-in feature, and not as a module

HTH

Andre

-- 
Andre Oliveira da Costa





More information about the fedora-list mailing list