PDA

View Full Version : Dreaded broadcom wireless on Fedora 7



Prank
9th June 2007, 10:30 AM
Hi All,

I have a Compaq V3000 laptop with dual boot WinXP & Fedora 7.
I have spent a lot of the last week trying to get my wireless working with no success.

I have tried using ndiswrapper to use the windows driver but am not sure of how well it worked.

As it sits, in my 'Network Devices' under 'Hardware' I have a "Broadcom Wireless Dell Corporation 1390" but it is listed as 'Ethernet' and not 'wireless'. If I try to add a new one, this broadcom does not exist in the list of adapters, also there is nothing other than 'ethX' options.

Should I try using fwcutter? I'm not sure of where to go from this point.. I can assure you I have spent some time searching google and these forums and have tried a lot of suggested examples but to no avail.

Thanks in advance!!!

Christian

leadgolem
9th June 2007, 10:48 AM
Last time I used ndiswrapper, my broadcom showed up as ethoX as well. It worked just fine though.

platomxv
9th June 2007, 11:31 AM
Please post the output from

ls /lib/firmware

Norm

Prank
9th June 2007, 12:25 PM
Last time I used ndiswrapper, my broadcom showed up as ethoX as well. It worked just fine though.
Yeah, it lists in there, but I forgot to mention that it is not in the devices list and when I try to add it as a device, the adapter isnt listed.


Please post the output from

ls /lib/firmware

Norm
ipw2100-1.3.fw ipw-2.4-boot.fw ipw-2.4-sniffer_ucode.fw
ipw2100-1.3-i.fw ipw-2.4-bss.fw iwlwifi-3945.ucode
ipw2100-1.3-p.fw ipw-2.4-bss_ucode.fw LICENSE.ipw2100
ipw2200-bss.fw ipw-2.4-ibss.fw LICENSE.ipw2200
ipw2200-ibss.fw ipw-2.4-ibss_ucode.fw zd1211
ipw2200-sniffer.fw ipw-2.4-sniffer.fw

Thanks guys.

Prank
9th June 2007, 12:26 PM
This might be easier to read

-rw-r--r-- 1 root root 209190 2004-09-28 01:26 ipw2100-1.3.fw
-rw-r--r-- 1 root root 201138 2004-09-28 01:26 ipw2100-1.3-i.fw
-rw-r--r-- 1 root root 196458 2004-09-28 01:26 ipw2100-1.3-p.fw
-rw-r--r-- 1 root root 191142 2006-03-08 06:49 ipw2200-bss.fw
-rw-r--r-- 1 root root 185660 2006-03-08 06:49 ipw2200-ibss.fw
-rw-r--r-- 1 root root 187836 2006-03-08 06:49 ipw2200-sniffer.fw
-rw-r--r-- 1 root root 6472 2005-08-11 23:06 ipw-2.4-boot.fw
-rw-r--r-- 1 root root 168344 2005-08-11 23:06 ipw-2.4-bss.fw
-rw-r--r-- 1 root root 16334 2005-08-11 23:06 ipw-2.4-bss_ucode.fw
-rw-r--r-- 1 root root 162884 2005-08-11 23:06 ipw-2.4-ibss.fw
-rw-r--r-- 1 root root 16312 2005-08-11 23:06 ipw-2.4-ibss_ucode.fw
-rw-r--r-- 1 root root 168344 2005-08-11 23:06 ipw-2.4-sniffer.fw
-rw-r--r-- 1 root root 16344 2005-08-11 23:06 ipw-2.4-sniffer_ucode.fw
-rw-r--r-- 1 root root 148476 2007-04-21 01:05 iwlwifi-3945.ucode
-rw-r--r-- 1 root root 11880 2004-03-04 06:13 LICENSE.ipw2100
-rw-r--r-- 1 root root 12007 2005-08-11 22:33 LICENSE.ipw2200
drwxr-xr-x 2 root root 4096 2007-06-03 08:35 zd1211

ramasees
9th June 2007, 12:48 PM
not sure if this will help you but this is what i did to get my wireless working in fc7 for my broadcom card

su -
yum -y install bcm43xx-fwcutter
wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2
tar xvf broadcom-wl-4.80.53.0.tar.bz2
cd broadcom*
cd kmod
/usr/bin/bcm43xx-fwcutter -w /lib/firmware wl_apsta.o
echo 'blacklist bcm43xx' >> /etc/modprobe.d/blacklist
modprobe -r bcm43xx
modprobe -r ieee80211softmac
modprobe -r ieee80211_crypt
modprobe -r ieee80211
modprobe -r bcm43xx_mac80211
modprobe bcm43xx_mac80211

restart

PhillipGreen
10th June 2007, 03:31 AM
Hi . . . I'm also having a problem with my wireless card in Fedora 7 on my laptop. I tried exactly what Ramasees suggested above. The good news is now my card will show all the available wireless networks (including mine); however, my card will not connect to my wireless network. Any suggestions? I've noticed that under Network settings there is still no Wireless card device (as there used to be in Fedora Core 6) . . . might this have something to do with it?? I held off from adding a new wireless device because I wanted more input. Below is my info:

OS: Fedora Seven

Linksys Wireless-G Notebook Adapter 2.4 GHz: Model No. WPC54G ver. 3 (Chipset Broadcom, BCM4318 . . .I think)

Linksys Wireless-G Broadband Router 2.4 GHz: Model No. WRT54G ver. 6

Laptop Hardware: Gateway 450SX4, Pent. IV, 1.5 Ghz, 512 Ram (Full Specs at http://support.gateway.com/s/Mobile...501271sp2.shtml)

Thank you all very much for your time and help.

Sincerely,
Phillip

Prank
10th June 2007, 11:11 AM
Hi ramasees,
I gave that a go, but still no go. Any other suggestions?

Thanks guys!

Prank
11th June 2007, 11:57 AM
Ok, so the latest in my saga is that I used this link to turn the KNetworkmanager on;
http://fedoraproject.org/wiki/Tools/NetworkManager#head-fc3fe44e92c63867615113b1ef69cf4fc0dc03cf

I can now see the wirless networks when I right click on the network manager icon in the panel but I cant connect to it. It gets to 'Activation stage: Configuring device' at about 28% and then gives me 'Connection Failure: Could not connect to the network XXXXX'.

Here is a snip from /var/log/messages



Jun 12 06:54:20 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1'
Jun 12 06:54:20 localhost NetworkManager: <info> SUP: response was 'OK'
Jun 12 06:54:20 localhost NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jun 12 06:54:20 localhost NetworkManager: <info> SUP: response was 'OK'
Jun 12 06:54:20 localhost NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jun 12 06:54:20 localhost NetworkManager: <info> SUP: response was 'OK'
Jun 12 06:54:20 localhost NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jun 12 06:54:40 localhost NetworkManager: <info> Activation (wlan0/wireless): association took too long (>20s), failing activation.
Jun 12 06:54:40 localhost NetworkManager: <info> Activation (wlan0) failure scheduled...
Jun 12 06:54:40 localhost NetworkManager: <info> Activation (wlan0) failed for access point (CB)
Jun 12 06:54:40 localhost NetworkManager: <info> Activation (wlan0) failed.
Jun 12 06:54:40 localhost NetworkManager: <info> Deactivating device wlan0.
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: Removing Interface type 2
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: Wireless interface stopped
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: DMA-32 0x0200 (RX) max used slots: 1/64
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: DMA-32 0x02A0 (TX) max used slots: 0/128
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: DMA-32 0x0280 (TX) max used slots: 0/128
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: DMA-32 0x0260 (TX) max used slots: 0/128
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: DMA-32 0x0240 (TX) max used slots: 0/128
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: DMA-32 0x0220 (TX) max used slots: 22/128
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: DMA-32 0x0200 (TX) max used slots: 0/128
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: Radio turned off
Jun 12 06:54:41 localhost kernel: ssb: Switching to ChipCommon core, index 0
Jun 12 06:54:41 localhost kernel: ssb: Switching to IEEE 802.11 core, index 1
Jun 12 06:54:41 localhost kernel: bcm43xx_mac80211: Radio turned off
Jun 12 06:54:53 localhost kernel: bcm43xx_mac80211: Adding Interface type 2
Jun 12 06:54:53 localhost kernel: ssb: Switching to ChipCommon core, index 0
Jun 12 06:54:53 localhost kernel: ssb: Switching to IEEE 802.11 core, index 1
Jun 12 06:54:53 localhost kernel: bcm43xx_mac80211: Radio turned on
Jun 12 06:54:53 localhost kernel: bcm43xx_mac80211: Radio enabled by hardware
Jun 12 06:54:53 localhost kernel: bcm43xx_mac80211: !WARNING! Idle-TSSI phy->cur_idle_tssi measuring failed. (cur=21, tgt=62). Disabling TX power adjustment.
Jun 12 06:54:53 localhost kernel: bcm43xx_mac80211: Chip initialized
Jun 12 06:54:53 localhost kernel: bcm43xx_mac80211: 32-bit DMA initialized
Jun 12 06:54:53 localhost kernel: bcm43xx_mac80211: Wireless interface started
Jun 12 06:54:53 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready

ramasees
11th June 2007, 01:31 PM
this may or may not help you
it seems alot of people are doing su when it should be su - try installing again you might have better luck

mwensyel
17th June 2007, 01:39 AM
I have the same problem. The card shows up as ETH1 under network as a wireless connection. Wireless Assistant sees wireless networks, including mine. I have added the security codes in wireless assistant for my network. When I try to connect, I get connecting... then failed to connect. I followed the post using su -, but no success.

weapon
17th June 2007, 01:00 PM
I have the EXACT same laptop, and had the same problem.

I ended up giving up and installing ubuntu, but I got sick of that and on Friday installed Fedora 7 again!

I could not get bcm43xx working (and it is limited to 11mb/s) but I got ndiswrapper working straight away.

1) Update (at least NetworkManager and wpa_supplicant and kernel if not everything)
2) install ndiswrapper
3) install the driver:
su -
ndiswrapper -i filename
(I downloaded the driver fro the HP website - just the Windows xp not vista)
(if you download the driver you need to install cabextract to extract the files)
4) remove other drivers
modprobe -r bcm43xx
modprobe -r bcm43xx_mac80211
5) add driver
modprobe ndiswrapper

if all goes well the little light for the wireless should go blue and you should be able to connect.

if everything works
1) add to modprobe.conf (or create a file modprobe.d/ndiswrapper)
blacklist bcm43xx
blacklist bcm43xx_mac802
alias wlan0 ndiswrapper
2) if you still have to modprobe ndiswrapper at boot add to /etc/rc.local
modprobe wlan0

mlager
18th June 2007, 07:35 PM
Running into the same problems with an Acer Aspire 9413Z. So far I haven't gotten anywhere with ndiswrapper, which just seems to work fine on my desktop. I'm currently using an old sweex usb thingy I apparently still had lying around somewhere. Surprisingly it worked out of the box.

Still, it's no real solution and I would prefer to use the internal wifi.

sailor
18th June 2007, 08:09 PM
I have a acer aspire with the built in broadcom wireless...I got it working once once I rebooted it was gone for good. I know my acer has a on/off switch for the wifi...and I have heard that this is the main problem.
My solution was to buy a D-Link AirExtreme G 650 pcimia card (ahteros chipset) and set it up with madwifi.

kai4785
23rd June 2007, 07:38 PM
This is from /var/log/messages. I was connected to the wired network and switched with the NetworkManager icon to the wireless network that it was able to see.



Jun 23 06:17:42 lappy NetworkManager: <info> User Switch: /org/freedesktop/NetworkManager/Devices/wlan0 / brogersclan
Jun 23 06:17:42 lappy NetworkManager: <info> Deactivating device wlan0.
Jun 23 06:17:42 lappy dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/wlan0 for sub-path wlan0.dbus.get.reason
Jun 23 06:17:42 lappy NetworkManager: <info> Device wlan0 activation scheduled...
Jun 23 06:17:42 lappy NetworkManager: <info> Deactivating device eth0.
Jun 23 06:17:42 lappy dhclient: wmaster0: unknown hardware address type 801
Jun 23 06:17:42 lappy dhclient: wmaster0: unknown hardware address type 801
Jun 23 06:17:42 lappy dhclient: DHCPRELEASE on eth0 to 192.168.0.1 port 67
Jun 23 06:17:43 lappy NetworkManager: <info> Activation (wlan0) started...
Jun 23 06:17:43 lappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 23 06:17:43 lappy avahi-daemon[2256]: Withdrawing address record for 192.168.0.13 on eth0.
Jun 23 06:17:43 lappy avahi-daemon[2256]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.0.13.
Jun 23 06:17:43 lappy avahi-daemon[2256]: Interface eth0.IPv4 no longer relevant for mDNS.
Jun 23 06:17:43 lappy avahi-daemon[2256]: Withdrawing address record for fe80::216:36ff:fe62:7a65 on eth0.
Jun 23 06:17:43 lappy avahi-daemon[2256]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::216:36ff:fe62:7a65.
Jun 23 06:17:43 lappy avahi-daemon[2256]: Interface eth0.IPv6 no longer relevant for mDNS.
Jun 23 06:17:43 lappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jun 23 06:17:43 lappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jun 23 06:17:43 lappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jun 23 06:17:43 lappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jun 23 06:17:43 lappy NetworkManager: <info> Activation (wlan0/wireless): access point 'brogersclan' is encrypted, but NO valid key exists. New key needed.
Jun 23 06:17:43 lappy NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'brogersclan'.
Jun 23 06:17:43 lappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jun 23 06:17:45 lappy NetworkManager: <info> Activation (wlan0) New wireless user key for network 'brogersclan' received.
Jun 23 06:17:45 lappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 23 06:17:45 lappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jun 23 06:17:45 lappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jun 23 06:17:45 lappy NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jun 23 06:17:45 lappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jun 23 06:17:45 lappy NetworkManager: <info> Activation (wlan0/wireless): access point 'brogersclan' is encrypted, and a key exists. No new key needed.
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: sending command 'INTERFACE_ADD wlan0 wext /var/run/wpa_supplicant '
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: response was 'OK'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: sending command 'AP_SCAN 1'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: response was 'OK'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: sending command 'ADD_NETWORK'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: response was '0'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 62726f67657273636c616e'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: response was 'OK'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt NONE'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: response was 'OK'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_key0 <key>'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: response was 'OK'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 wep_tx_keyidx 0'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: response was 'OK'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0'
Jun 23 06:17:46 lappy NetworkManager: <info> SUP: response was 'OK'
Jun 23 06:17:46 lappy NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jun 23 06:17:47 lappy wpa_supplicant[3076]: Trying to associate with 00:0f:66:60:3d:9f (SSID='brogersclan' freq=2437 MHz)
Jun 23 06:17:47 lappy wpa_supplicant[3076]: Associated with 00:0f:66:60:3d:9f
Jun 23 06:17:47 lappy wpa_supplicant[3076]: CTRL-EVENT-CONNECTED - Connection to 00:0f:66:60:3d:9f completed (auth) [id=0 id_str=]
Jun 23 06:17:47 lappy NetworkManager: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'brogersclan'.
Jun 23 06:17:47 lappy NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 23 06:17:47 lappy NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Jun 23 06:17:47 lappy kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Jun 23 06:17:48 lappy NetworkManager: <info> Activation (wlan0) Beginning DHCP transaction.
Jun 23 06:17:48 lappy dhclient: wmaster0: unknown hardware address type 801
Jun 23 06:17:48 lappy NetworkManager: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Jun 23 06:17:48 lappy NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface wlan0
Jun 23 06:17:48 lappy NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface wlan0
Jun 23 06:17:48 lappy dhclient: wmaster0: unknown hardware address type 801
Jun 23 06:17:48 lappy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
Jun 23 06:17:48 lappy avahi-daemon[2256]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::214:a5ff:feb1:5642.
Jun 23 06:17:48 lappy avahi-daemon[2256]: New relevant interface wlan0.IPv6 for mDNS.
Jun 23 06:17:48 lappy avahi-daemon[2256]: Registering new address record for fe80::214:a5ff:feb1:5642 on wlan0.*.
Jun 23 06:17:52 lappy NetworkManager: <info> Old device 'wlan0' activating, won't change.
Jun 23 06:17:54 lappy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
Jun 23 06:18:06 lappy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
Jun 23 06:18:21 lappy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 23 06:18:28 lappy dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
Jun 23 06:18:33 lappy NetworkManager: <info> Device 'wlan0' DHCP transaction took too long (>45s), stopping it.
Jun 23 06:18:33 lappy dhclient: wmaster0: unknown hardware address type 801
Jun 23 06:18:33 lappy dhclient: wmaster0: unknown hardware address type 801
Jun 23 06:18:34 lappy NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Jun 23 06:18:34 lappy NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface wlan0
Jun 23 06:18:34 lappy NetworkManager: <info> DHCP daemon state is now 14 (normal exit) for interface wlan0
Jun 23 06:18:34 lappy NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) started...
Jun 23 06:18:34 lappy NetworkManager: <info> Activation (wlan0) New wireless user key requested for network 'brogersclan'.
Jun 23 06:18:34 lappy NetworkManager: <info> Activation (wlan0) Stage 4 of 5 (IP Configure Timeout) complete.
Jun 23 06:23:51 lappy wpa_supplicant[3076]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jun 23 06:23:52 lappy wpa_supplicant[3076]: Trying to associate with 00:0f:66:60:3d:9f (SSID='brogersclan' freq=2437 MHz)
Jun 23 06:23:52 lappy wpa_supplicant[3076]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jun 23 06:23:59 lappy NetworkManager: <info> wlan0: link timed out.
Jun 23 06:24:07 lappy wpa_supplicant[3076]: Authentication with 00:00:00:00:00:00 timed out.
Jun 23 06:24:08 lappy wpa_supplicant[3076]: Trying to associate with 00:0f:66:60:3d:9f (SSID='brogersclan' freq=2437 MHz)
Jun 23 06:24:23 lappy wpa_supplicant[3076]: Authentication with 00:00:00:00:00:00 timed out.
Jun 23 06:24:23 lappy wpa_supplicant[3076]: Trying to associate with 00:0f:66:60:3d:9f (SSID='brogersclan' freq=2437 MHz)
Jun 23 06:24:38 lappy wpa_supplicant[3076]: Authentication with 00:00:00:00:00:00 timed out.
Jun 23 06:24:45 lappy wpa_supplicant[3076]: Trying to associate with 00:0f:66:60:3d:9f (SSID='brogersclan' freq=2437 MHz)
Jun 23 06:25:00 lappy wpa_supplicant[3076]: Authentication with 00:00:00:00:00:00 timed out.


I tried just like ramasees suggests, after switching to root with su - . I am not getting any better performance. It seems to fail twice. First, it authenticates the key, and then fails on DHCPDISCOVER. Then it tries again and fails on the authentication for the key.

From here I'm going to try NDSWRAPPER and see how far I can get. Let me nkow if this helps.

scotta3234
23rd June 2007, 08:00 PM
Can an Community Manager or Admin please move my how-to to the how-to section for broadcom cards, particularly the broadcom 1390: http://fedoraforum.org/forum/showthread.php?t=156282

ramasees
23rd June 2007, 08:20 PM
i have a gui version of ndiswrapper in my how toos which might help some of you and if you want to remove the built in rt2xx ,broadcom so it doesnt interfere with ndiswrapper you need to do
su-
rm -rf /lib/modules/2.6.21-1.3228.fc7/kernel/drivers/net/wireless/mac80211/rt2x00; depmod

worked well for me but use at your own risk

Savij
26th June 2007, 01:50 AM
Here is how I got my brodacom 1394 wireless adapter connected to my WPA encrypted network in FC6. I see no reason why this shouldnt work for any combination of linux distro, wireless adapter, laptop provided the following statements are true:

Your linux distro recognises your adapter is connected to the system
Your wireless adapter is listed on the ndiswrapper website
You have the the windows drivers handy - (the .sys and .inf files)

You will need the following tools:

ndiswrapper
wpa_supplicant - should already be installed if using fedora

You will NOT need:

the linux bcm43xx kernel module
or the bcm43xx-fwcutter tool

Make sure your not running NetworkManager.

install the windows drivers:


# ndiswrapper -i /path/to/bcmwl5.inf

make sure everythings ok:


# ndiswrapper -l

bcmwl5 : driver installed
device (14E4:4311) present (alternate driver: bcm43xx)


Now you need to edit the /etc/wpa_supplicant/wpa_supplicant.conf file.

First you can use the 'wpa_passphrase' tool to calculate your psk in hex. usage is :

wpa_passphrase <ssid> [passphrase]

so:


# wpa_passphrase mySSID myPassphrase
network={
ssid="mySSID"
#psk="myPassphrase"
psk=bdf58e1a5b00b3cf004bde118f7affe8e8098a9c97a738 b144f21136894af890
}

Copy the output onto the clipboard and open the wpa_supplicant.conf. Edit so it looks like this, using the information you just copied:


ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel

network={
ssid="mySSID"
#psk="myPassphrase"
psk=bdf58e1a5b00b3cf004bde118f7affe8e8098a9c97a738 b144f21136894af890

key_mgmt=WPA-PSK
pairwise=TKIP
proto=WPA

}


You should unload the bcm43xx kernel module:


# rmmod bcm43xx

And load the ndiswapper module:


# modprobe ndiswrapper

You can now make a connection like so:


# wpa_supplicant -ieth1 -Dwext -c/etc/wpa_supplicant/wpa_supplicant.conf

Of course you should replace eth1 with your wireless device name.

You will get lots of output as the program will run in the foreground. Use the -B switch to suppress all this nasty stuff once you get it working.

Wait a couple of seconds for the handshake to complete then run (in another terminal):


# ifup eth1

or


# dhclient eth1

Use wpa_supplicant with the -d or -dd switch for more detail if you get problems. Hope this works for you!

mlager
26th June 2007, 08:44 AM
I got mine working a couple of days ago with ndiswrapper. The biggest problem seems to be to find a compatible .sys and .inf file. The once provided by the driver CD didn't work in my case and I had to try several hundrerds before I got a set that would do the trick.

sjdude
13th September 2007, 07:29 AM
Please: when you say connecting failed, be sure to say whether you are using encryption and, if so, which variety. I have gotten BCM4318 working (using ndiswrapper and native) but each has problems for me. With ndiswrapper, I can get full speed with WEP and no encryption, but I can't get WPA working. I believe I've seen WPA working with the native driver, but I could only get 1Mbps over the air.

So when you're reporting "my connection fails", please also report the encryption you are using as well. Chipset (e.g. BCM4318, etc. is also important!).

Thanks everyone!

sjdude
21st September 2007, 02:28 PM
I spent over a week and a half in BCM4318 hell and finally gave up. On F7, I was able to get WEP working with both the native driver and ndiswrapper. I was, at one point, able to get WPA working with the native driver, but I could never get full speed with it, only about 1Mb/sec. Since I use WPA at my office, I needed full speed.

So, eventually, since this was a new install for me, I decided to try a different distro "just to see what would happen". I dropped ubuntu 7.04 on the machine and whatever kernel version and native driver combination it has works for me, full speed, and with both WPA and WEP, which is what I needed.

My conclusion: F7 + BCM4318 + WPA: not working

I posted some details of what I did here: http://forums.fedoraforum.org/forum/showthread.php?t=165967

Good luck to the rest of you.