On Sat, 23 Sep 2006, George Galt wrote:
I'm trying to install Elo's USB touchscreen driver for an Elo 1524L
touchscreen on FC5 (the touchscreen is identified as USB Kernel Input
device name: "EloTouchSystems,Inc Elo TouchSystems 2216 AccuTouch(r)
USB Touchmonitor Interface"). The "elographics" driver in xorg appears
to only work with a serial touchscreen. I'm using FC5 and the
2.6.15-1.2054_FC5 kernel.
The instructions from Elo are to load their USB driver after
"usbcore" but before "hid". I'm not sure how to do this. Elo's
instructions are to load the driver through modprobe.conf, but that
doesn't to work. I have also been given the suggestion of loading
through rc.sysinit by placing:
action $"Initializing EloUSB Drivers:" modprobe elousb 2> /dev/null
prior to the line which has "modprobe hid 2>/dev/null", ultimately
ending up with a section that looks like:
needusbstorage=
if[$usb="1"] then
needusbstorage=.....
action $"Initializing EloUSB Drivers:" modprobe elousb 2> /dev/null
If["${version[0]} ........... ]
LC_ALL=C grep 'hid' /proc/bus/usb/drivers" ||action $Initializing USB
HID Interface:" modprobe hid 2>/dev/null
action $Initializing USB Keyboard" modprobe keybdev 2> /dev/null
The only problem is that I don't have anything that approximates this
section in rc.sysinit.
It's a bad idea to modify rc.sysinit anyway. It will be overwritten at
the next initscripts update.
Here's a line that you might find useful for /etc/modprobe.conf. I had to
use it for a while to make sure that my wired interface module
(e1000) loaded before my wireless (ipw2200). Something similar should
work to sequence the loading of the modules you need.
alias eth0 e1000
alias eth1 ipw2200
install ipw2200 /sbin/modprobe -q eth0; /sbin/modprobe --ignore-install ipw2200
The last line installs the ipw2200 driver using a two-command sequence.
The first command installs the e1000 driver and the second one installs
the ipw2200 driver, but ignores the install line in /etc/modprobe.conf.
One other issue may be that Elo states that 'hid' must be built as a
loadable module, rather than compiled in to the kernel. How do I
check this?
Almost all drivers in Red Hat and Fedora kernels are loadable modules.
You can see the config file used to build the kernel if you have the
kernel-devel RPM installed. Find it in
/lib/modules/$(uname -r)/source/.config.
Any help or ideas?
HTH.
Thanks,
George
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
