Admittedly, only been running this for a few minutes but so far so good. Changing the power led to low does now prevent me for being blinded each time I turn on my laptop.
Thank you @Kieran_Levin and the team.
Installed the new Bios update.
If I read the release notes right there is no need to update the Windows drivers if you are already using 3.03 drivers and using the Realtek chip, right?
The drivers in 3.03 are outdated. At least the graphics and bt ones so I would install the better driver package @2disbetter
However-
this suggests that there are not driver version updates in this driver bundle.
Oh, I didn’t see that comment in the release notes. Well, for those using the driver bundle, use the Intel driver assistant to update your drivers
Just updated the BIOS and power button dimming works like a charm!
Can confirm that power on without battery works as well.
@Foxboron looks like that TPM2 eventlog issue is fixed?
Clear evidence that public shaming works after all. /s
Thank you Framework for delivering. I hope we all can take a moment to appreciate their efforts to make this right.
Would it be possible for Framework to provide ISO’s for us to manually copy to USB drives until official LVFS updates are set up?
Here’s an example of Lenovo provides ISOs for Thinkpad X1 Carbon bios updates: BIOS Update (Utility & Bootable CD) for Windows 10, 8.1 (64-bit), 7 (32-bit, 64-bit), Linux - ThinkPad X1 Carbon (Type 20HQ, 20HR, 20K3, 20K4) - Lenovo Support US
^^^ This please!
I already missed out on 3.03, couldn’t install it on my Linux-only Framework even with a Windows To Go drive.
Can confirm the mainboard works without the battery, outside the case, and on an external display. Let the tinkering begin!
Framework laptop built for linux but still a minority. I wonder what percentage windows and linux Framework users.
This sounds related to the workaround I did on Ubuntu 20.04 where I rmmod i2c_hid
on suspend and modprobe i2c_hid
on resume to avoid the touchpad turning into a potato. Maybe that workaround won’t be needed with this BIOS. Will test.
I’m so excited to see what you do with this! I saw your video on the battery issue when it went live, and your ideas are undoubtedly going to be fruitful with potential.
A question for all is, could this be a good opportunity to buy just a mainboard to use as an independent computer in a 3D-printed case? I have worries that this won’t be sustainable due to the way that a laptop is designed to be used and using it like a PC or Latte would damage it in the long run. Thoughts?
I will be using 3D printing for prototyping but it’s not a long term solution due to the heat the mainboard generates. Prototypes that are promising will be sent off and machined from aluminum. This isn’t really a cost effective solution for most unless your a builder/Modder and have a passion for it. I will be buying mainboards when available but I don’t see it as hugely cost effective for most unless again my previous justification applies.
Oh? Please share your experience. I was planning to do exactly that.
Normally I’d be hesitant to do that, as the way framework has those modules implemented on the mainboard is going to vary from application to application. Hence the drivers they provide could be specific to that implementation. Otherwise, wouldn’t they tell us to just use the ones straight from Intel?
Still have you seen improvements? About the only thing I want is standby improvements.
Framework bundles the drivers they’ve extensively tested and confirmed to work, so you can get every part of their eponymous laptop up and running on a clean install, but ‘not the recommended version’ is far from ‘incompatible’. Framework’s laptop is a modder’s dream, and it can be your dream too if you dare to dream it. And troubleshoot it.
So far so good on Windows 11 (22000.282). Both BIOS and driver bundle installed. A cool feature in the future would be the ability to create a custom fan curve in the bios for the cooler. Maybe with safeguards in place so someone can’t purposely cook their CPU. Thanks for the hard work Framework!
Just an FYI for others who might have any issues:
I installed the BIOS update using a Windows To Go drive, which worked fine for BIOS 3.03. It rebooted fine, and it went through the install like normal. After doing the EC update, it hung on “Update status: Complete”. I left it like that for about 30 minutes, and no change. I just tapped the power button (tapped, not held), and it turned off. I turned it back on, and was greeted with a black screen for about 25 seconds. After that, the normal Framework post screen came up, and it tried to start.
However, it just threw me into a Windows blue error screen (A required device is not connected). I rebooted to try and change my boot settings, only to notice that my Linux boot entry was gone (Arch on my NVMe drive), and it was listing Windows Boot Manager on the NVMe drive, while in actuality there’s no Windows EFI data on my internal drive, it’s all on the expansion card. I removed the expansion card, had no effect.
I tried an Arch USB, to reinstall my boot entry, but I then discovered that no new boot devices showed up whatsoever. Also, while I was in there I tried the power button dimming option in the bios when I first rebooted (it’s why I updated), and it didn’t have any effect. Still the same brightness.
At this time, I started to panic a little. I opened up the laptop, and I wasn’t greeted by the normal flashing LEDs when I first opened the chassis. Completely dark. I disconnected the battery, then (very carefully) removed the CMOS battery, waited a few seconds, and put it back in. I then reconnected the battery, and upon turning the machine on (and going through another memory training), everything is normal again. I was able to boot into an Arch USB and reinstall the boot entry, and the new power button dimming feature works perfectly now.
Hope this helps if anyone else has the same issue. It might be my fault for pressing power (given that it tells you explicitly not to do that in the initial program), but I didn’t know what else to do after it hung for a long time with seemingly no change.