Re: USB (internally fixed) card reader questions

On Saturday 30 May 2009, Harald Schmalzbauer wrote:
> Hans Petter Selasky schrieb am 30.05.2009 12:03 (localtime):
> ...
>
> > If recompiling hald and checking that libusb is up to date,
> > see /usr/src/lib/libusb, does not solve your problem, then write me some
> > text about how to get going using usbconfig, and I will add it as a
> > workaround FAQ for USB flash cards.
>
> After updating to todays -current and all ports (including hal), I can
> again use the `true > /dev/da0` trick and with the second insertion of
> the card hal "exports" the media. That's same like with 7-stable before.
> But inserting a UFD leads to hal death.
> Here's what I get from dmesg:
> ugen3.3: <USB> at usbus3
> umass1: <USB Flash Disk, class 0/0, rev 2.00/2.00, addr 3> on usbus3
> umass1:  SCSI over Bulk-Only; quirks = 0x0000
> umass1:6:1:-1: Attached to scbus6
> xptioctl: pass driver is not in the kernel
> xptioctl: put "device pass" in your kernel config file
> (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
> (probe0:umass-sim1:1:0:0): CAM Status: SCSI Status Error
> (probe0:umass-sim1:1:0:0): SCSI Status: Check Condition
> (probe0:umass-sim1:1:0:0): UNIT ATTENTION asc:28,0
> (probe0:umass-sim1:1:0:0): Not ready to ready change, medium may have
> changed
> (probe0:umass-sim1:1:0:0): Retrying Command (per Sense Data)
> da4 at umass-sim1 bus 1 target 0 lun 0
> da4: <I-Stick2 IntelligentStick 2.00> Removable Direct Access SCSI-2 device
> da4: 40.000MB/s transfers
> da4: 249MB (511488 512 byte sectors: 64H 32S/T 249C)
> GEOM: da4: partition 1 does not start on a track boundary.
> GEOM: da4: partition 1 does not end on a track boundary.
> GEOM_LABEL: Label for provider da4s1 is msdosfs/BIOS-UFD.
>
> Before the UFS plugin I had some hald-addon-storage: /dev/da0 etc.
> These are all gone, just these left:
> 1084  ??  Ss     0:00,43 /usr/local/sbin/hald
>   1088  ??  I      0:00,04 hald-runner
>   1122  ??  I      0:00,01 hald-addon-mouse-sysmouse: /dev/ums0
> (hald-addon-mouse-sy)
>   1132  ??  I      0:00,01 hald-addon-mouse-sysmouse: /dev/ums1
> (hald-addon-mouse-sy)
>   1156  ??  S      0:00,04 hald-addon-storage: /dev/acd0
> (hald-addon-storage)
>   1158  ??  S      0:00,07 hald-addon-storage: /dev/acd1
> (hald-addon-storage)
>   1439  ??  S      0:00,01 hald-addon-storage: /dev/probe0
> (hald-addon-storage)
>
> Now I have some essential question:
> I know that inserting a Flash Card in a fixed USB card reader doesn't
> inform the kernel that there's a new media, so I have to issue a write
> request to get the GEOM notified. This is not easily fixable, as far as
> I remember some discussion at least one year ago.
> But after GEOM knows about the new labels, hal still doesn't catch them.
> First I have to pull out and reinsert the card.
> Is that fixable?

I think you have to ask some file system guys.

Usually I use:

cat /dev/null > /dev/daX

>
> Do I have to use `camcontrol eject` before removing flash cards from
> fixed readers?

Depends on the firmware in the reader. Usually not.

>
> Any hope for my UFD-hal problem?
> Especially the "xptioctl: put "device pass" in your kernel config file"
> error message seems very odd to me.

Did you try adding "device pass" to your kernel config?

--HPS