Wacom tablets in Ubuntu guide/howto

[dsavi]

I'm having a similar problem with mapping my Wacom Bamboo Fun Medium to a single 20" monitor, of course the twinview option is gone. Found something interesting while googling it yesterday:
http://old.nabble.com/-ANNOUNCE--xf8...p30254032.html

First of all: this release does not have TwinView support anymore.
Users running X Servers 1.9 or later have a property in the X server that
provides the same functionality (mapping the tablet to any section of the
screen). Users of servers 1.8 are advised not to update if they require the
TwinView functionality.

That's all well and good, but I have no idea how to map it. My guess is that I'm going to start editing my xorg.conf. I have another problem too however.

The driver doesn't seem to be using enough data from my tablet, the lines aren't smooth if I draw quickly, like this:


Help would be appreciated. It's been a long time since I had so many problems with drivers on Linux.

[Jarvo]

Dear All
Newbie here so sorry if this is the wrong part of the forum to say this, I have Ubuntu 10.10 and a Wacom ET tablet. It works well in WINE photo-shop 6 for both stylus/pressure and eraser It works well with pressure not eraser in GIMP, However the mouse only scrolls downwards (annoying) and the eraser doesn't work in GIMP. I tried making fixes ,downloaded wacom control panel, I don't have wacom tools config and I don't have a clue how terminal really works. i just dumbly paste text that I read on the 'how to' forums. Is there a fix foe the mouse scroll bug? I don't want o undo the good settings I already have. I am getting round it by using a regular mouse on the pad and swapping over to the stylus when I need to use it but it takes up a usb port

[Favux]

Hi Jarvo,

Wecome to Ubuntu forums!

Hi dsavi,

It looks like you are both on Maverick (10.10). In which case you both would probably benefit from getting the latest version of the xf86-input-wacom by cloning its git repository. There was a recent fix for scroll wheels and Bamboo P&T filtering logic, among other things. I don't know for sure if it applies to the Wacom mouse but it's worth a try.

See II. in the Bamboo P & T HOW TO or Section 2 in the Wacom HOW TO.

As I mentioned earlier there's suppose to be a new xsetwacom command (if your xf86-input-wacom is up to date enough) in the form of:

xsetwacom set <device name> "MapToOutput" VGA1

Which is suppose to only apply once, so if you change output you have to rerun it. We haven't figured out how to use it yet. So far trying to run it we get the error:

"Server does not support transformation"

dsavi if you see the same error then I should file a bug report to LWP.

[Jarvo]

Fantastic the wacom graphire 2 now works perfectly. i followed section 1 of the link you gave me and it fell over at section 2. I failed at this point cd ./Desktop tar xjvf util-macros-1.8.0.tar.bz when it said no such file or directory. But when I rebooted it works perfectly. Yipee , I am not to bothered if I only loaded 1/2 the code as long as it works.
Thanks Jarvo

[dsavi]

Thanks for your help again Favux. Updating to the development versions of xf86-input-wacom and input-wacom-0.10.10 (The new linuxwacom) fixed the worse problem (Non-smooth strokes), but I can't seem to get twinview to work, even with MapToOutput. This is probably because xrandr -q doesn't display devices with which I can do xsetwacom set <device> "MapToOutput" <output>. I'm not sure how I could configure my screens so that xrandr detects the devices with nVidia drivers (260.19.06).

[Favux]

Hi dsavi,

Interesting, so you got the wacom.ko from input-wacom 10.10 and that worked better. By the way the plan is pair a release of that now with each point release of xf86-input-wacom. So you'll be back to getting the whole LWP package.

What's your output of:

xrandr -q --verbose

look like?

If you're using the proprietary Nvidia driver isn't there a configuration applet that has multimonitor setup? Then given its Nvidia the changes would show up in your xorg.conf in /etc/X11 I'd think.

[dsavi]

Yes, there is nvidia-settings which I use for configuring Twinview with my 2x20" monitors, works like a charm. The changes should show up, it edits xorg.conf and requires root privileges to run.

xrandr -q --verbose:

Screen 0: minimum 1680 x 1050, current 3360 x 1050, maximum 3360 x 1050
default connected 3360x1050+0+0 (0x161) normal (normal) 0mm x 0mm
	Identifier: 0x160
	Timestamp:  3005835
	Subpixel:   unknown
	Clones:    
	CRTC:       0
	CRTCs:      0
	Transform:  1.000000 0.000000 0.000000
	            0.000000 1.000000 0.000000
	            0.000000 0.000000 1.000000
	           filter: 
  3360x1050 (0x161)  176.4MHz *current
        h: width  3360 start    0 end    0 total 3360 skew    0 clock   52.5KHz
        v: height 1050 start    0 end    0 total 1050           clock   50.0Hz
  1680x1050 (0x194)   90.0MHz
        h: width  1680 start    0 end    0 total 1680 skew    0 clock   53.5KHz
        v: height 1050 start    0 end    0 total 1050           clock   51.0Hz
  3360x1050 (0x1c6)  179.9MHz
        h: width  3360 start    0 end    0 total 3360 skew    0 clock   53.5KHz
        v: height 1050 start    0 end    0 total 1050           clock   51.0Hz

[Favux]

OK, it's adding your two 1680 x 1050's into one 3360 x 1050 monitor on Screen 0. But it seems to be saying that one monitor, the minimum 1680 x 1050 is available. I'm thinking the other monitor would be 1681 x 1050.

What does your xorg.conf look like?

[dsavi]

There's some junk in there as I have been playing with Xinerama to see if that would solve my problem:

# nvidia-settings: X configuration file generated by nvidia-settings
# nvidia-settings:  version 260.19.06  (buildd@palmer)  Mon Oct  4 16:01:38 UTC 2010


Section "ServerLayout"

# Removed Option "Xinerama" "0"
# Removed Option "Xinerama" "1"
    Identifier     "Layout0"
    Screen      0  "Screen0" 0 0
    InputDevice    "Keyboard0" "CoreKeyboard"
    InputDevice    "Mouse0" "CorePointer"
    Option         "Xinerama" "0"
EndSection

Section "Files"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/psaux"
    Option         "Emulate3Buttons" "no"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"

    # generated from default
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "Monitor"

    # HorizSync source: edid, VertRefresh source: edid
    Identifier     "Monitor0"
    VendorName     "Unknown"
    ModelName      "LG Electronics W2042"
    HorizSync       30.0 - 83.0
    VertRefresh     56.0 - 75.0
    Option         "DPMS"
EndSection

Section "Monitor"
    Identifier     "Monitor1"
    VendorName     "Unknown"
    ModelName      "Samsung SyncMaster"
    HorizSync       30.0 - 81.0
    VertRefresh     56.0 - 75.0
EndSection

Section "Device"
    Identifier     "Device0"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 8600 GT"
EndSection

Section "Device"
    Identifier     "Device1"
    Driver         "nvidia"
    VendorName     "NVIDIA Corporation"
    BoardName      "GeForce 8600 GT"
    BusID          "PCI:2:0:0"
    Screen          1
EndSection

Section "Screen"

# Removed Option "TwinView" "1"
# Removed Option "metamodes" "DFP-0: nvidia-auto-select +1680+0, DFP-1: nvidia-auto-select +0+0"
# Removed Option "TwinView" "0"
# Removed Option "metamodes" "DFP-0: nvidia-auto-select +0+0"
    Identifier     "Screen0"
    Device         "Device0"
    Monitor        "Monitor0"
    DefaultDepth    24
    Option         "TwinView" "1"
    Option         "metamodes" "DFP-0: nvidia-auto-select +1680+0, DFP-1: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

Section "Screen"
    Identifier     "Screen1"
    Device         "Device1"
    Monitor        "Monitor1"
    DefaultDepth    24
    Option         "TwinView" "0"
    Option         "metamodes" "DFP-1: nvidia-auto-select +0+0"
    SubSection     "Display"
        Depth       24
    EndSubSection
EndSection

[Favux]

Do you remember what a fresh Nvidia xorg.conf looks like? A backup?

I'm wondering if Twinview has been deprecated (dropped) in Maverick.

There seem to be two devices configured.

What does your:

xinput --list

output look like?

Using the "Device name" for stylus (in quotes) let's look at the output of:

xsetwacom list params

You can skip the button output. Then:

xinput list-props "Device name"