similar to: Chaining with chain.c32 from syslinux 6.01 error

On Mon, 22 Jul, at 12:07:34PM, Matt Fleming wrote: > On Thu, 18 Jul, at 01:22:04PM, Adrian Irimia wrote: > > Hi, > > ? > > ? I have a bootable usb with syslinux 5.10 on wich the following?code is working ok. > > ??? LABEL - > > ?? MENU LABEL GRUB LEGACY > > ?? MENU INDENT 1 > > ???? COM32 chain.c32 > > ???? APPEND boot fs

W dniu 22.07.2013 13:07, Matt Fleming pisze: > On Thu, 18 Jul, at 01:22:04PM, Adrian Irimia wrote: >> Hi, >> >> I have a bootable usb with syslinux 5.10 on wich the following code is working ok. >> LABEL - >> MENU LABEL GRUB LEGACY >> MENU INDENT 1 >> COM32 chain.c32 >> APPEND boot fs grub=/boot/grub-legacy/stage2

? In qemu (virtual machine) it is working ok. ? On?a physsical machine syslinux does not boot at all : ? ? SYSLINUX 6.02 EDD 6.02-pre9 ... ? Boot error. I attached the usb drive info. ________________________________ From: Matt Fleming <matt at console-pimps.org> To: Adrian Irimia <adixtx at yahoo.com> Cc: "syslinux at zytor.com" <syslinux at zytor.com> Sent:

I just tested 6.02-pre10 version. ? On physsical machine it is booting ok now,?but chain.c32 result is the same errors :? ERR: Primary partition (in MBR) with invalid offset and/or length. ? ERR: Cant't find myself on the drive I booted from Adding 'relax' option to chain.c32 invocation resolves the problem. ? In qemu the boot and chaining works ok (without 'relax' option).

Yes. Prior versions (all to 6.01 inclusive) are working very well. ?And yes it fail before invoking chain.c32 (as I said in qemu there is no errors). ________________________________ From: Matt Fleming <matt at console-pimps.org> To: Adrian Irimia <adixtx at yahoo.com> Cc: "syslinux at zytor.com" <syslinux at zytor.com> Sent: Tuesday, July 23, 2013 5:16 PM

? In qemu (virtual machine) it is working ok. ? On?a physsical machine syslinux does not boot at all : ? ? SYSLINUX 6.02 EDD 6.02-pre9 ... ? Boot error. ? ________________________________ From: Matt Fleming <matt at console-pimps.org> To: Adrian Irimia <adixtx at yahoo.com> Cc: "syslinux at zytor.com" <syslinux at zytor.com> Sent: Monday, July 22, 2013 4:37 PM

On Thu, 18 Jul, at 01:22:04PM, Adrian Irimia wrote: > Hi, > ? > ? I have a bootable usb with syslinux 5.10 on wich the following?code is working ok. > ??? LABEL - > ?? MENU LABEL GRUB LEGACY > ?? MENU INDENT 1 > ???? COM32 chain.c32 > ???? APPEND boot fs grub=/boot/grub-legacy/stage2 grubcfg=/boot/grub-legacy/grub-legacy.cfg nohand nosect > ? > ?After upgrading to

On 2013-07-24 15:39, Adrian Irimia wrote: > I just tested 6.02-pre10 version. > > On physsical machine it is booting ok now, but chain.c32 result is the same errors : ERR: Primary partition (in MBR) with invalid offset and/or length. > ERR: Cant't find myself on the drive I booted from > Adding 'relax' option to chain.c32 invocation resolves the problem. > Then

Here is a patch that makes it possible to chainload GRUB2 core.img form chain.c32. It reuses the grub= parameter (used for chainloading GRUB Legacy stage2): - both loaded at 0x8000 - start execution at offset 0x200 (0x8200 in memory) GRUB2 allows to specify another "GRUB home dir" than the standard /boot/grub GRUB2 doesn't allow to change the configfile 'grub.cfg' name

On Mon, 22 Jul, at 12:50:46PM, Adrian Irimia wrote: > ? > In qemu (virtual machine) it is working ok. > ? > On?a physsical machine syslinux does not boot at all : > ? > ? SYSLINUX 6.02 EDD 6.02-pre9 ... > ? Boot error. Presumably you were able to boot a previous version on this physical machine? Does it now fail before even invoking chain.c32? -- Matt Fleming, Intel Open

On Tue, 23 Jul, at 08:06:46AM, Adrian Irimia wrote: > Yes. Prior versions (all to 6.01 inclusive) are working very well. > ?And yes it fail before invoking chain.c32 (as I said in qemu there is no errors). Could you try 6.02-pre10? -- Matt Fleming, Intel Open Source Technology Center

> ? > In qemu (virtual machine) it is working ok. > ? > On?a physsical machine syslinux does not boot at all : > ? > ? SYSLINUX 6.02 EDD 6.02-pre9 ... > ? Boot error. > > > I attached the usb drive info. > The CHS values in the Partition Table are inconsistent with the LBA and fs size. Partition Table: Start CHS: 0 / 1 / 1 End CHS: 888 / 254 / 63

>From 1db8a8919482dbed4cc15509d8078b2f16a289bb Mon Sep 17 00:00:00 2001 From: Gert Hulselmans <gerth at zytor.com> Date: Wed, 30 Jun 2010 14:10:23 +0200 Subject: [PATCH] chain.c32: add grubcfg= for passing an alternative config filename to GRUB Legacy GRUB Legacy reserves 89 bytes for storing the filename of the configfile from memory address 0x8217 to 0x826f. We allow overwriting the

filename to GRUB Legacy GRUB Legacy reserves 89 bytes for storing the filename of the configfile from memory address 0x8217 to 0x826f. We allow overwriting the default value (/boot/grub/menu.lst) when grubcfg=<filename> is used together with grub=<loader>. Examples: chain.c32 fs grub=/boot/grub/stage2 grubcfg=/boot/grub/grub.lst chain.c32 hd1,10 grub=/boot/grub/stage2

Correct the "seg=" value(s) corresponding to the "reactos=" option for chain.c32. The correct segment parameter should be "seg=0x0F80", instead of the incorrect / failing ones "seg=0:0x8000:0x8100". References: https://svn.reactos.org/svn/reactos/trunk/reactos/boot/freeldr/notes.txt?revision=73859&view=markup&pathrev=73859#l24

Dear All: I am having trouble trying to dual-boot VMware and Linux, and I tried everything I could come up with. The situation is that /dev/sda is fully used by VMware and /dev/sdb is used by Linux. VMware uses Syslinux, so I thought this would be simple... However, it is not. The bootable FAT partition is too smal to have kernels in it. As a fallback I tried to chain-load GRUB, but that did not

# HG changeset patch # User Olaf Hering <olaf@aepfle.de> # Date 1346945306 -7200 # Node ID 8a2eef481d3ab3ca5692dd0083c95cf314fe1da3 # Parent 19d367bf07b7687b831c212a57a70e73ea14d3b7 pygrub: always append --args If a bootloader entry in menu.lst has no additional kernel command line options listed and the domU.cfg has ''bootargs="--args=something"'' the additional

This is a bit updated set of chain.c32 changes that simplifies a few things (and in partiter part), fixes few minor issues and adds a few new features. Details are in the following commits, below is the summary and pull details at the end. Shao - any chance to peek over them ? Most of those are relatively simple changes and well tested, though of course something might have slipped my attention.

Fix for pygrub path on Solaris. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/tools/python/xen/xend/XendDomainInfo.py b/tools/python/xen/xend/XendDomainInfo.py --- a/tools/python/xen/xend/XendDomainInfo.py +++ b/tools/python/xen/xend/XendDomainInfo.py @@ -37,7 +37,7 @@ from xen.util.blkif import blkdev_uname_ from xen.util.blkif import blkdev_uname_to_file from xen.util

On Mon, Feb 20, 2017 at 2:17 PM, Ady Ady via Syslinux <syslinux at zytor.com> wrote: > Correct the "seg=" value(s) corresponding to the "reactos=" option > for chain.c32. > > The correct segment parameter should be "seg=0x0F80", > instead of the incorrect / failing ones "seg=0:0x8000:0x8100". > > References: >