similar to: Intel Graphics on Dell Optiplex (Generic Question)

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

I've got an old Dell Optiplex (Pentium-II, 1998 Vintage) which is successfully running an X100P card. I'm hoping to upgrade to a TDM400. Has anybody tried running these cards in old Optiplex machines? I'm not particularly worried about horsepower - more about the motherboard having a PCI bus that's able to power up the card... -Ronan

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

Shantanu, let's continue here. You first noticed this on a Dell OptiPlex 755. I think it covers all Dell OptiPlex/Latitude/Precision models that are PCIe based with Intel LoM (LAN on motherboard) utilizing the BIOS PXE OROM, based on the similarity of these systems. The symptoms are that PXELINUX requests pxelinux.cfg/<UUID> by TFTP (but it might not strictly be a TFTP issue) when not

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 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

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

hi, i upgraded my testsystem running on a Dell Optiplex 780 fine for the last five years from Debian 8 to Debian 9. It also crashes on boot, after complaining abount an errer for the mcelog (-16) mounting the root partition (/dev/md0) loading parport driver (?) afterwards my monitor is out of frequency was not able to run further tests right now. best regards Thomas --------------

Hi, I am havind deep trouble with a bunch of our newly arrived Optiplex 330 as it can't run Centos 5.2 property. The installation works fine, but when it boots up, it can't be connected to the network. I am getting error saying " link is not ready" when doing system-config-network. I check lspci and it can detect the network controller no problem. The light next to the cable

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

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

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 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,

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,

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.

Our site has many Dell OptiPlex 790s, all of which are unable to use the 'localboot' PXELINUX option as they either hang at 'Booting from local disk...' or immediately reboot depending on which SYSLINUX version is used. Many people have suggested using chain.c32 to chain load the local disk as a workaround, but this causes problems with Windows 7 BitLocker as it detects the chain

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

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,

Notice the same thing happens with optiplex 790 (core i5 sandy bridge). With 790 too everything is ok with pxelinx 4.0.7. I'll post a wireshark later. Le 25/02/2014 17:06, H. Peter Anvin a ?crit : > On 02/25/2014 07:45 AM, H. Peter Anvin wrote: >> On 02/25/2014 07:07 AM, Eric PEYREMORTE wrote: >>> I did some additional tests : >>> >>> On a dell optiplex