|
From: Patkos C. <pat...@gm...> - 2010-07-29 16:07:37
|
On Mon, 26 Jul 2010 22:56:13 +0300, Ping Cheng <pin...@gm...> wrote: > On Mon, Jul 26, 2010 at 11:36 AM, Patkos Csaba <pat...@gm...> > wrote: >> >> Hello everybody, >> >> I am new here and I hope you can help set up this tablet. I am a long >> time >> Linux user, so I am familiar with the ins and outs of Linux, especially >> Mandriva. >> >> What's give: >> - Broadcom based blue-tooth adapter, working properly. >> - Wacom Graphire CTE-630BT tablet (here is the problem) >> - Mandriva 2010.1 64 bits >> >> Before I posted here I tried the following: >> - using the included packages in Mandriva (xf86-input-wacom, version >> 10.7) >> - compile the 10.7 version as explained in the linuxwacom official >> documentation and/or wiki page >> - compile the latest (10.8) driver also as explained in the >> documentation - >> I also updated the X.org macros to 10.8 in order to be able to compile >> it. >> >> What I am getting: >> - if I use any of the above mentioned solutions, all I can get is click >> (if >> I touch the pad with the pan), right click and middle click. >> >> What I can not get in any situation: >> - cursor movement >> >> Where am I know: >> - my last try was to install the latest xf86-input-wacom, released on >> July >> the 26th 2010, also taken with git clone >> - I compiled it with ./autogen.sh --libdir=/usr/lib64 and the >> wacom_drv.so >> was installed in the appropriate X.org folder >> - when configured with HAL and I start X I can see these relevant >> information in the Xorg.0.log: >> >> [csaba@localhost ~]$ grep -A 30 wacom /var/log/Xorg.0.log >> (II) LoadModule: "wacom" >> (II) Loading /usr/lib64/xorg/modules/input/wacom_drv.so >> (II) Module wacom: vendor="X.Org Foundation" >> compiled for 1.7.7, module version = 0.10.8 >> Module class: X.Org XInput Driver >> ABI class: X.Org XInput driver, version 7.0 >> (**) Option "Device" "/dev/input/event5" >> (II) WACOM Pen Tablet: type not specified, assuming 'stylus'. >> (II) WACOM Pen Tablet: other types will be automatically added. >> (**) WACOM Pen Tablet stylus: always reports core events >> (--) WACOM Pen Tablet stylus: using pressure threshold of 27 for button >> 1 >> (--) WACOM Pen Tablet stylus: Wacom USB Graphire4 tablet maxX=16704 >> maxY=12064 maxZ=511 resX=2032 resY=2032 tilt=disabled >> (II) WACOM Pen Tablet stylus: hotplugging dependent devices. >> (**) Option "Device" "/dev/input/event5" >> (**) WACOM Pen Tablet eraser: always reports core events >> (--) WACOM Pen Tablet eraser: Wacom USB Graphire4 tablet maxX=16704 >> maxY=12064 maxZ=511 resX=2032 resY=2032 tilt=disabled >> (II) XINPUT: Adding extended input device "WACOM Pen Tablet eraser" >> (type: >> ERASER) >> (--) WACOM Pen Tablet eraser: top X=0 top Y=0 bottom X=16704 bottom >> Y=12064 >> resol X=2032 resol Y=2032 >> (**) Option "Device" "/dev/input/event5" >> (**) WACOM Pen Tablet cursor: always reports core events >> (--) WACOM Pen Tablet cursor: Wacom USB Graphire4 tablet maxX=16704 >> maxY=12064 maxZ=511 resX=2032 resY=2032 tilt=disabled >> (II) XINPUT: Adding extended input device "WACOM Pen Tablet cursor" >> (type: >> CURSOR) >> (--) WACOM Pen Tablet cursor: top X=0 top Y=0 bottom X=16704 bottom >> Y=12064 >> resol X=2032 resol Y=2032 >> (**) Option "Device" "/dev/input/event5" >> (**) WACOM Pen Tablet pad: always reports core events >> (--) WACOM Pen Tablet pad: Wacom USB Graphire4 tablet maxX=16704 >> maxY=12064 >> maxZ=511 resX=2032 resY=2032 tilt=disabled >> (II) XINPUT: Adding extended input device "WACOM Pen Tablet pad" (type: >> PAD) >> (--) WACOM Pen Tablet pad: top X=0 top Y=0 bottom X=16704 bottom Y=12064 >> resol X=2032 resol Y=2032 >> (II) WACOM Pen Tablet stylus: hotplugging completed. >> (II) XINPUT: Adding extended input device "WACOM Pen Tablet stylus" >> (type: >> STYLUS) >> (--) WACOM Pen Tablet stylus: top X=0 top Y=0 bottom X=16704 bottom >> Y=12064 >> resol X=2032 resol Y=2032 >> >> - these lines are followed by a lot of lines repeating these: >> >> (EE) WACOM Pen Tablet stylus: rel event recv'd (0)! >> (EE) WACOM Pen Tablet stylus: rel event recv'd (1)! >> >> - if I configure Xorg.conf by hand, I can see a similar output. The only >> difference is, that with xorg.conf configured by hand I can see code >> scrolling when I touch or move the pen on the tablet with "xxd >> /dev/input/event5" >> >> >> - here is the output of lshal for the bluetooth device AND the Wacom >> tablet: >> >> udi = >> '/org/freedesktop/Hal/devices/usb_device_b05_1715_noserial_if0_bluetooth_hci_0' >> bluetooth_hci.address = 0 (0x0) (uint64) >> bluetooth_hci.originating_device = >> '/org/freedesktop/Hal/devices/usb_device_b05_1715_noserial_if0' (string) >> info.capabilities = {'bluetooth_hci'} (string list) >> info.category = 'bluetooth_hci' (string) >> info.parent = >> '/org/freedesktop/Hal/devices/usb_device_b05_1715_noserial_if0' (string) >> info.product = 'Bluetooth Host Controller Interface' (string) >> info.subsystem = 'bluetooth' (string) >> info.udi = >> '/org/freedesktop/Hal/devices/usb_device_b05_1715_noserial_if0_bluetooth_hci_0' >> (string) >> linux.hotplug_type = 2 (0x2) (int) >> linux.subsystem = 'bluetooth' (string) >> linux.sysfs_path = >> '/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/bluetooth/hci0' >> (string) >> >> udi = '/org/freedesktop/Hal/devices/bluetooth_acl_13c2033cc7' >> bluetooth_acl.address = 84859370695 (0x13c2033cc7) (uint64) >> bluetooth_acl.originating_device = >> '/org/freedesktop/Hal/devices/usb_device_b05_1715_noserial_if0_bluetooth_hci_0' >> (string) >> info.capabilities = {'bluetooth_acl'} (string list) >> info.category = 'bluetooth_acl' (string) >> info.parent = >> '/org/freedesktop/Hal/devices/usb_device_b05_1715_noserial_if0_bluetooth_hci_0' >> (string) >> info.product = 'Bluetooth Asynchronous Connection-oriented Link' >> (string) >> info.subsystem = 'bluetooth' (string) >> info.udi = '/org/freedesktop/Hal/devices/bluetooth_acl_13c2033cc7' >> (string) >> linux.hotplug_type = 2 (0x2) (int) >> linux.subsystem = 'bluetooth' (string) >> linux.sysfs_path = >> '/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11' >> (string) >> >> udi = >> '/org/freedesktop/Hal/devices/bluetooth_acl_13c2033cc7_logicaldev_input' >> info.capabilities = {'input', 'input.mouse', 'input.tablet'} (string >> list) >> info.category = 'input' (string) >> info.parent = '/org/freedesktop/Hal/devices/bluetooth_acl_13c2033cc7' >> (string) >> info.product = 'WACOM Pen Tablet' (string) >> info.subsystem = 'input' (string) >> info.udi = >> '/org/freedesktop/Hal/devices/bluetooth_acl_13c2033cc7_logicaldev_input' >> (string) >> input.device = '/dev/input/event5' (string) >> input.originating_device = >> '/org/freedesktop/Hal/devices/bluetooth_acl_13c2033cc7' (string) >> input.product = 'WACOM Pen Tablet' (string) >> input.x11_driver = 'wacom' (string) >> linux.device_file = '/dev/input/event5' (string) >> linux.hotplug_type = 2 (0x2) (int) >> linux.subsystem = 'input' (string) >> linux.sysfs_path = >> '/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/bluetooth/hci0/hci0:11/input7/event5' >> (string) >> >> udi = >> '/org/freedesktop/Hal/devices/usb_device_b05_1715_noserial_if0_bluetooth_hci_0_rfkill_hci0_bluetooth' >> info.addons.singleton = {'hald-addon-rfkill-killswitch'} (string list) >> info.capabilities = {'killswitch'} (string list) >> info.category = 'killswitch' (string) >> info.interfaces = {'org.freedesktop.Hal.Device.KillSwitch'} (string >> list) >> info.parent = >> '/org/freedesktop/Hal/devices/usb_device_b05_1715_noserial_if0_bluetooth_hci_0' >> (string) >> info.product = 'hci0 bluetooth Killswitch' (string) >> info.subsystem = 'rfkill' (string) >> info.udi = >> '/org/freedesktop/Hal/devices/usb_device_b05_1715_noserial_if0_bluetooth_hci_0_rfkill_hci0_bluetooth' >> (string) >> killswitch.access_method = 'rfkill' (string) >> killswitch.name = 'hci0' (string) >> killswitch.state = 1 (0x1) (int) >> killswitch.type = 'bluetooth' (string) >> linux.hotplug_type = 2 (0x2) (int) >> linux.subsystem = 'rfkill' (string) >> >> - here is what xinput thinks I have (also looks good): >> >> [root@localhost Wacom]# xinput --list >> ⎡ Virtual core pointer id=2 [master pointer (3)] >> ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] >> ⎜ ↳ Microsoft Microsoft Wireless Optical Desktop® 2.10 id=6 [slave >> pointer >> (2)] >> ⎜ ↳ Macintosh mouse button emulation id=10 [slave pointer (2)] >> ⎜ ↳ WACOM Pen Tablet eraser id=11 [slave pointer (2)] >> ⎜ ↳ WACOM Pen Tablet cursor id=12 [slave pointer (2)] >> ⎜ ↳ WACOM Pen Tablet pad id=13 [slave pointer (2)] >> ⎜ ↳ WACOM Pen Tablet stylus id=14 [slave pointer (2)] >> ⎣ Virtual core keyboard id=3 [master keyboard (2)] >> ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] >> ↳ Power Button id=7 [slave keyboard (3)] >> ↳ Power Button id=8 [slave keyboard (3)] >> ↳ Microsoft Microsoft Wireless Optical Desktop® 2.10 id=9 [slave >> keyboard >> (3)] >> >> >> To sum it up: >> - whatever I do, it seem like everything is in place > > There are two pieces of driver for Wacom USB devices: the kernel > driver, wacom.ko and the X server driver, wacom_drv.so. So far, you > have done a great job for wacom_drv.so. But you haven't even touched > the kernel driver yet. Please download linuxwaocm-0.8.8-7. After > untaring the file, please: > > --------------------- > cd linuxwacom-0.8.8-7 > ./configure --enable-wacom > su > cp src/kernel_dir_given_above/wacom.ko /lib/modules/`uname > -r`/kernel/drivers/usb/input > /sbin/rmmod wacom > /sbin/modprobe wacom > exit > ------------------------ > > Then bringing your stylus into the prox to see what happens. > > Don't forget to share your result with us. Thank you. > > Ping Thanks for the quick reply. Unfortunately it is still not working. Here is what I did: - downloaded driver 0.8.8-7 (latest stable) - ./configure... went OK, and I've got a wacom.ko file - I had to copy it in a different location, specifically in /lib/modules/2.6.33.5-desktop-2mnb/kernel/drivers/input/tablet/ than I had to gzip it. I found this out because I already had a wacom.ko.gz there, probably installed by my distribution at some point in my testing. So I renamed the old file, loaded the new one ... same thing. I even restarted the computer, still no luck. Then I thought let's try a lsmod | grep wacom And this is what I am getting: hid_wacom 3481 0 hid 81725 4 hid_wacom,hidp,usbhid,hid_microsoft Then I played around a little bit and I tried all possible combinations: [root@localhost src]# rmmod hid_wacom [root@localhost src]# lsmod | grep wacom [root@localhost src]# modprobe wacom [root@localhost src]# lsmod | grep wacom wacom 32589 0 usbcore 210260 11 wacom,snd_usb_audio,snd_usb_lib,btusb,gspca_zc3xx,gspca_main,uhci_hcd,ohci_hcd,ehci_hcd,usbhid [root@localhost src]# lsmod | grep wacom hid_wacom 3481 0 wacom 32589 0 usbcore 210260 11 wacom,snd_usb_audio,snd_usb_lib,btusb,gspca_zc3xx,gspca_main,uhci_hcd,ohci_hcd,ehci_hcd,usbhid hid 81725 4 hid_wacom,hidp,usbhid,hid_microsoft [root@localhost src]# rmmod hid_wacom [root@localhost src]# lsmod | grep wacom wacom 32589 0 usbcore 210260 11 wacom,snd_usb_audio,snd_usb_lib,btusb,gspca_zc3xx,gspca_main,uhci_hcd,ohci_hcd,ehci_hcd,usbhid If I remove the hid_wacom module, I can't even get "click" to work. It's all dead, even if the wacom module is loaded. -- ing. Patkos Csaba Tel: 0745056549 E-Mail: pat...@ma... pat...@gm... -------------------------------------- "Our deepest fear is not that we are inadequate. Our deepest fear is that we are powerful beyond measure. [...] We ask ourselves, Who am I to be brilliant, gorgeous, talented and fabulous? Actually, who are you not to be?" - Marianne Williamson |