Bug 246689
Summary: | Dell 1490 (Broadcom 4312) wireless interface won't start | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bruce Orchard <orchard> | ||||||||||||||||||||
Component: | kernel | Assignee: | John W. Linville <linville> | ||||||||||||||||||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||||||||||
Priority: | low | ||||||||||||||||||||||
Version: | 7 | CC: | cebbert, davej | ||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||
Hardware: | i686 | ||||||||||||||||||||||
OS: | Linux | ||||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||
Last Closed: | 2007-08-21 18:43:12 UTC | Type: | --- | ||||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||
Embargoed: | |||||||||||||||||||||||
Attachments: |
|
Description
Bruce Orchard
2007-07-04 01:20:41 UTC
Created attachment 158489 [details]
ifcfg for wireless
Created attachment 158490 [details]
kudzu description of wireless interface
This is the output from kudzu -p for the wireless interface. This interface
description does not end up in /etc/sysconfig/hwconf
Created attachment 158492 [details]
Output from ifconfig -a
Created attachment 158493 [details]
WEP key
Please attach the output of running 'dmesg' shortly after booting and attempting to bring-up the interface. Do you have the proper firmware installed? Created attachment 158525 [details]
output from dmesg
The interesting part starts at line 428
The wireless interface works OK with Windows, so I would expect the firmware is correct. Created attachment 158552 [details]
Output from lsmod
Note that bcm43xx_mac80211 is loaded
Created attachment 158628 [details]
bcm43xx-mac80211.example
Did you actually ifup the interface before running dmesg? I'm attaching
example dmesg output from my bcm4318 pccard on my FC6 Thinkpad. Please notice
how your dmesg lacks the corresponding lines starting with the "Adding
Interface" line. This should have been tiggered by ifup or the equivalent
"ifconfig wlan0 up" or similar.
Also, based on comment 7 I have to ask if you have run bcm43xx-fwcutter, and if so what driver you used to source the firmware? Created attachment 158685 [details]
Output from dmesg including ifup wlan0
Here is the output from dmesg including when ifup wlan0 was run. I see it is
looking for bcm43xx_microcode5.fw. I found the file Windows is using for a
driver, bcmwl6.sys, but fwcutter refuses to run on it, saying it is an
unrecognized file.
Here is what Windows Vista says about \\windows\system32\drivers\bcmwl6.sys File description: BCM 802.11g Network Adapter wireless Type: System File File version: 4.82.28.56 Product name: BCM 802.11g Network Adapter wireless Copyright: 1988-2006, Broadcom Corporation, All Rights Size: 453 KB Date modified: 11/2/2006 2:30 AM Language: Language Neutral Try this procedure: # you need to be root wget http://downloads.openwrt.org/sources/broadcom-wl-4.80.53.0.tar.bz2 tar -xjvf broadcom-wl-4.80.53.0.tar.bz2 bcm43xx-fwcutter -w /lib/firmware/ broadcom-wl-4.80.53.0/kmod/wl_apsta.o Follow that by either 'modprobe -r bcm43xx-mac80211 ; modprobe bcm43xx-mac80211' or simply reboot. Does that work any better for you? Created attachment 159097 [details]
dmesg output from ifup
Here is what ifup said: [root@orchard-laptop-2 network-scripts]# ifup wlan0 Error for wireless request "Set Bit Rate" (8B20) : SET failed on device wlan0 ; Operation not supported. Determining IP information for wlan0... From dmesg, it looks like it found the firmware All that looks fine. Do you get a usable connection? Closed due to lack of response...please re-open when the requested information becomes available... |