On Mon, Dec 12, 2005 at 10:26:16AM +0000, Ricardo Ferreira wrote: > I have the same problem. At first I thought it might be the way yaird was > generating the ram disk, so I tried using initramfs-tools instead. This did > not work (the error was about the same stated in other words in the boot > process). When I "dpkg -i" to the version that was previously working fine > (kernel version 2.6.14-4) I was surprised to find it had now the exact same > error. This probably means that it is not the kernel package's fault, but > something about the way the initrd is generated (although it is giving the > same problem with yaird and initramfs-tools). > > I repeat: The previously working fine kernel package > linux-image-2.6.14-2-686_2.6.14-4 is _not_ working now either after I rolled > back to it using "dpkg -i". > > On boot the system does give me a console when hitting the error so it lets > me manually load the modules. "modprobe ide-generic" and "modprobe ide-disk" > allows the system to boot just fine.
the debian kernel package has an patch that prevents udev from properly loading ide-generic. that patch is on the way to be removed. the ide-disk case needs to be looked into. anyway as short time workaround add -- /etc/mkinitramfs/modules ide-generic ide-disk -- and dpkg-reconfigure your linux-image. regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
