LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Laptop and Netbook (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/)
-   -   Howto: Get your Gateway (Or Finepoint Pen) Working (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/howto-get-your-gateway-or-finepoint-pen-working-497879/)

ace214 11-28-2007 10:24 PM

OK, thanks for everyone who contributed to this and the Ubuntu topic.

I've gotten the pen to track fine, but I don't have clicking working and would like to have the pen rotate automatically. I thought that meeble's patch was added to the driver so just adding the Option "TrackRandR" would work but it doesn't so I suppose I'm going to have to patch the file?? Or is there a current SVN version of the driver that has the patches already???

Also, when I try to configure the driver source, it says
Code:

checking for XORG... configure: error: Package requirements (xorg-server >= 1.0.99.901 xproto  randrproto inputproto) were not met:

No package 'xproto' found
No package 'randrproto' found
No package 'inputproto' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XORG_CFLAGS
and XORG_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

I'm not sure where to get these packages because there are lots... Thanks for any help- really wanna get this thing working.

I'm on Ubuntu Gutsy.

jamiie 01-10-2008 04:36 AM

Fix for the random clicking
 
If anyone is still having problems with the random clicks this should help. First apply all three patches posted earlier in the thread. Then open xf86Fpit.c

Find the line that says:

/* the active pen's buttons map directly to the mouse buttons. Right-click may happen even in hover mode. */

and below it add:

else {
/* random clicks were being sent in hover mode so only allow button presses when pen is on screen */
if (~buttons & SW1) buttons=0;
/* only one button on the gateway so map it to right click */
if (buttons & SW2) {
buttons|=SW3;
buttons&=~SW2;
}

}

This will stop ANY click from registering unless the pen is touching the screen. It also maps the pen button correctly if you were getting middle clicks before. You will need to turn off 3 button emulation if you have it on, otherwise you might still get middle clicks.

wescotte 01-31-2008 05:20 PM

Poor pen design FPIT feature request
 
The gateway pen's design makes it very easy to accidentally right click and I'm looking for a way to enable/disable right click for the driver on demand. Is there a way to add this feature to the driver? or is it even easier than that? Maybe a command line app that does this?

Thanks
Eric

Caeda 02-26-2008 10:12 AM

I suppose you could use the button switching code that you type in to make right clicking work to begin with. Just set all the buttons to the first click and it wont matter what your touching. Not sure what you mean by "easy to accidently right click" though. I'm usualy pressing the right click button with my thumb as I rarely right click. When not in use, my thumbs a good 2 inches from the button? Pretty much impossible to hit by accident. Unless they changed the pen design again, just turn the pen?

ace214 04-22-2008 11:18 PM

Hate to revive an old thread but I'm trying to get my tablet working on Ubuntu Hardy. I successfully compiled the fpit module from GIT and put it in the proper directory, did the setserial stuff, put an entry in my xorg.conf and the pen doesn't work. Can anyone help me figure out what's going on? This is the exact same process I used in Ubuntu Gutsy except I used the module that was posted on UbuntuForums thread (referenced earlier in this thread). I did a fresh install of Hardy.

Caeda 04-24-2008 12:54 AM

did you install the normal apt-get available driver so that ubuntu knows where, why, and what the module is and can use and start it? Normally you would install this driver first, then copy your compiled driver over it, replacing it with the patched code.

ace214 04-25-2008 10:38 AM

Quote:

Originally Posted by Caeda (Post 3131100)
did you install the normal apt-get available driver so that ubuntu knows where, why, and what the module is and can use and start it? Normally you would install this driver first, then copy your compiled driver over it, replacing it with the patched code.

Yes, I tried that and when I get the pen near the screen, my screen turns gray and X crashes. I tried then, installing the compiled driver over the repo one and nothing works again. I'm wondering if this is perhaps an X version conflict? Perhaps I need to compile the whole X from source....

Here's the relevant info from my X log
Quote:

X.Org X Server 1.4.0.90

Release Date: 5 September 2007

X Protocol Version 11, Revision 0

Build Operating System: Linux Ubuntu (xorg-server 2:1.4.1~git20080131-1ubuntu9)

Current Operating System: Linux MobileStudio 2.6.24-16-rt #1 SMP PREEMPT RT Thu Apr 10 15:15:40 UTC 2008 i686

Build Date: 15 April 2008 05:26:17PM



(II) Loading /usr/lib/xorg/modules/input//fpit_drv.so

(II) Module fpit: vendor="X.Org Foundation"

compiled for 1.4.0.90, module version = 1.2.0

Module class: X.Org XInput Driver

ABI class: X.Org XInput driver, version 2.0



(**) TOUCHSCREEN: doesn't report core events

(**) FPIT device name: TOUCHSCREEN

(**) Fpit associated screen: 0

(**) Option "MaximumXPosition" "12550"

(**) FPIT maximum x position: 12550

(**) Option "MinimumXPosition" "400"

(**) FPIT minimum x position: 400

(**) Option "MaximumYPosition" "7650"

(**) FPIT maximum y position: 7650

(**) Option "MinimumYPosition" "400"

(**) FPIT minimum y position: 400

(**) Option "InvertY" "true"

(**) FPIT invert X axis: No

(**) FPIT invert Y axis: Yes

(**) FPIT swap X and Y axis: No

(**) FPIT Passive button mode: No

(**) FPIT RandR tracking: Yes



(II) evaluating device (TOUCHSCREEN)

(II) XINPUT: Adding extended input device "TOUCHSCREEN" (type: Fujitsu Stylistic)



(**) Option "Device" "/dev/ttyS0"

(**) Option "BaudRate" "38400"

(**) Option "StopBits" "0"

(**) Option "DataBits" "8"

(**) Option "Parity" "None"

(**) Option "Vmin" "10"

(**) Option "Vtime" "1"

(**) Option "FlowControl" "None"
Xorg.conf:
Code:

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

If I do "xinput test TOUCHSCREEN" I get lots of data so it must not be connecting to the pointer?

Caeda 04-30-2008 06:13 AM

Well, finally install hardy. Had the same problem. Oy... wish they'd quit f-ing around with the way xorg handles it's config files... Anyway. After spending my third shift day off picking around at various problems and installing everything, I did in fact get the touchscreen pen working.

What's the secret? Er, I had a xorg.conf laying around from 7.04 days on a spare hard drive, dropped it in and the blasted thing works fine now. Did have to add a "true" after the CoreEvents option.

I did not experience any problem with crashing however. That appears related to your particular pc/install.

ace214 04-30-2008 09:21 AM

Quote:

Originally Posted by Caeda (Post 3137601)
Well, finally install hardy. Had the same problem. Oy... wish they'd quit f-ing around with the way xorg handles it's config files... Anyway. After spending my third shift day off picking around at various problems and installing everything, I did in fact get the touchscreen pen working.

What's the secret? Er, I had a xorg.conf laying around from 7.04 days on a spare hard drive, dropped it in and the blasted thing works fine now. Did have to add a "true" after the CoreEvents option.

I did not experience any problem with crashing however. That appears related to your particular pc/install.

To clarify your correction, what seems to work, is NOT having the AlwaysCore option and having SendCoreEvents "true". Also, apparently you can't have any BaudRate in the xorg.conf.

Did you get right-click to work? I added the .xinitrc to my home directory and it still sends middle clicks. "xsetpointer TOUCHSCREEN" says "Extended device TOUCHSCREEN not found"

Caeda 04-30-2008 06:15 PM

I'll let you know. I do a complicated upgrade. Install. Find everything that's broken. Spend a few hours fixing it all by downloading all sorts of crap and testing and poking... (for each computer >.<) then once there's a garunteed was to zip zip it all works, reinstall and do the fast way so the file system isn't so full of crap and add ons.

Just got done with the redo. Forgot to test the click cause honestly I barely ever use it.

Caeda 05-01-2008 01:56 AM

Well, I got to really wondering just what the heck was so different about the old xorg.conf compared to what gutsy made on it's own. So, I played around a bit more with some blank configs from gutsy and feisty and added in the tablet stuff from my post and... WHAM... same bug.

So I checked what I added in to the blank against the old config to see why it was so eager to work and hey, whattya know. I left off the TrackRandr in my new config. lol.

Made an .xsession file with the options and not only did it not work, giving the same "TOUCHSCREEN" not found error, but also crashes x even if file is completely blank. heh

ninjabob7 06-01-2010 12:01 AM

I realize this is an old thread but it seemed more appropriate to add to this discussion than to make a new thread.

I just got my pen working on Slackware 13.1 by compiling xf86-input-fpit-1.3.0 with a patch I found (from Gentoo?) to make it compatible with Xorg 1.7. It tracks the pen fairly well on the Y-axis, I can click with either button, and it still works after rotating the screen with xrandr.

However, I still have two problems. First, the X-axis seems to scale wrong. When I am on the left side of the screen, the pointer is under the pen, but as I move right it gets farther away, until it hits the right edge of the screen when the pen is just over halfway across. Anything I do to the min/max values just seems to either do nothing or make it worse. Second, the right-click seems to be actually producing a middle-click. I can fix this with that xmodmap line, but then it also remaps my normal mouse buttons.

Here's the section from xorg.conf:
Code:

Section "InputDevice"
        Identifier        "Tablet"
        Driver                "fpit"
        Option                "Device" "/dev/ttyS0"
        Option                "BaudRate" "19200"
        Option                "AlwaysCore" "on"
        Option                "MinimumXPosition" "400"
        Option                "MinimumYPosition" "400"
        Option                "MaximumXPosition" "12550"
        Option                "MaximumYPosition" "7650"
        Option                "SendCoreEvents"
        Option                "InvertY"
        Option                "TrackRandR" "on"
        Option                "ZAxisMapping" "4 5 6 7"
        Option                "ButtonThreshold" "17"
        Option                "ReportingMode" "Scaled"
EndSection

I'm using a Gateway convertible, but can't find a model number. My screen resolution is 1280x768. Also, has anyone made progress on the front buttons? They don't produce anything in xev or acpi_listen.

kingofearth 06-02-2010 12:27 AM

My pen hasn't worked in over a year now. It was always pretty on and off before it stopped all together, so I had pretty much given up hope on it. But if you could point me to that patch that will make the fpit driver work with the new XOrg I would love to try it out and see if I could get it to work and hopefully fix your problem along the way.

ninjabob7 06-02-2010 03:10 PM

http://bugs.gentoo.org/show_bug.cgi?id=321175

Probably should have posted that anyway, just for future reference. Also for future reference, the sources for the fpit driver are here:
http://www.x.org/releases/individual/driver/
It still exists, but it's been removed from the main xorg packages, which gave me some trouble finding it.


All times are GMT -5. The time now is 07:23 PM.