Bug 663852 (False, Positive, RFKill)

Summary: RFKill False Positive for Mobile Intel Wireless 5300
Product: [Fedora] Fedora Reporter: Jakob J Lorberblatt <beiyaku>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: dcbw, jklimes
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-13 21:26:57 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:
Attachments:
Description Flags
Comment none

Description Jakob J Lorberblatt 2010-12-17 03:19:42 UTC 
Description of problem:
From Fresh Install on Fedora 14 i386 NetworkManager lists wireless as disabled, attempts to bring up wireless result in RFKill enabled unable to complete type errors.

Version-Release number of selected component (if applicable):
Fedora 14 i386 Release Versions, will update if more currently updated (I'm pretty sure it was but will verify precise version)

How reproducible:
Like clockwork, happens every time on fresh install

Steps to Reproduce:
1. Take ZaReason (brand name, linux only netbook) Terra w/ intel 5300 upgrade
2. Install Fedora 14 i386
3. Examine the NetworkManager status of wireless, no adapters, when wlan0 exists in ifconfig results.
  
Actual results:
Disabled wireless from NetworkManager, wlan0 up by default but unassociated from command line in GUI

Expected results:
Available Networks, operational wireless networking, the usual NetworkManager thing.

Additional info:
I will try Kernel Modifications, and examine if the wrong driver ends up associated somehow; although I am fairly certain it all seems correct.
The Machine came pre-installed with Fedora 13 (basically default as far as they say, or I could tell) with the wireless functioning flawlessly.
Comment 1 Jirka Klimes 2010-12-20 12:05:04 UTC 
Please paste in /var/log/messages file. Also, could you grab output of these commands:
$ nm-tool

$rfkill list
Comment 2 Jakob J Lorberblatt 2010-12-21 22:52:07 UTC 
Created attachment 915174 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).
Comment 3 Jakob J Lorberblatt 2010-12-21 22:58:33 UTC 
rfkill was not installed by default on the system, rfkill unblock returns an error, unless rfkill unblock all is executed. Then as so many other times checked the network manager applet "Enable Wireless" clicked on it again, the checkbox was unchecked, checked it a second time and this time it is now enabled. Still it did and should work out of the box it is fully supported hardware.
Comment 4 Dan Williams 2011-04-13 21:26:57 UTC 
There have been some updates since then to make the wifi state work better.  Your problem was that initially the kernel reported the killswitch as on (ie radios disabled) and NM respects what the kernel says.  Then after the killswitch was turned off (ie, radios on) NM respected that, but when you toggle the Enable Wireless item, that state gets saved independently of the kernel rfkill state, and that was off.  I think in the end, the major problem is that the kernel drivers for you laptop are not properly processing the rfkill state.  In any case, try the updated version of NM in updates as that should work better here.  If not, please re-open.  Thanks!