From owner at bugs.debian.org  Mon May  3 16:33:10 2021
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 03 May 2021 15:33:10 +0000
Subject: Processed: unarchiving 932966
References: <1620055755-3556-bts-steve@einval.com>
Message-ID: <handler.s.C.16200558157532.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> unarchive 932966
Bug #932966 {Done: Colin Watson <cjwatson at debian.org>} [src:grub2] GRUB2 EFI has incompatibility with Devuan
Unarchived Bug 932966
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932966
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From owner at bugs.debian.org  Mon May  3 16:33:12 2021
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 03 May 2021 15:33:12 +0000
Subject: Processed: reopening 932966
References: <1620055763-238-bts-steve@einval.com>
Message-ID: <handler.s.C.16200558157540.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> reopen 932966
Bug #932966 {Done: Colin Watson <cjwatson at debian.org>} [src:grub2] GRUB2 EFI has incompatibility with Devuan
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions grub2/2.04-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932966
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From owner at bugs.debian.org  Mon May  3 16:42:09 2021
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Mon, 03 May 2021 15:42:09 +0000
Subject: Processed: reopening 932966
References: <1620056262-3850-bts-steve@einval.com>
Message-ID: <handler.s.C.162005629210162.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> reopen 932966
Bug #932966 [src:grub2] GRUB2 EFI has incompatibility with Devuan
Bug 932966 is not marked as done; doing nothing.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932966
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From steve at einval.com  Mon May  3 16:50:29 2021
From: steve at einval.com (Steve McIntyre)
Date: Mon, 3 May 2021 16:50:29 +0100
Subject: Bug#932966: GRUB2 EFI has incompatibility with Devuan
In-Reply-To: <20190725100154.GA8820@fq>
References: <20190725100154.GA8820@fq> <20190725100154.GA8820@fq>
Message-ID: <20210503155028.GA20337@tack.einval.com>

Hi Ivan,

Apologies for not seeing this bug earlier - I should have responded
way back when you first opened it, sorry... :-/

On Thu, Jul 25, 2019 at 10:01:54AM +0200, Ivan J. wrote:
>Package: grub-common
>Version: 2.02+dfsg1-20
>Source: grub2
>
>When in Devuan grub is updated to the buster version, there is an EFI
>signing issue with --bootloader-id, because 'devuan' is not recognized.
>This renders an error in GRUB when booting and requires manual
>interference to boot the system by loading the kernel and initramfs.
>
>The issue is much the same like KUbuntu, which already has a patch, and
>supporting Devuan should be done in the same way.

Ummmm. Kubuntu is very much maintained as a tiny variation from
Ubuntu, using the same kernel, grub, shim, etc. AFAIK Devuan is *not*
doing the same style of variation from Debian? In that case, Devuan
should absolutely *not* be installing things in the ESP under
/EFI/debian but should switch everything to /EFI/devuan instead. That
would also have the advantage for users that dual-booting between
Debian and Devuan would work, with different boot entries etc.

-- 
Steve McIntyre, Cambridge, UK.                                steve at einval.com
  Mature Sporty Personal
  More Innovation More Adult
  A Man in Dandism
  Powered Midship Specialty


From steve at einval.com  Mon May  3 16:28:47 2021
From: steve at einval.com (Steve McIntyre)
Date: Mon, 3 May 2021 16:28:47 +0100
Subject: Installing grub via triggers instead of duplicating code in shim
 signed and friends
In-Reply-To: <20200713174332.GA2350528@debian.org>
References: <20200713174332.GA2350528@debian.org>
Message-ID: <20210503152838.GB31306@tack.einval.com>

Hey Julian,

[ a *long* time later... ]

On Mon, Jul 13, 2020 at 05:47:45PM +0200, Julian Andres Klode wrote:
>
>I was wondering if it would make sense to invoke grub-install
>via (await) triggers from shim-signed and friends, rather than
>calling grub-install in the postinst.
>
>In Ubuntu, we have patched grub to install to multiple ESPs,
>by means of a script which does the whole debconf dance similar
>to the logic for installing to MBRs, which exists mostly only
>because we need to be able to access this logic from shim and
>friends (not sure which packages entirely).
>
>This also caused a few problems, as apparently the debconf
>template needs to be in each package that calls that helper
>script now, otherwise debconf can't find it (sometimes).
>
>While thinking about this it occured to me that instead
>of a script and invoking that explicitly, it would be much
>nicer to just trigger the grub package - although I'm not
>exactly sure _which_ grub package yet.
>
>What do you guys think?

I think it would make sense, yes. I'm just tweaking various of the
maint scripts in the shim packages now, and there's a lot of overlap
here. Unfortunately, the grub postinst is also a huge ball of mud and
I'm not sure of exactly the right way to play with it right
now. Definitely too big a change to make just before the Bullseye
release!

I'm almost thinking it's *maybe* worth thinking about separating out
the grub*efi maintscripts from the non-efi versions. There's a lot of
common stuff, but also a lot that just isn't needed. Hmmm.

Ugh, while I've been looking I've also just found a bug - IMHO #932966
just have been closed, not by taking a patch there. About to open a
new bug...

-- 
Steve McIntyre, Cambridge, UK.                                steve at einval.com
  Getting a SCSI chain working is perfectly simple if you remember that there
  must be exactly three terminations: one on one end of the cable, one on the
  far end, and the goat, terminated over the SCSI chain with a silver-handled
  knife whilst burning *black* candles. --- Anthony DeBoer



From pmenzel at molgen.mpg.de  Tue May 11 20:19:28 2021
From: pmenzel at molgen.mpg.de (Paul Menzel)
Date: Tue, 11 May 2021 21:19:28 +0200
Subject: Bug#988392: Impossible to install grub-pc and grub-efi-amd64 in
 parallel
Message-ID: <e0136a1e-45be-b03b-cea3-636aac978668@molgen.mpg.de>

Package: src:grub
Version: 2.04-18
Severity: normal


Dear Debian folks,


I have a Debian installation on a disk, I carry around, and I want to 
boot on BIOS and (U)EFI systems. This would be possible with the switch 
`--target`.

     sudo grub-install --target=i386-pc --boot-directory=/boot /dev/sda

and

     sudo grub-install --target=x86_64-efi /dev/sda

Unfortunately I am unable to install both packages in parallel as they 
conflict (Replaces?) with each other.

     $ apt show grub-pc
     [?]
     Replaces: grub, grub-common (<= 1.97~beta2-1), grub-coreboot, 
grub-efi-amd64, grub-efi-ia32, grub-ieee1275, grub-legacy, grub2 (<< 
2.04-18)

The GRUB build system also does not seem to allow to configure the build 
to build the platforms in parallel, but in the end the files in 
`/usr/lib/grub/` should be able to coexist.

It? be great if Debian?s GRUB packages could be installed in parallel.


Kind regards,

Paul


From owner at bugs.debian.org  Tue May 11 23:15:05 2021
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Tue, 11 May 2021 22:15:05 +0000
Subject: Bug#988392: marked as done (Impossible to install grub-pc and
 grub-efi-amd64 in parallel)
References: <20210511213728.GA26923@riva.ucam.org>
 <e0136a1e-45be-b03b-cea3-636aac978668@molgen.mpg.de>
Message-ID: <handler.988392.D988392.162077101119487.ackdone@bugs.debian.org>

Your message dated Tue, 11 May 2021 22:37:28 +0100
with message-id <20210511213728.GA26923 at riva.ucam.org>
and subject line Re: Bug#988392: Impossible to install grub-pc and grub-efi-amd64 in parallel
has caused the Debian Bug report #988392,
regarding Impossible to install grub-pc and grub-efi-amd64 in parallel
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 at bugs.debian.org
immediately.)


-- 
988392: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988392
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Paul Menzel <pmenzel at molgen.mpg.de>
Subject: Impossible to install grub-pc and grub-efi-amd64 in parallel
Date: Tue, 11 May 2021 21:19:28 +0200
Size: 2903
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20210511/137ac220/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Colin Watson <cjwatson at debian.org>
Subject: Re: Bug#988392: Impossible to install grub-pc and grub-efi-amd64 in parallel
Date: Tue, 11 May 2021 22:37:28 +0100
Size: 3325
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20210511/137ac220/attachment-0001.eml>

From pmenzel at molgen.mpg.de  Wed May 12 07:51:05 2021
From: pmenzel at molgen.mpg.de (Paul Menzel)
Date: Wed, 12 May 2021 08:51:05 +0200
Subject: Bug#988392: Impossible to install grub-pc and grub-efi-amd64 in
 parallel
In-Reply-To: <20210511213728.GA26923@riva.ucam.org>
References: <e0136a1e-45be-b03b-cea3-636aac978668@molgen.mpg.de>
 <20210511213728.GA26923@riva.ucam.org>
 <e0136a1e-45be-b03b-cea3-636aac978668@molgen.mpg.de>
Message-ID: <8f6b8166-4eb1-f687-b766-430b9e302aa4@molgen.mpg.de>

Dear Colin,


Am 11.05.21 um 23:37 schrieb Colin Watson:
> On Tue, May 11, 2021 at 09:19:28PM +0200, Paul Menzel wrote:
>> I have a Debian installation on a disk, I carry around, and I want to boot
>> on BIOS and (U)EFI systems. This would be possible with the switch
>> `--target`.
>>
>>      sudo grub-install --target=i386-pc --boot-directory=/boot /dev/sda
>>
>> and
>>
>>      sudo grub-install --target=x86_64-efi /dev/sda
>>
>> Unfortunately I am unable to install both packages in parallel as they
>> conflict (Replaces?) with each other.
>>
>>      $ apt show grub-pc
>>      [?]
>>      Replaces: grub, grub-common (<= 1.97~beta2-1), grub-coreboot, grub-efi-amd64, grub-efi-ia32, grub-ieee1275, grub-legacy, grub2 (<< 2.04-18)
> 
> The purpose of grub-pc and grub-efi-amd64 is to own the system's boot
> process, and so only one of those may be installed at once; those
> Conflicts are deliberate.  However, to support your use case, you can
> install grub-pc-bin and grub-efi-amd64-bin in parallel, and doing so
> gives you enough to be able to run the grub-install commands you're
> asking for.

As always thank you very much for the fast and helpful reply with the 
solution. Sorry for not thinking of that myself.


Kind regards,

Paul


From sunil at medhas.org  Thu May 13 16:31:11 2021
From: sunil at medhas.org (Sunil Mohan Adapa)
Date: Thu, 13 May 2021 08:31:11 -0700
Subject: Bug#984760: grub-pc: upgrade works,
 boot fails (error: symbol `grub_is_lockdown` not found)
In-Reply-To: <093f3a88-7909-ffc5-b8d5-eac25f3a03d6@medhas.org>
References: <161738111411.11040.1135995262993589298.reportbug@familie.fantom.de>
 <161738111411.11040.1135995262993589298.reportbug@familie.fantom.de>
 <093f3a88-7909-ffc5-b8d5-eac25f3a03d6@medhas.org>
 <093f3a88-7909-ffc5-b8d5-eac25f3a03d6@medhas.org>
 <161517360882.7419.17121812337560587232.reportbug@dhat>
Message-ID: <a310ada9-6cbb-8416-9131-95a52813ce78@medhas.org>

On Thu, 15 Apr 2021 23:00:22 -0700 Sunil Mohan Adapa <sunil at medhas.org>
wrote:
> Hi,
> 
> The problem is not limited to amd64. I see this problem on arm64. On a
> FreedomBox arm64 image, on a Raspberry Pi 3B+ (when booted with UEFI
> firmware[1]) when grub efi packages are upgraded, boot fails with the
> error 'symbol `grub_is_lockdown` not found'.
> 
> Links:
> 1) https://github.com/pftf/RPi3
> 

In my case, after uninstalling and reinstalling grub-efi-arm64* and
grub?-common packages, everything worked well. This action installed
additional packages (like shim-signed?) that were not present before.

The problem surfaced after an upgrade, in my case, done using
unattended-upgrades. This may indicate that something that is supposed
to be in Depends: list is in Recommends: list.

-- 
Sunil


From kuehnel at codecivil.de  Thu May 20 17:13:16 2021
From: kuehnel at codecivil.de (Marco =?UTF-8?Q?K=C3=BChnel?=)
Date: Thu, 20 May 2021 18:13:16 +0200
Subject: Bug#988876: grub-efi-amd64: outb command no longer works
Message-ID: <162152719672.3212.13405676296549273045.reportbug@caspianmac>

Package: grub-efi-amd64
Version: 2.02+dfsg1-20+deb10u4
Severity: important
Tags: d-i

After a fresh install of debian buster a grub.cfg containing an outb command throws the error "outb command not found" (and, in my case, 
cannot start lightdm thereafter). This problem does not appear when downgrading all installed grub packages to version 
2.02+dfsg1-20+deb10u3. 

-- Package-specific info:

*********************** BEGIN /proc/mounts
/dev/sdb4 / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sdb9 /home ext4 rw,relatime 0 0
/dev/sdb5 /var ext4 rw,relatime 0 0
/dev/sdb2 /home/mac/macOS ext4 rw,relatime 0 0
/dev/sdb7 /tmp ext4 rw,relatime 0 0
/dev/sdb3 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
*********************** END /proc/mounts

*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
insmod iorw
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
set root='hd1,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4  fb7e40d6-bc1d-447c-b907-accd056dc7eb
else
  search --no-floppy --fs-uuid --set=root fb7e40d6-bc1d-447c-b907-accd056dc7eb
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=1440x900
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=de_DE
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_gpt
insmod ext2
set root='hd1,gpt4'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4  fb7e40d6-bc1d-447c-b907-accd056dc7eb
else
  search --no-floppy --fs-uuid --set=root fb7e40d6-bc1d-447c-b907-accd056dc7eb
fi
insmod png
if background_image /usr/share/desktop-base/futureprototype-theme/grub/grub-4x3.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
	set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-fb7e40d6-bc1d-447c-b907-accd056dc7eb' {
	load_video
        outb 0x728 1
        outb 0x710 2
        outb 0x740 2
        outb 0x750 0
	insmod gzio
	if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
	insmod part_gpt
	insmod ext2
	set root='hd1,gpt4'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4  fb7e40d6-bc1d-447c-b907-accd056dc7eb
	else
	  search --no-floppy --fs-uuid --set=root fb7e40d6-bc1d-447c-b907-accd056dc7eb
	fi
	echo	'Linux 4.19.0-16-amd64 wird geladen ?'
	linux	/boot/vmlinuz-4.19.0-16-amd64 root=UUID=fb7e40d6-bc1d-447c-b907-accd056dc7eb ro  quiet splash i915.modeset=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=0 libata.force=noncq
	echo	'Initiale Ramdisk wird geladen ?'
	initrd	/boot/initrd.img-4.19.0-16-amd64
}
submenu 'Erweiterte Optionen f?r Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-fb7e40d6-bc1d-447c-b907-accd056dc7eb' {
	menuentry 'Debian GNU/Linux, mit Linux 4.19.0-16-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-16-amd64-advanced-fb7e40d6-bc1d-447c-b907-accd056dc7eb' {
		load_video
	        outb 0x728 1
	        outb 0x710 2
	        outb 0x740 2
	        outb 0x750 0
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4  fb7e40d6-bc1d-447c-b907-accd056dc7eb
		else
		  search --no-floppy --fs-uuid --set=root fb7e40d6-bc1d-447c-b907-accd056dc7eb
		fi
		echo	'Linux 4.19.0-16-amd64 wird geladen ?'
		linux	/boot/vmlinuz-4.19.0-16-amd64 root=UUID=fb7e40d6-bc1d-447c-b907-accd056dc7eb ro  quiet splash i915.modeset=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=0 libata.force=noncq
		echo	'Initiale Ramdisk wird geladen ?'
		initrd	/boot/initrd.img-4.19.0-16-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-16-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-16-amd64-recovery-fb7e40d6-bc1d-447c-b907-accd056dc7eb' {
		load_video
	        outb 0x728 1
	        outb 0x710 2
	        outb 0x740 2
	        outb 0x750 0
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4  fb7e40d6-bc1d-447c-b907-accd056dc7eb
		else
		  search --no-floppy --fs-uuid --set=root fb7e40d6-bc1d-447c-b907-accd056dc7eb
		fi
		echo	'Linux 4.19.0-16-amd64 wird geladen ?'
		linux	/boot/vmlinuz-4.19.0-16-amd64 root=UUID=fb7e40d6-bc1d-447c-b907-accd056dc7eb ro single 
		echo	'Initiale Ramdisk wird geladen ?'
		initrd	/boot/initrd.img-4.19.0-16-amd64
	}
	menuentry 'Debian GNU/Linux, mit Linux 4.19.0-11-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-11-amd64-advanced-fb7e40d6-bc1d-447c-b907-accd056dc7eb' {
		load_video
	        outb 0x728 1
	        outb 0x710 2
	        outb 0x740 2
	        outb 0x750 0
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4  fb7e40d6-bc1d-447c-b907-accd056dc7eb
		else
		  search --no-floppy --fs-uuid --set=root fb7e40d6-bc1d-447c-b907-accd056dc7eb
		fi
		echo	'Linux 4.19.0-11-amd64 wird geladen ?'
		linux	/boot/vmlinuz-4.19.0-11-amd64 root=UUID=fb7e40d6-bc1d-447c-b907-accd056dc7eb ro  quiet splash i915.modeset=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=0 libata.force=noncq
		echo	'Initiale Ramdisk wird geladen ?'
		initrd	/boot/initrd.img-4.19.0-11-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-11-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-11-amd64-recovery-fb7e40d6-bc1d-447c-b907-accd056dc7eb' {
		load_video
	        outb 0x728 1
	        outb 0x710 2
	        outb 0x740 2
	        outb 0x750 0
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd1,gpt4'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,gpt4 --hint-efi=hd1,gpt4 --hint-baremetal=ahci1,gpt4  fb7e40d6-bc1d-447c-b907-accd056dc7eb
		else
		  search --no-floppy --fs-uuid --set=root fb7e40d6-bc1d-447c-b907-accd056dc7eb
		fi
		echo	'Linux 4.19.0-11-amd64 wird geladen ?'
		linux	/boot/vmlinuz-4.19.0-11-amd64 root=UUID=fb7e40d6-bc1d-447c-b907-accd056dc7eb ro single 
		echo	'Initiale Ramdisk wird geladen ?'
		initrd	/boot/initrd.img-4.19.0-11-amd64
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/15_linux_sda ###
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os  'gnulinux-simple-e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7' {
	load_video
        outb 0x728 1
        outb 0x710 2
        outb 0x740 2
        outb 0x750 0
	insmod gzio
	if [ x = xxen ]; then insmod xzio; insmod lzopio; fi
	insmod part_gpt
	insmod ext2
	set root='hd0,gpt2'
	if [ x = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  d64727a5-ce33-4fd8-83be-f941be9779f9
	else
	  search --no-floppy --fs-uuid --set=root d64727a5-ce33-4fd8-83be-f941be9779f9
	fi
	echo	'Loading Linux 4.19.0-16-amd64 ...'
	linux	/vmlinuz-4.19.0-16-amd64 root=/dev/mapper/caspiansea--vg-root ro  quiet splash i915.modeset=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=0 libata.force=noncq
	echo	'Loading initial ramdisk ...'
	initrd	/initrd.img-4.19.0-16-amd64
}
submenu 'Advanced options for Debian GNU/Linux'  'gnulinux-advanced-e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7' {
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-16-amd64' --class debian --class gnu-linux --class gnu --class os  'gnulinux-4.19.0-16-amd64-advanced-e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7' {
		load_video
	        outb 0x728 1
	        outb 0x710 2
	        outb 0x740 2
	        outb 0x750 0
		insmod gzio
		if [ x = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd0,gpt2'
		if [ x = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  d64727a5-ce33-4fd8-83be-f941be9779f9
		else
		  search --no-floppy --fs-uuid --set=root d64727a5-ce33-4fd8-83be-f941be9779f9
		fi
		echo	'Loading Linux 4.19.0-16-amd64 ...'
		linux	/vmlinuz-4.19.0-16-amd64 root=/dev/mapper/caspiansea--vg-root ro  quiet splash i915.modeset=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=0 libata.force=noncq
		echo	'Loading initial ramdisk ...'
		initrd	/initrd.img-4.19.0-16-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-16-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os  'gnulinux-4.19.0-16-amd64-recovery-e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7' {
		load_video
	        outb 0x728 1
	        outb 0x710 2
	        outb 0x740 2
	        outb 0x750 0
		insmod gzio
		if [ x = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd0,gpt2'
		if [ x = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  d64727a5-ce33-4fd8-83be-f941be9779f9
		else
		  search --no-floppy --fs-uuid --set=root d64727a5-ce33-4fd8-83be-f941be9779f9
		fi
		echo	'Loading Linux 4.19.0-16-amd64 ...'
		linux	/vmlinuz-4.19.0-16-amd64 root=/dev/mapper/caspiansea--vg-root ro single 
		echo	'Loading initial ramdisk ...'
		initrd	/initrd.img-4.19.0-16-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-14-amd64' --class debian --class gnu-linux --class gnu --class os  'gnulinux-4.19.0-14-amd64-advanced-e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7' {
		load_video
	        outb 0x728 1
	        outb 0x710 2
	        outb 0x740 2
	        outb 0x750 0
		insmod gzio
		if [ x = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd0,gpt2'
		if [ x = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  d64727a5-ce33-4fd8-83be-f941be9779f9
		else
		  search --no-floppy --fs-uuid --set=root d64727a5-ce33-4fd8-83be-f941be9779f9
		fi
		echo	'Loading Linux 4.19.0-14-amd64 ...'
		linux	/vmlinuz-4.19.0-14-amd64 root=/dev/mapper/caspiansea--vg-root ro  quiet splash i915.modeset=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=0 libata.force=noncq
		echo	'Loading initial ramdisk ...'
		initrd	/initrd.img-4.19.0-14-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-14-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os  'gnulinux-4.19.0-14-amd64-recovery-e78fa255-2ca7-4d0b-a72e-ab2c6f4d3ea7' {
		load_video
	        outb 0x728 1
	        outb 0x710 2
	        outb 0x740 2
	        outb 0x750 0
		insmod gzio
		if [ x = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_gpt
		insmod ext2
		set root='hd0,gpt2'
		if [ x = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  d64727a5-ce33-4fd8-83be-f941be9779f9
		else
		  search --no-floppy --fs-uuid --set=root d64727a5-ce33-4fd8-83be-f941be9779f9
		fi
		echo	'Loading Linux 4.19.0-14-amd64 ...'
		linux	/vmlinuz-4.19.0-14-amd64 root=/dev/mapper/caspiansea--vg-root ro single 
		echo	'Loading initial ramdisk ...'
		initrd	/initrd.img-4.19.0-14-amd64
	}
}
### END /etc/grub.d/15_linux_sda ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
*********************** END /boot/grub/grub.cfg

*********************** BEGIN /proc/mdstat
cat: /proc/mdstat: No such file or directory
*********************** END /proc/mdstat

*********************** BEGIN /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root  9 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC -> ../../sdb
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC-part4 -> ../../sdb4
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC-part5 -> ../../sdb5
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC-part6 -> ../../sdb6
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC-part7 -> ../../sdb7
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC-part8 -> ../../sdb8
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-ST750LX003-1AC154_W200LVNC-part9 -> ../../sdb9
lrwxrwxrwx 1 root root  9 May 20 17:54 ata-Samsung_SSD_850_EVO_250GB_S21PNSBG104291J -> ../../sda
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-Samsung_SSD_850_EVO_250GB_S21PNSBG104291J-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-Samsung_SSD_850_EVO_250GB_S21PNSBG104291J-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 May 20 17:54 ata-Samsung_SSD_850_EVO_250GB_S21PNSBG104291J-part3 -> ../../sda3
lrwxrwxrwx 1 root root  9 May 20 17:54 wwn-0x5000c5005e0519c3 -> ../../sdb
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5000c5005e0519c3-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5000c5005e0519c3-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5000c5005e0519c3-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5000c5005e0519c3-part4 -> ../../sdb4
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5000c5005e0519c3-part5 -> ../../sdb5
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5000c5005e0519c3-part6 -> ../../sdb6
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5000c5005e0519c3-part7 -> ../../sdb7
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5000c5005e0519c3-part8 -> ../../sdb8
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5000c5005e0519c3-part9 -> ../../sdb9
lrwxrwxrwx 1 root root  9 May 20 17:54 wwn-0x5002538da014e727 -> ../../sda
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5002538da014e727-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5002538da014e727-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 May 20 17:54 wwn-0x5002538da014e727-part3 -> ../../sda3
*********************** END /dev/disk/by-id

*********************** BEGIN /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 May 20 17:54 18190bfb-e5e9-44dc-a705-eed694fe15d7 -> ../../sdb2
lrwxrwxrwx 1 root root 10 May 20 17:54 1ad465c9-5bf4-4430-81e9-4c54230c7347 -> ../../sda3
lrwxrwxrwx 1 root root 10 May 20 17:54 65f560ce-4cc0-4bb5-ab3b-f778f202311f -> ../../sdb5
lrwxrwxrwx 1 root root 10 May 20 17:54 7703-6332 -> ../../sdb3
lrwxrwxrwx 1 root root 10 May 20 17:54 96f7b45d-6ab5-466e-a9ab-9ff00774969d -> ../../sdb1
lrwxrwxrwx 1 root root 10 May 20 17:54 AAC3-4131 -> ../../sda1
lrwxrwxrwx 1 root root 10 May 20 17:54 a9099464-4d25-46db-b0d7-644e80bc0b6e -> ../../sdb9
lrwxrwxrwx 1 root root 10 May 20 17:54 c2042193-840f-435e-bed9-0d6124d177fb -> ../../sdb6
lrwxrwxrwx 1 root root 10 May 20 17:54 d64727a5-ce33-4fd8-83be-f941be9779f9 -> ../../sda2
lrwxrwxrwx 1 root root 10 May 20 17:54 ec399a4d-88e9-4726-a2ed-f3a8b79d64ae -> ../../sdb8
lrwxrwxrwx 1 root root 10 May 20 17:54 f5dadcf2-715a-4be4-92c4-d9ce10035a8a -> ../../sdb7
lrwxrwxrwx 1 root root 10 May 20 17:54 fb7e40d6-bc1d-447c-b907-accd056dc7eb -> ../../sdb4
*********************** END /dev/disk/by-uuid

-- System Information:
Debian Release: 10.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-16-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages grub-efi-amd64 depends on:
ii  debconf [debconf-2.0]  1.5.71
hi  grub-common            2.02+dfsg1-20+deb10u3
hi  grub-efi-amd64-bin     2.02+dfsg1-20+deb10u3
hi  grub2-common           2.02+dfsg1-20+deb10u3
ii  ucf                    3.0038+nmu1

grub-efi-amd64 recommends no packages.

grub-efi-amd64 suggests no packages.

-- debconf information:
* grub2/linux_cmdline_default: quiet splash i915.modeset=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=0 libata.force=noncq
  grub2/kfreebsd_cmdline_default: quiet
  grub2/force_efi_extra_removable: false
* grub2/linux_cmdline:
  grub2/update_nvram: true
  grub2/kfreebsd_cmdline:

From cjwatson at debian.org  Thu May 20 23:02:16 2021
From: cjwatson at debian.org (Colin Watson)
Date: Thu, 20 May 2021 23:02:16 +0100
Subject: Bug#988876: grub-efi-amd64: outb command no longer works
In-Reply-To: <162152719672.3212.13405676296549273045.reportbug@caspianmac>
References: <162152719672.3212.13405676296549273045.reportbug@caspianmac>
 <162152719672.3212.13405676296549273045.reportbug@caspianmac>
Message-ID: <20210520220216.GA13709@riva.ucam.org>

On Thu, May 20, 2021 at 06:13:16PM +0200, Marco K?hnel wrote:
> After a fresh install of debian buster a grub.cfg containing an outb command throws the error "outb command not found" (and, in my case, 
> cannot start lightdm thereafter). This problem does not appear when downgrading all installed grub packages to version 
> 2.02+dfsg1-20+deb10u3. 

Can you clarify whether you have UEFI Secure Boot enabled?  The outb
command had to be disabled in Secure Boot mode, because it could be used
to subvert boot security mechanisms.  Systems that use the outb command
will have to disable Secure Boot, or find some other way to achieve the
same effect.

>         outb 0x728 1
>         outb 0x710 2
>         outb 0x740 2
>         outb 0x750 0

I'm just noting explicitly here that these are local customizations to
grub.cfg (presumably by way of editing /etc/grub.d/10_linux or similar),
and not in the default setup.

-- 
Colin Watson (he/him)                              [cjwatson at debian.org]


From kuehnel at codecivil.de  Fri May 21 16:40:43 2021
From: kuehnel at codecivil.de (Marco =?UTF-8?Q?K=C3=BChnel?=)
Date: Fri, 21 May 2021 17:40:43 +0200
Subject: Bug#988876: grub-efi-amd64: outb command no longer works
In-Reply-To: <20210520220216.GA13709@riva.ucam.org>
References: <162152719672.3212.13405676296549273045.reportbug@caspianmac>
 <20210520220216.GA13709@riva.ucam.org>
 <162152719672.3212.13405676296549273045.reportbug@caspianmac>
Message-ID: <2202858.JmtnFXlOW0@caspiansea>

UEFI Secure Boot is disabled. The machine is a Macbook8,3 converted to a pure 
Linux box, however. So, the EFI firmware might be damaged. Thank you for the 
clarification.

In order to disable the (not properly supported) discrete graphics card, I 
need to execute the mentioned outb commands. Indeed, I edited /etc/grub.d/
10_linux in order to do this. 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-grub-devel/attachments/20210521/1871ca21/attachment.sig>

From russell at coker.com.au  Fri May 28 10:47:30 2021
From: russell at coker.com.au (Russell Coker)
Date: Fri, 28 May 2021 19:47:30 +1000
Subject: Bug#989201: "error: failed to get canonical path" is not informative
 enough
Message-ID: <162219525033.31490.3298436992693531101.reportbug@xev>

Package: grub-common
Version: 2.04-17
Severity: normal
Tags: upstream

root at xev:/# /usr/sbin/grub-probe --target=device /boot
/dev/sdh1
root at xev:/# chcon -t user_home_dir_t /boot
root at xev:/# /usr/sbin/grub-probe --target=device /boot
/usr/sbin/grub-probe: error: failed to get canonical path of `/boot'.

Above is an example of a permission error not being passed back to the user.
In the above example it should say "no permission to stat /boot" (or
something similar).  When googling this error I see cases where error
messages such as "%s is not a directory" or "directory %s does not exist"
would have allowed the user to solve their own problem without asking on
mailing lists or forums.

-- Package-specific info:

*********************** BEGIN /proc/mounts
/dev/mapper/root4 / btrfs rw,seclabel,noatime,ssd,space_cache,skip_balance,subvolid=5,subvol=/ 0 0
/dev/sdh1 /boot ext4 rw,seclabel,nodev,relatime 0 0
*********************** END /proc/mounts

*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod btrfs
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  6d8e3282-131f-4356-9c9c-f89761714d8e
else
  search --no-floppy --fs-uuid --set=root 6d8e3282-131f-4356-9c9c-f89761714d8e
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_AU
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
	set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-6d8e3282-131f-4356-9c9c-f89761714d8e' {
	load_video
	insmod gzio
	if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
	insmod part_msdos
	insmod ext2
	set root='hd1,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	else
	  search --no-floppy --fs-uuid --set=root 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	fi
	echo	'Loading Linux 5.10.0-6-amd64 ...'
	linux	/vmlinuz-5.10.0-6-amd64 root=UUID=6d8e3282-131f-4356-9c9c-f89761714d8e ro  
	echo	'Loading initial ramdisk ...'
	initrd	/initrd.img-5.10.0-6-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-6d8e3282-131f-4356-9c9c-f89761714d8e' {
	menuentry 'Debian GNU/Linux, with Linux 5.10.0-6-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-6-amd64-advanced-6d8e3282-131f-4356-9c9c-f89761714d8e' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd1,msdos1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
		else
		  search --no-floppy --fs-uuid --set=root 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
		fi
		echo	'Loading Linux 5.10.0-6-amd64 ...'
		linux	/vmlinuz-5.10.0-6-amd64 root=UUID=6d8e3282-131f-4356-9c9c-f89761714d8e ro  
		echo	'Loading initial ramdisk ...'
		initrd	/initrd.img-5.10.0-6-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 5.10.0-6-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-6-amd64-recovery-6d8e3282-131f-4356-9c9c-f89761714d8e' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd1,msdos1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
		else
		  search --no-floppy --fs-uuid --set=root 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
		fi
		echo	'Loading Linux 5.10.0-6-amd64 ...'
		linux	/vmlinuz-5.10.0-6-amd64 root=UUID=6d8e3282-131f-4356-9c9c-f89761714d8e ro single 
		echo	'Loading initial ramdisk ...'
		initrd	/initrd.img-5.10.0-6-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-16-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-16-amd64-advanced-6d8e3282-131f-4356-9c9c-f89761714d8e' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd1,msdos1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
		else
		  search --no-floppy --fs-uuid --set=root 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
		fi
		echo	'Loading Linux 4.19.0-16-amd64 ...'
		linux	/vmlinuz-4.19.0-16-amd64 root=UUID=6d8e3282-131f-4356-9c9c-f89761714d8e ro  
		echo	'Loading initial ramdisk ...'
		initrd	/initrd.img-4.19.0-16-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-16-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.19.0-16-amd64-recovery-6d8e3282-131f-4356-9c9c-f89761714d8e' {
		load_video
		insmod gzio
		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
		insmod part_msdos
		insmod ext2
		set root='hd1,msdos1'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
		else
		  search --no-floppy --fs-uuid --set=root 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
		fi
		echo	'Loading Linux 4.19.0-16-amd64 ...'
		linux	/vmlinuz-4.19.0-16-amd64 root=UUID=6d8e3282-131f-4356-9c9c-f89761714d8e ro single 
		echo	'Loading initial ramdisk ...'
		initrd	/initrd.img-4.19.0-16-amd64
	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
	insmod part_msdos
	insmod ext2
	set root='hd1,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	else
	  search --no-floppy --fs-uuid --set=root 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	fi
	linux16	/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
	insmod part_msdos
	insmod ext2
	set root='hd1,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	else
	  search --no-floppy --fs-uuid --set=root 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	fi
	linux16	/memtest86+.bin console=ttyS0,115200n8
}
menuentry "Memory test (memtest86+, experimental multiboot)" {
	insmod part_msdos
	insmod ext2
	set root='hd1,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	else
	  search --no-floppy --fs-uuid --set=root 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	fi
	multiboot	/memtest86+_multiboot.bin
}
menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
	insmod part_msdos
	insmod ext2
	set root='hd1,msdos1'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	else
	  search --no-floppy --fs-uuid --set=root 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0
	fi
	multiboot	/memtest86+_multiboot.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Debian GNU/Linux 11 (bullseye) (on /dev/sda2)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-simple-ff27171b-e5c7-4aeb-9f9a-145ac1f058e6' {
	insmod part_gpt
	insmod btrfs
	set root='hd0,gpt2'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
	else
	  search --no-floppy --fs-uuid --set=root ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
	fi
	linux /boot/vmlinuz-5.10.0-6-amd64 root=UUID=ff27171b-e5c7-4aeb-9f9a-145ac1f058e6 ro
	initrd /boot/initrd.img-5.10.0-6-amd64
}
submenu 'Advanced options for Debian GNU/Linux 11 (bullseye) (on /dev/sda2)' $menuentry_id_option 'osprober-gnulinux-advanced-ff27171b-e5c7-4aeb-9f9a-145ac1f058e6' {
	menuentry 'Debian GNU/Linux (on /dev/sda2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.0-6-amd64--ff27171b-e5c7-4aeb-9f9a-145ac1f058e6' {
		insmod part_gpt
		insmod btrfs
		set root='hd0,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		else
		  search --no-floppy --fs-uuid --set=root ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		fi
		linux /boot/vmlinuz-5.10.0-6-amd64 root=UUID=ff27171b-e5c7-4aeb-9f9a-145ac1f058e6 ro
		initrd /boot/initrd.img-5.10.0-6-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 5.10.0-6-amd64 (on /dev/sda2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.0-6-amd64--ff27171b-e5c7-4aeb-9f9a-145ac1f058e6' {
		insmod part_gpt
		insmod btrfs
		set root='hd0,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		else
		  search --no-floppy --fs-uuid --set=root ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		fi
		linux /boot/vmlinuz-5.10.0-6-amd64 root=UUID=ff27171b-e5c7-4aeb-9f9a-145ac1f058e6 ro
		initrd /boot/initrd.img-5.10.0-6-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 5.10.0-6-amd64 (recovery mode) (on /dev/sda2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-5.10.0-6-amd64-root=UUID=ff27171b-e5c7-4aeb-9f9a-145ac1f058e6 ro single-ff27171b-e5c7-4aeb-9f9a-145ac1f058e6' {
		insmod part_gpt
		insmod btrfs
		set root='hd0,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		else
		  search --no-floppy --fs-uuid --set=root ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		fi
		linux /boot/vmlinuz-5.10.0-6-amd64 root=UUID=ff27171b-e5c7-4aeb-9f9a-145ac1f058e6 ro single
		initrd /boot/initrd.img-5.10.0-6-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-16-amd64 (on /dev/sda2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.19.0-16-amd64--ff27171b-e5c7-4aeb-9f9a-145ac1f058e6' {
		insmod part_gpt
		insmod btrfs
		set root='hd0,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		else
		  search --no-floppy --fs-uuid --set=root ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		fi
		linux /boot/vmlinuz-4.19.0-16-amd64 root=UUID=ff27171b-e5c7-4aeb-9f9a-145ac1f058e6 ro
		initrd /boot/initrd.img-4.19.0-16-amd64
	}
	menuentry 'Debian GNU/Linux, with Linux 4.19.0-16-amd64 (recovery mode) (on /dev/sda2)' --class gnu-linux --class gnu --class os $menuentry_id_option 'osprober-gnulinux-/boot/vmlinuz-4.19.0-16-amd64-root=UUID=ff27171b-e5c7-4aeb-9f9a-145ac1f058e6 ro single-ff27171b-e5c7-4aeb-9f9a-145ac1f058e6' {
		insmod part_gpt
		insmod btrfs
		set root='hd0,gpt2'
		if [ x$feature_platform_search_hint = xy ]; then
		  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		else
		  search --no-floppy --fs-uuid --set=root ff27171b-e5c7-4aeb-9f9a-145ac1f058e6
		fi
		linux /boot/vmlinuz-4.19.0-16-amd64 root=UUID=ff27171b-e5c7-4aeb-9f9a-145ac1f058e6 ro single
		initrd /boot/initrd.img-4.19.0-16-amd64
	}
}

### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
*********************** END /boot/grub/grub.cfg

*********************** BEGIN /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10] 
md0 : active raid1 sda1[2] sdb1[3]
      306880 blocks super 1.2 [2/2] [UU]
      
unused devices: <none>
*********************** END /proc/mdstat

*********************** BEGIN /dev/disk/by-id
total 0
lrwxrwxrwx. 1 root root  9 May 28 17:53 ata-Samsung_SSD_850_EVO_500GB_S2R9NX0H610979N -> ../../sda
lrwxrwxrwx. 1 root root 10 May 28 17:53 ata-Samsung_SSD_850_EVO_500GB_S2R9NX0H610979N-part1 -> ../../sda1
lrwxrwxrwx. 1 root root 10 May 28 17:53 ata-Samsung_SSD_850_EVO_500GB_S2R9NX0H610979N-part2 -> ../../sda2
lrwxrwxrwx. 1 root root  9 May 28 17:53 ata-Samsung_SSD_860_EVO_500GB_S3YANB0K504260V -> ../../sdb
lrwxrwxrwx. 1 root root 10 May 28 17:53 ata-Samsung_SSD_860_EVO_500GB_S3YANB0K504260V-part1 -> ../../sdb1
lrwxrwxrwx. 1 root root 10 May 28 17:53 ata-Samsung_SSD_860_EVO_500GB_S3YANB0K504260V-part2 -> ../../sdb2
lrwxrwxrwx. 1 root root  9 May 28 17:53 ata-hp_CDDVDW_SH-216BB_R8TM68ED3000N0 -> ../../sr0
lrwxrwxrwx. 1 root root 10 May 28 18:09 dm-name-root3 -> ../../dm-2
lrwxrwxrwx. 1 root root 10 May 28 18:44 dm-name-root4 -> ../../dm-3
lrwxrwxrwx. 1 root root 10 May 28 18:09 dm-uuid-CRYPT-LUKS2-23178b50f2dc4672b888c183b45a2dfa-root3 -> ../../dm-2
lrwxrwxrwx. 1 root root 10 May 28 18:44 dm-uuid-CRYPT-LUKS2-6a793f6199b5437e962b0a7f13b2d219-root4 -> ../../dm-3
lrwxrwxrwx. 1 root root  9 May 28 17:53 md-name-xev:0 -> ../../md0
lrwxrwxrwx. 1 root root  9 May 28 17:53 md-uuid-62ee7b97:834bbe1c:672b5259:cb8af8d8 -> ../../md0
lrwxrwxrwx. 1 root root 13 May 28 18:05 nvme-CT1000P1SSD8_20502C60CACC -> ../../nvme1n1
lrwxrwxrwx. 1 root root 13 May 28 18:05 nvme-CT1000P1SSD8_20502C60E3FF -> ../../nvme0n1
lrwxrwxrwx. 1 root root 13 May 28 18:05 nvme-eui.000000000000000100a075202c60cacc -> ../../nvme1n1
lrwxrwxrwx. 1 root root 13 May 28 18:05 nvme-eui.000000000000000100a075202c60e3ff -> ../../nvme0n1
lrwxrwxrwx. 1 root root  9 May 28 17:53 usb-Generic-_Compact_Flash_20060413092100000-0:0 -> ../../sdc
lrwxrwxrwx. 1 root root  9 May 28 17:53 usb-Generic-_MS_MS-Pro_HG_20060413092100000-0:3 -> ../../sdf
lrwxrwxrwx. 1 root root  9 May 28 17:53 usb-Generic-_SD_MMC_20060413092100000-0:2 -> ../../sde
lrwxrwxrwx. 1 root root  9 May 28 17:53 usb-Generic-_SD_MMC_MS_MSPRO_20060413092100000-0:4 -> ../../sdg
lrwxrwxrwx. 1 root root  9 May 28 17:53 usb-Generic-_SM_xD-Picture_20060413092100000-0:1 -> ../../sdd
lrwxrwxrwx. 1 root root  9 May 28 17:54 usb-Generic_Flash_Disk_68D01787-0:0 -> ../../sdh
lrwxrwxrwx. 1 root root 10 May 28 17:54 usb-Generic_Flash_Disk_68D01787-0:0-part1 -> ../../sdh1
lrwxrwxrwx. 1 root root  9 May 28 17:53 wwn-0x5002538d40ffb8ed -> ../../sda
lrwxrwxrwx. 1 root root 10 May 28 17:53 wwn-0x5002538d40ffb8ed-part1 -> ../../sda1
lrwxrwxrwx. 1 root root 10 May 28 17:53 wwn-0x5002538d40ffb8ed-part2 -> ../../sda2
lrwxrwxrwx. 1 root root  9 May 28 17:53 wwn-0x5002538e40396e7f -> ../../sdb
lrwxrwxrwx. 1 root root 10 May 28 17:53 wwn-0x5002538e40396e7f-part1 -> ../../sdb1
lrwxrwxrwx. 1 root root 10 May 28 17:53 wwn-0x5002538e40396e7f-part2 -> ../../sdb2
*********************** END /dev/disk/by-id

*********************** BEGIN /dev/disk/by-uuid
total 0
lrwxrwxrwx. 1 root root 10 May 28 17:54 0cd55df8-fc99-4d69-a6bf-a5c4cd0434e0 -> ../../sdh1
lrwxrwxrwx. 1 root root  9 May 28 17:53 2101888c-108d-4b08-8a11-bb8209ba38fa -> ../../md0
lrwxrwxrwx. 1 root root 13 May 28 18:05 23178b50-f2dc-4672-b888-c183b45a2dfa -> ../../nvme0n1
lrwxrwxrwx. 1 root root 13 May 28 18:05 6a793f61-99b5-437e-962b-0a7f13b2d219 -> ../../nvme1n1
lrwxrwxrwx. 1 root root 10 May 28 17:53 9de0d847-9a85-4823-9904-d271e7e4504d -> ../../sdb2
lrwxrwxrwx. 1 root root 10 May 28 17:53 af42c6d4-c8bf-40ae-8290-346805205b78 -> ../../sda2
*********************** END /dev/disk/by-uuid

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-6-amd64 (SMP w/6 CPU threads)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default

Versions of packages grub-common depends on:
ii  gettext-base        0.21-4
ii  libc6               2.31-12
ii  libdevmapper1.02.1  2:1.02.175-2.1
ii  libefiboot1         37-6
ii  libefivar1          37-6
ii  libfreetype6        2.10.4+dfsg-1
ii  libfuse2            2.9.9-5
ii  liblzma5            5.2.5-2

Versions of packages grub-common recommends:
ii  os-prober  1.78

Versions of packages grub-common suggests:
ii  console-setup  1.202
ii  desktop-base   11.0.3
pn  grub-emu       <none>
ii  mtools         4.0.26-1
pn  multiboot-doc  <none>
pn  xorriso        <none>

-- no debconf information


From etienne at edechamps.fr  Sat May 29 12:00:25 2021
From: etienne at edechamps.fr (Etienne Dechamps)
Date: Sat, 29 May 2021 12:00:25 +0100
Subject: Bug#848945: #848945 Empty rpool leaves ZFS systems unbootable
References: <20161221040446.7468.29533.reportbug@hephaestus.lan.complete.org>
Message-ID: <CAAAz6HQpgtkArOAMaqZ-z9n-_u-8GVWMp4uY7h0oCH6-hvSVHA@mail.gmail.com>

Control: found -1 2.04-18

I just hit this bug. It rendered my system unbootable because my root
ZFS pool has the new zstd compression feature enabled, and it looks
like grub-probe choked on that.

There are two things that I found highly frustrating here:

- While my root (/) is on ZFS, my /boot is not, precisely to try to
avoid issues like these. In this setup GRUB doesn't need to be able to
read the zpool - all that matters is the name of the pool, which can
be trivially determined without the need for any kind of subtle
low-level probing. It seems like as long as the
bootloader/kernel/initrd itself is not stored on ZFS, GRUB should Just
Work regardless of the low-level zpool details (such as zpool
features). That is not presently the case because /etc/grub.d/10_linux
insists on using grub-probe and grub-probe insists on using its own
custom low-level ZFS read code just to figure out the name of the
zpool. That's just... silly.

- The error handling here is appalling. In my case update-grub
(grub-mkconfig) *did not even display a single error message*. The
"unknown filesystem" error from grub-probe is being swallowed somehow,
and /etc/grub.d/10_linux doesn't check that the returned `rpool` looks
valid. update-grub will happily generate an obviously garbage,
unbootable config with a syntactically invalid root=ZFS= kernel
parameter and everything will look fine at first... until you try to
reboot! At the very least an error message should be displayed;
ideally update-grub should refuse to generate a new config altogether,
to avoid replacing a working config with a broken one.

By the way, here are steps to reproduce to make grub-probe choke on a
ZFS pool with zstd enabled:

# dd if=/dev/zero of=/tmp/pool bs=1 count=1 seek=$((128*1024*1024))
# zpool create testpool /tmp/pool
# zfs set compression=zstd testpool
# /usr/sbin/grub-probe --device /tmp/pool --target=fs_label
/usr/sbin/grub-probe: error: unknown filesystem.

If the "zfs set compression" step is omitted, grub-probe works. Tested
with zfs 2.0.3-8.


From owner at bugs.debian.org  Sat May 29 12:03:03 2021
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sat, 29 May 2021 11:03:03 +0000
Subject: Processed: #848945 Empty rpool leaves ZFS systems unbootable
References: <CAAAz6HQpgtkArOAMaqZ-z9n-_u-8GVWMp4uY7h0oCH6-hvSVHA@mail.gmail.com>
 <20161221040446.7468.29533.reportbug@hephaestus.lan.complete.org>
Message-ID: <handler.s.B848945.16222860474987.transcript@bugs.debian.org>

Processing control commands:

> found -1 2.04-18
Bug #848945 [grub-common] grub-common: Empty rpool leaves ZFS systems unbootable
Marked as found in versions grub2/2.04-18.

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


From etienne at edechamps.fr  Sat May 29 12:49:52 2021
From: etienne at edechamps.fr (Etienne Dechamps)
Date: Sat, 29 May 2021 12:49:52 +0100
Subject: Bug#848945: #848945 Empty rpool leaves ZFS systems unbootable
In-Reply-To: <CAAAz6HQpgtkArOAMaqZ-z9n-_u-8GVWMp4uY7h0oCH6-hvSVHA@mail.gmail.com>
References: <20161221040446.7468.29533.reportbug@hephaestus.lan.complete.org>
 <CAAAz6HQpgtkArOAMaqZ-z9n-_u-8GVWMp4uY7h0oCH6-hvSVHA@mail.gmail.com>
 <20161221040446.7468.29533.reportbug@hephaestus.lan.complete.org>
Message-ID: <CAAAz6HR_RN=TGYwpaCyoazGOYPU=YRFkvCeUQ=MBuXkD8L25bg@mail.gmail.com>

By the way, for those who don't like patching packaged files, here's a
workaround for manually overriding the root= parameter from
/etc/default/grub:

GRUB_FS=manual
GRUB_DISABLE_LINUX_UUID=true
GRUB_DEVICE=ZFS=yourpoolname/path/to/your/root/dataset


From joseph at maher.org.uk  Sat May 29 17:00:17 2021
From: joseph at maher.org.uk (Joseph Maher)
Date: Sat, 29 May 2021 12:00:17 -0400 (EDT)
Subject: Bug#989229: grub-install: warning: Cannot read EFI Boot* variables.
Message-ID: <alpine.DEB.2.21.2105291157550.2653@ariadne>


Package: grub2-common
Version: 2.04-17
Severity: grave
Justification: renders package unusable


grub seems unhappy on my laptop (testing=bullseye, acer spin 1), currently 
grub-install doesn't work, and so the various grub packages aren't 
installable / upgradable

Not sure what the severity should be, or which package I should file a bug 
against, but I've appended some typical output below that may or may not 
be useful:

Yours

Joseph


# grub-install --target=x86_64-efi
Installing for x86_64-efi platform.
grub-install: warning: Cannot read EFI Boot* variables.
grub-install: warning: efivarfs_get_variable: read failed: Interrupted system call.
grub-install: warning: efi_get_variable: ops->get_variable failed: Interrupted system call.
grub-install: error: failed to register the EFI boot entry: Interrupted system call.


# grub-install --target=x86_64-efi --debug

This output is very verbose, but I've left a copy here:

https://www.maher.org.uk/~joseph/20210529-grub-install.log



# efibootmgr 
Skipping unreadable variable "Boot0000": Interrupted system call
Skipping unreadable variable "Boot0001": Interrupted system call
Skipping unreadable variable "Boot0002": Interrupted system call
Skipping unreadable variable "Boot0003": Interrupted system call
Skipping unreadable variable "Boot0005": Interrupted system call
Skipping unreadable variable "Boot0008": Interrupted system call
Skipping unreadable variable "Boot000B": Interrupted system call
Skipping unreadable variable "Boot000E": Interrupted system call
Skipping unreadable variable "Boot0011": Interrupted system call
Skipping unreadable variable "Boot0014": Interrupted system call
Skipping unreadable variable "Boot0017": Interrupted system call
Skipping unreadable variable "Boot2001": Interrupted system call
Skipping unreadable variable "Boot2002": Interrupted system call
Skipping unreadable variable "Boot2003": Interrupted system call
show_order(): Interrupted system call


# efivar -l
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0003
8be4df61-93ca-11d2-aa0d-00e098032b8c-dbxDefault
8be4df61-93ca-11d2-aa0d-00e098032b8c-dbDefault
8be4df61-93ca-11d2-aa0d-00e098032b8c-KEKDefault
8be4df61-93ca-11d2-aa0d-00e098032b8c-PKDefault
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0017
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0014
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0011
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot000E
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot000B
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0008
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0005
89cb0e8d-393c-4830-bfff-65d9147e8c3b-AUPS
89cb0e8d-393c-4830-bfff-65d9147e8c3b-ACUB
8be4df61-93ca-11d2-aa0d-00e098032b8c-OsIndications
a9b5f8d2-cb6d-42c2-bc01-b5ffaae4335e-PBRDevicePath
d719b2cb-3d3a-4596-a3bc-dad00e67656f-db
8be4df61-93ca-11d2-aa0d-00e098032b8c-KEK
8be4df61-93ca-11d2-aa0d-00e098032b8c-PK
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0002
eaec226f-c9a3-477a-a826-ddc716cdc0e3-OfflineUniqueIDEKPubCRC
eaec226f-c9a3-477a-a826-ddc716cdc0e3-OfflineUniqueIDEKPub
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0001
89cb0e8d-393c-4830-bfff-65d9147e8c3b-WBSN
89cb0e8d-393c-4830-bfff-65d9147e8c3b-WBMN
59d1c24f-50f1-401a-b101-f33e0daed443-TargetHddDevPath
a04a27f4-df00-4d42-b552-39511302113d-BootType
8be4df61-93ca-11d2-aa0d-00e098032b8c-BootOrder
bf661981-1bce-42fc-abc4-716d8531aac5-WIFICTL
89cb0e8d-393c-4830-bfff-65d9147e8c3b-ASSN
0d9a1427-e02a-437d-926b-aa521fd722ba-PciLanInfo
04b37fe8-f6ae-480b-bdd5-37d98c5e89aa-VarErrorFlag
89cb0e8d-393c-4830-bfff-65d9147e8c3b-AEBT
0a4cd120-ea2d-4aef-a4b0-b0c08cbbdbbe-BootDevice
59d1c24f-50f1-401a-b101-f33e0daed443-PhysicalBootOrder
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0000
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot2003
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot2002
8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot2001
59d1c24f-50f1-401a-b101-f33e0daed443-EMMC_DTR
89cb0e8d-393c-4830-bfff-65d9147e8c3b-SMAC
89cb0e8d-393c-4830-bfff-65d9147e8c3b-SMAB
89cb0e8d-393c-4830-bfff-65d9147e8c3b-SMAA
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOut
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConIn
8be4df61-93ca-11d2-aa0d-00e098032b8c-Timeout
89cb0e8d-393c-4830-bfff-65d9147e8c3b-A01LastSataPortPresent
89cb0e8d-393c-4830-bfff-65d9147e8c3b-ABRV
a04a27f4-df00-4d42-b552-39511302113d-Custom
59d1c24f-50f1-401a-b101-f33e0daed443-CustomPlatformLang
89cb0e8d-393c-4830-bfff-65d9147e8c3b-ACFB
59d1c24f-50f1-401a-b101-f33e0daed443-AdministerSecureBoot
89cb0e8d-393c-4830-bfff-65d9147e8c3b-ASTM
aeb9c5c1-94f1-4d02-bfd9-4602db2d3c54-Tcg2PhysicalPresence
aeb9c5c1-94f1-4d02-bfd9-4602db2d3c54-Tcg2PhysicalPresenceFlags
e20939be-32d4-41be-a150-897f85d49829-MemoryOverwriteRequestControl
89cb0e8d-393c-4830-bfff-65d9147e8c3b-AFBD
89cb0e8d-393c-4830-bfff-65d9147e8c3b-AACV
382af2bb-ffff-abcd-aaee-cce099338877-SecureFlashInfo
8be4df61-93ca-11d2-aa0d-00e098032b8c-PlatformLang
8be4df61-93ca-11d2-aa0d-00e098032b8c-Lang
fd21bf2b-f5d1-46c5-aee3-c60158339239-MsdmAddress
eb704011-1402-11d3-8e77-00a0c969723b-MTC
89cb0e8d-393c-4830-bfff-65d9147e8c3b-AT2D3
89cb0e8d-393c-4830-bfff-65d9147e8c3b-AT2D2
89cb0e8d-393c-4830-bfff-65d9147e8c3b-AT2D1
89cb0e8d-393c-4830-bfff-65d9147e8c3b-AT2D0
59d1c24f-50f1-401a-b101-f33e0daed443-CustomSecurity
59d1c24f-50f1-401a-b101-f33e0daed443-RestoreFactoryDefault
59d1c24f-50f1-401a-b101-f33e0daed443-SecureBootEnforce
d719b2cb-3d3a-4596-a3bc-dad00e67656f-dbx
59d1c24f-50f1-401a-b101-f33e0daed443-certdb
89cb0e8d-393c-4830-bfff-65d9147e8c3b-WBOA
8be4df61-93ca-11d2-aa0d-00e098032b8c-SecureBoot
8be4df61-93ca-11d2-aa0d-00e098032b8c-SetupMode
aaf32c78-947b-439a-a180-2e144ec37792-AuthVarKeyDatabase
bb983ccf-151d-40e1-a07b-4a17be168292-MemoryOverwriteRequestControlLock
a04a27f4-df00-4d42-b552-39511302113d-Setup
5bce4c83-6a97-444b-63b4-672c014742ff-IrsiInfo
9cfa1ece-4488-49be-9a4b-e9b511826577-SSRAMBASE
8be4df61-93ca-11d2-aa0d-00e098032b8c-BootCurrent
39473de5-df3b-49a1-9fa6-41b35b36fa39-DynamicBar
39473de5-df3b-49a1-9fa6-41b35b36fa39-FixedBar
8be4df61-93ca-11d2-aa0d-00e098032b8c-ErrOutDev
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConInDev
59d1c24f-50f1-401a-b101-f33e0daed443-ConOutCandidateDev
8be4df61-93ca-11d2-aa0d-00e098032b8c-ConOutDev
59d1c24f-50f1-401a-b101-f33e0daed443-ConInCandidateDev
19ad5244-fd6b-4e5c-826a-414646d6da6a-PlatformInfo
8be4df61-93ca-11d2-aa0d-00e098032b8c-PlatformLangCodes
8be4df61-93ca-11d2-aa0d-00e098032b8c-LangCodes
8be4df61-93ca-11d2-aa0d-00e098032b8c-VendorKeys
8be4df61-93ca-11d2-aa0d-00e098032b8c-SignatureSupport
8be4df61-93ca-11d2-aa0d-00e098032b8c-OsIndicationsSupported






-- Package-specific info:

*********************** BEGIN /proc/mounts
/dev/mapper/chekhov--vg-root / btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ 0 0
/dev/mmcblk0p2 /boot ext2 rw,relatime 0 0
/dev/mmcblk0p1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/mapper/mmcblk1p1_crypt /home/maher btrfs rw,relatime,ssd,space_cache,subvolid=5,subvol=/ 0 0
*********************** END /proc/mounts

*********************** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
   set have_grubenv=true
   load_env
fi
if [ "${next_entry}" ] ; then
    set default="${next_entry}"
    set next_entry=
    save_env next_entry
    set boot_once=true
else
    set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
   menuentry_id_option="--id"
else
   menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
   set saved_entry="${prev_saved_entry}"
   save_env saved_entry
   set prev_saved_entry=
   save_env prev_saved_entry
   set boot_once=true
fi

function savedefault {
   if [ -z "${boot_once}" ]; then
     saved_entry="${chosen}"
     save_env saved_entry
   fi
}
function load_video {
   if [ x$feature_all_video_module = xy ]; then
     insmod all_video
   else
     insmod efi_gop
     insmod efi_uga
     insmod ieee1275_fb
     insmod vbe
     insmod vga
     insmod video_bochs
     insmod video_cirrus
   fi
}

if [ x$feature_default_font_path = xy ] ; then
    font=unicode
else
insmod lvm
insmod btrfs
set root='lvmid/ORyqe8-tFfK-w5p2-ZksD-RWtq-U94O-dVYeIU/utNdXv-L1eK-rHGS-FONR-NsL7-dnzb-eTP9f1'
if [ x$feature_platform_search_hint = xy ]; then
   search --no-floppy --fs-uuid --set=root --hint='lvmid/ORyqe8-tFfK-w5p2-ZksD-RWtq-U94O-dVYeIU/utNdXv-L1eK-rHGS-FONR-NsL7-dnzb-eTP9f1'  90ae93fe-053b-43f0-bc0c-2c6deace60d2
else
   search --no-floppy --fs-uuid --set=root 90ae93fe-053b-43f0-bc0c-2c6deace60d2
fi
     font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
   set gfxmode=auto
   load_video
   insmod gfxterm
   set locale_dir=$prefix/locale
   set lang=en_US
   insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
   set timeout=30
else
   if [ x$feature_timeout_style = xy ] ; then
     set timeout_style=menu
     set timeout=5
   # Fallback normal timeout code in case the timeout_style feature is
   # unavailable.
   else
     set timeout=5
   fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
 	set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 	load_video
 	insmod gzio
 	if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
 	insmod part_gpt
 	insmod ext2
 	if [ x$feature_platform_search_hint = xy ]; then
 	  search --no-floppy --fs-uuid --set=root  2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 	else
 	  search --no-floppy --fs-uuid --set=root 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 	fi
 	echo	'Loading Linux 5.10.0-6-amd64 ...'
 	linux	/vmlinuz-5.10.0-6-amd64 root=/dev/mapper/chekhov--vg-root ro  quiet
 	echo	'Loading initial ramdisk ...'
 	initrd	/initrd.img-5.10.0-6-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 	menuentry 'Debian GNU/Linux, with Linux 5.10.0-6-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-6-amd64-advanced-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 		load_video
 		insmod gzio
 		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
 		insmod part_gpt
 		insmod ext2
 		if [ x$feature_platform_search_hint = xy ]; then
 		  search --no-floppy --fs-uuid --set=root  2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		else
 		  search --no-floppy --fs-uuid --set=root 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		fi
 		echo	'Loading Linux 5.10.0-6-amd64 ...'
 		linux	/vmlinuz-5.10.0-6-amd64 root=/dev/mapper/chekhov--vg-root ro  quiet
 		echo	'Loading initial ramdisk ...'
 		initrd	/initrd.img-5.10.0-6-amd64
 	}
 	menuentry 'Debian GNU/Linux, with Linux 5.10.0-6-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-6-amd64-recovery-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 		load_video
 		insmod gzio
 		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
 		insmod part_gpt
 		insmod ext2
 		if [ x$feature_platform_search_hint = xy ]; then
 		  search --no-floppy --fs-uuid --set=root  2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		else
 		  search --no-floppy --fs-uuid --set=root 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		fi
 		echo	'Loading Linux 5.10.0-6-amd64 ...'
 		linux	/vmlinuz-5.10.0-6-amd64 root=/dev/mapper/chekhov--vg-root ro single
 		echo	'Loading initial ramdisk ...'
 		initrd	/initrd.img-5.10.0-6-amd64
 	}
 	menuentry 'Debian GNU/Linux, with Linux 5.10.0-5-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-5-amd64-advanced-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 		load_video
 		insmod gzio
 		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
 		insmod part_gpt
 		insmod ext2
 		if [ x$feature_platform_search_hint = xy ]; then
 		  search --no-floppy --fs-uuid --set=root  2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		else
 		  search --no-floppy --fs-uuid --set=root 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		fi
 		echo	'Loading Linux 5.10.0-5-amd64 ...'
 		linux	/vmlinuz-5.10.0-5-amd64 root=/dev/mapper/chekhov--vg-root ro  quiet
 		echo	'Loading initial ramdisk ...'
 		initrd	/initrd.img-5.10.0-5-amd64
 	}
 	menuentry 'Debian GNU/Linux, with Linux 5.10.0-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-5-amd64-recovery-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 		load_video
 		insmod gzio
 		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
 		insmod part_gpt
 		insmod ext2
 		if [ x$feature_platform_search_hint = xy ]; then
 		  search --no-floppy --fs-uuid --set=root  2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		else
 		  search --no-floppy --fs-uuid --set=root 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		fi
 		echo	'Loading Linux 5.10.0-5-amd64 ...'
 		linux	/vmlinuz-5.10.0-5-amd64 root=/dev/mapper/chekhov--vg-root ro single
 		echo	'Loading initial ramdisk ...'
 		initrd	/initrd.img-5.10.0-5-amd64
 	}
 	menuentry 'Debian GNU/Linux, with Linux 5.10.0-3-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-3-amd64-advanced-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 		load_video
 		insmod gzio
 		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
 		insmod part_gpt
 		insmod ext2
 		if [ x$feature_platform_search_hint = xy ]; then
 		  search --no-floppy --fs-uuid --set=root  2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		else
 		  search --no-floppy --fs-uuid --set=root 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		fi
 		echo	'Loading Linux 5.10.0-3-amd64 ...'
 		linux	/vmlinuz-5.10.0-3-amd64 root=/dev/mapper/chekhov--vg-root ro  quiet
 		echo	'Loading initial ramdisk ...'
 		initrd	/initrd.img-5.10.0-3-amd64
 	}
 	menuentry 'Debian GNU/Linux, with Linux 5.10.0-3-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.10.0-3-amd64-recovery-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 		load_video
 		insmod gzio
 		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
 		insmod part_gpt
 		insmod ext2
 		if [ x$feature_platform_search_hint = xy ]; then
 		  search --no-floppy --fs-uuid --set=root  2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		else
 		  search --no-floppy --fs-uuid --set=root 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		fi
 		echo	'Loading Linux 5.10.0-3-amd64 ...'
 		linux	/vmlinuz-5.10.0-3-amd64 root=/dev/mapper/chekhov--vg-root ro single
 		echo	'Loading initial ramdisk ...'
 		initrd	/initrd.img-5.10.0-3-amd64
 	}
 	menuentry 'Debian GNU/Linux, with Linux 5.9.0-4-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.9.0-4-amd64-advanced-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 		load_video
 		insmod gzio
 		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
 		insmod part_gpt
 		insmod ext2
 		if [ x$feature_platform_search_hint = xy ]; then
 		  search --no-floppy --fs-uuid --set=root  2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		else
 		  search --no-floppy --fs-uuid --set=root 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		fi
 		echo	'Loading Linux 5.9.0-4-amd64 ...'
 		linux	/vmlinuz-5.9.0-4-amd64 root=/dev/mapper/chekhov--vg-root ro  quiet
 		echo	'Loading initial ramdisk ...'
 		initrd	/initrd.img-5.9.0-4-amd64
 	}
 	menuentry 'Debian GNU/Linux, with Linux 5.9.0-4-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.9.0-4-amd64-recovery-90ae93fe-053b-43f0-bc0c-2c6deace60d2' {
 		load_video
 		insmod gzio
 		if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
 		insmod part_gpt
 		insmod ext2
 		if [ x$feature_platform_search_hint = xy ]; then
 		  search --no-floppy --fs-uuid --set=root  2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		else
 		  search --no-floppy --fs-uuid --set=root 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e
 		fi
 		echo	'Loading Linux 5.9.0-4-amd64 ...'
 		linux	/vmlinuz-5.9.0-4-amd64 root=/dev/mapper/chekhov--vg-root ro single
 		echo	'Loading initial ramdisk ...'
 		initrd	/initrd.img-5.9.0-4-amd64
 	}
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
   source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
   source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
*********************** END /boot/grub/grub.cfg

*********************** BEGIN /proc/mdstat
cat: /proc/mdstat: No such file or directory
*********************** END /proc/mdstat

*********************** BEGIN LVM
   --- Volume group ---
   VG Name               chekhov-vg
   System ID
   Format                lvm2
   Metadata Areas        1
   Metadata Sequence No  3
   VG Access             read/write
   VG Status             resizable
   MAX LV                0
   Cur LV                2
   Open LV               2
   Max PV                0
   Cur PV                1
   Act PV                1
   VG Size               28.12 GiB
   PE Size               4.00 MiB
   Total PE              7200
   Alloc PE / Size       7200 / 28.12 GiB
   Free  PE / Size       0 / 0
   VG UUID               ORyqe8-tFfK-w5p2-ZksD-RWtq-U94O-dVYeIU

   --- Physical volume ---
   PV Name               /dev/mapper/mmcblk0p3_crypt
   VG Name               chekhov-vg
   PV Size               <28.13 GiB / not usable 2.00 MiB
   Allocatable           yes (but full)
   PE Size               4.00 MiB
   Total PE              7200
   Free PE               0
   Allocated PE          7200
   PV UUID               uBewrr-FuXc-OY8N-1Hvv-KcAW-HxFb-G8k3dc

   --- Logical volume ---
   LV Path                /dev/chekhov-vg/root
   LV Name                root
   VG Name                chekhov-vg
   LV UUID                utNdXv-L1eK-rHGS-FONR-NsL7-dnzb-eTP9f1
   LV Write Access        read/write
   LV Creation host, time chekhov, 2021-02-11 09:31:01 -0500
   LV Status              available
   # open                 1
   LV Size                <27.17 GiB
   Current LE             6955
   Segments               1
   Allocation             inherit
   Read ahead sectors     auto
   - currently set to     256
   Block device           254:1

   --- Logical volume ---
   LV Path                /dev/chekhov-vg/swap_1
   LV Name                swap_1
   VG Name                chekhov-vg
   LV UUID                u3SIBS-o5K6-F9vA-28b7-3J9s-y3GA-G2YK4d
   LV Write Access        read/write
   LV Creation host, time chekhov, 2021-02-11 09:31:01 -0500
   LV Status              available
   # open                 2
   LV Size                980.00 MiB
   Current LE             245
   Segments               1
   Allocation             inherit
   Read ahead sectors     auto
   - currently set to     256
   Block device           254:2

*********************** END LVM

*********************** BEGIN /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 10 May 29 11:10 dm-name-chekhov--vg-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 May 29 11:10 dm-name-chekhov--vg-swap_1 -> ../../dm-2
lrwxrwxrwx 1 root root 10 May 29 11:10 dm-name-mmcblk0p3_crypt -> ../../dm-0
lrwxrwxrwx 1 root root 10 May 29 11:10 dm-name-mmcblk1p1_crypt -> ../../dm-3
lrwxrwxrwx 1 root root 10 May 29 11:10 dm-uuid-CRYPT-LUKS2-38eaff4d7f3042f8bdbf6c1a785b8022-mmcblk1p1_crypt -> ../../dm-3
lrwxrwxrwx 1 root root 10 May 29 11:10 dm-uuid-CRYPT-LUKS2-6e686fada86748ec93a8cd1d25e2fffe-mmcblk0p3_crypt -> ../../dm-0
lrwxrwxrwx 1 root root 10 May 29 11:10 dm-uuid-LVM-ORyqe8tFfKw5p2ZksDRWtqU94OdVYeIUu3SIBSo5K6F9vA28b73J9sy3GAG2YK4d -> ../../dm-2
lrwxrwxrwx 1 root root 10 May 29 11:10 dm-uuid-LVM-ORyqe8tFfKw5p2ZksDRWtqU94OdVYeIUutNdXvL1eKrHGSFONRNsL7dnzbeTP9f1 -> ../../dm-1
lrwxrwxrwx 1 root root 10 May 29 11:10 lvm-pv-uuid-uBewrr-FuXc-OY8N-1Hvv-KcAW-HxFb-G8k3dc -> ../../dm-0
lrwxrwxrwx 1 root root 13 May 29 11:10 mmc-BJNB4R_0x3d884dbc -> ../../mmcblk0
lrwxrwxrwx 1 root root 15 May 29 11:10 mmc-BJNB4R_0x3d884dbc-part1 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 May 29 11:10 mmc-BJNB4R_0x3d884dbc-part2 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 May 29 11:10 mmc-BJNB4R_0x3d884dbc-part3 -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 13 May 29 11:10 mmc-SN512_0x73781504 -> ../../mmcblk1
lrwxrwxrwx 1 root root 15 May 29 11:10 mmc-SN512_0x73781504-part1 -> ../../mmcblk1p1
*********************** END /dev/disk/by-id

*********************** BEGIN /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 10 May 29 11:10 19c607d4-3ab6-44c0-8134-d4fc518bb519 -> ../../dm-3
lrwxrwxrwx 1 root root 15 May 29 11:10 2176d1b1-0fb2-49aa-8651-2c2d7a8eb99e -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 May 29 11:10 38eaff4d-7f30-42f8-bdbf-6c1a785b8022 -> ../../mmcblk1p1
lrwxrwxrwx 1 root root 15 May 29 11:10 6e686fad-a867-48ec-93a8-cd1d25e2fffe -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 10 May 29 11:10 90ae93fe-053b-43f0-bc0c-2c6deace60d2 -> ../../dm-1
lrwxrwxrwx 1 root root 15 May 29 11:10 B65F-015F -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 10 May 29 11:10 a311c620-d232-4161-aca5-ff930c00c5a6 -> ../../dm-2
*********************** END /dev/disk/by-uuid

-- System Information:
Debian Release: 11.0
   APT prefers testing-security
   APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages grub2-common depends on:
ii  dpkg                1.20.9
ii  grub-common         2.04-17
ii  install-info        6.7.0.dfsg.2-6
ii  libc6               2.31-12
ii  libdevmapper1.02.1  2:1.02.175-2.1
ii  libefiboot1         37-6
ii  libefivar1          37-6
ii  liblzma5            5.2.5-2

grub2-common recommends no packages.

grub2-common suggests no packages.

-- no debconf information


From owner at bugs.debian.org  Sun May 30 20:48:19 2021
From: owner at bugs.debian.org (Debian Bug Tracking System)
Date: Sun, 30 May 2021 19:48:19 +0000
Subject: Processed (with 2 errors): BTS housekeeping and severity adjustments
References: <20210530194458.GB20679@localhost>
Message-ID: <handler.s.C.162240390327210.transcript@bugs.debian.org>

Processing commands for control at bugs.debian.org:

> severity 983618 serious
Bug #983618 [python3-django] python3-django 3.2 breaks python3-django-pyscss
Severity set to 'serious' from 'important'
> severity 989245 serious
Bug #989245 [python3-django] python3-django needs to depends on libjs-jquery, not only recommend this package
Severity set to 'serious' from 'important'
> severity 946447 serious
Bug #946447 [thefuck] thefuck: does not start without python3-distutils installed
Severity set to 'serious' from 'important'
> forwarded 946349 https://github.com/bit-team/backintime/issues/974
Bug #946349 [backintime-qt] backintime-qt: Backup initiated from the GUI overwrites remote backup path permissions to 0700
Set Bug forwarded-to-address to 'https://github.com/bit-team/backintime/issues/974'.
> tags 946349 fixed-upstream patch
Bug #946349 [backintime-qt] backintime-qt: Backup initiated from the GUI overwrites remote backup path permissions to 0700
Added tag(s) fixed-upstream.
> severity 946349 serious
Bug #946349 [backintime-qt] backintime-qt: Backup initiated from the GUI overwrites remote backup path permissions to 0700
Severity set to 'serious' from 'important'
> forwarded 946620 https://bugs.gnu.org/38574
Bug #946620 [diffutils] diff called 'GNU'
Set Bug forwarded-to-address to 'https://bugs.gnu.org/38574'.
> tags 946620 patch fixed-upstream
Bug #946620 [diffutils] diff called 'GNU'
Added tag(s) fixed-upstream and patch.
> severity 946620 minor
Bug #946620 [diffutils] diff called 'GNU'
Severity set to 'minor' from 'important'
> unarchive 938327
Bug #938327 {Done: Ritesh Raj Sarraf <rrs at debian.org>} [src:rabbitvcs] rabbitvcs: Python2 removal in sid/bullseye
Unarchived Bug 938327
> reassign 942778 src:rabbitvcs
Bug #942778 [rabbitvcs-nautilus] rabbitvcs-nautilus: Please port to python3-nautlius
Bug reassigned from package 'rabbitvcs-nautilus' to 'src:rabbitvcs'.
No longer marked as found in versions rabbitvcs/0.17.1-3.
Ignoring request to alter fixed versions of bug #942778 to the same values previously set
> forcemerge 938327 942778
Bug #938327 {Done: Ritesh Raj Sarraf <rrs at debian.org>} [src:rabbitvcs] rabbitvcs: Python2 removal in sid/bullseye
Bug #942778 [src:rabbitvcs] rabbitvcs-nautilus: Please port to python3-nautlius
Set Bug forwarded-to-address to 'https://github.com/rabbitvcs/rabbitvcs/issues/279'.
Severity set to 'serious' from 'important'
Failed to forcibly merge 938327: Failure while trying to adjust bugs, please report this as a bug: Not altering archived bugs; see unarchive..
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

> affects 938327 rabbitvcs-nautilus
Bug #938327 {Done: Ritesh Raj Sarraf <rrs at debian.org>} [src:rabbitvcs] rabbitvcs: Python2 removal in sid/bullseye
Added indication that 938327 affects rabbitvcs-nautilus
> severity 940911 serious
Bug #940911 [grub2] TPM error are fatal
Severity set to 'serious' from 'important'
> forwarded 939497 https://github.com/mgrouchy/django-stronghold/issues/75
Bug #939497 [python3-django-stronghold] AttributeError: 'method' object has no attribute 'STRONGHOLD_IS_PUBLIC'
Set Bug forwarded-to-address to 'https://github.com/mgrouchy/django-stronghold/issues/75'.
> tags 939497 fixed-upstream
Bug #939497 [python3-django-stronghold] AttributeError: 'method' object has no attribute 'STRONGHOLD_IS_PUBLIC'
Added tag(s) fixed-upstream.
> severity 939497 serious
Bug #939497 [python3-django-stronghold] AttributeError: 'method' object has no attribute 'STRONGHOLD_IS_PUBLIC'
Severity set to 'serious' from 'important'
> severity 936052 serious
Bug #936052 [amavisd-new] amavisd-new: Missing dependency on  libnet-snmp-perl
Severity set to 'serious' from 'important'
> unarchive 943999
Bug #943999 {Done: Debian FTP Masters <ftpmaster at ftp-master.debian.org>} [src:pulseaudio] Drop /usr/lib/systemd/user/sockets.target.wants/pulseaudio.socket symlink
Unarchived Bug 943999
> forcemerge 943999 935405
Bug #943999 {Done: Debian FTP Masters <ftpmaster at ftp-master.debian.org>} [src:pulseaudio] Drop /usr/lib/systemd/user/sockets.target.wants/pulseaudio.socket symlink
Unable to merge bugs because:
package of #935405 is 'pulseaudio' not 'src:pulseaudio'
Failed to forcibly merge 943999: Did not alter merged bugs.

> severity 934713 serious
Bug #934713 [os-prober] os-prober: missing dependency on mount
Severity set to 'serious' from 'important'
> unarchive 935096
Bug #935096 {Done: Andreas Beckmann <anbe at debian.org>} [console-common] install-keymap(8) binary not included although package description tells so
Unarchived Bug 935096
> reassign 933873 console-common
Bug #933873 [src:console-common] console-common: install-keymap utility missing from 0.7.90
Bug reassigned from package 'src:console-common' to 'console-common'.
No longer marked as found in versions console-common/0.7.90.
Ignoring request to alter fixed versions of bug #933873 to the same values previously set
> forcemerge 935096 933873
Bug #935096 {Done: Andreas Beckmann <anbe at debian.org>} [console-common] install-keymap(8) binary not included although package description tells so
Bug #933873 [console-common] console-common: install-keymap utility missing from 0.7.90
Severity set to 'grave' from 'important'
Marked Bug as done
Marked as fixed in versions console-common/0.7.90+deb10u1 and console-common/0.7.91.
Marked as found in versions console-common/0.7.90.
Added tag(s) patch.
Merged 933873 935096
> severity 932501 serious
Bug #932501 [src:squid-deb-proxy] squid-deb-proxy: daemon does not start due to the conf file not being allowed by apparmor
Severity set to 'serious' from 'important'
> forwarded 932008 http://www.gedanken.org.uk/viewvc/procmeter3?view=revision&revision=407
Bug #932008 [procmeter3] stat-disk.so: undefined symbol: minor
Set Bug forwarded-to-address to 'http://www.gedanken.org.uk/viewvc/procmeter3?view=revision&revision=407'.
> tags 932008 patch fixed-upstream
Bug #932008 [procmeter3] stat-disk.so: undefined symbol: minor
Added tag(s) fixed-upstream.
> severity 932008 serious
Bug #932008 [procmeter3] stat-disk.so: undefined symbol: minor
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
932008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932008
932501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932501
933873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933873
934713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934713
935096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935096
935405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935405
936052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936052
938327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938327
939497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939497
940911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940911
942778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942778
943999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943999
946349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946349
946447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946447
946620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946620
983618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983618
989245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989245
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems


From alex.bennee at linaro.org  Fri May 28 16:03:16 2021
From: alex.bennee at linaro.org (Alex =?utf-8?Q?Benn=C3=A9e?=)
Date: Fri, 28 May 2021 15:03:16 -0000
Subject: What's missing for arm64 Xen boot with FDT via Grub in Debian
 Bullseye?
Message-ID: <87mtse2ac8.fsf@linaro.org>


Hi,

I'm currently trying to pull together the threads for booting Xen on
Debian. I'm currently doing this within QEMU's TCG emulation and the
"virt" machine model:

  -machine type=virt,virtualization=on,gic-version=3 \
  -cpu max,pauth-impdef=on

with the firmware on my Ubuntu machine:

  -drive if=pflash,file=/usr/share/AAVMF/AAVMF_CODE.fd,format=raw,readonly=on -drive if=pflash,file=$HOME/images/AAVMF_VARS.fd,format=raw

(qemu-efi-aarch64 Version: 0~20180205.c0d9813c-2ubuntu0.3)

When booting this way I get the Grub menu and Xen is loaded by Grub but
falls over later:

  (XEN) MODULE[0]: 00000000f5869000 - 00000000f59b60c8 Xen
  (XEN) MODULE[1]: 000000013857d000 - 0000000138580000 Device Tree
  (XEN) MODULE[2]: 00000000f73a1000 - 00000000f8da0780 Kernel
  (XEN) MODULE[3]: 00000000f59b7000 - 00000000f739f99b Ramdisk
  (XEN)
  (XEN) CMDLINE[00000000f73a1000]:chosen placeholder root=UUID=435201aa-c5cf-4e7a-8107-5eef28844188 ro console=hvc0
  (XEN)
  (XEN) Command line: placeholder dom0_mem=2G loglvl=all guest_loglvl=all no-real-mode edd=off
  (XEN) parameter "placeholder" unknown!
  (XEN) parameter "no-real-mode" unknown!
  (XEN) parameter "edd" unknown!
  (XEN) Domain heap initialised
  (XEN) Booting using Device Tree
  (XEN) Platform: Generic System
  (XEN)
  (XEN) ****************************************
  (XEN) Panic on CPU 0:
  (XEN) Unable to find a compatible timer in the device tree
  (XEN) ****************************************

It seems like there are bits of the DT missing. I can however
successfully boot Xen with the Linux guest using the guest-loader device
and bypassing the firmware/boot code step. This gives:

  (XEN) MODULE[0]: 0000000040200000 - 000000004034d0c8 Xen
  (XEN) MODULE[1]: 0000000048000000 - 0000000048100000 Device Tree
  (XEN) MODULE[2]: 0000000046000000 - 0000000046eb2200 Kernel
  (XEN)
  (XEN) CMDLINE[0000000046000000]:chosen root=/dev/sda2 console=hvc0 earlyprintk=xen
  (XEN)
  (XEN) Command line: dom0_mem=4G dom0_max_vcpus=4
  (XEN) Domain heap initialised
  (XEN) Booting using Device Tree
  (XEN) Platform: Generic System
  (XEN) Taking dtuart configuration from /chosen/stdout-path
  (XEN) Looking for dtuart at "/pl011 at 9000000", options ""
   Xen 4.15.1-pre
  (XEN) Xen version 4.15.1-pre (alex.bennee@) (aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0) debug=y Tue May 18 09:34:55 UTC 2021
  (XEN) Latest ChangeSet:
  (XEN) build-id: a50d8f03a1a15662ac7c4e5f73f2f544a6739df2
  (XEN) Processor: 411fd070: "ARM Limited", variant: 0x1, part 0xd07, rev 0x0
  (XEN) 64-bit Execution:
  (XEN)   Processor Features: 0000000001000222 0000000000000000
  (XEN)     Exception Levels: EL3:No EL2:64+32 EL1:64+32 EL0:64+32
  (XEN)     Extensions: FloatingPoint AdvancedSIMD GICv3-SysReg
  (XEN)   Debug Features: 0000000010305106 0000000000000000
  (XEN)   Auxiliary Features: 0000000000000000 0000000000000000
  (XEN)   Memory Model Features: 0000000000001124 0000000000000000
  (XEN)   ISA Features:  0000000000011120 0000000000000000
  (XEN) 32-bit Execution:
  (XEN)   Processor Features: 00000131:10011001
  (XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
  (XEN)     Extensions: GenericTimer
  (XEN)   Debug Features: 03010066
  (XEN)   Auxiliary Features: 00000000
  (XEN)   Memory Model Features: 10101105 40000000 01260000 02102211
  (XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
  (XEN) Using SMC Calling Convention v1.0
  (XEN) Using PSCI v0.2
  (XEN) SMP: Allowing 8 CPUs
  (XEN) enabled workaround for: ARM erratum 832075
  (XEN) enabled workaround for: ARM erratum 834220
  (XEN) enabled workaround for: ARM erratum 1319367
  (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 62500 KHz
  (XEN) GICv3 initialization:
  (XEN)       gic_dist_addr=0x00000008000000
  (XEN)       gic_maintenance_irq=25
  (XEN)       gic_rdist_stride=0
  (XEN)       gic_rdist_regions=1
  (XEN)       redistributor regions:
  (XEN)         - region 0: 0x000000080a0000 - 0x00000009000000
  (XEN) GICv3: 256 lines, (IID 0000043b).
  (XEN) GICv3: CPU0: Found redistributor in region 0 @000000004001c000

Attempting to boot with acpi=on still sees Grub attempt to use DT to
boot the hypervisor. However selecting the kernel directly boots with
ACPI (which is a shame as I'd like to see what FDT it gets presented
with).

The full command line for booting via the guest-loader is:

  ./qemu-system-aarch64 \
    -machine virt,virtualization=on,gic-version=3 \
    -cpu max,pauth-impdef=on \
    -serial mon:stdio \
    -netdev user,id=net1,hostfwd=tcp::2222-:22 \
    -device virtio-net-pci,netdev=net1 \
    -device virtio-scsi-pci \
    -drive file=/dev/zvol/hackpool-0/debian-buster-arm64,id=hd0,index=0,if=none,format=raw \
    -device scsi-hd,drive=hd0 \
    -display none \
    -m 16384 \
    -kernel ~/lsrc/xen/xen.build.arm64-xen/xen/xen \
    -append "dom0_mem=4G dom0_max_vcpus=4" \
    -device guest-loader,addr=0x46000000,kernel=$HOME/lsrc/linux.git/builds/arm64/arch/arm64/boot/Image,bootargs="root=/dev/sda2 console=hvc0 earlyprintk=xen" \
    -smp 8

So some questions:

  - is Xen on arm64 tested on Debian Bullseye? If so what platform?
  - how do I tell Grub to do a straight FDT boot with the DT from the firmware?
  - are there any missing pieces I should be aware of?

I appreciate that ACPI is the preferred enterprise way of booting but at
the moment I think FDT is probably preferred because:

  - lack of real HW with decent ACPI (my MachiatoBin only boots with DT)
  - I want to try additional hypervisors who don't have ACPI aware implementations

That said if I can get an ACPI version of Xen booting via Grub that
would be an improvement.

-- 
Alex Benn?e


From julien at xen.org  Fri May 28 17:13:15 2021
From: julien at xen.org (Julien Grall)
Date: Fri, 28 May 2021 16:13:15 -0000
Subject: What's missing for arm64 Xen boot with FDT via Grub in Debian
 Bullseye?
In-Reply-To: <87mtse2ac8.fsf@linaro.org>
References: <87mtse2ac8.fsf@linaro.org>
Message-ID: <0df82c26-078a-83de-952c-cbad06b3ad2d@xen.org>



On 28/05/2021 13:49, Alex Benn?e wrote:
> 
> Hi,

Hi Alex,

> I'm currently trying to pull together the threads for booting Xen on
> Debian. I'm currently doing this within QEMU's TCG emulation and the
> "virt" machine model:
> 
>    -machine type=virt,virtualization=on,gic-version=3 \
>    -cpu max,pauth-impdef=on
> 
> with the firmware on my Ubuntu machine:
> 
>    -drive if=pflash,file=/usr/share/AAVMF/AAVMF_CODE.fd,format=raw,readonly=on -drive if=pflash,file=$HOME/images/AAVMF_VARS.fd,format=raw
> 
> (qemu-efi-aarch64 Version: 0~20180205.c0d9813c-2ubuntu0.3)
> 
> When booting this way I get the Grub menu and Xen is loaded by Grub but
> falls over later:
> 
>    (XEN) MODULE[0]: 00000000f5869000 - 00000000f59b60c8 Xen
>    (XEN) MODULE[1]: 000000013857d000 - 0000000138580000 Device Tree
>    (XEN) MODULE[2]: 00000000f73a1000 - 00000000f8da0780 Kernel
>    (XEN) MODULE[3]: 00000000f59b7000 - 00000000f739f99b Ramdisk
>    (XEN)
>    (XEN) CMDLINE[00000000f73a1000]:chosen placeholder root=UUID=435201aa-c5cf-4e7a-8107-5eef28844188 ro console=hvc0
>    (XEN)
>    (XEN) Command line: placeholder dom0_mem=2G loglvl=all guest_loglvl=all no-real-mode edd=off
>    (XEN) parameter "placeholder" unknown!
>    (XEN) parameter "no-real-mode" unknown!
>    (XEN) parameter "edd" unknown!
>    (XEN) Domain heap initialised
>    (XEN) Booting using Device Tree
>    (XEN) Platform: Generic System
>    (XEN)
>    (XEN) ****************************************
>    (XEN) Panic on CPU 0:
>    (XEN) Unable to find a compatible timer in the device tree
>    (XEN) ****************************************
> 
> It seems like there are bits of the DT missing. I can however
> successfully boot Xen with the Linux guest using the guest-loader device
> and bypassing the firmware/boot code step. This gives:
> 
>    (XEN) MODULE[0]: 0000000040200000 - 000000004034d0c8 Xen
>    (XEN) MODULE[1]: 0000000048000000 - 0000000048100000 Device Tree
>    (XEN) MODULE[2]: 0000000046000000 - 0000000046eb2200 Kernel
>    (XEN)
>    (XEN) CMDLINE[0000000046000000]:chosen root=/dev/sda2 console=hvc0 earlyprintk=xen
>    (XEN)
>    (XEN) Command line: dom0_mem=4G dom0_max_vcpus=4
>    (XEN) Domain heap initialised
>    (XEN) Booting using Device Tree
>    (XEN) Platform: Generic System
>    (XEN) Taking dtuart configuration from /chosen/stdout-path
>    (XEN) Looking for dtuart at "/pl011 at 9000000", options ""
>     Xen 4.15.1-pre
>    (XEN) Xen version 4.15.1-pre (alex.bennee@) (aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0) debug=y Tue May 18 09:34:55 UTC 2021
>    (XEN) Latest ChangeSet:
>    (XEN) build-id: a50d8f03a1a15662ac7c4e5f73f2f544a6739df2
>    (XEN) Processor: 411fd070: "ARM Limited", variant: 0x1, part 0xd07, rev 0x0
>    (XEN) 64-bit Execution:
>    (XEN)   Processor Features: 0000000001000222 0000000000000000
>    (XEN)     Exception Levels: EL3:No EL2:64+32 EL1:64+32 EL0:64+32
>    (XEN)     Extensions: FloatingPoint AdvancedSIMD GICv3-SysReg
>    (XEN)   Debug Features: 0000000010305106 0000000000000000
>    (XEN)   Auxiliary Features: 0000000000000000 0000000000000000
>    (XEN)   Memory Model Features: 0000000000001124 0000000000000000
>    (XEN)   ISA Features:  0000000000011120 0000000000000000
>    (XEN) 32-bit Execution:
>    (XEN)   Processor Features: 00000131:10011001
>    (XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
>    (XEN)     Extensions: GenericTimer
>    (XEN)   Debug Features: 03010066
>    (XEN)   Auxiliary Features: 00000000
>    (XEN)   Memory Model Features: 10101105 40000000 01260000 02102211
>    (XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
>    (XEN) Using SMC Calling Convention v1.0
>    (XEN) Using PSCI v0.2
>    (XEN) SMP: Allowing 8 CPUs
>    (XEN) enabled workaround for: ARM erratum 832075
>    (XEN) enabled workaround for: ARM erratum 834220
>    (XEN) enabled workaround for: ARM erratum 1319367
>    (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 62500 KHz
>    (XEN) GICv3 initialization:
>    (XEN)       gic_dist_addr=0x00000008000000
>    (XEN)       gic_maintenance_irq=25
>    (XEN)       gic_rdist_stride=0
>    (XEN)       gic_rdist_regions=1
>    (XEN)       redistributor regions:
>    (XEN)         - region 0: 0x000000080a0000 - 0x00000009000000
>    (XEN) GICv3: 256 lines, (IID 0000043b).
>    (XEN) GICv3: CPU0: Found redistributor in region 0 @000000004001c000
> 
> Attempting to boot with acpi=on still sees Grub attempt to use DT to
> boot the hypervisor. However selecting the kernel directly boots with
> ACPI (which is a shame as I'd like to see what FDT it gets presented
> with).

ACPI is not built by default in Xen on Arm. You will need to select it 
from Kconfig and rebuild the hypervisor.

> 
> The full command line for booting via the guest-loader is:
> 
>    ./qemu-system-aarch64 \
>      -machine virt,virtualization=on,gic-version=3 \
>      -cpu max,pauth-impdef=on \
>      -serial mon:stdio \
>      -netdev user,id=net1,hostfwd=tcp::2222-:22 \
>      -device virtio-net-pci,netdev=net1 \
>      -device virtio-scsi-pci \
>      -drive file=/dev/zvol/hackpool-0/debian-buster-arm64,id=hd0,index=0,if=none,format=raw \
>      -device scsi-hd,drive=hd0 \
>      -display none \
>      -m 16384 \
>      -kernel ~/lsrc/xen/xen.build.arm64-xen/xen/xen \
>      -append "dom0_mem=4G dom0_max_vcpus=4" \
>      -device guest-loader,addr=0x46000000,kernel=$HOME/lsrc/linux.git/builds/arm64/arch/arm64/boot/Image,bootargs="root=/dev/sda2 console=hvc0 earlyprintk=xen" \
>      -smp 8
> 
> So some questions:
> 
>    - is Xen on arm64 tested on Debian Bullseye? If so what platform?

I am using Debian Bullseye on QEMU and also the FVP. We are also using 
Debian in Osstest for all the testing (it is possible an older version 
of Debian).

>    - how do I tell Grub to do a straight FDT boot with the DT from the firmware?

Is the firmware actually providing a DT? You could try to boot Xen from 
UEFI directly to confirm that.

However, I vaguely recall that GRUB may only pass ACPI if it is provided.

>    - are there any missing pieces I should be aware of?

Other than re-building Xen with ACPI=y, I am not aware of any issue to 
use Xen with Debian bullseye.

Cheers,

-- 
Julien Grall


From alex.bennee at linaro.org  Fri May 28 18:30:28 2021
From: alex.bennee at linaro.org (Alex =?utf-8?Q?Benn=C3=A9e?=)
Date: Fri, 28 May 2021 17:30:28 -0000
Subject: What's missing for arm64 Xen boot with FDT via Grub in Debian
 Bullseye?
In-Reply-To: <0df82c26-078a-83de-952c-cbad06b3ad2d@xen.org>
References: <87mtse2ac8.fsf@linaro.org>
 <0df82c26-078a-83de-952c-cbad06b3ad2d@xen.org>
Message-ID: <878s3y22bz.fsf@linaro.org>


Julien Grall <julien at xen.org> writes:

> On 28/05/2021 13:49, Alex Benn?e wrote:
>> Hi,
>
> Hi Alex,
>
>> I'm currently trying to pull together the threads for booting Xen on
>> Debian. I'm currently doing this within QEMU's TCG emulation and the
>> "virt" machine model:
>>    -machine type=virt,virtualization=on,gic-version=3 \
>>    -cpu max,pauth-impdef=on
>> with the firmware on my Ubuntu machine:
>>    -drive
>> if=pflash,file=/usr/share/AAVMF/AAVMF_CODE.fd,format=raw,readonly=on
>> -drive if=pflash,file=$HOME/images/AAVMF_VARS.fd,format=raw
>> (qemu-efi-aarch64 Version: 0~20180205.c0d9813c-2ubuntu0.3)
>> When booting this way I get the Grub menu and Xen is loaded by Grub
>> but
>> falls over later:
>>    (XEN) MODULE[0]: 00000000f5869000 - 00000000f59b60c8 Xen
>>    (XEN) MODULE[1]: 000000013857d000 - 0000000138580000 Device Tree
>>    (XEN) MODULE[2]: 00000000f73a1000 - 00000000f8da0780 Kernel
>>    (XEN) MODULE[3]: 00000000f59b7000 - 00000000f739f99b Ramdisk
>>    (XEN)
>>    (XEN) CMDLINE[00000000f73a1000]:chosen placeholder root=UUID=435201aa-c5cf-4e7a-8107-5eef28844188 ro console=hvc0
>>    (XEN)
>>    (XEN) Command line: placeholder dom0_mem=2G loglvl=all guest_loglvl=all no-real-mode edd=off
>>    (XEN) parameter "placeholder" unknown!
>>    (XEN) parameter "no-real-mode" unknown!
>>    (XEN) parameter "edd" unknown!
>>    (XEN) Domain heap initialised
>>    (XEN) Booting using Device Tree
>>    (XEN) Platform: Generic System
>>    (XEN)
>>    (XEN) ****************************************
>>    (XEN) Panic on CPU 0:
>>    (XEN) Unable to find a compatible timer in the device tree
>>    (XEN) ****************************************
>> It seems like there are bits of the DT missing. I can however
>> successfully boot Xen with the Linux guest using the guest-loader device
>> and bypassing the firmware/boot code step. This gives:
>>    (XEN) MODULE[0]: 0000000040200000 - 000000004034d0c8 Xen
>>    (XEN) MODULE[1]: 0000000048000000 - 0000000048100000 Device Tree
>>    (XEN) MODULE[2]: 0000000046000000 - 0000000046eb2200 Kernel
>>    (XEN)
>>    (XEN) CMDLINE[0000000046000000]:chosen root=/dev/sda2 console=hvc0 earlyprintk=xen
>>    (XEN)
>>    (XEN) Command line: dom0_mem=4G dom0_max_vcpus=4
>>    (XEN) Domain heap initialised
>>    (XEN) Booting using Device Tree
>>    (XEN) Platform: Generic System
>>    (XEN) Taking dtuart configuration from /chosen/stdout-path
>>    (XEN) Looking for dtuart at "/pl011 at 9000000", options ""
>>     Xen 4.15.1-pre
>>    (XEN) Xen version 4.15.1-pre (alex.bennee@) (aarch64-linux-gnu-gcc (Debian 8.3.0-2) 8.3.0) debug=y Tue May 18 09:34:55 UTC 2021
>>    (XEN) Latest ChangeSet:
>>    (XEN) build-id: a50d8f03a1a15662ac7c4e5f73f2f544a6739df2
>>    (XEN) Processor: 411fd070: "ARM Limited", variant: 0x1, part 0xd07, rev 0x0
>>    (XEN) 64-bit Execution:
>>    (XEN)   Processor Features: 0000000001000222 0000000000000000
>>    (XEN)     Exception Levels: EL3:No EL2:64+32 EL1:64+32 EL0:64+32
>>    (XEN)     Extensions: FloatingPoint AdvancedSIMD GICv3-SysReg
>>    (XEN)   Debug Features: 0000000010305106 0000000000000000
>>    (XEN)   Auxiliary Features: 0000000000000000 0000000000000000
>>    (XEN)   Memory Model Features: 0000000000001124 0000000000000000
>>    (XEN)   ISA Features:  0000000000011120 0000000000000000
>>    (XEN) 32-bit Execution:
>>    (XEN)   Processor Features: 00000131:10011001
>>    (XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
>>    (XEN)     Extensions: GenericTimer
>>    (XEN)   Debug Features: 03010066
>>    (XEN)   Auxiliary Features: 00000000
>>    (XEN)   Memory Model Features: 10101105 40000000 01260000 02102211
>>    (XEN)  ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
>>    (XEN) Using SMC Calling Convention v1.0
>>    (XEN) Using PSCI v0.2
>>    (XEN) SMP: Allowing 8 CPUs
>>    (XEN) enabled workaround for: ARM erratum 832075
>>    (XEN) enabled workaround for: ARM erratum 834220
>>    (XEN) enabled workaround for: ARM erratum 1319367
>>    (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 62500 KHz
>>    (XEN) GICv3 initialization:
>>    (XEN)       gic_dist_addr=0x00000008000000
>>    (XEN)       gic_maintenance_irq=25
>>    (XEN)       gic_rdist_stride=0
>>    (XEN)       gic_rdist_regions=1
>>    (XEN)       redistributor regions:
>>    (XEN)         - region 0: 0x000000080a0000 - 0x00000009000000
>>    (XEN) GICv3: 256 lines, (IID 0000043b).
>>    (XEN) GICv3: CPU0: Found redistributor in region 0 @000000004001c000
>> Attempting to boot with acpi=on still sees Grub attempt to use DT to
>> boot the hypervisor. However selecting the kernel directly boots with
>> ACPI (which is a shame as I'd like to see what FDT it gets presented
>> with).
>
> ACPI is not built by default in Xen on Arm. You will need to select it
> from Kconfig and rebuild the hypervisor.

OK so I think what was happening is grub was always passing ACPI and
with Xen not built for it there was simply no DTB to process. Testing
with a ACPI build works for Bullseye.

Testing on Buster Xen does boot but hangs at:

  (XEN) *** LOADING DOMAIN 0 ***
  (XEN) Loading d0 kernel from boot module @ 00000000f7d2d000
  (XEN) Loading ramdisk from boot module @ 00000000f304b000
  (XEN) Allocating 1:1 mappings totalling 2048MB for dom0:
  (XEN) BANK[0] 0x00000040000000-0x000000c0000000 (2048MB)
  (XEN) Grant table range: 0x000000f2ef5000-0x000000f2f35000
  (XEN) Allocating PPI 16 for event channel interrupt
  (XEN) Loading zImage from 00000000f7d2d000 to 0000000040080000-0000000041264780
  (XEN) Loading d0 initrd from 00000000f304b000 to 0x0000000048200000-0x000000004cee0c00
  (XEN) Loading d0 DTB to 0x0000000048000000-0x000000004800027f
  (XEN) Initial low memory virq threshold set at 0x4000 pages.
  (XEN) Scrubbing Free RAM in background
  (XEN) Std. Loglevel: All
  (XEN) Guest Loglevel: All
  (XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
  (XEN) Freed 380kB init memory.


I'll need to update by build environment and rebuild for Bullseye to
check I can still start a new domain.

>
>> The full command line for booting via the guest-loader is:
>>    ./qemu-system-aarch64 \
>>      -machine virt,virtualization=on,gic-version=3 \
>>      -cpu max,pauth-impdef=on \
>>      -serial mon:stdio \
>>      -netdev user,id=net1,hostfwd=tcp::2222-:22 \
>>      -device virtio-net-pci,netdev=net1 \
>>      -device virtio-scsi-pci \
>>      -drive file=/dev/zvol/hackpool-0/debian-buster-arm64,id=hd0,index=0,if=none,format=raw \
>>      -device scsi-hd,drive=hd0 \
>>      -display none \
>>      -m 16384 \
>>      -kernel ~/lsrc/xen/xen.build.arm64-xen/xen/xen \
>>      -append "dom0_mem=4G dom0_max_vcpus=4" \
>>      -device guest-loader,addr=0x46000000,kernel=$HOME/lsrc/linux.git/builds/arm64/arch/arm64/boot/Image,bootargs="root=/dev/sda2 console=hvc0 earlyprintk=xen" \
>>      -smp 8
>> So some questions:
>>    - is Xen on arm64 tested on Debian Bullseye? If so what platform?
>
> I am using Debian Bullseye on QEMU and also the FVP. We are also using
> Debian in Osstest for all the testing (it is possible an older version
> of Debian).
>
>>    - how do I tell Grub to do a straight FDT boot with the DT from the firmware?
>
> Is the firmware actually providing a DT? You could try to boot Xen
> from UEFI directly to confirm that.
>
> However, I vaguely recall that GRUB may only pass ACPI if it is provided.
>
>>    - are there any missing pieces I should be aware of?
>
> Other than re-building Xen with ACPI=y, I am not aware of any issue to
> use Xen with Debian bullseye.
>
> Cheers,


-- 
Alex Benn?e