similar to: 5.01 BOOT_IMAGE= is missing in cmdline but path appears two times

Hello While testing PXE booting, I decided to change IPAPPEND to the new SYSAPPEND and does not work: nothing is appended to command line. I tested using menu.c32 and vesamenu.c32, same issue. --------------------------------------------------------------------- SERIAL 0 38400 UI boot/syslinux/vesamenu.c32 LABEL arch64_nbd MENU LABEL Boot Arch Linux (x86_64) (NBD) LINUX boot/x86_64/vmlinuz

On 06/13/2013 10:15 PM, Gene Cumm wrote: > On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi > <vmlinuz386 at yahoo.com.ar> wrote: >> Hello >> >> While testing PXE booting, I decided to change IPAPPEND to the new >> SYSAPPEND and does not work: nothing is appended to command line. >> >> I tested using menu.c32 and vesamenu.c32, same issue.

Hello, First, this setup works fine without any error in syslinux 4.06 as show below. For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] directories (~2MB each) are uploaded ready for test. As said before, this is tested on qemu-1.5.0 + dnsmasq 2.66 in Arch Linux @ 64-bit. If more info is needed, please let me know. Good luck! Relevant directory structure is at

On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote: > Hello > > While testing PXE booting, I decided to change IPAPPEND to the new > SYSAPPEND and does not work: nothing is appended to command line. > > I tested using menu.c32 and vesamenu.c32, same issue. > > ---------------------------------------------------------------------

On 06/13/2013 11:06 PM, Gerardo Exequiel Pozzi wrote: > On 06/13/2013 10:15 PM, Gene Cumm wrote: >> On Thu, Jun 13, 2013 at 8:08 PM, Gerardo Exequiel Pozzi >> <vmlinuz386 at yahoo.com.ar> wrote: >>> Hello >>> >>> While testing PXE booting, I decided to change IPAPPEND to the new >>> SYSAPPEND and does not work: nothing is appended to command

Hi, I have Xen installed and running several (win 7) HVMs. I've setup an Arch linux PV guest but I am having a problem booting it. (The install image booted fine.) After each failed attempt to boot I try to view the /var/log/xen/bootloader.XX.log file but all of these files are zero bytes. So, I'm having some trouble troubleshooting this. I followed the instructions from

Hello again, * TFTP and DHCP started using: dnsmasq --port=0 \ --no-daemon \ --enable-tftp \ --tftp-root=/run/archiso/bootmnt \ --dhcp-range=192.168.0.2,192.168.0.254,86400 \ --dhcp-boot=/arch/boot/syslinux/gpxelinux.0 \ --dhcp-option-force=209,boot/syslinux/archiso.cfg \ --dhcp-option-force=210,/arch * and for DHCP+HTTP

On Wed, 12 Jun, at 12:42:01PM, Gerardo Exequiel Pozzi wrote: > make installer > make -C utils > make -C com32 > > then copy all files *.c32 (including ldlinux.c32) and lpxelinux.0 I suspect the above make commands aren't enough to rebuild the necessary files. I just pushed out a 5.11-pre1 with a version of the patch that only changes the internal representation of PATH. Could

On Wed, 12 Jun, at 11:17:44AM, Gerardo Exequiel Pozzi wrote: > Cool thanks!. Now looks better, but still not work. > > For some reason, "ldlinux.c32" is apparently sent but "Failed to load" > by PXELINUX and few seconds later, dnsmasq shows an error message > "failed sending": Argh! The patch was broken. I missed the new core/path.c file. My bad.

> I'm the developer of manjaroiso, the tool we use to build our install > medias for Manjaro Linux. > During our testings we found out, that syslinux6 won't work on older > hardware. I've a new Lenovo i7 notebook which booted up our images > just fine. Even with syslinux6. On my other PCs I got similar error > messages as Carl got. (snip) > > In

On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote: > On 06/11/2013 01:03 AM, Matt Fleming wrote: > > On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > >> Either that or make the path a list rather than a string, using the > >> normal word separators when entered on the command line, a bit like the > >> (t)csh does. That is a bigger change but is probably

-- Re-sent as original may be stuck at awaiting "authorisation" (originally sent before I joined the mailing list) Hi All, It is impossible to boot Linux-based ISOs that use Syslinux 6.02 via CD or DVD on older - non-UEFI - systems. Any attempt to do so will result in the following error message: ISOLINUX 6.02 ETCDisolinux: Disk error 01, AX = 4279, drive FE It is still possible to

This one is the most critical for my app, but also possibly the most controversial to integrate. A few applications that convert isolinux ISOs to bootable USB, including mine, copy the ISO content to a VFAT formatted partition and then add syslinux to make it bootable. This would work great... if isolinux and syslinux shared the same defaults when it comes to configuration files.

Hello With 4.06 this works fine all times. But with versions 5.1x-preX and 6.0x-preX, 6.01) does not work, random errors or nothing shows (netconn_write error -5), random behaviour. Only few times works (1/50...). Note that retriving files via TFTP works perfect in all cases. This happens using pre-compiled files in tarball and building for source. # dnsmasq --port=0 \

Generically, yes, the hardware is supported. On Mon, Sep 18, 2017 at 11:42 PM, <ygrishin-lists at mail2.ca> wrote: > I will update the thread as soon as I get the hardware back. It was > something serious like artifacts or no video in X so that I had to resort to > proprietary drivers. > So the question is whether this hardware is supported or not. > > > On 2017-09-18

Hello, now that 5.00pre is out, is there any timeline or rough estimate when stable EFI support can be expected? I'm one of the authors of a live CD project which we'd really like to make usable on Macs which only have EFI support (without BootCamp). Most other EFI-capable machines I've seen so far also have a BIOS emulation, but I expect things to change with upcoming Windows 8

Hello! SSIA - when syslinux sees 'BOOT_IMAGE=' on the append line, something seems to go terribly wrong (didn't investigate in detail). You don't even get to see a boot-prompt, even if you try to force it. pxelinux shows the same problem, so I figure it's something generic in the config parser ... Best regards, Andreas P.S: and thanks for this software ;) -- "The

On 06/12/2013 09:40 AM, Matt Fleming wrote: > On Tue, 11 Jun, at 03:54:21AM, H. Peter Anvin wrote: >> On 06/11/2013 01:03 AM, Matt Fleming wrote: >>> On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: >>>> Either that or make the path a list rather than a string, using the >>>> normal word separators when entered on the command line, a bit like the

> Their isolinux/isolinux.cfg has > DEFAULT loadconfig > LABEL loadconfig > CONFIG /arch/boot/syslinux/archiso.cfg > The file arch/boot/syslinux/archiso.cfg is readable too. > IIRC, Arch isolinux/isolinux.cfg should say: DEFAULT loadconfig LABEL loadconfig CONFIG /arch/boot/syslinux/archiso.cfg APPEND /arch/ Or it might be using relative paths: DEFAULT

On Mon, 10 Jun, at 07:57:50AM, H. Peter Anvin wrote: > Either that or make the path a list rather than a string, using the > normal word separators when entered on the command line, a bit like the > (t)csh does. That is a bigger change but is probably a better solution. How would this solution handle filenames containing spaces? Would we need to escape (presumably with a backslash)