Results 1 to 4 of 4

Thread: Toughbook touchscreen support lost after upgrading to Kali Rolling 2016.2

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Join Date
    2016-Oct
    Posts
    2

    Unhappy Toughbook touchscreen support lost after upgrading to Kali Rolling 2016.2

    Hello everyone.

    Before posting this Q I did a few searches for "Fujitsu", "Toughbook" and "2016.2" with no positive results. I hope this is not a double post of someone else's.

    I have been using Kali all the way since BT5 died and I have been using it extensively on a Panasonic Toughbook CF-19 without any major issues, at least not that I can remember now. All base hardware (including the touch screen) used to work just fine and after minor tweaks even touch screen right-click emulation was perfect for drawing on-screen in Gimp for example.

    A while ago I prepared a new live USB stick with Kali 2016.2 and suddenly I had no touchscreen.
    Maybe not a complete catastrophe but since I usually leave my "business card" in the form of a small illustration it's a bit annoying not being able to draw on-screen anymore.

    When I noticed that I had lost my touchscreen I tried to prepare a live stick with the 32 bit version but the result is the same. The debug info provided is from the 64-bit version which I usually run.



    The little debug info I have collected so far is provided below.

    The touch panel is detected as can be seen here:

    root@BXVBOOUQ:~# dmesg | grep -i touch
    [ 3.377275] usb 3-2: Product: USB Touch Panel
    [ 3.401464] input: Fujitsu Component USB Touch Panel as /devices/pci0000:00/0000:00:1d.0/usb3/3-2/3-2:1.0/0003:0430:0530.0001/input/input9
    [ 3.401788] hid-generic 0003:0430:0530.0001: input,hidraw0: USB HID v1.00 Device [Fujitsu Component USB Touch Panel] on usb-0000:00:1d.0-2/input0
    [ 4.131502] input: PS/2 BYD TouchPad as /devices/platform/i8042/serio4/input/input8


    When I do a xinput list however there is no longer any Fujitsu Component USB Touch Panel

    root@BXVBOOUQ:~# xinput list
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ PS/2 BYD TouchPad id=10 [slave pointer (2)]
    ⎜ ↳ Logitech M570 id=12 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=9 [slave keyboard (3)]
    ↳ Panasonic Laptop Support id=11 [slave keyboard (3)]



    And of course there is no calibratable device:

    root@BXVBOOUQ:~# xinput_calibrator
    Error: No calibratable devices found.


    Nor do lsusb show anything that I recognize as the Fujitsu device:

    root@BXVBOOUQ:~# lsusb
    Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 010 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
    Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 004 Device 003: ID 044e:3001 Alps Electric Co., Ltd UGTZ4 Bluetooth
    Bus 004 Device 002: ID 1410:2420 Novatel Wireless Expedite EU850D/EU860D/EU870D
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 003 Device 002: ID 0430:0530 Sun Microsystems, Inc.
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 006 Device 002: ID 0781:5567 SanDisk Corp. Cruzer Blade
    Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub




    A modinfo usbtouchscreen on the other hand seems to indicate that the kernel module is loaded and the output looks very much the same as it did on the 2016.1 Rolling (except the vermagic string):

    root@BXVBOOUQ:~# modinfo usbtouchscreen
    filename: /lib/modules/4.6.0-kali1-amd64/kernel/drivers/input/touchscreen/usbtouchscreen.ko
    alias: mtouchusb
    alias: itmtouch
    alias: touchkitusb
    license: GPL
    description: USB Touchscreen Driver
    author: Daniel Ritz <[email protected]>
    alias: usb:v7374p0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v04E7p0020d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v1870p0001d*dc*dsc*dp*ic0Aisc00ip00in*
    alias: usb:v10F0p2002d*dc*dsc*dp*ic0Aisc00ip00in*
    alias: usb:v0664p0306d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0664p0309d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v14C8p0003d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v1AC7p0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0F92p0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v08F2p00F4d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v08F2p00CEd*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v08F2p007Fd*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0DFCp0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v1391p1000d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v6615p0012d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v6615p0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v595Ap0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0AFAp03E8d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0637p0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v1234p5678d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v16E3pF9E9d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0403pF9E9d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0596p0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v134Cp0004d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v134Cp0003d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v134Cp0002d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v134Cp0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v1234p0002d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v1234p0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0EEFp0002d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0EEFp0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0123p0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v3823p0002d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v3823p0001d*dc*dsc*dp*ic*isc*ip*in*
    alias: usb:v0EEFp0002d*dc*dsc*dp*ic03isc*ip*in*
    alias: usb:v0EEFp0001d*dc*dsc*dp*ic03isc*ip*in*
    depends: usbcore
    intree: Y
    vermagic: 4.6.0-kali1-amd64 SMP mod_unload modversions
    parm: swap_xy:If set X and Y axes are swapped. (bool)
    parm: hwcalib_xy:If set hw-calibrated X/Y are used if available (bool)


    The output from xinput used to look like this in Kali rolling 2016.1 (with the USB touch panel showing up as device nr 9):

    xinput list
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ PS/2 Generic Mouse id=11 [slave pointer (2)]
    ⎜ ↳ Fujitsu Component USB Touch Panel id=9 [slave pointer (2)]
    ⎣ Virtual core keyboard id=3 [master keyboard (2)]
    ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
    ↳ Power Button id=6 [slave keyboard (3)]
    ↳ Video Bus id=7 [slave keyboard (3)]
    ↳ Power Button id=8 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
    ↳ Panasonic Laptop Support id=12 [slave keyboard (3)]


    Is there some driver for X11 that's missing??

    I have been looking around the net for a solution but haven't been able to find something useful for my noobish level of incompetence. I.I.R.C I have never been forced to compile or install any proprietary drivers for the touch panel but I might be wrong here and just can't remember it with my nitrogen-bubble-damaged brain (I used to be a military diver and I've had my fair share of oopses). In that case the driver has been sitting in my system through a long chain of upgrades without needing any attention. Now I'm completely stuck since I'm noobish enough not to be 100% proficient in Linux tweaking.

    Anyone out there who can guide me in the right direction to solve this?

    Best regards

    // C0RE

  2. #2
    Join Date
    2017-Feb
    Posts
    1
    Just thought I would jump in here too. I used kali 2? IDK 6mo. ago via live USB and the touchscreen did work. I've tried each of the current version desktop environs without success. It is interesting to note that mint 17/18 are on the same kernel and the touch panel works there. The 19 doesn't really have enough grunt to really run kali in a Vbox - but if you want to go through that pain, you could run kali on mint or other distro where the TS is functional. The optimal resolution would be if one of the devs could take a look at what changes were made and enable the Fujitsu panel. Buy the way my cf-19 shows the same thing as yours, it's recognized

  3. #3
    Join Date
    2016-Oct
    Location
    /dev/sda
    Posts
    1,012
    Quote Originally Posted by cws View Post
    Just thought I would jump in here too. I used kali 2? IDK 6mo. ago via live USB and the touchscreen did work. I've tried each of the current version desktop environs without success. It is interesting to note that mint 17/18 are on the same kernel and the touch panel works there. The 19 doesn't really have enough grunt to really run kali in a Vbox - but if you want to go through that pain, you could run kali on mint or other distro where the TS is functional. The optimal resolution would be if one of the devs could take a look at what changes were made and enable the Fujitsu panel. Buy the way my cf-19 shows the same thing as yours, it's recognized
    Can you show the output of /etc/modprobe.d/blacklist.conf and modinfo hid_multitouch | head and modinfo hid_multitouch | head?

  4. #4
    Join Date
    2017-Mar
    Posts
    1
    I am having the same issue. Here is the output from modinfo hid_multitouch|head:
    filename: /lib/modules/4.6.0-kali1-686-pae/kernel/drivers/hid/hid-multitouch.ko
    license: GPL
    description: HID multitouch panels
    author: Benjamin Tissoires <[email protected]>
    author: Stephane Chatty <[email protected]>
    alias: hid:b*g0004v*p*
    alias: hid:b*g0002v*p*
    alias: hid:b0003g0002v00001477p00001025
    alias: hid:b0003g0002v00001477p00001026
    alias: hid:b0003g0002v00001477p00001024


    There is no file named blacklist.conf in /etc/modprobe.d

    As others have stated, Mint recognizes the touchscreen without issue.

Similar Threads

  1. Lost internet access since upgrading Kali
    By kali-man in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2019-12-23, 01:24
  2. toughbook touchscreen not working
    By r0tati0n in forum TroubleShooting Archive
    Replies: 4
    Last Post: 2018-06-01, 16:57
  3. issues upgrading from kali 2.0 to 2016.1 rolling.
    By gunner_k in forum TroubleShooting Archive
    Replies: 3
    Last Post: 2016-03-11, 22:37
  4. Replies: 2
    Last Post: 2016-02-09, 12:27
  5. Touchscreen only detects edges, and other Toughbook U1 Ultra issues
    By Sentinal in forum TroubleShooting Archive
    Replies: 0
    Last Post: 2014-04-14, 16:19

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •