I'm using a Gateway M285-E and I'm using the fpit driver with all the patches.
I managed to get the pen to track correctly by doubling the maximum width setting in the Xorg.conf.

The only issue that's left is the messed up clicks. I discovered that by holding down the pen's right click button, the pen operated normally registering the pen taps has a left clicks. But if I release it, I get a bunch of random clicks, even if I'm not tapping.
This seems like a driver issue, not configuration. Perhaps it isn't registering the signals correctly?

EDIT:
It appears that I'm randomly getting middle clicks everywhere, even when I have right click button held. Something seems to be randomly triggering it.
Also, I'm unable to view any information using xinput. I seems that the pen isn't a device in the xinput list.

Hey all,

So after several months of using this driver as contributed by meekles (thanks again!), I'm wondering if anybody has had any luck (or good theories for success in) filtering out the jitters. I've begun to be frustrated having to rewrite a large fraction of my words. Even though I'm just making short annotations, it is painful. (For example, it just took 8 strokes and associated undo clicks in order to draw two lines across the screen in xournal.)

Would it be possible to average the postion and button status over a certain time frame, or better yet apply a signal filter to it? I think a filter is the best long term solution.

The jitters seem to be both in position and mouse click. I'm collecting some baseline data on the driver output and plan to analyze it.

I have a cx2608 and am running ubuntu 7.04. I have only gotten so far as the pen flickering around on the screen and what seems to be random clicking. (somewhat hard to tell since its flickering so much) I have followed several forum threads to install the drivers. I have used preconfiged fpit drivers, and compiled them myself (Which certainly was an ordeal). I have edited my xorg.conf as well and installed setserial and entered to necessary commands. Please help, I am an absolute noob. I am a computer enginneering student so I know a bit, but I am completely new to being a linux admin. Thanks again.

Open your /etc/serial.conf file and see what the baud rate is. 38400 is the correct baud rate, at least for my tablet.

I had the same problem with the mouse moving randomly and that turned out to be the issue.

My /etc/serial.conf is:

Thanks for the reply,

I'll try that tonight and let you know how it works out. Some one else emailed me saying the same thing so hopefully you are both right.

To know the exact entry you should put in YOUR serial.conf file on your computer and not the serial.conf file info from your prefered thread helper, do the following as root:

# dmesg | grep ttyS

It will print to screen the info you should add to your serial.conf file.

EXAMPLE: For my gateway 2720 tablet, I get the following output from the previous command.

serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

Therefore, I added this line to my serial.conf file:

/dev/ttyS0 uart 16550a port 0x3f8 irq 4 baud_base 34800

Then it works.



zetan

Thank you meekles and one_stinky_bum for your patches, and caeda for your instructions!!

I have a Gateway M285-E, and I'm running Ubuntu 7.04.

At first I followed steps 1, 2 and 4 in the first post in this thread, and used one_stinky_bum's modified ubuntu binary for fpit_drv.so and fpit_drv.la. If I do that, the pen works fine, clicking works more or less ok (although I get way too many "button press/button release" signals), but if I rotate the screen 90 degrees with xrandr, the cursor moves perpendicular to the motion of the pen.

Since I wanted to have rotation work properly with xrandr, I recompiled the driver using meekle's patches. With this version of the driver the cursor jumps to the top left corner of the screen and stays there for as long as the pen is near the screen, touching it or not. I can still use my touchpad and that works fine.

To try to diagnose what's going on, I used "xinput test TOUCHSCREEN > dumpfile" and tapped near each of the 4 corners of the screen: top left, top right, bottom left and bottom right in that order. Even though the arrow is all the time at the top left, the dumpfile for meekle's version of the driver looks pretty similar to the one using one_stinky_bum's binary.

Here is the dump for one_stinky_bum's version filtered by "fgrep button"
$ fgrep "button" fpit_dump_xy.txt
button press 3 a[0]=574 a[1]=762
button release 3 a[0]=574 a[1]=760
button press 1 a[0]=562 a[1]=725
button release 1 a[0]=556 a[1]=728
button press 2 a[0]=560 a[1]=737
button release 2 a[0]=560 a[1]=748
button press 3 a[0]=12399 a[1]=765
button release 3 a[0]=12401 a[1]=770
button press 3 a[0]=12432 a[1]=771
button release 3 a[0]=12439 a[1]=772
button press 2 a[0]=12473 a[1]=770
button release 2 a[0]=12479 a[1]=769
button press 2 a[0]=12493 a[1]=760
button release 2 a[0]=12495 a[1]=759
button press 2 a[0]=12494 a[1]=759
button release 2 a[0]=12494 a[1]=759
button press 2 a[0]=12242 a[1]=7325
button release 2 a[0]=12247 a[1]=7328
button press 2 a[0]=12286 a[1]=7348
button release 2 a[0]=12284 a[1]=7346
button press 1 a[0]=12282 a[1]=7345
button release 1 a[0]=12270 a[1]=7335
button press 2 a[0]=627 a[1]=7253
button release 2 a[0]=631 a[1]=7258

And the same thing for meekle's version:
$ fgrep "button" fpit_dump_xy_jump2.txt
button press 2 a[0]=1023 a[1]=790
button release 2 a[0]=1022 a[1]=792
button press 1 a[0]=897 a[1]=717
button release 1 a[0]=840 a[1]=740
button press 3 a[0]=841 a[1]=748
button release 3 a[0]=862 a[1]=748
button press 2 a[0]=12258 a[1]=853
button press 3 a[0]=12258 a[1]=853
button release 2 a[0]=12283 a[1]=856
button release 3 a[0]=12283 a[1]=856
button press 1 a[0]=12349 a[1]=884
button release 1 a[0]=12355 a[1]=909
button press 3 a[0]=12363 a[1]=905
button release 3 a[0]=12363 a[1]=905
button press 3 a[0]=12343 a[1]=909
button release 3 a[0]=12337 a[1]=915
button press 3 a[0]=12208 a[1]=1029
button release 3 a[0]=12212 a[1]=1047
button press 2 a[0]=12256 a[1]=7199
button release 2 a[0]=12256 a[1]=7203
button press 1 a[0]=12385 a[1]=7282
button release 1 a[0]=12397 a[1]=7294
button press 3 a[0]=584 a[1]=7292
button release 3 a[0]=614 a[1]=7287
button press 1 a[0]=629 a[1]=7250

I have never compiled a driver before, and I have almost no experience compiling software from source, so I wouldn't exclude the possibility of having made some silly mistake there.

Does anyone have any suggestions on how to diagnose what's wrong?

thanks again to all!!

Im pretty much and noob trying to cross the threshold of intermediate user,. i did the tutorial with great carefullness and believed i did everything it said. But the thing that is the problem is my serial error. when i cat dev/ttyS0 i get an input/output error, another user within this forum had the same error but the fixed it by i believe changing the port or the irq, i'm changed the port and irq sever times, i'm tried ttyS1,2,3, and still no luck. i have setserial written to with the correct stuff. i have the xorg correct reflecting my tty changes when i do setserial /dev/ttys l......... ( what caeda told kingoftheworldto do) i does nothing. when i grep|.mesg tty(something like that) i get nothing. I've tried it in debian still nothing. the tablet works in vista it's a cx2750 finepoint i have no idead what to do . If you would like me to post more info please tell me to but remember i am an ignorant noob and if idid give ednought info i'm sorry . thanks
josh

You need to be root to execute. (Did you included the # symbol in the command line...) This symbol only means that your prompt is in root mode, privileged mode. Anyway, become root and type exactly this:

dmesg | grep ttyS

If you have sudo installed, the command should be

sudo dmesg | grep ttyS

IT IS practically impossible that this command does not work on any linux system. These command and the executable they refer are part of the base system.

wish you luck,

zetan

yes i did it as root.

i just got done trying centos using the exact tutorial again. just copy paaste, no typos' i dont' know i gues si'll try ubuntu again. and be very care full can anyone give me their yahoo message id or emai or whatever so that i can have an immediate means of communication with an fpit finepoint epxerienced person if so my email is joshin472003@yahoo.com
thanks
josh

i you guys want somthing posted like an xorg.conf file just aks and i;ll get it. i've been working a tthis for over a month now, i hate vista i hate vista i hate vista i want to completely move to linux thisi s the only factor....please help . i

I did a fresh install of ubuntu (newest version as of 10/23/07) i've done all the steps, i used the drivers provided by the guy on ubuntu forums. i will now post what happens.

dmesg | grep tty does this:

[ 15.392472] hash matches device ttytd
[ 19.376000] audit(1193116629.474:3): type=1503 operation="inode_permission" requested_mask="a" denied_mask="a" name="/dev/tty" pid=5076 profile="/usr/sbin/cupsd"

here is my xorg.conf file:

josh@RAVN:~$ cat /etc/X11/xorg.conf
# xorg.conf (xorg X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Files"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "true"
EndSection

Section "InputDevice"
Identifier "Synaptics Touchpad"
Driver "synaptics"
Option "SendCoreEvents" "true"
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
Option "HorizEdgeScroll" "0"
EndSection

Section "InputDevice"
Identifier "Tablet"
Driver "fpit"
Option "Device" "/dev/ttyS0"
Option "AlwaysCore" "on"
Option "InvertY"
Option "MaximumXPosition" "12550"
Option "MaximumYPosition" "7650"
Option "MinimumXPosition" "400"
Option "MinimumYPosition" "400"
Option "SendCoreEvents"
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "stylus"
Option "Device" "/dev/input/wacom"
Option "Type" "stylus"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "eraser"
Option "Device" "/dev/input/wacom"
Option "Type" "eraser"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "InputDevice"
Driver "wacom"
Identifier "cursor"
Option "Device" "/dev/input/wacom"
Option "Type" "cursor"
Option "ForceDevice" "ISDV4" # Tablet PC ONLY
EndSection

Section "Device"
Identifier "Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
Driver "intel"
BusID "PCI:0:2:0"
EndSection

Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
Monitor "Generic Monitor"
DefaultDepth 24
SubSection "Display"
Modes "1280x768" "622x0" "0x256"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "Tablet"
# Uncomment if you have a wacom tablet
# InputDevice "stylus" "SendCoreEvents"
# InputDevice "cursor" "SendCoreEvents"
# InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection

Here the link to my pasted xorg log:
http://rafb.net/p/CIQJX976.html

here is my setserial link:
http://rafb.net/p/ljcugi27.html

i have the .xinitrc file with the indicated text.
Please help mememe

Ok, this is just my two cents,

On Ubuntu, did you install setserial before trying 'dmesg | grep ttyS'?. I ask because the setserial script you posted is an rc script and therefore run at boot time. Setserial automatically sets things for you, and this may be why the output of 'dmesg ...' returns what you get. Right now, my Ubuntu 7.04 doesn't have setserial installed and the output of 'dmesg ...' gives me useful info. Dmesg returns kernel info and what you are interested in is raw detection of devices, not the info from an already configured device.

If I am wrong or half correct, please someone rectify.

o. henley

Okay what where is exactly the file then that i am supposed to add the /dev/.............................................stuff. Cause i got nothing.

http://rafb.net/p/3Tdtug60.html


here is the link to my /bin/setserial file......it's looks kindof weird like corrupt or something. hmmmmm

Do you mean that you do not have /dev/ttyS0? Do you have serial configured into your kernel? Perhaps it should be compiled into the kernel instead of as a module? I could not get it to work as a module with 2.6.22 (and probably a couple of earlier versions).