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.
james_jenkins post with with everything needed to get the touchscreen working with a 2.4 kernel is in another, clearer thread here: http://www.linuxquestions.org/questi...36#post2664436
The same results can be got with a recent 2.6 kernel but it requires a re-compile of the psmouse module for anything other than the cf-18, with the changes to lifebook.c as described by Azizcoos near the start of the thread and also above.
There are a few other changes that can be made to lifebook.c and psmouse-base.c to get more info on the signal needed to switch modes.
PPaFin, glad you got what you needed sorted out, even if it is the opposite of what most of this thread was looking in to. Fits the title though For the 3G card, there may already be another thread for it but these 2 links claim it works 100% : http://mybroadband.co.za/vb/showthread.php?t=21726 http://wiki.clug.org.za/wiki/3G_card_on_Linux
Could james_jenkins either post or mail the output of "od /dev/psaux" when switching between pad and screen. The output from the 2.4 kernel should make it much easier to check if the screen is using exactly the same controller as the lifebook.
Thanks,
Stan
Last edited by stan.distortion; 03-10-2007 at 09:41 PM..
Could james_jenkins either post or mail the output of "od /dev/psaux" when switching between pad and screen. The output from the 2.4 kernel should make it much easier to check if the screen is using exactly the same controller as the lifebook.
Thanks,
Stan
PPaFin, glad you got what you needed sorted out, even if it is the opposite of what most of this thread was looking in to. Fits the title though
You're right. I am certainly looking also to touch configuration, but I need pad working for those experiments
Quote:
Originally Posted by stan.distortion
For the 3G card, there may already be another thread for it but these 2 links claim it works 100% :
Thanks, first one was pcmcia version. Toughbook CF-Y5 has integrated 3G/HSDPA module, so second seems to be more for that. In my early tests, I got serial connection to module with speed 213kpbs and 115kbps with minicom, but I began to think that if module can download up to 3.6MBit/s, is this serial speed a limiting data transfer?
Distribution: debian with bits of everything stuck on it
Posts: 172
Thanked: 0
james_jenkins, thanks for the output, its just what I was looking for. Firstly, there is no switching bit. The good thing is there is a bit registering "untouched" at 110044, 120201, 120255, 130005 and 130162. It is a 0 on the 6th bit from the left, on all the all the others it is set to 1 which fits in with both fujitsu's info and all the previous working drivers.
With the differences in the output for the cf-18 from PPaFin, either the screen controller is different (unlikely) or the output is being altered by the psmouse driver.
For now it should be possible to do a cludge on the lbtouch driver to switch modes when this bit is seen. It would result in:
a: the driver switching modes when either the pad or screen are touched. (annoying but kind of usable)
or b: getting stuck in relative mode as it is looking for a different switch to change it back to absolute (should be the 5th bit from the left)
Hopefully it would be the second as the first would be nearly impossible to write a driver for. With the second it wont be simple to do as the driver has to unload and reset the controller for each touch, all the info so far says this is slow.
It would be simpler to try this with the 2.4 kernel first as the output from od seems to be more accurate and the lbtouch driver doesn't need a kernel module, it is in user space. I'll try and do something with the lbtouch driver later, its above my programing skills though.
JettCRX, if the offer is still open could you post?
Cheers,
Stan
Distribution: debian with bits of everything stuck on it
Posts: 172
Thanked: 0
I have had some trouble with links recently too, the shortened link is coming up instead of the full address. Add the http://www. part:
geocities.com/dt_or/tmp/lifebook-probe-last.patch.gz
The patch is for psmouse-base.c . It allows other PS/2 devices to load before the lifebook touchscreen is identified.
If I keep adding my 2c the bank will be calling me up.
IMHO the driver needs to be set to wait for a change in resolution when the screen is released (the 6th bit from the left of byte 0 normally used for the middle button). According to the Fujitsu info this will reset the controller to relative mode awaiting a resolution setting or the input to switch to absolute mode followed by a (useless) resolution setting.
When the controller is in this state it will still give output but is waiting for a command. I am guessing here but I expect the output to include either the 5th bit set if the pad is touched to switch to relative or the 6th bit set if the screen is touched to switch to absolute as confirmed for the cf-28 by James's output with the 2.4 kernel.
It looks like this needs to be done every time the screen or pad is released to allow a change of modes for the next touch.
Cheers,
Stan
Last edited by stan.distortion; 03-12-2007 at 04:27 PM..
1. The patch is for 2.6 kernel, the tip of Linus's tree. However there weren't many changes to lifebook driver so it should work for older kernels as well. The patch should reside at:
2. Do not try to analyze data steam coming from /dev/psaux on 2.6 kernels. What you see is not a raw datastream but emulated [Explorer] PS/2 protocol reconstructed from however many input devices present in the system by the kernel. If you really need to see the raw data stream coming from a PS/2 port you need to load serio_raw module and manually bind it to approproate serio port via sysfs.
3. If you make your touchscreen work (you will most likely need the patch above to resolve issue with multiple PS/2 ports present) please send your dmidata to dtor@insightbb.com
Distribution: debian with bits of everything stuck on it
Posts: 172
Thanked: 0
Thank Dmitry. Just got my cf-28 and tried the patch, screen and pad were both in absolute mode. I'll give it a try with a 2.6.20 kernel later just to be sure.
Thanks again,
Stan
Thank Dmitry. Just got my cf-28 and tried the patch, screen and pad were both in absolute mode. I'll give it a try with a 2.6.20 kernel later just to be sure.
It is a bit of a conspiracy isn't it. I had a CF-30 in for demo and it uses the same touchscreen drivers in Windows XP as the CF-29 (at least CF-29 Windows XP Ghost image booted up and let the touchscreen work so I assume the magic code that lets the touchpad/touchscreen work should be the same for this model as for the older models). Our only hope is that if enough Toughbook models use same the sequence and using Linux on them becomes a more popular choice that somebody will figure it out for free or perhaps Panasonic will start supporting Linux on them.
I have a CF-30CT on which I am attempting to get the Touchscreen to work using RHEL WS3 (2.4.21-47). The CF-30 has a "Fujitsu Component USB Touch Panel", which is not what is on the CF-29ET's and CF-29NT's that I have.
I don't know what WinXP uses.
If anybody has a working Linux touchscreen driver for the CF-30, let me know.
I have 3 patches for PS/2 Fujitsu touchscreens that I am thinking about sending for 2.6.22 and it would be great if they receive some testing. The patches are called lifebook-*.patch and located here:
The CF-28 I would like to try your patches on has Suse 10.1 on it. It has kernel 2.6.16.21-0.25. I have imaged the drive, so all I'm out is the time I dick with it and the hour it takes to re-image if it nukes. Stan sent me a module and asked for the output of "modinfo psmouse", but my machine gave me "modinfo: could not find module psmouse". I have tried other patches in the past on this machine for the touchscreen, but not had any success. I have been assuming it was because of something that Suse was doing that was slightly "Non-Standard", but without proof one way or another, I still get unexpected errors while trying to apply patches. Needless to say, I don't end up with the expected results.
I was wondering if it was possible for you to list step-by-step how you think your patches should be applied, and recompiled through reboot. That way anyone should be able to succeed in applying them, and if I have the same issues I've had in the past, we know where things are failing on Suse, and maybe someone can assist me in getting past them.
While I succeeded in 2.4 with Slackware, I failed miserably with 2.6 and Suse. I don't mind going through the pain again, but I would like to know I have some backup this time. My end goal is having a working touchscreen under Suse.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
For the 3G card, there may already be another thread for it but these 2 links claim it works 100% :
