I have a problem with my notebook again. I had to reinstall arch and now I cant get my special keys (FNs) to work.
Its a ASUS W1N and I had it run already once, but I didnt write it down and dont remember how I did it.
What I know and what I have done:
1) load module asus_acpi
2) start daemon acpid
I created some scripts which should perform some action (volume etc) when the keys are pressed, but when I start xev and try to get an output of the keyaction when I press it, nothing happens.
"$ ps ax" tells me, that acpid is running (no error on startup) and also lsmod tells me "asus_acpi 13976 0"
You have any idea what I should check or what could be the problem? Somehow I think its a problem of the module or acpid...
Thank you for you help!!
EDIT: On startup I get the message:
Asus Laptop ACPI Extras version 0.30
W1N model detected, supported
When I check the messages.log, I get a "Unknown handler group" or sth similar. But now it works.
For the W1N I had to change the amixer things to PCM.
Thanks for your help!!!
plz post full listing, i have problems with that
Sorry for my english
plz post full listing, i have problems with that
can you describe what kind of problem you have?
tail -f /var/log/messages.log will tell you the code of the pressed fn-key. just make a special acpi-handler file for it or use the handler.sh. be sure, that you have acpid running and loaded the asus-acpi module.
sorry for my bad english
I'm also having problems trying to put the Fn+ keys working on my ASUS A6Vc.
I tried following this Wiki on Hotkeys http://wiki.archlinux.org/index.php/Hotkeys but no luck.
The showkeys doesn't show anything for the Fn+(F10...F12) which should control the volume.
On ubuntu it worked out of the box, so it should work on Arch too... should only be a matter of how.
My messages.log says:
Jun 22 13:53:23 vudumachine logger: ACPI group/action undefined: hotkey / ATKD Jun 22 13:56:37 vudumachine logger: ACPI group/action undefined: hotkey / ATKD Jun 22 13:56:38 vudumachine logger: ACPI group/action undefined: hotkey / ATKD Jun 22 13:56:38 vudumachine logger: ACPI group/action undefined: hotkey / ATKD
The Fn+F2 that should change the wireless, shows no output on the message.log, but doesn't seem to do anything too.
The F1 (suspend), F5/F6(brightness), F8 (turn screen on/off) work.
How should I enable that asus-laptop module?
EDIT: I went to ACPI4Asus and since my kernel is >=2.6.21 i must use the CVS, but...
[root@vudumachine vudu]# cvs -d:pserver:email@example.com:/cvsroot/acpi4asus login Logging in to :pserver:firstname.lastname@example.org:2401/cvsroot/acpi4asus CVS password: cvs login: authorization failed: server acpi4asus.cvs.sourceforge.net rejected access to /cvsroot/acpi4asus for user anonymous
I tried anonymous and some other passwords, but nothing...
I dunno... I can browse the CVS on sourceforge's browser, but I can't seem to download the files with cvs.
EDIT 2: Ok, I managed to download the source files, one by one, from the cvs browser and compiled.
I edited the /etc/acpi/handler.h instead of using the samples of asus_acpi.
But I'd like to know to to show that pop up showing the volume change. I can see it's changing on gnome's volume applet, but I'd like to have that cool pop up that ubuntu has.
Last edited by VuDu (2007-06-22 17:13:15)
yes, i also want these nice popups. is there a chance to fade a picture in/out when changing the volume?
sorry for my bad english
asus-laptop is included with 2.6.21 default Arch kernel.
Just add asus_acpi to MOD_BLACKLIST and asus-laptop to MODULES in /etc/rc.conf.
asus-laptop to MODULES in /etc/rc.conf.
asus-laptop or asus_laptop?
And should I leave the DAEMONS as it is? What about the asus_acpi daemon that the acpi4asus installs?
Last edited by VuDu (2007-06-23 13:47:29)
asus-laptop. I don't use asus_acpi, so I have no idea. It should be possible to install only new asus_acpi daemon from new release of acpi4asus, without building the module.
Yes, latest ACPI4Asus does come with the Driver/Module asus-laptop and the Deamon asus_acpid.
I built the module and the daemon, added the module to the MODULE list and black-listed the old one.
But now I dunno how to use the asus_acpid daemon. I already have a acpid on DAEMON list on rc.conf.
I red on another thread that we could edit the /etc/acpi/handler.sh and so I manually added some actions to that file, but I'd like to know how to use the asus_acpi daemon.
Because that way I can make it run scripts that I may keep in my home folder that's great because I don't have to remember weird paths and backing it up before formatting the system.
Last edited by VuDu (2007-06-23 20:21:38)
VuDu: I haven't used asus_acpid, but probably you need to run both acpid and asus_acpid. If you have KDE, instead of asus_acpid you can try lapsus (it is in AUR).
Yes I already installed Lapsus and only found out it didn't work on Gnome when I ran it
If my asus_acpid is correctly installed, shouldn't it show up on /etc/rc.d like the other daemons? :s
It probably doesn't have rc script, but you can start it in /etc/rc.local file - just by adding "/usr/local/bin/asus_acpid &" line (or something similar).
Hmm... I am almost sure that once it was 'asus-laptop'. I have checked now, and it is 'asus_laptop'... Maybe the name of the module built from acpi4asus sources is different than the one that comes with kernel?
From the README:
This package provides 2 things :
- asus-laptop.o or asus-laptop.ko (for 2.6.X kernel), a kernel module to handle
hotkey events, LEDs, Backlight, etc...
- asus_acpid, a user-level daemon, based on acpid, to handle events generated
by the kernel module. This daemon is only provided as an example, you can use
any tool you want, as all events reported by the driver are inserted in the
/proc/acpi/event queue. So, if you want, you can use the regular acpid. The
advantage of this daemon is that it can be launched by any user, and so,
interact directly with the X session opened by this user. You may then be
able to launch X programs with this daemon, whereas with the classical ACPI
daemon, this is not possible easily.
We're supposed to build this new module to use it instead of the old one.
The old module is (not anymore?):
# modinfo asus_acpi filename: /lib/modules/2.6.21-ARCH/kernel/drivers/acpi/asus_acpi.ko license: GPL description: Asus Laptop ACPI Extras Driver author: Julien Lerouge, Karol Kozimor depends: vermagic: 2.6.21-ARCH SMP preempt mod_unload 686 parm: asus_uid:UID for entries in /proc/acpi/asus. (uint) parm: asus_gid:GID for entries in /proc/acpi/asus. (uint)
But it's weird, because the README also says to run the old module:
4.1 Kernel module
Try "modprobe asus_acpi". Check your dmesg (simply type dmesg). You should
see some lines like this :
So installing the kernel module should REPLACE the old one instead of installing a new one. So it doesn't really matter if it's asus-laptop or asus_laptop, because (for what I understand) it should work using the old name asus_acpi, like the README says.
The daemon is used by simply calling "asus_acpid" on the terminal. Now I wonder how to "put" it on rc.conf. Tanis said to use the full path, but how and where? Should I add the full path to the DAEMON=() list? Should I add it to /etc/rc.d/? How? Are there any HowTo's there about this?
And by the way, did anyone find how to show the "popup"? Using amixer doesn't show any popup.
Last edited by VuDu (2007-06-24 23:07:46)
Another weird thing is that the make install says:
make: Entering directory `/home/vudu/acpi4asus/driver' install -d /lib/modules/2.6.21-ARCH/acpi/ install -m 644 -c asus-laptop.ko /lib/modules/2.6.21-ARCH/acpi/
#modinfo asus-laptop filename: /lib/modules/2.6.21-ARCH/kernel/drivers/misc/asus-laptop.ko #modinfo asus_acpi filename: /lib/modules/2.6.21-ARCH/kernel/drivers/acpi/asus_acpi.ko
Where's the /lib/modules/2.6.21-ARCH/acpi/asus-laptop.ko from the make install?
Last edited by VuDu (2007-06-24 23:18:49)
I don't use asus_acpid, so I might be completely wrong
But I am pretty sure, that acpi4asus doesn't have any Arch rc.d scripts. So just forget about running it from /etc/rc.d or adding it to DAEMONS list. Unless you write your own rc.d script, or use Arch package for that, if there is any.
What you might want to do is to place asus_acpid somewhere, for example in /usr/local/bin, and run it using its full path in rc.local file.
But it will be started by root, so probablyit won't be able to "interact directly with X session".
You can also use it as a user, and run it from ~/.xprofile file in your user's home directory.
You won't be able to control volume level when you are not logged in though, because asus_acpid must be running for that.
Another thing - new acpi4asus releases provide asus-laptop driver. It is new, shiny and better than asus_acpi.
But standard Arch 2.6.21 kernel has both drivers built. The older one is placed in drivers/acpi/asus_acpi.ko,
and probably used by default. The new one is considered experimental, and is in drivers/misc/asus-laptop.ko - in kernel's 'config'
it is ina different place too. You don't need to build asus-laptop module, unless you want some newest features.
Could you check if you have asus-laptop.ko file in drivers/acpi as well?
Probably you have 3 files: acpi/asus_acpi.ko misc/asus-laptop.ko (both from stanrard Arch package), and acpi/asus-laptop.ko (built by acpi4asus makefile). Maybe modinfo just shows one of two asus-laptop.ko modules?
You can try to remove asus_acpi.ko and both asus-laptop.ko files and try 'make install' in acpi4asus sources again.
And do depmod -a if that makefile doesn't do that. After that you should be fine
As for "popups" - asus_acpid comes with some sample action files.
Those files show how to use osd_cat program (part of xosd package) to display "popup" messages (but you need to edit them to enable that). Those are not real pop-ups, just text printed on your screen.
Pop-ups similar to those present in Windows are different. I have no idea what makes Gnome show that
Another thing - that 'Try "modprobe asus_acpi".' in README is probably a bug. "asus_acpi" is the name of old driver. If you use that, you get 0.30 version (or 0.31/0.32, but it is still the old one). README should tell to load asus-laptop module.
I know But he uses Gnome...
acpi4asus shows whatever you want. It runs userscripts so you can set it to do whatever you want. The problem is knowing how to do what we want.