HP Envy x360 (AMD Ryzen 7) won't run Linux after BIOS update 8/20/2018 - 15.19.0.0, F.19 Rev.A

[meller]

I can't boot - not even run USB installation memory stick - of Linux system (using OpenSuse Tumbleweed). It seems that this BIOS update has disabled my HP Envy x360 laptop from running Linux.

Here is more detailed info about the BIOS update:

Type:

BIOS

Version:

F.19 Rev.A

Operating systems:

Windows 10 (64-bit)

Release date:

Aug 29, 2018

File name:

sp91692.exe

(19.9 MB)

Fix and enhancements:

- Fixes an issue which causes the touch screen to stop functioning properly.

It appears that this BIOS update may not be compatible with the latest Linux kernels - I also tried load from Ubuntu 18.04.1 LTS USB stick. After a short moment the screen goes blank and the system hangs.

HP software team: please kindly fix this issue in your next update.

Thanks.

[pepe999]

Hi,

The BIOS upgrade has probably restored the original settings with Secure Boot enabled which won't allow to boot anything except the original OS. Just in case try a manual boot with F9 at boot and then choose the appropriate boot option. Works for me on my Probook turned to Hackintosh/Sabayon (Windows free).

[meller]

Thanks for the reply. I tried both with and without secure boot. Same issue. In fact the Linux boot process does start ... but after reaching a certain point (not sure which one) the screen goes blank.

Interestingly, booting with an older Linux Kernel version (4.12) does work but not with the latest ones (4.17, 4.18).

[meller]

HI HP ... and AMD firrmware S/w ... team (it really should go to the BIOS s/w developers):

After investigating in other Linux forums it appears that the latest F.19 Rev.A BIOS update  made the most recent Linux Kernels incompatible with this update.

Could you please take a closer look and let me - and all the other users who are (or going to be) affected by this (apparently untested by Linux) - know what the next steps are??

Many thanks.

[meller · Accepted solution]

After upgrading to Kernel 4.18.8 the problem was gone.