similar to: Dell and pxelinux keyboard problems

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I am having trouble with memdisk not freeing all all memory - mem /c shows only about 570K memory (and I happen to need that extra memory in DOS ... :-( ). I found some (rather old) information about this issue. It seems as if this is just what is happening to me: http://syslinux.zytor.com/archives/2003-June/002213.html

git://git.zytor.com/users/genec/syslinux.git Branch memdiskdbg-for-sha0 This starts with adding another check in two of the disk probes (by Shao; Thank you), expands the debug output, adds an additional check in the third probe and expands/reorders the debug output. At this time, it appears to resolve the MEMDISK issues that Jason Vasquez first noticed. The additional check in the third probe

Yes on optiplex 790 i upgraded from A07 to A18 (there was a nic upgrade) but it didn't change anything.. On optiplex 380 i upgraded from bios A01 to A07(don't know if upgrade contained pxe or not)... I tried, lpxelinux.0 and it wasn't faster. Only v4.07 helped on these machines. Tomorrow, i will give a try with 6.03pre2. In wireshark, i saw no errors, the packet length was the

Hi there, We had to setup a pxelinux on a new server (windows 2012) and used the latest release of pxelinux 6.0.2. Everything went ok on my first client test machine : dell optiplex 740. Pxe was really fast (vesamenu with large background image was appearing in less than 3 secondes) But on different client machine i got different results : On optiplex 790 (core i5 with intel 82579 nic) and

Hello, I'm interrested in testing any possible workaroud for the Dell Optiplex GX620 keyboard problem, as I just can't downgrade the BIOS version on each and every Gx620 I have to (re)install ! (Plus I can't find a link to download the old A10 BIOS itself.) Don't hesitate to give me guidance on how to proceed, because I can't find anything relevant on the website

Sorry for the delay, we were too busy drinking and playing with explosives yesterday. :) Here are some tests. We did one on a similar machine and it worked. We deleted the configuration file, obviously. # Dell OptiPlex GX620 ISOLINUX 5.11 5.11-pre7 isolinux: Starting up, DL = 82 isolinux: Loaded spec packet OK, drive = 82 isolinux: Main image LBA = 00000115 isolinux: Image checksum error,

Same CD. Any Linux distribution without the 5.X series boots on this machine. We can use 4.06 and it boots just fine. It's not the computer's hardware. Like I said, we can take the CD out of the GX620 and place it in the 9010 and it boots. Put 4.06 on the CD, and they both boot. Patrick On Sat, Jul 6, 2013 at 7:18 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > On Fri, Jul 5,

Hi, am using latest C6 on a Dell GX270 with latest Bios. It fails to power down but restarts when running $ sudo poweroff I tried some google hints for kernel boot option: acpi=force no help, looks like acpi is working anyway when looking in dmesg acpi=off makes e1000 nic fail to initialize Any suggestions? Rainer

I'm not exactly sure what you need. Is this it? ISOLINUX 4.06 0x513e88f5 isolinux: Starting up, DL = 82 isolinux: Loaded spec packet OK, drive = 82 isolinux: Main image LBA = 0000011D isolinux: Main image read, jumping to main code... I created an iso with isolinux-debug.bin as the boot loader and booted it on that machine. If this is not what you are looking for, what are correct steps?

Hello All, I encountered the same problem as reported to this list earlier, http://lists.freebsd.org/pipermail/freebsd-stable/2009-February/048305.html, but then with 7.1-RELEASE-p4. Interestingly enough, FreeBSD booted fine on the machine installed (updated from 7.0 to 7.1-RELEASE-p4). This machine is a PowerEdge 1850 bios A04 with Perc 43/Si bios H430 / fwVer 521S. When booting a drive

On 15 Nov 2014 05:06:52 +0200, Ady wrote: > > I would start by updating the BIOS. Prudent advice. As it turns out, I'm already at the latest version. On 15 Nov 2014 07:31:27 +0100, Geert Stappers wrote: > > And would reduce 'iPXE => pxe.0 => lpxelinux.0 => "vmlinux"' > into 'iPXE => "vmlinux"' That makes sense generally, but at

Hello, My desktop machine at work was replaced and they gave me a Dell Optiplex GX520 machine to use. When booting from CD-ROM I use isolinux 3.50 and the keyboard does not work. It does work once linux boots, and it works if I hit the F2 to go into bios before isolinux starts. I have searched google and the syslinux archives for 'Optiplex GX520' but have not found any reports of

System: Dell OptiPlex GX620 (Both BIOS A10 and A11 affected) Medium: Physical CD-RW Observed: ISOLINUX 5.11 0x51D1AE48 ETCD_ is the only line displayed on-screen. A flashing cursor trails at the end of the line. Escape key does not return boot: prompt. Line1 of syslinux.cfg: DEFAULT vesamenu.c32 Note: Reverting to syslinux-4.06 allows for successful booting on the same system. Patrick On Tue,

Hello all. Again I call upon the greats of this mailing list to help me with an issue related to MEMDISK - notably when paired with various Dell OptiPlex and Latitude systems. The issue presented itself sometime ago and I best dealt with it by remaining with version 3.83 of the SYSLINUX package. But valuing the improved changes fostered by newer versions, I would prefer to move forward with

I'm trying to nuke a Dell Optiplex GX620. I've got a perfectly good dban 1.0.4 that I've used a bunch of times... but on this machine, it says starting, then dies, saying "dban has finished with non-fatal errors. Check the log for more information" It never gets to the interactive menu. Now that I've disabled the non-existant floppy drive, at least it does say "to

This same system boots with syslinux-4.06. Let me know if there is any further info you need. We tried syslinux-5.11-pre5 as well. Patrick Verner partedmagic.com

We have tried compiling the binaries our self and using the pre-compiled in the syslinux tar ball as well. It just locks up with the text we provided. The problem is booting from CD, booting from USB works. I suspect the problem is in isolinux.bin. The CD only fails on this one machine. It works on everything else we tried. 4.06 worked without any issue on this same machine. Parted Magic has been

Morning All, I upgraded from 9.2-STABLE to 10.0-PRERELEASE #0 r259144 last night and I am now getting this every 2 seconds in /var/log/messages: Dec 10 07:54:31 Shop kernel: ata1: FAILURE - zero length DMA transfer attempted Dec 10 07:54:31 Shop kernel: ata1: setting up DMA failed cat /var/log/messages | grep ata1: cd0 at ata1 bus 0 scbus3 target 0 lun 0 cd0: <TSSTcorp DVD-ROM TS-H352C

============================================= [ INFO: possible recursive locking detected ] 3.17.0 #50 Not tainted --------------------------------------------- Xorg/1170 is trying to acquire lock: (&dev->struct_mutex){+.+.+.}, at: [<ffffffffa010ae93>] i915_gem_unmap_dma_buf+0x33/0xc0 [i915] but task is already holding lock: (&dev->struct_mutex){+.+.+.}, at:

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 isolation/troubleshooting advice will be a good education no matter what.) To get to our PXE-launched tools from