You are not logged in.
Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.
There's no "probe with driver amdgpu failed with -22" - was that just because of "nomodeset" at the time?
There're no relevant kernel errors at all, userspace issue ? (dunst dies in glib)
And apparently this is also not related to any firmware.
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st
and
loginctl session-status
If you're running a compositor (picom), kill that.
If you're starting the session w/ xinit/startx, see the last link below.
Offline
Yes, I now think I got confused and the "probe with driver amdgpu failed with -22" was from a boot with "nomodeset". I'm sorry.
I'm not running X or wayland, I'm only booting to tty. That might be the reason for dunst failing. I've collected journals from linux-firmware-20250508.788aadc8-2 and from an up-to-date system with linux-firmware-amdgpu 20250627-1 and they seem identical, so I'm only posting the ones from the updated system.
journalctl -b: http://0x0.st/8091.txt
loginctl session-status: http://0x0.st/809e.txt
Please let me know if this doesn't seem relevant to the linux-firmware update, I'll start a new thread in the newbie corner so as not to pollute this thread any further. Also, thanks for your help!
Offline
There're no obvious errors…
Add
nvidia_drm.modeset=1
to the https://wiki.archlinux.org/title/Kernel_parameters to block the simpledrm device (we just abuse that side effect and don't care that there's no nvidia device) and disable asusd.
Then run and post
for OUT in /sys/class/drm/card*; do echo $OUT; edid-decode $OUT/edid; echo "================="; done
You'll need https://archlinux.org/packages/extra/x86_64/v4l-utils/ - maybe we can just force an output, https://www.kernel.org/doc/Documentation/fb/modedb.rst
I'll start a new thread in the newbie corner so as not to pollute this thread any further.
We'll see and in doubt just request the subthread to be split off.
Offline
Turns out, my laptop screen brightness just somehow got set to zero during or after the update. "nomodeset" prevented applying the zero brightness. And as I never touch the brightness setting and have no shortcuts defined to change it, I had no idea and took me a long time to notice.
Thanks for all your help and sorry for wasting your time.
Offline