NIKON D80 with firmware 1.10 needs support in in unusual_devs.h

Bug #245118 reported by Victor Osadci
10
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Hardy by Ivan Panchenko

Bug Description

Nikon has released new firmware ver.1.10, which is not in "unusual_devs.h", so USB mass storage for the camera stopped working after the firmware update.

Look at bug # 134477 for more info

Tags: cft-2.6.27
Revision history for this message
Guilherme Salgado (salgado) wrote :

Is it really 1.10 that needs to be in unusual_devs.h? The patch at http://lkml.org/lkml/2008/7/14/262 seems to imply that it should fix the issue for D80+1.11 as well, but isn't it actually replacing 1.10 with 1.11 on the D80 section?

Revision history for this message
Victor Osadci (victor-os) wrote :

Guilherme,

1. There is no 1.11 firmware for the D80 - maybe they put that in there to make sure it works for future firmware too.

2. I'm not familiar with what should "UNUSUAL_DEV" contain, but a similar change for the D40 was reported as fixing the bug for D40. I assume that the "0x0100, 0x0110" string is a range - from 1.00 to 1.10; so changing it to "0x0100, 0x0111" could work.

3. Even firmware 1.10 does not work for me in Ubuntu Hardy, so I assume that Hardy only has 1.01 in "unusual_devs.h". Can this change be back ported to Hardy ?

Revision history for this message
Victor Osadci (victor-os) wrote :

Hrm, I don't like putting non-existing firmware in there - what if Nikon fixes their USB implementation in a future firmware 1.11 ? Would this cause problems ?

I think only "known-to-be-bad" firmware should be included.

Revision history for this message
Ivan Panchenko (wao-mail) wrote :

I think that Nikon most probably will not fix the USB implementation soon, because it works excellently with their windows drivers. There is no reason for Nikon to fix it. "While it works, don't touch it".

Is it possible to make the kernel automatically detect if this known bug is fixed or not?

Could such strategy of automatic bugfix applicability testing is reasonable?
Let the software itself check when Nikon and others fix their bugs, why should people think of it any more!

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

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.

Revision history for this message
Victor Osadci (victor-os) wrote :

Works with Intrepid Alpha5.

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

Thanks for the update, we'll go ahead and close this.

Changed in linux:
status: New → Fix Released
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.