If you think it’s the RTC battery, contact Framework Support, they replaced my RTC Battery, free of charge out of warranty.
Various posts in this forum recommend “mem_sleep_default=deep” for increased battery life on the 11th Gen Framework. I also used this setting for years now without problems.
But after updating my BIOS from 3.17 to 3.20, I thought I had bricked my laptop. After putting it to sleep, it would only turn on the fan on high speed, the display would stay black (backlight didn’t turn on), and after 15s or so, would turn off again, only to turn back on after 5s and repeating this forever. Turning it off manually by holding the power button would not help. While it would stay off, the next time I tried to power it on, the same effect happened without me ever being able to boot.
The only way to fix it is resetting the mainboard state by removing the battery and the CMOS battery. The laptop will then show the same effect once (15s high fan speed without backlight), but after turning itself off it will then boot up normally. Phew!
Through trail-and-error I managed to find that this would always happen whenever “mem_sleep_default=deep” is in the kernel command line, and never without. “sleep=deep” alone does not cause the issue.
6 Likes
Thank you so much for pinning down the issue on the sleep mode!
I have exactly the same problem as you described. Now with s2idle sleep it works fine.
Which distro are you using?
Did you already create a bug report for this issue?
I changed the CMOS battery, but had the same issues.
Which distro are you using?
Debian Testing, but I don’t think it matters, the problem seems to lie on the firmware level, not the kernel
Did you already create a bug report for this issue?
No, I’m not actually sure how to do that. I was assuming Framework monitors this thread (they moved my initial report to this one), and are aware of this issue. I might be wrong though, where can I file a bug report? Just sending a message to support?
1 Like
Regarding “Please Note: After updating to 3.20, you will not be able to downgrade to an earlier version.”
Why this restriction? It seems to go against Framework’s philosophy of giving choice & control to the user, and it takes away a useful troubleshooting/recovery option for those who have issues.
Thanks for the report! We will update our release notes.
As a note S3 is not officially supported by intel on 11th Gen and beyond.
1 Like
Yes, I am concerned about doing an update and something going wrong and not being able to undo.
I also think that Framework should say why downgrades are blocked, and not just warn that they are.
Hi all, having a, “Am I being really stupid?” moment…
Got the notification that BIOS version 3.20 is available for my machine - hooray!
I’m running Ubuntu 24.04, so going to use the EFI updater.
I download the file from this link here:
https://downloads.frame.work/bios/Framework_Laptop_13_11th_Gen_Intel_Core_BIOS_3.20_EFI.zip
extract it a USB pen drive,
Reboot, disable Secure Boot
Reboot and boot from USB drive.
At first, shows updating correctly - hooray!
I reboot again after the update, and then go in to the BIOS to re-enable Secure Boot
I notice that the BIOS shows version is still/only 3.17 (now due to this situation I’m not sure what version it was previously…)
VERY STRANGE…
So I go back to the webpage, download the file again to be 200% sure I’m getting the right file, repeat the process all over again, except this time it will not update, saying “Cannot update to the same version as already installed”
But after I boot back into Ubuntu and check the BIOS version again, it is still showing 3.17 !!!
Anyone else had this issue?
Is it possible that a mistake has been made with packaging the wrong firmware file into the EFI ZIP package??
Here is the output of dmidecode:
Vendor: INSYDE Corp.
Version: 03.17
Release Date: 10/27/2022
Address: 0xE0000
product: 11th Gen Intel(R) Core™ i7-1165G7 @ 2.80GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: 6.140.1
Thoughts…?
Can you try upgrading to 3.19 first to see if you are having the same issue?
Check this…and the next few messages after that. It’s a ‘seen’/known issue that somehow still exist:
Evening again,
Cracked it! Reading the posts you linked @Second_Coming, especially about updating the bare motherboard configs, made me think “I wonder if I need to have the power connected?” Apologies if I’ve just plain missed this in the main instructions, but I don’t remember reading it. Anyhow, yesterday I was trying without AC power connected. Today I tried with AC power connected, and also on the LH side of the laptop (usually I have it on the right) - this was from a comment made on the bare motherboard thread which stated the AC needs to be connected on the LH side…
When I did this, I tried to execute the update from the USB again - it told me once again that it couldn’t update to the same version, HOWEVER, when it re-booted it on the initial splash screen it showed the green progress bar which I didn’t get previously, and took 5-10 mins to complete the update. Then when finally booted up again, now shows BIOS version 3.20.
Apologies for changing 2 variables in one try, but it was either having the AC power connected, or having it connected AND on the LH side of the laptop.
2 Likes
@anon81945988 I’m not using the Windows update so I didn’t read those instructions. I’m using Ubuntu so only read the section on the EFI updater. I re-read those this morning, and there isn’t a mention of any need to have AC power connected - perhaps that should be added @Destroya ?
2 Likes
Hi! I’m finally updating my BIOS to the latest version but getting an error. Here’s what I’m doing:
- I downloaded the files [here] (Framework Laptop BIOS and Driver Releases (11th Gen Intel® Core™)) to a USB then unmount and reboot from the USB by pressing F12. I select the USB option from the menu.
- It starts to run the setup script but very quickly crashes with this message: “Security issue on line 1” …(or 11 - can’t recall).
- I type “exit” to get out of the terminal and reboot my machine and go to the internet for help.
Anyone else experiencing this issue?
Another possibly relevant information: I recently updated from Ubuntu 22->24 and found that I was having issues with my WiFi no longer working, which is what prompted me to get around to installing framework updates because I was thinking there may be an issue with my driver. I’m doing this all on ethernet.
Please help!!
It looks like you have Secure Boot enabled; it must be disabled for the EFI updater to work. (This was mentioned in instructions for previous updates, for example 3.17, not sure why it was not mentioned in the latest instructions.)
1 Like
I noticed that the battery icon is showing a lightning bolt but is “using battery power” when I moused over it. UPower status shows “pending-charge”:
native-path: BAT1
vendor: NVT
model: Framewo
serial: 0177
power supply: yes
updated: Fri 26 Jul 2024 10:26:29 PM (6 seconds ago)
has history: yes
has statistics: yes
battery
present: yes
rechargeable: yes
state: pending-charge
warning-level: none
energy: 53.0222 Wh
energy-empty: 0 Wh
energy-full: 53.0376 Wh
energy-full-design: 55.0088 Wh
energy-rate: 0 W
voltage: 17.517 V
charge-cycles: 13
percentage: 99%
capacity: 96.4166%
technology: lithium-ion
icon-name: ‘battery-full-charging-symbolic’
History (rate):
1722029189 0.000 pending-charge
Had been having many problems since new (11th Gen Intel) with battery not charging, CMOS battery dying, and not powering on unless the main battery is disconnected, even needed to replace the main battery on support’s recommendation (but problems remained).
I updated BIOS from 3.06 to 3.17, then 3.20 today and all seemed normal until I check battery status. Concerned that I may be repeating previous sagas with dead battery, not charging and not powering on with connected battery (making this a desktop).
Any advice would be appreciated.
Yes, an older one and have had it from new, but it became unusable for a long time after power on and battery not charging problems. Running Mint but was on MX initially.
Kept on resetting the board at first, changed the ML1220 at least twice and eventually resetting did not work any more. Main battery was then ordered (support diagnosed that) but as I had relocated, I had to wait for months before I could return to fetch the new battery…
So, only managed to persuade the device to charge and run on the new battery recently by some “black magic” trial and error of procedures. And finally, BIOS got and update.
However, I am getting a few hints/reminders of symptoms that make me worry. For example, when I plug in the power, the bolt deos not appear and it still runs on battery until I reboot. And there is that charge-pending status.
Read that Windows does not have these issues, but I am not eager to run that and far prefer Linux especially vs 11.
1 Like
I now do full power off and not use suspend out of caution
1 Like
I do still have them: when I unplug and run on battery and then plug in to charge, the bolt does not appear but if I boot up with power cable, it is there until I unplug and reinserting the cable does the same no-bolt.
Head-scratching stuff…
Will try other OS as you suggested. Thanks for that.
1 Like
Yes:
Plugged in, boot up (normal and expected icon display with bolt)
- unplug (on battery, again normal icon with bolt now gone)
- run down battery for a little bit
- plug in to charge (no bolt in icon, and charge-pending status)
Also, now a new symptom. Powered down device to deal with screw holes. Closed up everything and attempted to boot up but everything was cold and dark, power button did not light up, totally unresponsive. Had to plug in, started up normally but noted that the side LED was orange and battery was 79%. Since it was booted up plugged-in, bolt was showing in the icon and battery status confirmed charging. Then I unplugged and the same repeats …
1 Like
More problems discovered:
It refused to power up after a full shut down even with 70% battery unless I plug in power cable! All was cold and dark, the power button did not light up, I tried a long press, multiple presses, nothing worked. Once the power cable went it, the LED was momentarily orange, then green, and the power button lit up and it booted normally.