Same problem with a hamster III plus
libfprint 0.0.6-2 installed from synaptic
lsusb output:

Bus 001 Device 048: ID 1162:0300 Secugen Corp.
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x1162 Secugen Corp.
  idProduct          0x0300
  bcdDevice           50.11
  iManufacturer           1 SecuGen Corp.
  iProduct                2 SecuGen USB
  iSerial                 0
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           55
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              100mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           0
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           4
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x06  EP 6 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
Device Status:     0x0000
  (Bus Powered)


fprintdemo output:

fdu2000:error [dev_init] Command: CAPTURE_END
fdu2000:error [dev_init] could not init dev
fdu2000:error [dev_init] No error
fp:error [fp_dev_open] device initialisation failed, driver=fdu2000

Best regards
Andrés

On Wed, May 5, 2010 at 11:07 AM, Sergej Pupykin <[email protected]> wrote:

> Hi,
>
> I have Secugen scanner, and want to help make it working
>
> Bus 001 Device 004: ID 1162:0322 Secugen Corp.
>
> After I add
>
> { .vendor = 0x1162, .product = 0x0322 },
>
> line into fdu2000.c it recognizes device but prints error:
>
> # pam_fprint_enroll
> This program will enroll your finger, unconditionally overwriting any
> selected print that was enrolled previously. If you want to continue,
> press enter, otherwise hit Ctrl+C
>
> Found device claimed by Secugen FDU 2000 driver
> fdu2000:error [dev_init] could not init dev
> fdu2000:error [dev_init] could not set alt intf 0/1: Invalid argument
> fp:error [fp_dev_open] device initialisation failed, driver=fdu2000
> Could not open device.
>
> # dmesg -c
> usb 1-3: selecting invalid altsetting 1
>
> _______________________________________________
> fprint mailing list
> [email protected]
> http://lists.reactivated.net/mailman/listinfo/fprint
>
_______________________________________________
fprint mailing list
[email protected]
http://lists.reactivated.net/mailman/listinfo/fprint

Reply via email to