From: Justin M. <jus...@gm...> - 2008-10-19 19:17:07
|
On Sun, Oct 19, 2008 at 6:06 AM, 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). > > Try installing your vmlinuz and initrd.img file in a smaller > partition. Or on a USB memory or a CD. > > Bye > > -- > Dr. Ludovic Rousseau > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > Something must be wrong with there .config, or grub/ try grub2 using it over here, just grab it from debian sid, not intrepid due to a bug with intrepid(keyboard freeze); As for the disk, over here I'm using the entire disk.(120gig); heres my partition map: Device Boot Start End Blocks Id System /dev/sda1 * 1 14223 114238281+ 83 Linux /dev/sda2 14223 14594 2982509 82 Linux swap / Solaris As for mmconfig heres the thread: http://lkml.org/lkml/2008/7/16/190 I just use direct or the any option in the kernel .config you should be able to load the latest git with no problems. regards; -- Justin P. Mattock |