Re: New Wacom Bamboo not working
Quote:
Originally Posted by
Favux
Yeah, I wish it would have been as simple as dependencies. I'll check over the modifications to the code again just to be sure. Each time after getting the error I also did a make clean because that worked for someone the development mailing list. I'm not really to sure what I else I can try and it's frustrating to get caught in the first step of the process. Who knows when I'll get to fail at configuring X to handle it :P?
Thanks for the link. I'll sit back and watch the rest and report back if I make any progress.
Re: New Wacom Bamboo not working
Hi johnny2k,
Did you try:
Code:
./configure --enable-wacom --prefix=/usr
instead of?:
Code:
./configure --enable-wacom
Re: New Wacom Bamboo not working
Quote:
Originally Posted by
Favux
Hi johnny2k,
Did you try:
Code:
./configure --enable-wacom --prefix=/usr
instead of?:
Code:
./configure --enable-wacom
Yeah, tried that too. I don't understand the error at all because I've built a module from source before and didn't have to do any kernel config business. It seems like most people have an easy time with this part, right? You didn't seen anything weird in the config summary did you?
Code:
----------------------------------------
BUILD ENVIRONMENT:
architecture - i486-linux-gnu
linux kernel - yes 2.6.28
module versioning - no
kernel source - yes /lib/modules/2.6.28-3-rt/build
XFree86 source - no
Xorg SDK - yes /usr/include/xorg
XSERVER64 - no
dlloader - yes
XLib - yes /usr/lib
xf86config - no
TCL - yes /usr/include/tcl8.4
TK - yes /usr/include/tcl8.4
ncurses - yes
BUILD OPTIONS:
wacom.o - yes
wacdump - yes
xidump - yes
libwacomcfg - yes
libwacomxi - yes
xsetwacom - yes
hid.o - no
wacom_drv.so - yes /usr/lib/xorg/modules/input
wacom_drv.o - no
wacom*_drv quirks - Uninit-called IsXExtensionPointer key-events dixScreenOrigins
----------------------------------------
Re: New Wacom Bamboo not working
Hi johnny2k,
Nope, looks ok. I'm confused. Given that you:
Code:
sudo apt-get install linux-headers-rt
It should configure. Yes, it should be "easy". May be someone else will recognize it.
Code:
Drivers not enabled as modules in your kernel config but requested through configure are NOT built
Re: New Wacom Bamboo not working
So far I can only come up with two alternatives. Neither seems very likely.
Either the kernel-header package isn't complete and lacks a .config, which stores the configuration of the kernel. And this is why you can't compile the kernel module.
Or the kernel is monolithic? The build process, trying to make the kernel modules, fails when the kernel is monolithic. But the rt kernel isn't monolithic. You'd have to use something like:
Code:
./configure --without-kernel --enable-wacom --prefix=/usr
But this doesn't build the kernel module you want to build.
Re: New Wacom Bamboo not working
Wow, you guy's have had a long discussion, I am totally left behind!
Re: New Wacom Bamboo not working
Hi,
I've got one of those new Wacom Bamboo Fun & Touch (CTH-661) and followed the instruction on how to modify the source to create a working .ko. Up to this point, everything seems to be working as I'm getting the following when booting (or adding the Wacom tablet):
Oct 19 10:24:28 efortin-laptop kernel: [ 8.959942] input: Wacom Intuos2 6x8 as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input8
Oct 19 10:24:28 efortin-laptop kernel: [ 8.977825] input: Wacom Intuos2 6x8 as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.1/input/input9
Oct 19 10:24:28 efortin-laptop kernel: [ 8.986771] usbcore: registered new interface driver wacom
Oct 19 10:24:28 efortin-laptop kernel: [ 8.986775] wacom: v1.49-pc-1:USB Wacom Graphire and Wacom Intuos tablet driver
This create automatically a /dev/input/wacom and /dev/input/wacom-touch. I can also see the device with a more /proc/bus/input/devices
I: Bus=0003 Vendor=056a Product=00d3 Version=0106
N: Name="Wacom Intuos2 6x8"
P: Phys=
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input8
U: Uniq=
H: Handlers=mouse2 event8
B: EV=1f
B: KEY=1cdf 0 1f0000 0 0 0 0 0 0 0 0
B: REL=100
B: ABS=100 f000163
B: MSC=1
I: Bus=0003 Vendor=056a Product=00d3 Version=0106
N: Name="Wacom Intuos2 6x8"
P: Phys=
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input8
U: Uniq=
H: Handlers=mouse2 event8
B: EV=1f
B: KEY=1cdf 0 1f0000 0 0 0 0 0 0 0 0
B: REL=100
B: ABS=100 f000163
B: MSC=1
However, I'm unable to do a xxd or wacdump on those devices. The first one is not providing any feedback at all and the second one is doing a segmentation fault.
BTW, I've tried both GRAPHIRE and WACOM_MO. I always get the same results.
I've tried to modify the xorg.conf as documented both on the linuxwacom project site and here without success so... I think I won't have it working until I at least get some noise from xxd or wacdump. For now, it seems the kernel is seeing the tablet but there is a missing link somewhere.
Is there something really obvious that I missed? Note that I've also tried creating a uvdev file. This change nothing.
If I unplug/replug the tablet, the device is getting a new event# each time but the /dev/input/wacom is not updated (it is only updated when rebooting). Also, once I unplug/replug without rebooting, I get a message saying this:
Oct 19 09:05:41 efortin-laptop logger: device input11 is bound to the driver
Oct 19 09:05:41 efortin-laptop logger: must rebind
Oct 19 09:05:41 efortin-laptop logger: device input12 is bound to the driver
Oct 19 09:05:41 efortin-laptop logger: must rebind
It is probably not a big issue for now but I have to remember not to unplug/replug the tablet if I want to do some test. I'm better with rebooting and then add the tablet (or have it connected when it's booting).
Any idea of what can be wrong?
Thank you for your time.
ehfortin
Re: New Wacom Bamboo not working
Quote:
Originally Posted by
Favux
Hi johnny2k,
Nope, looks ok. I'm confused. Given that you:
Code:
sudo apt-get install linux-headers-rt
It should configure. Yes, it should be "easy". May be someone else will recognize it.
Code:
Drivers not enabled as modules in your kernel config but requested through configure are NOT built
I am not for sure if this message is something of concern or not. I just compiled it on mine and I receive the same message. The kernel module is built along with all executables and shared objects.
If you are able to find the wacom.ko file in src/2.6.28 and the wacom_drv.so in src/xdrv, you might just go ahead and install it.
Re: New Wacom Bamboo not working
Quote:
Originally Posted by
ehfortin
Hi,
I've got one of those new Wacom Bamboo Fun & Touch (CTH-661) and followed the instruction on how to modify the source to create a working .ko. Up to this point, everything seems to be working as I'm getting the following when booting (or adding the Wacom tablet):
Oct 19 10:24:28 efortin-laptop kernel: [ 8.959942] input: Wacom Intuos2 6x8 as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input8
Oct 19 10:24:28 efortin-laptop kernel: [ 8.977825] input: Wacom Intuos2 6x8 as /devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.1/input/input9
Oct 19 10:24:28 efortin-laptop kernel: [ 8.986771] usbcore: registered new interface driver wacom
Oct 19 10:24:28 efortin-laptop kernel: [ 8.986775] wacom: v1.49-pc-1:USB Wacom Graphire and Wacom Intuos tablet driver
This create automatically a /dev/input/wacom and /dev/input/wacom-touch. I can also see the device with a more /proc/bus/input/devices
I: Bus=0003 Vendor=056a Product=00d3 Version=0106
N: Name="Wacom Intuos2 6x8"
P: Phys=
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input8
U: Uniq=
H: Handlers=mouse2 event8
B: EV=1f
B: KEY=1cdf 0 1f0000 0 0 0 0 0 0 0 0
B: REL=100
B: ABS=100 f000163
B: MSC=1
I: Bus=0003 Vendor=056a Product=00d3 Version=0106
N: Name="Wacom Intuos2 6x8"
P: Phys=
S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb5/5-1/5-1:1.0/input/input8
U: Uniq=
H: Handlers=mouse2 event8
B: EV=1f
B: KEY=1cdf 0 1f0000 0 0 0 0 0 0 0 0
B: REL=100
B: ABS=100 f000163
B: MSC=1
However, I'm unable to do a xxd or wacdump on those devices. The first one is not providing any feedback at all and the second one is doing a segmentation fault.
BTW, I've tried both GRAPHIRE and WACOM_MO. I always get the same results.
I've tried to modify the xorg.conf as documented both on the linuxwacom project site and here without success so... I think I won't have it working until I at least get some noise from xxd or wacdump. For now, it seems the kernel is seeing the tablet but there is a missing link somewhere.
Is there something really obvious that I missed? Note that I've also tried creating a uvdev file. This change nothing.
If I unplug/replug the tablet, the device is getting a new event# each time but the /dev/input/wacom is not updated (it is only updated when rebooting). Also, once I unplug/replug without rebooting, I get a message saying this:
Oct 19 09:05:41 efortin-laptop logger: device input11 is bound to the driver
Oct 19 09:05:41 efortin-laptop logger: must rebind
Oct 19 09:05:41 efortin-laptop logger: device input12 is bound to the driver
Oct 19 09:05:41 efortin-laptop logger: must rebind
It is probably not a big issue for now but I have to remember not to unplug/replug the tablet if I want to do some test. I'm better with rebooting and then add the tablet (or have it connected when it's booting).
Any idea of what can be wrong?
Thank you for your time.
ehfortin
When you start up and you see that the wacom module has loaded through dmesg or /var/log/messages, have you checked /var/log/Xorg.0.log? It will tell you if the device is attached to xorg or not.
Re: New Wacom Bamboo not working
Hi again,
Well, in the Xorg log, I can see that the it is talking with the Wacom. The /dev/input/event7 (wacom) is getting the "Wacom Intuos2 6x8 Wacom X driver can't grab event device, errno=16" for the device. This error message is not there for any of the related stuff (erase, stylus, pad, etc). The /dev/input/event8 (wacom-touch) seems to be fine (Wacom Intuos2 6x8 Wacom X driver grabbed event device. and I don't see any error related to this but... it is not helping as X is not doing anything.
Actually, once the xorg.conf is configured, I'm loosing my USB mouse as well. Is there a way to have both (tablet and mouse) active at the same time? At least, while I'm debugging the tablet, that would help instead of having to go back to a terminal.
Is that information that is helping? I can do a cut&paste but I'll have to reboot as... I don't have access to my mouse right now :)
Thank you.
ehfortin