grub 2.04 could not boot from iso at UEFI native environment

[Seiichi Nakashima]

Dear everyone

I use ubuntu-20.04.1 at my UEFI CSM environment desktop PC.
grub 2.04 can boot from iso file.
and I use ubuntu-18.04.5 at my UEFI native environment note PC.
grub 2.02 can boot from iso file.

I check to boot from iso using ubuntu-20.04.1 liveCD usb at note PC.
I power on note PC, and selecting boot device to use UEFI boot manager.
then grub 2.04 boot menu displayed.

I change Boot from next volume to iso boot.
iso boot step as same as grub 2.02 definition.
but grub 2.04 could not boot from iso, display black screen.
I power off note PC.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: nakasima 1542 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-05-29 (120 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp.
 Bus 001 Device 003: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Jumper EZbook
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=86097f4a-e2d9-4432-8006-816cf4c322c3 ro ipv6.disable=1 quiet
ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-48-generic N/A
 linux-backports-modules-5.4.0-48-generic N/A
 linux-firmware 1.173.19
Tags: bionic
Uname: Linux 5.4.0-48-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/01/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
dmi.board.asset.tag: Default string
dmi.board.name: EZbook
dmi.board.vendor: Jumper
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: EZbook
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Jumper

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Seiichi Nakashima (ubuntu-linuxer)]

apport information

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Woodrow Shen (woodrow-shen)]

Hi can you try to add nomodeset into kernel parameter? basically 20.04 image should work with UEFI/secure boot, and that's what I did set up for all my machines/laptops. For example, one of my machines is Intel NUC7 and it was installed by 20.04. Or, Maybe you can update BIOS if it has the latest version available.

[Seiichi Nakashima (ubuntu-linuxer)]

thank you mail.

I change grub 2.04 paramater to add nomodeset.
but nothing occure.
I boot up ubuntu-20.04.1 usb,
then I challenge boot up ubuntu-20.04.1 iso from disk,
grub 2.04 linux line add to nomodeset.

==

2020-09-27 (日) の 07:13 +0000 に Woodrow Shen さんは書きました:
> Hi can you try to add nomodeset into kernel parameter? basically
> 20.04
> image should work with UEFI/secure boot, and that's what I did set up
> for all my machines/laptops. For example, one of my machines is Intel
> NUC7 and it was installed by 20.04. Or, Maybe you can update BIOS if
> it
> has the latest version available.
>

[Seiichi Nakashima (ubuntu-linuxer)]

This is not a bug, I found a grub parameter in web.
I update my NotePC from ubuntu-18.04.5 to ubuntu-20.04.1.
thank you

[Julian Andres Klode (juliank)]

@Seiichi Please explain. You said yourself this is not a bug, so I marked it as invalid, so why did you reopen it?

I also don't see how this is supposed to be a bug in the bootloader in the first place.

[Seiichi Nakashima (ubuntu-linuxer)]

I am sorry.

I confirm to understand that this is not bug.
I do not want to reopen.
I do not understand invalid status mean,
I thought I need to comfirm it.

=

> @Seiichi Please explain. You said yourself this is not a bug, so I
> marked it as invalid, so why did you reopen it?
>
> I also don't see how this is supposed to be a bug in the bootloader
> in
> the first place.
>

[Julian Andres Klode (juliank)]

Setting to Invalid again, then.