| Summary: | netapplet detects wireless oddly with kernel 3.4.24 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Steve Havelka <yoshi> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | mageia, philippel |
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel--3.4.24 | CVE: | |
| Status comment: | |||
| Attachments: |
the bug
The bug in the network center display cauldron desktop 3.6.5 The bug showing up in the notifications |
||
|
Description
Steve Havelka
2012-10-15 22:17:43 CEST
I see the same in cauldron (don't have a mga2) with the same card and the classical kernel CC:
(none) =>
mageia Created attachment 3032 [details]
the bug
with the last kernel-desktop cauldron I see the bug too
with the linus one I don't see it, (and my led works too which was not the case before)
Created attachment 3034 [details]
The bug in the network center display
As you can see, there are three devices listed in the network center listing here -- one ethernet, two wifi, and only two named devices. The wifi does work--I'm using it now--but if I click on that middle device, the system tries to install the broadcom packages for 3.3.8.
Also included, a listing of /etc/sysconfig/network-scripts - as you can see, I only have the two ifcfg- files, one for each named device.[-]==============
(In reply to comment #3) > Created attachment 3034 [details] > The bug in the network center display > > As you can see, there are three devices listed in the network center listing > here -- one ethernet, two wifi, and only two named devices. The wifi does > work--I'm using it now--but if I click on that middle device, the system tries > to install the broadcom packages for 3.3.8. > > Also included, a listing of /etc/sysconfig/network-scripts - as you can see, I > only have the two ifcfg- files, one for each named device.[-]============== Oops -- sorry about the =====, my cat just tried to help with the bug report. Created attachment 3035 [details]
cauldron desktop 3.6.5
forget what I said in my last post, maybe it's my first boot in this kernel, don't remember, sorry :s
so here eth0 and eth1 are switched which is another bug iirc.
Created attachment 3046 [details]
The bug showing up in the notifications
For some reason, the notification tray also has the wrong device name, as you can see in the screenshot.
*** Bug 8744 has been marked as a duplicate of this bug. ***
Manuel Hiebel
2013-01-23 18:07:50 CET
Summary:
netapplet detects wireless oddly with testing kernel =>
netapplet detects wireless oddly with kernel 3.4.24 I have a broadcom BCM4313 and have similar issues. When kernel 3.4.24 was released, my wireless stopped working. I went through MCC to try and reconfigure it and discovered a new wireless interface wlan0 (previously wireless was known as eth0 or eth1). Configuring this new wlan0 allowed me to connect to my home wireless, however the signal strength was so poor (even being only 7-8 feet away from the router in direct line of sight) that this interface became unusable. I have a theory as to what the problem is. I think what's going on is that there is free in-kernel support for the broadcom chipset. When the new kernel was installed, the new interface wlan0 was revealed. However in my case (and this may also occur with other BCM43xx chipsets) the free driver doesn't work correctly and renders wireless unusable. Trying to reconfigure the interface to user eth1 as before failed as the driver could not be located. A little bit of digging, I found that the package dkms-broadcom-wl was not installed. Installing this package and kernel-firmware-nonfree as per the errata followed by a reboot allowed my connection to work again with the new 3.4 kernel and the closed driver. As a side effect of this though is that mageia's network applet now registers the wireless connection as being wired, and doesn't provide information about SSID or signal strength as it should normally do. So there is definitely a bug with the network configuration tool which is not aware that it's suppose to call dkms-broadcom-wl to make this interface work. In my case, I must use this driver as the free one doesn't work correctly at all. CC:
(none) =>
philippe.l Good news on this bug: yesterday I upgraded to the 3.4.32 kernel, on the netbook with the broadcom chipset, and the odd device detection seems to have mostly cleared itself up! I'm now seeing just two devices again, not three. The one remaining oddity is that the wifi device doesn't seem to be completely recognized as a wifi device. The net_applet icon doesn't show the signal strength bars, just the "device is connected" picture, as though this were a wired device. Still, it works, and it seems to pick up weak networks better again. closing then. For the other part it's another bug. (don't remember if we have one) Status:
NEW =>
RESOLVED |