[solved] both wayland and x11 unexpectedly stopped working

slug001 · 2025-02-10 19:05:52

hi everyone. i picked up my laptop today and noticed it won't go past greetd. i opened up a new tty, tried starting hyprland (and later xfce4), and my display goes blank briefly (no backlight), then hyprland crashes. log attached here: https://0x0.st/8ZKu.txt . dmesg shows that nouveau detects my gpu and sets it up correctly, except for one message about failing to create a "ce channel", couldn't find what that means and i don't know if it was there before, because my wise self decided to enable quiet. the laptop worked yesterday. i updated the grub config, but only changed the timeout from 5 to 1. i made the config and forgot about it. turns out for some reason the config in /etc/default/grub was the default config, not mine. i restored a backup that was in that directory, made the config, and now i can't run hyprland. i tried launching xfce4 and it complains about glx initialization failing. the card is an nvidia gt 240m. i'm using linux-lts.

Last edited by slug001 (2025-02-12 15:31:39)

seth · 2025-02-10 21:46:14

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

slug001 · 2025-02-10 23:42:39

journal: https://0x0.st/8Zqx.txt
grub conf: https://0x0.st/8ZqY.txt

seth · 2025-02-11 07:17:06

Feb 11 00:17:04 archlinux kernel: Linux version 6.6.67-1-lts (linux-lts@archlinux) (gcc (GCC) 14.2.1 20240910, GNU ld (GNU Binutils) 2.43.0) #1 SMP PREEMPT_DYNAMIC Thu, 19 Dec 2024 20:39:01 +0000

You're running an older LTS kernel, the newer kernels might already fail you at

Feb 11 00:17:05 archlinux kernel: fbcon: nouveaudrmfb (fb0) is primary device
Feb 11 00:17:05 archlinux kernel: nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device

so stall the update for the moment.

Feb 11 00:17:04 archlinux kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Try to block that, add "nvidia_drm.modeset=1" to the https://wiki.archlinux.org/title/Kernel_parameters (the parameter is irrelevant to nouveau but will block the simpledrm device)

Feb 11 00:17:52 archlinux systemd[1]: Started Session 5 of User greeter.
Feb 11 00:17:52 archlinux systemd[762]: Starting Update XDG user dir configuration...
Feb 11 00:17:52 archlinux xdg-user-dirs-update[772]: Can't create dir //Desktop
Feb 11 00:17:52 archlinux xdg-user-dirs-update[772]: Can't create dir //Downloads
Feb 11 00:17:52 archlinux xdg-user-dirs-update[772]: Can't create dir //Templates
Feb 11 00:17:52 archlinux xdg-user-dirs-update[772]: Can't create dir //Public
Feb 11 00:17:52 archlinux xdg-user-dirs-update[772]: Can't create dir //Documents
Feb 11 00:17:52 archlinux xdg-user-dirs-update[772]: Can't create dir //Music
Feb 11 00:17:52 archlinux xdg-user-dirs-update[772]: Can't create dir //Pictures
Feb 11 00:17:52 archlinux xdg-user-dirs-update[772]: Can't create dir //Videos

looks like a problem w/ the DM.

Other than that there's only the Hyprland abort, do you have an X11 log?
https://wiki.archlinux.org/title/Xorg#General

slug001 · 2025-02-11 08:45:21

i'll send it to you at home, but i looked through it and noticed immediately that x11 couldn't initialize glx. i know about the update unfortunately, this is the newest kernel that worked so i'm using this, do you know why it could be failing?

seth · 2025-02-11 12:16:32

do you know why it could be failing?

[ERR] [AQ] drm: Connector has neither crtc_id nor encoder_id
[ERR] [AQ] drm: Connector has neither crtc_id nor encoder_id
[LOG] [AQ] drm: Mode 0: 1366x768@59.94Hz  (preferred)
[ERR] [AQ] Wayland backend cannot start: wl_display_connect failed (is a wayland compositor running?)
[ERR] [AQ] Requested backend (wayland) could not start, enabling fallbacks
[ERR] [AQ] Implementation wayland failed, erasing.
[ERR] [AQ] Couldn't open a GBM device at fd 27
[ERR] [AQ] Cannot create a GBM Allocator: gbm failed to create a device.
[CRITICAL] Critical error thrown: CBackend::create() failed!

Not from that hyprland abort and the journal doesn't indicate any issues w/ nouveau either.
The xorg log will hopefully tell more - my best guesss rn is the simpledrm device getting in the way.

slug001 · 2025-02-11 14:00:32

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

here's the log. please note i booted with the nvidia drm parameter that you mentioned

edit: when talking about failing, i meant

You're running an older LTS kernel, the newer kernels might already fail you at [...]

Last edited by slug001 (2025-02-11 14:50:43)

seth · 2025-02-12 08:37:58

Looks like a stack corruption in glx, probably broken libGL

pacman -Qikk mesa
ldd /usr/bin/glxinfo

slug001 · 2025-02-12 15:31:18

oh my, thank you so much. i didn't have glxinfo so i decided to install mesa-tools, and i reinstalled mesa just to see if it fixes anything. now it works!!

Arch Linux

#1 2025-02-10 19:05:52

[solved] both wayland and x11 unexpectedly stopped working

#2 2025-02-10 21:46:14

Re: [solved] both wayland and x11 unexpectedly stopped working

#3 2025-02-10 23:42:39

Re: [solved] both wayland and x11 unexpectedly stopped working

#4 2025-02-11 07:17:06

Re: [solved] both wayland and x11 unexpectedly stopped working

#5 2025-02-11 08:45:21

Re: [solved] both wayland and x11 unexpectedly stopped working

#6 2025-02-11 12:16:32

Re: [solved] both wayland and x11 unexpectedly stopped working

#7 2025-02-11 14:00:32

Re: [solved] both wayland and x11 unexpectedly stopped working

#8 2025-02-12 08:37:58

Re: [solved] both wayland and x11 unexpectedly stopped working

#9 2025-02-12 15:31:18

Re: [solved] both wayland and x11 unexpectedly stopped working

Board footer