Page 8 of 8

Re: A quest, get the CF-19 front keys working!

Posted: Fri Jul 07, 2017 10:38 pm
by kode-niner
Right. Now you are at the same point I was a few days ago.

After you compile the hbtn_panasonic module and run the modprobe command, copy the ko file in

Code: Select all

/lib/modules/`uname -r`/kernel/drivers/input
then run this to update the kernel dependencies

Code: Select all

depmod -ae

Re: A quest, get the CF-19 front keys working!

Posted: Fri Jul 07, 2017 11:10 pm
by SHEEPMAN!
That's copy the file "into" not in correct?

And the ko file is in the area extracted before???o.k. I found it.

Not making complete sense but we're good so far. This is my edge of knowledge we are teetering on.

Oh and uname -r is used as is? yes? (btw it's 3.16.0-4-686-pae)

--------------------------------------------------------------------
Now where is xset? Command not found, I'll get it in a second. :D

Re: A quest, get the CF-19 front keys working!

Posted: Fri Jul 07, 2017 11:29 pm
by SHEEPMAN!
Looks like I need to set a Wacom Tablet Area.......If it ain't one thing it's another. (scratching head)

xsetwacom was in xserver-xorg-input-Wacom

Re: A quest, get the CF-19 front keys working!

Posted: Fri Jul 07, 2017 11:57 pm
by SHEEPMAN!
That's enough for one day.

Re: A quest, get the CF-19 front keys working!

Posted: Sat Jul 08, 2017 5:39 am
by kode-niner
SHEEPMAN! wrote:That's copy the file "into" not in correct?
Yes, into the directory. It was getting late and I'm not on the left coast. ;)
SHEEPMAN! wrote: Oh and uname -r is used as is? yes? (btw it's 3.16.0-4-686-pae)
Yes, `uname -r` with the accent characters before the u and after the r. It's a way to pass the output of one command inside arguments to another. But if you know the kernel version and the directory is 3.16.0-4-686-pae then that works too. The whole ` ` thing is useful in scripts.

When you try out my instructions for calibration, keep in mind that I had to try multiple times to get values that looked correct. Yours should be close to mine. If you get numbers in the tens of thousands or in the negatives, just try again until they look more reasonable because for some reason they sometimes come out all wrong. So far I haven't found a better way to supply calibration numbers to xsetwacom than to use xinput_calibrator. My /etc/X11/Xsession.d/10-wacom file's contents looks like this:

/usr/sbin/xsetwacom --set "Wacom ISDv4 93 Finger touch" Area 207 17 4008 3800