Patrick Masotta
2015-Mar-12 14:55 UTC
[syslinux] Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
> 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 bootmgr.efi performs the TFTP transfers not relying on Binding Services (probably using some PXE TFTP service)> Is it > possible that the reported network boot behavior is > different between cold-boot and warm-boot? >Exactly the same behavior. Please consider the environment never crashes, syslinux.efi just bails because it cannot continue w/o the Binding Services, it properly returns control to HP firmware which displays a proper message of a failing booting image.> At any rate, and > considering several reports about different HP > hardware failing to boot syslinux.efi, I would > tend to think that contacting HP and > requesting an updated firmware release could be > helpful. >I agree that this looks like an HP problem. I'm holding my doubts on HP willingness to fix this.> FWIW, > there are (recent) patches in gnu-efi that were originated > by developers somewhat related to (or > working for) HP. This might be another hint > to both, using an updated gnu-efi submodule and/or needing > an updated firmware from HP for these failing systems. >I'm going to take a look at this point> Let's see what kind of info or tests the > Syslinux's devs. would need for > troubleshooting the particular hardware. >Trust me; in this case they won't need pcap files.> I would > guess that CSM mode is actually verified to be set to > "off" > (i.e. UEFI mode), among > others ("secure boot", "fast boot", > "whichever > fancy name" boot...). > Sometimes some minor setting that was overlooked > can be the cause of wasting hours of > troubleshooting. >I'm booting "plain and simple" UEFI mode Best, Patrick
Patrick Masotta
2015-Mar-13 11:54 UTC
[syslinux] Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
I have installed the latest gnu-efi sources, (git clone git://git.code.sf.net/p/gnu-efi/code gnu-efi-code) recompiled and tested getting exactly the same results. I have posted the issue at HP http://h30434.www3.hp.com/t5/Notebook-Operating-Systems-and-Software/EFI-firmware-bug-on-HP-EliteBook-2560p-8460p/td-p/4931486 Best, Patrick
Ady
2015-Mar-15 20:23 UTC
[syslinux] Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
> > 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 bootmgr.efi > performs the TFTP transfers not relying on Binding Services > (probably using some PXE TFTP service)When looking for updates for these particular HP EliteBook systems, users must choose an OS before being presented with available updates, even when the update is not supposed to be dependent on a particular OS, such as firmware. The opposite though, could potentially be a valid concern: updating to a newer firmware version while the (current) OS might not be able to boot (e.g. having Windows XP already installed while updating to a UEFI firmware version without CSM). Under this procedure, when users select "Windows 8.1 64-bits", the latest UEFI firmware version at this time is "F50" (year 2014), but when selecting "Linux" as OS, then the respective latest version available is "F21" (year 2011). Additionally, going back to a prior firmware version is not possible (or at least not supported). My guess is that HP is not testing the newer firmware versions with anything but Windows' bootmgr.efi. Regards, Ady.> > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux >
Patrick Masotta
2015-Mar-15 23:05 UTC
[syslinux] Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
> When > looking for updates for these particular HP EliteBook > systems, > users must choose an OS before > being presented with available updates, > even when the update is not supposed to be > dependent on a particular > OS, such as > firmware. The opposite though, could potentially be a valid > concern: updating to a newer firmware > version while the (current) OS > might not be > able to boot (e.g. having Windows XP already installed > while updating to a UEFI firmware version > without CSM). > > Under this > procedure, when users select "Windows 8.1 > 64-bits", the > latest UEFI firmware > version at this time is "F50" (year 2014), but > when selecting "Linux" as OS, then > the respective latest version > available is > "F21" (year 2011). Additionally, going back to a > prior > firmware version is not possible (or > at least not supported).I know; I have used Windows 8.1 64 bits in order to download the newest firmware version F50 (2014)> My > guess is that HP is not testing the newer firmware versions > with > anything but Windows' > bootmgr.efi. >You are probably right; that makes me wonder if SL shouldn't then check if the UDP/TCP4 Binding Service is not available then default to TFTP transfers under PXE protocol control (like bootmgr.efi does)? Best, Patrick
Reasonably Related Threads
- Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
- Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
- Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
- Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p
- Problems PXE booting syslinux.efi on HP EliteBook 2560p / 8460p