Great device. Loved it - for about a month. Couldn’t touch it without pain after that.
I wonder what kind of realistic ETA there is (if any) for these kinds of features.
Speakers also do work but they are disabled by default so a bug in the current implementation doesn’t blow up the hardware.
And a whole set of major features will be supported as soon as the thunderbolt driver is done which I’ve heard is in progress.
The touchbar, fingerprint reader, and camera are things I wouldn’t hold my breath for.
Laughs in NetBSD
[1]: https://phpc.social/@[email protected]/10981800943090...
stuff like USB, the touchpad, keyboard, speakers, 3.5mm audio, suspend/sleep are all still WIP
That makes it sound as if they are barely (un)usable which isn't true eitherFeels like Apple have made this a lot harder than it needed to be. Of course they're masters at designing great hardware with ridiculous flaws. Like somehow being fragile despite the metal construction. Missing connectors, weird keyboard design choices. Soldered-on components. I bought a Macbook Pro once almost a decade ago. Never again. Never before or since have I felt less like I actually owned the hardware I'd bought.
You sound like anything but apple is good, but there's a lot of awful hardware out there, that is for sure. How to you avoid it ? What's your foolproof buyer method ? I might sound snarky, but I'm also genuinely interested !
I expect to keep my Thinkpad for another 5 years at least. But I might switch to Framework at some point if they can match the Thinkpad build quality. For laptops I value sturdyness and repairability over all other considerations, because I'm clumsy as hell. Apple products are far too fragile for me and far less sturdy than they look.
Amen.
Reading trustworthy test sites, before buying anything expensive. Which has gotten a bit harder, due to LOTS of paid content, but it still works, if you know how to spot the signs of a bad site.
For example with Thinkpad that meant finding a compatible panel based on specs they publish about all their models, then finding a teardown and rebuild video published on the Lenovo website for the model.
I was really interested in an m1 laptop but I tried my process with it and all research pointed to "send it in to apple care" which I don't want to do because I know how to use a screw driver and order parts, that should be enough.
I bought my second Macbook and I'm using mostly wireless accessoires to prevent port damage. I don't use its built-in keyboard and touchpad to prevent them from breaking. I don't disconnect it from power to prevent battery damage. I bought huge SSD (2TB) and don't fill it with data to prolong its life.
And you know what? It works wonders. This macbook works without hiccups for almost a year! Sure, I'll need to replace my Apple Keyboard soon, but that's just $250, not $5200.
For full clarity, having observed Marcans socials for a while, a big reason as to why upstreaming into the kernel is slow is because the Linux kernel suffers heavily from having BDFL maintainers.
Basically a specific maintainer can make upstreaming patches to their part of the kernel a process few people want to go through due to how much leeway they have in approving/rejecting patches. Stuff like yelling at merges that also happen to fix bugs in the parts that they modify because "bugs should be upstreamed separately" (even when splitting out the bugfix makes zero structural sense) or getting angry at contributors for lines they didn't contribute but that git diff happened to spit out around their commit to keep the diff readable.
Having watched that for a few weeks really gives you an understanding as to why so few Linux modifications for obscure devices have their patches upstreamed. (Switchroots main project, which is the Linux kernel but modified to run on the Switch for example doesn't bother upstreaming anything as far as I can tell.)
There's plenty of maintainers who aren't that sort of a stick in the mud (even on the Linux kernel), the problem is that the Linux kernel has a few too many entrenched ones who are basically using their position to be a bully to interested contributors. They're generally aware enough that they know that the people they get into fights with aren't likely to use any of the official processes and are more willing to put up with it.
It's more akin to "this maintainer should be replaced" rather than "the entire management is bad"; to my understanding the actually important trees (as in, the server related components, since Linux is primarily used as a server kernel) don't have these maintainers; they're mostly on the stuff that matters less like well... Sleep/Wake related things, speakers and batteries, all of which are mostly useful for desktops and laptops.
(Benevolent Dictator For Life)
It's worth noting that these features were long available since July 2022 (https://asahilinux.org/2022/07/july-2022-release/) to Asahi users. And like other Asahi users, I've been using them since that time on my Mac Studio running Asahi (with HDMI output, 10G ethernet, and Bluetooth too): https://triosdevelopers.com/jason.eckert/stuff/AsahiSwayM1Ul...
There is a list of upstreamed and missing functionality on the Asahi Linux wiki here: https://github.com/AsahiLinux/docs/wiki/Feature-Support
Linux 6.2 adds (checks notes): cpufreq to M1s, devicetree for newer hardware, HDMI out to Mac Studio (2022) and bluetooth support.
That doesn't sound as interesting as this article suggests when stuff like USB, the touchpad, keyboard, speakers, 3.5mm audio, suspend/sleep are all still WIP downstream.
This isn't a dig at the Asahi Linux developers. They're making solid progress. This is just a bad article.