Bug#894034: marked as done (debian-installer: mount point /boot/efi)

["Debian Bug Tracking System" <owner@bugs.debian.org>]

Your message dated Wed, 19 Jun 2019 11:43:22 +0100
with message-id <20190619104322.GA3959@tack.einval.com>
and subject line Re: Bug#894034: debian-installer: mount point /boot/efi
has caused the Debian Bug report #894034,
regarding debian-installer: mount point /boot/efi
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
894034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894034
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- Begin Message ---

• To: Debian Bug Tracking System <submit@bugs.debian.org>
• Subject: debian-installer: mount point /boot/efi
• From: Heinrich Schuchardt <xypron.glpk@gmx.de>
• Date: Sun, 25 Mar 2018 19:15:29 +0200
• Message-id: <68d3c3d4-9bc5-179e-c1b8-4bdd15bd765c@gmx.de>

Package: debian-installer
Version: 20171204
Severity: normal

I am installing Debian buster armhf on a BananaPi.
This is the image I am using:
debian-testing-armhf-netinst.iso	2018-03-25 18:24

Grub expects that the EFI partition is mounted as /boot/efi.
When setting up the partions some default paths are offered but
/boot/efi is missing.
Please, add /boot/efi to the list of default paths.

Best regards

Heinrich Schuchardt

--- End Message ---

--- Begin Message ---

• To: Ben Hutchings <ben@decadent.org.uk>, 894034-done@bugs.debian.org
• Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
• Subject: Re: Bug#894034: debian-installer: mount point /boot/efi
• From: Steve McIntyre <steve@einval.com>
• Date: Wed, 19 Jun 2019 11:43:22 +0100
• Message-id: <20190619104322.GA3959@tack.einval.com>
• In-reply-to: <1522081241.2495.301.camel@decadent.org.uk>
• References: <68d3c3d4-9bc5-179e-c1b8-4bdd15bd765c@gmx.de> <handler.894034.B.152199814932720.ack@bugs.debian.org> <68d3c3d4-9bc5-179e-c1b8-4bdd15bd765c@gmx.de> <f8e5a883-346e-6deb-d654-1100820a19d1@gmx.de> <68d3c3d4-9bc5-179e-c1b8-4bdd15bd765c@gmx.de> <1522081241.2495.301.camel@decadent.org.uk>

On Mon, Mar 26, 2018 at 05:20:41PM +0100, Ben Hutchings wrote:
>On Sun, 2018-03-25 at 22:20 +0200, Heinrich Schuchardt wrote:
>> debian-installer/packages/partman-efi/check.d/efi starts with these lines:
>> 
>> if [ ! -d /proc/efi ] && [ ! -d /sys/firmware/efi ]; then
>>         exit 0
>> fi
>> 
>> if [ -f /var/lib/partman/ignore_uefi ]; then
>>         exit 0
>> fi
>> 
>> 
>> So it seems installation for EFI is only supported if the installer is
>> booted via EFI.
>
>This is because EFI booting normally requires setting variables through
>EFI runtime services.
>
>> The armhf netinstall iso does not make use of the UEFI implementation of
>> u-boot in contrast to what Suse and Fedora do. So we get stuck in a
>> legacy mode of booting. This is unsatisfactory if we want to setup a
>> multi-boot installation.
>
>That should be fixed, presumably through changes to debian-cd.

And it has - we have UEFI armhf support included now. Closing...

-- 
Steve McIntyre, Cambridge, UK.                                steve@einval.com
There's no sensation to compare with this
Suspended animation, A state of bliss

--- End Message ---