From: Felipe S. <do...@gm...> - 2008-10-11 18:28:36
|
Hi I was just wondering if all the patches found here: http://mactel-linux.svn.sourceforge.net/svnroot/mactel-linux/trunk/kernel/mactel-patches-2.6.26/ have gone upstream into the new 2.6.27. -- Felipe Sere |
From: Sven A. <an...@an...> - 2008-10-13 19:23:26
|
Felipe Sere schrieb: > Hi > > I was just wondering if all the patches found here: > http://mactel-linux.svn.sourceforge.net/svnroot/mactel-linux/trunk/kernel/mactel-patches-2.6.26/ > have gone upstream into the new 2.6.27. Hi! Not all. These two patches didn't made it upstream. The input maintainer missed them... So here they are (again)... What about the other patches? Regards Sven -- Sven Anders <an...@an...> () Ascii Ribbon Campaign /\ Support plain text e-mail ANDURAS service solutions AG Innstraße 71 - 94036 Passau - Germany Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55 Rechtsform: Aktiengesellschaft - Sitz: Passau - Amtsgericht Passau HRB 6032 Mitglieder des Vorstands: Sven Anders, Marcus Junker Vorsitzender des Aufsichtsrats: Mark Peters |
From: mike d. <fl...@po...> - 2008-10-17 22:59:31
|
I am still unable to boot anything greater than 2.6.25.14 on my MacBook2,1. Kernel hangs on startup with the following two lines: Kernel alive. Kernel really alive. And then just stops (it used to say stuff about MMCONFIG with 2.6.26). Am I the only one who's stuck with this? -- mike dentifrice <fl...@po...> |
From: Osamu A. <os...@de...> - 2008-10-18 03:44:09
|
Hi, On Sat, Oct 18, 2008 at 12:33:33AM +0200, mike dentifrice wrote: > I am still unable to boot anything greater than 2.6.25.14 on my > MacBook2,1. > > Kernel hangs on startup with the following two lines: > > Kernel alive. > Kernel really alive. > > And then just stops (it used to say stuff about MMCONFIG with 2.6.26). > > Am I the only one who's stuck with this? 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 |
From: mike d. <fl...@po...> - 2008-10-19 10:16:12
|
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. -- mike dentifrice <fl...@po...> |
From: Sven A. <an...@an...> - 2008-10-19 11:27:50
|
mike dentifrice schrieb: > 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. Hello! This is my current config for 2.6.27 kernel. It's for an MacBookPro (2.Gen), so you have to adapt some drivers. Regards Sven -- Sven Anders <an...@an...> () Ascii Ribbon Campaign /\ Support plain text e-mail ANDURAS service solutions AG Innstraße 71 - 94036 Passau - Germany Web: www.anduras.de - Tel: +49 (0)851-4 90 50-0 - Fax: +49 (0)851-4 90 50-55 Rechtsform: Aktiengesellschaft - Sitz: Passau - Amtsgericht Passau HRB 6032 Mitglieder des Vorstands: Sven Anders, Marcus Junker Vorsitzender des Aufsichtsrats: Mark Peters |
From: Ludovic R. <lud...@gm...> - 2008-10-19 13:06:12
|
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 |
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 |
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 |
From: Ludovic R. <lud...@gm...> - 2008-10-30 17:33:23
|
On Thu, Oct 30, 2008 at 10:41 AM, Ludovic Rousseau <lud...@gm...> wrote: > 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. This change works when booting my Linux system from VMWare. Yes, you can boot a system from a real partition using VMWare. But the same problem is present if I boot from rEFIt. In this case I have to edit the file /etc/initramfs-tools/initramfs.conf to set MODULES=dep and regenerate the initrd.img file using: sudo update-initramfs -k 2.6.27-1-amd64 -u -v It looks like the BIOS provided by the iMac firmware is less "complete" than the BIOS provided by VMWare. Bye -- Dr. Ludovic Rousseau |
From: mike d. <fl...@po...> - 2009-09-07 17:54:58
|
I finally managed to boot a recent kernel on my MacBook2,1 (before that, I was stuck with 2.6.25.14 for ages). My problem happened to be lilo itself. The "large-memory" option did not help, and it was not until I replaced lilo with grub2 (using the 'grub-pc' Debian package) that I could boot something fresh (2.6.30). Though the thread is pretty old, I thought I'd share the enthusiasm, and mark the issue as closed. Ludovic Rousseau a dit: > 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 -- mike dentifrice <fl...@po...> |