We detached this subthread from https://news.ycombinator.com/item?id=28763252.
I like Apple hardware (and ThinkPads), but I prefer the openness of Linux (and BSD).
Current MacBook Airs are pretty competitive in terms of price, and the fanless CPU is very appealing. Is it much of a gamble to purchase one now expecting to run mainline Linux in a year or so?
Aside from the new architecture, some components Apple has been using are quite unfriendly. Broadcom wireless cards tend to perform really poorly with open source drivers.
I wouldn't buy an M1 right now... just because the next generation is likely around the corner :-). But yes, I can't promise all the polish or that every single thing will be upstream, but things should be solidly in the "daily driver" category a year from now. I'd be surprised if there was any non-optional (i.e. excluding accelerators - no idea if anyone cares about the Neural Engine yet...) hardware left without usable support by then. GPU is a big question mark that should become clear in the next month or two as I poke at the kernel side, but honestly I expect solid OpenGL a year from now, at the very least.
For the kernel mode part, ANE is behind an ASC.
Some things are dodgier - e.g. though supporting the AMX CPU extensions is quite viable in a kernel fork, I'm not sure if that kind of thing would fly upstream. Same with security features like SPRR - not likely to happen. But these aren't really things the average end user has to care about; they're bonus features, not anything core.
(Put another way: I'm wondering whether you think the difficulty is technical or political.)
I'm hoping we can at least push through a prctl to turn on TSO mode for x86 emulation. I think that one will be simple enough and have enough benefits to convince people.
(The x86 xstate design is horrible. I doubt that ARM64 is anywhere near as bad.)
Linux on M1 Macs is "supported" exactly the same as Linux on any random PC without manufacturer support. Sure, it's more work to get running, because it's a new undocumented platform... but we've signed up to do the work. If Linux on these machines is an "unsupported hack" then so is Linux on the vast majority of desktop/laptop computers people use.
But more than that, it is also to spread the fudge that the M1 supports alternative OSes, where as the reality is that it will never support a fully features OS - Apple's business and design goals with the M1 was to create a locked desktop that can only run macOS and only allow other alternate OSes to run using virtualisation on macOS, so that the users data can always be mined. And they have successfully done that.
The developers behind this project are naive to believe that Apple will let them sabotage their efforts to lock down the macOS platform, like the ios platform that earns, that earns them billions of dollars. The locked-down M1 desktops / laptops are just one of the last step towards this goal. As I said elsewhere, just look at what has been happening to the Mac Mini:
1. The first few Intel Mac Minis allowed you some level of customisation of both the hardware (change RAM or HDD / SSD) and software (install other full featured OS).
2. Then came the Mac Minis with soldered RAM and SSD. You could no longer customise the hardware. Software was still customisable and you could still install other OSes. (Recall that Apple even offered free drivers for another OS, i.e. Windows).
3. The current generation of M1 Mini now doesn't allow you to customise both the hardware (everything is soldered) and the software. Technically you can install other OSes, but the reality is that currently only crippled versions of Linux and xBSD is available and practically the only full-featured OS available for it is macOS.
These are clear indicators of how Apple has been working slowly to lockdown the Mac platform like their ios platforms.
The frog is still slowly boiling - https://en.wikipedia.org/wiki/Boiling_frog - to keep you in denial.
Now the only thing that remains is for the bootloader to be locked, and that will the last nail in the coffin of the M1 desktop platform. And it will happen in the near future once the M1 platform reaches a critical adoption point.
(I can understand why the project developers are hostile here to critics like me - the good publicity has been bringing them money, and that's quite rare for an open source projects).
Support from chip manufacturers doesn't mean you're actually going to end up with a better user experience.
Apple has a long, continuous history of locking down hardware. Never having a bootloader unlockable iDevice, unibody, glue, soldered on components that are traditionally user replaceable, soldering in displays and backs when people try to repair batteries, serializing the components so you can't even swap official parts.
Apple has never gone in the reverse direction to make components more easily user serviceable. It's always been in the more restrictive direction. More proprietary with every iteration. Now it's the CPU. Bootloader locking on an M1 Macbook is the next logical step.
They could've just released a locked down Macbook in the first place if that was the goal.
OK, great, but we're talking about a manufacturer that makes products designed to go in the rubbish bin 2-4 years after manufacture (witness the half dozen comments by users in this thread saying they have already put their M1 computers in a drawer somewhere!). Apple are constantly iterating, and the goal of a project like Asahi is to stay ahead of the game and continue running on new hardware.
The proper and correct point that techrat should have made is that the second something like Asahi is a threat to Apple for any reason, Apple can release new hardware that's locked down similar to iOS. You'll even have people on this site defending the changes too, in the name of security or something.
They have a LONG history of making decisions that ultimately are hostile to the user. Apple also has a history of explicitly locking out Linux users.
https://www.phoronix.com/scan.php?page=news_item&px=Apple-T2...
> It looks like even if disabling the Secure Boot functionality, the T2 chip is reportedly still blocking operating systems aside from macOS and Windows 10.
This is further than Microsoft has ever gone with hardware.
Apple has been dipping their toes into the telemetry and ad tracking waters for a while now. If they see Asahi cutting into those margins because people are buying Apple hardware and installing an OS that prevents them from collecting user data, I can believe they'd see them as a threat.
Why? Again, history. Apple has shut down numerous developers who made "competing" features for iOS via apps in the App Store... even though those developers had the app first before Apple decided to add the features into iOS.
But yeah, something something security something...
Just buy the hardware you want to use and don't assume it will get better over time. Even if Apple suddenly decided they wanted to lock out other OS's (they won't), they can't remotely update the bootloader if you're running Linux.
https://developer.apple.com/documentation/apple-silicon/inst...
And here's the kmutil manpage that explicitly describes the option they added to support fully custom kernels, which is what we use:
https://keith.github.io/xcode-man-pages/kmutil.8.html
And here's a blog by the head of XNU development at Apple explaining how to build and run your own XNU kernel for these machines:
https://kernelshaman.blogspot.com/2021/02/building-xnu-for-m...
This isn't an accident. This is a documented, explicitly advertised feature that Apple put a significant amount of engineering time into developing.
Re on the M1 specifically, Apple suggests they'd totally be on board should Microsoft put in the effort:
https://www.macrumors.com/2021/09/14/arm-windows-m1-macs-not...
> Apple's software engineering chief Craig Federighi last year said that Windows coming to M1 Macs is "up to Microsoft." The M1 chip contains the core technologies needed to run Windows, but Microsoft has to decide whether to license its Arm version of Windows to Mac users.
I imagine that once Windows on Arm is supported, they'd be totally be on board.
Perhaps if you weren't so hostile in your replies, you'd be down-voted less. You come across as angry.
> Perhaps if you weren't so hostile in your replies, you'd be down-voted less. You come across as angry.
You get what you read into it.
Majority of my posts are statements of fact yet they get downvoted because there's no placating the Apple horde with the truth.
Even if you're right that Apple deliberately locks things down so the 4th or 5th or whatever generation of this hardware can't run anything but macOS, this project still has value. Maybe not to you, but it will to lots of people. And that's really all that matters. Your negativity here is a waste of time and is frankly boring and off topic.
That's not been my experience, but I guess in such circumstances your mileage may vary.
> ... there's no placating the Apple horde with the truth.
Pretty much summarizes what's I was suggesting as hostile.
What limits are you referring to, and by what performance metrics is Boot Camp unable to make full use of the hardware capabilities?
Well, let's be fair: They could try, but again, that'd require those OEMs to cooperate. And you'd still end up with folks like System76 and Framework that'd go their own way because nothing can stop a vendor from creating an open x86-based design. They just wouldn't be able to ship Windows pre-installed.
Apple, by contrast, could just do it by fiat because they own the entire ecosystem, and no one could do a damn thing about it.
That's the difference between an open, interoperable ecosystem and a closed one.
I genuinely don't understand the debate, here. Are you seriously trying to claim that the Apple hardware platform and the x86 ecosystem are equally open/closed?
Seriously, there's no way I'd be half as happy working at Intel on Linux drivers as I am working on the M1. And it's not like they support external developers either - most of the chip documentation for Intel/AMD stuff is not public. You can't actually build working graphics drivers from their public docs, not even remotely close. Heck, I had to reverse engineer AMD's GPU microcode to get the variant in the PS4 to work. Totally undocumented stuff.
If Apple had provided a bunch of binary blobs for Linux, that would have been great - for Linux only.
It will be ironic if the mac mini becomes the most open hardware platform for alternative systems.
Of course, if that doesn't convince you, we can always fall on the fact that you aren't the person writing the code, and in the world of free software you don't get to tell others what they ought to spend their time on.
Odd, because here I am with an Intel laptop running Linux that manages that just fine.
> Support from chip manufacturers doesn't mean you're actually going to end up with a better user experience.
Honestly, this is just ridiculous. Go ask the Nouveau folks how their reverse engineering project is going.
I love the drive you guys have, and I wish you the best of luck. But Apple could pull the rug out from under you any time they want in a future hardware rev (either deliberately or accidentally), and all you can do is keep on reverse engineering in the hopes of keeping up.
Edit: Updated pronouns since apparently the OP is one of the project maintainers.
Then it's not an Ivy Bridge running multiple external displays on KDE.
> Honestly, this is just ridiculous. Go ask the Nouveau folks how their reverse engineering project is going.
Nvidia created an actively hostile firmware situation. We already have the firmware story worked out. Plus having to support a bazillion GPU generations with incompatible interfaces burns people out. We're starting with one, and Apple has a much better track record of incremental change and avoiding hardware churn. This is unique, and we've literally heard from Apple employees that this is an explicit goal. It shows all throughout the SoC design.
> and all you can do is keep on reverse engineering in the hopes of keeping up.
And we will keep on reverse engineering, and we'll keep up :-)
Tiger Lake (whose microarchitecture I just learned is Willow Cove) running Gnome via Wayland (damn HiDPI...), single external display via USB C dock plus an onboard.
More fully, previously I was running a Lenovo X1C5 with Intel integrated graphics. Again, no issues there. In that case I ran Xorg with TearFree enabled.
I'm currently running a Framework sporting an i7-1165G7 with the aforementioned setup.
It was genuinely a little shocking, having spent my earlier days manually hacking modelines in X, to see this hardware come up flawlessly on first boot with Ubuntu 21.04... amazing what a reasonably open hardware ecosystem will enable. jab jab ;)
> We're starting with one, and Apple has a much better track record of incremental change and avoiding hardware churn. This is unique, and we've literally heard from Apple employees that this is an explicit goal. It shows all throughout the SoC design.
Absolutely a fair point! I concede that the reverse engineering story with Apple may very well be less painful than it is with other vendors. Honestly, I hope for your sanity that it is! :D
The statement they made is ridiculous, and I stand by my decision to label it as such.
If you want to explain to me how I'm wrong instead of simply appealing to authority, you're obviously free to do so.
That sounds entirely ridiculous and unsupportable to me.
And please don't trot out the "appealing to authority" bit. That absolutely doesn't apply here; when it comes to an opinion about some hardware/software project, I would 100% take the word of the lead developer on that project over a rando on HN who has for some inexplicable reason decided to pick a fight about something they appear to not have any domain knowledge about.
Hell, most Lenovo, Dell, IBM, etc. laptops don't have official Linux support from their manufacturers. They're also "unsupported". I guess that means everyone should just buy System76, Framework, or Purism, or one of the scant few models that a small minority of the big manufacturers actually support Linux on, right?
> Compare this to where people make a LineageOS release for their mobile device. Still unsupported by the manufacturer, but GPL requirements often mean there's still device code to work with, if not at least the device ROM being released that images can be used to boot another OS.
This is a pretty bad example considering that many phones with LineageOS support still require closed-source binary blobs since the manufacturers don't provide source for everything. If anything, LineageOS is more of a "hack" than the M1 effort, which aims to produce open-source drivers for everything.
> Apple is still one of the only hardware companies who have gone out of their way to prevent Linux from being run on their hardware.
I think you're ascribing to malice that which is driven by indifference. The things Apple does that incidentally make it hard to run Linux on their hardware are probably driven more by lack of caring than any deliberate effort. As marcan pointed out in reply to one of my other comments here, Apple does things because they need to in order to get the features, performance, battery life, cost, and security they want. If the "Linux friendly" way of doing things doesn't jive with that, they'll go their own way.
> As such, I cannot see why open source advocates would continue to try to get any distro running on Apple hardware
Perhaps you just lack imagination? Your motivations (or lack thereof) are not others'. "Open source advocates" do what they do for a wide variety of reasons. And the people who are working on this might not even be "advocates"; maybe they just like Linux and don't like macOS, but love Apple's hardware.
See also: the entire PC industry exists because IBM's BIOS was reverse engineered!
However, “Unsupported hack, at best” is pretty dismissive of the engineering effort going on with this. People running Linux on “windows branded PCs” of the not so distant past could have easily said the same thing because Say Dell and Microsoft would be commercially motivated to only keep Windows running on their hardware. However the ecosystem around Linux made things happen such that it is almost a no-brained that most systems you buy _will_ run say Ubuntu with more than reasonable success.
With enough motivation, and the efforts of engineers such as those listed in this article, I bet we might even see better use of Apple hardware than MacOS. Apple might optimise for their stuff, but Linux can bring the power built for other needs(HPC, Real-time systems etc) to the table and can leap over MacOS given the right abstractions. The future is exciting for the hopeful.
I don't think this needs qualification. It's still true today.
It's fine to worry about it (and UEFI was a real threat until Microsoft mandated support for other-os booting), but support for Linux in the PC world has never been as fragile as support for it on Macs. You're entirely at the mercy of Apple's whims; I support the Asahi project, but that's just the truth.
Intel and AMD both contribute heavily to the Linux Kernel. This means that on the vast majority of Intel or AMD based systems, you can boot from USB and have a working system.
Apple doesn't even release documentation on their SOCs.
Apple doesn't use standard, open boot methods to allow other OSes to simply boot from USB. No BIOS/Standard UEFI.
There is a huge chasm between what you can do on the vast majority of PCs out there... and what you have to do to get anything else running on Apple hardware. IF you can get anything running. (Eg, locked bootloaders on iDevices)
Most computers anyone can buy are full of components that only have drivers or support in the linux kernel because people reverse engineered them. Most are also full of components that linux only works with because of extracted firmware blobs from other systems.
EFI is more or less an open boot system (which.. you know intel macs used that right?), though with plenty of proprietary extensions and alterations in most booting computers, but the BIOS boot that predated it? Yeah you know that was a proprietary system right? Linux booted off it because people reverse engineered and cloned it until it was forced to be an 'open' thing. It didn't just magically happen one day and IBM even sued about it back in the day.
It seems like there's an entire generation of folks out there who can no longer tell the difference between an open technology ecosystem and a closed one...
What disappoints me is a "generation of folks" who can't tell that openness is a spectrum and that every bit of openness they enjoy was hard-fought for by pushing the boundaries of the platforms that existed beyond their original intentions, and now treat an effort to do the same on new platforms as some kind of windmill tilting.
And Apple is very far on the closed end of that spectrum relative to their competitors, and always has been.
There is simply no arguing this point.
> every bit of openness they enjoy was hard-fought for by pushing the boundaries of the platforms that existed beyond their original intentions, and now treat an effort to do the same on new platforms as some kind of windmill tilting.
Let's be real: Asahi isn't gonna change Apple's corporate culture. It's a super cool technical project and I absolutely applaud these sorts of efforts simply because they're cool.
But you're not the Jedi fighting the empire here. You're not gonna blow open the M1 and suddenly change Apple hearts and minds.
The PC industry became more open for one reason and one reason only: Money.
The IBM monopoly was destroyed because clones were cheap, not because of ragtag freedom fighters.
Linux won over in the embedded space because it doesn't cost anything, not because folks suddenly got stars in their eyes over the GPL.
Apple will only change their practices when economics force them to. But it's very clear that they view a walled garden of hardware and software as key to their financial success, and everything they're doing is intended to build those walls just a little bit higher.
So until you can change that financial equation, nothing in the Apple ecosystem will change.
But, honestly, keep plugging away! Have fun! I personally love repurposing hardware to make it do cool things for which it was never intended. When I see projects like this, I think of Everest: We do it because it's there.
But let's not pretend that you're somehow going to change Apple just because you get the Linux kernel booting on the M1.
Also I am not involved in or affiliated with or even a likely user of the Asahi project, to be clear. I just find this attitude incredibly frustrating, and I'm definitely bristling at accused of being a young'un or some shit for believing people can actually do surprising things. I am not the dewy-eyed idealist you seem to think I am, I believe what I'm saying here because I've seen it happen over and over and over again.
What attitude? The attitude that Apple's hardware is closed and Apple should be criticized for building a walled garden? That we should, where possible, invest in open hardware and technology and put our money where our mouths are, so as to create the kinds of economic incentives that ensure that technology remains open in the future?
Do you really disagree with that?
> I am not the dewy-eyed idealist you seem to think I am, I believe what I'm saying here because I've seen it happen over and over and over again.
What "it" are we talking about here?
What do you think the end game is going to be?
I genuinely have no idea what your argument is, other than to tell me how I'm wrong without providing any specifics regarding how I'm wrong.
Please, enlighten me, I'm happy to listen!
We can do both. We should do both.
At any rate, I'd suggest you go read marcan_'s replies and the OP submitted to HN because the picture you paint and the picture they paint of this platform are not quite the same to begin with. I think the people doing the work deserve a little more credit to describe the platform they're working on.
So, other than for the intellectual curiosity (which is absolutely a great reason!), I have a simple question: why?
Edit:
By the way, thinking about it, I have my own answer to this question: So that this hardware can continue to remain useful long after Apple has ended support for it.
Of course, I continue to believe that it's better, now, to simply buy hardware that doesn't need this kind of reverse engineering to ensure longevity, and I steer my hardware purchases accordingly.
But the hardware exists, and people are buying it, so this project is a way to keep it alive after Apple eventually abandons it (which, granted, could be a long time; while I have a lot of problems with Apple, they are very good about continuing to support old gear).
For Linux and BSD, ALL OF IT was hacked and reversed engineered from the beginning. With your stupid mentality we would never have any free operating systems, we would only have proprietary operating systems. This is how its done. New hardware is released, someone hacks it, then its supported. If we are forced to wait like children for manufacturers permission or assistance (which is not actually required) then Linux, BSD, and other free / open source operating systems would never exist.
Linux has been ported to every modern computing device on the planet and this M1 port is par for the course. Only an actual idiot would recommend Linux devs should ignore the M1.
And no. That is not even remotely my argument.
It’s true that we are never going to see first-party support for Linux from Apple. That kind of sucks, and it would be much better for everyone if they had a more open and documented approach to this new platform. But it does at least have explicit support for booting third-party operating systems, and the attitude of the team behind the project is clearly not “hack together a prototype and we are done”.
I guess the point is that it’s not black and white, and there’s a large spectrum between “first-party support” and “unsupported hack”.
I support the work of anyone who gets Linux running on any hardware, I condemn the difficulty in which Apple unnecessarily restricts people from doing what they want with the hardware they own.
It is an unsupported hack because Apple doesn't provide means (such as documentation or code) for people to run what they want. So anything you can do will always end up being a method that Apple may decide to close up with later software updates and everything has to be reverse engineered from scratch.
Contrast this with AMD and Intel code in the Linux Kernel contributed by those companies themselves and being able to just boot from USB using a user accessible BIOS/UEFI loader.
It's Apple's restrictions that make this necessary to be a hack.
I've dropped Apple pretty hard (to the point where I've gone back to a flip phone - my objections to Android are significant as well), and I've accepted that if I want to use computers, it's probably best to use weird configurations that are often broken, because it discourages me from spending too much time on them.
I mean, I feel like even using x86 Linux boxes is lazy. :/ This box, currently, is an ODroid N2+ that's working fine. I've got a Raspberry Pi 4 over on the other side of my office (the "solar shed" posted yesterday, for some reason), and I've made that into a nice little desktop too. Still working on Spotify support, and I was actually quite surprised to find out that I can watch something on YouTube today...
My laptop is a PineBook Pro running a custom kernel (I really should push the sleep/resume patches I wrote for the sound card upstream... one of these days...).
Unsupported hacks are fun! They're challenging, and also reduce my dependence on computers, because odds are good that one or more simply don't work at any given moment.
And it's not just computers. The closest thing I have to a "daily driver" (other than the family car, which my wife and kids have priority for) is a 2005 Ural - sidecar motorcycle, evolution on a late 1930s BMW, quite literally the most vile handling thing you'll ever encounter on the road. It works, I work on it, I get places eventually, just no longer at the speed limit.
Anyway, the very insanity of bare metal Linux on the M1 actually appeals an awful lot to me.