Roger, Thanks to Bernd Schroeder and Karsten Festag, the Microtek Scanmaker X6usb is on the supported list at: http://www.mostang.com/sane/sane-backends.html
$xscanimage microtek2:/dev/sg1 detects and will allow me to conduct one or two scans, but dies upon me changing the resolution and color depth. I have to admit that I just found the man page at: http://www.mostang.com/sane/man/sane-microtek2.5.html After reading it, I see that I should create log files and send them to Karsten. I appreciate your help Roger. This does look like a backend problem and I will start working with Karsten to improve it. --John On Tue, 2002-05-28 at 23:46, Roger wrote: > just an fyi, dunno if this model is support under sane (but my astra > umax 2200 scsi/usb is). > > try either xscanimage or using scanimage manully: > > xscanimage umax:/dev/usb/scanner0 > scanimage umax:/dev/usb/scanner0 > > or yours would be something like: > xscanimage mustek:/dev/usb/scanner0 > > On Tue, 2002-05-28 at 21:34, John Yarger wrote: > > I wanted to pass on my configuration experiences regarding scannerdrake > > to the developer of the project to aid with the auto-detection. I have > > the Microtek ScanMaker X6USB now running with sane 1.0.7 and xsane 0.86 > > on ML 8.2. Below is my configuration saga... > > > > After running "scannerdrake" as root, and choosing "Microtek ScanMaker > > X6USB", scannerdrake exits. I then attempted to run xsane as a normal > > user. xsane displays a license message when first run. I chose "Accept", > > at which point xsane displays a "scanning for devices" message. After a > > few seconds, the message "xsane: no devices available" is displayed. > > > > The followings command shows that it is detected on the usb hub: > > # cat /proc/bus/usb/devices > > T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 > > B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 > > D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > > P: Vendor=0000 ProdID=0000 Rev= 0.00 > > S: Product=USB UHCI Root Hub > > S: SerialNumber=d400 > > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms > > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 10 Spd=12 MxCh= 0 > > D: Ver= 1.00 Cls=ff(vend.) Sub=03 Prot=00 MxPS=64 #Cfgs= 1 > > P: Vendor=05da ProdID=0099 Rev= 0.00 > > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > > I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=microtekX6 > > E: Ad=01(O) Atr=02(Bulk) MxPS= 32 Ivl= 0ms > > E: Ad=82(I) Atr=02(Bulk) MxPS= 32 Ivl= 0ms > > E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl= 0ms > > > > The following command checks all of the common scanner locations to find > > an open: > > $sane-find-scanner -v > > ... > > sane-find-scanner: checking /dev/sg0... open ok > > sane-find-scanner: found SCSI CD-drive "HP CD-Writer+ 7200 3.01" at > > device /dev/sg0sane-find-scanner: checking /dev/sg1... open ok > > sane-find-scanner: found SCSI scanner " Scanner 636A4 1.40" at device > > /dev/sg1 > > ... > > > > After discovering that the scanner uses a SCSI interface underneath, > > this command shows some more information about the scanner: > > $ cat /proc/scsi/scsi > > Attached devices: > > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > > Vendor: HP Model: CD-Writer+ 7200 Rev: 3.01 > > Type: CD-ROM ANSI SCSI revision: 02 > > Host: scsi1 Channel: 00 Id: 00 Lun: 00 > > Vendor: Model: Scanner 636A4 Rev: 1.40 > > Type: Scanner ANSI SCSI revision: 02 > > > > In order to tell xsane what backend driver to use as well as which > > device, issue this command: > > $xsane microtek2:/dev/sg1 > > > > Or to get xsane to work from the program menu entry, I put the following > > entries into /etc/sane.d/microtek2.conf: > > /dev/sg1 > > option connect-device > > > > Most everything works when I use the default settings. When I vary some > > options, such as adjust the resolution or color depth higher, I get the > > following error: "Failed to start scanner: Error during device I/O." The > > next attempt at producing a scan results in a segmentation fault. I was > > able to vary these settings once or twice successfully, but it usually > > resulted in the error. > > > > If I can be of any assistance in the effort to get this working better, > > please let me know. > > > > --John > > > > > -- > Roger > ----- > Verify my pgp/gnupg signature on my HomePage: > http://www.alltel.net/~rogerx/about/index.html
