I’m assembling my desktop pc, and since I use Qubes, I have a few questions about the compatibility (I want to avoid wasting thousands of $ ):
Question 1: am I right in thinking that the compatibility issue only concerns 3 components: Motherboard, CPU, GPU. Is that right?
Question2: if I purchase the following:
the latest nvidia gpu (RTX 30xx or 40xx)
a good fresh motherboard with TPM enabled (qubes requirement)
an Intel CPU with all the qubes requirements (vt-x + vt-d + EPT)
Then there’s literally nothing that can go wrong, am I correct?
1: Yes, but it’s mostly the motherboard and GPU.
2: Keep in mind that Qubes can’t utilize the latest GPUs, getting an RTX 40xx can be a massive waste of money.
Get a motherboard that is confirmed to be working, use the HCL.
Yes, I believe all modern Intel CPUs can run Qubes.
I’m using the MSI Z690 with an Intel 12900K and the GTX1060, I would need to pay +$1000 for an RTX4070 and a used 1060 is $100
opened 10:23PM - 12 Dec 18 UTC
T: bug
C: Xen
P: major
r4.1-buster-stable
hardware support
r4.1-bullseye-stable
r4.1-dom0-stable
needs diagnosis
pr submitted
r4.1-centos-stream8-cur-test
r4.1-bookworm-stable
r4.2-host-cur-test
affects-4.1
affects-4.2
### Qubes OS version:
<!-- (e.g., `R3.2`)
You can get it from the dom0 te… rminal with the command
`cat /etc/qubes-release`
Type below this line. -->
R4.0
### Affected component(s):
intel_pstate
acpi-cpufreq
xenpm
---
### Steps to reproduce the behavior:
<!-- Use single backticks (`) for in-line code snippets and
triple backticks (```) for code blocks.
Type below this line. -->
Tested on:
- Lenovo T480s
- Lenovo X1 Carbon Gen. 6
- Huawei Matebook X Pro.
All with Intel i7-8550U.
Latest BIOS revisions for the respective systems as of Dec. 2018
Kernel: 4.19.2-3.pvops.qubes.x86_64.
EFI install.
In dom0, `sudo xenpm get-cpufreq-para`
### Expected behavior:
The processor is rated at 1.8 GHz (4.0 turbo), so we would expect to see appropriate scaling in that range, available frequencies from 1800000 - 4000000.
Further, we would expect to see `scaling_driver = intel_pstate`.
### Actual behavior:
The CPU frequencies do not scale correctly. Why?
Frequencies are pinned at 2 GHz max, 400 MHz min, across all cores.
```
# xenpm cpu-freq-para
...
cpu id : 0
affected_cpus : 0
cpuinfo frequency : max [2001000] min [400000] cur [2001000]
scaling_driver : acpi-cpufreq
scaling_avail_gov : userspace performance powersave ondemand
current_governor : ondemand
ondemand specific :
sampling_rate : max [10000000] min [10000] cur [20000]
up_threshold : 80
scaling_avail_freq : 2001000 2000000 1900000 1800000 1700000 1500000 1400000 1300000 1200000 1100000 1000000 800000 700000 600000 500000 *400000
scaling frequency : max [2001000] min [400000] cur [400000]
turbo mode : enabled
...
```
Confirmed with `watch -n1 "cat /proc/cpuinfo | grep \"[c]pu MHz\""`
`xenpm set-scaling-maxfreq` and `-minfreq` have no effect.
`xenpm get-cpufreq-states` shows 16 total/usable P-states.
Changing the governor to `performance` has no effect. Default is `ondemand`
`dmidecode` reports a max of 2 GHz on the Lenovos, and an apparently erroneous speed on the Huawei (~ 8 GHz).
```
# dmidecode | grep -i speed
Speed: 2400 MT/s
Configured Clock Speed: 2400 MT/s
Speed: 2400 MT/s
Configured Clock Speed: 2400 MT/s
Speed: Unknown
Speed: Unknown
Speed: Unknown
Max Speed: 2000 MHz
Current Speed: 1800 MHz
```
The `scaling_driver` is legacy `acpi-cpufreq`. Interestingly, `intel_pstate` can be seen initializing during boot, but it does not take over handling anything. Attempting to `blacklist acpi-cpufreq` in `modprobe.d` has no effect.
```
# dmesg | grep pstate
[ 5.067624] intel_pstate: Intel P-state driver initializing
```
`/sys/devices/system/cpu/intel_pstate/` contains the expected attributes, but as mentioned in the "related issue" linked below, `no_turbo`, `num_pstates`, and `turbo_pct` error `Resource temporarily unavailable`.
`/sys/devices/system/cpu/intel_pstate/status` always returns `off`, and does not respond to `echo "active" >`. This behavior has been tested with various kernel command line parameters, including `intel_pstate=force`, `intel_pstate=disabled`, `intel_pstate=no_hwp`, `intel_pstate=enable` with no change in performance aside from `../cpu/intel_pstate/` attributes disappearing when `no_hwp` or `disabled` were in effect. Also tried `processor.ignore_ppc=1`.
Strangely, none of the appropriate attributes for `cpufreq` exist in `/sys/devices/system/cpu/cpu*/`.
```
# ls /sys/devices/system/cpu/cpu0/
acpi_cppc driver hotplug power topology
cache firmware_node node0 subsystem uevent
```
`lsmod | grep cpufreq` shows no results, trying to `modprobe acpi-cpufreq` or `cpufreq-xen` returns errors. `xen_acpi_processor` is loaded.
```
# modprobe acpi-cpufreq
modprobe: ERROR: could not insert 'acpi_cpufreq': No such device
# modprobe cpufreq-xen
modprobe: FATAL: Module cpufreq-xen not found in directory /lib/modules/4.19.2-3.pvops.qubes.x86_64
```
`cpupower frequency-info` is completely unresponsive, with zero information available about the processor.
```
analyzing CPU 0:
no or unknown cpufreq driver is active on this CPU
CPUs which run at the same hardware frequency: Not Available
CPUs which need to have their frequency coordinated by software: Not Available
maximum transition latency: Cannot determine or is not supported.
Not Available
available cpufreq governors: Not Available
Unable to determine current policy
current CPU frequency: Unable to call hardware
current CPU frequency: Unable to call to kernel
boost state support:
Supported: yes
Active: yes
```
Though it shouldn't have any effect, testing was attempted with `smt=on` and `off`, and `Hyperthreading` enabled/disabled in the BIOS appropriately.
Testing was also performed while toggling various BIOS settings.
- enable/disable `Intel SpeedStep`
- power settings at `Maximum Performance` vs. `Balanced`
It does not appear to be a thermal throttling issue, with idle ~ 37*C and under load ~60*C observed consistently.
`tlp` was tested with no effect on the frequency scaling, regardless of being enabled or disabled. `tlp-stat` yields minimal additional info, with what seems to be an outdated recommendation for the Lenovos to install `tp-smapi kernel modules`, that are in fact deprecated in favor of `thinkpad_acpi`, which appears to be active on the Thinkpads.
```
dmesg | grep thinkpad
[ 19.589434] thinkpad_acpi: ThinkPad ACPI Extras v0.26
[ 19.589439] thinkpad_acpi: http://ibm-acpi.sf.net/
[ 19.589440] thinkpad_acpi: ThinkPad BIOS N22ET50W (1.27 ), EC unknown
[ 19.589441] thinkpad_acpi: Lenovo ThinkPad T480s, model 20L7CTO1WW
[ 19.591883] thinkpad_acpi: radio switch found; radios are enabled
[ 19.591898] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver
[ 19.591899] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
[ 19.612278] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is unblocked
[ 19.643468] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one
[ 19.674512] thinkpad_acpi: battery 1 registered (start 0, stop 100)
[ 19.674576] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/
```
`thermald` is not loaded.
### General notes:
https://www.kernel.org/doc/html/v4.12/admin-guide/pm/intel_pstate.html
- This link suggests removing `irqbalance` but I'm skeptical.
https://askubuntu.com/questions/1067866/ubuntu-18-04-steam-games-frame-rate-drop/1073353#1073353?newreg=c7c120f373da4effb7317104571cd573
- https://cateee.net/lkddb/web-lkddb/XEN_ACPI_PROCESSOR.html
Regarding xen_acpi_processor: "It also registers itself as the SMM so that other drivers (such as ACPI cpufreq scaling driver) will not load."
How could `lsmod` report `xen_acpi_processor` as loaded but `xenpm` shows the scaling driver `acpi-cpufreq` ? This might make sense as to the missing `/sys/devices/.../cpufreq` entries.
- The following exchange is dubious at best, the final post gets down to the point of disabling intel microcode. They also suggest the use of `msr-tools`, but that really shouldn't be necessary.
https://bbs.archlinux.org/viewtopic.php?id=231077
- This is good work, but in my opinion, running a script every few seconds in dom0 isn't a legitimate fix.
https://github.com/erpalma/lenovo-throttling-fix
---
### Related issues:
https://github.com/QubesOS/qubes-issues/issues/4491
https://github.com/QubesOS/qubes-issues/issues/450
opened 03:08AM - 22 Nov 22 UTC
closed 04:38PM - 15 Feb 23 UTC
T: bug
C: installer
P: default
hardware support
affects-4.1
affects-4.2
### Qubes OS release
I tried three qubes isos
1. official Qubes-R4.1.1-x86… _64.iso
2. Qubes-20221112-x86_64.iso from qubes.notset.fr
3. Qubes-20221112-kernel-latest-x86_64.iso from qubes.notset.fr
### Brief summary
qubes-os installer isn't working on
Machine
model: PRO Z690-A WIFI DDR4(MS-7D25)
CPU:
12th Gen Intel Core i9-12900K
Graphics
AMD Navi 22 Radeon6700 XT
Memory: 64 GiB ddr4
[dmesg message that I saved before the installer freeze the host](https://gist.github.com/tusind/9a9a7e035743aad721f20747db5b4d75)
### Steps to reproduce
boot from a usb with an intel i9-12900K and amd Radeon6700 XT
the installer failed just before starting the gui installer. the host freeze after it
I tried to install it with uefi mode and legacy mode.
I disabled the onboard nic card and added an external dual 1GB card.
### Expected behavior
have a working qubes-os installation process
### Actual behavior
the host freeze and the installation stop right before starting the gui part.
opened 02:15PM - 17 Feb 21 UTC
T: enhancement
C: Xen
P: major
hardware support
waiting for upstream
C: power management
***Editor's note:** The original issue description below is somewhat out-of-date… . This issue is now narrowly focused on support for the S0ix sleep state (aka "Modern Standby," "Low Power S0 Idle," "InstantGo," "Connected Standby," etc.) found in newer CPUs (especially Tiger Lake and later).*
-----
**The problem you're addressing (if any)**
It appears Qubes does not support Intel's latest version of processors.
**Describe the solution you'd like**
Support for Intel's latest version of their processors (i.e., tiger lake)
**Where is the value to a user, and who might that user be?**
People who want to benefit from the significant performance upgrades of Tiger Lake
**Describe alternatives you've considered**
N/A
**Additional context**
N/A
**Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted**
N/A (I've checked GitHub for any open issues on this but either I've missed it or my SearchFu is weak)
**Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues**
N/A
Also this and probably some more:
opened 10:15AM - 15 Aug 20 UTC
T: bug
C: installer
P: default
hardware support
affects-4.1
**Qubes OS version**
R4.0.3
**Affected component(s) or functionality**
Inst… aller
**Brief summary**
Everything works up until Qubes tries to start an X server.
**To Reproduce**
Steps to reproduce the behavior:
1. Boot from USB.
2. Choose whatever option you like.
3. Wait until the screen with 3 dots goes away. _Kinda awkward that this renders in my opinion._
4. See log in "Additional context."
**Expected behavior**
The X server starts successfully.
**Actual behavior**
The X server fails to start.
**Screenshots**
N/A
**Additional context**
- Secure boot is disabled.
- Legacy support is enabled.
- Legacy boot first is enabled.
<details>
```
Starting installer, one moment...
anaconda 25.20.9-1 for Qubes R4.0.3 started.
* installation for log files are stored in /tmp during the installation
* shell is available on TTY2
* if the graphical interface fails to start, try again with the inst.txt bootoption to start text installation.
* when reporting a bug add logs from /tmp as separate text/plain attachments
XX:XX:XX Not asking for VNC because we don't have a network
XX:XX:XX X startup failed, aborting installation
XX:XX:XX X startup failed, aborting installation
The installation cannot continue and the system will be rebooted
Press ENTER to continue
(Enter)
Pane is dead
```
```
archlinux
description: Notebook
product: 81UH (LENOVO_MT_81UH_BU_idea_FM_Legion Y740-15IRHg)
vendor: LENOVO
version: Lenovo Legion Y740-15IRHg
serial: MP1LENTF
width: 64 bits
capabilities: smbios-3.0.1 dmi-3.0.1 smp vsyscall32
configuration: administrator_password=disabled boot=normal chassis=notebook family=Legion Y740-15IRHg frontpanel_password=disabled keyboard_password=disabled power-on_password=disabled sku=LENOVO_MT_81UH_BU_idea_FM_Legion Y740-15IRHg uuid=6BDA9AE0-6F78-E911-8101-9C5A445184A0
*-core
description: Motherboard
product: LNVNB161216
vendor: LENOVO
physical id: 0
version: SDK0R32862 WIN
serial: MP1LENTF
slot: Type2 - Board Chassis Location
*-firmware
description: BIOS
vendor: LENOVO
physical id: 0
version: BVCN10WW(V1.06)
date: 06/06/2019
size: 128KiB
capacity: 10MiB
capabilities: pci upgrade shadowing cdboot bootselect edd int13floppynec int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int9keyboard int10video acpi usb biosbootspecification uefi
*-cpu
description: CPU
product: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
serial: To Be Filled By O.E.M.
slot: U3E1
size: 4350MHz
capacity: 4500MHz
width: 64 bits
clock: 100MHz
capabilities: lm fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp x86-64 constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d cpufreq
configuration: cores=6 enabledcores=6 threads=12
*-cache:0
description: L1 cache
physical id: 5
slot: L1 Cache
size: 384KiB
capacity: 384KiB
capabilities: synchronous internal write-back unified
configuration: level=1
*-cache:1
description: L2 cache
physical id: 6
slot: L2 Cache
size: 1536KiB
capacity: 1536KiB
capabilities: synchronous internal write-back unified
configuration: level=2
*-cache:2
description: L3 cache
physical id: 7
slot: L3 Cache
size: 12MiB
capacity: 12MiB
capabilities: synchronous internal write-back unified
configuration: level=3
*-memory
description: System Memory
physical id: 25
slot: System board or motherboard
size: 16GiB
*-bank:0
description: SODIMM DDR4 Synchronous 2667 MHz (0.4 ns)
product: RMSA3260ME78HAF-2666
vendor: Ramaxel
physical id: 0
serial: 136581AA
slot: ChannelA-DIMM0
size: 8GiB
width: 64 bits
clock: 2667MHz (0.4ns)
*-bank:1
description: SODIMM DDR4 Synchronous 2667 MHz (0.4 ns)
product: RMSA3260ME78HAF-2666
vendor: Ramaxel
physical id: 1
serial: 1215A28D
slot: ChannelB-DIMM0
size: 8GiB
width: 64 bits
clock: 2667MHz (0.4ns)
*-pci
description: Host bridge
product: 8th Gen Core Processor Host Bridge/DRAM Registers
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 07
width: 32 bits
clock: 33MHz
configuration: driver=skl_uncore
resources: irq:0
*-pci:0
description: PCI bridge
product: Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16)
vendor: Intel Corporation
physical id: 1
bus info: pci@0000:00:01.0
version: 07
width: 32 bits
clock: 33MHz
capabilities: pci pm msi pciexpress normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:121 ioport:4000(size=4096) memory:50000000-640fffff ioport:92000000(size=1048576)
*-display
description: VGA compatible controller
product: TU104BM [GeForce RTX 2080 Mobile]
vendor: NVIDIA Corporation
physical id: 0
bus info: pci@0000:01:00.0
version: a1
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
configuration: driver=nvidia latency=0
resources: irq:180 memory:63000000-63ffffff memory:50000000-5fffffff memory:60000000-61ffffff ioport:4000(size=128) memory:62000000-6207ffff
*-multimedia
description: Audio device
product: TU104 HD Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@0000:01:00.1
version: a1
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:17 memory:64000000-64003fff
*-usb
description: USB controller
product: TU104 USB 3.1 Host Controller
vendor: NVIDIA Corporation
physical id: 0.2
bus info: pci@0000:01:00.2
version: a1
width: 64 bits
clock: 33MHz
capabilities: msi pciexpress pm xhci cap_list
configuration: driver=xhci_hcd latency=0
resources: irq:143 memory:92000000-9203ffff memory:92040000-9204ffff
*-usbhost:0
product: xHCI Host Controller
vendor: Linux 5.8.1-arch1-1 xhci-hcd
physical id: 0
bus info: usb@3
logical name: usb3
version: 5.08
capabilities: usb-2.00
configuration: driver=hub slots=2 speed=480Mbit/s
*-usbhost:1
product: xHCI Host Controller
vendor: Linux 5.8.1-arch1-1 xhci-hcd
physical id: 1
bus info: usb@4
logical name: usb4
version: 5.08
capabilities: usb-3.10
configuration: driver=hub slots=4 speed=10000Mbit/s
*-serial
description: Serial bus controller
product: TU104 USB Type-C UCSI Controller
vendor: NVIDIA Corporation
physical id: 0.3
bus info: pci@0000:01:00.3
version: a1
width: 32 bits
clock: 33MHz
capabilities: msi pciexpress pm bus_master cap_list
configuration: driver=nvidia-gpu latency=0
resources: irq:145 memory:64004000-64004fff
*-generic:0
description: Signal processing controller
product: Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem
vendor: Intel Corporation
physical id: 4
bus info: pci@0000:00:04.0
version: 07
width: 64 bits
clock: 33MHz
capabilities: msi pm bus_master cap_list
configuration: driver=proc_thermal latency=0
resources: irq:16 memory:92410000-92417fff
*-generic:1 UNCLAIMED
description: System peripheral
product: Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
vendor: Intel Corporation
physical id: 8
bus info: pci@0000:00:08.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: msi pm bus_master cap_list
configuration: latency=0
resources: memory:92424000-92424fff
*-generic:2
description: Signal processing controller
product: Cannon Lake PCH Thermal Controller
vendor: Intel Corporation
physical id: 12
bus info: pci@0000:00:12.0
version: 10
width: 64 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list
configuration: driver=intel_pch_thermal latency=0
resources: irq:16 memory:92425000-92425fff
*-usb
description: USB controller
product: Cannon Lake PCH USB 3.1 xHCI Host Controller
vendor: Intel Corporation
physical id: 14
bus info: pci@0000:00:14.0
version: 10
width: 64 bits
clock: 33MHz
capabilities: pm msi xhci bus_master cap_list
configuration: driver=xhci_hcd latency=0
resources: irq:142 memory:92400000-9240ffff
*-usbhost:0
product: xHCI Host Controller
vendor: Linux 5.8.1-arch1-1 xhci-hcd
physical id: 0
bus info: usb@1
logical name: usb1
version: 5.08
capabilities: usb-2.00
configuration: driver=hub slots=16 speed=480Mbit/s
*-usb:0
description: Keyboard
product: ITE Device(8910)
vendor: ITE Tech. Inc.
physical id: 4
bus info: usb@1:4
version: 13.11
capabilities: usb-2.01
configuration: driver=usbhid maxpower=100mA speed=12Mbit/s
*-usb:1
description: Keyboard
product: Corsair Gaming K95 RGB PLATINUM Keyboard
vendor: Corsai
physical id: 6
bus info: usb@1:6
version: 13.11
capabilities: usb-2.00
configuration: driver=usbhid maxpower=100mA speed=12Mbit/s
*-usb:2
description: Video
product: Integrated Camera
vendor: Chicony Electronics Co.,Ltd.
physical id: 7
bus info: usb@1:7
version: 0.27
serial: 0001
capabilities: usb-2.01
configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s
*-usb:3
description: Bluetooth wireless interface
vendor: Intel Corp.
physical id: e
bus info: usb@1:e
version: 0.02
capabilities: bluetooth usb-2.00
configuration: driver=btusb maxpower=100mA speed=12Mbit/s
*-usbhost:1
product: xHCI Host Controller
vendor: Linux 5.8.1-arch1-1 xhci-hcd
physical id: 1
bus info: usb@2
logical name: usb2
version: 5.08
capabilities: usb-3.10
configuration: driver=hub slots=8 speed=10000Mbit/s
*-memory UNCLAIMED
description: RAM memory
product: Cannon Lake PCH Shared SRAM
vendor: Intel Corporation
physical id: 14.2
bus info: pci@0000:00:14.2
version: 10
width: 64 bits
clock: 33MHz (30.3ns)
capabilities: pm bus_master cap_list
configuration: latency=0
resources: memory:92420000-92421fff memory:92426000-92426fff
*-network
description: Wireless interface
product: Wireless-AC 9560 [Jefferson Peak]
vendor: Intel Corporation
physical id: 14.3
bus info: pci@0000:00:14.3
logical name: wlp0s20f3
version: 10
serial: a4:c3:f0:48:3a:14
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=5.8.1-arch1-1 firmware=46.8902351f.0 9000-pu-b0-jf-b0- ip=192.168.0.157 latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:16 memory:92418000-9241bfff
*-serial:0
description: Serial bus controller
product: Cannon Lake PCH Serial IO I2C Controller #0
vendor: Intel Corporation
physical id: 15
bus info: pci@0000:00:15.0
version: 10
width: 64 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=intel-lpss latency=0
resources: irq:16 memory:64100000-64100fff
*-serial:1
description: Serial bus controller
product: Cannon Lake PCH Serial IO I2C Controller #1
vendor: Intel Corporation
physical id: 15.1
bus info: pci@0000:00:15.1
version: 10
width: 64 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=intel-lpss latency=0
resources: irq:17 memory:64101000-64101fff
*-communication:0
description: Communication controller
product: Cannon Lake PCH HECI Controller
vendor: Intel Corporation
physical id: 16
bus info: pci@0000:00:16.0
version: 10
width: 64 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list
configuration: driver=mei_me latency=0
resources: irq:146 memory:92429000-92429fff
*-sata
description: SATA controller
product: Cannon Lake Mobile PCH SATA AHCI Controller
vendor: Intel Corporation
physical id: 17
bus info: pci@0000:00:17.0
version: 10
width: 32 bits
clock: 66MHz
capabilities: sata msi pm ahci_1.0 bus_master cap_list
configuration: driver=ahci latency=0
resources: irq:128 memory:92422000-92423fff memory:9242e000-9242e0ff ioport:5040(size=8) ioport:5048(size=4) ioport:5020(size=32) memory:9242d000-9242d7ff
*-pci:1
description: PCI bridge
product: Cannon Lake PCH PCI Express Root Port #17
vendor: Intel Corporation
physical id: 1b
bus info: pci@0000:00:1b.0
version: f0
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:122 ioport:6000(size=8192) memory:94000000-aa0fffff ioport:70000000(size=570425344)
*-pci:2
description: PCI bridge
product: Cannon Lake PCH PCI Express Root Port #21
vendor: Intel Corporation
physical id: 1b.4
bus info: pci@0000:00:1b.4
version: f0
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:123 memory:92300000-923fffff
*-nvme
description: NVMe device
product: SAMSUNG MZVLB1T0HALR-000L2
vendor: Samsung Electronics Co Ltd
physical id: 0
bus info: pci@0000:3e:00.0
logical name: /dev/nvme0
version: 5L1QEXA7
serial: S3RSNA0M539249
width: 64 bits
clock: 33MHz
capabilities: nvme pm msi pciexpress msix nvm_express bus_master cap_list
configuration: driver=nvme latency=0 nqn=nqn.2014.08.org.nvmexpress:144d144dS3RSNA0M539249 SAMSUNG MZVLB1T0HALR-000L2 state=live
resources: irq:16 memory:92300000-92303fff
*-namespace
description: NVMe disk
physical id: 1
bus info: nvme@0:1
logical name: /dev/nvme0n1
size: 953GiB (1024GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: guid=80d810a0-377f-2342-92ff-13cce4d78d76 logicalsectorsize=512 sectorsize=512 wwid=eui.00253885910a1ab4
*-volume:0 UNCLAIMED
description: Windows FAT volume
vendor: mkfs.fat
physical id: 1
bus info: nvme@0:1,1
version: FAT32
serial: 0a59-a3af
size: 1022MiB
capacity: 1023MiB
capabilities: boot fat initialized
configuration: FATs=2 filesystem=fat
*-volume:1
description: EFI partition
physical id: 2
bus info: nvme@0:1,2
logical name: /dev/nvme0n1p2
serial: cb61dc16-6723-43fa-87cf-0165d4153db9
size: 952GiB
capacity: 952GiB
width: 2954862648 bits
capabilities: encrypted luks initialized
configuration: bits=11544797240 filesystem=luks hash=sha256 version=2
*-pci:3
description: PCI bridge
product: Cannon Lake PCH PCI Express Root Port #13
vendor: Intel Corporation
physical id: 1d
bus info: pci@0000:00:1d.0
version: f0
width: 32 bits
clock: 33MHz
capabilities: pci pciexpress msi pm normal_decode bus_master cap_list
configuration: driver=pcieport
resources: irq:124 ioport:3000(size=4096) memory:92200000-922fffff
*-network
description: Ethernet interface
product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
vendor: Realtek Semiconductor Co., Ltd.
physical id: 0
bus info: pci@0000:3f:00.0
logical name: enp63s0
version: 15
serial: 9c:5a:44:51:84:a0
size: 1Gbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=5.8.1-arch1-1 duplex=full firmware=rtl8168h-2_0.0.2 02/26/15 ip=192.168.0.241 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
resources: irq:16 ioport:3000(size=256) memory:92204000-92204fff memory:92200000-92203fff
*-communication:1
description: Communication controller
product: Cannon Lake PCH Serial IO UART Host Controller
vendor: Intel Corporation
physical id: 1e
bus info: pci@0000:00:1e.0
version: 10
width: 64 bits
clock: 33MHz
capabilities: pm bus_master cap_list
configuration: driver=intel-lpss latency=0
resources: irq:20 memory:64102000-64102fff
*-isa
description: ISA bridge
product: Intel Corporation
vendor: Intel Corporation
physical id: 1f
bus info: pci@0000:00:1f.0
version: 10
width: 32 bits
clock: 33MHz
capabilities: isa bus_master
configuration: latency=0
*-multimedia
description: Audio device
product: Cannon Lake PCH cAVS
vendor: Intel Corporation
physical id: 1f.3
bus info: pci@0000:00:1f.3
version: 10
width: 64 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list
configuration: driver=snd_hda_intel latency=32
resources: irq:178 memory:9241c000-9241ffff memory:92100000-921fffff
*-serial:2
description: SMBus
product: Cannon Lake PCH SMBus Controller
vendor: Intel Corporation
physical id: 1f.4
bus info: pci@0000:00:1f.4
version: 10
width: 64 bits
clock: 33MHz
configuration: driver=i801_smbus latency=0
resources: irq:16 memory:9242b000-9242b0ff ioport:5000(size=32)
*-serial:3
description: Serial bus controller
product: Cannon Lake PCH SPI Controller
vendor: Intel Corporation
physical id: 1f.5
bus info: pci@0000:00:1f.5
version: 10
width: 32 bits
clock: 33MHz
capabilities: bus_master
configuration: driver=intel-spi latency=0
resources: irq:0 memory:fe010000-fe010fff
*-pnp00:00
product: Motherboard registers
physical id: 1
capabilities: pnp
configuration: driver=system
*-pnp00:01
product: Motherboard registers
physical id: 2
capabilities: pnp
configuration: driver=system
*-pnp00:02
product: Motherboard registers
physical id: 3
capabilities: pnp
configuration: driver=system
*-pnp00:03
product: Motherboard registers
physical id: 5
capabilities: pnp
configuration: driver=system
*-pnp00:04
product: AT Real-Time Clock
physical id: 6
capabilities: pnp
configuration: driver=rtc_cmos
*-pnp00:05
product: PnP device INT3f0d
physical id: 7
capabilities: pnp
configuration: driver=system
*-pnp00:06
product: IBM Enhanced keyboard controller (101/2-key)
physical id: 8
capabilities: pnp
configuration: driver=i8042 kbd
*-pnp00:07
product: Motherboard registers
physical id: 9
capabilities: pnp
configuration: driver=system
*-pnp00:08
product: Motherboard registers
physical id: a
capabilities: pnp
configuration: driver=system
*-battery
description: Zinc Air Battery
product: CRB Battery 0
vendor: -Virtual Battery 0-
physical id: 1
version: 08/08/2010
serial: Battery 0
slot: Fake
*-power UNCLAIMED
description: OEM Define 1
product: OEM Define 5
vendor: OEM Define 2
physical id: 2
version: OEM Define 6
serial: OEM Define 3
capacity: 75mWh
```
</details>
**Solutions you've tried**
- I applied what I always did to get the Arch Linux installer to start: Add `nouveau.modeset=0` to the boot configuration.
- I consulted the [NVidia Troubleshooting Guide](https://www.qubes-os.org/doc/nvidia-troubleshooting/) and added `nouveau.modeset=0 rd.driver.blacklist=nouveau video=vesa:off` to my boot configuration.
- I consulted [this](https://www.reddit.com/r/Qubes/comments/i6ey7x/qubes_installation_failure_x_startup_failed/) reddit post. Although I added `xdriver=nouveau` instead of `xdriver=intel`.
**Relevant [documentation](https://www.qubes-os.org/doc/) you've consulted**
- [NVidia Troubleshooting Guide](https://www.qubes-os.org/doc/nvidia-troubleshooting/)
**Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues**
N/A
Be careful with NVidia and consult this: Hardware compatibility list (HCL) | Qubes OS .
1 Like
Also WiFi it seems can cause problems:
I have a new Thinkpad L14 AMD Gen 3 with Ryzen 5875U and WiFi is AMD RZ616(Apparently a rebranded MediaTek MT7922).
With some troubleshooting I was able to install Qubes 4.1.1 and it is now mostly functional.
I applied clocksource=tsc tsc=unstable hpetbroadcast=0 parameters to Grub and the system is now nice and fast. However, I noticed that when only the Ethernet PCI device is attached to sys-net, sys-net boots very fast, but when the WiFi PCI device is attached as well, it takes a long time …
There are lots of HCL reports with both Tiger and Alder Lake systems, saying that it’s not working is a little misleading.
I’m using the 12900K and have been using it for more than 6 months, I know for a fact the R4.1.1 installer works with 12th Gen Intel.
Someone saying it doesn’t work might be true for them and only them.
Yea tbh I don’t even play games so a rtx 30xx/40xx is a huge waste of money, I’ll just grab an used gtx10xx as you suggested, and perhaps upgrade it in the future.
I’m concerned about two things:
the links provided by @fsflover , since I already decided I need the latest gen13 (i9-13900K), I cannot throw away $650 of cpu in case Qubes doesn’t like it
but honestly I wonder what issues could arise, afterall the i9-13900k has ALL the security features qubes wants…
I need a very new motherboard to be able to use ddr5 RAM, I doubt the HCL list has fresh motherboards on it… is the risk of incompatibility high with the motherboard?
There is very little difference between 12th and 13th Gen, I personally wouldn’t be worried about the CPU.
Dasharo might be adding Raptor Lake S support to the Z690, the CPUs are so similar that support can be added though the firmware support package.
If you are looking for one of the new motherboards, use the HCL to find something that worked with 12th gen. There is no guarantee that the next gen will work, but if the Z690 worked, there is a decent chance that the Z790 is going to work. I don’t think the next gen motherboards are going to have a lot of new tech, support for the new intel CPUs and DDR5 was added in the last gen.
You can always try to arrange with the seller that you can return the motherboard for a replacement if it doesn’t work, it’s normally not an issue if you ask for it before you buy.
1 Like
enmus
January 11, 2023, 9:40pm
8
It’s not anymore if CPU HAS everything needed by Qubes. As I see it is now more CPU NOT to has many things offered these days.
For example, I’m almost sure I’ll buy 12800HX. Now, here’s to compare it with said 12900K,
https://ark.intel.com/content/www/us/en/ark/compare.html?productIds=134599,226058
then check what 12800HX doesn't have
, then search this forum on these (especially security features related) terms, and you can get a picture which whatnots might be important to each of us and why…
@renehoj First of all, thank you immensely , your inputs are literally more than the whole documentation is providing me on the latest gen gear.
So, I’ma go for the 13 gen Intel, now all that remains is to decide the motherboard and gpu.
For the GPU I think I’ll go on the 1060 or another one on 10xx series, at least for now.
As for the motherboard , they’re pretty much the same, quote: “There aren’t a lot of differences between the two motherboards. Apart from the reallocated PCIe lanes and a bit higher DDR5 memory clock speed, everything remains the same In Z690 & Z790. ”
Would you say there’s could be some risk of Qubes not working depending if I use ddr5 vs ddr4 attached to Z690/790?
Cuz I’m either going for z690 + ddr4 or z790 + ddr5…
I’m slightly confused/worried about the Dasharo firmware thing, do I need to install it on the motherboard, is that mandatory? plus is that severely hard to accomplish? what’s wrong with the default msi firmware?
Thanks a lot mate
renehoj
January 12, 2023, 7:10pm
10
1: Yes, there is some risk. There is always a chance that the hardware isn’t compatible, unless someone else has confirmed that it works.
I think the best you can do when testing a new motherboard, is to buy it from a seller who will let you return it for a replacement.
2: You don’t need it to use Dasharo, it also only works with the Z690. Dasharo is Coreboot and open source firmware, it’s an option for people who want to use open source firmware.
1 Like
OK, sorry last question, you mention in the HCL list that you have “MSI PRO Z690-A DDR4”, but in your post here MSI Pro Z690-A WiFi DDR4 with Alder Lake 12900K you say in the title you have “MSI PRO Z690-A Wifi DDR4”, please note these are actually two different versions , what’s written on the box?
renehoj
January 12, 2023, 9:05pm
12
You can get the Z690 with and without built-in Wi-Fi, I have the board with Wi-Fi.
The boards are identical apart from the Wi-Fi.
1 Like
redmind
January 17, 2023, 12:48pm
13
I hope I’m not too late with this but I had all sorts of weird issues with GT730 and it all went away once I switched to AMD RX6400 (the simplest AMD GPU I could find). It wasn’t hardware issues as the GT730 was tested ok on windows.
It was my understanding that AMD GPU is more “friendly” to Qubes (or even Linux in general) than NVIDIA, because of drivers and sorts, so I took a leap of faith, put my money on AMD GPU and presto! no more graphics issues.
Hope this helps.
2 Likes
Thanks but I already got an used GTX 1060, since I do not game, and mostly because it’s the same as renehoj from which I’m basing my build (out of fear of it non being compatible with qubes at the end).
@renehoj btw, I’m almost done getting the parts, but I have one question remaining, in the qubes HCL list you state this in the notes in regards to the default motherboard firmware (v1.10): "needs legacy boot, integrated gfx doesn’t work ", does that mean if I set legacy boot Qubes still wont work?
renehoj
January 19, 2023, 6:52pm
15
I couldn’t install Qubes without enabling legacy mode, and the internal graphics didn’t work with legacy mode enabled, but it worked just fine with using a GPU.
I used the stock firmware for 1 day before trying Dasharo, and I have not tried any of the new version, the issue could have been fixed.
Ok great to hear. Sadly atm dasharo doesn’t have support for CPU gen13, so I cannot use that atm, but we’ll see.
I have the gtx 1060 just as you, so I hope if I enable legacy mode it’ll work for me as well x)
renehoj
January 19, 2023, 7:41pm
17
If you get the 13900KS you might be able to use Dasharo in the future, currently it’s only support for the S model CPU that is planned for the Z690 in v1.1.1
But the KS is a lot more expensive than the K model.
The stock firmware support all 13th gen models, but I don’t think they have the resources to add full support to Dasharo.
1 Like
renehoj
January 21, 2023, 10:19pm
18
MSI PRO Z690-A DDR5 coreboot support 13th gen intel processors
It seems like there will might be support for the 13900K with the DDR5 motherboard, maybe it’s only the DDR4 board that only has support for the S model CPU.