Enabling software longevity

[takaides]

@Destroya

Regarding the Framework Laptop 16 BIOS, we haven’t shared any updates primarily because there hasn’t been anything new to share. The issues are still being tracked and investigated, and we are conducting extensive internal testing. (In hindsight, perhaps we could have communicated that we’re still investigating and working on the BIOS update—do you think that would have helped?)

YES! 1000x this.

Bad news, with a planned path forward, is much better than no news. Neutral news is better than bad news. Not everything has to be sunshine and daisies, but no news is particularly difficult.

@Destroya

We have released BIOS updates for each of our products this year…

@Destroya

Apart from Intel Core 12th Gen, we’ve released new driver bundles for each of our products this year.

@Destroya

The overall longevity of devices as complex as modern notebooks also depends on how long the software and firmware continues to be useful. That includes compatibility updates to support newer generations hardware modules, fixes for bugs or compatibility issues found by end users, and especially patches for security vulnerabilities.

In the fast-moving world of modern computers, yearly updates are better than no updates, but not what I expect in terms of software longevity. I understand Framework can’t do anything about proprietary/closed-source software provided by vendors that doesn’t have upgrades available, but many of these vendors (especially AMD and Intel) are releasing nearly monthly driver updates with bug and compatibility fixes, and security patches, as well as support for new features (October’s first AMD update includes support for “AMD Fluid Motion Frames (AFMF) 2,” which has major performance improvements specifically for gaming). As of October 2nd, issues had been reported to Framework (via community forums) of major crashing and issues related to this release. You chimed in on the same day to remind folks to use official Framework drivers, and, on the following day, confirmed Frameworks driver bundle was from April. To me, this is a compatibility issue for a bug fix, security patch, and new feature release. I feel that this specific update hits all of the points mentioned in the quote.

@Destroya

we’re dependent on the support lifetimes of our upstream silicon vendors who in some cases haven’t shared public end of support dates. Instead, we can state that our intent is to provide security updates for at least as long as our silicon vendors are able to. Note that this specifically applies to the UEFI firmware and drivers that are provided to us as binaries.

AMD has released 9 driver updates for CPU/APU/GPU alone, since Framework’s bundled drivers were last updated. (I’m going off of the Driver Build date of 2/22/2024, a few days before the Adrenalin 24.2.1 release on 2/26/2024.)

What is Framework’s intended policy regarding ongoing software (specifically drivers) support?

Unrelated note regarding response times

Also, as an aside, I don’t work for Framework, and can post whenever I please. I don’t know where you are located (and have no need to know), but it was well after what I hope would be an end of shift for California/PST based folks when you posted your response. I hope you are able to have downtime and aren’t burning the candle at both ends on my behalf. I can wait until standard business hours for a response (especially if you need to check with any other Framework employees to formulate a response). I am not sure if I appear hostile/angry (which is not my intent), but I want Framework to succeed, and that includes healthy work/life balance to prevent burnout. I am frustrated, but I do seriously want everyone at Framework, especially those in customer facing roles of any kind, to have a great day, everyday.