You just said firmware can't be removed. So can I just removepkg? Edit: That was stupid, I meant to say remove package with sbopkg? Which I did just now.

Ticked the "create usb boot disk" option. I've been looking at trying to reinstall it but I have more experience with grub and don't want to wind up having to just reinstall everything. Well, actually, at this point that may be a more preferred route; start from a clean slate and such.

Figured a new comment was required for this:

I removed, patched, built, and installed it again. Rebooted per the post you linked, logged back in, ran modprobe wl but still receive
What does this mean? What do I have to do now?

New update

I wound up installing broadcom-sta from slackbuild on a clean slackware 14 install, patched it with the included patch, now when I try to modprobe wl it kicks back the following:

I still have no idea what this means.

As I said earlier you seem to be confused about the wl driver and the firmware. From your earlier post, it seemed like you didn't use the slackbuild to install the firmware, but built b43-fwcutter and extracted it manually.

grub is in /extra on the Slackware installation media. If you're happier with grub, just remove lilo and install it.
If the kernel module is still unusable, even after this:

Clean installing Slackware would have made no difference, this is not windows.

At this point your best bet is to build a newer kernel and try b43 + the firmware.

It means that the kernel is refusing to load the module. It's an upstream problem. If the suggested patches don't help, I'm out of ideas on that one.

Actually, yes, I was confused. I was thinking of wl driver as firmware and that was my stumbling block. Sorry. I did build the b43-fwcutter manually. Should I use the slackbuild after upgrading the kernel, or would it matter either way?

IIRC the version included is grub 0.97, I was planning on install grub 2 later on. Thanks though!
Ah, well ok thanks for clearing up the error at least. I was thinking the module had a messed up line in the coding or the call for it was wonky or something, wasn't sure.

True, very very true. I needed to fix my partitions and table anyway, and once I finished with the install the system is actually running a bit smother. I think I botched something during install the first time. I'm going to build a newer kernel and update the thread when I go through that.

Thanks for the patience while I'm still learning

There is a slackbuild for b43-fwcutter and another for the firmware. If you install via the slackbuild, it's simpler and slackware packages are created.
Then try grub2 from slackbuilds or just stick with lilo.
Usually if there is typo or syntax error in the source itself, it won't build.

Sorry this took so long, I got tied up with a few things. So, I fixed up the new kernel, currently using 3.10.12, I have b43 installed and all that. I can now connect, but only to 2.4ghz. Device still isn't showing 5ghz range. Is there something else that I missed or that needs to take place?

You might try this:

http://crunchbang.org/forums/viewtopic.php?id=17368

Tried it, quality of connection didn't seem to change (still slow as molasses), and the 5ghz band is still no where to be found.

Update:
Internet speed seems to be fluctuant. At times it is normal speed, at others it is slow as molasses in Canada in January (yay analogies!). This doesn't seem to be caused by the network or network instability. The device itself seems to be unpredictable. I'm not sure how I would test this with 100% certainty.

5Ghz range still unavailable. Not sure why. The wifi pcmcia adapter worked fine with the b43 firmware under debian.

This site might be useful:

http://wireless.kernel.org/en/users/Drivers/b43

You might send a question to the b43 mailing list as well?

http://lists.infradead.org/mailman/listinfo/b43-dev

First link - tried earlier in the thread.

Second link - I will do that. I didn't realize there was a mailing list. [Edit] The mailing list didn't accept an email from any email address I tried

Could you please tell us which Debian version and which kernel you used? That would allow us to compare drivers and firmware. If possible, exact names of packages used would help.

Also, did you install firmware in Slackware using packages built using the SlackBuilds available @ http://slackbuilds.irg? In that case, did you build and install first b43-fw-cutter? Then did you build and install b43-firmware or b43-legacy-firmware?

Ran under 6.0.7, which ever kernel version was default. Quick google search tells me it was 2.6.32.

Slackbuilds has a couple different tools that act as package managers for downloading from the site. I used sbopkg, with a queue file set up to download and install b43-fw-cutter first, then download and install b43-firmware. Legacy was never used.