Omarchy on MBP 2017 laptop? #2457
Replies: 7 comments 8 replies
|
Unsure of that mbp version. I've tested this model, sounds similar. The answer to your question is no not really. This is what is/isn't supported out of the box. Omarchy installs just fine. You can boot into the machine with no additional issues. Omarchy automated install using the ISO overwrites and re-partitions the whole drive. This is NOT OPTIMAL, as the touchbar, videocam, and sound are only accessible via the iBridge (T1 chip device) and the iBridge reports as in recovery when you boot into Omarchy. If you dual boot the operating system starting with macOS, then creating the necessary Linux partitions using archinstall, and finally manually installing Omarchy after arch is on the drive, it is possible to access the iBridge. Having the efi boot loader for Apple on the machine allows the hardware to be "turned on" so it can be used. Removing the Apple partitions from the drive does not allow the hardware to "turn on" correctly.
You may have some luck talking with the people on the Omarchy Mac Discord. They are focused on T2 chip devices 2018+, and they have limited people using T1 chip devices 2016-2017, but you might ask around. I'm working on a kernel module to support my device. I have the Touchbar working and am working on the sound. Stay tuned if you are interested. |
Could this be the reason why the T1 chip doesn't show with |
|
Thank you very much for quick response. My model does not have a touch bar, it is MBP 2017 with 3 thuderbolt port version. |
|
Sounds like a T2 variant. The discord I shared I. The last message likely
will have people who can offer their experience with the device.
Best of luck!
…On Wed, Oct 15, 2025 at 07:28 Srđan Pavlović ***@***.***> wrote:
Thank you very much for quick response. My model does not have a touch
bar, it is MBP 2017 with 3 thuderbolt port version.
—
Reply to this email directly, view it on GitHub
<#2457 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5LKCLZUXLBBQH6J3I4BDPD3XY4YVAVCNFSM6AAAAACJGFNN7KVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRYG4YDEMQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
This MacBook Pro 2017 does not have a T2 chip — all security and SSD management are handled by the Intel platform controller instead. |
|
Following up on this thread since it's where I started. All of it works now on a @iamobservable was right that keeping macOS matters, and here is the mechanism. The T1 has no firmware in ROM. macOS writes it to the EFI System Partition at You don't need a manual archinstall for this. Omarchy's own Free space install preserves it. Shrink the APFS container from macOS first, then pick that option. It creates its own 2 GB ESP and leaves Apple's 300 MB one untouched: Touch Bar needed two driver bugs fixed (PR upstream), neither of them discussed anywhere. The second is why this looks impossible: Wi-Fi is worth a look even if you don't care about 5 GHz. Audio works via Two corrections to Omarchy's Mac docs while I'm here:
Also useful for anyone here: Omarchy never writes Caveat: one machine, |
A huge thank you to the original poster 🙏I just wanted to take a moment to give credit where it's genuinely due. A while back someone in this group (the Here's what that original write-up gave me directly:
Why this matters to me: this is my daily driver. I use this machine for work every single day — the Touch Bar, the speakers, the keyboard mapping all being just-right makes Omarchy feel like it was designed for it, rather than "kinda working on a Mac." So — genuine, heartfelt thanks. Huge respect for the troubleshooting and, even more, for documenting it properly so random people like me can follow along and get a fully-working setup in an afternoon. If anyone reading this has a T1 Mac, dig into that repo before you start — it's the difference between a frustrating weekend and a smooth install. 🍎💚 -Details on my Macbook Pro 2017 touchbar. Omarchy on MacBook Pro (14,3) — Full Install & Hardware SummaryGenerated: 2026-08-28 · Machine ID: MBPOMARCH-001 1. Machine Identity
2. OS & Kernel
3. CPU
Matches SPX: "Quad-Core Intel Core i7", current_processor_speed 2.9 GHz. 4. Memory
5. Graphics / DisplayDual-GPU (automatic graphics switching via Apple gMUX):
Internal Panel (driven by Radeon via gMUX):
6. Storage
Partition layout (dual-boot with macOS + Omarchy on same APFS/disk):
Root: btrfs on LUKS, 362G total, ~23G used (7%). *Matches SPX: SN *********, model APPLE SSD SM0512L. 7. Network / Radio
Wi-Fi/BT support Apple's hardware via 8. Battery
9. Audio
Audio confirmed working (built-in output + mic). 10. Touch Bar (Apple T1) — HOW WE GOT IT WORKINGResult: WORKING. Touch Bar registered as input device
11. Keyboard Mapping Fix (this session)
12. Overall Health
Source of truth for baseline specs: |
|
Can you link to the repo/thread you are referring to please? I can't seem to find it. |
|
if you read up higher its all there https://github.com/nohzafk/omarchy-macbookpro-t1 |
|
🤦♂️ My bad! Not sure how on earth I missed that. Thanks for taking the time to point me in the right direction. |
|
easily done I do it all the time. :-) |
|
Got Omarchy 4.0.2 working on a 15" MacBook Pro 2017 (MacBookPro14,3, Touch Bar / T1, AMD dGPU) by following the nohzafk/omarchy-macbookpro-t1 guide plus the extra steps below; everything works except suspend/hibernate and Touch ID. Omarchy on MacBookPro14,3 (15" 2017, Touch Bar, T1) — steps beyond the T1 guideBase guide: nohzafk/omarchy-macbookpro-t1 Hardware and software
1. Wi-Fi 5 GHz: regulatory domainWith the NVRAM file and the real MAC in place, 5 GHz was still not available. sudo sed -i 's/^WIRELESS_REGDOM=.*/WIRELESS_REGDOM="DE"/' /etc/conf.d/wireless-regdom
sudo reboot
iw reg get | head -2 # country DE: DFS-ETSICodes tried on this machine:
NVRAM edits ( Result: 5 GHz link at 300 Mbit/s. 2. Reloading the Wi-Fi driver without a rebootnmcli radio wifi off
sudo modprobe -r brcmfmac_wcc brcmfmac
sudo modprobe brcmfmac
nmcli radio wifi on3. Suspend and hibernate disabledOn this 14,3 both S3 resume and hibernate resume end in a black screen and a forced
[Login]
HandleLidSwitch=lock
HandleLidSwitchExternalPower=lock
[Sleep]
AllowSuspend=no
AllowSuspendThenHibernate=no
AllowHibernation=no
AllowHybridSleep=no4. Screen brightness restored across reboots
5. Touch Bar: media keys by defaultChanged |
|
touch id is being worked on as well as ambient lights. check Boyd out https://x.com/0xBOYD. and if you want a nice cli in the terminal you can have a look at my dotfiles https://github.com/CG-8663/omarchy-dotfiles. welcome to Omarchy |
|
For T1 Touch Bar owners who already did a full-disk install and wiped macOS: as @nohzafk explained above, the T1 firmware is gone then. The chip shows up as If you'd rather not do that, I put together a keyboard-only workaround that doesn't need the T1 at all. It uses mainline Details: #13519 |
|
Correction to my comment above: a full-disk install doesn't mean you need macOS back. niconistal/t1-revive regenerates the T1 firmware from Linux. After running it, my On my MacBookPro14,3 the Touch Bar now works properly (Esc/media keys, hold Fn for F1–F12), along with the camera and the ambient light sensor with automatic brightness ( The keyd keyboard-only setup is still there as an opt-in fallback. |
Uh oh!
There was an error while loading. Please reload this page.
I have MBP from 2017 (Intel i5, 8gb ram, 250gb ssd...)
Did someone try Omarchy on that model? I would like to use it instead of MacOS... if it is possible,
and all of MBP hardware is supported.
All reactions