I recommend using the SlackBuild script to install this driver to a manageable directory.

There are several open source drivers that are used to drive Broadcom 802.11 chips such as b43 and ssb. They will conflict with this driver and need to be uninstalled before this driver can be installed. Any previous revisions of the wl driver also need to be removed.

The ssb driver must be removed (by hand or script) before wl is loaded. The wl driver will not function
...

Honestly as a Slackware user I'm very well skilled in this trait and can easily manage my own system, but what about automated package management distributions? Sure you can have a system hold your hand and walk you through in baby steps, but what about that rare case when a dependency is not resolved by the package management system because the package is obscure enough not to have a mainstream dependency file? What then? Honestly, I have ran across some of these. I've had to often do hour long...

I've been using Linux on and off for the past ten years or so and at first, even I was very intimidated by the OS. It took a lot of researching and also a lot of trial and error before I settled in on my current distribution, Slackware. I've had the opportunity and unfortunate privilege of trying out other distributions that were more or less a migraine. Red Hat, Mandrake, SuSE, Ubuntu, and a few others I've forgotten over the years.

As a user of Linux I've been ridiculed in college...