similar to: Problem with 1.2.1pre19

Displaying 20 results from an estimated 900 matches similar to: "Problem with 1.2.1pre19"

2014 Aug 01
2
DELL E6510 pxelinux issues
> Hello, > > On 24.07.2014 17:32, Gene Cumm wrote: > > On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> wrote: > >> On 24.07.2014 13:52, Gene Cumm wrote: > >>> As expected. You have a different OUI (the first 3 octets of the MAC > >>> address). Try everything from 6.03-pre18 and then lpxelinux.0 from > >>>
2005 Aug 23
4
isolinux 3.10-pre20 doesn't work at all
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.
2014 Jul 24
3
DELL E6510 pxelinux issues
On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> wrote: > Hello, > > On 24.07.2014 13:52, Gene Cumm wrote: >> On Thu, Jul 24, 2014 at 4:56 AM, Philipp Hahn <hahn at univention.de> wrote: >>> PS: <http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz> did not work. >> >> As expected. You have a different OUI (the first 3
2000 Mar 31
4
anomalous wtmp logging bug
I've noticed rather strange wtmp logging behavior in sshd. Can anyone confirm or solve the following: Once a user authenticates themself to sshd, sshd among other things records the login in the wtmp, which `last` reads. However, sshd logs hostnames which are longer than 16 characters instead of IPs like normal programs would. As a result, I have useless entries such as: tempest
2014 Sep 29
0
I had a problem in all of the IBM THINKPAD SL410 serise laptop by lPEXLINUX.0
On Mon, Sep 29, 2014 at 3:26 AM, hangzhong at 126.com <hangzhong at 126.com> wrote: > thank for your help,Gene. I download 6.03-pre18 and try the lpxelinux.0 > from it.My Laptop (IBM THINKPAD SL410) didn't get that error message,but > reboot repeatly. after vesion of 6.03-pre18, 6.03-pre19-20 is ok. > > echee > > 29th.SEP > ________________________________ >
2005 Sep 13
2
Fw: Issue with pxelinux
I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken
2014 Aug 27
0
DELL E6510 pxelinux issues
Hello Ady, On 27.08.2014 16:46, Ady wrote: >> On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>>>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> >> wrote: >>>>>> On 24.07.2014 13:52, Gene Cumm wrote: >> ... >>>>>> Your special build gets the gateway working, but the
2014 Aug 27
3
DELL E6510 pxelinux issues
> Hello, > > On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: > >>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp 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
2014 Sep 29
2
I had a problem in all of the IBM THINKPAD SL410 serise laptop by lPEXLINUX.0
Hi,I have a PXE server with pxelinux 6.02 in my school. It can boot the laptop and desktop computer and it working very well.but I had a problem in all of the IBM THINKPAD SL410 serise laptop,the error message say "pxelinux 6.02 lwIP 2003-10-13 copyright (c) 1994-2013 H. Peter Anvin et al Boot failed:press a key to retry, or wait for reset" when it boot,after a while automaticaly
2008 Jun 18
0
SYSLINUX 3.70-pre19 and the frozen USB keyboards
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. This would be incredibly useful! Thanks, -hpa
2014 Jun 25
3
testing out 6.03 network booting...
> > From: Matt Fleming [matt at console-pimps.org] > > Sent: 25 June 2014 07:39 > > To: Andrew Rae > > Cc: Gene Cumm; syslinux at zytor.com > > Subject: Re: [syslinux] testing out 6.03 network booting... > > > > Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release > > button yesterday and -pre18 contains my change. It would be
2014 Aug 11
2
testing out 6.03 network booting... (6.03-pre19)
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
2014 Jun 25
2
testing out 6.03 network booting...
On Sun, 22 Jun, at 06:15:50PM, Andrew Rae wrote: > > Matt - I'd love to try it - but I'm not so good at fixing compiling > issues. right now I get stuck at being unable to 'make' the efi32 or > efi64 components due to an error: Andrew, could you try out syslinux-6.03-pre18? Peter pushed the release button yesterday and -pre18 contains my change. It would be good to
2014 Aug 27
0
DELL E6510 pxelinux issues
Hello, On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp 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
2014 Jul 10
2
lpxelinux hangs under Intel Boot Agent 1.3.81 (2.1 build 089) on Dell Optiplex 990 BIOS A16
Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel Boot Agent 1.3.81 (2.1 build 089). It gets network and launches lpxelinux.0, I see the PXELINUX banner line, but there it hangs. I tried both 6.03-pre18 and 5.10, same hanging behavior. If I instead use pxelinux.0 or gpxelinux.0, either 6.03-pre18 or 5.10 or 4.07, there are no problems. The problem seems isolated to
2014 Aug 11
0
testing out 6.03 network booting... (6.03-pre19)
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: OptiPlex 960. BIOS A17 * Things are
2014 Aug 27
1
DELL E6510 pxelinux issues
On Wed, Aug 27, 2014 at 12:21 PM, Philipp Hahn <hahn at univention.de> wrote: > Hello Ady, > > On 27.08.2014 16:46, Ady wrote: >>> On 01.08.2014 19:22, Ady wrote:>> On 24.07.2014 17:32, Gene Cumm wrote: >>>>>> On Thu, Jul 24, 2014 at 10:29 AM, Philipp Hahn <hahn at univention.de> >>> wrote: >>>>>>> On 24.07.2014
2014 Jul 27
1
pxelinux HTTP transport UEFI vmlinuz
Op 2014-07-23 om 17:57 schreef Gene Cumm: > On Wed, Jul 23, 2014 at 10:32 AM, Geert Stappers <stappers at stappers.nl> wrote: > > Hi, > > > > Since which version of pxelinux.0 is understood in pxelinux.cfg/default that > > > > kernel http://host.lan/netboot/vmlinuz > > > > means vmlinuz should be transported over HTTP? > > For non-EFI
2014 Aug 14
0
testing out 6.03 network booting... (6.03-pre19)
-------------------------------------------- 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
2014 Jul 08
3
Possible memdisk issue
I'm having trouble getting memdisk 6.03pre18 to boot large floppies and wondering whether I'm doing something incorrectly. 1) Download http://www.fdos.org/bootdisks/autogen/FDOEM.144.gz 2) gunzip FDOEM.144.gz 3) newmkfloppyimg.sh 8 FDOEM144.img fdoem_8mb.img 4) newmkfloppyimg.sh 9 FDOEM144.img fdoem_9mb.img 5) Use following pxelinux.cfg: LABEL works LINUX syslinux/memdisk INITRD