Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

1 votes
0 answers
20 views
No signal on VGA monitor when booting Arch Linux with RX480 GPU
I have a problem with system boot. There is no signal communication ("Input not supported") on the monitor, but only on Linux. My specs are below: * Arch Linux * GPU: MSI RX480 (DVI-D) * Adapter: DVI-D to VGA * Monitor: VGA On Windows OS with the same configuration, everything is okay. The kernel pa...
I have a problem with system boot. There is no signal communication ("Input not supported") on the monitor, but only on Linux. My specs are below: * Arch Linux * GPU: MSI RX480 (DVI-D) * Adapter: DVI-D to VGA * Monitor: VGA On Windows OS with the same configuration, everything is okay. The kernel parameter nomodeset makes the system start, but it doesn't solve the problem. I also tried the parameter amdgpu.dc=0, but it doesn't work. With the same configuration on Windows, everything is fine. So I think it's a problem with Linux.
Janusz Kruszewicz (11 rep)
Aug 2, 2025, 01:34 PM • Last activity: Aug 2, 2025, 01:44 PM
0 votes
1 answers
4866 views
How can enable iommu in AMD CPU during boot?
Motherboard info: sudo dmidecode -t baseboard | grep -B 1 Product Manufacturer: Colorful Technology And Development Co.,LTD Product Name: BATTLE-AX B450M-HD CPU info: sudo dmidecode -t processor | grep Version Version: AMD Athlon 3000G with Radeon Vega Graphics OS info: uname -a Linux debian 5.10.0-...
Motherboard info: sudo dmidecode -t baseboard | grep -B 1 Product Manufacturer: Colorful Technology And Development Co.,LTD Product Name: BATTLE-AX B450M-HD CPU info: sudo dmidecode -t processor | grep Version Version: AMD Athlon 3000G with Radeon Vega Graphics OS info: uname -a Linux debian 5.10.0-22-amd64 #1 SMP Debian 5.10.178-3 (2023-04-22) x86_64 GNU/Linux I have enabled SVM in the bios setting,and set GRUB_CMDLINE_LINUX according to: https://unix.stackexchange.com/questions/263901/kfd-error-getting-iommu-info grep 'GRUB_CMDLINE_LINUX' /etc/default/grub GRUB_CMDLINE_LINUX="quiet amd_iommu=on iommu=pt" Reboot,check booting info on iommu: sudo dmesg | grep "error" [ 4.056168] kfd kfd: error getting iommu info. is the iommu enabled? [ 4.056221] kfd kfd: device 1002:15d8 NOT added due to errors Maybe we can't enable it on AMD CPU because it is not a bug? sudo dmesg | grep -e DMAR -e IOMMU [ 1.191400] AMD-Vi: AMD IOMMUv2 functionality not available on this system - This is not a bug. I have enabled the SVM mode in my motherboard's BIOS,and sudo update-grub,the iommu issue remains after reboot. enter image description here
showkey (499 rep)
Jul 17, 2023, 01:15 AM • Last activity: Jul 24, 2025, 05:05 PM
8 votes
1 answers
710 views
Kernel shows SMT as "notsupported" for AMD 3970x
I have a Threadripper 3970x that has 32 cores and 64 threads. I installed Linux and the kernel shows SMT as being "notsupported": root@services:~# cat /sys/devices/system/cpu/smt/control notsupported Kernel version: 6.8.12-11-pve I know that SMT is supported for this CPU. I have also enabled SMT in...
I have a Threadripper 3970x that has 32 cores and 64 threads. I installed Linux and the kernel shows SMT as being "notsupported": root@services:~# cat /sys/devices/system/cpu/smt/control notsupported Kernel version: 6.8.12-11-pve I know that SMT is supported for this CPU. I have also enabled SMT in the BIOS. When I first did a lscpu I found there were vulnerabilities that disabled SMT. So I added mitigations=off to the GRUB_CMDLINE_LINUX_DEFAULT line in /etc/default/grub: GRUB_CMDLINE_LINUX_DEFAULT="quiet amd_iommu=on mitigations=off" After running update-grub and a reboot the mitigations were disabled, but SMT was still not enabled. This is the current output of lscpu showing the mitigations were disabled and still no SMT support: root@services:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 43 bits physical, 48 bits virtual Byte Order: Little Endian CPU(s): 32 On-line CPU(s) list: 0-31 Vendor ID: AuthenticAMD BIOS Vendor ID: Advanced Micro Devices, Inc. Model name: AMD Ryzen Threadripper 3970X 32-Core Processor BIOS Model name: AMD Ryzen Threadripper 3970X 32-Core Processor Unknown CPU @ 3.7GHz BIOS CPU family: 107 CPU family: 23 Model: 49 Thread(s) per core: 1 Core(s) per socket: 32 Socket(s): 1 Stepping: 0 Frequency boost: enabled CPU(s) scaling MHz: 82% CPU max MHz: 4549.1211 CPU min MHz: 2200.0000 BogoMIPS: 7399.55 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr ss e sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_t sc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 mov be popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a mis alignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfct r_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibpb stibp vmmcall fsgsbase bmi1 avx2 sme p bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm _occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd amd_ppin ara t npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pf threshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca sev s ev_es Virtualization features: Virtualization: AMD-V Caches (sum of all): L1d: 1 MiB (32 instances) L1i: 1 MiB (32 instances) L2: 16 MiB (32 instances) L3: 128 MiB (8 instances) NUMA: NUMA node(s): 1 NUMA node0 CPU(s): 0-31 Vulnerabilities: Gather data sampling: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Reg file data sampling: Not affected Retbleed: Vulnerable Spec rstack overflow: Vulnerable Spec store bypass: Vulnerable Spectre v1: Vulnerable: __user pointer sanitization and usercopy barriers only; no swapgs barriers Spectre v2: Vulnerable; IBPB: disabled; STIBP: disabled; PBRSB-eIBRS: Not affected; BHI: Not affected Srbds: Not affected Tsx async abort: Not affected When I run dmidecode this is the output for the cpu section: Processor Information Socket Designation: SP3r2 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 10 0F 83 00 FF FB 8B 17 Signature: Family 23, Model 49, Stepping 0 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size extension) CLFSH (CLFLUSH instruction supported) MMX (MMX technology supported) FXSR (FXSAVE and FXSTOR instructions supported) SSE (Streaming SIMD extensions) SSE2 (Streaming SIMD extensions 2) HTT (Multi-threading) Version: AMD Ryzen Threadripper 3970X 32-Core Processor Voltage: 1.1 V External Clock: 100 MHz Max Speed: 4550 MHz Current Speed: 3700 MHz Status: Populated, Enabled Upgrade: Socket SP3r2 L1 Cache Handle: 0x001A L2 Cache Handle: 0x001B L3 Cache Handle: 0x001C Serial Number: Unknown Asset Tag: Unknown Part Number: Unknown Core Count: 32 Core Enabled: 32 Thread Count: 64 Characteristics: 64-bit capable Multi-Core Hardware Thread Execute Protection Enhanced Virtualization Power/Performance Control So dmidecode shows that the CPU is capable of hyperthreading, I just can't figure out how to enable it. Why would SMT be marked as "notsupported" and, if possible, how can I enable it?
JackCarmichael (181 rep)
Jun 22, 2025, 10:55 PM • Last activity: Jun 26, 2025, 06:25 PM
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
0 answers
143 views
Ubuntu 22.04 install.iso and other VMs won't start in VirtualBox
I have not had this problem before with VirtualBox so I thought I would share and hope for some answers. UPDATE: The VMs are working fine on QEMU/KVM. When loading Ubuntuy 22.04 install .iso or the Kali Linux "prepared" VirtualBox VM (.vbox) image, VirtualBox just shows some boot-up text on the scre...
I have not had this problem before with VirtualBox so I thought I would share and hope for some answers. UPDATE: The VMs are working fine on QEMU/KVM. When loading Ubuntuy 22.04 install .iso or the Kali Linux "prepared" VirtualBox VM (.vbox) image, VirtualBox just shows some boot-up text on the screen and never loads (see image below). The screen content is the same between both virtual machines (Ubuntu .iso and prepared Kali .vbox). I don't see any errors in the vbox.log files and ran them through ChatGPT which also didn't identify any errors. The host is Ubuntu 22.04 with full updates and upgrades. The most recent Virtualbox 7 is installed downloaded from the Oracle website along with Extension Pack. After installing VirtualBox, I did updates and upgrades again, and rebooted. enter image description here The graphics card is AMD Radeon 780M. I installed the [AMD Radeon drivers](https://www.amd.com/en/support/linux-drivers) for the base system Ubuntu 22.04 with no problems. Both VMs were configured with 128 MB of memory for graphics. This happens when using "Safe Graphics" install method for Ubuntu. Curiously, the Kali preconfigured VM loads custom Kali GRUB, then after selecting the OS to boot, fails with the screen above. Here is the output of lscpu, AMD Ryzen 7. Virtualization is enabled in the BIOS.
$ lscpu
Architecture:            x86_64
  CPU op-mode(s):        32-bit, 64-bit
  Address sizes:         48 bits physical, 48 bits virtual
  Byte Order:            Little Endian
CPU(s):                  16
  On-line CPU(s) list:   0-15
Vendor ID:               AuthenticAMD
  Model name:            AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
    CPU family:          25
    Model:               116
    Thread(s) per core:  2
    Core(s) per socket:  8
    Socket(s):           1
    Stepping:            1
    CPU max MHz:         6080.0000
    CPU min MHz:         400.0000
    BogoMIPS:            7585.63
    Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall
                          nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good amd_lbr_v2 nopl nonstop_tsc cpuid extd_apicid ap
                         erfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdra
                         nd lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce top
                         oext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba perfmon_v2 ibrs i
                         bpb stibp ibrs_enhanced vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed
                         adx smap avx512ifma clflushopt clwb avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc
                          cqm_occup_llc cqm_mbm_total cqm_mbm_local avx512_bf16 clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt
                          lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold v_vmsave_vml
                         oad vgif x2avic v_spec_ctrl vnmi avx512vbmi umip pku ospke avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx
                         512_bitalg avx512_vpopcntdq rdpid overflow_recov succor smca flush_l1d
Virtualization features:
  Virtualization:        AMD-V
Caches (sum of all):    
  L1d:                   256 KiB (8 instances)
  L1i:                   256 KiB (8 instances)
  L2:                    8 MiB (8 instances)
  L3:                    16 MiB (1 instance)
NUMA:                    
  NUMA node(s):          1
  NUMA node0 CPU(s):     0-15
Vulnerabilities:        
  Gather data sampling:  Not affected
  Itlb multihit:         Not affected
  L1tf:                  Not affected
  Mds:                   Not affected
  Meltdown:              Not affected
  Mmio stale data:       Not affected
  Retbleed:              Not affected
  Spec rstack overflow:  Mitigation; safe RET, no microcode
  Spec store bypass:     Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:            Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  Spectre v2:            Mitigation; Enhanced / Automatic IBRS, IBPB conditional, STIBP always-on, RSB filling, PBRSB-eIBRS Not affec
                         ted
  Srbds:                 Not affected
  Tsx async abort:       Not affected
Finally, here is a [pastebin with the vbox.log contents](https://pastebin.com/r7AuEarF) Any ideas where should start to look for a solution to this?
I'm Root James (213 rep)
Jan 25, 2024, 02:05 PM • Last activity: Jun 19, 2025, 01:03 AM
6 votes
2 answers
2237 views
radeon errors: GPU lockup: ring 0 stalled for more than x msec
I have newly installed machine with Debian Buster. The GPU is radeon `FirePro W2100`. After couple of hours of use, the machine suddenly freezes, the display switches to "white noise", and machine is unusable. In the logs, I see many errors like these: kernel: radeon 0000:65:00.0: ring 0 stalled for...
I have newly installed machine with Debian Buster. The GPU is radeon FirePro W2100. After couple of hours of use, the machine suddenly freezes, the display switches to "white noise", and machine is unusable. In the logs, I see many errors like these: kernel: radeon 0000:65:00.0: ring 0 stalled for more than 10240msec kernel: radeon 0000:65:00.0: GPU lockup (current fence id 0x0000000000039bff last fence id 0x0000000000039c42 on ring 0) kernel: adeon 0000:65:00.0: failed to get a new IB (-35) kernel: [drm:ffffffff816219d0] *ERROR* Couldn't update BO_VA (-35) kernel: radeon 0000:65:00.0: failed to get a new IB (-35) and then kernel: radeon 0000:65:00.0: ring 0 stalled for more than 10032msec kernel: radeon 0000:65:00.0: GPU lockup (current fence id 0x0000000000039bff last fence id 0x0000000000039c42 on ring 0) what do the errors mean, and how can I fix this ? Is this HW or SW problem ?
Martin Vegter (586 rep)
Dec 8, 2019, 07:18 PM • Last activity: May 17, 2025, 12:11 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
0 votes
0 answers
52 views
Is there a bug in the kernel or in the microcode for Ryzen 5 1600?
I'm using the following system: - OS: Linux Mint 22.1 - Kernel: Linux 6.8.0-59-generic. - CPU: Ryzen 5 1600 - GPU: GT430C - Motherboard: B450M-A II - PSU: Corsair RM850 - BIOS 3002 - Microcode 0x08001138 From time to time, the PC beeps once and reboots. With BIOS 4609 and 4410, the PC could hang or...
I'm using the following system: - OS: Linux Mint 22.1 - Kernel: Linux 6.8.0-59-generic. - CPU: Ryzen 5 1600 - GPU: GT430C - Motherboard: B450M-A II - PSU: Corsair RM850 - BIOS 3002 - Microcode 0x08001138 From time to time, the PC beeps once and reboots. With BIOS 4609 and 4410, the PC could hang or reboot anywhere between 30 and 170 minutes. I'm using mdadm to create a RAID 6 and Samba to use the PC as NAS. The next time after it hung, I found this in the journal.
watchdog: BUG: soft lockup - CPU#2 stuck for 100s! [kcompactd0:100]
kernel: watchdog: BUG: soft lockup - CPU#4 stuck for 3855s! [gdbus:2699]
I would appreciate any info about this. Thanks. I read this [thread](https://forums.debian.net/viewtopic.php?t=148561) and seems like the first Ryzen generation/family has some issues, at least at that time. I wonder if this was solved in the current kernel?
E_Blue (101 rep)
May 10, 2025, 11:30 PM • Last activity: May 11, 2025, 02:17 AM
0 votes
1 answers
5969 views
Arch Linux: Stuck on boot screen (Reached target Graphical Interface)
Two days ago I did a system update with `sudo pacman -Syyu` Unfortunately, my battery was empty and my laptop turned off during the System update. When I tried to start Arch Linux again, I was stuck on the grub Bootloader with the following message: ` Error: file /vmlinux-linux-lts not found. Error:...
Two days ago I did a system update with sudo pacman -Syyu Unfortunately, my battery was empty and my laptop turned off during the System update. When I tried to start Arch Linux again, I was stuck on the grub Bootloader with the following message: ` Error: file /vmlinux-linux-lts not found. Error: you need to load the kernel first Press a key to continue` According to https://bbs.archlinux.org/viewtopic.php?id=238904 , I have to reinstall linux again so I did the following: 1. Installed an Arch Linux iso on a USB-stick 2. Checked my partitions with fdisk -l 3. Mounted my root partition with mount /dev/sda1 /mnt (I don`t have a boot partiton) 4. Installed mkinitcpio, linux. linux-lts and systemd with sudo pacman -S linux linux-lts mkinitcpio systemd 5. Typed exit and rebooted. As you can see, I forgot to umount my root partiton. When I rebooted the system, I could finally boot into arch without the error messages but I run into the next problem. I was stuck at the boot screen with the message:
Starting Version 244.3-1-arch
/dev/sda1: recovering Journal
/dev/sda1: clean, 712088/5898240 files, 15789063/23592960 blocks
After a while, I switched to tty2 by pressing Ctrl+strg+F2. I did some research on the Internet and I found a solution how to escape from this: On the grub menu, I selected Arch Linux and pressed e. In the line
linux /boot/vmlinuz-linux-lts root=UUID=168b8466-66a9-4da7-bld4-07f5e95d1c73 rw loglevel=3 quiet
I removed quiet and booted into arch. Now I am stuck at Reached target Graphical Interface. For any reason, sddm does not want to start. If I switch to tty2, I always get prompted into a zsh shell. I tried everything, from removing ./Xauthority to reinstalling the xorg package. Nothing worked. Additional Information: Laptop name: HP625 processor: AMD Athlon II P320 GPU: ATI Radeon HD 4250 dual-boot system (Arch Linux alongside with Kali Linux) Related links: https://unix.stackexchange.com/questions/330999/arch-linux-stuck-at-boot-reached-target-graphical-interface https://bbs.archlinux.org/viewtopic.php?id=228814 https://wiki.archlinux.org/index.php/Xorg https://wiki.archlinux.org/index.php/SDDM https://wiki.archlinux.org/index.php/LightDM https://github.com/sddm/sddm/issues/352
antimatter (53 rep)
Feb 15, 2020, 11:07 AM • Last activity: May 10, 2025, 12:12 AM
1 votes
0 answers
400 views
Linux not working with Radeon Vega 8 GPU
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...
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.
Aleksander (11 rep)
Jun 7, 2023, 04:09 AM • Last activity: Apr 26, 2025, 10:50 AM
4 votes
1 answers
3874 views
How to know if a AMD cpu's SME feature is enabled?
More recent AMD CPUs have a feature named [Secure Memory Encryption SME][1] which if available can be explicitly be enabled by adding this parameter to linux' command line. mem_encrypt=on (according to https://libvirt.org/kbase/launch_security_sev.html) I am unsure if my system (with an AMD EPYC cpu...
More recent AMD CPUs have a feature named Secure Memory Encryption SME which if available can be explicitly be enabled by adding this parameter to linux' command line. mem_encrypt=on (according to https://libvirt.org/kbase/launch_security_sev.html) I am unsure if my system (with an AMD EPYC cpu) has this feature enabled (i.e. if the feature might be default on anyway). My question is how to check if the AMD SME feature is enabled? Since https://www.kernel.org/doc/html/latest/arch/x86/amd-memory-encryption.html suggests that: > If support for SME is present, MSR 0xc00100010 (MSR_K8_SYSCFG) can be > used to determine if SME is enabled and/or to enable memory > encryption: I have run this commands (on a debian 10): apt-get install msr-tools rdmsr --raw 0xc0010010 | xxd -b which presented me this output 00000000: 00000000 00000000 11110100 00000000 00000000 00000000 ...... 00000006: 00000000 00000000 where according to the source quoted the 23rd bit indicates if SME is indeed enabled/active (=1) or not (=0). If above is indeed the correct way to test this, a confirmation may be considered a valid answer, ideally of course providing some background. Else again I would be very happy to be able to check the state of SME on a running linux system.
fraleone (897 rep)
Jan 4, 2021, 11:05 AM • Last activity: Mar 25, 2025, 11:00 AM
0 votes
0 answers
29 views
DTS parameters for USB3 in Xilinx ZynqMP
When setting USB3 in device tree, I've seen in dts of reference boards (for example DTS for zcu102-RevA) different parameters for setting PHY. there are two parameters in dts for USB: ```cpp phys = ; phy-names = "usb3-phy"; ``` Seems to me, that "xlnx,zynqmp-dwc3" and "snps,dwc3" redirect settings o...
When setting USB3 in device tree, I've seen in dts of reference boards (for example DTS for zcu102-RevA) different parameters for setting PHY. there are two parameters in dts for USB:
phys = ;
phy-names = "usb3-phy";
Seems to me, that "xlnx,zynqmp-dwc3" and "snps,dwc3" redirect settings of phys to "xilinx,psgtr" In yml of this driver, there is description of each parameter:
properties:
  "#phy-cells":
    const: 4
    description: |

      The cells contain the following arguments.

      - description: The GTR lane
        minimum: 0
        maximum: 3
      - description: The PHY type
        enum:
          - PHY_TYPE_DP
          - PHY_TYPE_PCIE
          - PHY_TYPE_SATA
          - PHY_TYPE_SGMII
          - PHY_TYPE_USB3
      - description: The PHY instance
        minimum: 0
        maximum: 1 # for DP, SATA or USB
        maximum: 3 # for PCIE or SGMII
      - description: The reference clock number
        minimum: 0
        maximum: 3
What does "The PHY instance" option mean? Why on some boards (zcu102 f.e.) it is set to 0, while others(zc1751 f.e.) have it equal to 1?
lazba (1 rep)
Mar 24, 2025, 03:50 PM
1 votes
0 answers
216 views
ASPM status of PCIe device won't stay set
I'm building a small home server using Proxmox as the base OS, and I've been trying to improve power efficiency by allowing the machine to go into lower power states. I'm running a Ryzen 5 7600 and an ASRock Rack B650D4U. One thing I've done is configure and enable ASPM, with every relevant option i...
I'm building a small home server using Proxmox as the base OS, and I've been trying to improve power efficiency by allowing the machine to go into lower power states. I'm running a Ryzen 5 7600 and an ASRock Rack B650D4U. One thing I've done is configure and enable ASPM, with every relevant option in the UEFI and Grub config correctly configured to allow it. On boot, I run this script to enable ASPM on every PCIe device - https://github.com/notthebee/AutoASPM I then run lspci -vv | awk '/ASPM/{print $0}' RS= | grep --color -P '(^[a-z0-9:.]+|ASPM )' to check the status, as well as lspci -vvv | grep "ASPM .*abled" to make it a bit more digestible. After running this script, one device seems to always immediately disable itself; 00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Raphael/Granite Ridge Internal GPP Bridge to Bus [C:A] (prog-if 00 [Normal decode]) LnkCap: Port #0, Speed 16GT/s, Width x16, ASPM L0s L1, Exit Latency L0s AMD CBS -> FCH Common Options -> USB Configuration Options -> USB2 controller enable` seemed to allow it to stay set. However, this workaround no longer works and I honestly have no idea why. How can I diagnose this and figure out what is preventing ASPM from being enabled on this device?
Jademalo (161 rep)
Mar 22, 2025, 07:56 AM
0 votes
1 answers
433 views
Unable to install ROCm AMD driver on Linux Min 22.1 "The following packages have unmet dependencies:"
I am trying to install the AMD ROCm driver on my Linux Mint 22.1 computer. All goes well when entering the code: ```sudo amdgpu-install --list-usecase``` The output of that is: ``` If --usecase option is not present, the default selection is "dkms,graphics,opencl,hip" Available use cases: dkms (to o...
I am trying to install the AMD ROCm driver on my Linux Mint 22.1 computer. All goes well when entering the code:
amdgpu-install --list-usecase
The output of that is:
If --usecase option is not present, the default selection is
"dkms,graphics,opencl,hip"
Available use cases:
dkms            (to only install the kernel mode driver)
  - Kernel mode driver (included in all usecases)
graphics        (for users of graphics applications)
  - Open source Mesa 3D graphics and multimedia libraries
multimedia      (for users of open source multimedia)
  - Open source Mesa 3D multimedia libraries
workstation     (for users of legacy WS applications)
  - Open source multimedia libraries
  - Closed source (legacy) OpenGL
rocm            (for users and developers requiring full ROCm stack)
  - OpenCL (ROCr/KFD based) runtime
  - HIP runtimes
  - Machine learning framework
  - All ROCm libraries and applications
wsl             (for using ROCm in a WSL context)
  - ROCr WSL runtime library (Ubuntu 22.04 only)
rocmdev         (for developers requiring ROCm runtime and
                profiling/debugging tools)
  - HIP runtimes
  - OpenCL runtime
  - Profiler, Tracer and Debugger tools
rocmdevtools    (for developers requiring ROCm profiling/debugging tools)
  - Profiler, Tracer and Debugger tools
amf             (for users of AMF based multimedia)
  - AMF closed source multimedia library
lrt             (for users of applications requiring ROCm runtime)
  - ROCm Compiler and device libraries
  - ROCr runtime and thunk
opencl          (for users of applications requiring OpenCL on Vega or later
                products)
  - ROCr based OpenCL
  - ROCm Language runtime
openclsdk       (for application developers requiring ROCr based OpenCL)
  - ROCr based OpenCL
  - ROCm Language runtime
  - development and SDK files for ROCr based OpenCL
hip             (for users of HIP runtime on AMD products)
  - HIP runtimes
hiplibsdk       (for application developers requiring HIP on AMD products)
  - HIP runtimes
  - ROCm math libraries
  - HIP development libraries
openmpsdk       (for users of openmp/flang on AMD products)
  - OpenMP runtime and devel packages
mllib           (for users executing machine learning workloads)
  - MIOpen hip/tensile libraries
  - Clang OpenCL
  - MIOpen kernels
mlsdk           (for developers executing machine learning workloads)
  - MIOpen development libraries
  - Clang OpenCL development libraries
  - MIOpen kernels
asan            (for users of ASAN enabled ROCm packages)
  - ASAN enabled OpenCL (ROCr/KFD based) runtime
  - ASAN enabled HIP runtimes
  - ASAN enabled Machine learning framework
  - ASAN enabled ROCm libraries
I then entered:
-install -y --usecase=graphics,rocm
Output:
:1 http://packages.linuxmint.com  xia InRelease
Get:2 https://dl.google.com/linux/chrome/deb  stable InRelease [1,825 B]        
Hit:3 https://repo.radeon.com/amdgpu/6.3.2/ubuntu  noble InRelease              
Hit:4 http://packages.linuxmint.com  xia Release                                
Hit:5 http://security.ubuntu.com/ubuntu  noble-security InRelease               
Hit:6 https://repo.radeon.com/rocm/apt/6.3.2  noble InRelease                   
Get:7 https://dl.google.com/linux/chrome/deb  stable/main amd64 Packages [1,208 B]
Hit:8 http://archive.ubuntu.com/ubuntu  noble InRelease    
Hit:10 http://archive.ubuntu.com/ubuntu  noble-updates InRelease
Hit:11 http://archive.ubuntu.com/ubuntu  noble-backports InRelease
Fetched 3,033 B in 1s (2,703 B/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
linux-headers-6.8.0-53-generic is already the newest version (6.8.0-53.55).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 rocm-hip-runtime : Depends: rocminfo (= 1.0.0.60302-66~24.04) but 5.7.1-3build1 is to be installed
 rocm-utils : Depends: rocminfo (= 1.0.0.60302-66~24.04) but 5.7.1-3build1 is to be installed
E: Unable to correct problems, you have held broken packages.
As I am relatively new to linux and its bits I have no clue what to do to fix this. Does it require "rocminfo"? When trying
apt install rocminfo
I get
package lists... Done
Building dependency tree... Done
Reading state information... Done
rocminfo is already the newest version (5.7.1-3build1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Apparently its already installed and up to date. So then does it require the other packages: "rocm-hip-runtime", "rocm-utils"? Attempting to install these packages results in the same errors:
following packages have unmet dependencies:
 rocm-hip-runtime : Depends: rocminfo (= 1.0.0.60302-66~24.04) but 5.7.1-3build1 is to be installed
 rocm-utils : Depends: rocminfo (= 1.0.0.60302-66~24.04) but 5.7.1-3build1 is to be installed
E: Unable to correct problems, you have held broken packages.
Any and all help would be great!
InfaredDelta (13 rep)
Feb 10, 2025, 10:23 PM • Last activity: Feb 25, 2025, 07:26 AM
2 votes
1 answers
2050 views
ASUS motherboard fan control under Linux
I built a machine using an [ASUS TUF GAMING B650M-PLUS](https://www.asus.com/br/motherboards-components/motherboards/tuf-gaming/tuf-gaming-b650m-plus/) motherboard and a Ryzen 7 8700G CPU. Linux installed with no problems, but I am missing fan control and monitoring. Under Windows, I use ASUS softwa...
I built a machine using an [ASUS TUF GAMING B650M-PLUS](https://www.asus.com/br/motherboards-components/motherboards/tuf-gaming/tuf-gaming-b650m-plus/) motherboard and a Ryzen 7 8700G CPU. Linux installed with no problems, but I am missing fan control and monitoring. Under Windows, I use ASUS software to do stuff like setting fan curves and monitoring fan speeds: enter image description here enter image description here What I have tried: * pwmconfig doesn't find any fans. * sensors-detect fails to find anything but spd5118 (RAM temperature, I believe), k10temp (CPU temperature), amdgpu and NVME temperature. * [CoolerControl](https://gitlab.com/coolercontrol/coolercontrol) doesn't find any fans, either. I keep finding stuff about fan control in ASUS laptops, which isn't the case. What tools can I use under Linux to manage CPU fans? Right now, I need to reboot and enter Setup, which is very impractical.
Renan (17338 rep)
Jan 31, 2025, 10:58 PM • Last activity: Feb 2, 2025, 12:44 PM
0 votes
0 answers
921 views
Driver problem with 780M (Ryzen 7 7840HS iGPU)
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...
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.
erenalyoruk (1 rep)
May 24, 2024, 01:03 PM • Last activity: Feb 2, 2025, 12:23 AM
2 votes
1 answers
46542 views
How to manually set CPU Fan Speed in Debian Linux?
As my CPU cooler fan broke on a setup with older hardware, I had to replace it with a similar fan, which unfortunately is pretty noisy. I am using the following system: - Mainboard Gigabyte F2A88X-Up4 - CPU AMD A10-7850k radeon r7 - Debian GNU/Linux 9 (stretch) 64-bit The fan is permanently running...
As my CPU cooler fan broke on a setup with older hardware, I had to replace it with a similar fan, which unfortunately is pretty noisy. I am using the following system: - Mainboard Gigabyte F2A88X-Up4 - CPU AMD A10-7850k radeon r7 - Debian GNU/Linux 9 (stretch) 64-bit The fan is permanently running at 3770 RPM and I am looking for a way to manually reduce the speed. There is an option in the BIOS to set the fan to a "silent" mode, but it does not have any effect. I then installed
-sensors
and
. Running the sensors I get the following output:
-pci-00c4
Adapter: PCI adapter
power1:           N/A  (crit =  95.09 W)

it8620-isa-0228
Adapter: ISA adapter
in0:          +0.70 V  (min =  +0.00 V, max =  +3.06 V)
in1:          +1.50 V  (min =  +0.00 V, max =  +3.06 V)
in2:          +2.03 V  (min =  +0.00 V, max =  +3.06 V)
in3:          +2.05 V  (min =  +0.00 V, max =  +3.06 V)
in4:          +2.05 V  (min =  +0.00 V, max =  +3.06 V)
in5:          +2.23 V  (min =  +0.00 V, max =  +3.06 V)
in6:          +2.23 V  (min =  +0.00 V, max =  +3.06 V)
3VSB:         +3.29 V  (min =  +0.00 V, max =  +6.12 V)
Vbat:         +2.69 V  
fan1:        3770 RPM  (min =    0 RPM)
fan2:           0 RPM  (min =    0 RPM)
fan3:           0 RPM  (min =    0 RPM)
fan4:           0 RPM  (min =    0 RPM)
fan5:           0 RPM  (min =    0 RPM)
temp1:        +22.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp2:         -8.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
temp3:        +13.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = Intel PECI
temp4:        +45.0°C  
temp5:        +45.0°C  
temp6:        +45.0°C  
intrusion0:  ALARM

radeon-pci-0008
Adapter: PCI adapter
temp1:        -11.0°C  (crit = +120.0°C, hyst = +90.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:         +0.0°C  (high = +70.0°C)
                       (crit = +80.0°C, hyst = +79.0°C)
I then ran the fancontrol configuration script with
:
the following devices:
   hwmon0 is it8620
   hwmon1 is k10temp
   hwmon2 is fam15h_power
   hwmon3 is radeon

Found the following PWM controls:
   hwmon0/pwm1           current value: 0
   hwmon0/pwm2           current value: 0
   hwmon0/pwm3           current value: 0
   hwmon0/pwm4           current value: 255
   hwmon0/pwm5           current value: 255

Giving the fans some time to reach full speed...
Found the following fan sensors:
   hwmon0/fan1_input     current speed: 3792 RPM
   hwmon0/fan2_input     current speed: 0 ... skipping!
   hwmon0/fan3_input     current speed: 0 ... skipping!
   hwmon0/fan4_input     current speed: 0 ... skipping!
   hwmon0/fan5_input     current speed: 0 ... skipping!
So I am trying to reduce the speed of
/fan1_input
. Running the test, which did not stop my CPU fan, I got the following result:
pwm control hwmon0/pwm1 ...
  hwmon0/fan1_input ... speed was 3792 now 3750
    no correlation

No correlations were detected.
There is either no fan connected to the output of hwmon0/pwm1,
or the connected fan has no rpm-signal connected to one of
the tested fan sensors. (Note: not all motherboards have
the pwm outputs connected to the fan connectors,
check out the hardware database on http://www.almico.com/forumindex.php) 

Did you see/hear a fan stopping during the above test (n)?
Based on this result I assume that I cannot control my CPU fan with
? Or is it possible to write a manual configuration for the fan in
/etc/fancontrol
despite the previous output? I would appreciate your feedback.
JohnSane (21 rep)
Jun 1, 2020, 08:22 PM • Last activity: Jan 24, 2025, 08:08 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
0 votes
0 answers
73 views
Kernel Panic after rescaling VPS from Intel to AMD using Ubuntu 16
After upgrading my VPS from a shared CPU (intel) to a dedicated CPU (amd), I get a kernel panic on bootup, including if I boot into recovery mode. I have managed to use the rescue console to get to the disk (and I'm currently copying the files off it), but what can I try or investigate to get it wor...
After upgrading my VPS from a shared CPU (intel) to a dedicated CPU (amd), I get a kernel panic on bootup, including if I boot into recovery mode. I have managed to use the rescue console to get to the disk (and I'm currently copying the files off it), but what can I try or investigate to get it working again? I also can't find the kernel panic in any logs from rescue mode (and I don't seem to be able to scroll in the console to be able to see what preceded it). Is there any way to get at those logs?
Ben Holness (113 rep)
Jan 7, 2025, 05:06 PM
0 votes
2 answers
2824 views
how to get my AMD GPU to work under debian?
Okay guys i lost all hope to solve this problem. I have a dell m4800 which supports 2 gpu's Intel and AMD m5100. i tried everything to get the AMD GPU to work but with no luck, the main problem is that the HDMI port is connected to the AMD GPU and i cant get it to work. here is my xrandr output : $x...
Okay guys i lost all hope to solve this problem. I have a dell m4800 which supports 2 gpu's Intel and AMD m5100. i tried everything to get the AMD GPU to work but with no luck, the main problem is that the HDMI port is connected to the AMD GPU and i cant get it to work. here is my xrandr output : $xrandr --listproviders Providers: number : 2 Provider 0: id: 0x46 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 4 associated providers: 0 name:modesetting Provider 1: id: 0xdd cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 4 associated providers: 0 name:VERDE @ pci:0000:01:00.0* so i cant tell it sees the GPU but i cant use it: the out put for inxi -G: Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel Device-2: AMD Venus XT [Radeon HD 8870M / R9 M270X/M370X] driver: radeon v: kernel Display: x11 server: X.Org 1.20.8 driver: ati,modesetting,radeon unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.1.2 i checked archwiki but unfortunately with no luck to solve the problem. any help would be great. thanks '''''''''''''''' Org X Server 1.20.8 X Protocol Version 11, Revision 0 [ 17707.015] Build Operating System: Linux 4.19.0-8-amd64 x86_64 Debian [ 17707.015] Current Operating System: SMP Debian 5.6.14-2 (2020-05-23) x86_64 [ 17707.015] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.6.0-2Debian-amd64 root=UUID=41ce03bf-3470-48db-92d9-0552d7f254ac ro quiet splash noautomount quiet [ 17707.015] Build Date: 31 March 2020 10:14:40AM [ 17707.015] xorg-server 2:1.20.8-2 (https://www.debian.org/support) [ 17707.015] Current version of pixman: 0.36.0 [ 17707.015] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 17707.015] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 17707.015] (==) Log file: "/var/log/Xorg.1.log", Time: Wed Jul 29 19:24:47 2020 [ 17707.015] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 17707.016] (==) No Layout section. Using the first Screen section. [ 17707.016] (==) No screen section available. Using defaults. [ 17707.016] (**) |-->Screen "Default Screen Section" (0) [ 17707.016] (**) | |-->Monitor "" [ 17707.016] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 17707.016] (==) Automatically adding devices [ 17707.016] (==) Automatically enabling devices [ 17707.016] (==) Automatically adding GPU devices [ 17707.016] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 17707.016] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 17707.016] Entry deleted from font path. [ 17707.016] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 17707.016] (==) ModulePath set to "/usr/lib/xorg/modules" [ 17707.016] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 17707.016] (II) Loader magic: 0x55bb4bc32e20 [ 17707.016] (II) Module ABI versions: [ 17707.016] X.Org ANSI C Emulation: 0.4 [ 17707.016] X.Org Video Driver: 24.1 [ 17707.016] X.Org XInput driver : 24.1 [ 17707.016] X.Org Server Extension : 10.0 [ 17707.017] (--) using VT number 2 [ 17707.017] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 17707.018] (II) xfree86: Adding drm device (/dev/dri/card0) [ 17707.018] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied [ 17707.018] (II) xfree86: Adding drm device (/dev/dri/card1) [ 17707.018] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied [ 17707.020] (--) PCI:*(0@0:2:0) 8086:0416:1028:05cc rev 6, Mem @ 0xf5800000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072 [ 17707.020] (--) PCI: (1@0:0:0) 1002:6821:1028:05cc rev 0, Mem @ 0xe0000000/268435456, 0xf7c00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072 [ 17707.020] (II) LoadModule: "glx" [ 17707.020] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 17707.021] (II) Module glx: vendor="X.Org Foundation" [ 17707.021] compiled for 1.20.8, module version = 1.0.0 [ 17707.021] ABI class: X.Org Server Extension, version 10.0 [ 17707.021] (==) Matched modesetting as autoconfigured driver 0 [ 17707.021] (==) Matched fbdev as autoconfigured driver 1 [ 17707.021] (==) Matched vesa as autoconfigured driver 2 [ 17707.021] (==) Assigned the driver to the xf86ConfigLayout [ 17707.021] (II) LoadModule: "modesetting" [ 17707.021] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 17707.021] (II) Module modesetting: vendor="X.Org Foundation" [ 17707.021] compiled for 1.20.8, module version = 1.20.8 [ 17707.021] Module class: X.Org Video Driver [ 17707.021] ABI class: X.Org Video Driver, version 24.1 [ 17707.021] (II) LoadModule: "fbdev" [ 17707.021] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 17707.021] (II) Module fbdev: vendor="X.Org Foundation" [ 17707.021] compiled for 1.20.0, module version = 0.5.0 [ 17707.021] Module class: X.Org Video Driver [ 17707.021] ABI class: X.Org Video Driver, version 24.0 [ 17707.021] (II) LoadModule: "vesa" [ 17707.021] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 17707.021] (II) Module vesa: vendor="X.Org Foundation" [ 17707.021] compiled for 1.20.4, module version = 2.4.0 [ 17707.021] Module class: X.Org Video Driver [ 17707.021] ABI class: X.Org Video Driver, version 24.0 [ 17707.021] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 17707.021] (II) FBDEV: driver for framebuffer: fbdev [ 17707.021] (II) VESA: driver for VESA chipsets: vesa [ 17707.350] (WW) Falling back to old probe method for modesetting [ 17707.350] (II) modeset(1): using default device [ 17707.350] (II) Loading sub module "fbdevhw" [ 17707.350] (II) LoadModule: "fbdevhw" [ 17707.350] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 17707.350] (II) Module fbdevhw: vendor="X.Org Foundation" [ 17707.350] compiled for 1.20.8, module version = 0.0.2 [ 17707.350] ABI class: X.Org Video Driver, version 24.1 [ 17707.350] (**) FBDEV(2): claimed PCI slot 0@0:2:0 [ 17707.350] (II) FBDEV(2): using default device [ 17707.350] (EE) Screen 0 deleted because of no matching config section. [ 17707.350] (II) UnloadModule: "modesetting" [ 17707.350] (EE) Fatal server error: [ 17707.350] (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices [ 17707.350] (EE) [ 17707.350] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 17707.350] (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. [ 17707.350] (EE) [ 17707.399] (EE) Server terminated with error (1). Closing log file.``
mobe (1 rep)
Jul 29, 2020, 08:51 PM • Last activity: Nov 13, 2024, 12:36 PM
Showing page 1 of 20 total questions