Search results

You will have to boot in to legacy mode otherwise linux isn't able to grab a clean copy of the rom. With UEFI it only gets a shadow copy. Than you can dump it and fix it with the rom-parser utility. $ git clone https://github.com/awilliam/rom-parser $ cd rom-parser $ make $ cd...

So I'm trying to figure out if I'm also affected by the issue but I'm having trouble with checking if the region exists in ACPI non-volatile storage. $ setpci -s 0000:00:02.0 fc.l 6d9d7018 But I don't find the region 6d9d7018 in /proc/iomem. $ cat /proc/iomem 00000000-00000fff : Reserved...

I'm having the same issue on Proxmox 7.1 with a J3455 (Apollo Lake) Platform. My IOMMU groups are seperated after patching the kernel and enabling the ACS override function. [ 2416.585989] DMAR: DRHD: handling fault status reg 2 [ 2416.586008] DMAR: [DMA Write NO_PASID] Request device...

The J3455 or for that matter the Apollo Lake / Goldmont plus / Gemini Lake platforms are not supported for gvt-g-linux. See here, here, here and here.

Thank you so much. With your information I was able to compile pve-kernel-5.15.12-1-pve_5.15.12-3_amd64 kernel with the proper patches for the J3455 mainboard. Now the acs override works.

Same here.

I think I stumbled upon the same problem. @DeMoB Can you be more specific which terminal commands I do have to execute in order to get the compilation working?

The acs override patch is still not working for J3455 mainboards as stated previously in this thread. There are other threads with the same problem here, here and here. I would really appreciate if someone could write a proper tutorial on how to change the kernel patch...

I worked around the issue by installing proxmox on a external usb to m.2 adapter with my laptop and reinstalling the m.2 media in the hp t620 after the installation was successful. So clearly the installation media wasn't the cause.

Yes, I did. I'm getting the same error. I also tried Easy2Boot and DriveDroid to rule out errors with the USB-Stick.

I'm trying to install Proxmox 6.4-1 on a HP T620 Plus. I flashed the Proxmox VE 6.4 ISO Installer on a 16GB USB-Stick with Balena Etcher. After I selected the first menu entry 'Install Proxmox VE' the installer throws me back to the commandline with an error stating unknown filesystem type...

But @Nazgile94 H470 DeskMini is also a mobo of the 400 series and seems to be having the same issues.

I'm running Proxmox 6.4 with Kernel 5.11.21-1-pve and having some issues with getting the QNAP QNA-UC5G1T to work with my setup. @Patrick01 Can you be more specific about how to block cdc_ether from loading. It seems my system also is suffering from this behaviour. lsmod | grep cdc cdc_ether...

My bad. It's already there: I must have missed it because I was solely focused on the PCIe Passthrough Chapter. On a different note: Do you know why Proxmox keeps grabbing the NVMe with the nvme driver even though I defined a softdep? $ echo "softdep nvme pre: vfio vfio_pci" >>...

Thanks for answering so quickly. Can you please add a note in that regard to the proxmox admin guide?

This is still a issue. I'm not able to change the boot order in the uefi because the changes dont stick. I'm passing through a nvme controller but even though I made the necessary changes in the uefi I will still get thrown into the uefi shell. Something overwrites the boot order. I also tried...

This isnt fixed. I'm passing through a NVMe controller and have no way of changing the boot order.

I'm having the same issue can you describe in more detail what you did to solve the problem. I also passthrough a nvme device but the bootorder in the ovmf (uefi disk) doesnt stick for some reason.

I'm running a ASRock X570 Taichi with a Gigabyte Titan Ridge AIC on Proxmox 6.1-8 with Ryzen 9 3900X. I do want to use the system as a workstation, so I followed the instructions in the wiki and installed the gnome desktop environment. $ inxi -F System: Host: pve-workstation Kernel...