Bug 735516
| Summary: | keyboard: can't emulate rawmode for keycode 240 when enabling wifi by multimedia key | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Cristian Paul Peñaranda Rojas <paul> | ||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | desintegr, gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda, mads | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-11-14 17:03:56 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
Cristian Paul Peñaranda Rojas
2011-09-02 21:18:11 UTC
I found a workaround, the issue seems to don't be present from a f15 liveusb, in wich i was finally able to enable wifi by pressing multimedia-wifi key (FN F2), boot lapto as usual and the wifi still enable :-) So you can toggle the FN F2 button repeatedly using the F15 liveusb image and it will correctly enable/disable wireless? Does it also print out the keycode 240 message with the liveusb image? Can you provide the output of dmesg and rfkill from the liveusb boot both before and after toggling the switch? If the liveusb seems to be working correctly, does running the 2.6.38 kernel on the machine booted into the install also work? Yes it seems to enable/disable wireless from liveusb and also print the eycode 240 message I do not have a f15 liveusb but i an give a try to f16 beta, is okay for you? (In reply to comment #3) > I do not have a f15 liveusb but i an give a try to f16 beta, is okay for you? Yes, that would be great. I also have this problem with Fedora 16 and kernel 3.1.2-1.fc16.i686.PAE. I would precise, I have a Dell Mini 1018. Created attachment 575968 [details] messages and smolt and dmidecode I see this on a friends computer with F16 and 3.3 kernel - also a Dell Inspiron 1018 A02. The main problem as I (and they) see it is that if they happen to press that button then wireless stops working. The workaround that works for them is to boot into windows and press the button so a window pops up and a checkmark in wireless can be set. The same problem is seen when wireless is disabled in gnome shell. Enabling it again doesn't turn on wireless, just like pressing the button doesn't. I assume 'rfkill unblock' should enable wireless again, but it do also not make any difference. Please let me know if other debug information is needed. It seems like http://www.mydellmini.com/forum/ubuntu/24448-mini1018-wifi-switch-f2-doesnt-work.html describe the same problem. # Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient). With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report. Some quick testing last week (with 3.6.6, IIRC) indicated that f2 no longer killed wireless permanently ... but it still gave the 240 message, and f2 didn't work as a kill/don't kill switch. I might be able to do some proper testing later on and reopen and make a decent report. |