Search results

Just checked: As expected, the "i915.ko" is part of the "linux-modules-extra" package in recent Ubuntu versions. And I can only guess, that on "minimal" (non standard!) installs, this does most likely NOT get installed by default. Install the matching package and try again.

Judging by the way how the system reports, that there is no i915 driver module, might it be, that this driver module is actually included in the (probably missing) "linux-modules-extra-{kernel-version}" package? Did you by any chance perform a "minimal" install for that Ubuntu VM?

The latest BIOS has vt-d enabled, according to a quick check. See attached screenshot from BIOS 7.70. The Board is using a standard AMI Aptio V BIOS, so of course this is flashable. See the AMI AFU update utility: https://www.ami.com/bios-uefi-utilities/ You'll neeed: - a FAT32 formatted USB...

Small update: My S2600ST issue was solved through a Ethernet NVM-update. The interesting thing is, that the "BAR" errors still persist. However, the devices started working. So, in all honesty, I have no real idea what exactly it is for your i350 controllers. However, it might be worth a try...

I'll have to check, but I think I might be seeing a similar issue on an Intel S2600ST with its Intel X722 interfaces. I'll have to check for NVM updates, though and will also need to do cross-checks with older Kernels.

If you look at the boot-log, it looks like the virtual functions are (at least part of) your problem. Try disabling those and see if it then boots. Besides that I guess the BIOS just doesn't enable enough resources for the scenario where the numerous virtual functions of the i350 are requesting...

You could try booting your Proxmox host with the additional Kernel parameter "pci=realloc" added. Just to see if it is a resource issue, that the Kernel itself can work around.

Check for i219 "ULP". This power-management feature has already been responsible for a lot of issues in the past. On Windows you have a direct driver option to work around it. For Linux, I honestly am not sure how to handle it. But it usually shows with a link down scenario. Often accompanied by...

AER is usually (exceptions prove the rule) one of two things: 1.) Poor PCIe signaling, due to damage, adapters and/or poor layout. 2.) Issues with power-management, that result in pseudo signaling issues. In other words: Power-Management related problems, that look like siganling issues, on the...

You want to pass-through the Intel iGPU, yet your list of blacklisted modules only lists modules for Nvidia and AMD. See the issue? hint: i915. At some point you seem to have tried it on the kernel commandline, but then commented it out again. Right? Next question: Did you pass the PCI-id of...

Forget about the ASPEED! This is the BMC graphics, which only has very rudimentary graphics functions. No video-codec and/or 3D-acceleration. So, scratch that thought! However, you might be lucky: Your CPU does actually have an integrated GPU. See here...

Had an effect just yesterday, that sounds very similar. For me, recreating the EFI-partition without the "Pre-Enroll keys" option solved it. Found the hint online and worked like a charm. Don't know the exact background. As I wrote, just found the information online.

Just FYI, after having tried the opt-in 5.19 kernel some time ago (see https://forum.proxmox.com/threads/opt-in-linux-5-19-kernel-for-proxmox-ve-7-x-available.115090/#post-498817) I now gave the opt-in 6.2 a try. Behavior seemed to be indentical to my experience with 5.19. In general it seems...

See here for how to retrieve the vbios file: https://pve.proxmox.com/wiki/PCI_Passthrough Additional hint: In order to save the legacy vbios, you will most likely need to make sure, that CSM is enabled in your system BIOS and that the "Video" Sub-Option for the CSM-ROM settings is actually set...

Try to use the saved Legacy VBIOS file (option "romfile=") and use legacy boot on your VM. This seems to have the best bet to get this working. At least it does work for my own Win10 VM on CoffeeLake.

OK, so you can scratch my request, as I obviously did not know about that option. Just tested and works fine with 5.15 and 5.19. Now that you mentioned it, I think I remember having read about it some time ago, but then forgot to try it out. Thanks anyway! Much appreciated input.

BTW, another quick question, about the upcoming kernel 5.19: Is there a chance to solve that dreadful simplefb dilemma with the 5.19 configuration, concerning simplefb. I have a Proxmox CoffeeLake system with passed-though iGPU. Up until 5.13 this worked (and still works) beautifully. However...

Tried all three kernel parameters with the current 5.19 pve-kernel. Sadly none brought back the previous functionality, as seen on 5.15. I do not have measurements, but it felt like "voluntary" was the worst, followed by "full" and the most acceptable (yet not nearly as good as on 5.15) was "none".

Just tried the Kernel 5.19 on my Xeon E5 v4 system with passed through GTX 980 Ti under Windows. Experienced massive lags/delays in games. Same setup runs smooth if I switch back to 5.15. I guess there still is work to do. BTW, nothing obvious in the system log, when the delays hit. And the...

Just FYI, the workaround did work perfectly for a Nvidia GTX980 Ti. However, on my other system, where the CoffeeLake iGPU gets passed-through, it did NOT work. I would guess because the GPU is an internal function there, instead of an external card. When the workaround is applied there, it...