Was able to recover. Disconnected the battery and plugged via AC only and it worked, then re-connected the battery and it works too. Hope it helps if anyone is hitting the same issue.
1 Like
Besides the problems I have reported, what does āEnhanced fan detection logic within the Input Module appā mean? What is the input module on the Framework Laptop 13?
1 Like
No issues on my FW13 after update done through fwupd.
Update from 3.17 to 3.18 went smoothly.
Hardware : AMD Ryzenā¢ 7 7840U w/ Radeonā¢ 780M Graphics Ć 16, 32.0 GiB RAM, 1.0 TB Disk
Software : Fedora Linux 42, Linux 6.18.6-100.fc42.x86_64
So maybe the update had succeeded, but it failed to put everything back in the correct state for normal use, instead leaving it stuck in a weird state with no way out. I would have hoped such a state didnāt exist at all.
Had you previously tried, while the screen was on but blank, holding in the power button for about 20 seconds to try to cut the power?
As I mentioned previously thatās how every update went so far - the update would seemingly complete but then the screen goes blank, caps lock light stops responding and fans get very loud, turning the laptop off and on would work just fine until this time. not sure what you meant by holding the power button for 20s, does it do anything special beyond just holding it for a few seconds which would turn off the laptop? (power led light goes off)
Update from 3.17 to 3.18 went well, with EFI shell.
Yes, apologies. I didnāt properly think through what you had already written. You must already know how long the power button normally needs to be held in to cut the power. Yes it is usually much less than 20 seconds.
This is no longer in beta and yet the repository still hasnāt been updated. Whatās the hold up?
1 Like
Why did it change to stable when two users reported massive problems?
Edit: three users, see Framework 13 7840u hanging on POST with Dell U2725QE monitor and an unacceptable support experience
Seems those are not reported on Github, atleast i canāt find them there.
No, I only posted about my issues here in the hope that someone from Framework would read it.
I think I would get bitten by āexternal dock has devices connected via USB4 (Thunderbolt) issueā and I didnāt get a chance to provide beta feedback before it was marked as STABLE ā Iām not updating and think that this was hasty.
This release broke my dock (CalDigit TS4). When booting the laptop via āPower on AC attachā, both the internal and external monitor stay black forever. Tapping the power button will instantly turn it off. I donāt have to hold the power button for several seconds, so it looks like it is not even getting to GRUB.
Workaround: Only connect the dock after GRUB has flashed. If you canāt plug/unplug easily because you have an under-the-desk setup like me, turn your setup/plugbar on, immediately turn it off again and wait 10 seconds before turning it back on.
I am seeing the exact same issue with a Lenovo ThinkPad USB-C Dock Gen 2 (40AS). If I power it on without the dock, all is fine. In my case, with an on-desk setup, I just plug it in after I get the Linux disk encryption prompt, and the USB keyboard starts working, and it then even shows the prompt on my external screen as well after which I close the lid. Just slightly a little bit annoying TBH. But what was most scary was during BIOS update itself when it just went black and died! Had me worry just a little there hahaha.
1 Like
Reported the issue.
3 Likes
Installed from Windows (my Linux UEFI partition is too small to install via fwupd), and have noticed no issues.
Honestly itās because thereās always some āmassive problemā reports. They could be due to issues that appear only in very rare combinations of circumstances, or even some users (out of thousands that try the beta) just randomly having some hardware fault around that time. Hard to say really, but if framework waited until there were zero issues reported, they would never release firmware updates, which would not be good.
Also keep in mind that Framework never make any fix, or other modification, between a ābetaā and a āstableā. 3.18 is what it is, and even if thereās a widespread serious issue that prevents marking āstableā, itāll be at least a month until thereās a 3.19 to replace it, because Framework have a separate contracted team at Insyde or somewhere else doing the EFI firmware. They literally canāt just fix a small obvious mistake the code, bump the version, test it on 10 laptops of the appropriate generation but with different variants/options/OSes, and then release it as a ābeta2ā in 48 hours. I wish they could.
Itās also annoying that there seems to be lots of minor bugs in EFI firmware or EC power-management logic, that persist for a long time. Probably thereās some calculation about the cost of putting very expensive human attention on investigating and testing solutions for them. But fixing some of them (any of them!) is probably under-valued because of the effect they have āmuddying the watersā whenever any problem is reported in any thread.
All that said, Iām happy to see firmware releases continue, two steps forward and sometimes one step back, this is still the way to improvement. I personally have not had any issues with this release, BIOS 3.18 seems to be working well on my FW13 AMD 7840u running Arch Linux. For my use cases Iām pretty happy with how it is now.
2 Likes
Successful update from 3.17 to 3.18 with fwupdmgr. 7640U with Fedora 43.
Failed to update from fedora add/remove software, and via fwupdmgr. Reports sent. Seems it was pulling 3.17 instead of 3.18. Maybe the release has been reverted.