Displaying 20 results from an estimated 2000 matches similar to: "[5.xx-6.01] broken PXE with HTTP"
2013 Jul 08
3
[5.xx-6.01] broken PXE with HTTP
On 07/05/2013 01:02 PM, Gerardo Exequiel Pozzi wrote:
>
> 5.00 [pxelinux.0] OK 5.01 [pxelinux.0] OK 5.02-pre1
> [pxelinux.0] OK 5.02-pre2 [pxelinux.0] OK 5.02-pre3 [pxelinux.0]
> BAD (freeze, no error messages, 100% CPU used)
>
> 5.10-pre1 [pxelinux.0] BAD (freeze, no error messages, 100% CPU
> used) 5.10-pre2 [pxelinux.0] BAD (Failed to load: ldlinux.c32,
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 06
7
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/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
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
2
[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":
Did you reinstall ldlinux.c32 after rebuilding? Did you do 'make
2013 Nov 26
3
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/26/2013 01:14 AM, H. Peter Anvin wrote:
> On 11/25/2013 06:32 PM, H. Peter Anvin wrote:
>> On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote:
>>>
>>> I made some more and more experiments beyond LBA 65535
>>>
>>> Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size
>>> 34816)
>>>
>>> Does not work: *
2013 Jul 09
0
[5.xx-6.01] broken PXE with HTTP
On Jul 8, 2013 5:34 PM, "H. Peter Anvin" <hpa at zytor.com> wrote:
> On 07/05/2013 01:02 PM, Gerardo Exequiel Pozzi wrote:
> >
> > 5.00 [pxelinux.0] OK 5.01 [pxelinux.0] OK 5.02-pre1
> > [pxelinux.0] OK 5.02-pre2 [pxelinux.0] OK 5.02-pre3 [pxelinux.0]
> > BAD (freeze, no error messages, 100% CPU used)
> >
> > 5.10-pre1
2013 Nov 26
3
Sysinux 6 will not boot ISOs on BIOS (i.e. pre-UEFI) systems
On 11/25/2013 04:12 PM, Gerardo Exequiel Pozzi wrote:
>
> I made some more and more experiments beyond LBA 65535
>
> Works: * isolinux-4.07.bin (size 24574) * isolinux-5.00.bin (size
> 34816)
>
> Does not work: * isolinux-5.01.bin (size 34816) * isolinux-5.10.bin
> (size 36864) * isolinux-6.00.bin (size 38912) * isolinux-6.02.bin
> (size 43008)
>
> * I just
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 04
3
Syslinux 5.10 released
Folks,
Finally, Syslinux 5.10 has been released. This release includes a merge
of the 4.10 development branch, which means that there's a new network
stack availble, based on the lwIP embedded TCP/IP stack. The jump from
the previous 5.01 release to 5.10 may be a little confusing, but a new
network stack is such a large change that it deserved a significant bump
in the version minor number.
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 14
2
[5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)
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.
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
2013 Jun 06
1
[5.10] PXE + dhcp opts 209, 210 and path issues in tftp/http
On 06/06/2013 02:00 AM, Gene Cumm wrote:
> 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
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 11
2
[5.10] serial console broken
Hello
Since syslinux-5.10, serial console looks broken (nothing is displayed),
at least using qemu-1.5.0/1.4.2. Versions 5.01 and 5.02-preX works OK.
Relevant directive is on top of syslinux.cfg:
--------------------
SERIAL 0 38400
...
...
--------------------
I guess something is worng due recent serial console changes. If you
need more info, or revert some commit / git-bisect, please let me
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 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 05
1
Syslinux 5.10 released
On Wed, Jun 5, 2013 at 12:58 AM, Gerardo Exequiel Pozzi
<vmlinuz386 at yahoo.com.ar> wrote:
> On 06/04/2013 06:16 PM, Matt Fleming wrote:
>> Folks,
>>
>> Finally, Syslinux 5.10 has been released. This release includes a merge
>> of the 4.10 development branch, which means that there's a new network
>> stack availble, based on the lwIP embedded TCP/IP
2013 Jul 10
1
[5.xx-6.01] broken PXE with HTTP
On 07/09/2013 06:41 AM, Gene Cumm wrote:
>
> The only specifics I recall seeing in packet captures is that even
> though lwIP is using UNDI to open a TCP socket on a port, iPXE steps
> in and says that port is closed.
>
Right, and that is death right there. I need to talk to Michael and see
if this can be worked around.
-hpa