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).
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 have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Distribution: debian with bits of everything stuck on it
There where a few questions relating to the 500mhz model further up the thread, nothing came of it though. It may be worth starting a new thread for this, this one is bloated already and quite a few folks seem to be having trouble when refering to it for configuration on cf-28 and 29's.
Can you PM me with the output of dmesg or post it in a new thread?
the whole reason I bought the thing was because I was tired of having laptops break. I wanted something indestructible...however, despite treating this laptop just like I treat my others, the power connector has broken, the CD door has broken off, the keyboard is falling apart, the touchscreen is getting distorted, and it's now on its third hard drive.
my 9-year-old step-daughter's Thinkpad, however, has been left out in the rain, dropped from a loft and down the stairs, used as a prop for the leg of a couch, and given a big drink of Mountain Dew. it's even been stepped on by a 200+ pound man when it was covered with a towel.
Little off topic, but we have had similar experiences. We field a lot of notebooks in a very rugged environment. VERY RUGGED. And the Toughbooks are usually missing keys, whereas other systems are solid. I would say there is a design flaw there. However I had drop tested the toughbook with the disk spinning, and can pick it up on use it. ALthough I did snap a hinge on the CD-ROM bay cover thing. I think there is a lot more potential for component durability with solid state hard drives making there debut. THey are pricey, but if you want to throw your laptop from a second story window, that's probably the way to go. They also run a lot cooler and draw less power, which would take the already HUGE battery life of the toughbook even further.
In any case. I just finished reading this the first time. I have the CF-18, and I noticed that samstar successfully got his working. Am I correct that this is what is needed:
use kernel 2.6.20
instal dmitry's 3 patches (do I compile anything here?)
use evdev for touchpad and evtouch for touchscreen
configure xorg.xonf appropriately
Without sufficient consideration of the consequences, I upgraded my CF-29 to Kubuntu 8.04. Naturally, that blew out the previous working configuration. The touchscreen sort-of worked out of the box afterward, but it was accelerated and not calibrated. I got Conan's evtouch-0.8.8, and followed the instructions. I had to comment out the "CorePointer" in the ServerLayout section of xorg.conf, because with that in place neither the touchscreen nor the touchpad work at all. Now the acceleration seems to be gone from the touchscreen, but the calibration is still way off and the X and Y Max and Min settings are completely ignored.
Sorry about the lost config Azizcoos,
(backup backup backup)
when I first set up my cf-72 I found a nifty little calibration program, but after searching for it for the last hour I unfortunately I can't point you at one. It appears from looking at the driver that the cf-28 and cf-29 have the same touch screen (I could be wrong), and as we will see it is the same as the cf-72, that I have. so here is my xorg.conf entry I hope it helps :
I did however upgrade my system to ubuntu 8.10 from 7.10 -fully expecting to have to re-compile the psmouse module. I downloaded the source and pulled up the lifebook.c file only to discover that it now is patched! And it has entries for more hardware dmicodes including the cf-72. This puzzled me because I had already configured the xorg.conf file hoping it would just work only to find that it still did not. So then I opened up the backup I had of the old patched lifebook.c file to compare differences.
I was shocked to discover that I had misreported my findings here in previous posts, and that the cf-72 was the same as the cf-28 and not the cf-18. And even more shocked that this somehow made it into the kernel modules without further testing.
That'll teach me to drink and drive(r hack).
Anyone know how to get word of this to the ubuntu folks?
Is this script also working for CF-29 with Jaunty?
I do not own a cf-29, but as far as I know the driver has worked for it for quite some time (no source editing necessary). That would leave configuration, which for these touchscreens must be done manually afaik. I never did get the Touchscreen configuration program in Ubuntu to work, it ran but changed nothing. The screen on the on the CF-29 is the same 13.3" one as on the CF-72, so I would wager that the config numbers are the same or nearly the same.
One other thing that I found was that the fglrx binary graphics driver conflicts with the touchscreen and must be uninstalled/blocked. Instead you must use the open source Radeon driver, no accelerated 3d. I found that this caused the same symptom you are describing.
Also you can completely replace the '/etc/X11/xorg.conf' file with a xml file for hal. Copy and paste the following lines into a text editor and save as '/etc/hal/fdi/policy/10-x11-input.fdi'
<?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
<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>
If you chose to use hal and the 10-x11-input.fdi XML file instead of xorg.conf, you will need to reboot the computer before the touchscreen is usable.
Good luck and let us know what ends up working(or not working).
I to am using Ubuntu, for a while now the inputs(keyboard & mouse/touchpad/touchscreen) and (video) outputs have been configured through hal (hardware abstraction layer). In the past these devices were configured in the /etc/X11/xorg.conf file. Now hal configures them automatically; except for the touchscreen, which is a unusual enough that we need to write an xml file describing it (the code I previously posted). This is important, but so is making certain that you are not using the fglrx binary graphics driver from ATI. You can use Synaptic (upper left menus 'System' -> 'Administration' -> 'Synaptic Package Manager')to remove the fglrx driver and make certain that the radeon driver is installed (use the search button not the 'quick search' function). Then create the /etc/hal/fdi/policy/10-x11-input.fdi as described in the previous post and reboot.
to configure the touchscreen, change the MinX MaxX MinY MaxY numbers in the /etc/hal/fdi/policy/10-x11-input.fdi file. Since you won't be able to see a change I would recommend temporarily moving or deleting this file after replacing it with the proper configuration in the /etc/X11/xorg.conf file;
# xorg.conf (X.Org X Window System server configuration file)
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# Note that some configuration settings that could be done previously
# in this file, now are automatically configured by the server and settings
# here are ignored.
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg
Identifier "Generic Keyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us
Option "XkbOptions" "lv3:ralt_switch"
Option "Device" "/dev/input/by-path/platform-i8042-serio-1-event-mouse"
Option "DeviceName" "touchscreen"
Option "MinX" "230" #"230"
Option "MinY" "220" #"220"
Option "MaxX" "3900" #"3900"
Option "MaxY" "3850" #"3850"
Option "MoveLimit" "5"
Option "ReportingMode" "Raw"
Option "SendCoreEvents" "true"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "40"
Identifier "Synaptics Touchpad"
Option "Mode" "Relative"
Option "CorePointer" "true"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Emulate3Buttons" "true"
#Option "HorizScrollDelta" "0"
Identifier "Configured Video Device"
Identifier "Configured Monitor"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Synaptics Touchpad" "CorePointer"
InputDevice "touchscreen" "SendCoreEvents"
With this file in place you will be able to log out and back in again between number changes. You will probably have to reboot once after replacing the /etc/hal/fdi/policy/10-x11-input.fdi with the /etc/X11/xorg.conf file just to get xorg off of the hal configuration and onto the xorg.conf configuration.
As for the configuartion, I would tackle one number at a time, start with minX trying to get the configuration near the left edge horizontally as accurate as possible (don't worry about vertical yet). Then move to MaxX and do the same for the right edge. Repeat for the top (minY) and then the bottom. I believe that both X numbers affect each other to some degree as do both Y numbers, so after you get MinX adjusted changing MaxX will slight unadjust it. You may have to change all of the numbers several times before it is perfect. I would recommend changing in increments of 5 or 10, leave the commented numbers there as references until you are happy with the final result of your efforts. I got it 'close enough' after an hour or so, but mine started out far worse than yours. I later came back and got it closer and it is now almost perfect. For some reason it will never be completely perfect, some areas tend to have bias. When you are happy with the numbers make a new /etc/hal/fdi/policy/10-x11-input.fdi file and rename the /etc/X11/xorg.conf file to /etc/X11/xorg.bak and reboot. At some point use of xorg.conf will be phased out, so I wouldn't recommend using it indefinitely.
Distribution: debian with bits of everything stuck on it
Nice one Quick note for future reference, the evtouch driver seems to be stagnating and is masked in gentoo:
!!! All ebuilds that could satisfy "x11-drivers/xf86-input-evtouch" have been masked.
!!! One of the following masked packages is required to complete your request:
- x11-drivers/xf86-input-evtouch-0.8.7 (masked by: package.mask)
# Rémi Cardona <firstname.lastname@example.org> (06 Aug 2009)
# Big Xorg 1.3/1.4 mask. Masked for removal Real Soon Now (tm)
# xf86-input-evtouch going out completely, switch to evdev
So may be worth reading up on evdev, I briefly tried to get it working a while ago but didn't get very far. Will post back if I do any more.
Last edited by stan.distortion; 10-08-2009 at 12:06 PM.
Reason: My keyboard can't spell
I recently upgraded my CF-29 to Kubuntu 9.10. Installed the evtouch driver and created the /etc/hal/fdi/policy/10-x11-input.fdi file. The /etc/X11/xorg.conf file has already been phased out, apparently, because it does not exist. Rebooted, and it worked! It took a couple more reboots to get the numbers tweaked, but now it is working perfectly. So add the CF-29 to the tested-working list.
If you aren't sure if your touchscreen is the same type, do
dmesg | grep LBPS
If it returns something like:
[ 26.439176] input: LBPS/2 Fujitsu Lifebook TouchScreen as /devices/platform/i8042/serio1/input/input8
I have read through this whole thread but several of the links early on do not work. I feel like I might have missed something. I am running a CF-29 and using 'evdev'. So far I haven't been able to figure out an xorg configuration that works. The touch screen was noticed by Debian right out of the box but the cursor moves faster then my finger and when I touch the screen it never lands under my finger.
I am running the latest version (of stable) Debian. At one point in this thread there was talk of starting a single thread with info on getting touchscreen to work. Did that ever happen? Any help would be greatly appreciated. I have followed so many dead end leads and this thread is by far the best info I have found.