[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1000743: installation-reports: bootx64.efi didn't seem to get installed and no UEFI boot entry was created for Debian



Hello,

Le 28/11/2021 à 12:28, Adam Baxter a écrit :

Comments/Problems:
Once the installer had finished and prompted me to reboot, the system came back up in Dell's hardware check mode and
some investigation revealed there was no UEFI boot entry for Debian.

Some UEFI firmwares are broken and do not handle EFI boot entries properly.

/boot/efi
└── EFI
     ├── debian
     │   ├── BOOTX64.CSV
     │   ├── fbx64.efi
     │   ├── grub.cfg
     │   ├── grubx64.efi
     │   ├── mmx64.efi
     │   └── shimx64.efi

At least GRUB itself was installed in the EFI partition.

Shouldn't there normally be EFI/boot/bootx64.efi?

Not by default. It happens only if you choose to install a copy of the boot loader in the removable device path. The option is available only in expert install or after changing priority for questions to low.

Additional issues:
This laptop has an upgraded AX201 wifi card - the installer detected that I needed non-free firmware and I was able
to load it from USB successfully. The message could be improved a bit with better instructions of where to
get the firmware and what structure is needed on the external drive.

The installation manual provides all this information.

I ended up grabbing https://saimei.ftp.acc.umu.se/cdimage/unofficial/non-free/firmware/testing/20211122/firmware.zip
and extracting the firmware files from firmware-iwlwifi_20210818-1_all.deb
Would the installer have coped if I'd just dropped that single deb file?

Yes, as stated in the installation manual.

Maybe it'd be worth having an option to allow a user to tether a mobile phone via USB to grab the firmware online.

This is automatic if the phone emulates a USB-ethernet adapter.

Also, a cdrom: entry was added to sources.list even though I installed from USB.

Because both contain the same ISO image so have the same data structure.


Reply to: