Hopefully, I’m just simply overlooking something, but after rebooting an HP EliteBook 8560p laptop running GNOME, I open the lid and:
The screen is blank.
The keyboard and touch pad don’t do anything, but the Caps Lock and Num Lock lights work.
External keyboards and mice don’t do anything, but the Caps Lock and Num Lock lights work.
None of the kernel i8042 options fix the problem.
I can log in remotely and work on the laptop with no problem.
Other laptop models (HP ZBook, Dell Precision 3541) with the same logind.conf config options below work as expected.
This started happening some time in the last two weeks.
/etc/systemd/logind.conf:
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
HandleLidSwitchExternalPower=ignore
mrmazda
February 25, 2022, 6:28am
#2
That laptop may have been upgraded to use a kernel that is broken WRT your hardware. There should be an advanced menu option to boot a prior kernel. Try it and let us know what happens. If you are able to reach your Gnome desktop, you may try running sudo zypper up, to install a newer kernel, but I suggest you report back here what happens first, and after running
sudo inxi -U
include input & output from:
sudo inxi -SGMxxyz
mrmazda:
That laptop may have been upgraded to use a kernel that is broken WRT your hardware. There should be an advanced menu option to boot a prior kernel. Try it and let us know what happens. If you are able to reach your Gnome desktop, you may try running sudo zypper up, to install a newer kernel, but I suggest you report back here what happens first, and after running
sudo inxi -U
include input & output from:
sudo inxi -SGMxxyz
The only previous kernel I have is 5.3.18-150300.59.43-default and it does the same thing. I am running Xorg instead of Wayland with WaylandEnable=false
in /etc/gdm/custom.conf. Here’s the output of inxi -SGMxxyz:
**System:**
**Kernel:** 5.3.18-150300.59.43-default x86_64 **bits:** 64 **compiler:** gcc **v:** 7.5.0
**Console:** pty pts/0 **DM:** GDM **Distro:** openSUSE Leap 15.3
**Machine:**
**Type:** Laptop **System:** Hewlett-Packard **product:** HP EliteBook 8560p **v:** A0001C02
**serial:** <filter> **Chassis:****type:** 10 **serial:** <filter>
**Mobo:** Hewlett-Packard **model:** 1618 **v:** KBC Version 97.4B **serial:** <filter>
**BIOS:** Hewlett-Packard **v:** 68SCF Ver. F.26 **date:** 05/31/2012
**Graphics:**
**Device-1:** AMD Seymour [Radeon HD 6400M/7400M Series] **vendor:** Hewlett-Packard
**driver:** N/A **pcie:****speed:** 2.5 GT/s **lanes:** 16 **bus-ID:** 01:00.0
**chip-ID:** 1002:6760
**Device-2:** Sunplus Innovation HP HD Webcam [Fixed] **type:** USB
**driver:** uvcvideo **bus-ID:** 2-1.4:3 **chip-ID:** 1bcf:2805
**Display:****server:** X.org **v:** 1.20.3 **with:** Xwayland **compositor:** gnome-shell
**driver:****X:****loaded:** ati **unloaded:** fbdev,modesetting,radeon,vesa **gpu:** N/A
**tty:** 211x47
**Message:** GL data unavailable in console for root.
mrmazda
February 26, 2022, 3:51am
#4
It’s not clear whether you have installed the latest kernel, which is 5.3.18-150300.59.49.1. If you don’t, get it installed and see if the problem with the radeon kernel driver not loading remains.
Then provide full output of “journalctl -b” after boot.
Finally getting back to this issue. Tried to post yesterday, but it vanished, probably because the journalctl output was too large.
We are on kernel 5.3.18-150300.59.49.1, and the journalctl -b output is at https://www.cs.nmsu.edu/~mleisher/leap-laptop-jcout.txt .
DNS_PROBE_FINISHED_NXDOMAIN
We have https://susepaste.org/ for this.
This looks pretty normal, Xorg is started and GNOME session is started. You are using nomodeset, so I suspect you are at the mercy of your BIOS.
Any reason for “nomodeset”? Did you try without it?
A few weeks ago, X would not start on these HPs unless ‘nomodeset’ was added. One of the updates since then must have fixed whatever that problem was. I removed ‘nomodeset’, and the issue is resolved.
Thanks for the help!