Displaying 20 results from an estimated 300 matches similar to: "[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http"
2013 Feb 02
1
5.01 problems with gpxelinux.0 (file paths related TFTP and HTTP)
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
2013 Jul 05
3
[5.xx-6.01] broken PXE with HTTP
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 \
2013 Jul 05
0
[5.xx-6.01] broken PXE with HTTP
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
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
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
2013 Jun 13
1
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/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
2013 Jun 12
5
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
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
2013 Jun 07
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
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
2013 Jun 12
3
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
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.
2013 Jun 06
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Am 06.06.2013 22:42, schrieb H. Peter Anvin:
> On 06/06/2013 01:25 AM, Thomas B?chler wrote:
>> Am 06.06.2013 07:00, schrieb Gene Cumm:
>>> iPXE details. My testing was with an Intel PXE OROM in a VMware
>>> hosted platform with 0 issues.
>>>
>>>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0"
>>>> 200 26813
2013 Jun 07
4
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
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
> >
2013 Jun 06
2
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
Am 06.06.2013 07:00, schrieb Gene Cumm:
> iPXE details. My testing was with an Intel PXE OROM in a VMware
> hosted platform with 0 issues.
>
>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" 200 26813
>> "" "iPXE/1.0.0+ (09c5)"
This is the iPXE version that comes bundled with qemu as the default
qemu boot rom.
-------------- next
2013 Jun 06
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi
<vmlinuz386 at yahoo.com.ar> wrote:
> 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 +
2013 Jun 06
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/06/2013 01:25 AM, Thomas B?chler wrote:
> Am 06.06.2013 07:00, schrieb Gene Cumm:
>> iPXE details. My testing was with an Intel PXE OROM in a VMware
>> hosted platform with 0 issues.
>>
>>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0"
>>> 200 26813 "" "iPXE/1.0.0+ (09c5)"
>
> This is the iPXE
2013 Jun 07
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi
<vmlinuz386 at yahoo.com.ar> wrote:
> [#1]
> https://dl.dropboxusercontent.com/u/88891866/archiso_syslinux_406.tar.xz
> https://dl.dropboxusercontent.com/u/88891866/archiso_syslinux_406.tar.xz.sig
>
> [#2]
> https://dl.dropboxusercontent.com/u/88891866/archiso_syslinux_510.tar.xz
>
2013 Nov 24
1
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
> 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
2013 Feb 01
2
5.01 BOOT_IMAGE= is missing in cmdline but path appears two times
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
2013 Jun 12
0
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
>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
2013 Nov 25
0
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
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
2013 Nov 24
0
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
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" \
2013 Jun 14
2
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
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