Bug#1055644: linux: amd driver not loaded since 6.4.x

[tsubame <gkappa@outlands.top>]

Source: linux
Severity: important

I am using an AMD R5 3600X CPU with an AMD RX6650XT GPU. My DE setup is Plasma
wayland plus sddm, and the latter have been unable to start ever since the 
first version of Debian Linux kernel 6.4.4-1. Ever time I boot with newer 
kernel it just stop at the systemd log of sddm and SimpleMonitor.
I have tried installing linux 6.6 rc from Ubuntu, updating firmwares from 
mainline or Arch Linux, switching the DisplayPort cable to HDMI, switching to 
greetd(which said 0 gpu), tweaking and resetting sddm (and kscreen) config,
but nothing works.
Switching to lxdm + lxqt did yeild some positive result. I ended up in
Plasma X11 with unknown monitor, no HDMI audio output and a fixed 93Hz 
display setting while my monitor is 2650*1440 165Hz.
Here's what I found at Xorg.0.log:

[    32.288] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    32.288] (II) FBDEV: driver for framebuffer: fbdev
[    32.288] (II) VESA: driver for VESA chipsets: vesa
[    32.288] (EE) open /dev/dri/card0: No such file or directory
[    32.288] (WW) Falling back to old probe method for modesetting
[    32.288] (EE) open /dev/dri/card0: No such file or directory
[    32.288] (II) Loading sub module "fbdevhw"
[    32.288] (II) LoadModule: "fbdevhw"         
[    32.288] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    32.288] (II) Module fbdevhw: vendor="X.Org Foundation"
[    32.288]    compiled for 1.21.1.9, module version = 0.0.2
[    32.288]    ABI class: X.Org Video Driver, version 25.2
[    32.288] (EE) Unable to find a valid framebuffer device
[    32.288] (WW) Falling back to old probe method for fbdev
[    32.288] (II) Loading sub module "fbdevhw"
[    32.288] (II) LoadModule: "fbdevhw"
[    32.288] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[    32.288] (II) Module fbdevhw: vendor="X.Org Foundation"
[    32.288]    compiled for 1.21.1.9, module version = 0.0.2
[    32.288]    ABI class: X.Org Video Driver, version 25.2
[    32.288] (II) FBDEV(2): using default device
[    32.288] vesa: Refusing to run, Framebuffer or dri device present
[    32.288] (EE) Screen 0 deleted because of no matching config section.
[    32.288] (II) UnloadModule: "modesetting"
[    32.288] (EE) Screen 0 deleted because of no matching config section.
[    32.288] (II) UnloadModule: "fbdev"
[    32.288] (II) UnloadSubModule: "fbdevhw"

And here is the sddm systemd log:

11月 09 16:39:37 debian systemd[1]: Starting sddm.service - LSB: Start SDDM...
11月 09 16:39:37 debian systemd[1]: Started sddm.service - LSB: Start SDDM.
11月 09 16:41:10 debian systemd[1]: sddm.service: Deactivated successfully.
11月 09 16:41:10 debian systemd[1]: Stopped sddm.service - Simple Desktop Display Manager.

I will provide more debug info if needed.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8), LANGUAGE=zh_CN:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled