Panasonic Toughbook CF-29HTM50BM touchscreen problems

I cant get my touchscreen to work.
I run Kubuntu 9.10

Here is dmesg output:



[ 24.546099] input: PS/2 Touchpad as /devices/platform/i8042/serio1/input/input8
[ 24.549391] yenta_cardbus 0000:02:00.1: ISA IRQ mask 0x0c38, PCI irq 9
[ 24.549396] yenta_cardbus 0000:02:00.1: Socket status: 30000006
[ 24.549402] pci_bus 0000:02: Raising subordinate bus# of parent bus (#02) from #04 to #07
[ 24.549414] yenta_cardbus 0000:02:00.1: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff
[ 24.549419] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3000-0x3fff: clean.
[ 24.549827] yenta_cardbus 0000:02:00.1: pcmcia: parent PCI bridge Memory window: 0xe0200000 - 0xe02fffff
[ 24.549832] yenta_cardbus 0000:02:00.1: pcmcia: parent PCI bridge Memory window: 0x40000000 - 0x47ffffff
[ 24.579065] input: LBPS/2 Fujitsu Lifebook TouchScreen as /devices/platform/i8042/serio1/input/input9
[ 24.613475] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x100-0x3af: clean.
[ 24.615100] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3e0-0x4ff: clean.
[ 24.615793] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x820-0x8ff:


Here is the related output from hal:

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/event9' (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 = 'synaptics' (string)
linux.device_file = '/dev/input/event9' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/platform/i8042/serio1/input/input9/event9' (string)

running cat /dev/input/event9 results i a load of garbled text if i touch the screen and move my finger on it.

A solution i got from a page is to make a .fdi file named 10-x11-input.fdi, and paste the following lines into a text editor and save as '/etc/hal/fdi/policy/10-x11-input.fdi'

the contents of the file is:

<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->
<!--
Pointer inputs for the Panasonic CF-72 w/ Touchscreen.Models without touchscreen do not need this file as they are automatically configured by hal-->
<deviceinfo version="0.2">
<device>
<match key="info.product" contains="LBPS/2 Fujitsu Lifebook TouchScreen">
<merge key="input.x11_driver" type="string">evtouch</merge>
<merge key="input.x11_options.Device" type="string">/dev/input/by-path/platform-i8042-serio-1-event-mouse</merge>
<merge key="input.x11_options.ReportingMode" type="string">Raw</merge>
<merge key="input.x11_options.MinX" type="string">240</merge>
<merge key="input.x11_options.MinY" type="string">220</merge>
<merge key="input.x11_options.MaxX" type="string">3900</merge>
<merge key="input.x11_options.MaxY" type="string">3800</merge>
<merge key="input.x11_options.MoveLimit" type="string">5</merge>
<merge key="input.x11_options.SendCoreEvents" type="string">true</merge>
</match>
</device>
</deviceinfo>

that does not work.

here is a list of all my *.fdi files:


./usr/share/hal/fdi/policy/10osvendor/debian-storage-policy-ignore-fixed-crypto-drives.fdi
./usr/share/hal/fdi/policy/10osvendor/15-storage-luks.fdi
./usr/share/hal/fdi/policy/10osvendor/10-input-policy.fdi
./usr/share/hal/fdi/policy/10osvendor/10-tabletPCs.fdi
./usr/share/hal/fdi/policy/10osvendor/10-cpufreq.fdi
./usr/share/hal/fdi/policy/10osvendor/10-imac-backlight.fdi
./usr/share/hal/fdi/policy/10osvendor/10-laptop-panel-mgmt-policy.fdi
./usr/share/hal/fdi/policy/10osvendor/10-fuse-permissions.fdi
./usr/share/hal/fdi/policy/10osvendor/10-dockstation.fdi
./usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi *
./usr/share/hal/fdi/policy/10osvendor/debian-x11-keymap.fdi
./usr/share/hal/fdi/policy/10osvendor/10-usbcsr-mice.fdi
./usr/share/hal/fdi/policy/10osvendor/10-rfkill-switch.fdi
./usr/share/hal/fdi/policy/10osvendor/20-storage-methods.fdi
./usr/share/hal/fdi/policy/10osvendor/10-power-mgmt-policy.fdi
./usr/share/hal/fdi/policy/10osvendor/10-sony-laptop-brightness.fdi
./usr/share/hal/fdi/policy/10osvendor/30-wol.fdi
./usr/share/hal/fdi/policy/10osvendor/20-ntfs-config-write-policy.fdi
./usr/share/hal/fdi/policy/10osvendor/10-leds.fdi
./usr/share/hal/fdi/policy/20thirdparty/25-ntfs-3g-policy.fdi
./usr/share/hal/fdi/policy/20thirdparty/20-libgpod-sysinfo-extended.fdi
./usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi
./usr/share/hal/fdi/policy/20thirdparty/11-x11-synaptics.fdi
./usr/share/hal/fdi/policy/20thirdparty/11-x11-vmmouse.fdi
./usr/share/hal/fdi/preprobe/10osvendor/10-ide-drives.fdi
./usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi
./usr/share/hal/fdi/preprobe/10osvendor/20-broken-usb-sticks.fdi
./usr/share/hal/fdi/preprobe/10osvendor/20-libsane.fdi
./usr/share/hal/fdi/information/20thirdparty/20-libmtp8.fdi
./usr/share/hal/fdi/information/10freedesktop/21-video-quirk-nvidia.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-apple.fdi
./usr/share/hal/fdi/information/10freedesktop/10-recall-battery-lenovo.fdi
./usr/share/hal/fdi/information/10freedesktop/10-ipw-rfkill-switch.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-asus.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-acer.fdi
./usr/share/hal/fdi/information/10freedesktop/10-usb-pda.fdi
./usr/share/hal/fdi/information/10freedesktop/99-video-quirk-default.fdi
./usr/share/hal/fdi/information/10freedesktop/10-sony-bluetooth-switch.fdi
./usr/share/hal/fdi/information/10freedesktop/10-recall-battery-gateway.fdi
./usr/share/hal/fdi/information/10freedesktop/10-modem.fdi
./usr/share/hal/fdi/information/10freedesktop/10-laptop-panel-hardware.fdi
./usr/share/hal/fdi/information/10freedesktop/10-scanner.fdi
./usr/share/hal/fdi/information/10freedesktop/10-iwl-rfkill-switch.fdi
./usr/share/hal/fdi/information/10freedesktop/10-camera-ptp.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-ibm.fdi
./usr/share/hal/fdi/information/10freedesktop/10-usb-card-readers.fdi
./usr/share/hal/fdi/information/10freedesktop/10-recall-battery-ibm.fdi
./usr/share/hal/fdi/information/10freedesktop/10-usb-obex.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-hp.fdi
./usr/share/hal/fdi/information/10freedesktop/10-battery.fdi
./usr/share/hal/fdi/information/10freedesktop/10-cd-dvd-burner.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-lenovo.fdi
./usr/share/hal/fdi/information/10freedesktop/10-usbcsr-mice.fdi
./usr/share/hal/fdi/information/10freedesktop/10-recall-battery-fujitsu.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-toshiba.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-misc.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-fujitsu.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-dell.fdi
./usr/share/hal/fdi/information/10freedesktop/10-usb-zip-drives.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-sony.fdi
./usr/share/hal/fdi/information/10freedesktop/10-thinkpad-rfkill-switch-bluetooth.fdi
./usr/share/hal/fdi/information/10freedesktop/10-usb-music-players.fdi
./usr/share/hal/fdi/information/10freedesktop/20-video-quirk-pm-samsung.fdi
./usr/share/hal/fdi/information/10freedesktop/10-recall-battery-toshiba.fdi
./usr/share/hal/fdi/information/10freedesktop/10-recall-battery-dell.fdi
./usr/share/kubuntu-default-settings/hal-policy-ntfs-config-write-policy.fdi
./usr/share/kubuntu-default-settings/20-ntfs-config-write-policy.fdi
./usr/share/doc/hal/examples/no-cd-media-check.fdi

* i have tried to replace this one with the 10-x11-input.fdi i mentioned, but that killed all my inputs.


My touchpad mouse does work.

there is a config program at
freedesktop.org - Software/xinput_calibrator

But trying to running that results in:
Error: No calibratable devices found.

Do anyone have any solutions ?

 

Dan,
I'm running two different H models and they both have touch.
Check out the Toughbooks and Linux post below. The basics are on page 8.
Here they are and I attribute this to 9nine9 who runs Ubuntu.

You may want to check out the Touchpad section also. These computers use the psmouse in three modes.....Touchscreen, Touchpad and keyboard. This works as above for me.
Jeff

 

The good news is that you are getting garbled input on your screen.

I had to load this file the three times I have done this. It does not come "stock".

It's covered in the step by step I sent you.

I would guess just looking at the code with two months only experience is that part about synaptics. Don't confuse this with Synaptics Package Manager.

The middle of the 50Toughbook.fdi file reads evtouch and that is what you want to have.

Kinda like this. This is from:$lshal | grep LBPS/2

Let me know either here or to save space write on the Toughbooks and Linux page.

Also if you need I reply to PM. Just go step by step and good luck to you.

Jeff

 

Have you verified that the touchscreen even works? Many of the SBC units have non-working touchscreens.

 

This line here says he is getting input from the screen.

J

 

I'm not into Linux or anything else other than Widoze (I know... I suck) I played around with it for a while but was losing hair....

Seems J could mean that he is getting input... But it could be an input error.... Just as when the touchscreen cursor retreats to the lower right corner. Does "J" mean it is working perfectly in all respects? I have no idea. What I do know is that some CF-29 models (as well as CF-18, some CF-19 and the CF-30 MK1 models) have known touchscreen issues due to an incorrect adhesive used... Or the adhesive was subjected to high heat.

This means that most PD units and other units used in the field have this issue. I would say, in my experience, that the failure rate is greater than 50% from the ones I have seen. When I buy a batch.... I buy them assuming that the touchscreen will be bad. One batch had a 75% failure rate! (And they weren't prior PD units!)

So... I would try loading a known OS (XP Pro) and verify that your touchscreen actually works according to how it was sent out.... THEN experiment with Linux...

Just my too scents....

 

Nah the J would be short for Jeff.

He has a unit worth looking at after the superfluous parts are removed.

I realize I have a short career (career can also mean out of control at high speed) in Linux as opposed to a lot of others that aren't talking.

His code is a little different from mine but based on the same system. If he had no response from the code he mentioned I would have been the first to say "you have a bad touch screen".

If the code I sent him is entered as sent he will have a working touch screen if no other issues are present.

Which again I will be the first to acknowledge is possible as much with the HTM50BM as it is possible with any high hour unit like the one I am typing on now. (which would be the Mark 4 described below) 22,000 hours would ya believe.

What 9nine9 sent to me is the top of the mark. If that don't make it work in Linux nothing will.

Respectfully submitted,.

Jeff

 

Well... Good luck... As I have said (and I know several of you have good results).... I WILL NOT buy an old SBC unit. There are also other units that I will not buy.... But when 10,000+ of them come on the market... You're gonna be all over the map... Some sellers are hiding flaws and not disclosing what they are and where they came from. Others are calling the broken touchscreens "non-touch equipped" in an effort to explain why there is no touchscreen.... Too much crap out there to wade through.... I'll use my regular sources....Thankyouverymuch....

 

I hear ya boss and understand the dilemma. But i already lost my hair so what the hey.

But it's like that broken unit I got for next to nothing being a softy I can't just write the b...std off.

And as I have stated before there is no cheap Toughbook. By the time you add a decent KB, new batt,fix the TS etc. and etc. you are up there with the real price. It's the same thing spread out over a length of time where you think you are getting a deal.

Case in point.
Cracked case HB50 $71.00 (bought it for the TS.)((couldn't stand to dump it))
Lower half H model $75.00 shipped
Backlit KB $110 shipped
And it still doesn't have it's own battery. What? $110 or so?
So for $366 we have a mediocre high hour morphodite machine.
Which would sell for what? $165.
THERE IS NO CHEAP LAPTOP.
The problem is the s.u.b. (sp) is my favorite.
And the thing I have not counted is the hourly rate for these repairs etc. I get $25.00/hour in my shop plus materials for my work. What do you get? Trust me amigo we ain't arguing.
If there is hope for Dan's unit we go for it. Otherwise bite the bullet and admit the TS is broken.
Respectfully submitted,
Jeff

 

"There are two major products to come out of University of California, Berkeley: LSD and UNIX. And we don't believe this to be a coincidence, do we?"

 

I suggest you find a copy of a little book called "What the Dormouse Said". Should be pretty cheap on Amazon. Then when you use your mouse, keyboard, monitor, and even the web, you will know just how much LSD the guys who thought up all this crap were taking. Actually, they were mostly at Stanford just down the bay.
CAP

 

I got it to work, the xserver-xorg-input-evtouch package was missing.
Everything works now.

With the dissatisfaction of
Vista, XP becoming obsolete, and the price of either of them being
inhibitive(and ridiculous); The cost of a Vista package here in Norway is 5000 NOK =759.28US$!

Linux is gaining popularity as a mainstream
operating system. Ubuntu Linux especially since it is free, and has
excellent support via web based forums.

And linux is for the most parts a GUI ( graphic User Interface ) operated system that detects 95% of all the existing hardware and installs "drivers" all by it self. You dont have to worry about viruses, trojans and other malware since all that crap is a SERIOUS pain in the a*** to code for linux. More on:
http://en.wikipedia.org/wiki/Linux_malware

 

The standing joke, even loved by many UNIX aficionados, isn't about taking Lysergic Acid Diethylamide (aka: LSD), it
is that the main proponents of UNIX (Ken Thompson) and LSD (Dr. Timothy Leary) are both UC Berkley alums.

 

I still recommend you and anyone else interested in how we got where we are relative to Personal Computing (which should actually stand for Personal Communicating) read the book.
CAP

 

Though LSD actually came from a chemist named Albert Hoffman working at Sandoz laboratories in Switzerland.

Being a new drug it was used by many universities, and showed great promise in the treatment of psychiatric disorders and ironically addiction.
Unfortunately the widespread recreational use got it a schedule 1 classification.

EDIT
Oh I see the Leary-Berkley connection you were referring to. Though I believe his use and testing coincided with his tenure at Harvard and Cambridge.

 

While What the Dormouse Said: How the Sixties Counterculture Shaped the Personal Computer Industry does sound interesting, I also recommend Triumph of the Nerds: The Rise of Accidental Empires, a three-part video written and hosted by Robert X. Cringely and originally funded by 3Com for its Public Broadcasting System (PBS) presentation in 1995. That was when I first viewed this excellent documentary.

While it was originally released for sale on VHS cassette I recently located it on DVD and added to to my collection.

Trivia words for today: "DARPA" and "ARPANET".

 

I'm from the last generation that got all of its information from the printed word well into adulthood. Its fascinating to read about the wars between the two factions at Stanford, one that could not understand why anyone would even want a monitor connected to a computer, much less a way to enter text that could be seen on said monitor, and the group that won. Contrary to popular belief, Jobs and Gates were late comers to this dynamic. Interestingly enough, most of the pioneers of the PC, as opposed to the main frame only crowd, were taking big bags of money from the defense department by day and protesting the war in Viet Nam by night
CAP

 

Yeah both Jobs and Gates got their GUI interface ideas and inspiration from people at PARC which was at that time part of Xerox. THEY invented the icon and window based GUI, the mouse, Ethernet and a few other things.
It's funny that Jobs sued Gates over copying the "look and feel" of the Mac OS considering he was "borrowing" the idea from someone else.

 

Steve Jobs: What is this? This is like doing business with a praying mantis. You get seduced, and then eaten alive afterwards?
Bill Gates: Get real, would ya? You and I are both like guys who had this rich neighbor - Xerox - who left the door open all the time. And you go sneakin' in to steal a TV set. Only when you get there, you realize that I got there first. I got the loot, Steve! And you're yellin'? "That's not fair. I wanted to try to steal it first." You're too late.
---
Bill Gates: There may be a few... similarities.
Steve Jobs: Similarities? Similarities? Try theft.
---
Steve Jobs: Good artists copy, great artists steal.
---
Steve Jobs: You're stealing from us!
---
Bill Gates: Success is a menace. It fools smart people into thinking they can't lose.
==
Pirates of Silicon Valley

 

See, that's what's wrong with movies and videos. The mouse was actually first built, out of wood, at SAIL (Stanford Artificial Intelligence Laboratory). Some of the players moved on to PARC where Gates and Jobs were allowed to steal the idea. Movies are allowed to bend the truth due to time constraints, books not so much. I did enjoy POSV, but it wasn't until years later that a friend, who was there, turned me on to that little book. If you're old enough to remember who Stewart Brand is, you'll be amazed to learn that he was one of the players in the birth of the PC. Remember, it wasn't initially about how to build a PC, it was about would computing be large groups of people sharing time on one computer or would individuals have separate computers. Xerox didn't care about Jobs and Gates because they didn't believe computers would have monitors or input devices which would allow the user to directly interface with the machine in real time. It was the guys taking acid and hanging out in the mountains behind Santa Cruz who saw the potential for using the machines to connect people for the purpose of sharing information as opposed to just doing the math for calculating the trajectory of a ICBM.
CAP
P.S. I wonder how our friend from Norway is making out with his touch screen speaking of input devices.

 

One thing to remember here: the engineers at the Palo Alto Research Center (aka: PARC), primarily Dan Ingalls, Larry Tesler, and Alan Kay, were well aware of the significance and value of their GUI development. It was the "big wigs" at parent XEROX who "didn't have a clue" (they knew copiers; not computers) and allowed this very valuable asset to "slip away", to the consternation of the PARC community and the "joy" of Steve Jobs, Steve Wozniak, and "Lisa".

 

Precisely, Larry Tesler and Doug Englebart were two of the prime movers at SAIL. They, among others, were in a large part responsible for the shift from development of huge main frames to the development of individual machines, first work stations then PCs. The point here is that they were pushing a direct, real time, interaction between humans and computers. This was a concept which was completely alien to main stream thinking at the time. Most computer developers at the time could not imagine that there would ever be any use for a computer which did not involve putting a bunch of data on cards, dropping them off at the only input terminal the computer had, and returning later to get the results printed out on fan fold paper. Gates, and to some extent Jobs, do get the credit for seeing that PCs had a future in every home and pushing to get that done. Most of these pioneers left the big universities for private industry because they couldn't get the government to fund anything but main frame development.
CAP

 

Actually, Ingalls, Tesler & Kay were all still working on a text-based columns x rows navigation concept (even with Englebart's mouse) until a woman researcher working with XEROX and PARC (D@MN... I Wish I could remember her name) suggested and laid the foundation code for the concepts of "WYSIWYG" and a bitmap screen that later became the infamous XEROX STAR OS... THESE are what made the modern GUI possible.

Jobs stole these concepts from XEROX but got bogged down in the details of how to make a Windowing OS work in Real Mode; Gates stole them from Jobs and got them to market FIRST by cheating and using "virtual real mode" concepts to keep the GUI running as a TSR in high memory that called other TSRs as applications.

The rest., as we know, is history... which of course is written by the winners, and is also why you can't find that woman's name ANYWHERE.

mnem
Primordial.

 

While in "PoSV" she is only identified as "Xerox Project Manager", my research reveals that her identity is most likely Adele Goldberg.

 

My favorite tech support story concerns PARC.
Sometime last year while I was working for a telephone tech support company who is a support partner of a certain "fruit" branded computer company. A guy from PARC was calling in wondering why his notebook was not able to print to his printer. We went through all the standard troubleshooting steps and I deemed there was no communication between the computer and printer, perhaps we should try a new cable.

He was getting quite frustrated and said it was the same issue when he tried the "other port right next to it". This made me pause and I placed him on hold while I went to the HP site to look up a manual of his printer. On the back center of his printer was one USB "B" port and on the back right, a pair of phone jacks as this was a fax printer. I got back on the line and asked as politely as I could if it was possible the USB cable was mistakenly in one of the phone jacks. He started to say something like "I know the difference betwee..." when he groaned and said "crap" or something to that effect. After plugging into the USB port his printer was recognized and printed fine. He gave me a quick thanks and hung up.

In my mind I pictured some flavor of engineering PhD baffled by his printer issue having to call a lowly Tier1 tech support guy to figure out he was placing his USB cable in a phone jack!



That incident makes me think of this particular "The Far Side" cartoon by Gary Larsen:

 

YES! THANK YOU!

Adele Goldberg is HER NAME!!!

She was ALSO responsible for the invention of the OPTICAL MOUSE... I had one of the earliest versions in my collection of dinosaur bones; it required a special mousepad with index pattern printed on it. It was far superior to then current opti-mechanical ball mouse technology, but it was discovered in short order that even users with multiple PHDs were evidently incapable of wiping down a plastic mat to keep the "palm crud" from building up and making it useless.

mnem
*Salutes Adele Goldberg*

 

It is interesting to note that "What's old is new again."

The mouse was basically a trackball inverted to run on a mousepad.

My favorite "rodentia" is the Logitech Trackman Marble.

The ball is red with a pattern of black spots for the optical sensors to read.

"Cleanliness" was never a problem.

Many said the design was poor, as the thumb does not have the dexterity of the other digits.

Mine worked quite well, Thank You Very Much!

 

hey
i still have that logitech on my main desktop i love the thing

 

I've had the more recent model :

Trackman® Marble®

for years; I'm a lefty, so I kindof needed the universal design. It's a good trackball; but nothing like my original first generation Kensington Expert Mouse. Or the one I hacked from an Atari Centipede trackball years before Kensington ever DREAMED of doing it.

I STILL have the 8-ball I used as an objective instead of the skeevy cueball that came with either...

mnem
Meeses.

 

Funny.. The story reminded me of the old Larson cartoon... "Double Your IQ or NO money back!" with the guy at the door looking at the salesman saying, "Uh... Okay!" (Sorry... I couldn't find the cartoon.)

I've had similar customers (and family members for that matter) that have tried everyone's patience and it turned out to be a simple matter that they hadn't mentioned... So you have to start out with, "Okay... Is it plugged into the wall?"

 

Reminds me of a Tech Support story:

Customer: "I have a problem with my computer"
TechSupp: "OK, Maam: what seems to be the problem?"
Customer: "My cup holder is broken."
TechSupp: "Your `cup holder'???"
Customer: "Yes, my cup holder. You know; the one that slides out when you push the button on the front." :confused2:
TechSupp: "Uh, Maam; that's your Compact Disc drive."

 

And so you say "Did you try rebooting the computer?"
"Okay..." *WHAMWHAMWHAM*
"No, sir, please stop kicking it... that will let all the magic smoke out. Do you have a 12 year old child in the house?"
"My daughter."
Good. Just hand the phone to her..."
"Hello? I'm April."
"Hi April... I'm mnem. Can you get into the network adapter properties for daddy's computer?"
"Yeah... sure. He's got his IPV4 set to 67.132.6.66... and the mask is crunk."
"Thanks sweetie... can you reset it to DHCP, and make sure port 80 is open in his firewall? And don't forget to enable Port Forwarding & NAT on his router if he has one."
"Got it. Good lord, the old man still has the default password in here... and remote config from the WiFi side. I'll have to enable Mac Address Filtering and lock that nugget down before some 8-year-old across the street pwns his butt to play WoW for free on his broadband... we're good now, I can handle it from here. DA-A-AD... did you know you still 12 months free of NORTON 360 here? I'm gonna turn it on for you..."
"Whatever you think is best, dear..."
*click*
I work H3LLDESK. Welcome to my world.

mnem
Of course, you could be doing ON-SITE...

 

I got it to work, and it worked for some time until it just stopped working.

I do have:
xserver-xorg-input-evtouch
xserver-xorg-input-evdev
/usr/share/hal/fdi/policy/20thirdparty/50-Toughbook.fdi

The configuration utility ( gksu /usr/bin/calibrate_touchscreen )
reports:
No evtouch capable device found.
i think it is related to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-evtouch/+bug/317094

 

can you run .

...to see if hal is seeing the touchscreen at all? In my case this yields:

If not found by hal it would seem to indicate a mechanical failure.

I only went through one of the lists in the bug you mentioned and the driver is evdev and they are using USB devices. I'll do some more reading after I feed the livestock.

More if and when I find it.

Jeff (good luck)

 

lshal |grep LBPS
info.product = 'LBPS/2 Fujitsu Lifebook TouchScreen' (string)
input.product = 'LBPS/2 Fujitsu Lifebook TouchScreen' (string)

so it is not hardware related.

 

I agree and disagree kind of.
hal sees my Mark 4 speaker and thinks it is merrily playing away. The speaker works, the rear jack works but no speaker in my level of hearing range. So...it sees it but something is broken. And I am still not sure it is not software related as the speaker loads muted by default every time.
I found an Ubuntu command called test touchscreen or something....... just a minute and I will find it.
That was to easy once I found it. Disclaimer: I know nothing about Kubuntu, very very little about Ubuntu, very little about Linux in general. I muddle along only researching something or reading the instructions when something goes wrong
That said I will proceed as if xinput is a usable command for you. Here goes.
For the manual

For touchscreen test I used

after I found out I needed to enter the information exactly as seen by hal.
O.K. I got the name and then

The quotes as I understand it are for devices with more than one word. The capital letters must be exactly as your $xinput list states.
If all is right with the world the cursor will jump to the left and down a line and from there on any time you touch the screen it will register a number. <Ctrl> <C> to end.
Let's see what that does.
I still have not received an answer to my post to the Linux forum as to why the cursor is in the wrong place until I <Ctrl><Alt><Backspace>. X reloads and then it is fine. You might try that after starting. Let me know if it does anything different please.

Jeff

 

You have PM

 

running cat /dev/input/event9 results i a load of garbled text if i touch the screen and move my finger on it.

xinput test "EVTouch TouchScreen"
unable to find device EVTouch TouchScreen

:~$ xinput list
"Virtual core pointer" id=0 [XPointer]
Num_buttons is 32
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is -1
Max_value is -1
Resolution is 0
Axis 1 :
Min_value is -1
Max_value is -1
Resolution is 0
"Virtual core keyboard" id=1 [XKeyboard]
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"AT Translated Set 2 keyboard" id=2 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Power Button" id=3 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Video Bus" id=4 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Power Button" id=5 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Panasonic Laptop Support" id=6 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Macintosh mouse button emulation" 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
"PS/2 Touchpad" 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
"USB OpticalWheel Mouse" id=9 [XExtensionPointer]
Type is MOUSE
Num_buttons is 7
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

And yes, my touch-screen is enabled in BIOS.

 

Here's mine.
Are you using a USB Mouse? This reminds me of something I will have to look up.
Meanwhile if you have a mouse plugged into the USB port I suggest unplugging it on boot, seeing if the TS is recognized and then hotplugging the mouse. All the Mice are on a shared port (including Pad and Screen).
I'll see if I can find a USB mouse and see what happens.
Here goes with the output for comparison.(as it is now)

$ xinput list
"Virtual core pointer" id=0 [XPointer]
Num_buttons is 32
Num_axes is 2
Mode is Relative
Motion_buffer is 256
Axis 0 :
Min_value is -1
Max_value is -1
Resolution is 0
Axis 1 :
Min_value is -1
Max_value is -1
Resolution is 0
"Virtual core keyboard" id=1 [XKeyboard]
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Power Button" id=2 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Video Bus" id=3 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"AT Translated Set 2 keyboard" id=4 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Power Button" id=5 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
Max_keycode is 255
"Panasonic Laptop Support" id=6 [XExtensionKeyboard]
Type is KEYBOARD
Num_keys is 248
Min_keycode is 8
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
Max_value is 1024
Resolution is 1024
Axis 1 :
Min_value is 0
Max_value is 768
Resolution is 1024

 

Yes, i do use a USB mouse.
Unplugging it and pluggin it in when the system is up does not help.
Still, no TS.

 

Hi Dan,

I have a CF-29 Mk4 w/ Touchscreen calibrated on Kubuntu 10.04. It was actually pretty easy to get it all configured since this version no longer relies squarely on HAL. Are you interested in 10.04 or are you die-hard about making it work on 9.10?

 

I have tried to update it to 10.04, and the upgrade freezes up after language selection.
The system freezes up, and becomes non responsive. The screen goes black.
It also messes the system up so it becomes completely dead.


That was in april, i haven't tried to update it since.

 

Have you tried a full format, then a new full installation?

 

Yes, i did try that back in april.
It caused the same problem.

i have even tried the alternative install disc.

 

The above quote is from an article found here. Erratic Mouse Behavior with Mouse on Linux and Belkin KVM Switch This helped me get the touchpad issue figured out. Unloading and reloading the mouse driver may help. I just tried this again but left off the proto=bare part.

At the time I would try anything and as I stated it worked for the touchpad.

gives all the parameters.

FWIW
Jeff (thanks fuzzydude)

 

There's no doubt in my mind that your CF-29 has a hardware failure of some sort. What do you have plugged into all of your ports during the install? Did you check the motherboard connections? That model didn't come with Bluetooth, Wifi, WWAN, GPS and came with 512MB. How much RAM do you have installed? It could be anything from a retrofitted Wifi card half plugged in to faulty memory. After language selection the installer only does a VERY safe hardware detection and initialization. The Linux kernel just about never hangs on hardware detection and especially not with known hardware like the CF-29 of every Mk You can try resetting the BIOS to defaults but other than that, I think your options are to search out the hardware gremlin. I suspect the older 9.10 gets farther because it flat out ignores some of your hardware. Here's one I'd almost bet ya: try disconnecting the touchscreen board and I bet that Kubuntu install completes.

 

I have tried to disable it in the BIOS.

My RAM , in megabytes:
total used free shared buffers cached
Mem: 993 782 210 0 46 436
-/+ buffers/cache: 299 694
Swap: 1608 0 1608

1 gigabyte installed.

You can find more info on my hardware in the file attached.

 

To get the video working in Ubuntu 10.04, I had to add "i915.modeset=1" (without quotes) at the kernel boot line in grub because there is a kernel bug that messes up the video with any 855gm chipset. That might be the problem?

How did you get yours calibrated correctly in 10.04?? I've googled everywhere and can't seem to figure this out. Mine works perfectly on Windows so it shouldn't be a hardware issue. By default the cursor just moves about 3 inches away from wherever i happen to touch, and the left click doesn't work.

I found this on the official toughbook thread

That made the left click work but now the mouse is stuck on the bottom right of the screen. Any ideas? I have no idea where this "calibration utility" is in 10.04? Thanks

 

On 9.10 it is gksu /usr/bin/calibrate_touchscreen .
I will try the i915.modeset=1 , that is mentioned as a bug that affects a lot of computers.

 

Did you do?

This works with Mint 8. The above bit installs a touchscreen calibration utility as a GUI. Again this is in Mint 8 but also works in version 9.? of Ubuntu.
With the way they are mucking around and phasing out hal it may not be applicable for your version.
Good luck to you and keep us posted. (pun intended)
Another thought....you might check the spelling syntax etc. of 50-Toughbook.fdi against the one on post 79 in Toughbooks and Linux. 9nine9 came up with it and I have three H models running it.

Jeff