Comment 27 for bug 633983

Hi, probably a tiny bit too late, but did you try out a (very) recent grub version? I for myself was persecuted by the boot problem starting with amd64 releases of ubuntu 9.xy on my MacBook3,1. Until today I ran a custom grub 1.96 setup on my EFI partition (I expect 1.98 to behave the same). I decided to give its bzr live development branch a try [1] and it fixes the broken ramdisk loading for me (I am now able to boot an official ubuntu kernel instead of the vanilla non-initrd workarounds I was used to). Only problem seems to be the working of video=efifb. Screen got blank somwhere in between booting (I'd guess when encountering conflict between efifb and intel(drm)fb [2]) and stayed blank, but luckily the gdm-startup sound/input sound was hearable. So I did a blank login (no change) and then did close/open the lid and trigger a sleep/wakeup cycle, which amazingly brought up the running X session, I'm writing from. Maybe I should just use video=inteldrmfb instead of video=efifb as boot parameter, though my vanilla kernel with video=efifb (and without inteldrmfb support) didn't show the blank screen issue.

[1]
[heiko:hal][~] >> grub-mkimage -V
grub-mkimage (GRUB) 1.99~beta0

[2]
[ 3.324964] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver
[ 3.326817] Console: switching to colour dummy device 80x25
[ 3.600250] Console: switching to colour frame buffer device 160x50
[ 3.602903] fb0: inteldrmfb frame buffer device