Closed xinyifly closed 7 years ago
Is it because the Arch Kernel > 4.7 ? DSDT patch not working ? https://github.com/cb22/macbook12-spi-driver/pull/1
I have it working here with Linux 4.10, so the kernel version shouldn't be the issue.
Have you already checked that the modification you did to the DSDT is there after you started up with it being patched?
@Dunedan Thank you for help. I updated the description and checked the DSDT above.
I'm also having this same issue with 4.9.11-1-ARCH. I've patched the DSDT successfully (the override is logged in dmesg) and I've passed intremap=nosid to the kernel. However, I get the same dmesg output as xinyifly and the keyboard does not work.
I'm having the same problem with 4.10.1-1-ARCH.
I was able to fix the issue by compiling the patches DSDT table into the kernel; the dynamic override wouldn't work.
Still not working for me unfortunately... I'm getting the exact same outputs as posted above.
Also make sure you have "intremap=none" but NOT "noapic" as kernel parameters. Noapic will disable spi as a side effect.
THANK YOU!!!! That was exactly the problem, I had the "noapi" kernel parameter. Now it's finally working.
PS you probably meant "intremap=nosid"
... does this mean that keyboard and trackpad can be activated (and everything is working)?
On Mar 17, 2017 6:01 AM, "Raphael" notifications@github.com wrote:
THANK YOU!!!! That was exactly the problem, I had the "noapi" kernel parameter. Now it's finally working.
PS you probably meant "intremap=nosid"
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cb22/macbook12-spi-driver/issues/11#issuecomment-287174393, or mute the thread https://github.com/notifications/unsubscribe-auth/ACkrqBp0Yb7yPaFpVEa4yn0O9F2Ge5l9ks5rmZUKgaJpZM4MTcwx .
I've only been using it for an hour or so but I'm very happy with it, absolutely no complaints so far. Great work @cb22 !! You should put a bitcoin address in the readme for donations, I want to buy you a beer as a token of appreciation :)
EDIT: I gave credit to the wrong user
(FYI the driver was written by @cb22)
Oops you're right. Edited my comment.
Cheers guys! The driver and the noapic
information by @Pamelloes saved my life. @cb22 Should we close this issue now?
PS: An update with README for avoid using noapic
kernel parameter would be helpful :)
Sorry for the off-topic question but did you get suspend/hibernate working on the early 2016 macbook9,1?
No, I've spent a few days trying to get it to work; I've tried all sorts of horrible kernel hacks and have consulted with various channels on Freenode to no avail :( The one bit of progress I did make was setting the kernel parameter no_console_suspend=1 which revealed debug output from during suspend that was lost otherwise: it turns out that the issues is the hard drive doesn't get turned back on after any form of suspend. If you have any suggestions for how to try and fix this, or where a better forum for discussing the issue would be, let me know :)
That's too bad... On the Arch Wiki it says:
Suspend-to-RAM works out of the box.
...under the macbook9,1 model specific information. I guess that's just plain wrong then :(
EDIT: I just changed the wiki to say hibernate / suspend doesn't work.
@carinawi if my stalking is correct, you are the author of the macbook9,1 article of the Arch wiki. Does/did suspend really work for you? Have you done anything to make it work or did it just work out of the box?
PS I tried to send you an email but the email you have on your Github doesn't work.
@xinyifly
Good to hear it's sorted; I'll change the README to make a note about not needing noapic
(intremap=nosid
is what replaces it)
@Pamelloes Yeah, the big problem with suspend / resume is currently the fact that the NVMe device disappeared. I did some digging on that which is documented in #2 - but unfortunately I never got around to testing sending custom opcodes.
In a nutshell, the NVMe device disappears, and refuses to be woken up. It seems like the Apple driver runs some custom commands on suspend / resume to ensure the device is in a usable state.
Funnily enough, that does mean that if you boot off USB, suspend / resume does actually work.
intel-lpss error in dmesg
DSDT Checked
With latest linux 4.9.11-1-ARCH
With linux 4.6.4-1-ARCH
How to confirm spi device?
So I can't get my keyboard work after
make test
with this driverLink to StackExchange
http://unix.stackexchange.com/questions/349259/new-macbook-2016-april-12-inch-keyboard-problem-spi-and-dsdt