Package Base Details: linux-macbook

Git Clone URL: https://aur.archlinux.org/linux-macbook.git (read-only, click to copy)
Keywords: kernel macbook mbp suspend
Submitter: m3thodic
Maintainer: greg2010
Last Packager: greg2010
Votes: 45
Popularity: 0.000000
First Submitted: 2016-07-05 23:22 (UTC)
Last Updated: 2020-11-19 06:48 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 23 Next › Last »

jimnutt commented on 2017-04-17 15:52 (UTC)

@m3thodic 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 (UTC)

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 (UTC)

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

m3thodic commented on 2017-04-04 00:38 (UTC)

@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 (UTC)

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 (UTC)

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

Desdic commented on 2017-03-14 20:27 (UTC)

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 (UTC)

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 (UTC)

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? Thanks

GuineaPiet commented on 2017-02-19 12:57 (UTC)

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: http://zanshin.net/2015/02/05/arch-linux-on-a-macbook-pro-part-3-base-installation/ 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