-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MacBookPro 15,1/2? #71
Comments
Is the keyboard and touchbar (using the drivers at my clone of macbook12-spi-driver) working for you? I've had reports so far that at least the keyboard doesn't. Assuming that's true, help would be appreciated in trying to debug the issue (and in which case please open an issue for this specifically). |
So I went ahead and custom built a Arch Linux live image with @roadrunner2's driver. (Archiso releng profile + macbook12-spi-driver-dkms from AUR) While the driver successfully loads, the keyboard fails to function and the touchbar remains blank. EDIT: |
You're the first person here who got one, so you might be the one being able to provide information. 😄 As there are some significant differences compared to the previous models, mainly due to the introduction of Apple's T2-chip, I suspect fewer components will work for now. As a start a PR with the output of the get-info.sh script would be really good. And you can of course follow the instructions for the 2016/2017 models and have a look which components work and which don't. For example I expect that Linux won't have access to the sensors previously exposed by the system management controller (SMC), as that's now handled by the T2-chip. Same for access to the disk via NVMe. While I expect that this works, it might require a kernel patch as did the controller for the 2016 and 2017 models. But as said: a PR with the information from the |
Well the SSD doesn't work at all, same with WIFI, looks like a new chip BCM4464 (nothing on google.) I also attempted manually specifying the SSD PCI ID (106B:2005 - ANS2 NVME Controller) with the following,
after which Not sure what went wrong, prob the T2 crashed or smth? I did receive a crash report after booting macOS with BridgeOS reporting a recoverable ANS2 failure. FYI, sending in a PR with the info from |
Lots of interesting bits in the dumps. The obvious ones:
|
@Dunedan Would a dump from |
Sure. More information is always good. 😄 |
Pastebin was complaining about file size so I just uploaded to here. (2.7 MB) Of particular interest are the following,
It seems that Apple is emulating a HCI controller through the IOBC to interface with the iBridge devices as USB, as evidenced by the recurring |
The biggest problem on my 15,1 is applesmc module, it refused to load with these messages:
without applesmc, it's always very hot. My kernel is
I haven't tried to get keyboard/touchpad to work. I'd like to provide any information needed. edit: |
Have you tried to turn off secure boot? https://support.apple.com/en-us/HT208330 |
@mikeeq Yes, thats the only way I was able to boot the device. |
@wsy2220 Do you have FileVault enabled? If not it me be worthwhile to test the following commands I used to recognize the NVMe drive:
I have a hunch that with FileVault disabled it won't spontaneously crash like it did in my situation. |
@aunali1 I have no FileVault. I tried those commands, and nvme device didn't show up, and the system got reset after about 10s. |
Regarding the keyboard, looking at the provided pci listing and dsdt, I see two things:
Looking at the ioreg info is more informative: it appears it's back on the USB bus, and hanging off the Bridge-Controller/T2-chip. But since it doesn't show up in |
Did someone have any success with the nvme of the MacBook Pro 2018? I have the same problems as other people described earlier (keyboard and trackpad not working and nvme not visible). The not working keyboard and trackpad doesn't bother me that much as I'm anyway using an external keyboard and mouse most of the time. The not recognized nvme however bother me quite a lot. |
@wsy2220 I don't expect @AndreasAZiegler The NVMe controller isn't recognized by default, because Apple screwed up and put a typo in the class code for the NVMe controller. So to get it automatically detected a patch for the Linux kernel is necessary (e.g. check out the patch I submitted for the MacBook Pro 2016: http://lists.infradead.org/pipermail/linux-nvme/2017-February/008323.html). Without the patch, you can manually discover the NVMe controller with the following commands (as already mentioned in the thread by @aunali1):
The problem then seems to be that this is causing system resets soon after as mentioned above as well.
@aunali1 Any chance you (or somebody else) can provide such a crash report? Maybe it contains some useful information. Updating to the latest macOS version could also fix the system reset, if it was caused by a bug in BridgeOS (not likely, but worth a shot). |
Hello all, I recently received this model of macbook pro, but it looks like unfortunately Linux is crippled on it. I would have liked to boot off an external drive, but if I understand correctly, the keyboard and trackpad don't work, and even worse, audio and wifi don't work at all. I suppose that brightness controls also don't work then? Has any headway been made towards making Linux usable on these machines? |
@KTRosenberg This entire Github project is designed to help you make it work on these laptops. I use it daily on a 14,3. There are compromises, but it's very useable. |
Could somebody provide the output from @Dunedan Might I suggest changing the |
@jboyens I see. But just to confirm--is it true that the wifi and audio are still unusuable beyond connecting external adapters and audio interfaces? |
@KTRosenberg it depends on the model. But yes, audio and WiFi are not working consistently without some compromises. I use a small WiFi dongle and USB headphones. |
I was referring to the 2018 model, which seems to be less functional than the previous models due to the T2 chip-related changes. |
@roadrunner2 Sure. Free free to open a PR and add what you think would be beneficial as well. |
While trying around with the latest Arch Linux installer (2018.10) and the current Ubuntu Live System, I made the following observations. When I run in the Ubuntu Live system sometimes the nvme drive appears and sometimes it doesn't. In both cases the system resets after around 10s as desribed by @wsy2220. In the Arch Linux installer neither does the drive appear nor does the system resets. Does anyone has some more success yet? |
@roadrunner2 I'll spin up a new Arch image and test out the command. |
@Dunedan I posted the dump of the report from macOS here https://pastebin.com/UtvGz403 (I hope that's right). Just for clarification how this report was generated: I booted from the Ubuntu Live USB stick, modified the nvme driver, recompiled the driver, loaded the driver "modprobe nvme", then my laptop crashed after around 10s, in macOS the aforementioned report was presented to me. |
Regarding the NVME related resets, there's this hack in the linux driver ( /*
* Temporary fix for the Apple controller found in the MacBook8,1 and
* some MacBook7,1 to avoid controller resets and data loss.
*/
if (pdev->vendor == PCI_VENDOR_ID_APPLE && pdev->device == 0x2001) {
dev->q_depth = 2;
dev_warn(dev->ctrl.device, "detected Apple NVMe controller, "
"set queue depth=%u to work around controller resets\n",
dev->q_depth); Might be worth seeing if this is also needed for the new controller. |
Here is my acpidump on 15,1: |
Unfortunately pacman gives me download errors from your repo (I think this is back: aunali1/linux-mbp-arch#2 ) and I have just been manually grabbing the files with wget as I can increase the retries. I didn't think to keep them after installing them though. |
@TRPB Odd, I'll look into that. Regarding previous releases, everything is mirrored on the github repo's releases so you can pull previous versions from there. |
@MCMrARM Not sure if I am late, but I highly doubt SMC is emulated inside the T2 bridgeOS portion (with some kext and userland applications) instead of SEP. |
@imbushuo it's in the SEP |
Fixed the 5.4.15 compat issue in the BCE driver, apparently I misunderstood what address_device is for and after they fixed the new_scheme formula it broke my driver as it stubbed it. |
Hi, thanks for the great work done here, I can now install arch on my mba2019. Not working now: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Any clue about this issue? Is the T2 implementation different on mba vs mbp? |
Hi all, sorry for barging in. This is some amazing work, congratulations! I see there's an Arch distro available with the updated kernel but I really need to use Ubuntu 16.04. How would I implement your solution with Ubuntu? Does anyone already have this distro running with the updated kernel? I have a MacBook Pro 15,2. Thank you! |
Hi,
To be continued, thanks again everyone for these amazing results |
Hi, |
Any news on Touch bar support for MacbookPro15,2 (MacbookPro 13" from 2018/2019)? I've made almost everything to work, including keyboard, sensors, sound and WiFi with the kernel patches from https://github.com/aunali1/linux-mbp-arch and the BCE driver from (https://github.com/MCMrARM/mbp2018-bridge-drv. I've tried, though, to use the SPI driver specifically for the touchbar. The modules compile and load fine, but nothing happens. I'd like to support this. Currently I don't have much time to code, but I can test and provide logs, system info collected from lshw, lsusb, dmesg, etc. and of course do some local compilations and test or make minor code adjustments. |
Can i ask you how you used the patches from linux-mbp-arch? I have a Macbook15,1 and I manage to make keyboard, touchbar, touchpad work, but with wifi I get nothing. In the settings on Wifi I get "No WiFi adapter found". I'm on Ubuntu 18.04 with kernel 5.3.0. I've tried 5.4.0 but was really bad, nothing worked. |
@MultiGiachi Actually, I created some scripts to make the installation process of the driver files in Linux more convenient. Original answerYou need the wifi driver files from your MacOS.
The wifi device name might differ on your Macbook, as I'm using MacbookPro15,2.
The files listed in the output must be renamed accordingly and copied to |
@stefanpartheym |
@MultiGiachi |
any support for an iMac Pro? or suggestions as to mods that would allow me to install linux on the internal SSD and boot from it? so far everything just hangs, even though I've disabled secure boot and system integrity protection. can't get past the EFI / boot selection - once chosen, only darkness. |
@stefanpartheym |
Hi @Skurrrr , |
Hey, |
@MultiGiachi @stefanpartheym
important are |
Hey @zfortier |
@zfortier : I made the changes and it seems to work fine. Can't say for sure wifi will be less flaky now. I think have to observe this for some days. But thanks for your help! |
I am on the MacBookPro15,1. I attempted the b3 (4464) driver on the custom t2 linux iso. Copy it over from the ISO to the disk you install arch on. Wifi will work afterwards. I hope this helps! |
T2 chip controls the SMC on a macbook pro you can patch kernel but it wont work properly so to get full support on this you would need to create drivers by dump the T2 chip and smc i have done this with script many years ago i tried agian making drivers for touch id and stuff to work proeprly in bottcamp in windows i got bored with it and gave i can try and find this script and upload here if you guys need it |
Isn't there any possibility of getting a driver from the OpenCoreLegacyPatcher? |
Any support/documentation for the refreshed 2018 MacBook Pros?
I have one and I'll be willing to help with tinkering stuff especially since they are using the new T2 chips.
The text was updated successfully, but these errors were encountered: