similar to: Dell OptiPlex 790 PXELINUX localboot reboot loop

Petr Vandrovec wrote: > Hello, > one of FreeDOS developers pointed out (in > http://www.vmware.com/community/thread.jspa?threadID=11324&messageID=109507&#109507) > that FreeDOS does not work under VMware when using ISOLINUX 3.0x. After > looking at their ISO image I downloaded syslinux-3.05, and there seems > to be bad bug: > > You have this in kernel.inc:

Currently, I'm looking at implementing 3 COMBOOT API calls for directories, opendir, readdir, and closedir. In order to track progress within the directory, I'll need to keep track of the current sector number that is being read and the offset within the sector for the next file entry to read. I'm contemplating if I should also keep track of the starting sector of the directory (in

ldlinux and extlinux are both using CurrentDir variable name. Rename CurDir to make it consistent with those. - Sebastian Index: syslinux-3.71-pre7/core/isolinux.asm =================================================================== --- syslinux-3.71-pre7.orig/core/isolinux.asm 2008-07-13 19:52:27.000000000 +0200 +++ syslinux-3.71-pre7/core/isolinux.asm 2008-07-13 19:53:11.000000000 +0200 @@

I have been using PXELINUX, with "LOCALBOOT 0" when wanting to boot from disk, for many years. Now on new Dell Optiplex 990 machines, PXE boot with "LOCALBOOT 0" hangs after message Booting from local disk... without the expected "Exiting PXE" message. I tried "LOCALBOOT -1" and some other values also, none seemed to work. I tested SYSLINUX 4.04.

Hello, I have a problem with our DELL E6510 notebooks (BIOS version A05): 1. After the update from syslinux-3.71 to 4.02 LOCALBOOT no longer works. I've read <http://www.syslinux.org/wiki/index.php/Hardware_Compatibility#LOCALBOOT_on_Dell_Latitude_E6400> and neither version works. The behavior differs between the laptop rebooting automatically and getting stuck. I checked all versions

Hi, We are using pxelinux at my company to test our product. And there are limitations that we have hit in the past w.r.t. the max length of a path, or the max length of a module name (in mboot.c / mboot.c32). We've used workarounds in the past, and reorganized the directory structure, but we face that problem again. Out of the 128 / FILENAME_MAX chars that can be used, 110 - 120 go to the

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add get config full file name to SYSLINUX Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Returns the full configuration file name. Int 22h AX 001Eh for now as it appears that the COMBOOT API is designed to be strictly sequential. The API gets extended but only implemented (for now) for SYSLINUX in ldlinux.asm.

I tried to replace display_labels asm code (ui.inc) with new C code (pm_display_labels), but the data i access in command_line doesn't seem to be always up to date. The patch i am working on is only for PXELINUX because of different vkernel structure: diff --git a/core/com32.inc b/core/com32.inc index 111590c..f19df7c 100644 --- a/core/com32.inc +++ b/core/com32.inc @@ -135,6 +135,7 @@

From: Gene Cumm <gene.cumm at gmail.com> COMBOOT API: Add get current working directory call to most Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- Adds an API call to obtain the current working directory. EXTLINUX will not return the correct value yet however SYSLINUX, ISOLINUX, and PXELINUX will return the correct value. For the moment, EXTLINUX will ONLY return

From: Sylvain Gault <sylvain.gault at gmail.com> Some linker scripts were splitted into i386 and x86_64 versions in commit d8eede3f2a360163235fad222a0190cd7c5bef38 but older scripts were left there. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> --- core/syslinux.ld | 414 ------------------------------------------------ core/x86_64/syslinux.ld | 389

Hi, we use PXELINUX in our product to show a boot menu on client computers, with options like "Boot from local hard disk", "Install Windows", etc. Unfortunately, a lot of computers seem to have broken BIOSes and won't boot with the LOCALBOOT command, and need to be booted with chain.c32 instead. We also have encountered some computers where it works only the other way -

Hello All. I have a dell optiplex 320 that I can install centos5 on using pci=nomsi. That seems to be the only way. After the install grub loads but thats about as far as it gets. It looks like a BIOS bug to me, but I just don't know. I left it sit for a few minutes and it just had the echoed boot params on the screen. I've tried booting with noapic nolapic apm=off acpi=off and noprobe

Hi, The CentOS 4.4 installation doesn't work on a Optiplex 745 because it doesn't support the sata controller. Is there a known work-around? (smaller prob: dvi video doesn't work at install time, vga only) If only we had CentOS 5 :-) Cheers, -- Henk van Lingen, Systems Administrator & DBA (o- -+ Dept. of Computer Science, Utrecht University.

Hi, I want to run a HVM domU. I have a Dell Optiplex 755: model name : Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz I have enabled VT in BIOS settings under performance. However, after I boot into a linux kernel (not under Xen), grep vmx /proc/cpuinfo returns nothing. When I boot under Xen, I get (XEN) Intel VT-d has been enabled (XEN) [VT-D]iommu.c:1700: Queued Invalidation hardware not

Hello every body, I ve installed Trixbox 1.2 on "DELL OPTIPLEX GX 240", i upgreded it to the latest version. I've 2 cards installed in the same pci channel via a bridge or plug i don't know exactly what's his name( but a card (1 pci) that gives 2 pci channels) the first card is TDM400P: it's ok the second is TE110P: it's not ok . No led is on neither the red nor the

After reading: *[1] http://forums.fedoraforum.org/showthread.php?t=141178 *[2] https://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=22187& forum=39 *[3] http://wirelessness.wordpress.com/2007/02/07/installing-fedora-linux-on-a-dell-o ptiplex-320/ *[4] http://lists.us.dell.com/pipermail/linux-desktops/2007-January/000148.html 1. I booted with linux rescue 2. chroot

I just started having an issue with PXELinux with one particular model of computer. The issue appears to occur on Dell Optiplex 740 computers, and any disk image that we try to boot with PXE Linux comes up with a Boot Disk Failure for two images or Cannot Load Kernel error for Dell Diagnostics. The error only appears to occurs on the Optiplex 740 model. I've tested PXE Linux and our boot

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

On Tue, Jul 2, 2013 at 4:07 PM, Patrick Verner <distrozilla at gmail.com> wrote: > 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. What do you actually observe? Perhaps BIOS rev A11 and not A10 or earlier? Regular physical CD and not an ISOHYBRID written to disk-like media or loaded with

On Jul 2, 2013 7:37 PM, "Patrick Verner" <distrozilla at gmail.com> wrote: > > 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 Is "ISOLINUX 5.11 0x51D1AE48 ETCD_" (assuming