similar to: Sysylinux-6.03 freezes at Loading kernel..., works smooth with 4.06 via SD-CARD

Hi, First of all thank you so much for your prompt suggestions/help. I really appreciate this. Here is the syslinux.cfg which works perfect with syslinux-4.06 ---- PROMPT 0 TIMEOUT 50 SERIAL 0 DEFAULT mylabel LABEL mylabel KERNEL vmlinuz0 APPEND initrd=initrd.img root=/dev/mmcblk0p2 rootwait rootfstype=ext3 console=tty0 console=ttyS0,9600 ---- To further round off the error possibilities I used

> Hi, > I am trying to boot syslinux with an SD-Card on COMe-mBTi10 board, it works > perfect with syslinux 4-06(as BIOS supports booting from SD-CARD), but > hangs with syslinux-6.03 during 'Loading vmlinuz ... '. > I tried various ways in which I could debug but no hints, just one time I > got the error below the loading screen. > > 'Loading vmlinuz0 ... CHS:

Hi, I am trying to boot syslinux with an SD-Card on COMe-mBTi10 board, it works perfect with syslinux 4-06(as BIOS supports booting from SD-CARD), but hangs with syslinux-6.03 during 'Loading vmlinuz ... '. I tried various ways in which I could debug but no hints, just one time I got the error below the loading screen. 'Loading vmlinuz0 ... CHS: Error 8001 reading sector 34(0/3/3)

> > Hi > I have tried to install syslinux 4.06 on the SD card again, it works > like a charm. > > I am being very carefull with c32 files from the same version > bootloader. No success. > > I am also unmounting /dev/sdb1 before installing syslinux, as mentioned > in the given documentations. > In the pasted syslinux.cfg content--- I have also tried using only

Hi I have tried to install syslinux 4.06 on the SD card again, it works like a charm. I am being very carefull with c32 files from the same version bootloader. No success. I am also unmounting /dev/sdb1 before installing syslinux, as mentioned in the given documentations. In the pasted syslinux.cfg content--- I have also tried using only one DEFAULT directive. No success. syslinux boots

I have the following problem with syslinux. With boards with same core chipset and bios, syslinux fails on some boards. The difference on boards are that the ones that succeed has standard PC components (KBC, PATA). The ones that failes have SATA only and no KBC. It does not matter if I boot from USB or Compact flash drive. I has been noted that the bootloader calls BIOS functions for a drive

This is an attempt to avoid potential confusion. Here are some example sizes for the two Syslinux versions mentioned in the e-mail subject. Your build results might be different. 4.06: 1 55 Sep 22 22:23 modules/int18.com 1 108 Nov 1 18:07 version.mk 1 138 Nov 1 18:07 version.gen 1 138 Nov 1 18:07 version.h 1 239 Sep 22 22:23 modules/poweroff.com 1 408 Sep 22 22:25

From: MartinS <ams at ludd.ltu.se> isohdp[fp]v.S which says E or C if EBIOS or CBIOS is used. isohdppv.S also says G or M if a GPT or MBR partition is detected. Signed-off-by: MartinS <ams at ludd.ltu.se> --- Comments? diff --git a/mbr/Makefile b/mbr/Makefile index be2bded..7095396 100644 --- a/mbr/Makefile +++ b/mbr/Makefile @@ -21,7 +21,8 @@ include $(MAKEDIR)/embedded.mk all:

Hi, I've tried to compile syslinux under mandriva, and the compilation always bails out because it hasn't created win32/syslinux.exe. As far as I understand, the build will work fine on a Windows / mingw installation, but not Linux. I've modified my Makefile to remove the win32/syslinux.exe from the build, and it now builds OK. This happened on 3.3.6 and also on 4.0pre.

Hi On Tue, May 20, 2014 at 3:12 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On May 20, 2014 12:33 AM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: >> >> Hi >> >> On Mon, May 19, 2014 at 6:58 PM, Gene Cumm <gene.cumm at gmail.com> wrote: >> > On May 19, 2014 5:17 PM, "Anatol Pomozov" <anatol.pomozov at

Ferenc Wagner <wferi at niif.hu> writes: > The internal Gnu-EFI build gives me grief: [...] Previous points still standing, but now I tried cleaning out everything by hand. I don't know whether it matters, but building gnu-efi pollutes its source directory (unlike syslinux itself) with the following files at least (found by git status in the gnu-efi submodule):

Hi On Tue, May 20, 2014 at 9:18 AM, Anatol Pomozov <anatol.pomozov at gmail.com> wrote: > Hi > > On Tue, May 20, 2014 at 3:12 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >> On May 20, 2014 12:33 AM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: >>> >>> Hi >>> >>> On Mon, May 19, 2014 at 6:58 PM, Gene Cumm

Hi On Mon, May 19, 2014 at 6:58 PM, Gene Cumm <gene.cumm at gmail.com> wrote: > On May 19, 2014 5:17 PM, "Anatol Pomozov" <anatol.pomozov at gmail.com> wrote: > >> Besides syslinux itself other things has changed e.g. gcc (but I >> really hope my problem not because of compiler). > > This alone can be the trigger.This might be a starting point: build

Gene Cumm <gene.cumm at gmail.com> writes: > Could you try gnuefi-script-for-wferi-test branch on my repos at > > git://git.zytor.com/users/genec/syslinux.git > git://github.com/geneC/syslinux.git > > These changes fixed my issues (aside from the concurrency issue which > 2-3 passes solves for me). Now this shows me something I haven't ever seen. Build

Hi, The internal Gnu-EFI build gives me grief: * efi/check-gnu-efi.sh: uses realpath, which is not available on my Debian wheezy system. I now use readlink -f, but wonder if it's needed at all. * efi/build-gnu-efi.sh: uses realpath, like above, and also pushd/popd, which is not built into a standard Bourne shell invoked by #!/bin/sh. Again I wonder what's the point of it, as

On Fri, Jan 10, 2014 at 2:53 AM, Ferenc Wagner <wferi at niif.hu> wrote: > Gene Cumm <gene.cumm at gmail.com> writes: > >> On Sat, Jan 4, 2014 at 6:39 AM, Gene Cumm <gene.cumm at gmail.com> wrote: >>> On Tue, Dec 17, 2013 at 8:39 AM, Ferenc Wagner <wferi at niif.hu> wrote: >>> >>>> * make spotless still fails after working around

Hi, H. Peter Anvin: > It means that the .iso can be booted from a partition using any of the > standard MBRs (not necessarily altmbr), But the --partok MBRs (isohdpp*) stem from altmbr ? If so: don't they need the partition number patched in ? (If not: i have to rethink the link to article "Mbr" at http://www.syslinux.org/wiki/index.php/Isohybrid#MBR_selection ) >

Hi, Duncan Elliot wrote: > As far as I can see, this essentially trims off the first 3 bytes of the > custom isohybrid MBR image before applying it to the ISO. You probably mean this line: memcpy(mbr, &isohdpfx[hd0 + 3 * partok], MBRSIZE); The indize do not apply to bytes but to byte arrays of size MBRSIZE. extern unsigned char isohdpfx[][MBRSIZE]; (hd0 + 3 * partok)

On Mon, Feb 16, 2015 at 12:06:07PM -0800, syslinux-bot for Gene Cumm wrote: > Commit-ID: 9d33f23c9bbb0f308ca6dab3fca16a128247e283 > Gitweb: http://www.syslinux.org/commit/9d33f23c9bbb0f308ca6dab3fca16a128247e283 > Author: Gene Cumm <gene.cumm at gmail.com> > AuthorDate: Mon, 16 Feb 2015 14:27:35 -0500 > Committer: Gene Cumm <gene.cumm at gmail.com> >

Hi, I have been attempting to set up a multi-boot USB stick (i.e. multiple bootable ISO images on the one stick) I have had good success by: - processing ISO with isohybrid (with "partok" flag) - dd'ing ISO to primary partitions on the USB stick (e.g /dev/sdc2, /dev/sdc3, /dev/sdc4) - installing grub to USB stick and configuring to chainload to these partitions To remove the limit