Package Base Details: linux-macbook

Git Clone URL: (read-only)
Submitter: m3thodic
Maintainer: annguyenfoss
Last Packager: annguyenfoss
Votes: 35
Popularity: 2.029008
First Submitted: 2016-07-05 23:22
Last Updated: 2019-05-29 03:29

Pinned Comments

annguyenfoss commented on 2019-05-29 03:33

Built and tested 5.1.5.arch1-1. Released. However, there are differences between this build's config and official kernel build's. I'll review and address those differences in next builds.

Latest Comments

« First ‹ Previous ... 3 4 5 6 7 8 9 10 11 12 13 ... Next › Last »

m3thodic commented on 2017-05-26 18:36

Thanks @jdz1214 if the updated wake-from-sleep is working for you I will commit the changes. I had issues with systemd and target=multi-user regarding cyclical dependencies or something along those lines but maybe this has been fixed.

Also to everyone, working on syncing linux-macbook with the latest Arch kernel release. Should have something posted in a few hours or so.

jdz1214 commented on 2017-05-05 13:15

I created a fix to the intermittent wake-from-sleep issue by adding two lines to the macbook-wakeup.service file. The complete file is below. The modified lines are "" and "". The modifications cause the service to run whenever the computer wakes from sleep (in addition to running at boot). My mac likes to re-enable some acpi wakeups when it has gone to sleep, so running the service upon waking reverses any unwanted enabling.

Steps to modify:
1) sudo nano /usr/lib/systemd/system/macbook-wakeup.service
2) add and as shown below
3) ctrl + o followed by Enter to save, ctrl + x to exit nano.
4) sudo systemctl disable macbook-wakeup.service
5) sudo systemctl enable macbook-wakeup.service
6) sudo systemctl start macbook-wakeup.service


Description=Configure device events for linux-macbook

ExecStart=/bin/sh -c "awk '$1 !~ /^LID/ && $3 ~ /enabled/ {print $1}' /proc/acpi/wakeup | xargs -I{} echo '{}' > /proc/acpi/wakeup"
ExecStart=/bin/sh -c "awk '$1 ~ /^LID/ && $3 ~ /disabled/ {print $1}' /proc/acpi/wakeup | xargs -I{} echo '{}' > /proc/acpi/wakeup"


m3thodic commented on 2017-04-18 00:55

@Synthead I'll have to look at PKGBUILDS for other kernels. I have no problem adding provides=() where it makes sense (ala linux-ck), I just don't know what (if any) repercussions providing the default linux kernel will have.

Synthead commented on 2017-04-17 20:13

Could you add provides=() to the packages in this PKGBUILD? I.e. linux-macbook would have provides=(linux), etc. This should allow other packages to use this -macbook flavored kernel as a substitute to the upstream Arch kernel. Without this, linux, linux-headers, etc. still need to be installed, but the kernel is not used.

jimnutt commented on 2017-04-17 19:45

Boot up problem was due to reFind using the wrong initrd. Fixing the reFind configuration solves the problem.

jimnutt commented on 2017-04-17 15:52


I'm not using grub at all, booting directly from reFind. I'll try adding splash to the kernel arguments and see what happens. I've tried running mkinitcpio by hand a few times to no avail. I'll give this newer version a shot.

Tom_B commented on 2017-04-10 19:47

Hi I'm getting odd issues with this new version.

Occasionally suspend will work, other times it will come back on after ~90 seconds. After sudo systemctl suspend it turns back on. I'm not sure why as it was working prior to 4.10.

enrique commented on 2017-04-08 14:34


This kernel fixed poweroff and suspend on my MacBookPro11,4, thanks!

m3thodic commented on 2017-04-04 00:38

@jimnutt which version were you attempting to boot? Your hooks appear correct, I'm going to venture a guess and say something isn't synced properly on your host.

Try running `mkinitcpio -p linux-macbook` manually, and also in /etc/default/grub add the boot argument "splash" after "quiet" to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and then run `grub-mkconfig -o /boot/grub/grub.cfg`.

I had some weird issues regarding EFI and being able to properly boot a 4.10 kernel when upgrading from 4.9 and adding that splash boot argument fixed both my macbook and a custom-built PC. I tried asking about it in the arch forums but some forum crank admin moved it to the Newbie Corner.

jimnutt commented on 2017-04-03 16:47

I'm having trouble with this booting from LVM2. It waits the 10 seconds for the LVM devices, then drops into an emergency shell. Unfortunately, there doesn't appear to be any keyboard drivers or something, as I can't actually do anything in the emergency shell (no keystrokes appear [from either keyboard, laptop or USB] and no commands will execute). I have the following HOOKS set in mkinitcpio.conf: HOOKS="base udev autodetect keyboard modconf block lvm2 filesystems fsck"

Any suggestions would be appreciated. I can fall back to the regular kernel, which works just fine, it's something to do with the macbook specific kernel.