On Sun, 6 Feb 2005, Jason Grant wrote: > On Sat, 2005-02-05 at 10:21 -0500, Alan Stern wrote: > > On Sat, 5 Feb 2005, Jason Grant wrote: > > > > The extract from your system log doesn't show anything going wrong. Could > > it be that your flash drive simply has an empty partition table, hence no > > partition 1? What does fdisk -l /dev/sdX show? > > > > 'fdisk -l /dev/sdc' returns nothing. 'fdisk /dev/sdc' returns 'Unable > to read /dev/sdc'. > > The log doesn't show anything wrong, however it also doesn't include a > lot of information that is produced when my working drive is plugged in. > I'm guessing that the full sequence as initiated by hotplug is bailing > somewhere, but I don't know how to debug it. For example, if my device > was not supported, or if there are partitioning issues, can I turn on > extra logging to see this?
Yes you can. Go into the kernel configuration and turn on the usb-storage verbose debugging option (CONFIG_USB_STORAGE_DEBUG). This will cause the driver to send lots of additional messages to the kernel log. (You may need to edit /etc/syslog.conf to tell syslogd not to ignore debug-level messages from the kernel. Or it may just be easier to get the kernel log from dmesg.) > The log info from my good flash drive is shown below - note how the bad > drive doesn't include the information like '...Write Protect..." and > "... sdb: sdb1 ...", so I think the logging is indicative that something > *is* going wrong. Yes, at least some of that information should have been there. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
