Robert Millan wrote:
> On Tue, Jan 19, 2010 at 12:37:57PM +, Daire Byrne wrote:
>
>> Is this just a kernel bug that I should report or can grub work around
>> this? It seems to be a unique incomparability with the EFI firmware in
>> the latest MBP because grub-efi can boot kernels with this
On Tue, Jan 19, 2010 at 12:37:57PM +, Daire Byrne wrote:
> Is this just a kernel bug that I should report or can grub work around
> this? It seems to be a unique incomparability with the EFI firmware in
> the latest MBP because grub-efi can boot kernels with this patch on
> earlier macbooks (e.
Robert,
I had some time to do the bisect work. It looks like this kernel patch
broke booting by grub-efi on MBP5,4 from v2.6.31 onwards:
ceefccc93932b920a8ec6f35f596db05202a12fe is the first bad commit
commit ceefccc93932b920a8ec6f35f596db05202a12fe
Author: H. Peter Anvin
Date: Mon May 11 16:1
Robert,
On Tue, Jan 5, 2010 at 5:15 PM, Daire Byrne wrote:
>> 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
On Tue, Jan 05, 2010 at 05:15:02PM +, 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.
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
