Hans Petter Selasky wrote:
On Monday 09 April 2012 21:28:02 Denver Hull wrote:
Hans Petter Selasky wrote:
On Monday 09 April 2012 19:59:17 Denver Hull wrote:
Hans Petter Selasky wrote:
On Thursday 29 March 2012 23:20:43 Denver Hull wrote:
Hans Petter Selasky wrote:
On Saturday 24 March 2012 18:14:41 Denver Hull wrote:
Hello,
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:
cuse4bsd-kmod-0.1.23
input-wacom-40.0.11.1
webcamd-3.2.0.2
I believe I've followed all the instructions properly, and when I
start webcamd, everything seems to be correct:
Attached ugen1.2[0] 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?
Hi,
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-3.4.0.1
--HPS
My Bamboo Pen is working fine now. I installed your latest version,
webcamd-3.4.0.1, and that takes care of getting webcamd started
properly. It's still necessary to make sure moused doesn't attach to
the tablet. I'm not sure what the best way is to do that, but for now
I've adjusted /etc/devd.conf so only the first ums device gets
attached.
Thanks Hans, this is great. I wish I had one or two other devices I
could try.
Hi,
To avoid ums attach, see "usbconfig dump_quirk_names | grep UMS".
--HPS
I don't get anything with that command on my 8.2-STABLE system. Is that
something that will work on 9 but not 8?
Did you kldload usb_quirk ?
--HPS
Well, that reports "kldload: can't load usb_quirk: File exists", but
usb_quirk isn't listed in kldstat. The man page for usb_quirk(4)
doesn't show anything for UMS. However, everything listed in the man
page is reported by "usbconfig dump_quirk_names". Or at least it looks
that way. I didn't do a line by line check.
I checked my kernel conf file, and there's no "device usb_quirk" line,
and it's not in loader.conf, so I'm not sure where it's coming from. In
my experience that kldload error usually just means it's compiled in.
But it's not listed in my kernel conf file. So that's kind of a mystery.
Did you run the usbconfig command like root ?
--HPS
Yes.
_______________________________________________
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
