Kali-Setup Macbook Pro - missing touchpad and bluetooth

[Edebeton]

Hy @ Ladies & Gents

I am trying to install kali Linux 64 Bit on an Macbook Pro late 2016 following this tutorial "https://docs.kali.org/installation/kali-linux-dual-boot-on-mac-hardware".
The ISO is burned to DVD and booting from the rEFInd installation stated in the above mentioned tutorial. After booting Kali-DVD-Iso it end with Kali/Gnome Graphical User Interface and Kali Wallpaper.

Next step should be resizing OSX partition to maybe 50 GBytes covering the Kali Linux boot partition, but my touchpad is not initialized as well as my bluetooth to pair mouse and additional keyboard. That means no way to get started with gParted.

Besides i have to adjust the screen resolution because of a 50+ grann´s eyes only can read this with magnifying glasses.

It is obvious that these question appears ten times a day so please be so kind and link my to a matching thread where i can find a solution for the following summary:

- adjusting/reducing screen resolution during Kali-Install

- Initializing the Touchpad of the MBP during Kali-Install

- Starting Bluetooth Services to pair Bluetooth Mouse and additional keyboard

Thanks in advance and best regards

Ede

[apothicon]

When installing a new OS on any machine it is good to have wired keyboard and mouse because most of the time you can't install the drivers you need until after installation. My first idea would be to pre-install the drivers necessary by building your own custom Kali ISO with the drivers already on it, for bluetooth and trackpad, mac hardware always gives linux systems a hard time, especially newer mac's. Getting Kali to run correctly on my 2015 Macbook pro was a headache but it is possible.
However this link might be able to help Macbook-Pro-Kali-Mac-OS-Dual-Boot-Install-Guide (https://forums.kali.org/showthread.php?25240-Macbook-Pro-Kali-Mac-OS-Dual-Boot-Install-Guide-amp-WiFi-Guide&highlight=macbook+wifi)
Good luck.

[Edebeton]

Hy @ apothicon...,

thks for Your reply. ;-) Still working on it since 14e4:43xx devices are closed source kali devleoper are acting brave and wise not to offer iso´s out of the box for macintosh devices. Since debian and linux manias are most of the time busy with feeding their hungry homebounds, there seems not enough income left for hardware that is solid like rocks.

In the meantime i did some kungfu with google and found the missing driver and an easy to read explanation on how PCI devices talk to each other @https://wireless.wiki.kernel.org/en/users/Drivers/b43?highlight=%28b43%29#Supported_devices. Now i am going to look for the cruical touchpad driver. With a little patience and luck it might be possible to get it fixed within the next days. May be it ends in building an iso running an MPB established in series 13.x and 14.x stored mega leaving a link down here.

Regards Ede

[Edebeton]

Dear Ladies & Gents...,

here is a link with necessary drivers for MBP 13.3 and 14.3 https://mega.nz/#!jJxWwZaT!QJIqt1rzCr6h4NhclcYTeB0Gi5NEBcLiSn_ecQu uwgI
Here are links with helpfull explainations and how to installhttps://unix.stackexchange.com/questions/175810/how-to-install-broadcom-bcm4360-on-debian-on-macbook-pro

https://wireless.wiki.kernel.org/en/users/Drivers/b43?highlight=%28b43%29#Supported_devices

Broadcom 4360 actually comes with either of two distinct chips, 14E4:4360 and 14E4:43A0. There is no driver in Linux for the first one, while wl is an appropriate driver for the second one. You can determine which one you have by means of the following command:

lspci -vnn | grep -i net

There is no support for Broadcom 4360 14E4:4360 on Linux. The definitive guide in these matters is Linux Wireless, which gives in this table the list of all Broadcomm wireless chips, and the available Linux drivers. As you can see, no driver is listed under BCM4360 14E4:4360.

[/URL]



PCI-ID Supported? Chip ID Modes PHY version Alternative
14e4:0576 not tested BCM43224 a/b/g/n ? wl/brcm80211
14e4:4301 yes (b43legacy) BCM4301 b B
14e4:4306 yes (b43legacy) BCM4306/2 b/g G
14e4:4307 yes BCM4306/3 b/g G
14e4:4311 yes BCM4311 b/g G wl
14e4:4312 yes BCM4311 a/b/g G (r8) wl
14e4:4313 not tested BCM4311 a ? wl
no BCM4313 b/g/n LCN (r1) wl/brcm80211
14e4:4315 yes BCM4312 b/g LP (r1) wl
14e4:4318 yes BCM4318 b/g G (r7)
14e4:4319 yes BCM4318 a/b/g G
14e4:4320 yes (b43legacy) BCM4306/2 b/g G (r1)
yes BCM4306/3 ? G (r2)
14e4:4321 partially BCM4321 ? N (r2)
14e4:4322 yes (3.18+) BCM4322 b/g/n N (r4) wl
14e4:4324 yes (b43legacy) BCM4306 a/b/g G (r1)
yes BCM4306/3 a/b/g G (r5)
14e4:4325 yes (b43legacy) BCM4306/2 b/g G (r1)
14e4:4328 partially BCM4321 a/b/g/n N (r2) wl
14e4:4329 partially BCM4321 b/g/n N (r1) wl
14e4:432a not tested BCM4321 a/n N wl
14e4:432b partially BCM4322 a/b/g/n N (r4) wl
14e4:432c yes BCM4322 b/g/n N wl
14e4:432d not tested BCM4322 a/n N wl
14e4:4331 yes (3.2-rc3+) BCM4331 a/b/g/n HT (r1) wl
14e4:4350 yes (3.8+) BCM43222 a/b/g/n N (r6)
14e4:4353 yes (3.1+) BCM43224 a/b/g/n N (r6) wl/brcm80211
14e4:4357 yes (3.1+) BCM43225 b/g/n N (r6) wl/brcm80211
14e4:4358 yes (3.17+) BCM43227 b/g/n N (r16) wl
14e4:4359 yes (3.17+) BCM43228 a/b/g/n N (r16) wl
14e4:4360 no BCM4360 ? AC (r1)
14e4:4365 no BCM43142 b/g/n LCN40 (r3) wl
14e4:43a0 no BCM4360 a/b/g/n/ac AC? wl
no BCM4352 a/b/g/n/ac ? wl
14e4:43a9 yes (3.17+) BCM43217 b/g/n N (r17)
14e4:43aa yes (3.17+) BCM43131 b/g/n N (r17)
14e4:43b1 no BCM4352 a/b/g/n/ac AC (r3) wl
14e4:4727 no BCM4313 b/g/n LCN (r1) wl/brcm80211
14e4:a8d6 not tested BCM43222 ? N (6)
14e4:a8d8 yes (3.6+) BCM43224 a/b/g/n N (r6) brcm80211
yes (3.6+) BCM43225 ? N (r6) brcm80211
14e4:a8db partially (3.18+) BCM43217 b/g/n N (r17)
14e4:a99d not tested BCM43421? ? ? wl



Two lines below in the same table, it is shown that the other chip with which 4360 is produced, 14E4:43A0, is instead supported by the proprietary driver wl. The correct procedure to install this driver is described here, in the Debian Wiki. For Wheezy, you should add this line.

deb http://http.debian.net/debian/ (https://wireless.wiki.kernel.org/en/users/Drivers/b43?highlight=%28b43%29#Supported_devices) wheezy main contrib non-free


Known problems & limitations

Some stalls (on G-PHY only?) possibly related to CCK vs. OFDM, see WRT54g / b43 / mac802.11 BREAKTHROUGH
N-PHY: 5 GHz support requires kernel 3.17+
HT-PHY: [U]no support for 5 GHz
No support for 802.11n features (HT, aggregation, 40 MHz width)

In case of questions just drop me a E-Mail.

Best Regards

Ede

[Edebeton]

Hey @ All

Just to continue answering the the questions in Post #1, here is a some helpful hints to initialize the cruical touch-pad and keyboard on
Apple`s new Macbook Pro series 13. 3 and 14.3 establishedEntefr late 2016 to 2017.

Just read and study following Link: https://github.com/roadrunner2/macbook12-spi-driver

Enter following lines in a terminal:

- "echo -e "\n# applespi\napplespi\nspi_pxa2xx_platform\nintel_lps s_pci" >> /etc/initramfs-tools/modules"

- "apt install dkms"

- "git clone https://github.com/cb22/macbook12-spi-driver.git /usr/src/applespi-0.1"

- "dkms install -m applespi -v 0.1"

Reboot MBP and following features should work:


- Basic Typing
- FN keys
- Driver unloading (no more hanging)
- Basic touchpad functionality (even right click, handled by libinput)
- MT touchpad functionality (two finger scroll, probably others)
- Interrupts!
- Suspend / resume

The timeouts till the touchbar is dimmed and turned off can be changed via the idle_timeout and dim_timeout module params or sysfs attributes (/sys/class/input/input9/device/...); they default to 3min and 2.5min, respectively. See also modinfo appletb.

Best regards Ede