I know it's usually not necessary to re-compile the kernel, but sometimes I like to experiment.

And usually it's no problem to keep the kernel images and modules separate from the official Slackware kernel package installs.

For instance, I add "-axe" to the kernel append line in the kernel config, so running "make modules_install" causes the modules to get sent to /lib/modules/2.6.33.4-axe.

But running "make firmware_install" sends the firmware to /lib/firmware and I'm concerned this could interfere with the official -firmware or -fw packages provided by Slackware.

And even if I got the firmware to a separate directory automatically, I don't know of any way to tell the kernel to look in a specific directory for that kernel's version at boot-time.

This *might* help you, just make sure you perform this task in a separate dir than /usr/src/linux-2.6.33.4:
http://blog.tpa.me.uk/slackware-kernel-compile-guide/

1 members found this post helpful.

Is there a particular reason that you feel it is necessary to run make firmware_install?

You can install firmware somewhere else by running:
You'll have to configure udev to load the firmware to load from the new path.
I have no idea how to do that, sorry.

1 members found this post helpful.

I wasn't sure if it's necessary or not. I don't always know what I'm doing. I saw the firmware_install option when running make help, and I ran it to see if it would install anything newly built. Figured I should have everything that was just built, and I'm used to modules being kernel-specific, so thought I'd better try to use the firmware as well.

So I'm wrong on a couple things, and learned a little about the files in /lib/firmware yesterday while doing something unrelated, and am now under the impression I need to do some more reading before I experiment.

After reading the replies here, I'm inclined to believe I shouldn't and don't need to worry about the firmware.

Thanks, people.