I have built kernel 3.3 on lfs, I checked the boxes (*) in the kernel for b43 drivers I installed wireles tools BLFS. I have followed this page
http://linuxwireless.org/en/users/Drivers/b43
Install from source b43 fw cutter & version 5.100.138 driver.
iwconfig shows NO wireless extensions

Thks in advance

I looked around for a bit and did not find the appropriate driver or method, but I did look at the page you mentioned in your post. Under "Supported Devices" there is no mention of your card, so it is not surprising that it failed to work. This might be and "ndiswrapper" kind of problem instead.

Another thought. If you actually meant that you had Broadcom 4318 instead of 4138, then you should first try "lsmod" in a terminal and see if the b43 module loaded. If not, try loading it with "modprobe".

Hi

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.

Thks stoat

I do keep tarballs of lfs I have built as well. As is with lfs it is learning which I am doing all the time, I will try both methods you have suggested. This will all be new to me regarding modules etc most times I have configured the kernel and it works but only with basic requirements, Thks I hope for pointing where to look at least for a start.

I think stoat is correct in his analysis. The monolithic kernel works for a lot of things, but you will find many instances where a module is called for instead. Broadcom is just a pain in the butt.

Hi

Thks for help on Modules I now have partial internet/networking.

My setup. Server Ubuntu connects to internet via 3g modem it then disturbutes internet to network via Ad Hoc, Ubuntu machines and window machines via eth0 and wlan0, I can connect LFS via eth0 all works well. Wireless on LFS only connects to lan I can ping other Ubuntu machine and server I can even ssh into server all by wireless, but I cant ping internet or use links on wireless.
I have not installed DHCP-4.2.3-P2 or set up DHCP-4.2.3-P2 client on LFS yet, is this the problem or is there something else in the kernel I need to setup 1st.
If I should still be able to ping outside lan without DHCP-4.2.3-P2 then I would like to fix this 1st.

Hi

Ok I have managed to fix the problem of connecting to internet, I installed dhcp, I installed the bootscript but this is causing an issue on boot, as i need to set the wireless card to Ad Hoc. It also hangs if there is not an eth0 cable connected, what i need to do is stop the dhclient bootscript from running on boot but I need dhclient installed,
So is there away to disable dhclient at boot?