Bug#1058806: HP EliteBook 860 G9 (4C148AV)
Hello Pascal and others, Op 17-12-2023 om 23:21 schreef Pascal Hambourg: On 17/12/2023 à 23:03, Paul van der Vlis wrote: Op 17-12-2023 om 22:36 schreef Pascal Hambourg: It may be an initialization issue: this error has been observed when booting after Windows hibernation or Fast Startup state. There is Windows on the NVMe disk of the laptop. Fastboot and secureboot where off. UEFI/BIOS "fast boot" is not the same as Windows "fast startup". I haven't changed anything in the bios, and I don't know Windows, if it started accidentally then I stopped it again. I have the machine to borrow from a dealer. I have also tested if I could boot the installer with fastboot on or secureboot on. But that dit not work. Debian should work with secure boot on. Also the installer? I was interested and tried it. The Debian installer did not start with secure boot on. I've tried it again now and found in the bios an option "use Microsoft UEFI CA key". This option was off, when I turn it on the Debian installer did start with secure boot on. With regards, Paul -- Paul van der Vlis Linux systeembeheer Groningen https://vandervlis.nl/
Bug#1058806: HP EliteBook 860 G9 (4C148AV)
Paul van der Vlis writes: > I've tried it again now and found in the bios an option "use Microsoft > UEFI CA key". This option was off, when I turn it on the Debian > installer did start with secure boot on. Yes, this is a problem with many modern PCs. Quite frustrating as the failure mode is without any visible warnings or hints at all. I hit the same issue on a Lenovo Thinkpad a while ago: https://www.mail-archive.com/debian-laptop@lists.debian.org/msg54007.html I believe this is worth a note in the installation guide. Bjørn
Bug#1058994: debian-installer: fakeroot is pseudo-required
Source: debian-installer Version: 20230217 Severity: normal Tags: d-i Hello Debian-installer team, Recently the dependency tree of the packages that are required for building the Debian Installer (using mk-build-deps) has changed, now fakeroot is no longer installed per default in chroot environments. However, the 'daily-build' script still has the default value for 'ROOTCMD' as 'fakeroot'. This issue was seen on Jenkins, where the installer is rebuilt from git for the sid images (as part of the live image build) [1] I've built 2 variants of the bookworm image, one with additionally installing fakeroot in my chroot environment and one with 'ROOTCMD=" "'. Both are identical, so fakeroot is indeed not required for a proper build. Can the default value for ROOTCMD be changed to an empty value (and the corresponding check be removed)? [3] With kind regards, Roland Clobus --- [1] https://jenkins.debian.net/view/live/job/reproducible_debian_live_build_standard_sid/671/console P: building the debian-installer ./daily-build: line 117: fakeroot: command not found E: An unexpected failure occurred, exiting... [2] /home/roland/git.nobackup/live-build/test/rebuild.sh --configuration standard --debian-version bookworm --timestamp archive --installer-origin git [3] https://sources.debian.org/src/debian- installer/20230607%2Bdeb12u4/build/daily-build/#L52 -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-debug'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-5-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
