I have a Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller. I set it up with ndiswrapper in suse 10.1, and everything was working great untill I tried to connect. It gave me a error,Aborting network swithcing due to invalid WEP key specification. In Kwifimanager where it said WEP on, I typed off and then it only goes into ad-hoc and I can't go online, any suggestions?

I have the same card using suse 10.1 as well.

I can't even see my wireless network which I know is OK because I tested it in XP. Did you have any problems viewing you network?

I decided to use WEP to start off until I can get the wireless connection working!

you will need to get your Windows driver which is somthing.INF

You will need to load this with ndiswrapper
Then you will need to
modprobe ndiswrapper and it will be functioning

Hi, yea I had already done all that. Using ndiswrapper 1.22, and drivers from

http://biginoz.free.fr/linux/bcmwl5a.inf
http://biginoz.free.fr/linux/bcmwl5.sys

do the modprobe

Do a iwconfig wlan0 and get

wlan0 IEEE 802.11g ESSIDff/any
Mode:Managed Frequency:2.462 GHz Access Point: Not-Associated
Bit Rate:54 Mb/s Tx-Power:25 dBm
RTS thr:2347 B Fragment thr:2346 B
Encryption keyff
Power Managementff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

I know there is something that am missing because it appears that other people have gotten this card to work on Suse 10.0 and ubuntu (breezer badger)

I have the same setup as each of you(SUSE 10.1/Broadcom), and this is what I have to do:

Allow KNetworkManager to load and attempt to connect. It fails.
Go into KWifiManager, scan for networks, find the Network, change WEP to "off".
Hit "Switch to Network". Will not connect, but Kwifimanager will go to Ad-hoc mode.
THEN, attempt to connect (again) with KNetworkManager. This does it for me, and gets me into my wireless. It's quite a hassle, I'm trying to figure out how to do it all with KNetworkManager, which is actually what I came here to post about when I saw your thread.

Hi Richard,
I'm nearly there. Am getting the aborting network switch due to invalid WEP key specification mesage from kiwiManager (have WEP back on now). I'm sure this is straight forward enough to sort.

I also had to use the blue function key to get the device active (Fn + F2).

I'm not sure how to solve your problem. What type of machine have you got? What way have you got the wireless card set-up in yast. Are you using ndiswrapper?

I'm using a Gateway 7510 GX with a Broadcom 4318 (AirForceOne 54G) Wireless Card. Yes, I'm using ndiswrapper. In YaST, there are two options, "User controlled with Network Manager" or "Traditional Method with ifup". Device Type is Wireless, Configuration Name is wlan0. And it's set with automatic device setup with DHCP. In General under Common Network Interface is Firewall Zone, set to No Zone, All Trafic Blocked (eh ?). Device Activation is On Cable Connection, User Controlled is unchecked and there is nothing set for MTU.

Miracuously, it started connecting all by itself when I start my laptop now. Odd, things don't normally happen spontaneously in Linux.