While you're here, please consider supporting GamingOnLinux on:
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Reward Tiers: Patreon. Plain Donations: PayPal.
This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!
You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
- GE-Proton 9-23 released with a Battle.net update fix for Linux / Steam Deck
- NVIDIA release new GPU driver updates for Linux and Windows after announcing security issues
- Games to claim from Prime Gaming, Jan 17 edition round-up for SteamOS Linux and Steam Deck
- Cubic Odyssey announced as a fusion of Minecraft and No Man's Sky
- Proton Experimental gets fixes for Marvel Rivals, Sea of Thieves and Stalker 2
- > See more over 30 days here
-
GE-Proton 9-23 released with a Battle.net update fix fo…
- Ali_John -
GE-Proton 9-23 released with a Battle.net update fix fo…
- Kaarlo -
Freejam studio closing with Robocraft and Robocraft 2 s…
- Altefier -
GE-Proton 9-23 released with a Battle.net update fix fo…
- Pyrate -
An idiots guide to setting up Minecraft on Steam Deck /…
- Eike - > See more comments
E.g. https://www.reddit.com/r/buildapc/comments/xypn1m/network_card_intel_ethernet_controller_i225v_igc/ gives a good overview.
As a fix from ASUS (We do not support Linux) seems to be very unlikely the known workaround is to deactivate PCI Power Management via the Linux Kernel at all and always keep any PCI device on full power. This is described to be achieved via setting a global Kernel parameter "pcie_port_pm=off".
However, I do not like the idea to disable the entire feature for any PCI device (which includes PCIe) just because of a single faulty device. I started reading a bit about pci power management (https://docs.kernel.org/power/pci.html). I also found https://wiki.archlinux.org/title/Power_management#Bus_power_management with the intersting part:
So I have
$ lspci -m -v -s 0c:00.0
Device: 0c:00.0
Class: Ethernet controller
Vendor: Intel Corporation
Device: Ethernet Controller I225-V
SVendor: ASUSTeK Computer Inc.
SDevice: Ethernet Controller I225-V
Rev: 03
ProgIf: 00
IOMMUGroup: 20
to retrieve vendor:device ids:
$ lspci -n -s 0c:00.0
0c:00.0 0200: 8086:15f3 (rev 03)
to check that vendor:device is correct:
$ lspci -d 8086:15f3
0c:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 03)
Do I get it right that I would just need to add the file
/etc/udev/rules.d/pci_pm.rules
with the content
# blacklist for pci runtime power management
SUBSYSTEM=="pci", ATTR{vendor}=="0x8086", ATTR{device}=="0x15f3", ATTR{power/control}="on", GOTO="pci_pm_end"
SUBSYSTEM=="pci", ATTR{power/control}="auto"
LABEL="pci_pm_end"
to have the same as "pcie_port_pm=off" but only for the faulty device?
This should work? Shouldn't it? Does anybody has a better idea to apply the workaround of disabling power management?
Any other suggestions or comments?
--
P.S. I hope this is not to technical for the audience here.
Last edited by HerrLange on 2 Oct 2023 at 5:50 pm UTC