---
layout:
'hcl'
type:
'Notebook'
hvm:
'yes'
iommu:
'yes'
slat:
'yes'
tpm:
'unknown'
remap:
'yes'
brand: |
Framework
model: |
Laptop (13th Gen Intel Core)
bios: |
03.04
cpu: |
13th Gen Intel(R) Core(TM) i7-1370P
cpu-short: |
FIXME
chipset: |
Intel Corporation Device [8086:a706]
chipset-short: |
FIXME
gpu: |
Intel Corporation Raptor Lake-P [Iris Xe Graphics] [8086:a7a0] (rev 04) (prog-if 00 [VGA controller])
gpu-short: |
FIXME
network: |
Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz [8086:2725] (rev 1a)
memory: |
65243
scsi: |
usb: |
4
certified:
'no'
versions:
- works:
'FIXME:yes|no|partial'
qubes: |
R4.2.0
xen: |
4.17.2
kernel: |
6.1.62-1
remark: |
FIXME
credit: |
FIXAUTHOR
link: |
FIXLINK
---
Remarks
Submitting a working report for another Intel Raptor Lake Framework - but with Qubes 4.2.0 out of the box.
Before install:
- out of own volition, not influenced by Qubes
- kept AMT/vPro disabled (but interested in testing at some point for
dom0remote control which has some use cases, particularly in testing infrastructure) - BIOS TZ set to Etc/UTC
- kept AMT/vPro disabled (but interested in testing at some point for
- influenced by Qubes
- Secure Boot disabled (but interested in trying to select the Qubes EFI executable as trusted for execution, or add to keklist+esldb alongside other installs)
After install:
Only light testing performed, happy to try specific things upon request.
- working fine
- wifi
- speaker audio
- volume hotkeys (F1/F2/F3)
- lock from inactivity to
xscreensaver - close lid to suspend and resume on open (didn’t really look at sleep state, just “does it wake up again from sleep”)
- Mouse and Touchpad: hardware exposes three different kinds of devices from the underlying touchpad: a Mouse (was default for me), Touchpad, and “ImExPS/2 Generic Explorer Mouse” which is a whole Insyde BIOS thing. The Touchpad device is correctly identified as a touchpad (which gives me tap to click)
- USB/HDMI adapter: display goes into partial mirror in the start, but full mirror/extend works fine. USB mouse works. USB keyboard works after configuring a
qubes.InputKeyboardpolicy.
- does not work out of the box
- brightness hotkeys as reported
- USB ethernet (in this case, a
RTL8153thatsys-netseems to identify and successfully load but can’t seem to DHCP. Further investigation required.)
What happens is you connect USB controller to some wrong qube (that does not redirect input to dom0), will keyboard and mouse still work like in case of PS/2 keyboard/mouse?
Keyboard and PS/2 mouse are via i8042 (PS/2 / IBM AT) controller. Mouse and Touchpad is also via i2c_designware. In other words, the built-in keyboard/touchpad are not via USB.