The only additional info I've been able to get is by running 'lsusb'. It lists the USB Flash drive that usbcore fails to probe correctly.
Here is the output from 'lsusb':
Bus 004 Device 004: ID 08ec:0010 M-Systems Flash Disk Pioneers DiskOnKey Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 003: ID 03f0:1e11 Hewlett-Packard Bus 001 Device 002: ID 0409:0058 NEC Corp. HighSpeed Hub Bus 001 Device 001: ID 0000:0000
tom
------------------------------------ * From: TGS <spam tachegroup com>
Same exact problem here.
I am able to use some USB Flash drives without issue, but some fail. The failures lock up the whole mount subsystem capability, and the only way to fix it is to restart. My errors are just like the below. Is there a way to gather detailed information for the failed devices?
On Mon, 2004-08-23 at 22:31, t l wrote:
The only additional info I've been able to get is by running 'lsusb'. It lists the USB Flash drive that usbcore fails to probe correctly.
Here is the output from 'lsusb':
Bus 004 Device 004: ID 08ec:0010 M-Systems Flash Disk Pioneers DiskOnKey Bus 004 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 001 Device 003: ID 03f0:1e11 Hewlett-Packard Bus 001 Device 002: ID 0409:0058 NEC Corp. HighSpeed Hub Bus 001 Device 001: ID 0000:0000
tom
- From: TGS <spam tachegroup com>
Same exact problem here.
I am able to use some USB Flash drives without issue, but some fail. The failures lock up the whole mount subsystem capability, and the only way to fix it is to restart. My errors are just like the below. Is there a way to gather detailed information for the failed devices?
Tom,
Both of my thumb drives appear as /dev/sda and work perfectly. Other folks have reported their thumb drives appear as /dev/sda1. And there are some truly evil thumb drives that require Windows security drivers to access them. Has that possibility been ruled out?
-- Doc Robert G. (Doc) Savage, BSE(EE), CISSP, RHCE | Fairview Heights, IL Fedora Core 1 kernel 2.4.22-1.2199.nptl on P-III/M IBM Thinkpad A22p "Perfection is the enemy of good enough." -- Admiral of the Fleet Sergei G. Gorshkov
On Tue, 24 Aug 2004 16:08, "Robert G. (Doc) Savage" dsavage@peaknet.net wrote:
Both of my thumb drives appear as /dev/sda and work perfectly. Other folks have reported their thumb drives appear as /dev/sda1. And there are some truly evil thumb drives that require Windows security drivers to access them. Has that possibility been ruled out?
Partitioning a flash disk is optional. If you run mkfs on /dev/sda (thus removing /dev/sda1) then you will get an extra 30K of data storage. Doing this may make it more difficult to access the device from other OSs, and makes it more difficult to make the device bootable (I couldn't get grub to install after making a file system on /dev/sda and had to go back to /dev/sda1).
Well...,
The DRIVE should show up as /dev/sda, the data partition should usually be /dev/sda1. Unfortunately my [sony] memory stick seems not to work under FC2 at least, but it doesn't cause hanging problems, it just doesn't work at all.
--
thanks, noah silva
Tom,
Both of my thumb drives appear as /dev/sda and work perfectly. Other folks have reported their thumb drives appear as /dev/sda1. And there are some truly evil thumb drives that require Windows security drivers to access them. Has that possibility been ruled out?
-- Doc Robert G. (Doc) Savage, BSE(EE), CISSP, RHCE | Fairview Heights, IL Fedora Core 1 kernel 2.4.22-1.2199.nptl on P-III/M IBM Thinkpad A22p "Perfection is the enemy of good enough." -- Admiral of the Fleet Sergei G. Gorshkov
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-test-list