[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: X unstable / integrated graphics chipset




Hello,


(A solution seems to have been found!)

I would suggest to use a newer kernel with the AMD Ryzen 8700G, maybe
from testing (6.16.12) or even from sid (8.17.8). Since the kernel
packages are nearly independent of any other package, it would not be
much trouble.

Very nice idea. I installed the 6.16 kernel from testing and saw a lot of improvement. Although in the end, X finally crashed.

And also use the according firmware-amd-graphics package.

I did not manage to install firmware-amd-graphics from testing though:

~> apt-cache search firmware-amd-graphics
firmware-amd-graphics - Binary firmware for AMD/ATI graphics and NPU chips

~> sudo apt install firmware-amd-graphics/trixie-backports
Package firmware-amd-graphics is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Could you point me to the correct syntax?

Also, I did not find out how to install the kernel from sid (if that's a
good idea). How can I do that?

Please show I/O from:
	lsmod | sort | grep -E 'video|radeon|amdgpu'

amdgpu              14450688  2
amdxcp                 12288  1 amdgpu
crc16                  12288  3 bluetooth,amdgpu,ext4
drm                   774144  12 gpu_sched,drm_kms_helper,drm_exec,drm_suballoc_helper,drm_display_helper,drm_buddy,amdgpu,drm_ttm_helper,ttm,amdxcp
drm_buddy              24576  1 amdgpu
drm_display_helper    274432  1 amdgpu
drm_exec               12288  1 amdgpu
drm_kms_helper        253952  3 drm_display_helper,amdgpu,drm_ttm_helper
drm_suballoc_helper    12288  1 amdgpu
drm_ttm_helper         16384  2 amdgpu
gpu_sched              65536  1 amdgpu
i2c_algo_bit           16384  1 amdgpu
ttm                   106496  2 amdgpu,drm_ttm_helper
video                  81920  1 amdgpu
wmi                    28672  3 video,gigabyte_wmi,wmi_bmof

There have been some modifications since changing kernels:

amdgpu              19292160  0
amdxcp                 12288  1 amdgpu
cec                    77824  2 drm_display_helper,amdgpu
crc16                  12288  3 bluetooth,amdgpu,ext4
drm                   835584  13 gpu_sched,drm_panel_backlight_quirks,drm_kms_helper,drm_exec,drm_suballoc_helper,drm_display_helper,drm_buddy,amdgpu,drm_ttm_helper,drm_client_lib,ttm,amdxcp
drm_buddy              32768  1 amdgpu
drm_client_lib         12288  1 amdgpu
drm_display_helper    299008  1 amdgpu
drm_exec               12288  1 amdgpu
drm_kms_helper        258048  4 drm_display_helper,amdgpu,drm_ttm_helper,drm_client_lib
drm_panel_backlight_quirks    12288  1 amdgpu
drm_suballoc_helper    20480  1 amdgpu
drm_ttm_helper         16384  2 amdgpu
gpu_sched              65536  1 amdgpu
i2c_algo_bit           16384  1 amdgpu
ttm                   135168  2 amdgpu,drm_ttm_helper
video                  81920  1 amdgpu
wmi                    28672  3 video,gigabyte_wmi,wmi_bmof

	ls -1 /sys/class/drm	# One, not L

card0@
card0-DP-1@
card0-DP-2@
card0-DP-3@
card0-DP-4@
card0-DP-5@
card0-DP-6@
card0-HDMI-A-1@
card0-HDMI-A-2@
card0-Writeback-1@
renderD128@
version

No changes here.

	inxi -GSaz --za

System:
   Kernel: 6.12.48+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
     clocksource: tsc avail: hpet,acpi_pm
     parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.48+deb13-amd64
     root=UUID=<filter> ro quiet
   Desktop: FVWM2 v: 2.7.0 tools: xscreensaver,xscreensaver-systemd
     dm: startx Distro: Debian GNU/Linux 13 (trixie)
Graphics:
   Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: Gigabyte
     driver: amdgpu v: kernel arch: RDNA-3 code: Phoenix process: TSMC n4 (4nm)
     built: 2023+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1
     empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, HDMI-A-2, Writeback-1
     bus-ID: 78:00.0 chip-ID: 1002:15bf class-ID: 0300 temp: 28.0 C
   Display: unspecified server: X.Org v: 21.1.16 driver: X: loaded: amdgpu
     unloaded: fbdev,modesetting,radeon,vesa dri: swrast gpu: amdgpu
     display-ID: localhost:10.0 screens: 1
   Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46")
     s-diag: 692mm (27.26")
   Monitor-1: HDMI-A-1 mapped: DP-0 model: Idek Iiyama PL2283H
     serial: <filter> built: 2016 res: mode: 2560x1440 hz: 60 scale: 100% (1)
     dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 576mm (22.7")
     ratio: 15:9 modes: max: 1920x1080 min: 720x400
   API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
     device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
     drv: swrast inactive: wayland
   API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.0.7-2 glx-v: 1.4
     direct-render: yes renderer: llvmpipe (LLVM 19.1.7 256 bits)
     device-ID: ffffffff:ffffffff memory: 29.76 GiB unified: yes
   Info: Tools: api: eglinfo,glxinfo gpu: radeontop x11: xdriinfo, xdpyinfo,
     xprop, xrandr

The changes here seem minor, unfortunately.

System:
  Kernel: 6.16.3+deb13-amd64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.16.3+deb13-amd64
    root=UUID=<filter> ro quiet modprobe.blacklist=radeon
  Desktop: N/A wm: FVWM v: 2.7.0 dm: startx Distro: Debian GNU/Linux 13
    (trixie)
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: Gigabyte
    driver: amdgpu v: kernel arch: RDNA-3 code: Phoenix process: TSMC n4 (4nm)
    built: 2023+ pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: HDMI-A-1
    empty: DP-1, DP-2, DP-3, DP-4, DP-5, DP-6, HDMI-A-2, Writeback-1
    bus-ID: 78:00.0 chip-ID: 1002:15bf class-ID: 0300 temp: 28.0 C
  Display: server: X.Org v: 21.1.16 driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa dri: swrast gpu: amdgpu
    display-ID: localhost:10.0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x342mm (23.70x13.46")
    s-diag: 692mm (27.26")
  Monitor-1: HDMI-A-1 mapped: DP-0 model: Idek Iiyama PL2283H
    serial: <filter> built: 2016 res: mode: 2560x1440 hz: 60 scale: 100% (1)
    dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 576mm (22.7")
    ratio: 15:9 modes: max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
    drv: swrast inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.0.7-2 glx-v: 1.4
    direct-render: yes renderer: llvmpipe (LLVM 19.1.7 256 bits)
    device-ID: ffffffff:ffffffff memory: 29.76 GiB unified: yes
  Info: Tools: api: eglinfo,glxinfo gpu: radeontop x11: xdriinfo, xdpyinfo,
    xprop, xrandr

Something to try: add to linu line in Grub stanza, to see if it helps:
	modprobe.blacklist=radeon

Is the correct way to do that to use the line
 	GRUB_CMDLINE_LINUX="modprobe.blacklist=radeon"
in /etc/default/grub, then run sudo update-grub, then reboot ?

That's the general idea how to make it permanent after testing to see if
it helps, but including in GRUB_CMDLINE_LINUX_DEFAULT=, possibly with
GRUB_CMDLINE_LINUX= also.

Strike "E" at the Grub menu and append it to the linu line before
proceeding with boot.

So, I rebooted and at the blue screen I pressed 'e'. At the "linux" line I
appended " modprobe.blacklist=radeon" (without quotes). It doesn't seem to
have created problems. I don't know if it helped because I had just
installed firmware-linux-free too (see below).

I see nothing that explains what is wrong, only evidence from inxi that
things are not right. Swrast is often a fallback, not what you want to
see, particularly for Display dri. Also bad is the OpenGL renderer report.
I don't know what the Phoenix renderer should be, but you don't want it to
be llvmpipe, another fallback.

Good to know.

I have no recent AMD GPUs, so no direct experience with Ryzen or Phoenix.
I suppose you have all these installed in current versions?:
	amd64-microcode
	firmware-amd-graphics
	firmware-linux-free
	libdrm-amdgpu1

Only 3 out of 4:

ii  amd64-microcode       3.20250311.1 amd64        Platform firmware and microcode for AMD CPUs and SoCs
ii  firmware-amd-graphics 20250410-2   all          Binary firmware for AMD/ATI graphics and NPU chips
un  firmware-linux-free   <none>       <none>       (no description available)
ii  libdrm-amdgpu1:amd64  2.4.124-2    amd64        Userspace interface to amdgpu-specific kernel DRM services -- runtime

I have now installed firmware-linux-free.

Since then, X seems to be stable.

Would firmware-linux-nonfree also be likely beneficial here?

If no one here comes up with any better suggestion(s), give a try asking
in one or more of the forums I find helpful, and help in when I can:
https://forums.debian.net/
https://www.linuxquestions.org/questions/debian-26/

Thanks.

Not all HDMI cables are created equal. Perhaps yours isn't top quality?
I've run across quite a number over the years that were junk to start
with, or didn't last.

I've used this one for years and it works fine when I use it with the older
central unit, so I'm confident this cable is not the problem.


Is it logical to suspect that the driver may be unreliable?

I would not exclude this possibility just as e.g. hardware failure.
Rather generic steps may help to reveal failure reason.

Install latest firmware (BIOS). If it offers an option to run hardware
self-test then try it.

Only twice in 30 years have I upgraded the firmware for a motherboard. Followed instructions to the letter. No problem during the update. Both times it crippled the machine. I will only ever do that again on a machine that I am ready to discard.

Check for errors, warnings, and all other messages related to graphics adapter output of the following command:
   sudo journalctl -b
You may discover e.g. missed firmware files.

Good idea. But... I don't know what a "missing firmware" line looks like here. And the output is both copious and very boring to read line-by-line.

If X is unreliable then you may use virtual console or ssh login from another machine (install ssh-server if have not it yet).

Yeah, but it's supposed to become a user-facing PC, not a server in a closet...


Many thanks for your ideas and your solutions!

Sébastien.

Reply to: