Are you sure you are even using the Grub-bootloader? Does "cat /proc/cmdline" show your additions, concerning ASPM?
Depending on how you installed, you might be using systemd-boot. Then editing the grub config would of course be pointless. In that case, you would need "/etc/kernel/cmdline".
See...
"/usr/lib/modules/5.15.0-100-generic/kernel/drivers/gpu/drm/i915/i915.ko" is clearly not the correct place for the modules. I have no idea how they ended up there, or what you are actually doing.
Why don't you lose that strange image and do a clean install, like you would do with a bare-metal...
Just a quick comment, concerning the power-consumption, but intentionally not fully tackling your "1 all-in-one machine vs. 2 dedicated machines" thought:
For pass-through to work, you usually completely unload all the relevant drivers from the host OS (Proxmox here). Which means, that this...
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.