- Re battery: Yup, battery life during sleep sucks, it seems like this is mostly an Intel 11th gen issue as S3 sleep went away and folks on Dell, Lenovo, etc., 11th gen hardware have similar issues.
- Re Fan: it does seem to like to ramp up a bit too much even when components are not really that hot yet.
- Re USB-C: have not used that, so cannot comment
- Re build quality: yes, it is a bit flimsier than I would like (though have definitely used laptops that are way worse), but it is also lighter than competitors that are less so. I am mostly okay with that trade-off, others may not be.
As you say, the company has been responsive and helpful on the community forums in a way the big players never have been, and the BIOS updates are fixing genuine issues and complaints with real release notes. It's not all great for sure, but there's lots of things that are a lot better than competitors.
Laptops are sold as an appliance for the most part, they have to own it’s quality.
Actually more than that, this should first be an excellent laptop and then the repairability and customisable it should be layered on top of that without compromising it (too much), as opposed to the other way around.
I understand the sleep issues but battery life is miserable generally - the sleep issues only exacerbate an already pretty-much-terrible situation. Fortunately I don't really need significant battery life but if I did I'd be looking to unload this thing at this point.
Which makes me wonder - maybe the Intel wifi board has a lot of problems but is still the best Linux option...
And I'm curious to know which WiFi chipset you would rather they have used, as most alternatives either have worse Linux support or aren't as advanced as Intel's. Would you rather they used Broadcom, The bane of WiFi and Linux?
That's what my last sentence was trying to express. Something can be shitty and also the best option.
I’m not trying to give Framework (or any other laptop maker) a free pass here, just saying that it’s not a unique problem to this laptop.
One of the benefits that a company like Framework has is that they don't have to support everything. They can be like Apple and tailor their hardware choices to the ones best supported by the software.
To me, Asahi Linux is the most exciting thing going on in Linux-land right now. They have a very small number of hardware configurations to support. In theory, they should be able to get it really dialed in and polished to the point where it just works. I don't care if they go for KDE or Gnome, SystemD or SysVinit, or anything else in particular. If it works right from the start and is extraordinarily stable, I'll learn to love the choices they make.
Asahi is more of a project for driver and related development and upstreaming it. They do plan to release a distro, but the current plan is for it to just be Arch with the bleeding edge of their work applied (so perhaps not the “dialed-in” you’re looking for since Arch is far from that). IMO, Asahi is just solving the same issue with anything else: lack of drivers for some hardware. It just so happens that the hardware is very specific and popular. My feeling is that I don’t want to invest in hardware whose manufacturer is unwilling to invest at all in my use-case (Linux).
Do you want open computing?
Or Apple?
Pick one.
I’m really tired of the IT community that just wants high paying jobs but none of the skills that earn them.
As a hardware designer; do better, software “engineers”.
If the community is going to claim the title, it damn well better start engineering better than these awful websites and hacky operating system kernels and GUIs that glitch.
Or stfu over others efforts which are a bit beyond memorizing textbook math and recalling them via your text editor with algorithmic help.
Look at all the non-contributors certain they can do better.
Anecdotally, my battery life is plenty good when actually using it (I've yet to feel like I need to reach for the charger at all unless I started very low), but everyone's use case is different.
Andrew noted in a sibling comment what the issue was with the AX210 in Linux. Intel has informed us that the patch is going into kernel 5.17. In retrospect had we known how many issues we'd see with AX210 relative to AX201, we would have gone with the latter as the default option on the DIY Edition. Going forward though, we do expect compatibility and stability to improve (on 5.17 and later).
On the USB-C issues, it would be great to know the model numbers of the displays and cables that are having this issue. We want to continue to build up our library of peripherals that have unknown issues in order to resolve them.
On build quality, we've seen exceeding few field failures on mechanical issues, and a couple of reports of people dropping their system (or as often happens, blaming their cat for this) from high enough to dent a corner of the chassis and then being able resolve that by ordering a replacement cover part from us.
EDIT: Speaking of startups, if you didn't know already you have a lot of "street cred" out there. When wrapping an in-person presentation or meeting many of the questions I get are about my Framework!
Where should I report on the displays and cables with the USB-C issues?
Regarding drops I've actually never dropped a laptop in the > 20 years I've had them. So kind of a non-concern but the comment was referring to the general "feel" which may not really mean anything outside of perception.
- As has been noted time and time again, battery life is atrocious. As in unusable for even the travel time required for a three hour flight: factoring in the poor sleep, an hour at the airport, and time on the aircraft the battery is dead. Crazy for 2021/2022 - my eight year old Macbook does better.
- Wifi. The Intel Wifi modules provided with the Framework are very poorly supported in Linux. I spent six hours the other night running additional ethernet drops because I just couldn't stand my workday routinely being interrupted by repeatedly disassociating from my AP (fixed with reboot). Even unloading and reloading the associated kernel modules wouldn't bring it back.
- USB-C acts... Strange. I have two 4K displays using Displayport over USB-C and the Framework repeatedly fails to initialize them from boot. I have to do a strange dance (the steps of which I'm still figuring out) involving powering off the Framework, unplugging/re-plugging everything, and then rebooting until it magically works again.
- Fan. The fan is crazy. I've settled on disabling turbo mode in Linux.
- Build quality. I'm convinced if I drop this thing it's all over.
All in all I'm mad at myself for spending over $3k on a productivity configuration centered around what is pretty much beta hardware. I should have known better.
Anyway, there's hope for some of these issues as they seem to be releasing BIOS updates pretty regularly (currently running 3.07) but even then I need to USB boot to use their EFI update tool. Intel wifi should get better over time and worst case I can swap it out for Atheros or something. That said I think the battery, build, and fan issues are fundamental hardware design choices.