USB quirks

[Dorian Büttner]

Ralph Zitz schrieb:
> Ralph Zitz wrote:
>> Hello,
>> How does one know which quirks to add? At the moment I'm getting the 
>> following messages when attaching my device:
>>
>> ugen4.2: <vendor 0x0781> at 
>> usbus4                                                                                                
>>
>> umass0: <vendor 0x0781 product 0x5406, class 0/0, rev 2.00/2.00, addr 
>> 2> on usbus4
>> umass0:  SCSI over Bulk-Only; quirks = 0x0000
>> umass0:3:0:-1: Attached to scbus3
>> (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
>> (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
>> (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition
>> (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:3a,0
>> (probe0:umass-sim0:0:0:0): Medium not present
>> (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data)
>> da0 at umass-sim0 bus 0 target 0 lun 0
>> da0: <SanDisk Cruzer 7.01> Removable Direct Access SCSI-0 device
>> da0: 40.000MB/s transfers
>> da0: 15286MB (31306239 512 byte sectors: 255H 63S/T 1948C)
>> xptioctl: pass driver is not in the kernel
>> xptioctl: put "device pass" in your kernel config file
>> (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
>> (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
>> (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
>> (probe0:umass-sim0:0:0:1): UNIT ATTENTION asc:29,0
>> (probe0:umass-sim0:0:0:1): Power on, reset, or bus device reset occurred
>> (probe0:umass-sim0:0:0:1): Retrying Command (per Sense Data)
>> (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0
>> (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error
>> (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition
>> (probe0:umass-sim0:0:0:1): NOT READY asc:3a,0
>> (probe0:umass-sim0:0:0:1): Medium not present
>> (probe0:umass-sim0:0:0:1): Unretryable error
>> cd1 at umass-sim0 bus 0 target 0 lun 1
>> cd1: <SanDisk Cruzer 7.01> Removable CD-ROM SCSI-0 device
>> cd1: 40.000MB/s transfers
>> cd1: cd present [49151 x 2048 byte records]
>> GEOM: da0: media size does not match label.
>>
>> The usbstick was formatted with fat32. In /dev I have da0 and da0a 
>> listed, yet neither can be mounted:
>>
>> sudo mount_msdosfs /dev/da0a /home/ralph/mnt
>> mount_msdosfs: /dev/da0a: Invalid argument
>>
>> sudo mount_msdosfs /dev/da0 /home/ralph/mnt
>> mount_msdosfs: /dev/da0: Invalid argument
>>
>> I also don't understand the message about the pass device not being 
>> in the kernel conf - it is.
>>
>> Any help would be greatly appreciated.
>>
>> Regards,
>> Ralph.
>> _______________________________________________
>> freebsd-usb at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-usb
>> To unsubscribe, send any mail to "freebsd-usb-unsubscribe at freebsd.org"
> I forgot to mention:
> uname -a:
> FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #17 r196849: Sat Sep  5 
> 09:35:27 CEST 2009  amd64
> _______________________________________________
> freebsd-usb at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-usb
> To unsubscribe, send any mail to "freebsd-usb-unsubscribe at freebsd.org"
How about that part:
xptioctl: pass driver is not in the kernel
xptioctl: put "device pass" in your kernel config file

Don't know how this is handled on neither 9-current nor on amd64, but I 
guess this should be solved first.