From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6092] New: Bootable ISO image creation seems to have stopped working since 2012.08
Date: Tue, 12 Mar 2013 16:54:29 +0000 (UTC) [thread overview]
Message-ID: <bug-6092-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6092
Summary: Bootable ISO image creation seems to have stopped
working since 2012.08
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: gfx229-uclibc at yahoo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
2012.08 and prior generated bootable ISO images whereas the changes after this
(which defaulted to CPIO initramfs from Ext2 filesystem image) seems to have
stopped working (could be operator error but no obvious documentation in this
scenario).
Repro (2012.11 to 2013.02) - used mostly straight-line defaults:
[ ] Linux kernel - Install kernel image to /boot in target, used
i386_defconfig extracted from Linux kernel build as
defined kernel config
[ ] Bootloaders - specified both grub and syslinux (Install isolinux)
[ ] Filesystem images - iso image, fs/iso9660/menu.lst
- cpio the root filesystem (no compression method)
[ ] Package selection - nothing but BusyBox
Observed behavior - burned ISO boots and hangs after "Loading Stage2 ....."
Previous good (2012.08)
[ ] Burned ISO bootable (I think because initrd is Ext2 rather than
Initramfs/CPIO)
---
Perhaps I'm doing something wrong or need other configuration parameters for
the Linux kernel (I tried adding other filesystem module support but that did
not help nor do I suspect it is necessary). If there is some BuildRoot
documentation that I'm overlooking or need to do more directly with Linux
kernel configuration to ensure even a "linked-in" initramfs copy works, I'm
happy to further investigate my own issues. (It just was working fine with the
Ext2 initrd but seems to have stopped after the changes in 2012.11 so I was
wondering where I've gone wrong or if this is not a widely tested scenario.)
Thank you very much and best regards.
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-03-12 16:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 16:54 bugzilla at busybox.net [this message]
2013-03-13 18:42 ` [Buildroot] [Bug 6092] Bootable ISO image creation seems to have stopped working since 2012.08 bugzilla at busybox.net
2013-03-13 19:02 ` bugzilla at busybox.net
2013-03-13 19:04 ` bugzilla at busybox.net
2013-03-13 21:54 ` bugzilla at busybox.net
2013-03-15 14:56 ` bugzilla at busybox.net
2013-05-26 13:35 ` bugzilla at busybox.net
2013-05-31 16:26 ` bugzilla at busybox.net
2013-08-26 9:57 ` bugzilla at busybox.net
2013-10-07 18:28 ` bugzilla at busybox.net
2014-01-08 5:02 ` bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-6092-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox