Do you think that Framework Laptop 12 (i3-1315U) and (i5-1334U) with Touch-screen, can work with QubesOS?
2 Likes
Sure there is the theoretical possibility. But since it’s on pre-order by the time of writing no one can tell for sure.
Just out of curiosity: Why not buy certified hardware?
2 Likes
ohhhhhhhhhhh. Super. I do search for certified hardware, but it is hard to find more options. Well, I trying to saving money by re-use my 2 Framework Laptop 13; one with Intel Core Ultra 7 165H and regular Intel i7 12th Gen. I bought the first one in Summer 2024 (intel i7 12th Gen) as emergency laptop. Due my Lenovo P51 workstation laptop is in heaven after 8 years of use; in September of 2024, i assemble all the parts to form Framework Laptop 13 of intel Core Ultra 7 165H. Unlucky that Framework Laptop Team is not have none there device certified. I thought at the start will work with any Linux distro at full potential. I encounter let down. In this year of 2025, I discover about the only device certified for QubesOS. I wish to sell this 2 Framework laptop 13. To regret to have it. At website of QubesOS, i can not find where are requirement for the installation.
1 Like
3 Likes
Thank You, I wish try to find way to sell my 2 Framework laptop 13. And buy StarLab laptop.
1 Like
Oh, I can hardly wait for the first reports on the Framework Laptop 12. 12 inches, completely foldable, stylish green casing… I’m very excited. Plus a laptop that can be repaired for a long time and relatively easily… sounds very tempting at least. Let’s see how it turns out. We’ll know more soon 
1 Like
They have already shipped the first few batches now, is there anyone who was fortunate to be among the first to have a hands on it and tried Qubes on it?
1 Like
I will.
I got mine. Tried with 4.3 rc for now.
Stylus and touchscreen are not over USB, it seems.
So touchscreen and stylus works in dom0 without any input forwarding from sys-usb.
I have not gotten to trying out, configuring auto-rotate yet.
The only device specific issue I have encountered is nvme timeouts when writing to disk, causing internment freezing when doing I/O write heavy task or sometimes just randomly when, for example, logging in. Especially visible when restoring from a backup.
I have SN770M ssd.
The nvme issue is fully eliminated by adding Xen parameter dom0_max_vcpus=1.
Of course, now dom0 will only use 1 core.
But with xfce this seems sufficient.
The issue with that workaround is that due to a Xen bug C states after C1 will not be detected by Xen for all but one core, which increases power usage. Though they can still clock down quite a lot it seems, but presumably they use more power than they would without the dom0 max cpus parameter.
CPU frequency scaling is not broken in general though (I have another intel device where it is always stuck at minimum clocks, but here it works fine), single core geekbench if you pin the vm to a p core are close to results on normal linux.
5 Likes
Can you publish an HCL in the forum so that it gets added to the list of supported hardware?
2 Likes
I spoke too soon about fully eliminating the nvme issue.
It seemed gone. Not a single error when restoring backup. Or various use, no visible issue after limiting dom0 to one vcpus.
But now I encountered it two days in a row after not encountering it for a long time.
Yesterday the issue started appearing, and also I didn’t shut down cleanly. Caused LVM to break. Though booting from a live usb and running lvm repair commands and manually changing volume cfg to change revision number to fix mismatch solved the issue. That started after 30 000 seconds of uptime
Today I encountered the issue again. After 5000 seconds of uptime.
At first it was hang that quickly went away, but everything quickly degraded, with time between hangs getting shorter. And I was unable to cleanly shutdown as it kept lvm2 service not shutting down, and syncing timing out, systemd sending sigkills.
Though thankfully this time there was no corruption.
Both times I was using a web development vm with all cores allocated to it. The first time I had just finished running a qubes update.
The second time I had recently started the template of the dev vm.
Both times I was using dom0 latest kernel, one vcpu for dom0, but no pinning.
Will publish an hcl later.
2 Likes
The down side that are not certified with QubesOS as out-of-the-box.