Ok. Solved it. It is sensitive to the ORDER that you load the modules: These have to go in in this order: evdev acecad usb-uhci I'll be writing a HOWTO for the Acecad Acecat Flair + let you guys know. J On Sun, 9 Sep 2001 00:45, you wrote: > This is driving me nutz. > > I got updated drivers for the Acecat Flair USB as noted in my last post, > compiled, installed etc. All fine. This driver is supposed to work with > XFree86, and indeed it does seem to do the right things as far as > initializing the tablet, and querying it etc. I put printk debug statements > in the driver itself acecat.o - and XFree debug statements in the > acecat_drv.o file and came to the conclusion that the kernel device driver > acecat.o never received an interrupt from the tablet. > > Since then, I have backed off to XFree86 v4.03 and recompiled - the whole > bit etc. No difference. > > I also got a program called xinput which is set up to test xinput devices. > Notice, further below, that the device is queried with no problem - and I > know it is functional because of this test: > > # cat -vet /dev/input/event0 > .-M-^Z;hj^F^@^A^@@^A^A^@^@^@.-M-^Z;hj^F^@^C^@^@^@M-=^P^@^@ > .-M-^Z;hj^F^@^C^@^A^@^\^L^@^@.-M-^Z;xM-^Q^F^@^C^@^@^@^A^R^@^ > @.-M-^Z;xM-^Q^F^@^C^@^A^@M-^L^L^@^@.-M-^Z;M-^XM-_^F^@^C^@^@^ > @M-^_^R^@^@.-M-^Z;M-^XM-_^F^@^C^@ > ( These are characters sent when the stylus gets into proximity. ) > > > However, under xinput (and gimp and X itself) the kernel never sees any > interrups or passes them on from the tablet. It therefore thinks that the > stylus is out of proximity at all times. > > Does anyone have any clue at all what I am missing here? I am pretty sure > that the drivers are loaded correctly, and installed correctly since > looking at dmesg confirms this. The USB system seems to be installed okay > too - but in any case, xinput can query the thing. I've even unloaded the > usbmouse module in case that was swallowing interrupts. No change) > > It has to be something really simple. Some dumb configuration somewhere, or > maybe a loadable driver that is not loaded. (btw - I do load evdev) > > [jeremy@linux jeremy]$ xinput > usage : > xinput get-feedbacks <device name> > xinput set-ptr-feedback <device name> <threshold> <num> <denom> > xinput set-integer-feedback <device name> <feedback id> <value> > xinput set-button-map <device name> <map button 1> [<map button 2> > [...]] > xinput set-pointer <device name> [<x index> <y index>] > xinput set-mode <device name> ABSOLUTE|RELATIVE > xinput list [<device name>...] > xinput query-state <device name> > xinput test [-proximity] <device name> > xinput version > [jeremy@linux jeremy]$ xinput query-state Stylus0 > 2 classes : > ButtonClass > button[1]=up > button[2]=up > button[3]=up > ValuatorClass Mode=Absolute Proximity=Out > valuator[0]=0 > valuator[1]=0 > valuator[2]=0 > > [jeremy@linux jeremy]$ xinput test Stylus0 > > (nothing at all here) > > > --------------------------------------------------------------------------- >-- > > Thanks, > Jeremy. > _______________________________________________ > Newbie mailing list > [EMAIL PROTECTED] > *** To unsubscribe , or change message options, see: > http://XFree86.Org/mailman/listinfo/newbie _______________________________________________ Newbie mailing list [EMAIL PROTECTED] *** To unsubscribe , or change message options, see: http://XFree86.Org/mailman/listinfo/newbie
