Bug#367675: xserver-xorg-input-aiptek: The X driver don't work with hyperpen 1200 U
On Sat, Oct 21, 2006 at 08:51:46PM +0200, guy wrote: > Hi Drew, > > > Only two suggestions at this point. First, we've now finished the > > X11R7.1 transition in unstable. Could you confirm if the problem still > > remains after the upgrade? > > Yes. I upgrade today my debian sid and the problem still remains ... Hi Guy, Do you still experience the same problem with a recent X.org installation? If so, please send the whole output of /usr/share/bug/xserver-xorg/script 3>&1 Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367675: xserver-xorg-input-aiptek: The X driver don't work with hyperpen 1200 U
> I upgrade today my debian sid and the problem still remains ... OK, thanks for the feedback. > I've tried the 'hyperpen' driver (xserver-xorg-input-hyperpen package). > The behavior of the tablet is comparable with a mouse. Do you mean here that the behaviour is satisfactorily smooth, not erratic the way it was with the aiptek driver? That's progress then :) > The stylet cannot reach all the screen. > ... > (EE) stylusC: invalid PMin value (should be > 2).Using default. > (EE) stylusC: invalid PMax value (should be > 3).Using default. The hyperpen options appear [1] to be: Device DebugLevel Mode Cursor XSize YSize PMin PMax XOffset YOffset InvX InvY BaudRate Except for PMin and PMax, it's probably safe to assume the other options are the same as for the aiptek driver, which you can check with the aiptek man page. PMin is the pressure threshold, PMax is maximum pressure read from tablet, so they probably don't explain why you don't reach the whole screen. Unfortunately I do not know what the correct values must be. Maybe the default values are OK? Debug level 6 will give more log data about it. Perhaps adjusting XSize,YSize and/or XOffset,YOffset, setting the dimensions of the active area, will give you the whole screen? You might be able to debug it by setting debug level 2 and looking for "reading max coordinates". If you feel like experimenting in a different direction, you could see if the evdev driver in mouse mode provides any access to the device. I'm not saying it will help, it's just another idea to play with. Drew [1] see xf86HypInit() in xf86HyperPen.c, http://necrotic.deadbeast.net/svn/xorg-x11/trunk/driver/xserver-xorg-input-hyperpen/src/xf86HyperPen.c -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367675: xserver-xorg-input-aiptek: The X driver don't work with hyperpen 1200 U
[forgot to CC:guy. Someone should really fix the BTS interface so email automatically forward to the submitter unless explicitly specified not to] > I upgrade today my debian sid and the problem still remains ... OK, thanks for the feedback. > I've tried the 'hyperpen' driver (xserver-xorg-input-hyperpen package). > The behavior of the tablet is comparable with a mouse. Do you mean here that the behaviour is satisfactorily smooth, not erratic the way it was with the aiptek driver? That's progress then :) > The stylet cannot reach all the screen. > ... > (EE) stylusC: invalid PMin value (should be > 2).Using default. > (EE) stylusC: invalid PMax value (should be > 3).Using default. The hyperpen options appear [1] to be: Device DebugLevel Mode Cursor XSize YSize PMin PMax XOffset YOffset InvX InvY BaudRate Except for PMin and PMax, it's probably safe to assume the other options are the same as for the aiptek driver, which you can check with the aiptek man page. PMin is the pressure threshold, PMax is maximum pressure read from tablet, so they probably don't explain why you don't reach the whole screen. Unfortunately I do not know what the correct values must be. Maybe the default values are OK? Debug level 6 will give more log data about it. Perhaps adjusting XSize,YSize and/or XOffset,YOffset, setting the dimensions of the active area, will give you the whole screen? You might be able to debug it by setting debug level 2 and looking for "reading max coordinates". If you feel like experimenting in a different direction, you could see if the evdev driver in mouse mode provides any access to the device. I'm not saying it will help, it's just another idea to play with. Drew [1] see xf86HypInit() in xf86HyperPen.c, http://necrotic.deadbeast.net/svn/xorg-x11/trunk/driver/xserver-xorg-input-hyperpen/src/xf86HyperPen.c -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367675: xserver-xorg-input-aiptek: The X driver don't work with hyperpen 1200 U
Hi Drew,
> Only two suggestions at this point. First, we've now finished the
> X11R7.1 transition in unstable. Could you confirm if the problem still
> remains after the upgrade?
Yes. I upgrade today my debian sid and the problem still remains ...
> Second, have you tried using xserver-xorg-input-hyperpen instead? It's
> only supposed to support Hyperpen 3000 - 6000, but it would be useful
> to confirm or refute if it also supports the 1200 model.
I've tried the 'hyperpen' driver (xserver-xorg-input-hyperpen package).
The behavior of the tablet is comparable with a mouse.
The stylet cannot reach all the screen.
I did not find any documentation to configure the tablet (xorg options).
And it is not recognized with "The GIMP".
This is what i get in Xorg.0.log :
...
(II) LoadModule: "hyperpen"
(II) Loading /usr/lib/xorg/modules/input/hyperpen_drv.so
(II) Module hyperpen: vendor="X.Org Foundation"
compiled for 7.1.1, module version = 1.1.0
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 0.6
...
(**) stylusC: always reports core events
(**) stylusC serial device is /dev/input/event5
(**) Option "DebugLevel" "100"
(**) stylusC: debug level set to 100
(**) stylusC is in absolute mode
(**) stylusC is in cursor-mode cursor
(EE) stylusC: invalid PMin value (should be > 2).Using default.
(EE) stylusC: invalid PMax value (should be > 3).Using default.
...
(II) XINPUT: Adding extended input device "stylusC" (type: HyperPen Tablet)
...
xf86HypProc pHyp=0x8216030 what=INIT
xf86HypControlProc
opening /dev/input/event5
(**) Option "Device" "/dev/input/event5"
/dev/input/event5 opened as fd 10
initializing HyperPen tablet
reading model
Timeout while reading HyperPen tablet. No tablet connected ???
END xf86HypProc Success what=0 dev=0x8216030 priv=0x82149a8
xkb_keycodes { include "xfree86+aliases(azerty)" };
xkb_types{ include "complete" };
xkb_compatibility{ include "complete" };
xkb_symbols { include "pc(pc105)+fr(latin9)" };
xkb_geometry { include "pc(pc105)" };
xf86HypProc pHyp=0x8216030 what=ON
opening /dev/input/event5
/dev/input/event5 opened as fd 10
initializing HyperPen tablet
reading model
Timeout while reading HyperPen tablet. No tablet connected ???
(II) Configured Mouse: ps2EnableDataReporting: succeeded
The 7 last lines repeat many times.
Thank you.
Guy
PS: 'lsusb -v'
Bus 002 Device 002: ID 08ca:0010 Aiptek International, Inc. Tablet
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x08ca Aiptek International, Inc.
idProduct 0x0010 Tablet
bcdDevice1.05
iManufacturer 1 AIPTEK International Inc.
iProduct3 USB Tablet Series Version 1.05
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 26mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType33
bcdHID 1.10
bCountryCode 30 Taiwan
bNumDescriptors 1
bDescriptorType34 Report
wDescriptorLength 462
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes3
Transfer TypeInterrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Device Status: 0x
(Bus Powered)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367675: xserver-xorg-input-aiptek: The X driver don't work with hyperpen 1200 U
Hi Guy, > When i launch gaiptek (manualy compiled), i get this message : > "There is no XServer Input Driver associated with the tablet" > > However the driver is here : > $ dpkg -L xserver-xorg-input-aiptek | grep so$ > /usr/lib/xorg/modules/input/aiptek_drv.so Only two suggestions at this point. First, we've now finished the X11R7.1 transition in unstable. Could you confirm if the problem still remains after the upgrade? Second, have you tried using xserver-xorg-input-hyperpen instead? It's only supposed to support Hyperpen 3000 - 6000, but it would be useful to confirm or refute if it also supports the 1200 model. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367675: xserver-xorg-input-aiptek: The X driver don't work with hyperpen 1200 U
Drew wrote : > Guy wrote: > > When i launch gaiptek (manualy compiled), i get this message : > > "There is no XServer Input Driver associated with the tablet" > > Hello Guy. The Xorg log is located at /var/log/Xorg.0.log. Look inside > it for aiptek, it will probably contain clues to what's going wrong. > > Drew Hello Drew, sorry Drew for the very late answer, i was on holidays ... When i launch gaiptek, i get the previous message and these 3 lines at the end of /var/log/Xorg.0.log : xf86AiptekControlProc xf86AiptekControlProc ProcXCloseDevice to close or not ? Here, some extracts from /var/log/Xorg.0.log, all seems correct, isnt'it ? Thank you. Guy X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.17-1-686 i686 Current Operating System: Linux elin 2.6.16-2-k7 #1 Fri Aug 18 19:48:42 UTC 2006 i686 Build Date: 16 March 2006 ... (II) LoadModule: "aiptek" (II) Loading /usr/lib/xorg/modules/input/aiptek_drv.so (II) Module aiptek: vendor="X.Org Foundation" compiled for 7.0.0, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.5 ... (II) xf86AiptekInit(): begins (**) xf86AiptekConfig: device not shared btw stylusC and stylusC (**) xf86AiptekConfig: device not shared btw stylusC and NVIDIA Event Handler (**) Option "AlwaysCore" (**) stylusC: always reports core events (**) Option "Device" "/dev/input/event4" (==) HID Device name: "Aiptek" (==) HID Driver Version: 1.0.0 (==) HID Driver knows it has 1 devices configured (==) HID Driver is using 10 as the fd >From ioctl() xCapacity=5999 >From ioctl() yCapacity=4499 (**) stylusC device is /dev/input/event4 (**) Option "DebugLevel" "10" (**) Debug level set to 10 (**) stylusC is in absolute mode (**) Option "USB" "on" (**) stylusC: reading USB link (**) Option "KeepShape" "on" (**) stylusC: keeps shape (**) Option "ZMax" "512" (**) stylusC: ZMax/MaxZ = 512 (**) Option "ZMin" "0" (**) stylusC: ZMin/MinZ = 0 (**) Option "BaudRate" "9600" (**) stylusC: BaudRate 9600 (**) stylusC: xf86AiptekInit() finished (**) Option "CoreKeyboard" (**) Generic Keyboard: Core Keyboard (**) Option "Protocol" "standard" (**) Generic Keyboard: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Generic Keyboard: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Generic Keyboard: XkbModel: "pc105" (**) Option "XkbLayout" "fr" (**) Generic Keyboard: XkbLayout: "fr" (**) Option "XkbVariant" "latin9" (**) Generic Keyboard: XkbVariant: "latin9" (**) Option "CustomKeycodes" "off" (**) Generic Keyboard: CustomKeycodes disabled (**) Option "Protocol" "ExplorerPS/2" (**) Configured Mouse: Device: "/dev/input/mice" (**) Configured Mouse: Protocol: "ExplorerPS/2" (**) Option "CorePointer" (**) Configured Mouse: Core Pointer (**) Option "Device" "/dev/input/mice" (**) Option "Emulate3Buttons" "true" (**) Configured Mouse: Emulate3Buttons, Emulate3Timeout: 50 (**) Configured Mouse: ZAxisMapping: buttons 4, 5, 6 and 7 (**) Configured Mouse: Buttons: 11 (II) XINPUT: Adding extended input device "Configured Mouse" (type: MOUSE) (II) XINPUT: Adding extended input device "Generic Keyboard" (type: KEYBOARD) (II) XINPUT: Adding extended input device "stylusC" (type: Stylus) (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other) xf86AiptekProc() type=stylus flags=193 request=0 xf86AiptekProc request=INIT xf86AiptekControlProc In xf86AiptekOpenDevice, with fd=-1 (**) xTop invalid; adjusted to 0 (**) yTop invalid; adjusted to 0 (**) xBottom invalid; adjusted to 5999 (**) yBottom invalid; adjusted to 4499 (**) ScreenNo invalid; adjusted to 0 Screen 0: screenRatio = 1.33, tabletRatio = 1.33 Screen 0: 'X' Gap of 0 computed xf86AiptekProc Success request=0 xf86AiptekProc() type=stylus flags=193 request=1 xf86AiptekProc request=ON In xf86AiptekOpenDevice, with fd=-1 (==) HID Device name: "Aiptek" (==) HID Driver Version: 1.0.0 (==) HID Driver knows it has 1 devices configured (==) HID Driver is using 10 as the fd >From ioctl() xCapacity=5999 >From ioctl() yCapacity=4499 Screen 0: screenRatio = 1.33, tabletRatio = 1.33 Screen 0: 'X' Gap of 0 computed Able to open aiptek device xf86AiptekProc Success request=1 (II) Configured Mouse: ps2EnableDataReporting: succeeded Could not init font path element /usr/share/fonts/X11/TTF/, removing from list! Could not init font path element /usr/share/fonts/X11/OTF, removing from list! Could not init font path element /usr/share/fonts/X11/CID/, removing from list! AUDIT: Sat Sep 9 09:59:04 2006: 6763 X: client 2 rejected from local host AUDIT: Sat Sep 9 09:59:04 2006: 6763 X: client 4 rejected from local host AUDIT: Sat Sep 9 09:59:04 2006: 6763 X: client 3 rejected from local host AUDIT: Sat Sep 9 09:59:04 2006: 6763 X: client 2 rejected from local host ProcXCloseDevice to close or not ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] wit
Bug#367675: xserver-xorg-input-aiptek: The X driver don't work with hyperpen 1200 U
Guy wrote: > When i launch gaiptek (manualy compiled), i get this message : > "There is no XServer Input Driver associated with the tablet" Hello Guy. The Xorg log is located at /var/log/Xorg.0.log. Look inside it for aiptek, it will probably contain clues to what's going wrong. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367675: xserver-xorg-input-aiptek: The X driver don't work with hyperpen 1200 U
Package: xserver-xorg-input-aiptek Version: 1:1.0.0.5-2 Severity: normal Hi, With : InputDevice"stylusC""AlwaysCore" in Section "ServerLayout" and : Section "InputDevice" Identifier "stylusC" Driver "aiptek" Option "Device" "/dev/input/event4" Option "Type" "stylus" Option "Mode" "absolute" Option "Cursor" "stylus" Option "USB" "on" Option "KeepShape" "on" Option "debuglevel" "10" Option "zMin" "0" Option "zMax" "512" Option "PressCurve" "0,5,95,100" EndSection when i change to console (CTRL-ALT-F1 for example) X restart ! When i launch gaiptek (manualy compiled), i get this message : "There is no XServer Input Driver associated with the tablet" However the driver is here : $ dpkg -L xserver-xorg-input-aiptek | grep so$ /usr/lib/xorg/modules/input/aiptek_drv.so when i move the stylus over the tablet, the mouse cursor move but it is very eratic, i can't clic. With gimp i can't configure the pressure, i can't clic ... I test varius options in Section "InputDevice" with no effects. I can give you more details if there is needs ... Thanks, Guy -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-k7 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg-input-aiptek depends on: ii libc6 2.3.6-7GNU C Library: Shared libraries ii xserver-xorg-core 1:1.0.2-8 X.Org X server -- core server xserver-xorg-input-aiptek recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
