On Wed, 20 Apr 2005, Avuton Olrich wrote: > On 4/20/05, Alan Stern <[EMAIL PROTECTED]> wrote: > > On Tue, 19 Apr 2005, Avuton Olrich wrote: > > > That "Medium not present" means the reader is saying there's no card > > inserted. The messages you sent are what you get when you unplug and > > replug the USB cable with no card present. What messages do you get if > > you insert a card and try to mount it? > > And you would think that there's no medium there, but I assure you > there is. I assure you also that this used to work in an earlier > version of linux 2.6 (although I can't test them now due to my > reliance on reiser4). > > Also, there is no partition to mount, so I can't try to mount it :(.
That _is_ a problem! :-) Normally hald would cause the partition to be created. Try doing this: Plug in the USB cable with the reader empty. After about 10 seconds insert a card in the reader. Then start hald and let it run for only a few seconds, and see what messages show up in the log. What _should_ happen is that when you first plug in the reader you get a couple of "Medium not present" errors. Then when hald starts those errors should no longer occur, so the partition should be created as you would expect. > To make things a bit more interesting, I inserted a different media in > another port in this reader (a CF card) and I get something totally > different: > > scsi9 : SCSI emulation for USB Mass Storage devices > usb-storage: device found at 12 > usb-storage: waiting for device to settle before scanning > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Command INQUIRY (6 bytes) > usb-storage: 12 00 00 00 24 00 > usb-storage: Bulk Command S 0x43425355 T 0x3186 L 36 F 128 Trg 0 LUN 0 CL 6 > usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes > usb-storage: Status code 0; transferred 31/31 > usb-storage: -- transfer complete > usb-storage: Bulk command transfer result=0 > usb-storage: usb_stor_bulk_transfer_buf: xfer 36 bytes > usb-storage: Status code 0; transferred 36/36 > usb-storage: -- transfer complete > usb-storage: Bulk data transfer result 0x0 > usb-storage: Attempting to get CSW... > usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes > usb-storage: Status code 0; transferred 13/13 > usb-storage: -- transfer complete > usb-storage: Bulk status result = 0 > usb-storage: Bulk Status S 0x53425355 T 0x3186 R 0 Stat 0x0 > usb-storage: scsi cmd done, result=0x0 > usb-storage: *** thread sleeping. > Vendor: Generic Model: STORAGE DEVICE Rev: 1.06 > Type: Direct-Access ANSI SCSI revision: 00 > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Command TEST_UNIT_READY (6 bytes) > usb-storage: 00 00 00 00 00 00 > usb-storage: Bulk Command S 0x43425355 T 0x3187 L 0 F 0 Trg 0 LUN 0 CL 6 > usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes > usb-storage: Status code 0; transferred 31/31 > usb-storage: -- transfer complete > usb-storage: Bulk command transfer result=0 > usb-storage: Attempting to get CSW... > usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes > usb-storage: Status code -32; transferred 0/13 > usb-storage: clearing endpoint halt for pipe 0xc0008c80 > usb-storage: usb_stor_control_msg: rq=01 rqtype=02 value=0000 index=81 len=0 > usb-storage: usb_stor_clear_halt: result = 0 > usb-storage: Attempting to get CSW (2nd try)... > usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes Is this totally different? It looks just the same as what you sent me before. > Oh yea, that error message before (with my xd card) was with hald, and > this is without hald with only my xd card: > > Attached scsi removable disk sdc at scsi7, channel 0, id 0, lun 0 > Attached scsi generic sg2 at scsi7, channel 0, id 0, lun 0, type 0 > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad LUN (0:1) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (1:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (2:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (3:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (4:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (5:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (6:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: queuecommand called > usb-storage: *** thread awakened. > usb-storage: Bad target number (7:0) > usb-storage: scsi cmd done, result=0x40000 > usb-storage: *** thread sleeping. > usb-storage: device scan complete This part also looks the same. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: New Crystal Reports XI. Version 11 adds new functionality designed to reduce time involved in creating, integrating, and deploying reporting solutions. Free runtime info, new features, or free trial, at: http://www.businessobjects.com/devxi/728 _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
