On Sat, 14 Jul 2007 12:29:50 -0600, Karl Larsen wrote:
[...]
>> When I ran:
>> modprobe bcm43xx
>> from the command line, it didn't say anything, so I assume it worked.
>> Later, I added it to rc.local, and I assume it is ok.
>>
> Do not assume a darn thing. Do a lsmod and make sure it is in the
> kernel. Now take the thing out of rc.local. NeworkManager will add it to
> /etc/modprobe.conf and it will be taken care of.
>
With modprobe in rc.local:
[root@mbrc35 ~]# lsmod | grep bcm
bcm43xx 419681 0
ieee80211softmac 35137 1 bcm43xx
ieee80211 35081 2 bcm43xx,ieee80211softmac
bcm43xx_mac80211 397985 0
ssb 35013 1 bcm43xx_mac80211
mac80211 145609 2 rc80211_simple,bcm43xx_mac80211
With modprobe removed from rc.local:
[root@mbrc35 ~]# lsmod | grep bcm
bcm43xx_mac80211 397985 0
ssb 35013 1 bcm43xx_mac80211
mac80211 145609 2 rc80211_simple,bcm43xx_mac802
Is this ok?
[...
>>
>> When I try to activate it from the "Network Device Control" gui, I get:
>>
>> Error for wireless request "Set Mode" (8B06) :
>> SET failed on device wlan0 ; Invalid argument.
>> Error for wireless request "Set Bit Rate" (8B20) :
>> SET failed on device wlan0 ; Operation not supported.
>>
>> Determining IP information for wlan0... failed.
>>
>> and this in /var/log/messages:
>> Jul 14 13:21:51 localhost dhclient: wmaster0: unknown hardware
>> address type 801
>> Jul 14 13:21:51 localhost dhclient: wmaster0: unknown hardware
>> address type 801 Jul 14 13:21:51 localhost dhclient:
>> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
>> Jul 14 13:21:54 localhost dhclient: DHCPDISCOVER on wlan0 to
>> 255.255.255.255 port 67 interval 5
>> Jul 14 13:21:59 localhost dhclient: DHCPDISCOVER on wlan0 to
>> 255.255.255.255 port 67 interval 14
>> Jul 14 13:22:13 localhost dhclient: DHCPDISCOVER on wlan0 to
>> 255.255.255.255 port 67 interval 21
>> Jul 14 13:22:34 localhost dhclient: DHCPDISCOVER on wlan0 to
>> 255.255.255.255 port 67 interval 18
>> Jul 14 13:22:52 localhost dhclient: No DHCPOFFERS received.
>>
>> Watching the router, I see no sign of action. I note also that
>> WinXP on the same box makes the wireless connection with no problem.
>>
>>
> Well your not set up right yet in Linux so it will not work. What does
> nm-tool tell you about your setup?
>
> Karl
>
[root@mbrc35 ~]# nm-tool
NetworkManager Tool
State: disconnected
- Device: wlan0 ----------------------------------------------------------------
NM Path: /org/freedesktop/NetworkManager/Devices/wlan0
Type: 802.11 Wireless
Driver: bcm43xx-pci
Active: no
HW Address: [correct MAC address, pardon my paranoia]
Capabilities:
Supported: yes
Wireless Settings
Scanning: yes
WEP Encryption: yes
WPA Encryption: yes
WPA2 Encryption: yes
Wireless Networks (* = Current Network)
- Device: eth0 ----------------------------------------------------------------
NM Path: /org/freedesktop/NetworkManager/Devices/eth0
Type: Wired
Driver: e100
Active: no
HW Address: [correct MAC address, pardon my paranoia]
Capabilities:
Supported: yes
Carrier Detect: yes
Speed: 10 Mb/s
Wired Settings
Hardware Link: no
Looks ok to me; how does it look to you?
Mike.
