Page 127 of 169 FirstFirst ... 2777117125126127128129137 ... LastLast
Results 1,261 to 1,270 of 1689

Thread: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

  1. #1261
    Join Date
    Apr 2007
    Location
    Mount Horeb, WI
    Beans
    4,312
    Distro
    Kubuntu Development Release

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Quote Originally Posted by dmegg View Post
    Using sudo xxd -g1 /dev/input/event9 gives me output whenever I touch the screen and move my finger around. It seems to be just XOrg that's not using the touchscreen as a pointer. I noted the following (twice) in the XOrg log:

    Code:
    [    23.642] (II) config/udev: Adding input device N-Trig Touchscreen (/dev/inpu
    t/event9)
    [    23.642] (**) N-Trig Touchscreen: Applying InputClass "evdev touchscreen catchall"
    [    23.642] (**) N-Trig Touchscreen: always reports core events
    [    23.642] (**) N-Trig Touchscreen: Device: "/dev/input/event9"
    [    23.681] (II) N-Trig Touchscreen: Found absolute axes
    [    23.681] (II) N-Trig Touchscreen: Found x and y absolute axes
    [    23.681] (II) N-Trig Touchscreen: Found absolute touchscreen
    [    23.681] (II) N-Trig Touchscreen: Configuring as touchscreen
    [    23.681] (**) N-Trig Touchscreen: YAxisMapping: buttons 4 and 5
    [    23.681] (**) N-Trig Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [    23.681] (II) XINPUT: Adding extended input device "N-Trig Touchscreen" (type: TOUCHSCREEN)
    [    23.681] (II) N-Trig Touchscreen: initialized for absolute axes.
    [    23.682] (II) config/udev: Adding input device N-Trig Touchscreen (/dev/input/mouse2)
    [    23.682] (II) No input driver/identifier specified (ignoring)
    Does the last line mean that the touchscreen is never being attached? Is there a way I can manually attach it as a pointer from inside an X session?
    The ignoring portion is referring to the /dev/input/mouse and not the touchscreen event.

    Can you try out:
    Code:
    sudo evtest /dev/input/event9
    to see if it reports anything? You might need to do this in the Console (via control-alt-F2). If you do get any results, can you let us know what codes you get?

    EDIT:
    I forgot to mention that it looks like the kernel module is working now because you are getting a response from the event. The previous version should not have reported anything.
    Last edited by Ayuthia; October 22nd, 2010 at 04:45 PM.

  2. #1262
    Join Date
    Nov 2005
    Beans
    21
    Distro
    Ubuntu Breezy 5.10

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Quote Originally Posted by Ayuthia View Post
    Can you try out:
    Code:
    sudo evtest /dev/input/event9
    to see if it reports anything? You might need to do this in the Console (via control-alt-F2). If you do get any results, can you let us know what codes you get?
    The command worked fine in gnome-terminal. Here's the beginning of the output (the events arrived when I moved my finger around the screen):

    Code:
    david@snape:~$ sudo evtest /dev/input/event9
    [sudo] password for david: 
    Input driver version is 1.0.1
    Input device ID: bus 0x3 vendor 0x1b96 product 0x1 version 0x110
    Input device name: "N-Trig Touchscreen"
    Supported events:
      Event type 0 (Sync)
      Event type 1 (Key)
        Event code 330 (Touch)
        Event code 333 (Tool Doubletap)
      Event type 3 (Absolute)
        Event code 0 (X)
          Value   4469
          Min        0
          Max     9600
        Event code 1 (Y)
          Value    477
          Min        0
          Max     7200
        Event code 40 (Misc)
          Value      0
          Min        0
          Max        1
        Event code 41 (?)
          Value      0
          Min        0
          Max        1
      Event type 4 (Misc)
        Event code 4 (ScanCode)
    Testing ... (interrupt to exit)
    Event: time 1287765860.572640, type 1 (Key), code 330 (Touch), value 1
    Event: time 1287765860.572647, type 1 (Key), code 333 (Tool Doubletap), value 1
    Event: time 1287765860.572649, type 3 (Absolute), code 0 (X), value 6264
    Event: time 1287765860.572652, type 3 (Absolute), code 1 (Y), value 2402
    Event: time 1287765860.572655, -------------- Report Sync ------------
    Event: time 1287765860.580711, type 3 (Absolute), code 1 (Y), value 2408
    Event: time 1287765860.580721, -------------- Report Sync ------------
    Event: time 1287765860.587640, type 3 (Absolute), code 0 (X), value 6263
    Event: time 1287765860.587653, type 3 (Absolute), code 1 (Y), value 2417
    Event: time 1287765860.587655, -------------- Report Sync ------------
    Event: time 1287765860.595664, type 3 (Absolute), code 0 (X), value 6261
    Event: time 1287765860.595669, type 3 (Absolute), code 1 (Y), value 2428
    Event: time 1287765860.595671, -------------- Report Sync ------------
    Event: time 1287765860.602668, type 3 (Absolute), code 0 (X), value 6258
    Event: time 1287765860.602673, type 3 (Absolute), code 1 (Y), value 2443
    Event: time 1287765860.602676, -------------- Report Sync ------------
    Event: time 1287765860.610666, type 3 (Absolute), code 0 (X), value 6254
    Event: time 1287765860.610671, type 3 (Absolute), code 1 (Y), value 2462
    Event: time 1287765860.610674, -------------- Report Sync ------------
    Event: time 1287765860.617663, type 3 (Absolute), code 0 (X), value 6250
    Event: time 1287765860.617668, type 3 (Absolute), code 1 (Y), value 2488
    Event: time 1287765860.617670, -------------- Report Sync ------------
    Event: time 1287765860.625635, type 3 (Absolute), code 0 (X), value 6247
    Event: time 1287765860.625640, type 3 (Absolute), code 1 (Y), value 2517
    Event: time 1287765860.625644, -------------- Report Sync ------------
    Event: time 1287765860.632653, type 3 (Absolute), code 0 (X), value 6243
    Event: time 1287765860.632659, type 3 (Absolute), code 1 (Y), value 2549
    Event: time 1287765860.632661, -------------- Report Sync ------------
    Event: time 1287765860.640641, type 3 (Absolute), code 0 (X), value 6239
    Event: time 1287765860.640649, type 3 (Absolute), code 1 (Y), value 2586
    Event: time 1287765860.640652, -------------- Report Sync ------------
    Event: time 1287765860.647664, type 3 (Absolute), code 0 (X), value 6236
    Event: time 1287765860.647676, type 3 (Absolute), code 1 (Y), value 2623
    Event: time 1287765860.647680, -------------- Report Sync ------------
    Event: time 1287765860.655636, type 3 (Absolute), code 0 (X), value 6233
    Event: time 1287765860.655643, type 3 (Absolute), code 1 (Y), value 2658

  3. #1263
    Join Date
    Apr 2007
    Location
    Mount Horeb, WI
    Beans
    4,312
    Distro
    Kubuntu Development Release

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    I was wrong about the kernel module. I just removed the firmware from my touchscreen and was unable to get it to work with that version.

    However, the patch that I created in launchpad is working. If you don't mind, can you try the following:
    Code:
    sudo dkms remove -m ntrig -v 20100504 --all
    cd /usr/src
    sudo wget http://linuxfans.keryxproject.org/packages/ntrig/dkms/maverick/ntrig-20101020.tar.bz2
    sudo tar -xvjf ntrig-20101020.tar.bz2
    sudo dkms add -m ntrig -v 20101020
    sudo dkms build -m ntrig -v 20101020
    sudo dkms install -m ntrig -v 20101020
    You will then need to restart.

    From what I can tell, the evdev driver does not like the doubletap that is coming in.

    Hopefully this should do the trick.

  4. #1264
    Join Date
    Nov 2005
    Beans
    21
    Distro
    Ubuntu Breezy 5.10

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Quote Originally Posted by Ayuthia View Post
    However, the patch that I created in launchpad is working. If you don't mind, can you try the following:
    Code:
    sudo dkms remove -m ntrig -v 20100504 --all
    cd /usr/src
    sudo wget http://linuxfans.keryxproject.org/packages/ntrig/dkms/maverick/ntrig-20101020.tar.bz2
    sudo tar -xvjf ntrig-20101020.tar.bz2
    sudo dkms add -m ntrig -v 20101020
    sudo dkms build -m ntrig -v 20101020
    sudo dkms install -m ntrig -v 20101020
    You will then need to restart.
    Victory! Single-touch is working in Maverick on my TX2 with the Vista N-Trig drivers. Thanks for all your help and patience.

  5. #1265
    Join Date
    Apr 2010
    Beans
    14

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    I would like to add that I have a very similar setup and I have also successfully followed the steps to getting touch in maverick. Thanks.

    Now, when are multitouch gestures going to arrive?!
    Last edited by lps1; October 23rd, 2010 at 01:58 PM.

  6. #1266
    Join Date
    Nov 2005
    Beans
    21
    Distro
    Ubuntu Breezy 5.10

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Quote Originally Posted by lps1 View Post
    I would like to add that I have a very similar setup and I have also successfully followed the steps to getting touch in maverick. Thanks.

    Now, when are multitouch gestures going to arrive?!
    From what I understand, to get multitouch you have to be able to run Windows 7 and update to the newest N-Trig firmware. After that, you probably need to install utouch or something similar, but since I can't get past step 1, I can't really say right now.

  7. #1267
    Join Date
    Aug 2005
    Beans
    33

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Hey Guys. I went ahead and put Windows 7 on my tx2 so I could upgrade to the latest firmware - and after doing so all I get is Eraser and Stylus in the xsetwacom list. I cannot disable/enable touch - and touch is definitely working. This is all on Maverick.

    xsetwacom list
    N-Trig Pen eraser ERASER
    N-Trig Pen stylus STYLUS

    xsetwacom -v list

    ... Display is '(null)'.
    ... 'list' requested.
    ... Found device 'Virtual core XTEST pointer' (4).
    ... Found device 'Virtual core XTEST keyboard' (5).
    ... Found device 'Power Button' (6).
    ... Found device 'Video Bus' (7).
    ... Found device 'Power Button' (8).
    ... Found device 'Sleep Button' (9).
    ... Found device 'HP Webcam' (10).
    ... Found device 'N-Trig Touchscreen' (11).
    ... Found device 'N-Trig Pen eraser' (12).
    N-Trig Pen eraser ERASER
    ... Found device 'N-Trig Pen stylus' (13).
    N-Trig Pen stylus STYLUS
    ... Found device 'N-Trig MultiTouch' (14).
    ... Found device 'AT Translated Set 2 keyboard' (15).
    ... Found device 'SynPS/2 Synaptics TouchPad' (16).
    ... Found device 'HP WMI hotkeys' (17).


    xinput list
    ⎡ Virtual core pointer id=2 [master pointer (3)]
    ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
    ⎜ ↳ N-Trig Touchscreen id=11 [slave pointer (2)]
    ⎜ ↳ N-Trig Pen eraser id=12 [slave pointer (2)]
    ⎜ ↳ N-Trig Pen stylus id=13 [slave pointer (2)]
    ⎜ ↳ N-Trig MultiTouch id=14 [slave pointer (2)]
    ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [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)]
    ↳ Sleep Button id=9 [slave keyboard (3)]
    ↳ HP Webcam id=10 [slave keyboard (3)]
    ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
    ↳ HP WMI hotkeys id=17 [slave keyboard (3)]

    Also - I followed the DKMS instructions on these last two pages and it made no difference. What could I be missing?
    Last edited by markginter24; October 24th, 2010 at 12:08 AM.

  8. #1268
    Join Date
    Nov 2008
    Beans
    9,635
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Hi markginter24,

    It's the N-trig snippet Rafi submitted to the LWP for inclusion in the 50-wacom.conf. It sets the stylus up on wacom but lets touch fall through to the evdev driver. You can test it by using the evdev touch on and off commands. To enable wacom for touch you'll need to change the snippet from:
    Code:
    Section "InputClass"
     	Identifier "Wacom N-Trig class"
    	MatchProduct "HID 1b96:0001|N-Trig Pen"
     	MatchDevicePath "/dev/input/event*"
     	Driver "wacom"
    	Option "Button2" "3"
    EndSection
    to
    Code:
    Section "InputClass"
     	Identifier "Wacom N-Trig class"
    	MatchProduct "HID 1b96:0001"
     	MatchDevicePath "/dev/input/event*"
     	Driver "wacom"
    	Option "Button2" "3"
    EndSection
    and then use an xsetwacom script to set up the stylus and multitouch.

  9. #1269
    Join Date
    Aug 2005
    Beans
    33

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Forgive my ignorance - but I'm having a deal of a time trying to find the evdev commands to enable/disable touch. Where can I go to bookmark the link?

  10. #1270
    Join Date
    Apr 2007
    Location
    Mount Horeb, WI
    Beans
    4,312
    Distro
    Kubuntu Development Release

    Re: HOW TO: Set up the HP TX2z and Dell XT & XT2 (N-trig digitizer) in Ubuntu

    Quote Originally Posted by markginter24 View Post
    Forgive my ignorance - but I'm having a deal of a time trying to find the evdev commands to enable/disable touch. Where can I go to bookmark the link?
    It is found on the first post of this thread under 5b. If you are using evdev:
    To turn off
    Code:
    xinput set-prop 'N-Trig MultiTouch' 'Device Enabled' 0
    To turn on:
    Code:
    xinput set-prop 'N-Trig MultiTouch' 'Device Enabled' 1

Page 127 of 169 FirstFirst ... 2777117125126127128129137 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

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