Framework 13 laptop ,Nvram locked ,TPM difficulties

Eotis

n00b
2FA
Joined
Nov 19, 2025
Messages
4
Hello to everyone.

I have a Framework 13 laptop with these specs.


Motherboard: Framework FRANBMCPOC AC
Processor: 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz 3.00 GHz

Graphics: Intel Iris xe
Installed RAM: 64.0 GB (63.8 GB usable)
System type: 64-bit operating system, x64-based processor

Bios: Uefi InsydeH20 3.24


Edition: Windows 11 Pro/ AtlasOS
Version: 23H2
Installed: ‎9/‎16/‎2024
OS build: 22631.4169

Intel Chipset driver: 10.1.19502.8391



This processor seems to have difficulty in staying cool. (80-90 C and sometimes reaches 100 under load and can spike to well above 70 when idle) I normally do not use this laptop often because after I bought it and noticed it running hot frequently and the fan comes on super loud, I have been disappointed and decided not to use it heavily.

Recently, I stumbled onto an idea. I have a uefi bios called Insydeh20. At the time my bios was version 3.19. I thought maybe if I updated my bios and drivers that maybe it would help the overheating. So I tried updating to version 3.20 and still my cpu was generating a significant amount of heat. Same as before the update. Then I updated the bios to 3.22 with no change. Now I am currently on bios update 3.24 and it still runs as hot as ever.

Something else strange is that I can be in game playing Skyrim (that's how I test it) and open up a screen that shows my current cpu and gpu utilization. Cpu utilization is always 10% or less but gpu is always maxed out at 100% unless the game is paused.

So, not only did I update the bios and by the way, this bios seems very limited in options that you can set. Even though it has an advanced tab, the advanced tab isn't very deep. I also downloaded and installed the latest drivers bundle from framework:

I am not posting this because I need help with my system heat. I just wanted to give you more details as to what led me to this issue. Apparently, once you update your bios to version 3.22 there is no return. You cannot downgrade. Well there was another unwanted side effect. Before I updated the bios, as far as I knew, I did not have a TPM or if I did, it was not active. After my bios updates, one of them (I'm guessing 3.22) activated the TPM.

Also, through some research I now believe this particular laptop already has the TPM built into the chipset. I believe it is called Intel PTT. I suppose it was dormant until I updated the bios. As I understand it, windows 11 is not supposed to even install on your pc without tpm but maybe because I am running a custom windows, the ptt never activated but now that I've updated the bios, the ptt seems to be active.

By the way, I strongly dislike the TPM and the whole idea of a trusted platform module. One detail I forgot to mention is that my laptop has a dual boot configuration. I have win 11 and LMDE 6. I have had issues in the past where my windows would update and during the update, windows would delete my linux from the boot menu. Well, this time I wasn't even updating windows. I was just updating my bios and somehow it acivated that stupid tpm and that tpm decided that having a linux os on my system and boot menu is untrustworthy.

Well I brought out my trusty LMDE 6 usb live boot and booted from it and opened up the boot repair program. Boot repair fails because it says the nvram is locked. I've never even heard of nvram but I suspected it has something to do with the tpm. I have been researching tpm chips in an attempt to try to disable it and so far the best I have been able to come up with is to disable tpm ownership. At least I think I disabled ownership in an attempt to get the current password and then change it to a password that I will know.

Also when I type in tpm.msc and open up the tpm console, the action list is very limited, The only 2 options it has is clear tpm and prepare tpm but prepare tpm is greyed out and cannot be used. Many of the options I have seen on the web to try to accomplish a task in the tpm console are not listed in mine.

Really, all I want to do is take control of the tpm and disable it, shut it down or turn it off in whatever way possible. I do not want a tpm nor do I need nor appreciate it's existence in my hardware and software environment. Actually would it be possible, even though framework says you cannot downgrade your bios, is there any way to downgrade my bios? I found a tutorial online to reset the mainboard. I followed the tutorial and the bios did not revert back to stock.

Any help and advice will be most welcome and greatly appreciated.
 
Last edited:
you should be able to disable the tpm on the security page in the bios.
the heat sounds about normal for a laptop, though. i have intels that run into the 90s...
maybe try limiting your fps or lower some settings?
 
you should be able to disable the tpm on the security page in the bios.
the heat sounds about normal for a laptop, though. i have intels that run into the 90s...
maybe try limiting your fps or lower some settings?
Thank you for the assistance and advice. For some reason, this insydeh20 bios is very limited and does not allow me to disable it in the bios. When I access my bios it says that TPM is not active but yet when I attempt to boot into my LMDE 6, apparently the TPM does not trust it and has removed it from my boot menu.

After my bios updates, the only way I can boot an OS is to mash f12 on start up to reach a screen with 2 options. Both options say: linpus lite with a string of numbers after it. If I choose the 2nd linpus lite, it takes me to a menu where I have a choice between LMDE 6 and Windows.

For some reason, updating my bios deleted my grub menu and now I can only access my oses with F12.
 
Sounds like the BIOS update just nuked your EFI entries, not TPM deciding Linux is evil. From an LMDE live USB you can either rerun grub-install or use efibootmgr to recreate a proper GRUB entry, then in the Framework BIOS set that as first in the boot order and you should be back to a normal menu instead of mashing F12.

On the TPM side, PTT on these Frameworks is firmware baked, so your realistic options are Clear TPM and leave it unowned, then ignore it; it does not control what OS you boot, and once EFI is fixed LMDE should come up fine regardless of whatever Windows and AtlasOS are doing.
 
Sounds like the BIOS update just nuked your EFI entries, not TPM deciding Linux is evil. From an LMDE live USB you can either rerun grub-install or use efibootmgr to recreate a proper GRUB entry, then in the Framework BIOS set that as first in the boot order and you should be back to a normal menu instead of mashing F12.

On the TPM side, PTT on these Frameworks is firmware baked, so your realistic options are Clear TPM and leave it unowned, then ignore it; it does not control what OS you boot, and once EFI is fixed LMDE should come up fine regardless of whatever Windows and AtlasOS are doing.
op never came back...
 
Back
Top