From christoph.bier@web.de Sun Jun 1 13:32:10 2003 From: christoph.bier@web.de (Christoph Bier) Date: Sun, 01 Jun 2003 14:32:10 +0200 Subject: [sane-devel] suddenly problems opening /dev/usbscanner0 In-Reply-To: <20030531143811.GC6785@meier-geinitz.de> References: <3ED6537D.3020004@web.de> <20030529184903.GC19114@hmg1> <3ED6630C.8070409@web.de> <20030530142302.GA3433@hmg1> <3ED79A4B.6000209@web.de> <20030530181542.GB689@hmg1> <3ED7AAE5.7090400@web.de> <20030530192852.GA749@hmg1> <3ED7C4A0.4070703@web.de> <20030531143811.GC6785@meier-geinitz.de> Message-ID: <3ED9F24A.8040007@web.de> Hi! Henning Meier-Geinitz schrieb: > Hi, [. . .] > You could try to use the older debian package to make sure that it > wasn't cause by an update from 1.0.10-1 to 1.0.10-2 or something like > that. I don't know where to get 1.0.10-1. > Otherwise I don't have new ideas. Me neither. I installed the scanner to my girlfriends pc, on which a Debian system is also running. No success. Tomorrow I will connect the scanner to my pc at work. Actually, I hope, that it won't work there, because I would have found the cause :-). If it works there, I don't know what else to do . . . Thanks for your help! Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier@wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From christoph.bier@web.de Mon Jun 2 10:15:26 2003 From: christoph.bier@web.de (Christoph Bier) Date: Mon, 2 Jun 2003 11:15:26 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) Message-ID: <20030602111526.5b4034a3.christoph.bier@web.de> Hi! As written in my last posting in the thread "suddenly problems [. . .]" I installed my scanner at the pc at work. Didn't help. BUT: after plugging in again the other, former at this pc installed (working!) scanner, I get the same error message starting xsane for this scanner, that worked 2 minutes before! I'm totally confused now. Only unplugging (and plugging in again) makes the scanner stop working. Even after rebooting the system, there's an error opening /dev/usbscanner0. USB-devices are hot-pluggable, aren't they?! Could I have destroyed the scanners by unplugging them while the pc was running?? Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier@wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From henning@meier-geinitz.de Mon Jun 2 14:58:33 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 2 Jun 2003 15:58:33 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030602111526.5b4034a3.christoph.bier@web.de> References: <20030602111526.5b4034a3.christoph.bier@web.de> Message-ID: <20030602135832.GA30314@meier-geinitz.de> Hi, On Mon, Jun 02, 2003 at 11:15:26AM +0200, Christoph Bier wrote: > As written in my last posting in the thread "suddenly > problems [. . .]" I installed my scanner at the pc at > work. Didn't help. BUT: after plugging in again the > other, former at this pc installed (working!) scanner, > I get the same error message starting xsane for this > scanner, that worked 2 minutes before! Maybe plugging in your (home) scanner confused the kernel. Do you get any messages from the USB system in /var/log/messages when you plug-in the scanner? > I'm totally confused now. Only unplugging (and > plugging in again) makes the scanner stop working. > Even after rebooting the system, there's an error > opening /dev/usbscanner0. Or your distribution found the scanner and used some hotplugging magic but failed. And that stops your scanner from beeing detected again. But that's not easy to diagnose from remote. > USB-devices are hot-pluggable, aren't they?! Yes. > Could I have destroyed the scanners by unplugging them while the > pc was running?? No. I don'tt day it's not edefective but if it is, it's not because you unplugged it. I'm doing that all the day with my USb scanners and that's the whole idea of USB. bye, Henning From ozymandias@charter.net Mon Jun 2 16:18:39 2003 From: ozymandias@charter.net (Howard Shane) Date: Mon, 02 Jun 2003 10:18:39 -0500 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org Message-ID: <3EDB6ACF.3010304@charter.net> I would like to announce the completion of the initial draft of the Scanner-HOWTO for the linux documentation project, and invite participants on the SANE-devel mailing list to comment on it. The goal of this document is to bridge point A (scanner) to point B (scanner running successfully in linux) for the relative newbie as efficiently as possible. As such it should not be too technical, it should cover the most common hardware interface types, the required steps to reach a working result, likely pitfalls and how to recover from them, and places to go for help. It is not designed to be an exaustive list of harware in/compatibilities. Any help you can suggest to clarify or otherwise improve the draft will be greatly appreciated and may even result in you being mentioned in the credits if you so desire. The document can be found at: http://ibiblio.org/gferg/ldp/Scanner-HOWTO.html From christoph.bier@web.de Mon Jun 2 16:42:12 2003 From: christoph.bier@web.de (Christoph Bier) Date: Mon, 2 Jun 2003 17:42:12 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030602135832.GA30314@meier-geinitz.de> References: <20030602111526.5b4034a3.christoph.bier@web.de> <20030602135832.GA30314@meier-geinitz.de> Message-ID: <20030602174212.0ce77aa9.christoph.bier@web.de> Hi! Am Mon, 2 Jun 2003 15:58:33 +0200 schrieb Henning Meier-Geinitz :: > Maybe plugging in your (home) scanner confused the kernel. Do you > get any messages from the USB system in /var/log/messages when you > plug-in the scanner? These are the messages I get, when I plug-out the (work) scanner and plug-in it again. Jun 2 17:33:38 nb-pc057 kernel: usb.c: USB disconnect on device 00:11.2-1 address 2 Jun 2 17:33:53 nb-pc057 kernel: hub.c: new USB device 00:11.2-1, assigned address 3 Jun 2 17:33:58 nb-pc057 kernel: usb_control/bulk_msg: timeout Jun 2 17:33:58 nb-pc057 kernel: hub.c: new USB device 00:11.2-1, assigned address 4 Jun 2 17:34:03 nb-pc057 kernel: usb_control/bulk_msg: timeout > > I'm totally confused now. Only unplugging (and > > plugging in again) makes the scanner stop working. > > Even after rebooting the system, there's an error > > opening /dev/usbscanner0. > > Or your distribution found the scanner and used some hotplugging > magic but failed. And that stops your scanner from beeing detected Is there a possibility to turn such "hotplugging magic" off? > again. But that's not easy to diagnose from remote. Hm. Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier@wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From peter@pscomp.com Mon Jun 2 17:44:17 2003 From: peter@pscomp.com (Peter Santoro) Date: Mon, 02 Jun 2003 12:44:17 -0400 Subject: [sane-devel] epson: scanimage threshold option not working in 1.0.12 backend Message-ID: <3EDB7EE1.3040403@pscomp.com> The scanimage threshold option worked in the 1.0.9 backend with my Epson 1660 Photo Perfection scanner. After uninstalling the 1.0.9 backend and installing the 1.0.12 backend, scanimage complains "attempted to set inactive option threshold" and fails. I took a quick look at the epson code (which I am not familiar with yet), but have not found anything yet. Was this change intentional? Thank you for your help, Peter From christoph.bier@web.de Mon Jun 2 19:58:20 2003 From: christoph.bier@web.de (Christoph Bier) Date: Mon, 02 Jun 2003 20:58:20 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030602135832.GA30314@meier-geinitz.de> References: <20030602111526.5b4034a3.christoph.bier@web.de> <20030602135832.GA30314@meier-geinitz.de> Message-ID: <3EDB9E4C.8090802@web.de> Hi! Henning Meier-Geinitz schrieb: > Hi, [. . .] > Maybe plugging in your (home) scanner confused the kernel. Do you get > any messages from the USB system in /var/log/messages when you plug-in > the scanner? With my scanner at home I get the following messages: - modules scanner, uhci: Jun 2 20:26:56 lotus kernel: usb.c: registered new driver usbscanner Jun 2 20:26:56 lotus kernel: scanner.c: 0.4.10:USB Scanner Driver Jun 2 20:27:03 lotus kernel: uhci.c: USB Universal Host Controller Interface driver v1.1 Jun 2 20:27:03 lotus kernel: PCI: Found IRQ 9 for device 00:07.3 Jun 2 20:27:03 lotus kernel: PCI: Sharing IRQ 9 with 00:07.2 Jun 2 20:27:03 lotus kernel: PCI: Sharing IRQ 9 with 00:0f.0 Jun 2 20:27:03 lotus kernel: uhci.c: USB UHCI at I/O 0xb800, IRQ 9 Jun 2 20:27:04 lotus kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 2 20:27:04 lotus kernel: hub.c: USB hub found Jun 2 20:27:04 lotus kernel: hub.c: 2 ports detected Jun 2 20:27:04 lotus kernel: PCI: Found IRQ 9 for device 00:07.2 Jun 2 20:27:04 lotus kernel: PCI: Sharing IRQ 9 with 00:07.3 Jun 2 20:27:04 lotus kernel: PCI: Sharing IRQ 9 with 00:0f.0 Jun 2 20:27:04 lotus kernel: uhci.c: USB UHCI at I/O 0xb400, IRQ 9 Jun 2 20:27:04 lotus kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 2 20:27:04 lotus kernel: hub.c: USB hub found Jun 2 20:27:04 lotus kernel: hub.c: 2 ports detected Jun 2 20:27:04 lotus kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 2 20:27:04 lotus kernel: scanner.c: USB scanner device (0x055f/0x021d) now attached to scanner0 - starting xsane : Jun 2 20:28:10 lotus kernel: Jun 2 20:28:11 lotus kernel: usb_control/bulk_msg: timeout Jun 2 20:28:11 lotus kernel: - libusb, modules uhci: Jun 2 20:29:12 lotus kernel: uhci.c: USB Universal Host Controller Interface driver v1.1 Jun 2 20:29:12 lotus kernel: PCI: Found IRQ 9 for device 00:07.3 Jun 2 20:29:12 lotus kernel: PCI: Sharing IRQ 9 with 00:07.2 Jun 2 20:29:12 lotus kernel: PCI: Sharing IRQ 9 with 00:0f.0 Jun 2 20:29:12 lotus kernel: uhci.c: USB UHCI at I/O 0xb800, IRQ 9 Jun 2 20:29:12 lotus kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 2 20:29:12 lotus kernel: hub.c: USB hub found Jun 2 20:29:12 lotus kernel: hub.c: 2 ports detected Jun 2 20:29:12 lotus kernel: PCI: Found IRQ 9 for device 00:07.2 Jun 2 20:29:12 lotus kernel: PCI: Sharing IRQ 9 with 00:07.3 Jun 2 20:29:12 lotus kernel: PCI: Sharing IRQ 9 with 00:0f.0 Jun 2 20:29:12 lotus kernel: uhci.c: USB UHCI at I/O 0xb400, IRQ 9 Jun 2 20:29:12 lotus kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 2 20:29:12 lotus kernel: hub.c: USB hub found Jun 2 20:29:12 lotus kernel: hub.c: 2 ports detected Jun 2 20:29:13 lotus kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 2 20:29:13 lotus kernel: usb.c: USB device 2 (vend/prod 0x55f/0x21d) is not claimed by any active driver. - starting xsane: no message in /var/log/messages (I guess explainable from the above message in the last line) Sorry for the long tail output, but I don't know what's really relevant and I hope, that Mozilla doesn't produce any uncomfortable linebreaks. BTW: usb.-uhci ends up with the same message. Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier@wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From karsten.festag@gmx.de Mon Jun 2 20:17:24 2003 From: karsten.festag@gmx.de (Karsten Festag) Date: Mon, 2 Jun 2003 21:17:24 +0200 Subject: [sane-devel] Microtek SlimScan C3, output always a black image In-Reply-To: <3ED56CD9.7080608@okstate.edu> References: <3ED27A5A.8050400@okstate.edu> <200305271856.47694.karsten.festag@gmx.de> <3ED56CD9.7080608@okstate.edu> Message-ID: <200306022117.24137.karsten.festag@gmx.de> Hi Jose, please look into your BIOS and make sure the parport mode is set to EPP, not ECP! I heard several times that this is the cause for stretched or shifted image lines. By the way: switching off the backend calibration has a negative side effect: you will probably see fine vertical stripes on your scanned images. Normally the backend calibration gets rid of it, but it looks like we have to find the bug in the calibration code so that it works with your scanner. Please tell me if we shall do some work in this direction - I'll need some testing work on your side to achieve this. Could you please tell me what error message appears if you use the '-y20' option to generate a logfile? Karsten On Thursday 29 May 2003 04:13, Jose Sanchez wrote: > Hi Karsten, thanks for the help, and sorry for the late answer. > > >until now I didn't find strange things in the logfile. But what error > > message gives the -y20 option (though this shouldn't be connected to the > > dark image failure)? > >Please try what happens when you (in xsane or xscanimage) turn off the > >advanced option 'calibration by backend'. > >Do you see that the scanning illumination is on during the scan? > > well I turn off the advance option you tell me and finally I am able to > see the image, although sometimes the image is acquire incorrectly, I > mean, it is cut and streched in some parts. I rescan the image several > times until the image is acquire correclty. Do you have any idea how > should I correct that error. > > Thanks > > Jose > > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From khk@khk.net Mon Jun 2 21:42:40 2003 From: khk@khk.net (Karl Heinz Kremer) Date: Mon, 2 Jun 2003 16:42:40 -0400 Subject: [sane-devel] epson: scanimage threshold option not working in 1.0.12 backend In-Reply-To: <3EDB7EE1.3040403@pscomp.com> References: <3EDB7EE1.3040403@pscomp.com> Message-ID: <20030602204240.GA9957@khk.net> --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable No it was not ... I'll take a look. Karl Heinz On Mon, Jun 02, 2003 at 12:44:17PM -0400, Peter Santoro wrote: > The scanimage threshold option worked in the 1.0.9 backend with my Epson= =20 > 1660 Photo Perfection scanner. After uninstalling the 1.0.9 backend and= =20 > installing the 1.0.12 backend, scanimage complains "attempted to set=20 > inactive option threshold" and fails. I took a quick look at the epson= =20 > code (which I am not familiar with yet), but have not found anything yet.= =20 > Was this change intentional? >=20 > Thank you for your help, >=20 > Peter >=20 > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel --=20 Karl Heinz Kremer khk@khk.net PGP Key at http://www.khk.net/download/khk.asc EPSON Sane Backend: http://www.khk.net --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQE+27bAxejv3RfKrhsRAoA5AKDZ7410Vpu4aGJ6YEIYkWZR5fFyRwCgvia6 tOrMggmHesT68q0Qe8GB2I4= =f9kM -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From dahjelle@mac.com Tue Jun 3 05:30:00 2003 From: dahjelle@mac.com (David Alan Hjelle) Date: Mon, 2 Jun 2003 21:30:00 -0700 (PDT) Subject: [sane-devel] Compiling SANE backends on Mac OS X 10.1.5 Message-ID: <20030603043000.5308.qmail@web13404.mail.yahoo.com> Hello. I've been trying to get my Microtek SlimScan C6 cheap-o scanner to work under Mac OS X for a while now, and just recently ran across SANE. I figure I should be able to use SANE with the GIMP, which I use somewhat regularly. I was trying to compile the lastest CVS snapshot (from June 2, 2003) of SANE backends, but I ran into some problems. ./configure ran no problem. make, however, eventually gave me the following errors (Or, at least, these are the errors deaing with the sanei_scsi.c file that seemed to be the cause for the compilation problem. I think everything else was just warnings. Of course, what do I know? I'm only just teaching myself C programming and have only had experience in VB and Java .): cc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes -pedantic -ansi sanei_scsi.c sanei_scsi.c:4444: illegal statement, missing `;' after `io_object_t' sanei_scsi.c:4446: illegal expression, found `int' sanei_scsi.c:4452: illegal expression, found `int' sanei_scsi.c:4454: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4460: illegal statement, missing `;' after `io_iterator_t' sanei_scsi.c:4466: illegal statement, missing `;' after `io_object_t' sanei_scsi.c:4476: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4480: illegal expression, found `int' sanei_scsi.c:4483: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4487: illegal expression, found `int' sanei_scsi.c:4503: illegal statement, missing `;' after `SInt32' sanei_scsi.c:4512: illegal statement, missing `;' after `HRESULT' sanei_scsi.c:4536: illegal statement, missing `;' after `CDBInfo' sanei_scsi.c:4540: illegal statement, missing `;' after `IOVirtualRange' sanei_scsi.c:4541: illegal statement, missing `;' after `UInt32' sanei_scsi.c:4542: illegal statement, missing `;' after `Boolean' sanei_scsi.c:4559: illegal statement, missing `;' after `SCSIResults' sanei_scsi.c:4560: illegal statement, missing `;' after `UInt32' sanei_scsi.c:4595: illegal expression, found `int' sanei_scsi.c:4601: illegal expression, found `int' sanei_scsi.c:4603: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4609: illegal statement, missing `;' after `io_iterator_t' sanei_scsi.c:4615: illegal statement, missing `;' after `io_object_t' sanei_scsi.c:4625: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4629: illegal expression, found `int' sanei_scsi.c:4632: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4636: illegal expression, found `int' sanei_scsi.c:4641: illegal statement, missing `;' after `SInt32' sanei_scsi.c:4651: illegal statement, missing `;' after `HRESULT' sanei_scsi.c:4664: illegal statement, missing `;' after `SCSIInquiry' sanei_scsi.c:4665: illegal statement, missing `;' after `UInt32' cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode In file included from /usr/include/machine/types.h:30, from /usr/include/sys/types.h:70, from ../include/sane/config.h:444, from sanei_scsi.c:47: /usr/include/ppc/types.h:75: warning: ANSI C does not support `long long' /usr/include/ppc/types.h:76: warning: ANSI C does not support `long long' In file included from sanei_scsi.c:47: ../include/sane/config.h:445: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:27, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:5, from sanei_scsi.c:184: /usr/include/stdint.h:68: warning: ANSI C does not support `long long' /usr/include/stdint.h:69: warning: ANSI C does not support `long long' In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:32, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:5, from sanei_scsi.c:184: /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore.framework/Headers/MacTypes.h:120: warning: ANSI C does not support `long long' /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore.framework/Headers/MacTypes.h:121: warning: ANSI C does not support `long long' /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore.framework/Headers/MacTypes.h:291: warning: function declaration isn't a prototype /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore.framework/Headers/MacTypes.h:292: warning: function declaration isn't a prototype In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:6, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:346: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:7, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBag.h:63: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFCharacterSet.h:35, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:8, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFData.h:40: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:11, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFCharacterSet.h:36, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:8, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFDictionary.h:516: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFCharacterSet.h:36, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:8, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:89: warning: ANSI C restricts enumerator values to range of `int' /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:232: warning: ANSI C forbids const or volatile functions /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:235: warning: ANSI C forbids const or volatile functions /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:449: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:14, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFSet.h:64: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:19, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFXMLNode.h:166: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:40, from sanei_scsi.c:184: /usr/include/math.h:191: warning: function declaration isn't a prototype In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:63, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBinaryHeap.h:209: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:66, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h: In function `CFSwapInt16': /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:40: `asm' undeclared (first use in this function) /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:40: (Each undeclared identifier is reported only once /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:40: for each function it appears in.) /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:40: parse error before `volatile' /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:33: warning: unused parameter `arg' /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h: In function `CFSwapInt32': /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:64: `asm' undeclared (first use in this function) /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:64: parse error before `volatile' /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:57: warning: unused parameter `arg' In file included from /usr/include/mach/machine/vm_types.h:27, from /usr/include/mach/port.h:65, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFRunLoop.h:66, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFMachPort.h:10, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:72, from sanei_scsi.c:184: /usr/include/mach/ppc/vm_types.h: At top level: /usr/include/mach/ppc/vm_types.h:181: warning: ANSI C does not support `long long' In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:82, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFStream.h:171: warning: ANSI C forbids const or volatile functions In file included from /usr/include/mach/memory_object_types.h:68, from /usr/include/mach/mach_types.h:69, from /System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:38, from sanei_scsi.c:185: /usr/include/mach/vm_types.h:34: warning: ANSI C does not support `long long' In file included from /usr/include/mach/mach_types.h:69, from /System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:38, from sanei_scsi.c:185: /usr/include/mach/memory_object_types.h:73: warning: ANSI C does not support `long long' /usr/include/mach/memory_object_types.h:74: warning: ANSI C does not support `long long' In file included from /System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:48, from sanei_scsi.c:185: /System/Library/Frameworks/IOKit.framework/Headers/OSMessageNotification.h:83: warning: ANSI C forbids zero-size array `content' /System/Library/Frameworks/IOKit.framework/Headers/OSMessageNotification.h:93: warning: ANSI C forbids zero-size array `args' In file included from /System/Library/Frameworks/IOKit.framework/Headers/cdb/IOSCSILib.h:15, from sanei_scsi.c:187: /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSICommand.h:61: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSICommand.h:71: warning: comma at end of enumerator list In file included from /System/Library/Frameworks/IOKit.framework/Headers/cdb/IOSCSILib.h:16, from sanei_scsi.c:187: /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:66: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:79: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:88: warning: ANSI C restricts enumerator values to range of `int' /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:89: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:95: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:101: warning: comma at end of enumerator list In file included from /System/Library/Frameworks/IOKit.framework/Headers/cdb/IOSCSILib.h:17, from sanei_scsi.c:187: /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:61: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:66: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:77: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:105: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:116: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:137: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:150: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:170: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:175: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:182: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:255: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:289: warning: comma at end of enumerator list In file included from ../include/sane/sanei.h:66, from sanei_scsi.c:198: ../include/sane/sane.h:197: warning: ANSI C forbids const or volatile functions In file included from sanei_scsi.c:199: ../include/sane/sanei_config.h:87: warning: ANSI C forbids const or volatile functions ../include/sane/sanei_config.h:104: warning: ANSI C forbids const or volatile functions sanei_scsi.c: In function `sanei_scsi_open': sanei_scsi.c:812: warning: unused variable `real_dev' sanei_scsi.c: In function `sanei_scsi_cmd2': sanei_scsi.c:4444: parse error before `scsiDevice' sanei_scsi.c:4447: `i' undeclared (first use in this function) sanei_scsi.c:4447: `scsiDevice' undeclared (first use in this function) sanei_scsi.c:4452: parse error before `int' sanei_scsi.c:4457: `deviceTypeRef' undeclared (first use in this function) sanei_scsi.c:4460: parse error before `scsiObjectIterator' sanei_scsi.c:4463: `scsiObjectIterator' undeclared (first use in this function) sanei_scsi.c:4466: parse error before `device' sanei_scsi.c:4467: `device' undeclared (first use in this function) sanei_scsi.c:4476: parse error before `scsiTargetRef' sanei_scsi.c:4481: `scsiTargetRef' undeclared (first use in this function) sanei_scsi.c:4481: `scsitarget' undeclared (first use in this function) sanei_scsi.c:4483: parse error before `scsiLunRef' sanei_scsi.c:4488: `scsiLunRef' undeclared (first use in this function) sanei_scsi.c:4488: `scsilun' undeclared (first use in this function) sanei_scsi.c:4491: warning: comparison between signed and unsigned sanei_scsi.c:4502: parse error before `*' sanei_scsi.c:4507: `plugInInterface' undeclared (first use in this function) sanei_scsi.c:4508: `score' undeclared (first use in this function) sanei_scsi.c:4512: parse error before `plugInResult' sanei_scsi.c:4515: `plugInResult' undeclared (first use in this function) sanei_scsi.c:4518: `scsiDeviceInterface' undeclared (first use in this function) sanei_scsi.c:4528: parse error before `*' sanei_scsi.c:4532: `cdbCommandInterface' undeclared (first use in this function) sanei_scsi.c:4536: parse error before `cdb' sanei_scsi.c:4537: `cdb' undeclared (first use in this function) sanei_scsi.c:4540: parse error before `range' sanei_scsi.c:4546: `range' undeclared (first use in this function) sanei_scsi.c:4548: `transferCount' undeclared (first use in this function) sanei_scsi.c:4549: `isWrite' undeclared (first use in this function) sanei_scsi.c:4559: parse error before `results' sanei_scsi.c:4564: `seqNumber' undeclared (first use in this function) sanei_scsi.c:4569: `results' undeclared (first use in this function) sanei_scsi.c: In function `sanei_scsi_find_devices': sanei_scsi.c:4595: parse error before `int' sanei_scsi.c:4596: `i' undeclared (first use in this function) sanei_scsi.c:4601: parse error before `int' sanei_scsi.c:4606: `deviceTypeRef' undeclared (first use in this function) sanei_scsi.c:4609: parse error before `scsiObjectIterator' sanei_scsi.c:4612: `scsiObjectIterator' undeclared (first use in this function) sanei_scsi.c:4615: parse error before `scsiDevice' sanei_scsi.c:4616: `scsiDevice' undeclared (first use in this function) sanei_scsi.c:4625: parse error before `scsiTargetRef' sanei_scsi.c:4630: `scsiTargetRef' undeclared (first use in this function) sanei_scsi.c:4630: `scsitarget' undeclared (first use in this function) sanei_scsi.c:4632: parse error before `scsiLunRef' sanei_scsi.c:4637: `scsiLunRef' undeclared (first use in this function) sanei_scsi.c:4637: `scsilun' undeclared (first use in this function) sanei_scsi.c:4640: parse error before `*' sanei_scsi.c:4646: `plugInInterface' undeclared (first use in this function) sanei_scsi.c:4647: `score' undeclared (first use in this function) sanei_scsi.c:4651: parse error before `plugInResult' sanei_scsi.c:4654: `plugInResult' undeclared (first use in this function) sanei_scsi.c:4657: `scsiDeviceInterface' undeclared (first use in this function) sanei_scsi.c:4664: parse error before `inquiry' sanei_scsi.c:4667: `inquiry' undeclared (first use in this function) sanei_scsi.c:4668: `inquirySize' undeclared (first use in this function) sanei_scsi.c:4585: warning: unused parameter `findtype' sanei_scsi.c:4586: warning: unused parameter `findbus' sanei_scsi.c:4586: warning: unused parameter `findchannel' sanei_scsi.c:4586: warning: unused parameter `findid' sanei_scsi.c: In function `sanei_scsi_req_enter2': sanei_scsi.c:4700: warning: unused parameter `idp' sanei_scsi.c: In function `sanei_scsi_req_wait': sanei_scsi.c:4706: warning: unused parameter `id' sanei_scsi.c: In function `sanei_scsi_req_flush_all_extended': sanei_scsi.c:4717: warning: unused parameter `fd' make[1]: *** [sanei_scsi.o] Error 1 make: *** [all-recursive] Error 1 Wow, that was really long. Sorry. I hope that was enough info, though. I hope you can help. I'd love to get this scanner working again. In Christ Alone, David Alan Hjelle 1 Corithians 2:2 http://welcome.to/theJESUSpage __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com From moali@sbox.tugraz.at Tue Jun 3 08:42:19 2003 From: moali@sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 09:42:19 +0200 Subject: [sane-devel] backends 1.0.12 compile-error Message-ID: <3EDC515B.8050706@sbox.tugraz.at> Hello sane-devel! Unfortunately my attempts to compile sane-backends 1.0.12 fail on my machine (1.0.11 worked without any problem). Configure mentions no error. Kernel 2.4.17 If you need any further information, please mail me. Regards, Maier Gerfried [...] hp5400_internal.c:411: warning: unused parameter `iHandle' hp5400_internal.c: In function `hp5400_test_scan_response': hp5400_internal.c:660: warning: unused parameter `req' hp5400_internal.c: In function `DoScan': hp5400_internal.c:729: warning: unused parameter `code' hp5400_internal.c: In function `hp5400_scan': hp5400_internal.c:909: warning: unused parameter `pHWParams' hp5400_internal.c: In function `InitScan2': hp5400_internal.c:1187: warning: comparison between signed and unsigned hp5400_internal.c:1223: warning: comparison between signed and unsigned hp5400.c: In function `attach_one_device': hp5400.c:432: warning: passing arg 1 of `HP5400Detect' discards qualifiers from pointer target type hp5400.c: At top level: hp5400_sanei.c:253: warning: `hp5400_bulk_read' defined but not used hp5400_sanei.c:361: warning: `hp5400_isOn' defined but not used hp5400_internal.c:605: warning: `DecodeImage' defined but not used hp5400_internal.c:661: warning: `hp5400_test_scan_response' defined but not used hp5400_internal.c:975: warning: `PreviewScan' defined but not used hp5400_internal.c:1013: warning: `InitScanner' defined but not used rm -f hp5400-s.c ln -s ./stubs.c hp5400-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=hp5400 hp5400-s.c -fPIC -DPIC -o .libs/hp5400-s.o gcc -shared .libs/hp5400.o .libs/hp5400-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../sanei/.libs/sanei_usb.o ../sanei/.libs/sanei_config2.o -lnsl -lm /usr/lib/libjpeg.so -ldl -Wl,-soname -Wl,libsane.so.1 -o .libs/libsane-hp5400.so.1.0.12 (cd .libs && rm -f libsane-hp5400.so.1 && ln -s libsane-hp5400.so.1.0.12 libsane-hp5400.so.1) (cd .libs && rm -f libsane-hp5400.so && ln -s libsane-hp5400.so.1.0.12 libsane-hp5400.so) creating libsane-hp5400.la (cd .libs && rm -f libsane-hp5400.la && ln -s ../libsane-hp5400.la libsane-hp5400.la) make[1]: Verlassen des Verzeichnisses Verzeichnis »/home/moali/src/sane-backends-1.0.12/backend« making all in frontend make[1]: Wechsel in das Verzeichnis Verzeichnis »/home/moali/src/sane-backends-1.0.12/frontend« gcc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I/usr/local/include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -g -O2 -W -Wall saned.c saned.c: In function `check_host': saned.c:559: structure has no member named `ss_family' saned.c:562: warning: unreachable code at beginning of switch statement saned.c: In function `start_scan': saned.c:1025: structure has no member named `ss_family' saned.c:1034: structure has no member named `ss_family' saned.c:1037: warning: unreachable code at beginning of switch statement saned.c:1074: structure has no member named `ss_family' saned.c:1077: warning: unreachable code at beginning of switch statement make[1]: *** [saned.o] Fehler 1 make[1]: Verlassen des Verzeichnisses Verzeichnis »/home/moali/src/sane-backends-1.0.12/frontend« make: *** [all-recursive] Fehler 1 From Martijn van Oosterhout Tue Jun 3 10:07:20 2003 From: Martijn van Oosterhout (Martijn van Oosterhout) Date: Tue, 3 Jun 2003 19:07:20 +1000 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC515B.8050706@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> Message-ID: <20030603090720.GA10945@svana.org> --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 03, 2003 at 09:42:19AM +0200, Gerfried Maier wrote: > Hello sane-devel! >=20 > Unfortunately my attempts to compile sane-backends 1.0.12 fail on my=20 > machine (1.0.11 worked without any problem). Configure mentions no error. >=20 > Kernel 2.4.17 W.R.T. the hp5400 backend those are just a bunch of warnings so they're not important (but should be fixed anyway). Your actual error is: > saned.c: In function `check_host': > saned.c:559: structure has no member named `ss_family' > saned.c:562: warning: unreachable code at beginning of switch statement I can't quite see what the problem is, my version here doesn't show it. Can you check the strucutre used to see if it really has it. Oh yeah, what OS is this? --=20 Martijn van Oosterhout http://svana.org/kleptog/ > "the West won the world not by the superiority of its ideas or values or > religion but rather by its superiority in applying organized violence. > Westerners often forget this fact, non-Westerners never do." > - Samuel P. Huntington --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+3GVIY5Twig3Ge+YRAlEFAJ9y4FiyiMy0Obm8tYErP7n66kVO4ACg3XDf ekXxdY8XToDMlPiTuY4X2MA= =eEdS -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J-- From moali@sbox.tugraz.at Tue Jun 3 10:27:28 2003 From: moali@sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 11:27:28 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <20030603090720.GA10945@svana.org> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> Message-ID: <3EDC6A00.90907@sbox.tugraz.at> Martijn van Oosterhout wrote: >On Tue, Jun 03, 2003 at 09:42:19AM +0200, Gerfried Maier wrote: > > >>saned.c: In function `check_host': >>saned.c:559: structure has no member named `ss_family' >>saned.c:562: warning: unreachable code at beginning of switch statement >> The affected lines from saned.c - unfortunately I'm not very used to C-programming, so that I cannot read that much out of them: [...] switch (remote_address.ss_family) { case AF_INET: if (IN_LOOPBACK (ntohl (sin->sin_addr.s_addr))) { DBG (DBG_MSG, "check_host: remote host is IN_LOOPBACK: access granted\n"); return SANE_STATUS_GOOD; } break; [...] remote_address is defined somewhere around line 195 in saned.c: [...] #ifdef SANED_USES_AF_INDEP static struct sockaddr_storage remote_address; static int remote_address_len; #else static struct in_addr remote_address; #endif /* SANED_USES_AF_INDEP */ [...] >I can't quite see what the problem is, my version here doesn't show it. Can >you check the strucutre used to see if it really has it. > >Oh yeah, what OS is this? > > Sorry, 've forgotten to mention it: Linux with Kernel 2.4.17 Maier Gerfried From jb@jblache.org Tue Jun 3 10:56:37 2003 From: jb@jblache.org (Julien BLACHE) Date: Tue, 03 Jun 2003 11:56:37 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC6A00.90907@sbox.tugraz.at> (Gerfried Maier's message of "Tue, 03 Jun 2003 11:27:28 +0200") References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: <87brxfxz56.fsf@frigate.technologeek.org> Gerfried Maier wrote: >>>saned.c: In function `check_host': >>>saned.c:559: structure has no member named `ss_family' >>>saned.c:562: warning: unreachable code at beginning of switch statement >>> > > The affected lines from saned.c - unfortunately I'm not very used to > C-programming, so that I cannot read that much out of them: If you do not need IPv6 support, configure sane-backends with --disable-ipv6 and it'll build fine. I think the version of the libc could be the problem here. JB. -- Julien BLACHE From knan@mo.himolde.no Tue Jun 3 11:09:55 2003 From: knan@mo.himolde.no (=?ISO-8859-1?Q?Erik_Inge_Bols=F8?=) Date: Tue, 3 Jun 2003 12:09:55 +0200 (CEST) Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC6A00.90907@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: On Tue, 3 Jun 2003, Gerfried Maier wrote: >Martijn van Oosterhout wrote: >>On Tue, Jun 03, 2003 at 09:42:19AM +0200, Gerfried Maier wrote: >>>saned.c: In function `check_host': >>>saned.c:559: structure has no member named `ss_family' >>>saned.c:562: warning: unreachable code at beginning of switch statement > >The affected lines from saned.c - unfortunately I'm not very used to >C-programming, so that I cannot read that much out of them: > > >[...] > switch (remote_address.ss_family) > { > case AF_INET: > if (IN_LOOPBACK (ntohl (sin->sin_addr.s_addr))) > { > DBG (DBG_MSG, > "check_host: remote host is IN_LOOPBACK: access >granted\n"); > return SANE_STATUS_GOOD; > } > break; >[...] > >remote_address is defined somewhere around line 195 in saned.c: >[...] >#ifdef SANED_USES_AF_INDEP >static struct sockaddr_storage remote_address; >static int remote_address_len; >#else >static struct in_addr remote_address; >#endif /* SANED_USES_AF_INDEP */ >[...] Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is defined or undefined? If it is undefined, the error would seem to be straightforward, since at least my struct in_addr (in netinet/in.h ) doesn't have any ss_family member... /* Internet address. */ typedef uint32_t in_addr_t; struct in_addr { in_addr_t s_addr; }; -- Erik I. Bolsų | email: The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. From henning@meier-geinitz.de Tue Jun 3 10:24:48 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 11:24:48 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030602174212.0ce77aa9.christoph.bier@web.de> References: <20030602111526.5b4034a3.christoph.bier@web.de> <20030602135832.GA30314@meier-geinitz.de> <20030602174212.0ce77aa9.christoph.bier@web.de> Message-ID: <20030603092448.GA5732@hmg1> Hi, On Mon, Jun 02, 2003 at 05:42:12PM +0200, Christoph Bier wrote: > These are the messages I get, when I plug-out the > (work) scanner and plug-in it again. > > Jun 2 17:33:38 nb-pc057 kernel: usb.c: USB disconnect on device > 00:11.2-1 address 2 > Jun 2 17:33:53 nb-pc057 kernel: hub.c: new USB device 00:11.2-1, > assigned address 3 > Jun 2 17:33:58 nb-pc057 kernel: usb_control/bulk_msg: timeout > Jun 2 17:33:58 nb-pc057 kernel: hub.c: new USB device 00:11.2-1, > assigned address 4 Looks fine. > Jun 2 17:34:03 nb-pc057 kernel: usb_control/bulk_msg: timeout Oh well. Either a hardware problem (too slow to react?) or a kernel bug. Check the linux-usb-users mailing list for this one, I remeber that other people had similar problems, but not with scanners. Maybe that's a problem with your USB chipset, but I don't remeber the details. It doesn't seem to be an issue of the scanner module or sane. > > Or your distribution found the scanner and used some hotplugging > > magic but failed. And that stops your scanner from beeing detected > > Is there a possibility to turn such "hotplugging > magic" off? Yes :-) For the details, consult your distribution's documentation. A rather drasti way is to renam the /sbin/hotplug program to something else. Bye, Henning From soumarmt@nerim.net Tue Jun 3 11:17:34 2003 From: soumarmt@nerim.net (Thomas Soumarmon) Date: Tue, 3 Jun 2003 12:17:34 +0200 Subject: [sane-devel] backends 1.0.12 compile-error Message-ID: <200306031217.34653.soumarmt@nerim.net> Maybe on a linux before version 2.4.19 the structures sockaddr_storage in_addr do not have ss_family member. A solution to that would be to migrate to a newer kernel or compile an older version of SANE ? From henning@meier-geinitz.de Tue Jun 3 11:28:52 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 12:28:52 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC6A00.90907@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: <20030603102852.GC13710@hmg1> Hi, On Tue, Jun 03, 2003 at 11:27:28AM +0200, Gerfried Maier wrote: > switch (remote_address.ss_family) > static struct sockaddr_storage remote_address; struct sockaddr_storage is defined in /usr/include/bits/socket.h: struct sockaddr_storage { __SOCKADDR_COMMON (ss_); /* Address family, etc. */ __ss_aligntype __ss_align; /* Force desired alignment. */ char __ss_padding[_SS_PADSIZE]; }; with: #define __SOCKADDR_COMMON(sa_prefix) \ sa_family_t sa_prefix##family So remote_address.ss_family should be ok. I think I've seen that compilation error on Linux/arm and that's a glibc bug (I guess). What version of the C-library do you use? Hoq is struct sockaddr_storage defined? Bye, Henning From moali@sbox.tugraz.at Tue Jun 3 12:25:55 2003 From: moali@sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 13:25:55 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: <3EDC85C3.4040309@sbox.tugraz.at> Erik Inge Bolsų wrote: >Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is >defined or undefined? > in include/sane/config.h: (around line 70) [...] /* Define to 1 if you have the `getaddrinfo' function. */ #define HAVE_GETADDRINFO 1 /* Define to 1 if you have the `getenv' function. */ #define HAVE_GETENV 1 /* Define to 1 if you have the `getnameinfo' function. */ #define HAVE_GETNAMEINFO 1 [...] and in frontend/saned.c: (around line 35) [...] #if defined(HAVE_GETADDRINFO) && defined (HAVE_GETNAMEINFO) # define SANED_USES_AF_INDEP #else # undef ENABLE_IPV6 #endif /* HAVE_GETADDRINFO && HAVE_GETNAMEINFO && HAVE_POLL */ [...] so finally, SANED_USES_AF_INDEP should be defined. >If it is undefined, the error would seem to be straightforward, since at >least my struct in_addr (in netinet/in.h ) doesn't have any ss_family >member... > >/* Internet address. */ >typedef uint32_t in_addr_t; >struct in_addr > { > in_addr_t s_addr; > }; > Same here. Maier Gerfried From moali@sbox.tugraz.at Tue Jun 3 12:28:51 2003 From: moali@sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 13:28:51 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <87brxfxz56.fsf@frigate.technologeek.org> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <87brxfxz56.fsf@frigate.technologeek.org> Message-ID: <3EDC8673.7060601@sbox.tugraz.at> Julien BLACHE wrote: >Gerfried Maier wrote: > > > >>>>saned.c: In function `check_host': >>>>saned.c:559: structure has no member named `ss_family' >>>>saned.c:562: warning: unreachable code at beginning of switch statement >>>> >>>> >>>> >>The affected lines from saned.c - unfortunately I'm not very used to >>C-programming, so that I cannot read that much out of them: >> >> > >If you do not need IPv6 support, configure sane-backends with >--disable-ipv6 and it'll build fine. > Unfortunately not. Same error. >I think the version of the libc could be the problem here. > # /lib/libc.so.6 GNU C Library stable release version 2.1.3, by Roland McGrath et al. Copyright (C) 1992, 93, 94, 95, 96, 97, 98, 99 Free Software Foundation, Inc. [...] Regards, Maier Gerfried From moali@sbox.tugraz.at Tue Jun 3 12:44:41 2003 From: moali@sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 13:44:41 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: <3EDC8A29.60500@sbox.tugraz.at> Erik Inge Bolsų wrote: >On Tue, 3 Jun 2003, Gerfried Maier wrote: > > >>[...] >> >>remote_address is defined somewhere around line 195 in saned.c: >>[...] >>#ifdef SANED_USES_AF_INDEP >>static struct sockaddr_storage remote_address; >>static int remote_address_len; >>#else >>static struct in_addr remote_address; >>#endif /* SANED_USES_AF_INDEP */ >>[...] >> >> > >Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is >defined or undefined? > >If it is undefined, the error would seem to be straightforward, since at >least my struct in_addr (in netinet/in.h ) doesn't have any ss_family >member... > >/* Internet address. */ >typedef uint32_t in_addr_t; >struct in_addr > { > in_addr_t s_addr; > }; > I just figured out that sockaddr_storage is defined in bits/socket.h. There it says (around line 143): [...] /* Structure large enough to hold any socket address (with the historical exception of AF_UNIX). We reserve 128 bytes. */ #if ULONG_MAX > 0xffffffff # define __ss_aligntype __uint64_t #else # define __ss_aligntype __uint32_t #endif #define _SS_SIZE 128 #define _SS_PADSIZE (_SS_SIZE - (2 * sizeof (__ss_aligntype))) struct sockaddr_storage { __SOCKADDR_COMMON (__ss_); /* Address family, etc. */ __ss_aligntype __ss_align; /* Force desired alignment. */ char __ss_padding[_SS_PADSIZE]; }; [...] No (obvious?) member ss_family, too. Maier Gerfried From knan@mo.himolde.no Tue Jun 3 12:46:19 2003 From: knan@mo.himolde.no (=?ISO-8859-1?Q?Erik_Inge_Bols=F8?=) Date: Tue, 3 Jun 2003 13:46:19 +0200 (CEST) Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC85C3.4040309@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC85C3.4040309@sbox.tugraz.at> Message-ID: On Tue, 3 Jun 2003, Gerfried Maier wrote: >Erik Inge Bolsų wrote: > >>Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is >>defined or undefined? >[...] > >so finally, SANED_USES_AF_INDEP should be defined. Okay. Ah. I think I found it. http://www.landfield.com/wu-ftpd/mail-archive/wuftpd-dev/2001/Aug/0001.html >| ftpd.c:1093: structure has no member named `ss_family' > >This message is because the Linux sockaddr_storage struct member is >called __ss_family not ss_family, if using configure add "#define >HAVE__SS_FAMILY" to the generated src/config.h (before the Socket >macros), then run make. >You could also try using build, edit config.h.noac, change "#undef INET6" >to "#define INET6" followed by ./build lnx should work. ... anyone feel like adding a configure check and a patch for this? Probably a certain libc or a certain distro has this problem. -- Erik I. Bolsų | email: The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. From knan@mo.himolde.no Tue Jun 3 12:48:00 2003 From: knan@mo.himolde.no (=?ISO-8859-1?Q?Erik_Inge_Bols=F8?=) Date: Tue, 3 Jun 2003 13:48:00 +0200 (CEST) Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC8A29.60500@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC8A29.60500@sbox.tugraz.at> Message-ID: On Tue, 3 Jun 2003, Gerfried Maier wrote: >[...] >/* Structure large enough to hold any socket address (with the historical > exception of AF_UNIX). We reserve 128 bytes. */ >#if ULONG_MAX > 0xffffffff ># define __ss_aligntype __uint64_t >#else ># define __ss_aligntype __uint32_t >#endif >#define _SS_SIZE 128 >#define _SS_PADSIZE (_SS_SIZE - (2 * sizeof (__ss_aligntype))) > >struct sockaddr_storage > { > __SOCKADDR_COMMON (__ss_); /* Address family, etc. */ > __ss_aligntype __ss_align; /* Force desired alignment. */ > char __ss_padding[_SS_PADSIZE]; > }; >[...] > >No (obvious?) member ss_family, too. See my other mail. This seems to confirm it. What distro / libc do you have? -- Erik I. Bolsų | email: The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. From moali@sbox.tugraz.at Tue Jun 3 13:35:53 2003 From: moali@sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 14:35:53 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC85C3.4040309@sbox.tugraz.at> Message-ID: <3EDC9629.8030405@sbox.tugraz.at> Erik Inge Bolsų wrote: >On Tue, 3 Jun 2003, Gerfried Maier wrote: > > >>Erik Inge Bolsų wrote: >> >> >> >>>Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is >>>defined or undefined? >>> >>> >>[...] >> >>so finally, SANED_USES_AF_INDEP should be defined. >> >> > >Okay. > >Ah. I think I found it. > >http://www.landfield.com/wu-ftpd/mail-archive/wuftpd-dev/2001/Aug/0001.html > > > >>| ftpd.c:1093: structure has no member named `ss_family' >> >>This message is because the Linux sockaddr_storage struct member is >>called __ss_family not ss_family, if using configure add "#define >>HAVE__SS_FAMILY" to the generated src/config.h (before the Socket >>macros), then run make. >>You could also try using build, edit config.h.noac, change "#undef INET6" >>to "#define INET6" followed by ./build lnx should work. >> >> > >... anyone feel like adding a configure check and a patch for this? >Probably a certain libc or a certain distro has this problem. > That's it! Replaced all occurences of ss_family in frontend/saned.c with __ss_family - and it compiles! Erik, Thank you for your help! Gerfried Maier From moali@sbox.tugraz.at Tue Jun 3 13:56:02 2003 From: moali@sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 14:56:02 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <20030603102852.GC13710@hmg1> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <20030603102852.GC13710@hmg1> Message-ID: <3EDC9AE2.8010700@sbox.tugraz.at> Henning Meier-Geinitz wrote: >Hi, > >On Tue, Jun 03, 2003 at 11:27:28AM +0200, Gerfried Maier wrote: > > >> switch (remote_address.ss_family) >> static struct sockaddr_storage remote_address; >> >> > >struct sockaddr_storage is defined in /usr/include/bits/socket.h: >struct sockaddr_storage > { > __SOCKADDR_COMMON (ss_); /* Address family, etc. */ > Ah. here it is: __SOCKADDR_COMMON (__ss_); /* Address family, etc. */ ^ ^ >[...] >So remote_address.ss_family should be ok. I think I've seen that >compilation error on Linux/arm and that's a glibc bug (I guess). What >version of the C-library do you use? Hoq is struct sockaddr_storage >defined? > This is glibc 2.1.3 Greetings, Maier Gerfried From henning@meier-geinitz.de Tue Jun 3 13:56:47 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 14:56:47 +0200 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org In-Reply-To: <3EDB6ACF.3010304@charter.net> References: <3EDB6ACF.3010304@charter.net> Message-ID: <20030603125647.GA817@hmg1> Hi, On Mon, Jun 02, 2003 at 10:18:39AM -0500, Howard Shane wrote: > I would like to announce the completion of the initial draft of the > Scanner-HOWTO for the linux documentation project, and invite > participants on the SANE-devel mailing list to comment on it. Cool! Nice work. > Any help you can suggest to clarify or otherwise improve the draft will > be greatly appreciated and may even result in you being mentioned in the > credits if you so desire. Ok, if you want corrections/comments you'll get them :-). I'm not a native English speaker, so I have misunderstood some of the documentation. | 2.1. SCSI Devices | In general if you have one of the following SCSI adapters, your | scanner should work without difficulty: Pretty much any SCSI adapter should work. Some may need some tweaking. I'm not sure if it helps to select just a few ones. | Acard/Advance At least with older kernels, there was a lot of trouble with those. | Adaptec AHA-1505/AHA-1542/AHA-2940 | ASUS SC200 | BusLogic BT958 | NCR/Symbios 53c400/53c400 ISA card | Domex DTC3181E/L/LE (DTCT436/436P) ISA card The last two are very low level cards that come with SCSI scanners (e.g. Mustek ones). I wouldn't call them "work without difficulty". While they can be made to work, they are slow and the driver tends to crash quite often. | Again, consult the above referenced link if you are unsure. That's the SANE backend list link? Maybe linking to the sane-scsi manpage makes sense here. The manpages are online on mostang.com in html format. | 2.3. Parallel Port Devices | If your scanner is really old and has a 25-pin connector it is | probably of this type. SOme SCSI scanners have the same db25 connector and the same cable. So be careful... | I recommend checking out the page on the subject by Jonathan Buzzard | for the working list, though as of this writing the page had not been | updated in some time so there may be hope if yours isn't listed. The scanner search engine can also print a list of all supported parport devices if you just select "parport" and don't enter any keywords. | 3. Kernel Support of your Scanner Device | $ ls -R /lib/modules/X.XX/drivers LC_ALL=C ls -R /lib/modules/2.4.21-rc6/drivers ls: /lib/modules/2.4.21-rc6/drivers: No such file or directory The directory structure changed in recent kernels. It's now /lib/modules/X.XX/kernel/drivers | (A hint for newbies: if the info in dmesg or the above module list | scrolls by too fast, you can catch the info in a file like so: dmesg > | file.txt, where 'file.txt' will contain the needed info.) If a newbie doesn't know how to deal with that kind of problem, he may not know ho to view the file. What about "dmesg|less"? | 3.1. SCSI Support | | If you have an SCSI card in your computer, there is no kernel option | for SCSI support other than that for your card plus generic SCSI | device support (usually named /dev/sg0, /dev/sg1 etc.). I don't really understand that part. "You only need to enable the two SCSI options ... in the kernel..."? | Since you | probably already know if your card is supported from the next page, | all that is necessary is to load the module like so: Which next page? | 3.2. USB Support Instead of the kernel scanner module, using libusb is also possible. In fact, it may be the only way in Linux 2.6. If you don't use libusb, you may need a really recent kernel (2.4.21-pre) to get some scanners working. | 3.3. Parallel Port Scanners Maybe the maintainers of the parport backends can give some more comments here. Some backends access the parport directly with inb/outb commands or via /dev/port. Loading the "parport" module may interfere with that (?). | Your parallel port should be set to preferably "ECP" mode, or | "bidirectional" (also known as "BPP" or "PS/2") at a minimum. | "Unidirectional" (also known as "SPP") and "EPP" may work, although | more slowly. There is usually a BIOS setting for this. At least the umax_pp backend manpage says "EPP only". | Depending on whether your parallel port scanner requires SCSI support, | you may need to patch your kernel for paraport-SCSI support. Typo: parport. | 4.2. Creating Devices Manually Nice, but are there really any distributions that don't have /dev/MAKEDEV or a similar script that takes care of these details if the devices haven't been created when installing Linux? | 4.2.3. Manually creating Parallel Port Devices Depending on the backend you may need /dev/port, /dev/parport or none of those. | 4.3. Groups and Permissions | # chmod u+rw /dev/usb/scanner0 | ...where u+rw means add read and write access for user. See the | documentation for chmod (man chmod or info chmod) for further info. Didn't you want to give the permission to the group, not the user? | 5. SANE | The final prerequisite for scanner access is the SANE tools and a | suitable SANE-frontend. The former are the drivers and low-level | access tools that interface with your scanner, and the latter are | graphical tools for complex functions used within the X-windows | system. Only the former are required for scanner access, though a | frontend is highly recommended in order to manipulate images and to | actually be able to see your images in a windowed environment without | having to print them. That's a bit confusing IMHO. What do you mean by "SANE tools"? Better use the package name "sane-backends" or the terms "backends" and "frontends". | 5.2. Configuring SANE | 5.2.1. By Scanner Manufacturer | find / -name saned.conf Better don't mention that, because people may start to edit saned.conf... Further more, it may take ages, "locate" is faster. But the rule of thumb is pretty much accurate: "If you compiled the source from mostang.com yourself, it's in /usr/local/etc, otherwise in /etc." | Change to the indicated directory and look for the name of your | manufacturer. For example, if you have an HP scanner, hp.conf or an | Epson scanner epson.conf and so on. That doesn't work for many scanners. E.g. Epson scanners may also be supported by the plustek backend. Mustek scanners may be supported by mustek, mustek_usb, mustek_pp, gt68xx, plustek or ma1509 backends. Better point the user to the devicel ists, they contain the name of the backend. | You should see two items in the file: interface type (scsi vs. usb), | and the device name. If you have a usb scanner, you will usually need | to comment out (make a # mark in front of) the 'scsi' line, and | uncomment the line containing 'usb.' While this may work with most backends, it's not a general rule. E.g. the plustek backend uses "device /dev/something". I wouldn't comment on these details without listing (and testing) every single backend that works this way. Most USB and SCSI scanners should work out-of-the-box. So better tell the user to first try "scanimage -L" and only if that doesn't show the scanner give some trouble-shooting tips. | (including sane-plustek, sane-qcam, sane-ricoh | sane-sharpsane-snapscansane-umax and so on. Typos: Missing space and closing parenthesis. | For a full list try apropos sane. Mentioning "man sane" may also make sense here. Don't forget to point to dll.conf. Some distributions tend to modify this file and some backends are commented out by default. | 5.2.2. Across a Network | | If you are interested in making scanner services available across a | network from or to a remote machine, you will need to edit the | saned.conf file ...the saned.conf file on the server (where the scanner is)... | in the same directory as outlined in the previous | section. It usually consists of an entry 'scan-client.somedomain.firm' | that will need to be replaced with the hostname of the target machine. ...the hostname of the client (without the scanner)... net.conf of the client should contain the host name of the server. | The saned daemon will need to be run as well as inetd or xined. The saned is run through inetd or xinetd. Typo: xinetd. | In addition port 6566 will need to be open, accomplished by adding the | following line to /etc/services: /etc/services is just a list of aliases, so you can use "sane" instead of "6566". It doesn't open the port itsself, that's done by (x)inetd. | WARNING: If you plan on running saned across a network it would be | wise to use a separate 'saned' group for those with scanner | privileges, as allowing suid root processed in a network setting is | highly discouraged for security reasons. The saned user/group should be used in (x)inetd.conf. It shouldn't be used by the users themselves. The idea is to give saned as little permissions as possible. | 5.2.3. Using SANE with a Video4linux Device | | Check the configuration directory where you found sane.conf. saned.conf. | There should be a file named 'v4l' v4l.conf. | Opening this file yields the following content (at least on my system): | #/dev/bttv0 | #/dev/video0 [...] The device files are not commented out in original sane-backends source code. Probably this was your distributor. | 6. Testing Your Scanner | sane-find-scanner -v Start with the easy stuff. Nobody likes to scroll through all these details. If "sane-find-scanner" doesn't print anything, "-v" or even "-v -v" can be added later. | If your scanner isn't identified by any of the above, but you're | pretty sure you've done everything right up to now, you can try | scanning as outlined in the next paragraph. If the scanner is not listed with -L, but scanning works with -d backend:/device, the reason is that the backend is commented out in dll.conf. | scanimage -d /dev/scanner0 --format pnm > outfile.pnm The format of -d is "backend:/device_name". The device_name is backend-specific. | 7. Sane Frontends scanimage is also a SANE frontend. | Now that you've got the hardware working, you should probably acquire | a suitable frontend if you plan on using your scanner device in | X-windows (which unless you have SVGAlib installed is probably a good | idea so you can see what you've scanned). Just nitpicking :-): | The X Consortium requests that the following names be used | when referring to this software: | | X | X Window System | X Version 11 | X Window System, Version 11 | X11 There are more frontends than just xsane and xscanimage. You can add a link to the SANE frontends web page, which provides a list of them. | 8.1. If your device cannot be found... It's relatively easy to check if it's a permission problem: Try as root. If it works now, it's most probably casued by permissions. | 8.2. What if SANE can't identify (or correctly identify) my USB scanner? I wouldn't mention the Linux source code at all. There is no need to download or install it. If the device is listed there, it will be detected by the scanner driver. If not, it won't help at all. Better point to the list of USHB devices on linux-usb.org or explain how to read /proc/bus/usb/devices or syslog to get the numbers. Bye, Henning From henning@meier-geinitz.de Tue Jun 3 14:09:37 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 15:09:37 +0200 Subject: [sane-devel] Compiling SANE backends on Mac OS X 10.1.5 In-Reply-To: <20030603043000.5308.qmail@web13404.mail.yahoo.com> References: <20030603043000.5308.qmail@web13404.mail.yahoo.com> Message-ID: <20030603130937.GB817@hmg1> Hi, [MacOS X sanei_scsi.c fails to compile] On Mon, Jun 02, 2003 at 09:30:00PM -0700, David Alan Hjelle wrote: > I was trying to compile the lastest CVS snapshot (from June 2, 2003) of > SANE backends, but I ran into some problems. Does sane-backends 1.0.12 work? > ./configure ran no problem. Try "./configure --disable-warnings" to avoid some of the warnings. > sanei_scsi.c:4444: illegal statement, missing `;' after `io_object_t' I think that's a real bug, the line marked "->" is 4444: if (ioReturnValue != kIOReturnSuccess || masterPort == NULL) return SANE_STATUS_IO_ERROR; -> io_object_t scsiDevice = NULL; int i; There are variable definitions after the code. I don't know if C99 allows this, but older C doesn't. That's C++. > Wow, that was really long. Sorry. I hope that was enough info, though. The core foundation warnings may be because of the enabled warning option in configure. > I hope you can help. I'd love to get this scanner working again. The MacOS X support for sanei_scsi is from Mattias Ellert . I'm cc'ing him in case he doesn't read sane-devel. Bye, Henning From joseos@okstate.edu Tue Jun 3 19:08:16 2003 From: joseos@okstate.edu (Jose Sanchez) Date: Tue, 03 Jun 2003 11:08:16 -0700 Subject: [sane-devel] Microtek SlimScan C3, output always a black image In-Reply-To: <200306022117.24137.karsten.festag@gmx.de> References: <3ED27A5A.8050400@okstate.edu> <200305271856.47694.karsten.festag@gmx.de> <3ED56CD9.7080608@okstate.edu> <200306022117.24137.karsten.festag@gmx.de> Message-ID: <3EDCE410.7040206@okstate.edu> This is a multi-part message in MIME format. --Boundary_(ID_hq7rBUcoNaeO1D2bhXCQiw) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit Hi Karsten, thanks again for the help. >please look into your BIOS and make sure the parport mode is set to EPP, not >ECP! I heard several times that this is the cause for stretched or shifted >image lines. > You were right my BIOS was configured with ECP+EPP I leave it as EPP and the image was not stretched neither shifted. >By the way: switching off the backend calibration has a negative side effect: >you will probably see fine vertical stripes on your scanned images. Normally >the backend calibration gets rid of it, but it looks like we have to find the >bug in the calibration code so that it works with your scanner. Please tell >me if we shall do some work in this direction - I'll need some testing work >on your side to achieve this. > I noticed,as you said, that there are some fine vertical stripes on the scanned images. I am willing to help in what ever you need to fix this problem. Just tell me what to do. >Could you please tell me what error message appears if you use the '-y20' >option to generate a logfile? > Well this error appeared when I was looking for help in the suse mailing list, then they told me to post my problem in the sane development list. In the log file I sent they told me there was the following line: scanimage: argument without option: `y20' However, I ran it again exactly as before and I was looking for that line and I don't find it. I attached the zip file with the scanned image, the new log file and the config file. I hope this will help in something, tell me what you need I and will be glad to help. Thanks Jose --Boundary_(ID_hq7rBUcoNaeO1D2bhXCQiw) Content-type: application/x-gunzip; name=output.tar.gz Content-disposition: inline; filename=output.tar.gz Content-transfer-encoding: base64 H4sICLzj3D4CA291dHB1dC50YXIA7Zxbb9vGEsf97E+xQB+SFJLDuy6ACrROmhanSYo4PThF EAgrcmmzpUiWXMXWeehnP7NLUhIvujinSZP0/zN9Ibkze5nd2dklrXQls5V8fPYhMQzHGLku /TaMkefo36ZT/q44oxveyPRMz6F0pmlbozPmnn0EVoXkOWNnv6WFOJxO5MXZF0da2n8Z+Xkq xe/WhZ8m4V9tf9MwvMreffZ3TVfb3zZcx3Y8Su8YnnfGDNj/g/MVuxKCFTwRw00feOg+YmGa M84CUfh5lMkoTVgaMnkjWKrPivPz8g8WrJYZs86/qk7j6PpGxlEwtF2WJpvLSTpccP93mdOP YXWNbld/FZIyGd4IJctM58I4P0lM3RJJMPR5HC1y3rrbKkl1VabX17EYxpxKvZs2ETyXQ76S KQ9+oz6xc9NP4zRf8JgnvhjWd8PwvPCLiH1NX1c+TxKRn59/vuO/oCpcxOn1h/H/B8e/azlb /2+4nhr/lpouMP4/Am/U0I/mgVisrt+SL5AySq6ZPmWxeCdiNe43noGGD7ONi/M3mytvte+Y R0kkp+z5Jt3Dd8bFxGWLVRQHzDIMm+Z01zJd8iwFXxfsRsRxenHR1JTxvBBzNQFF1/MwisWU hdnMuBurPmIbjbT+jfB/n5cjdMqKqtzakcwrR0JlVb5E05DlUnL/Zp4mlEHCl2L24HEg3j0u rs0HzXRBQA3zLvLFPI4Kql95sje5VnsslfIa1Fx/rKJ8PaWWreo3cp3BEck3ldTbxlXTGhhG dXj6Z69QLopVLJuihqflLHW4i60aa8/REKbzkT3w6DAHntCHOxhZKp1t68MYOPbAtfuEbUon VArbG/Bwm/O+o1lsY3Cv4xMRVhPlnOeCT1nDJo1EGmNKpqFOaxmWuyj7LzV380ulo/Fz8Ya+ WU1HlelNSXJkezZF1oK+3JFFF2yF4diuXatiRTmHMUY3Lq96VNnWlL4tYRu2x8OqVEYLldC6 MDxVMl28i/YYVzjjaVeyT1WtYb8qz/nLVI2Nv0RV6Zi2AzzYDHCj6weoNwRz8ht5tFhJURz1 BwNWpKucLjV1vamst9XUHOjWWPXGsdXun+X1I6rKXtrSGFiDiam1mAPL1w6EdE0GIbmUYMBH 9XW/utg/jMKwOibjbaFsrdQYa8dkDERXOHS0cNN19Iy1Pe3aSNk4qQI5tpVkYZ4uKzuo2WXl y1UuGkKzE+nN6ccn7f7z5y6tTvpvinYpLn9BcxZrMmUP6j8ftISepwHN4j0yWqge99Wwbwu/ opoXKghmPcJqpPfndkk/uwLGHQ+brRBHS9US7NJmj9nPNzyR1Nq27fl3LbVPSgu8XmeipVyp NTz2sGrRR4OWZN3SUom2CvR9zOVCBHUjtCVXWZbmku5Xa54dyW9pobCkFYfPgtRfLUUiWShE IPIpe5F2PfpeXuc8KSjuEYm/ZksRRJyiDp7JeytSBaIAKqOaBkIKX4VD91URvFNLnIBlke7l rFgXUizvqeVKhWBqyN1PihZqvUK6e9BQlJ0+OGW/imL/WGbsxyW/VkHhJc/4IoojGYmi6/j/ 7KeV6lKtAbeTZH/+jL1YLRd0P+NFIYo6manPOwOrSOOV3B1aU/af4ZLfTdVkSzNNkEXn7Di/ 1jJeJdPM55lIl0Lm60bDVRep995GgaSQlVmua7BMFuzh+MI1Hjx4dIrttmrKiJsCBIeCfq3G NC88t6vnJY0kWq6zfFv9qaptjxcp2ub+qVykT8tz6ikntM4PPA6lDvQrmVOqlfP1dNu+ZOQT MtIdZLor1HZgmbzpVOlFtFjEos7xtOKZxnARyaFfZniijPUeMs57yHgHZYLHejn5w2saEZJ8 XKLboJ3qO1o0kvvaTUZOvpXop19eM39nYJfNSZY+5BGeR4VPC09asKaroiF+sl/o9Q5PuORq x4xmhGZ3ZYu13luiiJ/RutbnUiRczSiF+GNFPl8MTmnV20jepCtZbkSRqoCGkEzzXhd1VSnu ma/v4Y4V390z/bN7pn/VSv9LoZx1GgfkG3mgnLe4klySocqW7ZvX9V5FlKvprjU/TFlebwLE ImwLX14+Ydc821c06m7abEWPWBbdibjYI6bcaFtGbU6y25tIinJ7QrA49Xld4CkbmobT7qf8 julNTUaxgd8TSTnj/omHBlcskqKnZGZPFslG6JY6VXpb7Aq0c7i64YFqbqkilpDEwlWy0+w6 DDM6k1zAqo3TPe1lt0We5UIk+4VIxGm31nfxShzIRol4HRcThr0xYS3yiqrakvn+6c+vXj5n +/tMy5FtF3hlHDUvdG9uLgkHLAxmw6Zx3iihUqYU6V3MmZ39hkl3MdfW1LsL5Oj1ltYx5vv3 L/Q+37WQ1ZYYVUT143ieJvF6ZmAnDDth2AnDThh2wj6tnbAvbhZS9SFbyPkqiaSuWdm36p7R zFqlVAl1urdHXFh3ukszkRx97HPPp0T9ydk2OeOxLq5aNKgkmFoxtWJqxdSKqRVT64ecWtU7 HNUbFVSJG54EsSgrYgf2eE+vUAvCeCXnRfRfceAxWzNZqwfWN2aOMfHKU5HIfF1etLrTsnpl R+4UcVPI97SP/dmsv6uaV2++sdabb+0WV8NsnvGcL4UUeY9R+yWWaSDmlJLilEw9HXg/KXU+ c5V/odMZ9Z9FJIt5lpHb2j1LV1KdZjm5IXHb07s6legq3iqtFR7XoibGGYUS7M6cmbY3GZTP QmamSaZla3NGXaN8rDGz7Ob+Udmnyv2weaQ2KqlQxZ726Uusrqm9tHJXMOCSd8qrLVsW+Jjd yh3GJ9G7qFC77mZ3EBTUV+47CJTMgUHATx8EbU2qvq0hMLlH8F9Q65T7lc1WJwMmwcxs5y3L tP4yaNXA6Q+nHLevBpWWGzKcyN8ej9fsYJ+KRbpnIVLOZSTqNzR1p69204VeY14b14fh6gmu bNX67qmh5ljnPK4lyysN4e7t3it7XLIeCTRqw/TA2NH+U6dUCXvdcKfgptHvhjdqen1w3Xk3 bWkGA2G1+7XqpP4gtE6pVJbFM/U4QDmleDby1F/6mcKMXE0ulpw8ljce9wVst5wmYiroUd/S znkztu8rsCqEfvKir7LyKtvThgfmRPuEFcrnMivfxyVtW1TFNg2ftNBPGvQVz3UmxmHh+uFK LJJrmou6/WNrhq5DG3fqXnfXdqFpslXvnGymJeWR285001e/VndnD5MofvT3Rn6fxUwWnNZt EJ19sOjsc3Ewwb1ini+j21NU669iLsX8mi+XHZ+TpcXWUw7K9x2UpXWf6rzc0VEWcl+SAHWQ JTU3U9Nv9fo/LV6lyIrGlROV7iuhuy2h+WmW0NuW0PqoJfyiw3TKerz9aegw250c3dR1BpNg e0/4h8J0E2H6wTDdHJibBwn2wN3pIXbdkAuunlOcGqZT4Kqj9LFr1YGP622idGc0Mq3e+KkM 7uqAu79xtiNMb+DUK/rDIfo/ZAXgpxTspfFcRRttL9GZ0JbF8JuNwFq9mz9j5QToip4guUqq VPeVdNIJlZ09PXJH0YE++bk9KILwlyM8HlcHOVXTbArTuUWHpQ6HDkcdY6cSoImHEpRHmaY5 VGoBx2ln0qu3IXwgk169zWLvz6RXb7vY+zLp1dsQPtpCLb3NOh9roZbetqkOt1BLb8dUJ5iX DsPv9LAeZ7x9N9R8UFSvL2s3uNaPEK1xc5VPdwORFJsthU5UWk6zf+sGQq6jwnmWp74oiiNb 9rsJW7syOh7YjRPUX9U9HUGQPDWjiiccWrgWuU9xgs5qNAlc4323j04Q7ivo/7F9VIdRe98E 3V2xly9pq4VDzAsKXtQdfVY103ENmx2DZkzmTLqiqhp9jyjLhl6EYeiJkVqf8Dtqi5ltjbym ieMsLt/H11bu2QDbk9pPs/W8fAW83cX1++YyVW+bq3rr9dSsNcShCIo+KUU7o+lrNVLG5sT6 oMMNpvjoNlVTI2wKm8KmsClMAVPAprApbAqbwqYwBWwKRbDp/SpuOePxB6j4jhb1kxmsfMo5 /IY9ffl9c7c9FjxZZfPq32jalVJPSovO81Ot31cfkhAfeWmsTBmnxaEnzyeWofWvL1q1uIvk 9H0/W6CbtAj0f1LOw1yIYE9u7PmPl69evn76L6v8/NHrNA0Wa3FxfvYPp/78X/p9kSXLj//5 v6btjGyr9fm/tuHg838/Cj9751+xq29fPNX/hsLCNI7T2+LcGtvM9c4t1/3HjxAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAACn8D+5GpuAAEABAA== --Boundary_(ID_hq7rBUcoNaeO1D2bhXCQiw)-- From jb@jblache.org Tue Jun 3 17:11:32 2003 From: jb@jblache.org (Julien BLACHE) Date: Tue, 03 Jun 2003 18:11:32 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC8673.7060601@sbox.tugraz.at> (Gerfried Maier's message of "Tue, 03 Jun 2003 13:28:51 +0200") References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <87brxfxz56.fsf@frigate.technologeek.org> <3EDC8673.7060601@sbox.tugraz.at> Message-ID: <87y90jw37v.fsf@frigate.technologeek.org> Gerfried Maier wrote: >>If you do not need IPv6 support, configure sane-backends with >>--disable-ipv6 and it'll build fine. > > Unfortunately not. Same error. Oh, yes, sorry. My bad. Well, has Henning said, this is a bug in certain versions of the libc, as the relevant RFCs document a ss_family member in struct sockaddr storage. Comment the definition of SANE_USES_AF_INDEP in saned.c, and it'll fall back to the IPv4-only code, which do not use this particular structure. You may need to do the same in backend/net.c. I'll look into adding a check to configure. JB. -- Julien BLACHE From jb@jblache.org Tue Jun 3 17:46:37 2003 From: jb@jblache.org (Julien BLACHE) Date: Tue, 03 Jun 2003 18:46:37 +0200 Subject: [sane-devel] [PATCH] backends 1.0.12 compile-error In-Reply-To: (Erik Inge Bols's message of "Tue, 3 Jun 2003 13:46:19 +0200 (CEST)") References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC85C3.4040309@sbox.tugraz.at> Message-ID: <87u1b7w1le.fsf_-_@frigate.technologeek.org> --=-=-= Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Erik Inge Bolsų wrote: > ... anyone feel like adding a configure check and a patch for this? > Probably a certain libc or a certain distro has this problem. Patch attached. Apply, run aclocal, autoconf, autoheader. Maybe I should ask for cvs write access, someday :) JB. -- Julien BLACHE --=-=-= Content-Disposition: attachment; filename=ss_family-check.diff Content-Description: Check for ss_family or __ss_family --- sane-backends-1.0.12.orig/acinclude.m4 2003-05-15 12:51:16.000000000 +0200 +++ sane-backends-1.0.12/acinclude.m4 2003-06-03 18:34:09.000000000 +0200 @@ -353,6 +353,7 @@ # # Check for AF_INET6, determines whether or not to enable IPv6 support +# Check for ss_family member in struct sockaddr_storage AC_DEFUN([SANE_CHECK_IPV6], [ AC_MSG_CHECKING([whether to enable IPv6]) @@ -383,6 +384,38 @@ ipv6=no ]) fi + + if test "$ipv6" != "no" ; then + AC_MSG_CHECKING([whether struct sockaddr_storage has an ss_family member]) + AC_TRY_COMPILE([ + #define INET6 + #include + #include ], [ + /* test if the ss_family member exists in struct sockaddr_storage */ + struct sockaddr_storage ss; + ss.ss_family = AF_INET; + exit (0); + ], [ + AC_MSG_RESULT(yes) + AC_DEFINE([HAS_SS_FAMILY], 1, [Define to 1 if struct sockaddr_storage has an ss_family member]) + ], [ + AC_TRY_COMPILE([ + #define INET6 + #include + #include ], [ + /* test if the __ss_family member exists in struct sockaddr_storage */ + struct sockaddr_storage ss; + ss.__ss_family = AF_INET; + exit (0); + ], [ + AC_MSG_RESULT([no, but __ss_family exists]) + AC_DEFINE([HAS___SS_FAMILY], 1, [Define to 1 if struct sockaddr_storage has __ss_family instead of ss_family]) + ], [ + AC_MSG_RESULT([no]) + ipv6=no + ]) + ]) + fi ]) # --- sane-backends-1.0.12.orig/frontend/saned.c 2003-05-12 18:34:03.000000000 +0200 +++ sane-backends-1.0.12/frontend/saned.c 2003-06-03 18:39:11.000000000 +0200 @@ -34,6 +34,14 @@ #if defined(HAVE_GETADDRINFO) && defined (HAVE_GETNAMEINFO) # define SANED_USES_AF_INDEP +# ifdef HAS_SS_FAMILY +# define SS_FAMILY(ss) ss.ss_family +# elif defined(HAS___SS_FAMILY) +# define SS_FAMILY(ss) ss.__ss_family +# else /* fallback to the old, IPv4-only code */ +# undef SANED_USES_AF_INDEP +# undef ENABLE_IPV6 +# endif #else # undef ENABLE_IPV6 #endif /* HAVE_GETADDRINFO && HAVE_GETNAMEINFO && HAVE_POLL */ @@ -556,7 +564,7 @@ sin = (struct sockaddr_in *) &remote_address; - switch (remote_address.ss_family) + switch (SS_FAMILY(remote_address)) { case AF_INET: if (IN_LOOPBACK (ntohl (sin->sin_addr.s_addr))) @@ -1022,7 +1030,7 @@ return -1; } - fd = socket (ss.ss_family, SOCK_STREAM, 0); + fd = socket (SS_FAMILY(ss), SOCK_STREAM, 0); if (fd < 0) { DBG (DBG_ERR, "start_scan: failed to obtain data socket (%s)\n", @@ -1031,7 +1039,7 @@ return -1; } - switch (ss.ss_family) + switch (SS_FAMILY(ss)) { case AF_INET: sin = (struct sockaddr_in *) &ss; @@ -1071,7 +1079,7 @@ return -1; } - switch (ss.ss_family) + switch (SS_FAMILY(ss)) { case AF_INET: sin = (struct sockaddr_in *) &ss; --=-=-=-- From JayGuerette@pobox.com Tue Jun 3 17:57:29 2003 From: JayGuerette@pobox.com (Jay Guerette) Date: Tue, 03 Jun 2003 12:57:29 -0400 (EDT) Subject: [sane-devel] Analysis of saned CPU utilization Message-ID: <30058.209.202.195.145.1054659449.squirrel@mail.guerette.net> First off, my deep thanks to everyone who has made sane possible. I am ecstatic that I can use my scanner on my Linux box, and also make it available to Windows clients over my network. I've experienced, and seen a few references to similar experiences on the web, saned consuming all available CPU when in use. After running a strace while it was doing this, and examining the source to saned, it appears that it is locked in a tight select loop with no timeout. It is definately not the ideal way to poll for data, and at the very least there should be a short timeout to release CPU cycles to other processes. Was this a deliberate design choice? If it is a flaw, what is the best way to get it fixed? Should I fix it and submit a patch, or try to take it up with whomever maintains that particular frontend? Regards, Jay Guerette From fzago@austin.rr.com Tue Jun 3 13:09:50 2003 From: fzago@austin.rr.com (Frank Zago) Date: Tue, 03 Jun 2003 07:09:50 -0500 Subject: [sane-devel] Compiling SANE backends on Mac OS X 10.1.5 In-Reply-To: <20030603043000.5308.qmail@web13404.mail.yahoo.com> References: <20030603043000.5308.qmail@web13404.mail.yahoo.com> Message-ID: <3EDC900E.2050409@austin.rr.com> I'm not an OSX user, but it seems this (sick pice of) code needs to be compiled with a C++ compiler, or at least a C compiler with non-standard extensions. You can try CC=g++ ./configure and recompile. Frank. David Alan Hjelle wrote: > Hello. > > I've been trying to get my Microtek SlimScan C6 cheap-o scanner to work > under Mac OS X for a while now, and just recently ran across SANE. I > figure I should be able to use SANE with the GIMP, which I use somewhat > regularly. > > I was trying to compile the lastest CVS snapshot (from June 2, 2003) of > SANE backends, but I ran into some problems. > > ./configure ran no problem. > > make, however, eventually gave me the following errors (Or, at least, > these are the errors deaing with the sanei_scsi.c file that seemed to > be the cause for the compilation problem. I think everything else was > just warnings. Of course, what do I know? I'm only just teaching myself > C programming and have only had experience in VB and Java .): > From henning@meier-geinitz.de Tue Jun 3 20:34:22 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 21:34:22 +0200 Subject: [sane-devel] [PATCH] backends 1.0.12 compile-error In-Reply-To: <87u1b7w1le.fsf_-_@frigate.technologeek.org> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC85C3.4040309@sbox.tugraz.at> <87u1b7w1le.fsf_-_@frigate.technologeek.org> Message-ID: <20030603193422.GA1001@hmg1> Hi, On Tue, Jun 03, 2003 at 06:46:37PM +0200, Julien BLACHE wrote: > Patch attached. Apply, run aclocal, autoconf, autoheader. I'll have a look at this one later. > Maybe I should ask for cvs write access, someday :) Good idea :-) bye, Henning From stef-listes@wanadoo.fr Tue Jun 3 23:49:01 2003 From: stef-listes@wanadoo.fr (stef) Date: Tue, 3 Jun 2003 22:49:01 +0000 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org In-Reply-To: <3EDB6ACF.3010304@charter.net> References: <3EDB6ACF.3010304@charter.net> Message-ID: <20030603224901.GA931@wanadoo.fr> On Mon, Jun 02, 2003 at 10:18:39AM -0500, Howard Shane wrote: > I would like to announce the completion of the initial draft of the > Scanner-HOWTO for the linux documentation project, and invite > participants on the SANE-devel mailing list to comment on it. > > The goal of this document is to bridge point A (scanner) to point B > (scanner running successfully in linux) for the relative newbie as > efficiently as possible. As such it should not be too technical, it > should cover the most common hardware interface types, the required > steps to reach a working result, likely pitfalls and how to recover from > them, and places to go for help. It is not designed to be an exaustive > list of harware in/compatibilities. > > Any help you can suggest to clarify or otherwise improve the draft will > be greatly appreciated and may even result in you being mentioned in the > credits if you so desire. > > The document can be found at: > > http://ibiblio.org/gferg/ldp/Scanner-HOWTO.html > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel Hello, I've parsed it a bit, and I must say that you're painting the picture darker than it really is for parallel port scanners. Parallel port scanners listed in SANE do work. No need to frighten people. I'm a bit skeptic about favouring ECP mode. It may be wise for printers, but I think it is useless for scanners, unless you use some patch that bring DMA reads. From a quick grep in SANE docs, EPP or ECP/EPP seems to be the recommended setting. By the way, an EPP scan is way faster than PS/2 or bidirectional mode. Also, I don't think unidirectional mode is suitable for scanning. Regards, Stef From jb@jblache.org Tue Jun 3 21:58:35 2003 From: jb@jblache.org (Julien BLACHE) Date: Tue, 03 Jun 2003 22:58:35 +0200 Subject: [sane-devel] Analysis of saned CPU utilization In-Reply-To: <30058.209.202.195.145.1054659449.squirrel@mail.guerette.net> (Jay Guerette's message of "Tue, 03 Jun 2003 12:57:29 -0400 (EDT)") References: <30058.209.202.195.145.1054659449.squirrel@mail.guerette.net> Message-ID: <87llwix4hw.fsf@frigate.technologeek.org> Jay Guerette wrote: > I've experienced, and seen a few references to similar experiences on the > web, saned consuming all available CPU when in use. > > After running a strace while it was doing this, and examining the source > to saned, it appears that it is locked in a tight select loop with no > timeout. Could you give some more details ? select() is only used once in the code (not counting the poll() in main(), or the select() that's used instead on platforms where poll() doesn't exist -- that's for 1.0.12). A testcase would be nice. To answer your question, patches are always welcome :) JB. -- Julien BLACHE From Franz Bakan" Message-ID: <20030603212008.5D8E0E9E@panda.mostang.com> Hi, On Fri, 30 May 2003 16:53:29 +0200, Henning Meier-Geinitz wrote: >> 1.0.12 configures and compiles fine on OS/2 with gcc 2.8.1 as well as= with gcc 3.2.1. > >Nice. The current entry on the platforms list is for "OS/2 4.5 >(eComStation)". Is this still correct? Yes >USB isn't supported? There is some support. One guy in Japan (Maeda Haruyuki) managed to compile a version that has = been reported to work with some epson-usb-scanners on OS/2. He used the sane-sources for his special build with some OS/2 specific changes. He compiled not with gcc but with IBM VAC++. The binaries are bundled with the TAME-frontend for OS/2 (not a 'real' frontend but a rexx-pm-gui that calls scanimage.exe a= t the end). See http://www.os2world.com/goran/tame.htm >What about >dynamic loading of shared libraries? I don't know, I don't exactly know what this means. Can DLLs (_dynamic_ linked libraries) be loaded _static_? On OS/2 we have just one (big) libsane.dll that contains all backends-co= de and works together with (small) scanimage.exe xscanimage.exe xsane.exe e= tc. These exes won't start if libsane.dll is not found. >> there is probably an error in line 2623 of >> sane-backends/po/sane-backends.fr.po >> that prevents iconv from recoding this file to ISO-8859-1 after this = line. > >Thanks. Fixed in CVS. There was one more occurance of a wrongly >encoded "=E9". Thanks, I now just uploaded a binary-os/2-package of the 1.0.12/1.0.11 backend-frontend combination including this minor fix to http://home.tiscalinet.de/fbakan Bye, Franz From peter@pscomp.com Wed Jun 4 02:19:12 2003 From: peter@pscomp.com (Peter Santoro) Date: Tue, 03 Jun 2003 21:19:12 -0400 Subject: [sane-devel] Re: epson: scanimage threshold option not working in 1.0.12 backend Message-ID: <3EDD4910.5000002@pscomp.com> Karl, I also noticed that Epson's ISCAN GUI no longer works after installing the SANE 1.0.12 backend. ISCAN has a setting for threshold, so it is probably the same bug. Using scanimage directly (not via my code) only works if the threshold option is not used, so I doubt it's my code. Also, "scanimage --help" shows that the threshold option is inactive, so the problem is probably somewhere in the initialization code. BTW, I'm using kernel 2.4.20 (RedHat 7.3 and Slackware 8.1) and USB 1.1. Peter From JayGuerette@pobox.com Wed Jun 4 13:54:35 2003 From: JayGuerette@pobox.com (Jay Guerette) Date: Wed, 04 Jun 2003 08:54:35 -0400 (EDT) Subject: [sane-devel] Analysis of saned CPU utilization In-Reply-To: <87llwix4hw.fsf@frigate.technologeek.org> References: <30058.209.202.195.145.1054659449.squirrel@mail.guerette.net> <87llwix4hw.fsf@frigate.technologeek.org> Message-ID: <1329.10.0.1.10.1054731275.squirrel@mail.guerette.net> >> I've experienced, and seen a few references to similar experiences on >> the web, saned consuming all available CPU when in use. >> >> After running a strace while it was doing this, and examining the >> source to saned, it appears that it is locked in a tight select loop >> with no timeout. > > Could you give some more details ? select() is only used once in the > code (not counting the poll() in main(), or the select() that's used > instead on platforms where poll() doesn't exist -- that's for 1.0.12). > > A testcase would be nice. I'll play with the code a bit, and come up with more detail. From keeper@neo.rr.com Wed Jun 4 10:49:00 2003 From: keeper@neo.rr.com (Michael Rasile) Date: Wed, 4 Jun 2003 09:49:00 +0000 Subject: [sane-devel] Canon Lide 30 backend Message-ID: <20030604094900.GA7629@watcher.WorkGroup> Greetings! Am trying to get my USB canon Lide 30 scanner to work under Gentoo. USB has been compiled into the kernel and when I do sane-find-scanner, the scanner is found. However, when I do scanimage -L the scanner is not found and therefore I am unable to use xsane. I was wondering what backend I should be using for this scannerand how should this be setup in /etc/sane.d/ I have tried everything, editing the canon.conf and the plustek.conf. I know the scanner works because when I was using Mandrake 9.1 I didn't have a problem setting it up. I would like to continue to use it under Gentoo. Any suggestions will be greatly appreciated. I've read a great deal about this, but nothing seems to help. Thanks for anything. -- Regards, Mike keeper@neo.rr.com "Don't Fear The Penguin." From christoph.bier@web.de Wed Jun 4 17:37:04 2003 From: christoph.bier@web.de (Christoph Bier) Date: Wed, 04 Jun 2003 18:37:04 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030603092448.GA5732@hmg1> References: <20030602111526.5b4034a3.christoph.bier@web.de> <20030602135832.GA30314@meier-geinitz.de> <20030602174212.0ce77aa9.christoph.bier@web.de> <20030603092448.GA5732@hmg1> Message-ID: <3EDE2030.9080306@web.de> Henning Meier-Geinitz schrieb: [. . .] > Oh well. Either a hardware problem (too slow to react?) or a kernel > bug. Check the linux-usb-users mailing list for this one, I remeber I did so. > that other people had similar problems, but not with scanners. Maybe > that's a problem with your USB chipset, but I don't remeber the > details. It doesn't seem to be an issue of the scanner module or sane. Ok. [. . .] >>Is there a possibility to turn such "hotplugging >>magic" off? > > Yes :-) For the details, consult your distribution's documentation. A Ok, thanks :-). > rather drasti way is to renam the /sbin/hotplug program to something > else. Thanks again for your help! Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier@wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From henning@meier-geinitz.de Wed Jun 4 19:09:34 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 4 Jun 2003 20:09:34 +0200 Subject: [sane-devel] compile 1.0.12 on OS/2 In-Reply-To: <20030603212008.5D8E0E9E@panda.mostang.com> References: <20030530145329.GC3433@hmg1> <20030603212008.5D8E0E9E@panda.mostang.com> Message-ID: <20030604180934.GA3795@hmg1> Hi, On Tue, Jun 03, 2003 at 11:20:04PM +0200, Franz Bakan wrote: > >USB isn't supported? > > There is some support. Thanks for the information. I'll add links and update the list. > >What about > >dynamic loading of shared libraries? > > I don't know, I don't exactly know what this means. > > Can DLLs (_dynamic_ linked libraries) be loaded _static_? The dll backend can either load other backends dynamically (on demand) or all the backends are linked into sane-dll (preloading). Last but not least sane-dll can be linked statically to the frontends (inclusing all the preloaded backends). > On OS/2 we have just one (big) libsane.dll that contains all backends-code > and works together with (small) scanimage.exe xscanimage.exe xsane.exe etc. That's shared but not dynamic. Bye, Henning From henning@meier-geinitz.de Wed Jun 4 19:17:53 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 4 Jun 2003 20:17:53 +0200 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030604094900.GA7629@watcher.WorkGroup> References: <20030604094900.GA7629@watcher.WorkGroup> Message-ID: <20030604181753.GB3795@hmg1> Hi, On Wed, Jun 04, 2003 at 09:49:00AM +0000, Michael Rasile wrote: > Am trying to get my USB canon Lide 30 scanner to work under Gentoo. The Lide 30 is supported by the plustek backend. > USB has been compiled into the kernel and when I do > sane-find-scanner, the scanner is found. However, when I do scanimage > -L the scanner is not found and therefore I am unable to use xsane. Try "SANE_DEBUG_PLUSTEK=255 scanimage -L" to find out what's wrong. > I > was wondering what backend I should be using for this scannerand how > should this be setup in /etc/sane.d/ The plustek backend is the right one. You can find out about which scanner is supported by which backend by using the scanner search engine: http://sane.informatik.uni-freiburg.de/cgi-bin/driver.pl The setup of the config file is explained in man sane-plustek. But ususally this should work without manual intervention. Also check that "plustek" is in dll.conf. Bye, Henning From henning@meier-geinitz.de Wed Jun 4 19:35:44 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 4 Jun 2003 20:35:44 +0200 Subject: [sane-devel] Please test sane-backends (and sane-frontends) on non-mainstream os and platforms Message-ID: <20030604183544.GC3795@hmg1> Hi, I'd like to update the list of platforms SANE can be compiled and used on. There is a temporary file with the latest updates here: http://www.meier-geinitz.de/sane/tmp/sane-support.html If you've successfully compiled and/or tested sane-backends 1.0.12 and/or sane-frontends-1.0.11 on any of the mentioned platforms that isn't up-to-date yet, please contact us. Also if the platform is mentioned, but there is a question mark for SCSI or USB support, please tell us if you were able to actually scan with a real scanner. If you have access to a platform but it has no scanner please try at least the test backend: "scanimage -d test -T". Any other corrections or additions are also welcome. Thanks, Henning From soumarmt@nerim.net Wed Jun 4 20:57:27 2003 From: soumarmt@nerim.net (Thomas Soumarmon) Date: Wed, 4 Jun 2003 21:57:27 +0200 Subject: [sane-devel] CVS freeze ? Message-ID: <200306042157.27319.soumarmt@nerim.net> Hi everybody, Sorry for the silly question but I have been a bit SANE-offline for a while, and I didn't find quickly the answer in the mail archive. I wanted to commit into CVS some changes about the hp5400 backend. Is there a CVS freeze at the moment or may I do it ? And before that, is there a compile farm or some kind of, to verify at least it compiles ok on various platforms before commiting it ? Thomas. PS : changes are not functional, they are "only" to make a synchronization between hp5400backend sourceforge CVS project and SANE CVS project. PS2: I have been messing around a lot before finding the DEBUG_NOT_STATIC trick to avoid the missing symbol sane_debug_hp5400_call !!! From jb@jblache.org Wed Jun 4 21:22:59 2003 From: jb@jblache.org (Julien BLACHE) Date: Wed, 04 Jun 2003 22:22:59 +0200 Subject: [sane-devel] CVS freeze ? In-Reply-To: <200306042157.27319.soumarmt@nerim.net> (Thomas Soumarmon's message of "Wed, 4 Jun 2003 21:57:27 +0200") References: <200306042157.27319.soumarmt@nerim.net> Message-ID: <87el29384c.fsf@frigate.technologeek.org> Thomas Soumarmon wrote: > I wanted to commit into CVS some changes about the hp5400 backend. > Is there a CVS freeze at the moment or may I do it ? The freeze is over :) > And before that, is there a compile farm or some kind of, to verify at least > it compiles ok on various platforms before commiting it ? SF.net has a compile farm (never used it), otherwise there's the HP/Compaq testdrive (http://testdrive.hp.com) but Henning knows more about this one than I do :) JB. -- Julien BLACHE From henning@meier-geinitz.de Wed Jun 4 21:25:28 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 4 Jun 2003 22:25:28 +0200 Subject: [sane-devel] CVS freeze ? In-Reply-To: <200306042157.27319.soumarmt@nerim.net> References: <200306042157.27319.soumarmt@nerim.net> Message-ID: <20030604202528.GH3795@hmg1> Hi, On Wed, Jun 04, 2003 at 09:57:27PM +0200, Thomas Soumarmon wrote: > Sorry for the silly question but I have been a bit SANE-offline for a while, > and I didn't find quickly the answer in the mail archive. Search for "release" and/or freeze in the archive. Or check the Changelog in CVS for messages like this: ****** Release of sane-backends 1.0.12. End of code freeze ****** > I wanted to commit into CVS some changes about the hp5400 backend. > Is there a CVS freeze at the moment or may I do it ? You can commit whatever you want :-) By the way, I changed backend/Makefile.in to not link hp5400 to sanei_config2.lo. That shouldn't affect your backend because you don't use that code at all. > And before that, is there a compile farm or some kind of, to verify > at least it compiles ok on various platforms before commiting it ? If you like, you can use the Hewlett Packard test drive at testdrive.hp.com. They have several Linux, *BSD, Tru64, and HP/UX machines. But setting this up to work at least semi-automatically requires quite some work and some non-linux Unix knowledge :-/ So if you don't want to invest some time into learning how crappy^h^h^h^h^h^h differnt from Linux some systems are, compiling with Linux (and maybe a BSD if you have it) is ok. I'm using the testdrive from time to time and will complain if something doesn't work. > PS2: I have been messing around a lot before finding the DEBUG_NOT_STATIC > trick to avoid the missing symbol sane_debug_hp5400_call !!! The debug macros ARE complex if you use more than one compilation unit. Bye, Henning From lee@trueskill.com Wed Jun 4 23:14:27 2003 From: lee@trueskill.com (Lee Morgan) Date: Wed, 4 Jun 2003 18:14:27 -0400 Subject: [sane-devel] ScanJet 4100C Message-ID: <200306041814.30374.lee@trueskill.com> Hello, I have RedHat 8.0 installed, when I run scanimage I get the following result: [root@shodan sane.d]# scanimage -d hp:/dev/usb/scanner0 scanimage: open of device hp:/dev/usb/scanner0 failed: Invalid argument I have compiled and installed sane-backends-1.0.12 and used the sane-1.0.9.hp.1.01 source. The scanner is detected at /dev/usb/scanner0: [root@shodan sane.d]# sane-find-scanner # Note that sane-find-scanner will find any scanner that is connected # to a SCSI bus and some scanners that are connected to the Universal # Serial Bus (USB) depending on your OS. It will even find scanners # that are not supported at all by SANE. It won't find a scanner that # is connected to a parallel or proprietary port. # If your scanner uses SCSI, you must have a driver for your SCSI # adapter and support for SCSI Generic (sg) in your Operating System # in order for the scanner to be used with SANE. If your scanner is # NOT listed above, check that you have installed the drivers. sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0101) at device /dev/usb/scanner0 But the product string is not reported when i cat /proc/bus/usb/devices: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0101 Rev= 1.00 S: SerialNumber=00MY8BH535KN C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=usbscanner E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms The scanner is a ScanJet4100C. Where am I going wrong? Is this a problem with the scanimage? Regards, Lee From peter@kirchgessner.net Thu Jun 5 05:57:27 2003 From: peter@kirchgessner.net (Peter Kirchgessner) Date: Thu, 05 Jun 2003 06:57:27 +0200 Subject: [sane-devel] ScanJet 4100C References: <200306041814.30374.lee@trueskill.com> Message-ID: <3EDECDB7.6090105@kirchgessner.net> Hi Lee, sane-backends-1.0.12 has the more current backend than sane-1.0.9.hp.1.01. But in your case it should make no difference. Please have a look at your /usr/local/etc/sane.d/hp.conf. It should have lines with # HP ScanJet 4100C usb 0x03f0 0x0101 You can also activate the lines /dev/usb/scanner0 option connect-device if the scanner is not recognized automatically. And please check which libraries are used. The libraries at /usr/lib/sane maybe the libraries which have been installed by your RedHat distribution. And at /usr/local/lib/sane your compiled libraries may be placed. Sincerely Peter Then libusb should find Lee Morgan schrieb: > Hello, > > I have RedHat 8.0 installed, when I run scanimage I get the following result: > > [root@shodan sane.d]# scanimage -d hp:/dev/usb/scanner0 > scanimage: open of device hp:/dev/usb/scanner0 failed: Invalid argument > > I have compiled and installed sane-backends-1.0.12 and used the > sane-1.0.9.hp.1.01 source. > > The scanner is detected at /dev/usb/scanner0: > > [root@shodan sane.d]# sane-find-scanner > # Note that sane-find-scanner will find any scanner that is connected > # to a SCSI bus and some scanners that are connected to the Universal > # Serial Bus (USB) depending on your OS. It will even find scanners > # that are not supported at all by SANE. It won't find a scanner that > # is connected to a parallel or proprietary port. > > # If your scanner uses SCSI, you must have a driver for your SCSI > # adapter and support for SCSI Generic (sg) in your Operating System > # in order for the scanner to be used with SANE. If your scanner is > # NOT listed above, check that you have installed the drivers. > > sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0101) at > device /dev/usb/scanner0 > > But the product string is not reported when i cat /proc/bus/usb/devices: > > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=03f0 ProdID=0101 Rev= 1.00 > S: SerialNumber=00MY8BH535KN > C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=usbscanner > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms > E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms > > The scanner is a ScanJet4100C. > > Where am I going wrong? Is this a problem with the scanimage? > > Regards, > > Lee > > > > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- Peter Kirchgessner http://www.kirchgessner.net mailto:peter@kirchgessner.net From henning@meier-geinitz.de Thu Jun 5 11:06:32 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 12:06:32 +0200 Subject: [sane-devel] CVS freeze ? In-Reply-To: <200306042157.27319.soumarmt@nerim.net> References: <200306042157.27319.soumarmt@nerim.net> Message-ID: <20030605100632.GA22362@hmg1> Hi, On Wed, Jun 04, 2003 at 09:57:27PM +0200, Thomas Soumarmon wrote: > Sorry for the silly question but I have been a bit SANE-offline for a while, > and I didn't find quickly the answer in the mail archive. By the way: Please summarize your changes in the "ChangeLog" file. See http://www.student.uit.no/~pere/linux/sane/cvs-server.html . Bye, Henning From henning@meier-geinitz.de Thu Jun 5 11:25:44 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 12:25:44 +0200 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 Message-ID: <20030605102544.GB11876@hmg1> Hi, Some people reported kernel USB timeouts with their gt68xx based scanners, e.g. Plustek 1247 or Mustek BearPaw series. This seems to be caused by the check if the firmware is already loaded in the gt68xx backend. I've disabled this check for now. If you encounter this problem, get the latest backend (at least 1.0-47) or an unofficial snapshot from http://www.meier-geinitz.de/sane/gt68xx-backend/ . I'll attach a patch against 1.0.12 that contains the work-around. Bye, Henning Index: backend/gt68xx.c =================================================================== RCS file: /cvsroot/external/sane/sane-backends/backend/gt68xx.c,v retrieving revision 1.20 retrieving revision 1.21 diff -u -u -r1.20 -r1.21 --- backend/gt68xx.c 27 Apr 2003 12:43:43 -0000 1.20 +++ backend/gt68xx.c 5 Jun 2003 09:58:45 -0000 1.21 @@ -48,7 +48,7 @@ #include "../include/sane/config.h" -#define BUILD 46 +#define BUILD 47 #define MAX_DEBUG #define WARMUP_TIME 30 #define CALIBRATION_HEIGHT 2.5 @@ -1245,12 +1245,13 @@ DBG (0, " details as possible, e.g. the exact name of your\n"); DBG (0, " scanner and what does (not) work.\n"); } - RIE (gt68xx_device_check_firmware (dev, &firmware_loaded)); + /* RIE (gt68xx_device_check_firmware (dev, &firmware_loaded));*/ + firmware_loaded = SANE_FALSE; if (firmware_loaded) DBG (3, "sane_open: firmware already loaded, skipping load\n"); else RIE (download_firmware_file (dev)); - RIE (gt68xx_device_check_firmware (dev, &firmware_loaded)); + /* RIE (gt68xx_device_check_firmware (dev, &firmware_loaded));*/ if (!firmware_loaded) { DBG (1, "sane_open: firmware still not loaded? Proceeding anyway\n"); From rsv869@adelphia.net Fri Jun 6 04:53:02 2003 From: rsv869@adelphia.net (Reid Vail) Date: Thu, 05 Jun 2003 23:53:02 -0400 Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <3E02B406.7010801@kirchgessner.net> References: <3E02AB22.2010409@adelphia.net> <3E02B406.7010801@kirchgessner.net> Message-ID: <3EE0101E.6010604@adelphia.net> About six months ago Peter gave me some advice about my HP6350c scanner. It fixed my issue and got it working. (I included that exchange at the bottom of this message). Recently I upgraded my Suse box to Suse 8.2 and it's not working again. I dug out the mail and checked the config. Looks OK to me, and I included a few scraps. I've included the output from sane-find-scanner. The permissions also look OK, too, I think. Any suggestions would be great. thx Reid reid@linux:~>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=0x03f0, product=0x0601) at libusb:001:002 # A USB device was detected. This program can't be sure if it's really # a scanner. If it is your scanner, 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. reid@linux:/etc/sane.d> ls -l hp.conf -rwxrwxrwx 1 root root 480 2003-06-05 21:14 hp.conf reid@linux:~> ls -l /etc/sane.d/dll.conf -rw-rw-rw- 1 root root 448 2002-12-18 00:16 /etc/sane.d/dll.conf dll.conf . . # dc210 # dc240 # dc25 # dll # dmc # epson hp # fujitsu # leo # microtek # microtek2 # mustek_usb # mustek # matsushita . . reid@linux:/etc/sane.d> more hp.conf #scsi HP # Uncomment the following if you have "Error during device I/O" on SCSI # option dumb-read # # The usual place for a SCSI-scanner on Linux # # USB-scanners supported by the hp-backend # HP ScanJet 4100C usb 0x03f0 0x0101 # HP ScanJet 5200C usb 0x03f0 0x0401 # HP ScanJet 62X0C usb 0x03f0 0x0201 # HP ScanJet 63X0C usb 0x03f0 0x0601 # # Uncomment the following if your scanner is connected by USB, # but you are not using libusb /dev/usb/scanner option connect-device reid@linux:/etc/sane.d> Peter Kirchgessner wrote: > Hi, > > pleae have a look at /etc/sane.d/hp.conf or > /usr/local/etc/sane.d/hp.conf. It must have two lines in it: > > /dev/usbscanner > option connect-device > > In dll.conf (same directories) the line with "hp" must be active. > You may need to set the permissions: > > chmod 666 /dev/usbscanner > > More hints can be found at http://www.kirchgessner.net/sanehpfaq.html > > Sincerely > > Peter > > Reid Vail schrieb: > >> I've been trying for a least a month to get an HP6350c USB Scanjet to >> work. I'm running a SuSE 8.1 Personal distro, which comes with a SANE >> implementation of 1.0.8-47. >> >> I think (but can't say for sure) that some part of the install of the >> unit (via YAST) isn't working because it doesn't even "test" >> correctly. However YAST does correctly identify it. >> >> When I run xscanimage I get this output: >> >> [xscanimage] No scanners were identified. If you were expecting >> something different, check that the scanner is plugged in, turned on and >> detected by sane-find-scanner (if appropriate). Please read the >> documentation which came with this software (README, FAQ, manpages). >> >> But when I run sane-find-scanner I get this output: >> >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = >> 0x0601) at device /dev/usb/scanner0 >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = >> 0x0601) at device /dev/usbscanner >> >> I make no claims that I'm not missing something obvious! I just >> don't get it. For what it's worth, I know the unit works because it >> runs under Windoze 2K. >> >> Thanks in advance. >> >> Reid Vail >> >> _______________________________________________ >> Sane-devel mailing list >> Sane-devel@www.mostang.com >> http://www.mostang.com/mailman/listinfo/sane-devel >> > > From henning@meier-geinitz.de Thu Jun 5 18:37:33 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 19:37:33 +0200 Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <3EE0101E.6010604@adelphia.net> References: <3E02AB22.2010409@adelphia.net> <3E02B406.7010801@kirchgessner.net> <3EE0101E.6010604@adelphia.net> Message-ID: <20030605173733.GB779@hmg1> Hi, On Thu, Jun 05, 2003 at 11:53:02PM -0400, Reid Vail wrote: > found USB scanner (vendor=0x03f0, product=0x0601) at libusb:001:002 So it's detected by libusb. It's not found by the kernel USB scanner driver. But that's ok. Just make sure that the permissions are ok (see man sane-usb). > reid@linux:/etc/sane.d> more hp.conf [...] > # HP ScanJet 63X0C > usb 0x03f0 0x0601 These "usb" lines should be enough to detect your scanner. > # Uncomment the following if your scanner is connected by USB, > # but you are not using libusb "but you are not using libusb". But you do! > /dev/usb/scanner > option connect-device So I don't think this entry is necessary. Do "SANE_DEBUG_HP=255 scanimage -L" to find out what's going on. Bye, Henning From anoah@pfeiffer.edu Thu Jun 5 19:02:08 2003 From: anoah@pfeiffer.edu (m. allan noah) Date: Thu, 5 Jun 2003 14:02:08 -0400 (EDT) Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <3EE0101E.6010604@adelphia.net> Message-ID: if you access the scanner via the /dev/* files under linux, you will need the scanner module inserted in your kernel. try 'insmod scanner' as root, then try sane-find-scanner again. currently, your system is accessing the scanner via libusb, if you wish to keep that instead, comment out the lines in the hp.conf that specify the /dev/ device (whether or not the hp driver works with libusb, i cant say, as i use mine via scsi.) allan On Thu, 5 Jun 2003, Reid Vail wrote: > About six months ago Peter gave me some advice about my HP6350c > scanner. It fixed my issue and got it working. (I included that > exchange at the bottom of this message). Recently I upgraded my Suse > box to Suse 8.2 and it's not working again. I dug out the mail and > checked the config. Looks OK to me, and I included a few scraps. I've > included the output from sane-find-scanner. The permissions also look > OK, too, I think. Any suggestions would be great. > > thx > > Reid > > reid@linux:~>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=0x03f0, product=0x0601) at libusb:001:002 > # A USB device was detected. This program can't be sure if it's really > # a scanner. If it is your scanner, 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. > > > > reid@linux:/etc/sane.d> ls -l hp.conf > -rwxrwxrwx 1 root root 480 2003-06-05 21:14 hp.conf > > reid@linux:~> ls -l /etc/sane.d/dll.conf > -rw-rw-rw- 1 root root 448 2002-12-18 00:16 > /etc/sane.d/dll.conf > > > dll.conf > . > . > # dc210 > # dc240 > # dc25 > # dll > # dmc > # epson > hp > # fujitsu > # leo > # microtek > # microtek2 > # mustek_usb > # mustek > # matsushita > . > . > > > > reid@linux:/etc/sane.d> more hp.conf > #scsi HP > # Uncomment the following if you have "Error during device I/O" on SCSI > # option dumb-read > # > # The usual place for a SCSI-scanner on Linux > # > # USB-scanners supported by the hp-backend > # HP ScanJet 4100C > usb 0x03f0 0x0101 > # HP ScanJet 5200C > usb 0x03f0 0x0401 > # HP ScanJet 62X0C > usb 0x03f0 0x0201 > # HP ScanJet 63X0C > usb 0x03f0 0x0601 > # > # Uncomment the following if your scanner is connected by USB, > # but you are not using libusb > /dev/usb/scanner > option connect-device > reid@linux:/etc/sane.d> > > > Peter Kirchgessner wrote: > > > Hi, > > > > pleae have a look at /etc/sane.d/hp.conf or > > /usr/local/etc/sane.d/hp.conf. It must have two lines in it: > > > > /dev/usbscanner > > option connect-device > > > > In dll.conf (same directories) the line with "hp" must be active. > > You may need to set the permissions: > > > > chmod 666 /dev/usbscanner > > > > More hints can be found at http://www.kirchgessner.net/sanehpfaq.html > > > > Sincerely > > > > Peter > > > > Reid Vail schrieb: > > > >> I've been trying for a least a month to get an HP6350c USB Scanjet to > >> work. I'm running a SuSE 8.1 Personal distro, which comes with a SANE > >> implementation of 1.0.8-47. > >> > >> I think (but can't say for sure) that some part of the install of the > >> unit (via YAST) isn't working because it doesn't even "test" > >> correctly. However YAST does correctly identify it. > >> > >> When I run xscanimage I get this output: > >> > >> [xscanimage] No scanners were identified. If you were expecting > >> something different, check that the scanner is plugged in, turned on and > >> detected by sane-find-scanner (if appropriate). Please read the > >> documentation which came with this software (README, FAQ, manpages). > >> > >> But when I run sane-find-scanner I get this output: > >> > >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = > >> 0x0601) at device /dev/usb/scanner0 > >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = > >> 0x0601) at device /dev/usbscanner > >> > >> I make no claims that I'm not missing something obvious! I just > >> don't get it. For what it's worth, I know the unit works because it > >> runs under Windoze 2K. > >> > >> Thanks in advance. > >> > >> Reid Vail > >> > >> _______________________________________________ > >> Sane-devel mailing list > >> Sane-devel@www.mostang.com > >> http://www.mostang.com/mailman/listinfo/sane-devel > >> > > > > > > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From christoph.bier@web.de Thu Jun 5 19:31:52 2003 From: christoph.bier@web.de (Christoph Bier) Date: Thu, 05 Jun 2003 20:31:52 +0200 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 In-Reply-To: <20030605102544.GB11876@hmg1> References: <20030605102544.GB11876@hmg1> Message-ID: <3EDF8C98.80006@web.de> Henning Meier-Geinitz schrieb: > Hi, > > Some people reported kernel USB timeouts with their gt68xx based > scanners, e.g. Plustek 1247 or Mustek BearPaw series. This seems to be > caused by the check if the firmware is already loaded in the gt68xx > backend. I've disabled this check for now. > > If you encounter this problem, get the latest backend (at least > 1.0-47) or an unofficial snapshot from > http://www.meier-geinitz.de/sane/gt68xx-backend/ . Hi, now my scanner at home works again :-)! But only with the scanner module. Thank you very much for the workaround!! Many greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier@wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From anoah@pfeiffer.edu Thu Jun 5 19:59:04 2003 From: anoah@pfeiffer.edu (m. allan noah) Date: Thu, 5 Jun 2003 14:59:04 -0400 (EDT) Subject: [sane-devel] any drivers do software calibration? Message-ID: with the adf fujitsu scanners, in grayscale or color, we get fine, lightly colored lines as a part of the scanned image, and the 'background' behind the document when the scan window exceeeds the size of the paper looks mottled gray, as reported on this list. i can find no way in the interface manual to prevent this in hardware, though it has been reported that the same scanners under twain do not display these problems. hence, i assume that this can be corrected in software. are any of the existing sane backends doing this internally? i would like to do something similar as an option in the fujitsu backend... thanks, allan noah -- "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 From henning@meier-geinitz.de Thu Jun 5 21:35:43 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 22:35:43 +0200 Subject: [sane-devel] any drivers do software calibration? In-Reply-To: References: Message-ID: <20030605203543.GA2573@hmg1> Hi, On Thu, Jun 05, 2003 at 02:59:04PM -0400, m. allan noah wrote: > with the adf fujitsu scanners, in grayscale or color, we get fine, lightly > colored lines as a part of the scanned image, Vertical lines? > and the 'background' behind the document when the scan window > exceeeds the size of the paper looks mottled gray, as reported on > this list. That may be the result of the selected gamma, brightness and contrast. > i can find no way in the interface manual to prevent this in hardware, > though it has been reported that the same scanners under twain do not > display these problems. > > hence, i assume that this can be corrected in software. are any of the > existing sane backends doing this internally? i would like to do something > similar as an option in the fujitsu backend... The gt68xx backend does calibration completely in software. I think mustek_usb does this also, other backends of the more low-level scanner may use the same scheme. All scanners supported by the gt68xx backend have a white calibration strip at the top of the scanning area. It's visible if you open these scanners. Calibration works about like this: a) Coarse calibration: The scan bar moves to the calibration strip. The gain and offset values of the analog frontend are setup so the brightest white of the calibration strip is defined as white (255) and the darkest black is 0. You get black by either turning offf the lamp or by scanning a small black mark on the strip. b) Fine calibration: The scan bar scans some milimeters of the white strip in full width. Once with the lamp turned on and once with the lamp turned off. So you get two values per pixel per color, one for max white and one for min black. If you do a real scan you can calculate the resulting pixel color like this (from my memory, untested): real_color = 255 * (scanned_color - min_black) / (max_white - min_black) Bye, Henning From henning@meier-geinitz.de Thu Jun 5 21:39:48 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 22:39:48 +0200 Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <200306060229.41812.rsv869@adelphia.net> References: <3E02AB22.2010409@adelphia.net> <3EE0101E.6010604@adelphia.net> <20030605173733.GB779@hmg1> <200306060229.41812.rsv869@adelphia.net> Message-ID: <20030605203948.GB2573@hmg1> Hi, On Fri, Jun 06, 2003 at 02:29:41AM -0400, Reid Vail wrote: > Hello Henning - I'mm cc'ing to the list as I'm not really an hp expert. > I issues the command you suggested, and everything looks Ok until it tries to > open the libusb. I'm not sure I looked in the right place for the libusb > libraries, but I captured the permissions of what I found. I changed the > libusb.a file with a chmod 666, but didn't see any improvement. Changing the permissions of the library doesn't work. YOu must change the permissions of the device files as explained in man sane-usb (section libusb). The manpage is also on the SANE website: http://panda.mostang.com/sane/man/sane-usb.5.html > [hp] hp_read_config: attach usb 0x03f0 0x0601 > [hp] hp_attach_matching_devices: usb attach matching "usb 0x03f0 0x0601" > [hp] hp_attach: "libusb:001:002" > [hp] sanei_hp_device_info_get: searching libusb:001:002 > [hp] sanei_hp_device_info_get: check libusb:001:002 > [hp] hp_get_dev: New device libusb:001:002, connect-usb, scsi-request=0 > [hp] sanei_hp_device_new: libusb:001:002 > [hp] sanei_hp_device_info_get: searching libusb:001:002 > [hp] sanei_hp_device_info_get: check libusb:001:002 > [hp] hp_nonscsi_open: open usb with "libusb:001:002" > [hp] hp_nonscsi_open: open device libusb:001:002 failed > [hp] nonscsi_new: open failed (Access to resource has been denied) Did you try as root? That's most probably a permission issue. Bye, Henning From anoah@pfeiffer.edu Thu Jun 5 22:27:50 2003 From: anoah@pfeiffer.edu (m. allan noah) Date: Thu, 5 Jun 2003 17:27:50 -0400 (EDT) Subject: [sane-devel] any drivers do software calibration? In-Reply-To: <20030605203543.GA2573@hmg1> Message-ID: On Thu, 5 Jun 2003, Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 05, 2003 at 02:59:04PM -0400, m. allan noah wrote: > > with the adf fujitsu scanners, in grayscale or color, we get fine, lightly > > colored lines as a part of the scanned image, > > Vertical lines? yes, as if some small portion of the diode array always reads, even when there is just white paper. leads to occasional pink or cyan lines, etc. > > > and the 'background' behind the document when the scan window > > exceeeds the size of the paper looks mottled gray, as reported on > > this list. > > That may be the result of the selected gamma, brightness and contrast. > seems to be no way to mess with gamma/brightness/contrast in the hardware, there is only an 8bit or 10bit single-color LUT. > > i can find no way in the interface manual to prevent this in hardware, > > though it has been reported that the same scanners under twain do not > > display these problems. > > > > hence, i assume that this can be corrected in software. are any of the > > existing sane backends doing this internally? i would like to do something > > similar as an option in the fujitsu backend... > > The gt68xx backend does calibration completely in software. I think > mustek_usb does this also, other backends of the more low-level > scanner may use the same scheme. All scanners supported by the gt68xx > backend have a white calibration strip at the top of the scanning > area. It's visible if you open these scanners. > this scanner is adf only, but the backer behind each read array is very bright white plastic. i could use that, if i could figure out how to get the scanner to send me data when there is no document in the scanner i may have to hook it up to a windows box (ack!) and usb snoop on it. thanks for the data below, i will look at these drivers and see if i can see this being done... allan > Calibration works about like this: > > a) Coarse calibration: The scan bar moves to the calibration strip. > The gain and offset values of the analog frontend are setup so the > brightest white of the calibration strip is defined as white (255) > and the darkest black is 0. You get black by either turning offf > the lamp or by scanning a small black mark on the strip. > b) Fine calibration: The scan bar scans some milimeters of the white > strip in full width. Once with the lamp turned on and once with the > lamp turned off. So you get two values per pixel per color, one for > max white and one for min black. > > If you do a real scan you can calculate the resulting pixel color like > this (from my memory, untested): > > real_color = 255 * (scanned_color - min_black) / (max_white - min_black) > > Bye, > Henning > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From peter@pscomp.com Thu Jun 5 22:39:06 2003 From: peter@pscomp.com (Peter Santoro) Date: Thu, 05 Jun 2003 17:39:06 -0400 Subject: [sane-devel] Re: epson: scanimage threshold option not working in 1.0.12 backend (Peter Santoro) Message-ID: <3EDFB87A.1010207@pscomp.com> Ok, I believe I've figured this one out. The function handle_depth_halftone (epson.c) indicates that for threshold to be enabled, the mode must be Binary and halftoning must be None. After adding in some fprintf (to stderr) statements, I discovered that the order of the command line arguements also matters with these options. I seem to remember reading this somewhere, but I must have forgotten. Epson's Image Scan! for Linux 1.4.0 still doesn't work. I'll try their new 1.5.1 release. I apologize if I caused anyone to waste time on this. Peter From karsten.festag@gmx.de Thu Jun 5 23:18:29 2003 From: karsten.festag@gmx.de (Karsten Festag) Date: Fri, 6 Jun 2003 00:18:29 +0200 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org In-Reply-To: <20030603224901.GA931@wanadoo.fr> References: <3EDB6ACF.3010304@charter.net> <20030603224901.GA931@wanadoo.fr> Message-ID: <200306060018.29761.karsten.festag@gmx.de> [....] > Hello, > > I've parsed it a bit, and I must say that you're painting the picture > darker than it really is for parallel port scanners. Parallel port scanners > listed in SANE do work. No need to frighten people. > > I'm a bit skeptic about favouring ECP mode. It may be wise for printers, > but I think it is useless for scanners, unless you use some patch that > bring DMA reads. From a quick grep in SANE docs, EPP or ECP/EPP seems to be > the recommended setting. Just a remark: The Microtek2 parport scanners (they use the onscsi parport chip) do not work in ECP or ECP/EPP mode (data corruption occurs). EPP is here the only option to get good results. Regards, Karsten From webmaster@airrequest.net Fri Jun 6 04:11:02 2003 From: webmaster@airrequest.net (Philip M Dunton) Date: Thu, 5 Jun 2003 20:11:02 -0700 Subject: [sane-devel] Redhat 9 and XSane .89 Message-ID: <200306052011.02553.webmaster@airrequest.net> I have an Epson 1650 scanner which worked perfectly with my Redhat 8 installation. Never a second of grief. Now, after switching to RH 9 and the version of Sane which comes with it I find a very ill-mannered Sane implementation. First, XSane goes out and looks for a scanner automatically on log-in. My scanner is on a USB switch so it can be shared with two other computers so most of the time it is not available on start-up. The "Looking" dialog just hangs around forever. Second, I cannot use XSane or anything (GIMP) that uses it. The application just locks up after running the scanning mechanism. I have to KILL the process. I am using the current iscan rpm from EpsonKowa. Is there something I should know here? Phil Dunton From gerhard@gjaeger.de Fri Jun 6 07:13:16 2003 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Fri, 6 Jun 2003 08:13:16 +0200 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org In-Reply-To: <200306060018.29761.karsten.festag@gmx.de> References: <3EDB6ACF.3010304@charter.net> <20030603224901.GA931@wanadoo.fr> <200306060018.29761.karsten.festag@gmx.de> Message-ID: <200306060813.16298.gerhard@gjaeger.de> Hi, On Freitag, 6. Juni 2003 00:18, Karsten Festag wrote: [SNIPSNAP] > Just a remark: > > The Microtek2 parport scanners (they use the onscsi parport chip) do no= t > work in ECP or ECP/EPP mode (data corruption occurs). EPP is here the o= nly > option to get good results. > The same applies to the Plustek devices, ECP/EPP even causes the autodete= ction to fail, so SPP and EPP but never ECP/EPP or plain ECP Gerhard From henning@meier-geinitz.de Fri Jun 6 08:51:20 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 09:51:20 +0200 Subject: [sane-devel] Redhat 9 and XSane .89 In-Reply-To: <200306052011.02553.webmaster@airrequest.net> References: <200306052011.02553.webmaster@airrequest.net> Message-ID: <20030606075120.GA2800@hmg1> Hi, On Thu, Jun 05, 2003 at 08:11:02PM -0700, Philip M Dunton wrote: > I have an Epson 1650 scanner which worked perfectly with my Redhat 8 > installation. Never a second of grief. > Now, after switching to RH 9 and the version of Sane which comes with it I Which version of SANE is that (scanimage --version)? > find a very ill-mannered Sane implementation. > First, XSane goes out and looks for a scanner automatically on log-in. You mean xsane is started when you log into X? Oh well... But that is really a setup you should ask Redhat about. We (the SANE developers) don't do that :-) > My scanner is on a USB switch so it can be shared with two other > computers so most of the time it is not available on start-up. The > "Looking" dialog just hangs around forever. All the frontends ask the backends for available scanners on start-up. But this shouldn't take more than a few seconds. > Second, I cannot use XSane or anything (GIMP) that uses it. The application > just locks up after running the scanning mechanism. I have to KILL the > process. Does that also happen with other frontends like xscanimage or scanimage? E.g. try (in an xterm): SANE_DEBUG_DLL=255 scanimage -L If it hangs, what are the last few lines of output? They should contain the name of the backend that freezes. You can comment out this backend in /etc/sane.d/dll.conf. > I am using the current iscan rpm from EpsonKowa. Oh, that's not part of the SANE package. If it's a problem with that package, better ask Epson-Kowa for help. > Is there something I should know here? You could try the normal epson backend that comes with SANE. Bye, Henning From twaugh@redhat.com Fri Jun 6 09:50:19 2003 From: twaugh@redhat.com (Tim Waugh) Date: Fri, 6 Jun 2003 09:50:19 +0100 Subject: [sane-devel] Redhat 9 and XSane .89 In-Reply-To: <20030606075120.GA2800@hmg1> References: <200306052011.02553.webmaster@airrequest.net> <20030606075120.GA2800@hmg1> Message-ID: <20030606085019.GN18481@redhat.com> --fNagykWcDoSVAmSd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jun 06, 2003 at 09:51:20AM +0200, Henning Meier-Geinitz wrote: > You mean xsane is started when you log into X? Oh well... That might be the case if he has put it in his GNOME session; it's not something Red Hat Linux does by default (of course). Tim. */ --fNagykWcDoSVAmSd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+4FXKtO8Ac4jnUq4RAh8eAKCQRB4p5Ham0NyynnaSk4W93EtIEgCdHCmc L4MEe6ALlSdZRXcrgG7wgVE= =V3CX -----END PGP SIGNATURE----- --fNagykWcDoSVAmSd-- From mfleming@michaelfleming.webcentral.com.au Fri Jun 6 12:16:05 2003 From: mfleming@michaelfleming.webcentral.com.au (Michael Fleming) Date: Fri, 6 Jun 2003 21:16:05 +1000 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 In-Reply-To: <3EDF8C98.80006@web.de> References: <20030605102544.GB11876@hmg1> <3EDF8C98.80006@web.de> Message-ID: <20030606111605.GA1885@michaelfleming.webcentral.com.au> On Thu, Jun 05, 2003 at 08:31:52PM +0200, Christoph Bier waffled thusly: > Henning Meier-Geinitz schrieb: > > Hi, > > > > Some people reported kernel USB timeouts with their gt68xx based > > scanners, e.g. Plustek 1247 or Mustek BearPaw series. This seems to be > > caused by the check if the firmware is already loaded in the gt68xx > > backend. I've disabled this check for now. > > > > If you encounter this problem, get the latest backend (at least > > 1.0-47) or an unofficial snapshot from > > http://www.meier-geinitz.de/sane/gt68xx-backend/ . > > Hi, > > now my scanner at home works again :-)! But > only with the scanner module. Thank you very > much for the workaround!! I can confirm it now works with my Genius ColorPage Vivid 3XE (USB) using libusb 0.1.6 and sane-backends 1.0.12 (on Redhat 9, hand-rolled RPM, current RH errata kernel) (This is the first time I've actually got this scanner working under Linux - the Windows scanning app supplied is horrible, sane/xsane are streets ahead. Thanks again!) > Many greetings, > > Christoph Cheers, Michael Fleming. -- Michael Fleming "Bother" said the Borg, "We've assimilated Pooh!" From henning@meier-geinitz.de Fri Jun 6 12:46:56 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 13:46:56 +0200 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 In-Reply-To: <20030606111605.GA1885@michaelfleming.webcentral.com.au> References: <20030605102544.GB11876@hmg1> <3EDF8C98.80006@web.de> <20030606111605.GA1885@michaelfleming.webcentral.com.au> Message-ID: <20030606114656.GB5060@hmg1> Hi, On Fri, Jun 06, 2003 at 09:16:05PM +1000, Michael Fleming wrote: > I can confirm it now works with my Genius ColorPage Vivid 3XE (USB) > using libusb 0.1.6 and sane-backends 1.0.12 (on Redhat 9, hand-rolled > RPM, current RH errata kernel) Thanks for the report. Any problems in color mode? There is a comment "Mostly works. Color problems?" on my list for this scanner, but I don't know if it's still valid. Bye, Henning From henning@meier-geinitz.de Fri Jun 6 13:00:30 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 14:00:30 +0200 Subject: [sane-devel] MacOS X and sm3600 backend: still crashes? Message-ID: <20030606120030.GC5060@hmg1> Hi, some time ago, there have been reports that it's necessary to comment out sm3600 in dll.conf on MacOS X because otherwise SANE crashes in that backend. Is this still the case? Bye, Henning From jochen.eisinger@gmx.de Fri Jun 6 15:01:36 2003 From: jochen.eisinger@gmx.de (Jochen Eisinger) Date: Fri, 06 Jun 2003 16:01:36 +0200 Subject: [sane-devel] New sanei_pa4s2 in cvs Message-ID: <3EE09EC0.4030109@gmx.de> This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5F795099F5F25C456C69E563 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I commited the new (and fixed) sanei_pa4s2 to cvs earlier today. In order to use the mustek_pp backend, you either have to install libieee1284 (and have configure detect it) [recommended] or enable direct port io (also with configure). What about including libieee1284 into the SANE distribution? I'd volunteer on keeping it up to date. best regards -- jochen --------------enig5F795099F5F25C456C69E563 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+4J7G8OF76YrreuMRAqaLAKCy9nqr1UQzhP+k89WXZiia59fSRACdENzZ cQ06fauc1LM7IZ3qWqswxn0= =r9hg -----END PGP SIGNATURE----- --------------enig5F795099F5F25C456C69E563-- From dahjelle@mac.com Fri Jun 6 17:24:59 2003 From: dahjelle@mac.com (David Alan Hjelle) Date: Fri, 6 Jun 2003 09:24:59 -0700 (PDT) Subject: [sane-devel] Microtek SlimScan C6 on Mac OS X 10.1.5 (sane-microtek2) Message-ID: <20030606162459.65000.qmail@web13405.mail.yahoo.com> Hello. I've been trying to get my Microtek SlimScan C6 working on my Macintosh running Mac OS X 10.1.5. After a couple days spent trying to get it to compile correctly (you can see the details on the mailing list), everything compiled (including libusb) and I was excited to try my scanner. It shows up under sane-find-scanner as: found USB scanner (vendor=0x05da, product=0x009a) at libusb:-07:005 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. scanimage -L reports: No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). So, I did some research. Apparently, the microtek2 backend only supports USB kernel extensions and not libusb? What would it take to modify the code so that it would work? Thanks for all your great work! It's greatly appreciated even if I don't get this scanner working! In Christ Alone, David Alan Hjelle 1 Corinthians 2:2 http://welcome.to/theJESUSpage __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com From jb@jblache.org Fri Jun 6 17:26:23 2003 From: jb@jblache.org (Julien BLACHE) Date: Fri, 06 Jun 2003 18:26:23 +0200 Subject: [sane-devel] New sanei_pa4s2 in cvs In-Reply-To: <3EE09EC0.4030109@gmx.de> (Jochen Eisinger's message of "Fri, 06 Jun 2003 16:01:36 +0200") References: <3EE09EC0.4030109@gmx.de> Message-ID: <87d6hrmats.fsf@frigate.technologeek.org> Jochen Eisinger wrote: > What about including libieee1284 into the SANE distribution? I'd > volunteer on keeping it up to date. As long as one has the option of using the system's libieee1284, I won't object. Otherwise you'll hear me scream ;-) Anyway, libieee1284 is quite small and easy to build, so I'm not sure it's worth the time you'll spend on having it integrated into the sane-backends source distribution... JB. -- Julien BLACHE From henning@meier-geinitz.de Fri Jun 6 17:53:27 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 18:53:27 +0200 Subject: [sane-devel] Microtek SlimScan C6 on Mac OS X 10.1.5 (sane-microtek2) In-Reply-To: <20030606162459.65000.qmail@web13405.mail.yahoo.com> References: <20030606162459.65000.qmail@web13405.mail.yahoo.com> Message-ID: <20030606165327.GD5060@hmg1> Hi, On Fri, Jun 06, 2003 at 09:24:59AM -0700, David Alan Hjelle wrote: > I've been trying to get my Microtek SlimScan C6 working on my Macintosh > running Mac OS X 10.1.5. [...] > So, I did some research. Apparently, the microtek2 backend only > supports USB kernel extensions and not libusb? What would it take to > modify the code so that it would work? All these scanners are SCSI. The SCSI protocoll is only transported over the USB in case of USB devices. So they use a kernel SCSI-over-USB driver (called "microtek"). So you either need to port this Linux driver to MacOS X or do the SCSI-over-USB logic in the backend itsself. Maybe the maintainer can tell you more about how complicated this may be. Userland SCSI-over-USB is used at least in the ma1509 and the avison backends. Bye, Henning From henning@meier-geinitz.de Fri Jun 6 18:07:49 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 19:07:49 +0200 Subject: [sane-devel] Please test: changed handling of list of backends Message-ID: <20030606170749.GE5060@hmg1> Hi, I've moved the list of backends that will be build from backend/Makefile.in to configure. So we can print more clearly which backends will be compiled and the tests are all in one place. The changes are in CVS now. Please test if I broke something. Configure pronts a warning if a backend is not built (disabling ...) and lists all the backends that are being built. If the variable "$BACKENDS" is set, only the listed backend are built. I don't want to advertise this feature to avoid trouble with missing backends. But it may be handy if you have a slow machine or want to rebuild one backend often. Examples: $ ./configure [...] *** disabling GPHOTO2 backend (not requested, or failed to find gphoto2-config or JPEG library) *** disabling PINT backend (sys/scanio.h not found) *** disabling pnm backend (not selected manually) [...] -> The following backends will be built: abaton agfafocus apple artec as6e avision bh canon canon630u coolscan coolscan2 dc25 dmc epson fujitsu gt68xx hp leo matsushita microtek microtek2 mustek mustek_pp mustek_usb nec pie plustek ricoh s9036 sceptre sharp sp15c st400 tamarack test teco1 teco2 teco3 umax umax_pp umax1220u artec_eplus48u ma1509 ibm hp5400 dc210 dc240 canon_pp hpsj5s qcam v4l net snapscan sm3600 $ BACKENDS="gt68xx net" ./configure [...] -> The following backends will be built: gt68xx net Bye, Henning From jochen.eisinger@gmx.de Fri Jun 6 18:32:37 2003 From: jochen.eisinger@gmx.de (Jochen Eisinger) Date: Fri, 06 Jun 2003 19:32:37 +0200 Subject: [sane-devel] New sanei_pa4s2 in cvs In-Reply-To: <87d6hrmats.fsf@frigate.technologeek.org> References: <3EE09EC0.4030109@gmx.de> <87d6hrmats.fsf@frigate.technologeek.org> Message-ID: <3EE0D035.10505@gmx.de> This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC23D0D5E5B47D942DBAEFBFB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Julien BLACHE wrote: > As long as one has the option of using the system's libieee1284, I > won't object. Otherwise you'll hear me scream ;-) Well ofcourse it just would be a fallback option. Not all systems come with libieee1284 and I'd like to keep the overhead to install SANE for mustek_pp as low as possible. regards -- jochen --------------enigC23D0D5E5B47D942DBAEFBFB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE+4NA68OF76YrreuMRAmHaAJ9Uhvz7WYE8eOa1SwcwWG5ZY4X16ACglgGA ySz1x32JwRorH6R20zSHEYQ= =LU8O -----END PGP SIGNATURE----- --------------enigC23D0D5E5B47D942DBAEFBFB-- From henning@meier-geinitz.de Fri Jun 6 19:18:54 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 20:18:54 +0200 Subject: [sane-devel] Proposal: Change of the backend and model status strings Message-ID: <20030606181853.GF5060@hmg1> Hi, There has been some criticism of the current handling of the :status keywords in the .desc files. These filse are used to create our lists of scanners and the output of the scanner search engine. We currently have two sorts of status indicators: 1) The backend status: alpha, beta or stable 2) The model status: unsupported, untested, alpha, beta or stable Concerning the backends status I think we don't really have the need to talk about stability. Crashing backends are rather seldom. So I'm not sure if we need this overall status at all anymore. If we want to keep it, what about a measurement on how active the backend is maintained, e.g.: unmaintained: There is no maintainer. Only security and other grave bugs will be fixed supported: There is a maintainer for the backend. Bugs will be fixed and patches will be accepted. development: The backend is under active development. New features and/or new models may be added. Model status: As proposed by others, I'd like to have a measurement on how good a scanner works compared to its capabilities. E.g.: unsupported: This device is not working at all. untested: The device may work, but nobody has tested it yet. minimal: The device is detected and does something but is not really usable. E.g. It scans in one mode but colors are off. basic: The device is usable, but some modes are not supported or quality is not perfect yet. good: Usable for day-to-day work. Some unusual modes or seldomly-used features aren't supported. perfect: Everything the scanner can do is supported. Here is an example on how the HTML lists could look like: http://www.meier-geinitz.de/sane/tmp/sane-mfgs.html#MUSTEK Only the model status is implemented. And only Mustek SCSi scanners have set the values. Comments? Bye, Henning From mfleming@michaelfleming.webcentral.com.au Sat Jun 7 01:21:30 2003 From: mfleming@michaelfleming.webcentral.com.au (Michael Fleming) Date: Sat, 7 Jun 2003 10:21:30 +1000 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 In-Reply-To: <20030606114656.GB5060@hmg1> References: <20030605102544.GB11876@hmg1> <3EDF8C98.80006@web.de> <20030606111605.GA1885@michaelfleming.webcentral.com.au> <20030606114656.GB5060@hmg1> Message-ID: <20030607002130.GA3855@michaelfleming.webcentral.com.au> On Fri, Jun 06, 2003 at 01:46:56PM +0200, Henning Meier-Geinitz waffled thusly: > Hi, > > On Fri, Jun 06, 2003 at 09:16:05PM +1000, Michael Fleming wrote: > > I can confirm it now works with my Genius ColorPage Vivid 3XE (USB) > > using libusb 0.1.6 and sane-backends 1.0.12 (on Redhat 9, hand-rolled > > RPM, current RH errata kernel) > > Thanks for the report. Any problems in color mode? There is a comment > "Mostly works. Color problems?" on my list for this scanner, but I > don't know if it's still valid. Thanks Henning, I've only run a few samples so far but I've not noted any issues with the scan result's colours. I'll run a few more over the course of the weekend and followup if I note anything interesting or unusual. My test scan is at http://www.michaelfleming.webcentral.com.au/carla2.tif (~130K) if you want a look. ( It's a cover shot my girlfriend's sister did for a local magazine) If I can, I'll have one of my artist friends give me a better idea re: colour precision - I'm a *little* red/green colourblind which might skew my judgement a little. > Bye, > Henning Cheers, Michael. -- Michael Fleming "Bother" said the Borg, "We've assimilated Pooh!" From david@rondotheatre.co.uk Sat Jun 7 01:46:55 2003 From: david@rondotheatre.co.uk (david stevenson) Date: Sat, 7 Jun 2003 01:46:55 +0100 Subject: [sane-devel] Proposal: Change of the backend and model status strings In-Reply-To: <20030606181853.GF5060@hmg1> References: <20030606181853.GF5060@hmg1> Message-ID: <200306070146.55658.david@rondotheatre.co.uk> Here are 2 personal opinions On Friday 06 June 2003 7:18 pm, Henning Meier-Geinitz wrote:> > There has been some criticism of the current handling of the :status > keywords in the .desc files. These filse are used to create our lists > of scanners and the output of the scanner search engine. > > We currently have two sorts of status indicators: > > 1) The backend status: alpha, beta or stable > 2) The model status: unsupported, untested, alpha, beta or stable > > > Concerning the backends status I think we don't really have the need > to talk about stability. Crashing backends are rather seldom. So I'm > not sure if we need this overall status at all anymore. If we want to > keep it, what about a measurement on how active the backend is > maintained, e.g.: > > unmaintained: There is no maintainer. Only security and other > grave bugs will be fixed > supported: There is a maintainer for the backend. Bugs will be fixed and > patches will be accepted. > development: The backend is under active development. New features > and/or new models may be added. Many backends support several scanners, and may be "supported" for most and under "development" for some. Is unmaintained and supported enough without the 3rd option? > Model status: As proposed by others, I'd like to have a measurement on > how good a scanner works compared to its capabilities. E.g.: > > unsupported: This device is not working at all. > untested: The device may work, but nobody has tested it yet. > minimal: The device is detected and does something but is not > really usable. E.g. It scans in one mode but colors > are off. > basic: The device is usable, but some modes are not supported > or quality is not perfect yet. > good: Usable for day-to-day work. Some unusual modes or > seldomly-used features aren't supported. > perfect: Everything the scanner can do is supported. > I do not like the word "perfect" it implies totally bug free and not improvable, would "complete" be more suitable. > > Here is an example on how the HTML lists could look like: > > http://www.meier-geinitz.de/sane/tmp/sane-mfgs.html#MUSTEK > > Only the model status is implemented. And only Mustek SCSi scanners > have set the values. > > Comments? > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From henning@meier-geinitz.de Sat Jun 7 09:57:38 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 7 Jun 2003 10:57:38 +0200 Subject: [sane-devel] Proposal: Change of the backend and model status strings In-Reply-To: <200306070146.55658.david@rondotheatre.co.uk> References: <20030606181853.GF5060@hmg1> <200306070146.55658.david@rondotheatre.co.uk> Message-ID: <20030607085738.GC6584@meier-geinitz.de> Hi, On Sat, Jun 07, 2003 at 01:46:55AM +0100, david stevenson wrote: [backend status] > Many backends support several scanners, and may be "supported" for most and > under "development" for some. > Is unmaintained and supported enough without the 3rd option? I think so, yes. So a boolean flag ":maintained" would be enough. [model status] > I do not like the word "perfect" it implies totally bug free and not > improvable, would "complete" be more suitable. Ok. Bye, Henning From soumarmt@nerim.net Sat Jun 7 16:43:35 2003 From: soumarmt@nerim.net (Thomas Soumarmon) Date: Sat, 7 Jun 2003 17:43:35 +0200 Subject: [sane-devel] Please test: changed handling of list of backends In-Reply-To: <20030606170749.GE5060@hmg1> References: <20030606170749.GE5060@hmg1> Message-ID: <200306071743.35428.soumarmt@nerim.net> Hi, I tested it with BACKENDS="hp5400" and it works great. It is nice to be able to compile only one backend without changing Makefile.in. I still have a problem compiling linux/videodev.h that prevents me from compiling v4l. I send another mail to talk about it. From soumarmt@nerim.net Sat Jun 7 16:43:45 2003 From: soumarmt@nerim.net (Thomas Soumarmon) Date: Sat, 7 Jun 2003 17:43:45 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <20030606170749.GE5060@hmg1> References: <20030606170749.GE5060@hmg1> Message-ID: <200306071743.45097.soumarmt@nerim.net> Hi, I have a problem compiling v4l because of the linux/videodev.h. Has anybody already had this problem with this file ? Follows the errors : In file included from /usr/include/linux/videodev.h:14, from v4l.c:76: /usr/include/linux/videodev2.h:432: parse error before "v4l2_std_id" /usr/include/linux/videodev2.h:432: ISO C forbids data definition with no type or storage class /usr/include/linux/videodev2.h:500: parse error before "v4l2_std_id" /usr/include/linux/videodev2.h:505: parse error before '}' token /usr/include/linux/videodev2.h:518: parse error before "v4l2_std_id" /usr/include/linux/videodev2.h:521: parse error before '}' token /usr/include/linux/videodev2.h:555: parse error before "v4l2_std_id" /usr/include/linux/videodev2.h:557: parse error before '}' token v4l.c: In function `sane_v4l_exit': Thank you for any help, Thomas. From henning@meier-geinitz.de Sat Jun 7 17:40:04 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 7 Jun 2003 18:40:04 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <200306071743.45097.soumarmt@nerim.net> References: <20030606170749.GE5060@hmg1> <200306071743.45097.soumarmt@nerim.net> Message-ID: <20030607164004.GD6584@meier-geinitz.de> Hi, On Sat, Jun 07, 2003 at 05:43:45PM +0200, Thomas Soumarmon wrote: > I have a problem compiling v4l because of the linux/videodev.h. > Has anybody already had this problem with this file ? No, but I haven't installed Video for Linux version 2 (the header is from version 2). > Follows the errors : > > In file included from /usr/include/linux/videodev.h:14, > from v4l.c:76: > /usr/include/linux/videodev2.h:432: parse error before "v4l2_std_id" > /usr/include/linux/videodev2.h:432: ISO C forbids data definition with no type > or storage class Maybe that's the result over our pedantic warning settings. Try with "--disable-warnings". Looks like the header file is not ISO C-conforming (for whatever version of ISO-C). Where did you get videodev2.h from? Is it from your version of libc (which one)? Or is /usr/include/linux a link to /usr/src/linux/include/linux and you have installed a 2.5 kernel? We'll have to think about supporting v4l version 2 anyway. There is an old v4l2 backend, but nobody yet responded to the question if v4l2 is the same as the new version 2 kernel interface. Bye, Henning From henning@meier-geinitz.de Sat Jun 7 21:36:15 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 7 Jun 2003 22:36:15 +0200 Subject: [sane-devel] Proposal: Change of the backend and model status strings In-Reply-To: <20030606181853.GF5060@hmg1> References: <20030606181853.GF5060@hmg1> Message-ID: <20030607203615.GE6584@meier-geinitz.de> Hi, On Fri, Jun 06, 2003 at 08:18:54PM +0200, Henning Meier-Geinitz wrote: > There has been some criticism of the current handling of the :status > keywords in the .desc files. These filse are used to create our lists > of scanners and the output of the scanner search engine. Ok. I wrote some more code and this is the result: http://www.meier-geinitz.de/sane/tmp/sane-mfgs.html http://www.meier-geinitz.de/sane/tmp/sane-backends.html I've changed the mustek backend settings for demondtsrion, so you may want to have a look at those. Tha status of the backend isn't used anymore. If a backend is no longer maintained, we just set the version to "UNMAINTAINED". See the mustek backend for an example. The status of the devices is set by the :status keyword. The menauings are explained in the legend. The code of sane-desc.c translates the old alpha, beta and stable codes like this: alpha: basic beta: good stable: good I think that reflects the current usage best. When sane-desc.c is in CVS, the backends should be moved to the new system. But until this has been done, the list can be generated using the old status vaules (with warnings). The backend status is still used if there is no device status. Please check (also for spelling). The only problem I see is that the scanner search engine code must be rewritten. The ascii output of sane-desc doesn't print the backend status anymore. The device status uses the new values. If a devic estatus is not available, the backend status is used. Bye, Henning From pjh@coastal.net.au Sun Jun 8 02:53:15 2003 From: pjh@coastal.net.au (Peter Howard) Date: 08 Jun 2003 11:53:15 +1000 Subject: [sane-devel] Problem building on OSX Message-ID: <1055037195.1678.7.camel@pig> (I've searched the archive and have seen related problems but not enough info to work the rest out :-( I'm trying to build sane-backends 1.0.12 on OSX 10.2, and I get the following load errors: gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a ../backend/.libs/libsane.dylib -lm -framework CoreFoundation -framework IOKit ld: multiple definitions of symbol _getopt /usr/lib/libm.dylib(getopt.So) definition of _getopt ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text) ld: multiple definitions of symbol _opterr /usr/lib/libm.dylib(getopt.So) definition of _opterr ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data) ld: multiple definitions of symbol _optind /usr/lib/libm.dylib(getopt.So) definition of _optind ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data) ld: multiple definitions of symbol _optopt /usr/lib/libm.dylib(getopt.So) definition of _optopt ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data) make[1]: *** [scanimage] Error 1 make: *** [all-recursive] Error 1 I gave no options to configure. Thanks PJH From soumarmt@nerim.net Sun Jun 8 09:17:41 2003 From: soumarmt@nerim.net (Thomas Soumarmon) Date: Sun, 8 Jun 2003 10:17:41 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <20030607164004.GD6584@meier-geinitz.de> References: <20030606170749.GE5060@hmg1> <200306071743.45097.soumarmt@nerim.net> <20030607164004.GD6584@meier-geinitz.de> Message-ID: <200306081017.41275.soumarmt@nerim.net> Hi, > > Follows the errors : > > > > In file included from /usr/include/linux/videodev.h:14, > > from v4l.c:76: > > /usr/include/linux/videodev2.h:432: parse error before "v4l2_std_id" > > /usr/include/linux/videodev2.h:432: ISO C forbids data definition with no > > type or storage class > > Maybe that's the result over our pedantic warning settings. Try with > "--disable-warnings". Looks like the header file is not ISO > C-conforming (for whatever version of ISO-C). I'll try that later and tell you what it changes. > > Where did you get videodev2.h from? Is it from your version of libc > (which one)? Or is /usr/include/linux a link to > /usr/src/linux/include/linux and you have installed a 2.5 kernel? Looking with the rpmdrake tool (Mdk 9.1 installed) it says that videodev2.h belongs to : glibc-devel-2.3.1-10mdk or kernel-source-2.4.21-0.13mdk I am wondering if this is exact or if it belongs to another package I would have tried on the machine (they have been numerous). > > We'll have to think about supporting v4l version 2 anyway. There is an > old v4l2 backend, but nobody yet responded to the question if v4l2 is > the same as the new version 2 kernel interface. > Have a nice day, Thomas. From henning@meier-geinitz.de Sun Jun 8 10:07:15 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 8 Jun 2003 11:07:15 +0200 Subject: [sane-devel] Problem building on OSX In-Reply-To: <1055037195.1678.7.camel@pig> References: <1055037195.1678.7.camel@pig> Message-ID: <20030608090715.GA18225@meier-geinitz.de> Hi, On Sun, Jun 08, 2003 at 11:53:15AM +1000, Peter Howard wrote: > (I've searched the archive and have seen related problems but not enough > info to work the rest out :-( I thought that problem was fixed. I have some reports that 1.0.12 works, so this maybe is one more occurance of the "all MacOS X systems are different from each other" syndrome. > I'm trying to build sane-backends 1.0.12 on OSX 10.2, and I get the > following load errors: > > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a > ../backend/.libs/libsane.dylib -lm -framework CoreFoundation -framework > IOKit > ld: multiple definitions of symbol _getopt > /usr/lib/libm.dylib(getopt.So) definition of _getopt > ../lib/liblib.a(getopt.o) definition of _getopt in section > (__TEXT,__text) It is defined multiple and that's ok (in libsane and liblib). You could ask the other MacOS X guys and find out what's different on your setup. There have been some MacOS X changes in the current CVS code, but I don't think they are related to your problem. Bye, Henning From henning@meier-geinitz.de Sun Jun 8 10:16:38 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 8 Jun 2003 11:16:38 +0200 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030607183652.GA7370@watcher.WorkGroup> References: <20030604094900.GA7629@watcher.WorkGroup> <20030604181753.GB3795@hmg1> <20030607183652.GA7370@watcher.WorkGroup> Message-ID: <20030608091638.GB18225@meier-geinitz.de> Hi, I'm cc'ing to the sane-devel list again. I'm not a plustek expert so please direct yout answers to the list. Maybe someone with more plustek experience knows what's going on better :-) On Sat, Jun 07, 2003 at 06:36:52PM +0000, Michael Rasile wrote: > Thanks for the reply. I tried everything you suggested but alas, no > go. I have the scanner and usb stuff compiled into the kernel, so I > am not using modules. I am using Gentoo and I know the version of > xsane is not the latest 0.86. I don't know if this has anything to do > with anything. I know the scanner works because I was using Mandrake > 9.1 previously and the scanner setup was all done automatically. The > kernel finds the scanner at boot time and sane-find-scanner finds the > scanner. Please show us the output of "sane-find-scanner -q". > Why won't xsane see the scanner. I'm so frustrated because I > can't figure this thing out even with the docs. :-) I checked the > website for the driver, but do I need to recompile sane-frontend and > back-end or what? If you have recent versions of sane-backends, no you don't need to recompile anything (I guess). Which version of sane-backends do you use (scanimage --version)? > I know this is all very simple for you, but I have > run into a brick wall. I have placed everything(I think) in > /etc/sane.d/dll.conf and plustek.conf but alas, no go. Any further > suggestions as to what I might do or where I might go to help myself > figure this out. Well, I told you how to enable debugging. Did you do that? What happened? I didn't tell you to send us the debug output explicitely, but that was my intention :-) So Please show us the ouput of SANE_DEBUG_PLUSTEK=255 scanimage -L You can save it into a file like this: SANE_DEBUG_PLUSTEK=255 scanimage -L 2>file.txt If there is no output (but the "No scanner found"), the plustek backend is not loaded at all (nor in dll.conf?) In this case, please also try: SANE_DEBUG_DLL=255 scanimage -L 2>file2.txt > I do appreciate your help and also your patience for > reading the ramblings of a nearly insane.(no pun intended) No problem. That's one of the aims of this mailing list :-) > :-))I've > checked the Gentoo forums and see people having the same problem with > xsane, but I haven't found anything yet that helps me. I will keep > searching. You know, if Mandrake is able to configure my scanner, > shouldn't just about every distro be able to do the same thing? (no > response needed here. :-)) Well, the response should be given by your distributor :-) Bye, Henning From henning@meier-geinitz.de Sun Jun 8 10:35:29 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 8 Jun 2003 11:35:29 +0200 Subject: [sane-devel] Redhat 9 and XSane .89 In-Reply-To: <200306071548.43449.webmaster@airrequest.net> References: <200306052011.02553.webmaster@airrequest.net> <20030606075120.GA2800@hmg1> <200306071548.43449.webmaster@airrequest.net> Message-ID: <20030608093529.GC18225@meier-geinitz.de> Hi, On Sat, Jun 07, 2003 at 03:48:43PM -0700, Philip M Dunton wrote: > Since Redhat is such a popular distribution I figured someone else already had > seen this anomalous behavior. I had zero problems after installing RH 8. Which anomalous behaviour? I asked what you really mean but you didn't answer that part of the mail. As Tim Waugh says xsane is not started on login by default, I don't really know what's going on if you don't give details. I haven't heard of any RedHat-specific problems that look like yours. If I had, I'd have said so in may response. > I was hoping for a quick answer. Well, it took only some hours. > I know how to trouble-shoot. The first computer I ever got to play with was > made by an outfit named "Univac." I'm impressed (really!). > Believe me I won't take the time to work out bugs in some else's software. Ok. Nobody asked you to do. Just for the record, I don't know of any current bug in sane-backends that could cause your problem. As you didn't give any details on what backend you are using you may not be using any part of sane-backends at all (but the stuff from Epson Kowa). If you don't care to describe what software you are using, how should we help? > I am too adept at putting them in my own work. Ok. So just ask someone to fix your installation for money. Maybe someone from Redhat? He'll try to find out the necessary information without asking a single dump question to you. > An easy solution for me is to back up to RH 8. Fortunately the > operation of a scanner isn't a priority just now, merely a token of > the stability of the system as a whole. > Geez, you Linux types need to get a grip. Ah, why didn't you put that on top of your mail? Or better don't write an email to the devlopers of a software about a bug that may not even exist in that software? So you are just trolling and don't want any response at all? Why should anyone help you? By the way: SANE is not Linux. Oh well, that long experience with computers and you haven't learned basic social stuff and even how to write an email to a list (cc added). Bye, Henning From peter@pogma.com Sun Jun 8 13:07:19 2003 From: peter@pogma.com (Peter O'Gorman) Date: Sun, 8 Jun 2003 21:07:19 +0900 Subject: [sane-devel] Problem building on OSX In-Reply-To: <1055037195.1678.7.camel@pig> Message-ID: Hi Peter, I am guessing here, but are you using Apple's developer tools which shipped with 10.2 ? This works for me with the ld from the December 2002 developer tools, looks like a linker issue may have been fixed in that release. You can get a copy of the December 2002 tools from http://connect.apple.com after free registration. I'd be interested to know if this solves your problem, I thought that this was solved prior to release of 1.0.12, but it may have only been "solved" for those of us with the latest linker :( Thanks, Peter On Sunday, June 8, 2003, at 10:53 AM, Peter Howard wrote: > (I've searched the archive and have seen related problems but not > enough > info to work the rest out :-( > > I'm trying to build sane-backends 1.0.12 on OSX 10.2, and I get the > following load errors: > > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a > ../backend/.libs/libsane.dylib -lm -framework CoreFoundation -framework > IOKit > ld: multiple definitions of symbol _getopt > /usr/lib/libm.dylib(getopt.So) definition of _getopt > ../lib/liblib.a(getopt.o) definition of _getopt in section > (__TEXT,__text) > ld: multiple definitions of symbol _opterr > /usr/lib/libm.dylib(getopt.So) definition of _opterr > ../lib/liblib.a(getopt.o) definition of _opterr in section > (__DATA,__data) > ld: multiple definitions of symbol _optind > /usr/lib/libm.dylib(getopt.So) definition of _optind > ../lib/liblib.a(getopt.o) definition of _optind in section > (__DATA,__data) > ld: multiple definitions of symbol _optopt > /usr/lib/libm.dylib(getopt.So) definition of _optopt > ../lib/liblib.a(getopt.o) definition of _optopt in section > (__DATA,__data) > make[1]: *** [scanimage] Error 1 > make: *** [all-recursive] Error 1 > > > I gave no options to configure. > > Thanks > > PJH > > > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > From sane-devel@mostang.com Sun Jun 8 16:01:01 2003 From: sane-devel@mostang.com (Henning Meier-Geinitz) Date: Sun, 8 Jun 2003 17:01:01 +0200 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030608104442.GA6034@watcher.WorkGroup> References: <20030604094900.GA7629@watcher.WorkGroup> <20030604181753.GB3795@hmg1> <20030607183652.GA7370@watcher.WorkGroup> <20030608091638.GB18225@meier-geinitz.de> <20030608104442.GA6034@watcher.WorkGroup> Message-ID: <20030608150101.GE18225@meier-geinitz.de> Hi, On Sun, Jun 08, 2003 at 10:44:42AM +0000, Michael Rasile wrote: > found USB scanner (vendor=0x04a9 produce=0x220e at /dev/usb/scanner0 > at /dev/usbscanner0 Ok, so the kernel USB scanner driver found it. > > Which version of sane-backends do you use (scanimage --version)? > > > backend version 1.0.9 Oh. Are you sure that this version supports your scanner? I can't find "Lide" on the list of supported scanners for 1.0.9. 1.0.12 is the current version of sane-backends but 1.0.10 may also work. But I'm not an plustek expert... > Thanks very much for your response. I apologize if I sent > this to the wrong list. Well, sane-devel is ok. Just don't send your answers to only me, because on the sane-devel mailing list there are more people (e.g. the plustek maintainer) who know much more about your scanner and the plustek backend. That's why I cc to the list again. > This will be the last time I'll post > here.I'll monitor sane-devel mailing list and figure it out. Please > find attached the debug output. If I am sending this to the wrong > place again, please tell me and I will not do so again. Just send it to sane-devel@mostang.com. That's the mailing list address. Not (only) to henning@meier-geinitz.de :-) > Even though I haven't solved the scanner problem yet, I am learning > something from this. When it is solved, maybe I can help someone else > with similar problems. That's very good. We need more people like you! > [plustek] >[usb] 0x04a9 0x220e< Ok, that should be your scanner. > [plustek] next device is a USB device (0x04A9-0x220E) > [plustek] next device is an USB device > [plustek] ># - device devicename< > [plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)< > [plustek] ># [usb] 0x07B3 0x0017< > [plustek] >device /dev/usbscanner0< > [plustek] Decoding device name >/dev/usbscanner0< [...] > [plustek] attach (/dev/usbscanner0, 0xbfffd170, (nil)) > [plustek] Device configuration: > [plustek] device name : >/dev/usbscanner0< > [plustek] porttype : 1 > [plustek] USB-ID : >0x04A9-0x220E< [...] > [plustek] usbDev_open(/dev/usbscanner0,0x04A9-0x220E) > [plustek] Vendor ID=0x04A9, Product ID=0x220E > [plustek] Device >0x04A9-0x220E<, is not supported! Looks like your backend is really too old. Bye, Henning From keeper@neo.rr.com Sun Jun 8 13:27:50 2003 From: keeper@neo.rr.com (Michael Rasile) Date: Sun, 8 Jun 2003 12:27:50 +0000 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030608150101.GE18225@meier-geinitz.de> References: <20030604094900.GA7629@watcher.WorkGroup> <20030604181753.GB3795@hmg1> <20030607183652.GA7370@watcher.WorkGroup> <20030608091638.GB18225@meier-geinitz.de> <20030608104442.GA6034@watcher.WorkGroup> <20030608150101.GE18225@meier-geinitz.de> Message-ID: <20030608122750.GA29906@watcher.WorkGroup> On Sun Jun 08, 2003 at 05:01:01PM +0200 or thereabouts, Henning Meier-Geinitz wrote: > Hi, > > On Sun, Jun 08, 2003 at 10:44:42AM +0000, Michael Rasile wrote: > > found USB scanner (vendor=0x04a9 produce=0x220e at /dev/usb/scanner0 > > at /dev/usbscanner0 > > Ok, so the kernel USB scanner driver found it. > > > > Which version of sane-backends do you use (scanimage --version)? > > > > > backend version 1.0.9 > > Oh. Are you sure that this version supports your scanner? I can't find > "Lide" on the list of supported scanners for 1.0.9. 1.0.12 is the > current version of sane-backends but 1.0.10 may also work. > > But I'm not an plustek expert... > > > Thanks very much for your response. I apologize if I sent > > this to the wrong list. > > Well, sane-devel is ok. Just don't send your answers to only me, > because on the sane-devel mailing list there are more people (e.g. the > plustek maintainer) who know much more about your scanner and the > plustek backend. That's why I cc to the list again. > > > This will be the last time I'll post > > here.I'll monitor sane-devel mailing list and figure it out. Please > > find attached the debug output. If I am sending this to the wrong > > place again, please tell me and I will not do so again. > > Just send it to sane-devel@mostang.com. That's the mailing list > address. Not (only) to henning@meier-geinitz.de :-) > > > Even though I haven't solved the scanner problem yet, I am learning > > something from this. When it is solved, maybe I can help someone else > > with similar problems. > > That's very good. We need more people like you! > > > [plustek] >[usb] 0x04a9 0x220e< > > Ok, that should be your scanner. > > > [plustek] next device is a USB device (0x04A9-0x220E) > > [plustek] next device is an USB device > > [plustek] ># - device devicename< > > [plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)< > > [plustek] ># [usb] 0x07B3 0x0017< > > [plustek] >device /dev/usbscanner0< > > [plustek] Decoding device name >/dev/usbscanner0< > > [...] > > > [plustek] attach (/dev/usbscanner0, 0xbfffd170, (nil)) > > [plustek] Device configuration: > > [plustek] device name : >/dev/usbscanner0< > > [plustek] porttype : 1 > > [plustek] USB-ID : >0x04A9-0x220E< > > [...] > > > [plustek] usbDev_open(/dev/usbscanner0,0x04A9-0x220E) > > [plustek] Vendor ID=0x04A9, Product ID=0x220E > > [plustek] Device >0x04A9-0x220E<, is not supported! > > Looks like your backend is really too old. > > Bye, > Henning Henning, Well, you were correct. It was an outdated backend. I installed the latest sane backend and all is well and scanning. Finally! You'll not be getting any more scanner questions from me.:-) (at least for now) The answer was so simple, I'm embarassed that I didn't see it staring me in the face. Thanks for all your help. Couldn't have done it without you. Take care. Best regards, Mike -- Regards, Mike keeper@neo.rr.com "Don't Fear The Penguin." From berezin@stanford.edu Sun Jun 8 23:12:41 2003 From: berezin@stanford.edu (Sergey Berezin) Date: 08 Jun 2003 15:12:41 -0700 Subject: [sane-devel] Canon CS 8000F, USB and VMWare Message-ID: Hi, I recently acquired Canon CanoScan 8000F (USB 2.0), which is not supported by SANE yet, and I'm thinking of writing a backend for it. Or at least try to reverse-engineer the protocol... So the first question is, has anyone worked on this scanner yet? (Vendor=04a9 ProdID=220f, other details from /proc/bus/usb are at the end). Web search hasn't produced anything useful for me yet, except consistent complaints that Canon wouldn't release even the name of the chipset, saying nothing of the specs... Now, about breaking the protocol. I'm running VMWare (win2k) through USB v.1, and the scanner seems to be working fine. I installed SnoopyPro on the Windows side, but it stops snooping after the the first 120+ tiny control messages right after the scanner is plugged in. No data is logged when it actually scans. According to some other random source, it probably gets confused by the first bulk transfer. As an alternative, I've read in many places (including the archives of this mailing list) that it's possible to log USB messages from VMWare directly from the linux kernel module. Since I'm not familiar with the kernel code, I wonder if someone has already done this and can share the experience or a hacked usb module with me. Regards, Sergey. PS. The relevant portion of /proc/bus/usb/devices: T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 20 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=220f Rev= 3.01 S: Manufacturer=Canon S: Product=Scanner C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=8ms From F J Brooks" Message-ID: <000601c32e4a$6e9dd180$a8ec403e@default> On Sat, 31 May 2003 09:15:11 +0200, Henning Meier-Geinitz wrote: > So an older version of xsane works? The current version is 0.91, by > the way. Is there any advantage to me in installing xsane 0.91, eg, will it solve my current problems? I installed v.0.90 only two or three weeks ago (when it was then the latest). > Which version of sane-backends do you use? The version of sane-backends (and sane-frontends) I have is 1.0.11. > Does it depend on resolution or mode setting? Only in viewer mode or > also in the preview window and when you save the image? It doesn't depend on mode, in that I get the same result in the viewer window, when I copy/print, and if I save the image to file and then print. The preview window doesn't seem to work in that it shows a dark, hatched strip about 3 cm wide across the top of the window, with the rest of the window area (A4) white. > Different speed are rather uncommon when using different frontends. Are > you sure that you have only one version of sane-backends installed? No, I found that I also had sane-backends-1.0.8 [the original which came with my SuSE distribution]. So I removed it (using YaST2). That's when things got even worse! I found that, when I clicked on my desktop scanner icon to open /usr/local/bin/xsane, I got the error message: 'Sorry - KDesktop: KDEInit could not launch '/usr/local/bin/xsane'. When I tried the same thing using Konqueror, I got the error message: 'Error - Konqueror: Unable to run the command specified. The file or directory file: /usr/local/bin/xsane does not exist.' I found this rather surprising so I tried: fredjb@FJBrooks:~> ls -l /usr/local/bin total 5281 -rwxr-xr-x 1 root root 20461 2003-05-18 14:18 gamma4scanimage -rwxr-xr-x 1 root root 2255362 2003-06-0509:39 gimp drwxr-xr-x 11 root root 2464 2003-06-05 17:01 glib-2.2.1 -rwxr-xr-x 1 root root 68062 2003-05-10 16:30 glib-genmarshal -rwxr-xr-x 1 root root 4650 2003-05-10 16:29 glib-gettextize -rwxr-xr-x 1 root root 13446 2003-05-10 16:30 glib-mkenums -rwxr-xr-x 1 root root 58018 2003-05-10 16:30 gobject-query drwxr-xr-x 14 root root 1688 2003-06-05 17:02 gtk+-2.2.1 -rwxr-xr-x 1 root root 380652 2003-05-10 15:39 pkg-config drwxr-xr-x 4 root root 1664 2003-06-05 17:04 pkgconfig-0.15.0 -rwxr-xr-x 1 root root 1469115 2003-05-20 16:52 quiteinsane drwxr-xr-x 4 root root 1008 2003-06-05 16:58 quiteinsane-0.10 drwxr-xr-x 12 root root 1696 2003-06-05 16:59 sane-backends-1.0.11 -rwxr-xr-x 1 root root 3298 2003-05-18 14:18 sane-config -rwxr-xr-x 1 root root 141103 2003-05-18 14:18 sane-find-scanner drwxr-xr-x 7 root root 816 2003-06-05 17:00 sane-frontends-1.0.11 -rwxr-xr-x 1 root root 67552 2003-05-12 09:46 scanadf -rwxr-xr-x 1 root root 102425 2003-05-18 14:18 scanimage -rwxr-xr-x 1 root root 305145 2003-05-12 09:46 xcam drwxr-xr-x 9 root root 1344 2003-06-05 16:56 xsane-0.90 -rwxr-xr-x 1 root root 478145 2003-05-12 09:46 xscanimage fredjb@FJBrooks:~> [Many of these were recently downloaded from their source sites on the net, to replace older, out-of-date versions.] To see what the general position was, I then tried: fredjb@FJBrooks:~> sane-find-scanner found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/scanner found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/sg2 # Your SCSI scanner was detected. It may or may not be supported by SANE. Try # scanimage -L and read the backend's manpage. # No USB scanners found. If you expected something different, make sure that # you have loaded a driver for your USB host controller and have installed a # kernel scanner module. # 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. Followed by: fredjb@FJBrooks:~> scanimage -L device `avision:/dev/scanner' is a Hewlett-Packard ScanJet 5300C flatbed scanner device `avision:/dev/sg2' is a Hewlett-Packard ScanJet 5300C flatbed scanner fredjb@FJBrooks:~> I then tried [I have extracted only the bits I thought relevant to my scanner]: SANE_DEBUG_DLL=255 scanimage -L [sanei_debug] Setting debug level of dll to 255. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `net' [dll] add_backend: adding backend `abaton' [dll] add_backend: adding backend `agfafocus' [dll] add_backend: adding backend `apple' [dll] add_backend: adding backend `avision' [dll] add_backend: adding backend `artec' [...................] [dll] add_backend: adding backend `umax1220u' [dll] add_backend: adding backend `v4l' [dll] load: searching backend `v4l' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/libsane-v4l.so.1' [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-v4l.so.1' [dll] init: initializing backend `v4l' [dll] init: backend `v4l' is version 1.0.2 [dll] load: searching backend `umax1220u' in `/usr/local/lib/sane' [........................] [dll] init: backend `artec' is version 1.0.0 [dll] load: searching backend `avision' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/libsane-avision.so.1' [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-avision.so.1' [dll] init: initializing backend `avision' [dll] init: backend `avision' is version 1.0.55 [dll] load: searching backend `apple' in `/usr/local/lib/sane' [.......................] [dll] load: searching backend `net' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/libsane-net.so.1' [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-net.so.1' [dll] init: initializing backend `net' [dll] init: backend `net' is version 1.0.11 device `avision:/dev/scanner' is a Hewlett-Packard ScanJet 5300C flatbed scanner device `avision:/dev/sg2' is a Hewlett-Packard ScanJet 5300C flatbed scanner [dll] sane_exit: exiting [dll] sane_exit: calling backend `v4l's exit function [......................] [dll] sane_exit: calling backend `artec's exit function [dll] sane_exit: calling backend `avision's exit function [dll] sane_exit: calling backend `apple's exit function [dll] sane_exit: calling backend `agfafocus's exit function [dll] sane_exit: calling backend `abaton's exit function [dll] sane_exit: calling backend `net's exit function [dll] sane_exit: finished fredjb@FJBrooks:~> > What happens if you scan with scanimage? E.g. "scanimage >image.pnm". > Or xscanimage? Tried: fredjb@FJBrooks:~> scanimage >image.pnm Scanner whirred quietly for a while, but no other response. Then tried: xscanimage: Got 'Select Device' panel giving choice: 'avision:/dev/scanner avision:/dev/sg2 Chose former, clicked 'OK', got: avision/dev/scanner window, on which clicked: 'Preview Window'. Got Preview Window, dragged dashed line into rectangle covering roughly A4 size, then clicked 'Acquire Preview'. Scanner made fairly loud scratching-type noise plus hum, then intermittent whirring noise. Nothing appeared in Preview Window, and 'Acquire Preview' button reappeared. Clicked 'Scan' on main window. After a minute or two, scanner started with whirring noise, and got 'Scanning' panel with 'Receiving RGB data for out.pnm' progress bar graphic. Also second panel headed: 'Output Filename', listing directories and files. After ten-plus minutes, scanning seems complete and 'Scanning' panel disappears. Open out.pnm file and get colour image of object, slightly distorted as is longer and thinner than original. So that's where I am, Henning - as you can see, in rather a mess. Anything you can do to resolve the situation would be much appreciated. Thanks Best Fred From crapsite@gmx.net Mon Jun 9 07:52:12 2003 From: crapsite@gmx.net (Michael Herder) Date: Mon, 9 Jun 2003 08:52:12 +0200 Subject: [sane-devel] Czech translation Message-ID: <20030609065717.DCB6F188@panda.mostang.com> Hi, someone ("Josef") provided a Czech sane-backends translation. If there are no objections, I'll add it to CVS this evening or tomorrow morning. If someone else is also working on a Czech translation, please let me know. Thanks Michael From henning@meier-geinitz.de Mon Jun 9 09:42:57 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 9 Jun 2003 10:42:57 +0200 Subject: [sane-devel] Canon CS 8000F, USB and VMWare In-Reply-To: References: Message-ID: <20030609084257.GB20551@meier-geinitz.de> Hi, On Sun, Jun 08, 2003 at 03:12:41PM -0700, Sergey Berezin wrote: > I recently acquired Canon CanoScan 8000F (USB 2.0), which is not > supported by SANE yet, and I'm thinking of writing a backend for it. > Or at least try to reverse-engineer the protocol... Very good! Have you looked at the SANE list of scanners if there are any othere canon scanners with the same output of /proc/bus/usb/devices? Maybe they use the same chip for diffferent scanners and only chage the ids. > Now, about breaking the protocol. I'm running VMWare (win2k) through > USB v.1, and the scanner seems to be working fine. I installed > SnoopyPro on the Windows side, but it stops snooping after the the > first 120+ tiny control messages right after the scanner is plugged > in. No data is logged when it actually scans. According to some > other random source, it probably gets confused by the first bulk > transfer. I've heard about similar behaviour from several people. It doesn't happen with my USB scanners, however. Maybe it's also related to USB2? > As an alternative, I've read in many places (including the archives of > this mailing list) that it's possible to log USB messages from VMWare > directly from the linux kernel module. Since I'm not familiar with > the kernel code, I wonder if someone has already done this and can > share the experience or a hacked usb module with me. I haven't used vmware. Can you find out how it uses the Linux USB system exactly? Does it use the Kernel scanner driver? Or does it use libusb or even the /proc/bus/usb/001/* devices directly? Anyway, adding some printk messages in usb_bulk_msg() (drivers/usb/usb.c) that print the buffer of the bulk message may be worth a try. If vmware uses the USB scanner driver, there are already some debug macros in scanner.c/.h, just enable them. Bye, Henning From henning@meier-geinitz.de Mon Jun 9 10:03:50 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 9 Jun 2003 11:03:50 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <200306081017.41275.soumarmt@nerim.net> References: <20030606170749.GE5060@hmg1> <200306071743.45097.soumarmt@nerim.net> <20030607164004.GD6584@meier-geinitz.de> <200306081017.41275.soumarmt@nerim.net> Message-ID: <20030609090350.GE20551@meier-geinitz.de> Hi, On Sun, Jun 08, 2003 at 10:17:41AM +0200, Thomas Soumarmon wrote: > > Where did you get videodev2.h from? Is it from your version of libc > > (which one)? Or is /usr/include/linux a link to > > /usr/src/linux/include/linux and you have installed a 2.5 kernel? > > Looking with the rpmdrake tool (Mdk 9.1 installed) it says that videodev2.h > belongs to : > glibc-devel-2.3.1-10mdk or kernel-source-2.4.21-0.13mdk Kernel version 2.4.21 is not released yet and the pre versions don't have that file. Anyway, kernel headers shouldn't be used from userspace. So it's probably from glibc. I'm just wondering why it's not on my system, I'm using the same version of glibc. > I am wondering if this is exact or if it belongs to another package I would > have tried on the machine (they have been numerous). Shouldn't rpm know which package installed a specific file? Bye, Henning From soumarmt@nerim.net Mon Jun 9 10:45:56 2003 From: soumarmt@nerim.net (Thomas Soumarmon) Date: Mon, 9 Jun 2003 11:45:56 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <20030609090350.GE20551@meier-geinitz.de> References: <20030606170749.GE5060@hmg1> <200306081017.41275.soumarmt@nerim.net> <20030609090350.GE20551@meier-geinitz.de> Message-ID: <200306091145.56431.soumarmt@nerim.net> Hi Henning, > > Kernel version 2.4.21 is not released yet and the pre versions don't > have that file. Anyway, kernel headers shouldn't be used from > userspace. So it's probably from glibc. I'm just wondering why it's > not on my system, I'm using the same version of glibc. > > > I am wondering if this is exact or if it belongs to another package I > > would have tried on the machine (they have been numerous). > > Shouldn't rpm know which package installed a specific file? My problem is more the .tar.gz packages I installed and tested, and also the different kernels (2.4.19, 2.4.20 to 2.5.?? ). That is why I think it is specific to my installation, but I was wondering if anyone else had that problem so that it could help me to find the reason and the fix. I'll probably try to force reinstallation of glibc rpm to fix it. Your idea was right for the --disable-warnings. It compiles OK with it. Bye, Thomas. From henning@meier-geinitz.de Mon Jun 9 11:19:38 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 9 Jun 2003 12:19:38 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <200306091145.56431.soumarmt@nerim.net> References: <20030606170749.GE5060@hmg1> <200306081017.41275.soumarmt@nerim.net> <20030609090350.GE20551@meier-geinitz.de> <200306091145.56431.soumarmt@nerim.net> Message-ID: <20030609101938.GG20551@meier-geinitz.de> Hi, On Mon, Jun 09, 2003 at 11:45:56AM +0200, Thomas Soumarmon wrote: > My problem is more the .tar.gz packages I installed and tested, and also the > different kernels (2.4.19, 2.4.20 to 2.5.?? ). The kernels don't install anything in /usr/include. Well, at least they shouldn't. What may be a problem is a link /usr/include/linux to /usr/src/linux/include/linux. If you have such a link, all kinds of funny things may happen :-) In kernel 2.5, the header does exist. Bye, Henning From martin@mkcollins.org Mon Jun 9 13:32:46 2003 From: martin@mkcollins.org (Martin Collins) Date: Mon, 9 Jun 2003 13:32:46 +0100 Subject: [sane-devel] multiple images on XSane In-Reply-To: <000601c32e4a$6e9dd180$a8ec403e@default> References: <20030601132533.21859.53611.Mailman@panda.mostang.com> <000601c32e4a$6e9dd180$a8ec403e@default> Message-ID: <20030609133246.3f594f5a.martin@mkcollins.org> On Mon, 9 Jun 2003 06:42:08 +0100 "F J Brooks" wrote: > No, I found that I also had sane-backends-1.0.8 [the original which > came with my SuSE distribution]. So I removed it (using YaST2). > That's when things got even worse! Did you install sane and xsane using YaST2 or from source? Often the two methods will put things in different places and that can lead to conflicts if you have two versions installed. It sounds like you installed sane-backends-1.0.11 from source and xsane from rpm using YaST2. Removing sane-backends-1.0.8 with YaST2 probably removed xsane as well, since xsane depends on sane-backends. If you did install any of sane-backends, sane-frontends or xsane from source I suggest you remove them by going into their respective source directories and (as root) typing 'make uninstall'. Then get the latest rpms you can find and reinstall them using YaST2. This may put xsane in /usr/bin instead of /usr/local/bin. If so you will need to change your icon's properties accordingly. Martin From tang@mac.com Mon Jun 9 19:57:38 2003 From: tang@mac.com (Dino Tang) Date: Mon, 9 Jun 2003 11:57:38 -0700 Subject: [sane-devel] Re: Sane-devel digest, Vol 1 #473 - 6 msgs In-Reply-To: <20030606132518.24192.77979.Mailman@panda.mostang.com> Message-ID: <3D178672-9AAC-11D7-8F98-00039357FFB6@mac.com> I've been compiling sane-backends-1.0.12 on various Mac OS X system without any problem. I did compile libusb using the patch file Mattias sent me. The sm3600 backend should not be an issue. --Dino On Friday, June 6, 2003, at 06:25 AM, sane-devel-request@www.mostang.com wrote: > some time ago, there have been reports that it's necessary to comment > out sm3600 in dll.conf on MacOS X because otherwise SANE crashes in > that backend. Is this still the case? From karsten.festag@gmx.de Mon Jun 9 20:33:41 2003 From: karsten.festag@gmx.de (Karsten Festag) Date: Mon, 9 Jun 2003 21:33:41 +0200 Subject: [sane-devel] Microtek SlimScan C6 on Mac OS X 10.1.5 (sane-microtek2) In-Reply-To: <20030606165327.GD5060@hmg1> References: <20030606162459.65000.qmail@web13405.mail.yahoo.com> <20030606165327.GD5060@hmg1> Message-ID: <200306092133.41746.karsten.festag@gmx.de> Hi, though I'm the maintainer of the microtek2 backend I cannot help you much with the SCSI-over-USB stuff. But Oliver Neukum has done the linux 'microtek' kernel module and I think he can give you some useful hints if you ask him. Regards, Karsten On Friday 06 June 2003 18:53, Henning Meier-Geinitz wrote: > Hi, > > On Fri, Jun 06, 2003 at 09:24:59AM -0700, David Alan Hjelle wrote: > > I've been trying to get my Microtek SlimScan C6 working on my Macintosh > > running Mac OS X 10.1.5. > > [...] > > > So, I did some research. Apparently, the microtek2 backend only > > supports USB kernel extensions and not libusb? What would it take to > > modify the code so that it would work? > > All these scanners are SCSI. The SCSI protocoll is only transported > over the USB in case of USB devices. So they use a kernel > SCSI-over-USB driver (called "microtek"). > > So you either need to port this Linux driver to MacOS X or do the > SCSI-over-USB logic in the backend itsself. Maybe the maintainer can > tell you more about how complicated this may be. > > Userland SCSI-over-USB is used at least in the ma1509 and the avison > backends. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From gerhard@gjaeger.de Tue Jun 10 11:05:59 2003 From: gerhard@gjaeger.de (Jaeger, Gerhard) Date: Tue, 10 Jun 2003 12:05:59 +0200 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030608150101.GE18225@meier-geinitz.de> References: <20030604094900.GA7629@watcher.WorkGroup> <20030608104442.GA6034@watcher.WorkGroup> <20030608150101.GE18225@meier-geinitz.de> Message-ID: <200306101205.59357.gerhard@gjaeger.de> Hi Henning, On Sonntag, 8. Juni 2003 17:01, Henning Meier-Geinitz wrote: [SNIPSNAP] > Oh. Are you sure that this version supports your scanner? I can't find > "Lide" on the list of supported scanners for 1.0.9. 1.0.12 is the > current version of sane-backends but 1.0.10 may also work. > > But I'm not an plustek expert... seems that you one are now :-) Sorry for not responding on that "cry out", but I'm currently very short of time and probably will be during the next 4 weeks :-( Thanks for solving the problems here Gerhard From janez.dovc@ijs.si Tue Jun 10 12:41:05 2003 From: janez.dovc@ijs.si (Janez Dovc) Date: Tue, 10 Jun 2003 13:41:05 +0200 Subject: [sane-devel] HP ScanJet 5550C Message-ID: <001701c32f45$307d1ae0$0401a8c0@csl03> Hello, I am shure, you are all tired of such questions, but I will try and ask anyway: Does anyone know if somebody works on driver for HP ScanJet 5550C? What is tendence, is there any posibility for such driver to be available in the close future? Thanks for answers, Janez From lnovak@dragon.klte.hu Tue Jun 10 13:29:48 2003 From: lnovak@dragon.klte.hu (Novak Levente) Date: Tue, 10 Jun 2003 14:29:48 +0200 (MET DST) Subject: [sane-devel] Video4linux Message-ID: Recently, the videodev2.h thread reminded me an old problem with the video4linux (or is it v4l?) backend. That is, only the first "scan" produces a (more or less) correct image, while the others have the succesive scanlines badly shifted. Is it normal? Can it be avoided? I know I can use other software (like XawTV) to take snapshots, but if there is such a SANE backend, it should work correctly. Also, a v4l2 backend would be welcome too. Levente From henning@meier-geinitz.de Tue Jun 10 19:17:24 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 10 Jun 2003 20:17:24 +0200 Subject: [sane-devel] HP ScanJet 5550C In-Reply-To: <001701c32f45$307d1ae0$0401a8c0@csl03> References: <001701c32f45$307d1ae0$0401a8c0@csl03> Message-ID: <20030610181724.GB1036@meier-geinitz.de> Hi, On Tue, Jun 10, 2003 at 01:41:05PM +0200, Janez Dovc wrote: > I am shure, you are all tired of such questions, but I will try and ask > anyway: No problem. Most of the time all the information we have is in the lists of (un)supported scanners or the search engine. http://panda.mostang.com/sane/sane-supported-devices.html > Does anyone know if somebody works on driver for HP ScanJet 5550C? I don't think so. > What is tendence, is there any posibility for such driver to be > available in the close future? If you start writing one, probably yes :-) Most of the time SANE developers don't write drivers for completely new scanners. Usually someone like you has such a scanner and wants support for it. So he writes a driver and becomes a SANE developer that way. Do you own such a device? If yes, could you please send us the output of /proc/bus/usb/devices when it's plugged in? So we have at least some information on the ids of the scanner. If you have more information, e.g. which chipset is used, this is also appreciated. Bye, Henning From henning@meier-geinitz.de Tue Jun 10 19:22:32 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 10 Jun 2003 20:22:32 +0200 Subject: [sane-devel] Video4linux In-Reply-To: References: Message-ID: <20030610182232.GA1219@meier-geinitz.de> Hi, On Tue, Jun 10, 2003 at 02:29:48PM +0200, Novak Levente wrote: > Recently, the videodev2.h thread reminded me an old problem with the > video4linux (or is it v4l?) backend. The backend is called "v4l". > That is, only the first "scan" > produces a (more or less) correct image, while the others have the > succesive scanlines badly shifted. Is it normal? If I remeber correctly, it didn't happen with my card the last time I checked. > Can it be avoided? > I know I can use other software (like XawTV) to take snapshots, but if > there is such a SANE backend, it should work correctly. The code of v4l suffers severe bitrot. The TODO mentions: * v4l: - Geometry support is missing - Frequency setting is missing - check if v4lctl distributed with xawtv can be used - Use #define _LINUX_TIME_H 1 just before including videodev.h or videodev2.h to avoid trouble if /usr/include/linux is a link. - Add v4l updates from Martin Palm, see http://www.meier-geinitz.de/sane/misc/sane-v4l-update.tar.gz - compilation seems to break when video4linux version 2 is installed? Martin Palm worked on the v4l backend but I haven't heard from him for quite some time. YOu can try the code in the above mentioned archive but I don't remember if it really works. You could bug Martin Palm or Julien Blache (who also wanted/wants to work on v4l) a bit :-) > Also, a v4l2 backend would be welcome too. Yes, please go ahead and write it :-) There is an old v4l2 backend but I guess that's a different version 2. Bye, Henning From jb@jblache.org Tue Jun 10 20:17:41 2003 From: jb@jblache.org (Julien BLACHE) Date: Tue, 10 Jun 2003 21:17:41 +0200 Subject: [sane-devel] Video4linux In-Reply-To: <20030610182232.GA1219@meier-geinitz.de> (Henning Meier-Geinitz's message of "Tue, 10 Jun 2003 20:22:32 +0200") References: <20030610182232.GA1219@meier-geinitz.de> Message-ID: <87n0gpbv3e.fsf@frigate.technologeek.org> Henning Meier-Geinitz wrote: Hi, > You could bug Martin Palm or Julien Blache (who also wanted/wants to > work on v4l) a bit :-) It's on my todo list for the upcoming weeks :) JB. -- Julien BLACHE From nakal@web.de Tue Jun 10 22:17:58 2003 From: nakal@web.de (Nakal) Date: Tue, 10 Jun 2003 23:17:58 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II Message-ID: <200306102317.58064.nakal@web.de> --Boundary-00=_Gsk5+USHsb9suHM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Well, how to say... it doesn't work. I compiled xsane-0.90 from ports. I tried to set 'norealcal' and/or 'noprecal'. The scanner always causes a timeout (see attachment) while starting "scanimage -d 'microtek:/dev/scanner'". Starting xsane or even scanimage without the correct '-d' option will freeze the system completely. Even --help will freeze it, I wonder why. Am I doing something wrong? Martin --- Here is data about my system which might be important for You: xxx@xxx:/usr/home/xxx> uname -a FreeBSD xxx 4.8-STABLE FreeBSD 4.8-STABLE #1: Sat May 3 22:35:40 CEST 2003 xxx@xxx:/usr/src/sys/compile/XXX i386 xxx@xxx:/usr/home/xxx> camcontrol devlist at scbus0 target 3 lun 0 (pass0,cd0) at scbus0 target 4 lun 0 (pass1,cd1) at scbus0 target 5 lun 0 (pass2,cd2) at scbus0 target 6 lun 0 (pass3) at scbus0 target 6 lun 1 (pass4) at scbus0 target 6 lun 2 (pass5) at scbus0 target 6 lun 3 (pass6) at scbus0 target 6 lun 4 (pass7) at scbus0 target 6 lun 5 (pass8) at scbus0 target 6 lun 6 (pass9) at scbus0 target 6 lun 7 (pass10) Part of dmesg: sym0: <875> port 0xc400-0xc4ff mem 0xe7002000-0xe7002fff,0xe7001000-0xe70010ff irq 11 at device 11.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking I get some errors in my dmesg like this (probably not important): Waiting 15 seconds for SCSI devices to settle (probe6:sym0:0:6:0): phase change 6-7 6@0f71418c resid=4. sym0: unexpected disconnect (probe1:sym0:0:6:1): phase change 6-7 6@0f71418c resid=4. sym0: unexpected disconnect --Boundary-00=_Gsk5+USHsb9suHM Content-Type: application/x-gzip; name="scanimage.log.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="scanimage.log.gz" H4sICDQ65j4AA3NjYW4ubG9nAO1d62/bRhL/3r9imqJIcrBkLinqYcANEttphGseFzntFUUhLMml zDNFMnzYVv76m1lKMknRpGhLaj7QVVKRO4/dmd/OzoxF5a+Ie8KZWsJIZn/DRMSx481AXoIrboQL vg1zxwz9WFxD7ANTh90f/lrd+RuIf+p4TnwC8H589vnj5cW/8eYigivhuv6P8OJG6TKty14+xGX6 nu3MOr/AT/DFM/35XHgx2D4y39JcXMcTpNhyIm64Ap6FgrtgctcxQh47vvcMQj/BaYuo231wamsl nk/8yP4Q5eeCeLh1XBcMgVMKTcdwF6uZWNuo23JNJtk6hCAUT1hYyv0Q4Vmq4lNOxVMXB/AlogU9 W5v1WSoyJGUxGNy8Fp5Fa8XZdRAJrKvkrGv6lqjXFJmRA/+S/ymg4KuPf2e5eBxz82oamdzzRIis x5a4OQ54FGmVZH4gPFrAluQRLobIxx/+82X8+c8srWNNVxcF2wU8jGhJXxMnXFSNoYIPfgzcg4s+ dDpkspisJ10GNAkcRWetfZSVZCXz4AElcHp6CpPXHy6O36928soxy81JFFmO0/UPTNLFwzgVDW9c 37xeE8znWTZ0i8ZAZ6Dg3wawvvSVAj0LeiPoaaCr0LNB70FPh54BWV5dgz6+GPQF0dMbA/o6DFRQ Fck+ojfrV5ZX00EVoKXaNalIW9L3+qCixgHoOKpJMpbjJRpNTskkOUijDUHDaWug2DA0wdRpCUKA Lm/m1ssyL6X+lePdgn79sm3Y0j2fReDjxrun2OC7Zzkv4ORc3DimgMtFIOAM9+UJKHdKP0vxHu+6 6zE9twV/Rzz5IXzgcxx8vjoLnmOMSLmWA6T9Pb8m/WMcg+clMiaBMB3bMWESh7jdiOtsMoa3x3/8 TmA9u/xN14ZKjvOtE85veSjQADdIr3f7LDe+EgAYlyIMPCdAkuhnZY7coN5lWe7PIgp8L8Ktx2NO wXLOY2kdtmne8ZzPKEac8YAbjuvEzkYAJ4NEuNt/w+DO0VvvuGvHPp4Jv4Z8geZ10QYF9b6byHg5 iUUAE+cb8bOfQf+ZlnBxF3DPElaOMAkICa9gIaKcIdL7SPzGiSP4hCuf8Hngom+GOaXv+V0XLN9M 5OEVoUoZrOWylWpCXJqq4/67gx4bjSBw7oSbm8TbEMEACUZ5MkM6DsCOh8+eR7lJ/ET5h5E4btxx PLha2onWruK6z/1bz/W5JQ/RAKO1CL3oFfyZX/E5+ezMn2M4jVLvZkfPfC8OeRSvkh+S3Utt6kcJ Aip7P8v42vpfEsVS9eSKW/7t8TtnduXin9ToKCND8t6xaOav8JzOqT93Zk6M0d0IiRGXFh37th2J mCizhL/y+ZzDZapP2ljFkIYWDxFfZCUGxiLGty/m0h8iiK/QpS9L9r+fhLjNPwaEkyI03wpERowR AP1iuzw28JJWcv4WogcQdb5yPfESnDJ0yLq8+wZPHDS0eY223BCxpBl7aC0XTzZppvuf5TCmZtZi w4KXIfciPEeFZy7Q4jyINyTlVJGv0y2GuRAd7ZtbRLjCTN0mhdsUHeSeLzollbMmmoivCU4DbRe4 mMZ0jEVHvoEXWoeSi5wzLq9CQaiNIqBZPGheChbpjDoMcwNreQOjEV6vbV2YF8o7XyaXaZBxvqX5 lgRQFfkkxojU8e0OxUU0eSZZK7KNPdpwCF6xij/yTVRCujytLnD6CNXqQ6syA7viQbCoTxhlPrfk qs8TtyHMZYrbMLS5Ypsrtrlimyu2uWKbK7a5Ypsrtrnid5IrUiZXepNg7KBWS55tZR3QJZUZCh4L WGqqIKS01EGjfFsT02bDg0tGvzix7Qrm126+Eb3qBpfndEW1MJNBQEKztIGcpSVkdWIH4+wNun8r lmXL2kSTV5kqYwE/DSJ4M5cLI8HUL40v2SHk+ppwtFoB8QUaC+Pm5lxMitu+u6SDF/j/U+WIm/T3 DXdPlTvDNmy7ZylHjmf7eK1s/rpiWyE9s0LITKxmO8Vj3QydIMag8EJ5WWbCB4hZE2K1CbHWhLjX hFhvQtxvQjxoQjxsQjxq5JRmLmzkQ9bIiayRF1m5G8vAzno5tA8VnfHBsDnYWTkYSlXqJSofsb9Y I0ixRphijUDFGqFKbYQqtVlkaIQqtRGq1EbBQW0UHdRGvlQb+VJt5Eu1kS+1Rr7UGvlSaxbmy31Z ugHVshOuatOXStF2IqVsLuZjokHjmMfyOtczX63kCWZ41AIaR9DmC4got38IVFhCYVGOGX1pmpin wKwsFLPE5SGklQ2YVAltwxVNqYsAp9Rpo+hWz2P5cTQNRDidz/FK6460gaIM6/lke+GekbHukDFF zRXxf4zPL999Gv8Xxw1h+1juYwmDZXO+tVUunz7xIbsCigIQBK5kQznLdzkBkjeK8gJiqgCl+Y4A fZvrJXVvOSbBIVW8oBQcggUNn7limn44pDDYlUUJFtlTm1RVj8pkvgPKkZJ2bI6oX1NJj/VKJT03 TRFF/kYPumstezVTWcNUj8r+UVlz4wjm/A7H9EpmY4EVmc0TN86RzRF300hW0hsmzQ5SR4oHU5dq nY31VbilK7eXrFWLI4Qduk87ME6iDdbCOGbLJ2hkQtERMG00AqCP5uQg9QuAQv100GAwANDxMtfD oOr9E6HtJHs7cO7WAKXOypUVptd0FZQgN/GodyuNj1BnwxGTjIknexarLSCnmDY96DIrAGNcnFUp r+93C48CaXLWVeTPFqGJNDtzPkM0rtAJ8pqAIvuUKPlOzmnZWeQxDMHAaHAsb2QlcJNaECQiFBZI kG9MgdxdcBjdwi3hz6flDYN/wOMbUzqBGQZmI4kWR9JRt44VXx0h3Zw7nmyr5zSWLhtpcMdN6bNa JzBQJXfq7yPwlt4fqLmVy3nIpVGzvOwsWQo2EttOu8V9pio4iyWqPGGRCnWQAy43r6eOF/tTctbG b9FWg4SuykE6gxB7KL0/BIi+LZXjTjBPYBN9Ja5vrkwd9jR1Q5mcwneANXVQjTXV3jXW8p6txZo6 2DfWCgdKi7U9YQ3tXI01gVjs7RJrBc/WYQ3J9401NtRarB0Aa2jnaqyN7B1jreDZOqwh+d6xxliL tUNgjbFqrOm7jmsFz9ZijbF9Y03RRi3WDoA1tHM11mDXca3g2TqsIfmesTbqt6XBAaCGZq5GmjmQ eNsZ0gp+rQEaUu8ZZ8NRWxYcAGdo5ppuh71bnBX8WoMzpN43ztS2JDgEztSaikDbcTwr+LUOZ+q+ 64GB3pYDB8AZmrmmy4HxTN0hzgp+rcEZUu8ZZ/1BWwocAGdo5mqc8cFucVbwaw3OkHrfOFPaOuAQ OFNq6gB9x/Gs4Nc6nCn7rgN0ra0DDoAzNHM1ztiO41nBrzU4Q+o946zXb+uAA+AMzVzT18B4xnaI s4Jfa3CG1HvGmTZq64AD4AzNXI2z4WC3OCv4tQZnSL1vnLG2DjgEzlhNHaDtOJ4V/FqHM7bvOkDt tXXAAXCGZq7GmT2g97vDWcGvNThD6n3/jnPQ1gEHwBmauaavYe8WZwW/1v2Cc7D3zwgpbR1wCJwp NXVAf8fxrODX+l+k7z0/a2F2iPSspqux42imNSoCMjVAnvExGFP7ml7AmLJHiEl1j4OY8KzSBzWi 2A/KBiYXHyYXPwLYFpwWNNA3MdDN+6/ryT2iMHe8Y3poZRbyRfrtuzfcTYiD9Y7LPp7aPqT1PT+k lY/DFU8DNURMZvw7frzr8Yt68MGwJ4j8xx8pe8Lcd/Ew2hPU7wW4Dz8A9wSZdUfv40WXHdr0rAlV nspA65ce28xIT2t5fhebKgWJ8mykEzsUcbjArQj6gSfPdjl5dmjTqzud/aFtr+1y9mrR9vepAhIX 94jNnfz3rW2V7mSSlqz0izD0Q7CSMP1XBORXBI6PP25MBrlNUTyusooz8inyrJ8mTb+2DBcZ+3HJ d92brh+VfhuRuHNK8yS6f1L8lwtmvm8ZC9H94f/37aKWHmEAAA== --Boundary-00=_Gsk5+USHsb9suHM-- From henning@meier-geinitz.de Wed Jun 11 10:27:48 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 11 Jun 2003 11:27:48 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306102317.58064.nakal@web.de> References: <200306102317.58064.nakal@web.de> Message-ID: <20030611092748.GB3357@meier-geinitz.de> Hi, On Tue, Jun 10, 2003 at 11:17:58PM +0200, Nakal wrote: > Well, how to say... it doesn't work. > > I compiled xsane-0.90 from ports. I tried to set 'norealcal' and/or > 'noprecal'. The scanner always causes a timeout (see attachment) while > starting "scanimage -d 'microtek:/dev/scanner'". Looks like a SCSI problem (either hardware or kernel driver). My Mustek SCSI scanners work fine with FreeBSD/386 so I don't think there is a general bug in the SCSI code of SANE. Maybe you need to disable automatic disconnect/reconnect and/or synchronous transfers. Some scanners don't like that. > Starting xsane or even scanimage without the correct '-d' option will freeze > the system completely. Even --help will freeze it, I wonder why. Kernel bug mist probably. User space programs should never be able to freeze the kernel. You can try to find out by which backend causes the problem by running SANE_DEBUG_DLL=255 scanimage -L and checking the last lines of the output. Disable that backend in dll.conf. That doesn't happen here either so it's either related to your SCSI adapter (driver) or the scanner. Well, I used FreeBSD 5.0 but I don't remeber such problems with older versions. > Am I doing something wrong? Probably not, but maybe your kernel :-) > xxx@xxx:/usr/home/xxx> camcontrol devlist > at scbus0 target 3 lun 0 (pass0,cd0) > at scbus0 target 4 lun 0 (pass1,cd1) > at scbus0 target 5 lun 0 (pass2,cd2) > at scbus0 target 6 lun 0 (pass3) > at scbus0 target 6 lun 1 (pass4) > at scbus0 target 6 lun 2 (pass5) > at scbus0 target 6 lun 3 (pass6) > at scbus0 target 6 lun 4 (pass7) > at scbus0 target 6 lun 5 (pass8) > at scbus0 target 6 lun 6 (pass9) > at scbus0 target 6 lun 7 (pass10) Bah, it shows up on all LUNs. I don't think it's important but maybe the SCSI driver has an option to disable that behaviour. > Part of dmesg: > sym0: <875> port 0xc400-0xc4ff mem 0xe7002000-0xe7002fff,0xe7001000-0xe70010ff > irq 11 at device 11.0 on pci0 > sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking Fast-20? I guess the scanner wil do 10 MHz at most. Maybe reducing the max speed will work together with the other options mentioned. > I get some errors in my dmesg like this (probably not important): > Waiting 15 seconds for SCSI devices to settle > (probe6:sym0:0:6:0): phase change 6-7 6@0f71418c resid=4. > sym0: unexpected disconnect Ah, try disabling reconnect/disconnect. Bye, Henning From lnovak@dragon.klte.hu Wed Jun 11 14:39:36 2003 From: lnovak@dragon.klte.hu (Novak Levente) Date: Wed, 11 Jun 2003 15:39:36 +0200 (MET DST) Subject: [sane-devel] Video4linux In-Reply-To: <20030610182232.GA1219@meier-geinitz.de> Message-ID: On Tue, 10 Jun 2003, Henning Meier-Geinitz wrote: > The backend is called "v4l". OK, I was not at my Linux box and did not remember its name. > > That is, only the first "scan" > > produces a (more or less) correct image, while the others have the > > succesive scanlines badly shifted. Is it normal? > > If I remeber correctly, it didn't happen with my card the last time I > checked. > > > Can it be avoided? > > I know I can use other software (like XawTV) to take snapshots, but if > > there is such a SANE backend, it should work correctly. > > The code of v4l suffers severe bitrot. The TODO mentions: > > * v4l: > - Geometry support is missing > - Frequency setting is missing Maybe it is the problem? I have a PAL system. But anyway, the first scan of the session is OK. Only the later ones have this problem. > - check if v4lctl distributed with xawtv can be used > - Use #define _LINUX_TIME_H 1 just before including videodev.h or videodev2.h to avoid > trouble if /usr/include/linux is a link. > - Add v4l updates from Martin Palm, see > http://www.meier-geinitz.de/sane/misc/sane-v4l-update.tar.gz > - compilation seems to break when video4linux version 2 is installed? Don't think so. I have and use v4l2 on my system (kernel 2.4.21-pre5, but with v4l2 patch), all the applications are linked against it (those which use v4l, of course). v4l2 has a compatibility mode, which makes it appear as v4l1 to the non-v4l2-compliant applications. But as v4l2 is not as mature as v4l1 and its API has slightly changed IIRC, this might perturb some programs. > > Martin Palm worked on the v4l backend but I haven't heard from him for > quite some time. YOu can try the code in the above mentioned archive > but I don't remember if it really works. > > You could bug Martin Palm or Julien Blache (who also wanted/wants to > work on v4l) a bit :-) > > > Also, a v4l2 backend would be welcome too. > > Yes, please go ahead and write it :-) > Would do it, but unfortunately don't speak C enough for this. Levente From crapsite@gmx.net Wed Jun 11 17:55:43 2003 From: crapsite@gmx.net (Michael Herder) Date: Wed, 11 Jun 2003 18:55:43 +0200 Subject: [sane-devel] (slightly OT) Using an Artec E+ 48U with Knoppix 3.1 Message-ID: <20030611165422.365A33E@panda.mostang.com> Hi, people asked me, whether it's possible to use the Artec E+ 48U with Knoppix 3.1 (Debian based Linux Demo, which boots from CD). Therefore I've set up a small web page, that shows how one can use this scanner, which isn't supported by the SANE version shipping with Knoppix 3.1. See: http://www.angelfire.com/linux/crapsite/artec2knoppix.html bb Michael From nakal@web.de Wed Jun 11 19:29:15 2003 From: nakal@web.de (Nakal) Date: Wed, 11 Jun 2003 20:29:15 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <20030611092748.GB3357@meier-geinitz.de> References: <200306102317.58064.nakal@web.de> <20030611092748.GB3357@meier-geinitz.de> Message-ID: <200306111902.41911.cinek@gmx.de> On Wednesday 11 June 2003 11:27, Henning Meier-Geinitz wrote: > Looks like a SCSI problem (either hardware or kernel driver). My > Mustek SCSI scanners work fine with FreeBSD/386 so I don't think there > is a general bug in the SCSI code of SANE. You might be right. I will check the cables and the terminator. > You can try to find out by which backend causes the > problem by running > > SANE_DEBUG_DLL=255 scanimage -L It's freezing in random backends. I removed all except microtek. > Fast-20? I guess the scanner wil do 10 MHz at most. Maybe reducing the > max speed will work together with the other options mentioned. No, I think it might be hardware, because I have 3 SCSI cdrom-drives attached and they work fine. > Ah, try disabling reconnect/disconnect. Nope... still same. Thanks for the response Henning. At least I know that it SHOULD work. I will give feedback after I've checked the hardware. Martin From homer_889@hotmail.com Thu Jun 12 01:29:34 2003 From: homer_889@hotmail.com (Homer) Date: Thu, 12 Jun 2003 10:29:34 +1000 Subject: [sane-devel] Query Message-ID: This is a multi-part message in MIME format. ------=_NextPart_000_0031_01C330CD.849CBFC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I know it's a really silly question but I'd thought I'd ask it anyway. = I'm using mandrake 9.1 and the Xsane package will detect and setup my = canon N640P. It will run as root but not as my normal user. I've = actually scanned from root but the scanner won't detect from user. It's probably a very simple answer to this but I've missed it somewhere, = any reasonable suggestions will be appreciated to fix this problem. thanks in advance HJ ------=_NextPart_000_0031_01C330CD.849CBFC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
I know it's a really silly = question but I'd=20 thought I'd ask it anyway. I'm using mandrake 9.1 and the Xsane package = will=20 detect and setup my canon N640P. It will run as root but not as my = normal user.=20 I've actually scanned from root but the scanner won't detect from=20 user.
It's probably a very simple answer to = this but I've=20 missed it somewhere, any reasonable suggestions will be appreciated to = fix this=20 problem.
thanks in advance
HJ
------=_NextPart_000_0031_01C330CD.849CBFC0-- From kilgota@banach.math.auburn.edu Thu Jun 12 01:51:40 2003 From: kilgota@banach.math.auburn.edu (Theodore Kilgore) Date: Wed, 11 Jun 2003 19:51:40 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <18Qp5L-1j8CMCC@fmrl02.sul.t-online.com> Message-ID: Henning, Perhaps you would be one to know this, or it is fine if someone else answers the question, too. I want this information because I am trying to write a driver for a camera, as a summer project (specifically for the lots of cameras which call themselves USB vendor:product 0x2770:0x9120 and belong to Class ff, Subclass ff, Protocol ff. These are some really cheap cameras (352x288 max resolution) so I took it on as a summer project, to learn how they work and to write a driver. My question is sufficiently on topic that I feel comfortable asking it from the sane-devel mailing list. Perhaps the gphoto-devel list would be a more appropriate place to ask, but I am sorry to say that the gphoto-devel mailing list seems unable to add me as a subscriber in spite of my attempts, over the past several weeks, to subscribe to it. My question: What are "gamma" and "bayer" and where can I find some literature to read up on such topics? I ask this because I am at this point able to get a picture out of the camera by the very primitive procedure of editing a debug log file. I know that both the Windows driver and the gphoto camlib program which I have written give identical data output. But a. the actual output is exactly one byte per pixel, and saving it as a "raw" file leads nowhere except to error messages when one tries to open them. b. The log output for one picture is much larger (because of whitespace), and putting a BMP or a PPM header on it actually turns the log output (after suitable editing to remove everything but the actual data) into a picture which roughly approximates the actual picture taken but is of quite low quality. So I suspect that some kind of interpolation routine is going on, in order to fill up the whitespace. The point is, what kind of interpolation? What different kinds are there? And how are they implemented? One can obviously confront similar problems when dealing with scanner output, and my questions relate to basic techniques in video imaging. Therefore, on the grounds that I do subscribe to the sane-devel list and am apparently unable to subscribe to the gphoto-devel list in spite of strenuous efforts to do so, I ask about the problems here, instead. I hope, as I said already, that these questions are considered of general interest. I would welcome any information, explanations, or references for reading about the relevant topics. I don't seem to find very much about this with Google, or perhaps I don't know exactly what to search for, so even the right words for a search would help, I think. Thank you very much, Theodore Kilgore From cadu07@bol.com.br Thu Jun 12 03:37:22 2003 From: cadu07@bol.com.br (Cadu) Date: Wed, 11 Jun 2003 23:37:22 -0300 Subject: [sane-devel] Scanner Genius CP HR6X - EPP -> It works! Message-ID: <200306112337.22426.cadu07@bol.com.br> Hi people! Recently i've made my Genius ColorPage HR6X EPP works on Linux, with Plustek module. It works fine! I hope I write an English-HOWTO in a few days. Now I have a Portuguese-HOWTO . . . :) Maybe I'll make an web page with pictures of my scanner opened ( I've opened it to view the chipset :)), and with pictures scanned by its. Sorry for my bad english . . . ;-) -- Cadu cadu07@bol.com.br http://cadu.webhop.org/ From henning@meier-geinitz.de Thu Jun 12 09:12:08 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 12 Jun 2003 10:12:08 +0200 Subject: [sane-devel] Query In-Reply-To: References: Message-ID: <20030612081208.GA10868@meier-geinitz.de> Hi, On Thu, Jun 12, 2003 at 10:29:34AM +1000, Homer wrote: > I know it's a really silly question but I'd thought I'd ask it anyway. It's not that silly. > I'm using mandrake 9.1 and the Xsane package will detect and setup my > canon N640P. It will run as root but not as my normal user. I've > actually scanned from root but the scanner won't detect from user. > It's probably a very simple answer to this but I've missed it > somewhere, any reasonable suggestions will be appreciated to fix this > problem. The answer is simple: it's a permission proble. The solution depends on how you access you USB scanner. Either you use libusb or /dev/usb/scanner*. "scanimage -L" prints which one you use. The manpage sane-usb describes on how to setup permissions for these two cases: LIBUSB The permissions for the device files used by libusb must be adjusted for user access. Otherwise only root can use SANE devices. For Linux, the devices are located in /proc/bus/usb/. There are directories named e.g. "001" (the bus name) containing files "001", "002" etc. (the device files). The right device files can be found out by running scanimage -L as root. Setting permissions with "chmod" is not permanent, however. They will be resetted after reboot or replugging the scan- ner. It's also possible to mount the usbfs with the option "devmode=0666", e.g. by using the following line in /etc/fstab: none /proc/bus/usb usbfs defaults,devmode=0666 0 0 However, this way everyone has access to all USB devices. Another way to set per- missions is to use the hotplug utilities (http://linux-hotplug.sourceforge.net/), which support dynamic setting of access permissions. Last, the frontends can be run as root. However, that's not recommended for security reasons. GENERIC KERNEL SCANNER DRIVER Ensure that the access permissions for the USB device are set appropriately. We recommend to add a group "scanner" to /etc/group which contains all users that should have access to the scanner. The permission of the device should then be set to allow group read and write access. For example, if the scanner is at USB device /dev/usb/scanner0, then the following two commands would set the permission correctly: $ chgrp scanner /dev/usb/scanner0 $ chmod 660 /dev/usb/scanner0 Bye, Henning From henning@meier-geinitz.de Thu Jun 12 09:28:14 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 12 Jun 2003 10:28:14 +0200 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: <18Qp5L-1j8CMCC@fmrl02.sul.t-online.com> Message-ID: <20030612082814.GB10868@meier-geinitz.de> Hi, On Wed, Jun 11, 2003 at 07:51:40PM -0500, Theodore Kilgore wrote: > What are "gamma" Very much simplified: A gamma table is used to transfer the color space used by your input device (scanner, camera) to the color space of your output device (display, printer). A gamma value (or factor) can be used to create a gamma table. Search for "gamma table" and "gamma factor" at google and you'll find lots of documentation. > and "bayer" I think that's a kind of halftoning (transferring gray/color imagaes to black/white). > So I suspect that some kind of interpolation routine is going on, in order > to fill up the whitespace. The point is, what kind of interpolation? What > different kinds are there? And how are they implemented? I don't really understand what you mean by "whitespace". Interpolation is usually used to create resolutions higher than supported by hardware. It's just a marketing gag, you don't get better images, just bigger ones. Example: You have a gray image with 2x2 pixels: 100 200 50 100 To expand it by 50% in both directions you'd interpolate like this: 100 150 200 75 112 150 50 75 100 > One can obviously confront similar problems when dealing with scanner > output, and my questions relate to basic techniques in video imaging. The scanners return image data in lots of differnt formats. E.g. 8, 10, 12, 16 bits/color, all the pixels of one color after each other, or all the colors of one pixel after each other and so on. Maybe your data is also compressed? Or it's transferred as a jpeg? bye, Henning From a.deuring@satzbau-gmbh.de Thu Jun 12 11:10:40 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Thu, 12 Jun 2003 12:10:40 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <20030611092748.GB3357@meier-geinitz.de> <200306111902.41911.cinek@gmx.de> Message-ID: <3EE851A0.CCA64E53@satzbau-gmbh.de> Nakal wrote: > > On Wednesday 11 June 2003 11:27, Henning Meier-Geinitz wrote: > > > Looks like a SCSI problem (either hardware or kernel driver). My > > Mustek SCSI scanners work fine with FreeBSD/386 so I don't think there > > is a general bug in the SCSI code of SANE. > > You might be right. I will check the cables and the terminator. > > > You can try to find out by which backend causes the > > problem by running > > > > SANE_DEBUG_DLL=255 scanimage -L > > It's freezing in random backends. I removed all except microtek. A long shot: IIRC, these Microtek scanners may freeze, if you access them with another LUN than 0 -- but they show up with all LUN values from 0 to 7. So, if any backend tries to access the scanner with a non-zero LUN, you'll have an unaccessible scanner. I don't know any details, but *if* a SCSI command to a non-zero LUN confuses the scanner in a way that the entire SCSI bus is blocked, worse errors may occur, e.g., the disk with the root partition may be unaccessible. So it's best to connect these cheap scanners to their own SCSI bus. And you should tell FreeBSD not to look for all LUNs of the scanner while it tries to detect devices on the SCSI bus. Abel From gerhard@gjaeger.de Thu Jun 12 12:36:55 2003 From: gerhard@gjaeger.de (Jaeger, Gerhard) Date: Thu, 12 Jun 2003 13:36:55 +0200 Subject: [sane-devel] Scanner Genius CP HR6X - EPP -> It works! In-Reply-To: <200306112337.22426.cadu07@bol.com.br> References: <200306112337.22426.cadu07@bol.com.br> Message-ID: <200306121336.55470.gerhard@gjaeger.de> Hi, On Donnerstag, 12. Juni 2003 04:37, Cadu wrote: > Hi people! > > Recently i've made my Genius ColorPage HR6X EPP works on Linux, with > Plustek module. good to hear that! > It works fine! I hope I write an English-HOWTO in a few days. Now I have a > Portuguese-HOWTO . . . :) If you want to, I can put this or at least the url of your web-site to the Plustek SANE driver page... > Maybe I'll make an web page with pictures of my scanner opened ( I've > opened it to view the chipset :)), and with pictures scanned by its. > > Sorry for my bad english . . . ;-) No problem so far :-) Gerhard From ljm@xs4all.nl Thu Jun 12 13:53:52 2003 From: ljm@xs4all.nl (Laurent-jan) Date: Thu, 12 Jun 2003 14:53:52 +0200 Subject: [sane-devel] "gamma" and "bayer" ? What are they? References: <18Qp5L-1j8CMCC@fmrl02.sul.t-online.com> <20030612082814.GB10868@meier-geinitz.de> Message-ID: <3EE877E0.10206@xs4all.nl> Henning Meier-Geinitz wrote: > Hi, > > On Wed, Jun 11, 2003 at 07:51:40PM -0500, Theodore Kilgore wrote: > >>What are "gamma" > > > Very much simplified: A gamma table is used to transfer the color > space used by your input device (scanner, camera) to the color space > of your output device (display, printer). A gamma value (or factor) > can be used to create a gamma table. > > Search for "gamma table" and "gamma factor" at google and you'll find > lots of documentation. > There is a link in the SANE-FAQ to the colorspace FAQ. If you want to know more about gamma, look at Carles Poynton's FAQs on color and gamma. >>and "bayer" Bayer is a dithering algoritm; it uses fixed paterns. For an example of the 4x4 patterns see: http://tiger.technion.ac.il/~cgcourse/lectures/4-intensity/sld007.htm > <..> -- (c) ljm @ xs4all . nl. No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author. From psfales@lucent.com Thu Jun 12 15:27:48 2003 From: psfales@lucent.com (Peter Fales) Date: Thu, 12 Jun 2003 09:27:48 -0500 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <20030612082814.GB10868@meier-geinitz.de> References: <18Qp5L-1j8CMCC@fmrl02.sul.t-online.com> <20030612082814.GB10868@meier-geinitz.de> Message-ID: <20030612142748.GA18318@lucent.com> On Thu, Jun 12, 2003 at 10:28:14AM +0200, Henning Meier-Geinitz wrote: > Maybe your data is also compressed? Or it's transferred as a jpeg? For a toy camera like this, it's most likely the raw output of the CCD device and needs a fair amount of processing of the raw pixel data. The dc25 backend shows an example of this kind of processing. (It's not likely that you'll be able to use that kind - just an example of that type of processing.) My guess is that the most effective technique would be to open up the camera and try to identify the manufacturer of the CCD. Then see if you can get anything from them. I think that's how the dc-25 algorithms were originally developed (not by me!) -- Pete Fales From kilgota@banach.math.auburn.edu Thu Jun 12 16:58:39 2003 From: kilgota@banach.math.auburn.edu (Theodore Kilgore) Date: Thu, 12 Jun 2003 10:58:39 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <20030612082814.GB10868@meier-geinitz.de> Message-ID: Henning, Well, it seems that my inquiry got some interest, for which I thank everyone who responded. I will try to follow down some of the leads, after writing the Calculus III test I have to give tomorrow. Meanwhile, a couple more comments/questions/responses: On Thu, 12 Jun 2003, Henning Meier-Geinitz wrote: > On Wed, Jun 11, 2003 at 07:51:40PM -0500, Theodore Kilgore wrote: > > What are "gamma" > Matter of fact, I did do soem searching about "gamma" and I did come up with an impression, at least: It seems to be a correction for non-linearity of gain in the hardware (i.e. hardware does not respond in linear fashion to a certain kind of stimulus, so we do something to fix that). > > > and "bayer" > (cut) > > I don't really understand what you mean by "whitespace". > What I meant by "whitespace" is the blank spots between bytes in a file. For example, bc 3f and what is between the c and the 3 I am calling "whitespace." > Interpolation is usually used to create resolutions higher than > supported by hardware. It's just a marketing gag, you don't get better > images, just bigger ones. Maybe so, but: The raw downloaded data for one 352x288 picture is exactly 352x128=101376 bytes. If you put this directly into a file, you get a file of exactly 101376 bytes. If you stick a ppm header on it you have a file with a ppm header on it, and you get an error message if you try to view it. However, if you take the log data output containing the same 101376 bytes, then you have the bytes represented in the form of text as two characters each, with a space between each two successive bytes. So when you remove all material from the log file except the actual data downloaded for a picture you have 101376 bytes of data, which now get saved as a file. The actual size of the file thus created is 3x101376 = 304128 bytes, which presumably happens because now each byte is represented by two characters (requiring one byte each) plus one empty space (the third byte). Addition of a ppm header to the edited log output then creates a .ppm file of size 304143 bytes, which is then a viewable picture. Just not a very good one. Addition of a bmp header instead of a ppm header produces ( after adjustment by, for example, removing the last byte of empty space) a file of size 304182 bytes, which is the size identical to the file size produced by the Windows driver software. Again, it is a viewable picture, which looks the same as the ppm file but with some colors switched seems that ppm and bmp handle endian-ness differently; the colors come out closer to right in the ppm version). Whether the bmp file is viewed with the Windows software or with Linux software is also immaterial. Also it does not matter whether the bytes from the log file were downloaded with the stock driver or with my own programming. I have checked this. > Example: (Example was clear, thanks) > > The scanners return image data in lots of differnt formats. E.g. 8, > 10, 12, 16 bits/color, all the pixels of one color after each other, > or all the colors of one pixel after each other and so on. > If I am not mistaken, this is 8-bit color, since I recall somewhere seeing that the camera gives 256 colors. Also this would fundamentally make sense to me because the actual data gives exactly one pixel per byte. So I guess a natural question might be, that how many "standard" ways are there by which 8-bit color at one pixel can be represented by one byte? And as to this particular instance, I suspect the order RGB is the one being used, not GRB or GBR or such. > Maybe your data is also compressed? Possibly, but the way it is compressed it is exactly 1/3 the size and it is also possible to get a picture resembling the original out of the log output, so my instincts would be against this. Of course, I have been wrong on occasions. > Or it's transferred as a jpeg? > I really don't expect this. The camera is really an el cheapo. If I told you how it downloads data you would probably not believe me. Thomas, my 13-year-old, says it is "brain dead." So I don't think it knows how to pronounce "jpeg." Besides, exactly one byte per pixel ??? Thanks for the help. Ted Kilgore From kilgota@banach.math.auburn.edu Thu Jun 12 17:14:27 2003 From: kilgota@banach.math.auburn.edu (Theodore Kilgore) Date: Thu, 12 Jun 2003 11:14:27 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <20030612142748.GA18318@lucent.com> Message-ID: On Thu, 12 Jun 2003, Peter Fales wrote: > > Maybe your data is also compressed? Or it's transferred as a jpeg? > > For a toy camera like this, it's most likely the raw output of the CCD > device and needs a fair amount of processing of the raw pixel data. Actually, I suspect it is a CMOS chip. The camera really is cheap. > The > dc25 backend shows an example of this kind of processing. (It's not likely > that you'll be able to use that kind - just an example of that type of > processing.) > > My guess is that the most effective technique would be to open up the camera > and try to identify the manufacturer of the CCD. And how would I do that identification if there is nothing written on said chip? Since I have already destroyed one of these things trying to look inside, I would be glad to look in it again (can't kill it twice, after all) if it would really help. And anyway the USB vendor:product number is 0x2770:0x9120, which tells us that the chip is from SQ Technologies ( website at www.sq.com.tw ) and they do claim to make video capture chips. They make an SQ905 and an SQ913 in particular. I suspect the one in this camera is the SQ905 (there is no 912) They have publicly available "data sheets" which are nothing but glossy sales brochures. Then see if you can get > anything from them. Good idea. They don't answer my e-mail. I think that's how the dc-25 algorithms were > originally developed (not by me!) > Hmmm. I will have a look. Thanks. Ted Kilgore From el_profesorfr@yahoo.fr Thu Jun 12 19:02:21 2003 From: el_profesorfr@yahoo.fr (=?iso-8859-1?q?Thomas=20VIAL?=) Date: Thu, 12 Jun 2003 20:02:21 +0200 (CEST) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: Message-ID: <20030612180221.21667.qmail@web12602.mail.yahoo.com> Hi, > What I meant by "whitespace" is the blank spots > between bytes in a file. > For example, > > bc 3f > > and what is between the c and the 3 I am calling > "whitespace." Er, "bc" and "3f" are just two distinct bytes in hexadecimal, 188 and 63 respectively. It seems you are interpreting the hex dump as raw data... One byte is 2 hex digit, and the whitespace is here for readability. Once correctly interpreted as a sequence of hex bytes, my guess is that the log data is strictly equivalent to the raw data, since the final number of bytes is the same. With a correct bmp header the raw data should be ok (maybe upside down). But with 1 byte per pixel the image should be interpreted as greyscale I think -- unless it uses a palette? Thomas ===== ------------------------------ Si vos aist Diex ! http://www.el-profesor.net/ ------------------------------ ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en franēais ! Yahoo! Mail : http://fr.mail.yahoo.com From psfales@lucent.com Thu Jun 12 19:38:06 2003 From: psfales@lucent.com (Peter Fales) Date: Thu, 12 Jun 2003 13:38:06 -0500 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: <20030612142748.GA18318@lucent.com> Message-ID: <20030612183806.GC28599@lucent.com> On Thu, Jun 12, 2003 at 11:14:27AM -0500, Theodore Kilgore wrote: > And anyway the USB vendor:product number is 0x2770:0x9120, which tells us > that the chip is from SQ Technologies ( website at www.sq.com.tw ) and > they do claim to make video capture chips. They make an SQ905 and an SQ913 > in particular. I suspect the one in this camera is the SQ905 (there is no > 912) They have publicly available "data sheets" which are nothing but > glossy sales brochures. The second page of the SQ905 data sheet implies that the sensor is actually not part of the SQ905, but is separate component. Do you think that is the case? -- Pete Fales From psfales@lucent.com Thu Jun 12 19:54:56 2003 From: psfales@lucent.com (Peter Fales) Date: Thu, 12 Jun 2003 13:54:56 -0500 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: <20030612142748.GA18318@lucent.com> Message-ID: <20030612185456.GA10604@lucent.com> Try taking a picture of solid red, green, and blue images. (As close to pure saturated colors as you can get). How does that affect the resulting data? -- Peter Fales Lucent Technologies, Room 1C-436 N9IYJ 2000 N Naperville Rd PO Box 3033 internet: psfales@lucent.com Naperville, IL 60566-7033 work: (630) 979-8031 On Thu, Jun 12, 2003 at 11:14:27AM -0500, Theodore Kilgore wrote: > > > On Thu, 12 Jun 2003, Peter Fales wrote: > > > > Maybe your data is also compressed? Or it's transferred as a jpeg? > > > > For a toy camera like this, it's most likely the raw output of the CCD > > device and needs a fair amount of processing of the raw pixel data. > > Actually, I suspect it is a CMOS chip. The camera really is cheap. > > > The > > dc25 backend shows an example of this kind of processing. (It's not likely > > that you'll be able to use that kind - just an example of that type of > > processing.) > > > > My guess is that the most effective technique would be to open up the camera > > and try to identify the manufacturer of the CCD. > > And how would I do that identification if there is nothing written on > said chip? Since I have already destroyed one of these things trying to > look inside, I would be glad to look in it again (can't kill it twice, > after all) if it would really help. > > And anyway the USB vendor:product number is 0x2770:0x9120, which tells us > that the chip is from SQ Technologies ( website at www.sq.com.tw ) and > they do claim to make video capture chips. They make an SQ905 and an SQ913 > in particular. I suspect the one in this camera is the SQ905 (there is no > 912) They have publicly available "data sheets" which are nothing but > glossy sales brochures. > > Then see if you can get > > anything from them. > > Good idea. They don't answer my e-mail. > > > I think that's how the dc-25 algorithms were > > originally developed (not by me!) > > > Hmmm. I will have a look. > > Thanks. > > Ted Kilgore > > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From kilgota@banach.math.auburn.edu Thu Jun 12 18:55:51 2003 From: kilgota@banach.math.auburn.edu (Theodore Kilgore) Date: Thu, 12 Jun 2003 12:55:51 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <20030612180221.21667.qmail@web12602.mail.yahoo.com> Message-ID: On Thu, 12 Jun 2003, [iso-8859-1] Thomas VIAL wrote: > Hi, > > > > What I meant by "whitespace" is the blank spots > > between bytes in a file. > > For example, > > > > bc 3f > > > > and what is between the c and the 3 I am calling > > "whitespace." > > Er, "bc" and "3f" are just two distinct bytes in > hexadecimal, 188 and 63 respectively. Yes. I know that. > It seems you are > interpreting the hex dump as raw data... > One byte is 2 hex digit, and the whitespace is here > for readability. > Again, yes. My point was that a string of bytes equal in number to the number of pixels in the picture will give precisely no good result, but that on the other hand putting the text fomat of same data, obtained by suitable editing of the log file, will give a picture provided one only puts a ppm header on the top. In other words, if you read (for example) bc as one byte, and not as three bytes (one for b, one for c, and one for the space after it, and so on through the rest of the file) you do get a file but it is not a picture, but if you do it the second way (stupid as that may look) you do get a picture. > Once correctly interpreted as a sequence of hex bytes, > my guess is that the log data is strictly equivalent > to the raw data, since the final number of bytes is > the same. > No it isn't. The "final number of bytes" in the text file is equal to the number of bytes dumped, times exactly three. And it is the text file with appropriate header which gives a picture. > With a correct bmp header the raw data should be ok > (maybe upside down). Well, actually, it is more complicated. The ppm format only turns the picture upside down, but leaves the colors approximately correct. The bmp format gives you the picture right-side up, mirror-imaged left to right, and seems to reverse red and blue or red and green. > But with 1 byte per pixel the image should be > interpreted as greyscale I think This is not what happens. I judge by the results. > -- unless it uses a > palette? Well, I did not introduce any palette. So if it is using one it is built-in in ImageMagick, GIMP, and in the Windows software, all three. I just dumped the log data into a file, stuck a header on it, and viewed it. Looking at things positively, I did get the data out of the camera by hook or by crook, and nobody told me how to do it. This is fun, isn't it? After all, I am only doing this because the problem is there to solve, and the camera seemed simple enough for a beginner in device support like me, that I could fool with it and learn something. after all, unlike a scanner it has no moving parts. Ted Kilgore From david@rondotheatre.co.uk Thu Jun 12 20:00:02 2003 From: david@rondotheatre.co.uk (david stevenson) Date: Thu, 12 Jun 2003 20:00:02 +0100 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: Message-ID: <200306121959.25287.david@rondotheatre.co.uk> On Thursday 12 June 2003 6:55 pm, Theodore Kilgore wrote: > On Thu, 12 Jun 2003, [iso-8859-1] Thomas VIAL wrote: > > Hi, > Again, yes. My point was that a string of bytes equal in number to the > number of pixels in the picture will give precisely no good result, but > that on the other hand putting the text fomat of same data, obtained by > suitable editing of the log file, will give a picture provided one only > puts a ppm header on the top. In other words, if you read (for example) bc > as one byte, and not as three bytes (one for b, one for c, and one for the > space after it, and so on through the rest of the file) you do get a file > but it is not a picture, but if you do it the second way (stupid as that > may look) you do get a picture. > An interesting way to process data, but if it works....... In converting a byte to hex it is effectivly split into 2 nibbles of 4bits and a fixed value of 0x30 added to each. (or 0x37 if the nibble value is more than 9) So using the ascii file as data should be twice the size (having ignored the spaces). The question then is what headers have you added to make the bitmap. Most headers include information on bits per pixel, pixels per line ... David From mouse@Rodents.Montreal.QC.CA Thu Jun 12 21:22:35 2003 From: mouse@Rodents.Montreal.QC.CA (der Mouse) Date: Thu, 12 Jun 2003 16:22:35 -0400 (EDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: Message-ID: <200306122033.QAA27264@Sparkle.Rodents.Montreal.QC.CA> >> It seems you are interpreting the hex dump as raw data... >> One byte is 2 hex digit, and the whitespace is here for readability. > Again, yes. My point was that a string of bytes equal in number to > the number of pixels in the picture will give precisely no good > result, but that on the other hand putting the text fomat of same > data, obtained by suitable editing of the log file, will give a > picture provided one only puts a ppm header on the top. Your previous description made no sense to me. While reading this, I had a brainflash, and I think I know what's going on. When you have one byte per pixel, you _do_ have a picture, it's just that it's a colourmapped picture, and you don't have the colourmap to go with it, so it makes no sense. Prepend a pgm (not ppm) header and it will be displayable, but it will make little sense - it may or may not be possible to see the original image in it; this amounts to using a gray-ramp colourmap instead of the colourmap the image should have. When you expand it to three bytes per pixel and prepend a ppm header, ppm takes those three bytes as the red, green, and blue bytes for that pixel, so you get one ppm pixel per picture pixel and you get something. This amounts to imposing a different colourmap, one that looks like index red green blue 0 48 48 32 ("00 ") 1 48 49 32 ("01 ") ... 185 98 57 32 ("b9 ") ... 255 102 102 32 ("ff ") which is why the picture looks as though its colours have been scrambled: they have been! Some of pixels may effectively use colourmap entries with 10 instead of 32 for the blue value, if you use newlines instead of spaces for some of the inter-byte spacing. >> But with 1 byte per pixel the image should be interpreted as >> greyscale I think > This is not what happens. I judge by the results. If you prepend a ppm header, no, it will perforce be taken as colour. But if you use a pgm header, it will be taken as grayscale and you should get something semi-sensible. (I don't know enough about bmp to comment on the results you get with bmp headers.) There unfortunately is no format in the pbm/pgm/ppm series that handles colourmapped images, as far as I know. To get sensible pictures in p*m format, you'll need to figure out what the colourmap the camera is assuming the image will be used with is. You may be able to do this by taking pictures of washes of each primary, from black to full brightness, and watching how the byte values change.... /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse@rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B From karsten.festag@gmx.de Thu Jun 12 22:19:32 2003 From: karsten.festag@gmx.de (Karsten Festag) Date: Thu, 12 Jun 2003 23:19:32 +0200 Subject: [sane-devel] Microtek SlimScan C3, output always a black image Message-ID: <200306122319.32379.karsten.festag@gmx.de> Hi Jose, ok, I think I found and solved the problem. I put the changed code on my homepage www.karstenfestag.gmxhome.de, it's the latest version. You will have to remove the SUSE packages and compile SANE from the sources if you want to use that. But I think you can try to exchange only the library file so you don't have to uninstall the SUSE package and compile SANE by yourself: for this you have to find the file 'libsane-microtek2.so.1.0.9'; I think it is in /usr/lib/sane or /usr/local/lib/sane. This file is linked to libsane-microtek2.so.1 and libsane-microtek2.so Please remove the links (all these things are to be done as root) and replace the libsane-microtek2.so.1.0.9 file with the one I attached to this mail (don't forget to unpack (bunzip) the attached file :-) ) The re-create the links: ln libsane-microtek2.so.1.0.9 libsane-microtek2.so.1 ln libsane-microtek2.so.1.0.9 libsane-microtek2.so ( of course to be typed in the directory where the libsane-microtek2.so.1.0.9 file is) Have luck! Karsten [ this is a copied mail for the list without attachment ] From a.deuring@satzbau-gmbh.de Thu Jun 12 23:47:24 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Fri, 13 Jun 2003 00:47:24 +0200 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: Message-ID: <3EE902FC.4030903@gmx.net> Theodore Kilgore wrote: > Matter of fact, I did do soem searching about "gamma" and I did come up > with an impression, at least: It seems to be a correction for > non-linearity of gain in the hardware (i.e. hardware does not respond in > linear fashion to a certain kind of stimulus, so we do something to fix > that). Right, that's probably the most common description. Often an arbitrary table or function is used for gamma correction, sometimes a function like out = pow(in, x) is called "gamme correction" and x is called the "gamma value". Occasionally, one can find 1/x being called the gamma value. > The raw downloaded data for one 352x288 picture is exactly 352x128=101376 > bytes. If you put this directly into a file, you get a file of exactly > 101376 bytes. If you stick a ppm header on it you have a file with a ppm > header on it, and you get an error message if you try to view it. For a PPM file of 352x288 pxiels you'll need 352x288x3 bytes. (1 byte for red, one for green, one for blue) > If I am not mistaken, this is 8-bit color, since I recall somewhere seeing > that the camera gives 256 colors. Also this would fundamentally make sense > to me because the actual data gives exactly one pixel per byte. So I > guess a natural question might be, that how many "standard" ways are there > by which 8-bit color at one pixel can be represented by one byte? As far as i know, most if not all CCD sensors have a color filter in front of each sensor element, so that one element "sees" only red light, and another one only green or blue light. A camera with better firmware will build some interpolated values for the "missing colors" of a pixel, or the data from three sensor elements may be merged into one pixle value. I would that your camera simply delivers the raw data. > > > And as to this particular instance, I suspect the order RGB is the one > being used, not GRB or GBR or such. Peter already mentioned that the best way to get a clue about the color representation within the scan data is to make photos of pure red/green/blue areas. This should show data with repeate sequences of two bytes with smaller values and one byte with a larger value, if my guess is right. And if data for all colors is stored in one byte, you'll also quickly get a clue, which bits represents which colors. But I wold bet a few virtual beers that the camera delivers one color channel per byte. Abel From joseos@okstate.edu Fri Jun 13 02:23:22 2003 From: joseos@okstate.edu (Jose Sanchez) Date: Thu, 12 Jun 2003 18:23:22 -0700 Subject: [sane-devel] Microtek SlimScan C3, output always a black image In-Reply-To: <200306122319.32379.karsten.festag@gmx.de> References: <200306122319.32379.karsten.festag@gmx.de> Message-ID: <3EE9278A.7070808@okstate.edu> Hi Karsten, thanks for the help and the time you have put in this. I have only a question, the thing is that I my SUSE distribution I have libsane-microtek2.so.1.0.11 instead of the libsane-microtek2.so.1.0.9. I tried replacing it but the scanner program doesn't even start. So, I made the following: I uninstall the sane package that came with SUSE and I downloaded one from the sane webpage 1.0.12 (I think is the last one). Can I replace the .c and .h with the one that you posted in your web page with this distribution of sane or should I download an older distribution. If so I will continue and see what happends. Thanks Jose Karsten Festag wrote: >Hi Jose, > >ok, I think I found and solved the problem. I put the changed code on my >homepage www.karstenfestag.gmxhome.de, it's the latest version. You will have >to remove the SUSE packages and compile SANE from the sources if you want to >use that. >But I think you can try to exchange only the library file so you don't have to >uninstall the SUSE package and compile SANE by yourself: for this you have to >find the file 'libsane-microtek2.so.1.0.9'; I think it is in /usr/lib/sane or >/usr/local/lib/sane. This file is linked to libsane-microtek2.so.1 and >libsane-microtek2.so > >Please remove the links (all these things are to be done as root) and replace >the libsane-microtek2.so.1.0.9 file with the one I attached to this mail >(don't forget to unpack (bunzip) the attached file :-) ) >The re-create the links: >ln libsane-microtek2.so.1.0.9 libsane-microtek2.so.1 >ln libsane-microtek2.so.1.0.9 libsane-microtek2.so > >( of course to be typed in the directory where the libsane-microtek2.so.1.0.9 >file is) > >Have luck! > >Karsten > >[ this is a copied mail for the list without attachment ] >_______________________________________________ >Sane-devel mailing list >Sane-devel@www.mostang.com >http://www.mostang.com/mailman/listinfo/sane-devel > > From gene.heskett@verizon.net Fri Jun 13 01:37:09 2003 From: gene.heskett@verizon.net (Gene Heskett) Date: Thu, 12 Jun 2003 20:37:09 -0400 Subject: [sane-devel] Logitech ClickSmart 310 help needed. Message-ID: <200306122037.09571.gene.heskett@verizon.net> Hi all; 2 areas in fact. The camera driver, qcamvc-1.0.5 does if I put the verndor/product numbers in its source code, seem to almost connect with this camera. I'm doing this to the source of the patch that gets installed on new kernels so I don't have to repatch the kernel by hand everytime. Anyway, by changing the line in /etc/modules.conf that used to say "alias char-major-81 bttv" so it now says alias char-major-81 videodev, I have lost all my bttv stuffs (I have a Haupauge bt848 based WinTV-Go+FM card too) I can apparently access it with both xsane and gqcam. The symptoms are (for both programs) a small (2.5x2.5 inches on my 1600x1200 screen) picture that looks as if the data has been scrambled in some sort of a geometric scramble pattern. I'd post it, but its about 220K. Suggestions anyone? I'm all ears (amd probably thumbs too :) -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved. From joseos@okstate.edu Fri Jun 13 08:24:50 2003 From: joseos@okstate.edu (Jose Sanchez) Date: Fri, 13 Jun 2003 00:24:50 -0700 Subject: [sane-devel] Microtek SlimScan C3, output always a black image In-Reply-To: <200306122319.32379.karsten.festag@gmx.de> References: <200306122319.32379.karsten.festag@gmx.de> Message-ID: <3EE97C42.60705@okstate.edu> Hi Karsten, Thanks a lot, I downloaded the sources files from suse change the files you told me, reinstall everything and it worked out. However, the image is with some vertical lines I don't know why but it doesn't output that annoying black image. Thanks for your time and I really appreciate your work. Sincerely, Jose Karsten Festag wrote: >Hi Jose, > >ok, I think I found and solved the problem. I put the changed code on my >homepage www.karstenfestag.gmxhome.de, it's the latest version. You will have >to remove the SUSE packages and compile SANE from the sources if you want to >use that. >But I think you can try to exchange only the library file so you don't have to >uninstall the SUSE package and compile SANE by yourself: for this you have to >find the file 'libsane-microtek2.so.1.0.9'; I think it is in /usr/lib/sane or >/usr/local/lib/sane. This file is linked to libsane-microtek2.so.1 and >libsane-microtek2.so > >Please remove the links (all these things are to be done as root) and replace >the libsane-microtek2.so.1.0.9 file with the one I attached to this mail >(don't forget to unpack (bunzip) the attached file :-) ) >The re-create the links: >ln libsane-microtek2.so.1.0.9 libsane-microtek2.so.1 >ln libsane-microtek2.so.1.0.9 libsane-microtek2.so > >( of course to be typed in the directory where the libsane-microtek2.so.1.0.9 >file is) > >Have luck! > >Karsten > >[ this is a copied mail for the list without attachment ] >_______________________________________________ >Sane-devel mailing list >Sane-devel@www.mostang.com >http://www.mostang.com/mailman/listinfo/sane-devel > > From stauff@guarana.org Fri Jun 13 08:07:51 2003 From: stauff@guarana.org (Matthew Duggan) Date: Fri, 13 Jun 2003 17:07:51 +1000 Subject: [sane-devel] Query In-Reply-To: References: Message-ID: <1055488071.3ee97847c0c8f@cheesypoof.guarana.org> Quoting Homer : > Hi, > I know it's a really silly question but I'd thought I'd ask it anyway. I'm > using mandrake 9.1 and the Xsane package will detect and setup my canon > N640P. It will run as root but not as my normal user. I've actually scanned > from root but the scanner won't detect from user. ... Hi, Henning's answer was half right :) This is actually a parallel scanner, but the fix is still permissions. I assume Mandrake 9.1 is a 2.4 distro with ppdev enabled so I'll assume you have /dev/parport*. Check the permissions on /dev/parport*.. they will probably look something like this. [stauff@cheesypoof stauff]$ ls -l /dev/parport* crw-rw---- 1 root lp 99, 0 Jun 15 2002 /dev/parport0 crw-rw---- 1 root lp 99, 1 Jun 15 2002 /dev/parport1 If I remember rightly mdk9 uses devfs so it actually won't look exactly like this.. they may be symlinks to somewhere else in /dev (in which case you should check the permissions on the targets) They will likely be owned by the "lp" group (as these ones are), so for the quick fix you can just do: adduser my_username lp Then log out and log back in, and you should be able to scan as non-root. You should add all the users you want to be able to scan to this group. Cheers, - Matthew Duggan ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ From priya" This is a multi-part message in MIME format. ------=_NextPart_000_0024_01C331AB.BC91DB70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all ! I have an interface for scanner on TWAIN protocol for windows. Now i = need to port it on the LINUX.=20 There are 2 solutions that either to work on TWAIN on sane bridge or to = rewrite my interface according to sane. Can anybody suggest what would be more beneficial ??? Regards, Priya Gupta ------=_NextPart_000_0024_01C331AB.BC91DB70 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
Hi all !
 
I have an interface for scanner on = TWAIN protocol=20 for windows.  Now i need to port it on the LINUX.
 
There are 2 solutions that either to = work on TWAIN=20 on sane bridge or to rewrite my interface according to = sane.
 
Can anybody suggest what would be more = beneficial=20 ???
 
 
Regards,
Priya=20 Gupta
------=_NextPart_000_0024_01C331AB.BC91DB70-- From ope557@yahoo.com Fri Jun 13 08:33:44 2003 From: ope557@yahoo.com (ope) Date: Fri, 13 Jun 2003 00:33:44 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness Message-ID: <20030613073344.999.qmail@web20608.mail.yahoo.com> I have an UMAX Astra 2200 scanner that I connecting to through USB. My problem is basically this: When I use xsane I can preview as many times as I want without any problems. However, once I actually try to scan I sometimes have success and sometimes don't. When I can't successfully scan what happens is that the scanner runs, the lamp moves completely down and back again, the 'REceiving RGB Data' progress bar is just about complete and then xsane completely freezes. Sometimes if I just leave it for 5-10 minutes the scanned image eventually pops up other times I can leave it for more than an hour and the application is still frozen. Here is what I see in messages: kernel: hub.c: USB new device connect on bus2/2, assigned device number 7 kernel: usb.c: USB device 7 (vend/prod 0x1606/0x230) is not claimed by any active driver. kernel: usb.c: registered new driver usbscanner kernel: scanner.c: 0.4.6:USB Scanner Driver kernel: usb_control/bulk_msg: timeout last message repeated 2 times last message repeated 3 times ... kernel: scanner.c: read_scanner(0): excessive NAK's received sane-find-scanner shows: found USB scanner (vendor=0x1606, product=0x0230) at /dev/usb/scanner0 __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com From aneeshmraj@hotmail.com Fri Jun 13 10:29:38 2003 From: aneeshmraj@hotmail.com (aneesh m raj) Date: Fri, 13 Jun 2003 14:59:38 +0530 Subject: [sane-devel] problem with UMAX 2000P printer Message-ID: This is a multi-part message in MIME format. ------=_NextPart_000_006E_01C331BC.69618FC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi , Im using a UMAX 2000P parallel port printer and I have downloaded SANE = and the patch for UMAX, when I run the umax_pp tool I receive a message = "No scanner found Status 134 not expected" .Im using debian linux kernel = 2.2.20. Any help is appreciated. Regards Aneesh ------=_NextPart_000_006E_01C331BC.69618FC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi ,
Im using a UMAX 2000P parallel port = printer=20 and I have downloaded SANE and the patch for UMAX, when I run the = umax_pp=20 tool I receive a message "No scanner found Status 134 not expected" .Im = using=20 debian linux kernel 2.2.20. Any help is appreciated.
Regards
Aneesh
------=_NextPart_000_006E_01C331BC.69618FC0-- From henning@meier-geinitz.de Fri Jun 13 10:50:16 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 11:50:16 +0200 Subject: [sane-devel] problem with UMAX 2000P printer In-Reply-To: References: Message-ID: <20030613095016.GB3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 02:59:38PM +0530, aneesh m raj wrote: > Im using a UMAX 2000P parallel port printer A printer? The "S" in SANE means "scanner" :-) Or is this a multi-function-device? > and I have downloaded > SANE and the patch for UMAX, when I run the umax_pp tool I receive a > message "No scanner found Status 134 not expected" .Im using debian > linux kernel 2.2.20. Any help is appreciated. Have you checked the manual page (sane-umax_pp)? Maybe it's a problem with the wrong parallel port mode ("EPP MODE ONLY"). Bye, Henning From henning@meier-geinitz.de Fri Jun 13 11:14:24 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 12:14:24 +0200 Subject: [sane-devel] Avision backend trouble (?) (was: multiple images on XSane) In-Reply-To: <000601c32e4a$6e9dd180$a8ec403e@default> References: <20030601132533.21859.53611.Mailman@panda.mostang.com> <000601c32e4a$6e9dd180$a8ec403e@default> Message-ID: <20030613101424.GC3579@meier-geinitz.de> Hi, On Mon, Jun 09, 2003 at 06:42:08AM +0100, F J Brooks wrote: > On Sat, 31 May 2003 09:15:11 +0200, Henning Meier-Geinitz > > wrote: > > So an older version of xsane works? The current version is 0.91, by > > the way. > > Is there any advantage to me in installing xsane 0.91, eg, will it solve my > current problems? I installed v.0.90 only two or three weeks ago (when it > was then the latest). I don't think so but I haven't seen your problem with any of my scanners so I can't be sure. I was more interested in the first part of the question, however :-) My questions try to find out if it's a frontend (xsane) or backend problem. As you say quiteinsane works, that would point to a frontend problem. However, the description of the bug looks more like a backend problem. Further more, there are no other reports of such a bug as far as I know so I don't really know what's going on. > > Which version of sane-backends do you use? > > The version of sane-backends (and sane-frontends) I have is 1.0.11. 1.0.12 is current but I don't know if that fixes your problem. > > Does it depend on resolution or mode setting? Only in viewer mode or > > also in the preview window and when you save the image? > > It doesn't depend on mode, in that I get the same result in the viewer > window, With "mode" I meant color, gray or lineart. > when I copy/print, and if I save the image to file and then print. Is the image already corrupted when displayed on the screen or is only the print wrong? > The preview window doesn't seem to work in that it shows a dark, hatched > strip about 3 cm wide across the top of the window, with the rest of the > window area (A4) white. That's a bad sign. Maybe really a backend problem because it doesn't happen with any of my backends and XSane. But the scanner does scan (move the scan slider) when you press the "Acquire preview" button? > > Different speed are rather uncommon when using different frontends. Are > > you sure that you have only one version of sane-backends installed? > > No, I found that I also had sane-backends-1.0.8 [the original which came > with my SuSE distribution]. So I removed it (using YaST2). That's when > things got even worse! > > I found that, when I clicked on my desktop scanner icon to open > /usr/local/bin/xsane, I got the error message: > > 'Sorry - KDesktop: KDEInit could not launch '/usr/local/bin/xsane'. Probably that xsane version was linked against your 1.0.8 SANE backends. That would explain why quiteinsane worked. Just rebuild xsane from source again. Now that you have only one version of sane-backends, it should find that one and link against it. In fact I'm a bit surprised that it doesn't work out-of-the-box. > When I tried the same thing using Konqueror, I got the error message: > > 'Error - Konqueror: Unable to run the command specified. The file or > directory file: /usr/local/bin/xsane does not exist.' Well, this message is pretty much clear :-) > I found this rather surprising so I tried: > > fredjb@FJBrooks:~> ls -l /usr/local/bin > drwxr-xr-x 7 root root 816 2003-06-05 17:00 sane-frontends-1.0.11 that's odd. You shouldn't place the source directory of sane-frontends in the directory for binaries. Better use /usr/src or your home directory. > drwxr-xr-x 9 root root 1344 2003-06-05 16:56 xsane-0.90 Same here. > [Many of these were recently downloaded from their source sites on the net, > to > replace older, out-of-date versions.] Yeah, but you did build them from source, did you? And not just unpacked them in /usr/local/bin? xsane (the binary) is just nor there. I don't think that yast removed it. > fredjb@FJBrooks:~> sane-find-scanner > > found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/scanner > found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/sg2 Ok. > > Followed by: > > fredjb@FJBrooks:~> scanimage -L > device `avision:/dev/scanner' is a Hewlett-Packard ScanJet 5300C flatbed > scanner > device `avision:/dev/sg2' is a Hewlett-Packard ScanJet 5300C flatbed > scanner > fredjb@FJBrooks:~> Also ok. > I then tried [I have extracted only the bits I thought relevant to my > scanner]: > > SANE_DEBUG_DLL=255 scanimage -L > [sanei_debug] Setting debug level of dll to 255. > [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends > 1.0.11 Ok, that's the new backend. > > What happens if you scan with scanimage? E.g. "scanimage >image.pnm". > > Or xscanimage? > > Tried: fredjb@FJBrooks:~> scanimage >image.pnm > > Scanner whirred quietly for a while, but no other response. Well, is the image ok (image.pnm)? Display it with e.g. gimp, quiv or display. > Then tried: xscanimage: > > Got 'Select Device' panel giving choice: > 'avision:/dev/scanner > avision:/dev/sg2 > > Chose former, clicked 'OK', got: avision/dev/scanner window, on which > clicked: 'Preview Window'. Got Preview Window, dragged dashed line into > rectangle covering roughly A4 size, Are you sure you started at the top left edge? SOme backends don't like it if you get the coordinates the wrong way. > then clicked 'Acquire Preview'. > Scanner made fairly loud scratching-type noise plus hum, then > intermittent whirring noise. > Nothing appeared in Preview Window, and 'Acquire Preview' button > reappeared. Anyway, preview should always show the whole scanning area. So it looks like a backend problem. > Clicked 'Scan' on main window. After a minute or two, scanner started with > whirring noise, and got 'Scanning' panel with 'Receiving RGB data for > out.pnm' progress bar graphic. Also second panel headed: 'Output Filename', > listing directories and files. > > After ten-plus minutes, That's really slow. But it may be faster if you set a lower resolution. > scanning seems complete and 'Scanning' panel > disappears. Open out.pnm file and get colour image of object, slightly > distorted as is longer and thinner than original. Backend problem. But at least it scans at all. > So that's where I am, Henning - as you can see, in rather a mess. > Anything you can do to resolve the situation would be much > appreciated. My final thought is that there is a problem with the avision backend you use. The frontend shouldn't matter. I you install xsane again, it'll probably show the same symptoms. scanimage should also be the same. Try lower resolutions. Try sane-backends 1.0.12. If that doesn't help, ask the avision maintainer for help if you didn't do already (Rene Rebe ). Bye, Henning From stef-listes@wanadoo.fr Fri Jun 13 13:34:24 2003 From: stef-listes@wanadoo.fr (stef) Date: Fri, 13 Jun 2003 12:34:24 +0000 Subject: [sane-devel] problem with UMAX 2000P printer In-Reply-To: References: Message-ID: <20030613123424.GA911@wanadoo.fr> On Fri, Jun 13, 2003 at 02:59:38PM +0530, aneesh m raj wrote: > Hi , > Im using a UMAX 2000P parallel port printer and I have downloaded SANE and the patch for UMAX, when I run the umax_pp tool I receive a message "No scanner found Status 134 not expected" .Im using debian linux kernel 2.2.20. Any help is appreciated. > Regards > Aneesh Hello, could you please send the output of 'umax_pp -p -t 255' ? Also, check that the linux kernel detects your parallel port correctly. Especially, check that EPP mode is detected. Regards, Stef From henning@meier-geinitz.de Fri Jun 13 11:28:54 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 12:28:54 +0200 Subject: [sane-devel] TWAIN on SANE In-Reply-To: <002701c3317d$a62e48b0$5505a8c0@priya> References: <002701c3317d$a62e48b0$5505a8c0@priya> Message-ID: <20030613102854.GD3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 01:00:16PM +0530, priya wrote: > I have an interface for scanner on TWAIN protocol for windows. Now i > need to port it on the LINUX. What do you mean by interface? Some application or library that uses a scanner over the TWAIN interface? > There are 2 solutions that either to work on TWAIN on sane bridge or > to rewrite my interface according to sane. I don't know much about TWAIN but I guess it isn't too easy to write such a bridge on Linux beacuse of the link of twain to the widget libraries. Also SANE and TWAIN are different in that SANE describes the interface between driver and scan application while twain describes the interface between scan application and image manipulation tool. > Can anybody suggest what would be more beneficial ??? From the information you provide I guess using SANE directly makes more sense. But maybe you can provide some more details :-) There are solutions to bridge between TWAIN and SANE, but they are based on Windows: http://www.mostang.com/sane/sane-frontends.html (at the bottom). Bye, Henning From janez.dovc@ijs.si Fri Jun 13 12:36:16 2003 From: janez.dovc@ijs.si (Janez Dovc) Date: Fri, 13 Jun 2003 13:36:16 +0200 Subject: [sane-devel] HP ScanJet 5550C In-Reply-To: <20030613094540.GA3579@meier-geinitz.de> Message-ID: <007b01c331a0$03248800$b7e6f9c2@csl03> Hi, > Open the scanner's case. That may harm your warranty,=20 > however. Write down the inscriptions of the chips you find. OK, I will try to do that, but next time, I will be in office. > Does your scanner have an ADF (automatic document feeder)? Yes.=20 So, what do you suggest? Is the only solution, that I write the driver myself? How much time does it take, to write a driver for HP scanner. Is their interface somehow inteligent? Are other Scanjets totally = uncompatible? Janez From aneeshmraj@hotmail.com Fri Jun 13 12:46:18 2003 From: aneeshmraj@hotmail.com (aneesh m raj) Date: Fri, 13 Jun 2003 17:16:18 +0530 Subject: [sane-devel] problem with UMAX 2000P scanner References: Message-ID: This is a multi-part message in MIME format. ------=_NextPart_000_0086_01C331CF.80C1C640 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi , Thank u it worked the mode was in ECP+EPP . Im using a program to detect = scanner devices but I cant retrieve the device by calling = sane_get_devices() function .The=20 SANE_Device structure is NULL. %%%%%%%%%%%%scanner.h%%%%%%% #include #define SANE_MAX_USERNAME_LEN 128 #define SANE_MAX_PASSWORD_LEN 128 typedef void (*SANE_Authorization_Callback) (SANE_String_Const resource, SANE_Char username[SANE_MAX_USERNAME_LEN], SANE_Char password[SANE_MAX_PASSWORD_LEN]); SANE_Status initialize_scanner(SANE_Int* = version,SANE_Authorization_Callback callback); void exit_scanner(void); SANE_Status get_scanners(const SANE_Device*** device, SANE_Bool local); %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% //scanner.c #include #include "scanner.h" int main() { SANE_Status status=3D 0;=20 const SANE_Device** dev; int i =3D 0; status =3D initialize_scanner(NULL,NULL); if(status !=3D SANE_STATUS_GOOD) { printf("Scanner not properly initialized...\nExit code: %d\n",status); exit(0); } else {=20 status =3D get_scanners(&dev,1); if(status =3D=3D SANE_STATUS_GOOD) {=20 /* dev[i] is NULL */ while(dev[i] !=3D NULL) { printf("Name - %s\n", ((const = SANE_Device*)dev[i])->name); printf("Vendor - %s\n",((const = SANE_Device*)dev[i])->vendor); printf("Model - %s\n",((const = SANE_Device*)dev[i])->model); printf("Type - %s\n\n",((const = SANE_Device*)dev[i])->type); i++; } } =20 } exit_scanner(); =20 return 0; } SANE_Status initialize_scanner(SANE_Int* = version,SANE_Authorization_Callback callback) { return sane_init (version,callback); } void exit_scanner(void) { sane_exit(); } SANE_Status get_scanners(const SANE_Device*** device, SANE_Bool local) { =20 return sane_get_devices (device,local); } Thanks in advance Aneesh ----- Original Message -----=20 From: aneesh m raj=20 To: sane-devel@www.mostang.com=20 Sent: Friday, June 13, 2003 2:59 PM Subject: [sane-devel] problem with UMAX 2000P printer Hi , Im using a UMAX 2000P parallel port printer and I have downloaded SANE = and the patch for UMAX, when I run the umax_pp tool I receive a message = "No scanner found Status 134 not expected" .Im using debian linux kernel = 2.2.20. Any help is appreciated. Regards Aneesh ------=_NextPart_000_0086_01C331CF.80C1C640 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi ,
Thank u it worked the mode was in = ECP+EPP . Im=20 using a program to detect scanner devices but I cant retrieve the device = by=20 calling sane_get_devices() function .The
SANE_Device structure is = NULL.
 
 
%%%%%%%%%%%%scanner.h%%%%%%%

#include <sane/sane.h>
#define SANE_MAX_USERNAME_LEN=20 128
#define SANE_MAX_PASSWORD_LEN 128
typedef void=20 (*SANE_Authorization_Callback)
     =20 (SANE_String_Const resource,
       = SANE_Char=20 username[SANE_MAX_USERNAME_LEN],
       = SANE_Char password[SANE_MAX_PASSWORD_LEN]);
SANE_Status=20 initialize_scanner(SANE_Int* version,SANE_Authorization_Callback=20 callback);
void exit_scanner(void);
SANE_Status get_scanners(const = SANE_Device*** device, SANE_Bool local);
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
//scanner.c
 
#include <stdio.h>
#include=20 "scanner.h"
 
int main()
{
  SANE_Status = status=3D 0;=20
  const SANE_Device** dev;
  int i =3D 0;
  = status =3D=20 initialize_scanner(NULL,NULL);
  if(status !=3D=20 SANE_STATUS_GOOD)
  {
  printf("Scanner not = properly=20 initialized...\nExit code: = %d\n",status);
  exit(0);
 
  }
  else
  {=20
        status =3D=20 get_scanners(&dev,1);
       =20 if(status =3D=3D=20 SANE_STATUS_GOOD)
        &nbs= p;=20 { 
       =20     /*
       =20     dev[i] is NULL
       =20    =20 */
            = while(dev[i] !=3D NULL)
       =20         = {
      =20             printf("Name - = %s\n",=20 ((const SANE_Device*)dev[i])->name);
    =    =20             printf("Vendor = -=20 %s\n",((const SANE_Device*)dev[i])->vendor);
   =20             =    =20 printf("Model - %s\n",((const=20 SANE_Device*)dev[i])->model);
    =    =20             printf("Type -=20 %s\n\n",((const SANE_Device*)dev[i])->type);
   =20             =    =20 i++;
           =20    =20 }
           = }
 
        =20
  }
  = exit_scanner();  
  return 0;
}
 
SANE_Status = initialize_scanner(SANE_Int*=20 version,SANE_Authorization_Callback callback)
{
  return = sane_init=20 (version,callback);
 
}
 
void = exit_scanner(void)
{
 
  sane_exit();
 
}
 

SANE_Status get_scanners(const SANE_Device*** device, SANE_Bool = local)
{
 
  return  sane_get_devices=20 (device,local);
 
}
Thanks in advance
Aneesh
----- Original Message -----
From:=20 aneesh m=20 raj
Sent: Friday, June 13, 2003 = 2:59 PM
Subject: [sane-devel] problem = with UMAX=20 2000P printer

Hi ,
Im using a UMAX 2000P parallel port = printer=20 and I have downloaded SANE and the patch for UMAX, when I run the = umax_pp=20 tool I receive a message "No scanner found Status 134 not expected" = .Im using=20 debian linux kernel 2.2.20. Any help is appreciated.
Regards
Aneesh
------=_NextPart_000_0086_01C331CF.80C1C640-- From henning@meier-geinitz.de Fri Jun 13 13:55:48 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 14:55:48 +0200 Subject: [sane-devel] problem with UMAX 2000P scanner In-Reply-To: References: Message-ID: <20030613125548.GE3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 05:16:18PM +0530, aneesh m raj wrote: > Thank u it worked the mode was in ECP+EPP . Im using a program to > detect scanner devices but I cant retrieve the device by calling > sane_get_devices() function .The SANE_Device structure is NULL. Try "scanimage -L" to make sure it's not a bug in your program. First guess: "umax_pp" is commented out in dll.conf. Bye, Henning From henning@meier-geinitz.de Fri Jun 13 14:03:35 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 15:03:35 +0200 Subject: [sane-devel] HP ScanJet 5550C In-Reply-To: <007b01c331a0$03248800$b7e6f9c2@csl03> References: <20030613094540.GA3579@meier-geinitz.de> <007b01c331a0$03248800$b7e6f9c2@csl03> Message-ID: <20030613130335.GF3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 01:36:16PM +0200, Janez Dovc wrote: > So, what do you suggest? Is the only solution, that I write the driver > myself? I think so, yes. > How much time does it take, to write a driver for HP scanner. That depends on how intelligent it is. If it's rather low-level, it may take weeks to understand the basic protocol and to get it to scan. On the other hand I was able to get an image out of a rather high level Mustek scanner after about 10 hours of work. > Is their interface somehow inteligent? I have no idea. That's up to you to find out :-) Some info on how to do that is here: http://www.meier-geinitz.de/sane/misc/develop.html http://www.meier-geinitz.de/sane/misc/unsupported.html You can also try check-usb-scanner, it tries to detect the chipset of USB scanners. But I'd be surprised if it's an already known chip: http://www.meier-geinitz.de/sane/check-usb-scanner/ > Are other Scanjets totally uncompatible? I don't know until you find out about that :-) Have a look at the list of HP scanners and compare if the protocoll looks similar once you have found outhow it basically works: http://sane.informatik.uni-freiburg.de/cgi-bin/driver.pl?manu=hewlett-packard&model=&bus=usb If you are lucky it's compatible (or similar) to one of the already supported scanners. But I don't think so. Contacting HP for help may also make sense. I don't know however, if they are helpfull at all. Bye, Henning From kilgota@banach.math.auburn.edu Fri Jun 13 16:48:11 2003 From: kilgota@banach.math.auburn.edu (Theodore Kilgore) Date: Fri, 13 Jun 2003 10:48:11 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? Thanks to everyone! In-Reply-To: <20030612082814.GB10868@meier-geinitz.de> Message-ID: Henning, Thank you very much for the space on the sane-devel mailing list for a discussion about gamma correction and bayer interpolation/decoding. To everyone who has responded about the topic, I also want to say thanks, because I have gotten several useful suggestions out of it. At this point I need at least a weekend, probably more, to absorb all of the suggestions and to try them out in various ways, whether by incorporating them in code, or by running more experiments with the camera, taking pictures of "pure" red, green, blue, black, white, and so on. So, again, thanks. I may respond to some of you privately, too, but give me time. And probably Henning thinks that enough room and bandwidth have been already taken up. I do hope the discussion has benefitted those trying to deal with scanners as well as with cameras; otherwise I can only admire the altruism of the list maintainers! Theodore Kilgore From henning@meier-geinitz.de Fri Jun 13 19:13:51 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 20:13:51 +0200 Subject: [sane-devel] "gamma" and "bayer" ? Thanks to everyone! In-Reply-To: References: <20030612082814.GB10868@meier-geinitz.de> Message-ID: <20030613181351.GG3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 10:48:11AM -0500, Theodore Kilgore wrote: > So, again, thanks. I may respond to some of you privately, too, but give > me time. And probably Henning thinks that enough room and bandwidth have > been already taken up. I do hope the discussion has benefitted those > trying to deal with scanners as well as with cameras; otherwise I can only > admire the altruism of the list maintainers! Color space/gamma table questions are ontopic on this list. As you have seen I don't know much of this stuff myself and learned quite a bit. And to avoid any misconceptions: I'm neither the list maintainer nor the inventor of SANE but simply know about how SANE works in general a little bit :-) Bye, Henning From knan@mo.himolde.no Fri Jun 13 19:38:05 2003 From: knan@mo.himolde.no (=?ISO-8859-1?Q?Erik_Inge_Bols=F8?=) Date: Fri, 13 Jun 2003 20:38:05 +0200 (CEST) Subject: [sane-devel] "gamma" and "bayer" ? Thanks to everyone! In-Reply-To: <20030613181351.GG3579@meier-geinitz.de> References: <20030612082814.GB10868@meier-geinitz.de> <20030613181351.GG3579@meier-geinitz.de> Message-ID: On Fri, 13 Jun 2003, Henning Meier-Geinitz wrote: >And to avoid any misconceptions: I'm neither the list maintainer nor >the inventor of SANE but simply know about how SANE works in general a >little bit :-) And you announce releases and timetables, which just might lead to people perceiving you as "the boss" :) -- Erik I. Bolsų | email: The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. From TomF@sjpc.org Fri Jun 13 20:04:20 2003 From: TomF@sjpc.org (TomF) Date: Fri, 13 Jun 2003 12:04:20 -0700 Subject: [sane-devel] ADF support for HP7450C Message-ID: <20030613120420.610305e8.TomF@sjpc.org> I am using XSANE 0.89 on Redhat 9.0 with an HP 7450C scanner, with ADF that works on Windows XP when I dual boot. Setup/Enhancement/Automatic Document Feeder Modus has only the option None. I did not understand how to set SANE_NAME_SCAN_SOURCE from the messages I read in the archives. How do you do this? In February, Rene Rebe suggested using the CVS version with this scanner. Is this still necessary? I would rather use a Redhat rpm if one is available with this support. From klaus.dahlke@gmx.de Fri Jun 13 20:59:50 2003 From: klaus.dahlke@gmx.de (Klaus Dahlke) Date: Fri, 13 Jun 2003 21:59:50 +0200 Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030613073344.999.qmail@web20608.mail.yahoo.com> References: <20030613073344.999.qmail@web20608.mail.yahoo.com> Message-ID: <20030613215950.2a184f4a.klaus.dahlke@gmx.de> On Fri, 13 Jun 2003 00:33:44 -0700 (PDT) ope wrote: > I have an UMAX Astra 2200 scanner that I connecting to > through USB. My problem is basically this: > > When I use xsane I can preview as many times as I want > without any problems. However, once I actually try to > scan I sometimes have success and sometimes don't. > When I can't successfully scan what happens is that > the scanner runs, the lamp moves completely down and > back again, the 'REceiving RGB Data' progress bar is > just about complete and then xsane completely freezes. > I have also an Umax 2200SU (SCSI and USB) and I do have the same problem when conneczed via USB. Sometimes okay (especially with no scan area selct), but selecting a scan area, the system freezes at about 95%. I have experienced that with xsane and xscanimage, so most likely it is in the backend. Best regards, Klaus From henning@meier-geinitz.de Fri Jun 13 21:10:19 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 22:10:19 +0200 Subject: [sane-devel] avision: ADF support for HP7450C In-Reply-To: <20030613120420.610305e8.TomF@sjpc.org> References: <20030613120420.610305e8.TomF@sjpc.org> Message-ID: <20030613201019.GH3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 12:04:20PM -0700, TomF wrote: > I am using XSANE 0.89 on Redhat 9.0 with an HP 7450C scanner, with ADF > that works on Windows XP when I dual boot. > > Setup/Enhancement/Automatic Document Feeder Modus has only the option > None. I did not understand how to set SANE_NAME_SCAN_SOURCE from the > messages I read in the archives. How do you do this? The avision backend provides the option "adf" ("Enable Automatic-Document-Feeder"). If this option isn't displayed, maybe the backend hasn't detected your ADF. Try "scanimage --help". That should list the ADF option, maybe as "inactive". But the avision maintainer will know the details :-) > In February, Rene Rebe suggested using the CVS version with this > scanner. Is this still necessary? I would rather use a Redhat rpm if > one is available with this support. At least since the release of sane-backends 1.0.12 there have been no changes to the CVS concerning the avision backend. So if you can get an RPM of 1.0.12 this is current concerning SANE CVS. Bye, Henning From steve@icarus.com Sat Jun 14 02:09:46 2003 From: steve@icarus.com (Stephen Williams) Date: Fri, 13 Jun 2003 18:09:46 -0700 Subject: [sane-devel] TWAIN on SANE In-Reply-To: Message from "priya" of "Fri, 13 Jun 2003 13:00:16 +0530." <002701c3317d$a62e48b0$5505a8c0@priya> Message-ID: <200306140109.h5E19kl20155@icarus.com> priyag@newgen.co.in said: > I have an interface for scanner on TWAIN protocol for windows.=A0 Now i= > need to port it on the LINUX. = The TWAIN working group occasionally wonders about porting TWAIN to Linux, or defining a Linux variant of TWAIN. The former is iffy due to integration with the Windows message pump, and the latter comes with a lack of motivation from the involved parties. There is a SaneTWAIN datasource for Windows that allows Windows TWAIN apps access scanners over the network via SANE and the scanner's SANE driver, but I've not heard of any Linux version of that. If to write such a thing, the TWG might be interested. -- = Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." From kilgota@banach.math.auburn.edu Sat Jun 14 01:01:45 2003 From: kilgota@banach.math.auburn.edu (Theodore Kilgore) Date: Fri, 13 Jun 2003 19:01:45 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" Thanks again. It works! In-Reply-To: <20030613181351.GG3579@meier-geinitz.de> Message-ID: Briefly: I had to make the "stock" bayer and gamma routines from gphoto2 to work in my program. The color map is standard, too. I want to thank everyone for helping me focus on exactly what was needed and on what I should at least try out. My program is very primitive at this point. It will sense the resolution setting and will download all of the pictures on the camera, directly into files on the hard drive. It is primitive because I really don't know very well yet to divide everything into different functions, and I also have not figured out yet how the gphoto "filesystem" functions fit together, so every time I try to incorporate them, I get C code which gives ten thousand error messages. The code will probably not work on low resolution, either. I haven't tested that yet. Also this camera can be used as a PC cam to download something like 10 frames per second. I have not addressed this at all, yet. All of this will take a little bit more time, but the camera assuredly works. On Fri, 13 Jun 2003, Henning Meier-Geinitz wrote: > Color space/gamma table questions are ontopic on this list. Whew! I would have thought, myself, that the gphoto-devel list would be more appropriate, but I seem to be unable to subscribe to it. Does anyone know if the instructions at gphoto.org for subscribing to the list are out of date, or what? > As you > have seen I don't know much of this stuff myself and learned quite a > bit. > Well, it is one of my acquired skills as a professor, that I know how to ask good questions even if I don't have the answers ;-) > And to avoid any misconceptions: I'm neither the list maintainer nor > the inventor of SANE but simply know about how SANE works in general a > little bit :-) > > Bye, > Henning > I will try to send a picture to those who have responded to my questions, because I do not feel it is right to send it here. I will be glad to do that, though, if someone in charge (who, then?) sends me an e-mail saying it is OK to do that. The picture is slightly retouched with "sharpen" under GIMP. Nothing else done to it (except to turn it right-side up). It looked almost as good as the Windows-produced BMP file before, and my retouched picture looks better than the Windows-produced picture when similarly retouched, too. Funny thing is, out of 20 pictures I took, some of them looked better as-is with my program, and some of them looked better with the Windows software issued with the camera. Theodore Kilgore From brian@aljex.com Sat Jun 14 07:19:54 2003 From: brian@aljex.com (Brian K. White) Date: Sat, 14 Jun 2003 02:19:54 -0400 Subject: [sane-devel] TWAIN on SANE In-Reply-To: <200306140109.h5E19kl20155@icarus.com> References: <200306140109.h5E19kl20155@icarus.com> Message-ID: <3EEABE8A.3040102@aljex.com> Stephen Williams wrote: > priyag@newgen.co.in said: > >>I have an interface for scanner on TWAIN protocol for windows. Now i >>need to port it on the LINUX. > > > The TWAIN working group occasionally wonders about porting TWAIN to > Linux, or defining a Linux variant of TWAIN. The former is iffy due > to integration with the Windows message pump, and the latter comes > with a lack of motivation from the involved parties. > > There is a SaneTWAIN datasource for Windows that allows Windows TWAIN > apps access scanners over the network via SANE and the scanner's SANE > driver, but I've not heard of any Linux version of that. If to write > such a thing, the TWG might be interested. I saw TWAIN on Linux at the AIIM show the year before this last one. These people may know something about it: http://www.jflinc.com/ Since the booth where I saw this had a guy from this company working it, I later went on to buy a copy of their twain library for a windows/unix/scanning project I was working on(1). ------- (1) text-based unix database app (written in filePro) sends a escape-sequence to either FacetWin or AnzioLite/AnzioWin terminal emulators to run a command. command is like: "aljex_scan P:/CompanyX/DocTypeY/DocNumZ-PageN.tif" aka "aljex_scan P:/united/invc/129003-4.tif" aljex_scan is hard-coded to scan a single sheet at fax-quality letter-size and output the file given on the command-line. P: is on the server thanks to FacetWin or Samba. To view the scanned docs I made a pair of pretty simple cgi scripts. one shows a table of thumbnails of all images found with requested doctype & docnumber, click on a thumbnail and the other cgi script displays the image in a single img tage with witdh=100% so the "print" button on the web browser prints a full proper-size copy regardless what the window looks like. the unix app sends the "run-program" sequence to the terminal emulator, with an argument of: "start http://server/cgi-bin/viewthm?encryptedjunk where the cgi decrypts the query string and gets basically a path to the images minus the page numbers. this cgi generates a table of thumbnails and links where the link is the another cgi script and encrypted query string to view a particular page in full-size. (both scripts are very light-weight, just ksh. no perl, but do use sort and ls) The documents are given path & filenames based on the file & they are using within the app. The image viewer is just their web browser (images are converted to png, and png thumbnails generated on the server immediately after being saved). The scanner settings are all hard-coded in the little VB app I put on PC's that have scanners. Voila. plain old unix app now has scanned documents, and users don't have to learn 10 minutes of new material to use it, since the "document management" is just piggybacked off the existing app that they already know how to navigate. Merely now some of their screens have a new hot-key & pull-down menu to "scan/view/fax/email/print/administer". -- Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/ +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani From crapsite@gmx.net Sat Jun 14 13:34:40 2003 From: crapsite@gmx.net (Michael Herder) Date: Sat, 14 Jun 2003 14:34:40 +0200 Subject: [sane-devel] [Info] Microstar MR 9791 Message-ID: <20030614123502.1BB6B22@panda.mostang.com> Hi, for the archive: it has been reported, that the Microstar MR 9791 scanner works with the artec_eplus48u backend (thanks to Jan-Oliver Bohnert). and to Henning: It seems, that this is just another Medion brand; www.microstar.de directs me to www.medion.de at least. Concerning the desc file, should we just add this to mfg "Medion/Lifetec/Tevion/Cytron" ? (My guess is, that there are also Microstar models, that work with your gt68xx backend). bb Michael From henning@meier-geinitz.de Sat Jun 14 13:59:56 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 14 Jun 2003 14:59:56 +0200 Subject: [sane-devel] [Info] Microstar MR 9791 In-Reply-To: <20030614123502.1BB6B22@panda.mostang.com> References: <20030614123502.1BB6B22@panda.mostang.com> Message-ID: <20030614125956.GC7241@meier-geinitz.de> Hi, On Sat, Jun 14, 2003 at 02:34:40PM +0200, Michael Herder wrote: > it has been reported, that the Microstar MR 9791 scanner works with the > artec_eplus48u backend (thanks to Jan-Oliver Bohnert). Is this a new scanner? Where was it bought? Is the number correct? I'm asking because google knows nothing about this scanner and that's quite strange. > It seems, that this is just another Medion brand; www.microstar.de directs > me to www.medion.de at least. Correct, the domain is registered by: domain: microstar.de descr: MEDION AG > Concerning the desc file, should we just add this to > mfg "Medion/Lifetec/Tevion/Cytron" ? I propose to use a separate "Microstar" manufacturer for now. If more Microstar products pop up or Medion products are sold under the same number as Microstar products we can merge them. The idea of the merged entry is that Medion uses the same numbers for different labels. When we are sure that it's the same with Microstar, we can merge it. Merging means changing some more .desc files. > (My guess is, that there are also Microstar models, that work with > your gt68xx backend). Maybe. However, I haven't ever heard of Microstar (no reports yet). Bye, Henning From henning@meier-geinitz.de Sat Jun 14 14:47:33 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 14 Jun 2003 15:47:33 +0200 Subject: [sane-devel] ANNOUNCE: GTK Application for troubleshooting SANE problems Message-ID: <20030614134733.GA4347@meier-geinitz.de> Hi, I wanted to do some GTK2 programming and thought a little troubleshooting tool for sane-backends may help. The idea is to have a user-friendly tool that gathers all necessary information about the system and SANE installation and tells the user what might be wrong. sane-troubleshoot can be found http://www.meier-geinitz.de/sane/sts/ Please test and tell me if something doesn't work. Spelling and other corrections are also welcome. For a description, I just append the README. Bye, Henning This is the README of sane-troubleshoot. * What's the purpose of this program? It tries to find out what's wrong with your installation of SANE. It checks for some common mistakes and explains what to do to fix them and where to find documentation and help. It writes everything it finds out to a logfile. It's NOT an installation wizard as it doesn't change any files. It's intended to be used for scanners, but may also work with other devices supported by SANE. Currently it's in early alpha stage and is only tested on Linux/i386. * How is it used? Just run ./sane-troubleshoot. You'll need gtk2.0 (http://www.gtk.org). If you get an error about missing libraries you may need to build from source (see below). * How to build You need gtk-2.0 including the development headers. Just enter "make". There is no installation target yet. * What kind of tests does it do? (+ means: works, - means: planned) + Checks if SANE libraries, headers and config files are installed + Checks for multiple installations + Check, if libsane can be loaded + Check for the version of sane-backends + Try to open the test backend + List all scanners that are found by SANE, if the scanner is found: + find out the backend + enable debugging + try to scan a small image, list all errors - If the scanner isn't found - list known manufacturers, select one - list known models, select one - If the scanner is known: - find out the backend - check if it's in dll - find out the type of scanner - try to get SCSI/USB sane-find-scanner-like output - check permissions - If the scanner isn't known, warn about not supported - check libsub, /proc/bus/usb, /proc/scsi/scsi From nakal@web.de Sun Jun 15 00:27:59 2003 From: nakal@web.de (Nakal) Date: Sun, 15 Jun 2003 01:27:59 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EE851A0.CCA64E53@satzbau-gmbh.de> References: <200306102317.58064.nakal@web.de> <200306111902.41911.cinek@gmx.de> <3EE851A0.CCA64E53@satzbau-gmbh.de> Message-ID: <200306150127.59523.nakal@web.de> On Thursday 12 June 2003 12:10, abel deuring wrote: > A long shot: IIRC, these Microtek scanners may freeze, if you access > them with another LUN than 0 -- but they show up with all LUN values > from 0 to 7. So, if any backend tries to access the scanner with a > non-zero LUN, you'll have an unaccessible scanner. I don't know any > details, but *if* a SCSI command to a non-zero LUN confuses the scanner > in a way that the entire SCSI bus is blocked, worse errors may occur, > e.g., the disk with the root partition may be unaccessible. So it's best > to connect these cheap scanners to their own SCSI bus. OK. I did that. I disconnected all devices except the scanner. I get still same effect. > And you should tell FreeBSD not to look for all LUNs of the scanner > while it tries to detect devices on the SCSI bus. Yupp, I did that too, still same. It still gets timeout. I found out that I can scan gray pictures, because it's only one pass. It works perfectly! But as soon as the scanner tries another pass (e.g. color mode) then it does not react (like it forgot the last SCSI command it got). It does not freeze. The scanner is simply idle. I think, sane should repeat the SCSI-command until it succeeds and gets ACK and not just wait for ACK, because there won't come any as long as the scanner moves back the carriage. I can directly start another scan after pressing control+C. There is no problem, but it will always get timeout while initializing the scan for the second pass in 3-pass mode. I remember that earlier (1 or 2 years ago) when I used Linux, sane worked with my microtek without problems. Martin From crapsite@gmx.net Sun Jun 15 04:35:39 2003 From: crapsite@gmx.net (Michael Herder) Date: Sun, 15 Jun 2003 05:35:39 +0200 Subject: [sane-devel] [Info] Microstar MR 9791 Message-ID: <20030615033931.D928818B@panda.mostang.com> Henning Meier-Geinitz, Samstag, 14. Juni 2003 14:59: (sorry for sending this mail in private; I was using KMails "l" button though) > Hi, > > On Sat, Jun 14, 2003 at 02:34:40PM +0200, Michael Herder wrote: > > it has been reported, that the Microstar MR 9791 scanner works with the > > artec_eplus48u backend (thanks to Jan-Oliver Bohnert). > > Is this a new scanner? Where was it bought? Is the number correct? I'm > asking because google knows nothing about this scanner and that's > quite strange. I was told, that the scanner was bought at "Kaufland", June 2002. It's in fact an Artec E+ 48u (same pid,vid). Probably a device, which some discounter sells for one week, and that's it. > > It seems, that this is just another Medion brand; www.microstar.de > > directs me to www.medion.de at least. > > Correct, the domain is registered by: > domain:      microstar.de > descr:       MEDION AG > > > Concerning the desc file, should we just add this to > > mfg "Medion/Lifetec/Tevion/Cytron" ? > > I propose to use a separate "Microstar" manufacturer for now. If more > Microstar products pop up or Medion products are sold under the same > number as Microstar products we can merge them. Ok, I will do this. Thanks for your reply. bb Michael From oliver.rauch@rauch-domain.de Sun Jun 15 16:26:49 2003 From: oliver.rauch@rauch-domain.de (Oliver Rauch) Date: Sun, 15 Jun 2003 17:26:49 +0200 Subject: [sane-devel] multiple images on XSane In-Reply-To: <000601c32e4a$6e9dd180$a8ec403e@default> References: <20030601132533.21859.53611.Mailman@panda.mostang.com> <000601c32e4a$6e9dd180$a8ec403e@default> Message-ID: <200306151726.49165.oliver.rauch@rauch-domain.de> > fredjb@FJBrooks:~> ls -l /usr/local/bin > drwxr-xr-x 9 root root 1344 2003-06-05 16:56 xsane-0.90 you did not install xsane, it looks like you copied the source directory = to=20 /usr/local/bin/ To compile xsane you have to unpack it in a directory of your choice, eg /tmp/xsane-0.90 then you enter this directory and do =2E/configure make to install it you do (may be as root) make install Oliver From oliver.rauch@rauch-domain.de Sun Jun 15 18:24:13 2003 From: oliver.rauch@rauch-domain.de (Oliver Rauch) Date: Sun, 15 Jun 2003 19:24:13 +0200 Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030613073344.999.qmail@web20608.mail.yahoo.com> References: <20030613073344.999.qmail@web20608.mail.yahoo.com> Message-ID: <200306151924.13177.oliver.rauch@rauch-domain.de> Please can you find out if this depends on the selected area (or size) and the selected resolution. Oliver On Friday 13 June 2003 09:33, ope wrote: > I have an UMAX Astra 2200 scanner that I connecting to > through USB. My problem is basically this: > > When I use xsane I can preview as many times as I want > without any problems. However, once I actually try to > scan I sometimes have success and sometimes don't. > When I can't successfully scan what happens is that > the scanner runs, the lamp moves completely down and > back again, the 'REceiving RGB Data' progress bar is > just about complete and then xsane completely freezes. > > Sometimes if I just leave it for 5-10 minutes the > scanned image eventually pops up other times I can > leave it for more than an hour and the application is > still frozen. > > Here is what I see in messages: > kernel: hub.c: USB new device connect on bus2/2, > assigned device number 7 > kernel: usb.c: USB device 7 (vend/prod 0x1606/0x230) > is not claimed by any active driver. > kernel: usb.c: registered new driver usbscanner > kernel: scanner.c: 0.4.6:USB Scanner Driver > kernel: usb_control/bulk_msg: timeout > last message repeated 2 times > last message repeated 3 times > ... > kernel: scanner.c: read_scanner(0): excessive NAK's > received > > sane-find-scanner shows: > found USB scanner (vendor=3D0x1606, product=3D0x0230) at > /dev/usb/scanner0 > > > __________________________________ > Do you Yahoo!? > Yahoo! Calendar - Free online calendar with sync to Outlook(TM). > http://calendar.yahoo.com > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel --=20 http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:Oliver.Rauch@Rauch-Domain.DE From a.deuring@satzbau-gmbh.de Sun Jun 15 21:20:40 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Sun, 15 Jun 2003 22:20:40 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306150127.59523.nakal@web.de> References: <200306102317.58064.nakal@web.de> <200306111902.41911.cinek@gmx.de> <3EE851A0.CCA64E53@satzbau-gmbh.de> <200306150127.59523.nakal@web.de> Message-ID: <3EECD518.6000000@gmx.net> Nakal wrote: >>And you should tell FreeBSD not to look for all LUNs of the scanner >>while it tries to detect devices on the SCSI bus. > > > Yupp, I did that too, still same. It still gets timeout. I found out that I > can scan gray pictures, because it's only one pass. It works perfectly! But > as soon as the scanner tries another pass (e.g. color mode) then it does not > react (like it forgot the last SCSI command it got). It does not freeze. The > scanner is simply idle. > > I think, sane should repeat the SCSI-command until it succeeds and gets ACK > and not just wait for ACK, because there won't come any as long as the > scanner moves back the carriage. I can directly start another scan after > pressing control+C. There is no problem, but it will always get timeout while > initializing the scan for the second pass in 3-pass mode. > > I remember that earlier (1 or 2 years ago) when I used Linux, sane worked with > my microtek without problems. That could be due to different timeout settings. Older versions of Sane had different SCSI command timeoit settings for different operating systems. This is meanwhile "unified" to 2 minutes, which might be too small for the Scanmaker II. IIRC, the delay between two scan passes is really long. So you could try to increase that time to 3 or 4 minutes or whatever might be appropriate. You can do this by setting the environment variable SANE_SCSICMD_TIMEOUT to the timeout value (in seconds). Abel From nakal@web.de Mon Jun 16 00:45:01 2003 From: nakal@web.de (Nakal) Date: Mon, 16 Jun 2003 01:45:01 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EECD518.6000000@gmx.net> References: <200306102317.58064.nakal@web.de> <200306150127.59523.nakal@web.de> <3EECD518.6000000@gmx.net> Message-ID: <200306160145.01370.nakal@web.de> --Boundary-00=_9TQ7++/s4/fNiZr Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Sunday 15 June 2003 22:20, abel deuring wrote: > IIRC, the delay between two scan passes is really long. I don't think so. It always was working fast. Usually about 1 sec after the pass the scanner made some switching noises and then recalibrated the position and processed the next pass. The effect now is that the scanner does not do anything after returning to the start position. It's like it does not listen anymore. > So you could try to increase that time to 3 or 4 minutes or whatever > might be appropriate. You can do this by setting the environment > variable SANE_SCSICMD_TIMEOUT to the timeout value (in seconds). This environment variable seems not to have any effect on FreeBSD. I made some additional logs for you. Perhaps they are more informative. The command was: SANE_DEBUG_DLL=128 SANE_DEBUG_SANEI_SCSI=128 scanimage -v -d 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log 2>&1 These lines might be interesting: [sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 [sanei_scsi] sanei_scsi_cmd: scsi returned with status 16 (Look at the rest of it inside the attachment.) Thanks for your patience with me, Martin :) --Boundary-00=_9TQ7++/s4/fNiZr Content-Type: application/x-gzip; name="microtek-on-fbsd48.log.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="microtek-on-fbsd48.log.gz" H4sICF4C7T4AA21pY3JvdGVrLW9uLWZic2Q0OC5sb2cA7VhBb9owFL73V7zbisRInBBIkXrYoYdd tkOPVcUcxwGrxma2w2h//exAIQyQCo9tUtVLZMfv+/ye/b3nxA+WKi7GJS/qySPcc+eEmkDTBckX XIKuoJQSnAaS5L2rB995hIAaCyXcCO6/fLtrLArKnrgqYcGNFVoB6cW9HCqjZ4355/W4bQYIWTPR shyvR0ahE6Z/ZfoxE8xox58+rY2lpt7KcmrY9LAhCAU/otqaSGpGZSRFEYXZdxmceQ5wH1PoHwSE RuP2K3XP6h7ZpSmlnnN13Qlcp3Osli88BZXi5Vjgb9mglY1lVmz3afvuEebU2hT8nlhW1DaGwSjG Ep+OawV9aN/sjnDittCYVs5oOdZz58evp1SVkt/GyzzOhjGNu6v3t3GXsnVjQWUdLIqqqKp+FneF qrTvx50L8qaMHeadcLfm9MtkmRFzp81xegSWILAJApsisH0ENkNgBwjsEIHNEdgbjDZQwsIoi2Ck RTDaIv1zEpz09zPcmxA6zC+R4CQ7y6nsmFMXqToEkw4Ekw8EkxAEkxEJZsESVK3FZESCyYgEU24T TL1NMApLMApLMApLMApLMQpLMQpLUcd5elaFSo5+GB2pm28lTk8l/ndfPsk5AW0WiuzGQ0n5Gs8q vjy/6Eb0+5c5K5CnKvnTq3w3anZe1MdUcqmokcf2iVFbR43bo+0g/7c2cc+poTPu/C/WvuvNmF07 Nmwcs4wqMaMT7n+3fVOFOZt+M5t44ZBn8ZLcDGEullxaoA5yKISzUfOiTUDZz1qYwGB4CVXwo+2d 4bTc96mkjm484nF3RpeShzI3HORd35pvBinrfNC9X7r2Pca2PWazcBMUBG+4q43yyvol3BR8Grna AonbCpwJFflpYGLo8ypnmtSEWyB5lGTZX83DswP4QL4n5OC/INt1fKPuEdwZow2UtVlpeCEYh6/R 953zjirG5YFEaFGGBPezDPtZDMWz4zZcvzrtqNxhktryQxm1NeHLcC0Ynt6h/QFGpTx8P2obEFS1 ag7dfWgllLBTXl79Bv6vqLLqFgAA --Boundary-00=_9TQ7++/s4/fNiZr-- From aneeshmraj@hotmail.com Mon Jun 16 06:29:05 2003 From: aneeshmraj@hotmail.com (aneesh m raj) Date: Mon, 16 Jun 2003 10:59:05 +0530 Subject: [sane-devel] problem with UMAX 2000P scanner References: <20030613125548.GE3579@meier-geinitz.de> Message-ID: Hi, I have tried scanimage -L but it also says "No scanner detected" . when I use umax_pp -p -t 1 the scanner is detected. umax_pp is not commented in dll.conf. Regards Aneesh ----- Original Message ----- From: "Henning Meier-Geinitz" To: Sent: Friday, June 13, 2003 6:25 PM Subject: Re: [sane-devel] problem with UMAX 2000P scanner > Hi, > > On Fri, Jun 13, 2003 at 05:16:18PM +0530, aneesh m raj wrote: > > Thank u it worked the mode was in ECP+EPP . Im using a program to > > detect scanner devices but I cant retrieve the device by calling > > sane_get_devices() function .The SANE_Device structure is NULL. > > Try "scanimage -L" to make sure it's not a bug in your program. > First guess: "umax_pp" is commented out in dll.conf. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > From stef-listes@wanadoo.fr Mon Jun 16 08:49:10 2003 From: stef-listes@wanadoo.fr (stef) Date: Mon, 16 Jun 2003 07:49:10 +0000 Subject: [sane-devel] problem with UMAX 2000P scanner In-Reply-To: References: <20030613125548.GE3579@meier-geinitz.de> Message-ID: <20030616074910.GA707@wanadoo.fr> On Mon, Jun 16, 2003 at 10:59:05AM +0530, aneesh m raj wrote: > Hi, > I have tried scanimage -L but it also says "No scanner detected" . when I > use umax_pp -p -t 1 the scanner is detected. umax_pp is not commented in > dll.conf. > Regards > Aneesh > ----- Original Message ----- > From: "Henning Meier-Geinitz" > To: > Sent: Friday, June 13, 2003 6:25 PM > Subject: Re: [sane-devel] problem with UMAX 2000P scanner > Hello, maybe there are several instances of dll.conf on your system, and the one used by scanimage may have umax_pp commented out. Also, 'umax_pp -p -t 1' does direct hardware access, while the backend is configured by default to use ppdev character device. You can change this by editing umax_pp.conf and change the 'port' option to 'port 0x378', if 0x378 is really your parport address. Regards, Stef > > > Hi, > > > > On Fri, Jun 13, 2003 at 05:16:18PM +0530, aneesh m raj wrote: > > > Thank u it worked the mode was in ECP+EPP . Im using a program to > > > detect scanner devices but I cant retrieve the device by calling > > > sane_get_devices() function .The SANE_Device structure is NULL. > > > > Try "scanimage -L" to make sure it's not a bug in your program. > > First guess: "umax_pp" is commented out in dll.conf. > > > > Bye, > > Henning > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel@www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From aneeshmraj@hotmail.com Mon Jun 16 07:10:52 2003 From: aneeshmraj@hotmail.com (aneesh m raj) Date: Mon, 16 Jun 2003 11:40:52 +0530 Subject: [sane-devel] problem with UMAX 2000P scanner References: <20030613125548.GE3579@meier-geinitz.de> <20030616074910.GA707@wanadoo.fr> Message-ID: Thank u everybody it worked , there was more than one instance of dll.conf and umax_pp was commented in the instance of dll.conf that was actually used by the scanimage. ----- Original Message ----- From: "stef" To: Sent: Monday, June 16, 2003 1:19 PM Subject: Re: [sane-devel] problem with UMAX 2000P scanner > On Mon, Jun 16, 2003 at 10:59:05AM +0530, aneesh m raj wrote: > > Hi, > > I have tried scanimage -L but it also says "No scanner detected" . when I > > use umax_pp -p -t 1 the scanner is detected. umax_pp is not commented in > > dll.conf. > > Regards > > Aneesh > > ----- Original Message ----- > > From: "Henning Meier-Geinitz" > > To: > > Sent: Friday, June 13, 2003 6:25 PM > > Subject: Re: [sane-devel] problem with UMAX 2000P scanner > > > > Hello, > > maybe there are several instances of dll.conf on your system, and the one > used by scanimage may have umax_pp commented out. Also, 'umax_pp -p -t 1' does > direct hardware access, while the backend is configured by default to use ppdev > character device. You can change this by editing umax_pp.conf and change the 'port' > option to 'port 0x378', if 0x378 is really your parport address. > > Regards, > Stef > > > > > > Hi, > > > > > > On Fri, Jun 13, 2003 at 05:16:18PM +0530, aneesh m raj wrote: > > > > Thank u it worked the mode was in ECP+EPP . Im using a program to > > > > detect scanner devices but I cant retrieve the device by calling > > > > sane_get_devices() function .The SANE_Device structure is NULL. > > > > > > Try "scanimage -L" to make sure it's not a bug in your program. > > > First guess: "umax_pp" is commented out in dll.conf. > > > > > > Bye, > > > Henning > > > _______________________________________________ > > > Sane-devel mailing list > > > Sane-devel@www.mostang.com > > > http://www.mostang.com/mailman/listinfo/sane-devel > > > > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel@www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > From cpinto@yimports.com Mon Jun 16 12:20:39 2003 From: cpinto@yimports.com (Celso Pinto) Date: Mon, 16 Jun 2003 12:20:39 +0100 Subject: [sane-devel] HP Scanjet 2300c Message-ID: <001d01c333f9$5179dcc0$7800a8c0@cpinto> I all, I noticed there's no support for the HP 2300c scanner. I'd be very glad to develop the driver but I have no experience at all developing for Linux so i'd really appreciate if someone could just please spend some time explaing me how to setup a development environment and i'll give my best to bring a driver as soon as possible (after all my 2300c scanner is gathering dust :) ). Regards, Celso Pinto From henning@meier-geinitz.de Mon Jun 16 15:07:16 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 16 Jun 2003 16:07:16 +0200 Subject: [sane-devel] HP Scanjet 2300c In-Reply-To: <001d01c333f9$5179dcc0$7800a8c0@cpinto> References: <001d01c333f9$5179dcc0$7800a8c0@cpinto> Message-ID: <20030616140716.GD15421@meier-geinitz.de> Hi, On Mon, Jun 16, 2003 at 12:20:39PM +0100, Celso Pinto wrote: > I all, I noticed there's no support for the HP 2300c scanner. I'd be > very glad to develop the driver but I have no experience at all > developing for Linux so i'd really appreciate if someone could just > please spend some time explaing me how to setup a development > environment and i'll give my best to bring a driver as soon as possible > (after all my 2300c scanner is gathering dust :) ). The biggest problem usually is to find out which protocol the scanner speaks. If you can't get a detailed protocol description from the manufacturer (unlikely), you'll have to "sniff" the USb connection under Windows. Some links: http://www.meier-geinitz.de/sane/misc/develop.html http://www.meier-geinitz.de/sane/misc/unsupported.html When you have gathered some protocoll data, try to understand what's going on. E.g. which series of transfers moves the scan head to the beginning and how to scan in gray mode. Concerning programming on Linux: a compiler (gcc), an editor, some libraries like libusb and the SANE source code will be enough. I recommend to start with wroting a simple C program that uses sanei/sanei_usb.c to wrire some stuff to the scanner and read the results. sanei_usb is documented here: http://sanei.meier-geinitz.de/sanei__usb_8h.html And please inform us about what you do. If possible, set up a website with all the information you find so others can help or use the information. Bye, Henning From a.deuring@satzbau-gmbh.de Mon Jun 16 20:16:55 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Mon, 16 Jun 2003 21:16:55 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306160145.01370.nakal@web.de> References: <200306102317.58064.nakal@web.de> <200306150127.59523.nakal@web.de> <3EECD518.6000000@gmx.net> <200306160145.01370.nakal@web.de> Message-ID: <3EEE17A7.6080301@gmx.net> Nakal schrieb: > On Sunday 15 June 2003 22:20, abel deuring wrote: > > >>IIRC, the delay between two scan passes is really long. > > > I don't think so. It always was working fast. Usually about 1 sec after > the pass the scanner made some switching noises and then recalibrated > the position and processed the next pass. What I meant with "time between two scan passes" is the time between the last read command from one scan pass (or perhaps a command telling the scanner that this scan pass is ove) and the execution of the next command. I had only a very short look into microtek.c, so I may be wrong, but as I understand it, the last command for a scan pass is a "read", and the next command is a "scan start". The "scan start" command is probably issued immediately after the last read from the previous scan pass, so the duration of this "start" command is the time required to move the scan head back, to switch the color filter and then to do the "usual things" for the scan start, like perhaps recalibrating the CCD, moving the scan head into the start position, and whatever else. And this time is IIRC in the order of a minute or so, perhaps even more. > > The effect now is that the scanner does not do anything after returning > to the start position. It's like it does not listen anymore. > > >>So you could try to increase that time to 3 or 4 minutes or whatever >>might be appropriate. You can do this by setting the environment >>variable SANE_SCSICMD_TIMEOUT to the timeout value (in seconds). > > > This environment variable seems not to have any effect on FreeBSD. Which values did you try? > > > I made some additional logs for you. Perhaps they are more informative. > The command was: > SANE_DEBUG_DLL=128 SANE_DEBUG_SANEI_SCSI=128 scanimage -v -d > 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log > 2>&1 > > These lines might be interesting: > [sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 > [sanei_scsi] sanei_scsi_cmd: scsi returned with status 16 The first error occurs immediately after a "read", and this at least does not contradict my suspicions about the timeout problems. But we could get a better clue, if you add a "SANE_DEBUG_MICROTEK=255". The DLL debug output is less interesting. Abel From nakal@web.de Mon Jun 16 22:22:35 2003 From: nakal@web.de (Nakal) Date: Mon, 16 Jun 2003 23:22:35 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EEE17A7.6080301@gmx.net> References: <200306102317.58064.nakal@web.de> <200306160145.01370.nakal@web.de> <3EEE17A7.6080301@gmx.net> Message-ID: <200306162322.35147.nakal@web.de> --Boundary-00=_bUj7+3jA47kNUKn Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Monday 16 June 2003 21:16, abel deuring wrote: > The first error occurs immediately after a "read", and this at least > does not contradict my suspicions about the timeout problems. But we > could get a better clue, if you add a "SANE_DEBUG_MICROTEK=255". The > DLL debug output is less interesting. OK. I attached the output of the command: SANE_DEBUG_MICROTEK=255 SANE_SCSICMD_TIMEOUT=180 scanimage -v -d 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log 2>&1 Martin --Boundary-00=_bUj7+3jA47kNUKn Content-Type: application/x-gzip; name="microtek-on-fbsd48.log.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="microtek-on-fbsd48.log.gz" H4sICN8r7j4AA21pY3JvdGVrLW9uLWZic2Q0OC5sb2cA7Rtrb9tG8nt/xTRFkeRgyXyIehhwg8SP Rrg4yUVOe0VRCEtyKe+Zr3CXtpVffzNLyeZKtCzGThoUVmhF3J3XzmtnR9SfkqVcTEPul7O/YMKV EukM9C3E/ILHkEWQiKDIFD8HlYHjed0f/lyO/AWEPxWpUHsAJ+ODD+9Oj/6Ng3MJZzyOsx/h2YXV td2u/fw2rCBLIzHr/AI/wcc0yJKEpwqiDJEvSZZYpJwYh0IyP+bwpOAshoDFwi+YEln6BIqsRLG5 7HZvFe2GSZoRAcR/KHkC0lMBecHvI1SFvoVMAB8lyfHkeiFP4FLEMRQkhgKfBec8DUlEpNlB5dtd q64vJBbyu2WSgRTwL/3PAguvPr7XsZhSLDibyoClKS8QdTfkF7s5k9LdCJblPKUFbAkucTEEPn77 n4/jD3/UYUU4Xd6saDlnhaQlfSpFMd80hwzeZgpYCkd96HRIZYq0p60BJATO+nxp7dCgFJZJfgsT 2N/fh8nLt0e7J8vgWRpmEQ8EUcfYv37BpFo8jCvS8CrOgvNrgCSpo6FZXBs8Gyx898Hua1tZ0Auh N4KeC54DvQi8HvQ86PlQx/Vc6ONlQ58TPH3woe/BwAHH0ugj+nB91XFdDxwObsXd1YzcBXyvDw5y HICHs64Gsw1cgnG1SAHRQRh3CC6K7YIVwTCAwKMlcA6eHjTWa9cu6+7LwN0C/vqKItjSPB94nmHg 3UCs4d2gHK74ySG/EAGH03nO4QDjcg+sK6tfhzjB0fh6zjNC8Df0p6yAtyzByafL9PsUc0SFtZgg 7ifsnPiPcQ6eNtCY5DwQkQhgogoMN8I6mIzhePf338hZD07feO7QMjCPRZFcsoKjAi4Q3uv2bWN+ SQAwL0lMPHtAlOi1VIcx6XXtOvYHLvMslRh6TDHMv0XClNaOva7eccJmlCMOWM58EQsl1vIuKURi tL/BnMzQWq9ZHKkMU/mvBZujemPUwQr7LC51vpwonsNEfCZ8+2fwfqYlHF3lLA15aACWOXnCC5hz aSiiGkfgV0JJeI8rn7Akj9E2Q4PpCbvqQpgFpd5zJLLUyVov29oMiEtzPIy/K+jZoxHk4orHhhDH BToDlJjlSQ3VPIC9O3zyVBpC/ERbvl+KWHVECmcLPdHaHVz3YXaZxhkL9d6XY7bmRSpfwB/mig/J ZgdZgulUVtatzx5kqSqYVMt6g2j3Kp1mskSHqo/XEV+G/yul0qwnZyzMLndfi9lZjH+V0pFGDeRE hCT5C0gzg/2hmAmF2d0vCBGXJnezKJJcEWQd8FeWJAxOK35axw6mNNR4gf5FWrLBnyv8+CzR9uC5 OkOTPm+I/6wsMMzf5eQnq655zNEzFGYAtEsUM+XjLa3k8BjkLR51uDQ94ZI71eAQdTH6CnccVHRw jrpcI7GAGaeorRh3Nq2mm9di+gNn4XxNg6cFSyXuozwN5qhxlqs1SgYrsnUVYu/RITD410OExzyo zKaJR5QddMyvGqWicw004Z9KFAN1l8dYxnT8eUd/gGduh4oLwxinZwUnr5USSIpb1UvJopKoY2Nt EC4GMBvh/bWuV+RCeoeLmrBKMuJzVW9pB9oEPlGYkTpZ1KG8iCqvFWuraOOUAg6dly/zj/4gG0AX u9URio+uunnT2liBnbE8n99dMOp6boF1d524DaBRKW6D8FgrPtaKj7XiY634WCs+1oqPteJjrfhY K34ntSJVco2D5MYCuYZ6b2vqlS6ggoIzxWHBaQMglaUClfL5GpiCDTcunf1UGUUbkF/GRmv5uonb XNOtsoWZTgLaNRv7vnVY8qyOEphnL9D8W6EsOs0BqnyTqmoayKokgoNGLYwA06wxv9SnEOtTyVBr Kx6/AhNi3lyXJaC8ncULOHiG/+9bOyyg9wsW71tXfuRHUW9k7Yg0yvDeWv+GYFsiVrCByIwvpZ3i th4UIleYFJ5Zz5tUeAuw3QbYaQPstgHutQH22gD32wAP2gAP2wCPWhmlnQlb2dBuZUS7lRXtZjM2 ObvdM7x9aHk2GwzbO7vd7AyNLL0Gll8QX3Yrl7Jb+ZTdyqnsVl7ltPIqp11maOVVTiuvclolB6dV dnBa2dJpZUunlS2dVrZ0W9nSbWVLt12ab7ZlYwA6TTvcpqBvpOK2pfIQu1kzcJN81SLtunjMGy3F 0/duMNxyrU0aG35JzmqdmW2T59BYAOr7Hsb6ogW0zvPtFyDpBHKbT+BBjyUczx2NxawJgbVjwWdl zAqozl8Q0HltGyw5pV4H7FM/kHLw3ThhpuQ058U0SfDO7Y7cgWUN78bTTZAbRNvuDm3bcoxWw+/j w9PX78f/xXmfR1nB6aCFh3uzAddMnx4nod7FaACQ57HGQjKLTwa+RpXSxFd0TNXa2wE0rdHw6l4y rNQLOpaDtWIPPHWxWcyn1XMnK5NdfXIS6WwaEavNs/rE0QFrx6raSjveyN4IjmeqDeCTYyTYA7CW 10i/D2sjFkQejfciJGGcbLosCLiU2VqP/eUB6rhOwKF3AzVcdKum+hS3umZzVnfQmto7O5CwK3pI aiOyP8czacTKWBlgCfr0VOpewpq96pPUk2P5NKbTHnXwjHbE5A2u1Ktpi9H70AfHBhjoCwdtrYQI +gNSy7ZO09Wxr4/7KzOTCXL1b7j2Rmv6JdcnTEogqpRrxFfm8Uiyh15CUbBThQc9/mRExC/Ew0NL uvQtgGZsyEQdkvcULHv14VxcXccXda/OwqK6p7u8IfDKlPrj2ry4yP6gp/HKVLeF6vFbtZXoro6O +VnVGer7m1BnMtcmtbuWfm2RVomxSNgMY2kZW6DvyRF1JxgpX5FIi9YtUxg/PiayXT1QJ8AC6vEQ hYKHoCN0TQJyhhVj0RDGc5ZMmzsy397aaxLtwQy3FL+U8x1tpUsRqrMdhEuYSPXXFnWGjYtGEAzn KT0KtwcDRyNrW+9AujD8wDGWraXQ66KvIpr2wAVdv4yiqhfftx0LZVg4VMpD6p4b+SNnwflUpCqb kqHWvqJcTpJjbZykrRPdznUGfUyn8vOCN4ZAsAfrjtdg9vbMnGHPddaYaRH+fj9zvM1+Nggf2M9M u97lZ473lf3Mcx/d7Ou7medu9jL3gbOZadU7nMxzb3zMRPwSH8Ot0VvxMeuf4mK24wzv4WI8DZsK Jyypsryxono/2atXVNVlQBy9nRz9CBCFeBBaOSrQl+H79WcUjKohEeku1amzgs2rp/zxEFgShj3a XSleH8983/uZz9wZNpTvLR3mH39a/HJ93OOceQ+mf/sJ9R6yfxdn23vI/1XCavvztGc/oB/dVcx8 OemmMsjB0xLWBI41cPuNhdDaOjdQ1NUG1UAFV8UcUwl431h4+yGFt7+16p0Hlf5b6959SOmdVd3f VDoIvBojERPmM3IPVM/Vezk1/kdFkRUQlkX1c0z94Od4992auIgd8NUNuS5ajT5lr2X/qnoWDbWg MtXws8MgzmTjIyb8SjTWgTS+9gvQWZaF/px3f/g/1fq9y2Y6AAA= --Boundary-00=_bUj7+3jA47kNUKn-- From a.deuring@satzbau-gmbh.de Mon Jun 16 23:16:22 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Tue, 17 Jun 2003 00:16:22 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306162322.35147.nakal@web.de> References: <200306102317.58064.nakal@web.de> <200306160145.01370.nakal@web.de> <3EEE17A7.6080301@gmx.net> <200306162322.35147.nakal@web.de> Message-ID: <3EEE41B6.4050606@gmx.net> Nakal wrote: > On Monday 16 June 2003 21:16, abel deuring wrote: > > >>The first error occurs immediately after a "read", and this at least >>does not contradict my suspicions about the timeout problems. But we >>could get a better clue, if you add a "SANE_DEBUG_MICROTEK=255". The >>DLL debug output is less interesting. > > > OK. I attached the output of the command: > SANE_DEBUG_MICROTEK=255 SANE_SCSICMD_TIMEOUT=180 scanimage -v -d > 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log > 2>&1 What I meant, was a combination of the log output of the Sane SCVSI library and of the Microtek backend ;) This allows in many cases to see, which SCSI command issued from a certain function of the backend causes an error. But from the log data of microtek backend alone I think that this is a pure backend problem. This is the relevant part: [microtek] get_scan_status(6): 27, 0, 20736 -> #0 [microtek] > 1b 0 0 0 51 0 [microtek] get_scan_status: busy, retry in 5... [microtek] SENSE! fd = 0 [microtek] sense = 00 00 00 00. [microtek] get_scan_status(6): 27, 0, 20736 -> #1 [microtek] > 1b 0 0 0 51 0 [microtek] get_scan_status: busy, retry in 10... [microtek] SENSE! fd = 0 [microtek] sense = 00 00 00 00. [microtek] get_scan_status(6): 27, 0, 20736 -> #2 [microtek] > 1b 0 0 0 51 0 [microtek] get_scan_status: busy, retry in 15... [microtek] SENSE! fd = 0 [microtek] sense = 00 00 00 00. [microtek] get_scan_status(6): 27, 0, 20736 -> #3 [microtek] > 1b 0 0 0 51 0 [microtek] get_scan_status: busy, retry in 20... [microtek] sane_start: get_scan_status fails The lines "get_scan_status: busy, retry..." are only printed, if the SCSI command "get scan status" does not produce a SCSI error (i.e., nothing went wrong during the transport of the SCSI data from the scanner to the application). So the SCSI system (kernel, kernel drivers or Sane's SCSI libraray) is probably not involved, but the get_scan_status in the Microtek backend is perhaps a bit too "impatient". But the maintainer of the Microtek backend can probably give a more qualified comment. Abel From ope557@yahoo.com Tue Jun 17 08:39:15 2003 From: ope557@yahoo.com (ope) Date: Tue, 17 Jun 2003 00:39:15 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <200306151924.13177.oliver.rauch@rauch-domain.de> Message-ID: <20030617073915.89884.qmail@web20605.mail.yahoo.com> Sorry for taking so long to respond... It definately works better (or worse) if I adjust the scan resolution. I set resolution set to 100 and did not have any problems. I normally expect to run into problems after about 2-3 scans and never get more than 5 scans without problems. After adjusting the resolution to 100 I scanned more than 10 times without a single problem. Then I played around with other resolutions and ran into problems with any resloution setting I chose. Changing selected areas does not seem to affect results in any circumstance. I have also noticed another thing that is worth mentioning. At one point when the xsane seemed to be stuck I tried unplugging the scanner from the USB port. I was expecting xsane to fail and close down. What actually did happen was that the complete scanned image instantly popped up in the viewer and xsane was running as if nothing has happened. Just for fun I tried it couple more times and had the same results each time. It appears to me that that the scan is essentially complete at the point that it is freezing. Thanks, ope --- Oliver Rauch wrote: > > Please can you find out if this depends on the > selected area (or size) and the selected resolution. > > Oliver > > On Friday 13 June 2003 09:33, ope wrote: > > I have an UMAX Astra 2200 scanner that I > connecting to > > through USB. My problem is basically this: > > > > When I use xsane I can preview as many times as I > want > > without any problems. However, once I actually > try to > > scan I sometimes have success and sometimes don't. > > When I can't successfully scan what happens is > that > > the scanner runs, the lamp moves completely down > and > > back again, the 'REceiving RGB Data' progress bar > is > > just about complete and then xsane completely > freezes. > > > > Sometimes if I just leave it for 5-10 minutes the > > scanned image eventually pops up other times I can > > leave it for more than an hour and the application > is > > still frozen. > > > > Here is what I see in messages: > > kernel: hub.c: USB new device connect on bus2/2, > > assigned device number 7 > > kernel: usb.c: USB device 7 (vend/prod > 0x1606/0x230) > > is not claimed by any active driver. > > kernel: usb.c: registered new driver usbscanner > > kernel: scanner.c: 0.4.6:USB Scanner Driver > > kernel: usb_control/bulk_msg: timeout > > last message repeated 2 times > > last message repeated 3 times > > ... > > kernel: scanner.c: read_scanner(0): excessive > NAK's > > received > > > > sane-find-scanner shows: > > found USB scanner (vendor=0x1606, product=0x0230) > at > > /dev/usb/scanner0 > > > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! Calendar - Free online calendar with sync > to Outlook(TM). > > http://calendar.yahoo.com > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel@www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > -- > http://www.xsane.org > http://www.mostang.com/sane > http://www.rauch-domain.de > mailto:Oliver.Rauch@Rauch-Domain.DE __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From nakal@web.de Tue Jun 17 16:24:52 2003 From: nakal@web.de (Nakal) Date: Tue, 17 Jun 2003 17:24:52 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EEE41B6.4050606@gmx.net> References: <200306102317.58064.nakal@web.de> <200306162322.35147.nakal@web.de> <3EEE41B6.4050606@gmx.net> Message-ID: <200306171724.52572.nakal@web.de> --Boundary-00=_ELz7+hd1IAGKfsJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Tuesday 17 June 2003 00:16, abel deuring wrote: > What I meant, was a combination of the log output of the Sane SCVSI > library and of the Microtek backend ;) This is the output of: SANE_DEBUG_MICROTEK=255 SANE_SCSICMD_TIMEOUT=180 SANE_DEBUG_SANEI_SCSI=128 scanimage -v -d 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log 2>&1 I'm sorry for flooding the mailing list with my logs, Martin --Boundary-00=_ELz7+hd1IAGKfsJ Content-Type: application/x-gzip; name="microtek-on-fbsd48.log.gz" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="microtek-on-fbsd48.log.gz" H4sICMsu7z4AA21pY3JvdGVrLW9uLWZic2Q0OC5sb2cA7Rtrc9NI8ju/opetLcJV7Ggky3ZSlaUg j8V1BDgcdm+LolwjaeTMRi+kURLz6697JDuSrTgWBMJRMcJIM93T756etviQ8UjIiSecfPoRxkIp GU1BP0IgLkQAsQ+hdNNYiXNQMZi23X30YT7yEQh/IiOp9gBORgfv3pwe/RsHZxmciSCIf4GtC6PL rC57ehOWG0e+nHZ+h1/hfeTGYSgiBX6MyJfESyAjQYQ9mXEnEPA4FTwAlwfSSbmScfQY0jhHtkXW 7d7I2jWRKKYFEP+u+HFJTykkqfgapgr0DXgCeJ8RH48XgjyGSxkEkBIbChzunovIIxZxzQ4qn3WN qr5wMU/czlPmZhL+pf8YYODVx+9HHzbxlwJGL4BcMHPYnePR2EdIeJZZgJxkrpNnBvT3jCo7XCnu niEsjyKRIk87nrjY0UhrweJERMRNFfxL2V1DJkPt0iqj1/95P3r3dxVWepP5w5LZE55mpONPuUxn 6+aQwOtYAY/gqA+dDtlQkTm1ewAxgbOOmLufV1vJy8PkBiKwv78P4+evj3ZO5tE895QyQAmiirG/ +MC4EB5GxdLwIojd8wVAGFbR0E8sBjYDA78dYH3tPAb0POjtQs8C24SeD3YPejb0HKji2hb08WLQ FwRPNw70bRiYYBoafZduFlcV17LBFGAV1C1NyCrhe30wkeIAbJy1NBir4RKMpVlyaR2EsYZgIdsW GD4MXXBtEkEIsPVgTV5WuYzbrxruBvCLy/dhQ/O8E0mMmeAaYgXvGuVwyU8OxYV0BZzOEgEHmCj2 wLgy+lWIExwNFnN2LXT/RH+KU3jNQ5x8Mt8PnmDSKrDKCaJ+ws+J/gjn4EnDGuNEuNKXLoxViuFG WAfjERzv/PUnOevB6SvbGho1zGOZhpc8FaiAC4S3u31Wm58vAJgoM8yEe0Ar0Weujtqk3WVV7Hci S+Iow9DjiuOGkIZcae2wVfWOQj6lHHHAE+7IQCq5shGQQjKM9le4SXC01kse+CrGveWPlM9QvQHq YIl8HOQ6gY+VSGAsPxM++w3s30iEo6uER57waoB5Qp7wDGYiqymiGEfgF1Jl8BYlH/MwCdA2wxrR E37VBS92c70JZkhS7x5abGM9IIpm2hh/V9Bju7uQyCsR1Jg4TtEZIMdth9RQzAOwneHjJ1mNiV8p STu5DFRHRnBW6olkN1Huw/gyCmLu6c04wWwt0ih7Bn/XJT4kmx3EIabTrLBudfYgjlTKMzXfIWjt XqHTOMvRoarjVcTn3j95pjTp8Rn34sudl3J6FuDfQum4RgXkRHrE+TOI4hr5QzmVCrO7kxIiipbt xL6fCUWQVcA/eBhyOC3oaR2bmNJQ4yn6F2mJgTNTeLsVanuIRJ2hSZ82xH+cpxjmbxLyk2XXPBbo GQozANrFD7hy8JEkOTyG7AaPOpybnnDJnSpwiFqOvsAdBxXtnqMuV5YoYUYRaivAnU2r6fpTTr8T 3JutaPA05VGG+6iI3BlqnCdqZaUaKbJ1EWJv0SEw+FdDRATCLcymF/cpO+iYXzZKsc4CaCw+5cgG 6i4JsLDoOLOOvoEtq0NFSc0Yp2epELoeAuLiRvVSsig46jCsDbxyALMRPi90vcQXrndYFqlFkpGf iwJQO9A68LHCjNSJ/Q7lRVR5pXpcRhtFFHDovGKef/RN1gBa7lZHyD666vpNa20FdsaTZHZ7Bavr wBLr9vpyE8BahblAeKgxH2rMhxrzocZ8qDEfasyHGvOhxnyoMX/eGpMqwMZBcmOJVD29tzU1fUso NxVcCSgprQGkclaiUj4vgCnYcOPS2U/lvr8G+XlQ65EvutHNNd0yWZjqJKBds7GBXYUlz+ooiXn2 As2/EUrZMndR5etUVdFAXCQRHKzVwggwiRvzS3UKsT7lHLW25PFLMB7mzVVeXMrbcVDCwRb+u29s c5e+L3iwb1w5vuP7vYGxLSM/xmdj9aeODRexhLtmkamYc4uHjcxNZaIwKWwZT5tUeAMwawNstgG2 2gD32gDbbYD7bYAHbYCHbYB3WxmlnQlb2ZC1MiJrZUXWbMYmZ2e9mrcPDZvxwbC9s7NmZ2gkaTeQ /IL4Yq1cirXyKdbKqVgrrzJbeZXZLjO08iqzlVeZrZKD2So7mK1sabaypdnKlmYrW1qtbGm1sqXV Ls0327IxAM2mHW5d0DeuYrVd5S52s2bgJv4KIVmVPW7Zc/YKdvlwQ1kbNNbrf0nOap2ZWZ3msC6A 2FSABmN9mQCt83x7ATI6gdzkE3jQ46HAc0djMVuHwNoxFdM84CkU5y9w6by2CVY2oV4H7FM/kHLw 7TherLJJItJJGOKT1d21BoYxvB1PN0GuERnrDhkzzFqr4a/R4enLt6P/4rwj/DgVdNDCw329Ade8 Pr0XQ72L3QFAkgQaC5cp72r4GjXL6viKjqlae9v0agi7i75695JjhZ/ScR6MJTviaY1PAzEpXrxZ muzqExfSm/jE4vpZfVLpgLFtFO2obXuXrQXHs9ga8PExLtgDMObXrv4eVkYM8G0a7/m4RO1E1OWu K7IsXunNPz9A21QXMOm7huqVXa6JPv0ty1yf1Z23prbQNoT8it4SW4vszNCQPs8DVQMLMRYmme5B rNirOkm9PJ5MAjolUuev1sYYv0JJ7Yq2OH0PHTAZwEBfOMi0EnzoD0gtmzpNV+cM3SZYmhmPkapz TbW3u6JfChnCpMSj8mxl8aV5PMrsoZdQ9GwXYUXvf9Ui6XeiYaMlLfr1QBOu8USdlbcUZHvV4URe LeKSul5nXlo801PSELB5RH11bV4Usj/oabw80u2katwX7Sh6qqJjXldVgvr5OkXwLNEmZV1DfzZI x0RYhnyKsTSPLdDPOiVQvwBXviKWypYvVxg/DibAHT1QXYC71BuiFVLhgY7QFQ7IGZaMRUMYz3E4 ae7kfH9rr3C0B1Pcipw8m21rK11KT51tI1zIZaR/7qgSbBQaQTCcdX7dg4GpkbWttyEqDT8wa2Jr LrRc9BNG095Zruvkvl/08PvMNJCH0qEi4VHXvZY/Eu6eT2Sk4gkZauWnzfkkOdbaSdpy0e0sc9DH dJp9LmljCLh7sOp4DWZvT8wc9ixzhZhm4f79zLTX+9nAu2M/q9v1Nj8z7W/sZ7b14Gbf3s1sa72X WXeczepWvcXJbOvax+qIX+JjuDXaSz5m/Cwuxkxz+BUuJiKvqXDCkipOGiuqt+O9akVVXPU3ya/v J27o7RUvradC5SmqHi6lOoPSX1m9Mjp6PT76BcD38Oi1dDihn9/3q29F1OqNUEY7VOFOUz4rTiF4 7MwJw2Q7S2XvwynzRz9lmt/mlHkPLvqTnmzvV5OtT9P3zO49neDvWep77Brcs+Q/WOLZvDtisx8i XpqL2vtlqqmQNvG8jVWlaQysfmMpvaLbNSvqepWqaBQjnWGCB/trxO5/T7HZXYrNvsrc31Vu807l /v+xt3WXcpvLm8N1fY7Ay7nA57L+LukdnV+qvcsK/aM0jVPw8rQoP/UL0qOdNyvsIrYrlou6KmuV 9WlnmPdri3c2UQsqVg3/z9gN4qzxVSxxJRtPLzS+8l++p3HsOTPRffQ/+GQXHFc+AAA= --Boundary-00=_ELz7+hd1IAGKfsJ-- From andras@users.sourceforge.net Tue Jun 17 21:20:27 2003 From: andras@users.sourceforge.net (Major A) Date: Tue, 17 Jun 2003 21:20:27 +0100 Subject: [sane-devel] Re: Nikon Coolscan IV and scanner.c funky result -75 In-Reply-To: References: Message-ID: <20030617202027.GC2162@ventus.lan> Dmitri, Hope you don't mind me also sending a copy to the SANE list. > often I get this strange error : scanner.c blah funky result:-75 > blah. I have been getting this for a while and once it happens, OK, that sounds familiar, but I still don't know a solution to it. The tricky bit about USB is that if there's a bug in one of the generic drivers, it might go unnoticed for very long because most hardware doesn't trigger it. I'm pretty sure this has to do with the USB system in Linux, and I think it has been reported to the USB team. A user-level program like SANE should not be allowed to crash the computer like that, so it's certainly not exclusively a SANE problem. > the only solution is to reboot - the scanner module cannot be > unloaded, it says it is always in use. The scanner module is more and more obsolete. Most backends in newer SANE releases (from 1.0.11 I think) use libusb, which on Linux uses usbdevfs to access the hardware. This should be much more robust. Could you please try the latest SANE release and make sure libusb (including development files) is installed when you build it? > scanner: HP5300C and that works just great with hpusb driver. Also, > I have a Nikon (speaking of the brand loyalty :) D100 digital camera > and just managed to get it connected (USB) to linux using gphoto2 > and hotplug. They both work great - so it seems that I got the USB > system right. Unfortunately, as I said above, this is not a guarantee that the USB system works all right. I've been using the VIA USB 2.0 controller on my mainboard for months now without any trouble, but the moment I connected an external USB 2.0 hard disk to it, things started going very wrong. The solution is still outstanding, the USB team are working on it... > VueScan. Great program, I just wish to have bought it when it was > only $40 for lifetime updates, now it is $80 for a year :( Seems that SANE is finally taking away some of Ed's income... Andras =========================================================================== Major Andras e-mail: andras@users.sourceforge.net www: http://andras.webhop.org/ =========================================================================== From henning@meier-geinitz.de Tue Jun 17 22:02:21 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 17 Jun 2003 23:02:21 +0200 Subject: [sane-devel] Re: Nikon Coolscan IV and scanner.c funky result -75 In-Reply-To: <20030617202027.GC2162@ventus.lan> References: <20030617202027.GC2162@ventus.lan> Message-ID: <20030617210221.GA4027@meier-geinitz.de> Hi, On Tue, Jun 17, 2003 at 09:20:27PM +0100, Major A wrote: > Hope you don't mind me also sending a copy to the SANE list. > > > often I get this strange error : scanner.c blah funky result:-75 > > blah. I have been getting this for a while and once it happens, Error 75 is EOVERFLOW. That's usually caused in connection with UHCI USB controllers in "babble" condition. That means something happend on the USB that the device (or the host) did not expect. It seems to happen with some USB devices when you send too long buffers or read more data than the scanner expected. > OK, that sounds familiar, but I still don't know a solution to it. The > tricky bit about USB is that if there's a bug in one of the generic > drivers, it might go unnoticed for very long because most hardware > doesn't trigger it. I'm pretty sure this has to do with the USB system > in Linux, and I think it has been reported to the USB team. There is a known problem with the kernel USB driver that occurs, when the user space program tries to read more data than the scanner wants to provide. Well, it's not really a problem in my view, more a kind of bad interaction. Some discussion about this can be found on the linux-usb-users lists. I've asked the old maintainers and they say that the behaviour is intended. I'll try to summarize the problem (copied from a mail to linux-usb-users): | We want to read 42448 bytes (e.g. two scan lines). The buffer size is | 32768 so that's the maximum we can do in one turn. The scanner returns | only 21224 bytes (probably one scan line). So far that's ok. | | The reason is that the next read reads only 9680 bytes instead of | 21224. The scanner doesn't seem to be able to handle this. So the scanner doesn't seem to like reads different from the size of one scan line (?). I gueess the backend shouldn't try to read more than the scanner is able to return. While the scanner driver's behaviour isn't the optimum (it could try to read 21224 bytes twice), I don't think it's wrong. There was a short read and that's a way to signal it. > A > user-level program like SANE should not be allowed to crash the > computer like that, so it's certainly not exclusively a SANE problem. That's true. On the other hand the only crash concerning the USB scanner driver is when you open /dev/usb/scanner*, unplug the scanner, and read or write to the scanner. I'm talking about 2.4.21 (and the later -pre versions) here, older versions may have more bugs. > > the only solution is to reboot - the scanner module cannot be > > unloaded, it says it is always in use. Please show me the decoded OOPS message, if it's 2.4.21(-pre). Otherwise updating the kernel may help. > The scanner module is more and more obsolete. Most backends in newer > SANE releases (from 1.0.11 I think) use libusb, They are able to use libusb. If the scanner driver is loaded, it will be used. > which on Linux uses usbdevfs to access the hardware. This should be > much more robust. For most scanners it works better. For some it doesn't (E.g. Mustek 600CU). But basically, you are right. > Could you please try the latest SANE release and make sure > libusb (including development files) is installed when you build it? And tell us the kernel version :-) > > scanner: HP5300C and that works just great with hpusb driver. Different USB driver :-) The Nikon Coolscan 4 seems to be the only scanner with this problem. At least that's the only one I ever got reports for. So I really think it's either a scanner or backend problem. > > Also, > > I have a Nikon (speaking of the brand loyalty :) D100 digital camera > > and just managed to get it connected (USB) to linux using gphoto2 > > and hotplug. They both work great - so it seems that I got the USB > > system right. > > Unfortunately, as I said above, this is not a guarantee that the USB > system works all right. I've been using the VIA USB 2.0 controller on > my mainboard for months now without any trouble, but the moment I > connected an external USB 2.0 hard disk to it, things started going > very wrong. The solution is still outstanding, the USB team are > working on it... I've heard similar reports and they seem to be fixed with 2.4.21. But your milage may vary... > > VueScan. Great program, I just wish to have bought it when it was > > only $40 for lifetime updates, now it is $80 for a year :( > > Seems that SANE is finally taking away some of Ed's income... By the way: The problem with coolscan/kernel scanner driver seems to happen (have happened?) also with vuescan. Looks like a similar scanning routine is used. Bye, Henning From andras@users.sourceforge.net Tue Jun 17 22:26:08 2003 From: andras@users.sourceforge.net (Major A) Date: Tue, 17 Jun 2003 22:26:08 +0100 Subject: [sane-devel] Re: Nikon Coolscan IV and scanner.c funky result -75 In-Reply-To: <20030617210221.GA4027@meier-geinitz.de> References: <20030617202027.GC2162@ventus.lan> <20030617210221.GA4027@meier-geinitz.de> Message-ID: <20030617212608.GD2162@ventus.lan> > I'll try to summarize the problem (copied from a mail to > linux-usb-users): > > | We want to read 42448 bytes (e.g. two scan lines). The buffer size is > | 32768 so that's the maximum we can do in one turn. The scanner returns > | only 21224 bytes (probably one scan line). So far that's ok. > | > | The reason is that the next read reads only 9680 bytes instead of > | 21224. The scanner doesn't seem to be able to handle this. > > So the scanner doesn't seem to like reads different from the size of > one scan line (?). I gueess the backend shouldn't try to read more > than the scanner is able to return. Ah, OK, but Coolscan2 strictly tries to read one scanline at the time. On the LS-40, this is a maximum of 23328 bytes (2916 pixels, 4 channels each, 2 bytes per channel), which is less than 32k. > They are able to use libusb. If the scanner driver is loaded, it will > be used. OK, in that case please make sure the scanner module isn't loaded. > The Nikon Coolscan 4 seems to be the only scanner with this problem. > At least that's the only one I ever got reports for. So I really think > it's either a scanner or backend problem. Hmmm, that would be me... the scanner is a bit silly in the way that it tunnels SCSI commands across USB in a proprietary way, but it seems to work great in most cases, so it's probably not a hardware fault. > > Unfortunately, as I said above, this is not a guarantee that the USB > > system works all right. I've been using the VIA USB 2.0 controller on > > my mainboard for months now without any trouble, but the moment I > > connected an external USB 2.0 hard disk to it, things started going > > very wrong. The solution is still outstanding, the USB team are > > working on it... > > I've heard similar reports and they seem to be fixed with 2.4.21. But > your milage may vary... No, not mine -- in fact, 2.4.20 nearly works, 2.4.21 is totally broken. With a different card, 2.4.21 works just fine... > By the way: The problem with coolscan/kernel scanner driver seems to > happen (have happened?) also with vuescan. Looks like a similar > scanning routine is used. That's right. VueScan also uses (used?) the scanner module, so go figure... Andras =========================================================================== Major Andras e-mail: andras@users.sourceforge.net www: http://andras.webhop.org/ =========================================================================== From a.deuring@satzbau-gmbh.de Tue Jun 17 22:30:44 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Tue, 17 Jun 2003 23:30:44 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306171724.52572.nakal@web.de> References: <200306102317.58064.nakal@web.de> <200306162322.35147.nakal@web.de> <3EEE41B6.4050606@gmx.net> <200306171724.52572.nakal@web.de> Message-ID: <3EEF8884.2000805@gmx.net> Nakal wrote: > On Tuesday 17 June 2003 00:16, abel deuring wrote: > > >>What I meant, was a combination of the log output of the Sane SCVSI >>library and of the Microtek backend ;) > > > This is the output of: > SANE_DEBUG_MICROTEK=255 SANE_SCSICMD_TIMEOUT=180 > SANE_DEBUG_SANEI_SCSI=128 scanimage -v -d 'microtek:/dev/scanner' > --mode color -y 50 > microtek-on-fbsd48.log 2>&1 > > I'm sorry for flooding the mailing list with my logs, Never mind, a few kilobytes are OK, IMHO. First a disclaimer for the following stuff: I don't have FreeBSD installed, I used it only rarely, and I never wrote software specifically for FreeBSD. So I am writing as a "backseat driver" ;) Looking through the log, it seems to me that something is wrong in sanei_scsi.c. From your log file: [microtek] .stop_scan... [microtek] SPS:1b 0 0 0 0 0 [sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 [microtek] SENSE! fd = 0 [microtek] sense = 00 00 00 00. scanimage: min/max graylevel value = 21/255 [microtek] sane_start... The "stop scan" command returns an error (the "sanei_scsi" line), and all following SCSI commands return errors too. The interesting point is this: For some the commands we have the line "scsi returned with status 10", for other commands we have the line "scsi returned with status 16". Since the sense handler is called for both status values, I assume that you are using FreeBSD's CAM interface. (The other FreeBSD SCSI interface calls the sense handler of the backend only for a single status value.) This is the relevant part of sanei_scsi.c: if ((ccb->ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_CMP) { SANEI_SCSI_Sense_Handler handler; DBG (1, "sanei_scsi_cmd: scsi returned with status %d\n", (ccb->ccb_h.status & CAM_STATUS_MASK)); if((ccb->ccb_h.status & CAM_STATUS_MASK) == SANE_STATUS_DEVICE_BUSY) return SANE_STATUS_DEVICE_BUSY; handler = fd_info[fd].sense_handler; if (handler) { SANE_Status st = (*handler) (fd, ((u_char*)(&ccb->csio.sense_data)), fd_info[fd].sense_handler_arg); cam_freeccb(ccb); return st; } else return SANE_STATUS_IO_ERROR; } Googling quickly for 'freebsd cam.h', I found a version of cam.h at http://www.freebsd.cz/pub/FreeBSD/branches/4.0-stable/src/sys/cam/cam.h, and found these definitions for the status values 10 and 16: 10 -> CAM_SEL_TIMEOUT, /* Target Selection Timeout */ 16 -> CAM_AUTOSENSE_FAIL = 0x10,/* Autosense: request sense cmd fail */ (definitions of this kind tend to be stable -- but control is better than trust some cases: Martin, can you confirm this for your version of cam.h?) OK, many commands fail with a selection time out. Not very surprising for a slow scanner with probably somewhat dumb firmware ;) This status means that the scanner simply did not accept the SCSI command, so it does not make sense to call the sense handler, but the sense handler is called anyway. (Fortunately, the CAM system sets the sense data to all zero, so that the backend doesn't become completely confused...) If this happens, sanei_scsi_cmd2 should return SANE_STATUS_DEVICE_BUSY, and the backend should retry to issue the command for a few times. It is perhaps enough to change the following part: if((ccb->ccb_h.status & CAM_STATUS_MASK) == SANE_STATUS_DEVICE_BUSY) return SANE_STATUS_DEVICE_BUSY; to if((ccb->ccb_h.status & CAM_STATUS_MASK) == CAM_SEL_TIMEOUT) return SANE_STATUS_DEVICE_BUSY; to fix at least some a part of the problem, but the backend will probably also need some patches... Another point: From reading cam.h, I think that the sense handler should only be called, if the bit CAM_AUTOSNS_VALID is set in ccb_h.status. Generally, I have the impression that the FreeBSD/CAM part of sanei_scsi.c could need a review. But that should be done by somebody who can run Sane under FreeBSD ;) Abel From oliver.rauch@rauch-domain.de Tue Jun 17 22:58:16 2003 From: oliver.rauch@rauch-domain.de (Oliver Rauch) Date: Tue, 17 Jun 2003 23:58:16 +0200 Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030617073915.89884.qmail@web20605.mail.yahoo.com> References: <20030617073915.89884.qmail@web20605.mail.yahoo.com> Message-ID: <200306172358.16932.oliver.rauch@rauch-domain.de> On Tuesday 17 June 2003 09:39, ope wrote: > I have also noticed another thing that is worth > mentioning. At one point when the xsane seemed to be > stuck I tried unplugging the scanner from the USB > port. I was expecting xsane to fail and close down. > What actually did happen was that the complete scanned > image instantly popped up in the viewer and xsane was > running as if nothing has happened. Just for fun I > tried it couple more times and had the same results > each time. It appears to me that that the scan is > essentially complete at the point that it is freezing. This sounds as if there is a problem with the USB communication. Do you get any messages about USB problems in /var/log/messages ? Oliver From henning@meier-geinitz.de Tue Jun 17 23:11:32 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 00:11:32 +0200 Subject: [sane-devel] Re: Nikon Coolscan IV and scanner.c funky result -75 In-Reply-To: <20030617212608.GD2162@ventus.lan> References: <20030617202027.GC2162@ventus.lan> <20030617210221.GA4027@meier-geinitz.de> <20030617212608.GD2162@ventus.lan> Message-ID: <20030617221132.GD4027@meier-geinitz.de> Hi, On Tue, Jun 17, 2003 at 10:26:08PM +0100, Major A wrote: > > I'll try to summarize the problem (copied from a mail to > > linux-usb-users): > > > > | We want to read 42448 bytes (e.g. two scan lines). The buffer size is > > | 32768 so that's the maximum we can do in one turn. The scanner returns > > | only 21224 bytes (probably one scan line). So far that's ok. > > | > > | The reason is that the next read reads only 9680 bytes instead of > > | 21224. The scanner doesn't seem to be able to handle this. > > > > So the scanner doesn't seem to like reads different from the size of > > one scan line (?). I gueess the backend shouldn't try to read more > > than the scanner is able to return. > > Ah, OK, but Coolscan2 strictly tries to read one scanline at the > time. On the LS-40, this is a maximum of 23328 bytes (2916 pixels, 4 > channels each, 2 bytes per channel), which is less than 32k. Ok. I was talking about a log created by vuescan: Mar 18 07:02:26 kletskop kernel: scanner.c: read stats(0): result:0 this_read:32768 partial:21224 count:42448 Mar 18 07:02:26 kletskop kernel: uhci.c: uhci_result_interrupt/bulk() failed with status 500000 [...] Mar 18 07:02:26 kletskop kernel: scanner.c: read stats(0): result:-75 this_read:9680 partial:9680 count:9680 Mar 18 07:02:26 kletskop kernel: scanner.c: read_scanner(0): funky result:-75. Consult Documentation/usb/scanner.txt. Mar 18 07:02:36 kletskop kernel: usb_control/bulk_msg: timeout I remember similar reports about SANE but can't find a log at the moment. Hint for the bug reporter: A kernel logfile would be nice. For that, enable USB debugging in make menuconfig (probably already enabled) and debug messages in drivers/usb/scanner.h. This way we can see what's exactly going on. > > The Nikon Coolscan 4 seems to be the only scanner with this problem. > > At least that's the only one I ever got reports for. So I really think > > it's either a scanner or backend problem. > > Hmmm, that would be me... the scanner is a bit silly in the way that > it tunnels SCSI commands across USB in a proprietary way, but it seems > to work great in most cases, so it's probably not a hardware fault. Maybe it just doesn't like "half-sent" buffers. On the other hand, if you don't send more than one scan line I really don't know what's wrong. > > By the way: The problem with coolscan/kernel scanner driver seems to > > happen (have happened?) also with vuescan. Looks like a similar > > scanning routine is used. > > That's right. VueScan also uses (used?) the scanner module, so go > figure... But vuescan does read more than 32k at once. At least that what's the log shows. Maybe it's a different problem? Bye, Henning From nakal@web.de Wed Jun 18 00:07:59 2003 From: nakal@web.de (Nakal) Date: Wed, 18 Jun 2003 01:07:59 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EEF8884.2000805@gmx.net> References: <200306102317.58064.nakal@web.de> <200306171724.52572.nakal@web.de> <3EEF8884.2000805@gmx.net> Message-ID: <200306180107.59518.nakal@web.de> On Tuesday 17 June 2003 23:30, abel deuring wrote: > First a disclaimer for the following stuff: I don't have FreeBSD > installed, I used it only rarely, and I never wrote software > specifically for FreeBSD. So I am writing as a "backseat driver" ;) Try it :) > I assume that you are using FreeBSD's CAM interface. Yes, that's right. > Googling quickly for 'freebsd cam.h', I found a version of cam.h at > http://www.freebsd.cz/pub/FreeBSD/branches/4.0-stable/src/sys/cam/cam >.h, and found these definitions for the status values 10 and 16: > > 10 -> CAM_SEL_TIMEOUT, /* Target Selection Timeout */ > 16 -> CAM_AUTOSENSE_FAIL = 0x10,/* Autosense: request sense cmd fail > */ > (definitions of this kind tend to be stable -- but control is better > than trust some cases: Martin, can you confirm this for your version > of cam.h?) The values 10 and 16 are still correct, but I'm sure you are using the enums by name. That should be fine, of course. Seems nothing has changed in cam.h since 2000/03/17. Even FreeBSD-current (5.1) seems to use the same values (2002/01/09). You can find the kernel sources for cam here (just in case you haven't found cam.c): ftp://ftp2.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/sys/cam > OK, many commands fail with a selection time out. Not very surprising > for a slow scanner with probably somewhat dumb firmware ;) Firmware? :) No firmware patch yet. My scanner is still good :) I'm patient. > Another point: From reading cam.h, I think that the sense handler > should only be called, if the bit CAM_AUTOSNS_VALID is set in > ccb_h.status. Hmmm... that's too high-level for me. I am not really a kernel developer. Maybe freebsd mailing lists would help you. http://www.freebsd.org/support.html#mailing-list > Generally, I have the impression that the FreeBSD/CAM part of > sanei_scsi.c could need a review. But that should be done by somebody > who can run Sane under FreeBSD ;) Well, I will try to help, but I am also a simple user who just writes 'make install' in /usr/ports/graphics/xsane and is expecting that everything works after few minutes. :) Generally it is better to have contact with the responsible ports committer. You can find him here: http://www.FreeBSD.org/cgi/ports.cgi?query=xsane&stype=all The ports version of xsane in FreeBSD ports tree is 0.90. Tomorrow I want to take a look, if I am able to build xsane-0.90 with your suggested patch. Martin From ope557@yahoo.com Wed Jun 18 01:14:21 2003 From: ope557@yahoo.com (ope) Date: Tue, 17 Jun 2003 17:14:21 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <200306172358.16932.oliver.rauch@rauch-domain.de> Message-ID: <20030618001421.34819.qmail@web20604.mail.yahoo.com> What I see in messages are a lot of messages saying: kernel: usb_control/bulk_msg: timeout last message repeated 2 times last message repeated 3 times ... and after 10 minutes or so I will see: kernel: scanner.c: read_scanner(0): excessive NAK's received --- Oliver Rauch wrote: > On Tuesday 17 June 2003 09:39, ope wrote: > > > I have also noticed another thing that is worth > > mentioning. At one point when the xsane seemed to > be > > stuck I tried unplugging the scanner from the USB > > port. I was expecting xsane to fail and close > down. > > What actually did happen was that the complete > scanned > > image instantly popped up in the viewer and xsane > was > > running as if nothing has happened. Just for fun > I > > tried it couple more times and had the same > results > > each time. It appears to me that that the scan is > > essentially complete at the point that it is > freezing. > > This sounds as if there is a problem with the USB > communication. > > Do you get any messages about USB problems > in /var/log/messages ? > > Oliver > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From pjh@coastal.net.au Wed Jun 18 04:46:43 2003 From: pjh@coastal.net.au (Peter Howard) Date: 18 Jun 2003 13:46:43 +1000 Subject: [sane-devel] Problem building on OSX In-Reply-To: References: Message-ID: <1055908005.2315.64.camel@pig> On Sun, 2003-06-08 at 22:07, Peter O'Gorman wrote: > Hi Peter, > > I am guessing here, but are you using Apple's developer tools which > shipped with 10.2 ? Indeed. > This works for me with the ld from the December 2002 developer tools, > looks like a linker issue may have been fixed in that release. > > You can get a copy of the December 2002 tools from > http://connect.apple.com after free registration. > > I'd be interested to know if this solves your problem, I thought that > this was solved prior to release of 1.0.12, but it may have only been > "solved" for those of us with the latest linker :( Skipping the mini-saga of getting it downloaded . . . I installed the December update this morning. And, lo and behold, sane builds and installs. Thanks. While I'm here . . .the reason I've been building sane is to do with the "less than perfect" support for OSX from scanner manufacturers. Searching back through the mailing list archives I saw some comments agreeing with that, but nothing much more. I have sitting next to me an Epson USB scanner (Perfection 610) beloning to my in-laws. Having had zero luck with the official Epson driver I'm turning to sane (which I also use on my linux box). However, not being the most technically minded, what my Mother-in-law really wants is to be able to drive the scanner from inside iPhoto. Has anyone done work on a sane frontend to plug in as a normal OSX scanner input? Given no SANE->TWAIN bridge around on OSX I suspect not, or not very far. But if you don't ask . . .:-) PJH > On Sunday, June 8, 2003, at 10:53 AM, Peter Howard wrote: > > > (I've searched the archive and have seen related problems but not > > enough > > info to work the rest out :-( > > > > I'm trying to build sane-backends 1.0.12 on OSX 10.2, and I get the > > following load errors: > > > > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a > > ../backend/.libs/libsane.dylib -lm -framework CoreFoundation -framework > > IOKit > > ld: multiple definitions of symbol _getopt > > /usr/lib/libm.dylib(getopt.So) definition of _getopt > > ../lib/liblib.a(getopt.o) definition of _getopt in section > > (__TEXT,__text) > > ld: multiple definitions of symbol _opterr > > /usr/lib/libm.dylib(getopt.So) definition of _opterr > > ../lib/liblib.a(getopt.o) definition of _opterr in section > > (__DATA,__data) > > ld: multiple definitions of symbol _optind > > /usr/lib/libm.dylib(getopt.So) definition of _optind > > ../lib/liblib.a(getopt.o) definition of _optind in section > > (__DATA,__data) > > ld: multiple definitions of symbol _optopt > > /usr/lib/libm.dylib(getopt.So) definition of _optopt > > ../lib/liblib.a(getopt.o) definition of _optopt in section > > (__DATA,__data) > > make[1]: *** [scanimage] Error 1 > > make: *** [all-recursive] Error 1 > > > > > > I gave no options to configure. > > > > Thanks > > > > PJH > > > > > > > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel@www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > From aneeshmraj@hotmail.com Wed Jun 18 09:07:30 2003 From: aneeshmraj@hotmail.com (aneesh m raj) Date: Wed, 18 Jun 2003 13:37:30 +0530 Subject: [sane-devel] The format of data after sane_read() Message-ID: This is a multi-part message in MIME format. ------=_NextPart_000_004C_01C3359E.C412D7E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi All, What will be the format of the output data received after the = sane_read() call ,will it be pnm format. Thanks Aneesh ------=_NextPart_000_004C_01C3359E.C412D7E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi All,
What will be the format of the output = data received=20 after the sane_read() call ,will it be pnm format.
Thanks
Aneesh
------=_NextPart_000_004C_01C3359E.C412D7E0-- From henning@meier-geinitz.de Wed Jun 18 09:11:47 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 10:11:47 +0200 Subject: [sane-devel] Problem building on OSX In-Reply-To: <1055908005.2315.64.camel@pig> References: <1055908005.2315.64.camel@pig> Message-ID: <20030618081147.GB12579@meier-geinitz.de> Hi, On Wed, Jun 18, 2003 at 01:46:43PM +1000, Peter Howard wrote: > While I'm here . . .the reason I've been building sane is to do with the > "less than perfect" support for OSX from scanner manufacturers. > Searching back through the mailing list archives I saw some comments > agreeing with that, but nothing much more. I have sitting next to me an > Epson USB scanner (Perfection 610) beloning to my in-laws. Having had > zero luck with the official Epson driver I'm turning to sane (which I > also use on my linux box). However, not being the most technically > minded, what my Mother-in-law really wants is to be able to drive the > scanner from inside iPhoto. What's iPhoto? A MacOS X image manipulation program? Can't she use the Gimp? > Has anyone done work on a sane frontend to plug in as a normal OSX > scanner input? I haven't heard of such a thing. > Given no SANE->TWAIN bridge around on OSX I suspect not, or not very > far. But if you don't ask . . Given the existing SANE-TWAIN bridges for Windows, it may not be to complicated to write one for MacOS X. But I'm just guessing here. Bye, Henning From henning@meier-geinitz.de Wed Jun 18 09:28:01 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 10:28:01 +0200 Subject: [sane-devel] The format of data after sane_read() In-Reply-To: References: Message-ID: <20030618082801.GD12579@meier-geinitz.de> Hi, On Wed, Jun 18, 2003 at 01:37:30PM +0530, aneesh m raj wrote: > What will be the format of the output data received after the > sane_read() call ,will it be pnm format. No, not really. See the SANE standard, "Image Data Format": http://www.mostang.com/sane/html/doc008.html Bye, Henning From petr.felenda@sun.com Wed Jun 18 11:25:22 2003 From: petr.felenda@sun.com (Petr Felenda) Date: Wed, 18 Jun 2003 12:25:22 +0200 Subject: [sane-devel] Revscan 19200i Message-ID: <3EF03E12.6070802@sun.com> I have scanner revscan 19200i. It is possible to use it with Sane ? Thanks Petr From henning@meier-geinitz.de Wed Jun 18 11:55:47 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 12:55:47 +0200 Subject: [sane-devel] Revscan 19200i In-Reply-To: <3EF03E12.6070802@sun.com> References: <3EF03E12.6070802@sun.com> Message-ID: <20030618105547.GE12579@meier-geinitz.de> Hi, On Wed, Jun 18, 2003 at 12:25:22PM +0200, Petr Felenda wrote: > I have scanner revscan 19200i. > It is possible to use it with Sane ? It's not in our lists so nobody seems to have tried so far. Maybe it's compatible to one of the supported devices? Can you please show us the output of "cat /proc/bus/usb/devices" when the scanner is plugged in? Bye, Henning From khk@khk.net Wed Jun 18 12:06:25 2003 From: khk@khk.net (khk@khk.net) Date: Wed, 18 Jun 2003 07:06:25 -0400 (EDT) Subject: [sane-devel] Problem building on OSX In-Reply-To: <1055908005.2315.64.camel@pig> References: <1055908005.2315.64.camel@pig> Message-ID: <49492.198.176.225.6.1055934385.squirrel@home.khk.net> > On Sun, 2003-06-08 at 22:07, Peter O'Gorman wrote: [ ... ] > While I'm here . . .the reason I've been building sane is to do with the > "less than perfect" support for OSX from scanner manufacturers. > Searching back through the mailing list archives I saw some comments > agreeing with that, but nothing much more. I have sitting next to me an > Epson USB scanner (Perfection 610) beloning to my in-laws. Having had > zero luck with the official Epson driver I'm turning to sane (which I > also use on my linux box). However, not being the most technically > minded, what my Mother-in-law really wants is to be able to drive the > scanner from inside iPhoto. Has anyone done work on a sane frontend to > plug in as a normal OSX scanner input? Given no SANE->TWAIN bridge > around on OSX I suspect not, or not very far. But if you don't ask . . [ ... ] For now you are stuck with a paper weight... Even with a Sane/TWAIN bridge, this configuration would not work: So far I had no success in getting the EPSON backend to actually scan on OS X. The scanner is recognized, and the initial communication up until the scan request does also work, but the backend never receives any image data from the scanner. The only way you can use this scanner under OS X at this time is with vuescan (http://www.hamrick.com). Karl Heinz From a.deuring@satzbau-gmbh.de Wed Jun 18 12:49:28 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Wed, 18 Jun 2003 13:49:28 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <200306171724.52572.nakal@web.de> <3EEF8884.2000805@gmx.net> <200306180107.59518.nakal@web.de> Message-ID: <3EF051C8.FE0079FE@satzbau-gmbh.de> Nakal wrote: > > On Tuesday 17 June 2003 23:30, abel deuring wrote: > > > First a disclaimer for the following stuff: I don't have FreeBSD > > installed, I used it only rarely, and I never wrote software > > specifically for FreeBSD. So I am writing as a "backseat driver" ;) > > > Try it :) > if you can give me some time ;) > > 10 -> CAM_SEL_TIMEOUT, /* Target Selection Timeout */ > > 16 -> CAM_AUTOSENSE_FAIL = 0x10,/* Autosense: request sense cmd fail > > */ > > (definitions of this kind tend to be stable -- but control is better > > than trust some cases: Martin, can you confirm this for your version > > of cam.h?) > > The values 10 and 16 are still correct, but I'm sure you are using the > enums by name. That should be fine, of course. Seems nothing has > changed in cam.h since 2000/03/17. Even FreeBSD-current (5.1) seems to > use the same values (2002/01/09). I tried to identify the error numbers in the log file. > > You can find the kernel sources for cam here (just in case you haven't > found cam.c): > ftp://ftp2.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/sys/cam Thanks for the pointer. But I think that it should be sufficient to read the CAM documentation on the FressBSD web site ;) It looks quite comprehensive. > > > OK, many commands fail with a selection time out. Not very surprising > > for a slow scanner with probably somewhat dumb firmware ;) > > Firmware? :) No firmware patch yet. My scanner is still good :) I'm > patient. An update should not be necessary (and would ptobably not help very much). What I meant is this: The first failing command ("stop scan") is rejected by the scanner with the reason "I'm busy". I assume that this is caused by a firmware which completely occipied by controlling the stepper motor of the scan head to move the scan head back after the scan. A better firmware with a decent interrupt management is able to accept SCSI command in such a situation, But Sane (specifically, sanei_scsi.c and the backend) should be able to work with a dumb scanner. > > > Another point: From reading cam.h, I think that the sense handler > > should only be called, if the bit CAM_AUTOSNS_VALID is set in > > ccb_h.status. > > Hmmm... that's too high-level for me. I am not really a kernel > developer. Maybe freebsd mailing lists would help you. > http://www.freebsd.org/support.html#mailing-list Thanks for the hint, but again, it should not be necesary to bother the FreeBSD developers. When a SCSI command is accepted by a device but results in an error, some details of the error are described in the so-called sense data, which can be retrieved by another SCSI command (REQUEST SENSE). REQUEST SENSE is automatically issued by the operating system, if this is reasonable. When the call issueing the failing command ends, the application can (1) check, if sense data is available, and (2) do some "clean up" or print details error information (for scanners, this can be tinhgs like "12V fuse blown" of "mechanical error", but also more generic stuff like "invalid SCSI command parameter"). One problem of the CAM part of sanei_scsi.c is that the avaliability of the sense data is not checked -- it simply assumes that it is available.. > > > Generally, I have the impression that the FreeBSD/CAM part of > > sanei_scsi.c could need a review. But that should be done by somebody > > who can run Sane under FreeBSD ;) > > Well, I will try to help, but I am also a simple user who just writes > 'make install' in /usr/ports/graphics/xsane and is expecting that > everything works after few minutes. :) > > Generally it is better to have contact with the responsible ports > committer. You can find him here: > http://www.FreeBSD.org/cgi/ports.cgi?query=xsane&stype=all > > The ports version of xsane in FreeBSD ports tree is 0.90. Tomorrow I > want to take a look, if I am able to build xsane-0.90 with your > suggested patch. No need to (re-)build xsane; the problem is in sane-backends. And I'm afraid that my patch will not completely fix it -- I think that there will be the need to retry a SCSI command that returns with "device busy". The problem is that I'm not sure, if this should be done in sanei_scsi.c or in the backend. IIRC we had a discussion of this question some time ago, but I don't have currently the time to search for it... If we don't find a volunteer for fixing sanei_scsi.c, I'll give a try during the weekend. Abel From henning@meier-geinitz.de Wed Jun 18 13:16:45 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 14:16:45 +0200 Subject: [sane-devel] Problem building on OSX In-Reply-To: <49492.198.176.225.6.1055934385.squirrel@home.khk.net> References: <1055908005.2315.64.camel@pig> <49492.198.176.225.6.1055934385.squirrel@home.khk.net> Message-ID: <20030618121645.GF12579@meier-geinitz.de> Hi, On Wed, Jun 18, 2003 at 07:06:25AM -0400, khk@khk.net wrote: > For now you are stuck with a paper weight... Even with a Sane/TWAIN bridge, > this configuration would not work: So far I had no success in getting the > EPSON backend to actually scan on OS X. But that's only with USB, isn't it? Or even only with this scanner? As far as I know, SCSI scanners work with the epson backend on MacOS X. At least I have one report about the Epson Perfection 1640SU working. More reports on which scanners work or don't work on MacOS X are welcome. Bye, Henning From khk@khk.net Wed Jun 18 14:10:08 2003 From: khk@khk.net (khk@khk.net) Date: Wed, 18 Jun 2003 09:10:08 -0400 (EDT) Subject: [sane-devel] Problem building on OSX In-Reply-To: <20030618121645.GF12579@meier-geinitz.de> References: <1055908005.2315.64.camel@pig> <49492.198.176.225.6.1055934385.squirrel@home.khk.net> <20030618121645.GF12579@meier-geinitz.de> Message-ID: <18767.198.176.225.6.1055941808.squirrel@home.khk.net> > Hi, > > On Wed, Jun 18, 2003 at 07:06:25AM -0400, khk@khk.net wrote: >> For now you are stuck with a paper weight... Even with a Sane/TWAIN >> bridge, >> this configuration would not work: So far I had no success in getting >> the >> EPSON backend to actually scan on OS X. > > But that's only with USB, isn't it? Or even only with this scanner? As > far as I know, SCSI scanners work with the epson backend on MacOS X. > At least I have one report about the Epson Perfection 1640SU working. > > More reports on which scanners work or don't work on MacOS X are > welcome. Yes, this is applies only to EPSON USB scanners under OS X. From maddog@mir.com Wed Jun 18 18:30:09 2003 From: maddog@mir.com (Matto Marjanovic) Date: Wed, 18 Jun 2003 13:30:09 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EEF8884.2000805@gmx.net> (message from abel deuring on Tue, 17 Jun 2003 23:30:44 +0200) References: <200306102317.58064.nakal@web.de> <200306162322.35147.nakal@web.de> <3EEE41B6.4050606@gmx.net> <200306171724.52572.nakal@web.de> <3EEF8884.2000805@gmx.net> Message-ID: <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> Hi, Sorry to get into this thread so late... I have to pull out all my microtek notes again; I might even already have a fix for this problem in the works --- a big graduation got in the way, and now I have to refresh many memories. But, in the meantime... 0) None of this generation of Microtek scanners supports SCSI disconnect. Disconnect needs to be disabled for the scanner device (if not the whole bus), and you should expect the scanner to monopolize the entire bus during a scan. 1) The firmware in the earlier Microtek scanners is particularly brain-dead with regards to timeouts like this. Even worse, I have pretty extensive documentation from Microtek --- *but every scanner deviates from the documented behavior in some important way*. Ugh. 2) With regards to this: >Looking through the log, it seems to me that something is wrong in >sanei_scsi.c. From your log file: > >[microtek] .stop_scan... >[microtek] SPS:1b 0 0 0 0 0 >[sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 >[microtek] SENSE! fd = 0 >[microtek] sense = 00 00 00 00. >scanimage: min/max graylevel value = 21/255 >[microtek] sane_start... > >The "stop scan" command returns an error (the "sanei_scsi" line), and >all following SCSI commands return errors too. The scanner probably *is* generating a SENSE error along with sense info. However, it is not a SCSI-2 device --- it follows SCSI-1-CCM (something like that) and it generates non-standard sense codes. I don't know about FreeBSD, but the Linux SCSI drivers always zero out the sense codes --- this frustrates me to no end. The Linux drivers are trying to be clever, but they assume that *every* device is SCSI-2, and since the codes do not conform to SCSI-2, they get squashed. Probably, FreeBSD is doing the same thing. What both OS's *should* do is just pass the poor sense codes up to the sense handler installed by the backend, which should be smart enough to deal with them. Instead, the sense handler always gets called with a bunch of zeros! 3) For 3-pass scans, the backend needs to implement some kind of delay between passes. *However*, because of o the loss of the actual sense information o the poor documentation it is unclear which commands can be sent during that delay, if that delay can be polled (i.e. ask the scanner if it is ready) or if it must be guessed, etc, etc. This is the part of maintaining this backend that I despise. I'll start rummaging through my notes. I'm recollecting now that I had a quick fix for this a couple of months ago --- but it was too late for the release back then, and then I got really really busy. -matt m. From nakal@web.de Wed Jun 18 22:51:22 2003 From: nakal@web.de (Nakal) Date: Wed, 18 Jun 2003 23:51:22 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <200306182351.22833.nakal@web.de> On Wednesday 18 June 2003 19:30, you wrote: > 0) None of this generation of Microtek scanners supports SCSI > disconnect. Disconnect needs to be disabled for the scanner device > (if not the whole bus), and you should expect the scanner to > monopolize the entire bus during a scan. I really don't understand SCSI much. FreeBSD gives me still "unexpected disconnect" with my scanner, after I switched off "disconnection" in my controller's BIOS. > 1) The firmware in the earlier Microtek scanners is particularly > brain-dead with regards to timeouts like this. Even worse, I have > pretty extensive documentation from Microtek --- *but every scanner > deviates from the documented behavior in some important way*. Ugh. Yes. It is a quite "cheap" scanner and came with a separate ISA SCSI-1 controller. Now I'm using one with a Symantec chipset (Tekram DC390/UW). The scanner is attached to external UW bus. I wonder if it is really correct to connect it like this, but IT WORKED earlier (1 or 2 years ago?) on Debian, so it should not be a problem. > The Linux > drivers are trying to be clever, but they assume that *every* device > is SCSI-2, and since the codes do not conform to SCSI-2, they get > squashed. > > Probably, FreeBSD is doing the same thing. What both OS's > *should* do is just pass the poor sense codes up to the sense handler > installed by the backend, which should be smart enough to deal with > them. Instead, the sense handler always gets called with a bunch of > zeros! Well, if I only had time to look at FreeBSD SCSI architecture, I would try to help. I wonder why they would remove information from the sense responses. > it is unclear which commands can be sent during that delay, if > that delay can be polled (i.e. ask the scanner if it is ready) or if > it must be guessed, etc, etc. There is a possibility to compile the FreeBSD kernel with CAM debugging. This produces LOTS of information (see: man camcontrol(8)). With just a bit luck, there might be some useful information about the scanner's behavior. > I'll start rummaging through my notes. I'm recollecting now that I > had a quick fix for this a couple of months ago --- but it was too > late for the release back then, and then I got really really busy. I don't know how many people are using old Microtek scanners. If it is too much trouble, simply forget it. Martin From mrjaneway@gmx.net Thu Jun 19 08:58:57 2003 From: mrjaneway@gmx.net (mrjaneway@gmx.net) Date: Thu, 19 Jun 2003 09:58:57 +0200 (MEST) Subject: [sane-devel] Sane support for Acer parallel port scanners Message-ID: <2263.1056009537@www36.gmx.net> Hello, I am new to this list, so I hope I dont ask any stupid questions.... I am also new to the Linux world and I installed SuSE Linux 8.2 on my PC. Everything is working, except my old scanner. It's a Acer / Benq 620P parallel port scanner, and in the Sane compatibility list the status for a driver for this model is marked as "unknown". Can you tell me if someone is working on a Sane driver for this model? Or can I use another driver that will work for my scanner too? I guess Acer is only relabeling its scanners.... Any help on this is very appreciated, thanks! Geetings, Tobias From henning@meier-geinitz.de Thu Jun 19 09:49:39 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 19 Jun 2003 10:49:39 +0200 Subject: [sane-devel] Sane support for Acer parallel port scanners In-Reply-To: <2263.1056009537@www36.gmx.net> References: <2263.1056009537@www36.gmx.net> Message-ID: <20030619084939.GJ12579@meier-geinitz.de> Hi, On Thu, Jun 19, 2003 at 09:58:57AM +0200, mrjaneway@gmx.net wrote: > I am new to this list, so I hope I dont ask any stupid questions.... I am > also new to the Linux world and I installed SuSE Linux 8.2 on my PC. Everything > is working, except my old scanner. It's a Acer / Benq 620P parallel port > scanner, and in the Sane compatibility list the status for a driver for this > model is marked as "unknown". Well, to be exact, it is not on our lists at all, only on Jonathan Buzzard's parallel port scanners list. Usually that means that there is no support in SANE. > Can you tell me if someone is working on a Sane driver for this > model? I don't think so. At least the scanner is not mentioned in our list or on the TODO list. I can add the Benq Parport scanners to our "unsupported" list to make that more clear. > Or can I use another driver that will work for my > scanner too? I guess Acer is only relabeling its scanners.... I don't know, but if it were possible to get it working with another backend, that fact would be most probably known. But it doesn't harm to try the parallel port backends. Just select "Parport" in the scanner search engine and try the hbackends that it mentions. Otherwise I guess it's up to you to write a backend. But I doubt it's worth the hassle for an old parport scanner. But maybe the maintainer of the snapscan backend which supports Benq SCSI scanners knows more details? Bye, Henning From henning@meier-geinitz.de Thu Jun 19 15:19:58 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 19 Jun 2003 16:19:58 +0200 Subject: [sane-devel] Device description format changed in CVS (.desc files) Message-ID: <20030619141958.GN12579@meier-geinitz.de> Hi, Yesterday I committed a new version of tools/sane-desc.c. That's the program that generates our HTML lists of supported devices and is also used for the scanner search engine. The main change is that there is no longer a backend status, only a per-device status. The possible status values have changed, I'll cite doc/descriptions.txt here: The keyword :status' is an indication of the level of support for the model. It's followed by one of the following keyword arguments: :unsupported', :untested', :minimal', :basic', :good', or :complete'. The :status' keyword refers to the previous :model', is optional and should be used only once per model. :unsupported' means the device is not supported at least by this backend. The keyword should only be used in the file unsupported.desc', or to make clear that a specific scanner is not supported by a backend. :untested' means the device may be supported but couldn't be tested. :minimal' means that the device is detected and scans at least in one mode. But the quality is bad or important features won't work. :basic' means it works at least in the most important modes but quality is not perfect. :good' means the device is usable for day-to-day work. Some rather exotic features may be missing. :complete' means the backends supports everything the device can do. Example: :status :untested' sane-desc.c still accepts the old status codes (with warnings) and tries to translate them: alpha->basic, beta->good, stable->complete. This translation isn't correct in mayne cases, however. So please update your description files as soon as possible to reflect the actual support for the devices. I'll update the unmaintained backends's description files. Thanks to Jochen Eisinger for updateing the scanner search enigine to the new format. Bye, Henning From a.deuring@satzbau-gmbh.de Thu Jun 19 20:59:10 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Thu, 19 Jun 2003 21:59:10 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306182351.22833.nakal@web.de> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> Message-ID: <3EF2160E.2090603@gmx.net> Nakal wrote: > I really don't understand SCSI much. FreeBSD gives me still "unexpected > disconnect" with my scanner, after I switched off "disconnection" in my > controller's BIOS. Could the FreeBSD driver ignore the BIOS settings? I assume that you can pass a parameter like "don't disconnect" to the driver. > Yes. It is a quite "cheap" scanner and came with a separate ISA SCSI-1 > controller. Now I'm using one with a Symantec chipset (Tekram > DC390/UW). The scanner is attached to external UW bus. I wonder if it > is really correct to connect it like this, but IT WORKED earlier (1 or > 2 years ago?) on Debian, so it should not be a problem. Well, a fast SCSI adapter may have problems with a slow device, but I don't believe that this is the case hre. After all, the scanner finishes one of the three passes, and that shows that several SCSI commands were successful. >> it is unclear which commands can be sent during that delay, if >>that delay can be polled (i.e. ask the scanner if it is ready) or if >>it must be guessed, etc, etc. > > > There is a possibility to compile the FreeBSD kernel with CAM debugging. > This produces LOTS of information (see: man camcontrol(8)). With just a > bit luck, there might be some useful information about the scanner's > behavior. That could be interesting -- but currently I think we can stay with the Sane debug messages. > I don't know how many people are using old Microtek scanners. If it is > too much trouble, simply forget it. From my POV, we should continue ;) I think you had simply the bad luck of being the first one to discover a bug in sanei_scsi.c (and perhaps another one in the Microtek backend) -- but these bugs could bite more people, if we don't fix them... And while I would really prefer it to leave the patches for sanei_scsi.c to somebody who has FreeBSD installed, I'll try to do it myself, if nobody shouts "I'm volunteering". But expect some extra work fixing typos in my patches ;) Abel PS: Considering the log output from running the Scanmaker II under Linux, it its perhaps worth, if you try my simple patch to sanei_scsi.c I am not sure, but both the backend and the scnner seem to be able to deal with a few failing commands. And the patch passes slightly better erro informations to the backend. From a.deuring@satzbau-gmbh.de Thu Jun 19 20:59:18 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Thu, 19 Jun 2003 21:59:18 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> References: <200306102317.58064.nakal@web.de> <200306162322.35147.nakal@web.de> <3EEE41B6.4050606@gmx.net> <200306171724.52572.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF21616.1030807@gmx.net> Matto Marjanovic wrote: > 0) None of this generation of Microtek scanners supports SCSI disconnect. > Disconnect needs to be disabled for the scanner device (if not the > whole bus), and you should expect the scanner to monopolize the entire > bus during a scan. > > 1) The firmware in the earlier Microtek scanners is particularly brain-dead > with regards to timeouts like this. Even worse, I have pretty extensive > documentation from Microtek --- *but every scanner deviates from the > documented behavior in some important way*. Ugh. At least you have some sort docs ;) > > 2) With regards to this: > > >Looking through the log, it seems to me that something is wrong in > >sanei_scsi.c. From your log file: > > > >[microtek] .stop_scan... > >[microtek] SPS:1b 0 0 0 0 0 > >[sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 > >[microtek] SENSE! fd = 0 > >[microtek] sense = 00 00 00 00. > >scanimage: min/max graylevel value = 21/255 > >[microtek] sane_start... > > > >The "stop scan" command returns an error (the "sanei_scsi" line), and > >all following SCSI commands return errors too. > > The scanner probably *is* generating a SENSE error along with sense info. > However, it is not a SCSI-2 device --- it follows SCSI-1-CCM (something > like that) and it generates non-standard sense codes. I don't think that the scanner returns any useful data in this case, except that it said "too busy to accept the SCSI command". I've found a Scanmaker II buried deep in a cabinet and connected it to my Linux box. Here we get a similar error: [microtek] .stop_scan... [microtek] SPS:1b 0 0 0 0 0 [sanei_scsi] scsi_req_enter: entered 0x40825008 [sanei_scsi] sanei_scsi.issue: 0x40825008 dev_max(currently)=8 max_active_device=2 (origin 1) scsi_dma_free_sectors=64 sg_pool_secs_aval=320 def_reserved_size=32768 >>> device=sg1 scsi0 chan=0 id=6 lun=0 em=0 sg_tablesize=127 excl=1 FD(1): timeout=120000ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 act: id=51 blen=0 t_o/elap=120000/20ms sgat=0 op=0x1b [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 2 [sanei_scsi] sanei_scsi_req_wait: waiting for 0x40825008 [sanei_scsi] sanei_scsi.issue: 0x40825008 dev_max(currently)=8 max_active_device=2 (origin 1) scsi_dma_free_sectors=64 sg_pool_secs_aval=320 def_reserved_size=32768 >>> device=sg1 scsi0 chan=0 id=6 lun=0 em=0 sg_tablesize=127 excl=1 FD(1): timeout=120000ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 rcv: id=51 blen=0 dur=620ms sgat=0 op=0x1b [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Erfolg [sanei_scsi] sense buffer: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [sanei_scsi] target status: 7f host status: 0003 driver status: 0026 [microtek] end_scan: OY! on stop_scan The non-zero values for host status and driver status indicate that the scanner did not "accept" the command. host status 3 means a timeout, but NOT a SCSI command timeout. driver status 26 means "driver timeout; suggest abort". The Linux part of sanei_scsi.c does not call the sense handler in this case (that would be pointless, because the scanner refused to do anything with the commands, so there is not sense data), but returns SANE_STATUS_DEVICE_BUSY. > I don't know about FreeBSD, but the Linux SCSI drivers always zero out > the sense codes --- this frustrates me to no end. The Linux drivers are > trying to be clever, but they assume that *every* device is SCSI-2, and > since the codes do not conform to SCSI-2, they get squashed. > > Probably, FreeBSD is doing the same thing. What both OS's *should* do > is just pass the poor sense codes up to the sense handler installed by > the backend, which should be smart enough to deal with them. Instead, > the sense handler always gets called with a bunch of zeros! Yes, they should do it, _if_ sense data is available. I tried to check this with Linux (but not very hard). I deliberately changed the data of the "start scan" command to "comm[6] = { 0x1B, 1, 1, 1, 1, 1 };" -- but the scanner simply accepted this command, while I expected to get some error back :( > > > 3) For 3-pass scans, the backend needs to implement some kind of delay > between passes. *However*, because of > > o the loss of the actual sense information > o the poor documentation > > it is unclear which commands can be sent during that delay, if that > delay can be polled (i.e. ask the scanner if it is ready) or if it > must be guessed, etc, etc. > > This is the part of maintaining this backend that I despise. I think that the backend should check for the error SANE_STATUS_DEVICE_BUSY and it should retry the failing commands for a reasonable amount of time. In the case of the 3-pass scans, this could be 30 seconds or so. Abel From alan.purchase@paradise.net.nz Fri Jun 20 09:25:35 2003 From: alan.purchase@paradise.net.nz (Alan Purchase) Date: 20 Jun 2003 20:25:35 +1200 Subject: [sane-devel] Microtek Scanmaker 6700 (USB and FireWire) Message-ID: <1056097536.2918.16.camel@localhost.localdomain> Hi, I have been running a dual boot Windows 98 and Mandrake Linux system for some time and now I want to drop Windows and run solely on Mandrake Linux 9.0. My problem is that I have a Microtek Scanmaker 6700 scanner that appears not to be supported by Sane. Can you tell me if someone is working on a Sane driver for this model and whether it will support USB, FireWire or both. Cheers, Alan. -- ______________________________________________________________________ Alan Purchase IT Consultant Tel: +64 9 817 3101 113 Victory Road Mobile: +64 21 925 028 Laingholm E-mail: alan.purchase@paradise.co.nz Auckland 1007 New Zealand ______________________________________________________________________ From henning@meier-geinitz.de Thu Jun 19 22:22:11 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 19 Jun 2003 23:22:11 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF2160E.2090603@gmx.net> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> <3EF2160E.2090603@gmx.net> Message-ID: <20030619212211.GP12579@meier-geinitz.de> Hi, On Thu, Jun 19, 2003 at 09:59:10PM +0200, abel deuring wrote: > From my POV, we should continue ;) I think you had simply the bad luck > of being the first one to discover a bug in sanei_scsi.c (and perhaps > another one in the Microtek backend) -- but these bugs could bite more > people, if we don't fix them... And while I would really prefer it to > leave the patches for sanei_scsi.c to somebody who has FreeBSD > installed, I'll try to do it myself, if nobody shouts "I'm > volunteering". But expect some extra work fixing typos in my patches ;) I'm not volunteering :-) but I can at least test if any of your patches break Mustek scanners on FreeBSD. Bye, Henning From henning@meier-geinitz.de Thu Jun 19 22:48:26 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 19 Jun 2003 23:48:26 +0200 Subject: [sane-devel] Microtek Scanmaker 6700 (USB and FireWire) In-Reply-To: <1056097536.2918.16.camel@localhost.localdomain> References: <1056097536.2918.16.camel@localhost.localdomain> Message-ID: <20030619214826.GC19044@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 08:25:35PM +1200, Alan Purchase wrote: > I have been running a dual boot Windows 98 and Mandrake Linux system for > some time and now I want to drop Windows and run solely on Mandrake > Linux 9.0. My problem is that I have a Microtek Scanmaker 6700 scanner > that appears not to be supported by Sane. Can you tell me if someone is > working on a Sane driver for this model and whether it will support USB, > FireWire or both. As it's not on our lists, it's quite unlikely than someone is working on it. Can you provide more details about the scanner, so we can at least list it as "unsupported"? E.g., plug it in, boot linux and show us the output of "cat /proc/bus/usb/devices", please. Maybe it's compatible to any of the already supported scanners. But I doubt that. Some links on how to write a SANE driver: http://www.meier-geinitz.de/sane/misc/unsupported.html http://www.meier-geinitz.de/sane/misc/develop.html Bye, Henning From yaya@ntlworld.com Thu Jun 19 23:35:22 2003 From: yaya@ntlworld.com (Philip) Date: Thu, 19 Jun 2003 23:35:22 +0100 Subject: [sane-devel] Canoscan D646U??? Message-ID: <200306192335.22638.yaya@ntlworld.com> Somone please help me. Using Mandrake 9.1 and need some help or information in obtaining a driver or support for this flatbed scanner, that is if there is any availible. Any info will be appreciated. Thanks From henning@meier-geinitz.de Fri Jun 20 09:32:45 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 20 Jun 2003 10:32:45 +0200 Subject: [sane-devel] Canoscan D646U??? In-Reply-To: <200306192335.22638.yaya@ntlworld.com> References: <200306192335.22638.yaya@ntlworld.com> Message-ID: <20030620083245.GD1867@meier-geinitz.de> Hi, On Thu, Jun 19, 2003 at 11:35:22PM +0100, Philip wrote: > Using Mandrake 9.1 and need some help or information in obtaining a driver or > support for this flatbed scanner, that is if there is any availible. > > Any info will be appreciated. All the information we have is listed in the scanner search engine: http://sane.informatik.uni-freiburg.de/cgi-bin/driver.pl?manu=canon&model=646&bus=any So as a summary: There is no driver yet. But you could contact the maintainer of the canon630u backend and find out, if these scanners are really similar and if your scanner can be supported by that backend. Please tell us the result. The maintainer is: Nathan Rutman . If the scanners are completely different, it's up to you to write a new backend: http://www.meier-geinitz.de/sane/misc/unsupported.html http://www.meier-geinitz.de/sane/misc/develop.html Bye, Henning From david@rondotheatre.co.uk Fri Jun 20 11:27:37 2003 From: david@rondotheatre.co.uk (david stevenson) Date: Fri, 20 Jun 2003 11:27:37 +0100 Subject: [sane-devel] Manufactures Message-ID: <200306201127.37790.david@rondotheatre.co.uk> Henning and all, I was rereading your >Some links on how to write a SANE driver: >http://www.meier-geinitz.de/sane/misc/unsupported.html >http://www.meier-geinitz.de/sane/misc/develop.html and it occurred to me that it may help to have a page directed at manufactures to explain how they can get their scanner supported. I realise that the number of requests on the list of this nature is low 8-) but the optimist in me says anyone working professionally on a scanner will have a look sooner or later, but may not want to reveal them selves. Just an idle thought, .... to generate work for others. David From henning@meier-geinitz.de Fri Jun 20 12:35:18 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 20 Jun 2003 13:35:18 +0200 Subject: [sane-devel] Manufactures In-Reply-To: <200306201127.37790.david@rondotheatre.co.uk> References: <200306201127.37790.david@rondotheatre.co.uk> Message-ID: <20030620113518.GH1867@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 11:27:37AM +0100, david stevenson wrote: > and it occurred to me that it may help to have a page directed at manufactures > to explain how they can get their scanner supported. You mean a page about what a manufacturer can do to get a SANE driver? Well, that's pretty easy: Write a driver like explained on the "unsupported page". Or pay someone else to write it. Releasing programming information may make it easier for someone else to write a driver, but it's not a guarantee to get it written. Something along these lines? I could also add that to the "unsupported page". Bye, Henning From david@rondotheatre.co.uk Fri Jun 20 12:53:53 2003 From: david@rondotheatre.co.uk (david stevenson) Date: Fri, 20 Jun 2003 12:53:53 +0100 Subject: [sane-devel] Manufactures In-Reply-To: <20030620113518.GH1867@meier-geinitz.de> References: <200306201127.37790.david@rondotheatre.co.uk> <20030620113518.GH1867@meier-geinitz.de> Message-ID: <200306201253.53192.david@rondotheatre.co.uk> On Friday 20 June 2003 12:35 pm, Henning Meier-Geinitz wrote: > Hi, > > On Fri, Jun 20, 2003 at 11:27:37AM +0100, david stevenson wrote: > > and it occurred to me that it may help to have a page directed at > > manufactures to explain how they can get their scanner supported. > > You mean a page about what a manufacturer can do to get a SANE driver? > > Well, that's pretty easy: Write a driver like explained on the > "unsupported page". Or pay someone else to write it. Releasing > programming information may make it easier for someone else to write a > driver, but it's not a guarantee to get it written. > > Something along these lines? I could also add that to the "unsupported > page". > Yes, general encouragement, I had not thought about all the details, it was an idea to see what others thought. But could include, benefits of working with the mailing list, testing, finding developers. Feedback on what would help them release Sane drivers with new units. David > Bye, > Henning > > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From henning@meier-geinitz.de Fri Jun 20 13:44:55 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 20 Jun 2003 14:44:55 +0200 Subject: [sane-devel] Manufactures In-Reply-To: <200306201253.53192.david@rondotheatre.co.uk> References: <200306201127.37790.david@rondotheatre.co.uk> <20030620113518.GH1867@meier-geinitz.de> <200306201253.53192.david@rondotheatre.co.uk> Message-ID: <20030620124455.GJ1867@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 12:53:53PM +0100, david stevenson wrote: > Yes, general encouragement, I had not thought about all the details, it was an > idea to see what others thought. > But could include, benefits of working with the mailing list, testing, finding > developers. Feedback on what would help them release Sane drivers with new > units. Ok, what about this one: http://www.meier-geinitz.de/sane/misc/manufacturers.html There is now also a page that explains the SANE license: http://www.meier-geinitz.de/sane/misc/license.html Bye, Henning From david@rondotheatre.co.uk Fri Jun 20 15:21:43 2003 From: david@rondotheatre.co.uk (david stevenson) Date: Fri, 20 Jun 2003 15:21:43 +0100 Subject: [sane-devel] Manufactures In-Reply-To: <20030620124455.GJ1867@meier-geinitz.de> References: <200306201127.37790.david@rondotheatre.co.uk> <200306201253.53192.david@rondotheatre.co.uk> <20030620124455.GJ1867@meier-geinitz.de> Message-ID: <200306201521.43432.david@rondotheatre.co.uk> Excellent, What instant service. Now all we need is manufactures to read it and start writing backends 8-) Thanks David > Ok, what about this one: > > http://www.meier-geinitz.de/sane/misc/manufacturers.html > > There is now also a page that explains the SANE license: > > http://www.meier-geinitz.de/sane/misc/license.html > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From Oliver.Schwartz@gmx.de Fri Jun 20 16:54:12 2003 From: Oliver.Schwartz@gmx.de (Oliver Schwartz) Date: Fri, 20 Jun 2003 17:54:12 +0200 Subject: [sane-devel] Sane support for Acer parallel port scanners In-Reply-To: <2263.1056009537@www36.gmx.net> References: <2263.1056009537@www36.gmx.net> Message-ID: <200306201754.37976.Oliver.Schwartz@gmx.de> =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > It's a Acer / Benq 620P parallel port scanner, and in the Sane > compatibility list the status for a driver for this model is marked > as "unknown". Can you tell me if someone is working on a Sane > driver for this model? Or can I use another driver that will work > for my scanner too?=20 As far as I know nobody ever got an Acer, Benq or Agfa scanner to work=20 with the snapscan backend. I can't say for Acer/Benq, but at least=20 Agfa seems to use it's own proprietary Parallel-SCSI adapter.=20 There is no documentation available for it, so the only chance would=20 be reverse-engineering the parallel port protocol using a logic=20 analyzer. =2D -Oliver =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+8y4p/V6sbrmfIuMRAvSwAJ0S0rHI3ZN7dSYEhhlIe6R8F5yPkACdGPnR JgOSvZrGyAdRtliWElH/t8k=3D =3Dj962 =2D----END PGP SIGNATURE----- From a.deuring@satzbau-gmbh.de Fri Jun 20 19:51:26 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Fri, 20 Jun 2003 20:51:26 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <20030619212211.GP12579@meier-geinitz.de> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> <3EF2160E.2090603@gmx.net> <20030619212211.GP12579@meier-geinitz.de> Message-ID: <3EF357AE.4090104@gmx.net> This is a multi-part message in MIME format. --------------010008090309060605090400 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Henning Meier-Geinitz schrieb: > I'm not volunteering :-) but I can at least test if any of your > patches break Mustek scanners on FreeBSD. Great. I've already sent a patch to Martin, and it seems to fix the problems with the Microtek Scanamker II. Attached is the proposed new version (with Martin's fixes of my typos) of sanei_scsi_cmd2 for FreeBSD/CAM. It should replace the function near line 2765 in sanei_scsi.c. Abel --------------010008090309060605090400 Content-Type: text/plain; name="sanei_scsi_cmd2_freebsd" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="sanei_scsi_cmd2_freebsd" #if USE == FREEBSD_CAM_INTERFACE SANE_Status sanei_scsi_cmd2(int fd, const void *cmd, size_t cmd_size, const void *src, size_t src_size, void *dst, size_t * dst_size) { /* xxx obsolete size_t cdb_size; */ struct cam_device *dev; union ccb *ccb; int rv; u_int32_t ccb_flags; char* data_buf; size_t data_len; SANE_Status status; if (fd < 0 || fd > CAM_MAXDEVS || cam_devices[fd] == NULL) { fprintf(stderr, "attempt to reference invalid unit %d\n", fd); return SANE_STATUS_INVAL; } /* xxx obsolete: cdb_size = CDB_SIZE (*(u_char *) src); */ dev = cam_devices[fd]; ccb = cam_getccb(dev); /* Build the CCB */ bzero(&(&ccb->ccb_h)[1], sizeof(struct ccb_scsiio)); bcopy(cmd, &ccb->csio.cdb_io.cdb_bytes, cmd_size); /* * Set the data direction flags. */ if(dst_size && *dst_size) { /* xxx obsolete: assert (cdb_size == src_size); */ ccb_flags = CAM_DIR_IN; data_buf = ((char*)(dst)); data_len = *dst_size; } else if(src_size > 0) { ccb_flags = CAM_DIR_OUT; data_buf = ((char*)(src)); data_len = src_size; } else { ccb_flags = CAM_DIR_NONE; data_buf = NULL; data_len = 0; } cam_fill_csio(&ccb->csio, /* retries */ 1, /* cbfncp */ NULL, /* flags */ ccb_flags, /* tag_action */ MSG_SIMPLE_Q_TAG, /* data_ptr */ (u_int8_t *)data_buf, /* dxfer_len */ data_len, /* sense_len */ SSD_FULL_SIZE, /* cdb_len */ cmd_size, /* timeout */ sane_scsicmd_timeout * 1000); /* Run the command */ errno = 0; if ((rv = cam_send_ccb(dev, ccb)) == -1) { cam_freeccb(ccb); return(SANE_STATUS_IO_ERROR); } if ((ccb->ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_CMP) { SANEI_SCSI_Sense_Handler handler; DBG (1, "sanei_scsi_cmd: scsi returned with status %d\n", (ccb->ccb_h.status & CAM_STATUS_MASK)); /* if((ccb->ccb_h.status & CAM_STATUS_MASK) == SANE_STATUS_DEVICE_BUSY) return SANE_STATUS_DEVICE_BUSY; */ switch (ccb->ccb_h.status & CAM_STATUS_MASK) { case CAM_BUSY: case CAM_SEL_TIMEOUT: case CAM_SCSI_BUSY: status = SANE_STATUS_DEVICE_BUSY; break; default: status = SANE_STATUS_IO_ERROR; } handler = fd_info[fd].sense_handler; if (handler && (ccb->ccb_h.status & CAM_AUTOSNS_VALID)) { SANE_Status st = (*handler) (fd, ((u_char*)(&ccb->csio.sense_data)), fd_info[fd].sense_handler_arg); cam_freeccb(ccb); return st; } else { cam_freeccb(ccb); return status; } } cam_freeccb(ccb); return SANE_STATUS_GOOD; } --------------010008090309060605090400-- From tang@mac.com Fri Jun 20 23:40:53 2003 From: tang@mac.com (Dino Tang) Date: Fri, 20 Jun 2003 15:40:53 -0700 Subject: [sane-devel] Problem building on OSX Message-ID: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> > But that's only with USB, isn't it? Or even only with this scanner? As > far as I know, SCSI scanners work with the epson backend on MacOS X. > At least I have one report about the Epson Perfection 1640SU working. > > More reports on which scanners work or don't work on MacOS X are > welcome. > As long as the usblib was installed properly using the recent toolset ( Dec 2002 ), quite a few of USB and SCSI devices should work. I have tested and got images back from the following devices: - UMax Astra 1220U in USB mode * Reasonable image quality, still need color correction. - UMax Astra 2000U in USB mode * Serious image quality problem. - Epson Perfection 1640SU in both USB and SCSI modes * Good image quality. Support a lot of options. Good performance in SCSI mode. - Epson Perfection 2450 PHOTO in USB mode * Good image quality. Support a lot of options. Still has problems in FireWire mode. - CANON IX-06015C ( similar to CanoScan 600 ) in SCSI mode * Does not support tiff format! ( --format=tiff ). I can only get image back in pnm format. --format=tiff returned bad argument error. This seems like a problem of the canon backend. Please correct me if I'm wrong. I too would like to see reports on which scanners work or don't work on MacOS X. --Dino From nakal@web.de Sat Jun 21 00:31:54 2003 From: nakal@web.de (Nakal) Date: Sat, 21 Jun 2003 01:31:54 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF357AE.4090104@gmx.net> References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> Message-ID: <200306210131.54270.nakal@web.de> On Friday 20 June 2003 20:51, abel deuring wrote: > Great. I've already sent a patch to Martin, and it seems to fix the > problems with the Microtek Scanamker II. Attached is the proposed new > version (with Martin's fixes of my typos) of sanei_scsi_cmd2 for > FreeBSD/CAM. It should replace the function near line 2765 in > sanei_scsi.c. Hi! I verified Your latest (second) patch. It also works without any problems, e.a. compiles, scans and picture looks fine. On FreeBSD 5.1 everything works fine, too, with this patch. Even my problem with "scanimage -L" disappeared there (still remember? looks like a kernel bug in FreeBSD-4.8). Martin :) From peter@pscomp.com Sat Jun 21 01:03:21 2003 From: peter@pscomp.com (Peter Santoro) Date: Fri, 20 Jun 2003 20:03:21 -0400 Subject: [sane-devel] scanimage and scanadf command line args Message-ID: <3EF3A0C9.1090907@pscomp.com> My application makes use of scanimage and scanadf (sane 1.0.12 backend and 1.0.11 frontend) and it appears that there are a few inconsistencies with respect to the command line args of these sane front-ends. For instance, when using my fujitsu fi-4120c, "scanadf --help" shows that there is a "--paper_size" option available. Actually, it needs to be entered as "paper_size". Also, there is no "--threshold" option listed on the help screen, but it can be entered and it does appear to work correctly. There are other apparent inconsistencies I've run across using scanimage, but I don't remember them now. None of these issues are a big deal, but I was wondering if I was missing something here. Thanks for your help, Peter From a.deuring@satzbau-gmbh.de Sat Jun 21 01:12:31 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Sat, 21 Jun 2003 02:12:31 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306210131.54270.nakal@web.de> References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> Message-ID: <3EF3A2EF.9020503@gmx.net> Nakal wrote: > I verified Your latest (second) patch. It also works without any > problems, e.a. compiles, scans and picture looks fine. > > On FreeBSD 5.1 everything works fine, too, with this patch. Even my > problem with "scanimage -L" disappeared there (still remember? looks > like a kernel bug in FreeBSD-4.8). Martin, thanks for this report. To be honest, i must admit that I can't really remember your first mails :( But it's nice to read that the patch fixes more bugs than expected :) Abel From a.deuring@satzbau-gmbh.de Sat Jun 21 01:12:34 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Sat, 21 Jun 2003 02:12:34 +0200 Subject: [sane-devel] Problem building on OSX In-Reply-To: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> References: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> Message-ID: <3EF3A2F2.2090509@gmx.net> Dino Tang wrote: > - CANON IX-06015C ( similar to CanoScan 600 ) in SCSI mode > * Does not support tiff format! ( --format=tiff ). I can only get image > back in pnm format. --format=tiff returned bad argument error. This > seems like a problem of the canon backend. Please correct me if I'm wrong. The backends have no idea about image formats except the sane-internal "format", so it is unlikely that this is a problem of the Canon backend. Does scanimage --format=tiff works with other scanners and the same Sane installation? Abel From maddog@mir.com Sat Jun 21 02:13:39 2003 From: maddog@mir.com (Matto Marjanovic) Date: Fri, 20 Jun 2003 21:13:39 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF3A2EF.9020503@gmx.net> (message from abel deuring on Sat, 21 Jun 2003 02:12:31 +0200) References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> Message-ID: <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> >> I verified Your latest (second) patch. It also works without any >> problems, e.a. compiles, scans and picture looks fine. ... >thanks for this report. To be honest, i must admit that I can't really >remember your first mails :( But it's nice to read that the patch fixes >more bugs than expected :) Likewise, I lost track of some of this thread. (But it's nice to see that I'm not immediately on the hook to fix anything anymore.) What does the patch do? (And how did it fix up the Microtek scanning?) -matt m. From brian_d_w@yahoo.com Sat Jun 21 10:14:56 2003 From: brian_d_w@yahoo.com (Brian D. Williams) Date: Sat, 21 Jun 2003 02:14:56 -0700 (PDT) Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> Message-ID: <20030621091456.81112.qmail@web41501.mail.yahoo.com> I have been trying to get sane to work with the epson perfection 660. I could build sane with 1.0.11 but not with the snapscan addition. I could not build 1.0.12 at all. It would stop building at when trying to make scanimage but I didn't see any error messages that made sense to me. I am running the latest os x (10.2.6). Sadly I don't have a scanner available (other than the epson) to test against. Any suggestions would be greatly appreciated. Brian --- Dino Tang wrote: > > But that's only with USB, isn't it? Or even only with this scanner? As > > far as I know, SCSI scanners work with the epson backend on MacOS X. > > At least I have one report about the Epson Perfection 1640SU working. > > > > More reports on which scanners work or don't work on MacOS X are > > welcome. > > > > As long as the usblib was installed properly using the recent toolset ( > Dec 2002 ), quite a few of USB and SCSI devices should work. I have > tested and got images back from the following devices: > > - UMax Astra 1220U in USB mode > * Reasonable image quality, still need color correction. > - UMax Astra 2000U in USB mode > * Serious image quality problem. > - Epson Perfection 1640SU in both USB and SCSI modes > * Good image quality. Support a lot of options. Good performance in > SCSI mode. > - Epson Perfection 2450 PHOTO in USB mode > * Good image quality. Support a lot of options. Still has problems in > FireWire mode. > - CANON IX-06015C ( similar to CanoScan 600 ) in SCSI mode > * Does not support tiff format! ( --format=tiff ). I can only get > image back in pnm format. --format=tiff returned bad argument error. > This seems like a problem of the canon backend. Please correct me if > I'm wrong. > > I too would like to see reports on which scanners work or don't work on > MacOS X. > > --Dino > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel ===== Brian Williams homepage == From henning@meier-geinitz.de Sat Jun 21 10:47:05 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 21 Jun 2003 11:47:05 +0200 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621091456.81112.qmail@web41501.mail.yahoo.com> References: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> <20030621091456.81112.qmail@web41501.mail.yahoo.com> Message-ID: <20030621094705.GB9347@meier-geinitz.de> Hi, On Sat, Jun 21, 2003 at 02:14:56AM -0700, Brian D. Williams wrote: > I have been trying to get sane to work with the epson perfection 660. I could > build sane with 1.0.11 but not with the snapscan addition. I could not build > 1.0.12 at all. It would stop building at when trying to make scanimage but I > didn't see any error messages that made sense to me. I am running the latest os > x (10.2.6). Sadly I don't have a scanner available (other than the epson) to > test against. Any suggestions would be greatly appreciated. Please show us the error messages (e.g. the last 100 lines of the output). Bye, Henning From a.deuring@satzbau-gmbh.de Sat Jun 21 13:13:18 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Sat, 21 Jun 2003 14:13:18 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF44BDE.4B306A98@satzbau-gmbh.de> Matto Marjanovic wrote: > > >> I verified Your latest (second) patch. It also works without any > >> problems, e.a. compiles, scans and picture looks fine. > ... > >thanks for this report. To be honest, i must admit that I can't really > >remember your first mails :( But it's nice to read that the patch fixes > >more bugs than expected :) > > Likewise, I lost track of some of this thread. (But it's nice to see > that I'm not immediately on the hook to fix anything anymore.) > > What does the patch do? (And how did it fix up the Microtek scanning?) Don't ask for too specific details ;) The main point is, that the sense handler is no longer called for every error status returned by FreeBSD's CAM system. Instead, sanei_scsi_cmd2 now returns either SANE_STATUS_GOOD, SANE_STATUS_IO_ERROR, or SANE_STATUS_DEVICE_BUSY, depending on the status returned by the OS. The sense handler is only called, if ccb->ccb_h.status & CAM_AUTOSNS_VALID is true, which should guarantee that useful sense data is available. Several attempts to send a command to the scanner time out (the first one is the "stop scan" command), where "time out" means that the host could not send the command to the scanner within a certain time (for Linux, this is ~0.5 seconds). This time out is different from the "command time out" value, which is the time the host waits until a device finishes a SCSI command. Without the patch, the sense handler of backend is called for every failing command, but because no sense data is available, the sense handler decides to return SANE_STATUS_GOOD, hence the backend makes wrong assuptions about the status of the scanner. What I don't really understand in hindsight is the CAM status value 16 in Martin's log data. It indicates that the FreeBSD CAM system tried to issue a REQUEST SENSE for one or another failing command (where "failing" means in this case that the scanner accepted the command, and returned CHECK CONDITION), and that the REQUEST SENSE was not successful. Another point: I would really appreciate if more people could test the patch -- I have some hope that it is not too buggy in itself, but not being able to test it for myself (well, ok -- I'm too lazy or too busy to install FreeBSD -- chose whatever you want...), I'm hesitating to commit it to the CVS server. Abel From brian_d_w@yahoo.com Sat Jun 21 13:13:08 2003 From: brian_d_w@yahoo.com (Brian D. Williams) Date: Sat, 21 Jun 2003 05:13:08 -0700 (PDT) Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621094705.GB9347@meier-geinitz.de> Message-ID: <20030621121308.13540.qmail@web41502.mail.yahoo.com> --0-1698544750-1056197588=:12806 Content-Type: text/plain; charset=us-ascii Content-Id: Content-Disposition: inline Hi Henning (and others), I have attached the last 100+ lines from from make. Thanks Brian --- Henning Meier-Geinitz wrote: > Hi, > > On Sat, Jun 21, 2003 at 02:14:56AM -0700, Brian D. Williams wrote: > > I have been trying to get sane to work with the epson perfection 660. I > could > > build sane with 1.0.11 but not with the snapscan addition. I could not > build > > 1.0.12 at all. It would stop building at when trying to make scanimage but > I > > didn't see any error messages that made sense to me. I am running the > latest os > > x (10.2.6). Sadly I don't have a scanner available (other than the epson) > to > > test against. Any suggestions would be greatly appreciated. > > Please show us the error messages (e.g. the last 100 lines of the > output). > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel ===== Brian Williams homepage == --0-1698544750-1056197588=:12806 Content-Type: text/plain; name="make_sane.txt" Content-Description: make_sane.txt Content-Disposition: inline; filename="make_sane.txt" gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=artec_eplus48u artec_eplus48u-s.c -fno-common -DPIC -o .libs/artec_eplus48u-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-artec_eplus48u.1.0.12.so .libs/artec_eplus48u.o .libs/artec_eplus48u-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o ../sanei/.libs/sanei_constrain_value.o ../sanei/.libs/sanei_usb.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-artec_eplus48u.1.so && ln -s libsane-artec_eplus48u.1.0.12.so libsane-artec_eplus48u.1.so) (cd .libs && rm -f libsane-artec_eplus48u.so && ln -s libsane-artec_eplus48u.1.0.12.so libsane-artec_eplus48u.so) creating libsane-artec_eplus48u.la (cd .libs && rm -f libsane-artec_eplus48u.la && ln -s ../libsane-artec_eplus48u.la libsane-artec_eplus48u.la) gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=ma1509 -DLIBDIR=/usr/local/lib/sane ma1509.c -fno-common -DPIC -o .libs/ma1509.o ma1509.c: In function `calibration': ma1509.c:826: warning: int format, long unsigned int arg (arg 3) ma1509.c: In function `send_gamma': ma1509.c:919: warning: int format, size_t arg (arg 3) rm -f ma1509-s.c ln -s ./stubs.c ma1509-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=ma1509 ma1509-s.c -fno-common -DPIC -o .libs/ma1509-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-ma1509.1.0.12.so .libs/ma1509.o .libs/ma1509-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o ../sanei/.libs/sanei_constrain_value.o ../sanei/.libs/sanei_usb.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-ma1509.1.so && ln -s libsane-ma1509.1.0.12.so libsane-ma1509.1.so) (cd .libs && rm -f libsane-ma1509.so && ln -s libsane-ma1509.1.0.12.so libsane-ma1509.so) creating libsane-ma1509.la (cd .libs && rm -f libsane-ma1509.la && ln -s ../libsane-ma1509.la libsane-ma1509.la) gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=ibm -DLIBDIR=/usr/local/lib/sane ibm.c -fno-common -DPIC -o .libs/ibm.o rm -f ibm-s.c ln -s ./stubs.c ibm-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=ibm ibm-s.c -fno-common -DPIC -o .libs/ibm-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-ibm.1.0.12.so .libs/ibm.o .libs/ibm-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o ../sanei/.libs/sanei_scsi.o ../sanei/.libs/sanei_config2.o ../sanei/.libs/sanei_constrain_value.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-ibm.1.so && ln -s libsane-ibm.1.0.12.so libsane-ibm.1.so) (cd .libs && rm -f libsane-ibm.so && ln -s libsane-ibm.1.0.12.so libsane-ibm.so) creating libsane-ibm.la (cd .libs && rm -f libsane-ibm.la && ln -s ../libsane-ibm.la libsane-ibm.la) gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=hp5400 -DLIBDIR=/usr/local/lib/sane hp5400.c -fno-common -DPIC -o .libs/hp5400.o In file included from hp5400.c:77: hp5400_internal.c: In function `CircBufferInit': hp5400_internal.c:411: warning: unused parameter `iHandle' hp5400_internal.c: In function `hp5400_test_scan_response': hp5400_internal.c:660: warning: unused parameter `req' hp5400_internal.c: In function `DoScan': hp5400_internal.c:729: warning: unused parameter `code' hp5400_internal.c: In function `hp5400_scan': hp5400_internal.c:909: warning: unused parameter `pHWParams' hp5400_internal.c: In function `InitScanner': hp5400_internal.c:1021: warning: int format, long unsigned int arg (arg 3) hp5400_internal.c: In function `InitScan2': hp5400_internal.c:1187: warning: comparison between signed and unsigned hp5400_internal.c:1223: warning: comparison between signed and unsigned In file included from hp5400.c:78: hp5400_sanei.c: In function `hp5400_bulk_read': hp5400_sanei.c:279: warning: passing arg 3 of `sanei_usb_read_bulk' from incompatible pointer type hp5400_sanei.c: In function `hp5400_bulk_read_block': hp5400_sanei.c:308: warning: passing arg 3 of `sanei_usb_read_bulk' from incompatible pointer type hp5400_sanei.c: In function `hp5400_bulk_command_write': hp5400_sanei.c:345: warning: passing arg 3 of `sanei_usb_write_bulk' from incompatible pointer type hp5400.c: In function `attach_one_device': hp5400.c:432: warning: passing arg 1 of `HP5400Detect' discards qualifiers from pointer target type /usr/include/stdio.h: At top level: hp5400_sanei.c:253: warning: `hp5400_bulk_read' defined but not used hp5400_sanei.c:361: warning: `hp5400_isOn' defined but not used hp5400_internal.c:605: warning: `DecodeImage' defined but not used hp5400_internal.c:661: warning: `hp5400_test_scan_response' defined but not used hp5400_internal.c:975: warning: `PreviewScan' defined but not used hp5400_internal.c:1013: warning: `InitScanner' defined but not used rm -f hp5400-s.c ln -s ./stubs.c hp5400-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=hp5400 hp5400-s.c -fno-common -DPIC -o .libs/hp5400-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-hp5400.1.0.12.so .libs/hp5400.o .libs/hp5400-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o ../sanei/.libs/sanei_usb.o ../sanei/.libs/sanei_config2.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-hp5400.1.so && ln -s libsane-hp5400.1.0.12.so libsane-hp5400.1.so) (cd .libs && rm -f libsane-hp5400.so && ln -s libsane-hp5400.1.0.12.so libsane-hp5400.so) creating libsane-hp5400.la (cd .libs && rm -f libsane-hp5400.la && ln -s ../libsane-hp5400.la libsane-hp5400.la) rm -f dll-preload.c list=""; for be in $list; do \ echo "PRELOAD_DECL($be)" >> dll-preload.c; \ done echo "static struct backend preloaded_backends[] = {" >> dll-preload.c sep=""; \ list=""; \ if test -z "${list}"; then \ echo { 0, 0, 0, 0, 0, 0, {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }} >> dll-preload.c; \ else \ for be in $list; do \ echo "${sep}PRELOAD_DEFN($be)" >> dll-preload.c; \ sep=","; \ done; \ fi echo "};" >> dll-preload.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=dll -DLIBDIR=/usr/local/lib/sane dll.c -fno-common -DPIC -o .libs/dll.o dll.c: In function `load': dll.c:418: warning: `op' might be used uninitialized in this function rm -f dll-s.c ln -s ./stubs.c dll-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=dll dll-s.c -fno-common -DPIC -o .libs/dll-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-dll.1.0.12.so .libs/dll.o .libs/dll-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-dll.1.so && ln -s libsane-dll.1.0.12.so libsane-dll.1.so) (cd .libs && rm -f libsane-dll.so && ln -s libsane-dll.1.0.12.so libsane-dll.so) creating libsane-dll.la (cd .libs && rm -f libsane-dll.la && ln -s ../libsane-dll.la libsane-dll.la) gcc -dynamiclib -flat_namespace -undefined suppress -o .libs/libsane.1.0.12.dylib .libs/dll.o .libs/dll-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit -install_name /usr/local/lib/libsane.1.dylib -compatibility_version 2 -current_version 2.12 (cd .libs && rm -f libsane.1.dylib && ln -s libsane.1.0.12.dylib libsane.1.dylib) (cd .libs && rm -f libsane.dylib && ln -s libsane.1.0.12.dylib libsane.dylib) creating libsane.la (cd .libs && rm -f libsane.la && ln -s ../libsane.la libsane.la) making all in frontend gcc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I/usr/local/include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -g -O2 -W -Wall scanimage.c scanimage.c: In function `scan_it': scanimage.c:1020: warning: unused variable `hang_over' gcc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I/usr/local/include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -g -O2 -W -Wall stiff.c mkdir .libs gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a ../backend/.libs/libsane.dylib /usr/local/lib/libusb.dylib -lIOKit -lm -framework CoreFoundation -framework IOKit ld: multiple definitions of symbol _getopt /usr/lib/libm.dylib(getopt.So) definition of _getopt ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text) ld: multiple definitions of symbol _opterr /usr/lib/libm.dylib(getopt.So) definition of _opterr ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data) ld: multiple definitions of symbol _optind /usr/lib/libm.dylib(getopt.So) definition of _optind ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data) ld: multiple definitions of symbol _optopt /usr/lib/libm.dylib(getopt.So) definition of _optopt ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data) make[1]: *** [scanimage] Error 1 make: *** [all-recursive] Error 1 --0-1698544750-1056197588=:12806-- From henning@meier-geinitz.de Sat Jun 21 13:52:53 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 21 Jun 2003 14:52:53 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF357AE.4090104@gmx.net> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> <3EF2160E.2090603@gmx.net> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> Message-ID: <20030621125253.GC9347@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 08:51:26PM +0200, abel deuring wrote: > Henning Meier-Geinitz schrieb: > > >I'm not volunteering :-) but I can at least test if any of your > >patches break Mustek scanners on FreeBSD. > > Great. I've already sent a patch to Martin, and it seems to fix the > problems with the Microtek Scanamker II. Attached is the proposed new > version (with Martin's fixes of my typos) of sanei_scsi_cmd2 for > FreeBSD/CAM. It should replace the function near line 2765 in sanei_scsi.c. Ok. I haven't tested FreeBSD with older scanners for some time so here are my results with Mustek SCSI scanners (symbios-compatible 810 SCSI controller, FreeBSD 5.0, sym driver): Scanner 1.0.12 your patch ------------------------------------------------------------------------ ScanExpress 6000 SP (relatively new) ok ok Paragon 1200 SP Pro (relatively new) detected, same but timeout Paragon 12000 SP (older) not detected not detected Paragon 12000 CX (stone age three-pass) not detected not detected If I try to use the "ncr" driver instead of "sym", FreeBSD doesn't even boot. With a Tekram 315 controller the results are the same as above. So your patch is ok but FreeBSD 5.0 is unusable with older Mustek scanners on at least these controllers. The scanners work just fine on Linux. The timeout with the Paragon 1200 SP Pro occurs when the lamp warms up that warm-up can take upto about 70 seconds. With Linux and the later SANE versiosn that's not a problem but FreeBSD seems to ignore the 120 seconds timeout. When the lamp is warm, the scan starts ok but sounds horribly and never finishes. No idea why, but this also happens without your patch. The "not-detection" looks like this: Booting FreeBSD stops and the scanner LED starts blinking. Looks like the scanner gets sent an invalid command from the kernel. If I turn off the scanner, FreeBSD boots. When I run "camcontrol rescan all", the scanner blinks again and camcontrol freezes. If I remember correctly, the old scanners worked once with FreeBSD. So maybe 5.0 has broken the SCSI system? Bye, Henning From maddog@mir.com Sat Jun 21 13:53:58 2003 From: maddog@mir.com (Matto Marjanovic) Date: Sat, 21 Jun 2003 08:53:58 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF44BDE.4B306A98@satzbau-gmbh.de> (message from abel deuring on Sat, 21 Jun 2003 14:13:18 +0200) References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> Message-ID: <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> >> What does the patch do? (And how did it fix up the Microtek scanning?) ... >depending on the status returned by the OS. The sense handler is only >called, if ccb->ccb_h.status & CAM_AUTOSNS_VALID is true, which should >guarantee that useful sense data is available. ... >Without the patch, the sense handler of backend is called for every >failing command, but because no sense data is available, the sense >handler decides to return SANE_STATUS_GOOD, hence the backend makes >wrong assuptions about the status of the scanner. > >What I don't really understand in hindsight is the CAM status value 16 >in Martin's log data. It indicates that the FreeBSD CAM system tried to >issue a REQUEST SENSE for one or another failing command (where >"failing" means in this case that the scanner accepted the command, and >returned CHECK CONDITION), and that the REQUEST SENSE was not >successful. A-ha --- ok, the sense handler is not called, an error condition is returned, and then - I imagine - the retry logic in the backend takes over. With regards to the mystery status value: in this situation under Linux (i.e., the scanner is busy, won't accept next command), a REQUEST SENSE *is* issued and the scanner *does* respond to it. However, the returned data does not conform to SCSI-2. In particular, the bit defined by Microtek to mean "this is valid sense data" is the bit which, in SCSI-2, means "this is *not* valid sense data". Because of this, the mid-level Linux SCSI driver *zeros out* the sense data, yet still indicates that REQUEST SENSE has been issued. Thus the backend's sense handler is called with absolutely nothing and decides "No error". I suspect a similar thing is happening in the FreeBSD CAM system --- some midlevel driver is unnecessarily killing the sense data. Your patch checks to see if the system thought the sense data is/was valid, and since it was declared invalid, issues a general error instead. It's just a theory... (I've never tried nor read FreeBSD code), -matt m. From henning@meier-geinitz.de Sat Jun 21 13:57:41 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 21 Jun 2003 14:57:41 +0200 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621121308.13540.qmail@web41502.mail.yahoo.com> References: <20030621094705.GB9347@meier-geinitz.de> <20030621121308.13540.qmail@web41502.mail.yahoo.com> Message-ID: <20030621125741.GD9347@meier-geinitz.de> Hi, On Sat, Jun 21, 2003 at 05:13:08AM -0700, Brian D. Williams wrote: > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a ../backend/.libs/libsane.dylib /usr/local/lib/libusb.dylib -lIOKit -lm -framework CoreFoundation -framework IOKit > ld: multiple definitions of symbol _getopt > /usr/lib/libm.dylib(getopt.So) definition of _getopt > ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text) > ld: multiple definitions of symbol _opterr > /usr/lib/libm.dylib(getopt.So) definition of _opterr > ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data) > ld: multiple definitions of symbol _optind > /usr/lib/libm.dylib(getopt.So) definition of _optind > ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data) > ld: multiple definitions of symbol _optopt > /usr/lib/libm.dylib(getopt.So) definition of _optopt > ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data) Yeah, that's the already known multiple definition error. Some MacOS X users don't seem to get that error, some see it. No idea why. And, by the way, I have no idea why libm should define _getopt. Bye, Henning From a.deuring@satzbau-gmbh.de Sat Jun 21 15:31:27 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Sat, 21 Jun 2003 16:31:27 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF46C3F.A897D7C4@satzbau-gmbh.de> Matto Marjanovic wrote: > A-ha --- ok, the sense handler is not called, an error condition is returned, > and then - I imagine - the retry logic in the backend takes over. Right, I think that's happening. > > With regards to the mystery status value: in this situation under Linux > (i.e., the scanner is busy, won't accept next command), a REQUEST SENSE > *is* issued and the scanner *does* respond to it. However, the returned > data does not conform to SCSI-2. In particular, the bit defined by > Microtek to mean "this is valid sense data" is the bit which, in SCSI-2, > means "this is *not* valid sense data". > Because of this, the mid-level Linux SCSI driver *zeros out* the sense data, > yet still indicates that REQUEST SENSE has been issued. Thus the backend's > sense handler is called with absolutely nothing and decides "No error". > > I suspect a similar thing is happening in the FreeBSD CAM system --- some > midlevel driver is unnecessarily killing the sense data. Your patch checks > to see if the system thought the sense data is/was valid, and since it was > declared invalid, issues a general error instead. Matt, are you sure that the Linux SCSI system (or FreeBSD) tries to issue a REQUEST SENSE, if it can't "connect" to device? (If I find enough time, I'll try that at home today or tomorrow. Shouldn't be difficult to provoke such a situation with my Sharp JX250. Removing the O_EXCL flag on the open call for the device file, using huge data blocks for READ commands and then attepting to access the scanner form a different process are worth a try.) OK, a SCSI device should be able to respond to a few basic commands like INQUIRY or REQUEST SENSE under more or less any circumstances, but the main point of the error "can't issue a SCSI command, because the device is busy" is to try it again later. I don't see the point, which additional information a REQUEST SENSE would provide. It's another point, if a command has been accepted by the device. If this command results in an error, a REQUEST SENSE if of course useful. Abel From a.deuring@satzbau-gmbh.de Sat Jun 21 15:38:43 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Sat, 21 Jun 2003 16:38:43 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> <3EF2160E.2090603@gmx.net> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <20030621125253.GC9347@meier-geinitz.de> Message-ID: <3EF46DF3.78959F15@satzbau-gmbh.de> Henning Meier-Geinitz wrote: > Ok. I haven't tested FreeBSD with older scanners for some time so here > are my results with Mustek SCSI scanners (symbios-compatible 810 SCSI > controller, FreeBSD 5.0, sym driver): > > Scanner 1.0.12 your patch > ------------------------------------------------------------------------ > ScanExpress 6000 SP (relatively new) ok ok > Paragon 1200 SP Pro (relatively new) detected, same > but timeout > Paragon 12000 SP (older) not detected not detected > Paragon 12000 CX (stone age three-pass) not detected not detected > > If I try to use the "ncr" driver instead of "sym", FreeBSD doesn't > even boot. With a Tekram 315 controller the results are the same as > above. > > So your patch is ok but FreeBSD 5.0 is unusable with older Mustek > scanners on at least these controllers. The scanners work just fine on > Linux. But we have least no new problems ;) > > The timeout with the Paragon 1200 SP Pro occurs when the lamp warms up > that warm-up can take upto about 70 seconds. With Linux and the later > SANE versiosn that's not a problem but FreeBSD seems to ignore the 120 > seconds timeout. When the lamp is warm, the scan starts ok but sounds > horribly and never finishes. No idea why, but this also happens > without your patch. > > The "not-detection" looks like this: Booting FreeBSD stops and the > scanner LED starts blinking. Looks like the scanner gets sent an > invalid command from the kernel. If I turn off the scanner, FreeBSD > boots. When I run "camcontrol rescan all", the scanner blinks again > and camcontrol freezes. > > If I remember correctly, the old scanners worked once with FreeBSD. So > maybe 5.0 has broken the SCSI system? It could be that it does not like older, very slow SCSI devices. IIRC, some Linux SCSI adapter drivers could not detect the Scanmaker II during a modprobe. The problem was that the scanner was too busy after a bus reset that it did not respond to the typoical INQUIRY. A later "echo scsi add-single-device ..." fixed that. Abel From brian_d_w@yahoo.com Sat Jun 21 17:04:34 2003 From: brian_d_w@yahoo.com (Brian D. Williams) Date: Sat, 21 Jun 2003 09:04:34 -0700 (PDT) Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621125741.GD9347@meier-geinitz.de> Message-ID: <20030621160434.54189.qmail@web41502.mail.yahoo.com> Hi, Thanks for having a look at that. Could I remove the offending define(s)? Brian --- Henning Meier-Geinitz wrote: > Hi, > > On Sat, Jun 21, 2003 at 05:13:08AM -0700, Brian D. Williams wrote: > > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a > ../backend/.libs/libsane.dylib /usr/local/lib/libusb.dylib -lIOKit -lm > -framework CoreFoundation -framework IOKit > > ld: multiple definitions of symbol _getopt > > /usr/lib/libm.dylib(getopt.So) definition of _getopt > > ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text) > > ld: multiple definitions of symbol _opterr > > /usr/lib/libm.dylib(getopt.So) definition of _opterr > > ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data) > > ld: multiple definitions of symbol _optind > > /usr/lib/libm.dylib(getopt.So) definition of _optind > > ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data) > > ld: multiple definitions of symbol _optopt > > /usr/lib/libm.dylib(getopt.So) definition of _optopt > > ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data) > > Yeah, that's the already known multiple definition error. Some MacOS X > users don't seem to get that error, some see it. No idea why. > And, by the way, I have no idea why libm should define _getopt. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel ===== Brian Williams homepage == From horst.schlonz@gmx.de Sat Jun 21 17:14:23 2003 From: horst.schlonz@gmx.de (horst.schlonz@gmx.de) Date: Sat, 21 Jun 2003 18:14:23 +0200 Subject: [sane-devel] mustek scanexpress 6000 p does not work anymore Message-ID: <200306211814.24072.horst.schlonz@gmx.de> i searched the archives for this issue to no avail. my se 6000p always worked with this mustek_pp.conf: name SE-6000P vendor Mustek option wait-lamp 15 apparently the syntax of mustek_pp.conf changed in recent versions of sane. there are some examples in the new mustek_pp.conf: # Uncomment/customize to your needs # # scanner Mustek-600CP 0x378 cis600 # scanner Mustek-1200CP 0x378 cis1200 # scanner Mustek-1200CP+ 0x378 cis1200+ but none of these fits to my se 6000p. according to this site http://www.penguin-breeder.org/sane/mustek_pp/#supported%20scanners ccd-scanners are not working any more. nice... they say i have to use sane <= 10.0.9. is think, they meant 1.0.9, so i compiled, installed an configured sane-backends 1.0.9 and sane-frontends 1.0.9. it's no use: # cat /usr/local/etc/sane.d/dll.conf mustek_pp # cat /usr/local/etc/sane.d/mustek_pp.conf option io-mode alt_lock option niceload port 0x378 name SE-6000P vendor Mustek option wait-lamp 15 # SANE_DEBUG_MUSTEK_PP=128 scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). root@sputnik:/home/headroom/Desktop/sane-frontends-1.0.9# can anybody please help me with this? i need to scan urgently. From peter@pscomp.com Sat Jun 21 18:22:07 2003 From: peter@pscomp.com (Peter Santoro) Date: Sat, 21 Jun 2003 13:22:07 -0400 Subject: [sane-devel] scheme interface for sane? Message-ID: <3EF4943F.2050102@pscomp.com> I'm currently using sane via scanimage and scanadf from scheme. If anyone has written a scheme extension/interface (preferably mzscheme) for sane or managed to call it from some ffi, I would appreciate hearing about it. Thank you, Peter From kmoffat@drizzle.com Sat Jun 21 18:59:44 2003 From: kmoffat@drizzle.com (Ken Moffat) Date: Sat, 21 Jun 2003 10:59:44 -0700 Subject: [sane-devel] WinXP problem Message-ID: <3EF49D10.2020804@drizzle.com> New user, first posting, probably just brainfade, but here's my problem: I use xsane on linux (libranet, a debian derivative) with an Epson 1660 scanner, and just installed xsane on WinXP on my home network. I have sane serving from libranet, and it works well from my other linux (debian 3.0) box. However, on WinXP I get errors about not being able to create temp files; many errors on startup, get preview and shutdown. This is true with unprivileged users on XP, but with a privileged user all is working. Does anyone have a fix? or is this just an out-of-luck on XP condition? (I don't wish to make my teenagers privileged if I can help it! ;-) ) -- Ken From tang@mac.com Sat Jun 21 20:00:39 2003 From: tang@mac.com (Dino Tang) Date: Sat, 21 Jun 2003 12:00:39 -0700 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621091456.81112.qmail@web41501.mail.yahoo.com> Message-ID: Hi Brian, You have the latest system, but you might not have the latest tool set. You can open the Project Builder and use the "About Project Builder" to find out what version you have. If it doesn't say "Version 2.1 (December 2002 Developer Tools)", you don't have the latest tool set. You can download the latest tools from the ADC ( Apple Developer Connection ) site. The "multiple symbol defined" problem has to do with the way you compile libusb. Mattias Ellert has sent me the following explanation and patch awhile back. Cheers! --Dino --- beginning Mattias's message --- If you get that error even when linking against libusb, I guess you didn't patch the libusb before compiling it. The attached patch should be applied to libusb before compiling. It does build without the patch, but the configure script cheats a bit and links frameworks as libraries, so the dependencies don't get recorded correctly in the libraries. This means that when you compile something that depends on libusb you might get into trouble -- as you did. Since the libusb patch changes some autoconf/automake files you need to rerun those. My build instructions for libusb are as follows. (The --disable-static is optional of course.) In this way you get a library with the correct dependencies recorded. tar -z -x -f libusb-0.1.7.tar.gz patch -p0 < frameworks.patch cd libusb-0.1.7 # Remove 'missing' in order to avoid warning about it being old during configure. # A newer version will be installed by automake. rm missing aclocal automake --add-missing autoconf ./configure --disable-static make Mattias PS. I have sent the patch to the maintainer of libusb, so it might be included in the next official release if it is accepted. The SANE prerelease already has the corresponding patch included. diff -ur libusb-0.1.7.orig/Makefile.am libusb-0.1.7/Makefile.am --- libusb-0.1.7.orig/Makefile.am Mon Nov 11 19:04:15 2002 +++ libusb-0.1.7/Makefile.am Sun Mar 2 15:59:42 2003 @@ -28,7 +28,7 @@ if DARWIN_API OS_SUPPORT = darwin.c CFLAGS_EXT = -no-cpp-precomp -LDADDS = -lIOKit -framework "CoreFoundation" +LDADDS = -framework IOKit -framework CoreFoundation else OS_SUPPORT = endif diff -ur libusb-0.1.7.orig/configure.in libusb-0.1.7/configure.in --- libusb-0.1.7.orig/configure.in Sun Nov 17 19:45:15 2002 +++ libusb-0.1.7/configure.in Sun Mar 2 15:59:42 2003 @@ -11,7 +11,8 @@ dnl we need to AC_DIVERT_PUSH/AC_DIVERT_POP these variable definitions so they dnl are available for $ac_help expansion (don't we all *love* autoconf?) -AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)dnl +ifdef([AC_DIVERSION_NOTICE], [AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)], + [AC_DIVERT_PUSH(NOTICE)]) # # The following version number definitions apply to libusb @@ -76,7 +77,8 @@ dnl Initialize maintainer mode AM_MAINTAINER_MODE -AC_CANONICAL_HOST +dnl This has already been dragged in by AM_PROG_LIBTOOL +dnl AC_CANONICAL_HOST AC_MSG_CHECKING(for what USB OS support) case $host in @@ -99,7 +101,7 @@ AC_SUBST(DARWIN_API) os_support=darwin AC_MSG_RESULT(Darwin and/or MacOS 10) - OSLIBS="-lIOKit" + OSLIBS="-framework IOKit" ;; esac @@ -111,7 +113,8 @@ dnl figure debugging default, prior to $ac_help setup dnl -AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)dnl +ifdef([AC_DIVERSION_NOTICE], [AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)], + [AC_DIVERT_PUSH(NOTICE)]) if test `expr $LIBUSB_MINOR_VERSION \% 2` = 1 ; then debug_default=yes else diff -ur libusb-0.1.7.orig/ltmain.sh libusb-0.1.7/ltmain.sh --- libusb-0.1.7.orig/ltmain.sh Wed Mar 27 20:10:10 2002 +++ libusb-0.1.7/ltmain.sh Sun Mar 2 15:59:42 2003 @@ -887,6 +887,11 @@ prev= continue ;; + framework) + deplibs="$deplibs -framework $arg" + prev= + continue + ;; release) release="-$arg" prev= @@ -988,6 +993,11 @@ continue ;; + -framework) + prev=framework + continue + ;; + # The native IRIX linker understands -LANG:*, -LIST:* and -LNO:* # so, if we see these flags be careful not to treat them like -L -L[A-Z][A-Z]*:*) @@ -1378,10 +1388,37 @@ link) libs="$deplibs %DEPLIBS% $dependency_libs" ;; esac fi + prev= for deplib in $libs; do + case $prev in + "") ;; + framework) + prev= + if test $linkmode = oldlib && test $linkmode = obj; then + $echo "$modename: warning: \`-framework' is ignored for archives/objects: $deplib" 1>&2 + continue + fi + if test $pass = conv; then + deplibs="-framework $deplib $deplibs" + continue + fi + if test "$linkmode,$pass" = "prog,link"; then + compile_deplibs="-framework $deplib $compile_deplibs" + finalize_deplibs="-framework $deplib $finalize_deplibs" + else + deplibs="-framework $deplib $deplibs" + test $linkmode = lib && newdependency_libs="-framework $deplib $newdependency_libs" + fi + continue + ;; + esac lib= found=no case $deplib in + -framework) + prev=framework + continue + ;; -l*) if test "$linkmode" = oldlib && test "$linkmode" = obj; then $echo "$modename: warning: \`-l' is ignored for archives/objects: $deplib" 1>&2 @@ -1553,12 +1590,35 @@ convenience="$convenience $ladir/$objdir/$old_library" old_convenience="$old_convenience $ladir/$objdir/$old_library" tmp_libs= + prev= for deplib in $dependency_libs; do - deplibs="$deplib $deplibs" - case "$tmp_libs " in - *" $deplib "*) specialdeplibs="$specialdeplibs $deplib" ;; + case $deplib in + -framework) + prev=framework + continue + ;; + *) + case $prev in + framework) + deplibs="-framework $deplib $deplibs" + case "$tmp_libs " in + *" $deplib "*) + specialdeplibs="$specialdeplibs -framework $deplib" ;; + esac + tmp_libs="$tmp_libs -framework $deplib" + ;; + *) + deplibs="$deplib $deplibs" + case "$tmp_libs " in + *" $deplib "*) + specialdeplibs="$specialdeplibs $deplib" ;; + esac + tmp_libs="$tmp_libs $deplib" + ;; + esac + ;; esac - tmp_libs="$tmp_libs $deplib" + prev= done elif test "$linkmode" != prog && test "$linkmode" != lib; then $echo "$modename: \`$lib' is not a convenience library" 1>&2 @@ -1668,22 +1728,34 @@ fi tmp_libs= + prev= for deplib in $dependency_libs; do case $deplib in + -framework) + prev=framework + continue + ;; -L*) newlib_search_path="$newlib_search_path "`$echo "X$deplib" | $Xsed -e 's/^-L//'`;; ### testsuite: skip nested quoting test esac # Need to link against all dependency_libs? if test "$linkalldeplibs" = yes; then - deplibs="$deplib $deplibs" + case $prev in + framework) deplibs="-framework $deplib $deplibs" ;; + *) deplibs="$deplib $deplibs" ;; + esac else # Need to hardcode shared library paths # or/and link against static libraries - newdependency_libs="$deplib $newdependency_libs" + case $prev in + framework) newdependency_libs="-framework $deplib $newdependency_libs" ;; + *) newdependency_libs="$deplib $newdependency_libs" ;; + esac fi case "$tmp_libs " in *" $deplib "*) specialdeplibs="$specialdeplibs $deplib" ;; esac tmp_libs="$tmp_libs $deplib" + prev= done # for deplib continue fi # $linkmode = prog... @@ -1979,12 +2051,35 @@ test "$link_static" = no && newdependency_libs="$abs_ladir/$laname $newdependency_libs" # ... and its dependency_libs tmp_libs= + prev= for deplib in $dependency_libs; do - newdependency_libs="$deplib $newdependency_libs" - case "$tmp_libs " in - *" $deplib "*) specialdeplibs="$specialdeplibs $deplib" ;; + case $deplib in + -framework) + prev=framework + continue + ;; + *) + case $prev in + framework) + newdependency_libs="-framework $deplib $newdependency_libs" + case "$tmp_libs " in + *" $deplib "*) + specialdeplibs="$specialdeplibs -framework $deplib" ;; + esac + tmp_libs="$tmp_libs -framework $deplib" + ;; + *) + newdependency_libs="$deplib $newdependency_libs" + case "$tmp_libs " in + *" $deplib "*) + specialdeplibs="$specialdeplibs $deplib" ;; + esac + tmp_libs="$tmp_libs $deplib" + ;; + esac + ;; esac - tmp_libs="$tmp_libs $deplib" + prev= done if test "$link_all_deplibs" != no; then @@ -2032,8 +2127,21 @@ done # for deplib in $libs if test "$pass" = dlpreopen; then # Link the dlpreopened libraries before other libraries + prev= for deplib in $save_deplibs; do - deplibs="$deplib $deplibs" + case $deplib in + -framework) + prev=framework + continue + ;; + *) + case $prev in + framework) deplibs="-framework $deplib $deplibs" ;; + *) deplibs="$deplib $deplibs" ;; + esac + ;; + esac + prev= done fi if test "$pass" != dlopen; then @@ -2059,21 +2167,37 @@ # Add libraries to $var in reverse order eval tmp_libs=\"\$$var\" new_libs= + prev= for deplib in $tmp_libs; do case $deplib in + -framework) + prev=framework + continue + ;; -L*) new_libs="$deplib $new_libs" ;; *) case " $specialdeplibs " in - *" $deplib "*) new_libs="$deplib $new_libs" ;; + *" $deplib "*) + case $prev in + framework) new_libs="-framework $deplib $new_libs" ;; + *) new_libs="$deplib $new_libs" ;; + esac + ;; *) case " $new_libs " in *" $deplib "*) ;; - *) new_libs="$deplib $new_libs" ;; + *) + case $prev in + framework) new_libs="-framework $deplib $new_libs" ;; + *) new_libs="$deplib $new_libs" ;; + esac + ;; esac ;; esac ;; esac + prev= done tmp_libs= for deplib in $new_libs; do --- ending Mattias's message --- On Saturday, June 21, 2003, at 02:14 AM, Brian D. Williams wrote: > I have been trying to get sane to work with the epson perfection 660. > I could > build sane with 1.0.11 but not with the snapscan addition. I could not > build > 1.0.12 at all. It would stop building at when trying to make scanimage > but I > didn't see any error messages that made sense to me. I am running the > latest os > x (10.2.6). Sadly I don't have a scanner available (other than the > epson) to > test against. Any suggestions would be greatly appreciated. > > Brian From tang@mac.com Sat Jun 21 20:05:54 2003 From: tang@mac.com (Dino Tang) Date: Sat, 21 Jun 2003 12:05:54 -0700 Subject: [sane-devel] Problem building on OSX Message-ID: <61F1E17F-A41B-11D7-8041-00039357FFB6@mac.com> > The backends have no idea about image formats except the sane-internal > "format", so it is unlikely that this is a problem of the Canon > backend. > Does scanimage --format=tiff works with other scanners and the same > Sane > installation? > This is what I expect. The --format=tiff option works fine on the other backends. I only run into problem with the canon backend. --Dino From anoah@pfeiffer.edu Sat Jun 21 20:53:31 2003 From: anoah@pfeiffer.edu (m. allan noah) Date: Sat, 21 Jun 2003 15:53:31 -0400 (EDT) Subject: [sane-devel] scanimage and scanadf command line args In-Reply-To: <3EF3A0C9.1090907@pscomp.com> Message-ID: the options you are discussing are backend specific. with no scanner attached to the machine, if you run scanimage --help and scanadf --help, you will see nothing about scanning options, only input and output file, and file format. the threshold and paper size options are provided by the scanner backend, so if they malfunction, it is probably my fujitsu 4120 code :) the fact that one of them works, but is hidden, perhaps is because that option is set to SANE_CAP_ADVANCED, which hides it from most users (try using xsane, you will see the advanced option in menu, iirc). allan On Fri, 20 Jun 2003, Peter Santoro wrote: > My application makes use of scanimage and scanadf (sane 1.0.12 backend and 1.0.11 frontend) and it appears that there > are a few inconsistencies with respect to the command line args of these sane front-ends. > > For instance, when using my fujitsu fi-4120c, "scanadf --help" shows that there is a "--paper_size" option available. > Actually, it needs to be entered as "paper_size". Also, there is no "--threshold" option listed on the help screen, but > it can be entered and it does appear to work correctly. There are other apparent inconsistencies I've run across > using scanimage, but I don't remember them now. > > None of these issues are a big deal, but I was wondering if I was missing something here. > > Thanks for your help, > > Peter > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From oliver.rauch@rauch-domain.de Sat Jun 21 21:26:11 2003 From: oliver.rauch@rauch-domain.de (Oliver Rauch) Date: Sat, 21 Jun 2003 22:26:11 +0200 Subject: [sane-devel] WinXP problem In-Reply-To: <3EF49D10.2020804@drizzle.com> References: <3EF49D10.2020804@drizzle.com> Message-ID: <200306212226.11105.oliver.rauch@rauch-domain.de> I am using xsane-win32 on winxp as non privileged user. Don`t ask me the exact settings. May be it is necessary to make the user a "Main User" (in German "Hauptbenuter", I am not sure about the exact keyword for the english version). Oliver On Saturday 21 June 2003 19:59, Ken Moffat wrote: > New user, first posting, probably just brainfade, but here's my problem= : > > I use xsane on linux (libranet, a debian derivative) with an Epson 1660 > scanner, and just installed xsane on WinXP on my home network. I have > sane serving from libranet, and it works well from my other linux > (debian 3.0) box. However, on WinXP I get errors about not being able t= o > create temp files; many errors on startup, get preview and shutdown. > This is true with unprivileged users on XP, but with a privileged user > all is working. > Does anyone have a fix? or is this just an out-of-luck on XP condition? > (I don't wish to make my teenagers privileged if I can help it! ;-) ) --=20 http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:Oliver.Rauch@Rauch-Domain.DE From peter@pscomp.com Sat Jun 21 23:30:49 2003 From: peter@pscomp.com (Peter Santoro) Date: Sat, 21 Jun 2003 18:30:49 -0400 Subject: [sane-devel] scanimage and scanadf command line args In-Reply-To: References: Message-ID: <3EF4DC99.9040503@pscomp.com> m. allan noah wrote: >the options you are discussing are backend specific. > >with no scanner attached to the machine, if you run scanimage --help and >scanadf --help, you will see nothing about scanning options, only input >and output file, and file format. > >the threshold and paper size options are provided by the scanner backend, >so if they malfunction, it is probably my fujitsu 4120 code :) > >the fact that one of them works, but is hidden, perhaps is because that >option is set to SANE_CAP_ADVANCED, which hides it from most users (try >using xsane, you will see the advanced option in menu, iirc). > >allan > >On Fri, 20 Jun 2003, Peter Santoro wrote: > > > >>My application makes use of scanimage and scanadf (sane 1.0.12 backend and 1.0.11 frontend) and it appears that there >>are a few inconsistencies with respect to the command line args of these sane front-ends. >> >>For instance, when using my fujitsu fi-4120c, "scanadf --help" shows that there is a "--paper_size" option available. >>Actually, it needs to be entered as "paper_size". Also, there is no "--threshold" option listed on the help screen, but >> it can be entered and it does appear to work correctly. There are other apparent inconsistencies I've run across >>using scanimage, but I don't remember them now. >> >>None of these issues are a big deal, but I was wondering if I was missing something here. >> >>Thanks for your help, >> >>Peter >> >>_______________________________________________ >>Sane-devel mailing list >>Sane-devel@www.mostang.com >>http://www.mostang.com/mailman/listinfo/sane-devel >> >> >> > > > Thanks again, Allan. I appreciate your patience for those of us who are new to the sane code base. Peter From henning@meier-geinitz.de Sat Jun 21 23:36:13 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 22 Jun 2003 00:36:13 +0200 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621160434.54189.qmail@web41502.mail.yahoo.com> References: <20030621125741.GD9347@meier-geinitz.de> <20030621160434.54189.qmail@web41502.mail.yahoo.com> Message-ID: <20030621223613.GE9347@meier-geinitz.de> Hi, On Sat, Jun 21, 2003 at 09:04:34AM -0700, Brian D. Williams wrote: > Thanks for having a look at that. Could I remove the offending define(s)? It's not a problem of an offending define. liblib.a uses _getopt internally. libm (?) also uses _getopt. Usually that's not a problem but your system tools (linker) don't seem too like it for some reason. Bye, Henning From henning@meier-geinitz.de Sat Jun 21 23:45:20 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 22 Jun 2003 00:45:20 +0200 Subject: [sane-devel] scanimage and scanadf command line args In-Reply-To: <3EF3A0C9.1090907@pscomp.com> References: <3EF3A0C9.1090907@pscomp.com> Message-ID: <20030621224520.GF9347@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 08:03:21PM -0400, Peter Santoro wrote: > My application makes use of scanimage and scanadf (sane 1.0.12 backend and > 1.0.11 frontend) and it appears that there are a few inconsistencies with > respect to the command line args of these sane front-ends. Does scanadf do anything for you that scanimage can't? scanadf is a spin-off of scanimage but scanimage had some improvements after that. So there may be some differences. > For instance, when using my fujitsu fi-4120c, "scanadf --help" shows that > there is a "--paper_size" option available. Actually, it needs to be > entered as "paper_size". I think that's a bug in the fujitsu backend. The SANE standard says: "The option name must consist of lower-case ASCII letters (a--z), digits (0--9), or the dash character (-) only." So the underscaore "_" is not allowed. > Also, there is no "--threshold" option listed on > the help screen, but it can be entered and it does appear to work > correctly. There is an option called "threshold_curve" in the current fujitsu backend. The same comment about the "_" applies. However, I'm not sure if this does influence the handling of scanimage/scanadf. > There are other apparent inconsistencies I've run across using > scanimage, but I don't remember them now. When you come across them again, please show them to us. Bye, Henning From jonesrf1@qwest.net Sun Jun 22 01:13:04 2003 From: jonesrf1@qwest.net (Randolph Jones) Date: Sat, 21 Jun 2003 17:13:04 -0700 Subject: [sane-devel] page orientation for adfHow do I set my scanner Message-ID: <3EF4F490.5080109@qwest.net> how do i set my SP15c adf to scan from the bottom of the page? The default requires me to put tje page in face down and head in. If the stack has been stapled the edges are damaged. Scanning from the bottom would vaoid this problem, but I will get a mass of upside down images. TIA rfjones From horst.schlonz@gmx.de Sun Jun 22 02:56:10 2003 From: horst.schlonz@gmx.de (horst.schlonz@gmx.de) Date: Sun, 22 Jun 2003 03:56:10 +0200 Subject: [sane-devel] mustek scanexpress 6000 p does not work anymore In-Reply-To: <20030621220446.1e6eec09.jochen@penguin-breeder.org> References: <200306211814.24072.horst.schlonz@gmx.de> <20030621220446.1e6eec09.jochen@penguin-breeder.org> Message-ID: <200306220356.10480.horst.schlonz@gmx.de> Am Samstag, 21. Juni 2003 22:04 schrieben Sie: > > # cat /usr/local/etc/sane.d/dll.conf > > mustek_pp > > > > # cat /usr/local/etc/sane.d/mustek_pp.conf > > option io-mode alt_lock > > option niceload > > port 0x378 > > name SE-6000P > > vendor Mustek > > option wait-lamp 15 > > > > # SANE_DEBUG_MUSTEK_PP=128 scanimage -L > > do you still have the old libraries installed? from that output, the > mustek_pp backend isn't even loaded. > > make sure there is no other conflicting version of sane on your system. > you can also try SANE_DEBUG_DLL=128 to see what the dll backend does. you were right, i uninstalled all sane-packages but i surveyed the libsane-package. now i have uninstalled all saneish packages plus my manually compiled sane and installed sane 1.0.7 and libsane 1.0.7 from debain stable (i am on unstable). the scanner now works. thank you. you saved my ass. From pjh@coastal.net.au Sun Jun 22 09:01:48 2003 From: pjh@coastal.net.au (Peter Howard) Date: 22 Jun 2003 18:01:48 +1000 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621125741.GD9347@meier-geinitz.de> References: <20030621094705.GB9347@meier-geinitz.de> <20030621121308.13540.qmail@web41502.mail.yahoo.com> <20030621125741.GD9347@meier-geinitz.de> Message-ID: <1056268909.1528.0.camel@pig> On Sat, 2003-06-21 at 22:57, Henning Meier-Geinitz wrote: > Yeah, that's the already known multiple definition error. Some MacOS X > users don't seem to get that error, some see it. No idea why. > And, by the way, I have no idea why libm should define _getopt. > As covered earlier in this thread, updating to the December 02 Developer Tools fixed the problem for me. Note, the interim update (IIRC October) still had the problem. PJH From a.deuring@satzbau-gmbh.de Sun Jun 22 13:00:02 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Sun, 22 Jun 2003 14:00:02 +0200 Subject: [sane-devel] page orientation for adfHow do I set my scanner In-Reply-To: <3EF4F490.5080109@qwest.net> References: <3EF4F490.5080109@qwest.net> Message-ID: <3EF59A42.2040002@gmx.net> Randolph Jones schrieb: > how do i set my SP15c adf to scan from the bottom of the page? > The default requires me to put tje page in face down and head in. > If the stack has been stapled the edges are damaged. > Scanning from the bottom would vaoid this problem, but I will get a mass > of upside down images. AFAIK, scanimage and scanadf don't have options to rotate the resulting image. But you can Imagemagick or some PNM tools to rotate, mirror or otherwise modify the image files produced by scanimage / scanadf. Abel From nakal@web.de Sun Jun 22 14:52:07 2003 From: nakal@web.de (Nakal) Date: Sun, 22 Jun 2003 15:52:07 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <20030621125253.GC9347@meier-geinitz.de> References: <200306102317.58064.nakal@web.de> <3EF357AE.4090104@gmx.net> <20030621125253.GC9347@meier-geinitz.de> Message-ID: <200306221552.07583.nakal@web.de> On Saturday 21 June 2003 14:52, Henning Meier-Geinitz wrote: > If I try to use the "ncr" driver instead of "sym", FreeBSD doesn't > even boot. With a Tekram 315 controller the results are the same as > above. ncr driver is old, you should not use it. As far as I know, sym should support everything which ncr supported earlier. Compare the manpages sym(4) and ncr(4). > So your patch is ok but FreeBSD 5.0 is unusable with older Mustek > scanners on at least these controllers. The scanners work just fine > on Linux. Please use 5.1 instead. > If I remember correctly, the old scanners worked once with FreeBSD. > So maybe 5.0 has broken the SCSI system? On 5.1 it's working fine. I can scan for all backends (scanimage -L). On FreeBSD 4.8 "scanimage -L" is freezing my PC. FreeBSD 5.1 is lots better, in my opinion. The patch works for both FreeBSD 4.8 (aka stable) and FreeBSD 5.1 (aka current). Martin From maddog@mir.com Sun Jun 22 17:39:13 2003 From: maddog@mir.com (Matto Marjanovic) Date: Sun, 22 Jun 2003 12:39:13 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF46C3F.A897D7C4@satzbau-gmbh.de> (message from abel deuring on Sat, 21 Jun 2003 16:31:27 +0200) References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> <3EF46C3F.A897D7C4@satzbau-gmbh.de> Message-ID: <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> Hi, Abel, >are you sure that the Linux SCSI system (or FreeBSD) tries to issue a >REQUEST SENSE, if it can't "connect" to device? (If I find enough time, I'm not exactly sure what is going on in this particular situation. Last winter, a user (Shawn Rutledge) was really helpful in tracking down lost sense codes. The backend sense handler was getting called with all zeros, as here. By slogging through debug output from the driver for the SCSI card in the kernel logs, it was apparent that the REQUEST SENSE was indeed issued. I then dug into the mid-level scsi driver and found at least one place where the results were being thrown away. The moral to the story is that I don't trust the error codes returned by the Linux SCSI system --- since it thinks that the results of the REQUEST SENSE are invalid, it decides that there must be some other problem. The trigger for this behavior is the peculiar sense codes from Microtek scanners. -matt m. From onymouse@garlic.com Sun Jun 22 19:24:12 2003 From: onymouse@garlic.com (jd) Date: Sun, 22 Jun 2003 11:24:12 -0700 Subject: [sane-devel] HP Scanjet 3P io errors Message-ID: <3EF5F44C.4020506@garlic.com> I found nothing related in the archives: Using sane front & back ends v1.0.7 Device is Scanjet 3P and ADF, model 2570A, firmware 3430. Connected to Buslogic BT946C. sane does not seem to like my scanner. It returns io device errors. Works fine with epson scanner. Using RedHat 7.3, latest & lastest updates. From dmesg: SCSI subsystem driver Revision: 1.00 kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 PCI: Found IRQ 11 for device 00:09.0 PCI: Sharing IRQ 11 with 00:0e.0 scsi: ***** BusLogic SCSI Driver Version 2.1.15 of 17 August 1998 ***** scsi: Copyright 1995-1998 by Leonard N. Zubkoff scsi0: Configuring BusLogic Model BT-946C PCI SCSI Host Adapter scsi0: Firmware Version: 4.28D, I/O Address: 0xA800, IRQ Channel: 11/Level scsi0: PCI Bus: 0, Device: 9, Address: Unassigned, Host Adapter SCSI ID: 7 scsi0: Parity Checking: Enabled, Extended Translation: Disabled scsi0: Synchronous Negotiation: Fast, Wide Negotiation: Disabled scsi0: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled scsi0: Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211 scsi0: Driver Queue Depth: 211, Host Adapter Queue Depth: 100 scsi0: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3 scsi0: Error Recovery Strategy: Default, SCSI Bus Reset: Enabled scsi0: SCSI Bus Termination: Enabled scsi0: *** BusLogic BT-946C Initialized Successfully *** scsi0 : BusLogic BT-946C Vendor: HP Model: C2570A Rev: 3430 Type: Processor ANSI SCSI revision: 02 scsi0: Target 0: Queue Depth 3, Asynchronous (Manually insmod'd scsi_hostadapter later. But it makes no difference whether it is loaded or not.) sane-find-scanner detects the device at /dev/sg0 sane -d hp:/dev/sg0 *(any command or option) returns "Error during device I/O" and the help page. THis occurs with or without option dumb-read From /etc/sane.d/hp.conf: (RedHat's default location) scsi hp option dumb-read /dev/sg0 From another form of hp.conf: scsi HP C2570A Processor 0 00 00 00 option connect-scsi option dumb-read hptool's hpinq returns the model number and firmware code but then returns nothing but io errors on stderr and "error in inquiry" for each command. This scanner works with windoze. I have no idea what is going on. Does anyone? Thanks... From brian_d_w@yahoo.com Sun Jun 22 20:59:38 2003 From: brian_d_w@yahoo.com (Brian D. Williams) Date: Sun, 22 Jun 2003 12:59:38 -0700 (PDT) Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <1056268909.1528.0.camel@pig> Message-ID: <20030622195938.38334.qmail@web41506.mail.yahoo.com> After getting the latest tools (dec2002) and getting the CVS versions of everything (sane, snapscan, libusb) it compiles. But it looks like I am stuck where everyone else has been getting stuck. Sane-find-scanner sees the scanner but I can't get scanimage to find it. I think that this is becoming not worth the effort. Has anyone gotten the epson perfection 660 and sane to work with os x? Thanks for the help everyone. Brian --- Peter Howard wrote: > On Sat, 2003-06-21 at 22:57, Henning Meier-Geinitz wrote: > > > Yeah, that's the already known multiple definition error. Some MacOS X > > users don't seem to get that error, some see it. No idea why. > > And, by the way, I have no idea why libm should define _getopt. > > > As covered earlier in this thread, updating to the December 02 Developer > Tools fixed the problem for me. Note, the interim update (IIRC October) > still had the problem. > > PJH > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel ===== Brian Williams homepage == From anoah@pfeiffer.edu Sun Jun 22 21:19:57 2003 From: anoah@pfeiffer.edu (m. allan noah) Date: Sun, 22 Jun 2003 16:19:57 -0400 (EDT) Subject: [sane-devel] page orientation for adfHow do I set my scanner In-Reply-To: <3EF4F490.5080109@qwest.net> Message-ID: you cant. use convert (part of ImageMagick) to '-flip -flop' or '-rotate 180' the images after you scan. allan On Sat, 21 Jun 2003, Randolph Jones wrote: > how do i set my SP15c adf to scan from the bottom of the page? > The default requires me to put tje page in face down and head in. > If the stack has been stapled the edges are damaged. > Scanning from the bottom would vaoid this problem, but I will get a mass > of upside down images. > > TIA > rfjones > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From a.deuring@satzbau-gmbh.de Sun Jun 22 21:25:13 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Sun, 22 Jun 2003 22:25:13 +0200 Subject: [sane-devel] HP Scanjet 3P io errors In-Reply-To: <3EF5F44C.4020506@garlic.com> References: <3EF5F44C.4020506@garlic.com> Message-ID: <3EF610A9.4080206@gmx.net> jd wrote: > I found nothing related in the archives: It' s a bit difficult to find ;) I needed a few minutes to search through my private mail archive to find the the answer. > > Using sane front & back ends v1.0.7 > > Device is Scanjet 3P and ADF, model 2570A, firmware 3430. > Connected to Buslogic BT946C. > > sane does not seem to like my scanner. It returns io device errors. > Works fine with epson scanner. In short: The combination Buslogic driver/Linux kernel 2.4/HP scanner does not work well. The longer explanation: For certain commands, the HP backend cannot predict the exact size of a data block returned for a certain SCSI command. If the scanner return less or more data than "declared" by the backend, the Buslogic driver raises an error and does not return any data. This data underrun/overrun is not an issue for most other scanners -- in general, the Sane backends can precisely predict the length of tha sent to/received from the scanner. The short conclusion: Use another SCSI adapter for the HP scanner. The longer conclusion: The Buslogic driver would need a new maintainer, who can continue the work of the late Leonard Zubkoff. Abel From Oliver.Schwartz@gmx.de Sun Jun 22 22:00:38 2003 From: Oliver.Schwartz@gmx.de (Oliver Schwartz) Date: Sun, 22 Jun 2003 23:00:38 +0200 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030622195938.38334.qmail@web41506.mail.yahoo.com> References: <20030622195938.38334.qmail@web41506.mail.yahoo.com> Message-ID: <200306222300.40706.Oliver.Schwartz@gmx.de> =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > After getting the latest tools (dec2002) and getting the CVS > versions of everything (sane, snapscan, libusb) it compiles. But it > looks like I am stuck where everyone else has been getting stuck. > Sane-find-scanner sees the scanner but I can't get scanimage to > find it. I think that this is becoming not worth the effort. Has > anyone gotten the epson perfection 660 and sane to work with os x? Please send me the output of "SANE_DEBUG_SNAPSCAN=3D255 scanimage -L".=20 Btw, the snapscan version in the SANE CVS archive is the most recent=20 version. There's no need to upgrade the snapscan backend from=20 Sourceforge anymore. =2D -Oliver =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+9hj2/V6sbrmfIuMRAtKaAJ9T6SSaR7ESgOT+9pwvEKtU1241VQCeKtUc 2lqzYdNhNaACZvI1appYWKU=3D =3Dz0WI =2D----END PGP SIGNATURE----- From a.deuring@satzbau-gmbh.de Sun Jun 22 23:50:56 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Mon, 23 Jun 2003 00:50:56 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> <3EF46C3F.A897D7C4@satzbau-gmbh.de> <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF632D0.7090102@gmx.net> Matt, > >are you sure that the Linux SCSI system (or FreeBSD) tries to issue a > >REQUEST SENSE, if it can't "connect" to device? (If I find enough time, > > I'm not exactly sure what is going on in this particular situation. > > Last winter, a user (Shawn Rutledge) was really helpful in tracking > down lost sense codes. The backend sense handler was getting called with > all zeros, as here. By slogging through debug output from the driver for > the SCSI card in the kernel logs, it was apparent that the REQUEST SENSE > was indeed issued. I then dug into the mid-level scsi driver and found > at least one place where the results were being thrown away. > > The moral to the story is that I don't trust the error codes returned by > the Linux SCSI system --- since it thinks that the results of the REQUEST > SENSE are invalid, it decides that there must be some other problem. > The trigger for this behavior is the peculiar sense codes from Microtek > scanners. OK, so we have indeed a flaw in the Linux SCSI system... I assume that the scanners identify themselves as SCSI 1 devices, where these short sense data blocks are normal. Did you try to issue REQUEST SENSE explicitly from the backend, where this looks reasonable? This may not work with every Linux adapter driver (IIRC, older versions of the aha152x driver did not like user land REQUEST SENSE commands), so it should be possible to turn them off with an option. cheers Abel From technomage-hawke@cox.net Mon Jun 23 05:24:16 2003 From: technomage-hawke@cox.net (technomage) Date: Sun, 22 Jun 2003 21:24:16 -0700 Subject: [sane-devel] any scanner drivers that will work with twian compliant digital cams? Message-ID: <200306222124.19391.technomage-hawke@cox.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 here's my rub, I have a vivtar brand vivcam-10. it has a usb port and works in windows (but I don;t have adaptive technology IN WINDOWS). I'd like to be able to use this device in sane. anyone know of a driver that will work for it? Mage - -- I will not be pushed, filed, stamped, indexed, briefed, debriefed, or numbered! My life is my own - No. 6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+9oDxn/usgigAaLcRArsBAJ9cXpAzFbXKRO9jkT0DPpwesgkFeACfS8Oq Nk06PmhTjL7h8ontQtw63Vw= =NJz1 -----END PGP SIGNATURE----- From maddog@mir.com Mon Jun 23 08:30:07 2003 From: maddog@mir.com (Matto Marjanovic) Date: Mon, 23 Jun 2003 03:30:07 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF632D0.7090102@gmx.net> (message from abel deuring on Mon, 23 Jun 2003 00:50:56 +0200) References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> <3EF46C3F.A897D7C4@satzbau-gmbh.de> <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> <3EF632D0.7090102@gmx.net> Message-ID: <1191-Mon23Jun2003033007-0400-maddog@yoo-hoo.ai.mit.edu> >OK, so we have indeed a flaw in the Linux SCSI system... I assume that >the scanners identify themselves as SCSI 1 devices, where these short >sense data blocks are normal. They do identify themselves, as a protocol between SCSI-1 and SCSI-2. ("SCSI_1_CCS" in drivers/scsi/scsi.h. This macro is used nowhere else in the Linux SCSI code.) >Did you try to issue REQUEST SENSE explicitly from the backend, where >this looks reasonable? This may not work with every Linux adapter driver Hmm, I never thought of that. (For the longest time, I figured the drivers would eventually get fixed; they haven't.) I'll give it a try. I don't suppose that a REQUEST SENSE can be issued by the sense handler itself? >(IIRC, older versions of the aha152x driver did not like user land >REQUEST SENSE commands), so it should be possible to turn them off with >an option. Heh --- if it's not one Linux SCSI bug, it is another. -matt m. From a.deuring@satzbau-gmbh.de Mon Jun 23 10:26:03 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Mon, 23 Jun 2003 11:26:03 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> <3EF46C3F.A897D7C4@satzbau-gmbh.de> <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> <3EF632D0.7090102@gmx.net> <1191-Mon23Jun2003033007-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF6C7AB.BCA46837@satzbau-gmbh.de> Matto Marjanovic wrote: > > >OK, so we have indeed a flaw in the Linux SCSI system... I assume that > >the scanners identify themselves as SCSI 1 devices, where these short > >sense data blocks are normal. > > They do identify themselves, as a protocol between SCSI-1 and SCSI-2. > ("SCSI_1_CCS" in drivers/scsi/scsi.h. This macro is used nowhere else > in the Linux SCSI code.) > > >Did you try to issue REQUEST SENSE explicitly from the backend, where > >this looks reasonable? This may not work with every Linux adapter driver > > Hmm, I never thought of that. (For the longest time, I figured the drivers > would eventually get fixed; they haven't.) I'll give it a try. > > I don't suppose that a REQUEST SENSE can be issued by the sense handler > itself? That would be a bit risky, I think. The problem is the Linux part of sanei_scsi.c. It supports command queueing, and without a careful review, how the command queue management works, I would recommend not to try a REQUEST SENSE from the sense handler itself. Abel From mrjaneway@gmx.net Mon Jun 23 10:22:47 2003 From: mrjaneway@gmx.net (mrjaneway@gmx.net) Date: Mon, 23 Jun 2003 11:22:47 +0200 (MEST) Subject: [sane-devel] Re: Sane support for Acer parallel port scanners References: <2263.1056009537@www36.gmx.net> Message-ID: <11756.1056360167@www59.gmx.net> Thank you Oliver and Henning for your replies regarding my problem! I think I will now try to run the scanner with windows-drivers using Wine. If that doesnt work, I will simply buy a new, Linux-compatible scanner - since they dont cost that much. I dont know how to write a backend - so thanks to all of you who can do it and who make it possible for the rest of all Linux Useres to use their scanners! Greetings, Tobias From henning@meier-geinitz.de Mon Jun 23 17:55:32 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 23 Jun 2003 18:55:32 +0200 Subject: [sane-devel] any scanner drivers that will work with twian compliant digital cams? In-Reply-To: <200306222124.19391.technomage-hawke@cox.net> References: <200306222124.19391.technomage-hawke@cox.net> Message-ID: <20030623165532.GA775@meier-geinitz.de> Hi, On Sun, Jun 22, 2003 at 09:24:16PM -0700, technomage wrote: > I have a vivtar brand vivcam-10. To answer the question in the subject: There is no such thing a a TWAIN-compliant camera o scanner. Only the scan applications are TWAIN-compatible. So beeing TWAIN-compatible doesn't mean anything for hardware. > it has a usb port and works in windows (but I don;t have adaptive > technology IN WINDOWS). What's "adaptive technology"? > I'd like to be able to use this device in sane. anyone know of a > driver that will work for it? As far as I know, no new SANE backends for cameras have been added during the last few years. But check our lists to be sure. However, there is the gphoto2 backend which can be used to access devices supported by gphoto2. See http://www.gphoto.org. There is also a backend for accessing video cameras supported by video4linux called v4l. Bye, Henning From TomF@sjpc.org Mon Jun 23 18:12:51 2003 From: TomF@sjpc.org (TomF) Date: Mon, 23 Jun 2003 10:12:51 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF Message-ID: <20030623101251.48d212b6.TomF@sjpc.org> On Redhat 9.0 with all Up2date patches installed, I uninstalled sane-backends and installed sane-backends-1.0.12-1asp.i386.rpm. When I ran xsane with ADF enabled, my HP7450C scanner, which is connected via usb, fed about 5 inches of the first document into the ADF, went into Initializing mode, and hung. I reproduced the problem with export SANE_DEBUG_AVISION=7, and sent a problem report to rene.rebe@gmx.net on Fri, 20 Jun 2003. I haven't received a response yet, and Rene appears to be on vacation: no activity since June 11. Yesteroday, I uninstalled sane, xsane-0.89-3, xsane-gimp-0.89-3, sane-frontends-1.0.9-2, and kdegraphics-3.1-5, and installed sane-backends-1.0.12.tar.gz and xsane-0.91.tar.gz. I got the same behavior when I ran xsane with ADF enabled. After hanging for a long time, sometimes a device disable error message is sent to the log, sometimes not. I am wondering if there is a SCSI/USB conflict. The usb/scsi emulation is supposed to be obsolete, but I found the following on my system: /var/log/messages shows kernel: Attached scsi generic sg5 at scsi1, channel 0, id 0, lun 0, type 6, during system startup. The Hardware Browser lists the scanner as sg5. /proc/bus/usb/devices contains: 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=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0801 Rev= 0.01 S: Manufacturer=hp S: Product=hp scanjet 7400c S: SerialNumber=87 tem 7400c I have been unable to determine precisely what is wrong with my configuration. Where should I look for the way to properly configure my scanner? From alan.purchase@paradise.net.nz Mon Jun 23 22:22:04 2003 From: alan.purchase@paradise.net.nz (Alan Purchase) Date: 24 Jun 2003 09:22:04 +1200 Subject: [sane-devel] Microtek Scanmaker 6700 (USB and FireWire) Message-ID: <1056403325.2759.8.camel@localhost.localdomain> Henning, FYI my PC has 2 USB ports, one is connected to an Epson printer and the other to a 4-port hub which in turn is connected to a Webcam, the Microtech Scanner, and my digital camera. I use the other hub port in Windows to connect to my wife's laptop using FastLynx. Here are the results of the cat /proc/bus/usb/devices that you asked for: T: Bus=02 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=d000 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=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 11/900 us ( 1%), #Int= 1, #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=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=07(print) Sub=01 Prot=02 MxPS=64 #Cfgs= 1 P: Vendor=04b8 ProdID=0001 Rev= 1.00 S: Manufacturer=EPSON S: Product=USB Printer C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 4 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0451 ProdID=1446 Rev= 1.10 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=ff(vend.) Sub=03 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=05da ProdID=20c9 Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms T: Bus=01 Lev=02 Prnt=03 Port=02 Cnt=02 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=067b ProdID=0000 Rev= 0.00 S: Manufacturer=Prolific Technology Inc. C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbnet E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=1ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=02 Prnt=03 Port=03 Cnt=03 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=046d ProdID=08b0 Rev= 0.02 S: SerialNumber=01402100A5000000 C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 0 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 196 Ivl=1ms I: If#= 0 Alt= 2 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 292 Ivl=1ms I: If#= 0 Alt= 3 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 448 Ivl=1ms I: If#= 0 Alt= 4 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 592 Ivl=1ms I: If#= 0 Alt= 5 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 704 Ivl=1ms I: If#= 0 Alt= 6 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 776 Ivl=1ms I: If#= 0 Alt= 7 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 840 Ivl=1ms I: If#= 0 Alt= 8 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 896 Ivl=1ms I: If#= 0 Alt= 9 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 960 Ivl=1ms I: If#= 0 Alt=10 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 960 Ivl=1ms I: If#= 1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=(none) I: If#= 2 Alt= 0 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 2 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 90 Ivl=1ms I: If#= 2 Alt= 2 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 46 Ivl=1ms I: If#= 2 Alt= 3 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms I: If#= 2 Alt= 4 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 16 Ivl=1ms I hope that all means something. Cheers, Alan. -- ______________________________________________________________________ Alan Purchase IT Consultant Tel: +64 9 817 3101 113 Victory Road Mobile: +64 21 925 028 Laingholm E-mail: alan.purchase@paradise.co.nz Auckland 1007 New Zealand ______________________________________________________________________ From psfales@lucent.com Tue Jun 24 02:14:11 2003 From: psfales@lucent.com (Peter Fales) Date: Mon, 23 Jun 2003 20:14:11 -0500 Subject: [sane-devel] any scanner drivers that will work with twian compliant digital cams? In-Reply-To: <20030623165532.GA775@meier-geinitz.de> References: <200306222124.19391.technomage-hawke@cox.net> <20030623165532.GA775@meier-geinitz.de> Message-ID: <20030624011411.GA15896@lucent.com> On Mon, Jun 23, 2003 at 06:55:32PM +0200, Henning Meier-Geinitz wrote: > However, there is the gphoto2 backend which can be used to access > devices supported by gphoto2. See http://www.gphoto.org. Unfortunately, there are no Vivatar cameras supported by gphoto2. A quick google search shows a number of people lamenting the lack of Linux support for Vivitar cameras. -- Peter Fales From ope557@yahoo.com Tue Jun 24 08:23:10 2003 From: ope557@yahoo.com (ope) Date: Tue, 24 Jun 2003 00:23:10 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030618001421.34819.qmail@web20604.mail.yahoo.com> Message-ID: <20030624072310.25101.qmail@web20608.mail.yahoo.com> I have found another 'behavior' that might shed some light on the problems that I am having. When I do a preview the interface auto selects a large square area covering most of the scanner bed which I then drag/resize to the actual image I am scanning (nothing new here). What I have noticed with absolute reliability is this: 1. If, after the preview, I can see the entire outline of the selection box then the subsequent scan will work. 2. However, If I can't see the entire selection box then the scan will not work. What I mean by this is that often times the bottom line of the selection box is 'off' the window such that I can't see any bottom line for selecting the image area only. If I put the mouse on the bottom of the frame and drag up I can select the scanning area. Does my explaination make sense? I can send screen shots if it does not. It is as if xsane thinks that the scanner bed is longer than it is. It oddly explains why the scanner lamp has completed the scan and returned but the software seems to be waiting for more data and is getting bulk_msg: timeout messages. Does anyone have any ideas? --- ope wrote: > What I see in messages are a lot of messages saying: > kernel: usb_control/bulk_msg: timeout > last message repeated 2 times > last message repeated 3 times > ... > > and after 10 minutes or so I will see: > kernel: scanner.c: read_scanner(0): excessive NAK's > received > > > --- Oliver Rauch > wrote: > > On Tuesday 17 June 2003 09:39, ope wrote: > > > > > I have also noticed another thing that is worth > > > mentioning. At one point when the xsane seemed > to > > be > > > stuck I tried unplugging the scanner from the > USB > > > port. I was expecting xsane to fail and close > > down. > > > What actually did happen was that the complete > > scanned > > > image instantly popped up in the viewer and > xsane > > was > > > running as if nothing has happened. Just for > fun > > I > > > tried it couple more times and had the same > > results > > > each time. It appears to me that that the scan > is > > > essentially complete at the point that it is > > freezing. > > > > This sounds as if there is a problem with the USB > > communication. > > > > Do you get any messages about USB problems > > in /var/log/messages ? > > > > Oliver > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel@www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > http://sbc.yahoo.com > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From henning@meier-geinitz.de Tue Jun 24 09:43:25 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 24 Jun 2003 10:43:25 +0200 Subject: [sane-devel] Microtek Scanmaker 6700 (USB and FireWire) In-Reply-To: <1056403325.2759.8.camel@localhost.localdomain> References: <1056403325.2759.8.camel@localhost.localdomain> Message-ID: <20030624084325.GB2856@meier-geinitz.de> Hi, On Tue, Jun 24, 2003 at 09:22:04AM +1200, Alan Purchase wrote: > T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=ff(vend.) Sub=03 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=05da ProdID=20c9 Rev= 0.00 > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms Thanks. I'll add that to our lists. Bye, Henning From moitinho@civil.ist.utl.pt Tue Jun 24 10:49:46 2003 From: moitinho@civil.ist.utl.pt (Jose Paulo Moitinho de Almeida) Date: Tue, 24 Jun 2003 10:49:46 +0100 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030623101251.48d212b6.TomF@sjpc.org> References: <20030623101251.48d212b6.TomF@sjpc.org> Message-ID: <200306241049.46918.moitinho@civil.ist.utl.pt> On Monday 23 June 2003 18:12, TomF wrote: > On Redhat 9.0 with all Up2date patches installed, I uninstalled > sane-backends and installed sane-backends-1.0.12-1asp.i386.rpm. When I > ran xsane with ADF enabled, my HP7450C scanner, which is connected > via usb, fed about 5 inches of the first document into the ADF, went > into Initializing mode, and hung. I reproduced the problem with export > SANE_DEBUG_AVISION=7, and sent a problem report to rene.rebe@gmx.net on > Fri, 20 Jun 2003. I haven't received a response yet, and Rene appears > to be on vacation: no activity since June 11. > > Yesteroday, I uninstalled sane, xsane-0.89-3, xsane-gimp-0.89-3, > sane-frontends-1.0.9-2, and kdegraphics-3.1-5, and installed > sane-backends-1.0.12.tar.gz and xsane-0.91.tar.gz. I got the same > behavior when I ran xsane with ADF enabled. After hanging for a long > time, sometimes a device disable error message is sent to the log, > sometimes not. > > > I am wondering if there is a SCSI/USB conflict. The usb/scsi emulation > is supposed to be obsolete, but I found the following on my system: > Without the logs it is difficult to tell. But the current version of the backend uses libusb, so (probably) the hpusbsci module is necessary for that scanner, but it may happen that when you plug the scanner the kernel loads it automatically... Please try to do an "lsmod" to check if the module is loaded and if it is do an "rmmod hpusbscsi" before trying to scan. Regards ZP From moitinho@civil.ist.utl.pt Tue Jun 24 11:42:25 2003 From: moitinho@civil.ist.utl.pt (Jose Paulo Moitinho de Almeida) Date: Tue, 24 Jun 2003 11:42:25 +0100 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <200306241049.46918.moitinho@civil.ist.utl.pt> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> Message-ID: <200306241142.25425.moitinho@civil.ist.utl.pt> On Tuesday 24 June 2003 10:49, Jose Paulo Moitinho de Almeida wrote: > On Monday 23 June 2003 18:12, TomF wrote: >..... > > Without the logs it is difficult to tell. But the current version of the > backend uses libusb, so (probably) the hpusbsci module is necessary for > that scanner, but it may happen that when you plug the scanner the kernel > loads it automatically... > Sorry! I meant "... the hpusbscsi module is NOT necessary ..." ZP From sigurd.stordal@stud.ibg.uit.no Tue Jun 24 14:56:46 2003 From: sigurd.stordal@stud.ibg.uit.no (Sigurd Stordal) Date: Tue, 24 Jun 2003 15:56:46 +0200 Subject: [sane-devel] Problems with the canon backend for a canoscan 2700F. Message-ID: <200306241556.48630.sigurd.stordal@stud.ibg.uit.no> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It will take a preview without problem, but when I choose scan in xsane, = I get=20 a "failed to start scanner: invalid argument", error. I get the same err= or=20 when trying xscanimage. Xsane 0.90, xscanimage 1.0.9. Sane-backends 1.0.1= 2. Had previous problems with backend 1.0.10, giving strange colours in the=20 scanner, this has been fixed no, but no there is this error. could it be = a=20 scsi problem. - --=20 Sigurd Stordal President of GOGS Experimental Petrologist -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE++FifSB4UOs/snOURAu88AJ9q3g9P1YUfpGr3T/Py4mKw4PvYqACdGOko IbC+oGNz6UJ2/74nsSSFH/w=3D =3D/dfh -----END PGP SIGNATURE----- From ukd@xenon.pc.Uni-Koeln.DE Tue Jun 24 16:48:29 2003 From: ukd@xenon.pc.Uni-Koeln.DE (Ulrich Deiters) Date: Tue, 24 Jun 2003 17:48:29 +0200 (METDST) Subject: [sane-devel] Problems with the Canoscan 2700F Message-ID: <200306241548.RAA29561@xenon.pc.Uni-Koeln.DE> Could you let me have a debug printout (after setting SANE_DEBUG_CANON=255), so that I can locate the problem? Regards, Ulrich Deiters From TomF@sjpc.org Tue Jun 24 18:40:15 2003 From: TomF@sjpc.org (TomF) Date: Tue, 24 Jun 2003 10:40:15 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <200306241049.46918.moitinho@civil.ist.utl.pt> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> Message-ID: <20030624104015.7b00f168.TomF@sjpc.org> On Tue, 24 Jun 2003 10:49:46 +0100 Jose Paulo Moitinho de Almeida wrote: > On Monday 23 June 2003 18:12, TomF wrote: ... > > I got the same > > behavior when I ran xsane with ADF enabled. After hanging for a > > long time, sometimes a device disable error message is sent to the > > log, sometimes not. ... > it may happen that when you plug the > scanner the kernel loads it automatically... > > Please try to do an "lsmod" to check if the module is loaded and if it > is do an "rmmod hpusbscsi" before trying to scan. > Thanks. I think I'm closer, but now my scanner is not recognized. hpusbscsi was loaded. I removed it, and checked the hardware browser. The entry for the Scanner was removed. To make sure hpusbscsi didn't get loaded on the next reboot, I renamed hpusbscsi.o. Then I rebooted to determine if the scanner would be detected as a usb device. The hardware browser still showed no browser, and xsane found no scanner device on startup. How can I get the scanner recognized as a USB device? From henning@meier-geinitz.de Tue Jun 24 18:42:24 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 24 Jun 2003 19:42:24 +0200 Subject: [sane-devel] Problems with the canon backend for a canoscan 2700F. In-Reply-To: <200306241556.48630.sigurd.stordal@stud.ibg.uit.no> References: <200306241556.48630.sigurd.stordal@stud.ibg.uit.no> Message-ID: <20030624174224.GB7697@meier-geinitz.de> Hi, On Tue, Jun 24, 2003 at 03:56:46PM +0200, Sigurd Stordal wrote: > It will take a preview without problem, but when I choose scan in xsane, I get > a "failed to start scanner: invalid argument", error. I get the same error > when trying xscanimage. Xsane 0.90, xscanimage 1.0.9. Sane-backends 1.0.12. > Had previous problems with backend 1.0.10, giving strange colours in the > scanner, this has been fixed no, but no there is this error. could it be a > scsi problem. I'm not a Canon expert, the canon backend maintainer may know more details. But nevertheless some general hints: * Make sure that you don't mix top-left and bottom-right coordinates. I don't know if that's possible with this frontend/backend combination but you never know. When you select what to scan, start with the top-left edge * The difference between preview and actual scan is usually only the resolution and sometimes scan mode. So try some differnt resolutions and modes (if the backend supports that). * Does scanimage show the same behaviour? E.g. try "scanimage >image.pnm". * You can enable debugging like this: SANE_DEBUG_CANON=255 xsane 2>logfile (and now scan an image and show us the logfile) * If it's a SCSI problem, the SCSI adapter and kernel version you use may be of interest Bye, Henning From oliver.rauch@rauch-domain.de Tue Jun 24 20:21:53 2003 From: oliver.rauch@rauch-domain.de (Oliver Rauch) Date: Tue, 24 Jun 2003 21:21:53 +0200 Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030624072310.25101.qmail@web20608.mail.yahoo.com> References: <20030624072310.25101.qmail@web20608.mail.yahoo.com> Message-ID: <200306242121.53495.oliver.rauch@rauch-domain.de> I suggest at first you disable the autmatic scanarea selection in the preferences of xsane. I will take a look at it. Oliver On Tuesday 24 June 2003 09:23, ope wrote: > I have found another 'behavior' that might shed some > light on the problems that I am having. When I do a > preview the interface auto selects a large square area > covering most of the scanner bed which I then > drag/resize to the actual image I am scanning (nothing > new here). What I have noticed with absolute > reliability is this: > > 1. If, after the preview, I can see the entire > outline of the selection box then the subsequent scan > will work. > > 2. However, If I can't see the entire selection box > then the scan will not work. What I mean by this is > that often times the bottom line of the selection box > is 'off' the window such that I can't see any bottom > line for selecting the image area only. If I put the > mouse on the bottom of the frame and drag up I can > select the scanning area. > > Does my explaination make sense? I can send screen > shots if it does not. > > It is as if xsane thinks that the scanner bed is > longer than it is. It oddly explains why the scanner > lamp has completed the scan and returned but the > software seems to be waiting for more data and is > getting bulk_msg: timeout messages. > > Does anyone have any ideas? > > --- ope wrote: > > What I see in messages are a lot of messages saying: > > kernel: usb_control/bulk_msg: timeout > > last message repeated 2 times > > last message repeated 3 times > > ... > > > > and after 10 minutes or so I will see: > > kernel: scanner.c: read_scanner(0): excessive NAK's > > received > > > > > > --- Oliver Rauch > > > > wrote: > > > On Tuesday 17 June 2003 09:39, ope wrote: > > > > I have also noticed another thing that is worth > > > > mentioning. At one point when the xsane seemed > > > > to > > > > > be > > > > > > > stuck I tried unplugging the scanner from the > > > > USB > > > > > > port. I was expecting xsane to fail and close > > > > > > down. > > > > > > > What actually did happen was that the complete > > > > > > scanned > > > > > > > image instantly popped up in the viewer and > > > > xsane > > > > > was > > > > > > > running as if nothing has happened. Just for > > > > fun > > > > > I > > > > > > > tried it couple more times and had the same > > > > > > results > > > > > > > each time. It appears to me that that the scan > > > > is > > > > > > essentially complete at the point that it is > > > > > > freezing. > > > > > > This sounds as if there is a problem with the USB > > > communication. > > > > > > Do you get any messages about USB problems > > > in /var/log/messages ? > > > > > > Oliver > > > _______________________________________________ > > > Sane-devel mailing list > > > Sane-devel@www.mostang.com > > > http://www.mostang.com/mailman/listinfo/sane-devel > > > > __________________________________ > > Do you Yahoo!? > > SBC Yahoo! DSL - Now only $29.95 per month! > > http://sbc.yahoo.com > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel@www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > http://sbc.yahoo.com > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel --=20 http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:Oliver.Rauch@Rauch-Domain.DE From henning@meier-geinitz.de Tue Jun 24 20:41:26 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 24 Jun 2003 21:41:26 +0200 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030624104015.7b00f168.TomF@sjpc.org> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> Message-ID: <20030624194126.GC7697@meier-geinitz.de> Hi, > Then I rebooted to determine if the scanner would be detected as a usb > device. The hardware browser still showed no browser, and xsane found > no scanner device on startup. > > How can I get the scanner recognized as a USB device? That's done automatically. If it's not detected as USB device by the kernel, it can't be used by hpusbscsi. Is it found by sane-find-scanner as root? Is it found by scanimage -L as root? If yes, you may need to set up permissions for libusb correctly. That's explained in man sane-usb. bye, Henning From hshane@austin.rr.com Wed Jun 25 02:42:24 2003 From: hshane@austin.rr.com (Howard Shane) Date: Tue, 24 Jun 2003 20:42:24 -0500 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP Message-ID: <3EF8FE00.3050107@austin.rr.com> ...is available for viewing at http://66.25.191.66/docs/HOWTOS/Scanner/index.html I've tried to incorporate everyone's corrections and suggestions wherever possible. For any remaining omissions or errata please let me know. Thanks! From ope557@yahoo.com Wed Jun 25 09:05:35 2003 From: ope557@yahoo.com (ope) Date: Wed, 25 Jun 2003 01:05:35 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <200306242121.53495.oliver.rauch@rauch-domain.de> Message-ID: <20030625080535.22628.qmail@web20604.mail.yahoo.com> Let me know if you need more detailed logs, system info or want to use my setup to test some things out. I am happy to pitch in if it will help. --- Oliver Rauch wrote: > > I suggest at first you disable the autmatic scanarea > selection > in the preferences of xsane. > > I will take a look at it. > > Oliver > > On Tuesday 24 June 2003 09:23, ope wrote: > > I have found another 'behavior' that might shed > some > > light on the problems that I am having. When I do > a > > preview the interface auto selects a large square > area > > covering most of the scanner bed which I then > > drag/resize to the actual image I am scanning > (nothing > > new here). What I have noticed with absolute > > reliability is this: > > > > 1. If, after the preview, I can see the entire > > outline of the selection box then the subsequent > scan > > will work. > > > > 2. However, If I can't see the entire selection > box > > then the scan will not work. What I mean by this > is > > that often times the bottom line of the selection > box > > is 'off' the window such that I can't see any > bottom > > line for selecting the image area only. If I put > the > > mouse on the bottom of the frame and drag up I can > > select the scanning area. > > > > Does my explaination make sense? I can send > screen > > shots if it does not. > > > > It is as if xsane thinks that the scanner bed is > > longer than it is. It oddly explains why the > scanner > > lamp has completed the scan and returned but the > > software seems to be waiting for more data and is > > getting bulk_msg: timeout messages. > > > > Does anyone have any ideas? > > > > --- ope wrote: > > > What I see in messages are a lot of messages > saying: > > > kernel: usb_control/bulk_msg: timeout > > > last message repeated 2 times > > > last message repeated 3 times > > > ... > > > > > > and after 10 minutes or so I will see: > > > kernel: scanner.c: read_scanner(0): excessive > NAK's > > > received > > > > > > > > > --- Oliver Rauch > > > > > > wrote: > > > > On Tuesday 17 June 2003 09:39, ope wrote: > > > > > I have also noticed another thing that is > worth > > > > > mentioning. At one point when the xsane > seemed > > > > > > to > > > > > > > be > > > > > > > > > stuck I tried unplugging the scanner from > the > > > > > > USB > > > > > > > > port. I was expecting xsane to fail and > close > > > > > > > > down. > > > > > > > > > What actually did happen was that the > complete > > > > > > > > scanned > > > > > > > > > image instantly popped up in the viewer and > > > > > > xsane > > > > > > > was > > > > > > > > > running as if nothing has happened. Just > for > > > > > > fun > > > > > > > I > > > > > > > > > tried it couple more times and had the same > > > > > > > > results > > > > > > > > > each time. It appears to me that that the > scan > > > > > > is > > > > > > > > essentially complete at the point that it is > > > > > > > > freezing. > > > > > > > > This sounds as if there is a problem with the > USB > > > > communication. > > > > > > > > Do you get any messages about USB problems > > > > in /var/log/messages ? > > > > > > > > Oliver > > > > > _______________________________________________ > > > > Sane-devel mailing list > > > > Sane-devel@www.mostang.com > > > > > http://www.mostang.com/mailman/listinfo/sane-devel > > > > > > __________________________________ > > > Do you Yahoo!? > > > SBC Yahoo! DSL - Now only $29.95 per month! > > > http://sbc.yahoo.com > > > _______________________________________________ > > > Sane-devel mailing list > > > Sane-devel@www.mostang.com > > > > http://www.mostang.com/mailman/listinfo/sane-devel > > > > __________________________________ > > Do you Yahoo!? > > SBC Yahoo! DSL - Now only $29.95 per month! > > http://sbc.yahoo.com > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel@www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > -- > http://www.xsane.org > http://www.mostang.com/sane > http://www.rauch-domain.de > mailto:Oliver.Rauch@Rauch-Domain.DE > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From jochen.eisinger@gmx.de Wed Jun 25 09:18:10 2003 From: jochen.eisinger@gmx.de (Jochen Eisinger) Date: Wed, 25 Jun 2003 10:18:10 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EF8FE00.3050107@austin.rr.com> References: <3EF8FE00.3050107@austin.rr.com> Message-ID: <20030625101810.139be97d.jochen.eisinger@gmx.de> --=.Ck,JUCF/u'4.N7 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, some remarks on the Parallel Port sections: Interface Types -> Parallel Port Devices: Jonathan's page is really very outdated for some time now. It's better (also for the other scanner types) to check the supported scanners list on sane.informatik.uni-freiburg.de/cgi-bin/driver.pl Kernel Support -> Parallel Port Scanners: Not all scanner drivers need kernel level support. Some are using directio (this needs to be enabled in configure) You're also mixing dmesg and lsmod a little (lsmod is in bold, but a dmesg output is shown). You could also note that you might have to enabled certain transfer modes in the BIOS Making and Accessing the Scanner Devices -> Manually creating ... crw------- 1 root root 99, 0 Jun 24 13:47 parport0 crw------- 1 root root 99, 1 Jun 24 13:47 parport1 crw------- 1 root root 99, 2 Jun 24 13:47 parport2 crw------- 1 root root 99, 3 Jun 24 13:47 parport3 crw-r----- 1 root root 1, 4 Jan 1 1970 port if a scanner doesn't use the kernel drivers, it normally needs the port number as device name. Making and... -> Groups and Permissions: If a scanner doesn't use the kernel drivers, you have to use the sane daemon (saned) to let non-root users access the scanner Configuring SANE: Parallel port backends often need libieee1284 installed or directio enabled. You could also stress the point a little more that an old SANE installation is the reason #1 why self compiled SANE version don't work (as you'd expect) The network setup is missing the (x)inetd setup and doesn't mention the possibility of using passwords Testing your scanner: There's an option --test for scanimage that's it :) regards -- jochen --=.Ck,JUCF/u'4.N7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE++VrK8OF76YrreuMRArQTAKCReMsOr0kGL5l1uJpYK4DAbf9PvwCePze4 ZaxTEK0r7jeQMKdlfptoHP4= =ca9K -----END PGP SIGNATURE----- --=.Ck,JUCF/u'4.N7-- From anoah@pfeiffer.edu Wed Jun 25 14:17:10 2003 From: anoah@pfeiffer.edu (m. allan noah) Date: Wed, 25 Jun 2003 09:17:10 -0400 (EDT) Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EF8FE00.3050107@austin.rr.com> Message-ID: it seems to me, that if you want your document to be more future-proof, you would spend some more time talking about using libusb instead of the kernel scanner driver, which is likely to be removed in later kernels (as libusb becomes more stable) until then, i would likely re-name section 3 to 'OS support' instead of kernel support, and make two usb entries, one for kernel and one for libusb. then, to keep things consistent, you would have to add a libusb section to 4.2. allan On Tue, 24 Jun 2003, Howard Shane wrote: > ...is available for viewing at > > http://66.25.191.66/docs/HOWTOS/Scanner/index.html > > I've tried to incorporate everyone's corrections and suggestions > wherever possible. For any remaining omissions or errata please let me know. > > Thanks! > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From hbs@ks.informatik.uni-kiel.de Wed Jun 25 14:16:35 2003 From: hbs@ks.informatik.uni-kiel.de (Henrik Schmidt) Date: Wed, 25 Jun 2003 15:16:35 +0200 (MEST) Subject: [sane-devel] Scsi problem with Solaris 2.6 Message-ID: I'm trying to use a Microtek ScanMaker III with Solaris 2.6 and the scg SCSI driver. I'm using sane-backends 1.0.12 with frontend 1.0.10. The scanner is detected but as soon as I start a scan or prescan either with xscanimage or xsane the application locks up. I get errors in /var/adm/messages. After 2 minutes the applications return with a timeout and i/o error. I checked the scanner on a Windows computer and it did work. I checked it on another computer with sane and it failed too. I had it running some a ago. When I moved the computer to a different location I updated sane and it failed to work afterwards. Going back to older sane backend versions (up to 1.0.8) didn't help either. I tried to contact both the microtek backend coder as well as the contact in README.solaris but got no reply. Is there any hope ? Henrik --------------------- /var/adm/messages ------------------------------- Jun 25 13:08:25 cortex unix: WARNING: /iommu@f,e0000000/sbus@f,e0001000/espdma@f ,400000/esp@f,800000 (esp0):^M^M Jun 25 13:08:25 cortex unix: data transfer overrun: current esp state: Jun 25 13:08:25 cortex unix: esp: State=DATA Last State=DATA_DONE^ M^M Jun 25 13:08:25 cortex unix: esp: Latched stat=0x91 intr=0x10 fifo 0x80^M^M Jun 25 13:08:25 cortex unix: esp: last msg out: IDENTIFY; last msg in: COMMAND COMPLETE^M^M Jun 25 13:08:25 cortex unix: esp: DMA csr=0xa4240010^M^M Jun 25 13:08:25 cortex unix: esp: addr=fc0245a0 dmacnt=0 last=fc01 55a0 last_cnt=f000^M^M Jun 25 13:08:25 cortex unix: esp: Cmd dump for Target 5 Lun 0:^M^M Jun 25 13:08:25 cortex unix: esp: cdblen=6, cdb=[ 0x8 0x0 0x0 0x0 0x91 0x0 ]^M^M Jun 25 13:08:25 cortex unix: esp: pkt_state=0xf pkt_flags=0x0 pkt_statistics=0x0^M^M Jun 25 13:08:25 cortex unix: esp: cmd_flags=0x462 cmd_timeout=110^ M^M Jun 25 13:08:25 cortex unix: handle_incomplete: 1 retry cnt: 0 Jun 25 13:08:25 cortex unix: scgintr: DONE_ERROR pkt_reason: 7 state: f resid: 0 packet resid: 126976 Jun 25 13:10:32 cortex unix: WARNING: /iommu@f,e0000000/sbus@f,e0001000/espdma@f ,400000/esp@f,800000 (esp0):^M^M Jun 25 13:10:32 cortex unix: Connected command timeout for Target 5.0 -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs@ks.informatik.uni-kiel.de From fsanta@arrakis.es Wed Jun 25 16:05:27 2003 From: fsanta@arrakis.es (fsanta) Date: Wed, 25 Jun 2003 17:05:27 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 Message-ID: <200306251705.27766.fsanta@arrakis.es> Hi everyone. After an upgrade from SuSE 8.1 to 8.2 my umax 2200 freezes the system hard after xsane preview: Here are the messages: Jun 24 12:24:24 sbs3 resmgr[748]: accepted connection from user steve Jun 24 12:24:24 sbs3 xsane: resmgr: server response code 502 Jun 24 12:24:24 sbs3 resmgr[748]: disconnect from steve Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses synchronous negotiation. Using asynchronous transfers The permissions on /dev/sg0 are global rw. I have an Adaptec 2904 (sic) card and everything was fine under 8.1. Can anyone help? Thanks, Steve. From ljm@xs4all.nl Wed Jun 25 16:19:19 2003 From: ljm@xs4all.nl (Laurent-jan) Date: Wed, 25 Jun 2003 17:19:19 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP References: <3EF8FE00.3050107@austin.rr.com> Message-ID: <3EF9BD77.20401@xs4all.nl> Howard Shane wrote: > ...is available for viewing at > > http://66.25.191.66/docs/HOWTOS/Scanner/index.html > > I've tried to incorporate everyone's corrections and suggestions > wherever possible. For any remaining omissions or errata please let me > know. > > Thanks! > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel Hi, Some remarks: 5.1: The howto-page is not mine; it has been made by Steve Sheriff. After he took it down, I got quite a few questions about the disapaered link, so I asked Steve if I could host a copy. And it's his model, not mine (allas...) 6: You put the scanimage command as: $ scanimage -d /dev/scanner0 --format pnm > outfile.pnm I remember some discussions about the -d argument. I think it should be -d backend:device, f.e. $ scanimage -d umax:/dev/sg6 --format pnm > outfile.pnm 8: Maybe we should think about a more general way of toubleshooting. Some maufacturers (f.e. of copiers) use a flowchart-like algoritm to find the actions. It would be nice if we could make somethong like that. ljm From henning@meier-geinitz.de Wed Jun 25 16:22:50 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 25 Jun 2003 17:22:50 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <200306251705.27766.fsanta@arrakis.es> References: <200306251705.27766.fsanta@arrakis.es> Message-ID: <20030625152250.GA9836@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 05:05:27PM +0200, fsanta wrote: > After an upgrade from SuSE 8.1 to 8.2 my umax 2200 freezes the system hard > after xsane preview: Here are the messages: That5 doesn't look like it's realted to SANE. Looks more like a kernel problem. > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > synchronous negotiation. Using asynchronous transfers Try disabling synchronous transfers in your SCSI driver or the BIOS (but I guess your SCSI controller doesn't have a BIOS). Bye, Henning From fsanta@arrakis.es Wed Jun 25 17:34:17 2003 From: fsanta@arrakis.es (fsanta) Date: Wed, 25 Jun 2003 18:34:17 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <20030625152250.GA9836@meier-geinitz.de> References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> Message-ID: <200306251834.17699.fsanta@arrakis.es> Hi Henning Could you tell me how to do that? the scsi card is a very basic 2904 which Oliver added to the database of usable cards way back years ago. The scsi terminator plug is missing on the scanner. Could it have anything to do with that? I can't test it as I haven't got an scsi terminator plug. We removed it under 8.1 to produce acceptable scans. It was of very poor quality with. In Spain scsi terminator plugs take a long time to get ;-) Cheers, Steve. On Wednesday 25 June 2003 17:22, Henning Meier-Geinitz wrote: > Hi, > > On Wed, Jun 25, 2003 at 05:05:27PM +0200, fsanta wrote: > > After an upgrade from SuSE 8.1 to 8.2 my umax 2200 freezes the system > > hard after xsane preview: Here are the messages: > > That5 doesn't look like it's realted to SANE. Looks more like a kernel > problem. > > > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > > synchronous negotiation. Using asynchronous transfers > > Try disabling synchronous transfers in your SCSI driver or the BIOS > (but I guess your SCSI controller doesn't have a BIOS). > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From henning@meier-geinitz.de Wed Jun 25 17:52:18 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 25 Jun 2003 18:52:18 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EF9BD77.20401@xs4all.nl> References: <3EF8FE00.3050107@austin.rr.com> <3EF9BD77.20401@xs4all.nl> Message-ID: <20030625165218.GC9836@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 05:19:19PM +0200, Laurent-jan wrote: > 6: You put the scanimage command as: > $ scanimage -d /dev/scanner0 --format pnm > outfile.pnm > I remember some discussions about the -d argument. I think it should be > -d backend:device, f.e. > $ scanimage -d umax:/dev/sg6 --format pnm > outfile.pnm You are right here. And pnm is the default so it makes only sense to mention that to show the difference to tiff. > 8: Maybe we should think about a more general way of toubleshooting. > Some maufacturers (f.e. of copiers) use a flowchart-like algoritm to > find the actions. It would be nice if we could make somethong like that. Such a kind of flowchart is used "inside" the sane-troubleshoot program at: http://www.meier-geinitz.de/sane/sts/ Not finished yet, however. Bye, Henning From tomf@sjpc.org Wed Jun 25 17:57:17 2003 From: tomf@sjpc.org (Thomas Frayne) Date: 25 Jun 2003 09:57:17 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030624194126.GC7697@meier-geinitz.de> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> Message-ID: <1056560236.3843.853.camel@localhost.localdomain> On Tue, 2003-06-24 at 12:41, Henning Meier-Geinitz wrote: > Hi, > > Then I rebooted to determine if the scanner would be detected as a usb > > device. The hardware browser still showed no browser, and xsane found > > no scanner device on startup. > > > > How can I get the scanner recognized as a USB device? > > That's done automatically. If it's not detected as USB device by the > kernel, it can't be used by hpusbscsi. > > Is it found by sane-find-scanner as root? > Is it found by scanimage -L as root? > If yes, you may need to set up permissions for libusb correctly. > That's explained in man sane-usb. > Thanks. I read the manual, found that permissions were not set correctly, set them in fstab as recommended. Then sane-find-scanner and scanimage -L worked as a normal user. However, the scanner still does not work. I think I am closer, but I am lost. Messages indicated failure of usbdevfs, which is supposed to be obsolete. /usr/local/etc/sane.d/avision.conf lists devices which do not exist. I suspect that there is a mismatches among the sane configuration which was set up for the initial Redhat 9, the sane configuration set up when I installed sane-backends-1.0.12.tar.gz and xsane-0.91.tar.gz, and the kernel 2.4.20-18.9, which was upgraded by Up2date, but I can't figure out how to straighten it out. I'll keep trying. I have just done modprobe scanner vendor=0x0001 product=0x0002, and I plan to reboot and continue debugging, starting with why /dev/usbscanner does not exist. Any help would be appreciated. Tom Frayne Here are the details: found USB scanner (vendor=0x03f0 [hp], product=0x0801 [hp scanjet 7400c]) at libusb:004:002 device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c flatbed scanner Hardware browser lists no scanners Messages: Jun 24 13:37:48 localhost syslogd 1.4.1: restart. Jun 24 13:37:48 localhost syslog: syslogd startup succeeded Jun 24 13:37:48 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started. Jun 24 13:37:48 localhost kernel: Linux version 2.4.20-18.9 (root@gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Wed Jun 4 15:04:35 PDT 2003 Jun 24 13:37:50 localhost kernel: usb.c: registered new driver usbdevfs Jun 24 13:37:50 localhost kernel: usb.c: registered new driver hub Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0 Jun 24 13:37:50 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0870000, IRQ 5 Jun 24 13:37:50 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC Corporation USB Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 24 13:37:50 localhost kernel: hub.c: USB hub found Jun 24 13:37:50 localhost kernel: hub.c: 3 ports detected Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1 Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0 Jun 24 13:37:50 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0872000, IRQ 9 Jun 24 13:37:50 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC Corporation USB (#2) Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 24 13:37:50 localhost kernel: hub.c: USB hub found Jun 24 13:37:50 localhost kernel: hub.c: 2 ports detected Jun 24 13:37:50 localhost kernel: hub.c: new USB device 00:0b.0-1, assigned address 2 Jun 24 13:37:50 localhost kernel: hub.c: USB hub found Jun 24 13:37:50 localhost kernel: hub.c: 4 ports detected Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2 Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2 Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 24 13:37:50 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB 2.0 Jun 24 13:37:50 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem f087a000 Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, assigned bus number 3 Jun 24 13:37:51 localhost kernel: PCI: 00:0b.2 PCI cache line size set incorrectly (32 bytes) by BIOS/FW. Jun 24 13:37:51 localhost kernel: PCI: 00:0b.2 PCI cache line size corrected to 128. Jun 24 13:37:51 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22 Jun 24 13:37:51 localhost kernel: usb.c: USB disconnect on device 00:0b.0-1 address 2 Jun 24 13:37:51 localhost kernel: hub.c: USB hub found Jun 24 13:37:51 localhost kernel: hub.c: 5 ports detected Jun 24 13:37:51 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time 07:14:02 May 29 2003 Jun 24 13:37:51 localhost kernel: usb-uhci.c: High bandwidth mode enabled Jun 24 13:37:51 localhost kernel: PCI: Found IRQ 10 for device 00:07.2 Jun 24 13:37:51 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2 Jun 24 13:37:51 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 24 13:37:51 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, IRQ 10 Jun 24 13:37:51 localhost kernel: usb-uhci.c: Detected 2 ports Jun 24 13:37:51 localhost kernel: usb.c: new USB bus registered, assigned bus number 4 Jun 24 13:37:51 localhost kernel: hub.c: USB hub found Jun 24 13:37:51 localhost kernel: hub.c: 2 ports detected Jun 24 13:37:51 localhost kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Jun 24 13:37:51 localhost kernel: usb.c: registered new driver hiddev Jun 24 13:37:51 localhost kernel: usb.c: registered new driver hid Jun 24 13:37:51 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik Jun 24 13:37:51 localhost kernel: hid-core.c: USB HID support drivers Jun 24 13:37:51 localhost kernel: mice: PS/2 mouse device common for all mice Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1, assigned address 2 Jun 24 13:37:51 localhost kernel: hub.c: USB hub found Jun 24 13:37:51 localhost kernel: hub.c: 4 ports detected Jun 24 13:37:51 localhost kernel: Adding Swap: 1582360k swap-space (priority -1) Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 24 13:37:51 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1.2, assigned address 3 Jun 24 13:37:51 localhost kernel: usb.c: USB device 3 (vend/prod 0x2821/0x5001) is not claimed by any active driver. Jun 24 13:37:51 localhost kernel: usbdevfs: remount parameter error Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1.4, assigned address 4 Jun 24 13:37:51 localhost kernel: usb.c: USB device 4 (vend/prod 0x3f0/0x3404) is not claimed by any active driver. Jun 24 13:37:51 localhost kernel: hdc: attached ide-scsi driver. Jun 24 13:37:51 localhost kernel: scsi1 : SCSI host adapter emulation for IDE ATAPI devices Jun 24 13:37:51 localhost kernel: Vendor: HP Model: CD-Writer+ 8100 Rev: 1.0g Jun 24 13:37:51 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 24 13:37:51 localhost kernel: Initializing USB Mass Storage driver... Jun 24 13:37:51 localhost kernel: usb.c: registered new driver usb-storage Jun 24 13:37:51 localhost kernel: scsi2 : SCSI emulation for USB Mass Storage devices Jun 24 13:37:51 localhost kernel: Vendor: ASUS Model: CRW-5224A Rev: 1.00 Jun 24 13:37:51 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 24 13:37:51 localhost kernel: USB Mass Storage support registered. Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0 Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr1 at scsi1, channel 0, id 0, lun 0 Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr2 at scsi2, channel 0, id 0, lun 0 Jun 24 13:37:51 localhost kernel: (scsi0:A:4): 10.000MB/s transfers (10.000MHz, offset 32) Jun 24 13:37:51 localhost kernel: sr0: scsi3-mmc drive: 0x/0x dvd-ram cd/rw xa/form2 cdda tray Jun 24 13:37:51 localhost kernel: Uniform CD-ROM driver Revision: 3.12 Jun 24 13:37:51 localhost kernel: sr1: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray Jun 24 13:37:51 localhost kernel: sr2: scsi-1 drive Jun 24 13:37:51 localhost kernel: usb.c: registered new driver usblp Jun 24 13:37:51 localhost kernel: printer.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404 Jun 24 13:37:51 localhost kernel: printer.c: v0.11: USB Printer Device Class driver Jun 24 13:37:51 localhost kernel: parport0: PC-style at 0x378 [PCSPP,TRISTATE] Jun 24 13:37:51 localhost kernel: ip_tables: (C) 2000-2002 Netfilter core team Jun 24 13:37:51 localhost kernel: ip_conntrack version 2.1 (6143 buckets, 49144 max) - 292 bytes per conntrack Jun 24 13:37:51 localhost kernel: Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002) Jun 24 13:37:51 localhost kernel: PCI: Found IRQ 11 for device 00:0c.0 Jun 24 13:45:57 localhost kernel: ac97_codec: AC97 codec, id: TRA35 (TriTech TR A5) Jun 24 13:45:58 localhost modprobe: modprobe: Can't locate module sound-service-0-3 Jun 24 13:52:13 localhost modprobe: modprobe: Can't locate module char-major-81 Jun 24 13:52:35 localhost last message repeated 7 times Jun 24 13:53:48 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:53:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 24 13:54:18 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:54:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x83 len 22 ret -110 Jun 24 13:54:48 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:54:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 24 13:55:18 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:55:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 24 13:55:48 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:55:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 24 13:57:50 localhost modprobe: modprobe: Can't locate module char-major-81 Jun 24 13:57:50 localhost last message repeated 3 times Jun 24 13:58:20 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:58:20 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 24 13:58:50 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:58:50 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 24 13:59:20 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:59:20 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 24 14:16:09 localhost gconfd (root-3450): Received signal 1, shutting down cleanly Jun 24 14:16:45 localhost rpc.statd[2040]: Caught signal 15, un-registering and exiting.Jun 25 08:55:06 Jun 25 08:55:06 localhost kernel: usb.c: registered new driver usbscanner Jun 25 08:55:06 localhost kernel: scanner.c: 0.4.12:USB Scanner Driver Jun 25 08:55:06 localhost kernel: scanner.c: probe_scanner: User specified USB scanner -- Vendor:Product - 1:2 GENERIC KERNEL SCANNER DRIVER Ensure that the access permissions for the USB device are set appropri- ately. We recommend to add a group "scanner" to /etc/group which con- tains all users that should have access to the scanner. The permission of the device should then be set to allow group read and write access. For example, if the scanner is at USB device /dev/usb/scanner0, then the following two commands would set the permission correctly: $ chgrp scanner /dev/usb/scanner0 $ chmod 660 /dev/usb/scanner0 If your scanner isnā€™t detected automatically by your operating systemā€™s scanner driver, you need to tell the kernel the vendor and product ids of your scanner. For Linux, this can be done with modprobe parameters: First, remove the scanner module (rmmod scanner), then load it again: modprobe scanner vendor=0x0001 product=0x0002. Use the appropriate vendor and product ids (e.g. from /var/log/messages, dmesg, or cat /proc/bus/usb/devices) /usr/local/etc/sane.d/avision.conf scsi AVISION scsi FCPA scsi MINOLTA scsi MITSBISH MCA-S600C scsi MITSBISH MCA-SS600 scsi HP scsi hp scsi /dev/scanner usb /dev/usbscanner usb /dev/usb/scanner [root@localhost root]# ls -l /dev/usb/scanner0 crw------- 1 tom root 180, 48 Jan 30 02:24 /dev/usb/scanner0 [root@localhost root]# ls -l /dev/usbscanner ls: /dev/usbscanner: No such file or directory [root@localhost root]# ls -l /dev/usb/scanner ls: /dev/usb/scanner: No such file or directory [root@localhost root]# /etc/fstab none /proc/bus/usb usbfs defaults,devmode=0666 0 0 /proc/bus/usb/devices 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=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0801 Rev= 0.01 S: Manufacturer=hp S: Product=hp scanjet 7400c S: SerialNumber=87 tem 7400c /proc/bus/usb/drivers usbdevfs hub 96-111: hiddev hid usb-storage 0- 15: usblp 48- 63: usbscanner From henning@meier-geinitz.de Wed Jun 25 19:11:01 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 25 Jun 2003 20:11:01 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <200306251834.17699.fsanta@arrakis.es> References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> <200306251834.17699.fsanta@arrakis.es> Message-ID: <20030625181101.GE9836@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 06:34:17PM +0200, fsanta wrote: > Could you tell me how to do that? To do what? Hint: If you quote the text you are referring to it's easier to understand what you mean? :-) I don't have your scanner or your card so I don't have personal experiences with this combination. But the "synchronous tranfer" SCSI feature seems to make trouble with many older SCSI scanners. And your kernel complains about it so it may be worth a try. Check the documentation in the Linux source code. Which SCSI driver do you use for the 2904? > the scsi card is a very basic 2904 which Oliver added to the database > of usable cards way back years ago. The scsi terminator plug is > missing on the scanner. Could it have anything to do with that? I > can't test it as I haven't got an scsi terminator plug. As I said, I don't have experience with that combination, but my scanners work without a terminator. At least if you have only one device on the SCSI bus. > We removed it > under 8.1 to produce acceptable scans. It was of very poor quality with. If adding/removing the terminator changes the quality of the scan something is completely broken. A wrong termination can lead to SCSI errors but I haven't heard about an influence on image quality. That would mean only the data is corrupted, not the commands and the SCSI system doesn't detect that (parity?). Bye, Henning From anoah@pfeiffer.edu Wed Jun 25 19:36:57 2003 From: anoah@pfeiffer.edu (m. allan noah) Date: Wed, 25 Jun 2003 14:36:57 -0400 (EDT) Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <1056560236.3843.853.camel@localhost.localdomain> Message-ID: tom, did you do an 'rpm -e --force --nodeps sane-backends' first? when you compiled the new sane backends, did you do: =2E/configure --prefix=3D/usr --sysconfdir=3D/etc make make install if not, start with those two things. then we can be sure that the version= =20 of sane you are using is the one you compiled. allan On 25 Jun 2003, Thomas Frayne wrote: > On Tue, 2003-06-24 at 12:41, Henning Meier-Geinitz wrote: > > Hi, > > > Then I rebooted to determine if the scanner would be detected as a us= b > > > device. The hardware browser still showed no browser, and xsane foun= d > > > no scanner device on startup. > > >=20 > > > How can I get the scanner recognized as a USB device? > >=20 > > That's done automatically. If it's not detected as USB device by the > > kernel, it can't be used by hpusbscsi. > >=20 > > Is it found by sane-find-scanner as root? > > Is it found by scanimage -L as root? > > If yes, you may need to set up permissions for libusb correctly. > > That's explained in man sane-usb. > >=20 >=20 > Thanks. I read the manual, found that permissions were not set > correctly, set them in fstab as recommended. Then sane-find-scanner and > scanimage -L worked as a normal user. However, the scanner still does > not work. I think I am closer, but I am lost. >=20 > Messages indicated failure of usbdevfs, which is supposed to be > obsolete. /usr/local/etc/sane.d/avision.conf lists devices which do not > exist. I suspect that there is a mismatches among the sane > configuration which was set up for the initial Redhat 9, the sane > configuration set up when I installed sane-backends-1.0.12.tar.gz and > xsane-0.91.tar.gz, and the kernel 2.4.20-18.9, which was upgraded by > Up2date, but I can't figure out how to straighten it out. >=20 > I'll keep trying. I have just done=20 > modprobe scanner vendor=3D0x0001 product=3D0x0002, > and I plan to reboot and continue debugging, starting with why > /dev/usbscanner does not exist. >=20 > Any help would be appreciated. >=20 > Tom Frayne >=20 >=20 >=20 >=20 > Here are the details: >=20 > found USB scanner (vendor=3D0x03f0 [hp], product=3D0x0801 [hp scanjet > 7400c]) at libusb:004:002 >=20 > device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c > flatbed scanner >=20 > Hardware browser lists no scanners >=20 > Messages: > Jun 24 13:37:48 localhost syslogd 1.4.1: restart. > Jun 24 13:37:48 localhost syslog: syslogd startup succeeded > Jun 24 13:37:48 localhost kernel: klogd 1.4.1, log source =3D /proc/kmsg > started. > Jun 24 13:37:48 localhost kernel: Linux version 2.4.20-18.9 > (root@gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 > Wed Jun 4 15:04:35 PDT 2003 > Jun 24 13:37:50 localhost kernel: usb.c: registered new driver usbdevfs > Jun 24 13:37:50 localhost kernel: usb.c: registered new driver hub > Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0 > Jun 24 13:37:50 localhost kernel: usb-ohci.c: USB OHCI at membase > 0xf0870000, IRQ 5 > Jun 24 13:37:50 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC > Corporation USB > Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, > assigned bus number 1 > Jun 24 13:37:50 localhost kernel: hub.c: USB hub found > Jun 24 13:37:50 localhost kernel: hub.c: 3 ports detected > Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1 > Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0 > Jun 24 13:37:50 localhost kernel: usb-ohci.c: USB OHCI at membase > 0xf0872000, IRQ 9 > Jun 24 13:37:50 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC > Corporation USB (#2) > Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, > assigned bus number 2 > Jun 24 13:37:50 localhost kernel: hub.c: USB hub found > Jun 24 13:37:50 localhost kernel: hub.c: 2 ports detected > Jun 24 13:37:50 localhost kernel: hub.c: new USB device 00:0b.0-1, > assigned address 2 > Jun 24 13:37:50 localhost kernel: hub.c: USB hub found > Jun 24 13:37:50 localhost kernel: hub.c: 4 ports detected > Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2 > Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2 > Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 > Jun 24 13:37:50 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB > 2.0 > Jun 24 13:37:50 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem > f087a000 > Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, > assigned bus number 3 > Jun 24 13:37:51 localhost kernel: PCI: 00:0b.2 PCI cache line size set > incorrectly (32 bytes) by BIOS/FW. > Jun 24 13:37:51 localhost kernel: PCI: 00:0b.2 PCI cache line size > corrected to 128. > Jun 24 13:37:51 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, > EHCI 0.95, driver 2003-Jan-22 > Jun 24 13:37:51 localhost kernel: usb.c: USB disconnect on device > 00:0b.0-1 address 2 > Jun 24 13:37:51 localhost kernel: hub.c: USB hub found > Jun 24 13:37:51 localhost kernel: hub.c: 5 ports detected > Jun 24 13:37:51 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time > 07:14:02 May 29 2003 > Jun 24 13:37:51 localhost kernel: usb-uhci.c: High bandwidth mode > enabled > Jun 24 13:37:51 localhost kernel: PCI: Found IRQ 10 for device 00:07.2 > Jun 24 13:37:51 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2 > Jun 24 13:37:51 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 > Jun 24 13:37:51 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, > IRQ 10 > Jun 24 13:37:51 localhost kernel: usb-uhci.c: Detected 2 ports > Jun 24 13:37:51 localhost kernel: usb.c: new USB bus registered, > assigned bus number 4 > Jun 24 13:37:51 localhost kernel: hub.c: USB hub found > Jun 24 13:37:51 localhost kernel: hub.c: 2 ports detected > Jun 24 13:37:51 localhost kernel: usb-uhci.c: v1.275:USB Universal Host > Controller Interface driver > Jun 24 13:37:51 localhost kernel: usb.c: registered new driver hiddev > Jun 24 13:37:51 localhost kernel: usb.c: registered new driver hid > Jun 24 13:37:51 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, > Vojtech Pavlik > Jun 24 13:37:51 localhost kernel: hid-core.c: USB HID support drivers > Jun 24 13:37:51 localhost kernel: mice: PS/2 mouse device common for all > mice > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1, > assigned address 2 > Jun 24 13:37:51 localhost kernel: hub.c: USB hub found > Jun 24 13:37:51 localhost kernel: hub.c: 4 ports detected > Jun 24 13:37:51 localhost kernel: Adding Swap: 1582360k swap-space > (priority -1) > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:07.2-1, > assigned address 2 > Jun 24 13:37:51 localhost kernel: usb.c: USB device 2 (vend/prod > 0x3f0/0x801) is not claimed by any active driver. > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1.2, > assigned address 3 > Jun 24 13:37:51 localhost kernel: usb.c: USB device 3 (vend/prod > 0x2821/0x5001) is not claimed by any active driver. > Jun 24 13:37:51 localhost kernel: usbdevfs: remount parameter error > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1.4, > assigned address 4 > Jun 24 13:37:51 localhost kernel: usb.c: USB device 4 (vend/prod > 0x3f0/0x3404) is not claimed by any active driver. > Jun 24 13:37:51 localhost kernel: hdc: attached ide-scsi driver. > Jun 24 13:37:51 localhost kernel: scsi1 : SCSI host adapter emulation > for IDE ATAPI devices > Jun 24 13:37:51 localhost kernel: Vendor: HP Model: CD-Writer+ > 8100 Rev: 1.0g > Jun 24 13:37:51 localhost kernel: Type: =20 > CD-ROM ANSI SCSI revision: 02 > Jun 24 13:37:51 localhost kernel: Initializing USB Mass Storage > driver... > Jun 24 13:37:51 localhost kernel: usb.c: registered new driver > usb-storage > Jun 24 13:37:51 localhost kernel: scsi2 : SCSI emulation for USB Mass > Storage devices > Jun 24 13:37:51 localhost kernel: Vendor: ASUS Model: > CRW-5224A Rev: 1.00 > Jun 24 13:37:51 localhost kernel: Type: =20 > CD-ROM ANSI SCSI revision: 02 > Jun 24 13:37:51 localhost kernel: USB Mass Storage support registered. > Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr0 at scsi0, > channel 0, id 4, lun 0 > Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr1 at scsi1, > channel 0, id 0, lun 0 > Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr2 at scsi2, > channel 0, id 0, lun 0 > Jun 24 13:37:51 localhost kernel: (scsi0:A:4): 10.000MB/s transfers > (10.000MHz, offset 32) > Jun 24 13:37:51 localhost kernel: sr0: scsi3-mmc drive: 0x/0x dvd-ram > cd/rw xa/form2 cdda tray > Jun 24 13:37:51 localhost kernel: Uniform CD-ROM driver Revision: 3.12 > Jun 24 13:37:51 localhost kernel: sr1: scsi3-mmc drive: 24x/24x writer > cd/rw xa/form2 cdda tray > Jun 24 13:37:51 localhost kernel: sr2: scsi-1 drive > Jun 24 13:37:51 localhost kernel: usb.c: registered new driver usblp > Jun 24 13:37:51 localhost kernel: printer.c: usblp0: USB Bidirectional > printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404 > Jun 24 13:37:51 localhost kernel: printer.c: v0.11: USB Printer Device > Class driver > Jun 24 13:37:51 localhost kernel: parport0: PC-style at 0x378 > [PCSPP,TRISTATE] > Jun 24 13:37:51 localhost kernel: ip_tables: (C) 2000-2002 Netfilter > core team > Jun 24 13:37:51 localhost kernel: ip_conntrack version 2.1 (6143 > buckets, 49144 max) - 292 bytes per conntrack > Jun 24 13:37:51 localhost kernel: Linux Tulip driver version > 0.9.15-pre12 (Aug 9, 2002) > Jun 24 13:37:51 localhost kernel: PCI: Found IRQ 11 for device 00:0c.0 >=20 > Jun 24 13:45:57 localhost kernel: ac97_codec: AC97 codec, id: TRA35 > (TriTech TR A5) > Jun 24 13:45:58 localhost modprobe: modprobe: Can't locate module > sound-service-0-3 > Jun 24 13:52:13 localhost modprobe: modprobe: Can't locate module > char-major-81 > Jun 24 13:52:35 localhost last message repeated 7 times > Jun 24 13:53:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:53:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x82 len 1 ret -110 > Jun 24 13:54:18 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:54:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x83 len 22 ret -110 > Jun 24 13:54:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:54:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x1 len 6 ret -110 > Jun 24 13:55:18 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:55:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x82 len 1 ret -110 > Jun 24 13:55:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:55:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x1 len 6 ret -110 > Jun 24 13:57:50 localhost modprobe: modprobe: Can't locate module > char-major-81 > Jun 24 13:57:50 localhost last message repeated 3 times >=20 > Jun 24 13:58:20 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:58:20 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x1 len 6 ret -110 > Jun 24 13:58:50 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:58:50 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x82 len 1 ret -110 > Jun 24 13:59:20 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:59:20 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x1 len 6 ret -110 >=20 > Jun 24 14:16:09 localhost gconfd (root-3450): Received signal 1, > shutting down cleanly >=20 > Jun 24 14:16:45 localhost rpc.statd[2040]: Caught signal 15, > un-registering and exiting.Jun 25 08:55:06=20 >=20 > Jun 25 08:55:06 localhost kernel: usb.c: registered new driver > usbscanner > Jun 25 08:55:06 localhost kernel: scanner.c: 0.4.12:USB Scanner Driver > Jun 25 08:55:06 localhost kernel: scanner.c: probe_scanner: User > specified USB scanner -- Vendor:Product - 1:2 >=20 > GENERIC KERNEL SCANNER DRIVER > Ensure that the access permissions for the USB device are set > appropri- > ately. We recommend to add a group "scanner" to /etc/group > which con- > tains all users that should have access to the scanner. The > permission > of the device should then be set to allow group read and write=20 > access. > For example, if the scanner is at USB device > /dev/usb/scanner0, then > the following two commands would set the permission correctly: > =20 > $ chgrp scanner /dev/usb/scanner0 > $ chmod 660 /dev/usb/scanner0 > =20 > If your scanner isn=E2=80=99t detected automatically by your opera= ting > system=E2=80=99s > scanner driver, you need to tell the kernel the vendor and > product ids > of your scanner. For Linux, this can be done with modprobe=20 > parameters: > First, remove the scanner module (rmmod scanner), then load it > again: > modprobe scanner vendor=3D0x0001 product=3D0x0002. Use the=20 > appropriate > vendor and product ids (e.g. from /var/log/messages, dmesg, > or cat > /proc/bus/usb/devices) > =20 >=20 > /usr/local/etc/sane.d/avision.conf > scsi AVISION > scsi FCPA > scsi MINOLTA > scsi MITSBISH MCA-S600C > scsi MITSBISH MCA-SS600 > scsi HP > scsi hp > scsi /dev/scanner > usb /dev/usbscanner > usb /dev/usb/scanner >=20 > [root@localhost root]# ls -l /dev/usb/scanner0 > crw------- 1 tom root 180, 48 Jan 30 02:24 > /dev/usb/scanner0 > [root@localhost root]# ls -l /dev/usbscanner > ls: /dev/usbscanner: No such file or directory > [root@localhost root]# ls -l /dev/usb/scanner > ls: /dev/usb/scanner: No such file or directory > [root@localhost root]# >=20 >=20 > /etc/fstab > none =09/proc/bus/usb =09=09usbfs defaults,devmode=3D0666 0 0 >=20 > /proc/bus/usb/devices > C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3D40 MxPwr=3D 0mA > I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver= =3Dhub > E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 8 Ivl=3D255ms > T: Bus=3D04 Lev=3D01 Prnt=3D01 Port=3D00 Cnt=3D01 Dev#=3D 2 Spd=3D12 M= xCh=3D 0 > D: Ver=3D 1.00 Cls=3D00(>ifc ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1 > P: Vendor=3D03f0 ProdID=3D0801 Rev=3D 0.01 > S: Manufacturer=3Dhp > S: Product=3Dhp scanjet 7400c > S: SerialNumber=3D87 tem 7400c =20 >=20 > /proc/bus/usb/drivers > usbdevfs > hub > 96-111: hiddev > hid > usb-storage > 0- 15: usblp > 48- 63: usbscanner >=20 >=20 >=20 >=20 > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel >=20 --=20 "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 From matt.lung@midwest-tool.com Wed Jun 25 20:16:23 2003 From: matt.lung@midwest-tool.com (Matt Lung) Date: Wed, 25 Jun 2003 14:16:23 -0500 Subject: [sane-devel] ScanJet 5300C question Message-ID: <3EF9F507.6040604@midwest-tool.com> I would like to use the ADF we have with our HP 5300C scanner under linux and Sane but I have yet to find any documentation or help on how to setup an ADF with this scanner. It scans just fine without it, but with out the ADF funcioning I'll be forced to use it in Windows forever. Is an ADF even supported with the HP 5300C? If so, where can I find information on how to do this? thanks for any help From tomf@sjpc.org Wed Jun 25 20:40:18 2003 From: tomf@sjpc.org (Thomas Frayne) Date: 25 Jun 2003 12:40:18 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: References: Message-ID: <1056570017.5677.24.camel@localhost.localdomain> On Wed, 2003-06-25 at 11:36, m. allan noah wrote: > tom, did you do an 'rpm -e --force --nodeps sane-backends' first? Yes. > > when you compiled the new sane backends, did you do: > > ./configure --prefix=/usr --sysconfdir=/etc No. I'll uninstall and verify that no sign of sane-backends remains, then install again. > make Yes. > make install Yes. > > if not, start with those two things. then we can be sure that the version > of sane you are using is the one you compiled. Thanks. I'll do it. > > allan > > On 25 Jun 2003, Thomas Frayne wrote: > > > On Tue, 2003-06-24 at 12:41, Henning Meier-Geinitz wrote: > > > Hi, > > > > Then I rebooted to determine if the scanner would be detected as a usb > > > > device. The hardware browser still showed no browser, and xsane found > > > > no scanner device on startup. > > > > > > > > How can I get the scanner recognized as a USB device? > > > > > > That's done automatically. If it's not detected as USB device by the > > > kernel, it can't be used by hpusbscsi. > > > > > > Is it found by sane-find-scanner as root? > > > Is it found by scanimage -L as root? > > > If yes, you may need to set up permissions for libusb correctly. > > > That's explained in man sane-usb. > > > > > > > Thanks. I read the manual, found that permissions were not set > > correctly, set them in fstab as recommended. Then sane-find-scanner and > > scanimage -L worked as a normal user. However, the scanner still does > > not work. I think I am closer, but I am lost. > > > > Messages indicated failure of usbdevfs, which is supposed to be > > obsolete. /usr/local/etc/sane.d/avision.conf lists devices which do not > > exist. I suspect that there is a mismatches among the sane > > configuration which was set up for the initial Redhat 9, the sane > > configuration set up when I installed sane-backends-1.0.12.tar.gz and > > xsane-0.91.tar.gz, and the kernel 2.4.20-18.9, which was upgraded by > > Up2date, but I can't figure out how to straighten it out. > > > > I'll keep trying. I have just done > > modprobe scanner vendor=0x0001 product=0x0002, > > and I plan to reboot and continue debugging, starting with why > > /dev/usbscanner does not exist. > > > > Any help would be appreciated. > > > > Tom Frayne > > From fsanta@arrakis.es Wed Jun 25 21:03:25 2003 From: fsanta@arrakis.es (fsanta) Date: Wed, 25 Jun 2003 22:03:25 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <20030625181101.GE9836@meier-geinitz.de> References: <200306251705.27766.fsanta@arrakis.es> <200306251834.17699.fsanta@arrakis.es> <20030625181101.GE9836@meier-geinitz.de> Message-ID: <200306252203.25459.fsanta@arrakis.es> Hi again. Just wondered if Oliver was still around who I think wrote the backend. As an iterim solution, I've gone back to SuSE 8.1 on the client where the scanner is and all is well. I'd just like all our clients to have the same OS for system consitency. Is there anyone from SuSE still on this list who could help me get the scanner going under 8.2? Thanks for your time and sorry to be such a pain as usual. Steve. On Wednesday 25 June 2003 20:11, Henning Meier-Geinitz wrote: > Hi, > > On Wed, Jun 25, 2003 at 06:34:17PM +0200, fsanta wrote: > > Could you tell me how to do that? > > To do what? Hint: If you quote the text you are referring to it's > easier to understand what you mean? :-) > > I don't have your scanner or your card so I don't have personal > experiences with this combination. But the "synchronous tranfer" SCSI > feature seems to make trouble with many older SCSI scanners. And your > kernel complains about it so it may be worth a try. Check the > documentation in the Linux source code. Which SCSI driver do you use > for the 2904? > > > the scsi card is a very basic 2904 which Oliver added to the database > > of usable cards way back years ago. The scsi terminator plug is > > missing on the scanner. Could it have anything to do with that? I > > can't test it as I haven't got an scsi terminator plug. > > As I said, I don't have experience with that combination, but my > scanners work without a terminator. At least if you have only one > device on the SCSI bus. > > > We removed it > > under 8.1 to produce acceptable scans. It was of very poor quality with. > > If adding/removing the terminator changes the quality of the scan > something is completely broken. A wrong termination can lead to SCSI > errors but I haven't heard about an influence on image quality. That > would mean only the data is corrupted, not the commands and the SCSI > system doesn't detect that (parity?). > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From tomf@sjpc.org Wed Jun 25 21:07:14 2003 From: tomf@sjpc.org (Thomas Frayne) Date: 25 Jun 2003 13:07:14 -0700 Subject: [sane-devel] ScanJet 5300C question In-Reply-To: <3EF9F507.6040604@midwest-tool.com> References: <3EF9F507.6040604@midwest-tool.com> Message-ID: <1056571633.5677.30.camel@localhost.localdomain> On Wed, 2003-06-25 at 12:16, Matt Lung wrote: ... > Is an ADF even supported with the HP 5300C? > > If so, where can I find information on how to do this? I am going through the same process for the HP 7450C. Try searching the archives for HP 7450C for some tips that may apply to you. If the connection is USB, you may need to upgrade sane-backends. I did this, and it looks like I am getting close, but I'm still not there yet. From henning@meier-geinitz.de Wed Jun 25 21:52:40 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 25 Jun 2003 22:52:40 +0200 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <1056560236.3843.853.camel@localhost.localdomain> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> Message-ID: <20030625205240.GA12653@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 09:57:17AM -0700, Thomas Frayne wrote: > Thanks. I read the manual, found that permissions were not set > correctly, set them in fstab as recommended. Then sane-find-scanner and > scanimage -L worked as a normal user. Is the scanner found as USB device now? Something like "libusb:001:002"? Please show us "sane-find-scanner -q". I have to admitt that I'm a bit confused by the backend. It uses USB interrupt transfers to get the status of the scanner. However that only works with libusb, not the kernel scanner driver. So I don't really know why the backend lists "usb /dev/ubs/scanner" in avision.conf. Maybe the maintainer can enlighten me :-) > However, the scanner still does not work. What exactly doesn't work? > Messages indicated failure of usbdevfs, which is supposed to be > obsolete. The name "usbdevfs" is obsolete. It's called "usbfs" now. But that's not your problem. > /usr/local/etc/sane.d/avision.conf lists devices which do not > exist. Usually the config files list all devices and device files the backend supports. So it doesn't matter if there are additional ones. The backend checks for all USB devices anymway, I don't think the entries in avsion.conf are necessary at all. > and xsane-0.91.tar.gz, and the kernel 2.4.20-18.9, Those two shouldn't matter. > I'll keep trying. I have just done > modprobe scanner vendor=0x0001 product=0x0002, These vendor and product ids are most probably wrong. If the scanner driver works at all, try something like this: rmmod scanner modprobe scanner vendor=0x03f0 product=0x0801 > and I plan to reboot and continue debugging, starting with why > /dev/usbscanner does not exist. Some distributions use(d) /dev/usbscanner, some use /dev/usb/scanner0. Shouldn't matter in your case. > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 > Jun 24 13:37:51 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. That's your scanner. It's ok that it's not "claimed by any active driver" because in this case it's used by usbfs (libusb). You can also try to load the USB scanner driver as mentioned above. Then you should get a message from that driver. > Jun 24 13:53:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:53:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 > Jun 24 13:54:18 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:54:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x83 len 22 ret -110 > Jun 24 13:54:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:54:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 > Jun 24 13:55:18 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:55:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 > Jun 24 13:55:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:55:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 That doesn't look good. Your scanner doesn't seem to accept any input on any endpoint (bulk in, out and interrupt). I recommend to unplug/replug your scanner before any test. Otherwise it may be confuded by eralier tests. > [root@localhost root]# ls -l /dev/usb/scanner0 > crw------- 1 tom root 180, 48 Jan 30 02:24 > /dev/usb/scanner0 That's ok. YOu can add a link /dev/usb/scanner to that one but I don't think it's necessary. > /proc/bus/usb/devices Those entries start with "T:" (topology). > 48- 63: usbscanner Is loaded but doesn't know about your scanner. Bye, Henning From kouno.hironori@pfu.fujitsu.com Thu Jun 26 01:50:23 2003 From: kouno.hironori@pfu.fujitsu.com (hironori kohno) Date: Thu, 26 Jun 2003 09:50:23 +0900 Subject: [sane-devel] Please let me know frontend which operates on "MacOS X". Message-ID: <200306260950.EJH42366.ISJPSPVPLOP.JO@pfu.fujitsu.com> Hello, I am developing the backend for MacOS X. If there is famous frontend which operates on MacOS X, please let me know some. Regards, Kouno -- kouno hironori kouno.hironori@pfu.fujitsu.com -- hironori kohno kouno.hironori@pfu.fujitsu.com From jollyprince@juno.com Thu Jun 26 02:30:22 2003 From: jollyprince@juno.com (jollyprince@juno.com) Date: Thu, 26 Jun 2003 01:30:22 GMT Subject: [sane-devel] Visioneer 5800 Message-ID: <20030625.183103.2373.545548@webmail01.lax.untd.com> I'm a newbie who just got his USB printer working and decided to tackle the scanner next. So far I've found the Vendor number and Product ID and inserted them into the modules.conf file. QUESTION: Is it a foregone conclusion that I need to recompile the kernel next or is there a scanner install that does not require kernel recompile? From crapsite@gmx.net Thu Jun 26 05:43:59 2003 From: crapsite@gmx.net (Michael Herder) Date: Thu, 26 Jun 2003 06:43:59 +0200 Subject: [sane-devel] Please let me know frontend which operates on "MacOS X". In-Reply-To: <200306260950.EJH42366.ISJPSPVPLOP.JO@pfu.fujitsu.com> References: <200306260950.EJH42366.ISJPSPVPLOP.JO@pfu.fujitsu.com> Message-ID: <20030626044233.1E98952@panda.mostang.com> hironori kohno, Donnerstag, 26. Juni 2003 02:50: > Hello, > > I am developing the backend for MacOS X. > If there is famous frontend which operates on MacOS X, > please let me know some. I don't know about famous ones, but some days back Trolltech released Qt/Mac under the GPL, therefore it should be possible to port QuiteInsane. It won't compile out of the box (in fact, I don't know, how platform dependent the code is), but if someone wants to try it, or already ported it, then please let me know. bb Michael http://www.trolltech.com/download/qt/mac.html http://sf.net/projects/quiteinsane From kouno.hironori@pfu.fujitsu.com Thu Jun 26 06:39:52 2003 From: kouno.hironori@pfu.fujitsu.com (hironori kohno) Date: Thu, 26 Jun 2003 14:39:52 +0900 Subject: [sane-devel] Please let me know frontend which operates on"MacOS X". In-Reply-To: <20030626044233.1E98952@panda.mostang.com> References: <200306260950.EJH42366.ISJPSPVPLOP.JO@pfu.fujitsu.com> <20030626044233.1E98952@panda.mostang.com> Message-ID: <200306261439.JEH62606.I.PVSJOPPOPJLS@pfu.fujitsu.com> <20030626044233.1E98952@panda.mostang.com> $B$N!"(B "Re: [sane-devel] Please let me know frontend which operates on"MacOS X"." $B$K$*$$$F!"(B "Michael Herder "$B$5$s$O=q$-$^$7$?!'(B > hironori kohno, Donnerstag, 26. Juni 2003 02:50: > > Hello, > > > > I am developing the backend for MacOS X. > > If there is famous frontend which operates on MacOS X, > > please let me know some. > > I don't know about famous ones, but some days back Trolltech released Qt/Mac > under the GPL, therefore it should be possible to port QuiteInsane. under the Qt/Mac, QuiteInsane. Thanks. > It won't compile out of the box (in fact, I don't know, how platform > >dependent the > code is), but if someone wants to try it, or already ported it, then please > let me know. > > bb > Michael > > http://www.trolltech.com/download/qt/mac.html > http://sf.net/projects/quiteinsane > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- kouno hironori kouno.hironori@pfu.fujitsu.com -- kouno hironori kouno.hironori@pfu.fujitsu.com From Martijn van Oosterhout Thu Jun 26 06:41:34 2003 From: Martijn van Oosterhout (Martijn van Oosterhout) Date: Thu, 26 Jun 2003 15:41:34 +1000 Subject: [sane-devel] Visioneer 5800 In-Reply-To: <20030625.183103.2373.545548@webmail01.lax.untd.com> References: <20030625.183103.2373.545548@webmail01.lax.untd.com> Message-ID: <20030626054133.GB26472@svana.org> --jho1yZJdad60DJr+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 26, 2003 at 01:30:22AM +0000, jollyprince@juno.com wrote: >=20 > I'm a newbie who just got his USB printer working and decided to tackle t= he scanner next. So far I've found the Vendor number and Product ID and in= serted them into the modules.conf file. >=20 > QUESTION: Is it a foregone conclusion that I need to recompile the kernel= next or is there a scanner install that does not require kernel recompile? Many of the modern drivers use libusb rather than a specific scanner module, so specific scanner modules are becoming a thing of the past. As long as you have usbfs compiled in, you should be fine. --=20 Martijn van Oosterhout http://svana.org/kleptog/ > "the West won the world not by the superiority of its ideas or values or > religion but rather by its superiority in applying organized violence. > Westerners often forget this fact, non-Westerners never do." > - Samuel P. Huntington --jho1yZJdad60DJr+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE++oeNY5Twig3Ge+YRApRUAKCGdUNVNxdHHOpP82gic+jRc4ywlwCgvc30 DUBcGNf2115bgjMNAHhYUEM= =Zdyy -----END PGP SIGNATURE----- --jho1yZJdad60DJr+-- From henning@meier-geinitz.de Thu Jun 26 08:44:35 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 26 Jun 2003 09:44:35 +0200 Subject: [sane-devel] Visioneer 5800 In-Reply-To: <20030625.183103.2373.545548@webmail01.lax.untd.com> References: <20030625.183103.2373.545548@webmail01.lax.untd.com> Message-ID: <20030626074435.GB26193@meier-geinitz.de> Hi, On Thu, Jun 26, 2003 at 01:30:22AM +0000, jollyprince@juno.com wrote: > I'm a newbie who just got his USB printer working and decided to > tackle the scanner next. So far I've found the Vendor number and > Product ID and inserted them into the modules.conf file. The scanner isn't even in our list of scanners. That usually means it is not supported by any SANE backend. Could you please give us any information you have about this scanner? Especially I'm interested in the output of "cat /proc/bus/usb/devices" while the scanner is plugged in. > QUESTION: Is it a foregone conclusion that I need to recompile the > kernel next No. modprobe scanner vendor=... product=... works the same way. Or just use libusb (without the scanner module). That's not the problem. If you tell me the vendor and product ids I'll add them to the kernel scanner driver. > or is there a scanner install that does not require kernel recompile? You don't need to recompile the kernel. But even recompilation doesn't help you because you need a SANE backend for yout scanner. And that's most probably not written yet. On how to write a backend see: http://www.meier-geinitz.de/sane/misc/unsupported.html Bye, Henning From henning@meier-geinitz.de Thu Jun 26 09:09:33 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 26 Jun 2003 10:09:33 +0200 Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: References: Message-ID: <20030626080933.GD26193@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 03:16:35PM +0200, Henrik Schmidt wrote: > I'm trying to use a Microtek ScanMaker III with Solaris 2.6 and the scg > SCSI driver. I'm using sane-backends 1.0.12 with frontend 1.0.10. I'm not sure how old this scanner is but as you can see in some recent threads on this list some scanners don't like "advanced" SCSI features like reconnect/disconnect or synchronous negotiation. Maybe it helps to turn them off in the SCSI driver or adapter BIOS. > The scanner is detected but as soon as I start a scan or prescan either > with xscanimage or xsane the application locks up. I get errors in > /var/adm/messages. After 2 minutes the applications return with a timeout > and i/o error. > Jun 25 13:08:25 cortex unix: data transfer overrun: current esp state: Hm, maybe the SCSI buffer is too big? Try setting the environment variable SANE_SG_BUFFER_SIZE to e.g. 32768. > I checked the scanner on a Windows computer and it did work. I checked it > on another computer with sane and it failed too. Also with Solaris? Same SCSI controller? At least for Solaris/x86 we have a positive report about a SCSI scanner working (with SANE 1.0.9). > I had it running some a ago. When I moved the computer to a different > location I updated sane and it failed to work afterwards. Going back to > older sane backend versions (up to 1.0.8) didn't help either. Then it doesn't look like a SANE problem, does it? > I tried to contact both the microtek backend coder as well as the contact > in README.solaris but got no reply. Matthew Marjanovic posted some days ago on this list. Maybe you can try it again? Bye, Henning From hbs@ks.informatik.uni-kiel.de Thu Jun 26 10:45:02 2003 From: hbs@ks.informatik.uni-kiel.de (Henrik Schmidt) Date: Thu, 26 Jun 2003 11:45:02 +0200 (MEST) Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: <20030626080933.GD26193@meier-geinitz.de> References: <20030626080933.GD26193@meier-geinitz.de> Message-ID: On Thu, 26 Jun 2003, Henning Meier-Geinitz wrote: > Hm, maybe the SCSI buffer is too big? Try setting the environment > variable SANE_SG_BUFFER_SIZE to e.g. 32768. > This didn't help. > > I checked the scanner on a Windows computer and it did work. I checked it > > on another computer with sane and it failed too. > > Also with Solaris? Same SCSI controller? > Yes. > At least for Solaris/x86 we have a positive report about a SCSI > scanner working (with SANE 1.0.9). > > > I had it running some a ago. When I moved the computer to a different > > location I updated sane and it failed to work afterwards. Going back to > > older sane backend versions (up to 1.0.8) didn't help either. > > Then it doesn't look like a SANE problem, does it? > I don't know. As the scg driver is working on the computer (I can use a cdrecorder with cdrecord) and the scanner is working too my rough guess was that sane might be involved. > > I tried to contact both the microtek backend coder as well as the contact > > in README.solaris but got no reply. > > Matthew Marjanovic posted some days ago on this list. Maybe you can > try it again? > Ok, will try. Here is the critical section of the debug output from xscanimage : [microtek] .download_gamma... [microtek] .download_gamma: 4096 entries of 2 bytes, max 255 [microtek] .download_gamma: by default [microtek] .mode_select 8... [microtek] .mode_select: pap_len: 8399 [microtek] .mode_select_1 8... [microtek] .wait_ready 8... [microtek] .start_scan... [microtek] .get_scan_status 8... [microtek] get_scan_status(6): 0, 300, 504 -> #0 [microtek] > 0 2c 1 f8 1 0 [microtek] Scan Param: [microtek] pix bpl: 894 hdr bpl: 6 ppl: 298 [microtek] undel bytes: 450576 unscan lines: 504 planes: 3 [microtek] dest bpl: 894 dest ppl: 298 aspect: 1.000000 [microtek] sane_get_parameters... [microtek] sane_set_io_mode... [microtek] sane_read... [microtek] read_from_scanner... [microtek] .get_scan_status 8... [microtek] get_scan_status(6): 0, 300, 504 -> #0 [microtek] > 0 2c 1 f8 1 0 [microtek] read_from_scanner: gss busy, linewidth, remaining: 0, 300, 504 [microtek] sane_read: max_scsi: 145, rem: 504, nlines: 145 [microtek] .read_scan_data... [microtek] sane_read: bad read_scan_data! [microtek] sane_read: read_from_scanner failed. [microtek] end_scan... [microtek] .stop_scan... [sanei_scsi] sanei_scsi_cmd 1b: timeout From fsanta@arrakis.es Thu Jun 26 16:19:07 2003 From: fsanta@arrakis.es (fsanta) Date: Thu, 26 Jun 2003 17:19:07 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <20030625152250.GA9836@meier-geinitz.de> References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> Message-ID: <200306261719.07135.fsanta@arrakis.es> > > > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > > synchronous negotiation. Using asynchronous transfers > > Try disabling synchronous transfers in your SCSI driver or the BIOS > (but I guess your SCSI controller doesn't have a BIOS). > Hi. Could anyone tell me how to do this. . ."disabling synchronous transfers in your SCSI driver or the BIOS..." THanks, Steve. From henning@meier-geinitz.de Thu Jun 26 16:54:19 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 26 Jun 2003 17:54:19 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <200306261719.07135.fsanta@arrakis.es> References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> <200306261719.07135.fsanta@arrakis.es> Message-ID: <20030626155419.GE26193@meier-geinitz.de> Hi, On Thu, Jun 26, 2003 at 05:19:07PM +0200, fsanta wrote: > Hi. Could anyone tell me how to do this. . ."disabling synchronous transfers > in your SCSI driver or the BIOS..." I've tried to explain that in my other mail: "I don't have your scanner or your card so I don't have personal experiences with this combination. But the "synchronous tranfer" SCSI feature seems to make trouble with many older SCSI scanners. And your kernel complains about it so it may be worth a try. Check the documentation in the Linux source code. Which SCSI driver do you use for the 2904?" I really don't know which SCSI driver you use. Check the README for that SCSI driver or the code itsself. If tell us which driver you use, maybe someone else knows the details. I don't think your SCSI adapter has a BIOS. But it's your hardware so you should know better :-) Bye, Henning From a.deuring@satzbau-gmbh.de Thu Jun 26 18:09:10 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Thu, 26 Jun 2003 19:09:10 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> <200306261719.07135.fsanta@arrakis.es> <20030626155419.GE26193@meier-geinitz.de> Message-ID: <3EFB28B6.E1B6AE83@satzbau-gmbh.de> Henning Meier-Geinitz wrote: > > Hi, > > On Thu, Jun 26, 2003 at 05:19:07PM +0200, fsanta wrote: > > Hi. Could anyone tell me how to do this. . ."disabling synchronous transfers > > in your SCSI driver or the BIOS..." > > I've tried to explain that in my other mail: > > "I don't have your scanner or your card so I don't have personal > experiences with this combination. But the "synchronous tranfer" SCSI > feature seems to make trouble with many older SCSI scanners. And your > kernel complains about it so it may be worth a try. Check the > documentation in the Linux source code. Which SCSI driver do you use > for the 2904?" > > I really don't know which SCSI driver you use. Check the README for > that SCSI driver or the code itsself. If tell us which driver you use, > maybe someone else knows the details. > > I don't think your SCSI adapter has a BIOS. But it's your hardware so > you should know better :-) Bad luck, I'm afraid. The Adaptec 2904 needs the aic7xxx driver, and that driver has no parameter "disable disconnect". At least the file README.aic7xxx from the Linux 2.4.18 kernel does not mention such an option. Abel From a.deuring@satzbau-gmbh.de Thu Jun 26 20:58:59 2003 From: a.deuring@satzbau-gmbh.de (abel deuring) Date: Thu, 26 Jun 2003 21:58:59 +0200 Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: References: Message-ID: <3EFB5083.3090208@gmx.net> Henrik Schmidt schrieb: > I'm trying to use a Microtek ScanMaker III with Solaris 2.6 and the scg > SCSI driver. I'm using sane-backends 1.0.12 with frontend 1.0.10. > > Jun 25 13:08:25 cortex unix: WARNING: > /iommu@f,e0000000/sbus@f,e0001000/espdma@f > ,400000/esp@f,800000 (esp0):^M^M > Jun 25 13:08:25 cortex unix: data transfer overrun: current esp state: ^^^^^^^^^^^^^^^^^^^^^ [...] > Jun 25 13:08:25 cortex unix: esp: Cmd dump for Target 5 Lun > 0:^M^M > Jun 25 13:08:25 cortex unix: esp: cdblen=6, cdb=[ 0x8 0x0 > 0x0 0x0 > 0x91 0x0 ]^M^M That's a READ of just 0x91 (145) bytes; shouldn't cause any buffer overflow, but it's an odd number of bytes. A long shot: It could be that the SCG driver does not like to transfer an odd number of bytes. Matt and Henrik, I'm admittedly too lazy to look closer into the Microtek backend, but I guess that it is trying to read a complete scan line with one SCSI command. Would it be difficult to change this behaviour to read an even number of bytes? Henrik, a test of my guess should not be too difficult: Just select a scan window with an even number of horizontal pixels. (Or perhaps better choose a multiple of 4 or 8 as the scan width, just in case that the SCG driver or some other Solaris part insists on using the complete bus width of 32 or 64 bit) Abel PS: If my guess is right, a number of backends would need to be modified, I'm afraid... From pinguellis@yahoo.co.uk Thu Jun 26 22:08:53 2003 From: pinguellis@yahoo.co.uk (Steven Ellis) Date: Thu, 26 Jun 2003 14:08:53 -0700 (PDT) Subject: [sane-devel] Visioneer 5800 In-Reply-To: <20030626074435.GB26193@meier-geinitz.de> Message-ID: <20030626210853.80375.qmail@web80512.mail.yahoo.com> --- Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 26, 2003 at 01:30:22AM +0000, > jollyprince@juno.com wrote: > > I'm a newbie who just got his USB printer working > and decided to > > tackle the scanner next. So far I've found the > Vendor number and > > Product ID and inserted them into the modules.conf > file. > > The scanner isn't even in our list of scanners. That > usually means it > is not supported by any SANE backend. This is a 48bit scanner and as such won't work with the viceo backend (http://viceo.orcon.net.nz) that supports E3 and E4 chipset families. Its probably E5 which appears to be LM9832 based but you will need to open your scanner to confirm this. Steve ===== -- If you listen very carefully you can sometimes hear the dolphins sing pinguellis@yahoo.co.uk __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From pinguellis@yahoo.co.uk Thu Jun 26 22:10:26 2003 From: pinguellis@yahoo.co.uk (Steven Ellis) Date: Thu, 26 Jun 2003 14:10:26 -0700 (PDT) Subject: [sane-devel] Tips on migrating an existing driver to use libusb? Message-ID: <20030626211026.45297.qmail@web80511.mail.yahoo.com> Are there any useful tips or an FAQ on migrating a scanner driver over to use libusb. It would be nice to get the viceo (http://viceo.orcon.net.nz) driver to work without using a special patch for scanner.c/h and a recompile of the modules. Steve ===== -- If you listen very carefully you can sometimes hear the dolphins sing pinguellis@yahoo.co.uk __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From gnawa@libero.it Thu Jun 26 22:58:11 2003 From: gnawa@libero.it (gnawa) Date: Thu, 26 Jun 2003 23:58:11 +0200 Subject: [sane-devel] hi! Message-ID: <200306262358.11927.gnawa@libero.it> hi to all! i'm a italian guy (with poor english...) and i'm going to do the biggest th= ing that i ever programmed... a driver for my scanner hp scanjet 2300c =2E..but i have no idea from where to begin :( so if anyone can help me... thank you gnawa ps in italian: se c'=E8 qualche italiano che pu=F2 aiutarmi (non con l'ingl= ese...)=20 in questa impresa o l'ha gi=E0 cominciata o esiste gi=E0 un driver funziona= nte per il mio scanner gli sar=F2 molto grato... anche solo per dirmi con cosa= =20 cominciare... ciao From henning@meier-geinitz.de Thu Jun 26 22:56:39 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 26 Jun 2003 23:56:39 +0200 Subject: [sane-devel] Tips on migrating an existing driver to use libusb? In-Reply-To: <20030626211026.45297.qmail@web80511.mail.yahoo.com> References: <20030626211026.45297.qmail@web80511.mail.yahoo.com> Message-ID: <20030626215639.GC902@meier-geinitz.de> Hi, On Thu, Jun 26, 2003 at 02:10:26PM -0700, Steven Ellis wrote: > Are there any useful tips or an FAQ on migrating a > scanner driver over to use libusb. It would be nice to > get the viceo (http://viceo.orcon.net.nz) driver to > work without using a special patch for scanner.c/h and > a recompile of the modules. I don't have a howto but the sanei_usb API is pretty simple and explained here: http://sanei.meier-geinitz.de/sanei__usb_8h.html The assumptions are: - not more than one endpoint of each type: bulk-in, bulk-out, interrupt - interrupt endpoint access works only with libusb 1) sanei_usb_init 2a) call sanei_usb_attach_matching_devices with the "usb" lined from your config file or 2b) call sanei_usb_find_devices for any of the scanners you support 3) sanei_usb_open the device that was selected by the user 4) call sanei_usb_read_bulk, write_bulk or control_msg as you need 5) sanei_usb_close Bye, Henning From cpinto@yimports.com Fri Jun 27 02:31:03 2003 From: cpinto@yimports.com (Celso Pinto) Date: 27 Jun 2003 02:31:03 +0100 Subject: [sane-devel] HP2300C Message-ID: <1056677463.8138.11.camel@cpinto> Hi all, finally I had some time to get into the research/development of a driver for HP 2300C scanner. Because I have no experience in development for Linux/SANE drivers, I was wondering if there's some kind of HOWTO or a quick crash course for developing scanner drivers. I downloaded a couple of other projects but they fail as a tutorial because there isn't much "green code" (source comments) on them and i'm having a really hard time trying to figure out what those lines of code are supposed to do. Can anyone please help? I already have USB log file for scanning an image so i'm really keen on getting my hands dirty. Also, I noticed all projects use C instead of C++. Is there a major reason for this? Thanks for your time, Celso From Martijn van Oosterhout Fri Jun 27 03:05:34 2003 From: Martijn van Oosterhout (Martijn van Oosterhout) Date: Fri, 27 Jun 2003 12:05:34 +1000 Subject: [sane-devel] HP2300C In-Reply-To: <1056677463.8138.11.camel@cpinto> References: <1056677463.8138.11.camel@cpinto> Message-ID: <20030627020534.GD15876@svana.org> --UFHRwCdBEJvubb2X Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 27, 2003 at 02:31:03AM +0100, Celso Pinto wrote: > Hi all, >=20 > finally I had some time to get into the research/development of a driver > for HP 2300C scanner. >=20 > Because I have no experience in development for Linux/SANE drivers, I > was wondering if there's some kind of HOWTO or a quick crash course for > developing scanner drivers. I downloaded a couple of other projects but > they fail as a tutorial because there isn't much "green code" (source > comments) on them and i'm having a really hard time trying to figure out > what those lines of code are supposed to do.=20 Well, I basically pulled up the driver for one of the other HP scanners. I pinched the code (with acknowledgements of course) that read the config file, accessed the USB device and implemented the SANE API. That meant I only had to write code to implement the actual protocol. Initially you'll have lots of constants as you try to replicate the various protocol elrement. I suggest working as a standalone program until you at least pull down a preview image. That saves you the hassle of dealing with the SANE interface until you actually have image to show. > Also, I noticed all projects use C instead of C++. Is there a major > reason for this? Until recently the C++ compilers have been slightly flakey. Straight C tends to be more portable too. Historical accident mostly. Good luck! Hope this helps, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > "the West won the world not by the superiority of its ideas or values or > religion but rather by its superiority in applying organized violence. > Westerners often forget this fact, non-Westerners never do." > - Samuel P. Huntington --UFHRwCdBEJvubb2X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE++6ZuY5Twig3Ge+YRAieYAJoCqmGL5+2PChjh8NFftjVqqcvdOQCghk8n ekJmCrS3u0Yzi58v9A38NVQ= =iQOv -----END PGP SIGNATURE----- --UFHRwCdBEJvubb2X-- From fsanta@arrakis.es Fri Jun 27 06:54:03 2003 From: fsanta@arrakis.es (fsanta) Date: Fri, 27 Jun 2003 07:54:03 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <20030626155419.GE26193@meier-geinitz.de> References: <200306251705.27766.fsanta@arrakis.es> <200306261719.07135.fsanta@arrakis.es> <20030626155419.GE26193@meier-geinitz.de> Message-ID: <200306270754.03409.fsanta@arrakis.es> Hi Henning I fully understand that you don't have my scenner combination. I don't think anyone else has anymore apart from perhaps the writer of the Xsane frontend. I posted to the list on the off chance that others may be able to help me. As Sane has matured there seem to be fewer and fewer people subscribed to the list. My driver is the aic7xxx and it works fine under SuSE 8.1 Cheers, Steve. On Thursday 26 June 2003 17:54, Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 26, 2003 at 05:19:07PM +0200, fsanta wrote: > > Hi. Could anyone tell me how to do this. . ."disabling synchronous > > transfers in your SCSI driver or the BIOS..." > > I've tried to explain that in my other mail: > > "I don't have your scanner or your card so I don't have personal > experiences with this combination. But the "synchronous tranfer" SCSI > feature seems to make trouble with many older SCSI scanners. And your > kernel complains about it so it may be worth a try. Check the > documentation in the Linux source code. Which SCSI driver do you use > for the 2904?" > > I really don't know which SCSI driver you use. Check the README for > that SCSI driver or the code itsself. If tell us which driver you use, > maybe someone else knows the details. > > I don't think your SCSI adapter has a BIOS. But it's your hardware so > you should know better :-) > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From kouno.hironori@pfu.fujitsu.com Fri Jun 27 08:48:38 2003 From: kouno.hironori@pfu.fujitsu.com (hironori kohno) Date: Fri, 27 Jun 2003 16:48:38 +0900 Subject: [sane-devel] [sane-devel]The report about 'sane-fujitsu' Message-ID: <200306271648.FEE65799.SOPPLP.PVJSIJO@pfu.fujitsu.com> Hi, I performed testing about 'sane-fujitsu'. It reports below. OS: RedHat Linux V8 Scanner: fi-4220C Indication matters: 1. color-mode When scan is carried out by color-mode, the information on a color differs from an actual manuscript. ex.A red paper is expressed as a yellow picture. 2. resolution A maximum of 600 dpi is appropriate to x resolution of fi-4x20 scanner. The maximum of y resolution can be specified to 600dpi. 3. rif (reverse image format) i want you to support not by rif but by SANE_NAME_NEGATIVE. i do not set up by rif of scanner I/F, but want you to be reversed to an actual picture color. 4. halftone-mode A picture cannot be taken even if it specifies the mode of halftone. 5. paper-size "A3" and "double" are not supporting. 6. Start button How to use start-button is not known. Bye, Kouno -- kouno.hironori@pfu.fujitsu.com -- kouno.hironori@pfu.fujitsu.com From henning@meier-geinitz.de Fri Jun 27 09:38:32 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 10:38:32 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <200306270754.03409.fsanta@arrakis.es> References: <200306251705.27766.fsanta@arrakis.es> <200306261719.07135.fsanta@arrakis.es> <20030626155419.GE26193@meier-geinitz.de> <200306270754.03409.fsanta@arrakis.es> Message-ID: <20030627083832.GA2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 07:54:03AM +0200, fsanta wrote: > I fully understand that you don't have my scenner combination. I don't think > anyone else has anymore apart from perhaps the writer of the Xsane frontend. > I posted to the list on the off chance that others may be able to help me. As > Sane has matured there seem to be fewer and fewer people subscribed to the > list. 580 subscribers currently + 133 getting the digest. > My driver is the aic7xxx and it works fine under SuSE 8.1 There are two aic7xxx drivers. In 2.4.21 they are called aic7xxx and aic7xxx_old. Maybe SuSE 8.1 used the older driver? Maybe you can load it instead of the other one? Bye, Henning From henning@meier-geinitz.de Fri Jun 27 09:42:32 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 10:42:32 +0200 Subject: [sane-devel] hi! In-Reply-To: <200306262358.11927.gnawa@libero.it> References: <200306262358.11927.gnawa@libero.it> Message-ID: <20030627084232.GB2318@meier-geinitz.de> Hi, On Thu, Jun 26, 2003 at 11:58:11PM +0200, gnawa wrote: > i'm a italian guy (with poor english...) and i'm going to do the biggest thing > that i ever programmed... a driver for my scanner hp scanjet 2300c > ...but i have no idea from where to begin :( so if anyone can help me... Some hours after your posting Celso Pinto wrote to sane-devel that he wants to start a backend: http://www.mostang.com/pipermail/sane-devel/2003-June/019271.html So maybe you can work together on this project? Bye, Henning From henning@meier-geinitz.de Fri Jun 27 10:26:41 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 11:26:41 +0200 Subject: [sane-devel] HP2300C In-Reply-To: <1056677463.8138.11.camel@cpinto> References: <1056677463.8138.11.camel@cpinto> Message-ID: <20030627092641.GC2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 02:31:03AM +0100, Celso Pinto wrote: > finally I had some time to get into the research/development of a driver > for HP 2300C scanner. "gnawa" also wants to write a driver for this scanner, see http://www.mostang.com/pipermail/sane-devel/2003-June/019269.html . Maybe you can help each other? > Because I have no experience in development for Linux/SANE drivers, I > was wondering if there's some kind of HOWTO or a quick crash course for > developing scanner drivers. Not really. General documentation and some tips are in doc/backend-writing.txt. I also think you should start with a simple program that inncludes sanei_usb.c. You can do the SANE interface stuff later. The sanei internal functions are explained here: http://sanei.meier-geinitz.de/ > I downloaded a couple of other projects but > they fail as a tutorial because there isn't much "green code" (source > comments) on them and i'm having a really hard time trying to figure out > what those lines of code are supposed to do. * in sane_init, read the config file and detect the available scanners * in sane_open, do any preliminary work like loading the firmware, heating up the lamp * in sane_start start the actual scan (e.g. set up the geometry, do calibration, start the scan slider) * in sane_read get the scan data * sane_cancel stops the scan and resets everything necesary in the scanner Could you identify which chipset this scanner uses? Could you add some testing code to the check-usb-scanner utility at http://www.meier-geinitz.de/sane/check-usb-scanner/ ? That way we could identify other similar scanners easier. > Can anyone please help? I already have USB log file for scanning an > image so i'm really keen on getting my hands dirty. Try to find out what the USB log means, e.g. which part are commands, which are data. Try to send them from Linux and check if they do what you think. > Also, I noticed all projects use C instead of C++. Is there a major > reason for this? I don't think C++ was wiedely used when SANE was born. C++ is just too young. To many incompatibilities and interface changes. We'd need compatible C++ compilers on all platforms supported by SANE. Even with C, there are quite some portability problems, I don't want to know hwt would happen if we used C++. Bye, Henning From jollyprince@juno.com Fri Jun 27 12:04:15 2003 From: jollyprince@juno.com (jollyprince@juno.com) Date: Fri, 27 Jun 2003 11:04:15 GMT Subject: [sane-devel] What next? Message-ID: <20030627.040444.754.120095@webmail06.lax.untd.com> [root@localhost roger]# scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [root@localhost roger]# sane-find-scanner found USB scanner (vendor=0x04a7, product=0x0226) at libusb:005:002 # A USB device was detected. This program can't be sure if it's really # a scanner. If it is your scanner, it may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. NOTE: "scanimage -L" finds no scanners and suggests that I run "sane-find-scanner" which identifies vendor as 0x04a7 (Visioneer) and product as 0x0226 (Model 5800). When I run xsane, it says no devices available. So I've come a long way but no cigar. HELP! From henning@meier-geinitz.de Fri Jun 27 12:35:22 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 13:35:22 +0200 Subject: [sane-devel] What next? In-Reply-To: <20030627.040444.754.120095@webmail06.lax.untd.com> References: <20030627.040444.754.120095@webmail06.lax.untd.com> Message-ID: <20030627113522.GF2318@meier-geinitz.de> Hi, there is no need to send a copy of every email to me, I'm reading the sane-devel list. On Fri, Jun 27, 2003 at 11:04:15AM +0000, jollyprince@juno.com wrote: > [root@localhost roger]# scanimage -L [not found] > [root@localhost roger]# sane-find-scanner > > found USB scanner (vendor=0x04a7, product=0x0226) at libusb:005:002 Ok. > NOTE: "scanimage -L" finds no scanners and suggests that I run > "sane-find-scanner" which identifies vendor as 0x04a7 (Visioneer) and > product as 0x0226 (Model 5800). Yes, that's ok. sane-find-scanner should find every scanner. > When I run xsane, it says no devices available. So I've come a long > way but no cigar. HELP! You'll get the cigar when you have written the SANE driver for this scanner. As mentioned in my previous mail, there is most probably no driver yet for this scanner. For writing a driver see: http://www.meier-geinitz.de/sane/misc/unsupported.html Even if you don't want to write a driver, please show us the output of "cat /proc/bus/usb/devices" when your scanner is plugged in. Bye, Henning From hbs@ks.informatik.uni-kiel.de Fri Jun 27 12:37:58 2003 From: hbs@ks.informatik.uni-kiel.de (Henrik Schmidt) Date: Fri, 27 Jun 2003 13:37:58 +0200 (MEST) Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: <3EFB5083.3090208@gmx.net> References: <3EFB5083.3090208@gmx.net> Message-ID: On Thu, 26 Jun 2003, abel deuring wrote: > Henrik Schmidt schrieb: > > I'm trying to use a Microtek ScanMaker III with Solaris 2.6 and the scg > > SCSI driver. I'm using sane-backends 1.0.12 with frontend 1.0.10. > > > > > Jun 25 13:08:25 cortex unix: WARNING: > > /iommu@f,e0000000/sbus@f,e0001000/espdma@f > > ,400000/esp@f,800000 (esp0):^M^M > > Jun 25 13:08:25 cortex unix: data transfer overrun: current esp state: > ^^^^^^^^^^^^^^^^^^^^^ > [...] > > Jun 25 13:08:25 cortex unix: esp: Cmd dump for Target 5 Lun > > 0:^M^M > > Jun 25 13:08:25 cortex unix: esp: cdblen=6, cdb=[ 0x8 0x0 > > 0x0 0x0 > > 0x91 0x0 ]^M^M > > That's a READ of just 0x91 (145) bytes; shouldn't cause any buffer > overflow, but it's an odd number of bytes. A long shot: It could be that > the SCG driver does not like to transfer an odd number of bytes. > > Matt and Henrik, I'm admittedly too lazy to look closer into the > Microtek backend, but I guess that it is trying to read a complete scan > line with one SCSI command. Would it be difficult to change this > behaviour to read an even number of bytes? > > Henrik, a test of my guess should not be too difficult: Just select a > scan window with an even number of horizontal pixels. (Or perhaps better > choose a multiple of 4 or 8 as the scan width, just in case that the SCG > driver or some other Solaris part insists on using the complete bus > width of 32 or 64 bit) > I did test and get the same error with a very small 8x12 scan window. -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs@ks.informatik.uni-kiel.de From henning@meier-geinitz.de Fri Jun 27 13:12:55 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 14:12:55 +0200 Subject: [sane-devel] What next? In-Reply-To: <20030627.070149.1480.0.jollyprince@juno.com> References: <20030627.070149.1480.0.jollyprince@juno.com> Message-ID: <20030627121255.GG2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 07:01:49AM -0500, Roger O Wales wrote: > If it's possible to use libusb instead of spedific scanner modules > wouldn't this be quicker and if so, how does one proceed? I guess that may be of interest for the mailing list so I'm cc'ing it. Generally speaking, it should be possible to access any scanner using libusb. libusb is just a way to access the generic USB driver in usbfs. How do you do it? Just unload any specific drivers (rmmod scanner) and make sure that the kernel has support for the "Preliminary USB device filesystem" and that filesystem in mounted. That's the default for most distributions nowerdays. For access as non-root, see man sane-usb. But usually libusb or the kernel scanner driver is not the problem. What is needed is a SANE driver for the specific scanner. It doesn't matter if libusb or the scanner driver is used in most situations. Bye, Henning From hshane@austin.rr.com Fri Jun 27 13:14:23 2003 From: hshane@austin.rr.com (Howard Shane) Date: Fri, 27 Jun 2003 07:14:23 -0500 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP References: Message-ID: <3EFC351F.50508@austin.rr.com> I've visited the libusb site, and the only documentation available seems to be for developers. If someone can point me to more user-oriented information I'll be happy to include it. I assume it's out of the beta phase? Are there distribution manufacturers including it in their stable branches of binaries? Thanks, hs m. allan noah wrote: > it seems to me, that if you want your document to be more future-proof, > you would spend some more time talking about using libusb instead of the > kernel scanner driver, which is likely to be removed in later kernels (as > libusb becomes more stable) > > until then, i would likely re-name section 3 to 'OS support' instead of > kernel support, and make two usb entries, one for kernel and one for > libusb. > > then, to keep things consistent, you would have to add a libusb section to > 4.2. > > allan > > On Tue, 24 Jun 2003, Howard Shane wrote: > > >>...is available for viewing at >> >>http://66.25.191.66/docs/HOWTOS/Scanner/index.html >> >>I've tried to incorporate everyone's corrections and suggestions >>wherever possible. For any remaining omissions or errata please let me know. >> >>Thanks! >> >>_______________________________________________ >>Sane-devel mailing list >>Sane-devel@www.mostang.com >>http://www.mostang.com/mailman/listinfo/sane-devel >> > > From henning@meier-geinitz.de Fri Jun 27 13:35:14 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 14:35:14 +0200 Subject: [sane-devel] What next? In-Reply-To: <20030627.071830.1480.1.jollyprince@juno.com> References: <20030627.071830.1480.1.jollyprince@juno.com> Message-ID: <20030627123514.GH2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 07:18:30AM -0500, Roger O Wales wrote: > Granting that I'm a newbie which course of action gets me there quickest? If you would quote the part of the mail you are talking about I may understand what you want to achieve :-) And please write to the mailing list, not to me personally. I'm adding a cc: to sane-devel again. So what do you want to achieve? What doesn't work when you do what I told you? What did you do until now? What scanner do you use? Which operating system? Which version of SANE? With supported scanners and recent Linux distributions your USB scanner should just work out-of-the-box. Bye, Henning From henning@meier-geinitz.de Fri Jun 27 14:28:46 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 15:28:46 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EFC351F.50508@austin.rr.com> References: <3EFC351F.50508@austin.rr.com> Message-ID: <20030627132846.GI2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 07:14:23AM -0500, Howard Shane wrote: > I've visited the libusb site, and the only documentation available seems > to be for developers. If someone can point me to more user-oriented > information I'll be happy to include it. I assume it's out of the beta > phase? Are there distribution manufacturers including it in their stable > branches of binaries? As far as I kno all Linux distributions include libusb. Libusb is a library to access generic USB devices. It uses the operating system generic USB driver and how that works exactly depends on the operating system. The only thing the user needs to know is that he can only use libusb access if no other kernel driver is attached to the speicfic device. In case of Linux, that means "rmmod scanner". For permission issues and other details look at man sane-usb. Maybe a pointer to that man page is sufficiant. Bye, Henning From till.kamppeter@gmx.net Fri Jun 27 14:50:58 2003 From: till.kamppeter@gmx.net (Till Kamppeter) Date: Fri, 27 Jun 2003 15:50:58 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EFC351F.50508@austin.rr.com> References: <3EFC351F.50508@austin.rr.com> Message-ID: <3EFC4BC2.1000300@gmx.net> Howard Shane wrote: > I've visited the libusb site, and the only documentation available seems > to be for developers. If someone can point me to more user-oriented > information I'll be happy to include it. I assume it's out of the beta > phase? Are there distribution manufacturers including it in their stable > branches of binaries? Mandrake contains libusb since 9.0 or so. SANE and libgphoto2 of Mandrake Linux 9.1 are compiled with libusb support. To use libusb with binary packages, the "libusb*" package has to be installed with urpmi libusb For compiling programs using libusb you need also the "libusb*-devel" package which can be installed with urpmi libusb-devel I don“t have info about other distros (I work as developer at MandrakeSoft), but if Debian ships libusb my guess is that one installs it with apt-get install libusb apt-get install libusb-dev I hope this helps. Till From jollyprince@juno.com Fri Jun 27 16:43:46 2003 From: jollyprince@juno.com (Roger O Wales) Date: Fri, 27 Jun 2003 10:43:46 -0500 Subject: [sane-devel] What next? Message-ID: <20030627.104346.1436.0.jollyprince@juno.com> On Fri, 27 Jun 2003 14:35:14 +0200 Henning Meier-Geinitz writes: > Hi, > > On Fri, Jun 27, 2003 at 07:18:30AM -0500, Roger O Wales wrote: > > Granting that I'm a newbie which course of action gets me there > quickest? > > If you would quote the part of the mail you are talking about I may > understand what you want to achieve :-) And please write to the > mailing list, not to me personally. I'm adding a cc: to sane-devel > again. I get it. I've been replying to the sender instead of sane-devl.. > So what do you want to achieve? What doesn't work when you do what > I told you? What did you do until now? What scanner do you use? Which > operating system? Which version of SANE? I can answer a few of your questions. I use Visioneer OneTouch 5800 on a Mandrake 9.1 operating system. I have a scanner0 at /dev/usb I believe I hace an unsupported scanner. sane-find-scanner found USB scanner vendor=0x04a7 (Visioneer) and product=0x0226 (Model 5800). I have inserted these into /etc/modules.conf. > With supported scanners and recent Linux distributions your USB scanner should just work out-of-the-box. Since I don't have that luxury, I have to choose to write a SANE driver for Visioneer 5800 or try to use a generic libusb driver. I don't know how to do either one of these, so I must call for HELP! From henning@meier-geinitz.de Fri Jun 27 17:24:16 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 18:24:16 +0200 Subject: [sane-devel] What next? In-Reply-To: <20030627.104346.1436.0.jollyprince@juno.com> References: <20030627.104346.1436.0.jollyprince@juno.com> Message-ID: <20030627162416.GK2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 10:43:46AM -0500, Roger O Wales wrote: > > So what do you want to achieve? What doesn't work when you do what > > I told you? What did you do until now? What scanner do you use? Which > > operating system? Which version of SANE? > > I can answer a few of your questions. I use Visioneer OneTouch 5800 on a > Mandrake 9.1 operating system. That one is unsupported by SANE as far as we know. > I have a scanner0 at /dev/usb I believe > I hace an unsupported scanner. sane-find-scanner found USB scanner > vendor=0x04a7 (Visioneer) and product=0x0226 (Model 5800). Ok, so the kernel has detected it. That's ok. > I have inserted these into /etc/modules.conf. Ok, but probably not necessary. > > With supported scanners and recent Linux distributions your USB scanner > should just work out-of-the-box. > > Since I don't have that luxury, I have to choose to write a SANE driver > for Visioneer 5800 or try to use a generic libusb driver. No, you don't have these choice. You (or someone else) must write a SANE driver (backend). That backend uses either libusb or the kernel scanner driver. So definitely need a SANE backend for every scanner. libusb and the kernel scanner driver just provide the means to contact the scanner. All the "intelligent" work is done in the backend. > I don't know how to do either one of these, so I must call for HELP! Well, see the discussions on this list and: http://www.meier-geinitz.de/sane/misc/unsupported.html Bye, Henning From maddog@mir.com Fri Jun 27 17:57:59 2003 From: maddog@mir.com (Matto Marjanovic) Date: Fri, 27 Jun 2003 12:57:59 -0400 Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: <3EFB5083.3090208@gmx.net> (message from abel deuring on Thu, 26 Jun 2003 21:58:59 +0200) References: <3EFB5083.3090208@gmx.net> Message-ID: <1191-Fri27Jun2003125759-0400-maddog@yoo-hoo.ai.mit.edu> Hi, Henrik, Abel, I'm catching up on this thread, too. (When I first received the bug report, I was at the tail-end of finishing a Ph.D. Don't expect too much more attention just yet -- now I am on vacation. :) >> Jun 25 13:08:25 cortex unix: esp: Cmd dump for Target 5 Lun 0: >> Jun 25 13:08:25 cortex unix: esp: cdblen=6, cdb=[ 0x8 0x0 0x0 0x0 0x91 0x0 ] > >That's a READ of just 0x91 (145) bytes; shouldn't cause any buffer >overflow, but it's an odd number of bytes. A long shot: It could be that >the SCG driver does not like to transfer an odd number of bytes. Actually, it's a read of 145 *scanlines*, each of which is 900 bytes (in this case). That's what the 0x8 command means to these scanners. That makes 145 * 900 = 130500 bytes total, just under the 128k limit. >Matt and Henrik, I'm admittedly too lazy to look closer into the >Microtek backend, but I guess that it is trying to read a complete scan And I am too lazy to look at the SCG driver to see what it does. Henrik, is there some more debugging you can enable in the kernel driver so that we can see what it was doing *before* the error condition? The implementation of sanei_scsi_cmd2() for the SOLARIS_SG_INTERFACE looks incomplete: it makes no reference to the sense handler, and it simply returns SANE_STATUS_IO_ERROR for all error conditions. (Thus, there is no way to access any sense data.) Plus, it has no DBG()'s! The logfile from the microtek backend is not very revealing: simply an indeterminate SCSI error during the first read command. Maybe this is one of those BUSY conditions (the scanner is still scanning 145 lines?), and the SCG driver is returning a busy signal/error instead of retrying the command itself? -matt m. From hshane@austin.rr.com Fri Jun 27 19:01:02 2003 From: hshane@austin.rr.com (Howard Shane) Date: Fri, 27 Jun 2003 13:01:02 -0500 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP References: <3EFC351F.50508@austin.rr.com> <20030627132846.GI2318@meier-geinitz.de> Message-ID: <3EFC865E.9040107@austin.rr.com> Wow, guess I'm behind the times...maybe its time I upgraded from Debian woody, as it might be another few years before the project issues a major upgrade. :-/ Henning Meier-Geinitz wrote: > As far as I kno all Linux distributions include libusb. Libusb is a > library to access generic USB devices. It uses the operating system > generic USB driver and how that works exactly depends on the operating > system. > > The only thing the user needs to know is that he can only use libusb > access if no other kernel driver is attached to the speicfic device. > In case of Linux, that means "rmmod scanner". For permission issues > and other details look at man sane-usb. Maybe a pointer to that man > page is sufficiant. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From anoah@pfeiffer.edu Fri Jun 27 19:26:03 2003 From: anoah@pfeiffer.edu (m. allan noah) Date: Fri, 27 Jun 2003 14:26:03 -0400 (EDT) Subject: [sane-devel] [sane-devel]The report about 'sane-fujitsu' In-Reply-To: <200306271648.FEE65799.SOPPLP.PVJSIJO@pfu.fujitsu.com> Message-ID: you use old version of sane. remove redhat version of sane-backend: rpm -e --force --nodeps sane-backend and re-install sane: ./configure --prefix=/usr --sysconfdir=/etc make make install see below for more comments On Fri, 27 Jun 2003, hironori kohno wrote: > Hi, > > I performed testing about 'sane-fujitsu'. > It reports below. > > OS: RedHat Linux V8 > Scanner: fi-4220C > > Indication matters: > > 1. color-mode > When scan is carried out by color-mode, the information > on a color differs from an actual manuscript. > ex.A red paper is expressed as a yellow picture. > yes 4x20 uses BGR color, fixed in current cvs version. > 2. resolution > A maximum of 600 dpi is appropriate to x resolution of > fi-4x20 scanner. > The maximum of y resolution can be specified to 600dpi. > yes, currently backend uses the capabilites of the M3091 as default. if you want to update code to use vpd instead, that would be good. > 3. rif (reverse image format) > i want you to support not by rif but by SANE_NAME_NEGATIVE. > i do not set up by rif of scanner I/F, but want you to be > reversed to an actual picture color. > sorry, i do not understand. > 4. halftone-mode > A picture cannot be taken even if it specifies the mode of > halftone. yes, also because of incorrect defaults. > > 5. paper-size > "A3" and "double" are not supporting. incorrect defaults i think. though from the interface manual of the scanner, fi-4x20 does not support setting the paper size. must be set to 0xC0. would have to use --paperheight and --paperwidth inside the backend to fake paper size setting? > > 6. Start button > How to use start-button is not known. > cannot be used in sane. there is no portion of the sane api for accessing status of control panel. i have used an external program. allan > Bye, > Kouno > > -- > kouno.hironori@pfu.fujitsu.com > > -- > kouno.hironori@pfu.fujitsu.com > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From gnawa@libero.it Fri Jun 27 20:31:12 2003 From: gnawa@libero.it (gnawa) Date: Fri, 27 Jun 2003 21:31:12 +0200 Subject: [sane-devel] hi! Message-ID: <200306272131.12053.gnawa@libero.it> Alle 10:42, venerd=EC 27 giugno 2003, Henning Meier-Geinitz ha scritto: > Some hours after your posting Celso Pinto wrote to sane-devel that he > wants to start a backend: > http://www.mostang.com/pipermail/sane-devel/2003-June/019271.html > > So maybe you can work together on this project? it's a good thing work together with someone who is interested in the same project!so i will talk to Celso Pinto: celso if you want to share info and work with me we can talk about this driver in public, so if someone read about "scanjet 2300c" and wants to he= lp us he can, or in private if you prefer... i need the point from where to start... then the other things will come naturally (poi le cose verranno da sole). thank's to all Gnawa From tomf@sjpc.org Fri Jun 27 20:45:37 2003 From: tomf@sjpc.org (Thomas Frayne) Date: 27 Jun 2003 12:45:37 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030625205240.GA12653@meier-geinitz.de> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> Message-ID: <1056743137.3204.1.camel@localhost.localdomain> On Wed, 2003-06-25 at 13:52, Henning Meier-Geinitz wrote: > Is the scanner found as USB device now? Something like "libusb:001:002"? > > Please show us "sane-find-scanner -q". > > I have to admitt that I'm a bit confused by the backend. It uses USB > interrupt transfers to get the status of the scanner. However that > only works with libusb, not the kernel scanner driver. So I don't > really know why the backend lists "usb /dev/ubs/scanner" in > avision.conf. Maybe the maintainer can enlighten me :-) > > The name "usbdevfs" is obsolete. It's called "usbfs" now. But that's > not your problem. > Usually the config files list all devices and device files the backend > supports. So it doesn't matter if there are additional ones. > > The backend checks for all USB devices anymway, I don't think the > entries in avsion.conf are necessary at all. > rmmod scanner > modprobe scanner vendor=0x03f0 product=0x0801 > Some distributions use(d) /dev/usbscanner, some use /dev/usb/scanner0. > Shouldn't matter in your case. > > > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 > > Jun 24 13:37:51 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. > > That's your scanner. It's ok that it's not "claimed by any active > driver" because in this case it's used by usbfs (libusb). You can also > try to load the USB scanner driver as mentioned above. Then you should > get a message from that driver. > > I recommend to unplug/replug your scanner before any test. Otherwise > it may be confuded by eralier tests. > > > [root@localhost root]# ls -l /dev/usb/scanner0 > > crw-- 1 tom root 180, 48 Jan 30 02:24 > > /dev/usb/scanner0 > > That's ok. YOu can add a link /dev/usb/scanner to that one but I don't > think it's necessary. > > > /proc/bus/usb/devices > > Those entries start with "T:" (topology). > > > 48- 63: usbscanner > > Is loaded but doesn't know about your scanner. > > Bye, > Henning I snipped what now seems taken care of. Here is a summary of the current state: modprobe scanner vendor=0x03f0 product=0x0801 Jun 26 08:05:09 localhost kernel: usb.c: registered new driver usbscanner Jun 26 08:05:09 localhost kernel: scanner.c: USB scanner device (0x03f0/0x0801) now attached to scanner0 Jun 26 08:05:09 localhost kernel: scanner.c: 0.4.12:USB Scanner Driver Modified /usr/local/etc/sane.d/avision.conf to add usb /dev/usb/scanner0 [root@localhost root]# sane-find-scanner found USB scanner (vendor=0x03f0, product=0x0801) at /dev/usb/scanner0 found USB scanner (vendor=0x03f0 [hp], product=0x0801 [hp scanjet 7400c]) at libusb:004:002 [root@localhost root]# scanimage -L No scanners were identified. Hardware Browser found no scanners. Modified /usr/local/etc/sane.d/avision.conf to add usb 0x03f0 0x0801 This made scanimage -L work after rebooting, both in root mode and user mode: device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c flatbed scanner I shutdown, powered off the scanner, rebooted, ran xsane, and started a scan. The scanner hung as before, and the following appeared in messages. Jun 26 11:34:14 localhost modprobe: modprobe: Can't locate module char-major-81 Jun 26 12:11:41 localhost last message repeated 4 times Jun 26 12:11:41 localhost last message repeated 3 times Jun 26 12:18:37 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:18:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 26 12:19:07 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:19:07 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x83 len 22 ret -110 Jun 26 12:19:37 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:19:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 26 12:20:07 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:20:07 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 26 12:20:37 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:20:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 I tried to change all occurrences of usbdevfs in my /etc (fstab, hotplug/usb.rc, mtab, rc.d/rc.sysinit, rc.sysinit) to usbfs, but something went wrong, and my system became unbootable. I restored my / and /var partitions. Now I am pretty sure that my problem is in usbdevfs, but I don't know how to fix it. What can I try next? From henning@meier-geinitz.de Fri Jun 27 22:11:10 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 23:11:10 +0200 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <1056743137.3204.1.camel@localhost.localdomain> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> Message-ID: <20030627211110.GM2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 12:45:37PM -0700, Thomas Frayne wrote: > I snipped what now seems taken care of. Here is a summary of the > current state: > > [root@localhost root]# sane-find-scanner > found USB scanner (vendor=0x03f0, product=0x0801) at /dev/usb/scanner0 > found USB scanner (vendor=0x03f0 [hp], product=0x0801 [hp scanjet 7400c]) at libusb:004:002 So it's detected by the USB scanner driver and libusb. That's ok but you can also try without the USB scanner driver (rmmod scanner). > [root@localhost root]# scanimage -L > No scanners were identified. Try "SANE_DEBUG_AVISION=255 scanimage -L" to find out why it isn't found. Also unplug/replug your scanner to make sure it isn't confused by earlier tests. > Hardware Browser found no scanners. I don't know what you mean by "hardware browser" but as sane-find-scanner finds the scanner twice, I think that "harware browser" program is broken :-) > Modified /usr/local/etc/sane.d/avision.conf to add usb 0x03f0 0x0801 Ok. Shouldn't be necessary, but shouldn't harm either. > This made scanimage -L work after rebooting, Rebooting shouldn't be ever necessary. But if your scanner hangs, unplugging it may help. > both in root mode and user mode: > > device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c > flatbed scanner Ok. > I shutdown, powered off the scanner, rebooted, ran xsane, Make sure that when you run xsane you use the "/dev/usb/scanner0" or the "libusb:something" device and not the "/dev/sg0" device. Just to be sure that xsane doesn't do anything bad. > and started a scan. Try scanning with scanimage and debugging enabled, e.g. SANE_DEBUG_AVISION=255 scanimage >image.pnm 2>log > The scanner hung as before, and the following appeared in > messages. > Jun 26 12:18:37 localhost kernel: usb_control/bulk_msg: timeout > Jun 26 12:18:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 This time you don't have loaded the scanner driver. Did you try with the scanner driver instead? > I tried to change all occurrences of usbdevfs in my /etc (fstab, That's just the name, it doesn't matter (for now). > hotplug/usb.rc, mtab, rc.d/rc.sysinit, rc.sysinit) to usbfs, but > something went wrong, and my system became unbootable. I restored my / > and /var partitions. I think you only need to change /etc/fstab. > Now I am pretty sure that my problem is in usbdevfs, but I don't know > how to fix it. I don't think so. The timeouts occur because the scanner doesn't understand something the backend sends. That may be a backend broblem or something odd in the USB system. > What can I try next? Try the scanner driver. If it shows the same behaviour, you are sure that it's not usbfs. Otherwise, well, wait until the avision maintainer shows up again :-) Bye, Henning From henning@meier-geinitz.de Fri Jun 27 22:14:15 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 23:14:15 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EFC865E.9040107@austin.rr.com> References: <3EFC351F.50508@austin.rr.com> <20030627132846.GI2318@meier-geinitz.de> <3EFC865E.9040107@austin.rr.com> Message-ID: <20030627211415.GN2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 01:01:02PM -0500, Howard Shane wrote: > Wow, guess I'm behind the times...maybe its time I upgraded from Debian > woody, as it might be another few years before the project issues a > major upgrade. :-/ Even Woody has libusb. But that version may be too old for current versions of SANE. I haven't checked... Bye, Henning From christoffer@kjoelbaek.dk Sat Jun 28 14:23:08 2003 From: christoffer@kjoelbaek.dk (=?iso-8859-1?Q?Christoffer_Holm_Kj=F8lb=E6k?=) Date: Sat, 28 Jun 2003 15:23:08 +0200 Subject: [sane-devel] sane-find-scanner can find my scanner, but Xsane can't? Message-ID: Hey I have a Canon LiDe30, wich shuold be supported by sane And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0 But, Xsane says, that there is no devices available, why? Kind regards - and thanks in adance Christoffer Kjųlbęk From haidara@gucmed.com Sat Jun 28 16:43:44 2003 From: haidara@gucmed.com (Ayman Haidar) Date: Sat, 28 Jun 2003 11:43:44 -0400 Subject: [sane-devel] (no subject) Message-ID: <200306281143.45082.haidara@gucmed.com> Hello, I would greatly appreciate if you could recommend a scanner that works with sane, has an ADF and fairly decent scanning speed. I need to use it in the office and we might scan about 50-100 documents daily. Thanks -- Ayman From henning@meier-geinitz.de Sat Jun 28 16:51:03 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 17:51:03 +0200 Subject: [sane-devel] sane-find-scanner can find my scanner, but Xsane can't? In-Reply-To: References: Message-ID: <20030628155103.GA10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 03:23:08PM +0200, Christoffer Holm Kjųlbęk wrote: > I have a Canon LiDe30, wich shuold be supported by sane It is, but the comment says "Poor color picture quality". > And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0 Ok, so it was found by the kernel scanner driver. > But, Xsane says, that there is no devices available, why? Without further details, nobody knows. Maybe your version of SANE is too old? If this is not the case, you could try sane-troubleshoot to find out what's wrong: http://www.meier-geinitz.de/sane/sts/ Bye, Henning From christoph.knauer@web.de Sat Jun 28 16:57:47 2003 From: christoph.knauer@web.de (Christoph Knauer) Date: 28 Jun 2003 17:57:47 +0200 Subject: [sane-devel] negative-scan Message-ID: <1056815865.14723.11.camel@christoph.local> Hi, i've a litle problem with scanning negatives on an microtek scanmaker x6 / phantom 636 with lightlid35 when i set the option using lightlit or toggle lamp. with "toggle the lamp" the scannerlam goes out, but when i push the button scan, it goes on again, and setting "use lightlid35" seems to do nothing. btw. why there is no "negativ"-format to set for preview? greetings, christoph From tomf@sjpc.org Sat Jun 28 17:00:21 2003 From: tomf@sjpc.org (Thomas Frayne) Date: 28 Jun 2003 09:00:21 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030627211110.GM2318@meier-geinitz.de> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> Message-ID: <1056816020.3271.53.camel@localhost.localdomain> On Fri, 2003-06-27 at 14:11, Henning Meier-Geinitz wrote: ... > > > Modified /usr/local/etc/sane.d/avision.conf to add usb 0x03f0 0x0801 > > Ok. Shouldn't be necessary, but shouldn't harm either. > > > This made scanimage -L work after rebooting, > > Rebooting shouldn't be ever necessary. But if your scanner hangs, > unplugging it may help. Next time the scanner hangs, I'll try unplugging without rebooting. The procedure that made scanimage -L work was done after unplugging and before starting xsane, so I think that the avision.conf change really was necessary. > > > both in root mode and user mode: > > > > device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c > > flatbed scanner > > Ok. > > > I shutdown, powered off the scanner, rebooted, ran xsane, > > Make sure that when you run xsane you use the "/dev/usb/scanner0" or > the "libusb:something" device and not the "/dev/sg0" device. Just to > be sure that xsane doesn't do anything bad. > > > and started a scan. > > Try scanning with scanimage and debugging enabled, e.g. > SANE_DEBUG_AVISION=255 scanimage >image.pnm 2>log OK. I'll set the debugging mode. I'll also try with scanimage to see if I can isolate the problem to xsane. > > > The scanner hung as before, and the following appeared in > > messages. > > Jun 26 12:18:37 localhost kernel: usb_control/bulk_msg: timeout > > Jun 26 12:18:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 > > This time you don't have loaded the scanner driver. Did you try with > the scanner driver instead? I don't understand your question. How do I try with the scanner driver? What is the name of the scanner driver? > > > I tried to change all occurrences of usbdevfs in my /etc (fstab, > > That's just the name, it doesn't matter (for now). > > > hotplug/usb.rc, mtab, rc.d/rc.sysinit, rc.sysinit) to usbfs, but > > something went wrong, and my system became unbootable. I restored my / > > and /var partitions. > > I think you only need to change /etc/fstab. > > > Now I am pretty sure that my problem is in usbdevfs, but I don't know > > how to fix it. > > I don't think so. The timeouts occur because the scanner doesn't > understand something the backend sends. That may be a backend broblem > or something odd in the USB system. > > > What can I try next? > > Try the scanner driver. If it shows the same behaviour, you are sure > that it's not usbfs. > > Otherwise, well, wait until the avision maintainer shows up again :-) > > Bye, > Henning OK. Thanks. I'll try all the suggestions you just made. Please give me more information on running the scanner driver, at least enough so I know what that means, and can look up documentation. Tom From psfales@lucent.com Sat Jun 28 17:37:56 2003 From: psfales@lucent.com (Peter Fales) Date: Sat, 28 Jun 2003 11:37:56 -0500 Subject: [sane-devel] Microtek Pagewiz Message-ID: <20030628163756.GA4381@lucent.com> Anyone know anything about Microtek Pagewiz Color Sheetfed Scanner? http://www.mir.com/mtek/pport-hints.html makes it sound promising, but I wonder if anyone has any direct experience. They are going for well under $10 on eBay. I thik it might be handy if it worked reasonable well with Linux. -- Peter Fales Lucent Technologies, Room 1C-436 N9IYJ 2000 N Naperville Rd PO Box 3033 internet: psfales@lucent.com Naperville, IL 60566-7033 work: (630) 979-8031 From henning@meier-geinitz.de Sat Jun 28 18:25:36 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 19:25:36 +0200 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <1056816020.3271.53.camel@localhost.localdomain> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> <1056816020.3271.53.camel@localhost.localdomain> Message-ID: <20030628172536.GC10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 09:00:21AM -0700, Thomas Frayne wrote: > > > The scanner hung as before, and the following appeared in > > > messages. > > > Jun 26 12:18:37 localhost kernel: usb_control/bulk_msg: timeout > > > Jun 26 12:18:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 > > > > This time you don't have loaded the scanner driver. Did you try with > > the scanner driver instead? > > > I don't understand your question. How do I try with the scanner driver? > What is the name of the scanner driver? Well, in your last mail you told us that you loaded the scanner driver :-) Simplified: There are two ways to access a USB scanner by the kernel: Either by a specific driver for scanners ("kernel USB scanner driver", "scanner.o") or by the generic USB driver ("usbfs", "usbdevfs", "devio", "libusb"). If you load the kernel scanner driver (modprobe scanner) and it detectes your scanner, you can access the scanner only over that kernel scanner driver. If it's not loaded, libusb (usbdevfs) is used. In the kernel messages you get an error "kernel: usbdevfs: USBDEVFS_BULK ..." so I assume the kernel scanner driver was not loaded at that point. If it was and the same error occured, the mssage would come from scanner.c, not from usbdevfs. > OK. Thanks. I'll try all the suggestions you just made. Please give > me more information on running the scanner driver, at least enough so I > know what that means, and can look up documentation. man sane-usb, http://www.meier-geinitz.de/kernel/ Bye, Henning From christoffer@kjoelbaek.dk Sat Jun 28 18:29:55 2003 From: christoffer@kjoelbaek.dk (=?iso-8859-1?Q?Christoffer_Holm_Kj=F8lb=E6k?=) Date: Sat, 28 Jun 2003 19:29:55 +0200 Subject: SV: [sane-devel] sane-find-scanner can find my scanner, but Xsane can't? In-Reply-To: <20030628170036.GA1070@watcher.WorkGroup> Message-ID: -----Oprindelig meddelelse----- Fra: Michael Rasile [mailto:keeper@neo.rr.com] Sendt: 28. juni 2003 19:01 Til: Christoffer Holm Kjųlbęk Emne: Re: [sane-devel] sane-find-scanner can find my scanner, but Xsane can't? Hey Mike Thanks for you answer I think the problem is the old backend, that came with RedHat 9.0 as default. The version was: 1.0.9-5 Amd the newest is 1.0.12, so maybe it is that Can i just install the new backend, and nothing else? regards Christoffer On Sat Jun 28, 2003 at 03:23:08PM +0200 or thereabouts, Christoffer Holm Kj?lb?k wrote: > Hey > > I have a Canon LiDe30, wich shuold be supported by sane > > And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0 > > But, Xsane says, that there is no devices available, why? > > Kind regards - and thanks in adance > Christoffer Kjųlbęk > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel Greetings! Well, I have the same scanner and I use Gentoo. The first time I installed gentoo, I couldn't get the scanner to work right away. The problem is the sane-backend. Do you know what version of sane you have. What does scanimage -L show? If it doesn't show anything and your scanner is found by the kernel, then the problem lies with sane's backend. If you upgrade to the latest version of the sane-backend, it should solve the problem. What I did was to download the backend from the website and follow the directions for unpacking and installing. I installed right over the backend that was installed by gentoo. It worked for me. Now, here is something strange. I had to reinstall gentoo and before I upgraded the sane-backend, I tried xsane and it worked. Who knows why? Well, if you upgrade your sane-backend, it should solve the problem. HTH -- Regards, Mike keeper@neo.rr.com "Don't Fear The Penguin." From JeffMay@earthlink.net Sat Jun 28 18:38:10 2003 From: JeffMay@earthlink.net (Jeffery C. May) Date: 28 Jun 2003 13:38:10 -0400 Subject: [sane-devel] Re: Sane-devel digest, Vol 1 #503 - 1 msg In-Reply-To: <20030628132618.13633.99099.Mailman@panda.mostang.com> References: <20030628132618.13633.99099.Mailman@panda.mostang.com> Message-ID: <1056821890.4190.34.camel@daisy.localdomain> On Sat, 2003-06-28 at 09:26, Christoffer Kjlbk wrote: > Hey > > I have a Canon LiDe30, wich shuold be supported by sane > > And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0 > > But, Xsane says, that there is no devices available, why? > > Kind regards - and thanks in adance > Christoffer Kjlbk I'm having the similar (but not identical) difficulty with a Benq (Acer) 3300U that worked perfectly under Red Hat 7.1. After upgrading to Red Hat 9.0 and the latest SANE packages (compiled, not Red Hat packages) I get the following behavior: Looking in /proc/bus/usb/devices I find: ===================begin /proc/bus/usb/devices listing============= E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1 P: Vendor=04a5 ProdID=20b0 Rev= 1.00 S: Manufacturer=Color S: Product= FlatbedScanner 22 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbscanner ===================end /proc/bus/usb/devices listing=============== So the scanner is seen by the kernel and the usbfs system. ===================begin sane-find-scanner output================== # 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=0x04a5, product=0x20b0) at /dev/usb/scanner0 found USB scanner (vendor=0x04a5, product=0x20b0) at libusb:001:003 # 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. ===================end sane-find-scanner output==================== Okay, sane-find-scanner sees it. ===================begin scanimage -L output================== device `snapscan:/dev/usb/scanner0' is a Acer FlatbedScanner22 flatbed scanner ===================end scanimage -L output==================== Okay, so scanimage says it's there. According to the Sourceforge page (http://snapscan.sourceforge.net/), the Acer/Benq 3300 uses either the "u222v067.bin" or "u176v046.bin" firmware files. Looking at the CD that came with the scanner I find the first one (u222v067.bin), but not the second one: ===================begin listing of CD firmware================== /mnt/cdrom1/u174v041.BIN /mnt/cdrom1/u176v042.bin /mnt/cdrom1/u222v067.bin /mnt/cdrom1/u34v110.bin /mnt/cdrom1/u96v121.bin ===================end listing of CD firmware==================== I copied the "u222v67.bin" file to /etc/sane.d/firmware/Benq_3300U and modified the /etc/sane.d/snapscan.conf file as shown below: ===================begin /etc/sane.d/snapscan.conf================ #------------------------------ General ----------------------------------- # Change to the fully qualified filename of your firmware file, if # firmware upload is needed by the scanner firmware /etc/sane.d/firmware/Benq_3300U/u222v067.bin # If not automatically found you may manually specify a device name. # For USB scanners also specify bus=usb, e.g. # /dev/usb/scanner0 bus=usb # For SCSI scanners specify the generic device, e.g. /dev/sg0 on Linux. # /dev/sg0 #--------------------------------------------------------------------------- # No changes should be necessary below this line #--------------------------------------------------------------------------- #-------------------------- SCSI scanners ---------------------------------- # These SCSI devices will be probed automatically scsi AGFA * Scanner scsi COLOR * Scanner scsi Color * Scanner scsi ACERPERI * Scanner #--------------------------- USB scanners ----------------------------------- # These USB devices will be probed automatically # (This will currently work only on Linux) # Benq/Acer/Vuego 320U usb 0x04a5 0x2022 # Benq/Acer/Vuego 620U / 620UT usb 0x04a5 0x1a2a usb 0x04a5 0x2040 # Benq/Acer/Vuego 640U usb 0x04a5 0x2060 # Benq/Acer/Vuego 640BU usb 0x04a5 0x207e # Benq/Acer/Vuego 1240U usb 0x04a5 0x20c0 # Benq/Acer/Vuego 3300 / 4300 usb 0x04a5 0x20b0 # Benq/Acer/Vuego 4300 usb 0x04a5 0x20de # Benq/Acer/Vuego 5000 usb 0x04a5 0x20fc # Benq/Acer/Vuego 5300 usb 0x04a5 0x20fe # Agfa 1236U usb 0x06bd 0x0002 # Agfa 1212U usb 0x06bd 0x0001 usb 0x06bd 0x2061 # Agfa Snapscan e10 usb 0x06bd 0x2093 # Agfa Snapscan e20 usb 0x06bd 0x2091 # Agfa Snapscan e25 usb 0x06bd 0x2095 # Agfa Snapscan e26 usb 0x06bd 0x2097 # Agfa Snapscan e40 usb 0x06bd 0x208d # Agfa Snapscan e42 usb 0x06bd 0x20ff # Agfa Snapscan e50 usb 0x06bd 0x208f # Agfa Snapscan e52 usb 0x06bd 0x20fd ===================end /etc/sane.d/snapscan.conf================== If I run Xsane at this point it hangs. Setting SANE_DEBUG_SNAPSCAN=255 and running scanimage I get the following messages: ===================begin scanimage debug================ [sanei_debug] Setting debug level of snapscan to 255. [snapscan] sane_snapscan_init [snapscan] sane_snapscan_init: Snapscan backend version 1.4.26 [snapscan] add_usb_device(/dev/usb/scanner0) [snapscan] add_usb_device: Detected (kind of) an USB device [snapscan] snapscani_usb_open(/dev/usb/scanner0) [snapscan] add_usb_device: Checking if 0x04a5 is a supported USB vendor ID [snapscan] snapscani_check_device() [snapscan] mini_inquiry [snapscan] snapscan_cmd [snapscan] snapscan_usb_cmd(0,0xbfffc3c0,6,0xbfffc390,0xbfffc38c (36)) [snapscan] atomic_usb_cmd(0,0xbfffc3c0,6,0xbfffc390,0xbfffc38c (36)) [snapscan] usb_cmd(0,0xbfffc3c0,6,0xbfffc390,0xbfffc38c (36)) [snapscan] usb_cmd: cmdlen=6, datalen=0 [snapscan] usb_write: writing: 0x12 0x00 0x00 0x00 0x24 0x00 [snapscan] usb_write: Only 0 bytes written [snapscan] mini_inquiry: snapscan_cmd command failed: error during device I/O [snapscan] snapscani_check_device: mini_inquiry failed with Error during device I/O [snapscan] snapscani_usb_close(0) [snapscan] add_usb_device(libusb:001:003) [snapscan] add_usb_device: Detected (kind of) an USB device [snapscan] snapscani_usb_open(libusb:001:003) [snapscan] add_usb_device: error opening device libusb:001:003: Access to resource has been denied [snapscan] sane_snapscan_get_devices (0xbfffd5d8, 0) scanimage: no SANE devices found [snapscan] sane_snapscan_exit ===================end scanimage debug================== Libusb is something new that Red Hat 7.1 didn't have. Any clues as to what I'm missing? I'm sure it's something simple. Jeff From fsanta@arrakis.es Sat Jun 28 20:05:28 2003 From: fsanta@arrakis.es (fsanta) Date: Sat, 28 Jun 2003 21:05:28 +0200 Subject: [sane-devel] Any umax persons still on the list? Message-ID: <200306282105.28692.fsanta@arrakis.es> Hi. Astra 2200 works with SuSE 8.1 but not with 8.2 Here is the error message: Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses synchronous negotiation. Using asynchronous transfers Can anyone tell me how to get 'synchronous transfers'? Adaptec 2904 scsi card with astra 2200su Cheers, Steve. From foffy_69@yahoo.es Sat Jun 28 20:30:54 2003 From: foffy_69@yahoo.es (=?iso-8859-1?q?Foffy?=) Date: Sat, 28 Jun 2003 21:30:54 +0200 (CEST) Subject: [sane-devel] [sane-delevel] writing a backend Message-ID: <20030628193054.76829.qmail@web41003.mail.yahoo.com> I have a genius colorpage vivid 3 usb scanner and i want to write a backend. how i can start writing it?? thanks a lot ___________________________________________________ Yahoo! Messenger - Nueva versión GRATIS Super Webcam, voz, caritas animadas, y mįs... http://messenger.yahoo.es From haidara@gucmed.com Sat Jun 28 20:34:41 2003 From: haidara@gucmed.com (Ayman Haidar) Date: Sat, 28 Jun 2003 15:34:41 -0400 Subject: [sane-devel] scanner recommendation In-Reply-To: <200306281143.45082.haidara@gucmed.com> References: <200306281143.45082.haidara@gucmed.com> Message-ID: <200306281534.41116.haidara@gucmed.com> sorry for the missing subject On Saturday 28 June 2003 11:43 am, Ayman Haidar wrote: > Hello, > > I would greatly appreciate if you could recommend a scanner that works with > sane, has an ADF and fairly decent scanning speed. > > I need to use it in the office and we might scan about 50-100 documents > daily. > > > Thanks -- Ayman Haidar, MD From henning@meier-geinitz.de Sat Jun 28 21:50:41 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 22:50:41 +0200 Subject: [sane-devel] Re: Sane-devel digest, Vol 1 #503 - 1 msg In-Reply-To: <1056821890.4190.34.camel@daisy.localdomain> References: <20030628132618.13633.99099.Mailman@panda.mostang.com> <1056821890.4190.34.camel@daisy.localdomain> Message-ID: <20030628205041.GD10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 01:38:10PM -0400, Jeffery C. May wrote: > I'm having the similar (but not identical) difficulty with a Benq (Acer) > 3300U that worked perfectly under Red Hat 7.1. Different backend (snapscan vs. plustek) so I don't think it's related. > [snapscan] snapscani_usb_open(/dev/usb/scanner0) > [snapscan] add_usb_device: Checking if 0x04a5 is a supported USB vendor ID [...] > [snapscan] usb_write: writing: 0x12 0x00 0x00 0x00 0x24 0x00 > [snapscan] usb_write: Only 0 bytes written > [snapscan] mini_inquiry: snapscan_cmd command failed: error during device I/O > Libusb is something new that Red Hat 7.1 didn't have. Any clues as to > what I'm missing? I'm sure it's something simple. I have no idea why it fails but it's not libusb. You are using the kernel scanner driver, see the first line of the log. You could try libusb (rmmod scanner) instead. Standard comments: - Make sure that your scanner is not confused by earlier tests (unplug/replug it) - diable everything but snapscan in dll.conf Bye, Henning From henning@meier-geinitz.de Sat Jun 28 21:56:21 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 22:56:21 +0200 Subject: [sane-devel] Any umax persons still on the list? In-Reply-To: <200306282105.28692.fsanta@arrakis.es> References: <200306282105.28692.fsanta@arrakis.es> Message-ID: <20030628205621.GE10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 09:05:28PM +0200, fsanta wrote: > Astra 2200 works with SuSE 8.1 but not with 8.2 Most people don't know what that means. What changed between these versions? i.e. kernel version + sane version? Try to find out what change causes the problem by using the old kernel or the old sane version. > Here is the error message: > > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > synchronous negotiation. Using asynchronous transfers > > Can anyone tell me how to get 'synchronous transfers'? I don't think it helps to repeat your questions without providing more information on what you did. As I said stuff like "sync negotiotaion" is done in the kernel SCSI driver. > Adaptec 2904 scsi card with astra 2200su Have you tried an older kernel or using the old SCSI driver as explained in my other mail? Bye, Henning From henning@meier-geinitz.de Sat Jun 28 21:59:47 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 22:59:47 +0200 Subject: [sane-devel] [sane-delevel] writing a backend In-Reply-To: <20030628193054.76829.qmail@web41003.mail.yahoo.com> References: <20030628193054.76829.qmail@web41003.mail.yahoo.com> Message-ID: <20030628205947.GF10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 09:30:54PM +0200, Foffy wrote: > I have a genius colorpage vivid 3 usb scanner and i > want to write a backend. > > how i can start writing it?? Have a look at the archive of this mailing list. There have been similar questions about this topic during the last week: http://www.mostang.com/pipermail/sane-devel/2003-June/thread.html As a start: http://www.meier-geinitz.de/sane/misc/unsupported.html Bye, Henning From JeffMay@earthlink.net Sun Jun 29 03:52:37 2003 From: JeffMay@earthlink.net (Jeffery C. May) Date: 28 Jun 2003 22:52:37 -0400 Subject: [sane-devel] Well, Duh... In-Reply-To: <20030628205202.16781.49733.Mailman@panda.mostang.com> References: <20030628205202.16781.49733.Mailman@panda.mostang.com> Message-ID: <1056855157.4240.22.camel@daisy.localdomain> Well, I figured out my Benq 3300U problem. I had the wrong firmware file. instead of using u222v067.bin, I should have been using the u176v042.bin file (that was also on the CD that came with it!) Found the proper hint on this page: http://www.acronymchile.com/scanner.html Jeff (Thanks for all the help!) From oliver.rauch@rauch-domain.de Sun Jun 29 17:20:48 2003 From: oliver.rauch@rauch-domain.de (Oliver Rauch) Date: Sun, 29 Jun 2003 18:20:48 +0200 Subject: [sane-devel] Any umax persons still on the list? In-Reply-To: <200306282105.28692.fsanta@arrakis.es> References: <200306282105.28692.fsanta@arrakis.es> Message-ID: <200306291820.48500.oliver.rauch@rauch-domain.de> Most umax scanners do not support syncronous transfers. The scsi controller/driver does the only valid thing: it uses async transfers. Where is the problem with that? Oliver On Saturday 28 June 2003 21:05, fsanta wrote: > Hi. > Astra 2200 works with SuSE 8.1 but not with 8.2 > > Here is the error message: > > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > synchronous negotiation. Using asynchronous transfers > > Can anyone tell me how to get 'synchronous transfers'? > > Adaptec 2904 scsi card with astra 2200su > > Cheers, Steve. > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel --=20 http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:Oliver.Rauch@Rauch-Domain.DE From hshane@austin.rr.com Sun Jun 29 17:54:37 2003 From: hshane@austin.rr.com (Howard Shane) Date: Sun, 29 Jun 2003 11:54:37 -0500 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP References: <3EFC351F.50508@austin.rr.com> <20030627132846.GI2318@meier-geinitz.de> Message-ID: <3EFF19CD.2040409@austin.rr.com> So, I guess my question boils down to this: Let's say hypothetically we're up to linux-2.6.0, and there is no more kernel usb-scanner support, and a person wants to use a SANE application. All they have to do is to be sure libusb is installed with the SANE backends and whatever frontend they're after, right? No other configuration steps are necessary? Are there any specific pitfalls to to be aware of? Sorry for my persistence but I want to be sure I am giving all those out there who read the HOWTO the most accurate and complete picture possible. :^) Thanks! Henning Meier-Geinitz wrote: > Hi, > > On Fri, Jun 27, 2003 at 07:14:23AM -0500, Howard Shane wrote: > >>I've visited the libusb site, and the only documentation available seems >>to be for developers. If someone can point me to more user-oriented >>information I'll be happy to include it. I assume it's out of the beta >>phase? Are there distribution manufacturers including it in their stable >>branches of binaries? > > > As far as I kno all Linux distributions include libusb. Libusb is a > library to access generic USB devices. It uses the operating system > generic USB driver and how that works exactly depends on the operating > system. > > The only thing the user needs to know is that he can only use libusb > access if no other kernel driver is attached to the speicfic device. > In case of Linux, that means "rmmod scanner". For permission issues > and other details look at man sane-usb. Maybe a pointer to that man > page is sufficiant. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > From henning@meier-geinitz.de Sun Jun 29 18:16:41 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 29 Jun 2003 19:16:41 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EFF19CD.2040409@austin.rr.com> References: <3EFC351F.50508@austin.rr.com> <20030627132846.GI2318@meier-geinitz.de> <3EFF19CD.2040409@austin.rr.com> Message-ID: <20030629171641.GA18926@meier-geinitz.de> Hi, On Sun, Jun 29, 2003 at 11:54:37AM -0500, Howard Shane wrote: > So, I guess my question boils down to this: Let's say hypothetically > we're up to linux-2.6.0, and there is no more kernel usb-scanner > support, and a person wants to use a SANE application. All they have to > do is to be sure libusb is installed with the SANE backends and whatever > frontend they're after, right? Usually sane-backends depends on libusb, so if SANE is installed, libusb should also be installed automatically. > No other configuration steps are necessary? Are there any specific > pitfalls to to be aware of? It may be necessary to adjust the permissions of usbdevfs as explained in man sane-usb. At least if you want to scan as non-root. I don't know how addvanced the hotplug setup currently is. That's something hotplug could do. Bye, Henning From moali@sbox.tugraz.at Sun Jun 29 18:47:02 2003 From: moali@sbox.tugraz.at (Gerfried Maier) Date: Sun, 29 Jun 2003 19:47:02 +0200 Subject: [sane-devel] XSane 0.90: Missing gettext produces hard to understand error-message when compiling Message-ID: <3EFF2616.6080205@sbox.tugraz.at> It took me a while to figure out what the problem was. The "no" from configure seems to be treated as gmsgfmt-command. A cut from the output of configure: [...] checking whether catgets can be used... no checking for msgfmt... (cached) no checking for gmsgfmt... no checking for xgettext... : checking for catalogs to be installed... cs da de es fr it ja nl pt pt_BR ro ru sk sl sr sv vi tr checking for sane-config... /usr/local/bin/sane-config [...] The making of... [...] make[1]: Leaving directory `/home/moali/src/xsane-0.90/src' making all in po make[1]: Entering directory `/home/moali/src/xsane-0.90/po' file=./`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && PATH=../src:$PATH no -o $file de.po /bin/sh: line 1: no: command not found make[1]: *** [de.gmo] Error 127 make[1]: Leaving directory `/home/moali/src/xsane-0.90/po' make: *** [all-recursive] Error 1 Regards, Maier Gerfried From jollyprince@juno.com Sun Jun 29 20:01:09 2003 From: jollyprince@juno.com (jollyprince@juno.com) Date: Sun, 29 Jun 2003 19:01:09 GMT Subject: [sane-devel] Visioneer 5800 backend Message-ID: <20030629.120151.16123.69038@webmail12.lax.untd.com> I'm interested in writing a backend for my Visioneer 5800. I've written some C code in my lifetime but that's about all the prerequisites that I have to bring to the project. I've opened up the box but couldn't get to the chipset for fear of damaging the wiring harness. Any suggestions about getting the maximum info about the product. I'm told it's a LM9832 chipset. Can anyone confirm or deny this? Can anyone recommend an example of a working backend that would be similar to what a Visioneer backend might look like? I've studied a bunch of stuff and feel lost in an information explosion. Any tips and shortcuts that are applicable would be greatly appreciated! Thanks in advance! From henning@meier-geinitz.de Sun Jun 29 21:01:39 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 29 Jun 2003 22:01:39 +0200 Subject: [sane-devel] Visioneer 5800 backend In-Reply-To: <20030629.120151.16123.69038@webmail12.lax.untd.com> References: <20030629.120151.16123.69038@webmail12.lax.untd.com> Message-ID: <20030629200139.GA23824@meier-geinitz.de> Hi, On Sun, Jun 29, 2003 at 07:01:09PM +0000, jollyprince@juno.com wrote: > I'm interested in writing a backend for my Visioneer 5800. I've > written some C code in my lifetime but that's about all the > prerequisites that I have to bring to the project. That and a lot of patience is enough :-) Please show us the output of "cat /proc/bus/usb/devices" when the scanner is plugged in. > I've opened up the box but couldn't get to the chipset for fear of > damaging the wiring harness. Any suggestions about getting the > maximum info about the product. I'm told it's a LM9832 chipset. Can > anyone confirm or deny this? Just try it. There is a tool to find out about some known chipsets: http://www.meier-geinitz.de/sane/check-usb-scanner/ > Can anyone recommend an example of a working backend that would be > similar to what a Visioneer backend might look like? If it's really a LM9832, adding support to the plustek backend is the way to go. But i doubt that it's really that chipset. Our database says "E5" chipset, whatever that means. > I've studied a bunch of stuff and feel lost in an information > explosion. Any tips and shortcuts that are applicable would be > greatly appreciated! Thanks in advance! There have been wuite some discussion about how to start writing a backend during the last week so reading the archive of sane-devel may help to get started. Bye, Henning From jollyprince@juno.com Sun Jun 29 21:38:25 2003 From: jollyprince@juno.com (jollyprince@juno.com) Date: Sun, 29 Jun 2003 20:38:25 GMT Subject: [sane-devel] Re: Visioneer 5800 Message-ID: <20030629.133908.559.189108@webmail05.lax.untd.com> T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=04a7 ProdID=0226 Rev= 1.00 S: Manufacturer=Visioneer S: Product=USB Scanner S: SerialNumber=RTS8801C2-004 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms RESULT: of cat /proc/bus/usb/devices | more From rene.rebe@gmx.net Sun Jun 29 22:14:17 2003 From: rene.rebe@gmx.net (Rene Rebe) Date: Sun, 29 Jun 2003 23:14:17 +0200 (CEST) Subject: [sane-devel] ScanJet 5300C question In-Reply-To: <3EF9F507.6040604@midwest-tool.com> References: <3EF9F507.6040604@midwest-tool.com> Message-ID: <20030629.231417.730551786.rene.rebe@gmx.net> Hi, On: Wed, 25 Jun 2003 14:16:23 -0500, Matt Lung wrote: > I would like to use the ADF we have with our HP 5300C scanner under = > linux and Sane but I have yet to find any documentation or help on ho= w = > to setup an ADF with this scanner. It scans just fine without it, bu= t = > with out the ADF funcioning I'll be forced to use it in Windows forev= er. > = > Is an ADF even supported with the HP 5300C? Theoretically yes. But I have still to solve ADF problem for the 7400 series. But older ADF units and the professional ones e.g. from the Avision 8000 series just work fine. So if you have luck the ADF will simply work when you plugged it into your scanner. If the ADF hangs during feeding the first page, use usbsnoop during ADF scanning under Windows to log the data traffic and send the output to me. I hope to have some free time this summer to continue to solve the last HP problems with the backend. > If so, where can I find information on how to do this? > = > thanks for any help Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene.rebe@gmx.net http://www.rocklinux.org http://www.rocklinux.org/people/rene = http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From rene.rebe@gmx.net Sun Jun 29 22:19:37 2003 From: rene.rebe@gmx.net (Rene Rebe) Date: Sun, 29 Jun 2003 23:19:37 +0200 (CEST) Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030625205240.GA12653@meier-geinitz.de> References: <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> Message-ID: <20030629.231937.846934703.rene.rebe@gmx.net> Hi, On: Wed, 25 Jun 2003 22:52:40 +0200, Henning Meier-Geinitz wrote: > I have to admitt that I'm a bit confused by the backend. It uses USB > interrupt transfers to get the status of the scanner. However that > only works with libusb, not the kernel scanner driver. So I don't > really know why the backend lists "usb /dev/ubs/scanner" in > avision.conf. Maybe the maintainer can enlighten me :-) Yes - the scanner Linux driver is not supported. The line in the avision.conf might only silpped in from my initial tests with the scanner driver. I'll remove it soon. > = > Usually the config files list all devices and device files the backen= d > supports. So it doesn't matter if there are additional ones. > = > The backend checks for all USB devices anymway, I don't think the > entries in avsion.conf are necessary at all. Yes - the entries are only an example how to add IDs for test reasons when new scanners are out ... > > I'll keep trying. I have just done = > > modprobe scanner vendor=3D0x0001 product=3D0x0002, > = > These vendor and product ids are most probably wrong. If the scanner > driver works at all, try something like this: > rmmod scanner > modprobe scanner vendor=3D0x03f0 product=3D0x0801 The scanner driver does not work. > That doesn't look good. Your scanner doesn't seem to accept any input= > on any endpoint (bulk in, out and interrupt). = > = > I recommend to unplug/replug your scanner before any test. Otherwise > it may be confuded by eralier tests. It needs to be powerer off to loose all it's state. > Is loaded but doesn't know about your scanner. > = > Bye, > Henning Thanks for the answering the questions Henning - when I'm as always out of time ;-) Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene.rebe@gmx.net http://www.rocklinux.org http://www.rocklinux.org/people/rene = http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From rene.rebe@gmx.net Sun Jun 29 22:25:24 2003 From: rene.rebe@gmx.net (Rene Rebe) Date: Sun, 29 Jun 2003 23:25:24 +0200 (CEST) Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030627211110.GM2318@meier-geinitz.de> References: <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> Message-ID: <20030629.232524.607955671.rene.rebe@gmx.net> Hi, On: Fri, 27 Jun 2003 23:11:10 +0200, Henning Meier-Geinitz wrote: > > This made scanimage -L work after rebooting, > = > Rebooting shouldn't be ever necessary. But if your scanner hangs, > unplugging it may help. Power off is needed for the scanner to loose all state. > > Now I am pretty sure that my problem is in usbdevfs, but I don't kn= ow > > how to fix it. = > = > I don't think so. The timeouts occur because the scanner doesn't > understand something the backend sends. That may be a backend broblem= > or something odd in the USB system. The scanner should "understand" all. It works here with a old HP 5300 and a slightly newer HP 5300 labelled as 5370. Which host controller chip and respective kernel driver is this? If communication via libusb is not reliable for you, you still can use the "deprecated" hpusbscsi driver in the kernel - but _not_ the scanner driver. > > What can I try next? > = > Try the scanner driver. If it shows the same behaviour, you are sure > that it's not usbfs. The scanner driver will not work - because of the missing interrupt endpoint notification support - but I do not want to support a 3rd "to be removed in the future" access method. So I think hpusbscsi and libusb should be ok. > Otherwise, well, wait until the avision maintainer shows up again :-)= CC'ing me always helps a lot ;-) > Bye, > Henning Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene.rebe@gmx.net http://www.rocklinux.org http://www.rocklinux.org/people/rene = http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From tomf@sjpc.org Mon Jun 30 04:54:01 2003 From: tomf@sjpc.org (Thomas Frayne) Date: 29 Jun 2003 20:54:01 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030629.232524.607955671.rene.rebe@gmx.net> References: <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> <20030629.232524.607955671.rene.rebe@gmx.net> Message-ID: <1056945240.3460.92.camel@localhost.localdomain> --=-RKQ6ngouQ5FBJDhEbC7Y Content-Type: text/plain Content-Transfer-Encoding: 7bit On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: > Hi, > > On: Fri, 27 Jun 2003 23:11:10 +0200, > Henning Meier-Geinitz wrote: > ... > > Which host controller chip and respective kernel driver is this? Here are messages that may help answer your questions. If this won't do it, could you tell me how to find the answers to your questions? Jun 29 07:33:03 localhost kernel: Linux version 2.4.20-18.9 (root@gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Wed Jun 4 15:04:35 PDT 2003 Installed via up2date. Jun 29 07:33:05 localhost kernel: usb.c: registered new driver usbdevfs Jun 29 07:33:05 localhost kernel: usb.c: registered new driver hub Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0 Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0870000, IRQ 5 Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC Corporation USB Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 3 ports detected Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0 Jun 29 07:33:06 localhost rc: Starting pcmcia: succeeded Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0872000, IRQ 9 Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC Corporation USB (#2) Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.0-1, assigned address 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB 2.0 Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem f087a000 Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 3 Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size set incorrectly (32 bytes) by BIOS/FW. Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size corrected to 128. Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22 Jun 29 07:33:06 localhost kernel: usb.c: USB disconnect on device 00:0b.0-1 address 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 5 ports detected Jun 29 07:33:06 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time 07:14:02 May 29 2003 Jun 29 07:33:06 localhost kernel: usb-uhci.c: High bandwidth mode enabled Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:07.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 29 07:33:06 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, IRQ 10 Jun 29 07:33:06 localhost kernel: usb-uhci.c: Detected 2 ports Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 4 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected Jun 29 07:33:06 localhost kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hiddev Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hid Jun 29 07:33:06 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik Jun 29 07:33:06 localhost kernel: hid-core.c: USB HID support drivers Jun 29 07:33:06 localhost kernel: mice: PS/2 mouse device common for all mice Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1, assigned address 2 Jun 29 07:33:06 localhost mount: mount: none already mounted or /proc/bus/usb busy Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost mount: mount: according to mtab, usbdevfs is already mounted on /proc/bus/usb Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected Jun 29 07:33:06 localhost netfs: Mounting other filesystems: failed Jun 29 07:33:06 localhost kernel: Adding Swap: 1582360k swap-space (priority -1) Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 29 07:33:06 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.2, assigned address 3 Jun 29 07:33:06 localhost kernel: usb.c: USB device 3 (vend/prod 0x2821/0x5001) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.4, assigned address 4 Jun 29 07:33:06 localhost kernel: usb.c: USB device 4 (vend/prod 0x3f0/0x3404) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: Initializing USB Mass Storage driver... Jun 29 07:33:06 localhost kernel: usb.c: registered new driver usb-storage Jun 29 07:33:07 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices Jun 29 07:33:07 localhost kernel: Vendor: ASUS Model: CRW-5224A Rev: 1.00 Jun 29 07:33:07 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 29 07:33:07 localhost kernel: USB Mass Storage support registered. Jun 29 07:33:07 localhost kernel: hdc: attached ide-scsi driver. Jun 29 07:33:07 localhost kernel: scsi2 : SCSI host adapter emulation for IDE ATAPI devices Jun 29 07:33:07 localhost kernel: Vendor: HP Model: CD-Writer+ 8100 Rev: 1.0g Jun 29 07:33:07 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 29 07:33:07 localhost kernel: usb.c: registered new driver usblp Jun 29 07:33:07 localhost kernel: printer.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404 > > If communication via libusb is not reliable for you, you still can use > the "deprecated" hpusbscsi driver in the kernel - but _not_ the > scanner driver. I've tried so many configuration variations over the last couple of weeks that I've gotten confused about what configuration settings do what. I don't think I understand the terminology. I now think I should avoid using the scanner driver. Would rmmod scanner do this for me, or is something else necessary? I would like to use libusb, but I have not been able to figure out what causes the libusb driver to be loaded. Some parts of my system refer to usbfs; others refer to usbdevfs. I think I need everything in the system refering to one or everything to the other, but when I tried changing the references to usbfs, I produced a system that would not boot, and had to restore a backup. What is the best way to get back to a clean system? Is there a modprobe command I should be using to load the libusb driver? If so, should I add it to /etc/rc.d/rc.local to get it to run during boot? I currently have hpusbbscsi disabled. Should both libusb and hpusbbscsi be enabled? ... > > The scanner driver will not work - because of the missing interrupt > endpoint notification support - but I do not want to support a 3rd "to > be removed in the future" access method. So I think hpusbscsi and > libusb should be ok. > --=-RKQ6ngouQ5FBJDhEbC7Y Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: 
Hi,

On: Fri, 27 Jun 2003 23:11:10 +0200,
    Henning Meier-Geinitz <henning@meier-geinitz.de> wrote:
... 

Which host controller chip and respective kernel driver is this?

Here are messages that may help answer your questions.  If this won't do it, could you tell me how to find the answers to your questions?


Jun 29 07:33:03 localhost kernel: Linux version 2.4.20-18.9 (root@gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Wed Jun 4 15:04:35 PDT 2003  Installed via up2date.
Jun 29 07:33:05 localhost kernel: usb.c: registered new driver usbdevfs
Jun 29 07:33:05 localhost kernel: usb.c: registered new driver hub
Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0
Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0870000, IRQ 5
Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC Corporation USB
Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 1
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 3 ports detected
Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0
Jun 29 07:33:06 localhost rc: Starting pcmcia:  succeeded
Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0872000, IRQ 9
Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC Corporation USB (#2)
Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 2
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.0-1, assigned address 2
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected
Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0
Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB 2.0
Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem f087a000
Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 3
Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size set incorrectly (32 bytes) by BIOS/FW.
Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size corrected to 128.
Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22
Jun 29 07:33:06 localhost kernel: usb.c: USB disconnect on device 00:0b.0-1 address 2
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 5 ports detected
Jun 29 07:33:06 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time 07:14:02 May 29 2003
Jun 29 07:33:06 localhost kernel: usb-uhci.c: High bandwidth mode enabled
Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:07.2
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0
Jun 29 07:33:06 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, IRQ 10
Jun 29 07:33:06 localhost kernel: usb-uhci.c: Detected 2 ports
Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 4
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected
Jun 29 07:33:06 localhost kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hiddev
Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hid
Jun 29 07:33:06 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
Jun 29 07:33:06 localhost kernel: hid-core.c: USB HID support drivers
Jun 29 07:33:06 localhost kernel: mice: PS/2 mouse device common for all mice
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1, assigned address 2
Jun 29 07:33:06 localhost mount: mount: none already mounted or /proc/bus/usb busy
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost mount: mount: according to mtab, usbdevfs is already mounted on /proc/bus/usb
Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected
Jun 29 07:33:06 localhost netfs: Mounting other filesystems:  failed
Jun 29 07:33:06 localhost kernel: Adding Swap: 1582360k swap-space (priority -1)
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2
Jun 29 07:33:06 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver.
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.2, assigned address 3
Jun 29 07:33:06 localhost kernel: usb.c: USB device 3 (vend/prod 0x2821/0x5001) is not claimed by any active driver.
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.4, assigned address 4
Jun 29 07:33:06 localhost kernel: usb.c: USB device 4 (vend/prod 0x3f0/0x3404) is not claimed by any active driver.
Jun 29 07:33:06 localhost kernel: Initializing USB Mass Storage driver...
Jun 29 07:33:06 localhost kernel: usb.c: registered new driver usb-storage
Jun 29 07:33:07 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices
Jun 29 07:33:07 localhost kernel:   Vendor: ASUS      Model: CRW-5224A         Rev: 1.00
Jun 29 07:33:07 localhost kernel:   Type:   CD-ROM                             ANSI SCSI revision: 02
Jun 29 07:33:07 localhost kernel: USB Mass Storage support registered.
Jun 29 07:33:07 localhost kernel: hdc: attached ide-scsi driver.
Jun 29 07:33:07 localhost kernel: scsi2 : SCSI host adapter emulation for IDE ATAPI devices
Jun 29 07:33:07 localhost kernel:   Vendor: HP        Model: CD-Writer+ 8100   Rev: 1.0g
Jun 29 07:33:07 localhost kernel:   Type:   CD-ROM                             ANSI SCSI revision: 02
Jun 29 07:33:07 localhost kernel: usb.c: registered new driver usblp
Jun 29 07:33:07 localhost kernel: printer.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404




If communication via libusb is not reliable for you, you still can use
the "deprecated" hpusbscsi driver in the kernel - but _not_ the
scanner driver.

I've tried so many configuration variations over the last couple of weeks that I've gotten confused about what configuration settings do what.  I don't think I understand the terminology.

I now think I should avoid using the scanner driver.  Would
rmmod scanner
do this for me, or is something else necessary?

I would like to use libusb, but I have not been able to figure out what causes the libusb driver to be loaded.  Some parts of my system refer to usbfs; others refer to usbdevfs.  I think I need everything in the system refering to one or everything to the other, but when I tried changing the references to usbfs, I produced a system that would not boot, and had to restore a backup.

What is the best way to get back to a clean system?
Is there a modprobe command I should be using to load the libusb driver?  If so, should I add it to /etc/rc.d/rc.local to get it to run during boot?

I currently have hpusbbscsi disabled.  Should both libusb and hpusbbscsi be enabled?


... 

The scanner driver will not work - because of the missing interrupt
endpoint notification support - but I do not want to support a 3rd "to
be removed in the future" access method. So I think hpusbscsi and
libusb should be ok.

--=-RKQ6ngouQ5FBJDhEbC7Y-- From tomf@sjpc.org Mon Jun 30 05:45:37 2003 From: tomf@sjpc.org (Thomas Frayne) Date: 29 Jun 2003 21:45:37 -0700 Subject: [sane-devel] HP 7450C ... addendum In-Reply-To: <20030629.232524.607955671.rene.rebe@gmx.net> References: <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> <20030629.232524.607955671.rene.rebe@gmx.net> Message-ID: <1056948336.3460.127.camel@localhost.localdomain> --=-HHTH88Z4DtJatcF7GpR3 Content-Type: text/plain Content-Transfer-Encoding: 7bit On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: > Hi, > > On: Fri, 27 Jun 2003 23:11:10 +0200, > Henning Meier-Geinitz wrote: ... > Which host controller chip and respective kernel driver is this? I sent my last message prematurely. Please disregard it. My system is Redhat 9.0, with up2date run today. I have sane-backends-1.0.12.tar.gz and xsane-0.91.tar.gz installed. Here are messages that may help answer your questions. If this won't do it, could you tell me how to find the answers to your questions? T: Bus=04 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=9000 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=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0801 Rev= 0.01 S: Manufacturer=hp S: Product=hp scanjet 7400c S: SerialNumber=87 tem 7400c C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=01(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms Jun 29 07:33:03 localhost kernel: Linux version 2.4.20-18.9 (root@gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Wed Jun 4 15:04:35 PDT 2003 Installed via up2date. Jun 29 07:33:05 localhost kernel: usb.c: registered new driver usbdevfs Jun 29 07:33:05 localhost kernel: usb.c: registered new driver hub Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0 Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0870000, IRQ 5 Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC Corporation USB Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 3 ports detected Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0 Jun 29 07:33:06 localhost rc: Starting pcmcia: succeeded Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0872000, IRQ 9 Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC Corporation USB (#2) Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.0-1, assigned address 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB 2.0 Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem f087a000 Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 3 Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size set incorrectly (32 bytes) by BIOS/FW. Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size corrected to 128. Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22 Jun 29 07:33:06 localhost kernel: usb.c: USB disconnect on device 00:0b.0-1 address 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 5 ports detected Jun 29 07:33:06 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time 07:14:02 May 29 2003 Jun 29 07:33:06 localhost kernel: usb-uhci.c: High bandwidth mode enabled Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:07.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 29 07:33:06 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, IRQ 10 Jun 29 07:33:06 localhost kernel: usb-uhci.c: Detected 2 ports Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 4 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected Jun 29 07:33:06 localhost kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hiddev Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hid Jun 29 07:33:06 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik Jun 29 07:33:06 localhost kernel: hid-core.c: USB HID support drivers Jun 29 07:33:06 localhost kernel: mice: PS/2 mouse device common for all mice Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1, assigned address 2 Jun 29 07:33:06 localhost mount: mount: none already mounted or /proc/bus/usb busy Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost mount: mount: according to mtab, usbdevfs is already mounted on /proc/bus/usb Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected Jun 29 07:33:06 localhost netfs: Mounting other filesystems: failed Jun 29 07:33:06 localhost kernel: Adding Swap: 1582360k swap-space (priority -1) Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 29 07:33:06 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.2, assigned address 3 Jun 29 07:33:06 localhost kernel: usb.c: USB device 3 (vend/prod 0x2821/0x5001) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.4, assigned address 4 Jun 29 07:33:06 localhost kernel: usb.c: USB device 4 (vend/prod 0x3f0/0x3404) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: Initializing USB Mass Storage driver... Jun 29 07:33:06 localhost kernel: usb.c: registered new driver usb-storage Jun 29 07:33:07 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices Jun 29 07:33:07 localhost kernel: Vendor: ASUS Model: CRW-5224A Rev: 1.00 Jun 29 07:33:07 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 29 07:33:07 localhost kernel: USB Mass Storage support registered. Jun 29 07:33:07 localhost kernel: hdc: attached ide-scsi driver. Jun 29 07:33:07 localhost kernel: scsi2 : SCSI host adapter emulation for IDE ATAPI devices Jun 29 07:33:07 localhost kernel: Vendor: HP Model: CD-Writer+ 8100 Rev: 1.0g Jun 29 07:33:07 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 29 07:33:07 localhost kernel: usb.c: registered new driver usblp Jun 29 07:33:07 localhost kernel: printer.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404 > If communication via libusb is not reliable for you, you still can use > the "deprecated" hpusbscsi driver in the kernel - but _not_ the > scanner driver. I've tried so many configuration variations over the last couple of weeks that I've gotten confused about what configuration settings do what. I don't think I understand the terminology. I now think I should avoid using the scanner driver. Would rmmod scanner do this for me, or is something else necessary? How can I tell whether or not I am using the scanner driver? I would like to use libusb, but I have not been able to figure out what causes the libusb driver to be loaded. Some parts of my system refer to usbfs; others refer to usbdevfs. I think I need everything in the system refering to one or everything to the other, but when I tried changing the usbdevfs references to usbfs, I produced a system that would not boot, and had to restore a backup. What is the best way to get back to a clean system? Is there a modprobe command I should be using to load the libusb driver? If so, should I add it to /etc/rc.d/rc.local to get it to run during boot? My guess is that modprobe scanner vendor=0x03f0 product=0x0801 should be added to /etc/rc.d/rc.local. Is that right? If so, what else needs to be done? What should be done to get the scanner mounted as rw with permissions for everyone to use it? The things I have tried with fstab did not work, since the system tried to mount it twice. I currently have hpusbbscsi disabled. Should both libusb and hpusbbscsi be enabled? ... > The scanner driver will not work - because of the missing interrupt > endpoint notification support - but I do not want to support a 3rd "to > be removed in the future" access method. So I think hpusbscsi and > libusb should be ok. --=-HHTH88Z4DtJatcF7GpR3 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: 
Hi,

On: Fri, 27 Jun 2003 23:11:10 +0200,
    Henning Meier-Geinitz <henning@meier-geinitz.de> wrote:
... 
Which host controller chip and respective kernel driver is this?

I sent my last message prematurely.  Please disregard it.

My system is Redhat 9.0, with up2date run today.  I have sane-backends-1.0.12.tar.gz and xsane-0.91.tar.gz installed.


Here are messages that may help answer your questions.  If this won't do it, could you tell me how to find the answers to your questions?

T:  Bus=04 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=9000
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=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=03f0 ProdID=0801 Rev= 0.01
S:  Manufacturer=hp
S:  Product=hp scanjet 7400c
S:  SerialNumber=87 tem  7400c
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=  2mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none)
E:  Ad=01(O) Atr=02(Bulk) MxPS=   8 Ivl=0ms
E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
E:  Ad=83(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms


Jun 29 07:33:03 localhost kernel: Linux version 2.4.20-18.9 (root@gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Wed Jun 4 15:04:35 PDT 2003  Installed via up2date.
Jun 29 07:33:05 localhost kernel: usb.c: registered new driver usbdevfs
Jun 29 07:33:05 localhost kernel: usb.c: registered new driver hub
Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0
Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0870000, IRQ 5
Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC Corporation USB
Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 1
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 3 ports detected
Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0
Jun 29 07:33:06 localhost rc: Starting pcmcia:  succeeded
Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0872000, IRQ 9
Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC Corporation USB (#2)
Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 2
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.0-1, assigned address 2
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected
Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0
Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB 2.0
Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem f087a000
Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 3
Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size set incorrectly (32 bytes) by BIOS/FW.
Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size corrected to 128.
Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22
Jun 29 07:33:06 localhost kernel: usb.c: USB disconnect on device 00:0b.0-1 address 2
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 5 ports detected
Jun 29 07:33:06 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time 07:14:02 May 29 2003
Jun 29 07:33:06 localhost kernel: usb-uhci.c: High bandwidth mode enabled
Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:07.2
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2
Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0
Jun 29 07:33:06 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, IRQ 10
Jun 29 07:33:06 localhost kernel: usb-uhci.c: Detected 2 ports
Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 4
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected
Jun 29 07:33:06 localhost kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hiddev
Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hid
Jun 29 07:33:06 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vojtech@suse.cz>
Jun 29 07:33:06 localhost kernel: hid-core.c: USB HID support drivers
Jun 29 07:33:06 localhost kernel: mice: PS/2 mouse device common for all mice
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1, assigned address 2
Jun 29 07:33:06 localhost mount: mount: none already mounted or /proc/bus/usb busy
Jun 29 07:33:06 localhost kernel: hub.c: USB hub found
Jun 29 07:33:06 localhost mount: mount: according to mtab, usbdevfs is already mounted on /proc/bus/usb
Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected
Jun 29 07:33:06 localhost netfs: Mounting other filesystems:  failed
Jun 29 07:33:06 localhost kernel: Adding Swap: 1582360k swap-space (priority -1)
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2
Jun 29 07:33:06 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver.
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.2, assigned address 3
Jun 29 07:33:06 localhost kernel: usb.c: USB device 3 (vend/prod 0x2821/0x5001) is not claimed by any active driver.
Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.4, assigned address 4
Jun 29 07:33:06 localhost kernel: usb.c: USB device 4 (vend/prod 0x3f0/0x3404) is not claimed by any active driver.
Jun 29 07:33:06 localhost kernel: Initializing USB Mass Storage driver...
Jun 29 07:33:06 localhost kernel: usb.c: registered new driver usb-storage
Jun 29 07:33:07 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices
Jun 29 07:33:07 localhost kernel:   Vendor: ASUS      Model: CRW-5224A         Rev: 1.00
Jun 29 07:33:07 localhost kernel:   Type:   CD-ROM                             ANSI SCSI revision: 02
Jun 29 07:33:07 localhost kernel: USB Mass Storage support registered.
Jun 29 07:33:07 localhost kernel: hdc: attached ide-scsi driver.
Jun 29 07:33:07 localhost kernel: scsi2 : SCSI host adapter emulation for IDE ATAPI devices
Jun 29 07:33:07 localhost kernel:   Vendor: HP        Model: CD-Writer+ 8100   Rev: 1.0g
Jun 29 07:33:07 localhost kernel:   Type:   CD-ROM                             ANSI SCSI revision: 02
Jun 29 07:33:07 localhost kernel: usb.c: registered new driver usblp
Jun 29 07:33:07 localhost kernel: printer.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404



If communication via libusb is not reliable for you, you still can use
the "deprecated" hpusbscsi driver in the kernel - but _not_ the
scanner driver.

I've tried so many configuration variations over the last couple of weeks that I've gotten confused about what configuration settings do what.  I don't think I understand the terminology.

I now think I should avoid using the scanner driver.  Would
rmmod scanner
do this for me, or is something else necessary?  How can I tell whether or not I am using the scanner driver?

I would like to use libusb, but I have not been able to figure out what causes the libusb driver to be loaded.  Some parts of my system refer to usbfs; others refer to usbdevfs.  I think I need everything in the system refering to one or everything to the other, but when I tried changing the usbdevfs references to usbfs, I produced a system that would not boot, and had to restore a backup.

What is the best way to get back to a clean system?
Is there a modprobe command I should be using to load the libusb driver?  If so, should I add it to /etc/rc.d/rc.local to get it to run during boot?
My guess is that
modprobe scanner vendor=0x03f0 product=0x0801
should be added to /etc/rc.d/rc.local.  Is that right?  If so,  what else needs to be done?

What should be done to get the scanner mounted as rw with permissions for everyone to use it?  The things I have tried with fstab did not work, since the system tried to mount it twice.

I currently have hpusbbscsi disabled.  Should both libusb and hpusbbscsi be enabled?


... 
The scanner driver will not work - because of the missing interrupt
endpoint notification support - but I do not want to support a 3rd "to
be removed in the future" access method. So I think hpusbscsi and
libusb should be ok.

--=-HHTH88Z4DtJatcF7GpR3-- From jollyprince@juno.com Mon Jun 30 05:51:42 2003 From: jollyprince@juno.com (jollyprince@juno.com) Date: Mon, 30 Jun 2003 04:51:42 GMT Subject: [sane-devel] Re: Visioneer 5800 Message-ID: <20030629.215242.2373.604481@webmail01.lax.untd.com> --- gerard klaver wrote: On Sun, 2003-06-29 at 20:38, jollyprince@juno.com wrote: > T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=04a7 ProdID=0226 Rev= 1.00 > S: Manufacturer=Visioneer > S: Product=USB Scanner > S: SerialNumber=RTS8801C2-004 > C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms > E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms > > RESULT: of cat /proc/bus/usb/devices | more > Realtek chip, see www.realtec.com.tw at page scanner ic some info is given about the chip. -- ---------- m.vr.gr. Gerard Klaver Bingo! You may have nailed it. Since the above serial number translates to a Realtek RTS88xx family chip, it may preclude the LM9832 of my previous Email. I made a request to Tech Support in Taiwan for data on the Realtek chip for Visioneer 5800. Once I get it I'm not sure what to do with it but it's a start. From jollyprince@juno.com Mon Jun 30 05:54:00 2003 From: jollyprince@juno.com (jollyprince@juno.com) Date: Mon, 30 Jun 2003 04:54:00 GMT Subject: [sane-devel] Fw: RTS8801C2 Serial Number Chipset Message-ID: <20030629.215444.2373.604497@webmail01.lax.untd.com> ---------- Forwarded Message ---------- I'm researching technical data to write a driver for a Visioneer 5800 Scanner. The above serial number was referenced when checking out the Visioneer 5800 specs. Am I on the right track and can you provide me with some help on this project? From kouno.hironori@pfu.fujitsu.com Mon Jun 30 06:55:57 2003 From: kouno.hironori@pfu.fujitsu.com (hironori kohno) Date: Mon, 30 Jun 2003 14:55:57 +0900 Subject: [sane-devel] Re: [sane-devel]The report about 'sane-fujitsu' In-Reply-To: References: <200306271648.FEE65799.SOPPLP.PVJSIJO@pfu.fujitsu.com> Message-ID: <200306301455.BAG28258.JVO.SSPPPPOIJL@pfu.fujitsu.com> $B$N!"(B "Re: [sane-devel] [sane-devel]The report about 'sane-fujitsu' " $B$K$*$$$F!"(B ""m. allan noah" "$B$5$s$O=q$-$^$7$?!'(B > you use old version of sane. remove redhat version of sane-backend: > > rpm -e --force --nodeps sane-backend > > and re-install sane: > > ./configure --prefix=/usr --sysconfdir=/etc > make > make install > > see below for more comments > > On Fri, 27 Jun 2003, hironori kohno wrote: > > > Hi, > > > > I performed testing about 'sane-fujitsu'. > > It reports below. > > > > OS: RedHat Linux V8 > > Scanner: fi-4220C > > > > Indication matters: > > Hi, i performed the following test again. OS: RedHat V9 Scanner: fi-4220x Sane : cvs version + patch 1. color-mode The negative picture was acquired when scan was carried out by Color Mode. A check of rif has improved the above-mentioned phenomenon. Even if it does not check rif-option, i consider that it is better to output the same tone as the color of a paper. Bye, Kouno -- kouno.hironori@pfu.fujitsu.com From renito73@hotmail.com Mon Jun 30 09:44:43 2003 From: renito73@hotmail.com (Renito 73) Date: Mon, 30 Jun 2003 08:44:43 +0000 Subject: [sane-devel] Genius Vivid-3xe Message-ID: I have troubles to use my Genius Vivid-3xe scanner... sane recognizes it, but applications don't use it... my usb configuration is working properly since I took pictures with my webcam... I did chmod rwxrwxrwx /dev/usb/scanner* since only root had access to the devices... my usb driver is usb-uhcii.o (the other one uhci.o worked fine but my vmware did not work with it, so I changed to usb-uhci.o instead but camera and vmware continued working fine... Background: reno@voodoo:~$ sane-config --version 1.0.12 reno@voodoo:~$ sane-find-scanner found USB scanner (vendor=0x0458, product=0x2017) at libusb:001:004 (3xe) found USB scanner (vendor=0x046d, product=0x0840) at libusb:001:002 (webcam) reno@voodoo:~$ scanimage -L device `gt68xx:/dev/usb/scanner0' is a Genius Colorpage Vivid3xe flatbed scanner but when running xsane or kooka they say scanner is not round... what could be the problem? I created this script to load the scanner.o module modprobe scanner vendor=0x0458 product=0x2017 got vendor and product from KDE Info Center (USB devices)... what could be wrong? thanx for your help! :) _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From rene.rebe@gmx.net Mon Jun 30 09:49:09 2003 From: rene.rebe@gmx.net (Rene Rebe) Date: Mon, 30 Jun 2003 10:49:09 +0200 (CEST) Subject: [sane-devel] HP 7450C ... addendum In-Reply-To: <1056948336.3460.127.camel@localhost.localdomain> References: <20030627211110.GM2318@meier-geinitz.de> <20030629.232524.607955671.rene.rebe@gmx.net> <1056948336.3460.127.camel@localhost.localdomain> Message-ID: <20030630.104909.730551847.rene.rebe@gmx.net> Hi, On: 29 Jun 2003 21:45:37 -0700, Thomas Frayne wrote: > On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: = > = > > Which host controller chip and respective kernel driver is this? [...] > Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase > 0xf0870000, IRQ 5 > Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC > Corporation USB Ah - ohci! The ohci driver in the kernel should be fine. It works with my SiS based Athlon boards and my iBook ... (in the last weeks I notices many problems with the two uhci drivers in general - not related to SANE/Avision). > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation U= SB > 2.0 > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem > f087a000 > Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, > assigned bus number 3 > Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size se= t > incorrectly (32 bytes) by BIOS/FW. > Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size > corrected to 128. > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, > EHCI 0.95, driver 2003-Jan-22 Hm - or ehci? Could you send the output of lsusb? > > If communication via libusb is not reliable for you, you still can = use > > the "deprecated" hpusbscsi driver in the kernel - but _not_ the > > scanner driver. > = > = > I've tried so many configuration variations over the last couple of > weeks that I've gotten confused about what configuration settings do > what. I don't think I understand the terminology. Ok - I rephrase it: There is a generic USB scanner driver in the kernel. The resulting module is named scanner.o. This driver does not work with Avision/HP scanners. You should no try to force it's loading. Instead you should use access via libusb. Libusb is a normal library (libusb.so in /usr/lib or so) which allows low-level access to usb devices from user-space applications. This library is automatically used when the permissions in /proc/bus/usb/0*/* allow you to access the device. But unfortunately this results in strance timeouts on your system. So as short time soluion and test you could try: Access via the "depricated" hpusbscsi driver. It is a kernel driver which name is hpusbscsi.o. It was written to access Avision and HP usb scanners via an emulated SCSI interface (/dev/sg?). When the hpusbscsi module is loaded the scanner would look like a scsi device. > I now think I should avoid using the scanner driver. Would > rmmod scanner = > do this for me, or is something else necessary? How can I tell wheth= er > or not I am using the scanner driver? lsmod lists the loaded kernel modules. A rmmod scanner does only unload the driver until the next reboot. You need to modify the place where it gets loaded on your distribution (maybe hotplug so /etc/hotplug ...) or you "simply" remove the scanner.o file in /lib/modules//... from your disk (if you do not have other USB scanners that needs to be accessed via the module ...) > I would like to use libusb, but I have not been able to figure out wh= at > causes the libusb driver to be loaded. Some parts of my system refer= to There is no libusb "driver" - it is a normal user-space library. Youl only need the usbfb mounted to /proc/bus/usb - and the permissions must allow your user to access the device. > usbfs; others refer to usbdevfs. I think I need everything in the > system refering to one or everything to the other, but when I tried > changing the usbdevfs references to usbfs, I produced a system that > would not boot, and had to restore a backup. If RedHat likes the usbdevfs name simply leave it as it is. usbdevfs and usbfs are the same. (That one alias is depricate and will disappear in the future does only need to wory RedHat - not you) > What is the best way to get back to a clean system? > Is there a modprobe command I should be using to load the libusb > driver? If so, should I add it to /etc/rc.d/rc.local to get it to ru= n > during boot? As written above - only usbfs need to be mounted and the permissions needs to be correct. Nothing else - no kernel driver. > My guess is that = > modprobe scanner vendor=3D0x03f0 product=3D0x0801 > should be added to /etc/rc.d/rc.local. Is that right? If so, what > else needs to be done? Nope - please do not force to load the not SANE/Avision compatible scanner driver. > What should be done to get the scanner mounted as rw with permissions= > for everyone to use it? The things I have tried with fstab did not > work, since the system tried to mount it twice. > = > I currently have hpusbbscsi disabled. Should both libusb and hpusbbs= csi > be enabled? You can use hpusbscsi - it should work fine - but when you use the new libusb access method - the hpusbscsi module should not be loaded. Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene.rebe@gmx.net http://www.rocklinux.org http://www.rocklinux.org/people/rene = http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From renito73@hotmail.com Mon Jun 30 11:00:46 2003 From: renito73@hotmail.com (Renito 73) Date: Mon, 30 Jun 2003 10:00:46 +0000 Subject: [sane-devel] Genius Vivid-3xe part II Message-ID: Finally I did it, just forgot the firmware file and now is fixed, but I have a doubt... xsane has 8/12 bit depth, does it mean the bpp? this model supports up to 24 or 36 (don't remember) but is it compile configuration related, or it is a driver limitation or what it means? sorry if it is a stupid question again but it is 5am and can't sleep fine if I leave something pending :P Regards _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From mfleming@michaelfleming.webcentral.com.au Mon Jun 30 11:47:42 2003 From: mfleming@michaelfleming.webcentral.com.au (Michael Fleming) Date: Mon, 30 Jun 2003 20:47:42 +1000 Subject: [sane-devel] Genius Vivid-3xe In-Reply-To: References: Message-ID: <20030630104742.GA5090@michaelfleming.webcentral.com.au> On Mon, Jun 30, 2003 at 08:44:43AM +0000, Renito 73 waffled thusly: > I have troubles to use my Genius Vivid-3xe scanner... sane recognizes it, > but applications don't use it... my usb configuration is working properly > since I took pictures with my webcam... I did chmod rwxrwxrwx > /dev/usb/scanner* since only root had access to the devices... my usb > driver is usb-uhcii.o (the other one uhci.o worked fine but my vmware did > not work with it, so I changed to usb-uhci.o instead but camera and vmware > continued working fine... > > Background: Let's compare notes - I've got the same model and make working fine, even for regular users. (Redhat 9.0, sane-backends 1.0.12, kernel 2.4.20-18.9 (RH Errata vendor kernel)) > reno@voodoo:~$ sane-config --version > 1.0.12 defender:~:$ sane-config --version 1.0.12 > reno@voodoo:~$ sane-find-scanner > found USB scanner (vendor=0x0458, product=0x2017) at libusb:001:004 (3xe) > found USB scanner (vendor=0x046d, product=0x0840) at libusb:001:002 (webcam) defender:~:$ sane-find-scanner | grep ^found found USB scanner (vendor=0x0458, product=0x2017 [600dpi USB Scanner]) at libusb:001:002 > reno@voodoo:~$ scanimage -L > device `gt68xx:/dev/usb/scanner0' is a Genius Colorpage Vivid3xe flatbed > scanner I'm not using the scanner.o module, never had much luck with it. libusb 0.1.6 works well enough for me. defender:~:$ scanimage -L device `gt68xx:libusb:001:002' is a Genius Colorpage Vivid3xe flatbed scanner > but when running xsane or kooka they say scanner is not round... what could > be the problem? I created this script to load the scanner.o module > > modprobe scanner vendor=0x0458 product=0x2017 Have you tried actually scanning an image? I really don't see any permissions or access related problems. (I had to remount my /proc/bus/usb devmode=0666 to enable user access, but that might be a Redhat-only issue. YMMV.). You can at least find the scanner as a user, which is encouraging. What happens when you run "scanimage > out.pnm"? > got vendor and product from KDE Info Center (USB devices)... > > what could be wrong? Do you see lots of "bulk_timeout"-like messages among your syslog entries when you try and scan or run xsane/kooka? There was a small patch for the gt68xx backend back in late April that addressed a USB timeout issue (it saw the scanner but subsequent operations seemed to overwhelm the USB bus on many systems). Check the archives for this, apply and recompile if you haven't got it. It worked spectacularly well for me. > thanx for your help! :) Cheers, Michael Fleming. (PS Henning, the colour handling/matching on this backend and the Genius Vivid3XE seems to be OK in my tests/experience, I'll put some more examples if you wish) -- Michael Fleming "Bother" said the Borg, "We've assimilated Pooh!" From sigurd.stordal@stud.ibg.uit.no Mon Jun 30 14:49:37 2003 From: sigurd.stordal@stud.ibg.uit.no (Sigurd Stordal) Date: Mon, 30 Jun 2003 15:49:37 +0200 Subject: [sane-devel] Problems with the canon backend for a canoscan 2700F. In-Reply-To: <20030624174224.GB7697@meier-geinitz.de> References: <200306241556.48630.sigurd.stordal@stud.ibg.uit.no> <20030624174224.GB7697@meier-geinitz.de> Message-ID: <200306301549.43807.sigurd.stordal@stud.ibg.uit.no> Will work with sane-backend 1.0.11. So something has to have changed from= .11=20 to .12 that makes the canon backend not work for my filmscanner. So, maybe take a look at what has changed from .11 to .12, to find out=20 possible reasons for this. --=20 Sigurd Stordal President of GOGS Experimental Petrologist From tomf@sjpc.org Mon Jun 30 16:44:13 2003 From: tomf@sjpc.org (Thomas Frayne) Date: 30 Jun 2003 08:44:13 -0700 Subject: [sane-devel] HP 7450C ... addendum In-Reply-To: <20030630.104909.730551847.rene.rebe@gmx.net> References: <20030627211110.GM2318@meier-geinitz.de> <20030629.232524.607955671.rene.rebe@gmx.net> <1056948336.3460.127.camel@localhost.localdomain> <20030630.104909.730551847.rene.rebe@gmx.net> Message-ID: <1056987852.3718.109.camel@localhost.localdomain> Please read the procedure at the end of this note before looking at the interleaved comments. On Mon, 2003-06-30 at 01:49, Rene Rebe wrote: > Hi, > > On: 29 Jun 2003 21:45:37 -0700, > Thomas Frayne wrote: > > > On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: > > > > > Which host controller chip and respective kernel driver is this? > > [...] > > > Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase > > 0xf0870000, IRQ 5 > > Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC > > Corporation USB > > Ah - ohci! The ohci driver in the kernel should be fine. It works with > my SiS based Athlon boards and my iBook ... (in the last weeks I > notices many problems with the two uhci drivers in general - not > related to SANE/Avision). Is there anything I should be doing about this? > > > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB > > 2.0 > > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem > > f087a000 > > Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, > > assigned bus number 3 > > Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size set > > incorrectly (32 bytes) by BIOS/FW. > > Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size > > corrected to 128. > > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, > > EHCI 0.95, driver 2003-Jan-22 > > Hm - or ehci? > > Could you send the output of lsusb? [root@localhost root]# lsusb Unknown line at line 58 Unknown line at line 2296 Unknown line at line 2297 Unknown line at line 2298 Unknown line at line 2299 Unknown line at line 2300 Unknown line at line 2301 Unknown line at line 2302 Unknown line at line 2303 Unknown line at line 2304 Unknown line at line 2305 Unknown line at line 2306 Unknown line at line 2307 Unknown line at line 2308 Unknown line at line 2309 Unknown line at line 2310 Unknown line at line 2311 Unknown line at line 2312 Unknown line at line 2313 Unknown line at line 2314 Unknown line at line 2315 Unknown line at line 2316 Unknown line at line 2317 Unknown line at line 2318 Unknown line at line 2319 Unknown line at line 2320 Unknown line at line 2321 Unknown line at line 2322 Unknown line at line 2323 Unknown line at line 2324 Unknown line at line 2325 Unknown line at line 2326 Unknown line at line 2327 Unknown line at line 2328 Unknown line at line 2329 Unknown line at line 2330 Unknown line at line 2331 Unknown line at line 2332 Unknown line at line 2333 Unknown line at line 2334 Unknown line at line 2335 Bus 004 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 iProduct 2 USB UHCI Root Hub iSerial 1 9000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 8 bInterval 255 Language IDs: (length=4) 0000 (null)((null)) Bus 004 Device 002: ID 03f0:0801 Hewlett-Packard Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 Interface bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x03f0 Hewlett-Packard idProduct 0x0801 bcdDevice 0.01 iManufacturer 1 hp iProduct 2 hp scanjet 7400c iSerial 3 87 tem 7400c bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 0 Interface bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type none wMaxPacketSize 8 bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 8 bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type none wMaxPacketSize 64 bInterval 0 Language IDs: (length=4) 0409 English(US) Bus 003 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.04 iManufacturer 3 Linux 2.4.20-18.9 ehci-hcd iProduct 2 NEC Corporation USB 2.0 iSerial 1 00:0b.2 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 2 bInterval 12 Language IDs: (length=4) 0000 (null)((null)) Bus 003 Device 002: ID 03f3:0081 Adaptec, Inc. cannot get string descriptor 1, error = Broken pipe(32) cannot get string descriptor 2, error = Broken pipe(32) Is there anything I should do about this? Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 bMaxPacketSize0 64 idVendor 0x03f3 Adaptec, Inc. idProduct 0x0081 bcdDevice 1.00 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 1 bInterval 12 Language IDs: (length=4) 0409 English(US) Bus 003 Device 003: ID 03f0:3404 Hewlett-Packard Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 Interface bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x03f0 Hewlett-Packard idProduct 0x3404 bcdDevice 1.00 iManufacturer 1 hp iProduct 2 deskjet 6122 iSerial 3 MY2771C0ZP50 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type none wMaxPacketSize 64 bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type none wMaxPacketSize 64 bInterval 0 Language IDs: (length=4) 0409 English(US) Bus 002 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 iProduct 2 USB OHCI Root Hub iSerial 1 f0872000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 2 bInterval 255 Language IDs: (length=4) 0000 (null)((null)) Bus 001 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 iProduct 2 USB OHCI Root Hub iSerial 1 f0870000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 2 bInterval 255 Language IDs: (length=4) 0000 (null)((null)) [root@localhost root]# This seems to say that bus 004 is a USB UHCI hub and Bus 004 Device 002: ID 03f0:0801 Hewlett-Packard is my Scanjet. Does that imply that the Scanjet is using UHCI? > > > > If communication via libusb is not reliable for you, you still can use > > > the "deprecated" hpusbscsi driver in the kernel - but _not_ the > > > scanner driver. > > > > > > I've tried so many configuration variations over the last couple of > > weeks that I've gotten confused about what configuration settings do > > what. I don't think I understand the terminology. > > Ok - I rephrase it: > > There is a generic USB scanner driver in the kernel. The resulting > module is named scanner.o. This driver does not work with Avision/HP > scanners. You should no try to force it's loading. Instead, I'll try to force it not to be loaded, e.g., by renaming scanner.o. Right? > > Instead you should use access via libusb. Libusb is a normal library > (libusb.so in /usr/lib or so) which allows low-level access to usb > devices from user-space applications. This library is automatically > used when the permissions in /proc/bus/usb/0*/* allow you to access > the device. But unfortunately this results in strance timeouts on your > system. So as short time soluion and test you could try: > [root@localhost root]# ls -l /proc/bus/usb/004/* -rw-r--r-- 1 root root 18 Jun 30 06:51 /proc/bus/usb/004/001 -rw-r--r-- 1 root root 18 Jun 30 06:51 /proc/bus/usb/004/002 [root@localhost root]# chmod 666 /proc/bus/usb/004/* [root@localhost root]# ls -l /proc/bus/usb/004/* -rw-rw-rw- 1 root root 18 Jun 30 06:51 /proc/bus/usb/004/001 -rw-rw-rw- 1 root root 18 Jun 30 06:51 /proc/bus/usb/004/002 [root@localhost root]# Right? > Access via the "depricated" hpusbscsi driver. It is a kernel driver > which name is hpusbscsi.o. It was written to access Avision and HP usb > scanners via an emulated SCSI interface (/dev/sg?). When the hpusbscsi > module is loaded the scanner would look like a scsi device. I currently have hpusbscsi.o renamed to disable it. I'll leave it disabled for now, and try to use libusb. If I see > > > I now think I should avoid using the scanner driver. Would > > rmmod scanner > > do this for me, or is something else necessary? How can I tell whether > > or not I am using the scanner driver? > > lsmod lists the loaded kernel modules. A rmmod scanner does only > unload the driver until the next reboot. You need to modify the place > where it gets loaded on your distribution (maybe hotplug so > /etc/hotplug ...) or you "simply" remove the scanner.o file in > /lib/modules//... from your disk (if you do not have other > USB scanners that needs to be accessed via the module ...) > > > I would like to use libusb, but I have not been able to figure out what > > causes the libusb driver to be loaded. Some parts of my system refer to > > There is no libusb "driver" - it is a normal user-space library. Youl > only need the usbfb mounted to /proc/bus/usb - and the permissions > must allow your user to access the device. > > > usbfs; others refer to usbdevfs. I think I need everything in the > > system refering to one or everything to the other, but when I tried > > changing the usbdevfs references to usbfs, I produced a system that > > would not boot, and had to restore a backup. > > If RedHat likes the usbdevfs name simply leave it as it is. usbdevfs > and usbfs are the same. (That one alias is depricate and will > disappear in the future does only need to wory RedHat - not you) > > > What is the best way to get back to a clean system? > > Is there a modprobe command I should be using to load the libusb > > driver? If so, should I add it to /etc/rc.d/rc.local to get it to run > > during boot? > > As written above - only usbfs need to be mounted and the permissions > needs to be correct. Nothing else - no kernel driver. > [root@localhost root]# mount /dev/sdb2 on / type ext2 (rw) none on /proc type proc (rw) usbdevfs on /proc/bus/usb type usbdevfs (rw) I am still confused here. You said to leave usbdevfs as it is, but you also said that libusb times out. Should I try libusb first, and try hpusbscsi if libusb fails? When modprobe scanner vendor=0x03f0 product=0x0801 was in effect, scanimage -L failed, but after rmmod scanner, I got: [root@localhost root]# scanimage -L device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c flatbed scanner [root@localhost root]# However, When I tried to scan with xsane, it failed with a timeout. Is this the libusb failure you were refering to? I'd like to try hpusbscsi without rebooting. The procedure to do this, as I currently understand it is: Turn off the scanner to clear the "initializing" state Rename back to hpusbscsi.o Don't do a modprobe; do an rmmod scanner to make sure. Modify /etc/rc.d/rc.local to remove the modprobe at the next boot Modify /usr/local/etc/sane.d/avision.conf to remove the usb lines and insert: scsi AVISION scsi HP scsi hp scsi /dev/scanner scsi /dev/usb/scanner0 umount /proc type proc mount what? Anything wrong, redundant, or missing? > > What should be done to get the scanner mounted as rw with permissions > > for everyone to use it? The things I have tried with fstab did not > > work, since the system tried to mount it twice. > > > > I currently have hpusbbscsi disabled. Should both libusb and hpusbbscsi > > be enabled? > > You can use hpusbscsi - it should work fine - but when you use the new > libusb access method - the hpusbscsi module should not be loaded. Should libusb be disabled when I am trying to use hpusbscsi? If so, how should I disable libusb? > > Sincerely yours, > RenƩ Rebe > - ROCK Linux stable release maintainer > > -- > RenƩ Rebe - Europe/Germany/Berlin > rene@rocklinux.org rene.rebe@gmx.net > http://www.rocklinux.org http://www.rocklinux.org/people/rene > http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From anoah@pfeiffer.edu Mon Jun 30 17:20:03 2003 From: anoah@pfeiffer.edu (m. allan noah) Date: Mon, 30 Jun 2003 12:20:03 -0400 (EDT) Subject: [sane-devel] Re: fujitsu patch, was: The report about 'sane-fujitsu' In-Reply-To: Message-ID: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1386611826-1974716381-1056990003=:8012 Content-Type: TEXT/PLAIN; charset=US-ASCII re-sending gzip'd due to file size.... > attached is a (rather large) patch to the cvs version of the fujitsu > backend. i am sending it to the list cause the backend maintainer is on > vacation, and so this wont be committed to cvs for a while, and i know > there are some fujitsu users outthere looking for some of this > functionality... (wink, wink, nudge, nudge :) > > 1. re-structured color mode code to support other modes (me, not finished) > 2. added code to select the various color read modes of some scanners (me) > 3. added code to support rrggbb mode of fi-4340 (oliver s.) > 4. moved a good bit of code so it is under the correct headings (me) > > allan > -- "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 --1386611826-1974716381-1056990003=:8012 Content-Type: APPLICATION/octet-stream; name="man-fujitsu-patch7.txt.gz" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="man-fujitsu-patch7.txt.gz" H4sICAiY/D4AA21hbi1mdWppdHN1LXBhdGNoNy50eHQA7X1pc9tIkujn9q9A e8I9okRJBHERlqWZdtvt6Hju8YTt3n0bO7sKkAQp2BSpJciW/Wb0319mHagT F0F57FkhumWSqMqqysrKyqq8ptls5hyvnXEy+Zgup6ez7Ydsk29PJs4yvRXf HnlhNOp74WgwKT49euY4znaZZ/NlOnWy5cbZrDbJ4nKabJLLPPt/ad/Bj6/T 2YZ+utysLtdpMj1Ta06ukrVzuEjW8/T5djZL12cmZOntO4DsnDuDs0fHx8eP Lmr7kNEvC0s3Lkq6cTlm/TCgy68JfNoTQIeHOPEnxScyBj5+KJVPkuUyXR9f jD9v0vzyBuvDT5eLbJk6h+I1+fEqzeZXm8ub7FO6yCk6tHEBRA5cIEIaascW L6wtSvDJmEMcaTQpPpGOSlOldEKaWmM2ixHI+LXV1suwnkFnYm+Cfwh8h6Ge zzRAOiim4pnefM/5k5iop/pbgV0bVBnjz8yeIWi5yFOzCCIyDrDvQdH3fJNs tjnAx2YuaRUCZLxYTT46BwwtfbmvKm33HaXb7QCy7hkQvWgQTvBP0VGOEkbj 6uqSO+AY1KmW9SIXcAB/CtCz23W2SZ0DZYhusZxpl2Y3PbUdpVYxDms1aG2E TY4UkiEjOa4aijwMo6AXDYFDwh8FRRoieTs9E0daSakt0uPhEIEPCfDbq2yR CrqWgLE3euUgnuCfkhVSReZQOcKWo6Ex87xIfnyRXW7WyTJHwl6ky/nmyhye qHFcVsWLRmECfyKo+J3aBjLa2I0S+BMTsACBEPT1aors6e3LH19c/vrmxcvL v/747h0W9gFU7MdiHZRV8Aax+/bVc6wT+lAnHNXX4Y2MYqgQ++o81lf0B8M4 8QdeUN/S81dvsbwXQHl/WF/+7dtXr57DYPw4Gvb9eORN4FPcDwYDV6XLL/Qo jWazgt8cX+DWQ8aQLDbpepls0p7Ww78bPTb2JcuYECYQ1XydfL6cbm8W6SfR gsTuZjcu/hn2zjQYd8p32BLT++pWnv7PNl1usmTRtl93bHl9p+N0tVitGVGc O4Qgfnrz+s3bHi2LfWcf6ieDlv3OFAXYSJrhtmjuTnxEnDLoNlFDhV+HJLMB 9oHMXPthk26Vdo79vguVYU0NCbu31QAr36kIuQOWMAonwAh84Aauyg1KJ2Ge AuRscnmT5Pnmar3azq/0BgfF9tOFGkt7kGfXOGJbq+Z8O20gNxxb0Yofx4i/ oc5ISxsYz5uuEkMWqF0WNQChrzH21d+hr3W01b6zdRCBHgPorT9oRpTY1wqy 0Pu3C2kFI89NglEQ9YNRhNvu6aGzgrMTOUBdJbmzuUqd2WqxWN1myzl8Wl8n m6fY7KGzXq9PTk7g73w+hw/wdzwewwf4O3Zokf/mfRMf6Iu/wXmcPH87nvMP Y/rqPbR4s4KTaLrOnXV/3h/TrzA+0hsQ9NcbZzXDL6wjp/NTKAQ/nziHp/Ab ngWyifP7KpvCt8lq+Xu63lxiR8djIvPNxwf5Zr2dbBx2/HcOC9xop2UHJeyb jfyCnJKJLIcrHJcgmwe96mq7gZowEQzGGSuHALLL5faaHFRzEIL7zoe+Iw6x +HPfgZNq8e1MtKIWqzkF8yZlWFBFA3LqnXHoUr/w9EfH6RwXn55oVXs951T7 iZDVEMgqAhY8GnGxkZDW4jMtfJvcIDUB/hcLQm05mTl88OeD7Hxw5mRw4JT6 Az8cHfX+zomelPuA5T5AOQVZzge5IDzX6fXk5rNzQGek/4N26v7Pg+xQG9bR wYdDGWbvv+CQ1TuDUayLnuJDIR4dne23tSP5W9H0/Is0PTy0NI7zN65u/o59 uMP5x6n3YB8ZjUL4FCODPj1Evnfo/PnPzrt0sslWSycAyvoVTyZOfpNOshms WrLyl8BCYafa4LSTSqcSuwNCSshyR0aLXfyT82Gbb2Ch33w+AbaQ5U5+tdou ps4yhZUPfOzmJl2e8G4e4u6dbZzpCpfeLSk4TuG/DTSMXCZPfk8ZGGglJQe0 vqidLKfOzToFkFMEw9jSMv20cditzvHxz7/8319fHh/rNC0RszYNlNgPYPA9 xls0am8wtxmdqoop4jME/5BJimCRxjA/8SCkvJ+BhJ1js10vc4dclhEEOLAZ wIZE/6N8F4s4aTK5YsUSmDHACSAEGCz8V8WMcW/7qjgxvRakrFhitoATeDsG lMCOQ5jVgYcz16Njzp1iimUwJZzTI8zSI/xxlADWR4D6YVjLHynQSgbJbjXb 08yhdzTcI2tDeO4e+RXAa8yA7pRpEyyC4OYb4REfzuX5PPTo5qbyhbab24e2 fMF3J0CXMRCnh6IqFSORS/+EJ513hThZtnB//uX1S0DC7KbHuHa5TF8Cwrhp 0p+iicvZerXcSG1eop6nh6MAEST2UKjFL7gfBcMp/OKZuhfpzr+Zxke96Xy/ +ut6NUnz3FJ9vk7T5eVqNstT6OV4sU2LL4vV6uOPVwCFXsIrVRH4G1LOrkqC LaNQIQz2pW0ySpGT7Wto6xWwo7KG1un03Wq7ngBqDsloi2842uLLBlvcIO8L ApiLcAg05uHe4+H19B+y2TSdOS9ePv/tlaW30IWfYHPZiE7gz9jy9rpPcUw+ kRa315ahYFk8OfDS9DMpjx+xxh9gtWYz+EA1ODKKrxM4Ak2kM79F1GY3WfvS T1lVf9qt9cCivzOPgbZSGekiXzzsG64cnKAQF0s4ggnyBzBBPr0J0IhBu/5Y Jzmsakbb8tjWab5abFHau/yMu9+ATaC8MIqbxIMhVFUaOhKQ5Bo9uQnruQcB SstNNFEGXipcD906O9ZFVaaB5UsTjkkDPH17iG4P0U01RAp3AFDy6OnoXjx/ 5Ry4g77zWB7S+ZNtXylMflAw8WT7t+XjvriEkKurdWHCqvAgwZAbqK7UK6Nt sjs0QJ9cEAr95bfXryvK/ZXeJRQFAdXIfyJC3hHiO95dqUuHL63jPEOVHF15 x9WvnzQksdNDsqSpFE5KOrepk36CA9PGgTpOnk1TJkXIy3oP+nGJLxDduACO eBwNAIWBCygMqNYMb0V1HD1zcEkrxNyThua8QZGXcFcUCECUWa0/I6Db9I8g Vi1XG2eb49VT4mzSa5CJs0V6woVubO/7YhDbPL3EMpdYBgWA0RCvH0LspI+d FGpQaFdQ7qHz76StbAmNjDN6twRHmfEida7SNTT3fuVM0wne75KVksM/6zVg f/G5j1NxRWTBFRmkDDbBASNYlP3I7IG4kya4TW2hlfHv2Wqbw+jxNQiLxxwL Uy4j3mYg/AMKZKBXKxBF0yW5xaW3NNDydEVlURwCHMmgMhyvoVOzJL/CY/YB iJZQBsaWbBDZvRMZ5CtYsgkl7jVr+kS5XYSD+4U0LD5ZCe8nSq44CEInSI0g KE8SmA8Qk5cp3azIWGQws2ydb4icQy8ZCcmSyig8w09LFeaJ88vM+cUh2m8Z DpOtb7IbQHJGp0VvF8mIfINWrqE4YAHLK6OijVL4tBaxHDhBQkJeEeJWGAoa UvkFFxDMLcA3yF+ztzDZnrId28pJDerVJTkfl4dai/LAniRd/12RtMmO8uu7 V5cv3761yOCPmRx/Q6Xdp3iOwNXCVi2SAW2PE8bBBn5e3ZCrnuNjPNSStQm7 j3Iccdh9g3MwUH6/0wYvWLk8LGRFsYuXTLiFRsiPopGyQQpiN0aA35G9PNke Pdky7gqriEwjJYAcR8jfqfumZHWlzHDfsL+RuTldQIg0QrvJ4iOnYXY5Utx8 cT4Hda6TjynHarKguxweQ5FgoH8J4eWUrdM6JiGW7VKSVNtmg+qd6e2ULwNW VtsfCnqUqFChwCYEh/1pRW46qeGBN0aJII6AfEa4ykd0OxNnMHHsENL90bnt AGe3YWNnS4kGbHyPzRwwaoEP0xpL2uCtdl5KCYutFwwUT/YDPH+NcF8cUWOn 6YoRttD72wzMFEMwib6OJXTJBg5/klBm9EappbJFQgiBhQRIZ55M2VolDF3g ENen0m1p4htbiGmyn2EkVnc3wZ/BJ5DNf5DMslDhFqNeOh4EiP1RPxwMVOOs 4ipBsx+Dg4pEjsc20nMoZZGHsH5l9iRC7Gkt6ZQM8vvwTLtzB/TdZpsJao4J Gsv2kEkCu/67H//y8vLd+x/f//bu8tWbNy+eVuopj85l0zV1X1CI+bii4Bh+ +nhW1ZGXb35+am52Ngp7+eZX52C5coDHULmNX73BnDyZEhJTJ3UvoytOO82H 9OLlv/3y08vL57+9+4+SoU3T37MJbhz5Z33LNcBP01myXWwskMr58XaZoJgM O9EcyDK7TuZM0iXrki2k7839fjZZrGAwB/z+rvw1uc1T354ekqtTfoF7i0w0 BVlzdc23yJwI7n9SbovLhQxYjngOHMSTcADSQjjwhfknZxoSR2thsaqsWo2P 1JupmdxDFcqdySKFcy5qWuiwpfHCDglNKqalg75tV1bgwe7toB3LQqjjqEyS 45bKxBJHaqZgCuK2h1nr9Uy2oFvvqZRWoqZnWJUHUr747EtGsTK0Nyqro/ba IhpCqk1KcM+txt+loE8PNeDMpNM+JHwJ4+kyLGX9lLMHGw+F1jaFPMv30e0y 397crNYbdsFNbaYoS7VQUP0R4U4jYHp4IwwIWBIKfzKxNrS3ljhSnTRCiz7l 8iceFLhgQri9+IocckVOD4r0oDQtbwe8+ZIzONnTi6Ox9EaMtkRyJJWqBEdS wCI31mPDKpsVnfzKRLORTTZzvSQcBC5sAcFQgbXDrk4Gross0ASqPFzcaoIA 2glVW7AOMom5nxTIMmzQNaNbhVSOzysqWupZnR1027SvRtZiV5n3L2oF8XCI 2n0fZjr0cKZDc6YLwcqcvE6ilgxNyFIWm8FvXbwDBKMNhR8CliMU3SK37JL3 PVHWM/sWcr+Xo3b+82orLB6Bgb91fk8WW9T6y7++kiHxAnhlKBd6zt7gBVK+ nSAKQWw60XqBV5WbGUhafedqdYvGB0DiOb2U3FwhXtCe4HC52hzSe+b8ZrUk d1SblQwJW+aXlnkCuHmM/XgMv9P70OQmXatt/7LMN4RN4vvHRM3zmHf5OgE5 jjSCdxLkapYPC6hi+tgcv4MWEyB+jtg19Gy7hrprWAirW4Bru/aG7spwSDdQ b1T0AkfuW+GdOAfvAUN/zMmljzcYTG+yMxkY/hwF8KuTYakhwY3rUEtKfOkG g+KtT94OHWZ+qcMJCXjHDUkxNsCTnj6PdmJKKFtCzHHUHMDU0i73CKNTkZAs ab38I4hF5EprRakBf6W3W9liyi4I0fQCZBiyFJVu84tt+WbfIH+iwxgneYaS /mfndrX+mMNmjbJVki359C8SmP3HypWAMv90d6cWuFz0IcY1ZP9AlKGVDYN2 DQTJrjfH6TxbYisKGc+EaQzVcOGW30f6oXoMZwJgN1QF9DhfZGQp3GZLIAul Vys049FIDsrBTgIoxJeL5IaQszowGV+n+z9gAW9CBhUMkEHhNhCLDb8wnIAN ybDWwEeypiCyES9+pOpojzRF3m023VwpnrX4CGMMDZasuT0i2roqcDqGHo6M D0dGqe1v4MiIOmsQ82Mh4SvePKoaGUgSyqNZRoCSXOzjEhYOpswPVSynZ6qG 40i9au3JN+N/N6Sx2hMs7ezBgWw30Wt8riWylvP9ueMq5oP4VEtkTdUy0yz/ iPaQgAeKGOwY2Qe46t4UFcuu5dhM4WkphNOSS/w6DSsxAYNadxkuiTquxEwd 6zK3VlLCZq/GokUVuIV9WW1vZAZ/b/0pbNxquyNtEffWG2qzJxRqKtZsb5hN H3/BrPTktYOUQvS+cYiUAtusq3nwU+ND3GcLqz61EbaQWblnsvXfUbUa1OI1 W0qmEgLgrCosJ3UfWAkdWE4iE7MkRw8WFBOo2DOqzyEb5dFRDxByKJgX/GCC 10tLfWlUXnTJUvzOIA0mlJzXyiEm7exUVSL5RjUrORAhUvbhtAIQKtjCUvIv PrYEIdYJ/9QSgLAnJEe/J/72KZxFCG7oOeaJtz1l/3NLqCfwDf+z30AVdrtH R/06C9y+ac5rAmQj65WQd7ETFquXbISVJow0VIbsc84/z2aLbX5luTkpHLvF Y2zdjHlomzc31VfsWbQgJ3YRC3lcTBTGQ+Rx8MkdilAiFfE6eBExu/ru3eb2 WpkR0xKeh+J4po1XGWCFgNQ3TKXEYUkyxtC03w3sBohY0+GiXg9aUlwmCj3B nYhKIql1L5yB849/KNePF8zfmtQSRKZclVlv0AojmjKbR9plQZkScEWso4ZV zDVfq8KWkGxhRRaRbmgmRMozrT2LFEmHY3uBV3tKY/AyROd9NI2YApHTjVwK BSPTGK0uljv7WTc0+t4w6OXbNgMgSTMMsHxrGg5cD7pCnGHwSwAr0BvCCiS+ JJp7zIttU++YMtcVm8+M4lq+q9NMfdMwuAgV4BGOMCgcLah+xuJV8Q05zggT c7LdvCa8n/7wcjl9XQiq7T1tNMvMqkLCgvH+nHbsdvRNfGru3ffHaERR1xDH m2pHIEK2r2t6jqRsKfPVegwRbiXV5Va6ujlea9tIIsZRqKpeSD5yP2M7gmrd eA++S9kl5Qg0JBwwmRj1rC5yGhpW714djBzDs6i1A1G76iJioRg2JUYYtYej hvG7LBZIlbMPtDQsAXdUGeODM3l+sdKmKq6hPlGTk/2P6KpHI+i1j/ueT30o T5mGAVVL3PIbr+GohklRj1CVElGSEEXegnv2E4VCulgt51TFJSmgbpI5BbXs O8kM2WbiTNI1qiqEUzaHwTQtGofvoc+D0M8wzRLVlXDb20IrdUiNFbBZ5knB PVVJ7BPqS0HVfrQ7yu6hdgRVV9yNIKV+3VrjRVsnvCb/F3VLVIckXM9pZQ6P fCsIDgnEAPLXRYo3v8kiXwlj48nq+hqkCKKhLPHqBUFrcsWBpJ9uFgnT5BHi d9LlZIUamBPs5WeisPs9WWRT2fiflOQgsIM5Bg+4TVHlSRQyCC79NEmppTbR dRHlJwz7duVM8NJwkiw4BBL9JSc1M67bnOMNI2L4MZ1DRPBj3JOWc6J/5arS Q1bglGBbms7HZBpLXzJIHAgCdB6TYrQlgpBkMdkuEjIGpsViC3acbm5h/eIO 0ucgyIomjSJPQY0vdTbarLPJx898+njpnxHVnxKckr5DtYcOqiSxEQqJaExV tS00R38uVuUfr4VijqrNSLSVtNBMUhelA8YCeme4F2GtbMlhIODrbDpdMD8D Nsc4rX2qTJ2v2MoFwnRDvhCZB5AERloPvHlj4a9RH45+Q8IPaFvMAnrxjFMs PcGdPYXjMfGkymbF8GkgChwBH3KGrcwKpSvVm7PpwrUAs4fSDKM5Z4whLJJ1 hrhhyvUCxwTxBVWSlgj0z6slUarDF7Zgr5PPOMxk+XlDajK6XSNROaNjNyyW 63tg/NAPyhQ32XVKr/3nW3RI25A9HYf4i3O1uiG/UJ3tcnXLQZzSnVvle6Zr IjtHtNhF4WzunknAGZ+zeT3qEgByJKju61uu4RHZvldnXNoShjeMIskVN725 2vYdzu7JF8q75tAD/aaq+kTQV7ov3QIxAUoVaTB4Aip48foZD1B+gFtlxLbK nT0duYhYdujXxUTtOGL3grUVVg8LXCaUIkOWtlHmjCa7v0jiZ7ljmqwdM64m C8c041pwv45p6rWuLikLzAhElDmm2WXrw3Mh0LHoOLKgLM7+efNIG4UnPxG0 qXnEZTalYXGAHlHWdPHmEKVuN2BS59fq8izfOVjOEdKZEUbl40XMAIYWoGga +LYboHJXZJ2y9+caLIPRvITbuAbLYCq9hCtdg2Uozb2EHcU3WIbB3YTFT6fF 5y6esTKLsLkK3iOHePfTu1+YYTW79UQmkWP/oQPE4qotf7j7glE8cC2wS0lc CyGuhUjslNabf+H9KlxfWzi92ld5WXyHnaJjwHD8BEaCXCsckOL/pHgI0BPE qYeH4BDxHFIzkPv0En3wFP66PIXxvoZcfwANRC58iuhFyFfkOyv7FpMV8mW8 igtpFzGDn6JIQUVHv9Zqf1YJZQ08W//V3Iwlcc9waeHynjuFGRGexl+XVyMK bcDjR8hUR15XDw+7rzBuhmQLAfocIR+PXVN8eHC8+VdwcoZZRguw0Iepjv1y IXHfTjf36FsDo0HLtlg1ajONNk2D0uauNMAgYG8beu4kHA7w0+DBlebBlebB lYb+apD/gytNjSvNM0EL36Sji9R/i5V/lZG/dkfx6MFu/cFuXbcV4c+DYbp4 HgzTdez9rzZMtzh67MUlE2RcOB8MRwEKuvhJS2WIdw0Hwjruma4j7Dn/+IdB XQdylWOzyhOYwnP0vDIPHT/84FiaYxrIXq8+W9wp0S/cJjRHDjA7PNJZTGWA A1JbDab7pyYXKGxJl/cyFkp7BSPUdbuWgVm6is8uRvqV1wqSjXQNi8PHDAqp P4X7A9HFk3Nr8Us3fwj+FIjtaxaNpX4S5bCqHCgUfwn9uTN+syQBxMc+jW3w eEDtbChpTnv4cu+IbOpeUg7MjraSzcrE3w4JFevV+tX1OQySH6J0YHtfcASo 5E/aRgypHgyBbFxrlJWs0fnJT1eX1TLgdv2f/JjLrPPSK/MiEvNbiYwGJsn6 o5o5HNXlHLOPuJI1V7MThSUTO7x9smSJiyi24y25cWNObGUpd/rRQHKeewi7 8BB24VsPuwASd9QPPTRCGg6HKHZ7CrlrYvfFuWHTeGzY8Jubi12YFoJ4vTSt ndnaMTr1uqpdbVN+MHCykxRuYuVcO2OUVzrQGyygSEeadjg97oTTlrXvWpPY fZOXeq5vhwnlAvP+iat+tdlw8sWJS77964LR1qSl7cn7DT4KnNJHThkgp5T1 fneN3J3vMzApdC3Ergl7AosTM+9kqVc0BTSCLWE4AmieuIT5Wp3ZYY6JOvWp k2fXK0wSkQFstksyzchssbolKtXv5UuVL+MG/4zRB/77Jf2l+VRbqCD0PBdm OPCnMMM0q4LkNMZt3w27977QPmES6mSBw0aXinRJltkmXRaONVxxSxbcr7+9 e+/85c179L4gx8gpzNVykjI97joF2mOk4uSbbFE4GS3TdEpIgyjeiAow25yY XcS0MXB03sDYiz5yGKSWYteecX0dyU6DPV2n1C+L1JVN0g0Hrn/HDDhWzKDy fTvmwyAq022+JWpIOJ1dZ5hakUOhvi+SKhrXANcUsg5Qhze+Tm6ldjkUOmpr ywu0IAaWnS3QcBhni1BBOpVaKDpjwcqJ845MEH7Oi3EQhzliz5yM8aQ+cv7P cw4FT+2A9T7Lm2TvS+Hed4z3m6RbKZx/0sLVL1lcrwAdaDRAnXRUf5o2Dhdm lAV5JVr9J3aKslBULr0gsUZTEJ2B5RiEuBI99iXGLwH9EqLhB/HEZSwVT1ot MnYqUQvm6+Rzm8qhF8GRwItwy/NhTxgGliyd6p5k9UdHCiPpfW3v0Ecd/l+X +icrFkzMmpL8g45ZlxvqYnSJX4h/EflEjzgHmN64Rx24Dn4Q5dgJCM1rvFEM g5MSSHXNgaUY+9TDSqpghT4atvr+cIp7srzj3bA7H7Jo0eq3sCrlhRjO7R4k CNkHyEE0gY1+IN9xsDTGygbvZCgawD/H515PFvXGcu7mZ8537DNejYhC8yaF 1lWFpHJ8idJ16fZVNYNeat6o1LiiFFmg8pzySoadqKubisobrh/EiOmhKioF fVNqdOHH0I8GUNzz9OLdY7vb2usONfTjEMgpHgGhBvsl1ACt3oJhAPgI4ZNH 7PuLytUxIlXKaUPYBmk7zndFV1XKNQm8tKBO5FpB7VRcFlBSJn0leKR6Eqq7 sN9v8EgVdtn9u37wLxvi/F9/iONveYgyF6mPfIWPGpeNXHLY8dKIr9KwSLop /vfquVQvoEdXrY+vWpt6EZ/9hl0tD7xKbmuDYQTcED1dPPR0AdFM5huC9lgs vG+W+5Xo0pAcdGN9uYTeZAmY+X7AjBuA0QMUli6JkjYq3VE0CjHUgeotDdBN iMQTwSYdhQrRwLsgSkAYRl1A7MtCtipDc/lacgjjP+HFoCRis57xt4gLJr1T sQOYFQ+sIA73bLRPnSeLrZOnk9VySvwcpVaO5UaEIH+BY8CDiu+61sNSo1Bt paelRrXDYARrMhgNsRdwXPJd6otYEuEHO1cXIGiX6kqQoJoARfMUamWTy5sk zzdXa+KkvEOwolowauCiYBQmoT/EE8gwAriU1A6dP//ZeYfez6ulE8BE/4oq OKFJJWS9hBng7pWkEpt6jILkD2N16vfhqS+ThBGWpwHgHnQuHkxDn8UpDGI4 UgcxcHAf/YJ9FmWrwoHYeF0Zwq8sjbvwZK3zaq4JCWhUbx4SUKkqu0na/I21 CH+1LslBHCBiI0RsDIiNrIi917sKMzifpdctg/M1uBBRLDhMB2815h4P5FAR c88AURtz74IbTzAWv0vMPeIOu6dId6wbewxdh+DU0HVsgzswIthJBuByjV5t bDoEqIS2402UgZcKN4FOp6Yipt2ZtD+jFkdu9xwj9siFyQ9Kd5kxTyGSyNXV ujU2/hIMuYHqSiIWb00AFat3PWuxNIBK5eu6ACpSjOBG0U8uNPkQHf2kO8UO 0U/0kCcy2BbRT6pDnshAq6KftAh5IoOUg58UahrxXih3u0Q8uWCyMewoMewo Ee4oI5fJY3uLXsF3kcLMrhhGRVCQIzkuCBlNWXSQApoUHUQZaN8IKgAbaTgA KTYcoIQy8nDYNOLwjjGHdg5OIYJ6qZE81H3CjORBNANVkTxgbAGOLcIbS6rf tsZ14R2YrowFuXsYCXFeaxNGAroc4ZwgKaL86Mc8wkVFbIua8BHSubU+kIR8 jO0QOEJiaOTZU0L0MHSRZF0kWZQC/ViEuWh2c2671OYQ9hY6wmpyY3mqQkco ud95vAhBVPuKF1Eb5cISLyIcArcIhyCAB4NIGazGMe3GI/gwk03xU3XcAblq WdwB5XbGiPCku+aXh3AIQw/O9YE7VCBaEgLoINWY9SGGKwo9RJKLtzGeCIXQ VVuiGT7JW2bH0AASpNahAZRedAoNIEFqGBpAqtEpNIAx/h1DA0hwuocGkJXM XUIDaHDKQgNo87h7aAAFCbuHBpC7LUIDiF8N8u8QGkAC1T00gEzGnUIDyIB2 DQ0gi83AlkC+CDzCloQS1xJVpjy4TWlMAV5gLzEFOLA9xRQIQx/Fh2A4hYGL LIIPlhCaJQSgyEc84eaFGAt8sRnqYZ4qDEQDzcRzD0ayFSajmpWsTKzt00TK yhtAxCgBHABKgiCyXcMVMyrCSahyVVU4CU0C6xIwQQalhJOo7o0aTuKe+iOH k6jujhJO4p56I4eTMLFme6OEkyiuQcMQQ5oFGB8zGFEJr8riWhcZreEn5AId wk+YOvFSupUwooWf0EuVh5/QS5aFn5BukNWnOvxEXWk9/ERdeS38hK5/12ml cSQIk5h2qtou/EQNS2oZfqJkPbQJP2FfOC3CT8gAOudFNM64kmvnTnkRDYDC u9RK3rvnRRRQBE0qeRGBAQ1hqw69CSpbUS9GFf4WZwDyc/UxtsL1gxfZj+uH gsFy1w9erLsDh5Bbyx04+FUw/mtx4MCfLQ4clgt/qwMHhW5z4LhwjMuDMErw ehYVCvAFdpcQDUXDgUh419rGu+5SqlVevD2m24OhgTweDoiBE3xByTMa4WDx AsX1q7XmSjLI9ip0o7zuAGBVD5tZBqqyzX37ivomuft20+ybuftKCym5+2qN BMIohhXkEhKKy0ajKIdsAd4tKvV7twMIw5ELXUcf7RDOXXVaf1tKPqOQJSXf V20eUJaST1fPdE/JJ/YF3RjzTlNAff2GCu1z7CGMDjn2Glga0Ox5ZBtDHWOI Yb9Cn/B4qtmq9O3BAhW+Pfj68FRIMDsnwmO1OyXCYzDYZeiOifB4R7okwlM6 0ioRHqvJ/90tEZ4GpFsiPAakSyI8BgI7uGMiPAZhx0R4rHa3RHgMSJdEeAxE XSI8WoyX7pgIj6/KLonwGIyuifAEmN0T4TEYHRPhMShdE+FxquyYCI+v9Q6J 8CgIlufCSIRHd9NiI9k1EZ4ALhLhaaDNfbc8EV7nXhFBDW010CA5xJwbIbO1 36PZkASOLPpzzWJYMSvaNRlfcRZvmYwPzqWjPpxLfRj/SLgZnCrBuouEewm/ H0AGrXjCOmyJOnmyTKnKnqxPGUwn71oJjhwPYJpRWzm9XVzewlOB7ApYXhkV W5L0XodyE9To2RNyNc/WJ821fjOzU8a/MHKHcJaIA02WpSnw4K2HbyMqxVUb U0JhOExFLlB7NODBQna2+WIKrkpzrJ2tMMNoOMBeDpnplPCNaGqXCRDg+BUN YwTj47CFAuw+ra8kvd/+MuP808ybBp9M4yFphEVIPNKvXpVZS5c0gBKYLmkA JTAd0gBKUHZOAygbKdyrUWxFGkA4vbmwLDDfVOSSBRJUGXO9evPmhWrFVW8A 9vLNzyWGX/qK+CpzBH29pnCVjRfBC4127itvT42VXcnrkow7NW68+0xDCdQf J7ghFvdFIAXiogjCCe5AuH+IFD61xjWFMcouYSd2MM5wvwrrjL3kxrxQmqzJ jQnzE8PUoMIsQsfEaFgmulIi4BKlXbKzywKkUjNRgBStsMPev1F8FAY4fuTc Q5TfvcAgjO5xQv6JMsfIFDq+IgP/C0dpuqN5fU1eRtHFBgb2SBkjYGhehEQR F5W/MuPzKML+jVwgX39k23HZQfkr2nBb2J5HMe4g8RBGF+DiHA3b7yBVcToe TMcfTMcfTMf5rwb5P5iO15iOS9vXN2kBLvW/bVY5YMsoLsYB8OYRfBoN1BS2 +wl1pMs5RqgjysFtZgH8ebBC/t9mhXyhZqu+T6tiWAAR0v5gAn88+OQODJqt zyDTIHPMvjPGyAYedA09mEOXmkPD3A5xlkOYZRc+xQqvU6OPSS/U0GI7Broq jbJV7ZDEJ+3BUvtLW2rbmVCjNH46WTZP42ccHWvT+Kk1zBiBe0njpwNtn8bP PBObXcVnp6xiVQdu6TqxhjfiYway0J+9pfErbaFAbPM0fqWwGiaPMuvfGb9p 0f/4Y5/GNnjsmsavCSIbp/ErBWZHW8kuZ+JP/W7BpYnHZoFJy+tzGDSNX9nA 9r7gCNDGafzskOyDIZBrQ57yp0HoU/7sOwQqf8pDofLHXGadl16DNH5VyGhg xqw/LdP42UdcyZqr2cne0vhZoUtcpGEaPyuYxpzYylLudDlE8vU609/tlvNM 73V9Uqo6BtYq55m1cuO0VHXMdpecZ9ZprEtLVVqpYVqqNjitTS1VidOWte9a k9h9k1ebnGe2ul+QuOpXmw0nX5y42uQ8q8LoDqSFZ/MY7138CRzLfV31T7h6 t7AMCGLfen9LYp4SL3k4FipjMR3nbXmuRpgSLUaPwdgtdYD9Fjxd2yc54zX/ tX1kwxFa1IyGOM34KfZci3eQFLX8mVMdtZySohy1nJkm7jdqOXNRknPLdM68 xqB0zLzGoHTKvMZgdMy8xqDwfztmXmNQOmZeY1C6Zl7jnbFgpUXmNQalY+Y1 TjZm5jX65hQWmYeKLS+ARSbHRyIDs+U7I5RWYo5nHkDDEWa5GgXuNIx99P5j ObfRwiSbKK6mdjf3RsH5ay2Faj3Sn7GLbM3pXATEL3iFEiWfGVeaL3aLwt8F jBqFfxR4iHEqK7CjtjocKBLizERYLqSDeBT5wyiJAjfqR8HQY/NKbGVITu2f 3rx+Q5KEFzOu3BXDh8tpekOMcIf+mVkIqPtmu7GW4R5t6QsY5u/p9N+o9QMf osVtVzc2loo8gkPizDlek0MprIlTRjInV8D7bsW3R64XJK4X0s1quRGJt890 CsIM8KslkC36A4os45Qlz7bLSV4kFz/EdeV6Ud/1RhP4H/6lC+v0sHDPG5N6 c4IaeiA/8ImhA2aZdxy+g5A6H5er2yVNPZ/3KslcdoytfNr2pBHEVv10/cHE 9V0+RsKIyVwjL2a8utsAm4P0XS/x3aDvk7ABf5imM0SDmqfeca2v3r599er5 c2dofclS0Due9e3zV28dzMbyKPAGSQDkEhDXf8YZUcYpKArzXfBU9WVBN7QI BDzMXAOLO3zUEAjcKJ4sdFuH1uv5fDz+Z/Up8AFZQTTBGFxBOLBvJ7umiWlq dao8fDuZip1lOiQMvVnP9hHMZa/9ap5dZWrmVWk+7ocZ+SZnpDBIqoDZBh4s 5EkQDvc6ObSP9R1sAisIXeifD8wmuPeJqu13K/gA6jt8zHb+P8AXAumkBQEA --1386611826-1974716381-1056990003=:8012-- From henning@meier-geinitz.de Mon Jun 30 17:34:25 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 30 Jun 2003 18:34:25 +0200 Subject: [sane-devel] Re: Visioneer 5800 In-Reply-To: <20030629.215242.2373.604481@webmail01.lax.untd.com> References: <20030629.215242.2373.604481@webmail01.lax.untd.com> Message-ID: <20030630163425.GA634@meier-geinitz.de> Hi, On Mon, Jun 30, 2003 at 04:51:42AM +0000, jollyprince@juno.com wrote: > On Sun, 2003-06-29 at 20:38, jollyprince@juno.com wrote: > > T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 > > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > > P: Vendor=04a7 ProdID=0226 Rev= 1.00 > > S: Manufacturer=Visioneer > > S: Product=USB Scanner > > S: SerialNumber=RTS8801C2-004 > > C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA > > I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) > > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > > E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms > > E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms > > > > RESULT: of cat /proc/bus/usb/devices | more > > > > Realtek chip, see www.realtec.com.tw at page scanner ic > some info is given about the chip. Also looks like Visioneer 4800, 5300 and 8920. Bye, Henning From henning@meier-geinitz.de Mon Jun 30 17:39:52 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 30 Jun 2003 18:39:52 +0200 Subject: [sane-devel] Fw: RTS8801C2 Serial Number Chipset In-Reply-To: <20030629.215444.2373.604497@webmail01.lax.untd.com> References: <20030629.215444.2373.604497@webmail01.lax.untd.com> Message-ID: <20030630163952.GB634@meier-geinitz.de> Hi, On Mon, Jun 30, 2003 at 04:54:00AM +0000, jollyprince@juno.com wrote: > I'm researching technical data to write a driver for a Visioneer 5800 > Scanner. The above serial number was referenced when checking out > the Visioneer 5800 specs. > > Am I on the right track and can you provide me with some help on this project? Looks like a realtek chipset. The other Visioneer scanners seem to use the B version. Here is some info: http://www.realtek.com.tw/products/products1-1.aspx?lineid=10 The links are dead for me but maybe you can ask realtek for details. I'll update our lists. Bye, Henning From henning@meier-geinitz.de Mon Jun 30 17:52:19 2003 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 30 Jun 2003 18:52:19 +0200 Subject: [sane-devel] Genius Vivid-3xe part II In-Reply-To: References: Message-ID: <20030630165219.GC634@meier-geinitz.de> Hi, On Mon, Jun 30, 2003 at 10:00:46AM +0000, Renito 73 wrote: > Finally I did it, just forgot the firmware file and now is fixed, but I > have a doubt... xsane has 8/12 bit depth, does it mean the bpp? Bits per pixel per color. > this model supports up to 24 or 36 (don't remember) Bits per color. In color mode: 12 * 3 = 36. Voila. Bye, Henning From jollyprince@juno.com Mon Jun 30 19:48:13 2003 From: jollyprince@juno.com (jollyprince@juno.com) Date: Mon, 30 Jun 2003 18:48:13 GMT Subject: [sane-devel] Fw: RTS8801C2 Serial Number Chipset Message-ID: <20030630.114820.754.154095@webmail06.lax.untd.com> --- Henning Meier-Geinitz wrote: Hi, On Mon, Jun 30, 2003 at 04:54:00AM +0000, jollyprince@juno.com wrote: > I'm researching technical data to write a driver for a Visioneer 5800 > Scanner. The above serial number was referenced when checking out > the Visioneer 5800 specs. > > Am I on the right track and can you provide me with some help on this project? Looks like a realtek chipset. The other Visioneer scanners seem to use the B version. Here is some info: http://www.realtek.com.tw/products/products1-1.aspx?lineid=10 I found it at: http://www.realtek.com.tw/products/products1-2.aspx?modelid=37 The links are dead for me but maybe you can ask realtek for details. I'll update our lists. Bye, Henning _______________________________________________ Sane-devel mailing list Sane-devel@www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel From karsten.festag@gmx.de Mon Jun 30 21:08:30 2003 From: karsten.festag@gmx.de (Karsten Festag) Date: Mon, 30 Jun 2003 22:08:30 +0200 Subject: [sane-devel] negative-scan In-Reply-To: <1056815865.14723.11.camel@christoph.local> References: <1056815865.14723.11.camel@christoph.local> Message-ID: <200306302208.30947.karsten.festag@gmx.de> Hi, that sounds like a problem with my backend :-( I'll have to check the code for the lamp control, but I'm afraid I can't do this before August. Regarding the negativ-preview: I think this might be a frontend feature for xsane and the other frontends (..requesting comments..) Karsten On Saturday 28 June 2003 17:57, Christoph Knauer wrote: > Hi, > > i've a litle problem with scanning negatives on an microtek scanmaker x6 > / phantom 636 with lightlid35 when i set the option using lightlit or > toggle lamp. with "toggle the lamp" the scannerlam goes out, but when i > push the button scan, it goes on again, and setting "use lightlid35" > seems to do nothing. > > btw. why there is no "negativ"-format to set for preview? > > greetings, christoph > > _______________________________________________ > Sane-devel mailing list > Sane-devel@www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From Oliver.Schwartz@gmx.de Mon Jun 30 22:24:47 2003 From: Oliver.Schwartz@gmx.de (Oliver Schwartz) Date: Mon, 30 Jun 2003 23:24:47 +0200 Subject: [sane-devel] Re: Sane-devel digest, Vol 1 #503 - 1 msg In-Reply-To: <1056821890.4190.34.camel@daisy.localdomain> References: <20030628132618.13633.99099.Mailman@panda.mostang.com> <1056821890.4190.34.camel@daisy.localdomain> Message-ID: <200306302324.48935.Oliver.Schwartz@gmx.de> =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > According to the Sourceforge page > (http://snapscan.sourceforge.net/), the Acer/Benq 3300 uses either > the "u222v067.bin" or "u176v046.bin" firmware files. Looking at the > CD that came with the scanner I find the first one (u222v067.bin), > but not the second one: The firmware file for the Acer 3300 depends on the USB ID. For 0x04a5,=20 0x20b0 it's u176v...bin. The last three digits are the version=20 number, the latest version I know of is u176v046.bin. However, using=20 u176v042.bin should work as well. Using u222v67 will not work for=20 your model. =2D -Oliver =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/AKqf/V6sbrmfIuMRArE2AJ9GBx4HZAKowpIb1/OUIgDBZ98O/QCggRU0 urfv/DMt64GSYA2MpWxmMl8=3D =3D8qz/ =2D----END PGP SIGNATURE----- From rsv869@adelphia.net Fri Jun 6 04:53:02 2003 From: rsv869@adelphia.net (Reid Vail) Date: Thu, 05 Jun 2003 23:53:02 -0400 Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <3E02B406.7010801@kirchgessner.net> References: <3E02AB22.2010409@adelphia.net> <3E02B406.7010801@kirchgessner.net> Message-ID: <3EE0101E.6010604@adelphia.net> About six months ago Peter gave me some advice about my HP6350c scanner. It fixed my issue and got it working. (I included that exchange at the bottom of this message). Recently I upgraded my Suse box to Suse 8.2 and it's not working again. I dug out the mail and checked the config. Looks OK to me, and I included a few scraps. I've included the output from sane-find-scanner. The permissions also look OK, too, I think. Any suggestions would be great. thx Reid reid@linux:~>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=0x03f0, product=0x0601) at libusb:001:002 # A USB device was detected. This program can't be sure if it's really # a scanner. If it is your scanner, 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. reid@linux:/etc/sane.d> ls -l hp.conf -rwxrwxrwx 1 root root 480 2003-06-05 21:14 hp.conf reid@linux:~> ls -l /etc/sane.d/dll.conf -rw-rw-rw- 1 root root 448 2002-12-18 00:16 /etc/sane.d/dll.conf dll.conf . . # dc210 # dc240 # dc25 # dll # dmc # epson hp # fujitsu # leo # microtek # microtek2 # mustek_usb # mustek # matsushita . . reid@linux:/etc/sane.d> more hp.conf #scsi HP # Uncomment the following if you have "Error during device I/O" on SCSI # option dumb-read # # The usual place for a SCSI-scanner on Linux # # USB-scanners supported by the hp-backend # HP ScanJet 4100C usb 0x03f0 0x0101 # HP ScanJet 5200C usb 0x03f0 0x0401 # HP ScanJet 62X0C usb 0x03f0 0x0201 # HP ScanJet 63X0C usb 0x03f0 0x0601 # # Uncomment the following if your scanner is connected by USB, # but you are not using libusb /dev/usb/scanner option connect-device reid@linux:/etc/sane.d> Peter Kirchgessner wrote: > Hi, > > pleae have a look at /etc/sane.d/hp.conf or > /usr/local/etc/sane.d/hp.conf. It must have two lines in it: > > /dev/usbscanner > option connect-device > > In dll.conf (same directories) the line with "hp" must be active. > You may need to set the permissions: > > chmod 666 /dev/usbscanner > > More hints can be found at http://www.kirchgessner.net/sanehpfaq.html > > Sincerely > > Peter > > Reid Vail schrieb: > >> I've been trying for a least a month to get an HP6350c USB Scanjet to >> work. I'm running a SuSE 8.1 Personal distro, which comes with a SANE >> implementation of 1.0.8-47. >> >> I think (but can't say for sure) that some part of the install of the >> unit (via YAST) isn't working because it doesn't even "test" >> correctly. However YAST does correctly identify it. >> >> When I run xscanimage I get this output: >> >> [xscanimage] No scanners were identified. If you were expecting >> something different, check that the scanner is plugged in, turned on and >> detected by sane-find-scanner (if appropriate). Please read the >> documentation which came with this software (README, FAQ, manpages). >> >> But when I run sane-find-scanner I get this output: >> >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = >> 0x0601) at device /dev/usb/scanner0 >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = >> 0x0601) at device /dev/usbscanner >> >> I make no claims that I'm not missing something obvious! I just >> don't get it. For what it's worth, I know the unit works because it >> runs under Windoze 2K. >> >> Thanks in advance. >> >> Reid Vail >> >> _______________________________________________ >> Sane-devel mailing list >> Sane-devel@www.mostang.com >> http://www.mostang.com/mailman/listinfo/sane-devel >> > > From christoph.bier at web.de Sun Jun 1 13:32:10 2003 From: christoph.bier at web.de (Christoph Bier) Date: Sun, 01 Jun 2003 14:32:10 +0200 Subject: [sane-devel] suddenly problems opening /dev/usbscanner0 In-Reply-To: <20030531143811.GC6785@meier-geinitz.de> References: <3ED6537D.3020004@web.de> <20030529184903.GC19114@hmg1> <3ED6630C.8070409@web.de> <20030530142302.GA3433@hmg1> <3ED79A4B.6000209@web.de> <20030530181542.GB689@hmg1> <3ED7AAE5.7090400@web.de> <20030530192852.GA749@hmg1> <3ED7C4A0.4070703@web.de> <20030531143811.GC6785@meier-geinitz.de> Message-ID: <3ED9F24A.8040007@web.de> Hi! Henning Meier-Geinitz schrieb: > Hi, [. . .] > You could try to use the older debian package to make sure that it > wasn't cause by an update from 1.0.10-1 to 1.0.10-2 or something like > that. I don't know where to get 1.0.10-1. > Otherwise I don't have new ideas. Me neither. I installed the scanner to my girlfriends pc, on which a Debian system is also running. No success. Tomorrow I will connect the scanner to my pc at work. Actually, I hope, that it won't work there, because I would have found the cause :-). If it works there, I don't know what else to do . . . Thanks for your help! Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier at wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From christoph.bier at web.de Mon Jun 2 10:15:26 2003 From: christoph.bier at web.de (Christoph Bier) Date: Mon, 2 Jun 2003 11:15:26 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) Message-ID: <20030602111526.5b4034a3.christoph.bier@web.de> Hi! As written in my last posting in the thread "suddenly problems [. . .]" I installed my scanner at the pc at work. Didn't help. BUT: after plugging in again the other, former at this pc installed (working!) scanner, I get the same error message starting xsane for this scanner, that worked 2 minutes before! I'm totally confused now. Only unplugging (and plugging in again) makes the scanner stop working. Even after rebooting the system, there's an error opening /dev/usbscanner0. USB-devices are hot-pluggable, aren't they?! Could I have destroyed the scanners by unplugging them while the pc was running?? Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier at wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From henning at meier-geinitz.de Mon Jun 2 14:58:33 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 2 Jun 2003 15:58:33 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030602111526.5b4034a3.christoph.bier@web.de> References: <20030602111526.5b4034a3.christoph.bier@web.de> Message-ID: <20030602135832.GA30314@meier-geinitz.de> Hi, On Mon, Jun 02, 2003 at 11:15:26AM +0200, Christoph Bier wrote: > As written in my last posting in the thread "suddenly > problems [. . .]" I installed my scanner at the pc at > work. Didn't help. BUT: after plugging in again the > other, former at this pc installed (working!) scanner, > I get the same error message starting xsane for this > scanner, that worked 2 minutes before! Maybe plugging in your (home) scanner confused the kernel. Do you get any messages from the USB system in /var/log/messages when you plug-in the scanner? > I'm totally confused now. Only unplugging (and > plugging in again) makes the scanner stop working. > Even after rebooting the system, there's an error > opening /dev/usbscanner0. Or your distribution found the scanner and used some hotplugging magic but failed. And that stops your scanner from beeing detected again. But that's not easy to diagnose from remote. > USB-devices are hot-pluggable, aren't they?! Yes. > Could I have destroyed the scanners by unplugging them while the > pc was running?? No. I don'tt day it's not edefective but if it is, it's not because you unplugged it. I'm doing that all the day with my USb scanners and that's the whole idea of USB. bye, Henning From ozymandias at charter.net Mon Jun 2 16:18:39 2003 From: ozymandias at charter.net (Howard Shane) Date: Mon, 02 Jun 2003 10:18:39 -0500 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org Message-ID: <3EDB6ACF.3010304@charter.net> I would like to announce the completion of the initial draft of the Scanner-HOWTO for the linux documentation project, and invite participants on the SANE-devel mailing list to comment on it. The goal of this document is to bridge point A (scanner) to point B (scanner running successfully in linux) for the relative newbie as efficiently as possible. As such it should not be too technical, it should cover the most common hardware interface types, the required steps to reach a working result, likely pitfalls and how to recover from them, and places to go for help. It is not designed to be an exaustive list of harware in/compatibilities. Any help you can suggest to clarify or otherwise improve the draft will be greatly appreciated and may even result in you being mentioned in the credits if you so desire. The document can be found at: http://ibiblio.org/gferg/ldp/Scanner-HOWTO.html From christoph.bier at web.de Mon Jun 2 16:42:12 2003 From: christoph.bier at web.de (Christoph Bier) Date: Mon, 2 Jun 2003 17:42:12 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030602135832.GA30314@meier-geinitz.de> References: <20030602111526.5b4034a3.christoph.bier@web.de> <20030602135832.GA30314@meier-geinitz.de> Message-ID: <20030602174212.0ce77aa9.christoph.bier@web.de> Hi! Am Mon, 2 Jun 2003 15:58:33 +0200 schrieb Henning Meier-Geinitz :: > Maybe plugging in your (home) scanner confused the kernel. Do you > get any messages from the USB system in /var/log/messages when you > plug-in the scanner? These are the messages I get, when I plug-out the (work) scanner and plug-in it again. Jun 2 17:33:38 nb-pc057 kernel: usb.c: USB disconnect on device 00:11.2-1 address 2 Jun 2 17:33:53 nb-pc057 kernel: hub.c: new USB device 00:11.2-1, assigned address 3 Jun 2 17:33:58 nb-pc057 kernel: usb_control/bulk_msg: timeout Jun 2 17:33:58 nb-pc057 kernel: hub.c: new USB device 00:11.2-1, assigned address 4 Jun 2 17:34:03 nb-pc057 kernel: usb_control/bulk_msg: timeout > > I'm totally confused now. Only unplugging (and > > plugging in again) makes the scanner stop working. > > Even after rebooting the system, there's an error > > opening /dev/usbscanner0. > > Or your distribution found the scanner and used some hotplugging > magic but failed. And that stops your scanner from beeing detected Is there a possibility to turn such "hotplugging magic" off? > again. But that's not easy to diagnose from remote. Hm. Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier at wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From peter at pscomp.com Mon Jun 2 17:44:17 2003 From: peter at pscomp.com (Peter Santoro) Date: Mon, 02 Jun 2003 12:44:17 -0400 Subject: [sane-devel] epson: scanimage threshold option not working in 1.0.12 backend Message-ID: <3EDB7EE1.3040403@pscomp.com> The scanimage threshold option worked in the 1.0.9 backend with my Epson 1660 Photo Perfection scanner. After uninstalling the 1.0.9 backend and installing the 1.0.12 backend, scanimage complains "attempted to set inactive option threshold" and fails. I took a quick look at the epson code (which I am not familiar with yet), but have not found anything yet. Was this change intentional? Thank you for your help, Peter From christoph.bier at web.de Mon Jun 2 19:58:20 2003 From: christoph.bier at web.de (Christoph Bier) Date: Mon, 02 Jun 2003 20:58:20 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030602135832.GA30314@meier-geinitz.de> References: <20030602111526.5b4034a3.christoph.bier@web.de> <20030602135832.GA30314@meier-geinitz.de> Message-ID: <3EDB9E4C.8090802@web.de> Hi! Henning Meier-Geinitz schrieb: > Hi, [. . .] > Maybe plugging in your (home) scanner confused the kernel. Do you get > any messages from the USB system in /var/log/messages when you plug-in > the scanner? With my scanner at home I get the following messages: - modules scanner, uhci: Jun 2 20:26:56 lotus kernel: usb.c: registered new driver usbscanner Jun 2 20:26:56 lotus kernel: scanner.c: 0.4.10:USB Scanner Driver Jun 2 20:27:03 lotus kernel: uhci.c: USB Universal Host Controller Interface driver v1.1 Jun 2 20:27:03 lotus kernel: PCI: Found IRQ 9 for device 00:07.3 Jun 2 20:27:03 lotus kernel: PCI: Sharing IRQ 9 with 00:07.2 Jun 2 20:27:03 lotus kernel: PCI: Sharing IRQ 9 with 00:0f.0 Jun 2 20:27:03 lotus kernel: uhci.c: USB UHCI at I/O 0xb800, IRQ 9 Jun 2 20:27:04 lotus kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 2 20:27:04 lotus kernel: hub.c: USB hub found Jun 2 20:27:04 lotus kernel: hub.c: 2 ports detected Jun 2 20:27:04 lotus kernel: PCI: Found IRQ 9 for device 00:07.2 Jun 2 20:27:04 lotus kernel: PCI: Sharing IRQ 9 with 00:07.3 Jun 2 20:27:04 lotus kernel: PCI: Sharing IRQ 9 with 00:0f.0 Jun 2 20:27:04 lotus kernel: uhci.c: USB UHCI at I/O 0xb400, IRQ 9 Jun 2 20:27:04 lotus kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 2 20:27:04 lotus kernel: hub.c: USB hub found Jun 2 20:27:04 lotus kernel: hub.c: 2 ports detected Jun 2 20:27:04 lotus kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 2 20:27:04 lotus kernel: scanner.c: USB scanner device (0x055f/0x021d) now attached to scanner0 - starting xsane : Jun 2 20:28:10 lotus kernel: Jun 2 20:28:11 lotus kernel: usb_control/bulk_msg: timeout Jun 2 20:28:11 lotus kernel: - libusb, modules uhci: Jun 2 20:29:12 lotus kernel: uhci.c: USB Universal Host Controller Interface driver v1.1 Jun 2 20:29:12 lotus kernel: PCI: Found IRQ 9 for device 00:07.3 Jun 2 20:29:12 lotus kernel: PCI: Sharing IRQ 9 with 00:07.2 Jun 2 20:29:12 lotus kernel: PCI: Sharing IRQ 9 with 00:0f.0 Jun 2 20:29:12 lotus kernel: uhci.c: USB UHCI at I/O 0xb800, IRQ 9 Jun 2 20:29:12 lotus kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 2 20:29:12 lotus kernel: hub.c: USB hub found Jun 2 20:29:12 lotus kernel: hub.c: 2 ports detected Jun 2 20:29:12 lotus kernel: PCI: Found IRQ 9 for device 00:07.2 Jun 2 20:29:12 lotus kernel: PCI: Sharing IRQ 9 with 00:07.3 Jun 2 20:29:12 lotus kernel: PCI: Sharing IRQ 9 with 00:0f.0 Jun 2 20:29:12 lotus kernel: uhci.c: USB UHCI at I/O 0xb400, IRQ 9 Jun 2 20:29:12 lotus kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 2 20:29:12 lotus kernel: hub.c: USB hub found Jun 2 20:29:12 lotus kernel: hub.c: 2 ports detected Jun 2 20:29:13 lotus kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 2 20:29:13 lotus kernel: usb.c: USB device 2 (vend/prod 0x55f/0x21d) is not claimed by any active driver. - starting xsane: no message in /var/log/messages (I guess explainable from the above message in the last line) Sorry for the long tail output, but I don't know what's really relevant and I hope, that Mozilla doesn't produce any uncomfortable linebreaks. BTW: usb.-uhci ends up with the same message. Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier at wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From karsten.festag at gmx.de Mon Jun 2 20:17:24 2003 From: karsten.festag at gmx.de (Karsten Festag) Date: Mon, 2 Jun 2003 21:17:24 +0200 Subject: [sane-devel] Microtek SlimScan C3, output always a black image In-Reply-To: <3ED56CD9.7080608@okstate.edu> References: <3ED27A5A.8050400@okstate.edu> <200305271856.47694.karsten.festag@gmx.de> <3ED56CD9.7080608@okstate.edu> Message-ID: <200306022117.24137.karsten.festag@gmx.de> Hi Jose, please look into your BIOS and make sure the parport mode is set to EPP, not ECP! I heard several times that this is the cause for stretched or shifted image lines. By the way: switching off the backend calibration has a negative side effect: you will probably see fine vertical stripes on your scanned images. Normally the backend calibration gets rid of it, but it looks like we have to find the bug in the calibration code so that it works with your scanner. Please tell me if we shall do some work in this direction - I'll need some testing work on your side to achieve this. Could you please tell me what error message appears if you use the '-y20' option to generate a logfile? Karsten On Thursday 29 May 2003 04:13, Jose Sanchez wrote: > Hi Karsten, thanks for the help, and sorry for the late answer. > > >until now I didn't find strange things in the logfile. But what error > > message gives the -y20 option (though this shouldn't be connected to the > > dark image failure)? > >Please try what happens when you (in xsane or xscanimage) turn off the > >advanced option 'calibration by backend'. > >Do you see that the scanning illumination is on during the scan? > > well I turn off the advance option you tell me and finally I am able to > see the image, although sometimes the image is acquire incorrectly, I > mean, it is cut and streched in some parts. I rescan the image several > times until the image is acquire correclty. Do you have any idea how > should I correct that error. > > Thanks > > Jose > > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From khk at khk.net Mon Jun 2 21:42:40 2003 From: khk at khk.net (Karl Heinz Kremer) Date: Mon, 2 Jun 2003 16:42:40 -0400 Subject: [sane-devel] epson: scanimage threshold option not working in 1.0.12 backend In-Reply-To: <3EDB7EE1.3040403@pscomp.com> References: <3EDB7EE1.3040403@pscomp.com> Message-ID: <20030602204240.GA9957@khk.net> No it was not ... I'll take a look. Karl Heinz On Mon, Jun 02, 2003 at 12:44:17PM -0400, Peter Santoro wrote: > The scanimage threshold option worked in the 1.0.9 backend with my Epson > 1660 Photo Perfection scanner. After uninstalling the 1.0.9 backend and > installing the 1.0.12 backend, scanimage complains "attempted to set > inactive option threshold" and fails. I took a quick look at the epson > code (which I am not familiar with yet), but have not found anything yet. > Was this change intentional? > > Thank you for your help, > > Peter > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel -- Karl Heinz Kremer khk at khk.net PGP Key at http://www.khk.net/download/khk.asc EPSON Sane Backend: http://www.khk.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From dahjelle at yahoo.com Tue Jun 3 05:30:00 2003 From: dahjelle at yahoo.com (David Alan Hjelle) Date: Mon, 2 Jun 2003 21:30:00 -0700 (PDT) Subject: [sane-devel] Compiling SANE backends on Mac OS X 10.1.5 Message-ID: <20030603043000.5308.qmail@web13404.mail.yahoo.com> Hello. I've been trying to get my Microtek SlimScan C6 cheap-o scanner to work under Mac OS X for a while now, and just recently ran across SANE. I figure I should be able to use SANE with the GIMP, which I use somewhat regularly. I was trying to compile the lastest CVS snapshot (from June 2, 2003) of SANE backends, but I ran into some problems. ./configure ran no problem. make, however, eventually gave me the following errors (Or, at least, these are the errors deaing with the sanei_scsi.c file that seemed to be the cause for the compilation problem. I think everything else was just warnings. Of course, what do I know? I'm only just teaching myself C programming and have only had experience in VB and Java .): cc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -g -O2 -W -Wall -Wcast-align -Wcast-qual -Wmissing-declarations -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wstrict-prototypes -pedantic -ansi sanei_scsi.c sanei_scsi.c:4444: illegal statement, missing `;' after `io_object_t' sanei_scsi.c:4446: illegal expression, found `int' sanei_scsi.c:4452: illegal expression, found `int' sanei_scsi.c:4454: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4460: illegal statement, missing `;' after `io_iterator_t' sanei_scsi.c:4466: illegal statement, missing `;' after `io_object_t' sanei_scsi.c:4476: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4480: illegal expression, found `int' sanei_scsi.c:4483: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4487: illegal expression, found `int' sanei_scsi.c:4503: illegal statement, missing `;' after `SInt32' sanei_scsi.c:4512: illegal statement, missing `;' after `HRESULT' sanei_scsi.c:4536: illegal statement, missing `;' after `CDBInfo' sanei_scsi.c:4540: illegal statement, missing `;' after `IOVirtualRange' sanei_scsi.c:4541: illegal statement, missing `;' after `UInt32' sanei_scsi.c:4542: illegal statement, missing `;' after `Boolean' sanei_scsi.c:4559: illegal statement, missing `;' after `SCSIResults' sanei_scsi.c:4560: illegal statement, missing `;' after `UInt32' sanei_scsi.c:4595: illegal expression, found `int' sanei_scsi.c:4601: illegal expression, found `int' sanei_scsi.c:4603: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4609: illegal statement, missing `;' after `io_iterator_t' sanei_scsi.c:4615: illegal statement, missing `;' after `io_object_t' sanei_scsi.c:4625: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4629: illegal expression, found `int' sanei_scsi.c:4632: illegal statement, missing `;' after `CFNumberRef' sanei_scsi.c:4636: illegal expression, found `int' sanei_scsi.c:4641: illegal statement, missing `;' after `SInt32' sanei_scsi.c:4651: illegal statement, missing `;' after `HRESULT' sanei_scsi.c:4664: illegal statement, missing `;' after `SCSIInquiry' sanei_scsi.c:4665: illegal statement, missing `;' after `UInt32' cpp-precomp: warning: errors during smart preprocessing, retrying in basic mode In file included from /usr/include/machine/types.h:30, from /usr/include/sys/types.h:70, from ../include/sane/config.h:444, from sanei_scsi.c:47: /usr/include/ppc/types.h:75: warning: ANSI C does not support `long long' /usr/include/ppc/types.h:76: warning: ANSI C does not support `long long' In file included from sanei_scsi.c:47: ../include/sane/config.h:445: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:27, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:5, from sanei_scsi.c:184: /usr/include/stdint.h:68: warning: ANSI C does not support `long long' /usr/include/stdint.h:69: warning: ANSI C does not support `long long' In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBase.h:32, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:5, from sanei_scsi.c:184: /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore.framework/Headers/MacTypes.h:120: warning: ANSI C does not support `long long' /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore.framework/Headers/MacTypes.h:121: warning: ANSI C does not support `long long' /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore.framework/Headers/MacTypes.h:291: warning: function declaration isn't a prototype /System/Library/Frameworks/CoreServices.framework/Headers/../Frameworks/CarbonCore.framework/Headers/MacTypes.h:292: warning: function declaration isn't a prototype In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:6, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFArray.h:346: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:7, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBag.h:63: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFCharacterSet.h:35, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:8, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFData.h:40: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:11, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFCharacterSet.h:36, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:8, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFDictionary.h:516: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFCharacterSet.h:36, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:8, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:89: warning: ANSI C restricts enumerator values to range of `int' /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:232: warning: ANSI C forbids const or volatile functions /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:235: warning: ANSI C forbids const or volatile functions /System/Library/Frameworks/CoreFoundation.framework/Headers/CFString.h:449: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:14, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFSet.h:64: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:19, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFXMLNode.h:166: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:40, from sanei_scsi.c:184: /usr/include/math.h:191: warning: function declaration isn't a prototype In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:63, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFBinaryHeap.h:209: warning: ANSI C forbids const or volatile functions In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:66, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h: In function `CFSwapInt16': /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:40: `asm' undeclared (first use in this function) /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:40: (Each undeclared identifier is reported only once /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:40: for each function it appears in.) /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:40: parse error before `volatile' /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:33: warning: unused parameter `arg' /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h: In function `CFSwapInt32': /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:64: `asm' undeclared (first use in this function) /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:64: parse error before `volatile' /System/Library/Frameworks/CoreFoundation.framework/Headers/CFByteOrder.h:57: warning: unused parameter `arg' In file included from /usr/include/mach/machine/vm_types.h:27, from /usr/include/mach/port.h:65, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFRunLoop.h:66, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CFMachPort.h:10, from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:72, from sanei_scsi.c:184: /usr/include/mach/ppc/vm_types.h: At top level: /usr/include/mach/ppc/vm_types.h:181: warning: ANSI C does not support `long long' In file included from /System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:82, from sanei_scsi.c:184: /System/Library/Frameworks/CoreFoundation.framework/Headers/CFStream.h:171: warning: ANSI C forbids const or volatile functions In file included from /usr/include/mach/memory_object_types.h:68, from /usr/include/mach/mach_types.h:69, from /System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:38, from sanei_scsi.c:185: /usr/include/mach/vm_types.h:34: warning: ANSI C does not support `long long' In file included from /usr/include/mach/mach_types.h:69, from /System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:38, from sanei_scsi.c:185: /usr/include/mach/memory_object_types.h:73: warning: ANSI C does not support `long long' /usr/include/mach/memory_object_types.h:74: warning: ANSI C does not support `long long' In file included from /System/Library/Frameworks/IOKit.framework/Headers/IOKitLib.h:48, from sanei_scsi.c:185: /System/Library/Frameworks/IOKit.framework/Headers/OSMessageNotification.h:83: warning: ANSI C forbids zero-size array `content' /System/Library/Frameworks/IOKit.framework/Headers/OSMessageNotification.h:93: warning: ANSI C forbids zero-size array `args' In file included from /System/Library/Frameworks/IOKit.framework/Headers/cdb/IOSCSILib.h:15, from sanei_scsi.c:187: /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSICommand.h:61: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSICommand.h:71: warning: comma at end of enumerator list In file included from /System/Library/Frameworks/IOKit.framework/Headers/cdb/IOSCSILib.h:16, from sanei_scsi.c:187: /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:66: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:79: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:88: warning: ANSI C restricts enumerator values to range of `int' /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:89: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:95: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIDevice.h:101: warning: comma at end of enumerator list In file included from /System/Library/Frameworks/IOKit.framework/Headers/cdb/IOSCSILib.h:17, from sanei_scsi.c:187: /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:61: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:66: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:77: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:105: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:116: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:137: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:150: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:170: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:175: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:182: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:255: warning: comma at end of enumerator list /System/Library/Frameworks/IOKit.framework/Headers/scsi/scsi-device/SCSIPublic.h:289: warning: comma at end of enumerator list In file included from ../include/sane/sanei.h:66, from sanei_scsi.c:198: ../include/sane/sane.h:197: warning: ANSI C forbids const or volatile functions In file included from sanei_scsi.c:199: ../include/sane/sanei_config.h:87: warning: ANSI C forbids const or volatile functions ../include/sane/sanei_config.h:104: warning: ANSI C forbids const or volatile functions sanei_scsi.c: In function `sanei_scsi_open': sanei_scsi.c:812: warning: unused variable `real_dev' sanei_scsi.c: In function `sanei_scsi_cmd2': sanei_scsi.c:4444: parse error before `scsiDevice' sanei_scsi.c:4447: `i' undeclared (first use in this function) sanei_scsi.c:4447: `scsiDevice' undeclared (first use in this function) sanei_scsi.c:4452: parse error before `int' sanei_scsi.c:4457: `deviceTypeRef' undeclared (first use in this function) sanei_scsi.c:4460: parse error before `scsiObjectIterator' sanei_scsi.c:4463: `scsiObjectIterator' undeclared (first use in this function) sanei_scsi.c:4466: parse error before `device' sanei_scsi.c:4467: `device' undeclared (first use in this function) sanei_scsi.c:4476: parse error before `scsiTargetRef' sanei_scsi.c:4481: `scsiTargetRef' undeclared (first use in this function) sanei_scsi.c:4481: `scsitarget' undeclared (first use in this function) sanei_scsi.c:4483: parse error before `scsiLunRef' sanei_scsi.c:4488: `scsiLunRef' undeclared (first use in this function) sanei_scsi.c:4488: `scsilun' undeclared (first use in this function) sanei_scsi.c:4491: warning: comparison between signed and unsigned sanei_scsi.c:4502: parse error before `*' sanei_scsi.c:4507: `plugInInterface' undeclared (first use in this function) sanei_scsi.c:4508: `score' undeclared (first use in this function) sanei_scsi.c:4512: parse error before `plugInResult' sanei_scsi.c:4515: `plugInResult' undeclared (first use in this function) sanei_scsi.c:4518: `scsiDeviceInterface' undeclared (first use in this function) sanei_scsi.c:4528: parse error before `*' sanei_scsi.c:4532: `cdbCommandInterface' undeclared (first use in this function) sanei_scsi.c:4536: parse error before `cdb' sanei_scsi.c:4537: `cdb' undeclared (first use in this function) sanei_scsi.c:4540: parse error before `range' sanei_scsi.c:4546: `range' undeclared (first use in this function) sanei_scsi.c:4548: `transferCount' undeclared (first use in this function) sanei_scsi.c:4549: `isWrite' undeclared (first use in this function) sanei_scsi.c:4559: parse error before `results' sanei_scsi.c:4564: `seqNumber' undeclared (first use in this function) sanei_scsi.c:4569: `results' undeclared (first use in this function) sanei_scsi.c: In function `sanei_scsi_find_devices': sanei_scsi.c:4595: parse error before `int' sanei_scsi.c:4596: `i' undeclared (first use in this function) sanei_scsi.c:4601: parse error before `int' sanei_scsi.c:4606: `deviceTypeRef' undeclared (first use in this function) sanei_scsi.c:4609: parse error before `scsiObjectIterator' sanei_scsi.c:4612: `scsiObjectIterator' undeclared (first use in this function) sanei_scsi.c:4615: parse error before `scsiDevice' sanei_scsi.c:4616: `scsiDevice' undeclared (first use in this function) sanei_scsi.c:4625: parse error before `scsiTargetRef' sanei_scsi.c:4630: `scsiTargetRef' undeclared (first use in this function) sanei_scsi.c:4630: `scsitarget' undeclared (first use in this function) sanei_scsi.c:4632: parse error before `scsiLunRef' sanei_scsi.c:4637: `scsiLunRef' undeclared (first use in this function) sanei_scsi.c:4637: `scsilun' undeclared (first use in this function) sanei_scsi.c:4640: parse error before `*' sanei_scsi.c:4646: `plugInInterface' undeclared (first use in this function) sanei_scsi.c:4647: `score' undeclared (first use in this function) sanei_scsi.c:4651: parse error before `plugInResult' sanei_scsi.c:4654: `plugInResult' undeclared (first use in this function) sanei_scsi.c:4657: `scsiDeviceInterface' undeclared (first use in this function) sanei_scsi.c:4664: parse error before `inquiry' sanei_scsi.c:4667: `inquiry' undeclared (first use in this function) sanei_scsi.c:4668: `inquirySize' undeclared (first use in this function) sanei_scsi.c:4585: warning: unused parameter `findtype' sanei_scsi.c:4586: warning: unused parameter `findbus' sanei_scsi.c:4586: warning: unused parameter `findchannel' sanei_scsi.c:4586: warning: unused parameter `findid' sanei_scsi.c: In function `sanei_scsi_req_enter2': sanei_scsi.c:4700: warning: unused parameter `idp' sanei_scsi.c: In function `sanei_scsi_req_wait': sanei_scsi.c:4706: warning: unused parameter `id' sanei_scsi.c: In function `sanei_scsi_req_flush_all_extended': sanei_scsi.c:4717: warning: unused parameter `fd' make[1]: *** [sanei_scsi.o] Error 1 make: *** [all-recursive] Error 1 Wow, that was really long. Sorry. I hope that was enough info, though. I hope you can help. I'd love to get this scanner working again. In Christ Alone, David Alan Hjelle 1 Corithians 2:2 http://welcome.to/theJESUSpage __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com From moali at sbox.tugraz.at Tue Jun 3 08:42:19 2003 From: moali at sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 09:42:19 +0200 Subject: [sane-devel] backends 1.0.12 compile-error Message-ID: <3EDC515B.8050706@sbox.tugraz.at> Hello sane-devel! Unfortunately my attempts to compile sane-backends 1.0.12 fail on my machine (1.0.11 worked without any problem). Configure mentions no error. Kernel 2.4.17 If you need any further information, please mail me. Regards, Maier Gerfried [...] hp5400_internal.c:411: warning: unused parameter `iHandle' hp5400_internal.c: In function `hp5400_test_scan_response': hp5400_internal.c:660: warning: unused parameter `req' hp5400_internal.c: In function `DoScan': hp5400_internal.c:729: warning: unused parameter `code' hp5400_internal.c: In function `hp5400_scan': hp5400_internal.c:909: warning: unused parameter `pHWParams' hp5400_internal.c: In function `InitScan2': hp5400_internal.c:1187: warning: comparison between signed and unsigned hp5400_internal.c:1223: warning: comparison between signed and unsigned hp5400.c: In function `attach_one_device': hp5400.c:432: warning: passing arg 1 of `HP5400Detect' discards qualifiers from pointer target type hp5400.c: At top level: hp5400_sanei.c:253: warning: `hp5400_bulk_read' defined but not used hp5400_sanei.c:361: warning: `hp5400_isOn' defined but not used hp5400_internal.c:605: warning: `DecodeImage' defined but not used hp5400_internal.c:661: warning: `hp5400_test_scan_response' defined but not used hp5400_internal.c:975: warning: `PreviewScan' defined but not used hp5400_internal.c:1013: warning: `InitScanner' defined but not used rm -f hp5400-s.c ln -s ./stubs.c hp5400-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=hp5400 hp5400-s.c -fPIC -DPIC -o .libs/hp5400-s.o gcc -shared .libs/hp5400.o .libs/hp5400-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../sanei/.libs/sanei_usb.o ../sanei/.libs/sanei_config2.o -lnsl -lm /usr/lib/libjpeg.so -ldl -Wl,-soname -Wl,libsane.so.1 -o .libs/libsane-hp5400.so.1.0.12 (cd .libs && rm -f libsane-hp5400.so.1 && ln -s libsane-hp5400.so.1.0.12 libsane-hp5400.so.1) (cd .libs && rm -f libsane-hp5400.so && ln -s libsane-hp5400.so.1.0.12 libsane-hp5400.so) creating libsane-hp5400.la (cd .libs && rm -f libsane-hp5400.la && ln -s ../libsane-hp5400.la libsane-hp5400.la) make[1]: Verlassen des Verzeichnisses Verzeichnis ?/home/moali/src/sane-backends-1.0.12/backend? making all in frontend make[1]: Wechsel in das Verzeichnis Verzeichnis ?/home/moali/src/sane-backends-1.0.12/frontend? gcc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I/usr/local/include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -g -O2 -W -Wall saned.c saned.c: In function `check_host': saned.c:559: structure has no member named `ss_family' saned.c:562: warning: unreachable code at beginning of switch statement saned.c: In function `start_scan': saned.c:1025: structure has no member named `ss_family' saned.c:1034: structure has no member named `ss_family' saned.c:1037: warning: unreachable code at beginning of switch statement saned.c:1074: structure has no member named `ss_family' saned.c:1077: warning: unreachable code at beginning of switch statement make[1]: *** [saned.o] Fehler 1 make[1]: Verlassen des Verzeichnisses Verzeichnis ?/home/moali/src/sane-backends-1.0.12/frontend? make: *** [all-recursive] Fehler 1 From kleptog at svana.org Tue Jun 3 10:07:20 2003 From: kleptog at svana.org (Martijn van Oosterhout) Date: Tue, 3 Jun 2003 19:07:20 +1000 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC515B.8050706@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> Message-ID: <20030603090720.GA10945@svana.org> On Tue, Jun 03, 2003 at 09:42:19AM +0200, Gerfried Maier wrote: > Hello sane-devel! > > Unfortunately my attempts to compile sane-backends 1.0.12 fail on my > machine (1.0.11 worked without any problem). Configure mentions no error. > > Kernel 2.4.17 W.R.T. the hp5400 backend those are just a bunch of warnings so they're not important (but should be fixed anyway). Your actual error is: > saned.c: In function `check_host': > saned.c:559: structure has no member named `ss_family' > saned.c:562: warning: unreachable code at beginning of switch statement I can't quite see what the problem is, my version here doesn't show it. Can you check the strucutre used to see if it really has it. Oh yeah, what OS is this? -- Martijn van Oosterhout http://svana.org/kleptog/ > "the West won the world not by the superiority of its ideas or values or > religion but rather by its superiority in applying organized violence. > Westerners often forget this fact, non-Westerners never do." > - Samuel P. Huntington -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: From moali at sbox.tugraz.at Tue Jun 3 10:27:28 2003 From: moali at sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 11:27:28 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <20030603090720.GA10945@svana.org> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> Message-ID: <3EDC6A00.90907@sbox.tugraz.at> Martijn van Oosterhout wrote: >On Tue, Jun 03, 2003 at 09:42:19AM +0200, Gerfried Maier wrote: > > >>saned.c: In function `check_host': >>saned.c:559: structure has no member named `ss_family' >>saned.c:562: warning: unreachable code at beginning of switch statement >> The affected lines from saned.c - unfortunately I'm not very used to C-programming, so that I cannot read that much out of them: [...] switch (remote_address.ss_family) { case AF_INET: if (IN_LOOPBACK (ntohl (sin->sin_addr.s_addr))) { DBG (DBG_MSG, "check_host: remote host is IN_LOOPBACK: access granted\n"); return SANE_STATUS_GOOD; } break; [...] remote_address is defined somewhere around line 195 in saned.c: [...] #ifdef SANED_USES_AF_INDEP static struct sockaddr_storage remote_address; static int remote_address_len; #else static struct in_addr remote_address; #endif /* SANED_USES_AF_INDEP */ [...] >I can't quite see what the problem is, my version here doesn't show it. Can >you check the strucutre used to see if it really has it. > >Oh yeah, what OS is this? > > Sorry, 've forgotten to mention it: Linux with Kernel 2.4.17 Maier Gerfried From jb at jblache.org Tue Jun 3 10:56:37 2003 From: jb at jblache.org (Julien BLACHE) Date: Tue, 03 Jun 2003 11:56:37 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC6A00.90907@sbox.tugraz.at> (Gerfried Maier's message of "Tue, 03 Jun 2003 11:27:28 +0200") References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: <87brxfxz56.fsf@frigate.technologeek.org> Gerfried Maier wrote: >>>saned.c: In function `check_host': >>>saned.c:559: structure has no member named `ss_family' >>>saned.c:562: warning: unreachable code at beginning of switch statement >>> > > The affected lines from saned.c - unfortunately I'm not very used to > C-programming, so that I cannot read that much out of them: If you do not need IPv6 support, configure sane-backends with --disable-ipv6 and it'll build fine. I think the version of the libc could be the problem here. JB. -- Julien BLACHE From knan at mo.himolde.no Tue Jun 3 11:09:55 2003 From: knan at mo.himolde.no (=?ISO-8859-1?Q?Erik_Inge_Bols=F8?=) Date: Tue, 3 Jun 2003 12:09:55 +0200 (CEST) Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC6A00.90907@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: On Tue, 3 Jun 2003, Gerfried Maier wrote: >Martijn van Oosterhout wrote: >>On Tue, Jun 03, 2003 at 09:42:19AM +0200, Gerfried Maier wrote: >>>saned.c: In function `check_host': >>>saned.c:559: structure has no member named `ss_family' >>>saned.c:562: warning: unreachable code at beginning of switch statement > >The affected lines from saned.c - unfortunately I'm not very used to >C-programming, so that I cannot read that much out of them: > > >[...] > switch (remote_address.ss_family) > { > case AF_INET: > if (IN_LOOPBACK (ntohl (sin->sin_addr.s_addr))) > { > DBG (DBG_MSG, > "check_host: remote host is IN_LOOPBACK: access >granted\n"); > return SANE_STATUS_GOOD; > } > break; >[...] > >remote_address is defined somewhere around line 195 in saned.c: >[...] >#ifdef SANED_USES_AF_INDEP >static struct sockaddr_storage remote_address; >static int remote_address_len; >#else >static struct in_addr remote_address; >#endif /* SANED_USES_AF_INDEP */ >[...] Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is defined or undefined? If it is undefined, the error would seem to be straightforward, since at least my struct in_addr (in netinet/in.h ) doesn't have any ss_family member... /* Internet address. */ typedef uint32_t in_addr_t; struct in_addr { in_addr_t s_addr; }; -- Erik I. Bols? | email: The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. From henning at meier-geinitz.de Tue Jun 3 10:24:48 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 11:24:48 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030602174212.0ce77aa9.christoph.bier@web.de> References: <20030602111526.5b4034a3.christoph.bier@web.de> <20030602135832.GA30314@meier-geinitz.de> <20030602174212.0ce77aa9.christoph.bier@web.de> Message-ID: <20030603092448.GA5732@hmg1> Hi, On Mon, Jun 02, 2003 at 05:42:12PM +0200, Christoph Bier wrote: > These are the messages I get, when I plug-out the > (work) scanner and plug-in it again. > > Jun 2 17:33:38 nb-pc057 kernel: usb.c: USB disconnect on device > 00:11.2-1 address 2 > Jun 2 17:33:53 nb-pc057 kernel: hub.c: new USB device 00:11.2-1, > assigned address 3 > Jun 2 17:33:58 nb-pc057 kernel: usb_control/bulk_msg: timeout > Jun 2 17:33:58 nb-pc057 kernel: hub.c: new USB device 00:11.2-1, > assigned address 4 Looks fine. > Jun 2 17:34:03 nb-pc057 kernel: usb_control/bulk_msg: timeout Oh well. Either a hardware problem (too slow to react?) or a kernel bug. Check the linux-usb-users mailing list for this one, I remeber that other people had similar problems, but not with scanners. Maybe that's a problem with your USB chipset, but I don't remeber the details. It doesn't seem to be an issue of the scanner module or sane. > > Or your distribution found the scanner and used some hotplugging > > magic but failed. And that stops your scanner from beeing detected > > Is there a possibility to turn such "hotplugging > magic" off? Yes :-) For the details, consult your distribution's documentation. A rather drasti way is to renam the /sbin/hotplug program to something else. Bye, Henning From soumarmt at nerim.net Tue Jun 3 11:17:34 2003 From: soumarmt at nerim.net (Thomas Soumarmon) Date: Tue, 3 Jun 2003 12:17:34 +0200 Subject: [sane-devel] backends 1.0.12 compile-error Message-ID: <200306031217.34653.soumarmt@nerim.net> Maybe on a linux before version 2.4.19 the structures sockaddr_storage in_addr do not have ss_family member. A solution to that would be to migrate to a newer kernel or compile an older version of SANE ? From henning at meier-geinitz.de Tue Jun 3 11:28:52 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 12:28:52 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC6A00.90907@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: <20030603102852.GC13710@hmg1> Hi, On Tue, Jun 03, 2003 at 11:27:28AM +0200, Gerfried Maier wrote: > switch (remote_address.ss_family) > static struct sockaddr_storage remote_address; struct sockaddr_storage is defined in /usr/include/bits/socket.h: struct sockaddr_storage { __SOCKADDR_COMMON (ss_); /* Address family, etc. */ __ss_aligntype __ss_align; /* Force desired alignment. */ char __ss_padding[_SS_PADSIZE]; }; with: #define __SOCKADDR_COMMON(sa_prefix) \ sa_family_t sa_prefix##family So remote_address.ss_family should be ok. I think I've seen that compilation error on Linux/arm and that's a glibc bug (I guess). What version of the C-library do you use? Hoq is struct sockaddr_storage defined? Bye, Henning From moali at sbox.tugraz.at Tue Jun 3 12:25:55 2003 From: moali at sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 13:25:55 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: <3EDC85C3.4040309@sbox.tugraz.at> Erik Inge Bols? wrote: >Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is >defined or undefined? > in include/sane/config.h: (around line 70) [...] /* Define to 1 if you have the `getaddrinfo' function. */ #define HAVE_GETADDRINFO 1 /* Define to 1 if you have the `getenv' function. */ #define HAVE_GETENV 1 /* Define to 1 if you have the `getnameinfo' function. */ #define HAVE_GETNAMEINFO 1 [...] and in frontend/saned.c: (around line 35) [...] #if defined(HAVE_GETADDRINFO) && defined (HAVE_GETNAMEINFO) # define SANED_USES_AF_INDEP #else # undef ENABLE_IPV6 #endif /* HAVE_GETADDRINFO && HAVE_GETNAMEINFO && HAVE_POLL */ [...] so finally, SANED_USES_AF_INDEP should be defined. >If it is undefined, the error would seem to be straightforward, since at >least my struct in_addr (in netinet/in.h ) doesn't have any ss_family >member... > >/* Internet address. */ >typedef uint32_t in_addr_t; >struct in_addr > { > in_addr_t s_addr; > }; > Same here. Maier Gerfried From moali at sbox.tugraz.at Tue Jun 3 12:28:51 2003 From: moali at sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 13:28:51 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <87brxfxz56.fsf@frigate.technologeek.org> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <87brxfxz56.fsf@frigate.technologeek.org> Message-ID: <3EDC8673.7060601@sbox.tugraz.at> Julien BLACHE wrote: >Gerfried Maier wrote: > > > >>>>saned.c: In function `check_host': >>>>saned.c:559: structure has no member named `ss_family' >>>>saned.c:562: warning: unreachable code at beginning of switch statement >>>> >>>> >>>> >>The affected lines from saned.c - unfortunately I'm not very used to >>C-programming, so that I cannot read that much out of them: >> >> > >If you do not need IPv6 support, configure sane-backends with >--disable-ipv6 and it'll build fine. > Unfortunately not. Same error. >I think the version of the libc could be the problem here. > # /lib/libc.so.6 GNU C Library stable release version 2.1.3, by Roland McGrath et al. Copyright (C) 1992, 93, 94, 95, 96, 97, 98, 99 Free Software Foundation, Inc. [...] Regards, Maier Gerfried From moali at sbox.tugraz.at Tue Jun 3 12:44:41 2003 From: moali at sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 13:44:41 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> Message-ID: <3EDC8A29.60500@sbox.tugraz.at> Erik Inge Bols? wrote: >On Tue, 3 Jun 2003, Gerfried Maier wrote: > > >>[...] >> >>remote_address is defined somewhere around line 195 in saned.c: >>[...] >>#ifdef SANED_USES_AF_INDEP >>static struct sockaddr_storage remote_address; >>static int remote_address_len; >>#else >>static struct in_addr remote_address; >>#endif /* SANED_USES_AF_INDEP */ >>[...] >> >> > >Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is >defined or undefined? > >If it is undefined, the error would seem to be straightforward, since at >least my struct in_addr (in netinet/in.h ) doesn't have any ss_family >member... > >/* Internet address. */ >typedef uint32_t in_addr_t; >struct in_addr > { > in_addr_t s_addr; > }; > I just figured out that sockaddr_storage is defined in bits/socket.h. There it says (around line 143): [...] /* Structure large enough to hold any socket address (with the historical exception of AF_UNIX). We reserve 128 bytes. */ #if ULONG_MAX > 0xffffffff # define __ss_aligntype __uint64_t #else # define __ss_aligntype __uint32_t #endif #define _SS_SIZE 128 #define _SS_PADSIZE (_SS_SIZE - (2 * sizeof (__ss_aligntype))) struct sockaddr_storage { __SOCKADDR_COMMON (__ss_); /* Address family, etc. */ __ss_aligntype __ss_align; /* Force desired alignment. */ char __ss_padding[_SS_PADSIZE]; }; [...] No (obvious?) member ss_family, too. Maier Gerfried From knan at mo.himolde.no Tue Jun 3 12:46:19 2003 From: knan at mo.himolde.no (=?ISO-8859-1?Q?Erik_Inge_Bols=F8?=) Date: Tue, 3 Jun 2003 13:46:19 +0200 (CEST) Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC85C3.4040309@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC85C3.4040309@sbox.tugraz.at> Message-ID: On Tue, 3 Jun 2003, Gerfried Maier wrote: >Erik Inge Bols? wrote: > >>Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is >>defined or undefined? >[...] > >so finally, SANED_USES_AF_INDEP should be defined. Okay. Ah. I think I found it. http://www.landfield.com/wu-ftpd/mail-archive/wuftpd-dev/2001/Aug/0001.html >| ftpd.c:1093: structure has no member named `ss_family' > >This message is because the Linux sockaddr_storage struct member is >called __ss_family not ss_family, if using configure add "#define >HAVE__SS_FAMILY" to the generated src/config.h (before the Socket >macros), then run make. >You could also try using build, edit config.h.noac, change "#undef INET6" >to "#define INET6" followed by ./build lnx should work. ... anyone feel like adding a configure check and a patch for this? Probably a certain libc or a certain distro has this problem. -- Erik I. Bols? | email: The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. From knan at mo.himolde.no Tue Jun 3 12:48:00 2003 From: knan at mo.himolde.no (=?ISO-8859-1?Q?Erik_Inge_Bols=F8?=) Date: Tue, 3 Jun 2003 13:48:00 +0200 (CEST) Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC8A29.60500@sbox.tugraz.at> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC8A29.60500@sbox.tugraz.at> Message-ID: On Tue, 3 Jun 2003, Gerfried Maier wrote: >[...] >/* Structure large enough to hold any socket address (with the historical > exception of AF_UNIX). We reserve 128 bytes. */ >#if ULONG_MAX > 0xffffffff ># define __ss_aligntype __uint64_t >#else ># define __ss_aligntype __uint32_t >#endif >#define _SS_SIZE 128 >#define _SS_PADSIZE (_SS_SIZE - (2 * sizeof (__ss_aligntype))) > >struct sockaddr_storage > { > __SOCKADDR_COMMON (__ss_); /* Address family, etc. */ > __ss_aligntype __ss_align; /* Force desired alignment. */ > char __ss_padding[_SS_PADSIZE]; > }; >[...] > >No (obvious?) member ss_family, too. See my other mail. This seems to confirm it. What distro / libc do you have? -- Erik I. Bols? | email: The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. From moali at sbox.tugraz.at Tue Jun 3 13:35:53 2003 From: moali at sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 14:35:53 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC85C3.4040309@sbox.tugraz.at> Message-ID: <3EDC9629.8030405@sbox.tugraz.at> Erik Inge Bols? wrote: >On Tue, 3 Jun 2003, Gerfried Maier wrote: > > >>Erik Inge Bols? wrote: >> >> >> >>>Can you check in your config.h post-configure if "SANED_USES_AF_INDEP" is >>>defined or undefined? >>> >>> >>[...] >> >>so finally, SANED_USES_AF_INDEP should be defined. >> >> > >Okay. > >Ah. I think I found it. > >http://www.landfield.com/wu-ftpd/mail-archive/wuftpd-dev/2001/Aug/0001.html > > > >>| ftpd.c:1093: structure has no member named `ss_family' >> >>This message is because the Linux sockaddr_storage struct member is >>called __ss_family not ss_family, if using configure add "#define >>HAVE__SS_FAMILY" to the generated src/config.h (before the Socket >>macros), then run make. >>You could also try using build, edit config.h.noac, change "#undef INET6" >>to "#define INET6" followed by ./build lnx should work. >> >> > >... anyone feel like adding a configure check and a patch for this? >Probably a certain libc or a certain distro has this problem. > That's it! Replaced all occurences of ss_family in frontend/saned.c with __ss_family - and it compiles! Erik, Thank you for your help! Gerfried Maier From moali at sbox.tugraz.at Tue Jun 3 13:56:02 2003 From: moali at sbox.tugraz.at (Gerfried Maier) Date: Tue, 03 Jun 2003 14:56:02 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <20030603102852.GC13710@hmg1> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <20030603102852.GC13710@hmg1> Message-ID: <3EDC9AE2.8010700@sbox.tugraz.at> Henning Meier-Geinitz wrote: >Hi, > >On Tue, Jun 03, 2003 at 11:27:28AM +0200, Gerfried Maier wrote: > > >> switch (remote_address.ss_family) >> static struct sockaddr_storage remote_address; >> >> > >struct sockaddr_storage is defined in /usr/include/bits/socket.h: >struct sockaddr_storage > { > __SOCKADDR_COMMON (ss_); /* Address family, etc. */ > Ah. here it is: __SOCKADDR_COMMON (__ss_); /* Address family, etc. */ ^ ^ >[...] >So remote_address.ss_family should be ok. I think I've seen that >compilation error on Linux/arm and that's a glibc bug (I guess). What >version of the C-library do you use? Hoq is struct sockaddr_storage >defined? > This is glibc 2.1.3 Greetings, Maier Gerfried From henning at meier-geinitz.de Tue Jun 3 13:56:47 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 14:56:47 +0200 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org In-Reply-To: <3EDB6ACF.3010304@charter.net> References: <3EDB6ACF.3010304@charter.net> Message-ID: <20030603125647.GA817@hmg1> Hi, On Mon, Jun 02, 2003 at 10:18:39AM -0500, Howard Shane wrote: > I would like to announce the completion of the initial draft of the > Scanner-HOWTO for the linux documentation project, and invite > participants on the SANE-devel mailing list to comment on it. Cool! Nice work. > Any help you can suggest to clarify or otherwise improve the draft will > be greatly appreciated and may even result in you being mentioned in the > credits if you so desire. Ok, if you want corrections/comments you'll get them :-). I'm not a native English speaker, so I have misunderstood some of the documentation. | 2.1. SCSI Devices | In general if you have one of the following SCSI adapters, your | scanner should work without difficulty: Pretty much any SCSI adapter should work. Some may need some tweaking. I'm not sure if it helps to select just a few ones. | Acard/Advance At least with older kernels, there was a lot of trouble with those. | Adaptec AHA-1505/AHA-1542/AHA-2940 | ASUS SC200 | BusLogic BT958 | NCR/Symbios 53c400/53c400 ISA card | Domex DTC3181E/L/LE (DTCT436/436P) ISA card The last two are very low level cards that come with SCSI scanners (e.g. Mustek ones). I wouldn't call them "work without difficulty". While they can be made to work, they are slow and the driver tends to crash quite often. | Again, consult the above referenced link if you are unsure. That's the SANE backend list link? Maybe linking to the sane-scsi manpage makes sense here. The manpages are online on mostang.com in html format. | 2.3. Parallel Port Devices | If your scanner is really old and has a 25-pin connector it is | probably of this type. SOme SCSI scanners have the same db25 connector and the same cable. So be careful... | I recommend checking out the page on the subject by Jonathan Buzzard | for the working list, though as of this writing the page had not been | updated in some time so there may be hope if yours isn't listed. The scanner search engine can also print a list of all supported parport devices if you just select "parport" and don't enter any keywords. | 3. Kernel Support of your Scanner Device | $ ls -R /lib/modules/X.XX/drivers LC_ALL=C ls -R /lib/modules/2.4.21-rc6/drivers ls: /lib/modules/2.4.21-rc6/drivers: No such file or directory The directory structure changed in recent kernels. It's now /lib/modules/X.XX/kernel/drivers | (A hint for newbies: if the info in dmesg or the above module list | scrolls by too fast, you can catch the info in a file like so: dmesg > | file.txt, where 'file.txt' will contain the needed info.) If a newbie doesn't know how to deal with that kind of problem, he may not know ho to view the file. What about "dmesg|less"? | 3.1. SCSI Support | | If you have an SCSI card in your computer, there is no kernel option | for SCSI support other than that for your card plus generic SCSI | device support (usually named /dev/sg0, /dev/sg1 etc.). I don't really understand that part. "You only need to enable the two SCSI options ... in the kernel..."? | Since you | probably already know if your card is supported from the next page, | all that is necessary is to load the module like so: Which next page? | 3.2. USB Support Instead of the kernel scanner module, using libusb is also possible. In fact, it may be the only way in Linux 2.6. If you don't use libusb, you may need a really recent kernel (2.4.21-pre) to get some scanners working. | 3.3. Parallel Port Scanners Maybe the maintainers of the parport backends can give some more comments here. Some backends access the parport directly with inb/outb commands or via /dev/port. Loading the "parport" module may interfere with that (?). | Your parallel port should be set to preferably "ECP" mode, or | "bidirectional" (also known as "BPP" or "PS/2") at a minimum. | "Unidirectional" (also known as "SPP") and "EPP" may work, although | more slowly. There is usually a BIOS setting for this. At least the umax_pp backend manpage says "EPP only". | Depending on whether your parallel port scanner requires SCSI support, | you may need to patch your kernel for paraport-SCSI support. Typo: parport. | 4.2. Creating Devices Manually Nice, but are there really any distributions that don't have /dev/MAKEDEV or a similar script that takes care of these details if the devices haven't been created when installing Linux? | 4.2.3. Manually creating Parallel Port Devices Depending on the backend you may need /dev/port, /dev/parport or none of those. | 4.3. Groups and Permissions | # chmod u+rw /dev/usb/scanner0 | ...where u+rw means add read and write access for user. See the | documentation for chmod (man chmod or info chmod) for further info. Didn't you want to give the permission to the group, not the user? | 5. SANE | The final prerequisite for scanner access is the SANE tools and a | suitable SANE-frontend. The former are the drivers and low-level | access tools that interface with your scanner, and the latter are | graphical tools for complex functions used within the X-windows | system. Only the former are required for scanner access, though a | frontend is highly recommended in order to manipulate images and to | actually be able to see your images in a windowed environment without | having to print them. That's a bit confusing IMHO. What do you mean by "SANE tools"? Better use the package name "sane-backends" or the terms "backends" and "frontends". | 5.2. Configuring SANE | 5.2.1. By Scanner Manufacturer | find / -name saned.conf Better don't mention that, because people may start to edit saned.conf... Further more, it may take ages, "locate" is faster. But the rule of thumb is pretty much accurate: "If you compiled the source from mostang.com yourself, it's in /usr/local/etc, otherwise in /etc." | Change to the indicated directory and look for the name of your | manufacturer. For example, if you have an HP scanner, hp.conf or an | Epson scanner epson.conf and so on. That doesn't work for many scanners. E.g. Epson scanners may also be supported by the plustek backend. Mustek scanners may be supported by mustek, mustek_usb, mustek_pp, gt68xx, plustek or ma1509 backends. Better point the user to the devicel ists, they contain the name of the backend. | You should see two items in the file: interface type (scsi vs. usb), | and the device name. If you have a usb scanner, you will usually need | to comment out (make a # mark in front of) the 'scsi' line, and | uncomment the line containing 'usb.' While this may work with most backends, it's not a general rule. E.g. the plustek backend uses "device /dev/something". I wouldn't comment on these details without listing (and testing) every single backend that works this way. Most USB and SCSI scanners should work out-of-the-box. So better tell the user to first try "scanimage -L" and only if that doesn't show the scanner give some trouble-shooting tips. | (including sane-plustek, sane-qcam, sane-ricoh | sane-sharpsane-snapscansane-umax and so on. Typos: Missing space and closing parenthesis. | For a full list try apropos sane. Mentioning "man sane" may also make sense here. Don't forget to point to dll.conf. Some distributions tend to modify this file and some backends are commented out by default. | 5.2.2. Across a Network | | If you are interested in making scanner services available across a | network from or to a remote machine, you will need to edit the | saned.conf file ...the saned.conf file on the server (where the scanner is)... | in the same directory as outlined in the previous | section. It usually consists of an entry 'scan-client.somedomain.firm' | that will need to be replaced with the hostname of the target machine. ...the hostname of the client (without the scanner)... net.conf of the client should contain the host name of the server. | The saned daemon will need to be run as well as inetd or xined. The saned is run through inetd or xinetd. Typo: xinetd. | In addition port 6566 will need to be open, accomplished by adding the | following line to /etc/services: /etc/services is just a list of aliases, so you can use "sane" instead of "6566". It doesn't open the port itsself, that's done by (x)inetd. | WARNING: If you plan on running saned across a network it would be | wise to use a separate 'saned' group for those with scanner | privileges, as allowing suid root processed in a network setting is | highly discouraged for security reasons. The saned user/group should be used in (x)inetd.conf. It shouldn't be used by the users themselves. The idea is to give saned as little permissions as possible. | 5.2.3. Using SANE with a Video4linux Device | | Check the configuration directory where you found sane.conf. saned.conf. | There should be a file named 'v4l' v4l.conf. | Opening this file yields the following content (at least on my system): | #/dev/bttv0 | #/dev/video0 [...] The device files are not commented out in original sane-backends source code. Probably this was your distributor. | 6. Testing Your Scanner | sane-find-scanner -v Start with the easy stuff. Nobody likes to scroll through all these details. If "sane-find-scanner" doesn't print anything, "-v" or even "-v -v" can be added later. | If your scanner isn't identified by any of the above, but you're | pretty sure you've done everything right up to now, you can try | scanning as outlined in the next paragraph. If the scanner is not listed with -L, but scanning works with -d backend:/device, the reason is that the backend is commented out in dll.conf. | scanimage -d /dev/scanner0 --format pnm > outfile.pnm The format of -d is "backend:/device_name". The device_name is backend-specific. | 7. Sane Frontends scanimage is also a SANE frontend. | Now that you've got the hardware working, you should probably acquire | a suitable frontend if you plan on using your scanner device in | X-windows (which unless you have SVGAlib installed is probably a good | idea so you can see what you've scanned). Just nitpicking :-): | The X Consortium requests that the following names be used | when referring to this software: | | X | X Window System | X Version 11 | X Window System, Version 11 | X11 There are more frontends than just xsane and xscanimage. You can add a link to the SANE frontends web page, which provides a list of them. | 8.1. If your device cannot be found... It's relatively easy to check if it's a permission problem: Try as root. If it works now, it's most probably casued by permissions. | 8.2. What if SANE can't identify (or correctly identify) my USB scanner? I wouldn't mention the Linux source code at all. There is no need to download or install it. If the device is listed there, it will be detected by the scanner driver. If not, it won't help at all. Better point to the list of USHB devices on linux-usb.org or explain how to read /proc/bus/usb/devices or syslog to get the numbers. Bye, Henning From henning at meier-geinitz.de Tue Jun 3 14:09:37 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 15:09:37 +0200 Subject: [sane-devel] Compiling SANE backends on Mac OS X 10.1.5 In-Reply-To: <20030603043000.5308.qmail@web13404.mail.yahoo.com> References: <20030603043000.5308.qmail@web13404.mail.yahoo.com> Message-ID: <20030603130937.GB817@hmg1> Hi, [MacOS X sanei_scsi.c fails to compile] On Mon, Jun 02, 2003 at 09:30:00PM -0700, David Alan Hjelle wrote: > I was trying to compile the lastest CVS snapshot (from June 2, 2003) of > SANE backends, but I ran into some problems. Does sane-backends 1.0.12 work? > ./configure ran no problem. Try "./configure --disable-warnings" to avoid some of the warnings. > sanei_scsi.c:4444: illegal statement, missing `;' after `io_object_t' I think that's a real bug, the line marked "->" is 4444: if (ioReturnValue != kIOReturnSuccess || masterPort == NULL) return SANE_STATUS_IO_ERROR; -> io_object_t scsiDevice = NULL; int i; There are variable definitions after the code. I don't know if C99 allows this, but older C doesn't. That's C++. > Wow, that was really long. Sorry. I hope that was enough info, though. The core foundation warnings may be because of the enabled warning option in configure. > I hope you can help. I'd love to get this scanner working again. The MacOS X support for sanei_scsi is from Mattias Ellert . I'm cc'ing him in case he doesn't read sane-devel. Bye, Henning From joseos at okstate.edu Tue Jun 3 19:08:16 2003 From: joseos at okstate.edu (Jose Sanchez) Date: Tue, 03 Jun 2003 11:08:16 -0700 Subject: [sane-devel] Microtek SlimScan C3, output always a black image In-Reply-To: <200306022117.24137.karsten.festag@gmx.de> References: <3ED27A5A.8050400@okstate.edu> <200305271856.47694.karsten.festag@gmx.de> <3ED56CD9.7080608@okstate.edu> <200306022117.24137.karsten.festag@gmx.de> Message-ID: <3EDCE410.7040206@okstate.edu> Hi Karsten, thanks again for the help. >please look into your BIOS and make sure the parport mode is set to EPP, not >ECP! I heard several times that this is the cause for stretched or shifted >image lines. > You were right my BIOS was configured with ECP+EPP I leave it as EPP and the image was not stretched neither shifted. >By the way: switching off the backend calibration has a negative side effect: >you will probably see fine vertical stripes on your scanned images. Normally >the backend calibration gets rid of it, but it looks like we have to find the >bug in the calibration code so that it works with your scanner. Please tell >me if we shall do some work in this direction - I'll need some testing work >on your side to achieve this. > I noticed,as you said, that there are some fine vertical stripes on the scanned images. I am willing to help in what ever you need to fix this problem. Just tell me what to do. >Could you please tell me what error message appears if you use the '-y20' >option to generate a logfile? > Well this error appeared when I was looking for help in the suse mailing list, then they told me to post my problem in the sane development list. In the log file I sent they told me there was the following line: scanimage: argument without option: `y20' However, I ran it again exactly as before and I was looking for that line and I don't find it. I attached the zip file with the scanned image, the new log file and the config file. I hope this will help in something, tell me what you need I and will be glad to help. Thanks Jose -------------- next part -------------- A non-text attachment was scrubbed... Name: output.tar.gz Type: application/x-gunzip Size: 3328 bytes Desc: not available URL: From jb at jblache.org Tue Jun 3 17:11:32 2003 From: jb at jblache.org (Julien BLACHE) Date: Tue, 03 Jun 2003 18:11:32 +0200 Subject: [sane-devel] backends 1.0.12 compile-error In-Reply-To: <3EDC8673.7060601@sbox.tugraz.at> (Gerfried Maier's message of "Tue, 03 Jun 2003 13:28:51 +0200") References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <87brxfxz56.fsf@frigate.technologeek.org> <3EDC8673.7060601@sbox.tugraz.at> Message-ID: <87y90jw37v.fsf@frigate.technologeek.org> Gerfried Maier wrote: >>If you do not need IPv6 support, configure sane-backends with >>--disable-ipv6 and it'll build fine. > > Unfortunately not. Same error. Oh, yes, sorry. My bad. Well, has Henning said, this is a bug in certain versions of the libc, as the relevant RFCs document a ss_family member in struct sockaddr storage. Comment the definition of SANE_USES_AF_INDEP in saned.c, and it'll fall back to the IPv4-only code, which do not use this particular structure. You may need to do the same in backend/net.c. I'll look into adding a check to configure. JB. -- Julien BLACHE From jb at jblache.org Tue Jun 3 17:46:37 2003 From: jb at jblache.org (Julien BLACHE) Date: Tue, 03 Jun 2003 18:46:37 +0200 Subject: [sane-devel] [PATCH] backends 1.0.12 compile-error In-Reply-To: (Erik Inge Bols's message of "Tue, 3 Jun 2003 13:46:19 +0200 (CEST)") References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC85C3.4040309@sbox.tugraz.at> Message-ID: <87u1b7w1le.fsf_-_@frigate.technologeek.org> Erik Inge Bols? wrote: > ... anyone feel like adding a configure check and a patch for this? > Probably a certain libc or a certain distro has this problem. Patch attached. Apply, run aclocal, autoconf, autoheader. Maybe I should ask for cvs write access, someday :) JB. -- Julien BLACHE -------------- next part -------------- --- sane-backends-1.0.12.orig/acinclude.m4 2003-05-15 12:51:16.000000000 +0200 +++ sane-backends-1.0.12/acinclude.m4 2003-06-03 18:34:09.000000000 +0200 @@ -353,6 +353,7 @@ # # Check for AF_INET6, determines whether or not to enable IPv6 support +# Check for ss_family member in struct sockaddr_storage AC_DEFUN([SANE_CHECK_IPV6], [ AC_MSG_CHECKING([whether to enable IPv6]) @@ -383,6 +384,38 @@ ipv6=no ]) fi + + if test "$ipv6" != "no" ; then + AC_MSG_CHECKING([whether struct sockaddr_storage has an ss_family member]) + AC_TRY_COMPILE([ + #define INET6 + #include + #include ], [ + /* test if the ss_family member exists in struct sockaddr_storage */ + struct sockaddr_storage ss; + ss.ss_family = AF_INET; + exit (0); + ], [ + AC_MSG_RESULT(yes) + AC_DEFINE([HAS_SS_FAMILY], 1, [Define to 1 if struct sockaddr_storage has an ss_family member]) + ], [ + AC_TRY_COMPILE([ + #define INET6 + #include + #include ], [ + /* test if the __ss_family member exists in struct sockaddr_storage */ + struct sockaddr_storage ss; + ss.__ss_family = AF_INET; + exit (0); + ], [ + AC_MSG_RESULT([no, but __ss_family exists]) + AC_DEFINE([HAS___SS_FAMILY], 1, [Define to 1 if struct sockaddr_storage has __ss_family instead of ss_family]) + ], [ + AC_MSG_RESULT([no]) + ipv6=no + ]) + ]) + fi ]) # --- sane-backends-1.0.12.orig/frontend/saned.c 2003-05-12 18:34:03.000000000 +0200 +++ sane-backends-1.0.12/frontend/saned.c 2003-06-03 18:39:11.000000000 +0200 @@ -34,6 +34,14 @@ #if defined(HAVE_GETADDRINFO) && defined (HAVE_GETNAMEINFO) # define SANED_USES_AF_INDEP +# ifdef HAS_SS_FAMILY +# define SS_FAMILY(ss) ss.ss_family +# elif defined(HAS___SS_FAMILY) +# define SS_FAMILY(ss) ss.__ss_family +# else /* fallback to the old, IPv4-only code */ +# undef SANED_USES_AF_INDEP +# undef ENABLE_IPV6 +# endif #else # undef ENABLE_IPV6 #endif /* HAVE_GETADDRINFO && HAVE_GETNAMEINFO && HAVE_POLL */ @@ -556,7 +564,7 @@ sin = (struct sockaddr_in *) &remote_address; - switch (remote_address.ss_family) + switch (SS_FAMILY(remote_address)) { case AF_INET: if (IN_LOOPBACK (ntohl (sin->sin_addr.s_addr))) @@ -1022,7 +1030,7 @@ return -1; } - fd = socket (ss.ss_family, SOCK_STREAM, 0); + fd = socket (SS_FAMILY(ss), SOCK_STREAM, 0); if (fd < 0) { DBG (DBG_ERR, "start_scan: failed to obtain data socket (%s)\n", @@ -1031,7 +1039,7 @@ return -1; } - switch (ss.ss_family) + switch (SS_FAMILY(ss)) { case AF_INET: sin = (struct sockaddr_in *) &ss; @@ -1071,7 +1079,7 @@ return -1; } - switch (ss.ss_family) + switch (SS_FAMILY(ss)) { case AF_INET: sin = (struct sockaddr_in *) &ss; From JayGuerette at pobox.com Tue Jun 3 17:57:29 2003 From: JayGuerette at pobox.com (Jay Guerette) Date: Tue, 03 Jun 2003 12:57:29 -0400 (EDT) Subject: [sane-devel] Analysis of saned CPU utilization Message-ID: <30058.209.202.195.145.1054659449.squirrel@mail.guerette.net> First off, my deep thanks to everyone who has made sane possible. I am ecstatic that I can use my scanner on my Linux box, and also make it available to Windows clients over my network. I've experienced, and seen a few references to similar experiences on the web, saned consuming all available CPU when in use. After running a strace while it was doing this, and examining the source to saned, it appears that it is locked in a tight select loop with no timeout. It is definately not the ideal way to poll for data, and at the very least there should be a short timeout to release CPU cycles to other processes. Was this a deliberate design choice? If it is a flaw, what is the best way to get it fixed? Should I fix it and submit a patch, or try to take it up with whomever maintains that particular frontend? Regards, Jay Guerette From fzago at austin.rr.com Tue Jun 3 13:09:50 2003 From: fzago at austin.rr.com (Frank Zago) Date: Tue, 03 Jun 2003 07:09:50 -0500 Subject: [sane-devel] Compiling SANE backends on Mac OS X 10.1.5 In-Reply-To: <20030603043000.5308.qmail@web13404.mail.yahoo.com> References: <20030603043000.5308.qmail@web13404.mail.yahoo.com> Message-ID: <3EDC900E.2050409@austin.rr.com> I'm not an OSX user, but it seems this (sick pice of) code needs to be compiled with a C++ compiler, or at least a C compiler with non-standard extensions. You can try CC=g++ ./configure and recompile. Frank. David Alan Hjelle wrote: > Hello. > > I've been trying to get my Microtek SlimScan C6 cheap-o scanner to work > under Mac OS X for a while now, and just recently ran across SANE. I > figure I should be able to use SANE with the GIMP, which I use somewhat > regularly. > > I was trying to compile the lastest CVS snapshot (from June 2, 2003) of > SANE backends, but I ran into some problems. > > ./configure ran no problem. > > make, however, eventually gave me the following errors (Or, at least, > these are the errors deaing with the sanei_scsi.c file that seemed to > be the cause for the compilation problem. I think everything else was > just warnings. Of course, what do I know? I'm only just teaching myself > C programming and have only had experience in VB and Java .): > From henning at meier-geinitz.de Tue Jun 3 20:34:22 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 3 Jun 2003 21:34:22 +0200 Subject: [sane-devel] [PATCH] backends 1.0.12 compile-error In-Reply-To: <87u1b7w1le.fsf_-_@frigate.technologeek.org> References: <3EDC515B.8050706@sbox.tugraz.at> <20030603090720.GA10945@svana.org> <3EDC6A00.90907@sbox.tugraz.at> <3EDC85C3.4040309@sbox.tugraz.at> <87u1b7w1le.fsf_-_@frigate.technologeek.org> Message-ID: <20030603193422.GA1001@hmg1> Hi, On Tue, Jun 03, 2003 at 06:46:37PM +0200, Julien BLACHE wrote: > Patch attached. Apply, run aclocal, autoconf, autoheader. I'll have a look at this one later. > Maybe I should ask for cvs write access, someday :) Good idea :-) bye, Henning From stef-listes at wanadoo.fr Tue Jun 3 23:49:01 2003 From: stef-listes at wanadoo.fr (stef) Date: Tue, 3 Jun 2003 22:49:01 +0000 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org In-Reply-To: <3EDB6ACF.3010304@charter.net> References: <3EDB6ACF.3010304@charter.net> Message-ID: <20030603224901.GA931@wanadoo.fr> On Mon, Jun 02, 2003 at 10:18:39AM -0500, Howard Shane wrote: > I would like to announce the completion of the initial draft of the > Scanner-HOWTO for the linux documentation project, and invite > participants on the SANE-devel mailing list to comment on it. > > The goal of this document is to bridge point A (scanner) to point B > (scanner running successfully in linux) for the relative newbie as > efficiently as possible. As such it should not be too technical, it > should cover the most common hardware interface types, the required > steps to reach a working result, likely pitfalls and how to recover from > them, and places to go for help. It is not designed to be an exaustive > list of harware in/compatibilities. > > Any help you can suggest to clarify or otherwise improve the draft will > be greatly appreciated and may even result in you being mentioned in the > credits if you so desire. > > The document can be found at: > > http://ibiblio.org/gferg/ldp/Scanner-HOWTO.html > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel Hello, I've parsed it a bit, and I must say that you're painting the picture darker than it really is for parallel port scanners. Parallel port scanners listed in SANE do work. No need to frighten people. I'm a bit skeptic about favouring ECP mode. It may be wise for printers, but I think it is useless for scanners, unless you use some patch that bring DMA reads. From a quick grep in SANE docs, EPP or ECP/EPP seems to be the recommended setting. By the way, an EPP scan is way faster than PS/2 or bidirectional mode. Also, I don't think unidirectional mode is suitable for scanning. Regards, Stef From jb at jblache.org Tue Jun 3 21:58:35 2003 From: jb at jblache.org (Julien BLACHE) Date: Tue, 03 Jun 2003 22:58:35 +0200 Subject: [sane-devel] Analysis of saned CPU utilization In-Reply-To: <30058.209.202.195.145.1054659449.squirrel@mail.guerette.net> (Jay Guerette's message of "Tue, 03 Jun 2003 12:57:29 -0400 (EDT)") References: <30058.209.202.195.145.1054659449.squirrel@mail.guerette.net> Message-ID: <87llwix4hw.fsf@frigate.technologeek.org> Jay Guerette wrote: > I've experienced, and seen a few references to similar experiences on the > web, saned consuming all available CPU when in use. > > After running a strace while it was doing this, and examining the source > to saned, it appears that it is locked in a tight select loop with no > timeout. Could you give some more details ? select() is only used once in the code (not counting the poll() in main(), or the select() that's used instead on platforms where poll() doesn't exist -- that's for 1.0.12). A testcase would be nice. To answer your question, patches are always welcome :) JB. -- Julien BLACHE From fbakan at gmx.net Tue Jun 3 22:20:04 2003 From: fbakan at gmx.net (Franz Bakan) Date: Tue, 03 Jun 2003 23:20:04 +0200 (CEST) Subject: [sane-devel] compile 1.0.12 on OS/2 In-Reply-To: <20030530145329.GC3433@hmg1> Message-ID: <20030603212008.5D8E0E9E@panda.mostang.com> Hi, On Fri, 30 May 2003 16:53:29 +0200, Henning Meier-Geinitz wrote: >> 1.0.12 configures and compiles fine on OS/2 with gcc 2.8.1 as well as with gcc 3.2.1. > >Nice. The current entry on the platforms list is for "OS/2 4.5 >(eComStation)". Is this still correct? Yes >USB isn't supported? There is some support. One guy in Japan (Maeda Haruyuki) managed to compile a version that has been reported to work with some epson-usb-scanners on OS/2. He used the sane-sources for his special build with some OS/2 specific changes. He compiled not with gcc but with IBM VAC++. The binaries are bundled with the TAME-frontend for OS/2 (not a 'real' frontend but a rexx-pm-gui that calls scanimage.exe at the end). See http://www.os2world.com/goran/tame.htm >What about >dynamic loading of shared libraries? I don't know, I don't exactly know what this means. Can DLLs (_dynamic_ linked libraries) be loaded _static_? On OS/2 we have just one (big) libsane.dll that contains all backends-code and works together with (small) scanimage.exe xscanimage.exe xsane.exe etc. These exes won't start if libsane.dll is not found. >> there is probably an error in line 2623 of >> sane-backends/po/sane-backends.fr.po >> that prevents iconv from recoding this file to ISO-8859-1 after this line. > >Thanks. Fixed in CVS. There was one more occurance of a wrongly >encoded "?". Thanks, I now just uploaded a binary-os/2-package of the 1.0.12/1.0.11 backend-frontend combination including this minor fix to http://home.tiscalinet.de/fbakan Bye, Franz From peter at pscomp.com Wed Jun 4 02:19:12 2003 From: peter at pscomp.com (Peter Santoro) Date: Tue, 03 Jun 2003 21:19:12 -0400 Subject: [sane-devel] Re: epson: scanimage threshold option not working in 1.0.12 backend Message-ID: <3EDD4910.5000002@pscomp.com> Karl, I also noticed that Epson's ISCAN GUI no longer works after installing the SANE 1.0.12 backend. ISCAN has a setting for threshold, so it is probably the same bug. Using scanimage directly (not via my code) only works if the threshold option is not used, so I doubt it's my code. Also, "scanimage --help" shows that the threshold option is inactive, so the problem is probably somewhere in the initialization code. BTW, I'm using kernel 2.4.20 (RedHat 7.3 and Slackware 8.1) and USB 1.1. Peter From JayGuerette at pobox.com Wed Jun 4 13:54:35 2003 From: JayGuerette at pobox.com (Jay Guerette) Date: Wed, 04 Jun 2003 08:54:35 -0400 (EDT) Subject: [sane-devel] Analysis of saned CPU utilization In-Reply-To: <87llwix4hw.fsf@frigate.technologeek.org> References: <30058.209.202.195.145.1054659449.squirrel@mail.guerette.net> <87llwix4hw.fsf@frigate.technologeek.org> Message-ID: <1329.10.0.1.10.1054731275.squirrel@mail.guerette.net> >> I've experienced, and seen a few references to similar experiences on >> the web, saned consuming all available CPU when in use. >> >> After running a strace while it was doing this, and examining the >> source to saned, it appears that it is locked in a tight select loop >> with no timeout. > > Could you give some more details ? select() is only used once in the > code (not counting the poll() in main(), or the select() that's used > instead on platforms where poll() doesn't exist -- that's for 1.0.12). > > A testcase would be nice. I'll play with the code a bit, and come up with more detail. From keeper at neo.rr.com Wed Jun 4 10:49:00 2003 From: keeper at neo.rr.com (Michael Rasile) Date: Wed, 4 Jun 2003 09:49:00 +0000 Subject: [sane-devel] Canon Lide 30 backend Message-ID: <20030604094900.GA7629@watcher.WorkGroup> Greetings! Am trying to get my USB canon Lide 30 scanner to work under Gentoo. USB has been compiled into the kernel and when I do sane-find-scanner, the scanner is found. However, when I do scanimage -L the scanner is not found and therefore I am unable to use xsane. I was wondering what backend I should be using for this scannerand how should this be setup in /etc/sane.d/ I have tried everything, editing the canon.conf and the plustek.conf. I know the scanner works because when I was using Mandrake 9.1 I didn't have a problem setting it up. I would like to continue to use it under Gentoo. Any suggestions will be greatly appreciated. I've read a great deal about this, but nothing seems to help. Thanks for anything. -- Regards, Mike keeper at neo.rr.com "Don't Fear The Penguin." From christoph.bier at web.de Wed Jun 4 17:37:04 2003 From: christoph.bier at web.de (Christoph Bier) Date: Wed, 04 Jun 2003 18:37:04 +0200 Subject: [sane-devel] Mustek BearPaw 2400 CU plus: now I'm totally confused (was: suddenly problems opening /dev/usbscanner0) In-Reply-To: <20030603092448.GA5732@hmg1> References: <20030602111526.5b4034a3.christoph.bier@web.de> <20030602135832.GA30314@meier-geinitz.de> <20030602174212.0ce77aa9.christoph.bier@web.de> <20030603092448.GA5732@hmg1> Message-ID: <3EDE2030.9080306@web.de> Henning Meier-Geinitz schrieb: [. . .] > Oh well. Either a hardware problem (too slow to react?) or a kernel > bug. Check the linux-usb-users mailing list for this one, I remeber I did so. > that other people had similar problems, but not with scanners. Maybe > that's a problem with your USB chipset, but I don't remeber the > details. It doesn't seem to be an issue of the scanner module or sane. Ok. [. . .] >>Is there a possibility to turn such "hotplugging >>magic" off? > > Yes :-) For the details, consult your distribution's documentation. A Ok, thanks :-). > rather drasti way is to renam the /sbin/hotplug program to something > else. Thanks again for your help! Greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier at wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From henning at meier-geinitz.de Wed Jun 4 19:09:34 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 4 Jun 2003 20:09:34 +0200 Subject: [sane-devel] compile 1.0.12 on OS/2 In-Reply-To: <20030603212008.5D8E0E9E@panda.mostang.com> References: <20030530145329.GC3433@hmg1> <20030603212008.5D8E0E9E@panda.mostang.com> Message-ID: <20030604180934.GA3795@hmg1> Hi, On Tue, Jun 03, 2003 at 11:20:04PM +0200, Franz Bakan wrote: > >USB isn't supported? > > There is some support. Thanks for the information. I'll add links and update the list. > >What about > >dynamic loading of shared libraries? > > I don't know, I don't exactly know what this means. > > Can DLLs (_dynamic_ linked libraries) be loaded _static_? The dll backend can either load other backends dynamically (on demand) or all the backends are linked into sane-dll (preloading). Last but not least sane-dll can be linked statically to the frontends (inclusing all the preloaded backends). > On OS/2 we have just one (big) libsane.dll that contains all backends-code > and works together with (small) scanimage.exe xscanimage.exe xsane.exe etc. That's shared but not dynamic. Bye, Henning From henning at meier-geinitz.de Wed Jun 4 19:17:53 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 4 Jun 2003 20:17:53 +0200 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030604094900.GA7629@watcher.WorkGroup> References: <20030604094900.GA7629@watcher.WorkGroup> Message-ID: <20030604181753.GB3795@hmg1> Hi, On Wed, Jun 04, 2003 at 09:49:00AM +0000, Michael Rasile wrote: > Am trying to get my USB canon Lide 30 scanner to work under Gentoo. The Lide 30 is supported by the plustek backend. > USB has been compiled into the kernel and when I do > sane-find-scanner, the scanner is found. However, when I do scanimage > -L the scanner is not found and therefore I am unable to use xsane. Try "SANE_DEBUG_PLUSTEK=255 scanimage -L" to find out what's wrong. > I > was wondering what backend I should be using for this scannerand how > should this be setup in /etc/sane.d/ The plustek backend is the right one. You can find out about which scanner is supported by which backend by using the scanner search engine: http://sane.informatik.uni-freiburg.de/cgi-bin/driver.pl The setup of the config file is explained in man sane-plustek. But ususally this should work without manual intervention. Also check that "plustek" is in dll.conf. Bye, Henning From henning at meier-geinitz.de Wed Jun 4 19:35:44 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 4 Jun 2003 20:35:44 +0200 Subject: [sane-devel] Please test sane-backends (and sane-frontends) on non-mainstream os and platforms Message-ID: <20030604183544.GC3795@hmg1> Hi, I'd like to update the list of platforms SANE can be compiled and used on. There is a temporary file with the latest updates here: http://www.meier-geinitz.de/sane/tmp/sane-support.html If you've successfully compiled and/or tested sane-backends 1.0.12 and/or sane-frontends-1.0.11 on any of the mentioned platforms that isn't up-to-date yet, please contact us. Also if the platform is mentioned, but there is a question mark for SCSI or USB support, please tell us if you were able to actually scan with a real scanner. If you have access to a platform but it has no scanner please try at least the test backend: "scanimage -d test -T". Any other corrections or additions are also welcome. Thanks, Henning From soumarmt at nerim.net Wed Jun 4 20:57:27 2003 From: soumarmt at nerim.net (Thomas Soumarmon) Date: Wed, 4 Jun 2003 21:57:27 +0200 Subject: [sane-devel] CVS freeze ? Message-ID: <200306042157.27319.soumarmt@nerim.net> Hi everybody, Sorry for the silly question but I have been a bit SANE-offline for a while, and I didn't find quickly the answer in the mail archive. I wanted to commit into CVS some changes about the hp5400 backend. Is there a CVS freeze at the moment or may I do it ? And before that, is there a compile farm or some kind of, to verify at least it compiles ok on various platforms before commiting it ? Thomas. PS : changes are not functional, they are "only" to make a synchronization between hp5400backend sourceforge CVS project and SANE CVS project. PS2: I have been messing around a lot before finding the DEBUG_NOT_STATIC trick to avoid the missing symbol sane_debug_hp5400_call !!! From jb at jblache.org Wed Jun 4 21:22:59 2003 From: jb at jblache.org (Julien BLACHE) Date: Wed, 04 Jun 2003 22:22:59 +0200 Subject: [sane-devel] CVS freeze ? In-Reply-To: <200306042157.27319.soumarmt@nerim.net> (Thomas Soumarmon's message of "Wed, 4 Jun 2003 21:57:27 +0200") References: <200306042157.27319.soumarmt@nerim.net> Message-ID: <87el29384c.fsf@frigate.technologeek.org> Thomas Soumarmon wrote: > I wanted to commit into CVS some changes about the hp5400 backend. > Is there a CVS freeze at the moment or may I do it ? The freeze is over :) > And before that, is there a compile farm or some kind of, to verify at least > it compiles ok on various platforms before commiting it ? SF.net has a compile farm (never used it), otherwise there's the HP/Compaq testdrive (http://testdrive.hp.com) but Henning knows more about this one than I do :) JB. -- Julien BLACHE From henning at meier-geinitz.de Wed Jun 4 21:25:28 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 4 Jun 2003 22:25:28 +0200 Subject: [sane-devel] CVS freeze ? In-Reply-To: <200306042157.27319.soumarmt@nerim.net> References: <200306042157.27319.soumarmt@nerim.net> Message-ID: <20030604202528.GH3795@hmg1> Hi, On Wed, Jun 04, 2003 at 09:57:27PM +0200, Thomas Soumarmon wrote: > Sorry for the silly question but I have been a bit SANE-offline for a while, > and I didn't find quickly the answer in the mail archive. Search for "release" and/or freeze in the archive. Or check the Changelog in CVS for messages like this: ****** Release of sane-backends 1.0.12. End of code freeze ****** > I wanted to commit into CVS some changes about the hp5400 backend. > Is there a CVS freeze at the moment or may I do it ? You can commit whatever you want :-) By the way, I changed backend/Makefile.in to not link hp5400 to sanei_config2.lo. That shouldn't affect your backend because you don't use that code at all. > And before that, is there a compile farm or some kind of, to verify > at least it compiles ok on various platforms before commiting it ? If you like, you can use the Hewlett Packard test drive at testdrive.hp.com. They have several Linux, *BSD, Tru64, and HP/UX machines. But setting this up to work at least semi-automatically requires quite some work and some non-linux Unix knowledge :-/ So if you don't want to invest some time into learning how crappy^h^h^h^h^h^h differnt from Linux some systems are, compiling with Linux (and maybe a BSD if you have it) is ok. I'm using the testdrive from time to time and will complain if something doesn't work. > PS2: I have been messing around a lot before finding the DEBUG_NOT_STATIC > trick to avoid the missing symbol sane_debug_hp5400_call !!! The debug macros ARE complex if you use more than one compilation unit. Bye, Henning From lee at trueskill.com Wed Jun 4 23:14:27 2003 From: lee at trueskill.com (Lee Morgan) Date: Wed, 4 Jun 2003 18:14:27 -0400 Subject: [sane-devel] ScanJet 4100C Message-ID: <200306041814.30374.lee@trueskill.com> Hello, I have RedHat 8.0 installed, when I run scanimage I get the following result: [root at shodan sane.d]# scanimage -d hp:/dev/usb/scanner0 scanimage: open of device hp:/dev/usb/scanner0 failed: Invalid argument I have compiled and installed sane-backends-1.0.12 and used the sane-1.0.9.hp.1.01 source. The scanner is detected at /dev/usb/scanner0: [root at shodan sane.d]# sane-find-scanner # Note that sane-find-scanner will find any scanner that is connected # to a SCSI bus and some scanners that are connected to the Universal # Serial Bus (USB) depending on your OS. It will even find scanners # that are not supported at all by SANE. It won't find a scanner that # is connected to a parallel or proprietary port. # If your scanner uses SCSI, you must have a driver for your SCSI # adapter and support for SCSI Generic (sg) in your Operating System # in order for the scanner to be used with SANE. If your scanner is # NOT listed above, check that you have installed the drivers. sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0101) at device /dev/usb/scanner0 But the product string is not reported when i cat /proc/bus/usb/devices: T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0101 Rev= 1.00 S: SerialNumber=00MY8BH535KN C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=usbscanner E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms The scanner is a ScanJet4100C. Where am I going wrong? Is this a problem with the scanimage? Regards, Lee From peter at kirchgessner.net Thu Jun 5 05:57:27 2003 From: peter at kirchgessner.net (Peter Kirchgessner) Date: Thu, 05 Jun 2003 06:57:27 +0200 Subject: [sane-devel] ScanJet 4100C References: <200306041814.30374.lee@trueskill.com> Message-ID: <3EDECDB7.6090105@kirchgessner.net> Hi Lee, sane-backends-1.0.12 has the more current backend than sane-1.0.9.hp.1.01. But in your case it should make no difference. Please have a look at your /usr/local/etc/sane.d/hp.conf. It should have lines with # HP ScanJet 4100C usb 0x03f0 0x0101 You can also activate the lines /dev/usb/scanner0 option connect-device if the scanner is not recognized automatically. And please check which libraries are used. The libraries at /usr/lib/sane maybe the libraries which have been installed by your RedHat distribution. And at /usr/local/lib/sane your compiled libraries may be placed. Sincerely Peter Then libusb should find Lee Morgan schrieb: > Hello, > > I have RedHat 8.0 installed, when I run scanimage I get the following result: > > [root at shodan sane.d]# scanimage -d hp:/dev/usb/scanner0 > scanimage: open of device hp:/dev/usb/scanner0 failed: Invalid argument > > I have compiled and installed sane-backends-1.0.12 and used the > sane-1.0.9.hp.1.01 source. > > The scanner is detected at /dev/usb/scanner0: > > [root at shodan sane.d]# sane-find-scanner > # Note that sane-find-scanner will find any scanner that is connected > # to a SCSI bus and some scanners that are connected to the Universal > # Serial Bus (USB) depending on your OS. It will even find scanners > # that are not supported at all by SANE. It won't find a scanner that > # is connected to a parallel or proprietary port. > > # If your scanner uses SCSI, you must have a driver for your SCSI > # adapter and support for SCSI Generic (sg) in your Operating System > # in order for the scanner to be used with SANE. If your scanner is > # NOT listed above, check that you have installed the drivers. > > sane-find-scanner: found USB scanner (vendor = 0x03f0, product = 0x0101) at > device /dev/usb/scanner0 > > But the product string is not reported when i cat /proc/bus/usb/devices: > > T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=03f0 ProdID=0101 Rev= 1.00 > S: SerialNumber=00MY8BH535KN > C:* #Ifs= 1 Cfg#= 1 Atr=60 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=usbscanner > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 16 Ivl=0ms > E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms > > The scanner is a ScanJet4100C. > > Where am I going wrong? Is this a problem with the scanimage? > > Regards, > > Lee > > > > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- Peter Kirchgessner http://www.kirchgessner.net mailto:peter at kirchgessner.net From henning at meier-geinitz.de Thu Jun 5 11:06:32 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 12:06:32 +0200 Subject: [sane-devel] CVS freeze ? In-Reply-To: <200306042157.27319.soumarmt@nerim.net> References: <200306042157.27319.soumarmt@nerim.net> Message-ID: <20030605100632.GA22362@hmg1> Hi, On Wed, Jun 04, 2003 at 09:57:27PM +0200, Thomas Soumarmon wrote: > Sorry for the silly question but I have been a bit SANE-offline for a while, > and I didn't find quickly the answer in the mail archive. By the way: Please summarize your changes in the "ChangeLog" file. See http://www.student.uit.no/~pere/linux/sane/cvs-server.html . Bye, Henning From henning at meier-geinitz.de Thu Jun 5 11:25:44 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 12:25:44 +0200 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 Message-ID: <20030605102544.GB11876@hmg1> Hi, Some people reported kernel USB timeouts with their gt68xx based scanners, e.g. Plustek 1247 or Mustek BearPaw series. This seems to be caused by the check if the firmware is already loaded in the gt68xx backend. I've disabled this check for now. If you encounter this problem, get the latest backend (at least 1.0-47) or an unofficial snapshot from http://www.meier-geinitz.de/sane/gt68xx-backend/ . I'll attach a patch against 1.0.12 that contains the work-around. Bye, Henning Index: backend/gt68xx.c =================================================================== RCS file: /cvsroot/external/sane/sane-backends/backend/gt68xx.c,v retrieving revision 1.20 retrieving revision 1.21 diff -u -u -r1.20 -r1.21 --- backend/gt68xx.c 27 Apr 2003 12:43:43 -0000 1.20 +++ backend/gt68xx.c 5 Jun 2003 09:58:45 -0000 1.21 @@ -48,7 +48,7 @@ #include "../include/sane/config.h" -#define BUILD 46 +#define BUILD 47 #define MAX_DEBUG #define WARMUP_TIME 30 #define CALIBRATION_HEIGHT 2.5 @@ -1245,12 +1245,13 @@ DBG (0, " details as possible, e.g. the exact name of your\n"); DBG (0, " scanner and what does (not) work.\n"); } - RIE (gt68xx_device_check_firmware (dev, &firmware_loaded)); + /* RIE (gt68xx_device_check_firmware (dev, &firmware_loaded));*/ + firmware_loaded = SANE_FALSE; if (firmware_loaded) DBG (3, "sane_open: firmware already loaded, skipping load\n"); else RIE (download_firmware_file (dev)); - RIE (gt68xx_device_check_firmware (dev, &firmware_loaded)); + /* RIE (gt68xx_device_check_firmware (dev, &firmware_loaded));*/ if (!firmware_loaded) { DBG (1, "sane_open: firmware still not loaded? Proceeding anyway\n"); From rsv869 at adelphia.net Fri Jun 6 04:53:02 2003 From: rsv869 at adelphia.net (Reid Vail) Date: Thu, 05 Jun 2003 23:53:02 -0400 Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <3E02B406.7010801@kirchgessner.net> References: <3E02AB22.2010409@adelphia.net> <3E02B406.7010801@kirchgessner.net> Message-ID: <3EE0101E.6010604@adelphia.net> About six months ago Peter gave me some advice about my HP6350c scanner. It fixed my issue and got it working. (I included that exchange at the bottom of this message). Recently I upgraded my Suse box to Suse 8.2 and it's not working again. I dug out the mail and checked the config. Looks OK to me, and I included a few scraps. I've included the output from sane-find-scanner. The permissions also look OK, too, I think. Any suggestions would be great. thx Reid reid at linux:~>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=0x03f0, product=0x0601) at libusb:001:002 # A USB device was detected. This program can't be sure if it's really # a scanner. If it is your scanner, 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. reid at linux:/etc/sane.d> ls -l hp.conf -rwxrwxrwx 1 root root 480 2003-06-05 21:14 hp.conf reid at linux:~> ls -l /etc/sane.d/dll.conf -rw-rw-rw- 1 root root 448 2002-12-18 00:16 /etc/sane.d/dll.conf dll.conf . . # dc210 # dc240 # dc25 # dll # dmc # epson hp # fujitsu # leo # microtek # microtek2 # mustek_usb # mustek # matsushita . . reid at linux:/etc/sane.d> more hp.conf #scsi HP # Uncomment the following if you have "Error during device I/O" on SCSI # option dumb-read # # The usual place for a SCSI-scanner on Linux # # USB-scanners supported by the hp-backend # HP ScanJet 4100C usb 0x03f0 0x0101 # HP ScanJet 5200C usb 0x03f0 0x0401 # HP ScanJet 62X0C usb 0x03f0 0x0201 # HP ScanJet 63X0C usb 0x03f0 0x0601 # # Uncomment the following if your scanner is connected by USB, # but you are not using libusb /dev/usb/scanner option connect-device reid at linux:/etc/sane.d> Peter Kirchgessner wrote: > Hi, > > pleae have a look at /etc/sane.d/hp.conf or > /usr/local/etc/sane.d/hp.conf. It must have two lines in it: > > /dev/usbscanner > option connect-device > > In dll.conf (same directories) the line with "hp" must be active. > You may need to set the permissions: > > chmod 666 /dev/usbscanner > > More hints can be found at http://www.kirchgessner.net/sanehpfaq.html > > Sincerely > > Peter > > Reid Vail schrieb: > >> I've been trying for a least a month to get an HP6350c USB Scanjet to >> work. I'm running a SuSE 8.1 Personal distro, which comes with a SANE >> implementation of 1.0.8-47. >> >> I think (but can't say for sure) that some part of the install of the >> unit (via YAST) isn't working because it doesn't even "test" >> correctly. However YAST does correctly identify it. >> >> When I run xscanimage I get this output: >> >> [xscanimage] No scanners were identified. If you were expecting >> something different, check that the scanner is plugged in, turned on and >> detected by sane-find-scanner (if appropriate). Please read the >> documentation which came with this software (README, FAQ, manpages). >> >> But when I run sane-find-scanner I get this output: >> >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = >> 0x0601) at device /dev/usb/scanner0 >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = >> 0x0601) at device /dev/usbscanner >> >> I make no claims that I'm not missing something obvious! I just >> don't get it. For what it's worth, I know the unit works because it >> runs under Windoze 2K. >> >> Thanks in advance. >> >> Reid Vail >> >> _______________________________________________ >> Sane-devel mailing list >> Sane-devel at www.mostang.com >> http://www.mostang.com/mailman/listinfo/sane-devel >> > > From henning at meier-geinitz.de Thu Jun 5 18:37:33 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 19:37:33 +0200 Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <3EE0101E.6010604@adelphia.net> References: <3E02AB22.2010409@adelphia.net> <3E02B406.7010801@kirchgessner.net> <3EE0101E.6010604@adelphia.net> Message-ID: <20030605173733.GB779@hmg1> Hi, On Thu, Jun 05, 2003 at 11:53:02PM -0400, Reid Vail wrote: > found USB scanner (vendor=0x03f0, product=0x0601) at libusb:001:002 So it's detected by libusb. It's not found by the kernel USB scanner driver. But that's ok. Just make sure that the permissions are ok (see man sane-usb). > reid at linux:/etc/sane.d> more hp.conf [...] > # HP ScanJet 63X0C > usb 0x03f0 0x0601 These "usb" lines should be enough to detect your scanner. > # Uncomment the following if your scanner is connected by USB, > # but you are not using libusb "but you are not using libusb". But you do! > /dev/usb/scanner > option connect-device So I don't think this entry is necessary. Do "SANE_DEBUG_HP=255 scanimage -L" to find out what's going on. Bye, Henning From anoah at pfeiffer.edu Thu Jun 5 19:02:08 2003 From: anoah at pfeiffer.edu (m. allan noah) Date: Thu, 5 Jun 2003 14:02:08 -0400 (EDT) Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <3EE0101E.6010604@adelphia.net> Message-ID: if you access the scanner via the /dev/* files under linux, you will need the scanner module inserted in your kernel. try 'insmod scanner' as root, then try sane-find-scanner again. currently, your system is accessing the scanner via libusb, if you wish to keep that instead, comment out the lines in the hp.conf that specify the /dev/ device (whether or not the hp driver works with libusb, i cant say, as i use mine via scsi.) allan On Thu, 5 Jun 2003, Reid Vail wrote: > About six months ago Peter gave me some advice about my HP6350c > scanner. It fixed my issue and got it working. (I included that > exchange at the bottom of this message). Recently I upgraded my Suse > box to Suse 8.2 and it's not working again. I dug out the mail and > checked the config. Looks OK to me, and I included a few scraps. I've > included the output from sane-find-scanner. The permissions also look > OK, too, I think. Any suggestions would be great. > > thx > > Reid > > reid at linux:~>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=0x03f0, product=0x0601) at libusb:001:002 > # A USB device was detected. This program can't be sure if it's really > # a scanner. If it is your scanner, 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. > > > > reid at linux:/etc/sane.d> ls -l hp.conf > -rwxrwxrwx 1 root root 480 2003-06-05 21:14 hp.conf > > reid at linux:~> ls -l /etc/sane.d/dll.conf > -rw-rw-rw- 1 root root 448 2002-12-18 00:16 > /etc/sane.d/dll.conf > > > dll.conf > . > . > # dc210 > # dc240 > # dc25 > # dll > # dmc > # epson > hp > # fujitsu > # leo > # microtek > # microtek2 > # mustek_usb > # mustek > # matsushita > . > . > > > > reid at linux:/etc/sane.d> more hp.conf > #scsi HP > # Uncomment the following if you have "Error during device I/O" on SCSI > # option dumb-read > # > # The usual place for a SCSI-scanner on Linux > # > # USB-scanners supported by the hp-backend > # HP ScanJet 4100C > usb 0x03f0 0x0101 > # HP ScanJet 5200C > usb 0x03f0 0x0401 > # HP ScanJet 62X0C > usb 0x03f0 0x0201 > # HP ScanJet 63X0C > usb 0x03f0 0x0601 > # > # Uncomment the following if your scanner is connected by USB, > # but you are not using libusb > /dev/usb/scanner > option connect-device > reid at linux:/etc/sane.d> > > > Peter Kirchgessner wrote: > > > Hi, > > > > pleae have a look at /etc/sane.d/hp.conf or > > /usr/local/etc/sane.d/hp.conf. It must have two lines in it: > > > > /dev/usbscanner > > option connect-device > > > > In dll.conf (same directories) the line with "hp" must be active. > > You may need to set the permissions: > > > > chmod 666 /dev/usbscanner > > > > More hints can be found at http://www.kirchgessner.net/sanehpfaq.html > > > > Sincerely > > > > Peter > > > > Reid Vail schrieb: > > > >> I've been trying for a least a month to get an HP6350c USB Scanjet to > >> work. I'm running a SuSE 8.1 Personal distro, which comes with a SANE > >> implementation of 1.0.8-47. > >> > >> I think (but can't say for sure) that some part of the install of the > >> unit (via YAST) isn't working because it doesn't even "test" > >> correctly. However YAST does correctly identify it. > >> > >> When I run xscanimage I get this output: > >> > >> [xscanimage] No scanners were identified. If you were expecting > >> something different, check that the scanner is plugged in, turned on and > >> detected by sane-find-scanner (if appropriate). Please read the > >> documentation which came with this software (README, FAQ, manpages). > >> > >> But when I run sane-find-scanner I get this output: > >> > >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = > >> 0x0601) at device /dev/usb/scanner0 > >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = > >> 0x0601) at device /dev/usbscanner > >> > >> I make no claims that I'm not missing something obvious! I just > >> don't get it. For what it's worth, I know the unit works because it > >> runs under Windoze 2K. > >> > >> Thanks in advance. > >> > >> Reid Vail > >> > >> _______________________________________________ > >> Sane-devel mailing list > >> Sane-devel at www.mostang.com > >> http://www.mostang.com/mailman/listinfo/sane-devel > >> > > > > > > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From christoph.bier at web.de Thu Jun 5 19:31:52 2003 From: christoph.bier at web.de (Christoph Bier) Date: Thu, 05 Jun 2003 20:31:52 +0200 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 In-Reply-To: <20030605102544.GB11876@hmg1> References: <20030605102544.GB11876@hmg1> Message-ID: <3EDF8C98.80006@web.de> Henning Meier-Geinitz schrieb: > Hi, > > Some people reported kernel USB timeouts with their gt68xx based > scanners, e.g. Plustek 1247 or Mustek BearPaw series. This seems to be > caused by the check if the firmware is already loaded in the gt68xx > backend. I've disabled this check for now. > > If you encounter this problem, get the latest backend (at least > 1.0-47) or an unofficial snapshot from > http://www.meier-geinitz.de/sane/gt68xx-backend/ . Hi, now my scanner at home works again :-)! But only with the scanner module. Thank you very much for the workaround!! Many greetings, Christoph -- Christoph Bier, Dipl.Oecotroph., Email: bier at wiz.uni-kassel.de Universitaet Kassel, FG Oekologische Lebensmittelqualitaet und Ernaehrungskultur \\ Postfach 12 52 \\ 37202 Witzenhausen Tel.: +49 (0) 55 42 / 98 -17 21, Fax: -17 13 From anoah at pfeiffer.edu Thu Jun 5 19:59:04 2003 From: anoah at pfeiffer.edu (m. allan noah) Date: Thu, 5 Jun 2003 14:59:04 -0400 (EDT) Subject: [sane-devel] any drivers do software calibration? Message-ID: with the adf fujitsu scanners, in grayscale or color, we get fine, lightly colored lines as a part of the scanned image, and the 'background' behind the document when the scan window exceeeds the size of the paper looks mottled gray, as reported on this list. i can find no way in the interface manual to prevent this in hardware, though it has been reported that the same scanners under twain do not display these problems. hence, i assume that this can be corrected in software. are any of the existing sane backends doing this internally? i would like to do something similar as an option in the fujitsu backend... thanks, allan noah -- "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 From henning at meier-geinitz.de Thu Jun 5 21:35:43 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 22:35:43 +0200 Subject: [sane-devel] any drivers do software calibration? In-Reply-To: References: Message-ID: <20030605203543.GA2573@hmg1> Hi, On Thu, Jun 05, 2003 at 02:59:04PM -0400, m. allan noah wrote: > with the adf fujitsu scanners, in grayscale or color, we get fine, lightly > colored lines as a part of the scanned image, Vertical lines? > and the 'background' behind the document when the scan window > exceeeds the size of the paper looks mottled gray, as reported on > this list. That may be the result of the selected gamma, brightness and contrast. > i can find no way in the interface manual to prevent this in hardware, > though it has been reported that the same scanners under twain do not > display these problems. > > hence, i assume that this can be corrected in software. are any of the > existing sane backends doing this internally? i would like to do something > similar as an option in the fujitsu backend... The gt68xx backend does calibration completely in software. I think mustek_usb does this also, other backends of the more low-level scanner may use the same scheme. All scanners supported by the gt68xx backend have a white calibration strip at the top of the scanning area. It's visible if you open these scanners. Calibration works about like this: a) Coarse calibration: The scan bar moves to the calibration strip. The gain and offset values of the analog frontend are setup so the brightest white of the calibration strip is defined as white (255) and the darkest black is 0. You get black by either turning offf the lamp or by scanning a small black mark on the strip. b) Fine calibration: The scan bar scans some milimeters of the white strip in full width. Once with the lamp turned on and once with the lamp turned off. So you get two values per pixel per color, one for max white and one for min black. If you do a real scan you can calculate the resulting pixel color like this (from my memory, untested): real_color = 255 * (scanned_color - min_black) / (max_white - min_black) Bye, Henning From henning at meier-geinitz.de Thu Jun 5 21:39:48 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 5 Jun 2003 22:39:48 +0200 Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <200306060229.41812.rsv869@adelphia.net> References: <3E02AB22.2010409@adelphia.net> <3EE0101E.6010604@adelphia.net> <20030605173733.GB779@hmg1> <200306060229.41812.rsv869@adelphia.net> Message-ID: <20030605203948.GB2573@hmg1> Hi, On Fri, Jun 06, 2003 at 02:29:41AM -0400, Reid Vail wrote: > Hello Henning - I'mm cc'ing to the list as I'm not really an hp expert. > I issues the command you suggested, and everything looks Ok until it tries to > open the libusb. I'm not sure I looked in the right place for the libusb > libraries, but I captured the permissions of what I found. I changed the > libusb.a file with a chmod 666, but didn't see any improvement. Changing the permissions of the library doesn't work. YOu must change the permissions of the device files as explained in man sane-usb (section libusb). The manpage is also on the SANE website: http://panda.mostang.com/sane/man/sane-usb.5.html > [hp] hp_read_config: attach usb 0x03f0 0x0601 > [hp] hp_attach_matching_devices: usb attach matching "usb 0x03f0 0x0601" > [hp] hp_attach: "libusb:001:002" > [hp] sanei_hp_device_info_get: searching libusb:001:002 > [hp] sanei_hp_device_info_get: check libusb:001:002 > [hp] hp_get_dev: New device libusb:001:002, connect-usb, scsi-request=0 > [hp] sanei_hp_device_new: libusb:001:002 > [hp] sanei_hp_device_info_get: searching libusb:001:002 > [hp] sanei_hp_device_info_get: check libusb:001:002 > [hp] hp_nonscsi_open: open usb with "libusb:001:002" > [hp] hp_nonscsi_open: open device libusb:001:002 failed > [hp] nonscsi_new: open failed (Access to resource has been denied) Did you try as root? That's most probably a permission issue. Bye, Henning From anoah at pfeiffer.edu Thu Jun 5 22:27:50 2003 From: anoah at pfeiffer.edu (m. allan noah) Date: Thu, 5 Jun 2003 17:27:50 -0400 (EDT) Subject: [sane-devel] any drivers do software calibration? In-Reply-To: <20030605203543.GA2573@hmg1> Message-ID: On Thu, 5 Jun 2003, Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 05, 2003 at 02:59:04PM -0400, m. allan noah wrote: > > with the adf fujitsu scanners, in grayscale or color, we get fine, lightly > > colored lines as a part of the scanned image, > > Vertical lines? yes, as if some small portion of the diode array always reads, even when there is just white paper. leads to occasional pink or cyan lines, etc. > > > and the 'background' behind the document when the scan window > > exceeeds the size of the paper looks mottled gray, as reported on > > this list. > > That may be the result of the selected gamma, brightness and contrast. > seems to be no way to mess with gamma/brightness/contrast in the hardware, there is only an 8bit or 10bit single-color LUT. > > i can find no way in the interface manual to prevent this in hardware, > > though it has been reported that the same scanners under twain do not > > display these problems. > > > > hence, i assume that this can be corrected in software. are any of the > > existing sane backends doing this internally? i would like to do something > > similar as an option in the fujitsu backend... > > The gt68xx backend does calibration completely in software. I think > mustek_usb does this also, other backends of the more low-level > scanner may use the same scheme. All scanners supported by the gt68xx > backend have a white calibration strip at the top of the scanning > area. It's visible if you open these scanners. > this scanner is adf only, but the backer behind each read array is very bright white plastic. i could use that, if i could figure out how to get the scanner to send me data when there is no document in the scanner i may have to hook it up to a windows box (ack!) and usb snoop on it. thanks for the data below, i will look at these drivers and see if i can see this being done... allan > Calibration works about like this: > > a) Coarse calibration: The scan bar moves to the calibration strip. > The gain and offset values of the analog frontend are setup so the > brightest white of the calibration strip is defined as white (255) > and the darkest black is 0. You get black by either turning offf > the lamp or by scanning a small black mark on the strip. > b) Fine calibration: The scan bar scans some milimeters of the white > strip in full width. Once with the lamp turned on and once with the > lamp turned off. So you get two values per pixel per color, one for > max white and one for min black. > > If you do a real scan you can calculate the resulting pixel color like > this (from my memory, untested): > > real_color = 255 * (scanned_color - min_black) / (max_white - min_black) > > Bye, > Henning > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From peter at pscomp.com Thu Jun 5 22:39:06 2003 From: peter at pscomp.com (Peter Santoro) Date: Thu, 05 Jun 2003 17:39:06 -0400 Subject: [sane-devel] Re: epson: scanimage threshold option not working in 1.0.12 backend (Peter Santoro) Message-ID: <3EDFB87A.1010207@pscomp.com> Ok, I believe I've figured this one out. The function handle_depth_halftone (epson.c) indicates that for threshold to be enabled, the mode must be Binary and halftoning must be None. After adding in some fprintf (to stderr) statements, I discovered that the order of the command line arguements also matters with these options. I seem to remember reading this somewhere, but I must have forgotten. Epson's Image Scan! for Linux 1.4.0 still doesn't work. I'll try their new 1.5.1 release. I apologize if I caused anyone to waste time on this. Peter From karsten.festag at gmx.de Thu Jun 5 23:18:29 2003 From: karsten.festag at gmx.de (Karsten Festag) Date: Fri, 6 Jun 2003 00:18:29 +0200 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org In-Reply-To: <20030603224901.GA931@wanadoo.fr> References: <3EDB6ACF.3010304@charter.net> <20030603224901.GA931@wanadoo.fr> Message-ID: <200306060018.29761.karsten.festag@gmx.de> [....] > Hello, > > I've parsed it a bit, and I must say that you're painting the picture > darker than it really is for parallel port scanners. Parallel port scanners > listed in SANE do work. No need to frighten people. > > I'm a bit skeptic about favouring ECP mode. It may be wise for printers, > but I think it is useless for scanners, unless you use some patch that > bring DMA reads. From a quick grep in SANE docs, EPP or ECP/EPP seems to be > the recommended setting. Just a remark: The Microtek2 parport scanners (they use the onscsi parport chip) do not work in ECP or ECP/EPP mode (data corruption occurs). EPP is here the only option to get good results. Regards, Karsten From webmaster at airrequest.net Fri Jun 6 04:11:02 2003 From: webmaster at airrequest.net (Philip M Dunton) Date: Thu, 5 Jun 2003 20:11:02 -0700 Subject: [sane-devel] Redhat 9 and XSane .89 Message-ID: <200306052011.02553.webmaster@airrequest.net> I have an Epson 1650 scanner which worked perfectly with my Redhat 8 installation. Never a second of grief. Now, after switching to RH 9 and the version of Sane which comes with it I find a very ill-mannered Sane implementation. First, XSane goes out and looks for a scanner automatically on log-in. My scanner is on a USB switch so it can be shared with two other computers so most of the time it is not available on start-up. The "Looking" dialog just hangs around forever. Second, I cannot use XSane or anything (GIMP) that uses it. The application just locks up after running the scanning mechanism. I have to KILL the process. I am using the current iscan rpm from EpsonKowa. Is there something I should know here? Phil Dunton From gerhard at gjaeger.de Fri Jun 6 07:13:16 2003 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Fri, 6 Jun 2003 08:13:16 +0200 Subject: [sane-devel] Announcing Scanner-HOWTO at tldp.org In-Reply-To: <200306060018.29761.karsten.festag@gmx.de> References: <3EDB6ACF.3010304@charter.net> <20030603224901.GA931@wanadoo.fr> <200306060018.29761.karsten.festag@gmx.de> Message-ID: <200306060813.16298.gerhard@gjaeger.de> Hi, On Freitag, 6. Juni 2003 00:18, Karsten Festag wrote: [SNIPSNAP] > Just a remark: > > The Microtek2 parport scanners (they use the onscsi parport chip) do not > work in ECP or ECP/EPP mode (data corruption occurs). EPP is here the only > option to get good results. > The same applies to the Plustek devices, ECP/EPP even causes the autodetection to fail, so SPP and EPP but never ECP/EPP or plain ECP Gerhard From henning at meier-geinitz.de Fri Jun 6 08:51:20 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 09:51:20 +0200 Subject: [sane-devel] Redhat 9 and XSane .89 In-Reply-To: <200306052011.02553.webmaster@airrequest.net> References: <200306052011.02553.webmaster@airrequest.net> Message-ID: <20030606075120.GA2800@hmg1> Hi, On Thu, Jun 05, 2003 at 08:11:02PM -0700, Philip M Dunton wrote: > I have an Epson 1650 scanner which worked perfectly with my Redhat 8 > installation. Never a second of grief. > Now, after switching to RH 9 and the version of Sane which comes with it I Which version of SANE is that (scanimage --version)? > find a very ill-mannered Sane implementation. > First, XSane goes out and looks for a scanner automatically on log-in. You mean xsane is started when you log into X? Oh well... But that is really a setup you should ask Redhat about. We (the SANE developers) don't do that :-) > My scanner is on a USB switch so it can be shared with two other > computers so most of the time it is not available on start-up. The > "Looking" dialog just hangs around forever. All the frontends ask the backends for available scanners on start-up. But this shouldn't take more than a few seconds. > Second, I cannot use XSane or anything (GIMP) that uses it. The application > just locks up after running the scanning mechanism. I have to KILL the > process. Does that also happen with other frontends like xscanimage or scanimage? E.g. try (in an xterm): SANE_DEBUG_DLL=255 scanimage -L If it hangs, what are the last few lines of output? They should contain the name of the backend that freezes. You can comment out this backend in /etc/sane.d/dll.conf. > I am using the current iscan rpm from EpsonKowa. Oh, that's not part of the SANE package. If it's a problem with that package, better ask Epson-Kowa for help. > Is there something I should know here? You could try the normal epson backend that comes with SANE. Bye, Henning From twaugh at redhat.com Fri Jun 6 09:50:19 2003 From: twaugh at redhat.com (Tim Waugh) Date: Fri, 6 Jun 2003 09:50:19 +0100 Subject: [sane-devel] Redhat 9 and XSane .89 In-Reply-To: <20030606075120.GA2800@hmg1> References: <200306052011.02553.webmaster@airrequest.net> <20030606075120.GA2800@hmg1> Message-ID: <20030606085019.GN18481@redhat.com> On Fri, Jun 06, 2003 at 09:51:20AM +0200, Henning Meier-Geinitz wrote: > You mean xsane is started when you log into X? Oh well... That might be the case if he has put it in his GNOME session; it's not something Red Hat Linux does by default (of course). Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From mfleming at michaelfleming.webcentral.com.au Fri Jun 6 12:16:05 2003 From: mfleming at michaelfleming.webcentral.com.au (Michael Fleming) Date: Fri, 6 Jun 2003 21:16:05 +1000 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 In-Reply-To: <3EDF8C98.80006@web.de> References: <20030605102544.GB11876@hmg1> <3EDF8C98.80006@web.de> Message-ID: <20030606111605.GA1885@michaelfleming.webcentral.com.au> On Thu, Jun 05, 2003 at 08:31:52PM +0200, Christoph Bier waffled thusly: > Henning Meier-Geinitz schrieb: > > Hi, > > > > Some people reported kernel USB timeouts with their gt68xx based > > scanners, e.g. Plustek 1247 or Mustek BearPaw series. This seems to be > > caused by the check if the firmware is already loaded in the gt68xx > > backend. I've disabled this check for now. > > > > If you encounter this problem, get the latest backend (at least > > 1.0-47) or an unofficial snapshot from > > http://www.meier-geinitz.de/sane/gt68xx-backend/ . > > Hi, > > now my scanner at home works again :-)! But > only with the scanner module. Thank you very > much for the workaround!! I can confirm it now works with my Genius ColorPage Vivid 3XE (USB) using libusb 0.1.6 and sane-backends 1.0.12 (on Redhat 9, hand-rolled RPM, current RH errata kernel) (This is the first time I've actually got this scanner working under Linux - the Windows scanning app supplied is horrible, sane/xsane are streets ahead. Thanks again!) > Many greetings, > > Christoph Cheers, Michael Fleming. -- Michael Fleming "Bother" said the Borg, "We've assimilated Pooh!" From henning at meier-geinitz.de Fri Jun 6 12:46:56 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 13:46:56 +0200 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 In-Reply-To: <20030606111605.GA1885@michaelfleming.webcentral.com.au> References: <20030605102544.GB11876@hmg1> <3EDF8C98.80006@web.de> <20030606111605.GA1885@michaelfleming.webcentral.com.au> Message-ID: <20030606114656.GB5060@hmg1> Hi, On Fri, Jun 06, 2003 at 09:16:05PM +1000, Michael Fleming wrote: > I can confirm it now works with my Genius ColorPage Vivid 3XE (USB) > using libusb 0.1.6 and sane-backends 1.0.12 (on Redhat 9, hand-rolled > RPM, current RH errata kernel) Thanks for the report. Any problems in color mode? There is a comment "Mostly works. Color problems?" on my list for this scanner, but I don't know if it's still valid. Bye, Henning From henning at meier-geinitz.de Fri Jun 6 13:00:30 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 14:00:30 +0200 Subject: [sane-devel] MacOS X and sm3600 backend: still crashes? Message-ID: <20030606120030.GC5060@hmg1> Hi, some time ago, there have been reports that it's necessary to comment out sm3600 in dll.conf on MacOS X because otherwise SANE crashes in that backend. Is this still the case? Bye, Henning From jochen.eisinger at gmx.de Fri Jun 6 15:01:36 2003 From: jochen.eisinger at gmx.de (Jochen Eisinger) Date: Fri, 06 Jun 2003 16:01:36 +0200 Subject: [sane-devel] New sanei_pa4s2 in cvs Message-ID: <3EE09EC0.4030109@gmx.de> Hi, I commited the new (and fixed) sanei_pa4s2 to cvs earlier today. In order to use the mustek_pp backend, you either have to install libieee1284 (and have configure detect it) [recommended] or enable direct port io (also with configure). What about including libieee1284 into the SANE distribution? I'd volunteer on keeping it up to date. best regards -- jochen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 252 bytes Desc: not available URL: From dahjelle at yahoo.com Fri Jun 6 17:24:59 2003 From: dahjelle at yahoo.com (David Alan Hjelle) Date: Fri, 6 Jun 2003 09:24:59 -0700 (PDT) Subject: [sane-devel] Microtek SlimScan C6 on Mac OS X 10.1.5 (sane-microtek2) Message-ID: <20030606162459.65000.qmail@web13405.mail.yahoo.com> Hello. I've been trying to get my Microtek SlimScan C6 working on my Macintosh running Mac OS X 10.1.5. After a couple days spent trying to get it to compile correctly (you can see the details on the mailing list), everything compiled (including libusb) and I was excited to try my scanner. It shows up under sane-find-scanner as: found USB scanner (vendor=0x05da, product=0x009a) at libusb:-07:005 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. scanimage -L reports: No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). So, I did some research. Apparently, the microtek2 backend only supports USB kernel extensions and not libusb? What would it take to modify the code so that it would work? Thanks for all your great work! It's greatly appreciated even if I don't get this scanner working! In Christ Alone, David Alan Hjelle 1 Corinthians 2:2 http://welcome.to/theJESUSpage __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com From jb at jblache.org Fri Jun 6 17:26:23 2003 From: jb at jblache.org (Julien BLACHE) Date: Fri, 06 Jun 2003 18:26:23 +0200 Subject: [sane-devel] New sanei_pa4s2 in cvs In-Reply-To: <3EE09EC0.4030109@gmx.de> (Jochen Eisinger's message of "Fri, 06 Jun 2003 16:01:36 +0200") References: <3EE09EC0.4030109@gmx.de> Message-ID: <87d6hrmats.fsf@frigate.technologeek.org> Jochen Eisinger wrote: > What about including libieee1284 into the SANE distribution? I'd > volunteer on keeping it up to date. As long as one has the option of using the system's libieee1284, I won't object. Otherwise you'll hear me scream ;-) Anyway, libieee1284 is quite small and easy to build, so I'm not sure it's worth the time you'll spend on having it integrated into the sane-backends source distribution... JB. -- Julien BLACHE From henning at meier-geinitz.de Fri Jun 6 17:53:27 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 18:53:27 +0200 Subject: [sane-devel] Microtek SlimScan C6 on Mac OS X 10.1.5 (sane-microtek2) In-Reply-To: <20030606162459.65000.qmail@web13405.mail.yahoo.com> References: <20030606162459.65000.qmail@web13405.mail.yahoo.com> Message-ID: <20030606165327.GD5060@hmg1> Hi, On Fri, Jun 06, 2003 at 09:24:59AM -0700, David Alan Hjelle wrote: > I've been trying to get my Microtek SlimScan C6 working on my Macintosh > running Mac OS X 10.1.5. [...] > So, I did some research. Apparently, the microtek2 backend only > supports USB kernel extensions and not libusb? What would it take to > modify the code so that it would work? All these scanners are SCSI. The SCSI protocoll is only transported over the USB in case of USB devices. So they use a kernel SCSI-over-USB driver (called "microtek"). So you either need to port this Linux driver to MacOS X or do the SCSI-over-USB logic in the backend itsself. Maybe the maintainer can tell you more about how complicated this may be. Userland SCSI-over-USB is used at least in the ma1509 and the avison backends. Bye, Henning From henning at meier-geinitz.de Fri Jun 6 18:07:49 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 19:07:49 +0200 Subject: [sane-devel] Please test: changed handling of list of backends Message-ID: <20030606170749.GE5060@hmg1> Hi, I've moved the list of backends that will be build from backend/Makefile.in to configure. So we can print more clearly which backends will be compiled and the tests are all in one place. The changes are in CVS now. Please test if I broke something. Configure pronts a warning if a backend is not built (disabling ...) and lists all the backends that are being built. If the variable "$BACKENDS" is set, only the listed backend are built. I don't want to advertise this feature to avoid trouble with missing backends. But it may be handy if you have a slow machine or want to rebuild one backend often. Examples: $ ./configure [...] *** disabling GPHOTO2 backend (not requested, or failed to find gphoto2-config or JPEG library) *** disabling PINT backend (sys/scanio.h not found) *** disabling pnm backend (not selected manually) [...] -> The following backends will be built: abaton agfafocus apple artec as6e avision bh canon canon630u coolscan coolscan2 dc25 dmc epson fujitsu gt68xx hp leo matsushita microtek microtek2 mustek mustek_pp mustek_usb nec pie plustek ricoh s9036 sceptre sharp sp15c st400 tamarack test teco1 teco2 teco3 umax umax_pp umax1220u artec_eplus48u ma1509 ibm hp5400 dc210 dc240 canon_pp hpsj5s qcam v4l net snapscan sm3600 $ BACKENDS="gt68xx net" ./configure [...] -> The following backends will be built: gt68xx net Bye, Henning From jochen.eisinger at gmx.de Fri Jun 6 18:32:37 2003 From: jochen.eisinger at gmx.de (Jochen Eisinger) Date: Fri, 06 Jun 2003 19:32:37 +0200 Subject: [sane-devel] New sanei_pa4s2 in cvs In-Reply-To: <87d6hrmats.fsf@frigate.technologeek.org> References: <3EE09EC0.4030109@gmx.de> <87d6hrmats.fsf@frigate.technologeek.org> Message-ID: <3EE0D035.10505@gmx.de> Hi, Julien BLACHE wrote: > As long as one has the option of using the system's libieee1284, I > won't object. Otherwise you'll hear me scream ;-) Well ofcourse it just would be a fallback option. Not all systems come with libieee1284 and I'd like to keep the overhead to install SANE for mustek_pp as low as possible. regards -- jochen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 252 bytes Desc: not available URL: From henning at meier-geinitz.de Fri Jun 6 19:18:54 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 6 Jun 2003 20:18:54 +0200 Subject: [sane-devel] Proposal: Change of the backend and model status strings Message-ID: <20030606181853.GF5060@hmg1> Hi, There has been some criticism of the current handling of the :status keywords in the .desc files. These filse are used to create our lists of scanners and the output of the scanner search engine. We currently have two sorts of status indicators: 1) The backend status: alpha, beta or stable 2) The model status: unsupported, untested, alpha, beta or stable Concerning the backends status I think we don't really have the need to talk about stability. Crashing backends are rather seldom. So I'm not sure if we need this overall status at all anymore. If we want to keep it, what about a measurement on how active the backend is maintained, e.g.: unmaintained: There is no maintainer. Only security and other grave bugs will be fixed supported: There is a maintainer for the backend. Bugs will be fixed and patches will be accepted. development: The backend is under active development. New features and/or new models may be added. Model status: As proposed by others, I'd like to have a measurement on how good a scanner works compared to its capabilities. E.g.: unsupported: This device is not working at all. untested: The device may work, but nobody has tested it yet. minimal: The device is detected and does something but is not really usable. E.g. It scans in one mode but colors are off. basic: The device is usable, but some modes are not supported or quality is not perfect yet. good: Usable for day-to-day work. Some unusual modes or seldomly-used features aren't supported. perfect: Everything the scanner can do is supported. Here is an example on how the HTML lists could look like: http://www.meier-geinitz.de/sane/tmp/sane-mfgs.html#MUSTEK Only the model status is implemented. And only Mustek SCSi scanners have set the values. Comments? Bye, Henning From mfleming at michaelfleming.webcentral.com.au Sat Jun 7 01:21:30 2003 From: mfleming at michaelfleming.webcentral.com.au (Michael Fleming) Date: Sat, 7 Jun 2003 10:21:30 +1000 Subject: [sane-devel] Timeouts with UHCI and gt68xx based scanners in sane-backends 1.0.12 In-Reply-To: <20030606114656.GB5060@hmg1> References: <20030605102544.GB11876@hmg1> <3EDF8C98.80006@web.de> <20030606111605.GA1885@michaelfleming.webcentral.com.au> <20030606114656.GB5060@hmg1> Message-ID: <20030607002130.GA3855@michaelfleming.webcentral.com.au> On Fri, Jun 06, 2003 at 01:46:56PM +0200, Henning Meier-Geinitz waffled thusly: > Hi, > > On Fri, Jun 06, 2003 at 09:16:05PM +1000, Michael Fleming wrote: > > I can confirm it now works with my Genius ColorPage Vivid 3XE (USB) > > using libusb 0.1.6 and sane-backends 1.0.12 (on Redhat 9, hand-rolled > > RPM, current RH errata kernel) > > Thanks for the report. Any problems in color mode? There is a comment > "Mostly works. Color problems?" on my list for this scanner, but I > don't know if it's still valid. Thanks Henning, I've only run a few samples so far but I've not noted any issues with the scan result's colours. I'll run a few more over the course of the weekend and followup if I note anything interesting or unusual. My test scan is at http://www.michaelfleming.webcentral.com.au/carla2.tif (~130K) if you want a look. ( It's a cover shot my girlfriend's sister did for a local magazine) If I can, I'll have one of my artist friends give me a better idea re: colour precision - I'm a *little* red/green colourblind which might skew my judgement a little. > Bye, > Henning Cheers, Michael. -- Michael Fleming "Bother" said the Borg, "We've assimilated Pooh!" From david at rondotheatre.co.uk Sat Jun 7 01:46:55 2003 From: david at rondotheatre.co.uk (david stevenson) Date: Sat, 7 Jun 2003 01:46:55 +0100 Subject: [sane-devel] Proposal: Change of the backend and model status strings In-Reply-To: <20030606181853.GF5060@hmg1> References: <20030606181853.GF5060@hmg1> Message-ID: <200306070146.55658.david@rondotheatre.co.uk> Here are 2 personal opinions On Friday 06 June 2003 7:18 pm, Henning Meier-Geinitz wrote:> > There has been some criticism of the current handling of the :status > keywords in the .desc files. These filse are used to create our lists > of scanners and the output of the scanner search engine. > > We currently have two sorts of status indicators: > > 1) The backend status: alpha, beta or stable > 2) The model status: unsupported, untested, alpha, beta or stable > > > Concerning the backends status I think we don't really have the need > to talk about stability. Crashing backends are rather seldom. So I'm > not sure if we need this overall status at all anymore. If we want to > keep it, what about a measurement on how active the backend is > maintained, e.g.: > > unmaintained: There is no maintainer. Only security and other > grave bugs will be fixed > supported: There is a maintainer for the backend. Bugs will be fixed and > patches will be accepted. > development: The backend is under active development. New features > and/or new models may be added. Many backends support several scanners, and may be "supported" for most and under "development" for some. Is unmaintained and supported enough without the 3rd option? > Model status: As proposed by others, I'd like to have a measurement on > how good a scanner works compared to its capabilities. E.g.: > > unsupported: This device is not working at all. > untested: The device may work, but nobody has tested it yet. > minimal: The device is detected and does something but is not > really usable. E.g. It scans in one mode but colors > are off. > basic: The device is usable, but some modes are not supported > or quality is not perfect yet. > good: Usable for day-to-day work. Some unusual modes or > seldomly-used features aren't supported. > perfect: Everything the scanner can do is supported. > I do not like the word "perfect" it implies totally bug free and not improvable, would "complete" be more suitable. > > Here is an example on how the HTML lists could look like: > > http://www.meier-geinitz.de/sane/tmp/sane-mfgs.html#MUSTEK > > Only the model status is implemented. And only Mustek SCSi scanners > have set the values. > > Comments? > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From henning at meier-geinitz.de Sat Jun 7 09:57:38 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 7 Jun 2003 10:57:38 +0200 Subject: [sane-devel] Proposal: Change of the backend and model status strings In-Reply-To: <200306070146.55658.david@rondotheatre.co.uk> References: <20030606181853.GF5060@hmg1> <200306070146.55658.david@rondotheatre.co.uk> Message-ID: <20030607085738.GC6584@meier-geinitz.de> Hi, On Sat, Jun 07, 2003 at 01:46:55AM +0100, david stevenson wrote: [backend status] > Many backends support several scanners, and may be "supported" for most and > under "development" for some. > Is unmaintained and supported enough without the 3rd option? I think so, yes. So a boolean flag ":maintained" would be enough. [model status] > I do not like the word "perfect" it implies totally bug free and not > improvable, would "complete" be more suitable. Ok. Bye, Henning From soumarmt at nerim.net Sat Jun 7 16:43:35 2003 From: soumarmt at nerim.net (Thomas Soumarmon) Date: Sat, 7 Jun 2003 17:43:35 +0200 Subject: [sane-devel] Please test: changed handling of list of backends In-Reply-To: <20030606170749.GE5060@hmg1> References: <20030606170749.GE5060@hmg1> Message-ID: <200306071743.35428.soumarmt@nerim.net> Hi, I tested it with BACKENDS="hp5400" and it works great. It is nice to be able to compile only one backend without changing Makefile.in. I still have a problem compiling linux/videodev.h that prevents me from compiling v4l. I send another mail to talk about it. From soumarmt at nerim.net Sat Jun 7 16:43:45 2003 From: soumarmt at nerim.net (Thomas Soumarmon) Date: Sat, 7 Jun 2003 17:43:45 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <20030606170749.GE5060@hmg1> References: <20030606170749.GE5060@hmg1> Message-ID: <200306071743.45097.soumarmt@nerim.net> Hi, I have a problem compiling v4l because of the linux/videodev.h. Has anybody already had this problem with this file ? Follows the errors : In file included from /usr/include/linux/videodev.h:14, from v4l.c:76: /usr/include/linux/videodev2.h:432: parse error before "v4l2_std_id" /usr/include/linux/videodev2.h:432: ISO C forbids data definition with no type or storage class /usr/include/linux/videodev2.h:500: parse error before "v4l2_std_id" /usr/include/linux/videodev2.h:505: parse error before '}' token /usr/include/linux/videodev2.h:518: parse error before "v4l2_std_id" /usr/include/linux/videodev2.h:521: parse error before '}' token /usr/include/linux/videodev2.h:555: parse error before "v4l2_std_id" /usr/include/linux/videodev2.h:557: parse error before '}' token v4l.c: In function `sane_v4l_exit': Thank you for any help, Thomas. From henning at meier-geinitz.de Sat Jun 7 17:40:04 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 7 Jun 2003 18:40:04 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <200306071743.45097.soumarmt@nerim.net> References: <20030606170749.GE5060@hmg1> <200306071743.45097.soumarmt@nerim.net> Message-ID: <20030607164004.GD6584@meier-geinitz.de> Hi, On Sat, Jun 07, 2003 at 05:43:45PM +0200, Thomas Soumarmon wrote: > I have a problem compiling v4l because of the linux/videodev.h. > Has anybody already had this problem with this file ? No, but I haven't installed Video for Linux version 2 (the header is from version 2). > Follows the errors : > > In file included from /usr/include/linux/videodev.h:14, > from v4l.c:76: > /usr/include/linux/videodev2.h:432: parse error before "v4l2_std_id" > /usr/include/linux/videodev2.h:432: ISO C forbids data definition with no type > or storage class Maybe that's the result over our pedantic warning settings. Try with "--disable-warnings". Looks like the header file is not ISO C-conforming (for whatever version of ISO-C). Where did you get videodev2.h from? Is it from your version of libc (which one)? Or is /usr/include/linux a link to /usr/src/linux/include/linux and you have installed a 2.5 kernel? We'll have to think about supporting v4l version 2 anyway. There is an old v4l2 backend, but nobody yet responded to the question if v4l2 is the same as the new version 2 kernel interface. Bye, Henning From henning at meier-geinitz.de Sat Jun 7 21:36:15 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 7 Jun 2003 22:36:15 +0200 Subject: [sane-devel] Proposal: Change of the backend and model status strings In-Reply-To: <20030606181853.GF5060@hmg1> References: <20030606181853.GF5060@hmg1> Message-ID: <20030607203615.GE6584@meier-geinitz.de> Hi, On Fri, Jun 06, 2003 at 08:18:54PM +0200, Henning Meier-Geinitz wrote: > There has been some criticism of the current handling of the :status > keywords in the .desc files. These filse are used to create our lists > of scanners and the output of the scanner search engine. Ok. I wrote some more code and this is the result: http://www.meier-geinitz.de/sane/tmp/sane-mfgs.html http://www.meier-geinitz.de/sane/tmp/sane-backends.html I've changed the mustek backend settings for demondtsrion, so you may want to have a look at those. Tha status of the backend isn't used anymore. If a backend is no longer maintained, we just set the version to "UNMAINTAINED". See the mustek backend for an example. The status of the devices is set by the :status keyword. The menauings are explained in the legend. The code of sane-desc.c translates the old alpha, beta and stable codes like this: alpha: basic beta: good stable: good I think that reflects the current usage best. When sane-desc.c is in CVS, the backends should be moved to the new system. But until this has been done, the list can be generated using the old status vaules (with warnings). The backend status is still used if there is no device status. Please check (also for spelling). The only problem I see is that the scanner search engine code must be rewritten. The ascii output of sane-desc doesn't print the backend status anymore. The device status uses the new values. If a devic estatus is not available, the backend status is used. Bye, Henning From pjh at coastal.net.au Sun Jun 8 02:53:15 2003 From: pjh at coastal.net.au (Peter Howard) Date: 08 Jun 2003 11:53:15 +1000 Subject: [sane-devel] Problem building on OSX Message-ID: <1055037195.1678.7.camel@pig> (I've searched the archive and have seen related problems but not enough info to work the rest out :-( I'm trying to build sane-backends 1.0.12 on OSX 10.2, and I get the following load errors: gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a ../backend/.libs/libsane.dylib -lm -framework CoreFoundation -framework IOKit ld: multiple definitions of symbol _getopt /usr/lib/libm.dylib(getopt.So) definition of _getopt ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text) ld: multiple definitions of symbol _opterr /usr/lib/libm.dylib(getopt.So) definition of _opterr ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data) ld: multiple definitions of symbol _optind /usr/lib/libm.dylib(getopt.So) definition of _optind ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data) ld: multiple definitions of symbol _optopt /usr/lib/libm.dylib(getopt.So) definition of _optopt ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data) make[1]: *** [scanimage] Error 1 make: *** [all-recursive] Error 1 I gave no options to configure. Thanks PJH From soumarmt at nerim.net Sun Jun 8 09:17:41 2003 From: soumarmt at nerim.net (Thomas Soumarmon) Date: Sun, 8 Jun 2003 10:17:41 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <20030607164004.GD6584@meier-geinitz.de> References: <20030606170749.GE5060@hmg1> <200306071743.45097.soumarmt@nerim.net> <20030607164004.GD6584@meier-geinitz.de> Message-ID: <200306081017.41275.soumarmt@nerim.net> Hi, > > Follows the errors : > > > > In file included from /usr/include/linux/videodev.h:14, > > from v4l.c:76: > > /usr/include/linux/videodev2.h:432: parse error before "v4l2_std_id" > > /usr/include/linux/videodev2.h:432: ISO C forbids data definition with no > > type or storage class > > Maybe that's the result over our pedantic warning settings. Try with > "--disable-warnings". Looks like the header file is not ISO > C-conforming (for whatever version of ISO-C). I'll try that later and tell you what it changes. > > Where did you get videodev2.h from? Is it from your version of libc > (which one)? Or is /usr/include/linux a link to > /usr/src/linux/include/linux and you have installed a 2.5 kernel? Looking with the rpmdrake tool (Mdk 9.1 installed) it says that videodev2.h belongs to : glibc-devel-2.3.1-10mdk or kernel-source-2.4.21-0.13mdk I am wondering if this is exact or if it belongs to another package I would have tried on the machine (they have been numerous). > > We'll have to think about supporting v4l version 2 anyway. There is an > old v4l2 backend, but nobody yet responded to the question if v4l2 is > the same as the new version 2 kernel interface. > Have a nice day, Thomas. From henning at meier-geinitz.de Sun Jun 8 10:07:15 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 8 Jun 2003 11:07:15 +0200 Subject: [sane-devel] Problem building on OSX In-Reply-To: <1055037195.1678.7.camel@pig> References: <1055037195.1678.7.camel@pig> Message-ID: <20030608090715.GA18225@meier-geinitz.de> Hi, On Sun, Jun 08, 2003 at 11:53:15AM +1000, Peter Howard wrote: > (I've searched the archive and have seen related problems but not enough > info to work the rest out :-( I thought that problem was fixed. I have some reports that 1.0.12 works, so this maybe is one more occurance of the "all MacOS X systems are different from each other" syndrome. > I'm trying to build sane-backends 1.0.12 on OSX 10.2, and I get the > following load errors: > > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a > ../backend/.libs/libsane.dylib -lm -framework CoreFoundation -framework > IOKit > ld: multiple definitions of symbol _getopt > /usr/lib/libm.dylib(getopt.So) definition of _getopt > ../lib/liblib.a(getopt.o) definition of _getopt in section > (__TEXT,__text) It is defined multiple and that's ok (in libsane and liblib). You could ask the other MacOS X guys and find out what's different on your setup. There have been some MacOS X changes in the current CVS code, but I don't think they are related to your problem. Bye, Henning From henning at meier-geinitz.de Sun Jun 8 10:16:38 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 8 Jun 2003 11:16:38 +0200 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030607183652.GA7370@watcher.WorkGroup> References: <20030604094900.GA7629@watcher.WorkGroup> <20030604181753.GB3795@hmg1> <20030607183652.GA7370@watcher.WorkGroup> Message-ID: <20030608091638.GB18225@meier-geinitz.de> Hi, I'm cc'ing to the sane-devel list again. I'm not a plustek expert so please direct yout answers to the list. Maybe someone with more plustek experience knows what's going on better :-) On Sat, Jun 07, 2003 at 06:36:52PM +0000, Michael Rasile wrote: > Thanks for the reply. I tried everything you suggested but alas, no > go. I have the scanner and usb stuff compiled into the kernel, so I > am not using modules. I am using Gentoo and I know the version of > xsane is not the latest 0.86. I don't know if this has anything to do > with anything. I know the scanner works because I was using Mandrake > 9.1 previously and the scanner setup was all done automatically. The > kernel finds the scanner at boot time and sane-find-scanner finds the > scanner. Please show us the output of "sane-find-scanner -q". > Why won't xsane see the scanner. I'm so frustrated because I > can't figure this thing out even with the docs. :-) I checked the > website for the driver, but do I need to recompile sane-frontend and > back-end or what? If you have recent versions of sane-backends, no you don't need to recompile anything (I guess). Which version of sane-backends do you use (scanimage --version)? > I know this is all very simple for you, but I have > run into a brick wall. I have placed everything(I think) in > /etc/sane.d/dll.conf and plustek.conf but alas, no go. Any further > suggestions as to what I might do or where I might go to help myself > figure this out. Well, I told you how to enable debugging. Did you do that? What happened? I didn't tell you to send us the debug output explicitely, but that was my intention :-) So Please show us the ouput of SANE_DEBUG_PLUSTEK=255 scanimage -L You can save it into a file like this: SANE_DEBUG_PLUSTEK=255 scanimage -L 2>file.txt If there is no output (but the "No scanner found"), the plustek backend is not loaded at all (nor in dll.conf?) In this case, please also try: SANE_DEBUG_DLL=255 scanimage -L 2>file2.txt > I do appreciate your help and also your patience for > reading the ramblings of a nearly insane.(no pun intended) No problem. That's one of the aims of this mailing list :-) > :-))I've > checked the Gentoo forums and see people having the same problem with > xsane, but I haven't found anything yet that helps me. I will keep > searching. You know, if Mandrake is able to configure my scanner, > shouldn't just about every distro be able to do the same thing? (no > response needed here. :-)) Well, the response should be given by your distributor :-) Bye, Henning From henning at meier-geinitz.de Sun Jun 8 10:35:29 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 8 Jun 2003 11:35:29 +0200 Subject: [sane-devel] Redhat 9 and XSane .89 In-Reply-To: <200306071548.43449.webmaster@airrequest.net> References: <200306052011.02553.webmaster@airrequest.net> <20030606075120.GA2800@hmg1> <200306071548.43449.webmaster@airrequest.net> Message-ID: <20030608093529.GC18225@meier-geinitz.de> Hi, On Sat, Jun 07, 2003 at 03:48:43PM -0700, Philip M Dunton wrote: > Since Redhat is such a popular distribution I figured someone else already had > seen this anomalous behavior. I had zero problems after installing RH 8. Which anomalous behaviour? I asked what you really mean but you didn't answer that part of the mail. As Tim Waugh says xsane is not started on login by default, I don't really know what's going on if you don't give details. I haven't heard of any RedHat-specific problems that look like yours. If I had, I'd have said so in may response. > I was hoping for a quick answer. Well, it took only some hours. > I know how to trouble-shoot. The first computer I ever got to play with was > made by an outfit named "Univac." I'm impressed (really!). > Believe me I won't take the time to work out bugs in some else's software. Ok. Nobody asked you to do. Just for the record, I don't know of any current bug in sane-backends that could cause your problem. As you didn't give any details on what backend you are using you may not be using any part of sane-backends at all (but the stuff from Epson Kowa). If you don't care to describe what software you are using, how should we help? > I am too adept at putting them in my own work. Ok. So just ask someone to fix your installation for money. Maybe someone from Redhat? He'll try to find out the necessary information without asking a single dump question to you. > An easy solution for me is to back up to RH 8. Fortunately the > operation of a scanner isn't a priority just now, merely a token of > the stability of the system as a whole. > Geez, you Linux types need to get a grip. Ah, why didn't you put that on top of your mail? Or better don't write an email to the devlopers of a software about a bug that may not even exist in that software? So you are just trolling and don't want any response at all? Why should anyone help you? By the way: SANE is not Linux. Oh well, that long experience with computers and you haven't learned basic social stuff and even how to write an email to a list (cc added). Bye, Henning From peter at pogma.com Sun Jun 8 13:07:19 2003 From: peter at pogma.com (Peter O'Gorman) Date: Sun, 8 Jun 2003 21:07:19 +0900 Subject: [sane-devel] Problem building on OSX In-Reply-To: <1055037195.1678.7.camel@pig> Message-ID: Hi Peter, I am guessing here, but are you using Apple's developer tools which shipped with 10.2 ? This works for me with the ld from the December 2002 developer tools, looks like a linker issue may have been fixed in that release. You can get a copy of the December 2002 tools from http://connect.apple.com after free registration. I'd be interested to know if this solves your problem, I thought that this was solved prior to release of 1.0.12, but it may have only been "solved" for those of us with the latest linker :( Thanks, Peter On Sunday, June 8, 2003, at 10:53 AM, Peter Howard wrote: > (I've searched the archive and have seen related problems but not > enough > info to work the rest out :-( > > I'm trying to build sane-backends 1.0.12 on OSX 10.2, and I get the > following load errors: > > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a > ../backend/.libs/libsane.dylib -lm -framework CoreFoundation -framework > IOKit > ld: multiple definitions of symbol _getopt > /usr/lib/libm.dylib(getopt.So) definition of _getopt > ../lib/liblib.a(getopt.o) definition of _getopt in section > (__TEXT,__text) > ld: multiple definitions of symbol _opterr > /usr/lib/libm.dylib(getopt.So) definition of _opterr > ../lib/liblib.a(getopt.o) definition of _opterr in section > (__DATA,__data) > ld: multiple definitions of symbol _optind > /usr/lib/libm.dylib(getopt.So) definition of _optind > ../lib/liblib.a(getopt.o) definition of _optind in section > (__DATA,__data) > ld: multiple definitions of symbol _optopt > /usr/lib/libm.dylib(getopt.So) definition of _optopt > ../lib/liblib.a(getopt.o) definition of _optopt in section > (__DATA,__data) > make[1]: *** [scanimage] Error 1 > make: *** [all-recursive] Error 1 > > > I gave no options to configure. > > Thanks > > PJH > > > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > From henning at meier-geinitz.de Sun Jun 8 16:01:01 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 8 Jun 2003 17:01:01 +0200 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030608104442.GA6034@watcher.WorkGroup> References: <20030604094900.GA7629@watcher.WorkGroup> <20030604181753.GB3795@hmg1> <20030607183652.GA7370@watcher.WorkGroup> <20030608091638.GB18225@meier-geinitz.de> <20030608104442.GA6034@watcher.WorkGroup> Message-ID: <20030608150101.GE18225@meier-geinitz.de> Hi, On Sun, Jun 08, 2003 at 10:44:42AM +0000, Michael Rasile wrote: > found USB scanner (vendor=0x04a9 produce=0x220e at /dev/usb/scanner0 > at /dev/usbscanner0 Ok, so the kernel USB scanner driver found it. > > Which version of sane-backends do you use (scanimage --version)? > > > backend version 1.0.9 Oh. Are you sure that this version supports your scanner? I can't find "Lide" on the list of supported scanners for 1.0.9. 1.0.12 is the current version of sane-backends but 1.0.10 may also work. But I'm not an plustek expert... > Thanks very much for your response. I apologize if I sent > this to the wrong list. Well, sane-devel is ok. Just don't send your answers to only me, because on the sane-devel mailing list there are more people (e.g. the plustek maintainer) who know much more about your scanner and the plustek backend. That's why I cc to the list again. > This will be the last time I'll post > here.I'll monitor sane-devel mailing list and figure it out. Please > find attached the debug output. If I am sending this to the wrong > place again, please tell me and I will not do so again. Just send it to sane-devel at mostang.com. That's the mailing list address. Not (only) to henning at meier-geinitz.de :-) > Even though I haven't solved the scanner problem yet, I am learning > something from this. When it is solved, maybe I can help someone else > with similar problems. That's very good. We need more people like you! > [plustek] >[usb] 0x04a9 0x220e< Ok, that should be your scanner. > [plustek] next device is a USB device (0x04A9-0x220E) > [plustek] next device is an USB device > [plustek] ># - device devicename< > [plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)< > [plustek] ># [usb] 0x07B3 0x0017< > [plustek] >device /dev/usbscanner0< > [plustek] Decoding device name >/dev/usbscanner0< [...] > [plustek] attach (/dev/usbscanner0, 0xbfffd170, (nil)) > [plustek] Device configuration: > [plustek] device name : >/dev/usbscanner0< > [plustek] porttype : 1 > [plustek] USB-ID : >0x04A9-0x220E< [...] > [plustek] usbDev_open(/dev/usbscanner0,0x04A9-0x220E) > [plustek] Vendor ID=0x04A9, Product ID=0x220E > [plustek] Device >0x04A9-0x220E<, is not supported! Looks like your backend is really too old. Bye, Henning From keeper at neo.rr.com Sun Jun 8 13:27:50 2003 From: keeper at neo.rr.com (Michael Rasile) Date: Sun, 8 Jun 2003 12:27:50 +0000 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030608150101.GE18225@meier-geinitz.de> References: <20030604094900.GA7629@watcher.WorkGroup> <20030604181753.GB3795@hmg1> <20030607183652.GA7370@watcher.WorkGroup> <20030608091638.GB18225@meier-geinitz.de> <20030608104442.GA6034@watcher.WorkGroup> <20030608150101.GE18225@meier-geinitz.de> Message-ID: <20030608122750.GA29906@watcher.WorkGroup> On Sun Jun 08, 2003 at 05:01:01PM +0200 or thereabouts, Henning Meier-Geinitz wrote: > Hi, > > On Sun, Jun 08, 2003 at 10:44:42AM +0000, Michael Rasile wrote: > > found USB scanner (vendor=0x04a9 produce=0x220e at /dev/usb/scanner0 > > at /dev/usbscanner0 > > Ok, so the kernel USB scanner driver found it. > > > > Which version of sane-backends do you use (scanimage --version)? > > > > > backend version 1.0.9 > > Oh. Are you sure that this version supports your scanner? I can't find > "Lide" on the list of supported scanners for 1.0.9. 1.0.12 is the > current version of sane-backends but 1.0.10 may also work. > > But I'm not an plustek expert... > > > Thanks very much for your response. I apologize if I sent > > this to the wrong list. > > Well, sane-devel is ok. Just don't send your answers to only me, > because on the sane-devel mailing list there are more people (e.g. the > plustek maintainer) who know much more about your scanner and the > plustek backend. That's why I cc to the list again. > > > This will be the last time I'll post > > here.I'll monitor sane-devel mailing list and figure it out. Please > > find attached the debug output. If I am sending this to the wrong > > place again, please tell me and I will not do so again. > > Just send it to sane-devel at mostang.com. That's the mailing list > address. Not (only) to henning at meier-geinitz.de :-) > > > Even though I haven't solved the scanner problem yet, I am learning > > something from this. When it is solved, maybe I can help someone else > > with similar problems. > > That's very good. We need more people like you! > > > [plustek] >[usb] 0x04a9 0x220e< > > Ok, that should be your scanner. > > > [plustek] next device is a USB device (0x04A9-0x220E) > > [plustek] next device is an USB device > > [plustek] ># - device devicename< > > [plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)< > > [plustek] ># [usb] 0x07B3 0x0017< > > [plustek] >device /dev/usbscanner0< > > [plustek] Decoding device name >/dev/usbscanner0< > > [...] > > > [plustek] attach (/dev/usbscanner0, 0xbfffd170, (nil)) > > [plustek] Device configuration: > > [plustek] device name : >/dev/usbscanner0< > > [plustek] porttype : 1 > > [plustek] USB-ID : >0x04A9-0x220E< > > [...] > > > [plustek] usbDev_open(/dev/usbscanner0,0x04A9-0x220E) > > [plustek] Vendor ID=0x04A9, Product ID=0x220E > > [plustek] Device >0x04A9-0x220E<, is not supported! > > Looks like your backend is really too old. > > Bye, > Henning Henning, Well, you were correct. It was an outdated backend. I installed the latest sane backend and all is well and scanning. Finally! You'll not be getting any more scanner questions from me.:-) (at least for now) The answer was so simple, I'm embarassed that I didn't see it staring me in the face. Thanks for all your help. Couldn't have done it without you. Take care. Best regards, Mike -- Regards, Mike keeper at neo.rr.com "Don't Fear The Penguin." From berezin at stanford.edu Sun Jun 8 23:12:41 2003 From: berezin at stanford.edu (Sergey Berezin) Date: 08 Jun 2003 15:12:41 -0700 Subject: [sane-devel] Canon CS 8000F, USB and VMWare Message-ID: Hi, I recently acquired Canon CanoScan 8000F (USB 2.0), which is not supported by SANE yet, and I'm thinking of writing a backend for it. Or at least try to reverse-engineer the protocol... So the first question is, has anyone worked on this scanner yet? (Vendor=04a9 ProdID=220f, other details from /proc/bus/usb are at the end). Web search hasn't produced anything useful for me yet, except consistent complaints that Canon wouldn't release even the name of the chipset, saying nothing of the specs... Now, about breaking the protocol. I'm running VMWare (win2k) through USB v.1, and the scanner seems to be working fine. I installed SnoopyPro on the Windows side, but it stops snooping after the the first 120+ tiny control messages right after the scanner is plugged in. No data is logged when it actually scans. According to some other random source, it probably gets confused by the first bulk transfer. As an alternative, I've read in many places (including the archives of this mailing list) that it's possible to log USB messages from VMWare directly from the linux kernel module. Since I'm not familiar with the kernel code, I wonder if someone has already done this and can share the experience or a hacked usb module with me. Regards, Sergey. PS. The relevant portion of /proc/bus/usb/devices: T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 20 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS=64 #Cfgs= 1 P: Vendor=04a9 ProdID=220f Rev= 3.01 S: Manufacturer=Canon S: Product=Scanner C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 10mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=8ms From fred at redgrave.screaming.net Mon Jun 9 06:42:08 2003 From: fred at redgrave.screaming.net (F J Brooks) Date: Mon, 9 Jun 2003 06:42:08 +0100 Subject: [sane-devel] multiple images on XSane References: <20030601132533.21859.53611.Mailman@panda.mostang.com> Message-ID: <000601c32e4a$6e9dd180$a8ec403e@default> On Sat, 31 May 2003 09:15:11 +0200, Henning Meier-Geinitz wrote: > So an older version of xsane works? The current version is 0.91, by > the way. Is there any advantage to me in installing xsane 0.91, eg, will it solve my current problems? I installed v.0.90 only two or three weeks ago (when it was then the latest). > Which version of sane-backends do you use? The version of sane-backends (and sane-frontends) I have is 1.0.11. > Does it depend on resolution or mode setting? Only in viewer mode or > also in the preview window and when you save the image? It doesn't depend on mode, in that I get the same result in the viewer window, when I copy/print, and if I save the image to file and then print. The preview window doesn't seem to work in that it shows a dark, hatched strip about 3 cm wide across the top of the window, with the rest of the window area (A4) white. > Different speed are rather uncommon when using different frontends. Are > you sure that you have only one version of sane-backends installed? No, I found that I also had sane-backends-1.0.8 [the original which came with my SuSE distribution]. So I removed it (using YaST2). That's when things got even worse! I found that, when I clicked on my desktop scanner icon to open /usr/local/bin/xsane, I got the error message: 'Sorry - KDesktop: KDEInit could not launch '/usr/local/bin/xsane'. When I tried the same thing using Konqueror, I got the error message: 'Error - Konqueror: Unable to run the command specified. The file or directory file: /usr/local/bin/xsane does not exist.' I found this rather surprising so I tried: fredjb at FJBrooks:~> ls -l /usr/local/bin total 5281 -rwxr-xr-x 1 root root 20461 2003-05-18 14:18 gamma4scanimage -rwxr-xr-x 1 root root 2255362 2003-06-0509:39 gimp drwxr-xr-x 11 root root 2464 2003-06-05 17:01 glib-2.2.1 -rwxr-xr-x 1 root root 68062 2003-05-10 16:30 glib-genmarshal -rwxr-xr-x 1 root root 4650 2003-05-10 16:29 glib-gettextize -rwxr-xr-x 1 root root 13446 2003-05-10 16:30 glib-mkenums -rwxr-xr-x 1 root root 58018 2003-05-10 16:30 gobject-query drwxr-xr-x 14 root root 1688 2003-06-05 17:02 gtk+-2.2.1 -rwxr-xr-x 1 root root 380652 2003-05-10 15:39 pkg-config drwxr-xr-x 4 root root 1664 2003-06-05 17:04 pkgconfig-0.15.0 -rwxr-xr-x 1 root root 1469115 2003-05-20 16:52 quiteinsane drwxr-xr-x 4 root root 1008 2003-06-05 16:58 quiteinsane-0.10 drwxr-xr-x 12 root root 1696 2003-06-05 16:59 sane-backends-1.0.11 -rwxr-xr-x 1 root root 3298 2003-05-18 14:18 sane-config -rwxr-xr-x 1 root root 141103 2003-05-18 14:18 sane-find-scanner drwxr-xr-x 7 root root 816 2003-06-05 17:00 sane-frontends-1.0.11 -rwxr-xr-x 1 root root 67552 2003-05-12 09:46 scanadf -rwxr-xr-x 1 root root 102425 2003-05-18 14:18 scanimage -rwxr-xr-x 1 root root 305145 2003-05-12 09:46 xcam drwxr-xr-x 9 root root 1344 2003-06-05 16:56 xsane-0.90 -rwxr-xr-x 1 root root 478145 2003-05-12 09:46 xscanimage fredjb at FJBrooks:~> [Many of these were recently downloaded from their source sites on the net, to replace older, out-of-date versions.] To see what the general position was, I then tried: fredjb at FJBrooks:~> sane-find-scanner found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/scanner found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/sg2 # Your SCSI scanner was detected. It may or may not be supported by SANE. Try # scanimage -L and read the backend's manpage. # No USB scanners found. If you expected something different, make sure that # you have loaded a driver for your USB host controller and have installed a # kernel scanner module. # 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. Followed by: fredjb at FJBrooks:~> scanimage -L device `avision:/dev/scanner' is a Hewlett-Packard ScanJet 5300C flatbed scanner device `avision:/dev/sg2' is a Hewlett-Packard ScanJet 5300C flatbed scanner fredjb at FJBrooks:~> I then tried [I have extracted only the bits I thought relevant to my scanner]: SANE_DEBUG_DLL=255 scanimage -L [sanei_debug] Setting debug level of dll to 255. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `net' [dll] add_backend: adding backend `abaton' [dll] add_backend: adding backend `agfafocus' [dll] add_backend: adding backend `apple' [dll] add_backend: adding backend `avision' [dll] add_backend: adding backend `artec' [...................] [dll] add_backend: adding backend `umax1220u' [dll] add_backend: adding backend `v4l' [dll] load: searching backend `v4l' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/libsane-v4l.so.1' [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-v4l.so.1' [dll] init: initializing backend `v4l' [dll] init: backend `v4l' is version 1.0.2 [dll] load: searching backend `umax1220u' in `/usr/local/lib/sane' [........................] [dll] init: backend `artec' is version 1.0.0 [dll] load: searching backend `avision' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/libsane-avision.so.1' [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-avision.so.1' [dll] init: initializing backend `avision' [dll] init: backend `avision' is version 1.0.55 [dll] load: searching backend `apple' in `/usr/local/lib/sane' [.......................] [dll] load: searching backend `net' in `/usr/local/lib/sane' [dll] load: trying to load `/usr/local/lib/sane/libsane-net.so.1' [dll] load: dlopen()ing `/usr/local/lib/sane/libsane-net.so.1' [dll] init: initializing backend `net' [dll] init: backend `net' is version 1.0.11 device `avision:/dev/scanner' is a Hewlett-Packard ScanJet 5300C flatbed scanner device `avision:/dev/sg2' is a Hewlett-Packard ScanJet 5300C flatbed scanner [dll] sane_exit: exiting [dll] sane_exit: calling backend `v4l's exit function [......................] [dll] sane_exit: calling backend `artec's exit function [dll] sane_exit: calling backend `avision's exit function [dll] sane_exit: calling backend `apple's exit function [dll] sane_exit: calling backend `agfafocus's exit function [dll] sane_exit: calling backend `abaton's exit function [dll] sane_exit: calling backend `net's exit function [dll] sane_exit: finished fredjb at FJBrooks:~> > What happens if you scan with scanimage? E.g. "scanimage >image.pnm". > Or xscanimage? Tried: fredjb at FJBrooks:~> scanimage >image.pnm Scanner whirred quietly for a while, but no other response. Then tried: xscanimage: Got 'Select Device' panel giving choice: 'avision:/dev/scanner avision:/dev/sg2 Chose former, clicked 'OK', got: avision/dev/scanner window, on which clicked: 'Preview Window'. Got Preview Window, dragged dashed line into rectangle covering roughly A4 size, then clicked 'Acquire Preview'. Scanner made fairly loud scratching-type noise plus hum, then intermittent whirring noise. Nothing appeared in Preview Window, and 'Acquire Preview' button reappeared. Clicked 'Scan' on main window. After a minute or two, scanner started with whirring noise, and got 'Scanning' panel with 'Receiving RGB data for out.pnm' progress bar graphic. Also second panel headed: 'Output Filename', listing directories and files. After ten-plus minutes, scanning seems complete and 'Scanning' panel disappears. Open out.pnm file and get colour image of object, slightly distorted as is longer and thinner than original. So that's where I am, Henning - as you can see, in rather a mess. Anything you can do to resolve the situation would be much appreciated. Thanks Best Fred From crapsite at gmx.net Mon Jun 9 07:52:12 2003 From: crapsite at gmx.net (Michael Herder) Date: Mon, 9 Jun 2003 08:52:12 +0200 Subject: [sane-devel] Czech translation Message-ID: <20030609065717.DCB6F188@panda.mostang.com> Hi, someone ("Josef") provided a Czech sane-backends translation. If there are no objections, I'll add it to CVS this evening or tomorrow morning. If someone else is also working on a Czech translation, please let me know. Thanks Michael From henning at meier-geinitz.de Mon Jun 9 09:42:57 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 9 Jun 2003 10:42:57 +0200 Subject: [sane-devel] Canon CS 8000F, USB and VMWare In-Reply-To: References: Message-ID: <20030609084257.GB20551@meier-geinitz.de> Hi, On Sun, Jun 08, 2003 at 03:12:41PM -0700, Sergey Berezin wrote: > I recently acquired Canon CanoScan 8000F (USB 2.0), which is not > supported by SANE yet, and I'm thinking of writing a backend for it. > Or at least try to reverse-engineer the protocol... Very good! Have you looked at the SANE list of scanners if there are any othere canon scanners with the same output of /proc/bus/usb/devices? Maybe they use the same chip for diffferent scanners and only chage the ids. > Now, about breaking the protocol. I'm running VMWare (win2k) through > USB v.1, and the scanner seems to be working fine. I installed > SnoopyPro on the Windows side, but it stops snooping after the the > first 120+ tiny control messages right after the scanner is plugged > in. No data is logged when it actually scans. According to some > other random source, it probably gets confused by the first bulk > transfer. I've heard about similar behaviour from several people. It doesn't happen with my USB scanners, however. Maybe it's also related to USB2? > As an alternative, I've read in many places (including the archives of > this mailing list) that it's possible to log USB messages from VMWare > directly from the linux kernel module. Since I'm not familiar with > the kernel code, I wonder if someone has already done this and can > share the experience or a hacked usb module with me. I haven't used vmware. Can you find out how it uses the Linux USB system exactly? Does it use the Kernel scanner driver? Or does it use libusb or even the /proc/bus/usb/001/* devices directly? Anyway, adding some printk messages in usb_bulk_msg() (drivers/usb/usb.c) that print the buffer of the bulk message may be worth a try. If vmware uses the USB scanner driver, there are already some debug macros in scanner.c/.h, just enable them. Bye, Henning From henning at meier-geinitz.de Mon Jun 9 10:03:50 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 9 Jun 2003 11:03:50 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <200306081017.41275.soumarmt@nerim.net> References: <20030606170749.GE5060@hmg1> <200306071743.45097.soumarmt@nerim.net> <20030607164004.GD6584@meier-geinitz.de> <200306081017.41275.soumarmt@nerim.net> Message-ID: <20030609090350.GE20551@meier-geinitz.de> Hi, On Sun, Jun 08, 2003 at 10:17:41AM +0200, Thomas Soumarmon wrote: > > Where did you get videodev2.h from? Is it from your version of libc > > (which one)? Or is /usr/include/linux a link to > > /usr/src/linux/include/linux and you have installed a 2.5 kernel? > > Looking with the rpmdrake tool (Mdk 9.1 installed) it says that videodev2.h > belongs to : > glibc-devel-2.3.1-10mdk or kernel-source-2.4.21-0.13mdk Kernel version 2.4.21 is not released yet and the pre versions don't have that file. Anyway, kernel headers shouldn't be used from userspace. So it's probably from glibc. I'm just wondering why it's not on my system, I'm using the same version of glibc. > I am wondering if this is exact or if it belongs to another package I would > have tried on the machine (they have been numerous). Shouldn't rpm know which package installed a specific file? Bye, Henning From soumarmt at nerim.net Mon Jun 9 10:45:56 2003 From: soumarmt at nerim.net (Thomas Soumarmon) Date: Mon, 9 Jun 2003 11:45:56 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <20030609090350.GE20551@meier-geinitz.de> References: <20030606170749.GE5060@hmg1> <200306081017.41275.soumarmt@nerim.net> <20030609090350.GE20551@meier-geinitz.de> Message-ID: <200306091145.56431.soumarmt@nerim.net> Hi Henning, > > Kernel version 2.4.21 is not released yet and the pre versions don't > have that file. Anyway, kernel headers shouldn't be used from > userspace. So it's probably from glibc. I'm just wondering why it's > not on my system, I'm using the same version of glibc. > > > I am wondering if this is exact or if it belongs to another package I > > would have tried on the machine (they have been numerous). > > Shouldn't rpm know which package installed a specific file? My problem is more the .tar.gz packages I installed and tested, and also the different kernels (2.4.19, 2.4.20 to 2.5.?? ). That is why I think it is specific to my installation, but I was wondering if anyone else had that problem so that it could help me to find the reason and the fix. I'll probably try to force reinstallation of glibc rpm to fix it. Your idea was right for the --disable-warnings. It compiles OK with it. Bye, Thomas. From henning at meier-geinitz.de Mon Jun 9 11:19:38 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 9 Jun 2003 12:19:38 +0200 Subject: [sane-devel] error in linux/videodev.h In-Reply-To: <200306091145.56431.soumarmt@nerim.net> References: <20030606170749.GE5060@hmg1> <200306081017.41275.soumarmt@nerim.net> <20030609090350.GE20551@meier-geinitz.de> <200306091145.56431.soumarmt@nerim.net> Message-ID: <20030609101938.GG20551@meier-geinitz.de> Hi, On Mon, Jun 09, 2003 at 11:45:56AM +0200, Thomas Soumarmon wrote: > My problem is more the .tar.gz packages I installed and tested, and also the > different kernels (2.4.19, 2.4.20 to 2.5.?? ). The kernels don't install anything in /usr/include. Well, at least they shouldn't. What may be a problem is a link /usr/include/linux to /usr/src/linux/include/linux. If you have such a link, all kinds of funny things may happen :-) In kernel 2.5, the header does exist. Bye, Henning From martin at mkcollins.org Mon Jun 9 13:32:46 2003 From: martin at mkcollins.org (Martin Collins) Date: Mon, 9 Jun 2003 13:32:46 +0100 Subject: [sane-devel] multiple images on XSane In-Reply-To: <000601c32e4a$6e9dd180$a8ec403e@default> References: <20030601132533.21859.53611.Mailman@panda.mostang.com> <000601c32e4a$6e9dd180$a8ec403e@default> Message-ID: <20030609133246.3f594f5a.martin@mkcollins.org> On Mon, 9 Jun 2003 06:42:08 +0100 "F J Brooks" wrote: > No, I found that I also had sane-backends-1.0.8 [the original which > came with my SuSE distribution]. So I removed it (using YaST2). > That's when things got even worse! Did you install sane and xsane using YaST2 or from source? Often the two methods will put things in different places and that can lead to conflicts if you have two versions installed. It sounds like you installed sane-backends-1.0.11 from source and xsane from rpm using YaST2. Removing sane-backends-1.0.8 with YaST2 probably removed xsane as well, since xsane depends on sane-backends. If you did install any of sane-backends, sane-frontends or xsane from source I suggest you remove them by going into their respective source directories and (as root) typing 'make uninstall'. Then get the latest rpms you can find and reinstall them using YaST2. This may put xsane in /usr/bin instead of /usr/local/bin. If so you will need to change your icon's properties accordingly. Martin From tang at mac.com Mon Jun 9 19:57:38 2003 From: tang at mac.com (Dino Tang) Date: Mon, 9 Jun 2003 11:57:38 -0700 Subject: [sane-devel] Re: Sane-devel digest, Vol 1 #473 - 6 msgs In-Reply-To: <20030606132518.24192.77979.Mailman@panda.mostang.com> Message-ID: <3D178672-9AAC-11D7-8F98-00039357FFB6@mac.com> I've been compiling sane-backends-1.0.12 on various Mac OS X system without any problem. I did compile libusb using the patch file Mattias sent me. The sm3600 backend should not be an issue. --Dino On Friday, June 6, 2003, at 06:25 AM, sane-devel-request at www.mostang.com wrote: > some time ago, there have been reports that it's necessary to comment > out sm3600 in dll.conf on MacOS X because otherwise SANE crashes in > that backend. Is this still the case? From karsten.festag at gmx.de Mon Jun 9 20:33:41 2003 From: karsten.festag at gmx.de (Karsten Festag) Date: Mon, 9 Jun 2003 21:33:41 +0200 Subject: [sane-devel] Microtek SlimScan C6 on Mac OS X 10.1.5 (sane-microtek2) In-Reply-To: <20030606165327.GD5060@hmg1> References: <20030606162459.65000.qmail@web13405.mail.yahoo.com> <20030606165327.GD5060@hmg1> Message-ID: <200306092133.41746.karsten.festag@gmx.de> Hi, though I'm the maintainer of the microtek2 backend I cannot help you much with the SCSI-over-USB stuff. But Oliver Neukum has done the linux 'microtek' kernel module and I think he can give you some useful hints if you ask him. Regards, Karsten On Friday 06 June 2003 18:53, Henning Meier-Geinitz wrote: > Hi, > > On Fri, Jun 06, 2003 at 09:24:59AM -0700, David Alan Hjelle wrote: > > I've been trying to get my Microtek SlimScan C6 working on my Macintosh > > running Mac OS X 10.1.5. > > [...] > > > So, I did some research. Apparently, the microtek2 backend only > > supports USB kernel extensions and not libusb? What would it take to > > modify the code so that it would work? > > All these scanners are SCSI. The SCSI protocoll is only transported > over the USB in case of USB devices. So they use a kernel > SCSI-over-USB driver (called "microtek"). > > So you either need to port this Linux driver to MacOS X or do the > SCSI-over-USB logic in the backend itsself. Maybe the maintainer can > tell you more about how complicated this may be. > > Userland SCSI-over-USB is used at least in the ma1509 and the avison > backends. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From gerhard at gjaeger.de Tue Jun 10 11:05:59 2003 From: gerhard at gjaeger.de (Jaeger, Gerhard) Date: Tue, 10 Jun 2003 12:05:59 +0200 Subject: [sane-devel] Canon Lide 30 backend In-Reply-To: <20030608150101.GE18225@meier-geinitz.de> References: <20030604094900.GA7629@watcher.WorkGroup> <20030608104442.GA6034@watcher.WorkGroup> <20030608150101.GE18225@meier-geinitz.de> Message-ID: <200306101205.59357.gerhard@gjaeger.de> Hi Henning, On Sonntag, 8. Juni 2003 17:01, Henning Meier-Geinitz wrote: [SNIPSNAP] > Oh. Are you sure that this version supports your scanner? I can't find > "Lide" on the list of supported scanners for 1.0.9. 1.0.12 is the > current version of sane-backends but 1.0.10 may also work. > > But I'm not an plustek expert... seems that you one are now :-) Sorry for not responding on that "cry out", but I'm currently very short of time and probably will be during the next 4 weeks :-( Thanks for solving the problems here Gerhard From janez.dovc at ijs.si Tue Jun 10 12:41:05 2003 From: janez.dovc at ijs.si (Janez Dovc) Date: Tue, 10 Jun 2003 13:41:05 +0200 Subject: [sane-devel] HP ScanJet 5550C Message-ID: <001701c32f45$307d1ae0$0401a8c0@csl03> Hello, I am shure, you are all tired of such questions, but I will try and ask anyway: Does anyone know if somebody works on driver for HP ScanJet 5550C? What is tendence, is there any posibility for such driver to be available in the close future? Thanks for answers, Janez From lnovak at dragon.klte.hu Tue Jun 10 13:29:48 2003 From: lnovak at dragon.klte.hu (Novak Levente) Date: Tue, 10 Jun 2003 14:29:48 +0200 (MET DST) Subject: [sane-devel] Video4linux Message-ID: Recently, the videodev2.h thread reminded me an old problem with the video4linux (or is it v4l?) backend. That is, only the first "scan" produces a (more or less) correct image, while the others have the succesive scanlines badly shifted. Is it normal? Can it be avoided? I know I can use other software (like XawTV) to take snapshots, but if there is such a SANE backend, it should work correctly. Also, a v4l2 backend would be welcome too. Levente From henning at meier-geinitz.de Tue Jun 10 19:17:24 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 10 Jun 2003 20:17:24 +0200 Subject: [sane-devel] HP ScanJet 5550C In-Reply-To: <001701c32f45$307d1ae0$0401a8c0@csl03> References: <001701c32f45$307d1ae0$0401a8c0@csl03> Message-ID: <20030610181724.GB1036@meier-geinitz.de> Hi, On Tue, Jun 10, 2003 at 01:41:05PM +0200, Janez Dovc wrote: > I am shure, you are all tired of such questions, but I will try and ask > anyway: No problem. Most of the time all the information we have is in the lists of (un)supported scanners or the search engine. http://panda.mostang.com/sane/sane-supported-devices.html > Does anyone know if somebody works on driver for HP ScanJet 5550C? I don't think so. > What is tendence, is there any posibility for such driver to be > available in the close future? If you start writing one, probably yes :-) Most of the time SANE developers don't write drivers for completely new scanners. Usually someone like you has such a scanner and wants support for it. So he writes a driver and becomes a SANE developer that way. Do you own such a device? If yes, could you please send us the output of /proc/bus/usb/devices when it's plugged in? So we have at least some information on the ids of the scanner. If you have more information, e.g. which chipset is used, this is also appreciated. Bye, Henning From henning at meier-geinitz.de Tue Jun 10 19:22:32 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 10 Jun 2003 20:22:32 +0200 Subject: [sane-devel] Video4linux In-Reply-To: References: Message-ID: <20030610182232.GA1219@meier-geinitz.de> Hi, On Tue, Jun 10, 2003 at 02:29:48PM +0200, Novak Levente wrote: > Recently, the videodev2.h thread reminded me an old problem with the > video4linux (or is it v4l?) backend. The backend is called "v4l". > That is, only the first "scan" > produces a (more or less) correct image, while the others have the > succesive scanlines badly shifted. Is it normal? If I remeber correctly, it didn't happen with my card the last time I checked. > Can it be avoided? > I know I can use other software (like XawTV) to take snapshots, but if > there is such a SANE backend, it should work correctly. The code of v4l suffers severe bitrot. The TODO mentions: * v4l: - Geometry support is missing - Frequency setting is missing - check if v4lctl distributed with xawtv can be used - Use #define _LINUX_TIME_H 1 just before including videodev.h or videodev2.h to avoid trouble if /usr/include/linux is a link. - Add v4l updates from Martin Palm, see http://www.meier-geinitz.de/sane/misc/sane-v4l-update.tar.gz - compilation seems to break when video4linux version 2 is installed? Martin Palm worked on the v4l backend but I haven't heard from him for quite some time. YOu can try the code in the above mentioned archive but I don't remember if it really works. You could bug Martin Palm or Julien Blache (who also wanted/wants to work on v4l) a bit :-) > Also, a v4l2 backend would be welcome too. Yes, please go ahead and write it :-) There is an old v4l2 backend but I guess that's a different version 2. Bye, Henning From jb at jblache.org Tue Jun 10 20:17:41 2003 From: jb at jblache.org (Julien BLACHE) Date: Tue, 10 Jun 2003 21:17:41 +0200 Subject: [sane-devel] Video4linux In-Reply-To: <20030610182232.GA1219@meier-geinitz.de> (Henning Meier-Geinitz's message of "Tue, 10 Jun 2003 20:22:32 +0200") References: <20030610182232.GA1219@meier-geinitz.de> Message-ID: <87n0gpbv3e.fsf@frigate.technologeek.org> Henning Meier-Geinitz wrote: Hi, > You could bug Martin Palm or Julien Blache (who also wanted/wants to > work on v4l) a bit :-) It's on my todo list for the upcoming weeks :) JB. -- Julien BLACHE From nakal at web.de Tue Jun 10 22:17:58 2003 From: nakal at web.de (Nakal) Date: Tue, 10 Jun 2003 23:17:58 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II Message-ID: <200306102317.58064.nakal@web.de> Well, how to say... it doesn't work. I compiled xsane-0.90 from ports. I tried to set 'norealcal' and/or 'noprecal'. The scanner always causes a timeout (see attachment) while starting "scanimage -d 'microtek:/dev/scanner'". Starting xsane or even scanimage without the correct '-d' option will freeze the system completely. Even --help will freeze it, I wonder why. Am I doing something wrong? Martin --- Here is data about my system which might be important for You: xxx at xxx:/usr/home/xxx> uname -a FreeBSD xxx 4.8-STABLE FreeBSD 4.8-STABLE #1: Sat May 3 22:35:40 CEST 2003 xxx at xxx:/usr/src/sys/compile/XXX i386 xxx at xxx:/usr/home/xxx> camcontrol devlist at scbus0 target 3 lun 0 (pass0,cd0) at scbus0 target 4 lun 0 (pass1,cd1) at scbus0 target 5 lun 0 (pass2,cd2) at scbus0 target 6 lun 0 (pass3) at scbus0 target 6 lun 1 (pass4) at scbus0 target 6 lun 2 (pass5) at scbus0 target 6 lun 3 (pass6) at scbus0 target 6 lun 4 (pass7) at scbus0 target 6 lun 5 (pass8) at scbus0 target 6 lun 6 (pass9) at scbus0 target 6 lun 7 (pass10) Part of dmesg: sym0: <875> port 0xc400-0xc4ff mem 0xe7002000-0xe7002fff,0xe7001000-0xe70010ff irq 11 at device 11.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking I get some errors in my dmesg like this (probably not important): Waiting 15 seconds for SCSI devices to settle (probe6:sym0:0:6:0): phase change 6-7 6 at 0f71418c resid=4. sym0: unexpected disconnect (probe1:sym0:0:6:1): phase change 6-7 6 at 0f71418c resid=4. sym0: unexpected disconnect -------------- next part -------------- A non-text attachment was scrubbed... Name: scanimage.log.gz Type: application/x-gzip Size: 3001 bytes Desc: not available URL: From henning at meier-geinitz.de Wed Jun 11 10:27:48 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 11 Jun 2003 11:27:48 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306102317.58064.nakal@web.de> References: <200306102317.58064.nakal@web.de> Message-ID: <20030611092748.GB3357@meier-geinitz.de> Hi, On Tue, Jun 10, 2003 at 11:17:58PM +0200, Nakal wrote: > Well, how to say... it doesn't work. > > I compiled xsane-0.90 from ports. I tried to set 'norealcal' and/or > 'noprecal'. The scanner always causes a timeout (see attachment) while > starting "scanimage -d 'microtek:/dev/scanner'". Looks like a SCSI problem (either hardware or kernel driver). My Mustek SCSI scanners work fine with FreeBSD/386 so I don't think there is a general bug in the SCSI code of SANE. Maybe you need to disable automatic disconnect/reconnect and/or synchronous transfers. Some scanners don't like that. > Starting xsane or even scanimage without the correct '-d' option will freeze > the system completely. Even --help will freeze it, I wonder why. Kernel bug mist probably. User space programs should never be able to freeze the kernel. You can try to find out by which backend causes the problem by running SANE_DEBUG_DLL=255 scanimage -L and checking the last lines of the output. Disable that backend in dll.conf. That doesn't happen here either so it's either related to your SCSI adapter (driver) or the scanner. Well, I used FreeBSD 5.0 but I don't remeber such problems with older versions. > Am I doing something wrong? Probably not, but maybe your kernel :-) > xxx at xxx:/usr/home/xxx> camcontrol devlist > at scbus0 target 3 lun 0 (pass0,cd0) > at scbus0 target 4 lun 0 (pass1,cd1) > at scbus0 target 5 lun 0 (pass2,cd2) > at scbus0 target 6 lun 0 (pass3) > at scbus0 target 6 lun 1 (pass4) > at scbus0 target 6 lun 2 (pass5) > at scbus0 target 6 lun 3 (pass6) > at scbus0 target 6 lun 4 (pass7) > at scbus0 target 6 lun 5 (pass8) > at scbus0 target 6 lun 6 (pass9) > at scbus0 target 6 lun 7 (pass10) Bah, it shows up on all LUNs. I don't think it's important but maybe the SCSI driver has an option to disable that behaviour. > Part of dmesg: > sym0: <875> port 0xc400-0xc4ff mem 0xe7002000-0xe7002fff,0xe7001000-0xe70010ff > irq 11 at device 11.0 on pci0 > sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking Fast-20? I guess the scanner wil do 10 MHz at most. Maybe reducing the max speed will work together with the other options mentioned. > I get some errors in my dmesg like this (probably not important): > Waiting 15 seconds for SCSI devices to settle > (probe6:sym0:0:6:0): phase change 6-7 6 at 0f71418c resid=4. > sym0: unexpected disconnect Ah, try disabling reconnect/disconnect. Bye, Henning From lnovak at dragon.klte.hu Wed Jun 11 14:39:36 2003 From: lnovak at dragon.klte.hu (Novak Levente) Date: Wed, 11 Jun 2003 15:39:36 +0200 (MET DST) Subject: [sane-devel] Video4linux In-Reply-To: <20030610182232.GA1219@meier-geinitz.de> Message-ID: On Tue, 10 Jun 2003, Henning Meier-Geinitz wrote: > The backend is called "v4l". OK, I was not at my Linux box and did not remember its name. > > That is, only the first "scan" > > produces a (more or less) correct image, while the others have the > > succesive scanlines badly shifted. Is it normal? > > If I remeber correctly, it didn't happen with my card the last time I > checked. > > > Can it be avoided? > > I know I can use other software (like XawTV) to take snapshots, but if > > there is such a SANE backend, it should work correctly. > > The code of v4l suffers severe bitrot. The TODO mentions: > > * v4l: > - Geometry support is missing > - Frequency setting is missing Maybe it is the problem? I have a PAL system. But anyway, the first scan of the session is OK. Only the later ones have this problem. > - check if v4lctl distributed with xawtv can be used > - Use #define _LINUX_TIME_H 1 just before including videodev.h or videodev2.h to avoid > trouble if /usr/include/linux is a link. > - Add v4l updates from Martin Palm, see > http://www.meier-geinitz.de/sane/misc/sane-v4l-update.tar.gz > - compilation seems to break when video4linux version 2 is installed? Don't think so. I have and use v4l2 on my system (kernel 2.4.21-pre5, but with v4l2 patch), all the applications are linked against it (those which use v4l, of course). v4l2 has a compatibility mode, which makes it appear as v4l1 to the non-v4l2-compliant applications. But as v4l2 is not as mature as v4l1 and its API has slightly changed IIRC, this might perturb some programs. > > Martin Palm worked on the v4l backend but I haven't heard from him for > quite some time. YOu can try the code in the above mentioned archive > but I don't remember if it really works. > > You could bug Martin Palm or Julien Blache (who also wanted/wants to > work on v4l) a bit :-) > > > Also, a v4l2 backend would be welcome too. > > Yes, please go ahead and write it :-) > Would do it, but unfortunately don't speak C enough for this. Levente From crapsite at gmx.net Wed Jun 11 17:55:43 2003 From: crapsite at gmx.net (Michael Herder) Date: Wed, 11 Jun 2003 18:55:43 +0200 Subject: [sane-devel] (slightly OT) Using an Artec E+ 48U with Knoppix 3.1 Message-ID: <20030611165422.365A33E@panda.mostang.com> Hi, people asked me, whether it's possible to use the Artec E+ 48U with Knoppix 3.1 (Debian based Linux Demo, which boots from CD). Therefore I've set up a small web page, that shows how one can use this scanner, which isn't supported by the SANE version shipping with Knoppix 3.1. See: http://www.angelfire.com/linux/crapsite/artec2knoppix.html bb Michael From nakal at web.de Wed Jun 11 19:29:15 2003 From: nakal at web.de (Nakal) Date: Wed, 11 Jun 2003 20:29:15 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <20030611092748.GB3357@meier-geinitz.de> References: <200306102317.58064.nakal@web.de> <20030611092748.GB3357@meier-geinitz.de> Message-ID: <200306111902.41911.cinek@gmx.de> On Wednesday 11 June 2003 11:27, Henning Meier-Geinitz wrote: > Looks like a SCSI problem (either hardware or kernel driver). My > Mustek SCSI scanners work fine with FreeBSD/386 so I don't think there > is a general bug in the SCSI code of SANE. You might be right. I will check the cables and the terminator. > You can try to find out by which backend causes the > problem by running > > SANE_DEBUG_DLL=255 scanimage -L It's freezing in random backends. I removed all except microtek. > Fast-20? I guess the scanner wil do 10 MHz at most. Maybe reducing the > max speed will work together with the other options mentioned. No, I think it might be hardware, because I have 3 SCSI cdrom-drives attached and they work fine. > Ah, try disabling reconnect/disconnect. Nope... still same. Thanks for the response Henning. At least I know that it SHOULD work. I will give feedback after I've checked the hardware. Martin From homer_889 at hotmail.com Thu Jun 12 01:29:34 2003 From: homer_889 at hotmail.com (Homer) Date: Thu, 12 Jun 2003 10:29:34 +1000 Subject: [sane-devel] Query Message-ID: Hi, I know it's a really silly question but I'd thought I'd ask it anyway. I'm using mandrake 9.1 and the Xsane package will detect and setup my canon N640P. It will run as root but not as my normal user. I've actually scanned from root but the scanner won't detect from user. It's probably a very simple answer to this but I've missed it somewhere, any reasonable suggestions will be appreciated to fix this problem. thanks in advance HJ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kilgota at banach.math.auburn.edu Thu Jun 12 01:51:40 2003 From: kilgota at banach.math.auburn.edu (Theodore Kilgore) Date: Wed, 11 Jun 2003 19:51:40 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <18Qp5L-1j8CMCC@fmrl02.sul.t-online.com> Message-ID: Henning, Perhaps you would be one to know this, or it is fine if someone else answers the question, too. I want this information because I am trying to write a driver for a camera, as a summer project (specifically for the lots of cameras which call themselves USB vendor:product 0x2770:0x9120 and belong to Class ff, Subclass ff, Protocol ff. These are some really cheap cameras (352x288 max resolution) so I took it on as a summer project, to learn how they work and to write a driver. My question is sufficiently on topic that I feel comfortable asking it from the sane-devel mailing list. Perhaps the gphoto-devel list would be a more appropriate place to ask, but I am sorry to say that the gphoto-devel mailing list seems unable to add me as a subscriber in spite of my attempts, over the past several weeks, to subscribe to it. My question: What are "gamma" and "bayer" and where can I find some literature to read up on such topics? I ask this because I am at this point able to get a picture out of the camera by the very primitive procedure of editing a debug log file. I know that both the Windows driver and the gphoto camlib program which I have written give identical data output. But a. the actual output is exactly one byte per pixel, and saving it as a "raw" file leads nowhere except to error messages when one tries to open them. b. The log output for one picture is much larger (because of whitespace), and putting a BMP or a PPM header on it actually turns the log output (after suitable editing to remove everything but the actual data) into a picture which roughly approximates the actual picture taken but is of quite low quality. So I suspect that some kind of interpolation routine is going on, in order to fill up the whitespace. The point is, what kind of interpolation? What different kinds are there? And how are they implemented? One can obviously confront similar problems when dealing with scanner output, and my questions relate to basic techniques in video imaging. Therefore, on the grounds that I do subscribe to the sane-devel list and am apparently unable to subscribe to the gphoto-devel list in spite of strenuous efforts to do so, I ask about the problems here, instead. I hope, as I said already, that these questions are considered of general interest. I would welcome any information, explanations, or references for reading about the relevant topics. I don't seem to find very much about this with Google, or perhaps I don't know exactly what to search for, so even the right words for a search would help, I think. Thank you very much, Theodore Kilgore From cadu07 at bol.com.br Thu Jun 12 03:37:22 2003 From: cadu07 at bol.com.br (Cadu) Date: Wed, 11 Jun 2003 23:37:22 -0300 Subject: [sane-devel] Scanner Genius CP HR6X - EPP -> It works! Message-ID: <200306112337.22426.cadu07@bol.com.br> Hi people! Recently i've made my Genius ColorPage HR6X EPP works on Linux, with Plustek module. It works fine! I hope I write an English-HOWTO in a few days. Now I have a Portuguese-HOWTO . . . :) Maybe I'll make an web page with pictures of my scanner opened ( I've opened it to view the chipset :)), and with pictures scanned by its. Sorry for my bad english . . . ;-) -- Cadu cadu07 at bol.com.br http://cadu.webhop.org/ From henning at meier-geinitz.de Thu Jun 12 09:12:08 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 12 Jun 2003 10:12:08 +0200 Subject: [sane-devel] Query In-Reply-To: References: Message-ID: <20030612081208.GA10868@meier-geinitz.de> Hi, On Thu, Jun 12, 2003 at 10:29:34AM +1000, Homer wrote: > I know it's a really silly question but I'd thought I'd ask it anyway. It's not that silly. > I'm using mandrake 9.1 and the Xsane package will detect and setup my > canon N640P. It will run as root but not as my normal user. I've > actually scanned from root but the scanner won't detect from user. > It's probably a very simple answer to this but I've missed it > somewhere, any reasonable suggestions will be appreciated to fix this > problem. The answer is simple: it's a permission proble. The solution depends on how you access you USB scanner. Either you use libusb or /dev/usb/scanner*. "scanimage -L" prints which one you use. The manpage sane-usb describes on how to setup permissions for these two cases: LIBUSB The permissions for the device files used by libusb must be adjusted for user access. Otherwise only root can use SANE devices. For Linux, the devices are located in /proc/bus/usb/. There are directories named e.g. "001" (the bus name) containing files "001", "002" etc. (the device files). The right device files can be found out by running scanimage -L as root. Setting permissions with "chmod" is not permanent, however. They will be resetted after reboot or replugging the scan- ner. It's also possible to mount the usbfs with the option "devmode=0666", e.g. by using the following line in /etc/fstab: none /proc/bus/usb usbfs defaults,devmode=0666 0 0 However, this way everyone has access to all USB devices. Another way to set per- missions is to use the hotplug utilities (http://linux-hotplug.sourceforge.net/), which support dynamic setting of access permissions. Last, the frontends can be run as root. However, that's not recommended for security reasons. GENERIC KERNEL SCANNER DRIVER Ensure that the access permissions for the USB device are set appropriately. We recommend to add a group "scanner" to /etc/group which contains all users that should have access to the scanner. The permission of the device should then be set to allow group read and write access. For example, if the scanner is at USB device /dev/usb/scanner0, then the following two commands would set the permission correctly: $ chgrp scanner /dev/usb/scanner0 $ chmod 660 /dev/usb/scanner0 Bye, Henning From henning at meier-geinitz.de Thu Jun 12 09:28:14 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 12 Jun 2003 10:28:14 +0200 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: <18Qp5L-1j8CMCC@fmrl02.sul.t-online.com> Message-ID: <20030612082814.GB10868@meier-geinitz.de> Hi, On Wed, Jun 11, 2003 at 07:51:40PM -0500, Theodore Kilgore wrote: > What are "gamma" Very much simplified: A gamma table is used to transfer the color space used by your input device (scanner, camera) to the color space of your output device (display, printer). A gamma value (or factor) can be used to create a gamma table. Search for "gamma table" and "gamma factor" at google and you'll find lots of documentation. > and "bayer" I think that's a kind of halftoning (transferring gray/color imagaes to black/white). > So I suspect that some kind of interpolation routine is going on, in order > to fill up the whitespace. The point is, what kind of interpolation? What > different kinds are there? And how are they implemented? I don't really understand what you mean by "whitespace". Interpolation is usually used to create resolutions higher than supported by hardware. It's just a marketing gag, you don't get better images, just bigger ones. Example: You have a gray image with 2x2 pixels: 100 200 50 100 To expand it by 50% in both directions you'd interpolate like this: 100 150 200 75 112 150 50 75 100 > One can obviously confront similar problems when dealing with scanner > output, and my questions relate to basic techniques in video imaging. The scanners return image data in lots of differnt formats. E.g. 8, 10, 12, 16 bits/color, all the pixels of one color after each other, or all the colors of one pixel after each other and so on. Maybe your data is also compressed? Or it's transferred as a jpeg? bye, Henning From a.deuring at satzbau-gmbh.de Thu Jun 12 11:10:40 2003 From: a.deuring at satzbau-gmbh.de (abel deuring) Date: Thu, 12 Jun 2003 12:10:40 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <20030611092748.GB3357@meier-geinitz.de> <200306111902.41911.cinek@gmx.de> Message-ID: <3EE851A0.CCA64E53@satzbau-gmbh.de> Nakal wrote: > > On Wednesday 11 June 2003 11:27, Henning Meier-Geinitz wrote: > > > Looks like a SCSI problem (either hardware or kernel driver). My > > Mustek SCSI scanners work fine with FreeBSD/386 so I don't think there > > is a general bug in the SCSI code of SANE. > > You might be right. I will check the cables and the terminator. > > > You can try to find out by which backend causes the > > problem by running > > > > SANE_DEBUG_DLL=255 scanimage -L > > It's freezing in random backends. I removed all except microtek. A long shot: IIRC, these Microtek scanners may freeze, if you access them with another LUN than 0 -- but they show up with all LUN values from 0 to 7. So, if any backend tries to access the scanner with a non-zero LUN, you'll have an unaccessible scanner. I don't know any details, but *if* a SCSI command to a non-zero LUN confuses the scanner in a way that the entire SCSI bus is blocked, worse errors may occur, e.g., the disk with the root partition may be unaccessible. So it's best to connect these cheap scanners to their own SCSI bus. And you should tell FreeBSD not to look for all LUNs of the scanner while it tries to detect devices on the SCSI bus. Abel From gerhard at gjaeger.de Thu Jun 12 12:36:55 2003 From: gerhard at gjaeger.de (Jaeger, Gerhard) Date: Thu, 12 Jun 2003 13:36:55 +0200 Subject: [sane-devel] Scanner Genius CP HR6X - EPP -> It works! In-Reply-To: <200306112337.22426.cadu07@bol.com.br> References: <200306112337.22426.cadu07@bol.com.br> Message-ID: <200306121336.55470.gerhard@gjaeger.de> Hi, On Donnerstag, 12. Juni 2003 04:37, Cadu wrote: > Hi people! > > Recently i've made my Genius ColorPage HR6X EPP works on Linux, with > Plustek module. good to hear that! > It works fine! I hope I write an English-HOWTO in a few days. Now I have a > Portuguese-HOWTO . . . :) If you want to, I can put this or at least the url of your web-site to the Plustek SANE driver page... > Maybe I'll make an web page with pictures of my scanner opened ( I've > opened it to view the chipset :)), and with pictures scanned by its. > > Sorry for my bad english . . . ;-) No problem so far :-) Gerhard From ljm at xs4all.nl Thu Jun 12 13:53:52 2003 From: ljm at xs4all.nl (Laurent-jan) Date: Thu, 12 Jun 2003 14:53:52 +0200 Subject: [sane-devel] "gamma" and "bayer" ? What are they? References: <18Qp5L-1j8CMCC@fmrl02.sul.t-online.com> <20030612082814.GB10868@meier-geinitz.de> Message-ID: <3EE877E0.10206@xs4all.nl> Henning Meier-Geinitz wrote: > Hi, > > On Wed, Jun 11, 2003 at 07:51:40PM -0500, Theodore Kilgore wrote: > >>What are "gamma" > > > Very much simplified: A gamma table is used to transfer the color > space used by your input device (scanner, camera) to the color space > of your output device (display, printer). A gamma value (or factor) > can be used to create a gamma table. > > Search for "gamma table" and "gamma factor" at google and you'll find > lots of documentation. > There is a link in the SANE-FAQ to the colorspace FAQ. If you want to know more about gamma, look at Carles Poynton's FAQs on color and gamma. >>and "bayer" Bayer is a dithering algoritm; it uses fixed paterns. For an example of the 4x4 patterns see: http://tiger.technion.ac.il/~cgcourse/lectures/4-intensity/sld007.htm > <..> -- (c) ljm @ xs4all . nl. No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author. From psfales at lucent.com Thu Jun 12 15:27:48 2003 From: psfales at lucent.com (Peter Fales) Date: Thu, 12 Jun 2003 09:27:48 -0500 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <20030612082814.GB10868@meier-geinitz.de> References: <18Qp5L-1j8CMCC@fmrl02.sul.t-online.com> <20030612082814.GB10868@meier-geinitz.de> Message-ID: <20030612142748.GA18318@lucent.com> On Thu, Jun 12, 2003 at 10:28:14AM +0200, Henning Meier-Geinitz wrote: > Maybe your data is also compressed? Or it's transferred as a jpeg? For a toy camera like this, it's most likely the raw output of the CCD device and needs a fair amount of processing of the raw pixel data. The dc25 backend shows an example of this kind of processing. (It's not likely that you'll be able to use that kind - just an example of that type of processing.) My guess is that the most effective technique would be to open up the camera and try to identify the manufacturer of the CCD. Then see if you can get anything from them. I think that's how the dc-25 algorithms were originally developed (not by me!) -- Pete Fales From kilgota at banach.math.auburn.edu Thu Jun 12 16:58:39 2003 From: kilgota at banach.math.auburn.edu (Theodore Kilgore) Date: Thu, 12 Jun 2003 10:58:39 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <20030612082814.GB10868@meier-geinitz.de> Message-ID: Henning, Well, it seems that my inquiry got some interest, for which I thank everyone who responded. I will try to follow down some of the leads, after writing the Calculus III test I have to give tomorrow. Meanwhile, a couple more comments/questions/responses: On Thu, 12 Jun 2003, Henning Meier-Geinitz wrote: > On Wed, Jun 11, 2003 at 07:51:40PM -0500, Theodore Kilgore wrote: > > What are "gamma" > Matter of fact, I did do soem searching about "gamma" and I did come up with an impression, at least: It seems to be a correction for non-linearity of gain in the hardware (i.e. hardware does not respond in linear fashion to a certain kind of stimulus, so we do something to fix that). > > > and "bayer" > (cut) > > I don't really understand what you mean by "whitespace". > What I meant by "whitespace" is the blank spots between bytes in a file. For example, bc 3f and what is between the c and the 3 I am calling "whitespace." > Interpolation is usually used to create resolutions higher than > supported by hardware. It's just a marketing gag, you don't get better > images, just bigger ones. Maybe so, but: The raw downloaded data for one 352x288 picture is exactly 352x128=101376 bytes. If you put this directly into a file, you get a file of exactly 101376 bytes. If you stick a ppm header on it you have a file with a ppm header on it, and you get an error message if you try to view it. However, if you take the log data output containing the same 101376 bytes, then you have the bytes represented in the form of text as two characters each, with a space between each two successive bytes. So when you remove all material from the log file except the actual data downloaded for a picture you have 101376 bytes of data, which now get saved as a file. The actual size of the file thus created is 3x101376 = 304128 bytes, which presumably happens because now each byte is represented by two characters (requiring one byte each) plus one empty space (the third byte). Addition of a ppm header to the edited log output then creates a .ppm file of size 304143 bytes, which is then a viewable picture. Just not a very good one. Addition of a bmp header instead of a ppm header produces ( after adjustment by, for example, removing the last byte of empty space) a file of size 304182 bytes, which is the size identical to the file size produced by the Windows driver software. Again, it is a viewable picture, which looks the same as the ppm file but with some colors switched seems that ppm and bmp handle endian-ness differently; the colors come out closer to right in the ppm version). Whether the bmp file is viewed with the Windows software or with Linux software is also immaterial. Also it does not matter whether the bytes from the log file were downloaded with the stock driver or with my own programming. I have checked this. > Example: (Example was clear, thanks) > > The scanners return image data in lots of differnt formats. E.g. 8, > 10, 12, 16 bits/color, all the pixels of one color after each other, > or all the colors of one pixel after each other and so on. > If I am not mistaken, this is 8-bit color, since I recall somewhere seeing that the camera gives 256 colors. Also this would fundamentally make sense to me because the actual data gives exactly one pixel per byte. So I guess a natural question might be, that how many "standard" ways are there by which 8-bit color at one pixel can be represented by one byte? And as to this particular instance, I suspect the order RGB is the one being used, not GRB or GBR or such. > Maybe your data is also compressed? Possibly, but the way it is compressed it is exactly 1/3 the size and it is also possible to get a picture resembling the original out of the log output, so my instincts would be against this. Of course, I have been wrong on occasions. > Or it's transferred as a jpeg? > I really don't expect this. The camera is really an el cheapo. If I told you how it downloads data you would probably not believe me. Thomas, my 13-year-old, says it is "brain dead." So I don't think it knows how to pronounce "jpeg." Besides, exactly one byte per pixel ??? Thanks for the help. Ted Kilgore From kilgota at banach.math.auburn.edu Thu Jun 12 17:14:27 2003 From: kilgota at banach.math.auburn.edu (Theodore Kilgore) Date: Thu, 12 Jun 2003 11:14:27 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <20030612142748.GA18318@lucent.com> Message-ID: On Thu, 12 Jun 2003, Peter Fales wrote: > > Maybe your data is also compressed? Or it's transferred as a jpeg? > > For a toy camera like this, it's most likely the raw output of the CCD > device and needs a fair amount of processing of the raw pixel data. Actually, I suspect it is a CMOS chip. The camera really is cheap. > The > dc25 backend shows an example of this kind of processing. (It's not likely > that you'll be able to use that kind - just an example of that type of > processing.) > > My guess is that the most effective technique would be to open up the camera > and try to identify the manufacturer of the CCD. And how would I do that identification if there is nothing written on said chip? Since I have already destroyed one of these things trying to look inside, I would be glad to look in it again (can't kill it twice, after all) if it would really help. And anyway the USB vendor:product number is 0x2770:0x9120, which tells us that the chip is from SQ Technologies ( website at www.sq.com.tw ) and they do claim to make video capture chips. They make an SQ905 and an SQ913 in particular. I suspect the one in this camera is the SQ905 (there is no 912) They have publicly available "data sheets" which are nothing but glossy sales brochures. Then see if you can get > anything from them. Good idea. They don't answer my e-mail. I think that's how the dc-25 algorithms were > originally developed (not by me!) > Hmmm. I will have a look. Thanks. Ted Kilgore From el_profesorfr at yahoo.fr Thu Jun 12 19:02:21 2003 From: el_profesorfr at yahoo.fr (=?iso-8859-1?q?Thomas=20VIAL?=) Date: Thu, 12 Jun 2003 20:02:21 +0200 (CEST) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: Message-ID: <20030612180221.21667.qmail@web12602.mail.yahoo.com> Hi, > What I meant by "whitespace" is the blank spots > between bytes in a file. > For example, > > bc 3f > > and what is between the c and the 3 I am calling > "whitespace." Er, "bc" and "3f" are just two distinct bytes in hexadecimal, 188 and 63 respectively. It seems you are interpreting the hex dump as raw data... One byte is 2 hex digit, and the whitespace is here for readability. Once correctly interpreted as a sequence of hex bytes, my guess is that the log data is strictly equivalent to the raw data, since the final number of bytes is the same. With a correct bmp header the raw data should be ok (maybe upside down). But with 1 byte per pixel the image should be interpreted as greyscale I think -- unless it uses a palette? Thomas ===== ------------------------------ Si vos aist Diex ! http://www.el-profesor.net/ ------------------------------ ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran?ais ! Yahoo! Mail : http://fr.mail.yahoo.com From psfales at lucent.com Thu Jun 12 19:38:06 2003 From: psfales at lucent.com (Peter Fales) Date: Thu, 12 Jun 2003 13:38:06 -0500 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: <20030612142748.GA18318@lucent.com> Message-ID: <20030612183806.GC28599@lucent.com> On Thu, Jun 12, 2003 at 11:14:27AM -0500, Theodore Kilgore wrote: > And anyway the USB vendor:product number is 0x2770:0x9120, which tells us > that the chip is from SQ Technologies ( website at www.sq.com.tw ) and > they do claim to make video capture chips. They make an SQ905 and an SQ913 > in particular. I suspect the one in this camera is the SQ905 (there is no > 912) They have publicly available "data sheets" which are nothing but > glossy sales brochures. The second page of the SQ905 data sheet implies that the sensor is actually not part of the SQ905, but is separate component. Do you think that is the case? -- Pete Fales From psfales at lucent.com Thu Jun 12 19:54:56 2003 From: psfales at lucent.com (Peter Fales) Date: Thu, 12 Jun 2003 13:54:56 -0500 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: <20030612142748.GA18318@lucent.com> Message-ID: <20030612185456.GA10604@lucent.com> Try taking a picture of solid red, green, and blue images. (As close to pure saturated colors as you can get). How does that affect the resulting data? -- Peter Fales Lucent Technologies, Room 1C-436 N9IYJ 2000 N Naperville Rd PO Box 3033 internet: psfales at lucent.com Naperville, IL 60566-7033 work: (630) 979-8031 On Thu, Jun 12, 2003 at 11:14:27AM -0500, Theodore Kilgore wrote: > > > On Thu, 12 Jun 2003, Peter Fales wrote: > > > > Maybe your data is also compressed? Or it's transferred as a jpeg? > > > > For a toy camera like this, it's most likely the raw output of the CCD > > device and needs a fair amount of processing of the raw pixel data. > > Actually, I suspect it is a CMOS chip. The camera really is cheap. > > > The > > dc25 backend shows an example of this kind of processing. (It's not likely > > that you'll be able to use that kind - just an example of that type of > > processing.) > > > > My guess is that the most effective technique would be to open up the camera > > and try to identify the manufacturer of the CCD. > > And how would I do that identification if there is nothing written on > said chip? Since I have already destroyed one of these things trying to > look inside, I would be glad to look in it again (can't kill it twice, > after all) if it would really help. > > And anyway the USB vendor:product number is 0x2770:0x9120, which tells us > that the chip is from SQ Technologies ( website at www.sq.com.tw ) and > they do claim to make video capture chips. They make an SQ905 and an SQ913 > in particular. I suspect the one in this camera is the SQ905 (there is no > 912) They have publicly available "data sheets" which are nothing but > glossy sales brochures. > > Then see if you can get > > anything from them. > > Good idea. They don't answer my e-mail. > > > I think that's how the dc-25 algorithms were > > originally developed (not by me!) > > > Hmmm. I will have a look. > > Thanks. > > Ted Kilgore > > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From kilgota at banach.math.auburn.edu Thu Jun 12 18:55:51 2003 From: kilgota at banach.math.auburn.edu (Theodore Kilgore) Date: Thu, 12 Jun 2003 12:55:51 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: <20030612180221.21667.qmail@web12602.mail.yahoo.com> Message-ID: On Thu, 12 Jun 2003, [iso-8859-1] Thomas VIAL wrote: > Hi, > > > > What I meant by "whitespace" is the blank spots > > between bytes in a file. > > For example, > > > > bc 3f > > > > and what is between the c and the 3 I am calling > > "whitespace." > > Er, "bc" and "3f" are just two distinct bytes in > hexadecimal, 188 and 63 respectively. Yes. I know that. > It seems you are > interpreting the hex dump as raw data... > One byte is 2 hex digit, and the whitespace is here > for readability. > Again, yes. My point was that a string of bytes equal in number to the number of pixels in the picture will give precisely no good result, but that on the other hand putting the text fomat of same data, obtained by suitable editing of the log file, will give a picture provided one only puts a ppm header on the top. In other words, if you read (for example) bc as one byte, and not as three bytes (one for b, one for c, and one for the space after it, and so on through the rest of the file) you do get a file but it is not a picture, but if you do it the second way (stupid as that may look) you do get a picture. > Once correctly interpreted as a sequence of hex bytes, > my guess is that the log data is strictly equivalent > to the raw data, since the final number of bytes is > the same. > No it isn't. The "final number of bytes" in the text file is equal to the number of bytes dumped, times exactly three. And it is the text file with appropriate header which gives a picture. > With a correct bmp header the raw data should be ok > (maybe upside down). Well, actually, it is more complicated. The ppm format only turns the picture upside down, but leaves the colors approximately correct. The bmp format gives you the picture right-side up, mirror-imaged left to right, and seems to reverse red and blue or red and green. > But with 1 byte per pixel the image should be > interpreted as greyscale I think This is not what happens. I judge by the results. > -- unless it uses a > palette? Well, I did not introduce any palette. So if it is using one it is built-in in ImageMagick, GIMP, and in the Windows software, all three. I just dumped the log data into a file, stuck a header on it, and viewed it. Looking at things positively, I did get the data out of the camera by hook or by crook, and nobody told me how to do it. This is fun, isn't it? After all, I am only doing this because the problem is there to solve, and the camera seemed simple enough for a beginner in device support like me, that I could fool with it and learn something. after all, unlike a scanner it has no moving parts. Ted Kilgore From david at rondotheatre.co.uk Thu Jun 12 20:00:02 2003 From: david at rondotheatre.co.uk (david stevenson) Date: Thu, 12 Jun 2003 20:00:02 +0100 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: Message-ID: <200306121959.25287.david@rondotheatre.co.uk> On Thursday 12 June 2003 6:55 pm, Theodore Kilgore wrote: > On Thu, 12 Jun 2003, [iso-8859-1] Thomas VIAL wrote: > > Hi, > Again, yes. My point was that a string of bytes equal in number to the > number of pixels in the picture will give precisely no good result, but > that on the other hand putting the text fomat of same data, obtained by > suitable editing of the log file, will give a picture provided one only > puts a ppm header on the top. In other words, if you read (for example) bc > as one byte, and not as three bytes (one for b, one for c, and one for the > space after it, and so on through the rest of the file) you do get a file > but it is not a picture, but if you do it the second way (stupid as that > may look) you do get a picture. > An interesting way to process data, but if it works....... In converting a byte to hex it is effectivly split into 2 nibbles of 4bits and a fixed value of 0x30 added to each. (or 0x37 if the nibble value is more than 9) So using the ascii file as data should be twice the size (having ignored the spaces). The question then is what headers have you added to make the bitmap. Most headers include information on bits per pixel, pixels per line ... David From mouse at Rodents.Montreal.QC.CA Thu Jun 12 21:22:35 2003 From: mouse at Rodents.Montreal.QC.CA (der Mouse) Date: Thu, 12 Jun 2003 16:22:35 -0400 (EDT) Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: Message-ID: <200306122033.QAA27264@Sparkle.Rodents.Montreal.QC.CA> >> It seems you are interpreting the hex dump as raw data... >> One byte is 2 hex digit, and the whitespace is here for readability. > Again, yes. My point was that a string of bytes equal in number to > the number of pixels in the picture will give precisely no good > result, but that on the other hand putting the text fomat of same > data, obtained by suitable editing of the log file, will give a > picture provided one only puts a ppm header on the top. Your previous description made no sense to me. While reading this, I had a brainflash, and I think I know what's going on. When you have one byte per pixel, you _do_ have a picture, it's just that it's a colourmapped picture, and you don't have the colourmap to go with it, so it makes no sense. Prepend a pgm (not ppm) header and it will be displayable, but it will make little sense - it may or may not be possible to see the original image in it; this amounts to using a gray-ramp colourmap instead of the colourmap the image should have. When you expand it to three bytes per pixel and prepend a ppm header, ppm takes those three bytes as the red, green, and blue bytes for that pixel, so you get one ppm pixel per picture pixel and you get something. This amounts to imposing a different colourmap, one that looks like index red green blue 0 48 48 32 ("00 ") 1 48 49 32 ("01 ") ... 185 98 57 32 ("b9 ") ... 255 102 102 32 ("ff ") which is why the picture looks as though its colours have been scrambled: they have been! Some of pixels may effectively use colourmap entries with 10 instead of 32 for the blue value, if you use newlines instead of spaces for some of the inter-byte spacing. >> But with 1 byte per pixel the image should be interpreted as >> greyscale I think > This is not what happens. I judge by the results. If you prepend a ppm header, no, it will perforce be taken as colour. But if you use a pgm header, it will be taken as grayscale and you should get something semi-sensible. (I don't know enough about bmp to comment on the results you get with bmp headers.) There unfortunately is no format in the pbm/pgm/ppm series that handles colourmapped images, as far as I know. To get sensible pictures in p*m format, you'll need to figure out what the colourmap the camera is assuming the image will be used with is. You may be able to do this by taking pictures of washes of each primary, from black to full brightness, and watching how the byte values change.... /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse at rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B From karsten.festag at gmx.de Thu Jun 12 22:19:32 2003 From: karsten.festag at gmx.de (Karsten Festag) Date: Thu, 12 Jun 2003 23:19:32 +0200 Subject: [sane-devel] Microtek SlimScan C3, output always a black image Message-ID: <200306122319.32379.karsten.festag@gmx.de> Hi Jose, ok, I think I found and solved the problem. I put the changed code on my homepage www.karstenfestag.gmxhome.de, it's the latest version. You will have to remove the SUSE packages and compile SANE from the sources if you want to use that. But I think you can try to exchange only the library file so you don't have to uninstall the SUSE package and compile SANE by yourself: for this you have to find the file 'libsane-microtek2.so.1.0.9'; I think it is in /usr/lib/sane or /usr/local/lib/sane. This file is linked to libsane-microtek2.so.1 and libsane-microtek2.so Please remove the links (all these things are to be done as root) and replace the libsane-microtek2.so.1.0.9 file with the one I attached to this mail (don't forget to unpack (bunzip) the attached file :-) ) The re-create the links: ln libsane-microtek2.so.1.0.9 libsane-microtek2.so.1 ln libsane-microtek2.so.1.0.9 libsane-microtek2.so ( of course to be typed in the directory where the libsane-microtek2.so.1.0.9 file is) Have luck! Karsten [ this is a copied mail for the list without attachment ] From adeuring at gmx.net Thu Jun 12 23:47:24 2003 From: adeuring at gmx.net (abel deuring) Date: Fri, 13 Jun 2003 00:47:24 +0200 Subject: [sane-devel] "gamma" and "bayer" ? What are they? In-Reply-To: References: Message-ID: <3EE902FC.4030903@gmx.net> Theodore Kilgore wrote: > Matter of fact, I did do soem searching about "gamma" and I did come up > with an impression, at least: It seems to be a correction for > non-linearity of gain in the hardware (i.e. hardware does not respond in > linear fashion to a certain kind of stimulus, so we do something to fix > that). Right, that's probably the most common description. Often an arbitrary table or function is used for gamma correction, sometimes a function like out = pow(in, x) is called "gamme correction" and x is called the "gamma value". Occasionally, one can find 1/x being called the gamma value. > The raw downloaded data for one 352x288 picture is exactly 352x128=101376 > bytes. If you put this directly into a file, you get a file of exactly > 101376 bytes. If you stick a ppm header on it you have a file with a ppm > header on it, and you get an error message if you try to view it. For a PPM file of 352x288 pxiels you'll need 352x288x3 bytes. (1 byte for red, one for green, one for blue) > If I am not mistaken, this is 8-bit color, since I recall somewhere seeing > that the camera gives 256 colors. Also this would fundamentally make sense > to me because the actual data gives exactly one pixel per byte. So I > guess a natural question might be, that how many "standard" ways are there > by which 8-bit color at one pixel can be represented by one byte? As far as i know, most if not all CCD sensors have a color filter in front of each sensor element, so that one element "sees" only red light, and another one only green or blue light. A camera with better firmware will build some interpolated values for the "missing colors" of a pixel, or the data from three sensor elements may be merged into one pixle value. I would that your camera simply delivers the raw data. > > > And as to this particular instance, I suspect the order RGB is the one > being used, not GRB or GBR or such. Peter already mentioned that the best way to get a clue about the color representation within the scan data is to make photos of pure red/green/blue areas. This should show data with repeate sequences of two bytes with smaller values and one byte with a larger value, if my guess is right. And if data for all colors is stored in one byte, you'll also quickly get a clue, which bits represents which colors. But I wold bet a few virtual beers that the camera delivers one color channel per byte. Abel From joseos at okstate.edu Fri Jun 13 02:23:22 2003 From: joseos at okstate.edu (Jose Sanchez) Date: Thu, 12 Jun 2003 18:23:22 -0700 Subject: [sane-devel] Microtek SlimScan C3, output always a black image In-Reply-To: <200306122319.32379.karsten.festag@gmx.de> References: <200306122319.32379.karsten.festag@gmx.de> Message-ID: <3EE9278A.7070808@okstate.edu> Hi Karsten, thanks for the help and the time you have put in this. I have only a question, the thing is that I my SUSE distribution I have libsane-microtek2.so.1.0.11 instead of the libsane-microtek2.so.1.0.9. I tried replacing it but the scanner program doesn't even start. So, I made the following: I uninstall the sane package that came with SUSE and I downloaded one from the sane webpage 1.0.12 (I think is the last one). Can I replace the .c and .h with the one that you posted in your web page with this distribution of sane or should I download an older distribution. If so I will continue and see what happends. Thanks Jose Karsten Festag wrote: >Hi Jose, > >ok, I think I found and solved the problem. I put the changed code on my >homepage www.karstenfestag.gmxhome.de, it's the latest version. You will have >to remove the SUSE packages and compile SANE from the sources if you want to >use that. >But I think you can try to exchange only the library file so you don't have to >uninstall the SUSE package and compile SANE by yourself: for this you have to >find the file 'libsane-microtek2.so.1.0.9'; I think it is in /usr/lib/sane or >/usr/local/lib/sane. This file is linked to libsane-microtek2.so.1 and >libsane-microtek2.so > >Please remove the links (all these things are to be done as root) and replace >the libsane-microtek2.so.1.0.9 file with the one I attached to this mail >(don't forget to unpack (bunzip) the attached file :-) ) >The re-create the links: >ln libsane-microtek2.so.1.0.9 libsane-microtek2.so.1 >ln libsane-microtek2.so.1.0.9 libsane-microtek2.so > >( of course to be typed in the directory where the libsane-microtek2.so.1.0.9 >file is) > >Have luck! > >Karsten > >[ this is a copied mail for the list without attachment ] >_______________________________________________ >Sane-devel mailing list >Sane-devel at www.mostang.com >http://www.mostang.com/mailman/listinfo/sane-devel > > From gene.heskett at verizon.net Fri Jun 13 01:37:09 2003 From: gene.heskett at verizon.net (Gene Heskett) Date: Thu, 12 Jun 2003 20:37:09 -0400 Subject: [sane-devel] Logitech ClickSmart 310 help needed. Message-ID: <200306122037.09571.gene.heskett@verizon.net> Hi all; 2 areas in fact. The camera driver, qcamvc-1.0.5 does if I put the verndor/product numbers in its source code, seem to almost connect with this camera. I'm doing this to the source of the patch that gets installed on new kernels so I don't have to repatch the kernel by hand everytime. Anyway, by changing the line in /etc/modules.conf that used to say "alias char-major-81 bttv" so it now says alias char-major-81 videodev, I have lost all my bttv stuffs (I have a Haupauge bt848 based WinTV-Go+FM card too) I can apparently access it with both xsane and gqcam. The symptoms are (for both programs) a small (2.5x2.5 inches on my 1600x1200 screen) picture that looks as if the data has been scrambled in some sort of a geometric scramble pattern. I'd post it, but its about 220K. Suggestions anyone? I'm all ears (amd probably thumbs too :) -- Cheers, Gene AMD K6-III at 500mhz 320M Athlon1600XP at 1400mhz 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved. From joseos at okstate.edu Fri Jun 13 08:24:50 2003 From: joseos at okstate.edu (Jose Sanchez) Date: Fri, 13 Jun 2003 00:24:50 -0700 Subject: [sane-devel] Microtek SlimScan C3, output always a black image In-Reply-To: <200306122319.32379.karsten.festag@gmx.de> References: <200306122319.32379.karsten.festag@gmx.de> Message-ID: <3EE97C42.60705@okstate.edu> Hi Karsten, Thanks a lot, I downloaded the sources files from suse change the files you told me, reinstall everything and it worked out. However, the image is with some vertical lines I don't know why but it doesn't output that annoying black image. Thanks for your time and I really appreciate your work. Sincerely, Jose Karsten Festag wrote: >Hi Jose, > >ok, I think I found and solved the problem. I put the changed code on my >homepage www.karstenfestag.gmxhome.de, it's the latest version. You will have >to remove the SUSE packages and compile SANE from the sources if you want to >use that. >But I think you can try to exchange only the library file so you don't have to >uninstall the SUSE package and compile SANE by yourself: for this you have to >find the file 'libsane-microtek2.so.1.0.9'; I think it is in /usr/lib/sane or >/usr/local/lib/sane. This file is linked to libsane-microtek2.so.1 and >libsane-microtek2.so > >Please remove the links (all these things are to be done as root) and replace >the libsane-microtek2.so.1.0.9 file with the one I attached to this mail >(don't forget to unpack (bunzip) the attached file :-) ) >The re-create the links: >ln libsane-microtek2.so.1.0.9 libsane-microtek2.so.1 >ln libsane-microtek2.so.1.0.9 libsane-microtek2.so > >( of course to be typed in the directory where the libsane-microtek2.so.1.0.9 >file is) > >Have luck! > >Karsten > >[ this is a copied mail for the list without attachment ] >_______________________________________________ >Sane-devel mailing list >Sane-devel at www.mostang.com >http://www.mostang.com/mailman/listinfo/sane-devel > > From stauff at guarana.org Fri Jun 13 08:07:51 2003 From: stauff at guarana.org (Matthew Duggan) Date: Fri, 13 Jun 2003 17:07:51 +1000 Subject: [sane-devel] Query In-Reply-To: References: Message-ID: <1055488071.3ee97847c0c8f@cheesypoof.guarana.org> Quoting Homer : > Hi, > I know it's a really silly question but I'd thought I'd ask it anyway. I'm > using mandrake 9.1 and the Xsane package will detect and setup my canon > N640P. It will run as root but not as my normal user. I've actually scanned > from root but the scanner won't detect from user. ... Hi, Henning's answer was half right :) This is actually a parallel scanner, but the fix is still permissions. I assume Mandrake 9.1 is a 2.4 distro with ppdev enabled so I'll assume you have /dev/parport*. Check the permissions on /dev/parport*.. they will probably look something like this. [stauff at cheesypoof stauff]$ ls -l /dev/parport* crw-rw---- 1 root lp 99, 0 Jun 15 2002 /dev/parport0 crw-rw---- 1 root lp 99, 1 Jun 15 2002 /dev/parport1 If I remember rightly mdk9 uses devfs so it actually won't look exactly like this.. they may be symlinks to somewhere else in /dev (in which case you should check the permissions on the targets) They will likely be owned by the "lp" group (as these ones are), so for the quick fix you can just do: adduser my_username lp Then log out and log back in, and you should be able to scan as non-root. You should add all the users you want to be able to scan to this group. Cheers, - Matthew Duggan ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ From priyag at newgen.co.in Fri Jun 13 08:30:16 2003 From: priyag at newgen.co.in (priya) Date: Fri, 13 Jun 2003 13:00:16 +0530 Subject: [sane-devel] TWAIN on SANE Message-ID: <002701c3317d$a62e48b0$5505a8c0@priya> Hi all ! I have an interface for scanner on TWAIN protocol for windows. Now i need to port it on the LINUX. There are 2 solutions that either to work on TWAIN on sane bridge or to rewrite my interface according to sane. Can anybody suggest what would be more beneficial ??? Regards, Priya Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From ope557 at yahoo.com Fri Jun 13 08:33:44 2003 From: ope557 at yahoo.com (ope) Date: Fri, 13 Jun 2003 00:33:44 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness Message-ID: <20030613073344.999.qmail@web20608.mail.yahoo.com> I have an UMAX Astra 2200 scanner that I connecting to through USB. My problem is basically this: When I use xsane I can preview as many times as I want without any problems. However, once I actually try to scan I sometimes have success and sometimes don't. When I can't successfully scan what happens is that the scanner runs, the lamp moves completely down and back again, the 'REceiving RGB Data' progress bar is just about complete and then xsane completely freezes. Sometimes if I just leave it for 5-10 minutes the scanned image eventually pops up other times I can leave it for more than an hour and the application is still frozen. Here is what I see in messages: kernel: hub.c: USB new device connect on bus2/2, assigned device number 7 kernel: usb.c: USB device 7 (vend/prod 0x1606/0x230) is not claimed by any active driver. kernel: usb.c: registered new driver usbscanner kernel: scanner.c: 0.4.6:USB Scanner Driver kernel: usb_control/bulk_msg: timeout last message repeated 2 times last message repeated 3 times ... kernel: scanner.c: read_scanner(0): excessive NAK's received sane-find-scanner shows: found USB scanner (vendor=0x1606, product=0x0230) at /dev/usb/scanner0 __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com From aneeshmraj at hotmail.com Fri Jun 13 10:29:38 2003 From: aneeshmraj at hotmail.com (aneesh m raj) Date: Fri, 13 Jun 2003 14:59:38 +0530 Subject: [sane-devel] problem with UMAX 2000P printer Message-ID: Hi , Im using a UMAX 2000P parallel port printer and I have downloaded SANE and the patch for UMAX, when I run the umax_pp tool I receive a message "No scanner found Status 134 not expected" .Im using debian linux kernel 2.2.20. Any help is appreciated. Regards Aneesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From henning at meier-geinitz.de Fri Jun 13 10:50:16 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 11:50:16 +0200 Subject: [sane-devel] problem with UMAX 2000P printer In-Reply-To: References: Message-ID: <20030613095016.GB3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 02:59:38PM +0530, aneesh m raj wrote: > Im using a UMAX 2000P parallel port printer A printer? The "S" in SANE means "scanner" :-) Or is this a multi-function-device? > and I have downloaded > SANE and the patch for UMAX, when I run the umax_pp tool I receive a > message "No scanner found Status 134 not expected" .Im using debian > linux kernel 2.2.20. Any help is appreciated. Have you checked the manual page (sane-umax_pp)? Maybe it's a problem with the wrong parallel port mode ("EPP MODE ONLY"). Bye, Henning From henning at meier-geinitz.de Fri Jun 13 11:14:24 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 12:14:24 +0200 Subject: [sane-devel] Avision backend trouble (?) (was: multiple images on XSane) In-Reply-To: <000601c32e4a$6e9dd180$a8ec403e@default> References: <20030601132533.21859.53611.Mailman@panda.mostang.com> <000601c32e4a$6e9dd180$a8ec403e@default> Message-ID: <20030613101424.GC3579@meier-geinitz.de> Hi, On Mon, Jun 09, 2003 at 06:42:08AM +0100, F J Brooks wrote: > On Sat, 31 May 2003 09:15:11 +0200, Henning Meier-Geinitz > > wrote: > > So an older version of xsane works? The current version is 0.91, by > > the way. > > Is there any advantage to me in installing xsane 0.91, eg, will it solve my > current problems? I installed v.0.90 only two or three weeks ago (when it > was then the latest). I don't think so but I haven't seen your problem with any of my scanners so I can't be sure. I was more interested in the first part of the question, however :-) My questions try to find out if it's a frontend (xsane) or backend problem. As you say quiteinsane works, that would point to a frontend problem. However, the description of the bug looks more like a backend problem. Further more, there are no other reports of such a bug as far as I know so I don't really know what's going on. > > Which version of sane-backends do you use? > > The version of sane-backends (and sane-frontends) I have is 1.0.11. 1.0.12 is current but I don't know if that fixes your problem. > > Does it depend on resolution or mode setting? Only in viewer mode or > > also in the preview window and when you save the image? > > It doesn't depend on mode, in that I get the same result in the viewer > window, With "mode" I meant color, gray or lineart. > when I copy/print, and if I save the image to file and then print. Is the image already corrupted when displayed on the screen or is only the print wrong? > The preview window doesn't seem to work in that it shows a dark, hatched > strip about 3 cm wide across the top of the window, with the rest of the > window area (A4) white. That's a bad sign. Maybe really a backend problem because it doesn't happen with any of my backends and XSane. But the scanner does scan (move the scan slider) when you press the "Acquire preview" button? > > Different speed are rather uncommon when using different frontends. Are > > you sure that you have only one version of sane-backends installed? > > No, I found that I also had sane-backends-1.0.8 [the original which came > with my SuSE distribution]. So I removed it (using YaST2). That's when > things got even worse! > > I found that, when I clicked on my desktop scanner icon to open > /usr/local/bin/xsane, I got the error message: > > 'Sorry - KDesktop: KDEInit could not launch '/usr/local/bin/xsane'. Probably that xsane version was linked against your 1.0.8 SANE backends. That would explain why quiteinsane worked. Just rebuild xsane from source again. Now that you have only one version of sane-backends, it should find that one and link against it. In fact I'm a bit surprised that it doesn't work out-of-the-box. > When I tried the same thing using Konqueror, I got the error message: > > 'Error - Konqueror: Unable to run the command specified. The file or > directory file: /usr/local/bin/xsane does not exist.' Well, this message is pretty much clear :-) > I found this rather surprising so I tried: > > fredjb at FJBrooks:~> ls -l /usr/local/bin > drwxr-xr-x 7 root root 816 2003-06-05 17:00 sane-frontends-1.0.11 that's odd. You shouldn't place the source directory of sane-frontends in the directory for binaries. Better use /usr/src or your home directory. > drwxr-xr-x 9 root root 1344 2003-06-05 16:56 xsane-0.90 Same here. > [Many of these were recently downloaded from their source sites on the net, > to > replace older, out-of-date versions.] Yeah, but you did build them from source, did you? And not just unpacked them in /usr/local/bin? xsane (the binary) is just nor there. I don't think that yast removed it. > fredjb at FJBrooks:~> sane-find-scanner > > found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/scanner > found SCSI scanner "HP ScanJet 5300C 6.00" at /dev/sg2 Ok. > > Followed by: > > fredjb at FJBrooks:~> scanimage -L > device `avision:/dev/scanner' is a Hewlett-Packard ScanJet 5300C flatbed > scanner > device `avision:/dev/sg2' is a Hewlett-Packard ScanJet 5300C flatbed > scanner > fredjb at FJBrooks:~> Also ok. > I then tried [I have extracted only the bits I thought relevant to my > scanner]: > > SANE_DEBUG_DLL=255 scanimage -L > [sanei_debug] Setting debug level of dll to 255. > [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends > 1.0.11 Ok, that's the new backend. > > What happens if you scan with scanimage? E.g. "scanimage >image.pnm". > > Or xscanimage? > > Tried: fredjb at FJBrooks:~> scanimage >image.pnm > > Scanner whirred quietly for a while, but no other response. Well, is the image ok (image.pnm)? Display it with e.g. gimp, quiv or display. > Then tried: xscanimage: > > Got 'Select Device' panel giving choice: > 'avision:/dev/scanner > avision:/dev/sg2 > > Chose former, clicked 'OK', got: avision/dev/scanner window, on which > clicked: 'Preview Window'. Got Preview Window, dragged dashed line into > rectangle covering roughly A4 size, Are you sure you started at the top left edge? SOme backends don't like it if you get the coordinates the wrong way. > then clicked 'Acquire Preview'. > Scanner made fairly loud scratching-type noise plus hum, then > intermittent whirring noise. > Nothing appeared in Preview Window, and 'Acquire Preview' button > reappeared. Anyway, preview should always show the whole scanning area. So it looks like a backend problem. > Clicked 'Scan' on main window. After a minute or two, scanner started with > whirring noise, and got 'Scanning' panel with 'Receiving RGB data for > out.pnm' progress bar graphic. Also second panel headed: 'Output Filename', > listing directories and files. > > After ten-plus minutes, That's really slow. But it may be faster if you set a lower resolution. > scanning seems complete and 'Scanning' panel > disappears. Open out.pnm file and get colour image of object, slightly > distorted as is longer and thinner than original. Backend problem. But at least it scans at all. > So that's where I am, Henning - as you can see, in rather a mess. > Anything you can do to resolve the situation would be much > appreciated. My final thought is that there is a problem with the avision backend you use. The frontend shouldn't matter. I you install xsane again, it'll probably show the same symptoms. scanimage should also be the same. Try lower resolutions. Try sane-backends 1.0.12. If that doesn't help, ask the avision maintainer for help if you didn't do already (Rene Rebe ). Bye, Henning From stef-listes at wanadoo.fr Fri Jun 13 13:34:24 2003 From: stef-listes at wanadoo.fr (stef) Date: Fri, 13 Jun 2003 12:34:24 +0000 Subject: [sane-devel] problem with UMAX 2000P printer In-Reply-To: References: Message-ID: <20030613123424.GA911@wanadoo.fr> On Fri, Jun 13, 2003 at 02:59:38PM +0530, aneesh m raj wrote: > Hi , > Im using a UMAX 2000P parallel port printer and I have downloaded SANE and the patch for UMAX, when I run the umax_pp tool I receive a message "No scanner found Status 134 not expected" .Im using debian linux kernel 2.2.20. Any help is appreciated. > Regards > Aneesh Hello, could you please send the output of 'umax_pp -p -t 255' ? Also, check that the linux kernel detects your parallel port correctly. Especially, check that EPP mode is detected. Regards, Stef From henning at meier-geinitz.de Fri Jun 13 11:28:54 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 12:28:54 +0200 Subject: [sane-devel] TWAIN on SANE In-Reply-To: <002701c3317d$a62e48b0$5505a8c0@priya> References: <002701c3317d$a62e48b0$5505a8c0@priya> Message-ID: <20030613102854.GD3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 01:00:16PM +0530, priya wrote: > I have an interface for scanner on TWAIN protocol for windows. Now i > need to port it on the LINUX. What do you mean by interface? Some application or library that uses a scanner over the TWAIN interface? > There are 2 solutions that either to work on TWAIN on sane bridge or > to rewrite my interface according to sane. I don't know much about TWAIN but I guess it isn't too easy to write such a bridge on Linux beacuse of the link of twain to the widget libraries. Also SANE and TWAIN are different in that SANE describes the interface between driver and scan application while twain describes the interface between scan application and image manipulation tool. > Can anybody suggest what would be more beneficial ??? From janez.dovc at ijs.si Fri Jun 13 12:36:16 2003 From: janez.dovc at ijs.si (Janez Dovc) Date: Fri, 13 Jun 2003 13:36:16 +0200 Subject: [sane-devel] HP ScanJet 5550C In-Reply-To: <20030613094540.GA3579@meier-geinitz.de> Message-ID: <007b01c331a0$03248800$b7e6f9c2@csl03> Hi, > Open the scanner's case. That may harm your warranty, > however. Write down the inscriptions of the chips you find. OK, I will try to do that, but next time, I will be in office. > Does your scanner have an ADF (automatic document feeder)? Yes. So, what do you suggest? Is the only solution, that I write the driver myself? How much time does it take, to write a driver for HP scanner. Is their interface somehow inteligent? Are other Scanjets totally uncompatible? Janez From aneeshmraj at hotmail.com Fri Jun 13 12:46:18 2003 From: aneeshmraj at hotmail.com (aneesh m raj) Date: Fri, 13 Jun 2003 17:16:18 +0530 Subject: [sane-devel] problem with UMAX 2000P scanner References: Message-ID: Hi , Thank u it worked the mode was in ECP+EPP . Im using a program to detect scanner devices but I cant retrieve the device by calling sane_get_devices() function .The SANE_Device structure is NULL. %%%%%%%%%%%%scanner.h%%%%%%% #include #define SANE_MAX_USERNAME_LEN 128 #define SANE_MAX_PASSWORD_LEN 128 typedef void (*SANE_Authorization_Callback) (SANE_String_Const resource, SANE_Char username[SANE_MAX_USERNAME_LEN], SANE_Char password[SANE_MAX_PASSWORD_LEN]); SANE_Status initialize_scanner(SANE_Int* version,SANE_Authorization_Callback callback); void exit_scanner(void); SANE_Status get_scanners(const SANE_Device*** device, SANE_Bool local); %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% //scanner.c #include #include "scanner.h" int main() { SANE_Status status= 0; const SANE_Device** dev; int i = 0; status = initialize_scanner(NULL,NULL); if(status != SANE_STATUS_GOOD) { printf("Scanner not properly initialized...\nExit code: %d\n",status); exit(0); } else { status = get_scanners(&dev,1); if(status == SANE_STATUS_GOOD) { /* dev[i] is NULL */ while(dev[i] != NULL) { printf("Name - %s\n", ((const SANE_Device*)dev[i])->name); printf("Vendor - %s\n",((const SANE_Device*)dev[i])->vendor); printf("Model - %s\n",((const SANE_Device*)dev[i])->model); printf("Type - %s\n\n",((const SANE_Device*)dev[i])->type); i++; } } } exit_scanner(); return 0; } SANE_Status initialize_scanner(SANE_Int* version,SANE_Authorization_Callback callback) { return sane_init (version,callback); } void exit_scanner(void) { sane_exit(); } SANE_Status get_scanners(const SANE_Device*** device, SANE_Bool local) { return sane_get_devices (device,local); } Thanks in advance Aneesh ----- Original Message ----- From: aneesh m raj To: sane-devel at www.mostang.com Sent: Friday, June 13, 2003 2:59 PM Subject: [sane-devel] problem with UMAX 2000P printer Hi , Im using a UMAX 2000P parallel port printer and I have downloaded SANE and the patch for UMAX, when I run the umax_pp tool I receive a message "No scanner found Status 134 not expected" .Im using debian linux kernel 2.2.20. Any help is appreciated. Regards Aneesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From henning at meier-geinitz.de Fri Jun 13 13:55:48 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 14:55:48 +0200 Subject: [sane-devel] problem with UMAX 2000P scanner In-Reply-To: References: Message-ID: <20030613125548.GE3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 05:16:18PM +0530, aneesh m raj wrote: > Thank u it worked the mode was in ECP+EPP . Im using a program to > detect scanner devices but I cant retrieve the device by calling > sane_get_devices() function .The SANE_Device structure is NULL. Try "scanimage -L" to make sure it's not a bug in your program. First guess: "umax_pp" is commented out in dll.conf. Bye, Henning From henning at meier-geinitz.de Fri Jun 13 14:03:35 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 15:03:35 +0200 Subject: [sane-devel] HP ScanJet 5550C In-Reply-To: <007b01c331a0$03248800$b7e6f9c2@csl03> References: <20030613094540.GA3579@meier-geinitz.de> <007b01c331a0$03248800$b7e6f9c2@csl03> Message-ID: <20030613130335.GF3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 01:36:16PM +0200, Janez Dovc wrote: > So, what do you suggest? Is the only solution, that I write the driver > myself? I think so, yes. > How much time does it take, to write a driver for HP scanner. That depends on how intelligent it is. If it's rather low-level, it may take weeks to understand the basic protocol and to get it to scan. On the other hand I was able to get an image out of a rather high level Mustek scanner after about 10 hours of work. > Is their interface somehow inteligent? I have no idea. That's up to you to find out :-) Some info on how to do that is here: http://www.meier-geinitz.de/sane/misc/develop.html http://www.meier-geinitz.de/sane/misc/unsupported.html You can also try check-usb-scanner, it tries to detect the chipset of USB scanners. But I'd be surprised if it's an already known chip: http://www.meier-geinitz.de/sane/check-usb-scanner/ > Are other Scanjets totally uncompatible? I don't know until you find out about that :-) Have a look at the list of HP scanners and compare if the protocoll looks similar once you have found outhow it basically works: http://sane.informatik.uni-freiburg.de/cgi-bin/driver.pl?manu=hewlett-packard&model=&bus=usb If you are lucky it's compatible (or similar) to one of the already supported scanners. But I don't think so. Contacting HP for help may also make sense. I don't know however, if they are helpfull at all. Bye, Henning From kilgota at banach.math.auburn.edu Fri Jun 13 16:48:11 2003 From: kilgota at banach.math.auburn.edu (Theodore Kilgore) Date: Fri, 13 Jun 2003 10:48:11 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" ? Thanks to everyone! In-Reply-To: <20030612082814.GB10868@meier-geinitz.de> Message-ID: Henning, Thank you very much for the space on the sane-devel mailing list for a discussion about gamma correction and bayer interpolation/decoding. To everyone who has responded about the topic, I also want to say thanks, because I have gotten several useful suggestions out of it. At this point I need at least a weekend, probably more, to absorb all of the suggestions and to try them out in various ways, whether by incorporating them in code, or by running more experiments with the camera, taking pictures of "pure" red, green, blue, black, white, and so on. So, again, thanks. I may respond to some of you privately, too, but give me time. And probably Henning thinks that enough room and bandwidth have been already taken up. I do hope the discussion has benefitted those trying to deal with scanners as well as with cameras; otherwise I can only admire the altruism of the list maintainers! Theodore Kilgore From henning at meier-geinitz.de Fri Jun 13 19:13:51 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 20:13:51 +0200 Subject: [sane-devel] "gamma" and "bayer" ? Thanks to everyone! In-Reply-To: References: <20030612082814.GB10868@meier-geinitz.de> Message-ID: <20030613181351.GG3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 10:48:11AM -0500, Theodore Kilgore wrote: > So, again, thanks. I may respond to some of you privately, too, but give > me time. And probably Henning thinks that enough room and bandwidth have > been already taken up. I do hope the discussion has benefitted those > trying to deal with scanners as well as with cameras; otherwise I can only > admire the altruism of the list maintainers! Color space/gamma table questions are ontopic on this list. As you have seen I don't know much of this stuff myself and learned quite a bit. And to avoid any misconceptions: I'm neither the list maintainer nor the inventor of SANE but simply know about how SANE works in general a little bit :-) Bye, Henning From knan at mo.himolde.no Fri Jun 13 19:38:05 2003 From: knan at mo.himolde.no (=?ISO-8859-1?Q?Erik_Inge_Bols=F8?=) Date: Fri, 13 Jun 2003 20:38:05 +0200 (CEST) Subject: [sane-devel] "gamma" and "bayer" ? Thanks to everyone! In-Reply-To: <20030613181351.GG3579@meier-geinitz.de> References: <20030612082814.GB10868@meier-geinitz.de> <20030613181351.GG3579@meier-geinitz.de> Message-ID: On Fri, 13 Jun 2003, Henning Meier-Geinitz wrote: >And to avoid any misconceptions: I'm neither the list maintainer nor >the inventor of SANE but simply know about how SANE works in general a >little bit :-) And you announce releases and timetables, which just might lead to people perceiving you as "the boss" :) -- Erik I. Bols? | email: The UNIX philosophy basically involves giving you enough rope to hang yourself. And then a couple of feet more, just to be sure. From TomF at sjpc.org Fri Jun 13 20:04:20 2003 From: TomF at sjpc.org (TomF) Date: Fri, 13 Jun 2003 12:04:20 -0700 Subject: [sane-devel] ADF support for HP7450C Message-ID: <20030613120420.610305e8.TomF@sjpc.org> I am using XSANE 0.89 on Redhat 9.0 with an HP 7450C scanner, with ADF that works on Windows XP when I dual boot. Setup/Enhancement/Automatic Document Feeder Modus has only the option None. I did not understand how to set SANE_NAME_SCAN_SOURCE from the messages I read in the archives. How do you do this? In February, Rene Rebe suggested using the CVS version with this scanner. Is this still necessary? I would rather use a Redhat rpm if one is available with this support. From klaus.dahlke at gmx.de Fri Jun 13 20:59:50 2003 From: klaus.dahlke at gmx.de (Klaus Dahlke) Date: Fri, 13 Jun 2003 21:59:50 +0200 Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030613073344.999.qmail@web20608.mail.yahoo.com> References: <20030613073344.999.qmail@web20608.mail.yahoo.com> Message-ID: <20030613215950.2a184f4a.klaus.dahlke@gmx.de> On Fri, 13 Jun 2003 00:33:44 -0700 (PDT) ope wrote: > I have an UMAX Astra 2200 scanner that I connecting to > through USB. My problem is basically this: > > When I use xsane I can preview as many times as I want > without any problems. However, once I actually try to > scan I sometimes have success and sometimes don't. > When I can't successfully scan what happens is that > the scanner runs, the lamp moves completely down and > back again, the 'REceiving RGB Data' progress bar is > just about complete and then xsane completely freezes. > I have also an Umax 2200SU (SCSI and USB) and I do have the same problem when conneczed via USB. Sometimes okay (especially with no scan area selct), but selecting a scan area, the system freezes at about 95%. I have experienced that with xsane and xscanimage, so most likely it is in the backend. Best regards, Klaus From henning at meier-geinitz.de Fri Jun 13 21:10:19 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 13 Jun 2003 22:10:19 +0200 Subject: [sane-devel] avision: ADF support for HP7450C In-Reply-To: <20030613120420.610305e8.TomF@sjpc.org> References: <20030613120420.610305e8.TomF@sjpc.org> Message-ID: <20030613201019.GH3579@meier-geinitz.de> Hi, On Fri, Jun 13, 2003 at 12:04:20PM -0700, TomF wrote: > I am using XSANE 0.89 on Redhat 9.0 with an HP 7450C scanner, with ADF > that works on Windows XP when I dual boot. > > Setup/Enhancement/Automatic Document Feeder Modus has only the option > None. I did not understand how to set SANE_NAME_SCAN_SOURCE from the > messages I read in the archives. How do you do this? The avision backend provides the option "adf" ("Enable Automatic-Document-Feeder"). If this option isn't displayed, maybe the backend hasn't detected your ADF. Try "scanimage --help". That should list the ADF option, maybe as "inactive". But the avision maintainer will know the details :-) > In February, Rene Rebe suggested using the CVS version with this > scanner. Is this still necessary? I would rather use a Redhat rpm if > one is available with this support. At least since the release of sane-backends 1.0.12 there have been no changes to the CVS concerning the avision backend. So if you can get an RPM of 1.0.12 this is current concerning SANE CVS. Bye, Henning From steve at icarus.com Sat Jun 14 02:09:46 2003 From: steve at icarus.com (Stephen Williams) Date: Fri, 13 Jun 2003 18:09:46 -0700 Subject: [sane-devel] TWAIN on SANE In-Reply-To: Message from "priya" of "Fri, 13 Jun 2003 13:00:16 +0530." <002701c3317d$a62e48b0$5505a8c0@priya> Message-ID: <200306140109.h5E19kl20155@icarus.com> priyag at newgen.co.in said: > I have an interface for scanner on TWAIN protocol for windows.? Now i > need to port it on the LINUX. The TWAIN working group occasionally wonders about porting TWAIN to Linux, or defining a Linux variant of TWAIN. The former is iffy due to integration with the Windows message pump, and the latter comes with a lack of motivation from the involved parties. There is a SaneTWAIN datasource for Windows that allows Windows TWAIN apps access scanners over the network via SANE and the scanner's SANE driver, but I've not heard of any Linux version of that. If to write such a thing, the TWG might be interested. -- Steve Williams "The woods are lovely, dark and deep. steve at icarus.com But I have promises to keep, http://www.icarus.com and lines to code before I sleep, http://www.picturel.com And lines to code before I sleep." From kilgota at banach.math.auburn.edu Sat Jun 14 01:01:45 2003 From: kilgota at banach.math.auburn.edu (Theodore Kilgore) Date: Fri, 13 Jun 2003 19:01:45 -0500 (CDT) Subject: [sane-devel] "gamma" and "bayer" Thanks again. It works! In-Reply-To: <20030613181351.GG3579@meier-geinitz.de> Message-ID: Briefly: I had to make the "stock" bayer and gamma routines from gphoto2 to work in my program. The color map is standard, too. I want to thank everyone for helping me focus on exactly what was needed and on what I should at least try out. My program is very primitive at this point. It will sense the resolution setting and will download all of the pictures on the camera, directly into files on the hard drive. It is primitive because I really don't know very well yet to divide everything into different functions, and I also have not figured out yet how the gphoto "filesystem" functions fit together, so every time I try to incorporate them, I get C code which gives ten thousand error messages. The code will probably not work on low resolution, either. I haven't tested that yet. Also this camera can be used as a PC cam to download something like 10 frames per second. I have not addressed this at all, yet. All of this will take a little bit more time, but the camera assuredly works. On Fri, 13 Jun 2003, Henning Meier-Geinitz wrote: > Color space/gamma table questions are ontopic on this list. Whew! I would have thought, myself, that the gphoto-devel list would be more appropriate, but I seem to be unable to subscribe to it. Does anyone know if the instructions at gphoto.org for subscribing to the list are out of date, or what? > As you > have seen I don't know much of this stuff myself and learned quite a > bit. > Well, it is one of my acquired skills as a professor, that I know how to ask good questions even if I don't have the answers ;-) > And to avoid any misconceptions: I'm neither the list maintainer nor > the inventor of SANE but simply know about how SANE works in general a > little bit :-) > > Bye, > Henning > I will try to send a picture to those who have responded to my questions, because I do not feel it is right to send it here. I will be glad to do that, though, if someone in charge (who, then?) sends me an e-mail saying it is OK to do that. The picture is slightly retouched with "sharpen" under GIMP. Nothing else done to it (except to turn it right-side up). It looked almost as good as the Windows-produced BMP file before, and my retouched picture looks better than the Windows-produced picture when similarly retouched, too. Funny thing is, out of 20 pictures I took, some of them looked better as-is with my program, and some of them looked better with the Windows software issued with the camera. Theodore Kilgore From brian at aljex.com Sat Jun 14 07:19:54 2003 From: brian at aljex.com (Brian K. White) Date: Sat, 14 Jun 2003 02:19:54 -0400 Subject: [sane-devel] TWAIN on SANE In-Reply-To: <200306140109.h5E19kl20155@icarus.com> References: <200306140109.h5E19kl20155@icarus.com> Message-ID: <3EEABE8A.3040102@aljex.com> Stephen Williams wrote: > priyag at newgen.co.in said: > >>I have an interface for scanner on TWAIN protocol for windows. Now i >>need to port it on the LINUX. > > > The TWAIN working group occasionally wonders about porting TWAIN to > Linux, or defining a Linux variant of TWAIN. The former is iffy due > to integration with the Windows message pump, and the latter comes > with a lack of motivation from the involved parties. > > There is a SaneTWAIN datasource for Windows that allows Windows TWAIN > apps access scanners over the network via SANE and the scanner's SANE > driver, but I've not heard of any Linux version of that. If to write > such a thing, the TWG might be interested. I saw TWAIN on Linux at the AIIM show the year before this last one. These people may know something about it: http://www.jflinc.com/ Since the booth where I saw this had a guy from this company working it, I later went on to buy a copy of their twain library for a windows/unix/scanning project I was working on(1). ------- (1) text-based unix database app (written in filePro) sends a escape-sequence to either FacetWin or AnzioLite/AnzioWin terminal emulators to run a command. command is like: "aljex_scan P:/CompanyX/DocTypeY/DocNumZ-PageN.tif" aka "aljex_scan P:/united/invc/129003-4.tif" aljex_scan is hard-coded to scan a single sheet at fax-quality letter-size and output the file given on the command-line. P: is on the server thanks to FacetWin or Samba. To view the scanned docs I made a pair of pretty simple cgi scripts. one shows a table of thumbnails of all images found with requested doctype & docnumber, click on a thumbnail and the other cgi script displays the image in a single img tage with witdh=100% so the "print" button on the web browser prints a full proper-size copy regardless what the window looks like. the unix app sends the "run-program" sequence to the terminal emulator, with an argument of: "start http://server/cgi-bin/viewthm?encryptedjunk where the cgi decrypts the query string and gets basically a path to the images minus the page numbers. this cgi generates a table of thumbnails and links where the link is the another cgi script and encrypted query string to view a particular page in full-size. (both scripts are very light-weight, just ksh. no perl, but do use sort and ls) The documents are given path & filenames based on the file & they are using within the app. The image viewer is just their web browser (images are converted to png, and png thumbnails generated on the server immediately after being saved). The scanner settings are all hard-coded in the little VB app I put on PC's that have scanners. Voila. plain old unix app now has scanned documents, and users don't have to learn 10 minutes of new material to use it, since the "document management" is just piggybacked off the existing app that they already know how to navigate. Merely now some of their screens have a new hot-key & pull-down menu to "scan/view/fax/email/print/administer". -- Brian K. White -- brian at aljex.com -- http://www.aljex.com/bkw/ +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani From crapsite at gmx.net Sat Jun 14 13:34:40 2003 From: crapsite at gmx.net (Michael Herder) Date: Sat, 14 Jun 2003 14:34:40 +0200 Subject: [sane-devel] [Info] Microstar MR 9791 Message-ID: <20030614123502.1BB6B22@panda.mostang.com> Hi, for the archive: it has been reported, that the Microstar MR 9791 scanner works with the artec_eplus48u backend (thanks to Jan-Oliver Bohnert). and to Henning: It seems, that this is just another Medion brand; www.microstar.de directs me to www.medion.de at least. Concerning the desc file, should we just add this to mfg "Medion/Lifetec/Tevion/Cytron" ? (My guess is, that there are also Microstar models, that work with your gt68xx backend). bb Michael From henning at meier-geinitz.de Sat Jun 14 13:59:56 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 14 Jun 2003 14:59:56 +0200 Subject: [sane-devel] [Info] Microstar MR 9791 In-Reply-To: <20030614123502.1BB6B22@panda.mostang.com> References: <20030614123502.1BB6B22@panda.mostang.com> Message-ID: <20030614125956.GC7241@meier-geinitz.de> Hi, On Sat, Jun 14, 2003 at 02:34:40PM +0200, Michael Herder wrote: > it has been reported, that the Microstar MR 9791 scanner works with the > artec_eplus48u backend (thanks to Jan-Oliver Bohnert). Is this a new scanner? Where was it bought? Is the number correct? I'm asking because google knows nothing about this scanner and that's quite strange. > It seems, that this is just another Medion brand; www.microstar.de directs > me to www.medion.de at least. Correct, the domain is registered by: domain: microstar.de descr: MEDION AG > Concerning the desc file, should we just add this to > mfg "Medion/Lifetec/Tevion/Cytron" ? I propose to use a separate "Microstar" manufacturer for now. If more Microstar products pop up or Medion products are sold under the same number as Microstar products we can merge them. The idea of the merged entry is that Medion uses the same numbers for different labels. When we are sure that it's the same with Microstar, we can merge it. Merging means changing some more .desc files. > (My guess is, that there are also Microstar models, that work with > your gt68xx backend). Maybe. However, I haven't ever heard of Microstar (no reports yet). Bye, Henning From henning at meier-geinitz.de Sat Jun 14 14:47:33 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 14 Jun 2003 15:47:33 +0200 Subject: [sane-devel] ANNOUNCE: GTK Application for troubleshooting SANE problems Message-ID: <20030614134733.GA4347@meier-geinitz.de> Hi, I wanted to do some GTK2 programming and thought a little troubleshooting tool for sane-backends may help. The idea is to have a user-friendly tool that gathers all necessary information about the system and SANE installation and tells the user what might be wrong. sane-troubleshoot can be found http://www.meier-geinitz.de/sane/sts/ Please test and tell me if something doesn't work. Spelling and other corrections are also welcome. For a description, I just append the README. Bye, Henning This is the README of sane-troubleshoot. * What's the purpose of this program? It tries to find out what's wrong with your installation of SANE. It checks for some common mistakes and explains what to do to fix them and where to find documentation and help. It writes everything it finds out to a logfile. It's NOT an installation wizard as it doesn't change any files. It's intended to be used for scanners, but may also work with other devices supported by SANE. Currently it's in early alpha stage and is only tested on Linux/i386. * How is it used? Just run ./sane-troubleshoot. You'll need gtk2.0 (http://www.gtk.org). If you get an error about missing libraries you may need to build from source (see below). * How to build You need gtk-2.0 including the development headers. Just enter "make". There is no installation target yet. * What kind of tests does it do? (+ means: works, - means: planned) + Checks if SANE libraries, headers and config files are installed + Checks for multiple installations + Check, if libsane can be loaded + Check for the version of sane-backends + Try to open the test backend + List all scanners that are found by SANE, if the scanner is found: + find out the backend + enable debugging + try to scan a small image, list all errors - If the scanner isn't found - list known manufacturers, select one - list known models, select one - If the scanner is known: - find out the backend - check if it's in dll - find out the type of scanner - try to get SCSI/USB sane-find-scanner-like output - check permissions - If the scanner isn't known, warn about not supported - check libsub, /proc/bus/usb, /proc/scsi/scsi From nakal at web.de Sun Jun 15 00:27:59 2003 From: nakal at web.de (Nakal) Date: Sun, 15 Jun 2003 01:27:59 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EE851A0.CCA64E53@satzbau-gmbh.de> References: <200306102317.58064.nakal@web.de> <200306111902.41911.cinek@gmx.de> <3EE851A0.CCA64E53@satzbau-gmbh.de> Message-ID: <200306150127.59523.nakal@web.de> On Thursday 12 June 2003 12:10, abel deuring wrote: > A long shot: IIRC, these Microtek scanners may freeze, if you access > them with another LUN than 0 -- but they show up with all LUN values > from 0 to 7. So, if any backend tries to access the scanner with a > non-zero LUN, you'll have an unaccessible scanner. I don't know any > details, but *if* a SCSI command to a non-zero LUN confuses the scanner > in a way that the entire SCSI bus is blocked, worse errors may occur, > e.g., the disk with the root partition may be unaccessible. So it's best > to connect these cheap scanners to their own SCSI bus. OK. I did that. I disconnected all devices except the scanner. I get still same effect. > And you should tell FreeBSD not to look for all LUNs of the scanner > while it tries to detect devices on the SCSI bus. Yupp, I did that too, still same. It still gets timeout. I found out that I can scan gray pictures, because it's only one pass. It works perfectly! But as soon as the scanner tries another pass (e.g. color mode) then it does not react (like it forgot the last SCSI command it got). It does not freeze. The scanner is simply idle. I think, sane should repeat the SCSI-command until it succeeds and gets ACK and not just wait for ACK, because there won't come any as long as the scanner moves back the carriage. I can directly start another scan after pressing control+C. There is no problem, but it will always get timeout while initializing the scan for the second pass in 3-pass mode. I remember that earlier (1 or 2 years ago) when I used Linux, sane worked with my microtek without problems. Martin From crapsite at gmx.net Sun Jun 15 04:35:39 2003 From: crapsite at gmx.net (Michael Herder) Date: Sun, 15 Jun 2003 05:35:39 +0200 Subject: [sane-devel] [Info] Microstar MR 9791 Message-ID: <20030615033931.D928818B@panda.mostang.com> Henning Meier-Geinitz, Samstag, 14. Juni 2003 14:59: (sorry for sending this mail in private; I was using KMails "l" button though) >?Hi, > >?On Sat, Jun 14, 2003 at 02:34:40PM +0200, Michael Herder wrote: >?> it has been reported, that the Microstar MR 9791 scanner works with the >?> artec_eplus48u backend (thanks to Jan-Oliver Bohnert). > >?Is this a new scanner? Where was it bought? Is the number correct? I'm >?asking because google knows nothing about this scanner and that's >?quite strange. I was told, that the scanner was bought at "Kaufland", June 2002. It's in fact an Artec E+ 48u (same pid,vid). Probably a device, which some discounter sells for one week, and that's it. >?> It seems, that this is just another Medion brand; www.microstar.de >?> directs me to www.medion.de at least. > >?Correct, the domain is registered by: >?domain: ? ? ?microstar.de >?descr: ? ? ? MEDION AG > >?> Concerning the desc file, should we just add this to >?> mfg "Medion/Lifetec/Tevion/Cytron" ? > >?I propose to use a separate "Microstar" manufacturer for now. If more >?Microstar products pop up or Medion products are sold under the same >?number as Microstar products we can merge them. Ok, I will do this. Thanks for your reply. bb Michael From oliver.rauch at rauch-domain.de Sun Jun 15 16:26:49 2003 From: oliver.rauch at rauch-domain.de (Oliver Rauch) Date: Sun, 15 Jun 2003 17:26:49 +0200 Subject: [sane-devel] multiple images on XSane In-Reply-To: <000601c32e4a$6e9dd180$a8ec403e@default> References: <20030601132533.21859.53611.Mailman@panda.mostang.com> <000601c32e4a$6e9dd180$a8ec403e@default> Message-ID: <200306151726.49165.oliver.rauch@rauch-domain.de> > fredjb at FJBrooks:~> ls -l /usr/local/bin > drwxr-xr-x 9 root root 1344 2003-06-05 16:56 xsane-0.90 you did not install xsane, it looks like you copied the source directory to /usr/local/bin/ To compile xsane you have to unpack it in a directory of your choice, eg /tmp/xsane-0.90 then you enter this directory and do ./configure make to install it you do (may be as root) make install Oliver From oliver.rauch at rauch-domain.de Sun Jun 15 18:24:13 2003 From: oliver.rauch at rauch-domain.de (Oliver Rauch) Date: Sun, 15 Jun 2003 19:24:13 +0200 Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030613073344.999.qmail@web20608.mail.yahoo.com> References: <20030613073344.999.qmail@web20608.mail.yahoo.com> Message-ID: <200306151924.13177.oliver.rauch@rauch-domain.de> Please can you find out if this depends on the selected area (or size) and the selected resolution. Oliver On Friday 13 June 2003 09:33, ope wrote: > I have an UMAX Astra 2200 scanner that I connecting to > through USB. My problem is basically this: > > When I use xsane I can preview as many times as I want > without any problems. However, once I actually try to > scan I sometimes have success and sometimes don't. > When I can't successfully scan what happens is that > the scanner runs, the lamp moves completely down and > back again, the 'REceiving RGB Data' progress bar is > just about complete and then xsane completely freezes. > > Sometimes if I just leave it for 5-10 minutes the > scanned image eventually pops up other times I can > leave it for more than an hour and the application is > still frozen. > > Here is what I see in messages: > kernel: hub.c: USB new device connect on bus2/2, > assigned device number 7 > kernel: usb.c: USB device 7 (vend/prod 0x1606/0x230) > is not claimed by any active driver. > kernel: usb.c: registered new driver usbscanner > kernel: scanner.c: 0.4.6:USB Scanner Driver > kernel: usb_control/bulk_msg: timeout > last message repeated 2 times > last message repeated 3 times > ... > kernel: scanner.c: read_scanner(0): excessive NAK's > received > > sane-find-scanner shows: > found USB scanner (vendor=0x1606, product=0x0230) at > /dev/usb/scanner0 > > > __________________________________ > Do you Yahoo!? > Yahoo! Calendar - Free online calendar with sync to Outlook(TM). > http://calendar.yahoo.com > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel -- http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:Oliver.Rauch at Rauch-Domain.DE From adeuring at gmx.net Sun Jun 15 21:20:40 2003 From: adeuring at gmx.net (abel deuring) Date: Sun, 15 Jun 2003 22:20:40 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306150127.59523.nakal@web.de> References: <200306102317.58064.nakal@web.de> <200306111902.41911.cinek@gmx.de> <3EE851A0.CCA64E53@satzbau-gmbh.de> <200306150127.59523.nakal@web.de> Message-ID: <3EECD518.6000000@gmx.net> Nakal wrote: >>And you should tell FreeBSD not to look for all LUNs of the scanner >>while it tries to detect devices on the SCSI bus. > > > Yupp, I did that too, still same. It still gets timeout. I found out that I > can scan gray pictures, because it's only one pass. It works perfectly! But > as soon as the scanner tries another pass (e.g. color mode) then it does not > react (like it forgot the last SCSI command it got). It does not freeze. The > scanner is simply idle. > > I think, sane should repeat the SCSI-command until it succeeds and gets ACK > and not just wait for ACK, because there won't come any as long as the > scanner moves back the carriage. I can directly start another scan after > pressing control+C. There is no problem, but it will always get timeout while > initializing the scan for the second pass in 3-pass mode. > > I remember that earlier (1 or 2 years ago) when I used Linux, sane worked with > my microtek without problems. That could be due to different timeout settings. Older versions of Sane had different SCSI command timeoit settings for different operating systems. This is meanwhile "unified" to 2 minutes, which might be too small for the Scanmaker II. IIRC, the delay between two scan passes is really long. So you could try to increase that time to 3 or 4 minutes or whatever might be appropriate. You can do this by setting the environment variable SANE_SCSICMD_TIMEOUT to the timeout value (in seconds). Abel From nakal at web.de Mon Jun 16 00:45:01 2003 From: nakal at web.de (Nakal) Date: Mon, 16 Jun 2003 01:45:01 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EECD518.6000000@gmx.net> References: <200306102317.58064.nakal@web.de> <200306150127.59523.nakal@web.de> <3EECD518.6000000@gmx.net> Message-ID: <200306160145.01370.nakal@web.de> On Sunday 15 June 2003 22:20, abel deuring wrote: > IIRC, the delay between two scan passes is really long. I don't think so. It always was working fast. Usually about 1 sec after the pass the scanner made some switching noises and then recalibrated the position and processed the next pass. The effect now is that the scanner does not do anything after returning to the start position. It's like it does not listen anymore. > So you could try to increase that time to 3 or 4 minutes or whatever > might be appropriate. You can do this by setting the environment > variable SANE_SCSICMD_TIMEOUT to the timeout value (in seconds). This environment variable seems not to have any effect on FreeBSD. I made some additional logs for you. Perhaps they are more informative. The command was: SANE_DEBUG_DLL=128 SANE_DEBUG_SANEI_SCSI=128 scanimage -v -d 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log 2>&1 These lines might be interesting: [sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 [sanei_scsi] sanei_scsi_cmd: scsi returned with status 16 (Look at the rest of it inside the attachment.) Thanks for your patience with me, Martin :) -------------- next part -------------- A non-text attachment was scrubbed... Name: microtek-on-fbsd48.log.gz Type: application/x-gzip Size: 819 bytes Desc: not available URL: From aneeshmraj at hotmail.com Mon Jun 16 06:29:05 2003 From: aneeshmraj at hotmail.com (aneesh m raj) Date: Mon, 16 Jun 2003 10:59:05 +0530 Subject: [sane-devel] problem with UMAX 2000P scanner References: <20030613125548.GE3579@meier-geinitz.de> Message-ID: Hi, I have tried scanimage -L but it also says "No scanner detected" . when I use umax_pp -p -t 1 the scanner is detected. umax_pp is not commented in dll.conf. Regards Aneesh ----- Original Message ----- From: "Henning Meier-Geinitz" To: Sent: Friday, June 13, 2003 6:25 PM Subject: Re: [sane-devel] problem with UMAX 2000P scanner > Hi, > > On Fri, Jun 13, 2003 at 05:16:18PM +0530, aneesh m raj wrote: > > Thank u it worked the mode was in ECP+EPP . Im using a program to > > detect scanner devices but I cant retrieve the device by calling > > sane_get_devices() function .The SANE_Device structure is NULL. > > Try "scanimage -L" to make sure it's not a bug in your program. > First guess: "umax_pp" is commented out in dll.conf. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > From stef-listes at wanadoo.fr Mon Jun 16 08:49:10 2003 From: stef-listes at wanadoo.fr (stef) Date: Mon, 16 Jun 2003 07:49:10 +0000 Subject: [sane-devel] problem with UMAX 2000P scanner In-Reply-To: References: <20030613125548.GE3579@meier-geinitz.de> Message-ID: <20030616074910.GA707@wanadoo.fr> On Mon, Jun 16, 2003 at 10:59:05AM +0530, aneesh m raj wrote: > Hi, > I have tried scanimage -L but it also says "No scanner detected" . when I > use umax_pp -p -t 1 the scanner is detected. umax_pp is not commented in > dll.conf. > Regards > Aneesh > ----- Original Message ----- > From: "Henning Meier-Geinitz" > To: > Sent: Friday, June 13, 2003 6:25 PM > Subject: Re: [sane-devel] problem with UMAX 2000P scanner > Hello, maybe there are several instances of dll.conf on your system, and the one used by scanimage may have umax_pp commented out. Also, 'umax_pp -p -t 1' does direct hardware access, while the backend is configured by default to use ppdev character device. You can change this by editing umax_pp.conf and change the 'port' option to 'port 0x378', if 0x378 is really your parport address. Regards, Stef > > > Hi, > > > > On Fri, Jun 13, 2003 at 05:16:18PM +0530, aneesh m raj wrote: > > > Thank u it worked the mode was in ECP+EPP . Im using a program to > > > detect scanner devices but I cant retrieve the device by calling > > > sane_get_devices() function .The SANE_Device structure is NULL. > > > > Try "scanimage -L" to make sure it's not a bug in your program. > > First guess: "umax_pp" is commented out in dll.conf. > > > > Bye, > > Henning > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel at www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From aneeshmraj at hotmail.com Mon Jun 16 07:10:52 2003 From: aneeshmraj at hotmail.com (aneesh m raj) Date: Mon, 16 Jun 2003 11:40:52 +0530 Subject: [sane-devel] problem with UMAX 2000P scanner References: <20030613125548.GE3579@meier-geinitz.de> <20030616074910.GA707@wanadoo.fr> Message-ID: Thank u everybody it worked , there was more than one instance of dll.conf and umax_pp was commented in the instance of dll.conf that was actually used by the scanimage. ----- Original Message ----- From: "stef" To: Sent: Monday, June 16, 2003 1:19 PM Subject: Re: [sane-devel] problem with UMAX 2000P scanner > On Mon, Jun 16, 2003 at 10:59:05AM +0530, aneesh m raj wrote: > > Hi, > > I have tried scanimage -L but it also says "No scanner detected" . when I > > use umax_pp -p -t 1 the scanner is detected. umax_pp is not commented in > > dll.conf. > > Regards > > Aneesh > > ----- Original Message ----- > > From: "Henning Meier-Geinitz" > > To: > > Sent: Friday, June 13, 2003 6:25 PM > > Subject: Re: [sane-devel] problem with UMAX 2000P scanner > > > > Hello, > > maybe there are several instances of dll.conf on your system, and the one > used by scanimage may have umax_pp commented out. Also, 'umax_pp -p -t 1' does > direct hardware access, while the backend is configured by default to use ppdev > character device. You can change this by editing umax_pp.conf and change the 'port' > option to 'port 0x378', if 0x378 is really your parport address. > > Regards, > Stef > > > > > > Hi, > > > > > > On Fri, Jun 13, 2003 at 05:16:18PM +0530, aneesh m raj wrote: > > > > Thank u it worked the mode was in ECP+EPP . Im using a program to > > > > detect scanner devices but I cant retrieve the device by calling > > > > sane_get_devices() function .The SANE_Device structure is NULL. > > > > > > Try "scanimage -L" to make sure it's not a bug in your program. > > > First guess: "umax_pp" is commented out in dll.conf. > > > > > > Bye, > > > Henning > > > _______________________________________________ > > > Sane-devel mailing list > > > Sane-devel at www.mostang.com > > > http://www.mostang.com/mailman/listinfo/sane-devel > > > > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel at www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > From cpinto at yimports.com Mon Jun 16 12:20:39 2003 From: cpinto at yimports.com (Celso Pinto) Date: Mon, 16 Jun 2003 12:20:39 +0100 Subject: [sane-devel] HP Scanjet 2300c Message-ID: <001d01c333f9$5179dcc0$7800a8c0@cpinto> I all, I noticed there's no support for the HP 2300c scanner. I'd be very glad to develop the driver but I have no experience at all developing for Linux so i'd really appreciate if someone could just please spend some time explaing me how to setup a development environment and i'll give my best to bring a driver as soon as possible (after all my 2300c scanner is gathering dust :) ). Regards, Celso Pinto From henning at meier-geinitz.de Mon Jun 16 15:07:16 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 16 Jun 2003 16:07:16 +0200 Subject: [sane-devel] HP Scanjet 2300c In-Reply-To: <001d01c333f9$5179dcc0$7800a8c0@cpinto> References: <001d01c333f9$5179dcc0$7800a8c0@cpinto> Message-ID: <20030616140716.GD15421@meier-geinitz.de> Hi, On Mon, Jun 16, 2003 at 12:20:39PM +0100, Celso Pinto wrote: > I all, I noticed there's no support for the HP 2300c scanner. I'd be > very glad to develop the driver but I have no experience at all > developing for Linux so i'd really appreciate if someone could just > please spend some time explaing me how to setup a development > environment and i'll give my best to bring a driver as soon as possible > (after all my 2300c scanner is gathering dust :) ). The biggest problem usually is to find out which protocol the scanner speaks. If you can't get a detailed protocol description from the manufacturer (unlikely), you'll have to "sniff" the USb connection under Windows. Some links: http://www.meier-geinitz.de/sane/misc/develop.html http://www.meier-geinitz.de/sane/misc/unsupported.html When you have gathered some protocoll data, try to understand what's going on. E.g. which series of transfers moves the scan head to the beginning and how to scan in gray mode. Concerning programming on Linux: a compiler (gcc), an editor, some libraries like libusb and the SANE source code will be enough. I recommend to start with wroting a simple C program that uses sanei/sanei_usb.c to wrire some stuff to the scanner and read the results. sanei_usb is documented here: http://sanei.meier-geinitz.de/sanei__usb_8h.html And please inform us about what you do. If possible, set up a website with all the information you find so others can help or use the information. Bye, Henning From adeuring at gmx.net Mon Jun 16 20:16:55 2003 From: adeuring at gmx.net (abel deuring) Date: Mon, 16 Jun 2003 21:16:55 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306160145.01370.nakal@web.de> References: <200306102317.58064.nakal@web.de> <200306150127.59523.nakal@web.de> <3EECD518.6000000@gmx.net> <200306160145.01370.nakal@web.de> Message-ID: <3EEE17A7.6080301@gmx.net> Nakal schrieb: > On Sunday 15 June 2003 22:20, abel deuring wrote: > > >>IIRC, the delay between two scan passes is really long. > > > I don't think so. It always was working fast. Usually about 1 sec after > the pass the scanner made some switching noises and then recalibrated > the position and processed the next pass. What I meant with "time between two scan passes" is the time between the last read command from one scan pass (or perhaps a command telling the scanner that this scan pass is ove) and the execution of the next command. I had only a very short look into microtek.c, so I may be wrong, but as I understand it, the last command for a scan pass is a "read", and the next command is a "scan start". The "scan start" command is probably issued immediately after the last read from the previous scan pass, so the duration of this "start" command is the time required to move the scan head back, to switch the color filter and then to do the "usual things" for the scan start, like perhaps recalibrating the CCD, moving the scan head into the start position, and whatever else. And this time is IIRC in the order of a minute or so, perhaps even more. > > The effect now is that the scanner does not do anything after returning > to the start position. It's like it does not listen anymore. > > >>So you could try to increase that time to 3 or 4 minutes or whatever >>might be appropriate. You can do this by setting the environment >>variable SANE_SCSICMD_TIMEOUT to the timeout value (in seconds). > > > This environment variable seems not to have any effect on FreeBSD. Which values did you try? > > > I made some additional logs for you. Perhaps they are more informative. > The command was: > SANE_DEBUG_DLL=128 SANE_DEBUG_SANEI_SCSI=128 scanimage -v -d > 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log > 2>&1 > > These lines might be interesting: > [sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 > [sanei_scsi] sanei_scsi_cmd: scsi returned with status 16 The first error occurs immediately after a "read", and this at least does not contradict my suspicions about the timeout problems. But we could get a better clue, if you add a "SANE_DEBUG_MICROTEK=255". The DLL debug output is less interesting. Abel From nakal at web.de Mon Jun 16 22:22:35 2003 From: nakal at web.de (Nakal) Date: Mon, 16 Jun 2003 23:22:35 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EEE17A7.6080301@gmx.net> References: <200306102317.58064.nakal@web.de> <200306160145.01370.nakal@web.de> <3EEE17A7.6080301@gmx.net> Message-ID: <200306162322.35147.nakal@web.de> On Monday 16 June 2003 21:16, abel deuring wrote: > The first error occurs immediately after a "read", and this at least > does not contradict my suspicions about the timeout problems. But we > could get a better clue, if you add a "SANE_DEBUG_MICROTEK=255". The > DLL debug output is less interesting. OK. I attached the output of the command: SANE_DEBUG_MICROTEK=255 SANE_SCSICMD_TIMEOUT=180 scanimage -v -d 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log 2>&1 Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: microtek-on-fbsd48.log.gz Type: application/x-gzip Size: 2660 bytes Desc: not available URL: From adeuring at gmx.net Mon Jun 16 23:16:22 2003 From: adeuring at gmx.net (abel deuring) Date: Tue, 17 Jun 2003 00:16:22 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306162322.35147.nakal@web.de> References: <200306102317.58064.nakal@web.de> <200306160145.01370.nakal@web.de> <3EEE17A7.6080301@gmx.net> <200306162322.35147.nakal@web.de> Message-ID: <3EEE41B6.4050606@gmx.net> Nakal wrote: > On Monday 16 June 2003 21:16, abel deuring wrote: > > >>The first error occurs immediately after a "read", and this at least >>does not contradict my suspicions about the timeout problems. But we >>could get a better clue, if you add a "SANE_DEBUG_MICROTEK=255". The >>DLL debug output is less interesting. > > > OK. I attached the output of the command: > SANE_DEBUG_MICROTEK=255 SANE_SCSICMD_TIMEOUT=180 scanimage -v -d > 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log > 2>&1 What I meant, was a combination of the log output of the Sane SCVSI library and of the Microtek backend ;) This allows in many cases to see, which SCSI command issued from a certain function of the backend causes an error. But from the log data of microtek backend alone I think that this is a pure backend problem. This is the relevant part: [microtek] get_scan_status(6): 27, 0, 20736 -> #0 [microtek] > 1b 0 0 0 51 0 [microtek] get_scan_status: busy, retry in 5... [microtek] SENSE! fd = 0 [microtek] sense = 00 00 00 00. [microtek] get_scan_status(6): 27, 0, 20736 -> #1 [microtek] > 1b 0 0 0 51 0 [microtek] get_scan_status: busy, retry in 10... [microtek] SENSE! fd = 0 [microtek] sense = 00 00 00 00. [microtek] get_scan_status(6): 27, 0, 20736 -> #2 [microtek] > 1b 0 0 0 51 0 [microtek] get_scan_status: busy, retry in 15... [microtek] SENSE! fd = 0 [microtek] sense = 00 00 00 00. [microtek] get_scan_status(6): 27, 0, 20736 -> #3 [microtek] > 1b 0 0 0 51 0 [microtek] get_scan_status: busy, retry in 20... [microtek] sane_start: get_scan_status fails The lines "get_scan_status: busy, retry..." are only printed, if the SCSI command "get scan status" does not produce a SCSI error (i.e., nothing went wrong during the transport of the SCSI data from the scanner to the application). So the SCSI system (kernel, kernel drivers or Sane's SCSI libraray) is probably not involved, but the get_scan_status in the Microtek backend is perhaps a bit too "impatient". But the maintainer of the Microtek backend can probably give a more qualified comment. Abel From ope557 at yahoo.com Tue Jun 17 08:39:15 2003 From: ope557 at yahoo.com (ope) Date: Tue, 17 Jun 2003 00:39:15 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <200306151924.13177.oliver.rauch@rauch-domain.de> Message-ID: <20030617073915.89884.qmail@web20605.mail.yahoo.com> Sorry for taking so long to respond... It definately works better (or worse) if I adjust the scan resolution. I set resolution set to 100 and did not have any problems. I normally expect to run into problems after about 2-3 scans and never get more than 5 scans without problems. After adjusting the resolution to 100 I scanned more than 10 times without a single problem. Then I played around with other resolutions and ran into problems with any resloution setting I chose. Changing selected areas does not seem to affect results in any circumstance. I have also noticed another thing that is worth mentioning. At one point when the xsane seemed to be stuck I tried unplugging the scanner from the USB port. I was expecting xsane to fail and close down. What actually did happen was that the complete scanned image instantly popped up in the viewer and xsane was running as if nothing has happened. Just for fun I tried it couple more times and had the same results each time. It appears to me that that the scan is essentially complete at the point that it is freezing. Thanks, ope --- Oliver Rauch wrote: > > Please can you find out if this depends on the > selected area (or size) and the selected resolution. > > Oliver > > On Friday 13 June 2003 09:33, ope wrote: > > I have an UMAX Astra 2200 scanner that I > connecting to > > through USB. My problem is basically this: > > > > When I use xsane I can preview as many times as I > want > > without any problems. However, once I actually > try to > > scan I sometimes have success and sometimes don't. > > When I can't successfully scan what happens is > that > > the scanner runs, the lamp moves completely down > and > > back again, the 'REceiving RGB Data' progress bar > is > > just about complete and then xsane completely > freezes. > > > > Sometimes if I just leave it for 5-10 minutes the > > scanned image eventually pops up other times I can > > leave it for more than an hour and the application > is > > still frozen. > > > > Here is what I see in messages: > > kernel: hub.c: USB new device connect on bus2/2, > > assigned device number 7 > > kernel: usb.c: USB device 7 (vend/prod > 0x1606/0x230) > > is not claimed by any active driver. > > kernel: usb.c: registered new driver usbscanner > > kernel: scanner.c: 0.4.6:USB Scanner Driver > > kernel: usb_control/bulk_msg: timeout > > last message repeated 2 times > > last message repeated 3 times > > ... > > kernel: scanner.c: read_scanner(0): excessive > NAK's > > received > > > > sane-find-scanner shows: > > found USB scanner (vendor=0x1606, product=0x0230) > at > > /dev/usb/scanner0 > > > > > > __________________________________ > > Do you Yahoo!? > > Yahoo! Calendar - Free online calendar with sync > to Outlook(TM). > > http://calendar.yahoo.com > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel at www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > -- > http://www.xsane.org > http://www.mostang.com/sane > http://www.rauch-domain.de > mailto:Oliver.Rauch at Rauch-Domain.DE __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From nakal at web.de Tue Jun 17 16:24:52 2003 From: nakal at web.de (Nakal) Date: Tue, 17 Jun 2003 17:24:52 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EEE41B6.4050606@gmx.net> References: <200306102317.58064.nakal@web.de> <200306162322.35147.nakal@web.de> <3EEE41B6.4050606@gmx.net> Message-ID: <200306171724.52572.nakal@web.de> On Tuesday 17 June 2003 00:16, abel deuring wrote: > What I meant, was a combination of the log output of the Sane SCVSI > library and of the Microtek backend ;) This is the output of: SANE_DEBUG_MICROTEK=255 SANE_SCSICMD_TIMEOUT=180 SANE_DEBUG_SANEI_SCSI=128 scanimage -v -d 'microtek:/dev/scanner' --mode color -y 50 > microtek-on-fbsd48.log 2>&1 I'm sorry for flooding the mailing list with my logs, Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: microtek-on-fbsd48.log.gz Type: application/x-gzip Size: 2729 bytes Desc: not available URL: From andras at users.sourceforge.net Tue Jun 17 21:20:27 2003 From: andras at users.sourceforge.net (Major A) Date: Tue, 17 Jun 2003 21:20:27 +0100 Subject: [sane-devel] Re: Nikon Coolscan IV and scanner.c funky result -75 In-Reply-To: References: Message-ID: <20030617202027.GC2162@ventus.lan> Dmitri, Hope you don't mind me also sending a copy to the SANE list. > often I get this strange error : scanner.c blah funky result:-75 > blah. I have been getting this for a while and once it happens, OK, that sounds familiar, but I still don't know a solution to it. The tricky bit about USB is that if there's a bug in one of the generic drivers, it might go unnoticed for very long because most hardware doesn't trigger it. I'm pretty sure this has to do with the USB system in Linux, and I think it has been reported to the USB team. A user-level program like SANE should not be allowed to crash the computer like that, so it's certainly not exclusively a SANE problem. > the only solution is to reboot - the scanner module cannot be > unloaded, it says it is always in use. The scanner module is more and more obsolete. Most backends in newer SANE releases (from 1.0.11 I think) use libusb, which on Linux uses usbdevfs to access the hardware. This should be much more robust. Could you please try the latest SANE release and make sure libusb (including development files) is installed when you build it? > scanner: HP5300C and that works just great with hpusb driver. Also, > I have a Nikon (speaking of the brand loyalty :) D100 digital camera > and just managed to get it connected (USB) to linux using gphoto2 > and hotplug. They both work great - so it seems that I got the USB > system right. Unfortunately, as I said above, this is not a guarantee that the USB system works all right. I've been using the VIA USB 2.0 controller on my mainboard for months now without any trouble, but the moment I connected an external USB 2.0 hard disk to it, things started going very wrong. The solution is still outstanding, the USB team are working on it... > VueScan. Great program, I just wish to have bought it when it was > only $40 for lifetime updates, now it is $80 for a year :( Seems that SANE is finally taking away some of Ed's income... Andras =========================================================================== Major Andras e-mail: andras at users.sourceforge.net www: http://andras.webhop.org/ =========================================================================== From henning at meier-geinitz.de Tue Jun 17 22:02:21 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 17 Jun 2003 23:02:21 +0200 Subject: [sane-devel] Re: Nikon Coolscan IV and scanner.c funky result -75 In-Reply-To: <20030617202027.GC2162@ventus.lan> References: <20030617202027.GC2162@ventus.lan> Message-ID: <20030617210221.GA4027@meier-geinitz.de> Hi, On Tue, Jun 17, 2003 at 09:20:27PM +0100, Major A wrote: > Hope you don't mind me also sending a copy to the SANE list. > > > often I get this strange error : scanner.c blah funky result:-75 > > blah. I have been getting this for a while and once it happens, Error 75 is EOVERFLOW. That's usually caused in connection with UHCI USB controllers in "babble" condition. That means something happend on the USB that the device (or the host) did not expect. It seems to happen with some USB devices when you send too long buffers or read more data than the scanner expected. > OK, that sounds familiar, but I still don't know a solution to it. The > tricky bit about USB is that if there's a bug in one of the generic > drivers, it might go unnoticed for very long because most hardware > doesn't trigger it. I'm pretty sure this has to do with the USB system > in Linux, and I think it has been reported to the USB team. There is a known problem with the kernel USB driver that occurs, when the user space program tries to read more data than the scanner wants to provide. Well, it's not really a problem in my view, more a kind of bad interaction. Some discussion about this can be found on the linux-usb-users lists. I've asked the old maintainers and they say that the behaviour is intended. I'll try to summarize the problem (copied from a mail to linux-usb-users): | We want to read 42448 bytes (e.g. two scan lines). The buffer size is | 32768 so that's the maximum we can do in one turn. The scanner returns | only 21224 bytes (probably one scan line). So far that's ok. | | The reason is that the next read reads only 9680 bytes instead of | 21224. The scanner doesn't seem to be able to handle this. So the scanner doesn't seem to like reads different from the size of one scan line (?). I gueess the backend shouldn't try to read more than the scanner is able to return. While the scanner driver's behaviour isn't the optimum (it could try to read 21224 bytes twice), I don't think it's wrong. There was a short read and that's a way to signal it. > A > user-level program like SANE should not be allowed to crash the > computer like that, so it's certainly not exclusively a SANE problem. That's true. On the other hand the only crash concerning the USB scanner driver is when you open /dev/usb/scanner*, unplug the scanner, and read or write to the scanner. I'm talking about 2.4.21 (and the later -pre versions) here, older versions may have more bugs. > > the only solution is to reboot - the scanner module cannot be > > unloaded, it says it is always in use. Please show me the decoded OOPS message, if it's 2.4.21(-pre). Otherwise updating the kernel may help. > The scanner module is more and more obsolete. Most backends in newer > SANE releases (from 1.0.11 I think) use libusb, They are able to use libusb. If the scanner driver is loaded, it will be used. > which on Linux uses usbdevfs to access the hardware. This should be > much more robust. For most scanners it works better. For some it doesn't (E.g. Mustek 600CU). But basically, you are right. > Could you please try the latest SANE release and make sure > libusb (including development files) is installed when you build it? And tell us the kernel version :-) > > scanner: HP5300C and that works just great with hpusb driver. Different USB driver :-) The Nikon Coolscan 4 seems to be the only scanner with this problem. At least that's the only one I ever got reports for. So I really think it's either a scanner or backend problem. > > Also, > > I have a Nikon (speaking of the brand loyalty :) D100 digital camera > > and just managed to get it connected (USB) to linux using gphoto2 > > and hotplug. They both work great - so it seems that I got the USB > > system right. > > Unfortunately, as I said above, this is not a guarantee that the USB > system works all right. I've been using the VIA USB 2.0 controller on > my mainboard for months now without any trouble, but the moment I > connected an external USB 2.0 hard disk to it, things started going > very wrong. The solution is still outstanding, the USB team are > working on it... I've heard similar reports and they seem to be fixed with 2.4.21. But your milage may vary... > > VueScan. Great program, I just wish to have bought it when it was > > only $40 for lifetime updates, now it is $80 for a year :( > > Seems that SANE is finally taking away some of Ed's income... By the way: The problem with coolscan/kernel scanner driver seems to happen (have happened?) also with vuescan. Looks like a similar scanning routine is used. Bye, Henning From andras at users.sourceforge.net Tue Jun 17 22:26:08 2003 From: andras at users.sourceforge.net (Major A) Date: Tue, 17 Jun 2003 22:26:08 +0100 Subject: [sane-devel] Re: Nikon Coolscan IV and scanner.c funky result -75 In-Reply-To: <20030617210221.GA4027@meier-geinitz.de> References: <20030617202027.GC2162@ventus.lan> <20030617210221.GA4027@meier-geinitz.de> Message-ID: <20030617212608.GD2162@ventus.lan> > I'll try to summarize the problem (copied from a mail to > linux-usb-users): > > | We want to read 42448 bytes (e.g. two scan lines). The buffer size is > | 32768 so that's the maximum we can do in one turn. The scanner returns > | only 21224 bytes (probably one scan line). So far that's ok. > | > | The reason is that the next read reads only 9680 bytes instead of > | 21224. The scanner doesn't seem to be able to handle this. > > So the scanner doesn't seem to like reads different from the size of > one scan line (?). I gueess the backend shouldn't try to read more > than the scanner is able to return. Ah, OK, but Coolscan2 strictly tries to read one scanline at the time. On the LS-40, this is a maximum of 23328 bytes (2916 pixels, 4 channels each, 2 bytes per channel), which is less than 32k. > They are able to use libusb. If the scanner driver is loaded, it will > be used. OK, in that case please make sure the scanner module isn't loaded. > The Nikon Coolscan 4 seems to be the only scanner with this problem. > At least that's the only one I ever got reports for. So I really think > it's either a scanner or backend problem. Hmmm, that would be me... the scanner is a bit silly in the way that it tunnels SCSI commands across USB in a proprietary way, but it seems to work great in most cases, so it's probably not a hardware fault. > > Unfortunately, as I said above, this is not a guarantee that the USB > > system works all right. I've been using the VIA USB 2.0 controller on > > my mainboard for months now without any trouble, but the moment I > > connected an external USB 2.0 hard disk to it, things started going > > very wrong. The solution is still outstanding, the USB team are > > working on it... > > I've heard similar reports and they seem to be fixed with 2.4.21. But > your milage may vary... No, not mine -- in fact, 2.4.20 nearly works, 2.4.21 is totally broken. With a different card, 2.4.21 works just fine... > By the way: The problem with coolscan/kernel scanner driver seems to > happen (have happened?) also with vuescan. Looks like a similar > scanning routine is used. That's right. VueScan also uses (used?) the scanner module, so go figure... Andras =========================================================================== Major Andras e-mail: andras at users.sourceforge.net www: http://andras.webhop.org/ =========================================================================== From adeuring at gmx.net Tue Jun 17 22:30:44 2003 From: adeuring at gmx.net (abel deuring) Date: Tue, 17 Jun 2003 23:30:44 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306171724.52572.nakal@web.de> References: <200306102317.58064.nakal@web.de> <200306162322.35147.nakal@web.de> <3EEE41B6.4050606@gmx.net> <200306171724.52572.nakal@web.de> Message-ID: <3EEF8884.2000805@gmx.net> Nakal wrote: > On Tuesday 17 June 2003 00:16, abel deuring wrote: > > >>What I meant, was a combination of the log output of the Sane SCVSI >>library and of the Microtek backend ;) > > > This is the output of: > SANE_DEBUG_MICROTEK=255 SANE_SCSICMD_TIMEOUT=180 > SANE_DEBUG_SANEI_SCSI=128 scanimage -v -d 'microtek:/dev/scanner' > --mode color -y 50 > microtek-on-fbsd48.log 2>&1 > > I'm sorry for flooding the mailing list with my logs, Never mind, a few kilobytes are OK, IMHO. First a disclaimer for the following stuff: I don't have FreeBSD installed, I used it only rarely, and I never wrote software specifically for FreeBSD. So I am writing as a "backseat driver" ;) Looking through the log, it seems to me that something is wrong in sanei_scsi.c. From your log file: [microtek] .stop_scan... [microtek] SPS:1b 0 0 0 0 0 [sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 [microtek] SENSE! fd = 0 [microtek] sense = 00 00 00 00. scanimage: min/max graylevel value = 21/255 [microtek] sane_start... The "stop scan" command returns an error (the "sanei_scsi" line), and all following SCSI commands return errors too. The interesting point is this: For some the commands we have the line "scsi returned with status 10", for other commands we have the line "scsi returned with status 16". Since the sense handler is called for both status values, I assume that you are using FreeBSD's CAM interface. (The other FreeBSD SCSI interface calls the sense handler of the backend only for a single status value.) This is the relevant part of sanei_scsi.c: if ((ccb->ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_CMP) { SANEI_SCSI_Sense_Handler handler; DBG (1, "sanei_scsi_cmd: scsi returned with status %d\n", (ccb->ccb_h.status & CAM_STATUS_MASK)); if((ccb->ccb_h.status & CAM_STATUS_MASK) == SANE_STATUS_DEVICE_BUSY) return SANE_STATUS_DEVICE_BUSY; handler = fd_info[fd].sense_handler; if (handler) { SANE_Status st = (*handler) (fd, ((u_char*)(&ccb->csio.sense_data)), fd_info[fd].sense_handler_arg); cam_freeccb(ccb); return st; } else return SANE_STATUS_IO_ERROR; } Googling quickly for 'freebsd cam.h', I found a version of cam.h at http://www.freebsd.cz/pub/FreeBSD/branches/4.0-stable/src/sys/cam/cam.h, and found these definitions for the status values 10 and 16: 10 -> CAM_SEL_TIMEOUT, /* Target Selection Timeout */ 16 -> CAM_AUTOSENSE_FAIL = 0x10,/* Autosense: request sense cmd fail */ (definitions of this kind tend to be stable -- but control is better than trust some cases: Martin, can you confirm this for your version of cam.h?) OK, many commands fail with a selection time out. Not very surprising for a slow scanner with probably somewhat dumb firmware ;) This status means that the scanner simply did not accept the SCSI command, so it does not make sense to call the sense handler, but the sense handler is called anyway. (Fortunately, the CAM system sets the sense data to all zero, so that the backend doesn't become completely confused...) If this happens, sanei_scsi_cmd2 should return SANE_STATUS_DEVICE_BUSY, and the backend should retry to issue the command for a few times. It is perhaps enough to change the following part: if((ccb->ccb_h.status & CAM_STATUS_MASK) == SANE_STATUS_DEVICE_BUSY) return SANE_STATUS_DEVICE_BUSY; to if((ccb->ccb_h.status & CAM_STATUS_MASK) == CAM_SEL_TIMEOUT) return SANE_STATUS_DEVICE_BUSY; to fix at least some a part of the problem, but the backend will probably also need some patches... Another point: From reading cam.h, I think that the sense handler should only be called, if the bit CAM_AUTOSNS_VALID is set in ccb_h.status. Generally, I have the impression that the FreeBSD/CAM part of sanei_scsi.c could need a review. But that should be done by somebody who can run Sane under FreeBSD ;) Abel From oliver.rauch at rauch-domain.de Tue Jun 17 22:58:16 2003 From: oliver.rauch at rauch-domain.de (Oliver Rauch) Date: Tue, 17 Jun 2003 23:58:16 +0200 Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030617073915.89884.qmail@web20605.mail.yahoo.com> References: <20030617073915.89884.qmail@web20605.mail.yahoo.com> Message-ID: <200306172358.16932.oliver.rauch@rauch-domain.de> On Tuesday 17 June 2003 09:39, ope wrote: > I have also noticed another thing that is worth > mentioning. At one point when the xsane seemed to be > stuck I tried unplugging the scanner from the USB > port. I was expecting xsane to fail and close down. > What actually did happen was that the complete scanned > image instantly popped up in the viewer and xsane was > running as if nothing has happened. Just for fun I > tried it couple more times and had the same results > each time. It appears to me that that the scan is > essentially complete at the point that it is freezing. This sounds as if there is a problem with the USB communication. Do you get any messages about USB problems in /var/log/messages ? Oliver From henning at meier-geinitz.de Tue Jun 17 23:11:32 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 00:11:32 +0200 Subject: [sane-devel] Re: Nikon Coolscan IV and scanner.c funky result -75 In-Reply-To: <20030617212608.GD2162@ventus.lan> References: <20030617202027.GC2162@ventus.lan> <20030617210221.GA4027@meier-geinitz.de> <20030617212608.GD2162@ventus.lan> Message-ID: <20030617221132.GD4027@meier-geinitz.de> Hi, On Tue, Jun 17, 2003 at 10:26:08PM +0100, Major A wrote: > > I'll try to summarize the problem (copied from a mail to > > linux-usb-users): > > > > | We want to read 42448 bytes (e.g. two scan lines). The buffer size is > > | 32768 so that's the maximum we can do in one turn. The scanner returns > > | only 21224 bytes (probably one scan line). So far that's ok. > > | > > | The reason is that the next read reads only 9680 bytes instead of > > | 21224. The scanner doesn't seem to be able to handle this. > > > > So the scanner doesn't seem to like reads different from the size of > > one scan line (?). I gueess the backend shouldn't try to read more > > than the scanner is able to return. > > Ah, OK, but Coolscan2 strictly tries to read one scanline at the > time. On the LS-40, this is a maximum of 23328 bytes (2916 pixels, 4 > channels each, 2 bytes per channel), which is less than 32k. Ok. I was talking about a log created by vuescan: Mar 18 07:02:26 kletskop kernel: scanner.c: read stats(0): result:0 this_read:32768 partial:21224 count:42448 Mar 18 07:02:26 kletskop kernel: uhci.c: uhci_result_interrupt/bulk() failed with status 500000 [...] Mar 18 07:02:26 kletskop kernel: scanner.c: read stats(0): result:-75 this_read:9680 partial:9680 count:9680 Mar 18 07:02:26 kletskop kernel: scanner.c: read_scanner(0): funky result:-75. Consult Documentation/usb/scanner.txt. Mar 18 07:02:36 kletskop kernel: usb_control/bulk_msg: timeout I remember similar reports about SANE but can't find a log at the moment. Hint for the bug reporter: A kernel logfile would be nice. For that, enable USB debugging in make menuconfig (probably already enabled) and debug messages in drivers/usb/scanner.h. This way we can see what's exactly going on. > > The Nikon Coolscan 4 seems to be the only scanner with this problem. > > At least that's the only one I ever got reports for. So I really think > > it's either a scanner or backend problem. > > Hmmm, that would be me... the scanner is a bit silly in the way that > it tunnels SCSI commands across USB in a proprietary way, but it seems > to work great in most cases, so it's probably not a hardware fault. Maybe it just doesn't like "half-sent" buffers. On the other hand, if you don't send more than one scan line I really don't know what's wrong. > > By the way: The problem with coolscan/kernel scanner driver seems to > > happen (have happened?) also with vuescan. Looks like a similar > > scanning routine is used. > > That's right. VueScan also uses (used?) the scanner module, so go > figure... But vuescan does read more than 32k at once. At least that what's the log shows. Maybe it's a different problem? Bye, Henning From nakal at web.de Wed Jun 18 00:07:59 2003 From: nakal at web.de (Nakal) Date: Wed, 18 Jun 2003 01:07:59 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EEF8884.2000805@gmx.net> References: <200306102317.58064.nakal@web.de> <200306171724.52572.nakal@web.de> <3EEF8884.2000805@gmx.net> Message-ID: <200306180107.59518.nakal@web.de> On Tuesday 17 June 2003 23:30, abel deuring wrote: > First a disclaimer for the following stuff: I don't have FreeBSD > installed, I used it only rarely, and I never wrote software > specifically for FreeBSD. So I am writing as a "backseat driver" ;) Try it :) > I assume that you are using FreeBSD's CAM interface. Yes, that's right. > Googling quickly for 'freebsd cam.h', I found a version of cam.h at > http://www.freebsd.cz/pub/FreeBSD/branches/4.0-stable/src/sys/cam/cam >.h, and found these definitions for the status values 10 and 16: > > 10 -> CAM_SEL_TIMEOUT, /* Target Selection Timeout */ > 16 -> CAM_AUTOSENSE_FAIL = 0x10,/* Autosense: request sense cmd fail > */ > (definitions of this kind tend to be stable -- but control is better > than trust some cases: Martin, can you confirm this for your version > of cam.h?) The values 10 and 16 are still correct, but I'm sure you are using the enums by name. That should be fine, of course. Seems nothing has changed in cam.h since 2000/03/17. Even FreeBSD-current (5.1) seems to use the same values (2002/01/09). You can find the kernel sources for cam here (just in case you haven't found cam.c): ftp://ftp2.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/sys/cam > OK, many commands fail with a selection time out. Not very surprising > for a slow scanner with probably somewhat dumb firmware ;) Firmware? :) No firmware patch yet. My scanner is still good :) I'm patient. > Another point: From reading cam.h, I think that the sense handler > should only be called, if the bit CAM_AUTOSNS_VALID is set in > ccb_h.status. Hmmm... that's too high-level for me. I am not really a kernel developer. Maybe freebsd mailing lists would help you. http://www.freebsd.org/support.html#mailing-list > Generally, I have the impression that the FreeBSD/CAM part of > sanei_scsi.c could need a review. But that should be done by somebody > who can run Sane under FreeBSD ;) Well, I will try to help, but I am also a simple user who just writes 'make install' in /usr/ports/graphics/xsane and is expecting that everything works after few minutes. :) Generally it is better to have contact with the responsible ports committer. You can find him here: http://www.FreeBSD.org/cgi/ports.cgi?query=xsane&stype=all The ports version of xsane in FreeBSD ports tree is 0.90. Tomorrow I want to take a look, if I am able to build xsane-0.90 with your suggested patch. Martin From ope557 at yahoo.com Wed Jun 18 01:14:21 2003 From: ope557 at yahoo.com (ope) Date: Tue, 17 Jun 2003 17:14:21 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <200306172358.16932.oliver.rauch@rauch-domain.de> Message-ID: <20030618001421.34819.qmail@web20604.mail.yahoo.com> What I see in messages are a lot of messages saying: kernel: usb_control/bulk_msg: timeout last message repeated 2 times last message repeated 3 times ... and after 10 minutes or so I will see: kernel: scanner.c: read_scanner(0): excessive NAK's received --- Oliver Rauch wrote: > On Tuesday 17 June 2003 09:39, ope wrote: > > > I have also noticed another thing that is worth > > mentioning. At one point when the xsane seemed to > be > > stuck I tried unplugging the scanner from the USB > > port. I was expecting xsane to fail and close > down. > > What actually did happen was that the complete > scanned > > image instantly popped up in the viewer and xsane > was > > running as if nothing has happened. Just for fun > I > > tried it couple more times and had the same > results > > each time. It appears to me that that the scan is > > essentially complete at the point that it is > freezing. > > This sounds as if there is a problem with the USB > communication. > > Do you get any messages about USB problems > in /var/log/messages ? > > Oliver > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From pjh at coastal.net.au Wed Jun 18 04:46:43 2003 From: pjh at coastal.net.au (Peter Howard) Date: 18 Jun 2003 13:46:43 +1000 Subject: [sane-devel] Problem building on OSX In-Reply-To: References: Message-ID: <1055908005.2315.64.camel@pig> On Sun, 2003-06-08 at 22:07, Peter O'Gorman wrote: > Hi Peter, > > I am guessing here, but are you using Apple's developer tools which > shipped with 10.2 ? Indeed. > This works for me with the ld from the December 2002 developer tools, > looks like a linker issue may have been fixed in that release. > > You can get a copy of the December 2002 tools from > http://connect.apple.com after free registration. > > I'd be interested to know if this solves your problem, I thought that > this was solved prior to release of 1.0.12, but it may have only been > "solved" for those of us with the latest linker :( Skipping the mini-saga of getting it downloaded . . . I installed the December update this morning. And, lo and behold, sane builds and installs. Thanks. While I'm here . . .the reason I've been building sane is to do with the "less than perfect" support for OSX from scanner manufacturers. Searching back through the mailing list archives I saw some comments agreeing with that, but nothing much more. I have sitting next to me an Epson USB scanner (Perfection 610) beloning to my in-laws. Having had zero luck with the official Epson driver I'm turning to sane (which I also use on my linux box). However, not being the most technically minded, what my Mother-in-law really wants is to be able to drive the scanner from inside iPhoto. Has anyone done work on a sane frontend to plug in as a normal OSX scanner input? Given no SANE->TWAIN bridge around on OSX I suspect not, or not very far. But if you don't ask . . .:-) PJH > On Sunday, June 8, 2003, at 10:53 AM, Peter Howard wrote: > > > (I've searched the archive and have seen related problems but not > > enough > > info to work the rest out :-( > > > > I'm trying to build sane-backends 1.0.12 on OSX 10.2, and I get the > > following load errors: > > > > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a > > ../backend/.libs/libsane.dylib -lm -framework CoreFoundation -framework > > IOKit > > ld: multiple definitions of symbol _getopt > > /usr/lib/libm.dylib(getopt.So) definition of _getopt > > ../lib/liblib.a(getopt.o) definition of _getopt in section > > (__TEXT,__text) > > ld: multiple definitions of symbol _opterr > > /usr/lib/libm.dylib(getopt.So) definition of _opterr > > ../lib/liblib.a(getopt.o) definition of _opterr in section > > (__DATA,__data) > > ld: multiple definitions of symbol _optind > > /usr/lib/libm.dylib(getopt.So) definition of _optind > > ../lib/liblib.a(getopt.o) definition of _optind in section > > (__DATA,__data) > > ld: multiple definitions of symbol _optopt > > /usr/lib/libm.dylib(getopt.So) definition of _optopt > > ../lib/liblib.a(getopt.o) definition of _optopt in section > > (__DATA,__data) > > make[1]: *** [scanimage] Error 1 > > make: *** [all-recursive] Error 1 > > > > > > I gave no options to configure. > > > > Thanks > > > > PJH > > > > > > > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel at www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > From aneeshmraj at hotmail.com Wed Jun 18 09:07:30 2003 From: aneeshmraj at hotmail.com (aneesh m raj) Date: Wed, 18 Jun 2003 13:37:30 +0530 Subject: [sane-devel] The format of data after sane_read() Message-ID: Hi All, What will be the format of the output data received after the sane_read() call ,will it be pnm format. Thanks Aneesh -------------- next part -------------- An HTML attachment was scrubbed... URL: From henning at meier-geinitz.de Wed Jun 18 09:11:47 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 10:11:47 +0200 Subject: [sane-devel] Problem building on OSX In-Reply-To: <1055908005.2315.64.camel@pig> References: <1055908005.2315.64.camel@pig> Message-ID: <20030618081147.GB12579@meier-geinitz.de> Hi, On Wed, Jun 18, 2003 at 01:46:43PM +1000, Peter Howard wrote: > While I'm here . . .the reason I've been building sane is to do with the > "less than perfect" support for OSX from scanner manufacturers. > Searching back through the mailing list archives I saw some comments > agreeing with that, but nothing much more. I have sitting next to me an > Epson USB scanner (Perfection 610) beloning to my in-laws. Having had > zero luck with the official Epson driver I'm turning to sane (which I > also use on my linux box). However, not being the most technically > minded, what my Mother-in-law really wants is to be able to drive the > scanner from inside iPhoto. What's iPhoto? A MacOS X image manipulation program? Can't she use the Gimp? > Has anyone done work on a sane frontend to plug in as a normal OSX > scanner input? I haven't heard of such a thing. > Given no SANE->TWAIN bridge around on OSX I suspect not, or not very > far. But if you don't ask . . Given the existing SANE-TWAIN bridges for Windows, it may not be to complicated to write one for MacOS X. But I'm just guessing here. Bye, Henning From henning at meier-geinitz.de Wed Jun 18 09:28:01 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 10:28:01 +0200 Subject: [sane-devel] The format of data after sane_read() In-Reply-To: References: Message-ID: <20030618082801.GD12579@meier-geinitz.de> Hi, On Wed, Jun 18, 2003 at 01:37:30PM +0530, aneesh m raj wrote: > What will be the format of the output data received after the > sane_read() call ,will it be pnm format. No, not really. See the SANE standard, "Image Data Format": http://www.mostang.com/sane/html/doc008.html Bye, Henning From petr.felenda at sun.com Wed Jun 18 11:25:22 2003 From: petr.felenda at sun.com (Petr Felenda) Date: Wed, 18 Jun 2003 12:25:22 +0200 Subject: [sane-devel] Revscan 19200i Message-ID: <3EF03E12.6070802@sun.com> I have scanner revscan 19200i. It is possible to use it with Sane ? Thanks Petr From henning at meier-geinitz.de Wed Jun 18 11:55:47 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 12:55:47 +0200 Subject: [sane-devel] Revscan 19200i In-Reply-To: <3EF03E12.6070802@sun.com> References: <3EF03E12.6070802@sun.com> Message-ID: <20030618105547.GE12579@meier-geinitz.de> Hi, On Wed, Jun 18, 2003 at 12:25:22PM +0200, Petr Felenda wrote: > I have scanner revscan 19200i. > It is possible to use it with Sane ? It's not in our lists so nobody seems to have tried so far. Maybe it's compatible to one of the supported devices? Can you please show us the output of "cat /proc/bus/usb/devices" when the scanner is plugged in? Bye, Henning From khk at khk.net Wed Jun 18 12:06:25 2003 From: khk at khk.net (khk at khk.net) Date: Wed, 18 Jun 2003 07:06:25 -0400 (EDT) Subject: [sane-devel] Problem building on OSX In-Reply-To: <1055908005.2315.64.camel@pig> References: <1055908005.2315.64.camel@pig> Message-ID: <49492.198.176.225.6.1055934385.squirrel@home.khk.net> > On Sun, 2003-06-08 at 22:07, Peter O'Gorman wrote: [ ... ] > While I'm here . . .the reason I've been building sane is to do with the > "less than perfect" support for OSX from scanner manufacturers. > Searching back through the mailing list archives I saw some comments > agreeing with that, but nothing much more. I have sitting next to me an > Epson USB scanner (Perfection 610) beloning to my in-laws. Having had > zero luck with the official Epson driver I'm turning to sane (which I > also use on my linux box). However, not being the most technically > minded, what my Mother-in-law really wants is to be able to drive the > scanner from inside iPhoto. Has anyone done work on a sane frontend to > plug in as a normal OSX scanner input? Given no SANE->TWAIN bridge > around on OSX I suspect not, or not very far. But if you don't ask . . [ ... ] For now you are stuck with a paper weight... Even with a Sane/TWAIN bridge, this configuration would not work: So far I had no success in getting the EPSON backend to actually scan on OS X. The scanner is recognized, and the initial communication up until the scan request does also work, but the backend never receives any image data from the scanner. The only way you can use this scanner under OS X at this time is with vuescan (http://www.hamrick.com). Karl Heinz From a.deuring at satzbau-gmbh.de Wed Jun 18 12:49:28 2003 From: a.deuring at satzbau-gmbh.de (abel deuring) Date: Wed, 18 Jun 2003 13:49:28 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <200306171724.52572.nakal@web.de> <3EEF8884.2000805@gmx.net> <200306180107.59518.nakal@web.de> Message-ID: <3EF051C8.FE0079FE@satzbau-gmbh.de> Nakal wrote: > > On Tuesday 17 June 2003 23:30, abel deuring wrote: > > > First a disclaimer for the following stuff: I don't have FreeBSD > > installed, I used it only rarely, and I never wrote software > > specifically for FreeBSD. So I am writing as a "backseat driver" ;) > > > Try it :) > if you can give me some time ;) > > 10 -> CAM_SEL_TIMEOUT, /* Target Selection Timeout */ > > 16 -> CAM_AUTOSENSE_FAIL = 0x10,/* Autosense: request sense cmd fail > > */ > > (definitions of this kind tend to be stable -- but control is better > > than trust some cases: Martin, can you confirm this for your version > > of cam.h?) > > The values 10 and 16 are still correct, but I'm sure you are using the > enums by name. That should be fine, of course. Seems nothing has > changed in cam.h since 2000/03/17. Even FreeBSD-current (5.1) seems to > use the same values (2002/01/09). I tried to identify the error numbers in the log file. > > You can find the kernel sources for cam here (just in case you haven't > found cam.c): > ftp://ftp2.freebsd.org/pub/FreeBSD/FreeBSD-stable/src/sys/cam Thanks for the pointer. But I think that it should be sufficient to read the CAM documentation on the FressBSD web site ;) It looks quite comprehensive. > > > OK, many commands fail with a selection time out. Not very surprising > > for a slow scanner with probably somewhat dumb firmware ;) > > Firmware? :) No firmware patch yet. My scanner is still good :) I'm > patient. An update should not be necessary (and would ptobably not help very much). What I meant is this: The first failing command ("stop scan") is rejected by the scanner with the reason "I'm busy". I assume that this is caused by a firmware which completely occipied by controlling the stepper motor of the scan head to move the scan head back after the scan. A better firmware with a decent interrupt management is able to accept SCSI command in such a situation, But Sane (specifically, sanei_scsi.c and the backend) should be able to work with a dumb scanner. > > > Another point: From reading cam.h, I think that the sense handler > > should only be called, if the bit CAM_AUTOSNS_VALID is set in > > ccb_h.status. > > Hmmm... that's too high-level for me. I am not really a kernel > developer. Maybe freebsd mailing lists would help you. > http://www.freebsd.org/support.html#mailing-list Thanks for the hint, but again, it should not be necesary to bother the FreeBSD developers. When a SCSI command is accepted by a device but results in an error, some details of the error are described in the so-called sense data, which can be retrieved by another SCSI command (REQUEST SENSE). REQUEST SENSE is automatically issued by the operating system, if this is reasonable. When the call issueing the failing command ends, the application can (1) check, if sense data is available, and (2) do some "clean up" or print details error information (for scanners, this can be tinhgs like "12V fuse blown" of "mechanical error", but also more generic stuff like "invalid SCSI command parameter"). One problem of the CAM part of sanei_scsi.c is that the avaliability of the sense data is not checked -- it simply assumes that it is available.. > > > Generally, I have the impression that the FreeBSD/CAM part of > > sanei_scsi.c could need a review. But that should be done by somebody > > who can run Sane under FreeBSD ;) > > Well, I will try to help, but I am also a simple user who just writes > 'make install' in /usr/ports/graphics/xsane and is expecting that > everything works after few minutes. :) > > Generally it is better to have contact with the responsible ports > committer. You can find him here: > http://www.FreeBSD.org/cgi/ports.cgi?query=xsane&stype=all > > The ports version of xsane in FreeBSD ports tree is 0.90. Tomorrow I > want to take a look, if I am able to build xsane-0.90 with your > suggested patch. No need to (re-)build xsane; the problem is in sane-backends. And I'm afraid that my patch will not completely fix it -- I think that there will be the need to retry a SCSI command that returns with "device busy". The problem is that I'm not sure, if this should be done in sanei_scsi.c or in the backend. IIRC we had a discussion of this question some time ago, but I don't have currently the time to search for it... If we don't find a volunteer for fixing sanei_scsi.c, I'll give a try during the weekend. Abel From henning at meier-geinitz.de Wed Jun 18 13:16:45 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 18 Jun 2003 14:16:45 +0200 Subject: [sane-devel] Problem building on OSX In-Reply-To: <49492.198.176.225.6.1055934385.squirrel@home.khk.net> References: <1055908005.2315.64.camel@pig> <49492.198.176.225.6.1055934385.squirrel@home.khk.net> Message-ID: <20030618121645.GF12579@meier-geinitz.de> Hi, On Wed, Jun 18, 2003 at 07:06:25AM -0400, khk at khk.net wrote: > For now you are stuck with a paper weight... Even with a Sane/TWAIN bridge, > this configuration would not work: So far I had no success in getting the > EPSON backend to actually scan on OS X. But that's only with USB, isn't it? Or even only with this scanner? As far as I know, SCSI scanners work with the epson backend on MacOS X. At least I have one report about the Epson Perfection 1640SU working. More reports on which scanners work or don't work on MacOS X are welcome. Bye, Henning From khk at khk.net Wed Jun 18 14:10:08 2003 From: khk at khk.net (khk at khk.net) Date: Wed, 18 Jun 2003 09:10:08 -0400 (EDT) Subject: [sane-devel] Problem building on OSX In-Reply-To: <20030618121645.GF12579@meier-geinitz.de> References: <1055908005.2315.64.camel@pig> <49492.198.176.225.6.1055934385.squirrel@home.khk.net> <20030618121645.GF12579@meier-geinitz.de> Message-ID: <18767.198.176.225.6.1055941808.squirrel@home.khk.net> > Hi, > > On Wed, Jun 18, 2003 at 07:06:25AM -0400, khk at khk.net wrote: >> For now you are stuck with a paper weight... Even with a Sane/TWAIN >> bridge, >> this configuration would not work: So far I had no success in getting >> the >> EPSON backend to actually scan on OS X. > > But that's only with USB, isn't it? Or even only with this scanner? As > far as I know, SCSI scanners work with the epson backend on MacOS X. > At least I have one report about the Epson Perfection 1640SU working. > > More reports on which scanners work or don't work on MacOS X are > welcome. Yes, this is applies only to EPSON USB scanners under OS X. From maddog at mir.com Wed Jun 18 18:30:09 2003 From: maddog at mir.com (Matto Marjanovic) Date: Wed, 18 Jun 2003 13:30:09 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EEF8884.2000805@gmx.net> (message from abel deuring on Tue, 17 Jun 2003 23:30:44 +0200) References: <200306102317.58064.nakal@web.de> <200306162322.35147.nakal@web.de> <3EEE41B6.4050606@gmx.net> <200306171724.52572.nakal@web.de> <3EEF8884.2000805@gmx.net> Message-ID: <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> Hi, Sorry to get into this thread so late... I have to pull out all my microtek notes again; I might even already have a fix for this problem in the works --- a big graduation got in the way, and now I have to refresh many memories. But, in the meantime... 0) None of this generation of Microtek scanners supports SCSI disconnect. Disconnect needs to be disabled for the scanner device (if not the whole bus), and you should expect the scanner to monopolize the entire bus during a scan. 1) The firmware in the earlier Microtek scanners is particularly brain-dead with regards to timeouts like this. Even worse, I have pretty extensive documentation from Microtek --- *but every scanner deviates from the documented behavior in some important way*. Ugh. 2) With regards to this: >Looking through the log, it seems to me that something is wrong in >sanei_scsi.c. From your log file: > >[microtek] .stop_scan... >[microtek] SPS:1b 0 0 0 0 0 >[sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 >[microtek] SENSE! fd = 0 >[microtek] sense = 00 00 00 00. >scanimage: min/max graylevel value = 21/255 >[microtek] sane_start... > >The "stop scan" command returns an error (the "sanei_scsi" line), and >all following SCSI commands return errors too. The scanner probably *is* generating a SENSE error along with sense info. However, it is not a SCSI-2 device --- it follows SCSI-1-CCM (something like that) and it generates non-standard sense codes. I don't know about FreeBSD, but the Linux SCSI drivers always zero out the sense codes --- this frustrates me to no end. The Linux drivers are trying to be clever, but they assume that *every* device is SCSI-2, and since the codes do not conform to SCSI-2, they get squashed. Probably, FreeBSD is doing the same thing. What both OS's *should* do is just pass the poor sense codes up to the sense handler installed by the backend, which should be smart enough to deal with them. Instead, the sense handler always gets called with a bunch of zeros! 3) For 3-pass scans, the backend needs to implement some kind of delay between passes. *However*, because of o the loss of the actual sense information o the poor documentation it is unclear which commands can be sent during that delay, if that delay can be polled (i.e. ask the scanner if it is ready) or if it must be guessed, etc, etc. This is the part of maintaining this backend that I despise. I'll start rummaging through my notes. I'm recollecting now that I had a quick fix for this a couple of months ago --- but it was too late for the release back then, and then I got really really busy. -matt m. From nakal at web.de Wed Jun 18 22:51:22 2003 From: nakal at web.de (Nakal) Date: Wed, 18 Jun 2003 23:51:22 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <200306182351.22833.nakal@web.de> On Wednesday 18 June 2003 19:30, you wrote: > 0) None of this generation of Microtek scanners supports SCSI > disconnect. Disconnect needs to be disabled for the scanner device > (if not the whole bus), and you should expect the scanner to > monopolize the entire bus during a scan. I really don't understand SCSI much. FreeBSD gives me still "unexpected disconnect" with my scanner, after I switched off "disconnection" in my controller's BIOS. > 1) The firmware in the earlier Microtek scanners is particularly > brain-dead with regards to timeouts like this. Even worse, I have > pretty extensive documentation from Microtek --- *but every scanner > deviates from the documented behavior in some important way*. Ugh. Yes. It is a quite "cheap" scanner and came with a separate ISA SCSI-1 controller. Now I'm using one with a Symantec chipset (Tekram DC390/UW). The scanner is attached to external UW bus. I wonder if it is really correct to connect it like this, but IT WORKED earlier (1 or 2 years ago?) on Debian, so it should not be a problem. > The Linux > drivers are trying to be clever, but they assume that *every* device > is SCSI-2, and since the codes do not conform to SCSI-2, they get > squashed. > > Probably, FreeBSD is doing the same thing. What both OS's > *should* do is just pass the poor sense codes up to the sense handler > installed by the backend, which should be smart enough to deal with > them. Instead, the sense handler always gets called with a bunch of > zeros! Well, if I only had time to look at FreeBSD SCSI architecture, I would try to help. I wonder why they would remove information from the sense responses. > it is unclear which commands can be sent during that delay, if > that delay can be polled (i.e. ask the scanner if it is ready) or if > it must be guessed, etc, etc. There is a possibility to compile the FreeBSD kernel with CAM debugging. This produces LOTS of information (see: man camcontrol(8)). With just a bit luck, there might be some useful information about the scanner's behavior. > I'll start rummaging through my notes. I'm recollecting now that I > had a quick fix for this a couple of months ago --- but it was too > late for the release back then, and then I got really really busy. I don't know how many people are using old Microtek scanners. If it is too much trouble, simply forget it. Martin From mrjaneway at gmx.net Thu Jun 19 08:58:57 2003 From: mrjaneway at gmx.net (mrjaneway at gmx.net) Date: Thu, 19 Jun 2003 09:58:57 +0200 (MEST) Subject: [sane-devel] Sane support for Acer parallel port scanners Message-ID: <2263.1056009537@www36.gmx.net> Hello, I am new to this list, so I hope I dont ask any stupid questions.... I am also new to the Linux world and I installed SuSE Linux 8.2 on my PC. Everything is working, except my old scanner. It's a Acer / Benq 620P parallel port scanner, and in the Sane compatibility list the status for a driver for this model is marked as "unknown". Can you tell me if someone is working on a Sane driver for this model? Or can I use another driver that will work for my scanner too? I guess Acer is only relabeling its scanners.... Any help on this is very appreciated, thanks! Geetings, Tobias From henning at meier-geinitz.de Thu Jun 19 09:49:39 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 19 Jun 2003 10:49:39 +0200 Subject: [sane-devel] Sane support for Acer parallel port scanners In-Reply-To: <2263.1056009537@www36.gmx.net> References: <2263.1056009537@www36.gmx.net> Message-ID: <20030619084939.GJ12579@meier-geinitz.de> Hi, On Thu, Jun 19, 2003 at 09:58:57AM +0200, mrjaneway at gmx.net wrote: > I am new to this list, so I hope I dont ask any stupid questions.... I am > also new to the Linux world and I installed SuSE Linux 8.2 on my PC. Everything > is working, except my old scanner. It's a Acer / Benq 620P parallel port > scanner, and in the Sane compatibility list the status for a driver for this > model is marked as "unknown". Well, to be exact, it is not on our lists at all, only on Jonathan Buzzard's parallel port scanners list. Usually that means that there is no support in SANE. > Can you tell me if someone is working on a Sane driver for this > model? I don't think so. At least the scanner is not mentioned in our list or on the TODO list. I can add the Benq Parport scanners to our "unsupported" list to make that more clear. > Or can I use another driver that will work for my > scanner too? I guess Acer is only relabeling its scanners.... I don't know, but if it were possible to get it working with another backend, that fact would be most probably known. But it doesn't harm to try the parallel port backends. Just select "Parport" in the scanner search engine and try the hbackends that it mentions. Otherwise I guess it's up to you to write a backend. But I doubt it's worth the hassle for an old parport scanner. But maybe the maintainer of the snapscan backend which supports Benq SCSI scanners knows more details? Bye, Henning From henning at meier-geinitz.de Thu Jun 19 15:19:58 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 19 Jun 2003 16:19:58 +0200 Subject: [sane-devel] Device description format changed in CVS (.desc files) Message-ID: <20030619141958.GN12579@meier-geinitz.de> Hi, Yesterday I committed a new version of tools/sane-desc.c. That's the program that generates our HTML lists of supported devices and is also used for the scanner search engine. The main change is that there is no longer a backend status, only a per-device status. The possible status values have changed, I'll cite doc/descriptions.txt here: The keyword :status' is an indication of the level of support for the model. It's followed by one of the following keyword arguments: :unsupported', :untested', :minimal', :basic', :good', or :complete'. The :status' keyword refers to the previous :model', is optional and should be used only once per model. :unsupported' means the device is not supported at least by this backend. The keyword should only be used in the file unsupported.desc', or to make clear that a specific scanner is not supported by a backend. :untested' means the device may be supported but couldn't be tested. :minimal' means that the device is detected and scans at least in one mode. But the quality is bad or important features won't work. :basic' means it works at least in the most important modes but quality is not perfect. :good' means the device is usable for day-to-day work. Some rather exotic features may be missing. :complete' means the backends supports everything the device can do. Example: :status :untested' sane-desc.c still accepts the old status codes (with warnings) and tries to translate them: alpha->basic, beta->good, stable->complete. This translation isn't correct in mayne cases, however. So please update your description files as soon as possible to reflect the actual support for the devices. I'll update the unmaintained backends's description files. Thanks to Jochen Eisinger for updateing the scanner search enigine to the new format. Bye, Henning From adeuring at gmx.net Thu Jun 19 20:59:10 2003 From: adeuring at gmx.net (abel deuring) Date: Thu, 19 Jun 2003 21:59:10 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306182351.22833.nakal@web.de> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> Message-ID: <3EF2160E.2090603@gmx.net> Nakal wrote: > I really don't understand SCSI much. FreeBSD gives me still "unexpected > disconnect" with my scanner, after I switched off "disconnection" in my > controller's BIOS. Could the FreeBSD driver ignore the BIOS settings? I assume that you can pass a parameter like "don't disconnect" to the driver. > Yes. It is a quite "cheap" scanner and came with a separate ISA SCSI-1 > controller. Now I'm using one with a Symantec chipset (Tekram > DC390/UW). The scanner is attached to external UW bus. I wonder if it > is really correct to connect it like this, but IT WORKED earlier (1 or > 2 years ago?) on Debian, so it should not be a problem. Well, a fast SCSI adapter may have problems with a slow device, but I don't believe that this is the case hre. After all, the scanner finishes one of the three passes, and that shows that several SCSI commands were successful. >> it is unclear which commands can be sent during that delay, if >>that delay can be polled (i.e. ask the scanner if it is ready) or if >>it must be guessed, etc, etc. > > > There is a possibility to compile the FreeBSD kernel with CAM debugging. > This produces LOTS of information (see: man camcontrol(8)). With just a > bit luck, there might be some useful information about the scanner's > behavior. That could be interesting -- but currently I think we can stay with the Sane debug messages. > I don't know how many people are using old Microtek scanners. If it is > too much trouble, simply forget it. From my POV, we should continue ;) I think you had simply the bad luck of being the first one to discover a bug in sanei_scsi.c (and perhaps another one in the Microtek backend) -- but these bugs could bite more people, if we don't fix them... And while I would really prefer it to leave the patches for sanei_scsi.c to somebody who has FreeBSD installed, I'll try to do it myself, if nobody shouts "I'm volunteering". But expect some extra work fixing typos in my patches ;) Abel PS: Considering the log output from running the Scanmaker II under Linux, it its perhaps worth, if you try my simple patch to sanei_scsi.c I am not sure, but both the backend and the scnner seem to be able to deal with a few failing commands. And the patch passes slightly better erro informations to the backend. From adeuring at gmx.net Thu Jun 19 20:59:18 2003 From: adeuring at gmx.net (abel deuring) Date: Thu, 19 Jun 2003 21:59:18 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> References: <200306102317.58064.nakal@web.de> <200306162322.35147.nakal@web.de> <3EEE41B6.4050606@gmx.net> <200306171724.52572.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF21616.1030807@gmx.net> Matto Marjanovic wrote: > 0) None of this generation of Microtek scanners supports SCSI disconnect. > Disconnect needs to be disabled for the scanner device (if not the > whole bus), and you should expect the scanner to monopolize the entire > bus during a scan. > > 1) The firmware in the earlier Microtek scanners is particularly brain-dead > with regards to timeouts like this. Even worse, I have pretty extensive > documentation from Microtek --- *but every scanner deviates from the > documented behavior in some important way*. Ugh. At least you have some sort docs ;) > > 2) With regards to this: > > >Looking through the log, it seems to me that something is wrong in > >sanei_scsi.c. From your log file: > > > >[microtek] .stop_scan... > >[microtek] SPS:1b 0 0 0 0 0 > >[sanei_scsi] sanei_scsi_cmd: scsi returned with status 10 > >[microtek] SENSE! fd = 0 > >[microtek] sense = 00 00 00 00. > >scanimage: min/max graylevel value = 21/255 > >[microtek] sane_start... > > > >The "stop scan" command returns an error (the "sanei_scsi" line), and > >all following SCSI commands return errors too. > > The scanner probably *is* generating a SENSE error along with sense info. > However, it is not a SCSI-2 device --- it follows SCSI-1-CCM (something > like that) and it generates non-standard sense codes. I don't think that the scanner returns any useful data in this case, except that it said "too busy to accept the SCSI command". I've found a Scanmaker II buried deep in a cabinet and connected it to my Linux box. Here we get a similar error: [microtek] .stop_scan... [microtek] SPS:1b 0 0 0 0 0 [sanei_scsi] scsi_req_enter: entered 0x40825008 [sanei_scsi] sanei_scsi.issue: 0x40825008 dev_max(currently)=8 max_active_device=2 (origin 1) scsi_dma_free_sectors=64 sg_pool_secs_aval=320 def_reserved_size=32768 >>> device=sg1 scsi0 chan=0 id=6 lun=0 em=0 sg_tablesize=127 excl=1 FD(1): timeout=120000ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 act: id=51 blen=0 t_o/elap=120000/20ms sgat=0 op=0x1b [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 2 [sanei_scsi] sanei_scsi_req_wait: waiting for 0x40825008 [sanei_scsi] sanei_scsi.issue: 0x40825008 dev_max(currently)=8 max_active_device=2 (origin 1) scsi_dma_free_sectors=64 sg_pool_secs_aval=320 def_reserved_size=32768 >>> device=sg1 scsi0 chan=0 id=6 lun=0 em=0 sg_tablesize=127 excl=1 FD(1): timeout=120000ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 rcv: id=51 blen=0 dur=620ms sgat=0 op=0x1b [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Erfolg [sanei_scsi] sense buffer: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [sanei_scsi] target status: 7f host status: 0003 driver status: 0026 [microtek] end_scan: OY! on stop_scan The non-zero values for host status and driver status indicate that the scanner did not "accept" the command. host status 3 means a timeout, but NOT a SCSI command timeout. driver status 26 means "driver timeout; suggest abort". The Linux part of sanei_scsi.c does not call the sense handler in this case (that would be pointless, because the scanner refused to do anything with the commands, so there is not sense data), but returns SANE_STATUS_DEVICE_BUSY. > I don't know about FreeBSD, but the Linux SCSI drivers always zero out > the sense codes --- this frustrates me to no end. The Linux drivers are > trying to be clever, but they assume that *every* device is SCSI-2, and > since the codes do not conform to SCSI-2, they get squashed. > > Probably, FreeBSD is doing the same thing. What both OS's *should* do > is just pass the poor sense codes up to the sense handler installed by > the backend, which should be smart enough to deal with them. Instead, > the sense handler always gets called with a bunch of zeros! Yes, they should do it, _if_ sense data is available. I tried to check this with Linux (but not very hard). I deliberately changed the data of the "start scan" command to "comm[6] = { 0x1B, 1, 1, 1, 1, 1 };" -- but the scanner simply accepted this command, while I expected to get some error back :( > > > 3) For 3-pass scans, the backend needs to implement some kind of delay > between passes. *However*, because of > > o the loss of the actual sense information > o the poor documentation > > it is unclear which commands can be sent during that delay, if that > delay can be polled (i.e. ask the scanner if it is ready) or if it > must be guessed, etc, etc. > > This is the part of maintaining this backend that I despise. I think that the backend should check for the error SANE_STATUS_DEVICE_BUSY and it should retry the failing commands for a reasonable amount of time. In the case of the 3-pass scans, this could be 30 seconds or so. Abel From alan.purchase at paradise.net.nz Fri Jun 20 09:25:35 2003 From: alan.purchase at paradise.net.nz (Alan Purchase) Date: 20 Jun 2003 20:25:35 +1200 Subject: [sane-devel] Microtek Scanmaker 6700 (USB and FireWire) Message-ID: <1056097536.2918.16.camel@localhost.localdomain> Hi, I have been running a dual boot Windows 98 and Mandrake Linux system for some time and now I want to drop Windows and run solely on Mandrake Linux 9.0. My problem is that I have a Microtek Scanmaker 6700 scanner that appears not to be supported by Sane. Can you tell me if someone is working on a Sane driver for this model and whether it will support USB, FireWire or both. Cheers, Alan. -- ______________________________________________________________________ Alan Purchase IT Consultant Tel: +64 9 817 3101 113 Victory Road Mobile: +64 21 925 028 Laingholm E-mail: alan.purchase at paradise.co.nz Auckland 1007 New Zealand ______________________________________________________________________ From henning at meier-geinitz.de Thu Jun 19 22:22:11 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 19 Jun 2003 23:22:11 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF2160E.2090603@gmx.net> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> <3EF2160E.2090603@gmx.net> Message-ID: <20030619212211.GP12579@meier-geinitz.de> Hi, On Thu, Jun 19, 2003 at 09:59:10PM +0200, abel deuring wrote: > From my POV, we should continue ;) I think you had simply the bad luck > of being the first one to discover a bug in sanei_scsi.c (and perhaps > another one in the Microtek backend) -- but these bugs could bite more > people, if we don't fix them... And while I would really prefer it to > leave the patches for sanei_scsi.c to somebody who has FreeBSD > installed, I'll try to do it myself, if nobody shouts "I'm > volunteering". But expect some extra work fixing typos in my patches ;) I'm not volunteering :-) but I can at least test if any of your patches break Mustek scanners on FreeBSD. Bye, Henning From henning at meier-geinitz.de Thu Jun 19 22:48:26 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 19 Jun 2003 23:48:26 +0200 Subject: [sane-devel] Microtek Scanmaker 6700 (USB and FireWire) In-Reply-To: <1056097536.2918.16.camel@localhost.localdomain> References: <1056097536.2918.16.camel@localhost.localdomain> Message-ID: <20030619214826.GC19044@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 08:25:35PM +1200, Alan Purchase wrote: > I have been running a dual boot Windows 98 and Mandrake Linux system for > some time and now I want to drop Windows and run solely on Mandrake > Linux 9.0. My problem is that I have a Microtek Scanmaker 6700 scanner > that appears not to be supported by Sane. Can you tell me if someone is > working on a Sane driver for this model and whether it will support USB, > FireWire or both. As it's not on our lists, it's quite unlikely than someone is working on it. Can you provide more details about the scanner, so we can at least list it as "unsupported"? E.g., plug it in, boot linux and show us the output of "cat /proc/bus/usb/devices", please. Maybe it's compatible to any of the already supported scanners. But I doubt that. Some links on how to write a SANE driver: http://www.meier-geinitz.de/sane/misc/unsupported.html http://www.meier-geinitz.de/sane/misc/develop.html Bye, Henning From yaya at ntlworld.com Thu Jun 19 23:35:22 2003 From: yaya at ntlworld.com (Philip) Date: Thu, 19 Jun 2003 23:35:22 +0100 Subject: [sane-devel] Canoscan D646U??? Message-ID: <200306192335.22638.yaya@ntlworld.com> Somone please help me. Using Mandrake 9.1 and need some help or information in obtaining a driver or support for this flatbed scanner, that is if there is any availible. Any info will be appreciated. Thanks From henning at meier-geinitz.de Fri Jun 20 09:32:45 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 20 Jun 2003 10:32:45 +0200 Subject: [sane-devel] Canoscan D646U??? In-Reply-To: <200306192335.22638.yaya@ntlworld.com> References: <200306192335.22638.yaya@ntlworld.com> Message-ID: <20030620083245.GD1867@meier-geinitz.de> Hi, On Thu, Jun 19, 2003 at 11:35:22PM +0100, Philip wrote: > Using Mandrake 9.1 and need some help or information in obtaining a driver or > support for this flatbed scanner, that is if there is any availible. > > Any info will be appreciated. All the information we have is listed in the scanner search engine: http://sane.informatik.uni-freiburg.de/cgi-bin/driver.pl?manu=canon&model=646&bus=any So as a summary: There is no driver yet. But you could contact the maintainer of the canon630u backend and find out, if these scanners are really similar and if your scanner can be supported by that backend. Please tell us the result. The maintainer is: Nathan Rutman . If the scanners are completely different, it's up to you to write a new backend: http://www.meier-geinitz.de/sane/misc/unsupported.html http://www.meier-geinitz.de/sane/misc/develop.html Bye, Henning From david at rondotheatre.co.uk Fri Jun 20 11:27:37 2003 From: david at rondotheatre.co.uk (david stevenson) Date: Fri, 20 Jun 2003 11:27:37 +0100 Subject: [sane-devel] Manufactures Message-ID: <200306201127.37790.david@rondotheatre.co.uk> Henning and all, I was rereading your >Some links on how to write a SANE driver: >http://www.meier-geinitz.de/sane/misc/unsupported.html >http://www.meier-geinitz.de/sane/misc/develop.html and it occurred to me that it may help to have a page directed at manufactures to explain how they can get their scanner supported. I realise that the number of requests on the list of this nature is low 8-) but the optimist in me says anyone working professionally on a scanner will have a look sooner or later, but may not want to reveal them selves. Just an idle thought, .... to generate work for others. David From henning at meier-geinitz.de Fri Jun 20 12:35:18 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 20 Jun 2003 13:35:18 +0200 Subject: [sane-devel] Manufactures In-Reply-To: <200306201127.37790.david@rondotheatre.co.uk> References: <200306201127.37790.david@rondotheatre.co.uk> Message-ID: <20030620113518.GH1867@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 11:27:37AM +0100, david stevenson wrote: > and it occurred to me that it may help to have a page directed at manufactures > to explain how they can get their scanner supported. You mean a page about what a manufacturer can do to get a SANE driver? Well, that's pretty easy: Write a driver like explained on the "unsupported page". Or pay someone else to write it. Releasing programming information may make it easier for someone else to write a driver, but it's not a guarantee to get it written. Something along these lines? I could also add that to the "unsupported page". Bye, Henning From david at rondotheatre.co.uk Fri Jun 20 12:53:53 2003 From: david at rondotheatre.co.uk (david stevenson) Date: Fri, 20 Jun 2003 12:53:53 +0100 Subject: [sane-devel] Manufactures In-Reply-To: <20030620113518.GH1867@meier-geinitz.de> References: <200306201127.37790.david@rondotheatre.co.uk> <20030620113518.GH1867@meier-geinitz.de> Message-ID: <200306201253.53192.david@rondotheatre.co.uk> On Friday 20 June 2003 12:35 pm, Henning Meier-Geinitz wrote: > Hi, > > On Fri, Jun 20, 2003 at 11:27:37AM +0100, david stevenson wrote: > > and it occurred to me that it may help to have a page directed at > > manufactures to explain how they can get their scanner supported. > > You mean a page about what a manufacturer can do to get a SANE driver? > > Well, that's pretty easy: Write a driver like explained on the > "unsupported page". Or pay someone else to write it. Releasing > programming information may make it easier for someone else to write a > driver, but it's not a guarantee to get it written. > > Something along these lines? I could also add that to the "unsupported > page". > Yes, general encouragement, I had not thought about all the details, it was an idea to see what others thought. But could include, benefits of working with the mailing list, testing, finding developers. Feedback on what would help them release Sane drivers with new units. David > Bye, > Henning > > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From henning at meier-geinitz.de Fri Jun 20 13:44:55 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 20 Jun 2003 14:44:55 +0200 Subject: [sane-devel] Manufactures In-Reply-To: <200306201253.53192.david@rondotheatre.co.uk> References: <200306201127.37790.david@rondotheatre.co.uk> <20030620113518.GH1867@meier-geinitz.de> <200306201253.53192.david@rondotheatre.co.uk> Message-ID: <20030620124455.GJ1867@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 12:53:53PM +0100, david stevenson wrote: > Yes, general encouragement, I had not thought about all the details, it was an > idea to see what others thought. > But could include, benefits of working with the mailing list, testing, finding > developers. Feedback on what would help them release Sane drivers with new > units. Ok, what about this one: http://www.meier-geinitz.de/sane/misc/manufacturers.html There is now also a page that explains the SANE license: http://www.meier-geinitz.de/sane/misc/license.html Bye, Henning From david at rondotheatre.co.uk Fri Jun 20 15:21:43 2003 From: david at rondotheatre.co.uk (david stevenson) Date: Fri, 20 Jun 2003 15:21:43 +0100 Subject: [sane-devel] Manufactures In-Reply-To: <20030620124455.GJ1867@meier-geinitz.de> References: <200306201127.37790.david@rondotheatre.co.uk> <200306201253.53192.david@rondotheatre.co.uk> <20030620124455.GJ1867@meier-geinitz.de> Message-ID: <200306201521.43432.david@rondotheatre.co.uk> Excellent, What instant service. Now all we need is manufactures to read it and start writing backends 8-) Thanks David > Ok, what about this one: > > http://www.meier-geinitz.de/sane/misc/manufacturers.html > > There is now also a page that explains the SANE license: > > http://www.meier-geinitz.de/sane/misc/license.html > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From Oliver.Schwartz at gmx.de Fri Jun 20 16:54:12 2003 From: Oliver.Schwartz at gmx.de (Oliver Schwartz) Date: Fri, 20 Jun 2003 17:54:12 +0200 Subject: [sane-devel] Sane support for Acer parallel port scanners In-Reply-To: <2263.1056009537@www36.gmx.net> References: <2263.1056009537@www36.gmx.net> Message-ID: <200306201754.37976.Oliver.Schwartz@gmx.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > It's a Acer / Benq 620P parallel port scanner, and in the Sane > compatibility list the status for a driver for this model is marked > as "unknown". Can you tell me if someone is working on a Sane > driver for this model? Or can I use another driver that will work > for my scanner too? As far as I know nobody ever got an Acer, Benq or Agfa scanner to work with the snapscan backend. I can't say for Acer/Benq, but at least Agfa seems to use it's own proprietary Parallel-SCSI adapter. There is no documentation available for it, so the only chance would be reverse-engineering the parallel port protocol using a logic analyzer. - -Oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+8y4p/V6sbrmfIuMRAvSwAJ0S0rHI3ZN7dSYEhhlIe6R8F5yPkACdGPnR JgOSvZrGyAdRtliWElH/t8k= =j962 -----END PGP SIGNATURE----- From adeuring at gmx.net Fri Jun 20 19:51:26 2003 From: adeuring at gmx.net (abel deuring) Date: Fri, 20 Jun 2003 20:51:26 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <20030619212211.GP12579@meier-geinitz.de> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> <3EF2160E.2090603@gmx.net> <20030619212211.GP12579@meier-geinitz.de> Message-ID: <3EF357AE.4090104@gmx.net> Henning Meier-Geinitz schrieb: > I'm not volunteering :-) but I can at least test if any of your > patches break Mustek scanners on FreeBSD. Great. I've already sent a patch to Martin, and it seems to fix the problems with the Microtek Scanamker II. Attached is the proposed new version (with Martin's fixes of my typos) of sanei_scsi_cmd2 for FreeBSD/CAM. It should replace the function near line 2765 in sanei_scsi.c. Abel -------------- next part -------------- #if USE == FREEBSD_CAM_INTERFACE SANE_Status sanei_scsi_cmd2(int fd, const void *cmd, size_t cmd_size, const void *src, size_t src_size, void *dst, size_t * dst_size) { /* xxx obsolete size_t cdb_size; */ struct cam_device *dev; union ccb *ccb; int rv; u_int32_t ccb_flags; char* data_buf; size_t data_len; SANE_Status status; if (fd < 0 || fd > CAM_MAXDEVS || cam_devices[fd] == NULL) { fprintf(stderr, "attempt to reference invalid unit %d\n", fd); return SANE_STATUS_INVAL; } /* xxx obsolete: cdb_size = CDB_SIZE (*(u_char *) src); */ dev = cam_devices[fd]; ccb = cam_getccb(dev); /* Build the CCB */ bzero(&(&ccb->ccb_h)[1], sizeof(struct ccb_scsiio)); bcopy(cmd, &ccb->csio.cdb_io.cdb_bytes, cmd_size); /* * Set the data direction flags. */ if(dst_size && *dst_size) { /* xxx obsolete: assert (cdb_size == src_size); */ ccb_flags = CAM_DIR_IN; data_buf = ((char*)(dst)); data_len = *dst_size; } else if(src_size > 0) { ccb_flags = CAM_DIR_OUT; data_buf = ((char*)(src)); data_len = src_size; } else { ccb_flags = CAM_DIR_NONE; data_buf = NULL; data_len = 0; } cam_fill_csio(&ccb->csio, /* retries */ 1, /* cbfncp */ NULL, /* flags */ ccb_flags, /* tag_action */ MSG_SIMPLE_Q_TAG, /* data_ptr */ (u_int8_t *)data_buf, /* dxfer_len */ data_len, /* sense_len */ SSD_FULL_SIZE, /* cdb_len */ cmd_size, /* timeout */ sane_scsicmd_timeout * 1000); /* Run the command */ errno = 0; if ((rv = cam_send_ccb(dev, ccb)) == -1) { cam_freeccb(ccb); return(SANE_STATUS_IO_ERROR); } if ((ccb->ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_CMP) { SANEI_SCSI_Sense_Handler handler; DBG (1, "sanei_scsi_cmd: scsi returned with status %d\n", (ccb->ccb_h.status & CAM_STATUS_MASK)); /* if((ccb->ccb_h.status & CAM_STATUS_MASK) == SANE_STATUS_DEVICE_BUSY) return SANE_STATUS_DEVICE_BUSY; */ switch (ccb->ccb_h.status & CAM_STATUS_MASK) { case CAM_BUSY: case CAM_SEL_TIMEOUT: case CAM_SCSI_BUSY: status = SANE_STATUS_DEVICE_BUSY; break; default: status = SANE_STATUS_IO_ERROR; } handler = fd_info[fd].sense_handler; if (handler && (ccb->ccb_h.status & CAM_AUTOSNS_VALID)) { SANE_Status st = (*handler) (fd, ((u_char*)(&ccb->csio.sense_data)), fd_info[fd].sense_handler_arg); cam_freeccb(ccb); return st; } else { cam_freeccb(ccb); return status; } } cam_freeccb(ccb); return SANE_STATUS_GOOD; } From tang at mac.com Fri Jun 20 23:40:53 2003 From: tang at mac.com (Dino Tang) Date: Fri, 20 Jun 2003 15:40:53 -0700 Subject: [sane-devel] Problem building on OSX Message-ID: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> > But that's only with USB, isn't it? Or even only with this scanner? As > far as I know, SCSI scanners work with the epson backend on MacOS X. > At least I have one report about the Epson Perfection 1640SU working. > > More reports on which scanners work or don't work on MacOS X are > welcome. > As long as the usblib was installed properly using the recent toolset ( Dec 2002 ), quite a few of USB and SCSI devices should work. I have tested and got images back from the following devices: - UMax Astra 1220U in USB mode * Reasonable image quality, still need color correction. - UMax Astra 2000U in USB mode * Serious image quality problem. - Epson Perfection 1640SU in both USB and SCSI modes * Good image quality. Support a lot of options. Good performance in SCSI mode. - Epson Perfection 2450 PHOTO in USB mode * Good image quality. Support a lot of options. Still has problems in FireWire mode. - CANON IX-06015C ( similar to CanoScan 600 ) in SCSI mode * Does not support tiff format! ( --format=tiff ). I can only get image back in pnm format. --format=tiff returned bad argument error. This seems like a problem of the canon backend. Please correct me if I'm wrong. I too would like to see reports on which scanners work or don't work on MacOS X. --Dino From nakal at web.de Sat Jun 21 00:31:54 2003 From: nakal at web.de (Nakal) Date: Sat, 21 Jun 2003 01:31:54 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF357AE.4090104@gmx.net> References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> Message-ID: <200306210131.54270.nakal@web.de> On Friday 20 June 2003 20:51, abel deuring wrote: > Great. I've already sent a patch to Martin, and it seems to fix the > problems with the Microtek Scanamker II. Attached is the proposed new > version (with Martin's fixes of my typos) of sanei_scsi_cmd2 for > FreeBSD/CAM. It should replace the function near line 2765 in > sanei_scsi.c. Hi! I verified Your latest (second) patch. It also works without any problems, e.a. compiles, scans and picture looks fine. On FreeBSD 5.1 everything works fine, too, with this patch. Even my problem with "scanimage -L" disappeared there (still remember? looks like a kernel bug in FreeBSD-4.8). Martin :) From peter at pscomp.com Sat Jun 21 01:03:21 2003 From: peter at pscomp.com (Peter Santoro) Date: Fri, 20 Jun 2003 20:03:21 -0400 Subject: [sane-devel] scanimage and scanadf command line args Message-ID: <3EF3A0C9.1090907@pscomp.com> My application makes use of scanimage and scanadf (sane 1.0.12 backend and 1.0.11 frontend) and it appears that there are a few inconsistencies with respect to the command line args of these sane front-ends. For instance, when using my fujitsu fi-4120c, "scanadf --help" shows that there is a "--paper_size" option available. Actually, it needs to be entered as "paper_size". Also, there is no "--threshold" option listed on the help screen, but it can be entered and it does appear to work correctly. There are other apparent inconsistencies I've run across using scanimage, but I don't remember them now. None of these issues are a big deal, but I was wondering if I was missing something here. Thanks for your help, Peter From adeuring at gmx.net Sat Jun 21 01:12:31 2003 From: adeuring at gmx.net (abel deuring) Date: Sat, 21 Jun 2003 02:12:31 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <200306210131.54270.nakal@web.de> References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> Message-ID: <3EF3A2EF.9020503@gmx.net> Nakal wrote: > I verified Your latest (second) patch. It also works without any > problems, e.a. compiles, scans and picture looks fine. > > On FreeBSD 5.1 everything works fine, too, with this patch. Even my > problem with "scanimage -L" disappeared there (still remember? looks > like a kernel bug in FreeBSD-4.8). Martin, thanks for this report. To be honest, i must admit that I can't really remember your first mails :( But it's nice to read that the patch fixes more bugs than expected :) Abel From adeuring at gmx.net Sat Jun 21 01:12:34 2003 From: adeuring at gmx.net (abel deuring) Date: Sat, 21 Jun 2003 02:12:34 +0200 Subject: [sane-devel] Problem building on OSX In-Reply-To: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> References: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> Message-ID: <3EF3A2F2.2090509@gmx.net> Dino Tang wrote: > - CANON IX-06015C ( similar to CanoScan 600 ) in SCSI mode > * Does not support tiff format! ( --format=tiff ). I can only get image > back in pnm format. --format=tiff returned bad argument error. This > seems like a problem of the canon backend. Please correct me if I'm wrong. The backends have no idea about image formats except the sane-internal "format", so it is unlikely that this is a problem of the Canon backend. Does scanimage --format=tiff works with other scanners and the same Sane installation? Abel From maddog at mir.com Sat Jun 21 02:13:39 2003 From: maddog at mir.com (Matto Marjanovic) Date: Fri, 20 Jun 2003 21:13:39 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF3A2EF.9020503@gmx.net> (message from abel deuring on Sat, 21 Jun 2003 02:12:31 +0200) References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> Message-ID: <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> >> I verified Your latest (second) patch. It also works without any >> problems, e.a. compiles, scans and picture looks fine. ... >thanks for this report. To be honest, i must admit that I can't really >remember your first mails :( But it's nice to read that the patch fixes >more bugs than expected :) Likewise, I lost track of some of this thread. (But it's nice to see that I'm not immediately on the hook to fix anything anymore.) What does the patch do? (And how did it fix up the Microtek scanning?) -matt m. From brian_d_w at yahoo.com Sat Jun 21 10:14:56 2003 From: brian_d_w at yahoo.com (Brian D. Williams) Date: Sat, 21 Jun 2003 02:14:56 -0700 (PDT) Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> Message-ID: <20030621091456.81112.qmail@web41501.mail.yahoo.com> I have been trying to get sane to work with the epson perfection 660. I could build sane with 1.0.11 but not with the snapscan addition. I could not build 1.0.12 at all. It would stop building at when trying to make scanimage but I didn't see any error messages that made sense to me. I am running the latest os x (10.2.6). Sadly I don't have a scanner available (other than the epson) to test against. Any suggestions would be greatly appreciated. Brian --- Dino Tang wrote: > > But that's only with USB, isn't it? Or even only with this scanner? As > > far as I know, SCSI scanners work with the epson backend on MacOS X. > > At least I have one report about the Epson Perfection 1640SU working. > > > > More reports on which scanners work or don't work on MacOS X are > > welcome. > > > > As long as the usblib was installed properly using the recent toolset ( > Dec 2002 ), quite a few of USB and SCSI devices should work. I have > tested and got images back from the following devices: > > - UMax Astra 1220U in USB mode > * Reasonable image quality, still need color correction. > - UMax Astra 2000U in USB mode > * Serious image quality problem. > - Epson Perfection 1640SU in both USB and SCSI modes > * Good image quality. Support a lot of options. Good performance in > SCSI mode. > - Epson Perfection 2450 PHOTO in USB mode > * Good image quality. Support a lot of options. Still has problems in > FireWire mode. > - CANON IX-06015C ( similar to CanoScan 600 ) in SCSI mode > * Does not support tiff format! ( --format=tiff ). I can only get > image back in pnm format. --format=tiff returned bad argument error. > This seems like a problem of the canon backend. Please correct me if > I'm wrong. > > I too would like to see reports on which scanners work or don't work on > MacOS X. > > --Dino > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel ===== Brian Williams homepage == From henning at meier-geinitz.de Sat Jun 21 10:47:05 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 21 Jun 2003 11:47:05 +0200 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621091456.81112.qmail@web41501.mail.yahoo.com> References: <3FF7104E-A370-11D7-BBE3-00039357FFB6@mac.com> <20030621091456.81112.qmail@web41501.mail.yahoo.com> Message-ID: <20030621094705.GB9347@meier-geinitz.de> Hi, On Sat, Jun 21, 2003 at 02:14:56AM -0700, Brian D. Williams wrote: > I have been trying to get sane to work with the epson perfection 660. I could > build sane with 1.0.11 but not with the snapscan addition. I could not build > 1.0.12 at all. It would stop building at when trying to make scanimage but I > didn't see any error messages that made sense to me. I am running the latest os > x (10.2.6). Sadly I don't have a scanner available (other than the epson) to > test against. Any suggestions would be greatly appreciated. Please show us the error messages (e.g. the last 100 lines of the output). Bye, Henning From a.deuring at satzbau-gmbh.de Sat Jun 21 13:13:18 2003 From: a.deuring at satzbau-gmbh.de (abel deuring) Date: Sat, 21 Jun 2003 14:13:18 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF44BDE.4B306A98@satzbau-gmbh.de> Matto Marjanovic wrote: > > >> I verified Your latest (second) patch. It also works without any > >> problems, e.a. compiles, scans and picture looks fine. > ... > >thanks for this report. To be honest, i must admit that I can't really > >remember your first mails :( But it's nice to read that the patch fixes > >more bugs than expected :) > > Likewise, I lost track of some of this thread. (But it's nice to see > that I'm not immediately on the hook to fix anything anymore.) > > What does the patch do? (And how did it fix up the Microtek scanning?) Don't ask for too specific details ;) The main point is, that the sense handler is no longer called for every error status returned by FreeBSD's CAM system. Instead, sanei_scsi_cmd2 now returns either SANE_STATUS_GOOD, SANE_STATUS_IO_ERROR, or SANE_STATUS_DEVICE_BUSY, depending on the status returned by the OS. The sense handler is only called, if ccb->ccb_h.status & CAM_AUTOSNS_VALID is true, which should guarantee that useful sense data is available. Several attempts to send a command to the scanner time out (the first one is the "stop scan" command), where "time out" means that the host could not send the command to the scanner within a certain time (for Linux, this is ~0.5 seconds). This time out is different from the "command time out" value, which is the time the host waits until a device finishes a SCSI command. Without the patch, the sense handler of backend is called for every failing command, but because no sense data is available, the sense handler decides to return SANE_STATUS_GOOD, hence the backend makes wrong assuptions about the status of the scanner. What I don't really understand in hindsight is the CAM status value 16 in Martin's log data. It indicates that the FreeBSD CAM system tried to issue a REQUEST SENSE for one or another failing command (where "failing" means in this case that the scanner accepted the command, and returned CHECK CONDITION), and that the REQUEST SENSE was not successful. Another point: I would really appreciate if more people could test the patch -- I have some hope that it is not too buggy in itself, but not being able to test it for myself (well, ok -- I'm too lazy or too busy to install FreeBSD -- chose whatever you want...), I'm hesitating to commit it to the CVS server. Abel From brian_d_w at yahoo.com Sat Jun 21 13:13:08 2003 From: brian_d_w at yahoo.com (Brian D. Williams) Date: Sat, 21 Jun 2003 05:13:08 -0700 (PDT) Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621094705.GB9347@meier-geinitz.de> Message-ID: <20030621121308.13540.qmail@web41502.mail.yahoo.com> Hi Henning (and others), I have attached the last 100+ lines from from make. Thanks Brian --- Henning Meier-Geinitz wrote: > Hi, > > On Sat, Jun 21, 2003 at 02:14:56AM -0700, Brian D. Williams wrote: > > I have been trying to get sane to work with the epson perfection 660. I > could > > build sane with 1.0.11 but not with the snapscan addition. I could not > build > > 1.0.12 at all. It would stop building at when trying to make scanimage but > I > > didn't see any error messages that made sense to me. I am running the > latest os > > x (10.2.6). Sadly I don't have a scanner available (other than the epson) > to > > test against. Any suggestions would be greatly appreciated. > > Please show us the error messages (e.g. the last 100 lines of the > output). > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel ===== Brian Williams homepage == -------------- next part -------------- gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=artec_eplus48u artec_eplus48u-s.c -fno-common -DPIC -o .libs/artec_eplus48u-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-artec_eplus48u.1.0.12.so .libs/artec_eplus48u.o .libs/artec_eplus48u-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o ../sanei/.libs/sanei_constrain_value.o ../sanei/.libs/sanei_usb.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-artec_eplus48u.1.so && ln -s libsane-artec_eplus48u.1.0.12.so libsane-artec_eplus48u.1.so) (cd .libs && rm -f libsane-artec_eplus48u.so && ln -s libsane-artec_eplus48u.1.0.12.so libsane-artec_eplus48u.so) creating libsane-artec_eplus48u.la (cd .libs && rm -f libsane-artec_eplus48u.la && ln -s ../libsane-artec_eplus48u.la libsane-artec_eplus48u.la) gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=ma1509 -DLIBDIR=/usr/local/lib/sane ma1509.c -fno-common -DPIC -o .libs/ma1509.o ma1509.c: In function `calibration': ma1509.c:826: warning: int format, long unsigned int arg (arg 3) ma1509.c: In function `send_gamma': ma1509.c:919: warning: int format, size_t arg (arg 3) rm -f ma1509-s.c ln -s ./stubs.c ma1509-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=ma1509 ma1509-s.c -fno-common -DPIC -o .libs/ma1509-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-ma1509.1.0.12.so .libs/ma1509.o .libs/ma1509-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o ../sanei/.libs/sanei_constrain_value.o ../sanei/.libs/sanei_usb.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-ma1509.1.so && ln -s libsane-ma1509.1.0.12.so libsane-ma1509.1.so) (cd .libs && rm -f libsane-ma1509.so && ln -s libsane-ma1509.1.0.12.so libsane-ma1509.so) creating libsane-ma1509.la (cd .libs && rm -f libsane-ma1509.la && ln -s ../libsane-ma1509.la libsane-ma1509.la) gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=ibm -DLIBDIR=/usr/local/lib/sane ibm.c -fno-common -DPIC -o .libs/ibm.o rm -f ibm-s.c ln -s ./stubs.c ibm-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=ibm ibm-s.c -fno-common -DPIC -o .libs/ibm-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-ibm.1.0.12.so .libs/ibm.o .libs/ibm-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o ../sanei/.libs/sanei_scsi.o ../sanei/.libs/sanei_config2.o ../sanei/.libs/sanei_constrain_value.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-ibm.1.so && ln -s libsane-ibm.1.0.12.so libsane-ibm.1.so) (cd .libs && rm -f libsane-ibm.so && ln -s libsane-ibm.1.0.12.so libsane-ibm.so) creating libsane-ibm.la (cd .libs && rm -f libsane-ibm.la && ln -s ../libsane-ibm.la libsane-ibm.la) gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=hp5400 -DLIBDIR=/usr/local/lib/sane hp5400.c -fno-common -DPIC -o .libs/hp5400.o In file included from hp5400.c:77: hp5400_internal.c: In function `CircBufferInit': hp5400_internal.c:411: warning: unused parameter `iHandle' hp5400_internal.c: In function `hp5400_test_scan_response': hp5400_internal.c:660: warning: unused parameter `req' hp5400_internal.c: In function `DoScan': hp5400_internal.c:729: warning: unused parameter `code' hp5400_internal.c: In function `hp5400_scan': hp5400_internal.c:909: warning: unused parameter `pHWParams' hp5400_internal.c: In function `InitScanner': hp5400_internal.c:1021: warning: int format, long unsigned int arg (arg 3) hp5400_internal.c: In function `InitScan2': hp5400_internal.c:1187: warning: comparison between signed and unsigned hp5400_internal.c:1223: warning: comparison between signed and unsigned In file included from hp5400.c:78: hp5400_sanei.c: In function `hp5400_bulk_read': hp5400_sanei.c:279: warning: passing arg 3 of `sanei_usb_read_bulk' from incompatible pointer type hp5400_sanei.c: In function `hp5400_bulk_read_block': hp5400_sanei.c:308: warning: passing arg 3 of `sanei_usb_read_bulk' from incompatible pointer type hp5400_sanei.c: In function `hp5400_bulk_command_write': hp5400_sanei.c:345: warning: passing arg 3 of `sanei_usb_write_bulk' from incompatible pointer type hp5400.c: In function `attach_one_device': hp5400.c:432: warning: passing arg 1 of `HP5400Detect' discards qualifiers from pointer target type /usr/include/stdio.h: At top level: hp5400_sanei.c:253: warning: `hp5400_bulk_read' defined but not used hp5400_sanei.c:361: warning: `hp5400_isOn' defined but not used hp5400_internal.c:605: warning: `DecodeImage' defined but not used hp5400_internal.c:661: warning: `hp5400_test_scan_response' defined but not used hp5400_internal.c:975: warning: `PreviewScan' defined but not used hp5400_internal.c:1013: warning: `InitScanner' defined but not used rm -f hp5400-s.c ln -s ./stubs.c hp5400-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=hp5400 hp5400-s.c -fno-common -DPIC -o .libs/hp5400-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-hp5400.1.0.12.so .libs/hp5400.o .libs/hp5400-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o ../sanei/.libs/sanei_usb.o ../sanei/.libs/sanei_config2.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-hp5400.1.so && ln -s libsane-hp5400.1.0.12.so libsane-hp5400.1.so) (cd .libs && rm -f libsane-hp5400.so && ln -s libsane-hp5400.1.0.12.so libsane-hp5400.so) creating libsane-hp5400.la (cd .libs && rm -f libsane-hp5400.la && ln -s ../libsane-hp5400.la libsane-hp5400.la) rm -f dll-preload.c list=""; for be in $list; do \ echo "PRELOAD_DECL($be)" >> dll-preload.c; \ done echo "static struct backend preloaded_backends[] = {" >> dll-preload.c sep=""; \ list=""; \ if test -z "${list}"; then \ echo { 0, 0, 0, 0, 0, 0, {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 }} >> dll-preload.c; \ else \ for be in $list; do \ echo "${sep}PRELOAD_DEFN($be)" >> dll-preload.c; \ sep=","; \ done; \ fi echo "};" >> dll-preload.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DBACKEND_NAME=dll -DLIBDIR=/usr/local/lib/sane dll.c -fno-common -DPIC -o .libs/dll.o dll.c: In function `load': dll.c:418: warning: `op' might be used uninitialized in this function rm -f dll-s.c ln -s ./stubs.c dll-s.c gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I. -I../include -I../include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -DSTUBS -DBACKEND_NAME=dll dll-s.c -fno-common -DPIC -o .libs/dll-s.o gcc -bundle -flat_namespace -undefined suppress -o .libs/libsane-dll.1.0.12.so .libs/dll.o .libs/dll-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit (cd .libs && rm -f libsane-dll.1.so && ln -s libsane-dll.1.0.12.so libsane-dll.1.so) (cd .libs && rm -f libsane-dll.so && ln -s libsane-dll.1.0.12.so libsane-dll.so) creating libsane-dll.la (cd .libs && rm -f libsane-dll.la && ln -s ../libsane-dll.la libsane-dll.la) gcc -dynamiclib -flat_namespace -undefined suppress -o .libs/libsane.1.0.12.dylib .libs/dll.o .libs/dll-s.o .libs/sane_strstatus.o ../sanei/.libs/sanei_init_debug.o ../sanei/.libs/sanei_config.o ../lib/.libs/isfdtype.o ../lib/.libs/strndup.o /usr/local/lib/libusb.dylib -lm -framework CoreFoundation -framework IOKit -install_name /usr/local/lib/libsane.1.dylib -compatibility_version 2 -current_version 2.12 (cd .libs && rm -f libsane.1.dylib && ln -s libsane.1.0.12.dylib libsane.1.dylib) (cd .libs && rm -f libsane.dylib && ln -s libsane.1.0.12.dylib libsane.dylib) creating libsane.la (cd .libs && rm -f libsane.la && ln -s ../libsane.la libsane.la) making all in frontend gcc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I/usr/local/include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -g -O2 -W -Wall scanimage.c scanimage.c: In function `scan_it': scanimage.c:1020: warning: unused variable `hang_over' gcc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I/usr/local/include -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_SANE_DATA_DIR=/usr/local/share -DV_MAJOR=1 -DV_MINOR=0 -g -O2 -W -Wall stiff.c mkdir .libs gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a ../backend/.libs/libsane.dylib /usr/local/lib/libusb.dylib -lIOKit -lm -framework CoreFoundation -framework IOKit ld: multiple definitions of symbol _getopt /usr/lib/libm.dylib(getopt.So) definition of _getopt ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text) ld: multiple definitions of symbol _opterr /usr/lib/libm.dylib(getopt.So) definition of _opterr ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data) ld: multiple definitions of symbol _optind /usr/lib/libm.dylib(getopt.So) definition of _optind ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data) ld: multiple definitions of symbol _optopt /usr/lib/libm.dylib(getopt.So) definition of _optopt ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data) make[1]: *** [scanimage] Error 1 make: *** [all-recursive] Error 1 From henning at meier-geinitz.de Sat Jun 21 13:52:53 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 21 Jun 2003 14:52:53 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF357AE.4090104@gmx.net> References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> <3EF2160E.2090603@gmx.net> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> Message-ID: <20030621125253.GC9347@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 08:51:26PM +0200, abel deuring wrote: > Henning Meier-Geinitz schrieb: > > >I'm not volunteering :-) but I can at least test if any of your > >patches break Mustek scanners on FreeBSD. > > Great. I've already sent a patch to Martin, and it seems to fix the > problems with the Microtek Scanamker II. Attached is the proposed new > version (with Martin's fixes of my typos) of sanei_scsi_cmd2 for > FreeBSD/CAM. It should replace the function near line 2765 in sanei_scsi.c. Ok. I haven't tested FreeBSD with older scanners for some time so here are my results with Mustek SCSI scanners (symbios-compatible 810 SCSI controller, FreeBSD 5.0, sym driver): Scanner 1.0.12 your patch ------------------------------------------------------------------------ ScanExpress 6000 SP (relatively new) ok ok Paragon 1200 SP Pro (relatively new) detected, same but timeout Paragon 12000 SP (older) not detected not detected Paragon 12000 CX (stone age three-pass) not detected not detected If I try to use the "ncr" driver instead of "sym", FreeBSD doesn't even boot. With a Tekram 315 controller the results are the same as above. So your patch is ok but FreeBSD 5.0 is unusable with older Mustek scanners on at least these controllers. The scanners work just fine on Linux. The timeout with the Paragon 1200 SP Pro occurs when the lamp warms up that warm-up can take upto about 70 seconds. With Linux and the later SANE versiosn that's not a problem but FreeBSD seems to ignore the 120 seconds timeout. When the lamp is warm, the scan starts ok but sounds horribly and never finishes. No idea why, but this also happens without your patch. The "not-detection" looks like this: Booting FreeBSD stops and the scanner LED starts blinking. Looks like the scanner gets sent an invalid command from the kernel. If I turn off the scanner, FreeBSD boots. When I run "camcontrol rescan all", the scanner blinks again and camcontrol freezes. If I remember correctly, the old scanners worked once with FreeBSD. So maybe 5.0 has broken the SCSI system? Bye, Henning From maddog at mir.com Sat Jun 21 13:53:58 2003 From: maddog at mir.com (Matto Marjanovic) Date: Sat, 21 Jun 2003 08:53:58 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF44BDE.4B306A98@satzbau-gmbh.de> (message from abel deuring on Sat, 21 Jun 2003 14:13:18 +0200) References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> Message-ID: <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> >> What does the patch do? (And how did it fix up the Microtek scanning?) ... >depending on the status returned by the OS. The sense handler is only >called, if ccb->ccb_h.status & CAM_AUTOSNS_VALID is true, which should >guarantee that useful sense data is available. ... >Without the patch, the sense handler of backend is called for every >failing command, but because no sense data is available, the sense >handler decides to return SANE_STATUS_GOOD, hence the backend makes >wrong assuptions about the status of the scanner. > >What I don't really understand in hindsight is the CAM status value 16 >in Martin's log data. It indicates that the FreeBSD CAM system tried to >issue a REQUEST SENSE for one or another failing command (where >"failing" means in this case that the scanner accepted the command, and >returned CHECK CONDITION), and that the REQUEST SENSE was not >successful. A-ha --- ok, the sense handler is not called, an error condition is returned, and then - I imagine - the retry logic in the backend takes over. With regards to the mystery status value: in this situation under Linux (i.e., the scanner is busy, won't accept next command), a REQUEST SENSE *is* issued and the scanner *does* respond to it. However, the returned data does not conform to SCSI-2. In particular, the bit defined by Microtek to mean "this is valid sense data" is the bit which, in SCSI-2, means "this is *not* valid sense data". Because of this, the mid-level Linux SCSI driver *zeros out* the sense data, yet still indicates that REQUEST SENSE has been issued. Thus the backend's sense handler is called with absolutely nothing and decides "No error". I suspect a similar thing is happening in the FreeBSD CAM system --- some midlevel driver is unnecessarily killing the sense data. Your patch checks to see if the system thought the sense data is/was valid, and since it was declared invalid, issues a general error instead. It's just a theory... (I've never tried nor read FreeBSD code), -matt m. From henning at meier-geinitz.de Sat Jun 21 13:57:41 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 21 Jun 2003 14:57:41 +0200 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621121308.13540.qmail@web41502.mail.yahoo.com> References: <20030621094705.GB9347@meier-geinitz.de> <20030621121308.13540.qmail@web41502.mail.yahoo.com> Message-ID: <20030621125741.GD9347@meier-geinitz.de> Hi, On Sat, Jun 21, 2003 at 05:13:08AM -0700, Brian D. Williams wrote: > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a ../backend/.libs/libsane.dylib /usr/local/lib/libusb.dylib -lIOKit -lm -framework CoreFoundation -framework IOKit > ld: multiple definitions of symbol _getopt > /usr/lib/libm.dylib(getopt.So) definition of _getopt > ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text) > ld: multiple definitions of symbol _opterr > /usr/lib/libm.dylib(getopt.So) definition of _opterr > ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data) > ld: multiple definitions of symbol _optind > /usr/lib/libm.dylib(getopt.So) definition of _optind > ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data) > ld: multiple definitions of symbol _optopt > /usr/lib/libm.dylib(getopt.So) definition of _optopt > ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data) Yeah, that's the already known multiple definition error. Some MacOS X users don't seem to get that error, some see it. No idea why. And, by the way, I have no idea why libm should define _getopt. Bye, Henning From a.deuring at satzbau-gmbh.de Sat Jun 21 15:31:27 2003 From: a.deuring at satzbau-gmbh.de (abel deuring) Date: Sat, 21 Jun 2003 16:31:27 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF46C3F.A897D7C4@satzbau-gmbh.de> Matto Marjanovic wrote: > A-ha --- ok, the sense handler is not called, an error condition is returned, > and then - I imagine - the retry logic in the backend takes over. Right, I think that's happening. > > With regards to the mystery status value: in this situation under Linux > (i.e., the scanner is busy, won't accept next command), a REQUEST SENSE > *is* issued and the scanner *does* respond to it. However, the returned > data does not conform to SCSI-2. In particular, the bit defined by > Microtek to mean "this is valid sense data" is the bit which, in SCSI-2, > means "this is *not* valid sense data". > Because of this, the mid-level Linux SCSI driver *zeros out* the sense data, > yet still indicates that REQUEST SENSE has been issued. Thus the backend's > sense handler is called with absolutely nothing and decides "No error". > > I suspect a similar thing is happening in the FreeBSD CAM system --- some > midlevel driver is unnecessarily killing the sense data. Your patch checks > to see if the system thought the sense data is/was valid, and since it was > declared invalid, issues a general error instead. Matt, are you sure that the Linux SCSI system (or FreeBSD) tries to issue a REQUEST SENSE, if it can't "connect" to device? (If I find enough time, I'll try that at home today or tomorrow. Shouldn't be difficult to provoke such a situation with my Sharp JX250. Removing the O_EXCL flag on the open call for the device file, using huge data blocks for READ commands and then attepting to access the scanner form a different process are worth a try.) OK, a SCSI device should be able to respond to a few basic commands like INQUIRY or REQUEST SENSE under more or less any circumstances, but the main point of the error "can't issue a SCSI command, because the device is busy" is to try it again later. I don't see the point, which additional information a REQUEST SENSE would provide. It's another point, if a command has been accepted by the device. If this command results in an error, a REQUEST SENSE if of course useful. Abel From a.deuring at satzbau-gmbh.de Sat Jun 21 15:38:43 2003 From: a.deuring at satzbau-gmbh.de (abel deuring) Date: Sat, 21 Jun 2003 16:38:43 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <3EEF8884.2000805@gmx.net> <41-Wed18Jun2003133009-0400-maddog@yoo-hoo.ai.mit.edu> <200306182351.22833.nakal@web.de> <3EF2160E.2090603@gmx.net> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <20030621125253.GC9347@meier-geinitz.de> Message-ID: <3EF46DF3.78959F15@satzbau-gmbh.de> Henning Meier-Geinitz wrote: > Ok. I haven't tested FreeBSD with older scanners for some time so here > are my results with Mustek SCSI scanners (symbios-compatible 810 SCSI > controller, FreeBSD 5.0, sym driver): > > Scanner 1.0.12 your patch > ------------------------------------------------------------------------ > ScanExpress 6000 SP (relatively new) ok ok > Paragon 1200 SP Pro (relatively new) detected, same > but timeout > Paragon 12000 SP (older) not detected not detected > Paragon 12000 CX (stone age three-pass) not detected not detected > > If I try to use the "ncr" driver instead of "sym", FreeBSD doesn't > even boot. With a Tekram 315 controller the results are the same as > above. > > So your patch is ok but FreeBSD 5.0 is unusable with older Mustek > scanners on at least these controllers. The scanners work just fine on > Linux. But we have least no new problems ;) > > The timeout with the Paragon 1200 SP Pro occurs when the lamp warms up > that warm-up can take upto about 70 seconds. With Linux and the later > SANE versiosn that's not a problem but FreeBSD seems to ignore the 120 > seconds timeout. When the lamp is warm, the scan starts ok but sounds > horribly and never finishes. No idea why, but this also happens > without your patch. > > The "not-detection" looks like this: Booting FreeBSD stops and the > scanner LED starts blinking. Looks like the scanner gets sent an > invalid command from the kernel. If I turn off the scanner, FreeBSD > boots. When I run "camcontrol rescan all", the scanner blinks again > and camcontrol freezes. > > If I remember correctly, the old scanners worked once with FreeBSD. So > maybe 5.0 has broken the SCSI system? It could be that it does not like older, very slow SCSI devices. IIRC, some Linux SCSI adapter drivers could not detect the Scanmaker II during a modprobe. The problem was that the scanner was too busy after a bus reset that it did not respond to the typoical INQUIRY. A later "echo scsi add-single-device ..." fixed that. Abel From brian_d_w at yahoo.com Sat Jun 21 17:04:34 2003 From: brian_d_w at yahoo.com (Brian D. Williams) Date: Sat, 21 Jun 2003 09:04:34 -0700 (PDT) Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621125741.GD9347@meier-geinitz.de> Message-ID: <20030621160434.54189.qmail@web41502.mail.yahoo.com> Hi, Thanks for having a look at that. Could I remove the offending define(s)? Brian --- Henning Meier-Geinitz wrote: > Hi, > > On Sat, Jun 21, 2003 at 05:13:08AM -0700, Brian D. Williams wrote: > > gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a > ../backend/.libs/libsane.dylib /usr/local/lib/libusb.dylib -lIOKit -lm > -framework CoreFoundation -framework IOKit > > ld: multiple definitions of symbol _getopt > > /usr/lib/libm.dylib(getopt.So) definition of _getopt > > ../lib/liblib.a(getopt.o) definition of _getopt in section (__TEXT,__text) > > ld: multiple definitions of symbol _opterr > > /usr/lib/libm.dylib(getopt.So) definition of _opterr > > ../lib/liblib.a(getopt.o) definition of _opterr in section (__DATA,__data) > > ld: multiple definitions of symbol _optind > > /usr/lib/libm.dylib(getopt.So) definition of _optind > > ../lib/liblib.a(getopt.o) definition of _optind in section (__DATA,__data) > > ld: multiple definitions of symbol _optopt > > /usr/lib/libm.dylib(getopt.So) definition of _optopt > > ../lib/liblib.a(getopt.o) definition of _optopt in section (__DATA,__data) > > Yeah, that's the already known multiple definition error. Some MacOS X > users don't seem to get that error, some see it. No idea why. > And, by the way, I have no idea why libm should define _getopt. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel ===== Brian Williams homepage == From horst.schlonz at gmx.de Sat Jun 21 17:14:23 2003 From: horst.schlonz at gmx.de (horst.schlonz at gmx.de) Date: Sat, 21 Jun 2003 18:14:23 +0200 Subject: [sane-devel] mustek scanexpress 6000 p does not work anymore Message-ID: <200306211814.24072.horst.schlonz@gmx.de> i searched the archives for this issue to no avail. my se 6000p always worked with this mustek_pp.conf: name SE-6000P vendor Mustek option wait-lamp 15 apparently the syntax of mustek_pp.conf changed in recent versions of sane. there are some examples in the new mustek_pp.conf: # Uncomment/customize to your needs # # scanner Mustek-600CP 0x378 cis600 # scanner Mustek-1200CP 0x378 cis1200 # scanner Mustek-1200CP+ 0x378 cis1200+ but none of these fits to my se 6000p. according to this site http://www.penguin-breeder.org/sane/mustek_pp/#supported%20scanners ccd-scanners are not working any more. nice... they say i have to use sane <= 10.0.9. is think, they meant 1.0.9, so i compiled, installed an configured sane-backends 1.0.9 and sane-frontends 1.0.9. it's no use: # cat /usr/local/etc/sane.d/dll.conf mustek_pp # cat /usr/local/etc/sane.d/mustek_pp.conf option io-mode alt_lock option niceload port 0x378 name SE-6000P vendor Mustek option wait-lamp 15 # SANE_DEBUG_MUSTEK_PP=128 scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). root at sputnik:/home/headroom/Desktop/sane-frontends-1.0.9# can anybody please help me with this? i need to scan urgently. From peter at pscomp.com Sat Jun 21 18:22:07 2003 From: peter at pscomp.com (Peter Santoro) Date: Sat, 21 Jun 2003 13:22:07 -0400 Subject: [sane-devel] scheme interface for sane? Message-ID: <3EF4943F.2050102@pscomp.com> I'm currently using sane via scanimage and scanadf from scheme. If anyone has written a scheme extension/interface (preferably mzscheme) for sane or managed to call it from some ffi, I would appreciate hearing about it. Thank you, Peter From kmoffat at drizzle.com Sat Jun 21 18:59:44 2003 From: kmoffat at drizzle.com (Ken Moffat) Date: Sat, 21 Jun 2003 10:59:44 -0700 Subject: [sane-devel] WinXP problem Message-ID: <3EF49D10.2020804@drizzle.com> New user, first posting, probably just brainfade, but here's my problem: I use xsane on linux (libranet, a debian derivative) with an Epson 1660 scanner, and just installed xsane on WinXP on my home network. I have sane serving from libranet, and it works well from my other linux (debian 3.0) box. However, on WinXP I get errors about not being able to create temp files; many errors on startup, get preview and shutdown. This is true with unprivileged users on XP, but with a privileged user all is working. Does anyone have a fix? or is this just an out-of-luck on XP condition? (I don't wish to make my teenagers privileged if I can help it! ;-) ) -- Ken From tang at mac.com Sat Jun 21 20:00:39 2003 From: tang at mac.com (Dino Tang) Date: Sat, 21 Jun 2003 12:00:39 -0700 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621091456.81112.qmail@web41501.mail.yahoo.com> Message-ID: Hi Brian, You have the latest system, but you might not have the latest tool set. You can open the Project Builder and use the "About Project Builder" to find out what version you have. If it doesn't say "Version 2.1 (December 2002 Developer Tools)", you don't have the latest tool set. You can download the latest tools from the ADC ( Apple Developer Connection ) site. The "multiple symbol defined" problem has to do with the way you compile libusb. Mattias Ellert has sent me the following explanation and patch awhile back. Cheers! --Dino --- beginning Mattias's message --- If you get that error even when linking against libusb, I guess you didn't patch the libusb before compiling it. The attached patch should be applied to libusb before compiling. It does build without the patch, but the configure script cheats a bit and links frameworks as libraries, so the dependencies don't get recorded correctly in the libraries. This means that when you compile something that depends on libusb you might get into trouble -- as you did. Since the libusb patch changes some autoconf/automake files you need to rerun those. My build instructions for libusb are as follows. (The --disable-static is optional of course.) In this way you get a library with the correct dependencies recorded. tar -z -x -f libusb-0.1.7.tar.gz patch -p0 < frameworks.patch cd libusb-0.1.7 # Remove 'missing' in order to avoid warning about it being old during configure. # A newer version will be installed by automake. rm missing aclocal automake --add-missing autoconf ./configure --disable-static make Mattias PS. I have sent the patch to the maintainer of libusb, so it might be included in the next official release if it is accepted. The SANE prerelease already has the corresponding patch included. diff -ur libusb-0.1.7.orig/Makefile.am libusb-0.1.7/Makefile.am --- libusb-0.1.7.orig/Makefile.am Mon Nov 11 19:04:15 2002 +++ libusb-0.1.7/Makefile.am Sun Mar 2 15:59:42 2003 @@ -28,7 +28,7 @@ if DARWIN_API OS_SUPPORT = darwin.c CFLAGS_EXT = -no-cpp-precomp -LDADDS = -lIOKit -framework "CoreFoundation" +LDADDS = -framework IOKit -framework CoreFoundation else OS_SUPPORT = endif diff -ur libusb-0.1.7.orig/configure.in libusb-0.1.7/configure.in --- libusb-0.1.7.orig/configure.in Sun Nov 17 19:45:15 2002 +++ libusb-0.1.7/configure.in Sun Mar 2 15:59:42 2003 @@ -11,7 +11,8 @@ dnl we need to AC_DIVERT_PUSH/AC_DIVERT_POP these variable definitions so they dnl are available for $ac_help expansion (don't we all *love* autoconf?) -AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)dnl +ifdef([AC_DIVERSION_NOTICE], [AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)], + [AC_DIVERT_PUSH(NOTICE)]) # # The following version number definitions apply to libusb @@ -76,7 +77,8 @@ dnl Initialize maintainer mode AM_MAINTAINER_MODE -AC_CANONICAL_HOST +dnl This has already been dragged in by AM_PROG_LIBTOOL +dnl AC_CANONICAL_HOST AC_MSG_CHECKING(for what USB OS support) case $host in @@ -99,7 +101,7 @@ AC_SUBST(DARWIN_API) os_support=darwin AC_MSG_RESULT(Darwin and/or MacOS 10) - OSLIBS="-lIOKit" + OSLIBS="-framework IOKit" ;; esac @@ -111,7 +113,8 @@ dnl figure debugging default, prior to $ac_help setup dnl -AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)dnl +ifdef([AC_DIVERSION_NOTICE], [AC_DIVERT_PUSH(AC_DIVERSION_NOTICE)], + [AC_DIVERT_PUSH(NOTICE)]) if test `expr $LIBUSB_MINOR_VERSION \% 2` = 1 ; then debug_default=yes else diff -ur libusb-0.1.7.orig/ltmain.sh libusb-0.1.7/ltmain.sh --- libusb-0.1.7.orig/ltmain.sh Wed Mar 27 20:10:10 2002 +++ libusb-0.1.7/ltmain.sh Sun Mar 2 15:59:42 2003 @@ -887,6 +887,11 @@ prev= continue ;; + framework) + deplibs="$deplibs -framework $arg" + prev= + continue + ;; release) release="-$arg" prev= @@ -988,6 +993,11 @@ continue ;; + -framework) + prev=framework + continue + ;; + # The native IRIX linker understands -LANG:*, -LIST:* and -LNO:* # so, if we see these flags be careful not to treat them like -L -L[A-Z][A-Z]*:*) @@ -1378,10 +1388,37 @@ link) libs="$deplibs %DEPLIBS% $dependency_libs" ;; esac fi + prev= for deplib in $libs; do + case $prev in + "") ;; + framework) + prev= + if test $linkmode = oldlib && test $linkmode = obj; then + $echo "$modename: warning: \`-framework' is ignored for archives/objects: $deplib" 1>&2 + continue + fi + if test $pass = conv; then + deplibs="-framework $deplib $deplibs" + continue + fi + if test "$linkmode,$pass" = "prog,link"; then + compile_deplibs="-framework $deplib $compile_deplibs" + finalize_deplibs="-framework $deplib $finalize_deplibs" + else + deplibs="-framework $deplib $deplibs" + test $linkmode = lib && newdependency_libs="-framework $deplib $newdependency_libs" + fi + continue + ;; + esac lib= found=no case $deplib in + -framework) + prev=framework + continue + ;; -l*) if test "$linkmode" = oldlib && test "$linkmode" = obj; then $echo "$modename: warning: \`-l' is ignored for archives/objects: $deplib" 1>&2 @@ -1553,12 +1590,35 @@ convenience="$convenience $ladir/$objdir/$old_library" old_convenience="$old_convenience $ladir/$objdir/$old_library" tmp_libs= + prev= for deplib in $dependency_libs; do - deplibs="$deplib $deplibs" - case "$tmp_libs " in - *" $deplib "*) specialdeplibs="$specialdeplibs $deplib" ;; + case $deplib in + -framework) + prev=framework + continue + ;; + *) + case $prev in + framework) + deplibs="-framework $deplib $deplibs" + case "$tmp_libs " in + *" $deplib "*) + specialdeplibs="$specialdeplibs -framework $deplib" ;; + esac + tmp_libs="$tmp_libs -framework $deplib" + ;; + *) + deplibs="$deplib $deplibs" + case "$tmp_libs " in + *" $deplib "*) + specialdeplibs="$specialdeplibs $deplib" ;; + esac + tmp_libs="$tmp_libs $deplib" + ;; + esac + ;; esac - tmp_libs="$tmp_libs $deplib" + prev= done elif test "$linkmode" != prog && test "$linkmode" != lib; then $echo "$modename: \`$lib' is not a convenience library" 1>&2 @@ -1668,22 +1728,34 @@ fi tmp_libs= + prev= for deplib in $dependency_libs; do case $deplib in + -framework) + prev=framework + continue + ;; -L*) newlib_search_path="$newlib_search_path "`$echo "X$deplib" | $Xsed -e 's/^-L//'`;; ### testsuite: skip nested quoting test esac # Need to link against all dependency_libs? if test "$linkalldeplibs" = yes; then - deplibs="$deplib $deplibs" + case $prev in + framework) deplibs="-framework $deplib $deplibs" ;; + *) deplibs="$deplib $deplibs" ;; + esac else # Need to hardcode shared library paths # or/and link against static libraries - newdependency_libs="$deplib $newdependency_libs" + case $prev in + framework) newdependency_libs="-framework $deplib $newdependency_libs" ;; + *) newdependency_libs="$deplib $newdependency_libs" ;; + esac fi case "$tmp_libs " in *" $deplib "*) specialdeplibs="$specialdeplibs $deplib" ;; esac tmp_libs="$tmp_libs $deplib" + prev= done # for deplib continue fi # $linkmode = prog... @@ -1979,12 +2051,35 @@ test "$link_static" = no && newdependency_libs="$abs_ladir/$laname $newdependency_libs" # ... and its dependency_libs tmp_libs= + prev= for deplib in $dependency_libs; do - newdependency_libs="$deplib $newdependency_libs" - case "$tmp_libs " in - *" $deplib "*) specialdeplibs="$specialdeplibs $deplib" ;; + case $deplib in + -framework) + prev=framework + continue + ;; + *) + case $prev in + framework) + newdependency_libs="-framework $deplib $newdependency_libs" + case "$tmp_libs " in + *" $deplib "*) + specialdeplibs="$specialdeplibs -framework $deplib" ;; + esac + tmp_libs="$tmp_libs -framework $deplib" + ;; + *) + newdependency_libs="$deplib $newdependency_libs" + case "$tmp_libs " in + *" $deplib "*) + specialdeplibs="$specialdeplibs $deplib" ;; + esac + tmp_libs="$tmp_libs $deplib" + ;; + esac + ;; esac - tmp_libs="$tmp_libs $deplib" + prev= done if test "$link_all_deplibs" != no; then @@ -2032,8 +2127,21 @@ done # for deplib in $libs if test "$pass" = dlpreopen; then # Link the dlpreopened libraries before other libraries + prev= for deplib in $save_deplibs; do - deplibs="$deplib $deplibs" + case $deplib in + -framework) + prev=framework + continue + ;; + *) + case $prev in + framework) deplibs="-framework $deplib $deplibs" ;; + *) deplibs="$deplib $deplibs" ;; + esac + ;; + esac + prev= done fi if test "$pass" != dlopen; then @@ -2059,21 +2167,37 @@ # Add libraries to $var in reverse order eval tmp_libs=\"\$$var\" new_libs= + prev= for deplib in $tmp_libs; do case $deplib in + -framework) + prev=framework + continue + ;; -L*) new_libs="$deplib $new_libs" ;; *) case " $specialdeplibs " in - *" $deplib "*) new_libs="$deplib $new_libs" ;; + *" $deplib "*) + case $prev in + framework) new_libs="-framework $deplib $new_libs" ;; + *) new_libs="$deplib $new_libs" ;; + esac + ;; *) case " $new_libs " in *" $deplib "*) ;; - *) new_libs="$deplib $new_libs" ;; + *) + case $prev in + framework) new_libs="-framework $deplib $new_libs" ;; + *) new_libs="$deplib $new_libs" ;; + esac + ;; esac ;; esac ;; esac + prev= done tmp_libs= for deplib in $new_libs; do --- ending Mattias's message --- On Saturday, June 21, 2003, at 02:14 AM, Brian D. Williams wrote: > I have been trying to get sane to work with the epson perfection 660. > I could > build sane with 1.0.11 but not with the snapscan addition. I could not > build > 1.0.12 at all. It would stop building at when trying to make scanimage > but I > didn't see any error messages that made sense to me. I am running the > latest os > x (10.2.6). Sadly I don't have a scanner available (other than the > epson) to > test against. Any suggestions would be greatly appreciated. > > Brian From tang at mac.com Sat Jun 21 20:05:54 2003 From: tang at mac.com (Dino Tang) Date: Sat, 21 Jun 2003 12:05:54 -0700 Subject: [sane-devel] Problem building on OSX Message-ID: <61F1E17F-A41B-11D7-8041-00039357FFB6@mac.com> > The backends have no idea about image formats except the sane-internal > "format", so it is unlikely that this is a problem of the Canon > backend. > Does scanimage --format=tiff works with other scanners and the same > Sane > installation? > This is what I expect. The --format=tiff option works fine on the other backends. I only run into problem with the canon backend. --Dino From anoah at pfeiffer.edu Sat Jun 21 20:53:31 2003 From: anoah at pfeiffer.edu (m. allan noah) Date: Sat, 21 Jun 2003 15:53:31 -0400 (EDT) Subject: [sane-devel] scanimage and scanadf command line args In-Reply-To: <3EF3A0C9.1090907@pscomp.com> Message-ID: the options you are discussing are backend specific. with no scanner attached to the machine, if you run scanimage --help and scanadf --help, you will see nothing about scanning options, only input and output file, and file format. the threshold and paper size options are provided by the scanner backend, so if they malfunction, it is probably my fujitsu 4120 code :) the fact that one of them works, but is hidden, perhaps is because that option is set to SANE_CAP_ADVANCED, which hides it from most users (try using xsane, you will see the advanced option in menu, iirc). allan On Fri, 20 Jun 2003, Peter Santoro wrote: > My application makes use of scanimage and scanadf (sane 1.0.12 backend and 1.0.11 frontend) and it appears that there > are a few inconsistencies with respect to the command line args of these sane front-ends. > > For instance, when using my fujitsu fi-4120c, "scanadf --help" shows that there is a "--paper_size" option available. > Actually, it needs to be entered as "paper_size". Also, there is no "--threshold" option listed on the help screen, but > it can be entered and it does appear to work correctly. There are other apparent inconsistencies I've run across > using scanimage, but I don't remember them now. > > None of these issues are a big deal, but I was wondering if I was missing something here. > > Thanks for your help, > > Peter > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From oliver.rauch at rauch-domain.de Sat Jun 21 21:26:11 2003 From: oliver.rauch at rauch-domain.de (Oliver Rauch) Date: Sat, 21 Jun 2003 22:26:11 +0200 Subject: [sane-devel] WinXP problem In-Reply-To: <3EF49D10.2020804@drizzle.com> References: <3EF49D10.2020804@drizzle.com> Message-ID: <200306212226.11105.oliver.rauch@rauch-domain.de> I am using xsane-win32 on winxp as non privileged user. Don`t ask me the exact settings. May be it is necessary to make the user a "Main User" (in German "Hauptbenuter", I am not sure about the exact keyword for the english version). Oliver On Saturday 21 June 2003 19:59, Ken Moffat wrote: > New user, first posting, probably just brainfade, but here's my problem: > > I use xsane on linux (libranet, a debian derivative) with an Epson 1660 > scanner, and just installed xsane on WinXP on my home network. I have > sane serving from libranet, and it works well from my other linux > (debian 3.0) box. However, on WinXP I get errors about not being able to > create temp files; many errors on startup, get preview and shutdown. > This is true with unprivileged users on XP, but with a privileged user > all is working. > Does anyone have a fix? or is this just an out-of-luck on XP condition? > (I don't wish to make my teenagers privileged if I can help it! ;-) ) -- http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:Oliver.Rauch at Rauch-Domain.DE From peter at pscomp.com Sat Jun 21 23:30:49 2003 From: peter at pscomp.com (Peter Santoro) Date: Sat, 21 Jun 2003 18:30:49 -0400 Subject: [sane-devel] scanimage and scanadf command line args In-Reply-To: References: Message-ID: <3EF4DC99.9040503@pscomp.com> m. allan noah wrote: >the options you are discussing are backend specific. > >with no scanner attached to the machine, if you run scanimage --help and >scanadf --help, you will see nothing about scanning options, only input >and output file, and file format. > >the threshold and paper size options are provided by the scanner backend, >so if they malfunction, it is probably my fujitsu 4120 code :) > >the fact that one of them works, but is hidden, perhaps is because that >option is set to SANE_CAP_ADVANCED, which hides it from most users (try >using xsane, you will see the advanced option in menu, iirc). > >allan > >On Fri, 20 Jun 2003, Peter Santoro wrote: > > > >>My application makes use of scanimage and scanadf (sane 1.0.12 backend and 1.0.11 frontend) and it appears that there >>are a few inconsistencies with respect to the command line args of these sane front-ends. >> >>For instance, when using my fujitsu fi-4120c, "scanadf --help" shows that there is a "--paper_size" option available. >>Actually, it needs to be entered as "paper_size". Also, there is no "--threshold" option listed on the help screen, but >> it can be entered and it does appear to work correctly. There are other apparent inconsistencies I've run across >>using scanimage, but I don't remember them now. >> >>None of these issues are a big deal, but I was wondering if I was missing something here. >> >>Thanks for your help, >> >>Peter >> >>_______________________________________________ >>Sane-devel mailing list >>Sane-devel at www.mostang.com >>http://www.mostang.com/mailman/listinfo/sane-devel >> >> >> > > > Thanks again, Allan. I appreciate your patience for those of us who are new to the sane code base. Peter From henning at meier-geinitz.de Sat Jun 21 23:36:13 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 22 Jun 2003 00:36:13 +0200 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621160434.54189.qmail@web41502.mail.yahoo.com> References: <20030621125741.GD9347@meier-geinitz.de> <20030621160434.54189.qmail@web41502.mail.yahoo.com> Message-ID: <20030621223613.GE9347@meier-geinitz.de> Hi, On Sat, Jun 21, 2003 at 09:04:34AM -0700, Brian D. Williams wrote: > Thanks for having a look at that. Could I remove the offending define(s)? It's not a problem of an offending define. liblib.a uses _getopt internally. libm (?) also uses _getopt. Usually that's not a problem but your system tools (linker) don't seem too like it for some reason. Bye, Henning From henning at meier-geinitz.de Sat Jun 21 23:45:20 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 22 Jun 2003 00:45:20 +0200 Subject: [sane-devel] scanimage and scanadf command line args In-Reply-To: <3EF3A0C9.1090907@pscomp.com> References: <3EF3A0C9.1090907@pscomp.com> Message-ID: <20030621224520.GF9347@meier-geinitz.de> Hi, On Fri, Jun 20, 2003 at 08:03:21PM -0400, Peter Santoro wrote: > My application makes use of scanimage and scanadf (sane 1.0.12 backend and > 1.0.11 frontend) and it appears that there are a few inconsistencies with > respect to the command line args of these sane front-ends. Does scanadf do anything for you that scanimage can't? scanadf is a spin-off of scanimage but scanimage had some improvements after that. So there may be some differences. > For instance, when using my fujitsu fi-4120c, "scanadf --help" shows that > there is a "--paper_size" option available. Actually, it needs to be > entered as "paper_size". I think that's a bug in the fujitsu backend. The SANE standard says: "The option name must consist of lower-case ASCII letters (a--z), digits (0--9), or the dash character (-) only." So the underscaore "_" is not allowed. > Also, there is no "--threshold" option listed on > the help screen, but it can be entered and it does appear to work > correctly. There is an option called "threshold_curve" in the current fujitsu backend. The same comment about the "_" applies. However, I'm not sure if this does influence the handling of scanimage/scanadf. > There are other apparent inconsistencies I've run across using > scanimage, but I don't remember them now. When you come across them again, please show them to us. Bye, Henning From jonesrf1 at qwest.net Sun Jun 22 01:13:04 2003 From: jonesrf1 at qwest.net (Randolph Jones) Date: Sat, 21 Jun 2003 17:13:04 -0700 Subject: [sane-devel] page orientation for adfHow do I set my scanner Message-ID: <3EF4F490.5080109@qwest.net> how do i set my SP15c adf to scan from the bottom of the page? The default requires me to put tje page in face down and head in. If the stack has been stapled the edges are damaged. Scanning from the bottom would vaoid this problem, but I will get a mass of upside down images. TIA rfjones From horst.schlonz at gmx.de Sun Jun 22 02:56:10 2003 From: horst.schlonz at gmx.de (horst.schlonz at gmx.de) Date: Sun, 22 Jun 2003 03:56:10 +0200 Subject: [sane-devel] mustek scanexpress 6000 p does not work anymore In-Reply-To: <20030621220446.1e6eec09.jochen@penguin-breeder.org> References: <200306211814.24072.horst.schlonz@gmx.de> <20030621220446.1e6eec09.jochen@penguin-breeder.org> Message-ID: <200306220356.10480.horst.schlonz@gmx.de> Am Samstag, 21. Juni 2003 22:04 schrieben Sie: > > # cat /usr/local/etc/sane.d/dll.conf > > mustek_pp > > > > # cat /usr/local/etc/sane.d/mustek_pp.conf > > option io-mode alt_lock > > option niceload > > port 0x378 > > name SE-6000P > > vendor Mustek > > option wait-lamp 15 > > > > # SANE_DEBUG_MUSTEK_PP=128 scanimage -L > > do you still have the old libraries installed? from that output, the > mustek_pp backend isn't even loaded. > > make sure there is no other conflicting version of sane on your system. > you can also try SANE_DEBUG_DLL=128 to see what the dll backend does. you were right, i uninstalled all sane-packages but i surveyed the libsane-package. now i have uninstalled all saneish packages plus my manually compiled sane and installed sane 1.0.7 and libsane 1.0.7 from debain stable (i am on unstable). the scanner now works. thank you. you saved my ass. From pjh at coastal.net.au Sun Jun 22 09:01:48 2003 From: pjh at coastal.net.au (Peter Howard) Date: 22 Jun 2003 18:01:48 +1000 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030621125741.GD9347@meier-geinitz.de> References: <20030621094705.GB9347@meier-geinitz.de> <20030621121308.13540.qmail@web41502.mail.yahoo.com> <20030621125741.GD9347@meier-geinitz.de> Message-ID: <1056268909.1528.0.camel@pig> On Sat, 2003-06-21 at 22:57, Henning Meier-Geinitz wrote: > Yeah, that's the already known multiple definition error. Some MacOS X > users don't seem to get that error, some see it. No idea why. > And, by the way, I have no idea why libm should define _getopt. > As covered earlier in this thread, updating to the December 02 Developer Tools fixed the problem for me. Note, the interim update (IIRC October) still had the problem. PJH From adeuring at gmx.net Sun Jun 22 13:00:02 2003 From: adeuring at gmx.net (abel deuring) Date: Sun, 22 Jun 2003 14:00:02 +0200 Subject: [sane-devel] page orientation for adfHow do I set my scanner In-Reply-To: <3EF4F490.5080109@qwest.net> References: <3EF4F490.5080109@qwest.net> Message-ID: <3EF59A42.2040002@gmx.net> Randolph Jones schrieb: > how do i set my SP15c adf to scan from the bottom of the page? > The default requires me to put tje page in face down and head in. > If the stack has been stapled the edges are damaged. > Scanning from the bottom would vaoid this problem, but I will get a mass > of upside down images. AFAIK, scanimage and scanadf don't have options to rotate the resulting image. But you can Imagemagick or some PNM tools to rotate, mirror or otherwise modify the image files produced by scanimage / scanadf. Abel From nakal at web.de Sun Jun 22 14:52:07 2003 From: nakal at web.de (Nakal) Date: Sun, 22 Jun 2003 15:52:07 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <20030621125253.GC9347@meier-geinitz.de> References: <200306102317.58064.nakal@web.de> <3EF357AE.4090104@gmx.net> <20030621125253.GC9347@meier-geinitz.de> Message-ID: <200306221552.07583.nakal@web.de> On Saturday 21 June 2003 14:52, Henning Meier-Geinitz wrote: > If I try to use the "ncr" driver instead of "sym", FreeBSD doesn't > even boot. With a Tekram 315 controller the results are the same as > above. ncr driver is old, you should not use it. As far as I know, sym should support everything which ncr supported earlier. Compare the manpages sym(4) and ncr(4). > So your patch is ok but FreeBSD 5.0 is unusable with older Mustek > scanners on at least these controllers. The scanners work just fine > on Linux. Please use 5.1 instead. > If I remember correctly, the old scanners worked once with FreeBSD. > So maybe 5.0 has broken the SCSI system? On 5.1 it's working fine. I can scan for all backends (scanimage -L). On FreeBSD 4.8 "scanimage -L" is freezing my PC. FreeBSD 5.1 is lots better, in my opinion. The patch works for both FreeBSD 4.8 (aka stable) and FreeBSD 5.1 (aka current). Martin From maddog at mir.com Sun Jun 22 17:39:13 2003 From: maddog at mir.com (Matto Marjanovic) Date: Sun, 22 Jun 2003 12:39:13 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF46C3F.A897D7C4@satzbau-gmbh.de> (message from abel deuring on Sat, 21 Jun 2003 16:31:27 +0200) References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> <3EF46C3F.A897D7C4@satzbau-gmbh.de> Message-ID: <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> Hi, Abel, >are you sure that the Linux SCSI system (or FreeBSD) tries to issue a >REQUEST SENSE, if it can't "connect" to device? (If I find enough time, I'm not exactly sure what is going on in this particular situation. Last winter, a user (Shawn Rutledge) was really helpful in tracking down lost sense codes. The backend sense handler was getting called with all zeros, as here. By slogging through debug output from the driver for the SCSI card in the kernel logs, it was apparent that the REQUEST SENSE was indeed issued. I then dug into the mid-level scsi driver and found at least one place where the results were being thrown away. The moral to the story is that I don't trust the error codes returned by the Linux SCSI system --- since it thinks that the results of the REQUEST SENSE are invalid, it decides that there must be some other problem. The trigger for this behavior is the peculiar sense codes from Microtek scanners. -matt m. From onymouse at garlic.com Sun Jun 22 19:24:12 2003 From: onymouse at garlic.com (jd) Date: Sun, 22 Jun 2003 11:24:12 -0700 Subject: [sane-devel] HP Scanjet 3P io errors Message-ID: <3EF5F44C.4020506@garlic.com> I found nothing related in the archives: Using sane front & back ends v1.0.7 Device is Scanjet 3P and ADF, model 2570A, firmware 3430. Connected to Buslogic BT946C. sane does not seem to like my scanner. It returns io device errors. Works fine with epson scanner. Using RedHat 7.3, latest & lastest updates. From dmesg: SCSI subsystem driver Revision: 1.00 kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2 PCI: Found IRQ 11 for device 00:09.0 PCI: Sharing IRQ 11 with 00:0e.0 scsi: ***** BusLogic SCSI Driver Version 2.1.15 of 17 August 1998 ***** scsi: Copyright 1995-1998 by Leonard N. Zubkoff scsi0: Configuring BusLogic Model BT-946C PCI SCSI Host Adapter scsi0: Firmware Version: 4.28D, I/O Address: 0xA800, IRQ Channel: 11/Level scsi0: PCI Bus: 0, Device: 9, Address: Unassigned, Host Adapter SCSI ID: 7 scsi0: Parity Checking: Enabled, Extended Translation: Disabled scsi0: Synchronous Negotiation: Fast, Wide Negotiation: Disabled scsi0: Disconnect/Reconnect: Enabled, Tagged Queuing: Enabled scsi0: Scatter/Gather Limit: 128 of 8192 segments, Mailboxes: 211 scsi0: Driver Queue Depth: 211, Host Adapter Queue Depth: 100 scsi0: Tagged Queue Depth: Automatic, Untagged Queue Depth: 3 scsi0: Error Recovery Strategy: Default, SCSI Bus Reset: Enabled scsi0: SCSI Bus Termination: Enabled scsi0: *** BusLogic BT-946C Initialized Successfully *** scsi0 : BusLogic BT-946C Vendor: HP Model: C2570A Rev: 3430 Type: Processor ANSI SCSI revision: 02 scsi0: Target 0: Queue Depth 3, Asynchronous (Manually insmod'd scsi_hostadapter later. But it makes no difference whether it is loaded or not.) sane-find-scanner detects the device at /dev/sg0 sane -d hp:/dev/sg0 *(any command or option) returns "Error during device I/O" and the help page. THis occurs with or without option dumb-read From /etc/sane.d/hp.conf: (RedHat's default location) scsi hp option dumb-read /dev/sg0 From another form of hp.conf: scsi HP C2570A Processor 0 00 00 00 option connect-scsi option dumb-read hptool's hpinq returns the model number and firmware code but then returns nothing but io errors on stderr and "error in inquiry" for each command. This scanner works with windoze. I have no idea what is going on. Does anyone? Thanks... From brian_d_w at yahoo.com Sun Jun 22 20:59:38 2003 From: brian_d_w at yahoo.com (Brian D. Williams) Date: Sun, 22 Jun 2003 12:59:38 -0700 (PDT) Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <1056268909.1528.0.camel@pig> Message-ID: <20030622195938.38334.qmail@web41506.mail.yahoo.com> After getting the latest tools (dec2002) and getting the CVS versions of everything (sane, snapscan, libusb) it compiles. But it looks like I am stuck where everyone else has been getting stuck. Sane-find-scanner sees the scanner but I can't get scanimage to find it. I think that this is becoming not worth the effort. Has anyone gotten the epson perfection 660 and sane to work with os x? Thanks for the help everyone. Brian --- Peter Howard wrote: > On Sat, 2003-06-21 at 22:57, Henning Meier-Geinitz wrote: > > > Yeah, that's the already known multiple definition error. Some MacOS X > > users don't seem to get that error, some see it. No idea why. > > And, by the way, I have no idea why libm should define _getopt. > > > As covered earlier in this thread, updating to the December 02 Developer > Tools fixed the problem for me. Note, the interim update (IIRC October) > still had the problem. > > PJH > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel ===== Brian Williams homepage == From anoah at pfeiffer.edu Sun Jun 22 21:19:57 2003 From: anoah at pfeiffer.edu (m. allan noah) Date: Sun, 22 Jun 2003 16:19:57 -0400 (EDT) Subject: [sane-devel] page orientation for adfHow do I set my scanner In-Reply-To: <3EF4F490.5080109@qwest.net> Message-ID: you cant. use convert (part of ImageMagick) to '-flip -flop' or '-rotate 180' the images after you scan. allan On Sat, 21 Jun 2003, Randolph Jones wrote: > how do i set my SP15c adf to scan from the bottom of the page? > The default requires me to put tje page in face down and head in. > If the stack has been stapled the edges are damaged. > Scanning from the bottom would vaoid this problem, but I will get a mass > of upside down images. > > TIA > rfjones > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From adeuring at gmx.net Sun Jun 22 21:25:13 2003 From: adeuring at gmx.net (abel deuring) Date: Sun, 22 Jun 2003 22:25:13 +0200 Subject: [sane-devel] HP Scanjet 3P io errors In-Reply-To: <3EF5F44C.4020506@garlic.com> References: <3EF5F44C.4020506@garlic.com> Message-ID: <3EF610A9.4080206@gmx.net> jd wrote: > I found nothing related in the archives: It' s a bit difficult to find ;) I needed a few minutes to search through my private mail archive to find the the answer. > > Using sane front & back ends v1.0.7 > > Device is Scanjet 3P and ADF, model 2570A, firmware 3430. > Connected to Buslogic BT946C. > > sane does not seem to like my scanner. It returns io device errors. > Works fine with epson scanner. In short: The combination Buslogic driver/Linux kernel 2.4/HP scanner does not work well. The longer explanation: For certain commands, the HP backend cannot predict the exact size of a data block returned for a certain SCSI command. If the scanner return less or more data than "declared" by the backend, the Buslogic driver raises an error and does not return any data. This data underrun/overrun is not an issue for most other scanners -- in general, the Sane backends can precisely predict the length of tha sent to/received from the scanner. The short conclusion: Use another SCSI adapter for the HP scanner. The longer conclusion: The Buslogic driver would need a new maintainer, who can continue the work of the late Leonard Zubkoff. Abel From Oliver.Schwartz at gmx.de Sun Jun 22 22:00:38 2003 From: Oliver.Schwartz at gmx.de (Oliver Schwartz) Date: Sun, 22 Jun 2003 23:00:38 +0200 Subject: [sane-devel] Epson perfection 660 ->Problem building on OSX In-Reply-To: <20030622195938.38334.qmail@web41506.mail.yahoo.com> References: <20030622195938.38334.qmail@web41506.mail.yahoo.com> Message-ID: <200306222300.40706.Oliver.Schwartz@gmx.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > After getting the latest tools (dec2002) and getting the CVS > versions of everything (sane, snapscan, libusb) it compiles. But it > looks like I am stuck where everyone else has been getting stuck. > Sane-find-scanner sees the scanner but I can't get scanimage to > find it. I think that this is becoming not worth the effort. Has > anyone gotten the epson perfection 660 and sane to work with os x? Please send me the output of "SANE_DEBUG_SNAPSCAN=255 scanimage -L". Btw, the snapscan version in the SANE CVS archive is the most recent version. There's no need to upgrade the snapscan backend from Sourceforge anymore. - -Oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE+9hj2/V6sbrmfIuMRAtKaAJ9T6SSaR7ESgOT+9pwvEKtU1241VQCeKtUc 2lqzYdNhNaACZvI1appYWKU= =z0WI -----END PGP SIGNATURE----- From adeuring at gmx.net Sun Jun 22 23:50:56 2003 From: adeuring at gmx.net (abel deuring) Date: Mon, 23 Jun 2003 00:50:56 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> <3EF46C3F.A897D7C4@satzbau-gmbh.de> <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF632D0.7090102@gmx.net> Matt, > >are you sure that the Linux SCSI system (or FreeBSD) tries to issue a > >REQUEST SENSE, if it can't "connect" to device? (If I find enough time, > > I'm not exactly sure what is going on in this particular situation. > > Last winter, a user (Shawn Rutledge) was really helpful in tracking > down lost sense codes. The backend sense handler was getting called with > all zeros, as here. By slogging through debug output from the driver for > the SCSI card in the kernel logs, it was apparent that the REQUEST SENSE > was indeed issued. I then dug into the mid-level scsi driver and found > at least one place where the results were being thrown away. > > The moral to the story is that I don't trust the error codes returned by > the Linux SCSI system --- since it thinks that the results of the REQUEST > SENSE are invalid, it decides that there must be some other problem. > The trigger for this behavior is the peculiar sense codes from Microtek > scanners. OK, so we have indeed a flaw in the Linux SCSI system... I assume that the scanners identify themselves as SCSI 1 devices, where these short sense data blocks are normal. Did you try to issue REQUEST SENSE explicitly from the backend, where this looks reasonable? This may not work with every Linux adapter driver (IIRC, older versions of the aha152x driver did not like user land REQUEST SENSE commands), so it should be possible to turn them off with an option. cheers Abel From technomage-hawke at cox.net Mon Jun 23 05:24:16 2003 From: technomage-hawke at cox.net (technomage) Date: Sun, 22 Jun 2003 21:24:16 -0700 Subject: [sane-devel] any scanner drivers that will work with twian compliant digital cams? Message-ID: <200306222124.19391.technomage-hawke@cox.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 here's my rub, I have a vivtar brand vivcam-10. it has a usb port and works in windows (but I don;t have adaptive technology IN WINDOWS). I'd like to be able to use this device in sane. anyone know of a driver that will work for it? Mage - -- I will not be pushed, filed, stamped, indexed, briefed, debriefed, or numbered! My life is my own - No. 6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+9oDxn/usgigAaLcRArsBAJ9cXpAzFbXKRO9jkT0DPpwesgkFeACfS8Oq Nk06PmhTjL7h8ontQtw63Vw= =NJz1 -----END PGP SIGNATURE----- From maddog at mir.com Mon Jun 23 08:30:07 2003 From: maddog at mir.com (Matto Marjanovic) Date: Mon, 23 Jun 2003 03:30:07 -0400 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II In-Reply-To: <3EF632D0.7090102@gmx.net> (message from abel deuring on Mon, 23 Jun 2003 00:50:56 +0200) References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> <3EF46C3F.A897D7C4@satzbau-gmbh.de> <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> <3EF632D0.7090102@gmx.net> Message-ID: <1191-Mon23Jun2003033007-0400-maddog@yoo-hoo.ai.mit.edu> >OK, so we have indeed a flaw in the Linux SCSI system... I assume that >the scanners identify themselves as SCSI 1 devices, where these short >sense data blocks are normal. They do identify themselves, as a protocol between SCSI-1 and SCSI-2. ("SCSI_1_CCS" in drivers/scsi/scsi.h. This macro is used nowhere else in the Linux SCSI code.) >Did you try to issue REQUEST SENSE explicitly from the backend, where >this looks reasonable? This may not work with every Linux adapter driver Hmm, I never thought of that. (For the longest time, I figured the drivers would eventually get fixed; they haven't.) I'll give it a try. I don't suppose that a REQUEST SENSE can be issued by the sense handler itself? >(IIRC, older versions of the aha152x driver did not like user land >REQUEST SENSE commands), so it should be possible to turn them off with >an option. Heh --- if it's not one Linux SCSI bug, it is another. -matt m. From a.deuring at satzbau-gmbh.de Mon Jun 23 10:26:03 2003 From: a.deuring at satzbau-gmbh.de (abel deuring) Date: Mon, 23 Jun 2003 11:26:03 +0200 Subject: [sane-devel] FreeBSD and Microtek Scanmaker II References: <200306102317.58064.nakal@web.de> <20030619212211.GP12579@meier-geinitz.de> <3EF357AE.4090104@gmx.net> <200306210131.54270.nakal@web.de> <3EF3A2EF.9020503@gmx.net> <1191-Fri20Jun2003211339-0400-maddog@yoo-hoo.ai.mit.edu> <3EF44BDE.4B306A98@satzbau-gmbh.de> <1191-Sat21Jun2003085358-0400-maddog@yoo-hoo.ai.mit.edu> <3EF46C3F.A897D7C4@satzbau-gmbh.de> <1191-Sun22Jun2003123913-0400-maddog@yoo-hoo.ai.mit.edu> <3EF632D0.7090102@gmx.net> <1191-Mon23Jun2003033007-0400-maddog@yoo-hoo.ai.mit.edu> Message-ID: <3EF6C7AB.BCA46837@satzbau-gmbh.de> Matto Marjanovic wrote: > > >OK, so we have indeed a flaw in the Linux SCSI system... I assume that > >the scanners identify themselves as SCSI 1 devices, where these short > >sense data blocks are normal. > > They do identify themselves, as a protocol between SCSI-1 and SCSI-2. > ("SCSI_1_CCS" in drivers/scsi/scsi.h. This macro is used nowhere else > in the Linux SCSI code.) > > >Did you try to issue REQUEST SENSE explicitly from the backend, where > >this looks reasonable? This may not work with every Linux adapter driver > > Hmm, I never thought of that. (For the longest time, I figured the drivers > would eventually get fixed; they haven't.) I'll give it a try. > > I don't suppose that a REQUEST SENSE can be issued by the sense handler > itself? That would be a bit risky, I think. The problem is the Linux part of sanei_scsi.c. It supports command queueing, and without a careful review, how the command queue management works, I would recommend not to try a REQUEST SENSE from the sense handler itself. Abel From mrjaneway at gmx.net Mon Jun 23 10:22:47 2003 From: mrjaneway at gmx.net (mrjaneway at gmx.net) Date: Mon, 23 Jun 2003 11:22:47 +0200 (MEST) Subject: [sane-devel] Re: Sane support for Acer parallel port scanners References: <2263.1056009537@www36.gmx.net> Message-ID: <11756.1056360167@www59.gmx.net> Thank you Oliver and Henning for your replies regarding my problem! I think I will now try to run the scanner with windows-drivers using Wine. If that doesnt work, I will simply buy a new, Linux-compatible scanner - since they dont cost that much. I dont know how to write a backend - so thanks to all of you who can do it and who make it possible for the rest of all Linux Useres to use their scanners! Greetings, Tobias From henning at meier-geinitz.de Mon Jun 23 17:55:32 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 23 Jun 2003 18:55:32 +0200 Subject: [sane-devel] any scanner drivers that will work with twian compliant digital cams? In-Reply-To: <200306222124.19391.technomage-hawke@cox.net> References: <200306222124.19391.technomage-hawke@cox.net> Message-ID: <20030623165532.GA775@meier-geinitz.de> Hi, On Sun, Jun 22, 2003 at 09:24:16PM -0700, technomage wrote: > I have a vivtar brand vivcam-10. To answer the question in the subject: There is no such thing a a TWAIN-compliant camera o scanner. Only the scan applications are TWAIN-compatible. So beeing TWAIN-compatible doesn't mean anything for hardware. > it has a usb port and works in windows (but I don;t have adaptive > technology IN WINDOWS). What's "adaptive technology"? > I'd like to be able to use this device in sane. anyone know of a > driver that will work for it? As far as I know, no new SANE backends for cameras have been added during the last few years. But check our lists to be sure. However, there is the gphoto2 backend which can be used to access devices supported by gphoto2. See http://www.gphoto.org. There is also a backend for accessing video cameras supported by video4linux called v4l. Bye, Henning From TomF at sjpc.org Mon Jun 23 18:12:51 2003 From: TomF at sjpc.org (TomF) Date: Mon, 23 Jun 2003 10:12:51 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF Message-ID: <20030623101251.48d212b6.TomF@sjpc.org> On Redhat 9.0 with all Up2date patches installed, I uninstalled sane-backends and installed sane-backends-1.0.12-1asp.i386.rpm. When I ran xsane with ADF enabled, my HP7450C scanner, which is connected via usb, fed about 5 inches of the first document into the ADF, went into Initializing mode, and hung. I reproduced the problem with export SANE_DEBUG_AVISION=7, and sent a problem report to rene.rebe at gmx.net on Fri, 20 Jun 2003. I haven't received a response yet, and Rene appears to be on vacation: no activity since June 11. Yesteroday, I uninstalled sane, xsane-0.89-3, xsane-gimp-0.89-3, sane-frontends-1.0.9-2, and kdegraphics-3.1-5, and installed sane-backends-1.0.12.tar.gz and xsane-0.91.tar.gz. I got the same behavior when I ran xsane with ADF enabled. After hanging for a long time, sometimes a device disable error message is sent to the log, sometimes not. I am wondering if there is a SCSI/USB conflict. The usb/scsi emulation is supposed to be obsolete, but I found the following on my system: /var/log/messages shows kernel: Attached scsi generic sg5 at scsi1, channel 0, id 0, lun 0, type 6, during system startup. The Hardware Browser lists the scanner as sg5. /proc/bus/usb/devices contains: 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=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0801 Rev= 0.01 S: Manufacturer=hp S: Product=hp scanjet 7400c S: SerialNumber=87 tem 7400c I have been unable to determine precisely what is wrong with my configuration. Where should I look for the way to properly configure my scanner? From alan.purchase at paradise.net.nz Mon Jun 23 22:22:04 2003 From: alan.purchase at paradise.net.nz (Alan Purchase) Date: 24 Jun 2003 09:22:04 +1200 Subject: [sane-devel] Microtek Scanmaker 6700 (USB and FireWire) Message-ID: <1056403325.2759.8.camel@localhost.localdomain> Henning, FYI my PC has 2 USB ports, one is connected to an Epson printer and the other to a 4-port hub which in turn is connected to a Webcam, the Microtech Scanner, and my digital camera. I use the other hub port in Windows to connect to my wife's laptop using FastLynx. Here are the results of the cat /proc/bus/usb/devices that you asked for: T: Bus=02 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=d000 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=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 11/900 us ( 1%), #Int= 1, #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=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=07(print) Sub=01 Prot=02 MxPS=64 #Cfgs= 1 P: Vendor=04b8 ProdID=0001 Rev= 1.00 S: Manufacturer=EPSON S: Product=USB Printer C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 2 Cls=07(print) Sub=01 Prot=02 Driver=usblp E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#= 3 Spd=12 MxCh= 4 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0451 ProdID=1446 Rev= 1.10 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=ff(vend.) Sub=03 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=05da ProdID=20c9 Rev= 0.00 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms T: Bus=01 Lev=02 Prnt=03 Port=02 Cnt=02 Dev#= 5 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=067b ProdID=0000 Rev= 0.00 S: Manufacturer=Prolific Technology Inc. C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbnet E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=1ms E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=02 Prnt=03 Port=03 Cnt=03 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=046d ProdID=08b0 Rev= 0.02 S: SerialNumber=01402100A5000000 C:* #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 0 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 196 Ivl=1ms I: If#= 0 Alt= 2 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 292 Ivl=1ms I: If#= 0 Alt= 3 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 448 Ivl=1ms I: If#= 0 Alt= 4 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 592 Ivl=1ms I: If#= 0 Alt= 5 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 704 Ivl=1ms I: If#= 0 Alt= 6 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 776 Ivl=1ms I: If#= 0 Alt= 7 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 840 Ivl=1ms I: If#= 0 Alt= 8 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 896 Ivl=1ms I: If#= 0 Alt= 9 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 960 Ivl=1ms I: If#= 0 Alt=10 #EPs= 2 Cls=0a(data ) Sub=ff Prot=00 Driver=Philips webcam E: Ad=82(I) Atr=03(Int.) MxPS= 1 Ivl=100ms E: Ad=85(I) Atr=01(Isoc) MxPS= 960 Ivl=1ms I: If#= 1 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=(none) I: If#= 2 Alt= 0 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms I: If#= 2 Alt= 1 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 90 Ivl=1ms I: If#= 2 Alt= 2 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 46 Ivl=1ms I: If#= 2 Alt= 3 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms I: If#= 2 Alt= 4 #EPs= 1 Cls=01(audio) Sub=02 Prot=00 Driver=(none) E: Ad=84(I) Atr=01(Isoc) MxPS= 16 Ivl=1ms I hope that all means something. Cheers, Alan. -- ______________________________________________________________________ Alan Purchase IT Consultant Tel: +64 9 817 3101 113 Victory Road Mobile: +64 21 925 028 Laingholm E-mail: alan.purchase at paradise.co.nz Auckland 1007 New Zealand ______________________________________________________________________ From psfales at lucent.com Tue Jun 24 02:14:11 2003 From: psfales at lucent.com (Peter Fales) Date: Mon, 23 Jun 2003 20:14:11 -0500 Subject: [sane-devel] any scanner drivers that will work with twian compliant digital cams? In-Reply-To: <20030623165532.GA775@meier-geinitz.de> References: <200306222124.19391.technomage-hawke@cox.net> <20030623165532.GA775@meier-geinitz.de> Message-ID: <20030624011411.GA15896@lucent.com> On Mon, Jun 23, 2003 at 06:55:32PM +0200, Henning Meier-Geinitz wrote: > However, there is the gphoto2 backend which can be used to access > devices supported by gphoto2. See http://www.gphoto.org. Unfortunately, there are no Vivatar cameras supported by gphoto2. A quick google search shows a number of people lamenting the lack of Linux support for Vivitar cameras. -- Peter Fales From ope557 at yahoo.com Tue Jun 24 08:23:10 2003 From: ope557 at yahoo.com (ope) Date: Tue, 24 Jun 2003 00:23:10 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030618001421.34819.qmail@web20604.mail.yahoo.com> Message-ID: <20030624072310.25101.qmail@web20608.mail.yahoo.com> I have found another 'behavior' that might shed some light on the problems that I am having. When I do a preview the interface auto selects a large square area covering most of the scanner bed which I then drag/resize to the actual image I am scanning (nothing new here). What I have noticed with absolute reliability is this: 1. If, after the preview, I can see the entire outline of the selection box then the subsequent scan will work. 2. However, If I can't see the entire selection box then the scan will not work. What I mean by this is that often times the bottom line of the selection box is 'off' the window such that I can't see any bottom line for selecting the image area only. If I put the mouse on the bottom of the frame and drag up I can select the scanning area. Does my explaination make sense? I can send screen shots if it does not. It is as if xsane thinks that the scanner bed is longer than it is. It oddly explains why the scanner lamp has completed the scan and returned but the software seems to be waiting for more data and is getting bulk_msg: timeout messages. Does anyone have any ideas? --- ope wrote: > What I see in messages are a lot of messages saying: > kernel: usb_control/bulk_msg: timeout > last message repeated 2 times > last message repeated 3 times > ... > > and after 10 minutes or so I will see: > kernel: scanner.c: read_scanner(0): excessive NAK's > received > > > --- Oliver Rauch > wrote: > > On Tuesday 17 June 2003 09:39, ope wrote: > > > > > I have also noticed another thing that is worth > > > mentioning. At one point when the xsane seemed > to > > be > > > stuck I tried unplugging the scanner from the > USB > > > port. I was expecting xsane to fail and close > > down. > > > What actually did happen was that the complete > > scanned > > > image instantly popped up in the viewer and > xsane > > was > > > running as if nothing has happened. Just for > fun > > I > > > tried it couple more times and had the same > > results > > > each time. It appears to me that that the scan > is > > > essentially complete at the point that it is > > freezing. > > > > This sounds as if there is a problem with the USB > > communication. > > > > Do you get any messages about USB problems > > in /var/log/messages ? > > > > Oliver > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel at www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > http://sbc.yahoo.com > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From henning at meier-geinitz.de Tue Jun 24 09:43:25 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 24 Jun 2003 10:43:25 +0200 Subject: [sane-devel] Microtek Scanmaker 6700 (USB and FireWire) In-Reply-To: <1056403325.2759.8.camel@localhost.localdomain> References: <1056403325.2759.8.camel@localhost.localdomain> Message-ID: <20030624084325.GB2856@meier-geinitz.de> Hi, On Tue, Jun 24, 2003 at 09:22:04AM +1200, Alan Purchase wrote: > T: Bus=01 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=ff(vend.) Sub=03 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=05da ProdID=20c9 Rev= 0.00 > C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms Thanks. I'll add that to our lists. Bye, Henning From moitinho at civil.ist.utl.pt Tue Jun 24 10:49:46 2003 From: moitinho at civil.ist.utl.pt (Jose Paulo Moitinho de Almeida) Date: Tue, 24 Jun 2003 10:49:46 +0100 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030623101251.48d212b6.TomF@sjpc.org> References: <20030623101251.48d212b6.TomF@sjpc.org> Message-ID: <200306241049.46918.moitinho@civil.ist.utl.pt> On Monday 23 June 2003 18:12, TomF wrote: > On Redhat 9.0 with all Up2date patches installed, I uninstalled > sane-backends and installed sane-backends-1.0.12-1asp.i386.rpm. When I > ran xsane with ADF enabled, my HP7450C scanner, which is connected > via usb, fed about 5 inches of the first document into the ADF, went > into Initializing mode, and hung. I reproduced the problem with export > SANE_DEBUG_AVISION=7, and sent a problem report to rene.rebe at gmx.net on > Fri, 20 Jun 2003. I haven't received a response yet, and Rene appears > to be on vacation: no activity since June 11. > > Yesteroday, I uninstalled sane, xsane-0.89-3, xsane-gimp-0.89-3, > sane-frontends-1.0.9-2, and kdegraphics-3.1-5, and installed > sane-backends-1.0.12.tar.gz and xsane-0.91.tar.gz. I got the same > behavior when I ran xsane with ADF enabled. After hanging for a long > time, sometimes a device disable error message is sent to the log, > sometimes not. > > > I am wondering if there is a SCSI/USB conflict. The usb/scsi emulation > is supposed to be obsolete, but I found the following on my system: > Without the logs it is difficult to tell. But the current version of the backend uses libusb, so (probably) the hpusbsci module is necessary for that scanner, but it may happen that when you plug the scanner the kernel loads it automatically... Please try to do an "lsmod" to check if the module is loaded and if it is do an "rmmod hpusbscsi" before trying to scan. Regards ZP From moitinho at civil.ist.utl.pt Tue Jun 24 11:42:25 2003 From: moitinho at civil.ist.utl.pt (Jose Paulo Moitinho de Almeida) Date: Tue, 24 Jun 2003 11:42:25 +0100 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <200306241049.46918.moitinho@civil.ist.utl.pt> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> Message-ID: <200306241142.25425.moitinho@civil.ist.utl.pt> On Tuesday 24 June 2003 10:49, Jose Paulo Moitinho de Almeida wrote: > On Monday 23 June 2003 18:12, TomF wrote: >..... > > Without the logs it is difficult to tell. But the current version of the > backend uses libusb, so (probably) the hpusbsci module is necessary for > that scanner, but it may happen that when you plug the scanner the kernel > loads it automatically... > Sorry! I meant "... the hpusbscsi module is NOT necessary ..." ZP From sigurd.stordal at stud.ibg.uit.no Tue Jun 24 14:56:46 2003 From: sigurd.stordal at stud.ibg.uit.no (Sigurd Stordal) Date: Tue, 24 Jun 2003 15:56:46 +0200 Subject: [sane-devel] Problems with the canon backend for a canoscan 2700F. Message-ID: <200306241556.48630.sigurd.stordal@stud.ibg.uit.no> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It will take a preview without problem, but when I choose scan in xsane, I get a "failed to start scanner: invalid argument", error. I get the same error when trying xscanimage. Xsane 0.90, xscanimage 1.0.9. Sane-backends 1.0.12. Had previous problems with backend 1.0.10, giving strange colours in the scanner, this has been fixed no, but no there is this error. could it be a scsi problem. - -- Sigurd Stordal President of GOGS Experimental Petrologist -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE++FifSB4UOs/snOURAu88AJ9q3g9P1YUfpGr3T/Py4mKw4PvYqACdGOko IbC+oGNz6UJ2/74nsSSFH/w= =/dfh -----END PGP SIGNATURE----- From ukd at xenon.pc.Uni-Koeln.DE Tue Jun 24 16:48:29 2003 From: ukd at xenon.pc.Uni-Koeln.DE (Ulrich Deiters) Date: Tue, 24 Jun 2003 17:48:29 +0200 (METDST) Subject: [sane-devel] Problems with the Canoscan 2700F Message-ID: <200306241548.RAA29561@xenon.pc.Uni-Koeln.DE> Could you let me have a debug printout (after setting SANE_DEBUG_CANON=255), so that I can locate the problem? Regards, Ulrich Deiters From TomF at sjpc.org Tue Jun 24 18:40:15 2003 From: TomF at sjpc.org (TomF) Date: Tue, 24 Jun 2003 10:40:15 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <200306241049.46918.moitinho@civil.ist.utl.pt> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> Message-ID: <20030624104015.7b00f168.TomF@sjpc.org> On Tue, 24 Jun 2003 10:49:46 +0100 Jose Paulo Moitinho de Almeida wrote: > On Monday 23 June 2003 18:12, TomF wrote: ... > > I got the same > > behavior when I ran xsane with ADF enabled. After hanging for a > > long time, sometimes a device disable error message is sent to the > > log, sometimes not. ... > it may happen that when you plug the > scanner the kernel loads it automatically... > > Please try to do an "lsmod" to check if the module is loaded and if it > is do an "rmmod hpusbscsi" before trying to scan. > Thanks. I think I'm closer, but now my scanner is not recognized. hpusbscsi was loaded. I removed it, and checked the hardware browser. The entry for the Scanner was removed. To make sure hpusbscsi didn't get loaded on the next reboot, I renamed hpusbscsi.o. Then I rebooted to determine if the scanner would be detected as a usb device. The hardware browser still showed no browser, and xsane found no scanner device on startup. How can I get the scanner recognized as a USB device? From henning at meier-geinitz.de Tue Jun 24 18:42:24 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 24 Jun 2003 19:42:24 +0200 Subject: [sane-devel] Problems with the canon backend for a canoscan 2700F. In-Reply-To: <200306241556.48630.sigurd.stordal@stud.ibg.uit.no> References: <200306241556.48630.sigurd.stordal@stud.ibg.uit.no> Message-ID: <20030624174224.GB7697@meier-geinitz.de> Hi, On Tue, Jun 24, 2003 at 03:56:46PM +0200, Sigurd Stordal wrote: > It will take a preview without problem, but when I choose scan in xsane, I get > a "failed to start scanner: invalid argument", error. I get the same error > when trying xscanimage. Xsane 0.90, xscanimage 1.0.9. Sane-backends 1.0.12. > Had previous problems with backend 1.0.10, giving strange colours in the > scanner, this has been fixed no, but no there is this error. could it be a > scsi problem. I'm not a Canon expert, the canon backend maintainer may know more details. But nevertheless some general hints: * Make sure that you don't mix top-left and bottom-right coordinates. I don't know if that's possible with this frontend/backend combination but you never know. When you select what to scan, start with the top-left edge * The difference between preview and actual scan is usually only the resolution and sometimes scan mode. So try some differnt resolutions and modes (if the backend supports that). * Does scanimage show the same behaviour? E.g. try "scanimage >image.pnm". * You can enable debugging like this: SANE_DEBUG_CANON=255 xsane 2>logfile (and now scan an image and show us the logfile) * If it's a SCSI problem, the SCSI adapter and kernel version you use may be of interest Bye, Henning From oliver.rauch at rauch-domain.de Tue Jun 24 20:21:53 2003 From: oliver.rauch at rauch-domain.de (Oliver Rauch) Date: Tue, 24 Jun 2003 21:21:53 +0200 Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <20030624072310.25101.qmail@web20608.mail.yahoo.com> References: <20030624072310.25101.qmail@web20608.mail.yahoo.com> Message-ID: <200306242121.53495.oliver.rauch@rauch-domain.de> I suggest at first you disable the autmatic scanarea selection in the preferences of xsane. I will take a look at it. Oliver On Tuesday 24 June 2003 09:23, ope wrote: > I have found another 'behavior' that might shed some > light on the problems that I am having. When I do a > preview the interface auto selects a large square area > covering most of the scanner bed which I then > drag/resize to the actual image I am scanning (nothing > new here). What I have noticed with absolute > reliability is this: > > 1. If, after the preview, I can see the entire > outline of the selection box then the subsequent scan > will work. > > 2. However, If I can't see the entire selection box > then the scan will not work. What I mean by this is > that often times the bottom line of the selection box > is 'off' the window such that I can't see any bottom > line for selecting the image area only. If I put the > mouse on the bottom of the frame and drag up I can > select the scanning area. > > Does my explaination make sense? I can send screen > shots if it does not. > > It is as if xsane thinks that the scanner bed is > longer than it is. It oddly explains why the scanner > lamp has completed the scan and returned but the > software seems to be waiting for more data and is > getting bulk_msg: timeout messages. > > Does anyone have any ideas? > > --- ope wrote: > > What I see in messages are a lot of messages saying: > > kernel: usb_control/bulk_msg: timeout > > last message repeated 2 times > > last message repeated 3 times > > ... > > > > and after 10 minutes or so I will see: > > kernel: scanner.c: read_scanner(0): excessive NAK's > > received > > > > > > --- Oliver Rauch > > > > wrote: > > > On Tuesday 17 June 2003 09:39, ope wrote: > > > > I have also noticed another thing that is worth > > > > mentioning. At one point when the xsane seemed > > > > to > > > > > be > > > > > > > stuck I tried unplugging the scanner from the > > > > USB > > > > > > port. I was expecting xsane to fail and close > > > > > > down. > > > > > > > What actually did happen was that the complete > > > > > > scanned > > > > > > > image instantly popped up in the viewer and > > > > xsane > > > > > was > > > > > > > running as if nothing has happened. Just for > > > > fun > > > > > I > > > > > > > tried it couple more times and had the same > > > > > > results > > > > > > > each time. It appears to me that that the scan > > > > is > > > > > > essentially complete at the point that it is > > > > > > freezing. > > > > > > This sounds as if there is a problem with the USB > > > communication. > > > > > > Do you get any messages about USB problems > > > in /var/log/messages ? > > > > > > Oliver > > > _______________________________________________ > > > Sane-devel mailing list > > > Sane-devel at www.mostang.com > > > http://www.mostang.com/mailman/listinfo/sane-devel > > > > __________________________________ > > Do you Yahoo!? > > SBC Yahoo! DSL - Now only $29.95 per month! > > http://sbc.yahoo.com > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel at www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > http://sbc.yahoo.com > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel -- http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:Oliver.Rauch at Rauch-Domain.DE From henning at meier-geinitz.de Tue Jun 24 20:41:26 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 24 Jun 2003 21:41:26 +0200 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030624104015.7b00f168.TomF@sjpc.org> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> Message-ID: <20030624194126.GC7697@meier-geinitz.de> Hi, > Then I rebooted to determine if the scanner would be detected as a usb > device. The hardware browser still showed no browser, and xsane found > no scanner device on startup. > > How can I get the scanner recognized as a USB device? That's done automatically. If it's not detected as USB device by the kernel, it can't be used by hpusbscsi. Is it found by sane-find-scanner as root? Is it found by scanimage -L as root? If yes, you may need to set up permissions for libusb correctly. That's explained in man sane-usb. bye, Henning From hshane at austin.rr.com Wed Jun 25 02:42:24 2003 From: hshane at austin.rr.com (Howard Shane) Date: Tue, 24 Jun 2003 20:42:24 -0500 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP Message-ID: <3EF8FE00.3050107@austin.rr.com> ...is available for viewing at http://66.25.191.66/docs/HOWTOS/Scanner/index.html I've tried to incorporate everyone's corrections and suggestions wherever possible. For any remaining omissions or errata please let me know. Thanks! From ope557 at yahoo.com Wed Jun 25 09:05:35 2003 From: ope557 at yahoo.com (ope) Date: Wed, 25 Jun 2003 01:05:35 -0700 (PDT) Subject: [sane-devel] UMAX Astra 2200 USB weirdness In-Reply-To: <200306242121.53495.oliver.rauch@rauch-domain.de> Message-ID: <20030625080535.22628.qmail@web20604.mail.yahoo.com> Let me know if you need more detailed logs, system info or want to use my setup to test some things out. I am happy to pitch in if it will help. --- Oliver Rauch wrote: > > I suggest at first you disable the autmatic scanarea > selection > in the preferences of xsane. > > I will take a look at it. > > Oliver > > On Tuesday 24 June 2003 09:23, ope wrote: > > I have found another 'behavior' that might shed > some > > light on the problems that I am having. When I do > a > > preview the interface auto selects a large square > area > > covering most of the scanner bed which I then > > drag/resize to the actual image I am scanning > (nothing > > new here). What I have noticed with absolute > > reliability is this: > > > > 1. If, after the preview, I can see the entire > > outline of the selection box then the subsequent > scan > > will work. > > > > 2. However, If I can't see the entire selection > box > > then the scan will not work. What I mean by this > is > > that often times the bottom line of the selection > box > > is 'off' the window such that I can't see any > bottom > > line for selecting the image area only. If I put > the > > mouse on the bottom of the frame and drag up I can > > select the scanning area. > > > > Does my explaination make sense? I can send > screen > > shots if it does not. > > > > It is as if xsane thinks that the scanner bed is > > longer than it is. It oddly explains why the > scanner > > lamp has completed the scan and returned but the > > software seems to be waiting for more data and is > > getting bulk_msg: timeout messages. > > > > Does anyone have any ideas? > > > > --- ope wrote: > > > What I see in messages are a lot of messages > saying: > > > kernel: usb_control/bulk_msg: timeout > > > last message repeated 2 times > > > last message repeated 3 times > > > ... > > > > > > and after 10 minutes or so I will see: > > > kernel: scanner.c: read_scanner(0): excessive > NAK's > > > received > > > > > > > > > --- Oliver Rauch > > > > > > wrote: > > > > On Tuesday 17 June 2003 09:39, ope wrote: > > > > > I have also noticed another thing that is > worth > > > > > mentioning. At one point when the xsane > seemed > > > > > > to > > > > > > > be > > > > > > > > > stuck I tried unplugging the scanner from > the > > > > > > USB > > > > > > > > port. I was expecting xsane to fail and > close > > > > > > > > down. > > > > > > > > > What actually did happen was that the > complete > > > > > > > > scanned > > > > > > > > > image instantly popped up in the viewer and > > > > > > xsane > > > > > > > was > > > > > > > > > running as if nothing has happened. Just > for > > > > > > fun > > > > > > > I > > > > > > > > > tried it couple more times and had the same > > > > > > > > results > > > > > > > > > each time. It appears to me that that the > scan > > > > > > is > > > > > > > > essentially complete at the point that it is > > > > > > > > freezing. > > > > > > > > This sounds as if there is a problem with the > USB > > > > communication. > > > > > > > > Do you get any messages about USB problems > > > > in /var/log/messages ? > > > > > > > > Oliver > > > > > _______________________________________________ > > > > Sane-devel mailing list > > > > Sane-devel at www.mostang.com > > > > > http://www.mostang.com/mailman/listinfo/sane-devel > > > > > > __________________________________ > > > Do you Yahoo!? > > > SBC Yahoo! DSL - Now only $29.95 per month! > > > http://sbc.yahoo.com > > > _______________________________________________ > > > Sane-devel mailing list > > > Sane-devel at www.mostang.com > > > > http://www.mostang.com/mailman/listinfo/sane-devel > > > > __________________________________ > > Do you Yahoo!? > > SBC Yahoo! DSL - Now only $29.95 per month! > > http://sbc.yahoo.com > > _______________________________________________ > > Sane-devel mailing list > > Sane-devel at www.mostang.com > > http://www.mostang.com/mailman/listinfo/sane-devel > > -- > http://www.xsane.org > http://www.mostang.com/sane > http://www.rauch-domain.de > mailto:Oliver.Rauch at Rauch-Domain.DE > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From jochen.eisinger at gmx.de Wed Jun 25 09:18:10 2003 From: jochen.eisinger at gmx.de (Jochen Eisinger) Date: Wed, 25 Jun 2003 10:18:10 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EF8FE00.3050107@austin.rr.com> References: <3EF8FE00.3050107@austin.rr.com> Message-ID: <20030625101810.139be97d.jochen.eisinger@gmx.de> Hi, some remarks on the Parallel Port sections: Interface Types -> Parallel Port Devices: Jonathan's page is really very outdated for some time now. It's better (also for the other scanner types) to check the supported scanners list on sane.informatik.uni-freiburg.de/cgi-bin/driver.pl Kernel Support -> Parallel Port Scanners: Not all scanner drivers need kernel level support. Some are using directio (this needs to be enabled in configure) You're also mixing dmesg and lsmod a little (lsmod is in bold, but a dmesg output is shown). You could also note that you might have to enabled certain transfer modes in the BIOS Making and Accessing the Scanner Devices -> Manually creating ... crw------- 1 root root 99, 0 Jun 24 13:47 parport0 crw------- 1 root root 99, 1 Jun 24 13:47 parport1 crw------- 1 root root 99, 2 Jun 24 13:47 parport2 crw------- 1 root root 99, 3 Jun 24 13:47 parport3 crw-r----- 1 root root 1, 4 Jan 1 1970 port if a scanner doesn't use the kernel drivers, it normally needs the port number as device name. Making and... -> Groups and Permissions: If a scanner doesn't use the kernel drivers, you have to use the sane daemon (saned) to let non-root users access the scanner Configuring SANE: Parallel port backends often need libieee1284 installed or directio enabled. You could also stress the point a little more that an old SANE installation is the reason #1 why self compiled SANE version don't work (as you'd expect) The network setup is missing the (x)inetd setup and doesn't mention the possibility of using passwords Testing your scanner: There's an option --test for scanimage that's it :) regards -- jochen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From anoah at pfeiffer.edu Wed Jun 25 14:17:10 2003 From: anoah at pfeiffer.edu (m. allan noah) Date: Wed, 25 Jun 2003 09:17:10 -0400 (EDT) Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EF8FE00.3050107@austin.rr.com> Message-ID: it seems to me, that if you want your document to be more future-proof, you would spend some more time talking about using libusb instead of the kernel scanner driver, which is likely to be removed in later kernels (as libusb becomes more stable) until then, i would likely re-name section 3 to 'OS support' instead of kernel support, and make two usb entries, one for kernel and one for libusb. then, to keep things consistent, you would have to add a libusb section to 4.2. allan On Tue, 24 Jun 2003, Howard Shane wrote: > ...is available for viewing at > > http://66.25.191.66/docs/HOWTOS/Scanner/index.html > > I've tried to incorporate everyone's corrections and suggestions > wherever possible. For any remaining omissions or errata please let me know. > > Thanks! > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From hbs at ks.informatik.uni-kiel.de Wed Jun 25 14:16:35 2003 From: hbs at ks.informatik.uni-kiel.de (Henrik Schmidt) Date: Wed, 25 Jun 2003 15:16:35 +0200 (MEST) Subject: [sane-devel] Scsi problem with Solaris 2.6 Message-ID: I'm trying to use a Microtek ScanMaker III with Solaris 2.6 and the scg SCSI driver. I'm using sane-backends 1.0.12 with frontend 1.0.10. The scanner is detected but as soon as I start a scan or prescan either with xscanimage or xsane the application locks up. I get errors in /var/adm/messages. After 2 minutes the applications return with a timeout and i/o error. I checked the scanner on a Windows computer and it did work. I checked it on another computer with sane and it failed too. I had it running some a ago. When I moved the computer to a different location I updated sane and it failed to work afterwards. Going back to older sane backend versions (up to 1.0.8) didn't help either. I tried to contact both the microtek backend coder as well as the contact in README.solaris but got no reply. Is there any hope ? Henrik --------------------- /var/adm/messages ------------------------------- Jun 25 13:08:25 cortex unix: WARNING: /iommu at f,e0000000/sbus at f,e0001000/espdma at f ,400000/esp at f,800000 (esp0):^M^M Jun 25 13:08:25 cortex unix: data transfer overrun: current esp state: Jun 25 13:08:25 cortex unix: esp: State=DATA Last State=DATA_DONE^ M^M Jun 25 13:08:25 cortex unix: esp: Latched stat=0x91 intr=0x10 fifo 0x80^M^M Jun 25 13:08:25 cortex unix: esp: last msg out: IDENTIFY; last msg in: COMMAND COMPLETE^M^M Jun 25 13:08:25 cortex unix: esp: DMA csr=0xa4240010^M^M Jun 25 13:08:25 cortex unix: esp: addr=fc0245a0 dmacnt=0 last=fc01 55a0 last_cnt=f000^M^M Jun 25 13:08:25 cortex unix: esp: Cmd dump for Target 5 Lun 0:^M^M Jun 25 13:08:25 cortex unix: esp: cdblen=6, cdb=[ 0x8 0x0 0x0 0x0 0x91 0x0 ]^M^M Jun 25 13:08:25 cortex unix: esp: pkt_state=0xf pkt_flags=0x0 pkt_statistics=0x0^M^M Jun 25 13:08:25 cortex unix: esp: cmd_flags=0x462 cmd_timeout=110^ M^M Jun 25 13:08:25 cortex unix: handle_incomplete: 1 retry cnt: 0 Jun 25 13:08:25 cortex unix: scgintr: DONE_ERROR pkt_reason: 7 state: f resid: 0 packet resid: 126976 Jun 25 13:10:32 cortex unix: WARNING: /iommu at f,e0000000/sbus at f,e0001000/espdma at f ,400000/esp at f,800000 (esp0):^M^M Jun 25 13:10:32 cortex unix: Connected command timeout for Target 5.0 -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs at ks.informatik.uni-kiel.de From fsanta at arrakis.es Wed Jun 25 16:05:27 2003 From: fsanta at arrakis.es (fsanta) Date: Wed, 25 Jun 2003 17:05:27 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 Message-ID: <200306251705.27766.fsanta@arrakis.es> Hi everyone. After an upgrade from SuSE 8.1 to 8.2 my umax 2200 freezes the system hard after xsane preview: Here are the messages: Jun 24 12:24:24 sbs3 resmgr[748]: accepted connection from user steve Jun 24 12:24:24 sbs3 xsane: resmgr: server response code 502 Jun 24 12:24:24 sbs3 resmgr[748]: disconnect from steve Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses synchronous negotiation. Using asynchronous transfers The permissions on /dev/sg0 are global rw. I have an Adaptec 2904 (sic) card and everything was fine under 8.1. Can anyone help? Thanks, Steve. From ljm at xs4all.nl Wed Jun 25 16:19:19 2003 From: ljm at xs4all.nl (Laurent-jan) Date: Wed, 25 Jun 2003 17:19:19 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP References: <3EF8FE00.3050107@austin.rr.com> Message-ID: <3EF9BD77.20401@xs4all.nl> Howard Shane wrote: > ...is available for viewing at > > http://66.25.191.66/docs/HOWTOS/Scanner/index.html > > I've tried to incorporate everyone's corrections and suggestions > wherever possible. For any remaining omissions or errata please let me > know. > > Thanks! > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel Hi, Some remarks: 5.1: The howto-page is not mine; it has been made by Steve Sheriff. After he took it down, I got quite a few questions about the disapaered link, so I asked Steve if I could host a copy. And it's his model, not mine (allas...) 6: You put the scanimage command as: $ scanimage -d /dev/scanner0 --format pnm > outfile.pnm I remember some discussions about the -d argument. I think it should be -d backend:device, f.e. $ scanimage -d umax:/dev/sg6 --format pnm > outfile.pnm 8: Maybe we should think about a more general way of toubleshooting. Some maufacturers (f.e. of copiers) use a flowchart-like algoritm to find the actions. It would be nice if we could make somethong like that. ljm From henning at meier-geinitz.de Wed Jun 25 16:22:50 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 25 Jun 2003 17:22:50 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <200306251705.27766.fsanta@arrakis.es> References: <200306251705.27766.fsanta@arrakis.es> Message-ID: <20030625152250.GA9836@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 05:05:27PM +0200, fsanta wrote: > After an upgrade from SuSE 8.1 to 8.2 my umax 2200 freezes the system hard > after xsane preview: Here are the messages: That5 doesn't look like it's realted to SANE. Looks more like a kernel problem. > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > synchronous negotiation. Using asynchronous transfers Try disabling synchronous transfers in your SCSI driver or the BIOS (but I guess your SCSI controller doesn't have a BIOS). Bye, Henning From fsanta at arrakis.es Wed Jun 25 17:34:17 2003 From: fsanta at arrakis.es (fsanta) Date: Wed, 25 Jun 2003 18:34:17 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <20030625152250.GA9836@meier-geinitz.de> References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> Message-ID: <200306251834.17699.fsanta@arrakis.es> Hi Henning Could you tell me how to do that? the scsi card is a very basic 2904 which Oliver added to the database of usable cards way back years ago. The scsi terminator plug is missing on the scanner. Could it have anything to do with that? I can't test it as I haven't got an scsi terminator plug. We removed it under 8.1 to produce acceptable scans. It was of very poor quality with. In Spain scsi terminator plugs take a long time to get ;-) Cheers, Steve. On Wednesday 25 June 2003 17:22, Henning Meier-Geinitz wrote: > Hi, > > On Wed, Jun 25, 2003 at 05:05:27PM +0200, fsanta wrote: > > After an upgrade from SuSE 8.1 to 8.2 my umax 2200 freezes the system > > hard after xsane preview: Here are the messages: > > That5 doesn't look like it's realted to SANE. Looks more like a kernel > problem. > > > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > > synchronous negotiation. Using asynchronous transfers > > Try disabling synchronous transfers in your SCSI driver or the BIOS > (but I guess your SCSI controller doesn't have a BIOS). > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From henning at meier-geinitz.de Wed Jun 25 17:52:18 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 25 Jun 2003 18:52:18 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EF9BD77.20401@xs4all.nl> References: <3EF8FE00.3050107@austin.rr.com> <3EF9BD77.20401@xs4all.nl> Message-ID: <20030625165218.GC9836@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 05:19:19PM +0200, Laurent-jan wrote: > 6: You put the scanimage command as: > $ scanimage -d /dev/scanner0 --format pnm > outfile.pnm > I remember some discussions about the -d argument. I think it should be > -d backend:device, f.e. > $ scanimage -d umax:/dev/sg6 --format pnm > outfile.pnm You are right here. And pnm is the default so it makes only sense to mention that to show the difference to tiff. > 8: Maybe we should think about a more general way of toubleshooting. > Some maufacturers (f.e. of copiers) use a flowchart-like algoritm to > find the actions. It would be nice if we could make somethong like that. Such a kind of flowchart is used "inside" the sane-troubleshoot program at: http://www.meier-geinitz.de/sane/sts/ Not finished yet, however. Bye, Henning From tomf at sjpc.org Wed Jun 25 17:57:17 2003 From: tomf at sjpc.org (Thomas Frayne) Date: 25 Jun 2003 09:57:17 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030624194126.GC7697@meier-geinitz.de> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> Message-ID: <1056560236.3843.853.camel@localhost.localdomain> On Tue, 2003-06-24 at 12:41, Henning Meier-Geinitz wrote: > Hi, > > Then I rebooted to determine if the scanner would be detected as a usb > > device. The hardware browser still showed no browser, and xsane found > > no scanner device on startup. > > > > How can I get the scanner recognized as a USB device? > > That's done automatically. If it's not detected as USB device by the > kernel, it can't be used by hpusbscsi. > > Is it found by sane-find-scanner as root? > Is it found by scanimage -L as root? > If yes, you may need to set up permissions for libusb correctly. > That's explained in man sane-usb. > Thanks. I read the manual, found that permissions were not set correctly, set them in fstab as recommended. Then sane-find-scanner and scanimage -L worked as a normal user. However, the scanner still does not work. I think I am closer, but I am lost. Messages indicated failure of usbdevfs, which is supposed to be obsolete. /usr/local/etc/sane.d/avision.conf lists devices which do not exist. I suspect that there is a mismatches among the sane configuration which was set up for the initial Redhat 9, the sane configuration set up when I installed sane-backends-1.0.12.tar.gz and xsane-0.91.tar.gz, and the kernel 2.4.20-18.9, which was upgraded by Up2date, but I can't figure out how to straighten it out. I'll keep trying. I have just done modprobe scanner vendor=0x0001 product=0x0002, and I plan to reboot and continue debugging, starting with why /dev/usbscanner does not exist. Any help would be appreciated. Tom Frayne Here are the details: found USB scanner (vendor=0x03f0 [hp], product=0x0801 [hp scanjet 7400c]) at libusb:004:002 device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c flatbed scanner Hardware browser lists no scanners Messages: Jun 24 13:37:48 localhost syslogd 1.4.1: restart. Jun 24 13:37:48 localhost syslog: syslogd startup succeeded Jun 24 13:37:48 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started. Jun 24 13:37:48 localhost kernel: Linux version 2.4.20-18.9 (root at gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Wed Jun 4 15:04:35 PDT 2003 Jun 24 13:37:50 localhost kernel: usb.c: registered new driver usbdevfs Jun 24 13:37:50 localhost kernel: usb.c: registered new driver hub Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0 Jun 24 13:37:50 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0870000, IRQ 5 Jun 24 13:37:50 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC Corporation USB Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 24 13:37:50 localhost kernel: hub.c: USB hub found Jun 24 13:37:50 localhost kernel: hub.c: 3 ports detected Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1 Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0 Jun 24 13:37:50 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0872000, IRQ 9 Jun 24 13:37:50 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC Corporation USB (#2) Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 24 13:37:50 localhost kernel: hub.c: USB hub found Jun 24 13:37:50 localhost kernel: hub.c: 2 ports detected Jun 24 13:37:50 localhost kernel: hub.c: new USB device 00:0b.0-1, assigned address 2 Jun 24 13:37:50 localhost kernel: hub.c: USB hub found Jun 24 13:37:50 localhost kernel: hub.c: 4 ports detected Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2 Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2 Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 24 13:37:50 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB 2.0 Jun 24 13:37:50 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem f087a000 Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, assigned bus number 3 Jun 24 13:37:51 localhost kernel: PCI: 00:0b.2 PCI cache line size set incorrectly (32 bytes) by BIOS/FW. Jun 24 13:37:51 localhost kernel: PCI: 00:0b.2 PCI cache line size corrected to 128. Jun 24 13:37:51 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22 Jun 24 13:37:51 localhost kernel: usb.c: USB disconnect on device 00:0b.0-1 address 2 Jun 24 13:37:51 localhost kernel: hub.c: USB hub found Jun 24 13:37:51 localhost kernel: hub.c: 5 ports detected Jun 24 13:37:51 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time 07:14:02 May 29 2003 Jun 24 13:37:51 localhost kernel: usb-uhci.c: High bandwidth mode enabled Jun 24 13:37:51 localhost kernel: PCI: Found IRQ 10 for device 00:07.2 Jun 24 13:37:51 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2 Jun 24 13:37:51 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 24 13:37:51 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, IRQ 10 Jun 24 13:37:51 localhost kernel: usb-uhci.c: Detected 2 ports Jun 24 13:37:51 localhost kernel: usb.c: new USB bus registered, assigned bus number 4 Jun 24 13:37:51 localhost kernel: hub.c: USB hub found Jun 24 13:37:51 localhost kernel: hub.c: 2 ports detected Jun 24 13:37:51 localhost kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Jun 24 13:37:51 localhost kernel: usb.c: registered new driver hiddev Jun 24 13:37:51 localhost kernel: usb.c: registered new driver hid Jun 24 13:37:51 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik Jun 24 13:37:51 localhost kernel: hid-core.c: USB HID support drivers Jun 24 13:37:51 localhost kernel: mice: PS/2 mouse device common for all mice Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1, assigned address 2 Jun 24 13:37:51 localhost kernel: hub.c: USB hub found Jun 24 13:37:51 localhost kernel: hub.c: 4 ports detected Jun 24 13:37:51 localhost kernel: Adding Swap: 1582360k swap-space (priority -1) Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 24 13:37:51 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1.2, assigned address 3 Jun 24 13:37:51 localhost kernel: usb.c: USB device 3 (vend/prod 0x2821/0x5001) is not claimed by any active driver. Jun 24 13:37:51 localhost kernel: usbdevfs: remount parameter error Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1.4, assigned address 4 Jun 24 13:37:51 localhost kernel: usb.c: USB device 4 (vend/prod 0x3f0/0x3404) is not claimed by any active driver. Jun 24 13:37:51 localhost kernel: hdc: attached ide-scsi driver. Jun 24 13:37:51 localhost kernel: scsi1 : SCSI host adapter emulation for IDE ATAPI devices Jun 24 13:37:51 localhost kernel: Vendor: HP Model: CD-Writer+ 8100 Rev: 1.0g Jun 24 13:37:51 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 24 13:37:51 localhost kernel: Initializing USB Mass Storage driver... Jun 24 13:37:51 localhost kernel: usb.c: registered new driver usb-storage Jun 24 13:37:51 localhost kernel: scsi2 : SCSI emulation for USB Mass Storage devices Jun 24 13:37:51 localhost kernel: Vendor: ASUS Model: CRW-5224A Rev: 1.00 Jun 24 13:37:51 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 24 13:37:51 localhost kernel: USB Mass Storage support registered. Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0 Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr1 at scsi1, channel 0, id 0, lun 0 Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr2 at scsi2, channel 0, id 0, lun 0 Jun 24 13:37:51 localhost kernel: (scsi0:A:4): 10.000MB/s transfers (10.000MHz, offset 32) Jun 24 13:37:51 localhost kernel: sr0: scsi3-mmc drive: 0x/0x dvd-ram cd/rw xa/form2 cdda tray Jun 24 13:37:51 localhost kernel: Uniform CD-ROM driver Revision: 3.12 Jun 24 13:37:51 localhost kernel: sr1: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda tray Jun 24 13:37:51 localhost kernel: sr2: scsi-1 drive Jun 24 13:37:51 localhost kernel: usb.c: registered new driver usblp Jun 24 13:37:51 localhost kernel: printer.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404 Jun 24 13:37:51 localhost kernel: printer.c: v0.11: USB Printer Device Class driver Jun 24 13:37:51 localhost kernel: parport0: PC-style at 0x378 [PCSPP,TRISTATE] Jun 24 13:37:51 localhost kernel: ip_tables: (C) 2000-2002 Netfilter core team Jun 24 13:37:51 localhost kernel: ip_conntrack version 2.1 (6143 buckets, 49144 max) - 292 bytes per conntrack Jun 24 13:37:51 localhost kernel: Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002) Jun 24 13:37:51 localhost kernel: PCI: Found IRQ 11 for device 00:0c.0 Jun 24 13:45:57 localhost kernel: ac97_codec: AC97 codec, id: TRA35 (TriTech TR A5) Jun 24 13:45:58 localhost modprobe: modprobe: Can't locate module sound-service-0-3 Jun 24 13:52:13 localhost modprobe: modprobe: Can't locate module char-major-81 Jun 24 13:52:35 localhost last message repeated 7 times Jun 24 13:53:48 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:53:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 24 13:54:18 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:54:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x83 len 22 ret -110 Jun 24 13:54:48 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:54:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 24 13:55:18 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:55:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 24 13:55:48 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:55:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 24 13:57:50 localhost modprobe: modprobe: Can't locate module char-major-81 Jun 24 13:57:50 localhost last message repeated 3 times Jun 24 13:58:20 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:58:20 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 24 13:58:50 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:58:50 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 24 13:59:20 localhost kernel: usb_control/bulk_msg: timeout Jun 24 13:59:20 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 24 14:16:09 localhost gconfd (root-3450): Received signal 1, shutting down cleanly Jun 24 14:16:45 localhost rpc.statd[2040]: Caught signal 15, un-registering and exiting.Jun 25 08:55:06 Jun 25 08:55:06 localhost kernel: usb.c: registered new driver usbscanner Jun 25 08:55:06 localhost kernel: scanner.c: 0.4.12:USB Scanner Driver Jun 25 08:55:06 localhost kernel: scanner.c: probe_scanner: User specified USB scanner -- Vendor:Product - 1:2 GENERIC KERNEL SCANNER DRIVER Ensure that the access permissions for the USB device are set appropri- ately. We recommend to add a group "scanner" to /etc/group which con- tains all users that should have access to the scanner. The permission of the device should then be set to allow group read and write access. For example, if the scanner is at USB device /dev/usb/scanner0, then the following two commands would set the permission correctly: $ chgrp scanner /dev/usb/scanner0 $ chmod 660 /dev/usb/scanner0 If your scanner isn?t detected automatically by your operating system?s scanner driver, you need to tell the kernel the vendor and product ids of your scanner. For Linux, this can be done with modprobe parameters: First, remove the scanner module (rmmod scanner), then load it again: modprobe scanner vendor=0x0001 product=0x0002. Use the appropriate vendor and product ids (e.g. from /var/log/messages, dmesg, or cat /proc/bus/usb/devices) /usr/local/etc/sane.d/avision.conf scsi AVISION scsi FCPA scsi MINOLTA scsi MITSBISH MCA-S600C scsi MITSBISH MCA-SS600 scsi HP scsi hp scsi /dev/scanner usb /dev/usbscanner usb /dev/usb/scanner [root at localhost root]# ls -l /dev/usb/scanner0 crw------- 1 tom root 180, 48 Jan 30 02:24 /dev/usb/scanner0 [root at localhost root]# ls -l /dev/usbscanner ls: /dev/usbscanner: No such file or directory [root at localhost root]# ls -l /dev/usb/scanner ls: /dev/usb/scanner: No such file or directory [root at localhost root]# /etc/fstab none /proc/bus/usb usbfs defaults,devmode=0666 0 0 /proc/bus/usb/devices 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=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0801 Rev= 0.01 S: Manufacturer=hp S: Product=hp scanjet 7400c S: SerialNumber=87 tem 7400c /proc/bus/usb/drivers usbdevfs hub 96-111: hiddev hid usb-storage 0- 15: usblp 48- 63: usbscanner From henning at meier-geinitz.de Wed Jun 25 19:11:01 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 25 Jun 2003 20:11:01 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <200306251834.17699.fsanta@arrakis.es> References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> <200306251834.17699.fsanta@arrakis.es> Message-ID: <20030625181101.GE9836@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 06:34:17PM +0200, fsanta wrote: > Could you tell me how to do that? To do what? Hint: If you quote the text you are referring to it's easier to understand what you mean? :-) I don't have your scanner or your card so I don't have personal experiences with this combination. But the "synchronous tranfer" SCSI feature seems to make trouble with many older SCSI scanners. And your kernel complains about it so it may be worth a try. Check the documentation in the Linux source code. Which SCSI driver do you use for the 2904? > the scsi card is a very basic 2904 which Oliver added to the database > of usable cards way back years ago. The scsi terminator plug is > missing on the scanner. Could it have anything to do with that? I > can't test it as I haven't got an scsi terminator plug. As I said, I don't have experience with that combination, but my scanners work without a terminator. At least if you have only one device on the SCSI bus. > We removed it > under 8.1 to produce acceptable scans. It was of very poor quality with. If adding/removing the terminator changes the quality of the scan something is completely broken. A wrong termination can lead to SCSI errors but I haven't heard about an influence on image quality. That would mean only the data is corrupted, not the commands and the SCSI system doesn't detect that (parity?). Bye, Henning From anoah at pfeiffer.edu Wed Jun 25 19:36:57 2003 From: anoah at pfeiffer.edu (m. allan noah) Date: Wed, 25 Jun 2003 14:36:57 -0400 (EDT) Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <1056560236.3843.853.camel@localhost.localdomain> Message-ID: tom, did you do an 'rpm -e --force --nodeps sane-backends' first? when you compiled the new sane backends, did you do: ./configure --prefix=/usr --sysconfdir=/etc make make install if not, start with those two things. then we can be sure that the version of sane you are using is the one you compiled. allan On 25 Jun 2003, Thomas Frayne wrote: > On Tue, 2003-06-24 at 12:41, Henning Meier-Geinitz wrote: > > Hi, > > > Then I rebooted to determine if the scanner would be detected as a usb > > > device. The hardware browser still showed no browser, and xsane found > > > no scanner device on startup. > > > > > > How can I get the scanner recognized as a USB device? > > > > That's done automatically. If it's not detected as USB device by the > > kernel, it can't be used by hpusbscsi. > > > > Is it found by sane-find-scanner as root? > > Is it found by scanimage -L as root? > > If yes, you may need to set up permissions for libusb correctly. > > That's explained in man sane-usb. > > > > Thanks. I read the manual, found that permissions were not set > correctly, set them in fstab as recommended. Then sane-find-scanner and > scanimage -L worked as a normal user. However, the scanner still does > not work. I think I am closer, but I am lost. > > Messages indicated failure of usbdevfs, which is supposed to be > obsolete. /usr/local/etc/sane.d/avision.conf lists devices which do not > exist. I suspect that there is a mismatches among the sane > configuration which was set up for the initial Redhat 9, the sane > configuration set up when I installed sane-backends-1.0.12.tar.gz and > xsane-0.91.tar.gz, and the kernel 2.4.20-18.9, which was upgraded by > Up2date, but I can't figure out how to straighten it out. > > I'll keep trying. I have just done > modprobe scanner vendor=0x0001 product=0x0002, > and I plan to reboot and continue debugging, starting with why > /dev/usbscanner does not exist. > > Any help would be appreciated. > > Tom Frayne > > > > > Here are the details: > > found USB scanner (vendor=0x03f0 [hp], product=0x0801 [hp scanjet > 7400c]) at libusb:004:002 > > device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c > flatbed scanner > > Hardware browser lists no scanners > > Messages: > Jun 24 13:37:48 localhost syslogd 1.4.1: restart. > Jun 24 13:37:48 localhost syslog: syslogd startup succeeded > Jun 24 13:37:48 localhost kernel: klogd 1.4.1, log source = /proc/kmsg > started. > Jun 24 13:37:48 localhost kernel: Linux version 2.4.20-18.9 > (root at gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 > Wed Jun 4 15:04:35 PDT 2003 > Jun 24 13:37:50 localhost kernel: usb.c: registered new driver usbdevfs > Jun 24 13:37:50 localhost kernel: usb.c: registered new driver hub > Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0 > Jun 24 13:37:50 localhost kernel: usb-ohci.c: USB OHCI at membase > 0xf0870000, IRQ 5 > Jun 24 13:37:50 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC > Corporation USB > Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, > assigned bus number 1 > Jun 24 13:37:50 localhost kernel: hub.c: USB hub found > Jun 24 13:37:50 localhost kernel: hub.c: 3 ports detected > Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1 > Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0 > Jun 24 13:37:50 localhost kernel: usb-ohci.c: USB OHCI at membase > 0xf0872000, IRQ 9 > Jun 24 13:37:50 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC > Corporation USB (#2) > Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, > assigned bus number 2 > Jun 24 13:37:50 localhost kernel: hub.c: USB hub found > Jun 24 13:37:50 localhost kernel: hub.c: 2 ports detected > Jun 24 13:37:50 localhost kernel: hub.c: new USB device 00:0b.0-1, > assigned address 2 > Jun 24 13:37:50 localhost kernel: hub.c: USB hub found > Jun 24 13:37:50 localhost kernel: hub.c: 4 ports detected > Jun 24 13:37:50 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2 > Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2 > Jun 24 13:37:50 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 > Jun 24 13:37:50 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB > 2.0 > Jun 24 13:37:50 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem > f087a000 > Jun 24 13:37:50 localhost kernel: usb.c: new USB bus registered, > assigned bus number 3 > Jun 24 13:37:51 localhost kernel: PCI: 00:0b.2 PCI cache line size set > incorrectly (32 bytes) by BIOS/FW. > Jun 24 13:37:51 localhost kernel: PCI: 00:0b.2 PCI cache line size > corrected to 128. > Jun 24 13:37:51 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, > EHCI 0.95, driver 2003-Jan-22 > Jun 24 13:37:51 localhost kernel: usb.c: USB disconnect on device > 00:0b.0-1 address 2 > Jun 24 13:37:51 localhost kernel: hub.c: USB hub found > Jun 24 13:37:51 localhost kernel: hub.c: 5 ports detected > Jun 24 13:37:51 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time > 07:14:02 May 29 2003 > Jun 24 13:37:51 localhost kernel: usb-uhci.c: High bandwidth mode > enabled > Jun 24 13:37:51 localhost kernel: PCI: Found IRQ 10 for device 00:07.2 > Jun 24 13:37:51 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2 > Jun 24 13:37:51 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 > Jun 24 13:37:51 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, > IRQ 10 > Jun 24 13:37:51 localhost kernel: usb-uhci.c: Detected 2 ports > Jun 24 13:37:51 localhost kernel: usb.c: new USB bus registered, > assigned bus number 4 > Jun 24 13:37:51 localhost kernel: hub.c: USB hub found > Jun 24 13:37:51 localhost kernel: hub.c: 2 ports detected > Jun 24 13:37:51 localhost kernel: usb-uhci.c: v1.275:USB Universal Host > Controller Interface driver > Jun 24 13:37:51 localhost kernel: usb.c: registered new driver hiddev > Jun 24 13:37:51 localhost kernel: usb.c: registered new driver hid > Jun 24 13:37:51 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, > Vojtech Pavlik > Jun 24 13:37:51 localhost kernel: hid-core.c: USB HID support drivers > Jun 24 13:37:51 localhost kernel: mice: PS/2 mouse device common for all > mice > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1, > assigned address 2 > Jun 24 13:37:51 localhost kernel: hub.c: USB hub found > Jun 24 13:37:51 localhost kernel: hub.c: 4 ports detected > Jun 24 13:37:51 localhost kernel: Adding Swap: 1582360k swap-space > (priority -1) > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:07.2-1, > assigned address 2 > Jun 24 13:37:51 localhost kernel: usb.c: USB device 2 (vend/prod > 0x3f0/0x801) is not claimed by any active driver. > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1.2, > assigned address 3 > Jun 24 13:37:51 localhost kernel: usb.c: USB device 3 (vend/prod > 0x2821/0x5001) is not claimed by any active driver. > Jun 24 13:37:51 localhost kernel: usbdevfs: remount parameter error > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:0b.2-1.4, > assigned address 4 > Jun 24 13:37:51 localhost kernel: usb.c: USB device 4 (vend/prod > 0x3f0/0x3404) is not claimed by any active driver. > Jun 24 13:37:51 localhost kernel: hdc: attached ide-scsi driver. > Jun 24 13:37:51 localhost kernel: scsi1 : SCSI host adapter emulation > for IDE ATAPI devices > Jun 24 13:37:51 localhost kernel: Vendor: HP Model: CD-Writer+ > 8100 Rev: 1.0g > Jun 24 13:37:51 localhost kernel: Type: > CD-ROM ANSI SCSI revision: 02 > Jun 24 13:37:51 localhost kernel: Initializing USB Mass Storage > driver... > Jun 24 13:37:51 localhost kernel: usb.c: registered new driver > usb-storage > Jun 24 13:37:51 localhost kernel: scsi2 : SCSI emulation for USB Mass > Storage devices > Jun 24 13:37:51 localhost kernel: Vendor: ASUS Model: > CRW-5224A Rev: 1.00 > Jun 24 13:37:51 localhost kernel: Type: > CD-ROM ANSI SCSI revision: 02 > Jun 24 13:37:51 localhost kernel: USB Mass Storage support registered. > Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr0 at scsi0, > channel 0, id 4, lun 0 > Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr1 at scsi1, > channel 0, id 0, lun 0 > Jun 24 13:37:51 localhost kernel: Attached scsi CD-ROM sr2 at scsi2, > channel 0, id 0, lun 0 > Jun 24 13:37:51 localhost kernel: (scsi0:A:4): 10.000MB/s transfers > (10.000MHz, offset 32) > Jun 24 13:37:51 localhost kernel: sr0: scsi3-mmc drive: 0x/0x dvd-ram > cd/rw xa/form2 cdda tray > Jun 24 13:37:51 localhost kernel: Uniform CD-ROM driver Revision: 3.12 > Jun 24 13:37:51 localhost kernel: sr1: scsi3-mmc drive: 24x/24x writer > cd/rw xa/form2 cdda tray > Jun 24 13:37:51 localhost kernel: sr2: scsi-1 drive > Jun 24 13:37:51 localhost kernel: usb.c: registered new driver usblp > Jun 24 13:37:51 localhost kernel: printer.c: usblp0: USB Bidirectional > printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404 > Jun 24 13:37:51 localhost kernel: printer.c: v0.11: USB Printer Device > Class driver > Jun 24 13:37:51 localhost kernel: parport0: PC-style at 0x378 > [PCSPP,TRISTATE] > Jun 24 13:37:51 localhost kernel: ip_tables: (C) 2000-2002 Netfilter > core team > Jun 24 13:37:51 localhost kernel: ip_conntrack version 2.1 (6143 > buckets, 49144 max) - 292 bytes per conntrack > Jun 24 13:37:51 localhost kernel: Linux Tulip driver version > 0.9.15-pre12 (Aug 9, 2002) > Jun 24 13:37:51 localhost kernel: PCI: Found IRQ 11 for device 00:0c.0 > > Jun 24 13:45:57 localhost kernel: ac97_codec: AC97 codec, id: TRA35 > (TriTech TR A5) > Jun 24 13:45:58 localhost modprobe: modprobe: Can't locate module > sound-service-0-3 > Jun 24 13:52:13 localhost modprobe: modprobe: Can't locate module > char-major-81 > Jun 24 13:52:35 localhost last message repeated 7 times > Jun 24 13:53:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:53:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x82 len 1 ret -110 > Jun 24 13:54:18 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:54:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x83 len 22 ret -110 > Jun 24 13:54:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:54:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x1 len 6 ret -110 > Jun 24 13:55:18 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:55:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x82 len 1 ret -110 > Jun 24 13:55:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:55:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x1 len 6 ret -110 > Jun 24 13:57:50 localhost modprobe: modprobe: Can't locate module > char-major-81 > Jun 24 13:57:50 localhost last message repeated 3 times > > Jun 24 13:58:20 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:58:20 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x1 len 6 ret -110 > Jun 24 13:58:50 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:58:50 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x82 len 1 ret -110 > Jun 24 13:59:20 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:59:20 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 > ep 0x1 len 6 ret -110 > > Jun 24 14:16:09 localhost gconfd (root-3450): Received signal 1, > shutting down cleanly > > Jun 24 14:16:45 localhost rpc.statd[2040]: Caught signal 15, > un-registering and exiting.Jun 25 08:55:06 > > Jun 25 08:55:06 localhost kernel: usb.c: registered new driver > usbscanner > Jun 25 08:55:06 localhost kernel: scanner.c: 0.4.12:USB Scanner Driver > Jun 25 08:55:06 localhost kernel: scanner.c: probe_scanner: User > specified USB scanner -- Vendor:Product - 1:2 > > GENERIC KERNEL SCANNER DRIVER > Ensure that the access permissions for the USB device are set > appropri- > ately. We recommend to add a group "scanner" to /etc/group > which con- > tains all users that should have access to the scanner. The > permission > of the device should then be set to allow group read and write > access. > For example, if the scanner is at USB device > /dev/usb/scanner0, then > the following two commands would set the permission correctly: > > $ chgrp scanner /dev/usb/scanner0 > $ chmod 660 /dev/usb/scanner0 > > If your scanner isn???t detected automatically by your operating > system???s > scanner driver, you need to tell the kernel the vendor and > product ids > of your scanner. For Linux, this can be done with modprobe > parameters: > First, remove the scanner module (rmmod scanner), then load it > again: > modprobe scanner vendor=0x0001 product=0x0002. Use the > appropriate > vendor and product ids (e.g. from /var/log/messages, dmesg, > or cat > /proc/bus/usb/devices) > > > /usr/local/etc/sane.d/avision.conf > scsi AVISION > scsi FCPA > scsi MINOLTA > scsi MITSBISH MCA-S600C > scsi MITSBISH MCA-SS600 > scsi HP > scsi hp > scsi /dev/scanner > usb /dev/usbscanner > usb /dev/usb/scanner > > [root at localhost root]# ls -l /dev/usb/scanner0 > crw------- 1 tom root 180, 48 Jan 30 02:24 > /dev/usb/scanner0 > [root at localhost root]# ls -l /dev/usbscanner > ls: /dev/usbscanner: No such file or directory > [root at localhost root]# ls -l /dev/usb/scanner > ls: /dev/usb/scanner: No such file or directory > [root at localhost root]# > > > /etc/fstab > none /proc/bus/usb usbfs defaults,devmode=0666 0 0 > > /proc/bus/usb/devices > 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=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 > D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=03f0 ProdID=0801 Rev= 0.01 > S: Manufacturer=hp > S: Product=hp scanjet 7400c > S: SerialNumber=87 tem 7400c > > /proc/bus/usb/drivers > usbdevfs > hub > 96-111: hiddev > hid > usb-storage > 0- 15: usblp > 48- 63: usbscanner > > > > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From matt.lung at midwest-tool.com Wed Jun 25 20:16:23 2003 From: matt.lung at midwest-tool.com (Matt Lung) Date: Wed, 25 Jun 2003 14:16:23 -0500 Subject: [sane-devel] ScanJet 5300C question Message-ID: <3EF9F507.6040604@midwest-tool.com> I would like to use the ADF we have with our HP 5300C scanner under linux and Sane but I have yet to find any documentation or help on how to setup an ADF with this scanner. It scans just fine without it, but with out the ADF funcioning I'll be forced to use it in Windows forever. Is an ADF even supported with the HP 5300C? If so, where can I find information on how to do this? thanks for any help From tomf at sjpc.org Wed Jun 25 20:40:18 2003 From: tomf at sjpc.org (Thomas Frayne) Date: 25 Jun 2003 12:40:18 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: References: Message-ID: <1056570017.5677.24.camel@localhost.localdomain> On Wed, 2003-06-25 at 11:36, m. allan noah wrote: > tom, did you do an 'rpm -e --force --nodeps sane-backends' first? Yes. > > when you compiled the new sane backends, did you do: > > ./configure --prefix=/usr --sysconfdir=/etc No. I'll uninstall and verify that no sign of sane-backends remains, then install again. > make Yes. > make install Yes. > > if not, start with those two things. then we can be sure that the version > of sane you are using is the one you compiled. Thanks. I'll do it. > > allan > > On 25 Jun 2003, Thomas Frayne wrote: > > > On Tue, 2003-06-24 at 12:41, Henning Meier-Geinitz wrote: > > > Hi, > > > > Then I rebooted to determine if the scanner would be detected as a usb > > > > device. The hardware browser still showed no browser, and xsane found > > > > no scanner device on startup. > > > > > > > > How can I get the scanner recognized as a USB device? > > > > > > That's done automatically. If it's not detected as USB device by the > > > kernel, it can't be used by hpusbscsi. > > > > > > Is it found by sane-find-scanner as root? > > > Is it found by scanimage -L as root? > > > If yes, you may need to set up permissions for libusb correctly. > > > That's explained in man sane-usb. > > > > > > > Thanks. I read the manual, found that permissions were not set > > correctly, set them in fstab as recommended. Then sane-find-scanner and > > scanimage -L worked as a normal user. However, the scanner still does > > not work. I think I am closer, but I am lost. > > > > Messages indicated failure of usbdevfs, which is supposed to be > > obsolete. /usr/local/etc/sane.d/avision.conf lists devices which do not > > exist. I suspect that there is a mismatches among the sane > > configuration which was set up for the initial Redhat 9, the sane > > configuration set up when I installed sane-backends-1.0.12.tar.gz and > > xsane-0.91.tar.gz, and the kernel 2.4.20-18.9, which was upgraded by > > Up2date, but I can't figure out how to straighten it out. > > > > I'll keep trying. I have just done > > modprobe scanner vendor=0x0001 product=0x0002, > > and I plan to reboot and continue debugging, starting with why > > /dev/usbscanner does not exist. > > > > Any help would be appreciated. > > > > Tom Frayne > > From fsanta at arrakis.es Wed Jun 25 21:03:25 2003 From: fsanta at arrakis.es (fsanta) Date: Wed, 25 Jun 2003 22:03:25 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <20030625181101.GE9836@meier-geinitz.de> References: <200306251705.27766.fsanta@arrakis.es> <200306251834.17699.fsanta@arrakis.es> <20030625181101.GE9836@meier-geinitz.de> Message-ID: <200306252203.25459.fsanta@arrakis.es> Hi again. Just wondered if Oliver was still around who I think wrote the backend. As an iterim solution, I've gone back to SuSE 8.1 on the client where the scanner is and all is well. I'd just like all our clients to have the same OS for system consitency. Is there anyone from SuSE still on this list who could help me get the scanner going under 8.2? Thanks for your time and sorry to be such a pain as usual. Steve. On Wednesday 25 June 2003 20:11, Henning Meier-Geinitz wrote: > Hi, > > On Wed, Jun 25, 2003 at 06:34:17PM +0200, fsanta wrote: > > Could you tell me how to do that? > > To do what? Hint: If you quote the text you are referring to it's > easier to understand what you mean? :-) > > I don't have your scanner or your card so I don't have personal > experiences with this combination. But the "synchronous tranfer" SCSI > feature seems to make trouble with many older SCSI scanners. And your > kernel complains about it so it may be worth a try. Check the > documentation in the Linux source code. Which SCSI driver do you use > for the 2904? > > > the scsi card is a very basic 2904 which Oliver added to the database > > of usable cards way back years ago. The scsi terminator plug is > > missing on the scanner. Could it have anything to do with that? I > > can't test it as I haven't got an scsi terminator plug. > > As I said, I don't have experience with that combination, but my > scanners work without a terminator. At least if you have only one > device on the SCSI bus. > > > We removed it > > under 8.1 to produce acceptable scans. It was of very poor quality with. > > If adding/removing the terminator changes the quality of the scan > something is completely broken. A wrong termination can lead to SCSI > errors but I haven't heard about an influence on image quality. That > would mean only the data is corrupted, not the commands and the SCSI > system doesn't detect that (parity?). > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From tomf at sjpc.org Wed Jun 25 21:07:14 2003 From: tomf at sjpc.org (Thomas Frayne) Date: 25 Jun 2003 13:07:14 -0700 Subject: [sane-devel] ScanJet 5300C question In-Reply-To: <3EF9F507.6040604@midwest-tool.com> References: <3EF9F507.6040604@midwest-tool.com> Message-ID: <1056571633.5677.30.camel@localhost.localdomain> On Wed, 2003-06-25 at 12:16, Matt Lung wrote: ... > Is an ADF even supported with the HP 5300C? > > If so, where can I find information on how to do this? I am going through the same process for the HP 7450C. Try searching the archives for HP 7450C for some tips that may apply to you. If the connection is USB, you may need to upgrade sane-backends. I did this, and it looks like I am getting close, but I'm still not there yet. From henning at meier-geinitz.de Wed Jun 25 21:52:40 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 25 Jun 2003 22:52:40 +0200 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <1056560236.3843.853.camel@localhost.localdomain> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> Message-ID: <20030625205240.GA12653@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 09:57:17AM -0700, Thomas Frayne wrote: > Thanks. I read the manual, found that permissions were not set > correctly, set them in fstab as recommended. Then sane-find-scanner and > scanimage -L worked as a normal user. Is the scanner found as USB device now? Something like "libusb:001:002"? Please show us "sane-find-scanner -q". I have to admitt that I'm a bit confused by the backend. It uses USB interrupt transfers to get the status of the scanner. However that only works with libusb, not the kernel scanner driver. So I don't really know why the backend lists "usb /dev/ubs/scanner" in avision.conf. Maybe the maintainer can enlighten me :-) > However, the scanner still does not work. What exactly doesn't work? > Messages indicated failure of usbdevfs, which is supposed to be > obsolete. The name "usbdevfs" is obsolete. It's called "usbfs" now. But that's not your problem. > /usr/local/etc/sane.d/avision.conf lists devices which do not > exist. Usually the config files list all devices and device files the backend supports. So it doesn't matter if there are additional ones. The backend checks for all USB devices anymway, I don't think the entries in avsion.conf are necessary at all. > and xsane-0.91.tar.gz, and the kernel 2.4.20-18.9, Those two shouldn't matter. > I'll keep trying. I have just done > modprobe scanner vendor=0x0001 product=0x0002, These vendor and product ids are most probably wrong. If the scanner driver works at all, try something like this: rmmod scanner modprobe scanner vendor=0x03f0 product=0x0801 > and I plan to reboot and continue debugging, starting with why > /dev/usbscanner does not exist. Some distributions use(d) /dev/usbscanner, some use /dev/usb/scanner0. Shouldn't matter in your case. > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 > Jun 24 13:37:51 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. That's your scanner. It's ok that it's not "claimed by any active driver" because in this case it's used by usbfs (libusb). You can also try to load the USB scanner driver as mentioned above. Then you should get a message from that driver. > Jun 24 13:53:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:53:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 > Jun 24 13:54:18 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:54:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x83 len 22 ret -110 > Jun 24 13:54:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:54:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 > Jun 24 13:55:18 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:55:18 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 > Jun 24 13:55:48 localhost kernel: usb_control/bulk_msg: timeout > Jun 24 13:55:48 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 That doesn't look good. Your scanner doesn't seem to accept any input on any endpoint (bulk in, out and interrupt). I recommend to unplug/replug your scanner before any test. Otherwise it may be confuded by eralier tests. > [root at localhost root]# ls -l /dev/usb/scanner0 > crw------- 1 tom root 180, 48 Jan 30 02:24 > /dev/usb/scanner0 That's ok. YOu can add a link /dev/usb/scanner to that one but I don't think it's necessary. > /proc/bus/usb/devices Those entries start with "T:" (topology). > 48- 63: usbscanner Is loaded but doesn't know about your scanner. Bye, Henning From kouno.hironori at pfu.fujitsu.com Thu Jun 26 01:50:23 2003 From: kouno.hironori at pfu.fujitsu.com (hironori kohno) Date: Thu, 26 Jun 2003 09:50:23 +0900 Subject: [sane-devel] Please let me know frontend which operates on "MacOS X". Message-ID: <200306260950.EJH42366.ISJPSPVPLOP.JO@pfu.fujitsu.com> Hello, I am developing the backend for MacOS X. If there is famous frontend which operates on MacOS X, please let me know some. Regards, Kouno -- kouno hironori kouno.hironori at pfu.fujitsu.com -- hironori kohno kouno.hironori at pfu.fujitsu.com From jollyprince at juno.com Thu Jun 26 02:30:22 2003 From: jollyprince at juno.com (jollyprince at juno.com) Date: Thu, 26 Jun 2003 01:30:22 GMT Subject: [sane-devel] Visioneer 5800 Message-ID: <20030625.183103.2373.545548@webmail01.lax.untd.com> I'm a newbie who just got his USB printer working and decided to tackle the scanner next. So far I've found the Vendor number and Product ID and inserted them into the modules.conf file. QUESTION: Is it a foregone conclusion that I need to recompile the kernel next or is there a scanner install that does not require kernel recompile? From crapsite at gmx.net Thu Jun 26 05:43:59 2003 From: crapsite at gmx.net (Michael Herder) Date: Thu, 26 Jun 2003 06:43:59 +0200 Subject: [sane-devel] Please let me know frontend which operates on "MacOS X". In-Reply-To: <200306260950.EJH42366.ISJPSPVPLOP.JO@pfu.fujitsu.com> References: <200306260950.EJH42366.ISJPSPVPLOP.JO@pfu.fujitsu.com> Message-ID: <20030626044233.1E98952@panda.mostang.com> hironori kohno, Donnerstag, 26. Juni 2003 02:50: > Hello, > > I am developing the backend for MacOS X. > If there is famous frontend which operates on MacOS X, > please let me know some. I don't know about famous ones, but some days back Trolltech released Qt/Mac under the GPL, therefore it should be possible to port QuiteInsane. It won't compile out of the box (in fact, I don't know, how platform dependent the code is), but if someone wants to try it, or already ported it, then please let me know. bb Michael http://www.trolltech.com/download/qt/mac.html http://sf.net/projects/quiteinsane From kouno.hironori at pfu.fujitsu.com Thu Jun 26 06:39:52 2003 From: kouno.hironori at pfu.fujitsu.com (hironori kohno) Date: Thu, 26 Jun 2003 14:39:52 +0900 Subject: [sane-devel] Please let me know frontend which operates on"MacOS X". In-Reply-To: <20030626044233.1E98952@panda.mostang.com> References: <200306260950.EJH42366.ISJPSPVPLOP.JO@pfu.fujitsu.com> <20030626044233.1E98952@panda.mostang.com> Message-ID: <200306261439.JEH62606.I.PVSJOPPOPJLS@pfu.fujitsu.com> <20030626044233.1E98952 at panda.mostang.com> ?? "Re: [sane-devel] Please let me know frontend which operates on"MacOS X"." ????? "Michael Herder "????????? > hironori kohno, Donnerstag, 26. Juni 2003 02:50: > > Hello, > > > > I am developing the backend for MacOS X. > > If there is famous frontend which operates on MacOS X, > > please let me know some. > > I don't know about famous ones, but some days back Trolltech released Qt/Mac > under the GPL, therefore it should be possible to port QuiteInsane. under the Qt/Mac, QuiteInsane. Thanks. > It won't compile out of the box (in fact, I don't know, how platform > >dependent the > code is), but if someone wants to try it, or already ported it, then please > let me know. > > bb > Michael > > http://www.trolltech.com/download/qt/mac.html > http://sf.net/projects/quiteinsane > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- kouno hironori kouno.hironori at pfu.fujitsu.com -- kouno hironori kouno.hironori at pfu.fujitsu.com From kleptog at svana.org Thu Jun 26 06:41:34 2003 From: kleptog at svana.org (Martijn van Oosterhout) Date: Thu, 26 Jun 2003 15:41:34 +1000 Subject: [sane-devel] Visioneer 5800 In-Reply-To: <20030625.183103.2373.545548@webmail01.lax.untd.com> References: <20030625.183103.2373.545548@webmail01.lax.untd.com> Message-ID: <20030626054133.GB26472@svana.org> On Thu, Jun 26, 2003 at 01:30:22AM +0000, jollyprince at juno.com wrote: > > I'm a newbie who just got his USB printer working and decided to tackle the scanner next. So far I've found the Vendor number and Product ID and inserted them into the modules.conf file. > > QUESTION: Is it a foregone conclusion that I need to recompile the kernel next or is there a scanner install that does not require kernel recompile? Many of the modern drivers use libusb rather than a specific scanner module, so specific scanner modules are becoming a thing of the past. As long as you have usbfs compiled in, you should be fine. -- Martijn van Oosterhout http://svana.org/kleptog/ > "the West won the world not by the superiority of its ideas or values or > religion but rather by its superiority in applying organized violence. > Westerners often forget this fact, non-Westerners never do." > - Samuel P. Huntington -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: From henning at meier-geinitz.de Thu Jun 26 08:44:35 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 26 Jun 2003 09:44:35 +0200 Subject: [sane-devel] Visioneer 5800 In-Reply-To: <20030625.183103.2373.545548@webmail01.lax.untd.com> References: <20030625.183103.2373.545548@webmail01.lax.untd.com> Message-ID: <20030626074435.GB26193@meier-geinitz.de> Hi, On Thu, Jun 26, 2003 at 01:30:22AM +0000, jollyprince at juno.com wrote: > I'm a newbie who just got his USB printer working and decided to > tackle the scanner next. So far I've found the Vendor number and > Product ID and inserted them into the modules.conf file. The scanner isn't even in our list of scanners. That usually means it is not supported by any SANE backend. Could you please give us any information you have about this scanner? Especially I'm interested in the output of "cat /proc/bus/usb/devices" while the scanner is plugged in. > QUESTION: Is it a foregone conclusion that I need to recompile the > kernel next No. modprobe scanner vendor=... product=... works the same way. Or just use libusb (without the scanner module). That's not the problem. If you tell me the vendor and product ids I'll add them to the kernel scanner driver. > or is there a scanner install that does not require kernel recompile? You don't need to recompile the kernel. But even recompilation doesn't help you because you need a SANE backend for yout scanner. And that's most probably not written yet. On how to write a backend see: http://www.meier-geinitz.de/sane/misc/unsupported.html Bye, Henning From henning at meier-geinitz.de Thu Jun 26 09:09:33 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 26 Jun 2003 10:09:33 +0200 Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: References: Message-ID: <20030626080933.GD26193@meier-geinitz.de> Hi, On Wed, Jun 25, 2003 at 03:16:35PM +0200, Henrik Schmidt wrote: > I'm trying to use a Microtek ScanMaker III with Solaris 2.6 and the scg > SCSI driver. I'm using sane-backends 1.0.12 with frontend 1.0.10. I'm not sure how old this scanner is but as you can see in some recent threads on this list some scanners don't like "advanced" SCSI features like reconnect/disconnect or synchronous negotiation. Maybe it helps to turn them off in the SCSI driver or adapter BIOS. > The scanner is detected but as soon as I start a scan or prescan either > with xscanimage or xsane the application locks up. I get errors in > /var/adm/messages. After 2 minutes the applications return with a timeout > and i/o error. > Jun 25 13:08:25 cortex unix: data transfer overrun: current esp state: Hm, maybe the SCSI buffer is too big? Try setting the environment variable SANE_SG_BUFFER_SIZE to e.g. 32768. > I checked the scanner on a Windows computer and it did work. I checked it > on another computer with sane and it failed too. Also with Solaris? Same SCSI controller? At least for Solaris/x86 we have a positive report about a SCSI scanner working (with SANE 1.0.9). > I had it running some a ago. When I moved the computer to a different > location I updated sane and it failed to work afterwards. Going back to > older sane backend versions (up to 1.0.8) didn't help either. Then it doesn't look like a SANE problem, does it? > I tried to contact both the microtek backend coder as well as the contact > in README.solaris but got no reply. Matthew Marjanovic posted some days ago on this list. Maybe you can try it again? Bye, Henning From hbs at ks.informatik.uni-kiel.de Thu Jun 26 10:45:02 2003 From: hbs at ks.informatik.uni-kiel.de (Henrik Schmidt) Date: Thu, 26 Jun 2003 11:45:02 +0200 (MEST) Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: <20030626080933.GD26193@meier-geinitz.de> References: <20030626080933.GD26193@meier-geinitz.de> Message-ID: On Thu, 26 Jun 2003, Henning Meier-Geinitz wrote: > Hm, maybe the SCSI buffer is too big? Try setting the environment > variable SANE_SG_BUFFER_SIZE to e.g. 32768. > This didn't help. > > I checked the scanner on a Windows computer and it did work. I checked it > > on another computer with sane and it failed too. > > Also with Solaris? Same SCSI controller? > Yes. > At least for Solaris/x86 we have a positive report about a SCSI > scanner working (with SANE 1.0.9). > > > I had it running some a ago. When I moved the computer to a different > > location I updated sane and it failed to work afterwards. Going back to > > older sane backend versions (up to 1.0.8) didn't help either. > > Then it doesn't look like a SANE problem, does it? > I don't know. As the scg driver is working on the computer (I can use a cdrecorder with cdrecord) and the scanner is working too my rough guess was that sane might be involved. > > I tried to contact both the microtek backend coder as well as the contact > > in README.solaris but got no reply. > > Matthew Marjanovic posted some days ago on this list. Maybe you can > try it again? > Ok, will try. Here is the critical section of the debug output from xscanimage : [microtek] .download_gamma... [microtek] .download_gamma: 4096 entries of 2 bytes, max 255 [microtek] .download_gamma: by default [microtek] .mode_select 8... [microtek] .mode_select: pap_len: 8399 [microtek] .mode_select_1 8... [microtek] .wait_ready 8... [microtek] .start_scan... [microtek] .get_scan_status 8... [microtek] get_scan_status(6): 0, 300, 504 -> #0 [microtek] > 0 2c 1 f8 1 0 [microtek] Scan Param: [microtek] pix bpl: 894 hdr bpl: 6 ppl: 298 [microtek] undel bytes: 450576 unscan lines: 504 planes: 3 [microtek] dest bpl: 894 dest ppl: 298 aspect: 1.000000 [microtek] sane_get_parameters... [microtek] sane_set_io_mode... [microtek] sane_read... [microtek] read_from_scanner... [microtek] .get_scan_status 8... [microtek] get_scan_status(6): 0, 300, 504 -> #0 [microtek] > 0 2c 1 f8 1 0 [microtek] read_from_scanner: gss busy, linewidth, remaining: 0, 300, 504 [microtek] sane_read: max_scsi: 145, rem: 504, nlines: 145 [microtek] .read_scan_data... [microtek] sane_read: bad read_scan_data! [microtek] sane_read: read_from_scanner failed. [microtek] end_scan... [microtek] .stop_scan... [sanei_scsi] sanei_scsi_cmd 1b: timeout From fsanta at arrakis.es Thu Jun 26 16:19:07 2003 From: fsanta at arrakis.es (fsanta) Date: Thu, 26 Jun 2003 17:19:07 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <20030625152250.GA9836@meier-geinitz.de> References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> Message-ID: <200306261719.07135.fsanta@arrakis.es> > > > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > > synchronous negotiation. Using asynchronous transfers > > Try disabling synchronous transfers in your SCSI driver or the BIOS > (but I guess your SCSI controller doesn't have a BIOS). > Hi. Could anyone tell me how to do this. . ."disabling synchronous transfers in your SCSI driver or the BIOS..." THanks, Steve. From henning at meier-geinitz.de Thu Jun 26 16:54:19 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 26 Jun 2003 17:54:19 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <200306261719.07135.fsanta@arrakis.es> References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> <200306261719.07135.fsanta@arrakis.es> Message-ID: <20030626155419.GE26193@meier-geinitz.de> Hi, On Thu, Jun 26, 2003 at 05:19:07PM +0200, fsanta wrote: > Hi. Could anyone tell me how to do this. . ."disabling synchronous transfers > in your SCSI driver or the BIOS..." I've tried to explain that in my other mail: "I don't have your scanner or your card so I don't have personal experiences with this combination. But the "synchronous tranfer" SCSI feature seems to make trouble with many older SCSI scanners. And your kernel complains about it so it may be worth a try. Check the documentation in the Linux source code. Which SCSI driver do you use for the 2904?" I really don't know which SCSI driver you use. Check the README for that SCSI driver or the code itsself. If tell us which driver you use, maybe someone else knows the details. I don't think your SCSI adapter has a BIOS. But it's your hardware so you should know better :-) Bye, Henning From a.deuring at satzbau-gmbh.de Thu Jun 26 18:09:10 2003 From: a.deuring at satzbau-gmbh.de (abel deuring) Date: Thu, 26 Jun 2003 19:09:10 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 References: <200306251705.27766.fsanta@arrakis.es> <20030625152250.GA9836@meier-geinitz.de> <200306261719.07135.fsanta@arrakis.es> <20030626155419.GE26193@meier-geinitz.de> Message-ID: <3EFB28B6.E1B6AE83@satzbau-gmbh.de> Henning Meier-Geinitz wrote: > > Hi, > > On Thu, Jun 26, 2003 at 05:19:07PM +0200, fsanta wrote: > > Hi. Could anyone tell me how to do this. . ."disabling synchronous transfers > > in your SCSI driver or the BIOS..." > > I've tried to explain that in my other mail: > > "I don't have your scanner or your card so I don't have personal > experiences with this combination. But the "synchronous tranfer" SCSI > feature seems to make trouble with many older SCSI scanners. And your > kernel complains about it so it may be worth a try. Check the > documentation in the Linux source code. Which SCSI driver do you use > for the 2904?" > > I really don't know which SCSI driver you use. Check the README for > that SCSI driver or the code itsself. If tell us which driver you use, > maybe someone else knows the details. > > I don't think your SCSI adapter has a BIOS. But it's your hardware so > you should know better :-) Bad luck, I'm afraid. The Adaptec 2904 needs the aic7xxx driver, and that driver has no parameter "disable disconnect". At least the file README.aic7xxx from the Linux 2.4.18 kernel does not mention such an option. Abel From adeuring at gmx.net Thu Jun 26 20:58:59 2003 From: adeuring at gmx.net (abel deuring) Date: Thu, 26 Jun 2003 21:58:59 +0200 Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: References: Message-ID: <3EFB5083.3090208@gmx.net> Henrik Schmidt schrieb: > I'm trying to use a Microtek ScanMaker III with Solaris 2.6 and the scg > SCSI driver. I'm using sane-backends 1.0.12 with frontend 1.0.10. > > Jun 25 13:08:25 cortex unix: WARNING: > /iommu at f,e0000000/sbus at f,e0001000/espdma at f > ,400000/esp at f,800000 (esp0):^M^M > Jun 25 13:08:25 cortex unix: data transfer overrun: current esp state: ^^^^^^^^^^^^^^^^^^^^^ [...] > Jun 25 13:08:25 cortex unix: esp: Cmd dump for Target 5 Lun > 0:^M^M > Jun 25 13:08:25 cortex unix: esp: cdblen=6, cdb=[ 0x8 0x0 > 0x0 0x0 > 0x91 0x0 ]^M^M That's a READ of just 0x91 (145) bytes; shouldn't cause any buffer overflow, but it's an odd number of bytes. A long shot: It could be that the SCG driver does not like to transfer an odd number of bytes. Matt and Henrik, I'm admittedly too lazy to look closer into the Microtek backend, but I guess that it is trying to read a complete scan line with one SCSI command. Would it be difficult to change this behaviour to read an even number of bytes? Henrik, a test of my guess should not be too difficult: Just select a scan window with an even number of horizontal pixels. (Or perhaps better choose a multiple of 4 or 8 as the scan width, just in case that the SCG driver or some other Solaris part insists on using the complete bus width of 32 or 64 bit) Abel PS: If my guess is right, a number of backends would need to be modified, I'm afraid... From pinguellis at yahoo.co.uk Thu Jun 26 22:08:53 2003 From: pinguellis at yahoo.co.uk (Steven Ellis) Date: Thu, 26 Jun 2003 14:08:53 -0700 (PDT) Subject: [sane-devel] Visioneer 5800 In-Reply-To: <20030626074435.GB26193@meier-geinitz.de> Message-ID: <20030626210853.80375.qmail@web80512.mail.yahoo.com> --- Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 26, 2003 at 01:30:22AM +0000, > jollyprince at juno.com wrote: > > I'm a newbie who just got his USB printer working > and decided to > > tackle the scanner next. So far I've found the > Vendor number and > > Product ID and inserted them into the modules.conf > file. > > The scanner isn't even in our list of scanners. That > usually means it > is not supported by any SANE backend. This is a 48bit scanner and as such won't work with the viceo backend (http://viceo.orcon.net.nz) that supports E3 and E4 chipset families. Its probably E5 which appears to be LM9832 based but you will need to open your scanner to confirm this. Steve ===== -- If you listen very carefully you can sometimes hear the dolphins sing pinguellis at yahoo.co.uk __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From pinguellis at yahoo.co.uk Thu Jun 26 22:10:26 2003 From: pinguellis at yahoo.co.uk (Steven Ellis) Date: Thu, 26 Jun 2003 14:10:26 -0700 (PDT) Subject: [sane-devel] Tips on migrating an existing driver to use libusb? Message-ID: <20030626211026.45297.qmail@web80511.mail.yahoo.com> Are there any useful tips or an FAQ on migrating a scanner driver over to use libusb. It would be nice to get the viceo (http://viceo.orcon.net.nz) driver to work without using a special patch for scanner.c/h and a recompile of the modules. Steve ===== -- If you listen very carefully you can sometimes hear the dolphins sing pinguellis at yahoo.co.uk __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com From gnawa at libero.it Thu Jun 26 22:58:11 2003 From: gnawa at libero.it (gnawa) Date: Thu, 26 Jun 2003 23:58:11 +0200 Subject: [sane-devel] hi! Message-ID: <200306262358.11927.gnawa@libero.it> hi to all! i'm a italian guy (with poor english...) and i'm going to do the biggest thing that i ever programmed... a driver for my scanner hp scanjet 2300c ...but i have no idea from where to begin :( so if anyone can help me... thank you gnawa ps in italian: se c'? qualche italiano che pu? aiutarmi (non con l'inglese...) in questa impresa o l'ha gi? cominciata o esiste gi? un driver funzionante per il mio scanner gli sar? molto grato... anche solo per dirmi con cosa cominciare... ciao From henning at meier-geinitz.de Thu Jun 26 22:56:39 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 26 Jun 2003 23:56:39 +0200 Subject: [sane-devel] Tips on migrating an existing driver to use libusb? In-Reply-To: <20030626211026.45297.qmail@web80511.mail.yahoo.com> References: <20030626211026.45297.qmail@web80511.mail.yahoo.com> Message-ID: <20030626215639.GC902@meier-geinitz.de> Hi, On Thu, Jun 26, 2003 at 02:10:26PM -0700, Steven Ellis wrote: > Are there any useful tips or an FAQ on migrating a > scanner driver over to use libusb. It would be nice to > get the viceo (http://viceo.orcon.net.nz) driver to > work without using a special patch for scanner.c/h and > a recompile of the modules. I don't have a howto but the sanei_usb API is pretty simple and explained here: http://sanei.meier-geinitz.de/sanei__usb_8h.html The assumptions are: - not more than one endpoint of each type: bulk-in, bulk-out, interrupt - interrupt endpoint access works only with libusb 1) sanei_usb_init 2a) call sanei_usb_attach_matching_devices with the "usb" lined from your config file or 2b) call sanei_usb_find_devices for any of the scanners you support 3) sanei_usb_open the device that was selected by the user 4) call sanei_usb_read_bulk, write_bulk or control_msg as you need 5) sanei_usb_close Bye, Henning From cpinto at yimports.com Fri Jun 27 02:31:03 2003 From: cpinto at yimports.com (Celso Pinto) Date: 27 Jun 2003 02:31:03 +0100 Subject: [sane-devel] HP2300C Message-ID: <1056677463.8138.11.camel@cpinto> Hi all, finally I had some time to get into the research/development of a driver for HP 2300C scanner. Because I have no experience in development for Linux/SANE drivers, I was wondering if there's some kind of HOWTO or a quick crash course for developing scanner drivers. I downloaded a couple of other projects but they fail as a tutorial because there isn't much "green code" (source comments) on them and i'm having a really hard time trying to figure out what those lines of code are supposed to do. Can anyone please help? I already have USB log file for scanning an image so i'm really keen on getting my hands dirty. Also, I noticed all projects use C instead of C++. Is there a major reason for this? Thanks for your time, Celso From kleptog at svana.org Fri Jun 27 03:05:34 2003 From: kleptog at svana.org (Martijn van Oosterhout) Date: Fri, 27 Jun 2003 12:05:34 +1000 Subject: [sane-devel] HP2300C In-Reply-To: <1056677463.8138.11.camel@cpinto> References: <1056677463.8138.11.camel@cpinto> Message-ID: <20030627020534.GD15876@svana.org> On Fri, Jun 27, 2003 at 02:31:03AM +0100, Celso Pinto wrote: > Hi all, > > finally I had some time to get into the research/development of a driver > for HP 2300C scanner. > > Because I have no experience in development for Linux/SANE drivers, I > was wondering if there's some kind of HOWTO or a quick crash course for > developing scanner drivers. I downloaded a couple of other projects but > they fail as a tutorial because there isn't much "green code" (source > comments) on them and i'm having a really hard time trying to figure out > what those lines of code are supposed to do. Well, I basically pulled up the driver for one of the other HP scanners. I pinched the code (with acknowledgements of course) that read the config file, accessed the USB device and implemented the SANE API. That meant I only had to write code to implement the actual protocol. Initially you'll have lots of constants as you try to replicate the various protocol elrement. I suggest working as a standalone program until you at least pull down a preview image. That saves you the hassle of dealing with the SANE interface until you actually have image to show. > Also, I noticed all projects use C instead of C++. Is there a major > reason for this? Until recently the C++ compilers have been slightly flakey. Straight C tends to be more portable too. Historical accident mostly. Good luck! Hope this helps, -- Martijn van Oosterhout http://svana.org/kleptog/ > "the West won the world not by the superiority of its ideas or values or > religion but rather by its superiority in applying organized violence. > Westerners often forget this fact, non-Westerners never do." > - Samuel P. Huntington -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: From fsanta at arrakis.es Fri Jun 27 06:54:03 2003 From: fsanta at arrakis.es (fsanta) Date: Fri, 27 Jun 2003 07:54:03 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <20030626155419.GE26193@meier-geinitz.de> References: <200306251705.27766.fsanta@arrakis.es> <200306261719.07135.fsanta@arrakis.es> <20030626155419.GE26193@meier-geinitz.de> Message-ID: <200306270754.03409.fsanta@arrakis.es> Hi Henning I fully understand that you don't have my scenner combination. I don't think anyone else has anymore apart from perhaps the writer of the Xsane frontend. I posted to the list on the off chance that others may be able to help me. As Sane has matured there seem to be fewer and fewer people subscribed to the list. My driver is the aic7xxx and it works fine under SuSE 8.1 Cheers, Steve. On Thursday 26 June 2003 17:54, Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 26, 2003 at 05:19:07PM +0200, fsanta wrote: > > Hi. Could anyone tell me how to do this. . ."disabling synchronous > > transfers in your SCSI driver or the BIOS..." > > I've tried to explain that in my other mail: > > "I don't have your scanner or your card so I don't have personal > experiences with this combination. But the "synchronous tranfer" SCSI > feature seems to make trouble with many older SCSI scanners. And your > kernel complains about it so it may be worth a try. Check the > documentation in the Linux source code. Which SCSI driver do you use > for the 2904?" > > I really don't know which SCSI driver you use. Check the README for > that SCSI driver or the code itsself. If tell us which driver you use, > maybe someone else knows the details. > > I don't think your SCSI adapter has a BIOS. But it's your hardware so > you should know better :-) > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From kouno.hironori at pfu.fujitsu.com Fri Jun 27 08:48:38 2003 From: kouno.hironori at pfu.fujitsu.com (hironori kohno) Date: Fri, 27 Jun 2003 16:48:38 +0900 Subject: [sane-devel] [sane-devel]The report about 'sane-fujitsu' Message-ID: <200306271648.FEE65799.SOPPLP.PVJSIJO@pfu.fujitsu.com> Hi, I performed testing about 'sane-fujitsu'. It reports below. OS: RedHat Linux V8 Scanner: fi-4220C Indication matters: 1. color-mode When scan is carried out by color-mode, the information on a color differs from an actual manuscript. ex.A red paper is expressed as a yellow picture. 2. resolution A maximum of 600 dpi is appropriate to x resolution of fi-4x20 scanner. The maximum of y resolution can be specified to 600dpi. 3. rif (reverse image format) i want you to support not by rif but by SANE_NAME_NEGATIVE. i do not set up by rif of scanner I/F, but want you to be reversed to an actual picture color. 4. halftone-mode A picture cannot be taken even if it specifies the mode of halftone. 5. paper-size "A3" and "double" are not supporting. 6. Start button How to use start-button is not known. Bye, Kouno -- kouno.hironori at pfu.fujitsu.com -- kouno.hironori at pfu.fujitsu.com From henning at meier-geinitz.de Fri Jun 27 09:38:32 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 10:38:32 +0200 Subject: [sane-devel] umax 2200 scsi no go under SuSE-8.2 In-Reply-To: <200306270754.03409.fsanta@arrakis.es> References: <200306251705.27766.fsanta@arrakis.es> <200306261719.07135.fsanta@arrakis.es> <20030626155419.GE26193@meier-geinitz.de> <200306270754.03409.fsanta@arrakis.es> Message-ID: <20030627083832.GA2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 07:54:03AM +0200, fsanta wrote: > I fully understand that you don't have my scenner combination. I don't think > anyone else has anymore apart from perhaps the writer of the Xsane frontend. > I posted to the list on the off chance that others may be able to help me. As > Sane has matured there seem to be fewer and fewer people subscribed to the > list. 580 subscribers currently + 133 getting the digest. > My driver is the aic7xxx and it works fine under SuSE 8.1 There are two aic7xxx drivers. In 2.4.21 they are called aic7xxx and aic7xxx_old. Maybe SuSE 8.1 used the older driver? Maybe you can load it instead of the other one? Bye, Henning From henning at meier-geinitz.de Fri Jun 27 09:42:32 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 10:42:32 +0200 Subject: [sane-devel] hi! In-Reply-To: <200306262358.11927.gnawa@libero.it> References: <200306262358.11927.gnawa@libero.it> Message-ID: <20030627084232.GB2318@meier-geinitz.de> Hi, On Thu, Jun 26, 2003 at 11:58:11PM +0200, gnawa wrote: > i'm a italian guy (with poor english...) and i'm going to do the biggest thing > that i ever programmed... a driver for my scanner hp scanjet 2300c > ...but i have no idea from where to begin :( so if anyone can help me... Some hours after your posting Celso Pinto wrote to sane-devel that he wants to start a backend: http://www.mostang.com/pipermail/sane-devel/2003-June/019271.html So maybe you can work together on this project? Bye, Henning From henning at meier-geinitz.de Fri Jun 27 10:26:41 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 11:26:41 +0200 Subject: [sane-devel] HP2300C In-Reply-To: <1056677463.8138.11.camel@cpinto> References: <1056677463.8138.11.camel@cpinto> Message-ID: <20030627092641.GC2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 02:31:03AM +0100, Celso Pinto wrote: > finally I had some time to get into the research/development of a driver > for HP 2300C scanner. "gnawa" also wants to write a driver for this scanner, see http://www.mostang.com/pipermail/sane-devel/2003-June/019269.html . Maybe you can help each other? > Because I have no experience in development for Linux/SANE drivers, I > was wondering if there's some kind of HOWTO or a quick crash course for > developing scanner drivers. Not really. General documentation and some tips are in doc/backend-writing.txt. I also think you should start with a simple program that inncludes sanei_usb.c. You can do the SANE interface stuff later. The sanei internal functions are explained here: http://sanei.meier-geinitz.de/ > I downloaded a couple of other projects but > they fail as a tutorial because there isn't much "green code" (source > comments) on them and i'm having a really hard time trying to figure out > what those lines of code are supposed to do. * in sane_init, read the config file and detect the available scanners * in sane_open, do any preliminary work like loading the firmware, heating up the lamp * in sane_start start the actual scan (e.g. set up the geometry, do calibration, start the scan slider) * in sane_read get the scan data * sane_cancel stops the scan and resets everything necesary in the scanner Could you identify which chipset this scanner uses? Could you add some testing code to the check-usb-scanner utility at http://www.meier-geinitz.de/sane/check-usb-scanner/ ? That way we could identify other similar scanners easier. > Can anyone please help? I already have USB log file for scanning an > image so i'm really keen on getting my hands dirty. Try to find out what the USB log means, e.g. which part are commands, which are data. Try to send them from Linux and check if they do what you think. > Also, I noticed all projects use C instead of C++. Is there a major > reason for this? I don't think C++ was wiedely used when SANE was born. C++ is just too young. To many incompatibilities and interface changes. We'd need compatible C++ compilers on all platforms supported by SANE. Even with C, there are quite some portability problems, I don't want to know hwt would happen if we used C++. Bye, Henning From jollyprince at juno.com Fri Jun 27 12:04:15 2003 From: jollyprince at juno.com (jollyprince at juno.com) Date: Fri, 27 Jun 2003 11:04:15 GMT Subject: [sane-devel] What next? Message-ID: <20030627.040444.754.120095@webmail06.lax.untd.com> [root at localhost roger]# scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). [root at localhost roger]# sane-find-scanner found USB scanner (vendor=0x04a7, product=0x0226) at libusb:005:002 # A USB device was detected. This program can't be sure if it's really # a scanner. If it is your scanner, it may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. NOTE: "scanimage -L" finds no scanners and suggests that I run "sane-find-scanner" which identifies vendor as 0x04a7 (Visioneer) and product as 0x0226 (Model 5800). When I run xsane, it says no devices available. So I've come a long way but no cigar. HELP! From henning at meier-geinitz.de Fri Jun 27 12:35:22 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 13:35:22 +0200 Subject: [sane-devel] What next? In-Reply-To: <20030627.040444.754.120095@webmail06.lax.untd.com> References: <20030627.040444.754.120095@webmail06.lax.untd.com> Message-ID: <20030627113522.GF2318@meier-geinitz.de> Hi, there is no need to send a copy of every email to me, I'm reading the sane-devel list. On Fri, Jun 27, 2003 at 11:04:15AM +0000, jollyprince at juno.com wrote: > [root at localhost roger]# scanimage -L [not found] > [root at localhost roger]# sane-find-scanner > > found USB scanner (vendor=0x04a7, product=0x0226) at libusb:005:002 Ok. > NOTE: "scanimage -L" finds no scanners and suggests that I run > "sane-find-scanner" which identifies vendor as 0x04a7 (Visioneer) and > product as 0x0226 (Model 5800). Yes, that's ok. sane-find-scanner should find every scanner. > When I run xsane, it says no devices available. So I've come a long > way but no cigar. HELP! You'll get the cigar when you have written the SANE driver for this scanner. As mentioned in my previous mail, there is most probably no driver yet for this scanner. For writing a driver see: http://www.meier-geinitz.de/sane/misc/unsupported.html Even if you don't want to write a driver, please show us the output of "cat /proc/bus/usb/devices" when your scanner is plugged in. Bye, Henning From hbs at ks.informatik.uni-kiel.de Fri Jun 27 12:37:58 2003 From: hbs at ks.informatik.uni-kiel.de (Henrik Schmidt) Date: Fri, 27 Jun 2003 13:37:58 +0200 (MEST) Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: <3EFB5083.3090208@gmx.net> References: <3EFB5083.3090208@gmx.net> Message-ID: On Thu, 26 Jun 2003, abel deuring wrote: > Henrik Schmidt schrieb: > > I'm trying to use a Microtek ScanMaker III with Solaris 2.6 and the scg > > SCSI driver. I'm using sane-backends 1.0.12 with frontend 1.0.10. > > > > > Jun 25 13:08:25 cortex unix: WARNING: > > /iommu at f,e0000000/sbus at f,e0001000/espdma at f > > ,400000/esp at f,800000 (esp0):^M^M > > Jun 25 13:08:25 cortex unix: data transfer overrun: current esp state: > ^^^^^^^^^^^^^^^^^^^^^ > [...] > > Jun 25 13:08:25 cortex unix: esp: Cmd dump for Target 5 Lun > > 0:^M^M > > Jun 25 13:08:25 cortex unix: esp: cdblen=6, cdb=[ 0x8 0x0 > > 0x0 0x0 > > 0x91 0x0 ]^M^M > > That's a READ of just 0x91 (145) bytes; shouldn't cause any buffer > overflow, but it's an odd number of bytes. A long shot: It could be that > the SCG driver does not like to transfer an odd number of bytes. > > Matt and Henrik, I'm admittedly too lazy to look closer into the > Microtek backend, but I guess that it is trying to read a complete scan > line with one SCSI command. Would it be difficult to change this > behaviour to read an even number of bytes? > > Henrik, a test of my guess should not be too difficult: Just select a > scan window with an even number of horizontal pixels. (Or perhaps better > choose a multiple of 4 or 8 as the scan width, just in case that the SCG > driver or some other Solaris part insists on using the complete bus > width of 32 or 64 bit) > I did test and get the same error with a very small 8x12 scan window. -- Henrik Schmidt Christian-Albrechts-Universitaet zu Kiel Institut fuer Informatik +49 (431) 880 75 - 50 Fax or 43 Phone Olshausenstr. 40 http://www.ks.informatik.uni-kiel.de 24098 Kiel, Germany email: hbs at ks.informatik.uni-kiel.de From henning at meier-geinitz.de Fri Jun 27 13:12:55 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 14:12:55 +0200 Subject: [sane-devel] What next? In-Reply-To: <20030627.070149.1480.0.jollyprince@juno.com> References: <20030627.070149.1480.0.jollyprince@juno.com> Message-ID: <20030627121255.GG2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 07:01:49AM -0500, Roger O Wales wrote: > If it's possible to use libusb instead of spedific scanner modules > wouldn't this be quicker and if so, how does one proceed? I guess that may be of interest for the mailing list so I'm cc'ing it. Generally speaking, it should be possible to access any scanner using libusb. libusb is just a way to access the generic USB driver in usbfs. How do you do it? Just unload any specific drivers (rmmod scanner) and make sure that the kernel has support for the "Preliminary USB device filesystem" and that filesystem in mounted. That's the default for most distributions nowerdays. For access as non-root, see man sane-usb. But usually libusb or the kernel scanner driver is not the problem. What is needed is a SANE driver for the specific scanner. It doesn't matter if libusb or the scanner driver is used in most situations. Bye, Henning From hshane at austin.rr.com Fri Jun 27 13:14:23 2003 From: hshane at austin.rr.com (Howard Shane) Date: Fri, 27 Jun 2003 07:14:23 -0500 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP References: Message-ID: <3EFC351F.50508@austin.rr.com> I've visited the libusb site, and the only documentation available seems to be for developers. If someone can point me to more user-oriented information I'll be happy to include it. I assume it's out of the beta phase? Are there distribution manufacturers including it in their stable branches of binaries? Thanks, hs m. allan noah wrote: > it seems to me, that if you want your document to be more future-proof, > you would spend some more time talking about using libusb instead of the > kernel scanner driver, which is likely to be removed in later kernels (as > libusb becomes more stable) > > until then, i would likely re-name section 3 to 'OS support' instead of > kernel support, and make two usb entries, one for kernel and one for > libusb. > > then, to keep things consistent, you would have to add a libusb section to > 4.2. > > allan > > On Tue, 24 Jun 2003, Howard Shane wrote: > > >>...is available for viewing at >> >>http://66.25.191.66/docs/HOWTOS/Scanner/index.html >> >>I've tried to incorporate everyone's corrections and suggestions >>wherever possible. For any remaining omissions or errata please let me know. >> >>Thanks! >> >>_______________________________________________ >>Sane-devel mailing list >>Sane-devel at www.mostang.com >>http://www.mostang.com/mailman/listinfo/sane-devel >> > > From henning at meier-geinitz.de Fri Jun 27 13:35:14 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 14:35:14 +0200 Subject: [sane-devel] What next? In-Reply-To: <20030627.071830.1480.1.jollyprince@juno.com> References: <20030627.071830.1480.1.jollyprince@juno.com> Message-ID: <20030627123514.GH2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 07:18:30AM -0500, Roger O Wales wrote: > Granting that I'm a newbie which course of action gets me there quickest? If you would quote the part of the mail you are talking about I may understand what you want to achieve :-) And please write to the mailing list, not to me personally. I'm adding a cc: to sane-devel again. So what do you want to achieve? What doesn't work when you do what I told you? What did you do until now? What scanner do you use? Which operating system? Which version of SANE? With supported scanners and recent Linux distributions your USB scanner should just work out-of-the-box. Bye, Henning From henning at meier-geinitz.de Fri Jun 27 14:28:46 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 15:28:46 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EFC351F.50508@austin.rr.com> References: <3EFC351F.50508@austin.rr.com> Message-ID: <20030627132846.GI2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 07:14:23AM -0500, Howard Shane wrote: > I've visited the libusb site, and the only documentation available seems > to be for developers. If someone can point me to more user-oriented > information I'll be happy to include it. I assume it's out of the beta > phase? Are there distribution manufacturers including it in their stable > branches of binaries? As far as I kno all Linux distributions include libusb. Libusb is a library to access generic USB devices. It uses the operating system generic USB driver and how that works exactly depends on the operating system. The only thing the user needs to know is that he can only use libusb access if no other kernel driver is attached to the speicfic device. In case of Linux, that means "rmmod scanner". For permission issues and other details look at man sane-usb. Maybe a pointer to that man page is sufficiant. Bye, Henning From till.kamppeter at gmx.net Fri Jun 27 14:50:58 2003 From: till.kamppeter at gmx.net (Till Kamppeter) Date: Fri, 27 Jun 2003 15:50:58 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EFC351F.50508@austin.rr.com> References: <3EFC351F.50508@austin.rr.com> Message-ID: <3EFC4BC2.1000300@gmx.net> Howard Shane wrote: > I've visited the libusb site, and the only documentation available seems > to be for developers. If someone can point me to more user-oriented > information I'll be happy to include it. I assume it's out of the beta > phase? Are there distribution manufacturers including it in their stable > branches of binaries? Mandrake contains libusb since 9.0 or so. SANE and libgphoto2 of Mandrake Linux 9.1 are compiled with libusb support. To use libusb with binary packages, the "libusb*" package has to be installed with urpmi libusb For compiling programs using libusb you need also the "libusb*-devel" package which can be installed with urpmi libusb-devel I don?t have info about other distros (I work as developer at MandrakeSoft), but if Debian ships libusb my guess is that one installs it with apt-get install libusb apt-get install libusb-dev I hope this helps. Till From jollyprince at juno.com Fri Jun 27 16:43:46 2003 From: jollyprince at juno.com (Roger O Wales) Date: Fri, 27 Jun 2003 10:43:46 -0500 Subject: [sane-devel] What next? Message-ID: <20030627.104346.1436.0.jollyprince@juno.com> On Fri, 27 Jun 2003 14:35:14 +0200 Henning Meier-Geinitz writes: > Hi, > > On Fri, Jun 27, 2003 at 07:18:30AM -0500, Roger O Wales wrote: > > Granting that I'm a newbie which course of action gets me there > quickest? > > If you would quote the part of the mail you are talking about I may > understand what you want to achieve :-) And please write to the > mailing list, not to me personally. I'm adding a cc: to sane-devel > again. I get it. I've been replying to the sender instead of sane-devl.. > So what do you want to achieve? What doesn't work when you do what > I told you? What did you do until now? What scanner do you use? Which > operating system? Which version of SANE? I can answer a few of your questions. I use Visioneer OneTouch 5800 on a Mandrake 9.1 operating system. I have a scanner0 at /dev/usb I believe I hace an unsupported scanner. sane-find-scanner found USB scanner vendor=0x04a7 (Visioneer) and product=0x0226 (Model 5800). I have inserted these into /etc/modules.conf. > With supported scanners and recent Linux distributions your USB scanner should just work out-of-the-box. Since I don't have that luxury, I have to choose to write a SANE driver for Visioneer 5800 or try to use a generic libusb driver. I don't know how to do either one of these, so I must call for HELP! From henning at meier-geinitz.de Fri Jun 27 17:24:16 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 18:24:16 +0200 Subject: [sane-devel] What next? In-Reply-To: <20030627.104346.1436.0.jollyprince@juno.com> References: <20030627.104346.1436.0.jollyprince@juno.com> Message-ID: <20030627162416.GK2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 10:43:46AM -0500, Roger O Wales wrote: > > So what do you want to achieve? What doesn't work when you do what > > I told you? What did you do until now? What scanner do you use? Which > > operating system? Which version of SANE? > > I can answer a few of your questions. I use Visioneer OneTouch 5800 on a > Mandrake 9.1 operating system. That one is unsupported by SANE as far as we know. > I have a scanner0 at /dev/usb I believe > I hace an unsupported scanner. sane-find-scanner found USB scanner > vendor=0x04a7 (Visioneer) and product=0x0226 (Model 5800). Ok, so the kernel has detected it. That's ok. > I have inserted these into /etc/modules.conf. Ok, but probably not necessary. > > With supported scanners and recent Linux distributions your USB scanner > should just work out-of-the-box. > > Since I don't have that luxury, I have to choose to write a SANE driver > for Visioneer 5800 or try to use a generic libusb driver. No, you don't have these choice. You (or someone else) must write a SANE driver (backend). That backend uses either libusb or the kernel scanner driver. So definitely need a SANE backend for every scanner. libusb and the kernel scanner driver just provide the means to contact the scanner. All the "intelligent" work is done in the backend. > I don't know how to do either one of these, so I must call for HELP! Well, see the discussions on this list and: http://www.meier-geinitz.de/sane/misc/unsupported.html Bye, Henning From maddog at mir.com Fri Jun 27 17:57:59 2003 From: maddog at mir.com (Matto Marjanovic) Date: Fri, 27 Jun 2003 12:57:59 -0400 Subject: [sane-devel] Scsi problem with Solaris 2.6 In-Reply-To: <3EFB5083.3090208@gmx.net> (message from abel deuring on Thu, 26 Jun 2003 21:58:59 +0200) References: <3EFB5083.3090208@gmx.net> Message-ID: <1191-Fri27Jun2003125759-0400-maddog@yoo-hoo.ai.mit.edu> Hi, Henrik, Abel, I'm catching up on this thread, too. (When I first received the bug report, I was at the tail-end of finishing a Ph.D. Don't expect too much more attention just yet -- now I am on vacation. :) >> Jun 25 13:08:25 cortex unix: esp: Cmd dump for Target 5 Lun 0: >> Jun 25 13:08:25 cortex unix: esp: cdblen=6, cdb=[ 0x8 0x0 0x0 0x0 0x91 0x0 ] > >That's a READ of just 0x91 (145) bytes; shouldn't cause any buffer >overflow, but it's an odd number of bytes. A long shot: It could be that >the SCG driver does not like to transfer an odd number of bytes. Actually, it's a read of 145 *scanlines*, each of which is 900 bytes (in this case). That's what the 0x8 command means to these scanners. That makes 145 * 900 = 130500 bytes total, just under the 128k limit. >Matt and Henrik, I'm admittedly too lazy to look closer into the >Microtek backend, but I guess that it is trying to read a complete scan And I am too lazy to look at the SCG driver to see what it does. Henrik, is there some more debugging you can enable in the kernel driver so that we can see what it was doing *before* the error condition? The implementation of sanei_scsi_cmd2() for the SOLARIS_SG_INTERFACE looks incomplete: it makes no reference to the sense handler, and it simply returns SANE_STATUS_IO_ERROR for all error conditions. (Thus, there is no way to access any sense data.) Plus, it has no DBG()'s! The logfile from the microtek backend is not very revealing: simply an indeterminate SCSI error during the first read command. Maybe this is one of those BUSY conditions (the scanner is still scanning 145 lines?), and the SCG driver is returning a busy signal/error instead of retrying the command itself? -matt m. From hshane at austin.rr.com Fri Jun 27 19:01:02 2003 From: hshane at austin.rr.com (Howard Shane) Date: Fri, 27 Jun 2003 13:01:02 -0500 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP References: <3EFC351F.50508@austin.rr.com> <20030627132846.GI2318@meier-geinitz.de> Message-ID: <3EFC865E.9040107@austin.rr.com> Wow, guess I'm behind the times...maybe its time I upgraded from Debian woody, as it might be another few years before the project issues a major upgrade. :-/ Henning Meier-Geinitz wrote: > As far as I kno all Linux distributions include libusb. Libusb is a > library to access generic USB devices. It uses the operating system > generic USB driver and how that works exactly depends on the operating > system. > > The only thing the user needs to know is that he can only use libusb > access if no other kernel driver is attached to the speicfic device. > In case of Linux, that means "rmmod scanner". For permission issues > and other details look at man sane-usb. Maybe a pointer to that man > page is sufficiant. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From anoah at pfeiffer.edu Fri Jun 27 19:26:03 2003 From: anoah at pfeiffer.edu (m. allan noah) Date: Fri, 27 Jun 2003 14:26:03 -0400 (EDT) Subject: [sane-devel] [sane-devel]The report about 'sane-fujitsu' In-Reply-To: <200306271648.FEE65799.SOPPLP.PVJSIJO@pfu.fujitsu.com> Message-ID: you use old version of sane. remove redhat version of sane-backend: rpm -e --force --nodeps sane-backend and re-install sane: ./configure --prefix=/usr --sysconfdir=/etc make make install see below for more comments On Fri, 27 Jun 2003, hironori kohno wrote: > Hi, > > I performed testing about 'sane-fujitsu'. > It reports below. > > OS: RedHat Linux V8 > Scanner: fi-4220C > > Indication matters: > > 1. color-mode > When scan is carried out by color-mode, the information > on a color differs from an actual manuscript. > ex.A red paper is expressed as a yellow picture. > yes 4x20 uses BGR color, fixed in current cvs version. > 2. resolution > A maximum of 600 dpi is appropriate to x resolution of > fi-4x20 scanner. > The maximum of y resolution can be specified to 600dpi. > yes, currently backend uses the capabilites of the M3091 as default. if you want to update code to use vpd instead, that would be good. > 3. rif (reverse image format) > i want you to support not by rif but by SANE_NAME_NEGATIVE. > i do not set up by rif of scanner I/F, but want you to be > reversed to an actual picture color. > sorry, i do not understand. > 4. halftone-mode > A picture cannot be taken even if it specifies the mode of > halftone. yes, also because of incorrect defaults. > > 5. paper-size > "A3" and "double" are not supporting. incorrect defaults i think. though from the interface manual of the scanner, fi-4x20 does not support setting the paper size. must be set to 0xC0. would have to use --paperheight and --paperwidth inside the backend to fake paper size setting? > > 6. Start button > How to use start-button is not known. > cannot be used in sane. there is no portion of the sane api for accessing status of control panel. i have used an external program. allan > Bye, > Kouno > > -- > kouno.hironori at pfu.fujitsu.com > > -- > kouno.hironori at pfu.fujitsu.com > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > -- "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 From gnawa at libero.it Fri Jun 27 20:31:12 2003 From: gnawa at libero.it (gnawa) Date: Fri, 27 Jun 2003 21:31:12 +0200 Subject: [sane-devel] hi! Message-ID: <200306272131.12053.gnawa@libero.it> Alle 10:42, venerd? 27 giugno 2003, Henning Meier-Geinitz ha scritto: > Some hours after your posting Celso Pinto wrote to sane-devel that he > wants to start a backend: > http://www.mostang.com/pipermail/sane-devel/2003-June/019271.html > > So maybe you can work together on this project? it's a good thing work together with someone who is interested in the same project!so i will talk to Celso Pinto: celso if you want to share info and work with me we can talk about this driver in public, so if someone read about "scanjet 2300c" and wants to help us he can, or in private if you prefer... i need the point from where to start... then the other things will come naturally (poi le cose verranno da sole). thank's to all Gnawa From tomf at sjpc.org Fri Jun 27 20:45:37 2003 From: tomf at sjpc.org (Thomas Frayne) Date: 27 Jun 2003 12:45:37 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030625205240.GA12653@meier-geinitz.de> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> Message-ID: <1056743137.3204.1.camel@localhost.localdomain> On Wed, 2003-06-25 at 13:52, Henning Meier-Geinitz wrote: > Is the scanner found as USB device now? Something like "libusb:001:002"? > > Please show us "sane-find-scanner -q". > > I have to admitt that I'm a bit confused by the backend. It uses USB > interrupt transfers to get the status of the scanner. However that > only works with libusb, not the kernel scanner driver. So I don't > really know why the backend lists "usb /dev/ubs/scanner" in > avision.conf. Maybe the maintainer can enlighten me :-) > > The name "usbdevfs" is obsolete. It's called "usbfs" now. But that's > not your problem. > Usually the config files list all devices and device files the backend > supports. So it doesn't matter if there are additional ones. > > The backend checks for all USB devices anymway, I don't think the > entries in avsion.conf are necessary at all. > rmmod scanner > modprobe scanner vendor=0x03f0 product=0x0801 > Some distributions use(d) /dev/usbscanner, some use /dev/usb/scanner0. > Shouldn't matter in your case. > > > Jun 24 13:37:51 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 > > Jun 24 13:37:51 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. > > That's your scanner. It's ok that it's not "claimed by any active > driver" because in this case it's used by usbfs (libusb). You can also > try to load the USB scanner driver as mentioned above. Then you should > get a message from that driver. > > I recommend to unplug/replug your scanner before any test. Otherwise > it may be confuded by eralier tests. > > > [root at localhost root]# ls -l /dev/usb/scanner0 > > crw-- 1 tom root 180, 48 Jan 30 02:24 > > /dev/usb/scanner0 > > That's ok. YOu can add a link /dev/usb/scanner to that one but I don't > think it's necessary. > > > /proc/bus/usb/devices > > Those entries start with "T:" (topology). > > > 48- 63: usbscanner > > Is loaded but doesn't know about your scanner. > > Bye, > Henning I snipped what now seems taken care of. Here is a summary of the current state: modprobe scanner vendor=0x03f0 product=0x0801 Jun 26 08:05:09 localhost kernel: usb.c: registered new driver usbscanner Jun 26 08:05:09 localhost kernel: scanner.c: USB scanner device (0x03f0/0x0801) now attached to scanner0 Jun 26 08:05:09 localhost kernel: scanner.c: 0.4.12:USB Scanner Driver Modified /usr/local/etc/sane.d/avision.conf to add usb /dev/usb/scanner0 [root at localhost root]# sane-find-scanner found USB scanner (vendor=0x03f0, product=0x0801) at /dev/usb/scanner0 found USB scanner (vendor=0x03f0 [hp], product=0x0801 [hp scanjet 7400c]) at libusb:004:002 [root at localhost root]# scanimage -L No scanners were identified. Hardware Browser found no scanners. Modified /usr/local/etc/sane.d/avision.conf to add usb 0x03f0 0x0801 This made scanimage -L work after rebooting, both in root mode and user mode: device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c flatbed scanner I shutdown, powered off the scanner, rebooted, ran xsane, and started a scan. The scanner hung as before, and the following appeared in messages. Jun 26 11:34:14 localhost modprobe: modprobe: Can't locate module char-major-81 Jun 26 12:11:41 localhost last message repeated 4 times Jun 26 12:11:41 localhost last message repeated 3 times Jun 26 12:18:37 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:18:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 26 12:19:07 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:19:07 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x83 len 22 ret -110 Jun 26 12:19:37 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:19:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 Jun 26 12:20:07 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:20:07 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 Jun 26 12:20:37 localhost kernel: usb_control/bulk_msg: timeout Jun 26 12:20:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -110 I tried to change all occurrences of usbdevfs in my /etc (fstab, hotplug/usb.rc, mtab, rc.d/rc.sysinit, rc.sysinit) to usbfs, but something went wrong, and my system became unbootable. I restored my / and /var partitions. Now I am pretty sure that my problem is in usbdevfs, but I don't know how to fix it. What can I try next? From henning at meier-geinitz.de Fri Jun 27 22:11:10 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 23:11:10 +0200 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <1056743137.3204.1.camel@localhost.localdomain> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> Message-ID: <20030627211110.GM2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 12:45:37PM -0700, Thomas Frayne wrote: > I snipped what now seems taken care of. Here is a summary of the > current state: > > [root at localhost root]# sane-find-scanner > found USB scanner (vendor=0x03f0, product=0x0801) at /dev/usb/scanner0 > found USB scanner (vendor=0x03f0 [hp], product=0x0801 [hp scanjet 7400c]) at libusb:004:002 So it's detected by the USB scanner driver and libusb. That's ok but you can also try without the USB scanner driver (rmmod scanner). > [root at localhost root]# scanimage -L > No scanners were identified. Try "SANE_DEBUG_AVISION=255 scanimage -L" to find out why it isn't found. Also unplug/replug your scanner to make sure it isn't confused by earlier tests. > Hardware Browser found no scanners. I don't know what you mean by "hardware browser" but as sane-find-scanner finds the scanner twice, I think that "harware browser" program is broken :-) > Modified /usr/local/etc/sane.d/avision.conf to add usb 0x03f0 0x0801 Ok. Shouldn't be necessary, but shouldn't harm either. > This made scanimage -L work after rebooting, Rebooting shouldn't be ever necessary. But if your scanner hangs, unplugging it may help. > both in root mode and user mode: > > device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c > flatbed scanner Ok. > I shutdown, powered off the scanner, rebooted, ran xsane, Make sure that when you run xsane you use the "/dev/usb/scanner0" or the "libusb:something" device and not the "/dev/sg0" device. Just to be sure that xsane doesn't do anything bad. > and started a scan. Try scanning with scanimage and debugging enabled, e.g. SANE_DEBUG_AVISION=255 scanimage >image.pnm 2>log > The scanner hung as before, and the following appeared in > messages. > Jun 26 12:18:37 localhost kernel: usb_control/bulk_msg: timeout > Jun 26 12:18:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 This time you don't have loaded the scanner driver. Did you try with the scanner driver instead? > I tried to change all occurrences of usbdevfs in my /etc (fstab, That's just the name, it doesn't matter (for now). > hotplug/usb.rc, mtab, rc.d/rc.sysinit, rc.sysinit) to usbfs, but > something went wrong, and my system became unbootable. I restored my / > and /var partitions. I think you only need to change /etc/fstab. > Now I am pretty sure that my problem is in usbdevfs, but I don't know > how to fix it. I don't think so. The timeouts occur because the scanner doesn't understand something the backend sends. That may be a backend broblem or something odd in the USB system. > What can I try next? Try the scanner driver. If it shows the same behaviour, you are sure that it's not usbfs. Otherwise, well, wait until the avision maintainer shows up again :-) Bye, Henning From henning at meier-geinitz.de Fri Jun 27 22:14:15 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 27 Jun 2003 23:14:15 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EFC865E.9040107@austin.rr.com> References: <3EFC351F.50508@austin.rr.com> <20030627132846.GI2318@meier-geinitz.de> <3EFC865E.9040107@austin.rr.com> Message-ID: <20030627211415.GN2318@meier-geinitz.de> Hi, On Fri, Jun 27, 2003 at 01:01:02PM -0500, Howard Shane wrote: > Wow, guess I'm behind the times...maybe its time I upgraded from Debian > woody, as it might be another few years before the project issues a > major upgrade. :-/ Even Woody has libusb. But that version may be too old for current versions of SANE. I haven't checked... Bye, Henning From christoffer at kjoelbaek.dk Sat Jun 28 14:23:08 2003 From: christoffer at kjoelbaek.dk (=?iso-8859-1?Q?Christoffer_Holm_Kj=F8lb=E6k?=) Date: Sat, 28 Jun 2003 15:23:08 +0200 Subject: [sane-devel] sane-find-scanner can find my scanner, but Xsane can't? Message-ID: Hey I have a Canon LiDe30, wich shuold be supported by sane And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0 But, Xsane says, that there is no devices available, why? Kind regards - and thanks in adance Christoffer Kj?lb?k From haidara at gucmed.com Sat Jun 28 16:43:44 2003 From: haidara at gucmed.com (Ayman Haidar) Date: Sat, 28 Jun 2003 11:43:44 -0400 Subject: [sane-devel] (no subject) Message-ID: <200306281143.45082.haidara@gucmed.com> Hello, I would greatly appreciate if you could recommend a scanner that works with sane, has an ADF and fairly decent scanning speed. I need to use it in the office and we might scan about 50-100 documents daily. Thanks -- Ayman From henning at meier-geinitz.de Sat Jun 28 16:51:03 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 17:51:03 +0200 Subject: [sane-devel] sane-find-scanner can find my scanner, but Xsane can't? In-Reply-To: References: Message-ID: <20030628155103.GA10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 03:23:08PM +0200, Christoffer Holm Kj?lb?k wrote: > I have a Canon LiDe30, wich shuold be supported by sane It is, but the comment says "Poor color picture quality". > And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0 Ok, so it was found by the kernel scanner driver. > But, Xsane says, that there is no devices available, why? Without further details, nobody knows. Maybe your version of SANE is too old? If this is not the case, you could try sane-troubleshoot to find out what's wrong: http://www.meier-geinitz.de/sane/sts/ Bye, Henning From christoph.knauer at web.de Sat Jun 28 16:57:47 2003 From: christoph.knauer at web.de (Christoph Knauer) Date: 28 Jun 2003 17:57:47 +0200 Subject: [sane-devel] negative-scan Message-ID: <1056815865.14723.11.camel@christoph.local> Hi, i've a litle problem with scanning negatives on an microtek scanmaker x6 / phantom 636 with lightlid35 when i set the option using lightlit or toggle lamp. with "toggle the lamp" the scannerlam goes out, but when i push the button scan, it goes on again, and setting "use lightlid35" seems to do nothing. btw. why there is no "negativ"-format to set for preview? greetings, christoph From tomf at sjpc.org Sat Jun 28 17:00:21 2003 From: tomf at sjpc.org (Thomas Frayne) Date: 28 Jun 2003 09:00:21 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030627211110.GM2318@meier-geinitz.de> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> Message-ID: <1056816020.3271.53.camel@localhost.localdomain> On Fri, 2003-06-27 at 14:11, Henning Meier-Geinitz wrote: ... > > > Modified /usr/local/etc/sane.d/avision.conf to add usb 0x03f0 0x0801 > > Ok. Shouldn't be necessary, but shouldn't harm either. > > > This made scanimage -L work after rebooting, > > Rebooting shouldn't be ever necessary. But if your scanner hangs, > unplugging it may help. Next time the scanner hangs, I'll try unplugging without rebooting. The procedure that made scanimage -L work was done after unplugging and before starting xsane, so I think that the avision.conf change really was necessary. > > > both in root mode and user mode: > > > > device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c > > flatbed scanner > > Ok. > > > I shutdown, powered off the scanner, rebooted, ran xsane, > > Make sure that when you run xsane you use the "/dev/usb/scanner0" or > the "libusb:something" device and not the "/dev/sg0" device. Just to > be sure that xsane doesn't do anything bad. > > > and started a scan. > > Try scanning with scanimage and debugging enabled, e.g. > SANE_DEBUG_AVISION=255 scanimage >image.pnm 2>log OK. I'll set the debugging mode. I'll also try with scanimage to see if I can isolate the problem to xsane. > > > The scanner hung as before, and the following appeared in > > messages. > > Jun 26 12:18:37 localhost kernel: usb_control/bulk_msg: timeout > > Jun 26 12:18:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 > > This time you don't have loaded the scanner driver. Did you try with > the scanner driver instead? I don't understand your question. How do I try with the scanner driver? What is the name of the scanner driver? > > > I tried to change all occurrences of usbdevfs in my /etc (fstab, > > That's just the name, it doesn't matter (for now). > > > hotplug/usb.rc, mtab, rc.d/rc.sysinit, rc.sysinit) to usbfs, but > > something went wrong, and my system became unbootable. I restored my / > > and /var partitions. > > I think you only need to change /etc/fstab. > > > Now I am pretty sure that my problem is in usbdevfs, but I don't know > > how to fix it. > > I don't think so. The timeouts occur because the scanner doesn't > understand something the backend sends. That may be a backend broblem > or something odd in the USB system. > > > What can I try next? > > Try the scanner driver. If it shows the same behaviour, you are sure > that it's not usbfs. > > Otherwise, well, wait until the avision maintainer shows up again :-) > > Bye, > Henning OK. Thanks. I'll try all the suggestions you just made. Please give me more information on running the scanner driver, at least enough so I know what that means, and can look up documentation. Tom From psfales at lucent.com Sat Jun 28 17:37:56 2003 From: psfales at lucent.com (Peter Fales) Date: Sat, 28 Jun 2003 11:37:56 -0500 Subject: [sane-devel] Microtek Pagewiz Message-ID: <20030628163756.GA4381@lucent.com> Anyone know anything about Microtek Pagewiz Color Sheetfed Scanner? http://www.mir.com/mtek/pport-hints.html makes it sound promising, but I wonder if anyone has any direct experience. They are going for well under $10 on eBay. I thik it might be handy if it worked reasonable well with Linux. -- Peter Fales Lucent Technologies, Room 1C-436 N9IYJ 2000 N Naperville Rd PO Box 3033 internet: psfales at lucent.com Naperville, IL 60566-7033 work: (630) 979-8031 From henning at meier-geinitz.de Sat Jun 28 18:25:36 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 19:25:36 +0200 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <1056816020.3271.53.camel@localhost.localdomain> References: <20030623101251.48d212b6.TomF@sjpc.org> <200306241049.46918.moitinho@civil.ist.utl.pt> <20030624104015.7b00f168.TomF@sjpc.org> <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> <1056816020.3271.53.camel@localhost.localdomain> Message-ID: <20030628172536.GC10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 09:00:21AM -0700, Thomas Frayne wrote: > > > The scanner hung as before, and the following appeared in > > > messages. > > > Jun 26 12:18:37 localhost kernel: usb_control/bulk_msg: timeout > > > Jun 26 12:18:37 localhost kernel: usbdevfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -110 > > > > This time you don't have loaded the scanner driver. Did you try with > > the scanner driver instead? > > > I don't understand your question. How do I try with the scanner driver? > What is the name of the scanner driver? Well, in your last mail you told us that you loaded the scanner driver :-) Simplified: There are two ways to access a USB scanner by the kernel: Either by a specific driver for scanners ("kernel USB scanner driver", "scanner.o") or by the generic USB driver ("usbfs", "usbdevfs", "devio", "libusb"). If you load the kernel scanner driver (modprobe scanner) and it detectes your scanner, you can access the scanner only over that kernel scanner driver. If it's not loaded, libusb (usbdevfs) is used. In the kernel messages you get an error "kernel: usbdevfs: USBDEVFS_BULK ..." so I assume the kernel scanner driver was not loaded at that point. If it was and the same error occured, the mssage would come from scanner.c, not from usbdevfs. > OK. Thanks. I'll try all the suggestions you just made. Please give > me more information on running the scanner driver, at least enough so I > know what that means, and can look up documentation. man sane-usb, http://www.meier-geinitz.de/kernel/ Bye, Henning From christoffer at kjoelbaek.dk Sat Jun 28 18:29:55 2003 From: christoffer at kjoelbaek.dk (=?iso-8859-1?Q?Christoffer_Holm_Kj=F8lb=E6k?=) Date: Sat, 28 Jun 2003 19:29:55 +0200 Subject: SV: [sane-devel] sane-find-scanner can find my scanner, but Xsane can't? In-Reply-To: <20030628170036.GA1070@watcher.WorkGroup> Message-ID: -----Oprindelig meddelelse----- Fra: Michael Rasile [mailto:keeper at neo.rr.com] Sendt: 28. juni 2003 19:01 Til: Christoffer Holm Kj?lb?k Emne: Re: [sane-devel] sane-find-scanner can find my scanner, but Xsane can't? Hey Mike Thanks for you answer I think the problem is the old backend, that came with RedHat 9.0 as default. The version was: 1.0.9-5 Amd the newest is 1.0.12, so maybe it is that Can i just install the new backend, and nothing else? regards Christoffer On Sat Jun 28, 2003 at 03:23:08PM +0200 or thereabouts, Christoffer Holm Kj?lb?k wrote: > Hey > > I have a Canon LiDe30, wich shuold be supported by sane > > And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0 > > But, Xsane says, that there is no devices available, why? > > Kind regards - and thanks in adance > Christoffer Kj?lb?k > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel Greetings! Well, I have the same scanner and I use Gentoo. The first time I installed gentoo, I couldn't get the scanner to work right away. The problem is the sane-backend. Do you know what version of sane you have. What does scanimage -L show? If it doesn't show anything and your scanner is found by the kernel, then the problem lies with sane's backend. If you upgrade to the latest version of the sane-backend, it should solve the problem. What I did was to download the backend from the website and follow the directions for unpacking and installing. I installed right over the backend that was installed by gentoo. It worked for me. Now, here is something strange. I had to reinstall gentoo and before I upgraded the sane-backend, I tried xsane and it worked. Who knows why? Well, if you upgrade your sane-backend, it should solve the problem. HTH -- Regards, Mike keeper at neo.rr.com "Don't Fear The Penguin." From JeffMay at earthlink.net Sat Jun 28 18:38:10 2003 From: JeffMay at earthlink.net (Jeffery C. May) Date: 28 Jun 2003 13:38:10 -0400 Subject: [sane-devel] Re: Sane-devel digest, Vol 1 #503 - 1 msg In-Reply-To: <20030628132618.13633.99099.Mailman@panda.mostang.com> References: <20030628132618.13633.99099.Mailman@panda.mostang.com> Message-ID: <1056821890.4190.34.camel@daisy.localdomain> On Sat, 2003-06-28 at 09:26, Christoffer Kjlbk wrote: > Hey > > I have a Canon LiDe30, wich shuold be supported by sane > > And if I run sane-find-scanner, it finds the scanner at /dev/usb/scanner0 > > But, Xsane says, that there is no devices available, why? > > Kind regards - and thanks in adance > Christoffer Kjlbk I'm having the similar (but not identical) difficulty with a Benq (Acer) 3300U that worked perfectly under Red Hat 7.1. After upgrading to Red Hat 9.0 and the latest SANE packages (compiled, not Red Hat packages) I get the following behavior: Looking in /proc/bus/usb/devices I find: ===================begin /proc/bus/usb/devices listing============= E: Ad=01(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=02 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=ff(vend.) Sub=ff Prot=ff MxPS= 8 #Cfgs= 1 P: Vendor=04a5 ProdID=20b0 Rev= 1.00 S: Manufacturer=Color S: Product= FlatbedScanner 22 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=usbscanner ===================end /proc/bus/usb/devices listing=============== So the scanner is seen by the kernel and the usbfs system. ===================begin sane-find-scanner output================== # 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=0x04a5, product=0x20b0) at /dev/usb/scanner0 found USB scanner (vendor=0x04a5, product=0x20b0) at libusb:001:003 # 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. ===================end sane-find-scanner output==================== Okay, sane-find-scanner sees it. ===================begin scanimage -L output================== device `snapscan:/dev/usb/scanner0' is a Acer FlatbedScanner22 flatbed scanner ===================end scanimage -L output==================== Okay, so scanimage says it's there. According to the Sourceforge page (http://snapscan.sourceforge.net/), the Acer/Benq 3300 uses either the "u222v067.bin" or "u176v046.bin" firmware files. Looking at the CD that came with the scanner I find the first one (u222v067.bin), but not the second one: ===================begin listing of CD firmware================== /mnt/cdrom1/u174v041.BIN /mnt/cdrom1/u176v042.bin /mnt/cdrom1/u222v067.bin /mnt/cdrom1/u34v110.bin /mnt/cdrom1/u96v121.bin ===================end listing of CD firmware==================== I copied the "u222v67.bin" file to /etc/sane.d/firmware/Benq_3300U and modified the /etc/sane.d/snapscan.conf file as shown below: ===================begin /etc/sane.d/snapscan.conf================ #------------------------------ General ----------------------------------- # Change to the fully qualified filename of your firmware file, if # firmware upload is needed by the scanner firmware /etc/sane.d/firmware/Benq_3300U/u222v067.bin # If not automatically found you may manually specify a device name. # For USB scanners also specify bus=usb, e.g. # /dev/usb/scanner0 bus=usb # For SCSI scanners specify the generic device, e.g. /dev/sg0 on Linux. # /dev/sg0 #--------------------------------------------------------------------------- # No changes should be necessary below this line #--------------------------------------------------------------------------- #-------------------------- SCSI scanners ---------------------------------- # These SCSI devices will be probed automatically scsi AGFA * Scanner scsi COLOR * Scanner scsi Color * Scanner scsi ACERPERI * Scanner #--------------------------- USB scanners ----------------------------------- # These USB devices will be probed automatically # (This will currently work only on Linux) # Benq/Acer/Vuego 320U usb 0x04a5 0x2022 # Benq/Acer/Vuego 620U / 620UT usb 0x04a5 0x1a2a usb 0x04a5 0x2040 # Benq/Acer/Vuego 640U usb 0x04a5 0x2060 # Benq/Acer/Vuego 640BU usb 0x04a5 0x207e # Benq/Acer/Vuego 1240U usb 0x04a5 0x20c0 # Benq/Acer/Vuego 3300 / 4300 usb 0x04a5 0x20b0 # Benq/Acer/Vuego 4300 usb 0x04a5 0x20de # Benq/Acer/Vuego 5000 usb 0x04a5 0x20fc # Benq/Acer/Vuego 5300 usb 0x04a5 0x20fe # Agfa 1236U usb 0x06bd 0x0002 # Agfa 1212U usb 0x06bd 0x0001 usb 0x06bd 0x2061 # Agfa Snapscan e10 usb 0x06bd 0x2093 # Agfa Snapscan e20 usb 0x06bd 0x2091 # Agfa Snapscan e25 usb 0x06bd 0x2095 # Agfa Snapscan e26 usb 0x06bd 0x2097 # Agfa Snapscan e40 usb 0x06bd 0x208d # Agfa Snapscan e42 usb 0x06bd 0x20ff # Agfa Snapscan e50 usb 0x06bd 0x208f # Agfa Snapscan e52 usb 0x06bd 0x20fd ===================end /etc/sane.d/snapscan.conf================== If I run Xsane at this point it hangs. Setting SANE_DEBUG_SNAPSCAN=255 and running scanimage I get the following messages: ===================begin scanimage debug================ [sanei_debug] Setting debug level of snapscan to 255. [snapscan] sane_snapscan_init [snapscan] sane_snapscan_init: Snapscan backend version 1.4.26 [snapscan] add_usb_device(/dev/usb/scanner0) [snapscan] add_usb_device: Detected (kind of) an USB device [snapscan] snapscani_usb_open(/dev/usb/scanner0) [snapscan] add_usb_device: Checking if 0x04a5 is a supported USB vendor ID [snapscan] snapscani_check_device() [snapscan] mini_inquiry [snapscan] snapscan_cmd [snapscan] snapscan_usb_cmd(0,0xbfffc3c0,6,0xbfffc390,0xbfffc38c (36)) [snapscan] atomic_usb_cmd(0,0xbfffc3c0,6,0xbfffc390,0xbfffc38c (36)) [snapscan] usb_cmd(0,0xbfffc3c0,6,0xbfffc390,0xbfffc38c (36)) [snapscan] usb_cmd: cmdlen=6, datalen=0 [snapscan] usb_write: writing: 0x12 0x00 0x00 0x00 0x24 0x00 [snapscan] usb_write: Only 0 bytes written [snapscan] mini_inquiry: snapscan_cmd command failed: error during device I/O [snapscan] snapscani_check_device: mini_inquiry failed with Error during device I/O [snapscan] snapscani_usb_close(0) [snapscan] add_usb_device(libusb:001:003) [snapscan] add_usb_device: Detected (kind of) an USB device [snapscan] snapscani_usb_open(libusb:001:003) [snapscan] add_usb_device: error opening device libusb:001:003: Access to resource has been denied [snapscan] sane_snapscan_get_devices (0xbfffd5d8, 0) scanimage: no SANE devices found [snapscan] sane_snapscan_exit ===================end scanimage debug================== Libusb is something new that Red Hat 7.1 didn't have. Any clues as to what I'm missing? I'm sure it's something simple. Jeff From fsanta at arrakis.es Sat Jun 28 20:05:28 2003 From: fsanta at arrakis.es (fsanta) Date: Sat, 28 Jun 2003 21:05:28 +0200 Subject: [sane-devel] Any umax persons still on the list? Message-ID: <200306282105.28692.fsanta@arrakis.es> Hi. Astra 2200 works with SuSE 8.1 but not with 8.2 Here is the error message: Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses synchronous negotiation. Using asynchronous transfers Can anyone tell me how to get 'synchronous transfers'? Adaptec 2904 scsi card with astra 2200su Cheers, Steve. From foffy_69 at yahoo.es Sat Jun 28 20:30:54 2003 From: foffy_69 at yahoo.es (=?iso-8859-1?q?Foffy?=) Date: Sat, 28 Jun 2003 21:30:54 +0200 (CEST) Subject: [sane-devel] [sane-delevel] writing a backend Message-ID: <20030628193054.76829.qmail@web41003.mail.yahoo.com> I have a genius colorpage vivid 3 usb scanner and i want to write a backend. how i can start writing it?? thanks a lot ___________________________________________________ Yahoo! Messenger - Nueva versi?n GRATIS Super Webcam, voz, caritas animadas, y m?s... http://messenger.yahoo.es From haidara at gucmed.com Sat Jun 28 20:34:41 2003 From: haidara at gucmed.com (Ayman Haidar) Date: Sat, 28 Jun 2003 15:34:41 -0400 Subject: [sane-devel] scanner recommendation In-Reply-To: <200306281143.45082.haidara@gucmed.com> References: <200306281143.45082.haidara@gucmed.com> Message-ID: <200306281534.41116.haidara@gucmed.com> sorry for the missing subject On Saturday 28 June 2003 11:43 am, Ayman Haidar wrote: > Hello, > > I would greatly appreciate if you could recommend a scanner that works with > sane, has an ADF and fairly decent scanning speed. > > I need to use it in the office and we might scan about 50-100 documents > daily. > > > Thanks -- Ayman Haidar, MD From henning at meier-geinitz.de Sat Jun 28 21:50:41 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 22:50:41 +0200 Subject: [sane-devel] Re: Sane-devel digest, Vol 1 #503 - 1 msg In-Reply-To: <1056821890.4190.34.camel@daisy.localdomain> References: <20030628132618.13633.99099.Mailman@panda.mostang.com> <1056821890.4190.34.camel@daisy.localdomain> Message-ID: <20030628205041.GD10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 01:38:10PM -0400, Jeffery C. May wrote: > I'm having the similar (but not identical) difficulty with a Benq (Acer) > 3300U that worked perfectly under Red Hat 7.1. Different backend (snapscan vs. plustek) so I don't think it's related. > [snapscan] snapscani_usb_open(/dev/usb/scanner0) > [snapscan] add_usb_device: Checking if 0x04a5 is a supported USB vendor ID [...] > [snapscan] usb_write: writing: 0x12 0x00 0x00 0x00 0x24 0x00 > [snapscan] usb_write: Only 0 bytes written > [snapscan] mini_inquiry: snapscan_cmd command failed: error during device I/O > Libusb is something new that Red Hat 7.1 didn't have. Any clues as to > what I'm missing? I'm sure it's something simple. I have no idea why it fails but it's not libusb. You are using the kernel scanner driver, see the first line of the log. You could try libusb (rmmod scanner) instead. Standard comments: - Make sure that your scanner is not confused by earlier tests (unplug/replug it) - diable everything but snapscan in dll.conf Bye, Henning From henning at meier-geinitz.de Sat Jun 28 21:56:21 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 22:56:21 +0200 Subject: [sane-devel] Any umax persons still on the list? In-Reply-To: <200306282105.28692.fsanta@arrakis.es> References: <200306282105.28692.fsanta@arrakis.es> Message-ID: <20030628205621.GE10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 09:05:28PM +0200, fsanta wrote: > Astra 2200 works with SuSE 8.1 but not with 8.2 Most people don't know what that means. What changed between these versions? i.e. kernel version + sane version? Try to find out what change causes the problem by using the old kernel or the old sane version. > Here is the error message: > > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > synchronous negotiation. Using asynchronous transfers > > Can anyone tell me how to get 'synchronous transfers'? I don't think it helps to repeat your questions without providing more information on what you did. As I said stuff like "sync negotiotaion" is done in the kernel SCSI driver. > Adaptec 2904 scsi card with astra 2200su Have you tried an older kernel or using the old SCSI driver as explained in my other mail? Bye, Henning From henning at meier-geinitz.de Sat Jun 28 21:59:47 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 28 Jun 2003 22:59:47 +0200 Subject: [sane-devel] [sane-delevel] writing a backend In-Reply-To: <20030628193054.76829.qmail@web41003.mail.yahoo.com> References: <20030628193054.76829.qmail@web41003.mail.yahoo.com> Message-ID: <20030628205947.GF10041@meier-geinitz.de> Hi, On Sat, Jun 28, 2003 at 09:30:54PM +0200, Foffy wrote: > I have a genius colorpage vivid 3 usb scanner and i > want to write a backend. > > how i can start writing it?? Have a look at the archive of this mailing list. There have been similar questions about this topic during the last week: http://www.mostang.com/pipermail/sane-devel/2003-June/thread.html As a start: http://www.meier-geinitz.de/sane/misc/unsupported.html Bye, Henning From JeffMay at earthlink.net Sun Jun 29 03:52:37 2003 From: JeffMay at earthlink.net (Jeffery C. May) Date: 28 Jun 2003 22:52:37 -0400 Subject: [sane-devel] Well, Duh... In-Reply-To: <20030628205202.16781.49733.Mailman@panda.mostang.com> References: <20030628205202.16781.49733.Mailman@panda.mostang.com> Message-ID: <1056855157.4240.22.camel@daisy.localdomain> Well, I figured out my Benq 3300U problem. I had the wrong firmware file. instead of using u222v067.bin, I should have been using the u176v042.bin file (that was also on the CD that came with it!) Found the proper hint on this page: http://www.acronymchile.com/scanner.html Jeff (Thanks for all the help!) From oliver.rauch at rauch-domain.de Sun Jun 29 17:20:48 2003 From: oliver.rauch at rauch-domain.de (Oliver Rauch) Date: Sun, 29 Jun 2003 18:20:48 +0200 Subject: [sane-devel] Any umax persons still on the list? In-Reply-To: <200306282105.28692.fsanta@arrakis.es> References: <200306282105.28692.fsanta@arrakis.es> Message-ID: <200306291820.48500.oliver.rauch@rauch-domain.de> Most umax scanners do not support syncronous transfers. The scsi controller/driver does the only valid thing: it uses async transfers. Where is the problem with that? Oliver On Saturday 28 June 2003 21:05, fsanta wrote: > Hi. > Astra 2200 works with SuSE 8.1 but not with 8.2 > > Here is the error message: > > Jun 24 12:24:37 sbs3 kernel: (scsi0:A:5:0): refuses > synchronous negotiation. Using asynchronous transfers > > Can anyone tell me how to get 'synchronous transfers'? > > Adaptec 2904 scsi card with astra 2200su > > Cheers, Steve. > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel -- http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:Oliver.Rauch at Rauch-Domain.DE From hshane at austin.rr.com Sun Jun 29 17:54:37 2003 From: hshane at austin.rr.com (Howard Shane) Date: Sun, 29 Jun 2003 11:54:37 -0500 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP References: <3EFC351F.50508@austin.rr.com> <20030627132846.GI2318@meier-geinitz.de> Message-ID: <3EFF19CD.2040409@austin.rr.com> So, I guess my question boils down to this: Let's say hypothetically we're up to linux-2.6.0, and there is no more kernel usb-scanner support, and a person wants to use a SANE application. All they have to do is to be sure libusb is installed with the SANE backends and whatever frontend they're after, right? No other configuration steps are necessary? Are there any specific pitfalls to to be aware of? Sorry for my persistence but I want to be sure I am giving all those out there who read the HOWTO the most accurate and complete picture possible. :^) Thanks! Henning Meier-Geinitz wrote: > Hi, > > On Fri, Jun 27, 2003 at 07:14:23AM -0500, Howard Shane wrote: > >>I've visited the libusb site, and the only documentation available seems >>to be for developers. If someone can point me to more user-oriented >>information I'll be happy to include it. I assume it's out of the beta >>phase? Are there distribution manufacturers including it in their stable >>branches of binaries? > > > As far as I kno all Linux distributions include libusb. Libusb is a > library to access generic USB devices. It uses the operating system > generic USB driver and how that works exactly depends on the operating > system. > > The only thing the user needs to know is that he can only use libusb > access if no other kernel driver is attached to the speicfic device. > In case of Linux, that means "rmmod scanner". For permission issues > and other details look at man sane-usb. Maybe a pointer to that man > page is sufficiant. > > Bye, > Henning > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel > From henning at meier-geinitz.de Sun Jun 29 18:16:41 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 29 Jun 2003 19:16:41 +0200 Subject: [sane-devel] Second draft of Scanner HOWTO for TLDP In-Reply-To: <3EFF19CD.2040409@austin.rr.com> References: <3EFC351F.50508@austin.rr.com> <20030627132846.GI2318@meier-geinitz.de> <3EFF19CD.2040409@austin.rr.com> Message-ID: <20030629171641.GA18926@meier-geinitz.de> Hi, On Sun, Jun 29, 2003 at 11:54:37AM -0500, Howard Shane wrote: > So, I guess my question boils down to this: Let's say hypothetically > we're up to linux-2.6.0, and there is no more kernel usb-scanner > support, and a person wants to use a SANE application. All they have to > do is to be sure libusb is installed with the SANE backends and whatever > frontend they're after, right? Usually sane-backends depends on libusb, so if SANE is installed, libusb should also be installed automatically. > No other configuration steps are necessary? Are there any specific > pitfalls to to be aware of? It may be necessary to adjust the permissions of usbdevfs as explained in man sane-usb. At least if you want to scan as non-root. I don't know how addvanced the hotplug setup currently is. That's something hotplug could do. Bye, Henning From moali at sbox.tugraz.at Sun Jun 29 18:47:02 2003 From: moali at sbox.tugraz.at (Gerfried Maier) Date: Sun, 29 Jun 2003 19:47:02 +0200 Subject: [sane-devel] XSane 0.90: Missing gettext produces hard to understand error-message when compiling Message-ID: <3EFF2616.6080205@sbox.tugraz.at> It took me a while to figure out what the problem was. The "no" from configure seems to be treated as gmsgfmt-command. A cut from the output of configure: [...] checking whether catgets can be used... no checking for msgfmt... (cached) no checking for gmsgfmt... no checking for xgettext... : checking for catalogs to be installed... cs da de es fr it ja nl pt pt_BR ro ru sk sl sr sv vi tr checking for sane-config... /usr/local/bin/sane-config [...] The making of... [...] make[1]: Leaving directory `/home/moali/src/xsane-0.90/src' making all in po make[1]: Entering directory `/home/moali/src/xsane-0.90/po' file=./`echo de | sed 's,.*/,,'`.gmo \ && rm -f $file && PATH=../src:$PATH no -o $file de.po /bin/sh: line 1: no: command not found make[1]: *** [de.gmo] Error 127 make[1]: Leaving directory `/home/moali/src/xsane-0.90/po' make: *** [all-recursive] Error 1 Regards, Maier Gerfried From jollyprince at juno.com Sun Jun 29 20:01:09 2003 From: jollyprince at juno.com (jollyprince at juno.com) Date: Sun, 29 Jun 2003 19:01:09 GMT Subject: [sane-devel] Visioneer 5800 backend Message-ID: <20030629.120151.16123.69038@webmail12.lax.untd.com> I'm interested in writing a backend for my Visioneer 5800. I've written some C code in my lifetime but that's about all the prerequisites that I have to bring to the project. I've opened up the box but couldn't get to the chipset for fear of damaging the wiring harness. Any suggestions about getting the maximum info about the product. I'm told it's a LM9832 chipset. Can anyone confirm or deny this? Can anyone recommend an example of a working backend that would be similar to what a Visioneer backend might look like? I've studied a bunch of stuff and feel lost in an information explosion. Any tips and shortcuts that are applicable would be greatly appreciated! Thanks in advance! From henning at meier-geinitz.de Sun Jun 29 21:01:39 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 29 Jun 2003 22:01:39 +0200 Subject: [sane-devel] Visioneer 5800 backend In-Reply-To: <20030629.120151.16123.69038@webmail12.lax.untd.com> References: <20030629.120151.16123.69038@webmail12.lax.untd.com> Message-ID: <20030629200139.GA23824@meier-geinitz.de> Hi, On Sun, Jun 29, 2003 at 07:01:09PM +0000, jollyprince at juno.com wrote: > I'm interested in writing a backend for my Visioneer 5800. I've > written some C code in my lifetime but that's about all the > prerequisites that I have to bring to the project. That and a lot of patience is enough :-) Please show us the output of "cat /proc/bus/usb/devices" when the scanner is plugged in. > I've opened up the box but couldn't get to the chipset for fear of > damaging the wiring harness. Any suggestions about getting the > maximum info about the product. I'm told it's a LM9832 chipset. Can > anyone confirm or deny this? Just try it. There is a tool to find out about some known chipsets: http://www.meier-geinitz.de/sane/check-usb-scanner/ > Can anyone recommend an example of a working backend that would be > similar to what a Visioneer backend might look like? If it's really a LM9832, adding support to the plustek backend is the way to go. But i doubt that it's really that chipset. Our database says "E5" chipset, whatever that means. > I've studied a bunch of stuff and feel lost in an information > explosion. Any tips and shortcuts that are applicable would be > greatly appreciated! Thanks in advance! There have been wuite some discussion about how to start writing a backend during the last week so reading the archive of sane-devel may help to get started. Bye, Henning From jollyprince at juno.com Sun Jun 29 21:38:25 2003 From: jollyprince at juno.com (jollyprince at juno.com) Date: Sun, 29 Jun 2003 20:38:25 GMT Subject: [sane-devel] Re: Visioneer 5800 Message-ID: <20030629.133908.559.189108@webmail05.lax.untd.com> T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=04a7 ProdID=0226 Rev= 1.00 S: Manufacturer=Visioneer S: Product=USB Scanner S: SerialNumber=RTS8801C2-004 C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms RESULT: of cat /proc/bus/usb/devices | more From rene.rebe at gmx.net Sun Jun 29 22:14:17 2003 From: rene.rebe at gmx.net (Rene Rebe) Date: Sun, 29 Jun 2003 23:14:17 +0200 (CEST) Subject: [sane-devel] ScanJet 5300C question In-Reply-To: <3EF9F507.6040604@midwest-tool.com> References: <3EF9F507.6040604@midwest-tool.com> Message-ID: <20030629.231417.730551786.rene.rebe@gmx.net> Hi, On: Wed, 25 Jun 2003 14:16:23 -0500, Matt Lung wrote: > I would like to use the ADF we have with our HP 5300C scanner under > linux and Sane but I have yet to find any documentation or help on how > to setup an ADF with this scanner. It scans just fine without it, but > with out the ADF funcioning I'll be forced to use it in Windows forever. > > Is an ADF even supported with the HP 5300C? Theoretically yes. But I have still to solve ADF problem for the 7400 series. But older ADF units and the professional ones e.g. from the Avision 8000 series just work fine. So if you have luck the ADF will simply work when you plugged it into your scanner. If the ADF hangs during feeding the first page, use usbsnoop during ADF scanning under Windows to log the data traffic and send the output to me. I hope to have some free time this summer to continue to solve the last HP problems with the backend. > If so, where can I find information on how to do this? > > thanks for any help Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene.rebe at gmx.net http://www.rocklinux.org http://www.rocklinux.org/people/rene http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From rene.rebe at gmx.net Sun Jun 29 22:19:37 2003 From: rene.rebe at gmx.net (Rene Rebe) Date: Sun, 29 Jun 2003 23:19:37 +0200 (CEST) Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030625205240.GA12653@meier-geinitz.de> References: <20030624194126.GC7697@meier-geinitz.de> <1056560236.3843.853.camel@localhost.localdomain> <20030625205240.GA12653@meier-geinitz.de> Message-ID: <20030629.231937.846934703.rene.rebe@gmx.net> Hi, On: Wed, 25 Jun 2003 22:52:40 +0200, Henning Meier-Geinitz wrote: > I have to admitt that I'm a bit confused by the backend. It uses USB > interrupt transfers to get the status of the scanner. However that > only works with libusb, not the kernel scanner driver. So I don't > really know why the backend lists "usb /dev/ubs/scanner" in > avision.conf. Maybe the maintainer can enlighten me :-) Yes - the scanner Linux driver is not supported. The line in the avision.conf might only silpped in from my initial tests with the scanner driver. I'll remove it soon. > > Usually the config files list all devices and device files the backend > supports. So it doesn't matter if there are additional ones. > > The backend checks for all USB devices anymway, I don't think the > entries in avsion.conf are necessary at all. Yes - the entries are only an example how to add IDs for test reasons when new scanners are out ... > > I'll keep trying. I have just done > > modprobe scanner vendor=0x0001 product=0x0002, > > These vendor and product ids are most probably wrong. If the scanner > driver works at all, try something like this: > rmmod scanner > modprobe scanner vendor=0x03f0 product=0x0801 The scanner driver does not work. > That doesn't look good. Your scanner doesn't seem to accept any input > on any endpoint (bulk in, out and interrupt). > > I recommend to unplug/replug your scanner before any test. Otherwise > it may be confuded by eralier tests. It needs to be powerer off to loose all it's state. > Is loaded but doesn't know about your scanner. > > Bye, > Henning Thanks for the answering the questions Henning - when I'm as always out of time ;-) Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene.rebe at gmx.net http://www.rocklinux.org http://www.rocklinux.org/people/rene http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From rene.rebe at gmx.net Sun Jun 29 22:25:24 2003 From: rene.rebe at gmx.net (Rene Rebe) Date: Sun, 29 Jun 2003 23:25:24 +0200 (CEST) Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030627211110.GM2318@meier-geinitz.de> References: <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> Message-ID: <20030629.232524.607955671.rene.rebe@gmx.net> Hi, On: Fri, 27 Jun 2003 23:11:10 +0200, Henning Meier-Geinitz wrote: > > This made scanimage -L work after rebooting, > > Rebooting shouldn't be ever necessary. But if your scanner hangs, > unplugging it may help. Power off is needed for the scanner to loose all state. > > Now I am pretty sure that my problem is in usbdevfs, but I don't know > > how to fix it. > > I don't think so. The timeouts occur because the scanner doesn't > understand something the backend sends. That may be a backend broblem > or something odd in the USB system. The scanner should "understand" all. It works here with a old HP 5300 and a slightly newer HP 5300 labelled as 5370. Which host controller chip and respective kernel driver is this? If communication via libusb is not reliable for you, you still can use the "deprecated" hpusbscsi driver in the kernel - but _not_ the scanner driver. > > What can I try next? > > Try the scanner driver. If it shows the same behaviour, you are sure > that it's not usbfs. The scanner driver will not work - because of the missing interrupt endpoint notification support - but I do not want to support a 3rd "to be removed in the future" access method. So I think hpusbscsi and libusb should be ok. > Otherwise, well, wait until the avision maintainer shows up again :-) CC'ing me always helps a lot ;-) > Bye, > Henning Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene.rebe at gmx.net http://www.rocklinux.org http://www.rocklinux.org/people/rene http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From tomf at sjpc.org Mon Jun 30 04:54:01 2003 From: tomf at sjpc.org (Thomas Frayne) Date: 29 Jun 2003 20:54:01 -0700 Subject: [sane-devel] HP 7450C USB scanner failure with ADF In-Reply-To: <20030629.232524.607955671.rene.rebe@gmx.net> References: <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> <20030629.232524.607955671.rene.rebe@gmx.net> Message-ID: <1056945240.3460.92.camel@localhost.localdomain> On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: > Hi, > > On: Fri, 27 Jun 2003 23:11:10 +0200, > Henning Meier-Geinitz wrote: > ... > > Which host controller chip and respective kernel driver is this? Here are messages that may help answer your questions. If this won't do it, could you tell me how to find the answers to your questions? Jun 29 07:33:03 localhost kernel: Linux version 2.4.20-18.9 (root at gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Wed Jun 4 15:04:35 PDT 2003 Installed via up2date. Jun 29 07:33:05 localhost kernel: usb.c: registered new driver usbdevfs Jun 29 07:33:05 localhost kernel: usb.c: registered new driver hub Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0 Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0870000, IRQ 5 Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC Corporation USB Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 3 ports detected Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0 Jun 29 07:33:06 localhost rc: Starting pcmcia: succeeded Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0872000, IRQ 9 Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC Corporation USB (#2) Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.0-1, assigned address 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB 2.0 Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem f087a000 Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 3 Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size set incorrectly (32 bytes) by BIOS/FW. Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size corrected to 128. Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22 Jun 29 07:33:06 localhost kernel: usb.c: USB disconnect on device 00:0b.0-1 address 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 5 ports detected Jun 29 07:33:06 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time 07:14:02 May 29 2003 Jun 29 07:33:06 localhost kernel: usb-uhci.c: High bandwidth mode enabled Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:07.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 29 07:33:06 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, IRQ 10 Jun 29 07:33:06 localhost kernel: usb-uhci.c: Detected 2 ports Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 4 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected Jun 29 07:33:06 localhost kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hiddev Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hid Jun 29 07:33:06 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik Jun 29 07:33:06 localhost kernel: hid-core.c: USB HID support drivers Jun 29 07:33:06 localhost kernel: mice: PS/2 mouse device common for all mice Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1, assigned address 2 Jun 29 07:33:06 localhost mount: mount: none already mounted or /proc/bus/usb busy Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost mount: mount: according to mtab, usbdevfs is already mounted on /proc/bus/usb Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected Jun 29 07:33:06 localhost netfs: Mounting other filesystems: failed Jun 29 07:33:06 localhost kernel: Adding Swap: 1582360k swap-space (priority -1) Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 29 07:33:06 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.2, assigned address 3 Jun 29 07:33:06 localhost kernel: usb.c: USB device 3 (vend/prod 0x2821/0x5001) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.4, assigned address 4 Jun 29 07:33:06 localhost kernel: usb.c: USB device 4 (vend/prod 0x3f0/0x3404) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: Initializing USB Mass Storage driver... Jun 29 07:33:06 localhost kernel: usb.c: registered new driver usb-storage Jun 29 07:33:07 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices Jun 29 07:33:07 localhost kernel: Vendor: ASUS Model: CRW-5224A Rev: 1.00 Jun 29 07:33:07 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 29 07:33:07 localhost kernel: USB Mass Storage support registered. Jun 29 07:33:07 localhost kernel: hdc: attached ide-scsi driver. Jun 29 07:33:07 localhost kernel: scsi2 : SCSI host adapter emulation for IDE ATAPI devices Jun 29 07:33:07 localhost kernel: Vendor: HP Model: CD-Writer+ 8100 Rev: 1.0g Jun 29 07:33:07 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 29 07:33:07 localhost kernel: usb.c: registered new driver usblp Jun 29 07:33:07 localhost kernel: printer.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404 > > If communication via libusb is not reliable for you, you still can use > the "deprecated" hpusbscsi driver in the kernel - but _not_ the > scanner driver. I've tried so many configuration variations over the last couple of weeks that I've gotten confused about what configuration settings do what. I don't think I understand the terminology. I now think I should avoid using the scanner driver. Would rmmod scanner do this for me, or is something else necessary? I would like to use libusb, but I have not been able to figure out what causes the libusb driver to be loaded. Some parts of my system refer to usbfs; others refer to usbdevfs. I think I need everything in the system refering to one or everything to the other, but when I tried changing the references to usbfs, I produced a system that would not boot, and had to restore a backup. What is the best way to get back to a clean system? Is there a modprobe command I should be using to load the libusb driver? If so, should I add it to /etc/rc.d/rc.local to get it to run during boot? I currently have hpusbbscsi disabled. Should both libusb and hpusbbscsi be enabled? ... > > The scanner driver will not work - because of the missing interrupt > endpoint notification support - but I do not want to support a 3rd "to > be removed in the future" access method. So I think hpusbscsi and > libusb should be ok. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomf at sjpc.org Mon Jun 30 05:45:37 2003 From: tomf at sjpc.org (Thomas Frayne) Date: 29 Jun 2003 21:45:37 -0700 Subject: [sane-devel] HP 7450C ... addendum In-Reply-To: <20030629.232524.607955671.rene.rebe@gmx.net> References: <20030625205240.GA12653@meier-geinitz.de> <1056743137.3204.1.camel@localhost.localdomain> <20030627211110.GM2318@meier-geinitz.de> <20030629.232524.607955671.rene.rebe@gmx.net> Message-ID: <1056948336.3460.127.camel@localhost.localdomain> On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: > Hi, > > On: Fri, 27 Jun 2003 23:11:10 +0200, > Henning Meier-Geinitz wrote: ... > Which host controller chip and respective kernel driver is this? I sent my last message prematurely. Please disregard it. My system is Redhat 9.0, with up2date run today. I have sane-backends-1.0.12.tar.gz and xsane-0.91.tar.gz installed. Here are messages that may help answer your questions. If this won't do it, could you tell me how to find the answers to your questions? T: Bus=04 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=9000 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=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=0801 Rev= 0.01 S: Manufacturer=hp S: Product=hp scanjet 7400c S: SerialNumber=87 tem 7400c C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 2mA I: If#= 0 Alt= 0 #EPs= 3 Cls=00(>ifc ) Sub=00 Prot=00 Driver=(none) E: Ad=01(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms E: Ad=82(I) Atr=03(Int.) MxPS= 8 Ivl=10ms E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms Jun 29 07:33:03 localhost kernel: Linux version 2.4.20-18.9 (root at gozin3) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Wed Jun 4 15:04:35 PDT 2003 Installed via up2date. Jun 29 07:33:05 localhost kernel: usb.c: registered new driver usbdevfs Jun 29 07:33:05 localhost kernel: usb.c: registered new driver hub Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 5 for device 00:0b.0 Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0870000, IRQ 5 Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC Corporation USB Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 1 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 3 ports detected Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 9 for device 00:0b.1 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 9 with 00:0a.0 Jun 29 07:33:06 localhost rc: Starting pcmcia: succeeded Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase 0xf0872000, IRQ 9 Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.1, NEC Corporation USB (#2) Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.0-1, assigned address 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:0b.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:07.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB 2.0 Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem f087a000 Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 3 Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size set incorrectly (32 bytes) by BIOS/FW. Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size corrected to 128. Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jan-22 Jun 29 07:33:06 localhost kernel: usb.c: USB disconnect on device 00:0b.0-1 address 2 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 5 ports detected Jun 29 07:33:06 localhost kernel: usb-uhci.c: $Revision: 1.275 $ time 07:14:02 May 29 2003 Jun 29 07:33:06 localhost kernel: usb-uhci.c: High bandwidth mode enabled Jun 29 07:33:06 localhost kernel: PCI: Found IRQ 10 for device 00:07.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0b.2 Jun 29 07:33:06 localhost kernel: PCI: Sharing IRQ 10 with 00:0d.0 Jun 29 07:33:06 localhost kernel: usb-uhci.c: USB UHCI at I/O 0x9000, IRQ 10 Jun 29 07:33:06 localhost kernel: usb-uhci.c: Detected 2 ports Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, assigned bus number 4 Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost kernel: hub.c: 2 ports detected Jun 29 07:33:06 localhost kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hiddev Jun 29 07:33:06 localhost kernel: usb.c: registered new driver hid Jun 29 07:33:06 localhost kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik Jun 29 07:33:06 localhost kernel: hid-core.c: USB HID support drivers Jun 29 07:33:06 localhost kernel: mice: PS/2 mouse device common for all mice Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1, assigned address 2 Jun 29 07:33:06 localhost mount: mount: none already mounted or /proc/bus/usb busy Jun 29 07:33:06 localhost kernel: hub.c: USB hub found Jun 29 07:33:06 localhost mount: mount: according to mtab, usbdevfs is already mounted on /proc/bus/usb Jun 29 07:33:06 localhost kernel: hub.c: 4 ports detected Jun 29 07:33:06 localhost netfs: Mounting other filesystems: failed Jun 29 07:33:06 localhost kernel: Adding Swap: 1582360k swap-space (priority -1) Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:07.2-1, assigned address 2 Jun 29 07:33:06 localhost kernel: usb.c: USB device 2 (vend/prod 0x3f0/0x801) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.2, assigned address 3 Jun 29 07:33:06 localhost kernel: usb.c: USB device 3 (vend/prod 0x2821/0x5001) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: hub.c: new USB device 00:0b.2-1.4, assigned address 4 Jun 29 07:33:06 localhost kernel: usb.c: USB device 4 (vend/prod 0x3f0/0x3404) is not claimed by any active driver. Jun 29 07:33:06 localhost kernel: Initializing USB Mass Storage driver... Jun 29 07:33:06 localhost kernel: usb.c: registered new driver usb-storage Jun 29 07:33:07 localhost kernel: scsi1 : SCSI emulation for USB Mass Storage devices Jun 29 07:33:07 localhost kernel: Vendor: ASUS Model: CRW-5224A Rev: 1.00 Jun 29 07:33:07 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 29 07:33:07 localhost kernel: USB Mass Storage support registered. Jun 29 07:33:07 localhost kernel: hdc: attached ide-scsi driver. Jun 29 07:33:07 localhost kernel: scsi2 : SCSI host adapter emulation for IDE ATAPI devices Jun 29 07:33:07 localhost kernel: Vendor: HP Model: CD-Writer+ 8100 Rev: 1.0g Jun 29 07:33:07 localhost kernel: Type: CD-ROM ANSI SCSI revision: 02 Jun 29 07:33:07 localhost kernel: usb.c: registered new driver usblp Jun 29 07:33:07 localhost kernel: printer.c: usblp0: USB Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x03F0 pid 0x3404 > If communication via libusb is not reliable for you, you still can use > the "deprecated" hpusbscsi driver in the kernel - but _not_ the > scanner driver. I've tried so many configuration variations over the last couple of weeks that I've gotten confused about what configuration settings do what. I don't think I understand the terminology. I now think I should avoid using the scanner driver. Would rmmod scanner do this for me, or is something else necessary? How can I tell whether or not I am using the scanner driver? I would like to use libusb, but I have not been able to figure out what causes the libusb driver to be loaded. Some parts of my system refer to usbfs; others refer to usbdevfs. I think I need everything in the system refering to one or everything to the other, but when I tried changing the usbdevfs references to usbfs, I produced a system that would not boot, and had to restore a backup. What is the best way to get back to a clean system? Is there a modprobe command I should be using to load the libusb driver? If so, should I add it to /etc/rc.d/rc.local to get it to run during boot? My guess is that modprobe scanner vendor=0x03f0 product=0x0801 should be added to /etc/rc.d/rc.local. Is that right? If so, what else needs to be done? What should be done to get the scanner mounted as rw with permissions for everyone to use it? The things I have tried with fstab did not work, since the system tried to mount it twice. I currently have hpusbbscsi disabled. Should both libusb and hpusbbscsi be enabled? ... > The scanner driver will not work - because of the missing interrupt > endpoint notification support - but I do not want to support a 3rd "to > be removed in the future" access method. So I think hpusbscsi and > libusb should be ok. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jollyprince at juno.com Mon Jun 30 05:51:42 2003 From: jollyprince at juno.com (jollyprince at juno.com) Date: Mon, 30 Jun 2003 04:51:42 GMT Subject: [sane-devel] Re: Visioneer 5800 Message-ID: <20030629.215242.2373.604481@webmail01.lax.untd.com> --- gerard klaver wrote: On Sun, 2003-06-29 at 20:38, jollyprince at juno.com wrote: > T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=04a7 ProdID=0226 Rev= 1.00 > S: Manufacturer=Visioneer > S: Product=USB Scanner > S: SerialNumber=RTS8801C2-004 > C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA > I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms > E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms > > RESULT: of cat /proc/bus/usb/devices | more > Realtek chip, see www.realtec.com.tw at page scanner ic some info is given about the chip. -- ---------- m.vr.gr. Gerard Klaver Bingo! You may have nailed it. Since the above serial number translates to a Realtek RTS88xx family chip, it may preclude the LM9832 of my previous Email. I made a request to Tech Support in Taiwan for data on the Realtek chip for Visioneer 5800. Once I get it I'm not sure what to do with it but it's a start. From jollyprince at juno.com Mon Jun 30 05:54:00 2003 From: jollyprince at juno.com (jollyprince at juno.com) Date: Mon, 30 Jun 2003 04:54:00 GMT Subject: [sane-devel] Fw: RTS8801C2 Serial Number Chipset Message-ID: <20030629.215444.2373.604497@webmail01.lax.untd.com> ---------- Forwarded Message ---------- I'm researching technical data to write a driver for a Visioneer 5800 Scanner. The above serial number was referenced when checking out the Visioneer 5800 specs. Am I on the right track and can you provide me with some help on this project? From kouno.hironori at pfu.fujitsu.com Mon Jun 30 06:55:57 2003 From: kouno.hironori at pfu.fujitsu.com (hironori kohno) Date: Mon, 30 Jun 2003 14:55:57 +0900 Subject: [sane-devel] Re: [sane-devel]The report about 'sane-fujitsu' In-Reply-To: References: <200306271648.FEE65799.SOPPLP.PVJSIJO@pfu.fujitsu.com> Message-ID: <200306301455.BAG28258.JVO.SSPPPPOIJL@pfu.fujitsu.com> ?? "Re: [sane-devel] [sane-devel]The report about 'sane-fujitsu' " ????? ""m. allan noah" "????????? > you use old version of sane. remove redhat version of sane-backend: > > rpm -e --force --nodeps sane-backend > > and re-install sane: > > ./configure --prefix=/usr --sysconfdir=/etc > make > make install > > see below for more comments > > On Fri, 27 Jun 2003, hironori kohno wrote: > > > Hi, > > > > I performed testing about 'sane-fujitsu'. > > It reports below. > > > > OS: RedHat Linux V8 > > Scanner: fi-4220C > > > > Indication matters: > > Hi, i performed the following test again. OS: RedHat V9 Scanner: fi-4220x Sane : cvs version + patch 1. color-mode The negative picture was acquired when scan was carried out by Color Mode. A check of rif has improved the above-mentioned phenomenon. Even if it does not check rif-option, i consider that it is better to output the same tone as the color of a paper. Bye, Kouno -- kouno.hironori at pfu.fujitsu.com From renito73 at hotmail.com Mon Jun 30 09:44:43 2003 From: renito73 at hotmail.com (Renito 73) Date: Mon, 30 Jun 2003 08:44:43 +0000 Subject: [sane-devel] Genius Vivid-3xe Message-ID: I have troubles to use my Genius Vivid-3xe scanner... sane recognizes it, but applications don't use it... my usb configuration is working properly since I took pictures with my webcam... I did chmod rwxrwxrwx /dev/usb/scanner* since only root had access to the devices... my usb driver is usb-uhcii.o (the other one uhci.o worked fine but my vmware did not work with it, so I changed to usb-uhci.o instead but camera and vmware continued working fine... Background: reno at voodoo:~$ sane-config --version 1.0.12 reno at voodoo:~$ sane-find-scanner found USB scanner (vendor=0x0458, product=0x2017) at libusb:001:004 (3xe) found USB scanner (vendor=0x046d, product=0x0840) at libusb:001:002 (webcam) reno at voodoo:~$ scanimage -L device `gt68xx:/dev/usb/scanner0' is a Genius Colorpage Vivid3xe flatbed scanner but when running xsane or kooka they say scanner is not round... what could be the problem? I created this script to load the scanner.o module modprobe scanner vendor=0x0458 product=0x2017 got vendor and product from KDE Info Center (USB devices)... what could be wrong? thanx for your help! :) _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From rene.rebe at gmx.net Mon Jun 30 09:49:09 2003 From: rene.rebe at gmx.net (Rene Rebe) Date: Mon, 30 Jun 2003 10:49:09 +0200 (CEST) Subject: [sane-devel] HP 7450C ... addendum In-Reply-To: <1056948336.3460.127.camel@localhost.localdomain> References: <20030627211110.GM2318@meier-geinitz.de> <20030629.232524.607955671.rene.rebe@gmx.net> <1056948336.3460.127.camel@localhost.localdomain> Message-ID: <20030630.104909.730551847.rene.rebe@gmx.net> Hi, On: 29 Jun 2003 21:45:37 -0700, Thomas Frayne wrote: > On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: > > > Which host controller chip and respective kernel driver is this? [...] > Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase > 0xf0870000, IRQ 5 > Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC > Corporation USB Ah - ohci! The ohci driver in the kernel should be fine. It works with my SiS based Athlon boards and my iBook ... (in the last weeks I notices many problems with the two uhci drivers in general - not related to SANE/Avision). > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB > 2.0 > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem > f087a000 > Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, > assigned bus number 3 > Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size set > incorrectly (32 bytes) by BIOS/FW. > Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size > corrected to 128. > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, > EHCI 0.95, driver 2003-Jan-22 Hm - or ehci? Could you send the output of lsusb? > > If communication via libusb is not reliable for you, you still can use > > the "deprecated" hpusbscsi driver in the kernel - but _not_ the > > scanner driver. > > > I've tried so many configuration variations over the last couple of > weeks that I've gotten confused about what configuration settings do > what. I don't think I understand the terminology. Ok - I rephrase it: There is a generic USB scanner driver in the kernel. The resulting module is named scanner.o. This driver does not work with Avision/HP scanners. You should no try to force it's loading. Instead you should use access via libusb. Libusb is a normal library (libusb.so in /usr/lib or so) which allows low-level access to usb devices from user-space applications. This library is automatically used when the permissions in /proc/bus/usb/0*/* allow you to access the device. But unfortunately this results in strance timeouts on your system. So as short time soluion and test you could try: Access via the "depricated" hpusbscsi driver. It is a kernel driver which name is hpusbscsi.o. It was written to access Avision and HP usb scanners via an emulated SCSI interface (/dev/sg?). When the hpusbscsi module is loaded the scanner would look like a scsi device. > I now think I should avoid using the scanner driver. Would > rmmod scanner > do this for me, or is something else necessary? How can I tell whether > or not I am using the scanner driver? lsmod lists the loaded kernel modules. A rmmod scanner does only unload the driver until the next reboot. You need to modify the place where it gets loaded on your distribution (maybe hotplug so /etc/hotplug ...) or you "simply" remove the scanner.o file in /lib/modules//... from your disk (if you do not have other USB scanners that needs to be accessed via the module ...) > I would like to use libusb, but I have not been able to figure out what > causes the libusb driver to be loaded. Some parts of my system refer to There is no libusb "driver" - it is a normal user-space library. Youl only need the usbfb mounted to /proc/bus/usb - and the permissions must allow your user to access the device. > usbfs; others refer to usbdevfs. I think I need everything in the > system refering to one or everything to the other, but when I tried > changing the usbdevfs references to usbfs, I produced a system that > would not boot, and had to restore a backup. If RedHat likes the usbdevfs name simply leave it as it is. usbdevfs and usbfs are the same. (That one alias is depricate and will disappear in the future does only need to wory RedHat - not you) > What is the best way to get back to a clean system? > Is there a modprobe command I should be using to load the libusb > driver? If so, should I add it to /etc/rc.d/rc.local to get it to run > during boot? As written above - only usbfs need to be mounted and the permissions needs to be correct. Nothing else - no kernel driver. > My guess is that > modprobe scanner vendor=0x03f0 product=0x0801 > should be added to /etc/rc.d/rc.local. Is that right? If so, what > else needs to be done? Nope - please do not force to load the not SANE/Avision compatible scanner driver. > What should be done to get the scanner mounted as rw with permissions > for everyone to use it? The things I have tried with fstab did not > work, since the system tried to mount it twice. > > I currently have hpusbbscsi disabled. Should both libusb and hpusbbscsi > be enabled? You can use hpusbscsi - it should work fine - but when you use the new libusb access method - the hpusbscsi module should not be loaded. Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene.rebe at gmx.net http://www.rocklinux.org http://www.rocklinux.org/people/rene http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From renito73 at hotmail.com Mon Jun 30 11:00:46 2003 From: renito73 at hotmail.com (Renito 73) Date: Mon, 30 Jun 2003 10:00:46 +0000 Subject: [sane-devel] Genius Vivid-3xe part II Message-ID: Finally I did it, just forgot the firmware file and now is fixed, but I have a doubt... xsane has 8/12 bit depth, does it mean the bpp? this model supports up to 24 or 36 (don't remember) but is it compile configuration related, or it is a driver limitation or what it means? sorry if it is a stupid question again but it is 5am and can't sleep fine if I leave something pending :P Regards _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From mfleming at michaelfleming.webcentral.com.au Mon Jun 30 11:47:42 2003 From: mfleming at michaelfleming.webcentral.com.au (Michael Fleming) Date: Mon, 30 Jun 2003 20:47:42 +1000 Subject: [sane-devel] Genius Vivid-3xe In-Reply-To: References: Message-ID: <20030630104742.GA5090@michaelfleming.webcentral.com.au> On Mon, Jun 30, 2003 at 08:44:43AM +0000, Renito 73 waffled thusly: > I have troubles to use my Genius Vivid-3xe scanner... sane recognizes it, > but applications don't use it... my usb configuration is working properly > since I took pictures with my webcam... I did chmod rwxrwxrwx > /dev/usb/scanner* since only root had access to the devices... my usb > driver is usb-uhcii.o (the other one uhci.o worked fine but my vmware did > not work with it, so I changed to usb-uhci.o instead but camera and vmware > continued working fine... > > Background: Let's compare notes - I've got the same model and make working fine, even for regular users. (Redhat 9.0, sane-backends 1.0.12, kernel 2.4.20-18.9 (RH Errata vendor kernel)) > reno at voodoo:~$ sane-config --version > 1.0.12 defender:~:$ sane-config --version 1.0.12 > reno at voodoo:~$ sane-find-scanner > found USB scanner (vendor=0x0458, product=0x2017) at libusb:001:004 (3xe) > found USB scanner (vendor=0x046d, product=0x0840) at libusb:001:002 (webcam) defender:~:$ sane-find-scanner | grep ^found found USB scanner (vendor=0x0458, product=0x2017 [600dpi USB Scanner]) at libusb:001:002 > reno at voodoo:~$ scanimage -L > device `gt68xx:/dev/usb/scanner0' is a Genius Colorpage Vivid3xe flatbed > scanner I'm not using the scanner.o module, never had much luck with it. libusb 0.1.6 works well enough for me. defender:~:$ scanimage -L device `gt68xx:libusb:001:002' is a Genius Colorpage Vivid3xe flatbed scanner > but when running xsane or kooka they say scanner is not round... what could > be the problem? I created this script to load the scanner.o module > > modprobe scanner vendor=0x0458 product=0x2017 Have you tried actually scanning an image? I really don't see any permissions or access related problems. (I had to remount my /proc/bus/usb devmode=0666 to enable user access, but that might be a Redhat-only issue. YMMV.). You can at least find the scanner as a user, which is encouraging. What happens when you run "scanimage > out.pnm"? > got vendor and product from KDE Info Center (USB devices)... > > what could be wrong? Do you see lots of "bulk_timeout"-like messages among your syslog entries when you try and scan or run xsane/kooka? There was a small patch for the gt68xx backend back in late April that addressed a USB timeout issue (it saw the scanner but subsequent operations seemed to overwhelm the USB bus on many systems). Check the archives for this, apply and recompile if you haven't got it. It worked spectacularly well for me. > thanx for your help! :) Cheers, Michael Fleming. (PS Henning, the colour handling/matching on this backend and the Genius Vivid3XE seems to be OK in my tests/experience, I'll put some more examples if you wish) -- Michael Fleming "Bother" said the Borg, "We've assimilated Pooh!" From sigurd.stordal at stud.ibg.uit.no Mon Jun 30 14:49:37 2003 From: sigurd.stordal at stud.ibg.uit.no (Sigurd Stordal) Date: Mon, 30 Jun 2003 15:49:37 +0200 Subject: [sane-devel] Problems with the canon backend for a canoscan 2700F. In-Reply-To: <20030624174224.GB7697@meier-geinitz.de> References: <200306241556.48630.sigurd.stordal@stud.ibg.uit.no> <20030624174224.GB7697@meier-geinitz.de> Message-ID: <200306301549.43807.sigurd.stordal@stud.ibg.uit.no> Will work with sane-backend 1.0.11. So something has to have changed from .11 to .12 that makes the canon backend not work for my filmscanner. So, maybe take a look at what has changed from .11 to .12, to find out possible reasons for this. -- Sigurd Stordal President of GOGS Experimental Petrologist From tomf at sjpc.org Mon Jun 30 16:44:13 2003 From: tomf at sjpc.org (Thomas Frayne) Date: 30 Jun 2003 08:44:13 -0700 Subject: [sane-devel] HP 7450C ... addendum In-Reply-To: <20030630.104909.730551847.rene.rebe@gmx.net> References: <20030627211110.GM2318@meier-geinitz.de> <20030629.232524.607955671.rene.rebe@gmx.net> <1056948336.3460.127.camel@localhost.localdomain> <20030630.104909.730551847.rene.rebe@gmx.net> Message-ID: <1056987852.3718.109.camel@localhost.localdomain> Please read the procedure at the end of this note before looking at the interleaved comments. On Mon, 2003-06-30 at 01:49, Rene Rebe wrote: > Hi, > > On: 29 Jun 2003 21:45:37 -0700, > Thomas Frayne wrote: > > > On Sun, 2003-06-29 at 14:25, Rene Rebe wrote: > > > > > Which host controller chip and respective kernel driver is this? > > [...] > > > Jun 29 07:33:06 localhost kernel: usb-ohci.c: USB OHCI at membase > > 0xf0870000, IRQ 5 > > Jun 29 07:33:06 localhost kernel: usb-ohci.c: usb-00:0b.0, NEC > > Corporation USB > > Ah - ohci! The ohci driver in the kernel should be fine. It works with > my SiS based Athlon boards and my iBook ... (in the last weeks I > notices many problems with the two uhci drivers in general - not > related to SANE/Avision). Is there anything I should be doing about this? > > > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: NEC Corporation USB > > 2.0 > > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: irq 10, pci mem > > f087a000 > > Jun 29 07:33:06 localhost kernel: usb.c: new USB bus registered, > > assigned bus number 3 > > Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size set > > incorrectly (32 bytes) by BIOS/FW. > > Jun 29 07:33:06 localhost kernel: PCI: 00:0b.2 PCI cache line size > > corrected to 128. > > Jun 29 07:33:06 localhost kernel: ehci-hcd 00:0b.2: USB 2.0 enabled, > > EHCI 0.95, driver 2003-Jan-22 > > Hm - or ehci? > > Could you send the output of lsusb? [root at localhost root]# lsusb Unknown line at line 58 Unknown line at line 2296 Unknown line at line 2297 Unknown line at line 2298 Unknown line at line 2299 Unknown line at line 2300 Unknown line at line 2301 Unknown line at line 2302 Unknown line at line 2303 Unknown line at line 2304 Unknown line at line 2305 Unknown line at line 2306 Unknown line at line 2307 Unknown line at line 2308 Unknown line at line 2309 Unknown line at line 2310 Unknown line at line 2311 Unknown line at line 2312 Unknown line at line 2313 Unknown line at line 2314 Unknown line at line 2315 Unknown line at line 2316 Unknown line at line 2317 Unknown line at line 2318 Unknown line at line 2319 Unknown line at line 2320 Unknown line at line 2321 Unknown line at line 2322 Unknown line at line 2323 Unknown line at line 2324 Unknown line at line 2325 Unknown line at line 2326 Unknown line at line 2327 Unknown line at line 2328 Unknown line at line 2329 Unknown line at line 2330 Unknown line at line 2331 Unknown line at line 2332 Unknown line at line 2333 Unknown line at line 2334 Unknown line at line 2335 Bus 004 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 iProduct 2 USB UHCI Root Hub iSerial 1 9000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 8 bInterval 255 Language IDs: (length=4) 0000 (null)((null)) Bus 004 Device 002: ID 03f0:0801 Hewlett-Packard Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 0 Interface bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x03f0 Hewlett-Packard idProduct 0x0801 bcdDevice 0.01 iManufacturer 1 hp iProduct 2 hp scanjet 7400c iSerial 3 87 tem 7400c bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 0 Interface bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type none wMaxPacketSize 8 bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 8 bInterval 10 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 2 Transfer Type Bulk Synch Type none wMaxPacketSize 64 bInterval 0 Language IDs: (length=4) 0409 English(US) Bus 003 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.04 iManufacturer 3 Linux 2.4.20-18.9 ehci-hcd iProduct 2 NEC Corporation USB 2.0 iSerial 1 00:0b.2 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 2 bInterval 12 Language IDs: (length=4) 0000 (null)((null)) Bus 003 Device 002: ID 03f3:0081 Adaptec, Inc. cannot get string descriptor 1, error = Broken pipe(32) cannot get string descriptor 2, error = Broken pipe(32) Is there anything I should do about this? Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 1 bMaxPacketSize0 64 idVendor 0x03f3 Adaptec, Inc. idProduct 0x0081 bcdDevice 1.00 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 1 bInterval 12 Language IDs: (length=4) 0409 English(US) Bus 003 Device 003: ID 03f0:3404 Hewlett-Packard Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 Interface bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x03f0 Hewlett-Packard idProduct 0x3404 bcdDevice 1.00 iManufacturer 1 hp iProduct 2 deskjet 6122 iSerial 3 MY2771C0ZP50 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower 2mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 7 Printer bInterfaceSubClass 1 Printer bInterfaceProtocol 2 Bidirectional iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type none wMaxPacketSize 64 bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type none wMaxPacketSize 64 bInterval 0 Language IDs: (length=4) 0409 English(US) Bus 002 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 iProduct 2 USB OHCI Root Hub iSerial 1 f0872000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 2 bInterval 255 Language IDs: (length=4) 0000 (null)((null)) Bus 001 Device 001: ID 0000:0000 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 iProduct 2 USB OHCI Root Hub iSerial 1 f0870000 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x40 Self Powered MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type none wMaxPacketSize 2 bInterval 255 Language IDs: (length=4) 0000 (null)((null)) [root at localhost root]# This seems to say that bus 004 is a USB UHCI hub and Bus 004 Device 002: ID 03f0:0801 Hewlett-Packard is my Scanjet. Does that imply that the Scanjet is using UHCI? > > > > If communication via libusb is not reliable for you, you still can use > > > the "deprecated" hpusbscsi driver in the kernel - but _not_ the > > > scanner driver. > > > > > > I've tried so many configuration variations over the last couple of > > weeks that I've gotten confused about what configuration settings do > > what. I don't think I understand the terminology. > > Ok - I rephrase it: > > There is a generic USB scanner driver in the kernel. The resulting > module is named scanner.o. This driver does not work with Avision/HP > scanners. You should no try to force it's loading. Instead, I'll try to force it not to be loaded, e.g., by renaming scanner.o. Right? > > Instead you should use access via libusb. Libusb is a normal library > (libusb.so in /usr/lib or so) which allows low-level access to usb > devices from user-space applications. This library is automatically > used when the permissions in /proc/bus/usb/0*/* allow you to access > the device. But unfortunately this results in strance timeouts on your > system. So as short time soluion and test you could try: > [root at localhost root]# ls -l /proc/bus/usb/004/* -rw-r--r-- 1 root root 18 Jun 30 06:51 /proc/bus/usb/004/001 -rw-r--r-- 1 root root 18 Jun 30 06:51 /proc/bus/usb/004/002 [root at localhost root]# chmod 666 /proc/bus/usb/004/* [root at localhost root]# ls -l /proc/bus/usb/004/* -rw-rw-rw- 1 root root 18 Jun 30 06:51 /proc/bus/usb/004/001 -rw-rw-rw- 1 root root 18 Jun 30 06:51 /proc/bus/usb/004/002 [root at localhost root]# Right? > Access via the "depricated" hpusbscsi driver. It is a kernel driver > which name is hpusbscsi.o. It was written to access Avision and HP usb > scanners via an emulated SCSI interface (/dev/sg?). When the hpusbscsi > module is loaded the scanner would look like a scsi device. I currently have hpusbscsi.o renamed to disable it. I'll leave it disabled for now, and try to use libusb. If I see > > > I now think I should avoid using the scanner driver. Would > > rmmod scanner > > do this for me, or is something else necessary? How can I tell whether > > or not I am using the scanner driver? > > lsmod lists the loaded kernel modules. A rmmod scanner does only > unload the driver until the next reboot. You need to modify the place > where it gets loaded on your distribution (maybe hotplug so > /etc/hotplug ...) or you "simply" remove the scanner.o file in > /lib/modules//... from your disk (if you do not have other > USB scanners that needs to be accessed via the module ...) > > > I would like to use libusb, but I have not been able to figure out what > > causes the libusb driver to be loaded. Some parts of my system refer to > > There is no libusb "driver" - it is a normal user-space library. Youl > only need the usbfb mounted to /proc/bus/usb - and the permissions > must allow your user to access the device. > > > usbfs; others refer to usbdevfs. I think I need everything in the > > system refering to one or everything to the other, but when I tried > > changing the usbdevfs references to usbfs, I produced a system that > > would not boot, and had to restore a backup. > > If RedHat likes the usbdevfs name simply leave it as it is. usbdevfs > and usbfs are the same. (That one alias is depricate and will > disappear in the future does only need to wory RedHat - not you) > > > What is the best way to get back to a clean system? > > Is there a modprobe command I should be using to load the libusb > > driver? If so, should I add it to /etc/rc.d/rc.local to get it to run > > during boot? > > As written above - only usbfs need to be mounted and the permissions > needs to be correct. Nothing else - no kernel driver. > [root at localhost root]# mount /dev/sdb2 on / type ext2 (rw) none on /proc type proc (rw) usbdevfs on /proc/bus/usb type usbdevfs (rw) I am still confused here. You said to leave usbdevfs as it is, but you also said that libusb times out. Should I try libusb first, and try hpusbscsi if libusb fails? When modprobe scanner vendor=0x03f0 product=0x0801 was in effect, scanimage -L failed, but after rmmod scanner, I got: [root at localhost root]# scanimage -L device `avision:libusb:004:002' is a Hewlett-Packard ScanJet 7400c flatbed scanner [root at localhost root]# However, When I tried to scan with xsane, it failed with a timeout. Is this the libusb failure you were refering to? I'd like to try hpusbscsi without rebooting. The procedure to do this, as I currently understand it is: Turn off the scanner to clear the "initializing" state Rename back to hpusbscsi.o Don't do a modprobe; do an rmmod scanner to make sure. Modify /etc/rc.d/rc.local to remove the modprobe at the next boot Modify /usr/local/etc/sane.d/avision.conf to remove the usb lines and insert: scsi AVISION scsi HP scsi hp scsi /dev/scanner scsi /dev/usb/scanner0 umount /proc type proc mount what? Anything wrong, redundant, or missing? > > What should be done to get the scanner mounted as rw with permissions > > for everyone to use it? The things I have tried with fstab did not > > work, since the system tried to mount it twice. > > > > I currently have hpusbbscsi disabled. Should both libusb and hpusbbscsi > > be enabled? > > You can use hpusbscsi - it should work fine - but when you use the new > libusb access method - the hpusbscsi module should not be loaded. Should libusb be disabled when I am trying to use hpusbscsi? If so, how should I disable libusb? > > Sincerely yours, > Ren? Rebe > - ROCK Linux stable release maintainer > > -- > Ren? Rebe - Europe/Germany/Berlin > rene at rocklinux.org rene.rebe at gmx.net > http://www.rocklinux.org http://www.rocklinux.org/people/rene > http://gsmp.tfh-berlin.de/gsmp http://gsmp.tfh-berlin.de/rene From anoah at pfeiffer.edu Mon Jun 30 17:20:03 2003 From: anoah at pfeiffer.edu (m. allan noah) Date: Mon, 30 Jun 2003 12:20:03 -0400 (EDT) Subject: [sane-devel] Re: fujitsu patch, was: The report about 'sane-fujitsu' In-Reply-To: Message-ID: re-sending gzip'd due to file size.... > attached is a (rather large) patch to the cvs version of the fujitsu > backend. i am sending it to the list cause the backend maintainer is on > vacation, and so this wont be committed to cvs for a while, and i know > there are some fujitsu users outthere looking for some of this > functionality... (wink, wink, nudge, nudge :) > > 1. re-structured color mode code to support other modes (me, not finished) > 2. added code to select the various color read modes of some scanners (me) > 3. added code to support rrggbb mode of fi-4340 (oliver s.) > 4. moved a good bit of code so it is under the correct headings (me) > > allan > -- "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 -------------- next part -------------- A non-text attachment was scrubbed... Name: man-fujitsu-patch7.txt.gz Type: application/octet-stream Size: 10710 bytes Desc: URL: From henning at meier-geinitz.de Mon Jun 30 17:34:25 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 30 Jun 2003 18:34:25 +0200 Subject: [sane-devel] Re: Visioneer 5800 In-Reply-To: <20030629.215242.2373.604481@webmail01.lax.untd.com> References: <20030629.215242.2373.604481@webmail01.lax.untd.com> Message-ID: <20030630163425.GA634@meier-geinitz.de> Hi, On Mon, Jun 30, 2003 at 04:51:42AM +0000, jollyprince at juno.com wrote: > On Sun, 2003-06-29 at 20:38, jollyprince at juno.com wrote: > > T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 > > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > > P: Vendor=04a7 ProdID=0226 Rev= 1.00 > > S: Manufacturer=Visioneer > > S: Product=USB Scanner > > S: SerialNumber=RTS8801C2-004 > > C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA > > I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=ff Driver=(none) > > E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms > > E: Ad=02(O) Atr=02(Bulk) MxPS= 8 Ivl=0ms > > E: Ad=83(I) Atr=03(Int.) MxPS= 1 Ivl=250ms > > > > RESULT: of cat /proc/bus/usb/devices | more > > > > Realtek chip, see www.realtec.com.tw at page scanner ic > some info is given about the chip. Also looks like Visioneer 4800, 5300 and 8920. Bye, Henning From henning at meier-geinitz.de Mon Jun 30 17:39:52 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 30 Jun 2003 18:39:52 +0200 Subject: [sane-devel] Fw: RTS8801C2 Serial Number Chipset In-Reply-To: <20030629.215444.2373.604497@webmail01.lax.untd.com> References: <20030629.215444.2373.604497@webmail01.lax.untd.com> Message-ID: <20030630163952.GB634@meier-geinitz.de> Hi, On Mon, Jun 30, 2003 at 04:54:00AM +0000, jollyprince at juno.com wrote: > I'm researching technical data to write a driver for a Visioneer 5800 > Scanner. The above serial number was referenced when checking out > the Visioneer 5800 specs. > > Am I on the right track and can you provide me with some help on this project? Looks like a realtek chipset. The other Visioneer scanners seem to use the B version. Here is some info: http://www.realtek.com.tw/products/products1-1.aspx?lineid=10 The links are dead for me but maybe you can ask realtek for details. I'll update our lists. Bye, Henning From henning at meier-geinitz.de Mon Jun 30 17:52:19 2003 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 30 Jun 2003 18:52:19 +0200 Subject: [sane-devel] Genius Vivid-3xe part II In-Reply-To: References: Message-ID: <20030630165219.GC634@meier-geinitz.de> Hi, On Mon, Jun 30, 2003 at 10:00:46AM +0000, Renito 73 wrote: > Finally I did it, just forgot the firmware file and now is fixed, but I > have a doubt... xsane has 8/12 bit depth, does it mean the bpp? Bits per pixel per color. > this model supports up to 24 or 36 (don't remember) Bits per color. In color mode: 12 * 3 = 36. Voila. Bye, Henning From jollyprince at juno.com Mon Jun 30 19:48:13 2003 From: jollyprince at juno.com (jollyprince at juno.com) Date: Mon, 30 Jun 2003 18:48:13 GMT Subject: [sane-devel] Fw: RTS8801C2 Serial Number Chipset Message-ID: <20030630.114820.754.154095@webmail06.lax.untd.com> --- Henning Meier-Geinitz wrote: Hi, On Mon, Jun 30, 2003 at 04:54:00AM +0000, jollyprince at juno.com wrote: > I'm researching technical data to write a driver for a Visioneer 5800 > Scanner. The above serial number was referenced when checking out > the Visioneer 5800 specs. > > Am I on the right track and can you provide me with some help on this project? Looks like a realtek chipset. The other Visioneer scanners seem to use the B version. Here is some info: http://www.realtek.com.tw/products/products1-1.aspx?lineid=10 I found it at: http://www.realtek.com.tw/products/products1-2.aspx?modelid=37 The links are dead for me but maybe you can ask realtek for details. I'll update our lists. Bye, Henning _______________________________________________ Sane-devel mailing list Sane-devel at www.mostang.com http://www.mostang.com/mailman/listinfo/sane-devel From karsten.festag at gmx.de Mon Jun 30 21:08:30 2003 From: karsten.festag at gmx.de (Karsten Festag) Date: Mon, 30 Jun 2003 22:08:30 +0200 Subject: [sane-devel] negative-scan In-Reply-To: <1056815865.14723.11.camel@christoph.local> References: <1056815865.14723.11.camel@christoph.local> Message-ID: <200306302208.30947.karsten.festag@gmx.de> Hi, that sounds like a problem with my backend :-( I'll have to check the code for the lamp control, but I'm afraid I can't do this before August. Regarding the negativ-preview: I think this might be a frontend feature for xsane and the other frontends (..requesting comments..) Karsten On Saturday 28 June 2003 17:57, Christoph Knauer wrote: > Hi, > > i've a litle problem with scanning negatives on an microtek scanmaker x6 > / phantom 636 with lightlid35 when i set the option using lightlit or > toggle lamp. with "toggle the lamp" the scannerlam goes out, but when i > push the button scan, it goes on again, and setting "use lightlid35" > seems to do nothing. > > btw. why there is no "negativ"-format to set for preview? > > greetings, christoph > > _______________________________________________ > Sane-devel mailing list > Sane-devel at www.mostang.com > http://www.mostang.com/mailman/listinfo/sane-devel From Oliver.Schwartz at gmx.de Mon Jun 30 22:24:47 2003 From: Oliver.Schwartz at gmx.de (Oliver Schwartz) Date: Mon, 30 Jun 2003 23:24:47 +0200 Subject: [sane-devel] Re: Sane-devel digest, Vol 1 #503 - 1 msg In-Reply-To: <1056821890.4190.34.camel@daisy.localdomain> References: <20030628132618.13633.99099.Mailman@panda.mostang.com> <1056821890.4190.34.camel@daisy.localdomain> Message-ID: <200306302324.48935.Oliver.Schwartz@gmx.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > According to the Sourceforge page > (http://snapscan.sourceforge.net/), the Acer/Benq 3300 uses either > the "u222v067.bin" or "u176v046.bin" firmware files. Looking at the > CD that came with the scanner I find the first one (u222v067.bin), > but not the second one: The firmware file for the Acer 3300 depends on the USB ID. For 0x04a5, 0x20b0 it's u176v...bin. The last three digits are the version number, the latest version I know of is u176v046.bin. However, using u176v042.bin should work as well. Using u222v67 will not work for your model. - -Oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE/AKqf/V6sbrmfIuMRArE2AJ9GBx4HZAKowpIb1/OUIgDBZ98O/QCggRU0 urfv/DMt64GSYA2MpWxmMl8= =8qz/ -----END PGP SIGNATURE----- From rsv869 at adelphia.net Fri Jun 6 04:53:02 2003 From: rsv869 at adelphia.net (Reid Vail) Date: Thu, 05 Jun 2003 23:53:02 -0400 Subject: [sane-devel] messed up HP6350 USB Scanje config? In-Reply-To: <3E02B406.7010801@kirchgessner.net> References: <3E02AB22.2010409@adelphia.net> <3E02B406.7010801@kirchgessner.net> Message-ID: <3EE0101E.6010604@adelphia.net> About six months ago Peter gave me some advice about my HP6350c scanner. It fixed my issue and got it working. (I included that exchange at the bottom of this message). Recently I upgraded my Suse box to Suse 8.2 and it's not working again. I dug out the mail and checked the config. Looks OK to me, and I included a few scraps. I've included the output from sane-find-scanner. The permissions also look OK, too, I think. Any suggestions would be great. thx Reid reid at linux:~>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=0x03f0, product=0x0601) at libusb:001:002 # A USB device was detected. This program can't be sure if it's really # a scanner. If it is your scanner, 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. reid at linux:/etc/sane.d> ls -l hp.conf -rwxrwxrwx 1 root root 480 2003-06-05 21:14 hp.conf reid at linux:~> ls -l /etc/sane.d/dll.conf -rw-rw-rw- 1 root root 448 2002-12-18 00:16 /etc/sane.d/dll.conf dll.conf . . # dc210 # dc240 # dc25 # dll # dmc # epson hp # fujitsu # leo # microtek # microtek2 # mustek_usb # mustek # matsushita . . reid at linux:/etc/sane.d> more hp.conf #scsi HP # Uncomment the following if you have "Error during device I/O" on SCSI # option dumb-read # # The usual place for a SCSI-scanner on Linux # # USB-scanners supported by the hp-backend # HP ScanJet 4100C usb 0x03f0 0x0101 # HP ScanJet 5200C usb 0x03f0 0x0401 # HP ScanJet 62X0C usb 0x03f0 0x0201 # HP ScanJet 63X0C usb 0x03f0 0x0601 # # Uncomment the following if your scanner is connected by USB, # but you are not using libusb /dev/usb/scanner option connect-device reid at linux:/etc/sane.d> Peter Kirchgessner wrote: > Hi, > > pleae have a look at /etc/sane.d/hp.conf or > /usr/local/etc/sane.d/hp.conf. It must have two lines in it: > > /dev/usbscanner > option connect-device > > In dll.conf (same directories) the line with "hp" must be active. > You may need to set the permissions: > > chmod 666 /dev/usbscanner > > More hints can be found at http://www.kirchgessner.net/sanehpfaq.html > > Sincerely > > Peter > > Reid Vail schrieb: > >> I've been trying for a least a month to get an HP6350c USB Scanjet to >> work. I'm running a SuSE 8.1 Personal distro, which comes with a SANE >> implementation of 1.0.8-47. >> >> I think (but can't say for sure) that some part of the install of the >> unit (via YAST) isn't working because it doesn't even "test" >> correctly. However YAST does correctly identify it. >> >> When I run xscanimage I get this output: >> >> [xscanimage] No scanners were identified. If you were expecting >> something different, check that the scanner is plugged in, turned on and >> detected by sane-find-scanner (if appropriate). Please read the >> documentation which came with this software (README, FAQ, manpages). >> >> But when I run sane-find-scanner I get this output: >> >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = >> 0x0601) at device /dev/usb/scanner0 >> sane-find-scanner: found USB scanner (vendor = 0x03f0, product = >> 0x0601) at device /dev/usbscanner >> >> I make no claims that I'm not missing something obvious! I just >> don't get it. For what it's worth, I know the unit works because it >> runs under Windoze 2K. >> >> Thanks in advance. >> >> Reid Vail >> >> _______________________________________________ >> Sane-devel mailing list >> Sane-devel at www.mostang.com >> http://www.mostang.com/mailman/listinfo/sane-devel >> > >