similar to: HP Elitebook 8460p

Hi, all. I'm intending to install CentOS 7 on a HP Elitebook 8460p. Does anybody have any experience of this? Many thanks for any help. Cheers, Phil...

Hi Phil I have Fedora 20, Fedora21, and Fedora 22 installed on an HP Elitebootk Folio 1040. The only problem with Fedora 22 was, that anaconda required a GPT partition table to install an UEFI system. But after having changed from MBR to GPT partition table (using gdisk), no problems any more. I can not explain why anaconda required the UEFI installation: The SD-disk on the laptop is far less

> > Hi there, > I have experienced problems on HP Elitebook 2560p and 8460p > latest firmware installed: > 2560p 68SSU ver. F50. 08/04/2014 > 8460p 68SCF ver. F50. 08/04/2014 > > > PXE boot, syslinux.efi gets perfectly TFTP transferred, it nevers asks for ldlinux.e64, and immediately gives up. > > I have traced the problem to: > >

Hi there, I have experienced problems on HP Elitebook 2560p and 8460p latest firmware installed: 2560p 68SSU ver. F50. 08/04/2014 8460p 68SCF ver. F50. 08/04/2014 PXE boot, syslinux.efi gets perfectly TFTP transferred, it nevers asks for ldlinux.e64, and immediately gives up. I have traced the problem to: /syslinux-6.03/efi/udp.c\core_udp_open()

> > Not being able to boot should probably qualify > > as good reason for HP to update the > > firmware, IMHO. > > > I agree but considering the problem appears when > PXE booting an EFI image requiring the Binding Services > of the NIC well I'm not really sure if they would pay any attention. > BTW the same failing hardware has not problem booting > MS

netbook (http://www.laptopspark.com) The world's largest computer maker (http://www.laptopspark.com/products/HP-G62-340US-NoteBook-AMD-Athlon-II-Dual-Core-P340220GHz-156-3GB-Memory-320GB-HDD-5400rpm-DVD-Super-Multi-ATI-Radeon-HD-4250-laptop-2047.html) startles analysts by scaling back its revenue forecast for the second time in as many quarters. It cites weak demand for desktops and

> Not being able to boot should probably qualify > as good reason for HP to update the > firmware, IMHO. > I agree but considering the problem appears when PXE booting an EFI image requiring the Binding Services of the NIC well I'm not really sure if they would pay any attention. BTW the same failing hardware has not problem booting MS bootmgr.efi but analyzing its code I see

> > >_ If similar newer HW can boot correctly, > >perhaps requesting from HP to > >release updated firmware versions for those systems that > >are failing might help? > > > I think we are aiming in the right direction here, > unfortunately HP (and other vendors) only update firmware bugs > when either heavily impacting functionality or security. Not

>_ There >have been some patches already merged after 6.03. >Unfortunately, currently there is no _official_ >git repository *publicly* available / > accessible that would contain such patches. > So bad; Any chance to get access to an updated git repository? it takes long time debugging this kind of things. > _ The official Syslinux 6.03 uses a one-year-old (ATM) gnu-efi

Hi, I have an Elitebook but I am unable to even load the kernel or get to a point where user interaction is posible. The bootloader reboots the machine just before or after the amount of memory is shown. Anyone with simliar problems an newer HP notebooks? Gr Matthias

Hello, I'm considering the HP EliteBook 6930 or the Dell Latitude e6400 notebooks for CentOS. I'm planning on using these in a situation in which they are always on, and I want low power and low noise and high reliability. HP claims up to 24 hours battery power and Dell up to 19 hours. I figure this can bridge the gap for most power outages in my neighborhood. I realize that I

https://bugs.freedesktop.org/show_bug.cgi?id=35171 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #5 from Ilia Mirkin <imirkin at

CentOS 5.6 x64 installs successfully on HP 6200pro SFF box with Intel Q65X Express chipset (including HD graphics), Core i5 and added NVS300 graphics card. Actually, it works great. HP lists "RedHat Enterprise x64" as a supported OS. The 6200pro is a "business desktop" that became available in early summer 2011. CentOS 6.2 x64 install halts during initial boot, with boot

Hi, all. I'm trying to install the EPEL repo on a fully up to date CentOS 6.4. I'm using wget to download from my usual source but after I install it via `sudo rpm -ivh epel-xxxxx` it's not actually there in `/etc/yum.repos.d`. Trying to install it again, Yum just tells me it's already installed. I've no idea where it is installed if it is (which I don't think it is)

Hi. I have a CentOS server (a Dell 860) with two drives in it. One is running CentOS 6.4 which I want to keep & the bigger 400GB drive has Debian 7 on it which I want to erase & use for backups. Which is the best way to go about achieving my intended goal? The Debian drive is not mounted when Centos is booted. Any help appreciated. Cheers, Phil... -- currently (ab)using Arch

On Thu, Jul 9, 2015 at 5:30 AM, Patrick Masotta <masottaus at yahoo.com> wrote: >>>> > > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) > > The only solution for these is to use our own stack (likely full > TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL). > Does the handle for Pxebc contain a Net?

> > Today there are certain PCs i.e Elitebook 2560p, Elitebook 8460p that with > updated FW ""to the last known version"" cannot PXE boot syslinux for the > above mentioned reasons. > > We have already talked about this with Gene an there's an strategy for making > syslinux able to deal with these "weirdo" FWs. > It's just a matter

>>> > 1) There's not "any" SB protocol present (Elitebook 8460p/2560p) The only solution for these is to use our own stack (likely full TCP/IP like lwIP) and connect to the Net GUID (EFI_SIMPLE_NETWORK_PROTOCOL).? Does the handle for Pxebc contain a Net?? >>> It does contain a Net but there are 2 issues with SNP: 1) The interface is different than

>>> > It does contain a Net but there are 2 issues with SNP: > 1) The interface is different than UDPv4/TCPv4 protocols; this imply lot of code. Not as much as you may think.? We already have lwIP implemented into lpxelinux.0.? It's more a matter of using more glue. > 2) SNP has its non-blocking transmit issues ; see "Flaws in the design" at >

On Fri, Aug 14, 2015 at 11:42 AM, Patrick Masotta via Syslinux <syslinux at zytor.com> wrote: >>>>> > website (meaning, HP could test their firmware to be compatible with > Syslinux and with non-Windows OSes). If the HP firmware could be made > (more) compliant with UEFI specs, or if it could be improved and still > be compliant with UEFI specs, wouldn't