Package: installation-reports
Version: 2.66
Severity: critical
-- Package-specific info:
Boot method: Netinstall CD image from USB stick
Image version:
https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/jigdo-cd/debian-testing-amd64-netinst.jigdo
dated 2018-01-14 04:22
Date: 2018-01-14
Machine: Fujitsu Lifebook AH532, first version (with BIOS version 1.09)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card:[O]
Configure network: [O]
Detect CD: [O]
Load installer modules: [O]
Clock/timezone setup: [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives: [O]
Install base system:[O]
Install tasks: [O]
Install boot loader:[O]
Overall install:[O]
Problems:
Short summary:
The installation process completed successfully, but the UEFI
firmware is broken afterwards; it is impossible to get into the
UEFI setup, boot from any external device anymore or get the
system to use the CSM to boot from a classical MBR.
Detailed description:
This was an installation in EFI mode (for the first time on this
device). The system was previously running an older BIOS-mode
installation without problems, but got a new, bigger harddisk and
therefore required a new installation which was done in EFI mode
(which is nowadays the default mode the installer starts in).
The installation itself worked without problems and the resulting
Debian system works fine, but it isn't possible anymore to get
into the BIOS/UEFI setup of the machine nor boot from any other
device. When powering on the system, the message ": Boot
Menu, : BIOS Setup" appears (as always), pressing F2 results
in a short "Please wait..." (als always), but then one doesn't
get into the UEFI/BIOS setup but instead the system directly
boots GRUB. Pressing F12 for the boot menu results in a screen
with a menu with the following structure:
- Boot Menu
debian
- Application Menu
Diagnostic Screen
"Diagnostic Screen" just shows the Firmware splash screen:
"Phoenix SecureCore Tiano(TM)
Copyright 1985-2011 Phoenix Technologies Ltd.
All Rights Reserved
Fixed Disk:
ATAPI CDROM:
Press any key to exit"
and the "debian" boot menu entry obviously starts GRUB.
There is no way to make the system boot from any external device
anymore, so it is impossible to boot a rescue system or reinstall
the device from scratch. Fallback to BIOS-mode booting also
doesn't work any more. Plugging back the the old harddisk with a
BIOS-mode install results in a non-booting system. The UEFI/BIOS
always tries to boot the "debian" EFI entry which for obvious
reasons doesn't work with a BIOS-mode setup on the disk.
There is also a Window 7 UEFI-mode installation on the (new)
disk, which can be started from GRUB, but it doesn't show up any
more in the firmware-provided boot-menu (which it did before
installing Debian).
Running "efibootmgr -v" from the installed systems results in "No
BootOrder is set; firmware will attempt recovery", which is what
doesn't seem to work. It somewhat looks like the UEFI/BIOS
setup, the Firmware-level boot menu and the CSM for BIOS-mode
booting are EFI applications that cannot be started anymore
because some NVRAM entry is broken.
BIOS Information from dmidecode:
Vendor: FUJITSU // Phoenix Technologies Ltd.
Version: Version 1.09
Release Date: 05/22/2012
Address: 0xE
Runtime Size: 128 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
PC Card (PCMCIA) is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
3.5"/720 kB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.9
This is the newest BIOS version that is available for this
device; newer versions (2.xx) are only available for a newer
board revision and are not compatible with this board revision.
How can one bring the NVRAM back into a sane state that allows
getting into the setup and booting from external devices?
Regards,
Karsten
Technical information about the system:
