MacBook Pro 2016 出门需要带多少转接头? - 知乎988被浏览<strong class="NumberBoard-itemValue" title=",302,971分享邀请回答216 条评论分享收藏感谢收起4746 条评论分享收藏感谢收起加载中，请稍后...
苹果MacBook Pro（Retina屏）15.4英寸系列
苹果MacBook Pro（Retina屏）15.4英寸
苹果MacBook Pro（Retina屏）15.4英寸产品为2012年6月上市的时尚镁铝合金产品，15.4寸 Retina屏，配Intel 双核处理器和苹果专属的Mac OS X Lion系统，采用银白色镁铝合金材质。
参考报价：
重要参数：
屏幕：15.4英寸
CPU主频：2.2GHz
核心数：四核心/八线程
显卡类型：核芯显卡
苹果在十多年前推出的PowerBookG4笔记本，在当年俗称飞机系列，因为外壳的铝合金和飞机的材质非常相似，更因为17英寸而被称作大飞机，冷光的背光键盘和精细的合金工艺，使得这款产品在当年存留着一些“风流史”。很显然，在当
苹果MacBookPro是一款15.4英寸 商务办公本产品，设计轻盈细致，B面的超窄边框屏幕让人一见倾心。银白色外观精美细腻，仅18mm的厚度以及2.04Kg的重量在15.4英寸笔记本中属于非常优秀的范畴。目前这款笔记本电脑正在京东 信诚平
屏幕尺寸：
笔记本重量：
(2款)(14款)
(2款)(2款)(2款)(2款)(2款)(2款)(2款)(2款)
(2款)(2款)(4款)(2款)(2款)(2款)(2款)
内存容量：
(2款)(1款)(6款)(3款)(1款)(2款)(1款)
硬盘容量：
(1款)(7款)(7款)(1款)
显卡芯片：
(1款)(8款)(2款)(1款)(1款)(1款)(2款)
操作系统：
(2款)(10款)(4款)
Intel 酷睿i7 4770HQ（2款）Intel 酷睿i7 4750HQ（2款）Intel 酷睿i7 4870HQ（2款）
含512GB SSD（8款）含256GB SSD（8款）
16GB（8款）8GB（8款）
NVIDIA显卡（11款）AMD显卡（1款）
在售经销商
酷睿i7 4770HQ/16GB/256GB SSD/核显
酷睿i7 4770HQ/16GB/256GB SSD/核显/Mac OS X Lion//大陆行货
在售经销商
酷睿i7 3740QM/16GB/512GB SSD/1GB GT650/Mac OS X Lion//大陆行货
酷睿i7 3740QM/16GB/512GB SSD/1GB GT650/Mac OS X Lion//香港行货
在售经销商
酷睿i7 3610QM/8GB/256GB SSD/1GB GT650/Mac OS X Lion//大陆行货
酷睿i7 3610QM/8GB/256GB SSD/1GB GT650/Mac OS X Lion//香港行货
5月8日新闻看点：看点一：Facbook承认有后门工作人员可随时登录看点二：坑哭：苹果电脑被爆严重设计缺陷看点三：沉寂好久摩托罗拉突然宣布新机看点四：日本发明透明厕所用完整个人不好了看点五：研究报告：每天拍照发朋友圈增
最近，苹果无论是macOS还是IOS系统都被爆出了许多设计漏洞，就连苹果也承认自己的团队内部的确出现了一些问题，并计划推迟下一代操作系统的发布来最大限度的减少可能存在的漏洞。不过，近日苹果的全新太空船总部也被爆出了一个
2017年苹果的iOS以及Mac电脑的系统都出现了许多匪夷所思的BUG以及漏洞，给用户的使用体验以及安全性都带来了极大的影响。不久前苹果表示今年iOS12的部分功能将推迟到2019年，之后macOS也爆出了推迟发布的消息。根据彭博社MarkG
苹果在十多年前推出的PowerBookG4笔记本，在当年俗称飞机系列，因为外壳的铝合金和飞机的材质非常相似，更因为17英寸而被称作大飞机，冷光的背光键盘和精细的合金工艺，使得这款产品在当年存留着一些“风流史”。很显然，在当
经过多个测试版本后，苹果终于正式公布OSX10.10Yosemite操作系统。苹果称这个第11版的OSX系统是自从2001年问世以来在视觉效果上变化最大的一次。那么事实真是如此么？下面我们就一起来回顾一下OSX系统的发展历史吧。苹果MacOSX
如果打算买一款新笔记本，有1万元以上的预算，恰好又对苹果不排斥的话，建议看看新款的MacBook Pro和MacBook。在前不如果打算买一款新笔记本，有1万元以上的预算，恰好又对苹果不排斥的话，建议看看新款的MacBook Pro和MacBook。在前不...
器材:尼康D7000(单机)镜头:18-105mm f/3.5-5.6 G VR时间: 18:02:29.50快门:1/1250光圈:F/7.1焦距:105毫米感器材:尼康D7000(单机)镜头:18-105mm f/3.5-5.6 G VR时间: 18:02:29.50快门:1/1250光圈:F/7.1焦距:105毫米感...
最主要原因是，苹果现在有了iPadPro，而且在最新的iPadPro广告中，苹果一再强调这是可以成为...
由于工作性质的原因，小编恰巧同时拥有这两款电脑，进过一段时间的使用，我觉得可以和大家介绍分享一下使用...
你好！ipad停用了，建议你重新恢复固件吧，点击打开链接下载最新固件重新下载固件，然后通过电脑更新吧...
您好！首先您的看到两台电脑的适配器电压是否都一样，然后在对比一下接口如果电压一样接口也一样那插进去就...
同光驱类型
同光驱类型
同光驱类型
同品牌，同摄像头
同光驱类型
同价位，同品牌，同摄像头
同价位，同品牌，同屏幕尺寸
同光驱类型
同光驱类型
同光驱类型
同光驱类型Unique features of MBP Browser.MyBrowserPage Mobile as Homepage.Lightning fast speed – Maxthon Cloud renders webpage using its optimized web engine that loads webpages and runs applications faster thaCloud sync – Maxthon Cloud syncs user data, history and tabs across any pCloud download – Simultaneous storage of user doCloud push – pushing user desired contents (webpage, text, pictures and links) from webpage to devices of their choice.Cloud share - Share web content with friends through Maxthon Cloud. What does it mean for you, the user?Easy to use makes it easy to get &#39;control’ of your devices.Maxthon Cloud’s design and user experience simplified and standardized across pYour web follows you. Maxthon Cloud will seamlessly sync through the cloud service users’ history, tabs, bookmarks, downloads and setting from one Maxthon CloCloud push and share Easily save and send web content from and to any of your devices. Share the same content with your friends – through the web or SMS.Superior Speed Users can enjoy faster speed in loading webpage and running applications.In short, Maxthon Cloud and MyBrowserPage offers a total seamless web browsing experience
手机扫描二维码下载
大家都在玩
大小：4.82MB
大家都在玩
热门安卓应用
WiFi万能钥匙
百度输入法
搜狗输入法
其他用户正在浏览
猪猪保卫战
蘑菇园 官方中文版笔记本电脑应该选择 ThinkPad 还是 MacBook？为什么？ - 知乎<strong class="NumberBoard-itemValue" title="被浏览<strong class="NumberBoard-itemValue" title=",543,028分享邀请回答78247 条评论分享收藏感谢收起46171 条评论分享收藏感谢收起From ArchWiki
(Redirected from )
Related articles
Installing Arch Linux on a MacBook (12"/Air/Pro) or an iMac is quite similar to installing it on any other computer. However, due to the specific hardware configuration of a Mac, there are a few deviations and special considerations which warrant a separate guide. For more background information, please see the
and . This guide contains installation-instructions that can be used on any Apple computer whose hardware is supported by the Linux kernel. Please see 'related' pages (on the top right of this page) for model-specific tips and troubleshooting.
Specifically, the procedure for installing Arch Linux on a MacBook is:
: It always helps to start from a clean, backed up, and up-to-date install of OS X.
: Resizing or deleting the OS X partition to create partitions for Arch Linux.
: Making sure that the new partition is bootable.
: Actually installing Arch Linux.
: MacBook-specific configuration.
Before proceeding with the installation of Arch Linux, it is important to ensure that the latest firmware updates for you MacBook are installed. This procedure requires OS X.
In OS X, open the App Store and check for updates. If your mac finds and installs any updates, make sure to reboot your computer, and then check again for updates to make sure that you installed everything.
Note: If you uninstalled OS X or want to reinstall it,
has great instructions.
It is advisable to keep OS X installed, because MacBook firmware updates can only be installed using OS X. However, if you plan to remove OS X completely, make backups of these files, which you will need in Linux for adjusting the :
/Library/ColorSync/Profiles/Displays/*
Continue to
Partitioning of the storage drive is no different from any other PC or laptop. However, if you plan on keeping OS X for dual booting, you should consider that, by default, a MacBook's drive is formatted using GPT and contains at least 3 partitions:
EFI: the ~200 MB .
OS X: the main partition containing your OS X installation. It is formatted using .
Recovery: A recovery partition present in almost all MacBooks running OS X 10.7 or newer. It is usually hidden from OS X but can be viewed with partitioning tools.
Note: In Macs that use the , the partition scheme could be different.
How to partition depends on how many operating systems you want install. The following options will be explained:
Single boot:
Dual boot:
(recommended so you can still return to OS X when needed)
Triple boot:
This situation is the easiest to deal with. Partitioning is the same as any other hardware that Arch Linux can be installed on. Please refer to the standard
for details.
Note: It is advisable to disable the MacBook startup sound before proceeding with partitioning. Just boot in OS X, mute your system sound and reboot again to the Arch Linux Installation media. Please keep in mind that the volume of the startup sound can only be modified reliably in OS X.
If you want to configure you system in order to have full-disk encryption, please look at the
page for details.
An example for a very basic partitioning, that does not consider a separate /home partition nor encryption or LVM, is the following:
mountpoint
Done, you can continue to
You need to partition your hard drive while keeping the partitions used for OS X/Windows. If you wish to keep OS X, the easiest way is to use partitioning tools in OS X and then finish with Arch Linux tools.
If you OS X partition is encrypted with FileVault 2, you must disable the disk encryption before proceeding. After the OS X partition has been resized, FileVault 2 can be re-enabled.
Procedure:
In OS X, run Disk Utility.app (located in /Applications/Utilities)
Select the drive to be partitioned in the left-hand column (not the partitions!). Click on the Partition button.
Add a new partition by pressing the + button and choose how much space you want to leave for OS X, and how much for the new partition. Keep in mind the new partition will be formatted in Arch Linux, so you can choose any partition type you want.
If the above completed successfully, then you can continue. If not, then you may need to fix your partitions from within OS X first.
Boot the Arch installation media or
by holding down the Alt during boot. Proceed with .
It is possible to resize the newly created partition from within the Arch installation media, or delete it in order to proceed with the creation of other partitions (eg. swap).
Tip: Instead of cluttering your drive with different partition, it is possible to use a
instead of a dedicated partition. Another solution can be setting up
in order to use the newly-created partition as a container. Please refer to the linked articles.
Run cgdisk
Delete the partition you made in Disk Utility.app and create the necessary partitions for Arch Linux. OS X likes to see a 128 MiB gap after partitions, so when you create the first partition after the last OS X-partition, type in +128M when cgdisk asks for the first sector for the partition. More information about Apple's partitioning policy can be read
. A simple example (no LVM, crypto):
The swap partition is optional on machines with 4GB of RAM or more. A
can be created later.
The easiest dual-boot option is to install rEFInd from inside OS X, to its root directory (default for install.sh). Following that, copy the driver folder from the installation tarball into the new rEFInd location, and uncomment the lines "scan_all_linux_kernels" and "also_scan_dirs" options in refind.conf. Configuration of boot options can then be done from a refind_linux.conf in Arch's /boot directory.
If you want to be able to boot GRUB from the Apple boot loader, you can create a small hfs+ partition (for convenience, use OS X to format it in Disk Utility.app afterwards). Follow the GRUB EFI install procedure, and mount your /boot/efi directory to the hfs+ partition you created. Finally, finish up again in OS X by blessing the partition. This will set GRUB as the default boot option (holding alt at startup goes to the mac boot options screen still. See ).,
OS X's EFI partition can be shared with Arch Linux, making the creation of an additional EFI partition dedicated to Arch completely optional.
Note: For more information on partitioning, see
mountpoint
Boot Arch Linux from the Apple boot loader (optional)
swap (optional)
Done, you can continue to
Run parted as root.
Delete the empty space partition and partition the space as you would for any other installation. Note that MBR is limited to 4 primary partitions (including the efi partition). That leaves 2 primary partitions for Arch. One strategy is to have a system and home partition, and use a swap file (I have not tried to use logical partitions). Another is to dedicate one partition to a shared partition (see below).
Next, create new filesystems on those partitions which need them, especially the partition which will contain /boot. If you are not sure how to do this using mkfs.ext2 (or whatever), run /arch/setup and work through until you get to Prepare Hard Drive and use the "Manually configure block devices..." option, then exit the installer. This is necessary so that rEFIt will set the right partition type in the MBR in the next step (without an existing filesystem, it seems to ignore the partition type set by parted), without which GRUB will refuse to install to the right partition.
At this point you should reboot your computer and have rEFIt fix the partition tables on your hard drive.
(If you do not do this, you may have to reinstall GRUB later on in order to have your Mac recognize the Linux partition.)
When you are into the rEFIt menu, select update partition table, then press y. Reboot.
Done, you can continue with .
This may not work for everyone but it has been successfully tested on a MacBook from late 2009.
The easiest way to partition your hard drive, so that all these operating systems can co-exist, is to use disk utility in OS X, use the formatter on windows XP, install XP and then finish with Arch Linux tools.
Warning: It is highly recommended that this only be attempted after a clean install of OS X. Using these methods on a pre-existing system may have undesired results. At least back your stuff up with timemachine or clonezilla before you begin.
Procedure:
In OS X, run Disk Utility (located in /Applications/Utilities).
Select the drive to be partitioned in the left-hand column (not the partitions!). Click on the partition tab on the right.
Select the volume to be resized in the volume scheme.
Decide how much space you wish to have for your OS X partition, how much for XP, and how much for Arch Linux. Remember that a typical installation of OS X requires around 15-20 GiB, and XP about the same, depending on the number of software applications and files. Something like OS X 200Gb, XP 25Gb, Arch 25Gb should be fine.
Put your decisions into action by pressing the + button and adding the new partitions, Label them as you like and make sure that your XP partition is the last one on the disk and is formatted for FAT32. It is probably best to have Arch formatted in HFS format as to not confuse you later, it will be reformatted anyway.
So in linux terms your partitions will be something like:
sda (disk)
sda1 (Mac boot partition - you cannot see this one in OS X)
sda2 (OS X install in HFS+)
sda3 (Arch install temporarly in HFS)
sda4 (XP install in FAT32)
Finally, click apply. This will create a new partition out of the empty space.
Note: Using this method you may not be able to have a shared partition between OS X and Arch Linux, this is because the mac will only allow for 4 active partitions. You will however be able to mount a HFS partition in Arch for one workaround. There are other workarounds possible also.
If the above completed successfully, you can continue. If not, then you may need to fix your partitions from within OS X first.
You will not be needing boot camp this way, the program rEFIt is much more flexible (though not as flexible as GRUB). Download and install rEFIt
Go into a terminal in OS X and perform the following, this will enable the rEFIt boot manager.
cd /efi/refit
./enable.sh
Reboot to check the rEFIt is working, it should appear on boot. When it comes up go to the rEFIt partition manager and agree to the changes.
Put your XP install CD and boot it with rEFIt - You may have to reboot a few times until it is recognized by the boot loader. Install XP and once it is installed use the OS X installation CD to get your drivers running nicely in XP.
Note: when installing XP make sure you select your XP partition and format it again inside the XP installer. If you do not reformat it will not work.
Boot the Arch install CD, log in as root and run # /arch/setup.
Follow the install as normal but note that you will have to tell that arch installer to mount sda3 as the root partition and format it as ext3, there will not be a /boot or swap partition so ignore those warnings.
At this point, if you are dual booting, you should reboot your computer and have rEFIt fix the partition tables on your hard drive.
(If you do not do this, you may have to reinstall GRUB later on in order to have your Mac recognize the Linux partition.)
When you are into the rEFIt menu, select update partition table, then press Y.
Done! You can continue to .
Apple's native EFI bootloader reads .efi files located inside the
at /EFI/BOOT/BOOTX64.EFI. Luckily, this is also the default install location for the
binary. This means that booting linux using systemd-boot is very simple.
First, make sure you mounted the EFI System Partition at /boot
Proceed with
Once inside the chrooted enviroment, type the following command to install systemd-boot:
# bootctl --path=/boot install
The above command will copy the systemd-boot binary to /boot/EFI/BOOT/BOOTX64.EFI and add systemd-boot itself as the default EFI application (default boot entry) loaded by the EFI Boot Manager.
Proceed to
in order to correctly set up the bootloader
At the next reboot, the Apple Boot Manager, shown when holding down the option key when booting the MacBook, should display Arch Linux (it will be displayed as EFI Boot as a possible boot option.
Tip: If you installed Arch Linux alongside OS X, you will be able to change the default boot location from
system Settings inside OS X. If Arch Linux does not show up as a possible boot option, you will have to mount the EFI System Partition inside OS X before selecting your boot option:
$ diskutil mount disk0s1
This article or section needs language, wiki syntax or style improvements.
Reason: Uses
procedure and explicitly lists many basic commands. (Discuss in )
Despite using UEFI, the MacBook's native EFI bootloader . Instead, it looks for .efi files inside all the partitions in internal and external drives and shows them as possible boot options if certain conditions are satisfied. For example, MacBooks can detect an existing OSX installation after checking that:
there is a partition formatted as HFS+
the partition contains the partition id af00
in the root of that partition, there is a file called mach_kernel
inside that partition, there a boot.efi file inside /System/Library/CoreServices
This means that configuring an Arch installation to be automatically recognized by the MacBook bootloader is possible. Moreover, it simply requires a properly-formatted HFS+ /boot partition and does not require meddling with the EFI system partition. The advantage of this method is that it can coexist with OS X nicely and allows to avoid other bootloaders such as rEFInd. However, this requires manual configuration. The following steps will illustrate how to perform this configuration using GRUB.
First, while configuring a new Arch installation, create a separate /boot partition. Many tools are available in the Arch ISO, for example cgdisk.
Make sure the partition is at least ~250 MB in size, since it will be used to store the kernel as well as any custom kernel you will install in the future. Moreover, make sure the partition type is set as Apple HFS/HFS+ (it will appear as Apple HFS/HFS+ in fdisk/cgdisk or af00 in gdisk)
Since the Arch installation ISO does not include the AUR package, we need to install it in the installation environment before proceeding with formatting the new partition as HFS+
# pacman -Sy hfsprogs
# modprobe hfsplus
# mkfs.hfsplus /dev/sdX -v "Arch Linux"
Note: replace /dev/sdX with the correct device as appropriate
Done, proceed with
Once inside the chrooted enviroment, don’t forget to install the AUR package on the newly installed system as well. After the installation of the package, regenerate the initramfs while chrooted
# mkinitcpio -p linux
Once inside the chrooted enviroment, install the
packages. The following steps install the GRUB UEFI application to /boot/EFI/arch/System/Library/CoreServices/boot.efi and install its modules to /boot/grub/x86_64-efi.
# grub-install --target=x86_64-efi --efi-directory=/boot
After that, remember to create a standard configuration file:
# grub-mkconfig -o /boot/grub/grub.cfg
As you can see, the directory structure of the boot.efi is not correct, as the /System/Library/CoreServices directory is not supposed to be a subdirectory of the /boot/EFI/ folder. For this reason, we need to relocate the boot.efi stub in a location the MacBook bootloader is able to recognize:
# mv /boot/EFI/arch/System/ /boot/
# rm -r /boot/EFI/
Also, create a dummy mach_kernel file
# touch /boot/mach_kernel
After that, you need to create the following file
# nano /boot/System/Library/CoreServices/SystemVersion.plist
&?xml version="1.0" encoding="UTF-8"?&
&plist version="1.0"&
&key&ProductBuildVersion&/key&
&string&&/string&
&key&ProductName&/key&
&string&Linux&/string&
&key&ProductVersion&/key&
&string&Arch Linux&/string&
At the next reboot, the Apple Boot Manager, shown when holding down the option key when booting the MacBook, should display Arch Linux as a possible boot option. Selecting that option will boot GRUB.
Done! GRUB can now be selected on the standard MacBook bootloader and you can boot into your newly installed Arch Linux.
After the installation, it is optionally possible to set a custom icon that will be displayed in the MacBook boot loader. In order to do that, you need to install the ,
and AUR packages. After that, just follow the following commands:
$ wget -O /tmp/archlinux.svg
$ rsvg-convert -w 128 -h 128 -o /tmp/archlogo.png /tmp/archlinux.svg
$ sudo png2icns /boot/.VolumeIcon.icns /tmp/archlogo.png
$ rm /tmp/archlogo.png
$ rm /tmp/archlinux.svg
Obviously, you can replace the Arch logo with any other icon you like.
This article or section is out of date.
Section that describes bootloader setup for other setups should be revised and re-structured into more readable way (Discuss in )
Tip: rEFIt is a popular bootloader for EFI-firmware computers (including Macs). It can be installed at any time during the installation. For instructions, please see .
If you are going for an Arch Linux-only setup, installing the bootloader is no different than on any other machine: Install ,
or other bootloader of your choice.
If, on the other hand, you are dual/triple booting, then read on.
If you would like to use GRUB as your main bootloader and use the "boot while holding the Alt/Option key" method to go back to OS X rather than using alternatives such as rEFIt (, mentioned previously in
and ) then you must install
to your Mac's already-existing EFI partition (see below).
These instructions are known to work on a MacBook Pro (Early 2011). Please read the procedure carefully as well as the details following it.
With a new MacBook Pro (Mid 2014), this procedure worked only after installing the
Procedure:
Make a directory named efi in /boot
Mount the already-existing EFI partition on your Mac to this /boot/efi directory
Install GRUB to this directory
Make a directory named
/boot/grub
grub.mo from
/usr/share/locale/en\@quot/LC_MESSAGES/ to
/boot/grub/locale
Generate a configuration for GRUB
Done! GRUB will now start on reboot and you can boot into your newly installed Arch Linux.
Remember to hold ALT/Option key while starting your computer if you want to boot back into OS X.
Details (quoted from ):
Finish the standard Arch install procedures, making sure that you install
and partition your boot hard disk as GPT.
The UEFI system partition will need to be mounted at /boot/efi/ for the GRUB install script to detect it:
# mkdir -p /boot/efi
# mount -t vfat /dev/sdXY /boot/efi
Where X is your boot hard disk and Y is the efi partition you created earlier.
Install GRUB UEFI application to
and its modules to /boot/grub/x86_64-efi using:
# modprobe dm-mod
# grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=arch_grub --recheck --debug
# mkdir -p /boot/grub/locale
# cp /usr/share/locale/en\@quot/LC_MESSAGES/grub.mo /boot/grub/locale/en.mo
Generate a configuration for GRUB
# grub-mkconfig -o /boot/grub/grub.cfg
It is possible to boot directly from GRUB in EFI mode without using rEFIt through what is known as "blessing" after placing GRUB on a separate partition.
These instructions are known to work on a MacBook7,1. It is advisable to host GRUB on either a FAT32 or HFS+ partition, but ext2 or ext3 may also work. GRUB's appleloader command does not currently work with the 7,1, but support can be added with the patch available .
After the GRUB install is in the desired location, the firmware needs to be instructed to boot from that location.
This can be done from either an existing OS X install or an OS X install disk.
The following command assumes that the GRUB install is in /efi/grub on an existing OS X partition:
# bless --folder /efi/grub --file /efi/grub/grub.efi
Some models may need EFI_ARCH set to i386.
bzr branch --revision -2 bzr://bzr.savannah.gnu.org/grub/trunk/grub grub
./autogen.sh
patch -p1 & appleloader_macbook_7_1.patch
export EFI_ARCH=x86_64
./configure --with-platform=efi --target=${EFI_ARCH} --program-prefix=""
cd grub-core
../grub-mkimage -O ${EFI_ARCH}-efi -d . -o grub.efi -p "" part_gpt part_msdos ntfs ntfscomp hfsplus fat ext2 normal chain boot configfile linux multiboot
cp grub.efi *.mod *.lst yourinstalllocation
Note: This section is only required if you want to have OS X installed along with Arch Linux. If not, follow the steps in the official install guide, then skip to .
Boot from the Arch Linux install CD, or from a
bootable USB drive.
On a MacBookPro7,1, I had an error booting the installation media Version : "unable to handle kernel NULL pointer dereference at 0010" during pacpi_set_dmamode. To fix this problem, boot with the option: acpi&#61;off. After chrooting, add MODULES&#61;"ata_generic" into /etc/mkinitcpio.conf and execute mkinitcpio -p linux, see: .
Some MacBook users report strange keyboard output such as long delays and character doubling. To fix this problem, boot with the following options: arch noapic irqpoll acpi&#61;force
Proceed through the installation as described in the
except in the following areas:
stage, do only the
steps, taking care to assign the correct partitions. Partitions have already been created if you followed
(for booting with EFI) After the
stage, exit the installer and install .
(for booting with BIOS-compatibility) In the
stage, edit the menu.lst file and add reboot=pci to the end of the kernel lines, for example: kernel /vmlinuz-linux root=/dev/sda5 ro reboot=pci This will allow your MacBook to reboot correctly from Arch.
(for booting with BIOS-compatibility) Also in the
stage, install GRUB on whatever partition that /boot is on. Warning: Do not install GRUB onto /dev/sda&#160;!!!
Doing so is likely to lead to an unstable post-environment.
stage, edit /etc/mkinitcpio.conf and ensure the keyboard hook is in the HOOKS line somewhere after the autodetect hook.
This will load the drivers for your keyboard in case you need to use it before Arch boots (e.g. entering a
password or using the troubleshooting shell).
When the install process is complete, reboot your computer.
If using optical media, hold down the eject key as your MacBook starts, this should eject the Arch Linux install disk.
If dual-booting OS X and Arch Linux, hold down the alt (option) key while the system boots to use the Mac bootloader to select which OS to boot.
This article or section needs language, wiki syntax or style improvements.
Reason: Duplicated information, does not comply with . (Discuss in )
for system management directions and post-installation tutorials like setting up a graphical user interface, sound or a touchpad.
Different MacBook models have different graphic cards.
To see which graphics card you have type:
$ lspci | grep VGA
If it returns a string containing Intel, read .
If it returns NVIDIA, read .
Otherwise if it returns ATI or AMD, read .
Tip: If you have installed OS in EFI mode and NVIDIA binary drivers are working only in BIOS mode (e.g. you get black screen on EFI boot), try this approach:
For MacBooks with NVIDIA graphics, for the backlight to work properly you may need the AUR package.
If backlight control does not work after installing nvidia-bl, you should
apple_bl kernel module.
If backlight control does not work even this way, try setting module parameters. Uncommenting options nvidia_bl max_level=0x1ffff shift=11 in /etc/modprobe.d/nvidia_bl.conf should do the trick.
Alternatively, you can choose to use the AUR package. If you do so, you may wish to change the step settings in /etc/pommed.conf.mactel to something around
depending on how many levels of brightness you desire.
The max brightness is around 80000, so take that into account.
The touchpad should have basic functionality by default. A true multitouch driver which behaves very similarly to native OS X is included in the AUR package.
Configuration options are documented in the .
The following mtrack options work well on a MacBook7,1:
Option "Thumbsize" "50"
Option "ScrollDistance" "100"
Probably, you also need to add:
MatchDevicePath "/dev/input/event10"
To disable tap-to-click (that is, to press down to click) by default, add the following to your mtrack configuration section
"TapButton1" "0"
"TapButton2" "0"
"TapButton3" "0"
Natural scrolling: To configure natural two finger scrolling similar to , refer to .
If you are using AUR, you can simply swap the scroll up and scroll down buttons (along with the scroll left and scroll right):
/etc/X11/xorg.conf.d/10-mtrack.conf
Option "ScrollUpButton" "5"
Option "ScrollDownButton" "4"
Option "ScrollLeftButton" "7"
Option "ScrollRightButton" "6"
Special Note About Older Macbook Models (confirmed on MacBook2,1): On older Macbook models (pre-multitouch), the touchpad will not function properly until you install the xf86-input-synaptics package. Please see
for more information on installing and configuring this package.
Note on MacBookPro5,5: I found it is much simpler to use the
in Extra. Although it does not have much function as 3 finger swipe, this driver provides faster response. AUR also provides a simple GUI config. Below is a Xorg config file /etc/X11/xorg.conf.d/60-synaptics.conf for reference only.
Section "InputClass"
Identifier "touchpad catchall"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "SHMConfig" "on"
Option "TapButton1" "1"
Option "TapButton2" "3"
Option "TapButton3" "2"
Option "PalmDetect" "on"
Option "VertEdgeScroll" "off"
Option "HorizEdgeScroll" "off"
Option "CornerCoasting" "off"
Option "EdgeMotionUseAlways" "off"
Option "AreaLeftEdge" "10"
Option "AreaRightEdge" "1270"
EndSection
For some users, the two-finger right-click may not work correctly and trackpad may also become less responsive after these settings. For me, removing the 'AreaLeftEdge' and 'AreaRightEdge', solved that problem.
OS X like MultiTouch Gestures currently broken due to newer synaptic drivers! For users looking to add more of OS X's multitouch gestures to Arch,
is a highly customisable, light weight perl script, which does just that. Once installed and configured (see xSwipe wiki on Github) I would recommend adding xSwipe as a .
MacBook keyboards work by default. For swaping fn keys with Fx keys see .
To enable it you can map with right application like xbindkeys or through DE but another very good way, that we recommend, is to install the AUR package.
Edit the /etc/pommed.conf according to your hardware on MacBook, building it from /etc/pommed.conf.mac or /etc/pommed.conf.ppc example files.
Note that you can also run it without a configuration file, the defaults may work for you. Then
and start pommed.service.
Tip: if you are using Gnome or KDE you can easily configure 3rd level functionality, multimedia key, etc. in Keyboard Preferences.
Note: See the
page for other configuration information.
The keyboard backlight is controlled by /sys/class/leds/smc::kbd_backlight.
Write the desired value to brightness in that directory.
Both AUR or AUR (stalled since 2015) allow to control keyboard backlight though scripts. With the appropriate udev rules or
they allow light-level changes without being root.
As of , AUR provides a "just-works" solution tested on a MacbookPro 8,1.
Alternatively you might want to check out the
wiki page.
If the brightness does not function correctly through pommed, make sure you have installed the AUR package and insert
find . -name "*" -exec sed -i 's/mbp_backlight/nvidia_backlight/' '{}' \;
into the second line of the pommed PKGBUILD build() function and remake the package. From .
Another possible solution is to modify the pommed PKGBUILD build():
find . -name "*" -exec sed -i 's/nvidia_backlight/apple_backlight/' '{}' \;
If the previous does not work try the following,
run nvidia-settings, edit
the file '/etc/X11/xorg.conf' and add this line into the Device section:
Option "RegistryDwords" "EnableBrightnessControl=1"
Save and reboot and check backlight buttons work.
More information available at
Different MacBook models have different wireless cards.
You can easily check what card do your MacBook have by:
# lspci | grep Network
If you have an Atheros card, all should work out-of-the-box.
If you have a Broadcom card, follow the
5.0 and 6.0 generation MacBooks may have a BCM43xx, follow the instructions for the broadcom-wl driver on the
page. The interfaces can swap during reboot so its best to define them in a udev rule (instructions on the
8.1 generation MacBooks have BCM4331, for which support is not present in either Linux (3.0 and 3.1) or the proprietary drivers by Broadcom. There is however preliminary support for it in Linux 3.2. To run the drivers on earlier kernels, you will need to use
If you have the correct broadcom DKMS driver (i.e. broadcom-wl-dkms) installed and your wifi card is still not being recognised, try rebuilding the driver (See ).
If your connection frequently drops, you may have to turn off Wi-Fi power management.
Eduroam or similar may crash your network manager. Simply delaying the connection after login should do the trick
is a very simple to set up set of scripts what will maximize your battery duration. A MacBook Air 2013 with powerdown provides about 11 hours of light usage with just powerdown installed.
All the usual
recomendations apply as well.
Adding 'acpi_osi=' to kernel parameters reportedly brings the battery life of a MacBook Air 2013 from 5 hours to 11-12 hours. See
for more information.
Suspending (suspend to ram) and hibernating (suspend to disk) work fine out of the box:
systemctl suspend
Issues were reported where the machine would "suspend immediately after resume" in certain conditions when suspending by closing the lid. This was solved by setting the option "sleep-inactive-ac-type" to "nothing" using dconf-editor, option path: org &#8594; gnome &#8594; settings-daemon &#8594; plugins &#8594; power).
for details on how to configure hibernation. Noticably, you'll need a swap partition or file (see the mentioned article for further instructions).
If after suspend laptop is woken up after few seconds, may help to disable all stuff in /proc/acpi/wakeup, exclude LID0:
# echo XHC1 & /proc/acpi/wakeup
$ cat /proc/acpi/wakeup
Device S-state
Sysfs node
S3 *disabled
S3 *disabled
S3 *disabled
S3 *disabled
S3 *disabled
S3 *disabled
S4 *disabled
S3 *disabled
S3 *disabled
S3 *disabled
S3 *disabled
S3 *disabled
S3 *enabled
And for permanent disabling:
$ cat /etc/udev/rules.d/90-xhc_sleep.rules
# disable wake from S3 on XHC1
SUBSYSTEM=="pci", KERNEL==".0", ATTR{power/wakeup}="disabled"
If this does not work, check that ARPT is disabled, and add a corresponding rule to udev, like this:
SUBSYSTEM=="pci", KERNEL==".0", ATTR{power/wakeup}="disabled"
If this still does not work, try disabling LID0.
This way suspending via lid-closing should be made impossible, so you might want to follow the instructions in
to make suspending via both lid-closing and systemd possible, by using systemd services.
The values can be read from:
/sys/devices/platform/applesmc.768/light
A "cat" on this path returns two-tuples like (4,0). The below referenced lighter script ignores the second value - which always seems to be 0 - and uses the first number as measured environment lighting brightness value.
If you want to use the built in light sensor to automatically adjust screen and keyboard backlight brightness check out
(simple perl script, easy to fine-tune) and Lightum
(Requires Gnome or KDE but is older and more complete than Lighter).
If using , the internal speaker might not be disabled when using the headphone jack. To solve this, enable "Auto-mute" using alsamixer
First of all follow
wiki page, then if something does not work correctly, continue reading this part.
Edit your /etc/modprobe.d/50-sound.conf or /etc/modprobe.d/modprobe.conf appending this line:
options snd_hda_intel model=intel-mac-auto
This should automatically specify the codec in your MacBook. If you have a MacBookPro12,1, you might need
options snd-hda-intel index=1,0
instead. Alternatively, for MacBookPro5,X, you can use:
options snd_hda_intel model=mb5
(note that the jack output is controlled with "HP").
If you have an iMac8,1, you should instead use
options snd-hda-intel model=mbp3 position_fix=2
For Aluminium iMacs, see
You can try to specify other options, that depend on your hardware. All other possible settings are listed in Kernel Documentation, avaible online:
Then, reboot.
Bluetooth should work out-of-the box. See the article on
to install and configure all software needed.
If you use a magic mouse you will find it works nicely out of the box. You might want to tweak some settings such as scroll-speed or acceleration. There is no GUI for this at this time. The only way to set these settings is to instruct the kernel driver (hid_magicmouse) with parameters. Create a modprobe config file for your mouse.
/etc/modprobe.d/magicmouse.conf
options hid_magicmouse scroll-speed=55 scroll-acceleration=1 emulate_3button=0
This will instruct the driver to have a fast scroll-speed, do exponential acceleration and do not emulate a 3 button mouse. You can find an overview of all parameters and their current settings in /sys/module/hid_magicmouse/parameters.
To play with the settings without rebooting you can also set them through the command line, like so:
# echo 55 & /sys/module/hid_magicmouse/parameters/scroll_speed
Note: Using kernel 4.10.10-1-macbook the Magic Mouse (hid_magicmouse) will cause a lot of system lock ups. If you experience random lock ups, try a different, wired, mouse to see if this is the case for you as well.
Note: Linux kernel from 2.6.26 includes the Linux UVC driver natively. MBP 6,2+ (Kernel ~2.6.37+) iSight works out of the box without the need to use firmware from OS X. Only use isight-firmware-tools if it doesn't work normally.
iSight webcams on MacBooks or pre 6,2 MacBook Pros (6,2 came out around 2010) require the Apple's proprietary firmware that cannot be redistributed. It must be extracted from OS X and loaded onto Arch.
You will need to install AUR to extract the firmware. This package also includes a udev rule and ELF binary that are necessary, even once you have extracted the firmware file into /lib/firmware/isight.fw, for the file to be loaded every time you boot your computer (namely /etc/udev/rules.d/isight.rules which uses /usr/lib/udev/ift-load).
Instructions:
First you need to get the firmware out of a particular file located on your OS X install. It is located in /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBVideoSupport.kext/Contents/MacOS/AppleUSBVideoSupport.
The AppleUSBVideoSupport file from a OS X 10.6 (Snow Leopard) installation may not work properly. If possible, use the file from OS X 10.5 or earlier.
To mount the OS X drive if multi-booting:
# mkdir /media/OSX
# mount -t hfsplus /dev/sda2 /media/OSX
Then, install the AUR package.
Locate the AppleUSBVideoSupport file in the OS X directory listed above. Either copy it over to your Arch system (Any OS X installation should do, such as an iMac, not just one specific to your system) or, if multi-booting, mount the OS X drive and navigate to the directory. (On 10.7 (Lion) the directory is /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/AppleUSBVideoSupport.kext/Contents/MacOS.) In that directory you can go ahead and extract the driver:
# ift-extract --apple-driver AppleUSBVideoSupport
When it's done, check that the firmware has been found:
# ls /lib/firmware/isight.fw
Once successful, completely SHUTDOWN your Mac and start it back up again (to clear the hardware state of the webcam). Do not reboot.
It should be automati if it isn't you can load the uvcvideo module .
You can use many applications to test the webcam:
# mplayer tv:// -tv driver=v4l2:width=320:height=240:device=/dev/video0 -fps 30
A simple solution to take snapshots is:
# mplayer tv:// -vf screenshot
and the pressing the s key to take a snapshot. Files are of the format shot\d\d\d\d.png and are reported in the standard output.
According to Apple, all recent MacBook models contain a Facetime HD camera instead of the iSight. The following list is an example:
iMac (21,5" mid 2011)
iMac (27" mid 2011)
MacBook Air (mid 2011)
MacBook Pro (15" early 2011)
MacBook Pro (17" early 2011)
MacBook Pro (13" early 2011)
If your MacBook is more recent than the models listed above, it is likely equipped with the Facetime HD camera as well.
In order to make the camera work, you need to install the AUR package. This will enable camera video support through the facetimehd kernel module.
In order to verify if the Facetime camera is working after the installation of both packages, you'll need to reboot your system.
Note: Keep in mind that, although working, this is a reverse-engineered driver. PC suspension is not supported if a program that is keeping the camera active is running.
For reading temperature just install . See the
page for more information.
We can use color profiles from OS X.
First, install the AUR package.
Second copy pre-saved color profiles placed in /Library/ColorSync/Profiles/Displays/ on OS X partition to ~/colorprofiles/ for example.
There are color profile files agree with in MacB select the right one:
Color LCD-4271800.icc for MacBook Pro with CoreDuo CPU
Color LCD-4271880.icc for MacBook with Core2Duo
Color LCD-4271780.icc for MacBook (non-Pro) based on CoreDuo or Core2Duo.
Tip: Also OS X allows to save current color profile from Displays & Color section of the Mac OS System Preferences, in this case file is saved to /Users/&username&/Library/ColorSync/Profiles.
Finally you can activate it by running
# xcalib ~/colorprofile.icc
Note: Previous command set the color profile only for this mean that you must run it every time you login in your system. For automating it you can execute the command by Autostart Application, concording with your DE (or add the command to your login manager's initialization script, e.g. /etc/gdm/Init/Default).
Warning: GNOME will revert the profile set by xcalib. It's preferable to set the profile using Color in settings.
First, to correctly install and configure the lirc software that control IR see
Then make LIRC use /dev/usb/hiddev0 (or /dev/hiddev0) by editing /etc/conf.d/lircd. Here is how mine look:
# Parameters for lirc daemon
LIRC_DEVICE="/dev/usb/hiddev0"
LIRC_DRIVER="macmini"
LIRC_EXTRAOPTS=""
LIRC_CONFIGFILE="/etc/lirc/lircd.conf"
Use irrecord (available when installing lirc) to create a configuration file matching your remote control signals (alternatively, you can try to use the lircd.conf below):
# irrecord -d /dev/usb/hiddev0 -H macmini output_conf_file
Start lircd and use irw to check if it works.
Example of an /etc/lirc/lircd.conf:
begin remote
lircd.conf.macbook
pre_data_bits
toggle_bit_mask 0x87EEFD01
begin codes
end remote
First, install the AUR package.
we have to list our partitions. Use
fdisk -l /dev/sda
example output:
# fdisk -l /dev/sda
Linux swap / Solaris
As we see, the "Unknown" partition is our OS X partition, which is located in /dev/sda2.
Create a "mac" folder in /media:
# mkdir /media/mac
Add at the end of /etc/fstab this line:
/media/mac
hfsplus auto,user,rw,exec
Mount it&#160;:
mount /media/mac
and check it:
ls /media/mac
HFS+ partitions, now the default in OS X, are not fully supported by Linux and are mounted as read-only by default. In order to write to an HFS+ partition, the safe way is to disable journaling. This can be accomplished using the OS X Disk Utility. Refer to this
for more information or try to do it from the command line:
Find your partition:
# diskutil list
/dev/disk0
IDENTIFIER
GUID_partition_scheme
Apple_HFS OSX
Apple_HFS Macintosh HD
Apple_Boot Recovery HD
In this example we will use disk0s3 partition named as Macintosh HD. To know if journaling is activate or not you could execute:
# diskutil info /dev/disk0s3 | grep -i journal
File System Personality:
Journaled HFS+
Name (User Visible):
Mac OS Extended (Journaled)
Journal size 49152 KB at offset 0x1176000
As you can read the journaling is active. To turn off the journaling you could execute:
# diskutil disableJournal disk0s3
To verify it is done execute the info command again.
If you get noting as output, then journaling is disabled.
However, if you fail to disable journaling. You can change "auto,user,rw,exec" in /etc/fstab to "auto,user,force,rw,exec" and mount it.
Since Yosemite, HFS+ partitions are now wrapped a CoreStorage volume. Verify that you have an CoreStorage volume.
# fdisk -l /dev/sdX
Disk /dev/sdX: 298.1 GiB,
Units: sectors of 1* 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
EFI System
Apple Core storage
Apple boot
HFS+ uses two volume headers, one 1024 bytes into the device and one 1024 from the end of the device. With the HFS+ partition wrapped in the CoreStorage volume the end of the partition is not actually 1024 bytes from the end of the /dev/sdX2 partition.
To fix this you need to specify sizelimit=X when mounting.
To determine sizelimit do the following:
Run testdisk /dev/sdX and select your drive
Select EFI GPT
Select Analyse and then Quick Search
Sample output:
TestDisk 7.0, Data Recovery Utility, April 2015
Christophe GRENIER &grenier@cgsecurity.org&
Disk /dev/sdX
- 320 GB / 298 GiB - CHS
Size in sectors
EFI System
What you see now is the output of the HFS partition itself without the CoreStorage volume. Take the size in sectors ( in this example) and multiply by the number of bytes in your logical sector size (512 in this example).
Finally, mount your disk with the sizelimit=X option.
mount /dev/sdX -t hfsplus -o ro,sizelimit=
UID Synchronization
Note: It is strongly recommended that UID/GID manipulation be done immediately after a new user account is created, in OS X as well as in Arch Linux.
If you installed OS X from scratch, then this operation is guaranteed to work after logging into your account for the first time.
Pre-Leopard
Open NetInfo Manager located in the /Applications/Utilities folder.
If not done for you already, enable access to user account transactions by clicking on the closed lock at the bottom of the window, and entering your account password, or root password if you have created a root account.
Navigate to /users/&new user name& where &new user name& is the name of the account that will have read/write access to the folder that will be shared with the primary user in Arch.
Change the UID value to 1000 (the value used by default for first user created in Arch).
Also change the GID value to 1000 (the value used by default for user account creation in Arch).
Navigate to /groups/&new user name&, automatically saving the changes you have made so far.
Note: If you get an error message that the transaction is not allowed, log out and log back in.
In Leopard, the NetInfo Manager application is not present. A different set of steps is required for UID synchronization:
Open System Preferences.
Click on Users & Groups.
Unlock the pane if not already done so.
Right-click on the desired user and select Advanced Options.
Write down the value of the User ID field, you will need it later on. Change both the UID and GID to match the UID and GID of the account wished to be shared with in Arch (1000 by default for the first user created in Arch).
Open up Terminal in the /Applications/Utilities folder.
Enter the following command to reclaim the permission settings of your home folder, replacing &your user name&, &your user group& and &your old UID& with the user name whose UID and GID values you just changed, the group name whose GID value you just changed and the old UID number, respectively.
# find /User/&your user name& -user &your old UID& -exec chown &your user name&:&your user group& {} \;
To synchronize your UID in Arch Linux, you are advised to perform this operation while creating a new user account.
It is therefore recommended that you do this as soon as you install Arch Linux.
Now you must substitute Arch's home with OS X's home, by modify entries of /etc/fstab.
If your MacBook spends 30 seconds with "white screen" before booting you need to tell the firmware where is the booting partition.
Boot OS X, if do not have it installed, you can use the install DVD (select language, then click Utilities-&Terminal), or another MacBook with OS X (connect the two computers via firewire or thunderbolt, start the other MacBook keeping pressed T, boot your MacBook keeping pressed Options).
Either way, once you got a OS X terminal running on your MacBook you need to execute, as root, a different command if the boot partition is EFI or it is not:
# bless --device /dev/disk0s1 --setBoot
# if the booting partition is EFI
# bless --device /dev/disk0s1 --setBoot --legacy
# if the booting partition is not EFI
(given that if your GRUB or EFI is on sda1, /dev/disk1s2 if it is on sdb2, etc). See also
The startup chime volume is controlled by the EFI variable SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe. So it can be muted with
# printf "\x07\x00\x00\x00\x00" & /sys/firmware/efi/efivars/SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe
Alternatively, you can use a OS X install disk to mute the chime. Boot from it, select language, then click Utilities & Terminal, and enter
# /usr/sbin/nvram SystemAudioVolume=%01
(or whatever volume you want).
Note: Required formatting of the value provided for key SystemAudioVolume may differ depending on MacBook model and perhaps the version of OS X install media. If the above command fails to work, try enclosing the value in double quotes.
Sometime with the addition of Yosemite, some users found that kworker CPU usage will spike, as disccused . This is sometimes the result of runaway ACPI interrupts.
To check and see, you can count the number of recent ACPI interrupts and see if any of them are out of control.
grep . -r /sys/firmware/acpi/interrupts/
If you see that one particular interrupt is out of control (possibly GPE66), i.e., registering hundreds of thousands of lines, you can try disabling it (replace XX with the runaway interrupt):
echo "disable" & /sys/firmware/acpi/interrupts/gpeXX
Disabling random ACPI interrupts could cause all kinds of problems, so do this at your own risk. If this fixes the problem, there is discussion about how to make a systemd service that automatically disables an interrupt at every boot .
You probably want to have a look at , which is some type of successor of rEFIt.
This is not a requirement.
It only gives you a menu to choose between OS X and Arch Linux upon every boot.
For more see, .
In OS X, download the ".dmg" from
and install it.
Note: If you have already partitioned your hard disk in preparation for the Arch installation, rEFIt may not be enabled by default.
You will have to run the "enable.sh" script installed in /efi/refit/.
Open up Terminal and enter:
./enable.sh
If you experience problems after the install of Arch or rEFIt, especially is the right OS is not showing up to boot to or if it dumps you at a GRUB prompt stuck like the following:
Then have a look at this link:
It can give you a basic idea on how to boot off the Arch live cd, mount the problem Arch install, chroot, use gptsync, and reinstall GRUB. This is probably for more advanced users who can translate the commands from a debian system to an Arch system and also apply it to the partitions on their machine. Be careful not to install GRUB in the wrong spot.
If you need a copy of gptsync you can wget it from here:
or try these, for 64 bit:
and for i386:
since they are .deb packages you will need the program AUR.
For some multi-boot users who utilize a separate Linux boot partition, the OS X Mavericks upgrade may overwrite the boot partition with Apple's own recovery boot filesystem. This breaks the Arch Linux boot option in rEFIt/rEFInd. The best way to proceed in this situation is to abandon a separate boot partition and use the EFI system partition (ESP) to install the bootloader of your choice. It is also recommended that you use rEFInd instead of rEFIt as development on the latter has halted.
Assuming grub2 as the bootloader:
Use the Arch LiveCD to boot to a shell and
to your broken Arch Linux environment.
Mount the ESP on /boot.
Edit the fstab and remove the old boot partition and make ESP the new boot partition. Now mount the ESP as the new /boot parition.
# mount -a
Create a new initramfs and vmlinuz in /boot.
# mkinitcpio -p linux
Install grub.
# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub --recheck --debug
Create a new grub.cfg file.
# grub-mkconfig -o /boot/EFI/grub/grub.cfg
Make sure that grub.cfg is in the same directory as grubx64.efi.
Generate a new refind_linux.conf file in /boot simply by running mkrlconf.sh which comes with rEFInd.
Exit the chroot environment.
Reboot. You should see a new entry for Arch Linux in rEFInd and it should boot to your Arch Linux installation.
Booting from USB via EFI works fine, when giving the intremap=nosid kernel option. (On Ubuntu, also noacpi nomodeset seem to be necessary.) Remember to hold the Alt key on booting to enter the boot menu.
The wireless card works out of the box with brcmfmac.
Suspend / hibernate does not work. The problem seems to be the NVMe that does not wake up. When booting from an external drive, suspend / hibernate works out of the box.
Audio recording works out of the box. Audio playback works, but the built-in speakers don't (no solution yet).
The keyboard and the touchpad do not work out of the box. There is a work-in-progress driver available that works well: AUR. Sometimes the touchpad does not work after booting but this can be fixed by reloading the driver with rmmod applespi && modprobe applespi.
The keyboard backlight does not work (no solution yet).
Note: I used the 201212 ISO image.
Since older Macbooks have a 32bit EFI running, the usual installation image is not recognized. You need to either remove the UEFI support from the disc ([: invalid section]) or build a 32bit EFI version of the disc. The paragraphs below will take the first path to success, booting into BIOS mode and its pitfalls. For a try the other way round, read
First prepare your harddisc according to your wishes. In this scenario it was a "Linux only" approach with
/dev/sda1 HFS+ AF00 200M -& EFI boot system on Apple HFS+ partition
/dev/sda2 ext4 G -& arch system
/dev/sda3 swap 8200 1G
The AUR package contains the tools to handle HFS/HFS+ filesystems. The rEFInd bootloader recognizes it on its own. Usually the partition for the EFI bootloader is a FAT32 (vfat) partition. In this case I tried rEFIt first, which apparently needs the HFS+ filesystem to work, and kept it at that.
The mount points are:
/dev/sda2 -& /
/dev/sda1 -& /boot
The bootloader in use was
instead of rEFIt. To install it, the rEFInd homepage provides a good guide. Usually it is simply done by copying rEFInd:
mkdir /boot/EFI
cp -vr /usr/share/refind/drivers_ia32 /boot/EFI/refind/
cp -vr /usr/share/refind/tools_ia32 /boot/EFI/refind/
cp -vr /usr/share/refind/fonts /boot/EFI/refind/
cp -vr /usr/share/refind/icons /boot/EFI/refind/
cp -v /usr/share/refind/refind_ia32.efi /boot/EFI/refind/
cp -v /usr/share/refind/refind.conf-sample /boot/EFI/refind/refind.conf
cp -v /usr/share/refind/refind_linux.conf-sample /boot/refind_linux.conf
Note: I'm using the 32bit version of Arch and refind, since the EFI of the old MacBooks is 32bit. I'm not sure about 32bit rEFInd booting a 64bit Arch...
The pitfall here is, that the system bootet in BIOS compatibility mode and not in EFI mode. You cannot therefore use efibootmgr, because the EFI variables (even with 'modprobe efivars') are not available. While installing the system get AUR. The hfs-bless utility comes in handy, when blessing the EFI bootloader. This is done by calling:
hfs-bless /boot/EFI/refind/refind_ia32.efi
Since the Linux kernel does come with EFI stub enabled, it seems a good idea to run it through a bootloader first. Especially if it runs not out of the box. But using rEFInd makes GRUB (or any other bootloader) obsolete, because of that.
Note: In the refind_linux.conf you add any kernel option you may want as long as you use the EFI stub of your kernel. In refind.conf you adjust your needs for the bootloader itself, like menu entries. If you use them (menu entries), rEFInd should not look for these EFI stub kernels itself, so blacklist the directories used in here, like /boot/.
Not running out of the box is unfortunately the initial stage for the kernel. Since we installed it in BIOS mode, two modules are missing to grant access to the root partition while booting. Hence the 'initfsram-linux.img' can not be found/loaded. Adding the following modules to your 'MODULES' line in /etc/mkinitcpio.conf solved this ().
/etc/mkinitcpio.conf
MODULES="ahci sd_mod"
Rebuild your kernel image:
mkinitcpio -p linux
The bootloader rEFInd can scan kernels even out of the '/boot/...' directory and assumes an efi kernel even without the extension '.efi'. If you do not want to try out special kernels, this should work without the hassle to copy each kernel after building to some spot special.
If you happen to get multiple entries for one boot image, it often results of a previous installation of a bootloader within the MBR. To remove that, try the following - taken from the . This is valid for GPT partitioned discs, so please check your environment and save your MBR first.
# dd if=/dev/zero of=/dev/sda bs=440 count=1
The brcmfmac driver is working as of , with newer firmware necessary for working 5GHz support ()
On the Macbook Pro 12,1 if the brcmfmac driver can not be started and the following errors occur in the journal:
brcmfmac: brcmf_chip_recognition: chip backplane type 15 is not supported
brcmfmac: brcmf_pcie_probe: failed 14e4:43ba
then check whether
is enabled on the device, and disable it if so.
Bluetooth is fully supported starting from kernel-4.4.0.
The 11,4 and 11,5 MacBook Pros do not shutdown or suspend correctly with the default kernel. This issue is being addressed in
and a temporary patch is currently available in AUR. Note that
has this patch included, and will be released shortly.
Haptic feedback works out of the box due to the trackpad's built-in firmware.
There are several drivers available that provide multitouch support. The following have been confirmed working with the MacBookPro12,1.
the following configuration emulates some features from the OS X functionality. For more options see .
/etc/X11/xorg.conf.d/90-libinput.conf
Section "InputClass"
Identifier "libinput touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "libinput"
Option "NaturalScrolling" "true"
EndSection
the following configuration is necessary to make the touchpad work fully.
/etc/X11/xorg.conf.d/60-magictrackpad.conf
Section "InputClass"
Identifier "Trackpad"
Driver "synaptics"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
EndSection
Further, some US/ANSI keyboards suffer from an issue where the tilde key (~, the key vertically between Esc and Tab) registers as & and &. The following config file fixes this issue.
/etc/modprobe.d/hid_apple.conf
options hid_apple iso_layout=0
for more details and the relevant patches for earlier kernels.
For Intel-only graphics, install the
package. For more information or OpenGL/3D support, follow instructions at .
kernel 4.16.6 dual graphics switching does work on the 11,5 (2015) with Intel modesetting and the AMD GPU utilizing the radeon driver (amdgpu is untested). See
to enable the integrated graphics. Once the laptop boots with integrated graphics enabled you can use VGA Switcheroo controls to power down the discrete GPU. However, if you keep it powered on you will be able to utilize HDMI connections and using AUR you can run applications on the AMD GPU.
Note: The kernel parameters acpi_backlight, i915.lvds_downclock, i915.enable_ips, and intel_iommu are no longer necessary as of kernel 4.2.
Note: (Kernel 4.10.8, MacBook Pro 11,4+) If you experience system lock ups and/or tearing in Xorg, remove the . completely, including any config file you made for it. Xorg will default to its modesetting DDX driver. The performance of this driver is good and the locks go away. See also:
Note: If you are experiencing flickering issues with Xorg, you can set i915.enable_rc6 to 0 parameter into the kernel parameters which will disable to power saving of .
(Late 2013—Mid 2014)
(Mid 2012—Early 2013)
This is almost the same as the 2013 version, where the only known difference is a slightly faster processor. The version numbers have not been changed since the 2013 version.
It works excellently after following the instructions for the MBA 2013 13" here and in the forum thread.
Bluetooth, which has been reported not working for some people with the 2013 version, works without trouble for the 2014 version, although it should be excactly the same.
Unless you have a local repository on a USB disk, you need a USB to ethernet adaptor or a USB wireless adaptor supported natively by the kernel to easily install Arch Linux, since you have to install the
package to make the internal wireless adaptor work.
Unresolved issues:
There is no driver for the webcam yet.
rEFInd uses 30 seconds to start booting. Using the bless trick stops rEFInd from loading, and it has to be re-installed.
Booting from a normal 2013.6 USB key works fine, but I could not seem to get either GRUB or Syslinux working.
I was able to boot by first installing Arch Linux following the MacBook guide at the wiki (having a separate FAT32 /boot partition). Skip the bootloader installation.
Installing
from OS X (important!) and installing the EFI stub loader made me able to boot fine.
Installing
from Linux (or from OS X, but to the esp) also works fine
This method works without rEFInd and uses grub to boot EFI.
Partition as follows:
/dev/sda1 200M Microsoft basic data
/dev/sda2 256M Linux filesystem
/dev/sda3 4G Linux swap
/dev/sda4 108.6G Linux filesystem
sda1 can also be a HFS+ partition for EFI.
This example chooses to use FAT32 (vfat). Although swap is optional, it is required for hibernation. Instead of sda4 for root and home, an alternative partition scheme would be to make sda4 as root and sda5 as home.
Format and mount:
mkfs.vfat -F 32 /dev/sda1
mkfs.ext2 /dev/sda2
mkswap /dev/sda3
swapon /dev/sda3
mkfs.ext4 /dev/sda4
mount /dev/sda4 /mnt
mkdir /mnt/boot
mount/dev/sda2 /mnt/boot
mkdir /mnt/boot/efi
mount /dev/sda1 /mnt/boot/efi
Finish the installation according to the
and skip anything after the bootloader.
After you have generated your initramfs and set root passwd follow below to setup grub:
pacman -S grub efibootmgr
mount -t efivarfs efivarfs /sys/firmware/efi/efivars
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=grub --recheck --debug
grub-mkconfig -o /boot/efi/EFI/grub/grub.cfg
cp /boot/efi/EFI/grub/grub.cfg /boot/grub/grub.cfg
cp /boot/efi/EFI/grub/grubx64.efi /boot/efi/EFI/boot/bootx64.efi}}
Now you can exit/unmount/reboot:
umount -R /mnt
Passing libata.force=1:noncq to the kernel parameters solves the problem.
This is the big worry for me. Every now and then my system hangs for a brief moment and everything involving net or disk access just hangs there for a while and then it seems to work.
So far it only seems to happen when I run something disk- or CPU-intensive. Also had an occassion when I could not start X and just got this repeating all over my screen:
ata1.00: failed command: WRITE FPDMA QUEUED
ata1.00: cmd 61/08:f0:10:8c:c2/00:00:0b:00:00/40 tag 30 ncq 4096 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata1.00: status: { DRDY }
On the next attempt it worked fine.
I did SMART short and long tests on my disk and they returned fine:
There are some messages in my boot that indicate this could be disk and/or ACPI related.
These are with 2013-06 ISO, 3.9.7-1
Seems to only work with the headphone jack, not with the speakers.
Same problem in 2017 with a Macbook Air early 2014. Updating the firmware (via migration to macOS Sierra) solved the issue.
If you have 2013 MacBook Air with a Marvell 128 or 256 GB drive, you mi}