http://bugzilla.opensuse.org/show_bug.cgi?id=939456 http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c6 Mateusz Mielczarek <sysek@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sysek@hotmail.com --- Comment #6 from Mateusz Mielczarek <sysek@hotmail.com> --- (In reply to Steffen Winterfeldt from comment #3)

Chris, you can run the tumbleweed iso through mksusecd (software.opensuse.org). This will give you a working iso. (mksusecd -c new.iso old.iso)

I tried that methon, but don't work for me (I tried under the arch linux) arch:~/Documents/git/mksusecd sysek$ sudo ./mksusecd -c new-opensuse.iso openSUSE-Tumbleweed-NET-x86_64-Snapshot20150728-Media.iso El-Torito legacy bootable (x86_64) El-Torito UEFI bootable (x86_64) building: 100% isohybrid: invalid offset: `8344', 0 <= offset <= 64 Error: isohybrid failed -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939456 http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c9 --- Comment #9 from Mateusz Mielczarek <sysek@hotmail.com> --- (In reply to Steffen Winterfeldt from comment #8)

Mateusz, you probably just run the script without installing everything properly first (try 'make install'). Note that it comes with its own isohybrid binary!

after that works, but NET install stops on download the first file system (1/5), so I am downloading DVD. Thanks for advice. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939456 Martin Pluskal <mpluskal@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939456 Marcel Witte <wittemar@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wittemar@googlemail.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939456 http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c15 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimstar@opensuse.org --- Comment #15 from Dominique Leuenberger <dimstar@opensuse.org> --- For reference, from: https://build.opensuse.org/build/openSUSE:Factory:Live/standard/x86_64/kiwi-... [ 4765s] Aug-11 11:32:08 <1> : EXEC [/usr/bin/isohybrid --offset 12396 --id 0xc7cb7d8b --type 0x83 --uefi /usr/src/packages/BUILD/kiwi-image-livecd-gnome-Tumbleweed/out/iso/openSUSE-13.2-livecd-gnome.x86_64-2.8.0.iso 2>&1] -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939456 http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c29 --- Comment #29 from Jochen Keil <jkeil@suse.com> --- https://github.com/openSUSE/kiwi/pull/479(In reply to Steffen Winterfeldt from comment #28)

I might pay off to adopt the kiwi code to deal with both mkisofs variants before you do this.

I don't quite understand. The cdrkit-cdrecord-compat package merely provides a symlink from mkisofs to genisoimage. Both tools work the same. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939456 http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c33 --- Comment #33 from Jochen Keil <jkeil@suse.com> --- How can I then find out how mkisofs behaves differently from genisoimage? The parameters are all the same and do the same, at least according to the documentation. Also, how would support for both programs look like? Check if mkisofs is a symlink and then do some genisoimage specific stuff, if there's any? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939456 http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c40 --- Comment #40 from Jochen Keil <jkeil@suse.com> --- Following Steffen's advice I've updated the pull request to kiwi inspired by his changes to mksusecd. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939456 http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c42 H. Zeng <zhx@cnzhx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zhx@cnzhx.net --- Comment #42 from H. Zeng <zhx@cnzhx.net> --- I am here to add a little information on this. I have encounter with this bug several times in the past a few months until I find this bug report when I try to file a bug report on the problem I have. The problem is detailed in this thread [1] in the openSUSE forum. In summary, several points are listed as follows. 1. At least this bug affects the DVD ISO image of openSUSE Tumbleweed snapshots of 20170308, 20170429, 20170505 and 20170510. I have tested all this snapshots trying to find out why I cannot boot to install openSUSE with a USB stick made with the ISO by using binary copy (the `dd` command). As a background, I tested this USB stick on a Lenovo ThinkPad T470s under EFI boot mode with secure boot ON and OFF. They all failed like this: after selecting the USB stick as boot device in the EFI boot menu, the screen turns black for a second with no splash of any text on it and then the EFI boot menu shows up again with the first entry selected. 2. All of the ISOs of the snapshots mentioned above can be made into USB stick using Rufus with ISO Image mode and these USB sticks can be used to install openSUSE Tumbleweed successfully. 3. At least, the USB stick with snapshot 20170510 works on a relative new HP Pavilion laptop (I forgot the specific model) under EFI boot mode with secure boot ON. I can at least proceed to the options menu with one entry as "Installation". 4. After doing a "mksusecd" with ISO of snapshot 20170510, then making the USB stick with the new ISO image, the USB stick can be booted from on the Lenovo ThinkPad T470s at least to the option selection menu screen. I proceeded further with the "Rescue" option and it ran into an error of "*** signal 11 ***" at the bottom left corner of the screen. After stalking on this screen for about 1 or 2 minutes, the machine rebooted automatically. But I guess this is another issue. 5. A similar USB stick made from GeckLinux static image with KDE can be booted from on the Lenovo ThinkPad T470s to installation screen without any problem. Hopefully this bug could be fixed with a relative high priority since it seems that openSUSE Tumbleweed becomes more popular than before and many people tend to use USB drive other than optical drive for installation and rescue nowadays. [1] https://forums.opensuse.org/showthread.php/524790-Problems-on-burning-ISO-to... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=939456 http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c72 Matthias Eliasson <matthias.eliasson@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias.eliasson@gmail.com --- Comment #72 from Matthias Eliasson <matthias.eliasson@gmail.com> --- This is still a issue for latest Tumbleweed iso (Snapshot20180130). I used the excellent workaround Steffen Winterfeldt: make sure to have usb in and check which device it gets (lsblk) sudo mksusecd -c tumbleweed.img --fat openSUSE-Tumbleweed-DVD-x86_64-Snapshot20180130-Media.iso --size /dev/sdx sudo dd if=tumbleweed.img of=/dev/sdx bs=4M && sync -- You are receiving this mail because: You are on the CC list for the bug.