~Toughbooktalk~

ok got the button at least show up in acpi_listen. I will try to get all the steps.

1. download both Makefile and panasonic-hbtn.c from https://github.com/heiher/panasonic-hbtn

2. create directory to work in, i used toughbook.

3 copy both file to the directory you created.

4. as root make sure you install linux-headers-$(shell uname -r) (the uname is the kernel version).

5. type make

6. as root type insmod panasonic-hbtn.ko ( this may be debian distro's only).

7 type acpi_listen and press each of the buttons and each should respond now.


Now have to get scripts for each of the buttons.

[edit] corrected the spelling mistakes (I type so fast that I forget to check spelling problem from time to time, sorry).

Looking forward to it. You'll be a hero btw.

oth above is "both", yes?

Thanks,

Jeff

I was checking on this and you may need to run make as root also, I had an issue with this. Also these steps may only work in Debian based distros, that is all I have tested so far. I did these steps and the lock button (rightmost one) works now, I am looking into writing scripts for each of the other buttons and how to implement them.

scottie4442 wrote:the only problem with using xorg.conf files with the distros that do not use them any longer is when you do update then you might have to go through and edit the xorg.conf or even start over for the changes in the system, this is why I am trying to get this working with the distro the way it is setup so that update will not mess this up (I have had this happen in the past with other system that I custom configured for one reason or another).

You're right, it's no longer necessary or practical to use a single conf file. That's why, like I said in my prevous post, the proper way is to use the xorg.conf.d directories and declare your devices individually. There are two directories where this works, and they can be created if they don't already exist. The first one takes precedence over the second one. cheers.

found another piece that I edited to fit what I wanted to do, I have my script to rotate left then back to normal (left for me is with the strap, back, of the 19 to my left (I am right handed so works for me).

#!/bin/sh

# Find the line in "xrandr -q --verbose" output that contains current screen orientation and "strip" out current orientation.

rotation="$(xrandr -q --verbose | grep 'connected' | egrep -o '\) (normal|left|inverted|right) \(' | egrep -o '(normal|left|inverted|right)')"

# Using current screen orientation proceed to rotate screen and input tools.

case "$rotation" in
normal)
# rotate to the left
xrandr -o left
xinput set-prop 'Fujitsu Component USB Touch Panel' 'Coordinate Transformation Matrix' 0 -1 1 1 0 0 0 0 1
;;
left)
# rotate to normal
xrandr -o normal
xinput set-prop 'Fujitsu Component USB Touch Panel' 'Coordinate Transformation Matrix' 1 0 0 0 1 0 0 0 1
;;
esac


the sites I got this info from are as follows:

the screen rotation for cf-19
http://crunchbang.org/forums/viewtopic.php?id=36173

the script to toggle the rotation from one command:
http://forums.linuxmint.com/viewtopic.php?f=42&t=110395
(use method #1)

once I have the acpi event figured out this is the script that I will use for the rotation button, just press button and it will rotate back and forth.

[Edit} i messed up in the rotation script for the return to normal orientation. it has been fixed now. what I changed is the second "coordination transform matrix" line added a 1 to the end, this fixes the problem with calibration going off when you rotate back to normal.

That's great!!!
Thanks to the kernel module, the buttons can now be intercepted as standard input events.
The lock button is: The rotate button is: The enter button is the same as the enter key I get nothing for the soft keyboard button, though.

I can finally use my window manager's (Openbox) hotkeys to run whatever script or application for these events. Many thanks!

how did you figure out that the rotate button was x86rotatewindows. I can see the acpi codes, but my the keyboard and rotate buttons do not show up under xev (key scancode program) at all. I am looking into how to setup acpi button events to run a script, when I have figure this out I will post my results, as you can see from my post before I have the script already written, just not sure how to apply it yet. Also I am trying to figure out what I want to do with the return button, do not need a button to press enter.

xev works for me. Are you sure the little white window is in the foreground when you hit the buttons?

Since I use Openbox, it's a trivial matter to run anything I want with the front buttons. Does your desktop manager have some sort of hotkey functionality? For the return button/key, you might have to modify the source code since it now acts the same as the enter key on your keyboard.

xev works but does not show the keyboard and rotation button scan codes, I am going to figure out how to get these two buttons working and then figure out what to do with the return button.

Keyboard doesn't work for me but rotation does.