HP ProBook x360 435 G7

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
vatosflokos
Level 1
Level 1
Posts: 7
Joined: Fri Jul 17, 2020 3:05 am

HP ProBook x360 435 G7

Post by vatosflokos »

Hello!
I want to install Linux Mint on a HP ProBook x360 435 G7 with touchscreen and a pen.
I would love to know if that's possible!
Thank you for all your help!
mr_raider
Level 7
Level 7
Posts: 1888
Joined: Sun Jun 20, 2010 9:50 am
Location: Montreal, QC

Re: HP ProBook x360 435 G7

Post by mr_raider »

Can't speak for the touchscreen or pen, but a lot of us have ryzen 4000 series laptops and we made it work.

You may not be able to boot the installer right away without a nomodeset option. You may need to manually upgrade to the 5.8 series kernel after that.

Plus a recent alsa update yesterday screwed with everyone's audio so that may be something to watch out for.

FYI I have an Acer Swift 3 with a 4700u and everything works, for now.
Image
mwrsa
Level 1
Level 1
Posts: 38
Joined: Sun Jan 19, 2014 3:06 pm

Re: HP ProBook x360 435 G7

Post by mwrsa »

I was able to boot the Mint 20 Mate image right away, but got no more than SVGA graphics, even after installing. Ok, I read that it's a kernel version thing, so I went with the latest 5.8 - but getting an entirely black screen after GRUB.

Next I resolved the "missing firmware" issue by following the steps of this thread (second reply):
https://askubuntu.com/questions/1124253 ... for-amdgpu

Now the "missing firmware" error disappeared, the black screen issue not so much though. Got any ideas please?

Edit: got the 4500U CPU here
mwrsa
Level 1
Level 1
Posts: 38
Joined: Sun Jan 19, 2014 3:06 pm

Re: HP ProBook x360 435 G7

Post by mwrsa »

Only since I wrote the previous post last night there have been two (yes, 2!) kernel updates incoming. None fixed the issue, neither did installing the Ubuntu mainline kernel v.5.9.8 resolve it. Still looking for a solution out there :(
User avatar
SMG
Level 11
Level 11
Posts: 3692
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: HP ProBook x360 435 G7

Post by SMG »

mwrsa wrote:
Mon Nov 16, 2020 5:50 pm
I was able to boot the Mint 20 Mate image right away, but got no more than SVGA graphics, even after installing.
Please give us information about your install by entering this command in a terminal:

Code: Select all

inxi -Fxxxrz
Select </> from the mini toolbar above the textbox where you type your reply and enclose the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.
LM20.1 Cinnamon
mwrsa
Level 1
Level 1
Posts: 38
Joined: Sun Jan 19, 2014 3:06 pm

Re: HP ProBook x360 435 G7

Post by mwrsa »

Sure thing, here we go:

Code: Select all

System:    Kernel: 5.4.0-54-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: MATE 1.24.0 info: mate-panel 
           wm: marco 1.24.0 dm: LightDM 1.30.0 Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Machine:   Type: Convertible System: HP product: HP ProBook x360 435 G7 v: N/A serial: <filter> Chassis: type: 31 
           serial: <filter> 
           Mobo: HP model: 8735 v: KBC Version 09.1F.00 serial: <filter> UEFI: HP v: S80 Ver. 01.01.04 date: 06/30/2020 
Battery:   ID-1: BAT0 charge: 32.0 Wh condition: 41.6/41.6 Wh (100%) volts: 12.2/11.4 model: Hewlett-Packard Primary 
           type: Li-ion serial: <filter> status: Unknown 
           Device-1: hid-0018:04F3:2AD5.0002-battery model: ELAN2513:00 04F3:2AD5 serial: N/A charge: N/A status: N/A 
CPU:       Topology: 6-Core model: AMD Ryzen 5 4500U with Radeon Graphics bits: 64 type: MCP arch: Zen rev: 1 
           L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 28444 
           Speed: 1499 MHz min/max: 1400/2375 MHz boost: enabled Core speeds (MHz): 1: 1402 2: 1397 3: 1397 4: 1399 
           5: 1397 6: 1397 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Renoir vendor: Hewlett-Packard driver: N/A bus ID: 04:00.0 
           chip ID: 1002:1636 
           Display: x11 server: X.Org 1.20.8 driver: ati,fbdev unloaded: modesetting,radeon,vesa compositor: marco 
           v: 1.24.0 resolution: 1024x768~76Hz 
           OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 compat-v: 3.1 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:1637 
           Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor vendor: Hewlett-Packard 
           driver: N/A bus ID: 04:00.5 chip ID: 1022:15e2 
           Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Hewlett-Packard driver: snd_hda_intel 
           v: kernel bus ID: 04:00.6 chip ID: 1022:15e3 
           Sound Server: ALSA v: k5.4.0-54-generic 
Network:   Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter vendor: Hewlett-Packard driver: rtw_pci 
           v: N/A port: 3000 bus ID: 01:00.0 chip ID: 10ec:c822 
           IF: wlp1s0 state: up mac: <filter> 
Drives:    Local Storage: total: 476.94 GiB used: 11.35 GiB (2.4%) 
           ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLQ512HALU-000H1 size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 
           serial: <filter> rev: HPS4NFXV scheme: GPT 
Partition: ID-1: / size: 29.91 GiB used: 9.07 GiB (30.3%) fs: ext4 dev: /dev/nvme0n1p5 
           ID-2: /home size: 284.37 GiB used: 1.10 GiB (0.4%) fs: ext4 dev: /dev/nvme0n1p6 
           ID-3: swap-1 size: 30.52 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p7 
Sensors:   System Temperatures: cpu: 41.8 C mobo: 0.0 C 
           Fan Speeds (RPM): N/A 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb http://ftp.halifax.rwth-aachen.de/linuxmint ulyana main upstream import backport
           2: deb http://ftp.uni-mainz.de/ubuntu focal main restricted universe multiverse
           3: deb http://ftp.uni-mainz.de/ubuntu focal-updates main restricted universe multiverse
           4: deb http://ftp.uni-mainz.de/ubuntu focal-backports main restricted universe multiverse
           5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:      Processes: 217 Uptime: N/A Memory: 15.11 GiB used: 733.0 MiB (4.7%) Init: systemd v: 245 runlevel: 5 Compilers: 
           gcc: 9.3.0 alt: 9 Shell: bash v: 5.0.17 running in: mate-terminal inxi: 3.0.38 
I tried a little more and concluded: Kernel 5.4 boots just fine but can't handle the integrated graphics, so I get SVGA. Kernel 5.8 seems to recognize the chip, but either doesn't know how to handle it or hast some wrong presets that make it blackscreen upon boot. Sadly I can't troubleshoot it if I don't see a thing on the screen :-(

I read somewhere else that the latest release of Fedora is pretty up to date with AMD, so I will probably give this a try next. Mint Mate still stays my preferred distribution, so I really want to get this to work. Maybe Fedora unveils some settings I can transfer over and make it work? Will report back.
User avatar
Larry78723
Level 11
Level 11
Posts: 3526
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: HP ProBook x360 435 G7

Post by Larry78723 »

You're missing the driver for your AMD graphics card. Someone else will have to tell you how to correct the issue.
Image
mwrsa
Level 1
Level 1
Posts: 38
Joined: Sun Jan 19, 2014 3:06 pm

Re: HP ProBook x360 435 G7

Post by mwrsa »

Not entirely sure, Larry, I'd rather think the 5.4 kernel doesn't recognize the integrated card and hence doesn't load the driver. Like I wrote in my previous post - no way of confirming under v.5.8 - unless you folks have some other idea.

Booting in recovery mode doesn't help either bc it doesn't load any graphics drivers that way, meh.
User avatar
Larry78723
Level 11
Level 11
Posts: 3526
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: HP ProBook x360 435 G7

Post by Larry78723 »

I checked the AMD website. Your card needs the amdgpu driver and I don't think it's available in the kernel. See https://www.amd.com/en/support/kb/relea ... inux-20-20
Image
User avatar
SMG
Level 11
Level 11
Posts: 3692
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: HP ProBook x360 435 G7

Post by SMG »

mwrsa wrote:
Fri Nov 20, 2020 10:10 am
Not entirely sure, Larry, I'd rather think the 5.4 kernel doesn't recognize the integrated card and hence doesn't load the driver. Like I wrote in my previous post - no way of confirming under v.5.8 - unless you folks have some other idea.

Booting in recovery mode doesn't help either bc it doesn't load any graphics drivers that way, meh.
Having helped many people on this forum with Renoir graphics, I am entire sure. The 5.4 kernel doesn't load the driver because there is no driver for it in the 5.4 kernel. You need to have at least kernel 5.7.1 installed in order to get the graphics driver for Renoir. That is why it was recommended to install the 5.8 kernel. Because you do not have the driver, you are also missing the AMD renderer and the amdgpu temperature reading in the inxi output you provided.

System: Kernel: 5.4.0-54-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: MATE 1.24.0 info: mate-panel
wm: marco 1.24.0 dm: LightDM 1.30.0 Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir vendor: Hewlett-Packard driver: N/A bus ID: 04:00.0
chip ID: 1002:1636
Display: x11 server: X.Org 1.20.8 driver: ati,fbdev unloaded: modesetting,radeon,vesa compositor: marco
v: 1.24.0 resolution: 1024x768~76Hz
OpenGL: renderer: llvmpipe (LLVM 10.0.0 128 bits) v: 3.3 Mesa 20.0.8 compat-v: 3.1 direct render: Yes
Sensors: System Temperatures: cpu: 41.8 C mobo: 0.0 C [missing reading for amdgpu]
Fan Speeds (RPM): N/A
mwrsa wrote:
Mon Nov 16, 2020 5:50 pm
I was able to boot the Mint 20 Mate image right away, but got no more than SVGA graphics, even after installing. Ok, I read that it's a kernel version thing, so I went with the latest 5.8 - but getting an entirely black screen after GRUB.

Next I resolved the "missing firmware" issue by following the steps of this thread (second reply):
https://askubuntu.com/questions/1124253 ... for-amdgpu

Now the "missing firmware" error disappeared, the black screen issue not so much though. Got any ideas please?
Did you update the firmware with the 5.4 kernel installed or the 5.8 kernel? I do not know if that might be a factor in this situation.

Here is the AMD page for AMD Ryzen™ 5 4500U Drivers & Support. There are no Linux drivers listed which means you need to be using the drivers supplied in the kernel. (The link supplied in the prior post is not the correct one for your apu.)

Regarding the black screen: It sounds like it's time to check the logs to determine what may be happening.

I'm currently helping someone in another thread HP ProBook 455 G7 with integrated AMD Radeon graphics card running in software rendering mode with the same 4500U processor who is having a sometimes it loads/sometimes it does not issue with the graphics driver while using the 5.8 kernel. No conclusion just yet on that thread.
LM20.1 Cinnamon
User avatar
Larry78723
Level 11
Level 11
Posts: 3526
Joined: Wed Jan 09, 2019 7:01 pm
Location: Jasper County, SC, USA

Re: HP ProBook x360 435 G7

Post by Larry78723 »

@SMG - Thanks for jumping in :D
Image
User avatar
SMG
Level 11
Level 11
Posts: 3692
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: HP ProBook x360 435 G7

Post by SMG »

I had a chance to check the log samples in the other thread. It is possible Secure Boot may be interfering.

Do you have secure boot turned on or off? You can check by running the following in a terminal:

Code: Select all

mokutil --sb-state
If it is on, turn it off and see if your computer has issues when booting into the 5.8 kernel.
LM20.1 Cinnamon
mwrsa
Level 1
Level 1
Posts: 38
Joined: Sun Jan 19, 2014 3:06 pm

Re: HP ProBook x360 435 G7

Post by mwrsa »

Please forgive my impatience if it comes through through my writing... Thank you all for contributing and helping my search for a solution! :idea:
  1. Forget about the 5.4 kernel in the inxi output. Like I wrote - I can boot with 5.8 and still get no gfx driver loaded because either I boot recovery mode (no driver loaded) or not (black screen - nothing to see).
  2. Yes, the xserver-xorg-video-amdgpu is installed and really everything is daily updated.
  3. How can I install Mint with kernel 5.8 ootb? I know of no such way. Neither did it help in Ubuntu Mate 20.10 - same black screen with said kernel ootb.
  4. Yes, Secure boot is off. I ran into that suggestion earlier.
  5. What logs do you think I have to look into?
    mintReport lists nothing at all even though I forcefully shutdown the laptop just earlier at the black screen.
    /var/log/Xorg.0.log I will paste just after this listing - could it be that it tries to load the Radeon driver? Looks a tad strange to me... I will crop the output to the lines I mean, the rest contains no [EE] Errors nor anything concerning graphics or AMD.
    Where else could I look?
I feel kinda inclined to blacklist the other AMD drivers. I already checked - AMDGPU is not blacklisted.

Code: Select all

[     4.577] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[     4.581] (--) PCI:*(4@0:0:0) 1002:1636:103c:8735 rev 195, Mem @ 0xd0000000/268435456, 0xe0000000/2097152, 0xe0700000/524288, I/O @ 0x00002000/256, BIOS @ 0x????????/131072
[     4.581] (II) LoadModule: "glx"
[     4.583] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     4.590] (II) Module glx: vendor="X.Org Foundation"
[     4.590] 	compiled for 1.20.8, module version = 1.0.0
[     4.590] 	ABI class: X.Org Server Extension, version 10.0
[     4.590] (==) Matched ati as autoconfigured driver 0
[     4.590] (==) Matched modesetting as autoconfigured driver 1
[     4.590] (==) Matched fbdev as autoconfigured driver 2
[     4.590] (==) Matched vesa as autoconfigured driver 3
[     4.590] (==) Assigned the driver to the xf86ConfigLayout
[     4.590] (II) LoadModule: "ati"
[     4.590] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[     4.590] (II) Module ati: vendor="X.Org Foundation"
[     4.590] 	compiled for 1.20.5, module version = 19.1.0
[     4.590] 	Module class: X.Org Video Driver
[     4.590] 	ABI class: X.Org Video Driver, version 24.0
[     4.687] (II) LoadModule: "radeon"
[     4.687] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[     4.690] (II) Module radeon: vendor="X.Org Foundation"
[     4.690] 	compiled for 1.20.5, module version = 19.1.0
[     4.690] 	Module class: X.Org Video Driver
[     4.690] 	ABI class: X.Org Video Driver, version 24.0
[     4.690] (II) LoadModule: "modesetting"
[     4.690] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     4.691] (II) Module modesetting: vendor="X.Org Foundation"
[     4.691] 	compiled for 1.20.8, module version = 1.20.8
[     4.691] 	Module class: X.Org Video Driver
[     4.691] 	ABI class: X.Org Video Driver, version 24.1
[     4.691] (II) LoadModule: "fbdev"
[     4.691] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[     4.691] (II) Module fbdev: vendor="X.Org Foundation"
[     4.691] 	compiled for 1.20.1, module version = 0.5.0
[     4.691] 	Module class: X.Org Video Driver
[     4.691] 	ABI class: X.Org Video Driver, version 24.0
[     4.691] (II) LoadModule: "vesa"
[     4.691] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     4.692] (II) Module vesa: vendor="X.Org Foundation"
[     4.692] 	compiled for 1.20.4, module version = 2.4.0
[     4.692] 	Module class: X.Org Video Driver
[     4.692] 	ABI class: X.Org Video Driver, version 24.0
[     4.692] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
	ATI Radeon Mobility X600 (M24), ATI FireMV 2400,
	ATI Radeon Mobility X300 (M24), ATI FireGL M24 GL,
	ATI Radeon X600 (RV380), ATI FireGL V3200 (RV380),
	ATI Radeon IGP320 (A3), ATI Radeon IGP330/340/350 (A4),
	ATI Radeon 9500, ATI Radeon 9600TX, ATI FireGL Z1, ATI Radeon 9800SE,
	ATI Radeon 9800, ATI FireGL X2, ATI Radeon 9600, ATI Radeon 9600SE,
	ATI Radeon 9600XT, ATI FireGL T2, ATI Radeon 9650, ATI FireGL RV360,
	ATI Radeon 7000 IGP (A4+), ATI Radeon 8500 AIW,
	ATI Radeon IGP320M (U1), ATI Radeon IGP330M/340M/350M (U2),
	ATI Radeon Mobility 7000 IGP, ATI Radeon 9000/PRO, ATI Radeon 9000,
	ATI Radeon X800 (R420), ATI Radeon X800PRO (R420),
	ATI Radeon X800SE (R420), ATI FireGL X3 (R420),
	ATI Radeon Mobility 9800 (M18), ATI Radeon X800 SE (R420),
	ATI Radeon X800XT (R420), ATI Radeon X800 VE (R420),
	ATI Radeon X850 (R480), ATI Radeon X850 XT (R480),
	ATI Radeon X850 SE (R480), ATI Radeon X850 PRO (R480),
	ATI Radeon X850 XT PE (R480), ATI Radeon Mobility M7,
	ATI Mobility FireGL 7800 M7, ATI Radeon Mobility M6,
	ATI FireGL Mobility 9000 (M9), ATI Radeon Mobility 9000 (M9),
	ATI Radeon 9700 Pro, ATI Radeon 9700/9500Pro, ATI FireGL X1,
	ATI Radeon 9800PRO, ATI Radeon 9800XT,
	ATI Radeon Mobility 9600/9700 (M10/M11),
	ATI Radeon Mobility 9600 (M10), ATI Radeon Mobility 9600 (M11),
	ATI FireGL Mobility T2 (M10), ATI FireGL Mobility T2e (M11),
	ATI Radeon, ATI FireGL 8700/8800, ATI Radeon 8500, ATI Radeon 9100,
	ATI Radeon 7500, ATI Radeon VE/7000, ATI ES1000,
	ATI Radeon Mobility X300 (M22), ATI Radeon Mobility X600 SE (M24C),
	ATI FireGL M22 GL, ATI Radeon X800 (R423), ATI Radeon X800PRO (R423),
	ATI Radeon X800LE (R423), ATI Radeon X800SE (R423),
	ATI Radeon X800 XTP (R430), ATI Radeon X800 XL (R430),
	ATI Radeon X800 SE (R430), ATI Radeon X800 (R430),
	ATI FireGL V7100 (R423), ATI FireGL V5100 (R423),
	ATI FireGL unknown (R423), ATI Mobility FireGL V5000 (M26),
	ATI Mobility Radeon X700 XL (M26), ATI Mobility Radeon X700 (M26),
	ATI Radeon X550XTX, ATI Radeon 9100 IGP (A5),
	ATI Radeon Mobility 9100 IGP (U3), ATI Radeon XPRESS 200,
	ATI Radeon XPRESS 200M, ATI Radeon 9250, ATI Radeon 9200,
	ATI Radeon 9200SE, ATI FireMV 2200, ATI Radeon X300 (RV370),
	ATI Radeon X600 (RV370), ATI Radeon X550 (RV370),
	ATI FireGL V3100 (RV370), ATI FireMV 2200 PCIE (RV370),
	ATI Radeon Mobility 9200 (M9+), ATI Mobility Radeon X800 XT (M28),
	ATI Mobility FireGL V5100 (M28), ATI Mobility Radeon X800 (M28),
	ATI Radeon X850, ATI unknown Radeon / FireGL (R480),
	ATI Radeon X800XT (R423), ATI FireGL V5000 (RV410),
	ATI Radeon X700 XT (RV410), ATI Radeon X700 PRO (RV410),
	ATI Radeon X700 SE (RV410), ATI Radeon X700 (RV410),
	ATI Radeon X1800, ATI Mobility Radeon X1800 XT,
	ATI Mobility Radeon X1800, ATI Mobility FireGL V7200,
	ATI FireGL V7200, ATI FireGL V5300, ATI Mobility FireGL V7100,
	ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
	ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
	ATI Mobility Radeon X1400, ATI Radeon X1550 64-bit,
	ATI Mobility Radeon X1300, ATI Radeon X1300, ATI FireGL V3300,
	ATI FireGL V3350, ATI Mobility Radeon X1450,
	ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
	ATI FireMV 2250, ATI Radeon X1650, ATI Mobility FireGL V5200,
	ATI Mobility Radeon X1600, ATI Radeon X1300 XT/X1600 Pro,
	ATI FireGL V3400, ATI Mobility FireGL V5250,
	ATI Mobility Radeon X1700, ATI Mobility Radeon X1700 XT,
	ATI FireGL V5200, ATI Radeon X2300HD, ATI Mobility Radeon HD 2300,
	ATI Radeon X1950, ATI Radeon X1900, ATI AMD Stream Processor,
	ATI RV560, ATI Mobility Radeon X1900, ATI Radeon X1950 GT, ATI RV570,
	ATI FireGL V7400, ATI Radeon 9100 PRO IGP,
	ATI Radeon Mobility 9200 IGP, ATI Radeon X1200, ATI RS740,
	ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro,
	ATI Radeon HD 2900 GT, ATI FireGL V8650, ATI FireGL V8600,
	ATI FireGL V7600, ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
	ATI Radeon HD 4850 x2, ATI FirePro V8750 (FireGL),
	ATI FirePro V7760 (FireGL), ATI Mobility RADEON HD 4850,
	ATI Mobility RADEON HD 4850 X2, ATI FirePro RV770,
	AMD FireStream 9270, AMD FireStream 9250, ATI FirePro V8700 (FireGL),
	ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
	ATI FirePro M7750, ATI M98, ATI Mobility Radeon HD 4650,
	ATI Radeon RV730 (AGP), ATI Mobility Radeon HD 4670,
	ATI FirePro M5750, ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
	ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
	ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
	ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
	ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
	ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI RV610,
	ATI Radeon HD 2400 XT, ATI Radeon HD 2400 Pro,
	ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000, ATI Radeon HD 2350,
	ATI Mobility Radeon HD 2400 XT, ATI Mobility Radeon HD 2400,
	ATI RADEON E2400, ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
	ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
	ATI Mobility Radeon HD 3850 X2, ATI Mobility Radeon HD 3870,
	ATI Mobility Radeon HD 3870 X2, ATI Radeon HD3870 X2,
	ATI FireGL V7700, ATI Radeon HD3690, AMD Firestream 9170,
	ATI Radeon HD 4550, ATI Radeon RV710, ATI Radeon HD 4350,
	ATI Mobility Radeon 4300 Series, ATI Mobility Radeon 4500 Series,
	ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
	ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
	ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
	ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
	ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
	ATI FireGL V3600, ATI Radeon HD 2600 LE,
	ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
	ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
	ATI Radeon HD 3450, ATI Radeon HD 3430, ATI FirePro V3700,
	ATI FireMV 2450, ATI Radeon HD 3600 Series, ATI Radeon HD 3650 AGP,
	ATI Radeon HD 3600 PRO, ATI Radeon HD 3600 XT,
	ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
	ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
	ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
	ATI Radeon HD 3300 Graphics, ATI Radeon 3000 Graphics, SUMO, SUMO2,
	ATI Radeon HD 4200, ATI Radeon 4100, ATI Mobility Radeon HD 4200,
	ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
	AMD Radeon HD 6310 Graphics, AMD Radeon HD 6250 Graphics,
	AMD Radeon HD 6300 Series Graphics,
	AMD Radeon HD 6200 Series Graphics, PALM, CYPRESS,
	ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
	AMD Firestream 9350, ATI Radeon HD 5800 Series,
	ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
	ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
	ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
	ATI Radeon HD 5670, ATI Radeon HD 5570, ATI Radeon HD 5500 Series,
	REDWOOD, ATI Mobility Radeon Graphics, CEDAR, ATI FirePro 2270,
	ATI Radeon HD 5450, CAYMAN, AMD Radeon HD 6900 Series,
	AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
	AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
	ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
	MULLINS, KAVERI, HAWAII
[     4.693] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     4.693] (II) FBDEV: driver for framebuffer: fbdev
[     4.693] (II) VESA: driver for VESA chipsets: vesa
[     4.694] (EE) open /dev/dri/card0: No such file or directory
[     4.694] (WW) Falling back to old probe method for modesetting
[     4.694] (EE) open /dev/dri/card0: No such file or directory
[     4.694] (II) Loading sub module "fbdevhw"
[     4.694] (II) LoadModule: "fbdevhw"
[     4.694] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     4.694] (II) Module fbdevhw: vendor="X.Org Foundation"
[     4.694] 	compiled for 1.20.8, module version = 0.0.2
[     4.694] 	ABI class: X.Org Video Driver, version 24.1
[     4.694] (**) FBDEV(1): claimed PCI slot 4@0:0:0
[     4.694] (II) FBDEV(1): using default device
[     4.694] (EE) Screen 0 deleted because of no matching config section.
[     4.694] (II) UnloadModule: "modesetting"
[     4.694] (II) FBDEV(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     4.694] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[     4.694] (==) FBDEV(0): RGB weight 888
[     4.694] (==) FBDEV(0): Default visual is TrueColor
[     4.694] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[     4.694] (II) FBDEV(0): hardware: EFI VGA (video memory: 3072kB)
[     4.694] (II) FBDEV(0): checking modes against framebuffer device...
[     4.694] (II) FBDEV(0): checking modes against monitor...
[     4.695] (II) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
[     4.695] (**) FBDEV(0):  Built-in mode "current": 78.7 MHz, 59.9 kHz, 75.7 Hz
[     4.695] (II) FBDEV(0): Modeline "current"x0.0   78.65  1024 1056 1184 1312  768 772 776 792 -hsync -vsync -csync (59.9 kHz b)
[     4.695] (==) FBDEV(0): DPI set to (96, 96)
[     4.695] (II) Loading sub module "fb"
[     4.695] (II) LoadModule: "fb"
[     4.695] (II) Loading /usr/lib/xorg/modules/libfb.so
[     4.695] (II) Module fb: vendor="X.Org Foundation"
[     4.695] 	compiled for 1.20.8, module version = 1.0.0
[     4.695] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     4.695] (**) FBDEV(0): using shadow framebuffer
[     4.695] (II) Loading sub module "shadow"
[     4.695] (II) LoadModule: "shadow"
[     4.695] (II) Loading /usr/lib/xorg/modules/libshadow.so
[     4.696] (II) Module shadow: vendor="X.Org Foundation"
[     4.696] 	compiled for 1.20.8, module version = 1.1.0
[     4.696] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     4.696] (II) UnloadModule: "radeon"
[     4.696] (II) Unloading radeon
[     4.696] (II) UnloadModule: "vesa"
[     4.696] (II) Unloading vesa
[     4.696] (II) FBDEV(0): FBIOBLANK: Invalid argument (Screen blanking not supported by kernel - disabling)
[     4.697] (==) FBDEV(0): Backing store enabled
[     4.698] (==) FBDEV(0): DPMS enabled
[     4.698] (II) Initializing extension Generic Event Extension
[     4.698] (II) Initializing extension SHAPE
[     4.698] (II) Initializing extension MIT-SHM
[     4.698] (II) Initializing extension XInputExtension
[     4.698] (II) Initializing extension XTEST
[     4.698] (II) Initializing extension BIG-REQUESTS
[     4.698] (II) Initializing extension SYNC
[     4.699] (II) Initializing extension XKEYBOARD
[     4.699] (II) Initializing extension XC-MISC
[     4.699] (II) Initializing extension SECURITY
[     4.699] (II) Initializing extension XFIXES
[     4.699] (II) Initializing extension RENDER
[     4.699] (II) Initializing extension RANDR
[     4.699] (II) Initializing extension COMPOSITE
[     4.699] (II) Initializing extension DAMAGE
[     4.699] (II) Initializing extension MIT-SCREEN-SAVER
[     4.699] (II) Initializing extension DOUBLE-BUFFER
[     4.699] (II) Initializing extension RECORD
[     4.699] (II) Initializing extension DPMS
[     4.699] (II) Initializing extension Present
[     4.699] (II) Initializing extension DRI3
[     4.699] (II) Initializing extension X-Resource
[     4.700] (II) Initializing extension XVideo
[     4.700] (II) Initializing extension XVideo-MotionCompensation
[     4.700] (II) Initializing extension SELinux
[     4.700] (II) SELinux: Disabled on system
[     4.700] (II) Initializing extension GLX
[     4.700] (II) AIGLX: Screen 0 is not DRI2 capable
[     4.775] (II) IGLX: Loaded and initialized swrast
[     4.775] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[     4.775] (II) Initializing extension XFree86-VidModeExtension
[     4.775] (II) Initializing extension XFree86-DGA
[     4.775] (II) Initializing extension XFree86-DRI
[     4.775] (II) Initializing extension DRI2
[     4.864] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[     4.864] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     4.864] (II) LoadModule: "libinput"
[     4.864] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[     4.868] (II) Module libinput: vendor="X.Org Foundation"
[     4.868] 	compiled for 1.20.4, module version = 0.29.0
[     4.868] 	Module class: X.Org XInput Driver
[     4.868] 	ABI class: X.Org XInput driver, version 24.1
[     4.868] (II) Using input driver 'libinput' for 'Power Button'
[     4.868] (**) Power Button: always reports core events
[     4.868] (**) Option "Device" "/dev/input/event3"
[     4.868] (**) Option "_source" "server/udev"
[     4.872] (II) event3  - Power Button: is tagged by udev as: Keyboard
[     4.872] (II) event3  - Power Button: device is a keyboard
[     4.872] (II) event3  - Power Button: device removed
[     4.895] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[     4.895] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     4.895] (**) Option "xkb_model" "pc105"
[     4.895] (**) Option "xkb_layout" "de"
[     4.915] (II) event3  - Power Button: is tagged by udev as: Keyboard
[     4.915] (II) event3  - Power Button: device is a keyboard
[     4.916] (II) config/udev: Adding input device Video Bus (/dev/input/event5)
[     4.916] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[     4.916] (II) Using input driver 'libinput' for 'Video Bus'
[     4.916] (**) Video Bus: always reports core events
[     4.916] (**) Option "Device" "/dev/input/event5"
[     4.916] (**) Option "_source" "server/udev"
[     4.917] (II) event5  - Video Bus: is tagged by udev as: Keyboard
[     4.917] (II) event5  - Video Bus: device is a keyboard
[     4.918] (II) event5  - Video Bus: device removed
[     4.927] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0c/LNXVIDEO:00/input/input5/event5"
[     4.927] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[     4.927] (**) Option "xkb_model" "pc105"
[     4.927] (**) Option "xkb_layout" "de"
[     4.929] (II) event5  - Video Bus: is tagged by udev as: Keyboard
[     4.929] (II) event5  - Video Bus: device is a keyboard
[     4.930] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[     4.930] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     4.930] (II) Using input driver 'libinput' for 'Power Button'
[     4.930] (**) Power Button: always reports core events
[     4.930] (**) Option "Device" "/dev/input/event0"
[     4.930] (**) Option "_source" "server/udev"
[     4.931] (II) event0  - Power Button: is tagged by udev as: Keyboard
[     4.931] (II) event0  - Power Button: device is a keyboard
[     4.931] (II) event0  - Power Button: device removed
[     5.659] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0/event0"
[     5.659] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[     5.659] (**) Option "xkb_model" "pc105"
[     5.659] (**) Option "xkb_layout" "de"
[     5.661] (II) event0  - Power Button: is tagged by udev as: Keyboard
[     5.661] (II) event0  - Power Button: device is a keyboard
[     5.661] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
[     5.661] (II) No input driver specified, ignoring this device.
[     5.661] (II) This device may have been added with another device file.
[     5.662] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[     5.662] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[     5.662] (II) Using input driver 'libinput' for 'Sleep Button'
[     5.662] (**) Sleep Button: always reports core events
[     5.662] (**) Option "Device" "/dev/input/event1"
[     5.662] (**) Option "_source" "server/udev"
[     5.663] (II) event1  - Sleep Button: is tagged by udev as: Keyboard
[     5.663] (II) event1  - Sleep Button: device is a keyboard
[     5.663] (II) event1  - Sleep Button: device removed
[     5.688] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1/event1"
[     5.688] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
[     5.688] (**) Option "xkb_model" "pc105"
[     5.688] (**) Option "xkb_layout" "de"
[     5.689] (II) event1  - Sleep Button: is tagged by udev as: Keyboard
[     5.689] (II) event1  - Sleep Button: device is a keyboard
[     5.690] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=3 (/dev/input/event16)
[     5.690] (II) No input driver specified, ignoring this device.
[     5.690] (II) This device may have been added with another device file.
[     5.690] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=7 (/dev/input/event17)
[     5.690] (II) No input driver specified, ignoring this device.
[     5.690] (II) This device may have been added with another device file.
[     5.691] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=8 (/dev/input/event18)
[     5.691] (II) No input driver specified, ignoring this device.
[     5.691] (II) This device may have been added with another device file.
[     5.691] (II) config/udev: Adding input device HD-Audio Generic HDMI/DP,pcm=9 (/dev/input/event19)
[     5.691] (II) No input driver specified, ignoring this device.
[     5.691] (II) This device may have been added with another device file.
EDIT:

From

Code: Select all

journalctl -o short-precise -k -b -2 -p 3
(from the other thread you mentioned) I get the following output:

Code: Select all

-- Logs begin at Mon 2020-11-16 22:01:11 CET, end at Fri 2020-11-20 20:45:17 CET. --
Nov 20 14:19:32.399522 mwwork kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.BUSB.SAT1], AE_NOT_FOUND (20190816/dswload2-162)
Nov 20 14:19:32.399553 mwwork kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190816/psobject-220)
Nov 20 14:19:32.416868 mwwork kernel: Initramfs unpacking failed: Decoding failed
Nov 20 14:19:32.416961 mwwork kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
Nov 20 14:19:32.622190 mwwork kernel: snd_pci_acp3x 0000:04:00.5: Invalid ACP audio mode : 1
EDIT #2:

In the 5.8-kernel modules.alias, the recognized card links to the right driver (imho):

Code: Select all

alias pci:v00001002d00001636sv*sd*bc*sc*i* amdgpu
(see my inxi output:)

Code: Select all

Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Renoir vendor: Hewlett-Packard driver: N/A bus ID: 04:00.0 
           chip ID: 1002:1636
User avatar
SMG
Level 11
Level 11
Posts: 3692
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: HP ProBook x360 435 G7

Post by SMG »

You computer needs a device driver to install before it ever gets to the point of installing display drivers. The N/A in your inxi report is a missing device driver. If there is no device driver then you will end up with software rendering display drivers. X Server handles display drivers, so checking the X Org log file means you are looking at what happens after the problem. The problem is upstream of X Server.

Part of what can be confusing about this is AMD names its device driver amdgpu which is also the name of the display driver, but they are two different things which help generate a display.
mwrsa wrote:
Fri Nov 20, 2020 3:39 pm
EDIT:
From

Code: Select all

journalctl -o short-precise -k -b -2 -p 3
(from the other thread you mentioned) I get the following output:

Code: Select all

-- Logs begin at Mon 2020-11-16 22:01:11 CET, end at Fri 2020-11-20 20:45:17 CET. --
Nov 20 14:19:32.399522 mwwork kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.BUSB.SAT1], AE_NOT_FOUND (20190816/dswload2-162)
Nov 20 14:19:32.399553 mwwork kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20190816/psobject-220)
Nov 20 14:19:32.416868 mwwork kernel: Initramfs unpacking failed: Decoding failed
Nov 20 14:19:32.416961 mwwork kernel: pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
Nov 20 14:19:32.622190 mwwork kernel: snd_pci_acp3x 0000:04:00.5: Invalid ACP audio mode : 1
None of those are errors which would result in a black screen. I think those message are from a recovery mode boot.

If your current boot is a recovery mode boot and your prior boot was a black screen boot then the following will give us the journalctl output of the black screen boot.

Code: Select all

journalctl -b -1 | tee >(gzip --stdout > journalctl_$USER.gz)
This command writes the prior boot system log messages to your screen and the file journalctl_(yourname).gz. The file will be located in your /home/login_name directory.

Attach this file to your next reply, please.

The -b -1 part is for the prior boot. If you have booted twice in a row in recovery mode, then change the 1 to a 2 or to whatever number is appropriate to get the information about a black screen boot.
LM20.1 Cinnamon
mwrsa
Level 1
Level 1
Posts: 38
Joined: Sun Jan 19, 2014 3:06 pm

Re: HP ProBook x360 435 G7

Post by mwrsa »

Why yes, here you go.

As a remark: The previous outputs I considered from kernel v.5.8 were actually from the 5.9.8 mainstream kernel!
This one now, as per last post request, is from the latest v.5.8 provided by the Mint repos. The optical result (black screen) is the same though.
I also just removed the mainstream kernel, as id did not help bus just added to the confusion (at least on my side).

Now, concerning that full journalctl output: I can see a few hiccups I think, but this goes beyond my experience right now.
Attachments
journalctl_whatever.gz
(32.68 KiB) Downloaded 19 times
mwrsa
Level 1
Level 1
Posts: 38
Joined: Sun Jan 19, 2014 3:06 pm

Re: HP ProBook x360 435 G7

Post by mwrsa »

SMG wrote:
Fri Nov 20, 2020 4:53 pm
The N/A in your inxi report is a missing device driver.
Let me guess: That's either because it's a boot on kernel v.5.4 (no driver there) or a recovery boot (no driver loaded) on either of the newer kernels? Like I mentioned before? Could be? Because it's the same inxi output all the time, and I still can't get one from a normal start with the newer kernels because... you know. Black screen. Where's the facepalm smiley? :arrow:

Anyway, another update: Fedora Workstation 33 shows in the same impressive way how black a black screen can be (even though this specific model doesn't have the blackest black of all screens) like all other attempts I made before. I am kinda frustrated now because I read about the great AMD support for before I ordered the device. It's late over here in Germany now anyway, so I am better headed for a slumber before I grow even more grey hair :shock:

Before I do so - another thank you for all the input on where to search and the explanations!
User avatar
SMG
Level 11
Level 11
Posts: 3692
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: HP ProBook x360 435 G7

Post by SMG »

mwrsa wrote:
Fri Nov 20, 2020 7:46 pm
SMG wrote:
Fri Nov 20, 2020 4:53 pm
The N/A in your inxi report is a missing device driver.
Let me guess: That's either because it's a boot on kernel v.5.4 (no driver there) or a recovery boot (no driver loaded) on either of the newer kernels?
That is correct.
mwrsa wrote:
Fri Nov 20, 2020 7:46 pm
...I still can't get one from a normal start with the newer kernels because... you know. Black screen.
Do you have automatic login set up for this install?
mwrsa wrote:
Fri Nov 20, 2020 7:16 pm
This one now, as per last post request, is from the latest v.5.8 provided by the Mint repos. The optical result (black screen) is the same though.
I also just removed the mainstream kernel, as id did not help bus just added to the confusion (at least on my side).

Now, concerning that full journalctl output: I can see a few hiccups I think, but this goes beyond my experience right now.
I made a first pass through the file, and the start up seemed to be going well. In fact, start-up did finish.

Code: Select all

Nov 21 00:03:25 mwwork systemd[1]: Startup finished in 6.324s (firmware) + 11.136s (loader) + 4.303s (kernel) + 1.006s (userspace) = 22.771s.
Along the way Renoir was recognized and the gpu manager successfully started. I was starting to think maybe this just might be an issue with the screen's backlight not initializing. Then seemingly out of the blue a core dump happened and that crashed lightdm which then tripped repeated crashes of X Server. Both lightdm and gpumanager have restart counters, but their limits were not reached, so it appears you may have killed the power to the laptop before the system stopped trying get a display up. Gpumanager was successfully starting, so I'm not quite sure what the issue might be.

I'm off to dream land now. Maybe I'll find some ideas there. :)
LM20.1 Cinnamon
mwrsa
Level 1
Level 1
Posts: 38
Joined: Sun Jan 19, 2014 3:06 pm

Re: HP ProBook x360 435 G7

Post by mwrsa »

SMG wrote:
Fri Nov 20, 2020 11:06 pm
Do you have automatic login set up for this install?
No I don't. Should I (for the sake of trying)? That would mean a fresh install bc I have my /home encrypted. Not too big a task though, it's still an all fresh install anyway (plus the updates and the kernels I tested), so nothing fancy happened yet.

Concerning the looong log, I am a little concerned that the issue may be in a totally different spot. The repeated occurrence of tis part leads me to this thought:

Code: Select all

Nov 21 00:03:26 mwwork systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 00:03:26 mwwork systemd[1]: lightdm.service: Failed with result 'exit-code'.
Nov 21 00:03:26 mwwork systemd-coredump[831]: Process 748 (Xorg) of user 0 dumped core.
                                              
                                              Stack trace of thread 748:
                                              #0  0x00007f79194b818b __GI_raise (libc.so.6 + 0x4618b)
                                              #1  0x00007f7919497859 __GI_abort (libc.so.6 + 0x25859)
                                              #2  0x000055f246f1ad30 OsAbort (Xorg + 0x1c0d30)
                                              #3  0x000055f246f20169 n/a (Xorg + 0x1c6169)
                                              #4  0x000055f246f20fca FatalError (Xorg + 0x1c6fca)
                                              #5  0x000055f246dbb2cd n/a (Xorg + 0x612cd)
                                              #6  0x00007f79194990b3 __libc_start_main (libc.so.6 + 0x270b3)
                                              #7  0x000055f246da4a2e _start (Xorg + 0x4aa2e)
Nov 21 00:03:26 mwwork systemd[1]: systemd-coredump@0-830-0.service: Succeeded.
Nov 21 00:03:26 mwwork systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Nov 21 00:03:26 mwwork systemd[1]: Stopped Light Display Manager.
This happens from line 1873 on a few times. Now again I have no clue what to take from this or where to search on.
User avatar
SMG
Level 11
Level 11
Posts: 3692
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: HP ProBook x360 435 G7

Post by SMG »

mwrsa wrote:
Sat Nov 21, 2020 7:31 am
SMG wrote:
Fri Nov 20, 2020 11:06 pm
Do you have automatic login set up for this install?
No I don't. Should I (for the sake of trying)? That would mean a fresh install bc I have my /home encrypted. Not too big a task though, it's still an all fresh install anyway (plus the updates and the kernels I tested), so nothing fancy happened yet.
I had checked another thread where someone had lightdm issues (which were resolved by the 5.9 kernel which you have already tried) and while investigating that I had come across info indicating people with automatic login were having lightdm crashing issues which is why I asked. I was going to suggest trying an install without the automatic login, but that does not apply here.

I do not have personal experience with encryption, but since you only have /home encrypted, I would not think that is an issue. I had noticed references to encryption in the log, but I will review the log again later today keeping in mind only /home is encrypted.
mwrsa wrote:
Sat Nov 21, 2020 7:31 am
Concerning the looong log, I am a little concerned that the issue may be in a totally different spot. The repeated occurrence of tis part leads me to this thought:

Code: Select all

Nov 21 00:03:26 mwwork systemd[1]: lightdm.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 00:03:26 mwwork systemd[1]: lightdm.service: Failed with result 'exit-code'.
Nov 21 00:03:26 mwwork systemd-coredump[831]: Process 748 (Xorg) of user 0 dumped core.
                                              
                                              Stack trace of thread 748:
                                              #0  0x00007f79194b818b __GI_raise (libc.so.6 + 0x4618b)
                                              #1  0x00007f7919497859 __GI_abort (libc.so.6 + 0x25859)
                                              #2  0x000055f246f1ad30 OsAbort (Xorg + 0x1c0d30)
                                              #3  0x000055f246f20169 n/a (Xorg + 0x1c6169)
                                              #4  0x000055f246f20fca FatalError (Xorg + 0x1c6fca)
                                              #5  0x000055f246dbb2cd n/a (Xorg + 0x612cd)
                                              #6  0x00007f79194990b3 __libc_start_main (libc.so.6 + 0x270b3)
                                              #7  0x000055f246da4a2e _start (Xorg + 0x4aa2e)
Nov 21 00:03:26 mwwork systemd[1]: systemd-coredump@0-830-0.service: Succeeded.
Nov 21 00:03:26 mwwork systemd[1]: lightdm.service: Scheduled restart job, restart counter is at 1.
Nov 21 00:03:26 mwwork systemd[1]: Stopped Light Display Manager.
This happens from line 1873 on a few times. Now again I have no clue what to take from this or where to search on.
There are actually lines about a core dump before the code you listed.

Code: Select all

Nov 21 00:03:25 mwwork systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Nov 21 00:03:25 mwwork systemd[1]: Started Process Core Dump (PID 830/UID 0)
However, I was not able to match that PID to any event, and the PIDs change with each boot, so I'm not sure if there is a way to get that information.

The part of the log you listed is the "lightdm crashes which crashed X Server" that I mentioned in my prior post. X Server usually keeps the current log and one log back. Maybe if you run cat /var/log/Xorg.0.log.old that might be the information about the black screen boot and give some clues. It might not be the black screen boot, but it is worth a try.

I'm also checking to see if there are other logs might provide information which would help.

I have a gut feeling there is some setting in the BIOS/UEFI that is a contributing factor. You have Secure Boot turned off and the log did say it is off, yet there were key checks for MS stuff in the log. I thought that was odd, but you have a very new computer so that may be how it is handled now.
LM20.1 Cinnamon
mwrsa
Level 1
Level 1
Posts: 38
Joined: Sun Jan 19, 2014 3:06 pm

Re: HP ProBook x360 435 G7

Post by mwrsa »

Only after trying Kubuntu to rule out LightDM issues (nope, same black screen) I remembered that Fedora probably doesn't use LightDM ootb either (idk though). Anyway - another thing I tried with no luck so far.

Yet another EDIT:

From all the distros I just tried, Manjaro got the furthest: It apparently displayed the boot messages in the right aspect ratio and size - only to get stuck halfway during boot. Sadly it gets stuck at a different point of the process every time I try to boot it, so diagnosing that would be fun too.

openSUSE Leap still has an old 5.3 kernel in its life image, while its Tumbleweed (rolling release) gives me the finger aka black screen too. *deep sigh*
Post Reply

Return to “Installation & Boot”