I am working with these current iso files: $ md5sum ../[lx]ubuntu/groovy-desktop-amd64.iso 5d4756194e6d917b45584a10109f8e0e ../lubuntu/groovy-desktop-amd64.iso 8ad63bfc247563dae765af648ea62b47 ../xubuntu/groovy-desktop-amd64.iso
and, Leo, I looked at the links provided by Steve. Now a cloned USB drive with the current daily Lubuntu Groovy can boot a Lenovo V130 (usnig Linpus Live) in UEFI mode with secure boot :-) I notice another difference: A third partition is created (during the boot process), but no file system is recognized by lsblk -f, and it is not used for logging (as we are used to from Focal and previous versions of Groovy). Is this intended, or a bug? -o- But now there are problems in another computer and BIOS mode. A cloned USB drive with the current daily Lubuntu Groovy fails to boot a Dell Latitude E7240 in BIOS mode (alias legacy mode) with the error message: isolinux.bin missing or corrupt. Selected boot device failed. Press any key to reboot the system. This computer can boot in UEFI mode. The same things happened, when I tested the cloned USB drive with the current daily Lubuntu Groovy in a Toshiba satellite-pro-c850-19w 'isolinux.bin missing or corrupt' in BIOS mode, and it works in UEFI mode (also with secure boot). -o- I tested with a cloned USB drive with the current daily Xubuntu Groovy system. And I had exactly the same boot behaviour as with Lubuntu in the three computers tested. -- 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/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
