Odd booting Behaviour/Boot Lottery On HP Elitebook 735

Im experiencing very odd behaviour from grub on an HP elitebook 735, effectively something I learned to call a boot lottery.

First of all the ONLY chance of a successful boot, is through the use of a boot menu, otherwise a hard lock on an HP sure start splash screen is imminent, and a decryption prompt is overlaying the HP logo.

If a boot menu is used however it looks completely normal, and a prompt is on a black background. After a successful decrypt, it flashes to a black screen, then the HP logo, afterwards(and this is the lottery part) it has about a 1 in 5 chance to boot. I’m perplexed as I can’t even begin to understand what’s up with the bios/grub here.

I should add, no info is displayed on the splash screen whatsoever at any time.

Anyone has any ideas?

Hi @ImmortalZ, and welcome!

In order for us, or anyone for that matter, to be able to provide assistance, more information is necessary. To that end, please see:

Hope you manage!


:bangbang: Tip: :bangbang:

To provide terminal output, copy the text you wish to share, and paste it here, surrounded by three (3) backticks, a.k.a grave accents. Like this:

```
pasted text
```

This will just cause it to be rendered like this:

Portaest sed
elementum
cursus nisl nisi
hendrerit ac quis
sit
adipiscing
tortor sit leo commodo.

Instead of like this:

Portaest sed elementum cursus nisl nisi hendrerit ac quis sit adipiscing tortor sit leo commodo.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby improving legibility and making it much easier for those trying to be of assistance.


:bangbang::bangbang: Also, if your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

Please edit your post accordingly.


At first glance I don’t see anything specific to you laptop in the Arch wiki:

https://wiki.archlinux.org/title/Laptop/HP

The closest I can quickly see is:

https://wiki.archlinux.org/title/HP_EliteBook_745_G5

But I’m no expert, especially not laptops and neither HP, so I might be completely wrong.

Best would be to provide the info as requested earlier in my post. Chances are better of obtaining help then.

Afraid i cant provide much apart from grub configuration photo and symptoms, now it just hangs on an hp logo with a manjaro logo underneath, but opens the grub menu consistently. One in 10 times it just opens and works, boot options and settings do not seem to affect the behaviour. Was working just now, now again its not. And then it magically springs back.

Can you boot using a live ISO? Because if not, I’m suspecting a hardware problem…if you can, boot with that and provide the requested info.

Other than that,

None from me. Sorry.

:sob:

I just booted into the installed version again…
But yeah, live iso works fine always, seems to be hp internal stuff, probably the ssd controller being…uncooperative. Guess ill make a shaman effigy out of old hard drives, and just suspend the machine.

Sounds like…like…I don’t know what it sounds like to be honest…

Like it just does what it wants, other distros i tried to install created even worse esoteric issues, zorin just didn’t do graphics, arch stopped booting with a freeze, Debian couldn’t connect to any mirrors, and didnt want to install wifi drivers from usb even, only windows seemed to just work. Well and manjaro, perfectly once it actually boots
Its magic at this stage for me

White and black magic it seems. And it seems white magic is losing…

:smiling_face_with_tear: Maybe switching kernels will do something

check in bios if fast boot is disabled - you may not have this option;
AHCI enabled, RAID disabled…
from the live usb provide the above requested inxi output;
from chroot provide logs from the failed boot:
journalctl -b-1 -p4 --no-pager

Is it possible on an already booted machine running an installed version, or is a live iso required, fast boot doesn’t seem to affect anything and is disabled, ahci is forced, raid controller is absent.

It is. Just run the command specified in the terminal on the first successful boot after failures.

 journalctl -b-1 -p4 --no-pager

Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20210730/dswload2-162)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210730/psobject-220)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: pci 0000:00:00.2: can't derive routing for PCI INT A
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: pci 0000:00:00.2: PCI INT A: not connected
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20210730/exoparg2-393)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI Error: Aborting method \_TZ.GETP due to previous error (AE_AML_PACKAGE_LIMIT) (20210730/psparse-529)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI Error: Aborting method \_TZ.CHGZ._CRT due to previous error (AE_AML_PACKAGE_LIMIT) (20210730/psparse-529)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20210730/exoparg2-393)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI Error: Aborting method \_TZ.GTTP due to previous error (AE_AML_PACKAGE_LIMIT) (20210730/psparse-529)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI Error: Aborting method \_TZ.CHGZ._TMP due to previous error (AE_AML_PACKAGE_LIMIT) (20210730/psparse-529)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI BIOS Error (bug): AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20210730/exoparg2-393)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI Error: Aborting method \_TZ.GETP due to previous error (AE_AML_PACKAGE_LIMIT) (20210730/psparse-529)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI Error: Aborting method \_TZ.CHGZ._CRT due to previous error (AE_AML_PACKAGE_LIMIT) (20210730/psparse-529)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI: thermal: [Firmware Bug]: No valid trip found
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Dec 24 13:56:51 immortal-hpelitebook735g5 kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B06 (\_SB.PCI0.SMBS.SMBO) (20210730/utaddress-204)
Dec 24 13:56:52 immortal-hpelitebook735g5 kernel: ipmi_si: Unable to find any System Interface(s)
Dec 24 13:56:52 immortal-hpelitebook735g5 kernel: r8169 0000:01:00.0: can't disable ASPM; OS doesn't have ASPM control
Dec 24 13:56:52 immortal-hpelitebook735g5 kernel: hp_wmi: query 0x4 returned error 0x5
Dec 24 13:56:52 immortal-hpelitebook735g5 kernel: hp_wmi: query 0xd returned error 0x5
Dec 24 13:56:52 immortal-hpelitebook735g5 kernel: hp_wmi: query 0xd returned error 0x5
Dec 24 13:56:52 immortal-hpelitebook735g5 systemd[548]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
Dec 24 13:56:52 immortal-hpelitebook735g5 bluetoothd[548]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Dec 24 13:56:52 immortal-hpelitebook735g5 bluetoothd[548]: src/plugin.c:plugin_init() Failed to init vcp plugin
Dec 24 13:56:52 immortal-hpelitebook735g5 bluetoothd[548]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Dec 24 13:56:52 immortal-hpelitebook735g5 bluetoothd[548]: src/plugin.c:plugin_init() Failed to init mcp plugin
Dec 24 13:56:52 immortal-hpelitebook735g5 bluetoothd[548]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Dec 24 13:56:52 immortal-hpelitebook735g5 bluetoothd[548]: src/plugin.c:plugin_init() Failed to init bap plugin
Dec 24 13:56:53 immortal-hpelitebook735g5 kernel: resource sanity check: requesting [mem 0x000c0000-0x000dffff], which spans more than PCI Bus 0000:00 [mem 0x000c0000-0x000c3fff window]
Dec 24 13:56:53 immortal-hpelitebook735g5 kernel: caller pci_map_rom+0x65/0x180 mapping multiple BARs
Dec 24 13:56:53 immortal-hpelitebook735g5 kernel: amdgpu 0000:04:00.0: amdgpu: Unable to locate a BIOS ROM
Dec 24 13:56:53 immortal-hpelitebook735g5 kernel: amdgpu 0000:04:00.0: amdgpu: Fatal error during GPU init
Dec 24 13:56:53 immortal-hpelitebook735g5 kernel: amdgpu: probe of 0000:04:00.0 failed with error -22
Dec 24 13:56:53 immortal-hpelitebook735g5 kernel: serial 0000:01:00.1: VPD access failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update
Dec 24 13:56:53 immortal-hpelitebook735g5 kernel: serial 0000:01:00.2: VPD access failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update
Dec 24 13:56:53 immortal-hpelitebook735g5 kernel: pci 0000:01:00.3: VPD access failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update
Dec 24 13:56:53 immortal-hpelitebook735g5 kernel: ehci-pci 0000:01:00.4: VPD access failed.  This is likely a firmware bug on this device.  Contact the card vendor for a firmware update
Dec 24 13:56:58 immortal-hpelitebook735g5 kernel: kauditd_printk_skb: 214 callbacks suppressed

Here is the first part of the output, cant post it whole, as its too big apparently

Then provide the link output when running:

journalctl -b-1 -p4 --no-pager | curl -F "file=@-" https://0x0.st

https://0x0.st/o5x1.txt

There you go, sorry kinda of a noob

Seems like its trying to run xorg a lot, unsuccessfully

now provide the inxi output:
inxi -Fazv7
and you probably have to add the kernel parameters mentioned in the above link:

Or:

inxi -Fazv7 | curl -F "file=@-" https://0x0.st

https://0x0.st/o5x_.txt

With the kernel options it now boots every second time or so it seems, not perfect but livable

Thank you for the help) Shame that it seems to be a widespread issue on mobile zen chips

did you added all of these parameters:

acpi_backlight=vendor idle=nomwait amdgpu.gpu_recovery=1 amd_iommu=pt audit_enabled=0

did you also modified the mkinitcpio.conf and added:
MODULES=(amdgpu radeon)