Bug#1013170: Installation of bookworm successfully at Asus ZenbookPro
Package: installation-reports Boot method: Network PXE Boot Image version: PXE Boot with daily > https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/initrd.gz > https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/linux Date: 2022-06-27 Machine: Asus Zenbook Pro UX501J Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz Memory: 16GB Partitions: > DateisystemTyp 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf > udev devtmpfs 81153280 81153280% /dev > tmpfs tmpfs 1627632 1076 16265561% /run > /dev/sda2 ext4 120983240 10152996 1046384249% / > tmpfs tmpfs 813814411552 81265921% /dev/shm > tmpfs tmpfs 51204 51161% /run/lock > /dev/sda1 vfat523244 1445231001% /boot/efi > tmpfs tmpfs 1627628 64 16275641% /run/user/1000 Output of lspci -knn: > 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor DRAM Controller [8086:0c04] (rev 06) > Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor > DRAM Controller [1043:18dd] > Kernel modules: ie31200_edac > 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor PCI Express x16 Controller [8086:0c01] (rev 06) > Kernel driver in use: pcieport > 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core > Processor Integrated Graphics Controller [8086:0416] (rev 06) > Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated > Graphics Controller [1043:18dd] > Kernel driver in use: i915 > Kernel modules: i915 > 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor HD Audio Controller [8086:0c0c] (rev 06) > Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD > Audio Controller [8086:2010] > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset > Family USB xHCI [8086:8c31] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > USB xHCI [1043:18dd] > Kernel driver in use: xhci_hcd > Kernel modules: xhci_pci > 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 > Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > MEI Controller [1043:18dd] > Kernel driver in use: mei_me > Kernel modules: mei_me > 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset > Family USB EHCI #2 [8086:8c2d] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > USB EHCI [1043:18dd] > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset > High Definition Audio Controller [8086:8c20] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High > Definition Audio Controller [1043:18dd] > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #1 [8086:8c10] (rev d5) > Kernel driver in use: pcieport > 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #3 [8086:8c14] (rev d5) > Kernel driver in use: pcieport > 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #4 [8086:8c16] (rev d5) > Kernel driver in use: pcieport > 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset > Family USB EHCI #1 [8086:8c26] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > USB EHCI [1043:18dd] > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > 00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller > [8086:8c4b] (rev 05) > Subsystem: ASUSTeK Computer Inc. HM87 Express LPC Controller [1043:18dd] > Kernel driver in use: lpc_ich > Kernel modules: lpc_ich > 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series > Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > 6-port SATA Controller 1 [AHCI mode] [1043:18dd] > Kernel driver in use: ahci > Kernel modules: ahci > 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family > SMBus Controller [8086:8c22] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > SMBus Controller [1043:18dd] > Kernel driver in use: i801_smbus > Kern
Bug#1013203: os-prober: Dual boot Windows 10 grub-probe error unknown filesystem
Package: os-prober
Version: 1.80
Severity: normal
X-Debbugs-Cc: zalek.ste...@gmail.com
Dear Maintainer,
What led to the situation:
Debian Testing new linux kernel 5.18.0-1 and updated grub 2.06-3 installed via
apt package manager; the new linux kernel installation prompted the update-grub
function to run.
By default this new version of grub does not run the the os-prober package,
hence, the Windows 10 partition was not detected and was eliminated from the
grub.cfg list of bootable partitions.
What I did that was effective/ineffective (part 1):
- Added 'GRUB_DISABLE_OS_PROBER=false' to /etc/default/grub and ran 'sudo
update-grub', forcing os-prober/grub to search for Windows partition
- this resulted in the Windows 10 partition on this computer (box0) to be
recognized, but with errors >>
[incidentally, this exact procedure worked perfectly on my dual-boot Debian
Testing/Windows 10 laptop - no errors]
terminal output >>
---
zaleksf@box0:~$ sudo update-grub
[sudo] password for zaleksf:
Generating grub configuration file ...
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-5.18.0-1-amd64
Found initrd image: /boot/initrd.img-5.18.0-1-amd64
Found linux image: /boot/vmlinuz-5.17.0-1-amd64
Found initrd image: /boot/initrd.img-5.17.0-1-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot
entries.
/usr/sbin/grub-probe: error: unknown filesystem.
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
/usr/sbin/grub-probe: error: unknown filesystem.
Adding boot menu entry for UEFI Firmware Settings ...
done
---
Outcome:
Upon rebooting and seeing the main grub list screen, there were the usual
entries for booting to Debian, Windows, etc. However, upon selecting the
Windows boot entry, I received an error indicating
'/EFI/Microsoft/Boot/bootmgfw.efi does not exist'
This was false, as I could find this file from both the Debian OS and Windows
OS file manager, and I could boot directly into Windows 10 from the BIOS using
the 'Enter/F12' key combination to bring up a list of boot partition choices
(which did show both Debian and Windows as options).
I investigated grub.cfg file and found that the 30_os-prober section for
Windows to be significantly truncated from its usual entry (and other Linux
kernel entries) >>
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda1)' --class windows --class os
$menuentry_id_option 'osprober-efi-/dev/sda1' {
insmod part_gpt
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/30_os-prober ###
What I did that was effective/ineffective (part 2):
Since my laptop (box1) also is dual-boot Debian Testing/Windows 10 with a
virtually identical set-up, I tried an experiment of copying its complete (and
functioning) 30_os-prober section to grub.cfg on this misbehaving desktop
system (box0). I tweaked this section (using logic) to point to the proper
Windows partition, etc. (since I really have no experience with grub at all).
Manually changed section 30_os-prober to this >>
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows Boot Manager (on /dev/sda1)' --class windows --class os
$menuentry_id_option 'osprober-efi-/dev/sda1' {
insmod part_gpt
insmod fat
set root='hd0,gpt1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-
efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 82CB-1126
else
search --no-floppy --fs-uuid --set=root 54C7-5867
fi
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
### END /etc/grub.d/30_os-prober ###
Saved grub.cfg, rebooted machine and selected Windows entry from grub.
Outcome:
Can boot into the Windows 10 partition perfectly, just as before. All grub list
entries work correctly.
If I run 'update-grub' again, the grub-probe error is indicated in the
terminal, and the truncated/broken section 30_os-prober returns to
/boot/grub/grub.cfg
My machine (and Windows and Debian) works just fine. This machine has been
dual-boot Debian Testing/Windows 10 for the last 5 years and has never
experienced this issue before this version of grub/os-prober was introduced.
My recommendation is to look into why the os-prober successfully recognizes a
dual-boot Windows partition for some machines and not others. Please let me
know if I can send additional files to support troubleshooting and/or
development.
Best regards, SZ
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (800, 'testing'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-1-amd64 (SMP w/16 C
