SLEPOS and greentouch touchscreen

Hi all:

im having a nightmare time trying o install the dependencies for a touchscreen from greentouch on a sles 11 sp3 with slePOS

its supposed to be this one: Model Number GT-TMO185A
http://www.greentouch.com.cn/products_detail/&productId=288.html

once i try to install the touchscreen.sh ask me for this :

make
tcl
tk
gcc
glibc-dlevel
XFree86-dlevel
kernel-source

the distro i had didint have any of those installed( its a super cut distro from a big enterprise)
i installed all but the XFree86 , its nowhere to be found
its not on the sles 11 sp3 dvd or SDK dvd.

tried looking for the RPM alone but the RPM ask me for another dependencies and so and so, dependencies after dependencies , which i cannot find anywhere

anyone can help me isntall this screen?

i appreciate the help

regards
«1

Comments

  • malcolmlewismalcolmlewis Knowledge Partner
    Hi and welcome to the Forum :)
    You want the Xorg (AKA XFree86) development rpm(s) which should be on the SDK.

    Which driver did you download?
  • MoratorroMoratorro Established Member
    Hi

    i got the drivers from the manufacturer:

    http://www.greentouch.com.cn/products_detail/&productId=158.html
    4 wire Resistive touch screen Windows 2000,Windows XP,Win 8,Windows NT,Windows CE,Linux,Mac>

    And i tried to install the xfree86 but i cant find it on any repo or SDK DVD.

    thats where im stuck.

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    Hi
    OK, so it's an egalax device, your connecting via USB? If so can you post the output from the following command;
    lsusb
    

    On your system if you use the following command do you see xorg devel packages?
    zypper se xorg x11
    

    Now if you look down in /tmp/touchkit there are already precompiled libraries for the device etc... so you could try manually copying to the correct location. Is this a 32 or 64bit install?

    A number of years ago I had a similar setup, need to get the screen out from the parts bin....
  • MoratorroMoratorro Established Member
    Hi

    here is the output

    Bus 004 Device 002: ID 8087:8000 Intel Corp.
    Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 002: ID 8087:8008 Intel Corp.
    Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 003: ID 046d:c063 Logitech, Inc. DELL Laser Mouse
    Bus 001 Device 002: ID 0c45:8419 Microdia
    Bus 001 Device 005: ID 413c:2110 Dell Computer Corp.
    Bus 001 Device 004: ID 413c:1010 Dell Computer Corp.
    Bus 001 Device 006: ID 0781:5567 SanDisk Corp. Cruzer Blade
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    and

    S | Name | Summary | Type
    --+
    +
    +
    i | dbus-1-x11 | D-Bus Message Bus System | package
    | dbus-1-x11 | D-Bus Message Bus System | srcpackage
    | emacs-x11 | GNU Emacs: Emacs binary with X Window System Support | package
    i | ghostscript-x11 | X11 library for Ghostscript | package
    i | libQt5X11Extras5 | Qt 5 X11 Extras Addon | package
    | libX11 | Core X11 protocol client library | srcpackage
    i | libX11-6 | Core X11 protocol client library | package
    i | libX11-6-32bit | Core X11 protocol client library | package
    i | libX11-data | Shared data for the Core X11 protocol library | package
    i | libX11-xcb1 | XCB X11 protocol client library | package
    i | libX11-xcb1-32bit | XCB X11 protocol client library | package
    | libgtkglext-x11-1_0-0 | OpenGL Extension to GTK | package
    i | libqt4-x11 | Qt 4 GUI related libraries | package
    i | libqt4-x11-32bit | Qt 4 GUI related libraries | package
    | libqt5-qtx11extras | Qt 5 X11 Extras Addon | srcpackage
    | libva-x11-1 | Video Acceleration (VA) API for Linux -- VA/X11 Backend | package
    i | libxkbcommon-x11-0 | Library for handling xkb descriptions using XKB-X11 | package
    | libxkbcommon-x11-0-32bit | Library for handling xkb descriptions using XKB-X11 | package
    i | patterns-sles-x11 | X Window System | package
    i | patterns-sles-x11-32bit | X Window System | package
    i | perl-X11-Protocol | Perl module for the X Window System Protocol, version 11 | package
    | perl-X11-Protocol | Perl module for the X Window System Protocol, version 11 | srcpackage
    i | pulseaudio-module-x11 | X11 module for PulseAudio | package
    | qt4-x11-tools | C++ Program Library, Core Components | package
    i | x11 | X Window System | pattern
    | x11-japanese-bitmap-fonts | Japanese Fixed Fonts for the X Window System | package
    | x11-japanese-bitmap-fonts | Japanese Fixed Fonts for the X Window System | srcpackage
    i | x11-tools | Tools for the X Window System | package
    | x11-tools | Tools for the X Window System | srcpackage
    i | x11perf | Utility to test X11 server performance | package
    | x11perf | Utility to test X11 server performance | srcpackage
    | xorg-docs | Miscellaneous documentation for the X Window System | package
    | xorg-docs | Miscellaneous documentation for the X Window System | srcpackage
    i | xorg-x11 | Compatibility metapackage for X.Org sample applications | package
    | xorg-x11 | Compatibility metapackage for X.Org sample applications | srcpackage
    i | xorg-x11-Xvnc | TigerVNC implementation of Xvnc | package
    | xorg-x11-driver-input | Compatibility metapackage for X.Org input drivers | package
    | xorg-x11-driver-input | Compatibility metapackage for X.Org input drivers | srcpackage
    i | xorg-x11-driver-video | Compatibility metapackage for X.Org video drivers | package
    | xorg-x11-driver-video | Compatibility metapackage for X.Org video drivers | srcpackage
    i | xorg-x11-essentials | Compatibility metapackage for X.Org core applications | package
    i | xorg-x11-fonts | X.Org fonts | package
    | xorg-x11-fonts | X.Org fonts | srcpackage
    i | xorg-x11-fonts-core | Core Fonts for X.Org | package
    i | xorg-x11-libs | Compatibility metapackage for X.Org libraries | package
    | xorg-x11-libs | Compatibility metapackage for X.Org libraries | srcpackage
    i | xorg-x11-server | X | package
    | xorg-x11-server | X | srcpackage
    i | xorg-x11-server-extra | Additional Xservers (Xdmx, Xephyr, Xnest) | package
    i | yast2-x11 | YaST2 - X11 support | package
    | yast2-x11 | YaST2 - X11 support | srcpackage

    Right now i have installed suse12 , ifyou really need the output from suse 11 let me know.
    also i installed ubuntu gnome and the touchscreen worked right away. nothing done on my side to make it work
    and i thought that maybe suse 12 now that it switched to gnome, would work too, but it didnt.
    also the drivers from the manufacturer are quite old, for suse 9, so no drivers . i dont think they will work ( also the installation script have errors)

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    Hi
    What release of SLE is now installed...
    cat /etc/SuSE-release
    

    What release are you wanting it to work on? There is a difference in Xorg file locations etc.

    What version of Ub* (esp versions of Xorg and kernel) can make a big difference, what about the lsusb output to identify the device from Ubuntu?

    Also on Ub* is it using usbtouchscreen kernel module;
    lsmod |grep usb
    
  • MoratorroMoratorro Established Member
    Hi

    The lsusb from Ubuntu its the same i sent you from SLES , the only device listed that i think its the mouse of the touchscreen its the
    Bus 003 Device 002 ID 0c45:8419 Midrodia

    im using the Ubuntu Gnome . 16.04.3

    The client wants to use SLES 11 SP3 , but i cannot install that anymore , there are no isos to download from the official page. only SP4

    what would i need to do to make the touchscreen work? and by working i mean the mouse ( or tracking?!) to be able to click on the screen
    i just need a single click, no right button , nothing. just click .

    how can i get the working config from ubuntu and use it on SLES?

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    Moratorro wrote: »
    Hi

    The lsusb from Ubuntu its the same i sent you from SLES , the only device listed that i think its the mouse of the touchscreen its the
    Bus 003 Device 002 ID 0c45:8419 Midrodia

    im using the Ubuntu Gnome . 16.04.3

    The client wants to use SLES 11 SP3 , but i cannot install that anymore , there are no isos to download from the official page. only SP4

    what would i need to do to make the touchscreen work? and by working i mean the mouse ( or tracking?!) to be able to click on the screen
    i just need a single click, no right button , nothing. just click .

    how can i get the working config from ubuntu and use it on SLES?

    regards
    Hi
    OK this looks like an infrared USB device;
    https://bugs.launchpad.net/ubuntu/+source/evtest/+bug/1519393

    When you test on Ub* can you post the output from that device with;
    lsusb -vvvv -c -d 0c45:8419
    

    Now, SLES 11 SP3 downloads are available, you want DVD1 (Not DVD2) but the later release you can use the better due to better driver support etc.

    https://www.suse.com/download-linux/source-code/

    So, PLEASE confirm both the release and arch (32 or 64bit) your going to use for this project so if needed I can install a test setup to duplicate what to install and where.

    There are also some tools in the SLE 11 branch called sax2 to help set up things as well for screens etc.
  • MoratorroMoratorro Established Member
    Hi

    thanks for the bug link, will check it now.

    the output in ubuntu:

    Bus 003 Device 003: ID 0c45:8419 Microdia
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor 0x0c45 Microdia
    idProduct 0x8419
    bcdDevice 1.00
    iManufacturer 1 SONiX
    iProduct 2 USB Device
    iSerial 0
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 34
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 1
    bInterfaceClass 3 Human Interface Device
    bInterfaceSubClass 1 Boot Interface Subclass
    bInterfaceProtocol 2 Mouse
    iInterface 0
    HID Device Descriptor:
    bLength 9
    bDescriptorType 33
    bcdHID 1.00
    bCountryCode 0 Not supported
    bNumDescriptors 1
    bDescriptorType 34 Report
    wDescriptorLength 199
    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 5
    Device Status: 0x0000
    (Bus Powered)

    The -c option didnt work.

    The client have suse 11 sp3 32bit

    and how can i use sas2x ? i hace checked some manuals but nothing about the touchscreen

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    On Tue 22 Aug 2017 07:34:01 PM CDT, Moratorro wrote:

    Hi

    thanks for the bug link, will check it now.

    the output in ubuntu:

    Bus 003 Device 003: ID 0c45:8419 Microdia
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor 0x0c45 Microdia
    idProduct 0x8419
    bcdDevice 1.00
    iManufacturer 1 SONiX
    iProduct 2 USB Device
    iSerial 0
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 34
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 1
    bInterfaceClass 3 Human Interface Device
    bInterfaceSubClass 1 Boot Interface Subclass
    bInterfaceProtocol 2 Mouse
    iInterface 0
    HID Device Descriptor:
    bLength 9
    bDescriptorType 33
    bcdHID 1.00
    bCountryCode 0 Not supported
    bNumDescriptors 1
    bDescriptorType 34 Report
    wDescriptorLength 199
    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 5
    Device Status: 0x0000
    (Bus Powered)

    The -c option didnt work.

    The client have suse 11 sp3 32bit

    and how can i use sas2x ? i hace checked some manuals but nothing about
    the touchscreen

    regards


    Hi
    Open a terminal and switch to root user and run the command;
    sax2
    
    That should give you a GUI to configure screen, mouse. X configuration
    etc. It's a mouse emulation via infrared LED's by the looks. I'm
    guessing on the screen front there is a gap in the plastic and not
    touching the screen, or small holes present?

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2|GNOME 3.20.2|4.4.79-18.26-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!
  • MoratorroMoratorro Established Member
    Hi

    yup i checked and there is a reddish hue in four inner edges.

    will check the sax2

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    Moratorro wrote: »
    Hi

    yup i checked and there is a reddish hue in four inner edges.

    will check the sax2

    regards
    Hi
    OK, so you need to confirm the real model as it appears to be infrared...
    http://www.greentouch.com.cn/products_detail/&productId=127.html
  • MoratorroMoratorro Established Member
    Hi

    on the back of the touchscreen say its s GT-TM185
    and there are no more drivers, there is only one available on the touchscreen page

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    On Tue 22 Aug 2017 11:04:02 PM CDT, Moratorro wrote:

    Hi

    on the back of the touchscreen say its s GT-TM185
    and there are no more drivers, there is only one available on the
    touchscreen page

    regards


    Hi
    OK, so can you install irda and yast2-irda packages, also want you to
    try adding a kernel module via;
    modprobe irda-usb
    

    Then look at the yast2 irda configuration and sax2 tools.

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2|GNOME 3.20.2|4.4.79-18.26-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!
  • MoratorroMoratorro Established Member
    Hi

    Thanks for the reply and i will install those packages.
    but im having a hard tie to install sles11 sp3

    it hangs on "initialazing gfx code"

    i checked the md5 hash nad its correct.
    changed the HDD AHCI to IDE
    using onboard video.

    this is the only version that gives me this error.

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    On Wed 23 Aug 2017 01:34:02 PM CDT, Moratorro wrote:

    Hi

    Thanks for the reply and i will install those packages.
    but im having a hard tie to install sles11 sp3

    it hangs on "initialazing gfx code"

    i checked the md5 hash nad its correct.
    changed the HDD AHCI to IDE
    using onboard video.

    this is the only version that gives me this error.

    regards


    Hi
    Stick with AHCI, is there an option in the BIOS to set the video ram
    size, gfx is the graphics card... So try selecting the text install
    option.

    --
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    openSUSE Leap 42.2|GNOME 3.20.2|4.4.79-18.26-default
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!
  • MoratorroMoratorro Established Member
    Hi

    I cant select any options, there is nothing else, only the line "initiilazing gfx code".
    it get stuckk there for hours if i let it.

    so i cannot isntall sles 11 sp3 at the moment.

    the MB its a MSI H81M E33

    can you help me fix the screen on sles 12? to move things forward

    regards and thanks!!
  • malcolmlewismalcolmlewis Knowledge Partner
    Moratorro wrote: »
    Hi

    I cant select any options, there is nothing else, only the line "initiilazing gfx code".
    it get stuckk there for hours if i let it.

    so i cannot isntall sles 11 sp3 at the moment.

    the MB its a MSI H81M E33

    can you help me fix the screen on sles 12? to move things forward

    regards and thanks!!
    Hi
    Sure, this is SLES 12 SP2 then?
  • MoratorroMoratorro Established Member
    Hi

    For now, till i can isntall sles 11 sp3 and try the options you sent me.

    so my request will be, can you help me with sles 12 sp2 for the moment please?

    i really appreciate your help

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    Moratorro wrote: »
    Hi

    For now, till i can isntall sles 11 sp3 and try the options you sent me.

    so my request will be, can you help me with sles 12 sp2 for the moment please?

    i really appreciate your help

    regards
    Hi
    Well the irda tools are lacking in SLES 12 SP2, however can you check on Ub* and see if the irda module is loaded AFTER you plug in the usb cord from the screen...

    Run this command before and after.
    lsmod |grep irda
    

    If the module is loaded, then need to check the same on SLES 12 SP2.

    On Ub* also need to look at the dmesg output AFTER you plug in the device as well to see what is being loaded/detected etc
  • MoratorroMoratorro Established Member
    Hi

    in ubuntu 17.04 :

    lsmod |grep irda doesnt return anything
    and the dmesg | grep usb

    [ 16.570880] input: SONiX USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:0C45:8419.0001/input/input13
    [ 16.570986] hid-multitouch 0003:0C45:8419.0001: input,hiddev0,hidraw3: USB HID v1.00 Mouse [SONiX USB Device] on usb-0000:00:14.0-2/input0
    [ 256.207270] usb 3-2: USB disconnect, device number 3
    [ 881.996029] usb 3-2: new low-speed USB device number 7 using xhci_hcd
    [ 882.140922] usb 3-2: New USB device found, idVendor=0c45, idProduct=8419
    [ 882.140924] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 882.140926] usb 3-2: Product: USB Device
    [ 882.140927] usb 3-2: Manufacturer: SONiX
    [ 882.155797] input: SONiX USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:0C45:8419.0005/input/input17
    [ 882.212377] hid-multitouch 0003:0C45:8419.0005: input,hiddev0,hidraw3: USB HID v1.00 Mouse [SONiX USB Device] on usb-0000:00:14.0-2/input0

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    Moratorro wrote: »
    Hi

    in ubuntu 17.04 :

    lsmod |grep irda doesnt return anything
    and the dmesg | grep usb

    [ 16.570880] input: SONiX USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:0C45:8419.0001/input/input13
    [ 16.570986] hid-multitouch 0003:0C45:8419.0001: input,hiddev0,hidraw3: USB HID v1.00 Mouse [SONiX USB Device] on usb-0000:00:14.0-2/input0
    [ 256.207270] usb 3-2: USB disconnect, device number 3
    [ 881.996029] usb 3-2: new low-speed USB device number 7 using xhci_hcd
    [ 882.140922] usb 3-2: New USB device found, idVendor=0c45, idProduct=8419
    [ 882.140924] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 882.140926] usb 3-2: Product: USB Device
    [ 882.140927] usb 3-2: Manufacturer: SONiX
    [ 882.155797] input: SONiX USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:0C45:8419.0005/input/input17
    [ 882.212377] hid-multitouch 0003:0C45:8419.0005: input,hiddev0,hidraw3: USB HID v1.00 Mouse [SONiX USB Device] on usb-0000:00:14.0-2/input0

    regards
    Hi
    OK, so it needs hid-multitouch built as a kmp.... (probably would even build for SLES 11 SP3) since this is not part of the SLES 12 SP2 kernel.

    Will look at building a KMP rpm for you shortly to test.
  • malcolmlewismalcolmlewis Knowledge Partner
    Hi
    OK, here is a link to the kernel module (KMP) you need to download and install;
    http://download.opensuse.org/repositories/home:/malcolmlewis:/TESTING/SLE-12-SP2_GA_standard/x86_64/hid-multitouch-kmp-default-4.4.21_k4.4.21_69-1.1.x86_64.rpm

    If it works, then there are two things to consider:
    1. If you upgrade the kernel then you need to rebuild this KMP from the src rpm locally to match the new running kernel.
    2. This module is available if you switch from SLES to SLED...
  • MoratorroMoratorro Established Member
    Hi :

    I´ve installed the rpm using zypper install name.rpm
    it only complained about the SH key but its installed now.

    but the screen still wont work.

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    Moratorro wrote: »
    Hi :

    I´ve installed the rpm using zypper install name.rpm
    it only complained about the SH key but its installed now.

    but the screen still wont work.

    regards

    Hi
    OK, might need to setup a modprobe rule, but for unplug the USB and run;
    modprobe hid-multitouch
    
    Then plug it in and check dmesg output.
  • MoratorroMoratorro Established Member
    Hi

    This is the output

    modprobe : ERROR: module 'hid-multitouch, is unsupported
    then asked me to edit the /etc/modprobe.d/10unsupported-modules.conf and set the aallow_unsupported_modules to 1

    did that and got this

    modprobe: ERROR: could not insert 'hid-multitouch' : numerical result out of range

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    Moratorro wrote: »
    Hi

    This is the output

    modprobe : ERROR: module 'hid-multitouch, is unsupported
    then asked me to edit the /etc/modprobe.d/10unsupported-modules.conf and set the aallow_unsupported_modules to 1

    did that and got this

    modprobe: ERROR: could not insert 'hid-multitouch' : numerical result out of range

    regards
    Hi
    Hmmm, don't see that here, ok might try building locally from the src rpm then.

    So as root user install the following packages;
    zypper in kernel-source kernel-syms make gcc rpm-build
    

    Then as your normal user not root;
    wget  http://download.opensuse.org/repositories/home:/malcolmlewis:/TESTING/SLE-12-SP2_GA_standard/src/hid-multitouch-4.4.21-1.1.src.rpm
    rpmbuild --rebuild hid-multitouch-4.4.21-1.1.src.rpm
    su -
    zypper in -f /home/<YOUR_USER_NAME>/rpmbuild/RPMS/x86_64/hid-multitouch-kmp-default-*
    modprobe hid-multitouch
    
  • MoratorroMoratorro Established Member
    HI

    everything went OK!
    the modprobe shows the same error, but i changed the /etc/modprobe.d/10-unsupported-modules.conf and set it to 1

    modprobe hid-multitouchmodprobe: ERROR: module 'hid_multitouch' is unsupported
    modprobe: ERROR: Use --allow-unsupported or set allow_unsupported_modules 1 in
    modprobe: ERROR: /etc/modprobe.d/10-unsupported-modules.conf
    modprobe: ERROR: could not insert 'hid_multitouch': Operation not permitted
    linux-xs19:/home/pos # vi /etc/modprobe.d/10-unsupported-modules.conf

    this is the dmesg
    dmesg | grep usb

    [ 1128.985864] usb 3-2: new low-speed USB device number 6 using xhci_hcd
    [ 1129.118799] usb 3-2: New USB device found, idVendor=0c45, idProduct=8419
    [ 1129.118801] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    [ 1129.118802] usb 3-2: Product: USB Device
    [ 1129.118803] usb 3-2: Manufacturer: SONiX
    [ 1129.126296] input: SONiX USB Device as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:0C45:8419.0004/input/input13
    [ 1129.126402] hid-multitouch 0003:0C45:8419.0004: input,hiddev0,hidraw3: USB HID v1.00 Mouse [SONiX USB Device] on usb-0000:00:14.0-2/input0

    so where do we go from here?

    a millions tks!
  • malcolmlewismalcolmlewis Knowledge Partner
    Hi
    So the device is still not working as a touchscreen?
  • MoratorroMoratorro Established Member
    HI

    NOp, everything was isntalled and configured, but the touchscreen doesnt work yet.

    regards
  • malcolmlewismalcolmlewis Knowledge Partner
    Moratorro wrote: »
    HI

    NOp, everything was isntalled and configured, but the touchscreen doesnt work yet.

    regards
    Hi
    So if you unplug the usb from the screen and check dmesg output it shows being removed?

    When plugged in what is the verbose output from lsusb (as root user) for the device?
Sign In or Register to comment.