similar to: 5.01 problems with gpxelinux.0 (file paths related TFTP and HTTP)

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

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 \

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

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

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.

On Wed, 05 Jun, at 09:29:58PM, Gerardo Exequiel Pozzi wrote: > dnsmasq-tftp: file /run/archiso/bootmnt/arch/libcom32.c32 not found > dnsmasq-tftp: file /run/archiso/bootmnt/arch//libcom32.c32 not found > dnsmasq-tftp: file /run/archiso/bootmnt/arch/libcom32.c32 not found > dnsmasq-tftp: file > /run/archiso/bootmnt/arch//arch//boot/syslinux/libcom32.c32 not found OK, here's the

On 07/05/2013 01:01 AM, Gerardo Exequiel Pozzi wrote: > 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

On Fri, 07 Jun, at 10:30:11AM, Matt Fleming wrote: > On Wed, 05 Jun, at 09:29:58PM, Gerardo Exequiel Pozzi wrote: > > dnsmasq-tftp: file /run/archiso/bootmnt/arch/libcom32.c32 not found > > dnsmasq-tftp: file /run/archiso/bootmnt/arch//libcom32.c32 not found > > dnsmasq-tftp: file /run/archiso/bootmnt/arch/libcom32.c32 not found > > dnsmasq-tftp: file > >

Hello Booting with 4.06 cmdline looks like: # cat /proc/cmdline archisobasedir=arch archisolabel=ARCH_201301 initrd=boot/i686/archiso.img console=ttyS0 BOOT_IMAGE=boot/i686/vmlinuz while using 5.01: # cat /proc/cmdline boot/i686/vmlinuz boot/i686/vmlinuz archisobasedir=arch archisolabel=ARCH_201302 initrd=boot/i686/archiso.img console=ttyS0 And this cause some issues for cmdline parsing, I

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.

> 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

> 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

>From f48d79be8c79241dd4635165e393683809edd823 Mon Sep 17 00:00:00 2001 From: Matt Fleming <matt.fleming at intel.com> Date: Wed, 12 Jun 2013 13:04:44 +0100 Subject: [PATCH] PATH: Change the PATH directive syntax In retrospect, choosing the colon character as the entry separator for the PATH directive was not a smart move, as that character is also used in TFTP-style paths. This conflict

-- 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.

On 11/23/2013 09:35 AM, Carl Duff wrote: > -- 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

Hi, i am experiencing strange boot failures after repacking the ISO image archlinux-2013.11.01-dual.iso without isohybrid and EFI: # mount -o loop archlinux-2013.11.01-dual.iso /mnt $ xorriso -as mkisofs \ -o arch_repacked.iso \ -c isolinux/boot.cat \ -b isolinux/isolinux.bin \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -V "ARCH_201311" \

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