On Sun, Apr 23, 2006 at 12:21:42AM +0800, Stephen Liu wrote: > Hi Charles and folks, > > Tks for your advice. > > > It might be simpler to run dmesg after inserting the device, > > # dmesg | grep usb > usbcore: registered new driver usbfs > usbcore: registered new driver hub > usbcore: registered new driver libusual > usbcore: registered new driver hiddev > usbcore: registered new driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts > [<ffffffff802a8d8c>] (usb_hcd_irq+0x0/0x50) > usb usb1: configuration #1 chosen from 1 choice > usb usb2: configuration #1 chosen from 1 choice > usb 2-2: new low speed USB device using ohci_hcd and address 2 > usb 2-2: configuration #1 chosen from 1 choice > input: USB HID v1.11 Mouse [Microsoft Microsoft USB Wireless Mouse] on > usb-0000:00:0b.0-2 Well, drat. The device may be mis-identifying itself as a rodent. This could be due to an error in the device, or a bug in the code that reads the device's ID. It is also possible that (since there are no time stamps in dmesg) this is an old message from an actual rodent. 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 > > # fdisk -l > > Disk /dev/sda: 80.0 GB, 80026361856 bytes > 255 heads, 63 sectors/track, 9729 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes Right. fdisk isn't going to help until we get the identification issue squared away. Here's what I see in my log (/var/log/messages) when I insert a thumb drive in my FC5 32 bit laptop. Apr 22 10:46:06 dragon kernel: usb 4-3: new high speed USB device using ehci_hcd and address 3 Apr 22 10:46:07 dragon kernel: usb 4-3: configuration #1 chosen from 1 choice Apr 22 10:46:07 dragon kernel: SCSI subsystem initialized Apr 22 10:46:07 dragon kernel: Initializing USB Mass Storage driver... Apr 22 10:46:07 dragon kernel: scsi0 : SCSI emulation for USB Mass Storage devices Apr 22 10:46:07 dragon kernel: usbcore: registered new driver usb-storage Apr 22 10:46:07 dragon kernel: USB Mass Storage support registered. Apr 22 10:46:12 dragon kernel: Vendor: Kingston Model: DataTraveler 2.0 Rev: 4.10 Apr 22 10:46:12 dragon kernel: Type: Direct-Access ANSI SCSI revision: 02 Apr 22 10:46:12 dragon kernel: 0:0:0:0: Attached scsi generic sg0 type 0 Apr 22 10:46:12 dragon kernel: SCSI device sda: 503808 512-byte hdwr sectors (258 MB) Apr 22 10:46:12 dragon kernel: sda: Write Protect is off Apr 22 10:46:12 dragon kernel: sda: assuming drive cache: write through Apr 22 10:46:12 dragon kernel: SCSI device sda: 503808 512-byte hdwr sectors (258 MB) Apr 22 10:46:12 dragon kernel: sda: Write Protect is off Apr 22 10:46:12 dragon kernel: sda: assuming drive cache: write through Apr 22 10:46:12 dragon kernel: sda: sda1 Apr 22 10:46:12 dragon kernel: sd 0:0:0:0: Attached scsi removable disk sda Notice that the penultimate line tells you the device has been set up as sda1. -- 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:
pgpF6wKPxhj0l.pgp
Description: PGP signature
