All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Javier Martín" <lordhabbit@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub-efi x86_64 on macbook air?
Date: Wed, 28 Jan 2009 17:56:43 +0100	[thread overview]
Message-ID: <1233161803.1302.5.camel@localhost> (raw)
In-Reply-To: <acc911d90901280842i517a218ds82c555e5922ac28d@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3847 bytes --]

El mié, 28-01-2009 a las 17:42 +0100, step21 escribió:
> Hey, while investigating possibilities on how it might be possible to
> install/run something "wubi" like on macs (without having windows
> installed) I ran into a couple of issues. I post here mainly in hope
> that one of the folks that actually wrote the code for this or at
> least have experience with it read this, cause most ppl on irc (while
> being very helpful) seem to know more about the pure x86/bios/linux
> side of things.
> 
> Besides some (minor?) issues like that the command line
> freezes/becomes unresponsive after a (relatively short) amount of time
> and the fact that booting back to OS X (which everyone says should
> work 100%) does not work at all (it complains that it can't find the
> specified os x *efi, but it is there, and search correctly finds the
> right drive) my biggest problem right now is the following:
> 
> I got some kerne/initrd combo to boot (2.6.26 from debian lenny
> netinstall iirc) but it gets to the language selection screen, first
> thing you notice, the keyboard is dead. I supplied "init=/bin/sh" to
> be able to read at least the last of the error messages. As it turns
> out to me it seems that seemingly everything pci-related is
> unavailable. Error messages are as follows:
> 
> [time after boot]PCI No IRQ known for interrup pin C of device
> 0000:00:1a.7. Please Try using pci=biosirq
> [time after boot]ehci_hcd 0000:00:1a.7 Found HC with no IRQ. Check
> BIOS/PCI 0000:00:1a.7 setup!
> [time after boot]ehci_hcd 0000:00:1a.7 fail, -19
> (of course time/device ids and pins (A-D) changed, but otherwise they
> were the same I think)
> I tried supplying pci=biosirq although I didn't think it would work,
> and it didn't, or some solution for a similiar issue from the debian
> wiki for the macbook (using a usb keyboard) which didn't work either.
> The usb keyboard works for refit and grub, but not once booted into
> linux. On some other wiki page it was suggested to supply "noapic
> acpi=force" and maybe "irqpoll" which I tried in various combinations
> without a change.
> 
> The machine I use for testing this is a first generation macbook air.
> Now while there are numerous reports about people running linux on it
> (pretty well actually) by providing it with a legacy bios environment,
> I didn't find a report about one running grub-efi on it successfully
> to boot linux. The most relevant posts my searches come up with are my
> own posts on the ubunutu forums.
> 
> So, I'm not sure who is to blame here, or if it's maybe just my own
> fault, but I decided that it would be nice to get the
> opinion/solutions? of some ppl who might be more intimately familiar
> with the workings of the mac boot firmware etc. and maybe know if this
> actually has been tested and should work, or not.
> 
> Thanks for an help in advance.

Are you sure that Debian lenny supports booting from EFI? I'm quite
literally talking out of my ass here, so I don't have a clue, but it
seems that the kernel you're trying to boot is trying to use BIOS
functionality. GRUB does _not_ include BIOS emulation, so that will
certainly not work. In order for a Linux kernel to boot from EFI, you
have to enable the switch in the pre-build kernel configuration.

From my past knowledge (on my brother's Macbook), at least Ubuntu/x86
kernels _do_ have the EFI switch enabled, so you might give it a try and
check if that's what's going wrong.

On the OS X and keyboard issues, I'm afraid I cannot help you. Perhaps
our elders would be wiser?

PS: you could try, however, to enable debug output when compiling your
GRUB so that you could see if there was anything wrong when loading the
file, like a hypothetical hfs.mod error (again, talking out of my
non-talking orifices)

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2009-01-28 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 16:42 grub-efi x86_64 on macbook air? step21
2009-01-28 16:56 ` Javier Martín [this message]
2009-01-28 17:30   ` step21
2009-01-28 18:05     ` Javier Martín
2009-01-28 20:23       ` step21

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=1233161803.1302.5.camel@localhost \
    --to=lordhabbit@gmail.com \
    --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.