Cannot Use Wayland Session After Trying Another Kernel

So I got a wild hair, never a good idea with a working system … you know where this is going.

My base system is up-to-date EndeavourOS, KDE, running wayland.

I’ve been reading about the zen kernel for some time. Decided to try it. Installed linux-zen and linux-zen-headers via yay. Used my grub hooks to regen the grub config. Installed neatly, and with no errors.

Rebooted into the new kernel. Booted fine through grub and into the sddm login screen. Logged in, and it faded to all black. I know it’s running back there, but I can’t get it to display.

Rebooted, rinsed, and repeated on my LTS and Linux kernels. Same new result: black screen.

Then, I decided to log in on x11, which works fine on all kernels.

So, essentially, what I think I’ve done is bork wayland.

I have since removed the zen kernel and headers, reinstalled linux, linux-lts, and all wayland -related packages on my system. Regen’d grub config. Rebooted.

I’m stable on both linux and lts kernels under x11, but can’t get into a wayland session under either kernel after logging in via sddm. Again, x11 works fine.

Looking for ideas/ solutions to fix the wayland issue. I guess I’m still learning after all these years …

TIA!

Barry

First maybe post your hardware output. You can post the url from the command.

inxi -Faz | eos-sendlog

https://0x0.st/8mMn.txt

Thanks, Rick

If you create a new user (even if just temporary), are you able to log into that account with a Wayland session?

Unfortunately, still not.

I personally don’t think the Zen kernel was the cause, but somehow through that process, something has gone awry. Having the issue present also on LTS would confirm that… but, perhaps I’m just repeating what you’ve already concluded.

  • Before installing the Zen kernel, did you perform a full system update? Something within that might have caused the issue.
  • Have you tried running a full system update now? (eg: eos-update --yay)

Sometimes what happens, is something like mesa (OpenGL) gets updated, and that might break some things, for some people.

Thanks for your thoughts.

Yes, I had run a full system update immediately prior to installing the new kernel. As well, yes, I have run a full system update since. No changes.

Looking through old posts on this forum to see if there were similar issues, many involved NVidia cards, which I don’t have. Still looking for clues …

Yeah, and as I was considering causes, this is what my mind kept reaching for, as a NVidia user who’s experienced such issues :sweat_smile:

It’s possible a regression was introduced into the kernels during that update and install. That is, your standard and LTS kernels were updated as you installed Zen, and co-incidentally introduced a regression (which would also be present in Zen).

I’ve not attempted this myself, but you could try installing an older LTS kernel, such as linux-lts66.

I guess there are no newer Bios updates for this HP desktop?

I had a look. The HP site I found only listed an older release than what @bkaplan already has :sweat_smile:

Because of some of the older posts, I looked into that, too, albeit with doubts. It seemed to me that if a kernel successfully loaded on a particular bios config with a known install earlier in the day, a stable bios configuration wouldn’t be the likely cause of failure. Still, looked at it and appreciate your thoughts.