Last Tuesday, the 6th Aug, Pat (Patrick Volkerding, Slackware's BDFL) released Linux kernel 3.10.5 in the -current tree. Bellow you can read Mr. Pat statement for this move:

Looks like 3.10.x got LTS status, but more importantly fixes the power issue on resume with some Intel machines. So, we're bumping the kernel to 3.10.5, and will stick with that series for the release. A few more things to look at before calling this a beta, but it's pretty close. Enjoy!

-- Patrick Volkerding

Well done, Pat. But the move, at least for me, owner of a MacBook Pro 7,1, was far from what I can name an enjoyable task. Not your fault tough. The one to blame is always those crappy proprietary hardware and its drivers.

NVIDIA and Broadcom drivers, at least as they are distributed at SlackBuilds.org just don't compile under the new 3.10 series kernel. Both is going to miserably fail when you try to compile them either using slackbuild's scripts or straight from the vendors tarballs.

So, let's troubleshoot it.

NVIDIA

NVIDIA was an easy fix. LinuxQuestion's user WhiteWolf1776 reported on a post that "like it was planned, -current moves to 3.10 series and nVidia releases a new driver 325.15." So you can build NVIDIA driver successfully on your brand new 3.10.5 kernel, you can use the slackbuild provided by WhiteWolf1776 or you can just copy (what I've done) your SlackBuild.org's scripts (nvidia-kernel and nvidia-driver), edit .info to change version, download URL's and md5 checksum, edit .SlackBuild to change versions and then build. They are going to build and install with no errors.

Broadcom

Unlike NVIDIA drivers, Broadcom was a pain in the ass. Broadcom is lazy enough to don't upgrade their proprietary Linux drivers since 2011. So, after each major change on kernel's API or some core code used by the WiFi card drivers, good developers out there must do their work and fix that shit on Broadcom's side so it can compile and run on newer Linuxes. Of course that somewhere in the future this trick will not work anymore. But at least for now we, the poor Broadcom enabled hardware owners, are in a safe place! Kudos to the Arch Linux broadcom-wl package maintainer, Krejzi. He managed to patch the driver for that distribution and I've put it together for Slackware.

So, to cut the crap talk out, all you have to do is to clone my GitHub repository for that driver, download the Broadcom's driver tarball from the vendor website in the same directory as the slackbuild lives and run the slackbuild script. It should build with success and place a package ready to install under your /temp. Install it and you should be good to go with no cables.

Now, just as Pat said before, enjoy!