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

[cocoa117]

That makes sense. I have not had a chance to try my laptop with another monitor yet, but I think that the issue might be with the screen resolution that is currently set with the wacom driver. Can you post the results of

xinput list-props 'N-Trig Pen stylus'

If the stylus is not called 'N-Trig Pen stylus', replace it with the name or id that it is defined in xinput --list.

Here it is the result of xinput --list

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ N-Trig Pen id=11 [slave pointer (2)]
⎜ ↳ N-Trig MultiTouch id=12 [slave pointer (2)]
⎜ ↳ N-Trig Touchscreen id=13 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)]
⎜ ↳ Macintosh mouse button emulation 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)]
↳ CNF8038 id=10 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]

And this is the 'N-Trig Pen', I think that is close enough

xinput list-props 'N-Trig Pen'
Device 'N-Trig Pen':
Device Enabled (147): 1
Device Accel Profile (269): 0
Device Accel Constant Deceleration (270): 1.000000
Device Accel Adaptive Deceleration (272): 1.000000
Device Accel Velocity Scaling (273): 10.000000
Evdev Reopen Attempts (263): 10
Evdev Axis Inversion (274): 0, 0
Evdev Axis Calibration (275): <no items>
Evdev Axes Swap (276): 0
Axis Labels (277): "Abs X" (266), "Abs Y" (267), "Abs Pressure" (268)
Button Labels (278): "Button 0" (265), "Button Unknown" (264), "Button Unknown" (264), "Button Wheel Up" (151), "Button Wheel Down" (152)
Evdev Middle Button Emulation (279): 2
Evdev Middle Button Timeout (280): 50
Evdev Wheel Emulation (281): 0
Evdev Wheel Emulation Axes (282): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (283): 10
Evdev Wheel Emulation Timeout (284): 200
Evdev Wheel Emulation Button (285): 4
Evdev Drag Lock Buttons (286): 0

[Ayuthia]

Here it is the result of xinput --list

⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ N-Trig Pen id=11 [slave pointer (2)]
⎜ ↳ N-Trig MultiTouch id=12 [slave pointer (2)]
⎜ ↳ N-Trig Touchscreen id=13 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)]
⎜ ↳ Macintosh mouse button emulation 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)]
↳ CNF8038 id=10 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)]

And this is the 'N-Trig Pen', I think that is close enough

xinput list-props 'N-Trig Pen'
Device 'N-Trig Pen':
Device Enabled (147): 1
Device Accel Profile (269): 0
Device Accel Constant Deceleration (270): 1.000000
Device Accel Adaptive Deceleration (272): 1.000000
Device Accel Velocity Scaling (273): 10.000000
Evdev Reopen Attempts (263): 10
Evdev Axis Inversion (274): 0, 0
Evdev Axis Calibration (275): <no items>
Evdev Axes Swap (276): 0
Axis Labels (277): "Abs X" (266), "Abs Y" (267), "Abs Pressure" (268)
Button Labels (278): "Button 0" (265), "Button Unknown" (264), "Button Unknown" (264), "Button Wheel Up" (151), "Button Wheel Down" (152)
Evdev Middle Button Emulation (279): 2
Evdev Middle Button Timeout (280): 50
Evdev Wheel Emulation (281): 0
Evdev Wheel Emulation Axes (282): 0, 0, 4, 5
Evdev Wheel Emulation Inertia (283): 10
Evdev Wheel Emulation Timeout (284): 200
Evdev Wheel Emulation Button (285): 4
Evdev Drag Lock Buttons (286): 0

Ok. From the information above, you are using the evdev driver for the stylus. Lucid should be defaulting the stylus to the wacom driver. Do you have something defined in /etc/X11/xorg.conf.d directory or /etc/X11/xorg.conf file to define your stylus to evdev (or do you prefer your stylus to be using the evdev driver)?

Currently the recommendation is to use the wacom driver for the stylus because it will allow you to define the button on the stylus to be set as a right click. The other nice feature is that you can define the resolution in the wacom driver. For me, when I am checking the the properties using the wacom driver, it looks like:

Device 'N-Trig Pen stylus':
        Device Enabled (148):   1
        Device Accel Profile (267):     0
        Device Accel Constant Deceleration (268):       1.000000
        Device Accel Adaptive Deceleration (270):       1.000000
        Device Accel Velocity Scaling (271):    10.000000
        Wacom Tablet Area (289):        0, 0, 9600, 7200
        Wacom Rotation (290):   0
        Wacom Pressurecurve (291):      0, 0, 100, 100
        Wacom Serial IDs (292): 1, 0, 2, 0
        Wacom TwinView Resolution (293):        0, 0, 0, 0
        Wacom Display Options (294):    -1, 0, 1
        Wacom Screen Area (295):        0, 0, 1280, 800
        Wacom Proximity Threshold (296):        42
        Wacom Capacity (297):   -1
        Wacom Pressure Threshold (298): 27
        Wacom Sample and Suppress (299):        2, 4
        Wacom Enable Touch (300):       0
        Wacom Hover Click (301):        1
        Wacom Enable Touch Gesture (302):       0
        Wacom Touch Gesture Parameters (303):   50, 20, 250
        Wacom Tool Type (304):  "STYLUS" (306)
        Wacom Button Actions (305):     "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0)

You can see that my Wacom Screen Area is listed as 0, 0, 1280, 800. I am thinking that yours is showing different values for the last two.

[Nphyx]

Hey guys, long time no see (again). I've been absolutely swamped at work and haven't even attempted to get n-trig fully functional in a while. Just popping in to pass on a couple discoveries.

I'm running Maverick now under Ubuntu (not Kubuntu). Everything works great out of the box. I had to install xserver-xorg-input-wacom and use the xorg.conf.d/10-wacom.conf to get rotation working, but xsetwacom was not playing nicely with my stylus at -all-. Here's what I get with xsetwacom list dev:

CNF8038     stylus

Attempting to set properties on "stylus" results in:

Error (2): WacomConfigOpenDevice: No such device
Set: Failed to open device 'stylus'

Attempting to set anything on CNF8083 fails silently.

Fortunately, I discovered I can now use xinput set-prop to set wacom rotation

I modified rafiyr's zsh script to use that method instead (I think it was rafiyr, sorry if I mis-attributed).

#!/bin/zsh

# if we wanted to shift through all settings in xrandr order
order=(normal left inverted right)

# but if we just want to toggle between two:
order=(normal right)

wacom_names=(none ccw half cw)
xrandr_order=(normal left inverted right)
old=$xrandr_order[1]
if [ -e /dev/shm/rotation ]
then
	old=`cat /dev/shm/rotation`
fi


function rotate()
{
	# shift until we're at the current if its on the list
	z=();
	while [ $#order > 0 -a $order[1] != $old ]
	do
		z=($z $order[1]);
		shift order;
	done

	# if not found, just reset the list
	#
	if [ $#order = 0 ] 
	then
		order=($z)
		return
	fi

	order=($order $z)

	for ((x=0;x<$1;x++))
	do
		t=$order[1];
		shift order
		order=($order $t)
	done
}
function all_rotate()
{
	order=($xrandr_order)
	rotate $*
}

function reorient()
{
	orientation=$1
	topx=0
	topy=0
	bottomx=9600
	bottomy=7200
	swap=0
	invert_x=0
	invert_y=0

	real_topx=0
	real_topy=0
	real_bottomx=9600
	real_bottomy=7200


	case $orientation in
		[0-3] )
			reorient $xrandr_order[`expr $orientation + 1`]
		;;
		normal | untablet )
			wacom=0
			orientation=normal
			swap=0
			invert_x=0
			invert_y=0
		;;
		left )
			wacom=2
			swap=1
			invert_x=1
			invert_y=0
			tmp=$bottomy
			bottomy=$bottomx
			bottomx=$tmp
			orientation=left
		;;
		inverted )
			wacom=3
			swap=0
			invert_x=1
			invert_y=1
		;;
		right | tablet )
			wacom=1
			swap=1
			invert_x=0
			invert_y=1
			tmp=$bottomy
			bottomy=$bottomx
			bottomx=$tmp
			orientation=right
		;;
		180 )
			all_rotate 2;
			reorient $order[1];
			return;
		;;
		ccw )
			all_rotate 1;
			reorient $order[1];
			return
		;;
		cw )
			all_rotate `expr $#xrandr_order - 1`
			reorient $order[1];
			return
		;;
		next )
			rotate 1;
			reorient $order[1];
			return
		;;
		prev )
			rotate `expr $#order - 1`
			reorient $order[1];
			return
		;;
		* )
			return
		;;
	esac

	if [ $old != $orientation -o 1 ]
	then
		xrandr -o $orientation
		for dev in `xinput list | grep N-Trig | grep pointer | grep slave | cut -c 55-56`
		do
			case `xinput list-props "$dev" |& grep "Evdev\|Wacom" | head -1 | sed 's/^\s//' | cut -f 1 -d ' '` in
				Evdev )
					xinput set-prop "$dev" "Evdev Axes Swap" $swap
					xinput set-prop "$dev" "Evdev Axis Inversion" $invert_x $invert_y
					xinput set-prop "$dev" "Evdev Axis Calibration" $topx $bottomx $topy $bottomy
				;;
				Wacom )
					res=`xinput list-props "$dev" | grep -c "Wacom Rotation"`
					if [ $res ]
					then
						xinput set-prop "$dev" "Wacom Rotation" $wacom
					fi
				;;
			esac
		done
#		if [ `ps -u $USER | grep -c easystroke` -gt 0 ]
#		then
#			pkill easystroke
#			easystroke &
#		fi
	else
		print "orientation is $orientation\n";
	fi

	echo $orientation > /dev/shm/rotation

}

reorient $1

It works great! Thanks

[Favux]

Hi Nphyx,

Thanks for the script. Added to the HOW TO.

[rafiyr]

Hey guys, long time no see (again). I've been absolutely swamped at work and haven't even attempted to get n-trig fully functional in a while. Just popping in to pass on a couple discoveries.

I'm running Maverick now under Ubuntu (not Kubuntu). Everything works great out of the box. I had to install xserver-xorg-input-wacom and use the xorg.conf.d/10-wacom.conf to get rotation working, but xsetwacom was not playing nicely with my stylus at -all-. Here's what I get with xsetwacom list dev:

It works great! Thanks

I can confirm that certainly looks a lot like my script, so I'll take the blame

Thank you for migrating the script to xinput properties. Moving forward, I think it makes a lot of sense for the supported features.

In other news, it sounds like more people are becoming aware of the problem and there's increasing interest in making these things follow the display orientation out of the box. Hopefully we'll see sane support and configurations within a year.

[Nphyx]

Well, I downgraded Xorg to 1.8.2 in an attempt to resolve another issue (getting fglrx running in Maverick) and now I've lost touch. I still have stylus, and I've confirmed that I still have the device registered in xinput --list, and I'm getting output via xxd /dev/input/n-trig-touch. I also have the ntrig.ko installed by Ayuthia's auto-install script. I have the udev rules and xorg.conf.d/10-wacom.conf described above, which were working for me before.

I browsed through the thread, but the solution for similar problems seemed to be to update ntrig.ko, but I've already done that; any other thoughts, anyone? It's a real mystery as it should work out of the box with Maverick's xorg packages.

[Ayuthia]

Well, I downgraded Xorg to 1.8.2 in an attempt to resolve another issue (getting fglrx running in Maverick) and now I've lost touch. I still have stylus, and I've confirmed that I still have the device registered in xinput --list, and I'm getting output via xxd /dev/input/n-trig-touch. I also have the ntrig.ko installed by Ayuthia's auto-install script. I have the udev rules and xorg.conf.d/10-wacom.conf described above, which were working for me before.

I browsed through the thread, but the solution for similar problems seemed to be to update ntrig.ko, but I've already done that; any other thoughts, anyone? It's a real mystery as it should work out of the box with Maverick's xorg packages.

Have you looked at /var/log/Xorg.0.log. I am guessing that the touch was rejected by xorg. Feel free to post the log also if you like.

I have not tried downgrading xorg yet. I am still trying to figure out why the Broadcom STA driver is failing partway through the downloads.

[Nphyx]

I'm still not sure what the cause was, but after painstakingly removing every Xorg package, downloading all the packages and dependencies manually from launchpad and installing via dpkg everything is working correctly again. You'd think there would be an easier way to do this, but there's no "downgrade package x to version y and downgrade all dependencies with it" button - at least not if the version you want to downgrade to is not in your archives or on the repository list anymore. It took about 2 1/2 hours to get everything and hand-check all the depends. Anyway, I'm just bitching, it works now

[Ayuthia]

I'm still not sure what the cause was, but after painstakingly removing every Xorg package, downloading all the packages and dependencies manually from launchpad and installing via dpkg everything is working correctly again. You'd think there would be an easier way to do this, but there's no "downgrade package x to version y and downgrade all dependencies with it" button - at least not if the version you want to downgrade to is not in your archives or on the repository list anymore. It took about 2 1/2 hours to get everything and hand-check all the depends. Anyway, I'm just bitching, it works now

Hopefully the next release of the fglrx driver will work with xorg-server-1.9. I just saw that you switched over to Ubuntu to test. I am currently using the Netbook Edition mainly to see how many multitouch gestures has been placed into Unity. So far I have found:

three finger drag - moves windows
three finger single-tap - shows the desktop.
four finger single-tap - brings up the task switcher

Nothing fancy quite yet, but it is exciting to see the progress being made this quickly.

Nphyx (you have a Dell, right) or rafiyr, does the mouse touchpad provide multiouch capabilities through Synaptics? The HP does not seem to do that in Linux yet.

[Nphyx]

Nah I have a tx2z, and still running Vista firmware (not willing/able to install Win7). Hoping they'll put out a linux firmware updater sometime soon, but no dice so far.

Edit: oh I misread you. No as far as I know the touchpad doesn't have multitouch support on the HP. At least it never reports that it does. I don't think the hardware supports it?