[Bug 939456] New: Tumbleweed installation USB key does not boot
http://bugzilla.opensuse.org/show_bug.cgi?id=939456 Bug ID: 939456 Summary: Tumbleweed installation USB key does not boot Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: tjcw@physics.org QA Contact: jsrain@suse.com Found By: --- Blocker: --- At 20150724, using imagewriter to make a 'bootable' USB key results in a non-bootable USB key. It looks like the partition information is not being written (the last step to modify an ISO before publication) -- 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#c6
Mateusz Mielczarek
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#c7
--- Comment #7 from Chris Ward
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c9
--- Comment #9 from Mateusz Mielczarek
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
http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c11
Benjamin Westrich
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
Martin Pluskal
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
Peter Linnell
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
Marcel Witte
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
Max Lin
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c15
Dominique Leuenberger
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c27
--- Comment #27 from Jochen Keil
mkisofs from cdrtools creates a correct boot catalog; so running fixCatalog() in kiwi is no longer necessary. (This might even produce the stay 3rd extra entry.)
In that case it might be safe to use mkisofs as drop-in replacement for genisoimage and get rid of cdrkit-cdrecord-compat/wodim entirely: https://github.com/openSUSE/kiwi/pull/479 -- 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
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#c31
--- Comment #31 from Jochen Keil
mkisofs from cdrtools works differently from genisoimage.
In what way? Why is it symlinked then in the compat package? (Sorry about the broken comment previously, I accidentally pasted the content of my clipboard..) -- 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
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c37
--- Comment #37 from Jochen Keil
genisoimage creates broken el-torito boot catalog entries; mkisofs not. This fixCatalog() function could just detect the situation and behave differently. I've just done this in the mksusecd package.
Although this might be heretic, but how about dropping the fixCatalog() stuff entirely? Is it necessary to keep the support for genisoimage around? -- 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
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
Emr Rec
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c42
H. Zeng
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
Luca Beltrame
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c72
Matthias Eliasson
http://bugzilla.opensuse.org/show_bug.cgi?id=939456
http://bugzilla.opensuse.org/show_bug.cgi?id=939456#c74
--- Comment #74 from H. Zeng
As it happens the new product builder is not used yet for TW. :-(
(But everywhere else - the Leap-15.0 images are fine, for example.)
Has anyone tried this for Leap 15.0? I used "openSUSE-Leap-15.0-DVD-x86_64-Build258.1-Media.iso" to make a USB drive using `dd` command, but it cannot boot up my T420s ThinkPad laptop to install the system. After selecting the USB drive to boot from, the system stopped at the black screen with only a cursor blinking at the top left corner. P.S. This laptop does not use UEFI boot. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com