Hi Thomas, On Thu, Oct 08, 2020 at 06:56:47AM -0000, Thomas Schmitt wrote: > so for now -partition_offset 16 is not to blame ?
Appears not. > The only tangible report was back in 2011 about a Macbook Pro > https://lists.debian.org/debian-cd/2011/04/msg00029.html > with decisive test in > https://lists.debian.org/debian-cd/2011/04/msg00060.html > and (deplorable) success report in > https://lists.debian.org/debian-cd/2011/04/msg00061.html > May i propose my personal favorite culprit for the next test here ? > If so, then try what happens if at ISO production time the options > -part_like_isohybrid -isohybrid-gpt-basdat > are omitted in order to drop the invalid GPT of the ISO. Yes, thanks, this was the next thing on the list for us to test. http://cdimage.ubuntu.com/ubuntu/daily-live/20201008/ is now built, with these changes (restore -partition_offset, drop isohybrid/gpt-basdat options). @sudodus, @leok, could you please retest on Lenovo V-series with this image? Reports on other hardware are only relevant if it does boot on the Lenovo V-series; also, we don't need test reports from using tools that modify the image when writing to disk. -- 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
