If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Kali-Setup Macbook Pro - missing touchpad and bluetooth

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:

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
Good luck.

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.

here is a link with necessary drivers for MBP 13.3 and 14.3 https://mega.nz/#!jJxWwZaT!QJIqt1rzC...cLiSn_ecQuuwgI
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

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.

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.

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.

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.