From: Ludovic R. <lud...@gm...> - 2008-10-30 09:41:35
|
On Sun, Oct 19, 2008 at 2:06 PM, Ludovic Rousseau <lud...@gm...> wrote: > On Sun, Oct 19, 2008 at 12:16 PM, mike dentifrice <fl...@po...> wrote: >> Osamu Aoki a dit: >>> I am too lazy to compile kernel but Debian distributed compiled kernel >>> works now. >>> >>> 2.6.26-1-amd64 kernel packaged in >>> linux-image-2.6.26-1-amd64 package >> >> Unfortunately, it still doesn't work for me. >> >> I get a MMCONFIG message followed by an explicit Kernel Panic: unable to >> mount root VFS blah. > > I also got such an error. It was because the BIOS could not load the > initrd.img image. My linux partition is sda2 but it must be too big > (50 GB) and the new files are now created outside range for the BIOS. > > Using lilo I got such an error message. Using grub the message was > more explicit (but I do not remember the message error code). My problem was a bug in LILO. The kernel + initrd image for Linux >= 2.6.26 was too large. Adding the option "large-memory" in /etc/lilo.conf solved the problem. See Debian bug #479607 for example. The option "large-memory" is now set by default in new Debian lenny installations. > Try installing your vmlinuz and initrd.img file in a smaller > partition. Or on a USB memory or a CD. I could not make grub2 from an USB memory stick to work. The boot partition on the USB memory is seen by rEFIt but it looks like the firmware can't load it. Bye -- Dr. Ludovic Rousseau |