AMD iGPU passthrough won't work

jhmc93 said:
output for the above command:

Code: 
IOMMU group 0 00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
IOMMU group 10 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
IOMMU group 11 02:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
IOMMU group 12 03:00.0 Non-Volatile memory controller [0108]: Micron/Crucial Technology P5 Plus NVMe PCIe SSD [c0a9:5407]
IOMMU group 13 04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] [1002:1638] (rev c5)
IOMMU group 14 04:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]
IOMMU group 15 04:00.2 Encryption controller [1080]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
IOMMU group 16 04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
IOMMU group 17 04:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
IOMMU group 18 04:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2] (rev 01)
IOMMU group 19 04:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3]
IOMMU group 1 00:01.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
IOMMU group 20 05:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Zeppelin/Raven/Raven2 PCIe Dummy Function [1022:145a] (rev 81)
IOMMU group 21 05:00.1 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 81)
IOMMU group 2 00:01.3 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
IOMMU group 3 00:02.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
IOMMU group 4 00:02.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
IOMMU group 5 00:08.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
IOMMU group 6 00:08.1 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
IOMMU group 7 00:08.2 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
IOMMU group 8 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51)
IOMMU group 8 00:14.3 ISA bridge [0601]: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
IOMMU group 9 00:18.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 0 [1022:166a]
IOMMU group 9 00:18.1 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 1 [1022:166b]
IOMMU group 9 00:18.2 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 2 [1022:166c]
IOMMU group 9 00:18.3 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 3 [1022:166d]
IOMMU group 9 00:18.4 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 4 [1022:166e]
IOMMU group 9 00:18.5 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 5 [1022:166f]
IOMMU group 9 00:18.6 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 6 [1022:1670]
IOMMU group 9 00:18.7 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Cezanne Data Fabric; Function 7 [1022:1671]
Click to expand...
I have never seen such nice groups on Ryzen except for X570 motherboards. What motherboard are you using?
jhmc93 said:
couldn't find rombar in my bios unfortunately
Click to expand...
Do you mean Resizable Bar? Do you have a link to the motherboard manual?

Have you tried passing only the VGA function without the audio? And also without the romfile?
 
jhmc93 said:
This is my pc:
https://trigkey.com/en-gb/products/trigkey-s5-16g-500g-5800h
Click to expand...
I fear that I might have bitten off more then I can chew. I cannot find anything more that is preventing passthrough and your hardware is just too special with not enough information available. Either find someone else who succeeded with the exact same hardware or dive deeper into ROM-file patching like people did for the 5700U. If the motherboard cannot disable Resizable Bar, it might not ever work. I'm very sorry and I would suggest using a discrete GPU as a work-around but your tiny system won't allow for that (or any other experimentation).
 
leesteken said:
I fear that I might have bitten off more then I can chew. I cannot find anything more that is preventing passthrough and your hardware is just too special with not enough information available. Either find someone else who succeeded with the exact same hardware or dive deeper into ROM-file patching like people did for the 5700U. If the motherboard cannot disable Resizable Bar, it might not ever work. I'm very sorry and I would suggest using a discrete GPU as a work-around but your tiny system won't allow for that (or any other experimentation).
Click to expand...
Well that’s a pain, thanks anyway
 
jhmc93 said:
Well that’s a pain, thanks anyway
Click to expand...
I learned to buy only hardware that is known to work with Linux and passthrough over many years. But some adventurous people have to be the first to do the hard work, and I do thank them. Maybe the people behind the github of the 5700U romfile can help?
 
leesteken said:
I learned to buy only hardware that is known to work with Linux and passthrough over many years. But some adventurous people have to be the first to do the hard work, and I do thank them. Maybe the people behind the github of the 5700U romfile can help?
Click to expand...
Ill find a way somehow. I'll see if someone on here can give me anymore help, if not i'll just have to make do with proxmox's virtual graphics, thanks for your help aanyway
 
what worked for my AMD Ryzen 3 PRO 4350GE with Radeon Graphics is to add nomodeset to the kernel commandline
it has a ton of other stuff there too that I am not certain is really needed but nomodeset was the last part of the puzzle.

i also had to find the gpu rom file.
i found one while searching for the name that popped up when using dmesg | grep amdgpu on the host when it properly loaded there

this is from the VM but the output will be rather similar on the host
[ 4.819988] amdgpu 0000:01:00.0: amdgpu: Fetched VBIOS from ROM BAR
[ 4.822307] amdgpu: ATOM BIOS: 113-RENOIR-034

so I searched for 113-RENOIR-034 and lo and behold someone managed to take out the vbios rom. So that kind a forced me to use seabios as the uefi rom I found did not play nice for me.

if you can't find one then you can create a portable windows (windows to go) and then use CPU-Z to extract the uefi rom or bios rom file depending on your host. I nearly went that route b ut in the nick of time I got it working sparing me this windows step in between.

hope this helps
 
Last edited:
diversity said:
what worked for my AMD Ryzen 3 PRO 4350GE with Radeon Graphics is to add nomodeset to the kernel commandline
it has a ton of other stuff there too that I am not certain is really needed but nomodeset was the last part of the puzzle.

i also had to find the gpu rom file.
i found one while searching for the name that popped up when using dmesg | grep amdgpu on the host when it properly loaded there

this is from the VM but the output will be rather similar on the host
[ 4.819988] amdgpu 0000:01:00.0: amdgpu: Fetched VBIOS from ROM BAR
[ 4.822307] amdgpu: ATOM BIOS: 113-RENOIR-034

so I searched for 113-RENOIR-034 and lo and behold someone managed to take out the vbios rom. So that kind a forced me to use seabios as the uefi rom I found did not play nice for me.

if you can't find one then you can create a portable windows (windows to go) and then use CPU-Z to extract the uefi rom or bios rom file depending on your host. I nearly went that route b ut in the nick of time I got it working sparing me this windows step in between.

hope this helps
Click to expand...
CPU-z doesn’t show anything in the program so can’t download the vbios, I’m also using grub as well not cmdline
Thanks for your input
 
the concept is the same for non grub boot I think.

this is my line after I have sanitized a bit (perhaps still more can be removed just not the nomodeset)
quiet amd_iommu=on iommu=pt initcall_blacklist=sysfb_init video=simplefb ff video=vesafb ff video=efifb ff video=vesa ff disable_vga=1 kvm.ignore_msrs=1 nomodeset

amd_iommu=on is probably no longer needed as well from higher kernels going forward.

you can add this to your grub thingy by following the proxmox guide
https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_edit_kernel_cmdline

in your case that would be

GRUB​

The kernel commandline needs to be placed in the variable
GRUB_CMDLINE_LINUX_DEFAULT in the file /etc/default/grub.
Running
update-grub appends its content to all linux entries in/boot/grub/grub.cfg.

Not sure though if we should still take note of using update-grub
as perhaps the
proxmox-boot-tool refresh
might be enough

I apologize that I have not ready all your thread but I do wish to help out regarding amd iGPU matters if I can as a give back.

What is your current hurdle to jump over?
 
Last edited:
diversity said:
the concept is the same for non grub boot I think.

this is my line after I have sanitized a bit (perhaps still more can be removed just not the nomodeset)
quiet amd_iommu=on iommu=pt initcall_blacklist=sysfb_init video=simplefb ff video=vesafb ff video=efifb ff video=vesa ff disable_vga=1 kvm.ignore_msrs=1 nomodeset

amd_iommu=on is probably no longer needed as well from higher kernels going forward.

you can add this to your grub thingy by following the proxmox guide
https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_edit_kernel_cmdline

in your case that would be

GRUB​

The kernel commandline needs to be placed in the variable
GRUB_CMDLINE_LINUX_DEFAULT in the file /etc/default/grub.
Running
update-grub appends its content to all linux entries in/boot/grub/grub.cfg.

Not sure though if we should still take note of using update-grub
as perhaps the
proxmox-boot-tool refresh
might be enough

I apologize that I have not ready all your thread but I do wish to help out regarding amd iGPU matters if I can as a give back.

What is your current hurdle to jump over?
Click to expand...
It is just not working, I’ve tried it with a Ubuntu live install but it says gpu failure, so obviously it’s something on the proxmox side. I followed the instructions found here as I was told it would work on ryzen 7 5800h, the link here: https://github.com/isc30/ryzen-7000-series-proxmox,
but no luck at all with it, in my gpu-z the bios part comes up with unknown so I’m wondering if it’s possible.
 
jhmc93 said:
It is just not working, I’ve tried it with a Ubuntu live install but it says gpu failure, so obviously it’s something on the proxmox side
Click to expand...
it can never be on the proxmox side as proxmox is just a layer on top of debian which is just yet another lay on linux.

Please be more specific.

Also ubuntu also failed for me while I was at 90% of reaching my goal.

So once again if you are serious about this issue then please be serious about following up.

Look, I can respect if you have moved on. that is fine. But as your/this thread shows up in search results I thought it important that this leads to a solution of some kind.
 
diversity said:
it can never be on the proxmox side as proxmox is just a layer on top of debian which is just yet another lay on linux.

Please be more specific.

Also ubuntu also failed for me while I was at 90% of reaching my goal.

So once again if you are serious about this issue then please be serious about following up.

Look, I can respect if you have moved on. that is fine. But as your/this thread shows up in search results I thought it important that this leads to a solution of some kind.
Click to expand...
I’m all for getting it working, if you can please read through my thread. So you can get a better idea of what some of my outputs are etc. Because right now I’m not on the PC
 
diversity said:
it can never be on the proxmox side as proxmox is just a layer on top of debian which is just yet another lay on linux.

Please be more specific.

Also ubuntu also failed for me while I was at 90% of reaching my goal.

So once again if you are serious about this issue then please be serious about following up.

Look, I can respect if you have moved on. that is fine. But as your/this thread shows up in search results I thought it important that this leads to a solution of some kind.
Click to expand...
Or not
 
diversity said:
it can never be on the proxmox side as proxmox is just a layer on top of debian which is just yet another lay on linux.

Please be more specific.

Also ubuntu also failed for me while I was at 90% of reaching my goal.

So once again if you are serious about this issue then please be serious about following up.

Look, I can respect if you have moved on. that is fine. But as your/this thread shows up in search results I thought it important that this leads to a solution of some kind.
Click to expand...
@diversity are u still there?
 
I will still try and help. what specific hurdle are you facing at the moment?

If you can be forthcoming then that saves me from reading up on a thread of which I have read sooooo many already. some of them end up in success while most just end up abandoned after a while.
 
diversity said:
I will still try and help. what specific hurdle are you facing at the moment?

If you can be forthcoming then that saves me from reading up on a thread of which I have read sooooo many already. some of them end up in success while most just end up abandoned after a while.
Click to expand...
Hello,
thanks for your reply,
so the hurdle I'm facing is I've followed the tutorial in the link above ^ and after getting a windows vm setup i'm getting error 43 and the gpu driver software is crashing on the windows 11 vm.
I hope this shines a bit of light on the issue I'm facing.
regards
 
what specific tutorial are you referring to?

Please remember I am just soo busy that sometimes I have time to write a long wided answer like I do now. But reading up on long threads has never been my strong point if I enter as an advice giver rather than the needer of advice.

So.

Please show us your kernel commands. You use grub that is just fine.
Please output the early boot process of your host using dmesg. it can tell us if you properly integrated your kernal command line options into the boot process.

then show an lspci -k

then we talk further should I have any insights
 
you see, rather than focusing on the Vm it self I would like to tackle this potential problem from the top down.

For example I have tried many configurations for VMs and I like the linux way of booting in where I can see things go right or wrong.
Now if we get a linux VM up and running then we at least know there is hope for you. But then I will withdraw as I no longer care a single tiny Planck unit for windows
 
diversity said:
what specific tutorial are you referring to?

Please remember I am just soo busy that sometimes I have time to write a long wided answer like I do now. But reading up on long threads has never been my strong point if I enter as an advice giver rather than the needer of advice.

So.

Please show us your kernel commands. You use grub that is just fine.
Please output the early boot process of your host using dmesg. it can tell us if you properly integrated your kernal command line options into the boot process.

then show an lspci -k

then we talk further should I have any insights
Click to expand...
it's probably a lot but here's output of dmesg:
Code: 
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.13-3-pve root=/dev/mapper/pve-root ro quiet amd_iommu=on iommu=pt
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Hygon HygonGenuine
[    0.000000]   Centaur CentaurHauls
[    0.000000]   zhaoxin   Shanghai
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000009bfefff] usable
[    0.000000] BIOS-e820: [mem 0x0000000009bff000-0x000000000a000fff] reserved
[    0.000000] BIOS-e820: [mem 0x000000000a001000-0x000000000a1fffff] usable
[    0.000000] BIOS-e820: [mem 0x000000000a200000-0x000000000a20efff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x000000000a20f000-0x00000000cc222fff] usable
[    0.000000] BIOS-e820: [mem 0x00000000cc223000-0x00000000cc3a3fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000cc3a4000-0x00000000cc3f5fff] ACPI data
[    0.000000] BIOS-e820: [mem 0x00000000cc3f6000-0x00000000cc5adfff] ACPI NVS
[    0.000000] BIOS-e820: [mem 0x00000000cc5ae000-0x00000000ccd83fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ccd84000-0x00000000ccdfefff] type 20
[    0.000000] BIOS-e820: [mem 0x00000000ccdff000-0x00000000cdffffff] usable
[    0.000000] BIOS-e820: [mem 0x00000000ce000000-0x00000000cfffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fdffffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000feb80000-0x00000000fec01fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fec10000-0x00000000fec10fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed40000-0x00000000fed44fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fed80000-0x00000000fed8ffff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fedc4000-0x00000000fedc9fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fedcc000-0x00000000fedcefff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000fedd5000-0x00000000fedd5fff] reserved
[    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000060e2fffff] usable
[    0.000000] BIOS-e820: [mem 0x000000060e300000-0x000000062fffffff] reserved
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] efi: EFI v2.7 by American Megatrends
[    0.000000] efi: ACPI=0xcc597000 ACPI 2.0=0xcc597014 TPMFinalLog=0xcc563000 SMBIOS=0xccc27000 SMBIOS 3.0=0xccc26000 MEMATTR=0xc8b82298 MOKvar=0xccc79000
[    0.000000] efi: Remove mem61: MMIO range=[0xf0000000-0xf7ffffff] (128MB) from e820 map
[    0.000000] e820: remove [mem 0xf0000000-0xf7ffffff] reserved
[    0.000000] efi: Remove mem62: MMIO range=[0xfd000000-0xfdffffff] (16MB) from e820 map
[    0.000000] e820: remove [mem 0xfd000000-0xfdffffff] reserved
[    0.000000] efi: Remove mem63: MMIO range=[0xfeb80000-0xfec01fff] (0MB) from e820 map
[    0.000000] e820: remove [mem 0xfeb80000-0xfec01fff] reserved
[    0.000000] efi: Not removing mem64: MMIO range=[0xfec10000-0xfec10fff] (4KB) from e820 map
[    0.000000] efi: Not removing mem65: MMIO range=[0xfed00000-0xfed00fff] (4KB) from e820 map
[    0.000000] efi: Not removing mem66: MMIO range=[0xfed40000-0xfed44fff] (20KB) from e820 map
[    0.000000] efi: Not removing mem67: MMIO range=[0xfed80000-0xfed8ffff] (64KB) from e820 map
[    0.000000] efi: Not removing mem68: MMIO range=[0xfedc4000-0xfedc9fff] (24KB) from e820 map
[    0.000000] efi: Not removing mem69: MMIO range=[0xfedcc000-0xfedcefff] (12KB) from e820 map
[    0.000000] efi: Not removing mem70: MMIO range=[0xfedd5000-0xfedd5fff] (4KB) from e820 map
[    0.000000] efi: Remove mem71: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
[    0.000000] e820: remove [mem 0xff000000-0xffffffff] reserved
[    0.000000] secureboot: Secure boot disabled
[    0.000000] SMBIOS 3.3.0 present.
[    0.000000] DMI: Trigkey S5/S5, BIOS 5800H506 03/29/2023
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 3194.164 MHz processor
[    0.000132] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000134] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000139] last_pfn = 0x60e300 max_arch_pfn = 0x400000000
[    0.000145] MTRR map: 5 entries (3 fixed + 2 variable; max 20), built from 9 variable MTRRs
[    0.000146] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT
[    0.000831] e820: update [mem 0xd0000000-0xffffffff] usable ==> reserved
[    0.000837] last_pfn = 0xce000 max_arch_pfn = 0x400000000
[    0.003589] Using GB pages for direct mapping
[    0.003805] secureboot: Secure boot disabled
[    0.003806] RAMDISK: [mem 0x30c6b000-0x3462cfff]
[    0.003808] ACPI: Early table checksum verification disabled
[    0.003810] ACPI: RSDP 0x00000000CC597014 000024 (v02 ALASKA)
[    0.003813] ACPI: XSDT 0x00000000CC596728 0000DC (v01 ALASKA A M I    01072009 AMI  01000013)
[    0.003817] ACPI: FACP 0x00000000CC3E8000 000114 (v06 ALASKA A M I    01072009 AMI  00010013)
[    0.003820] ACPI: DSDT 0x00000000CC3DF000 008D01 (v02 ALASKA A M I    01072009 INTL 20200717)
[    0.003823] ACPI: FACS 0x00000000CC561000 000040
[    0.003824] ACPI: SSDT 0x00000000CC3EE000 0072B0 (v02 AMD    AmdTable 00000002 MSFT 04000000)
[    0.003826] ACPI: IVRS 0x00000000CC3ED000 0001A4 (v02 AMD    AmdTable 00000001 AMD  00000000)
[    0.003828] ACPI: SSDT 0x00000000CC3E9000 003A21 (v01 AMD    AMD AOD  00000001 INTL 20200717)
[    0.003829] ACPI: FIDT 0x00000000CC3DE000 00009C (v01 ALASKA A M I    01072009 AMI  00010013)
[    0.003831] ACPI: MCFG 0x00000000CC3DD000 00003C (v01 ALASKA A M I    01072009 MSFT 00010013)
[    0.003833] ACPI: HPET 0x00000000CC3DC000 000038 (v01 ALASKA A M I    01072009 AMI  00000005)
[    0.003834] ACPI: FPDT 0x00000000CC3DB000 000044 (v01 ALASKA A M I    01072009 AMI  01000013)
[    0.003836] ACPI: VFCT 0x00000000CC3CD000 00D884 (v01 ALASKA A M I    00000001 AMD  31504F47)
[    0.003838] ACPI: TPM2 0x00000000CC3CC000 00004C (v04 ALASKA A M I    00000001 AMI  00000000)
[    0.003839] ACPI: SSDT 0x00000000CC3C6000 005354 (v02 AMD    AmdTable 00000001 AMD  00000001)
[    0.003841] ACPI: CRAT 0x00000000CC3C5000 000F38 (v01 AMD    AmdTable 00000001 AMD  00000001)
[    0.003842] ACPI: CDIT 0x00000000CC3C4000 000029 (v01 AMD    AmdTable 00000001 AMD  00000001)
[    0.003844] ACPI: SSDT 0x00000000CC3C3000 000149 (v01 AMD    AmdTable 00000001 INTL 20200717)
[    0.003846] ACPI: SSDT 0x00000000CC3C1000 00148E (v01 AMD    AmdTable 00000001 INTL 20200717)
[    0.003847] ACPI: SSDT 0x00000000CC3BF000 00151E (v01 AMD    AmdTable 00000001 INTL 20200717)
[    0.003849] ACPI: SSDT 0x00000000CC3BE000 00078E (v01 AMD    AmdTable 00000001 INTL 20200717)
[    0.003850] ACPI: SSDT 0x00000000CC3BD000 000641 (v01 AMD    AmdTable 00000001 INTL 20200717)
[    0.003852] ACPI: SSDT 0x00000000CC3B9000 00386E (v01 AMD    AmdTable 00000001 INTL 20200717)
[    0.003854] ACPI: WSMT 0x00000000CC3B8000 000028 (v01 ALASKA A M I    01072009 AMI  00010013)
[    0.003855] ACPI: APIC 0x00000000CC3B7000 0000DE (v04 ALASKA A M I    01072009 AMI  00010013)
[    0.003857] ACPI: SSDT 0x00000000CC3B6000 00008D (v01 AMD    AmdTable 00000001 INTL 20200717)
[    0.003858] ACPI: SSDT 0x00000000CC3B5000 0008F0 (v01 AMD    AmdTable 00000001 INTL 20200717)
[    0.003860] ACPI: Reserving FACP table memory at [mem 0xcc3e8000-0xcc3e8113]
[    0.003861] ACPI: Reserving DSDT table memory at [mem 0xcc3df000-0xcc3e7d00]
[    0.003861] ACPI: Reserving FACS table memory at [mem 0xcc561000-0xcc56103f]
[    0.003861] ACPI: Reserving SSDT table memory at [mem 0xcc3ee000-0xcc3f52af]
[    0.003862] ACPI: Reserving IVRS table memory at [mem 0xcc3ed000-0xcc3ed1a3]
[    0.003862] ACPI: Reserving SSDT table memory at [mem 0xcc3e9000-0xcc3eca20]
[    0.003863] ACPI: Reserving FIDT table memory at [mem 0xcc3de000-0xcc3de09b]
[    0.003863] ACPI: Reserving MCFG table memory at [mem 0xcc3dd000-0xcc3dd03b]
[    0.003863] ACPI: Reserving HPET table memory at [mem 0xcc3dc000-0xcc3dc037]
[    0.003864] ACPI: Reserving FPDT table memory at [mem 0xcc3db000-0xcc3db043]
[    0.003864] ACPI: Reserving VFCT table memory at [mem 0xcc3cd000-0xcc3da883]
[    0.003865] ACPI: Reserving TPM2 table memory at [mem 0xcc3cc000-0xcc3cc04b]
[    0.003865] ACPI: Reserving SSDT table memory at [mem 0xcc3c6000-0xcc3cb353]
[    0.003865] ACPI: Reserving CRAT table memory at [mem 0xcc3c5000-0xcc3c5f37]
[    0.003866] ACPI: Reserving CDIT table memory at [mem 0xcc3c4000-0xcc3c4028]
[    0.003866] ACPI: Reserving SSDT table memory at [mem 0xcc3c3000-0xcc3c3148]
[    0.003867] ACPI: Reserving SSDT table memory at [mem 0xcc3c1000-0xcc3c248d]
[    0.003867] ACPI: Reserving SSDT table memory at [mem 0xcc3bf000-0xcc3c051d]
[    0.003867] ACPI: Reserving SSDT table memory at [mem 0xcc3be000-0xcc3be78d]
[    0.003868] ACPI: Reserving SSDT table memory at [mem 0xcc3bd000-0xcc3bd640]
[    0.003868] ACPI: Reserving SSDT table memory at [mem 0xcc3b9000-0xcc3bc86d]
[    0.003869] ACPI: Reserving WSMT table memory at [mem 0xcc3b8000-0xcc3b8027]
[    0.003869] ACPI: Reserving APIC table memory at [mem 0xcc3b7000-0xcc3b70dd]
[    0.003870] ACPI: Reserving SSDT table memory at [mem 0xcc3b6000-0xcc3b608c]
[    0.003870] ACPI: Reserving SSDT table memory at [mem 0xcc3b5000-0xcc3b58ef]
[    0.003925] No NUMA configuration found
[    0.003926] Faking a node at [mem 0x0000000000000000-0x000000060e2fffff]
[    0.003930] NODE_DATA(0) allocated [mem 0x60e2d5000-0x60e2fffff]
[    0.004026] Zone ranges:
[    0.004027]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.004028]   DMA32    [mem 0x0000000001000000-0x00000000ffffffff]
[    0.004029]   Normal   [mem 0x0000000100000000-0x000000060e2fffff]
[    0.004030]   Device   empty
[    0.004031] Movable zone start for each node
[    0.004031] Early memory node ranges
[    0.004032]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.004033]   node   0: [mem 0x0000000000100000-0x0000000009bfefff]
[    0.004033]   node   0: [mem 0x000000000a001000-0x000000000a1fffff]
[    0.004034]   node   0: [mem 0x000000000a20f000-0x00000000cc222fff]
[    0.004034]   node   0: [mem 0x00000000ccdff000-0x00000000cdffffff]
[    0.004035]   node   0: [mem 0x0000000100000000-0x000000060e2fffff]
[    0.004037] Initmem setup node 0 [mem 0x0000000000001000-0x000000060e2fffff]
[    0.004039] On node 0, zone DMA: 1 pages in unavailable ranges
[    0.004050] On node 0, zone DMA: 96 pages in unavailable ranges
[    0.004141] On node 0, zone DMA32: 1026 pages in unavailable ranges
[    0.007353] On node 0, zone DMA32: 15 pages in unavailable ranges
[    0.007393] On node 0, zone DMA32: 3036 pages in unavailable ranges
[    0.031481] On node 0, zone Normal: 8192 pages in unavailable ranges
[    0.031524] On node 0, zone Normal: 7424 pages in unavailable ranges
[    0.031710] ACPI: PM-Timer IO Port: 0x808
[    0.031717] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[    0.031729] IOAPIC[0]: apic_id 33, version 33, address 0xfec00000, GSI 0-23
[    0.031734] IOAPIC[1]: apic_id 34, version 33, address 0xfec01000, GSI 24-55
[    0.031735] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[    0.031737] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[    0.031739] ACPI: Using ACPI (MADT) for SMP configuration information
[    0.031740] ACPI: HPET id: 0x10228201 base: 0xfed00000
[    0.031743] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back