Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
1
votes
1
answers
1906
views
dota 2 graphics problem in ubuntu 14.04
I installed Ubuntu 14.04 in my laptop. I then installed steam and finally dota 2. But the graphics are very bad. I have AMD Radeon 7400 in my laptop. It seems like dota 2 is not running through my graphic card. I don't even know whether after installing Ubuntu I have my graphic card driver installed...
I installed Ubuntu 14.04 in my laptop. I then installed steam and finally dota 2.
But the graphics are very bad.
I have AMD Radeon 7400 in my laptop. It seems like dota 2 is not running through my graphic card.
I don't even know whether after installing Ubuntu I have my graphic card driver installed or not. Do I have to manually install the graphic card driver or it is already installed? And if so, how to enable it so that dota 2 runs with some good textures.
But the graphics are very bad.
I have AMD Radeon 7400 in my laptop. It seems like dota 2 is not running through my graphic card.
I don't even know whether after installing Ubuntu I have my graphic card driver installed or not. Do I have to manually install the graphic card driver or it is already installed? And if so, how to enable it so that dota 2 runs with some good textures.
Anurag Kumar
(83 rep)
Dec 2, 2014, 05:48 PM
• Last activity: Jul 28, 2025, 04:06 PM
0
votes
0
answers
46
views
AntiX Linux and amdgpu
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 s...
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.
Mahler
(101 rep)
Jul 3, 2025, 07:46 PM
• Last activity: Jul 4, 2025, 10:38 AM
2
votes
1
answers
2404
views
How to change desktop resolution from terminal for KDE5 running on Wayland?
Using KDE5 on Arch Linux with Wayland. I hit apply when changing resolutions to see which one would be suitable, small desktop resolution and then my monitor said it was unsupported. How do I revert/reset it from a terminal?
Using KDE5 on Arch Linux with Wayland. I hit apply when changing resolutions to see which one would be suitable, small desktop resolution and then my monitor said it was unsupported.
How do I revert/reset it from a terminal?
Obsidian Jackal
(1467 rep)
Jul 22, 2018, 09:54 PM
• Last activity: Jul 2, 2025, 10:04 AM
6
votes
1
answers
2901
views
Switchable graphics Intel + AMD Venus Pro
I'm using Manjaro Linux on my laptop with switchable graphic cards: ``` 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus PRO [Radeon HD 8850M / R9 M265X] (rev ff) `...
I'm using Manjaro Linux on my laptop with switchable graphic cards:
The above shows that bumblebee's drivers are installed, but the daemon fails:
[luke@manjaro ~]$ sudo systemctl status bumblebeed
● bumblebeed.service - Bumblebee C Daemon
Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since pią 2015-09-18 16:22:55 CEST; 29s ago
Process: 1192 ExecStart=/usr/bin/bumblebeed (code=exited, status=1/FAILURE)
Main PID: 1192 (code=exited, status=1/FAILURE)
wrz 18 16:22:55 manjaro systemd
: bumblebeed.service: Unit entered failed state.
wrz 18 16:22:55 manjaro systemd
: bumblebeed.service: Failed with result 'exit-code'.
During my trial-and-error I also tried to install
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus PRO [Radeon HD 8850M / R9 M265X] (rev ff)
Here's a screenshot of the drivers section of Manjaro Settings Manager:



video-catalyst
driver (in window shown above). It ended miserably - after the initial startup the screen was full white. I switched to another TTY and deleted video-catalyst using mhwd
.
My goal is to be able to play games on Steam. What can you recommend?
Luke
(151 rep)
Sep 18, 2015, 02:46 PM
• Last activity: Jun 29, 2025, 05:04 PM
0
votes
0
answers
40
views
Thinkpad T14 AMD battery drain issue
I have a battery drain in a Thinkpad T14 Gen1 AMD Ryzen 7 that's been happening since YEARS, and I cannot solve. Just look at these two lines, ``` Jun 24 20:17:59 t14 kernel: PM: suspend entry (deep) [...] Jun 25 20:08:47 t14 systemd-sleep[7518]: Battery energy change of -35.5 % (-18310 mWh) at an a...
I have a battery drain in a Thinkpad T14 Gen1 AMD Ryzen 7 that's been happening since YEARS, and I cannot solve. Just look at these two lines,
Jun 24 20:17:59 t14 kernel: PM: suspend entry (deep)
[...]
Jun 25 20:08:47 t14 systemd-sleep: Battery energy change of -35.5 % (-18310 mWh) at an average rate of -1.48 %/h (-767 mW).
-35% in a day suspended! something's really wrong.
I don't know what to do to debug or improve these numbers. This has been happening since I've bought it, and I've tried different kernels.
S3 is setup in BIOS.
Pop! _OS 22.04.
Linux version is Linux t14 6.9.3-76060903-generic #202405300957~1738770968~22.04~d5f7c84 SMP PREEMPT_DYNAMIC Wed F x86_64 x86_64 x86_64 GNU/Linux
If you're 100% sure this is firmware issue, you can close this post and vote negative, I won't blame you. I just need help to debug, and maybe some of you happen
Full log if it helps to find you some clue,
Jun 24 20:17:58 t14 systemd: Reached target Sleep.
Jun 24 20:17:58 t14 systemd: Condition check resulted in Record successful boot for GRUB being skipped.
Jun 24 20:17:58 t14 systemd: Condition check resulted in GRUB failed boot detection being skipped.
Jun 24 20:17:58 t14 systemd: Starting NVIDIA system suspend actions...
Jun 24 20:17:58 t14 suspend: nvidia-suspend.service
Jun 24 20:17:58 t14 logger: Jun 24 20:17:58 suspend: nvidia-suspend.service
Jun 24 20:17:58 t14 systemd: nvidia-suspend.service: Deactivated successfully.
Jun 24 20:17:58 t14 systemd: Finished NVIDIA system suspend actions.
Jun 24 20:17:58 t14 systemd: Starting System Suspend...
Jun 24 20:17:58 t14 systemd-sleep: Currently on battery.
Jun 24 20:17:58 t14 systemd-sleep: Saving time and battery energy before sleeping (suspend).
Jun 24 20:17:59 t14 rfkill: block set for type bluetooth
Jun 24 20:17:59 t14 systemd-sleep: Entering sleep state 'suspend'...
Jun 24 20:17:59 t14 kernel: PM: suspend entry (deep)
Jun 24 20:17:59 t14 kernel: Filesystems sync: 0.026 seconds
Jun 25 20:08:47 t14 kernel: Freezing user space processes
Jun 25 20:08:47 t14 kernel: Freezing user space processes completed (elapsed 0.002 seconds)
Jun 25 20:08:47 t14 kernel: OOM killer disabled.
Jun 25 20:08:47 t14 kernel: Freezing remaining freezable tasks
Jun 25 20:08:47 t14 kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jun 25 20:08:47 t14 kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117)
Jun 25 20:08:47 t14 kernel: ACPI: EC: interrupt blocked
Jun 25 20:08:47 t14 kernel: ACPI: PM: Preparing to enter system sleep state S3
Jun 25 20:08:47 t14 kernel: ACPI: EC: event blocked
Jun 25 20:08:47 t14 kernel: ACPI: EC: EC stopped
Jun 25 20:08:47 t14 kernel: ACPI: PM: Saving platform NVS memory
Jun 25 20:08:47 t14 kernel: Disabling non-boot CPUs ...
Jun 25 20:08:47 t14 kernel: smpboot: CPU 1 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 2 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 3 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 4 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 5 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 6 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 7 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 8 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 9 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 10 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 11 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 12 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 13 is now offline
Jun 25 20:08:47 t14 kernel: smpboot: CPU 14 is now offline
Jun 25 20:08:47 t14 kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Jun 25 20:08:47 t14 kernel: smpboot: CPU 15 is now offline
Jun 25 20:08:47 t14 kernel: ACPI: PM: Low-level resume complete
Jun 25 20:08:47 t14 kernel: ACPI: EC: EC started
Jun 25 20:08:47 t14 kernel: ACPI: PM: Restoring platform NVS memory
Jun 25 20:08:47 t14 kernel: AMD-Vi: Virtual APIC enabled
Jun 25 20:08:47 t14 kernel: AMD-Vi: Virtual APIC enabled
Jun 25 20:08:47 t14 kernel: LVT offset 0 assigned for vector 0x400
Jun 25 20:08:47 t14 kernel: Enabling non-boot CPUs ...
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C001: Found 3 idle states
Jun 25 20:08:47 t14 kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Jun 25 20:08:47 t14 kernel: CPU1 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C002: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU2 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C003: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU3 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 4 APIC 0x4
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C004: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU4 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 5 APIC 0x5
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C005: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU5 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 6 APIC 0x6
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C006: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU6 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C007: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU7 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 8 APIC 0x8
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C008: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU8 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 9 APIC 0x9
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C009: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU9 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 10 APIC 0xa
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C00A: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU10 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 11 APIC 0xb
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C00B: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU11 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 12 APIC 0xc
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C00C: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU12 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 13 APIC 0xd
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C00D: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU13 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 14 APIC 0xe
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C00E: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU14 is up
Jun 25 20:08:47 t14 kernel: smpboot: Booting Node 0 Processor 15 APIC 0xf
Jun 25 20:08:47 t14 kernel: ACPI: \_SB_.PLTF.C00F: Found 3 idle states
Jun 25 20:08:47 t14 kernel: CPU15 is up
Jun 25 20:08:47 t14 kernel: ACPI: PM: Waking up from system sleep state S3
Jun 25 20:08:47 t14 kernel: ACPI: EC: interrupt unblocked
Jun 25 20:08:47 t14 kernel: ACPI: EC: event unblocked
Jun 25 20:08:47 t14 kernel: usb usb1: root hub lost power or was reset
Jun 25 20:08:47 t14 kernel: usb usb2: root hub lost power or was reset
Jun 25 20:08:47 t14 kernel: usb usb3: root hub lost power or was reset
Jun 25 20:08:47 t14 kernel: xhci_hcd 0000:06:00.0: Zeroing 64bit base registers, expecting fault
Jun 25 20:08:47 t14 kernel: [drm] PCIE GART of 1024M enabled.
Jun 25 20:08:47 t14 kernel: [drm] PTB located at 0x000000F41FC00000
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: PSP is resuming...
Jun 25 20:08:47 t14 kernel: usb 6-4: reset full-speed USB device number 3 using xhci_hcd
Jun 25 20:08:47 t14 kernel: usb 2-2: reset high-speed USB device number 2 using xhci_hcd
Jun 25 20:08:47 t14 kernel: nvme nvme0: 16/0/0 default/read/poll queues
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: reserve 0x400000 from 0xf41f800000 for PSP TMR
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: RAS: optional ras ta ucode is not available
Jun 25 20:08:47 t14 kernel: psmouse serio1: synaptics: queried max coordinates: x [..5678], y [..4694]
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: RAP: optional rap ta ucode is not available
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resuming...
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: dpm has been disabled
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resumed successfully!
Jun 25 20:08:47 t14 kernel: [drm] DMUB hardware initialized: version=0x0101002B
Jun 25 20:08:47 t14 kernel: [drm] kiq ring mec 2 pipe 1 q 0
Jun 25 20:08:47 t14 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
Jun 25 20:08:47 t14 kernel: [drm] JPEG decode initialized successfully.
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
Jun 25 20:08:47 t14 kernel: amdgpu 0000:07:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
Jun 25 20:08:47 t14 kernel: psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1162..]
Jun 25 20:08:47 t14 kernel: OOM killer enabled.
Jun 25 20:08:47 t14 kernel: Restarting tasks ...
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
Jun 25 20:08:47 t14 kernel: pci_bus 0000:01: Allocating resources
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.1: bridge window [io 0x1000-0x0fff] to [bus 01] add_size 1000
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.1: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 01] add_size 200000 add_align 100000
Jun 25 20:08:47 t14 kernel: pci_bus 0000:02: Allocating resources
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.2: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 02] add_size 200000 add_align 100000
Jun 25 20:08:47 t14 kernel: pci_bus 0000:03: Allocating resources
Jun 25 20:08:47 t14 kernel: pci_bus 0000:04: Allocating resources
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.4: bridge window [io 0x1000-0x0fff] to [bus 04] add_size 1000
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.4: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 04] add_size 200000 add_align 100000
Jun 25 20:08:47 t14 kernel: pci_bus 0000:05: Allocating resources
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.6: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 05] add_size 200000 add_align 100000
Jun 25 20:08:47 t14 kernel: pci_bus 0000:06: Allocating resources
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.7: bridge window [io 0x1000-0x0fff] to [bus 06] add_size 1000
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.7: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 06] add_size 200000 add_align 100000
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.1: bridge window [mem 0x430200000-0x4303fffff 64bit pref]: assigned
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.2: bridge window [mem 0x430400000-0x4305fffff 64bit pref]: assigned
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.4: bridge window [mem 0x430600000-0x4307fffff 64bit pref]: assigned
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.6: bridge window [mem 0x430800000-0x4309fffff 64bit pref]: assigned
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.7: bridge window [mem 0x430a00000-0x430bfffff 64bit pref]: assigned
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.1: bridge window [io 0x5000-0x5fff]: assigned
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.4: bridge window [io 0x6000-0x6fff]: assigned
Jun 25 20:08:47 t14 kernel: pcieport 0000:00:02.7: bridge window [io 0x7000-0x7fff]: assigned
Jun 25 20:08:47 t14 kernel: done.
Jun 25 20:08:47 t14 kernel: random: crng reseeded on system resumption
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: Device revision is 1
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: Secure boot is enabled
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: OTP lock is enabled
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: API lock is enabled
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: Debug lock is disabled
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: Boot Address: 0x24800
Jun 25 20:08:47 t14 kernel: Bluetooth: hci0: Firmware Version: 132-3.24
Jun 25 20:08:47 t14 kernel: thermal thermal_zone1: failed to read out thermal zone (-61)
Jun 25 20:08:47 t14 kernel: PM: suspend exit
Jun 25 20:08:47 t14 kernel: pci_bus 0000:07: Allocating resources
Jun 25 20:08:47 t14 systemd-resolved: Clock change detected. Flushing caches.
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/ldac
Jun 25 20:08:47 t14 tailscaled: control: controlhttp: failed dialing using DialPlan, falling back to DNS; errs=multiple errors:
Jun 25 20:08:47 t14 tailscaled: all connection attempts failed (HTTP: dial tcp [2a05:d014:386:202:1e36:2966:5bec:a911]:80: connect: network is unreachable, HTTPS: dial tcp [2a05:d014:386:202:1e36:2966:5bec:a911]:443: connect: network is unreachable)
Jun 25 20:08:47 t14 tailscaled: connection attempts aborted by context: context deadline exceeded
Jun 25 20:08:47 t14 tailscaled: connection attempts aborted by context: context deadline exceeded
Jun 25 20:08:47 t14 tailscaled: connection attempts aborted by context: context deadline exceeded
Jun 25 20:08:47 t14 tailscaled: connection attempts aborted by context: context deadline exceeded
Jun 25 20:08:47 t14 tailscaled: connection attempts aborted by context: context deadline exceeded
Jun 25 20:08:47 t14 tailscaled: connection attempts aborted by context: context deadline exceeded
Jun 25 20:08:47 t14 tailscaled: connection attempts aborted by context: context deadline exceeded
Jun 25 20:08:47 t14 systemd-logind: Lid opened.
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink/aptx_hd
Jun 25 20:08:47 t14 systemd-sleep: System returned from sleep state.
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/aptx_hd
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink/aptx
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/aptx
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink/aac
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/aac
Jun 25 20:08:47 t14 systemd: Starting Daily dpkg database backup service...
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink/sbc
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/sbc
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink/sbc_xq
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/sbc_xq
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/faststream
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink/opus_05
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/opus_05
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jun 25 20:08:47 t14 bluetoothd: Endpoint unregistered: sender=:1.39 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jun 25 20:08:47 t14 systemd-sleep: Currently on battery.
Jun 25 20:08:47 t14 systemd-sleep: Duration of 0 days 23 hours 50 minutes sleeping (suspend).
Jun 25 20:08:47 t14 systemd: Condition check resulted in Rotate log files being skipped.
Jun 25 20:08:47 t14 systemd-sleep: Battery energy change of -35.5 % (-18310 mWh) at an average rate of -1.48 %/h (-767 mW).
Jun 25 20:08:47 t14 systemd: Stopped target Bluetooth.
Jun 25 20:08:47 t14 systemd: Stopped target Bluetooth Support.
Jun 25 20:08:47 t14 systemd: Reached target Bluetooth.
Jun 25 20:08:47 t14 systemd: Reached target Bluetooth Support.
Jun 25 20:08:47 t14 systemd: dpkg-db-backup.service: Deactivated successfully.
Jun 25 20:08:47 t14 systemd: Finished Daily dpkg database backup service.
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): EDID vendor "LGD", prod id 1530
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): Printing DDC gathered Modelines:
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): Modeline "1920x1080"x0.0 138.70 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): Modeline "1920x1080"x0.0 114.46 1920 1968 2000 2164 1080 1083 1088 1102 +hsync -vsync (52.9 kHz e)
Jun 25 20:08:48 t14 gnome-shell: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b).
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): EDID vendor "LGD", prod id 1530
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): Printing DDC gathered Modelines:
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): Modeline "1920x1080"x0.0 138.70 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): Modeline "1920x1080"x0.0 114.46 1920 1968 2000 2164 1080 1083 1088 1102 +hsync -vsync (52.9 kHz e)
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): EDID vendor "LGD", prod id 1530
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): Printing DDC gathered Modelines:
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): Modeline "1920x1080"x0.0 138.70 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.7 kHz eP)
Jun 25 20:08:48 t14 /usr/libexec/gdm-x-session: (II) AMDGPU(0): Modeline "1920x1080"x0.0 114.46 1920 1968 2000 2164 1080 1083 1088 1102 +hsync -vsync (52.9 kHz e)
Jun 25 20:08:48 t14 systemd: Starting Fingerprint Authentication Daemon...
Jun 25 20:08:48 t14 gnome-shell: Window manager warning: Overwriting existing binding of keysym ff61 with keysym ff61 (keycode 6b).
Jun 25 20:08:48 t14 rfkill: unblock set for type bluetooth
Jun 25 20:08:48 t14 systemd: systemd-suspend.service: Deactivated successfully.
Jun 25 20:08:48 t14 systemd: Finished System Suspend.
Jun 25 20:08:48 t14 systemd: Stopped target Sleep.
Jun 25 20:08:48 t14 systemd: Reached target Suspend.
Jun 25 20:08:48 t14 systemd-logind: Operation 'sleep' finished.
whitenoisedb
(183 rep)
Jun 25, 2025, 11:47 PM
2
votes
1
answers
5485
views
Video card driver problem in Debian (AMD Radeon R5 M330)
I am new to Linux. I am using Debian 8. I tried to play some games, but it seems that they are using my integrated Intel video card instead of discrete AMD Radeon: Star Conflict doesn't even show the space - everything is completely black (I can only see ship's interface components). Games with much...
I am new to Linux. I am using Debian 8. I tried to play some games, but it seems that they are using my integrated Intel video card instead of discrete AMD Radeon: Star Conflict doesn't even show the space - everything is completely black (I can only see ship's interface components). Games with much less requirements can produce the image but they are running very slow even on low graphics settings. On the same laptop on Windows side I can play Bioshock Infinite on high settings very well. So, it seems to be linux driver's fault. I have some program called "ATI Catalyst Control Center Linux edition" in my gnome menu and when I try to run it, I get this message:
There was a problem initializing Catalyst Control Center Linux edition. It could be caused by the following.
No AMD graphics driver is installed, or the AMD driver is not functioning properly.
Please install the AMD driver appropriate for you AMD hardware, or configure using aticonfig
I tried installing AMD proprietary driver, but it fails to install.
So, I'd like to use open-source driver, it doesn't really matter, I just want to get my graphics card working.
Output of
lspci | grep 'AMD'
:
0d:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] (rev ff)
I am also curios why it says "Display controller" instead of "VGA compatible controller" like it says about Intel's integrated card.
So, the final question is:
What software/driver should I install or how should I configure my system to get my discrete card working?
I am sorry if I gave not enough info - I just don't know what information is needed here. I would like to provide any info you ask.
Alexandr Gnatyuk
(103 rep)
Oct 10, 2016, 10:09 PM
• Last activity: Jun 25, 2025, 09:05 AM
1
votes
1
answers
3127
views
AMD GPU not being used by Debian
I'm running Debian 10 with kernel 5.10 via buster backports. The installed driver for amd is amdgpu and the output of ```dmesg``` from my understanding tells me the driver is being recognized, ``` [ 2.774224] [drm] amdgpu kernel modesetting enabled. [ 2.774409] amdgpu: Topology: Add CPU node [ 2.774...
I'm running Debian 10 with kernel 5.10 via buster backports. The installed driver for amd is amdgpu and the output of
from my understanding tells me the driver is being
recognized,
[ 2.774224] [drm] amdgpu kernel modesetting enabled.
[ 2.774409] amdgpu: Topology: Add CPU node
[ 2.774596] amdgpu 0000:03:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported
[ 2.792960] amdgpu 0000:03:00.0: amdgpu: Fetched VBIOS from ATRM
[ 2.792962] amdgpu: ATOM BIOS: BR64533.001
[ 2.811910] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_k_mc.bin
[ 2.811918] amdgpu 0000:03:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
[ 2.811919] amdgpu 0000:03:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF
[ 2.811996] [drm] amdgpu: 2048M of VRAM memory ready
[ 2.811997] [drm] amdgpu: 3072M of GTT memory ready.
[ 2.812695] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_pfp_2.bin
[ 2.812704] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_me_2.bin
[ 2.812712] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_ce_2.bin
[ 2.812721] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_rlc.bin
[ 2.812776] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_mec_2.bin
[ 2.812832] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_mec2_2.bin
[ 2.813340] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_sdma.bin
[ 2.813348] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_sdma1.bin
[ 2.813383] amdgpu: hwmgr_sw_init smu backed is polaris10_smu
[ 2.813465] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_uvd.bin
[ 2.814530] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_vce.bin
[ 2.815130] amdgpu 0000:03:00.0: firmware: direct-loading firmware amdgpu/polaris12_k_smc.bin
[ 3.051566] amdgpu 0000:03:00.0: amdgpu: SE 2, SH per SE 1, CU per SH 5, active_cu_number 10
[ 3.055642] [drm] Initialized amdgpu 3.40.0 20150101 for 0000:03:00.0 on minor 1
and -c video
shows both the integrated and dedicated GPU
*-display
description: VGA compatible controller
product: Intel Corporation
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 02
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:130 memory:c1000000-c1ffffff memory:a0000000-afffffff ioport:4000(size=64) memory:c0000-dffff
*-display
description: Display controller
product: Advanced Micro Devices, Inc. [AMD/ATI]
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 0
bus info: pci@0000:03:00.0
version: c0
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi bus_master cap_list rom
configuration: driver=amdgpu latency=0
resources: irq:131 memory:b0000000-bfffffff memory:c0000000-c01fffff ioport:3000(size=256) memory:c2300000-c233ffff memory:c2340000-c235ffff
However when I run -B
or DRI_PRIME=1 glxinfo -B
the output is
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: VMware, Inc. (0xffffffff)
Device: llvmpipe (LLVM 7.0, 256 bits) (0xffffffff)
Version: 18.3.6
Accelerated: no
Video memory: 15817MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES profile version: 3.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 7.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.3.6
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 3.1 Mesa 18.3.6
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.3.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
I have tried running programs that could use the GPU as well but they seem to keep using the VMWare llvmpipe gpu, the output of
always shows up as 0%. How do I get my machine to use amdgpu?
PC-02
(11 rep)
Jun 11, 2021, 06:32 PM
• Last activity: Jun 20, 2025, 06:03 PM
0
votes
1
answers
4943
views
radeon failed vce resume after upgrade to newest Linux kernel
I have upgraded my Debian to latest version on the kernel version 3.16.0-4-amd64. Update went fine. After that I decided to upgrade linux kernel version to the latest one supported by Debian 10 - 4.19.0-5-amd64. After reboot my X-server didn't get up and in logs when system starting I see an error l...
I have upgraded my Debian to latest version on the kernel version 3.16.0-4-amd64. Update went fine. After that I decided to upgrade linux kernel version to the latest one supported by Debian 10 - 4.19.0-5-amd64. After reboot my X-server didn't get up and in logs when system starting I see an error like that
radeon 0000:01:00.0 failed VCE resume (-110)
Laptom model: Samsung 300E5V/300E4EV/270E5EV/270E4EV/2470EV/2470EE
After sysmtem start I get in command line interface. When try to execute startx
I see then same error about radeon and message from x-server:

$lspci | grep VGA
radeon failed VCE resume (-110)
VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller(rev 09)
Here is ls -pci
[log](https://pastebin.com/3SUh0zXM) and [log](https://pastebin.com/jS66q0GC) from Xorg.0.log file.
Could you help me please fix an issue and get my desktop up again?
slesh
(121 rep)
Aug 4, 2019, 05:34 PM
• Last activity: May 30, 2025, 06:10 AM
1
votes
1
answers
2150
views
Cannot overclock AMD GPU on Ubuntu 18.04 LTS
I am trying to overclock the memory on my GPU with AMDGPU Pro 18.40 driver. Nonetheless, `/sys/class/drm/card0/device/pp_od_clk_voltage` is an empty file and I cannot write to it. When I try echo "m 2 1600 950" > /sys/class/drm/card0/device/pp_od_clk_voltage as root it produces the following error:...
I am trying to overclock the memory on my GPU with AMDGPU Pro 18.40 driver.
Nonetheless,
/sys/class/drm/card0/device/pp_od_clk_voltage
is an empty file and I cannot write to it.
When I try
echo "m 2 1600 950" > /sys/class/drm/card0/device/pp_od_clk_voltage
as root it produces the following error:
-bash: echo: write error: Invalid argument
I have amdgpu.ppfeaturemask=0xffffffff
in GRUB_CMDLINE_LINUX_DEFAULT
in /etc/default/grub
.
I have also tried running:
echo manual | sudo tee /sys/class/drm/card0/device/power_dpm_force_performance_level
My question is based on the answer to the following question: https://unix.stackexchange.com/questions/404780/cant-overclock-gpu-using-amdgpu-driver-on-archlinux
The author claims that this method works, however it obviously does not.
user325562
Dec 12, 2018, 04:17 PM
• Last activity: May 11, 2025, 10:02 AM
2
votes
1
answers
358
views
How to make `ffmpeg` use GPU mostly for reducing file sizes?
I'm on `Debian 12` & I'm using a `ryzen 5600H with integrated graphics + Nvidia 1650` setup & I'm running the following command ```sh ffmpeg -y -hwaccel cuda -i input.mp4 -vcodec libx264 -crf 24 output.mp4 ``` But this mostly uses `CPU`, as I can see all of the `12` threads are getting to `100%` and...
I'm on
Debian 12
& I'm using a ryzen 5600H with integrated graphics + Nvidia 1650
setup & I'm running the following command
ffmpeg -y -hwaccel cuda -i input.mp4 -vcodec libx264 -crf 24 output.mp4
But this mostly uses CPU
, as I can see all of the 12
threads are getting to 100%
and bloating other tasks. How can I make ffmpeg
use my NVIDIA GPU
mostly for this task?
I have searched through various posts before, but they all seemed to be very outdated, and the ones I was able to make work destroyed the quality.
Saikat Karmakar
(123 rep)
May 1, 2025, 08:24 AM
• Last activity: May 4, 2025, 10:50 AM
0
votes
0
answers
107
views
Display freeze with Debian/Lenovo t14
I'm experiencing a regular occurring issue. After start up into the xfce Desktop everything runs well. Then suddenly, both display freeze and go black. After a few seconds sometimes the xfce session comes back as before the freeze, sometimes the session stops completely and I have to log on again. I...
I'm experiencing a regular occurring issue.
After start up into the xfce Desktop everything runs well. Then suddenly, both display freeze and go black.
After a few seconds sometimes the xfce session comes back as before the freeze, sometimes the session stops completely and I have to log on again.
I check the log files with the following command
# sudo journalctl -S 2025-01-28
and get the following out put at the time of the "blackout" (shortend)
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=10171, emitted seq=10173
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process chromium pid 2494 thread chromium:cs0 pid 2523
amdgpu 0000:64:00.0: amdgpu: GPU reset begin!
[drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:67:crtc-0] hw_done or flip_done timed out
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
[drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
[drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
I would like to know how to stop this freezing of the displays.
- Notebook: Lenovo T14 Gen 4
- CPU: AMD Ryzen 5 PRO 7540U
- GPU: Radeon 740M Graphics
- Dockingstation: Universal USB Dock V2
- OS: Debian 12,freshly updated
- kernel: 6.1.0-28-amd64
sake
(1 rep)
Jan 28, 2025, 10:16 AM
1
votes
0
answers
85
views
When does Unified Memory Access (UMA) grow with demand?
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 ga...
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
AlexLoss
(183 rep)
Jan 27, 2025, 10:56 AM
• Last activity: Jan 27, 2025, 12:51 PM
5
votes
3
answers
6017
views
How can I list AMDGPU VRAM usage by process?
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'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.
Atemu
(857 rep)
Jan 24, 2022, 08:37 PM
• Last activity: Jan 26, 2025, 10:46 AM
0
votes
0
answers
169
views
How to overclock an AMD APU
I'm trying to overclock a Lenovo IdeaPad 5 15ALC05 with an AMD Ryzen 7 5700U, since it maxes out at less than 70, but usually closer to 60°C without using any external cooling. Now I know that it's possible, since it's worked on Windows using MSI Afterburner & Universal x86 Tuning Utility (at t...
I'm trying to overclock a Lenovo IdeaPad 5 15ALC05 with an AMD Ryzen 7 5700U, since it maxes out at less than 70, but usually closer to 60°C without using any external cooling. Now I know that it's possible, since it's worked on Windows using MSI Afterburner & Universal x86 Tuning Utility (at the very least it let me change the values I didn't actually test if it changed something), but I can't get it to work on Linux (Fedora 41).
I checked the BIOS, which doesn't seem to have an option for overclocking or adjusting fan speed as far as I can tell. Then I tried CoreCtrl , LACT , which both just gave me the option to choose between presets without being able to manually adjust values, and lastly amdgpu-clocks which doesn't work as
/sys/class/drm/card1/device/pp_od_clk_voltage
is just an empty file.
So I consulted the arch wiki where I noticed that for one, commands like echo "r" > /sys/class/drm/card1/device/pp_od_clk_voltage
don't work, as pp_od_clk_voltage is an empty file, but more curiously I noticed that cat /sys/kernel/debug/dri/1/amdgpu_pm_info
has the following output:
GFX Clocks and Power:
1200 MHz (MCLK)
400 MHz (SCLK)
0 MHz (PSTATE_SCLK)
0 MHz (PSTATE_MCLK)
1306 mV (VDDGFX)
743 mV (VDDNB)
7.00 W (current SoC including CPU)
GPU Temperature: 48 C
GPU Load: 6 %
SMC Feature Mask: 0xffffffffffffffff
VCN: Powered down
Clock Gating Flags Mask: 0x30bc944f
Graphics Fine Grain Clock Gating: Off
Graphics Medium Grain Clock Gating: On
Graphics Medium Grain memory Light Sleep: On
Graphics Coarse Grain Clock Gating: On
Graphics Coarse Grain memory Light Sleep: On
Graphics Coarse Grain Tree Shader Clock Gating: Off
Graphics Coarse Grain Tree Shader Light Sleep: Off
Graphics Command Processor Light Sleep: On
Graphics Run List Controller Light Sleep: Off
Graphics 3D Coarse Grain Clock Gating: On
Graphics 3D Coarse Grain memory Light Sleep: On
Memory Controller Light Sleep: Off
Memory Controller Medium Grain Clock Gating: Off
System Direct Memory Access Light Sleep: On
System Direct Memory Access Medium Grain Clock Gating: Off
Bus Interface Medium Grain Clock Gating: On
Bus Interface Light Sleep: On
Unified Video Decoder Medium Grain Clock Gating: Off
Video Compression Engine Medium Grain Clock Gating: Off
Host Data Path Light Sleep: On
Host Data Path Medium Grain Clock Gating: Off
Digital Right Management Medium Grain Clock Gating: Off
Digital Right Management Light Sleep: On
Rom Medium Grain Clock Gating: Off
Data Fabric Medium Grain Clock Gating: On
VCN Medium Grain Clock Gating: Off
Host Data Path Deep Sleep: Off
Host Data Path Shutdown: Off
Interrupt Handler Clock Gating: Off
JPEG Medium Grain Clock Gating: Off
Repeater Fine Grain Clock Gating: Off
Perfmon Clock Gating: Off
Address Translation Hub Medium Grain Clock Gating: On
Address Translation Hub Light Sleep: On
For some reason, PSTATE_SCLK and PSTATE_MCLK both display 0 MHz, but I don't think they should do that.
And lastly, /sys/class/drm/card1/device/hwmon/hwmon3/power1_cap
also doesn't exist.
At this point, I'm beyond confused, but I also don't want to switch back to Windows. Any advice on how to enable overclocking?
I_racso_I
(1 rep)
Jan 13, 2025, 09:33 PM
1
votes
0
answers
117
views
Asus TUF A16 AMD Laptop wakes up immediately after sleep when External Monitor is plugged in
I'm using the ASUS TUF A16 which comes with AMD Radeon RX 7700S dedicated GPU, and an integrated Radeon 680M. It manages them through a MUX switcher in the laptop, with the only option to run dedicated-gpu only on boot menu. I'm on KDE-fedora, but I have replicated the problem on multiple distros an...
I'm using the ASUS TUF A16 which comes with AMD Radeon RX 7700S dedicated GPU, and an integrated Radeon 680M. It manages them through a MUX switcher in the laptop, with the only option to run dedicated-gpu only on boot menu.
I'm on KDE-fedora, but I have replicated the problem on multiple distros and desktop environments.
The problem I'm having is that the laptop goes to sleep and immediately wakes up when my external monitor is plugged in. I've done some research and troubleshooting, and I've come to think the cause is that the external GPU restarts whenever it goes to sleep with the external monitor on, possibly related to AMD's MUX switch, but that's just speculation. I assume this is because the hdmi is run by the dgpu, and doesn't work with the igpu, but how to fix it has proven so far to be out of my league.
This is the last minute of journalctl log after suspension:
Dec 31 12:13:29 LaptopHostName systemd-logind: The system will suspend now!
Dec 31 12:13:29 LaptopHostName ModemManager: [sleep-monitor-systemd] system is about to suspend
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7223] manager: sleep: sleep requested (sleeping: no enabled: yes)
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7229] device (eno1): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7347] device (p2p-dev-wlp6s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7350] manager: NetworkManager state is now ASLEEP
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.7352] device (wlp6s0): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Dec 31 12:13:29 LaptopHostName kded6: org.kde.plasma.nm.kded: Unhandled active connection state change: 3
Dec 31 12:13:29 LaptopHostName systemd: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service...
░░ Subject: A start job for unit NetworkManager-dispatcher.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit NetworkManager-dispatcher.service has begun execution.
░░
░░ The job identifier is 13845.
Dec 31 12:13:29 LaptopHostName systemd: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service.
░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit NetworkManager-dispatcher.service has finished successfully.
░░
░░ The job identifier is 13845.
Dec 31 12:13:29 LaptopHostName audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 31 12:13:29 LaptopHostName kernel: wlp6s0: deauthenticating from 58:ae:f1:59:cf:cc by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 31 12:13:29 LaptopHostName wpa_supplicant: nl80211: send_event_marker failed: Source based routing not supported
Dec 31 12:13:29 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-DISCONNECTED bssid=58:ae:f1:59:cf:cc reason=3 locally_generated=1
Dec 31 12:13:29 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 31 12:13:29 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9105] device (wlp6s0): supplicant interface state: completed -> disconnected
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9107] device (wlp6s0): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Dec 31 12:13:29 LaptopHostName avahi-daemon: Withdrawing address record for fe80::55c1:d249:2295:4446 on wlp6s0.
Dec 31 12:13:29 LaptopHostName avahi-daemon: Leaving mDNS multicast group on interface wlp6s0.IPv6 with address fe80::55c1:d249:2295:4446.
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9114] dhcp4 (wlp6s0): canceled DHCP transaction
Dec 31 12:13:29 LaptopHostName avahi-daemon: Interface wlp6s0.IPv6 no longer relevant for mDNS.
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9114] dhcp4 (wlp6s0): activation: beginning transaction (timeout in 45 seconds)
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9114] dhcp4 (wlp6s0): state changed no lease
Dec 31 12:13:29 LaptopHostName audit: NETFILTER_CFG table=firewalld:51 family=1 entries=34 op=nft_unregister_rule pid=2027 subj=system_u:system_r:firewalld_t:s0 comm="firewalld"
Dec 31 12:13:29 LaptopHostName audit: SYSCALL arch=c000003e syscall=46 success=yes exit=2680 a0=6 a1=7fffc43f33f0 a2=0 a3=7fffc43f3560 items=0 ppid=1 pid=2027 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="firewalld" exe="/usr/bin/python3.13" subj=system_u:system_r:firewalld_t:s0 key=(null)
Dec 31 12:13:29 LaptopHostName audit: PROCTITLE proctitle=2F7573722F62696E2F707974686F6E33002D7350002F7573722F7362696E2F6669726577616C6C64002D2D6E6F666F726B002D2D6E6F706964
Dec 31 12:13:29 LaptopHostName avahi-daemon: Interface wlp6s0.IPv4 no longer relevant for mDNS.
Dec 31 12:13:29 LaptopHostName avahi-daemon: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.1.9.
Dec 31 12:13:29 LaptopHostName avahi-daemon: Withdrawing address record for 192.168.1.9 on wlp6s0.
Dec 31 12:13:29 LaptopHostName NetworkManager: [1735658009.9423] device (wlp6s0): set-hw-addr: set MAC address to 1A:DF:02:F4:56:54 (scanning)
Dec 31 12:13:29 LaptopHostName avahi-daemon: Joining mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.1.9.
Dec 31 12:13:29 LaptopHostName avahi-daemon: New relevant interface wlp6s0.IPv4 for mDNS.
Dec 31 12:13:29 LaptopHostName avahi-daemon: Registering new address record for 192.168.1.9 on wlp6s0.IPv4.
Dec 31 12:13:29 LaptopHostName avahi-daemon: Withdrawing address record for 192.168.1.9 on wlp6s0.
Dec 31 12:13:29 LaptopHostName avahi-daemon: Leaving mDNS multicast group on interface wlp6s0.IPv4 with address 192.168.1.9.
Dec 31 12:13:29 LaptopHostName avahi-daemon: Interface wlp6s0.IPv4 no longer relevant for mDNS.
Dec 31 12:13:29 LaptopHostName systemd-resolved: wlp6s0: Bus client set default route setting: no
Dec 31 12:13:29 LaptopHostName systemd-resolved: wlp6s0: Bus client reset DNS server list.
Dec 31 12:13:30 LaptopHostName NetworkManager: [1735658010.0132] device (wlp6s0): supplicant interface state: disconnected -> interface_disabled
Dec 31 12:13:30 LaptopHostName NetworkManager: [1735658010.0134] device (wlp6s0): supplicant interface state: interface_disabled -> disconnected
Dec 31 12:13:30 LaptopHostName NetworkManager: [1735658010.0136] device (wlp6s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Dec 31 12:13:30 LaptopHostName chronyd: Source 216.238.106.159 offline
Dec 31 12:13:30 LaptopHostName chronyd: Source 143.107.229.210 offline
Dec 31 12:13:30 LaptopHostName chronyd: Source 200.160.7.197 offline
Dec 31 12:13:30 LaptopHostName chronyd: Can't synchronise: no selectable sources
Dec 31 12:13:30 LaptopHostName chronyd: Source 200.160.7.193 offline
Dec 31 12:13:30 LaptopHostName NetworkManager: [1735658010.0599] device (wlp6s0): set-hw-addr: reset MAC address to 94:BB:43:74:7D:0D (unmanage)
Dec 31 12:13:30 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 31 12:13:30 LaptopHostName systemd: Reached target sleep.target - Sleep.
░░ Subject: A start job for unit sleep.target has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit sleep.target has finished successfully.
░░
░░ The job identifier is 14007.
Dec 31 12:13:30 LaptopHostName systemd: Starting systemd-suspend.service - System Suspend...
░░ Subject: A start job for unit systemd-suspend.service has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-suspend.service has begun execution.
░░
░░ The job identifier is 14004.
Dec 31 12:13:30 LaptopHostName wpa_supplicant: wlp6s0: CTRL-EVENT-DSCP-POLICY clear_all
Dec 31 12:13:30 LaptopHostName wpa_supplicant: nl80211: deinit ifname=wlp6s0 disabled_11b_rates=0
Dec 31 12:13:30 LaptopHostName systemd-sleep: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Dec 31 12:13:30 LaptopHostName systemd-sleep: This is not recommended, and might result in unexpected behavior, particularly
Dec 31 12:13:30 LaptopHostName systemd-sleep: in suspend-then-hibernate operations or setups with encrypted home directories.
Dec 31 12:13:30 LaptopHostName systemd-sleep: Performing sleep operation 'suspend'...
░░ Subject: System sleep state suspend entered
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The system has now entered the suspend sleep state.
Dec 31 12:13:30 LaptopHostName kernel: PM: suspend entry (s2idle)
Dec 31 12:13:30 LaptopHostName kernel: Filesystems sync: 0.032 seconds
Dec 31 12:13:32 LaptopHostName kernel: Freezing user space processes
Dec 31 12:13:32 LaptopHostName kernel: Freezing user space processes completed (elapsed 0.003 seconds)
Dec 31 12:13:32 LaptopHostName kernel: OOM killer disabled.
Dec 31 12:13:32 LaptopHostName kernel: Freezing remaining freezable tasks
Dec 31 12:13:32 LaptopHostName kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Dec 31 12:13:32 LaptopHostName kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Dec 31 12:13:32 LaptopHostName kernel: queueing ieee80211 work while going to suspend
Dec 31 12:13:32 LaptopHostName kernel: PM: suspend devices took 0.282 seconds
Dec 31 12:13:32 LaptopHostName kernel: [drm] PCIE GART of 1024M enabled (table at 0x000000F41FC00000).
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: SMU is resuming...
Dec 31 12:13:32 LaptopHostName kernel: [drm] PCIE GART of 512M enabled (table at 0x00000081FEB00000).
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: PSP is resuming...
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: SMU is resumed successfully!
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring gfx_0.1.0 uses VM inv eng 1 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 4 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 5 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 12 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring sdma0 uses VM inv eng 13 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 8
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv eng 1 on hub 8
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv eng 4 on hub 8
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:77:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
Dec 31 12:13:32 LaptopHostName kernel: nvme nvme0: 16/0/0 default/read/poll queues
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: reserve 0x1300000 from 0x81fc000000 for PSP TMR
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: RAS: optional ras ta ucode is not available
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x00000035, smu fw if version = 0x00000040, smu fw program = 0, smu fw version = 0x00525c00 (82.92.0)
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
Dec 31 12:13:32 LaptopHostName kernel: usb 9-1: reset full-speed USB device number 7 using xhci_hcd
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
Dec 31 12:13:32 LaptopHostName kernel: [drm] DMUB hardware initialized: version=0x07002A00
Dec 31 12:13:32 LaptopHostName kernel: usb 9-1: PM: dpm_run_callback(): usb_dev_resume returns -5
Dec 31 12:13:32 LaptopHostName kernel: usb 9-1: PM: failed to resume async: error -5
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Dec 31 12:13:32 LaptopHostName kernel: amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
Dec 31 12:13:32 LaptopHostName kernel: [drm] ring gfx_32823.1.1 was added
Dec 31 12:13:32 LaptopHostName kernel: [drm] ring compute_32823.2.2 was added
Dec 31 12:13:32 LaptopHostName kernel: [drm] ring sdma_32823.3.3 was added
Dec 31 12:13:32 LaptopHostName kernel: [drm] ring gfx_32823.1.1 ib test pass
Dec 31 12:13:32 LaptopHostName kernel: [drm] ring compute_32823.2.2 ib test pass
Dec 31 12:13:32 LaptopHostName kernel: [drm] ring sdma_32823.3.3 ib test pass
Dec 31 12:13:32 LaptopHostName kernel: PM: resume devices took 1.520 seconds
Dec 31 12:13:32 LaptopHostName kernel: OOM killer enabled.
Dec 31 12:13:32 LaptopHostName kernel: Restarting tasks ...
Dec 31 12:13:32 LaptopHostName kernel: usb 9-1: USB disconnect, device number 7
Dec 31 12:13:32 LaptopHostName kernel: done.
Dec 31 12:13:32 LaptopHostName kernel: random: crng reseeded on system resumption
Dec 31 12:13:32 LaptopHostName kernel: PM: suspend exit
Dec 31 12:13:32 LaptopHostName audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 31 12:13:32 LaptopHostName plasmashell: org.kde.pulseaudio: No object for name "alsa_output.usb-ACTIONS_Pebble_V3-00.analog-stereo"
Dec 31 12:13:32 LaptopHostName audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-suspend comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 31 12:13:32 LaptopHostName bluetoothd: Controller resume with wake event 0x0
Dec 31 12:13:32 LaptopHostName kded6: org.kde.pulseaudio: No object for name "alsa_output.usb-ACTIONS_Pebble_V3-00.analog-stereo"
Dec 31 12:13:32 LaptopHostName systemd-sleep: System returned from sleep operation 'suspend'.
░░ Subject: System sleep state suspend left
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The system has now left the suspend sleep state.
Dec 31 12:13:32 LaptopHostName systemd: systemd-suspend.service: Deactivated successfully.
I also came across a python script which helps identify sleep problems, and this is the result (I'm gonna cut to the main line as the log is full of emojis and I want to spare you that):
> 2024-12-31 12:25:21,494 INFO: Suspend count: 1
> 2024-12-31 12:25:21,494 INFO: ○ GPIOs active: ['29', '29', '29', '29', '29', '29', '29']
> 2024-12-31 12:25:21,494 INFO: Wakeup triggered from IRQ 7: GPIO Controller
> 2024-12-31 12:25:21,494 DEBUG: Used Microsoft uPEP GUID in LPS0 _DSM
> 2024-12-31 12:25:21,494 INFO: Woke up from IRQ 7: GPIO Controller
> 2024-12-31 12:25:21,495 DEBUG: ACPI Lid (/proc/acpi/button/lid/LID0/state): closed
> 2024-12-31 12:25:21,495 ERROR: ❌ Userspace suspended for 0:00:04.616088 ( 2024-12-31 12:25:21,496 ERROR: ❌ Did not reach hardware sleep state
So, I assume this has to do with the GPU, as unplugging the hdmi let's the laptop sleep, and it's triggered by IRQ 7. I have found that IRQ7 is
pinctrl_amd
, so I'm not sure it's the responsible part, as it's a general-purpose GPIO driver as far as I know. /sys/kernel/irq/7/wakeup
is enabled but I'm not sure it would be a good idea to disable it, and I have not even been able to find where to disable it for a test.
Some of the things I have tried:
- disable wakeup for the gpu drivers (only one of the cards seems to have the wakeup
file though)
- disabled everything on /proc/acpi/wakeup
- Disabled wake up capability from every device with powertop
- Tried the kernel parameters amdgpu.runpm=1
(default is 0), amdgpu.dpm=1
(-1 default), amdgpu.bapm=1
(-1 default), acpi.ec_no_wakeup=1
(default 0)
altz3r0
(11 rep)
Jan 2, 2025, 05:56 PM
• Last activity: Jan 2, 2025, 06:44 PM
0
votes
0
answers
120
views
Prevent binding an iGPU to the host OS to use it later as PCI passthrough to a VM
I have an AMD iGPU (integrated in an AMD Ryzen 9 9950x CPU) that I want to use as the video output for a Windows VM in proxmox (I have no other GPU installed). I discovered that it doesn't have the Function Level Reset capability, so from my understanding I can't unbind it from the host OS and rebin...
I have an AMD iGPU (integrated in an AMD Ryzen 9 9950x CPU) that I want to use as the video output for a Windows VM in proxmox (I have no other GPU installed). I discovered that it doesn't have the Function Level Reset capability, so from my understanding I can't unbind it from the host OS and rebind it to the VM. I tried using vendor-reset, but it is not compatible with my iGPU. Then, I tried to prevent the iGPU from ever being initialised by the host OS, by blacklisting my GPU drivers (amdgpu and radeon) by creating a config file in
/etc/modprobe.d/
that looks like this:
blacklist amdgpu
blacklist radeon
blacklist vgaarb
blacklist efifb
blacklist vesafb
install amdgpu /bin/false
install radeon /bin/false
install vgaarb /bin/false
I tried to specify every possible restriction on any frame buffer or GPU driver, as well as giving full control of the GPU to the vfio driver. I hoped this would prevent any part of the OS from ever touching the iGPU, but vgaarb still sets it as the boot VGA device, only to deactivate it afterwards, as displayed by dmesg:
[ 0.472763] pci 0000:72:00.0: vgaarb: setting as boot VGA device
[ 0.472763] pci 0000:72:00.0: vgaarb: bridge control possible
[ 0.472763] pci 0000:72:00.0: vgaarb: VGA device added: decodes=io+mem,owns=none,locks=none
[ 0.490408] pci 0000:72:00.1: D0 power state depends on 0000:72:00.0
[ 0.491001] pci 0000:72:00.0: Adding to iommu group 35
[ 2.052946] vfio-pci 0000:72:00.0: vgaarb: deactivate vga console
My full kernel command line (as displayed by dmesg) is:
BOOT_IMAGE=/vmlinuz-6.8.12-5-pve root=ZFS=/ROOT/pve-1 ro root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet amd_iommu=on iommu=pt nofb pcie_aspm=off nomodeset video=vesafb:off video=efifb:off video=vesa:off video=simplefb:off disable_vga=1 vga=none vgaarb=off video=off vfio-pci.ids=1002:13c0,1002:1640 vfio-pci.disable_vga=1 initcall_blacklist=sysfb_init,amd_iommu_v2_init modprobe.blacklist=amdgpu,radeon,snd_hda_intel,r8169 module_blacklist=amdgpu,radeon vgaarb.multi_gpu_switch=0 video.ignore_edd=1 vfio_iommu_type1.allow_unsafe_interrupts=1 kvm.ignore_msrs=1 rd.driver.blacklist=amdgpu rd.driver.blacklist=radeon rd.driver.pre=vfio-pci pcie_acs_override=downstream,multifunction radeon.modeset=0 amdgpu.modeset=0 amdgpu.aspm=0
I can confirm that in the end the GPU uses vfio as its driver, but it already has been initialised by the host OS and starting the VM returns the error is already attached
The output of -nnk
:
72:00.0 VGA compatible controller : Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:13c0] (rev c1)
Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
Kernel driver in use: vfio-pci
Kernel modules: amdgpu
The VM's configuration file:
bios: ovmf
boot: order=ide2;net0
cores: 8
cpu: host
efidisk0: local-zfs:vm-100-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
hostpci0: 0000:72:00,pcie=1,x-vga=1
ide2: local:iso/windows-11.iso,media=cdrom,size=5695402K
machine: pc-q35-9.0
memory: 16384
meta: creation-qemu=9.0.2,ctime=1733853637
name: windows11
net0: virtio=BC:24:11:2B:1A:A2,bridge=vmbr0,firewall=1
numa: 0
ostype: win11
scsi0: local-zfs:vm-100-disk-1,aio=native,iothread=1,size=128G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=e73054d1-f03b-4b84-8cdc-9115d85676fa
sockets: 1
tpmstate0: local-zfs:vm-100-disk-2,size=4M,version=v2.0
vmgenid: e16f7ba2-2469-4495-ab4f-7480c7f89041
args: -device vfio-pci,host=72:00.0,multifunction=on,x-vga=on,rombar=0 -device vfio-pci,host=72:00.1
What else could I try? Thank you in advance!
CiprianC
(1 rep)
Dec 25, 2024, 12:14 PM
0
votes
0
answers
270
views
Drivers for AMD FirePro D700 in Ubuntu 24
I've got an old Mac Pro 6,1 at home running Ubuntu 24. Its got a pair of AMD FirePro D700's inside (The Apple exclusive GPU ones). I've tried installing AMD drivers for it but Ubuntu still says its using software rendering not hardware rendering. I'm not sure if the current AMD drivers support the D...
I've got an old Mac Pro 6,1 at home running Ubuntu 24. Its got a pair of AMD FirePro D700's inside (The Apple exclusive GPU ones). I've tried installing AMD drivers for it but Ubuntu still says its using software rendering not hardware rendering. I'm not sure if the current AMD drivers support the D700s. Does anyone know if there are drivers for these available?
Jobalisk
(101 rep)
Dec 13, 2024, 10:00 PM
0
votes
1
answers
500
views
How to upgrade video drivers on Debian stable?
I'm having some problems with my video driver on Debian stable. For some reason I cannot use testing. Don't know why, it was a while ago since I tried, but the computer basically does not start when using testing. So if possible, I'd like to upgrade only the video drivers. Since I have a Radeon RX 7...
I'm having some problems with my video driver on Debian stable. For some reason I cannot use testing. Don't know why, it was a while ago since I tried, but the computer basically does not start when using testing.
So if possible, I'd like to upgrade only the video drivers. Since I have a Radeon RX 7700S, I assume that means a kernel upgrade?
But how do I do it?
klutt
(566 rep)
Aug 17, 2024, 09:18 PM
• Last activity: Aug 18, 2024, 07:13 AM
1
votes
0
answers
123
views
MCLK locked to 1000MHz idle, resolution investigation
A few months ago, I became interested in Linux and decided to install it. I went with a dual boot setup (on a separate drive) using Arch Linux. Everything was going okay until I noticed my RX 6700 XT VRAM clock was always at maximum frequency, even when idle. Maybe the problem is related to the high...
A few months ago, I became interested in Linux and decided to install it. I went with a dual boot setup (on a separate drive) using Arch Linux. Everything was going okay until I noticed my RX 6700 XT VRAM clock was always at maximum frequency, even when idle. Maybe the problem is related to the high refresh rate? Using the trial-and-error method, I discovered that every resolution above 152Hz locks the MCLK (memory clock) to its maximum value of 1000MHz (or 2000MHz effective). However, I'm running an identical configuration—1080p 165Hz—on Windows too, and it works flawlessly there, so what's the problem?
In trying to find an answer, I was able to narrow it down to X11 (i3, DWM, KDE X11 were affected, whereas KDE Wayland was unaffected). The next step was to download CRU on Windows, write down the active detailed resolution, and compare it to the result of xrandr --verbose. Both resolutions were identical:
.96 1920 1968 2032 2080 1080 1083 1088 1110 -hsync +vsync
That truly left me confused: why does a resolution that works flawlessly on Windows become problematic on Linux? After more searching, I was able to find an answer: It turns out the problem is with "blanking," and Linux doesn't like resolutions outside of VESA Coordinated Video Timings (CVT) (I'm still not sure why that's the case). Plugging 1080p 165Hz into a CVT calculator resulted in the following resolution:
.53 1920 2088 2296 2672 1080 1083 1089 1192 -hsync +vsync
But setting this resolution only resulted in a black screen. Then I tried the CVT "revision" CVT-RB, and I got this resolution:
.21 1920 1968 2000 2080 1080 1083 1088 1169 +hsync -vsync
This time it worked, and my MCLK dropped to 96MHz. At first, it seemed like a success, but I quickly started experiencing problems with it: each reboot is a gamble. It either works correctly, the screen displays, or I'm met with an "Out of Range" message, or—most commonly—the screen is blurred and divided into out-of-order fragments (image ://i.sstatic.net/xFJlBR6i.jpg
). Turing monitor on or off can sometimes fix the problem, but it's just a gamble - sometimes problem comes back when screensaver turns screen off and I move mouse it wake it.
Finally, I tried CVT-RB2 resolution:
.77 1920 1928 1960 2000 1080 1155 1063 1169 +hsync -vsync
but I also got the "Out of Range" message there. I also noticed that if I plug the CVT-RB2 resolution into CRU, the refresh value becomes red at every value above 144Hz. I have no idea where to go from here.
```
A few additional details:
GPU: RX 6700 XT
Driver:
[f0x@Arch ~]$ lspci -k | grep -A 2 -E "(VGA|3D)"
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] (rev c1)
Subsystem: ASUSTeK Computer Inc. Device 05d7
Kernel driver in use: amdgpu
Distro: Linux Arch KDE/dwm X11
Edid:
Section "Monitor"
Identifier "ASUS VG249Q1A"
ModelName "ASUS VG249Q1A"
VendorName "AUS"
# Monitor Manufactured week 43 of 2021
# EDID version 1.4
# Digital Display
DisplaySize 520 290
Gamma 2.20
Option "DPMS" "true"
Horizsync 200-200
VertRefresh 48-165
# Maximum pixel clock is 600MHz
#Not giving standard mode: 1280x960, 60Hz
#Not giving standard mode: 1280x1024, 60Hz
#Not giving standard mode: 1440x900, 60Hz
#Not giving standard mode: 1152x864, 75Hz
#Not giving standard mode: 1280x720, 60Hz
#Not giving standard mode: 1680x1050, 60Hz
#Extension block found. Parsing...
Modeline "Mode 16" +hsync -vsync
Modeline "Mode 0" +hsync -vsync
Modeline "Mode 1" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
Modeline "Mode 2" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
Modeline "Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
Modeline "Mode 5" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 6" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 7" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
Modeline "Mode 8" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
Modeline "Mode 9" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Modeline "Mode 10" 54.054 1440 1472 1596 1716 480 489 495 525 -hsync -vsync
Modeline "Mode 11" 54.054 1440 1472 1596 1716 480 489 495 525 -hsync -vsync
Modeline "Mode 12" 54.000 1440 1464 1592 1728 576 581 586 625 -hsync -vsync
Modeline "Mode 13" 54.000 1440 1464 1592 1728 576 581 586 625 -hsync -vsync
Modeline "Mode 14" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
Modeline "Mode 15" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
Modeline "Mode 17" +hsync +vsync
Modeline "Mode 18" +hsync +vsync
Option "PreferredMode" "Mode 16"
EndSection
Letus252
(11 rep)
Aug 13, 2024, 06:13 PM
• Last activity: Aug 14, 2024, 01:50 AM
4
votes
1
answers
7223
views
How do I switch my Display Controller to Radeon instead of the built-in Intel graphics?
**Distro:** Pop OS 19.10 **Laptop:** HP Notebook 15-bs185tx **Graphics Card:** - AMD Radeon™ 520 Graphics (2 GB DDR3 dedicated) - Intel Corporation UHD Graphics 620 I've tried almost all the solutions available online but nothing works. Both VGA and Display Controller are running on my built-in Inte...
**Distro:** Pop OS 19.10
**Laptop:** HP Notebook 15-bs185tx
**Graphics Card:** - AMD Radeon™ 520 Graphics (2 GB DDR3 dedicated) - Intel Corporation UHD Graphics 620 I've tried almost all the solutions available online but nothing works. Both VGA and Display Controller are running on my built-in Intel graphics. I've used multiple commands including this one
**Laptop:** HP Notebook 15-bs185tx
**Graphics Card:** - AMD Radeon™ 520 Graphics (2 GB DDR3 dedicated) - Intel Corporation UHD Graphics 620 I've tried almost all the solutions available online but nothing works. Both VGA and Display Controller are running on my built-in Intel graphics. I've used multiple commands including this one
lspci -k | grep -EA3 'VGA|3D|Display'
to see my active graphics adapters. Please let me know if you have any solutions regarding the problem.
Thank you!
Evon
(60 rep)
Apr 8, 2020, 08:25 AM
• Last activity: Aug 1, 2024, 03:00 PM
Showing page 1 of 20 total questions