Sway/hyprland iso graphical problem using ryzen 7 with embedded amd radeon

I have problems with booting from ISO (sway/hyprland and using “nomodeset”) at the following hw:

CPU: 8-core AMD Ryzen 7 5700G with Radeon Graphics (-MT MCP-)
...
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]

from journal:

Mar 31 07:01:27 garuda-sway systemd[1]: Started Process Core Dump (PID 1235/UID 0).
Mar 31 07:01:27 garuda-sway systemd-coredump[1236]: Process 1187 (sway) of user 1000 dumped core.
                                                    
                                                    Stack trace of thread 1187:
                                                    #0  0x00007f16be48e32c n/a (libc.so.6 + 0x8d32c)
                                                    #1  0x00007f16be43d6c8 raise (libc.so.6 + 0x3c6c8)
                                                    #2  0x00007f16be4254b8 abort (libc.so.6 + 0x244b8)
                                                    #3  0x00007f16be4253dc n/a (libc.so.6 + 0x243dc)
                                                    #4  0x00007f16be435d46 __assert_fail (libc.so.6 + 0x34d46)
                                                    #5  0x00007f16be6ad1a6 n/a (libwlroots.so.11 + 0x2b1a6)
                                                    #6  0x00007f16be6b37fd wlr_gles2_renderer_get_egl (libwlroots.so.11 + 0x317fd)
                                                    #7  0x00005bf9f35058e0 n/a (sway + 0x218e0)
                                                    #8  0x00007f16be78e01e wl_signal_emit_mutable (libwayland-server.so.0 + 0xa01e)
                                                    #9  0x00007f16be78e01e wl_signal_emit_mutable (libwayland-server.so.0 + 0xa01e)
                                                    #10 0x00007f16be6ca92b n/a (libwlroots.so.11 + 0x4892b)
                                                    #11 0x00007f16be6baa7c n/a (libwlroots.so.11 + 0x38a7c)
                                                    #12 0x00007f16be6d94b6 n/a (libwlroots.so.11 + 0x574b6)
                                                    #13 0x00005bf9f34f74bf n/a (sway + 0x134bf)
                                                    #14 0x00007f16be426cd0 n/a (libc.so.6 + 0x25cd0)
                                                    #15 0x00007f16be426d8a __libc_start_main (libc.so.6 + 0x25d8a)
                                                    #16 0x00005bf9f34f7fa5 n/a (sway + 0x13fa5)
                                                    
                                                    Stack trace of thread 1224:
                                                    #0  0x00007f16be50788d syscall (libc.so.6 + 0x10688d)
                                                    #1  0x00007f16be9a9337 g_cond_wait (libglib-2.0.so.0 + 0xb3337)
                                                    #2  0x00007f16be91b1b4 n/a (libglib-2.0.so.0 + 0x251b4)
                                                    #3  0x00007f16be91b21c g_async_queue_pop (libglib-2.0.so.0 + 0x2521c)
                                                    #4  0x00007f16bdbb6c48 n/a (libpangoft2-1.0.so.0 + 0x8c48)
                                                    #5  0x00007f16be981a45 n/a (libglib-2.0.so.0 + 0x8ba45)
                                                    #6  0x00007f16be48c55a n/a (libc.so.6 + 0x8b55a)
                                                    #7  0x00007f16be509a3c n/a (libc.so.6 + 0x108a3c)
                                                    ELF object binary architecture: AMD x86-64
Mar 31 07:01:27 garuda-sway systemd[1]: [email protected]: Deactivated successfully.
Mar 31 07:01:27 garuda-sway greetd[1163]: pam_unix(greetd:session): session closed for user garuda
Mar 31 07:01:27 garuda-sway greetd[1240]: config: Config { file: ConfigFile { terminal: ConfigTerminal { vt: None, switch: false }, general: ConfigGeneral { source_profile: true, runfile: "/run/greetd.run" }, default_session: ConfigSession { command: "", user: "" }, initial_session: None }, internal: ConfigInternal { session_worker: 11 } }

Notes:

  1. Everything is fine with KDE ISO (nomodeset)
  2. Everything is fine with fedorasway (nomodeset)
  3. Everything is fine at my second HW with intell i7 CPU and embedded graphics

What is the filename of the ISO?

The newest kernels have moved the video mode setting into the kernel. So all the programming of the hardware specific clock rates and registers on the video card happen in the kernel rather than in the X driver when the X server starts… This makes it possible to have high resolution nice looking splash (boot) screens and flicker free transitions from boot splash to login screen.
Unfortunately, on some cards this doesnt work properly and you end up with a black screen.
Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded.


What’s the problem with not posting garuda-inxi?
It contains additional, useful information about the status of your system.


Info
nomodeset should not have any effect on the proprietary (fglrx/nvidia) drivers. They don’t have this kind of kernel mode setting.
The other way :slight_smile:

Both:

  • garuda-sway-linux-lts-240319.iso
  • garuda-hyprland-linux-zen-240325.iso

Sorry, but I couldn’t resist.

This just reminded me of the Blues Brothers a little too much:

Here is my garuda-inxi output:

System:
  Kernel: 6.6.22-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1 clocksource: tsc
    avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=en_US keytable=us tz=UTC
    misobasedir=garuda root=miso:LABEL=GARUDA_SWAY_SPIZAETUS quiet systemd.show_status=1
    checksum=y systemd.unified_cgroup_hierarchy=1 driver=free nouveau.modeset=1 i915.modeset=1
    radeon.modeset=0 nomodeset
  Console: tty 2 LM: greetd Distro: Garuda base: Arch Linux
Machine:
  Type: Desktop Mobo: ASRock model: B550M Pro4 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends LLC. v: P2.60 date: 02/07/2023
CPU:
  Info: model: AMD Ryzen 7 5700G with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3 gen: 4
    level: v3 note: check built: 2021-22 process: TSMC n7 (7nm) family: 0x19 (25)
    model-id: 0x50 (80) stepping: 0 microcode: 0xA50000D
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache: L1: 512 KiB
    desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB desc: 8x512 KiB L3: 16 MiB desc: 1x16 MiB
  Speed (MHz): avg: 562 high: 2993 min/max: 400/4673 scaling: driver: amd-pstate-epp
    governor: powersave cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400 8: 400 9: 400
    10: 400 11: 400 12: 400 13: 400 14: 400 15: 400 16: 2993 bogomips: 121416
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series] driver: N/A alternate: amdgpu
    arch: GCN-5 code: Vega process: GF 14nm built: 2017-20 pcie: gen: 3 speed: 8 GT/s lanes: 16
    link-max: gen: 4 speed: 16 GT/s bus-ID: 06:00.0 chip-ID: 1002:1638 class-ID: 0300
  Device-2: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.1:3 chip-ID: 046d:0825 class-ID: 0102
  Display: server: Xwayland v: 23.2.4 driver: N/A tty: 102x38
  Monitor-1: Unknown-1 size-res: N/A in console modes: 1024x768
  API: Vulkan v: 1.3.279 layers: 3 device: 0 type: cpu name: llvmpipe (LLVM 17.0.6 256 bits)
    driver: mesa llvmpipe v: 24.0.3-arch1.1 (LLVM 17.0.6) device-ID: 10005:0000 surfaces: N/A
  API: EGL Message: EGL data unavailable in console, eglinfo missing.
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 06:00.1 chip-ID: 1002:1637
    class-ID: 0403
  Device-2: AMD Family 17h/19h HD Audio vendor: ASRock driver: snd_hda_intel v: kernel pcie:
    gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s bus-ID: 06:00.6
    chip-ID: 1022:15e3 class-ID: 0403
  Device-3: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.1:3 chip-ID: 046d:0825 class-ID: 0102
  API: ALSA v: k6.6.22-1-lts status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.0.4 status: off with: 1: pipewire-pulse status: off 2: wireplumber
    status: off 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: ASRock
    driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager,systemd-timesyncd
Drives:
  Local Storage: total: 2.3 TiB used: 0 KiB (0.0%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Seagate model: BarraCuda Q5 ZP500CV30001
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: SU5SS002 temp: 34.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Kingston model: SFYRD2000G size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: EIFK31.6 temp: 42.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 model: USB DISK 3.0 size: 28.91 GiB block-size: physical: 512 B
    logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 tech: N/A
    serial: <filter> fw-rev: PMAP scheme: MBR
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
  Message: No partition data found.
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 62.17 GiB used: 0 KiB (0.0%) priority: 100 comp: zstd
    avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 48.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 64 GiB note: est. available: 62.17 GiB used: 1.6 GiB (2.6%)
  Processes: 250 Power: uptime: 2m states: freeze,mem,disk suspend: deep avail: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 24.84 GiB
    Init: systemd v: 255 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1188 libs: 367 tools: pacseek,paru Compilers: gcc: 13.2.1
    Shell: garuda-inxi default: Bash v: 5.2.26 running-in: tty 2 inxi: 3.3.33
warning: database file for 'garuda' does not exist (use '-Sy' to download)
warning: database file for 'core' does not exist (use '-Sy' to download)
warning: database file for 'extra' does not exist (use '-Sy' to download)
warning: database file for 'community' does not exist (use '-Sy' to download)
warning: database file for 'multilib' does not exist (use '-Sy' to download)
warning: database file for 'chaotic-aur' does not exist (use '-Sy' to download)
Garuda (2.6.23-1):
  System install date:     2024-04-01
  Last full system update: 2024-04-01 ↻
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut
  Windows dual boot:       <superuser required>
  Failed units:            greetd.service 

As I said, there problem is only reproduced for garuda-sway and hyprland editions (I posted a stack-trace of sway crash above). Let me duplicate it here again:

Stack trace of thread 1187:
#0  0x00007f16be48e32c n/a (libc.so.6 + 0x8d32c)
#1  0x00007f16be43d6c8 raise (libc.so.6 + 0x3c6c8)
#2  0x00007f16be4254b8 abort (libc.so.6 + 0x244b8)
#3  0x00007f16be4253dc n/a (libc.so.6 + 0x243dc)
#4  0x00007f16be435d46 __assert_fail (libc.so.6 + 0x34d46)
#5  0x00007f16be6ad1a6 n/a (libwlroots.so.11 + 0x2b1a6)
#6  0x00007f16be6b37fd wlr_gles2_renderer_get_egl (libwlroots.so.11 + 0x317fd)
#7  0x00005bf9f35058e0 n/a (sway + 0x218e0)
#8  0x00007f16be78e01e wl_signal_emit_mutable (libwayland-server.so.0 + 0xa01e)
#9  0x00007f16be78e01e wl_signal_emit_mutable (libwayland-server.so.0 + 0xa01e)
#10 0x00007f16be6ca92b n/a (libwlroots.so.11 + 0x4892b)
#11 0x00007f16be6baa7c n/a (libwlroots.so.11 + 0x38a7c)
#12 0x00007f16be6d94b6 n/a (libwlroots.so.11 + 0x574b6)
#13 0x00005bf9f34f74bf n/a (sway + 0x134bf)
#14 0x00007f16be426cd0 n/a (libc.so.6 + 0x25cd0)
#15 0x00007f16be426d8a __libc_start_main (libc.so.6 + 0x25d8a)
#16 0x00005bf9f34f7fa5 n/a (sway + 0x13fa5)

Stack trace of thread 1224:
#0  0x00007f16be50788d syscall (libc.so.6 + 0x10688d)
#1  0x00007f16be9a9337 g_cond_wait (libglib-2.0.so.0 + 0xb3337)
#2  0x00007f16be91b1b4 n/a (libglib-2.0.so.0 + 0x251b4)
#3  0x00007f16be91b21c g_async_queue_pop (libglib-2.0.so.0 + 0x2521c)
#4  0x00007f16bdbb6c48 n/a (libpangoft2-1.0.so.0 + 0x8c48)
#5  0x00007f16be981a45 n/a (libglib-2.0.so.0 + 0x8ba45)
#6  0x00007f16be48c55a n/a (libc.so.6 + 0x8b55a)
#7  0x00007f16be509a3c n/a (libc.so.6 + 0x108a3c)
ELF object binary architecture: AMD x86-64

The KDE (on wayland) and fedora-sway work fine with my HW.
The question is - is it a sway-specific problem and I need to report it at sway github issues or the problem is pretty garuda-specific and we need to continue investigation here…

BTW: here is a full journal : Garuda's PrivateBin

These ISOs have an issue that affects AMD cpus, see this thread here:

You have a few options:

  1. Use the ISO from the downloads page (this is the easiest option available to you). The ISO builds page you got those files from has all recent ISO builds, including testing ISOs or ISOs that have issues we haven’t addressed yet. Often those ISOs are fine to use, but in your case there is an issue we haven’t addressed.
  2. Fix the issue yourself by chrooting into the system after installation and add this line to /etc/default/grub:
GRUB_EARLY_INITRD_LINUX_STOCK=''

See also this related commit here: fix(boot): don't load microcode via GRUB (ff149a75) · Commits · Garuda Linux 🦅 / Tools / garuda-tools · GitLab

Some folks have also reported success installing amd-ucode-git from a chroot after the installation is complete (see the linked discussion above), although this seems to fix the issue by coincidence instead of actually addressing the problem.

  1. Wait for a new ISO to be released.

I hope that helps, welcome to the community by the way. :wave:

3 Likes

Thank you very much, @BluishHumility .
Let me use the 3-rd option (just wait for the appropriate ISOs with a fix) and read the mentioned long-read thread Call for testers of our new major release builds!

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