next news:
I change "pen" to "stylus" in xorg.conf.d
I got confusing movement on the screen yesterday. Today, nothing
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)
xinput :
Device 'ISD-V4 Pen':
Device Enabled (121): 1
Coordinate Transformation Matrix (123): 1.000000, 0.000000, 0.000000,
0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
Device Accel Profile (247): 0
Device Accel Constant Deceleration (248): 1.000000
Device Accel Adaptive Deceleration (249): 1.000000
Device Accel Velocity Scaling (250): 10.000000
Device Node (485): "/dev/input/event14"
Wacom Tablet Area (486): 0, 0, 10000, 6250
Wacom Rotation (487): 0
Wacom Pressurecurve (488): 0, 25, 75, 100
Wacom Serial IDs (489): 6047, 0, 2, 0
Wacom Serial ID binding (490): 0
Wacom Pressure Threshold (491): 5
Wacom Sample and Suppress (492): 2, 4
Wacom Enable Touch (493): 0
Wacom Hover Click (494): 1
Wacom Enable Touch Gesture (495): 0
Wacom Touch Gesture Parameters (496): 0, 0, 250
Wacom Tool Type (497): "STYLUS" (480)
Wacom Button Actions (498): "None" (0), "None" (0), "None" (0),
"None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0),
"None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0),
"None" (0)
Device Product ID (499): 2821, 6047
Wacom Debug Levels (500): 0, 0
Le samedi 31 décembre 2011 à 10:17 -0600, Chris Bagwell a écrit :
> On Sat, Dec 31, 2011 at 2:51 AM, Mike Rolland <none...@gmail.com> wrote:
> > Ok, this evterst main display:
> > I attach full log in file.
> >
> > [root@hpm mike]# evtest /dev/input/event14
> > Input driver version is 1.0.1
> > Input device ID: bus 0x3 vendor 0xb05 product 0x179f version 0x110
> > Input device name: "ASUSTek Computer, Inc. Eee Note Digitizer"
> > Supported events:
> > Event type 0 (Sync)
> > Event type 1 (Key)
> > Event code 272 (LeftBtn)
> > Event code 273 (RightBtn)
> > Event code 274 (MiddleBtn)
> > Event code 330 (Touch)
> > Event type 2 (Relative)
> > Event code 0 (X)
> > Event code 1 (Y)
> > Event code 8 (Wheel)
>
> Yes, this is the part that shows why its not working out of the box.
> Having both relative and absolute X/Y events will confuse
> xf86-input-evdev into making your touchscreen act like a touchpad.
>
> Also, there is no PEN/STYLUS described which may or may not confuse
> xf86-input-wacom (I forget were we are at there. I tried to make it
> optional but do not remember if I was successful).
>
> This proves you'll have to get a custom kernel driver handling this
> device before it will work with xf86-input-*.
>
> Chris
>
> > Event type 3 (Absolute)
> > Event code 0 (X)
> > Value 0
> > Min 0
> > Max 16480
> > Event code 1 (Y)
> > Value 0
> > Min 0
> > Max 12410
> > Event code 24 (Pressure)
> > Value 0
> > Min 0
> > Max 255
> > Event type 4 (Misc)
> > Event code 4 (ScanCode)
> > Testing ... (interrupt to exit)
> >
> > Le vendredi 30 décembre 2011 à 16:45 -0600, Chris Bagwell a écrit :
> >
> > On Fri, Dec 30, 2011 at 2:21 PM, Mike Rolland <none...@gmail.com> wrote:
> >> Le vendredi 30 décembre 2011 à 11:37 -0600, Chris Bagwell a écrit :
> >>
> >>> * Run "dmesg | grep ASUSTek" and look for line telling if kernel
> >>> driver has been installed for this device.
> >>
> >> [root@hpm mike]# dmesg | grep ASUSTek
> >> usb 2-1.2: Manufacturer: ASUSTek Computer, Inc.
> >> input: ASUSTek Computer, Inc. Eee Note Digitizer as
> >> /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input14
> >> generic-usb 0003:0B05:179F.0002: input,hiddev0,hidraw1: USB HID v1.10
> >> Mouse
> >> [ASUSTek Computer, Inc. Eee Note Digitizer] on usb-0000:00:1d.0-1.2/input0
> >
> > OK, this is the part I want to concentrate on. That USB HID v1.10
> > Mouse part means its probably being reported to userland as a strange
> > mouse+pen combo device. Its related to the HID report for digitizer
> > declaring a mouse (required by Microsoft for tabletPC's I think even
> > if its not really used).
> >
> > To better see what kernel is doing, you'll need to install the
> > "evtest" app from your distro's repo. Run it as root and from a
> > console (not from X) or it will hide some stuff from you.
> >
> > evtest /dev/input/eventtX <--- The value for X is usually found from
> > trail and error.
> >
> > Please send what this displays. You can pipe to a file as well
> > (evtest /dev/input/eventX > log).
> >
> >>
> >>> I googled for this USB ID and got one result where it said its being
> >>> detected as a generic HID Mouse. This would not be a good thing and
> >>> all your work in xf86-input-wacom or xf86-input-evdev will be in vain
> >>> until kernel side issue is resolved.
> >>
> >> Not really sure about that.
> >> Often the problem comes only from XF86 driver, but like I told to Favux, I
> >> will have a look to wacom dev kernel libs. The first time I made my
> >> homebrew
> >> with my WALTOP tablet, I remember I change something in kernel driver.
> >> So...
> >
> > In last year, I think problem areas have moved. xf86-input-wacom and
> > xf86-input-evdev have become quite stable for new
> > digitizers/tabletPC's and touchscreens without modifications. The
> > issues are almost always in kernel now for new hardware.
> >
> > I see people go to great lengths though to hack up xf86-input-*
> > instead of fixing the real kernel side issue and try to ignore that
> > invalid mouse information.
> >
> > When we see the mouse+touchscreen issue in recent times, the cure is
> > to get the hid-multitouch driver to control the touchscreen.
> >
> > In your case, its a mouse+pen so I'm not sure what driver its supposed
> > to be routed to. If the Asus web page that Favux is to be trusted,
> > its a Wacom digitizer and so maybe it should be handled by wacom
> > driver. I have seen Wacom commonly use 0x81 as Endpoint address for
> > PEN's so thats a good sign.
> >
> > I'd try the hint given by Favux and update the file wacom_wac.c from
> > input-wacom package to understand Eee product ID's.
> >
> > 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
