[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel Panic après l'install du 2.4.24



Jean-Michel OLTRA wrote:
>>d'éditer le lilo.conf . Donc je boot sur ma disquelle qui contient le
>>2.4.18-bf4, et j'ajoute "initrd=/initrd.img" à la section
>>"image=/vmlinuz" de /etc/lilo.conf.
>>un petit
>>Pourriez vous m'indiquer ce j'ai loupé, et comment le corriger ?
> 
> Faut pas refaire l'initrd ?
> 

A en croire les messages lors de l'install (recopiés à la fin de ce msg)
je pensais que l'initrd était fait automatiquement lors de l'install et
que le lien avait été créé.

Voila ce que j'ai pu vérifier:
* J'ai bien le bon lien symbolique dans / :
lrwxrwxrwx 1 root root 31 Feb 12 10:39 initrd.img ->
boot/initrd.img-2.4.24-1-586tsc

* et initrd.img-2.4.24-1-586tsc est bien présent dans /boot :
-rw-r--r-- 1 root root 3567616 Feb 12 10:38 initrd.img-2.4.24-1-586tsc

Pourriez-vous m'indiquer plus précisement comment refaire son initrd
dans ce cas la, je n'ai pas trouvé de notice explicative qui détaille ce
cas de figure ...

Merci d'avance

Florent

Voici les messages lors de l'install:
--- Begin ---
You are attempting to install an initrd kernel image (version
2.4.24-1-586tsc)
This will not work unless you have configured your boot loader to use
initrd. (An initrd image is a kernel image that expects to use an INITial
Ram Disk to mount a minimal root file system into RAM and use that for
booting).

    As a reminder, in order to configure LILO, you need
    to add an 'initrd=/initrd.img' to the image=/vmlinuz
    stanza of your /etc/lilo.conf

I repeat, You need to configure your boot loader -- please read your
bootloader documentation for details on how to add initrd images.

If you have already done so, and you wish to get rid of this message,
please put
  `do_initrd = Yes'
in /etc/kernel-img.conf. Note that this is optional, but if you do not,
you'll continue to see this message whenever you install a kernel
image using initrd.
Do you want to stop now? [Y/n]n


/initrd.img does not exist. Installing from scratch, eh?
Or maybe you don't want a symbolic link here. Hmm? Lets See.
I notice that you do not have initrd.img symbolic
link. I can create one for you, and it shall be
updated by newer kernel image packages. This is
useful if you use a boot loader like lilo.
Do you want me to create a link from /boot/initrd.img-2.4.24-1-586tsc to
initrd.img?[Yn] Y
A new kernel image has been installed, and usually that means
that some action has to be taken to make sure that the new
kernel image is used next time the machine boots. Usually,
this entails running a ``bootloader'' like SILO, loadlin, LILO,
ELILO, QUIK, VMELILO, ZIPL, or booting from a floppy.   (Some
boot loader, like grub, for example, do not need to be run on
each new image install, so please ignore this if you are using
such a boot loader).

A new kernel image has been installed at /boot/vmlinuz-2.4.24-1-586tsc
 (Size: 807kB)


 Initial rootdisk image: /boot//initrd.img-2.4.24-1-586tsc (Size: 3484kB)

Symbolic links, unless otherwise specified, can be found in /

LILO sets up your system to boot Linux directly from your hard
disk, without the need for booting from a boot floppy.


WARNING
If you are keeping another operating system or another version
of Linux on a separate disk partition, you should not have LILO
install a boot block now. Wait until you read the LILO documentation.
That is because installing a boot block now might make the other
system un-bootable. If you only want to run this version of Linux,
go ahead and install the boot block here. If it does not work, you
can still boot this system from a boot floppy.

You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes]Yes




Reply to: