Would I need to recompile just to add, for example, the b43 firmware for broadcom chipsets?

I didn't do a full install, I installed everything except the KDE and XFCE trees. If I ran "slackpkg install-new" would this install those trees as well? If so, how would I avoid that?

Regarding the kernel packages, how exactly would I have the latest kernel packages (3.10.11) if I only installed from 14? I am using the slackware-current mirror and ran "slackpkg update" first thing when booting my system, but I didn't see any of the current kernel files.

What if I'm using slackbuilds? I installed openbox, tint2, and dmenu (along with a few other things) from slackbuilds earlier, would those be removed if they aren't in the mirror's file list?

No, I'm not. I'm using slackware-current for my mirror. Why is it that you're only supposed to use one mirror?

No
Please read "man slackpkg". You will see that the purpose of --install-new is not to get a full install, here "new" means "added to a newer release or to --current. If you want to install all packages just run "slackpkg install slackware" (but blacklist first those you don't want).
Do not use a -current mirror if you want to stay on 14.0, your kernel put aside. You're going to screw-up your Slackware for good.

If you want to upgrade only the kernel, see e.g. this HOW-TO from Alen BOB and reuse only the config.gz from -current before running "make oldconfig". Do not use slackpkg for that.
Just un-check them when you see the list of packages to remove if you run "slackpkg --clean-system"
Because else you'll screw up your system.

PS I can hardly see the benefit of upgrading the kernel on a T42 ;)

Brilliant, thanks for the concise, to-the-point answers!

One follow up question for it though: what exactly do you mean by "screw-up your Slackware for good" and what are the pros/cons for slack 14 vs current?

I was wanting to use a slackpkg for upgrading the kernel because I tried following that guide on a prior install and got an unfixable kernel panic. I just said "Screw it" and installed clean and was going to try again with a proper package if it was possible.

The benefit in upgrading the kernel on a T42 is for the b43 firmware I mentioned. I have another thread where I was discussing some wifi problems I'm having with a dual-band pcmcia card that requires that firmware but when I loaded it up on the 3.2.* kernel it only gave access to the 2.4Ghz range and not the 5Ghz. It was suggested that I try using the latest kernel with that firmware package.

In a Linux system, a given software often rely on other software that should be neither too old nor too new.
If you mix releases (or a stable release with -current) you mix parts that don't fit together, so some of your applications will fail.
Slackware-current being provided mainly to allow people to test it before it become the next stable release, I suggest you stay on 14.0 at the moment, as it is stable. You will be able to upgrade to 14.1 when it will: be ready: instructions for that will be provided

I see. Nevertheless, using slackpkg for that is not the way to go.

Then you could first check the support for you card in the b43 kernel module.

To do that, please provide output of following command:

I've already been through that. The b43 module does cover my card. I had a minimal install of Debian that I was working off of prior to using slack and I had the b43 module loaded in kernel 2.6.* and had access to both bands with no issue.

However, just for kicks I ran that command just to see if any new info would show up, and I saw the following for the card I'm using:

So, according to this I have some version of b43 already installed, but it doesn't allow the card to work.

Well, coming back from this thread...
<rant>But I've found 3 thread about your wireless card, really that doesn't help people to help you, so please be patient and keep only one thread open per topic, even if you don't get an answer within five minutes</rant>.

Back to your issue.

1. I think that you were mislead about backport. Reading this it seems that what is meant is "use on an older kernel a driver shipped in a newer kernel".
2. Anyhow on this page it is stated that your card [14e4:4328] is only partially supported by the b43 driver.
3. So your best bet would be to use the Linux STA driver from BROADCOM. At least they claim to support your dual-band PCMCIA card in their README.txt.
4. But as it may not be easy to install for a beginner (we will give you guidance as needed, though) and there were reports (maybe obsolete?) of a patch needed to make it work....
5. Let us first make 100% sure it is exactly this chipset and how it is currently handled by your system.

So first, please type exactly following commands (as root for lspci) and post back full results.

Well this thread was specifically meant for the slackpkg questions, it got off topic. Also, I am new to slackware, this is true, but I do know a fair bit about what I'm doing... sometimes. These issues have just gotten out of my grasp. Regardless, here are the results (all hand typed unfortunately...):
That kernel driver line is what confused me last time I ran the command, because if I have some b43 driver in use, should I see at least power supplied to the device?

lsmod is way too long, so instead I'll post a pastebin link *HERE* when I move over to my laptop.

Sorry if you felt my post was harsh. At least yes, this is that chipset. I'll will wait for your lsmod, meanwhile I'll compile the driver on my laptop to see if there is any hurdle on the way.

Not harsh, just blunt. I prefer blunt. Less chance of misinterpretation.

Also, post has been updated

Unfortunately, English is not my native language and I have hard time with polysemous words (and you have many of them :-)

I could build, install and load the module without a hitch. so I think that's worth trying. You will need the kernel sources for 3.2.45, so if need be do this firstThen just follow README.TXT or if you want a summary:
You should be all set then.

If that works, blacklist the modules you had to remove with 'rmmod' and add a line with: to /etc/rc.c/rc.modules-3.2.45

Please tell us the outcome.

PS I forgot to answer this:It is not uncommon that, though a driver claim a device, it be not the best to handle it. If there is a conflict (several drivers claiming the same device), one have to determine which is the best and blacklist the other one (which is easier and sometimes only possible if it is compiled as a module). But I am not very knowledgeable there, so anyone please correct me if I am wrong.

Wrong post, sorry

That's very true. I'm a native speaker and even I am learning new ones all the time.

I've used the wl module (built from source) before and it didn't work the way it should, wouldn't it be better to use the slackbuild packages for b43 or broadcom-sta (slackbuild for wl.ko)? If so, should/how do I remove the existing b43?

Welp, the source is no longer found on the broadcom website. Looked around, and I can't find it. The linux-sta hybrid driver is still available, but no where is the broadcom-sta source found.

Well, hybrid-sta and broadcom-sta are actually the same driver under different names, it seems. Also, you don't find the source because it is old and Broadcom seems to ship only the most recent driver.

But if you download the most recent one here the SlackBuild will fail, because the tarball versions don't match (but this can be easily fixed) and applying associated patch fail (as a source file has changed). But it seems that patch be no longer needed as the compilation goes fine without it.

I think that using the SlackBuild slightly updated to use the new source tarball is the way to go as it is cleaner than a direct install (afterwards the package can be managed with the Slackware tools), but as the end result should be the same, please first elaborate a bit the problem you had building it from source as the sentence "it didn't work the way it should" doesn't give much clue about what went wrong.

So please list the steps you followed and their results.

I'm going to try using the 3.10.* kernel tonight, but when I tried last time (I may have messed something up along the way) the wl driver wound up not allowing full access to the network, meaning that my connection was very slow as well as the 5ghz range was unavailable.