.
Get your own
Free Website now!
This laptop and most acer laptops have some extra hotkeys that do not work out of the box. To get them working, you will need the acerhk driver from http://www2.informatik.hu-berlin.de/~tauber/acerhk/. The latest version of this driver is 0.5.34. This version, without a patch, will need to be loaded with the force_series=4650 parameter in order to work. However, I have contacted the author of this driver, Olaf Tauber, and he provided me with a patch to make it autodetect Aspire 9110 Series. You can get this patch here. To apply it, simply replace the acerhk.c file that is in the 0.5.34 tarball with the one that you get from here. See the README and INSTALL files for installation instructions. If you notice that the latest version of acerhk is not 0.5.34 but something higher than that, then probably you will not need this patch as Olaf Tauber will probably have included it in the driver. (Please mail me if you notice that, so that I change this paragraph)
To save some resources, you can load this driver with the poll=0 parameter, as polling isn't actually needed for this model.
UPDATE: If you are using my linux-2.6.19-beyond4 packages or you are building linux-2.6.19-beyond4 with the acerhk.patch then you don't need to compile acerhk separately, because it is included in the kernel.
When you have successfully loaded the driver (i.e. the kernel module "acerhk"), get this shell script and run it as root (you may have to make it executable with chmod +x setup_keycodes). You will probably want to place it somewhere in your init scripts so that it is executed at every boot. The above script maps key scancodes to kernel keycodes. It does not make them functional under X. To map these keys under X, download this xmodmaprc file and this script, put them in the same directory, and run the script (you may also have to make this script executable with chmod +x map_keys). If you are using KDE, you can put them somewhere and make a link to the map_keys script in ~/.kde/Autostart in order to map keys automatically on KDE login.
Alternatively, you can run xmodmap /path/to/xmodmaprc in a X terminal and it will map the keys. I have also read that you can also rename xmodmaprc to .Xmodmap and put it in your home directory and it will be loaded on each login. However, I couldn't make this method work on gentoo, so I created that "map_keys" script.
I have had some problems mapping certain keys in the past, but I tried to fix them. If you notice that a certain key is not working, mail me and I will try to fix it. (I may have made a mistake, who knows?)
The remote control receiver is part of the keyboard. It is not seen as a separate keyboard device. The hotkeys configuration files above include all the remote buttons. (Note: The power button is not included as it sends an acpi event and does not need to be catched by X.) This method makes the remote control buttons to be keyboard buttons, so you have to configure keyboard shortcuts in your favorite application to make them work. However, this method does not allow you to use the advanced features of lirc. If you want to try to setup lirc to work with this remote, then try it and mail me if you manage to make it work.
Edit /etc/conf.d/local.start and insert a line saying the full path to the setup_keycodes script (the first script I mention above). For example, /usr/local/bin/setup_keycodes. Make sure that the setup_keycodes script is executable! Edit /etc/modules.autoload.d/kernel-2.6 (or kernel-2.4 depending on what you are running) and add a line saying this: acerhk poll=0 If you are using KDE, place the map_keys script and the xmodmaprc file in a directory of your preference (I use ~/bin) and make a link to map_keys in ~/.kde/Autostart. If you are using any other desktop environment, find yourself where these files should be placed to load automatically when you login or when the X server starts.
Edit /etc/init.d/boot.local and insert these lines:
modprobe acerhk poll=0
/usr/local/bin/setup_keycodes
(Change the path to setup_keycodes if needed. setup_keycodes is the first script I mentioned above.)
If you are using KDE, place the map_keys script and the xmodmaprc file in a directory of your preference (I use ~/bin) and make a link to map_keys in ~/.kde/Autostart. If you are using any other desktop environment, find yourself where these files should be placed to load automatically when you login or when the X server starts.
NOTE: I noticed that openSUSE 10.2 beta 1 has packages for acerhk 0.5.34. If you want, you can use them instead of compiling your own, but then you will have to change these lines in boot.local to append the force_series=4650 parameter to acerhk, like this:
modprobe acerhk poll=0 force_series=4650
/usr/local/bin/setup_keycodes
I think gentoo also has ebuilds for that driver, but as it happens with all packages in gentoo, they are outdated.
Download this script, put it in /etc/init.d and make it executable (chmod +x acerhk). Edit it, and change the SETUP_KEYCODES_PATH variable (there is a comment there to guide you) to point to the directory where the setup_keycodes script is. Now, issue these commands:
$ su
# update-rc.d acerhk defaults
If you are using KDE, place the map_keys script and the xmodmaprc file in a directory of your preference (I use ~/bin) and make a link to map_keys in ~/.kde/Autostart. If you are using any other desktop environment, find yourself where these files should be placed to load automatically when you login or when the X server starts.
When the acerhk kernel module is loaded (see the above section for instructions), you can turn on/off the mail, wireless and bluetooth leds through /proc/driver/acerhk. To do that, simply echo on > /proc/driver/acerhk/led. This command turns on the mail led. To turn it off, try echo off > /proc/driver/acerhk/led. You do not need to be root to do that. To operate the wireless led, replace "led" with "wirelessled" in the above comands. To operate the bluetooth led, replace "led" with "blueled".
To make things easier, I have written a shell script to operate the leds. Get it here. Put it somewhere in your $PATH (for example in /usr/local/bin), name it "led" and call it like this:
$ led mail on
$ led mail off
$ led wifi on
$ led wifi off
$ led bluetooth on
$ led bluetooth off
You can try to call it without parameters, to see a help message about its usage.
Note that when you light on the wifi and bluetooth leds, the hardware associated with them gets activated too. For example, echo on > /proc/driver/acerhk/blueled or led bluetooth on will both light up the led and connect the bluetooth hardware to the usb bus. Also note that the wifi and bluetooth leds are turned on/off when you press their button. The mail led, however, can only be turned on/off using the /proc/driver/acerhk interface.
Some 9110 Series models also have a 3G button/led. I bet this button won't be operational via the /proc/driver/acerhk interface, unless you patch acerhk. If you really need to get it working via the /proc/driver/acerhk interface, then you can either try to patch acerhk yourself or talk with Olaf Tauber.
|
This website is hosted for free by .
Get your own
Free Website now!
|