Adding a note about the following:
- brightness hotkeys: this is indeed a
libinput
/hid_sensor_hub
comorbidities as described here [SOLVED-GUIDE] 12th gen not sending XF86MonBrightnessUp / Down - Linux - Framework Community - blacklisting or unloading is the Framework recommended workaround until they probably write their own thing? - suspend: kernel reports ACPI PM supports S0 S3 S5, and
/sys/power/mem_sleep
reports[s2idle] deep
- but looks like we were only getting toPM: suspend entry (s2idle)
. Used the suggestedmem_sleep_default=deep nvme.noacpi=1
to get toPM: suspend entry (deep)
.
I didn’t use rd.qubes.hide_all_usb
, opting with a qubes.InputKeyboard
policy as previously mentioned.
I don’t believe these issues are blockers for nominating Framework 13" Intel laptops as community-recommended computers. Going through the criteria for inclusion:
- Qubes installer works without any workarounds.
- Graphics, wireless networking, and audio work out of the box (other than new users learning to attach the mic to a qube of choice).
- 16 GB is possible, prebuilts come in 16 and 32G configs, DIY orders get you 64G.
- Keyboard and touchpad are connected via PS/2 even though this is a laptop. The touchpad is also enumerated over i2c.
- The device is readily available to be purchased. I’ve ordered 4 Framework 13s so far, and in every case I have pushed button
received baconreceived laptop stateside dropshipped from Taiwan in 3 days or less.
Looking forward to additional reports which would be the final barrier to add to the community-recommended list.