On Mon, 16 Feb 2009, Phil Dibowitz wrote: > On Mon, Feb 16, 2009 at 11:33:04AM -0500, Alan Stern wrote: > > On Mon, 16 Feb 2009, Phil Dibowitz wrote: > > > > > On Mon, Feb 16, 2009 at 10:55:52AM -0500, Alan Stern wrote: > > > > On Mon, 16 Feb 2009, Phil Dibowitz wrote: > > > > > > > > > Alan Stern wrote: > > > > > > Was this the device for which the manufacturer has made a firmware > > > > > > upgrade available? > > > > > > > > > > Nope. The hardware is different and they said that was not possible. > > > > > > > > By the way, have you taken a look at this bug report: > > > > > > > > http://bugzilla.kernel.org/show_bug.cgi?id=12559 > > > > > > > > It seems like the same kind of issue. > > > > > > No, that's the opposite issue. I removed the usb-storage blacklist (so it > > > *does* get seen as mass-storage). That bug is about something *not* getting > > > seen as mass-storage.... > > > > Then maybe you can add a comment to that bug report, explaining the > > situation and telling the user how to fix the problem. > > I would, but I don't know what the story is there. It seems completely > unrelated... > > Based on the users's bissect, it looks like a patch by the HW makers: > > Author: fangxiaozhi <huananhu@xxxxxxxxxx> Well, I seem to remember a reasonably lengthy thread about this, in which it turned out the best solution was to install the manufacturer's firmware upgrade. For example: https://lists.one-eyed-alien.net/pipermail/usb-storage/2008-December/004313.html But I could easily be mixing up two different sorts of device; I can't keep these things straight. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
