You either do compatibility testing, and frame the marketing around the truth, or you have pissed off customers. There's not really an alternative in the hardware world. The logo on the exterior of the product is who they'll, rightfully, blame.
? I looked at framework laptops and as far as I could see there is zero official Linux support. There are some community forums for it, but no warranty if something doesn't work or officially support distributions or anything.
> Available in configurations with Windows 11 Home and Pro, we’ve also tested for compatibility with the most popular Linux distributions and written step-by-step setup guides for them.
that links to https://frame.work/linux
> We designed the Framework Laptop from the outset to be a great Linux laptop
> We deliberately selected components and modules that didn’t require new kernel driver development and have been providing distro maintainers with pre-release hardware to test to improve compatibility
> We and members of the Framework Community Linux sub-forum have been testing a range of Linux distributions for compatibility with the Framework Laptop to highlight the ones that work best
Does Apple actually do anything? I see plenty of people complain to Apple and it falls on deaf ears.
Perhaps most famously, when Nvidia manufactured defective GPUs, Apple launched a repair program at their own expense [1], and IIRC the fallout from this is what (at least somewhat) led to the severance of ties between Apple and NVIDIA.
I’ve had multiple cases of bad GPUs, bad batteries and the like, and while Apple has denied me service before, they’ve repaired or replaced far more as a percentage than any other computer manufacturer I’ve dealt with.
[1] https://www.macrumors.com/2015/02/19/2011-macbook-pro-repair...
Fedora cost me $0
Maybe there were good reasons for that. Maybe it was parts availability or engineering support. The reasons aren't all that important to the end user though; Framework made that choice and bears responsibility for its consequences.
I highly doubt it's a fanboying issue, they're a small company with big challenges and supporting multiple platforms is not easy at any scale. They also wouldn't want to say anything positive or negative that could sour relations with AMD or other partners in future.
Indeed, but considering that Ryzen 5000 was better than 11th gen and Ryzen 6000 is better than 12th gen the solution is obvious: AMD only.
I think one thing to keep in mind also is that for whatever reason, 10 months after launch, the number of Ryzen 6000U laptops I've ever seen advertised for sale I can count on one hand (I was watching all year, I would have much preferred a Ryzen 6800U laptop!). Currently, only the Asus Zenbook S 13 and Lenovo ThinkBook 13s are available in retail stores in the US (Amazon and Newegg, respectively). In the EU, Geizhals search turns up exactly 1 6800U model (Lenovo Yoga 7 14ARB7). [3] Personally, I'm not convinced Ryzen 6000U ever actually shipped in quantity...
[1] https://github.com/FrameworkComputer/Mainboard/blob/main/Ele...
[2] https://github.com/FrameworkComputer/Mainboard/blob/main/Ele...
[3] https://geizhals.eu/?cat=nb&xf=6751_26&asuch=6800u&bpmin=&bp...
This is a significantly different situation than Framework's situation.
Apple controls the hardware and the operating system.
Framework only controls the hardware, not the software.
Let's look at a totally hypothetical example:
Let's say the Framework laptop ships with Ubuntu 22.04 running the 5.15 kernel, and the Framework folks test it carefully, it works great, all is well. Ubuntu then decides to ship an over-the-air software update automatically to the 5.17 kernel, which has a driver bug causing the laptop to freeze every minute. Ubuntu does this without consulting Framework, Framework has no chance to test it.
Who's fault is the above? Is it Framework for not building their own operating system too, like apple did, and putting the software experience of their hardware in someone else's hands? Is it the linux kernel for breaking something? Is it ubuntu for shipping an update to a laptop the distro developers may not even own?
This is no different than the situation for decades with Windows and PC vendors. When I built a PC from commodity hardware and installed Windows on it, if something went wrong, I'd blame Microsoft, or the manufacturers of the components I used, or myself. But when I would buy an HP laptop, if something went wrong, that was HP's fault.
They do now, but prior to ASi, they were using Intel CPUs and AMD/Nvidia GPUs until Nvidia pissed them off so badly around 2010-2011 that they went exclusive with AMD.
The trashcan Mac Pro had a GPU issue that affected renders from Resolve. Resolve said AMD. AMD said Apple. Apple said not us, and crossed their arms pointing at the other two. The fun thing was if you used BootCamp to run windows on the exact same hardware with the Windows version of Resolve on the exact same footage using the same grading session, the timeline would render without any errors. Reboot back as Mac, and render errors. So, clearly, not a hardware issue. Definitely seemed software, but I gave up on the issue well before any errors were resolved but switching back to the latest cheese grater chassis.
The company the person pays money to is the company responsible.
Yes there are limits to this (if you install something outside the supported software then you are on your own) but if you are doing what they say and it doesn't work then they are responsible.
To me, what's interesting is that none of the ISVs that are Linux-exclusive vendors actually caught this in QC/smoke testing. The alternative seems to be "certifying" to a particular distro, but I don't think that'll help most people who run Linux and have the distros they like. Sometimes Linux pre-loading can be a negative as well - Dell is notorious for not actually bothering to upstream their kernel changes for the Developer Edition Linux laptops to mainline for example (they'd done it before w/ their touchpads, and currently have the same w/ their webcam drivers).
One of the big things in Framework's favor is there's an active official forum, w/ a very active Linux section [5]. I think Lenovo is the only other laptop vendor I've seen that has something comparable. [6]
[1] https://lore.kernel.org/all/55905860-adf9-312c-69cc-491ac8ce...
[2] https://lore.kernel.org/all/YzsfrkJcwqKOO+E%[email protected]/
[3] https://community.frame.work/t/psa-dont-upgrade-to-linux-ker...
[4] https://bugzilla.redhat.com/show_bug.cgi?id=2130699
[5] https://community.frame.work/c/framework-laptop/linux/91
[6] https://forums.lenovo.com/t5/Linux-Operating-Systems/ct-p/lx...
The good thing is they found a solution. But despite being a hundred billion dollar plus company it took then anywhere from 5-10 years to find solutions in both cases.
That a new startup hasn't been able to resolve it in less than a couple of years is significantly less worse than the blaming Apple and its fans have done.
Edit: I was looking up some supporting articles and I completely forgot that before Intel and IBM, Apple was blaming Motorola:
Meanwhile, how many assemblies of PC components in the shape of a laptop get a unique part number each year? Surely someone knows how to meld kit into a SKU and make sure important bits have drivers for the OSes you market.
* If Apple starts grumbling about your chips, check your calendar. Not long till your lunch is gone. Every time.
They’ve been complaining about their chip makers since 1999 at least.
The example is ironic. Apple’s behavior isn’t. They conveyed the truth. Just like Framework is conveying the truth.
Is that a valid excuse for Framework? Not for their customers at least. Just like it wasn’t a valid excuse for Apple when it was selling absolute lemons with Motorola chips in them and then absolute lemons with IBM G4 chips in them towards the end of their IBM relationship, or absolute lemons which couldn’t support 32GB of memory when their much smaller competitors using the same chips had been doing so for years.
Presumably an "absolute" lemon wouldn't work. All those models you mentioned worked fine for most folks.
To the point about checking the calendar, it takes time to re-platform, Apple can't stop filling buyer need for Macs for the years that takes to re-platform, and they definitely signaled recognition of chip unhappiness so buyers could beware if they cared.
It's not like Apple shipped something to your door that didn't work and said "Oh, that's IBM's fault". Complaining that IBM wasn't able to meet their demand seems utterly fair to me, though I don't know what the root cause of the delay was. But regardless, Apple was still standing by the products that they actually sent out.
I disagree, given that there are a bajillion different Linux distros.
To be clear, if Framework shipped a version of their laptop with Linux pre-installed, that to me would say they have tested everything together with that version of Linux, and I would expect it all to work, and if it didn't I would call up Framework.
But (at least looking at their website right now), Framework only offers a "bring your own OS" version for Linux. The answer to the "Can I install Linux?" FAQ says "Yes! We have installation guides for Fedora, Ubuntu, Mint, Manjaro, and Pop!_OS. In the Framework Community, there are even more community-edited setup guides for additional Linux distributions." Perhaps I'm just jaded by all my experience over the years installing Linux on my own, but I'm never surprised when there are driver issues, etc. when I'm installing OS on hardware where it wasn't pre-installed.
and
> To be clear, if Framework shipped a version of their laptop with Linux pre-installed, that to me would say they have tested everything together with that version of Linux, and I would expect it all to work, and if it didn't I would call up Framework.
are exactly why I stopped doing that so long ago. I only buy from vendors that ship with Linux and which support it.
The obvious issue with this is that when issues occur upstream, we end up reactive to them alongside Framework Laptop customers. There are several possible solutions to this (which are not mutually exclusive):
1. Building our own Linux distribution for the Framework Laptop. We don't believe this is a good business to get into, and we've seen strong distro preferences in the community that mean that even if we did this, we may not address a plurality of customers' needs.
2. Partner more deeply with specific Linux distributions to attempt to validate kernel updates on Framework hardware before they are accepted for release. We see this as much more viable than option 1, and it's something we are discussing with distros (and we would love to work with additional ones on this).
3. Provide more clarity in our recommended Linux distributions and setup guides around which ones have more conservative kernel policies that are unlikely to run into issues (Ubuntu LTS with an OEM kernel for example) vs ones that more aggressively update and have more risk of driver breakage as a result (basically all of the other distros we currently list). Also as noted in this thread, the risks here will be higher for newer platforms (Intel 12th Gen) than older platforms (Intel 11th Gen). This is something we are now going to prioritize based on feedback we've gotten in the community.
We're always open to any and all additional feedback.
Critically, the bulk of the resources on the distro side that would test your hardware as part of their regular testing are quite distant from upstream (Ubuntu is the closest, Fedora is largely community driven, RHEL and SLES aren't appealing desktop distros for most users), so having some upstream testing in-house would probably help a lot in getting ahead of problems.
Maybe you could try and get boards into kernelci.org? They're mostly focused on ARM SoCs but they have x86 boards in there too, though I don't think there's much on the desktop side. The i915 driver which has caused me much pain and suffering over the last couple of weeks has some test automation that could be run too: https://intel-gfx-ci.01.org/
I'm sure there has to be more upstream automated testing initiatives for laptops but I'm not super familiar with that space.
Oh and if anyone's interested I gave a talk back in 2020 about how Linux kernel testing is fundamentally boned here: https://www.youtube.com/watch?v=9Fzd6MapG3Y
Good luck!
Same as to questions regarding AMD?
Hire more kernel devs full time, sponsor some more, get the hardware in their hands, make it their job to do nothing but fix or improve frameworks, and then get your shit merged upstream not in some random distro.
This. When my Mac has GPU problems, I don't complain to NVIDIA or AMD; I complain to Apple. Since Apple is the final integrator, it has the ultimate responsibility for ensuring that all parts work well together.
Similarly, whenever a laptop is advertised by its manufacturer as "linux compatible" or "linux certified", it is their job to ensure that linux actually works out of the box.