[sane-devel] sm3600 backend problem

2004-02-16 Thread Mattias Ellert
Hi!

I have been trying to solve a problem for a user with a Microtek 3600 
scanner on a Mac. The first error log he sent me looked like a libusb 
problem, and after looking through the libusb code I was able patch 
libusb to handle a change of usb configuration without loosing the claim 
of the interface. (The patch has been added to the libusb support system 
at sourceforge).

http://sourceforge.net/tracker/index.php?func=detailaid=897350group_id=1674atid=301674

With this fixed libusb library, it works better. It manages to claim the 
interface again after changing the configuration (this is where it 
failed without the patch):

usb_os_open: 05da:40b3
usb_claim_interface: called for interface 0
Interface 0 of device is 0x0
claim_interface: No interface found; selecting configuration
claim_interface: device has 1 configuration
claim_interface: configuration value is 1
claim_interface: Interface 0 of device is 0xf0b
claim_interface: Interface 0 of device from QueryInterface is 0x3049f0
usb_set_configuration: called for config 1
Interface 0 of device is 0xe9b
claim_interface: Interface 0 of device from QueryInterface is 0x304ae0

Then the following is repeated several times:

usb_bulk_read: ep addr = 0x82
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 1 number: 2
ep_to_pipeRef: pipeRef for ep address 0x82 found: 0x01
usb_bulk_read: endpoint=0x82 size=4096 timeout=2000 ms
read/write completed, result=0, size=4096
usb_bulk_read: ep addr = 0x82
Converting ep address to pipeRef.
ep_to_pipeRef: Pipe 1: DIR: 1 number: 2
ep_to_pipeRef: pipeRef for ep address 0x82 found: 0x01
usb_bulk_read: endpoint=0x82 size=1204 timeout=2000 ms
read/write completed, result=0, size=1204

with some lt1=n, lt2=n between them until it finally says lt3=0.

Then it repeats the above sequence 8 times more without any lt[1,2,3]=n 
statements.

This is (if I understand the backend code correctly) the scanner first 
positioning the scanner for the calibration and then doing the 
calibration step. Looking at the code the calibration requires reading 
5300 bytes 8 times.

Then it fails with:

scanimage: sane_start: Error during device I/O
[sm3600] cancel called...
[sm3600] closing scanner
usb_os_close: 05da:40b3
[sm3600] Error status: 9, Timeout while waiting for CTL

The complete log (with SANE_DEBUG_SM3600=255 SANE_DEBUG_SANEI_USB=255) 
can be found at:

http://www.ellert.se/twain-sane/debug/sm3600.log

Grepping for fork in the sm3600* files does not give any match, so it 
(at least at first sight) doesn't look like a fork problem.

The code for the sm3600 backend is not very easy to follow, so I really 
could do with some more input here.

Mattias

-- 


mattias.ell...@tsl.uu.se   tel: +46 18 471 32 58
http://www.tsl.uu.se/~ellert/  fax: +46 18 471 35 13





[sane-devel] epson perfection 1200 SCSI not scanning via TWAIN

2004-02-16 Thread Mattias Ellert
Michael C. Haller wrote:
 
 But I am not able to scan thru the TWAIN-Interface, i.e. 
 GraphicConverter or Adobe Photoshop CS. GraphicConverter does just 
 nothing and Photoshop says: there is no scanner.
 
 Please, help!
 
 Thx a lot.
 
 Michael.
 

Hi,

Version 0.5 of the TWAIN SANE Interface was released yesterday. Some 
incompatibility issues with a number of backends (including the epson 
backend) have been solved. Please let me know if the new version solves 
your problem, or at least let you come closer to a working solution.

Mattias

-- 


mattias.ell...@tsl.uu.se   tel: +46 18 471 32 58
http://www.tsl.uu.se/~ellert/  fax: +46 18 471 35 13





[sane-devel] Canoscan 2700f

2004-02-16 Thread Jonathan Knight

Hi everyone.

I have a canoscan 2700F which has been the bain of my life on Linux since
the day I bought it.  It basically doesn't work at all unless you fiddle
a number of things to get it working.  I would like to make contact with
other 2700F owners who have successfully got the canoscan to run on Redhat 9.

I had the scanner running on redhat 9 until a recent up2date which patched
the kernel and sane.  Since then nothing worked.  I've gone through my
checklist of things that need to be fiddled with and all of those seem fine.
The sense buffer that's returned for sane 1.0.12 gives a lamp failure.  On
1.0.5 the process hangs when trying to preview or scan.

For the record - here's the checklist I go through:

1.  Make sure IRQ 10 is set for legacy ISA in the BIOS
2.  echo 131072  /proc/scsi/sg/def_reserved_size
3.  patch sg.c with the non-standard scsi command lengths
4.  configure /etc/sane.d/canon.conf

(I do smile when sane lists the 2700F driver status as good when in order
to get it working you have to patch and recompile the kernel.  Hardly
something most users will consider an easy option)

That list has managed to get the scanner to run under redhat 7 and 9 until
now.  If anyone has the scanner running under the latest redhat 9 kernel
then I'd like to know what else needs changing to achieve that.

I intend to try and older version of sg.c to see if that's the problem.


-- 
  __jonat...@cs.keele.ac.ukJonathan Knight,
/  Department of Computer Science
   / _   __ Telephone: +44 1782 583437 University of Keele, Keele,
(_/ (_) / / Fax  : +44 1782 713082 Staffordshire.  ST5 5BG.  U.K.



[sane-devel] SANE support for Ricoh is410

2004-02-16 Thread Oliver Schirrmeister
Am Donnerstag 12 Februar 2004 22:02 schrieb John Lei:
 To whom it may concern,

   I have an old Ricoh is410 SCSI scanner that I was hoping to be 
 able
 to pull out of our graveyard. I've hooked it up to a PowerMac G4
 running OS X.2.8 using a Grappler 906F (current firmware) and the
 TWAIN-SANE interface. The scanner is not being detected by SANE;
 although it is showing up in my system profiler.
 I was hoping someone could assist me in this experiment; whether or
 not I'd be able to get this scanner working again.
 Thanks for your help.

 John.

I've played with the IS410 and the ibm backend some years ago. I was able
to move the paper through the ADF or even scan with some minor patches of the
backend (don't know if I've commited them to Henning). The ricoh backend
didn't work at all with that scanner. If you want to use the scanner seriously
there is some work to do. I wasn't able to get some documentation of the
scanner from ricoh. 

Oliver.



[sane-devel] Canoscan 2700f

2004-02-16 Thread abel deuring
Jonathan Knight wrote:
 
 Hi everyone.
 
 I have a canoscan 2700F which has been the bain of my life on Linux since
 the day I bought it.  It basically doesn't work at all unless you fiddle
 a number of things to get it working.  I would like to make contact with
 other 2700F owners who have successfully got the canoscan to run on Redhat 9.
 
 I had the scanner running on redhat 9 until a recent up2date which patched
 the kernel and sane.  Since then nothing worked.  I've gone through my
 checklist of things that need to be fiddled with and all of those seem fine.
 The sense buffer that's returned for sane 1.0.12 gives a lamp failure.  On
 1.0.5 the process hangs when trying to preview or scan.
 
 For the record - here's the checklist I go through:
 
 1.  Make sure IRQ 10 is set for legacy ISA in the BIOS

So you have an ISA SCSI adapter? they may indeed be a bit difficult to
configure. If this really bothers you, I'd recommend to buy a cheap PCI
SCSI adapter. You can get good used one for a few Euro or Pound at Ebay.
My personal favourites are adapters that work with the sym53c8xx driver
or the aic7xxx driver. And with a PCI SCSI adapter, you'll be able to
use SCSI transfer block sizes larger then 64kB.

 2.  echo 131072  /proc/scsi/sg/def_reserved_size

A buffer size larger than 64k is not reasonable for ISA adapters, due to
the broken ISA DMA architecture. Moreover, Sane negotiates the size of
the buffer independly (OK, perhaps not in Sane 1.0.5 -- I'd need to look
into the sources to be sure), but version 1.0.12 definitely does this.

 3.  patch sg.c with the non-standard scsi command lengths

This patch is only necessary for really old SG drivers -- no need tor a
recent Linux version like RH9.

 4.  configure /etc/sane.d/canon.conf
 
 (I do smile when sane lists the 2700F driver status as good when in order
 to get it working you have to patch and recompile the kernel.  Hardly
 something most users will consider an easy option)

As said above, it should not be necessary to recompile the SG driver
since, ummm, I guess, at least 3 or 4 years. Can't recall, when exactly
the SG driver (version 2.x) got the ability to explicitly set the
command length, and when I made sanei_scsi.c aware of the capabilities
of version 3 of the SG driver.

 
 That list has managed to get the scanner to run under redhat 7 and 9 until
 now.  If anyone has the scanner running under the latest redhat 9 kernel
 then I'd like to know what else needs changing to achieve that.
 
 I intend to try and older version of sg.c to see if that's the problem.

Alternatively, it would be intersting to see what exactly goes wrong
with the unpatched SG driver. The output of SANE_DEBUG_CANON=255
SANE_DEBUG_SANEI_SCSI=255 scanimage (or the output some other Sane
program with SANE_DEBUG_CANON and SANE_DEBUG_SANEI_SCSI set to 255)
would give us a clue. 

Abel



[sane-devel] Canoscan 2700f

2004-02-16 Thread Jonathan Buzzard
jonat...@cs.keele.ac.uk said:
 (I do smile when sane lists the 2700F driver status as good when in
 order to get it working you have to patch and recompile the kernel.
 Hardly something most users will consider an easy option)

Generally speaking the driver status refers to the quality and
comprehensiveness of the scanner driver. It does *not* refer to
how easy it is to setup. As such it means in this instance that once
setup your 2700F will function correctly giving good scans in all
modes, and all or nearly all the features of the scanner supported.

Most of your problems seem to stem from using an ancient and decrepit
ISA SCSI card. I strongly suspect that if you where using a PCI
SCSI card you would have a much easier time.

JAB.

-- 
Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk
Northumberland, United Kingdom.   Tel: +44 1661-832195





[sane-devel] Code for writing bulk transfer

2004-02-16 Thread Henning Meier-Geinitz
Hi,

On Sun, Feb 15, 2004 at 05:48:57PM -0500, Jason Anderson wrote:
 I'm trying to do some bulk transfer with this little code I have.
 The only trouble is that I've forgotten which commands to use when
 compiling it.  Could anyone of you please help me with it?  Wasn't
 the command gcc -c foo.c?

Basically, yes. Maybe you must add some -I options so the includes are
found.

 Also, to link with a library, shouldn't
 I do something like gcc -c foo.c -lsane?  Thank you in advance.

Also basically yes. But you aren't linking to libsane but you want to
use sane internal functions. So you need to link to libsanei. You may
also need to link to libusb. Some -L options to point to the directory
where the lib is may also be necessary.

You could also have a look at the tools directory, e.g. how
sane-find-scanner is linked.

 /* Try to write something to the device*/
 staus = sanei_usb_write_bulk(fd, 8, 8);

status
And I guess you don't want to write 8 bytes starting at Absolute
address 8 ...


Bye,
  Henning



[sane-devel] epson perfection 1200 SCSI not scanning via TWAIN

2004-02-16 Thread Michael C. Haller
The new version 0.5 is working fine. :-)

On Feb 13, 2004, at 12:33 AM, Karl Heinz Kremer wrote:

 Is this on a Mac?

 On Feb 11, 2004, at 5:05 PM, Michael C. Haller wrote:

 Hello,

 from the command-line everything seems to work fine:

 sane-find-scanner

   # No SCSI scanners found. If you expected something different, 
 make sure that
   # you have loaded a SCSI driver for your SCSI adapter.

 found USB scanner (vendor=0x086a, product=0x0003) at 
 libusb:004:003-086a-0003-ff-00
 found USB scanner (vendor=0x06cd [Keyspan, a division of InnoSys 
 Inc.], product=0x0119 [Keyspan USA-19QW]) at 
 libusb:004:004-06cd-0119-ff-ff
   # Your USB scanner was (probably) detected. It may or may not be 
 supported by
   # SANE. Try scanimage -L and read the backend's manpage.

   # Scanners connected to the parallel port or other proprietary 
 ports can't be
   # detected by this program.

   # You may want to run this program as root to find all devices. 
 Once you
   # found the scanner devices, be sure to adjust access permissions 
 as
   # necessary.

 scanimage -L
 device `epson:iokitscsi@02416d220872a9e0' is a Epson 
 Perfection1200 flatbed scanner

 But I am not able to scan thru the TWAIN-Interface, i.e. 
 GraphicConverter or Adobe Photoshop CS. GraphicConverter does just 
 nothing and Photoshop says: there is no scanner.

 Please, help!

 Thx a lot.

 Michael.


 -- 
 sane-devel mailing list: sane-devel@lists.alioth.debian.org
 http://lists.alioth.debian.org/mailman/listinfo/sane-devel
 Unsubscribe: Send mail with subject unsubscribe your_password
 to sane-devel-requ...@lists.alioth.debian.org