Toughbooks and Linux

TO SUMMARIZE THIS THREAD.WORKS ON #! Crunchbang Linux
1.FOR TOUCHSCREEN SEE #79 FOR TOUCHPAD SEE #88. IF ON A MARK 3 #79 SHOWS NO RESPONSE "YOU MOST LIKELY HAVE A DEAD TOUCHSCREEN"
2. THERE IS SOME VERY GOOD INFORMATION BY 9NINE9 STARTING ON PAGE TWO.
3. THE TOUCHSCREEN INFORMATION HERE WORKS ON MARKS 2,3 and 4.
4. PAGE 7 TOUCHPAD SENSITIVITY ISSUE. BREAK-THROUGH.

Finally got it downloaded and I got wireless about ten minutes ago.

Who's the Linux expert here?

I'd like to have touch screen back.

The touch pad is way slow even on highest settings. Driver?

Got tired of M'sft telling me what to do and I have always wanted to play with Linux.

It's Mint by the way and I do like the look of the desktop. Now if I could figure out what to do with it.

This is on my stock so far CF-29LAQGZBM. The backlit keyboard works fine and the space between keys seems to help my hunt and peck style with my big hands.

Any leads on the touch issues would be appreciated.
Laptop Forums and Notebook Computer Discussion
Jeff
May have to apologize for starting this thread. Tell you later. My problem was not asking the right question in a search. So I am here now. CF-28 Touch Screen Installation with Recent Linux Distributions

 

What flavor of Linux are you using?

 

I have Mint as well, there were some who were trying but so far no one has been able to get the touchscreen working with any flavor of linux. Search the threads from about 6 months ago. I am trying to get Viking, which is a GPS mapping software, to talk with my GPS engine, so far no luck, but will try some more when I have time.

 

If I would only read and understand.

When I first read through it I thought you were talking about the CONDITION!

 

Yeah try doing a search for anything with Mint and Toughbook and see what you get.

Is there an alternate driver for the touch pad? I would be fairly happy with that and am re-learning keyboard commands.
That mouse is bad for carpal tunnel and it's outside the Toughbook.
By the by I did read and "mess" with the post by Modly. Still working on that.
The saga continues. My goal? Equipping the LAQ with totally freeware. I don't believe someone should work for nothing and am not opposed to a gratuity here and there but M is out of the pcture for this unit.

 

Learnig to search a little better??? I am gone to here now. http://forum.notebookreview.com/showthread.php?t=369483&highlight=linux+mint

Jeff

 

What is your touchpad doing? Mine works fine right out of the box with Mint, I have not installed any driver software, though I suppose I should use Wine to install the hotkey driver, but have just not gotten around to it yet. I know what you mean by MS. I love Windows 7 but refuse to pay such an exorbitant price for a product that at most is not worth more than $50.00. If MS would follow that logic then they would not have to spend so much time and energy trying to keep people from making illegal copies of it, but what do I know.

 

That is the thread I was referring to....I am just not fluent enough to help, but on the other hand I might figure it out by accident.

 

I might try to search the Linux Mint forums to see if anyone on there might have found out how to make a touch screen work.

 

Just went through a small! update. Rolling again now.
My pad is verrrrry slow and insensitive.

 

Ok, I know what you are talking about, mine drags a bit as well, I think that there is a way to adjust it but it has not been enough of a bother to deal with.

 

Ok, solved the touchpad problem, click menu, then click control center, scroll down to mouse, click mouse, set pointer speed to fast and sensitivity to low and that should make your touchpad more responsive, then adjust to your liking.

 

Klonsdale Mate,

You have made my day! Did't make sense to me to do that but now I see I think.

Jeff

 

Tried loading the hot key driver for XP using Wine, no joy. I also tried the same with the touchscreen driver, no joy.

 

Had a little fun last night this morning wee hours. Attempting to fool with the touch screen and no access allowed via sudo. Reloaded Mint three times so far 'cause I thought I messed the password up. Seems like we have three passwords on board. Grub, Admin, User.
After three days you would think I knew everything about Linux.
The saga continues.
What's your take on GPS via Linux?

Jeff

 

For the touchscreen on the CF-29 (and cf-18), you need the evtouch driver:

Code:

sudo apt-get install xserver-xorg-input-evtouch

unfortunately, the touchscreen calibration software doesn't work, you'll have to do the calibration by hand. Google has a bunch of help for how to do that

 

Nine,
In the nick of time. I've been reading and using some of your earlier posts. Be right back.

O.K. followed your post.
The only change was in rebuilding dependency key. It already saw the file.
Restart.
On opening, the password manager came up saying the touch screen calibration tool required a password. That's new.
Then it said no evtouch device found am I sure I have one.
Another step.
Tinker,tinker, tinker.
Thanks.
Jeff

Dummy.....I clicked the button to place calibration on the start up menu.

 

As far as GPS goes, most linux GPS applications use gpsd to talk to the GPS receiver. It allows multiple apps to get GPS data at the same time, and isolates the applications from the specific GPS formats. To install:

Code:

sudo apt-get install gpsd gpsd-clients

it should come up with a configuration dialog. for my internal GPS, the device is /dev/ttyS1

the command 'cgps' should give you a quick overview of your gps status, so you can verify everything is working right.

Not too up on the linux GPS applications. The last time I looked, the biggest issue was getting the data. For Topo data, there is now Topoquest.com, which has USGS DRG's (digital versions of the 1:24K Quads) for free download.

Hotkeys. if your hotkeys are not working, make sure the panasonic_laptop kernel module is installed:

Code:

nine@cf29:~$ lsmod | grep pana
panasonic_laptop        5468  0 
nine@cf29:~$

if it's installed, your hotkeys should be working. If it's not installed:

Code:

sudo modprobe panasonic_laptop

should do it

 

Still showing no evtouch screen error message.
Any insight?
Thanks for all the above.
I entered a couple of suggested lines of code and have been going through that to see if it lights any lights upstairs.
As logical as computer's are I probably don't have a evtouch display.
Jeff

 

ok, so I got the calibration thing figured out.
it's actually fairly easy:
1. get rid of /etc/X11/xorg.conf

Code:

sudo mv /etc/X11/xorg.conf /etc/X11/xorg.conf.bak

2. create the file /usr/share/hal/fdi/policy/20thirdparty/50-Toughbook.fdi with the following contents:

Code:

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->

<deviceinfo version="0.2">

  <device>
    <match key="info.product" contains="LBPS/2 Fujitsu Lifebook TouchScreen">
      <match key="info.capabilities" contains="input">
         <merge key="input.x11_driver" type="string">evtouch</merge>
         <merge key="input.x11_options.reportingmode" type="string">raw</merge>
         <merge key="input.x11_options.emulate3buttons" type="string">true</merge>
         <merge key="input.x11_options.emulate3timeout" type="string">50</merge>
         <merge key="input.x11_options.sendcoreevents" type="string">on</merge>
         <merge key="input.x11_options.minx" type="string">310</merge>
         <merge key="input.x11_options.miny" type="string">280</merge>
         <merge key="input.x11_options.maxx" type="string">3700</merge>
         <merge key="input.x11_options.maxy" type="string">4100</merge>
      </match>
    </match>
  </device>

</deviceinfo>

3. reboot
4. run the calibration utility, follow the directions
5. log out
6. log in
7. enjoy your calibrated touchscreen!

 

Don't go to bed yet.
Working.....................................

 

Calibrating.

 

I've done this before on XP. In regards to the tapping etc. I am only getting the first X to turn red.

?????
Made some progress though. Any thoughts?

By the way. The way the script layed out when I cut and pasted there was a space in front of the e thats hanging over to the left. I deleted the space and it looked fine.

Thank you.

J

 

is the touchscreen working before you start calibration? the calibration will be off, (hopefully not too bad), but you should be able to move the pointer around.
Not sure why you are having calibration problems. The calibration process is a bit different from the typical XP one.
when the cal screen first comes up, it's expecting you to go all the way around the edge. I do it a few times. This is just to set the min and max values on both axis'.
once you've done that, hit enter, and then the first X will turn red and you will be in the more normal poke the X's mode.

nine

 

Not working before calibration. I went around a few times. Then got the red x when I pressed [Enter] No screen reaction at all.

 

if you run 'lshal | grep LBPS', do you get entries like
info.product = 'LBPS/2 Fujitsu Lifebook TouchScreen' (string)
input.product = 'LBPS/2 Fujitsu Lifebook TouchScreen' (string)

if it doesn't give you any results, then your touchscreen is not being found by the hardware layer. did you have the touchscreen working under XP?

nine

 

Returned the same as you stated. Exactly.

Yes it worked under XP.

J

 

ok. if it shows up in HAL (the lshal command), then the system sees it.
try the command 'xinput list', you should see a section like this:

Code:

"EVTouch TouchScreen"	id=9	[XExtensionPointer]
	Type is TOUCHSCREEN
	Num_buttons is 5
	Num_axes is 2
	Mode is Absolute
	Motion_buffer is 256
	Axis 0 :
		Min_value is 0
		Max_value is 1024
		Resolution is 1024
	Axis 1 :
		Min_value is 0
		Max_value is 768
		Resolution is 1024

if you don't, then the X input driver for the touchscreen is not loading correctly. In that case, I'd check the changes made so far, especially look for typos in the hal .fdi file. You also might read through the /var/log/Xorg.0.log and see if anything pops out at you. Another thing to check is to see if HAL has the correct entries for the touchscreen. Run the command 'lshal | less', and then type '/TouchScreen<enter>' to jump to the section for your touchscreen. make sure there is an entry 'input.x11_driver = 'evtouch'' (space bar will go forward, b goes back, and q quits) if it all looks ok, you might try totally removing and then reinstalling the evtouch driver (back up the .fdi file you created, just in case it gets purged with the following)

Code:

sudo apt-get purge xserver-xorg-input-evtouch
sudo apt-get install xserver-xorg-input-evtouch

that's about all I can think of right now.

nine

 

Thanks, can't wait till my off days to try this out as well as the hot keys. Rep to you.

 

At this point returns "/TouchScreen no such file or directory."
2 inches of snow here , snowing hard, south wind I'm going to the barn if I can find my snowshoes.
It becomes clear re: the files etc. I have "no" experience with the Linux commands and I truly appreciate you teaching me some as we go along.
Later.
Jeff

 

So other interesting discussions on the internet on this subject.

http://www.linux-laptop.net/panasonic.html

http://www.linuxquestions.org/quest...anasonic-toughbook-cf-29-touch-screen-485053/

 

Jeff

What we're trying to do with the lshal command is verify that all the settings are correct. Unfortunately, just running lshal will produce about 2000 lines of output, and manually searching through that much output to find what we're looking for is no fun, especially when we can use tools to do it for us. in this case, we want to pipe the output of the lshal command to the 'less' program, which will 1)paginate the output, so we can see one page at a time and 2) let us search for specific strings in the output.

when you run 'lshal | less', you should see the first page of output from the command, and the last line will be a : and the cursor. at the colon prompt, type '/TouchScreen' and press enter. the / is the search command, and TouchScreen is what we want to search for. You should then be jumped ahead to the first match for TouchScreen in the file. at this point, you can use the following commands at the : prompt to move around in the file:
<space> - down one page
<enter> - down one line
b - up one page

I've attached that section of the hal output from my cf29 below. yours should be the same, except for the calibration section (maxx,maxy,minx,miny,x0-9,y0-9), which may be different, or missing, since you're not successfully calibrated yet.

Code:

udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input_0'
  info.capabilities = {'input', 'input.touchpad'} (string list)
  info.category = 'input'  (string)
  info.parent = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port'  (string)
  info.product = 'LBPS/2 Fujitsu Lifebook TouchScreen'  (string)
  info.subsystem = 'input'  (string)
  info.udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input_0'  (string)
  input.device = '/dev/input/event8'  (string)
  input.originating_device = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port'  (string)
  input.product = 'LBPS/2 Fujitsu Lifebook TouchScreen'  (string)
  input.x11_driver = 'evtouch'  (string)
  input.x11_options.emulate3buttons = 'true'  (string)
  input.x11_options.emulate3timeout = '50'  (string)
  input.x11_options.maxx = '3962'  (string)
  input.x11_options.maxy = '3808'  (string)
  input.x11_options.minx = '276'  (string)
  input.x11_options.miny = '306'  (string)
  input.x11_options.reportingmode = 'raw'  (string)
  input.x11_options.sendcoreevents = 'on'  (string)
  input.x11_options.x0 = '-13'  (string)
  input.x11_options.x1 = '-14'  (string)
  input.x11_options.x2 = '-3'  (string)
  input.x11_options.x3 = '-13'  (string)
  input.x11_options.x4 = '-11'  (string)
  input.x11_options.x5 = '3'  (string)
  input.x11_options.x6 = '-19'  (string)
  input.x11_options.x7 = '-12'  (string)
  input.x11_options.x8 = '2'  (string)
  input.x11_options.y0 = '-9'  (string)
  input.x11_options.y1 = '-6'  (string)
  input.x11_options.y2 = '0'  (string)
  input.x11_options.y3 = '-2'  (string)
  input.x11_options.y4 = '-6'  (string)
  input.x11_options.y5 = '-3'  (string)
  input.x11_options.y6 = '8'  (string)
  input.x11_options.y7 = '3'  (string)
  input.x11_options.y8 = '-3'  (string)
  linux.device_file = '/dev/input/event8'  (string)
  linux.hotplug_type = 2  (0x2)  (int)
  linux.subsystem = 'input'  (string)
  linux.sysfs_path = '/sys/devices/platform/i8042/serio1/input/input8/event8'  (string)

good luck in the snow

nine

 

Ok I have completed the above rebooted and ran the calibration utility, the utility comes up and tells me to run my pen around the edge of the screen and wait for the x to turn red. The screen flickers and after I run the pen around the edges it gives min and max values but nothing else happens and I can't get out of this screen unless I do a hard restart. At least I am making progress.

OK touched all the Xs and the utility exited and advised me to end session and restart. Never saw a red X. When I touch the screen the mouse pointer is about 2 inches low and left.

 

info.product = 'LBPS/2 Fujitsu Lifebook TouchScreen' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port_logicaldev_input_0' (string)
input.device = '/dev/input/event8' (string)
input.originating_device = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX_port' (string)
input.product = 'LBPS/2 Fujitsu Lifebook TouchScreen' (string)
input.x11_driver = 'evtouch' (string)
input.x11_options.emulate3buttons = 'true' (string)
input.x11_options.emulate3timeout = '50' (string)
input.x11_options.maxx = '3700' (string)
input.x11_options.maxy = '4100' (string)
input.x11_options.minx = '310' (string)
input.x11_options.miny = '280' (string)
input.x11_options.reportingmode = 'raw' (string)
input.x11_options.sendcoreevents = 'on' (string)
linux.device_file = '/dev/input/event8' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/platform/i8042/serio1/input/input8/event8' (string)

:

Here it is such as it it. Thank you for the explanation in codes etc.

Jeff

p.s. 14 inches of snow in the road out front this a.m.

 

Been reading some old posts. Took out several (hundred?) lines.

$ cat /proc/bus/input/devices

Bus=0011 Vendor=0001 Product=0001 Version=ab41
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=120013
B: KEY=4 2000000 3803078 f800d001 feffffdf ffefffff ffffffff fffffffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor=0000 Product=0006 Version=0000
N: Name="Video Bus"
P: Phys=/video/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/input/input5
U: Uniq=
H: Handlers=kbd event5
B: EV=3
B: KEY=3f000b 0 0 0 0 0 0 0

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="Panasonic Laptop Support"
P: Phys=panasonic/hkey0
S: Sysfs=/devices/virtual/input/input6
U: Uniq=
H: Handlers=kbd event6
B: EV=3
B: KEY=8000 0 0 0 0 0 1003 2000 0 104000 e0000 0 0 0

I: Bus=0011 Vendor=0002 Product=0009 Version=0000
N: Name="PS/2 Touchpad"
P: Phys=isa0060/serio1/input1
S: Sysfs=/devices/platform/i8042/serio1/input/input7
U: Uniq=
H: Handlers=mouse1 event7
B: EV=7
B: KEY=30000 0 0 0 0 0 0 0 0
B: REL=3

I: Bus=0011 Vendor=0002 Product=0009 Version=0006
N: Name="LBPS/2 Fujitsu Lifebook TouchScreen"
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input8
U: Uniq=
H: Handlers=mouse2 event8
B: EV=b
B: KEY=400 0 70000 0 0 0 0 0 0 0 0
B: ABS=3

FWIW
Jeff

 

After running your pen (or finger) around the edge of the screen (do it a few times, until the min/max values stop changing), hit enter, and the top left X should turn red

when it says end session and restart, it means log out and log back in

on my cf-18, I have to run the calibration process twice to get a good result

nine

 

jeff

what does 'xinput list' show? is there an entry for "EVTouch TouchScreen"

nine

 

_________________________________________
( While you recently had your problems on )
( the run, they've regrouped and are )
( making another attack. )
-----------------------------------------
o
o
.--.
|o_o |
|:_/ |
// \ \
(| | )
/'\_ _/`\
\___)=(___/

jeff@jeff-laptop ~ $ xinput | list
usage :
xinput get-feedbacks <device name>
xinput set-ptr-feedback <device name> <threshold> <num> <denom>
xinput set-integer-feedback <device name> <feedback id> <value>
xinput get-button-map <device name>
xinput set-button-map <device name> <map button 1> [<map button 2> [...]]
xinput set-pointer <device name> [<x index> <y index>]
xinput set-mode <device name> ABSOLUTE|RELATIVE
xinput list [--loop || --short || <device name>...]
xinput query-state <device name>
xinput test [-proximity] <device name>
xinput version
xinput list-props <device> [<device> ...]
xinput set-int-prop <device> <property> <format (8, 16, 32)> <val> [<val> ...]
xinput set-float-prop <device> <property> <val> [<val> ...]
xinput set-atom-prop <device> <property> <val> [<val> ...]
xinput watch-props <device>
xinput delete-prop <device> <property>
No command 'list' found, did you mean:
Command 'dist' from package 'nmh' (universe)
Command 'lst' from package 'lustre-utils' (universe)
Command 'hist' from package 'loki' (universe)
Command 'flist' from package 'nmh' (universe)
Command 'last' from package 'sysvinit-utils' (main)
Command 'slist' from package 'ncpfs' (universe)
Command 'klist' from package 'heimdal-clients' (universe)
Command 'klist' from package 'krb5-user' (main)
Command 'gist' from package 'yorick' (universe)
list: command not found
jeff@jeff-laptop ~ $ /EVTouch TouchScreen
bash: /EVTouch: No such file or directory
jeff@jeff-laptop ~ $

 

Oops. Wrong command.

Working..................................................

 

to quick on the reply, waiting....

nine

 

This better?

Max_keycode is 255
"PS/2 Touchpad" id=7 [XExtensionPointer]
Type is MOUSE
Num_buttons is 5
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is -1
Max_value is -1
Resolution is 1
Axis 1 :
Min_value is -1
Max_value is -1
Resolution is 1
"Macintosh mouse button emulation" id=8 [XExtensionPointer]
Type is MOUSE
Num_buttons is 5
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is -1
Max_value is -1
Resolution is 1
Axis 1 :
Min_value is -1
Max_value is -1
Resolution is 1
"EVTouch TouchScreen" id=9 [XExtensionPointer]
Type is TOUCHSCREEN
Num_buttons is 5
Num_axes is 2
Mode is Absolute
Motion_buffer is 256
Axis 0 :
Min_value is 0

 

Got to go feed a few dozen animals. BBS. (Be back soon)
Thanks for everything....still snowing.

J

 

Jeff

ok, I'm officially stumped. X seems to see the touchscreen, but not be using it. I'd take a look at the /var/log/Xorg.0.log file, and see if it has any clues. especially look for lines starting with '(EE)', as those indicate errors.

if you haven't yet, you might also try removing/reinstalling the evtouch drivers.

sudo apt-get purge xserver-xorg-input-evtouch
<reboot>
sudo apt-get install xserver-xorg-input-evtouch

make sure to back up the .fdi file you created, as the above may blow it away

nine

 

Thanks I'll try that, I know that I am close to getting it.

 

nine,
Is this supposed to be here? The Macintosh part?
dmesg |grep mouse
[ 1.730623] input: Macintosh mouse button emulation as /devices/virtual/input/input3
[ 1.770170] mice: PS/2 mouse device common for all mice

J

 

yep, that's normal (if slightly strange)

nine

 

This one hangs up in test mode indefinitely. Changing to event7 and using the touch pad results in a fine bunch of numbers which leads me to believe that i8042 is o.k.
Sudo evtest /dev/input/event8

Input device ID: bus 0x11 vendor 0x2 product 0x9 version 0x6
Input device name: "LBPS/2 Fujitsu Lifebook TouchScreen"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 272 (LeftBtn)
Event code 273 (RightBtn)
Event code 274 (MiddleBtn)
Event code 330 (Touch)
Event type 3 (Absolute)
Event code 0 (X)
Value 0
Min 0
Max 4096
Event code 1 (Y)
Value 0
Min 0
Max 4096
Testing ... (interrupt to exit)

One of many things I looked at.
cat /proc/interrupts returns: (a portion)

10: 8 IO-APIC-edge
12: 57700 IO-APIC-edge i8042
14: 27216 IO-APIC-edge ata_piix
12 is the irq specified below. Of course I don't know what any of this means but 12 does return a different number each time. The 57700 above for instance.

And FWIW here's a little tidbit from dmesg.

[ 1.185168] PNP: PS/2 Controller [PNP0303:K101,FJC6000:MOU2] at 0x60,0x64 irq 1,12
[ 1.190784] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.190791] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.190857] mice: PS/2 mouse device common for all mice

What all this means is beyond me though I suspect a problem with IRQ 12 for some reason.
One reason is a tidbit gleaned some-place that IRQ 12 causes trouble.
I suspected i8042 for a while and was interested to see it also runs a keyboard. But then recalled that the mice share a port. (make sense?)
Any takers? By the way I reloaded everything I could think of at 9's suggestion. The calibrate touchscreen device works again though I have to hard boot out of it after 1 red x.
As stated above FWIW.
Jeff

 

9
Here are a few lines for you re:ee
(II) LoadModule: "i810"
(WW) Warning, couldn't open module i810
(II) UnloadModule: "i810"
(EE) Failed to load module "i810" (module does not exist, 0)
(II) LoadModule: "vesa"
(II) Loading /usr/lib/xorg/modules/drivers//vesa_drv.so
(II) Module vesa: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 2.2.1
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 5.0
(II) LoadModule: "fbdev"
(II) Loading /usr/lib/xorg/modules/drivers//fbdev_drv.so

J

 

Pulled the Hard drive from my LAQ and stuffed it in the H model. The thing fired up and TouchScreen is almost right. A little to the left. I've been chasing my tail for days. And bothering other people too. That's what bugs me.

Thank you nine and everyone else that was amazed at my technical abilities. Yeah right.

I am very impressed that Mint didn't care what machine it was loaded into.

The good news is I am learning a little Linux code.

Again thank you all and now to find out what that error message is when I swapped the H drive into the L.

Jeff........crawling under a rock this time.

 

Jeff

That's very interesting. I have linux (I'm actually using ubuntu, but for the purposes of this problem, they are identical) loaded on a 29H and a 18D, and the instructions I gave work on both of those (although the 18 requires you to go through the calibration process twice to get a woking calibration ???). I'm wondering if there is some difference in the touchscreen hardware between the H and L models, and the newer hardware doesn't work with the evtouch driver. It's strange though that the hardware seems to identify itself identically to the operating system, even though it's not compatable. Unfortunately, I don't have a newer 29 to test with.

nine