Bug#716927: grub-efi-amd64: grub-efi doesn't support HFS+ EFI partitions

[Mike Hommey]

On Thu, Apr 03, 2014 at 02:21:03PM +0900, Mike Hommey wrote:
> On Tue, Mar 11, 2014 at 10:43:19AM +0100, Muammar El Khatib wrote:
> > Package: grub-efi-amd64
> > Version: 2.02~beta2-7
> > Followup-For: Bug #716927
> > 
> > 
> > Hello,
> > 
> > Now the situation is even worst. With last updated package, grub-install is not
> > anymore a script but a binary... So there is no way to change this (at least
> > that you recompile the package with the desired change I imagine).
> > 
> > 
> > Isn't there any way to add a conditional to detect the hfsplus the exfat
> > partition to continue?.
> > 
> > This is the error I get:
> > 
> >  ✘ muammar at ihacku ⮀ ~ ⮀ sudo apt-get dist-upgrade
> >  [sudo] password for muammar:
> >  Reading package lists... Done
> >  Building dependency tree
> >  Reading state information... Done
> >  Calculating upgrade... Done
> >  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> >  1 not fully installed or removed.
> >  After this operation, 0 B of additional disk space will be used.
> >  Do you want to continue? [Y/n]
> >  Setting up grub-efi-amd64 (2.02~beta2-7) ...
> >  Installing for x86_64-efi platform.
> >  grub-install: error: Can't create file: No such file or directory.
> >  dpkg: error processing package grub-efi-amd64 (--configure):
> >   subprocess installed post-installation script returned error exit status 1
> >   Errors were encountered while processing:
> >    grub-efi-amd64
> >    E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> Actually, it works, but requires the mach_kernel file to be in
> /boot/efi/EFI/debian. Once you're past that, all chances are you get an
> unbootable system. At least that's the state mine is right now.

So, the problem is that the new grub expecting and putting stuff in
/boot/efi/EFI/debian conflicts with my previous hack. Once I purge
/boot/efi/System, and rerun grub-install, I can finally get a bootable
system.

On the other hand, there are two downsides:
- The debian item "title" uses a different font than the other items in
  apple firmware.
- The debian item doesn't show up in OSX settings for startup.

So, to me, there are at least two different bugs in the version in
unstable:
- Using EFI/debian on hfs volumes.
- Failing with an obscure error message when mach_kernel doesn't exist.

Mike