[sane-devel] problems with Fujitsu M3093DG with USB/SCSI

[m. allan noah]

that microtek usb to scsi adapter is a weird beast. it changes its usb 
interface based on whether it was plugged into the device or the host 
first. hence, those weird mass-storage devices it makes. try searching 
around for reviews of it online, some will surely mention the details.

i wont have a chance to look at your log file for awhile, not getting much 
sleep as it is, but i can say there was some discussion recently about the 
older fujitsu's needing the scsi buffer size set to something really huge, 
because the scanner did not like having to stop transmitting. this may 
explain your EOF patch?

i swear i am going to take a vacation here at some point, and work on some 
of this...

allan
sometime fujitsu backend maintainer

On Wed, 5 Oct 2005, Stefanie Tellex wrote:

> Hello,
>
> I have a Fujitsu M3093DG scanner connected via a Microtech USB-SCSI-DB25 
> cable to a Debian DNU/Linux testing system, with sane 1.0.16-2.
>
> scanimage seems to talk to the scanner to some degree: it returns reasonable 
> error messages when the ADF is jammed or when there's nothing in the feeder, 
> and it switches between the ADF and the document tray correctly when I pass 
> the --source option.
>
> However, when I run scanimage, it returns very quickly (well before the 
> scanner has stopped), and the image file is corrupt.  I tried both pnm and 
> tiff formats, and gimp couldn't load either one.  When I ran 
> sane-troubleshoot, the image was black once, and black with stripes once. 
> I've attached the logfile from running SANE_DEBUG_FUJITSU=255 scanimage 
> 1>image.pnm 2> logfile
>
> Another weird thing was the first time I plugged in the scanner, it got 
> attached to lots of scsi devices.  Here's the log from dmesg:
>
> usb 1-1: new full speed USB device using address 2
> SCSI subsystem initialized
> Initializing USB Mass Storage driver...
> usb-storage: This device (07af,0004,0100 S 06 P 50) has unneeded SubClass and 
> Protocol entries in unusual_devs.h
>  Please send a copy of this message to 
> <linux-usb-devel at lists.sourceforge.net>
> scsi0 : SCSI emulation for USB Mass Storage devices
> Vendor: FUJITSU   Model: M3093DGdim        Rev: 02
> Type:   Scanner                            ANSI SCSI revision: 02
> Vendor: FUJITSU   Model: M3093DGdim        Rev: 02
> Type:   Scanner                            ANSI SCSI revision: 02
> Vendor: FUJITSU   Model: M3093DGdim        Rev: 02
> Type:   Scanner                            ANSI SCSI revision: 02
> Vendor: FUJITSU   Model: M3093DGdim        Rev: 02
> Type:   Scanner                            ANSI SCSI revision: 02
> Attached scsi generic sg0 at scsi0, channel 0, id 1, lun 0,  type 6
> Attached scsi generic sg1 at scsi0, channel 0, id 2, lun 0,  type 6
> Attached scsi generic sg2 at scsi0, channel 0, id 3, lun 0,  type 6
> Attached scsi generic sg3 at scsi0, channel 0, id 4, lun 0,  type 6
> Vendor: FUJITSU   Model: M3093DGdim        Rev: 02
> Type:   Scanner                            ANSI SCSI revision: 02
> Attached scsi generic sg4 at scsi0, channel 0, id 5, lun 0,  type 6
> Vendor: FUJITSU   Model: M3093DGdim        Rev: 02
> Type:   Scanner                            ANSI SCSI revision: 02
> Attached scsi generic sg5 at scsi0, channel 0, id 6, lun 0,  type 6
> USB Mass Storage device found at 2
> usbcore: registered new driver usb-storage
> USB Mass Storage support registered.
>
>
> I played around with unplugging and replugging it in, and I changed the scsi 
> ID on the dial, and then it only made one /dev/sg* drive.   I plugged and 
> unplugged it a few more times and now it won't detect it at all.
>
> Thanks in advance for your help!
>
> Stefanie
>

-- 
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera