Bug 373961
Summary: | Broadcom wireless device does not show up in system-config-network on Dell Inspiron 1520 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Răzvan Sandu <rsandu2004> |
Component: | system-config-network | Assignee: | Harald Hoyer <harald> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | jmoskovc, sergio, ville.skytta |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | http://forum.notebookreview.com/showthread.php?t=152717 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-05-04 16:27:38 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: | |||
Bug Depends On: | 244029, 328451 | ||
Bug Blocks: |
Description
Răzvan Sandu
2007-11-09 22:28:56 UTC
Here's the complete output of wlassistant, in a background terminal, when trying to start the device wlan0 using it: [root@mazarin ~]# wlassistant kbuildsycoca running... Reusing existing ksycoca Loaded application options. All interfaces: eth0, virbr0, wlan0, wmaster0 Wireless interface(s): wlan0 Permissions checked. DHCP Client: dhclient All executables found. scan: /sbin/iwlist wlan0 scan Networks found: 1 ACTION: CONNECT. No DHCP client running. No pre-connection command specified. iwconfig_set: /sbin/iwconfig wlan0 mode managed channel 6 key off essid zando iwconfig_ap: /sbin/iwconfig wlan0 ap 00:19:5B:0E:A6:27 ==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory Using wpa_supplicant driver: wext WPA client started. Waiting for status... ==>stderr: Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory CONNECTION FAILED. disconnect: /sbin/iwconfig wlan0 mode managed key off ap off essid off Application options saved. Kernel socket closed. what is the output of: # iwconfig ?? Reproduced with "04:09.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)". iwconfig looked ok (don't have the output available any more, sorry). What fixed it for me was manually adding "alias wlan0 b43" to /etc/modprobe.conf. Hello, Here's the output of iwconfig, as Harald requested: [root@mazarin ~]# iwconfig lo no wireless extensions. wmaster0 no wireless extensions. wlan0 IEEE 802.11g ESSID:"" Mode:Managed Channel:0 Access Point: Not-Associated Tx-Power=0 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:off 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 eth0 no wireless extensions. virbr0 no wireless extensions. Thanks a lot, Răzvan I've followed advice in comment #3 and I've manually put "alias wlan0 b43" in /etc/modprobe.conf, then rebooted. Now wlan0 *does* show up in system-config-network's Hardware tab and one may attempt configuring it on the Device tab. I've tried to guess the proper settings; however, I get the error: Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Invalid argument. Regards, Răzvan I got that too, apparently s-c-n creates some bogus (at least for these devices) entries in the config file, maybe that's another bug. I trimmed my /etc/sysconfig/network-script/ifcfg-wlan0 to the following and it now works without any error messages: TYPE=Wireless DEVICE=wlan0 HWADDR=... BOOTPROTO=dhcp DHCP_HOSTNAME=... ONBOOT=yes USERCTL=no IPV6INIT=no PEERDNS=yes ESSID=... (In reply to comment #6) > /etc/sysconfig/network-script/ifcfg-wlan0 I meant /etc/sysconfig/network-scripts/ifcfg-wlan0 this is the same bug of #370971 ? I was unable to connect just by following Ville's advice in comment #6. I also added a CHANNEL=6 to it. However, I *did* connect after logging in as root and manually starting wlassistant. But until now I was unable to automatically regain connection after restart. BTW, where do we save/set the preshared key ? I am using WPA2 with preshared key; access point is a DLink DWL-G700AP. wpa_supplicant must be started at boot (checked in ntsysv) while we experiment all these ? I'll try rebooting again... Regards, Răzvan the thing at least with me , when I turn wifi on: Nov 13 04:19:30 localhost kernel: ipw2200: Failed to send SCAN_ABORT: Command timed out. Nov 13 04:19:31 localhost kernel: ipw2200: Failed to send CARD_DISABLE: Command timed out. and things like that I realize that is because: cat /etc/sysconfig/wpa_supplicant # wlan0 and wifi0 # INTERFACES="-iwlan0 -iwifi0" INTERFACES="-ieth1" # ndiswrapper and prism # DRIVERS="-Dndiswrapper -Dprism" DRIVERS="-Dwext" so here , after comment driver section (with #) and keep my interface I got wireless working again. see man wpa_supplicant to find your appropriate driver Hello, There are some *very strange things* here... 1. The wlan0 interface doesn't go up at boot, independently of the fact that wpa_supplicant is started automatically (marked in ntsysv) or not. 2. However, manually starting wlassistant as root and inserting the correct parameters *does* bring up the interface (and then works normally, good performance). One must check the "ASCII" box near the WPA key field in wlassistant to get the password working (I use an alphanumeric password). 3. The WiFi LED on the laptop stays out even when the interface wlan0 do work. 4. wpa_supplicant does not start at boot, even when it's checked in ntsysv. However, if I (re)start it manually, it shows an error message about a missing file, but it starts (writes OK in green). IMHO, at boot, the radio connection (ESSID, key, etc.) must be set up *before* system-config-network tries to wake up all the interfaces - please correct me if I'm wrong... Where do we set up the wireless parameters for the whole system (at boot), if we don't want to use wlassistant ? Regards, Răzvan > system-config-network tries to wake up all the interfaces
huh? when does it do that?
Sorry, I meant starting interfaces at boot (eth0, wlan0, etc.) Răzvan To summarize: About the bug we are discussing here (#373961), I will consider it fixed if the next update of system-config-network: - automatically creates an entry for the wireless adapter on the Hardware tab (see comment #3 above), provided that someone previously installed the correct firmware, as presented in bug #336981, comment #4; - allows for flawless configuration of it on the Devices tab, as for any other network interface. The rest of issues (authentication in the wireless network) seems to be wpa_supplicant-related (please see bug #375721). (Esentially, wpa_supplicant *fails at boot*, but succesfully allows for *manual* restarting service later, after the system has been started. However, it throws error messages in both cases). Regards, Răzvan Sorry, I've meant "...as presented in bug #328451, comment #4" in the sentence above. Răzvan s-c-network part fixed in git. will be in the next update. stay tuned. Hello, Here's some indirect feedback I have about the Dell Inspiron 1520 wireless from another user - Franco, in Italy. I quote it for reference, even if I don't know it's the exact same issue: "hi, i'm in italy and i found your post very interesting, i do have an ispiron 1520 i installed fedora 8 and so far no majors problem only problem i do have is the wireless, i have a broadcom corporation bcm4312 pt 802.11 a/b/g i did install and has been reconized but as soon i do activation saysError for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Invalid argument. SIOCSIFFLAGS: No such file or directory can you help me? please? ciao franco" This refers to my post on: http://forum.notebookreview.com/showthread.php?t=152717 Seems to be solved - now wlan0 shows up in system-config-network. system-config-network-1.5.7-1.fc9.noarch Closing - many thanks. Răzvan |