Package Base Details: linux-macbook

Git Clone URL: (read-only, click to copy)
Keywords: kernel macbook mbp suspend
Submitter: m3thodic
Maintainer: greg2010
Last Packager: greg2010
Votes: 40
Popularity: 0.80
First Submitted: 2016-07-05 23:22
Last Updated: 2020-05-05 00:12

Latest Comments

« First ‹ Previous ... 7 8 9 10 11 12 13 14 15 16 17 ... Next › Last »

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.

Kisuke-CZE commented on 2017-03-15 17:00

just do
gpg --recv-keys 38DBBDC86092693E
gpg --recv-keys 79BE3E4300411886

Desdic commented on 2017-03-14 20:27

I'm trying to get my suspend to work and noticed this package. But I get

==> Verifying source file signatures with gpg...
linux-4.9.tar ... FAILED (unknown public key 79BE3E4300411886)
patch-4.9.14 ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!
:: failed to verify linux-macbook integrity

when installing .. what do I need ?

Kisuke-CZE commented on 2017-03-13 07:59

Package does not build. Something with "signature failure". Seems hashes of kernel sources has changed. Does it work for you?

deimosfr commented on 2017-02-19 21:39

Hi, thanks a lot for this patched kernel ! That really works better with it :-).

I've another request, it looks like acpi -b can't get battery information with this patched kernel compared to the current one on Arch. Does anyone get an idea on how to get it? May be there's another way to get it?


GuineaPiet commented on 2017-02-19 12:57

Okay posting solution here for the unwary traveler that may come across this thread in search of answers:

Chances are that after installing the linux-macbook kernel from the AUR you may have forgotten to rebuild your grub.efi file that is placed on the hard drive you are booting from. More instructions about this can be found here:

More specifically, the section that says Bootloader configuration and setup

Chances are that this is actually posted somewhere in some document that I am just unable to find. Good luck

GuineaPiet commented on 2017-02-19 10:59

So if I build using makepkg, will the poweroff patches automatically be applied?

GuineaPiet commented on 2017-02-18 08:25

Sorry if I am being an idiot, but for the life of me I cannot find the instructions to get the power off on the Retina Macbook Pro Mid 2015 to work correctly. Can someone point me in the right direction please?

m3thodic commented on 2017-02-11 00:48

Hey everyone -- first off thanks for all the feedback and getting involved, very appreciated!

So I was able to finish updating this port to 4.9 with the necessary patches required. I was able to adjust the brightness, suspend/resume and power-off the machine without any issues. Hopefully these updates help others that had issues with the 4.8 branch!

Thanks again, please report back on any successes or failures.

NOTE: if you were running this kernel since 4.8, you no longer need disable_mode=1 in your boot options.