You are not logged in.
Pages: 1
My asus ux32VD fails to find DSTS during boot:
dmesg | grep wmi
[ 5.131249] wmi: Mapper loaded
[ 5.670761] asus_wmi: ASUS WMI generic driver loaded
[ 5.682175] asus_wmi: Initialization: 0x1
[ 5.682215] asus_wmi: BIOS WMI version: 7.9
[ 5.682276] asus_wmi: SFUN value: 0x4a2877
[ 5.682474] asus_wmi: Can't find DSTS
I've found this patch that should solve the problem, but I'm not sure how to proceed?
http://comments.gmane.org/gmane.linux.kernel/1315719
Any help would be appreciated.
Offline
Ditto. Same here. This is probably also the reason, why the asus_laptop module can't be loaded. With the newest kernel, most buttons work, except that they aren't mapped to any action via acpid (at least thats what I see in the dmesg log) - didn't bother to manually assign them. Guess we will have to wait a few days until this problem is sorted out.
Update: I patched the 3.4.4 kernel with the mentioned fix. Now the acpi events seem to be correct ..kinda - it sends button/VolDown/Up etc. back, but the events still don't trigger any action. Don't know how this usually works, but on my old asus laptop (which loads the asus-laptop module without problems) the asus-laptop module seems to handle these events (sending the necessary commands to the mixer, screen brightness control stuff etc.).
I looked through the source of the asus-laptop module, but I didn't find out how it triggers actions like volup/down. Can anyone shed some light on that?
Last edited by dontbugme (2012-07-06 17:46:10)
Offline
@beosound
Instructions are there:
https://wiki.archlinux.org/index.php/AS … ction_keys
Offline
Pages: 1