Hi Fanthom,
Thank you for your explanation. I now understand what you meant by pull from slackware.
Penmount is tricky. Anyone working with their touchscreens just has no luck unless they get the severely proporietary driver from penmount. I know what you are saying with regards to the kernel driver and supporting package but nobody gets this t work. Here is the original email from penmount:
Checked your email further, here are the best suggestions we have:
(1) For using PenMount 9000 with standard PenMount device driver
Please change the protocol in penmount.ini to PM9000 instead of PM9000COM
and perform installation again. Please do not use the kernel driver (the driver from Linux kernel) in
this case.
(2) For using PenMount 9000 kernel driver that comes with the Linux kernel.
If you prefer the open source solution, please try the attached file. This
file contains a install script for automatically install the PenMount
kernel driver and tslib in Debian 6.
The installation is for installing PenMount device on /dev/ttyS0. If using
other ports, please modify the rc.local file in the driver package and
perform installation again.
For more information, please check the README file in the device driver
package.
Hope this helps.
Shane
Shane also indicated in another email:
Code: Select all
When you use the tslib, you will need to setup the following:
(1) Modify /etc/ts.conf and setup module_raw, the tslib will read “/dev/inut/eventX” device.
(2) Set the environment variable: TSLIB_TSDEVICE to PenMount event device (for example, /dev/input/event2).
(3) Calibration reads /dev/fb0. Your system needs to support frame buffer.
Regards,
In the referenced package
http://daryl.no-ip.org:5000/fbsharing/5PY35bpp here there is a script that makes a new penmount.ko and inserts it.
No I did not recompile the kernel, the kernel sources package was needed for the makefile script that came in the linked package and I thought that it may be enough.
Penmount or Salt.tw reports that stock kernel penmount.ko does not report to event layer without patch. The instructions for using inputattach in the linked files is why I thought I needed it. The vendor for the touchscreen indicates its needed. When I asked about inputattach on my first message it was you who references the gpm package so I was just following your lead. I did find a gpm and input attach that has the options that I need in debian squeeze, wheezy and sid. I have made modules seven times over last night from the debian packages. When I insert the modules in to porteus dialogs indicate success however the command "inputattach" is not found after insertion and even rebooting leaving module in /mnt/sda1/porteus/modules. Rebooting with and without the module numerous times did not help.
For whateverreason Porteus reports success on inputattach module but the command is not found.
This is why I asked if there was a way to debug modules. I meant porteus modules. I can make a xzm from deb2xzm but after inserting inputattach.xzm I get errors on the command.
I made the rc.local file as you mentioned and I can see penmount get loaded on init and its being used by 8 whatever 8 is. I was my intentions to use tslibs and not the severely proprietary penmount driver that led me to inputattach and trying to get the device on /dev/ttyS0 moved over to /dev/input/eventX.
I have tried to make a custom kernel for this device from porteus kernel documentation in the past but did not complete the instructions due to various errors. Left off with Brokenman with a "I will ship you one of these tablets once I get the money". Today I am still unemployed and cant afford to ship otherwise I would make you the offer. Any chance you are in Denver?
