dunedan / mbp-2016-linux Goto Github PK

Hi everyone!
What commands should be used in the terminal in order to correct the operation of the keyboard and mouse? I do not understand myself.

MacBookPro14,3 , Kali Linux on flash usb (16 gb)

Bit of a weird one here that I haven't been able to reproduce consistently.

On a Macbook 14,3 when using Wayland with libinput handling the Touchpad. I've seen a lock up if I reload my Sway config which re-inits libinput to set device options. I've narrowed it down there because without it being defined in the config file, it seems to not die on reload.

What I see is a lock up of the graphical subsystem. No mouse, no change to the screen, nothing. Hardware power button works and will shut the machine down. Machine is back to normal on reboot. Network is still active during the "lockup" as I can ssh in. I haven't had success killing Wayland yet, when the lock up happens, but that's my next trick.

Happy to help debug in anyway that I can

I played a bit around with power saving on my MacBookPro13,2 and I'm quite puzzled.

I simply tried to reach the lowest possible power consumption as a base line, but weren't able to reach less than ~9W! And that's with display at the lowest brightness level, switched off TouchBar, no external devices, no running applications, all options set suggested by powertop, (no dGPU as the MacBookPro13,2 got none) ...

Apple claims 10 hours of wireless surfing or movie playback with MacOS. As the battery is 49,2Wh that means they get the power consumption down to ~5W with a brighter display backlight and processors doing actual work. So it'd be fair to say they are 50% more efficient than Linux.

What seems to be missing under Linux is power management of the NVMe SSD. At least APST doesn't seem to be supported (at least nvme id-ctrl /dev/nvme0 shows no additional power state beside ps 0 with Linux 4.12rc5). That could be the reason for a few watts of additional power usage, but I doubt it could be responsible for 4W. Anyway I'm pretty sure the SSD supports some kind of power management, so this could be an area to look into further.

What are your experiences? Any ideas where we can get additional savings from?

In readme, it says

Booting
To boot Linux properly, it's necessary to set intremap=nosid as kernel boot parameter.

How can I set the parameter?
Intall a linux on a USB and run it on another computer, then use terminal to set the parameter?

Does any one have the same problem? It's said that bluetooth works out of box on Linux 4.16 or above. I'm on 4.17 and the system seems not detecting the bluetooth hardware, neither rfkill list nor dmesg can find the bluetooth.

MacBookPro14,3
Ubuntu: 18.04
Grub: 2.02

In Grub menu there are missing characters: up-arrow and down-arrow.

This is only cosmetic issue, but might relate #54

I am trying to install Ubuntu on a MBP 13,1. From try ubuntu I can do the NVMe workaround and detect the flash drive. After I install ubuntu on the drive and try to boot up, it gets a dark red screen, I believe it get stuck at the grub and grub cannot recognise the flash drive. My question is how can we do the workaround at this stage? Or what is the correct way to get Ubuntu install?

https://bugzilla.kernel.org/show_bug.cgi?id=193121#c9

The country code X0 is apparently stored in the device itself. Now this country needs to be supported by the firmware we released to linux-firmware and my guess is that it does not.

As far as I see this man has fixed several of these issues already, does someone know if resolving these 13.2 wifi issues is on the horizon as well? Like is there something that could motivate him to do this or is it a gamble?

Hi,

I've put Linux on the 2017 base model of MacBook Pro (13 inch without touch bar). The result of get-info.sh can be found here.

I haven't tested everything yet, but so far the info on your repository appears mostly accurate for my machine. I will let you know when I see any problems.

Thanks @Dunedan @roadrunner2 and @cb22 for your great work!

I'm struggling to get KMS to work on a MBP 13,1.

It boots fine with nomodeset, but without it the screen becomes scrambled. Since there is no dedicated graphics card, I assume the workaround in #6 isn't necessary.

Did anyone get this to work? Or is this a known issue?

When I first installed my MBP mid 2017 touchbar in autumn 2017, the synaptics driver would not work properly and I only could make the touchpad working reasonably well with libinput.

Today I upgraded the notebook to Ubuntu 18.04 and this messed up my xinput configuration. Palm detection, disable-tapping-while-typing, loads of stuff wasn't working any more. After trying to re-configure it for a while I decided to give synaptics another go and it seems to do the job perfectly fine by now. With libinput I could not configure the touchpad in KDE's system settings, this works fine with synaptics now. Also normal pointer speed settings seem to work with it, while with libinput I had to fiddle with the Transformation matrix to achieve a reasonable speed with in turn was breaking some edge panel stuff before.

Hope this information helps people who are struggling with the touchpad.

Hi everyone,

Anyone else having problems with the driver manager?

It shows an update for my Intel(R) Core(TM) i7-7700HQ CPU @ 2.80Ghz
I can do a update, to version 3.20170707.1~ubuntu16.04.0

I update it, and reboot, when i start the driver manager again, it shows the same update.
Because of this i am unable to get into the actual driver manager itself..

Cheers

I frequently see messages like:

[ 1895.960304] CPU7: Core temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.960305] CPU3: Core temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.960308] CPU0: Package temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.960308] CPU4: Package temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.960317] CPU5: Package temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.960318] CPU3: Package temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.960319] CPU6: Package temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.960320] CPU2: Package temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.960325] CPU7: Package temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.960396] CPU1: Package temperature above threshold, cpu clock throttled (total events = 10)
[ 1895.963293] CPU7: Core temperature/speed normal
[ 1895.963293] CPU3: Core temperature/speed normal
[ 1895.963295] CPU3: Package temperature/speed normal
[ 1895.963296] CPU7: Package temperature/speed normal
[ 1895.963336] CPU0: Package temperature/speed normal
[ 1895.963337] CPU1: Package temperature/speed normal
[ 1895.963338] CPU5: Package temperature/speed normal
[ 1895.963338] CPU4: Package temperature/speed normal
[ 1895.963339] CPU6: Package temperature/speed normal
[ 1895.963340] CPU2: Package temperature/speed normal

These messages appear while running almost no workload (browser, slack, maybe one other thing). When I look, I see temps approaching 100C on the CPUs.

Does anyone else have this? Are there tricks for dealing with it? I'm researching the available applesmc options right now, but I haven't had tons of success with that in the past.

Hi!
I bought adapter Jack to USB-C, but it's not working with my Apple headphones. Can anyone tried this case?
lsusb no display anything.

This was an issue on Gnome Shell and any recent kernels.
https://bugs.freedesktop.org/show_bug.cgi?id=98897#c22

Over at cb22/macbook12-spi-driver#64 we're currently collecting the results of info queries from the keyboard, to figure out what two unknown bytes in there mean. So if you have some time to spare, please head over there, gather the data and post it there together with your MBP model and your keyboard layout.

The most likely meaning of these two bytes is the keyboard layout, which would allow automated detection of the keyboard layout by the driver. Another theory is that it could contain a vendor id and product id which would allow automatic enabling of some Apple quirks for the Touchpad. In any case, figuring out what these two bytes mean, will likely result a nice benefit.

I can modprobe appletb and then it is shown by lsmod. dmesg is not showing anything.

sudo mbp-2016-linux/touchbar 1
causes: sending usb-control: Broken pipe

Hello,

I installed Manjaro on my mbp 14,1 and the wifi worked initially for some time but now the 'brcmfmac' module is failing to load for me with the following dmesg error:

brcmfmac: brcmf_chip_recognition: chip backplane type 15 is not supported
brcmfmac: brcmf_pcie_probe: failed 14e4:43a3

I tried installing all possible drivers and solutions for the Broadcom BCM4350 wifi chipset given here:

https://wiki.archlinux.org/index.php/broadcom_wireless
https://bbs.archlinux.org/viewtopic.php?id=216743
https://bbs.archlinux.org/viewtopic.php?id=218310
#10

Surprisingly, when I boot into the manjaro live usb, wifi works fine. But If I reload the 'brcmfmac' module in the live usb, it again gives the above error and wifi stops working.

I have tried the following versions of linux kernel: 4.14, 4.16

Everything else is working great.

Has anyone got the wifi working on mbp 14,1 ? Seems related to #10

It would be great if some note about wifi on mbp 14,1 could be added in the 'Wifi' section of README.md

Sound works over HDMI.

For the builtin speakers and headphone jack some pin configuration quirks seem to be needed, similar to this: https://github.com/torvalds/linux/blob/master/sound/pci/hda/patch_cirrus.c#L462-L467

They can be modified at runtime as described by https://bugzilla.kernel.org/show_bug.cgi?id=110561#c24

Any idea how to find out the needed configuration?

Also, the linked bug report seems to deal with a different model, we should probably open a new bug for the MacBookPro13 line specifically.

According to this commit, the Caps Lock LED should now be working. You may want to upadate README.md

As I want to mimic the same touchpad experience as on macos there probably are a lot of tricks to do so.

What I found so far (I'm under Gnome on Wayland) is that you need to go to the Tweaks section, then Keyboard and Mouse and change the Touchpad click method to fingers.

I haven't solved the occasional "jumps" of the trackpad. I built from source the latest libinput (1.7) but the palm rejection is still not functioning as well as I'd wanted.

Anyone has some tricks/suggestions?

@Dunedan I didn't know any other location to start this issue.

As my 13,1 macbook was getting reallyhot when pushed to the limits and I could hear the fan wasn't revving up like it did under MacOs I installed macfanctld and it's working great.

Should I make a pull request to document this?

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.

Anybody find a solution to the Wifi connectivity issues on MacBook Pro 14.3? Can only connect via Ethernet. Connecting to AP is impossible.

Several months ago I gave up, because this issue made it impossible to work on something without having to worry that suddenly the screen goes down, forcing a hard reset (color of the screen is not always the same)...

I can't seem to find anyone else having this problem.

I have tried with ubuntu 17.10, 17.04, 16.04 and it happens with all of them

the 17.10 i tried yesterday is using kernel 4.12.0
today i used isorespin to put kernel v4.12.12 on ubuntu 16.04
i am about to try debian 9 out of curiosity and have fedora 26 ready too but did not manage to boot the usb stick yet.

right now I got everything working fine (except the stuff that doesn't work yet) with ubuntu 16.04 and kernel v4.12.12 and am trying to figure out why the screen goes kaput sometimes. unfortunately i did not recognize a pattern and can't reproduce.

it seems like it happens faster when i tamper with the display/screen in any way (like turn brightness down, do something in settings>display), but i am not sure. right now it has been running for 30minutes without issues, but i did not turn the brightness down (and am wearing sunglasses instead :-P man, it's so damn bright!). it's a pity because other than that it's really pleasant and running smooth

Does anyone know how i could troubleshoot this?

edit: i got fedora 26 running now and it already happened once...

There seems to be a different wifi card on the macbook13,1:

$ lspci -s 02:00.0 -vnn
02:00.0 Network controller [0280]: Broadcom Limited BCM4350 802.11ac Wireless Network Adapter [14e4:43a3] (rev 05)
        Subsystem: Apple Inc. Device [106b:0159]
        Flags: fast devsel, IRQ 16
        Memory at 92400000 (64-bit, non-prefetchable) [size=32K]
        Memory at 92000000 (64-bit, non-prefetchable) [size=4M]
        Capabilities: <access denied>
        Kernel modules: brcmfmac

I'm running the latest kernel that ships with ArchLinux:

$ uname -r
4.10.10-1-ARCH

The device does not seem to be recognized at all:

$ dmesg | grep brcmfmac:
[    3.774619] brcmfmac: brcmf_chip_recognition: chip backplane type 15 is not supported
[    3.774685] brcmfmac: brcmf_pcie_probe: failed 14e4:43a3

Is there any known workaround for this?

When I switch to Linux, the machine gets quite warm compared to MacOS (mainly left of the touchpad). The temperature reported via sensors is about 58 degrees Celsius. Does anyone else experience this ? Any ideas what to do to fix that ?

• Arch Linux
• MacbookPro13,1
• i3wm

I successfully installed Ubuntu 16.04 on my MBP 13,1 and everything went on smoothly. However, I found that if I closed the lid while Linux is running, and I opened it again, nothing would show up. Completely black screen is the only result. This is quite annoying because every time I need to go somewhere else, I can only shut down Linux completely and start it up again somewhere else. Has anyone met the same problem as I have? Any help will be greatly appreciated. Thanks in advance.

#29 (comment)

Have a tracking bug. ;)

I'm not sure if I am alone here, but I haven't been able to boot my 14,1 with the mainline kernel since a few release candidates ago. I thought it would be somehow fixed by the time the stable kernel was out, but alas, both the latest Fedora rawhide image and the Arch Linux kernel from the staging repository aren't bootable as of today. My machine is stuck at a blank screen at boot, and there are no error messages whatsoever, so there isn't any clue here.

Can one of you MacBookPro13,1 owners please try out, if the webcam works with the bcwc_pcie driver? Should be a low hanging fruit to get some clarity on.

Hi, I'm wondering if anyone finds hotplugging USB devices (e.g. flash drive) kind of hit-or-miss.

Hi,
I have a 2016 Macbook Pro which has been quite stable for a while now. However, I let the power drain completely and now the Ubuntu installation is broken. When I try to recovery mode I see that the message:

suspending console(s) (use no_console_suspend to debug)

I have tried using that flag in grub, but I have been unable to boot the system. Additionally, I have tried nomodeset option as well.
Any ideas/suggestion that you can point me to will be very helpful.

Thanks,
Vik

I just added
sudo iwconfig wlp3s0 txpower 10dBm
and it's working ok now.
Previous value 31dBm
But only 2.4GHz

I'm new to installing Linux on the macbook and was trying to install the rEFInd boot manager. Then I'd like to know what EFI booting procedure is working well for others who are using FV2 from a similar setup. Are people installing linux using rEFInd or another method with FV2?

Regarding rEFInd:

I went through the procedure "rEFInd with SIP Enabled" on a 2016 MBP 13,3 running Sierra, documented here: http://www.rodsbooks.com/refind/sip.html#sip_enabled.

I have to use FV2 encryption on the device, but can disable it temporarily.

Note: This was necessary to see the macOS Volume from the terminal in the recovery in order to install rEFInd.

After restarting I got the rEFInd splash screen. But then after rebooting macOS , I'm prompted to reenable FV2 to login to macOS; due to constraints. After FV2 was re enabled and I rebooted, the rEFInd splash screen went away. I assume that possibly FV2 re-wrote the boot loader.

Then I think I must choose one of the Disabling SIP options.

Do you have any recommendations on which approach(es) to try next? Is it easier to not use rEFInd? Should I try rEFInd with another specific option?

This patch fixed the gmux control of brightness on the MBP 11,5. Maybe this patch is already upstream now? This was a problem on Ubuntu Gnome 16.04/16.10: https://bugzilla.kernel.org/show_bug.cgi?id=105051

I don't know what the state of shutdown is, but the MBP 11,5 has this patch to apply to get suspend to RAM and power off during shutdown working: https://bugzilla.kernel.org/show_bug.cgi?id=103211#c306

Maybe it's a similar problem on the 2016 MBP?

macbookpro 14,3
ubuntu 18.04, linux 4.15.0-20-generic

Plugging in the external GPU results in the following kernel messages:

[Thu May 17 15:09:35 2018] nvidia-nvlink: Nvlink Core is being initialized, major device number 509
[Thu May 17 15:09:35 2018] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:
                           NVRM: BAR1 is 0M @ 0x0 (PCI:0000:0a:00.0)
[Thu May 17 15:09:35 2018] NVRM: The system BIOS may have misconfigured your GPU.
[Thu May 17 15:09:35 2018] nvidia: probe of 0000:0a:00.0 failed with error -1
[Thu May 17 15:09:35 2018] NVRM: The NVIDIA probe routine failed for 1 device(s).
[Thu May 17 15:09:35 2018] NVRM: None of the NVIDIA graphics adapters were initialized!
[Thu May 17 15:09:35 2018] nvidia-nvlink: Unregistered the Nvlink Core, major device number 509
[Thu May 17 15:09:35 2018] thunderbolt 0000:06:00.0: current switch config:
[Thu May 17 15:09:35 2018] thunderbolt 0000:06:00.0:  Switch: 8086:1576 (Revision: 4, TB Version: 2)
[Thu May 17 15:09:35 2018] thunderbolt 0000:06:00.0:   Max Port Number: 11
[Thu May 17 15:09:35 2018] thunderbolt 0000:06:00.0:   Config:
[Thu May 17 15:09:35 2018] thunderbolt 0000:06:00.0:    Upstream Port Number: 1 Depth: 1 Route String: 0x1 Enabled: 1, PlugEventsDelay: 254ms
[Thu May 17 15:09:35 2018] thunderbolt 0000:06:00.0:    unknown1: 0x0 unknown4: 0x0
[Thu May 17 15:09:35 2018] thunderbolt 0000:06:00.0: 1: reading drom (length: 0x5a)
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0: 1: uid: 0x414f41ac904b00
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:  Port 0: 8086:1578 (Revision: 4, TB Version: 1, Type: Port (0x1))
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max hop id (in/out): 7/7
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max counters: 8
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   NFC Credits: 0x800000
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:  Port 1: 8086:1578 (Revision: 4, TB Version: 1, Type: Port (0x1))
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max hop id (in/out): 15/15
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max counters: 16
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   NFC Credits: 0x7800000
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:  Port 2: 8086:1578 (Revision: 4, TB Version: 1, Type: Port (0x1))
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max hop id (in/out): 15/15
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max counters: 16
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   NFC Credits: 0x0
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0: 1:3: disabled by eeprom
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0: 1:4: disabled by eeprom
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0: 1:5: disabled by eeprom
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:  Port 6: 8086:1578 (Revision: 4, TB Version: 1, Type: PCIe (0x100102))
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max hop id (in/out): 8/8
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max counters: 2
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   NFC Credits: 0x800000
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:  Port 7: 8086:1578 (Revision: 4, TB Version: 1, Type: PCIe (0x100101))
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max hop id (in/out): 8/8
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   Max counters: 2
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0:   NFC Credits: 0x800000
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0: 1:8: disabled by eeprom
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0: 1:9: disabled by eeprom
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0: 1:a: disabled by eeprom
[Thu May 17 15:09:36 2018] thunderbolt 0000:06:00.0: 1:b: disabled by eeprom
[Thu May 17 15:09:36 2018] pci_bus 0000:05: Allocating resources
[Thu May 17 15:09:36 2018] pcieport 0000:05:01.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 08-40] add_size 200000 add_align 100000
[Thu May 17 15:09:36 2018] pcieport 0000:05:02.0: bridge window [io  0x1000-0x0fff] to [bus 07] add_size 1000
[Thu May 17 15:09:36 2018] pcieport 0000:05:02.0: bridge window [mem 0x00100000-0x000fffff 64bit pref] to [bus 07] add_size 200000 add_align 100000
[Thu May 17 15:09:36 2018] pcieport 0000:05:01.0: BAR 15: assigned [mem 0xc0200000-0xc03fffff 64bit pref]
[Thu May 17 15:09:36 2018] pcieport 0000:05:02.0: BAR 15: assigned [mem 0xc0400000-0xc05fffff 64bit pref]
[Thu May 17 15:09:36 2018] pcieport 0000:05:02.0: BAR 13: no space for [io  size 0x1000]
[Thu May 17 15:09:36 2018] pcieport 0000:05:02.0: BAR 13: failed to assign [io  size 0x1000]
[Thu May 17 15:09:36 2018] pcieport 0000:05:02.0: BAR 13: no space for [io  size 0x1000]
[Thu May 17 15:09:36 2018] pcieport 0000:05:02.0: BAR 13: failed to assign [io  size 0x1000]
[Thu May 17 15:09:36 2018] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:01.0/0000:08:00.0/0000:09:01.0/0000:0a:00.1/sound/card3/input19
[Thu May 17 15:09:36 2018] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:01.0/0000:08:00.0/0000:09:01.0/0000:0a:00.1/sound/card3/input20
[Thu May 17 15:09:36 2018] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:01.0/0000:08:00.0/0000:09:01.0/0000:0a:00.1/sound/card3/input21
[Thu May 17 15:09:36 2018] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.1/0000:04:00.0/0000:05:01.0/0000:08:00.0/0000:09:01.0/0000:0a:00.1/sound/card3/input22

any ideas where to start?

This might be interesting : http://lukeluo.blogspot.in/2014/04/mac-book-pro-113-linux-customization-2.html

Apple does not "expect" other OS running in rmbp. Its EFI firmware will power down some hardware if it realize you are not booting into OS X. At this time, the Intel Iris GPU won't show up.

Looking into how I can test this. I'm running refind, which directly hooks into the kernel stub loader, and thus doesn't use GRUB.

Not sure if this is relevant. It may be possible to get this script to work with extracting the new firmware from OS X and creating a driver to suit: https://github.com/patjak/bcwc_pcie

Hi, I have been a mac user for a long time and an linux enthusiast maybe long before that. I have tried quite a lot of distros since redhat 6... Unfortunately I never have achieved a pleasant usage of GNU-linux. Always there is something that does not work well (I mean well) not just works...(andf that after countless hours of forum investigating) But anyway I still try... I suppose its a love-hate relation I have with Linux.

Now I have been following this github for some months and finally decided to give a try on my 13.1 with antergos-KDE (kernel 13.x.x). I love how smooth it runs, even streamed videos.

I think I will change to a full Linux experience (single boot) when audio and suspend work.

I, of course, will not ask for a Time Frame but I would like to ask.... Do you think that in the future will be easy to make everything work for us, users? Like follow a tutorial... You know Im not afraid of tinkering but things like compile kernel.... well are a little too much for me and some instructions sound like klingon..
Thanks for your time and efforts.
Keep going!!!!!

Update: BTW If I can be of any help, within my knowledge I would be willing to do so. I enter here almost every day! :D

Hello,
I think this is the best place to share my issue. I've a MacbookPro 13,1.

Some weeks ago, I tried to start a Fedora 25 USB stick (kernel 4.10), no way. I've just tried with Fedora 26 Beta (kernel 4.11) and same problem. I tried with the official Apple USB-C adapter and a Dell A200 as well, no change.

When the mac starts and I press the option key, I see:

• macOS
• Fedora Live
• EFI Boot
• EFI Boot

Both "EFI Boot" and "Fedora Live" start the Fedora Live image. I get to the Fedora Live start menu, I choose "try Fedora", the USB stick blinks for few seconds, and finally, nothing happens. No more blink and blank screen.

As I read you almost successfully run Linux on macs, I guess there is something I do the wrong way. Any help would be great, thanks.

I'm trying to dualboot Arch Linux on my MacBookPro 14,1; but I am completely unable to boot off of any liveUSB devices. When booting the computer with Alt held down I can see the EFI Boot option, but when I select it, it just boots into macOS. Here's what I've tried:

• Arch, Ubuntu, and Gentoo installation images, all of which had the exact same behavior
• USB2.0 and USB3.0 drives, both of which had the same behavior
• Attaching the drive through a dongle or through a dock, which also made no difference
• Creating the drive with Etcher, or manually; both of which yielding the same result
• Disabling secure boot (Utilities menu on the screen that comes up with cmd+R at boot)
• Shaking the computer

Am I missing something? Is there some special step that is required for me to be able to boot the liveUSB?

@roadrunner2 I had a look at the keyboard.conf to see what was loaded, but I couldn't find anything different to load to get the keyboard/touchbar turned on before the encryption key entry stage. It loads fine after I enter the encryption key, so it's a config step somewhere which I'm missing.

Any more tips?

So I was poking around the Bluetooth, and I noticed that the DSDT contains this:

If (!OSDW ())
{
    Return (UBUF) /* \_SB_.PCI0.URT0.BLTH._CRS.UBUF */
}

Return (ABUF) /* \_SB_.PCI0.URT0.BLTH._CRS.ABUF */

This might be a stupid question, but isn't this bit the same as the SPI stuff that used to require patching to get the keyboard and touchpad working?

MacBookPro14,3
Ubuntu: 18.04
Grub: 2.02

In grub menu, press 'e' to edit selected entry.
Help text says that "Press Ctrl-x or F10 to boot". But pressing Ctrl-x produces letter "x". This happens with built-in keyboard and with external usb-keyboard. Ctrl-c is working (and starts command line).
There are no F10 in in-built keyboard, because of touch bar, so this is harmful issue.

I tested ubuntu 18.04 on virtualbox and there ctrl-x is working as expected.

Using a MBP 13.3 for while now but I keep on hitting issues with the keyboard. Initially I thought I just need to get used to this super flat keys but by now I'm not so sure any more and I'd like to ask if you guys here can confirm this:

I use it a lot for development, so I jump around in text files with an IDE a lot, using arrow keys a lot and "fn + arrow" to jump to begin/end etc. For some reason, the arrow keys seem to not react to all presses. I cannot seem to be able to reproduce this by just pressing the arrows repeatedly, but when typing and then switching to the arrow keys they often seem to ignore the first press. It's kinda driving me crazy as I keep on tying in the wrong place.

Anyone here experiencing the same?

Also, let me use the opportunity to thank you for the amazing efforts you've put into this!

Hi,

I just wanted to mention that running a rosnode will force the wifi to stop working after a couple of minutes. MBP 13,1 late 2017
This happens even when the nodes are running on the same machine.

ROS.
Thank you for your efforts!

Best,
Marc

I am using 4.11.7-041107-generic kernel on MacBook Pro 2017 14.3 laptop.
I got the touch bar running and I can adjust the keyboard backlight and sounds, however, I cannot change the screen brightness. I ran the patch mentioned in ReadMe, however, the screen brightness does not work. (Resolved)

Following are the instructions I used:

curl -O https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.11.7.tar.xz
tar xf linux-4.11.7.tar.xz 
curl -o file.patch https://bugzilla.kernel.org/attachment.cgi?id=218051
patch apple-gmux.c < file.patch

patch apple-gmux.c < file.patch
patching file apple-gmux.c
Hunk #1 succeeded at 586 (offset 3 lines).
Hunk #2 succeeded at 596 (offset 3 lines).

make

make -C /lib/modules/4.11.7-041107-generic/build M=/home/chirag/apple-gmux/linux-4.11.7/drivers/platform/x86 modules
make[1]: Entering directory '/usr/src/linux-headers-4.11.7-041107-generic'
CC [M] /home/chirag/apple-gmux/linux-4.11.7/drivers/platform/x86/apple-gmux.o
Building modules, stage 2.
MODPOST 1 modules
CC /home/chirag/apple-gmux/linux-4.11.7/drivers/platform/x86/apple-gmux.mod.o
LD [M] /home/chirag/apple-gmux/linux-4.11.7/drivers/platform/x86/apple-gmux.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.11.7-041107-generic'

targetDir="/lib/modules/$(uname -r)/kernel/drivers/platform/x86"
sudo cp ${targetDir}/apple-gmux.ko ${targetDir}/apple-gmux.ko.backup
sudo cp apple-gmux.ko ${targetDir}
reboot

It worked by using the following commands before copying it to the drivers/platform/x86 directory

rmmod apple-gmux
insmod ./apple-gmux.ko

-Thanks

@Dunedan Just wanted to let you know that I noticed that if I put a hand above the screen (right above the camera) the screen brightness autoadjusts).
At least that's working out of the box.