Bug 16957 - Wifi status in taskbar is unreliable for Broadcom chipset.
Summary: Wifi status in taskbar is unreliable for Broadcom chipset.
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-10-14 09:59 CEST by Herman Viaene
Modified: 2016-12-21 09:05 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Herman Viaene 2015-10-14 09:59:54 CEST 
Description of problem:
Broadcom BCM4313 wifi. The wifi status indicator in the taskbar (KDE) is unreliable. It reports the linklevel either as more than 90% - which is correct as laptop and router are in the same room - or in about 2 out of 3 reboots as 0%. This reporting never changes during a session. And the internet connection always works OK, what is very unlikely if the linklevel is really 0%.

AFAICS this never happens on another laptop with Atheros wifi.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Backlund 2015-10-14 10:06:00 CEST 
is this with the broadcom-wl driver or the in-kernel drivers ?

CC: (none) => tmb

Comment 2 Herman Viaene 2015-10-14 10:37:05 CEST 
It is the broadcom-wl driver
Comment 3 Marja Van Waes 2016-12-21 07:36:13 CET 
Is this bug still valid?

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Assignee: bugsquad => kernel

Comment 4 Herman Viaene 2016-12-21 08:42:52 CET 
I cann't test it anymore. That laptop has gone to IT-heavens.
Comment 5 Marja Van Waes 2016-12-21 09:05:30 CET 
(In reply to Herman Viaene from comment #4)
> I cann't test it anymore. That laptop has gone to IT-heavens.

Thanks for the feedback, closing as OLD, then

@ anyone still seeing this issue:

Please reopen this bug report :-)

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.