Cannot boot to desktop after (big) April update

I’ve been using Slowroll on multiple machines. My cheap plastic intel laptop accepted the big (2,000+ package) April update (including Plasma 6) with no problem.

However, my AMD A-10 desktop completely broke–and will not reinstall: I could not get to the desktop (Plasma 6) after the upgrade. It goes through the boot process until the mouse pointer appears, then booting stops. Reinstalled from scratch, upgrading breaks it again. Installing Tumbleweed seems to go smoothly, but again, Tumbleweed won’t boot to desktop. I could only install Leap from a live usb, but again it fails if I try to move to either Tumbleweed or Slowroll. It does not appear to be a hardware issue, as I’m typing this using Kubuntu, on the same box.

This is beginning to feel like Fedora felt when they completely dropped all support for AMD APUs older the Ryzen. Please tell me Tumbleweed/Slowroll didn’t just drop all AMD older than Ryzen.

@LanceHaverkamp I’m running Aeon on an A10 CPU… all good there…

System:
  Kernel: 6.8.4-rc1-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
  Desktop: GNOME v: 46.0 tk: GTK v: 3.24.41 wm: gnome-shell dm: GDM
    Distro: openSUSE MicroOS
Machine:
  Type: Laptop System: HP product: HP Pavilion Notebook v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: HP model: 81FE v: 81.21 serial: <superuser required>
    part-nu: W2L75UA#ABA UEFI: American Megatrends v: F.32 date: 04/25/2019
Battery:
  ID-1: BAT0 charge: 17.7 Wh (100.0%) condition: 17.7/17.7 Wh (100.0%)
    volts: 8.5 min: 7.7 model: Hewlett-Packard Primary serial: N/A status: full
CPU:
  Info: quad core model: AMD A10-9600P RADEON R5 10 COMPUTE CORES 4C+6G
    bits: 64 type: MT MCP arch: Excavator rev: 1 cache: L1: 320 KiB L2: 2 MiB
  Speed (MHz): avg: 1243 high: 1391 min/max: 1200/2400 boost: enabled cores:
    1: 1184 2: 1200 3: 1200 4: 1391 bogomips: 19168
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Wani [Radeon R5/R6/R7 Graphics] vendor: Hewlett-Packard
    driver: amdgpu v: kernel arch: GCN-3 ports: active: eDP-1 empty: HDMI-A-1
    bus-ID: 00:01.0 chip-ID: 1002:9874
  Device-2: AMD Topaz XT [Radeon R7 M260/M265 / M340/M360 M440/M445 530/535
    620/625 Mobile] vendor: Hewlett-Packard driver: amdgpu v: kernel
    arch: GCN-3 pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 04:00.0
    chip-ID: 1002:6900 temp: 32.0 C
  Device-3: Chicony HP Wide Vision HD driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-1.3:3 chip-ID: 04f2:b56d
  Display: wayland server: X.org v: 1.21.1.12 with: Xwayland v: 23.2.5
    compositor: gnome-shell driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: ChiMei InnoLux 0x15c6 res: 1366x768 dpi: 101
    diag: 394mm (15.5")
  API: OpenGL v: 4.6 vendor: amd mesa v: 24.0.3 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon R5 Graphics (radeonsi carrizo LLVM
    18.1.2 DRM 3.57 6.8.4-rc1-1-default) device-ID: 1002:9874 display-ID: :0.0
  API: Vulkan v: 1.3.280 surfaces: xcb,xlib,wayland device: 0
    type: integrated-gpu driver: N/A device-ID: 1002:9874 device: 1
    type: discrete-gpu driver: N/A device-ID: 1002:6900
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: AMD Kabini HDMI/DP Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:01.1 chip-ID: 1002:9840
  Device-2: AMD Family 15h Audio vendor: Hewlett-Packard
    driver: snd_hda_intel v: kernel bus-ID: 00:09.2 chip-ID: 1022:157a
  API: ALSA v: k6.8.4-rc1-1-default status: kernel-api
  Server-1: PipeWire v: 1.0.4 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard
    driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000
    bus-ID: 02:00.0 chip-ID: 10ec:8136
  IF: eno1 state: up speed: 100 Mbps duplex: full mac: <filter>
  Device-2: Intel Wireless 3165 driver: iwlwifi v: kernel pcie:
    speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 8086:3165
  IF: wlo1 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-1.4:4 chip-ID: 8087:0a2a
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.2
    lmp-v: 8
Drives:
  Local Storage: total: 111.79 GiB used: 53.74 GiB (48.1%)
  ID-1: /dev/sda vendor: PNY model: 120GB SATA SSD size: 111.79 GiB
    speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 111.29 GiB used: 53.73 GiB (48.3%) fs: btrfs dev: /dev/sda2
  ID-2: /boot/efi size: 511 MiB used: 5.8 MiB (1.1%) fs: vfat dev: /dev/sda1
  ID-3: /home size: 111.29 GiB used: 53.73 GiB (48.3%) fs: btrfs
    dev: /dev/sda2
  ID-4: /opt size: 111.29 GiB used: 53.73 GiB (48.3%) fs: btrfs
    dev: /dev/sda2
  ID-5: /var size: 111.29 GiB used: 53.73 GiB (48.3%) fs: btrfs
    dev: /dev/sda2
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 49.9 C mobo: N/A
  Fan Speeds (rpm): N/A
  GPU: device: amdgpu temp: 33.0 C device: amdgpu temp: 49.0 C
Info:
  Memory: total: 12 GiB note: est. available: 11.15 GiB used: 1.29 GiB (11.6%)
  Processes: 229 Power: uptime: 0h 2m wakeups: 0 Init: systemd v: 255
    default: graphical
  Packages: pm: flatpak pkgs: 33 Compilers: N/A Shell: Bash v: 5.2.26
    running-in: gnome-terminal inxi: 3.3.33

Update: I’m now able to get to the sddm login screen, but the keyboard & mouse buttons don’t work. Searching online turns-up a ton of sddm keyboard issues, but very few fixes. Again, not a hardware problem, as the keyboard works in Kubuntu & leap (as long as I don’t update).

Since Mesa 24 update some AMD GPUs were affected, in my case the system boots ok, but SDDM screen never shows, I only get a black screen with mouse pointer. Slowroll wasn’t affected because it was using Mesa 23, but in the recent big update Mesa 24 was included.

As a workaround there was this suggestion:

There haven’t been a permanent fix so far.

1 Like

I’ve changed the tag on this thread from “tumbleweed” to “slowroll”.

Thanks nrickert, I looked and looked and looked. I couldn’t get the slowroll category to appear, though it now seems to be working again. Though this does affect Tumbleweed too.

1 Like

The second-half of this problem–sddm not letting users enter a password to login is a known upstream issue that was fixed by KDE back in December: https://bugs.kde.org/show_bug.cgi?id=477251

What I don’t understand is how this made it into Tumbleweed at all, let alone Slowroll. Or is this a regression of some kind?

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.