Bug 304682

Summary:	NetworkManager wrongfully interprets radio killswitch on ipw2100
Product:	[openSUSE] openSUSE 10.3	Reporter:	Forgotten User Drfk9mafMw <forgotten_Drfk9mafMw>
Component:	Network	Assignee:	Danny Al-Gaaf <dalgaaf>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 2
Target Milestone:	---
Hardware:	i686
OS:	Other
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	/var/log/messages /var/log/NetworkManager

Description Forgotten User Drfk9mafMw 2007-08-26 00:07:56 UTC

With wifi turned on, NetworkManager thinks the wireless nic is turned off. Turning the card off, /var/log/messages report (correctly) that the wireless interface is turned off -- /var/log/NetworkManager however does the exact opposite:

Aug 26 01:47:27 dionysosBeta2 kernel: eth1: Radio is disabled by RF switch.

vs:

Aug 26 01:47:30 dionysosBeta2 NetworkManager: <info>  Wireless now enabled by radio killswitch

Trying to enable wireless in knetworkmanager when the RF switch is already turned on yields this:

Aug 25 15:10:52 dionysosBeta2 NetworkManager: <info>  User request to enable wireless overridden by radio kill switch.

Comment 1 Forgotten User Drfk9mafMw 2007-08-26 00:08:35 UTC

Created attachment 159871 [details]
/var/log/messages

Comment 2 Forgotten User Drfk9mafMw 2007-08-26 00:08:58 UTC

Created attachment 159872 [details]
/var/log/NetworkManager

Comment 3 Andreas Jaeger 2007-08-26 07:50:21 UTC

Might be a duplicate of 303834 - but that one was ipw3945.

Comment 4 Forgotten User Drfk9mafMw 2007-08-26 09:30:57 UTC

Hello, I was just about to say that this very much looks like a duplicate to me, too! Seems I wasn't having my eyes open when reading the MABs...

The described behavior fully matches mine here, so it seems the chipset doesn't make a difference.

Comment 5 Danny Al-Gaaf 2007-08-26 12:03:12 UTC

the bug effect all intel WLAN chipsets.

*** This bug has been marked as a duplicate of bug 303834 ***