I have problems getting a NJY touch screen (LINK) to work that I purchased a while back off ebay. Of course I let myself be fooled by the claims of the manufacturer that it works with openSUSE and did not realize that their drivers (DRIVERS) only go up 9.2 and only 32bit until it was already too late.
The first problem is that I cannot even get the .sh file to extract the driver without giving me errors and all attempts to manually extract the embedded tgz file have failed miserably. The technical support of the manufacturer is extremely limited regarding driver/installation; though they quickly respond to emails, all I got was "try the driver on our download page" - as well as answers along the line "64bit is way too advanced - nobody uses it anyway"
The panel and the controller themselves work, I could get them to work on a WinXP test box. I was hoping that given the multitude of similar panels out there there might be another way of getting it to work... I would really appreciate if any of you guys could help!
When I plug it in, dmesg reports:
[16691.691059] usb 3-3: new low speed USB device using ohci_hcd and address 2
[16691.882579] usb 3-3: New USB device found, idVendor=0eef, idProduct=0001
[16691.882585] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[16691.882588] usb 3-3: Product: Љ
[16691.882591] usb 3-3: Manufacturer: Љ
[16691.903041] generic-usb: probe of 0003:0EEF:0001.0004 failed with error -32
It does not even recognize the manufacturer (unless that weird symbol actually means something), nor does it register as a HID device.
And lsusb -v reports:
I googled extensively and tried all sorts of tricks / suggestions that are floating around ... e.g. disabling acpi, blocking usbtouch kernel modules to get similar drivers working etc. I tried the eGalax driver, DWav driver, and I contacted eGalax who responded that they are not the manufacturer... kinda makes sense, but it's still weird, particularly since the windows driver was also programmed by DWav/eGalax.Code:Bus 003 Device 002: ID 0eef:0001 D-WAV Scientific Co., Ltd eGalax TouchScreen Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0eef D-WAV Scientific Co., Ltd idProduct 0x0001 eGalax TouchScreen bcdDevice 1.00 iManufacturer 1 ? iProduct 2 ? iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 ? bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 44mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 0 No Subclass bInterfaceProtocol 0 None iInterface 0 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.12 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 141 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Device Status: 0x0000 (Bus Powered)
Can anybody provide me with some pointers what to try, where to look etc? Or maybe help me extract that driver from the file on the manufacturer's website? If that works, is there any way to use a 32bit driver in a 64b system? Or do you think it's possible to use any of the other manufacturers' drivers by adjusting some parameters - they look pretty identical and should not differ too much (I hope)?
From what I gather the lsusb output is quite similar if not identical what other people get with other controllers.