| Summary: | wifi fails to start on broadcom BCM 4313 through Network Center | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Tauseef Hussain <tauseef> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | philippel, tauseef, tmb |
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | list of commands in the order of execution | ||
|
Tauseef Hussain
2013-06-25 22:22:38 CEST
CC:
(none) =>
tauseef
claire robinson
2013-06-26 09:48:57 CEST
CC:
(none) =>
tmb Here it works fine without any of these modprobe command. Btw, maybe you could give a try to networkmanager I did a fresh install of Mageia 3. enabled the non free updates. i saw that by default brcmsmac was used as the driver. I learnt from many online forums that the "wl" proprietary driver provided by Broadcom is a better one. Hence, accordingly I used the MCC to install the following : 1.dkms-broadcom-wl ( kernel module for broadcome wireless adapters) 2. broadcom-wl-kernel-3.8.13-desktop-1.mga3 After installing the above I see wireless networks through the Network Center icon at lower left tray on desktop. But when i try to connect to them, the system fails to connect displaing the message "Connection failed ". Please tell me what should i do to access wireless on Mageia 3. I have been using Mageia 3 on desktop for a long time now and I dont want to switch to a different linux just because I cannot access wireless through it. I have the same chipset in my laptop, and have been experiencing the same problem since Mageia 1. Even if it fails to connect upon completion of the configuration, it should work if you reboot your computer. Not sure exactly why, but the network config tool can't seem to figure out how to get the interface up and going once you've given it all the information. Rebooting will allow your system to load the correct modules and associate them with the proper interfaces and it should work fine from then on. CC:
(none) =>
philippe.l This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |
Created attachment 4168 [details] list of commands in the order of execution do a reboot of Mageia 2 system on my Lenovo laptop.(with my wifi switch turned on and the wifi led glowing) take logs of several commands(lspcidrake,lsmod,iwconfig) to see status of wireless connection on my machine. With the network center tool, accessed through the bottom left panel on desktop, I can see that SSIDs are listed but signal strengths are at zero levels. Then a I do a modprobe of lib80211 and wl drivers. I see refresh teh list of SSIDs on the network center tool and the signal strength goes up to 100% for all the SSIDs. I select one of the SSID and press on the "connect" button. After few seconds it fails to connect and displays this message - "fail to connect" on a new small popup window. The complete list of commands,in the order executed, is given in the attached text file. details of my system are [root@localhost gehna]# uname -a Linux localhost.localdomain 3.4.45-desktop-1.mga2 #1 SMP Sun May 12 13:07:18 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux