2.6.16 is kinda old, I don't think the patches will apply, I will have to rebase them. However it is getting late here so I'll try to do this tomorrow.

Sounds like suse are building everything into the kernel instead of using modules. This howto seems to cover things well.
http://www.howtoforge.com/kernel_compilation_suse
lifebook.c is the file the patch needs applying to, so working in the directory where you have the patch stored:
patch /usr/src/linux/drivers/input/mouse/lifebook.c lifebook-02-cf28.patch
patch /usr/src/linux/drivers/input/mouse/lifebook.c lifebook-use-secondary-device.patch
Few notes on the kernel: The patch would only work ok with kernels after 2.6.18 for me, would recommend the most recent in kernel.org if you are going to the trouble of compiling the full kernel.
When configuring the kernel, build psmouse as a module (drivers, input section) so if there are further patches it doesn't mean rebuilding the full kernel.
Always keep a working kernel to boot from if things go wrong.
It is worth reading a few kernel optimisation guides as some time spent setting up the kernel configuration can make a big difference, for the first time just go with a good guide and get a feel for how it works though.
If something isn't working with your compiled kernel (ie, sound or usb), your not the first its more than likely a missing module. Opening the config file (/usr/src/linux/.config) in a text editor and doing a search is a lot quicker than trying to find it with xconfig.
The changes for the cf-18 should also work for the cf-29, they wont work for the cf-28 though. The changes for the cf-28 'should' work for all models but I'm not 100% sure.
Nothing is going to work without changes to xorg.conf, I'll post mine for the cf-28 with both patches (12" screen) later.
Cheers,
Stan

Thanks for the pointer Stan. I will review this how-to some more when it is not 1:30am, but this was what I was looking for.

I have been lucky, or unlucky, to have never had any real NEED to HAVE to recompile kernels. Not that I have never tried. I have. But I don't think I was any better off than I was before. I also found that there is NO quicker way to break a working system. I think that bottom line, I just don't know what I'm doing when it comes to the kernel. Research would indicate that I would have a different Linux experience if I knew what was going on in the kernel and could bend it to my will. Time is always an issue for me. I have several areas of expertise and they occupy most all of my time. Breaking one of my machines messing around is not a good way to end the day. That is why I have a GhostCast server and lots of spare machines. Pretty quick, I'm right back where I was.

I will give the patches a go in the next few days and let you guys know how it turns out, or if I run into any trouble. I have another CF-28 that is suppose to be delivered in 2 days. I might just wait for it since it won't be in service yet.

Thanks.
James

To true. You would not believe the trouble I have got myself in to compiling kernels in the past, mysterious disapearing USB synrome was not the half of it.
Its a pain in the neck suse is not using modules, all you would need to do is compile against the source for the kernel you are using and swap in the new module.
If you where interested in giving ubuntu or another variant of debian a try on your new system I have 2.6.20.3 compiled and packaged with the patches applied.
Section from my xorg.conf:
And further down:
Devices can be found with "cat /proc/bus/input/devices", X and Y are simple enough by trial and error. This should be quite close for a cf-28 with a 12" screen.
Cheers,
Stan

Quick note. With the cf-28 patch check line 77 for the model number by default it is "CF-28SRJGZDM", I have entering just "CF-28" here and it works fine.
Cheers,
Stan

I'm getting patch failures on 2.6.18:
The 2.6.18 source seems to be the newest available as a Debian package. Apologies in advance if this is due to my inexperience with these things.

The patches should apply to 2.6.20 (actually they were made against the latest development tree, post 2.6.21-rc5). My apologies, I keep forgetting that not everyone uses bleeding edge I will rebase patches against some older versions tonight.

I added patches for 2.6.16 and 2.6.18. Please give them a spin.

On cf-28, patches for all 3 kernels tested and working ok, same xorg config with no modifications for all.
For all 3 kernels first patch (02) applies ok with an offset, second patch (03) fails on just the first change but the change is straightforward to edit by hand.
Thanks for putting the work in to it.
Stan

Very interesting and very informative and constructive thread.

I have a CF-18 here. So if you guys needs testing to be done on this model, Let me know.

Did the patches (well, the very first one, lifebook-01-cf18) work for you?

There is a patch for the cf-18 in Dmitry's link above, any testing would be a big help. It means compiling either the full kernel or just the psmouse module for your kernel. If you need any help with it just post.
Cheers,
Stan

I finally got a kernel built and running using 2.6.18. I got no response from the touchscreen. Looking in lifebook.c, I found that there is no ident section for the CF-29. I added one, and tried it with both the callback line from the CF-28 section and the two lines for the CF-18, but no joy. Of course I have no idea if any other changes are required.

Please send your dmesg and output of dmidecode utility to dtor@insightbb.com. Thanks!

Azizcoos, it will need changes to xorg.conf to be usable.
Did the lifebook show up in dmesg when you added the CF-29 to the DMI detection?
And if so, are there 2 lifebook entries with "cat /proc/bus/input/devices"?
If there are you should be able to check the output from each, "od /dev/input/event3" for instance, and get one output from the pad and another from the screen.
At least, that is my understanding of how it should work with the cf-18, please let me know if I'm wrong on anything.
Cheers,
Stan