Yep, the touchscreen is most definately there. I actually hadn't read your last post before I replied to your message. The event numbers do tend to change, which is one of the reasons that hal exists as an intermediate layer. Also, the (EE) message that you see in your Xorg.0.log is actually normal, and is about the Intel Graphics chipset driver.
If you want something else to try, you should be able to use the evtest program to see if the device is really working. Unfortunately, it won't work while X is running, so you'll have to shut it down. running `sudo /etc/init.d/gdm stop` will shut down the X server, and should drop you to a good old fashion full screen terminal with a login: prompt.
login, and then run 'sudo evtest /dev/input/event8' You'll get some summary info, then the "Testing...(interupt to exit)" prompt. at this point, touching the screen should give you a stream of information about the events being generated by the screen.
If you are seeing that, then your touchscreen is working. If so, I'd suggest trying to figure out the max and min X and Y values reported by evtest, and plug them in to the hal file you created from my first post.
The values don't have to be exact, as long as they are close, you should be in good shape. In fact, I'd suggest subtracting about 100 from each of the min values, and adding 100 to the max.
Ctrl-C will exit evtest, and 'sudo /etc/init.d/gdm start' will restart X and take you back to the graphical login prompt.
This is too valuable to keep to myself. nine and I have been doing a little chatting on the side. Results to follow.
At least from my output generated by his input we have a Touchscreen . I'm happy 'bout that 'cause I hate to be taken advantage of. The vendor said it was touch and I took him at his word. And a person's word is their most valuable possession outside their family. Whew! where did that come from...............wud dey put in dis burgundy?
-
Almost done with dinner. The last time I checked TS was on event 7. I'll fudge that around once I get a command prompt.
Later.
J -
-
I can't believe what I have been doing.
One more time Jeff ....computers are logical if it asks for a login it wants a name not a password you idiot.
Talking to myself. -
Got there, did the test and it hangs on testing with no apparent input from the screen. Changing the last number to the touchpad (7) and it reels off a nice string of numbers.
-
nine,
What do you know about preprobe?
Do you have /usr/local/share/hal/fdi/preprobe/20thirdparty/ etc? I don't. Just wondering after reading the attached. Or does just the .fdi specify the action to hal regardless of where hal finds it?
Here's why I ask.
''Sometimes, when hal probes a device, this can cause the system to hang, panic, or otherwise behave badly. By using device information files (.fdi files), you can tell hal to ignore such devices. These files are in XML format, and should be created under /usr/local/share/hal/fdi/preprobe/20thirdparty. For example, to tell hal to ignore USB uhci controller 0, create a file /usr/local/share/hal/fdi/preprobe/20thirdparty/10-ignore-uhci0.fdi with the following contents: from h.....ww.freebsd.org/gnome/docs/halfaq
J -
Thank you.
Jeff -
And one more question before we close this out.
Is anyone using a Linux based program on a Mark 4 or 5 with Touchscreen with any success?
Thank you.
Jeff -
-
Over and over. But I'll look again. See pm.
Later.
J -
jeff:
preprobe - I didn't make any changes, and the problems you're seeing don't seem to point there. The main purpose of preprobe is to allow you to keep hal from crashing the system when probing devices. I wouldn't expect changes there to help
lshal - that output looks just about like what I get, although I don't have the output from mine in front of me right now.
it sounds like you're not getting output from evtest on the device file that's listed for the touchscreen when doing lshal. If so, that's definitely what you are going to have to fix. It indicates that the problem is either in the hardware or at the kernel level. what do you get when running lsmod?
also, make sure you've updated the system to the latest kernel version
nine -
I'll start with the kernel.I'll look it up.
Welcome back.
J -
Check this out. Out of the blue and after I ran a calibration on the desktop. What the ...is going on here. Looks like the screen is over near the kitchen stove.
J -
evtouch throws the calibration data into HAL. the min and max are set as you go around the edge of the screen, the x1-x9 and y1-y9 are correction factors for any non-linearity in various areas of the screen. x1,y1 provide the correction in the upper left, y9,y9 are the lower right, and they go left to right, and top to bottom in between:
123
456
789
it looks like you got through a calibration, but the values are way off. The x1..y9 values should be small, in the +/- 20 range.
if you did a fresh reload, all you should need to do is install the evtouch driver with apt, and put the HAL .fdi file in place, reboot and you should be good to go, although I'm beginning to suspect that there is something physically wrong with your touchscreen. I know that the later model CF-29's have a chronic problem with one of the flat cables in the touch screen, so it may be the touchscreen is there, but just not working
nine -
Yah. I been thinking the same thing after reading TouchScreen issues all over the internet.
The reaction of the H model when I stuck the Linux HD in it sorta proves the point don't it?
I did load an old Dell version of XP in the LAQ for a while yesterday. Touchscreen didn't work but they didn't seem to have a vast quantity of drivers in it so I still didn't believe the bear tracks. (If you are walking up the trail and you see bear tracks and bear scat chances are you are following a bear) (and if the scat smells like pepper spray it's pro'bly a grizzly)
So how to check hardware. I have the H here and I'm 'bout ready to dump XP from it and reload Linux. Yeah I like Linux.
Is the flat cable replaceable? I was toying with changing out flat screens between units but talked myself out of it.
Another thing...I had no joy on finding an understandable answer re: kernel's. There are later ones but the Linux folks talk in other tongues.
And another thing....it's pro'bly not an issue but the LAQ is running on all generic drivers.
I sincerely appreciate your patience and helpful information.
I have really learned a lot in chasing this thing around and hope it has helped someone else.
And another thing....I haven't heard anyone anywhere brag that their CF-29 Mark IV or V runs on Linux. (ANY TAKERS)
"preciate it man.
J -
So I know this thread ended up being *mostly* about touchscreens, but there was also a little discussion about touchpads, and the title is "toughbook and linux" so it seemed a reasonable place to discuss some things....
I have been playing both with Ubuntu (vanilla Lucid) and Mint 9 (which is really Ubuntu, I know) and was thrilled to see how many things "just work". I don't have a touchscreen, so that's not an issue for me. My touchpad was slow, and I adjust the mouse properties re:
Also, it won't wake from suspend - or perhaps the problem is that it hangs when trying to suspend. Anyone else running Ubuntu have suspend working? Did you have to configure anything to get it working?
Thanks,
Aerik -
Yah, the other day I found a Linux command to accelerate the mouse(pad). I used it and then decided it made the TP jumpy. I'll look it up again this evening. You might try Googling linux mouse accelerate. You'll find it before I do probably.
I Googled it just now and there is a lot to read.
Jeff -
Aerik -
I'm taking a look at gpointing from Synaptics. Will report.
-
I'll let you know after I re-boot.
********Re-boot and success*******
Running 3/4 throttle and low sensitivity.
$sudo modprobe -r psmouse
$sudo modprobe psmouse proto=bare (if this works then)
$sudo gedit /etc/modprobe.conf
#add to file "options psmouse proto=bare" without the quotes
#save and re-boot
See future post for Mint specific Code.(EDIT)((IN GREEN)) -
DUDE! You da man! I'm enjoying the heck out of my new, speedy pointer... ah...
I'll let you know if I find anything out about suspend - wait, does your suspend work?
Thanks!
Aerik -
Now you know how I felt when Klonsdale told me to turn the sensitivity down instead of up.
You get after the suspend issue, o.k.?
Also I got a message re:deprecated file.WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d/.
I'll work on that.
Warning: Two months ago I didn't know Linux from Ibex.
Use at your own risk. But hey it's only a computer.
Seriously: I've been looking for the newest files on some of this stuff, forgetting that I am using an "old" computer. So stuff from 2007 isn't out of the ball park.
Wheweeee look at that mouse go.
Jeff -
I found some bug reports about the suspend issue - seems like it's a problem across the board problem... some folks suggest using a different kernal (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/568711). My hibernate doesn't work either.
I'll let you know if I find anything. FWIW, my linux is pretty limited too - just some basic server admin for my webserver until this.
Thanks!
Aerik -
FOR LINUX MINT 8
$sudo modprobe -r psmouse
$sudo modprobe psmouse proto=bare (if this works then)
$sudo gedit /etc/modprobe.d/psmouse.conf
#add to file "options psmouse proto=bare" without the quotes
#save and re-boot
EDIT: Return to normal by opening the file (sudo gedit) /etc/modprobe.d/psmouse.config and commenting out (#)the line that you inserted. -
Awesome, thanks for the update! I am playing with different flavors of Ubuntu - I just loaded Xubuntu which uses a different power manager app (xfce4-power-manager vs. gnome-power-manager) and hibernate (mostly) works (it opens my SD card upon resume, weird), but suspend doesn't. I've been digging a bit into how suspend actually works, and I think I'm getting warmer:
Ubuntu Manpage: pm-action - suspend or hibernate your computer
That page mentions a lot of "quirks" necessary to get different video cards to suspend and recover, so I'm going to play with that a bit and report back...
BTW, where did you find the answer about the mouse? I can't tell you how happy that makes me - I hated the slow mouse action.
Thanks,
Aerik -
I haven't got a Toughbook yet but I am looking to buy. I always run linux and sometimes dual boot windows as well. The impression that I'm getting from various threads in Panasonic forum are that either; 1) the touchscreen does not work in linux. or 2) it will work with lots of tinkering. Now if 2 is true that's fine. I always enjoy a little tinkering to get things just so, especially if I know that the computer will last long enough to make the work worth while. However if 1 is true, then I'm wondering if I should just forgo the touchscreen in favor of some other goodie. Maybe a backlit or rubberized keyboard.
So has anyone managed to get the touchscreen working in the most current version of any distribution of Linux?
Thanks,
Keith -
I am using Version 8 of Mint and TS works in two of my Mark 3's. Linux Kernel 2.6.31-14.
The hard drive that is in this unit (mark 4) when run in a mark 3 has a good touchscreen so it's not a lack of resources. Defective screen.
You don't have the TS automatically but it's as easy as 9nine9 stated in page 2 of this thread.
I'll put it all in one post eventually. Maybe today.
I booted from Linux Mint Live CD, installed to the hdd and then added the extras. It's like the search for TS drivers for XPPro only easier.
Jeff -
For clarification I did some slight editing here to the parts that confused me as I was brand new to Linux. This works in Mint 8. For the real deal wade through the mess that 9nine9 was trying to help me with starting on page two. HE knows what he is talking about. This works if your Touchscreen works. At least on the Mark 3 anyway. I may have to get another Mark 4 to test this. (Hmmmmm
there's an idea)
DO THIS FIRST:
1. get rid of /etc/X11/xorg.conf
DO THIS NEXT:
THEN DO THIS:
Jeff -
Excellent! Thanks for the response Jeff. The unit I am most leaning toward is a MK3 with a touchscreen. I'd have hated having it and not being able to use it.
Keith -
We have an Uh-Oh.
It appears we can have fast Touchpad or Touchscreen.
I just switched to a Mark 3 which has the Touchpad change and lo and behold NO Touchscreen. Popped another hdd that does not have the Touchpad change and Touchscreen is operational.
I'll work on it.
-----------------------------------------------------------------------------------
Cancel the Uh-Oh. Mostly. Change bare to any. Information of usable commands found in modinfo psmouse. Tried them all and "any" allowed both TS and TP. The TP is more sensitive than normal but not as good as when using "bare". The "problem" is that TS and TP share the psmouse port. My terminology is questionable here.
If we can find the correct language to address the bare command to the touchpad alone then we will be home free.
I'm leaving bare up on my non-touch and using any on the others.
Anyone coming in out of the blue and reading this will have a fine case of huh? You will need to read back a couple of pages.
Respectfully submitted,
Jeff -
Stand by for another Uh-Oh. I'm getting some strange reactions over here.
Doing the following yields from one to three TouchScreens and zero to one TouchPad.
Let's go slow for a bit until I figure this out.
Try from a Terminal:
Code:
dmesg | grep PS/2
and see what you get.
Let me know.
Jeff
EDIT: Return to normal by opening the file (sudo gedit) /etc/modprobe.d/psmouse.config and commenting out (#)the line that you inserted. -
Sorry, no touchscreen on either of mine (well, one is touchscreen, but nonfunctional) so I can't help... reading more about ACPI than I ever wanted to know in the quest for suspend on Ubuntu though...
Aerik -
Thought it through and came up with some ideas that I may not be able to write coherently.
In your case what you did was disable the psmouse in the kernel and then reload it again in the kernel at a different spot. Make sense?
Then the next time you re-boot/boot the following occurs.
HAL (hardware abstraction layer) loads version info from a file that I forget the name of and then reads the psmouse.config file and loads another shall we call it version. I guess that the last instance detected is the one utilized.
Hey anybody that knows what they are doing want to jump in here?
I would like a look at your "dmesg | grep PS/2 " if you get a chance.
Jeff -
Also Touchpad related. I am typing on the Amalgabook. HTM50BM top and HWQGZBM bottom.
The Touchpad is very liveable and the TS works. What I did was the HWQ had no Touchpad so I carefully removed the TP from the cracked case HTM50 and installed it on the HWQ. Of course I had to lift the palm rest cover but it was partially lifted anyway and wrinkled a bit.
This did two things.
1. The cables were reseated.
2. There was a certain amount of flexing of the TP going on during the install.
3. Make that three things....the pad was cleaned under the surrounding bezel.
The removal was done using a very sharp wood chisel....the idea being to cut the adhesive without stretching the TP or palm rest cover as would occur if a screwdriver were used for the lifting.
When I get some replacement heat sink pads I am going to try just re-seating the cables in my other units.
I stuck the TP down with no additional adhesive ..it had plenty. The half lifted palm rest was glued back down with Barge contact cement.
FWIW
Jeff -
Gork! said: ↑I would like a look at your "dmesg | grep PS/2 " if you get a chance.Click to expand...
[ 0.887015] PNP: PS/2 Controller [PNP0303:K101,FJC6001:MOU1] at 0x60,0x64 irq 1,12
[ 0.903565] mice: PS/2 mouse device common for all mice
[ 15.620098] input: PS/2 Fujitsu Lifebook TouchScreen as /devices/platform/i8042/serio1/input/input7
Funny, this is a non-touchscreen model. Must still have all the connectors and junk, but just not the actual touchscreen.
Aerik -
jeff@jeff-laq ~ $ lshal | grep PS/2
info.product = 'IBM Enhanced (101/102-key, PS/2 mouse support)' (string)
pnp.description = 'IBM Enhanced (101/102-key, PS/2 mouse support)' (string)
info.product = 'PS/2 Fujitsu Lifebook TouchScreen' (string)
input.product = 'PS/2 Fujitsu Lifebook TouchScreen' (string)Click to expand...
I've got my Linux computers set up to run the config file as discussed before the Uh-ohs mentioned a post or two back. The touchscreen works on the H models when enabled but I would rather have a good touchpad. Watch for updates if I get it figured out.
For clarity when lshal mentions psmouse it can be referring to the touchscreen, touchpad or keyboard in some apps. Do you use an external mouse? How does it respond to the config file?
Jeff -
$sudo gedit /etc/modprobe.d/psmouse.conf
#add to file "options psmouse proto=bare" without the quotes
#save and re-bootClick to expand...
If I may be so bold as to ask " How would you like a Touchscreen and a Very Usable Touchpad"? In Linux!
It's easy. (Only took four months to figure it out)sarcasm
Forget any previous modifications and do the following:
#In a terminal type:
sudo gedit /etc/modprobe.d/psmouse.conf
#add to the file: (which should be empty)((or delete the previous code mentioned earlier in this thread))
options psmouse resolution=400
#save and re-boot
Turn your mouse down in Control Panel.Click to expand...
modinfo psmouse
My TS seems to be more accurate also. You may have to tinker the number up or down to suit your system. Just remember to save re-boot for the option to become permanent.
And to undo the fix just delete the file /etc/modprobe.d/psmouse.config.
Time will tell but for now "Wah cotton-pickin Hoo". -
EDIT:
I had an idea going here but after further testing was unable to verify it so deleted the confusing part. "All of it".
At this point in Linux Mint I have one Mark 3 dead on with the TS with a rapid TP.
I'l clean the bezel on the other Mark 3 and see if I can duplicate my findings before reporting further.
J -
Sorry I can't help with the touchscreen troubleshooting - setting the psmouse resolution is working great for touchpad though. I'm still burning way too much time reading about acpi and stuff. Honestly I'm kind of lost in all the pieces, as it looks like there are layers of stuff happening, but I'm chipping away at it.
Good luck with the TS.
Aerik -
I'm sorry I dwelt on the touchscreen quite a bit. But I think the touchpad issue is more important for Linux users.
My non-touch Mark4 likes the resolution 400 also.
If I can find and modify the psmouse set-up information in whatever file it is written in then we can do away with psmouse.config altogether.
I touched on ACPI a few times in my search. Ouch.
So you changed to resolution?
Jeff -
where the heck is the calibration utility for the touchscreen!?!
-
gmgfarrand said: ↑where the heck is the calibration utility for the touchscreen!?!Click to expand...
Short version:
For the touchscreen on the CF-29 (and cf-18), you need the evtouch driver:
Code:
sudo apt-get install xserver-xorg-input-evtouchClick to expand...
The program evtouch includes the calibration utility.
O.K. this is new to this post....
I calibrate the Touchscreen and exit, then restart. No change to the previous Touch commands. HERE IT IS...[Ctrl][Alt][Backspace] restarts the desktop and the Touchscreen is right on!
Why? I'm looking into it, and have been for several days. It may be related to a recent kernel update but I think not. More on this as I get it.
So if you re-calibrate and have little or no change try the above. THEN LET ME KNOW PLEASE.I'm trying to track this down.
-
I am running Ubuntu 10.04
And it already tells me I have xserver-xorg-input-evtouch installed.
I can;t find a utility though.... -
I see your online so a couple questions. Does your TS work?
Did you play with [ctrl][alt][bksp]to see if it changed the TS?
I've gotta leave in a minute but I asked another member to ping this sight as he uses Ubuntu.
Jeff -
Touchscreen works, it's just waaaayyy off.
[ctrl][alt][bksp] doesn't seem to do anything -
Gork! said: ↑I've gotta leave in a minute but I asked another member to ping this sight as he uses Ubuntu.Click to expand...
Also, do we know for a fact that there is a calibration utility under linux? (So many linux things are driven by configuration files, it's conceivable to me that it might be more manual than we'd like...)
Aerik -
<system>< administration> <calibrate touchscreen> on my machine.
Or try this...(from 9nine9) if you haven't yet, you might also try removing/reinstalling the evtouch drivers.Click to expand...sudo apt-get purge xserver-xorg-input-evtouch
<reboot>
sudo apt-get install xserver-xorg-input-evtouchClick to expand...
or do a search for the file evtouch and let me know where it sits. I'd like to get a feel for the file system you are using.
Jeff -
Thanks Aerik
How do you search for a directory in Ubuntu? -
Hi!!
I have a Panasonic Toughbook CF-18 and I've installed Ubuntu 9.10, I have followed several guides to operate the touchcreen but it was all in vain, someone can help me?
Toughbooks and Linux
Discussion in 'Panasonic' started by SHEEPMAN!, Apr 2, 2010.