All of lore.kernel.org
 help / color / mirror / Atom feed
From: Isaac Dupree <id@isaac.cedarswampstudios.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: macbook EFI experiences
Date: Fri, 30 May 2008 17:01:51 -0400	[thread overview]
Message-ID: <48406B3F.1070704@isaac.cedarswampstudios.org> (raw)
In-Reply-To: <20080530192626.GA29768@thorin>

Robert Millan wrote:
> On Fri, May 30, 2008 at 12:29:59PM -0400, Isaac Dupree wrote:
>> It's fixed now for my hardware, Intel's new video driver in Xorg 7.3 
>> doesn't need any BIOS hacks or anything, I believe.  Anyway, I'll find 
>> out if it works just as soon as I manage to actually get into 
>> linux-kernel under EFI, so *if* it doesn't break, then I can keep using 
>> that and avoid (1) the unnecessary and potentially buggy CSM, (2) the 
>> hassles of installing a pc-bios-style bootloader on the header of one of 
>> my partitions. (and (3) be able to report bugs (in whatever software is 
>> affected) that happen later on when doing it that way.)  It can't hurt 
>> to try...
> 
> You don't need to use the header of one of your partitions.  You can use
> the MBR or even have a dedicated partition for core.img.  Then you can install
> the rest of GRUB in a filesystem that's not case unsensitive! ;-P

I know, but I don't entirely understand how it works and I'd rather 
not... and it gives me limited options: theoretical maximum of 5 I 
think, 1 in MBR and 1 in each of first four partitions (each with their 
own hacks).  I much prefer being able to put as many .efi files as fit 
all on one partition, for refit to find.  As it is, when I upgrade GRUB, 
there always has to be the fear that I did something wrong that I can't 
easily fix because it's not just in the location of my files (it's 
hidden in mbr/partition headers), and because I can't boot into Linux 
anymore because I broke the bootloader :-)  It's been very lucky that I 
can so far always boot into OS X without going through GRUB, and edit my 
grub.cfg from there... That, and keeping 10.4 updated, are the two main 
reasons I ever boot into MacOS :-)

> Btw what's a CSM?

"Compatibility Support Modules", it's a name for the BIOS substitute 
that Apple added to EFI to support their "Boot Camp"/Windows.


Looking at the page http://refit.sourceforge.net/myths/ "Fact: You need 
BIOS compatibility for 2D/3D accelleration" (which hasn't been updated 
for a long time...) it looks like if I want the console (rather than X) 
to display anything, I'll still need video BIOS... good to know when 
testing to see if anything works




  reply	other threads:[~2008-05-30 21:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 14:42 macbook EFI experiences Isaac Dupree
2008-05-30 15:18 ` Robert Millan
2008-05-30 16:06   ` Isaac Dupree
2008-05-30 16:17     ` Bean
2008-05-30 16:29       ` Isaac Dupree
2008-05-30 19:26         ` Robert Millan
2008-05-30 21:01           ` Isaac Dupree [this message]
2008-05-31  9:35             ` Robert Millan
2008-05-31  9:41               ` rename partmap/pc.c? (Re: macbook EFI experiences) Robert Millan
2008-05-31 17:13                 ` Pavel Roskin
2008-06-01 10:23                   ` Robert Millan
2008-06-01 17:44                     ` Pavel Roskin
2008-05-31 18:57               ` macbook EFI experiences Isaac Dupree
2008-05-31 19:26                 ` Robert Millan
2008-05-31 19:52                   ` Bean
2008-05-31 21:10                     ` Robert Millan
2008-05-31 21:46                   ` Isaac Dupree
2008-06-03  6:06                     ` Bean
2008-06-03 16:28                       ` Isaac Dupree
2008-06-03 18:28                         ` Bean
2008-06-04 11:01                           ` Isaac Dupree
2008-06-04 11:08                             ` Bean
2008-06-04 11:27                               ` Isaac Dupree
2008-06-04 11:35                                 ` Bean
2008-06-04 13:03                                   ` Isaac Dupree

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=48406B3F.1070704@isaac.cedarswampstudios.org \
    --to=id@isaac.cedarswampstudios.org \
    --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.