NIKON DSC E2000 (=coolpix2000) propably needs support in in unusual_devs.h

[ezechiel]

Nikon Coolpix camera stopped working some time ago

regarding https://bugs.launchpad.net/ubuntu/+source/linux/+bug/134477 I start a new description, because this camera does not seem to be in the unusual_devs, as I understand it.

My System - Configuration is:

----------------------------------

Description: Ubuntu 7.10
Release: 7.10

linux-image-2.6.22-14-generic:
  Installiert:2.6.22-14.52
  Mögliche Pakete:2.6.22-14.52
  Versions-Tabelle:
 *** 2.6.22-14.52 0
        500 http://de.archive.ubuntu.com gutsy-updates/main Packages
        500 http://security.ubuntu.com gutsy-security/main Packages
        100 /var/lib/dpkg/status
     2.6.22-14.46 0
        500 http://de.archive.ubuntu.com gutsy/main Packages
----------------------------------

After pluggin in the camera I get the following in /var/log/messages:

Jun 17 15:32:16 hal9000 kernel: [61141.408000] usb 4-1: new full speed USB device using uhci_hcd and address 3
Jun 17 15:32:18 hal9000 kernel: [61142.944000] usb 4-1: configuration #1 chosen from 1 choice
Jun 17 15:32:18 hal9000 kernel: [61142.948000] scsi5 : SCSI emulation for USB Mass Storage devices
Jun 17 15:32:23 hal9000 kernel: [61147.956000] scsi 5:0:0:0: Direct-Access NIKON DSC E2000 1.00 PQ: 0 ANSI: 2
Jun 17 15:32:23 hal9000 kernel: [61147.980000] sd 5:0:0:0: [sdc] 4001761 512-byte hardware sectors (2049 MB)
Jun 17 15:32:23 hal9000 kernel: [61147.984000] sd 5:0:0:0: [sdc] Write Protect is off
Jun 17 15:32:23 hal9000 kernel: [61147.996000] sd 5:0:0:0: [sdc] 4001761 512-byte hardware sectors (2049 MB)
Jun 17 15:32:23 hal9000 kernel: [61148.000000] sd 5:0:0:0: [sdc] Write Protect is off
Jun 17 15:32:23 hal9000 kernel: [61148.000000] sdc: sdc1
Jun 17 15:32:23 hal9000 kernel: [61148.012000] sd 5:0:0:0: [sdc] Attached SCSI removable disk
Jun 17 15:32:23 hal9000 kernel: [61148.012000] sd 5:0:0:0: Attached scsi generic sg3 type 0
Jun 17 15:32:23 hal9000 kernel: [61148.480000] usb 4-1: reset full speed USB device using uhci_hcd and address 3
Jun 17 15:32:24 hal9000 kernel: [61148.756000] usb 4-1: reset full speed USB device using uhci_hcd and address 3
Jun 17 15:32:54 hal9000 kernel: [61179.024000] usb 4-1: reset full speed USB device using uhci_hcd and address 3
Jun 17 15:32:54 hal9000 kernel: [61179.292000] usb 4-1: reset full speed USB device using uhci_hcd and address 3

The last line repeats any few or so.

After turning camera off I get the following in /var/log/messages
Jun 17 15:33:11 hal9000 kernel: [61195.784000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61195.784000] end_request: I/O error, dev sdc, sector 4001760
Jun 17 15:33:11 hal9000 kernel: [61195.884000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61195.884000] end_request: I/O error, dev sdc, sector 4001760
Jun 17 15:33:11 hal9000 kernel: [61195.900000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61195.900000] end_request: I/O error, dev sdc, sector 4001752
Jun 17 15:33:11 hal9000 kernel: [61195.916000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61195.916000] end_request: I/O error, dev sdc, sector 4001753
Jun 17 15:33:11 hal9000 kernel: [61195.928000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61195.928000] end_request: I/O error, dev sdc, sector 4001752
Jun 17 15:33:11 hal9000 kernel: [61195.940000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61195.940000] end_request: I/O error, dev sdc, sector 4001753
Jun 17 15:33:11 hal9000 kernel: [61195.956000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61195.956000] end_request: I/O error, dev sdc, sector 4001760
Jun 17 15:33:11 hal9000 kernel: [61195.972000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61195.972000] end_request: I/O error, dev sdc, sector 4001760
Jun 17 15:33:11 hal9000 kernel: [61195.988000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61195.992000] end_request: I/O error, dev sdc, sector 4001760
Jun 17 15:33:11 hal9000 kernel: [61196.008000] sd 5:0:0:0: [sdc] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61196.008000] end_request: I/O error, dev sdc, sector 4001752
Jun 17 15:33:11 hal9000 kernel: [61196.016000] usb 4-1: USB disconnect, address 3
Jun 17 15:33:11 hal9000 kernel: [61196.020000] scsi 5:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
Jun 17 15:33:11 hal9000 kernel: [61196.020000] end_request: I/O error, dev sdc, sector 4001753

So neither the connect nor the disconnect seems to work properly.

The camera reveals the following information with sudo lsusb -v -s 4:4
(4:4 is the current bus/device)

Bus 004 Device 004: ID 04b0:0301 Nikon Corp. Coolpix 2000 (storage)
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 8
  idVendor 0x04b0 Nikon Corp.
  idProduct 0x0301 Coolpix 2000 (storage)
  bcdDevice 0.10
  iManufacturer 1 NIKON
  iProduct 2 NIKON DSC E2000
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 39
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
      Self Powered
    MaxPower 0mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk (Zip)
      iInterface 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 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 0x83 EP 3 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval 16
Device Status: 0x0000
  (Bus Powered)

Could this be scheduled for the next kernel update please?

[ezechiel (private-alexanderbraun)]

Now using kernel 2-6-22-15, which was rolled out yesterday

The behavior does not differ from the old kernel

Same messages in /va/log/messages as before

[Marlon Cisternas Milla (mcisternas-deactivatedaccount)]

Hi.

I use one Nikon Coopix L4 and I don't have problems. Do you tried with the kernel 2.6.24-19 and Ubuntu Hardy 8.04.1?

Thanks..

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Leann Ogasawara (leannogasawara)]

Marking this Incomplete against the actively developed kernel until we get further feedback. Also, against 2.6.22 this will be closed as it does not qualify for a Stable Release Update - http://wiki.ubuntu.com/StableReleaseUpdates . Thanks.

[Leann Ogasawara (leannogasawara)]

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".