Description of problem: Mageia 3 wouldn't see my wifi router, although it would see other wifi networks. - Is my network "secret"? I don't know, it might be. - Did my wifi worked with Mageia 2 and 1? I didn't have a home internet connection back then. It seemed to work fine on public networks. My system was not a new install, but an upgrade from Mageia 2. After doing a new, testing, installation of Mageia 3, it turned out that the nonfree driver is to blame. broadcom-wl-kernel-xxxxx (testing various kernels, versions... they all had the same problem) I think that the Live ISO's use the nonfree driver. Uninstalling it, fixes the problem - in my testing installation of Mageia 3, a system restart was also needed. - in my default installation of Mageia 3, it worked right after I uninstalled the nonfree driver I will do some more testing with Cauldron. Version-Release number of selected component (if applicable): broadcom-wl-kernel-xxxxx How reproducible: every time Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
Created attachment 4438 [details] lspcidrake -v my netbook's hardware
did you used kernel, broadcom-wl or glibc from the testing repositories ? cf https://bugs.mageia.org/show_bug.cgi?id=11463#c5
I used the standard "broadcom-wl-kernel-xxxxx" packages. I didn't use any testing packages. There is a "glibc" rpm installed in my system, but it is not a "kernel", so I guess that this is not what you are referring to.
By the way, the "broadcom-bcma-config" package doesn't seem to affect this bug, whether it is installed or not. The only affect it has is that it might need a system restart, after you installed it, or uninstalled it, so as to have the wifi working properly again.
For Mageia 4 ... The same problem is there in Mageia 4 Live DVD, (ATTENTION -->>) although the broadcom-wl-kernel rpm is NOT installed, by default. Installing the broadcom-wl-kernel rpm, as you would expect, does NOT fix the problem. But I tried it anyway. So, I could not fix it in a system installed with a Live DVD. On the other hand, the problem is NOT there, if you use the DulaArch DVD, to make a new installation. Because it uses the free drivers, I suppose...
Some more results with this issue. Again, I ran the Live DVD (not installing it) and Mageia could see my router. (In the past, I had done the same with a Mageia 4 Live RCsomething DVD, with good results, and I had come under the impression that this bug was solved). Now, I did a new installation of the Live DVD, BUT... when I did the first boot (before creating the first account), I chose not to let the system configure the internet connection. And, yes, when I logged in, Mageia could see my router. So, I suspect, that, during the first boot, of a newly installed Mageia, the system configures my wifi connection in a way that is different to the way that is configured when you just ran the Live DVD. The next days I will double check that...
I have the same Broadcom chipset in a HP Pavilion dv7 (details on request but I don't think they're relevant), i.e. PCI id 14e4:4727 (rev 01). The version 6.30.223.141 Broadcom wl STA hybrid driver wrapped by the current non-free broadcom-wl and dkms-broadcom-wl packages (i.e. version 6.30.223.141) works fine at the physical level (i.e. the chipset connects fine to APs to set up the WPA2 session) but it fails to get DHCP going on some APs. For instance, it works fine on a Hua Wei ADSL Wireless router (sorry, can't lookup model number) but it fails to get an IP address on my provider (Telenet)-provided latest cable modem/wireless router. However, when I download the latest version (6.30.223.248) of the STA driver directly from Broadcom and compile the kernel module myself, suddenly it all works again and I can connect again to my wireless cable modem just fine (there is still the occasional kernel trace and power setting interface errors in dmesg I've come to expect of the prop driver but nothing fatal). So, the non-free packages need upgrading to version 6.30.223.248 of the driver in order to support kernel versions > 3.11. Despite the fact that this only looks like a patch version, the README_6.30.223.248.txt states that this version is NOT a patch version and that it supercedes all previous versions (don' ask my about Broadcom release versioning policy!). Given the widely reported problems issues with Broadcom chipsets since mid last year I guess it makes sense to upgrade the non-free packages.
CC: (none) => gbormann.nospamHardware: i586 => AllVersion: 3 => 4Source RPM: (none) => broadcom-wl-kernel-desktop-latest-6.30.223.141-32.mga4.nonfree, broadcom-wl-kernel-server-latest-6.30.223.141-32.mga4.nonfree, dkms-broadcom-wl-6.30.223.141-32.mga4.nonfree
Now, with Mageia Live, beta 1, 32 bit, KDE, DVD, things have gone worse. After running the Live DVD, and entering KDE, and opening the Network Center, you see NO wi-fi networks to connect to (if the Network Center filters out week signals, this might be the reason I don't see neighbor routers) If I choose to Create a New Connection, the wizard will see the neighbor's signal, but, again, of course, not my router.
Continuing with this bug... after updating from Mageia 3 to Mageia 4... now, I cannot see my router.
Now in Mageia 4, I have tried it with, or without, the broadcoam kernel. In both cases the problem is there. So in Mageia 4 not only the proprietary, but the free drivers, too, have this issue. I also tried dkms-broadcom-wl No luck there, either.
The same problem with Mageia 5, beta 1. Both, with the broadcoam kernel, or without it.
A newer version of the driver is available from broadcom... http://www.broadcom.com/support/802.11/linux_sta.php > WHAT'S NEW IN RELEASE 6.30.223.23X > --------------------------------- > + Upgraded to Support 3.11 kernels > + Added cfg80211 wowlan support for Magic Packets and Disconnect
I have such a problem with a PCI-E wifi card. On my LAN there is a wifi router D-LINK DIR615 which is used by a desktop and a laptop, all use Mageia 4. I wanted to configure a new desktop with Mageia 4 and a wifi PCIE card. The green wifi icon was shown, an IP address and DNS server are allocated. But no route to LAN or internet is available. Ifconfig shows it is UP. I have another wifi router DIR615. I plug it on the LAN... and the wifi works fine with it! I think I made a mistake in the first initialization with MCC. I tried to remove the connection and I have compared the installation with other PC. IMO, something wrong is somewhere, but where?
CC: (none) => jarillon
Nikos, the broadcom world is pretty complicated, so it's quite impossible to make it work on LiveDVD. It's possible but you need to do some manual steps. On the installed system the following command: rpm -qa |grep broadcom should return only this package: broadcom-bcma-config If there are any other *broadcom* packages just remove them and reboot. You should have a working system. If not then report back. To make it work on a LiveDVD you would have to unload some modules and then reload only those that are needed, else the modules will conflict and your wifi won't work. I might be wrong but it was something like that: 1. rmmod brcmsmac && rmmod bcma && rmmod ssb && rmmod b43 2. echo "blacklist ssb" >> /etc/modprobe.d/blacklist-mga.conf && echo "blacklist b43" >> /etc/modprobe.d/blacklist-mga.conf 3. modprobe bcma 4. Open network center and it should be able to connect. broadcom-bcma-config is for step 2 but it can't be done on live system. Pierre, is your PCI-E wifi card from broadcom? If not then it's unrelated problem and you should open a new bug.
CC: (none) => mageia
Yes it returns only "broadcom-bcma-config", but it is not working properly. I won't go into customizing the Live CD, as I have upgraded my installation to Mageia 4, and the problem is present (in the free and in the proprietary driver). I have also ran a live image of Android, with the proprietary driver, and it, too, had this issue. To sum up... the last driver that did work alright, was the free driver from Mageia 3. Downgrading to that driver is some sort of solution, that should work. (I might also try a test installation of Mageia 5, in another partition, but I don't expect to see any different results)
> Pierre, is your PCI-E wifi card from broadcom? If not then it's unrelated > problem and you should open a new bug. It is a broadcom. But now,the PC belongs to my grandson and is not at home. It works fine on a numericable wifi. Only the first link cannot work. I resume: * Router 1 - not correct * Router 2 - works fine (D-LINK DIR615 same model than Router 1) * Numericable box : works fine. IMO, it is a problem of configuration rather than a problem of driver.
Ok, more on the subject... I ran CentOS Live CD, and it worked fine. It uses... kernel 3.10 http://rpm.pbone.net/index.php3/stat/4/idpl/26642947/dir/centos_7/com/kernel-3.10.0-123.el7.x86_64.rpm.html linux-firmware-20140213-0.3.git4164c23.el7 http://rpm.pbone.net/index.php3/stat/4/idpl/26644695/dir/centos_7/com/linux-firmware-20140213-0.3.git4164c23.el7.noarch.rpm.html and I get the following, with lspci, but it doesn't print any "Kernel modules: " information (as described here: http://www.cyberciti.biz/faq/linux-find-wireless-driver-chipset/) [liveuser@localhost ~] lspci -vv -s 07:00.0 ... kernel driver in use: bcma-pci-bridge If all these mean anything...
>> IMO, it is a problem of configuration rather than a problem of driver. It seems that there are different BCM4313 chips, and some drivers work on some of them, while other drivers work on other chips. https://www.google.gr/search?q=bcma-pci-bridge https://www.google.gr/search?q=Problem+linux+BCM4313 and... https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
Summary: BCM4313 broadcom wifi nonfree driver doesn't see my router => BCM4313 broadcom wifi driver doesn't see my router
Created attachment 5835 [details] lspci from CentOS 7 Live CD
Mageia 5, beta 3, Live KDE, 32bit, The problem is still there. With the standard configuration, or after installing broadcom-wl-kernel-3.19.0-desktop586-1.mga5 through the drakrpm (in both cases it sees other networks, just not mine :( )
CC: (none) => doktor5000
Any opinion tmb?
CC: (none) => tmbSource RPM: broadcom-wl-kernel-desktop-latest-6.30.223.141-32.mga4.nonfree, broadcom-wl-kernel-server-latest-6.30.223.141-32.mga4.nonfree, dkms-broadcom-wl-6.30.223.141-32.mga4.nonfree => kmod-broadcom-wl
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you 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. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
See also Bug 12954 - broadcom bcm4311 wi -fi problem Always for broadcom, see Bug 15618
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD