Thank you! The trackpoint works fine, but it’s bizarre that the trackpad works for about 10 seconds after logging in. I still can’t open any Qube. Below are some of the errors I’m having.
dom0 kernel: i2c_designware AMDI0010:00: controller timed out
dom0 kernel: pciback 000:01:00.0: not ready 1023ms after FLR; waiting
dom0 kernel: i2c_designware AMDI0010:00: controller timed out
dom0 kernel: pciback 000:01:00.0: not ready 2047ms after FLR; waiting
dom0 kernel: i2c_designware AMDI0010:00: controller timed out
dom0 kernel: pciback 000:01:00.0: not ready 4095ms after FLR; waiting
dom0 kernel: pciback 000:01:00.0: not ready 8191ms after FLR; waiting
I was receiving this error:
dom0 libvirtd[1886]: internal error: libxenlight failed to create new domain 'sys-net'
dom0 libvirtd[1886]: internal error: Unknown PCI header type '127' for device '0000:06:00.0'
dom0 libvirtd[1886]: Failed to reset PCI device: internal error: Unknown PCI header type '127' for device '0000:06:00.0'
So I opened Qubes Manager » sys-net settings » Devices » and removed 06:00.0 Network controller: MEDIATEK Corp., but it still does not work:
$ qvm-start sys-net
Start failed: internal error: libxenlight failed to create new domain 'sys-net', see /var/log/libvirt/libxl/libxl-driver.log for details
/var/log/libvirt/libxl/libxl-driver.log:
libxl: libxl_dm.c:2801:stubdom_xswait_cb: Domain 8:Stubdom 9 for 8 startup: startup timed out
libxl: libxl_create.c:1913:domcreate_devmodel_started: Domain 8:device model did not start: -9
I checked this bug https://github.com/QubesOS/qubes-issues/issues/7717 and ran xl pci-assignable-list. Both my ethernet device and WiFi device are included in the output list, which should be a good sign.
Current problem: no VM will start
E.g. starting vault will claim success (or sometimes the VM will immediately shut down), but I will not be able to open any program, including a terminal. Sometimes the VM will use 100% CPU.
When I run sudo xl console -t pv vault, I get the below:
WARNING: CPU: 0 PID: 1 at kernel/time/clockevents.c:310 clockevents_program_event+0xac/0xf0
And after adding back in the clocksource boot flags mentioned above, I receive the same error:
Is this the kernel crashing and, if so, why?
Thank you for taking the time to read all of this!