Problems with Manjaro Linux on a HP Elitebook 755 G5 with Ryzen 7 and Vega 10


#1

I bought a HP EliteBook 755 laptop from here: https://store.hp.com/UKStore/Merch/Product.aspx?id=3UN70EA&opt=ABU&sel=NTB&lang=en-GB

Specs: Ryzen7 Pro, 256GB SSD, 8GB RAM.

I tried installing from a bootable USB with the latest XFCE release but the screen would either show a kernel panic on legacy mode, or stay dark on UEFI. Never manage to get any systemd output with this so I just gave up and switched to Architect. While I managed to get it to start the install process 2 times (out of 40+ tries) I did not manage to get it to finish as for some reason it would not let me install grub nor configure fstab.

First: here’s what I’ve experimented with:

  • Secure boot off; switching between UEFI and Legacy, UEFI would either blacksceen, kernel panic or work (2 out of 40+ tries). Legacy would always kernel panic but the stacktrace is printed with large letters and it’s truncated, probably useless. I do have a decent picture of the stacktrace on UEFI (see below). I don’t always get the stacktrace to display though, most of the time it’s just black. Removing quiet from the parameters does not do anything.
  • Switching between free and nonfree drivers, in all combinations of UEFI and Legacy. So far the 2 tries I got Architect working were on UEFI with free drivers.
  • Having iommu=soft in the parameters might help… both tries that got me to Architect had it. But many more failed as well.
  • Once architect started it was straightforward, but I don’t know why I could never install grub successfully. It prompts me about /boot/uefi and if I want to change to /boot, but did not manage to try that yet (it’s hard to even get to that stage). Fstab config I assume follows grub so no wonder it always failed.
  • I can not give you an inxi output from that laptop as I hardly am able so start a shell. Next time I manage to get to a shell I’ll try to get it.
  • I’ve formatted and re-installed both architect and XFCE on the USB multiple times. Also I checked the sha1 of both ISO files and they are matching.

Here’s a screenshot of the stacktrace I get on UEFI/free drivers/iommu=soft:

Also, I get these errors when actually running an install:

My assumption is that the kernel version in Architect have something to do with this… but then again the hardware itself might be faulty. Anyway, I would like to install a linux419 kernel on this laptop and see if they happen again.

If you have any idea what I need to do to get it to install properly please let me know. And if you do give advice (much appreciated) please write it with as much detail as possible, some things might seem trivial and common knowledge to you but I most probably never heard of them (especially with kernel parameters and bios settings).

Thanks in advance!


[Unstable Update] 2018-12-25 - KDE Frameworks, KDE Apps, Deepin, ZFS, LibreOffice, QT, Mesa, Systemd
#2

Another segfault that might be relevant:
UEFI/removed quiet/iommu=soft/free drivers/Architect


#3

Please provide specific versions. This “latest” version changes over time.

I’d start with checking for a BIOS update, then concentrate on getting a live environment up-and-running.

If I remember correctly, the version 18.0 images have kernel 4.19.


#4

Latest as displayed on https://manjaro.org/get-manjaro/, downloaded yesterday. So for XFCE it’s Manjaro XFCE Edition (18.0) and Architect is Manjaro-Architect ISO (17.1.12).

I’ve done an uname -a on Architect and it had kernel 4.14.

Will try a bios update tomorrow morning.

In the end I managed to get it to start Architect and managed to install the CLI system but not with grub (second option, don’t remember the name). Now I only see a black screen when starting up.

Tomorrow I’ll post an update with what I manage to do.

Thanks!


#5

OK so I’ve tried multiple things over the weekend, what worked (partially):

  • Downgraded the bios, now I can boot into the USB in UEFI every time.
  • Managed to install a desktop system with Architect.
  • I still need to pass iommu=soft to manage to get past GRUB after install.

But I can not get to a successful start every time. It’s like a 1/20 chance to do it successfully.
There is this error in the logs:

Nov 18 09:40:01 me kernel: BIOS-e820: [mem 0x0000000004000000-0x0000000004009fff] ACPI NVS
Nov 18 09:40:01 me kernel: BIOS-e820: [mem 0x000000007acce000-0x000000007b3cdfff] ACPI NVS
Nov 18 09:40:01 me kernel: BIOS-e820: [mem 0x000000007b3ce000-0x000000007b44dfff] ACPI data
Nov 18 09:40:01 me kernel: efi:  ACPI=0x7b44d000  ACPI 2.0=0x7b44d014  SMBIOS=0x7a5c9000  SMBIOS 3.0=0x7a5c7000  ESRT=0x77870718  MEMATTR=0x76a0d698 
Nov 18 09:40:01 me kernel: ACPI: Early table checksum verification disabled
Nov 18 09:40:01 me kernel: ACPI: RSDP 0x000000007B44D014 000024 (v02 HPQOEM)
Nov 18 09:40:01 me kernel: ACPI: XSDT 0x000000007B420188 0000F4 (v01 HPQOEM SLIC-BPC 00000001      01000013)
Nov 18 09:40:01 me kernel: ACPI: FACP 0x000000007B43B000 00010C (v05 HPQOEM SLIC-BPC 00000001 HP   00000001)
Nov 18 09:40:01 me kernel: ACPI: DSDT 0x000000007B423000 010398 (v02 HPQOEM 83D5     00000000 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: FACS 0x000000007B314000 000040
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B44A000 00012A (v02 HP     ShmTable 00000001 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B444000 00533D (v02 AMD    AmdTable 00000002 MSFT 02000002)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B442000 00119C (v01 AMD    AMD CPU  00000001 AMD  00000001)
Nov 18 09:40:01 me kernel: ACPI: CRAT 0x000000007B441000 000810 (v01 AMD    AMD CRAT 00000001 AMD  00000001)
Nov 18 09:40:01 me kernel: ACPI: CDIT 0x000000007B440000 000029 (v01 AMD    AMD CDIT 00000001 AMD  00000001)
Nov 18 09:40:01 me kernel: ACPI: UEFI 0x000000007B331000 000042 (v01 HPQOEM EDK2     00000002      01000013)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B43F000 000EC4 (v02 HP     UcsiAcpi 00000001 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B43E000 0000FB (v02 HP     UcsiCntr 00000001 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B43D000 0003C8 (v02 HPQOEM Tpm2Tabl 00001000 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: TPM2 0x000000007B43C000 000034 (v03 HPQOEM EDK2     00000002      01000013)
Nov 18 09:40:01 me kernel: ACPI: ASF! 0x000000007B43A000 00006E (v32 HPQOEM 83D5     00000001 HP   00000001)
Nov 18 09:40:01 me kernel: ACPI: MSDM 0x000000007B439000 000055 (v03 HPQOEM SLIC-BPC 00000000 HP   00000001)
Nov 18 09:40:01 me kernel: ACPI: SLIC 0x000000007B438000 000176 (v01 HPQOEM SLIC-BPC 00000001 HP   00000001)
Nov 18 09:40:01 me kernel: ACPI: WSMT 0x000000007B437000 000028 (v01 HPQOEM 83D5     00000001 HP   00000001)
Nov 18 09:40:01 me kernel: ACPI: HPET 0x000000007B436000 000038 (v01 HPQOEM 83D5     00000001 HP   00000001)
Nov 18 09:40:01 me kernel: ACPI: APIC 0x000000007B435000 000138 (v02 HPQOEM 83D5     00000001 HP   00000001)
Nov 18 09:40:01 me kernel: ACPI: MCFG 0x000000007B434000 00003C (v01 HPQOEM 83D5     00000001 HP   00000001)
Nov 18 09:40:01 me kernel: ACPI: IVRS 0x000000007B421000 0000D0 (v02 AMD    AMD IVRS 00000001 AMD  00000000)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B44C000 000884 (v01 HP     HPADNBWL 00001000 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B41F000 000032 (v01 HP     HPCONDEV 00001000 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B422000 0008CB (v01 AMD    AmdTable 00000001 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: FPDT 0x000000007B41E000 000044 (v01 HPQOEM EDK2     00000002      01000013)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B41C000 001B93 (v01 AMD    AmdTable 00000001 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: BGRT 0x000000007B41B000 000038 (v01 HPQOEM EDK2     00000002      01000013)
Nov 18 09:40:01 me kernel: ACPI: SSDT 0x000000007B44B000 0002F9 (v02 HP     PwrCtlEv 00000001 INTL 20160527)
Nov 18 09:40:01 me kernel: ACPI: Local APIC address 0xfee00000
Nov 18 09:40:01 me kernel: ACPI: PM-Timer IO Port: 0x408
Nov 18 09:40:01 me kernel: ACPI: Local APIC address 0xfee00000
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x0c] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x0d] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x0e] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: LAPIC_NMI (acpi_id[0x0f] high edge lint[0x1])
Nov 18 09:40:01 me kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov 18 09:40:01 me kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
Nov 18 09:40:01 me kernel: ACPI: IRQ0 used by override.
Nov 18 09:40:01 me kernel: ACPI: IRQ9 used by override.
Nov 18 09:40:01 me kernel: Using ACPI (MADT) for SMP configuration information
Nov 18 09:40:01 me kernel: ACPI: HPET id: 0x10228210 base: 0xfed00000
Nov 18 09:40:01 me kernel: ACPI: Core revision 20180810
Nov 18 09:40:01 me kernel: PM: Registering ACPI NVS region [mem 0x04000000-0x04009fff] (40960 bytes)
Nov 18 09:40:01 me kernel: PM: Registering ACPI NVS region [mem 0x7acce000-0x7b3cdfff] (7340032 bytes)
Nov 18 09:40:01 me kernel: ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
Nov 18 09:40:01 me kernel: ACPI: bus type PCI registered
Nov 18 09:40:01 me kernel: acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov 18 09:40:01 me kernel: ACPI: Added _OSI(Module Device)
Nov 18 09:40:01 me kernel: ACPI: Added _OSI(Processor Device)
Nov 18 09:40:01 me kernel: ACPI: Added _OSI(3.0 _SCP Extensions)
Nov 18 09:40:01 me kernel: ACPI: Added _OSI(Processor Aggregator Device)
Nov 18 09:40:01 me kernel: ACPI: Added _OSI(Linux-Dell-Video)
Nov 18 09:40:01 me kernel: ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
Nov 18 09:40:01 me kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Nov 18 09:40:01 me kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20180810/dswload2-160)
Nov 18 09:40:01 me kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20180810/psobject-221)
Nov 18 09:40:01 me kernel: ACPI Error: Ignore error and continue table load (20180810/psobject-604)
Nov 18 09:40:01 me kernel: ACPI Error: Skip parsing opcode Scope (20180810/psloop-543)
Nov 18 09:40:01 me kernel: ACPI: 12 ACPI AML tables successfully acquired and loaded
Nov 18 09:40:01 me kernel: ACPI: EC: EC started
Nov 18 09:40:01 me kernel: ACPI: EC: interrupt blocked
Nov 18 09:40:01 me kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Used as first EC
Nov 18 09:40:01 me kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0x3, EC_CMD/EC_SC=0x66, EC_DATA=0x62
Nov 18 09:40:01 me kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to handle transactions
Nov 18 09:40:01 me kernel: ACPI: Interpreter enabled
Nov 18 09:40:01 me kernel: ACPI: (supports S0 S1 S3 S4 S5)
Nov 18 09:40:01 me kernel: ACPI: Using IOAPIC for interrupt routing
Nov 18 09:40:01 me kernel: PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov 18 09:40:01 me kernel: ACPI: Enabled 8 GPEs in block 00 to 1F
Nov 18 09:40:01 me kernel: ACPI: Power Resource [PXP] (off)
Nov 18 09:40:01 me kernel: ACPI: Power Resource [APPR] (off)
Nov 18 09:40:01 me kernel: ACPI: Power Resource [P0ST] (on)
Nov 18 09:40:01 me kernel: ACPI: Power Resource [P3ST] (on)
Nov 18 09:40:01 me kernel: ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
Nov 18 09:40:01 me kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 5 6 10 11) *0, disabled.
Nov 18 09:40:01 me kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 5 6 10 11) *0, disabled.
Nov 18 09:40:01 me kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 5 6 10 11) *0, disabled.
Nov 18 09:40:01 me kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 5 6 10 11) *0, disabled.
Nov 18 09:40:01 me kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 5 6 10 11) *0, disabled.
Nov 18 09:40:01 me kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 5 6 10 11) *0, disabled.
Nov 18 09:40:01 me kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 5 6 10 11) *0, disabled.
Nov 18 09:40:01 me kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 5 6 10 11) *0, disabled.
Nov 18 09:40:01 me kernel: ACPI: EC: interrupt unblocked
Nov 18 09:40:01 me kernel: ACPI: EC: event unblocked
Nov 18 09:40:01 me kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0x3, EC_CMD/EC_SC=0x66, EC_DATA=0x62
Nov 18 09:40:01 me kernel: ACPI: \_SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to handle transactions and events
Nov 18 09:40:01 me kernel: ACPI: bus type USB registered
Nov 18 09:40:01 me kernel: PCI: Using ACPI for IRQ routing
Nov 18 09:40:01 me kernel: pnp: PnP ACPI init
Nov 18 09:40:01 me kernel: pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov 18 09:40:01 me kernel: system 00:01: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 18 09:40:01 me kernel: system 00:02: Plug and Play ACPI device, IDs PNP0c01 (active)
Nov 18 09:40:01 me kernel: pnp 00:03: Plug and Play ACPI device, IDs HPQ8002 PNP0303 (active)
Nov 18 09:40:01 me kernel: pnp 00:04: Plug and Play ACPI device, IDs SYN306f SYN0100 SYN0002 PNP0f13 (active)
Nov 18 09:40:01 me kernel: system 00:05: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 18 09:40:01 me kernel: system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov 18 09:40:01 me kernel: pnp: PnP ACPI: found 7 devices
Nov 18 09:40:01 me kernel: ACPI: Power Button [PWRB]
Nov 18 09:40:01 me kernel: ACPI: Sleep Button [SLPB]
Nov 18 09:40:01 me kernel: ACPI: Lid Switch [LID]
Nov 18 09:40:01 me kernel: ACPI: Power Button [PWRF]
Nov 18 09:40:01 me kernel: ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
Nov 18 09:40:01 me kernel: ACPI: Thermal Zone [HEPZ] (30 C)
Nov 18 09:40:01 me kernel: ACPI: Thermal Zone [CPUZ] (57 C)
Nov 18 09:40:01 me kernel: ACPI: Thermal Zone [GFXZ] (0 C)
Nov 18 09:40:01 me kernel: ACPI: Thermal Zone [EXTZ] (47 C)
Nov 18 09:40:01 me kernel: ACPI: Thermal Zone [LOCZ] (51 C)
Nov 18 09:40:01 me kernel: ACPI: Thermal Zone [BATZ] (32 C)
Nov 18 09:40:01 me kernel: ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20180810/exoparg2-396)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_TZ.GETP, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20180810/exoparg2-396)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_TZ.GTTP, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_TZ.CHGZ._TMP, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: AE_AML_PACKAGE_LIMIT, Index (0x000000005) is beyond end of object (length 0x5) (20180810/exoparg2-396)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_TZ.GETP, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_TZ.CHGZ._CRT, AE_AML_PACKAGE_LIMIT (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B06 (\_SB.PCI0.SMBS.SMBO) (20180810/utaddress-213)
Nov 18 09:40:01 me kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov 18 09:40:01 me kernel: ACPI: AC Adapter [AC] (on-line)
Nov 18 09:40:01 me kernel: battery: ACPI: Battery Slot [BAT0] (battery present)
Nov 18 09:40:01 me kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000a8686f44 (20180810/exresop-560)
Nov 18 09:40:01 me kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20180810/dswexec-427)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 00000000fc99f004 (20180810/exresop-560)
Nov 18 09:40:01 me kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20180810/dswexec-427)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Needed [Buffer/String/Package], found [Integer] 000000003f700bcb (20180810/exresop-560)
Nov 18 09:40:01 me kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Index] (20180810/dswexec-427)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_SB.WMIV.WVPO, AE_AML_OPERAND_TYPE (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_TYPE (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Attempt to CreateField of length zero (20180810/dsopcode-134)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_SB.WMIV.WVPI, AE_AML_OPERAND_VALUE (20180810/psparse-516)
Nov 18 09:40:01 me kernel: ACPI Error: Method parse/execution failed \_SB.WMIV.WMPV, AE_AML_OPERAND_VALUE (20180810/psparse-516)

I tried acpi=off but this just makes it kernel panic instantly. Also did acpi=strict which may or may not have helped.

Here’s some extra information:
inxi -Fxxx

System:    Host: me Kernel: 4.19.2-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.1 Desktop: N/A wm: xfwm4 dm: LightDM 1.28.0 
           Distro: Manjaro Linux 
Machine:   Type: Laptop System: HP product: HP EliteBook 755 G5 v: N/A serial: <root required> Chassis: type: 10 
           serial: <root required> 
           Mobo: HP model: 83D5 v: KBC Version 08.43.00 serial: <root required> UEFI: HP v: Q81 Ver. 01.00.04 date: 06/03/2018 
Battery:   ID-1: BAT0 charge: 57.0 Wh condition: 57.0/57.0 Wh (100%) volts: 13.1/11.6 model: Hewlett-Packard Primary 
           type: Li-ion serial: 35721 2018/09/15 status: Full 
CPU:       Topology: Quad Core model: AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen 
           L2 cache: 2048 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 35150 
           Speed: 1371 MHz min/max: 1600/2200 MHz Core speeds (MHz): 1: 1369 2: 1432 3: 1369 4: 1371 5: 1376 6: 1380 7: 1591 
           8: 1511 
Graphics:  Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu 
           v: kernel bus ID: 04:00.0 chip ID: 1002:15dd 
           Display: x11 server: X.org 1.20.3 driver: amdgpu,ati unloaded: modesetting alternate: fbdev,vesa 
           resolution: <xdpyinfo missing> 
           OpenGL: renderer: AMD RAVEN (DRM 3.27.0 4.19.2-1-MANJARO LLVM 7.0.0) v: 4.5 Mesa 18.2.5 compat-v: 4.4 
           direct render: Yes 
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 
           chip ID: 1002:15de 
           Device-2: Advanced Micro Devices [AMD] vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.6 
           chip ID: 1022:15e3 
           Sound Server: ALSA v: k4.19.2-1-MANJARO 
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel 
           port: 3300 bus ID: 01:00.0 chip ID: 10ec:8168 
           IF: enp1s0f0 state: up speed: 100 Mbps duplex: full mac: c8:d9:d2:d7:34:23 
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: 3000 bus ID: 02:00.0 chip ID: 8086:24fd 
           IF: wlp2s0 state: down mac: 5e:c0:4e:16:4d:7f 
Drives:    Local Storage: total: 238.47 GiB used: 6.77 GiB (2.8%) 
           ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG30ZMV256G size: 238.47 GiB speed: 15.8 Gb/s lanes: 2 
           serial: 981PCAJBP12P rev: ADHA0101 scheme: GPT 
Partition: ID-1: / size: 233.24 GiB used: 6.73 GiB (2.9%) fs: ext4 dev: /dev/nvme0n1p2 
Sensors:   System Temperatures: cpu: 49.2 C mobo: N/A gpu: amdgpu temp: 49 C 
           Fan Speeds (RPM): N/A 
Info:      Processes: 205 Uptime: 9m Memory: 6.74 GiB used: 986.7 MiB (14.3%) Init: systemd v: 239 Compilers: gcc: 8.2.1 
           Shell: bash v: 4.4.23 running in: xfce4-terminal inxi: 3.0.27 

I’ll try to see if switching to proprietary drivers helps.


#6

They won’t help for a Vega iGPU.

I suspect your hardware is too new for the available drivers. There’s a lot of discussion around these newer APUs:

I also seem to think that HP Envy laptops are generally pretty poor when it comes to supporting Linux…


#7

No AMD drivers in proprietary AFAIK


#8

With these parameters: iommu=soft acpi=strict acpi_rev_override=1 it gets a successful start 1/5 times. (I have absolutely no idea what I’m doing, just searching for stuff and trying out parameters).

If you know of any other things I could try please let me know. I’m out of ideas.


#9

Cutting edge hardware and Linux don’t go hand in hand, there is usually a latency period until kernel and driver support is rolled out by manufacturers.

Good news is as soon as it is released you’ll get it on Arch / Manjaro.

Keep your eyes on Phoronix site, which contains news on new hardware kernel and driver support.


#10

Well then if there’s nothing else I can do then I guess I’ll switch that laptop testing and try out the newer kernels when they arrive, keeping this thread updated with the progress…

(This is both frustrating and exciting at the same time, I guess my body and mind are adapting and reacting to the type of stimulation that only a kernel update could deliver).


#11

i was looking at the specification on the hp site, does it really have an intel 8265 wireless device or have they switched it for a broadcom?

also have you tried noapic


#12

inxi -Fxxx output shows:

I did not really care about the wireless device when buying this so I don’t know if it’s good or not. I had no problems with it while testing yesterday.

noapic does not seem to impact the success rate either.

So, yesterday I tested out some things when I managed to get a successful boot:

  • Sound worked great.
  • Wireless had no problems.
  • A 1 hour video conference was as good as it could be.
  • HD video on youtube displayed wonderfully and with no issues.

Once it’s past systemd’s output everything works properly… at least as far as I’ve seen.


#13

it’s good, setting up and using broadcom adaptors can be a pain in the backside for linux whereas intel usually just works


#14

Can this help?

Its about a 735 GS but might be usefull for the 755 too.


#15

Downgrading the bios to 01.00.04 is exactly what I did. The 735 is pretty much the same laptop as mine, only with a smaller frame. The APU might be Ryzen5/Vega8 instead of Ryzen7/Vega10 and that might be the reason why my setup only works sometimes while that person reported everything working properly for them.

A side-note, HP actually reports they have a new version of their BIOS available (01.04) on their website but the automatic updater does not pick it up, and the system does not detect it as valid when I put it on an USB. I guess they screwed that one up.

I’m hopeful that the next kernel update (4.20) might have some good stuff for me. It’s in RC2 right now.


#16

Reading through the 4.20-rc3 comments here: https://www.phoronix.com/forums/forum/software/general-linux-open-source/1062264-linux-4-20-rc3-kernel-released I’m optimistic about the problems going away soon. I might even try to tweak the PKGBUILD and compile it myself before it’s release to try it out, if I get bored and find myself having to much free time.


#17

This thread might help, as it links to a 4.20-rc2 already built for Manjaro. Kernel building is an acquired taste. But it’s easier to learn kernel building when your system already works well, not when waiting for linux support for your system to mature.


#18

contact them and ask them to send you a direct link to it on their FTP server


#19

Some more things that I’ve tried and failed:

My quest continues…


#20

Hi,

I have a Ryzen 5 on a Lenovo laptop, I had to add this line before going further into the installation/booting process : ivrs_ioapic[32]=00:14.0
Thus I don’t personally know what it does, but it worked. I used the Manjaro 18. With the v17, I had graphic issues that I haven’t experienced yet.


Steven