Comment 25 for bug 1277959

@Ant,

Your model does not use the asus_nb_wmi driver which the bug is about, so your problem is not related to this particular bug, nor is the workaround for you. Blindly applying patches/workarounds not meant for your model would only make the problem worse.

If you have a thread on the problem on ubuntuforums.org, please give me its link so I can try what we can. If not, and the problem still exists, I suggest you do that now - post a thread on ubuntuforums.org and give me its link (posting it here or via PM on ubuntuforums).

PS:
Based on confirmations in comment #22 here, and comment #59 in the related bug #1173681 , I have edited the ubuntuforums post (http://ubuntuforums.org/showthread.php?t=2181558) to change the wapf value from 1 to 4, and added the request to post the command output for model number.

Still unsure though why it broke on models on which there was no problem with older kernels. As long as that remains unexplained and the Fn+F2 unfixed, this will still remain a 'Workaround', not a fix.

But thanks to you, Hans, for at least patching the code for reported models to make them work out of box, and not requiring to apply the workaround manually.

It'd be a delightful day when the real culprit is found and the 'real' fix is released, so that the Fn+F2 issue is fixed too.