Quote:
|
Originally Posted by spiky0011
The output of lsmod
Module Size Used by
modprobe -v b43 shows nothing
|
IMO, no modules were listed by that because you chose to build in the kernel's drivers as opposed to building them as modules (nothing wrong about that). Anyway, that is what the "[*]" thing in menuconfig usually means, and I think that is what you meant in post #1.
I don't really know with authority what you need to do about the wireless thing. Sorry. I can only say what my experience was with a driver that likewise required me to acquire and add external firmware. It was for the radeon graphics driver, but the situation may apply here. I found that if I compiled the radeon driver as a module, then I merely had to copy the external firmware to /lib/firmware/radeon after compiling the kernel. But if I compiled the kernel with the radeon driver built in, then I had to build in the external firmware by adding it as extra firmware for the kernel's firmware library in menuconfig before compiling the kernel. I think all of this may have to do with the kernel initializing built-in drivers for detected devices early before the root filesystem may be mounted. Whereas driver modules are loaded later (unless an initial ram filesystem is used, and I don't). I don't know any of this with certainty or with authority, and I can't prove it ATM either.
So I guess what I'm suggesting is to try recompiling the kernel with your wireless driver stuff as modules (and visually confirm that the broadcom .fw files were put in /lib/firmware/b43 by b43-fwcutter). Or else, recompile the kernel and list all that broadcom firmware as extra firmware in menuconfig. You may not want to do either of those ideas (understandable because either one is considerable work and are sort of based on a stranger's hunch). Personally, I would do the modules idea (sounds easier to me). Actually, I chose to compile a large number of drivers as modules.
No promises for anything above this sentence. This is just something to consider and is based on my personal and anecdotal experience, not any formal training, knowledge, or expertise. Maybe somebody else will come along with a better idea or otherwise confirm my experiences and thoughts on the matter.
P.S.: If you decide to do something suggested above, first make and test a backup of the system. I always create a tarball of my LFS system before I try anything new on it (and I have restored back from those tarballs many times). And even if a new kernel works for the wireless thing, don't remove the original kernel for a while.
