New Kernel still bad

[Erich Zigler]

On Wed, August 1, 2007 7:29 am, Karl Larsen wrote:

> 	It was my guess that USB uses Firewire. I can be wrong. The device is a
> tiny sim in a plastic housing with a USB male plug.

Nope. USB and Firewire are two different devices types. If it was a
firewire device it would be plugged in to a Firewire card on your
computer.

> Here is dmesg:
> usb-storage: device found at 3
> usb-storage: waiting for device to settle before scanning
> usb-storage: device scan complete
> scsi 3:0:0:0: Direct-Access     Kingston DataTraveler 2.0 PMAP PQ: 0
> ANSI: 0 CCS
> sd 3:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
> sd 3:0:0:0: [sdg] Write Protect is off
> sd 3:0:0:0: [sdg] Mode Sense: 23 00 00 00
> sd 3:0:0:0: [sdg] Assuming drive cache: write through
> sd 3:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
> sd 3:0:0:0: [sdg] Write Protect is off
> sd 3:0:0:0: [sdg] Mode Sense: 23 00 00 00
> sd 3:0:0:0: [sdg] Assuming drive cache: write through
>   sdg: sdg1
> sd 3:0:0:0: [sdg] Attached SCSI removable disk
> sd 3:0:0:0: Attached scsi generic sg8 type 0
> usb 4-6: USB disconnect, address 3
> usb 4-6: new high speed USB device using ehci_hcd and address 4
> usb 4-6: configuration #1 chosen from 1 choice
> scsi4 : SCSI emulation for USB Mass Storage devices
> usb-storage: device found at 4
> usb-storage: waiting for device to settle before scanning
> usb-storage: device scan complete
> scsi 4:0:0:0: Direct-Access     Kingston DataTraveler 2.0 PMAP PQ: 0
> ANSI: 0 CCS
> sd 4:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
> sd 4:0:0:0: [sdg] Write Protect is off
> sd 4:0:0:0: [sdg] Mode Sense: 23 00 00 00
> sd 4:0:0:0: [sdg] Assuming drive cache: write through
> sd 4:0:0:0: [sdg] 4030464 512-byte hardware sectors (2064 MB)
> sd 4:0:0:0: [sdg] Write Protect is off
> sd 4:0:0:0: [sdg] Mode Sense: 23 00 00 00
> sd 4:0:0:0: [sdg] Assuming drive cache: write through
>   sdg: sdg1
> sd 4:0:0:0: [sdg] Attached SCSI removable disk
> sd 4:0:0:0: Attached scsi generic sg8 type 0
> [karl at k5di ~]$

Well the kernel is seeing the device. It seems others are seeing this same
behavior with their devices. I would fill out a bugzilla report.

Thanks,

Erich