I installed Don't Starve through steam, and this appeared (https://i.sstatic.net/EjSGUPZP.png) It looks like there is a trouble with gpu drivers, i had same problem with kitty terminal, but solved it by installing mesa-amber instead of mesa. How can i solve this problem? lspci -k output:

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: skl_uncore
lspci: Unable to load libkmod resources: error -2
00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07)
        DeviceName: Onboard IGD
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: i915
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: intel_pch_thermal
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: mei_me
00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: ahci
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 (rev f1)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: pcieport
00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
        Subsystem: Hewlett-Packard Company Device 8101
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
        Subsystem: Hewlett-Packard Company Device 8101
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: snd_hda_intel
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: i801_smbus
01:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] (rev 83)
        Subsystem: Hewlett-Packard Company Radeon R7 M340
        Kernel driver in use: amdgpu
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: r8169
03:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
        Subsystem: Intel Corporation Dual Band Wireless AC 3165 [Stone Peak 1x1]
        Kernel driver in use: iwlwifi
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01)
        Subsystem: Hewlett-Packard Company Device 8101
        Kernel driver in use: rtsx_pci

system: arch, made pacman -Syu this morning(before it game didn't work too)

Does the AntiX use amdgpu for AMD videocards? I found that in Xubuntu system there is a problem with new amdgpu, so I cannot update, and AntiX works normally. The problem is that after the update Xubuntu boots only in command line regime. Xfce4 doesn't start. I think that new amdgpu module doesn't support my 11 year old videocard. In AntiX linux amdgpu works fine because there is 6.1 kernel while in Xubuntu there is 6.11 kernel.

Is there a way to simulate a physical HDMI cable unplugging and replugging on a Linux system running Xorg with AMDGPU driver? In my Xfce system on X11, I have trouble with monitor output/connector detection. In particular, when the system transitions from the Rescueshell/GRUB to the distro login manager (lightdm), the monitor turns blackish grey, and the only fix I've found so far is by unplugging the monitor's HDMI and replugging, or by changing the monitor's own FreeSync setting (Options: Standard Engine, Ultimate Engine, Off) in that black screen state and doing Ctrl+Alt+F2, which I think effectively "resets" the HDMI connection. Using drm.edid= as a kernel boot option can help with the issue, but having a valid Xorg.conf in /usr/share/X11/xorg.conf.d/ basically makes it useless and recreates the blackscreen, as I think Xorg/AMDGPU (my graphics driver) takes over control of the graphical output and uses the edid or modeline in the Xorg.conf, once it gets to the initial pre-login/post-login stage in lightdm. This switchup probably confuses my monitor. But I want to have a Xorg.conf for proper functionality. The blackscreen isn't completely black, as in a no signal, but it's somewhat grey. If I switch TTYs, the screen will flicker and go grey again, but there'll be no display at this stage. It's like the monitor is detected, but there the signal isn't interpreted right. I want to know if there is any way to make the KMS/DRM driver think that the monitor has been disconnected and reconnected, without a real physical disconnect, so the driver refreshes all "connectors" and hopefully gives output to the monitor, possibly using a udev HOTPLUG event. According to the answers in this question: , it is possible to use udevadm trigger to masquerade udev events to specific devices in /sys subsystems. Or by directly using echo ACTION > /sys/class/SUBSYTEM/DEVICE/uevent From udevadm trigger --verbose --action=help /sys/class/drm/card0-HDMI-A-1 I get a list of all possible 'trigger' options:

add
remove
change
move
online
offline
bind
unbind

I've tried using all of them, but they don't do anything equivalent to a full replugging. The screen stays on the whole time. However 'change' using udevadm trigger --verbose --action=change /sys/class/drm/card0-HDMI-A-1 forces a rescan for the device EDID in dmesg:

[34870.335496] Registering platform device 'HDMI-A-1'. Parent at platform
[34870.335523] device: 'HDMI-A-1': device_add
[34870.335545] platform HDMI-A-1: No ACPI support
[34870.335553] bus: 'platform': add device HDMI-A-1
[34870.335720] bus: 'platform': remove device HDMI-A-1
[34870.335746] [drm] Got external EDID base block and 0 extensions from "edid/1920x1080.bin" for connector "HDMI-A-1"

This does not turn off the screen though, and so doesn't help with the problem. Is there any way to mention a specific key / ENV{ATTRIBUTE} when triggering a udev event? For example someone else's udev logs during a monitor unplug and replug cycle:

udevadm monitor --environment --udev 
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV  [1370.249130] change   /devices/pci0000:00/0000:00:02.0/drm/card0 (drm)
ACTION=change
DEVNAME=/dev/dri/card0
DEVPATH=/devices/pci0000:00/0000:00:02.0/drm/card0
DEVTYPE=drm_minor
HOTPLUG=1
ID_FOR_SEAT=drm-pci-0000_00_02_0
ID_PATH=pci-0000:00:02.0
ID_PATH_TAG=pci-0000_00_02_0
MAJOR=226
MINOR=0
SEQNUM=1884
SUBSYSTEM=drm
TAGS=:seat:uaccess:
USEC_INITIALIZED=715

Here the main ACTION is "change", but is there a way *I* can specify that HOTPLUG=1 parameter? It's noteworthy that when *I* use udevadm monitor and do an unplug cycle, nothing shows up in output. But when switching TTYs to F2 then F7 (my GUI) using Ctrl+Alt+..., then I get this:

udevadm monitor --environment --udev
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing

UDEV  [4315.550505] add      /devices/platform/HDMI-A-1 (platform)
ACTION=add
DEVPATH=/devices/platform/HDMI-A-1
SUBSYSTEM=platform
MODALIAS=platform:HDMI-A-1
SEQNUM=3714
USEC_INITIALIZED=4315229577
ID_PATH=platform-HDMI-A-1
ID_PATH_TAG=platform-HDMI-A-1

UDEV  [4315.551278] remove   /devices/platform/HDMI-A-1 (platform)
ACTION=remove
DEVPATH=/devices/platform/HDMI-A-1
SUBSYSTEM=platform
MODALIAS=platform:HDMI-A-1
SEQNUM=3715
USEC_INITIALIZED=4315229577
ID_PATH=platform-HDMI-A-1
ID_PATH_TAG=platform-HDMI-A-1

which could indicate that hotplugging is not supported or triggered properly in my system, leading to my issues. I found a Gentoo forum post: which had my same question regarding unplug and replug, but there was not a solution there. I have tried echo off > /sys/class/drm/card0-HDMI-A-1/status and echo on > /sys/class/drm/card0-HDMI-A-1/status but it doesn't cause the monitor to turn off, only an EDID rescan in dmesg. The same thing as a udevadm trigger --action=change. echoing to enabled or dpms in that same directory doesn't seem to be allowed. I have tried xset -display :0 dpms force off (or -display :0.0) from a TTY/shell script, but it doesn't turn off the monitor. Though it works in a GUI of course, after I've already unplugged the monitor once. I tried

sudo mount -o remount,exec /dev
sudo vbetool dpms off
sudo mount -o remount,noexec /dev

from [this](https://old.reddit.com/r/linux4noobs/comments/vo7u7l/how_can_i_turn_the_display_off_in_a_tty/) and [this](https://askubuntu.com/questions/1384221/real-mode-call-failed-on-macbook-pro-when-trying-to-turn-screen-off-ubuntu-serve) , but it outputs Real mode call failed. So now I tried setterm --blank 1 from and consoleblank=200 (approximate bootup time for my device in seconds) as a kernel commandline parameter, and they also don't work as I want them to. They can turn off the screen, but it's not a hard enough reset that makes the monitor redetected like in a physical replugging. I've tried a systemd service like this ExecStart=/bin/sh -c 'while [ -n "$(pidof lightdm)" ] || [ -n "$(pidof X)" ] || [ -n "$(pidof Xorg)" ]; do sleep 10; done; sleep 15; echo '' > /sys/module/drm/parameters/edid_firmware && pkill X' to restart X at the login prompt, but it doesn't help either. I came across this guide , which mentioned > void (*output_poll_changed)(struct drm_device *dev); > >This operation notifies the driver that the status of one or more connectors has changed. Drivers that use the fb helper can just call the drm_fb_helper_hotplug_event function to handle this operation. Is there a way I can compile a binary and call this function manually at X startup, to achieve what I'm looking for? Or is there any other solution to address this? I am having this issue on a PS4 system running Arch Linux, and I think the monitor might have trouble with EDID communication. So the hardware situation is a bit flaky, but most of the underlying mechanics are still the same.

I am running Arch Linux on a Lenovo laptop with an AMD Ryzen 5 CPU/integrated GPU. Previously, I was using the AMDGPU driver and the GPU was running very well with it. However, after running a full system upgrade a couple of months ago, the AMDGPU module no longer seems to be getting loaded on boot, and if I try to load it manually with modprobe, I get the following error message: # modprobe amdgpu modprobe: ERROR: could not insert 'amdgpu': Cannot allocate memory I hold the versions of the Linux kernel, firmware, etc. when I upgrade (to ensure I stick with versions that I know work with my hardware). So, even though the rest of the system was upgraded, the kernel, modules, firmware were not changed during the update. So, I am a little confused as to what might be suddenly causing the AMDGPU module to not load properly. I suspect that some issue with udev may have been introduced with the upgrade, as there were a couple of other modules that were also not being loaded on boot after the upgrade, which I had to add manually to the initcpio. However, it seems strange that I would not be able to load AMDGPU manually after boot. Another thing to add is that my dmesg shows no lines that include either 'amdgpu' or '[drm]', which also seems a little odd. I have tried booting the laptop with an Arch live USB. In that case, amdgpu is being loaded and all of the dmesg [drm] amdgpu lines are present. So, I am fairly sure there is no issue with the hardware. Does anyone have any suggestions as to how I can troubleshoot this?

This is a follow-up to a question I asked a couple of days ago, relating to the amdgpu module not being loadable on boot after an Arch upgrade (https://unix.stackexchange.com/questions/794724/amdgpu-module-fails-to-load-after-arch-upgrade-cannot-allocate-memory) . Having read around a bit online, I suspect the issue may be that the GPU firmware is not being loaded on boot. So, I have a double-barrelled question related to this: 1) How can I verify if the firmware for my AMD GPU was loaded on boot or not? 2) If it wasn't, is it possible to load the GPU firmware manually, after boot? Is there a command for that? (I know that won't be a workable long-term solution, but it might help pinpoint where the issue is)

I have a laptop, an Acer Aspire 3 A315-41G-R6KL with an integrated Radeon Vega 8 graphics card on a Ryzen 5 2500U CPU and a discrete Radeon R535. This laptop was running Windows 10 before. But today, I installed an SSD with Fedora 37 on it. After 2–3 minutes of starting, the screen freezes and stops responding, as does the keyboard. I tried the following kernel versions: 6.2, 6.1, 6.0, 5.19 (in most cases, the screen freezes immediately after the desktop appears). With the amdgpu driver. I also tried to install a new version of Fedora, but the installer freezes right after the desktop is displayed. I also tried installing Manjaro and Ubuntu. In both cases, the screen and keyboard freeze after a couple of minutes. Manjaro also had frequent screen flashes. While trying to find a solution to the problem, I saw several articles stating that this line of processors has issues with Linux. Is this still relevant, and isn’t there any way to fix this? **Update:** I was able to fix my issues by switching to full Xorg and installing all the AMD drivers, as well as removing all other Nvidia and Intel drivers.

I recently encountered issues with some packages on my Linux Mint 22 Cinnamon system, particularly libgl. To fix them, I uninstalled all packages and then selectively reinstalled some. However, this process accidentally removed many graphics-related packages (I use AMD GPU). After realizing this, I rebooted. **What Happened After Rebooting:** - GRUB Menu Appeared: I selected my usual Linux Mint 22 Cinnamon option. - It booted into a TTY terminal instead of the graphical interface. - Reinstalling Graphics Packages in TTY: I logged in, installed the missing packages, and resolved held packages by downgrading certain dependencies. - Instead of rebooting, I ran sudo systemctl restart lightdm. This resulted in a black screen with only an underscore. Keyboard shortcuts like Ctrl+Alt+F1/F3/F6 did nothing, so I forcefully powered off the system. After Powering On Again, the system now shows a completely black screen immediately after boot. One click on the power button turns the PC off. I think this confirms that the problem with the gpu. **Recovery Mode Attempt:** - I rebooted, entered recovery mode, and selected the latest kernel. - Enabled Networking: It mentioned that this would remount the root filesystem as read/write and mount all filesystems from /etc/fstab. - Root Shell Access: I dropped into the root shell instead of pressing Ctrl+D for maintenance mode. - Tried Reinstalling AMD GPU Packages (Failed): In recovery mode, I tried reinstalling the missing AMD GPU packages, but the system keeps saying they aren’t installed, and I can’t proceed further. **System Configuration:** Primary SSD (Partitioned as follows): - Root (/) - Home (/home) - A second partition (auto-mounted via /etc/fstab) Secondary HDD (3 partitions, also auto-mounted via /etc/fstab, but not related to Linux). **Final Question:** As a last resort, I am considering reinstalling Linux Mint on the root (/) partition while keeping the same username to match my existing /home partition. - Will this preserve my data in /home and the second SSD partition? - Are there any other solutions before attempting a reinstallation? Would appreciate any guidance on how to recover my system without losing data.

I have HP Victus 16 with configuration Ryzen 7 7840HS(780M iGPU) and RTX3050. There is issues with my 780M iGPU. It gives black screen on Linux 6.9.1 when using iGPU. Using dGPU (which is RTX3050) from BIOS works perfectly. Furthermore, latest AMD drivers in Windows has same issues. Ubuntu 24.04 has different problems. Sometimes it has black screen in internal monitor of my laptop. I could not find any solutions to it.

My computer does not scale the UMA when it is maxed out. My laptop has an integrated GPU (iGPU), 32 GB of RAM, and it makes use of UMA. Its UEFI firmware has the following possibilities to configure the UMA: - auto (default, used during test) - 512 MB - 1 GB - 2 GB - 4 GB - 8 GB - 16 GB I start a game (via steam + proton) and it runs poorly. I monitor the system via nvtop, and see the GPU is maxed out, both on VRAM and 100% load. Interestingly, the VRAM is indicated to be 512 MB. I had hoped it would automatically scale with demand, given that is the intended use with UMA. After manually setting the UMA to 8 GB VRAM, the game performs much better and uses 5 GB. I see this as a bug or a missing feature. Could it be due to the motherboard firmware? Do I have to configure Wayland in a certain way? Is it up to the program (proton/the game) to demand for UMA scaling? Do I need to activate a kernel module/set a kernel argument? **System info** Distro: NixOS 24.11 (Vicuna) Kernel: 6.6.67 RAM: 31 GB GPU Driver: 4.6 Mesa 24.2.6 GPU: AMD Radeon (radeonsi, renoir, LLVM 18.1.8, DRM 3.54, 6.6.67) CPU: AMD Ryzen 7 4700U with Radeon Graphics

I've got an AMDGPU on Linux and want to be able to see which processes are utilising my precious 4GB of VRAM I need for gaming. I'd like this to be presented in a similar manner to top listing all processes utilising VRAM by usage. radeontop only shows total VRAM usage.

I do 3d art and was excited to get a new GPU, 7900XT. Week Before getting it, my grub corrupted because I resized my lvm partitions and moved them around, so now I have to manually boot through grub>. After installing the new GPU, my system has become very unstable. Here are some observations I made(all of these apply to both Wayland and X11 KDE plasma): - if I boot and log into either Wayland or X11, and don't move my mouse, the mouse will freeze within 3 minutes, then screen turns black, and my system will reboot on it's own. - if I boot and log, then asap open a browser and start a YouTube video, I know the system won't hang as long as the video is playing.(??) If I pause it, the system might or might not hang and reboot. It's a gamble. If it doesn't hang a few mins after pausing, then I can go for hours without issue. - Journalctl reports nothing that could explain these crashes. - the pc works fine if I stay in ctrl-alt-f3 or other (I think it's called tty?) any nongraphical session is stable. I tried the following: - updating motherboard bios - updating amd drivers manually (amdgpu_install from their proprietary repo) - changing session types (x11) My current boot process: 1. Fail at bios cause my usb keyboard fails to detect. 2. Reboot 3. Get to GRUB cli cause my grub/efi broke and I can't fix it for a week now, so I have to manualy type: 3.1. set root=(hd0,gpt4) 3.2. linux /vmlinuz-5....7..... root=/dev/mapper/rl-root 3.3. initrd /initramfs-5...7.... 3.4. boot 4. Log into Linux, wait 1 min for it to crash. 4.1. MAYBE if I immediately start browser and yt video on boot, the system seems to crash way less likely on first/second boot?! 5. Redo everything above except 4, cause now there's a 50/50 chance it will stay working. 6. Repeat five, chances it stays stable increase every reboot 7. Profit (10min later?) From what I saw online, Wayland and kernel weren't saying nicely with the 7900xt till recently, so the only solution I can think of is to compile a custom kernel with latest version and use that (then what's the point of using rhel9...) or maybe only latest Wayland (GCC is outdated on rhel9, so I can't.) Please give me some ideas how to fix it. I really don't want to reinstall. It would take me a week to get all the programs I need set up again, and many of them don't work on other distros(davinci resolve only works on rhel7-9, even provide a custom distro just for their program...) inxi:

djkato@djkato-vfx ~> inxi -I -G
Graphics:
  Device-1: AMD Navi 31 [Radeon RX 7900 XT/7900 XTX/7900 GRE/7900M]
    driver: amdgpu v: 6.8.5
  Device-2: AMD Raphael driver: amdgpu v: 6.8.5
  Display: wayland server: X.org v: 1.20.11 with: Xwayland v: 22.1.9
    compositor: kwin_wayland driver: X: loaded: amdgpu unloaded: modesetting
    dri: radeonsi gpu: amdgpu,amdgpu resolution: 1: 3072x1728 2: 2560x1440
  API: EGL v: 1.5 drivers: kms_swrast,radeonsi,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6 vendor: amd mesa v: 24.2.0-devel renderer: Radeon RX
    7900 XT (radeonsi navi31 LLVM 18.1.7 DRM 3.58
    5.14.0-427.37.1.el9_4.x86_64)
  API: Vulkan v: 1.3.268 drivers: radv,llvmpipe surfaces: xcb,xlib,wayland
Info:
  Memory: total: 32 GiB note: est. available: 30.5 GiB used: 3.62 GiB (11.9%)
  Processes: 366 Uptime: 26m Shell: fish inxi: 3.3.33

I have a Debian 12 in a machine where I have installed Windows 10 as a Guest using KVM (Managed with Virt-Manager). The machine has 2 graphic cards. 1) GeForce RTX 2060 12GB (I want to use in the host) 2) AMD Radeon R5 220 2GB ddr3 (I wanted to use in a Guest Windows 10) I follow mainly this link [kvm-gpu-passthrough](https://drakeor.com/2022/02/16/kvm-gpu-passthrough-tutorial/) In the Windows the device manager shows the Amd Radeon graphic cards and the Red Hat QXL controller. In the Windows I have install the driver from [AMD driver r5-220](https://www.amd.com/pt/support/downloads/drivers.html/graphics/radeon-r9-r7-r5/radeon-r5-200-series/amd-radeon-r5-220.html) but when I try to run the AMD program it says "No AMD graphics driver is installed or the AMD driver is not functioning properly I have configured the /etc/default/grub file as

GRUB_CMDLINE_LINUX_DEFAULT="quiet modprobe.blacklist=radeon"
GRUB_CMDLINE_LINUX="amd_iommu=on iommu=pt "

Using the Virt-Manager I have added 2 PCI associated to the AMD card

and

I have used the script

!/bin/bash
shopt -s nullglob
for g in /sys/kernel/iommu_groups/*; do
    echo "IOMMU Group ${g##*/}:"
    for d in $g/devices/*; do
        echo -e "\t$(lspci -nns ${d##*/})"
    done;
done;

in order to get this 2 "pci devices". This script gives me

IOMMU Group 28:
	0b:00.0 VGA compatible controller : NVIDIA Corporation TU106 [GeForce RTX 2060 12GB] [10de:1f03] (rev a1)
	0b:00.1 Audio device : NVIDIA Corporation TU106 High Definition Audio Controller [10de:10f9] (rev a1)
IOMMU Group 29:
	0c:00.0 VGA compatible controller : Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9]
	0c:00.1 Audio device : Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] [1002:aa68]

and I have supposed that the Group 29 is the one I have to add to the Virtual Machine I do not know if I am missing something.

Situation: Desktop PC with and AMD CPU with an iGPU plus a Radeon GPU at PCIe. EndeavourOS with systemd-boot (but have also tried Pop OS which uses GRUB). In the BIOS settings, the PCIe GPU is selected as primary. The bootloaders (both systemd-boot and GRUB) give VGA out from both mainboard connectors (iGPU) and the Radeon connector. But when the kernel takes over, output is only available from iGPU. Both for boot messages and later through SDDM, wayland, KDE Plasma. When a monitor is attached to the PCIe GPU, the monitor turns on but has a blank screen. If I disable iGPU from the BIOS, then no output on either GPU.

# inxi -F
System:
  Host: caladan Kernel: 6.9.3-arch1-1 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.0.5 Distro: EndeavourOS
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: TUF GAMING B650-PLUS WIFI v: Rev 1.xx
    serial: 240131817600271 UEFI: American Megatrends v: 1811 date: 10/07/2023
CPU:
  Info: 8-core model: AMD Ryzen 7 7800X3D bits: 64 type: MT MCP cache:
    L2: 8 MiB
  Speed (MHz): avg: 1429 min/max: 400/5050 cores: 1: 400 2: 400 3: 3657
    4: 4019 5: 400 6: 400 7: 400 8: 3601 9: 3609 10: 400 11: 400 12: 400 13: 400
    14: 400 15: 3584 16: 400
Graphics:
  Device-1: AMD Navi 32 [Radeon RX 7700 XT / 7800 XT] driver: N/A
  Device-2: AMD Raphael driver: amdgpu v: kernel
  Device-3: Jieli USB PHY 2.0 driver: snd-usb-audio,uvcvideo type: USB
  Display: server: X.Org v: 24.1 with: Xwayland v: 24.1.0 driver: X:
    loaded: amdgpu unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu
    resolution: 3440x1440~60Hz
  API: EGL v: 1.5 drivers: radeonsi,swrast platforms: x11,surfaceless,device
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.1.1-arch1.1
    renderer: AMD Radeon Graphics (radeonsi raphael_mendocino LLVM 17.0.6 DRM
    3.57 6.9.3-arch1-1)
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: AMD Navi 31 HDMI/DP Audio driver: snd_hda_intel
  Device-2: AMD Rembrandt Radeon High Definition Audio driver: snd_hda_intel
  Device-3: AMD Family 17h/19h HD Audio driver: snd_hda_intel
  Device-4: GN Netcom Jabra EVOLVE 20 SE driver: jabra,snd-usb-audio,usbhid
    type: USB
  Device-5: Jieli USB PHY 2.0 driver: snd-usb-audio,uvcvideo type: USB
  API: ALSA v: k6.9.3-arch1-1 status: kernel-api
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 10:7c:61:73:9a:73
  Device-2: Realtek RTL8852BE PCIe 802.11ax Wireless Network
    driver: rtw89_8852be
  IF: wlan0 state: down mac: 12:07:7d:d1:bc:35
Bluetooth:
  Device-1: IMC Networks Bluetooth Radio driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: A8:41:F4:2B:00:6D bt-v: 5.3
Drives:
  Local Storage: total: 1.82 TiB used: 11 GiB (0.6%)
  ID-1: /dev/nvme0n1 vendor: Corsair model: MP600 PRO XT size: 931.51 GiB
  ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 970 EVO 1TB size: 931.51 GiB
Partition:
  ID-1: / size: 906.17 GiB used: 10.9 GiB (1.2%) fs: ext4 dev: /dev/nvme0n1p2
Swap:
  ID-1: swap-1 type: partition size: 8.8 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme0n1p3
Sensors:
  System Temperatures: cpu: 40.6 C mobo: N/A gpu: amdgpu temp: 37.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 30.57 GiB used: 4.26 GiB (13.9%)
  Processes: 305 Uptime: 18m Shell: Bash inxi: 3.3.34

Dmesg has this interesting part:

[   23.739334] [drm:amdgpu_bo_init [amdgpu]] *ERROR* Unable to set WC memtype for the aperture base
[   23.739462] [drm:amdgpu_device_init [amdgpu]] *ERROR* sw_init of IP block  failed -22
[   23.739587] amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_init failed
[   23.739588] amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
[   23.739590] amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device.
[   23.739712] amdgpu: probe of 0000:03:00.0 failed with error -22

I recently installed Xubuntu 22.04 on a new PC Build. The PC is using the onboard GPU from an AMD 7900 X3D CPU. Everything displays correctly on the system, except for Firefox (see pic). Even though you can't see the window, the program is responsive. I am able to navigate to google.com, and close down the application correctly. I tried making changes to the Window Manager settings, Display, and XFCE settings but with no success. I also erased the disk and installed ubuntu 23.10 Desktop on the PC, but that suffers from the same issue. Does anyone know what could be causing it, and how I can fix it? -Robert

I have recently built a PC. Specs: - Mobo: TUF GAMING B650-PLUS WIFI - GPU: Radeon Rx 6800 XT OC - CPU: Ryzen 7 7800x3d - RAM: 2x 16GB 6000Hz CL30 First I've installed Windows. That system had problems with using the mobo's network card. After **installing the provided drivers** it all came together nicely and works without issues. ## Minor issues Unfortunately, I've encountered many problems during Debian installation (I want to have both systems). During installation, the installer was unable to configure DHCP, so I simply skipped this step and continued without the internet connection. After installation, I was unable to use wifi (I haven't checked if the RJ45 port works), so I'm using my phone to share internet through usb. I might add that bluetooth also doesn't really work, it's unable to connect to any device and sometimes it doesn't even register surrounding devices. I was unable to find proper drivers. There are only drivers for Red Hat, Ubuntu and SLED. I couldn't find any quick fixes, so I didn't bother with this issue (I won't be using the network adapter anyways). ## The most important issue is that my GPU refuses to output HDMI signal (now, my monitor is connected to the integrated graphics). Let me clarify what happens if I connect my monitor through HDMI (I don't have display port in that device). My screen simply constantly displays:[The image of the freezed screen](https://i.sstatic.net/lFxVx.jpg) . Changing the to the mobo's port after that freeze makes the screen work correctly. Changing back, to gpu reverts to the same freeze screen. The text on the freezed screen:

Booting `Debian GNU/Linux'

Loading Linux 6.1.0-18-amd64 . . . 
Loading initial ramdisk . . .

I've tried running apt update, apt upgrade. Running sudo update-initramfs -u resulted in printing a lot of missing modules, which I've installed according to the fix provided [here](https://askubuntu.com/questions/1124253/missing-firmware-for-amdgpu) and [here](https://unix.stackexchange.com/questions/710036/possible-missing-firmware-although-firmware-is-installed) . The second fix actually was onto something, I didn't have the "firmware-linux" pacakge installed (I did install it). Yet after all this, after running sudo update-initramfs -u I get:

update-initramfs: Generating /boot/initrd.img-6.1.0-18-amd64
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpu

I'll be grateful for any help, because I'm unable to solve this issue by myself. EDIT: After running the suggested commands my sources.list file looks like this:

# deb cdrom:[Debian GNU/Linux 12.5.0 _Bookworm_ - Official amd64 DVD Binary-1 with firmware 20240210-11:28]/ bookworm contrib main non-free-firmware
deb https://deb.debian.org/debian/  bookworm main contrib non-free non-free-firmware
deb http://deb.debian.org/debian-security  bookworm-security main contrib non-free non-free-firmware

Edit 2: The system or someone, flagged this as a [duplicated] question. I assure you it was not, the fix in the linked question DIDN'T work for me. The problem was, that I had an old version of bios installed on my mobo. After updating bios the gpu problem vanished (I might add, that I've tried many things and in the end I've installed Ubuntu 22.04.04 instead of Debian 12). For the record, the version of bios my mobo was using was 1811, and the version that works for me is 2413. I've also had the newest (6.0.60002) amd drivers installed while I've updated my bios. I would have closed this question, if it hadn't been closed before, by someone who didn't assess the situation well or the system. So yeah, kids update your bios if you've got such a strange driver issue.

I've got 6700S laptop GPU that has 100W power limit provided by ASUS' custom design or whatever. On Windows it uses 100W power limit just fine. But on Linux with **amdgpu** it starts for a couple of seconds with 100W after system boot and by ~25th second it turns it down to 80W which is its vanilla power limit. The value is confirmed by cat /sys/class/drm/card0/device/hwmon/hwmon4/power1_cap. I've tried several kernels: 6.2, 6.5, 6.7. Also I tried several mesa versions: 23.1, 24.1. Also I manually upgraded **linux-firmware** for **amdgpu** specifically - no luck. Dmesg shows this output when 100W to 80W change happens (supposedly): [ 22.496680] amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 22.513799] amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 22.513802] amdgpu 0000:03:00.0: amdgpu: SMU is resuming... [ 22.513806] amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x0000000f, smu fw if version = 0x00000013, smu fw program = 0, version = 0x003b2f00 (59.47.0) [ 22.513810] amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched [ 22.565134] amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully! Where should I dig to allow this GPU to have power1_cap_max to be 100W? UPD: It seems like this happens when this GPU is being sent to low-power state and then it resumes. By default it boots with 100W limit just fine. Then it's being suspended (or smth) due to inactivity - iGPU is used. When the system needs this GPU back it resumes it and then it overrides the limit!

I installed Debian 12 Bookworm with Gnome on my new Yoga notebook (Ryzen 7 7840HS with Radeon™ 780M), and I'm getting strange amdgpu error while booting. This is my dmesg | grep 'firmware' output: [ 0.053111] Spectre V2 : Enabling Restricted Speculation for firmware calls [ 1.896309] amdgpu 0000:63:00.0: firmware: failed to load amdgpu/gc_11_0_1_mes_2.bin (-2) [ 1.896357] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware [ 1.896394] amdgpu 0000:63:00.0: firmware: failed to load amdgpu/gc_11_0_1_mes_2.bin (-2) [ 1.896420] amdgpu 0000:63:00.0: Direct firmware load for amdgpu/gc_11_0_1_mes_2.bin failed with error -2 [ 1.896464] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_mes.bin [ 1.896499] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_mes1.bin [ 1.897445] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/psp_13_0_4_toc.bin [ 1.897487] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/psp_13_0_4_ta.bin [ 1.897621] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/dcn_3_1_4_dmcub.bin [ 1.897624] [drm] Loading DMUB firmware via PSP: version=0x08000500 [ 1.897657] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_imu.bin [ 1.897693] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_pfp.bin [ 1.897725] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_me.bin [ 1.897746] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_rlc.bin [ 1.897779] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/gc_11_0_1_mec.bin [ 1.898313] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/sdma_6_0_1.bin [ 1.898366] amdgpu 0000:63:00.0: firmware: direct-loading firmware amdgpu/vcn_4_0_2.bin [ 1.898367] [drm] Found VCN firmware Version ENC: 1.10 DEC: 5 VEP: 0 Revision: 0 [ 1.898373] amdgpu 0000:63:00.0: amdgpu: Will use PSP to load VCN firmware [ 4.531269] platform regulatory.0: firmware: direct-loading firmware regulatory.db [ 4.531359] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s [ 4.701149] mt7921e 0000:01:00.0: firmware: direct-loading firmware mediatek/WIFI_MT7922_patch_mcu_1_1_hdr.bin [ 4.716652] mt7921e 0000:01:00.0: firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7922_1.bin [ 4.766133] mt7921e 0000:01:00.0: firmware: direct-loading firmware mediatek/WIFI_RAM_CODE_MT7922_1.bin [ 5.508199] bluetooth hci0: firmware: direct-loading firmware mediatek/BT_RAM_CODE_MT7922_1_1_hdr.bin I would be very grateful if you could help me with this.

Before start: I replied to a thread on Arch Linux forum about similar issue (https://bbs.archlinux.org/viewtopic.php?id=284076) , since I'm on Arch. I'm asking here to get more help and check if anyone using other distributions is having the same issue. After upgrading the kernel to the current newest on Arch repository, that is 6.5.2-arch1, or the version I used to use, 6.5.2-zen1, I'm experiencing random GPU crash that renders the system virtually unusable because it happens around 5~20 minutes of uptime. The system journal log showed something like this:

Sep 11 20:00:46 yoohyeon.dc.sidlibrary.org kernel: amdgpu 0000:07:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:1 pasid:32814, for process chrome pid 4073 thread chrome:cs0 pid 4101)
Sep 11 20:00:46 yoohyeon.dc.sidlibrary.org kernel: amdgpu 0000:07:00.0: amdgpu:   in page starting at address 0x0000e38dbdd3b000 from IH client 0x1b (UTCL2)
Sep 11 20:00:46 yoohyeon.dc.sidlibrary.org kernel: amdgpu 0000:07:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00100430
Sep 11 20:00:46 yoohyeon.dc.sidlibrary.org kernel: amdgpu 0000:07:00.0: amdgpu:          Faulty UTCL2 client ID: IA (0x2)
Sep 11 20:00:46 yoohyeon.dc.sidlibrary.org kernel: amdgpu 0000:07:00.0: amdgpu:          MORE_FAULTS: 0x0
Sep 11 20:00:46 yoohyeon.dc.sidlibrary.org kernel: amdgpu 0000:07:00.0: amdgpu:          WALKER_ERROR: 0x0
Sep 11 20:00:46 yoohyeon.dc.sidlibrary.org kernel: amdgpu 0000:07:00.0: amdgpu:          PERMISSION_FAULTS: 0x3
Sep 11 20:00:46 yoohyeon.dc.sidlibrary.org kernel: amdgpu 0000:07:00.0: amdgpu:          MAPPING_ERROR: 0x0
Sep 11 20:00:46 yoohyeon.dc.sidlibrary.org kernel: amdgpu 0000:07:00.0: amdgpu:          RW: 0x0

I tried switching between mesa/proprietary drivers, also between mesa radeon-vulkan and amdvlk, changing the session type (X11/Wayland) chrome uses, or changing the session type for the whole DE (I use KDE Plasma, but based on quick search GNOME users seemed to have the same problem), or adding kernel cmdline parameters suggested on here and there on the web (relax, I referred to documentations for the implications before applying it), such as amdgpu.runpm=0, amdgpu.dpm=0, amdgpu.vm_update_mode=3 and so on, but no luck on any of them or their combinations. Especially, amdgpu.dpm=0 rendered the system unbootable, so I guess that's definitely not the one I was looking for. The issue happened more frequently when I was using chrome/chromium (with or without vaapi hardware acceleration, and both X11/Wayland session), and when the external monitor (4K2K@60Hz*1 + FHD@60Hz*1) was attached via USB-C DP Alt and then converted to HDMI by the dock. Fortunately, downgrading the kernel to 6.4.12-arch1 or 6.4.12-zen1 seemed to make the system stable, and that is why I'm suspecting the new kernel is the problem, and decided to ask here to see if any other distro kernel or vanilla kernel from kernel.org has the same issue. I'm now on linux-lts Arch kernel package (specifically, 6.1.52-1-lts kernel) temporarily to make the system usable, and it is stable so far, but I want to be that early adaptor who keeps living on the almost-newest kernel versions XD While I will try to bisect what commit may have contributed to this issue with Arch forum's help, any ideas, issue me-tos, or suggestions are welcomed. Thanks for taking time to read this question and, if you do so, replying/answering it!

New install of Debian bookworm on a system featuring an AMD Radeon RX 6600 using the amdgpu driver. I installed vdpauinfo (sudo apt install vdpauinfo) and found a problem that is discussed in the [Arch wiki](https://wiki.archlinux.org/title/Hardware_video_acceleration#Configuring_VDPAU) .

> vdpauinfo
display: :0   screen: 0
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
Error creating VDPAU device: 1

I'm surprised this isn't configured out of the box with bookworm (and I'm new to Debian). Am I missing something, or do I need to set the VDPAU_DRIVER environment variable (which is unset out of the box in my distro)?

Found out that Hardware Acceleration when using a AMD Ryzen 9 5900HX will cause video lockups or system reboots. Using a Minisforum HX90 computer. Using open-source drivers and admgpu. No error msg, justs locks up or reboots. All drivers, OS and software updated and current. Been using Linux for a while, but have not run into this type of problem before and have not studied Arch Linux internals. How do I disable this feature from AMDgpu. Thanks.