Menu
▾
▴
mactel-linux-users
|
From: Tino K. <tin...@ti...> - 2010-03-17 20:44:20
|
Hi,
I tried to use grub-efi on my Mac mini Core 2 Duo (Macmini2,1). I can
get the kernel to start, but then the screen gets garbled and nothing
happens. I use a pretty standard 2.6.33 kernel with kernel mode setting
enabled. Grub2 is version 1.98.
Here is my grub.cfg file:
timeout=10
set F1=ctrl-x
menuentry "GNU/Linux" {
search --set -f /boot/default-kernel
linux /boot/default-kernel root=/dev/sda3 ro gpt i915.modeset=1
}
Does anyone have a working setup using grub-efi on similar hardware?
Regards,
Tino
|
|
From: Justin P. M. <jus...@gm...> - 2010-03-17 20:51:17
|
On 03/17/2010 01:28 PM, Tino Keitel wrote:
> Hi,
>
> I tried to use grub-efi on my Mac mini Core 2 Duo (Macmini2,1). I can
> get the kernel to start, but then the screen gets garbled and nothing
> happens. I use a pretty standard 2.6.33 kernel with kernel mode setting
> enabled. Grub2 is version 1.98.
>
> Here is my grub.cfg file:
>
> timeout=10
> set F1=ctrl-x
>
> menuentry "GNU/Linux" {
> search --set -f /boot/default-kernel
> linux /boot/default-kernel root=/dev/sda3 ro gpt i915.modeset=1
> }
>
> Does anyone have a working setup using grub-efi on similar hardware?
>
> Regards,
> Tino
>
> ------------------------------------------------------------------------------
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Mactel-linux-users mailing list
> Mac...@li...
> https://lists.sourceforge.net/lists/listinfo/mactel-linux-users
>
I never liked the whole grub-efi thing.
grub2 is o.k. but for some reason I always would see
a messed up screen on boot(from time to time).
lilo is the best from over here(easier to build, and use).
Justin P. Mattock
|
|
From: Tino K. <tin...@ti...> - 2010-03-17 20:57:11
|
On Wed, Mar 17, 2010 at 13:51:05 -0700, Justin P. Mattock wrote: [...] > I never liked the whole grub-efi thing. I never liked the whole legacy boot thing... :-) Regards, Tino |
|
From: Justin P. M. <jus...@gm...> - 2010-03-17 21:14:00
|
On 03/17/2010 01:56 PM, Tino Keitel wrote: > On Wed, Mar 17, 2010 at 13:51:05 -0700, Justin P. Mattock wrote: > > [...] > >> I never liked the whole grub-efi thing. > > I never liked the whole legacy boot thing... :-) > > Regards, > Tino > > refit is nice, this way you don't have to press option(legacy) every boot. Justin P. Mattock |
|
From: Tino K. <tin...@ti...> - 2010-03-17 21:53:01
|
On Wed, Mar 17, 2010 at 14:13:48 -0700, Justin P. Mattock wrote: [...] > refit is nice, this way you don't have to press option(legacy) every boot. I meant that messing around with MS-DOS partitions and the pretty long delay for legacy boot. Regards, Tino |
|
From: cyberdork33 <cyb...@gm...> - 2010-03-17 22:32:04
|
Delay ? I've never had a delay. Ricky On Mar 17, 2010, at 4:52 PM, Tino Keitel <tin...@ti... > wrote: > On Wed, Mar 17, 2010 at 14:13:48 -0700, Justin P. Mattock wrote: > > [...] > >> refit is nice, this way you don't have to press option(legacy) >> every boot. > > I meant that messing around with MS-DOS partitions and the pretty long > delay for legacy boot. > > Regards, > Tino > > --- > --- > --- > --------------------------------------------------------------------- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users |
|
From: Andy B. <an...@an...> - 2010-03-19 09:40:28
|
> I meant that messing around with MS-DOS partitions and the pretty long > delay for legacy boot. This annoyed me too on my Mac Mini, until I found this: http://ubuntuforums.org/showpost.php?p=5166788&postcount=21 Quote: How to single boot Linux without delay on Mac --------------------------------------------------------- 1. If you have OSX installed, boot to it and mute sound. This assures that you won't be annoyed by the startup/poweron sound afterwards. I even used This software to be absolutely sure. Restart to confirm that no startup sound is audible. 2. Prepare rEFIt boot disk (CD-RW). 3. Boot Ubuntu install and remove all partitions, partition as you like for your Linux installation. Install Ubuntu, restart. 4. Put in rEFIt CD and holding down alt key, boot rEFIT cd. Synchronize GUID and MBR. Restart. 5. Insert OSX disc, boot from it, open terminal and enter following: bless --device /dev/disk0s2 --setBoot --legacy --verbose where /dev/disk0s2 is the partition you installed grub (do 'diskutil list' to find out correct partition). Of course, '--verbose' is optional. This makes Macbook EFI firmware boot your Linux installation in legacy mode without long delay (20s vs 3s). 6. Restart your Macbook (don't forget to remove OSX disc). And boot directly to Linux! Hope this helps :) |
|
From: Justin P. m. <jus...@gm...> - 2010-03-19 13:34:00
|
On 03/19/2010 02:11 AM, Andy Botting wrote: >> I meant that messing around with MS-DOS partitions and the pretty long >> delay for legacy boot. > > This annoyed me too on my Mac Mini, until I found this: > http://ubuntuforums.org/showpost.php?p=5166788&postcount=21 > > Quote: > > How to single boot Linux without delay on Mac > --------------------------------------------------------- > > 1. If you have OSX installed, boot to it and mute sound. This assures > that you won't be annoyed by the startup/poweron sound afterwards. I > even used This software to be absolutely sure. > Restart to confirm that no startup sound is audible. > > 2. Prepare rEFIt boot disk (CD-RW). > > 3. Boot Ubuntu install and remove all partitions, partition as you > like for your Linux installation. Install Ubuntu, restart. > > 4. Put in rEFIt CD and holding down alt key, boot rEFIT cd. > Synchronize GUID and MBR. Restart. > > 5. Insert OSX disc, boot from it, open terminal and enter following: > bless --device /dev/disk0s2 --setBoot --legacy --verbose > where /dev/disk0s2 is the partition you installed grub (do 'diskutil > list' to find out correct partition). Of course, '--verbose' is > optional. > > This makes Macbook EFI firmware boot your Linux installation in legacy > mode without long delay (20s vs 3s). > > 6. Restart your Macbook (don't forget to remove OSX disc). And boot > directly to Linux! > > > Hope this helps :) > > nice!! I do see a delay, but am not bothered by it. Justin P. Mattock |
|
From: Sam N. <sa...@th...> - 2010-03-19 16:03:14
|
On Fri, 2010-03-19 at 20:11 +1100, Andy Botting wrote: > 5. Insert OSX disc, boot from it, open terminal and enter following: > bless --device /dev/disk0s2 --setBoot --legacy --verbose > where /dev/disk0s2 is the partition you installed grub (do 'diskutil > list' to find out correct partition). Of course, '--verbose' is > optional. Whoa! way back in 2007-2008 I spent a lot of time trying to figure out a way that I could run bless without installing OSX. http://sourceforge.net/mailarchive/forum.php?thread_name=1202414009.5266.38.camel@isaac.localdomain&forum_name=mactel-linux-users Does this really work knoppix style like that? Will it work with my circa 2007 OSX disc? -- GPG key F343E5FC (fingerprint:DF37 93BC AFEC 0A6A CC08 4A95 3790 8B4C F343 E5FC) available at: http://www.thepromisedlan.org/sam_noble.gpg.asc |
|
From: Tino K. <tin...@ti...> - 2010-03-21 22:42:07
|
On Fri, Mar 19, 2010 at 20:11:08 +1100, Andy Botting wrote: > > I meant that messing around with MS-DOS partitions and the pretty long > > delay for legacy boot. > > This annoyed me too on my Mac Mini, until I found this: > http://ubuntuforums.org/showpost.php?p=5166788&postcount=21 > > Quote: > > How to single boot Linux without delay on Mac > --------------------------------------------------------- > > 1. If you have OSX installed, boot to it and mute sound. This assures > that you won't be annoyed by the startup/poweron sound afterwards. I > even used This software to be absolutely sure. > Restart to confirm that no startup sound is audible. > > 2. Prepare rEFIt boot disk (CD-RW). > > 3. Boot Ubuntu install and remove all partitions, partition as you > like for your Linux installation. Install Ubuntu, restart. > > 4. Put in rEFIt CD and holding down alt key, boot rEFIT cd. > Synchronize GUID and MBR. Restart. > > 5. Insert OSX disc, boot from it, open terminal and enter following: > bless --device /dev/disk0s2 --setBoot --legacy --verbose > where /dev/disk0s2 is the partition you installed grub (do 'diskutil > list' to find out correct partition). Of course, '--verbose' is > optional. > > This makes Macbook EFI firmware boot your Linux installation in legacy > mode without long delay (20s vs 3s). > > 6. Restart your Macbook (don't forget to remove OSX disc). And boot > directly to Linux! > > > Hope this helps :) Not really, as I want to keep the OS X installation. Furthermore, gptsync was causing trouble the last time I used it. The 4th partition with my LVM was gone after this, because gptsync inserted a dummy partition before the EFI partition. I had to use fdisk to recover it. So gptsync is marked as "unreliable" for me, which is another reason why I want to switch from grub-pc to grub-efi. Regards, Tino |
|
From: Stefan M. <mo...@ir...> - 2010-03-25 13:54:55
|
> I tried to use grub-efi on my Mac mini Core 2 Duo (Macmini2,1). I can
> get the kernel to start, but then the screen gets garbled and nothing
> happens. I use a pretty standard 2.6.33 kernel with kernel mode setting
> enabled. Grub2 is version 1.98.
> Here is my grub.cfg file:
> timeout=10
> set F1=ctrl-x
> menuentry "GNU/Linux" {
> search --set -f /boot/default-kernel
> linux /boot/default-kernel root=/dev/sda3 ro gpt i915.modeset=1
> }
> Does anyone have a working setup using grub-efi on similar hardware?
[ Looks like people are too busy explaining why you shouldn't use
grub-efi to actually answer your question. ]
The problem may simply be that the `intel' Xorg driver relies on the
BIOS of your video card, which is usually initialized by the legacy BIOS
but is not initialized by the normal EFI boot.
Checkout http://grub.enbug.org/TestingOnMacbook where they provide some
steps that may be helpful to fix your problem (e.g. how to tell EFI to
initialize the video BIOS).
Stefan
|
|
From: Tino K. <tin...@ti...> - 2010-03-25 18:13:31
|
On Thu, Mar 25, 2010 at 09:54:25 -0400, Stefan Monnier wrote: [...] > [ Looks like people are too busy explaining why you shouldn't use > grub-efi to actually answer your question. ] Yeah, strange. > The problem may simply be that the `intel' Xorg driver relies on the > BIOS of your video card, which is usually initialized by the legacy BIOS > but is not initialized by the normal EFI boot. As the graphics is now handled by the kernel if KMS is used, this dependency moved from the Xorg driver to the kernel, too. > Checkout http://grub.enbug.org/TestingOnMacbook where they provide some > steps that may be helpful to fix your problem (e.g. how to tell EFI to > initialize the video BIOS). Thanks. I already looked over the page, but missed the important bit. Now I can start the kernel, and get video output. However, I get a panic when the root partition should be mounted, because the SATA disk is not detected. At least there are no messages regarding sda. The DVD drive is detected, though. Any further hints are appreciated. Regards, Tino |
|
From: mike d. <fl...@po...> - 2010-05-14 08:07:46
|
Justin P. Mattock a dit: > Hmm.. Thought grub2 needs to be compiled with efi support or > something. > (standard x86_32 build over here) Yes. You need to either compile grub2 with '--with-platform=efi' or use the grub-efi package if you're using Debian or Ubuntu. See instructions on http://grub.enbug.org/TestingOnEFI and more Macintosh related details on http://grub.enbug.org/TestingOnMacbook. > If this then is not the case, then(probably) my machine needs to > have the framebuffer address added to efifb.c It would sure be nice to know (and possibly get it fixed upstream). I'm assuming your machine has 64bit EFI (my Macbook2,1 and Tino's MacMini use 32bit EFI, AFAIK). >From what I read over threads [1], while success has been reached with some 32bit Macs (especially those with intel graphics), a lot remains to be done of the more recent Macs so they can boot EFI alright (the latest models partly implementing UEFI, I think). 1. see http://ubuntuforums.org/showthread.php?t=995704 (beware, it's _very_ long, hence hard to read... -- mike dentifrice <fl...@po...> |
|
From: Justin P. M. <jus...@gm...> - 2010-05-14 08:44:15
|
On 05/14/10 01:07, mike dentifrice wrote: > Justin P. Mattock a dit: >> Hmm.. Thought grub2 needs to be compiled with efi support or >> something. >> (standard x86_32 build over here) > > Yes. You need to either compile grub2 with '--with-platform=efi' or use > the grub-efi package if you're using Debian or Ubuntu. See instructions > on http://grub.enbug.org/TestingOnEFI and more Macintosh related details > on http://grub.enbug.org/TestingOnMacbook. > >> If this then is not the case, then(probably) my machine needs to >> have the framebuffer address added to efifb.c > > It would sure be nice to know (and possibly get it fixed upstream). I'm > assuming your machine has 64bit EFI (my Macbook2,1 and Tino's MacMini > use 32bit EFI, AFAIK). > >> From what I read over threads [1], while success has been reached with > some 32bit Macs (especially those with intel graphics), a lot remains to > be done of the more recent Macs so they can boot EFI alright (the latest > models partly implementing UEFI, I think). > > 1. see http://ubuntuforums.org/showthread.php?t=995704 (beware, it's > _very_ long, hence hard to read... > ah.. yep I haven't yet compiled grub2 with efi, (maybe)causing the stuckage with efifb, but then again I tried with nvidiafb, and hit the same green colored stuckage(but could be wrong), leading me to believe just a simple adding of an address but then again In any case I'll try to work this.. (be nice to get some patches sent upstream for this area). Justin P. Mattock |
|
From: Tino K. <tin...@ti...> - 2010-03-25 20:48:51
|
On Thu, Mar 25, 2010 at 19:13:15 +0100, Tino Keitel wrote: [...] > Thanks. I already looked over the page, but missed the important bit. > Now I can start the kernel, and get video output. However, I get a > panic when the root partition should be mounted, because the SATA disk > is not detected. At least there are no messages regarding sda. The > DVD drive is detected, though. > > Any further hints are appreciated. To answer myself: when booting with EFI, CONFIG_SATA_AHCI needs to be enabled in the kernel. CONFIG_ATA_PIIX doesn't work. Now I can boot my Linux using grub-efi. Everything seems to work, including X. Regards, Tino |
|
From: mike d. <fl...@po...> - 2010-05-13 12:06:13
|
Tino Keitel a dit: > To answer myself: when booting with EFI, CONFIG_SATA_AHCI needs to be > enabled in the kernel. CONFIG_ATA_PIIX doesn't work. Now I can boot > my Linux using grub-efi. Everything seems to work, including X. Thanks for sharing that with us. Booting my MacBook2,1 with grub-efi had been on my TODO list for a while (especially since it seems to be the only way to boot from a USB stick, and to allow grub to see and therefore access anything else than the internal hard-disk). So, I finally found a bit of time to try it, and successfully booted Debian with grub-efi installed on a USB stick (using 'fix_video' and 'fakebios' in the grub menu entry) while retaining grub-pc on the hard-disk for now. So far, everything seems to be working : efifb provides a nice textmode console, and X.org using the 'intel' driver runs seemingly just as fast as when legacy booted (judging by the output of glxgears). However, a few questions remain for me: - what are the actual advantages and drawbacks from booting in EFI on such a platform? - where is it best to put the grub.efi EFI application? is it advised to have it sit on the first EFI system partition, within the EFI folder? - if not, where? Cheers, -- mike dentifrice <fl...@po...> |
|
From: Tino K. <tin...@ti...> - 2010-05-13 12:39:37
|
On Thu, May 13, 2010 at 14:05:54 +0200, mike dentifrice wrote: [...] > > So far, everything seems to be working : efifb provides a nice > textmode console, and X.org using the 'intel' driver runs seemingly > just as fast as when legacy booted (judging by the output of > glxgears). I didn't try efifb. I just use the DRM framebuffer along with kernel mode setting, which is also used by the native Intel driver in Xorg. > However, a few questions remain for me: > - what are the actual advantages and drawbacks from booting in EFI on > such a platform? You don't have to mess around with gptsync, which is limited to 4 partitions. And in my setup, it created a dummy partition before the EFI partition, lowering the limit to 3. Also, there is no delay at boot time which is caused by the legacy BIOS. > - where is it best to put the grub.efi EFI application? is it advised to > have it sit on the first EFI system partition, within the EFI folder? > - if not, where? I created a small HFS+ partition only for grub. It has no journal, so I can also write it in Linux to update grub or modify grub.cfg. Regards, Tino |
|
From: mike d. <fl...@po...> - 2010-05-14 08:20:36
|
Tino Keitel a dit: > I didn't try efifb. I just use the DRM framebuffer along with kernel > mode setting, which is also used by the native Intel driver in Xorg. Oh, I'm gonna give that a try then. > > However, a few questions remain for me: - what are the actual > > advantages and drawbacks from booting in EFI on such a platform? > > You don't have to mess around with gptsync, which is limited to 4 > partitions. And in my setup, it created a dummy partition before the > EFI partition, lowering the limit to 3. Also, there is no delay at > boot time which is caused by the legacy BIOS. Right. The partition limit is not a big deal for me, and I don't mind about the faster bootup procedure, but is there another obvious benefit, or any drawback for that matter? > > - where is it best to put the grub.efi EFI application? is it > > advised to have it sit on the first EFI system partition, within the > > EFI folder? - if not, where? > > I created a small HFS+ partition only for grub. It has no journal, so > I can also write it in Linux to update grub or modify grub.cfg. Ok. So - what is the EFI system partition for? Seemed like a good place to put EFI applications, but when I mount it under Debian, it shows empty, while there's an EFI folder in it when I mount it under MacOS X. Any eplanation for that? Cheers, -- mike dentifrice <fl...@po...> |
|
From: Justin P. M. <jus...@gm...> - 2010-05-13 14:08:22
|
On 05/13/10 05:21, Tino Keitel wrote: > On Thu, May 13, 2010 at 14:05:54 +0200, mike dentifrice wrote: > > [...] > >> >> So far, everything seems to be working : efifb provides a nice >> textmode console, and X.org using the 'intel' driver runs seemingly >> just as fast as when legacy booted (judging by the output of >> glxgears). > > I didn't try efifb. I just use the DRM framebuffer along with kernel > mode setting, which is also used by the native Intel driver in Xorg. > >> However, a few questions remain for me: >> - what are the actual advantages and drawbacks from booting in EFI on >> such a platform? > > You don't have to mess around with gptsync, which is limited to 4 > partitions. And in my setup, it created a dummy partition before the > EFI partition, lowering the limit to 3. Also, there is no delay at > boot time which is caused by the legacy BIOS. > >> - where is it best to put the grub.efi EFI application? is it advised to >> have it sit on the first EFI system partition, within the EFI folder? >> - if not, where? > > I created a small HFS+ partition only for grub. It has no journal, so I > can also write it in Linux to update grub or modify grub.cfg. > > Regards, > Tino > > ------------------------------------------------------------------------------ > > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users > Cool.. was looking into using efifb on the iMac9,1 but had no luck. Either my grub2 needed to be built with efi support and/or I needed to add the device address to efifb.c What/where are the instructions? I'd like to see if either it's a simple configuration and/or if a patch needs to be created for efifb.c and pushed upstream for these devices(only a few in there I see now). Justin P. Mattock |
|
From: Tino K. <tin...@ti...> - 2010-05-13 15:51:34
|
On Thu, May 13, 2010 at 07:08:09 -0700, Justin P. Mattock wrote: [...] > > Cool.. was looking into using efifb on > the iMac9,1 but had no luck. Either > my grub2 needed to be built with > efi support and/or I needed to add the device > address to efifb.c > > What/where are the instructions? Instructions for what? I just boot an unpatched kernel which uses kernel mode setting for intel graphics. However, I needed to include this to my grub.cfg: search --set -f /boot/vbios.bin insmod loadbios loadbios /boot/vbios.bin /boot/int10.bin Regards, Tino |
|
From: mike d. <fl...@po...> - 2010-05-14 08:14:24
|
Tino Keitel a dit:
> Instructions for what? I just boot an unpatched kernel which uses
> kernel mode setting for intel graphics. However, I needed to include
> this to my grub.cfg:
>
> search --set -f /boot/vbios.bin
> insmod loadbios
> loadbios /boot/vbios.bin /boot/int10.bin
Here goes the grub config for my MacBook2,1. I tried to use the BIOS
dumps, but it wouldn't work, and it turns out I don't need them to boot,
since 'fakebios' is sufficient:
menuentry "Debian Squeeze" {
fix_video
fakebios
linux /vmlinuz root=/dev/sda4 video=efifb
initrd /initrd.img
}
AFAIK, fix_video is only used to fix the grambled screen during the boot
sequence, and is not necessary if you don't care about the text console.
--
mike dentifrice <fl...@po...>
|
|
From: Justin P. M. <jus...@gm...> - 2010-05-13 16:33:44
|
> > Hmm.. Thought grub2 needs to be compiled with efi support or > something. (standard x86_32 build over here) If this then is not the case, then(probably) my machine needs to have the framebuffer address added to efifb.c Thanks for the info, Ill have a look, and see.(BTW:threads proably all crapped out cause I don't know how to send from a phone); Justin P. Mattock On May 13, 2010, at 8:51 AM, Tino Keitel <tin...@ti... > wrote: > On Thu, May 13, 2010 at 07:08:09 -0700, Justin P. Mattock wrote: > > [...] >> >> Cool.. was looking into using efifb on >> the iMac9,1 but had no luck. Either >> my grub2 needed to be built with >> efi support and/or I needed to add the device >> address to efifb.c >> >> What/where are the instructions? > > Instructions for what? I just boot an unpatched kernel which uses > kernel mode setting for intel graphics. However, I needed to include > this to my grub.cfg: > > search --set -f /boot/vbios.bin > insmod loadbios > loadbios /boot/vbios.bin /boot/int10.bin > > Regards, > Tino > > --- > --- > --- > --------------------------------------------------------------------- > > _______________________________________________ > Mactel-linux-users mailing list > Mac...@li... > https://lists.sourceforge.net/lists/listinfo/mactel-linux-users |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X