# Known issues on early Framework Laptops **URL:** \ **Category:** Framework Laptop 13\ **Created:** [August 7, 2021, 11:35pm UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551 "2021-08-07T23:35:10Z")\ **Posts on this page:** 13\ **Page:** 3
**Author:** ![vaioware](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/vaioware/32/6530_2.png) [@vaioware](https://community.frame.work/u/vaioware)\ **Post date:** [September 10, 2021, 7:40pm UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/47 "2021-09-10T19:40:13Z")
I love Noctua’s brown fans. Gives me a great excuse to shop for PC parts that don’t aesthetically match or anything- just throw an opaque case panel on everything ---
**Author:** ![cameron\_lambert](https://avatars.discourse-cdn.com/v4/letter/c/c68b51/32.png) [@cameron\_lambert](https://community.frame.work/u/cameron_lambert)\ **Post date:** [September 15, 2021, 2:36am UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/48 "2021-09-15T02:36:15Z")
@Alex_Whittemore > PCB designer here - Do you have evidence it was actually impactful on a particular test, or was it designed in as a matter of best practice? Is there something you’re concerned about related to that? I’m thinking about buying one and I’m trying to get as much info as possible about what I might be getting myself into ---
**Author:** ![Alex\_Whittemore](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/alex_whittemore/32/1103_2.png) [@Alex\_Whittemore](https://community.frame.work/u/Alex_Whittemore)\ **Post date:** [September 15, 2021, 3:35am UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/49 "2021-09-15T03:35:06Z")
> [@cameron\_lambert](#): > > Is there something you’re concerned about related to that? Absolutely not, even the opposite. My gut is that it’s intensive butt-covering, but I’d love to find out that the minute impedance discontinuity going into the connector actually does radiate enough to be a problem in testing. ---
**Author:** ![nrp](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/nrp/32/352_2.png) [@nrp](https://community.frame.work/u/nrp)\ **Post date:** [September 15, 2021, 6:20am UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/50 "2021-09-15T06:20:47Z")
We didn’t test it without, so I guess you could call it butt-covering! It is indeed best practice taken from many previous notebooks our manufacturing partner has worked on. ---
**Author:** ![nrp](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/nrp/32/352_2.png) [@nrp](https://community.frame.work/u/nrp)\ **Post date:** [September 21, 2021, 8:04am UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/51 "2021-09-21T08:04:19Z")
We’ve found a workaround for the S4/S0 LED blink issue (which also resolves some other cases where the laptop won’t boot and the LEDs on the side are blinking). We’ve added it to the bottom of the article here: [My Framework Laptop is not powering on](https://knowledgebase.frame.work/en_us/my-laptop-is-not-powering-on-ryQLXvQkt) We’re continuing to work on determining the root cause of the issue in order to resolve it in production. ---
**Author:** ![Foxboron](https://avatars.discourse-cdn.com/v4/letter/f/3be4f8/32.png) [@Foxboron](https://community.frame.work/u/Foxboron)\ **Post date:** [September 21, 2021, 9:55am UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/52 "2021-09-21T09:55:03Z")
There are some ACPI issues on Framework laptops. It reports the TPM2 eventlog over the TPM2 table, but the kernel returns the function which causes the `/sys/kernel/security/tpm0/binary_bios_measurements` file to never be created. It can probably be fixed with a BIOS patch, but the function shouldn’t error without reading it off from the EFI configuration table so I have submitted a patch to try correct the general behaviour. [https://patchwork.kernel.org/project/linux-integrity/patch/20210920203447.4124005-1-morten@linderud.pw/](https://patchwork.kernel.org/project/linux-integrity/patch/20210920203447.4124005-1-morten@linderud.pw/) Should be noted that this isn’t isolated to Framework. I have seen this from other vendors as well. But I have never been capable of reproducing this personally until now 🙂 ---
**Author:** ![CraigO](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/craigo/32/1762_2.png) [@CraigO](https://community.frame.work/u/CraigO)\ **Post date:** [September 21, 2021, 1:18pm UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/53 "2021-09-21T13:18:10Z")
> [@Foxboron](#): > > I have never been capable of reproducing this personally until now Our gain - thanks for helping to diagnose! ---
**Author:** ![Kieran\_Levin](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/kieran_levin/32/110_2.png) [@Kieran\_Levin](https://community.frame.work/u/Kieran_Levin)\ **Post date:** [September 22, 2021, 8:15am UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/55 "2021-09-22T08:15:33Z")
@Foxboron Could you elaborate a little bit more on the ACPI issue you are seeing? We can look at fixing it. ---
**Author:** ![Foxboron](https://avatars.discourse-cdn.com/v4/letter/f/3be4f8/32.png) [@Foxboron](https://community.frame.work/u/Foxboron)\ **Post date:** [September 22, 2021, 8:28am UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/56 "2021-09-22T08:28:12Z")
> [@Kieran\_Levin](#): > > Could you elaborate a little bit more on the ACPI issue you are seeing? We can look at fixing it. I’m not quite sure about the actual issue. It’s a little bit beyond me and hard to debug without having to build and run the kernel on the Framework multiple times. Essentially it seems like `Minimum Log Length` and `Log Address` in the `TPM2` table is wrongly reported? The kernel is unable to take the values and map the memory for the log which abort the function. It can be fetched from the EFI configuration table just fine though. The issue is that it would be easier to debug if I knew what a proper ACPI TPM2 table with an eventlog looked like 🙂 ---
**Author:** ![Alex\_Whittemore](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/alex_whittemore/32/1103_2.png) [@Alex\_Whittemore](https://community.frame.work/u/Alex_Whittemore)\ **Post date:** [October 4, 2021, 12:52pm UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/57 "2021-10-04T12:52:49Z")
> [@nrp](#): > > Touchpad physical click not registering I seem to be having this issue now. My touchpad has worked reliably for a few months, then yesterday I noticed clicks stopped working (crept up on me since I usually tap-to-click by habit). If I push firmly center-bottom, it goes back to working normally, but it seems after a bit it stops registering again. I have to say, it’s REALLY nice to search for an issue like this and very quickly find “yes, it’s a hardware problem we know about and haven’t figured out yet and we’ll send you a new input cover if you want one.” Also the whole “if there’s a problem we’ll send you the parts and you can repair it yourself.” This is exactly what I signed up for. ---
**Author:** ![Alex\_S](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/alex_s/32/24003_2.png) [@Alex\_S](https://community.frame.work/u/Alex_S)\ **Post date:** [November 13, 2021, 8:33pm UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/58 "2021-11-13T20:33:50Z")
Let us know how the temps are, if you add kryonaut to the Framework ---
**Author:** ![Atul\_Ingle](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/atul_ingle/32/2202_2.png) [@Atul\_Ingle](https://community.frame.work/u/Atul_Ingle)\ **Post date:** [March 1, 2022, 5:31am UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/59 "2022-03-01T05:31:52Z")
I’m one of the batch 1 DIYers facing the S4/S0 issue after five months of hiccup-free experience. I’m curious if there’s any update on the root cause of this issue. An RTC mainboard reset fixed it partially — laptop boots up now provided all expansion cards are unplugged. It gives S4/S0 blink codes if try powering it on with all four expansion cards plugged in. My replacement mainboard is on its way. I’ll be happy to send my current mainboard back for analysis. ---
**Author:** ![Ray\_Kiddy](https://avatars.discourse-cdn.com/v4/letter/r/65b543/32.png) [@Ray\_Kiddy](https://community.frame.work/u/Ray_Kiddy)\ **Post date:** [January 6, 2023, 9:32pm UTC](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551/60 "2023-01-06T21:32:18Z")
I have also had an issue, for several months, with the trackpad not accepting clicks. It has been difficult to determine, though, if it is a hw issue or software. I am using Ubuntu 20.04.1. Configuring the trackpad is confusing. (Does it accept 3.find clicks? Does a bottom-middle click act as right click? etc) It would help if there were more tools to test/check the hardware. For example, put an icon into the Favorites bar. Have that icon light up when the hw receives a trackpad signal. Then I can look at it and click around the trackpad and see where it might not be responding. [Previous page](https://community.frame.work/t/known-issues-on-early-framework-laptops/4551.md?page=2)