On Wed, Oct 14, 2020 at 08:04:19AM -0000, sudodus wrote: > The current Groovy iso files of Lubuntu and Xubuntu have a later date > and time (from zsync), yet they fail to boot the HP Elitebook 8560p.
> Is this because the latest tweak suggested by Thomas Schmitt is only > present in the Ubuntu Groovy iso file, or is there some other cause of > this difference? All Ubuntu flavors use the same bootloader logic; there is no distinction here. And I have checked that the latest xubuntu image has the same partition setup. Ubuntu 20201014: $ fdisk groovy-desktop-amd64.iso Welcome to fdisk (util-linux 2.34). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk groovy-desktop-amd64.iso: 2.76 GiB, 2939303936 bytes, 5740828 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: B4C6B0BE-D645-4E64-8EB9-B4C4C650029D Device Start End Sectors Size Type groovy-desktop-amd64.iso1 64 5730211 5730148 2.7G Microsoft basic data groovy-desktop-amd64.iso2 5730212 5740163 9952 4.9M EFI System groovy-desktop-amd64.iso3 5740164 5740763 600 300K Microsoft basic data Command (m for help): M Entering protective/hybrid MBR disklabel. Command (m for help): p Disk groovy-desktop-amd64.iso: 2.76 GiB, 2939303936 bytes, 5740828 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type groovy-desktop-amd64.iso1 1 5740827 5740827 2.8G ee GPT groovy-desktop-amd64.iso2 * 0 0 1 512B 0 Empty Partition table entries are not in disk order. Command (m for help): q $ Xubuntu 20201014: $ fdisk groovy-desktop-amd64.iso Welcome to fdisk (util-linux 2.34). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Command (m for help): p Disk groovy-desktop-amd64.iso: 1.71 GiB, 1814708224 bytes, 3544352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 5F95C427-857C-4F99-A8DA-0BDAD813137F Device Start End Sectors Size Type groovy-desktop-amd64.iso1 64 3533735 3533672 1.7G Microsoft basic data groovy-desktop-amd64.iso2 3533736 3543687 9952 4.9M EFI System groovy-desktop-amd64.iso3 3543688 3544287 600 300K Microsoft basic data Command (m for help): M Entering protective/hybrid MBR disklabel. Command (m for help): p Disk groovy-desktop-amd64.iso: 1.71 GiB, 1814708224 bytes, 3544352 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Device Boot Start End Sectors Size Id Type groovy-desktop-amd64.iso1 1 3544351 3544351 1.7G ee GPT groovy-desktop-amd64.iso2 * 0 0 1 512B 0 Empty Partition table entries are not in disk order. Command (m for help): q $ So a failure to boot Xubuntu where Ubuntu works is not explained by missing/different xorriso options. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
