Hi,
so for now -partition_offset 16 is not to blame ?
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. Lengthy motivation is in: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895131/comments/22
Have a nice day :)
Thomas
Hi,
so for now -partition_offset 16 is not to blame ?
The only tangible report was back in 2011 about a Macbook Pro /lists. debian. org/debian- cd/2011/ 04/msg00029. html /lists. debian. org/debian- cd/2011/ 04/msg00060. html /lists. debian. org/debian- cd/2011/ 04/msg00061. html
https:/
with decisive test in
https:/
and (deplorable) success report in
https:/
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. /bugs.launchpad .net/ubuntu/ +source/ casper/ +bug/1895131/ comments/ 22
Lengthy motivation is in:
https:/
Have a nice day :)
Thomas