Laptop/HP

Even if UEFI, Arch Linux and (e.g.) GRUB are correctly configured and with the correct UEFI NVRAM variables set, the system may not boot from the HDD/SSD. The problem is that HP hard coded the paths for the OS boot manager in their UEFI boot manager to \EFI\Microsoft\Boot\bootmgfw.efi to boot Microsoft Windows, regardless of how the UEFI NVRAM variables are changed. There are two workarounds:

The latest HP firmware allows defining a "Customized Boot" path in the UEFI pre-boot graphical environment. Select the "Customized Boot" option in the UEFI pre-boot graphical environment under "Boot Options" and set the path to your OS boot loader on the ESP (see EFI system partition), e.g.:

\EFI\grub\grubx64.efi

Always verify the correct path to the .efi file. Also, adjust the device boot order (also in the UEFI pre-boot graphical environment) to boot this entry first.

Change the UEFI application path of the OS boot loader to that hard coded path. On your EFI system partition; e.g. with esp being the EFI system partition mountpoint:

# mkdir -p esp/EFI/Microsoft/Boot
# cp esp/EFI/grub/grubx64.efi esp/EFI/Microsoft/Boot/bootmgfw.efi

or

# mkdir -p esp/EFI/BOOT
# cp esp/EFI/grub/grubx64.efi esp/EFI/BOOT/BOOTx64.EFI

Since Linux 4.1x, laptop's fan may not spin down to a lower rev step (and noise) effectively appearing stuck at higher spinning speed with no apparent temperature reason. Possible workarounds are loading a 3D application, a quick suspend to ram or power off for more than 10 minutes. If those tricks do not work, the max CPU frequency can be set to a lower one. See CPU frequency scaling#Setting maximum and minimum frequencies. Related: [2] [3]

Follow the steps outlined in Suspend and hibernate#Hibernation. The suspend to disk process works correctly, but the laptop does not power itself off. To fix this, create the following file:

/etc/systemd/system/sleep.conf

[Sleep]
HibernateMode=shutdown

This file tells systemd to write shutdown instead of platform to /sys/power/disk before writing disk to /sys/power/state.

For making the mute LED work, append model=alc295-hp-x360 to snd-hda-intel's kernel module parameters.

For making the mute LED work, append model=hp-mute-led-mic3 to snd-hda-intel's kernel module parameters.

For making the mute LED work, append model=hp-dock to snd-hda-intel's kernel module parameters.

This Section applies if running lsusb shows a line containing 06cb:00df Synaptics, Inc.. There's at least two firmware issues that may make the fingerprint reader not work. Both can be solved with fwupd. Running fwupdmgr get-devices shows two sub-devices belonging to the fingerprint reader: The "Prometheus" device and its IOTA Config.

• if fprintd-enroll doesn't find the fingerprint reader, try using fwupdmgr to update its firmware (possibly enabling the lvfs-testing remote, see man fwupdmgr)
• if fprintd-enroll now finds the reader, but shows something like enroll-unknown-error, the version of fwupd you're using likely has the bug that prevents it from updating the Prometheus IOTA Config. To fix this, remove fwupd and install an older version of the package (1.5.9 worked) and use it, like before, to update your firmware. It's possible that you'll have to download the firmware package manually from fwupd.org because of a mismatched sha1 checksum in the automatic download. Don't forget to run pacman -Syu afterwards to remove the outdated fwupd package.
• An additional step that may help is resetting the reader's own storage from the BIOS setup, hit Esc during boot-up to enter the BIOS setup and check the "reset fingerprint on boot" checkbox in the Security section. Make sure none of the operating systems that are currently installed require a fingerprint for anything, though.

Upgrade to kernel >= 6.2.7 and add the following to your kernel boot parameters:

amdgpu.sg_display=0

Check it the parameter was applied successfully with:

$ cat /proc/cmdline

Driver issue tracker: GitLab

For EliteBook 845 G10 with AMD Ryzen 7 PRO 7840HS, the CPU frequency may be locked at 400-544MHz when switched to battery, a workaround is to blacklist the `amd_pmf` module.

/etc/modprobe.d/cpufreq.conf

blacklist amd-pmf

Driver issue tracker: Bugzilla

If the hardware buttons for volume don't work, add enable_5_button_array=1 to intel_hid's kernel module parameters.

After shuting down from a Linux distribution, HP Omen 16 does not fully shutdown all the devices causing battery draining or energy draining when plugged. This may heat up the PC over 85oC overnight possibly breaking the components. Unfortunately the latest BIOS (F.06) does not resolve the issue.

To be able to use Arch Linux (and any Linux distribution) there are two ways:

1. After shutting down, press the shutdown ACPI button during 5 seconds. This will trigger a hardware shutdown, avoiding any power consumption.
2. When using Windows dual boot, boot Windows and shut it down from there.

• HP

• Pages or sections flagged with Template:Style
• Sections flagged with Template:Remove