Package Details: linux-macbook 5.1.5.arch1-1

Git Clone URL: https://aur.archlinux.org/linux-macbook.git (read-only)
Package Base: linux-macbook
Description: The Linux-macbook kernel and modules
Upstream URL: https://git.archlinux.org/linux.git/log/?h=v5.1.5-arch1
Licenses: GPL2
Submitter: m3thodic
Maintainer: annguyenfoss
Last Packager: annguyenfoss
Votes: 35
Popularity: 1.714619
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

1 2 3 4 5 6 ... Next › Last »

annguyenfoss commented on 2019-06-24 11:29

@hcl31415: Ah nevermind, it was a mistake of my part during the build. I removed that comment of mine immediately before releasing 5.1.5.arch1-1 build.

@jketcham: As above.

@dilyn: I'm setting up a new build server with Jenkins. Stay tuned.

dilyn commented on 2019-06-19 22:01

Been a longtime user of this kernel and noticed it recently changed hands; wondering if there's anything I can do to help the process of keeping this up to date?

jketcham commented on 2019-06-16 08:21

I'm seeing the same error and typo as @hcl31415, that patch would be appreciated. I'm new to contributing to AUR packages; I see the read-only git url, how would one submit the patch themselves?

And in case anyone is curious, this is the message that is trying to be printed:

    To get suspend working properly you must do the following:

    Enable the macbook-wakeup service for suspend/resume on LID events:
    systemctl enable --now macbook-wakeup.service

    Optionally, include the kernel boot option processor.ignore_ppc=1
    to allow frequency changing on battery power.

hcl31415 commented on 2019-05-29 09:20

@anngyenfoss: As far as I know since considerable time, when installing the package an error message occurs because of a spelling error in a function name. Could you maybe include the following diff:

diff --git a/linux.install b/linux.install index ab733fb..dc80fa2 100644 --- a/linux.install +++ b/linux.install @@ -1,4 +1,4 @@ -display_display_message () { +display_message () {

Sorry for the styling... I am new to this.

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.

saulocastelo commented on 2019-05-20 02:34

Hi ...

I can run the tests on my MacbookPro retina 11,1 for us before you launch

If one owner of each Macbook(Pro) version do this will you be able to continue this amazing project?

We could create an repo exclusive for the tests and I'm able to maintain this for some time on my server (Google Cloud)

Big thank you for all your work

annguyenfoss commented on 2019-05-10 04:44

Built and tested 5.0.13.arch1-1. Released.

m3thodic commented on 2019-05-07 19:36

@annguyenfoss Thank you for the thank you's, greatly appreciated!

Most of the patches came from mailing lists -- I wanna say they were titled something like Macbook RFC that had 3 different versions I had to port to newer kernels but nothing super heavy handed. It mostly had to do with using the same code just having to massage it a bit for when newer releases added things that screwed up the line number(s) relating to the patches.

Sorry for orphaning this, but at the end of the day I don't have any way of doing any sort of quality control/assurance since the place I work for has moved from Macbook's to Dell XPS hardware. I'm still subscribed to receiving alerts to this package so I'll continue to keep an eye out in case anyone gets stuck, but of course ultimately I'd like to see the mainline kernel codebase Just Work(tm) with Apple hardware.

annguyenfoss commented on 2019-05-06 06:29

@m3thodic Thanks a lot! I've built every single version of this kernel in the last 3+ years. It has been really helpful for me all these years.

Now, I'm a python dev and my C/C++/makefile writing are quite rustee. Is it very difficult from a programming perspective to maintain this build? Did you have to write the patch yourself and fix bug/improve the patch's codes all these years while maintaining this package?

I'm trying to figure out what would be required if I'm to adopt this package.

Thanks!

m3thodic commented on 2019-05-05 22:36

@annguyenfoss Yeah I orphaned it, I haven't had a macbook in almost 2 years now I've just been maintaining it without really being able to test new releases.