similar to: lpxelinux hangs on R610 with recent BIOS, works with old BIOS

Hi, We have a little over 100 servers, almost all running CentOS 5.7. Virtually all are Dell servers, generally a mix of 1950s, R610s, and R410s. We use NTP and/or PTP to sync their clocks. One phenomenon we've noticed is that (1) on reboot, the clocks are all greatly out of sync, and (2) if the PTP or NTP process is stopped, the clocks start drifting very quickly. If it was isolated to

On 07/10/2014 04:07 PM, Alexander Perlis wrote: > 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

On Fri, Jul 11, 2014 at 5:49 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 07/11/2014 04:31 PM, H. Peter Anvin wrote: >> >> On 07/11/2014 10:17 AM, Alexander Perlis wrote: >>> >>> >>> Trace shows that lpxelinux.0 6.03-pre18 is transferred, and after that >>> there is only ARP traffic: a "gratuitous" ARP announcement by

On 07/11/2014 10:17 AM, Alexander Perlis wrote: > > Trace shows that lpxelinux.0 6.03-pre18 is transferred, and after that > there is only ARP traffic: a "gratuitous" ARP announcement by the > client, and then a string of ARP requests and replies in which the > client is asking for the MAC of the PXE server, about every 3 seconds, > for about 2 minutes, after which I

On 07/10/2014 06:39 PM, Gene Cumm wrote: > On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: >> On 07/10/2014 04:07 PM, Alexander Perlis wrote: >>> 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,

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

On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/10/2014 04:07 PM, Alexander Perlis wrote: >> 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

On 07/11/2014 04:31 PM, H. Peter Anvin wrote: > On 07/11/2014 10:17 AM, Alexander Perlis wrote: >> >> Trace shows that lpxelinux.0 6.03-pre18 is transferred, and after that >> there is only ARP traffic: a "gratuitous" ARP announcement by the >> client, and then a string of ARP requests and replies in which the >> client is asking for the MAC of the PXE

On 07/11/2014 09:39 PM, Gene Cumm wrote: > With everything else from 6.03-pre18, try this binary (xzip-compressed): > http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz It works! Thanks! Anything else I should do/report on this hardware before I upgrade the BIOS and possibly eliminate the broken environment that exhibited the problem? Alex

Hello everybody, I am looking for the efi64/syslinux.efi with IP support like the bios/lpxelinux.0 version has. I am using debian buster with: syslinux-efi 3:6.04~git20190206.bf6db5b4+dfsg1-1 all collection of bootloaders (UEFI bootloader) Thank you in advance, Kind regards, Jelle de Jong

On 07/12/2014 02:24 PM, Gene Cumm wrote: > On Sat, Jul 12, 2014 at 3:15 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: >> On 07/11/2014 09:39 PM, Gene Cumm wrote: >>> >>> With everything else from 6.03-pre18, try this binary (xzip-compressed): >>> http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz >> >> It works! Thanks! > > Oh

I am currently using a Dell PowerEdge server R610 with Xen 4.0 installed and the 2.6.31.13 pvops kernel. I am accessing the server console using the iDRAC KVM feature of the dell management console. Does anyone know how to configure the console option in the grub menu so that all the boot messages can be seen on the mgmt console? Currently I can view only the Xen bootup messages if I dont specify

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading the R610 server from Debian 7 to Debian 8, the dom0 becomes unresponsive via ssh after an hour or so, although the domUs still remain accessible. Initially we thought it may be a disk space issue on / or /boot so action was taken to increase those

On Sat, Jul 12, 2014 at 3:38 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 07/12/2014 02:24 PM, Gene Cumm wrote: >> >> On Sat, Jul 12, 2014 at 3:15 PM, Alexander Perlis <aperlis at math.lsu.edu> >> wrote: >>> >>> On 07/11/2014 09:39 PM, Gene Cumm wrote: >>>> >>>> >>>> With everything else from

On Sat, Jul 12, 2014 at 3:15 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 07/11/2014 09:39 PM, Gene Cumm wrote: >> >> With everything else from 6.03-pre18, try this binary (xzip-compressed): >> http://www.zytor.com/~genec/lpxelinux-6.03p18g3.tgz > > > It works! Thanks! > > Anything else I should do/report on this hardware before I upgrade the

We have DELL R900 server with PERC6/i and PERC 6/E in it. O.S. is CENTOS 5.3. I download latest PERC 6 driver from DELL site and tried to installed it. I have error messages said : Module version 00.00.03.21 for megaraid_sas.ko is not newer than what is already found in kernel 2.6.18-128.1.10.el5 (00.00.04.01-RH1). Does CENTOS 5.3 come with PERC6 driver? I knew in CENTOS 4.X PERC 5 or PERC6

SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP DL360p gen8, two six-core Thuban-II workstations plua their monitors, and the network stack and KVM. The APC SU3000RM (3KVA) that blew up last week considered this to be just short of 60% load. The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power factor, considers this same load to be 43% load. I wasn't

On Jul 1, 2014 10:37 PM, "Alexander Perlis" <aperlis at math.lsu.edu> wrote: > > I believe I'm seeing a bug in lpxelinux.0 6.03-pre17 but I need some advice on how to isolate and troubleshoot this. (I can't try pre18 at the moment, but did try 4.07 and 5.10 and saw similar behavior, also with pxelinux.0, so although I'll give pre18 a try soon, some

On this list in early July 2014 I reported that on certain hardware one cannot chain from ipxe to lpxelinux.0 . My report at the time was about 6.03-pre17. I've repeated the tests with the release version of 6.03 and here is an updated report with more details. I boot to a USB stick with iPXE, which then is told to "dhcp" and then "chain http://xxx.xxx.xxx.xxx/pxe.0".

hi does anyone know if there are some known issues with running lpxelinux.0 with device that doesn't support Interrupts? i.e. irq function is null...