On Sun, Apr 23, 2006 at 10:31:49PM +0800, Stephen Liu wrote: > Hi Charles, > > I tested the USB thumb drives on a FC3 32bit box. I haven't got FC5 > 32bit running. > > > AVIXE 1G > ======== > # ps -ef | grep usb > root 4555 1 0 21:39 ? 00:00:00 [usb-storage] > root 4807 4772 0 21:48 pts/3 00:00:00 grep usb > > > # dmesg | grep usb > usbcore: registered new driver usbfs > usbcore: registered new driver hub > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.01:USB HID core driver > SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts > usb 4-1: new high speed USB device using ehci_hcd and address 2 > usb-storage: device found at 2 > usb-storage: waiting for device to settle before scanning > usbcore: registered new driver usb-storage > usb-storage: device scan complete > * * * END * * * Curious, either it didn't show the plug-in information, like what I showed you recently, or you didn't copy it in. No big deal, as the fdisk results show what we need. > > > # fdisk -l > Disk /dev/sda: 1007 MB, 1007419392 bytes > 31 heads, 62 sectors/track, 1023 cylinders > Units = cylinders of 1922 * 512 = 984064 bytes > > Device Boot Start End Blocks Id System > /dev/sda1 1 204 196013 6 FAT16 > /dev/sda2 205 1018 782254 83 Linux > /dev/sda3 1019 1023 4805 83 Linux > * * * End * * * Obviously it's there. > > > > AVIXE 512M > ========== > > # ps -ef | grep usb > root 4946 1 0 21:49 ? 00:00:00 [usb-storage] > root 5101 4772 0 21:49 pts/3 00:00:00 grep usb > > > # dmesg | grep usb > usbcore: registered new driver usbfs > usbcore: registered new driver hub > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.01:USB HID core driver > SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts > usb 4-1: new high speed USB device using ehci_hcd and address 2 > usb-storage: device found at 2 > usb-storage: waiting for device to settle before scanning > usbcore: registered new driver usb-storage > usb-storage: device scan complete > usb 4-1: USB disconnect, address 2 > usb 4-1: new high speed USB device using ehci_hcd and address 3 > usb-storage: device found at 3 > usb-storage: waiting for device to settle before scanning > usb-storage: device scan complete > * * * End * * * > > > # fdisk -l > > > Disk /dev/sda: 503 MB, 503709696 bytes > 64 heads, 32 sectors/track, 480 cylinders > Units = cylinders of 2048 * 512 = 1048576 bytes > > Device Boot Start End Blocks Id System > /dev/sda1 * 1 287 293872 6 FAT16 > /dev/sda2 288 250000 255706112 83 Linux > Partition 2 has different physical/logical endings: > phys=(1023, 63, 32) logical=(249999, 63, 32) > * * * End * * * Again, obviously there. > > > > > Have you got a 32 bit machine you can look at the device's ID with > > lsusb and compare that to the results on your 64 bit machine? What > > you > > want is the ID column, something like 0c76:0005 in: > > > > Bus 004 Device 003: ID 0c76:0005 JMTek, LLC. USBdisk > > 1G > === > # lsusb > Bus 006 Device 001: ID 0000:0000 > Bus 005 Device 001: ID 0000:0000 > Bus 004 Device 004: ID 0457:0151 Silicon Integrated Systems Corp. > Bus 004 Device 001: ID 0000:0000 > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 > * * * End * * * > > > 512M > ==== > # lsusb > Bus 006 Device 001: ID 0000:0000 > Bus 005 Device 001: ID 0000:0000 > Bus 004 Device 005: ID 0457:0151 Silicon Integrated Systems Corp. > Bus 004 Device 001: ID 0000:0000 > Bus 003 Device 001: ID 0000:0000 > Bus 002 Device 001: ID 0000:0000 > Bus 001 Device 001: ID 0000:0000 > * * * End * * * > > Both seems the same. Right. The left hand value (0457) is the manufacturer's ID, which will be the same for all of the manufaturer's products. The right hand one (0151) is for the specific product. I think they should have changed it so their own manufacturing processes could tell them apart, but that doesn't affect us here. Anyway, the things are clearly working correctly under FC3. I've seem other USB devices work on one version of Linux but not another. So my guess is that there is a bug, either in FC5 or in FC5_64. It would help to have an FC5_32 machine to narrow things down. We'll see what lsusb reveals. > > > On FC5_64 box > # which lsusb > /usr/bin/which: no lsusb in > (/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin) > > Neither "yum search lsusb" found this package. Please advise which > package is needed? TIA Odd. "yum provides lsusb" got no hits. It should have returned "usbutils", which is the package you want. I wonder if that's a bug in yum? BTW, you could have gone to the FC3 box and run "rpm -qf $(which lsusb)" to get the package name, but you didn't know that. -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
Attachment:
pgp1zDNif8Xz7.pgp
Description: PGP signature
