similar to: Bad gzip magic numbers and ISOLINUX

On 10/24/2013 01:09 AM, Christian Hesse wrote: >>> >>> version 6.02-pre5 works, 6.02-pre6 does not. >> >> Struggled with git bisect, but finally succeeded: >> >> 8f470e7bfe75f6401f6c5432988c620b863ad274 is the first bad commit >> commit 8f470e7bfe75f6401f6c5432988c620b863ad274 Author: Matt >> Fleming <matt.fleming at intel.com> Date:

"H. Peter Anvin" <hpa at zytor.com> on Tue, 2013/12/03 20:26: > On 10/24/2013 01:09 AM, Christian Hesse wrote: > >>> > >>> version 6.02-pre5 works, 6.02-pre6 does not. > >> > >> Struggled with git bisect, but finally succeeded: > >> > >> 8f470e7bfe75f6401f6c5432988c620b863ad274 is the first bad commit > >>

I would suggest putting this syslinux web page info near the top of the man page. I was using debian, which has all the linux images being linux.bin. So, to make my own boot disk, I thought I would just copy bzImage to the floppy as linux.bin. Big mistake, if one does that it will not work, and one gets output like: - 0400 AX:0208 BX:0200 CX:0002 DX:0000 etc. Just renaming

I'm trying to display a picture on a bootable CD that I'm working on. I tried isolinux-debug.bin, and the printouts we not very helpful. I see 'isolinux: Configuration file opened...', and then it displays the text from my display file (but not the image). Here's the strange thing, syslinux displays the image just fine. I take the appropriate files from the CD, copy

syslinux.doc: "...To bzImage and recent zImage kernels, SYSLINUX 1.30 and higher will identify using the ID byte 0x31. PXELINUX identifies using the ID byte 0x32, and ISOLINUX 0x33. The ID range 0x34-0x3f is reserved for future versions or derivatives of SYSLINUX...." Is this info available after boot in /proc or similar, or is it just something the kernel is told and keeps for

Hello, Im building my own linux CD, For booting I use isolinux. Problem: isolinux cant find kernel. Hierarchy of CD is: /boot/bzImage /boot/isolinux.bin /boot/isolinux.cfg isolinux.cfg file: DEFAULT linux LABEL linux KERNEL bzImage and for maiking iso I use: mkisofs -o name.iso \ -b boot/isolinux.bin -c boot/boot.cat \ -no-emul-boot -boot-info-table -boot-load-size 4 \ -v -J -R -D -A

Christian Hesse <list at eworm.de> on Tue, 2013/10/22 13:14: > Christian Hesse <list at eworm.de> on Tue, 2013/10/22 12:56: > > Gene Cumm <gene.cumm at gmail.com> on Tue, 2013/10/22 06:35: > > > On Tue, Oct 22, 2013 at 5:41 AM, Christian Hesse <list at eworm.de> wrote: > > > > Hello everybody, > > > > > > > > iPXE builds

Hi Peter, You've done a great job but I have some trouble on enjoying it. I tried to make a ISOLINUX CD, and followed the instructions in isolinux.doc, but dunno where shall I tell the kernel to find the root device? My isolinux.cfg contains only a "kernel bzimage" line. After I run mkisofs command, I test the .iso file on a VMware machine. ISOLINUX load the bzimage and than

I'm a newbie to bootable kernels and i've actually gotten it working before but i'm guessing that was luck. I'm building the kernel by doing a make bzImage and copying the bzImage into the isolinux directory and renaming it to vmlinuz. Then I burn a CD with ISOLINUX on it and my initrd.img file. I get the initial boot prompt, hit return and get the following messages: boot:

Hello I have a problem with isolinux my root filesystem is a iso9660 cdrom , it wont start the init but it mounts /dev/hdc as root. Cant linux start directly from a the cdrom or is this another problem? I get this: VFS: Mounted root filesystem (iso9660) readonly Freeing unused kernel memory: 2808kb freead Warning: unable to open an intital console Kernel panic: no init found. try parsing

hi! I?m working on a projekt ( unattended.sourceforge.net ) This is using a linuxboot.iso My problem is the following: I opened up the iso with winiso, extrcat the isolinux.cfg, edited it with vi for windows as follows: # isolinux/pxelinux configuration file default unattended label unattended kernel bzImage # Add options (z_user=..., z_path=..., etc.) to this line. append

Christian Hesse <list at eworm.de> on Thu, 2013/10/24 10:09: > Christian Hesse <list at eworm.de> on Tue, 2013/10/22 13:14: > > Christian Hesse <list at eworm.de> on Tue, 2013/10/22 12:56: > > > Gene Cumm <gene.cumm at gmail.com> on Tue, 2013/10/22 06:35: > > > > On Tue, Oct 22, 2013 at 5:41 AM, Christian Hesse <list at eworm.de> >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am trying to build a live fs on a CD that is selfbooting that later installs a pre-configured linux (this is acctually an upgrade, I have already done it before with 1.67). Anyway, I can't get it to work this time. All I see is - -----8<------ Cannot load disk image (invalid file)? - -----8<------ My isolinux/isolinux.cfg file: -

I''m working with some internally created software that is very closely tied to the kernel version. I *must* use version 2.6.23.9 of the kernel with a couple in-house patches applied. I''d like to be able to virtualize some machines and run this software within Xen. Because Xen does not currently support bzImage kernels I am struggling to get my kernel small enough for a zImage

Hi there, I failed to boot an installer in a VMware player (Version6.0.3 build-1895310) using syslinux 6.03, be it off an hybrid ISO image and an USB stick. Booting succeeds if the VM is set to use a BIOS firmware with both media, but fails using an efi firmware. Trying to boot off the ISO image I get an error message "The firmware encountered an unexpected exception" Trying to

Hi! Here is my isolinux.cfg. It's slackware based. ====================== default Kernels/bare.i/bzImage initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=8192 rw root=/dev/ram ZILIX_KERNEL=bare.i prompt 1 timeout 1200 font lat1-16.psfu display mensagem.msg F1 mensagem.msg F2 opcoes.msg F3 help.msg label linux kernel Kernels/bare.i/bzImage append - label adaptec.s kernel

Upstream commit 4370eec05a88 "arm64: Expand arm64 image header" ended up changing the zImage magic (which was actually the initial branch instructio encoding!). The new header has a proper magic number at a fixed location. Switch Xen itself to using this format. Neither the bootwrapper nor the models care about this header themselves and real bootloaders are not widely used, so now is

OK, here's another go-around. This patch leaves the bzImage itself unmodified, but it changes the payload into an ELF file. That is, the 32-bit decompression/relocation+compressed kernel is now a properly formed ELF file. One thing that fell out of this is that code32_start end up being a pointer to the ELF header rather than an entrypoint. Rather than reproducing Vivek's (?) hack of

OK, here's another go-around. This patch leaves the bzImage itself unmodified, but it changes the payload into an ELF file. That is, the 32-bit decompression/relocation+compressed kernel is now a properly formed ELF file. One thing that fell out of this is that code32_start end up being a pointer to the ELF header rather than an entrypoint. Rather than reproducing Vivek's (?) hack of

> On Sat, 7 Feb 2015, Ady via Syslinux wrote: > > Thank you for this meaningful report. Ideally, I would suggest > > performing a similar test (at least with the same kernel built with all > > the above "config_*=y" settings) with official pre-built Syslinux > > versions 4.07 and 3.86 (remembering that all Syslinux-related files, > > including c32