search for: pre19

...gt; > wrote: > >>>> On 24.07.2014 13:52, Gene Cumm wrote: > ... > >>>> Your special build gets the gateway working, but the downloaded InitRD > >>>> still gets corrupted sometimes. Boot-time is down from 16m to ~2m. > ... > > Syslinux 6.03-pre19 is out. Since several prior versions were tested > > in this same hardware with different results, it could be very useful > > to repeat the tests with 6.03-pre19 too, which includes some patches > > for (l)pxelinux. > > > > Feedback is appreciated. > > lpxelinu...

...>>>>> On 24.07.2014 13:52, Gene Cumm wrote: >> ... >>>>>> Your special build gets the gateway working, but the downloaded InitRD >>>>>> still gets corrupted sometimes. Boot-time is down from 16m to ~2m. >> ... >>> Syslinux 6.03-pre19 is out. Since several prior versions were tested >>> in this same hardware with different results, it could be very useful >>> to repeat the tests with 6.03-pre19 too, which includes some patches >>> for (l)pxelinux. >>> >>> Feedback is appreciated. >...

On 08/11/2014 06:12 AM, Shantanu Gadgil wrote: > Hi all, > > I too am getting positive results using 6.03-pre19 lpxelinux.0, for the problem that I have been facing. > > The symptom was that booting hangs on client side. > On the server (DNSMasq TFTP) it keeps getting a request for the same (MAC address) file. > OR, alternatively it just stops completely. > > My server: OptiPlex 755. BIOS...

Hi all, I too am getting positive results using 6.03-pre19 lpxelinux.0, for the problem that I have been facing. The symptom was that booting hangs on client side. On the server (DNSMasq TFTP) it keeps getting a request for the same (MAC address) file. OR, alternatively it just stops completely. My server: OptiPlex 755. BIOS A22 The PXE booting client: O...

-------------------------------------------- On Mon, 8/11/14, H. Peter Anvin <hpa at zytor.com> wrote: Subject: Re: [syslinux] testing out 6.03 network booting... (6.03-pre19) To: "Shantanu Gadgil" <shantanugadgil at yahoo.com>, "syslinux at zytor.com" <syslinux at zytor.com> Date: Monday, August 11, 2014, 10:21 PM On 08/11/2014 06:12 AM, Shantanu Gadgil wrote: ... ... > * Things are broken using 6.03-pre17 lpxelinux.0 and wor...

...ux-http > > LINUX http://boot-server/boot/vmlinuz > > APPEND initrd=http://boot-server/boot/initrd > > That worked: Booting was reasonable fast and no corruption thanks to TCP > checksums. Thank you for your help! > > Sincerely > Philipp > Syslinux 6.03-pre19 is out. Since several prior versions were tested in this same hardware with different results, it could be very useful to repeat the tests with 6.03-pre19 too, which includes some patches for (l)pxelinux. Feedback is appreciated. TIA, Ady.

> > We are not ready for "prime-time" though. > Using the "lpxelinux.0" file from 6.03-pre19 ... > > My RHEL5 installs, when using the "http://" for kernel, initrd and append lines, seem to be hitting some sort of parameter length limit. > The culprit seems to be the long "append" line. > > The same append line, when NOT using "http://" work...

I have pushed out SYSLINUX 3.70-pre19. This includes a workaround that I have some early indications might actually resolve the "frozen USB keyboard" problem. If you have a system with this issue, I would *greatly* appreciate: a) if you could test it; b) if it works, if you could verify that 3.70-pre18 *DOESN'T* work...

I just pushed out SYSLINUX 3.10-pre19. This version adds symlink support for EXTLINUX. As part of the process of implementing that, I ran into a somewhat embarrassing bug in the menu support, which I fixed, however, if any of you have a chance to test especially menu.c32 on as many derivatives as possible (SYSLINUX, PXELINUX, ISO...

...ipp Hahn <hahn at univention.de> wrote: >>>> On 24.07.2014 13:52, Gene Cumm wrote: ... >>>> Your special build gets the gateway working, but the downloaded InitRD >>>> still gets corrupted sometimes. Boot-time is down from 16m to ~2m. ... > Syslinux 6.03-pre19 is out. Since several prior versions were tested > in this same hardware with different results, it could be very useful > to repeat the tests with 6.03-pre19 too, which includes some patches > for (l)pxelinux. > > Feedback is appreciated. lpxelinux from 6.03-pre20 works for my DELL...

...On 24.07.2014 13:52, Gene Cumm wrote: >>> ... >>>>>>> Your special build gets the gateway working, but the downloaded InitRD >>>>>>> still gets corrupted sometimes. Boot-time is down from 16m to ~2m. >>> ... >>>> Syslinux 6.03-pre19 is out. Since several prior versions were tested >>>> in this same hardware with different results, it could be very useful >>>> to repeat the tests with 6.03-pre19 too, which includes some patches >>>> for (l)pxelinux. >>>> >>>> Feedback...

> >? ? > > We are not ready for > "prime-time" though. > > Using > the "lpxelinux.0" file from 6.03-pre19 ... > > > > My RHEL5 installs, > when? using the "http://" for kernel, initrd and > append lines, seem to be hitting some sort of parameter > length limit. > > The culprit seems to be > the long "append" line. > > > > The same append l...

The pre19 code assumes that struct lastlog either exists in lastlog.h or isn't there. On NetBSD, struct lastlog is defined in utmp.h. Even worse, the non-lastlog code in login.h is terrible on NetBSD (since NetBSD doesn't have a ut_type struct member). With the patch below, openssh will compile and...

ok on a soekris 4801. Now that youre in late pre-release, pls consider these doc-patches, 1st sent in May. which are (I assume) still true, if not directly desirable. (reword as you see fit, or reject outrite) They apply -p0 other trivialities: early part of pxelinux paints approx 16 chars wide across serial to my terminal (picocom) and often doesnt scroll, (does so rarely, dont recall

I tried isolinux 3.10-pre20 on an Acer Aspire 1501LMi notebook and a Shuttle FS-40 desktop box; it fails on both, simply hanging after printing the first line. Last known good version is 3.10-pre16; will try pre17-pre19 when I have some time.

...g] > Sent: 09 July 2014 19:50 > Hey Andrew, > Sorry for the delay. Could you provide the packet dumps of the network > traffic involved in the failed EFI boot? > Hopefully that will allow us to track down exactly what's going wrong. Hi Matt, Appears to all be working under 6.03-pre19 on vmware workstation 8, as well as on a series 8 Asus board I tried with an onboard Intel NIC.. That's in all 4 modes I was trying - BIOS (both pxelinux and lpxelinux), EFI32, EFI64. I used both HTTP (not in pxelinux) and TFTP to boot from to test each. (Apologies again for not getting some...

-------------------------------------------- On Mon, 8/18/14, Ady <ady-sf at hotmail.com> wrote: But then you report that typing in the exact same full command, it boots OK? I don't type the /complete/ command by hand. I let the error box popup and then I type in the missing 6 characters and then press ENTER. The installation then continues. Regards, Shantanu

...-eltorito-platform 0xEF" for this "current Mac" hardware, as Thomas suggested. > > If that works I could suggest to Parick Volkerding to upgrade the cdrtools > Slackware package in Slackware-current (upcoming Slackware release). > > About mixing with Syslinux 6.03-pre19 (or newer) as suggested in your > previous post... Let me clarify. I would suggest updating Slackware to use the latest cdrecord / cdrtools / mkisofs version that would be available just before the next Slackware release (ATM, 3.01a24). I am hoping that the combination of adequate mkisofs...

...that even with "-eltorito-platform Mac" in the mkiosfs command, isohybrid doesn't complain any more, right? If that works I could suggest to Parick Volkerding to upgrade the cdrtools Slackware package in Slackware-current (upcoming Slackware release). About mixing with Syslinux 6.03-pre19 (or newer) as suggested in your previous post... Yes, the scripts/receipts for using Syslinux 6.xx in Slackware would need changes and I am very doubtful that Patrick will accept to do that in next Slackware release. I could try this tentatively just for testing if that helps, but then I would need...

...y on the TFTP server that can serve several "architectures". > Problem (solved) #1: The default directory location for both > syslinux.efi is the same. > > Solution #1: Rename each syslinux.efi to bootx64.efi and to > bootia32.efi. | stappers at nero:~/dl/syslinux-6.03-pre19 | $ find . -name "*.efi" | ./efi64/efi/syslinux.efi | ./efi32/efi/syslinux.efi | ./gpxe/src/arch/x86_64/Makefile.efi | ./gpxe/src/arch/x86/Makefile.efi | ./gpxe/src/arch/i386/Makefile.efi That rename is _not_ in the 6.03 pre-release 19. > Problem (solved) #2: Each syslinux.efi needs...