You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This forces the writing to DD mode. We also don't seem to be able to detect that there exists an EFI/BOOT/bootx64.efi on that ISO, which should at the very least allow us to write in EFI mode.
Once again, the openSUSE people have managed to find a way to master their ISO in a manner that creates problems for everybody down the line... Why is it that it's always openSUSE that manages to break stuff. Can't they take a page from Debian for once, and try to play nice?
Would be nice to try to fix this for 3.0 if we can.
ISO analysis:
Image is an ISO9660 image
libcdio: from_733: broken byte order
libcdio: from_733: broken byte order
libcdio: Bad directory information for docu
Could not access directory /docu
Will use '/boot/x86_64/loader/isolinux.cfg' for Syslinux
Detected Syslinux version: 4.04/0x9f68dc20 (from '/boot/x86_64/loader/isolinux.bin')
Disk image analysis:
Image has an unknown Master Boot Record
Image is a bootable disk image
Using image: openSUSE-Leap-15.0-DVD-x86_64.iso (3.6 GB)
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
lockbot
locked and limited conversation to collaborators
Apr 6, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This forces the writing to DD mode. We also don't seem to be able to detect that there exists an
EFI/BOOT/bootx64.efi
on that ISO, which should at the very least allow us to write in EFI mode.Once again, the openSUSE people have managed to find a way to master their ISO in a manner that creates problems for everybody down the line... Why is it that it's always openSUSE that manages to break stuff. Can't they take a page from Debian for once, and try to play nice?
Would be nice to try to fix this for 3.0 if we can.
The text was updated successfully, but these errors were encountered: