Bug 137129 - [ums] [usb8] SteelSeries Ikari USB laser mouse not attaching
Summary: [ums] [usb8] SteelSeries Ikari USB laser mouse not attaching
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: usb (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-usb (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-25 15:30 UTC by Alastair Hogge
Modified: 2017-12-31 22:35 UTC (History)
0 users

See Also:

Attachments
file.diff (583 bytes, patch)
2009-07-25 15:30 UTC, Alastair Hogge 		no flags Details | Diff
file.diff (932 bytes, patch)
2009-07-25 15:30 UTC, Alastair Hogge 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alastair Hogge 2009-07-25 15:30:01 UTC 
Mouse fails to attach/load. No screen pointer.

Fix: The following diffs add a product code & a quirk. 
How-To-Repeat: Plug in Ikari laser mouse.
Comment 1 Hans Petter Selasky 2009-07-25 16:00:43 UTC 
Hi,

Your patch looks good.

Is this device being driven by libusb?

Can you send output from:

usbconfig -u XXX -a YYY dump_device_desc dump_curr_config_desc

For your device, and I'll get your patch in.

Thanks for your patch.

--HPS
Comment 2 agh 2009-07-25 16:58:14 UTC 
How can I find out if the mouse is being driven by libusb?

# usbconfig -u 0 -a 3 dump_device_desc dump_curr_config_desc
ugen0.3: <Ikari Laser SteelSeries ApS> at usbus0, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200          
  bDeviceClass = 0x0000    
  bDeviceSubClass = 0x0000 
  bDeviceProtocol = 0x0000 
  bMaxPacketSize0 = 0x0008 
  idVendor = 0x04b4        
  idProduct = 0x121f       
  bcdDevice = 0x0100       
  iManufacturer = 0x0001  <SteelSeries ApS>
  iProduct = 0x0002  <Ikari Laser>         
  iSerialNumber = 0x0000  <no string>      
  bNumConfigurations = 0x0001              


 Configuration index 0

    bLength = 0x0009 
    bDescriptorType = 0x0002 
    wTotalLength = 0x0022    
    bNumInterfaces = 0x0001  
    bConfigurationValue = 0x0001 
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x00a0               
    bMaxPower = 0x0019                  

    Interface 0
      bLength = 0x0009 
      bDescriptorType = 0x0004 
      bInterfaceNumber = 0x0000 
      bAlternateSetting = 0x0000 
      bNumEndpoints = 0x0001     
      bInterfaceClass = 0x0003   
      bInterfaceSubClass = 0x0001 
      bInterfaceProtocol = 0x0002 
      iInterface = 0x0000  <no string>

      Additional Descriptor

      bLength = 0x09
      bDescriptorType = 0x21
      bDescriptorSubType = 0x11
       RAW dump:
       0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0xe8,
       0x08 | 0x00

     Endpoint 0
        bLength = 0x0007
        bDescriptorType = 0x0005
        bEndpointAddress = 0x0081
        bmAttributes = 0x0003
        wMaxPacketSize = 0x0008
        bInterval = 0x0001
        bRefresh = 0x0000
        bSynchAddress = 0x0000
Comment 3 Hans Petter Selasky 2009-07-25 17:09:02 UTC 
On Saturday 25 July 2009 17:58:14 Alastair Hogge wrote:
> How can I find out if the mouse is being driven by libusb?

What application are you using your mouse with? X11 or some Game?

--HPS
Comment 4 agh 2009-07-26 01:08:14 UTC 
On Sun July 26 2009 00:09:02 Hans Petter Selasky wrote:
> On Saturday 25 July 2009 17:58:14 Alastair Hogge wrote:
> > How can I find out if the mouse is being driven by libusb?
>
> What application are you using your mouse with? X11 or some Game?
OK. Mouse works in console, X11, & tested with some games I have installed.

> --HPS
-al
Comment 5 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:01:44 UTC 
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped