Proxmox Host Screen Resolution

D

dCipher

New Member
Jul 19, 2025
28
2
3
Hi

My VM's are all running at the correct higher screen resolutions. However the Proxmox host is stuck at 1920x1080 as the only choice. I would like it to use the default screen resolution of my display which is 2560x1440 because I am also using it as a workstation. Can someone explain who to set a higher resolution for the Proxmox host?

Thanks,
Simon
 
Hello

First we need to get to "know" your system better.

Here are some questions:

Are you booting your Proxmox host in Legacy BIOS/GRUB mode or UEFI mode?
(Tip: You can check with ls /sys/firmware/efi — if the folder exists, you’re on UEFI.)

What is the output of:

Code: 
grep -E "GRUB_GFX|CMDLINE" /etc/default/grub

This shows what resolution/kernel settings are already configured.


Hardware & Display

What kind of hardware are you running Proxmox on (server, workstation, NUC, etc.)?

Which GPU or onboard graphics is driving the display?

Is the monitor connected directly to the Proxmox host, and via HDMI/DP/DVI?

Current Console Behavior

Does the higher resolution show up in the GRUB boot menu, but drop back to 1920×1080 after boot?

Or is the GRUB menu itself also locked at 1920×1080?



Kernel & Framebuffer

What kernel version are you running? (uname -r)

What resolutions are reported by the framebuffer?

Code: 
cat /sys/class/graphics/fb0/modes


What does the boot log show about framebuffer/EFI?

Code: 
dmesg | grep -i fb
 
I am running on the Minisforum AI X1 Pro with 128Gb ram and 2Tb NVMe drives. It has the AMD Ryzen™ AI 9 HX 370 processor and Radeon™ 890M

root@minipc:~# grep -E "GRUB_GFX|CMDLINE" /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
#GRUB_GFXMODE=640x480

root@minipc:~# ls /sys/firmware/efi
config_table esrt fw_vendor runtime systab
efivars fw_platform_size mok-variables runtime-map

root@minipc:~# uname -r
6.14.8-2-pve

root@minipc:~# cat /sys/class/graphics/fb0/modes
U:1920x1080p-0

root@minipc:~# dmesg | grep -i fb
[ 0.383378] pci 0000:00:18.3: [1022:16fb] type 00 class 0x060000 conventional PCI endpoint
[ 0.446985] Driver imsttfb not loading because of nomodeset parameter
[ 0.446986] Driver asiliantfb not loading because of nomodeset parameter
[ 1.965474] fbcon: Deferring console take-over
[ 1.965475] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[ 1.984655] integrity: Loaded X.509 cert 'Microsoft Corporation: Windows UEFI CA 2023: aefc5fbbbe055d8f8daa585473499417ab5a5272'
[ 3.600307] fbcon: Taking over console

root@minipc:~#
 
Hello

The Radeon 890M GPU should support 2560×1440, but since only simple-framebuffer is active, the kernel is not yet loading a proper AMD GPU driver for the console.

check if the AMD Gpu is loaded in proxmox

Code: 
lsmod | grep amdgpu
dmesg | grep amdgpu

if it is then it should support higher resolutions automatically. if its not loaded then there is the issue.

Check for nomodeset In your GRUB config, the logs mention nomodeset.

That prevents the AMDGPU driver from taking over graphics and leaves you with a generic framebuffer.

Edit /etc/default/grub:
Remove nomodeset if it’s present in GRUB_CMDLINE_LINUX_DEFAULT.

Then:

Code: 
update-grub
reboot
Without nomodeset, the amdgpu kernel driver should initialize, which can expose native resolutions like 2560×1440.

EDIT:

If needed, add video=2560x1440 to GRUB_CMDLINE_LINUX_DEFAULT.
 
Last edited:
Hi

There are no results shown for the following two comands

root@minipc:~# lsmod | grep amdgpu
root@minipc:~# dmesg | grep amdgpu

root@minipc:~# nano /etc/default/grub


GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`( . /etc/os-release && echo ${NAME} )`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

Synaptic shows I have installed:
libdrm-amdgpu1 2.4.124-2
xserver-xorg-video-amdgpu 23.0.0-1

This is not installed and I do not know if I need it.

firmware-amd-graphics

If I mark it for installation I am warned that the following will be uninstalled:
proxmox-default-kernel
proxmox-kernel-6.14
proxmox-ve
pve-firmware
 
Hello

you dont want to uninstall proxmox stuff.. i feel like the Xorg stuff is not standard install have you added it your self?
Better to wait for a proxmox staff to help
 
What is the output of cat /proc/cmdline and lspci -nnk (for the GPU/VGA device)?

EDIT: Debian firmware packages conflict with PVE firmware packages (and you should uninstall the Debian kernel).
 
Last edited:
Hi

Perhaps the issue is the nomodeset. I only installed Proxmox so I do not believe I am running the Debian Kernel.

root@minipc:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-6.14.8-2-pve root=/dev/mapper/pve-root ro nomodeset quiet

root@minipc:~# lspci -nnk
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo Root Complex [1022:1507]
Subsystem: Device [1f4c:b020]
00:00.2 IOMMU [0806]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo IOMMU [1022:1508]
Subsystem: Device [1f4c:b020]
00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo Dummy Host Bridge [1022:1509]
00:01.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo PCIe USB4 Bridge [1022:150a]
Subsystem: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo PCIe USB4 Bridge [1022:150a]
Kernel driver in use: pcieport
00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo PCIe USB4 Bridge [1022:150a]
Subsystem: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo PCIe USB4 Bridge [1022:150a]
Kernel driver in use: pcieport
00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo Dummy Host Bridge [1022:1509]
DeviceName: Onboard IGD
00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo GPP Bridge [1022:150b]
Subsystem: Device [1f4c:b020]
Kernel driver in use: pcieport
00:02.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo GPP Bridge [1022:150b]
Subsystem: Device [1f4c:b020]
Kernel driver in use: pcieport
00:02.4 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo GPP Bridge [1022:150b]
Subsystem: Device [1f4c:b020]
Kernel driver in use: pcieport
00:02.5 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo GPP Bridge [1022:150b]
Subsystem: Device [1f4c:b020]
Kernel driver in use: pcieport
00:03.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo Dummy Host Bridge [1022:1509]
00:03.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo GPP Bridge [1022:150b]
Subsystem: Device [1f4c:b020]
Kernel driver in use: pcieport
00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo Dummy Host Bridge [1022:1509]
00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo Internal GPP Bridge to Bus [C:A] [1022:150c]
Subsystem: Device [1f4c:b020]
Kernel driver in use: pcieport
00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo Internal GPP Bridge to Bus [C:A] [1022:150c]
Subsystem: Device [1f4c:b020]
Kernel driver in use: pcieport
00:08.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo Internal GPP Bridge to Bus [C:A] [1022:150c]
pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted
Subsystem: Device [1f4c:b020]
Kernel driver in use: pcieport
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 71)
Subsystem: Device [1f4c:b020]
Kernel driver in use: piix4_smbus
Kernel modules: i2c_piix4, sp5100_tco
00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
Subsystem: Device [1f4c:b020]
00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 0 [1022:16f8]
00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 1 [1022:16f9]
00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 2 [1022:16fa]
00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 3 [1022:16fb]
Kernel driver in use: k10temp
Kernel modules: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 4 [1022:16fc]
00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 5 [1022:16fd]
00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 6 [1022:16fe]
00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Strix Data Fabric; Function 7 [1022:16ff]
c1:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. Device [2646:502d]
Subsystem: Kingston Technology Company, Inc. Device [2646:502d]
Kernel driver in use: nvme
Kernel modules: nvme
c2:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7925]
Subsystem: Quectel Wireless Solutions Co., Ltd. Device [1eac:8005]
Kernel driver in use: mt7925e
Kernel modules: mt7925e
c3:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
Kernel driver in use: r8169
Kernel modules: r8169
c4:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
Kernel driver in use: r8169
Kernel modules: r8169
c5:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal] [144d:a80c]
Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
Kernel driver in use: nvme
Kernel modules: nvme
c6:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Strix [Radeon 880M / 890M] [1002:150e] (rev c1)
Subsystem: Device [1f4c:b020]
Kernel modules: amdgpu
c6:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Radeon High Definition Audio Controller [Rembrandt/Strix] [1002:1640]
Subsystem: Device [1f4c:b020]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
c6:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Strix/Krackan/Strix Halo CCP/ASP [1022:17e0]
Subsystem: Device [1f4c:b020]
Kernel driver in use: ccp
Kernel modules: ccp
c6:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151e]
Subsystem: Device [1f4c:b020]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
c6:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h/1ah HD Audio Controller [1022:15e3]
Subsystem: Device [1f4c:b020]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
c6:00.7 Signal processing controller [1180]: Advanced Micro Devices, Inc. [AMD] Sensor Fusion Hub [1022:164a]
Subsystem: Advanced Micro Devices, Inc. [AMD] Sensor Fusion Hub [1022:164a]
Kernel driver in use: pcie_mp2_amd
Kernel modules: amd_sfh
c7:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo PCIe Dummy Function [1022:150d]
Subsystem: Advanced Micro Devices, Inc. [AMD] Strix/Strix Halo PCIe Dummy Function [1022:150d]
c7:00.1 Signal processing controller [1180]: Advanced Micro Devices, Inc. [AMD] Strix/Krackan/Strix Halo Neural Processing Unit [1022:17f0] (rev 10)
Subsystem: Advanced Micro Devices, Inc. [AMD] Strix/Krackan/Strix Halo Neural Processing Unit [1022:17f0]
Kernel driver in use: amdxdna
Kernel modules: amdxdna
c8:00.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151f]
Subsystem: Device [1f4c:b020]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
c8:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151a]
Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:151a]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
c8:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Device [1022:151b]
Subsystem: Advanced Micro Devices, Inc. [AMD] Device [1022:151b]
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
c8:00.5 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] USB4 Router 0 [1022:151c]
Subsystem: Advanced Micro Devices, Inc. [AMD] USB4 Router 0 [1022:151c]
Kernel driver in use: thunderbolt
Kernel modules: thunderbolt
c8:00.6 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] USB4 Router 1 [1022:151d]
Subsystem: Advanced Micro Devices, Inc. [AMD] USB4 Router 1 [1022:151d]
Kernel driver in use: thunderbolt
Kernel modules: thunderbolt
root@minipc:~#
 
Last edited:
dCipher said:
BOOT_IMAGE=/boot/vmlinuz-6.14.8-2-pve root=/dev/mapper/pve-root ro nomodeset quiet
Click to expand...
Make sure that this does not show nomodeset. Did you ever put it in the GRUB configuration? You showed (please use CODE-tags in the future) that it is no longer in the GRUB configuration but did you ever apply those changes? Maybe have a look at the manual about editing the kernel parameters: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysboot_edit_kernel_cmdline
dCipher said:
Code: 
c6:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Strix [Radeon 880M / 890M] [1002:150e] (rev c1)
        Subsystem: Device [1f4c:b020]
        Kernel modules: amdgpu
Click to expand...
The amdgpu driver would probably load automatically once you remove the nomodeset from the kernel parameters.
 
Hi

When I first installed Proxmox 8.4 I had to use the edit option in the boot menu to add the nomodeset because it would never install otherwise. It was another user of this forum that suggested I do that. So now if I understand correctly the "nomodeset" needs to be removed. So I will have to read up on how to do that.

Thanks
Simon
 
Hi

I removed the nomodeset from the proxmox-ve.cfg in /etc/default/grub.d and now I do not have a video signal to the monitor put Proxmox is running because I can use the web interface. If I put the "nomodeset" back into the proxmox-ve.cfg I also do not get a video signal. In both cases I ran update-grub. I can see the change on the Proxmox boot screen because in one case it shows the "nomodeset" and in the other it does show the "nomodeset"

Simon
 
I assume the .d in /etc/default/grub.d and that proxmox-ve.cfg are typos. If you have no host console (no output on the display) then maybe amdgpu does not (yet) support your (very recent) hardware?
Is amdgpu loaded when you have no host console? What is the output of lspci -nnks c6:00.0 when connecting to the Proxmox host via SSH? Anything related in the journalctl -b 0?
What version of Proxmox are you running? Have you tried the latest kernel version 6.14? Maybe stick with nomodeset until your hardware is fully supported by the Linux kernel that Proxmox uses. Laptop support can be a bit behind on Linux.

EDIT: You can press e in the GRUB menu when booting to make temporary changes to the kernel parameters that only last that one boot.
 
Last edited:
leesteken said:
I assume the .d in /etc/default/grub.d and that proxmox-ve.cfg are typos. If you have no host console (no output on the display) then maybe amdgpu does not (yet) support your (very recent) hardware?
Is amdgpu loaded when you have no host console? What is the output of lspci -nnks c6:00.0 when connecting to the Proxmox host via SSH? Anything related in the journalctl -b 0?
What version of Proxmox are you running? Have you tried the latest kernel version 6.14? Maybe stick with nomodeset until your hardware is fully supported by the Linux kernel that Proxmox uses. Laptop support can be a bit behind on Linux.

EDIT: You can press e in the GRUB menu when booting to make temporary changes to the kernel parameters that only last that one boot.
Click to expand...
root@minipc:~# cd /etc/default/grub.d
root@minipc:/etc/default/grub.d# ls
installer.cfg proxmox-ve.cfg
root@minipc:/etc/default/grub.d#

root@minipc:/etc/default/grub.d# lspci -nnks c6:00.0
c6:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Strix [Radeon 880M / 890M] [1002:150e] (rev c1)
Subsystem: Device [1f4c:b020]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
root@minipc:/etc/default/grub.d#

root@minipc:/etc/default/grub.d# journalctl -b 0
Aug 25 13:01:33 minipc kernel: Linux version 6.14.8-2-pve (build@proxmox) (gcc (Debi>
Aug 25 13:01:33 minipc kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.14.8-2-pve r>
Aug 25 13:01:33 minipc kernel: KERNEL supported cpus:
Aug 25 13:01:33 minipc kernel: Intel GenuineIntel
Aug 25 13:01:33 minipc kernel: AMD AuthenticAMD
Aug 25 13:01:33 minipc kernel: Hygon HygonGenuine
Aug 25 13:01:33 minipc kernel: Centaur CentaurHauls
Aug 25 13:01:33 minipc kernel: zhaoxin Shanghai
Aug 25 13:01:33 minipc kernel: x86/split lock detection: #DB: warning on user-space >
Aug 25 13:01:33 minipc kernel: BIOS-provided physical RAM map:

Aug 25 13:01:33 minipc kernel: [drm] amdgpu kernel modesetting enabled.
Aug 25 13:01:33 minipc kernel: amdgpu: Virtual CRAT table created for CPU
Aug 25 13:01:33 minipc kernel: amdgpu: Topology: Add CPU node
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: enabling device (0006 -> 0007)
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 0 <soc21_common>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 1 <gmc_v11_0>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 2 <ih_v6_1>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 3 <psp>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 4 <smu>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 5 <dm>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 6 <gfx_v11_0>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 7 <sdma_v6_0>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 8 <vcn_v4_0_5>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 9 <jpeg_v4_0_5>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 10 <mes_v11_0>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 11 <vpe_v6_1>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: detected ip block number 12 <isp_ip>
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: Fetched VBIOS from VFCT
Aug 25 13:01:33 minipc kernel: amdgpu: ATOM BIOS: 113-STRIXEMU-001
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: VPE: collaborate mode false
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: [drm] Optional firmware "amdgpu/isp_4_1_0.bin" was not found
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: Trusted Memory Zone (TMZ) feature disabled as experimental (default)
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: VRAM: 8192M 0x0000008000000000 - 0x00000081FFFFFFFF (8192M used)
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: GART: 512M 0x00007FFF00000000 - 0x00007FFF1FFFFFFF
Aug 25 13:01:33 minipc kernel: [drm] amdgpu: 8192M of VRAM memory ready
Aug 25 13:01:33 minipc kernel: [drm] amdgpu: 60180M of GTT memory ready.
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: reserve 0x8900000 from 0x81e0000000 for PSP TMR
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: RAS: optional ras ta ucode is not available
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: RAP: optional rap ta ucode is not available
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: SMU is initialized successfully!
Aug 25 13:01:33 minipc kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Aug 25 13:01:33 minipc kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
Aug 25 13:01:33 minipc kernel: amdgpu: Virtual CRAT table created for GPU
Aug 25 13:01:33 minipc kernel: amdgpu: Topology: Add dGPU node [0x150e:0x1002]
Aug 25 13:01:33 minipc kernel: kfd kfd: amdgpu: added device 1002:150e
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: SE 1, SH per SE 2, CU per SH 8, active_cu_number 16
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring jpeg_dec_0 uses VM inv eng 1 on hub 8
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: ring vpe uses VM inv eng 4 on hub 8
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: amdgpu: Runtime PM not available
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: [drm] Registered 4 planes with drm panic
Aug 25 13:01:33 minipc kernel: [drm] Initialized amdgpu 3.61.0 for 0000:c6:00.0 on minor 1
Aug 25 13:01:33 minipc kernel: amdgpu 0000:c6:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Aug 25 13:01:34 minipc kernel: snd_hda_intel 0000:c6:00.1: bound 0000:c6:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Aug 25 13:01:35 minipc sensors[1189]: amdgpu-pci-c600
root@minipc:/etc/default/grub.d#
 
Last edited:
dCipher said:
root@minipc:~# cd /etc/default/grub.d
root@minipc:/etc/default/grub.d# ls
installer.cfg proxmox-ve.cfg
root@minipc:/etc/default/grub.d#
Click to expand...
Editing the kernel parameters is described very differently in the manual (that I linked before): https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysboot_edit_kernel_cmdline
dCipher said:
c6:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Strix [Radeon 880M / 890M] [1002:150e] (rev c1)
Subsystem: Device [1f4c:b020]
Kernel driver in use: amdgpu
Kernel modules: amdgpu
Click to expand...
Looks like the driver loaded all right (Kernel driver in use: amdgpu).
dCipher said:
Aug 25 13:01:33 minipc kernel: Linux version 6.14.8-2-pve (build@proxmox) (gcc (Debi>
Click to expand...
You are on the latest kernel version. The rest of the system logs is cut short (in both directions) and you'll need to investigate it yourself for anything relevant to amdgpu and your issue.
Your hardware is probably too new (or too "laptop-like") and since I don't have similar hardware I don't feel like troubleshooting any further.
 
You must log in or register to reply here.
Top Bottom