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 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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: debian with bits of everything stuck on it
Posts: 114
Rep:
You had both pad and screen working ok, or just the pad before the kernel upgrade to 2.6.17-11 ?
Also, with the dmesg output above, you didn't have an external mouse connected?
I will need to have a better look at the od command, it doesn't seem to catch all input events. A tap on the pad for a single left click doesn't get any output from it here.
Thanks for the output. Can you send me the output of lsmod, I'm using 2.6.15 and I think the module name has been changed, it may be lbps2 or something similar.
The xorg module should also be mentioned in /etc/X11/xorg.conf in the Pointer Device section, you should be able to edit that to get things working normaly (without the touchscreen). If you want, post the input device sections and I'll try and post back something. Here is mine as an example:
You had both pad and screen working ok, or just the pad before the kernel upgrade to 2.6.17-11 ?
Pad was working ok, before upgrade.
Quote:
Originally Posted by stan.distortion
Thanks for the output. Can you send me the output of lsmod, I'm using 2.6.15 and I think the module name has been changed, it may be lbps2 or something similar.
Here it goes (from my second CF-18, which do have same problem):
I have tried different things with this one (and there is now device with path experiment going on). It seems that I can put or take away almost anything in xorg.conf, but touchpad and screen are working just as bad.
Distribution: debian with bits of everything stuck on it
Posts: 114
Rep:
Quick note, try:
sudo rmmod evdev
sudo rmmod psmouse
sudo modprobe psmouse
it probably will refuse with "module evdev in use", thats where the touchscreen input is coming in. You could try and force it to unload with "sudo rmmod -f evdev" but it will probably cause a kernel panic.
cheers,
stan
Here it goes (from my second CF-18, which do have same problem):
--
PPaFin,
What are the full model numbers of your CF-18's? There are two distinctly different screens on these:
* Touchscreen PC version: 10.4" 1024 x 768 (XGA) transmissive, outdoor-readable TFT Active Matrix Color LCD
* Tablet PC version: 10.4" 1024 x 768 (XGA) transmissive, outdoor-readable TFT Active Matrix Color LCD with Digitizer
Do you happen to have a spare CF-29 lying around that you could try following my instructions earlier in this thread on? I am very interested if someone can CONFIRM that the same procedure that worked for a CF-28 will work for a CF-29. (I don't have a CF-29 to try it on yet).
Just for grins I think I may image off my CF-28 and try installing kubuntu 6.10 this weekend just to see what happens.
Do you happen to have a spare CF-29 lying around that you could try following my instructions earlier in this thread on? I am very interested if someone can CONFIRM that the same procedure that worked for a CF-28 will work for a CF-29. (I don't have a CF-29 to try it on yet).
Yes indeed I have one CF-29 with kubuntu 6.10. I could try with that almost anything, could you point out what you wishes are ?
Distribution: debian with bits of everything stuck on it
Posts: 114
Rep:
Could you send me the output of "sudo od /psaux" again please. The 000010 on line 300 should be switching to absolute, just want to check if it is a glitch or not. Can you tap the screen, then the pad, screen, pad etc around 10 or 15 times each. You can email it to me direct at stan.distortion<at_goes_here>laposte.net to save cluttering up the list. I haven't figured out haw to shrink quotes yet
Thanks a lot
Distribution: debian with bits of everything stuck on it
Posts: 114
Rep:
PPaFin, what devices do you have in /dev/input on the cf-18? The same as the cf-29? I'm reading through the kernel mailing lists, the intention was to have 2 separate devices for the screen and the pad. If it was implemented and is loading properly there should be at least one extra device node in /dev/input
cheers
Distribution: debian with bits of everything stuck on it
Posts: 114
Rep:
Thanks for the output. It will be hard to see what is happening with just the od command, the line shows 8 byte and the mouse communicates with 3, so you need 2 to 3 signals before anything shows up.
"od -tx1 -vw3 /dev/psaux" would give a better idea of what is happening but it still needs to be converted from hex (octal with just od) to binary to see what is actually happening. If you set a scientific calc to oct, paste the blocks in and switch to bin you will see the signal. It starts at 100471 above, the next 2 blocks are for the position, then repeats again. The last bit is always 1 which should mean "left mouse button pressed". The only exception above was the 000010, in the output you sent me there are a few more but no positive "switch output here" signals. 3 and 4 (count back from 8 on the right, the first 8 are a repeat of the previous position signal) are showing something but they should also be for the position.
I wrote a few scripts to separate and convert everything, will do a few more to separate each bit and translate the known signals over the weekend. Just hoping all the input gets to /dev/psaux and doesn't get filtered by the driver.
If you do "uname -a" and send me the output, I can recompile the lifebook module to get your touchpad acting normally again. As for a fix, looking at the lifebook module I don't think it will be simple. It looks like once it is loaded it is stuck in absolute, the idea of having 2 separate nodes looks better from here.
Cheers,
Stan
Distribution: debian with bits of everything stuck on it
Posts: 114
Rep:
Have the psmouse module compiled for 2.6.17-11-386 without cf-18 support. It should make the touchpad usable again, just need somewhere to upload it to. Run "modinfo psmouse" and make sure it matches "2.6.17.11 preempt mod_unload 486 gcc-4.0", if not I can re-compile for whatever is listed there.
Cheers,
Stan
Distribution: debian with bits of everything stuck on it
Posts: 114
Rep:
Bit more info that may be of use to anyone else looking at this: http://www.fujitsu.com/downloads/MIC...-0559-v044.pdf
About half way down are the byte sequences, below that are the commands.
The important part seems to be on page 17, when the panel it touched bit 2 of the first byte is set to 1. When released it is set to 0. Bit 3 is always set to 0.
These 2 bits are opposite to the ps2 mouse specs where bit 2 is set to 0 and bit 3 is set to 1.
From everything I have looked at from the /dev/psaux output, bit 2 is 0 and bit 3 is 1 as per the ps2 specs. Bit 0 is unusual as it is almost always set to 1 ie. left mouse button pressed.
I think either the specs for this controller are different to other Fujitsu controllers or bit 2 and 3 are being set by the psmouse module.
The lifebook part of the psmouse module seems to look for the Fujitsu spec for bit 3 here: http://www.gelato.unsw.edu.au/lxr/so...lifebook.c#L76
It is switching to absolute mode yet bit 3 is always 1 in the output,
I'm learning a lot trying to figure this out, but it is over my head. If anyone could help out and shed some light on this I would appreciate it.
Thanks,
Stan
This has been great work from Stan so far. He pointed out the problem in lifebook.c and as I downloaded 2.6.20 kernel version and did modification to lifebook.c file before compiling, I got results!
So far I have refreshed my ability to compile kernel and got my CF-18 working with pad. Looking also forward to see this issue resolved in future, I can offer testing with our various Toughbooks.
This was so nice work, that I might put in some request for our latest CF-Y5 model, which do have integrated 3G/HSDPA module - which you can guess is not working with linux Module is Novatel Wireless and I have also sent feedback to Panasonic and Novatel. So far there has been no response.
So, now I am back into track with this CF-18. This is nice machine with integrated GPRS and it would be shame to keep it with windows
I've been out of the loop here for a while. It seems that LQ didn't send me a notice of new traffic on this thread...
My CF-29, which does have a touchscreen that I have no reason to think was not factory installed, but I can't be sure since I bought it used, reports under dmidecode as:
Code:
System Information
Product Name: CF-29HWLGZBM
Base Board Information
Product Name: CF29-3
My try at kernel source hacking last fall was indeed to simply add:
into /usr/src/linux-2.6-2.6.17/drivers/input/mouse/lifebook.c . Of course, I have now upgraded to 2.6.18, so I'll have to update the kernel source before I can try it again... but either "CF-29" or "CF29" would work. While researching last fall, I ran across some discussion on the subject, and the people who put that into the kernel code were also lamenting about the crudeness of the method.
James asked:
Quote:
Do you happen to have a spare CF-29 lying around that you could try following my instructions earlier in this thread on? I am very interested if someone can CONFIRM that the same procedure that worked for a CF-28 will work for a CF-29.
I do, in fact, although I wouldn't call it "a spare" One question first though; James- what kernel version are you using? I ask because IIRC 2.6.17 was the first one which shipped with the lifebook driver included, so any fix that worked for versions <2.6.17 would likely need to be modified for later ones.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
