From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: EFI boot problem with MBP 5,4
Date: Thu, 7 Jan 2010 22:21:48 +0100 [thread overview]
Message-ID: <20100107212148.GD26340@thorin> (raw)
In-Reply-To: <131780341001050915g6025cca3m60b433d168c8b3bc@mail.gmail.com>
On Tue, Jan 05, 2010 at 05:15:02PM +0000, Daire Byrne wrote:
> Hi,
>
> It looks like recent kernels (namely 2.6.31 and 2.6.32) can't find the
> initrd when booting from grub (efi) on a macbook pro 5,4 giving the
> error:
>
> RAMDISK: Couldn't find valid RAM disk image starting at 0.
>
> The 2.6.30 kernel does not seem to suffer from this so something must
> have changed in 2.6.31+. I also tested all three kernels on a MBP4,1
> and they all boot fine from grub - they find and load the initrd. In all
> cases the grub.cfg and initrd remained the same and only the kernel
> was changed. This could be a kernel issue but the fact that they all
> boot on a MBP4,1 makes me think it is a EFI1.1 vs EFI 2.0 thing.
>
> As an aside I can get the nvidia module working with MBP5,4+2.6.30 but
> a MBP4,1+2.6.30 can't find the vbios. Is this a known thing and is
> there a possible fix for it?
Perhaps you could run a regression test (aka bisect) on Linux source? This
would help us figure out the problem (whether it's a bug in Linux, in GRUB
or in your firmware).
--
Robert Millan
"Be the change you want to see in the world" -- Gandhi
next prev parent reply other threads:[~2010-01-07 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <131780341001050857t6794b2a5o18be810f5bc30d11@mail.gmail.com>
2010-01-05 17:15 ` EFI boot problem with MBP 5,4 Daire Byrne
2010-01-07 21:21 ` Robert Millan [this message]
2010-01-11 17:17 ` Daire Byrne
2010-01-19 12:37 ` Daire Byrne
2010-01-19 22:34 ` Robert Millan
2010-01-19 22:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=20100107212148.GD26340@thorin \
--to=rmh@aybabtu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox