Arch Linux User Repository

@m3thodic yeah i've tried that, but it didn't work. I checked the /boot/grub/grub.cgf and it looks like it is writing to it, but I just can't choose it in the GRUB on boot

@notjacktall after changing /etc/default/grub you have to run the following command as root: grub-mkconfig -o /boot/grub/grub.cfg

@m3thodic for some weird reason I am never able to boot straight into the kernel. I have to manually edit the GRUB every boot. I check my grub.cgf and it seems fine, but it just won't boot or give me the option to boot into the linux-macbook kernel. I change my GRUB_CMDLINE_DEFAULT in /etc/default/grub to BOOT_IMAGE=vmlinuz-linux-macbook, but that doesn't seem to be working.

Many thanks to m3thodic! I'm finally able to work on my mid-2015 mbp with arch linux. Just the wake-up from a suspend status needs a few extra seconds. would be perfect to fix that. not a big problem tho.

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.

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 "After=suspend.target" and "WantedBy=multi-user.target sleep.target". 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 After=suspend.target and WantedBy=multi-user.target sleep.target 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 ----------macbook-wakeup.service--------------- [Unit] Description=Configure device events for linux-macbook ConditionPathExists=/proc/acpi/wakeup After=suspend.target [Service] User=root Type=oneshot 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" TimeoutSec=0 [Install] WantedBy=multi-user.target sleep.target

@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.

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.

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