Touchscreen HOWTO
@tempestuous
NO Luck:
xorg just goes to a black screen. Am I missing something?
Package installed but no menu entry:
touchscreen-Puppy4.1.pet
modules.conf:
#after running alsaconf, stuff gets appended...
alias char-major-13-67 evdev
rc.local:
modprobe usbtouchscreen
modprobe evdev
xorg.conf:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "touchscreen" "CorePointer"
InputDevice "dummy"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "touchscreen"
Driver "fujitsu"
Option "Device" "/dev/input/event8"
Option "DeviceName" "touchscreen"
Option "MinX" "98"
Option "MinY" "43"
Option "MaxX" "940"
Option "MaxY" "925"
Option "ReportingMode" "Raw"
Option "Emulate3Buttons"
Option "Emulate3Timeout" "50"
Option "SendCoreEvents" "On"
EndSection
Section "InputDevice"
Identifier "dummy"
Driver "void"
Option "Device" "/dev/input/mice"
EndSection
# Perhaps this link can help to for configuration of the p1120:
http://sifter.org/~simon/journal/20030911.html
NO Luck:
xorg just goes to a black screen. Am I missing something?
Package installed but no menu entry:
touchscreen-Puppy4.1.pet
modules.conf:
#after running alsaconf, stuff gets appended...
alias char-major-13-67 evdev
rc.local:
modprobe usbtouchscreen
modprobe evdev
xorg.conf:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "touchscreen" "CorePointer"
InputDevice "dummy"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "touchscreen"
Driver "fujitsu"
Option "Device" "/dev/input/event8"
Option "DeviceName" "touchscreen"
Option "MinX" "98"
Option "MinY" "43"
Option "MaxX" "940"
Option "MaxY" "925"
Option "ReportingMode" "Raw"
Option "Emulate3Buttons"
Option "Emulate3Timeout" "50"
Option "SendCoreEvents" "On"
EndSection
Section "InputDevice"
Identifier "dummy"
Driver "void"
Option "Device" "/dev/input/mice"
EndSection
# Perhaps this link can help to for configuration of the p1120:
http://sifter.org/~simon/journal/20030911.html
Fujitsu P1120 Working!
Maybe you need the touchpanel pet file from the beginning of this forum still but after that all you need is...
In:
/etc/X11/xorg.conf
Under:
Section "ServerLayout"
Add:
InputDevice "touchscreen" "CorePointer"
Also add the following:
Section "InputDevice"
Identifier "touchscreen"
Driver "evdev"
Option "Device" "/dev/input/js0"
Option "DeviceName" "touchscreen"
EndSection
Now you will need to download and use Joytouch:
http://sifter.org/~simon/journal/ims/20 ... ch-1.2.tgz
All you have to do is:
chmod 777 runjoy
./runjoy
Note: I typed all this out by hand so there might be some typos and you will also probably want to have it load the following on startup:
./runjoy
I didn't cover that here yet... I spent forever trying to configure this... and I just wanted something up that works for the P1120!
All I need now is to figure out how to run this script on startup.
rc.local doesn't seem to work with:
/root/joytouch-1.2/runjoy
Maybe you need the touchpanel pet file from the beginning of this forum still but after that all you need is...
In:
/etc/X11/xorg.conf
Under:
Section "ServerLayout"
Add:
InputDevice "touchscreen" "CorePointer"
Also add the following:
Section "InputDevice"
Identifier "touchscreen"
Driver "evdev"
Option "Device" "/dev/input/js0"
Option "DeviceName" "touchscreen"
EndSection
Now you will need to download and use Joytouch:
http://sifter.org/~simon/journal/ims/20 ... ch-1.2.tgz
All you have to do is:
chmod 777 runjoy
./runjoy
Note: I typed all this out by hand so there might be some typos and you will also probably want to have it load the following on startup:
./runjoy
I didn't cover that here yet... I spent forever trying to configure this... and I just wanted something up that works for the P1120!
All I need now is to figure out how to run this script on startup.
rc.local doesn't seem to work with:
/root/joytouch-1.2/runjoy
-
- Posts: 5
- Joined: Mon 12 Apr 2010, 20:16
I'm trying to figure out how to get my touchscreen on this MSI Pennote 3100 working. I have looked at the manual and website, but haven't found much more than information identifying it as a touchscreen.
I can't seem to identify who made the device or anything. I guess it simply runs through the motherboard's PS/2 port from what I've derived from /proc/bus/input/devices. Is there any other way to identify it?
Having read through this, is it correct that Puppy doesn't support any PS/2 touchscreens or just some? I'm a bit confused.
I can't seem to identify who made the device or anything. I guess it simply runs through the motherboard's PS/2 port from what I've derived from /proc/bus/input/devices. Is there any other way to identify it?
Having read through this, is it correct that Puppy doesn't support any PS/2 touchscreens or just some? I'm a bit confused.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Hi tempestuous/other interesteds
untested, but couldn't PS2 to USB adapter be used....?
Some clever clogs may try their own connections ps2>usb
http://pinouts.ru/InputCables/usb_ps2_m ... nout.shtml
[Info gathered whilst researching Car PC project]
However check out Chinese touchscreens [usb solderless] for EEEPC etc on ebay....they're getting cheap!!
HTH
Aitch
untested, but couldn't PS2 to USB adapter be used....?
http://www.ehow.co.uk/list_6311834_uses ... ector.htmlOlder computer monitors that offered touch screen capabilities often used a PS/2 interface to transmit the coordinates touched on the monitor to the computer. Touch screens work in a very similar way to a mouse, with the actual screen coordinates replacing mouse movement data and tapping on the screen replacing mouse clicks. In some cases, a touch screen that uses the PS/2 interface may have a pass-through that also allows you to use a mouse with your touch screen. However, the touch screen would likely have priority in cases of conflicts between mouse input and screen input. How this works will depend on the how the hardware and software of the touch screen are designed. Older touch screens use the PS/2 interface. More modern touch screens use USB.
Some clever clogs may try their own connections ps2>usb
http://pinouts.ru/InputCables/usb_ps2_m ... nout.shtml
[Info gathered whilst researching Car PC project]
However check out Chinese touchscreens [usb solderless] for EEEPC etc on ebay....they're getting cheap!!
HTH
Aitch
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Maybe, I don't know. Certainly the touchscreen events will appear at the USB bus of the Puppy computer, but there's no guarantee that the nature of these events (which would normally be interpreted by extended driver code in the Linux PS/2 driver) will be recognised by the usbtouchscreen module in Puppy.Aitch wrote:untested, but couldn't PS2 to USB adapter be used....?
I have asked Barry to include PS/2 touchscreen support in future kernels -
http://bkhome.org/blog/?viewDetailed=01682
Panasonic CF-73 Laptop touchscreen... can't make it work
Hello all, I recently discovered puppy and been toying with it for a few days now, I took my old Panasonic Toughbook CF-73 which i use mostly to connect to a LCD tv and watch movies killed winXP and put a puppy into it... it all works and looks nice, i can access the samba shares faster than from a win machine and life is good... so I tried to make the touchscreen work as it is a nice options to control the film from the bed how lazy i am...
Anyway, i followed the instructions here and in some other posts and invented some... to no avail i cannot make it work...
The laptop on windows finds the touchscreen as a serial device on com port 7, and the hardware identifier is: FJC5000 which i assume is a Fujitsu...
I am running puppy 511 and used the .pet in the first post for the closes version 4xx something... edited the xorg.conf in all possible ways:
used eventXX, ttySXX, all.. and no matter what the touchscreen remains irresponsive...
any help or advice will be much appreciated
thanks!
N
Anyway, i followed the instructions here and in some other posts and invented some... to no avail i cannot make it work...
The laptop on windows finds the touchscreen as a serial device on com port 7, and the hardware identifier is: FJC5000 which i assume is a Fujitsu...
I am running puppy 511 and used the .pet in the first post for the closes version 4xx something... edited the xorg.conf in all possible ways:
used eventXX, ttySXX, all.. and no matter what the touchscreen remains irresponsive...
any help or advice will be much appreciated
thanks!
N
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
That was wrong. I suggest you delete the entire /usr/X11R7/lib/xorg/modules/input/ directory.CoronelN wrote:I am running puppy 511 and used the .pet in the first post for the closes version 4xx something...
Puppy 5.1.x already contains the necessary touchscreen Xorg plugins at /usr/lib/xorg/modules/input
Now see the next post.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Fujitsu Toughbooks
Apparently there was a range of different touchscreen devices across the Toughbook range, some on the serial port, some USB. You will need to Google to find our which touchscreen driver components each Toughbook requires.
The Toughbook CF-73 has an "SMK" serial touchscreen device, which requires the fairly conventional "evtouch" Xorg input plugin, but also a special kernel module called "toughbooksmk", plus a special utility called "inputattach".
Puppy 5.1 already contains the evtouch plugin, but here are the other 2 components.
The source code (which I needed to hack) was obtained from
http://sourceforge.net/projects/toughbooksmk/
Instructions:
First set up the evtouch plugin as per the serial setup instructions earlier in this thread
http://www.murga-linux.com/puppy/viewto ... 651#295651
The difference will be:
In section 2b, the two modules to load at bootup are "toughbooksmk" and "evdev".
In section 4, your "Driver" value will be "evtouch".
In section 5, the extra command to add to /etc/rc.d/rc.local is
Cross your fingers and reboot.
If no success, it may be that the Puppy kernel image needs to be replaced (??), too, because while I was compiling the toughbooksmk kernel module I noticed that the patchfile updated the kernel's serial include files.
Apparently there was a range of different touchscreen devices across the Toughbook range, some on the serial port, some USB. You will need to Google to find our which touchscreen driver components each Toughbook requires.
The Toughbook CF-73 has an "SMK" serial touchscreen device, which requires the fairly conventional "evtouch" Xorg input plugin, but also a special kernel module called "toughbooksmk", plus a special utility called "inputattach".
Puppy 5.1 already contains the evtouch plugin, but here are the other 2 components.
The source code (which I needed to hack) was obtained from
http://sourceforge.net/projects/toughbooksmk/
Instructions:
First set up the evtouch plugin as per the serial setup instructions earlier in this thread
http://www.murga-linux.com/puppy/viewto ... 651#295651
The difference will be:
In section 2b, the two modules to load at bootup are "toughbooksmk" and "evdev".
In section 4, your "Driver" value will be "evtouch".
In section 5, the extra command to add to /etc/rc.d/rc.local is
Code: Select all
inputattach -smk /dev/ttyS4
If no success, it may be that the Puppy kernel image needs to be replaced (??), too, because while I was compiling the toughbooksmk kernel module I noticed that the patchfile updated the kernel's serial include files.
- Attachments
-
- toughbooksmk-k2.6.33.2.pet
- for Puppy 5.1/5.2
- (8.89 KiB) Downloaded 738 times
tempestuous, thanks for the reply, I did as you told me and crossed my fingers, however now i only get a black screen when i start Xwin...
I am trying to figure out how to solve that.
Here is what i did:
tried to delete the files in
/usr/X11R7/lib/xorg/modules/input/
the window just froze and the files did not delete.
Q: the are a lot of files in there also are you sure i need to delete them all?
(What i did was to copy them elsewhere and deleted them from the console)
Then i Downloaded the .pet at the end of your post (I assumed it had the files you mention in the post
Did the edits as per your post.
Crossed my fingers and restarted...
Result black screen....
I did a inputattch -debug /dev/ttySX until i found that /dev/ttyS2 gives me gibberish in the console when i press the touchscreen... so i assume the TS is on ttyS2 not in 4... anyway when i run from the console
inputattach -smk /dev/ttyS2 it just sits there doing nothing...
I've also tried inputattach -fjs as Windows finds the TS to be a fujitsu fjc5000...
do you have any more advice?
once i succeed in having X11 start i will try to fiddle a bit with your instructions...
thanks!
BTW: i left the laptop with an Ironbrowser window open and there was a video embeed in one page and the laptop refused to throttle down the CPU even thou the video was not playing curious about it i ran a top from the console and the flashlib.so was using 90% cpu time even thou nothing was happening in the PC... i selectively closed Iron tabs until by closing the one with the video embeeded the cpu when to idle and flashlib stopped using it.... would that be considered a bug? should i report it somewherE ?
I am trying to figure out how to solve that.
Here is what i did:
tried to delete the files in
/usr/X11R7/lib/xorg/modules/input/
the window just froze and the files did not delete.
Q: the are a lot of files in there also are you sure i need to delete them all?
(What i did was to copy them elsewhere and deleted them from the console)
Then i Downloaded the .pet at the end of your post (I assumed it had the files you mention in the post
Did the edits as per your post.
Crossed my fingers and restarted...
Result black screen....
I did a inputattch -debug /dev/ttySX until i found that /dev/ttyS2 gives me gibberish in the console when i press the touchscreen... so i assume the TS is on ttyS2 not in 4... anyway when i run from the console
inputattach -smk /dev/ttyS2 it just sits there doing nothing...
I've also tried inputattach -fjs as Windows finds the TS to be a fujitsu fjc5000...
do you have any more advice?
once i succeed in having X11 start i will try to fiddle a bit with your instructions...
thanks!
BTW: i left the laptop with an Ironbrowser window open and there was a video embeed in one page and the laptop refused to throttle down the CPU even thou the video was not playing curious about it i ran a top from the console and the flashlib.so was using 90% cpu time even thou nothing was happening in the PC... i selectively closed Iron tabs until by closing the one with the video embeeded the cpu when to idle and flashlib stopped using it.... would that be considered a bug? should i report it somewherE ?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
OK, that's good diagnosis.CoronelN wrote:I did a inputattch -debug /dev/ttySX until i found that /dev/ttyS2 gives me gibberish in the console when i press the touchscreen... so i assume the TS is on ttyS2 not in 4
I suggest you also have a look at /var/log/Xorg.0.log, looking for anything relating to the "evtouch" plugin.
I have a feeling you will need a revised kernel image, which will provide the extra logic for the serial driver to talk to the touchscreen driver.
I can compile this shortly after Christmas.
Mmm, there should not be anything in there in Puppy 5.1.xCoronelN wrote:tried to delete the files in
/usr/X11R7/lib/xorg/modules/input/
the window just froze and the files did not delete.
Q: the are a lot of files in there also are you sure i need to delete them all?
Thanks again!
I managed to recover from the blank screen, by commenting the touchscreen lines out in:
/etc/rc.d/rc.local
Unfortunately XORG decided that it needed to run the wizard and it destroyed my previos xorg.conf but there was an .old one in the folder so i recovered it
I am still struggling to get rid of a second panel /task bar that appeared after that and trying to figure out why my script in startup stopped mounting the samba shares...
I did a selective
/etc/rc.d/rc.local
enabling and by commenting the
toughbooksmk X asks me to run the wizard (I hit ignore, but still black screen)
I just remembered that in /etc/X11/xorg.conf file is a module section and i added the evdev and the toughtbooksmk in the form:
load "modulename"
because modprobe was telling me that:
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d
That didn't work neither...
Finally i commented in /etc/X11/xorg.conf
the line:
InputDevice "touchscreen" "CorePointer"
and Xwin started but the menu items for restart X server and reboot power off are nt working also y have the annoyng double taskbar...
Once i solved this i will re-post with touchscreen related actions...
I managed to recover from the blank screen, by commenting the touchscreen lines out in:
/etc/rc.d/rc.local
Unfortunately XORG decided that it needed to run the wizard and it destroyed my previos xorg.conf but there was an .old one in the folder so i recovered it
I am still struggling to get rid of a second panel /task bar that appeared after that and trying to figure out why my script in startup stopped mounting the samba shares...
I did a selective
/etc/rc.d/rc.local
enabling and by commenting the
toughbooksmk X asks me to run the wizard (I hit ignore, but still black screen)
I just remembered that in /etc/X11/xorg.conf file is a module section and i added the evdev and the toughtbooksmk in the form:
load "modulename"
because modprobe was telling me that:
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d
That didn't work neither...
Finally i commented in /etc/X11/xorg.conf
the line:
InputDevice "touchscreen" "CorePointer"
and Xwin started but the menu items for restart X server and reboot power off are nt working also y have the annoyng double taskbar...
Once i solved this i will re-post with touchscreen related actions...
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
To avoid messing up your installation I suggest in the testing phase you just boot to the Puppy 5.1 CD, and restart X (Ctrl<Alt>Backspace) each time you change your xorg.conf file. And of course once X has launched, you need to run the "inputattach" command to activate the touchscreen.
Yes, some Xorg modules contain logic which will load a kernel module (Xorg DRI modules, for example) but I don't think Xorg can directly load a kernel module.
But there's no need to make things so complex anyway, just run these 2 commands
And I still suspect you will need a revised kernel, which will need to wait.
Don't worry about that, it's just a warning to update the old /etc/modprobe.conf regime, but the old regime is still recognised.CoronelN wrote:... modprobe was telling me that:
WARNING: Deprecated config file /etc/modprobe.conf, all config files belong into /etc/modprobe.d
I don't think that will work. My understanding is that "modulename" refers to an Xorg module or extension, not kernel module.CoronelN wrote:I just remembered that in /etc/X11/xorg.conf file is a module section and i added the evdev and the toughtbooksmk in the form:
load "modulename"
Yes, some Xorg modules contain logic which will load a kernel module (Xorg DRI modules, for example) but I don't think Xorg can directly load a kernel module.
But there's no need to make things so complex anyway, just run these 2 commands
Code: Select all
modprobe toughbooksmk
modprobe evdev
tempestuous thanks again!
I have not found out how to unbreak what i broke but it is surprisingly easy to break even thou i dont know what it is lol...
I just realized myself that i will need to reinstall again the puppy and that i definitively will use 2 install.. 1 to use the laptop and another to get that bloody TS working...
I will do it and keep you posted in case the kennel (puppy kernel ) needs to be modified...
BTW i am running LUPU-515 i just checked...
So if i boot from the CD i should:
From the console:
modprobe toughtbooksmk
modprobe evdev
set serial etc...
inputattach xxxx
edit the xorg.conf and restart X (CTRL ALT BSPACE) and xwin ?
and it should work if it is gonna work ?
I tried from the CD and upon modding the xorg.conf X refused to start used xorgwizard and it broke the menus had to hard boot the machine... maybe there is a bug in xorgwizard ?
Merry xmas mate and have i said thanks?
I have not found out how to unbreak what i broke but it is surprisingly easy to break even thou i dont know what it is lol...
I just realized myself that i will need to reinstall again the puppy and that i definitively will use 2 install.. 1 to use the laptop and another to get that bloody TS working...
I will do it and keep you posted in case the kennel (puppy kernel ) needs to be modified...
BTW i am running LUPU-515 i just checked...
So if i boot from the CD i should:
From the console:
modprobe toughtbooksmk
modprobe evdev
set serial etc...
inputattach xxxx
edit the xorg.conf and restart X (CTRL ALT BSPACE) and xwin ?
and it should work if it is gonna work ?
I tried from the CD and upon modding the xorg.conf X refused to start used xorgwizard and it broke the menus had to hard boot the machine... maybe there is a bug in xorgwizard ?
Merry xmas mate and have i said thanks?
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Yes, I can see it's getting confusing. So here are the complete steps:
Boot to the Puppy 5.1 CD, and install toughbooksmk-k2.6.33.2.pet
Now load the toughbooksmk module, plus evdev module -
It may be necessary to add this to /etc/modules.conf -
It wouldn't hurt.
Now modify your /etc/X11/xorg.conf file;
Add these two new InputDevice sections -
Notice ttyS2.
In Section "ServerLayout" find the line:
InputDevice "Mouse0" "CorePointer"
and below that line add this -
Now it's time to restart the X server.
Ctrl<Alt>Backspace will exit X and leave you at the command prompt.
UPDATE: before relaunching X, it's very important to run this command -
Now you can launch X with "xwin"
Boot to the Puppy 5.1 CD, and install toughbooksmk-k2.6.33.2.pet
Now load the toughbooksmk module, plus evdev module -
Code: Select all
modprobe toughbooksmk
modprobe evdev
Code: Select all
alias char-major-13-67 evdev
Now modify your /etc/X11/xorg.conf file;
Add these two new InputDevice sections -
Code: Select all
Section "InputDevice"
Identifier "touchscreen"
Driver "evtouch"
Option "Device" "/dev/ttyS2"
Option "DeviceName" "touchscreen"
Option "MinX" "82"
Option "MinY" "146"
Option "MaxX" "4036"
Option "MaxY" "3999"
Option "SendCoreEvents" "On"
EndSection
Section "InputDevice"
Identifier "dummy"
Driver "void"
Option "Device" "/dev/input/mice"
EndSection
In Section "ServerLayout" find the line:
InputDevice "Mouse0" "CorePointer"
and below that line add this -
Code: Select all
InputDevice "touchscreen" "CorePointer"
InputDevice "dummy"
Ctrl<Alt>Backspace will exit X and leave you at the command prompt.
UPDATE: before relaunching X, it's very important to run this command -
Code: Select all
inputattach -smk /dev/ttyS2
Last edited by tempestuous on Tue 28 Dec 2010, 02:46, edited 1 time in total.
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
Tempestuos, thanks you very much i hope you spent a nice xmas and the next year be all that you expect! (my way of best wishes in my esp-fran-glish..)
I tried as you suggested and X11 doenst starts.
maybe i need that kernel after all... one question thou... whenever i update to a newer version of puppy lets say lupu-518 or 520... i will need to apply the kernel ?
I mean as far as i undersand the kernel doesnt necessarly changes between versoins... or i am wrong ?
my question is because if i need a new kernel each time i'd rather ask you to show me how to compile it than brother you every update...
Thanks again ! a 1000 thanks!
N
I tried as you suggested and X11 doenst starts.
maybe i need that kernel after all... one question thou... whenever i update to a newer version of puppy lets say lupu-518 or 520... i will need to apply the kernel ?
I mean as far as i undersand the kernel doesnt necessarly changes between versoins... or i am wrong ?
my question is because if i need a new kernel each time i'd rather ask you to show me how to compile it than brother you every update...
Thanks again ! a 1000 thanks!
N
Hi,
I am completely new to Linux and obviously Puppy 5.1.1 and have spent the last 2 days working out how to create a Puppy LiveUSB and install Java and run a Java app. I finally got that all working and now the problem i have is getting my Elo touchscreen working correctly. I run the xorg wizard and probed for a suitable driver and then used xvidtune to fill out the space. So the display is working fine but its the touch input that i'm having the trouble with.
This thread has brought some light to my situation. i have read through it thourghly and have a small understanding of what I need to do but still don't really know where to start.
I put the command into the console;
modprobe elo and got a warning: deprecated config file so i renamed the file with a .OLD extention as advised by another website.
Then i entered the command again which seemed to work correctly. Then i entered modprobe elographics_drv and got error FATAL: Module elographics_drv not found. The module is definately there as I have found it in a search of files.
If anyone would be able to give me some help or guide me through this process, I would be extremely grateful.
Thanks,
Anthony
I am completely new to Linux and obviously Puppy 5.1.1 and have spent the last 2 days working out how to create a Puppy LiveUSB and install Java and run a Java app. I finally got that all working and now the problem i have is getting my Elo touchscreen working correctly. I run the xorg wizard and probed for a suitable driver and then used xvidtune to fill out the space. So the display is working fine but its the touch input that i'm having the trouble with.
This thread has brought some light to my situation. i have read through it thourghly and have a small understanding of what I need to do but still don't really know where to start.
I put the command into the console;
modprobe elo and got a warning: deprecated config file so i renamed the file with a .OLD extention as advised by another website.
Then i entered the command again which seemed to work correctly. Then i entered modprobe elographics_drv and got error FATAL: Module elographics_drv not found. The module is definately there as I have found it in a search of files.
If anyone would be able to give me some help or guide me through this process, I would be extremely grateful.
Thanks,
Anthony