Yes, I’ll give that a try. It may take a week or so as I am busy for the next few days and may be heading out for up to a week. I’ll persevere with it like this till I get back. That sounds like a good idea; I’ll give it a shot and report back any results/changes. Thanks Fraoch.
3 Likes
I tried that (swapping power to the other side and performing the upgrade again).
I still have to periodically reinsert my USB-A cards.
1 Like
Hey Framework. Maybe it’s time to bring in some assistance to wrap this stuff up. It’s feeling like you don’t have the proper resources to figure this out.
1 Like
@Brent_Douglas Perhaps you don’t know this but the BIOS is contracted out to Insyde. They don’t dev it themselves. I’m not excusing how long this BIOS has been in beta but it would be in error to assert that they don’t have assistance.
2 Likes
This delay is lowering my confidence of my framework investment.
5 Likes
@Brent_Douglas What? What does that even mean? Confidence in what? This sounds like you don’t know how these updates are rolled out. Granted it is taking an absurdly long time to move out of beta, I’ll not contest that but I think it’s ridiculous to draw any meaningful conclusion on long-term support from this thread or this beta.
Given the issues that have popped up in this thread, it isn’t unlikely that FW contacted Insyde to patch the BIOS to address these problems before a final release and yes, once again, Insyde is slow to do so. That’s the theory that I’m putting my monopoly money on.
4 Likes
Good day gentlemen and gentlewomen
I’m confirming that after that power of retimer reset, right ports work for thunderbolt… Sorta.
I’m having some tb4 instability with a “retimer disconnected” in the dmesg.
Thanks for the transparency you provided us, framework team.
@GhostLegion I think the comment is a valid frustration. While I understand why they are using a third party contractor it does not mean I have to be happy about it. They really should prioritize making the hires necessary to do this in house, to commit to regular updates, and to essentially strive to provide an enterprise grade product. I hope that as time goes by they get closer and closer to achieving that. Simply the user appears frustrated that some very basic items don’t work right, are flaky, or don’t appear to be getting the appropriate amount of attention. It is an area where Frameworks close mouthed approach is not helpful.
1 Like
Which enterprise manufacture makes their own bioses? for consumer level hardware for now.
Ill wait.
Is there are way to make a backup of the firmware (for all parts im updating) before updating?
I generally don’t buy consumer grade hardware, and really don’t consider the Framework consumer grade. Guess we should all lower out expectations, or desires, however seeing as how this is their only product and taking into consideration their stated goals they are going to have to move in that direction eventually.
Guess I was spoiled with Thinkpads.
3 Likes
I dont see what people are complaining about. My experience of laptop manufacturers is they MIGHT release ONE bios update for any given model if and only if there is a serious problem with the shipped version, and they MIGHT release another to further restrict consumer choice if they find out that consumers are doing things to bypass restrictions in the original version. (Hello HP, retroactively encrypting your bioses to stop people defeating your anti-consumer hardware whitelists)
Other than that, you can get stuffed, especially if it’s more than a year old, because they aren’t interested in it anymore.
2 Likes
I agree that FW has been slow to provide updates and feedback. What I disagree with is drawing conclusions about the health of the company or about FW’s commitment to long-term support.
2 Likes
Now this I appreciate. Thank you.
1 Like
Yeah but then that one actually works, because if it doesn’t they have to take it back and refund the whole thing, and that blows away the profit from 10 other laptops.
I would prefer if there were zero updates, because the factory bios was actually finished before shipping.
1 Like
Disclaimer: I solved the problem, just posting to save other people time and reporting a bug.
I had a problem upgrading over lfvs. When updating, it said, PD1 Update failed, while PD2 was successful. In the BIOS PD Controller 1 Ver was 0.1.14, while PD Controller 2 Ver was 0.1.21. Back in the system fwupdmgr downloaded the updated again, so I wanted to reboot and update gain, but I was not able to really start it. Fwupdmgr.efi was booted, found the update, rebooted the system twice to a black screen, then it booted back into my system.
I tried a lot of things in different combinations: Changing the charger from the left to the right (all 4 ports multiple times), tried USB-A charger method, tried changing DisableCapsuleUpdateOnDisk=false, since I thought probably the new 3.06 BIOS does not need it set to true anymore, but always the same behavior.
In the end I tried the UEFI Shell update method, which worked fine.
4 Likes
Ideal situation indeed.
But nothing is finished with unforseen bugs and feature additions you only come up with by actual infield usage. I also dislike microcode updates, why do Intel not just make a cpu and its perfect? /s
2 Likes
Can we get weekly status reports on the progress here?
2 Likes
I think the point being made by Brian was about the comparison to other manufactures and that they would rather one fully functional BIOS than getting any updates at all which right or wrong is their perception of other manufactures BIOS and desire.
Good point non the less everything created by humans is flawed in some way and at least they are doing the right thing by trying to fixing the problems.
2 Likes
Hi, I have installed a fresh Windows 11 Enterprise 22H2, and installed the BIOS 3.06 beta update. I do not have drivers for many of the laptop devices (e.g. touchpad gestures don’t function, no right-click etc). Is there a driver back I can install without worrying about accidentally downgrading the bios version?
1 Like