MX Linux Forum

Posted: **Wed Dec 20, 2023 9:20 pm**

I am using the integrated GPU on an AMD 7900X with two monitors and MX23. Everything has worked well up until now. I applied several updates a night or two ago and I believe they were mostly (if not entirely) firmware updates. Today on boot up the right (secondary) monitor was inoperative (power save mode), while the primary works fine. Both monitors are detected and show as active in KDE settings. Dmesg is also spammed with "[ 354.796847] [drm:dc_dmub_srv_cmd_run_list [amdgpu]] *ERROR* Error queueing DMUB command: status=2". Also the system has become very "laggy".

Thinking I probably needed a newer kernel for the new firmware, I tried updating kernels from 6.5.0-1 (I am using kernel 6.5 series due to the newness of my hardware which up to now gave noticeable improvements) to the latest 6.5.0-5, but then neither monitor worked(!). Same happens if I try the latest Liquorix (6.6.6-1) and LTS (6.1.0-16) kernels (neither monitor works). But, if I use the original kernel from when I installed (6.1.0-10), both displays work again. So in summary:

6.1.0-10 - OK
6.1.0-16 - Both monitors in power save
6.5.0-1 - Primary monitor works, but secondary is in power save
6.5.0-5 - Both monitors in power save
6.6.6-1 - Both monitors in power save

I've tried systemd and sysv but that doesn't seem to have an effect (other than boot time becomes exasperatingly long with sysv)

Any ideas here? I'm at a loss, and unfortunately this is quite a setback!

QSI:

Code: Select all

System:
  Kernel: 6.5.0-1mx-ahs-amd64 [6.5.3-1~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1mx-ahs-amd64 root=UUID=<filter> ro quiet splash
    init=/lib/systemd/systemd
  Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM
    Distro: MX-23.1_KDE_x64 Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX B650E-F GAMING WIFI v: Rev 1.xx serial: <superuser required>
    UEFI: American Megatrends v: 1654 date: 08/25/2023
CPU:
  Info: model: AMD Ryzen 9 7900X bits: 64 type: MT MCP arch: Zen 4 gen: 5 level: v4 note: check
    built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x61 (97) stepping: 2
    microcode: 0xA601203
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache: L1: 768 KiB desc: d-12x32
    KiB; i-12x32 KiB L2: 12 MiB desc: 12x1024 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 1397 high: 5450 min/max: 400/5733 scaling: driver: amd-pstate-epp
    governor: powersave cores: 1: 400 2: 3814 3: 4258 4: 400 5: 3311 6: 400 7: 400 8: 5450 9: 400
    10: 400 11: 400 12: 400 13: 400 14: 400 15: 400 16: 400 17: 3373 18: 3155 19: 400 20: 400
    21: 400 22: 400 23: 3382 24: 400 bogomips: 225612
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: safe RET, no microcode
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS, IBPB: conditional, STIBP: always-on,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: DP-1,HDMI-A-1 empty: none bus-ID: 0b:00.0 chip-ID: 1002:164e class-ID: 0300
    temp: 37.0 C
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3840x1200 s-dpi: 96 s-size: 1016x317mm (40.00x12.48") s-diag: 1064mm (41.9")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,left model: Dell U2412M serial: <filter>
    built: 2019 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 518x324mm (20.39x12.76")
    diag: 611mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: right model: Dell U2412M serial: <filter> built: 2019
    res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 518x324mm (20.39x12.76") diag: 611mm (24.1")
    ratio: 16:10 modes: max: 1920x1200 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon Graphics (raphael_mendocino LLVM
    15.0.6 DRM 3.54 6.5.0-1mx-ahs-amd64) direct-render: Yes
Audio:
  Device-1: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
    bus-ID: 1-10.3:9 v: kernel pcie: chip-ID: 0d8c:0012 class-ID: 0300 gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-2: C-Media USB Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
  API: ALSA v: k6.5.0-1mx-ahs-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 07:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 8.23 TiB used: 5.34 TiB (64.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Crucial model: CT1000P5PSSD8 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: P7CR403 temp: 31.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Mushkin model: MKNSSDVT2TB-D8 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 3.H.J.CB temp: 31.9 C scheme: GPT
  ID-3: /dev/nvme2n1 maj-min: 259:1 vendor: Kingston model: SKC3000D2048G size: 1.86 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: EIFK31.6 temp: 21.9 C scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 vendor: Toshiba model: HDWE140 size: 3.64 TiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: FP2A
    scheme: GPT
Partition:
  ID-1: / raw-size: 120 GiB size: 117.56 GiB (97.97%) used: 17.59 GiB (15.0%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:6
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:5
  ID-3: /home raw-size: 803.26 GiB size: 789.58 GiB (98.30%) used: 383.84 GiB (48.6%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:8
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 48.6 C mobo: N/A gpu: amdgpu temp: 37.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2644 libs: 1420 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/syncthing.list
    1: deb https://apt.syncthing.net/ syncthing stable
Info:
  Processes: 408 Uptime: 20m wakeups: 0 Memory: 30.49 GiB used: 2.61 GiB (8.6%) Init: systemd
  v: 252 target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Wed Dec 20, 2023 9:29 pm**

For reference - QSI with kernel 6.1.0-10 where both monitors are working normally.

Code: Select all

System:
  Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-10-amd64 root=UUID=<filter> ro quiet splash
    init=/lib/systemd/systemd
  Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM
    Distro: MX-23.1_KDE_x64 Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX B650E-F GAMING WIFI v: Rev 1.xx serial: <superuser required>
    UEFI: American Megatrends v: 1654 date: 08/25/2023
CPU:
  Info: model: AMD Ryzen 9 7900X bits: 64 type: MT MCP arch: Zen 4 gen: 5 level: v4 note: check
    built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25) model-id: 0x61 (97) stepping: 2
    microcode: 0xA601203
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache: L1: 768 KiB desc: d-12x32
    KiB; i-12x32 KiB L2: 12 MiB desc: 12x1024 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 2999 high: 3000 min/max: 3000/5733 boost: enabled scaling:
    driver: acpi-cpufreq governor: ondemand cores: 1: 2999 2: 2999 3: 3000 4: 2998 5: 3000 6: 3000
    7: 3000 8: 3000 9: 2998 10: 3000 11: 3000 12: 3000 13: 3000 14: 3000 15: 2999 16: 3000 17: 3000
    18: 3000 19: 2999 20: 3000 21: 3000 22: 3000 23: 3000 24: 3000 bogomips: 225592
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: retbleed status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: always-on, RSB
    filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Raphael vendor: ASUSTeK driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x
    process: TSMC n7 (7nm) built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: DP-1,HDMI-A-1 empty: none bus-ID: 0b:00.0 chip-ID: 1002:164e class-ID: 0300
    temp: 36.0 C
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3840x1200 s-dpi: 96 s-size: 1016x317mm (40.00x12.48") s-diag: 1064mm (41.9")
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary,left model: Dell U2412M serial: <filter>
    built: 2019 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 518x324mm (20.39x12.76")
    diag: 611mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: right model: Dell U2412M serial: <filter> built: 2019
    res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 518x324mm (20.39x12.76") diag: 611mm (24.1")
    ratio: 16:10 modes: max: 1920x1200 min: 720x400
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: AMD Radeon Graphics (raphael_mendocino LLVM
    15.0.6 DRM 3.49 6.1.0-10-amd64) direct-render: Yes
Audio:
  Device-1: AMD Rembrandt Radeon High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 1-10.3:10 pcie: chip-ID: 0d8c:0012 gen: 4 class-ID: 0300 speed: 16 GT/s
    lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-2: C-Media USB Audio Device type: USB driver: hid-generic,snd-usb-audio,usbhid
  API: ALSA v: k6.1.0-10-amd64 status: kernel-api tools: alsamixer,amixer
  Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel pcie: gen: 2 speed: 5 GT/s
    lanes: 1 port: N/A bus-ID: 07:00.0 chip-ID: 8086:15f3 class-ID: 0200
  IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 8.23 TiB used: 5.34 TiB (64.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:4 vendor: Crucial model: CT1000P5PSSD8 size: 931.51 GiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: P7CR403 temp: 36.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:1 vendor: Mushkin model: MKNSSDVT2TB-D8 size: 1.82 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: 3.H.J.CB temp: 33.9 C scheme: GPT
  ID-3: /dev/nvme2n1 maj-min: 259:0 vendor: Kingston model: SKC3000D2048G size: 1.86 TiB
    block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter>
    rev: EIFK31.6 temp: 22.9 C scheme: GPT
  ID-4: /dev/sda maj-min: 8:0 vendor: Toshiba model: HDWE140 size: 3.64 TiB block-size:
    physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: FP2A
    scheme: GPT
Partition:
  ID-1: / raw-size: 120 GiB size: 117.56 GiB (97.97%) used: 17.59 GiB (15.0%) fs: ext4
    dev: /dev/nvme0n1p2 maj-min: 259:6
  ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
    dev: /dev/nvme0n1p1 maj-min: 259:5
  ID-3: /home raw-size: 803.26 GiB size: 789.58 GiB (98.30%) used: 383.83 GiB (48.6%) fs: ext4
    dev: /dev/nvme0n1p4 maj-min: 259:8
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
  System Temperatures: cpu: 43.8 C mobo: N/A gpu: amdgpu temp: 36.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: pm: dpkg pkgs: 2644 libs: 1420 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
    pm: flatpak pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/syncthing.list
    1: deb https://apt.syncthing.net/ syncthing stable
Info:
  Processes: 427 Uptime: 1m wakeups: 0 Memory: 30.5 GiB used: 2.3 GiB (7.5%) Init: systemd v: 252
  target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
  Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI

Posted: **Wed Dec 20, 2023 9:52 pm**

There's ample evidence from my own experiences as well as those of @CharlesV and others here that the Ryzen CPUs and chipsets just perform better with a Liquorix kernel. I think that you should use MXPI to install the Liquorix 6.6.6-1 kernel, then use Boot Options to make it the default and then reboot.

Posted: **Wed Dec 20, 2023 10:07 pm**

Code: Select all

Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland

Does the same thing happen when using x11 instead?

Posted: **Wed Dec 20, 2023 10:38 pm**

j2mcgreg wrote: Wed Dec 20, 2023 9:52 pm I think that you should use MXPI to install the Liquorix 6.6.6-1 kernel, then use Boot Options to make it the default and then reboot.

You missed where I said I tried that and it made things worse (both monitors are out).

siamhie wrote: Wed Dec 20, 2023 10:07 pm Does the same thing happen when using x11 instead?

How do I switch?

Posted: **Wed Dec 20, 2023 11:44 pm**

texneus wrote: Wed Dec 20, 2023 10:38 pm

siamhie wrote: Wed Dec 20, 2023 10:07 pm Does the same thing happen when using x11 instead?
How do I switch?

I believe you log out of the desktop and switch display servers at the top right corner?

Posted: **Thu Dec 21, 2023 12:41 am**

@texneus Never mind checking display servers. I loaded up my MX-23 KDE live ISO and it reported the same thing.

Code: Select all

Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland

Found an article on Phoronix that might help you out. Your good for the mesa package and kernel.
I think you might also need the linux-firmware.git package. Read the article over.

For the iGPU, you need to be running Mesa 22.2+, Linux 5.18+, and using Linux-Firmware.Git from the past few weeks.
The necessary AMDGPU firmware was only recently published and without that you will have just a black screen at boot
if using the iGPU. When fetching that new firmware, the iGPU was running fine.

https://www.phoronix.com/review/ryzen-7 ... ies-gaming

Posted: **Thu Dec 21, 2023 11:15 am**

I have my doubts on this. I'm familiar with that article as I referenced it trying to get Zen 4 graphics working under MX21. Note the article is over a year old (as are the drivers mentioned) and surely doesnt apply to Debian 12 or MX23 (surely these are considered "modern" distros that now include the necessary firmware - perhaps somebody could verify). This is a NEW problem that just started with updates earlier this week who's severity depends on the kernel version. MX23 has always run my Zen 4 GPU properly since the early betas, until now. That said, I do suspect buggy firmware as there were a large quantity of firmware updates applied.

It will be later tonight before I can play more with this but please keep the ideas coming.

Question for the masses - is no one else affected? Or am I the only MX user actually using a Zen 4 GPU?

Posted: **Thu Dec 21, 2023 11:24 am**

A quick search around and I see a few zen 's in use in topics, but I dont see a Zen 4 in use.

You might check out what happened in the firmware updates, that might hold a clue. Also, you could try walking back in the firmware updates. All are here:
https://git.kernel.org/pub/scm/linux/ke ... mware.git/

I have jumped several updates forward or back (usually forward) and resolved some issues.

And if you have TimeShift, working regularly, it might be time to save what is new and then do a restore to before you updated ? (I suggest doing a timeshift create *first* right before you restore, so you have what is new / latest or can roll back to now if needed.

Posted: **Thu Dec 21, 2023 11:35 am**

... But ... -10 still works fine with the same (updated) firmware.

You can do this at least for now: Make 6.1.0-10 the default with "MX Boot Options" - "Boot to" . Then if you like you can also remove unnecessary kernels simply with "MX Cleanup".

If you like only (if you're using Timeshift you can take a snapshot beforehand, or you can run MX Snapshot) and for even most recent ones:

Ctrl+Alt+T

Code: Select all

wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20231211.tar.gz ; tar -xf linux-firmware-20231211.tar.gz ; cd linux-firmware-20231211 ; sudo cp -R * /lib/firmware/ ; sudo update-initramfs -uk all

Reboot

Posted: **Thu Dec 21, 2023 12:33 pm**

texneus wrote: Thu Dec 21, 2023 11:15 am Question for the masses - is no one else affected? Or am I the only MX user actually using a Zen 4 GPU?

Zen 4 is still (practically) new. X670 chipset boards released in Sep 2022 with the B650 chipset boards released in Oct 2022.

Do you have a discrete graphics card to test with?

There's also a newer BIOS update available for that motherboard. Version 1807 https://rog.asus.com/us/motherboards/ro ... desk_bios/

Posted: **Thu Dec 21, 2023 9:24 pm**

Good news everyone! It was indeed the firmware (so a tip of the hat to @siamhie) and the instructions provided by @Charlie Brown to download and install the latest available were spot on. Doing some more digging today I found that despite being a new update, the latest firmware in the MX Repos are 6 months old (dated 20230625 vs the latest 20231211) - presumably that's driven by Debian, but I wrongly assumed repos would have the latest. What is interesting is looking at the linux-firmware log https://git.kernel.org/pub/scm/linux/ke ... e.git/log/ I can see "Partially revert "amdgpu: DMCUB updates for DCN 3.1.4 and 3.1.5" on July 7, which might be related to the Dmesg errors I saw. There are several amdgpu updates since, probably mostly routine stuff...but nice to be at the latest.

I will take the advice of @j2mcgreg and migrate to the Liquorix 6.6 kernel - I had been patiently been waiting for an official Debian one but after looking into that I learned there won't be one (which seems odd as it's an LTS kernel. Oh well).

Posted: **Thu Dec 21, 2023 10:37 pm**

Glad it worked out for you @texneus. Now we know that users on the Zen4 iGPU will need the latest firmware installed. I'm sure those with discrete cards won't.

Posted: **Thu Dec 21, 2023 11:24 pm**

siamhie wrote: Thu Dec 21, 2023 10:37 pm ...users on the Zen4 iGPU will need the latest firmware installed. I'm sure those with discrete cards won't.

Well, assuming I'm not a fluke all we can really say is they will need something other than 20230625 currently provided by MX23. Whatever prior version installed before was OK. It would be a wild guess as to where the problem actually came and left, but so far the Dec 11 2023 firmware seems to work well with everything else of mine too, so its got that going for it. I never thought to check but presumably software rendering with nomodset will work even with the gimped firmware. That may be necessary to at least get functioning displays so newer firmware can be installed. That or an old kernel.

I can't speak about a discrete card as absolutely nothing I do would ever benefit from one, so I don't have one to try. If the Zen 4/RDNA2 architecture appears on any graphics cards it seems to me that discrete cards might be affected.

Posted: **Fri Dec 22, 2023 3:15 am**

I will take a look at again porting over Ubuntu's linux-firmware package like a few times before, since they do regular updates, unlike Rip van Winkeldebian...

Debian's 6.6 kernel is still in their Experimental section, recently updated to 6.6.7. The build configuration in /debian, compared what I have to to do port over Liquorix, is considerably more complex, and they are also making some significant changes in there with 6.6. I have been spending the last several hours poking around in there, and may have some MX builds later tonight.

Posted: **Fri Dec 22, 2023 10:04 am**

@texneus So glad to hear it worked, and thank you for the feedback :)

Posted: **Fri Dec 22, 2023 11:12 am**

texneus wrote: Thu Dec 21, 2023 11:24 pm
siamhie wrote: Thu Dec 21, 2023 10:37 pm ...users on the Zen4 iGPU will need the latest firmware installed. I'm sure those with discrete cards won't.
I can't speak about a discrete card as absolutely nothing I do would ever benefit from one, so I don't have one to try. If the Zen 4/RDNA2 architecture appears on any graphics cards it seems to me that discrete cards might be affected.

My train of thought is that you were having problems getting two monitors to work with your motherboards video outputs (DP+HDMI) using the newer kernels for the Raphael chipset.
We know those who run the Radeon 7900XT cards aren't having issues with the latest kernels. It's possible AMD made changes after the 6.1 kernel release which requires firmware newer than June.

Posted: **Sat Dec 23, 2023 12:34 am**

Ubuntu has switched to compressing all their firmwire files to zstd archives. The kernel added a configuration option to enable support for this in 5.19, and I assumed that at least the Liquorix kernels supported this, but after I ported over their latest linux-firmware and installed it, I lost my GUI (amd iGPU). Luckily, I was able to bring up a virtual terminal session and just use apt to reinstall firmware-amd-graphics and firmware-iwlwifi from the debs in my apt cache.

Maybe some one could look at their copy-firmware.sh script and disable that zstd stuff, so that we just get the original firmware files like their Creator intended.

Posted: **Mon Dec 25, 2023 9:21 am**

I've only quickly skimmed through this thread, and I've only been running Linux for a short while so I'm still a novice, but I thought I'd add a quick post to share my display issue. I have a Ryzen 7900X CPU and I'm just using the integrated graphics. I installed the “ahs” version of MX 23 Xfce a while back.

The PC's display port is connected to a gizmo that's converting the signal to analogue, and from there it's connected to a CRT.
The HDMI output is connected to an LCD.

The MX updater installed a bunch of updates today. I didn't pay much attention though and just let it run.

After a restart (I gave the BIOS an update for Xmas) the CRT was still working but not the LCD. According to the GUI for configuring displays, the LCD was connected but when I switched it on manually it complained about a lack of signal .
Not to worry. I saved a snapshot of my setup a few weeks ago so it didn't take long to run the Live USB Maker and restore it, and both monitors worked again.... until I let the MX updater do it's thing.

I installed MX 23.3 Xfce ahs from scratch, but because it's Xmas and I've been pickling my brain all day, and because I've been somewhat distracted, I can't remember if the LCD monitor failed to work straight away or if I had to run the updater again to stop it working. I think it was the latter.
I tried the KDE version of MX 23.3 as well. The displays definitely worked normally after it was installed but once again the LCD monitor stopped working after running the updater.
At the moment I have the non-ahs Xfce flavour of MX 23.3 installed, and I was able to run the updater without it causing a display problem.

I assume the issue is fixable as the thread's marked solved. I'll have to try reading through it again when the remaining Xmas cheer has worn off.

Posted: **Mon Dec 25, 2023 9:23 am**

If you cannot get it solved, please start a thread of your own and include the Quick System Info in it, thanks. :)

MX Linux Forum

Major video problem after firmware updates

Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates [Solved]

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates

Re: Major video problem after firmware updates