On Fri, Feb 20, 2009 at 07:40:45PM -0000, Manuel Siggen wrote:
> No more luck here : I just installed the 138-1 version and the boot
> sequence still doesn't ask for the passphrase.
After installing the new version of udev, you will also need to update your
initramfs (sudo update-initramfs -u -k 2.6.28-8-generic).
> Also, until now I could easily fall back to an old kernel (2.6.28-5) and
> continue to use my machine without much trouble. But with the 138-1
> version, the udevd daemon eats 40-50% CPU continuously (the disk LED
> blinks but no disk activity can be heard), and the whole machine is
> quite unstable (fortunately, the consoles still work). Is it possible
> that a mismatch between kernel and udev causes this problem ?
That sounds like quite another matter; I'll defer to Scott here.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>
On Fri, Feb 20, 2009 at 07:40:45PM -0000, Manuel Siggen wrote:
> No more luck here : I just installed the 138-1 version and the boot
> sequence still doesn't ask for the passphrase.
After installing the new version of udev, you will also need to update your
initramfs (sudo update-initramfs -u -k 2.6.28-8-generic).
> Also, until now I could easily fall back to an old kernel (2.6.28-5) and
> continue to use my machine without much trouble. But with the 138-1
> version, the udevd daemon eats 40-50% CPU continuously (the disk LED
> blinks but no disk activity can be heard), and the whole machine is
> quite unstable (fortunately, the consoles still work). Is it possible
> that a mismatch between kernel and udev causes this problem ?
That sounds like quite another matter; I'll defer to Scott here.
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>