Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

openSUSE Leap 15.0 ISOhybrid is not properly detected as ISO #1136

Closed
pbatard opened this issue May 25, 2018 · 2 comments
Closed

openSUSE Leap 15.0 ISOhybrid is not properly detected as ISO #1136

pbatard opened this issue May 25, 2018 · 2 comments
Assignees
Milestone

Comments

@pbatard
Copy link
Owner

pbatard commented May 25, 2018

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)
@pbatard pbatard added this to the 3.0 milestone May 25, 2018
@pbatard pbatard self-assigned this May 25, 2018
@pbatard
Copy link
Owner Author

pbatard commented May 26, 2018

For the record, I have also reported this issue to libcdio:
http://lists.gnu.org/archive/html/libcdio-devel/2018-05/msg00007.html

@lock
Copy link

lock bot commented Apr 6, 2019

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.

@lock lock bot locked and limited conversation to collaborators Apr 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant