xenarc touchscreen(usb) not detected on startup -CentOS4

**mclarenfan** · 08-24-2006, 06:42 PM

Hi,
I have a xenarc 1020 tsv touchscreen, with CentOS 4. The touchscreen is caliberated and it works fine, when the touchscreen is connected after the OS boots. (the hotplug works)

For some reason, the touchscreen is not detected if it is connected before I start the computer.
cat /proc/bus/input/devices does not list the device.
lsusb does not show any usb device connected.

The weird part is, if I connect a USB mouse and the touchscreen before startup, then both these devices are detected. If only the USB mouse is connected before startup, then that is detected too.(hence I can say that coldplug works)

any pointers?

Thanks.

**saverio911** · 08-27-2006, 09:42 PM

This happened to me as well in gentoo. If the touchscreen is showing up in dmesg after bootup then reinstall/rebuild coldplug and hotplug. I got info from here: http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/b89783a1e2682771/6b5222475d5c5c2f?lnk=st&q=linux+usb+mouse&rnum=2&hl=en#6b5222475d5c5c2f

**mclarenfan** · 08-28-2006, 04:16 PM

Thanks for the reply!
The touchscreen does not show up in dmesg...
Even when I disconnect the USB to connect it again, dmesg shows nothing. It does show up a entry when I reconnect the USB.

I am using the following udev rule: (I read about it here: Touchscreen changing usb event device on power on/off)
BUS="usb",KERNEL="event*",SYSFS{manufacturer}="eGa lax Inc.",SYMLINK="touchscreen"

does this look right? because now even the usb mouse is not detected (when USB mouse is the only device connected)

**saverio911** · 08-29-2006, 04:16 PM

If you get no listing in dmesg you aren't going to get anywhere.
When you hot plug the device after bootup do you get any new messages added to the bottom of /var/log/messages or dmesg or wherever you configured you box to send them?
I would remove the UDEV rule just to see if coldplug works again. If it does then the UDEV rule is the most likely culprit. For me, at least, UDEV has a steep learning curve. Every UDEV rule I have made from scratch needs 4 or 5 iterations to work right.

Oh yeah - shouldn't it be SYMLINK="input/touchscreen" instead of just SYMLINK="touchscreen" so you get /dev/input/touchscreen?

**mclarenfan** · 08-31-2006, 03:08 PM

Originally Posted by saverio911

If you get no listing in dmesg you aren't going to get anywhere.
When you hot plug the device after bootup do you get any new messages added to the bottom of /var/log/messages or dmesg or wherever you configured you box to send them?

when I hotplug the touchscreen, this is what dmesg gives:
usb 2-2: new low speed USB device using address 2
input: eGalax Inc. USB TouchController on usb-0000:00:10.0-2
usbcore: registered new driver touchkitusb

Originally Posted by saverio911

I would remove the UDEV rule just to see if coldplug works again. If it does then the UDEV rule is the most likely culprit. For me, at least, UDEV has a steep learning curve. Every UDEV rule I have made from scratch needs 4 or 5 iterations to work right.

Oh yeah - shouldn't it be SYMLINK="input/touchscreen" instead of just SYMLINK="touchscreen" so you get /dev/input/touchscreen?

I removed the udev rule, but no luck, device still not detected at boot.

**saverio911** · 08-31-2006, 05:36 PM

Which version of UDEV tools are you using? If it is not current or you rebuilt it from source I would do a refresh. According to rpmfind the current version for RHEL (which I use the srpm to build with) is 039-10.8. I wish I could be more helpful but I am only using CentOS for my servers and not my carpc.