Still happy about every reply that might lead me to a new line of thought. Thanks!
In regard to the initial setup failing/sys-net not starting because of the PCI device (both 4.1 and 4.2-rc5): I solved this with the steps from my initial post when I installed 4.1 again last night to see if I can get this version to work in a way that allows me to quickly prepare some work while I keep figuring this out. I installed 4.1 (no issue with install medium verification still, only 4.2-rc5), didn’t setup any VM, booted, ran echo -n "1" > /sys/bus/pci/devices/<device>/remove as root and then ran /usr/libexec/initial-setup/initial-setup-graphical to run the setup without the PCI device interfering. I don’t think I remember any error while following logs when it ran. I didn’t have much time to work with it but the system looked okay to me. A few errors from different log files and issues I noticed:
Error logs/issues from/in 4.1
error calling qrexec-policy-agent in dom0 <…>
Didn’t happen on most recent reboots. I think this happens when I boot, can’t allow the mouse with my keyboard because anon-whonix setup takes over the focus and I wasn’t able to refocus the form for allowing the mouse, which led me to plugging it back in. I guess confirming it twice with both forms then does this. I now use i3 and I can easily get the focus back to the form so that would make sense.
systemd-vconsole-setup: /usr/bin/setfont failed with exit status 71
I don’t think this is something to be concerned of, noise.
usbguard-daemon: Device insert exception <...> Protocol error
kernel: usb 1-5: can't set config #1, error -71
kernel: usb usb1-port5: disabled by hub (EMI?) re-enabling
I think this might be related to the USB-C port not being supported. Nothing to be concerned of too I’m assuming.
libvirtd: internal error: Unable to reset PCI device 000:00:<ID>.0: no FLR, PM reset or bus reset available
Not too concerned here for now. Should I be?
libvirtd: internal error: Unknown PCI header type '127' for device '0000:0<device>:00.0'
Again, I think this is the WIFI not being supported which would be the fixed issue with sys-net. I didn’t disable the PCI device permanently, which might resolve this altogether as I don’t even need it.
systemd-modules-load: Failed to insert module 'xen_acpi_processor': No such device
Not sure what to comment on this.
Moving windows and hovering over some buttons was stuttering very much without i3 and nouveau.noaccel=1. Similar experience on my old device. With i3 and the kernel parameter, I think it will be no issue.
<several USB devices> client bug: event processing lagging behind by 15ms, your system is too slow
Saw this in other threads related to moving windows. After installing i3 and increasing RAM in sys-usb and other sys-* VMs, I didn’t see this anymore yet.
I think the system does look pretty much good like this. Please correct me if I’m wrong. So 4.1 with a few tricks seems okay at this early stage so far.
I gave Google a try before posting. Will check more in-depth another time including the forum later on.
Mainboard: B760 chipset, 32 GB DDR5 on it
CPU: i5 13th generation
(GPU: GeForce GT 1030)
NV2 NVMe M.2 SSD
Now I will dd 4.2-rc5 on a different USB stick again and install it the very same way I described and did with 4.1 to see how that goes. I will use kernel-latest though. Will document issues and things I notice here in the same manner.
If there is anything that helps you helping me, I’m more than happy to grab the information.
Edit:
I couldn’t even finish the 4.2-rc5 installation with /usr/libexec/initial-setup/initial-setup-graphical. Same errors as described by a different user: AppVMs fail to start on 4.2.0 RC-3 - #9 by b34
4.2-rc5 errors finishing install with /usr/libexec/initial-setup/initial-setup-grahic
failed to load module nvdimm: libbd_nvdimm.so.2: cannot open shared object file: No such file or directory
/usr/lib64/python3.11/site-packages/pyconda/ui/gui/hubs/initi.py line 415 in _on_spoke_clicked
/usr/share/anaconda/addons/org_qubes_os_initial_setup/gui/spokes/qubes_os.py line 658 in refresh self.choice_default_template.set_entry(val)
/usr/share/anaconda/addons/org_qubes_os_initial_setup/gui/spokes/qubes_os.py line 215 in set_entry entry_index = self.entries.index(entry)
ValueError: ‘Fedora 38 Xfce’ is not in list.
Will try one more time and then without kernel-latest.
Interesting enough the installation medium in the boot menu now boots the installed Qubes 4.2 from the NVMe and lsblk shows <device> 8:32 1 0B 0 disk.