Talk:Framework Laptop 13
MicroSD/HDMI Support
Updated MicroSD and HDMI to Yes, as both work for me without adjustment on 5.13.13. However, I'm new to both Arch and the wiki, so if there's more concrete testing that needs to be done, just let me know and I'm happy to do it! HDMI and MicroSD happen to be the two cards I have besides USB-C. Jwisser (talk) 19:27, 3 September 2021 (UTC)
s2idle vs s3 suspend. S3 not supported on Tiger Lake?
So according to some sources (namely Jeremy Soller, Principal Engineer at System76), the Tiger Lake CPUs shipped in the Framework Laptop do not support S3 suspend. While S3 suspend does appear to work, this is probably the reason why the kernel chooses s2idle by default. Investigation is needed to determine whether s2idle is fully functional.
- https://twitter.com/jeremy_soller/status/1335591509207384065?ref_src=twsrc%5Etfw
- https://www.reddit.com/r/System76/comments/k7xrtz/ill_have_whatever_intel_was_smoking_when_they/gev9mkp/
HappyMan (talk) 02:12, 17 September 2021 (UTC)HappyMan
Machine Motherboard Versions
The motherboards section mentioned that there should be a way to identify which motherboard model and/or revision is used. I found that inxiAUR reports both by running inxi -Mxxx (you can also just call dmidecode), but I'm not sure how these values vary across laptop configs.
Colorwheel (talk) 19:35, 2 October 2021 (UTC)
Not sure if discussion is best place for this or if we should just add it to the table, but let's find out. dmidecode -t 2) will show just Base Board information (although it needs superuser perms to run where inxi doesn't).
Mine is a
Batch 5 i7-1185G7
Product Name: FRANBMCP08
Version: A8
Tgm4883 (talk) 23:38, 16 November 2021 (UTC)
Mine is:
Batch 2 i5-1240P (DIY)
Product Name: FRANMACP04
Version: A4
CodeAsm (talk) 17:18, 16 June 2023 (UTC)
The product name is based on the smbios name + something else I can't quite figure out. You can find the ones that exist in: https://github.com/FrameworkComputer/framework-system/blob/5b61d74d92a26cd92fb6c651a76071ade128e06c/framework_lib/src/smbios.rs#L107-L118.
So something like FRANMACP04 is FRANMACP, the Alder Lake board, and 04 which seems suspiciously close to Version: A4. Same for FRANBMCP08, that's FRANBMCP, the Tiger Lake board, and 08 which again very close to Version: A8.
Personally, I think something like FRANMACP is hard to grok, and not something someone might have been exposed to. It might be good enough to go by "generation", so "Tiger Lake, "Alder Lake", "Raptor Lake", "Ryzen 7040" etc? It seems unlikely either the CPU or a specific motherboard revision could result in it not booting on Linux at this point, since it's all amd64 CPUs and a UEFI BIOS. Other hardware might cause issues still, but I doubt a CPU would ever be the problem.
Daenney (talk) 14:47, 22 October 2023 (UTC)
BootManager
Hey,
I used `dd` to install an arch linux usb stick, and the Framework laptop's bootloader recognizes the efi partition but when I load it, it flashes a black screen; no error then goes back to the bootloader. Do you think it is my laptop unable to load systemd-boot or grub or is it the laptop or ram?
I tested the ram with the BIOS and there were no errors.
Has anybody else had issues with the bootmanagers and using the bootloader?
Solution
I realized I needed to disable secure boot. I will add to the wiki. Tsangares (talk) 20:09, 25 October 2021 (UTC)
Display
The monitor is 2256 x 1504 (3:2 ratio) and 13.5 inches diagonally (product page). Which is ~11.2 inches horizontally and ~7.5 inches vertically making for a DPI of ~201.
A similar display with a horizontal resolution of 1920px would have a horizontal DPI of ~171.
TylerSzabo (talk) 20:55, 26 January 2022 (UTC)
What about the new 2.8k display framework now ships? Can I use the AMD calibration file? I think it's not the same display at all. Framework now comes with a totally new 2.8k display. Can somebody upload this calibration file?
Danger89 (talk) 09:06, 19 August 2024 (UTC)
- To answer myself: No you can't use the old calibration file for the new 2.8k display. I hope somebody with a screen calibration device can create a new calibration file for the 2.8k display. Thanks! Danger89 (talk) 22:04, 19 August 2024 (UTC)
Again a regression on iwlwifi for AX210 5.16.11 ?
Edit: it looks like with on Linux 5.16.12-arch1-1 it seems back.
kernel: 5.16.11-arch1-2, tested with stable linux-firmware and linux-firmware-git:
[ 9.102715] iwlwifi 0000:aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 9.102823] iwlwifi 0000:aa:00.0: Loaded firmware version: 67.8f59b80b.0 ty-a0-gf-a0-67.ucode [ 9.102824] iwlwifi 0000:aa:00.0: 0x00000000 | ADVANCED_SYSASSERT [ 9.102825] iwlwifi 0000:aa:00.0: 0x00000000 | trm_hw_status0 [ 9.102825] iwlwifi 0000:aa:00.0: 0x00000000 | trm_hw_status1 [ 9.102826] iwlwifi 0000:aa:00.0: 0x00000000 | branchlink2 [ 9.102826] iwlwifi 0000:aa:00.0: 0x00000000 | interruptlink1 [ 9.102827] iwlwifi 0000:aa:00.0: 0x00000000 | interruptlink2 [ 9.102827] iwlwifi 0000:aa:00.0: 0x00000000 | data1 [ 9.102828] iwlwifi 0000:aa:00.0: 0x00000000 | data2 [ 9.102828] iwlwifi 0000:aa:00.0: 0x00000000 | data3 [ 9.102829] iwlwifi 0000:aa:00.0: 0x00000000 | beacon time [ 9.102829] iwlwifi 0000:aa:00.0: 0x00000000 | tsf low [ 9.102830] iwlwifi 0000:aa:00.0: 0x00000000 | tsf hi [ 9.102830] iwlwifi 0000:aa:00.0: 0x00000000 | time gp1 [ 9.102831] iwlwifi 0000:aa:00.0: 0x00000000 | time gp2 [ 9.102831] iwlwifi 0000:aa:00.0: 0x00000000 | uCode revision type [ 9.102832] iwlwifi 0000:aa:00.0: 0x00000000 | uCode version major [ 9.102832] iwlwifi 0000:aa:00.0: 0x00000000 | uCode version minor [ 9.102833] iwlwifi 0000:aa:00.0: 0x00000000 | hw version [ 9.102833] iwlwifi 0000:aa:00.0: 0x00000000 | board version [ 9.102834] iwlwifi 0000:aa:00.0: 0x00000000 | hcmd [ 9.102834] iwlwifi 0000:aa:00.0: 0x00000000 | isr0 [ 9.102835] iwlwifi 0000:aa:00.0: 0x00000000 | isr1 [ 9.102835] iwlwifi 0000:aa:00.0: 0x00000000 | isr2 [ 9.102836] iwlwifi 0000:aa:00.0: 0x00000000 | isr3 [ 9.102836] iwlwifi 0000:aa:00.0: 0x00000000 | isr4 [ 9.102837] iwlwifi 0000:aa:00.0: 0x00000000 | last cmd Id [ 9.102837] iwlwifi 0000:aa:00.0: 0x00000000 | wait_event 9.102838] iwlwifi 0000:aa:00.0: 0x00000000 | l2p_control [ 9.102838] iwlwifi 0000:aa:00.0: 0x00000000 | l2p_duration [ 9.102839] iwlwifi 0000:aa:00.0: 0x00000000 | l2p_mhvalid [ [ 9.102839] iwlwifi 0000:aa:00.0: 0x00000000 | l2p_addr_match [ 9.102840] iwlwifi 0000:aa:00.0: 0x00000000 | lmpm_pmg_sel [ 9.102840] iwlwifi 0000:aa:00.0: 0x00000000 | timestamp [ 9.102841] iwlwifi 0000:aa:00.0: 0x00000000 | flow_handler [ 9.102915] iwlwifi 0000:aa:00.0: Start IWL Error Log Dump: [ 9.102916] iwlwifi 0000:aa:00.0: Transport status: 0x00000042, valid: 7 [ 9.102917] iwlwifi 0000:aa:00.0: 0x201013F2 | ADVANCED_SYSASSERT [ 9.102917] iwlwifi 0000:aa:00.0: 0x00000000 | umac branchlink1 [ 9.102918] iwlwifi 0000:aa:00.0: 0x8045E20E | umac branchlink2 [ 9.102919] iwlwifi 0000:aa:00.0: 0x00000000 | umac interruptlink1 [ 9.102919] iwlwifi 0000:aa:00.0: 0x00000000 | umac interruptlink2 [ 9.102920] iwlwifi 0000:aa:00.0: 0x0000000C | umac data1 [ 9.102920] iwlwifi 0000:aa:00.0: 0x00040000 | umac data2 [ 9.102921] iwlwifi 0000:aa:00.0: 0xDEADBEEF | umac data3 [ 9.102921] iwlwifi 0000:aa:00.0: 0x00000043 | umac major [ 9.102922] iwlwifi 0000:aa:00.0: 0x8F59B80B | umac minor [ 9.102922] iwlwifi 0000:aa:00.0: 0x00011F6F | frame pointer [ 9.102923] iwlwifi 0000:aa:00.0: 0xC0887F34 | stack pointer [ 9.102923] iwlwifi 0000:aa:00.0: 0x00000000 | last host cmd [ 9.102924] iwlwifi 0000:aa:00.0: 0x00000000 | isr status reg [ 9.102973] iwlwifi 0000:aa:00.0: IML/ROM dump: [ 9.102974] iwlwifi 0000:aa:00.0: 0x00000B03 | IML/ROM error/state [ 9.102985] iwlwifi 0000:aa:00.0: 0x0000762F | IML/ROM data1 [ 9.102995] iwlwifi 0000:aa:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
Gbin (talk) 18:37, 2 March 2022 (UTC)
I am running a ax210 on `Linux taxi 5.16.11-arch1-1 #1 SMP PREEMPT Thu, 24 Feb 2022 02:18:20 +0000 x86_64 GNU/Linux` `Bus 003 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth` Let me know how I can help you.
--Tsangares (talk) 00:15, 4 March 2022 (UTC)
Facial Recognition
I am setting up facial recognition and I am trying to make a wiki entry. But I am having difficulties.
Install howdy for facial recognition. It works with /dev/video0 - the normal camera but fails with the IR camera /dev/video1. I installed linux-enable-ir-emitterAUR and ran linux-enable-ir-emitter configure -d /dev/video1 to recieve the output,
INFO: Warning to do not kill the process ! [ WARN:0@0.141] global /build/opencv/src/opencv-4.5.5/modules/videoio/src/cap_gstreamer.cpp (2401) handleMessage OpenCV | GStreamer warning: Embedded video playback halted; module source reported: Could not read from resource. [ WARN:0@0.141] global /build/opencv/src/opencv-4.5.5/modules/videoio/src/cap_gstreamer.cpp (1356) open OpenCV | GStreamer warning: unable to start pipeline [ WARN:0@0.141] global /build/opencv/src/opencv-4.5.5/modules/videoio/src/cap_gstreamer.cpp (862) isPipelinePlaying OpenCV | GStreamer warning: GStreamer: pipeline have not been created CRITICAL: Cannot access to /dev/video1.
Does anybody know how to get the IR working on framework laptop? --Tsangares (talk) 22:56, 11 March 2022 (UTC)
I don't think framework has an IR camera, it has an IR filter lens but I dont think it can recieve an IR signal -- Keloran
12th gen specific page?
Just received my 12th gen upgrade and I was wondering if we should split off the page or have a specific section?
Weird behavior - I need to wait a long time before the trackpad comes up on sddm (with ps/2 on auto or not).
Errors in dmegs pci 0000:00:07.0: DPC: RP PIO log size 0 is invalid [...] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead [...] cros-usbpd-charger cros-usbpd-charger.5.auto: No USB PD charging ports found cros-usbpd-charger cros-usbpd-charger.5.auto: Unexpected number of charge port count cros-usbpd-charger cros-usbpd-charger.5.auto: Failing probe (err:0xffffffb9) cros-usbpd-charger: probe of cros-usbpd-charger.5.auto failed with error -71 [...]
Gbin (talk) 16:45, 15 August 2022 (UTC)
- I think a specific section is enough here. If you have found soultion of your problem, please add it. --Fengchao (talk) 13:34, 30 January 2023 (UTC)
Config file to disable wifi6
The following line does not work for me (this is what's in the wiki at the moment of writing)
options iwlwifi disable_11ax=Y
What I have to do instead is:
options iwlwifi disable_11ax=1
Mattzjack (talk) 05:33, 30 October 2022 (UTC)
Custom Secure Boot keys
No links nor a table of specific models are provided to confirm that enrolling custom secure boot keys are possible. Enrolling custom secure boot keys is serious because depending on the hardware, can lead to soft-bricking the user's device.
https://man.archlinux.org/man/loader.conf.5.en
https://github.com/Foxboron/sbctl/wiki/FAQ#option-rom Nu4425 (talk) 20:39, 25 October 2023 (UTC)
- I cannot test this as I don't own a framework device, but a TPM event log should confirm this. However, I'm uncertain if it alone suffices. See https://github.com/Foxboron/sbctl/wiki/FAQ#option-rom Nu4425 (talk) 21:08, 25 October 2023 (UTC)
Page per mainboard
This page needs a tidy up due to obsolete information and bug fixes that have largely been solved with UEFI, EC and kernel updates. The troubleshooting is also getting unwieldy due to the mix of several generations of Intel mainboards along with the AMD variant and will not get any better when the Intel ultra boards are released in a few months therefore I propose that there should be a separate page for each mainboard generation similarly to how other laptop brand SKUs have their own pages.
I will make a start on separating out the AMD 7040 series. Invverse (talk) 20:02, 4 June 2024 (UTC)
- I have made a start on Framework Laptop 13 (AMD Ryzen 7040 Series) as I own this model. Help would be appreciated if you own another variant - I have created pages for each. Invverse (talk) 22:09, 4 June 2024 (UTC)
- Do you also own the latest 2.8k display? Danger89 (talk) 09:12, 19 August 2024 (UTC)
- I do not, but no you cannot use the calibration files from the older matte display. You will need to buy/borrow a display calibrator or wait for someone to upload their own calibration. Invverse (talk) 09:16, 19 August 2024 (UTC)
- ow too bad, but makes a ton on sense. In that case I need to wait for somebody to upload their new calibration file.
- If somebody is reading this and own the new 2.8k display. Please help us! Danger89 (talk) 22:03, 19 August 2024 (UTC)
- I do not, but no you cannot use the calibration files from the older matte display. You will need to buy/borrow a display calibrator or wait for someone to upload their own calibration. Invverse (talk) 09:16, 19 August 2024 (UTC)
- Do you also own the latest 2.8k display? Danger89 (talk) 09:12, 19 August 2024 (UTC)
Bios updates
In the bottom of the table it says you need to update your bios for the first batch and 2nd batch of AMD. However, I'm now in the first batch for the renewed AMD framework 13 laptop.
I believe this table content is referring to the first framework laptop, right? And not the renewed Framework 13 7640U - 2.8K Display edition?
Maybe make this more clear... Since Framework is start count from Batch #1 again.
Danger89 (talk) 22:01, 19 August 2024 (UTC)
- Correct. Most of this page is horribly out of date now hence why I'm (slowly) trying to separate information out based on model. UEFI versions are omitted from the new page as all laptops now ship with a BIOS that works with Linux - batch 1 was comparatively tiny compared to subsequent runs and customers who had bought this batch would've been contacted directly by FW to let them know an update was required.
- See Framework Laptop 13 (AMD Ryzen 7040 Series) and if you're able to contribute to this page to build it out a bit especially wrt. the new display and webcam please do :) Invverse (talk) 22:50, 19 August 2024 (UTC)
- Also just realised you're the winegui guy, thanks for your hard work :) Invverse (talk) 22:54, 19 August 2024 (UTC)
- Thanks for pointing to that other page as well, I will do my best to contribute.
- Haha, now I'm the WineGUI guy, but yes you're correct. I'm the developer of WineGUI, Mbin, LibreWeb and much more software projects. Thank you so much! Danger89 (talk) 10:31, 20 August 2024 (UTC)
- I updated that other page now as well, I hope you like it. If you want to chat further, feel free to contact me via Matrix, I'm also in #archlinux under the nickname melroy. Danger89 (talk) 15:58, 20 August 2024 (UTC)
- Also just realised you're the winegui guy, thanks for your hard work :) Invverse (talk) 22:54, 19 August 2024 (UTC)
Problems Booting & Disabling Secure Boot sections
I spent this afternoon troubleshooting post codes and struggling to find documentation on the second part of the code, then spent HOURS trying to figure out why my installer wouldn't boot. Turns out my laptop came with secure boot enabled, and it wasn't mentioned anywhere. I have a 16" so I wrote 2 sections the Framework Laptop 16 article, but they might also apply to the 13" Non-bin (talk) 09:28, 4 December 2024 (UTC)
- I'm not sure this needs to be mentioned, I haven't seen a Laptop in years that didn't have Secure Boot enabled out-of-the-box. The installation guide also mentions explicitly that you need to disable it in order to boot the installation medium. Out of interest, can you give more details regarding the post codes you saw when trying to boot an unsigned binary? 6 5 11 9 18 (talk) 09:43, 4 December 2024 (UTC)
- I think I agree. First I added it to the page but then changed my mind and reverted it again. I remember that it also took me a moment to figure this out but it's also sufficiently standard these days. Maybe it can be a bit more prominent in the article. I'll see what I can do. Saraedum (talk) 12:07, 4 December 2024 (UTC)
- I got code A3 which means SMM_S3_SLEEP_CALLBACK, after googling that I tried switching my ram from slot 0 to slot 1 and it booted fine Non-bin (talk) 05:51, 5 December 2024 (UTC)
- My feeling is that it doesn't hurt to have the info there, people who don't need it can just skip it.
- I didn't find the secure boot settings because it wouldn't open because I had a USB plugged in, so I assumed the settings weren't relevant if they wouldn't open Non-bin (talk) 05:54, 5 December 2024 (UTC)
- But it's redundant because it is already mentioned in the installation guide. And it doesn't just apply to Framework, every laptop that came out in the last couple of years comes with secure boot enabled. This information does not belong in individual Laptop wiki pages.
- What exactly do you mean with the settings wouldn't open because you had a USB-stick plugged in? To enter the BIOS you need to press F2 during boot, this should work regardless of any operating systems or peripherals.
- The Information about which slot to use when using a single stick of RAM is good to know and not universal, so adding that sounds pretty reasonable. 6 5 11 9 18 (talk) 15:55, 5 December 2024 (UTC)