Bug#731016: Can't mount external USB HD Asus AN300
Am 04.12.2013 15:07, schrieb Ben Hutchings:
Le mercredi, 4 décembre 2013, 11.01:14 Josua Dietze a écrit :
It's clear now that usb_modeswitch can't do anything here.
I don't see that at all. There could be some magic file on the virtual
CD-ROM that Windows already knows how to interpret. (I don't know what
the point of that would be!)
That is highly unlikely. After all, there are only two possibilities:
1. Windows accesses the main drive device in a generic (built-in) way. If this
included some sort of 'magic' file, then that way of access would be known -
if not documented - by now. It's not likely that the Asus drive would be the
only device where this special generic access method applied.
2. A special software is used for access or at least for initialisation before
using the main drive device. This has been ruled out by Ido's tests.
usb_modeswitch helps with devices that change their complete layout after
receiving a specific command. In most cases this involves a change of the USB
product ID, but there is *always* a change in interface layout and classes.
I can't see that with the Asus drive. The interfaces with their expected
device class seem to be there from the moment of plug-in.
That said, it would become clearer with a detailed "lsusb" listing. Some
interface details are visible in the udev monitoring output from the original
report, but not very concise.
Ido, can you run the following terminal command with the drive connected?
$ sudo lsusb -v -d 0b05:17b6
Then post the output in your reply, please.
(As a side note, I noticed that long lines of text are not wrapped on the bug
track page - is that intended?)
Reply to: