NaturalPoint SmartNav4 support

[Bryce Harrington]

Binary package hint: hal-info

Here's a start at an FDI file for the SmartNav4 hands-free mouse:

<?xml version="1.0" encoding="ISO-8859-1"?>

<deviceinfo version="0.2">
  <device>
    <match key="usb_device.vendor" prefix="Natural Point">

      <match key="usb_device.product_id" int="262">
        <merge key="info.product" type="string">SmartNav 4</merge>
        <merge key="input.x11_driver" type="string">evdev</merge>
        <append key="input.x11_options.SendCoreEvents" type="string">true</append>
      </match>

    </match>
  </device>
</deviceinfo>

[Bryce Harrington (bryce)]

This was at the tail end of Xorg.0.log:

(WW) config/hal: no driver or path specified for /org/freedesktop/Hal/devices/usb_device_131d_106_noserial

[Bryce Harrington (bryce)]

The problem seems to be that the info.capabilities property is not getting set (see the lshal output). It should be set to {'input', 'input.mouse'}, however that's generally not done in FDI files.

So something lower level (kernel perhaps?) needs to set the capabilities for the device.

Possibly there may also need to be kernel-level driver support added for it, but I'm not sure.

[Bryce Harrington (bryce)]

Created an attachment (id=19509)
Difference in lshal output when device is attached

The SmartNav4 is a hands-free USB mouse device. HAL seems to be picking it up, however it's not associating input.capabilities information with it. I'm guessing this is why it isn't getting associated with evdev? What needs done to get the input.capabilities to list input.mouse?

This is what shows in Xorg.0.log when the device is plugged in:

(WW) config/hal: no driver or path specified for /org/freedesktop/Hal/devices/usb_device_131d_106_noserial

[Julien Cristau (jcristau)]

On Wed, Oct 8, 2008 at 22:13:59 -0700, <email address hidden> wrote:

> The SmartNav4 is a hands-free USB mouse device. HAL seems to be picking it up,
> however it's not associating input.capabilities information with it. I'm
> guessing this is why it isn't getting associated with evdev? What needs done
> to get the input.capabilities to list input.mouse?
>
Sounds like NOTOURBUG, then. Need to look into hal or the kernel as far
as I can tell.

[Bryce Harrington (bryce)]

What in particular in hal or the kernel needs to be investigated?

I'm trying to sort out, what's the upstreaming path for these kinds of bugs... What component is responsible for setting the input.capabilities value?

[Bryce Harrington (bryce)]

I'm adding a kernel task to investigate if there is a kernel driver issue needing to be resolved, as X upstream seems to suggest.

[Bryce Harrington (bryce)]

This is printed to dmesg when connecting the device:

[714855.492077] usb 4-3: new high speed USB device using ehci_hcd and address 2
[714856.320559] usb 4-3: string descriptor 0 read error: -22
[714856.320683] usb 4-3: string descriptor 0 read error: -22
[714856.321530] usb 4-3: configuration #1 chosen from 1 choice

[Leann Ogasawara (leannogasawara)]

Hi Bryce,

After you've plugged in the device, what's the output of lsusb. I'm also curious if the device shows up in /proc/bus/input/devices (I'm assuming it doesn't). Based on the dmesg output you pasted, I don't think it's registering as an input device. I expected to see something similar to:

[2907019.089597] usb 1-2: new low speed USB device using uhci_hcd and address 2
[2907019.321575] usb 1-2: configuration #1 chosen from 1 choice
[2907019.337707] input: Dynex 5-Button Wired Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/input/input8
[2907019.373452] input,hidraw2: USB HID v1.11 Mouse [Dynex 5-Button Wired Optical Mouse] on usb-0000:00:1d.0-2

[Bryce Harrington (bryce)]

On Fri, Oct 31, 2008 at 04:41:27PM -0000, Leann Ogasawara wrote:
> Hi Bryce,
>
> After you've plugged in the device, what's the output of lsusb. I'm

Here is the change in lsusb output from before and after plugging in the
device:

--- lsusb.1 2008-10-31 15:25:48.000000000 -0700
+++ lsusb.2 2008-10-31 15:25:59.000000000 -0700
@@ -4,4 +4,5 @@ Bus 005 Device 001: ID 1d6b:0001 Linux F
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+Bus 004 Device 003: ID 131d:0106 Natural Point
 Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

> also curious if the device shows up in /proc/bus/input/devices (I'm
> assuming it doesn't). Based on the dmesg output you pasted, I don't
> think it's registering as an input device.

Right, it's not showing up there. Attached is my devices file.

Bryce

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Bryce Harrington (bryce)]

[Hal is obsolete; closing out the tasks, but leaving the linux task. Actually I think this might need to go against udev now perhaps.]

[Ajax-a (ajax-a)]

Mass closure: This bug has been untouched for more than six years, and is not
obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.