Re: How to boot machine with newly installed kernel using presseed.cfg
On Fri, 13 Aug 2010 10:37:04 -0400 (EDT), Jordan Metzmeier wrote:
> On 08/13/2010 09:47 AM, Stephen Powell wrote:
>>
>> I seem to recall seeing something on the lists about an incompatibility between
>> the 2.6.32 kernel used by Squeeze and the version of udev which runs on Lenny.
>> I assume that the same incompatibility exists with the 2.6.33 kernel. If you
>> need a 2.6.33 kernel, I suggest you install Squeeze rather than Lenny.
>
> This is backwards. The udev in squeeze requires a newer kernel with
> CONFIG_SYSFS_DEPRECATED=n . The squeeze kernel works fine in lenny, and
> is even available in Lenny backports. You just can not go the other way
> around (Lenny kernel on a squeeze machine).
>
> The .32 kernel is also available in the kmuto Lenny installer.
Thanks for setting me straight, Jordan. That's what I get for going from
memory instead of bothering to look it up.
As for the OP, please provide more information, such as:
(1) Where did you get your 2.6.33 kernel? Backports? Experimental?
Custom built? etc. How did you install it?
(2) What bootloader do you use? grub? (version 1) grub-pc (version 2),
lilo? extlinux? etc.
(3) What is the contents of /etc/kernel-img.conf?
(4) What is the contents of your boot loader configuration file?
(/etc/lilo.conf for lilo, /boot/grub/menu.lst for grub version 1,
etc.)
(5) What scripts exist in /etc/kernel/postinst.d, /etc/kernel/postrm.d,
and /etc/initramfs/post-update.d?
(6) Are symbolic links used for the kernel, such as vmlinuz,
and vmlinuz.old? And what about the initial RAM file systems?
Are symbolic links used for them too? (initrd.img, initrd.img.old)
If so, where are these symbolic links? (/, /boot, etc.)
(7) What exactly are the symptoms of failure when you attempt to
boot the 2.6.33 kernel?
--
.''`. Stephen Powell
: :' :
`. `'`
`-
Reply to: