wacom and x11 and webcamd
denverh at comcast.net
Mon Mar 26 14:25:49 UTC 2012
Hans Petter Selasky wrote:
> On Saturday 24 March 2012 18:14:41 Denver Hull wrote:
>> I discovered this when I saw an update to input-wacom at
>> freshports.org. I've installed cuse4bsd, the new input-wacom, and the
>> latest webcamd:
>> I believe I've followed all the instructions properly, and when I start
>> webcamd, everything seems to be correct:
>> Attached ugen1.2 to cuse unit 0
>> Creating /dev/input/event0
>> According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen):
>> ugen1.2:<Wacom Co.,Ltd.> at usbus1
>> The /dev/input/event0 node is indeed created. However, when I start X,
>> I get the following:
>> (EE) stylus: Wacom X driver can't grab event device (Bad address)
>> (EE) eraser: Wacom X driver can't grab event device (Bad address)
>> (EE) cursor: Wacom X driver can't grab event device (Bad address)
>> (EE) pad: Wacom X driver can't grab event device (Bad address)
>> (EE) touch: Wacom X driver can't grab event device (Bad address)
>> Protocol not supported by server
>> The last line repeats indefinitely, and X never finishes starting up.
>> The system I'm trying this on is 8.3-PRERELEASE. I had tried this
>> quickly a while ago on 8.2-STABLE with similar results.
>> Does anyone have any ideas about what might be wrong?
> I think the wacom has two interfaces.
> So you need to do two instances of webcamd, using -i 0 and -i 1 .
> Else search google for webcamd-220.127.116.11
Thanks for the reply. I did have trouble figuring out how to get
webcamd started properly. The start script in /usr/local/etc/rc.d looks
like it needs at least two parameters, but it wasn't clear what they
should be. When I get a chance I'll look at that again & see if I can
figure something out. I'll let you know how I do.
The "Protocol not supported" problem was something else, not related to
the tablet or webcamd.
More information about the freebsd-usb