Thread: [DIGImend-users] Aiptek Media Tablet 14000u worked instantly (and almost complete) in linux 3.3.2
Brought to you by:
spb_nick
Menu
▾
▴
digimend-users
|
From: Eduardo H. S. <hob...@gm...> - 2012-04-28 17:59:09
|
Hi, just wanted to report how my Aiptek Media Tablet 14000u worked
instantly (and almost complete) in a newly installed Fedora 17 (beta).
It worked just by plugin in. By default it uses the wacom driver,
which enables the stylus with pressure, but both stylus buttons are
configured to click (1) and the tablet scroll wheels are non
functioning. I couldn't configure the buttons for middle-click: it
painted instead when I held the button, and erased what had been
painted when released. Occasionally it would do a middle-click.
Following the evdev HOWTO instructions in the wiki, I created
/etc/X11/xorg.conf.d/52-tablet-on-evdev.conf and I now have buttons
configured and scroll wheels working.
I tried removing the wacom configuration, but then it didn't work in
Gimp (worked fine in inkscape though).
I do have a question, is there support for the Macros or function keys
of the tablet?
Here's some info in case it can be useful:
Linux 3.3.2
xinput list:
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ WALTOP International Corp. Media Tablet id=9 [slave pointer (2)]
⎜ ↳ WALTOP International Corp. Media Tablet id=10 [slave pointer (2)]
⎜ ↳ PS/2+USB Mouse id=13 [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)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ WALTOP International Corp. Media Tablet id=11 [slave keyboard (3)]
↳ WALTOP International Corp. Media Tablet id=12 [slave keyboard (3)]
↳ Asus Laptop extra buttons id=14 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)]
/usr/share/X11/xorg.conf.d/50-wacom.conf:
Section "InputClass"
Identifier "Wacom class"
MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection
Section "InputClass"
Identifier "Wacom serial class"
MatchProduct "Serial Wacom Tablet"
Driver "wacom"
EndSection
Section "InputClass"
Identifier "Wacom serial class identifiers"
MatchProduct "WACf|FUJ02e5|FUJ02e7|FUJ02e9"
Driver "wacom"
EndSection
# N-Trig Duosense Electromagnetic Digitizer
Section "InputClass"
Identifier "Wacom N-Trig class"
MatchProduct "HID 1b96:0001|N-Trig Pen"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
Option "Button2" "3"
EndSection
/etc/X11/xorg.conf.d/52-tablet-on-evdev.conf:
Section "InputClass"
Identifier "Aptik"
MatchProduct "WALTOP"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "ButtonMapping" "1 2 3"
EndSection
dmesg:
[50186.456040] usb 6-1: new full-speed USB device number 99 using uhci_hcd
[50186.618520] usb 6-1: New USB device found, idVendor=172f, idProduct=0500
[50186.618524] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[50186.618527] usb 6-1: Product: Media Tablet
[50186.618529] usb 6-1: Manufacturer: WALTOP International Corp.
[50186.632625] input: WALTOP International Corp. Media Tablet as
/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input383
[50186.633053] input: WALTOP International Corp. Media Tablet as
/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input384
[50186.633156] input: WALTOP International Corp. Media Tablet as
/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input385
[50186.633266] input: WALTOP International Corp. Media Tablet as
/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input386
[50186.633440] waltop 0003:172F:0500.0060: input,hidraw1: USB HID
v1.10 Mouse [WALTOP International Corp. Media Tablet] on
usb-0000:00:1d.1-1/input0
Xorg.0.log:
[ 50613.946] (II) config/udev: Adding input device WALTOP
International Corp. Media Tablet (/dev/input/event10)
[ 50613.946] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "evdev tablet catchall"
[ 50613.946] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "Wacom class"
[ 50613.946] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "Aptik"
[ 50613.946] (II) Using input driver 'evdev' for 'WALTOP International
Corp. Media Tablet'
[ 50613.946] (**) WALTOP International Corp. Media Tablet: always
reports core events
[ 50613.946] (**) evdev: WALTOP International Corp. Media Tablet:
Device: "/dev/input/event10"
[ 50613.946] (**) evdev: WALTOP International Corp. Media Tablet:
ButtonMapping '1 2 3'
[ 50613.946] (--) evdev: WALTOP International Corp. Media Tablet:
Vendor 0x172f Product 0x500
[ 50613.946] (--) evdev: WALTOP International Corp. Media Tablet:
Found absolute axes
[ 50613.946] (--) evdev: WALTOP International Corp. Media Tablet:
Found x and y absolute axes
[ 50613.946] (--) evdev: WALTOP International Corp. Media Tablet:
Found absolute tablet.
[ 50613.946] (II) evdev: WALTOP International Corp. Media Tablet:
Configuring as tablet
[ 50613.946] (**) evdev: WALTOP International Corp. Media Tablet:
YAxisMapping: buttons 4 and 5
[ 50613.946] (**) evdev: WALTOP International Corp. Media Tablet:
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout:
200
[ 50613.946] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input383/event10"
[ 50613.946] (II) XINPUT: Adding extended input device "WALTOP
International Corp. Media Tablet" (type: TABLET, id 9)
[ 50613.946] (II) evdev: WALTOP International Corp. Media Tablet:
initialized for absolute axes.
[ 50613.946] (**) WALTOP International Corp. Media Tablet: (accel)
keeping acceleration scheme 1
[ 50613.946] (**) WALTOP International Corp. Media Tablet: (accel)
acceleration profile 0
[ 50613.946] (**) WALTOP International Corp. Media Tablet: (accel)
acceleration factor: 2.000
[ 50613.946] (**) WALTOP International Corp. Media Tablet: (accel)
acceleration threshold: 4
[ 50613.947] (II) config/udev: Adding input device WALTOP
International Corp. Media Tablet (/dev/input/mouse2)
[ 50613.947] (II) No input driver specified, ignoring this device.
[ 50613.947] (II) This device may have been added with another device file.
[ 50613.947] (II) config/udev: Adding input device WALTOP
International Corp. Media Tablet (/dev/input/event11)
[ 50613.947] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "Wacom class"
[ 50613.947] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "Aptik"
[ 50613.947] (II) Using input driver 'evdev' for 'WALTOP International
Corp. Media Tablet'
[ 50613.947] (**) WALTOP International Corp. Media Tablet: always
reports core events
[ 50613.947] (**) evdev: WALTOP International Corp. Media Tablet:
Device: "/dev/input/event11"
[ 50613.947] (**) evdev: WALTOP International Corp. Media Tablet:
ButtonMapping '1 2 3'
[ 50613.947] (--) evdev: WALTOP International Corp. Media Tablet:
Vendor 0x172f Product 0x500
[ 50613.947] (--) evdev: WALTOP International Corp. Media Tablet:
Found scroll wheel(s)
[ 50613.947] (II) evdev: WALTOP International Corp. Media Tablet:
Forcing buttons for scroll wheel(s)
[ 50613.947] (--) evdev: WALTOP International Corp. Media Tablet:
Found relative axes
[ 50613.947] (II) evdev: WALTOP International Corp. Media Tablet:
Forcing relative x/y axes to exist.
[ 50613.948] (II) evdev: WALTOP International Corp. Media Tablet:
Configuring as mouse
[ 50613.948] (II) evdev: WALTOP International Corp. Media Tablet:
Adding scrollwheel support
[ 50613.948] (**) evdev: WALTOP International Corp. Media Tablet:
YAxisMapping: buttons 4 and 5
[ 50613.948] (**) evdev: WALTOP International Corp. Media Tablet:
EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout:
200
[ 50613.948] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input384/event11"
[ 50613.948] (II) XINPUT: Adding extended input device "WALTOP
International Corp. Media Tablet" (type: MOUSE, id 10)
[ 50613.948] (II) evdev: WALTOP International Corp. Media Tablet:
initialized for relative axes.
[ 50613.948] (**) WALTOP International Corp. Media Tablet: (accel)
keeping acceleration scheme 1
[ 50613.948] (**) WALTOP International Corp. Media Tablet: (accel)
acceleration profile 0
[ 50613.948] (**) WALTOP International Corp. Media Tablet: (accel)
acceleration factor: 2.000
[ 50613.948] (**) WALTOP International Corp. Media Tablet: (accel)
acceleration threshold: 4
[ 50613.948] (II) config/udev: Adding input device WALTOP
International Corp. Media Tablet (/dev/input/event12)
[ 50613.948] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "evdev keyboard catchall"
[ 50613.948] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "Wacom class"
[ 50613.948] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "system-setup-keyboard"
[ 50613.948] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "Aptik"
[ 50613.948] (II) Using input driver 'evdev' for 'WALTOP International
Corp. Media Tablet'
[ 50613.948] (**) WALTOP International Corp. Media Tablet: always
reports core events
[ 50613.948] (**) evdev: WALTOP International Corp. Media Tablet:
Device: "/dev/input/event12"
[ 50613.949] (**) evdev: WALTOP International Corp. Media Tablet:
ButtonMapping '1 2 3'
[ 50613.949] (--) evdev: WALTOP International Corp. Media Tablet:
Vendor 0x172f Product 0x500
[ 50613.949] (--) evdev: WALTOP International Corp. Media Tablet: Found keys
[ 50613.949] (II) evdev: WALTOP International Corp. Media Tablet:
Configuring as keyboard
[ 50613.949] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input385/event12"
[ 50613.949] (II) XINPUT: Adding extended input device "WALTOP
International Corp. Media Tablet" (type: KEYBOARD, id 11)
[ 50613.949] (**) Option "xkb_rules" "evdev"
[ 50613.949] (**) Option "xkb_model" "pc105"
[ 50613.949] (**) Option "xkb_layout" "pt"
[ 50613.949] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[ 50613.949] (II) config/udev: Adding input device WALTOP
International Corp. Media Tablet (/dev/input/event13)
[ 50613.949] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "evdev keyboard catchall"
[ 50613.949] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "Wacom class"
[ 50613.949] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "system-setup-keyboard"
[ 50613.949] (**) WALTOP International Corp. Media Tablet: Applying
InputClass "Aptik"
[ 50613.949] (II) Using input driver 'evdev' for 'WALTOP International
Corp. Media Tablet'
[ 50613.950] (**) WALTOP International Corp. Media Tablet: always
reports core events
[ 50613.950] (**) evdev: WALTOP International Corp. Media Tablet:
Device: "/dev/input/event13"
[ 50613.950] (**) evdev: WALTOP International Corp. Media Tablet:
ButtonMapping '1 2 3'
[ 50613.950] (--) evdev: WALTOP International Corp. Media Tablet:
Vendor 0x172f Product 0x500
[ 50613.950] (--) evdev: WALTOP International Corp. Media Tablet: Found keys
[ 50613.950] (II) evdev: WALTOP International Corp. Media Tablet:
Configuring as keyboard
Eduardo
|
|
From: Favux ... <fav...@gm...> - 2012-04-29 03:19:56
|
Hi Eduardo,
Recently Nick submitted a snippet to the Linux Wacom Project to keep
the Waltop stylus on the Wacom X driver but have the evdev X driver
control the tablet frame/bezel stuff. Maybe we should try that. I
would very much like to find out if there is something wrong in the
Waltop Media Tablet 14.1" HID kernel driver making the stylus buttons
incompatible with the Wacom X driver (xf86-input-wacom) or not. The
new snippet looks like:
# Waltop tablets
Section "InputClass"
Identifier "Waltop class"
MatchProduct "WALTOP"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
EndSection
It's the MatchIsTablet that picks up the stylus from evdev for the
Wacom X driver in 50-wacom.conf.
In /usr/share/X11/xorg.conf.d the 10-evdev.conf matches first. From
your Xorg.0.log the two evdev snippets that are matching are:
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev tablet catchall"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
With your current setup evdev claims the tablet, then wacom, then your
custom rule puts it back on evdev.
Let's try to replicate the new /usr/share/X11/xorg.conf.d matches in
/etc/X11/xorg.conf.d without putting it entirely back on the evdev
driver. First remove or comment out your 52-tablet-on-evdev.conf. We
should change the suggested name from 52-waltop-on-wacom.conf to say
52-waltop-custom.conf because we're now using both the evdev and Wacom
drivers.
/etc/X11/xorg.conf.d/52-waltop-custom.conf:
Section "InputClass"
Identifier "Waltop evdev custom"
MatchProduct "WALTOP"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "Waltop wacom custom"
MatchProduct "WALTOP"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
# Option "Button2" "2"
# Option "Button3" "3"
EndSection
Yes very redundant. :) But hopefully it will work.
With the stylus back on Wacom there is something you want to check
before removing the comments from the button options in the Wacom
snippet.
The GNOME Wacom Graphics Tablet applet in System Settings will
override these options anyway. Check its settings and change them to
what you want. I'm wondering if that was what was causing the problem
in the first place. Because I don't recall anyone reporting all
stylus buttons set to Button1 1 before, so something funky is going
on. Maybe Fedora has introduced a bug by inadvertently setting the
gnome-settings-daemon key values wrong for the two stylus side
buttons. And the scroll wheels should work with this setup, i.e.
being on evdev.
Favux
|
|
From: Eduardo H. S. <hob...@gm...> - 2012-04-29 12:28:35
|
2012/4/29 Favux ... <fav...@gm...>: > Hi Eduardo, > > Recently Nick submitted a snippet to the Linux Wacom Project to keep > the Waltop stylus on the Wacom X driver but have the evdev X driver > control the tablet frame/bezel stuff. Maybe we should try that. I > would very much like to find out if there is something wrong in the > Waltop Media Tablet 14.1" HID kernel driver making the stylus buttons > incompatible with the Wacom X driver (xf86-input-wacom) or not. The > new snippet looks like: > > # Waltop tablets > Section "InputClass" > Identifier "Waltop class" > MatchProduct "WALTOP" > MatchIsTablet "on" > MatchDevicePath "/dev/input/event*" > Driver "wacom" > EndSection > > It's the MatchIsTablet that picks up the stylus from evdev for the > Wacom X driver in 50-wacom.conf. > > In /usr/share/X11/xorg.conf.d the 10-evdev.conf matches first. From > your Xorg.0.log the two evdev snippets that are matching are: > > Section "InputClass" > Identifier "evdev keyboard catchall" > MatchIsKeyboard "on" > MatchDevicePath "/dev/input/event*" > Driver "evdev" > EndSection > > Section "InputClass" > Identifier "evdev tablet catchall" > MatchIsTablet "on" > MatchDevicePath "/dev/input/event*" > Driver "evdev" > EndSection > > With your current setup evdev claims the tablet, then wacom, then your > custom rule puts it back on evdev. > > Let's try to replicate the new /usr/share/X11/xorg.conf.d matches in > /etc/X11/xorg.conf.d without putting it entirely back on the evdev > driver. First remove or comment out your 52-tablet-on-evdev.conf. We > should change the suggested name from 52-waltop-on-wacom.conf to say > 52-waltop-custom.conf because we're now using both the evdev and Wacom > drivers. > > /etc/X11/xorg.conf.d/52-waltop-custom.conf: > > Section "InputClass" > Identifier "Waltop evdev custom" > MatchProduct "WALTOP" > MatchIsKeyboard "on" > MatchDevicePath "/dev/input/event*" > Driver "evdev" > EndSection > > Section "InputClass" > Identifier "Waltop wacom custom" > MatchProduct "WALTOP" > MatchIsTablet "on" > MatchDevicePath "/dev/input/event*" > Driver "wacom" > # Option "Button2" "2" > # Option "Button3" "3" > EndSection > > Yes very redundant. :) But hopefully it will work. > > With the stylus back on Wacom there is something you want to check > before removing the comments from the button options in the Wacom > snippet. > > The GNOME Wacom Graphics Tablet applet in System Settings will > override these options anyway. Check its settings and change them to > what you want. The Gnome Wacom applet doesn't shown me options, saying that no tablet was detected. This with all my previous configurations, and with your new suggestion. Btw, I just need to restart X to have the configuration re-read right? > I'm wondering if that was what was causing the problem > in the first place. Because I don't recall anyone reporting all > stylus buttons set to Button1 1 before, so something funky is going > on. Maybe Fedora has introduced a bug by inadvertently setting the > gnome-settings-daemon key values wrong for the two stylus side > buttons. And the scroll wheels should work with this setup, i.e. > being on evdev. Yep, with your new config file, the scroll wheels work, and the stylus has pressure. But the first button paints, and the second button paints while held and undos it when released. In inkscape, this 2nd button sometimes does a zoom in. Eduardo |
|
From: Nikolai K. <sp...@gm...> - 2012-04-29 10:22:26
|
Hi Eduardo, Dave, On 04/29/2012 06:19 AM, Favux ... wrote: > The GNOME Wacom Graphics Tablet applet in System Settings will > override these options anyway. Check its settings and change them to > what you want. I'm wondering if that was what was causing the problem > in the first place. Because I don't recall anyone reporting all > stylus buttons set to Button1 1 before, so something funky is going > on. Maybe Fedora has introduced a bug by inadvertently setting the > gnome-settings-daemon key values wrong for the two stylus side > buttons. And the scroll wheels should work with this setup, i.e. > being on evdev. To me this side button behavior looks as though, for some reason, the kernel didn't use the Waltop-specific driver, but used the generic HID driver instead. However, the presence of four event devices shows that the correct kernel driver is used. Were they seen at the time the buttons didn't work? The wheels and mode buttons should work, but may need some configuration. The scroll mode may require the following snippet to be placed into the X.org configuration: Section "InputClass" Identifier "evdev waltop scroll" MatchIsPointer "off" MatchIsKeyboard "off" MatchIsTablet "off" MatchIsTouchpad "off" MatchIsTouchscreen "off" MatchProduct "WALTOP" MatchDevicePath "/dev/input/event*" Driver "evdev" EndSection This forces the corresponding event device, which has scrolling only and isn't qualified by X.org as any specific device type, to be handled by evdev. The zoom mode may require configuring key bindings in applications as most of them don't recognize zooming key codes. The volume mode, OTOH, should just work. Regarding the "virtual" buttons located on the tablet surface, we are not intending to support them, because their usefulness is limited. When using the tablet you need to look at the screen, but to hit these buttons you need to look at the tablet, because it's hard to locate them otherwise. This makes you loose concentration. Sincerely, Nick |
|
From: Eduardo H. S. <hob...@gm...> - 2012-04-29 12:35:56
|
2012/4/29 Nikolai Kondrashov <sp...@gm...>: > Hi Eduardo, Dave, > > > On 04/29/2012 06:19 AM, Favux ... wrote: >> >> The GNOME Wacom Graphics Tablet applet in System Settings will >> override these options anyway. Check its settings and change them to >> what you want. I'm wondering if that was what was causing the problem >> in the first place. Because I don't recall anyone reporting all >> stylus buttons set to Button1 1 before, so something funky is going >> on. Maybe Fedora has introduced a bug by inadvertently setting the >> gnome-settings-daemon key values wrong for the two stylus side >> buttons. And the scroll wheels should work with this setup, i.e. >> being on evdev. > > > To me this side button behavior looks as though, for some reason, the kernel > didn't use the Waltop-specific driver, but used the generic HID driver > instead. However, the presence of four event devices shows that the correct > kernel driver is used. Were they seen at the time the buttons didn't work? I'll paste here my Xorg.0.log with the configuration that Dave gave me which make the side buttons react oddly like I said above: [ 95933.688] (II) config/udev: Adding input device WALTOP International Corp. Media Tablet (/dev/input/event13) [ 95933.695] (**) WALTOP International Corp. Media Tablet: Applying InputClass "evdev keyboard catchall" [ 95933.695] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Wacom class" [ 95933.695] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Aptik" [ 95933.695] (**) WALTOP International Corp. Media Tablet: Applying InputClass "system-setup-keyboard" [ 95933.695] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Waltop evdev custom" [ 95933.695] (II) Using input driver 'evdev' for 'WALTOP International Corp. Media Tablet' [ 95933.695] (**) WALTOP International Corp. Media Tablet: always reports core events [ 95933.695] (**) evdev: WALTOP International Corp. Media Tablet: Device: "/dev/input/event13" [ 95933.695] (**) evdev: WALTOP International Corp. Media Tablet: ButtonMapping '1 2 3' [ 95933.695] (--) evdev: WALTOP International Corp. Media Tablet: Vendor 0x172f Product 0x500 [ 95933.695] (--) evdev: WALTOP International Corp. Media Tablet: Found keys [ 95933.695] (II) evdev: WALTOP International Corp. Media Tablet: Configuring as keyboard [ 95933.695] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input403/event13" [ 95933.695] (II) XINPUT: Adding extended input device "WALTOP International Corp. Media Tablet" (type: KEYBOARD, id 13) [ 95933.695] (**) Option "xkb_rules" "evdev" [ 95933.695] (**) Option "xkb_model" "pc105" [ 95933.695] (**) Option "xkb_layout" "pt" [ 95933.695] (**) Option "xkb_options" "terminate:ctrl_alt_bksp," [ 95933.719] (II) config/udev: Adding input device WALTOP International Corp. Media Tablet (/dev/input/event11) [ 95933.719] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Wacom class" [ 95933.719] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Aptik" [ 95933.719] (II) Using input driver 'evdev' for 'WALTOP International Corp. Media Tablet' [ 95933.719] (**) WALTOP International Corp. Media Tablet: always reports core events [ 95933.719] (**) evdev: WALTOP International Corp. Media Tablet: Device: "/dev/input/event11" [ 95933.719] (**) evdev: WALTOP International Corp. Media Tablet: ButtonMapping '1 2 3' [ 95933.719] (--) evdev: WALTOP International Corp. Media Tablet: Vendor 0x172f Product 0x500 [ 95933.719] (--) evdev: WALTOP International Corp. Media Tablet: Found scroll wheel(s) [ 95933.719] (II) evdev: WALTOP International Corp. Media Tablet: Forcing buttons for scroll wheel(s) [ 95933.719] (--) evdev: WALTOP International Corp. Media Tablet: Found relative axes [ 95933.719] (II) evdev: WALTOP International Corp. Media Tablet: Forcing relative x/y axes to exist. [ 95933.719] (II) evdev: WALTOP International Corp. Media Tablet: Configuring as mouse [ 95933.719] (II) evdev: WALTOP International Corp. Media Tablet: Adding scrollwheel support [ 95933.719] (**) evdev: WALTOP International Corp. Media Tablet: YAxisMapping: buttons 4 and 5 [ 95933.719] (**) evdev: WALTOP International Corp. Media Tablet: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [ 95933.719] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input401/event11" [ 95933.719] (II) XINPUT: Adding extended input device "WALTOP International Corp. Media Tablet" (type: MOUSE, id 14) [ 95933.719] (II) evdev: WALTOP International Corp. Media Tablet: initialized for relative axes. [ 95933.719] (**) WALTOP International Corp. Media Tablet: (accel) keeping acceleration scheme 1 [ 95933.719] (**) WALTOP International Corp. Media Tablet: (accel) acceleration profile 0 [ 95933.719] (**) WALTOP International Corp. Media Tablet: (accel) acceleration factor: 2.000 [ 95933.719] (**) WALTOP International Corp. Media Tablet: (accel) acceleration threshold: 4 [ 95933.724] (II) config/udev: Adding input device WALTOP International Corp. Media Tablet (/dev/input/event10) [ 95933.724] (**) WALTOP International Corp. Media Tablet: Applying InputClass "evdev tablet catchall" [ 95933.724] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Wacom class" [ 95933.724] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Aptik" [ 95933.724] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Waltop wacom custom" [ 95933.724] (II) LoadModule: "wacom" [ 95933.724] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so [ 95933.774] (II) Module wacom: vendor="X.Org Foundation" [ 95933.774] compiled for 1.11.99.901, module version = 0.14.0 [ 95933.774] Module class: X.Org XInput Driver [ 95933.774] ABI class: X.Org XInput driver, version 16.0 [ 95933.774] (II) Using input driver 'wacom' for 'WALTOP International Corp. Media Tablet' [ 95933.774] (**) WALTOP International Corp. Media Tablet: always reports core events [ 95933.774] (**) Option "Device" "/dev/input/event10" [ 95933.775] (II) WALTOP International Corp. Media Tablet: type not specified, assuming 'stylus'. [ 95933.775] (II) WALTOP International Corp. Media Tablet: other types will be automatically added. [ 95933.775] (--) WALTOP International Corp. Media Tablet stylus: using pressure threshold of 27 for button 1 [ 95933.775] (--) WALTOP International Corp. Media Tablet stylus: Wacom USB Bamboo tablet maxX=16383 maxY=16383 maxZ=1023 resX=53000 resY=88000 tilt=disabled [ 95933.775] (II) WALTOP International Corp. Media Tablet stylus: hotplugging dependent devices. [ 95933.775] (EE) WALTOP International Corp. Media Tablet stylus: Invalid type 'eraser' for this device. [ 95933.775] (EE) WALTOP International Corp. Media Tablet stylus: Invalid type 'cursor' for this device. [ 95933.775] (EE) WALTOP International Corp. Media Tablet stylus: Invalid type 'touch' for this device. [ 95933.775] (EE) WALTOP International Corp. Media Tablet stylus: Invalid type 'pad' for this device. [ 95933.775] (II) WALTOP International Corp. Media Tablet stylus: hotplugging completed. [ 95933.775] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input400/event10" [ 95933.775] (II) XINPUT: Adding extended input device "WALTOP International Corp. Media Tablet stylus" (type: STYLUS, id 15) [ 95933.775] (**) WALTOP International Corp. Media Tablet stylus: (accel) keeping acceleration scheme 1 [ 95933.775] (**) WALTOP International Corp. Media Tablet stylus: (accel) acceleration profile 0 [ 95933.775] (**) WALTOP International Corp. Media Tablet stylus: (accel) acceleration factor: 2.000 [ 95933.775] (**) WALTOP International Corp. Media Tablet stylus: (accel) acceleration threshold: 4 [ 95933.776] (II) config/udev: Adding input device WALTOP International Corp. Media Tablet (/dev/input/mouse2) [ 95933.776] (II) No input driver specified, ignoring this device. [ 95933.776] (II) This device may have been added with another device file. [ 95933.776] (II) config/udev: Adding input device WALTOP International Corp. Media Tablet (/dev/input/event12) [ 95933.776] (**) WALTOP International Corp. Media Tablet: Applying InputClass "evdev keyboard catchall" [ 95933.776] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Wacom class" [ 95933.776] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Aptik" [ 95933.776] (**) WALTOP International Corp. Media Tablet: Applying InputClass "system-setup-keyboard" [ 95933.776] (**) WALTOP International Corp. Media Tablet: Applying InputClass "Waltop evdev custom" [ 95933.776] (II) Using input driver 'evdev' for 'WALTOP International Corp. Media Tablet' [ 95933.776] (**) WALTOP International Corp. Media Tablet: always reports core events [ 95933.776] (**) evdev: WALTOP International Corp. Media Tablet: Device: "/dev/input/event12" [ 95933.776] (**) evdev: WALTOP International Corp. Media Tablet: ButtonMapping '1 2 3' [ 95933.776] (--) evdev: WALTOP International Corp. Media Tablet: Vendor 0x172f Product 0x500 [ 95933.776] (--) evdev: WALTOP International Corp. Media Tablet: Found keys [ 95933.776] (II) evdev: WALTOP International Corp. Media Tablet: Configuring as keyboard [ 95933.776] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input402/event12" [ 95933.777] (II) XINPUT: Adding extended input device "WALTOP International Corp. Media Tablet" (type: KEYBOARD, id 16) > The wheels and mode buttons should work, but may need some configuration. After using Dave's configuration, the wheel and mode buttons work immediately. > The scroll mode may require the following snippet to be placed into the > X.org configuration: > > Section "InputClass" > Identifier "evdev waltop scroll" > MatchIsPointer "off" > MatchIsKeyboard "off" > MatchIsTablet "off" > MatchIsTouchpad "off" > MatchIsTouchscreen "off" > MatchProduct "WALTOP" > > MatchDevicePath "/dev/input/event*" > Driver "evdev" > EndSection > > This forces the corresponding event device, which has scrolling only and > isn't qualified by X.org as any specific device type, to be handled by > evdev. > > The zoom mode may require configuring key bindings in applications as most > of them don't recognize zooming key codes. > > The volume mode, OTOH, should just work. > > Regarding the "virtual" buttons located on the tablet surface, we are not > intending to support them, because their usefulness is limited. When using > the tablet you need to look at the screen, but to hit these buttons you need > to look at the tablet, because it's hard to locate them otherwise. This > makes you loose concentration. Ah, I see, I hadn't thought of that. Eduardo > > Sincerely, > Nick |
|
From: Favux ... <fav...@gm...> - 2012-04-29 18:22:20
|
On Sun, Apr 29, 2012 at 7:35 AM, Eduardo H. Silva <hob...@gm...> wrote:
>
> Yep, with your new config file, the scroll wheels work, and the stylus
> has pressure. But the first button paints, and the second button
> paints while held and undos it when released. In inkscape, this 2nd
> button sometimes does a zoom in.
>
>> The wheels and mode buttons should work, but may need some configuration.
>
> After using Dave's configuration, the wheel and mode buttons work immediately.
Good. So we have everything working with 52-waltop-custom.conf except
the two stylus side buttons. We need to find out why. Your new
Xorg.0.log shows that event10 is the stylus and is being set up by
Wacom while events 11, 12, and 13 are being claimed by evdev. I think
that is correct, Nick can tell us. On those 3 events evdev is
reporting:
ButtonMapping '1 2 3'
Event 10 on Wacom is reporting:
using pressure threshold of 27 for button 1
which is correct.
Still see Aiptek, so you commented out the evdev driver line but left
the matching in?
With the 52-waltop-custom.conf let's try to find out what we have.
What is the output of?
xsetwacom list
I'll guess that event10 was the ID # 9 on your 'xinput list' and that
hasn't changed. Let's see if we can get a button map reported in the
output of:
xinput list-props 9
If rerunning 'xinput list' shows different ID numbers you'll have to
guess until you hit the stylus. You'll know you have the right one
when the driver in the output is wacom not evdev.
We can also get the assigned button values reported separately using
the xsetwacom get command. So using the stylus ID # from above:
xsetwacom get 9 Button 1
xsetwacom get 9 Button 2
xsetwacom get 9 Button 3
The other thing is to look at the gnome-settings-daemon's key values.
Since the applet isn't allowing access install dconf-editor and run
it. Then navigate to org.gnome.settings-daemon.peripherals.wacom. If
your tablet was listed there, under the tablet name would be one or
more styli. They should report a pressurecurve and the active one a
buttonmapping. Anything regarding a stylus or tablet in there?
Buttonmapping?
> The Gnome Wacom applet doesn't shown me options, saying that no tablet
> was detected. This with all my previous configurations, and with your
> new suggestion. Btw, I just need to restart X to have the
> configuration re-read right?
I don't think so. As far as I know it should be run-time, changing
the gnome-settings-daemon's key values with the Wacom Tablet applet
should change behavior instantly just like a xsetwacom command.
If it is on the Wacom driver why isn't it showing up on the tablet
applet? We know the xf86-input-wacom driver is handling the stylus
according to the Xorg.0.log and it is working because you have
pressure. Libwacom does have a stylus file with a generic stylus
section. Libwacom is a Wacom tablet metadata library that was added
shortly after the initial Wacom Graphics Tablet applet came out. And
the applet was then changed to work with it. The idea was to simplify
the applet and make the library available to other applications that
might want to use the tablet metadata. So my guess is that it is
libwacom blocking recognition of the Waltop stylus, which is why you
don't see it in the applet. If so that may be also true for the
N-Trig and Hanwang tablets. Not good. I think I need to ask the LWP
about this.
Favux
|
|
From: Nikolai K. <sp...@gm...> - 2012-05-01 12:19:38
|
Hi Dave, On 04/29/2012 09:22 PM, Favux ... wrote: > Your new Xorg.0.log shows that event10 is the stylus and is being set up > by Wacom while events 11, 12, and 13 are being claimed by evdev. I think > that is correct, Nick can tell us. Yes, I think this is the best way to set it up. Sincerely, Nick |
|
From: Favux ... <fav...@gm...> - 2012-04-29 21:45:59
|
On Sun, Apr 29, 2012 at 4:08 PM, Eduardo H. Silva <hob...@gm...> wrote:
>>
>> Still see Aiptek, so you commented out the evdev driver line but left
>> the matching in?
>
> Oops, I forgot I had a waltop-on-evdev.conf file which looked for
> identifier in /usr/share/X11/xorg.conf.d/ . I've removed it.
>
>>
>> With the 52-waltop-custom.conf let's try to find out what we have.
>> What is the output of?
>> xsetwacom list
>
> WALTOP International Corp. Media Tablet stylus id: 10 type: STYLUS
Clearly on the Wacom X driver and identified correctly.
>> I'll guess that event10 was the ID # 9 on your 'xinput list' and that
>> hasn't changed. Let's see if we can get a button map reported in the
>> output of:
>> xinput list-props 9
>> If rerunning 'xinput list' shows different ID numbers you'll have to
>> guess until you hit the stylus. You'll know you have the right one
>> when the driver in the output is wacom not evdev.
>
> xinput list-props 10:
> Device 'WALTOP International Corp. Media Tablet stylus':
> Device Enabled (134): 1
> Coordinate Transformation Matrix (136): 1.000000, 0.000000, 0.000000,
> 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
> Device Accel Profile (260): 0
> Device Accel Constant Deceleration (261): 1.000000
> Device Accel Adaptive Deceleration (262): 1.000000
> Device Accel Velocity Scaling (263): 10.000000
> Device Node (254): "/dev/input/event10"
> Wacom Tablet Area (288): 0, 0, 16383, 16383
> Wacom Rotation (289): 0
> Wacom Pressurecurve (290): 0, 0, 100, 100
> Wacom Serial IDs (291): 1280, 1, 0, 0, 0
> Wacom Serial ID binding (292): 0
> Wacom Pressure Threshold (293): 27
> Wacom Sample and Suppress (294): 2, 4
> Wacom Enable Touch (295): 1
> Wacom Hover Click (296): 1
> Wacom Enable Touch Gesture (297): 0
> Wacom Touch Gesture Parameters (298): 0, 0, 250
> Wacom Tool Type (299): "STYLUS" (281)
> Wacom Button Actions (300): "None" (0), "None" (0), "None" (0),
> "None" (0), "None" (0), "None" (0), "None" (0)
> Device Product ID (253): 5935, 1280
> Wacom Debug Levels (301): 0, 0
>
> Hm, "Button Actions: "None"...
That all looks good. Shoot, I couldn't remember if it gave us a
stylus button map or not. Guess not. Maybe only cursor? Don't worry
about "Button Actions", it doesn't mean what you think.
>> We can also get the assigned button values reported separately using
>> the xsetwacom get command. So using the stylus ID # from above:
>> xsetwacom get 9 Button 1
>> xsetwacom get 9 Button 2
>> xsetwacom get 9 Button 3
>
> Yep, shows them as 1, 2, 3.
So there is our stylus button map and as far as xf86-input-wacom is
concerned it is correct.
>> The other thing is to look at the gnome-settings-daemon's key values.
>> Since the applet isn't allowing access install dconf-editor and run
>> it. Then navigate to org.gnome.settings-daemon.peripherals.wacom. If
>> your tablet was listed there, under the tablet name would be one or
>> more styli. They should report a pressurecurve and the active one a
>> buttonmapping. Anything regarding a stylus or tablet in there?
>> Buttonmapping?
>
> Hmm, I don't have a wacom sections under peripherals...
Alright so your Waltop tablet isn't being detected. I wish I could be
sure that meant none of the configuration gui stuff was messing with
the stylus, but I'm not. Although the correct button map from the
xsetwacom get commands sure seems to suggest that.
>>> The Gnome Wacom applet doesn't shown me options, saying that no tablet
>>> was detected. This with all my previous configurations, and with your
>>> new suggestion. Btw, I just need to restart X to have the
>>> configuration re-read right?
>>
>> I don't think so. As far as I know it should be run-time, changing
>> the gnome-settings-daemon's key values with the Wacom Tablet applet
>> should change behavior instantly just like a xsetwacom command.
>
> Ah, but what about adding rules in /etc/X11/xorg.conf.d/?
The gnome-settings-daemon runs after the xorg.conf.d conf files so
what it says goes. And you can over ride it with an xsetwacom
command. So what happens if you run these commands:
xsetwacom set 10 Button 2 2
xsetwacom set 10 Button 3 3
Any change on the stylus buttons behavior? If the tablet isn't being
recognized maybe no gnome-settings-daemon key values are being
applied. So if this works try uncommenting those button options from
earlier in the Wacom snippet and see what happens. Actually try that
either way I suppose.
>> If it is on the Wacom driver why isn't it showing up on the tablet
>> applet? We know the xf86-input-wacom driver is handling the stylus
>> according to the Xorg.0.log and it is working because you have
>> pressure.
> But what about the last message about wacom in Xorg.0.log:
> UnloadModule: "wacom"
What, where is that in the last Xorg.0.log snippet you gave? We know
the stylus is on the Wacom X driver (module) from the diagnostics you
ran above.
Favux
|
|
From: Eduardo H. S. <hob...@gm...> - 2012-04-29 23:05:19
|
2012/4/29 Favux ... <fav...@gm...>:
> On Sun, Apr 29, 2012 at 4:08 PM, Eduardo H. Silva <hob...@gm...> wrote:
>>>
>>> Still see Aiptek, so you commented out the evdev driver line but left
>>> the matching in?
>>
>> Oops, I forgot I had a waltop-on-evdev.conf file which looked for
>> identifier in /usr/share/X11/xorg.conf.d/ . I've removed it.
>>
>>>
>>> With the 52-waltop-custom.conf let's try to find out what we have.
>>> What is the output of?
>>> xsetwacom list
>>
>> WALTOP International Corp. Media Tablet stylus id: 10 type: STYLUS
>
> Clearly on the Wacom X driver and identified correctly.
>
>>> I'll guess that event10 was the ID # 9 on your 'xinput list' and that
>>> hasn't changed. Let's see if we can get a button map reported in the
>>> output of:
>>> xinput list-props 9
>>> If rerunning 'xinput list' shows different ID numbers you'll have to
>>> guess until you hit the stylus. You'll know you have the right one
>>> when the driver in the output is wacom not evdev.
>>
>> xinput list-props 10:
>> Device 'WALTOP International Corp. Media Tablet stylus':
>> Device Enabled (134): 1
>> Coordinate Transformation Matrix (136): 1.000000, 0.000000, 0.000000,
>> 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
>> Device Accel Profile (260): 0
>> Device Accel Constant Deceleration (261): 1.000000
>> Device Accel Adaptive Deceleration (262): 1.000000
>> Device Accel Velocity Scaling (263): 10.000000
>> Device Node (254): "/dev/input/event10"
>> Wacom Tablet Area (288): 0, 0, 16383, 16383
>> Wacom Rotation (289): 0
>> Wacom Pressurecurve (290): 0, 0, 100, 100
>> Wacom Serial IDs (291): 1280, 1, 0, 0, 0
>> Wacom Serial ID binding (292): 0
>> Wacom Pressure Threshold (293): 27
>> Wacom Sample and Suppress (294): 2, 4
>> Wacom Enable Touch (295): 1
>> Wacom Hover Click (296): 1
>> Wacom Enable Touch Gesture (297): 0
>> Wacom Touch Gesture Parameters (298): 0, 0, 250
>> Wacom Tool Type (299): "STYLUS" (281)
>> Wacom Button Actions (300): "None" (0), "None" (0), "None" (0),
>> "None" (0), "None" (0), "None" (0), "None" (0)
>> Device Product ID (253): 5935, 1280
>> Wacom Debug Levels (301): 0, 0
>>
>> Hm, "Button Actions: "None"...
>
> That all looks good. Shoot, I couldn't remember if it gave us a
> stylus button map or not. Guess not. Maybe only cursor? Don't worry
> about "Button Actions", it doesn't mean what you think.
>
>>> We can also get the assigned button values reported separately using
>>> the xsetwacom get command. So using the stylus ID # from above:
>>> xsetwacom get 9 Button 1
>>> xsetwacom get 9 Button 2
>>> xsetwacom get 9 Button 3
>>
>> Yep, shows them as 1, 2, 3.
>
> So there is our stylus button map and as far as xf86-input-wacom is
> concerned it is correct.
>
>>> The other thing is to look at the gnome-settings-daemon's key values.
>>> Since the applet isn't allowing access install dconf-editor and run
>>> it. Then navigate to org.gnome.settings-daemon.peripherals.wacom. If
>>> your tablet was listed there, under the tablet name would be one or
>>> more styli. They should report a pressurecurve and the active one a
>>> buttonmapping. Anything regarding a stylus or tablet in there?
>>> Buttonmapping?
>>
>> Hmm, I don't have a wacom sections under peripherals...
>
> Alright so your Waltop tablet isn't being detected. I wish I could be
> sure that meant none of the configuration gui stuff was messing with
> the stylus, but I'm not. Although the correct button map from the
> xsetwacom get commands sure seems to suggest that.
>
>>>> The Gnome Wacom applet doesn't shown me options, saying that no tablet
>>>> was detected. This with all my previous configurations, and with your
>>>> new suggestion. Btw, I just need to restart X to have the
>>>> configuration re-read right?
>>>
>>> I don't think so. As far as I know it should be run-time, changing
>>> the gnome-settings-daemon's key values with the Wacom Tablet applet
>>> should change behavior instantly just like a xsetwacom command.
>>
>> Ah, but what about adding rules in /etc/X11/xorg.conf.d/?
>
> The gnome-settings-daemon runs after the xorg.conf.d conf files so
> what it says goes. And you can over ride it with an xsetwacom
> command. So what happens if you run these commands:
> xsetwacom set 10 Button 2 2
> xsetwacom set 10 Button 3 3
> Any change on the stylus buttons behavior? If the tablet isn't being
> recognized maybe no gnome-settings-daemon key values are being
> applied.
It remains the same, and I've figured that:
1 - xsetwacom is working. If I assign:
Button 1 1
Button 2 3
Button 3 2
, the button's behaviors switch.
2 - if I assign:
Button 1 0
Button 2 2
Button 3 3
, the buttons are working as expected in Gimp and elsewhere, but
pressing with the stylus doesn't work.
Also, the broken behavior in Inkscape and throughout Gnome's interface
is different than Gimp's. If the assignment is:
Button 1 1
Button 2 2
Button 3 3
, button 2 does action 1 and 2 (left and middle-click) and button 3
does action 3 (right-click).
> So if this works try uncommenting those button options from
> earlier in the Wacom snippet and see what happens. Actually try that
> either way I suppose.
Uncommented the options and restarted X, but
>
>>> If it is on the Wacom driver why isn't it showing up on the tablet
>>> applet? We know the xf86-input-wacom driver is handling the stylus
>>> according to the Xorg.0.log and it is working because you have
>>> pressure.
>> But what about the last message about wacom in Xorg.0.log:
>> UnloadModule: "wacom"
>
> What, where is that in the last Xorg.0.log snippet you gave? We know
> the stylus is on the Wacom X driver (module) from the diagnostics you
> ran above.
Ah, at the time of that diagnostic, I was only copying what seemed to
have to do with the tablets, and may have missed the unload message.
Also, only now I noticed that once I removed waltop-on-evdev.conf from
/usr/share/X11/xorg.conf.d/ , makes the wheels not work.
Sorry about this confusion.
Ok, so my configuration is exactly like the one you told in your first
reply. To make sure, it is:
/usr/share/X11/xorg.conf.d/:
Section "InputClass"
Identifier "Wacom class"
MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
# Option "Button1" "3"
# Option "Button2" "1"
# Option "Button3" "2"
EndSection
Section "InputClass"
Identifier "Wacom serial class"
MatchProduct "Serial Wacom Tablet"
Driver "wacom"
EndSection
Section "InputClass"
Identifier "Wacom serial class identifiers"
MatchProduct "WACf|FUJ02e5|FUJ02e7|FUJ02e9"
Driver "wacom"
EndSection
# N-Trig Duosense Electromagnetic Digitizer
Section "InputClass"
Identifier "Wacom N-Trig class"
MatchProduct "HID 1b96:0001|N-Trig Pen"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
Option "Button2" "3"
EndSection
/etc/X11/xorg.conf.d/52-waltop-custom.conf
Section "InputClass"
Identifier "Waltop evdev custom"
MatchProduct "WALTOP"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "Waltop wacom custom"
MatchProduct "WALTOP"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "wacom"
Option "Button2" "2"
Option "Button3" "3"
EndSection
The complete Xorg.0.log after restarting X with the tablet plugged in:
[128945.619]
X.Org X Server 1.12.0
Release Date: 2012-03-04
[128945.619] X Protocol Version 11, Revision 0
[128945.619] Build Operating System: x86-09 2.6.32-220.4.1.el6.x86_64
[128945.619] Current Operating System: Linux portatil-edu
3.3.2-8.fc17.i686.PAE #1 SMP Sat Apr 21 12:34:01 UTC 2012 i686
[128945.619] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-3.3.2-8.fc17.i686.PAE
root=/dev/mapper/FedoraOS-FedoraOS ro rd.md=0 rd.dm=0 SYSFONT=True
rd.lvm.lv=FedoraOS/swapFedoraOS rd.lvm.lv=FedoraOS/FedoraOS rd.luks=0
KEYTABLE=pt-latin1 LANG=pt_PT.UTF-8 rhgb quiet
[128945.620] Build Date: 14 March 2012 03:01:49PM
[128945.620] Build ID: xorg-x11-server 1.12.0-2.fc17
[128945.620] Current version of pixman: 0.24.4
[128945.620] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[128945.620] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[128945.620] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Apr 29
23:49:16 2012
[128945.620] (==) Using config directory: "/etc/X11/xorg.conf.d"
[128945.620] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[128945.620] (==) No Layout section. Using the first Screen section.
[128945.620] (==) No screen section available. Using defaults.
[128945.620] (**) |-->Screen "Default Screen Section" (0)
[128945.620] (**) | |-->Monitor "<default monitor>"
[128945.621] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[128945.621] (==) Automatically adding devices
[128945.621] (==) Automatically enabling devices
[128945.621] (==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
[128945.621] (==) ModulePath set to "/usr/lib/xorg/modules"
[128945.621] (II) The server relies on udev to provide the list of
input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[128945.621] (II) Loader magic: 0x8223580
[128945.621] (II) Module ABI versions:
[128945.621] X.Org ANSI C Emulation: 0.4
[128945.621] X.Org Video Driver: 12.0
[128945.621] X.Org XInput driver : 16.0
[128945.621] X.Org Server Extension : 6.0
[128945.622] (--) PCI:*(0:0:2:0) 8086:2a02:1043:14e2 rev 3, Mem @
0xfeb00000/1048576, 0xd0000000/268435456, I/O @ 0x0000ec00/8, BIOS @
0x????????/131072
[128945.622] (--) PCI: (0:0:2:1) 8086:2a03:1043:14e2 rev 3, Mem @
0xfe900000/1048576, BIOS @ 0x????????/65536
[128945.622] (II) LoadModule: "extmod"
[128945.623] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[128945.623] (II) Module extmod: vendor="X.Org Foundation"
[128945.623] compiled for 1.12.0, module version = 1.0.0
[128945.623] Module class: X.Org Server Extension
[128945.623] ABI class: X.Org Server Extension, version 6.0
[128945.623] (II) Loading extension SELinux
[128945.623] (II) Loading extension MIT-SCREEN-SAVER
[128945.623] (II) Loading extension XFree86-VidModeExtension
[128945.623] (II) Loading extension XFree86-DGA
[128945.623] (II) Loading extension DPMS
[128945.623] (II) Loading extension XVideo
[128945.623] (II) Loading extension XVideo-MotionCompensation
[128945.623] (II) Loading extension X-Resource
[128945.623] (II) LoadModule: "dbe"
[128945.624] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[128945.624] (II) Module dbe: vendor="X.Org Foundation"
[128945.624] compiled for 1.12.0, module version = 1.0.0
[128945.624] Module class: X.Org Server Extension
[128945.624] ABI class: X.Org Server Extension, version 6.0
[128945.624] (II) Loading extension DOUBLE-BUFFER
[128945.624] (II) LoadModule: "glx"
[128945.624] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[128945.624] (II) Module glx: vendor="X.Org Foundation"
[128945.624] compiled for 1.12.0, module version = 1.0.0
[128945.624] ABI class: X.Org Server Extension, version 6.0
[128945.624] (==) AIGLX enabled
[128945.624] (II) Loading extension GLX
[128945.624] (II) LoadModule: "record"
[128945.624] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[128945.625] (II) Module record: vendor="X.Org Foundation"
[128945.625] compiled for 1.12.0, module version = 1.13.0
[128945.625] Module class: X.Org Server Extension
[128945.625] ABI class: X.Org Server Extension, version 6.0
[128945.625] (II) Loading extension RECORD
[128945.625] (II) LoadModule: "dri"
[128945.625] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[128945.625] (II) Module dri: vendor="X.Org Foundation"
[128945.625] compiled for 1.12.0, module version = 1.0.0
[128945.625] ABI class: X.Org Server Extension, version 6.0
[128945.625] (II) Loading extension XFree86-DRI
[128945.625] (II) LoadModule: "dri2"
[128945.625] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[128945.625] (II) Module dri2: vendor="X.Org Foundation"
[128945.625] compiled for 1.12.0, module version = 1.2.0
[128945.625] ABI class: X.Org Server Extension, version 6.0
[128945.625] (II) Loading extension DRI2
[128945.626] (==) Matched intel as autoconfigured driver 0
[128945.626] (==) Matched vesa as autoconfigured driver 1
[128945.626] (==) Matched fbdev as autoconfigured driver 2
[128945.626] (==) Assigned the driver to the xf86ConfigLayout
[128945.626] (II) LoadModule: "intel"
[128945.626] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[128945.626] (II) Module intel: vendor="X.Org Foundation"
[128945.626] compiled for 1.11.99.901, module version = 2.18.0
[128945.626] Module class: X.Org Video Driver
[128945.626] ABI class: X.Org Video Driver, version 12.0
[128945.626] (II) LoadModule: "vesa"
[128945.626] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[128945.626] (II) Module vesa: vendor="X.Org Foundation"
[128945.626] compiled for 1.11.99.901, module version = 2.3.0
[128945.626] Module class: X.Org Video Driver
[128945.626] ABI class: X.Org Video Driver, version 12.0
[128945.626] (II) LoadModule: "fbdev"
[128945.626] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[128945.626] (II) Module fbdev: vendor="X.Org Foundation"
[128945.626] compiled for 1.11.99.901, module version = 0.4.2
[128945.626] ABI class: X.Org Video Driver, version 12.0
[128945.626] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server
[128945.627] (II) VESA: driver for VESA chipsets: vesa
[128945.627] (II) FBDEV: driver for framebuffer: fbdev
[128945.627] (--) using VT number 2
[128945.639] (WW) Falling back to old probe method for vesa
[128945.639] (WW) Falling back to old probe method for fbdev
[128945.639] (II) Loading sub module "fbdevhw"
[128945.639] (II) LoadModule: "fbdevhw"
[128945.639] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[128945.639] (II) Module fbdevhw: vendor="X.Org Foundation"
[128945.639] compiled for 1.12.0, module version = 0.0.2
[128945.639] ABI class: X.Org Video Driver, version 12.0
[128945.639] drmOpenDevice: node name is /dev/dri/card0
[128945.640] drmOpenDevice: open result is 8, (OK)
[128945.640] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
[128945.640] drmOpenDevice: node name is /dev/dri/card0
[128945.640] drmOpenDevice: open result is 8, (OK)
[128945.640] drmOpenByBusid: drmOpenMinor returns 8
[128945.640] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[128945.640] (II) intel(0): Creating default Display subsection in
Screen section
"Default Screen Section" for depth/fbbpp 24/32
[128945.640] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[128945.640] (==) intel(0): RGB weight 888
[128945.640] (==) intel(0): Default visual is TrueColor
[128945.640] (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM
[128945.640] (--) intel(0): Chipset: "965GM"
[128945.640] (**) intel(0): Relaxed fencing enabled
[128945.640] (**) intel(0): Wait on SwapBuffers? enabled
[128945.640] (**) intel(0): Triple buffering? enabled
[128945.640] (**) intel(0): Framebuffer tiled
[128945.640] (**) intel(0): Pixmaps tiled
[128945.640] (**) intel(0): 3D buffers tiled
[128945.640] (**) intel(0): SwapBuffers wait enabled
[128945.640] (==) intel(0): video overlay key set to 0x101fe
[128945.640] (II) intel(0): Output LVDS1 has no monitor section
[128945.640] (II) intel(0): found backlight control interface
/sys/class/backlight/acpi_video0
[128945.656] (II) intel(0): Output VGA1 has no monitor section
[128945.656] (II) intel(0): EDID for output LVDS1
[128945.656] (II) intel(0): Manufacturer: CMO Model: 1554 Serial#: 0
[128945.656] (II) intel(0): Year: 2007 Week: 40
[128945.656] (II) intel(0): EDID Version: 1.3
[128945.656] (II) intel(0): Digital Display Input
[128945.656] (II) intel(0): Max Image Size [cm]: horiz.: 33 vert.: 21
[128945.656] (II) intel(0): Gamma: 2.20
[128945.656] (II) intel(0): No DPMS capabilities specified
[128945.656] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[128945.656] (II) intel(0): First detailed timing is preferred mode
[128945.656] (II) intel(0): redX: 0.602 redY: 0.340 greenX: 0.306
greenY: 0.530
[128945.656] (II) intel(0): blueX: 0.151 blueY: 0.120 whiteX: 0.313
whiteY: 0.329
[128945.656] (II) intel(0): Manufacturer's mask: 0
[128945.656] (II) intel(0): Supported detailed timing:
[128945.656] (II) intel(0): clock: 71.0 MHz Image Size: 331 x 207 mm
[128945.656] (II) intel(0): h_active: 1280 h_sync: 1328 h_sync_end
1360 h_blank_end 1440 h_border: 0
[128945.656] (II) intel(0): v_active: 800 v_sync: 803 v_sync_end 809
v_blanking: 823 v_border: 0
[128945.656] (II) intel(0): N154I3-L03
[128945.656] (II) intel(0): CMO
[128945.656] (II) intel(0): N154I3-L03
[128945.656] (II) intel(0): EDID (in hex):
[128945.656] (II) intel(0): 00ffffffffffff000daf541500000000
[128945.656] (II) intel(0): 28110103802115780a07f59a574e8726
[128945.656] (II) intel(0): 1e505400000001010101010101010101
[128945.656] (II) intel(0): 010101010101bc1b00a0502017303020
[128945.656] (II) intel(0): 36004bcf10000018000000fe004e3135
[128945.656] (II) intel(0): 3449332d4c30330a2020000000fe0043
[128945.656] (II) intel(0): 4d4f0a202020202020202020000000fe
[128945.656] (II) intel(0): 004e31353449332d4c30330a202000a5
[128945.656] (II) intel(0): EDID vendor "CMO", prod id 5460
[128945.656] (II) intel(0): Printing DDC gathered Modelines:
[128945.656] (II) intel(0): Modeline "1280x800"x0.0 71.00 1280 1328
1360 1440 800 803 809 823 -hsync -vsync (49.3 kHz eP)
[128945.656] (II) intel(0): Not using default mode "320x240"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "400x300"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "400x300"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "512x384"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "640x480"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "640x512"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "800x600"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "896x672"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "928x696"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "960x720"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "700x525"
(doublescan mode not supported)
[128945.656] (II) intel(0): Not using default mode "1024x768"
(doublescan mode not supported)
[128945.656] (II) intel(0): Printing probed modes for output LVDS1
[128945.656] (II) intel(0): Modeline "1280x800"x59.9 71.00 1280
1328 1360 1440 800 803 809 823 -hsync -vsync (49.3 kHz eP)
[128945.656] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024
1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz d)
[128945.656] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840
968 1056 600 601 605 628 +hsync +vsync (37.9 kHz d)
[128945.656] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824
896 1024 600 601 603 625 +hsync +vsync (35.2 kHz d)
[128945.656] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656
752 800 480 490 492 525 -hsync -vsync (31.5 kHz d)
[128945.672] (II) intel(0): EDID for output VGA1
[128945.672] (II) intel(0): Output LVDS1 connected
[128945.672] (II) intel(0): Output VGA1 disconnected
[128945.672] (II) intel(0): Using exact sizes for initial modes
[128945.672] (II) intel(0): Output LVDS1 using initial mode 1280x800 +0+0
[128945.672] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0)
unless otherwise stated.
[128945.672] (II) intel(0): Kernel page flipping support detected, enabling
[128945.672] (**) intel(0): Display dimensions: (330, 210) mm
[128945.672] (**) intel(0): DPI set to (98, 96)
[128945.672] (II) Loading sub module "fb"
[128945.672] (II) LoadModule: "fb"
[128945.672] (II) Loading /usr/lib/xorg/modules/libfb.so
[128945.672] (II) Module fb: vendor="X.Org Foundation"
[128945.672] compiled for 1.12.0, module version = 1.0.0
[128945.672] ABI class: X.Org ANSI C Emulation, version 0.4
[128945.672] (II) Loading sub module "dri2"
[128945.672] (II) LoadModule: "dri2"
[128945.672] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[128945.673] (II) Module dri2: vendor="X.Org Foundation"
[128945.673] compiled for 1.12.0, module version = 1.2.0
[128945.673] ABI class: X.Org Server Extension, version 6.0
[128945.673] (II) UnloadModule: "vesa"
[128945.673] (II) Unloading vesa
[128945.673] (II) UnloadModule: "fbdev"
[128945.673] (II) Unloading fbdev
[128945.673] (II) UnloadSubModule: "fbdevhw"
[128945.673] (II) Unloading fbdevhw
[128945.673] (==) Depth 24 pixmap format is 32 bpp
[128945.673] (II) intel(0): [DRI2] Setup complete
[128945.673] (II) intel(0): [DRI2] DRI driver: i965
[128945.673] (II) intel(0): Allocated new frame buffer 1280x800 stride
5120, tiled
[128945.689] (II) UXA(0): Driver registered support for the following
operations:
[128945.689] (II) solid
[128945.689] (II) copy
[128945.689] (II) composite (RENDER acceleration)
[128945.689] (II) put_image
[128945.689] (II) get_image
[128945.689] (==) intel(0): Backing store disabled
[128945.689] (==) intel(0): Silken mouse enabled
[128945.689] (II) intel(0): Initializing HW Cursor
[128945.748] (II) intel(0): RandR 1.2 enabled, ignore the following
RandR disabled message.
[128945.758] (==) intel(0): DPMS enabled
[128945.758] (==) intel(0): Intel XvMC decoder enabled
[128945.758] (II) intel(0): Set up textured video
[128945.758] (II) intel(0): Set up overlay video
[128945.758] (II) intel(0): [XvMC] i965_xvmc driver initialized.
[128945.758] (II) intel(0): direct rendering: DRI2 Enabled
[128945.758] (==) intel(0): hotplug detection: "enabled"
[128945.759] (--) RandR disabled
[128945.759] (II) Initializing built-in extension Generic Event Extension
[128945.759] (II) Initializing built-in extension SHAPE
[128945.759] (II) Initializing built-in extension MIT-SHM
[128945.759] (II) Initializing built-in extension XInputExtension
[128945.759] (II) Initializing built-in extension XTEST
[128945.759] (II) Initializing built-in extension BIG-REQUESTS
[128945.759] (II) Initializing built-in extension SYNC
[128945.759] (II) Initializing built-in extension XKEYBOARD
[128945.759] (II) Initializing built-in extension XC-MISC
[128945.759] (II) Initializing built-in extension XINERAMA
[128945.759] (II) Initializing built-in extension XFIXES
[128945.759] (II) Initializing built-in extension RENDER
[128945.759] (II) Initializing built-in extension RANDR
[128945.759] (II) Initializing built-in extension COMPOSITE
[128945.759] (II) Initializing built-in extension DAMAGE
[128945.761] (II) SELinux: Disabled by boolean
[128945.784] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[128945.784] (II) AIGLX: enabled GLX_INTEL_swap_event
[128945.784] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[128945.784] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[128945.789] (II) AIGLX: Loaded and initialized i965
[128945.790] (II) GLX: Initialized DRI2 GL provider for screen 0
[128945.790] (II) intel(0): Setting screen physical size to 338 x 211
[128945.833] (II) config/udev: Adding input device Power Button
(/dev/input/event2)
[128945.833] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[128945.833] (**) Power Button: Applying InputClass "system-setup-keyboard"
[128945.833] (II) LoadModule: "evdev"
[128945.833] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[128945.833] (II) Module evdev: vendor="X.Org Foundation"
[128945.833] compiled for 1.12.0, module version = 2.7.0
[128945.833] Module class: X.Org XInput Driver
[128945.833] ABI class: X.Org XInput driver, version 16.0
[128945.833] (II) Using input driver 'evdev' for 'Power Button'
[128945.833] (**) Power Button: always reports core events
[128945.833] (**) evdev: Power Button: Device: "/dev/input/event2"
[128945.834] (--) evdev: Power Button: Vendor 0 Product 0x1
[128945.834] (--) evdev: Power Button: Found keys
[128945.834] (II) evdev: Power Button: Configuring as keyboard
[128945.834] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[128945.834] (II) XINPUT: Adding extended input device "Power Button"
(type: KEYBOARD, id 6)
[128945.834] (**) Option "xkb_rules" "evdev"
[128945.834] (**) Option "xkb_model" "pc105"
[128945.834] (**) Option "xkb_layout" "pt"
[128945.834] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[128945.863] (II) config/udev: Adding input device Video Bus (/dev/input/event6)
[128945.864] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[128945.864] (**) Video Bus: Applying InputClass "system-setup-keyboard"
[128945.864] (II) Using input driver 'evdev' for 'Video Bus'
[128945.864] (**) Video Bus: always reports core events
[128945.864] (**) evdev: Video Bus: Device: "/dev/input/event6"
[128945.864] (--) evdev: Video Bus: Vendor 0 Product 0x6
[128945.864] (--) evdev: Video Bus: Found keys
[128945.864] (II) evdev: Video Bus: Configuring as keyboard
[128945.864] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input6/event6"
[128945.864] (II) XINPUT: Adding extended input device "Video Bus"
(type: KEYBOARD, id 7)
[128945.864] (**) Option "xkb_rules" "evdev"
[128945.864] (**) Option "xkb_model" "pc105"
[128945.864] (**) Option "xkb_layout" "pt"
[128945.864] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[128945.864] (II) config/udev: Adding input device Lid Switch
(/dev/input/event1)
[128945.864] (II) No input driver specified, ignoring this device.
[128945.864] (II) This device may have been added with another device file.
[128945.865] (II) config/udev: Adding input device Sleep Button
(/dev/input/event0)
[128945.865] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[128945.865] (**) Sleep Button: Applying InputClass "system-setup-keyboard"
[128945.865] (II) Using input driver 'evdev' for 'Sleep Button'
[128945.865] (**) Sleep Button: always reports core events
[128945.865] (**) evdev: Sleep Button: Device: "/dev/input/event0"
[128945.865] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[128945.865] (--) evdev: Sleep Button: Found keys
[128945.865] (II) evdev: Sleep Button: Configuring as keyboard
[128945.865] (**) Option "config_info"
"udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input0/event0"
[128945.865] (II) XINPUT: Adding extended input device "Sleep Button"
(type: KEYBOARD, id 8)
[128945.865] (**) Option "xkb_rules" "evdev"
[128945.865] (**) Option "xkb_model" "pc105"
[128945.865] (**) Option "xkb_layout" "pt"
[128945.865] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
[128945.866] (II) config/udev: Adding input device HDA Intel Mic
(/dev/input/event8)
[128945.866] (II) No input driver specified, ignoring this device.
[128945.866] (II) This device may have been added with another device file.
[128945.866] (II) config/udev: Adding input device HDA Intel Headphone
(/dev/input/event9)
[128945.866] (II) No input driver specified, ignoring this device.
[128945.866] (II) This device may have been added with another device file.
[128945.866] (II) config/udev: Adding input device PS/2+USB Mouse
(/dev/input/event4)
[128945.867] (**) PS/2+USB Mouse: Applying InputClass "evdev pointer catchall"
[128945.867] (II) Using input driver 'evdev' for 'PS/2+USB Mouse'
[128945.867] (**) PS/2+USB Mouse: always reports core events
[128945.867] (**) evdev: PS/2+USB Mouse: Device: "/dev/input/event4"
[128945.867] (--) evdev: PS/2+USB Mouse: Vendor 0x4f3 Product 0x212
[128945.867] (--) evdev: PS/2+USB Mouse: Found 9 mouse buttons
[128945.867] (--) evdev: PS/2+USB Mouse: Found scroll wheel(s)
[128945.867] (--) evdev: PS/2+USB Mouse: Found relative axes
[128945.867] (--) evdev: PS/2+USB Mouse: Found x and y relative axes
[128945.867] (II) evdev: PS/2+USB Mouse: Configuring as mouse
[128945.867] (II) evdev: PS/2+USB Mouse: Adding scrollwheel support
[128945.867] (**) evdev: PS/2+USB Mouse: YAxisMapping: buttons 4 and 5
[128945.867] (**) evdev: PS/2+USB Mouse: EmulateWheelButton: 4,
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[128945.867] (**) Option "config_info"
"udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-1/6-1:1.0/input/input399/event4"
[128945.867] (II) XINPUT: Adding extended input device "PS/2+USB
Mouse" (type: MOUSE, id 9)
[128945.867] (II) evdev: PS/2+USB Mouse: initialized for relative axes.
[128945.867] (**) PS/2+USB Mouse: (accel) keeping acceleration scheme 1
[128945.867] (**) PS/2+USB Mouse: (accel) acceleration profile 0
[128945.867] (**) PS/2+USB Mouse: (accel) acceleration factor: 2.000
[128945.867] (**) PS/2+USB Mouse: (accel) acceleration threshold: 4
[128945.868] (II) config/udev: Adding input device PS/2+USB Mouse
(/dev/input/mouse0)
[128945.868] (II) No input driver specified, ignoring this device.
[128945.868] (II) This device may have been added with another device file.
[128945.868] (II) config/udev: Adding input device WALTOP
International Corp. Media Tablet (/dev/input/event10)
[128945.868] (**) WALTOP International Corp. Media Tablet...
[truncated message content] |
|
From: Eduardo H. S. <hob...@gm...> - 2012-04-29 21:46:51
|
---------- Forwarded message ---------- From: Eduardo H. Silva <hob...@gm...> Date: 2012/4/29 Subject: Re: [DIGImend-users] Aiptek Media Tablet 14000u worked instantly (and almost complete) in linux 3.3.2 To: "Favux ..." <fav...@gm...> 2012/4/29 Favux ... <fav...@gm...>: > On Sun, Apr 29, 2012 at 7:35 AM, Eduardo H. Silva <hob...@gm...> wrote: >> >> Yep, with your new config file, the scroll wheels work, and the stylus >> has pressure. But the first button paints, and the second button >> paints while held and undos it when released. In inkscape, this 2nd >> button sometimes does a zoom in. >> >>> The wheels and mode buttons should work, but may need some configuration. >> >> After using Dave's configuration, the wheel and mode buttons work immediately. > > Good. So we have everything working with 52-waltop-custom.conf except > the two stylus side buttons. We need to find out why. Your new > Xorg.0.log shows that event10 is the stylus and is being set up by > Wacom while events 11, 12, and 13 are being claimed by evdev. I think > that is correct, Nick can tell us. On those 3 events evdev is > reporting: > ButtonMapping '1 2 3' > Event 10 on Wacom is reporting: > using pressure threshold of 27 for button 1 > which is correct. > > Still see Aiptek, so you commented out the evdev driver line but left > the matching in? Oops, I forgot I had a waltop-on-evdev.conf file which looked for identifier in /usr/share/X11/xorg.conf.d/ . I've removed it. > > With the 52-waltop-custom.conf let's try to find out what we have. > What is the output of? > xsetwacom list WALTOP International Corp. Media Tablet stylus id: 10 type: STYLUS > I'll guess that event10 was the ID # 9 on your 'xinput list' and that > hasn't changed. Let's see if we can get a button map reported in the > output of: > xinput list-props 9 > If rerunning 'xinput list' shows different ID numbers you'll have to > guess until you hit the stylus. You'll know you have the right one > when the driver in the output is wacom not evdev. xinput list-props 10: Device 'WALTOP International Corp. Media Tablet stylus': Device Enabled (134): 1 Coordinate Transformation Matrix (136): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (260): 0 Device Accel Constant Deceleration (261): 1.000000 Device Accel Adaptive Deceleration (262): 1.000000 Device Accel Velocity Scaling (263): 10.000000 Device Node (254): "/dev/input/event10" Wacom Tablet Area (288): 0, 0, 16383, 16383 Wacom Rotation (289): 0 Wacom Pressurecurve (290): 0, 0, 100, 100 Wacom Serial IDs (291): 1280, 1, 0, 0, 0 Wacom Serial ID binding (292): 0 Wacom Pressure Threshold (293): 27 Wacom Sample and Suppress (294): 2, 4 Wacom Enable Touch (295): 1 Wacom Hover Click (296): 1 Wacom Enable Touch Gesture (297): 0 Wacom Touch Gesture Parameters (298): 0, 0, 250 Wacom Tool Type (299): "STYLUS" (281) Wacom Button Actions (300): "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0) Device Product ID (253): 5935, 1280 Wacom Debug Levels (301): 0, 0 Hm, "Button Actions: "None"... > We can also get the assigned button values reported separately using > the xsetwacom get command. So using the stylus ID # from above: > xsetwacom get 9 Button 1 > xsetwacom get 9 Button 2 > xsetwacom get 9 Button 3 Yep, shows them as 1, 2, 3. > The other thing is to look at the gnome-settings-daemon's key values. > Since the applet isn't allowing access install dconf-editor and run > it. Then navigate to org.gnome.settings-daemon.peripherals.wacom. If > your tablet was listed there, under the tablet name would be one or > more styli. They should report a pressurecurve and the active one a > buttonmapping. Anything regarding a stylus or tablet in there? > Buttonmapping? Hmm, I don't have a wacom sections under peripherals... > >> The Gnome Wacom applet doesn't shown me options, saying that no tablet >> was detected. This with all my previous configurations, and with your >> new suggestion. Btw, I just need to restart X to have the >> configuration re-read right? > > I don't think so. As far as I know it should be run-time, changing > the gnome-settings-daemon's key values with the Wacom Tablet applet > should change behavior instantly just like a xsetwacom command. Ah, but what about adding rules in /etc/X11/xorg.conf.d/? > If it is on the Wacom driver why isn't it showing up on the tablet > applet? We know the xf86-input-wacom driver is handling the stylus > according to the Xorg.0.log and it is working because you have > pressure. But what about the last message about wacom in Xorg.0.log: UnloadModule: "wacom" ? > Libwacom does have a stylus file with a generic stylus > section. Libwacom is a Wacom tablet metadata library that was added > shortly after the initial Wacom Graphics Tablet applet came out. And > the applet was then changed to work with it. The idea was to simplify > the applet and make the library available to other applications that > might want to use the tablet metadata. So my guess is that it is > libwacom blocking recognition of the Waltop stylus, which is why you > don't see it in the applet. If so that may be also true for the > N-Trig and Hanwang tablets. Not good. I think I need to ask the LWP > about this. > > Favux |
|
From: Favux ... <fav...@gm...> - 2012-04-29 23:12:04
|
Thanks Eduardo, I'll take a look.
But just to let you know:
Option "Button1" "1"
is always the default. That's why I didn't include it in the button
options with the Wacom snippet. You always want to leave Button1 (the
stylus tip) assigned to 1 (left click). Otherwise you can't select or
draw with the stylus as you found out.
There was a bug in the buttons a little while ago. What version of
xf86-input-wacom does Fedora 16 beta have?
xsetwacom -V
Favux
|
|
From: Eduardo H. S. <hob...@gm...> - 2012-04-29 23:19:24
|
2012/4/30 Favux ... <fav...@gm...>: > Thanks Eduardo, I'll take a look. > > But just to let you know: > Option "Button1" "1" > > is always the default. That's why I didn't include it in the button > options with the Wacom snippet. You always want to leave Button1 (the > stylus tip) assigned to 1 (left click). Otherwise you can't select or > draw with the stylus as you found out. > > > There was a bug in the buttons a little while ago. What version of > xf86-input-wacom does Fedora 16 beta have? > xsetwacom -V > > Favux It's at version 0.14.0 Eduardo |
|
From: Favux ... <fav...@gm...> - 2012-04-29 23:30:02
|
OK, that has the Jason's fix then. What was happening is when folks did a:
xsetwacom set <device name> Button 1 1
they were breaking things. There is no reason to ever run that since
it is the driver default, but still it shouldn't break things. It
turned out in a variable renaming one of the button release functions
didn't get the variable renamed. Oops.
Favux
|
|
From: Favux ... <fav...@gm...> - 2012-04-30 00:12:29
|
On Sun, Apr 29, 2012 at 6:05 PM, Eduardo H. Silva <hob...@gm...> wrote:
>
>> The gnome-settings-daemon runs after the xorg.conf.d conf files so
>> what it says goes. And you can over ride it with an xsetwacom
>> command. So what happens if you run these commands:
>> xsetwacom set 10 Button 2 2
>> xsetwacom set 10 Button 3 3
>> Any change on the stylus buttons behavior? If the tablet isn't being
>> recognized maybe no gnome-settings-daemon key values are being
>> applied.
>
> It remains the same, and I've figured that:
>
> 1 - xsetwacom is working. If I assign:
>
> Button 1 1
> Button 2 3
> Button 3 2
>
> , the button's behaviors switch.
>
> 2 - if I assign:
> Button 1 0
> Button 2 2
> Button 3 3
>
> , the buttons are working as expected in Gimp and elsewhere, but
> pressing with the stylus doesn't work.
Out of curiosity what happens when you assign 'Button 1 1' along with?
Button 2 2
Button 3 3
Still see the confusion between Button 2 and Button 1?
> Also, the broken behavior in Inkscape and throughout Gnome's interface
> is different than Gimp's. If the assignment is:
> Button 1 1
> Button 2 2
> Button 3 3
>
> , button 2 does action 1 and 2 (left and middle-click) and button 3
> does action 3 (right-click).
So for now is it OK if you use xsetwacom to assign:
Button 2 3
Button 3 3
Sure they're both assigned 3 (right click), but does it avoid the
confusion with 2 (middle click) & 1?
>> So if this works try uncommenting those button options from
>> earlier in the Wacom snippet and see what happens. Actually try that
>> either way I suppose.
>
> Uncommented the options and restarted X, but
Oops, what happened?
>>> But what about the last message about wacom in Xorg.0.log:
>>> UnloadModule: "wacom"
>>
>> What, where is that in the last Xorg.0.log snippet you gave? We know
>> the stylus is on the Wacom X driver (module) from the diagnostics you
>> ran above.
>
> Ah, at the time of that diagnostic, I was only copying what seemed to
> have to do with the tablets, and may have missed the unload message.
> Also, only now I noticed that once I removed waltop-on-evdev.conf from
> /usr/share/X11/xorg.conf.d/ , makes the wheels not work.
> Sorry about this confusion.
So now you've lost the scroll wheels. Then leave it in? Or do we
need to match to another evdev snippet, maybe?
MatchIsPointer "on"
Or else try the snippet Nick suggested for that.
> Ok, so my configuration is exactly like the one you told in your first
> reply. To make sure, it is:
>
> /usr/share/X11/xorg.conf.d/:
> Section "InputClass"
> Identifier "Wacom class"
> MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL"
> MatchDevicePath "/dev/input/event*"
> Driver "wacom"
> # Option "Button1" "3"
> # Option "Button2" "1"
> # Option "Button3" "2"
>
>
> EndSection
>
> Section "InputClass"
> Identifier "Wacom serial class"
> MatchProduct "Serial Wacom Tablet"
> Driver "wacom"
> EndSection
>
> Section "InputClass"
> Identifier "Wacom serial class identifiers"
> MatchProduct "WACf|FUJ02e5|FUJ02e7|FUJ02e9"
> Driver "wacom"
> EndSection
>
>
> # N-Trig Duosense Electromagnetic Digitizer
> Section "InputClass"
> Identifier "Wacom N-Trig class"
> MatchProduct "HID 1b96:0001|N-Trig Pen"
> MatchDevicePath "/dev/input/event*"
> Driver "wacom"
> Option "Button2" "3"
> EndSection
>
> /etc/X11/xorg.conf.d/52-waltop-custom.conf
> Section "InputClass"
> Identifier "Waltop evdev custom"
> MatchProduct "WALTOP"
> MatchIsKeyboard "on"
> MatchDevicePath "/dev/input/event*"
> Driver "evdev"
> EndSection
>
> Section "InputClass"
> Identifier "Waltop wacom custom"
> MatchProduct "WALTOP"
> MatchIsTablet "on"
> MatchDevicePath "/dev/input/event*"
> Driver "wacom"
> Option "Button2" "2"
> Option "Button3" "3"
> EndSection
>
>
> The complete Xorg.0.log after restarting X with the tablet plugged in:
>
> [128945.868] (II) config/udev: Adding input device WALTOP
> International Corp. Media Tablet (/dev/input/event10)
> [128945.868] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "evdev tablet catchall"
> [128945.868] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "Wacom class"
> [128945.868] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "Waltop wacom custom"
> [128945.868] (II) LoadModule: "wacom"
> [128945.868] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so
> [128945.868] (II) Module wacom: vendor="X.Org Foundation"
> [128945.869] compiled for 1.11.99.901, module version = 0.14.0
> [128945.869] Module class: X.Org XInput Driver
> [128945.869] ABI class: X.Org XInput driver, version 16.0
> [128945.869] (II) Using input driver 'wacom' for 'WALTOP International
> Corp. Media Tablet'
> [128945.869] (**) WALTOP International Corp. Media Tablet: always
> reports core events
> [128945.869] (**) Option "Device" "/dev/input/event10"
> [128945.869] (II) WALTOP International Corp. Media Tablet: type not
> specified, assuming 'stylus'.
> [128945.869] (II) WALTOP International Corp. Media Tablet: other types
> will be automatically added.
> [128945.869] (**) Option "Button2" "2"
> [128945.869] (**) Option "Button3" "3"
> [128945.869] (--) WALTOP International Corp. Media Tablet stylus:
> using pressure threshold of 27 for button 1
> [128945.869] (--) WALTOP International Corp. Media Tablet stylus:
> Wacom USB Bamboo tablet maxX=16383 maxY=16383 maxZ=1023 resX=53000
> resY=88000 tilt=disabled
> [128945.869] (II) WALTOP International Corp. Media Tablet stylus:
> hotplugging dependent devices.
> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus:
> Invalid type 'eraser' for this device.
> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus:
> Invalid type 'cursor' for this device.
> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus:
> Invalid type 'touch' for this device.
> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus:
> Invalid type 'pad' for this device.
> [128945.869] (II) WALTOP International Corp. Media Tablet stylus:
> hotplugging completed.
> [128945.869] (**) Option "config_info"
> "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input424/event10"
> [128945.869] (II) XINPUT: Adding extended input device "WALTOP
> International Corp. Media Tablet stylus" (type: STYLUS, id 10)
> [128945.869] (**) WALTOP International Corp. Media Tablet stylus:
> (accel) keeping acceleration scheme 1
> [128945.869] (**) WALTOP International Corp. Media Tablet stylus:
> (accel) acceleration profile 0
> [128945.869] (**) WALTOP International Corp. Media Tablet stylus:
> (accel) acceleration factor: 2.000
> [128945.869] (**) WALTOP International Corp. Media Tablet stylus:
> (accel) acceleration threshold: 4
> [128945.870] (II) config/udev: Adding input device WALTOP
> International Corp. Media Tablet (/dev/input/mouse2)
> [128945.870] (II) No input driver specified, ignoring this device.
> [128945.870] (II) This device may have been added with another device file.
> [128945.870] (II) config/udev: Adding input device WALTOP
> International Corp. Media Tablet (/dev/input/event11)
> [128945.870] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "Wacom class"
> [128945.870] (II) Using input driver 'wacom' for 'WALTOP International
> Corp. Media Tablet'
> [128945.870] (**) WALTOP International Corp. Media Tablet: always
> reports core events
> [128945.870] (**) Option "Device" "/dev/input/event11"
> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid
> type 'stylus' for this device.
> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid
> type 'eraser' for this device.
> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid
> type 'cursor' for this device.
> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid
> type 'touch' for this device.
> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid
> type 'pad' for this device.
> [128945.871] (EE) WALTOP International Corp. Media Tablet: No type specified
> [128945.871] (EE) PreInit returned 8 for "WALTOP International Corp.
> Media Tablet"
> [128945.871] (II) UnloadModule: "wacom"
I can't tell if that is a general wacom module/X driver unload or not.
As long as 'xsetwacom list' still shows the stylus and you see the
Wacom driver in 'xinput list-props <stylus ID #> we may not need to
worry about this. It appears to be happening to event11 not event10
which is the stylus. But if the stylus isn't in 'xsetwacom list' etc.
then we do have a problem.
> [128945.871] (II) config/udev: Adding input device WALTOP
> International Corp. Media Tablet (/dev/input/event12)
> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "evdev keyboard catchall"
> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "Wacom class"
> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "system-setup-keyboard"
> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "Waltop evdev custom"
> [128945.871] (II) Using input driver 'evdev' for 'WALTOP International
> Corp. Media Tablet'
> [128945.871] (**) WALTOP International Corp. Media Tablet: always
> reports core events
> [128945.871] (**) evdev: WALTOP International Corp. Media Tablet:
> Device: "/dev/input/event12"
> [128945.871] (--) evdev: WALTOP International Corp. Media Tablet:
> Vendor 0x172f Product 0x500
> [128945.871] (--) evdev: WALTOP International Corp. Media Tablet: Found keys
> [128945.871] (II) evdev: WALTOP International Corp. Media Tablet:
> Configuring as keyboard
> [128945.871] (**) Option "config_info"
> "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input426/event12"
> [128945.871] (II) XINPUT: Adding extended input device "WALTOP
> International Corp. Media Tablet" (type: KEYBOARD, id 11)
> [128945.871] (**) Option "xkb_rules" "evdev"
> [128945.871] (**) Option "xkb_model" "pc105"
> [128945.871] (**) Option "xkb_layout" "pt"
> [128945.871] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
> [128945.872] (II) config/udev: Adding input device WALTOP
> International Corp. Media Tablet (/dev/input/event13)
> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "evdev keyboard catchall"
> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "Wacom class"
> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "system-setup-keyboard"
> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying
> InputClass "Waltop evdev custom"
> [128945.872] (II) Using input driver 'evdev' for 'WALTOP International
> Corp. Media Tablet'
> [128945.872] (**) WALTOP International Corp. Media Tablet: always
> reports core events
> [128945.872] (**) evdev: WALTOP International Corp. Media Tablet:
> Device: "/dev/input/event13"
> [128945.872] (--) evdev: WALTOP International Corp. Media Tablet:
> Vendor 0x172f Product 0x500
> [128945.872] (--) evdev: WALTOP International Corp. Media Tablet: Found keys
> [128945.872] (II) evdev: WALTOP International Corp. Media Tablet:
> Configuring as keyboard
> [128945.872] (**) Option "config_info"
> "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input427/event13"
> [128945.872] (II) XINPUT: Adding extended input device "WALTOP
> International Corp. Media Tablet" (type: KEYBOARD, id 12)
> [128945.872] (**) Option "xkb_rules" "evdev"
> [128945.872] (**) Option "xkb_model" "pc105"
> [128945.872] (**) Option "xkb_layout" "pt"
> [128945.872] (**) Option "xkb_options" "terminate:ctrl_alt_bksp,"
Assuming we don't have a driver problem and the stylus is on the Wacom
X driver I'm thinking this is a kernel driver problem. What are your
thoughts Nick?
Favux
|
|
From: Eduardo H. S. <hob...@gm...> - 2012-04-30 02:12:09
|
2012/4/30 Favux ... <fav...@gm...>: > On Sun, Apr 29, 2012 at 6:05 PM, Eduardo H. Silva <hob...@gm...> wrote: >> >>> The gnome-settings-daemon runs after the xorg.conf.d conf files so >>> what it says goes. And you can over ride it with an xsetwacom >>> command. So what happens if you run these commands: >>> xsetwacom set 10 Button 2 2 >>> xsetwacom set 10 Button 3 3 >>> Any change on the stylus buttons behavior? If the tablet isn't being >>> recognized maybe no gnome-settings-daemon key values are being >>> applied. >> >> It remains the same, and I've figured that: >> >> 1 - xsetwacom is working. If I assign: >> >> Button 1 1 >> Button 2 3 >> Button 3 2 >> >> , the button's behaviors switch. >> >> 2 - if I assign: >> Button 1 0 >> Button 2 2 >> Button 3 3 >> >> , the buttons are working as expected in Gimp and elsewhere, but >> pressing with the stylus doesn't work. > > Out of curiosity what happens when you assign 'Button 1 1' along with? > Button 2 2 > Button 3 3 > Still see the confusion between Button 2 and Button 1? Yep. >> Also, the broken behavior in Inkscape and throughout Gnome's interface >> is different than Gimp's. If the assignment is: >> Button 1 1 >> Button 2 2 >> Button 3 3 >> >> , button 2 does action 1 and 2 (left and middle-click) and button 3 >> does action 3 (right-click). > > So for now is it OK if you use xsetwacom to assign: > Button 2 3 > Button 3 3 > Sure they're both assigned 3 (right click), but does it avoid the > confusion with 2 (middle click) & 1? No, and now I notice that Button 3 is also linked with what is set for Button 1. >>> So if this works try uncommenting those button options from >>> earlier in the Wacom snippet and see what happens. Actually try that >>> either way I suppose. >> >> Uncommented the options and restarted X, but > > Oops, what happened? oops, should end with "...but things remained the same." > >>>> But what about the last message about wacom in Xorg.0.log: >>>> UnloadModule: "wacom" >>> >>> What, where is that in the last Xorg.0.log snippet you gave? We know >>> the stylus is on the Wacom X driver (module) from the diagnostics you >>> ran above. >> >> Ah, at the time of that diagnostic, I was only copying what seemed to >> have to do with the tablets, and may have missed the unload message. >> Also, only now I noticed that once I removed waltop-on-evdev.conf from >> /usr/share/X11/xorg.conf.d/ , makes the wheels not work. >> Sorry about this confusion. > > So now you've lost the scroll wheels. Then leave it in? Or do we > need to match to another evdev snippet, maybe? > MatchIsPointer "on" > Or else try the snippet Nick suggested for that. No, doesn't work with MatchIsPointer. with Nick's addition, and moving all of the wacom config options to the end of the /etc/X11/xor.conf.d/52-waltop-custom.conf file, I now have volume and scrolling. >> Ok, so my configuration is exactly like the one you told in your first >> reply. To make sure, it is: >> >> /usr/share/X11/xorg.conf.d/: >> Section "InputClass" >> Identifier "Wacom class" >> MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL" >> MatchDevicePath "/dev/input/event*" >> Driver "wacom" >> # Option "Button1" "3" >> # Option "Button2" "1" >> # Option "Button3" "2" >> >> >> EndSection >> >> Section "InputClass" >> Identifier "Wacom serial class" >> MatchProduct "Serial Wacom Tablet" >> Driver "wacom" >> EndSection >> >> Section "InputClass" >> Identifier "Wacom serial class identifiers" >> MatchProduct "WACf|FUJ02e5|FUJ02e7|FUJ02e9" >> Driver "wacom" >> EndSection >> >> >> # N-Trig Duosense Electromagnetic Digitizer >> Section "InputClass" >> Identifier "Wacom N-Trig class" >> MatchProduct "HID 1b96:0001|N-Trig Pen" >> MatchDevicePath "/dev/input/event*" >> Driver "wacom" >> Option "Button2" "3" >> EndSection >> >> /etc/X11/xorg.conf.d/52-waltop-custom.conf >> Section "InputClass" >> Identifier "Waltop evdev custom" >> MatchProduct "WALTOP" >> MatchIsKeyboard "on" >> MatchDevicePath "/dev/input/event*" >> Driver "evdev" >> EndSection >> >> Section "InputClass" >> Identifier "Waltop wacom custom" >> MatchProduct "WALTOP" >> MatchIsTablet "on" >> MatchDevicePath "/dev/input/event*" >> Driver "wacom" >> Option "Button2" "2" >> Option "Button3" "3" >> EndSection >> >> >> The complete Xorg.0.log after restarting X with the tablet plugged in: >> >> [128945.868] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/event10) >> [128945.868] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "evdev tablet catchall" >> [128945.868] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Wacom class" >> [128945.868] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Waltop wacom custom" >> [128945.868] (II) LoadModule: "wacom" >> [128945.868] (II) Loading /usr/lib/xorg/modules/input/wacom_drv.so >> [128945.868] (II) Module wacom: vendor="X.Org Foundation" >> [128945.869] compiled for 1.11.99.901, module version = 0.14.0 >> [128945.869] Module class: X.Org XInput Driver >> [128945.869] ABI class: X.Org XInput driver, version 16.0 >> [128945.869] (II) Using input driver 'wacom' for 'WALTOP International >> Corp. Media Tablet' >> [128945.869] (**) WALTOP International Corp. Media Tablet: always >> reports core events >> [128945.869] (**) Option "Device" "/dev/input/event10" >> [128945.869] (II) WALTOP International Corp. Media Tablet: type not >> specified, assuming 'stylus'. >> [128945.869] (II) WALTOP International Corp. Media Tablet: other types >> will be automatically added. >> [128945.869] (**) Option "Button2" "2" >> [128945.869] (**) Option "Button3" "3" >> [128945.869] (--) WALTOP International Corp. Media Tablet stylus: >> using pressure threshold of 27 for button 1 >> [128945.869] (--) WALTOP International Corp. Media Tablet stylus: >> Wacom USB Bamboo tablet maxX=16383 maxY=16383 maxZ=1023 resX=53000 >> resY=88000 tilt=disabled >> [128945.869] (II) WALTOP International Corp. Media Tablet stylus: >> hotplugging dependent devices. >> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus: >> Invalid type 'eraser' for this device. >> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus: >> Invalid type 'cursor' for this device. >> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus: >> Invalid type 'touch' for this device. >> [128945.869] (EE) WALTOP International Corp. Media Tablet stylus: >> Invalid type 'pad' for this device. >> [128945.869] (II) WALTOP International Corp. Media Tablet stylus: >> hotplugging completed. >> [128945.869] (**) Option "config_info" >> "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input424/event10" >> [128945.869] (II) XINPUT: Adding extended input device "WALTOP >> International Corp. Media Tablet stylus" (type: STYLUS, id 10) >> [128945.869] (**) WALTOP International Corp. Media Tablet stylus: >> (accel) keeping acceleration scheme 1 >> [128945.869] (**) WALTOP International Corp. Media Tablet stylus: >> (accel) acceleration profile 0 >> [128945.869] (**) WALTOP International Corp. Media Tablet stylus: >> (accel) acceleration factor: 2.000 >> [128945.869] (**) WALTOP International Corp. Media Tablet stylus: >> (accel) acceleration threshold: 4 >> [128945.870] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/mouse2) >> [128945.870] (II) No input driver specified, ignoring this device. >> [128945.870] (II) This device may have been added with another device file. >> [128945.870] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/event11) >> [128945.870] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Wacom class" >> [128945.870] (II) Using input driver 'wacom' for 'WALTOP International >> Corp. Media Tablet' >> [128945.870] (**) WALTOP International Corp. Media Tablet: always >> reports core events >> [128945.870] (**) Option "Device" "/dev/input/event11" >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'stylus' for this device. >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'eraser' for this device. >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'cursor' for this device. >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'touch' for this device. >> [128945.870] (EE) WALTOP International Corp. Media Tablet: Invalid >> type 'pad' for this device. >> [128945.871] (EE) WALTOP International Corp. Media Tablet: No type specified >> [128945.871] (EE) PreInit returned 8 for "WALTOP International Corp. >> Media Tablet" >> [128945.871] (II) UnloadModule: "wacom" > > I can't tell if that is a general wacom module/X driver unload or not. > As long as 'xsetwacom list' still shows the stylus and you see the > Wacom driver in 'xinput list-props <stylus ID #> we may not need to > worry about this. It appears to be happening to event11 not event10 > which is the stylus. But if the stylus isn't in 'xsetwacom list' etc. > then we do have a problem. > >> [128945.871] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/event12) >> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "evdev keyboard catchall" >> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Wacom class" >> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "system-setup-keyboard" >> [128945.871] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Waltop evdev custom" >> [128945.871] (II) Using input driver 'evdev' for 'WALTOP International >> Corp. Media Tablet' >> [128945.871] (**) WALTOP International Corp. Media Tablet: always >> reports core events >> [128945.871] (**) evdev: WALTOP International Corp. Media Tablet: >> Device: "/dev/input/event12" >> [128945.871] (--) evdev: WALTOP International Corp. Media Tablet: >> Vendor 0x172f Product 0x500 >> [128945.871] (--) evdev: WALTOP International Corp. Media Tablet: Found keys >> [128945.871] (II) evdev: WALTOP International Corp. Media Tablet: >> Configuring as keyboard >> [128945.871] (**) Option "config_info" >> "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input426/event12" >> [128945.871] (II) XINPUT: Adding extended input device "WALTOP >> International Corp. Media Tablet" (type: KEYBOARD, id 11) >> [128945.871] (**) Option "xkb_rules" "evdev" >> [128945.871] (**) Option "xkb_model" "pc105" >> [128945.871] (**) Option "xkb_layout" "pt" >> [128945.871] (**) Option "xkb_options" "terminate:ctrl_alt_bksp," >> [128945.872] (II) config/udev: Adding input device WALTOP >> International Corp. Media Tablet (/dev/input/event13) >> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "evdev keyboard catchall" >> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Wacom class" >> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "system-setup-keyboard" >> [128945.872] (**) WALTOP International Corp. Media Tablet: Applying >> InputClass "Waltop evdev custom" >> [128945.872] (II) Using input driver 'evdev' for 'WALTOP International >> Corp. Media Tablet' >> [128945.872] (**) WALTOP International Corp. Media Tablet: always >> reports core events >> [128945.872] (**) evdev: WALTOP International Corp. Media Tablet: >> Device: "/dev/input/event13" >> [128945.872] (--) evdev: WALTOP International Corp. Media Tablet: >> Vendor 0x172f Product 0x500 >> [128945.872] (--) evdev: WALTOP International Corp. Media Tablet: Found keys >> [128945.872] (II) evdev: WALTOP International Corp. Media Tablet: >> Configuring as keyboard >> [128945.872] (**) Option "config_info" >> "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb6/6-2/6-2:1.0/input/input427/event13" >> [128945.872] (II) XINPUT: Adding extended input device "WALTOP >> International Corp. Media Tablet" (type: KEYBOARD, id 12) >> [128945.872] (**) Option "xkb_rules" "evdev" >> [128945.872] (**) Option "xkb_model" "pc105" >> [128945.872] (**) Option "xkb_layout" "pt" >> [128945.872] (**) Option "xkb_options" "terminate:ctrl_alt_bksp," > > Assuming we don't have a driver problem and the stylus is on the Wacom > X driver I'm thinking this is a kernel driver problem. What are your > thoughts Nick? > > Favux In inkscape I can test the stylus in a special window, and it shows that pressing the tip and the buttons register differently. Eduardo |
|
From: Favux ... <fav...@gm...> - 2012-04-30 14:21:48
|
Hi, There's a bit of disagreement on the LWP project. Either Waltop tablets with their stylus on the xf86-input-wacom driver are suppose to show up in Wacom Graphics Tablet applet as a generic stylus without details (what I thought had been happening) or they now need a libwacom tablet data file first. The libwacom page on the LWP mediawiki shows a sample data file: http://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Libwacom But either way we should probably submit Waltop data files. Favux |
|
From: Nikolai K. <sp...@gm...> - 2012-05-01 12:16:45
|
Hi Dave, Eduardo, On 04/30/2012 03:12 AM, Favux ... wrote: > Assuming we don't have a driver problem and the stylus is on the Wacom > X driver I'm thinking this is a kernel driver problem. What are your > thoughts Nick? Eduardo, to rule this out, could you please get some evtest output for the stylus event device? You will probably need to run evtest in a text console, because the Wacom driver grabs it under X. Please run "sudo evtest" and try to find out which event device corresponds to the stylus, it will probably be the least numbered among Waltop devices and it will produce output when moving the pen. After you've identified it, could you please capture and send here the evtest output for the "pressure" and "buttons" parts of the "collecting tablet diagnostics" HOWTO: http://sf.net/apps/mediawiki/digimend/?title=Collecting_tablet_diagnostics#Pressure http://sf.net/apps/mediawiki/digimend/?title=Collecting_tablet_diagnostics#Buttons Please use "sudo evtest" in place of "sudo usbhid-dump ...". Meanwhile I'll try to find the time to install Fedora on a virtual machine and try to reproduce you problem with Media Tablet 10.6, which is similar to your model. Thanks! Sincerely, Nick |
|
From: Eduardo H. S. <hob...@gm...> - 2012-05-02 19:55:57
Attachments:
pen_pressure.txt
pen_buttons.txt
|
2012/5/1 Nikolai Kondrashov <sp...@gm...>: > Hi Dave, Eduardo, > > > On 04/30/2012 03:12 AM, Favux ... wrote: >> >> Assuming we don't have a driver problem and the stylus is on the Wacom >> X driver I'm thinking this is a kernel driver problem. What are your >> thoughts Nick? > > > Eduardo, to rule this out, could you please get some evtest output for the > stylus event device? You will probably need to run evtest in a text console, > because the Wacom driver grabs it under X. > > Please run "sudo evtest" and try to find out which event device corresponds > to the stylus, it will probably be the least numbered among Waltop devices > and it will produce output when moving the pen. > > After you've identified it, could you please capture and send here the > evtest output for the "pressure" and "buttons" parts of the "collecting > tablet diagnostics" HOWTO: > > http://sf.net/apps/mediawiki/digimend/?title=Collecting_tablet_diagnostics#Pressure > http://sf.net/apps/mediawiki/digimend/?title=Collecting_tablet_diagnostics#Buttons > > Please use "sudo evtest" in place of "sudo usbhid-dump ...". > > Meanwhile I'll try to find the time to install Fedora on a virtual machine > and try to reproduce you problem with Media Tablet 10.6, which is similar to > your model. > > Thanks! > > Sincerely, > Nick I'm attaching the outputs. Eduardo |
|
From: Nikolai K. <sp...@gm...> - 2012-05-03 05:47:14
|
On 05/02/2012 10:55 PM, Eduardo H. Silva wrote: > I'm attaching the outputs. Thanks! This is unexpected. I see the kernel indeed reporting full pressure on a side button click. This is something new. When I tested this model, it didn't do such thing, so this must be a recent addition. I don't know the purpose though. Could you please do the "pen buttons" test, but with usbhid-dump this time? I have a workaround for this behavior for the tablet with PID 0038. So, if usbhid-dump verifies your tablet does the same thing, I will add its handling there and will send you a kernel patch to test. Sincerely, Nick |
|
From: Eduardo H. S. <hob...@gm...> - 2012-05-06 19:52:36
|
2012/5/3 Nikolai Kondrashov <sp...@gm...>:
> On 05/02/2012 10:55 PM, Eduardo H. Silva wrote:
>>
>> I'm attaching the outputs.
>
>
> Thanks! This is unexpected. I see the kernel indeed reporting full pressure
> on a side button click. This is something new. When I tested this model, it
> didn't do such thing, so this must be a recent addition. I don't know the
> purpose though.
>
> Could you please do the "pen buttons" test, but with usbhid-dump this time?
>
> I have a workaround for this behavior for the tablet with PID 0038. So, if
> usbhid-dump verifies your tablet does the same thing, I will add its
> handling there and will send you a kernel patch to test.
>
> Sincerely,
> Nick
I'm sorry for the late reply, I delayed to the following day to do
what you asked, but then forgot.
The usbhid-dump command, the one you originally linked to, gives the error:
invalid option -- 'm'
Removing the -m option, gives the error:
Not enough arguments
Just doing usbhid-dump --help, shows:
Usage: usbhid-dump [OPTION]... <bus> <dev> [if]
Dump a USB device HID report descriptor(s) and/or stream(s).
Arguments:
bus bus number (1-255)
dev device address (1-255)
if interface number (0-254);
if omitted, all device HID interfaces
are dumped
Options:
-h, --help this help message
-e, --entity=STRING what to dump: either "descriptor",
"stream" or "both"; value can be
abbreviated
-p, --stream-paused start with the stream dump output paused
-f, --stream-feedback enable stream dumping feedback: for every
transfer dumped a dot is printed to stderr
Default options: --entity=descriptor
Signals:
USR1/USR2 pause/resume the stream dump output
usbutils is at version 004-4.
Eduardo
|
|
From: Nikolai K. <sp...@gm...> - 2012-05-07 05:41:54
|
Hi Eduardo, On 05/06/2012 10:52 PM, Eduardo H. Silva wrote: > I'm sorry for the late reply, I delayed to the following day to do > what you asked, but then forgot. > > The usbhid-dump command, the one you originally linked to, gives the error: > > invalid option -- 'm' Most distributions have older version of usbhid-dump. You could download newer version at http://sf.net/apps/mediawiki/digimend/?title=Usbhid-dump or you could use the older one by finding out your tablet bus number and device address using lsusb and then supplying it to usbhid-dump as the arguments. Sincerely, Nick |
|
From: Eduardo H. S. <hob...@gm...> - 2012-05-09 12:44:24
Attachments:
usbhid-dump_pen_buttons.txt
|
2012/5/7 Nikolai Kondrashov <sp...@gm...>: > Hi Eduardo, > > > On 05/06/2012 10:52 PM, Eduardo H. Silva wrote: >> >> I'm sorry for the late reply, I delayed to the following day to do >> what you asked, but then forgot. >> >> The usbhid-dump command, the one you originally linked to, gives the >> error: >> >> invalid option -- 'm' > > > Most distributions have older version of usbhid-dump. You could download > newer version at http://sf.net/apps/mediawiki/digimend/?title=Usbhid-dump > or you could use the older one by finding out your tablet bus number and > device address using lsusb and then supplying it to usbhid-dump as the > arguments. > > Sincerely, > Nick Thanks, I've compiled the newer version. Attaching the result of pressing the pen's buttons. Eduardo |
|
From: Eduardo H. S. <hob...@gm...> - 2012-05-16 00:22:46
|
Hi Nikolai, Did I do the dump correctly, does it have the information you were asking? Eduardo 2012/5/9 Eduardo H. Silva <hob...@gm...>: > 2012/5/7 Nikolai Kondrashov <sp...@gm...>: >> Hi Eduardo, >> >> >> On 05/06/2012 10:52 PM, Eduardo H. Silva wrote: >>> >>> I'm sorry for the late reply, I delayed to the following day to do >>> what you asked, but then forgot. >>> >>> The usbhid-dump command, the one you originally linked to, gives the >>> error: >>> >>> invalid option -- 'm' >> >> >> Most distributions have older version of usbhid-dump. You could download >> newer version at http://sf.net/apps/mediawiki/digimend/?title=Usbhid-dump >> or you could use the older one by finding out your tablet bus number and >> device address using lsusb and then supplying it to usbhid-dump as the >> arguments. >> >> Sincerely, >> Nick > > Thanks, I've compiled the newer version. Attaching the result of > pressing the pen's buttons. > > Eduardo |
|
From: Nikolai K. <sp...@gm...> - 2012-05-16 08:30:30
|
Hi Eduardo, On 05/16/2012 03:22 AM, Eduardo H. Silva wrote: > Did I do the dump correctly, does it have the information you were asking? Yes, thank you. Sorry for the delay - I was having a flu and didn't do much. The dump confirms my guess. I can make a patch for your kernel that fixes this problem. Do you still use version 3.3.2? Will you be able to build a patched kernel package yourself? Sincerely, Nick |
|
From: Eduardo H. S. <hob...@gm...> - 2012-05-16 09:31:54
|
2012/5/16 Nikolai Kondrashov <sp...@gm...>: > Hi Eduardo, > > > On 05/16/2012 03:22 AM, Eduardo H. Silva wrote: >> >> Did I do the dump correctly, does it have the information you were asking? > > > Yes, thank you. Sorry for the delay - I was having a flu and didn't do much. > > The dump confirms my guess. I can make a patch for your kernel that fixes > this problem. Do you still use version 3.3.2? Will you be able to build a > patched kernel package yourself? I'm in Fedora 17, which currently is at 3.3.4 . I have compiled kernels a long time ago, so I may be able to figure out (with a lot of searching) how to apply the patch :) Eduardo |
Thanks for helping keep SourceForge clean.
X