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

Re: Kernel upgrade problem and question about "apt-get install kernel-image..."

On Wednesday 28 April 2004 08:55, Adam Funk wrote:
> I'm running Debian testing on an Athlon 1100 box, and currently using
> the kernel-image-2.4.23-1-386 package successfully.
> I just upgraded with "apt-get install kernel-image-2.4.25-1-386" and
> ended up with an unbootable system from that kernel: it got stuck doing
> "hda: lost interrupt" messages (the same problem I had when I
> ignorantly tried to run the 686 kernel on the Athlon 1100).  So my
> first question is: shouldn't the 2.4.25 386 kernel run on this
> processor?
I would think so, but you'll have to ask someone more guru than me to find 
out for sure.
> Fortunately the backup kernel worked because the apt-get install rotated
> the 2.4.23 kernel into the /vmlinuz.old and /initrd.img.old symlinks.
> I would now like to try the kernel-image-2.4.25-1-k7 package (which I
> believe is the optimum kernel for my CPU) but I'm concerned about what
> will happen during the rotation.  If I apt-get install a third kernel
> package, will the first one (2.4.23) still remain in /boot?  If so,
> should I just add a 3rd stanza to my /etc/lilo.conf for this kernel?
> The file currently looks like this:
> boot=/dev/hda
> prompt
> timeout=100
> root=/dev/hda1
> install=/boot/boot.b
> map=/boot/map
> vga=0x317
> default=Linux
> image=/vmlinuz
>         label=Linux
>         initrd=/initrd.img
>         append="devfs=mount hdd=ide-scsi"
> image=/vmlinuz.old
>         label=LinuxOLD
>         initrd=/initrd.img.old
>         append="devfs=mount hdd=ide-scsi"
>         optional
> So would I just add this:
> image=/boot/vmlinuz-2.4.23-1-386
>         label=Linux-2.4.23-1-386
>         initrd=/boot/initrd.img-2.4.23-1-386
>         append="devfs=mount hdd=ide-scsi"
>         optional
> to ensure that I've always got one good kernel?  I strongly suspect this
> will work, but I'd appreciate some advice/encouragement so I don't get
> stuck.
> Thanks,
> Adam

Your changes look fine.  Just remember to run /sbin/lilo after you make the 
changes, and you're good to go.

Justin Guerin

Reply to: