Re: kernel updates - was: adding a kernel from backports
I attempted to upgrade my live system (persistent), including a kernel upgrade. I
got basically the same message as what's shown below. Note that I'm not attempting
to use a kernel from backports.org this time, but a standard Debian kernel.
What's the proper way to handle this?
-Rob
On Fri, Nov 06, 2009 at 08:56:35PM -0500, Rob Owens wrote:
> In order to get a wireless card working, I need to install a kernel from
> lenny backports. I get this message:
>
> You are attempting to install an initrd kernel image (version ↑
> 2.6.30-bpo.2-486). This will not work unless the boot loader is
> configured to use an 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.
> The boot loader must be configured to use such images and the
> system ▒
> will not boot until this is done.
> ▒
> This message will appear for any new kernel installation unless the
> following is added to /etc/kernel-img.conf:
>
> "do_initrd = Yes"
>
>
> Is there any reason not to do this on a live system? I ask because my
> /etc/kernel-img.conf file is empty on my live system, while my Lenny
> system installed on a hard disk has this in /etc/kernel-img.conf:
>
> do_symlinks = yes
> relative_links = yes
> do_bootloader = no
> do_bootfloppy = no
> do_initrd = yes
> link_in_boot = no
> postinst_hook = update-grub
> postrm_hook = update-grub
>
> By the way, I'm using syslinux as my bootloader.
>
> -Rob
>
>
> --
> To UNSUBSCRIBE, email to debian-live-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: