Nikon D40 mass storage not accessible via USB

Bug #145153 reported by David Rekowski
18
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I cannot mount my Nikon D40 any more, since I updated to gutsy (tribe 5). Regular updates didn't solve the problem either.

System: IBM Thinkpad T42p running kernel 2.6.22-12-386

This is the output of dmesg:
<code>
[ 165.708000] usb 4-4: new high speed USB device using ehci_hcd and address 4
[ 165.840000] usb 4-4: configuration #1 chosen from 1 choice
[ 166.028000] usbcore: registered new interface driver libusual
[ 166.248000] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 166.252000] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
[ 166.264000] Initializing USB Mass Storage driver...
[ 166.268000] scsi2 : SCSI emulation for USB Mass Storage devices
[ 166.268000] usb-storage: device found at 4
[ 166.268000] usb-storage: waiting for device to settle before scanning
[ 166.268000] usbcore: registered new interface driver usb-storage
[ 166.268000] USB Mass Storage support registered.
[ 171.268000] usb-storage: device scan complete
[ 171.268000] scsi 2:0:0:0: Direct-Access NIKON D40 1.10 PQ: 0 ANSI: 2
[ 171.268000] sd 2:0:0:0: [sdb] 3970049 512-byte hardware sectors (2033 MB)
[ 171.272000] sd 2:0:0:0: [sdb] Write Protect is off
[ 171.272000] sd 2:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[ 171.272000] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 171.272000] sd 2:0:0:0: [sdb] 3970049 512-byte hardware sectors (2033 MB)
[ 171.272000] sd 2:0:0:0: [sdb] Write Protect is off
[ 171.272000] sd 2:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[ 171.272000] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 171.272000] sdb: sdb1
[ 171.276000] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 171.276000] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 171.652000] end_request: I/O error, dev sdb, sector 3970048
[ 171.652000] Buffer I/O error on device sdb, logical block 3970048
[ 171.656000] end_request: I/O error, dev sdb, sector 3970048
[ 171.656000] Buffer I/O error on device sdb, logical block 3970048
[ 171.660000] end_request: I/O error, dev sdb, sector 3970048
[ 171.660000] Buffer I/O error on device sdb, logical block 3970048
[ 171.660000] end_request: I/O error, dev sdb, sector 3970048
[ 171.660000] Buffer I/O error on device sdb, logical block 3970048
[ 171.664000] end_request: I/O error, dev sdb, sector 3970048
[ 171.664000] Buffer I/O error on device sdb, logical block 3970048
[ 171.676000] end_request: I/O error, dev sdb, sector 3970048
[ 171.676000] Buffer I/O error on device sdb, logical block 3970048
[ 171.680000] end_request: I/O error, dev sdb, sector 3970048
[ 171.680000] Buffer I/O error on device sdb, logical block 3970048
[ 171.680000] end_request: I/O error, dev sdb, sector 40
[ 171.680000] Buffer I/O error on device sdb, logical block 40
[ 171.684000] end_request: I/O error, dev sdb, sector 41
[ 171.684000] Buffer I/O error on device sdb, logical block 41
[ 171.684000] Buffer I/O error on device sdb, logical block 42
[ 171.684000] end_request: I/O error, dev sdb, sector 40
[ 171.684000] end_request: I/O error, dev sdb, sector 41
[ 171.688000] end_request: I/O error, dev sdb, sector 40
[ 171.688000] end_request: I/O error, dev sdb, sector 41
[ 171.688000] end_request: I/O error, dev sdb, sector 40
[ 171.692000] end_request: I/O error, dev sdb, sector 41
[ 171.692000] end_request: I/O error, dev sdb, sector 40
[ 171.692000] end_request: I/O error, dev sdb, sector 41
[ 171.716000] end_request: I/O error, dev sdb, sector 0
[ 171.716000] end_request: I/O error, dev sdb, sector 0
[ 171.716000] end_request: I/O error, dev sdb, sector 1
[ 171.720000] end_request: I/O error, dev sdb, sector 0
[ 171.720000] end_request: I/O error, dev sdb, sector 1
[ 171.744000] end_request: I/O error, dev sdb, sector 249
<snipped-110-repeating-249-250-lines />
[ 171.960000] end_request: I/O error, dev sdb, sector 250
[ 171.964000] end_request: I/O error, dev sdb, sector 0
[ 171.964000] end_request: I/O error, dev sdb, sector 1
[ 171.964000] end_request: I/O error, dev sdb, sector 0
[ 171.968000] end_request: I/O error, dev sdb, sector 1
[ 171.968000] end_request: I/O error, dev sdb, sector 0
[ 171.968000] end_request: I/O error, dev sdb, sector 1
</code>

I put the same SD-Card in a Casio Exilim EX-Z 750 and used the docking station to connect. Worked fine. I also can plug in and mount other external USB HDDs.

Revision history for this message
Stuart Read (sread) wrote :

I have the exact same problem with a Nikon D50. This camera also worked perfectly before upgrading to Gutsy.

Revision history for this message
Jonathan Crockett (jcrockett) wrote :

I believe the problem is in the way the Nikon cameras report the mass storage size. See my comment in bug #134477.

Revision history for this message
Roel Groeneveld (roel-groeneveld) wrote :

I had the same problem with a Nikon D50, which was set to the USB Mass Storage setting. Changing the in-camera setting from USM Mass Storage to PTP made libgphoto recognize it.

Revision history for this message
Jonathan Crockett (jcrockett) wrote : Re: [Bug 145153] Re: Nikon D40 mass storage not accessible via USB

On Wed, Oct 03, 2007 at 09:03:37PM -0000, Roel Groeneveld wrote:
> From: Roel Groeneveld <email address hidden>
> Subject: [Bug 145153] Re: Nikon D40 mass storage not accessible via USB
> To: <email address hidden>
> Reply-To: Bug 145153 <email address hidden>
> Date: Wed, 03 Oct 2007 21:03:37 -0000
>
> I had the same problem with a Nikon D50, which was set to the USB Mass
> Storage setting. Changing the in-camera setting from USM Mass Storage to
> PTP made libgphoto recognize it.
>

True, that will work. Also, the USB Mass Storage will be fixed for
Nikon D-40/50/80/100/200 in an upcoming release via this bug:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/134477

-Jonathan

--------------------------------------------------------------------------------
                               Jonathan Crockett
      | | Software Developer
     :|: :|:
    :|||: :|||: Access Router Technology Group
 .:|||||||:..:|||||||:. mailto:<email address hidden>
C i s c o S y s t e m s +1 (408) 902-8892
--------------------------------------------------------------------------------

Revision history for this message
hotani (hotani) wrote :

Same problem here. D40 was working fine in Feisty but I lost the ability to mount it with the Gutsy upgrade.

Revision history for this message
Adam Jiang (jiang-adam) wrote :

I got the same problem. My Nikon D40 worked fine in Feisty.
There are some informations
XXX@XXXXX:~$ lsusb
Bus 005 Device 006: ID 04b0:0413 Nikon Corp.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 002: ID 046d:08a9 Logitech, Inc.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 002: ID 046d:c50e Logitech, Inc. MX-1000 Cordless Mouse Receiver
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
XXX@XXXXX:~$ mount
/dev/sda2 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw,noexec,nosuid,nodev)
/sys on /sys type sysfs (rw,noexec,nosuid,nodev)
varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
udev on /dev type tmpfs (rw,mode=0755)
devshm on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
lrm on /lib/modules/2.6.22-14-generic/volatile type tmpfs (rw)
/dev/sda5 on /home type ext3 (rw)
/dev/sda1 on /media/sda1 type fuseblk (rw,nosuid,nodev,noatime,allow_other,default_permissions,blksize=4096)
securityfs on /sys/kernel/security type securityfs (rw)

Revision history for this message
Wouter Horré (wouterh) wrote :

Same problem here with a D40x.

I'm running Kubuntu Gutsy Final.

Revision history for this message
David Rekowski (david-rekowski) wrote :

I don't have the problem with a recent kernel any more. It works for me.

Revision history for this message
Wouter Horré (wouterh) wrote :

@David: do you have a D40 or a D40x?

Last time I checked, it was not working for my D40x.

Revision history for this message
David Rekowski (david-rekowski) wrote :

I have a Nikon D40. I bought it in August 2007, I don't have the firmware version at hand, though.
And I run Ubuntu, not Kubuntu, if that is relevant for any reason.

$ uname -a
Linux telos 2.6.22-14-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686 GNU/Linux

Revision history for this message
Wouter Horré (wouterh) wrote :

Ok. That confirms what other people have reported already. It works
for the D40 with a recent kernel.

I'll do another test with my D40x tonight to see if anything has
changed since my last test.

On 11/5/07, David Rekowski <email address hidden> wrote:
> I have a Nikon D40. I bought it in August 2007, I don't have the firmware version at hand, though.
> And I run Ubuntu, not Kubuntu, if that is relevant for any reason.
>
> $ uname -a
> Linux telos 2.6.22-14-386 #1 Sun Oct 14 22:36:54 GMT 2007 i686 GNU/Linux
>
> --
> Nikon D40 mass storage not accessible via USB
> https://bugs.launchpad.net/bugs/145153
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
http://wouter.horre.be/

Revision history for this message
Wouter Horré (wouterh) wrote :

I've just retested my D40x. It is still not working. I have firmware version 1.00.

$ uname -a
Linux abel 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Revision history for this message
Vital (vital-butinar) wrote :

Same thing here. Nikon D40x firmware version 1.00 on kernel "Linux localhost 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux" doesn't work.
I tried patching kernel 2.6.23 but also no luck there. Unfortunately there is no firmware upgrade for D40x.

Revision history for this message
tomaszko (kossut) wrote :

Hello,

I have the same problem with D40x

Revision history for this message
ces (goodmorning-no) wrote :

Same problem here, using a Nikon D40. Can someone confirm whether this problem is fixed with a new kernel, and what version it is? I can import photos when setting the mode to PTP as mentioned above. I am using the 2.6.22-14-rt (realtime) kernel.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux-source-2.6.22.

Revision history for this message
Brian Murray (brian-murray) wrote :

Reviewing this bug report and its comments it seems that multiple people are experiencing this problem. Subsequently, I am confirming this bug report. For future reference you can manage the status of bug reports by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status .

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Stuart Read (sread) wrote :

I used my Nikon D50 yesterday and it operated perfectly as before. This is with a fully updated version of Gutsy. Note that earlier this fall it did not work with an updated version of Gutsy, so along the way an update must have fixed the problem, at least for me. Perhaps others who had this problem could recheck with an updated system.

Revision history for this message
Wouter Horré (wouterh) wrote :

@Stuart: It was fixed a while ago for most camera's (see earlier in
this bug report), but the D40x is still broken (I just retested with
the latest gutsy updates).

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

Changed in linux:
status: New → Incomplete
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Against linux-source-2.6.22 this bug does not meet the criteria for a stable release update and is being marked as Won't Fix. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . However, please note that the bug is not being closed as work will continue on fixing it for the next release, Hardy Heron (8.04). The newly added 'linux' task, corresponds the the Hardy kernel package. Thanks!

Changed in linux-source-2.6.22:
status: Confirmed → Won't Fix
Revision history for this message
mayo_s (majo-s) wrote :

I have same problem with stable Ubuntu 8.04 and Nikon D40. Same SD card in SD card reader work`s fine.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.