1 Attachment(s)
Re: New Wacom Bamboo not working
I think the wacom pen (no touch) still has 2 /dev/input/event's for some reason, if you followed the linuxwacom howto for installing udev rules, it sems to always map the second event to wacom-touct. (I may be totally wrong, but that is a possibility)
http://linuxwacom.sourceforge.net/in...howto/newwacom
I have also attached my xorg.conf file
Re: New Wacom Bamboo not working
Hi TheguywholikesLINUX, Ayuthia, _Stefan_3_, and kgingeri,
Do we need to add a symlink to the "40-xserver-xorg-input-wacom.rules" in "/lib/udev/rules.d/"? Something like?:
Code:
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00d1", SYMLINK="input/tablet-wacom-bamboo-pen_touch-$env{WACOM_TYPE}"
The script there does try to grab back the device if another module tries to bind to it.
And it would be similar for _Stefan_3_ and kgingeri but without the "$env{WACOM_TYPE}".
Edit: Left space which I think violates format. Put a '-' in.
Re: New Wacom Bamboo not working
So If I use this it should try to set wacom as the driver that is in control of the wacom tablet?
Re: New Wacom Bamboo not working
Hi TheguywholikesLINUX,
Right the script does that, you'd add it to the bottom of the table:
Code:
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c5", SYMLINK+="input/tablet-cintiq20wsx"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c6", SYMLINK+="input/tablet-cintiq12wx"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c7", SYMLINK+="input/tablet-dtu1931"
# Convenience links for the common case of a single tablet. We could do just this:
#ATTRS{idVendor}=="056a", SYMLINK+="input/wacom-$env{WACOM_TYPE}"
like
Code:
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c5", SYMLINK+="input/tablet-cintiq20wsx"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c6", SYMLINK+="input/tablet-cintiq12wx"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00c7", SYMLINK+="input/tablet-dtu1931"
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00d1", SYMLINK="input/tablet-wacom-bamboo-pen_touch-$env{WACOM_TYPE}"
# Convenience links for the common case of a single tablet. We could do just this:
#ATTRS{idVendor}=="056a", SYMLINK+="input/wacom-$env{WACOM_TYPE}"
I'm just not sure of the formatting and how necessary it is. I know HAL does copy all the udev rules to itself. But we need someone like Ayuthia or kgingeri to tell us if this is needed and if the format is right. Unless you want to experiment with it, which is what I do/would do. But then I'm crazy reckless!
Re: New Wacom Bamboo not working
Quote:
Originally Posted by
Favux
Hi TheguywholikesLINUX, Ayuthia, _Stefan_3_, and kgingeri,
Do we need to add a symlink to the "40-xserver-xorg-input-wacom.rules" in "/lib/udev/rules.d/"? Something like?:
Code:
ATTRS{idVendor}=="056a", ATTRS{idProduct}=="00d1", SYMLINK="input/tablet-wacom bamboo-pen_touch-$env{WACOM_TYPE}"
The script there does try to grab back the device if another module tries to bind to it.
And it would be similar for _Stefan_3_ and kgingeri but without the "$env{WACOM_TYPE}".
I am not for sure. However, if we define the .fdi correctly, the evdev driver should not end up grabbing it. It should only be picked up by evdev if xorg does not find any definitions for the device.
TheguywholikesLINUX, you don't have anything defined in xorg.conf so xorg should be looking for the information from the .fdi file. The xorg.0.log does not even seem to be accepting/rejecting anything from the .fdi file which leads me to believe that there is something in the .fdi file that it does not like.
I am almost thinking of starting the .fdi file with something simple like just getting the stylus defined:
Code:
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="input.originating_device" contains="if0">
<match key="info.product" contains="Wacom">
<merge key="input.x11_driver" type="string">wacom</merge>
<merge key="input.x11_options.Type" type="string">stylus</merge>
<merge key="info.product" type="string">stylus</merge>
</match>
</match>
</device>
</deviceinfo>
Then restart hal:
Code:
sudo /etc/init.d/hal restart
and check lshal again to see if the changes were made. In theory, the change should look something like:
Code:
udi = '/org/freedesktop/Hal/devices/usb_device_56a_d1_noserial_if0_logicaldev_input'
info.capabilities = {'input', 'input.tablet'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/usb_device_56a_d1_noserial_if0' (string)
info.product = 'stylus' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedesktop/Hal/devices/usb_device_56a_d1_noserial_if0_logicaldev_input' (string)
input.device = '/dev/input/event4' (string)
input.originating_device = '/org/freedesktop/Hal/devices/usb_device_56a_d1_noserial_if0' (string)
input.product = 'Wacom Bamboo Pen & Touch' (string)
input.x11_driver = 'wacom' (string)
linux.device_file = '/dev/input/event4' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:0b.0/usb2/2-2/2-2:1.0/input/input4/event4' (string)
in lshal.
1 Attachment(s)
Re: New Wacom Bamboo not working
Here is the output of lshal.
Re: New Wacom Bamboo not working
Code:
udi = '/org/freedesktop/Hal/devices/usb_device_56a_d1_noserial_if0_logicaldev_input'
info.capabilities = {'input', 'input.tablet'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedesktop/Hal/devices/usb_device_56a_d1_noserial_if0' (string)
info.product = 'stylus' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedesktop/Hal/devices/usb_device_56a_d1_noserial_if0_logicaldev_input' (string)
input.device = '/dev/input/event4' (string)
input.originating_device = '/org/freedesktop/Hal/devices/usb_device_56a_d1_noserial_if0' (string)
input.product = 'Wacom Bamboo Pen & Touch' (string)
input.x11_driver = 'wacom' (string)
input.x11_options.Type = 'stylus' (string)
linux.device_file = '/dev/input/event4' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:0b.0/usb2/2-2/2-2:1.0/input/input10/event4' (string)
It looks like the information has now changed. Have you tried restarting to see if the changes make a difference? If so, please post the results of /var/log/Xorg.0.log to see what comes up.
1 Attachment(s)
Re: New Wacom Bamboo not working
Hey all, these mod'd files are from camdenb (as I'll call him until he decides to join) on the wacom-linux mailing list.
He has more edits than I did. But better parameters.
Also, I don't beleive I mod'd the fdi file at all. I do get 3 devices 'wacom', 'wacom-touch' (even tho my tablet doesn't support it) and the 'tablet-wacom...' one.
- ok see if I can attach the archive of camdenb's files... ;)
(BTW, he has a CTL-460)
Man, it's hard to do any work with all this going on!! ;p
Re: New Wacom Bamboo not working
Re: New Wacom Bamboo not working
Quote:
Originally Posted by
TheguywholikesLINUX
Still no luck :(
Can you provide the results of /var/log/Xorg.0.log? It will help us see what xorg did not like. At this point, we are still having some configuration issues with xorg that we need to clean up.