Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you look way, way back, and it may have been on another thread, I tried that last September with 2.6.17 IIRC. It caused the touchpad to switch into absolute mode, but didn't wake up the touchscreen. That may be my next move, since lifebook.c has been modified since then, but for now I'm keeping the system clean for dtor's R&D work.
There are still calibration and other usability issues, but output has been detected from the touchscreen, and the pointer moves. The touchscreen is indeed a PS2, not serial. Add a CF-29 section to lifebook.c. (Copy the entire CF-28 section, then replace "8" with "9") The final trick (for which dtor deserves all the credit) is to add i8042.nomux to the kernel command line in /boot/grub/menu.lst.
Distribution: debian with bits of everything stuck on it
Posts: 114
Rep:
nice one so that's the thread finally answered, the cf-29 touchscreen has entered the building. Thanks for the work put in, especially by Dmitry. Just have to find something non-violent to clean the finger smudges off the screen with now. Anyone have a cf-19 or 30...
Cheers,
Stan
That's great news. Maybe someone now can enter this hardware or the CF's into LQ's hardware compatibility list. I'm sure there's many others that could use this news.
The next question is what are your "InputDevice" sections in xorg.conf?
(Assuming that someone here has one that works somewhere near properly)
I just tried plugging the numbers seen in od output into the Min and Max X and Y values. That didn't work. Here is what I have currently, which may also have other problems:
I am trying this on a CF-29 now with Ubuntu 7.04. Started with fresh install of Ubuntu and then I downloaded all the items needed to recompile the kernel and the 2.6.20.7 kernel sources and the lifebook.c from dtor's link (which I then edited for the CF-29) - is this all I need to get the new lifebook.c compiled into the kernel. When I try I get an error:
drivers/input/lifebook.c: In function 'lifebook_create_relative_device':
drivers/input/lifebook.c:255: error: 'struct input_dev' has no member named 'dev'
Dtor's three patches applied cleanly here to the stock lifebook.c in the 2.6.20.7 sources. You could try that approach. Run the patches in order 01,02,03 from the top level of the source tree, e.g. ...src/linux-2.6.20.7/ with the command: patch -bp1 xxx.patch After that, add the CF-29 DMI section.
It's nice to have another CF-29 in the fray!
The biggest remaining issue here (besides learning how to use it ) is that every time I restart after hibernating the machine, the /dev/input/ list picks up additional devices for some unknown reason; the touchpad and touchscreen switch devices up to a higher numbered device, and then they don't work anymore since the xorg.conf is still trying to read from the devices which were formerly correct.
drivers/input/lifebook.c: In function 'lifebook_create_relative_device':
drivers/input/lifebook.c:255: error: 'struct input_dev' has no member named 'dev'
Should be fixed now. I also added CF-29 DMI signature.
The biggest remaining issue here (besides learning how to use it ) is that every time I restart after hibernating the machine, the /dev/input/ list picks up additional devices for some unknown reason
This should not be happening. Could you please do:
Well I am getting closer but also taking steps backward as well. I managed to get the patches applied and the kernel recompiled. I am now getting touchscreen output on my CF-29 I can see with OD /dev/input/event4 and when I tap on the middle of the touchscreen desktop I get the trash folder coming up and the shutdown options when I tap onthe top of the screen. I must have something wrong in my xorg.conf. By recompiling I managed to disable my wireless card (which worked before with Ubuntu right off the install) and I have no sound volume (although the drivers seem to be there and this was a problem before recompiling). Not too mention that the recompiling takes forever which kind of adds to the pain as well.
I guess with my limited knowledge I need what I suggested before - somebody to outline all the steps to get the touchscreen working on a toughbook CF-28/CF-29 for a specific distribution. Maybe Ubuntu was the wrong distribution to try - let me know which distro you have luck getting this going on.
I'm running Debian Etch (except for the 2.6.20.7 kernel). Did you use the kernel-package system? It's in Debian, so it should be available for Ubuntu too. It is easier than the usual build method, and produces a *.deb file that installs using dpkg. Debian uses initrd images by default, so I had to play with update-initramfs from the initramfs-tools package as well. If you had any problem with that, you would have known about it already, because the system won't boot if the initrd setup is messed up. There's some good info about building kernels here.
I finally have a working Suse 10.1 installation on my CF-28 that has a working touchscreen and a 2.6.16 kernel. It was quite a PITA, but 99% of that was my fault or ignorance. Well, maybe 100%, but this is my story and I'm telling it.
I have a couple of issues with it, but they are probably calibrating the sensitivity and configuration issues in my xorg.conf. They may just be because I had to use an old version of evtouch 0.8.0. I tried using 0.8.1,3,4, but kept getting a error in my xorg.log mentioning that my "something" was newer than the server. I will have to get back with you guys on what the actual error was, but it would cause evtouch to unload. Version 0.8.0 is approx 2 years old, so it may just be that, but I'll have to get around that error before I can use a newer version.
Anyway, I will get back with you later with details as it is 3:30am, but it IS working now.
James
Last edited by james_jenkins; 04-26-2007 at 04:31 AM.
Dumb question here... I am the proud owner of a CF-27 P III 500 mhz model CF-27LBAGHDM. I THINK it uses a PS/2 input for it's touchscreen because when I had the wrong drivers installed in Win 2k, it worked, but caused issues with the built in mouse, much like what others here are experiencing. Will these linux drivers work for me?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
so that's the thread finally answered, the cf-29 touchscreen has entered the building. Thanks for the work put in, especially by Dmitry. Just have to find something non-violent to clean the finger smudges off the screen with now. Anyone have a cf-19 or 30... 
) is that every time I restart after hibernating the machine, the /dev/input/ list picks up additional devices for some unknown reason; the touchpad and touchscreen switch devices up to a higher numbered device, and then they don't work anymore since the xorg.conf is still trying to read from the devices which were formerly correct.
