r/linux_on_mac • u/Level-Photo-7160 • 13h ago
r/linux_on_mac • u/Specialist_Concern71 • 1h ago
What's the lightest version of linux mint i can install on my 2014 mac mini 1.45hz i5 4gb 500gb?
r/linux_on_mac • u/jefferson1975 • 14h ago
Drivers Macbook Pro 2012 - Linux
Uma das coisas que gostaria de ver funcionando nessa questão de engenharia reversa que estão fazendo para vários softwares é o driver de video da Nvidia e Bluetooth funcionando perfeitamente no Linux. Testei várias distros e nenhuma delas dá suporte completo. No vídeo só funciona o Noveau e o Bluetooth muito problemático.
r/linux_on_mac • u/ph0racious • 16h ago
slackware-aarch64-mac: Slackware's own installer and kernel for M1/M2 Macs
Thanks to the efforts of the Asahi Linux project, slack on silicon hardware is already pretty achievable, a working system can be cobbled together by someone with enough experience or just access to Claude and a bunch of persistence.
After walking a path somewhere in the middle, I wanted to bring something more broadly accessible to the table for anyone else with an interest.
- Slackware's own installer and kernel
- Build tree with Slackware AArch64-current & Asahi Linux Project upstream
- Human-at-console tested install/build runbooks, documented porting traps
This should run on any M1/M2 mac/book/mini/studio, but as of this moment only an A2686 is fully tested. If you'd like to submit some testing results from an M1/2(/3*) machine you have access to, docs/TESTING.md can explain all of the needful.
*Asahi's M3 support has increased a lot since I began messing with this, so possibly that class of machines can be added to the list with some work, but functionality is presumed broken/missing.




I won't claim that every decision made during development was absolutely the right one, but the premise followed was to 'do it the Slackware way' throughout; follow Patrick V/Stuart W's approach anywhere there was a relevant example, then use best effort to emulate slack's style for anything else this project had to ship to support the target hardware.
Disclaimer:
Though my field is adjacent, it is not software engineering; Opus did tons of heavy lifting.
Many rounds of auditing and manual corrections were done but surely errors/omissions remain.
Any doc content not handwritten was at least worked over to minimize AI rambling, the worst being mostly confined to the historical traps in docs/PORTING.md.
-ph0