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!