https://bugzilla.novell.com/show_bug.cgi?id=446158 User jmatejek@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=446158#c4 Summary: on MSI PR200 with iwl4965, rfkill switch does not work Product: openSUSE 11.1 Version: Beta 5 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: hschaa@novell.com ReportedBy: jmatejek@novell.com QAContact: qa@suse.de Found By: --- when the rfkill key is pressed, the LED light is toggled but the wireless card doesn't register the change until i do "ifconfig wlan0 down && ifconfig wlan0 up", or alternately "rmmod iwlagn && insmod iwlagn" basically the same as bug 446013. relevant comments: ------- Comment #4 From Jan Matejek 2008-11-18 07:49:28 MST [reply] ------- Private i can confirm this on iwl4965 toggling the rfkill doesn't leave any trace in dmesg, apart from a bunch of "key unknown". afterwards, i first need to do "ifconfig wlan0 down" (which, by the way, stalls pretty much everything else for about a second) and then "ifconfig wlan0 up". afterwards, the wifi works. ------- Comment #11 From Jan Matejek 2008-11-18 09:21:31 MST [reply] ------- Private (In reply to comment #9 from Helmut Schaa)
Do you have a hardware kill switch or only function keys to enable/disable wireless?
Not sure i understand the question. There is no physical "switch", but there's a dedicated key that toggles wireless and bluetooth. It emits "Unknown key pressed", but works - at least it did, at some point of time. Most special keys on this laptop behave like this, emit "key unknown" but work anyway. Anyway, the LED light is toggled properly and after insmod/rmmod the card knows which state it's in. ..actually it emits two keycodes, one for "bluetooth toggle" and one for "wifi toggle". But the bluetooth doesn't have its own rfkill, it's instead a usb device that is connected and disconnected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.