Framework 13 (AMD Ryzen 7040) Sys-net setup failure

[Anneleya]

HCL Report:

---
layout:
  'hcl'
type:
  'Notebook'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  '2.0'
remap:
  'yes'
brand: |
  Framework
model: |
  Laptop 13 (AMD Ryzen 7040Series)
bios: |
  03.05
cpu: |
  AMD Ryzen 5 7640U w/ Radeon 760M Graphics
cpu-short: |
  FIXME
chipset: |
  Advanced Micro Devices, Inc. [AMD] Device [1022:14e8]
chipset-short: |
  FIXME
gpu: |
  Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev cb) (prog-if 00 [VGA controller])
gpu-short: |
  FIXME
network: |
  MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616]
memory: |
  32060
scsi: |

usb: |
  8
certified:
  'no'
versions:
  - works:
      'FIXME:yes|no|partial'
    qubes: |
      R4.2.2
    xen: |
      4.17.4
    kernel: |
      6.9.7-1
    remark: |
      FIXME
    credit: |
      FIXAUTHOR
    link: |
      FIXLINK

Remarks

Pre-install:
Disabled Secure boot
Updated BIOS through EFI

Initial issues with default install settings:
Trackpad does not work
Black screen issue at decrypt screen (Solved by installing with latest Kernel)
During Sys-net setup, this error is tripped:

['/usr/bin/qvm-start', 'sys-firewall'] failed:
stdout:""
stderr:"Start failed: internal error: libxenlight failed to create new domain 'sys-net', see /var/log/libvirt/libxl/libxl-driver.log for details"

The referenced logfile reads:

libxl: libxl_dm.c:2857:stubdom_xswait_cb: Domain 2:Stubdom 3 for 2 startup: startup timed out
libxl: libxl_create.c:1975:domcreate_devmodel_started: Domain 2:device model did not start: -9

Click okay and setup completes, but Sys-net fails to start with the same error.
Ethernet add-on port doesn’t seem to be recognized, is not in the device list.
So no internet, and no USB drives. USB mouse still works for some reason. Retry has the same result.

My sort-of fix (Not particularly experienced here, probably way harder then it needs to be.):
Ran an install without any pre-sets besides the template VMs, then manually created network qubes with salt:

How to configure Qubes OS 4.2 manually?

I got it. For those who will seek it later (1) qubesctl saltutil.sync_all (initial setup of salt) (1.5) qubesctl state.sls qvm.default-dispvm qvm.default-mgmt-dvm (installing default dispvm and mgmt vm for salt) (2) qubesctl top.enable qvm.sys-net qvm.sys-usb (configure your system to have sys-usb and sys-net) (3) qubesctl top.enable qvm.sys-net-as-usbvm pillar=True (configure that sys-net and sys-usb is one vm using configs in pillar directory) (4) qubesctl top.enable qvm.disposable-sys-us…

This fixed the WIFI and USB, but system updates do not work. (UpdateVM not set) From my trawling through the forums (and the absence of the file) it seems I’m at the very least missing /etc/qubes/policy.d/30-user.policy. I’ll have to figure out how to write up something that works tomorrow.

[apparatus]

@Anneleya

Trackpad does not work

You can try this:

No USB with 4.2.0-rc5 on Framework Laptop 13 AMD

@Anneleya

This fixed the WIFI and USB, but system updates do not work. (UpdateVM not set) From my trawling through the forums (and the absence of the file) it seems I’m at the very least missing /etc/qubes/policy.d/30-user.policy. I’ll have to figure out how to write up something that works tomorrow.

You can set the UpdateVM in Qubes Global Config GUI tool → Updates tab.

[Anneleya]

Worked, thank you! Slightly embarrassing that I never looked at the system settings…

Touchpad is back working, Non-Whonix System updates as well.
Whonix is only because it was never set up.
The Sys-net I created before includes USB, which seems to have solved the Ethernet addon-card issue as well.