On Sun, Jan 1, 2012 at 3:59 AM, Mike Rolland <none...@gmail.com> wrote: > next news: > I change "pen" to "stylus" in xorg.conf.d > I got confusing movement on the screen yesterday. Today, nothing >
When it was moving, the confusing part could have been related to your options; especially those BottomX/Y listed below. Not sure why its not doing anything today. Can you remove options and resend the same Xlog output and show what it auto-detected to use? It doesn't print much information beyond that line with maxX/Y you listed below. > xorg.log : > > [ 1932.785] (II) config/udev: Adding input device ISD-V4 Pen > (/dev/input/event14) > [ 1932.785] (**) ISD-V4 Pen: Applying InputClass "evdev tablet catchall" > [ 1932.785] (**) ISD-V4 Pen: Applying InputClass "Wacom class" > [ 1932.785] (II) LoadModule: "wacom" > [ 1932.785] (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so > [ 1932.786] (II) Module wacom: vendor="X.Org Foundation" > [ 1932.786] compiled for 1.10.1, module version = 0.12.0 > [ 1932.786] Module class: X.Org XInput Driver > [ 1932.786] ABI class: X.Org XInput driver, version 12.2 > [ 1932.786] (II) Using input driver 'wacom' for 'ISD-V4 Pen' > [ 1932.786] (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so > [ 1932.786] (**) ISD-V4 Pen: always reports core events > [ 1932.786] (**) Option "Device" "/dev/input/event14" > [ 1932.786] (**) Option "Type" "stylus" > [ 1932.786] (**) Option "Mode" "Absolute" > [ 1932.786] (**) Option "Tilt" "on" > [ 1932.786] (**) Option "PressCurve" "0,25,75,100" > [ 1932.786] (**) Option "TopX" "0" > [ 1932.786] (**) Option "TopY" "0" > [ 1932.786] (**) Option "BottomX" "10000" > [ 1932.786] (**) Option "BottomY" "6250" > [ 1932.786] (**) Option "Threshold" "5" > [ 1932.786] (**) Option "Button1" "1" > [ 1932.786] (**) Option "Button2" "3" > [ 1932.786] (**) Option "Button3" "2" > [ 1932.786] (--) ISD-V4 Pen: Wacom USB Intuos4 tablet maxX=12800 maxY=8000 > maxZ=255 resX=100000 resY=100000 tilt=enabled > [ 1932.821] (**) Option "config_info" > "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input16/event14" > [ 1932.821] (II) XINPUT: Adding extended input device "ISD-V4 Pen" (type: > STYLUS) > [ 1932.821] (**) ISD-V4 Pen: (accel) keeping acceleration scheme 1 > [ 1932.821] (**) ISD-V4 Pen: (accel) acceleration profile 0 > [ 1932.821] (**) ISD-V4 Pen: (accel) acceleration factor: 2.000 > [ 1932.821] (**) ISD-V4 Pen: (accel) acceleration threshold: 4 > [ 1932.821] (II) config/udev: Adding input device ISD-V4 Pen > (/dev/input/mouse1) > [ 1932.821] (II) No input driver/identifier specified (ignoring) > > evtest : > > > Input driver version is 1.0.1 > Input device ID: bus 0x3 vendor 0xb05 product 0x179f version 0x129 > Input device name: "ISD-V4 Pen" > > Supported events: > Event type 0 (Sync) > Event type 1 (Key) > Event code 320 (ToolPen) > Event code 321 (ToolRubber) > Event code 330 (Touch) > Event code 331 (Stylus) > Event code 332 (Stylus2) > > Event type 3 (Absolute) > Event code 0 (X) > Value 0 > Min 0 > Max 12800 > Fuzz 4 > > Event code 1 (Y) > Value 0 > Min 0 > Max 8000 > Fuzz 4 > > Event code 24 (Pressure) > Value 0 > Min 0 > Max 255 > Testing ... (interrupt to exit) > When you do this evtest, can you generate events? This will prove if wacom kernel driver is able to correctly talk to your device. Try putting the pen on the screen and see if anything is printed. Note: X will grab the /dev/input/eventX device. When device is grabbed, evtest will print the above header information but no events will be generated. You can make X ungrab the device by either stopping X or switching to a text console and running evtest from text console. Oh yes. Now that you've successfully got hid-core to not grab your device, can you run the following commands as root and send lsusb output again. When no drivers are grabbing a device, lsusb will decode the HID report (where it used to say NOT AVAILABLE) and we should be able to tell if this is really a Wacom ISDv4 digitizer. rmmod wacom lsusb -vvvv -d 0b05:179f hid-core is usually statically linked into kernel and no easy way I know of to get HID report in that case without recompiling. Chris ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
