Hi,
> There was a problem with permissions.
Hm. I should make xorriso report this. No read permission should not
count as blank pseudo-medium.
What kind of permission was missing and which change fixed it ?
> This test.iso file modified according to comment #181, when cloned,
> makes USB drive that can boot the Lenovo V130 in UEFI mode with secure
> boot.
> > -boot_image any replay \
> > -boot_image any appended_part_as=gpt \
> > -boot_image any mbr_force_bootable=off
So it wants to see a valid GPT.
grub-mkrescue produces this by default.
Does installation to the stick by usb-pack-efi produce GPT ?
There remains the riddle why the V130 booted with older Ubuntus which
have an invalid GPT. (I assume that it does. Does it ?)
Even the 20201007.1 ISO had an invalid GPT, much like older Ubuntus.
Whatever, this success will probably not happen with Leó Kolbeinsson's
Lenovo V14 IIL, as it does not boot by grub-mkreascue.
Nevertheless, it would be worth a try. Just to be sure.
------------------------------------------------------------------------
I am running out of ideas. Open questions are:
- does Lenovo V14 IIL boot with
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.6.0-amd64-netinst.iso
which has an old Fedora/Debian/Ubunto partition layout ?
- with which publicly downloadable ISO does V14 IIL boot at all ?
Do i get it right that the problems currently only affect sudodus'
Lenovo V130 and Leó Kolbeinsson's Lenovo V14 IIL ?
Any other machines which do not boot by the newest Ubuntu ISOs ?
(E.g. 20201008, MD5 0ca0a6242caffcb7c67497fc659f2b8c).
Have a nice day :)
Thomas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886148
Title:
failure to boot groovy daily
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1886148/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
