Are you claiming you actually know of other manufacturers laptops that have no serious problems at all? Isn’t there always something, admittedly it’s usually something I don’t care about, but it’s something that doesn’t work right?
You only care about this problem if you are one of the unusual people who insist on using their laptop for everything all the time and try to turn it into a desktop PC when most people would just use a separate desktop PC when they have space for separate bigger screens etc.
Literally the iPhone 4 meme where Steve Jobs said “just stop holding it the wrong way”.
Imo these issues are more of a symptom of Framework being a young company. I give them a lot of of slack. They are the best Laptop company and have S-Tier support. But due to problems like this, plus the 4 hardware issues I’ve had, on top of 2 severe driver issues, I can’t recommend Framework to non-Linux people or my Family members.
Hi, I am here to report that my upgrade 3.17 to 3.18 worked fine for me.
I have a minor issue that always happened after I upgraded bios on this laptop. I could not find a report on this.
So after bios update completed, the computer reboot, it still enter the ?fi_manager and waits 10 seconds to start the normal boot process. Previous support ticket to framework says to switch ssd. I did that previous 2 time I upgraded. And it works. It does not go into the 10 seconds wait anymore.
But this time after upgrading bios, I just took out the ssd, and boot it, obviously it cannot boot, there is no ssd.
Then I boot it, and it works now(no more 10 seconds delay).
So I don’t understand why I have to do this extra step(though we upgrade bios so very rarely) and haven’t found report of other people seeing this issue.
Did it work on earlier BIOS versions? With my laptop it hasn’t worked for months, the battery extender always gets reset on reboot. After extensive troubleshooting FW support concluded that I would need a new motherboard, which I am not buying for such a minor issue.
I have now set a charge limit, because I don’t want to stress the battery any more.
Update:
This may have happened to me now as well. Only once though, and simply pressing the power button once to turn it back off and again to power on was enough for it to work on the second attempt: no need to unplug anything.
So two potential options:
Maybe it’s not a 100% black and white error, even given identical test setups. Some have been very successful with replicating it, but others have not.
My issue was different. Unfortunately I didn’t catch the blink code to know. And since I haven’t been been able to reproduce, I can’t confirm.
Since I’m also experiencing the blocked boot when connected to a dock, I already added my contribution in the GitHub issue.
But now it seems that I have another issue: after a few hours of use, the wired connection becomes unreliable to the point that most of the network requests are failing.
As soon as I disconnect the wired connection and go back to Wifi, no issue.
The wired connection comes from the the dock that provides keyboard/mouse/external screen/Ethernet.
Everything was working as expected for a year and a half, until the BIOS upgrade last Sunday.
Is there an ETA for a fix or should I downgrade to get rid of those two annoying issues?
As there are currently no visible efforts to find a solution, I would recommend downgrading.
The release is still marked as stable, the issues are not mentioned in the ‘known issues’ section, and the latest (and only) post from the Framework team was two weeks ago.
I’m having the similar issue, but my dock is an Anker TB5 dock, but I do not have a mouse connected to it, only an 10GbE TB3 NIC and a keyboard on the back USB-A. I’ll try to unpug the keyboard to see if it boots up. I already tried unplugging the monitor from the DP port and the TB 10GbE NIC
I think you’re misunderstanding what a bios update is in FWspeak
It’s simply to add half baked ideas and to break things while being able to feign the illusion of support because they added another .01 to the version number.
I don’t know of any bios update for any version that actually solved any fundamental problem from day one of that board.
@Brian_Gregory I don’t see why anybody has to modify the way they use a computer just because it’s a framework and we should hold them to a different standard.
They are investigating internally. After lots and lots of complaining on my part, the support case I opened for the firmware hanging issue has been escalated to the point where a very recognizable Framework employee is now handling it and the engineering team has been able to reproduce the problem.
@Michael_Marley
I think the firmware hanging is related to this problem:
A FW Firmware engineer commented:
“We finally have a reproduction system. The error is caused by a communication breakdown between the EC and the APU’s APML. We’re currently debugging the root cause.”
Like all things like this. Unless FW engineers can reproduce the problem, a fix will never happen. If a FW engineer can reproduce the problem, the problem is essentially fixed because the fixing is the easy bit, except it takes time.
Agreed that the release should not be marked as stable until the fix comes through. That is not confidence inspiring. With that said, echoing @Michael_Marley ‘s post after hearing back on my support ticket – they’re hard at work on it.
Here’s part of the response:
…our Engineering team was able to successfully reproduce the issue and are currently debugging the root cause. For more specific information, the preliminary analysis suggests a possible regression was introduced by an AMD kernel update. We do have an internal ticket to track this issue while it is investigated further…
Good catch! I did say this back to them (i.e. this is before the kernel loads), and pointed them back towards this post and the corresponding GitHub Issue.
Thanks for posting this solution, I had the exact same problem as you and this worked for me also.
Updating from 0.0.3.17 to 0.0.3.18 resulted in “Update success!” during the initial flash, but after the rebooting, I was stuck on a blank screen with my fans spinning up and down, somewhere near maximum. I tried rebooting with/without AC connected, expansion cards inserted, etc, to no avail.
The only thing that worked was disconnecting the battery, plugging in AC, then powering up again. I then cleared the fTPM, it then went through the flashing process again, and I was finally able to boot into the OS.
I updated using fwupd on Arch Linux, and have never had a problem before (after 4-5 BIOS updates in total).
For some previous BIOS update with this issue, it helped in some cases to remove the limit (set to 100%), power off and wait 30+ seconds for the EC to power off as well, and power on to set the limit again.
If that does not fix it for you, you can downgrade by running the Windows installer for the older version or use fwupdmgr downgrade on Linux.
