As the title said after I updated my system on newer kernel and reboot my system. My PC won’t boot up it just goes to grub pick the 6.18 kernel and my screen/monitor just goes black then my monitor will said “No Signal”. My PC still running my keyboard and mouse still have the lights on it just my monitor.
Edit: Forgot to include this. I did a rollback for now and hoping this issue will be fix sometime.
@projectmirai39 what graphics setup? Post the output from inxi -GSaz.
Sorry for late reply
here:
System:
Kernel: 6.17.8-1-default arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=(hd3,gpt1)/opensuse-tumbleweed/6.17.8-1-default/linux-a760380af884ec5fcfc52b450402ab4a8f94d348
splash=silent quiet amdgpu.dc=0 mitigations=auto security=selinux
selinux=1 root=/dev/mapper/cr_root
rootflags=subvol=@/.snapshots/93/snapshot
systemd.machine_id=f602e925d710065a0808b285691d357b
Desktop: Xfce v: 4.20.1-UNKNOWN tk: Gtk v: 3.24.51 wm: xfwm4 v: 4.20.0
with: xfce4-panel tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
Distro: openSUSE Tumbleweed 20251119
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Ellesmere [Radeon RX
470/480/570/570X/580/580X/590] vendor: Sapphire Nitro+ driver: amdgpu
v: kernel arch: GCN-4 code: Arctic Islands process: GF 14nm built: 2016-20
pcie: gen: 3 speed: 8 GT/s lanes: 16 ports: active: DVI-D-1,HDMI-A-1
empty: DP-1,DP-2,HDMI-A-2 bus-ID: 06:00.0 chip-ID: 1002:67df
class-ID: 0300 temp: 33.0 C
Display: x11 server: X.org v: 1.21.1.15 compositor: xfwm4 v: 4.20.0
driver: X: loaded: modesetting unloaded: vesa alternate: fbdev dri: radeonsi
gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 3520x1080 s-size: <missing: xdpyinfo>
Monitor-1: DVI-D-1 pos: bottom-l model: BenQ GL2070 serial: <filter>
built: 2017 res: mode: 1600x900 hz: 60 scale: 100% (1) dpi: 94 gamma: 1.2
size: 432x240mm (17.01x9.45") diag: 494mm (19.5") ratio: 16:9 modes:
max: 1600x900 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: primary,top-right
model: AOC 27B1H2 serial: <filter> built: 2023 res: mode: 1920x1080 hz: 60
scale: 100% (1) dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23")
diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400
API: OpenGL v: 4.6 vendor: amd mesa v: 25.3.0 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: AMD Radeon RX 580 Series (radeonsi polaris10
ACO DRM 3.64 6.17.8-1-default) device-ID: 1002:67df memory: 7.81 GiB
unified: no
API: Vulkan v: 1.4.328 layers: 5 device: 0 type: discrete-gpu name: AMD
Radeon RX 580 Series (RADV POLARIS10) driver: mesa radv v: 25.3.0
device-ID: 1002:67df surfaces: N/A device: 1 type: cpu name: llvmpipe
(LLVM 21.1.5 256 bits) driver: mesa llvmpipe v: 25.3.0 (LLVM 21.1.5)
device-ID: 10005:0000 surfaces: N/A
Info: Tools: api: glxinfo,vulkaninfo de: xfce4-display-settings
x11: xprop,xrandr
@projectmirai39 are you using the Packman repo for your Mesa packages? If so I wonder if the recent changes affect your GPU;
* Tue Dec 02 2025 Simon Vogl <simon.vogl@gmx.net>
- Build with VK_AMD_anti_lag vulkan extension support to allow AMD
Anti-Lag to be used on AMD GPUs
- Create new subpackage Mesa-vulkan-anti-lag for this new vulkan
extension
* Tue Nov 18 2025 llyyr <llyyr.public@gmail.com>
- Build with -Ddisplay-info=enabled to allow VK_EXT_hdr_metadata
support for VK_KHR_display
Yup, I’m using packman on my Mesa package. I did change vendor though when I fresh installed Tumbleweed.
So if I’m gonna guess this is just waiting game? Just wait for this issue to got fixed?
And I just noticed that there’s new snapshot released 4hr ago and there’s Mesa change included (again) on that snapshot. I’ll try to update once I got home and let ya know if that snapshot fixed the problem me having.
Update on my issue: After installing the new snapshot the issue still there. Well I guess I need to wait for quite while.
@projectmirai39 well there is the option to switch back to openSUSE packages to see if it duplicates?
If you try to boot and it fails, then when you reboot into the previous kernel. Check the previous boot log with journalctl -b -1 -r this will start at the last boot log entry and work in reverse (-r)
Oh wow, i just had the same exact problem recently, i have an quite old PC made of cheap spare parts and an chinese X79 motherboard + $30 R9 380 4GB GPU, and OpenSUSE TW worked just fine.
And commited the mistake of updating it, now i have dark screen now, the monitor doesn’t say “No Signal” just keeps the black screen on.
Note, i’m not using the Packman repositories or any other repo that replaces system packages at all. 
Now i’m scared to update my daily driver work computer which has far modern hardware.
Is this the output you talking about? And sorry for reply again.
> journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Reached target Exit the Session.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Finished Exit the Session.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Reached target Shutdown.
Dec 09 01:37:24 projectmirai39 systemd[3585]: app.slice: Consumed 4h 49min 1.775s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice User Application Slice.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Closed D-Bus User Message Bus Socket.
Dec 09 01:37:24 projectmirai39 systemd[3585]: session.slice: Consumed 3min 50.030s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice User Core Session Slice.
Dec 09 01:37:24 projectmirai39 systemd[3585]: dbus-broker.service: Consumed 1.039s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped D-Bus User Message Bus.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Create User Files and Directories.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping D-Bus User Message Bus...
Dec 09 01:37:24 projectmirai39 dbus-broker[3618]: Dispatched 45020 messages @ 3(±6)μs / message.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Closed PipeWire Multimedia System Sockets.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Closed PipeWire PulseAudio.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Daily Cleanup of User's Temporary Directories.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Timers.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Sockets.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Paths.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Basic System.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Accessibility services bus.
Dec 09 01:37:24 projectmirai39 systemd[3585]: pipewire.service: Consumed 4.687s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped PipeWire Multimedia Service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping PipeWire Multimedia Service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: wireplumber.service: Consumed 1min 27.157s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Multimedia Service Session Manager.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Multimedia Service Session Manager...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice Slice /app/dbus-:1.2-org.gnome.OnlineAccounts.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice Slice /app/dbus-:1.2-org.gnome.Identity.
Dec 09 01:37:24 projectmirai39 systemd[3585]: tumblerd.service: Consumed 3.352s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Thumbnailing service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Virtual filesystem service - disk device monitor.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Virtual filesystem service.
There’s still alot of lines but I guess this what you only need right?
@projectmirai39 Yes, so keep paging through the output and look for errors…
All the log today and I try to boot the kernel 6.18 before I boot on 6.17
> journalctl -b -1 -r
Hint: You are currently not seeing messages from other users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Reached target Exit the Session.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Finished Exit the Session.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Reached target Shutdown.
Dec 09 01:37:24 projectmirai39 systemd[3585]: app.slice: Consumed 4h 49min 1.775s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice User Application Slice.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Closed D-Bus User Message Bus Socket.
Dec 09 01:37:24 projectmirai39 systemd[3585]: session.slice: Consumed 3min 50.030s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice User Core Session Slice.
Dec 09 01:37:24 projectmirai39 systemd[3585]: dbus-broker.service: Consumed 1.039s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped D-Bus User Message Bus.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Create User Files and Directories.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping D-Bus User Message Bus...
Dec 09 01:37:24 projectmirai39 dbus-broker[3618]: Dispatched 45020 messages @ 3(±6)μs / message.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Closed PipeWire Multimedia System Sockets.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Closed PipeWire PulseAudio.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Daily Cleanup of User's Temporary Directories.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Timers.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Sockets.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Paths.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Basic System.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Accessibility services bus.
Dec 09 01:37:24 projectmirai39 systemd[3585]: pipewire.service: Consumed 4.687s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped PipeWire Multimedia Service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping PipeWire Multimedia Service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: wireplumber.service: Consumed 1min 27.157s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Multimedia Service Session Manager.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Multimedia Service Session Manager...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice Slice /app/dbus-:1.2-org.gnome.OnlineAccounts.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice Slice /app/dbus-:1.2-org.gnome.Identity.
Dec 09 01:37:24 projectmirai39 systemd[3585]: tumblerd.service: Consumed 3.352s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Thumbnailing service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Virtual filesystem service - disk device monitor.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Virtual filesystem service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Portal service (GTK/GNOME implementation).
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Xfce configuration service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped flatpak session helper.
Dec 09 01:37:24 projectmirai39 systemd[3585]: pipewire-pulse.service: Consumed 2min 14.051s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped PipeWire PulseAudio.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Bluetooth OBEX service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Virtual filesystem service - Media Transfer Protocol monitor.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Portal service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped dbus-:1.2-org.gnome.Identity@0.service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped dbus-:1.2-org.gnome.OnlineAccounts@0.service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Virtual filesystem service - GNOME Online Accounts monitor.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped flatpak document portal service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped sandboxed app permission store.
Dec 09 01:37:24 projectmirai39 systemd[3585]: gvfs-metadata.service: Consumed 1.214s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped Virtual filesystem metadata service.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped User preferences database.
Dec 09 01:37:24 projectmirai39 obexd[5330]: Terminating
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Xfce configuration service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping sandboxed app permission store...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping flatpak document portal service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Portal service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Thumbnailing service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping PipeWire PulseAudio...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Bluetooth OBEX service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Virtual filesystem service - disk device monitor...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Virtual filesystem service - Media Transfer Protocol monitor...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Virtual filesystem metadata service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Virtual filesystem service - GNOME Online Accounts monitor...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Virtual filesystem service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping flatpak session helper...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping User preferences database...
Dec 09 01:37:24 projectmirai39 dbus-broker[3717]: Dispatched 16059 messages @ 2(±5)μs / message.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping dbus-:1.2-org.gnome.OnlineAccounts@0.service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping dbus-:1.2-org.gnome.Identity@0.service...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopping Accessibility services bus...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Main User Target.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Stopped target Bluetooth.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice User Background Tasks Slice.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice Slice /app/dbus-:1.2-org.fedoraproject.sealert.
Dec 09 01:37:24 projectmirai39 systemd[3585]: app-dbus\x2d:1.11\x2dorg.a11y.atspi.Registry.slice: Consumed 1.075s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: Removed slice Slice /app/dbus-:1.11-org.a11y.atspi.Registry.
Dec 09 01:37:24 projectmirai39 /usr/libexec/xdg-desktop-portal[5137]: Failed to close session implementation: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.freedesktop.impl.portal.desktop.g>
Dec 09 01:37:24 projectmirai39 systemd[3585]: Activating special unit Exit the Session...
Dec 09 01:37:24 projectmirai39 systemd[3585]: Starting Portal service (GTK/GNOME implementation)...
Dec 09 01:37:24 projectmirai39 systemd[3585]: app-flatpak-org.telegram.desktop-3677283072.scope: Consumed 42.759s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: app-flatpak-net.lutris.Lutris-2926159210.scope: Consumed 1h 37min 47.483s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
Dec 09 01:37:24 projectmirai39 systemd[3585]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
Dec 09 01:37:24 projectmirai39 systemd[3585]: xfce4-notifyd.service: Consumed 1.289s CPU time.
Dec 09 01:37:24 projectmirai39 systemd[3585]: xfce4-notifyd.service: Failed with result 'exit-code'.
Dec 09 01:37:24 projectmirai39 systemd[3585]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
Dec 09 01:37:24 projectmirai39 systemd[3585]: dbus-:1.11-org.a11y.atspi.Registry@0.service: Consumed 1.075s CPU time.
Dec 09 01:37:24 projectmirai39 /usr/libexec/xdg-desktop-portal[5137]: Failed to close session implementation: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Dec 09 01:37:24 projectmirai39 systemd[3585]: dbus-:1.11-org.a11y.atspi.Registry@0.service: Failed with result 'exit-code'.
Dec 09 01:37:24 projectmirai39 systemd[3585]: dbus-:1.11-org.a11y.atspi.Registry@0.service: Main process exited, code=exited, status=1/FAILURE
Dec 09 01:37:24 projectmirai39 at-spi2-registryd[3719]: X connection to :0 broken (explicit kill or server shutdown).
Dec 09 01:36:44 projectmirai39 systemd[3585]: dbus-:1.2-org.fedoraproject.sealert@0.service: Unit process 103388 (glycin-image-rs) remains running after unit stopped.
Dec 09 01:36:44 projectmirai39 systemd[3585]: dbus-:1.2-org.fedoraproject.sealert@0.service: Unit process 103387 (bwrap) remains running after unit stopped.
Dec 09 01:36:41 projectmirai39 setroubleshoot[103350]: gtk_grid_attach: assertion '_gtk_widget_get_parent (child) == NULL' failed
Dec 09 01:36:40 projectmirai39 systemd[3585]: Started dbus-:1.2-org.fedoraproject.sealert@0.service.
Dec 09 01:36:40 projectmirai39 systemd[3585]: Created slice Slice /app/dbus-:1.2-org.fedoraproject.sealert.
Dec 09 01:36:33 projectmirai39 sudo[10303]: pam_unix(sudo:session): session closed for user root
Dec 09 01:28:53 projectmirai39 systemd[3585]: Started Xfce configuration service.
Dec 09 01:28:53 projectmirai39 systemd[3585]: Starting Xfce configuration service...
Dec 09 01:28:53 projectmirai39 systemd[3585]: Started Thumbnailing service.
Dec 09 01:28:53 projectmirai39 systemd[3585]: Starting Thumbnailing service...
Dec 09 01:18:21 projectmirai39 systemd[3585]: Started Thumbnailing service.
Dec 09 01:18:21 projectmirai39 systemd[3585]: Starting Thumbnailing service...
Dec 09 01:17:53 projectmirai39 su[92453]: pam_unix(su:session): session closed for user root
Dec 09 01:12:33 projectmirai39 keepassxc[92744]: YubiKey: PCSC interface is disabled or not initialized.
Dec 09 01:12:33 projectmirai39 keepassxc[92744]: YubiKey: Failed to establish PCSC context.
Dec 09 01:11:32 projectmirai39 su[92453]: pam_unix(su:session): session opened for user root(uid=0) by miku(uid=1000)
Dec 09 01:11:32 projectmirai39 su[92453]: (to root) miku on pts/3
Dec 09 01:07:37 projectmirai39 xfce4-screensaver-dialog[90842]: pam_warn(xfce4-screensaver:account): function=[pam_sm_acct_mgmt] flags=0 service=[xfce4-screensaver] terminal=[:0.0] user=[miku] ruser=[<unknown>] rhost=[<unknown>]
Dec 09 01:07:37 projectmirai39 xfce4-screensaver-dialog[90842]: gkr-pam: unlocked login keyring
Dec 09 01:07:29 projectmirai39 xfce4-screensaver-dialog[90842]: gkr-pam: the password for the login keyring was invalid.
Dec 09 01:07:29 projectmirai39 xfce4-screensaver-dialog[90842]: pam_unix(xfce4-screensaver:auth): authentication failure; logname=miku uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=miku
Dec 09 01:07:29 projectmirai39 unix_chkpwd[91195]: password check failed for user (miku)
Dec 09 01:07:20 projectmirai39 xfce4-screensaver-dialog[90842]: gkr-pam: the password for the login keyring was invalid.
Dec 09 01:07:20 projectmirai39 xfce4-screensaver-dialog[90842]: pam_unix(xfce4-screensaver:auth): authentication failure; logname=miku uid=1000 euid=1000 tty=:0.0 ruser= rhost= user=miku
Dec 09 01:07:20 projectmirai39 unix_chkpwd[91151]: password check failed for user (miku)
Dec 09 01:07:09 projectmirai39 systemd[3585]: Reached target Bluetooth.
Dec 09 01:07:09 projectmirai39 systemd[3585]: Stopped target Bluetooth.
Dec 09 01:07:09 projectmirai39 wireplumber[3747]: spa.audioconvert: 0x55c081a9a6a0: (46 suppressed) out of buffers on port 0 3
Dec 09 01:07:09 projectmirai39 wireplumber[3747]: spa.audioconvert: 0x55c081a9a6a0: (0 suppressed) out of buffers on port 0 3
Dec 09 01:07:09 projectmirai39 wireplumber[3747]: spa.bluez5.sink.media: 0x55c081a79458: connection (/org/bluez/hci0/dev_41_42_CB_FC_F3_63/fd0) terminated unexpectedly
Dec 09 00:27:29 projectmirai39 systemd[3585]: Started Xfce configuration service.
Dec 09 00:27:29 projectmirai39 systemd[3585]: Starting Xfce configuration service...
Dec 09 00:17:50 projectmirai39 systemd[3585]: Started Xfce configuration service.
Dec 09 00:17:50 projectmirai39 systemd[3585]: Starting Xfce configuration service...
Dec 09 00:17:45 projectmirai39 systemd[3585]: app-flatpak-net.lutris.Lutris-4086583284.scope: Consumed 1h 32min 17.389s CPU time.
@malcolmlewis I guess I’m just gonna wait till this got fixed? I’ll try to update again today and hold mesa and see if Mesa is the problem or the kernel 6.18 or maybe I’ll just wait for fixes?
@projectmirai39 Not really sure, I don’t have any AMD hardware as such (laptop running Leap 15.6). @panorain has a similar GPU, maybe he can advise.
Hi, I am away from the desktop machine containing the RX550 at the moment but have with me a HP g6 laptop with AMD Terascale GPU and there are no major display problems with the 6.18.xx kernel.
I have some notes to share with you right now though.
List amdgpu modules: # lsinitrd | grep amdgpu.
Get SystemD Journal amdgpu related entries: # journalctl -b -1 -g amdgpu
Get SystemD Journal of entries containing fail,error,warn: # journalctl -b -1 -g "error\|warn\|fail"
Note, the above is for prior boot i.e. -1. For current boot do not add -1. Also # is for root which is gotten by passing su - in terminal.
Do you mix Packman and openSUSE repos? Please use only one of them.
From Packman you need only VA API (VDPAU) drivers. Or install all Mesa 3D from Packman.
Older snippet of zypper se -si mesa Konsole output of desktop here with RX550 shown below:
$ zypper se -si mesa
S | Name | Type | Version | Arch | Repository
---+---------------------------------+---------+----------------------+--------+-------------------
i | libOSMesa8 | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i | libOSMesa8-32bit | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-32bit | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i | Mesa-demo-egl | package | 9.0.0-3.3 | x86_64 | repo-oss
i | Mesa-demo-x | package | 9.0.0-3.3 | x86_64 | repo-oss
i+ | Mesa-dri | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-dri-32bit | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-gallium | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-gallium-32bit | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-libEGL1 | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-libGL1 | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-libGL1-32bit | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-libglapi0 | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-libglapi0-32bit | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-libva | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-vulkan-device-select | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
i+ | Mesa-vulkan-device-select-32bit | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
@hightower-i5-6600k:~>
Mesa-libva is available from Packman, but all other “libva” - not. Passing zypper se -si libva
$ zypper se -si libva
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+------------------------+---------+----------------------+--------+-------------------
i | libva-drm2 | package | 2.22.0-1.1 | x86_64 | repo-oss
i | libva-drm2-32bit | package | 2.22.0-1.1 | x86_64 | repo-oss
i | libva-glx2 | package | 2.22.0-1.1 | x86_64 | repo-oss
i+ | libva-utils | package | 2.22.0-1.1 | x86_64 | repo-oss
i | libva-wayland2 | package | 2.22.0-1.1 | x86_64 | repo-oss
i | libva-x11-2 | package | 2.22.0-1.1 | x86_64 | repo-oss
i | libva-x11-2-32bit | package | 2.22.0-1.1 | x86_64 | repo-oss
i | libva2 | package | 2.22.0-1.1 | x86_64 | repo-oss
i | libva2-32bit | package | 2.22.0-1.1 | x86_64 | repo-oss
i | libvapoursynth-70 | package | 70-1.1 | x86_64 | repo-oss
i | libvapoursynth-script0 | package | 70-1.1 | x86_64 | repo-oss
i+ | Mesa-libva | package | 24.3.1-1699.401.pm.1 | x86_64 | packman-essentials
I install libva-utils also. A collection of utilities and examples to exercise VA-API | package
# zypper in libva-utils
Pass eglinfo -B in your terminal. Is it installed? If not install this package and switch vendor to specific vendor you choose to use . It is shown in the Mesa list above as package:
Mesa-libEGL1
For the RX550 Vulkan Driver The following packages are installed.
Pass zypper se -si vulkan in your terminal:
$ zypper se -si vulkan
S | Name | Type | Version | Arch | Repository
---+---------------------------------+---------+----------------------+--------+-------------------
i+ | libgstvulkan-1_0-0 | package | 1.24.9-1.1 | x86_64 | repo-oss
i | libvulkan1 | package | 1.3.296-1.1 | x86_64 | repo-oss
i | libvulkan1-32bit | package | 1.3.296-1.1 | x86_64 | repo-oss
i+ | libvulkan_intel | package | 24.3.1-1699.400.pm.1 | x86_64 | packman-essentials
i+ | libvulkan_intel-32bit | package | 24.3.1-1699.400.pm.1 | x86_64 | packman-essentials
i+ | libvulkan_lvp | package | 24.3.1-1699.400.pm.1 | x86_64 | packman-essentials
i+ | libvulkan_radeon | package | 24.3.1-1699.400.pm.1 | x86_64 | packman-essentials
i+ | libvulkan_radeon-32bit | package | 24.3.1-1699.400.pm.1 | x86_64 | packman-essentials
i+ | Mesa-vulkan-device-select | package | 24.3.1-1699.400.pm.1 | x86_64 | packman-essentials
i+ | Mesa-vulkan-device-select-32bit | package | 24.3.1-1699.400.pm.1 | x86_64 | packman-essentials
i | vulkan-tools | package | 1.3.296-1.1 | x86_64 | repo-oss
I see a 4 packages in the list above are coming from repo-oss instead of packman. I have not experienced issues yet and will look when back near the machine.
On the RX550 card here I am using dual monitors such as you. I am using DisplayPort-0 for monitor on the left and Display-Port-2 for monitor on the right. I am not using the center DisplayPort-1 currently. If you have 3 outputs on your card try not using the middle output if possible.
Passing vainfo in your terminal should give you some output similar to the following:
:~> vainfo
libva info: VA-API version 1.16.0
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_16
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.16 (libva 2.15.0)
vainfo: Driver version: Mesa Gallium driver 22.3.5 for AMD Radeon Graphics (raven, LLVM 15.0.7, DRM 3.49, 5.14.21-150500.55.83-default)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
Is OpenGL rendering working? Try passing glxinfo | grep 'OpenGL renderer string' If working you will see some output such as the following:
OpenGL renderer string: AMD Radeon RX 640 (radeonsi, polaris12, LLVM 19.1.6, DRM 3.59, 6.12.8-1-default)
Additional information, vlc-vdpau is not needed for AMD hardware, just adds additional possibilities as shown below the output of zypper se -si vlc.
$ zypper se -si vlc
S | Name | Type | Version | Arch | Repository
---+----------------------+---------+--------------------+--------+-------------------
i+ | libvlc5 | package | 3.0.21-1699.8.pm.7 | x86_64 | packman-essentials
i+ | libvlccore9 | package | 3.0.21-1699.8.pm.7 | x86_64 | packman-essentials
i | phonon-vlc-lang | package | 0.12.0-2.3 | noarch | repo-oss
i+ | phonon-vlc-qt5 | package | 0.12.0-2.3 | x86_64 | repo-oss
i | phonon-vlc-qt6 | package | 0.12.0-2.3 | x86_64 | repo-oss
i+ | vlc | package | 3.0.21-1699.8.pm.7 | x86_64 | packman-essentials
i | vlc-codec-fluidsynth | package | 3.0.21-1699.8.pm.7 | x86_64 | packman-essentials
i+ | vlc-codec-gstreamer | package | 3.0.21-1699.8.pm.7 | x86_64 | packman-essentials
i | vlc-codecs | package | 3.0.21-1699.8.pm.7 | x86_64 | packman-essentials
i+ | vlc-lang | package | 3.0.21-1699.8.pm.7 | noarch | packman-essentials
i+ | vlc-noX | package | 3.0.21-1699.8.pm.7 | x86_64 | packman-essentials
i+ | vlc-qt | package | 3.0.21-1699.8.pm.7 | x86_64 | packman-essentials
i+ | vlc-vdpau | package | 3.0.21-1699.8.pm.7 | x86_64 | packman-essentials
This post I am now linking did help me in setting up the RX550 video card here :< RX550 gpu exhibits blank screen after unlocking - #9 by panorain
You can now compare some of this information with the results on your machine and it will hopefully help.
Edit: Also try switching from X11 to Wayland at your SDDM or Display Manager (password) screen and see if this may help.
Update: Today I tried to hold the Mesa update since I thought this cause of the problem as @malcolmlewis said Mesa added new feature. But after I updated my System with Mesa software update hold. My system still won’t boot. Still the same, the grub will show up > then will show all the kernel I have installed and what kernel will boot into > then will prompt it will boot on 6.18 kernel > hangs a bit > then my monitor will turn off and prompt me with not signal. So the problem is not Mesa but the Kernel 6.18 itself (I guess).
Well there are three possibles, kernel, amdgpu firmware and Mesa/Mesa Drivers…
Update: New snapshot of Tumbleweed with amdgpu firmware update and new Kernel update. After updating my system still the same. I don’t know what I’m gonna do right now. This the first time opensuse gives me back to back bad update (and installations as well). I might do a reinstall today and if the reinstall failed I’ll just go back at Fedora. Better to use a distro you hate that works than distro you love the most that ain’t working.
Have you tried adding kernel parameter of nomodeset and then boot OS?