Forwarding with permission.
--- Begin Message ---
- To: Jonathan Nieder <jrnieder@gmail.com>
- Subject: Re: asus-wmi: use ASUS_WMI_METHODID_DSTS2 as default DSTS ID
- From: Carsten Otto <otto@informatik.rwth-aachen.de>
- Date: Tue, 26 Jun 2012 21:34:13 +0200
- Message-id: <20120626193413.GA21479@carsten-otto>
- Reply-to: Carsten Otto <otto@informatik.rwth-aachen.de>
- In-reply-to: <[🔎] 20120626192847.GA11961@burratino>
- References: <[🔎] 20120626191749.6002.44628.reportbug@localhost.localdomain> <[🔎] 20120626192847.GA11961@burratino>
On Tue, Jun 26, 2012 at 02:28:47PM -0500, Jonathan Nieder wrote: > The kernel package has an asus_wmi module, but you seem to be loading > one from somewhere else. Can you say more about what happened? Yes. I applied the patch manually and compiled from source (in my stable system). Then I loaded the module using insmod. I am still trying to determine if that solves my problems. > What symptoms did you experience? Which kernel version did the > problem start with --- is this a regression? Once we understand the > nature of the problem, we can move on to figuring out how to fix it. The sympton is that the Fn keys (for example Fn+F10 to disable the speakers) do not trigger any action, even "xev" does not show anything. I did not see any other behaviour so far (the system is brand new). > The patch you pointed to addresses a symptom that would be signalled > by "Can't find DSTS" in the kernel log, which I don't see in yours. My current assumption is that I did not even trigger this part of the module yet. I am investigating and experimenting. Best regards, -- Carsten Otto otto@informatik.rwth-aachen.de LuFG Informatik 2 http://verify.rwth-aachen.de/otto/ RWTH Aachen phone: +49 241 80-21211Attachment: signature.asc
Description: Digital signature
--- End Message ---