[plug] system hangs after kernel upgrade
Lance Duivenbode
lduivenb-mlist at iinet.net.au
Thu Jan 5 13:15:47 WST 2006
Oops! Yes - definitely make sure you run 'lilo' before rebooting. You
can tell I'm a GRUB user :)
Tomasz Grzegurzko wrote:
>Quoting Lance Duivenbode <lduivenb-mlist at iinet.net.au>:
>
>
>
>>Jon,
>>
>>I'm not sure about aptitude, but I know that when I upgrade machines
>>from a 2.4 kernel to a 2.6 kernel apt usually displays a message before
>>installing the image. This message states (and repeats) the need to
>>manually insert the 'initrd' parameter to your boot loader config and
>>requires you to enter 'Y' so you are you you want to proceed.
>>
>>For GRUB, all you need to add is the line:
>>
>>initrd /initrd.img
>>
>>to your /boot/grub/menu.lst file at the appropriate location (note that
>>it is '.lst' with a lowercase 'L' not the number '1').
>>
>>For LILO you need to add the line
>>
>>initrd = /initrd.img
>>
>>to your /etc/lilo.conf file at the appropriate location.
>>
>>
>
>And don't forget to re-run lilo!!!
>
># lilo -v
>
>Tomasz
>
>
>>Finally, note that Debian usually creates a symlink at /initrd.img to
>>the latest version of the init image. If you want to run multiple custom
>>kernels, then the above lines need to be changed to point to the correct
>>init file.
>>
>>Hope this helps,
>>Lance
>>
>>Jon Miller wrote:
>>
>>
>>
>>>Craig,
>>>So you are saying that using aptitude to install does not pass the initrd
>>>
>>>
>>command? Can you refresh my memory with either a document that describes
>>this or the command to be used as I've not done this before.
>>
>>
>>>Thanks
>>>
>>>Jon
>>>
>>>
>>>
>>>
>>>
>>>>>>craig at postnewspapers.com.au 1:35:29 am 5/01/2006 >>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>On Thu, Jan 05, 2006 at 03:21:38PM +0800, Jon Miller wrote:
>>>
>>>
>>>
>>>
>>>>I'm attempting to do an kernel upgrade from 2.4.27-2-686 to 2.6.8-2-686
>>>>
>>>>
>>and when the system boot it hangs at the prompt /sbin/init: 432: Connot open
>>dev/console No such file.
>>
>>
>>>>
>>>>
>>>>
>>>>
>>>Most likely you forgot to include the initrd on the boot command line.
>>>The initrd is required to set up udev, without which you won't get far.
>>>
>>>
>>>
>>>
>>>
>
>_______________________________________________
>PLUG discussion list: plug at plug.org.au
>http://www.plug.org.au/mailman/listinfo/plug
>Committee e-mail: committee at plug.linux.org.au
>
>
>
More information about the plug
mailing list