On Tue, Oct 28, 2008 at 11:38:57AM -0400, Drew Ogle wrote:
> Ah, missed that.
>
> What it reports is :
> Input device ID: bus 0x3 vendor 0x46d product 0xc626 version 0x110
> Input device name: "3Dconnexion SpaceNavigator"
> Supported events:
> Event type 0 (Sync)
> Event type 1 (Key)
> Eve
Ah, missed that.
What it reports is :
Input device ID: bus 0x3 vendor 0x46d product 0xc626 version 0x110
Input device name: "3Dconnexion SpaceNavigator"
Supported events:
Event type 0 (Sync)
Event type 1 (Key)
Event code 256 (Btn0)
Event code 257 (Btn1)
Event type 2 (Relative)
Ev
On Tue, Oct 28, 2008 at 09:50:56AM -0400, Drew Ogle wrote:
> xinput list doesn't show the device, so I can't use evtest.
evtest is run against the /dev/input device node, not against an xinput
device.
--
Matthew Garrett | [EMAIL PROTECTED]
___
xorg ma
xinput list doesn't show the device, so I can't use evtest.
On Mon, Oct 27, 2008 at 6:56 PM, Peter Hutterer <[EMAIL PROTECTED]>wrote:
> On Mon, Oct 27, 2008 at 01:23:03PM -0400, Drew Ogle wrote:
> > (II) 3Dconnexion SpaceNavigator: Found x and y relative axes
> > (WW) 3Dconnexion SpaceNavigator:
On Mon, Oct 27, 2008 at 01:23:03PM -0400, Drew Ogle wrote:
> (II) 3Dconnexion SpaceNavigator: Found x and y relative axes
> (WW) 3Dconnexion SpaceNavigator: Don't know how to use device
that probably just means that it doesn't expose buttons. what's the output of
evtest when you point it at the de
I have a uncommon pointing device - a 3Dconnexion SpaceNavigator.
Using Fedora 10's 1.5.2, evdev it recognizes it, but isn't sure what to do
with the device.
(II) 3Dconnexion SpaceNavigator: Found x and y relative axes
(WW) 3Dconnexion SpaceNavigator: Don't know how to use device
being the opera
