[sane-devel] Microtek Scanmaker 35t+ Error during device I/O

2006-06-13 Thread Matt Henley
I get the exact same error.  If you find out anything, please let me know.
I used the scanner under sane some 5 years ago or so and the
author/maintainer of the microtek backend was very helpful in solving the
issues I had with it.  I have not been able to get in contact with him
lately (its been several months since trying due to travel).

Matt Henley
nwm...@gmail.com


On 6/4/06, James Tuttle jwtut...@gmail.com wrote:

 Hi, everyone.

 I am trying to get my Microtek Scanmaker 35t+ SCSI slide scanner
 working on my Ubuntu box, and I'm not having any luck. In particular,
 everything seems to be working right, but when I try to scan, I get a
 Error during device I/O error and then everything just stops. I'm
 hoping somebody out there can help me.

 I don't know what information to provide so I'll start with the
 basics: machine is a P4 running Kubuntu (Ubunutu+KDE) Breezy, with an
 OrangeMicro Grappler 906F SCSI card. The card works fine for other
 applications; I have a tape changer/drive connected through it which
 is great.

 Running a cat /proc/scsi/scsi on the system shows this about the
 scanner:

 Host: scsi0 Channel: 00 Id: 05 Lun: 00
Vendor: MICROTEK Model: ScanMaker 35t+   Rev: 1.40
Type:   Scanner  ANSI SCSI revision: 01 CCS

 I have modprobe sg being run as part of my bootmisc script, and the
 scanner is /dev/sg2 (sg0 and sg1 belong to the tape drive).

 scanimage -L doesn't produce any errors. I will append its output to
 the bottom of the message, but at least to my untrained eye there
 didn't seem to be anything amiss.

 The problem is when I try to actually use the scanner via scanimage
 or xsane. The output it gives me is basically the same stuff as
 scanimage -L, but then followed by its actual attempts to scan, which
 fail:

 [microtek] sane_start...
 [microtek] sane_get_parameters...
 [microtek] sane_get_parameters:  regular 1-pass color
 [microtek] sane_get_parameters:  res_code = 5 ( 5)
 [microtek] bright_r of 0 set to 0x0
 [microtek] sane_get_parameters:  dots_per_mm:  3.937008
 [microtek] sane_get_parameters:  units_per_mm:  76.771654
 [microtek] WIDTHPIX:  before exp: 136
 [microtek] sane_get_parameters:  lines: 137  ppl: 136  bpl: 408
 [microtek] .wait_ready 5...
 [microtek] finagle_precal...
 [microtek] .scanning_frame...
 [microtek] .scanning_frame:  in- 0,0  2686,2686
 [microtek] .scanning_frame: out- 0,0  2686,2686
 [microtek] .accessory...
 [microtek] .download_gamma...
 [microtek] .download_gamma:  1024 entries of 2 bytes, max 255
 [microtek] .download_gamma: by default
 [microtek] end_scan...
 scanimage: sane_start: Error during device I/O
 [microtek] sane_cancel...
 [microtek] end_scan...
 [microtek] sane_close...
 [microtek] sane_exit...
 [microtek] sane_exit:  MICROTEK says goodbye.

 That's the most I can get it to do. Running xsane does the same thing
 but gives me the error in a dialog instead of on the console. I've
 tried playing around with the file permissions on /dev/sg2 and /dev/
 scanner, checking the config files, running it as root ... I can't
 get it to do anything more. Since this scanner allegedly works with
 Sane, I'm hoping maybe someone can shed some light on the problem?

 Thanks very much in advance!

 -James Tuttle
 jwtut...@gmail.com


 Following is the complete output of scanimage -T, with maximum
 debugging verbosity:
 [sanei_debug] Setting debug level of microtek to 128.
 [microtek] sane_init:  MICROTEK says hello! (v0.13.1)
 [microtek] sane_init:  config- # Uncomment following line to disable
 real calibration routines...
 [microtek] sane_init:  config- #norealcal
 [microtek] sane_init:  config- # Uncomment following line to disable
 clever precalibration routines...
 [microtek] sane_init:  config- #noprecal
 [microtek] sane_init:  config- #   Using norealcal will revert
 backend to pre-0.11.0 calibration code.
 [microtek] sane_init:  config- scsi * * Scanner
 [microtek] attach_scanner:  /dev/sg2
 [microtek] attach_scanner:  opening /dev/sg2
 [microtek] attach_scanner:  sending INQUIRY
 [microtek] id_microtek...
 [microtek] parse_inquiry...
 [microtek] parse_inquiry:  Not an E6 -- pretend recal cannot be
 disabled.
 [microtek] dump_inquiry...
 [microtek]  === SANE/Microtek backend v0.13.1 ===
 [microtek] == Scanner Inquiry Block mm
 [microtek] 06 31 19 01 5b 00 00 00 4d 49 43 52 4f 54 45 4b
 [microtek] 53 63 61 6e 4d 61 6b 65 72 20 33 35 74 2b 20 20
 [microtek] 31 2e 34 30 53 43 53 49 20 46 2f 57 56 33 2e 34
 [microtek] 20 43 54 4c 35 33 38 30 03 ef 8c c2 80 ec 62 23
 [microtek] 01 03 23 01 00 83 00 01 0e 0e 01 05 00 00 00 00
 [microtek] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff
 [microtek] == Scanner Inquiry Report ==
 [microtek] = Scanner ID...
 [microtek] Device Type Code: 0x06
 [microtek] Model Code: 0x62
 [microtek] Vendor Name: 'MICROTEK'   Model Name: 'ScanMaker 35t+  '
 [microtek] Vendor Specific String: 'SCSI F/WV3.4 CTL5380'
 [microtek] Firmware Rev: '1.40'
 

[sane-devel] Microtek Scanmaker 35t+ Error during device I/O

2006-06-05 Thread James Tuttle
Hi, everyone.

I am trying to get my Microtek Scanmaker 35t+ SCSI slide scanner  
working on my Ubuntu box, and I'm not having any luck. In particular,  
everything seems to be working right, but when I try to scan, I get a  
Error during device I/O error and then everything just stops. I'm  
hoping somebody out there can help me.

I don't know what information to provide so I'll start with the  
basics: machine is a P4 running Kubuntu (Ubunutu+KDE) Breezy, with an  
OrangeMicro Grappler 906F SCSI card. The card works fine for other  
applications; I have a tape changer/drive connected through it which  
is great.

Running a cat /proc/scsi/scsi on the system shows this about the  
scanner:

Host: scsi0 Channel: 00 Id: 05 Lun: 00
   Vendor: MICROTEK Model: ScanMaker 35t+   Rev: 1.40
   Type:   Scanner  ANSI SCSI revision: 01 CCS

I have modprobe sg being run as part of my bootmisc script, and the  
scanner is /dev/sg2 (sg0 and sg1 belong to the tape drive).

scanimage -L doesn't produce any errors. I will append its output to  
the bottom of the message, but at least to my untrained eye there  
didn't seem to be anything amiss.

The problem is when I try to actually use the scanner via scanimage  
or xsane. The output it gives me is basically the same stuff as  
scanimage -L, but then followed by its actual attempts to scan, which  
fail:

[microtek] sane_start...
[microtek] sane_get_parameters...
[microtek] sane_get_parameters:  regular 1-pass color
[microtek] sane_get_parameters:  res_code = 5 ( 5)
[microtek] bright_r of 0 set to 0x0
[microtek] sane_get_parameters:  dots_per_mm:  3.937008
[microtek] sane_get_parameters:  units_per_mm:  76.771654
[microtek] WIDTHPIX:  before exp: 136
[microtek] sane_get_parameters:  lines: 137  ppl: 136  bpl: 408
[microtek] .wait_ready 5...
[microtek] finagle_precal...
[microtek] .scanning_frame...
[microtek] .scanning_frame:  in- 0,0  2686,2686
[microtek] .scanning_frame: out- 0,0  2686,2686
[microtek] .accessory...
[microtek] .download_gamma...
[microtek] .download_gamma:  1024 entries of 2 bytes, max 255
[microtek] .download_gamma: by default
[microtek] end_scan...
scanimage: sane_start: Error during device I/O
[microtek] sane_cancel...
[microtek] end_scan...
[microtek] sane_close...
[microtek] sane_exit...
[microtek] sane_exit:  MICROTEK says goodbye.

That's the most I can get it to do. Running xsane does the same thing  
but gives me the error in a dialog instead of on the console. I've  
tried playing around with the file permissions on /dev/sg2 and /dev/ 
scanner, checking the config files, running it as root ... I can't  
get it to do anything more. Since this scanner allegedly works with  
Sane, I'm hoping maybe someone can shed some light on the problem?

Thanks very much in advance!

-James Tuttle
jwtut...@gmail.com


Following is the complete output of scanimage -T, with maximum  
debugging verbosity:
[sanei_debug] Setting debug level of microtek to 128.
[microtek] sane_init:  MICROTEK says hello! (v0.13.1)
[microtek] sane_init:  config- # Uncomment following line to disable  
real calibration routines...
[microtek] sane_init:  config- #norealcal
[microtek] sane_init:  config- # Uncomment following line to disable  
clever precalibration routines...
[microtek] sane_init:  config- #noprecal
[microtek] sane_init:  config- #   Using norealcal will revert  
backend to pre-0.11.0 calibration code.
[microtek] sane_init:  config- scsi * * Scanner
[microtek] attach_scanner:  /dev/sg2
[microtek] attach_scanner:  opening /dev/sg2
[microtek] attach_scanner:  sending INQUIRY
[microtek] id_microtek...
[microtek] parse_inquiry...
[microtek] parse_inquiry:  Not an E6 -- pretend recal cannot be  
disabled.
[microtek] dump_inquiry...
[microtek]  === SANE/Microtek backend v0.13.1 ===
[microtek] == Scanner Inquiry Block mm
[microtek] 06 31 19 01 5b 00 00 00 4d 49 43 52 4f 54 45 4b
[microtek] 53 63 61 6e 4d 61 6b 65 72 20 33 35 74 2b 20 20
[microtek] 31 2e 34 30 53 43 53 49 20 46 2f 57 56 33 2e 34
[microtek] 20 43 54 4c 35 33 38 30 03 ef 8c c2 80 ec 62 23
[microtek] 01 03 23 01 00 83 00 01 0e 0e 01 05 00 00 00 00
[microtek] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff
[microtek] == Scanner Inquiry Report ==
[microtek] = Scanner ID...
[microtek] Device Type Code: 0x06
[microtek] Model Code: 0x62
[microtek] Vendor Name: 'MICROTEK'   Model Name: 'ScanMaker 35t+  '
[microtek] Vendor Specific String: 'SCSI F/WV3.4 CTL5380'
[microtek] Firmware Rev: '1.40'
[microtek] SCSI F/W version: 3.1 Scanner F/W version: 1.9
[microtek] Response data format: 0x01
[microtek] = Imaging Capabilities...
[microtek] Modes:  Lineart Halftone Gray Color (X-msv) (OnePass)  
(Negative)
[microtek] Resolution Step Sizes: 1% 5%Expanded Resolution  
Support? yes
[microtek] Supported Bits Per Sample: 4 8
[microtek] Max. document size code: 0x80
[microtek] Max. document size:  2686 x 2686 pixels
[microtek] Frame units:  pixels  1/8's