Arch Linux

Thingi

Member

Registered: 2024-12-04

Posts: 3

What is the Arch equivilant to this Debian snippet?

I need to convert the following turned into 'Arch language' so to speak...

echo "devices/pci0000:00/0000:00:02.0/sriov_numvfs = 7" > /etc/sysfs.conf

Now I know that file doesn't exist in Arch and I'm supposed to use tmpfiles.d instead but after that it's a bit fuzzy for me.

I get that it's changing a device structure for my hardware and that it's done on boot every time since it'll always be wrong on boot and then sysfs.conf is then doing something (to /dev?) to then make the IR_SOV stuff work properly.

I'm on 12th Gen and having a devil of a time with code43 in Windows for my iGPU during passthru, this command is what I think is the last in my config to make it work properly.

Please go gentle but give it to me a simple as possible...

Thingi

Last edited by Thingi (2025-01-28 19:30:15)

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 8,817

Website

Re: What is the Arch equivilant to this Debian snippet?

Arch doesn't use sysfs.conf, it is parsed by an init script rather than a systemd unit file: https://salsa.debian.org/debian/sysfsut … type=heads

You will have to use tmpfiles.d(5) instead. Sorry.

EDIT: something like this in /etc/tmpfiles.d/fix.conf should work:

w /sys/devices/pci0000:00/0000:00:02.0/sriov_numvfs - - - - 7

Last edited by Head_on_a_Stick (2025-01-28 19:39:34)

---

Jin, Jîyan, Azadî

mackin_cheese

Member

Registered: 2025-01-07

Posts: 274

Re: What is the Arch equivilant to this Debian snippet?

What is the exact issue you are trying to solve? What's happening that's making you go this route

Thingi

Member

Registered: 2024-12-04

Posts: 3

Re: What is the Arch equivilant to this Debian snippet?

Arch doesn't use sysfs.conf, it is parsed by an init script rather than a systemd unit file: https://salsa.debian.org/debian/sysfsut … type=heads

You will have to use tmpfiles.d(5) instead. Sorry.

EDIT: something like this in /etc/tmpfiles.d/fix.conf should work:

w /sys/devices/pci0000:00/0000:00:02.0/sriov_numvfs - - - - 7

Nice one, thank you!

Thingi

Member

Registered: 2024-12-04

Posts: 3

Re: What is the Arch equivilant to this Debian snippet?

What is the exact issue you are trying to solve? What's happening that's making you go this route

What I'm actually trying to do is pass-through my iGPU (Alderlake/12th Gen) to a VM while using my 3080 for my Arch desktop while still having my iGPU as the Primary vid output in BIOS/UEFI. I'm using the latest Promox info on the subject because the Arch Documentation on this isn't the best due to the difference between partitioning the iGPU then passing a sub-class of the iGPU to a VM vs 'real pass-through'.

It doesn't help that 12th gen upwards does not officially support GPU partitioning so hence the reason to go for IR-SOV instead which still isn't playing nicely. What I'm trying to achieve in this:- https://www.derekseaman.com/2024/07/pro … -lake.html but on Arch instead of Proxmox.
 
I can run Arch and a VM (Win 11) using passthrough of my NVidia 3080 via KVM and use the iGPU for my Linux no problems but passing though the iGPU and Onboard Audio and using my 3080 as my 'Host desktop' is being far more problematic.

What I really want is for my JetKVM to connect to the mobo's HDMI and have access to the BIOS while in Arch Desktop from my 3080 HDMI port to my Monitor/TV (with my iGPU disabled in Arch i.e. 915 driver blocked) and then reuse the iGPU for a VM.

I'm using Sunshine/Moonlight for remote access of my main Arch desktop but that's no good for BIOS/UEFI, so essentially I want fully a GPU accelerated Arch remote desktop via sunshine/moonlight, access to BIOS and a VM running Windows also fully GPU accelerated via the iGPU also via Sunshine/Moonlight.

There are 'simpler' methods but all have been a PITA. If I install Arch and use the 3080 as 'Primary' while my iGPU is still enabled in BIOS it messes up Chrome on KDE, it won't even render the Chrome window properly, even with the iGPU screen disabled in KDE. With no iGPU enabled in BIOS it's fine, same can be said when the 915 driver is blocked in Arch too grrrrrr.   

JetKVM-HDMI to iGPU HDMI as Primary in BIOS = full BIOS access (1080p), then iGPU disabled in Arch so the 3080 becomes the Primary 4K VRR/HDR accelerated screen in Arch for use with my TV/Sunshine/Moonlight leaving the iGPU available for a Windows VM (@ 1080p because an EDID of higher res would not play nicely with my JetKVM) is the ultimate goal. Oh and the 3080 must be connected to my monitor via HDMI (well technically it's a LG C2 OLED 4K) for Sunshine/Moonlight to work properly. DisplayPort-to-HDMI Dongles and HDMI Dummy Plugs cause other issues (no VRR / HDR) for my main screen if I do.

 
thingi

Last edited by Thingi (2025-01-29 00:39:53)