Hi,
Alan Stern wrote:
From things I've seen in the past, I'll guess that the device reports "No medium present" until it finishes initializing, which might require a few seconds. Since the usb-storage and other drivers try probing the device right away, they are forced to assume that there are no partitions and no data -- until something tells them to take a second look.
It's not clear what the best solution to this is. But here's something you can try that might confirm my guess. Make sure all hotplug support is turned off so that drivers aren't loaded automatically. Make sure usb-storage isn't loaded and plug in the device. Then maybe 30 seconds later modprobe usb-storage and see if it detects the disk partitions.
That would make sense. And yes - you are right, if given time to warm up, the device will report sda1 when you load the usb-storage module. I can think of a few userspace workarounds to get around this, are there any acceptable ways you can think of doing this in the kernel?
I can get you the complete logs if required.
Daniel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
