All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Jarvis <James.Jarvis@ed.ac.uk>
To: grub-devel@gnu.org
Subject: grub2 and fat efi files on latest Apples
Date: Wed, 13 May 2009 16:35:26 +0100	[thread overview]
Message-ID: <4A0AE8BE.9010103@ed.ac.uk> (raw)

Newbie post but hopefully I will be providing some useful data rather 
than merely questions...

I have been using the svn trunk over the last few days with some success 
compiling 32 and 64 bit EFI grub and creating a dual architecture 
grub.efi from the results that seems to work on hard disk on newer and 
older Apple Intel Macs. I use the fatglue.py python script from refit to 
make the fat grub.efi. Not sure if anyone else is doing anything similar...

I have observed that fat modules don't work - need to use grub-mkimage 
to insert all the required modules.

Another interesting observation (not really grub but maybe worth 
comment) is that using a Linux 2.6.29.2 kernel and initrd on the newer 
macs in efi mode boot (uses framebuffer console) works up until the 
insertion of modules. It appears that some modules do insert and other 
don't. The same kernel and initrd booted in "legacy mode" (after a call 
to fakebios) boots fine.

Finally, the reboot call from linux on the iMac 9,1 hangs - possibly an 
issue with fakebios??? If the output of grub-dumpbios is any use let me 
know...

Models tested (all intel)

macmini
iMac 4,1 requires ia32 or "fat"  grub.efi
iMac 8,1 requires x86_64 or "fat"  grub.efi
iMac 9,1 requires x86_64 or "fat"  grub.efi

James








-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.




             reply	other threads:[~2009-05-13 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 15:35 James Jarvis [this message]
2009-05-14  4:31 ` grub2 and fat efi files on latest Apples Peter Cros
2009-05-14  5:37   ` James Jarvis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A0AE8BE.9010103@ed.ac.uk \
    --to=james.jarvis@ed.ac.uk \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.