From ukd@xenon.pc.Uni-Koeln.DE Tue Jun 1 08:15:54 2004 From: ukd@xenon.pc.Uni-Koeln.DE (Ulrich Deiters) Date: Tue, 1 Jun 2004 09:15:54 +0200 (METDST) Subject: [sane-devel] Canon FS4000 support Message-ID: <200406010715.JAA11254@xenon.pc.Uni-Koeln.DE> I once had an opportunity to look at an SCSI protocol of a FS4000. The protocol differs significantly from those of the SCSI flatbed scanners and the older film scanners. Moreover, there appear several SCSI commands which my handbook lists as "proprietary/undocumented". Reverse engineering will therefore require much experimental work. And who knows - perhaps Canon built some unconventional commands into the scanner ("eject light bulb", "burn the slide") to discourage people like us? :-) Regards, Ulrich Deiters From gilles@ffii.org Tue Jun 1 12:14:42 2004 From: gilles@ffii.org (gilles@ffii.org) Date: Tue, 1 Jun 2004 13:14:42 +0200 Subject: [sane-devel] HP5370C still not working Message-ID: <20040601111441.GA8138@ffii.org> Hello. In January, I reported that the HP5370C, supported by the "avision" back-end, was not behaving correctly (producing an image skewed by a 45 degree angle). I retried yesterday, and to my deep disappointment, the scanner doesn't even go that far anymore: trying scanimage -d avision:libusb:002:007 > image.pnm the scanner tray moves a little (but in the wrong direction), and after some 3 seconds, the light starts flashing. Best regards, Gilles P.S. Rene Rebe answered my previous post by offering to test newer, but I must have overlooked his mail at the time; sorry for that. Anyway, I've upgraded since then: Debian GNU/Linux 2.6.5 scanimage (sane-backends) 1.0.14; backend version 1.0.14 libusb-0.1-4 udev O.024 From henning@meier-geinitz.de Tue Jun 1 14:58:18 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 1 Jun 2004 15:58:18 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601111441.GA8138@ffii.org> References: <20040601111441.GA8138@ffii.org> Message-ID: <20040601135818.GC12076@meier-geinitz.de> Hi, On Tue, Jun 01, 2004 at 01:14:42PM +0200, gilles@ffii.org wrote: > I retried yesterday, and to my deep disappointment, the scanner > doesn't even go that far anymore: trying > > scanimage -d avision:libusb:002:007 > image.pnm > > the scanner tray moves a little (but in the wrong direction), > and after some 3 seconds, the light starts flashing. > Debian GNU/Linux 2.6.5 There have been reports about USB trouble with Linux 2.6.5 and 2.6.6. I don't know if that's valid for all USB scanners. As far as I can see the reports are mostly about Epson scanners. Nevertheless, have a look at syslog and check for bulk timeouts/errors. I'm using Linux 2.6.7-rc2 and don't see any USB errors but I'm using Mustek and Plustek scanners only and haven't tested 2.6.5 or 2.6.6. Bye, Henning From cward@go-integral.com Tue Jun 1 19:05:01 2004 From: cward@go-integral.com (Chris Ward) Date: Tue, 1 Jun 2004 13:05:01 -0500 Subject: [sane-devel] JSane Message-ID: <439FB88065E2FF4DB75E6DC5E19C2B2A087FBD@ibsmmex001.go-integral.net> Rainer, If there is any type of java scanning API, let Andi and I know. We = aren't aware of any. I have been trying to use the existing japi classes = for some time now, and they are kind of broken. Andi's classes look = interresting, and I would like to try them soon (if I can ever get a = saned damon running). Chris Ward >Hello Andi, > >isn't there a standard scanning API for Java? There could be >immplementations for twain AND for sane. > >Just my 2cents, >Rainer > From rene@rocklinux-consulting.de Tue Jun 1 19:41:44 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Tue, 01 Jun 2004 20:41:44 +0200 (CEST) Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601111441.GA8138@ffii.org> References: <20040601111441.GA8138@ffii.org> Message-ID: <20040601.204144.291475760.rene@rocklinux-consulting.de> Hi, On: Tue, 1 Jun 2004 13:14:42 +0200, gilles@ffii.org wrote: > Hello. > = > In January, I reported that the HP5370C, supported by the = > "avision" back-end, was not behaving correctly (producing > an image skewed by a 45 degree angle). > = > I retried yesterday, and to my deep disappointment, the scanner > doesn't even go that far anymore: trying > = > scanimage -d avision:libusb:002:007 > image.pnm > = > the scanner tray moves a little (but in the wrong direction), > and after some 3 seconds, the light starts flashing. Oh. I never heared of s.th. like that. If it is ok for you I schedule a review of your logs for the weekend - I have two very important other things to do first ... > Best regards, > Gilles > = > P.S. Rene Rebe answered my previous post by offering to test > newer, but I must have overlooked his mail at the time; > sorry for that. > Anyway, I've upgraded since then: > = > Debian GNU/Linux 2.6.5 > scanimage (sane-backends) 1.0.14; backend version 1.0.14 > libusb-0.1-4 > udev O.024 Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene@rocklinux-consulting.de Tue Jun 1 19:43:23 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Tue, 01 Jun 2004 20:43:23 +0200 (CEST) Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601135818.GC12076@meier-geinitz.de> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> Message-ID: <20040601.204323.466679361.rene@rocklinux-consulting.de> Hi, On: Tue, 1 Jun 2004 15:58:18 +0200, Henning Meier-Geinitz wrote: > Hi, > = > On Tue, Jun 01, 2004 at 01:14:42PM +0200, gilles@ffii.org wrote: > > I retried yesterday, and to my deep disappointment, the scanner > > doesn't even go that far anymore: trying > > = > > scanimage -d avision:libusb:002:007 > image.pnm > > = > > the scanner tray moves a little (but in the wrong direction), > > and after some 3 seconds, the light starts flashing. > = > > Debian GNU/Linux 2.6.5 > = > There have been reports about USB trouble with Linux 2.6.5 and 2.6.6.= > I don't know if that's valid for all USB scanners. As far as I can se= e > the reports are mostly about Epson scanners. > Nevertheless, have a look at syslog and check for bulk timeouts/error= s. > = > I'm using Linux 2.6.7-rc2 and don't see any USB errors but I'm using > Mustek and Plustek scanners only and haven't tested 2.6.5 or 2.6.6. Thanks for this hints Henning. Gilles, could you check if you hit this USB errors? Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From insane@piments.com Tue Jun 1 21:41:29 2004 From: insane@piments.com (insane@piments.com) Date: Tue, 01 Jun 2004 22:41:29 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601.204323.466679361.rene@rocklinux-consulting.de> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> Message-ID: I'm not sure how much of this can be laid at the door of "USB", I think it is more specifically trouble with SANE backends. I had wasted probably weeks trying to get my cannon FB630U to work under 2.6x kernels until some helpful sole suggested I try vuescan. This worked beautifully straight out of the box and produces better results that I had got with the sane backend when it did work under 2.4 I would like to work with open source solutions but there is a limit to how much time I can reasonably spend on a broken driver (and I have already over-stepped that mark by an order of magnitude. ) Emails to the maintainer remain unanswered. Big thanks to the guy who made me aware of vuescan. Regards to all. On Tue, 01 Jun 2004 20:43:23 +0200 (CEST), Rene Rebe wrote: > Hi, > > On: Tue, 1 Jun 2004 15:58:18 +0200, > Henning Meier-Geinitz wrote: >> Hi, >> >> On Tue, Jun 01, 2004 at 01:14:42PM +0200, gilles@ffii.org wrote: >> > I retried yesterday, and to my deep disappointment, the scanner >> > doesn't even go that far anymore: trying >> > >> > scanimage -d avision:libusb:002:007 > image.pnm >> > >> > the scanner tray moves a little (but in the wrong direction), >> > and after some 3 seconds, the light starts flashing. >> >> > Debian GNU/Linux 2.6.5 >> >> There have been reports about USB trouble with Linux 2.6.5 and 2.6.6. >> I don't know if that's valid for all USB scanners. As far as I can see >> the reports are mostly about Epson scanners. >> Nevertheless, have a look at syslog and check for bulk timeouts/errors. >> >> I'm using Linux 2.6.7-rc2 and don't see any USB errors but I'm using >> Mustek and Plustek scanners only and haven't tested 2.6.5 or 2.6.6. > > Thanks for this hints Henning. Gilles, could you check if you hit this > USB errors? > > Sincerely yours, > René Rebe > - ROCK Linux stable release maintainer > > -- > René Rebe - Europe/Germany/Berlin > rene@rocklinux.org rene@rocklinux-consulting.de > http://www.rocklinux.org http://www.rocklinux-consulting.de > > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request@lists.alioth.debian.org > -- Using M2, Opera's e-mail client: on Gentoo Linux From henning@meier-geinitz.de Tue Jun 1 21:52:43 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 1 Jun 2004 22:52:43 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> Message-ID: <20040601205243.GD12076@meier-geinitz.de> Hi, On Tue, Jun 01, 2004 at 10:41:29PM +0200, insane@piments.com wrote: > I'm not sure how much of this can be laid at the door of "USB", I think it > is more specifically trouble with SANE backends. If several sane backends fail with two specific kernel versions and those backends worked with older kernel versions then the conclusion that it might be a kernel issue isn't far-fetched. If you have facts that there is a bug in the backends that only showed up because of kernel changes, please tell us. Just to make one point clear: There is no general problem with SANE concerning Linux 2.6. > I had wasted probably weeks trying to get my cannon FB630U to work under > 2.6x kernels until some helpful sole suggested I try vuescan. Can someone else confirm that the canon630u backend does not work on Linux 2.6? So we can either add a warning about trouble with Linux 2.6 for this scanner? > I would like to work with open source solutions but there is a limit to > how much time I can reasonably spend on a broken driver (and I have > already over-stepped that mark by an order of magnitude. ) I'm sorry for that. Could you please send a summary of the problems and possible solutions/work-arounds you have found until now? Or if you have already done that, could you point me to that posting? This way your effort isn't wasted and other people with similar problems don't need to try the same things. > Emails to the maintainer remain unanswered. Unfortunately sometimes maintainers just vanish or ignore requests because they are not interested in the project any longer. I don't like that either but writing software is just a hobby for most people so it's understandable. The last change by Nathan Rutman in SANE CVS was on 2003-12-01, so at least at that hime he was still active. Bye, Henning From gilles@ffii.org Tue Jun 1 22:56:56 2004 From: gilles@ffii.org (gilles@ffii.org) Date: Tue, 1 Jun 2004 23:56:56 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601.204323.466679361.rene@rocklinux-consulting.de> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> Message-ID: <20040601215656.GA3524@ffii.org> Hi. > > > > There have been reports about USB trouble with Linux 2.6.5 and 2.6.6. > > Thanks for this hints Henning. Gilles, could you check if you hit this > USB errors? > When the command SANE_DEBUG_AVISION=7 scanimage -d avision:libusb:001:002 -l 5mm -t 5mm -x 15mm -y 15mm was run, here is the result from "tail -f kern.log" (so, the lines corresponding to the "scanimage" itself start at "Jun 1 17:49:11"): [...] Jun 1 17:44:30 dawn kernel: usb 1-1: registering 1-1:1.0 (config #1, interface 0) Jun 1 17:44:30 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:45:09 dawn kernel: usb 1-1: control timeout on ep0in Jun 1 17:45:09 dawn kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 1 17:45:10 dawn kernel: usb 1-1: control timeout on ep0in Jun 1 17:45:10 dawn kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 1 17:45:32 dawn kernel: usb 1-1: control timeout on ep0in Jun 1 17:45:32 dawn kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 1 17:45:33 dawn kernel: usb 1-1: control timeout on ep0in Jun 1 17:45:33 dawn kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 1 17:49:11 dawn kernel: usb 1-1: usb_disable_device nuking non-ep0 URBs Jun 1 17:49:11 dawn kernel: usb 1-1: unregistering interface 1-1:1.0 Jun 1 17:49:11 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:49:11 dawn kernel: usb 1-1: registering 1-1:1.0 (config #1, interface 0) Jun 1 17:49:11 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:49:12 dawn kernel: usb 1-1: usb_disable_device nuking non-ep0 URBs Jun 1 17:49:12 dawn kernel: usb 1-1: unregistering interface 1-1:1.0 Jun 1 17:49:12 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:49:12 dawn kernel: usb 1-1: registering 1-1:1.0 (config #1, interface 0) Jun 1 17:49:12 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:49:50 dawn kernel: usb 1-1: bulk timeout on ep3in Jun 1 17:49:50 dawn kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x83 len 4096 ret -110 [...] The "scanimage" didn't complete (and wasn't doing anything other than make the scanner produce clicking sounds) so that I had to "kill" it. Many thanks for trying to help. Gilles From oschirr@abm.de Wed Jun 2 18:23:13 2004 From: oschirr@abm.de (Oliver Schirrmeister) Date: Wed, 2 Jun 2004 19:23:13 +0200 Subject: [sane-devel] Fi-4120c duplex color In-Reply-To: <4092663a44c4e@wp.pl> References: <4092663a44c4e@wp.pl> Message-ID: <200406021923.13293.oschirr@abm.de> Am Freitag 30 April 2004 16:44 schrieb Krzysztof Cieniuch: > Hi, > > Is it possible to scan duplex in color with this scanner ? > I've tried scanadf --rif=yes --duplex=both --resoluton=72 -d > fujitsu:/dev/sg0 > but i've ended up with one properly scaned image and one > totally black. Is this feature missing in fujitsu backend ? > In what time if ever will be this functionality available in > fujitsu backend ? > That was a bug in the fujitsu backend. I've fixed that, checkout the latest version. Oliver From faxguy@howardsilvan.com Wed Jun 2 21:32:40 2004 From: faxguy@howardsilvan.com (Lee Howard) Date: Wed, 2 Jun 2004 13:32:40 -0700 Subject: [sane-devel] Fujitsu papersize problems, sane-backends-1.0.14 Message-ID: <20040602203240.GI12815@bilbo.x101.com> Hello. I have a Fujitsu M4097Ddm and am using sane-frontends-1.0.12 and sane-backends-1.0.14. I am having trouble when using the --papersize options other than A4/Letter. If I do: scanimage --source ADF --papersize Autodetect or: scanadf --source ADF --papersize Autodetect I get: sane_start: Invalid argument If I use "--papersize Legal" then the scanning is performed, but the image files are only letter/A4 size; the image is truncated at the bottom. I haven't tried any other options, but I would guess that all --papersize options other than letter/A4 will not result as expected. Is this something that is a known bug? Is it fixed in a development version? I'd be happy to provide verbose debugging information if it will help. Thanks. Lee. From Franz Bakan" On Sat, 29 May 2004 17:21:06 +0200, Henning Meier-Geinitz wrote: ... >> What do you think? Could this script be added to >> sane-backends/ >> or >> sane-backends/backend/ > >What about tools/? There is already a script called by the Makefile. >You could call it from backend/Makefile if the install target is run >on OS/2. tools/ is fine. >I'd change the license to just GPL. E.g. at the moment, nobody is >allowed to use your script (only copy, distribute and modify it) :-) Change it to what you think is best. I am not shure if a license is necessary at all for such a short script, but I'm not a lawyer and don't know if there are sane-project-specific rules for these things. Ciao Franz From martin@mkcollins.org Thu Jun 3 09:07:19 2004 From: martin@mkcollins.org (Martin Collins) Date: Thu, 3 Jun 2004 09:07:19 +0100 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <20040530043040.5034a5e2.martin@mkcollins.org> References: <20040530043040.5034a5e2.martin@mkcollins.org> Message-ID: <20040603090719.45d7eb5b.martin@mkcollins.org> Can anyone (khk, Olaf) confirm that the GT10000 with ADF is supposed to be supported by a sane backend? If not what can I do to help it to become supported? Martin From olaf@epkowa.co.jp Thu Jun 3 10:35:38 2004 From: olaf@epkowa.co.jp (Olaf Meeuwissen) Date: Thu, 03 Jun 2004 18:35:38 +0900 Subject: [sane-devel] Epson GT10000 and ADF problems References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> Message-ID: <87aczloufp.fsf@zen.epkowa.co.jp> Martin Collins writes: > Can anyone (khk, Olaf) confirm that the GT10000 with ADF is supposed to > be supported by a sane backend? > If not what can I do to help it to become supported? Sorry Martin. I meant to follow up but forgot about it. As far as "Image Scan! for Linux" is concerned: 1.2.0 added support for the GT10000 1.5.1 added ADF support so you would say it should work. Our Q&A group has tested ADF support of this scanner for iscan-1.5.1 and didn't find any problems. However, it has not been tested since, so a bug *may* have crept in in a later release. Looking at the diff I don't see anything obvious though. Not much help, I'm afraid. -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From faxguy@howardsilvan.com Thu Jun 3 15:36:13 2004 From: faxguy@howardsilvan.com (Lee Howard) Date: Thu, 3 Jun 2004 07:36:13 -0700 Subject: [sane-devel] Fujitsu papersize problems, sane-backends-1.0.14 In-Reply-To: <200406031403.57151.oschirr@abm.de>; from oschirr@abm.de on Thu, Jun 03, 2004 at 05:03:56 -0700 References: <20040602203240.GI12815@bilbo.x101.com> <200406031403.57151.oschirr@abm.de> Message-ID: <20040603143613.GS12815@bilbo.x101.com> On 2004.06.03 05:03 Oliver Schirrmeister wrote: > Am Mittwoch 02 Juni 2004 22:32 schrieb Lee Howard: > > Hello. > > > > I have a Fujitsu M4097Ddm and am using sane-frontends-1.0.12 and > > sane-backends-1.0.14. > > > > I am having trouble when using the --papersize options other than > > A4/Letter. > > > > If I do: > > > > scanimage --source ADF --papersize Autodetect > > > > or: > > > > scanadf --source ADF --papersize Autodetect > > > > I get: > > > > sane_start: Invalid argument > > Seems that autodetect doesn't work with the 4097. I've tried that > option with > the 3093 but it wasn's reliable. Oh, alright. By your comments here I assume that --papersize is used solely to indicate to the ADF the size of the paper that it is supposed to pull through, but does not indicate the size of the area that is to be scanned. Is this correct? I don't really understand the value of the --papersize option, then, since the scanner seems to deal with mixed-size and other-size paper regardless of what --papersize option I use. E.g., if I use --papersize Letter, then it seems to be quite happy about scanning Letter and Legal sized paper mixed in the ADF. > > If I use "--papersize Legal" then the scanning is performed, but the > > image files are only letter/A4 size; the image is truncated at the > > bottom. > > > > Did you set the -x and -y option? These options specify the scanning > area. > The default of x and y is 210x297 mm (A4). > papersize specifies the page you enter in the adf (centered). -l -t -x > -y is > the scanning area relative to that page. No, I did not set -l -t -x -y. I had thought (hoped) that my --papersize indication would have made those indicators superfluous. I see now that's not the case. Thanks. Lee. From oschirr@abm.de Thu Jun 3 16:53:26 2004 From: oschirr@abm.de (Oliver Schirrmeister) Date: Thu, 3 Jun 2004 17:53:26 +0200 Subject: [sane-devel] Fujitsu papersize problems, sane-backends-1.0.14 In-Reply-To: <20040603143613.GS12815@bilbo.x101.com> References: <20040602203240.GI12815@bilbo.x101.com> <200406031403.57151.oschirr@abm.de> <20040603143613.GS12815@bilbo.x101.com> Message-ID: <200406031753.26352.oschirr@abm.de> Am Donnerstag 03 Juni 2004 16:36 schrieb Lee Howard: > > > I am having trouble when using the --papersize options other than > > > A4/Letter. > > > > > > If I do: > > > > > > scanimage --source ADF --papersize Autodetect > > > > > > or: > > > > > > scanadf --source ADF --papersize Autodetect > > > > > > I get: > > > > > > sane_start: Invalid argument > > > > Seems that autodetect doesn't work with the 4097. I've tried that > > option with > > the 3093 but it wasn's reliable. > > Oh, alright. > > By your comments here I assume that --papersize is used solely to > indicate to the ADF the size of the paper that it is supposed to pull > through, but does not indicate the size of the area that is to be > scanned. Is this correct? Correct. > I don't really understand the value of the --papersize option, then, > since the scanner seems to deal with mixed-size and other-size paper > regardless of what --papersize option I use. E.g., if I use > --papersize Letter, then it seems to be quite happy about scanning > Letter and Legal sized paper mixed in the ADF. Your scanner has a DIN A3 ADF and you use those plastic bars (how are they called?) to center your letter sized paper. The origin of the scanning area (-x -y -l -t) is 0/0 in the picture below if you use --papersize Letter, not the left side of the A3 ADF. | <----------- DIN A3 ---------->| | | 0/0 | | | | <- Letter -> | | | | | | | | | | | | If you put mixed-size paper in the adf with different paper width (e.g letter and A5) you'll more likely get a paper jam and the A5 paper will probably be skewed. The resulting image of the A5 paper will have letter size if -x and -y are set to letter size. I think this subject is better described in one of that guides of your scanner (have a look at the fujitsu home page). -- Oliver From martin@mkcollins.org Thu Jun 3 23:03:32 2004 From: martin@mkcollins.org (Martin Collins) Date: Thu, 3 Jun 2004 23:03:32 +0100 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <87aczloufp.fsf@zen.epkowa.co.jp> References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> Message-ID: <20040603230332.3dd7a5f6.martin@mkcollins.org> On Thu, 03 Jun 2004 18:35:38 +0900 Olaf Meeuwissen wrote: > As far as "Image Scan! for Linux" is concerned: > > 1.2.0 added support for the GT10000 > 1.5.1 added ADF support The Ekpowa website doesn't offer 1.5.1 for download. Is there an FTP site or something? Martin From olaf@epkowa.co.jp Fri Jun 4 00:50:38 2004 From: olaf@epkowa.co.jp (Olaf Meeuwissen) Date: Fri, 04 Jun 2004 08:50:38 +0900 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <20040603230332.3dd7a5f6.martin@mkcollins.org> (Martin Collins's message of "Thu, 3 Jun 2004 23:03:32 +0100") References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> Message-ID: <873c5c19rl.fsf@zen.epkowa.co.jp> Martin Collins writes: > On Thu, 03 Jun 2004 18:35:38 +0900 > Olaf Meeuwissen wrote: > >> As far as "Image Scan! for Linux" is concerned: >> >> 1.2.0 added support for the GT10000 >> 1.5.1 added ADF support > > The Ekpowa website doesn't offer 1.5.1 for download. Is there an FTP > site or something? Unfortunately, there is no FTP site or something. # And I much dislike company policy not to provide old versions :-( If you don't mind getting an RPM in the mail ... it's about 450kB. -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From martin@mkcollins.org Fri Jun 4 01:12:10 2004 From: martin@mkcollins.org (Martin Collins) Date: Fri, 4 Jun 2004 01:12:10 +0100 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <873c5c19rl.fsf@zen.epkowa.co.jp> References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> <873c5c19rl.fsf@zen.epkowa.co.jp> Message-ID: <20040604011210.240e6d85.martin@mkcollins.org> On Fri, 04 Jun 2004 08:50:38 +0900 Olaf Meeuwissen wrote: > If you don't mind getting an RPM in the mail ... it's about 450kB. No problem, I'd prefer the tar.gz though. Thanks Martin From olaf@epkowa.co.jp Fri Jun 4 01:35:08 2004 From: olaf@epkowa.co.jp (Olaf Meeuwissen) Date: Fri, 04 Jun 2004 09:35:08 +0900 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <20040604011210.240e6d85.martin@mkcollins.org> (Martin Collins's message of "Fri, 4 Jun 2004 01:12:10 +0100") References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> <873c5c19rl.fsf@zen.epkowa.co.jp> <20040604011210.240e6d85.martin@mkcollins.org> Message-ID: <87smdcyxc3.fsf@zen.epkowa.co.jp> Martin Collins writes: > On Fri, 04 Jun 2004 08:50:38 +0900 > Olaf Meeuwissen wrote: > >> If you don't mind getting an RPM in the mail ... it's about 450kB. > > No problem, I'd prefer the tar.gz though. Alright, I'll send the tarball for gcc-3.2 (or later) in a separate mail. -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From c0sga4a@euskalnet.net Fri Jun 4 15:48:58 2004 From: c0sga4a@euskalnet.net (JKD) Date: Fri, 4 Jun 2004 16:48:58 +0200 Subject: [sane-devel] planning to write abackend for HP scanjet 3970 Message-ID: <20040604144858.GA3006@JKDSoft.cjb.net> Hello every one, I'm new in this list. I own an HP Scanjet 3970 and I'm planning to write a backend for this scanner. I would like to know if anybody has started to analyze usb protocol of this scanner or if there is any developer who is already working on it. Sincerely, JKD From robelsner@ngfc.com Sat Jun 5 04:25:04 2004 From: robelsner@ngfc.com (Rob Elsner) Date: Fri, 04 Jun 2004 21:25:04 -0600 Subject: [sane-devel] Want to write HP 4570c Driver RFI Message-ID: <1086405903.5792.4087.camel@linux.site> Hello. I've tried to find out the current status of a driver for this scanner, but haven't seen anything on it. I would be interested in writing said driver, if anyone has any information about what needs to be done. Since I've just started trying to use it in Linux, I've gathered no developer info. There is some mention of it being compatible/similar to GL841/GL646, but sane doesn't seem to think so, at least for me. Will look into this. Rob Elsner From henning@meier-geinitz.de Sat Jun 5 10:49:07 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 11:49:07 +0200 Subject: [sane-devel] OS/2 specific patch for sane-backends/backend/dll.c References: <20040529152106.GA30272@meier-geinitz.de> Message-ID: <20040605094907.GC19373@meier-geinitz.de> Hi, On Wed, Jun 02, 2004 at 10:31:30PM +0200, Franz Bakan wrote: > On Sat, 29 May 2004 17:21:06 +0200, Henning Meier-Geinitz wrote: > >What about tools/? There is already a script called by the Makefile. > >You could call it from backend/Makefile if the install target is run > >on OS/2. > > tools/ is fine. I've added the script to the tools directory. If you want to call it automatically from backend/Makefile please send a patch for the install traget that only executes when os2 is used. > >I'd change the license to just GPL. E.g. at the moment, nobody is > >allowed to use your script (only copy, distribute and modify it) :-) > > Change it to what you think is best. I am not shure if a license is > necessary at all for such a short script, but I'm not a lawyer and > don't know if there are sane-project-specific rules for these things. Better add a license to everything to avoid discussions. I've used GPL in this case. Please check if the script still works. By the way, your website says: "Optionally you can remove support for scanners you don't need to make compiling faster and libsane.dll smaller. For this purpose you have to modify sane-backends-1.0.14/backend/Makefile.in and remove the scanners you don't need from the list which starts with: PRELOADABLE_BACKENDS = " That doesn't work anymore. Just run configure like this: BACKENDS="net mustek whatever" ./configure Or modify backend/Makefile after it was generated by configure. Also "--enable-translations" has been the default setting for some time now. Bye, Henning From henning@meier-geinitz.de Sat Jun 5 10:53:12 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 11:53:12 +0200 Subject: [sane-devel] canon lide 80 In-Reply-To: References: Message-ID: <20040605095312.GD19373@meier-geinitz.de> Hi, On Sun, May 30, 2004 at 07:56:07PM +0200, Mark Pustjens wrote: > i wanted to confirm that the canon lide 80 indeed has the GL841 chip > > output from sane-find-scanner -v -v: > > found USB scanner (vendor=0x04a9 [Canon], product=0x2214 [CanoScan], chip=GL841) at libusb:003:004 Thanks. I've added that to our lists. Bye, Henning From henning@meier-geinitz.de Sat Jun 5 11:02:40 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 12:02:40 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086025927.11981.15.camel@yoda> References: <1086025927.11981.15.camel@yoda> Message-ID: <20040605100240.GE19373@meier-geinitz.de> Hi, On Mon, May 31, 2004 at 10:52:11AM -0700, Keith Clayton wrote: > I'm at a bit of a loss as to how I can troubleshoot this further. > Unfortunately I don't have another linux box on my small network that I > can test with to determine whether the problem is with win32-xsane or > rather with saned. You have one, you just don't know :-) What happens if you scan over the local net? E.g. "scanimage -d net:localhost:plustek"? You can enable debugging on the client by using "export SANE_DEBUG_NET=255". On the server, disable saned in (x)inetd.conf, and start it manually e.g. like this for max debugging: SANE_DEBUG_PLUSTEK=255 saned -d255 This way you have to restart saned after each connection. > Any pointers for troubleshooting this further would be much appreciated! Maybe little/big endian problems? But in this case the first scan should also fail. Bye, Henning From henning@meier-geinitz.de Sat Jun 5 11:05:27 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 12:05:27 +0200 Subject: [sane-devel] planning to write abackend for HP scanjet 3970 In-Reply-To: <20040604144858.GA3006@JKDSoft.cjb.net> References: <20040604144858.GA3006@JKDSoft.cjb.net> Message-ID: <20040605100527.GF19373@meier-geinitz.de> Hi, On Fri, Jun 04, 2004 at 04:48:58PM +0200, JKD wrote: > I'm new in this list. I own an HP Scanjet 3970 and I'm planning > to write a backend for this scanner. I would like to know if anybody has > started to analyze usb protocol of this scanner or if there is any > developer who is already working on it. At least I don't remember anyone trying to write a backend. So go ahead :-) Please tell us when you have some more information, e.g. logs, chipset details, documentation. Put that info on a website so we can link to it. Thanks and good luck, Henning From henning@meier-geinitz.de Sat Jun 5 11:09:50 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 12:09:50 +0200 Subject: [sane-devel] Want to write HP 4570c Driver RFI In-Reply-To: <1086405903.5792.4087.camel@linux.site> References: <1086405903.5792.4087.camel@linux.site> Message-ID: <20040605100950.GG19373@meier-geinitz.de> Hi, On Fri, Jun 04, 2004 at 09:25:04PM -0600, Rob Elsner wrote: > There is some mention of it being compatible/similar to GL841/GL646, but > sane doesn't seem to think so, at least for me. There is no test for the HP variant of the GL841 in sane-find-scanner yet. So as a first step you may have a look at tools/check-usb-scanner.c, copy the tests for the gl841 to e.g. gl841_hp, modify them so the scanner is detected. If the test that sends actual commands works it's most probably a GL841. See also the gl646/gl646_hp tests for an example. Please tell us about the result and send a patch when you are ready. Good luck! Bye, Henning From martin@mkcollins.org Sat Jun 5 18:01:07 2004 From: martin@mkcollins.org (Martin Collins) Date: Sat, 5 Jun 2004 18:01:07 +0100 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <87smdcyxc3.fsf@zen.epkowa.co.jp> References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> <873c5c19rl.fsf@zen.epkowa.co.jp> <20040604011210.240e6d85.martin@mkcollins.org> <87smdcyxc3.fsf@zen.epkowa.co.jp> Message-ID: <20040605180107.3dda0c3e.martin@mkcollins.org> On Fri, 04 Jun 2004 09:35:08 +0900 Olaf Meeuwissen wrote: > Alright, I'll send the tarball for gcc-3.2 (or later) in a separate > mail. Thanks for that. However it wouldn't make. Some C++ library or header mismatch. Could be my GTK is too new. In the process I discovered I had a tarball of 1.5.2 on one of my machines. That did compile cleanly but didn't work in a similar way to 1.8.1 I will try to get 1.5.1 compiled and do some testing later this week. Martin From keith@claytons.org Sat Jun 5 19:00:23 2004 From: keith@claytons.org (Keith Clayton) Date: Sat, 05 Jun 2004 11:00:23 -0700 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040605100240.GE19373@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> Message-ID: <1086458420.26103.10.camel@yoda> --=-Jqb2DeyKptpZmhWla+bp Content-Type: text/plain Content-Transfer-Encoding: 7bit Ooops . . sorry Henning . . meant to send my reply to the list rather than directly to you. Ok . . reply . . take 2. Thanks for the reply Henning. Most helpful. Here's some results of testing. scanimage -d net:localhost:plustek works perfectly. Can scan as many times consecutively as I'd like. win32-xsane continues to fail on the 2nd scan. After power-cycling the scanner I ran win32-xsane first then scanimage from the local machine. Scanimage failed in this case. First pass of win32-xsane is evidently leaving the scanner in a bad state. Used the debug flags as you suggested and captured the output. Something is definitely going wrong at the end of the win32-xsane/saned scan. I've attached the gzip output of running saned as you suggested with debugging on and xinetd disabled. I X'd out any host, IP info from the top of the log files but otherwise they're exactly what the debug kicked out. I'm sure your busy . . seems like we all are! but if you could take a peek the the logs at some point it would be most appreciated. >From there, if you've got any other suggestions, let me know and I'll give it a shot. Thanks! Keith On Sat, 2004-06-05 at 12:02 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Mon, May 31, 2004 at 10:52:11AM -0700, Keith Clayton wrote: > > I'm at a bit of a loss as to how I can troubleshoot this further. > > Unfortunately I don't have another linux box on my small network that I > > can test with to determine whether the problem is with win32-xsane or > > rather with saned. > > You have one, you just don't know :-) > > What happens if you scan over the local net? E.g. > "scanimage -d net:localhost:plustek"? > > You can enable debugging on the client by using > "export SANE_DEBUG_NET=255". On the server, disable saned in > (x)inetd.conf, and start it manually e.g. like this for max debugging: > > SANE_DEBUG_PLUSTEK=255 saned -d255 > > This way you have to restart saned after each connection. > > > Any pointers for troubleshooting this further would be much appreciated! > > Maybe little/big endian problems? But in this case the first scan > should also fail. > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request@lists.alioth.debian.org --=-Jqb2DeyKptpZmhWla+bp Content-Disposition: attachment; filename=local_scan.txt.gz Content-Type: application/x-gzip; name=local_scan.txt.gz Content-Transfer-Encoding: base64 H4sICPoBwkAAA2xvY2FsX3NjYW4udHh0AOxce3PbOJL/fz8FprbqYs9KMt961Dh1ju1kfOuHKnIm SaVSPkqEbG4kUktSdnyffrsBUOZTpBxmJrzA5cQS0Wg2Gv3CjyA+hbZHnc9kabveiISRHUSud0sc Ol3fkqXvULK3oPd0QTTT3P/bpxR1FDwibeSTWxqRlR9EZO4HJKTBvTuj5H+R+AXZg0bbcQLXm/tZ Dp+UzyT0Z1+g+94+WYfI7mx8b5WTzW13QZ0ROQKONAzh+9JdPBLPj0i4XqEM1CHTR7IK/Mif+Yss J7XwhkYRGY2Q0l8haUH71PUcZALDZ0O3TCsnN5At3DCiXp7Fg+0yTaPGZr4XBf4C/3p0Frm+tyFm f8je0esu3I6u/oHa2SfzwF+ypu7UhsF4TkjUntJTDRJQ23nc9J7d0dmXmzs/jEbEns1QYaCbgC79 iBJ+WdX60BP6FnZKkBI3JGeXN+dXV+NXR8f/3DC8DWwPlL7p7nputFMjavBD7ue/84LBnGK/m4D+ e01RuqQOxcVy4lswEfGFaOVkQjaQCezLXwdoyKvFGibxy4v0cNwb5iWfyYRGCafh7uLPieiFrMB5 en/7JC58JmPRIiaP/KH0jH5XVTtkBf6HfYvmNsHg5d9jHt3J0eUpeSUYgQHN3dt1YKMNkTm4ym/p Xq9BU+uQkgc3uiPnF8OBrh5oBzpIEsJEvJu8IuHMBiMMwnTH1LcMT2rP7mDszOc9SkFeOwIt2KDn 6MEHB/BoOMr06ZJP63D6mdyD1H7QPTshNogPk+GsZxF8zZEL/vyPZy+zA3N7tMfsINbtnvJV6b/S 98m7a1U7UK0DzWDXFLW/n+nLReH0hJNkKMTdD+DvARALHWWI/OwF0WvhTqHPaDqdjhzHydA83NGA EmhD94ru4OM69NbLKQ2YRqADuxqrl7VkWCztLxSCH7CJ7kDzj2C0OMcBubPDhDkfoKkfAHscwQHc 8SAnTYYxRG0XDcleQIQFtgSGTcIVnbnzR4iiS0ogOEJ7mB2THSzXqw5ZXM3nV96p58BHe7mCb1tv h7ZpryPIOREPgjiKoql6xuTkpoqE7nK1eKxmn+/pzpkyHiAUEFvow53FYkzXbApA+fcwXz5xHWoT e+rDZZjIYtE9zLPAGfuhd3KL6QgZMRPFjrLdTWobMqp56zAvr65PR5nZAAMN7TntEDArN0JBucVi YscLEGAzXPgPS1ZIyMLLeho+AsGyR86YHl8ElGVvnovzKuI/KUk6TFEX7ybXXMt2FEEIwkSC9s+H WMxFeAcI0sWc3dl4DGck5pI6vV6vbvzLmYxHv8ZCcB2lZE8Qwk2SxOURNmuC3OlYtEO1rgLo769D pl8KlcTj1u4hxH4I2OiRkGnmxJ5HECu+fv0KdjYLO0Qhjhva04WY3Tm1I4gtKSZcgtipia4oyeYT OvMdnExB9rLI+QtDBlnRwPUdsCiUxYfUh+IsqQ2jBVfiREWSiO6quVWOgv4ZMeKbQfYCc0C5u1AS R6DbtRf5azSyDrPWmFAo08+GNgL3wxx+M1v4YbHy4uBI1O3Ki+m2yF1iIBD0owdqf+FeurRvKS/w wfZDFtgz/fbeH729PLt8M8IOAX3BlO5CwRNACiBQ+gADVhz+8ssv+1sliE3T84MldMWQTGwoTbd0 EuMF0WDAH8h2ixJU5Qw+1mLwcZstsDHAoEOoyag3c2lYdLtoZdeQV1CVM6iSV1BVyevRWyj97otF hcYaogqqcgZVogqq+ubK14y8hEajmdmQ/0QJG0aBuyLN2yvpqsKDMd9O1+4C1jdeLfOc3Nk43o/A osrEYtKSea/LKUFaMi11OSVI689PhEq9p0HEXTo2sVqZolCJnNtlzKjCnjLUO8kdQhg/gHVc5EOV MfPtIEybl2NHNWLSDKuLY3txAtQV0TpJWl9StEF7wew2SgsYQN2I66dqIaH/caLjdp2miauiSvjF Xa2w+8Odv8j6Jy1MyNglKc52rWWoa8sDxY4LEzsHDW2X6u9Fkw/1rON7hckZ7/AauW5XY0y2TWBw kZkd8FUcWOJ6wdb3zF/wBg93bnrKt4nznhFX63JDW6XJgK4W9iwOvLc2FF739mJNsbhc4/JzHUBj VpXbhQ2oc8M4kapoFFMWcbkNKPU4nwouT5RFfKYwGiFOBZ8N5W6Zy3b+BRdiFTp0buMU39rLpS10 We27oIg3rEP8o/a2G17coVRzSXZVzJ46lCkwJVwVu02HYuHsx524bTrsFPeph2mJXI+PyJ4HbMa8 Way0QqjOF4/ZiiAu6eMpnFJYE7q4XIT17mZliGsTvugVZUbEEmCGV1xccDmqDYDTobjbtbGhq68N BAwg4MxgICFNYEndPIhWjBVsw1VK4ISN3DG+AbeCpJMFHapmEWYCQ6QNNceDYNXhKxiOX/KGkC+s swhjBZTDMQOyh0JBJfO1P5/Pp3Nd6YDBuIv9/dRo2CBS2Ooo0Z4cJBnlx4low9mJsPdRetj4hGVB /Pugx9qURJNY08bdVDNMNMZLb9EIK/B8I19djsgjTfZMFTPZxkRdQKHR8xNtT0m6R3IdNwmTy5Pr uMlI2Y6b6i7s5TpCBX3zlWw0oGSaHsubQl7k3jyOIOon2qB4LeOITSUcsamMI9TmZRyxqYQjNpVx hNhORP7Ebqk2Fqrj1kwbxt1NxwKeaBWI9xTzFK1FPOOOBTw3oXyEgVzJcRXtuVbGN+5c0Nd+LG/t Fv0k2sHvwWNv/BX1uHcnffkoicX1esmHMse4UoyfJiGGOtW7DENV6hCpdYj6dYjMxjjpjRHVGl0t PRmNqaAWJ6sxZdYhUmoRzRsjak5P2hYiQ1GASFWUbRO8IdpmKvWIzAEQaduVuSEa1CEa1iDa6ggb om0a3xBtMzp9jipQzK1zJ4isrUTGFG8Hbpc0ldd82SbKsoi8FA8fQeUjGGKy9PiDPVEiZyeHyOzV oEPG/LmSuKQqr9NR1fVvTljoZM+Nv25tHIkFJPumHSR1y8kgefBHWuS/4udZcN8R4bJ0c/c/iZ// hrPA5dUw6uFliv43ftdeWrQb3HQA/fd0rcP11umqBQXe+6PX7P7sx7AzTDjSfw658MPe1eWh0oEq /DDFZsKfBSAJ8OlAgrwNPylfzeFncsj4Jmjfnr6BJkXjTYOkP+Aq4PLqmjhCT/kp40tOtnECysnT VZheiHPe5pTzVodkbxl+gRkdKElpz48uxt3J9dH1u8nTqDMyTk6vr88u3yDHs8n16dvJXlpxcfv1 76fk4mxyTM4OrpLFXXxNPGNiDPFmhoolt2Hg/+n4lIBncPcCW6Sw558w1GQtfxD4fnTQw0csB0wB 3TEN5jyt36iaqdyM7/zI783sxW+ZiZzQaAJLmbEdAG8QK9xLDulX8vvJ+GxEBr20Mn4lH+D6oWrC xCLFYZ7g44bgwvXg80f8kqLAmnvsfqWLCS5iDq1hh5xDYQxlOnzeRtlXnij7Ctk7OvmfpNAvXxJo 6XLapIApnq/XiwWZRHTFngxNoCrHCME6CQPNdEDaift/dG8cUJiDfaDSdJXvoqD9tNZQpYgMzdYL Nn1hurj6lYl/Tr3b6O5QVfp9iw/oLSw0jv2FHxyquVuHcGu4pdU3mbVYGJQ0/NSHT7ae1tf4hBya pjVA6VRzpuwXNGsKb4ZAvd9hICHBexyyO+DXUAvo/aGe1sJiQb1Y5EVa5A75dzTzmMrv5uxDxtbe 0Oji+PyfJ+6969AgY2hnXkRvhbFfu2DnR8yvcS7I3pONdRiHQwM/Z3QuHpq8wVp7/P7iZB09Hj/O FvTcf0gRHq+DgHoRQU5ECAO3YSyzk35xdX31titYhyMCfJniO/jp5uTd9UeWHNKW9To2FTQRC9QB AcgYiLin8q9xGDRSXcd3j68eIxpCpX9ItGwTmohoskwoQ019kCK59iN7wfsfEhNWwZqu9K00l/ND bQjzO/PpfM6mW1NhJkOwVZq1urG9Dum5u3RxElgvFJxywYdiHPN4WNVxheHLmWyEa5NbCsvsVTrw TDi8wnZTBMscyCBC/4iwaJeMsQxBgIanAEgwAB6wAJgsDRb2bcgWokXB3gnu2aPqlExC3DDyVyhe URteh9izty+QGfSFlR18yboC0uZvwFGYkYBBDsnLwkEkIzh7qI5rO9Ilics8QnFvYAtHDsvh5lXv 0FCGVtpzju9Q2YtPyueOgGrVXDiPadQaNFoNGr2UpnBFm1nelm1XfNJHQKN14OHe2Mmabfr6Dvsm je/A05Q8JU9pn5Kn5Pn/mmf/6Z0GLBRu8HnSSGz7ZC9Q6JqqMLa4KyOb8lmfEpQ3jXGk8N6fGeTQ tZ1AjmeBC0YxuCCoRMlvqDGVMvh2CCI9rHcTbN0ADaII/CYQYkuRjjbLXoo6JHpxj8BfnUEFny2V cSV4hjswc43j8TkuNozkwuZ8fATX0ujBK0bXN5KSTgP39i7ycIO/0uFvEeFbFwWld8gXJ6fefU6y iX1Pi0VzHnDNsMEGEL6tO6pfsSK/d+kDW58wPAtE+CW53hHl+tJe4etddkQYMqw55mxWQqY+kelq OZmWIDPTZJsFDQST3Iomhn5UrQT7UWJopYCiCvz5c/2GQ5GokHO2zdvLzNs3g5lGdvWb4agyjkop R/WJo1DJMGnY79mz7y6iIgFPFykcNK3M4XdQZnJ4KPFGFH+1SoniPMxjHzGEj8A1BknAWhbxC+61 ycXq9dnFKYFbvr0uzHIMNaiXgDFTFr01uOWtNtaFv6uJ72Uk3rLbiILvENLgRjCJ9U/24I5fqLNf SjnavD4K93l7enTCb7anqqoFapmiUpK9p+s59wZw1OFwUBC2IIjg7uvYVcXoHF8UD9migOuQRjeQ qDFM434C72a68NmDkxTYkyUVSk+3Q0AHmgUo92bubG1Mz9lGQKEYVMnb8fGmFMK87nyXxYqVccsT PwGpp6Id9PKJ2IOw2WCddFfedAUpxvUgmiVn5wL6BhjwLAyJF/bXC/+eTlaUOodKb4DXnhBBhF07 HM891FJMEGgsxRfRn0z4pOKLTMZAkCCMyDw46U6Iat68fv0esWLS7b5EL07Vj5lBotXimxwJki+n 48nVpah9ltSLkgUE1At4i0/6AcI8vGBlr9mQwYhYAkPtgCfl0uNbcI8jz5lgJcE23KRmoEuwHbll tyRz18QHIAlyQnZ46JG6TfapChSlQYj4Io93aikxyoKxWuls/ln6QC/4W2PkzEUITE/qfvD91cfx 0WRSS+HqiGhPCk/pG4cyIh8+EIg0ikE0BT/AV36FKDZR56xNw+a+Q/Q+USyS4qACB9ViVCZRZkTt s88K9k58UeMP7DfFQQMOmo2MocXY/D8jBsrgEEUXvfQ5mc+LOOjAIdmY/Jy6b6kMBnDItKMXacTW CRv+gF0yRNtQxRGlOJioB8o0YBCTkStz1lVlo4BcChltaJTLYHEZQMcqdO+zvhaxB8QYEDFDvJdT xqGfGYWe+FxHD2fxBk2xJBiV2Ur8m7AVhYn8p9oK/CY/sz9N2Yoa/9a2FcEhZysFHJ5s5YnkWbZS +FvP4rO2siuH37rdfBR6dpL7K3JcgbBwIZZ2mJHWsL5JSHUjZOqt1SoZU5klXW2VPvZ4ygkRdJyR N3h2Rq7G19lKQM1fn5Vcd7LXBfur+RzCRcEN+LPM/PVhyXU7e716hPFavLhUuPTzVYJ4wSm5qp5l dJxFieptfvguK+DcpgY1tf9B1dStxMktEECsbd8EYQ5NLSlqinX1RgjbTnWY5DdCgAuxjRDqjMqN EN99IwQ3N7ETQtthJ8Tv7u1dirJkK4T2XbZCsKyQ3AqhpbdCpDczpLZCqMZQybY+7YYwzPRWidQ+ CKuvG4NMZ9wEYTxrE4TR+CYIDu6M4C9f5Kpm/LZ/snxDWHEMS13iguaZmU1Q2kH2hnC3VxSWqDlc 88JenfgP3sK3nYy9JWBTNDHMVKn2DZBK4vb8U31HsBagI1Gybp4lUKsItDRBbgiF8TxuFqt1ljhS vlG4wHoLCgsRDD9ZL1dkSuf4emwgFqNs0VdWLMf1qSiW+YLiT19Y2TZ2ojZ+ZgsrPS6W1e9dLBu8 VI/bCxZWti3adl5YKTWLZZABl7czHLSuYQ/tT1xYTezlakE/sv1EbGvmnqmQX9jjig55mKyXCBal bPAYTIvDWQg+vBDXuyt31gvshxfJHE4+HBpDiEwfeSXh0BWkyUHKdLmVshfZsAjy/IdkAQRh8mTl 9jav5GAoTbmuIHhMEqTqlHchDVIsII4XtT+WtF+yM5qu5iwyrecYY7RB6gETi+NjGiQoTEtLjtJ5 SCQDUpQQGAWrj8KYAhSXIkgkBU6QSwzAJMGB77Mz0nIkhWAE6SdQzsMfUHE6T2zyYjAOYqj8FsOM EEwfJ+I96ew+QNF87bM6jTXr+WaclOLpFAKcxy+n5YYQw1W5onsSv2au8zPMCjIP9mOZag8Hlc1A ZyHyPLq33QXuRjvzTt4eXaRuwV7Cc0NixzRb78FTQEe8Rp5+o2wjrFpDWLSl3GPA2reqN/j6/MTM o/DaMzW9m/CFs116oyym/3TqJWZMMlAHA/5oQ5zKyPdxJjizpwWMtsu74OMg1iPPPN2e4VguyUOA BwP0jVgSuDRbuFDn5js9BH4Z6Z+m0h9l7kDRipy7RlVqWUNNqrSd7mAOSzQt5+7ZKlWHllRpO93B MAyZ2ZtVqd5XZMJtqTtoQ1Nm9oZVqiky4bbUHVTDlJm94eWYsnO+jXuUabSEY6VGVa22RuuQfjtm oFtbB6oX22LVODfL38phFlH+dD4/UGVF2DgEIyvCtrqDZcmKsHEIRlaEbXUHU5UVYeMQzO4l4c+u 0h9l7nTLkpm9aQhGlQm3pe6gqZbM7E1DMKpMuC11B8vaNbFvepRMXRnHqqmz+rWxnlqkDewP2Y71 9J+H9QxqYz1FlD+K3QxUWRG21ef7uqwIGw+jsiJsqzuYA1kRNg7ByIqwre5g6DuXhD/93FVCMJpM uC11B23Ql5m9aQhGkwm3pe6g6iXLXjl3z147aDtDMFoFBFPCsRKC0etDMHVIvx2C2dSRJSMtqzOr RqpqtVGYQtKfzu8HiqwKG4dhZFXYVnewTFkVNg7DyKqwre5gKrIqbByG2bks/OlV+qPMnW4OZGZv GobRZcJtqTtoykBm9qZhmJI3TaRKf3h3MHdGQTY9SqaujGPV1JnD2nhPLdIG8B6zAu8p2dpdifdY 9fGeItIfxXYGiqwK2+r3fU1WhY3DMLIqbKs7mH1ZFTYOw8iqsK3uYGjy/LrGYRh5rFxb3UHry/Pr Godh5LFybXUHVZPn1zVdLO18hsimRxkMU8KxEoYx68MwdUgbgGGGFTBMiTVWjVRTasMwhaQ/nd/3 h7IqbByGkVVhW93BMmRV2DgMI6vCtrqDMZRVYeMwjDxarq3uoJvyDLvGYRh5tFxb3QFWUDKzNw3D yKPl2uoO5s4HlpgVpxqXcazEe+qfalyL9NvxHq3iWGPtmecaa/UPNi4k/VFspz+UVWFb/b6vyaqw cRhGVoVtdQezL6vCxmEYWRW21R0MTZ5j1zQMY8jj5drqDlpfnmPXNGYwlMfLtdUdVE2eY9d0wt35 HBGj4sDhMo5VGjXqHzhci7QBGKbixGHtmUcOa/XPHC4k/en8vj+UVWHTKlVlVdhWd7AMWRU2DcNY sipsqzsYQ1kVNq1SVR4v11Z30A15jl3TMIwlj5drqzuoQ3mOXdMqVeXxcm11B2PnA0uMitONyzhW 4j31TzeuRfrteI9ecbqxXlVn/nVzy1Wq1z9GuRZpFjMY/NhV4V82Dz9CgKnEe2RV2DQMo8uqsK1p 0LRkVdh0ZTGQVWFb3cFQ5Tl2TcMwujxerq3uoFnyHLumMYOBPF6ure6gqvIcu6azw+7gRMWhw2Uc KzGD+ocO1yJtAIapOHRYf+ahw3r9Q4cLSX86v+8PZFXYtEoVWRW21R0sXVaFTcMwpqwK2+oOxkBW hU2rVJHHy7XVHXRdnmPXNAxjyuPl2uoO6kCeY9e0ShV5vFxb3UHf+cCSTY8yFOSZpxvr9U83rkXa AN5Tcbqx/szTjY36pxsXkv4ottPvy6qwrX7fV2RV2DQMo8mqsK3uYJqyKmwaM+jLqrCt7mAo8hy7 xmEYebxcW91BM+U5do3DMPJ4uba6g6rIc+yazg47nyOiVxw6XMaxEoapf+hwLdJvh2GMikOHjWce OmzUP3S4kPSn8/t+X1aFjcMwsipsqztYmqwKG4dhZFXYVncw+rIqbByGkcfLtdUddE2eY9c4DCOP l2urO6h9eY5d4zCMPF6ure6g7XxgiVZxunEZx6qp0/7TztX1pg1D0ff9Cr8tlQiyIYQGKZWqAhUa FNSk6qZpYmnslKgpSeNQ2H797PAhQ4OSbunUbO5LjXNs32vfY1/dh1Nc3bgQtIR6T466sfab6sZa cXXjTOh7iZ12W2aFVeW9bsissPQyjMwKq0qHliazwtLLMDIrrCodmsb71rF7j2eXW4aR8nJVpUND kzp2pZdhpLxcVelgSBm7si+YV8uINHI0h4/NmFuFKa45XAj651WYVo7mcOtImpnnaau4FHAm9L+j fVuXSWHpVRiZFFaVDjqSSWHpVRiZFFaVDpous8LSqzBSXe4v0YFvDomnURy6hNIO8Py5T2cEpx/4 TmBmgYBXrMHlCbiY+QEGPmUTL+dAof793AlM1C5wtOifUbnLrZ28WhMObv3cQXD87AYhJXsxYA9G PdC76gLUAQ1I98++S56nNAkjHgKHkcO/8f7eHCsnNUATJ05MVAOREz+YSMCOwiSMu5OBqUNYAyNn lXZYESHYhHWDd/b7VkIiy/9JTE1viGPH9vi6Aya3IxOuYKPGW9Pujf2F/0QArrQWa6Emb52mfTXe NFjTJeI8F8NP037/FphAB6p6xkBQjMSh8xiptv9I4rUjLGaVBeUnMOAbdJ3h+8utTHumkR8RoMTp /4wQFs8mJ8aYJcmCMpO/sz0Gocf4FBA+gcs49fEY3g0xyR4Blg4FDsbMORZXdwvPy1yVBMRNph5O 4alPON2y3rifzwOjKAsKANcXzdorM8Oh3YjNhcPC/2lBKLuUlo6fcLO8MAabzuPg+zDZgsDpIaOY IS4JRBKFL/t2HGpsOFS6Xc0XdvFzeYOFEDxciax88emxZoskvahdJwg4TTB5Vs88bKqMeoF/x9jR gRB1IGqK3LgVDNoEvMqp8KNer4uzL/3EnXFgwBjJDtzb/37du/wKV627b4wVcGVoQHmkD4zs+6/W BmWsURraouCpiBqejyaqZZ/bN1aH3wfrP5RpzXBjzcHTSFMA//hZGV+ZsGZPzs09U9ZTpOPZIvzZ vKeCB0g76hx6A+fgsSsvjCKBT08Ln4UFP3jm+4dfhi22K6RKAQA= --=-Jqb2DeyKptpZmhWla+bp Content-Disposition: inline; filename=win32_scan.txt.gz Content-Type: application/x-gzip; name=win32_scan.txt.gz Content-Transfer-Encoding: base64 H4sICPMDwkAAA3dpbjMyX3NjYW4udHh0AOxde3PbOJL/fz8FpqbqIs9JMp961Th1jp1kfOuHKnIm SaVSXkqEbG4oUktSdnSf/roBkCL4EKn4EU+GLieWiO4fGo1GoxskwM+h5VH7C1lYjjciYWQFkeNd E5tOV9dk4duUtFx6S12imebePz5L1FGwRtrIJ9c0Iks/iMjcD0hIg1tnRsm/kPgFaUGhZduB4839 LMJn5QsJ/dlXYG/tkVWIcCfj21452dxyXGqPyCEg0jCE7wvHXRPPj0i4WqIM1CbTNVkGfuTPfDeL pBZWaBSR0Qgp/SWSFpRPHc9GEGg+a3rP7OXkBjLXCSPq5SHuLIdpGjU2870o8F3869FZ5PheQsz+ kNbhmw5UR5f/jdrZI/PAX7CiztSCxnh2SNSu0lUNElDLXifcsxs6+3p144fRiFizGSoMdBPQhR9R wi9/TP0U8qWoiRMyTZ+cX51eXIxfHR79E74H8L2XXCjEcP2Z5TIIz1rQdKU1yFvhHmmxFh+fT/Yk iZ8dd1pZtk9D70VEbqxbCp21oASHAbFCXkchv7+kHloFWMLcAeMAYx+RfRrN9rE87NL/rJzbQs6Z hXUh/3Zm0jr3YajMblg5gd6znQCMzg/We/VFYnRdvFQszIYWBoAHDP/69UVtyhR6faYd4C9vKBty 1ItC4s9JdENTVRJOjbZOLMLGL0Eq3qkErSJsE/AaO9RocW9FQ9T3yRj0P/XAvZDW0cnxOxxSFg56 8CU3VkSsgJIlDRZOhL4M3MsqpNxkdqhxcnj+Grw4OuKwy3xqSojFCloypYR6M9cPoRLHI9MAPUmE TbPAsZHwxl+59i5tdO+sNegMcMMlnTlzhwODdh10cYslq91Gj7foPlrHxiMX3Gw0u0HDFU5rZoW0 E1IvBL97Sx9FgBAGYWfmOmBY3dBfUNtHX9+dO8GiPog61Lpqb4DuvDZT2okXMwnvfx1YHloVc2lg iMImpFkg5docz8nxbi1Ec5Wg/qcEGeZn5LsKwClRFDA9H4qL5cTX0J/iC1E5mXPFYpYvZEKjVAjD gxcYvksXjJ5+RQEhlOn+47O48IWMRYmYSsmfStfod1S1TZYQDSFv0UybAnj5a4zRYcPulQDiHbUK 2OBm/fW7zPUG2oqD+86Jbsjp2XCgq/vavg6S4Dh5P3lF0KI8GoQyo/Qtg0ktcO184BOPUpAXXIpL LdBUdOczgwlHGZ4O+bwKp1/ILUjtB52TY+YCQOv2ahbB1xy5wOd/cLRlKJwu7bKejHXbUr4p/Vf6 Hnl/qWr7am9fM9g1Re3vZXi5KJyecJIMhah9H/7uA7HQUYbIz14QXK4zBZ7RdDod2badobm7oeB8 oQydBk4LQOutFlMaMI0AA7saq5eVZCAW1ldwgCuAYc587a9YHwcQBoTxYAEb3Eeb3gd4bME+1Lif kyYDDEPVQUOyXIh3ARZnfOFp1wS9DczUWB5m22QFi9WyTdyL+fzCe+3Z8NFaLOHb1urQNq1VBBlA xENSbEVRV31H5+S6ioTOYumuq+HznM6cKeMO3A9M12LmmcViTFesC3gM5vnEsalFrKkPl6Eji0X3 MOsBZORjUy+zmLaQEfOCeKBsHya1DRnVvLWZ5xeXr0eZ3gADDa05bWM86UQoKLdYTLPwArjIDAr/ YZ4fCZl7WU3DNRAsIERgenwRUDZZ8sworyL+I0nSZoo6ez+55Fq2oghcEE4FaP+8icUoYnSAIB3M oNrJiBEhcxxFdLvduv4vZzIe/RYLwXUkyZ4ihErSxOUeNmuCfNAxb4dqhSjn1vFXIdMvBALBeit7 CL4fHDaOSJhp5sSaR+Arvn37BnY2g2BMgfA8tKau6N05tSLwLRIIlyAe1ERXlHTxMZ35NnamIHtZ NPgLXQYGoY7PYjiQxYepD8VZUMvDgEoQFUki2FVzqxwF/Bkx4spg9gJzQLk7IUTKoNuVF/krNLI2 s9aYUCjTz7o2AvXhHH7Fwt1C5cXOkajblRfTbZG7xEDA6Ud31PrKR+nCuqZ8uQVsP2SOPcPX+nD4 7vzk/O0IGQL6gindgSArgCmAQLgFACzC++WXX/a2ShCbJqTqC2BFl4xJhrWFSbQXRIMGfyTbLUpQ lQN8qgXwaZstsDZAo0OIySBtcWhYVF20tGrIK6jKAarkFVRV8nr02sJco1BUKKwhqqAqB6gSVVDV N1e+gsdDaDQaSDudqQhhwyhwluTh7ZV0VDGCcb6drhw3As5a5jm5sbC9nwCiysRi0pJ+r4uUIi3p lrpIKdL6/ROhUm9pEPEhHZtYrZmiUIkc7TwGqrCnDPVOcofgxvch3Yz8ABdgrCCUzcu2oho+aYbR xZHlHgN1hbdOk9aXFG3QcpndRrKAAcSNmD9VCwn8RynG7TqViau8SvjVWS6R/e7Gd7PjkxZOyMiS Fme71jLUteWBYMeBjp2DhrZL9WtR50M8a/te4eSMNbxB1O1qjMm2CQxDZGYFPIsDS1y5UbwAyMS+ u3HkLt8mzgdGXK3LhLZKkwFdutYsdrzXFgRet5a7ohhcrjD9XAVQmFXldmEDal8xJFLljWLKIpTr gFKP41SgbCiLcKbQGiFOBU5CudvMZdn/hguxCm06t7CLr63FwhK6rB67oIi3jCH+UbvbDS9mKNVc Gq4KbMNQpkBJuCq4hKFYOGu9E1rCsJPfpx5OS+RyfEhaHsCMeXG8PA3RubvORgRxSB934ZRCTuhg ugj5bnZ9eRNmRGwCzGDFwQWXo9oAOB2Ku10bCV19beCCATicGTQkpKm1pE5+Ea14rWDbukrJckIi d7y+gavjL3OLDlW9CD2BLtKCmONOQLV5BsPXL3lByBPr7ApjxVIOXzMgLRQKIplv/fl8Pp0rShsM xnH39qTWsEZIa6ujVHm6kWSUbyeuNpwcC3sfyc3G+90u8W+DLitTUkUip43ZVDNMFcaptyiEDDxf yLPLEVnTNKcUzGQLU3EBhULPT5VtJukuyTEmEyaXJ8eYzEhZxiS6C7s5Roigr76RRANKpmhdXhTy IPdqPQKvnyqD4LUMEYtKELGoDBFi8zJELCpBxKIyRPDtRMyfyCaVMVcdl2bK0O8mjAWYaBW43lOM KUqLMGPGAszElY/QkSs5VFGeK2W4MXMBr7UuL+0U/aTKYdzDiL3Cm8h8dKfH8mF6La7bTd+UOcJM Mb4fhGuoU73D1lCVOkRqHaJ+HSLzwZD0ByOq1bpaejIeTAW1kHoPpsw6REotovmDET2cnrQtRIai AJGqKNs6OCHaZir1iMwBEGnblZkQDeoQDWsQbR0ICdE2jSdE24xOn6MKFHNr3wmi3lYiY4rVwbBL m8obnraJsCwiL8XNR1D5CJqYDj3+ZHeUyMnxAYK9GrTJmN9XEpdU5Y3sVR3/6pi5Tnbf+NvWwpFI INk3bT+tW04Gkwe/pUX+K76fBfWOCJelk6v/OL7/G84Ch0fDqIeXEv3vvNauLNoVPjYA/C1da3O9 tTtqQYD34fANq5/9GFYGhK/0n8Jc+LF1cX6gtCEKP5BgJvxeAJIAThsmyOvws/LNHH4hBww3Rfvu 9VsoUjReNEiPB8wCzi8uiS30lO8ynnKyRx8gnHy9DOVEnGObU46tGqS1CL9Cjw6UtLSnh2fjzuTy 8PL9ZNPqjIyT15eXJ+dvEfFkcvn63aQlKy4uv/zjNTk7mRyRk/2LdHAXXxP3mBggVmaoGHIbRpvJ l7bx1PIMPr3AkhR2/xOamo7l9wPfj/a7eItlnymgM6bBnE/rV6pmKlfjGz/yuzPL/T3TkRMaTSCV GVsBYINYYSvdpN/IH8fjkxEZdGVl/EY+wvUD1YSORYqDPMGnhODM8eDzJ/wiUWDMPXa+UXeCScxB b9gmpxAYQ5gOn7dR9pUNZV8hrcPj/00L/fIlgZIOp00LKGG+WbkumUR0ye4MTSAqRw/BmISBZhiQ duL8H22NAwp9sAdUmq7ypyhoX9YaqhRXhmYrl3VfKAdXvzHxT6l3Hd0cqEq/3+MNegeJxpHv+sGB mqs6hKqhyl7fZNbSQ6ek4ac+fLJ0WV/jY3Jgmr0BSqeaM2WvoFhTeDE46r02WyQkWMcBqwG/hlpA bw90WQuuS71YZFcWuU3+E808pvKbOfuQsbW3NDo7Ov3nsXPr2DTIGNqJF9FrYeyXDtj5IRvX2Bek tbGxNkM4MPBzRufipslbjLXHH86OV9H6aD1z6al/JxEerYKAehFBJCKEgWoYZLbTzy4uL951BHQ4 IoDLFN/GT1fH7y8/sclBtqw3samgifRAHeCAjIHweyr/GrtBQ2Id36xfrSMaQqQPrNkiNBFR1NPU Yd8c9CSSSz+yXM5/QEzN0Iem2s+gnB5oQ+jfmU/nc9bdmgo9GYKt0qzVja1VSE+dhYOdwLhQcMoF H4p2zONmVfsVtr6cmY0wN7mmkGYvZccz4csr7GmKYJFbZBCuf0SYt0v7WLaCAAUbB0jQAe4zB5gO DVzrOmSJaJGzt4NbdqtakkmIG0b+EsUrKsPr4Htae2JlBsfC0gq+ZocC0uYr4KswI7EMckBeFjYi 7cHZTXXQ31W8lNfiazc2hIJtou49wuN+WjnZ5ukq8JD+KsA9CELUF5unF2Xh2QPTHSIHZiki7mz5 wGY5MF9hxF0R3oGhDHuyEzi6QbtxPytf2mLVWc3NTDGNWoNGq0Gjl9IUJueZTL1MmRvtBDRaBR5u upismIYfoVeNR8A0G8wGs8FsMBvM78Ls/UXkbDAbzAazwWzizwazwdwJM8kUcYmb7/mYwRV/IRJK kfqG3SYjbpxLg9lgNpgNZoPZJMwNZoPZYDaYjf9sMBvMxuYbzAazsfkGs8FsMBvMxn82mA1mY/MN ZoPZYP7UmP2EjD1wf4XnMozErXR2LLyuqRqDxdONsk+fM56S3dLyI+nSvum/82ZBXdtps+BDbtIT VGLrjKHGVMrg/lv55Ga9n2BpsmEvfgzjPpv5tmx2QZtlr3o4IHoxR+AvT7y5n91ygjuqTvAkw1zh eHyKW5q0NN7p+BD3BQ3SUr1idKombbibBs71TeTBmMONm+zlCHh8ccEelpDv8nnt3eZEm1i3tFg2 +w433ySb7DKds7VZv+HTL7cOvWMbfbBffklvGhKPxSysJb6xwooI215tDvT+rIRMTZHNysm0DVlP kcmSXUHgSXLbguL9k6pWsoFSifcnFlBU7aB82kHD9/OiQk7ZWaleps/uvSPYyG4hyyCqDFEpRVQ3 iEIlw7Slf2AHyHRwa2HA5wppM5KszOEjKDPdPJQ4EcVfLiVR7Lt5PD4MwQvX2L6+MQ1wE6AYsiS9 T/rk7DWBOt9dFs5xbO9dvekX50npTSgJHL7bhAZXgjtWImkB11dq75VSjpLX2kQ+qPDwmNfR6huq MuyRKbYszT1dzVnrdWWgWfKhBmK0gRfAc0iLtuFdHfupfdNSKcQNPhEHzSSnaKbNiRddgPtzPBht afM/A94AB2QPh+yZ9e3Mv6WTJaX2gdId4LXNtk/cW9vmm3YPNAkEd5OWbiLF/jbhk4qnVRsDQYJ7 RZmFpXsbt65evXnzATcEk07nJVqZFNxkGokdgsf1pki+vh5PLs7FxLzAV3HIW9mxis/6Pj7ux6Mp dpYyGYxIT2yUbYMR5lz3O+j5Q8+e4DTHTlWSeqBDsJw95pg5d5Kfi4273FPkhOyws12qJrt1HiKm IMRNpHw8qqXEKAv6EqWd/OvpA73gb42Ws1FHoHuk+uD7q0/jw8mklsLVEdE2Cpf0jU3BV+IQcBCK wf5X8Cu/QhSLqHN2VcPivk30PlF6REJQAUHtMSqTKDOi9gUOcKe+qPEH9ishaICgWQgMJUby/4wY KINNFF1w6XMynxch6ICQLkx/luotlcEAhEw5jiKNWDphzR+wS7GOhiq2SEIwUQ+UacCAGIkRzhmr yloBvt4wyNAol6HHZQAdqwPEQd4e0QbEGBCph+wyhH6mFXrqcx09nMSn8Il4dVRmK/Fvylbge/+J bQV+05/Zn4eyFTX+rW0rAiFnKwUIG1vZkHyXrRT+1rP4rK3sivB7p5P3Qt89yf2IOa5AWLgQSzvM SGv07iWkmggpvZqgSkZpZmERWNWT8Ok5Ad9KNSNv8XV1uRhUZ5Gqmr8+K7luZ68L+Iv5HNxFQQX8 wIr89WHJdSt7vbqFcZ5YHCqc+/koQZxinc76ZhkdZ5cw6p1w8ygZWu7kGjV9yI2q6Jq6lTp90A1S a9vPulEV1dTS0krg1QfeWJbEMMkfeAOjiB14o85oc+DNox94wy1OnHij7XDizR/O9Y1EWXLkjfYo R96wiSF95I0mH3kzkFjlI29MQ8mWbk69UfumIZVKB94YhmmqvQw7Hnejf9dxN7p83I1y/+Nu+ArE CP7yZFs14/e6lCfmmyNVmPvj73jFTGnzljo94bZ9sfydXdbm6wA0unL8K1xoxJNlvaup67Mj9CQ9 ZEmz0xYrxxNnQupCGnY1z53oIhXK6w6JgKKdqIV346NkMR+TNftRtmulD0piS4tjoCYOmDcbyxM0 iEG2T0HUV/TayS8xnFnLY//Oc33Lzgzq1NIpjmOMCKTyZDGVxOX5XXS2gBaLj0TJ+tIsgVpFoMkE uSYUzptxsVgVYRO05IAKE9l3oLAQV8SPV4slmdI5vmsiEEk/S67LkpI4DxBJCU/cnjyBtSxM2UwN P7MEVo+TEvWxkxKDp0RxeUECC8LxsqGyYwKr1ExKQIaejiDUIFOmdesJE9iJtVi69BM7nIudc9gy FfILOH4Mse4mqwUuykk2eASmxT0CLvK8ENc7S2fWDay7F+lIiXw8GBjg/D8dmAOjTWy6hFhkIJku t1J2Kjx6W8+/SweaMBcdL51ucr41zkjS0BUE6zSBFA++D2kgQcBkWVS+Lik/Zy88vJgzz7Sao49R e6a0sIyT5ZgGKQpdV9Kpj32XmnFJ0azLKFgYGsYUoDiJIDXxcoL85AsoKQhOJN2OEkvaJEWQuQ9l 3/0Jsb29wckLwiBEY4W+BrIUTCPH4rUj2WP1RPGlz8JhVqzni7Fbkv6Qbp8JAU7js97zbYhXBnP5 zSR+bYvO3wlaMPkgH5usWtiq7CR0EiLm4a3luLgB/MQ7fnd4JlXBDrV3QmLFNFvr4LMA3kTB17LI J7Qnwqo1hEVzyt0NrF1VvcbXxxNdj8Jr36np3YQv7O3SirKRURSsxY0SnDTJQB0M+A0S8c55fi5i NuZitB3Owu4MMZY8eoYgg1kuy13AXrWj9XXBCNf4e5bzXHeBX0r7ZGp9Lv3XG0KU3/TfQ6vV7Bla o9a/7rAw9BJdN/13H7Xqye30Rq1/xWGhDjS96b+Hny0gi9xNqwlHiVLLEKt0appGXZXWIr1/tNhX t5tPUr5jS/tabeMpJP3bjf2+0Xu6SPHn025T0RNV9PjTRlVKpQ4rYv97qCA3xvSB0t86xjYEO3pI faCqdRVVjzajKA24Go/SVPTcK/rhHkVVlYqw6SE9yqa2sjFWS5z7q1VVtdpqrUW7czT6oI562Nuu 1g1B47p+8ooqp95hv7bp16PNrm9pasVCTBOjcEUpuyY9CUdJWysRn5ep/nwVVdmUoQzrmlQt0h87 6xiKtn3oJQS7Dj1D6dUeerVos0OvP2juoTznYVe12G8qT3cP5efTblPRM5kPHj290zT9CYOxTW0l Y6xUnCpFaZqh1FVUPdr73z7QBsb2OyUbgsajNBU9jUcBm6t9m60ebfaGop4wNend1pU1U3+6G9rP 1FqbimrFtE8VDPR2fRYg4Sib4aoQn1fnVTrPXn3fWYf0x6bnplHhOhOCXV2nadZ3nbVos+l5Ty+W rEnP75U1672KqbtR6zOdIbi3VYZPd1P7J+q/are8o1YTjhKlliFW6XSg1b41U4v0/jmuEXvvsjsO ZrFFVi6Em2bdlhaS/u3Gfr//hNnE32fs94ydY+ImSWsqenaZy6PnjqY6qAjJm2UfPvr1/tPtQ3mm 1tpU9Pwr+uEeRVV2DmhijrJhUoJY2dTEl1S3tA7pj1326SvGdteZEOzqOvvJs5nVrrMWbXbZ5//b u7reOm4j+lfuWx3AKZYf+8EA6ktsF0bjJohdBH1yVes6EepYqqQ0QX99V05KOpfmnUPpXs7sap7q Kmf3cC9nhxzunBk/6WZMicQTsbtOZwu7n+N4FEttxqDhyJk/MYbibMVmFMLyLj3GEWnoEaCGsjgi 0piNxxPLIexuCNr52sjq7nHk+ubvoRPxnwxYB6TnH8oZJ7bizhgZznLmb34eOLkew/IuppPf/+kl AaqPwDz88QXDZhVuvGY+KZF4Iv44rhuB/KmDeZTIVvIopeGQHqUb4cQpDHuA7OyuI3LRI0A9ihK1 8Si2M7iMAcJmBULGpnsUDa+EE7FHPdYNDc8qE1vJ60PDkTN/YgzFuhE2FAzLXDJjpEpmIJ5Uzvwp 0fF8ZJgqSmYg2KxkBrIV1VX7wRCxr9ou1NYmiVcU/emn70i/fPCpHgRlLplhqJIZ5q4lM0xFyQwE m5XMGLVkhmQPQ73RPmjJDCUST8R+KGutbVoyw1IlMwrDIQM26ypKZiDYQ5TMIIqLJ4B6lMURkRY5 4SXgMWxWm8LVClw1GFIicWtcg9okVLONQ65xia20j4SGs5z5m58HVxRAWOZKEv3++UuAZczf+ohI j9L3sEVi2LxkB1GbQI8wlWiVi+lka1VL8YpS/YjCHalHnSy8v4agrKuODRPxKTcgkmQ5hro+IjLg CwH/ZgxhM1V6WIQqXej8KdFyVx3jpobHlImtFMJBw7l/ZOUCfKiJYXkjqyEQKbkRUPs9cAh4Si6E zcTaoV0xOaFOQInkE7F/T3LWtoyMI1tRrI0MR878iTGU+YfDZVMQllmsbYk6IRGghrJyItL0jcUr v0DYTNqNFJLWOO7BEPGHV9YDW9GDhVeRrbgzRoaznPkztq/YdSFYZrG2pTyKvWu9Qldh6Ag2E2v3 hK/TOE6J+In447huatn4JrIVxdqF4ZAepZvwzRyEvX9eoAlhf158AqhHUaJGHiUEWFKBYTOxNmLU /FEP+2bczlfpHkWJpBOx71GM6RpGPYmt9I5Bw7n/z2oMrM/FsMzS9IGSpg8qTX8YROTSG8YKaTqC zaTpRqXpCzAUORZ57M2g72ql6fGKglGV7kg9qu9gaToEZZamd5Q0vburNL2rkKYj2EyaPrWTpgt9 LZVIPhF7eOD6ruFHrcRWlA0VhkOrWQz8Q2HYAxxh9kTlsQRQj6JEjTxKjxdtw7C7R5iD0QT8BRjK +ojY4xA7tSzaltiKlTO0nPHdREpTRU1eCMss1nbUrstpZCPaIl3vK7a3CDYTa/uGnUh01VYiMav2 VF0hKF5REmsX7kg96uTgNBwIyizWHveXCEmA2jJmYYQrV2DY3dzz1FhPTw+VSCwR/+lhQLo38u8a 2NcYU8j13udQiLND6o6yTHV9ROTLh2fpQ1BmVfpEqdILjbrJV2+YKlTpCHY3sukLzc11MVciQUT8 i7ltWq8tshVV6YXhkB4ldTEFVNkI9gCfAmPTzJJHmZDzFznWqkTyiUiPMnk4WwnD7n4KdMi5Mn94 IHT+lOgjIvYQzva2urZ9vKR0BEbeczXzJ5SIPGvsHZxNjWGZVemG8pFI9oac+VsfEe3obIWjQ7CZ /L9le05dtZVIzKfAvicSZjLzjVcUrLd0R+pR+wHOQIGgvKuO7alYv9cKdLJfPdtXHKog2N1VJ7iG /Ud01VkzEfs6Yoytlh/FS4rKaeqesuaPPH0yFq+lAWGZJdo9UZ0nApYxf0sgIl/00OOFjSBspoV2 tZ0+dOlRInHO+PgSbVPbajheUZJoF+5IPaq38GdUCMq76riJKAziCsMhLcIFvIwEhM0k2qE22Na8 DCUS5zobSLRbduZ0VGdObDhy5k+JajbMFW1KMez9c2d8F/afHiaAWuTKicjNXRfgY0oMm5UaCnpM uQBDWR8Rewhnq0sqxSuKAvW7lY+yE3xyCEGZ1dl2f2poAlTXxLFwfh+GzUTDfW1UryGcEolznccP 4Zp25nRUZ87icIBDITgtAcMeILWeaphpSg0zhVqrEsknIj1KRa9VDLubWk/2WtU45EER8YcHw9Qw Mk5spdgCGo6c+RNjKPMPh1fXgLDMyuWBKGIcAWooKycifeQw4GWpIWymRUdyuHTVfjBE7Kv2WF3p KF5RMKrSHalHHQ18cg9BeVedLhAheEdlP8gyVCU63jtuOvxQBcJmrbTbSgx11RFOxL7qGDs2lBgm tuI3B2Q4y5k/Yye89hSE5V1Mx0DUL46A6rpvHV5WF8JmWtqptjWRfiFTIoEe5dhfyFITxhYeJbKV PAo0HDnzJ8ZQ5h8OP0KBsMzKZUdkw1pEtipn/tZHRFqkdXhKK4TNlMuIeF3DKyVaXxxnPJBacbA4 LrIVJdLIcO6/GTIe/7gPYZmVy444q4wA9SiLIyJ9RPD46SOEzSTSvjalS9c4JRKzxnlHmFouWHL7 rbd0R1Lc4uEnhaDMyuWRqCgfAdVJqiNeUR7C7lrEZLSivBKJJ+I/1Ot9y8g4shWFNIXh0EIajxc/ g7CHaC7tiIryEaAeRYkaeZTUSJT2KBA2ay7ttaL8AgxlCUTskYWdqO5pedp7vKQoqUU6sq1i/oQS kfn1k8crykNYZvky5SN79ZGyLdL1FY4OwmY68ZbpXrpqK5GY08NpqC1yF68oWG/pjtSjTiN8zg9B mZtLE7F+AlQ3l8ZjfQybNZf2RMbIEk8P+c+aQuG4eNE/qxKtjYj9RZltuuFmLLEVddqF4ZCOeuzg pRvD3v9Q1rpxv0dJAPUoStTowMFNsEfBsLs7mqkDvjTwh3fswYAJVNEW3aMoET8R+x5ltNWqdEuo 0gt3pB51tLgqHYEyq9KpwnDdXQvDdRWF4SBspmEO1V/I1XUq0YNznW4qVIsVthkTOn9KJOkLeX2e 5f4ebNT9DvOKwy3HECS38p6QP46Fcvik6YwBV+VB2Cxtm2oKoRsGJeIn4t8wGNPSo0S2svL+jg3L Un9UQHmOYA+QpBt7SpY8Smo6qR5Fidp4lDDALwqG3U3StbZltXsNQaQTsccR1puGQXFiK30FhIYj Z/7EGIpNTV/pT1kQllt5T2ggQ6G9NPlGBYdrICFspuqmuplreKVE/ETs4ZUNU0MNZGIr5kUiw5Ez f2IMZf7hKvJCESyz/H7Yf1SaAGooKyciNxNugI+0MWxWUME2LCOlAaN4IvaA0XRdQ51xYivtjKHh LGf+TGfwXReEZV1MfTcQFX8ioLbkTzfiNX8g7K7rNaa2vJHGcUokz6McPY6bfMOGi4mtqPMvDIeM YyYPb+Yw7AFkE9YRjcIjQD2KEjUK+K3Du8xD2N2U1tBrM7gFGIoYizz+ZzLTsl5bYit5fWg4y5m/ +XnwI0QIy6zBJyrQJcAy5m99RPShNl6vDcPmxQ60XtsCDGUJROzLo/HV9drSJcWM9GXVayPjcI9X N8OwzN3DiflLgGXMnxLVeJQBN2YMm/UD97XloXSNUyIxAeNIbfAz8x2JmKF0R+pRR3wjC0GZddoj 0Z4wAvQdXxwR+dZ2I95CEcLuBmVkc0tddZRI7qpjXNfwmDKxlUI4aDjLmb/5eeBjSgzLrGEe9285 EqBawzzCmw4MuxseeCrtR5MzlIifiD05wxmkQ+XBPIqhGmZCw5Ezf2IMxZmKZpQQlrl7OJHXmQBq KEIt0uKZqhg26x5e2H0cxyI1jlMiMXGcQSRGB4vjDKF4woZz/82QwdU0GJZZw2yIs8pQOG0i7S8Y /BwMwmYaZuoUVcMrJeInYg+vbAgNs3gSWzGvrDAc+mS9wzdzEPYAue/dSDRI6JDmWXKsVYnkE5F5 gd0Eb/0w7G6JKIOEGRr1KBFNxB7HWBtqs3jSJfHuzX6wXWkVNfjVGMqBfeS8Q4B9JIRl1jD7/buu BFBDkWmRvuvh7S2GzcTiiKBDV20lWt1ZpbO15e7iFcVvP3cTcDuLF+NBoLynh34iCsxHgL7jQl89 P+GV/CHs7qoztkz30lVnzUTs68gUarsUxysK9kje8SBv+RTgerIQlFm5bIgz11CoikQGhcHiB2cQ NhPUFipJ6TcrJRJExP7NypG9VnXX8KCI2Jd+Q0UyuecmgqPSHcmXD9+xQ1BmiTYVaA93jbSHilAb wmby36F2N6iLuRKJc53HX8zt1PJzcWQrHt0hw5Ezf2IMxdmAr7EQllmnTbR3SwA1lJUT0blneNc1 DJupurXr2hIMRY5FHl+n3bLrWmIr6rSX1XWN3HU5vBkahmXWaQ/7dfYJUK3THmBBO4bNdNq2OrTX OE6JxHmU4+u0+5aNfiJbUaddGA7pUUyPt1eEsIfoNW33q9ITQD2KEjXyKKmBKe1RIGzWaxqJsDXq WTARexxjvZcyqXkqQxxbKZVBzuBlEZGpHL7HUzkgLG94NQXirDIC1FBWTkR61NDhZ5UQNlPeT3pW uQBDkWORx17jPVWFJxdMEWUFS3ckVTx4UUEIytxmmujslgD66q2ciHzHHd5wDcNmbaa14doSDEWO RR6/zXTLhmuJrXRCCA1nOfM3Pw9eyRjCMku0ieYJCVDdZhpvn4BhM+UwJR7XL2RKxE/E/oXMTmPD yDixlU4PoeHImT8xhmKnCa8OAmGZddqEM04ANZRmHz487owwbHYoQmVMadSjRPxE7HFc6Gqrg8Qr Cq9J6Y7Uo4YOlixBUGaddrdfAJcA6kxkvnrzDMFaQwybCeInrQ6yAENZHxH7qmP82DCbMrGVzmOg 4dw/BPcjnHuJYZnlyx3RTCgCquXLBm+mA2Ez+fJYnaSqh3pKJM1RHz/tPXVJbPLNvSMaHkLDkTN/ Ygxl/uHwho8Qllm+7Al9RASooayciDT9zuOKFwibyZe91mtagKHIscjjy5cdcLh0sPAqshXly8hw ljN/8/PgVaggLLN82ROVjCOgWr7s4R8Kw2byZSrtR+M4JeIn4o/jUjvGJvLlgVDslIZDehQz4voO CHsI+XK3/2kTQD2KEjXyKKl3KSBfRrCZfLllutfdox72zbj1Q20qiu5RlEieRzn2HsWY0FDkkthK 7xg0nPv/rCbA2iEMyyzWnoiaxhGgrmvlRPTSO+FVqiHs7vFAal4oeo8idP7WR8S+GfRTrZgoXlFS ThXuSAqnAt5xEYEyi7UNceAQAbXhgbP4gQOEzSxiqG3Bq+GBEolzncc/wuxDw49aia3kUUrDIT1K H/CPIhD2AEeYVDNLo80slai1R6loz4lhd48wtT3nIgxlfUTscYiFem8eyvQt1QkUG46c+RNjKLai uymGZRZr90QCcASooci0yHmG8ExjCJtJuy0Q3OqqrUSrW7VD4RCrbL6BOBcr3ZF61ICfikFQXrH2 RJyxJkBtU+0JP2XFsJmGOGhygRKJJ2I/PfSdXUQFTfY1xprajOp4Rcl7UneUZarrIyJXKQPXmoSg vCFkHwhVegRUq9K7ClU6gs1U6fUH97qYK5E0f9JAld6yPaej2nMWh0MnF+B9MDHsAT4FUs0sTamZ pVBrVSL5RKRHqeiDimF3PwWSfVBlhAdC528JRPyR1WCkNAzJY7g4tlIQJ2fwD5SIjOIGAwsJMCyz Kp2oKpAAapEyLXKeoQr5/x3qJPjUvFBXbcGGsj4i9s3EQNW3ysx3IEpmle5IPeqAl1eCoLyrjhmI dzwC9B0X+uqZEX/1IOzuN9fOACagq44SLSAoNbZQo3ffNwei7i99T1nzR59n4+WIMSyzRJsoh50A y5g/JaryKHgRcgybia5NbUsRXeOUSExk1VONWTLz7YleL6U7Uo/a4w1IICizRJvoG5QA+o4vjoj+ 0o13d8KwmYx+qj0Q0VVHicSsOqZD8rQO5YwTWymEg4aznPkzXUVKEoRl7qdNuK4EqO6njRs6hs36 aY+EU9UkRyXiJ2JPcrRka85DehRLtfXEhiNn/sQYiq1obIphmSXafn9+qCNr8suav/URkZtZ7+Fs SgybSbQLDSOOdJ6tcZwSCYnjgiPSJDPzjVeUJNqFO1KPGhycDghBmSXa434NRgJUS7RHWIOBYXfP k1M7PQ14lEgsEXvA4zt3vI4Ssn5rYfugu62abB8X7qPBsLXlMuIVpYWHuuNhgkiLL1IIlFmiPe3f 8iRAdW3VCd70YNhdHzV0tfs7XcyV6OEt5s41rdIW2YrJBYXh0B+uHfxDYdhDSLT9/oU+AdSjKFEj jzL28MkKhs0UL24RaffsR1B2sNpRQonEE7HvUYzrm7ZJ74keC9BwFjR/rq9ok45gq7dOt7Dt1evL q4s32+vrLzZvz9+fX/+wPfvwH25vdTb/Nh/hH718/ufPNl/+cP7ubHN+PRP//H7z6Pr8+/en707M uH/BGC2lVy+UGCEXjNFWyKgRbCajpir6HHDBYH/rXf2GO8plIuTs6j9v3l1cb3/3Xr16/uLp5ulf n2zMF5tpuP79+/Rk+5/X1zcXl7ev1e7bePvfbv/+9P3Zo88eb65vTq9uTszjzeXp1b9OzEfYFxc3 F1dPvnl+MnTd482L018+/OHl5XZ7dtL9Mdz+8dmzlzfby5fn/92e+MF+fO3Xr77+9ovNN9+9OOl+ 6ezj23+9fvK3V3+//b9m0/3i+/lfxt3+a/rwt8e3/wzzP99sP77Pl1/95fWzZ99tTjbD5vPP/zSD uo/foa9Of7z8/NX5j9urXx9kftse/XR9OwPPb3+gbz/x7PlP+eEvry/PL7ebR1cf/vcT54Afzw1h ZfNIbn66nof8j/k33ly8nT3Bu+3tDd7M3uAPJfybi7Ptp6/Y/Hx6vTk9O5sfbrarf/709u0nWbfv tm9uXr89+wD/8ExnH36yp18/Az7gwZ/vaOCvzvvXpzr5xAPFK35zlbP5//un7fXs6H8+Pb+5Hdbb i6vNb38sg7+/uPk/aDPtvlHzQN5s3338El3kf4vvkJ3foen6COPq9Z4P8p5+IePUe+o99Z56T72n 3lPvqffUe+o9W95zWMg9l/J76j1Z7/k/0wG/GZgNAwA= --=-Jqb2DeyKptpZmhWla+bp-- From henning@meier-geinitz.de Sun Jun 6 11:07:16 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 12:07:16 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble Message-ID: <20040606100716.GH19373@meier-geinitz.de> Hi, Everyone who gets timeouts/USB errors with these two scanners and sane-backends 1.0.14 please use the following workaround: Comment out the "epson" line in dll.conf (/etc/sane.d/ or /usr/local/etc/sane.d/). The epson backend seems to try to talk to these scanners because they are Epson scanners. As they are supported by the plustek backend (not epson) the scanners don't like the epson commands and USB errors occur. See bug 300751 for details: https://alioth.debian.org/tracker/index.php?group_id=1308&atid=410366 I guess that bug didn't show up before the 1.0.14 release because the automatic detection for USB scanners in the epson backend wasn't turned on. Bye, Henning From serge@yotvata.com Sun Jun 6 14:12:29 2004 From: serge@yotvata.com (Serge) Date: Sun, 6 Jun 2004 13:12:29 +0000 Subject: [sane-devel] HP ScanJet 5370C - calibration Message-ID: <200406061312.29158.serge@yotvata.com> Hi everybody My HP scanjet 5370C scanner works. But i get vertical lines. I read somewhere here in the list that it seems to be a calibration problem. How do i calibrate the scanner? Thank you -- Serge. _______________________ Sent with KMail Powered by Gentoo Linux _______________________ From rene@rocklinux-consulting.de Sun Jun 6 12:14:24 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 13:14:24 +0200 (CEST) Subject: [sane-devel] HP ScanJet 5370C - calibration In-Reply-To: <200406061312.29158.serge@yotvata.com> References: <200406061312.29158.serge@yotvata.com> Message-ID: <20040606.131424.511742157.rene@rocklinux-consulting.de> Hi, On: Sun, 6 Jun 2004 13:12:29 +0000, Serge wrote: > Hi everybody > = > My HP scanjet 5370C scanner works. But i get vertical lines. I read s= omewhere = > here in the list that it seems to be a calibration problem. > How do i calibrate the scanner? = The scanner is automatically calibrated when needed (for some scanners for each scan - for other the first time after power-on it is used). You just seem to run an old SANE/Avision backend version. Getting the last release should be enough - alternatively the current beta release code is at the homepage at: http://www.rocklinux-consulting.de/oss/avision/ Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From serge@yotvata.com Sun Jun 6 15:33:42 2004 From: serge@yotvata.com (Rene Rebe) Date: Sun, 6 Jun 2004 14:33:42 +0000 Subject: [sane-devel] HP ScanJet 5370C - calibration Message-ID: <200406061433.42682.rene@rocklinux-consulting.de> Thank you, Rene, for your quick answer. I do have the last sane version [not cvs], compiled from source [gentoo]. Having vertical lines... Hi, On: Sun, 6 Jun 2004 13:12:29 +0000, Serge wrote: > Hi everybody > > My HP scanjet 5370C scanner works. But i get vertical lines. I read > somewhere here in the list that it seems to be a calibration problem. > How do i calibrate the scanner? The scanner is automatically calibrated when needed (for some scanners for each scan - for other the first time after power-on it is used). You just seem to run an old SANE/Avision backend version. Getting the last release should be enough - alternatively the current beta release code is at the homepage at: http://www.rocklinux-consulting.de/oss/avision/ Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer =2D- Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From gilles@ffii.org Sun Jun 6 14:20:40 2004 From: gilles@ffii.org (gilles@ffii.org) Date: Sun, 6 Jun 2004 15:20:40 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606100716.GH19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: <20040606132040.GA14021@ffii.org> > > Everyone who gets timeouts/USB errors with these two scanners and Is this what happens to the HP5370C too? (see my posting from June 1st "HP5370C still not working"). > sane-backends 1.0.14 please use the following workaround: > Comment out the "epson" line in dll.conf (/etc/sane.d/ or > /usr/local/etc/sane.d/). > What's the solution is my case? Thanks for your help. Gilles From khk@khk.net Sun Jun 6 14:25:29 2004 From: khk@khk.net (Karl Heinz Kremer) Date: Sun, 6 Jun 2004 09:25:29 -0400 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606100716.GH19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: I just left my comments in the bug report. The Epson backend does not have information about these scanners (this means no product ID), so they should not be recognized and therefore the backend should not try to send any data. The only way this would happen is, if somebody explicitly uses the "usb 0x4b8 0xXXX" entry in epson.conf to manually add this scanner to the list of known scanners. I don't have these scanners, so I cannot test this. I do however know that if I add an EPSON scanner that is not yet supported (this was e.g. the case with the Perfection 4850), the new scanner is not recognized, and skipped during the scanner detection. There may be something else doing on, but I don't know what yet. I need a debug log for this case to find out what's going on. Unfortunately the author of the bug report did not leave an email address, so I hope that either my comment in the bug database, or this mail reaches the author. Henning, do you know how to get in touch with Jan? Karl Heinz On Jun 6, 2004, at 6:07 AM, Henning Meier-Geinitz wrote: > Hi, > > Everyone who gets timeouts/USB errors with these two scanners and > sane-backends 1.0.14 please use the following workaround: > Comment out the "epson" line in dll.conf (/etc/sane.d/ or > /usr/local/etc/sane.d/). > > The epson backend seems to try to talk to these scanners because they > are Epson scanners. As they are supported by the plustek backend (not > epson) the scanners don't like the epson commands and USB errors occur. > > See bug 300751 for details: > https://alioth.debian.org/tracker/index.php?group_id=1308&atid=410366 > > I guess that bug didn't show up before the 1.0.14 release because the > automatic detection for USB scanners in the epson backend wasn't > turned on. > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request@lists.alioth.debian.org From henning@meier-geinitz.de Sun Jun 6 14:25:50 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 15:25:50 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606132040.GA14021@ffii.org> References: <20040606100716.GH19373@meier-geinitz.de> <20040606132040.GA14021@ffii.org> Message-ID: <20040606132550.GI19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 03:20:40PM +0200, gilles@ffii.org wrote: > > > > Everyone who gets timeouts/USB errors with these two scanners and > > Is this what happens to the HP5370C too? (see my posting from June 1st > "HP5370C still not working"). I don't think so. > > sane-backends 1.0.14 please use the following workaround: > > Comment out the "epson" line in dll.conf (/etc/sane.d/ or > > /usr/local/etc/sane.d/). > > > > What's the solution is my case? I don't know. Looks like a completely different problem. However, commenting out everything but "avision" in dll.conf may be worth a try. Bye, Henning From henning@meier-geinitz.de Sun Jun 6 14:58:01 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 15:58:01 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: <20040606135800.GJ19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 09:25:29AM -0400, Karl Heinz Kremer wrote: > The Epson backend does not have information about these scanners (this > means no product ID), You mean: no internal product id? The USB product id of these scanners are actually listed in your code. > so they should not be recognized and therefore > the backend should not try to send any data. The only way this would > happen is, if somebody explicitly uses the "usb 0x4b8 0xXXX" entry in > epson.conf to manually add this scanner to the list of known scanners. I'll try to understand what happens: "usb" is in epson.conf so sane_init() calls attach_one_usb(). By the way, the attach_string related code seems to be unused in that function. Now attach() is called. As isLibUSB is false and dev_name is empty, for every known device sanei_usb_find_devices() is called. As The 1260 and 1250 are known (see epson_usb.conf) attach_one_usb() and attach () is called again, this time with the full libusb name. There is another test if the scanner is in the list of ids and it actually is. After that, commands like reset() and get_identity_information() are sent to the scanner. These commands will crash scanners that don't speak the epson protocoll. I may have missed something in this analysis, however. So the ids of these scanners should just be removed from epson_usb.c. > I don't have these scanners, so I cannot test this. I do however know > that if I add an EPSON scanner that is not yet supported (this was e.g. > the case with the Perfection 4850), the new scanner is not recognized, > and skipped during the scanner detection. Maybe you added it to epson_usb.c but in epson.conf there was no "usb"? Or the scanner just didn't mind being sent some epson protocol commands? > There may be something else doing on, but I don't know what yet. > > I need a debug log for this case to find out what's going on. > Unfortunately > the author of the bug report did not leave an email address, so I hope > that either my comment in the bug database, or this mail reaches the > author. > > Henning, do you know how to get in touch with Jan? No. But as he has responded to my previous questions I guess he reads the bug tracker from time to time. By the way: there are some other bug/wish list reports for your backend that could use some comments (or fixes if possible): https://alioth.debian.org/tracker/index.php?group_id=1308&atid=410366 Thanks, Henning From tmwg-sane@inxservices.com Sun Jun 6 15:03:28 2004 From: tmwg-sane@inxservices.com (George Garvey) Date: Sun, 6 Jun 2004 07:03:28 -0700 Subject: [sane-devel] HP 7450C scan problem: color bar on one size of scan Message-ID: <20040606140328.GA11281@inxservices.com> I put a small sample at http://inxservices.com/scan_problem.png. The bars of colors on the left are an artifact. This was scanned with xsane on Fedora: xsane-0.92-11 and sane-backends-1.0.14-1. I replaced the avision files with the latest from Rene's SVN yesterday and rebuilt the RPMS. From tmwg-sane@inxservices.com Sun Jun 6 15:10:49 2004 From: tmwg-sane@inxservices.com (George Garvey) Date: Sun, 6 Jun 2004 07:10:49 -0700 Subject: [sane-devel] HP 7450C libusb problems Message-ID: <20040606141049.GB11281@inxservices.com> I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and 2.6.6-1.422 and this scanner. Jun 6 06:33:03 vanserver kernel: usb 1-1: bulk timeout on ep3in Jun 6 06:33:03 vanserver kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 Jun 6 06:33:33 vanserver kernel: usb 1-1: bulk timeout on ep2in Jun 6 06:33:33 vanserver kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 1 ret -110 Jun 6 06:34:03 vanserver kernel: usb 1-1: bulk timeout on ep3in Jun 6 06:34:03 vanserver kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 22 ret -110 Jun 5 16:46:21 vanserver kernel: usb 1-1: bulk timeout on ep3in Jun 5 16:46:21 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x83 len 2528 ret -110 Jun 5 16:46:49 ns named[870]: XX+/127.0.0.1/mwg.inxservices.lan/A/IN Jun 5 16:46:49 ns named[870]: XX+/192.168.1.3/3.1.168.192.in-addr.arpa/PTR/IN Jun 5 16:46:49 ns named[870]: XX+/192.168.1.3/12.1.168.192.in-addr.arpa/PTR/IN Jun 5 16:46:51 vanserver kernel: usb 1-1: bulk timeout on ep2in Jun 5 16:46:51 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x82 len 1 ret -110 Jun 5 16:46:55 vanserver kernel: usb 1-1: bulk timeout on ep1out Jun 5 16:46:55 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x1 len 10 ret -110 Jun 5 16:46:55 vanserver kernel: usb 1-1: usbfs: interface 0 claimed while 'saned' sets config #1 Jun 5 16:46:55 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x1 len 6 ret -108 Jun 5 16:46:55 vanserver kernel: usb 1-1: usbfs: interface 0 claimed while 'saned' sets config #1 Jun 5 16:46:55 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x82 len 1 ret -108 Jun 5 16:47:10 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x1 len 6 ret -71 Jun 5 16:47:10 vanserver kernel: usb 1-1: USB disconnect, address 3 Jun 5 16:47:23 vanserver kernel: usb 1-1: new full speed USB device using address 4 Jun 5 23:34:54 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 10 ret -71 Jun 5 23:34:54 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -84 Jun 5 23:34:54 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -71 Jun 5 23:34:57 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 10 ret -71 Jun 5 23:34:57 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -84 Jun 5 23:34:57 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -71 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x83 len 4096 ret -84 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x82 len 1 ret -84 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x1 len 6 ret -71 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x1 len 10 ret -71 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x82 len 1 ret -84 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x1 len 6 ret -71 Jun 5 23:06:59 vanserver kernel: usb 1-1: USB disconnect, address 14 Jun 5 23:07:10 vanserver kernel: usb 1-1: new full speed USB device using address 15 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x83 len 4096 ret -84 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x82 len 1 ret -84 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x1 len 6 ret -71 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x1 len 10 ret -71 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x82 len 1 ret -84 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x1 len 6 ret -71 These are with Fedora sane-backends-1.0.14-1. I replaced the avision files with the latest from Rene's SVN yesterday and rebuilt the RPMS. These messages are from after using this newly built RPM. The problem was happening before, with the standard RPM from Fedora. This is what prompted trying the beta version. From tmwg-sane@inxservices.com Sun Jun 6 15:13:09 2004 From: tmwg-sane@inxservices.com (George Garvey) Date: Sun, 6 Jun 2004 07:13:09 -0700 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606132550.GI19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> <20040606132040.GA14021@ffii.org> <20040606132550.GI19373@meier-geinitz.de> Message-ID: <20040606141309.GC11281@inxservices.com> On Sun, Jun 06, 2004 at 03:25:50PM +0200, Henning Meier-Geinitz wrote: > On Sun, Jun 06, 2004 at 03:20:40PM +0200, gilles@ffii.org wrote: > > Is this what happens to the HP5370C too? (see my posting from June 1st > > "HP5370C still not working"). > > However, commenting out everything but "avision" in dll.conf may be > worth a try. I just posted kernel messages about this. In my case, dll.conf only has net and avision. From henning@meier-geinitz.de Sun Jun 6 15:21:54 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 16:21:54 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606141049.GB11281@inxservices.com> References: <20040606141049.GB11281@inxservices.com> Message-ID: <20040606142154.GK19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 07:10:49AM -0700, George Garvey wrote: > I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and > 2.6.6-1.422 and this scanner. > > Jun 6 06:33:03 vanserver kernel: usb 1-1: bulk timeout on ep3in > Jun 6 06:33:03 vanserver kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 110 is "connection timed out". I still think this type of problem is kernel-related as it only seems to happen with 2.6.5 and 2.6.6. Please try 2.6.7-rc2. It works for me (with different scanners) but I haven't tested 2.6.5 nor 2.6.6. Bye, Henning From khk@khk.net Sun Jun 6 15:41:26 2004 From: khk@khk.net (Karl Heinz Kremer) Date: Sun, 6 Jun 2004 10:41:26 -0400 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606135800.GJ19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> <20040606135800.GJ19373@meier-geinitz.de> Message-ID: <20040606144126.GA6798@khk.net> --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 06, 2004 at 03:58:01PM +0200, Henning Meier-Geinitz wrote: > Hi, >=20 > On Sun, Jun 06, 2004 at 09:25:29AM -0400, Karl Heinz Kremer wrote: > > The Epson backend does not have information about these scanners (this > > means no product ID), >=20 > You mean: no internal product id? > The USB product id of these scanners are actually listed in your code. Guilty. This was a copy&paste error. I never intended to get these into the= production code. I'll take them out right away.=20 Thanks for doing my work :-) Karl Heinz --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAwy0Wxejv3RfKrhsRAh8UAJ4zHBy5YrBGHE7n11MXleML3POXbACdGjaw IKqKPiDdwjh6EtOjKeFYack= =kV2O -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From rene@rocklinux-consulting.de Sun Jun 6 15:42:53 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 16:42:53 +0200 (CEST) Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606141049.GB11281@inxservices.com> References: <20040606141049.GB11281@inxservices.com> Message-ID: <20040606.164253.572697249.rene@rocklinux-consulting.de> Hi, On: Sun, 6 Jun 2004 07:10:49 -0700, George Garvey wrote: > I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and > 2.6.6-1.422 and this scanner. > These are with Fedora sane-backends-1.0.14-1. I replaced the avisi= on > files with the latest from Rene's SVN yesterday and rebuilt the RPMS.= These > messages are from after using this newly built RPM. The problem was > happening before, with the standard RPM from Fedora. This is what pro= mpted > trying the beta version. Hm - works here on 2.6.3 on an UltraSPARC and an iBook. I can test 2.6.6 in the next days - but I heared here on this list that recent 2.6 kernels have some USB problem(s)? Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From keith@claytons.org Sun Jun 6 17:36:42 2004 From: keith@claytons.org (Keith Clayton) Date: Sun, 6 Jun 2004 09:36:42 -0700 (PDT) Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606100716.GH19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: In my case, w/problems scanning from win32-xsane across the network using an Epson Perfection 1250, I commented out all backends except net and plustek from dll.conf. This had no impact on my problem, where I could sucessfully scan once but then the scanner is left in an unusable state and and additional scan from any other machine fails. Keith On Sun, 6 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > Everyone who gets timeouts/USB errors with these two scanners and > sane-backends 1.0.14 please use the following workaround: > Comment out the "epson" line in dll.conf (/etc/sane.d/ or > /usr/local/etc/sane.d/). > > The epson backend seems to try to talk to these scanners because they > are Epson scanners. As they are supported by the plustek backend (not > epson) the scanners don't like the epson commands and USB errors occur. > > See bug 300751 for details: > https://alioth.debian.org/tracker/index.php?group_id=1308&atid=410366 > > I guess that bug didn't show up before the 1.0.14 release because the > automatic detection for USB scanners in the epson backend wasn't > turned on. > > Bye, > Henning > > From henning@meier-geinitz.de Sun Jun 6 17:41:31 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 18:41:31 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: <20040606164131.GL19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 09:36:42AM -0700, Keith Clayton wrote: > In my case, w/problems scanning from win32-xsane across the network using > an Epson Perfection 1250, I commented out all backends except net and > plustek from dll.conf. > > This had no impact on my problem, where I could > sucessfully scan once but then the scanner is left in an unusable state > and and additional scan from any other machine fails. Not all problems are caused by that bug :-) If your problem was caused by that bug, you wouldn't be able to scan locally. Bye, Henning From henning@meier-geinitz.de Sun Jun 6 17:50:23 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 18:50:23 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086458420.26103.10.camel@yoda> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> Message-ID: <20040606165023.GM19373@meier-geinitz.de> Hi, On Sat, Jun 05, 2004 at 11:00:23AM -0700, Keith Clayton wrote: > scanimage -d net:localhost:plustek works perfectly. Can scan as many > times consecutively as I'd like. > > win32-xsane continues to fail on the 2nd scan. After power-cycling the > scanner I ran win32-xsane first then scanimage from the local machine. > Scanimage failed in this case. First pass of win32-xsane is evidently > leaving the scanner in a bad state. Used the debug flags as you > suggested and captured the output. Something is definitely going wrong > at the end of the win32-xsane/saned scan. > > I've attached the gzip output of running saned as you suggested with > debugging on and xinetd disabled. I X'd out any host, IP info from the > top of the log files but otherwise they're exactly what the debug kicked > out. Local: [...] [plustek] sane_cancel [plustek] do_cancel [plustek] TIME END 2: 20s [saned] process_request: waiting for request [saned] process_request: got request 3 [plustek] sane_close [saned] process_request: waiting for request [saned] process_request: got request 10 [plustek] sane_exit [plustek] Shutdown called (dev->fd=-1, libusb:001:013) [plustek] Waiting for scanner-ready... [plustek] Switching lamp off... [plustek] REG[0x5b] = 0x94 (msk=0x80) [plustek] REG[0x59] = 0x41 (msk=0x08) [plustek] LAMP-STATUS: 0x00000001 [plustek] Switching Lamp off [plustek] usb_switchLampX(ON=0,TPA=0) [plustek] Switch Lamp: 0, regs[0x5b] = 0x14 [plustek] REG[0x5b] = 0x14 (msk=0x80) [plustek] REG[0x59] = 0x41 (msk=0x08) [plustek] LAMP-STATUS: 0x00000000 [plustek] Lamp-Timer stopped [saned] quit: exiting Looks sane :-) The scan is cancelled, the device is closed and then sane_exit is called. net: [plustek] sane_cancel [plustek] do_cancel [plustek] TIME END 2: 88s [saned] process_request: waiting for request [saned] process_request: got request 5 [saned] process_request: waiting for request [saned] process_request: got request 5 [...] After sane-cancel() neither sane_close nor sane_exit() is called. That may cause a scanner to hang. The rquest 5 which is repeated some times is sane_control_option. Not too unusual, but xsane just seems to crash at that point so sane isn't closed correctly. Or saned crashes but you should get a segmentation fault or similar at that point. However, it's strange that "[saned] quit: exiting" is missing. Bye, Henning From sietse@cs.rug.nl Sun Jun 6 18:21:07 2004 From: sietse@cs.rug.nl (Sietse Achterop) Date: Sun, 06 Jun 2004 19:21:07 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606.164253.572697249.rene@rocklinux-consulting.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> Message-ID: <40C35283.1090507@cs.rug.nl> Rene Rebe wrote: > >> I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and >>2.6.6-1.422 and this scanner. > ...... > > Hm - works here on 2.6.3 on an UltraSPARC and an iBook. I can test > 2.6.6 in the next days - but I heared here on this list that recent > 2.6 kernels have some USB problem(s)? > Hi, Indeed, and I just retried it using the latest kernel (2.6.7-rc2-bk7) and the problem stays the same; somehow a bulk transport in usb falls in a timeout. Now the /var/log/kernel mentions: Jun 6 19:05:01 localhost kernel: usb 1-1: new full speed USB device using address 3 Jun 6 19:06:11 localhost kernel: usb 1-1: bulk timeout on ep3in Jun 6 19:06:11 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 Jun 6 19:06:41 localhost kernel: usb 1-1: bulk timeout on ep2in Jun 6 19:06:41 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 1 ret -110 Jun 6 19:06:44 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 22 ret -84 Jun 6 19:06:44 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x1 len 10 ret -71 Jun 6 19:06:44 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 1 ret -84 Jun 6 19:06:44 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x1 len 6 ret -71 See also my report from May 10, see: http://lists.alioth.debian.org/pipermail/sane-devel/2004-May/010985.html So I am afraid the problem still persists, with my HP7400C anyway. Greetings, Sietse Achterop From keith@claytons.org Sun Jun 6 18:27:57 2004 From: keith@claytons.org (Keith Clayton) Date: Sun, 6 Jun 2004 10:27:57 -0700 (PDT) Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040606165023.GM19373@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> Message-ID: No seg fault on the saned end. Its happily running, waiting to finish up. Xsane itself remains responsive. I can open menus, quit the app, etc. Not knowing the xsane code, does it start a child process to initiate scanning and maybe that process has crashed/hung? I'll look at the windows machine more. I can do a tcpdump capture of the communication if that would be helpful. K On Sun, 6 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > On Sat, Jun 05, 2004 at 11:00:23AM -0700, Keith Clayton wrote: > > scanimage -d net:localhost:plustek works perfectly. Can scan as many > > times consecutively as I'd like. > > > > win32-xsane continues to fail on the 2nd scan. After power-cycling the > > scanner I ran win32-xsane first then scanimage from the local machine. > > Scanimage failed in this case. First pass of win32-xsane is evidently > > leaving the scanner in a bad state. Used the debug flags as you > > suggested and captured the output. Something is definitely going wrong > > at the end of the win32-xsane/saned scan. > > > > I've attached the gzip output of running saned as you suggested with > > debugging on and xinetd disabled. I X'd out any host, IP info from the > > top of the log files but otherwise they're exactly what the debug kicked > > out. > > Local: > [...] > [plustek] sane_cancel > [plustek] do_cancel > [plustek] TIME END 2: 20s > [saned] process_request: waiting for request > [saned] process_request: got request 3 > [plustek] sane_close > [saned] process_request: waiting for request > [saned] process_request: got request 10 > [plustek] sane_exit > [plustek] Shutdown called (dev->fd=-1, libusb:001:013) > [plustek] Waiting for scanner-ready... > [plustek] Switching lamp off... > [plustek] REG[0x5b] = 0x94 (msk=0x80) > [plustek] REG[0x59] = 0x41 (msk=0x08) > [plustek] LAMP-STATUS: 0x00000001 > [plustek] Switching Lamp off > [plustek] usb_switchLampX(ON=0,TPA=0) > [plustek] Switch Lamp: 0, regs[0x5b] = 0x14 > [plustek] REG[0x5b] = 0x14 (msk=0x80) > [plustek] REG[0x59] = 0x41 (msk=0x08) > [plustek] LAMP-STATUS: 0x00000000 > [plustek] Lamp-Timer stopped > [saned] quit: exiting > > Looks sane :-) The scan is cancelled, the device is closed and then > sane_exit is called. > > net: > [plustek] sane_cancel > [plustek] do_cancel > [plustek] TIME END 2: 88s > [saned] process_request: waiting for request > [saned] process_request: got request 5 > [saned] process_request: waiting for request > [saned] process_request: got request 5 > [...] > > After sane-cancel() neither sane_close nor sane_exit() is called. That > may cause a scanner to hang. The rquest 5 which is repeated some times > is sane_control_option. Not too unusual, but xsane just seems to crash > at that point so sane isn't closed correctly. Or saned crashes but you > should get a segmentation fault or similar at that point. However, > it's strange that "[saned] quit: exiting" is missing. > > Bye, > Henning > > From rene@rocklinux-consulting.de Sun Jun 6 18:42:42 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 19:42:42 +0200 (CEST) Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <40C35283.1090507@cs.rug.nl> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> Message-ID: <20040606.194242.85423590.rene@rocklinux-consulting.de> Hi, On: Sun, 06 Jun 2004 19:21:07 +0200, Sietse Achterop wrote: > Hi, > = > Indeed, and I just retried it using the latest kernel (2.6.7-rc2-bk7)= and > the problem stays the same; somehow a bulk transport in usb falls in = a timeout. > So I am afraid the problem still persists, with my HP7400C anyway. Have you tried if it works on your side with an older kernel? Say 2.6.3 or so? Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From sietse@cs.rug.nl Sun Jun 6 19:03:57 2004 From: sietse@cs.rug.nl (Sietse Achterop) Date: Sun, 06 Jun 2004 20:03:57 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606.194242.85423590.rene@rocklinux-consulting.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> Message-ID: <40C35C8D.7040401@cs.rug.nl> Rene Rebe wrote: > >>So I am afraid the problem still persists, with my HP7400C anyway. > > > Have you tried if it works on your side with an older kernel? Say > 2.6.3 or so? > No, I made the change to 2.6 after that one I think. Would it be usefull to test it with that version? If so I could test that. Regards, Sietse From insane@piments.com Sun Jun 6 19:12:51 2004 From: insane@piments.com (insane@piments.com) Date: Sun, 06 Jun 2004 20:12:51 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <40C35283.1090507@cs.rug.nl> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> Message-ID: Hi, Yes this seems to be a pretty broad issue with sane/libusb and more recent 2.6.x kernels I am getting very similar behaviour from my canoscan FB636U on Athlon-XP/Gentoo/2.6.6 kernel. [ebuild R ] media-gfx/xsane-0.93 [ebuild R ] media-gfx/sane-backends-1.0.14-r2 [ebuild R ] dev-libs/libusb-0.1.8 It was scanning briefly at one stage and I think I was running early 2.6 kernels at that time although I can not be precise. I does not appear to be a problem in the kernel itself since vuescan works perfectly on this system. If sane is going to continue to be an option it appears some dev work is needed to resolve this issue. I emailed Oliver Rauch and he indicated I should contact the backend maintainer (who apparently no longer replies to bug reports). But it seems from some of the posts here that the issue is much larger. Could someone remind me what the debug line is for this scanner so I can get more detailed output. Thanks, Peter. On Sun, 06 Jun 2004 19:21:07 +0200, Sietse Achterop wrote: > Rene Rebe wrote: >> >>> I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and >>> 2.6.6-1.422 and this scanner. >> > ...... >> Hm - works here on 2.6.3 on an UltraSPARC and an iBook. I can test >> 2.6.6 in the next days - but I heared here on this list that recent >> 2.6 kernels have some USB problem(s)? >> > > Hi, > > Indeed, and I just retried it using the latest kernel (2.6.7-rc2-bk7) and > the problem stays the same; somehow a bulk transport in usb falls in a > timeout. > Now the /var/log/kernel mentions: > > Jun 6 19:05:01 localhost kernel: usb 1-1: new full speed USB device > using address 3 > Jun 6 19:06:11 localhost kernel: usb 1-1: bulk timeout on ep3in > Jun 6 19:06:11 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed > ep 0x83 len 4096 ret -110 > Jun 6 19:06:41 localhost kernel: usb 1-1: bulk timeout on ep2in -- Using M2, Opera's e-mail client: on Gentoo Linux From henning@meier-geinitz.de Sun Jun 6 19:03:54 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 20:03:54 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606.194242.85423590.rene@rocklinux-consulting.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> Message-ID: <20040606180354.GO19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 07:42:42PM +0200, Rene Rebe wrote: > > So I am afraid the problem still persists, with my HP7400C anyway. > > Have you tried if it works on your side with an older kernel? Say > 2.6.3 or so? The gt68xx backend once had a bug that caused timeouts and frozen scanners. However, that bug only occured with some scanners and only with UHCI host controllers. As I used an OHCI controller at that time, I couldn't reproduce the bug at all. But it did exist. So looking at which kind of host controller the bug shows up and even which mainboard is used may help to find out what's actually going on. Bye, Henning From rene@rocklinux-consulting.de Sun Jun 6 19:24:22 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 20:24:22 +0200 (CEST) Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <40C35C8D.7040401@cs.rug.nl> References: <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> <40C35C8D.7040401@cs.rug.nl> Message-ID: <20040606.202422.805788455.rene@rocklinux-consulting.de> Hi, On: Sun, 06 Jun 2004 20:03:57 +0200, Sietse Achterop wrote: > No, I made the change to 2.6 after that one I think. > Would it be usefull to test it with that version? Yes - please test it. Also, what USB host controler type fo you have? Ohci, uhci or ehci? It can be obtained from /proc/bus/usb/devices - maybe just mail it if you are unsure ... > If so I could test that. > = > Regards, > Sietse Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From henning@meier-geinitz.de Sun Jun 6 19:25:52 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 20:25:52 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> Message-ID: <20040606182552.GP19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 08:12:51PM +0200, insane@piments.com wrote: > Yes this seems to be a pretty broad issue with sane/libusb and more recent > 2.6.x kernels > > I am getting very similar behaviour from my canoscan FB636U on > Athlon-XP/Gentoo/2.6.6 kernel. That scanner is listed as "untested" so you were lucky if it worked. > [ebuild R ] media-gfx/xsane-0.93 > [ebuild R ] media-gfx/sane-backends-1.0.14-r2 > [ebuild R ] dev-libs/libusb-0.1.8 Some more data points: Linux 2.6.7rc2, ohci host controller, libusb 0.1.8 The following scanners do work without any trouble: Mustek 1200 CU (mustek_usb) Mustek BearPaw 1200 CU (gt68xx) Mustek BearPaw 2400 CU Plus (gt68xx) Plustek OpticPro U16B (gt68xx) Plustek Opticpro UT16 (plustek) > It was scanning briefly at one stage and I think I was running early 2.6 > kernels at that time although I can not be precise. > > I does not appear to be a problem in the kernel itself since vuescan works > perfectly on this system. That may be a hint, but needn't as SANE may trigger a bug in the kernel by accessing the scanner differently. > If sane is going to continue to be an option it appears some dev work is > needed to resolve this issue. First, we need to find out when this bug happens and in which part of SANE or the kernel it is. > Could someone remind me what the debug line is for this scanner so I can > get more detailed output. export SANE_DEBUG_CANON630U=255 For USB debug messages try also: export SANE_DEBUG_SANEI_USB=255 Bye, Henning From henning@meier-geinitz.de Sun Jun 6 20:12:18 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 21:12:18 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606182552.GP19373@meier-geinitz.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606182552.GP19373@meier-geinitz.de> Message-ID: <20040606191218.GQ19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 08:25:52PM +0200, Henning Meier-Geinitz wrote: > > Yes this seems to be a pretty broad issue with sane/libusb and more recent > > 2.6.x kernels As already mentioned on this list and in the bug tracking system (https://alioth.debian.org/tracker/index.php?func=detail&aid=300759&group_id=1308&atid=410366) scanning fails with libusb if the scanner is accessed during that scan. This access can even be caused by sane-find-scanner. Maybe these two problems are in fact the same? E.g. when some hotplugscript tries to access the scanner while it's opened by sane? I don't know if it's at least theoretically possible to cause the double access bug by a bug in sane. As the libusb device is claimed by sane, it shouldn't be possible to send anything to the device while the interface is claimed. Bye, Henning From insane@piments.com Sun Jun 6 20:35:56 2004 From: insane@piments.com (insane@piments.com) Date: Sun, 06 Jun 2004 21:35:56 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606182552.GP19373@meier-geinitz.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606182552.GP19373@meier-geinitz.de> Message-ID: Thanks Henning, > That scanner is listed as "untested" so you were lucky if it worked. True but it seems to be very close to the FB630U for which the backend was written. Anyway it has worked with sane at one stage, and pretty well. Hopefully I can soon provide some feedback and it will be classed as tested! > SANE may trigger a bug in the > kernel by accessing the scanner differently. Fair point, vuescan does not prove anything more that the hardware is good and CAN work on Linux. 0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) 0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) So I am on UHCI, seems like others having pbs are using this driver as well (I also compiled ehci as module but it did not change the bahaviour). Here's an end snip of the USB debug output. [sanei_usb] 0000: 01 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132, index = 0, len = 1 [sanei_usb] 0000: 00 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 12, value = 131, index = 0, len = 1 [sanei_usb] 0000: 01 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132, index = 0, len = 1 [sanei_usb] 0000: 00 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 12, value = 131, index = 0, len = 1 [sanei_usb] 0000: 01 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132, index = 0, len = 1 [sanei_usb] 0000: 00 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 12, value = 131, index = 0, len = 1 [sanei_usb] 0000: 01 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132, index = 0, len = 1 This is the loop it gets stuck in and hangs sane. xsane xscanimage etc. all lock up. I Cntl-C out at this point. Now here's the end of the Canon_bebug output: [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ I dont know if that enables you to see more of what is happening. Regards, Peter. On Sun, 6 Jun 2004 20:25:52 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Sun, Jun 06, 2004 at 08:12:51PM +0200, insane@piments.com wrote: >> Yes this seems to be a pretty broad issue with sane/libusb and more >> recent >> 2.6.x kernels >> >> I am getting very similar behaviour from my canoscan FB636U on >> Athlon-XP/Gentoo/2.6.6 kernel. > > That scanner is listed as "untested" so you were lucky if it worked. > >> [ebuild R ] media-gfx/xsane-0.93 >> [ebuild R ] media-gfx/sane-backends-1.0.14-r2 >> [ebuild R ] dev-libs/libusb-0.1.8 > > Some more data points: Linux 2.6.7rc2, ohci host controller, libusb 0.1.8 > > The following scanners do work without any trouble: > > Mustek 1200 CU (mustek_usb) > Mustek BearPaw 1200 CU (gt68xx) > Mustek BearPaw 2400 CU Plus (gt68xx) > Plustek OpticPro U16B (gt68xx) > Plustek Opticpro UT16 (plustek) > >> It was scanning briefly at one stage and I think I was running early 2.6 >> kernels at that time although I can not be precise. >> >> I does not appear to be a problem in the kernel itself since vuescan >> works >> perfectly on this system. > > That may be a hint, but needn't as SANE may trigger a bug in the > kernel by accessing the scanner differently. > >> If sane is going to continue to be an option it appears some dev work is >> needed to resolve this issue. > > First, we need to find out when this bug happens and in which part of > SANE or the kernel it is. > >> Could someone remind me what the debug line is for this scanner so I can >> get more detailed output. > > export SANE_DEBUG_CANON630U=255 > > For USB debug messages try also: > > export SANE_DEBUG_SANEI_USB=255 > > Bye, > Henning > -- Using M2, Opera's e-mail client: on Gentoo Linux From sietse@cs.rug.nl Sun Jun 6 20:47:03 2004 From: sietse@cs.rug.nl (Sietse Achterop) Date: Sun, 06 Jun 2004 21:47:03 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606.202422.805788455.rene@rocklinux-consulting.de> References: <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> <40C35C8D.7040401@cs.rug.nl> <20040606.202422.805788455.rene@rocklinux-consulting.de> Message-ID: <40C374B7.6010806@cs.rug.nl> Rene Rebe wrote: > Yes - please test it. Hi, just tested kernel 2.6.3 and it has exactly the same problem:(. > > Also, what USB host controler type fo you have? Ohci, uhci or ehci? > It can be obtained from /proc/bus/usb/devices - maybe just mail it if > you are unsure ... > Uhci is used and a 440LX chipset with a Pentium II (333 MHz). It is an Asus P2L-B motherboard. Regards, Sietse ================================================== From /proc/bus/usb/devices : S: Manufacturer=Linux 2.6.7-rc2-bk7 uhci_hcd S: Product=Intel Corp. 82371AB/EB/MB PIIX4 USB And from lspci: 0000:00:00.0 Host bridge: Intel Corp. 440LX/EX - 82443LX/EX Host bridge (rev 03) 0000:00:01.0 PCI bridge: Intel Corp. 440LX/EX - 82443LX/EX AGP bridge (rev 03) 0000:00:04.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 01) 0000:00:04.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) 0000:00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) 0000:00:04.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 01) 0000:00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) 0000:00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 0000:01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4400] (rev a2) From r3ddr@yahoo.com Sun Jun 6 20:49:23 2004 From: r3ddr@yahoo.com (Ciprian Manea) Date: Sun, 6 Jun 2004 12:49:23 -0700 (PDT) Subject: [sane-devel] sane :: plustek opticslim m12 In-Reply-To: <1086435353.11282.ezmlm@linuxhacker.org> Message-ID: <20040606194923.78653.qmail@web50405.mail.yahoo.com> --0-9979661-1086551363=:78634 Content-Type: text/plain; charset=us-ascii Content-Id: Content-Disposition: inline Now I have another problem :| ps. yes, OpticSlim M12 it's an AutoFeed scanner (small format, marketted as a notebook scanner :) I tried to "fix" the source, and make scanimage ignore this 'power' stuff, but then the "scanning" is verry erratic. it will feed the page, too fast to do any scanning I guess (indicator light will be solid green. usually under Win the light is blinking during operation/scanning); then it will properly eject the page (that is, feeding it much faster to the 'exit' :) Any advice on what should be done from this point? thanks! # scanimage [gt68xx] sane_open: power control failure: check power plug! scanimage: open of device gt68xx:/dev/usb/scanner0 failed: Error during device I/O output with SANE_DEBUG_GT68XX=255 in the attached file ===== http://nou.surse.ro - Portalul tau cu stiri, informatii si resurse online. __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ --0-9979661-1086551363=:78634 Content-Type: text/plain; name="scan.txt" Content-Description: scan.txt Content-Disposition: inline; filename="scan.txt" [sanei_debug] Setting debug level of gt68xx to 255. [gt68xx] SANE GT68xx backend version 1.0 build 60 from sane-backends 1.0.14-cvs [gt68xx] sane_init: authorize != null [gt68xx] sane_init: debug options are enabled, handle with care [gt68xx] sane_init: little endian machine [gt68xx] sane_init: reading config file `gt68xx.conf' [gt68xx] sane_init: config file line 1: ignoring empty line [gt68xx] sane_init: config file line 2: ignoring comment line [gt68xx] sane_init: config file line 3: ignoring comment line [gt68xx] sane_init: config file line 4: ignoring empty line [gt68xx] sane_init: config file line 5: ignoring comment line [gt68xx] sane_init: config file line 6: ignoring comment line [gt68xx] sane_init: config file line 7: ignoring comment line [gt68xx] sane_init: config file line 8: ignoring comment line [gt68xx] sane_init: config file line 9: ignoring empty line [gt68xx] sane_init: config file line 10: ignoring comment line [gt68xx] sane_init: config file line 11: ignoring comment line [gt68xx] sane_init: config file line 12: ignoring comment line [gt68xx] sane_init: config file line 13: trying to attach `usb 0x05d8 0x4002' [gt68xx] sane_init: config file line 14: ignoring empty line [gt68xx] sane_init: config file line 15: ignoring comment line [gt68xx] sane_init: config file line 16: ignoring empty line [gt68xx] sane_init: config file line 17: ignoring comment line [gt68xx] sane_init: config file line 18: ignoring comment line [gt68xx] sane_init: config file line 19: ignoring empty line [gt68xx] sane_init: config file line 20: ignoring comment line [gt68xx] sane_init: config file line 21: ignoring comment line [gt68xx] sane_init: config file line 22: ignoring comment line [gt68xx] sane_init: config file line 23: ignoring comment line [gt68xx] sane_init: config file line 24: ignoring empty line [gt68xx] sane_init: config file line 25: ignoring comment line [gt68xx] sane_init: config file line 26: ignoring comment line [gt68xx] sane_init: config file line 27: ignoring comment line [gt68xx] sane_init: config file line 28: ignoring comment line [gt68xx] sane_init: config file line 29: ignoring empty line [gt68xx] sane_init: config file line 30: ignoring comment line [gt68xx] sane_init: config file line 31: ignoring comment line [gt68xx] sane_init: config file line 32: ignoring empty line [gt68xx] sane_init: config file line 33: ignoring comment line [gt68xx] sane_init: config file line 34: ignoring comment line [gt68xx] sane_init: config file line 35: ignoring comment line [gt68xx] sane_init: config file line 36: ignoring empty line [gt68xx] sane_init: config file line 37: ignoring comment line [gt68xx] sane_init: config file line 38: ignoring comment line [gt68xx] sane_init: config file line 39: ignoring comment line [gt68xx] sane_init: config file line 40: ignoring comment line [gt68xx] sane_init: config file line 41: ignoring empty line [gt68xx] sane_init: config file line 42: ignoring comment line [gt68xx] sane_init: config file line 43: ignoring comment line [gt68xx] sane_init: config file line 44: ignoring comment line [gt68xx] sane_init: config file line 45: ignoring comment line [gt68xx] sane_init: config file line 46: ignoring empty line [gt68xx] sane_init: config file line 47: ignoring comment line [gt68xx] sane_init: config file line 48: ignoring comment line [gt68xx] sane_init: config file line 49: ignoring comment line [gt68xx] sane_init: config file line 50: ignoring comment line [gt68xx] sane_init: config file line 51: ignoring empty line [gt68xx] sane_init: config file line 52: ignoring comment line [gt68xx] sane_init: config file line 53: ignoring comment line [gt68xx] sane_init: config file line 54: ignoring comment line [gt68xx] sane_init: config file line 55: ignoring comment line [gt68xx] sane_init: config file line 56: ignoring empty line [gt68xx] sane_init: config file line 57: ignoring comment line [gt68xx] sane_init: config file line 58: ignoring comment line [gt68xx] sane_init: config file line 59: ignoring empty line [gt68xx] sane_init: config file line 60: ignoring comment line [gt68xx] sane_init: config file line 61: ignoring comment line [gt68xx] sane_init: config file line 62: ignoring comment line [gt68xx] sane_init: config file line 63: ignoring comment line [gt68xx] sane_init: config file line 64: ignoring empty line [gt68xx] sane_init: config file line 65: ignoring comment line [gt68xx] sane_init: config file line 66: ignoring comment line [gt68xx] sane_init: config file line 67: trying to attach `usb 0x055f 0x021e' [gt68xx] sane_init: config file line 68: ignoring empty line [gt68xx] sane_init: config file line 69: ignoring comment line [gt68xx] sane_init: config file line 70: ignoring empty line [gt68xx] sane_init: config file line 71: ignoring comment line [gt68xx] sane_init: config file line 72: ignoring comment line [gt68xx] sane_init: config file line 73: ignoring empty line [gt68xx] sane_init: config file line 74: ignoring comment line [gt68xx] sane_init: config file line 75: ignoring comment line [gt68xx] sane_init: config file line 76: trying to attach `usb 0x055f 0x0218' [gt68xx] sane_init: config file line 77: ignoring empty line [gt68xx] sane_init: config file line 78: ignoring comment line [gt68xx] sane_init: config file line 79: ignoring empty line [gt68xx] sane_init: config file line 80: ignoring comment line [gt68xx] sane_init: config file line 81: ignoring comment line [gt68xx] sane_init: config file line 82: ignoring empty line [gt68xx] sane_init: config file line 83: ignoring comment line [gt68xx] sane_init: config file line 84: ignoring comment line [gt68xx] sane_init: config file line 85: trying to attach `usb 0x055f 0x0219' [gt68xx] sane_init: config file line 86: ignoring empty line [gt68xx] sane_init: config file line 87: ignoring comment line [gt68xx] sane_init: config file line 88: ignoring comment line [gt68xx] sane_init: config file line 89: trying to attach `usb 0x055f 0x021a' [gt68xx] sane_init: config file line 90: ignoring empty line [gt68xx] sane_init: config file line 91: ignoring comment line [gt68xx] sane_init: config file line 92: ignoring comment line [gt68xx] sane_init: config file line 93: ignoring empty line [gt68xx] sane_init: config file line 94: ignoring comment line [gt68xx] sane_init: config file line 95: ignoring comment line [gt68xx] sane_init: config file line 96: trying to attach `usb 0x055f 0x021d' [gt68xx] sane_init: config file line 97: ignoring empty line [gt68xx] sane_init: config file line 98: ignoring comment line [gt68xx] sane_init: config file line 99: ignoring comment line [gt68xx] sane_init: config file line 100: trying to attach `usb 0x055f 0x021c' [gt68xx] sane_init: config file line 101: ignoring empty line [gt68xx] sane_init: config file line 102: ignoring comment line [gt68xx] sane_init: config file line 103: ignoring empty line [gt68xx] sane_init: config file line 104: ignoring comment line [gt68xx] sane_init: config file line 105: ignoring comment line [gt68xx] sane_init: config file line 106: ignoring comment line [gt68xx] sane_init: config file line 107: ignoring empty line [gt68xx] sane_init: config file line 108: ignoring comment line [gt68xx] sane_init: config file line 109: ignoring comment line [gt68xx] sane_init: config file line 110: trying to attach `usb 0x055f 0x0210' [gt68xx] sane_init: config file line 111: ignoring empty line [gt68xx] sane_init: config file line 112: ignoring comment line [gt68xx] sane_init: config file line 113: ignoring empty line [gt68xx] sane_init: config file line 114: ignoring comment line [gt68xx] sane_init: config file line 115: ignoring comment line [gt68xx] sane_init: config file line 116: trying to attach `usb 0x043d 0x002d' [gt68xx] sane_init: config file line 117: ignoring empty line [gt68xx] sane_init: config file line 118: ignoring comment line [gt68xx] sane_init: config file line 119: ignoring comment line [gt68xx] sane_init: config file line 120: trying to attach `usb 0x07b3 0x0401' [gt68xx] sane_init: config file line 121: trying to attach `usb 0x07b3 0x0400' [gt68xx] sane_init: config file line 122: ignoring empty line [gt68xx] sane_init: config file line 123: ignoring comment line [gt68xx] sane_init: config file line 124: ignoring empty line [gt68xx] sane_init: config file line 125: ignoring comment line [gt68xx] sane_init: config file line 126: ignoring comment line [gt68xx] sane_init: config file line 127: ignoring comment line [gt68xx] sane_init: config file line 128: ignoring empty line [gt68xx] sane_init: config file line 129: ignoring comment line [gt68xx] sane_init: config file line 130: ignoring comment line [gt68xx] sane_init: config file line 131: trying to attach `usb 0x07b3 0x0402' [gt68xx] sane_init: config file line 132: trying to attach `usb 0x07b3 0x0403' [gt68xx] sane_init: config file line 133: ignoring empty line [gt68xx] sane_init: config file line 134: ignoring comment line [gt68xx] sane_init: config file line 135: ignoring empty line [gt68xx] sane_init: config file line 136: ignoring comment line [gt68xx] sane_init: config file line 137: ignoring comment line [gt68xx] sane_init: config file line 138: ignoring empty line [gt68xx] sane_init: config file line 139: ignoring comment line [gt68xx] sane_init: config file line 140: ignoring comment line [gt68xx] sane_init: config file line 141: trying to attach `usb 0x07b3 0x0412' [gt68xx] attach: start: devp != NULL, may_wait = 0 [gt68xx] attach: trying to open device `/dev/usb/scanner0' [gt68xx] gt68xx_device_new: enter [gt68xx] gt68xx_device_new:: leave: ok [gt68xx] gt68xx_device_open: enter: dev=0x80859e0 [gt68xx] gt68xx_device_open: leave: ok [gt68xx] attach: device `/dev/usb/scanner0' successfully opened [gt68xx] attach: found Plustek flatbed scanner OpticSlim M12 at /dev/usb/scanner0 [gt68xx] gt68xx_device_close: enter: dev=0x80859e0 [gt68xx] gt68xx_device_close: leave: ok [gt68xx] attach: exit [gt68xx] attach: start: devp != NULL, may_wait = 0 [gt68xx] attach: trying to open device `libusb:001:011' [gt68xx] gt68xx_device_new: enter [gt68xx] gt68xx_device_new:: leave: ok [gt68xx] gt68xx_device_open: enter: dev=0x8085a58 [gt68xx] gt68xx_device_open: sanei_usb_open failed: Device busy [gt68xx] attach: couldn't open device `libusb:001:011': Device busy [gt68xx] gt68xx_device_free: enter: dev=0x8085a58 [gt68xx] gt68xx_device_free: freeing dev [gt68xx] gt68xx_device_free: leave: ok [gt68xx] somewhere: attach (devname, &dev, 0): Device busy [gt68xx] sane_init: config file line 142: ignoring empty line [gt68xx] sane_init: config file line 143: ignoring comment line [gt68xx] sane_init: config file line 144: ignoring comment line [gt68xx] sane_init: config file line 145: trying to attach `usb 0x07b3 0x0413' [gt68xx] sane_init: config file line 146: ignoring empty line [gt68xx] sane_init: config file line 147: ignoring comment line [gt68xx] sane_init: config file line 148: ignoring comment line [gt68xx] sane_init: config file line 149: trying to attach `usb 0x07b3 0x0422' [gt68xx] sane_init: config file line 150: ignoring empty line [gt68xx] sane_init: config file line 151: ignoring comment line [gt68xx] sane_init: config file line 152: ignoring comment line [gt68xx] sane_init: config file line 153: trying to attach `usb 0x0458 0x2011' [gt68xx] sane_init: config file line 154: ignoring empty line [gt68xx] sane_init: config file line 155: ignoring comment line [gt68xx] sane_init: config file line 156: ignoring empty line [gt68xx] sane_init: config file line 157: ignoring comment line [gt68xx] sane_init: config file line 158: ignoring comment line [gt68xx] sane_init: config file line 159: trying to attach `usb 0x0458 0x201b' [gt68xx] sane_init: config file line 160: ignoring empty line [gt68xx] sane_init: config file line 161: ignoring comment line [gt68xx] sane_init: config file line 162: ignoring comment line [gt68xx] sane_init: config file line 163: trying to attach `usb 0x0458 0x2017' [gt68xx] sane_init: config file line 164: ignoring empty line [gt68xx] sane_init: config file line 165: ignoring comment line [gt68xx] sane_init: config file line 166: ignoring comment line [gt68xx] sane_init: config file line 167: trying to attach `usb 0x0458 0x201a' [gt68xx] sane_init: config file line 168: ignoring empty line [gt68xx] sane_init: config file line 169: ignoring comment line [gt68xx] sane_init: config file line 170: ignoring comment line [gt68xx] sane_init: config file line 171: trying to attach `usb 0x0458 0x201f' [gt68xx] sane_init: config file line 172: ignoring empty line [gt68xx] sane_init: config file line 173: ignoring comment line [gt68xx] sane_init: config file line 174: ignoring comment line [gt68xx] sane_init: config file line 175: trying to attach `usb 0x0458 0x2014' [gt68xx] sane_init: config file line 176: ignoring empty line [gt68xx] sane_init: config file line 177: ignoring comment line [gt68xx] sane_init: config file line 178: ignoring comment line [gt68xx] sane_init: config file line 179: trying to attach `usb 0x04a7 0x0444' [gt68xx] sane_init: config file line 180: ignoring empty line [gt68xx] sane_init: config file line 181: ignoring comment line [gt68xx] sane_init: exit [gt68xx] sane_get_devices: start: local_only = false [gt68xx] sane_get_devices: exit [gt68xx] sane_open: start (devicename = `/dev/usb/scanner0') [gt68xx] sane_open: found `plustek-opticslim-m12' in devlist [gt68xx] gt68xx_device_open: enter: dev=0x80859e0 [gt68xx] gt68xx_device_open: leave: ok [gt68xx] gt68xx_device_activate: model "plustek-opticslim-m12" [gt68xx] download_firmware: trying /usr/local/share/sane/gt68xx/cism216.fw [gt68xx] firmware size: 8192 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x0, size=0x40, data=0x8095968 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x40, size=0x40, data=0x80959a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x80, size=0x40, data=0x80959e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xc0, size=0x40, data=0x8095a28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x100, size=0x40, data=0x8095a68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x100, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x140, size=0x40, data=0x8095aa8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x140, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x180, size=0x40, data=0x8095ae8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x180, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1c0, size=0x40, data=0x8095b28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x200, size=0x40, data=0x8095b68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x200, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x240, size=0x40, data=0x8095ba8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x240, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x280, size=0x40, data=0x8095be8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x280, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x2c0, size=0x40, data=0x8095c28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x2c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x300, size=0x40, data=0x8095c68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x300, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x340, size=0x40, data=0x8095ca8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x340, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x380, size=0x40, data=0x8095ce8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x380, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x3c0, size=0x40, data=0x8095d28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x3c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x400, size=0x40, data=0x8095d68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x400, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x440, size=0x40, data=0x8095da8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x440, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x480, size=0x40, data=0x8095de8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x480, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x4c0, size=0x40, data=0x8095e28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x4c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x500, size=0x40, data=0x8095e68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x500, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x540, size=0x40, data=0x8095ea8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x540, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x580, size=0x40, data=0x8095ee8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x580, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x5c0, size=0x40, data=0x8095f28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x5c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x600, size=0x40, data=0x8095f68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x600, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x640, size=0x40, data=0x8095fa8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x640, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x680, size=0x40, data=0x8095fe8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x680, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x6c0, size=0x40, data=0x8096028 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x6c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x700, size=0x40, data=0x8096068 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x700, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x740, size=0x40, data=0x80960a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x740, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x780, size=0x40, data=0x80960e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x780, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x7c0, size=0x40, data=0x8096128 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x7c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x800, size=0x40, data=0x8096168 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x800, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x840, size=0x40, data=0x80961a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x840, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x880, size=0x40, data=0x80961e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x880, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x8c0, size=0x40, data=0x8096228 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x8c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x900, size=0x40, data=0x8096268 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x900, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x940, size=0x40, data=0x80962a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x940, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x980, size=0x40, data=0x80962e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x980, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x9c0, size=0x40, data=0x8096328 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x9c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xa00, size=0x40, data=0x8096368 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xa00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xa40, size=0x40, data=0x80963a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xa40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xa80, size=0x40, data=0x80963e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xa80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xac0, size=0x40, data=0x8096428 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xac0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xb00, size=0x40, data=0x8096468 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xb00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xb40, size=0x40, data=0x80964a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xb40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xb80, size=0x40, data=0x80964e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xb80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xbc0, size=0x40, data=0x8096528 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xbc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xc00, size=0x40, data=0x8096568 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xc00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xc40, size=0x40, data=0x80965a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xc40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xc80, size=0x40, data=0x80965e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xc80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xcc0, size=0x40, data=0x8096628 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xcc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xd00, size=0x40, data=0x8096668 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xd00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xd40, size=0x40, data=0x80966a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xd40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xd80, size=0x40, data=0x80966e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xd80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xdc0, size=0x40, data=0x8096728 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xdc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xe00, size=0x40, data=0x8096768 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xe00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xe40, size=0x40, data=0x80967a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xe40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xe80, size=0x40, data=0x80967e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xe80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xec0, size=0x40, data=0x8096828 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xec0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xf00, size=0x40, data=0x8096868 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xf00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xf40, size=0x40, data=0x80968a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xf40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xf80, size=0x40, data=0x80968e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xf80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xfc0, size=0x40, data=0x8096928 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xfc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1000, size=0x40, data=0x8096968 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1000, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1040, size=0x40, data=0x80969a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1040, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1080, size=0x40, data=0x80969e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1080, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x10c0, size=0x40, data=0x8096a28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x10c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1100, size=0x40, data=0x8096a68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1100, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1140, size=0x40, data=0x8096aa8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1140, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1180, size=0x40, data=0x8096ae8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1180, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x11c0, size=0x40, data=0x8096b28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x11c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1200, size=0x40, data=0x8096b68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1200, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1240, size=0x40, data=0x8096ba8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1240, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1280, size=0x40, data=0x8096be8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1280, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x12c0, size=0x40, data=0x8096c28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x12c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1300, size=0x40, data=0x8096c68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1300, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1340, size=0x40, data=0x8096ca8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1340, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1380, size=0x40, data=0x8096ce8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1380, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x13c0, size=0x40, data=0x8096d28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x13c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1400, size=0x40, data=0x8096d68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1400, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1440, size=0x40, data=0x8096da8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1440, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1480, size=0x40, data=0x8096de8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1480, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x14c0, size=0x40, data=0x8096e28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x14c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1500, size=0x40, data=0x8096e68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1500, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1540, size=0x40, data=0x8096ea8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1540, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1580, size=0x40, data=0x8096ee8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1580, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x15c0, size=0x40, data=0x8096f28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x15c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1600, size=0x40, data=0x8096f68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1600, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1640, size=0x40, data=0x8096fa8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1640, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1680, size=0x40, data=0x8096fe8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1680, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x16c0, size=0x40, data=0x8097028 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x16c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1700, size=0x40, data=0x8097068 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1700, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1740, size=0x40, data=0x80970a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1740, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1780, size=0x40, data=0x80970e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1780, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x17c0, size=0x40, data=0x8097128 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x17c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1800, size=0x40, data=0x8097168 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1800, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1840, size=0x40, data=0x80971a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1840, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1880, size=0x40, data=0x80971e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1880, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x18c0, size=0x40, data=0x8097228 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x18c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1900, size=0x40, data=0x8097268 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1900, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1940, size=0x40, data=0x80972a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1940, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1980, size=0x40, data=0x80972e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1980, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x19c0, size=0x40, data=0x8097328 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x19c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1a00, size=0x40, data=0x8097368 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1a00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1a40, size=0x40, data=0x80973a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1a40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1a80, size=0x40, data=0x80973e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1a80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1ac0, size=0x40, data=0x8097428 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1ac0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1b00, size=0x40, data=0x8097468 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1b00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1b40, size=0x40, data=0x80974a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1b40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1b80, size=0x40, data=0x80974e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1b80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1bc0, size=0x40, data=0x8097528 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1bc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1c00, size=0x40, data=0x8097568 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1c00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1c40, size=0x40, data=0x80975a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1c40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1c80, size=0x40, data=0x80975e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1c80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1cc0, size=0x40, data=0x8097628 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1cc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1d00, size=0x40, data=0x8097668 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1d00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1d40, size=0x40, data=0x80976a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1d40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1d80, size=0x40, data=0x80976e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1d80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1dc0, size=0x40, data=0x8097728 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1dc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1e00, size=0x40, data=0x8097768 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1e00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1e40, size=0x40, data=0x80977a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1e40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1e80, size=0x40, data=0x80977e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1e80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1ec0, size=0x40, data=0x8097828 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1ec0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1f00, size=0x40, data=0x8097868 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1f00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1f40, size=0x40, data=0x80978a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1f40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1f80, size=0x40, data=0x80978e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1f80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1fc0, size=0x40, data=0xbfffaa00 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1fc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_generic_req: command=0x69 [gt68xx] >> 69 01 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] << 00 69 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] gt68xx_device_generic_req: command=0x2e [gt68xx] >> 2e 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] << 00 2e 12 04 b3 07 05 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] get_id: vendor id=0x0412, product id=0x07B3, DID=0x04000005, FID=0x0000 [gt68xx] gt68xx_device_generic_req: command=0x3f [gt68xx] >> 3f 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] << 00 3f 3f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] sane_open: power control failure: check power plug! scanimage: open of device gt68xx:/dev/usb/scanner0 failed: Error during device I/O [gt68xx] sane_exit: start [gt68xx] gt68xx_device_free: enter: dev=0x80859e0 [gt68xx] gt68xx_device_close: enter: dev=0x80859e0 [gt68xx] gt68xx_device_close: leave: ok [gt68xx] gt68xx_device_free: freeing dev [gt68xx] gt68xx_device_free: leave: ok [gt68xx] sane_exit: exit --0-9979661-1086551363=:78634-- From henning@meier-geinitz.de Sun Jun 6 20:53:24 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 21:53:24 +0200 Subject: [sane-devel] sane :: plustek opticslim m12 In-Reply-To: <20040606194923.78653.qmail@web50405.mail.yahoo.com> References: <1086435353.11282.ezmlm@linuxhacker.org> <20040606194923.78653.qmail@web50405.mail.yahoo.com> Message-ID: <20040606195324.GR19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 12:49:23PM -0700, Ciprian Manea wrote: > ps. yes, OpticSlim M12 it's an AutoFeed scanner (small > format, marketted as a notebook scanner :) This is the first autofeed scanner that will (hopefully) be supported by the gt68xx backend so you'll need some more effort than for a flatbed scanner. > I tried to "fix" the source, Please send a patch of the changes you did so far, especially gt68xx_devices.c. > and make scanimage ignore this 'power' stuff, The next gt68xx version will have a flag to disable that test as it doesn't work with other Plustek scanners, either. > but then the "scanning" is verry > erratic. it will feed the page, too fast to do any > scanning I guess (indicator light will be solid green. > usually under Win the light is blinking during > operation/scanning); then it will properly eject the > page (that is, feeding it much faster to the 'exit' :) > > > Any advice on what should be done from this point? > thanks! Make a logfile of the windows scan process using the sniffusb program. Anaylze the log file and add the changes to the gt68xx backend. Check especially the "20 01" (setup scan) command and the move mohme commands. > [gt68xx] gt68xx_device_generic_req: command=0x3f > [gt68xx] >> 3f 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > [gt68xx] << 00 3f 3f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > [gt68xx] sane_open: power control failure: check power plug! Just disable this test. Bye, Henning From rene@rocklinux-consulting.de Sun Jun 6 21:43:20 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 22:43:20 +0200 (CEST) Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <40C374B7.6010806@cs.rug.nl> References: <40C35C8D.7040401@cs.rug.nl> <20040606.202422.805788455.rene@rocklinux-consulting.de> <40C374B7.6010806@cs.rug.nl> Message-ID: <20040606.224320.558917180.rene@rocklinux-consulting.de> Hi, On: Sun, 06 Jun 2004 21:47:03 +0200, Sietse Achterop wrote: > just tested kernel 2.6.3 and it has exactly the same problem:(. > = > > = > > Also, what USB host controler type fo you have? Ohci, uhci or ehci?= > > It can be obtained from /proc/bus/usb/devices - maybe just mail it = if > > you are unsure ... > > = > = > Uhci is used and a 440LX chipset with a Pentium II (333 MHz). > It is an Asus P2L-B motherboard. Ok - then it might be a generic UHCI problem. I only have OHCI hardware around. I try to find s.th. to test - maybe some colleagues box if I find a UHCI one ... Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From olaf@epkowa.co.jp Mon Jun 7 01:52:36 2004 From: olaf@epkowa.co.jp (Olaf Meeuwissen) Date: Mon, 07 Jun 2004 09:52:36 +0900 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <20040605180107.3dda0c3e.martin@mkcollins.org> (Martin Collins's message of "Sat, 5 Jun 2004 18:01:07 +0100") References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> <873c5c19rl.fsf@zen.epkowa.co.jp> <20040604011210.240e6d85.martin@mkcollins.org> <87smdcyxc3.fsf@zen.epkowa.co.jp> <20040605180107.3dda0c3e.martin@mkcollins.org> Message-ID: <87smd88a0b.fsf@zen.epkowa.co.jp> Martin Collins writes: > On Fri, 04 Jun 2004 09:35:08 +0900 > Olaf Meeuwissen wrote: > >> Alright, I'll send the tarball for gcc-3.2 (or later) in a separate >> mail. > > Thanks for that. However it wouldn't make. Some C++ library or header > mismatch. Could be my GTK is too new. "Image Scan! for Linux" still has to add GTK 2.x support :-( > In the process I discovered I had a tarball of 1.5.2 on one of my > machines. That did compile cleanly but didn't work in a similar way to > 1.8.1 but if 1.5.2 (a backend bugfix release) compiles cleanly, I doubt that is the cause. Looks more like some of the modifications to the build machinery fixed whatever makes the compile of 1.5.1 fail for you. > I will try to get 1.5.1 compiled and do some testing later this week. Rather than getting 1.5.1 to compile, I'd suggest you drop epkowa.c from 1.5.1 into the source tree of 1.5.2 if you really want to test with 1.5.1. All other changes are not related to the backend. HTH, -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From tmwg-sane@inxservices.com Mon Jun 7 07:42:08 2004 From: tmwg-sane@inxservices.com (George Garvey) Date: Sun, 6 Jun 2004 23:42:08 -0700 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606180354.GO19373@meier-geinitz.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> <20040606180354.GO19373@meier-geinitz.de> Message-ID: <20040607064208.GA4324@inxservices.com> On Sun, Jun 06, 2004 at 08:03:54PM +0200, Henning Meier-Geinitz wrote: > So looking at which kind of host controller the bug shows up and even > which mainboard is used may help to find out what's actually going on. Mine is an ASUS A7V333. This is proc/bus/usb/devices: 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.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.6-1.422 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=0000:00:11.3 C:* #Ifs= 1 Cfg#= 1 Atr=c0 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= 2 Ivl=255ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.6-1.422 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=0000:00:11.2 C:* #Ifs= 1 Cfg#= 1 Atr=c0 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= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 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=SCN2A9S0330LZ 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 From linux@defi.hu Mon Jun 7 12:01:45 2004 From: linux@defi.hu (Nyitrai Tamas) Date: Mon, 7 Jun 2004 13:01:45 +0200 (CEST) Subject: [sane-devel] scanimage: timeout Message-ID: Hello, I have got an Epson Perfection 1260 scanner. It always work right, but about a month ago it stopped working under Linux. I receive the following error messages: # scanimage -L usb 2-1: bulk timeout on ep2in usb 2-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 1 ret -110 usb 2-1: bulk timeout on ep2in usb 2-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 4 ret -110 device `v4l:/dev/video0' is a Noname BT878 video (Pinnacle PCTV Stud virtual device device `plustek:libusb:002:002' is a Epson Perfection 1260/Photo USB flatbed scanner usb 2-1: usbfs: interface 0 claimed while 'scanimage' sets config #1 If I try to scan an image with quiteinsane, the I get usb 2-1: usbfs: interface 0 claimed while 'quiteinsane' sets config #1 I am running linux 2.6.7-rc2 at the moment but the situation is the same under 2.4.25 (with scanner.o inserted). After receiving these error message I have tried this scanner with an other machine with Windows98 running on it and it worked! What could cause the promlem? I have Debian/unstable installed. libsane 1.0.14-2 quiteinsane 0.10-4 sane 1.0.12-2 sane-utils 1.0.14-2 Thanking you in advance, Tamas From henning@meier-geinitz.de Mon Jun 7 12:14:46 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 7 Jun 2004 13:14:46 +0200 Subject: [sane-devel] scanimage: timeout In-Reply-To: References: Message-ID: <20040607111446.GC3351@meier-geinitz.de> Hi, On Mon, Jun 07, 2004 at 01:01:45PM +0200, Nyitrai Tamas wrote: > I have got an Epson Perfection 1260 scanner. It always work right, > but about a month ago it stopped working under Linux. Edit /etc/sane.d/dll.conf (or /usr/local/etc/sane.d/dll.conf) and comment out "epson". See the postings in this mailing list and the bug tracking systems for the reason. Bye, Henning From linux@defi.hu Mon Jun 7 12:25:45 2004 From: linux@defi.hu (Nyitrai Tamas) Date: Mon, 7 Jun 2004 13:25:45 +0200 (CEST) Subject: [sane-devel] scanimage: timeout In-Reply-To: <20040607111446.GC3351@meier-geinitz.de> References: <20040607111446.GC3351@meier-geinitz.de> Message-ID: On Mon, 7 Jun 2004, Henning Meier-Geinitz wrote: > > I have got an Epson Perfection 1260 scanner. It always work right, > > but about a month ago it stopped working under Linux. > Edit /etc/sane.d/dll.conf (or /usr/local/etc/sane.d/dll.conf) and > comment out "epson". See the postings in this mailing list and the bug > tracking systems for the reason. Thank you. That helped. Regards, Tamas From baudelet@ensta.org Mon Jun 7 22:20:38 2004 From: baudelet@ensta.org (Christophe de Livois) Date: Mon, 7 Jun 2004 23:20:38 +0200 Subject: [sane-devel] niash:libusb:002:005 failed: Device busy Message-ID: <1086643238.40c4dc2663514@imp3-q.free.fr> Hi, My HP scanjet 3400C scanner works well with a 2.4.2X kernel but I can't h= ave it working on a 2.6.3 kernel (root or not, whatever the permisions of /proc/usb/002/005 are). Here are the messages that I get. Do you have any clues for me? chris@home:~$ scanimage scanimage: open of device niash:libusb:002:005 failed: Device busy chris@home:~$ scanimage -L device `niash:libusb:002:005' is a Hewlett-Packard ScanJet 3400C flatbed = scanner chris@home:~$ strace scanimage 2>&1| grep -A5 -B5 busy close(38) =3D 0 munmap(0x40789000, 4096) =3D 0 open("/proc/bus/usb/002/005", O_RDWR) =3D 38 ioctl(38, USBDEVFS_SETCONFIGURATION, 0xbfffe704) =3D -1 ETIMEDOUT (Connec= tion timed out) close(38) =3D 0 write(2, "scanimage: open of device niash:"..., 67scanimage: open of devi= ce niash:libusb:002:005 failed: Device busy ) =3D 67 munmap(0x401d5000, 1348000) =3D 0 munmap(0x4032d000, 503648) =3D 0 munmap(0x403af000, 75136) =3D 0 munmap(0x403a8000, 27524) =3D 0 chris@home:~$ lsmod | grep hcd ehci_hcd 22532 0 ohci_hcd 17412 0 usbcore 94044 5 ehci_hcd,hid,ohci_hcd Thanks a lot, Chris From Franz Bakan" Hi, On Sat, 5 Jun 2004 11:49:07 +0200, Henning Meier-Geinitz wrote: >I've added the script to the tools directory. If you want to call it >automatically from backend/Makefile please send a patch for the >install traget that only executes when os2 is used. I'll see what I can do. >Please check if the script still works. It still works, only a cosmetic issue: Linebreaks now are (hex) 0D 0D 0A instead of 0D 0A (after getting the .cmd via cvs) >By the way, your website says: >"Optionally you can remove support for scanners you don't need to make >compiling faster and libsane.dll smaller. >For this purpose you have to modify >sane-backends-1.0.14/backend/Makefile.in and remove the scanners you >don't need from the list which starts with: >PRELOADABLE_BACKENDS = >" > >That doesn't work anymore. Just run configure like this: >BACKENDS="net mustek whatever" ./configure > >Or modify backend/Makefile after it was generated by configure. > >Also "--enable-translations" has been the default setting for some >time now. thanks for the info, I'll correct this when I update the pages. Bye, Franz From us@bernafon.ch Tue Jun 8 08:04:51 2004 From: us@bernafon.ch (Ullrich Sigwanz) Date: Tue, 8 Jun 2004 09:04:51 +0200 Subject: [sane-devel] niash:libusb:002:005 failed: Device busy Message-ID: <2ED257AB11E3D84B8526737E255288EE14FB4F@brnnt12.bernafon.ch> Hi Chris, You must compile the kernel to solve the problem. The NIASH00019 chips return an old string-length-descriptor and the kernel code cannot handle this symptom any longer, alas. I posted several times to the guys who wrote the linux usb code, to revert a change they did when trading the 2.4 code into 2.6 They are successfully refusing. There is a statement in the kernel-sources in the file drivers/usb/core/messages.c (about line 1200) which reads len=tbuf[0]; when you change this to len=255; your 3400C will work again . but as I sayed, the kernel must be compiled. Perhaps you can also mail to linux-usb-devel? The more, the better. Good luck Ullrich From henning@meier-geinitz.de Tue Jun 8 09:34:27 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 10:34:27 +0200 Subject: [sane-devel] OS/2 specific patch for sane-backends/backend/dll.c In-Reply-To: References: <20040605094907.GC19373@meier-geinitz.de> Message-ID: <20040608083427.GF3351@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 12:24:51AM +0200, Franz Bakan wrote: > It still works, only a cosmetic issue: > > Linebreaks now are (hex) > 0D 0D 0A > instead of > 0D 0A > > (after getting the .cmd via cvs) Hehe, CVS is not intelligent enough, emacs is too intelligent :-) I used your file with 0d 0a and edited it so emacs thought "ha, that's for DOS, I'll keep 0d 0a". I checked it into CVS and it has "0d 0a" in cvs. cvs on your local system knows that all this crap is unix (0a only) and converts every 0a to a 0d 0a even if it already is a 0d 0a. It's fixed in CVS now (0a only). Bye, Henning From henning@meier-geinitz.de Tue Jun 8 09:52:34 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 10:52:34 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> Message-ID: <20040608085234.GG3351@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: > No seg fault on the saned end. Its happily running, waiting to finish > up. Xsane itself remains responsive. Ok. So you sent the logfile when both xsane and saned were still running? In this case the log file looks ok. Can you please retry and after the scan, close xsane? saned should also closes itsself. Thanks. > I can open menus, quit the app, > etc. Not knowing the xsane code, does it start a child process to > initiate scanning and maybe that process has crashed/hung? As far as I know it doesn't start a child process. However, it uses the gtk facilities to call the read function when data is available (something like select(), I don't remember the gtk function name. There has been trouble with that, but I think it looked differently (freezes of the scan or cancel process). > I'll look at the windows machine more. I can do a tcpdump capture of the > communication if that would be helpful. If there is an error that causes the scanner not to be detected anymore, I guess it must be visible in the saned or backend log. If that fails, we can look at tcp logs later. Bye, Henning From esoterican@freenet.de Tue Jun 8 11:05:06 2004 From: esoterican@freenet.de (esoterican@freenet.de) Date: Tue, 08 Jun 2004 12:05:06 +0200 Subject: [sane-devel] saned only run once Message-ID: hello list!

i'm using a microtek scanmaker 9600 xl. everything works fine... except one= feature:

when i want to use this scanner in the network and adjust everthing mention= ed in

http://www.penguin-breeder.org/sane/saned/

it runs when i start "saned -d" only once and the exited. i've tried the "= cover" method mentioned in the article, but it doesn't work.
the central error message is "[net] connect_dev: [0] failed to connect (Con= nection refused)".
where's my fault?
in addition some config files and debug outputs... hope it helps. i've fina= lly got no idea how to fix this problem, please help me.

thanks in advance
eric


SERVER SIDE - given command: /usr/sbin/saned.bin -d128
[saned] main: starting debug mode (level 128)
[saned] main: [1] socket () using IPv4
[saned] main: [1] bind () to port 6566
[saned] saned (AF-indep+IPv6) from sane-backends 1.0.14 ready
[saned] check_host: access by remote host: 10.1.1.127
[saned] check_host: local hostname: scanbox
[saned] check_host: access granted from IP address 10.1.1.127 (in subnet 10= .1.1.0/16)
[saned] init: access granted to saned-user@149.219.182.127
[saned] process_request: access to resource `microtek2' granted
[saned] process_request: sane_open returned: Success


CLIENT -> SERVER - given command scanimage -d net:10.1.1.155:microt= ek2:/dev/sg1 (saned -d not started)

[net] sane_init: SANE net backend version 1.0.12 (AF-indep+IPv6) from sane-= backends 1.0.14
[net] sane_init: Client has little endian byte order
[net] add_device: backend 10.1.1.155 added
[net] sane_init: done
[net] sane_open("10.1.1.155:microtek2:/dev/sg1")
[net] sane_open: host =3D 10.1.1.155, device =3D microtek2:/dev/sg1
[net] sane_open: device found in list
[net] sane_open: device not connected yet...
[net] connect_dev: trying to connect to 10.1.1.155
[net] connect_dev: [0] failed to connect (Connection refused)
[net] connect_dev: couldn't connect to host (see messages above)
[net] sane_open: could not connect to device
scanimage: open of device net:10.1.1.155:microtek2:/dev/sg1 failed: Error d= uring device I/O

CLIENT -> SERVER - given command scanimage -d net:149.219.181= .155:microtek2:/dev/sg1 Everything works fine
[net] connect_dev: trying to connect to 10.1.1.155
[net] connect_dev: [0] connection succeeded (IPv4)
[net] connect_dev: sanei_w_init
[net] connect_dev: net_init (user=3D(null), local version=3D1.0.3)
[net] connect_dev: freeing init reply (status=3DSuccess, remote version=3D1= .0.3)
[net] connect_dev: done
[net] sane_open: net_open
[net] sane_open: success
[net] sane_control_option: option 0, action 0
[net] sane_control_option: getting option descriptors
[net] fetch_options: 0x8052ae8
[net] fetch_options: get_option_descriptors
[net] fetch_options: creating 60 local option descriptors
[net] fetch_options: copying 60 option descriptors
[net] fetch_options: 60 options fetched
[net] sane_control_option: remote control option
[net] sane_control_option: done (Success)
[net] sane_control_option: option 0, action 0
[net] sane_control_option: remote control option
[net] sane_control_option: done (Success)
[net] sane_get_option_descriptor: option 0 ........
[net] sane_control_option: done (Success)
[net] sane_start ..................................................= ........... *snip*
=0A=0A=0A
--
=0A=0A From gerhard@gjaeger.de Tue Jun 8 11:15:54 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Tue, 8 Jun 2004 12:15:54 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( Message-ID: <200406081215.54463.gerhard@gjaeger.de> Hi, I'm currenlty trying to add more frontend configurable options to the Plustek backend and have some problems with xsane now. There's a value whose range is from -1..63. At the default state, when starting xsane, it is properly displayed: -1. When changing once to i.e. 6 and changing it back to -1, xsane stores it as 0 and also displays it after the next startup as 0.. Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, the contraint_type is SANE_CONTRAINT_RANGE... The configfile of xsane shows, that this value is stored as 0 and not as -1... Any ideas? Gerhard From henning@meier-geinitz.de Tue Jun 8 11:20:55 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 12:20:55 +0200 Subject: [sane-devel] saned only run once In-Reply-To: References: Message-ID: <20040608102055.GA3504@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 12:05:06PM +0200, esoterican@freenet.de wrote: > hello list!
>
Could you please use plain text (not HTML) when writing to mailing lists? Thanks. > i'm using a microtek scanmaker 9600 xl. everything works fine... except one feature:
>
> when i want to use this scanner in the network and adjust everthing mentioned in
>
> http://www.penguin-breeder.org/sane/saned/
>
> it runs when i start "saned -d" only once and the exited. That's not a bug. -d is the debug mode. In fact, saned also exits after each connection if it's not in debug mode but is restarted by (x)inetd automatically. > i've tried the "cover" method mentioned in the article, but it doesn't work.
By cover method you mean using xinetd or inetd? Which one did you use? > the central error message is "[net] connect_dev: [0] failed to connect (Connection refused)".
> where's my fault?
Connection refused means that saned isn't running on the server or (x)inetd isn't configured correctly and therefore doesn't listen to the sane port (6566). You can try that yourself: "telnet server-ip-address 6566". If you get "connection refused" it's the above mentioned problem. Double-check your (x)inetd configuration and look for error messages in syslog. The "connection refused" comes from the kernel, not from saned. Also check that there is no firewall or kernel filter involved, that blocks port 6566. Bye, Henning From henning@meier-geinitz.de Tue Jun 8 11:22:32 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 12:22:32 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( In-Reply-To: <200406081215.54463.gerhard@gjaeger.de> References: <200406081215.54463.gerhard@gjaeger.de> Message-ID: <20040608102232.GB3504@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 12:15:54PM +0200, Gerhard Jaeger wrote: > I'm currenlty trying to add more frontend configurable options to the Plustek > backend and have some problems with xsane now. > There's a value whose range is from -1..63. At the default state, when > starting xsane, it is properly displayed: -1. > When changing once to i.e. 6 and changing it back to -1, xsane stores > it as 0 and also displays it after the next startup as 0.. > Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, > the contraint_type is SANE_CONTRAINT_RANGE... > The configfile of xsane shows, that this value is stored as 0 and not as -1... How does the definition of the constraint look like? Bye, Henning From gerhard@gjaeger.de Tue Jun 8 12:16:28 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Tue, 8 Jun 2004 13:16:28 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( In-Reply-To: <20040608102232.GB3504@meier-geinitz.de> References: <200406081215.54463.gerhard@gjaeger.de> <20040608102232.GB3504@meier-geinitz.de> Message-ID: <200406081316.28349.gerhard@gjaeger.de> On Tuesday 08 June 2004 12:22, Henning Meier-Geinitz wrote: > Hi, > > On Tue, Jun 08, 2004 at 12:15:54PM +0200, Gerhard Jaeger wrote: > > I'm currenlty trying to add more frontend configurable options to the > > Plustek backend and have some problems with xsane now. > > There's a value whose range is from -1..63. At the default state, when > > starting xsane, it is properly displayed: -1. > > When changing once to i.e. 6 and changing it back to -1, xsane stores > > it as 0 and also displays it after the next startup as 0.. > > Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, > > the contraint_type is SANE_CONTRAINT_RANGE... > > The configfile of xsane shows, that this value is stored as 0 and not as > > -1... > > How does the definition of the constraint look like? static const SANE_RANGE gain_range = { -1, 63, 1 }; should be okay - shouldn't it? Okay, some more investigations on that show, that when reducing the range from -1 to -2 and I set -2 in the dialogue, I will be internally set to -1... I also checked this with the quiteinsane backend, which seems to have no problems on that, so I thinks it's a bug in xsane... Ciao, Gerhard From philipp.neubeck@epost.de Tue Jun 8 13:58:12 2004 From: philipp.neubeck@epost.de (philipp.neubeck@epost.de) Date: Tue, 8 Jun 2004 14:58:12 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606182552.GP19373@meier-geinitz.de> Message-ID: <20040608125812.GA3350@braveman.lan> Hi, perhaps this can help you, but i'm not sure if these errors are related: https://alioth.debian.org/tracker/index.php?func=detail&aid=300756&group_id=1308&atid=410366 bye Philipp Neubeck From Oliver.Rauch@Rauch-Domain.DE Tue Jun 8 14:44:52 2004 From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch) Date: 08 Jun 2004 15:44:52 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( In-Reply-To: <200406081215.54463.gerhard@gjaeger.de> References: <200406081215.54463.gerhard@gjaeger.de> Message-ID: <1086702292.2129.40.camel@Babylon7> Hello Gerhard. This is caused by a rounding in xsane-back-gtk.c line 2218 in function: static void xsane_back_gtk_value_update(...) case SANE_TYPE_INT: val = adj_data->value + 0.5; remove the "+ 0.5" and it should work. But I am not sure if this will cause other problems. I think there has been a reason for adding the "+ 0.5" Oliver Am Die, 2004-06-08 um 12.15 schrieb Gerhard Jaeger: > Hi, > > I'm currenlty trying to add more frontend configurable options to the Plustek > backend and have some problems with xsane now. > There's a value whose range is from -1..63. At the default state, when > starting xsane, it is properly displayed: -1. > When changing once to i.e. 6 and changing it back to -1, xsane stores > it as 0 and also displays it after the next startup as 0.. > Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, > the contraint_type is SANE_CONTRAINT_RANGE... > The configfile of xsane shows, that this value is stored as 0 and not as -1... > > Any ideas? > Gerhard > From kaplanam1@comcast.net Tue Jun 8 16:21:27 2004 From: kaplanam1@comcast.net (Allan Kaplan) Date: Tue, 08 Jun 2004 08:21:27 -0700 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? Message-ID: Greetings, Having recently purchased an NEC Petiscan unit, I've discovered the driver is not supported by MacOSX, and the Classic emulator won't hook up through the USB port. Please forgive my naivete, but is it possible to use SANE to fabricate one, and is there anyone out there who might be game to do it?? And if it is possible but no one's interested, any chance of getting some coaching? This is a fantastic little portable unit and it would be nice to be able to use it! Many thanks in advance, Allan From keith@claytons.org Tue Jun 8 16:31:51 2004 From: keith@claytons.org (Keith Clayton) Date: Tue, 08 Jun 2004 08:31:51 -0700 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040608085234.GG3351@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> Message-ID: <1086708706.641.4.camel@yoda> --=-1b4qrM9kqOVj64F7W2sL Content-Type: text/plain Content-Transfer-Encoding: 7bit On Tue, 2004-06-08 at 10:52 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: > > No seg fault on the saned end. Its happily running, waiting to finish > > up. Xsane itself remains responsive. > > Ok. So you sent the logfile when both xsane and saned were still > running? In this case the log file looks ok. Can you please retry and > after the scan, close xsane? saned should also closes itsself. Thanks. I would expect xsane to close the fd used to access the scanner though. Anyway, generated a log with a scan followed by closing xsane. saned exited as expected. As you'll see in the log, saned quits however, I never see any entry regarding the closing of the active fd. gzipped log is attached. thanks for all your work . . looks like you've been busy as of late 8^( Keith > > I can open menus, quit the app, > > etc. Not knowing the xsane code, does it start a child process to > > initiate scanning and maybe that process has crashed/hung? > > As far as I know it doesn't start a child process. However, it uses > the gtk facilities to call the read function when data is available > (something like select(), I don't remember the gtk function name. > There has been trouble with that, but I think it looked differently > (freezes of the scan or cancel process). > > > I'll look at the windows machine more. I can do a tcpdump capture of the > > communication if that would be helpful. > > If there is an error that causes the scanner not to be detected > anymore, I guess it must be visible in the saned or backend log. If > that fails, we can look at tcp logs later. > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request@lists.alioth.debian.org --=-1b4qrM9kqOVj64F7W2sL Content-Disposition: attachment; filename=remote_scan_quit.log.gz Content-Type: application/x-gzip; name=remote_scan_quit.log.gz Content-Transfer-Encoding: base64 H4sICEraxUAAA3JlbW90ZV9zY2FuX3F1aXQubG9nAO2dXW8bNxaG7/srCOxFHGzjDj/mK0AXm21T IOgiCdq9WRSFO5aoWKiscWdGSf3vlyOrtneO0ryHhBbMLK+CyA+PhhrykHzPIflT32zt8mdx3ay3 z0U/NN2w3r4TS3u5eyeu26UVZxv73m6EyvOnX/z0X/TQ3Y7s0Ip3dhA3bTeIVduJ3nbv1wsrfhnh J+LM/bFZLrv1dtVOLfyU/Sz6dvGrK372VOz60dyrt++Lj2OrZr2xy+fihbNo+979/3q9uRXbdhD9 7mZ8BrsUl7fipmuHdtFuppbk0S80xzA7jGR7M6JH/n653i5HI676+6oXeUGe22GbdT/YLTXxoVnv f+nxF1u026FrN+O/W7sY1u32Ht7/I85efPfMfZ29+ev46zwVq6693v/p2WXjKrNd9kKeZ+fSiM42 y9v70osru/j14qrth+eiWSzGH8z9Np29bgcr7j6WtTqXReVK66PFHsFi3e9/6FevL/755s3bf7z4 5nv3/879v7j/4KiNTbtoNnsT2+baPhe37bIBwLP+qTjbV/Xb1z8+jabY419k2dp++2QQV817617I tRVjUxdNf2f8aPn2xm7HN+/e9mrtGoBr0M/FV3ZYfDX+vT+3v+3W74+WXDTjd43l/7ywOHvduu6w uNr/XbhXtFx3rmG13e1T/JH23Pn40fGHeWBdI9+6Ar/85QlMPrKOF2KY/9eV3Xcrux160a7EcGUf faW4o8cGLRqx76NipO5eqhibQ/+lcJ6B8Y3NnUey/fh7v3rrfv/LrXMh4uybV9/+MPabZuzYzl9c NYNoOitubHe9HkZ/5VzIrrd3TYbxjT++eP3SeerR2fbne7/56CGud64ml1bY7WLT9u5L1ltx2Y3e Yhir1jjnJfqrdrdZcuq4+dDcut/M2e1v7GK9Wt8Zdr/uenRj1zf7b1+OXu36/GQv9o8u61zpsLga G+7BMy2a3j7r7bZ3vvW9PckD9K4TPlts1q5hnffttV22oz8/X627a9zIg9OVcKFHjvp4mYODf9c1 27FR7V2Za4eHJnHU0a+3a1LwT/84NtXvX77+95vXfz9mz426I33ROTdkx2d6PModPvw4/M69wcN/ hDyBTfVx7FBLVzv3W7W7bpy+3GxcF7K/PiE/DCk9fn6xd8udHXbddpyg/LjbmzxBNcwJbObJZrKZ bCabyaaXzeIzec5kM9lMNpPNNP9MNpPN1I+SzWQz2Uw2k81k83OxmdbayWaymWwmm8l/JpvJZmrz yWaymdp8splsJpvJZvKfyWaymdp8splsJpvzsFneY/stahdjFv7zw/6t/e4rKQu1N7tshgZ7gJE8 tuWKFHpIDt8XudvoNmbXH0uBX7aHh9s/KP34YH18iB/efnNfwXYrVsuTpAQU9BkeNu6N28VEJatK XN4Otj9sLHPQ1na03J6Wqqgh+uFbPnTrwbqCpT4UdJ/dbaGgpT50LcxO6lHUMp9DPfLCqDnUw2jw ySKvh87qYg71kJXSc6hHnmd4NVB4Wos8N2glIDTI55bS71WUCn4TEDqpRGmKWTjcwg3kc6iHqcF2 Enk9dGFm4XCVLmfhcKXMGB4Xpkk9ZAb7XIwNcrqqzEqveqhSSrQeGDsdAE2JPdldb6o866ErvB4Y O21XRTGLfq5rRjdHYfI26hJ+GQga1De0kcavFkZWcDUgdjoGliXDV8XbN+qcMZSj8LQWdQF3DAgN 87eVwWjib6tcwf4WYqf+VmuGn4q3TclczWK+rnLGdB2FSavKC7hRIWiYv81z7M2RNpXfu4ZPtymI nfrbQs1jzaFzTh9HafI+dJHB7wNiw8TcUnnO1UuFz9UhdromNwU2w4i8XeWylnOoh67lLIIEqjCM MRCmyehRGNjvYmzY3MporBWSehidw/WA2Gn/KHPO4ineuVXNCtqgNOkftYGnJRgbNi+R2nMdKDW+ DoTYabvKOFGCiNuV0qz5FUhTv2sYfhdhw9pVpX3fh2G8D4QlQU0zC+0t5yxpUZgE0Qw82YXQsDal Sr8x0BWEx0CMpXGbeYyBMuOMgSh9JE6Aj4EQG9au6tJzDKxLfAyE2Gm7UpITt4l3zl6DowGPJnPd Gh87MDZQY8/89FBtJKyHYizV2Gehh9ac9AUUpho7vBCE0FCN3VMNrfB1B8aS+chMkt4yTtJbvH1D 5ZxmBcJUJcEDNwgaqLEbvzal8xxuUxhLNHY9i7iN1gWjj8P0EY0d9lUYG6ixe8bKXUF4foixRGOf R6xcFZxgebz9Q+qKkw+D0qQeuoaX5Rgb5neL2i8G5QrCMSiMnfpdUzNiUPH2j6JiyAsoPK1FUcH5 SRAaqEsrX11aMXRphCW6dDGLNbkuK86aPNeeM8Tc4FNEiCX6OiceCNNH9HV4GYixofq6pxZa4fFA jCX6+jzigTlnOYvCVF+HJ7oQGqiveyokWuESCcamfREcms6rcjxHCWLD1k9Ge+YoGY3nKEHsdF5V 5rOYH6raMHwuTB/R1+EpIsaG6uue+oLB408YS/T1iqOTRNuuajDgyoKJvo4HZyE0UF/3jJSrCg+V YyzV11nzw1jblMw5sUCYJmNHjscCMTZQm/bM69E5nteDsUSb5qyf4m1XFZjIxoKntajwpDcIDfNV Nbg7lY7jJWMcR9ipr1KSMXBEPF+vQdUj8r7hKs95HZ4eV+MOF0EDNenKV5OuGJo0wk79bZ7NYl+E VqACxaOptsDQqyA2UJf23TcrGftmIZbo0vOIBUrFiwV67px1HYvRP06+d9b9VL7vQzHeB8ISPbdg DR7R+quMFQtEafI+shrv5xAbqOnmvn43Z/hdhCWarp5FnEBKxcqZBmmaM60YOdMIG5gzDSqnNGc6 x/sHxJKcaVBtjtxfqTpn5UyDNF0LFoycaYQNW9NKz5PSlMSPSsPYaawg4yQbx+uvlOLEPOLtH3XF 0aZBmGjTFa5NI2hQ3zBZ7RefdQXh+CzGkpzpah450yXHVYEwjRQwDrs5fc40ePoH1aU1Q5dGWKJL gyemRO6ntGbFAlGa5kxXjJxphA2L+Ree6ydXEM+ZhliSMw1mq8buq4qS4XNhmu7wqPB5FcQG6rrg iYNU1y0ZOTEIS3TdeZyvoln5lDBN9QU8nxJjA3VdzzNPNePMU4wlum41ixylR40RC0L5xTZdQTi2 ibGBum7meVrow4sE3gfCEl2Xs4CK2F9JcJc1jz4Sv8H3ZENs2PyqLvzqIesSrgfGTudXSs5ib7ky GeecMZQm8yu34IbnVxAbqOsaz3GwNvg4CLFE1zWzGAcNJ+yBwkTx0fDgAaFhbUr7nq+iGeerQOz0 XVTzOF9Fs3IqYfpILiLeN06fU2ky8BR9qodWcD0wdtquJOh9IvdVinNvEgrTiDm+MEfQQD0UzFyk fUPi8XKIJXooZ/0Ub5uqOEdIoDDJ08UPkIDQwDxd3zNoa8YZtBBL8nR5Z1NGO/7VnHtI4u0bkhXy 8DxRXuIHykNooJ7rebq/K4jHOyCW6Ll6FudZaVY+JUxTPRfPp8TYMH3EN59SMvIpMXaqj7DyKeP1 VSrn3LcA02QMzPH7FjA2zF+VYKYDeR9ljfcPiCW6ApgdEnm7yjnhDhSe1iKvYGEBQgNzdMFrXanP VXiMAGJJjm7BiBHE26ak5JwlD9M0Rxe/cxZjA7Vc5bkirzW+JIdYouVyDqeMd26lHpL+oHUgSNN1 YMVYByJsoJ4LnoBF9dwCjxFALNFzwVPDYvdXGec8eZgm/SOTeKwcYgP13MIz2pEVeLgDYomeq2Yx DmpOuAOFaaSckRBz8jHQ1L6xjowR60BYoudyzt+LdwyEb5Ll0eR9nPreWW5+q6cy/ejK5E+/D4id 6gs5Zz9avL7q0cXaUDK+Z9zGFcTvR4PYQD3U9z6ugnEfF8QSPXQe93GVnJAHCk9rUeKH9kBoWJvK PHPFdIbnimHsVOuR88gVk5qTKwbTZOzQeK4YxgZqob73cZWM+7ggduqrzDzu4yo413Gh8LQWBX4Y IoQGaqGefcMVZOwn8OgbbiExj1h5mXF8LkrTPi5xDRFiA7VQ37zvmpH3DbFEC53HXVyGsz0ehYnS gx80DaGBOqjnqd+uIGOvpse53wa9JSx2X5Wz7uJCaar14PXA2EAd1DNfzBVk7PP3yBdz06pZ7PPX ijUl8Rw5ND5wIGigDuq5/1cbfP8vxk7bVMlaO8XrqwwnXwym6fvQjLPLETZQBwV35VAd1MB6FcYS HRTcyRS5r1IleEJH5P1DGk6+GEyTehg8XwxjA/Vc5XsOrWKcQ4uwRM8tZhErLznXDaEw0XNzOMAM oYF6ru/Zexnj7D2IJXruPM7e0xXn7L14+wbntiHPu4bwm4ZOfs+QLsFsRapVFQw9GmGJHg1meMbe L1h5lDBNM0jwPEqMDWtX0vPcPVcQ16QhlmjS8zh3T0rOwXswTfNz8aP3MDasXVW1ryadMTRphCWa NOse43j9FSuPEqbpvArPo8TYQF3aV1vQDG0BYokuDe72i91fZYaRmwTTND/XwPMSjA3UpbWvLq0Z ujTCEl3azGIc1KzrhjxvZNb4hcwQGqhL+8ZsDCNmA7FEl5Yz0aU5sUCYpu+DEdOE2EBd2jOPUjLy KDGW6NLzyKNUrERKmKb5uXgqJcYG6rm++TAFIx8GYomey1lDxduuSs72eBQmem4JVwJCA/Vc3zP3 MsaZexBL9Nx5nLknNefQPZim+bn4sXsYG6iHet7z7Qri61mIJXooZ/0Ub7sqOOEOFCb5ucjF9of8 XAQN1EI9z9zTEj9zD2OnvirjnLkX8Xy95FxkDNO0jzP2C0FsoBbqe19rxbivFWKnvkpz7muN11eZ mjEEojBRemp44IDQQB3Ud6+pZuw1hViig3Luao3YV+Xg7moeTddOjL3YEBuog3qeLWYy/GwxjCU6 6DzOFtOcVDEUPtKqGI3q5Dqo7z2thnFPK8QSHZS1dorXVxnw1BoeTd8H44wbiA3UQcEdtlQHVXge JcQSHRTclRy5r1IlJ1cs3v4hDefgPZim+bn40XsYG+Z389oz3pHXeLwDYomeCz5Z5P2j5FwzhMJE z8XvaYXQQD3X99y9jHHuHsQSPXce5+65hfwszjoF70XhsLRn4B3j5Hq0p67uCjL0aA9d3aCz79j7 BSuPEqaPaLmMu9BOn0eJrnppPfAwIMYSTRpUCiL3U1JxzoyAado/8Bg5xgZq0qBKR99HydCkEZZo 0pwz9yL2V6w8Spg+EifHNZLT51FqNKJAdemMoUsjLNGlwShM7P4q45wbAdM0P5fRPyA2UJf2fB8m w98HxhJdGowaR+6vVM2JBcI0yXmr8X6OsUHtSsnSTyNxBWGNBGOnGmImZ6GRKJUxxkGYJu/j4XC1 T78PiA1rV1XpeR5+VcL7CTB2Om9/ODwRqUfumYmvcjwVH2OJNs2JB8brd6WpWdo0SFNtumZo0wgb qE1Xvtp0xdCmEXY6nrMOpozX75Y1R5sGYaLA1bg2jaCB2rRnPFBneDwQY4k2PY94oNSseCBK01zj Aq4HxgZqu9L3XjQFjx0YS7RdzsGU8Y6BWnLigdgyvh+aYdeLr8UvL7dL0a7Ear2xo4HFlV0++Ri/ aJf2eAnxoelFs1za5fjYl7vV6ui32o1dDBer5R5fbNre8c+e/U28fPPdp39oeOYHgMt2a7881Orr IxW6L3HTtQvb9xed/W1n+8F9RbMexsdatZ04fPhx+F07/AGJ6gQ282Tz/9Km+UyeM9lMNpPNZDPZ TDaTzWQz2Uw2/5c2i8/E5ufyeyabyWaymWwmm8lmspnmDMlmsplsfr429Qlsyuye+223dn+0v+8t ffEf20RCabE6AQA= --=-1b4qrM9kqOVj64F7W2sL-- From henning@meier-geinitz.de Tue Jun 8 16:31:27 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 17:31:27 +0200 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? In-Reply-To: References: Message-ID: <20040608153127.GA7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 08:21:27AM -0700, Allan Kaplan wrote: > Having recently purchased an NEC Petiscan unit, I've discovered the driver > is not supported by MacOSX, and the Classic emulator won't hook up through > the USB port. Please forgive my naivete, but is it possible to use SANE to > fabricate one, Uaually it's possible to write a backend for any scanner. > and is there anyone out there who might be game to do it?? I guess that would be you :-) > And if it is possible but no one's interested, any chance of getting some > coaching? Just ask this list, if you have specific questions. Some docu about backend writing is here: http://www.sane-project.org/contrib.html Could you please send us more information about this device so we can add it to our lists? E.g. if "NEC Petiscan" is the full name and the output of "sane-find-scanner -v -v" when the scanner is connceted to your computer? Bye, Henning From henning@meier-geinitz.de Tue Jun 8 16:40:42 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 17:40:42 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086708706.641.4.camel@yoda> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> Message-ID: <20040608154042.GB7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 08:31:51AM -0700, Keith Clayton wrote: > On Tue, 2004-06-08 at 10:52 +0200, Henning Meier-Geinitz wrote: > > Hi, > > > > On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: > > > No seg fault on the saned end. Its happily running, waiting to finish > > > up. Xsane itself remains responsive. > > > > Ok. So you sent the logfile when both xsane and saned were still > > running? In this case the log file looks ok. Can you please retry and > > after the scan, close xsane? saned should also closes itsself. Thanks. > > I would expect xsane to close the fd used to access the scanner though. sane_close() will be called when xsane is closed. Some backends close the device file (or use the equivalent call to libusb) after the scan has finished but not all. > Anyway, generated a log with a scan followed by closing xsane. saned > exited as expected. As you'll see in the log, saned quits however, I > never see any entry regarding the closing of the active fd. Please try again with SANE_DEBUG_PLUSTEK=255. saned doesn't print messages about closing but from your log I expect that the devices are actually closed. The plustek messages should show that. In that case we must have a closer look at the communication. > thanks for all your work . . looks like you've been busy as of late 8^( Fortunately I've two weeks of holidays and a lot of that time is used for SANE :-) Bye, Henning From keith@claytons.org Tue Jun 8 16:55:55 2004 From: keith@claytons.org (Keith Clayton) Date: Tue, 08 Jun 2004 08:55:55 -0700 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040608154042.GB7920@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> <20040608154042.GB7920@meier-geinitz.de> Message-ID: <1086710152.643.7.camel@yoda> Did use SANE_DEBUG_PLUSTEK=255 when starting saned. Cmd line was SANE_DEBUG_PLUSTEK=255 saned -d255 1>&2 2>remote_scan_quit.log So in that regard, was quite strange to not see any closing of the scanner's fd. Cheers, Keith PS: So your saying debugging mailing list issues is a holiday ?!? Heh, heh On Tue, 2004-06-08 at 17:40 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Tue, Jun 08, 2004 at 08:31:51AM -0700, Keith Clayton wrote: > > On Tue, 2004-06-08 at 10:52 +0200, Henning Meier-Geinitz wrote: > > > Hi, > > > > > > On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: > > > > No seg fault on the saned end. Its happily running, waiting to finish > > > > up. Xsane itself remains responsive. > > > > > > Ok. So you sent the logfile when both xsane and saned were still > > > running? In this case the log file looks ok. Can you please retry and > > > after the scan, close xsane? saned should also closes itsself. Thanks. > > > > I would expect xsane to close the fd used to access the scanner though. > > sane_close() will be called when xsane is closed. Some backends close > the device file (or use the equivalent call to libusb) after the scan > has finished but not all. > > > Anyway, generated a log with a scan followed by closing xsane. saned > > exited as expected. As you'll see in the log, saned quits however, I > > never see any entry regarding the closing of the active fd. > > Please try again with SANE_DEBUG_PLUSTEK=255. saned doesn't print > messages about closing but from your log I expect that the devices are > actually closed. The plustek messages should show that. In that case > we must have a closer look at the communication. > > > thanks for all your work . . looks like you've been busy as of late 8^( > > Fortunately I've two weeks of holidays and a lot of that time is used > for SANE :-) > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request@lists.alioth.debian.org From henning@meier-geinitz.de Tue Jun 8 17:01:40 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 18:01:40 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086710152.643.7.camel@yoda> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> <20040608154042.GB7920@meier-geinitz.de> <1086710152.643.7.camel@yoda> Message-ID: <20040608160140.GE7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 08:55:55AM -0700, Keith Clayton wrote: > Did use SANE_DEBUG_PLUSTEK=255 when starting saned. Cmd line was > > SANE_DEBUG_PLUSTEK=255 saned -d255 1>&2 2>remote_scan_quit.log > > > So in that regard, was quite strange to not see any closing of the > scanner's fd. Your first two logs contained the plustek messages. However, the log you have just sent didn't contain any plustek messages. So maybe the command line had a typo? Bye, Henning From insane@piments.com Tue Jun 8 18:42:04 2004 From: insane@piments.com (insane@piments.com) Date: Tue, 08 Jun 2004 19:42:04 +0200 Subject: [sane-devel] niash:libusb:002:005 failed: Device busy In-Reply-To: <2ED257AB11E3D84B8526737E255288EE14FB4F@brnnt12.bernafon.ch> References: <2ED257AB11E3D84B8526737E255288EE14FB4F@brnnt12.bernafon.ch> Message-ID: Nice post. Sadly this does not seem to help for all scanners. I did the change you suggested , recomp, reboot and my scanner locks up just the same. Shame it did not do it for canoscan. I would suggest you look into the code a bit more seriously before suggesting it as a fix to be integrated into the kernel. You cant just hack code like that without looking at the consenquences. At least not if you expect to have a stable kernel. I'd rather have a scanner the dont scan than an OS like win9x. Get the point? Maybe that is why devs at that have not done it yet. The evenual code fix will need to be more thorough. Regards. On Tue, 8 Jun 2004 09:04:51 +0200, Ullrich Sigwanz wrote: > Hi Chris, > > You must compile the kernel to solve the problem. > The NIASH00019 chips return an old string-length-descriptor and the > kernel > code cannot handle this > symptom any longer, alas. > > I posted several times to the guys who wrote the linux usb code, > to revert a change they did when trading the 2.4 code into 2.6 > They are successfully refusing. > > There is a statement in the kernel-sources in the file > drivers/usb/core/messages.c (about line 1200) > which reads > > len=tbuf[0]; > > when you change this to > > len=255; > > your 3400C will work again . > > but as I sayed, the kernel must be compiled. > > Perhaps you can also mail to linux-usb-devel? The more, the better. > > Good luck > > Ullrich > > -- Using M2, Opera's e-mail client: on Gentoo Linux From henning@meier-geinitz.de Tue Jun 8 20:34:00 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 21:34:00 +0200 Subject: [sane-devel] niash:libusb:002:005 failed: Device busy In-Reply-To: References: <2ED257AB11E3D84B8526737E255288EE14FB4F@brnnt12.bernafon.ch> Message-ID: <20040608193400.GG7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 07:42:04PM +0200, insane@piments.com wrote: > Nice post. > > Sadly this does not seem to help for all scanners. You can't fix a problem that doesn't exist. As most scanners don't return wrong lengths of string descriptors, that workaround is just not necessary for most scanners. > I did the change you suggested , recomp, reboot and my scanner locks up > just the same. He suggested that workaround for niash users. > Shame it did not do it for canoscan. I thought you got timeouts, not EBUSY? > I would suggest you look into the code a bit more seriously before > suggesting it as a fix to be integrated into the kernel. You cant just > hack code like that without looking at the consenquences. At least not if > you expect to have a stable kernel. That's true. As the kernel has conatined the code that is proposed here earlier, it doesn't seem to be that far off. Maybe a more intelligent way is needed, e.g. inspect the contents of tbuf[0] and if it's invalid, use 255. > Maybe that is why devs at that have not done it yet. The evenual code fix > will need to be more thorough. As far as I can see the proposed code does actually fix the problem for niash users. It may not be good enough for general use but that shouldn't stop niash users from trying it. Bye, Henning From erik@epo.dk Wed Jun 9 00:26:58 2004 From: erik@epo.dk (Erik P. Olsen) Date: Wed, 09 Jun 2004 01:26:58 +0200 Subject: [sane-devel] Howto update sane and xsane? Message-ID: <1086737218.8819.13.camel@epo.dk> I am running FC2 and want to upgrade xsane and sane-?ends to latest level, but being new to linux I am unsure of how I should do this. Since they exist as rpm installed packages should they then be removed from the system before installation or is it safe to let them stay and install the new levels on top of them? The latest levels do not yet come in rpm format so I assume that if I let them stay then the up2date process may later catch up if an even newer level comes out in rpm format - or is this a false assumption? -- Regards, Erik P. Olsen From kaplanam1@comcast.net Wed Jun 9 06:17:36 2004 From: kaplanam1@comcast.net (Allan Kaplan) Date: Tue, 08 Jun 2004 22:17:36 -0700 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? Message-ID: Subject: Re: [sane-devel] NEC Petiscan driver for MacOSX possible? Hi Henning, Thanks for your response. Yes, NEC Petiscan is the name of the scanner. As far as "sane-find-scanner" goes, am I to assume that I have to be running Linux, or can I use the Terminal program on the Mac and do this in Unix? And can I further assume that Mattias Ellert's MacOSX downloads will not be applicable in this case? Thanks, Allan > Hi, > > On Tue, Jun 08, 2004 at 08:21:27AM -0700, Allan Kaplan wrote: >> Having recently purchased an NEC Petiscan unit, I've discovered the driver >> is not supported by MacOSX, and the Classic emulator won't hook up through >> the USB port. Please forgive my naivete, but is it possible to use SANE to >> fabricate one, > > Uaually it's possible to write a backend for any scanner. > >> and is there anyone out there who might be game to do it?? > > I guess that would be you :-) > >> And if it is possible but no one's interested, any chance of getting some >> coaching? > > Just ask this list, if you have specific questions. Some docu about > backend writing is here: http://www.sane-project.org/contrib.html > > Could you please send us more information about this device so we can > add it to our lists? E.g. if "NEC Petiscan" is the full name and the > output of "sane-find-scanner -v -v" when the scanner is connceted to > your computer? > > Bye, > Henning From henning@meier-geinitz.de Wed Jun 9 07:42:08 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 08:42:08 +0200 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? In-Reply-To: References: Message-ID: <20040609064208.GJ7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 10:17:36PM -0700, Allan Kaplan wrote: > As far as "sane-find-scanner" goes, am I to assume that I have to be running > Linux, or can I use the Terminal program on the Mac and do this in Unix? MacOS X is ok. Any system that runs SANE should work. > And can I further assume that Mattias Ellert's MacOSX downloads will not be > applicable in this case? If they conatin sane-find-scanner, they should work. Bye, Henning From henning@meier-geinitz.de Wed Jun 9 08:02:33 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 09:02:33 +0200 Subject: [sane-devel] Howto update sane and xsane? In-Reply-To: <1086737218.8819.13.camel@epo.dk> References: <1086737218.8819.13.camel@epo.dk> Message-ID: <20040609070233.GK7920@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 01:26:58AM +0200, Erik P. Olsen wrote: > I am running FC2 and want to upgrade xsane and sane-?ends to latest > level, but being new to linux I am unsure of how I should do this. > > Since they exist as rpm installed packages should they then be removed > from the system before installation or is it safe to let them stay and > install the new levels on top of them? Maybe you can use the RPMs from http://rpmfind.net/linux/rpm2html/search.php?query=sane-backends ? Even if you can't, building your own RPM based on the 1.0.14 source RPM is probably the cleanest way. > The latest levels do not yet come in rpm format so I assume that if I > let them stay then the up2date process may later catch up if an even > newer level comes out in rpm format - or is this a false assumption? If you do not want or can't make an RPM yourself there are some other options: 1) Remove the existing SANE RPMs. You may get trouble trying this as other software may depend on them. You can try to force rpm to remove the packages that will break dependencies and you may get trouble later. 2) Overwrite the current installation. Linux distributions usually put their software into /usr, so "configure --prefix=/usr --sysconfdir=/etc" should work (check the syntax). This isn't a clean solution either and your sane installation may be destroyed when your distribution is updated. 3) Ignore the current installation and install SANE in /usr/local/. That's the default. It works but graphical frontends generally use the old installation in /usr, not the new one in /usr/local. /usr/local/bin/scanimage knows where to find the new libs, however. You can try some tricks to use the new libs, e.g. change the search order in /etc/ld.so.conf, use "LD_PRELOAD=/usr/local/lib/libcane.so xsane" or link /usr/lib/libsane.so to /usr/local/lib/libsane.so. Bye, Henning From Francois.Patte@math-info.univ-paris5.fr Wed Jun 9 09:22:48 2004 From: Francois.Patte@math-info.univ-paris5.fr (=?iso-8859-1?b?RnJhbudvaXM=?= Patte) Date: Wed, 9 Jun 2004 10:22:48 +0200 Subject: [sane-devel] How to configure sane, xsane, etc. In-Reply-To: <20040609070233.GK7920@meier-geinitz.de> References: <1086737218.8819.13.camel@epo.dk> <20040609070233.GK7920@meier-geinitz.de> Message-ID: <1086769368.40c6c8d8aaf7d@www.math-info.univ-paris5.fr> Bonjour, I am facing a big problem with xsane from fedora C1. (xsane-0.91-1): 1- I have a scanner Nikon LS-2000. The first person who ran xsane was not= root and it now impossible to change the owner and right of the device /dev/sg= 0. This device has been set with owner didier and group root with permission= s 600 and whatever root can do to change this is destroyed by the next use of x= sane: ownership, group and permission are reset as previously defined!!!! So no= body but didier can use xsane and the scanner! man sane-scsi : When using a SCSI scanner, ensure that the access permission for the generic SCSI device is 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 b= e set to allow group read and write access. For example, if the scann= er is at generic SCSI device /dev/sg0, then the following two commands = would set the permission correctly: $ chgrp scanner /dev/sg0 $ chmod 660 /dev/sg0 This is now impossible to do! Where are the configuration files responsib= le for this awful behavior? 2- Even for didier the use of xsane is not easy: every time he asks for x= sane he has to accept the license and to wait about 10/15 minutes for the researc= h of peripherics.... And, worse, he has to wait also if he wants to use gimp: = gimp hangs on xsane plug-ins.... I would like to understand how this can happen and how to corrct this win= dows like behavior: unix systems were done for many users, it is more and more difficult to use them like this. Thank you for attention. -- Fran=E7ois Patte Inde : Ecole fran=E7aise d'Extr=EAme-Orient Deccan College Pune 411006 T=E9l : (00 91) (0) 20 26 69 39 04 France : Universit=E9 Ren=E9 Descartes - Paris 5 UFR de math=E9matiques et informatique http://www.math-info.univ-paris5.fr/~patte From henning@meier-geinitz.de Wed Jun 9 10:49:22 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 11:49:22 +0200 Subject: [sane-devel] Re: How to configure sane, xsane, etc. Message-ID: <20040609094922.GN7920@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 10:08:32AM +0200, François Patte wrote: > I am facing a big problem with xsane from fedora C1. (xsane-0.91-1): > > 1- I have a scanner Nikon LS-2000. The first person who ran xsane was not root > and it now impossible to change the owner and right of the device /dev/sg0. > > This device has been set with owner didier and group root with permissions 600 > and whatever root can do to change this is destroyed by the next use of xsane: > ownership, group and permission are reset as previously defined!!!! So nobody > but didier can use xsane and the scanner! xsane doesn't change any access permissions. In fact it doesn't even know which device file to use. The sane libraries ("sane-backends") themselves also don't touch permissions. So your problem is most probably caused by some automatic procedure introduced by Fedora. I remember that there is some stuff to change permissions based on who logs into the computer locally. > man sane-scsi : > > When using a SCSI scanner, ensure that the access permission for the > generic SCSI device is 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 generic SCSI device /dev/sg0, then the following two commands would > set the permission correctly: > > $ chgrp scanner /dev/sg0 > $ chmod 660 /dev/sg0 > > This is now impossible to do! Where are the configuration files responsible for > this awful behavior? It works quite fine, I'm doing it on this system. Really looks like a Fedora problem. Better look at their docs or ask on their mailing lists for help. > 2- Even for didier the use of xsane is not easy: every time he asks for xsane he > has to accept the license xsane asks for accepting the liability exclusion only on the first start (and when xsane is updated to a newer version). So if that happens more than once, maybe the directoriy ~/.sane/xsane can't be written? > and to wait about 10/15 minutes for the research of > peripherics.... That shouldn't happen. Which version of sane do you use (scanimage --version)? The scan takes about 1 to5 seconds at least with newer versions of SANE. As a workaround, you can disable everything but "coolscan" in /etc/sane.d/dll.conf. > And, worse, he has to wait also if he wants to use gimp: gimp hangs > on xsane plug-ins.... If you don't need the xsane gimp plugin, remove the link to xsane. > I would like to understand how this can happen and how to corrct this windows > like behavior: unix systems were done for many users, it is more and more > difficult to use them like this. The behaviour you describe isn't the normal SANE behaviour. 1) is not cause by SANE and 2) is caused by the kernel trying to load drivers for hardware that doesn't exist. That shouldn't happen with current sane versions anymore. Bye, Henning From David@phenix.fr Wed Jun 9 12:54:57 2004 From: David@phenix.fr (David Neary) Date: Wed, 9 Jun 2004 13:54:57 +0200 Subject: [sane-devel] JSane Message-ID: This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C44E18.95B7D150 Content-Type: text/plain; charset="iso-8859-1" Hi all, I know that some people were asking about a Java SANE API recently. I did some work before 1.0.14 on getting it at least compiling with at least a Sun SDK, and have since been quite happily using these JNI bindings. There are still some bugs in here, notably for lineart mode, and I have been unashamedly messing about with stuff to make it work just for me, for one particular task, so it's probably not pretty. But perhaps people who need something now will be happy with it. This is simply a tar of the japi directory after I did a make clean. I also have a dllmain.c and a project file for making a sanej.dll for Windows, if anyone would like those. This is more or less untested, and ymmv. I also have a tarball of the javadocs, but I didn't do anything particular to generate them except run javadoc so there's no real point in sending those to the list. Cheers, Dave. -- David Neary Phenix Engineering 110 ave Jean Jaures, 69007 Lyon ------_=_NextPart_000_01C44E18.95B7D150 Content-Type: application/octet-stream; name="jsane.tar.bz2" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="jsane.tar.bz2" QlpoOTFBWSZTWU7/ZJ0An6p//v7/xMR///////////////9HAMEQJQEAYggBBBCgCOB9e8+98HQA eQA97h6e9y5z1ryy5W6Z9z5tmu3u3vh9e7vt1d9u++90Tt92BWVe3Pfd9tb33ve+76cACgF609z0 9o3vt9efX0VpY0k6bcY8GdvfJl9UBFD60kol7wPcD6b6IO7dtc129uu2uO+DefXzW3wkCVTc2Xaa Xn091at9uevfbvvV2+8+67329qHRfZdle73NzzquvO326c+2vfe1Te91p9N976nVesdXZYUFthtY Z9xnSqLTV5TuXe3fJpm2AA+vo1W917ryd7Hqtt4vX3O8KPVLXdkCvew66d2Gq22+tL31z3VvH0PX dPuNBO3pduXu97vvI+bs7Z8UiX326dOmqOm6Nj2Ap3fXRz20oOGh8262qtr0933TRoB3wdKt7un3 z19SAttvgHb6dZiJrJsyRi0q7773u968fdt7hJECABAmQamE0AmJkNE2kw1TwUn6nqPEUzyppo2U NB6jygAAD1PUCRE0EEEmjSNMT0JNNTTCnlGj1NGygPUep6gGmgAAAAGgAAASCRIhNFT9U09oxU9N qj8k2p5U/SZMmpkepskHlGmgepp6nqekPU9QAA0ANAA0CFIiQE0TCT00Mpk9Sj09J6jI0wTQ9ExT Yk9TEaBoDQ0aHqaABoAAESRBACT0NATVP0pnoTCAp6MptKab0k0abUbU0PU9T0jI09EekDTIAAAC JEgmgg00U0YT0EmSbRinmkMih+iTJ6n6p5Q0aADJoAaAZAAAPS+6T4kC6qP4Q/kZX9rIvjy/ufL7 s8vyPl+z/FTn9BCPZCOqBuQZSsFPr4Kv/6AAHngAJ/PHyfEpR84P0fePqrb9V6hV2T6p9V7YzDIz hpQZRSqUSMiuaJuCCDnu7bxrZjBugSAS7i022Kd7jte0Xr5BvIgXy90iXKfiMFAB0TYfiqQcNA0B B9lgMgWqBKGCWgmiWqFiBQaQaCaSVaWAgXy7QQ1qiFQlZGnMTDrXq0aQopImRmDSmcwaqCCCVdEm pSlQD8u98wWwUdAgKaET+OAAvT9X8tK1VPeRKiNXqzClBTlaIT72YxqmQmqWKWeY40mBPOGbsgpp miuHMaCdYOE6yqokmIIpIkYkomYIgJJAkKSaopCiSiKmhmCZaIikohgiZIimm+7lWLgQ0BSkxDKQ QytISNAwRCkKUl/q7eObh9lywSYRdwaRE0wglAkPU4jnafM5oZgAKfv5gQ9UFCmRAjmQRHXGBmYZ mOZZkUwVBVLJRKTUZBmsdTokIqCCCWgrv2hpmIYj4fsr9VfAsQfkoN9mJVwbYlKwZSqoZ1tGJme4 natEaUVxVKlY21Ip2mR6HgRx0pYmogiJgJWkJ0AcNuIJ1uGCMgxQlioorU5EyFULAwBLMTNVFEVJ ATRBJUkUDEzRQVKxERVTFFAUM0lEEE0FTBmYnE5FMxMDENDUwFARLJUIsNG8ShwJ3b52GWawKlhJ WpkogtziTGZhAyE04Y5EQk0UE0UsFDIpAfoQ4wozEg0IyqVrMRv9+ebx3kvtWT6rgJH9fhBhAhz/ g7++5HTljBXXgs/ZyTFg8iDpV5in+ji1b8GXgqY/0s+hhYDfj9vO5j/Nv/g/F6Jxzuu8yNPtSS0x orVVtmKRiY0Y0SQ6O0utdn5OXRR4zh+/iXBkw0YiF7bpcTW2ii3x5ysL06Ir7rCC7DOtsYEYVMsn U/nHUlDmzR2KUTGmx1DtrZxFRg7iqdm+jRgbiAxnRVOJlDOIU1VRMu6n/EhPs258HXoiMfdy3jm+ mzTjGNNxHIxFWMgnGYWsrc3B/M3MMQo5qG2GDG3fRzA7MNNVuWOVhzzm0t4ZvVObs2hQFFBTiXBk LqgdJl/s5PHUpmXBAD9W1C/loBOBFdRFDwe7QXSEjHQHCBCPea3hQBogqXN8ZwpyV7dGV8iTKufO 1ioVijjnKIvMp6XN+66VCaRznExZNZjDGqw1Bhc3Qlc7oS6miagDYmMQcDGUcCMHYnCTlC0cRyUz kYoxttspq3GquOyqXcE32zMNNVyadAazFxJaaMbDGLKw6YZrMIy1mZGpKNy9SgwBkxB5Xy7rlfrL YxrKiLzDlotLAgcR6LQiYgN65EbwA9IQ4DpD05zVaMCzMqSnCpaNyONsY++dl0heZowQ9qRDEYwC MXPLZXJ5DOt7zFOkc9eWZYVmDURoASkcr4ul/I3b4TjfSc+g/C/5nA5OhDZIGlT93yP8szP5ng6G 2P70nErb9hH2sanR63td5+nudjZDe5Pg+4pNsfefePP8KEG04ihKrYs6kw75Eqww7OM6e7dPWpEV kRFxkxtPCLLwUCDa9iQB+jq0G9uONJuHpwi5McceW2DQVOmwjISrNaNIEYRiGpHk3PerGxnGJ6w8 XoBjTY2iyhjwxJNiu8wFFmgzUre0hYY4G7T3+n2L+B3tA0zouIoTtO6OwuzDKnVmTkEZezOEPF3Z QUg/O8n3fvVetmdthwZLalWdDImKd6UOYiiW5S7I2R6bZovTdNV40Earo3XBstje3KbbVI5yETKG XKmiCYakevEq44RbQvq9/ntckhm22I7gxlHLywofXZgxYMjDme0Upy1xZsDx+ae/oNMGet3BipA5 I9frIGcIiksWZgk08gwMGCyUEjZSXs+34/OKlnJuolBpzvUoh0Eyzo7Bv6jyP2CN1rDY1Bxh6c/G am2XNkwAwBxtG0rIsQ4QhKOfrSN36A6xLiZifoEoSwJYT5QTqE8hLgmsSAmsSCUCbxMhOP3XMuJu EwE6hNwliWJ5Luc8c+YVkZVw4vvQ4w6ovqAJ7iB3pnFPBTpHroAr8ZscyBxCGIBuOZgxOszCo7Cs 85eRKG0kIwR/UjIcdjpYFqXtLmPfduPtj0+inxnzYU+fZRUtHNgGefxWRO4TN3JaaJ9DvC9iM/Kc s3DiMfOYsbyLyb915GOwmnzn8FzD4F65hLf0tvoY4jl/JLtnCnrhxM6D5x51a3kurv5lJgSXulKl kTkL6x5Zj39n7aHBMMNBWBBPumfeTueo9ZeRNHUrq2K9llZDyguxs/Z72dKpoZ4yOJnV4ilB8cx/ kiCWQ9aa+B6H4I6tUI/4vZPJTNN40Bo5jyqfAGivBenv3xgZarnfLOv6xABF7Q/Q6vJrxa10w6oa jnXLZg75ngfUXPSESkGD/1n7cuAoI6h4U+p+o+nn5Md31HzWbEPOu66Jtp4LihazLteE1haAQPRW Vlb1UQCLnbjncVB60GCAKfZ0yUAJ7IiqAU69GCnogQNQfRikaQIZSlSgVSkcgwxsRoEMZQMAJcgC TeAo5CoUqIEbcBA/sn8OCgummQaEHfKGdAgCRH2iQB2lBzAwHSA/FRX5/D+4fxK/QwRumCGMSTNA GCDgd8K/BoTCEoVggSEhU2gxgnIiJnAEq7QLr8DaBPDwkWT/PKJW0U/lS/l1ey14elgZBh0HSdtP hvnCz4he7vceP1IWR7QC0fUmCixBsB98ZZin5GK2QuvwBE32nruzD7Z0By3ojTac8VUZWm5022Y5 QM5afD8WzK/LInSVC2bgJter07Gmj2vmSw440xt0bcR+Rn33Kkc9T6Ld49jTHcNAZOLobN1WZuLK P5+FD7gi1oN+rYe3qT9H3tGSvL8R7wQ2K6BR5ulwtj3F++RLLqGG9tDuMkEyfZjNkvb7fwSYP0B7 wVtkHsSdxO4A5JNMLSJ2b8wWZRjGDoKoxsiI7xB4phNNAP2MDg3pKs+bnzyz1GvgNFrrCmTfEuYM BRl032uJEGCQYYUZ/jZKDl/J5WA4exD2gNRqBVUoRI2Yd2gCL5f3zDZHABmFAyAEIdtlAKQTQOwP 3xiOtMRjA2sCNC4u3LtX+4dfKVEzieZWZpmFWyDKcXEM+e7tgCQFCLIS4BcXb1afiAK/Vg26zuI8 Eae2vw6yDn7is3nP0+6x9R85XQcwEeMgDjJgQvbOryGsUg+3uhdDHFh+KPuSGPe/dvbqIqZqAWU2 OQ4UuDlQa3dQY6Be4MkdKkrRSUW6zWfpMCie8TE52Gv7TAOc+tybOJ8REyiB8z0up9g632t3W9Wr mQO8amf4LWa56AtAtsf1mL8qJD3Gj3/AzYB2x9hKT7BOSB5v8YOnzyFU/QgHYEqmXviVYzr1X9+r V5dpRUxMUEIP78D52lilj9MsSDx2V4n1gmGnlNbS4hcwDBYMUPMkwKtQHubUG0GP6Yb4Y4Q0ywcg u8i4N2HSOWkIlBgeMW85+w83oZv2HphrfzeXc7HxnHcuoYqYA+ZkphUHqY/vDA7LlV30dpoWwL2R oZHCvRSIL9y+Q75AD1DICmQ1uHWNL84CvhtZU9GZqWr6tT/EecXyfBX7oW5chkdLouYYil+1biaY TMzogoHAwevlyr1TadhSRZGSGi+7ikjczPcd/Ibn6cd79eF0MSU/pMi+ciQ32M8V8d0f27crsP0w /D7KruWWzpgEa+3CN22us5zngyH70eo8vBswDqxINgv2YdVYHnpfg8Kcc7aM+tHeIg24aq9oh11D MWQbJtnzUWBWD0Lmwh7530d8o6BjuuV9bW32cXz+WuhPSjbw4s2qL4nb7IClf8qZyDf5TeWNcCeN 3v22uWfZl2jDjggolHuFAgbznIHQWIkMkGbBfwxzwiNXEa7tLCyh4fLSIK6vkJVKSEQEAxx6DfOD BYt6hXGNn0FeJHzHnSS4gvf9TMdGS/j8Ij4TuLl+faC2ElYJcwiEWJ/TBPxRkfkkOwj3GNhee/OD YcwD4VtKbHiXvTZwI/MQiWnf6PTYBloDZYUBrncHG/V28BLm/9U8QeVkvmmgd8vcLpJ5r+uFjGuN hLG8SA48jEsA84nrhQK5mJ/cFTMSDrDtpISqWIIAJKOnWnmEYbcyOXH174/LbvdATMgkfPq413PT lc4JkUCui6zEBTnRKo89a08qFzCa4BtLjYAonMOCR8j1NKT6n465xiFrqshoAOfUCgpmQW19/DuD nVNghqdYJRBIdphLE3GpQlnmeQy/SAS8Bt0sHAJ4tBprDFY94L7UPb4g3ldKZlt1w1fQCuTyOBR0 I6ISB4g5bafDQPH1XBYa6wW+wEwKpwTPeeUFWCkTBc8H9Y6HQwnKq5PHZYGxC5r3rrTqxZROgxAD G3lbbQr11wL5+1XZJH1XaDxDFzN6ppMS2GK2GWiIiIj0ElpLHr92AXYR5mim22yAwAgXqKW1iKH5 8jE3BmbxKYTYBtL7QUqJVKQnTn2gsDkrsmK8RQcfBzUQiwkSJEJHB8XGw7fCqqq7wdmPL8oNFxFC tzqR0UIg3IEfZopCb9i6r9he9SqW8wZ+y7BsMeZppjGMYxg+jkdhkYGZ555108wTpfIY0li/QlfH XmV55MkGd9snGAXpEaD17EiPYZDXRY3tASFi4jmumv2QXtDy2cQZBNgr3BUsinI25vnAcvBVLviO YcFmCYsOdz2yyqTb5CLGNY0jwerXEFSovqRw476a5PdnC17BDCGGW8Ewg3RBTJMdD+0/znPb2jYU 6SGA62qBjIv5zmlKzQpUTmbTlHNeqYlpsK/ezhk+UgVgKAIMKy5DHiK1S4TRBGS49IKyatOvS+za +4F6dnUuSxAqgWxrBkatMZ4HIkpnRwTsKFc4mWhJ7ISbrUr08/FV7L5lY1uELldI5OWxcVqEaEFj VYe8YkkYsbVM7pRo9W2M5Ss1CkbTQImgvqrLgVfZSxwsS42vqUe42F86gVHYBcnoUoWIumZc+dsg oScKGVUu+mwDp0slzIY1Z9JXthdQwTLMUTfQmpqYjN2LmbB1zkaAo0oDMr7zn7tRZWcTtFWiV+sv vGqFcDk7NlH4GwxuLjFwxalyL7YM3KduEQpyhhGJCO582NP203BhNXBSC6NBnSD4ezUl47KvuiIG 0zuBXgp83cIZsXmWkFQQzVWsmIJo88jAE3Zqu40t2FNTaeww1StJgu8yUKZ0TAKwEwkagTiO0oIY oIYmCn2LVydUa594s0qgn3kmEimSKDIF+dbF2fZVcNnz3K0RoTBXRYfm6xqjUmjImIdipOm6EgWq 7CNN8coHOmh0XGvu79AyqqEZGJvMYgrfmaa6okiXM8KyYjy2m7KUpX1x5+VW8cpGSvt2jDtFa05U CtcdkojMsb+Fm+dIg7qZQNJO9TzboUiHeBYI7l5RGzEZdRAxZW955EBxxBDQmLc7dVq7urUZ6gvO 3OAx2NAaMx5jm2JMwzKB1zB5+dBzQ2TBJLBKEtGQ9IBwZR1P3Oh6BaBVue87z+q/aMlNFyCMmdGA /bhqJGZcLdQI9EicpITiGWa80r9cyGNSh60cIW84zRaQXWxaQXPtzYF8Ez5zg0HQkGG9YFfZs53v aIin7lK5+nAl9TATYLcIRXaU2JhEUZkY4hPaYOjWE5RhGNBHxAJdGoPjlwnsKK7MdjjAO1bA68fH kaYM68Lq+4BuwfTx554mVG0RoHHhliwcHSG458AdyMsLlvzBva1B5shJDO8Ynib+OZumyPK/Dj57 IY6rEHAfUpFDyySSQsAihcvXGdMp93u487voE56HM3A6dfDeTqmLP1kki+mdKRIupjIXA2MJGS6l 4VnQu75WQ5AXIC4vQ3D3GibTg6rvQ6lwIcnDpcpCccLxxYDgaWZdshHeJ2XqJjWWsLqGBRhz+4F1 83vrpVrrOmrzYDZwBQEtBHFxGo1Fs24PjlZDtg+XW0jbtUmAhBOoayxR1AIiwgPxZCUSruEC0u6T WX8ltYth0fQPQ6dMwefLxyR8mwlA5A5ibAdivFYANX+iUhSeB4HBsajcwZ7KvX0ET5ZkrQKgWTrW zvEMA4YldqZVKC+qI0C4BQxDiwarWVYMMiG84nTuEwQqOl6c6O42XnYkD5R+Mu6Kjuk2p19MTpFJ DI9e3bBvKa6wcwphFl1dHZ3OuXqrIK9pqjf2FiNUN6ZIoYrBlHu8ZJxcqwxBWAnMtAtJq6O3Qobm nKDQIWEMTXLb0P6Zgr9wKltIvj4clZR/FvqGGQZwpakIbQNxAqiwPnwrzhqfgw0g8QaBs5MjE8JA lUaarzZceDIjv1lhma1XkZaCO0vKrgFjBALsvN0SfIRj89vBychE7WxQRPrPbi5Uu1RKKnYJtSgR vMyBZWCsBcMcwWqYKwE4M9ewFXWVCOKVVHoy4xhMf3CFXltJmY7rkBNA6WBaJgNSSis9VTyAj2Op MQ9zxnCFMRyszJeiI9Yvb19M5C9w+GL+Sw1NLPQ+BfBPhcsJSQY6fBCjtl0NWUMIZEyWk2qLNdKT wyoQBc1WKhH/H08bYhI7QfNWZv4FECGl9IpCAwiPhOUxC5OUBs4GpxNBwGXXaGvGd86bqOy2dUOV rOAKQLWI6DfbFloJn2CiaIUCuXS+vZzZ42vrICMxhhGsGmHmEoGwlhNhxwseWOBvBglxICMAKCAn K2oonoCkFznBwCtQKS81PrEdznoCoiZQqi1wUFiyF76qxbgtPjsCg9+lc8MVnoC4BXEYBPdSI3MA rq5cZyI1WuKijFBQMkdxGMVEWdygWCTl1bgueAKzQm4K6qExuBniNR0IyvGMiO53EYNP6r+smEKy 5e1Atib84DkEyWNE/anPcZ56t6ix4afNrYCMymK5tlmVdW7cVkb+fCuGk60U3NmjUVgnmCxlZQsw MhGZdrZWXO971KA/QDQbvmqaDNzGmtGurvY9Jlb7twPjr2SmAY2rGi0xeC4LwYKubfTojbbdqUc4 /AHmvUdRQ20wGMcEA2gUMWHiamqfEZg697sDqZnUEndXdiu62w9wiyOPDgpaBa6Hl4mrwK2m4p1I MZqAVx9TZK8iOS25VlJf0tHpHilewLtAKwivCZzAvO+Cr3WW9POCmCiF5umVo266H5hjWbSagXJO w7d/RwDzB6xKgMgDYPUDuBsHioaO1T+h9nFfHzvZpNvsk1VVNMAIFBVSMQfWRUPlfsi0HdE85A+C PSdPy9dgouFQx/mlZz52HaQhIxVjAIQ/o/bXjoz8rvGj7frLnDDwtSI+ZbeRDt9qd9QYeGR73g4/ CudDN2FjNstrLmlI78bvrkf67RFqxrk2FuOLmbdnKGtB2VmzQf2vh+KNofFyQ92pO3Q/CHQxNtuf GZScoE7RjtdmPJ42hrKKrXZ6+y2vk/A7e89afeh/ybaK2jIVAQMX+WoDJPzSmVP8nuGJoGKszLnM IJwg5rWFQRRFJFrN6MsjCS3GyNbzZakhiD+mD/6ZbyhoNMD/EEuAQFP9YkApZSX+BxhxTGD9dn77 p+k6e4JWzvGmMVP5hgUMBe/owbDqfipB+0JFinkTmIASAfh7Hz6S1z8EXB2eFQJ8RRmvUV4IZ5+v R+KEcgD5iLtnBJe2H2fZe/CFwHr5LDUr01mRdMeZzWI5BT9uD5Z3A2cF9z90OK4rNGApEAN+gGR6 m3CV8LMRy7qLlFpo/C1lqPrtRB09kejjhxMtLSuKvWNyYlkY24QfW1RGNAM4hUc57XEs01exL3ta cEwDRpmMOgmuyiDaI/M6Cd3Tec0TQ42vjWoIpWsNWLsh3fQ7tAh/kCF4afgg/tBUJjSRFHVwT4Xc FOt0QGGjZ7mzCOyDg2+t0DIOELnMhiwFc4uxxCsLAiqRN0hgF7+QZpCKaSY2VSdQGPPgkdmNk51m uGF5bJ75K+LMokCpBvxFIg1ocr98UeU9kUQQcwQs77IhbYJGTO7bpWkhYKBdg5WyS/RhaHAN0yGI MTC9FGokWoFAohBeVcILFMwwzjoJwnGxKjvkJJi83yK3ccl7l4tcrpe6ArUlpUQ4ti9nPcYe8gic K+2c1WxdmEGmWkutmYZWwGtXsXGu4J7rxg38rzxEf3oKwt3O6mw7pfvWNgU0u3MHq3wMCrPLj0m0 E6iYiGIb9yjuGKKCw9DCNUyas45I+qV4JiRpehChtB0vvOd0L1yiyJszi+wJ8LB7mtW3jiw+kHdo k6SzEQVyjuxHwI2jO4OkwxHpyuap4ND7GNX6xyXy0elL1jCRRKkKD0/GHxeqxu49b9xhyNcCyaqN Ikgo0ZxivgcIogslPhRPNoOiMh20Ul9IWJlz3Lf6+tw3+uF09uPXTqHkscn6dSc36jV3bZxZ5SmD WYfEFl9xGCsWIuRfzL9ROzMqhBh8LoYRgF+o27P5MIwg0VAcWor8UuEjmYk9hVE5nGKHNBpQjEzX KS+jIOrZOMgbYnOT+veOuAWElX6JYsb0bIPZ/dX5KaDgo+78oLBWL8joX9pVrf+zxdoP87M50d4/ Dum3vtx8u1Zbta0RoydV3+TywB7+01hNeukLsn3BOp4L/UwAfY4qfGXd48y0qmx1ZOvMMjm5hr0u ioTybn5dG8kVtZPElPCHbOy8P6t5/BxUnBUd5Ipne5B2k9DzbbWtaxjs72yyEnGVI1nMcPD031pH MuKQkbIT690CiNHEMyLlt3G6AgiU/nnxFEOthSb7L3Wu537j7kyhJvDwBTrXQxw/HePl7IL+M0rL puW+9mujPPynWWep05LW9xEnH8jVhdl0071I/xMvJ2jyV42+mZt4xt9O2wxW6+68+D22RCkSzlay URmC25oSjGktVCxB4bfathSXdue2st1lL5HXL7vGVsxXGqCqhtZu13Ilsqtrld7PN1Ds5tL7rOeN s6twp3deriDK+bEl+rrLbwQc3t0xFuPGMPNH0+vCuuV2cSrXjpfTlzxVoR6p44JpF+LVwnWThHna 4LbLCNb5GN9l1Pyb44PGWhyRtBM9nOSqIEscsoNkPcVPVJy23rst6Hi8LDwfq1R6uh2wrxwck3S5 jHer3qZ9+rVFox5fn9eL5vM7cV92tmXuY3NusEH05MMG+jI+36u7st3VsycHWn14/Az0PZ1eL86W PRbvf08Boc7n29WJ+shutma3pbn7KXyHldGB34+7B7WtDBi5mZ3d9G2cr+EZpas4ODyqecX5/458 GvgvssOhkzPaAR640Nn1WlHQjJPzAhSKeY/WMQDcwm0DZrAoaUJIgBqSkCIIGZlCkEhIX9yEwYWq Bf2YCkOJSYpTIQ6QCPzQr9PoB+oa6EdyikAeh2YhwR+sMxH88l7Iy/oEP7gQPEG6ogNEP4ZyU4f9 OIn8X8fQ0PMGyKGiBnCCB+v3fF6YJ88J9VL9ZkB1Ohh9Og0NxfXq5cjF8rRUDy85AVbocTDD4wFm LvejU0ca/Y3d9tj4xVdXwHoH+G1W4COtrrpY+iRL5MFmTlkVAiDDI7GztdJmEXxnLJ5+sHxcdtK7 vTbhnVO59npfv+kMIFrZMOkM2Py6pRPgK31gnHo44KrNqvgMdNoKcOShjI1NBsmeiD49sbvlBOfL 79X57eFphaSEUYyqsrKlkS3vZPGubKyL1Vts0OYvN7ZBMREQQypx3P/XTQ79bqfGNsAMV+gIb5yE zBqcodQEB5HHrKgoVZliKzyQZBIWhZHctyliCw6QVHzlUnEVwQ7KD4ADwgQ5JvFOpL2VZnyMzGW9 tZTQOsDWpi6yLSNAnT2DZHlc06TTjitPMYufSZpyeU5MjbLxHpv882L22BMF4+yID1C2OD0hwQNK Zc9NbTLeP2m7E1g9hidgaEdk/cD4hWEVCo9L9R+7PfL1Ffq5PUDZ/aM1FK3C6TtKqNQnBcMBXSwT 88Db4OehKPZ8OK9J5zPPq0OpNZEezCgeVeVc93s150jIhitEKA+ELspWiV6vazW4x/VPMq0+33/G bKiCn2as2rPdy+7+G3TF6+BFZsJvc51Pf5vPa/Y3wMGcO/qglNtnTOQ26HbF1tl3LlJaJJLZ63zm sYjaYImy4xKZrg2ny1OTA6DM8o8OKLHOj+dxvcteF0j7J8VqOnHhxxDKfvHmEsTQToJBOAlichNu 32fG4fzTyGVcN+T2GkR1tjeDBtGVRTSBrjU7PLdKMaE9/c4RnbnD31QXtDvtL7QbuK7CGkeosaPU M0SUW9E1LEnAhUrbXXcpcdZ5rt3jqawJc5ztKE3Pp+DGm/zx80hEs0gbTueeqz67xFdfCFmcR7dH gzy8/JhOuVA8L+7RUb19FpGqgwb71m9Ba016yb8Unu/mXB+YFTIldAvB4eDmvC4eW9qqFTwm0vNC ptTeDZXzDn5gaH6yM29AH0e+vskTPxCHnMBRUWfu0THvBzevu5vVhyQyyZzMCmZb22MEzMOHTRke fudwVoeD8IRmFnNfUsCM5W4YADKanW6Ja4NXoeFnjCYz2xeI1UuH6x8Rl5dnO2w3j8IJt+Y34tvz OiiTkwY8HJji3QwacG/MaHvyMYdCXRIM+JzS8aChEE+fVFJd7ne0fq+q+2sKEj7h0OCJeDQ0snUf RziNslfOOFHEPoGGsyy0I4j0vO1qI9uirZDsIpmS40G/nVLDjM8LbkS5UIXdbMacNDhtpt8GUnuO bzg4hqmJxTJxeWAFne6HBps53M32utI0/iBjb6bSLN2YWylTIxhpAC7/QZSx8fubLUQTwiozrpS3 ealbC+b3eeDAENvAs6yZHq1GiYnDhENR2Q3rpMDJ3O1oYDmnOPG6cJ0J5UjhNg130ZlvJXqd5eqB tA6VeufQRPEEASoSSRKJSUAFSwA1SBCSlMqeifuSggeCfc9X6QAH3BcrogSv2Te4IiIP17DJxIgV gmiRFhcmkfe/ZfT2PgNJbRAGkSxS5iGQQRFCAUoiJdJjPrMkkbbp7rqfWxzi1uyO2btpjW3XcLmS uGSZaUjJkHMZqZrJGY5TVJJWi6Bx5QcVTTySSBJI8sBp+81BjGV5S0Ud1aq1jjdLVEN5I38ZIOsO Ul5OAbk4cIMzE/N14tvEyC6Y5Jqitfpe29PnnMzE/XPo+e1/n++XanzPV+YewXlEgfM0qngDC0f4 NPd8/8R6jofjyM2YEu+4sXfHyzbnJjHWfGdZG7RCdxoFBeQFIoxZSSyVpIyisg9CqBaCXjIjntc3 m5xEKODDZwJzrYxOJZE4vX+Dz96iH5zM23v1Fp+xgzLRIS2DIJKopIs3WVvBx4wsi6F6JAOGiiHv 27scclEPhUQs/s/2/f+VYkihd9ndGP6PY/P+uP8/1fyf0YfU+T/brQLeC5dQcjdwXXdYqeGVmQNZ QMxqBIOZEU71QxIFCHIvmZ53z78jvkJ3IwDun47FAGIPznEgSTfSHyVURfJetkrDUgWaEfJE1a9c omloKyQoFfxAMWu72R+vTiA4ZjoiO4L0wr1skv1M0paTugVbh5u/hinfV9EVEiDbaFuwlrsxibEO 3bs9cFB7D64BSt8yS/yM+Y8sX6A1m+VK7go8eOaP6d8KVPosFgth+JLPuBqTHgTeGXyTMLVD+n6w x3WEiqrZsNRJYlYJ62QotQ+nIc5I02RBPq+KyDaim16fWyNYtmMOiqjcm27kTszMMJhmhCskrc1R kx5RDbPVIRvrwc6O24auhHhFjfJPIk7kxzfZcKzSiF1gN+NBqYkw6Z0yEg64NE6jFqtLpwziUQeE I3ZxZAtklgPsHO207FkXZxPlPXffhAnZ7RgRAgVgWicPEWQXhlPY4KvxGpg0frCFMgsm37zNq8Hu AtgzBFeIgVoCuep5EHvakabT9OPqj6nQ+ATPyJBoCoCh8f4+f7fsXdj7UpffBz088w89X3zq9B+j 5kfevoTr5mGZJsrLDAt8a81anZrErZ2/KAQAKj+L5ByAx6gNEEEjNpuUOFn8a1gAhbhukX48AtiG Tpg+hUDBXL4gTL+WrD5F4IHqivYEK21fy+P05yv1/yfvfLN7nfH5l79UbXx0dQoYDpRn2OSMRos9 pqvzJ8q5fXxpObKyY535d2JrYgzbbapBJLD5R1jViP7h6vc8kfNwfN309UI1535sqMkG9uV81GM2 zYrZamvtdBBqmpki3+mg6fxVlJA0fn+T14uBJuYmyJ2b+HG5uicImU7YpJuqXYMlJCV+xZ2x3891 h6ovbnWcE/e1r7YcYnCqkUrBWsQ2gbR5TbfXl93DZFi3J0tjJLK3Yz7ODEZBuceG7hAlWPUDvrWt FKatlCcSBW/PxuYMXGUQD0eNYRLlV5rU1LRDwSJnB4sR2zL111ER2xQ7YeMA4QPwg++g/T0ugb6c LKi14MjdJ0UCLDskbWBH2bCD66qUbsD1DOEzX0nKyZ2j55wJ95k849dVXg1MIaPfToienOtkGokj OqkqDqM63wDuqi4wY0mvIgA8mjQOLQjXyhHDKXhCyxYnrIsXjWYIGSN1BZ6YBkaD7R6Pn0WLNe5i UGDqY7nDhpnR+d5IfGDLYRZ6QYIygep5Uqqdok2szYD8TzoXE6nvGreUT6InpJi4zzU/L2fGbq4L 4yC7DSGTucfNE9LOGRUj5BYtRAdPwgrgoW+Xua4EZD8rNwRBluwu5jPZ4Kqj/n+QvjA4MhmTEUwD 9R/H/i9fWb3ejodET6Z++cPMBWwp/iJTzARAwqYQIERpCQH/b3feyiYpIFQhQ1CJgIowEEBtQkUJ +cY6gkgiUg000qUpwQmQ0gjpMYoKZimLFSCUdkiFpeLBi7DsJoLNht+2es8DsOg+HKHzD5Q26lB9 XmS/tkEgwXsZUPiXvL5vfksMm1wyf0N9UIwPnJwpTz3MMfyHX9TzBQSEyghrVDVFQIQDqr4MB1IZ sIe3BRY7fSd49mtv4uRzf8vc4R/GqfXp9DuheQXhQZg/JD+nI/veAP23nYP5rIgiczwBx2jC/m7y X9M4DH2BkfoDUEnD9SV4luQK0D++ngK/aAYJxpfSjMAXfK6Q4UDpGceNQEsh7AYDkDsWikwQy0gx OBl+UGgbgeUZSceI2xVOt1UOO4zDgmZwB/bZ6xvQfp2VEHxv83ANNr6IGGY0MEMSw6F7G+5fQmD7 4EIeBhzA7QXXithy7v08URVwwdKtSRzQU/mnq3CEfrWZ3w2hKTDXUBfSH8Y0ZeuMIQkmO3F6u1x3 vhpRj+oun5s8JXphFccbcZCRsL2izVRKoo721lccycDlBeniEgUlLtQqAHXqQ84aQP0Z+w8Tc6tO YZpniDcPF0Li4p8K0bC+sVKlyHPI4hREERAywWXGD4s34SaRaCoUs1DbEBcyAiQ5oJd0OZzmZSA3 dEPZb79R0FWnjG2oaLbFWN75AF1mYuGjATPOaKehCFpyaeEN5FxA3TYiyRSkQ0l7gGE0yqhSp6VK AmSiYAFd405DA/HKGdDoQ8INd4LbbCQRgU86ceQd3R0hHqv1D+kaPWuRPjGwZubnTQ9K3qwX0hG0 KwctjAOKHCSfXs5dWt4lhygSNotwHJ1EzKwT9fWRJEu3U2834TMgZkK+EiQjegRQmOb90/vfQ9B8 B8nwv6ew3W6ceCFHUiwwug1E6YmCaaA8Yhs3DRh6lNrjwb7oVLlFDhhCePwzM9neL2MDGcgiiUEe ug9gViy6ilbyBpi9nmtmGrosHbiybG7mQVfa1OkA7QN/WbmBybgUNFt29TOIPL6HPN7IDGRXgAaP R3sd0QbMk5GrsJKEMgE2TuEnQOOGiA8AfSvx/bC9Vf1ZdAY7K1FT5g867hmAdcuxdZU7vdDtSdOp HkAvGRVePJS3nQjD27MbB3ni84fIeLgMYzjtBojd+E9J8/4QzU4mOWcA9aXzigoKCho4LyetxzJA H3IKnksO2FsYmuL+yF5Uv4SJ2BHoyoc4p6UgD1kb9BhYi6SUiEB6/rN1eIMPjZGEV8jzX9rcCtgB 3LAKIQhgg4GMIFxFNhF4AhEQqPp2bfNfBONChqO3WkY8gbdRB7xg9galyB8lgaDrhHWU5WUikG0N u22HMfjU+oNZxyfrgnyiOZYedxbvEwxOswL+pF4aQD10Iet4QBWKSANfkXYHFjtDYGnIzM4w53sx SEHUDMXHvDtEw9JCEnPN+o+dzZ6isR90wxNEm88YHUhqENT88ZHU1/jDSalkQmpwXU/dXsU4OOwd om1CAHA3g+YGi4PUroS6c5HNV+zuVudLe1oIDsZxvHDq7kIqzpp2zhMeJyPDxFRWy9wOlqcDWUMa uVftLqAMGAxmLjqn09GquoPSt0dnxtOpgQN1dqZW1SRYERwwXXRWRUKhIAfgV0DAXE1pgF0n0vOn Rhf2793waTLr5nWaWk0NZWB4RSAgwA8KCVWEIGjAfwdtXDKKj+7QUmffTvLjQeL8vsp+BfUO3Xdw HV9Zo0Pkk9uiyh8lwaC3jhew3fJB9PuB3gTJw5Ox9vpQyXEcbAGlHg4Ezz2VKaYDzGqPeQ1B2dzU AOA86MUUECKUBfUPeXJIQYbEDm+t4z7i+ST0er4Sn6W4FYxlA2MB64PrkfM3Y8wCHUaEkiAheft0 dr8g6qx2DlGMTTdEqwMVvvxcbyOQZgYd35jw4B4mW7maDQ2Bx5DhxdlBOnZuByFwHvE9EDwdb5wz 0YaAbKOlzG6ubmMYxjXJhMcAYac/Jz5m3lLtEZnVoRoknp/fbd7+mmwuPDULba0MY64XSAzH312v X/x8p3F4jKonELCw8RIGYESIkTEKwZ9UG0gmgxcST56BxAB7FbQwH3F5p8RhDfZuLBYAaVuJqDgC 2gbQPpBXsGrByCLEPwdpPEIczmzhRXuU76V5TMALFHDrLvX0Qn3D0ngB9fKazx5gB0R8A9r9C7ZI HD8I/fB1LgSbvWSQgXCxED+JcQsh3ABk++AzwczxNkr5AbC22gIUSfhTZfWi41cze5A8cr3VA+Px 96OQIoJoJ7/mog8QHjXgPTbAa8PhJxvQVGWRi6KWOFCvkWlCgA1A+xgeBgMHACirmqjpPbYpaQlB pDd6EB/Kt/jdePwF4Rh31evToYgvh7ofo70hxLBLEJWgzYimRrMG9TQ9YBX1g+IHNg6FNpmDrDxG J1dj8PX83jnckG5AvV6IX5ZHtzOOhg4xpjAgrzJRsblfmSgJGZBaPnNpNIZHMoc1sLISABZM+g/1 x3eZeaAwGe+NmzQuJdC4WC5D4gD2L6QSia0dK6eUF4yiLy4StRXrWXOrkUGKkpKIWCh1+HSYnZi5 hHnM+YHYupd6Og7gdwO8ExQKBrpU6pu17W4+XwLx+YZhhiUNotHxafX1B6j46MHlI0Yhd1F+QHvo S0hlprbh0Y63ppTsD6Do2GurYPLc6FQF5REbYAHpJiOvyqQ5RAenRpbb7oM7fIBnHw5jA7FO5p7F jwB7AJzvnGDGmlDWGjPUNsgBqRGh0AMwDA2OG+1OMUS38Y4xDHZBeaGo8abHXUUIIGRaB87BJTUC MWCzQZZGYbDLWTIUwkrxhspIcYaD23D5SESDgI19Lgw5tIWBphBokGHy9ZZRk0e94gDDOZx6QdA3 mBI+atdVHagXnqY1Y/SyiZYxtIafwEj8rBQaaU8A+gdCMYoPanfFFwg8DwXXrAfppPcD7gKhCrLQ mwGNHlvipgIhkMcQIjMYJ8svBbQ0pyHchxlbOOuV/wdQft+lfSmb26h9G8yrhqLl4q4jRt4CyKfn xbemY2NN1hp4PN8d9d8+kQ9QPU9LDwaLsT1gFgaaaTTQycRnrCwSwEKIvwey925xdKuSGGToBpTI H4jNSzcHJ9Z6ldALs2cKpgPYD6Pd83tqqorjwI8kZB0igg2IFkImDzyRXoj2j9HdbuE/Ely73+gk jmnwxAkDaAMooBnpQ3W3S+20oeIK+sU6Xl1g+7AenNOmEicu80dwNNwdPcqlgfwofCQO9wN7xBzO c/CGKhv2ofJ4F49K1LzZSO5IJKhOCgoEMLmC8Ww0X+Q+E8UgUla4O9OwrEh/Wjzuqty+6tmFNsCS Xuhecwc3ET7zQB3v1mBCd9HUD3A4lg0mJgGCjhcB1fo3rfuHh6fxt+2i2Pto7sj9BHEf0RMBckog BD9Jltzn5R8z56w6trBzrccM+o7QNheAGNkwHfGjm4YYLPvjgummDqnF4FQ+edp18g/UBv9hvA+P r/XXy1QvVD7X52v08+wkOwQGVt5/t70PB0qySgesgMAiDq2mUeS2a+RrpZbCjrzTJSMzl9kXh8Hg 7v3/o9fcpxs+jyGyCKwH5QhK/ePTH9HDsmzlwGvnJYNUAIDoZL+kbB+QLNLcyJPn0kkIfahvyDOD aFA2e5s0MwOtIsQ0uAajPdDSrfYFi3sCw91RKA6fbwyF7A+A9n5R3AczI9LZIpptjZ4/YXUeQwKO sI5AgvVDg2APg+wDgZKJC2pGkwTPo7kH5Rdx7f4JRtboxzUVQh1MErV8RSJIoQHEEYNSGK6FZTfK JcAIoH3FIoYbUKQKNiRgkXicryAf40B+qI87DuOBl1m8LR1B+ZNYc0dof4uLAulT4bQkzcA6rR++ U6enFxUPrz9v3X78mTQ0FB+thicmbzPIOGmBLsa5WDrq8Bh0djI/F1iJRn9qA+CkqwlECIaB8wed +spegU/DB1A9Hw+0LEsloNkXkHMnlSCXBtQof18nseIrrekU8x75yagBuBX9x8QcCDpbuIXiCQzN IJcEoSDE8KRwmEmw8CJ3bRlOcCxUM7D4BA1BM6hlBVxF1PMrQdYXcj+gMIvUeKaIBgKqgIZYHxDM HyQGUUwThhS5URRYRGYREEUROGOBI0gvo/pGKvD3o9ntMMdD2g0sOMLA/djN4BhJFiyCnWmvgWXx HM6ZGJxmj3lA0NOsplCCUgqgaSkYloaaUOPY/TRIQlT35BsAwAJliZAhJCVgEckcQGCUgJEWUSqS oYCqqagTH34pCIaZIiKe/xI/U9wI63FMEzBYQbwRbhRYsK8xzV2vXxgU0ZA4OOJAgQIQB7VGkxGP eAEsHw6sDyNyDwHtm9PF0HL1J1eQmRoSkAkA/aU6iF7VgaS5wS7+b9rcDmCF8wYfuTQm4wBgBMRH V0FPDITwozNNJ2YNmzRBW68UE5uIicAF2RASJAagnL5gcge10tEglQWvKmotA2r0lIUKQH41PnIC mjYhyBLSIcCgaDse0tcGRkrSRjRKW8MQMMQjzobgoTRxedk5OeAOpXyB5CAWCuZuJyM9gP983Awg OYD63gDIBA9VImkBE8l0Yo8Qe9R/bYCwWKjACLUR5+37pSPCbVB6958IJ1C9IMH17mgYGDUXvBil iEiDPlAh2JvO4r+Gy+gnsStjZNR6oVkARBDqjke/6EHFQ5HjR7p2L9Ewo/b55PwSfafoSDK0CUko WeSOwXwkaRlokaCjeCiui1nAVwF9CKDnGdvSxowQkOrB/c+9w+5O4/q6fTRNSAXzQTgBojqmoc71 4VWiJ1g8W8phoKJ+qnaB6o/L3SfiHdgA3AhF3bylV7qohaWXzLKU5dxCqNIwE7jmbPI94zNsPI9E gQMYA1KKUID6/VxqlMwYZqqXIkyPG/SB608Y3dinSB5IECFQHNzbYvXAcaJAIXS/wXDyukuDhjKE BQl6POeBwbAOIGBgIkMHynlj6ug8XqiqA/eIiIiIiUrtjsA3AO/JHQex/WB6kb4HEJBZHJW4MR8I OHuxqN2QtBg6zU0UIPANloBC+/76ImS3TCK4EdZyBiSDmaXfPqUO3VJJSUGxU+dUeMg5ZWB6K4e2 5695kZmBYhlKkJA/OE9vDERMxGImevHEzJwDB+D2BpfExy4zY22SRkDSy3caAtJtVGY+HPZLTlQU KUzJzSqWDxLocXxsvM/tNga+deTmmP0P5+++tJDOnwAlbQqwRXXv0lgKgBgF/CyuROYL0BIegiOJ 1g0i4HHhDAvIhZU8UrwfR6YUiR+AwHAA0DCaDS4EesGJoKKLAGfCU2Xtbcf36QN5iAOoQfX4PW73 DjhsgGOu7p42EHtSB3lpdmxNlaEFUpTMrpHICyEoJsBRM7bUQ88EdV2QwFUzddIJ6cMcYlFDBNma KSkCNLgsW99WpjJOCU5AqBOMxMscWNCxt3RZy4EO0qS2UGbyo2wbBGU4K2YyrI0LgAl4TvA40HIR KGrMigdI0o4ApXLApojcAwEwpu3aD2a1N0QhF3Q8YP7LB73A9n6ibQYjuAdCD/uQePwdKHBUDzDA eQh0B3tDSnUSgIqVvsHpjO18N/0Ho3H1nrx60CR5u3q9kxrv5goPeJ5Bn1bxxhd3SfKEdJYhX1Wi LRdIwI7yxdDNwGFyO4czlAYhCCBUqB8Z5yhzmV63CJ1JyDmpoS6P5ZmsZJTZdZALpg5HEELJxepu WPEIP3Z8CDJ7BlyTBJ91XPamSqqL5qaHGXlUmYIUpprKa0KVC3HqdQ9nG1aZhG6sqOxi+LGDwHQD YB2A/CGoVWymDA39EKTqYmj16Ucr4+mpFUptXlDSMNMLmBDbJF4+eywDnGB2R4B9590EbVN9CVDo U48y5oeHycrAH0YegT6RKEgnYJVzQbjApz635oazSa3Xr76+QKuT6tUZZthZ1wns1U2xYOGixIt3 hpTY85xtkFQLQu/XIKVi/EaCIRBoYcOihQRFSQMIJKJ4VFDJyLdnQXiCJdyBSXTRAmUyEiDqYXPi rRASbxScLDQ7WG63DXqhqkZcmkHJW1vcQCigXc6O6wzByCq/OgUAtozJK6RR3SiOgCqCecZIBQc5 RWyKekJoOXYSGzYFpzZSSmI1ASXGlUXzV1SLAsIjBRZEEhntYFSyUVoF0J4RoG02m2mEZOwLnm24 KUwTLgo2gJx0dzWZBYMqSRXzAKzuiZQqgFMcWsUZqa6Ar9yAXUnVGEEvKRGdFXBSUc2ni17gmWKO qYZxNHUve9sj37AucAYpJdAWChHJgFgks4EVwW2Bc7k3KU0ZsCgGG3SV26goC3TWsZN20xKx2gsY XGCyW+Oou/a+IfKns3w+hNnSnS/InPXnBggjaEZ5g3nLM4huV1Fe9saeBEoCyZN7SaKis3mmEPF8 3zBe5EagVlGbuIsrMhq0QtcLy9MQI4Z2VWmtUw4MOJWoBaQ6bOU59+HXrqbG0y9EcVDZw9ZgyEjd B6g4q94di2z43qdPGYtlwFogziNB1cUQQ3ZYx5uqDm4fDRzvoQ6hsMR7AZ5OMNwtmgWILq6PxrEM 2yauz5OusRiIe13jgothFkq9Gp2Yr05xanyIoRsYuavlVZ2vCwQi7KWAVhE8346c5i0DwQYEO6QE QQggMqFRpdokRIRDiCJEBgZjkkYNRRdRdYkoF3ahpBhpsQg3E2ScO197kjJGcwCqYYqSV73qYCgz quOw0akpoWAVTW8WsUaQYs03i8M8F0SLhzZNNq6SdiaTE5UjEiQkHklTETrcXRqtJhRzNCg2TBA3 gWCmrjZtUKFoRQYbGilZqIXEXBTDAo1AB9JmiBgWKdqv5N7zYCEYqBuQTlBQoGRQJfqNq7ygemBi DpLi4dIp3PdpohTuxyohHxriPzAdgG3tAHj4bnw7ei6QHoTRxL7QbANGZvzBsDQMefApGn4fQEyj QPkE9MFD5RpLjeqbyN46BIRtw/5VrpA2FnDLhISEpQKU0wo3EqMEIECYA3RgI/ODNL9lHcRG4Vsb b2ZkhEjyjR9gvnUs2ADA3fgMwde1XqXV0IHpIfZFClZtvTPzg+gGzYQ7g6sF1NBpQ700wwyKOdym 8GmEyQaxkskINgQlJVRh1KoZgOkeh4DCMCBkBr8SeXgtfHNaOSBpr9hegV371XSHr/LX0wsTlkjz sDsgJyiqB4JZRd1dBvXcDwyX4XPuyyppkw7O2sM9WMAcuzZrY8lPIVHDFSxaEEiQZGJozDv6ybQ6 r2c8f0mo1jwcAzrAT8QK+3uO8CaiSKKqYkiSHXq6wEOIvf52JuHGixbaIYF6q1r+MFQLYYlptgMs IiDSxBThvzecuiYD0JB5CT71CjeJvYop50WAIVfUbU2nSbwNyIni2Bu22YQ3nPeXC4ONay1m5VwX NADmCseFicfH6xrNVUkaBOygYK5AjaiAVAqvRAeu4bimQgghly6FEqwoJBpmwJyG9id1qShJrAma qMOlRoLQLpX2q05uRmYaEV0WgyE1D4RNYDxF4LwS8WuYDBd3Vp4POORnDeESHAGkc5s5b6tIKYkY JEhYp2Kh7IpIRgTmhQQ1FyWBr1kAU4eSmEdtYjGYCrBWjnWgUWwSChM1wWUR4wLKGErI/rmZrjJm 5XW1lwqKnpunY666rCopXSykvi19gxpDXLLJm9xw1BJAPXym0EhwIaIPb97xCkY+sgaI7DMtSZhg Yz1uAajTotHxNyG3yaOC5jDa4SEFBERCUEUpFBgDmCzFhoEw0EmtMymA6CUiKRZgoZCdE4jNFL4g foNyBtO9Fe0GPpAIB4TY2CAGcFwDoh5pAKoqpmYioR7POsAMBgnZ086J8J8gOHI9JlpSZZCQghZg gJJ6AeQUH0wjLAfnkJEImDiwgoGYd59D9n7wFgwQH2/foMqn5de3M+TuH5/siwpxXKJhsUICB2Ds 4A/1Qnt83qIemqoSe+prDyboi1k3xxDAhHRHvAwuoQlYOUgRPmE0DAOC/gfHJ9LrCgq68ceNdbRG w9nLynau8R4iRMl1nMv0tzzakDEhD2AGlAsUWDyF4MNgHvTyBIEgx2BbOykhH2s2g6K/GORVgirz 8KW96tCkgJvgdakRCpXVKRizDChySsNsIAXK/HJcoyT9yNVRdSgwb1gB4Gn65UzH4emfckr8JMck WmKuw5jWX2UhrLFjE6k/Nez4xTEjbaUgdQMAIoansTzAhQO3PEOQPFeTDPOfn7T4bYFFFLXEK4Sg NHM8ZcI63JAR7hBl4jyOcG0YhctCwGgtDqBhEMTSaRO9EKSQDaiYd/W9gHG6oQOICJzMckaQpJlo JiYmEKBmqmZKSJVkgkJAYJFgN/ou9cqxxAhCfJinqda7yLzwuTiXuF7l6KOaMqjC9rOBZb34961w 8O4KQKEgkKKTNJ7AMQQiNl6UCiAuScA6jQBGIKWdaF2ZZSKWuuOhvk7SqKgqQ4BXk2fUxoOuHrJh jt0oYB1OnAHUEszRJcYzjgFA8GMJhkKRO5TU0vckB/djCarIDCAObhmIDRZEfqGHn2d/rxfHWyyg IgSYMZwi+eSYH43vgpYqmxaCrGpdID74rIetKoUurAW0IoQMC0gFIkVAnPMMMBQFJF3TWbOvonCE 8oiXwpguMAYSFg6HgG3E44B+WQ8zI8nQDm5SRgYQIGiYBgGgXQQDpHaRoGHQD46FgMv2pQUDCpgc L3giZZg67P5zgWOArzyJCITTRY5DdtJH7QIgGrrAyI9EHaPWhBAvnU8QPQSMH9KopCgE9swL8MiH 2pRwEOcBOoZRMgoEpGiEGiRBmFcE7xPd9VVx4vcPpAPxifYWhSITgSBDuAQlT2ofcjyBtQeWmoDF EIC4USwcMAHznUKfdkXAe3YOcn5IJqkWKMSMAZYDwwDNQPe58yePN8ao+yXPTBM6lPRHI2QUu7V7 dYOuCM4JdjgYN4F5DE99scBX+iaQHmIDuPvcwHJsDBfjB7rsB+oivnPgANA8E9XyIF+t95pfQjCp DUq1RKVRJpgwlJeFGMVNpFO5Gw7nAHfmQPHoOudE6Sk6EkQkaXrDjQ0mbYjyCKKEYzcyWh3rAJ8R avnu+XQnIWdshfT12LL5588B+gf78AHf9ROvm9PQT3w9OLoitse9RLsjJAomAIkgML9NNCfhhS5J mW6cuagruAW4fTpvSfdgxiBQO872fNpun0v3DtDcBufZBYshHvPygxMQN5QGR+CfA7juPU35C0EK MZLJyFQeDt5vJzXy81M/MRnU5JhPOAlAgcicgSTqSmEuh2+OqyWoPmBWBQAeTAidSKmBEgD2q1k4 gtGSexwAoeIGnBc+1u5xXZ7xzc8Dxr0EqSP9KNZFOFblHQ96Zh5n9l2mge/vcG3Jn4CKkUiLtPYU VIkscx7L+GBXyxs28xZsZnpTNEEuS0kNLMMMQVG8PV0aa7cLXu6WPv3nNGNWLWgRQ0jCJNyYxGGt YMSjZt3NV5onGpow3wRXibY44bhEdC7zRQMuMjBEoLQLxhQroDW+xq1JMaGCaMXgQPhgZqAxG4oe J5FkdQPor5cAPikoIGApQgb3YVMlF+isKGRQJSDMrCTBABREAREDIMMhJChAQxIxAfFIB+JOrW7D 0PJQ3fKcAWRUhAEjCEVmDs+rj8vxzY/zDuGiIKBkQIRqYCYGAGoFgWTp1P0hO0HnZBVPgD5XbpnK gYZgKlKKKMcMCFKKKZICcVxUgQ+p3/WzrrsIvKUqFzBPuNAQEwFrDVIqwbYMNVaUKjySJtITZ3ie QHhAenB0R0OAAHqBit0NpcNYbAb8R4xBhrtpSd5AKF1U4A0d9qIaoH2RJoDSHIGkrN9wdIwCI8pF gUh+ISEIJSjh7zgwOZqEiU1KoKEzGjSbd8KoaIiDoDxA/qXQkSiL3P/uX/R/9Hr/8e5/Z+31/qbt s+b/h/6/q/fP/5V+5vzm33UA9Eo4CTA0OdAdbG2L9mJ+uafs++CTBQkQMbd3CLR9KA19ZwA3CGq+ o8b2U/+N/GxfHA/fW/PwcP0Q4RNSEU+EIgFOyKUJokcQcve2C/qHNyKOpw1rAkzDEglIyJMwYzEV xMkYliDDMwHWg1QWhBjGkjHUusTVjpTAuTZuLa4zS0zME2KOzrMcDUGGY4l9UHSYuhyLiUw/GlhQ OzB3LokecxyxJdwBAXFSmiClIUMDzCHDUcCFBDR7wfceuUnxA/byDJOZfRGBFBhFirFIqQafLxSF VupH5DsxSPd2HM64wuyygYlxRqlIlHQGITy61wT5oO/DEchfQqUEQjwRF6xmgTCBORVATBZVaDWu fRrVsGoJbocZWtqYMFrFNGY1qwzBrLIMmZKFmBnQN05M0E0QLCGmCbKOxsZGmKoiS7KXIYwXfSFR pNIrt5UKbNBWrSWQdRdcr1/AAR4rLAMXFkKq38HpvxaNHoyigPqm8L6YCDVUQffh3ZKSCXbsjwSr tAyUerznumk+t4g/s2W1sAnBxJl6jA25seYiL2I/W+MIiaSGl7QfSe8ETNJBXvWY5otY+QMcXBxx prJOAqlgCcAzTOZACEIpzm9Q5+9KSyndZL3ujA3L+tKDXvKEDbYIOIiNri0RUhcAcKBgLFMBM23M c0yCFhVxOQ7PnQB7FB+s6iW8iBwXLED8QqLBJLYwKdLwUTeMk28iudTvf4MgphTE2NkofgIiIIVE kQTrYjgqcQJEb6VR5XCEBGREsdhxOJRnr72qJX11RcG5QEmQZ6ibEdh5bXrui92sIyIhssUOTEWA T+eCyeBrYakdA2EhGoxYCyY2wqAhrSZGKsBgaQ4vV4IJlBoxAgFZoKRY4MozWXgaY6gc6A3AEBEu +KIiqq2Gk6H5SUiUKCYoZhJZUpSFCEVCLBIMCK8QNowHz28DZ3CdpHZet65piFy8V377/x6ZkR2X 1MAUoXBqTCGNaX6d37DCmqhU89TQpEp5Pc8ieCk948i9p2qHJZChFtwETfUJSRKUIGlYByoQu70+ vS0ru+9xwGOV4zzIL6QTBScFJZmqlrBc0HB8Fixkc6DElVk4CWLDIOikD1HiQ0kjAyo614C42FYE GFFAUlJSwh3bDmOdsGQc6EoiiLSka2kYl56qVQUYtSA2CpoklBMIwcXhoGu7qF3hTEZsLGOLTmZg ZchWnB0uJgnloNWJgm4aybE9YM81s54KJObh4xMRmFg4+Jzlo4k3tsVBNCLEmMYKjtvBwEqFATRn agllNjBaTdUTLS2zDIe2GSBm7Mg3tXtWJaUaRoBIOCDRIZqLHjeYYYiWsVwihJ0GROUUSBhK5D2x ohmNMDwTSHzpIyZAVTXJglRgc0QIbiOYM2sxIgSBsyFbqBgxEgMUbICiGBiYUphTtMB4AgdpJDAf ITpQYpE7eo83qLnuwuXGYNeklHQySstJOlWaEMI4dR+ct4b02BYE9oBbHEnIGyGnJ57D4DpUfK8R UefRycnvZhzzjFQwazImBPSgygK8oClKyAwwbbZ+QEEJKjoVjJX0OINA0IacxHDDMihCCYMYKTFw kEHBqFmLDAUA5G2AcrDAqeyBIpmDhsX3IUgQSK8ovHm6CecigiAhkGlG/BOMSAev8f6P4tn3ZPqE dPmwHBh7Fjr/Gdf7R/Jr8Tioch5geTEESxIJEQ8wMEGghFyVDFPMKkfkdmo2i7PQp0AxIJSDoRhI fxs4JEmimxHkac4DGAwp/chAPmAtUyiHaL97jVmr6jQK9/5QwDfaHMi4EBkqfTheQEMBxaFtC1LY rClASWNmR7W/nzoo0cCBoJFiEKCmhiWRIN5iCUDyErkLSd4OYlAJAwTEQPSBxtwmSujONGDxhjS6 zBhsBpb1kI1TMZG1GCgBMi4WEQcIsqucC4DJmBpCGhMtHGCo4gDoQwdYRLiQpKmQWJAyC0bl+BgA e9DoRBPWhm6M0LAKFAaRsgmcUfZ731sa3lvYdXR4BGxjZyYxqzQGNNID9sD+pA0uj9QQ+vSk0iO0 KEmmxSgb5JCI6kQJP0pAvQHS0DUe0gh7cqwkXsR6nTeU6mo6aGB8QQyYT47VJGDqfbo+UA/f+BX4 Zgv1EMDAIsP3SLCRpKBCGsMQMlT7A18Dn2CMsAKdp0+58Aj7fkn5Mja9wD2g9K74CkgEiQBOCP5A UNxvPiXAT0MIkVQiEDvLjMYXrViJoRMRgG4OAHGIKUQ4kEiAyNaZMBwM4HyDmEjEwkdnpAhJU4cC MBaBqIBbMFNeMDENsCUAEwsSEJCxDQFK0qMwEVU0CD409z2cNpw9wHoocI8GHaPWnWdYt2g2UjRS hBDwJ2xNLITDCSQCRAEQsEgQJ4v2GKxQNKFAEQUAwBcAfGjBkCOd7S+hoRWlQ6QXRBfl1fmzPKNv gzrUwt6ZhkJQYCYGCfBmH3iiw9mZJVaz62mwxOyB50ZiTkU0SSgdYQCQi9/aDCQGvL7gnxiWUHMo GgAoxdnMPp7bo3FJO2si066b1KDrIQ0lI2SLGbMUUTcC7zqCIop2BxBFJfj/Xa+gaA9od8y1+lGo StZzHqW/2Hf5hfMQ5NU01GqoZHHMfwzkNObx1Opybdj6s0aYePa4zGdYB4HMbjdHqgMiSQidYP3R F83ADV3eqZdbmDBOomj9gnTqOoHajn76hPeQQO9dwjQnn71/CAP8AMAbJ8USTLTHKhaOgB8QfXaB qDvSAhDYH4fjGFvlOTXdwBoshqsPI5fPke+aoA0Dpn460lNVRxtdPkpxJx2dvNxeDMRcfgg1CFWs dpvBPzkIQRyBBwoaMCilSyOgGuorBu5BS9gc0GSQGJIh99Padrxfm6sJ4kPn0xAKI1BrIwSDhC6V ReBLJWB1jfHExSKFjqfJTeD0WyLWidECgyrsnLyp/LCzF98V0EPsg6YQY0RohIA+/4NNJ9YPdAni vJGAnpMhbP6oSMXLhbJXeYGCD0aHtOh2xfPEHqHC4ZBA9FCTkwhUhuRxQSHYahcPaZUHdnGTNQD7 ci7p8h2I2OYl4cSeY7ySfsf3SiAQIQgX64BvMs5bee6qQB7wB1EAbHcS/iULkQBLR5/xEyXEDh2i gngh3wiGBM4oZI0DQlbxDAdZBIQSIQrgMhirY5okTTBDDgB4j9XsL09b4SUtVVJCVUQUkzQsLJMD A0gbgCkYX6gK/69lfNEeD3e3t16+rNXSxpK2gDRZGIOLAHKoLc6RcgHB3kbs27LQOIBRBv3hNROi CgygjGCR0YYoxgRoGVNDgNlOA5kAVThmEkg2A4o41EyQasKRoirJEYAxvSbAIKaKhFGZSnchEsaF rUAgPOmLRDKAaHjNtB81J4uJvdrYFlVVi0GoRMkgBhYp9eb8pFBLBXj5kGoiYH1PClMBJI6AU7wN rEN9LQbQf1PnZ7UEyNQPkYoGMFeZB8i8R5HpKMI5RhmrBbRg6dRoIVCQssAsGNLt3+JyeTgR+8T4 jqFaXiAEB+AU5I0DyAm4BrdwvdGA2DoAfAHwVpGj4B9sQDP1h2FAN20WbpsAaTAwdXPXV0legiDq yE5WSVUCRr64hTY+/LumXRTcA+gPkfzFUZanaQYQegPo++9AeCoB5hOXWAOKickauDge8HXdeeDo lUe472UB7VDfxA/bCQCGolNgDlBHYy0eaPDBCABgVogMVdioIpxdAOgJNLKpQaFE7BIHxgHMC9Is DmQUSgFuYaMhTtTElx9LI2LJVg/gAiEiQc8gB82LR7GTzAwryEBSI8MKux8qBs4VGANwGQRVC6h1 gUj9S6oiUGFqFirjY2nTb9NfEvFrObd1WJFKvQst9Rja8S9b+DGWeWYpOPEspyZjbb+HoxQ1fmLl g+8q5JwCXx7/gOSjtvR7G0adzpXCcbTUmS5InkI8PvH2t+QJlvibV21GsT4EEChQQmuAWKmYs2RK BQEQkkVECLBY7YOaBW8+FGM7m2EKqGjKyRuYcPfDfg10E0Ly31hGQGHMHHcDgFQKrtO5e0Q5asC1 kgEGxWS1kLF7F1ayWwDxUDEUmUhPpomeNpkSsCaxmLjKkulq9GitwWSyyCZpv32kmjEEg8pQeKeP E2zmXlnoFEHaJ04u0IjZckWDYXhYC8YUliBJwJnj1drTCFyDNt4DxscPhgV6nfD5MZtVJDeq1qEk QN3ObAcHBZ9ip8FG2bVfJbqqIcQXOLZqDEzG8CIts7zbCmS8lVaMuBDkgvk4tpXVmlnVrXsLFKL5 a0LAkMBXWpIXRQurCQtAryg0WtcbTVkKZgUly+H5cmlzh1duJkl2ANzeR0cFLeErdYzTiXz3ZrVg RsYLMewFwXBseASlSoDARw2NsaHiRdtegP9Vev7vfbaiVK9UBeFs8dKeRPyrXz9zS9CbEVo9dNGz kQQYIh9FaFI3yIVAh8iibigkffN8TCHybGiA9ZWs2v3vMr44I7ebfZLTXKCVX76B9RELj6yOiJoW kSstFfwh0r8HeJK8EEqxnAaBt4lWBwS4NxHvMFurgDgDAHxcEsPOmOlzBnB0lL4A+hhTYhyBxVM3 5BdhJ1eg+Aj1BxuDQnwkBrS5V/DZqrCSmKxi8y4XD7e99DsIJCi/nfPgD03V0hA6zt0dLJc7eQu7 nBpUqIMB6ZiGl38fvaR+S88ncRWRFk9GPgCEPfB+1+rr1Mftx1MA3vMNA0dKPFDf1vWdhJoYh2Sb l0QDssIhYUIqQKJIcgFwIDsBMUgu4umxH72tLXobq9BiHbo1KRZqvFqIAuDYyEQbQgFEEa0EDNB7 N+xNzztlPcdDJOFhF2HAU7XleVPWWLS7e5rE2cq3CMMRIQD4x9uvztIeU9YoOKnHzHOD265NQ1PQ 9KgnRoBDUDh4SQhNnNRIGM6Rjq3Tla9RSajU3RDUjZRDBNCSiEGgKC1stg2gLTXQW1cPzry3I91Y Y8GtEXCIlwMt78QGAWCSCUDGMuWsfPhe1/LRWXpuKenb7gsKI2CHlWf4aO95awXGQaJRAI1ILtvK CjZpFwQAsugrNGqhoD81RwYOQVlgFkUHXRCXVDOXjVASt08MedndkDoqRwXOzsFpKiMhpYRDHvUD g2oSQXGIWxxvtVAx50CYKZXAgWwBbhYGocFoMTa4a6UupqApl5gslgaNTk0Bz0RI5TZnGknCNoDq YUnMKlbAV9wtAaaMgtiTZUaan7MZNcmrInYQ4RBAiEwYxYaGZmZQwsC6ZEXwcrJOAMgtE3G9FA6i DnCi1lHDMQpMItywlEERw4e04lWWnvnYo3LGw5Bshse6+uAjOb3yZIFR2sRktJAjAwJttvLV4rnM y4mcwTa+cQXLtnwdsq7Wb5zYsghD3wIldQTUAsQji4UCYI5rRfZi0dZswk3ilDd7CLCL1Dy3CHWp tWRRbPI2lonJhGuwt3qDwkEzNN51O2BwpsbbJVEYG67Hc5juUBSEpaMQlIwBqwK4+XE3IDieOSOb xoMJOAlOWiHGI0ccqJsGhhg0mDCkQ1wwHIWwUsiOox3rDcXY4A1SMBmgrgBhKpLlCUSA6ldg9Qb0 Uk4AEwsq4TwEj4gnsPcONUgRKRC9cDyo6MEOs2OBQTjFIFLEwULNGjTqdJ2qDwCHyQN+xsHY3AMq +joivBCyEExJA0KjAUDAIQJxwSHUJsQ+fgOhAxjbK4QAdYMOwYIhdiYIYI0SxMMOGO0kwsUgTQeK WuexTGsgoNTAK0IibAokbarWrDAGFd55Tzef0llkMFnpt+t/JWeZv4HkSRIxB3CgxVpIwKeKmzkD YE3dGMZarBsNQzU3HpgOt4QXvUMfd7aHzxPXWl1N7535+LbY3LKGlPPRaXECmAhCS4hs3gQxFrDM yzGZSiTGcNJwAp7IAgFPE8wjBNQcR5FtgobBCCex+YkslwHvBoHxzBpapDw1ArjqEuZJkl99uRoM 8qEjThC6MlHBAtJFQpGGFCIU9hBEgkQRgOZBQhxZBBBjCBooGU0kyEEkBoyEjNAy6sBgPEnYhNEj n5u099+iscIQu1BkGtJoQZA1ahAiAPscVXngA2BioEgjl2m4RgMFMW6bNUo9BNDdjEPVwDaxIxYY hAOYFe3cxNFFKibAKVgB6owKoIhpBpWJEhZQk4Y70AZQ1DIjDZfX/MvNevpUhGpSyTWhslruoqQa kzetKRaULCMAyZlWfRmScEoW/ppSiAwwXagmK8US6KkARPuAh5K8NIOs+Jh1HLql6oq4GwQMZCA0 g0DKD6XyQf9l/k3wj9wE7iASRClSJBXoCHxKHrIPWKvWQBpCIhrRKBsGIQ9AB+RHSthumEUx5weI OAuaqavxUi3DoHTProGGAAYAUdNWIQCdT8JiqNkICbjfSaNJrEecHpaJ+NjC974vVofio0b1kcRk 7bve7rF1EUQGsjEw7kDFAPAJDy6PHE+pE9MipiAYtHMQEdEEQ0JAEgvMjFDYRXAIQ8l+b78j+ug6 jtU1m+JKe8qwMEajImFzHEBYlhimpoiVdgDoEO4HzJwfsw1TSlMSSBSeseIWkIiHyHjgCPGHxRhp RSfXKCoqDgC8UyihV2VEKSw9yE9lIWEQqftEsLmiNo0QNYK8QPlD57yn4oG/h4GyCb0UMAwJ2EaE PpgNIyGlzAeZIHO46vX7M+YQ5iEg6sBkGyuw3/O2UNETfN/yVeTJo3w0m7voQHeoPe4Bx0hDthAp E1+Uw4dKQMopMkQhERSTJzybXSh8WGcBAxhFokqlT8fiCGAL3wTarkDXwwU01S+n1V9kgx0gdGHR h7V1a40vSAooiB1kRx7SkzWAafhH2WEoSDnAA1xUO1wDadD4YS90DPS0JQAxhzUSsIDQEbU6dnDY QTmpAxQz9GBE1FHCvMTg4FYOQBrTI1AlJ6UOw1nYXAyL1jAUZ4h2dZp2B607AZYGhSgGYUDYA2/j EMC44RTB/0lcSCA2AfZjEPeJFtTXFws9erYiA1ZI0O28FYSBM1riHQ3mhA0a9sh5r75kGI2QsyrA qJwCjAlVAnILT2CgdogIKUFIoYCg29whUxo5NrQrMaqot7hEKCB0X7kFmVQLoDQrvacLAK4B3Aff pqUoOwHR05Xu9goOu9H85CRkhO484g+09A+2CphoCZEPDR8ZvYjqAKFx2W7FIcLAjIr4gHkE9I+0 MtNCijGed6QHKED99EH24JiGBiYta5IwIZCKQGyICNFUDSNWa0jqKoaEczSOroZaFtS6NkiVCBhg EUzHcRiQ2DLPWn2nrJIsIEAOoTAYpheIJfwb8P3uf+/4P8dd8P3/wc/gxC/+Z/b7kQg+6P/8XckU 4UJBO/2SdA== ------_=_NextPart_000_01C44E18.95B7D150-- From David@phenix.fr Wed Jun 9 13:10:52 2004 From: David@phenix.fr (David Neary) Date: Wed, 9 Jun 2004 14:10:52 +0200 Subject: [sane-devel] Re: How to configure sane, xsane, etc. Message-ID: Hi Fran=E7ois, Fran=E7ois Patte said: > I am facing a big problem with xsane from fedora C1. (xsane-0.91-1): >=20 > 1- I have a scanner Nikon LS-2000. The first person who ran=20 > xsane was not=3D > root > and it now impossible to change the owner and right of the=20 > device /dev/sg0. I have just come across more or less the same problem, and have tracked = down the answer. It seems to be a problem with the default PAM set-up on redhat. When you start a console, you can use PAM to control access to system resources (such as a flash card, or scanner, etc) for the duration of = the session, and on finishing the session have the permissions revert to = sane defaults. The file which configures how this is done is in /etc/security/console.perms. You should look for a line which says = something like=20 0600 0600 root This says that if a user logged on to a console tries to access a file = in the scanner class, the permissions on the file will be set to 0600, = with his ownership, and when he's finished they'll revert to 0600 and root = ownership (at least, I think that's what it means, I don't understand it too = well). If you remove this line, restart pam, and change the permissions on = /dev/sg0 to what you want, they should stick. Cheers, Dave. -- David Neary Phenix Engineering 110 ave Jean Jaures, 69007 Lyon=20 From yannig.perre@ext.anpe.fr Wed Jun 9 13:40:08 2004 From: yannig.perre@ext.anpe.fr (PERRE yannig (DSI NOISIEL)) Date: Wed, 9 Jun 2004 14:40:08 +0200 Subject: [sane-devel] Re: How to configure sane, xsane, etc. Message-ID: Hi, I think, you'd better try to change the permission for this device in = the /etc/security/console.perms file. Change your previous scanner line = with this : 0660 0660 root.scan_group Then add user to scan_group group (or whatever_group_you_want) to enable = access to the scanner. Also, you can look at the hotplug daemon. For an USB scanner, you need = to change /etc/hotplug/usb/usbscanner script. I guess, you can look at = /etc/hotplug/scsi/(.*)scanner for a scsi scanner. Cheers, Yannig -----Message d'origine----- De : sane-devel-admin@lists.alioth.debian.org [mailto:sane-devel-admin@lists.alioth.debian.org]De la part de David Neary Envoy=E9 : mercredi 9 juin 2004 14:11 =C0 : 'sane-devel@lists.alioth.debian.org' Objet : [sane-devel] Re: How to configure sane, xsane, etc. Hi Fran=E7ois, Fran=E7ois Patte said: > I am facing a big problem with xsane from fedora C1. (xsane-0.91-1): >=20 > 1- I have a scanner Nikon LS-2000. The first person who ran=20 > xsane was not=3D > root > and it now impossible to change the owner and right of the=20 > device /dev/sg0. I have just come across more or less the same problem, and have tracked = down the answer. It seems to be a problem with the default PAM set-up on redhat. When you start a console, you can use PAM to control access to system resources (such as a flash card, or scanner, etc) for the duration of = the session, and on finishing the session have the permissions revert to = sane defaults. The file which configures how this is done is in /etc/security/console.perms. You should look for a line which says = something like=20 0600 0600 root This says that if a user logged on to a console tries to access a file = in the scanner class, the permissions on the file will be set to 0600, with = his ownership, and when he's finished they'll revert to 0600 and root = ownership (at least, I think that's what it means, I don't understand it too = well). If you remove this line, restart pam, and change the permissions on = /dev/sg0 to what you want, they should stick. Cheers, Dave. -- David Neary Phenix Engineering 110 ave Jean Jaures, 69007 Lyon=20 --=20 sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-request@lists.alioth.debian.org From esoterican@freenet.de Wed Jun 9 13:54:15 2004 From: esoterican@freenet.de (esoterican@freenet.de) Date: Wed, 09 Jun 2004 14:54:15 +0200 Subject: [sane-devel] saned only run once Message-ID: > Connection refused means that saned isn't running
yeah, that's what i said ;-)

> on the server or (x)inetd isn't configured correctly
this was the point.
i didn't expect that in a new (knoppix hd-installed) system there's no inet= d running.
maybe i pressed the wrong buttons thru the install procedure.

i now installed xinetd and configured it correctly...

and ... suprise, suprise ... it worked :-)

thank U very much!=0A=0A=0A
--
=0A=0A From gilles@ffii.org Wed Jun 9 14:40:39 2004 From: gilles@ffii.org (Gilles Sadowski) Date: Wed, 9 Jun 2004 15:40:39 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601215656.GA3524@ffii.org> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> <20040601215656.GA3524@ffii.org> Message-ID: <20040609134039.GA3769@ffii.org> Hello. So, what is the final word about this "timeout" problem? Is it caused by the "uhci" driver? The one I must use, according to the following: Jun 9 13:06:27 dawn kernel: usb usb2: Product: VIA Technologies, Inc. USB (#2) Jun 9 13:06:27 dawn kernel: usb usb2: Manufacturer: Linux 2.6.5+g6 uhci_hcd Jun 9 13:06:27 dawn kernel: usb usb2: SerialNumber: 0000:00:04.3 Jun 9 13:06:27 dawn kernel: hub 2-0:1.0: USB hub found Jun 9 13:06:27 dawn kernel: hub 2-0:1.0: 2 ports detected Jun 9 13:06:27 dawn kernel: usb 1-1: new full speed USB device using address 2 Jun 9 13:06:27 dawn kernel: gameport: pci0000:00:0a.1 speed 1242 kHz Jun 9 13:06:27 dawn kernel: usb 1-1: Product: Hewlett Packard ScanJet 5300C/5370C Jun 9 13:06:27 dawn kernel: usb 1-1: Manufacturer: Hewlett Packard Jun 9 13:06:27 dawn kernel: usb 1-1: SerialNumber: 0000000000000000 Best regards, Gilles From henning@meier-geinitz.de Wed Jun 9 16:18:18 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 17:18:18 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040609134039.GA3769@ffii.org> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> <20040601215656.GA3524@ffii.org> <20040609134039.GA3769@ffii.org> Message-ID: <20040609151818.GO7920@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 03:40:39PM +0200, Gilles Sadowski wrote: > So, what is the final word about this "timeout" problem? The reason is unknown as of now. It's not that easy as these timeouts may have several reason. Every wrong command that's sent to the scanner can cause timeouts. It doesn't seem to be a general SANE problem. I've tried several scanners on Linux 2.6.7-rc2 with UHCI, OHCI and EHCI USB host controllers and can't reproduce the timeouts. So someone who does see the timeouts needs to investigate the details. E.g. if there is a specific SANE version that does work without trouble. If that's the case, identify the change that causes problems. If it depends on kernel versions, identify the kernel version that started showing those timeouts. I'll try to summarize what I've read here and in the bug tracking system: Timeouts: - HP5370C (avision) on UHCI VIA, Linux 2.6.5 - HP7450C (avision), sane-backends 1.0.14 (also tried latest avision code), Linux 2.6.5 - HP7400 (avision) on UHCI (Intel Corp. 82371AB/EB/MB PIIX4 USB) Asus board, sane-backends 1.0.14, Linux 2.6.3, 2.6.5, 2.6.6 and 2.6.7-rc2-bk7 - HP7450C (avision), there was a hint about the hpusbscsi driver making trouble in that case - Epson Perfection 1670 (snapscan) on UHCI VIA, sane-backends 1.0.14, Linux 2.6.5-mm2 No timeouts: - Several Mustek+Plustek scanners (mustek_usb, plustek, gt68xx), sane-backends 1.0.14, on OHCI + UHCI (VIA PCI card) on Linux 2.6.7-rc2 and Linux 2.4.26 - Avision scanners, on OHCI, sane-backends 1.0.14 + latest avison code on Linux 2.6.3 (UltraSparc +iBook) Typical log: Jun 6 19:06:11 localhost kernel: usb 1-1: bulk timeout on ep3in Jun 6 19:06:11 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 An unrelated bug showed the same timeouts: - Epson Perfection 1260 (plustek), sane-backends-1.0.14, on Linux 2.6.7-rc2 and 2.4.25 with scanner.o(!) Reason: the epson backend tries to talk to this scanner There are some other reports about USB trouble but it's unclear if they are related. All these bug reports are newer than 6 weeks. So it's either the new SANE, kernel, libusb release or some other part of software that got changed recently. All but one reports are about the avision backend. Maybe the trouble is located there and the Epson 1670 problem has a different reason? Bye, Henning From misc@tomweissmann.org Wed Jun 9 16:48:51 2004 From: misc@tomweissmann.org (Tom Schutzer-Weissmann) Date: Wed, 9 Jun 2004 16:48:51 +0100 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. Message-ID: <20040609164851.1fcddb78@expensive> I had problems using the Epkowa libraries (libsane-epkowa) and the iscan frontend with my usb scanner in kernel 2.6. The scanner was closed after each operation. Once closed, nothing could be read from it, and I got lots of BULK TIMEOUTs, although there were no errors when the device was reopened. By modifying the code so that usb_reset() was always called before usb_release_interface() and usb_close(), I solved the problem. For libusb developers, my question is, should this be the case? There is nothing in the API docs to indicate that it's necessary - perhaps it is self-evident? Farideh - in the belief that you are a point of contact for Epson developers - could you make them aware of this issue, if they aren't already. I think this is relevant to SANE because although I had some success scanning with xsane and xscanimage, using the libsane-epson libraries, I still got timeouts if I closed, say, xsane, and then restarted it - for lack of a usb_reset() I believe. Apologies if this is old news. Tom SW From insane@piments.com Wed Jun 9 19:15:01 2004 From: insane@piments.com (insane@piments.com) Date: Wed, 09 Jun 2004 20:15:01 +0200 Subject: [sane-devel] Fwd: [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ In-Reply-To: References: Message-ID: Hi Henning, here's a copy of the email I sent to the maintainer of the fb630u backend. It gives the full debug output, the last lines where it blocks being the same as those I already posted on this list. I got no reply from Nathan so I have nothing more to contriute from him. As you can see communication seems to go quite well at first but then gets stuck in a loop with no apparent timeout. regards, Peter. ------- Forwarded message ------- From: peter@piments.com To: "Nathan Rutman" Subject: [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ Date: Sun, 23 May 2004 22:27:03 +0200 Hi, here is the full debug output from scanimage. The final line just repeats until I kill the process or unplug the scanner. This should give you a good idea of what is happening. I'm an active member of forums.gentoo.org and there seem to be quite a lot of posts with very similar pbs. So once I get it working will post the solution. Thanks again for any help or suggestions. Regards, Peter. bash-2.05b# !! SANE_DEBUG_CANON630U=255 scanimage -d canon630u [sanei_debug] Setting debug level of canon630u to 255. [canon630u] sane_init: version_code != 0, authorize != 0 [canon630u] sane_init: SANE Canon630u backend version 1.0.1 from sane-backends 1.0.14-cvs [canon630u] reading configure file canon630u.conf [canon630u] attach_matching_devices(usb 0x04a9 0x2204) [canon630u] attach_scanner: libusb:001:012 [canon630u] attach_scanner: opening libusb:001:012 [canon630u] CANON_open_device: `libusb:001:012' [canon630u] CANON_close_device: [canon630u] finished reading configure file [canon630u] sane_open [canon630u] sane_open: no devicename, opening first device [canon630u] CANON_open_device: `libusb:001:012' [canon630u] sane_control_option: handle=0x8056d60, opt=0, act=0, val=0xbfffe780, info=(nil) [canon630u] sane_control_option: handle=0x8056d60, opt=0, act=0, val=0xbfffe6e8, info=(nil) [canon630u] sane_get_option_descriptor: option = 0 [canon630u] sane_get_option_descriptor: option = 1 [canon630u] sane_get_option_descriptor: option = 2 [canon630u] sane_get_option_descriptor: option = 3 [canon630u] sane_get_option_descriptor: option = 4 [canon630u] sane_get_option_descriptor: option = 5 [canon630u] sane_get_option_descriptor: option = 6 [canon630u] sane_get_option_descriptor: option = 7 [canon630u] sane_control_option: handle=0x8056d60, opt=7, act=0, val=0x80544b8, info=(nil) [canon630u] sane_get_option_descriptor: option = 8 [canon630u] sane_control_option: handle=0x8056d60, opt=8, act=0, val=0x80544bc, info=(nil) [canon630u] sane_control_option: handle=0x8056d60, opt=5, act=0, val=0xbfffe6e4, info=(nil) [canon630u] sane_control_option: handle=0x8056d60, opt=6, act=0, val=0xbfffe6e4, info=(nil) [canon630u] sane_control_option: handle=0x8056d60, opt=5, act=0, val=0xbfffe77c, info=(nil) [canon630u] sane_get_option_descriptor: option = 7 [canon630u] sane_control_option: handle=0x8056d60, opt=7, act=1, val=0xbfffe778, info=0xbfffe774 [canon630u] sane_control_option: handle=0x8056d60, opt=6, act=0, val=0xbfffe77c, info=(nil) [canon630u] sane_get_option_descriptor: option = 8 [canon630u] sane_control_option: handle=0x8056d60, opt=8, act=1, val=0xbfffe778, info=0xbfffe774 [canon630u] sane_start [canon630u] CANON_set_scan_parameters: [canon630u] cal = 0 [canon630u] gray = 0 (ignored) [canon630u] res = 75 [canon630u] gain = 1 [canon630u] gamma = 1.599991 [canon630u] in 600dpi pixels: [canon630u] left = 0, top = 0 [canon630u] right = 5099, bottom = 6999 [canon630u] CANON_start_scan called [canon630u] init query: 4 [canon630u] write_byte(fd, 0x42, 0x06); [canon630u] write_byte(fd, 0x0b, 0x0d); [canon630u] write_byte(fd, 0x0c, 0x4c); [canon630u] write_byte(fd, 0x0d, 0x2f); [canon630u] read_byte(fd, 0x0b, &result); /* got 0d */ [canon630u] read_byte(fd, 0x0c, &result); /* got 4c */ [canon630u] read_byte(fd, 0x0d, &result); /* got 2f */ [canon630u] write_byte(fd, 0x70, 0x73); [canon630u] init post-reset: 4 [canon630u] Calibrating [canon630u] read_byte(fd, 0x69, &result); /* got 02 */ [canon630u] write_byte(fd, 0x42, 0x06); [canon630u] multi write 32 [canon630u] 0008:04[canon630u] write_byte(fd, 0x08, 0x04); [canon630u] 0009:1a[canon630u] write_byte(fd, 0x09, 0x1a); [canon630u] 000a:00[canon630u] write_byte(fd, 0x0a, 0x00); [canon630u] 000b:0d[canon630u] write_byte(fd, 0x0b, 0x0d); [canon630u] 000c:4c[canon630u] write_byte(fd, 0x0c, 0x4c); [canon630u] 000d:2f[canon630u] write_byte(fd, 0x0d, 0x2f); [canon630u] 000e:00[canon630u] write_byte(fd, 0x0e, 0x00); [canon630u] 000f:01[canon630u] write_byte(fd, 0x0f, 0x01); [canon630u] 0010:07[canon630u] write_byte(fd, 0x10, 0x07); [canon630u] 0011:04[canon630u] write_byte(fd, 0x11, 0x04); [canon630u] 0012:05[canon630u] write_byte(fd, 0x12, 0x05); [canon630u] 0013:06[canon630u] write_byte(fd, 0x13, 0x06); [canon630u] 0014:07[canon630u] write_byte(fd, 0x14, 0x07); [canon630u] 0015:00[canon630u] write_byte(fd, 0x15, 0x00); [canon630u] 0016:00[canon630u] write_byte(fd, 0x16, 0x00); [canon630u] 0017:00[canon630u] write_byte(fd, 0x17, 0x00); [canon630u] 0018:03[canon630u] write_byte(fd, 0x18, 0x03); [canon630u] 0019:00[canon630u] write_byte(fd, 0x19, 0x00); [canon630u] 001a:00[canon630u] write_byte(fd, 0x1a, 0x00); [canon630u] 001b:00[canon630u] write_byte(fd, 0x1b, 0x00); [canon630u] 001c:03[canon630u] write_byte(fd, 0x1c, 0x03); [canon630u] 001d:25[canon630u] write_byte(fd, 0x1d, 0x25); [canon630u] 001e:00[canon630u] write_byte(fd, 0x1e, 0x00); [canon630u] 001f:4b[canon630u] write_byte(fd, 0x1f, 0x4b); [canon630u] 0020:15[canon630u] write_byte(fd, 0x20, 0x15); [canon630u] 0021:e0[canon630u] write_byte(fd, 0x21, 0xe0); [canon630u] 0022:00[canon630u] write_byte(fd, 0x22, 0x00); [canon630u] 0023:4b[canon630u] write_byte(fd, 0x23, 0x4b); [canon630u] 0024:14[canon630u] write_byte(fd, 0x24, 0x14); [canon630u] 0025:37[canon630u] write_byte(fd, 0x25, 0x37); [canon630u] 0026:15[canon630u] write_byte(fd, 0x26, 0x15); [canon630u] 0027:00[canon630u] write_byte(fd, 0x27, 0x00); [canon630u] [canon630u] multi write 55 [canon630u] 0029:02[canon630u] write_byte(fd, 0x29, 0x02); [canon630u] 002a:00[canon630u] write_byte(fd, 0x2a, 0x00); [canon630u] 002b:00[canon630u] write_byte(fd, 0x2b, 0x00); [canon630u] 002c:03[canon630u] write_byte(fd, 0x2c, 0x03); [canon630u] 002d:ff[canon630u] write_byte(fd, 0x2d, 0xff); [canon630u] 002e:00[canon630u] write_byte(fd, 0x2e, 0x00); [canon630u] 002f:01[canon630u] write_byte(fd, 0x2f, 0x01); [canon630u] 0030:03[canon630u] write_byte(fd, 0x30, 0x03); [canon630u] 0031:ff[canon630u] write_byte(fd, 0x31, 0xff); [canon630u] 0032:00[canon630u] write_byte(fd, 0x32, 0x00); [canon630u] 0033:01[canon630u] write_byte(fd, 0x33, 0x01); [canon630u] 0034:03[canon630u] write_byte(fd, 0x34, 0x03); [canon630u] 0035:ff[canon630u] write_byte(fd, 0x35, 0xff); [canon630u] 0036:00[canon630u] write_byte(fd, 0x36, 0x00); [canon630u] 0037:01[canon630u] write_byte(fd, 0x37, 0x01); [canon630u] 0038:00[canon630u] write_byte(fd, 0x38, 0x00); [canon630u] 0039:00[canon630u] write_byte(fd, 0x39, 0x00); [canon630u] 003a:00[canon630u] write_byte(fd, 0x3a, 0x00); [canon630u] 003b:01[canon630u] write_byte(fd, 0x3b, 0x01); [canon630u] 003c:01[canon630u] write_byte(fd, 0x3c, 0x01); [canon630u] 003d:01[canon630u] write_byte(fd, 0x3d, 0x01); [canon630u] 003e:00[canon630u] write_byte(fd, 0x3e, 0x00); [canon630u] 003f:00[canon630u] write_byte(fd, 0x3f, 0x00); [canon630u] 0040:00[canon630u] write_byte(fd, 0x40, 0x00); [canon630u] 0041:00[canon630u] write_byte(fd, 0x41, 0x00); [canon630u] 0042:06[canon630u] write_byte(fd, 0x42, 0x06); [canon630u] 0043:1d[canon630u] write_byte(fd, 0x43, 0x1d); [canon630u] 0044:00[canon630u] write_byte(fd, 0x44, 0x00); [canon630u] 0045:13[canon630u] write_byte(fd, 0x45, 0x13); [canon630u] 0046:04[canon630u] write_byte(fd, 0x46, 0x04); [canon630u] 0047:1a[canon630u] write_byte(fd, 0x47, 0x1a); [canon630u] 0048:01[canon630u] write_byte(fd, 0x48, 0x01); [canon630u] 0049:04[canon630u] write_byte(fd, 0x49, 0x04); [canon630u] 004a:00[canon630u] write_byte(fd, 0x4a, 0x00); [canon630u] 004b:00[canon630u] write_byte(fd, 0x4b, 0x00); [canon630u] 004c:00[canon630u] write_byte(fd, 0x4c, 0x00); [canon630u] 004d:00[canon630u] write_byte(fd, 0x4d, 0x00); [canon630u] 004e:57[canon630u] write_byte(fd, 0x4e, 0x57); [canon630u] 004f:02[canon630u] write_byte(fd, 0x4f, 0x02); [canon630u] 0050:00[canon630u] write_byte(fd, 0x50, 0x00); [canon630u] 0051:3c[canon630u] write_byte(fd, 0x51, 0x3c); [canon630u] 0052:35[canon630u] write_byte(fd, 0x52, 0x35); [canon630u] 0053:94[canon630u] write_byte(fd, 0x53, 0x94); [canon630u] 0054:00[canon630u] write_byte(fd, 0x54, 0x00); [canon630u] 0055:10[canon630u] write_byte(fd, 0x55, 0x10); [canon630u] 0056:08[canon630u] write_byte(fd, 0x56, 0x08); [canon630u] 0057:3f[canon630u] write_byte(fd, 0x57, 0x3f); [canon630u] 0058:2b[canon630u] write_byte(fd, 0x58, 0x2b); [canon630u] 0059:91[canon630u] write_byte(fd, 0x59, 0x91); [canon630u] 005a:00[canon630u] write_byte(fd, 0x5a, 0x00); [canon630u] 005b:00[canon630u] write_byte(fd, 0x5b, 0x00); [canon630u] 005c:01[canon630u] write_byte(fd, 0x5c, 0x01); [canon630u] 005d:00[canon630u] write_byte(fd, 0x5d, 0x00); [canon630u] 005e:80[canon630u] write_byte(fd, 0x5e, 0x80); [canon630u] 005f:00[canon630u] write_byte(fd, 0x5f, 0x00); [canon630u] [canon630u] multi read 32 [canon630u] read_byte(fd, 0x08, &result); /* got 04 */ [canon630u] 0008:04[canon630u] read_byte(fd, 0x09, &result); /* got 1a */ [canon630u] 0009:1a[canon630u] read_byte(fd, 0x0a, &result); /* got 00 */ [canon630u] 000a:00[canon630u] read_byte(fd, 0x0b, &result); /* got 0d */ [canon630u] 000b:0d[canon630u] read_byte(fd, 0x0c, &result); /* got 4c */ [canon630u] 000c:4c[canon630u] read_byte(fd, 0x0d, &result); /* got 2f */ [canon630u] 000d:2f[canon630u] read_byte(fd, 0x0e, &result); /* got 00 */ [canon630u] 000e:00[canon630u] read_byte(fd, 0x0f, &result); /* got 01 */ [canon630u] 000f:01[canon630u] read_byte(fd, 0x10, &result); /* got 07 */ [canon630u] 0010:07[canon630u] read_byte(fd, 0x11, &result); /* got 04 */ [canon630u] 0011:04[canon630u] read_byte(fd, 0x12, &result); /* got 05 */ [canon630u] 0012:05[canon630u] read_byte(fd, 0x13, &result); /* got 06 */ [canon630u] 0013:06[canon630u] read_byte(fd, 0x14, &result); /* got 07 */ [canon630u] 0014:07[canon630u] read_byte(fd, 0x15, &result); /* got 00 */ [canon630u] 0015:00[canon630u] read_byte(fd, 0x16, &result); /* got 00 */ [canon630u] 0016:00[canon630u] read_byte(fd, 0x17, &result); /* got 00 */ [canon630u] 0017:00[canon630u] read_byte(fd, 0x18, &result); /* got 03 */ [canon630u] 0018:03[canon630u] read_byte(fd, 0x19, &result); /* got 00 */ [canon630u] 0019:00[canon630u] read_byte(fd, 0x1a, &result); /* got 00 */ [canon630u] 001a:00[canon630u] read_byte(fd, 0x1b, &result); /* got 00 */ [canon630u] 001b:00[canon630u] read_byte(fd, 0x1c, &result); /* got 03 */ [canon630u] 001c:03[canon630u] read_byte(fd, 0x1d, &result); /* got 25 */ [canon630u] 001d:25[canon630u] read_byte(fd, 0x1e, &result); /* got 00 */ [canon630u] 001e:00[canon630u] read_byte(fd, 0x1f, &result); /* got 4b */ [canon630u] 001f:4b[canon630u] read_byte(fd, 0x20, &result); /* got 15 */ [canon630u] 0020:15[canon630u] read_byte(fd, 0x21, &result); /* got e0 */ [canon630u] 0021:e0[canon630u] read_byte(fd, 0x22, &result); /* got 00 */ [canon630u] 0022:00[canon630u] read_byte(fd, 0x23, &result); /* got 4b */ [canon630u] 0023:4b[canon630u] read_byte(fd, 0x24, &result); /* got 14 */ [canon630u] 0024:14[canon630u] read_byte(fd, 0x25, &result); /* got 37 */ [canon630u] 0025:37[canon630u] read_byte(fd, 0x26, &result); /* got 15 */ [canon630u] 0026:15[canon630u] read_byte(fd, 0x27, &result); /* got 00 */ [canon630u] 0027:00[canon630u] [canon630u] multi read 55 [canon630u] read_byte(fd, 0x29, &result); /* got 02 */ [canon630u] 0029:02[canon630u] read_byte(fd, 0x2a, &result); /* got 00 */ [canon630u] 002a:00[canon630u] read_byte(fd, 0x2b, &result); /* got 00 */ [canon630u] 002b:00[canon630u] read_byte(fd, 0x2c, &result); /* got 03 */ [canon630u] 002c:03[canon630u] read_byte(fd, 0x2d, &result); /* got ff */ [canon630u] 002d:ff[canon630u] read_byte(fd, 0x2e, &result); /* got 00 */ [canon630u] 002e:00[canon630u] read_byte(fd, 0x2f, &result); /* got 01 */ [canon630u] 002f:01[canon630u] read_byte(fd, 0x30, &result); /* got 03 */ [canon630u] 0030:03[canon630u] read_byte(fd, 0x31, &result); /* got ff */ [canon630u] 0031:ff[canon630u] read_byte(fd, 0x32, &result); /* got 00 */ [canon630u] 0032:00[canon630u] read_byte(fd, 0x33, &result); /* got 01 */ [canon630u] 0033:01[canon630u] read_byte(fd, 0x34, &result); /* got 03 */ [canon630u] 0034:03[canon630u] read_byte(fd, 0x35, &result); /* got ff */ [canon630u] 0035:ff[canon630u] read_byte(fd, 0x36, &result); /* got 00 */ [canon630u] 0036:00[canon630u] read_byte(fd, 0x37, &result); /* got 01 */ [canon630u] 0037:01[canon630u] read_byte(fd, 0x38, &result); /* got 00 */ [canon630u] 0038:00[canon630u] read_byte(fd, 0x39, &result); /* got 00 */ [canon630u] 0039:00[canon630u] read_byte(fd, 0x3a, &result); /* got 00 */ [canon630u] 003a:00[canon630u] read_byte(fd, 0x3b, &result); /* got 01 */ [canon630u] 003b:01[canon630u] read_byte(fd, 0x3c, &result); /* got 01 */ [canon630u] 003c:01[canon630u] read_byte(fd, 0x3d, &result); /* got 01 */ [canon630u] 003d:01[canon630u] read_byte(fd, 0x3e, &result); /* got 00 */ [canon630u] 003e:00[canon630u] read_byte(fd, 0x3f, &result); /* got 00 */ [canon630u] 003f:00[canon630u] read_byte(fd, 0x40, &result); /* got 00 */ [canon630u] 0040:00[canon630u] read_byte(fd, 0x41, &result); /* got 00 */ [canon630u] 0041:00[canon630u] read_byte(fd, 0x42, &result); /* got 06 */ [canon630u] 0042:06[canon630u] read_byte(fd, 0x43, &result); /* got 1d */ [canon630u] 0043:1d[canon630u] read_byte(fd, 0x44, &result); /* got 00 */ [canon630u] 0044:00[canon630u] read_byte(fd, 0x45, &result); /* got 13 */ [canon630u] 0045:13[canon630u] read_byte(fd, 0x46, &result); /* got 04 */ [canon630u] 0046:04[canon630u] read_byte(fd, 0x47, &result); /* got 1a */ [canon630u] 0047:1a[canon630u] read_byte(fd, 0x48, &result); /* got 01 */ [canon630u] 0048:01[canon630u] read_byte(fd, 0x49, &result); /* got 04 */ [canon630u] 0049:04[canon630u] read_byte(fd, 0x4a, &result); /* got 00 */ [canon630u] 004a:00[canon630u] read_byte(fd, 0x4b, &result); /* got 00 */ [canon630u] 004b:00[canon630u] read_byte(fd, 0x4c, &result); /* got 00 */ [canon630u] 004c:00[canon630u] read_byte(fd, 0x4d, &result); /* got 00 */ [canon630u] 004d:00[canon630u] read_byte(fd, 0x4e, &result); /* got 57 */ [canon630u] 004e:57[canon630u] read_byte(fd, 0x4f, &result); /* got 02 */ [canon630u] 004f:02[canon630u] read_byte(fd, 0x50, &result); /* got 00 */ [canon630u] 0050:00[canon630u] read_byte(fd, 0x51, &result); /* got 3c */ [canon630u] 0051:3c[canon630u] read_byte(fd, 0x52, &result); /* got 35 */ [canon630u] 0052:35[canon630u] read_byte(fd, 0x53, &result); /* got 94 */ [canon630u] 0053:94[canon630u] read_byte(fd, 0x54, &result); /* got 00 */ [canon630u] 0054:00[canon630u] read_byte(fd, 0x55, &result); /* got 10 */ [canon630u] 0055:10[canon630u] read_byte(fd, 0x56, &result); /* got 08 */ [canon630u] 0056:08[canon630u] read_byte(fd, 0x57, &result); /* got 3f */ [canon630u] 0057:3f[canon630u] read_byte(fd, 0x58, &result); /* got 2b */ [canon630u] 0058:2b[canon630u] read_byte(fd, 0x59, &result); /* got 91 */ [canon630u] 0059:91[canon630u] read_byte(fd, 0x5a, &result); /* got 00 */ [canon630u] 005a:00[canon630u] read_byte(fd, 0x5b, &result); /* got 00 */ [canon630u] 005b:00[canon630u] read_byte(fd, 0x5c, &result); /* got 01 */ [canon630u] 005c:01[canon630u] read_byte(fd, 0x5d, &result); /* got 00 */ [canon630u] 005d:00[canon630u] read_byte(fd, 0x5e, &result); /* got 80 */ [canon630u] 005e:80[canon630u] read_byte(fd, 0x5f, &result); /* got 00 */ [canon630u] 005f:00[canon630u] [canon630u] write_byte(fd, 0x70, 0x73); [canon630u] write_byte(fd, 0x2c, 0x3f); [canon630u] write_byte(fd, 0x2d, 0xff); [canon630u] write_byte(fd, 0x2e, 0x00); [canon630u] write_byte(fd, 0x2f, 0x01); [canon630u] write_byte(fd, 0x30, 0x3f); [canon630u] write_byte(fd, 0x31, 0xff); [canon630u] write_byte(fd, 0x32, 0x00); [canon630u] write_byte(fd, 0x33, 0x01); [canon630u] write_byte(fd, 0x34, 0x3f); [canon630u] write_byte(fd, 0x35, 0xff); [canon630u] write_byte(fd, 0x36, 0x00); [canon630u] write_byte(fd, 0x37, 0x01); [canon630u] read_byte(fd, 0x02, &result); /* got 2d */ [canon630u] write_byte(fd, 0x07, 0x02); [canon630u] read_poll_flag... [canon630u] read_byte(fd, 0x02, &result); /* got 2c */ [canon630u] read_byte(fd, 0x02, &result); /* got 0e */ [canon630u] write_byte(fd, 0x07, 0x01); [canon630u] read_byte(fd, 0x02, &result); /* got 0c */ [canon630u] read_byte(fd, 0x02, &result); /* got 0c */ [canon630u] write_byte(fd, 0x07, 0x02); [canon630u] write_byte(fd, 0x03, 0x00); [canon630u] write_byte(fd, 0x04, 0x00); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] write_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x02); [canon630u] write_byte(fd, 0x04, 0x00); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] write_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x04); [canon630u] write_byte(fd, 0x04, 0x00); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] write_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x00); [canon630u] write_byte(fd, 0x04, 0x20); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] read_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x02); [canon630u] write_byte(fd, 0x04, 0x20); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] read_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x04); [canon630u] write_byte(fd, 0x04, 0x20); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] read_bulk(fd, 0x06, buf, 0x0400); [canon630u] read_byte(fd, 0x02, &result); /* got 0e */ [canon630u] write_byte(fd, 0x07, 0x01); [canon630u] read_byte(fd, 0x02, &result); /* got 0e */ [canon630u] read_byte(fd, 0x08, &result); /* got 04 */ [canon630u] write_byte(fd, 0x08, 0x04); [canon630u] read_byte(fd, 0x46, &result); /* got 04 */ [canon630u] write_byte(fd, 0x46, 0x3f); [canon630u] read_byte(fd, 0x47, &result); /* got 1a */ [canon630u] write_byte(fd, 0x47, 0xff); [canon630u] read_byte(fd, 0x48, &result); /* got 01 */ [canon630u] write_byte(fd, 0x48, 0x01); [canon630u] read_byte(fd, 0x49, &result); /* got 04 */ [canon630u] write_byte(fd, 0x49, 0x04); [canon630u] read_byte(fd, 0x4a, &result); /* got 00 */ [canon630u] write_byte(fd, 0x4a, 0x00); [canon630u] read_byte(fd, 0x4b, &result); /* got 00 */ [canon630u] write_byte(fd, 0x4b, 0xc8); [canon630u] read_byte(fd, 0x4e, &result); /* got 57 */ [canon630u] write_byte(fd, 0x4e, 0x04); [canon630u] read_byte(fd, 0x4f, &result); /* got 02 */ [canon630u] write_byte(fd, 0x4f, 0x02); [canon630u] read_byte(fd, 0x50, &result); /* got 00 */ [canon630u] write_byte(fd, 0x50, 0x00); [canon630u] write_byte(fd, 0x57, 0x1f); [canon630u] write_byte(fd, 0x07, 0x08); [canon630u] write_byte(fd, 0x07, 0x00); [canon630u] write_byte(fd, 0x07, 0x03); [canon630u] waiting... [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ ....................... this continues until I cntl-C or kill the process. -- Using M2, Opera's e-mail client: on Gentoo Linux From henning@meier-geinitz.de Wed Jun 9 21:33:11 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 22:33:11 +0200 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <20040609164851.1fcddb78@expensive> References: <20040609164851.1fcddb78@expensive> Message-ID: <20040609203310.GP7920@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 04:48:51PM +0100, Tom Schutzer-Weissmann wrote: > I had problems using the Epkowa libraries (libsane-epkowa) and the > iscan frontend with my usb scanner in kernel 2.6. > The scanner was closed after each operation. Once closed, nothing > could be read from it, and I got lots of BULK TIMEOUTs, although > there were no errors when the device was reopened. > > By modifying the code so that usb_reset() was always called before > usb_release_interface() and usb_close(), I solved the problem. Doesn't usb_reset() cause a renumeration and therefore the device gets a new device file? I guess this isn't the default for closing USB devices. Maybe the usb_reset just hides a bug in the SANE backend, libusb or the kernel. Bye, Henning From olaf@epkowa.co.jp Thu Jun 10 03:26:55 2004 From: olaf@epkowa.co.jp (Olaf Meeuwissen) Date: Thu, 10 Jun 2004 11:26:55 +0900 Subject: [sane-devel] Re: How to configure sane, xsane, etc. In-Reply-To: <20040609094922.GN7920@meier-geinitz.de> (Henning Meier-Geinitz's message of "Wed, 9 Jun 2004 11:49:22 +0200") References: <20040609094922.GN7920@meier-geinitz.de> Message-ID: <87y8mw87ww.fsf@zen.epkowa.co.jp> Henning Meier-Geinitz writes: > On Wed, Jun 09, 2004 at 10:08:32AM +0200, Fran=E7ois Patte wrote: > >> and to wait about 10/15 minutes for the research of >> peripherics.... > > That shouldn't happen. Which version of sane do you use > (scanimage --version)? The scan takes about 1 to5 seconds at least > with newer versions of SANE. As a workaround, you can disable > everything but "coolscan" in /etc/sane.d/dll.conf. That should do the trick, but if the net backend is enabled, you could in principle get pretty long delays depending on the settings in your net.conf (and your network latency). However, 10 to 15 minutes is a bit too long, if you ask me. --=20 Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From olaf@epkowa.co.jp Thu Jun 10 05:02:21 2004 From: olaf@epkowa.co.jp (Olaf Meeuwissen) Date: Thu, 10 Jun 2004 13:02:21 +0900 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <20040609164851.1fcddb78@expensive> (Tom Schutzer-Weissmann's message of "Wed, 9 Jun 2004 16:48:51 +0100") References: <20040609164851.1fcddb78@expensive> Message-ID: <87u0xk83hu.fsf@zen.epkowa.co.jp> Hi Tom, I am the lead developer of iscan and the sane-epkowa backend that comes with it. Farideh has also contacted me about your issue, but I think that my reply is better sent to sane-devel (at least it'll be archived :-). Tom Schutzer-Weissmann writes: > I had problems using the Epkowa libraries (libsane-epkowa) and the > iscan frontend with my usb scanner in kernel 2.6. > > The scanner was closed after each operation. Once closed, nothing > could be read from it, and I got lots of BULK TIMEOUTs, although there > were no errors when the device was reopened. Sorry to say, but I can't reproduce your problem. I've tried with a GT-8200 (aka Perfection 1650) on SuSE 9.1 and Debian (testing). FWIW, the version of relevant packages: SuSE Debian iscan 1.8.1-0.redhat.8.0 1.8.1-0.redhat.8.0 sane 1.0.13-73 -- libsane -- 1.0.14-2 libusb 0.1.8-31 -- libusb-0.1-4 -- 0.1.8-11 kernel-default 2.6.4-52 -- kernel-image-2.6.6-1-686 -- 2.6.6-1 with the note that I compiled iscan from sources on Debian. Can you give more information about your setup? Things like scanner and distribution used as well as version of relevant software might help me in reproducing your problem. When you say that "Once closed, nothing could be read ...", do you mean the calls to sanei_usb_close? I've looked at the debugging USB output and don't see any bulk timeouts. My system logs also show nothing. > By modifying the code so that usb_reset() was always called before > usb_release_interface() and usb_close(), I solved the problem. The epkowa backend does not call the usb_* functions directly, so I presume you have been mucking around in sanei_usb, right? This would seem to indicate that you think the problem is not specific to the epkowa backend. I see below that you also get BULK TIMEOUTs with the epson backend. Both backends share a lot of code, so this is not an indication that your problem is not backend specific. Has anyone seen this with other backends? > For libusb developers, my question is, should this be the case? There > is nothing in the API docs to indicate that it's necessary - perhaps > it is self-evident? > > Farideh - in the belief that you are a point of contact for Epson > developers - could you make them aware of this issue, if they aren't > already. I read sane-devel ;-) > I think this is relevant to SANE because although I had some success > scanning with xsane and xscanimage, using the libsane-epson libraries, > I still got timeouts if I closed, say, xsane, and then restarted it - > for lack of a usb_reset() I believe. I have no problems closing iscan and restarting it (for the setups listed above). > Apologies if this is old news. Tom SW Hope this helps, -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From keith@claytons.org Thu Jun 10 05:16:13 2004 From: keith@claytons.org (Keith Clayton) Date: Wed, 09 Jun 2004 21:16:13 -0700 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040608160140.GE7920@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> <20040608154042.GB7920@meier-geinitz.de> <1086710152.643.7.camel@yoda> <20040608160140.GE7920@meier-geinitz.de> Message-ID: <1086840970.8298.19.camel@yoda> Very right . . must have had a typo in the command line. I re-did my tests. First test: used xsane to do a remote full scan and quit. Everything worked fine. gzipped log: xsane_regscan_quit_log.txt.gz 2nd test: used xsane to do a remote preview scan then attempt a regular scan once the preview has completed and the scanner head returned to starting position. preview scan is fine, regular scan dies. xsane bails completely. saned is left running. scanner is inaccesible even from host box and needs to be power cycled. One interesting thing I recognized in the process table of the host box is that there where *2* saned processes running. Looks like the preview scan in xsane uses the saned process started with SANE_DEBUG_PLUSTEK=255 saned -d255 but then the subsequent regular scan attempt forks the saned process so there are 2 saned -d255 processing running and then it dies. Note: saned is disabled in xinetd so its not getting started that way. gzipped log: xsane_previewscan_regscan_die_log.txt.gz Note in the case of the first test, when I quit, the single instance of saned running is closed out. Don't know if this sheds any light on the situation or not. Hope my description is clear enough. Sorry took me a couple of days to get back on this. Lots of life the past couple of days Cheers, Keith On Tue, 2004-06-08 at 18:01 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Tue, Jun 08, 2004 at 08:55:55AM -0700, Keith Clayton wrote: > > Did use SANE_DEBUG_PLUSTEK=255 when starting saned. Cmd line was > > > > SANE_DEBUG_PLUSTEK=255 saned -d255 1>&2 2>remote_scan_quit.log > > > > > > So in that regard, was quite strange to not see any closing of the > > scanner's fd. > > Your first two logs contained the plustek messages. However, the log > you have just sent didn't contain any plustek messages. So maybe the > command line had a typo? > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request@lists.alioth.debian.org From henning@meier-geinitz.de Thu Jun 10 09:10:36 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 10 Jun 2004 10:10:36 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086840970.8298.19.camel@yoda> References: <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> <20040608154042.GB7920@meier-geinitz.de> <1086710152.643.7.camel@yoda> <20040608160140.GE7920@meier-geinitz.de> <1086840970.8298.19.camel@yoda> Message-ID: <20040610081036.GC1513@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 09:16:13PM -0700, Keith Clayton wrote: > I re-did my tests. Nice. But it looks like you forgot to attach the results :-) > 2nd test: used xsane to do a remote preview scan then attempt a regular > scan once the preview has completed and the scanner head returned to > starting position. preview scan is fine, regular scan dies. xsane > bails completely. saned is left running. scanner is inaccesible even > from host box and needs to be power cycled. One interesting thing I > recognized in the process table of the host box is that there where *2* > saned processes running. Looks like the preview scan in xsane uses the > saned process started with SANE_DEBUG_PLUSTEK=255 saned -d255 but then > the subsequent regular scan attempt forks the saned process so there are > 2 saned -d255 processing running and then it dies. Note: saned is > disabled in xinetd so its not getting started that way. The plustek backend uses fork() (or rather sanei_thread_begin() ) to start a reader process after the start of the scan. So you get two processes everytime a scan is ongoing. So if you see two saned processes that just means that the plustek backend is still scanning (or trying to scan). Bye, Henning From henning@meier-geinitz.de Thu Jun 10 09:35:14 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 10 Jun 2004 10:35:14 +0200 Subject: [sane-devel] Fwd: [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ In-Reply-To: References: Message-ID: <20040610083514.GA1580@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 08:15:01PM +0200, insane@piments.com wrote: > As you can see communication seems to go quite well at first but then gets > stuck in a loop with no apparent timeout. I have had a quick look at the sourcecode and think the loop happens at backend/canon630u-common.c, line 374 ff. The backend asks the scanner how many scan data it can provide. The scanner say "0". The backend tries for 60 seconds but the scanner still doesn't have any scan data. So it should time out after 60 seconds. But that's just my guess. However, I don't know why there is no scan data. Bye, Henning From keith@claytons.org Thu Jun 10 05:18:11 2004 From: keith@claytons.org (Keith Clayton) Date: Wed, 09 Jun 2004 21:18:11 -0700 Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) Message-ID: <1086841087.8304.22.camel@yoda> --=-LXWa6OL6bN8i+5klQC12 Content-Type: text/plain Content-Transfer-Encoding: 7bit Hate when I do that . . here's the xsane logs described in my previous email --=-LXWa6OL6bN8i+5klQC12 Content-Disposition: attachment; filename=xsane_previewscan_regscan_die_log.txt.gz Content-Type: application/x-gzip; name=xsane_previewscan_regscan_die_log.txt.gz Content-Transfer-Encoding: base64 H4sICPPZx0AAA3hzYW5lX3ByZXZpZXdzY2FuX3JlZ3NjYW5fZGllX2xvZy50eHQA7F17c9s4kv9/ PwWmpuoiz0kyX3rWKHWO7WR844cqciaTSqW8FAnZ3FCklqTs6D79dQMgRfAlKrEzzg5dTiwR3T80 Go3uBkiAH0PTo/YnsjQdb0zCyAwix7slNp2vb8nStylpufSeukTr9Q7+8VGijoIN0kY+uaURWflB RBZ+QEIa3DsWJf9E4hekBYWmbQeOt/CzCB+VTyT0rc/A3jog6xDhzqb3/XKyhem41B6TI0CkYQjf l467IZ4fkXC9QhmoTeYbsgr8yLd8N4ukFlZoFJHRCCn9FZIWlM8dz0YQaD5rer/Xz8kNZK4TRtTL QzyYDtM0aszyvSjwXfzrUStyfC8hZn9I6+h1B6qjq/9G7RyQReAvWVFnbkJjPDskalfpqgYJqGlv Em7rjlqfb+78MBoT07JQYaCbgC79iBJ+WR1pXbU/BG69kC1FTJyQKfrs8ub86mr66uj4d/gewPd+ cqEQw/Ut02UQnrmkY7LxbbMGYSs8IC3W1JPL2cGzYUtrxPZp6L2IyJ15T6FDlpSgqRMz5OCF/P6K etjz0NsLBwwADHpMDmlkHWJ52KX/Xjv3hZyWiXUhfzUzaV36MBysO1ZOoItsJwDD8oPNQX2RGF0X LxULs6UFI/eA4Z8/v6hNmUKvz7QH/PUdZcOKelFI/AWJ7miqSsKp0aCJSdgYJUjFO5WgOYRtAp5h jxpN7pFoiPo+m4L+5x64ENI6Pjt5i+PGxIEN/uLOjIgZULKiwdKJ0F+BC1mHlJvMHjXOji5PwVOj sw27zG+mhFiuoSVzSqhnuX4IlTgemQfoLSJsmgnOi4R3/tq192mj+2BuQGeAG66o5SwcDgzaddCN LVesdhu92rL7ZB0bD1lwpZF1h4YrPJNlhrQTUi8E33pPn0SAEAZhx3IdMKxu6C+p7aM/7y6cYFkf ZOt01dpMKUddzCMc/G1gemhUzJWBHQqTKHT0jufkGCsL0VR/P738cHX5P0V4EHWR+iYAN0RRpnSU ExfLiW+hB8UXonIy54ZlIp/IjEapxISnJDBgVy6YOf2MYkGC0v3HR3HhE5mKEhEgyR9K1xh0VLVN VpDjIG9R/EwBvPw5xuiwgfZKAPGuWQdsOLMe+lXmeg1txeH84ER35PxiNNTVQ+1QB0lwZLybvSJo Qx4NQplR+pbBpCY4cz7UiUcpyAtOxKUmaCp68JmJhOMMT4d8XIfzT+QepPaDztkJG/SgdXttRfA1 Ry7w+R8cXxkKp0u7rCdj3baUL8rglX5A3l2r2qHaP9QMdk1RBwcZXi4KpyecJEMhaj+Ev4dALHSU IfKzFwSX68yBZzyfz8e2bWdoHu4ouFsoQzeBgQBovfVyTgOmEWBgV2P1spIMxNL8DC5vDTDMfW/8 NevjAAJ/GA8RsMFDtOlDgMcWHEKNhzlpMsAwOh00JNOFLBZgMcYL37oh6F8gNmN5mG2TGSzXqzZx rxaLK+/Us+GjuVzBt8rq0DbNdQR5fcQTTWxFUVd9RefkuoqEznLlbnbD5zmdBVPGAzgdCNAi1lix GPM16wKedXk+cWxqEnPuw2XoyGLRPZzLADLysWDLLKYtZMRsPx4o1cOktiGjmiubeXl1fTrO9AYY aGguaBszSCdCQbnF4uQJL4CLzKDwH+bskZC5l/U83ADBEpICpscXAWXhkc938iriP5Ikbaaoi3ez a65lM4rABWEAQPvnTSxGEaMDBOngvKidjBiRJMd5Q7fbrev/cibj0S+xEFxHkuwpQqgkTVzuYbMm yAcd83aoVshr7h1/HTL9QugPNpXsIfh+cNg4IiHSLIi5iMBXfPnyBezMgvRLgYQ8NOeu6N0FNSPw LRIIlyAe1ERXlHTxCbV8GztTkL0sGvyFLgPTTsdnWRvI4kPoQ3GW1PQwhRJERZIIdrVXKUcBf0aM uDKIXmAOKHcnhNwYdLv2In+NRtZm1hoTCmX6WddGoD6M4TcswS1UXuwciVqtvJiuQu4SAwGnHz1Q 8zMfpUvzlvJFFLD9kDn2DF/r/dHby7PLN2NkCOgLpnQHUqsAQgCBJAsAWFL3008/HVRKEJsmzMCX wIouGacVZgWTaC+IBg3+k1RblKAqB/hQC+BDlS2wNkCjQ8jJYKLi0LCoumhl1pBXUJUD7JJXUO2S 16O3Js4uCkWFwhqiCqpygF2iCqr65srX5XgKjUYDE01nLlLYMAqcFXl8eyUdVYxgjLfzteNGwFnL PGd3Jrb3A0DsMrGYtKTf6yKlSEu6pS5SirR+/0So1HsaRHxIxyZWK1IUKpGjXcZAO+wpQ72X3CG4 8UOYYUZ+gEsuZhDK5mWbUQ2fZGF2cWy6J0C9w1unSetLijZousxuI1nAAPJGnD/tFhL4j1OM1TqV iXd5lfCzs1oh+8Od72bHJy0MyMiSFqdaaxnq2vJAsuNAxy5AQ9VS/VzU+ZDP2r5XGJyxhteIWq3G mKxKYBgilhnwWRxY4tqN4iU/JvbDnSN3eZU47xnxbl0mtLs0GdCVa1qx4701IfG6N901xeRyjdPP dQCFWVVWCxtQ+4YhkV3eKKYsQrkNKPU4zg6ULWURzhxaI8TZgZNQ7he5TPtfcCFWoU0XJnbxrblc mkKXu8cuKOINY4h/1G614cUMpZpLw+0C2zKUKVASbhdcwlAsnLnZCy1h2MvvUw/DErmeHpGWBzBT XhwvSEN27m6yGUGc0sddOKcwJ3Rwugjz3eyK8jbNiFgAzGDFyQWXY7cBcDoUt1obCV19beCCATgc CxoS0tRaUie/iFa8VlC1rlKynJDIHa9v4Hr4y9yiw65ehJ5AF2lCzvEgoNp8BsPXL3lByCfW2RXG HUs5fM2AtFAoyGS+DBaLxZz2lDYYjOMeHEitYY2Q1lbHqfJ0I8k4305cbTg7EfY+lpuNd7Fd4t8H XVampIrEnDZmU3thqjCeeotCmIHnC/nsckw2NM0pJTPZwlReQKHQ81Nl2yDdJTnGJGByeXKMSUTK MibZXdjNMUIGffOFJBpQMkWb8qKQJ7k3mzF4/VQZJK9liFhUgohFZYiQm5chYlEJIhaVIYJvJyJ+ IptUxlx1XJopQ7+bMBZgolXgek8xpigtwowZCzATVz5GR67kUEV5rpThxswFvOamvLRT9JMqh3EP I/YGbxvz0Z0ey0fptbhuN31T5hhnivH9IFxDnesdtoaq1CFS6xAN6hD1Hg1JfzSiWq2rpSfj0VRQ C6n/aMqsQ6TUIlo8GtHj6UmrIDIUBYhURanq4ISoylTqEfWGQKRVKzMhGtYhGtUgqhwICVGVxhOi KqPTF6gCpVfZd4KoX0lkzLE6GHZpU3nNp20iLYvIS3HzEVQO//rp1OMPdkeJnJ1MEOzVsE2m/L6S uKQqr2Wv6vg3J8x1svvGXyoLx2ICyb5ph2ndcjIIHvyWFvmv+H4W1DsmXJZOrv6T+P5vaAUOz4ZR Dy8l+l95rV1ZtBt8WAD4W7rW5nprd9SCBO/90WtWP/sxzAwIX+k/h1j4Z+vqcqK0IQufSDAzfi8A SQCnDQHyNvyofOmNPpEJw03Rvj19A0WKxouG6SKcBVxeXRNb6CnfZXzKyR54gHTydBXKE3GO3Ztz bHVEWsvw8wRrSUt7fnQx7cyuj67fzbatzsg4O72+Prt8g4hns+vTt7OWrLi4/Pq3U3JxNjsmZ4dX 6eQuvibuMTFArMxQMeU2DPxf9k+p5Rl8eoFNUtj9T2hqOpc/vPOX9PCz5ZqbyPcOu3iv5ZBpojOl wYLH9xtV6yk30zs/8ruW6f6a6dEZjWYwp5maAVQC8oWtdNt+Ib+dTM/GZNiVtfIL+ROuT1ScKiDF JE/wISG4cDz4/AG/SBSYfE+dL9Sd4Wxm0h+1yTlkyJCvw+cqyoGypRwopHV08r9poV++JFDS4bRp ASXM12vXJbOIrtgtohmk5+gqGJOw1AwD0s6c/6OtaUChMw6AStNV/jgFHchaQ5XiEpG1dlk/hnKW 9QsT/5x6t9HdRFUGgz5v0FuYcRz7rh9M1FzVIVQNVfYHPWY2ffROGn4awCdTl/U1PSGTXq8/ROnU nqUcFBRrCi8Gj33QZquFBOuYsBrwa6gF9H6iy1pwXerFIruyyG3y78jymMrvFuxDxtbe0Oji+Pz3 E+fesWmQMbQzL6K3wuqvHTD4IzbAsS9Ia2tjbYYwMfBzRufi7skbTLqn7y9O1tHmeGO59Nx/kAiP 10FAvYggEhHCQDUMMtvpF1fXV287AjocE8Blim/jp5uTd9cfWJSQLet1bCpoIn1QB3giYygcoMq/ xv7QkFind5tXm4iGkPIDa7YITUQU9XuQj/b0oURy7Uemy/knpAfTYU1XBn0Z5XyijaB/LZ8uFqy7 NRV6MgRbpVmrm5rrkJ47Swc7gXGh4JQLPhLtWMTN2u1X2EJzehhcgE8KsGf7CroJ8wu7MFtRak+U 7ggvbnU5MfpphbCOKe0PHBc9+KTiEyDGcML1jmqHj9JTBmgEN69fv8ehBbOql9iWTNTDidQtjY7N lewcZ3wtiD36ESxzKyIiTo0J88hSs3G5Awq2Tpqgkz5kTjqdx7jmbchmzUWRyQ7u2X11SSYhbhj5 KxSvqAyvg39sHYhlJByvKzP4nB2uSJuvgC8ZjcWazYS8LGxEOsqwJwBAfzfxumOLLzRZix6kW+rB EzybqJWTbR8FAy/urwPcBiFEfbF9wFIWnj3P3SFyFpki4gGBOx82YefLobgxw5sYyqgvO6rjO7Qb 96PyqS2WyNVc9Ixp1Bo0Wg0avZSmcCUhs6xQpsytdgIarQMP933M1kzDT9CrxhNg9hrMBrPBbDAb zK/C7P8gcjaYDWaD2WA2+WeD2WDuhZnMFHE9nm9QseCKvxQTSjH1DbvNjPj5OZey+yHG198P+Sac H8XoG8wG8zljNuO6wWwwG8xmgabBbDAbzAaz8Z8NZoPZ2HyD2WA2Nt9gNpgNZoPZ+M8Gs8FsbL7B bDAbzL8J5iAhYxs8bvDQkrF4dIO9CUHVhgMGi0d/ZXc7MJ6SowTkLRDSoQJ/5520urbXTtqv2sFa ckdWUIntZIYaUynDb9/nKjfr3QxLk92s8WM/37LTtWJzFdose7vJhOjFHIG/OvMWfnaLE+4yPMNj PnOF0+k5bvPT0njn0yPcKzdMS/WK0amatAl1Hji3d5EHYw53NbP3geDZ3gV7pkK+8+3Uu8+JNjPv abFs9gNu9ko2nmY6p7JZv+DTVvcOfWAby7BffkpvUhOPYS3NFb6kxYwIO3tAs0zdKiFTt2S6Uk6m pcgMmSzZhQaeJLcNLd5TrGolm4qVeM9uAcWuXcXfd9Dwze6okHN2kLCX6bNv3i5vZLdVZhBVhqiU IqpbRKGSUdrS37PTlTq43TbgsULa/CYrc/QEykw3DyVORPFXK0kU+2ERjw9D8MI1ttd1SgPcGCuG LEkfInB2cUqgzrfXhTGO7UetF34xTkov/0ng8HU+NLgR3LESSQu4PlP7oJRynLzJKfJBhUcnvI7W wFCVUZ/MsWVp7vl6wVqvK0NtJJ/4IUYbeAE8pLdo2+fNiZ86VEAqhbzBJ+IUpuSI2bQ58aIrcH+O B6Mtbf4F+3fvabx9d5jZvtvT4DvbyD7RJJB9N/JqyUZeZZju7ZKdvGXdu90IyhTPX46Fh7QXvTbD 9kUSlU2OuDXR6AYSFgxXeHiXdzN3fXZKibShOksqzC+/TzakLpjZzSK3D1UqlK03EVC0E3vz7fQ4 SQkxv7Gf5CHT9EbYrB2hzeNx4SmSz6fT2dWlyH2W+PKftLGdXmMvftQP8QlenrCys9zJcEz6Yn9+ G8Z5Ljq+hcF15NkzzCTYqW6SkXcIlrMnlzPn3vIux1M2UuSEfM3JGlJ92TM8IDsNQtwgzn2fWkqM QqHfVtrJv74+1Av+1lABsxECQ0GqD76/+jA9ms1qaV4dE22reUnx2JQx+fNPAs5YMYim4Af4yq8Q xSTqgpVpWDywiT4gSp9ICCogqH1G1SOKRdQB+6wgd+qLGn9gvxKCBgiaicBQYiT/W8RAGWyi6IJL X5DFoghBB4R0YfqzVG+pDAYgZMrRY2nE1Alr/pBdMkTZSMUWSQg91ANlGjAgH2WEC8aqslZAXDUM MjLKZehzGfQ+UYdkbjHePtGGxBgS0UNCsjKEQaYVeupzHT2cxceBirnBuMxW4t+UrcD3wXe2FfhN f2Z/HstW1Pi3tq0IhJytFCBsbWVL8lW2Uvhbz+KztrIvwq+dTt4LfXVC8R3ziSphn93pJVJkkdON 0q0t25iAL8SzyBt8G2Yu39fZrEDNX7dKrtvZ6wL+arEAd1FQAT8wJ399VHLdzF7f3cJ4Tl6cM1z6 +XRBHKefnmFbGR1nl4vqnbD1JLPh3MlZavqQLVXRNbWSOn3QFlJr1WdtqYra09LSSuC7D9wyTYlh lj9wC0YRO3BLtWhz4NaTH7jFLU6cuKXtceLWb87tnURZcuSW9iRHbrHAkD5yS5OP3JIPzZKP3OoZ SrZ0e+qWOugZUql04JZh9HpqP8OOx23pX3Xcli4ft6V8+3FbfLVnDH/5VE/txS+YSudwuMY4hQkf cUD3zNBmKO0wWyHU9oreOvm1hgtzdeI/eK5v2hmLS62hopFhuJLKk1VVEpfnt2/aAlqsQhIlO9Cz BOouAk0myDWh0KnHxWJ5hEUPaXQUzrLegsJCXBo/WS9XZE4X+EaWQExN2cyvLGOOk1SRMfNZxXef XZkmzid6Gn5msys9zpjVp86YDZ6vx+UFsysQjpeNlD1nV0rNjBlkwDmuhVxzpvWC2dX8qWZXM3O5 cukHdiocOw201VPIT+CVMP4/zNZLXJ2TbPAYTIsv6uAKxAtxvbNyrG5gPrxIh3Hy52RogGf6MOkN jTax6QoC5VAyXW6l7N0JmAl5/kM6CwJHebJyuskp8OgupaErCDZpAilZeRfSQIIAT15Uvikpv2Sv Bb1aMM+0XqCPUfs9aYUZPfmUBikKXVfSebn9kAoHpCgkMAqWI4UxBShOIkhFBU6QjwyAkoLgRNJ9 KbG2TVIEmRtS9sMfkHjaW5y8IAxCNFboayhLwTRyIl7Okz1zUhRf+yxXY8V6vhi7JekP6T6aEOA8 fiNCvg3xslUu+Z7FLzfS+ZtzC4IP8rFg1cJWZYPQWYiYR/em4+LJA2feydujC6kK9uoHJyRmTFNZ B48CeDcFX14kv8cgEVatISyaU+62YO2q6jW+Pp7oehRe+0pN7yd8YW+XVpRd3I6CjbhjgkGTDNXh kN8p4cu44uUsKWS2bM5oO5yF3SJiLHn0DEEGs1yWh4C9kEob6IIRrvH3j+e5HgK/lPa7qfW59F9/ BClo03+PrdZe39Aatf64w8LQS3Td9N+3qFVP7qs3av0Rh4U61PSm/x4/WsAscj+tJhwlSi1D3KXT Xs+oq9JapN+eLQ7UavNJyvds6UCrbTyFpH+7sT8w+k2m+AQJuDpqMsUfeFgYoxIH1PTfN2WKfaPJ FH/gYaHpgyZTfIIEXFX2TRW3LGVq3Yn51zVa9J+q1E5L69E+wirmLmP9Wlt9VuYndFpn+GRVqjQL i0+RLg6+48Lif17Uair6ThU9/YjctaZi1DHqr1RBbozpQ2VQOca2BHu6Ln2oqnUVVY82m1L0e9/v Dt4ztdYfoaK/fETpw30DesLxF6qpnujPy0p2+4RRfZdQg3TvbPhRXaehadWuMyHY13UaWr+2nmrR Ztd+Bv1m7e7H9JnCsobfb+3uP0+7TUV/TTDfT8zHCP2apu5YjX3MiLCtrWSMlYqzS62apil1fWQ9 2m9fSNKG/er1uS3Bvq0d9msvmxXTPoPxwCdzumY0jvrHnToYSk9t+q+p6G9o+tpgsHdESFjKIkIZ 5s6IMBhqj5RWfEOnZENPlVCPGWi10Q61JgT7qlVXarRAtLaQ9hmMBx5oh8Pvd9v9P8/bNBU9kxWy p89o+uqO5xua2wvcUSv7LpElHCVtLUPc1dShUns1sBbpt0cko1/dq0n5ni01BrX7tJD0mQ76/2/v 6pvbtpn8V+H9c3U7dkKA7566M2mc9PFdXjxx+rSdzjM+RqITXRRJjyTn5T79AZRMioSgXdgSASmb SRtb+mEXBBaLXRC7u7ttL0nY+pGmg9yHDGschuS2EyOn1ntX1w9YApx4dDbWh2RNsEBzFkoahRg5 xMi6/klN7Zl0s0rQ0IOeM0OrAwzS7j2FhG9+T1MDTLVmwtHvaXDYtrMaxmSHESPnGVnXmgHLEFbb 1jRKxU2nUVDdcWf+nBEUMXARWqOisHa3HnYXa60VlAhQ8G7NHzEy8FXF5KZ4YcZg276qH5g6Vfd3 IQ9v/r53RvYPBTgUgr1NZVxz01rGmO7sz/wxjk+VgcPa3UzTCFJd0X1Pv2IDQcdglaxUvLvXFI5K KzFyn5F9P87H2MNb0yg+ZJ6juuPO/DkjKGLg8KYvCmt36+GQw8/J4XdcIrnByQIK297j02wvLhY5 On/EaI/9OD8F7opt1Y+ruOksY1R3Hm4M+Sn6XhoOa3ePyzLAGKoApu5VluGNARS2rXpZRpcLiJHz jKy7V8JKRRgF29IoNTdd3IauO2DcRsbROxoOu4UoFRZt1ig1gDQKMepGo3AWozUKDtu+KexzRIYW 8nqIEczIuh/DOTO9blU30ac82KsjRFCjcIY25nFYq14PT+PNzmQN2I/5I0a7E/00Rjv8OKyaLaPD cxTaTJ1nZH1HZBHr8F5lzU13KIPqzv7Mn3ge9EsJHNbuEWIUR5s1SgSVInFr/vaBEagjohifdBKF VSPqTZPx0dZDjJxTxh1kVDA9U6xaaDMq3C/vTcrQaW9QULsuXJYBB68VwPTFle+jT89wWCXY2Dg1 M724IkbOqc7d3wvMGHnGeyAozkhkB3dejBNj+oBzq6EI30PB+5AYqOVgbX9zCuEaYByszdAphHFY JVjbOGEkbebEyDnVufvNnPtdvjOuuGnvbmO64878OSMoYuDwJ0sorOVg7RDIE1IBSFC6i6EO8SlW UFglhto41R25B8TIPWW8+2DtoMP4lpqb1jLGdGd/5k88T4K3ujBYy8Ha4eb5qwHGwdoheqBwWCVY O6SaF8TIeUb2/Tg/7lKjVNy0wdqa7sCveRL06zAcdgvRBD7w6q8GkEYhRt1oFO7j3xvjsO1oApZ0 WK6O/DjnGVn3eniAubG2LYmsuem0Pqo77syfM4IiBg59VonDWg7WToGzygpAgnLgjEAdmaX4I1QU tu0wc7/LpE20a7vOyPquHUCpeNYoVOC4SkMRXnz4wyoM1O6uEwLBjjWAlt6BMwIFP8THieKw7V0n SRAWDu063w0j67tOBuX3UKQqA1KG6ChCj5rhsz6goJZDtEPgKLQCmKaRSSP8eRYKqwT0BlSVlxg5 z8j6q6TQjyl55h4IyuExsm418Mi0znLVQrcfaiiC22GET2+BgVqORY+gWPRo/VE6KBFRZBBQjcEq AdXc1JAkq4EYOac6d38BJYi6fF1ccdNpFFR33Jk/ZwQlqIsDwxoVhbUckJ5CAekpKWOnJZJnGT5v JgqrRP5nlDdzDwTl8BhZd3hYkHb4urjmprOMUd15uDEUpOj3ITisXfcqzjY7oTXA1L2KM7QbisMq cdqanpF7RYwcYmTfveq0PGcAlefEdced+XNGUAKDOqA4rOU4bQ744RWABOXAGYGizwL8yQIKq4SP R51GVZIf5zgj++4VDzus8VNz01rGmO7sz/wxHqHnD4e1HKfNAasr1byMggU9wFsdKKwSp615gUd+ HDFyiJF9P67T8pwBVJ5T2x1QoxgU3MRhHx6nzaCqmUxXNdNRaSVG7jMCNYpBwVUcVonThgquuuH1 WDfGeZDQVR5i5Dwj6zYKY5q0vrvxWhmQZRjXnYcPK8PnJMZhLUelJ1BUOiZmy51lQYx2dw6WJQZR 6RisEpWOiUW1b6M4On+Hx8i6MRj6plHpVQuNUOkoQo8a+uiodBTUclS6D0Wla/JTgBIR+gYxzBis EsMMZWkh94AY2Wdk3T0IIszuuTWNEkGbua47cOyQwR6Dwm7hCDOCNEpEGoUYdaxRIgONgsK2jzBj Rhfw90BQDo+RdT+Ep13ma6u5adN3YLrjzvw5Iyg8xbsnOKzliO1wc4G8GmBsdYXoEnk4rBKxrSlm QH4cMXKIkX0/Lug0aVsAvY9Adced+XNGUMTA4U/vUVjLEdsJkHe7ApCguCmRYobwCb5R2PZN/7qC ITmMDgvK4TGy7jCyIOtQGdfctBHbmO483BgKfXR2SBzWcsR2snlYa4BxxHaKr5+Ewrbdqwi6jUPu FTGyz8i+e9Vpjc4AqtGp7Q6oUQyKYeKwW3hNBlW0ZLqKlo5KKzFynxGoUQyKoeKw7ddkYDFU8nr2 nJF194JHgektqLqJ7sAGpHkw8/e9MwJPhqIAfVaJw1qO2GZAYuMUc7PBnfk7PEYIjYrPII3CKqHx GOeWdm1idHBnlRGUj0cR36qFRnp1FKFHjWL0qRgKanfX4SGUnS2k8zS3l54wbvCHKhhse9fJArpS uQeCsg+MrO8jjHHgVqJ6Qlg10UYVQzTdmj/w9IlxfJ4JFNZy+DJQWKcG7Mf8ESMTjZLhyx/hsEpA cmCad5r2OGLkjGcVcuBNgCK+VQtd+LKGIvSoIUdf50ZB7e46QQqVFUopnXHXm0GQGVQkwmCVyG/o DhNtBsTIPiPru06Wdhj4XTHTrDBUZ/Zn8rIMPXcoqNV9NPSBqms1wDhbCr4YGA6rJIaBioHR/UZi ZJ+R9fuNPOUdZjKuuWkjlzHdcWf+nBEUMXD4UtMorOXIZQ5chK0AJChuSqSYIfyNYxRWCRGP6SLl HgjK4TGy7sKlken1zqqFRnp1FKFHTSP0TUAU1HLQcrR5jdcAw2HiWYyWCBxWiaXlgPYhh4cY2Wdk 3eEJsmgvkhhb32OYeQIeKJyLorkcX3wGoU/3iHzqOjo7BpIYVwDj6OwYn8QYhVWiszklMSZGzjOy v5l3WpkzgCpzaruDuEiM38x3UwJT1ShQHUumq2PpqLQSI/cZgRrFoAQqDqtEZ0MlUMk9WByFRKHx bW6yUYiRcxpl53XYeNLha4qam3aNYbqzV/OHvrqKw1qORfehWHR//QYF7wi+QYg0BquESFNlTmLk PiPrO0LQaWXOAKrMieuOO/PnjKAEBrVGcVjLAekBFJAekDJ2WyJ5aBCQjsEqAenhXrjHjs4fMdrf OzeMBR2+OK65aSPfMd15uDHEAoOAdAzWckB6CAWkh3QBeV8ZgToiCw0C0jFYJaAXkh7a44iRu3tc GBgHpAdAQLqGIhghFuAD0jFQywHpCRSQnqx3wUGJCFKDqGoMti0RdZU7OtQjRs4ysn+oF3Waqq3i po2P0nQHDtsJ8K8JUNht1NMG6lgyXR1LR6WVGLnPCNQoBiVQcVilnjbmvjSdtRGjLXjGu6+QbZyq rW6iDRaHaB7M/DnKCAx7SwODqHQM1nJUOoOi0hmFuDgtkWKGDKLSMVglKr3L6160axMjZ04P09g4 Kj0GotI1FKFHTWN8VDoGajkqHQg7qQHGUen4sBMcVolKDygqnRg56PB0EGeuiS6lzZwY7cFmziLj 8P8ICP/XUIQP2vBR6Rio5aj0CIpK1+SnACUijgyi0jFYJSrduKgkbeaHzMj+Hss16Zg2GNNRsLk2 WQ0giTxwRqB7FIXoenM4bEt+E6isqCK+CVCpVEcRetQEXz4TBbW7x/oZcMmzApjusX6Gv0CIwrYd Zl3PaI8lRg4xsr/110V86ZjdYUHZB0bWfW3T+1CbLdhtmK/w+savbtethSQDwh4rgHnEPT4aD4VV rmunVOWCGDnPyL61wFiHVS5qbtqIe013QI3CGN7/QGG3cDk3A/JsMvBNiFvSSozcZwRqlAyfohWH bV/O5VCKVvI/vitG1p0IHvodesQ1N905Oqo77syfM4LCQ4Y2hnBYyxH3ARD7WAFIUA6cEagjsxAf zYrCqvH53ebyo13bbUbWd+3Q+IJk1UIbcX+/y6BhiH5SFNR2xP3mm8U1wDjiPkHfLcZhlYh7RomV iZHzjOwf6qGCvremUaAYdG13QI1iEEiMw24j4h7IL8BQ6Q7ckVZi5D4j+CIwPjUFDqtG3O/FpQLr VitPoUuSZKMQI/uMrNsoLIo7zApUc9Pu2pju7NH8RbHBjoDB2s4vANmYjPIcOS2RYoYMjHkMVs0v QFmB9kBQ9oGRdTsyjU1vu1cttBkDtpESCBqYNEZfw0FBbecX2Gw1cFTS/4NYEY4yAt8ZZyHaDsJh 1UQOe+EZOzp/xMilXYeF3Pj0omqi86xAmm7NH+hZhQH+ij8KaznsPtw8fzVgP+aPGO3OhYsjtOjj sGoihS7rv9Fm6joj6ztiwo0D0TkQiK6hCD1qwvGB6Bio5UD0FApETymDbdfmpZ8axPBjsG1fiflb KALU2YDRZvCdMrK+6zCedVoZPdv8cgXXnf2ZP/E8BpXRMVjLcdopUPIk0URDg4KepPiSJyiscslX E0G+SVrpugQxck6j7DxOm3daGZ1DldEx3XFn/pwRlIAFBpXRMVjLldEZkCKEY7IRuTN/h8cIlEjO DSqjY7BKZfQub3rRoR4xcsePY5qUxbvx4xiQQRnXnYcbQwyfbxmHtRynzaHK6PyeSWsyblB1G4NV onqNrxGRe0WMnFPUO3eveJZ2mSKk4qa9V6bpDnzdKcOnyEBhHx4xx/0UqNJTAUijEKNuNAr3M3yB JxS2HTHnZwihJq+HGMGMrPsxnKfAcZ+q9asmOq0P0jyY+XOUEagjeYY+q8RhrfpxoR9ttrpqAEmk mxIZ+jHavMVh2w4zg+570a5NjA7yrDIwTq5UtdC+JLxnvTaGL9eGgdo9PQwzoDJ6BTAdpjBDl//D YZWAWujaD50eEiP7jKyfHgYh61SjMCBiB9Udd+bPGUEJQo6Pb0FhLYcvc6g8Oifz0mmJ5FlgUIce g1XCl6FCoeTwEKODdHhYGHZ4pbLmpo2TxnTn4cZQGKEP9XBYy+HLAZDOOIZqc7u1LIjR7jRKHOAT VKOwSvhyl9e9aDN1npH1PS4JgZRoilRVLXThyxqK0KMmIfqwCgW1HL4MVHarAcZ1tPHluXBYJQYX Ks9Fh3rEyD4j+4d6abgXnrH1PQZK2bLGZgcsdtIl3wUj+G0//l2/6wZDkgD5iyuAcYh2gk+ri8K2 nZq6kh4ZDMTIWUb2DQYWdln4tuKmv31xzzpeLMQfk6Cw2yilDRgNjGplEqOuNYpBUU4cVimlTUU5 90FQnJHIDkppQ1U5tymRHKroieuOO/PnjKBwg5qmOKzlEG0fuBJVAUhQDpwRqCMzhr/khcIqQfcJ JTHeA0FxRyJ3XkobSsCjxkoB5dJ0FMEjPXxVMhTUcintEEgMUgFo6R04I3CNByE+1QsKqxRHx8ga 7TrfDSPruw7zgy6TGFfcdCeEqO7sz/yJ58EnMUZhLUdnA7XWaoCpzeHjS4DhsErQMFQCjN6QESP7 jKy/IeN1yccuTg8rbrrTQ1R33Jk/ZwSFpwk+MQgKazlEOwGSGFcAEhQ3JTIIU3wSYxS2vccnPiUG 2QNBOTxG1v24NDNNDFK10EivjiL0qGmGvhuPglqOzmabIy1qAK1xN5eemCF0UAsOq0Rna26F0q5D jA5712Fh3OFtypqbNjob052Hu+BhjL57icNajs5mUKwHW++Cg/IXc3wdHRRWieWNjS+p0qEeMXJN Ue/+2ntdILGTglMZUOsQ1R135s8ZQREDh6/1iMJaDtGOgPiICkCCcuCMQNH3I3zECwqrBN0HlBhk DwTFHYncuXsVcMTh0tbcq4qbzjJGdWd/5k88D/pkCIe1HL4cAUmMK4Bx+HKEHigcVglfhq79kB9H jOwzsu/H1ZUYOwlfjoCIHV13QI3CYnx8Bwq7jfBlIGVzDSCNQow60igZPts1DquEL3d53WuPMyjx MDIN0CEbhRi5p1F2baMwlnYY5FJz060xVHcePqwsRccO4bB2nUnoelAA3jhya1kQox2eg+GvfOGw SrB21mXSJjqZ7Z7Rg8w7s25uJVgbumuuhk4B19d1FMHAKfyd6vtcqe46WJsDBw4VwNQ9EC3ROgqF VUJ7I9MUq+QeECPnNvPdH2FGaYcvtWpuOo2i6w6oUaIU/1IEhd3CESZUx5Lp6lg6Kq3EyH1G8HVZ fAlUHLZ9hAmWQCX3gBgd5A0RnqYdesY1N22wNqY77syfM4IiBg59uQ2HtRysDaQmC+6bmywwSE6G wyqePaM8IcTIeUb2/bhOK3MGUGVOXHfcmT9nBCUwqDWKw9qN2E6zzcq4BpCguCmRPPPRqguHVSK2 U8oTsgeCcniMrDuMLEw6DHKpuWnPIzHd2cIRVIJ+Q43DWo7Y9oGcxhXAOGLbx2fARWGViG3oNg65 V8TIPiP77lXgI4R6axql4qZ98a7pDvzineGTvqGwW3hNlsSbLbIaQBqFGHWkUeriorBGQWHbr8lC hhBq8nqIEczIuh/Da+MTq/XrJrqTIZDmwcyfo4zAk6GY4XMao7DGxoSEFdPryXTcK2azU+9mMBrM PhT98gtJqi/GZgV/dHXx24/e0w+DYd8bzATjLyPvaDZ4P8qHZyzZrEKTADDKEk1Oe3B5JiHeKENh lYBuTR2AXbh59m11lpg6tdV79ArSn37uDcezorGu3l68fOY9e3XusVMvCmbN9XRefL6ezccTuaza q1F+Jz9/Nuof/Xjszeb5dH7Gjr1JPv14xlawL8fz8fT88uIs9v1j72X+tfzgalIU/TP/USY/fP78 al5Mrgb/V5yFMV9t+/rt6zen3uUfL8/8rz4/lj9dn//+9i/5K/P8r2EkfhI2vfgpLT87lj9m4sde sUrn6Yv/vn7+/A/vzIu9k5NfBMhfXUMv8k+Tk7eDT8V08SBitR3dzuQMXMgBerPm2dWhLD+5ngwm hXc0Lf9ds4+tzg0gZaIn89uZ6PL/iDH2xjdCEwwLSaAntMEPOnxv3C/Wt/C+5DMv7/fFwwm5end7 c7OWazEsevPrm34JL5+pXw7Zs9fP4ZWAfnWOAC6U9+KpztY8UNViqSqF+P/7tpgJRf8lH8xlt27G U2/5oR78fjy/A3lpe0WJjvSK4eoiGqufVWuIizUUzXbQr4hofpc0wz3pJ9EkmkSTaBJNokk0iSbR 3Ewz3hOa+zKeRJNoEk2iSTSJJtEkm4FoEk2iSTSJJtEkmmQzEE2iSTSJJtEkmkSTbAaiSTSJJtEk mkSTaLpJk2wGokk0iSbRJJpEk2iSzUA0iSbRJJpEk2gSTbIZiCbRJJpEk2gSTaJJNgPRJJpEk2gS TaJJNF2jSTYD0SSaRJNoEk2iSTTJZiCaRJNoEk2iSTTdp0l7MdEkmkSTaBJNonl4e/EuaCYVrCwr tCxss6gsNBlP5x7jaVqSbRX1kq2uyzZq5aHxpBgdDQfvxK+nvs/Ef/Hxah2ifxajvqB4cS4LIoW/ psfe5XTcv+3Nlx8x/3mT6GB8fV7Mi978xcssDb5u/PJU9PZ21PfK3/jjYAW8gBV97/OiA/8px2bJ 99Rb9OVE4S+eaNArvH4x600Hk/lgPCrH45cG/ucF10etcm+D0WAu2h8F/FjC36XHAf9Rpf3Hk+cl //JPmKtDlff/V34g6yKder88m8zGo59XUG+e/fa3/zV69y/vTJDJQu/o0+yjGMlm/bklKlugQnaH 8tNV1IsnLy9Prt4+efv7Vd0nnzXoXD17+/bi1W+S4sXV22dvro6aj/X7lfz25cXVU+/i8WtvVsyl dK7W7qq+y2/mxXRB8rTsVVkfKzwun0MVrffF/Gk+mTXKWkmZ/SSLSp15wfoW0/HkYnQzVur1/VbM y0J8ypeXly9kJS4erQ7M5RPxWZqtfvZriWNpsvrhu+ng/Yf5SKw5zz/2euPRfJqLpearfRMDs6hQ 9lktJZh/Ltb3rf/l+TB/X87hQl78dn1C7WP9JBaakLjii/dSjter12/l3PzHCuJqMVXep3zyt/8v Lxfd/sp8n/fyoKeBsRoW+HoYX4GFTVhVyE1oE6WS20/eP84vL0699JHfeNCfvD9lzTYWiTGWiDMV 8FcFeDkYiZ//kr9YXDZdcmsUjBtPJrIa2YoI3dyJULgUIfHZr7Le2WUxfTEYFUup9tpFxATPN2/X bgNlNTTcDiW3ErkuRkIbC3WqLS1Zl7oTrT4W/R+1yNMSKenPx2IIn5wveByxOEkZX9ZhXG3+7vam fPzAT3nm+6kqjWKlTPJpsa6y4PX5+Gku9rdpLrvf+FbsrWNv9mFRB3Myng1aD3i1+Oq1UBGDkZDH VXFcU4fwc3FXhjBtlSGMuPhd/jY74w0ipgUJeVWQ0E9XpxuqSNh+SK8qeldBPj67vHr9arl5fSpG 89UdQCh8yeLv4DH/1/HS4hCQ6TcvPfXiRwuJPhb2h6LeZP3UJ6P+ldwKhkod1hPvzbIMaa+eo4U4 lNUMZYG+FbjnPf4w/lQ8/tgb5t/m49HjR1KCH5db7IlYDDcLGb0WUuRfX34QU/RI0NXLed4rJVdI QcmytKFKvizjj1gslNSjoGq9WhmxYUgtllUxvxbGjdzaTr2R6MO74bj3UTxZo3plG7pch83vxSZ4 XdVN3PhlcxlXHVw+pxzWN5dPK/NR2kL9nRSBixtTurLcFhUWPxfTmfhlqfyYFiwn4dRjx/5x9V8c pMGafxFSVo6NJ5ZCg5/4/de/Lp9cXaGEm596vBbuxnYkH+XU+/NPT2hjPyz/78tfF594fu6xm/JT Lr9OZPFbz4+9BgUmKLC4REWe3/NYsqQjWq/8wu5+KP82KHBBgeeSsPgmzz2eehGXpELZh77nB0sK wY13c7OOQiAorH65+vMKX3b3V6UQCgph+TG/+15qLO7lgVc+flp+dDdGiy41KERyHIpyBEIvKuH+ TdmUlU8hNtYw9LJQPw6xoCA7H4uN0BN7kGwbe3nqhanXmCGmo5AsKFR/g5WfG19o+nAxEqbxKB/e 2c+nOlm5+7siK/5yAjuUFTlbKz83H323stIaQxZUFFRZUSnUslJD7iUra/9iZlqVFVMKP5+cqFro 3gaFDXtiH6owN3aW5jZ7sv7P6p4wFw173m/5YLS6khcGf1C6Baq7EPQ0n/fbny/Jv765EepiDYO0 9CjUzzPN53n7c/gJ7/zW9WbZq7FqkUljWTRY9UB7rTFuH6lcLXzmy3yafyqEgpx15S3+5MmHuhx8 LYZXZS1xnkbJsSe9pWej/lmSxhGAThvo2Dt6cv5fq53/5RdPfHeywEfCK1npa4P089vhcLFW5Qhe fRxMpG9dtlueC+R5o8HdujkSXo0Qjx8FSqwg70guhV7RHEA5unIWerfDchZmjx49agDkM7woRu/n H4T/kiTx4qne5PPi6Xg4njas0wXrmWAt11QSlesuLlep/CkRP+VBc9guz72zKIpT2TsW9fwf13zN /cXXYZSWpd2LiSd5nJUc5K8zPi0+nwXNYRsOi9Fdl4fNLh97/573RvMzMfsfbsof1DMVqR3OB58H wu9syZzcqd8vZVb63N6T0uWRc+Ed1eJ2XFI4K+2/1pgvD0p+mxbFSCiv89v5t6ffesPiH4P3HxrI p7fTqbAkS1XlLXsj+NzZlA1sqRZPlrRnWv3YFK1Kxwqq5Z7wt1Sai+MI2VT+ujydaLjNP3mXH76V RwjCp5KnB6nf/laKyeLbNEsaX74dz/PhorFoGqdxELdavzjjWShP0wqh4ORUcyZmUTgnw6ItcZf5 7ax4Mfg0kBNQtpJ9LpbnLmzx683yERisXhQ1VB6uXQrvxRuIUS0l6Px2Mhz0hDylbXqC2K+FcPaV Q4SX+eR8/GU0HOf9ljitHCBKCZL7UOP76kjRu/ueKdqsvyS9PH7z/PYqbgMYBOBNgPIIa7X13dfL c49yW2jI/lr36Y0YsJk8Fz6//TTx3hXCeyzKEx/Zl9Kl05nCd9bn0hReuAvSuOvQFH4nfxA83+US VbpNQU3ButuU58vvspKOgdvkI01h0YfYl0RuuBdw2SL1Fbepvyu36akQlMWZgzwo+GH5+clk0Hs0 zb/8sLrfen+exVyokb/O0kxsHP1iIva0tCGIC5mbfygWBsto/GXVWBFK7XwyePTVu/tz1vLpl4Bv WsDvs2LaIKEDfNMBXt1+eldMX9+Umub2RuoMzoPGWbDUu5fFdAURNg3o/pcV5e2tU+AlojRnZncI MXQNwIoSX5JQFLmgskJiSSVqAFZ7sexI0kT8U1iI/ZqOhsTyYUtAkLR6UY7I+UBsH9N+ieDq12/H pWG1IKB+LeflrovNl0LLDpTH6Ouf4e58SbGSJceJFLigNFBmrTbymWS7cgM6kk/V3lQuZpLmk8/5 YJi/GxYXo/M3T142WMjvxb7l5XeYjTwWWv1YKN/Z7XB+2tiIqs4yRGelOCnvuNCscA+Pp7ecetl5 fs+RNuv82tnWMmqfvs6n35bvNuQm6KViMBevNBZHyxI0Kqbtc90Se7JoUr7MKZuo1FuAFk19X75M B/NCNsyWDcVnveFAWKdqqy/TsRbryrDGgZ8ZDmuQRP7GYa0BhsMqGobYYV2PdWVYeRStlyz9sNZN NMOqpQkNq2iIllYcdgtrk2XA2qwAOpq7nmIzRqDKYBleZaCw7ZWcpcBKfsAQ7JUSAAYq4IHp2qyb 6J4WpLkVIRJs0EKEwxqv5G0KkejhZiGqATsdVsEGLXI4bGtYo6RqRGtz477ph8CEb9HK29ed5MHG JzAJLGamc3DXQjcFGorgo8YR+kkxUKvaLojuNmjdsow0Ozi4LKMsQC9LFLY1UGEEGWNbVEJ7uix3 rhvT0HRZVi00U6CjCD1qGqKXJQpq1wjJ/M3LsgaY+l0ZQy9LHLZtVnBoZ6NlufNlySJuvF1WTXT7 pY6mlSuK70SPZvN8fjvzOG8/V284nq0ep5a/X08Gk8I7mpb/tqf0ntLQn34uaTealfezn70699ip F7TOMxfX68cTSbbNS34nP3826h+VL9Pl7QN27E3y6ccz5fWoG8KeAeibfDBsXEV2lOnvF6+9Yjod T4HPrHSuEUKwvIi/uMp6IWXtzRo5UqWyXBjF18HqgeTVh9u5fLssb5kMJdV+8fnkl5v+2QmTFzNW 48ZWSf2xslCXWuBEqohv8sX0/wNXlMnq16ADAI== --=-LXWa6OL6bN8i+5klQC12 Content-Disposition: attachment; filename=xsane_regscan_quit_log.txt.gz Content-Type: application/x-gzip; name=xsane_regscan_quit_log.txt.gz Content-Transfer-Encoding: base64 H4sICHHdx0AAA3hzYW5lX3JlZ3NjYW5fcXVpdF9sb2cudHh0AOxdeXPbOLL/fz8FpqbqRZ6VZF46 a5R6juVk/MaHKnImSaVSXoiEbK4pUktSdvQ+/XYDIMVblGPnqJHLiSWi+4dGo7vRAAnwU0BdZn0m C2q7QxKE1A9t94ZYbLa6IQvPYqThsHvmEK3TOfjHpxR16K+RNvTIDQvJ0vNDMvd8EjD/3jYZ+RcS vyANKKSW5dvu3MsifFI+k8Az74C9cUBWAcKdTu675WRzajvMGpIjQGRBAN8XtrMmrheSYLVEGZhF Zmuy9L3QMz0ni6QWVmgUkbEQKb0lkhaUz2zXQhBoPm96t9PNyQ1kjh2EzM1DPFCbaxo1Znpu6HsO /nWZGdqeGxPzP6Rx9LoF1bHlP1E7B2Tuewte1JpRaIxrBURtK23VID6j1jrmNm+ZeXd96wXhkFDT RIWBbny28EJGxGV1oLXVbh+49UK2BDGxA67o04vrs8vLyauj4z/huw/fu/GFQgzHM6nDIVy6YEOy 9ixag7ARHJAGb+r4Ynrww7AlNWJ5LHBfhOSW3jPokAUjaOqEBgK8kN9bMhd7Hnp7boMBgEEPySEL zUMsD9rsPyv7vpDTpFgX8lczk8aFB+5g3vJyAl1k2T4YluevD+qLxOnaeKlYmA0tGLkLDP/69UVt ygR6faYd4K9uGXcr5oYB8eYkvGWJKomgRoMmlHAfJUglOpWgOQRNApFhhxqpiEgsQH2fTkD/MxdC CGkcn47fot9QdGyIF7c0JNRnZMn8hR1ivIIQsgqYMJkdapweXZxApMZgG7R53EwIsVhBS2aMMNd0 vAAqsV0y8zFahNg0CsGLBLfeyrF2aaPzQNegM8ANlsy057YABu3aGMYWS167hVFt0X62jo1cFkJp aN6i4crIZNKAtQLmBhBb79mzCBCAE7ZMxwbDagfeglkexvP23PYX9UE2QVetzZQI1MU8MsDf+NRF o+KhDOxQmkRhoLddO8dYWYim+ufJxcfLi/8twoNRF6mvfQhDDGVKjnLyYjnxDfSg/EJUQWZf80zk M5myMJGYiJQEHHbpgJmzOxQLEpT2Pz7JC5/JRJbIAZL8pbSNXktVm2QJOQ7yFo2fCYCXv0YYLe5o rySQ6JqVz92Z99Dvaa7X0FZ05wc7vCVn54O+rh5qhzpIgp7xbvqKoA25zA/SjKlvGUxGIZgLVycu YyAvBBGHUdBU+OBxEwmGGZ4W+bQKZp/JPUjt+a3TMXd60Lq1MkP4miOX+OIP+leGwm6zNu/JSLcN 5YvSe6UfkHdXqnaodg81g19T1N5BhleIIuiJIMlQyNoP4e8hEEsdZYi87AXJ5dgz4BnOZrOhZVkZ modbBuEWyjBM4EAAtO5qMWM+1wgw8KuRenlJBmJB7yDkrQCGh++1t+J97MPAH0QuAjZ4iDZ9CPDY gkOo8TAnTQYYvNNGQ6IOZLEAi2O8jK1rgvEFxmYsD7Jtov5itWwS53I+v3RPXAs+0sUSvlVWh7ZJ VyHk9aFINLEVRV31iM7JdRUJ7MXSWW+Hz3Pac66MBwg6MEDLscaMxJiteBeIrMv1iG0xSujMg8vQ kcWiuziXAWTk44Mtt5imlBGz/chRqt2ktiGjmiubeXF5dTLM9AYYaEDnrIkZpB2ioMJicfKEFyBE ZlDEDw/2SMjDy2oWrIFgAUkB1+MLn/HhUcx38ioSPylJmlxR5++mV0LLNAwhBOEAgPYvmliMIr0D BGnhvKgZe4xMkqO8od1u141/OZNx2ZdICKGjlOwJQqgkSVweYbMmKJyORztUK+Q197a3Crh+Yej3 15XsAcR+CNjokTDSzAmdhxArvnz5AnZmQvqlQEIe0Jkje3fOaAixJQUiJIicmuiKkiweM9OzsDMl 2csi5y8MGZh22h7P2kAWD4Y+FGfBqIsplCQqkkSyq51KOQr4M2JElcHoBeaAcrcCyI1Btys39FZo ZE1urRGhVKaXDW0E6sMx/JonuIXKi4IjUauVF9FVyF1iIBD0wwdG74SXLugNE4soYPsBD+wZvsb7 o7cXpxdvhsjgsxdc6TakVj4MAQSSLADgSd0vv/xyUClBZJowA18AK4ZknFbQCibZXhANGvyBVFuU pCoH+FgL4GOVLfA2QKMDyMlgomKzoKi6cElryCupygG2ySuptsnrshuKs4tCUaGwhqiSqhxgm6iS qr65inU5kUKj0cBE057JFDYIfXtJnt5eSUuVHozj7WxlOyFw1jLP6S3F9n4EiG0mFpGW9HtdpARp SbfURUqQ1u+fEJV6z/xQuHRkYrVGikIlCrSLCGiLPWWod5I7gDB+CDPM0PNxyYX6Qdq8LBrWiEkm ZhfH1BkD9ZZonSStLynaIHW43YZpAX3IG3H+tF1I4D9OMFbrNE28LaoEd/ZyiewPt56T9U9WOCAj S1Kcaq1lqGvLA8mODR07Bw1VS/VrUedDPmt5buHgjDW8RtRqNUZkVQKDi5jUF7M4sMSVE0ZLflzs h1s73eVV4rznxNt1GdNu06TPlg41o8B7QyHxuqfOimFyucLp58qHwqwqq4X1mXXNkci2aBRRFqHc +Iy5AmcLyoayCGcGrZHibMGJKXcbuaj1b7gQqdBic4pdfEMXCyp1ud13QRFvOEP0o7arDS9iKNVc Em4b2IahTIEp4bbBxQzFwtH1Tmgxw05xn7k4LJGryRFpuAAzEcXRgjRk5846mxFEKX3UhTMGc0Ib p4sw382uKG/SjJAPgBmsKLkQcmw3AEGH4lZrI6arrw1cMICAY0JDApZYS2rlF9GK1wqq1lVKlhNi uaP1DVwPf5lbdNjWi9ATGCIp5BwPEqopZjBi/VIUBGJinV1h3LKUI9YMSAOFgkzmS28+n89YR2mC wdjOwUGqNbwRqbXVYaI82UgyzLcTVxtOx9Leh+lm411sh3j3fpuXKYkiOaeN2NROkCiMpt6yEGbg +UIxuxySNUtyppKZbGEiL2BQ6HqJss0g3SY5xnjAFPLkGOMRKcsYZ3dBO8cIGfT1FxJrQMkUrcuL ApHkXq+HEPUTZZC8liFiUQkiFpUhQm5ehohFJYhYVIYIsZ3I8RPZUmU8VEelmTKMuzFjASZaBa73 FGPK0iLMiLEAMw7lQwzkSg5VludKOW7EXMBL1+WlraKfRDn4PXjsNd42Ft6d9OWj5Fpcu528KXOM M8XofhCuoc70Fl9DVeoQqXWIenWIOk+GpD8ZUa3W1dKT8WQqqIXUfTJl1iFSahHNn4zo6fSkVRAZ igJEqqJUdXBMVGUq9Yg6fSDSqpUZE/XrEA1qEFU6QkxUpfGYqMro9DmqQOlU9p0k6lYSGTOsDtwu aSqvxbRNpmUheSlvPoLK4V/qbtBf/I4SOR2PEOxVv0km4r6SvKQqr9NR1fauxzx08vvGXyoLh3IC yb9ph0ndCjIYPMQtLfI/0f0sqHdIhCytXP3j6P5vYPq2yIZRDy9T9L+LWttp0a7xYQHgb+haU+it 2VILErz3R695/fzHoBkQsdJ/BmPhh8blxUhpQhY+SsFMxb0AJAGcJgyQN8En5Utn8JmMOG6C9u3J GyhSNFHUTxbhLODi8opYUk/5LhNTTv7AA6STJ8sgPREX2J2ZwFYHpLEI7kZYS1Las6PzSWt6dXT1 brppdUbG6cnV1enFG0Q8nV6dvJ020oqLyq/+OCHnp9Njcnp4mUzuomvyHhMHxMoMFVNuw8D/0/Ep sTyDTy/wSQq//wlNTebyh7fegh3emQ5dh5572MZ7LYdcE60J8+difL9WtY5yPbn1Qq9tUuf3TI9O WTiFOc2E+lAJyBc0km37jfwxnpwOSb+d1spv5ANcH6k4VUCKUZ7gY0xwbrvw+SN+SVFg8j2xvzBn irOZUXfQJGeQIUO+Dp+rKHvKhrKnkMbR+P+SQr98SaCkJWiTAqYwX68ch0xDtuS3iKaQnmOo4EzS UjMMSDu1/581Jj6DzjgAKk1XxeMUrJfWGqoUl4jMlcP7MUhnWb9x8c+YexPejlSl1+uKBr2FGcex 53j+SM1VHUDVUGW31+Fm08XopOGnHnyielpfkzEZdTrdPkqndkzloKBYU0QxROyDJl8tJFjHiNeA XwPNZ/cjPa0Fx2FuJLKTFrlJ/hOaLlf57Zx/yNjaGxaeH5/9ObbvbYv5GUM7dUN2I63+ygaDP+IO jn1BGhsba3KEkYGfMzqXd0/eYNI9eX8+XoXr47XpsDPvIUV4vPJ95oYEkYgUBqrhkNlOP7+8unzb ktDBkAAuV3wTP12P31195KNE2rJeR6aCJtIFdUAkMvoyAKriaxQPjRTr5Hb9ah2yAFJ+YM0WoYnI om4H8tGO3k+RXHkhdQT/iHRgOqzpSq+bRjkbaQPoX9Nj8znvbk2FngzAVlnW6iZ0FbAze2FjJ3Au FJwJwQeyHfOoWdvjCl9oTrrBOcQkH3u2q2CYoF/4hemSMWuktAd4caPLkdFNKoR3TGl/oF904JOK T4AY/ZHQO6odPqaeMkAjuH79+j26FsyqXmJbMqMeTqRuWHhMl+ngOBVrQfzRD3+RWxGR49SQ8Iic ajYud0DBJkgTDNKHPEgn8xiH3gR81lw0Mln+Pb+vnpJJihuE3hLFKyrD6xAfGwdyGQn9dUn9u6y7 Im2+ArFkNJRrNiPysrARyVGGPwEA+ruO1h0bYqHJnHcg3VIPnuHZRK2cbPMoGERxb+XjNggp6ovN A5Zp4fnz3C2SziITRGJAEMGHT9jFcihuzHBHhjLopgPV8S3ajfNJ+dyUS+RqbvSMaNQaNFoNGr2U pnAlIbOsUKbMjXZ8Fq58F/d9TFdcw8/Qq8YzYHb2mHvMPeYec4/5KMzuTyLnHnOPucfcY+7zzz3m HnMnzHimiOvxYoOKCVe8hZxQyqlv0N7PiH+84FJ2P8R4/P2Qr8L5WYx+j7nH/JEx9369x9xj7jH3 CzR7zD3mHnOPuY+fe8w95t7m95h7zL3N7zH3mHvMPeY+fu4x95h/c5t/Djl7MRl/iPwaD0YYytvD /LR1VesPOCweL5R9oprzlGxXTj9mndq4/HferadrO+3We9QuuZK7PpJKblkx1IhK6X/9Xrp0s95N sTTeMRc9WvA1u+kqNnCgzfI3KIyIXszhe8tTd+5lt1HgTqZTPEowVziZnAGaqnWT227OJkd4sWck d7W94pR6b5DcwzPz7Zvb0AWvw72T/K0DeIJwwc6MQOyvOXHvc8JN6T0rls56wC0l8fY23Ipct2G/ 4TMd9zZ74NtX+LMgIMIvye0w8oGPBV3i6yBoSPguZ82kullCpm7IdKWcTEuQGWmyeL8LxJPchpdn 3L34bR1HbKpFdZzxA0vdTK999bZcI7t9K4OockSlFFHdIEqVDJI++J6f4tLCbX2+GC9Sm2zSyhw8 gzKTzUOJY1G85TIlivUwjzzEkB4C1/ieugnzcQOedFqS3Kx8en5CoM63V4mL+J4P5l/LQTRqNWnA EHDHrINSymH8ipfQgzYfjfkAShrdrqH1FI3MUJYk+2w15/LqSl8bpM8CkN4BnovHd+b8YzMU8615 9bIELk3yPSgpuxl7id3LqcogefCIPO4lPssyaU+i6BIioO2CuyXtv2Cj4D2L9gn2M/sEOxp85ztm R1oKZNcdg1q8Y1BJdfe2LYPZRmIH46G5CZK7k8n08kKOzgt8BUZSEydXWMUn/RCfYxMpFT/RmPSH pCt3qTZhkMlF77dgSUeuNcWxjp9tlOqBFsFy/vxe5vRHcTo17jVPkBPymP3lqfqyO9khf/ID3CYp PFMtJUahMKoozfhfV+/rBX9rqIAbN4F+StUH3199nBxNp7U0rw2JttF8p+KJl80GQ65Z8dIlVG/R 6xgsTybO2YRYuCYLryFJxRQFD4Vyr2eOx0+/SG3UzZJKX87vvwyYA112Pc/tb0wVpkNBLKBsJ2rk 7eQ4ngZgx1rP8vBiMoFCaxmSDx8IRGPFIJqCH+CruEIUStQ5L9OwuGdBhCZKl6QQVEBQu5yqQxQT 0jH+WUHuxBc1+sB/UwgaIGgUgaHEiP83iYEyWETRJZc+J/N5EYIOCMnC5OdUvaUyGICQKceIpRGq E978Pr9kyLKBii1KIXRQD4xrwCAdTq7MOavKWwEDq2GQgVEuQ1fIoHeJ2kdlI2+XaH1i9InsIcE1 K0PoZVqhJz7X0cNpdO6gnCAMy2wl+k3YiiI78BvaCvwmP/M/T2UravRb21YkQs5WChA2trIheZSt FP7Ws/isreyK8HurlQ/0j04ovkc+8TMck5AavNPjT+kz9JthF9+8ZZI3+Nq9XMKv82mBmr9ully3 stcl/OV8DuGioAJxMkf++qDkOs1e397CaFpenJZdePmMTJ7bnZxgmxkdZ9eMfpyjfNTkWT6qog16 ldTJ83yQul99pI+qqFr/8cf6UJpimOaP9QEX4sf6qCbbH+vzTY/10XY41ucP++Y2RVlyro/2LOf6 8EEhea6Plj7XJ30yT+pcH72fESZ1tI/a66SrTZ3q0+128ux4po/2qDN9tPSZPsrXn+kjlnqG8Ffk /WoneotNMn/DJcYJZP/EBt1zOxuvlo5tgtX1s5VCja/YjZ07y+b6nC7H3oPreNTKGF1iGRXtDIer VHm8sEqi8vw+MUtCy0VIomR9PUugbiPQ0gS5JhQG9ahYLo/w0SPlIYUT2begsADXx8erxZLM2Bxf /eDL2T+fXJdlzFGSKjNmMavAHPCbZsyU4nxCp/iZz670KGNWnztjNkS+HpUXzK4olWUDZcfZlVIz YwYZNI2n3QaZca3T/OzKeq7Z1TEYipiz45LNC3m9tbTNtk8fXiSHZfJhhPc6mgRSgp4Bg77FljD2 9VOmKKyOH7qOmY3rPSSzGgh+46Xdjo+PxhCYyi4kwbqU4F3A/BREGcG6jOCCv1Hwcs5jzWqOUUNV leTgy+PzhPkJCk1TkmsU1kMiyJOiQM8peN4TxGKkbxRZD4lgLyjyAR9gEhjFMEk5hCjp+0zWw1+Q TFoboDIM2V5O0etm5OBKGctXe2RPrJPFVx7PwYQQ+WLsmrgV6RtkUoKz6ED1fCui9b5cSj2N3o2i ixdvFgwpyMeHoQY2Kzu0nAaIeXRPbQc3Lp+647dH56kq+MnxdkBoRFNZh4jteJME332SPgY9Flat ISzaQu5+X+2q6jW+Pp7sexRee6SmdxO+sLdLK8quYYb+Wt5XwaGQ9NV+X9xOka9rF+f5ZVdHOW1L sPA7P5wlj54hyGCWy/Lg4/tsoGPlvR28Jl5fnOd68L1S2t3UukU3ht7vVutm9+74OdW6RVGdvrGj DcUcJW0tQ9zW1E5szVtbWov0CbxFU6ubuiHYtVs1tXZji2mf1lsGPeVn8JanavQ38i1V7e5qchuW Et2UYm5rrar2are2Hu3XO5jW1ZXK1m4IdmwtMBp1W1uPNhs3O50tgXPvMo9xmV5H29VlYpYylynD 3OoyvU63tsvUon0Cl1GMbrXLxAS7uozSUWq7TC3aTGu7ql7DRvcus6NaNV3fkurmjShmKTOiMsyt RqQb9Y2oFu3Xu4yK90MqA0RMsGuAMLr1A0Qt2qzL9LQt4fDHcJnv7wQDbUsGm3eCmKXMCbZiPkmA gGrqpyq1aL/eZfq9akOIy3e0g36/thnUIs20tKcrP8Ws/ycbYfSOsusiwYalTDdlmFtb21HqT51r 0e7sLk9pRIYyqB6cNgQ7KgqPqayrqHq02VWDMsn2LgOBevfhaNto9MiZ8GCH0eU5BpcnDbmxQ5eH lUdmKB21vkXUos16S7e3a5r+t/GWfm/X8SXmKE1QHje6bBKb7QlKHdLv6i2bbLE8w32cmoCxtp7q 0WaX17TurgH0b+Mt+GjczlPgTrVuSjFrTIHrLyvXov2+LhOvSZSujBjfZFKoG/WH7Vq0+ft+O+f0 P/HygGLsmqpuWMoXWh+XmCdWaGsstNah/a4us1n5Ll9/rzEr/2qXUXvd2kuP9Wizi3GGtmvc/Zld pqvtvKwcs5TezivB3Ooym/uAdW7nPcey8pO6THx/tfQub6/Guu/Xu4zaq79+XYs2uyCnqN9uieC7 u4yuqTsnrTFL+SMmj5v3J55NqfOIyY8+848f+flve2/ca0tuXXf+P5/i/TcyIBlFsopVZaADGLEd GGPHhqXAMxgMNLK6ZTeiWIq6ZSvz6ee+7vbl091vn7UWL6t4easCBFH6Le57eE7tIrm5+KPzPS3M h3l1wiw7/QRR0pfpsuzn1Qj6p8u6n2uhABVp6uO8fnlYfg/8tVLaBka355/P+27K7ys/RPQIw2mt 0XOIHdLBagzLpo5kzy3cF3TdOFbspPiVy0ib2ELBQ1Acm+qYHfmfldIao2e+N0gPMXqqxZTSxF0C ODHxpD7TAwynbWL0BJXo4sGUV4Z8JZrSWqPnEN7o/kmwznJZ+rmJWzpCMRuVjha+iE1pWxg9F1CJ npwHE9cfF762TGmt0fP2Rh9i9JSL2M9N3O0MJybeoEh8EZvSNjF6gkr07Ex/8C7XyteWKa0xejpT xjtlXmfDCXIR+7mJu2nuxIQpU/ykzKb5Kd7oZ5el56NwVteor9tGvx0oqTV63qv+Q4yecgH7uYn3 3XgxYW+LQxT3ltL2Nno+fq984sE88iGaw0S/hTitsYW+q2PpaIRB58ztALOB8cWJiIcXYXR56zuk xWLpvlacnUX8Wgl8RZrSWqPnbYv2HiJ0ztxOUNbHw4sXEU5QVnpwoaS9jZ6Pn59PPJjqSyXRTwSn NUZPZA66braEGZ0x/8wSeAFlZS8mXgIvfFmZ0vY2eoKKdEIGyVZGT75+TWmt0fM8J3X3lIkTOmP+ mUJrAi9PLyYutM78y5PSdjZ65sdj8SeuyoONnvTYzWmt0fNK3uiMzpjblHlu4m7nOTFhyhSHKLGd x2h7Gz1BRTqgU2GNjJ4bX7+mtMbo6Zy7e5cpkyI6Z257+9zENY04MWFvi0OUMI0w2r5GT3AeekGH jhsZPenXECW1Rs8r+aJXdBq6cbUeVKSpj/P65eHKn7zmtE2MnuAttNW+hTbhLURpjdHTYY7cWz6v MnrKp9IXMKXxIsJXLj9FoaQtjJ5gmvuJB1M2evJFaEprjZ73BukhRk+1mFKauEsAJyae1AvrYErb xOgJiim5tpiShWIKpTVGTweceKfMK22hchF7BbVZNyYuHfHVVk7bxOgJKtFTZcn+qSFfW6a01ug5 hDd6sJSJST5oXpq42xm1O4BJ2AGktC2MnmBX+BMPpmz05MdUSmuNnkN4o/snwS4fHS9N3G1wFLMR 0ZO3mHDaFkbPx6u2rdJ1tPGuI0r6slAWmVd6/3QZbIRJs37QfAb+RTcm7O3COxI5bYOlPzoQXXse WjgOXXEaevX82m8sXbonwDzJB5wv83KIqNBqB16Ai/YiwoGUx0VT0s6WVsAbL4Jjn5+F541zWmOA lU9DD/wm2VCh1U7FwHUEXkQ4FeMvI6CknS2t6IqKvfaKil24ooLSGkurfBD6MmNLmFGR9TOLfXDj jRsTL/b5G284bWdLK7gIqQjkGhB/ERKnNSZV+WjzZVImTqjI+pmSMrpXzYuJS8rCvWqUtrelFQEo 0BV+jSytwuV8lNZYWuWD0APPyWJGRVabMhnc9enGhCmT+bs+OW1nSyu4/7UIjra0Cpijigtj10k/ DD1uyqSARkvb24B668WEvY1Cbylt15TJ4Ih8Rg9ak4TJ/HF6SmosrfJN0iOny3puoRVgOriP8/q5 7spjPThtC0sruqR7q72kexMu6aa01tJ62ycOsLTKt24vYBXgRURdXfhZPSVtYWkFK8MikMdsfmXI aY2l9b5x+xBLq37jdkA3bnsx8aReuHGb0rawtKIbt3PtjdtZuHGb0hpL633j9iGWVvnG7dLELTRV bmeEld/O4LQtLK1gi6sI5Pojv8nFaY2ldYwbtwdLmZj0+7kTup/bi4m3M4QbtyltE0srqETPlSaK MPMuCk5rLK33rduHGGDlW7dLE3fTvPLW7aeGfBGb0jawtIILXTbnPhfU142/oIWSWkvrEKv+7gmQ Zn15+9zE6y2M2eblMPMXRXHaBkt/dNNY7UVjwj1jFdeMrfBy6Dtdvq+PTDd30h1LZe5kBCeMvIhw IOXPF1HS3pZW8Pws6CRbI0srf0aN0xpL64mUyu7ZssnYyQ0cYfUiwqkYf4CVkna2tCLk5F55rPmp oTA7r4FIxhMhkoONLWGWkZOlibvYr6QkhJmnJHDazpZWAM8ogmNPdCYetcFpjQH2UsjJSUdOTgg5 6cXEJWUBOUlpO1taEXJyrQQ0hVWASFJaY1I9ESI52CgTs4ycLE3cjctK2FvMPOyN03a2tALmZBEc bGnlqZOc9mWC7ZfCTgZUaP1MjQyxI72YuEom0CApbWdL6+OnIqM3eRtLa6CfIEpqLK0yHHHkdFnP LbSuwLZJfZzXD9zrSi+dOW0LSyviTm613MlN4E5SWmNpvbmTh1ha1ZFsAQtnLyLq6sIvhClpE0sr eAhiZTElRb6YwmmNpfVGTh5iadWRkwEhJ72YeFIvICcpbQtLK0JO5lrkZBaQk5TWWlqHcE+MljKr jJwsTdxCUyVyMqz8dh6nbWFpRRvCU+2O8CRsCVNaY2kdAzk5WMrEpAMqEwJUejHxBoWAnKS0LSyt gDlZBPIuF0+d5LQvUybf2MkjUmaTsZOliZcyXkyYMjuPneS0r0+ZHWAnn/9d7OvOYycpqbG0joGd HCxd0qxDKp+beN+NFxP2dt74AjalbWFpRQCK2oW/sO6vqCsX/F77dNEe8vdUwJ6nK3Eno8ydjOhQ Xu2ZPOFI3lvjTlIDwSMDLDjWWQTq87Pwxzo5rbG0nkip7J4tm4yd3MCpby8i6urGn/mmpJ0trQg5 udciJ3cBOUlpjaX1ROTk8c9/q6ntDwtzGTlZmriL/UqwyFND4UqWt4acfOUAExNA0xSBXDHi4TSc 1lhaL4WcnHTk5ISQk15MXFIWkJOUtrOlFSEn13OQk6uAnKS01gB7IeRkXGTkZGnipYwXEy9i+N5y 2r4pEwFzsgiOTZnIUyc5rbG0Xgo7GVCh9XM1MmAm82LC3gaBBklp+1paw+MFX0bTmTaW1kgvDymp sbTKcMSR02U9sND6mS8qg2IQ9XFe/QildeVLR5S2haUVcSe3Wu7kJnAnKa2xtN7cySMsrTJ2cgG1 Ji8i6urCV5ooaQtLKyg+FoG8s8WXHzmtsbTeyMlDLK06cjIg5KQXE07qg4CcpLQtLK1wd6t+e0vZ 36qoRC83cvIYS6tcxF4BctKNiUtHPHKS0zaxtIJiylR7b+ckXNxJaY2ldQzkZPckiEmHSCYEkYQx GzE3BOQkpW1haQXMySLQLa18bZnSWkvrEAcn+qfMpr9JN4CdxDHbpMzGYyc5bQNLK8BO7pXYyZ3H TlJSY2kdAzs52KQszTqk8rmJ9914MWFv55UvYFPaFkt/tPKvXPgnft3PSI2ldRli2d89AebpRJLk YC+HKHMnIzrHWnuMVTjF+ua5k2kBZ5uLQDep8vAMSmtNqjd30nuIZOzkBkAJXkTU1Y3HJFDSkfx5 OwJU7pWgjaeG/LFgSmsMsFdCToZZRk6WJu5ivxLD89SQB71R2r4u8ASQk0Ugm1R55CSnNSbVGznp TscmHTk5IeSkFxOXlAXkJKXtbGlFyMn1HOTkKiAnKe3LsmO6EnIyLjJysjRx1zCVyMmnhvwMgtL2 trQC3kw8BToZIk+d5LTG0nop7GRAhVbb24DYkV5M2Nsg0CAp7UBrmRwff6vZWS+gLzVH+julpNbS eqFDE2k9t9C6oC+K+Tivn+uumf9aKW0TSyv4bmrrKUkoqHBaY2m9uZNHWFpl7CSqzNYWZoW6bE1Z tmpfC5TqU22tPgnFek5rLa1DOCcGy5YQdORkQMhJLyac1AcBOUlpW1haEXIy1yIns4CcpLTG0noj Jw+xtMrIydLELTRVIiefGgqlo3OQk3ECyMkikOuPPHKS075c9U83cvKIilzUkZMRISe9mHg7Q0BO UtoGltYFMCeLQH1BLDx1ktMaS+sY2Mn+SbDJIMnSxEsCGLORpZXHTnLaFpbWxw/CXomd3HnsJCU1 ltZzT0ObdNEejVGSK806dvK5ifcq8WLC3s6ZXwxT2gZL/wQ6myr7mviuMlJraR1i2d89AebpRJLk aNNPmTuJjn7XnvwWDn7XnPs+29IKWACpFgaQBBoApzWW1hO5k4Nli8cAeWRpfTxLraWKCFCRGqbI W94GflrcgsNsey1ycheQk5TWWFqvhJwMs4ycLE28xb4XEy72Zx45yWk7W1oBcrIIDj4EzSMnOa01 wF7IPRF2GTlZmngp48XEJWUBOUlp+/rzNoSc9B41+G7ZBIgkpTUm1RMhkoPNyeIiIydLE+/l6cXE ixgeOclpB5qYhQgIlcGb/sAEizx1ktMaS+ulsJMBFVptbwNiR3oxYW+DQIOktAOlzPNa2/lWvbU4 +lJzol9DlNRYWmU44sjpsp5baF0eT1O4j/P6gXtd6EkNp21haUXcydpbb5Jw7Q2nNZbWmzt5hKVV xk6iG7FqL8QS7sOquQ6rDtUCitC1N6ol4Uo1TmssrTdy8hhLq4ycDAg56cWEk/ogICcpbRNLK6gt 51rkZBaQk5TWWFrHQE6OljKrDKgsTbyU8WLClFl55CSnbWFpBcjJItAtrXxtmdJaS+sQDorBUiZG /SGKCFDpxYQPURSQk5S2haUVMCeLQLa08tRJTmssrTd28hADrIydLE28lPFiwpTZeOwkp21gaQXY yb0SO7nz2ElKaiytN3aSNKnq2MnnJl5vYcw2L4c586UjSttg6T+Dlf9cufCf+XU/IzWWVudz3eli LK0tasDv8ruJMncyAlCCFxEOpDwmgZIOtLGVFsCdTB4VBT4/C8+d5LTGAHsl7uQmYyc3QJ30IqKu bjxzkpL29eftCDkJIVpt/Hm7AKiktMbSeiKgsnu2hFlGTpYm3mLfiwkX+zOPnOS0nS2tADkZIaqx kaWVR05y2pcpA9GZ7ypldhk5WZp4KePFhCmz88hJTtvb0gq8vxAf3AY5uQnISUprDLBXQk7GRUZO libey9OLCV+HC4+c5LR9UyYCimSA2PlGlFaeOslpraX1QgcnUkCFVtvbgNiRXkzY2yDQIClt15R5 vuPE+Z7gHShNEibP9MhNSY2lVYYjjpwu67mFVlSOpj7Oqx+hpz/Dl68pbQtLK+JObrXcyU3gTlJa a2m97RMHWFpl7OQCqJNeRNTVhWdOUtIWllaAnCwC2dLKIyc5rbG03sjJQyytOnIyIOSkFxNO6oOA nKS0LSytCDmZa5GTWUBOUtqXb8KZeUbvlFFTJsvIydLESxkvJkyZlUdOctoGKRMAcrII1JQJPHKS 0xpL64HIyQt7CqIOqIwIUOnFhA9RFJCTlLaJpRVUopdK6GRYeOokpzWW1s7Yyfc5ysRNxk6WJl7K eDFhymw8dpLTNrC0AuzkXomd3HnsJCW1ltbjVv3XHWHSrEMqn5t4vfViwt7OC99bSttg6Y+OxTuP JeyrcMy94pT7ujlp/MZGl+4JME83d9IdS2XuZATcSS8iHEh57iQl7bqxlRZAkiwC+aXCkyQ5rTGp nkiSHCxbNhk7uQHqpBcRdXXjmZOUtLOlFSEnd4dSB18quwCRfKTVnlR/A+ZSyMmkIycT6K0bEy72 Z763nLZvyswAOVkE8tESHjnJaY1J9UTk5PFJ0GoI+/7x3mXkZGnipYwXE6bMziMnOW1nSyuCSG5o 5tPI0iogJymtsbReCTkZFxk5WZp4L08vJnx5LjxyktN2trQCimQRHGxp5amTnNZYWi+FnQyo0Gp7 G1CRzIsJexuEMhml7WxpffxU5MrCaebrppTUmFRl3OFlVv1pPbfQii4N8z4O/KJW4dowStvCpIpI kptDkmz9EAncSUprLK03d/IQS6s6ki2AOulFRF1deOYkJW1iaQUPQaxETqbIIyc5rbG03sjJQyyt OnIyIOSkFxNO6oOAnKS0LSytCDmZa5GTWUBOUlprab3PTBxhadUdaxkgJ92YMGUyj5zktC0srQA5 WQSypZVHTnJaY2m9kZOHWFp15GREyEkvJnyIooCcpLQtLK2AOVkEsqWVp05yWmNpPRA7eV2PXtxk SGVp4qWMFxOmzMZjJzltA0srOOe7V2Ind/7cLiU1ltYDT0NrifOe0iXNCAxgezsD1oAbE/Z25vkB nLaFpRXZzyp/WQE/UUGfWDdn3LtHl9cZYK/EnYwydzIC7qQXEc89hannW7dPpAVwJ4tAtrTyJElO ayytJ5IkB1usbTJ2cgPUSS8i6urGMycpaWdLK0JO7ucgJ3cBOUlpX5Ydw6WQk0lHTiaEnPRiwsV+ EpCTlLa3pfXxY1EEsqWVh0hyWmNpPREiOdgAE3YZOVmaeCnjxYQps/PISU7b2dKKkJObM/OHX9Qm QCQprTWpnncUYrCUiYuMnCxNvJenFxO+PBd+zc9pO1taQR2oCA62tPJVI05rLK2Xwk4GVGi1vQ2I HenFhL0NAg2S0p6ZMq+sk2WwLZErdyUyvylBSY0BVoYjjpwu64GF1s98UWC/k/s4rx+4V353lNO2 MMAi7uRWy53cBO4kpTWW1ps7eYSlVcZOLoA66UVEXV145iQlbWFpBcjJIpAtrTxyktO+zJbtRk4e UV6YdOTkhJCTXkw4qQ8CcpLSNvDnrQg5+SxQV4argJyktMbSeiBy8sIpk2XkZGnipYwXE6ZM5pGT nLaJpRUUU0IlcjIGHjnJaY2l9UZOHuIp0JGTESEnvZjwIYoCcpLStrC0glOLRaBbWvlKNKW1ltYh Dk70T4JNBkmWJl4SwJhttsE3/vg0p21gaQUn6vfKA/U7f56ekhpL64Gnoa/r0UuzDqmcAZ3DjQl7 O/O8DU7bYOkPmC2pEtmSeGILJTWWVmeqeI8uL02qJ3Inj+9tq/Hrh/WGPPsE3EkvIl7A8FPPN8+d TAvgThaBbmnlURuU1lpab/uE98qVsZPom6l9jQg9rcPRnpotE0BOFoGaLROPnOS0ZkvlRk661cCk IycTQk56MeFiPwnISUrb2dIKkJNFIFtaeYgkpzWW1hMhkoMNMGGXkZOliZcyXkyYMju/gOG0A5mN woYAlVvlEvipIf8morTGAHsl5GRcZORkaeK9PL2Y8OW58CUyTtvb0gp4M/GUImuIfJGV0xpL64mQ yu4pkwIqtNreBsSO9GLC3gaBHUlpu6ZMBntzGW33NUmYzO/jUVJrab3QbRNpPbfQCiwC3Md5/Vx3 5Q0FnLaJpRV8N1std3ITuJOU1lhab+7kEZZWGTu5AOqkFxF1deGZk5S0haUVICeLQLe08mM2pbWW 1iGcE4NlS5h0+82EkJNeTDipnwTkJKVtYWlFyMm1Fjm5CshJSmssrTdy8hBLq4ycLE28lPFiwpTJ PHKS07awtIIjWEUg7wjzh6o4rbG0HoicvG7KxKgjJyNCTnox4UMUBeQkpW1haQXng4tAtrTy54M5 rbG0HoidvHDKbDJ2sjTxUsaLCVNm4wECnLaFpfXxg7BXMih2HkFBSY2l9dzT0BdJlzTr2MkZAG3c mLC3Mw+04bQNlv4Ac5QqKUeJhxxRUmtp7bvs1xJhlAL2PJ1Iqeze2yhzJyPgTnoR8QJGWL+8MfuE fSIWwJ0sAtnSypMkOe3L59/7ZPdQ+mGVsZMroE56EVFXV545SUl7W1rB8wPfyW2en4kHVHJaY4A9 EVDZPVuCN3F6ZGlFyMnayVgQZmOctrOlFczQI5z1tznRKcznOa01wF7IPRG8pfkjSytY7bsxYcoI 631O29efh2pAAdaV2vjzhIoRpzWW1ishJ6NX/n1kaQUlZTcmfB0KJWVO29nSCnYaQu1OQxB2Gjit Mam+K5Bk07NGydtkfGRpRezI2o3LJGxcctq+llawnQ13yNtYWvmt75qd71WHI77l5ELp4tlYjrK0 gvOd1Md5/WJY8OBw2haWVsSd3Gq5k5vAnaS0L8tqkSmB3Ztb6tcqYydnQJ30IqKuLjxzkpI2yJYE kJNFoGZL4pGTnNZYWg9ETl6XbhQmHTk5IeSkFxMuASYBOUlpm1haASjNO08CV4bCCRFOayytN3Ly EEurjJwM6FibGxOmjHBUjdO2sLSCw46x9rBjFA47clpraR3i4ET3JIjw5LJ9LNBpaByzzQaFcBqa 07awtIIj9aH2SH0QjtRzWmNpPRA7ed1RJnp8jEeWVsDccGPClBGYG5y2gaUVcFtqsS0CtaUG2rLG GztJmlR17CSiOuGYbV4OAgOK07YolIGVfyUYTOCC1WDB1s0pSLyxdBlsdJk9IuC7fJUEmTsZQF+9 iHAg5XtKSfua9DLiTnosVPhEZIE7SWmNpfVE7uRg74ZVxk6uYGzxIqKurvzYQkk7W1rR5MTjbMMn YhKmG5TWmFRv5KQ7tnh4+0eWVoScrEXmB4GZz2k7W1rRghbezdDI0iosf2tuXVjWKyEng3eBykNL K6iP1V7KEoRbWThtb0srmLmec69PEO714bTG0nol5GT0Lul6ZGlFuzC1F39F4eIvTtvZ0oo25+Ad c40orcJWXs3tcXm/FHbSuwrykaUVsSNrr5dMwvWSnPbMlHmlPQZdUVp7Q6lwQWnN/aSrDkccOV28 y4YPKrQiI1rt3cdJuPuY07aovSOS5OaQJFsvhgXuJKW1ltbj7BPXNenN8hM3A+qkFxF1deaZk5S0 haUVmeNTJXLyqSFfhKa05me9kZOHWFp15OSEkJNeTDipnwTkJKVtYWlFyMm1Fjm5CshJSmssrTdy 8hBLq4ycLE28lPFiwpTJwkFQStvC0orOB4fa88FBOB9MaY2l9UZOHmOAlZGTESEnvZjwIYoCcpLS NrG0gkr0UkuhWAQKBaU1ltYxsJP9k2CTQZKliZcEMGabPb1NwNRQ2gaWVoA62itJRzsPOqKk1tJ6 H5rgLK06SHJGIDQYs5GlVQChUdoGS39A0kuVJL3Ek/Qo6ct0WZliX/90GWxClvYTKZXdextk7mQA 2eJFhLMxPlso6UAbWymjl3N2Xs7w+cnC65bSGgPslbiTq4ydXMFUzIuIurryUzFK2tnSiqDw0ylz +ac/w+9rUVprgL2QcyIkHTmZ0GLfiwmHlyQs9iltZ0srqgHNtTWgWagBUVpjUj0RIjnY5PNpZiPv Oe3oFiMvJjEj4/ecKG1nSyvaadjQ7kUjS6uwL0FpjaX1XQEqUe1wkZGTpYn38vRiwpfnImxcUtqB ljEhot3vWLv7HYXdb0prLK2Xwk4GVGi1vQ3IHuPFhL0Ngj2G0nYdZTJwTGXmw7x6jMm8v4qSvlwH 63DEkdMln1pozcjkSX2c1891s2DypLRNKvXA7rvX2n13we5LaY2l9UDu5HUXTLOMnZzBKQIvIurq zJ8ioKRNLK3gIUi1x1CScAyF0pqfdQzkZPfnP0w6RHJC59RgzDbr4Ek4p0ZpW1ha0WHHtfaw4yoc dqS01tI6hHtisAEmZBlQWZp4CebFhCmThdPQlLaFpRUcqS8C2dLKH6nntMbSeiBy8rrHjGLUkZMR ETq8mPAhigJzg9K2sLQicMtSC25ZBHALpTWW1jGwk4ONMnGTIZWliZcyXkyYMhvPgeK0DSytAA22 V6LBdh4NRkmNpXUM7GT3BEizDpKcETYQxmxkaRUgg5S2RaEMPAiVz8HMPwaU1PirnEuW7gnZ6yyt J1Iqu/c2yNzJAAYXLyKcjfGDCyXta9LLiDuZa7mTWeBOUlpjUr25k+4rV8ZOrmDx4kVEXV35pQsl 7WxpBQvaIjjY0sovfzmtsbReCjmZdORkQshJLyYcXpKAnKS0vS2tz4/F65LgRTjZACvc60NpjQH2 SsjJsMvIydLESxkvJkyZnd+F4bSdLa1oK2+rvQ9uEzbnKK01qb6noxCtRu3vX12LjJwsTbzXoRcT vg4X4XpJSts3ZSK6dTTW3joahVtHKa0xqb4rkGTTlEkBFVrtdxOQmcyLCb+bIJjJKG1fSyu41zpX 3mu98vdaU1JjUtXLppdJl3xgofUzpaMNlY6Yj/P6xXDehUITo21RqUfG+r3WWL8LxnpKayytB3In r1utn2Xs5AzO3XgR4W4Pf+qGkrawtIKTW0UgW1r5k1uc1lhab+TkIQZYHTk5oYOgXky4BJiEo52U toWlFSEn11rk5CogJymtsbSOgZzsnwRZhkiWJl4SeDFhEmQeIPBQq72KWqZMABSKIpAtrTyFgtMa S+sYyMnBRpkYdUBlRIBKLyZ8iKKAnKS0LSytAHRUBLqlla9EU1prab0PThxhaZUhlaWJlzJeTJgy G89B47QNLK0ApLdXgvR2HqRHSV+W1cIY2MnuCZCSDpJ8buIub1HMNi+HtPMFbEr7+nSZp8eLtud/ V4scgV6yUVJjaV3vZf8RltYrcSeDzJ0MaDpWOxsTJmNvnzuZEXcyV07RnxoK8IyKKfq8nEiSHOzd sMrYyRWs972IqKsrv9qnpJ0traZiVFmheRFOza2Jry9xWmNpPRFQ2T1bQtKRkwkhJ72YcHhJAnKS 0na2tIKdhiKQTar8TgOnNSbVEyGSgw0wYZeRk6WJlzJeTJgyO79xyWnPTJnXIic3hJzcapGTm4Cc pLTGAHsl5GRcZORkaeK9PL2Y8OW58M4YTtvb0gp4M/EU6GSIPHWS075Mme1S2MkJFVo/M0VH7Egv Jp50CzRISts1Zdbp8fe0Iqd1k4RZJ/o7paTWAPuejligdMmnFlqf/5pbOmI+zuvnunnjv1ZK28TS iugTtdzJXeBOUlpjaR2DOznYgmmWIZUzONjmRYS7PfyxNkrawtIKDjsWgW5p5cdsSmstrbdz4ghL q46cnBBy0osJJ/WTgJyktC0srQg5udYiJ1cBOUlpjaX1QOTkhVMmy8jJ0sRLGS8mTJnMMzc4bQtL K6C2FIFsaeW5LZzWWFpv5OQhllYdORkRctKLCR+iKCAnKW0LSyvCgi21XLBFAINRWmNpvbGTrElV LktvADuJYzZ5QTz9GX6qQmlbWFofPwh75XMQJv454LTG1HrqeehxE+ZpmSgXpZ+buAtcFLORqXUT lsOMtoGpNYAyR6gscwS+zMFIral1iIV//3TZb/Kkv2aTTRQIm19LzReg+W+NPPlaTgJaBafaVXAS VsGc1lhgr0Se9Cpaj0ytj+eptTUyoURWUyE73dQKnojawmkSCqec1thUT8RIjja2eHsmj0ytCDpZ uw8ThH0YTtvZ1Ar25mLt5lwUduc4rTW13qcmvJTxNuUfmVrBRr8bE6aMsNHPaQeakz19NIDm2GoR lZuAqKS0xtT6rhCVqHq4yNDJ0sR7eXox4ctz4aGTnLazqRVQJ4tAHo557iSnNTbVGzzpFkQmVGj9 zBQd0SO9mHiKLvAgKW1fU2t4/GpZ0YGDNqbWQL+GKKkxtcp4xLecXChd8qmF1ue/5haDmI/z+rlu XulpCqdtYWpF5MnaA1xJOMDFaY2p9SZPHmFqlcGT6DRo7WFQ4SxozVHQKlMrOCGcak8IJ+GEMKc1 ptYxoJODZUvwjvs/NLWCdXAtQiAICAFO28TUCuBntRSKKGAoOK0xtd7QyUM2SGXoZEBEGzcmTBmB aMNpW5haAeUo1mKOosA54rTW1DqEg2KwlIlRh05GBJ30YsKHKArQSUrbwtQKqJNFIJtaee4kp32Z MssY4MnRUmaVMZWliTtVcWLiqQoPnuS0DVJmAuTJIpCnoTx7ktMaW+sY8MnuSZCSjpN8buIucVHM VrZW4eISRtvA1hofvx+e/10tdET67UBJja01D7H0758u+02fdFdtMn0S3TZRe9mEcNdEzVUTZ7Na QTEo1d5XkoT7SjitKRSfyJMcLFu8u4ce7HKCynLtbUbCZUY1dxmdbWsFWw2p9oqrJFxxxWmNrfUG T7pji3e73SNbKwJP1t6YF4Qb8zhtZ1srQElG6Dxoc65TuHWR0xoT7JXAk8G7PvWhrRXUyGqvZA3C layctq9Hb0PgSeiEawOe3ATwJKV9WXr0vIbvMmXiLIMnSxP35VkJnnxqKJwJePPgyZAAeTJAB3Wb lEk8e5LTWhPsleCTEyq0fmaKjgiSXkw8RReYkJS2r601Ph6N4ZmeNrbWyJ96ZKRmHSwjEkdOl3xq ofX5r7mlI+bjvH55mDNvXaO0LWytiD6519Ind4E+SWmtrfW2UBxga5XhkzM4Qu1FhLs9/AFqStrC 1grO1BeBbGvlT9VzWmNrvcGTh9hadfDkhMCTXkw4qZ8E8CSlbWFrReDJtRY8uQrgSUprbK03ePIQ W6sMnixNvJTxYsKUyTx4ktO2sLUC8GQRyLZWHjzJaY2tdQzw5GApE6OOqYwIU+nFhA9RFMCTlLaJ rRV5KGrRk5n/bTmtsbWOgZ4cLWVWGVRZmrhTFScmnqrw6ElO28LWCtiTRaDbWvnaMqW1ttZ75X+E CVaHVT43cRfETky8IF753lLaBrbW9HhIff53tdCR6AGVkhpb6zLE0r9/AuwnEiUHezkEmT8ZQK3M iwiHF75SRkl721rB85Nr+ZNZ4E9SWmNrvfmT7itXxk+uYB/Gi4i6uvK7MJS0s60VoCeLQLe18rtV lNbaWu8jE97YknT0ZELoSS8mHF6SgJ6ktJ1trQAmGeEtsY1srTx6ktMaW+uV0JNhl9GTpYmXMl5M mDI7j57ktJ1trQg9Ce8hb+PR2wVQJaU1ttZ3BapEFcFZRk+WJv7Ls3LzcubRk5y2s60VsCeL4GBb K0+f5LTG1nop/OSECq2fmaIjhqQXE0/RBSokpe1sa338VKzoGFwbW2uinyBKamytMiRx5HTJpxZa n/+aWzpiPs7rl4d54ZfOlLaFrRXxJ/da/uQu8CcprbG13vzJQ2yt6kg2A+CAFxHu9vC4AUraxNaK dvEqERQp8QwKTmtsrTd68hBbq46enBB60osJJ/WTgJ6ktC1srQg9udaiJ1cBPUlpra31dk8cYWuV 0ZOliZcyXkyYMplHT3LaFrZWgJ4sAtnWyqMnOe3LlNlv9OQRFbmgoycDQk96MYmHSPBGn4SezAg9 mWvRk1lAT1JaY2u90ZOkUVVGT5Ym/uTjjA2KuPLoSU7bwtYK2JNFoE9DhdNVNfjJMAZ+crBR5mld KRexn5u4C2InJrEgFs55MtoWtlZwfjfVvTrnmf5hKamxtc5DLP37J8B+8yfdVZvMnwygsuxFhMML X1empJ1trYg/mWv5k1ngT1JaY2u9+ZPuK1fGT66APulFRF1defYkJe1sawXoySLQ98z53SpKa2yt J8IkB8uWkHT0ZELoSS8mHF6SgJ6ktL1trY8foiLQnVn0Y8FpX6ZMPhEmOVrKbDJ6sjTxUsaLCVNm 49GTnLavR29H6Mn9HPTkLqAnKa21tV4IPRlnGT1Zmrgvz0r05NNbV3h5vnn0ZEiAPVkEB9taefok pzW21kvhJydUaP3MFB0xJL2YeIouUCEpbV9ba3q54NNy4cXy0DliCpeHM788ZKTG1ipDEkdOl3xq ofX5r7mlI+bjvH6umxeh0MRoW9haEX9yr+VP7gJ/ktIaW+vNnzzC1irjJ2dAn/Qiwt0enj1JSVvY WgF6sgjkXTwePclpja31Rk8eYmvV0ZMTQk96MeGkfhLQk5S2ha0VoSfXWvTkKqAnKa2xtd7oyWNs rXIROwP0pBsTpkzm0ZOctomtFRRTQuXEPkb+t+W0xtZ6oycPsbXq6MmA0JNeTPgQBQE9SWlb2FoR ejLXoiezgJ6ktNbWeh+eOMIEK6MnSxN3qlKJnowrj57ktC1srYA9WQTyNJSnT3JaY2u98ZOkUVXH Tz43cZe4KGabF0Ra+CI2pW1gawV1xNkpI8JCB18XpKTG1urYbe90eWlrvfmT7qpN5k8GwJ/0IsLh hedPUtLOtlbEn8xoH7XVTXICcqOCVjkvJ9Iqu2fLKuMnV0Cf9CKirq48e5KSdra1AvRkEch75jxM ktMaW+uJMMnhxhYdPfncxB1datGTSUBPUtrOtlaAniyCY092Ljx6ktMaE+yV0JNPz5C877QB9KQb E6bMxqMnOW1nWytCT+7OEQX4Re0CTJLSGqPqiTDJwUaZOMvoydLEfXlWoiefGgrw6jePngwJsCeL 4GBbK0+f5LTG1nop/OSECq2fmaIjhqQXE0/RBSokpe1ra50ff08rOmLdhtY6098pJbW21gut+lM+ tdCaAWWB+zgNSkc8lYHTNrG1gu9mr+VP7gJ/ktIaW+vNnzzC1irjJ2dAn/Qiwt0enj1JSVvYWgF6 sgh0Wys/ZlNaa2u93RNH2Fp19OSE0JNeTDipnwT0JKVtYWtF6Mm1Fj25CuhJSvuyUJZu9OQRKbPI 6MnSxEsZLyZMmYVHT3LaBikTAXqyCGRbK4+e5LTG1joGenKwlIlBB1UGBKr0YsKHKAjoSUrbwtaK 0JO5Fj2ZBfQkpTW21hs9eYytVS5irwA96cbEUxUePclpm9ha0TS0Ej4ZJr7OwWmNaWQM/ORgKZOS DqtMoDjrxsQLYr7gymkb2FpBxX6uLNjPfL2eklpb6xBL//4JsN/8SXfVJvMnA+BPehHh8MLzJylp Z1sr4k/mWv5kFviTlNYYVW/+pD9DUSefK6BPehFRV1eePUlJe9tawfMzVaIn08SjJznty8rIdKMn /bFFR09GhJ70YsLhJQroSUrb19a6APRkERxta+UPQ1Naa2u9kIMibDJ6sjTxUsaLCVNm49GTnLaz rRWhJ/dz0JO7gJ6ktMYEeyX0ZJxl9GRp4r08vZjwdTjz6ElO29nWatiTL1ImoROjjWytPH2S0xpb 66XwkxMqtH5mio4Ykl5MPEUXqJCUtq+tFeAD1lPoASsPD6CkxtYqQxJHTpd8aqE1Ay4J93FevzzM PMWE07awtSL+5F7Ln9wF/iSlNf7Lmz95hK1Vxk/OgD7pRYS7PTx7kpK2sLUC9GQRyLt4PHqS0xpb 642ePMbWKqMnJ4Se9GLCSf0koCcpbRNbK0Kg1aInhd+W0xpb642ePMTWKqMnSxMvZbyYMGUWHj3J aVvYWgF6sgh0WytfW6a01tY6hINisJSJQUdPBoSe9GLChygI6ElK28LWitCT3hIPviCERRunNbbW Gz1JGlVl9GREtSMcs82enlA94rQtbK2g/hhq649BqD9yWmMaGQM/Odgok+DWw2cWxGA7w42JF8T8 BgWnbWBrBZtctXtcwhZXzQ7XujpHOt5YuvRPALhd/bC3r0v3N/7dBJk/GQB/0osIhxeeP0lJO9ta EX/Sc+vg3QaBP0lpja315k+6r1wZP/ncwtvlrIRPrjx7kpJ2trUC9GTyzKPwiQg8TJLTGlvriTDJ wbIlRB09GRF60ouJhxcBPUlpO9taDXpSezxeLJi9swxwCbzwoEpOa2ytJ4Iq+6fMJqMnSxMvZbyY MGU2Hj3JaXvbWsHMFR5/a2RrFdCTlNbYWq+EnozeqdNHtlZwkNWNCV+HwlFWTtvZ1gqONwd4ZLqV rZXfzqs5DP20ULrQ4YnkkQ0eTdERQ7KWlpAEWgKn7WtrBQwNiOVoY2vleRs1uI1VhySOnC4eO+eg 0hFA+XAf5/XLQwH8w2lb2FoRf3Kv5U/uAn+S0lpb622hOMDWKuMnZ0Cf9CLC3R6ePUlJW9haAXqy CORdPB49yWlf/qzrgehJ6sl+lyPZLpMndwCe9CKiru48dpKSNrDnbYg6udVSJzeBOklpjaP1pk4e 4miVqZOlibdg9mLCJfDCUyc5bQtHK5iqFoHsaOUnn5zWOFpv6uQxjlaZOhkQddKLCR+iIFAnKW0T RysoQnt3ccAXhHC7Bqc1jtabOnmI/1WmTkZ0JZAbE6aMcM0Pp23haAXV+lB7UVQQLoritNbROsSi v3sSJHjr22dWt2A7D8ds84IQbpLjtA0crWBLuPYyQuEuwpqrCNfVOQB1p8tLR+uNnnRXbTJ6MgD0 pBcRDi88epKS9na0gufHu1YZbzQI6ElK+7KYCC+uvm62ZJk8mQF40ouIupp57CQl7ZstAVAni0B3 tPIbVZTWOlrPs0IMli0h6tTJiKiTXkw4vESBOklpOztaAXWyCI491Lnw1ElOaxytV6JOhk2mTpYm Xsp4MWHKbPyRPE7b2dGKqJN75THNsAscSUprPKonciQHG2XiLFMnSxPv5enFhK/DmT/1zWk7O1oB OqAIDna08ugATmscrZciT06o0Gp7OyF8pBcT9nYSgJCUtrOj9fFTsSKITRtHK0+noaTG0SrzEUdO l3xqoTUD8BX3cV4/cGcek8VpWzhaEXpyr0VP7gJ6ktIaR+uNnjzE0aqOZDMAT3oR4W4Pj52kpE0c rWjPr/aVOws/K6U1jtabOnmEo1WGTu6AOelFRF3deeIkJW3haEXAya0WOLkJwElKax2tQxgnBsuW sMjAydLEWzB7MeESeOGn9Jy2haMVLAqLQHa08otCTmscrWMAJwdLmRh0PGVAeEovJnyIggCcpLQt HK0IOJlrgZNZAE5SWuNovYGThzhaZeBkaeKljBcTpszK72Rw2haOVrTBNdVucE3CBhelNY7WMaCT g6VMSjqiMoH9cjcm7G3id8A5bQtHKzi1W2mimHkPBSU1jlbnzOAbS5f+CbDf1El31SZTJ59buONL 9fAijC5vfF8rZUSdzLXUyVWgTlJa42i9qZP+xrc6+cyAOelFRF3NPHGSknZ2tBrg5IvnJ6AzCW2e n8ADJzmt8b9eCjgZdeBkRMBJLyYcXqIAnKS0vR2tjx+LIjjY0cqfUOO0xtF6JeBk2GTgZGnipYwX E6bMJhxhpbSdHa0IOLmfA5zcBeAkpbX+1wsBJ+MsAydLE+/l6cWEr8OZByVw2s6OVsDPKIKDHa08 bYPTmon9paCTEyq02t5OiBzpxYS9nQQWJKXt62gFkKYVcZ/aOFp5oBMlNY5WGY04crrkUwutGbDi uI/z+sVw5slynLaFoxVRJ/da6uQuUCcp7cuyWjiQOnndilySqZMJUCe9iPgJEizR5xCNZ/QmmSup k2kW3g2U1jhab+rkEY5WGTq5g+mMFxF1decnKJS0haMVASe3WuDkJgAnKa1xtN7AyWMcrXL9ekEL Zi8mXAIvwhKY0jZxtII6Sqyto0ShjkJpjaN1DODkq5JAS7gmxbigAycDAk56MeFDFATgJKVt4WhF 1fpcW63PQrWe0lpH631u4ghHq4ynLE28lPFiwpRZhe08StvC0Yr2hKfaPeFJ2BOmtMbROgZ0crCU SUlHVCZkMfFiwt4mwTRCaRs4WoHraK50Hc2864iSvkyXzDyf/dOlfwJsN3XSrXHIh3bBmd3aI7t8 feONb2mlFQEn11rg5CoAJymtNbPewElvPi/zJjM4KOFFRF3N/EEJStrZzIrOzoTaszNBODtDaY09 9UR65GDZEqLOmozoKJ4XEy5conAUj9J2NrOiE5pL7QnNRTihSWmNPfVmTbops8msydLESxkvJkyZ TTjwTWk7m1kRa3I/hzW5C6xJSmvMrFdiTcZZZk2WJt7L04sJX56zgBWhtL3NrIA2k06hTYYksGko rTGzXoo3OaEaq+3thKCRXkzY20nAQFLavmZWwDNbESGtkZmV/k4pqTWzXui4RFpOrbEu6IuiPs7r 57pZ+FopbRMzK/hu9sqH6OmB5skTlNaYWW/g5CFlfXkkAy9oLyLuKj+MnQOcTDMas+faMXsWxmxK a82st3HigI0emTe5gwWAFxHu9fATekrawsyKFoVb7aJwExaFlNaYWW/W5CFmVpk1WZp4C2YvJlwC L0LViNK2MLOia25i7TU3UbjmhtIaM+vNmjyiGBd01mRAOxleTPgQBWEng9K2MLOiDa5cu8GVhQ0u SmvMrDdr8hgzq1y/XtHdjF5MmDKrcNsipW1iZgVF6Kn2ys5JuLKT0hoz682bJO2pOm8yIYsVjNnm BZEEQxalbWBmBQa9udKhN/MWPUpqzaxDrPr7p8t2AyfddFEnoMD4Xen75m3fb581uaKDAGvtQYBV OAhAaY2Z9UR65GCJkmXUZAaniryIqKuZP1NESXubWcHzEypPmqXAnzTjtMbMisCR1JP9LofcEHXM ZEQHV72YcOEShYOrlLazmRWdZ15qzzMvnzuj/LoX9bP1Vf9al3wlzGTYZMxkaeKljBcTpszG4xE4 bWczK6Jm7LXUjF2gZlBaY099V+DIVrO+7190s4yZLE28l6cXE748ZwHCQ2k7m1kBmKkIDjaz8iAn TmvMrJdCTU6oxmp7OyHKmxcT9nYSKG+Utq+ZFYD/VoQSbGNm5TGBlPRl1bECiDhwuiyn1lgXRB+l Ps7riymLwCqltA2K9OgtNNe+hWbhLcRpjZn1Zk0ekZsyaxJNabyIRFeFnp6RLQlNc1PtNDcJ01xO a8ysN2vyEDOrWktBa+baJbOwYq5ZMNeZWQHurLaOEoU6Cqc1ZtYxMJODZUvwSqiPzKzo9p/asmyg iqf/YWY9BzMZUbU+1lbro1Ct57TWzDqEb2KwlIneRt0jMyvCTNZu/kVh84/TtjCzIsxk7Y5wELaE Oa0xs96YyUPMrDJmMiJ3iRsTpozgLuG0LcyswG5UBLKZlbcccdqXdbJpDNTkYCmTog6mjOiqbC8m 7G0SrsqmtK9PmQXcnv7872JfF/72dEpqzKzbEKv+/gmw3cBJ9yFSkwUclag8KMEfk3j7rEl0dibV np1JwtkZTmvMrDdr0p3Py6hJdBCv9hyecAyv5hTe2WZWcDgzwQOfbZ4f4SgnpzXW1xOhlN2zJXjn sh+ZWRFmsvasdxDOenPazmZWgACItQiAKCAAOK2xp54IjhxsgAke/eOhmRWUx2qJIkEginDa3mZW 4PqF4JpGZFYBM1mDpcnxSpjJ6OGlHplZAbLKjQlfngKyitN2NrMCjFmAZLRWZlZ+J6+Ge5a3K6Em o8cvfJAyiInoxoS9FZiInPbMlHnlUbXnx875Vr3HEpZSJnrkpqTGzKoDEcdNl7ScWmN9/mveF0V9 nNfPdZeNN6xR2hZmVjBwz7V86FngQ3Naa2a93RMH5KbMmkSweS8iUZgV6rJnZEtCFxCk2gsIknAB Aac1ZtabNXmEmVVGTaLbTLyIqKvC7SQ1l5NUmVkRZrL2hpso3HDDaY2Z9cZMHmJmlTGTAV2Y5caE S2DhwixO28LMCna3Yu09alG4R43TGjPrGJjJ7kkQvUsRH9pTATgSxmzygojCtYyctomZFRSha+/q DMJlnZzWmFnHwEwONspE747eR2ZWAKV0Y8KUEe795bQtzKyAM1kEupmVLytTWmtmvRf9R5hZ9bXw cxPvu/Fiwt7Gne8tpW1gZg2PB+Dnf1fNrIEeUCmpMbOu96r/COvriXjK7r2VeZPgdFHl2SL+ZNHb Z02uiDW51rImV4E1SWmNmRWxJq/7WsgyajKDs6teRNTVzJ9cpaSdzazgPHMRqNkS+PPMnNbaU+8z El4xMOqYyYgwk15MuHCJAmaS0nY2swJkRhEcWzBaeMQGpzXW13cFpUQps8mYydLESxkvJkyZjefv cNrOZlaEmdzPwUzuAmaS0hoz65Uwk3GWMZOliffy9GLC1+HMA944bWczK+BMBohobGRm5UmTnPZl ykBg5rtKmR3VWG3K7IAX6caEKbPzBEhO2zVlnhG/zvcEEcBNEmYL9BNESY2ZtQKIOGy6pOXUGuvz X/O+KOrjvH55uKz80pnStjCzgrluEchmVn6uy2mNmfVmTR5iZpXLL2Dh7EWEXeUXwpS0iZkVPARz ZTElzXwxhdMaM+vNmjzCzCqjJndQmfUioq7ufF2WkrYwsyLM5FaLmdwEzCSltWbW2zNxhJlVxkyW Jt6C2YsJl8ALv+/HaVuYWcFGcBHIZlZ+M5jTGjPrGJjJ7kkQgw6ODAgcCWM2MrMKmElK28LMijCT uRYzmQXMJKV9WSObmdd6/5QZbJSJWcZMliZegnkxYcqsPGaS0zZImQA4k0WgpkzgSZOc1hirxkBN DpYyKepgyucm3nfjxYS9jRu/8Ke0Lcysjx+E539XzayR/mEpqTGz5nvVf4SZ9UQ8Zffe6rxJgJus pU2yvXz7rMkVsSbXyhOaaRXokZTWmFlPpEcO9lrIMmoyg+PeXkSYK/xhb0ra2cwKzv8XgWxm5QkA nNaYWW/MpFsMjDpmMiLMpBcTLlyigJmktGemzCsBYHEBOJoiUFe/Cw+k4bTGzHolzGTYZMxkaeKl jBcTpszG06o4bWczK8JM7udgJncBM0lprZn1SpjJpGMmE+itGxO+Dme+t5y2b8rMgBxZBMemzMyT JjmtMbNeCTUZd1RjtSmzA16kGxOmzM4TIDntmSmjPejma93C4+Xh5kx+0Je6RXp5SEmNmVUHIo6b Lmk5tcb6/Ne8L4r6OK9fHi4rX2iitC3MrGB5WASymZVfHnJaY2a9WZOH5KZcfkG1ptpSk1BpOoc1 mWZQfCwC2czKlx85rTGz3qzJI8ysMmpyB/sYXkTU1Z3fxaCkLcysCDO51WImNwEzSWmNmXUMzORg 2RIWGUpZmngLZi8mXAIvPGaS0zYxs4I6SqzETMbIYyY5rTGz3pjJQ6yvOmYyIMykFxM+REHATFLa FmZWhJnMtZjJLGAmKa01sw5xZKJ/EmT9TZoBOBLHbOP/zjxmktO2MLMCzmQRyGZWnjTJaY2ZdQzU ZPeUSVGHRz438XoLY7YZU+PKL/wpbQMza3y8anv+d9XMmuhVGyU1ZtblXvUfYWY9EU/ZvbcybxKc Ya08wcqfX337rMkVsSbXWtbkKrAmKa01s96sSW8+L6MmM4AjeBFRVzOPRqCknc2siJYRTsFMPv0Z /pANpTXW10thJqOOmYwIM+nFhAuXKGAmKW3XlIkLwEwWgWxP5cGRnNbYU08ERw42wIRNxkyWJl7K eDFhymw8ZpLTdjazIszk7uAZ4Re1C+BISvty3hFOBEcOljIx6ZjJhDCTXkz48kwCZpLS9jazAtDM fApoMsw8aZLTGjPrlVCTcUc1VpsyO+BFujFhyuw8AZLTdk2ZLT7+nja0AmhDZo30d0pJrZn1Qscl 0nJqjfX5r3lfFPVxXj9wL5n/WiltEzPr4++mCGQzK19Q4bTGzHqzJo/ITZk1mVBltrYwK9Rlz2FN phnU6YtAN7MKna2o1s/rzZo8wswqoyZ3QJr0IqKu7jxnkpK2MLMizORWi5ncBMwkpTVm1jEwk4Nl S1hkKGVp4i2YvZhwCbzwmElO28LMCjCTRSCbWXnMJKd9mTLbjZk8orIw6ZjJCWEmvZjwIQoCZpLS NnDmrQgz+SxQXxCrgJmktMbMemMmj7G+yvXrDDCTbkyYMpnHTHLaJmZWUIQOlaDJEHjSJKc1ZtYx UJPdkyBFHR753MTrLYzZyMya+bUwpW1gZk3AoJcqHXqJ7ioltWbWIVb9/dNlu4GTbulInYCCE9+V 5735095vnzW5lvP/r3sYXoSTra8CL4DSGuvriWTK7omSZdRkBigRLyLqauZBIpS0t5kVPBEBkYAa mVl5zCSnNWbWS2Emo46ZjAgz6cWEC5coYCYpbWczK8BMFsGxRzkXHjPJaa319UK+iQBnlJ8pj4He ujFhygi95bR9U2YCmMkiODZlJh4zyWmN9fVSmMmkYyYTwkx6MeFvmwTMJKXtbGYF5MgiUN8tM8+O 5LTGnnoiPHKw9X7cUY3VpswOeJFuTJgyO0+A5LRnpswrkflbevwi2pzVNfpSt0S/hiipMbPqQMRx R5i0nFpjff5r3hdFfZzXv4WWhZ6mcNoWZlZUeZwqa4/zxFcfOa0xs96sySNyU2ZNJnRnVu2VWcKN WeewJtMMWJNFIPeVZ01yWmNmvVmTh5hZ1VrKDkiTXkTU1Z3nTFLSJmZWAEfbajGTm4CZpLTGzHpj Jg8xs8qYydLEWzB7MeGCeeExk5y2hZkVYCaLQDez8mVlSmvNrEP4JgZLmTjpD9GEoJReTFxoFTCT lLaFmRVhJtdazOQqYCYprTGzjoGZHC1lsgylLE28lPFiwpTJPGaS07YwswLOZBHIZlaeNMlpjZl1 DNRk9yRIUYdHPjfxegtjtjKz8gt/StvAzDo/fj88/7vq0JvptwMlNWZW53O9sXQZbIRJ24l4yjfQ W7WvoKeVdASejfDWjRNpRazJ1WGbwIdhFeiRlNbYU0+kRw72WsgyajID0qQXEXU185xJStrZzAow k0WgZkvgMZOc1thTb8ykWwyMOmYyIsykFxMuXKKAmaS0nc2sADNZBAebWXkoJad9mWCwH+9pJhZW GTNZmrjlsUrM5FNDoTz25jGTcQKYyQjf5Y3MrDxmktMaM+ulMJNJx0wmhJn0YsLfNgmYSUrb2cwK OJMBLhYakVl50iSntdbXC633445qrDZldsCLdGPClNl5AiSn7Zoyz4Uj53uChaU2ZNaZHrkpqTGz 6kDEcdMlebXfg8ysoBLNfZzXLw+FyjWnbWFmBazJItDNrPQIw2mtmfV2TxyxCyaXXwBr0osIu8qz JilpCzMrYE0WgWxm5VmTnNaYWW/W5BFmVhk1uQPSpBcRdXXnOZOUtIWZFWEmt1rM5CZgJintyxpZ ZB7PO1vUYtwsYyZLE3fBXImZDAuPmeS0DVImAcxkEch1FB4zyWmNmfXGTB5jZpUxkxPCTHoxcaFV wExS2iZmVoSeqMVMrgJmktIaM+uNmSTtqTJmsjTxkgDGbLM3kXnMJKdtYWYFnMki0M2sfFmZ0loz 6xCL/u4pk6KOmnxu4i7kUcxGZtaF/24obQMzKzgP7x2HR30VzrfXHG9fs5PIbyxdBpuUJQ+J8T5f JfJGHiiS1ZbI+ALZG9/SSitiTXrgIPglrQI9ktIaM+uJ9MjBXgtZRk1mQJr0IqKuZp4zSUnPzJZX 0oxSAFDK5JHp4PMTeMwkp7XW1wt5JkLQMZMB9NaNCRcuUcBMUtozU0ZLns+slRGU0uOf4tWvgJmk tMbMeiXMZFhlzGRp4pbHKjGTTw2Fi4vePGYyTgAzGSE3u5GZlYdSclozSzkRStk9ZWLSMZMJYSa9 mHgTRsBMUtrOZlZAjgzwYoZGZlaeNMlpjZn1SqjJuKMaq02ZHdTH3JgwZXa+QsZpO5tZHz8V8IKg NmZWvsBKSY2ZVQcijpsuybuV6yAzK9i74T7O64spwp1inLaFmRWwJotANrPyrElOa8ysN2vykF0w uaACWJNeRLypxZevz2FNphmwJotArtTzrElOa8ysN2vyCDOrjJrcAWnSi4i6uvOcSUrawsyKMJNb LWayXGmOZ7iU1ppZh/BMDJYtYdaNNzPATLox8RKYx0xy2hZmVoCZLAK5jsJjJjmtMbPemMlDzKw6 ZnJCmEkvJi60CphJStvCzIowk2stZnIVMJOU1phZx8BMjpYyWYZSlibudp4TE6ZM5jGTnLaFmRWc 7i0C2czKn9fltMbMOgZqsnsSPK2I9XU8wAbgmI3MrDw4gNO2MLM+fhCWSvDEwnMnKKkxszpj350u L+2pN3DSHU/lCSiYftYyzvlx9I1vaaUVsSbXWtbkKrAmKa0xszbhk73Ll0iWUZMZkCa9iKirmedM UtK+2RIAZrIIZHsqD47ktC+zZT8RHDnYsBKCjpkMCDPpxcQLFwEzSWn7OvMywkzmczCTWcBMUlpj Zr0SZjKsMmayNHHLY5WYyaeG/MFVStvZzAowk0VwtJmV39uitNbMeqEjEzHpmMmEMJNeTLwJI2Am KW1nMysoGBWBvDfHl4A4rbGnngiPHGxiFndUY7Ups4OKshsTpszOV5Q5bV8zK9hn2E65+2rj9yQo qTGz6kDEcUeYtJxaY13Adif3cV7/Flr4zVFO28LMCliTRSCbWXnWJKc1ZtabNXlEbsqsyQRYk15E XGoSKk2nGCfSDFiTRSCbWXnWJKd9mS35Zk0ekC2bjJrcAGnSi4i6uvOcSUrawJm3I8zks0Ce4QqY SUprzKw3ZvIYM6tcv54BZtKNiRfMPGaS0zYxs6I6SiVmMiYeM8lpjZl1DMzkYCkTJx1KOSEopRcT F1oFzCSlbWFmRZjJtRYzuQqYSUprzaz3kYkjzKwylLI0cTf/nJgwZTJ/CprTtjCzgnP0RSDvCfPn 6DmtMbPeqMlDrK86ajICLIcbE/Y28qANTtvAzApgLUslq2XhUS2U1JhZneniG0uX/gmw3cBJf9Um r9nAiq1ubOEnY2/dOJFWRI9ca+mRq0CPpLTWzHqeFWKwRFlk1OQCvhkvIupq5ntKSftmSwTgyCKQ Zxo8OJLTGjPrieDIwbIlBB0zGRBm0ouJFy4CZpLSdjazIsxkPgczmQXMJKU1ZtYrYSbDKmMmSxO3 PFa5dAkrv3bhtJ3NrGA9WwQHm1n51S+nNWbWS2Emk46ZTAgz6cXEmzACZpLS9jazItDMKaDJMPM1 Vk5rrK9XQk3GHdVYbcrsYBPGjQlTZuc3YThtXzMr2JrbTrkubuO38SipNbNe6LhEWk6tsS7AIcB9 nNcvDxfeT8Bpm5hZH383RSCbWXnWJKc1ZtYDWZPXPV6eZNZkAqxJLyLsKs+apKQtzKyANVkEupmV 7yyltWbW2zhxgJlVfoY2QJr0IsIJCs+ZpKQtzKwIM7nXYiZ3ATNJaY2Z9cZMHrItKmMmSxN3wVyJ mXxqKFxOcg5mMiZw7qoI5DoKf5KK0xoz642ZPMTMqmMmJ4SZ9GLiQquAmaS0LcysCDO51mImVwEz SWmNmfXGTLL2VLkinQE1AMdstJ3HMwY4bRMzKyhCh0r0RAg8eoLTGjPrGKjJwUaZFHUwZQQkGzcm 7G3k2TSctoGZFfCNlkq80cLTjSipNbMOsep/VQJoydYkXTbENXsr302L3sq4yYf9rHRO8L6Jt+6a ePqhwSmAtRY0uQqgSUr7soiYbtCku/6VOZMLwEx6EeGYwkMmKWlvJyt4fqLzLsbTDJ4ayWmNk/VE auRg2RKCzpgMiDHpxcSrFoExSWk7O1kRYzJXzsyfGvLOEkprvan3UQkvZVaZMVmauLWx2oX+Kiz0 KW1nJyuqFk3nVIsmoVpEaY2T9UQiZfeUiUlnTCbEmPRi4h0YgTFJaTs7WcEuQxEc7GTl9yQ4rXGy XokzGXdUYLUps6NNSy8mTJld2LSktH2drGAre0O7422crPy2NyU1TladhjhuuqTl1ALrAhw13Md5 /Vx34f03nLaFkxWAJotAdrLyoElO+7JQMN2gyUOGMn0kQwNZJaqUB01S0gZO1gWAJotA7evCgyY5 rXGy3qDJQ5ysauVlA5hJLyKcoPCQSUraxMkKWGd7LWNyFxiTlNY4WW/G5CFOVpkxWZq4C+ZKxuRT Q75+TWlbOFnR8cZUe7wxCccbKa11sg5hmhgsZeKkMyYnxJj0YuJCq8CYpLQtnKyIMbnWMiZXgTFJ aY2T9WZMHuJ7lRmTpYm7+VfJmHxqKNyNfA5jMgSEagm1qJYgoFoorXGy3pxJ0puqcyYjYDnhmG1e EJFnOXHaBk5WwANbKnFgC08Do6TGyerUI+50Md7U20LxJrZ7PvO1VlqVX/fI8RNd5Qt9/sn4Nxyl NZZTvbY5bvIuzhbFo9c5oGxXbnos/J4HJe1sIkX3rcXaC9eicOMapbUm0tty7RXhgnPR4kMTKbrH ofLyxk/cp8yC4a37rot9011HIltMo/OTiR+/KK2xnMoHrAceYD6p7ghlKXRbkBOTKEvxdWtK29tE ii6RcsyXuFo5018Up7W20HvR4BXhyh6CsPkBXp5eTLz5MfOvQ0rb2USawXA8owMBrUykwsWGjNaa SK/kuy471YKJFNStvZgwZYr7lNlif+u+62dPpue6QIfO2phIN3p5SEmNifRKB6w/sUGdYiKdQHGc +jivH7gX/lA3p21hIgVncj/xd8omUnqE4bTWRHpvwR4ylOkjGRrIKscxYRg7Zfe1/k3S/d0wZwdr fGfLqzZY5BPvtdOZzhOUKhPpsDPcJWbwFryzpc5EKtevqxfM3ZfAdSbSUesoyzbfvutDTKTyRSvj lmXrTKSjVuvznG7f9REmUvn8ev3mH0yZo7fzqkykw+4JrxO6afpOmTrLqWy6GNdiUmUiHdJ1tMLr pt9GuvRPgFU+O12a+L09pax8tCPxZOvahm7yhn7fVl8rj3ygtNboeaEdUs9l/+58+6cbPZ9fQq97 /l+Ek8fsgw9+zPulLvH2TnG9y5NhZxs9aw8MNjd6Hnu8cFmudIm3e1b4XZ4/Pt3oWXksvXHKHH2I PYdLXeLtESneJeXidKNnJfykudHzWFRKXq90kbfLPXq0DT4sS+nQlHnljdODwrjWiuumx00XF6p3 lNGzkvHX2uh5MBGwzuj5eDxy7ZSot5/APGFvOa01et7bpAcMZbo7Bdzk7UUkxjFhGDsjW+q5w/jd cDBJeM73Td6HGD3VWkot/BxOUI7FmdcZPUfl4S/xvsT7EKOnfMa8/noNYgl87IUZVUbPYW9dWbYx LvEeLGXwhUufK8tWXuKEC60HX8tUZ/R8/CS83bu98jzGJd79k8C7qO+hdbPy8r/W23kHXxVYZ/Qc 9QbJdRrjIu/BRhn38thHFpNhL6StMXqOeUfxuoxxGLp/Anh3jT/sLSgrw5htXg5H33Z+utHz8eD0 iavy4HcuPZRxWmv0vNAO6YLOmdtX7vq4r15E+Mrd6J5S0oE2R4vF0h2znV17PGZHvn5Naa3R80Ib pCGgg+afmdTnx8ORGxNP6jM9wHDa3kZPUJbOjtsLr/VmvixNaY11U7465jJLmKclq1xbfm7ilo6c mLh0tPC1ZUrb2ei5gLL0hDzFrYyefBGb0lqj54W80TGhg+af2aBIoLbsxcQbFImvLVPagSZmxWLp 7nI551zwLtfKF7EprTF66tfSDJwyOzpoblPmuYm7De7EhClTHKLENjij7TrKPPsmPWcEOhjZiOhJ f6eU1Bo9L7TqTzOaXNrezqi3XkzY20XoLaXtWyhDB6LPOQ8tHIeuOA29wqR/T+kyT/eV3odYWuVp LjhF4EWEIzZ/ioCSNrG0godgqTyGkhb+GAqnNZbW+0rvIyytcqF1A2favIhwKsafUaOkLSyt6Jzj XnvOcRfOOVJaa2m9nRNHWFrlkmxp4i72K2/zDjN/EJrTtrC0gtP0RSBXjPjT9JzWWFrv27wPsbTq t3lPCM7hxcQlZQG3QWlbWFoRs2WtZbasArOF0hpL6xi3eY+WMlkuspYm7jZnJdQpZh7qxGlbWFoB FqwI5N1vHgzGaY2l9b7RmzWpyqXTiIpkMGabF0QUymSUtoWlFfirKp+DzD8GlNRYWtHd0He6/PDJ KkqnYAsGx2xkaeU3YThtZ0srYiJviLPcaJoiEJQprbG0nnhJd/cEW+RbtxcAWPcioq4uPF6dkvbN lgig+0Ugm1R56D6nNSbVE+/QHmwJE4J+43ZAd3h4MfGkXrjDg9J2trSiq10yui6m0WFH4SIYSmsN sBdyT4RVvnG7NHFLR5U3RYWVvymK03a2tIILxIpArijyF4hxWmNSPfEO7cFGmadRW64tJ3QfoRcT b1AI9xFS2q4pE2ZwR2URHPoQhZm/05LTGkvrlW7djju65tqmzA4uvHVjwpTZ+QtvOW1fSys4Iryd ckJ44w8IU9KXFTn9buiB0yXNCDtpezsDeoAbE/Z25vkBnLazpRU8Fei93GaSIuAnKugTq3459MDp Mk83d/KIQVsutEbAnfQiwhGb505S0haWVsCdLALZ0spzJzmtsbTe3MkjLK1yWXYD1EkvIpyK8cxJ StrC0oqQk3stcnIXkJOU1lhab+TkMZZW+cqkGSAn3Zh4sc8jJzltE0vr4yehCOSKEY+c5LTG0joG cnKwlImTDqicEKDSi4kL0AJyktK2sLQi5ORai5xcBeQkpbWW1vvgxBGWVrnIWpq425yVyMmY+TU/ p21haQVVoyKQd7/5qhGnfZky+42d5IqJQS+dBoSdhDEbVckE7CSlfX3KZLAtkSt3JTK/KUFJjaUV wRHvdPnhk1WUTsGmJY7ZytLKl44obWdLKyJJbuj+x0bTFIE7SWmNpfVK3MlFxk4ugDrpRURdXXjm JCXtbGkFyMkikC2tPHKS0xpL642cdAtlQUdOBoSc9GLiSb2AnKS0nS2tCDmZz0FOZgE5SWmNpfVK yMmwysjJ0sQtHVUiJ58a8utgStvb0grKI5MDkWycMhOPnOS0xgB7KeRk0pGTCSEnvZh4g0JATlLa zpZWcOCxCOR9K/4II6e1JtXzjkIMNjGLm4ydLE28lPFiwpTZ+d5y2q4ps4MT9fspB+p3/jw9JTWW 1ithJ9OMsJO2tzPgbbgxYW9nnrfBafsu/QGFJaGpTCv+BF8lqChgb2hi+Z7SZZ5u7uQhG8L6HZ/w 1GvdiM1zJylpC0sr4E4WgW5p5VEblNZaWm/7xAGWVrksuwHqpBcRdXXjmZOUtIWlFSEn91rk5C4g JymtsbTeyMlDLK1ykbU0cUsDlcjJp4Y8UY7StrC0AuRkEcgVIx45yWmNpXUM5GT3JIiTDpGcEEQS xmxUUhaQk5S2haUVISfXWuTkKiAnKa2xtI6BnBxslIlZLsmWJu4axomJFzF8iYzTNrG0AjpNqHx5 hsj/tpzWWFrHwE4OljIp6IXWgCCVXkzY2yBgJyltA0sr2MnLlRt5md/Ho6TW0jrEqr9/AqwVpVOw z49jNrK08vv8nLa3pRV8rZvDnWz9zhUolZTWWFpPpFR2T7BFxk4ugDrpRURdXXjmJCXtbGkFyMki 0C2t/ChMaa2l9XZOeIWyoCMnA0JOejHhpD4IyElK29nSipCTuRY5mQXkJKU1L9EbOemmzCojJ0sT t3RUiZx8aiiUjt48cjJO4PRWERxcf+RPb3FaY2m9FHIy6cjJhJCTXky8QSEgJyltZ0srOB9cBIem zNOfEXa5Ks4H53wl7GTcZOxkaeKljBcTpszGAwQ4bWdL6+OnYj8FO7nzCApKaiytV8JOphlhJ21v Z4CocWPC3s48oobT9l76o5X/GfN6HnJESa2l9UI3TczTzZ08YtCWC60RcCe9iLhCIFzZeYp9Ii2A O1kEsqWV505yWmNpvbmTh1ha1TfuBqiTXkTU1Y1nTlLSJpZWcDxtr0VO7gJyktIaS+uNnDzE0iqX ZEsTtzRQiZx8aiicdj0HORkTmM8XgW5pFQ5BV8znl+1GTh5igNWRkxNCTnoxcUlZQE5S2haWVoSc XGuRk6uAnKS0L6uBaQzk5Ggps8hF1tLEXcM4MWHKLHxJmdM2SJkI9iWKQLa08vsSnNZYWm/sJGlS 1UunAWEnYcxGlFYBO0lpG1haweZ3rtz7zvzWNyU1llYER7zT5YdPVlE6BdYYHLORpZU30nDazpZW xJ3cHO5k62mKQKmktMbSeiKlsnuCLTJ2cgHUSS8i6urCMycpaed9LYCcLIKDd7Z45CSnNQbYSyEn g46cDAg56cWEk/ogICcpbW9LKyiPZOcoCt6wEiCSlNZYWk+ESA626g+rjJwsTdzSUeVJtaeGfG2Z 0p6ZMtQP/qj+CA47FoFcf+QPO3Jaa2m9kIMiRh05GUFv3Zh4g0JATlLavpbWBRySL4JjLa0Lf6Se 0xpL65Wwk3GTsZOliZcyXkyYMhvP3OC0fS2tgNuyn4Jt2XlqCyU1ltYrYSfTjLCTtrczoDq5MWFv Z57qxGn7Lv0B6yuhBXObeT3PBaOkxtKKyhfvKV3m6eZOHjFoy4XWCLiTXkQ4YvPcSUrawtIKuJNF IFtaee4kpzWW1ps7eYSlVS60bmAk8iKirm782EJJW1haEXJyr0VO7gJyktIaS+sYyMnBsiXMckm2 NPFKA15MuNif+cULp21haUXL31S7/E3C8pfSGkvrjZw8xtIqHwueEHLSi4lLygJyktI2sbQCOk3t CiYIvy2nNZbWGzl5iKVVLrKWJl7KeDHxIkbYhaG0LSytaCsv1m7lRWErj9JaS+sQi/7uSZCCXjoN CDsJYzaytArYSUrbwNIK/CK50i6SebcIJTWWVgRHvNPlh09WUTpFbjIYs5GlVXCTUdrOllbEndwc 7mRzSyvPn6C01tJ6IfvEImMnF0Cd9CKiri48c5KSDmQ2ShG58GMloDJFwVdPaY2l9URAZfdsCUFH TgaEnPRiwkl9EJCTlLazpRUhJ7Nzcguu9bIAkaS0xtJ6IkRysFV/WGXkZGnilo5qj3auwtFOSts3 ZSZ04nc6BTn59Gf4IjalfVlegP14T6NMjDpyMiLkpBcT/rZRQE5S2t6WVlCWhu/yRpZWnkLBaY2l 9UrYybjJ2MnSxEsZLyZMmU3A1FDavpZWAC+CK4BGllb6O6Wk1tJ6oVV/mhF20vZ2BiA0Nybs7cyD 0Dht30IZYOPB8lKbeT1P0qOkxtKKin3vKV3mqRd38nUPxRv/WqNcaI0gt7yIcMTms4WSNrG0gmxZ al+3i/C6pbTG0npzJ4+wtMqF1g1M3LyIqKsbPxWjpC0srWguv9fO5XdhLk9praV1COfEYNkSZrkk W5p4pQEvJlzsz8Jin9K2sLSiilGqrRgloWJEaV+mzDoGcrJ/Euxy2bQ08ZIAxmxTH9uFW4wobQN/ 3ob2JbbafYlN2JegtMbSOgZycrBRJi5ykbU08d67Xkz43l2EbU5K28LSina/Y+3udxR2vymtsbSO gZ0cLGVS0AutAdljvJiwt0Gwx1DaFpbWxw9CrvRXZd5fRUmNpRXBEd9GuvRPgLWidIq8lzBmI0ur 4L2ktJ0trcgpDMENjd65glOY0hpL65W4k4uMnVzAKQIvIurqwp8ioKR9syWiYygeFQg+EVE4WEJp jUn1Rk66NYKgIycDOqfmxYST+iCcU6O0nS2t6Piix52Da70sHF+ktNbS+p78EK2S8vvHO8vIydLE SxkvJkyZVTgNTWn7pkxAh+Qh3bSNpTUIR+oprbG0Xgo5GXXkZETMDS8m/G2jwNygtAOdNQoLArd4 fG74JloEcAulNZbWK2Ennx48uba8IbKTFxOmzCaQnShtX0srgH3BexraWFp5NBglNZbWK2En04yw k7a3M8IGejFhb2cBG0hpO1takfX3lKUwz52kpMbSiq5kek/pMk83d/KIQVsutEYwFHkR4YjNDy6U tIWlFUGxl1oo9iJAsSmtsbTe3MkjLK1yWXYDixcvIurqxi9dKGkLSyta/u61y99dWP5SWmNpvZGT x1ha5fvUZnSBixcTLvZn4UoWStvE0vr4SSgC+XyIcK8PpTWW1jGQk/2TYJfLpqWJlwQwZiNLK79n w2lbWFrRVt5Wu5W3CVt5lNZaWo87OPFaoNO4CRYXuchamnjvXS8mfO8uwmWUlLaFpRXdURpr7yiN wh2llNZYWm/sJGlS1UunAZnJYMxGlFbBTEZpG1hawS3YufIW7Mzfgk1JjaUVwRHfRroMto5Ja0Wh NYHSkRcT9nZlbr1/trS+9Y2ttCGr/Ibs940eIsFYT2mNpfVK3MlFxk4u4NyNFxF1deFP3VDSzpZW cBarCI7Nlsif3OK0xgB7IqCye7aEoCMnAzra6cWEk/ogHO2ktJ0trQg5mZ3zwXCtlwWIJKV9+RKd T4RIDjYnC1lGTpYmXsp4MWHKZB4gwGkH8ufFACgURaAmWOApFJzWWFovhZyMOnIyIkyNFxP+tlHA 1FDarqNMWAC6qAiOLdkvPOqI01pL63s6ZoFSZpOxk6WJlzJeTJgyG89B47R9La0Ajbefgp3ceZAe JTWW1ithJ9OMsJO2t89NvN56MWFv55mvK1Pavkv/BXrRzpjXZ37dz0iNpTVeaNk/Tzd38pB5rj7N RbPc2kmuMMc9xT6RFjChLwLd0sqjNiittbTe3MkDLK1yoXUD630vIurqxq/2KWkLSytCTu61yMld QE5S2pe1wzAGcnKwbAlJB1QmBKj0YsLFfhKQk5S2QcrMYF+iCGRLK78vwWmNpfVGTh5igJWLrKWJ lzJeTJgyO79xyWlbWFoRcnKrRU5uAnKS0hpL642cPMbSKl80sQAfjRsTvncX3hnDaZtYWgGdJlZC J0PkqZOc1lhaD8ROXtcFnoJeaA0IUunFhL0NAnaS0jawtC6PO5sdpzXqa17orlJSa2kdYtXfPwHW itJpRL1FMRtRWhP/3VDa3pZW8LVu6MRKo2mKQKmktMbSeiKlsnuCLTJ2cgFH1byIqKsLf1CNkna2 tILDjkVwtKWVH7MprbW0Xsg5ESYdOTmB3rox4aQ+CMhJStvX0roi5OR6DnJyFZCTlNYYYK+EnAxZ Rk6WJl7KeDFhymSeucFp+6ZMAByWIjg2ZQLPbeG0xtJ6KeRk1JGTESEnvZjwt40CcpLSdra0AtBX EajvloVHfXFaY1I9ESQ5Wm15k7GTpYmXMl5MmDIbj53ktJ0trY+fof0U7OTOYycpqbG0Xgk7mWaE nbS9fW7i9daLCXs7J36NSmn7Lv0z+J7yKQv/zH+njNRaWi+07J+nmzt5xKAtF1ojXO/UTnKFOe4p 9om0gDVwEciWVn4NzGmNpfXmTh5iaVXfuBsoqHkRUVc3vkBGSZtYWsHxtL12bJmEn5XSmg2YGzlJ mlR15GRCyEkYs8351SQgJyltC0sr2McrAt3Syh8QobTW0nojJ4+wtMpF1tLESzAvJkyZnd/m57Qt LK0IObnVIic3ATlJaY2ldQzk5GBzsrjIJdnSxHvvejHhe3fhkZOctoWlFTAni0C2tPLUSU5rLK03 dvIQS6teaA0IO+nFhL0NAnaS0jawtObH74fsHE5Afc2ZfjtQUmNpRXDEO13qDLB6oTU+nqa4MWFv 10hPUzhtZ0sr4k5u53AnN4E7SWmNpfVK3MlFxk4u4HSnFxF1deHPdlLSzpZWcOK3CNQnIvInfjnt y+d/u5GT7qp/0pGTE0JOejHhpH4SkJOU9syUeS1yckXIybUWObkKyElKayytV0JOhiwjJ0sTL2W8 mDBlMk+o4bSdLa2IWhROQU4+/Rm+iE1praX1Qg6KGHXkZETISS8m/G2jgJyktJ0trYA5WQTH7nIt PHWS0xoD7JWwk3GTsZOliZcyXkyYMhuPneS0fS2tADu5n4Kd3HnsJCU1ltYrYSfTjLCTtrfPTbze ejFhb+fEV3Qobd+l/wpW/itR+n39UnjlqwSM1Fhaw3lFgu7pMk83d/KIQVsutEa06K++ZkK4ZeIU +0RaQNmoCGRLK1824rQvs2W5uZMHZMsql2VXUIP2IqKurnwFmpI2yJYJbEoUgWxp5bclOK2xtN7I yUMMsDpyMiHkpBcTLvaTgJyktC0srQA5WQSypZVHTnJaY2m9kZPHWFrlza0dICfdmDBldh45yWmb WFqBgXerRU5uAnKS0hpL64HIyfe01IuLXDYtTbw3KYzZZhdm4ZGTnLaFpRUwJ4tAt7TyW3mU1lpa h1j0d0+ZFPTSaUDYSRizzZgaBOwkpW1gaV0fD6nZOc+D+lr2zGFXKamxtCI44n3OqMrSWlFoDagC 7cTEReUgVJUZbWdLK+JObudwJzeBO0lpraX1QvaJWcZOzqCvXkTU1YXvKSXtmy0JnJBP8Clrky2J P1HPaY0B9lLIyUlHTk4IOenFhJP6SUBOUtq+/rwVIVjWWgbLKkBYKK0xqZ4IkRytUJZl5GRp4qWM FxOmTOaRk5y2s6UVICeLQN7j5ZGTnNaYVG/kpFtWizpyMiLkpBcTPglRQE5S2t6WVlCWXk6BToaF p05yWmNpvRJ2Mm4ydrI08VLGiwlTZuOxk5x2oLNGO4BU7g6kEn2pO4+dpKTW0nqhVX+aEXbS9va5 iddbLybsbdk7x72ltJ0LZWDlv52y8N/4dT8jNZbW6ULL/rng99707tZo81y50BrRRS6V3MkoXMxy DncyLeghWGqzJQs/K6U1ltYxuJODZcsqF1pXsGPjRURdXfkdGErawtIKkJNFoFta+e0mSmstrUM4 JwbLlpB05GRCyEkvJlzsJwE5SWlbWFoBcrIIZEsrj5zktMbSeiMnD7G0yiXZ0sRLGS8mTJmdR05y 2haWVoSc3GqRk5uAnKS0xtJ6IycPMcDKRdbSxHvvejHhe3fhkZOctoWlFTAni0C2tPLUSU5rLK1j YCe7J0EKeuk0IJAkjNnI0ipgJyltC0vr4wchO0fgUF/Lzaawq5TUWFoRHPFOlx8+WUXpdALLWxiz ESdh4hfDlLZzpR5xJyHdsdE0RaBUUtqXFTmPn/kuE2yWsZMzwAd4EVFXZx4eQEnPzBbtGbfPTwL0 ieSRg+Hzk3j+BKc1ltZLIScnHTk5IeSkFxNO6icBOUlpO1taEXJyPQc5uQrISUprDbAXck+ELCMn SxMvZbyYMGUyj5zktJ0trQA5WQSypZWHSHJaY2ltcnL5XaZMjDpyMiLkpBcTPglRQE5S2s6WVsCc LAL13bLwHElOa0yqJ4IkR6stbzJ2sjTxUsaLCVNm47GTnLZryuwAO7mfgp3ceewkJTWW1ithJ9OM sJO2t89NvN56MWFvyw2nuLeUtvfZb1AnO+WNu/NPECN9mS4Fv3eFdNlv7uQhHgrdQoEcFLUGCsE/ cQ53MiPuZK7lTmaBO0lpjaX15k4eYWmVC60roE56EVFXV545SUlbWFoBcrIIZEsrj5zktMbSeiBy 8ro1lJB05GRCyEkvJhxekoCcpLRNLK2Pf9sikC2tPHKS0xpL6xjIycEGmLDLgMrSxJ2QOTHxjIxH TnLaFpZWhJzcapGTm4CcpLTW0nofnDjC0iqXZEsT773rxYTv3YVHTnLaFpZWwJwsAtnSylMnOa2x tB6InXxPU60U9NJpQCBJGLORpVXATlLaBpbW7fGqLTsHRlFf806v2ijpy+UphCO+jXQZbIRJWS+0 PjdxS0dOTNjbdeJLR5S2b6V+R9zJ/Rzu5C5wJymtsbReiTs5y9jJGVAnvYioqzPPnKSkfbMlAeRk EcgmVR45yWnNE4HON1+4UDbpyMkJISe9mHBSPwnISUrb2dKKkJOrg5xsbWkVAJWU1lhaTwRU9k+Z LCMnSxMvZbyYMGUyj5zktL0traA8Ek5BTsbAIyc5rTHAXgo5GXXkZETISS8m/G2jgJyktJ0trYAi WQSHpszTn+GL2JTWGmAvdHAibjJ2sjTxUsaLCVNm47GTnLavpRVgJ/dTsJM7j52kpMbSeiXsZJoR dtL29rmJ11svJuztPPF1ZUrbuVAGVv6oRtkkXWa++EhJjb9Ktx0NnC77zZ08YmkoF1oD4E56EeFs jOdOUtIWllbEncy13MkscCcprbW03vaJAyytMnZyBdRJLyLq6sozJylpC0srQE4WgWxp5ZGTnNZY Wm/k5CGWVh05mRBy0osJh5ckICcpbQtLK0BOFoFsaeWRk5zWWFpv5OQhlla5yFqaeCnjxYQps/PI SU7bwtKKkJNbLXJyE5CTlNZYWm/kJGtSla+OWAByEsdsswuz8MhJTtvE0groNLESOhkiT53ktMbS emMnSUurXjoNCDsJYzaytArYSUrbwNK6P/5qsnO8GvU173RXKam1tN6r/iMsrRWlIwRV8GLi0pEA SqC0vS2t4IvaHZJka0urwJ2ktMbSeiXu5CxjJ2dAnfQiwk0YnjlJSTtbWgFysgh0Sys/ClNaa2k9 zwsx2AATJh05OSHkpBcTTuonATlJaTtbWhFycq1FTq4CcpLSGpOqfL75OimTZeRkaeKljBcTpkzm kZOctrOlFSAni+BgSysPqOS0xtJ6IqCye8rEqCMnI0JOejHhbxsF5CSl7WxpBczJIjjY0spTJzmt sbReCTsZNxk7WZp4KePFhCmz8dhJTtvZ0vr4qdiZD/PqhNn5agolfVmRC5fCTiaEnfzMihaUWt2Y eEXLF1s5bdd0mUG1fj6lWD/ztXpKai2tFzowkfabO3nE0lAutAbAnfQiwtkYz52kpC0srYg7mWu5 k1ngTlJaY2k9kDt53WxZ5bLsCqiTXkTU1ZVnTlLSJpZW8BBMlcjJNPHISU5rLK03cvIQS6uOnEwI OenFhMNLEpCTlLaFpRUgJ4tAt7Tyh6AprbW03u6JIyytcpG1NPFSxosJU2bnkZOctoWlFSEnt1rk 5CYgJymtsbSOgZwcLGXiIhdZSxPvvevFhO/dhUdOctoWllbAnCwC2dLKUyc57cuU2cbATnZPgjTp pdMJnfuGMVtZWnk+HKV9fcqsAB3w/O/qqo0HB1BSY2lFcMQ7XX4o3Oil0wyoIjhmm3TJPFeE055Z qX8tiXFHlMq9llK5C5RKSmssrfJx6IETbJaxkzOgTnoR4SYMz5ykpJ0trQA5WQTyBiAPkeS0xtJ6 IkRysCVMmHTk5ISQk15MOKmfBOQkpe1taQXUtPUc5OQqICcprTHAXgk5GbKMnCxNvJTxYsKUyTxy ktN2trQC5GQRHG1p5YvYlNZaWi/koIhRR05GhJz0YsLfNgrISUrb2dIKVodFoL5bFn6993ltq6T8 PmXylbCTcXMKPY8sraB25MaEKbPx1SNO29fSCsqP+ynVxzDx1UdOa0ytlwJPJgSe/MyaFmxPuDHx mpbfnuC0fU2tYNNqPuVStZnf4KKkxtSKjn68q3TZb/LkIYtDeY8UkCe9iHB44cmTlLSFqRWRJ3Mt eTIL5ElKa0ytN3nyCFOrXJhdAXfSi4i6uvLUSUrawtQKoJNFIJtaeegkpzWm1hs6eYipVYdOJgSd 9GLC4SUJ0ElK28LUCqCTRSCbWnnoJKc1ptYxoJOjpcwul1lLEy9lvJgwZXYeOslpm5hawfRzq4VO bgJ0ktIaU+sY0MnBUiYucpm1NPHeu15M+N5d+IOsnLaFqRUchS4C3dTKb+ZRWmtqvRf9R1hgK2b3 CDzpxcSzewE8SWkbmFoBa2OtRG2sPGmDkhpTK8Ijvo106Z8AWS+dZkDiwTEbmVp5Eg+n7WvT2xF5 cnfIk42/1l3gVFJaa2q9kIFilsGTM+BOehHhJgxPnaSknU2tADpZBPIGIA+d5LTG1HpDJ91V/6RD JycEnfRiwkn9JEAnKW1nUyuCTq7nQCdXATpJaY2p9UrQyZBl6GRp4u5cVkInQ+ahk5y2s6kVTHWL 4GBTKz/V5bTG1Hop6GTUoZMRQSe9mPC3jQJ0ktL2NrWCsvRyCnYyLHwxhdO+TJnlSuDJuMrgydLE nW9UVlvjyldbOW3flJlAEb4Ijra18kVsSmttrRda+aeE4JOfWdWCPT03Jl7V8nt6nLavrRXs9M6n 3EU487vClNTYWtGJqXeVLvtNnzxkeSjbKAB90ouI14a8h+Ik+mRG9MlcS5/MAn2S0pqy8oH0Se0Z f08voVUuza6APelFRF1defIkJW1hawXgySLQba38lhOltbbW2z1xhK1VB08mBJ70YsLhJQngSUrb wtYKwJNFINtaefAkpzW21hs8eYitVS60liZeyngxYcrs/Lk8TtvC1orAk1steHITwJOU9mVFMDLP aP+U6Z4EcZZLp6WJ+yY95eh3XPij35y2QcokQA8oAnlM5ekBnNbYWseATw42yqRJL7ROCFXpxcSz ewE+SWlb2FofPwhrJaFm5QE1lNQsTxEi8W2kyw9qLW06pkvWC60Z4K7cmLh0xAOsOG1nWyuiT+4O fbK1rVVgVVJaY2s9kVXZfYSZZfjkDNiTXkS4CcOTJylpb1sr2gB0wJPwiUg8SpLTGlvriSjJweZj YdLBkxMCT3ox4aR+EsCTlLazrRWBJ71tVLjWWwWUJKW1RtXz/BCjpUyWwZOlibtzWTmtD5mf13Pa M1Pmlfz8GMDKMHq2HphggV8Zclpja70UeDLq4MkISkduTPjbRgE8SWk721pB/TFAO2gbj14W0JOU 1thar4SejKuMnixN3PlG5QZFXPkNCk7b2daK9q3goYNGtlZhl4vSGlvrpfCTCeEnP7OqBdvgbky8 quW3wTltZ1srOPqL/BZtbK28kYKSGlsrOmb4rtJlH4M/2f2LCnL5NACiJIzY6KARP7qcxJ/MiD+Z a/mTWeBPUlpTVr75k0fYWuXS7Arok15E1NWVZ09S0ha2VoCeLAJ545tHT3JaY2u90ZPH2FrlMxMJ oSe9mHB4SQJ6ktI2sbU+fhKKQLa18sfUOK2xtd7oyUNsrXKhtTTxUsaLCVNmF86xUtoWtlaEntxq 0ZPlunPcW0prba334YkjTLAV713AVnBj4vcuT0vgtC1srQC5UQTymMojNzitsbWOgZ8cLGXSpBda JwSr9GLi2b2An6S0DWytgOu0VmKdVp7qREmNrRVBEt9GuvRPgKyXTjOgvuGYjWitPPWN03a2tSL+ 5O7wJ1vbWgVaJaU1ttYTaZXdE2yW8ZMzoE96EeEmDM+epKSdba3oJZSclxB8IpLwWqG0xtZ6Ikxy sPlYmHT05ITQk15MOKmfBPQkpe1sa0XoSXjpZSNaq4CepLTGBHsl9GTIMnqyNPFSxosJUyYL62BK 2zdlAiqPeB8HJkEQyiOU9mUSwIurrzvKPH2hMnoyIPSkF5N4EvgzAZS2r0cvoyJ8Pgc9mYWSPaW1 ttYLoSefBmK5tryiPT0vJp5BCHt6lHagwxNP01kweE+1G8OTsDFMaY2t9VL4yYTwk59Z1SLniBeT WNXytWVK29fWCsxEM7IntbG18tYjSmpsrc7J3PeZLvuB/MnrznWDXGwNgD/pRYTDC8+fpKQtbK2I P5lr+ZNZ4E9SWmtrvS0UB9ha5dLsCg5YeBFRV1f+yAQlbWFrRWduptozN5Nw5obSGlvrjZ48xNaq oycTOsLnxYTDSxIO5VHaFrZWdLJzrj3ZOQsnOynty5TJY6AnR0uZTS7LliZeyngxYcrswtFvStvA o7cj9OSzQO+twKatQU/GMdCT3ZPg6a0n35Y2I2QIjNlm83IWACOUtomtFVBqUi2lJgmUGkprbK1j 4CcHG2XSpBdaJ4Sf9GLi2b2An6S0DWytAIW2VpLQVh6ERkmtrXWIVX//BMh66TQjUCKM2cjWKmAV KW1vWyv4WvdzvtZd+FoprbG1nkir7J5gs4yfnMEr14sIN2H4Vy4l7WxrRaNwqh2FkzAKU1pra73R k96qf9LRkxOa1Hsx4aR+Eib1lLazrRWtDNdamOQqrPUorTGqngiTHC1lsoyeLE28lPFiwpTJQumI 0g5kOIoBXZQTKuuPMQpX31BaY4K9FHoy6OjJgDYovJjwtw3CBgWlHShlQka7XLl2lysLu1yU1tha r4SejKuMnixN3PlG7Q2Mq3ADI6Xt6wSf0MWc0ynwyTAJ13hSWmNrvRR+MiH85GdWtchn5cXEq1rB Z0Vp+9pagfVuRma+RrZWvqJSYdRbV3SO/V2ly37zJw+xHsk2CmAZ9yLC4YU3gVPSFrZWdIog154i yMIpAkprbK03f/IQW6v6xl3BISMvIurqyh8xoqRNbK3gIZgqj6mliT+mxmmNrfVGTx4ytujoyYRO vXox4fCShHOslLaFrRUdhp5rD0PPwmFoSmttrUM4KEZLma2CXwrYCm5MmDIbz1bgtC1srQi5sdci N3YBuUFpja31Rk8eYoKVC62lifverURPPjXkmTyUtoWtFYGdUi3YKQlgJ0prbK03fpI0quql0wmR 32DMNi+ISeDEUdoGtlaADlwr0YErjw6kpMbWiiCJd7r8ULjRS6cZYUVhzEa2VgErSmk721rRW2g/ 5y20C28hSmtsrSfSKrsn2CzjJ2cwSfEiwk0YfopCSTvbWhEzPdUy05PATKe0xtZ6IkxysCVMmHT0 5ITWwV5MOKmfhHUwpe1ta0X0NObjvPohiqsAqqS0Lyty6URQZf+UWWT0ZGnipYwXE6bMIlz0Q2n7 pkwERfgi0I2qfFma0lqj6n14wiuUBR09GRB60osJn4QgoCcpbV+PXkYwyYy2jhvRWgX0JKU1ttYr oSfjKqMnSxN3vlFpGnlqKPDe3zx6MkzISDSdAp8Mk2A8orTG1nop/GRC+MnPrGrRrdheTLyqFW7F prR9ba3gWvX5lGvVZ/5adUpqbK3pvEJB/3TZb/7kEctDudga0CGLSv5kEA5NnMSfzIg/mWv5k1ng T1JaY2u9+ZNH2Frl0uwKzuV5EVFXV/5UHiVtYWsFJzuLQLa18ic7Oe3LYsh0oycPGVt09GRE6Ekv Jh5eBPQkpW1ga10AP6AI1CXwwvMDOK2xtY6BnhwtZTa5LFuaeCnjxYQps/E4Ek7bxNYKpp97LaVm Fyg1lNbYWm/05CG2VrnQWpp4710vJnzvzjz0itO2sLUCEFoR6LZW4ahIBQstb2PgJwdLmTTphdYJ URW9mHh2L3ASKW0DW+vyeEhdnccSrtoW/jAiIzW2VgRJfBvp0j8Bsl46fW7iFoNQzEa21sT7zyht Z1sr4k/uaHhvZWvluR6U1tpaLwShmGX85Azm9V5EuAnDz+opaWdbK1jrFYG8Aciv9TitsbXe6El3 1T/p6MkJlI7cmHBSPwnoSUrb2daKYJIrqlK2sbVuAnqS0hpb65XQk2GR0ZOliZcyXkyYMgu/QcFp O9tawaZVERybMpHf5OK0xgR7KfRk0NGTAaEnvZjwtw0CepLS9ra1grJ0Pgc9mQUXBaU1ttYroSfj KqMnSxN3vlGJnnxqyNeWKW1nWyu69nk6BT4ZJuGaaEprba0XWvmnhPCTn1nVJtBbLyZe1c58bylt X1trfjwaP//7sbbWTI/clNTYWuOFDk6k/eZPHmI9km0U6FxSJX8yCOeMTuJPZsSfzLX8ySzwJymt sbXe/MkjbK1yaXYFB1+9iKirK3/slZK2sLWCw9BFoNta+S0nSmttrbd74pAjExVnJuChiUrXWhTQ k5S2ha0VIDeKQLa18sgNTmtsrTd68hBbq1xoLU28lPFiwpTZeIIPp21ha0Xoyb0WPbkL6ElKa2yt Y6AnB0uZOMuF1tLEe+96MeF7d+ahb5y2ha0VsCeLQLa18vRJTmtsrWPgJwdLmTTphdYJwSq9mHh2 L+AnKW0LW+vjB2F13uRw1ZbpH5aSGlsrgiS+jXTpnwBZL50+N3GLQShmI1tr5BfDlLazrRXxJ6H1 oJGtVaBVUlpjaz2RVtk9wWYZPzmDpbAXEW7C8AthStrb1oo2ACvLIynx5RFO+/KJgO7B687Hdpk8 uYNaqxcRdXXnK62UtK89b0PUSc9qDZd52+dq6q976p4drRX1a8/M/i7HlrDI1MnSxFsCezHhEnjh d/I4bWdHK9jdjfB0TiNHK78bzGmNo/VS1MmgUycDok56MeFvGwTqJKXt7GhF1Ml8DnUyC9RJSmsc rVeiTsZVpk6WJl7KeDFhyqw8dZLTdna0AuxkEchnsniUJKc1HtUTWZKDLWNSQuTJzyxoEygrezHx gjbxZWVK29nRCk795jMeoXKJIS6mMFLjaA0XOjOR9hs9ecTyUK6zBnCKz4sIByP+VB4lbeFoRejJ XIuezAJ6ktK+rB/OzON5Z4s6qZershkcE/cioq6u/LFvStogWwJABxSBmi2BRwdwWuNovamTxzha 9eMSiDrpxYTDSxSok5S2iaP18ZNQBLKjlefTcFrjaL2pk4c4WuVCa2nipYwXE6bMxsOrOG0LRyui Tu611MldoE5SWutovc9NHOFolQutpYn33vViwvfuzFMnOW0LRyvAThaB7GjlwZOc1jhab/Ik6VHV C60TIk/CmG1eEJNAnqS0DRyt+fGqbXUmP3DVtvKrNkZqHK2Ij3inyw+FG710+tzELQahmK0crULp iNF2drQi9CS8UbaRo1UAVVJa42g9EVTZPcFmmTw5g+qRFxFuwvC1I0ra2dEKyonJu4QcPhEzX1Dk tMbReiJHcrAlzC5DJ3ewM+FFRF3d+X0JStrZ0YqAk1vlXtVTQ96URWmNR/VEhORg2RIWGThZmnhL YC8mXAIvPHCS0/Z2tILKSKy8hzNGHiHJaY1H9USE5GApE4MOnAwIOOnFhE9CEICTlLazoxUBJ/M5 wMksACcprXW0XujcRFxl4GRp4qWMFxOmzMoDJzltZ0crIE4WwbEpM/HMSU5r/K+Xgk4mBJ38zII2 giK0FxP2NkW+rExp+zpa18cLvud/P9bRutHLQ0pqHK3TeTWC/umy39TJI5aHcp01gIOvXkQ8vPAT spOokxlRJ3MtdTIL1ElKax2tt3viAEer/AxlAFXwIqKuZh6pQElbOFoBZaMIZEcrz9ngtMbRegMn D3G06sDJiICTXkw4vEQBOElpWzhaAXCyCGRHKw+c5LTG0XoDJw9xtMpl2dLESxkvJkyZjQdOctoW jlYEnNxrgZO7AJyktMbR2hA4+fR03Snz/TtylgutpYn33vViwvfuzAMnOW27OorNpQRQlEUgW115 GCWnNRNxRKP8KPvqdz//7e9+88uvvvnmzz786ut//fqbf/nqy+/+4WOoL5++n0/0P/rpX/+XP/nw n//l619/+eHrb57+8L//64cfffP1P//rL379RVjfrbVv0kuuE4JVejFhbycBP0lpG3hb18edXZ2V A+rrutJdpaTW26q+FJ/fiM+SL3/3b7/89W+++eqP3iI/++u//csPf/lf/+JD+LOPJ3q/+eM3z198 9W8//+bb3/z247DxcgT7+G8f//tf/uuXP/qTH3/45ttf/O7bL8KPP/z2F7/771+ET7R/+5tvf/O7 v/j7v/7iaVr44w9/+4s/fPcffvrbr7768ovpT/eP//Gv/uqn3371259+/f999cWc46dt/+5nf/cP f/bh7//xb7+Y/jDFH3/8Xz//i//2s//r4/83fJj+MC9P/yukj/9r++6//fjj/9yf/ucvv/o0zn/+ m//j53/1V//44YsP+cNPfvKfnkTTp6+Lv/nF//jtT3729f/46nffd+TpxfKj33/z8Sf464/f0D98 pu/2u/zuv/z8t1//9qsPP/rdd//vnziPGTcaPX2Sb3//zdNH/n+fvuMPv/nV00vv1199DPDLpxff /+7pf/mbL7/6fIsP//6Lbz784ssvnzr39GD90+9/9avP/tWvfv3VL7/9+a++/E7+XZ++/O4r+8u/ +yucCDubBoTw+8nJ97364jMdem7xw6jw9Pz/z99/9c3TRObff/H1tx8/1q9+87sPP/xHX/zPv/n2 P0Qftpcp9fRBfvnVrz/Not/Y//acRPEpidbpmwM+2HLHvGO+4Zh5kM95x7xj3jGvEzOZAf3jhOaA PxSml3/pqz98/e0n/+2n//L7b79bhv7yF7/+9cf55Zdf/dtP/tOvvvziJ09z1l9//U9P08o/m6bw 9H//aHn6j598oB9mij/5OIf8X3/6p3/6afR///rbX/7LR+Gvn6ayTzOlX/3xv//DX/6X/3v6w/JP /8/TdHL6wz5/+NH/+Oa/P82Stz8qO/2g2r9XzeE/VNP2qepv/vxv//4nP/3Zn//sv/30zz5OpL// P+Gzn+Zvfvg0Lyoa33wn+PiP/+eP/u6/fjH9+Gd//+df/NFH+T7Ed+2f/sjHGtU/f/NJD8Lsdi4c 0LnJWyv85re//WQi+j9///XTY/Hxh3/q+//2/wMN3RQcDf0KAD== --=-LXWa6OL6bN8i+5klQC12-- From khk@khk.net Thu Jun 10 10:36:52 2004 From: khk@khk.net (Karl Heinz Kremer) Date: Thu, 10 Jun 2004 05:36:52 -0400 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <87u0xk83hu.fsf@zen.epkowa.co.jp> References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> Message-ID: I'm also reading sane-devel, so no need to take a detour with any Epson backend related information :-) I've never experienced any of the problem you describe, and I've been running a 2.6.x kernel for some time now (SuSE 9.1 beta versions and the final SuSE 9.1). I've tried this with two different USB controllers (USB-1.1 and high speed USB-2) with a number of different Epson scanners. Karl Heinz On Jun 10, 2004, at 12:02 AM, Olaf Meeuwissen wrote: > Hi Tom, > > I am the lead developer of iscan and the sane-epkowa backend that > comes with it. Farideh has also contacted me about your issue, but I > think that my reply is better sent to sane-devel (at least it'll be > archived :-). > > Tom Schutzer-Weissmann writes: > >> I had problems using the Epkowa libraries (libsane-epkowa) and the >> iscan frontend with my usb scanner in kernel 2.6. >> >> The scanner was closed after each operation. Once closed, nothing >> could be read from it, and I got lots of BULK TIMEOUTs, although there >> were no errors when the device was reopened. > > Sorry to say, but I can't reproduce your problem. I've tried with a > GT-8200 (aka Perfection 1650) on SuSE 9.1 and Debian (testing). FWIW, > the version of relevant packages: > > SuSE Debian > iscan 1.8.1-0.redhat.8.0 1.8.1-0.redhat.8.0 > sane 1.0.13-73 -- > libsane -- 1.0.14-2 > libusb 0.1.8-31 -- > libusb-0.1-4 -- 0.1.8-11 > kernel-default 2.6.4-52 -- > kernel-image-2.6.6-1-686 -- 2.6.6-1 > > with the note that I compiled iscan from sources on Debian. > > Can you give more information about your setup? Things like scanner > and distribution used as well as version of relevant software might > help me in reproducing your problem. > > When you say that "Once closed, nothing could be read ...", do you > mean the calls to sanei_usb_close? I've looked at the debugging USB > output and don't see any bulk timeouts. My system logs also show > nothing. > >> By modifying the code so that usb_reset() was always called before >> usb_release_interface() and usb_close(), I solved the problem. > > The epkowa backend does not call the usb_* functions directly, so I > presume you have been mucking around in sanei_usb, right? This would > seem to indicate that you think the problem is not specific to the > epkowa backend. I see below that you also get BULK TIMEOUTs with the > epson backend. Both backends share a lot of code, so this is not an > indication that your problem is not backend specific. > > Has anyone seen this with other backends? > >> For libusb developers, my question is, should this be the case? There >> is nothing in the API docs to indicate that it's necessary - perhaps >> it is self-evident? >> >> Farideh - in the belief that you are a point of contact for Epson >> developers - could you make them aware of this issue, if they aren't >> already. > > I read sane-devel ;-) > >> I think this is relevant to SANE because although I had some success >> scanning with xsane and xscanimage, using the libsane-epson libraries, >> I still got timeouts if I closed, say, xsane, and then restarted it - >> for lack of a usb_reset() I believe. > > I have no problems closing iscan and restarting it (for the setups > listed above). > >> Apologies if this is old news. Tom SW > > Hope this helps, > -- > Olaf Meeuwissen EPSON KOWA Corporation, PF1 > FSF Associate Member #1962 sign up at http://member.fsf.org/ > GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 > Penguin's lib! -- I hack, therefore I am -- LPIC-2 > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request@lists.alioth.debian.org From henning@meier-geinitz.de Thu Jun 10 14:44:04 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 10 Jun 2004 15:44:04 +0200 Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <1086841087.8304.22.camel@yoda> References: <1086841087.8304.22.camel@yoda> Message-ID: <20040610134404.GB2294@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > Hate when I do that . . here's the xsane logs described in my previous > email Ok, let's look at the second log. The preview scan looks ok (but I don't know the details of the plustek backend). The real scan also starts fine and then we see this: [plustek] sane_read - read 3750 bytes [saned] do_scan: read 3750 bytes from scanner [plustek] usb_ScanReadImage() done, result: 0 [plustek] usb_ReadData() [plustek] usb_ScanReadImage(3760) [plustek] usb_ScanReadImage() done, result: 0 [saned] do_scan: trying to write 3754 bytes to client [saned] do_scan: wrote 3754 bytes to client [saned] do_scan: trying to read 1521 bytes from scanner [plustek] sane_read - read 1521 bytes [saned] do_scan: read 1521 bytes from scanner Now these 1521 bytes should be sent to the frontend... [saned] do_scan: processing RPC request on fd 4 [saned] process_request: waiting for request [saned] process_request: bad status 22 saned thinks something has been sent to it by the control (not data) connection. But when trying to decode what was sent it gets an error when reading the first word. 22 is "invalid argument". That means that no data could be read. Maybe xsane has crashed on the clent side meanwhile? Usually during the scan nothing is sent to the control file descriptor. Anyway. As sane_cancel isn't called the reader_process in the plustek backend isn't killed and the plustek backend gets confused. So my impression is that the problem is with xsane (or the net frontend on windows) and the scanner lockup is just a consequence. But I don't know why xsane (or the net backend) crashes. So maybe finding out the details here may help- E.g. gdb xsane on the client or enabling debugging for xsane and the net backend and looking at the last few lines before the crash. Maybe the xsane and plustek maintainers can have a look at the logfiles, too? Bye, Henning From keith@claytons.org Thu Jun 10 15:09:36 2004 From: keith@claytons.org (Keith Clayton) Date: Thu, 10 Jun 2004 07:09:36 -0700 (PDT) Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <20040610134404.GB2294@meier-geinitz.de> References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> Message-ID: What sort of steps are availble for me to take debugging-wise on the windows end? If xsane is started from the command prompt, are there any swithces available to generate debugging output at the command prompt? K On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > > Hate when I do that . . here's the xsane logs described in my previous > > email > > Ok, let's look at the second log. The preview scan looks ok (but I > don't know the details of the plustek backend). The real scan also > starts fine and then we see this: > > [plustek] sane_read - read 3750 bytes > [saned] do_scan: read 3750 bytes from scanner > [plustek] usb_ScanReadImage() done, result: 0 > [plustek] usb_ReadData() > [plustek] usb_ScanReadImage(3760) > [plustek] usb_ScanReadImage() done, result: 0 > [saned] do_scan: trying to write 3754 bytes to client > [saned] do_scan: wrote 3754 bytes to client > [saned] do_scan: trying to read 1521 bytes from scanner > [plustek] sane_read - read 1521 bytes > [saned] do_scan: read 1521 bytes from scanner > > Now these 1521 bytes should be sent to the frontend... > > [saned] do_scan: processing RPC request on fd 4 > [saned] process_request: waiting for request > [saned] process_request: bad status 22 > > saned thinks something has been sent to it by the control (not data) > connection. But when trying to decode what was sent it gets an error > when reading the first word. 22 is "invalid argument". That means that > no data could be read. Maybe xsane has crashed on the clent side > meanwhile? > > Usually during the scan nothing is sent to the control file descriptor. > > Anyway. As sane_cancel isn't called the reader_process in the plustek > backend isn't killed and the plustek backend gets confused. > > So my impression is that the problem is with xsane (or the net > frontend on windows) and the scanner lockup is just a consequence. > But I don't know why xsane (or the net backend) crashes. So maybe > finding out the details here may help- E.g. gdb xsane on the client or > enabling debugging for xsane and the net backend and looking at the > last few lines before the crash. > > Maybe the xsane and plustek maintainers can have a look at the > logfiles, too? > > Bye, > Henning > > From henning@meier-geinitz.de Thu Jun 10 15:10:41 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 10 Jun 2004 16:10:41 +0200 Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> Message-ID: <20040610141041.GD2294@meier-geinitz.de> Hi, On Thu, Jun 10, 2004 at 07:09:36AM -0700, Keith Clayton wrote: > What sort of steps are availble for me to take debugging-wise on the > windows end? > > If xsane is started from the command prompt, are there any swithces > available to generate debugging output at the command prompt? I don't know how setting environment variables works on windows but with bash you'd do export XSANE=DEBUG=255 export SANE_DEBUG_NET=255 XSANE_DEBUG will produce a huge amount of debug messages. Bye, Henning From keith@claytons.org Thu Jun 10 15:30:24 2004 From: keith@claytons.org (Keith Clayton) Date: Thu, 10 Jun 2004 07:30:24 -0700 (PDT) Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <20040610141041.GD2294@meier-geinitz.de> References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> <20040610141041.GD2294@meier-geinitz.de> Message-ID: I don't know much about windows side either. Guess I'll plug away a bit and see if I can coax some debug output out of xsane Cheers, Keith On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 10, 2004 at 07:09:36AM -0700, Keith Clayton wrote: > > What sort of steps are availble for me to take debugging-wise on the > > windows end? > > > > If xsane is started from the command prompt, are there any swithces > > available to generate debugging output at the command prompt? > > I don't know how setting environment variables works on windows but > with bash you'd do > > export XSANE=DEBUG=255 > export SANE_DEBUG_NET=255 > > XSANE_DEBUG will produce a huge amount of debug messages. > > Bye, > Henning > > From Oliver.Rauch@Rauch-Domain.DE Thu Jun 10 16:03:56 2004 From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch) Date: 10 Jun 2004 17:03:56 +0200 Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> Message-ID: <1086879836.2126.2.camel@Babylon7> For windows you can not enable a debug output - at least I do not know a way with the published binaries because they are compiled as GUI. BTW. Did you ever test xsane-0.94-win32? Oliver Am Don, 2004-06-10 um 16.09 schrieb Keith Clayton: > What sort of steps are availble for me to take debugging-wise on the > windows end? > > If xsane is started from the command prompt, are there any swithces > available to generate debugging output at the command prompt? > > K > > > > On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > > > Hi, > > > > On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > > > Hate when I do that . . here's the xsane logs described in my previous > > > email > > > > Ok, let's look at the second log. The preview scan looks ok (but I > > don't know the details of the plustek backend). The real scan also > > starts fine and then we see this: > > > > [plustek] sane_read - read 3750 bytes > > [saned] do_scan: read 3750 bytes from scanner > > [plustek] usb_ScanReadImage() done, result: 0 > > [plustek] usb_ReadData() > > [plustek] usb_ScanReadImage(3760) > > [plustek] usb_ScanReadImage() done, result: 0 > > [saned] do_scan: trying to write 3754 bytes to client > > [saned] do_scan: wrote 3754 bytes to client > > [saned] do_scan: trying to read 1521 bytes from scanner > > [plustek] sane_read - read 1521 bytes > > [saned] do_scan: read 1521 bytes from scanner > > > > Now these 1521 bytes should be sent to the frontend... > > > > [saned] do_scan: processing RPC request on fd 4 > > [saned] process_request: waiting for request > > [saned] process_request: bad status 22 > > > > saned thinks something has been sent to it by the control (not data) > > connection. But when trying to decode what was sent it gets an error > > when reading the first word. 22 is "invalid argument". That means that > > no data could be read. Maybe xsane has crashed on the clent side > > meanwhile? > > > > Usually during the scan nothing is sent to the control file descriptor. > > > > Anyway. As sane_cancel isn't called the reader_process in the plustek > > backend isn't killed and the plustek backend gets confused. > > > > So my impression is that the problem is with xsane (or the net > > frontend on windows) and the scanner lockup is just a consequence. > > But I don't know why xsane (or the net backend) crashes. So maybe > > finding out the details here may help- E.g. gdb xsane on the client or > > enabling debugging for xsane and the net backend and looking at the > > last few lines before the crash. > > > > Maybe the xsane and plustek maintainers can have a look at the > > logfiles, too? > > > > Bye, > > Henning > > > > From ngamradt@hotmail.com Thu Jun 10 16:16:45 2004 From: ngamradt@hotmail.com (Neal Gamradt) Date: Thu, 10 Jun 2004 15:16:45 +0000 Subject: [sane-devel] Question About Mustek 600CP scanner on Suse 9.1 Message-ID: Hello All, First off I would like to thank you all for the the work you have put into scanner support for Linux, I have a Mustek 600CP and historically I have never had much trouble setting it up thanks to the great work you have done. I recently upgraded from Suse 8.2 to Suse 9.1. Currently I am having trouble with scanimage not finding my scanner. I have tested the scanner on a Windows 2000 machine and it is working fine on there. I never had this problem on Suse 8.2. In the dll.conf file I have commented out everything except for the "mustek_pp" and in the mustek_pp.conf file I have commented out everything except for the line "scanner mustek-cis600 * cis600". The following is what I get when I run "scanimage -L" after setting SANE_DEBUG_MUSTEK_PP=128 and SANE_DEBUG_SANEI_PA4S2=128: [sanei_debug] Setting debug level of mustek_pp to 128. [mustek_pp] sane-mustek_pp, version 0.13-beta. build for SANE 1.0.14 [mustek_pp] backend by Jochen Eisinger [sanei_debug] Setting debug level of sanei_pa4s2 to 128. [sanei_pa4s2] sanei_pa4s2: interface called for the first time [sanei_pa4s2] sanei_pa4s2_devices: invoked [sanei_pa4s2] pa4s2_init: static int first_time = 1 [sanei_pa4s2] pa4s2_init: called for the first time [sanei_pa4s2] pa4s2_init: initializing libieee1284 [sanei_pa4s2] pa4s2_init: 1 ports reported by IEEE 1284 library [sanei_pa4s2] pa4s2_init: port 0 is `parport0` [sanei_pa4s2] pa4s2_init: allocating port list [sanei_pa4s2] pa4s2_init: initialized successfully [mustek_pp] sanei_init: auto probing port [sanei_pa4s2] sanei_pa4s2_open: called for device 'parport0' [sanei_pa4s2] sanei_pa4s2_open: trying to connect to port [sanei_pa4s2] pa4s2_open: trying to attach dev `parport0` [sanei_pa4s2] pa4s2_init: static int first_time = 0 [sanei_pa4s2] pa4s2_init: sanei already initalized [sanei_pa4s2] pa4s2_open: looking up port in list [sanei_pa4s2] pa4s2_open: port is in list at port[0] [sanei_pa4s2] pa4s2_open: setting up port data [sanei_pa4s2] pa4s2_open: name=parport0 in_use=SANE_TRUE [sanei_pa4s2] pa4s2_open: enabled=SANE_FALSE mode=PA4S2_MODE_NIB [sanei_pa4s2] pa4s2_open: opening device [sanei_pa4s2] pa4s2_open: device `parport0` opened... [sanei_pa4s2] pa4s2_open: returning SANE_STATUS_GOOD [sanei_pa4s2] pa4s2_open: open dev `parport0` as fd 0 [sanei_pa4s2] sanei_pa4s2_open: connected to device using fd 0 [sanei_pa4s2] sanei_pa4s2_open: checking for scanner [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1 [sanei_pa4s2] sanei_pa4s2_enable: enable port 'parport0' [sanei_pa4s2] pa4s2_enable: prelock[] = {0xff, 0x47, 0x0c} [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: reading ASIC id [sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0 [sanei_pa4s2] sanei_pa4s2_readbegin: NIB readbegin [sanei_pa4s2] pa4s2_readbegin_nib: selecting register 0 at 'parport0' [sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0 [sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readbyte: read in NIB mode [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5 from 'parport0' [sanei_pa4s2] sanei_pa4s2_readbyte: read finished [sanei_pa4s2] sanei_pa4s2_readbyte: got value 0xa5 [sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readend: called for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readend: NIB mode readend [sanei_pa4s2] pa4s2_readend_nib: end of reading sequence for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: detected ASIC id 1015 [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0 [sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0' [sanei_pa4s2] pa4s2_disable: state restored [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: trying better modes [sanei_pa4s2] sanei_pa4s2_open: trying mode 0 [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1 [sanei_pa4s2] sanei_pa4s2_enable: enable port 'parport0' [sanei_pa4s2] pa4s2_enable: prelock[] = {0xff, 0x47, 0x0c} [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0 [sanei_pa4s2] sanei_pa4s2_readbegin: NIB readbegin [sanei_pa4s2] pa4s2_readbegin_nib: selecting register 0 at 'parport0' [sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0 [sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readbyte: read in NIB mode [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5 from 'parport0' [sanei_pa4s2] sanei_pa4s2_readbyte: read finished [sanei_pa4s2] sanei_pa4s2_readbyte: got value 0xa5 [sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readend: called for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readend: NIB mode readend [sanei_pa4s2] pa4s2_readend_nib: end of reading sequence for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0 [sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0' [sanei_pa4s2] pa4s2_disable: state restored [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: mode works [sanei_pa4s2] sanei_pa4s2_open: skipping mode UNI [sanei_pa4s2] sanei_pa4s2_open: trying mode 2 [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1 [sanei_pa4s2] sanei_pa4s2_enable: enable port 'parport0' [sanei_pa4s2] pa4s2_enable: prelock[] = {0xff, 0x47, 0x0c} [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0 [sanei_pa4s2] sanei_pa4s2_readbegin: EPP readbegin [sanei_pa4s2] pa4s2_readbegin_epp: selecting register 0 at 'parport0' [sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0 [sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readbyte: read in EPP mode [sanei_pa4s2] pa4s2_readbyte_epp: reading value 0xfd from 'parport0' [sanei_pa4s2] sanei_pa4s2_readbyte: read finished [sanei_pa4s2] sanei_pa4s2_readbyte: got value 0xfd [sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readend: called for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readend: EPP mode readend [sanei_pa4s2] pa4s2_readend_epp: end of reading sequence [sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0 [sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0' [sanei_pa4s2] pa4s2_disable: state restored [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: mode failed [sanei_pa4s2] sanei_pa4s2_open: returned ASIC-ID 0xfd [sanei_pa4s2] sanei_pa4s2_open: using mode 0 [sanei_pa4s2] sanei_pa4s2_open: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1 [sanei_pa4s2] sanei_pa4s2_enable: enable port 'parport0' [sanei_pa4s2] pa4s2_enable: prelock[] = {0xff, 0x8f, 0x0c} [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0 [sanei_pa4s2] sanei_pa4s2_readbegin: NIB readbegin [sanei_pa4s2] pa4s2_readbegin_nib: selecting register 0 at 'parport0' [sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0 [sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readbyte: read in NIB mode [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x00 from 'parport0' [sanei_pa4s2] sanei_pa4s2_readbyte: read finished [sanei_pa4s2] sanei_pa4s2_readbyte: got value 0x00 [sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readend: called for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readend: NIB mode readend [sanei_pa4s2] pa4s2_readend_nib: end of reading sequence for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0 [sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0' [sanei_pa4s2] pa4s2_disable: state restored [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_close: fd = 0 [sanei_pa4s2] sanei_pa4s2_close: freeing resources [sanei_pa4s2] pa4s2_close: fd=0 [sanei_pa4s2] pa4s2_close: this is port 'parport0' [sanei_pa4s2] pa4s2_close: checking whether port is enabled [sanei_pa4s2] pa4s2_close: trying to free io port [sanei_pa4s2] pa4s2_close: marking port as unused [sanei_pa4s2] pa4s2_close: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_close: finished [mustek_pp] cis_attach: asic id (0x00) not recognized 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). [mustek_pp] sane_exit: all drivers unloaded >From what I have read it appears that the "asic id" it is giving back in invalid, but I have no idea what would be causing that since the scanner works fine in Windows. Please let me know if you need any more information, oh, and "sane-find-scanner -p" says it found a possible Mustek scanner but it cannot find the correct driver. I have a printer attached but I have shut it off to make sure it isn't causing any problems. Any feedback you could give me wouldbe greatly appreciated! Thanks! Neal _________________________________________________________________ Get fast, reliable Internet access with MSN 9 Dial-up – now 3 months FREE! http://join.msn.click-url.com/go/onm00200361ave/direct/01/ From keith@claytons.org Thu Jun 10 16:32:26 2004 From: keith@claytons.org (Keith Clayton) Date: Thu, 10 Jun 2004 08:32:26 -0700 (PDT) Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <1086879836.2126.2.camel@Babylon7> References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> <1086879836.2126.2.camel@Babylon7> Message-ID: No, still running 0.90 on the windows box. I upgraded to 0.94 on the linux box and looked for windows binaries at the same time. Didn't see them. Did I miss it? K On Thu, 10 Jun 2004, Oliver Rauch wrote: > For windows you can not enable a debug output - at least I do not know > a way with the published binaries because they are compiled as GUI. > > BTW. Did you ever test xsane-0.94-win32? > > Oliver > > Am Don, 2004-06-10 um 16.09 schrieb Keith Clayton: > > What sort of steps are availble for me to take debugging-wise on the > > windows end? > > > > If xsane is started from the command prompt, are there any swithces > > available to generate debugging output at the command prompt? > > > > K > > > > > > > > On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > > > > > Hi, > > > > > > On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > > > > Hate when I do that . . here's the xsane logs described in my previous > > > > email > > > > > > Ok, let's look at the second log. The preview scan looks ok (but I > > > don't know the details of the plustek backend). The real scan also > > > starts fine and then we see this: > > > > > > [plustek] sane_read - read 3750 bytes > > > [saned] do_scan: read 3750 bytes from scanner > > > [plustek] usb_ScanReadImage() done, result: 0 > > > [plustek] usb_ReadData() > > > [plustek] usb_ScanReadImage(3760) > > > [plustek] usb_ScanReadImage() done, result: 0 > > > [saned] do_scan: trying to write 3754 bytes to client > > > [saned] do_scan: wrote 3754 bytes to client > > > [saned] do_scan: trying to read 1521 bytes from scanner > > > [plustek] sane_read - read 1521 bytes > > > [saned] do_scan: read 1521 bytes from scanner > > > > > > Now these 1521 bytes should be sent to the frontend... > > > > > > [saned] do_scan: processing RPC request on fd 4 > > > [saned] process_request: waiting for request > > > [saned] process_request: bad status 22 > > > > > > saned thinks something has been sent to it by the control (not data) > > > connection. But when trying to decode what was sent it gets an error > > > when reading the first word. 22 is "invalid argument". That means that > > > no data could be read. Maybe xsane has crashed on the clent side > > > meanwhile? > > > > > > Usually during the scan nothing is sent to the control file descriptor. > > > > > > Anyway. As sane_cancel isn't called the reader_process in the plustek > > > backend isn't killed and the plustek backend gets confused. > > > > > > So my impression is that the problem is with xsane (or the net > > > frontend on windows) and the scanner lockup is just a consequence. > > > But I don't know why xsane (or the net backend) crashes. So maybe > > > finding out the details here may help- E.g. gdb xsane on the client or > > > enabling debugging for xsane and the net backend and looking at the > > > last few lines before the crash. > > > > > > Maybe the xsane and plustek maintainers can have a look at the > > > logfiles, too? > > > > > > Bye, > > > Henning > > > > > > > > > From David@phenix.fr Thu Jun 10 16:46:29 2004 From: David@phenix.fr (David Neary) Date: Thu, 10 Jun 2004 17:46:29 +0200 Subject: [sane-devel] RE: sane-devel digest, Vol 1 #365 - 11 msgs Message-ID: Hi, Keith Clayton wrote: > What sort of steps are availble for me to take debugging-wise on the > windows end? > > If xsane is started from the command prompt, are there any swithces > available to generate debugging output at the command prompt? As Henning said, you just need to set your environment variables XSANE_DEBUG and SANE_DEBUG_NET. You can set these as: set XSANE_DEBUG=255 set SANE_DEBUG_NET=255 and then run scanimage.exe or xsane.exe to see what's happenning. Make sure you have set the SANE_CONFIG_DIR environment variable to point to where your dll.conf and net.conf are on the disk, otherwise nothing will work (set SANE_CONFIG_DIR=C:\xsane for example). In case this gives you a problem, check your version of sane, since 1.0.13 didn't have the path separators and directory separators set correctly for win32. Cheers, Dave. From misc@tomweissmann.org Thu Jun 10 17:08:47 2004 From: misc@tomweissmann.org (Tom Schutzer-Weissmann) Date: Thu, 10 Jun 2004 17:08:47 +0100 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> Message-ID: <20040610170847.5c305388@expensive> On Thu, 10 Jun 2004 05:36:52 -0400 Karl Heinz Kremer wrote: > I'm also reading sane-devel, so no need to take a detour with > any Epson backend related information :-) > I've never experienced any of the problem you describe, and I've > been running a 2.6.x kernel for some time now (SuSE 9.1 beta versions > and the final SuSE 9.1). > > I've tried this with two different USB controllers (USB-1.1 and high > speed USB-2) with a number of different Epson scanners. > > Karl Heinz Thank you for all your responses. I'm using Debian unstable, kernel 2.6.6 with ohci_usb, libusb-0-1.4 (0.1.8-11). The scanner is an Epson Perfection 2450. It seems libusb isn't working as it should - maybe future Debian updates will solve the problem; in the meantime I am happy with my hack, but if anyone would like me to try out some suggestions to get to the bottom of this mystery, I'd be happy to help off-list. Regards, Tom From mattias.ellert@tsl.uu.se Thu Jun 10 21:14:02 2004 From: mattias.ellert@tsl.uu.se (Mattias Ellert) Date: Thu, 10 Jun 2004 22:14:02 +0200 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? In-Reply-To: References: Message-ID: <40C8C10A.5080500@tsl.uu.se> This is a cryptographically signed message in MIME format. --------------ms070607030900050808020401 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Allan Kaplan wrote: > Hi Mattias, > > I am happy to report a little progress. Once I installed the proper files > I did recognize the scanner, but that's all. I tried the other commands > with no progress. I am suspicious that the codes returned by sane are > generic "we really don't know anything about this scanner" information. So > what's what you say my next step is? Crack open the scanner and post the > info on the chipset and pray? Am I really out of luck? > > Thanks for all your help, > > Allan > > Here's the transcript. I took out most of the annotations. > > Last login: Thu Jun 10 00:25:37 on ttyp1 > Welcome to Darwin! > [Lolita:~] amkaplan% /usr/local/bin/sane-find-scanner > > > found USB scanner (vendor=0x0475, product=0x0100) at > libusb:003:002-0475-0100-ff-00 > # Your USB scanner was (probably) detected. It may or may not be supported > by > # SANE. Try scanimage -L and read the backend's manpage. > Could you run sane-find-scanner in very verbose mode (as suggested by Henning in his answer to the mailing list): sane-find-scanner -v -v This should hopefully give some information. According to http://www.linux-usb.org/usb.ids the vendor ID 0475 is "Relisys/Teco Information System" and not NEC, but this is probably not significant -- there are a lot of scanners that are produced by one company and sold by an other. According to http://www.sane-project.org/sane-mfgs.html there only seem to exist SANE drivers for Relisys SCSI scanners. The Relisys USB scanners mentioned in the list (0475-0103, 0475-0270) are all listed as "probably unsupported". And this one is (0475-0100) not mentioned, either under Relisys or NEC. Mattias -- ________________________________________________________________________ mattias.ellert@tsl.uu.se tel: +46 18 471 32 58 http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13 ________________________________________________________________________ --------------ms070607030900050808020401 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGbDCC AzIwggKboAMCAQICAgJ2MA0GCSqGSIb3DQEBBAUAME8xDTALBgNVBAoTBEdyaWQxEjAQBgNV BAoTCU5vcmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVHcmlkIENlcnRpZmljYXRpb24gQXV0aG9y aXR5MB4XDTA0MDUwNDE0MjY0MVoXDTA1MDUwNDE0MjY0MVowUDENMAsGA1UEChMER3JpZDES MBAGA1UEChMJTm9yZHVHcmlkMRIwEAYDVQQLEwl0c2wudXUuc2UxFzAVBgNVBAMTDk1hdHRp YXMgRWxsZXJ0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDV8f0oE9EY8Zc7W18Puyjc ZAZUPXqwDqMJigz+FKIy2Tqy3Xcv8hAXk/VM+wU+RZMpfwwRihb0TFYAvqsuHn6rV6Z4xUhn B5uUjlNp4vBomtPcXOwVBSpflFyMVdkUCTQls+rIoHo/jO07W1NZMRXxBTWoSC/YXfbV9MsP +6MsFwIDAQABo4IBGjCCARYwCQYDVR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0P BAQDAgXgMCwGCWCGSAGG+EIBDQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAd BgNVHQ4EFgQUHC2rjql+Xupjzclc4OC8+kH0iQUwdwYDVR0jBHAwboAUGAXA/AvRtzr0ZZIJ +1mhX8eIxPChU6RRME8xDTALBgNVBAoTBEdyaWQxEjAQBgNVBAoTCU5vcmR1R3JpZDEqMCgG A1UEAxMhTm9yZHVHcmlkIENlcnRpZmljYXRpb24gQXV0aG9yaXR5ggEAMCMGA1UdEQQcMBqB GG1hdHRpYXMuZWxsZXJ0QHRzbC51dS5zZTANBgkqhkiG9w0BAQQFAAOBgQBJVHRvfXvI5bjp 2wX92F0MONzIxczNls3F1HBg/GSQ5zq89mGidKVNbbv61r0TztpWOew1r2DfuexFsdLG1mgH RPtLzWaYnEpAPcJx4DECHqm2cmp+NOP2eWv8hI3uL/279Lxm0B6wIU7V5v/I83kUVZ/JJrNs 5wvrsTRYaKyuVDCCAzIwggKboAMCAQICAgJ2MA0GCSqGSIb3DQEBBAUAME8xDTALBgNVBAoT BEdyaWQxEjAQBgNVBAoTCU5vcmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVHcmlkIENlcnRpZmlj YXRpb24gQXV0aG9yaXR5MB4XDTA0MDUwNDE0MjY0MVoXDTA1MDUwNDE0MjY0MVowUDENMAsG A1UEChMER3JpZDESMBAGA1UEChMJTm9yZHVHcmlkMRIwEAYDVQQLEwl0c2wudXUuc2UxFzAV BgNVBAMTDk1hdHRpYXMgRWxsZXJ0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDV8f0o E9EY8Zc7W18PuyjcZAZUPXqwDqMJigz+FKIy2Tqy3Xcv8hAXk/VM+wU+RZMpfwwRihb0TFYA vqsuHn6rV6Z4xUhnB5uUjlNp4vBomtPcXOwVBSpflFyMVdkUCTQls+rIoHo/jO07W1NZMRXx BTWoSC/YXfbV9MsP+6MsFwIDAQABo4IBGjCCARYwCQYDVR0TBAIwADARBglghkgBhvhCAQEE BAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBD ZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUHC2rjql+Xupjzclc4OC8+kH0iQUwdwYDVR0jBHAwboAU GAXA/AvRtzr0ZZIJ+1mhX8eIxPChU6RRME8xDTALBgNVBAoTBEdyaWQxEjAQBgNVBAoTCU5v cmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVHcmlkIENlcnRpZmljYXRpb24gQXV0aG9yaXR5ggEA MCMGA1UdEQQcMBqBGG1hdHRpYXMuZWxsZXJ0QHRzbC51dS5zZTANBgkqhkiG9w0BAQQFAAOB gQBJVHRvfXvI5bjp2wX92F0MONzIxczNls3F1HBg/GSQ5zq89mGidKVNbbv61r0TztpWOew1 r2DfuexFsdLG1mgHRPtLzWaYnEpAPcJx4DECHqm2cmp+NOP2eWv8hI3uL/279Lxm0B6wIU7V 5v/I83kUVZ/JJrNs5wvrsTRYaKyuVDGCAn4wggJ6AgEBMFUwTzENMAsGA1UEChMER3JpZDES MBAGA1UEChMJTm9yZHVHcmlkMSowKAYDVQQDEyFOb3JkdUdyaWQgQ2VydGlmaWNhdGlvbiBB dXRob3JpdHkCAgJ2MAkGBSsOAwIaBQCgggF/MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw HAYJKoZIhvcNAQkFMQ8XDTA0MDYxMDIwMTQwMlowIwYJKoZIhvcNAQkEMRYEFMDrjnzZEk4h PqDvVAbzsu6z72buMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMGQGCSsGAQQBgjcQ BDFXMFUwTzENMAsGA1UEChMER3JpZDESMBAGA1UEChMJTm9yZHVHcmlkMSowKAYDVQQDEyFO b3JkdUdyaWQgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkCAgJ2MGYGCyqGSIb3DQEJEAILMVeg VTBPMQ0wCwYDVQQKEwRHcmlkMRIwEAYDVQQKEwlOb3JkdUdyaWQxKjAoBgNVBAMTIU5vcmR1 R3JpZCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eQICAnYwDQYJKoZIhvcNAQEBBQAEgYCpIPZ7 7yO0fWpfU/jPh8V7qPERlOXQtQgQiP+Jnlm+YMkfRh78cPUloIC+aUqMlIW7O3wnuanmByWa VI/ikOE46wLtf5VEZSsm4QV7bOYOgpYsDOZnkf4xJ8zKUJIPqiH8HnuAfsu4PeXPPx+H8GT4 wH7aLVf3Rxes+6m2S3AEMgAAAAAAAA== --------------ms070607030900050808020401-- From olaf@epkowa.co.jp Fri Jun 11 01:37:21 2004 From: olaf@epkowa.co.jp (Olaf Meeuwissen) Date: Fri, 11 Jun 2004 09:37:21 +0900 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <20040610170847.5c305388@expensive> (Tom Schutzer-Weissmann's message of "Thu, 10 Jun 2004 17:08:47 +0100") References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> <20040610170847.5c305388@expensive> Message-ID: <87r7snudz2.fsf@zen.epkowa.co.jp> Tom Schutzer-Weissmann writes: > On Thu, 10 Jun 2004 05:36:52 -0400 > Karl Heinz Kremer wrote: > >> I'm also reading sane-devel, so no need to take a detour with >> any Epson backend related information :-) >> I've never experienced any of the problem you describe, and I've >> been running a 2.6.x kernel for some time now (SuSE 9.1 beta versions >> and the final SuSE 9.1). >> >> I've tried this with two different USB controllers (USB-1.1 and high >> speed USB-2) with a number of different Epson scanners. >> >> Karl Heinz > > Thank you for all your responses. > > I'm using Debian unstable, kernel 2.6.6 with ohci_usb, libusb-0-1.4 > (0.1.8-11). The scanner is an Epson Perfection 2450. That's what you get for running bleeding edge ;-) I'm using Debian testing, kernel 2.6.6 with uhci_hcd (and ehci_hcd), libusb-0.1-4 (0.1.8-11) and will see if I can lay my hands on a Perfection 2450. The USB modules are autoprobed, I don't have anything USB related in my /etc/modules-2.6. There is an usb-uhci in my /etc/modules but IIRC that file is not used if /etc/modules-2.6 exists. > It seems libusb isn't working as it should - maybe future Debian > updates will solve the problem; in the meantime I am happy with my > hack, but if anyone would like me to try out some suggestions to get > to the bottom of this mystery, I'd be happy to help off-list. As I'm using the same libusb as you do, I am sceptical about libusb being the culprit. Apart from the usb module and scanner model, we use the same setup. I'll get back with the results on the Perfection 2450 ASAP. HTH, -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From mattias.ellert@tsl.uu.se Fri Jun 11 02:17:33 2004 From: mattias.ellert@tsl.uu.se (Mattias Ellert) Date: Fri, 11 Jun 2004 03:17:33 +0200 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? Message-ID: <40C9082D.9030200@tsl.uu.se> This is a cryptographically signed message in MIME format. --------------ms090808030104000206020707 Content-Type: multipart/mixed; boundary="------------050503010401050303030202" This is a multi-part message in MIME format. --------------050503010401050303030202 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi! I forward this to sane-devel.... Mattias -------- Original Message -------- Subject: Re: [sane-devel] NEC Petiscan driver for MacOSX possible? Date: Thu, 10 Jun 2004 17:58:02 -0700 From: Allan Kaplan To: Mattias Ellert Hi Mattias, I did the verbose command and got back a verbose response. Here's what applies to the scanner, with the whole thing as an attachment. I hope it makes some sense to you, because all I found was that it doesn't recognize the chipset. Does this help at all? What do you suggest as a next step? Many thanks, Allan bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 255 bDeviceSubClass 0 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x0475 idProduct 0x0100 bcdDevice 1.00 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 128 () MaxPower 500 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x01 (out 0x01) bmAttributes 2 (bulk) wMaxPacketSize 8 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 8 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 checking for GT-6801 ... this is not a GT-6801 (bcdUSB = 0x100) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bDeviceSubClass = 0x0) checking for MA-1509 ... this is not a MA-1509 (bcdUSB = 0x100) checking for LM983[1,2,3] ... this is not a LM983x (bEndpointAddress = 0x1, bmAttributes = 0x2, wMaxPacketSize = 0x8, bInterval = 0x0) checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x100) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... this is not a GL841 (bcdUSB = 0x100) checking for ICM532B ... check 2, this is not a ICM532B (bcdUSB = 0x100) found USB scanner (vendor=0x0475, product=0x0100) at libusb:003:002-0475-0100-ff-00 -- ________________________________________________________________________ mattias.ellert@tsl.uu.se tel: +46 18 471 32 58 http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13 ________________________________________________________________________ --------------050503010401050303030202 Content-Type: application/octet-stream; name="-v -v.rtf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="-v -v.rtf" e1xydGYxXG1hY1xhbnNpY3BnMTAwMDBcY29jb2FydGYxMDIKe1xmb250dGJsXGYwXGZzd2lz c1xmY2hhcnNldDc3IEhlbHZldGljYTt9CntcY29sb3J0Ymw7XHJlZDI1NVxncmVlbjI1NVxi bHVlMjU1O30KXG1hcmdsMTQ0MFxtYXJncjE0NDBcdmlld3c5MDAwXHZpZXdoOTAwMFx2aWV3 a2luZDAKXHBhcmRcdHg3MjBcdHgxNDQwXHR4MjE2MFx0eDI4ODBcdHgzNjAwXHR4NDMyMFx0 eDUwNDBcdHg1NzYwXHR4NjQ4MFx0eDcyMDBcdHg3OTIwXHR4ODY0MFxxbFxxbmF0dXJhbAoK XGYwXGZzMjQgXGNmMCBMYXN0IGxvZ2luOiBUaHUgSnVuIDEwIDExOjQyOjM0IG9uIGNvbnNv bGVcCldlbGNvbWUgdG8gRGFyd2luIVwKW0xvbGl0YTp+XSBhbWthcGxhbiUgL3Vzci9sb2Nh bC9iaW4vc2FuZS1maW5kLXNjYW5uZXJcClwKICAjIE5vIFNDU0kgc2Nhbm5lcnMgZm91bmQu IElmIHlvdSBleHBlY3RlZCBzb21ldGhpbmcgZGlmZmVyZW50LCBtYWtlIHN1cmUgdGhhdFwK ICAjIHlvdSBoYXZlIGxvYWRlZCBhIFNDU0kgZHJpdmVyIGZvciB5b3VyIFNDU0kgYWRhcHRl ci5cClwKZm91bmQgVVNCIHNjYW5uZXIgKHZlbmRvcj0weDA0NzUsIHByb2R1Y3Q9MHgwMTAw KSBhdCBsaWJ1c2I6MDAzOjAwMi0wNDc1LTAxMDAtZmYtMDBcCiAgIyBZb3VyIFVTQiBzY2Fu bmVyIHdhcyAocHJvYmFibHkpIGRldGVjdGVkLiBJdCBtYXkgb3IgbWF5IG5vdCBiZSBzdXBw b3J0ZWQgYnlcCiAgIyBTQU5FLiBUcnkgc2NhbmltYWdlIC1MIGFuZCByZWFkIHRoZSBiYWNr ZW5kJ3MgbWFucGFnZS5cClwKICAjIE5vdCBjaGVja2luZyBmb3IgcGFyYWxsZWwgcG9ydCBz Y2FubmVycy5cClwKICAjIE1vc3QgU2Nhbm5lcnMgY29ubmVjdGVkIHRvIHRoZSBwYXJhbGxl bCBwb3J0IG9yIG90aGVyIHByb3ByaWV0YXJ5IHBvcnRzXAogICMgY2FuJ3QgYmUgZGV0ZWN0 ZWQgYnkgdGhpcyBwcm9ncmFtLlwKXAogICMgWW91IG1heSB3YW50IHRvIHJ1biB0aGlzIHBy b2dyYW0gYXMgcm9vdCB0byBmaW5kIGFsbCBkZXZpY2VzLiBPbmNlIHlvdVwKICAjIGZvdW5k IHRoZSBzY2FubmVyIGRldmljZXMsIGJlIHN1cmUgdG8gYWRqdXN0IGFjY2VzcyBwZXJtaXNz aW9ucyBhc1wKICAjIG5lY2Vzc2FyeS5cCltMb2xpdGE6fl0gYW1rYXBsYW4lIC91c3IvbG9j YWwvYmluL3NhbmUtZmluZC1zY2FubmVyIC12IC12XApcCnNlYXJjaGluZyBmb3IgU0NTSSBz Y2FubmVyczpcCiAgIyBObyBTQ1NJIHNjYW5uZXJzIGZvdW5kLiBJZiB5b3UgZXhwZWN0ZWQg c29tZXRoaW5nIGRpZmZlcmVudCwgbWFrZSBzdXJlIHRoYXRcCiAgIyB5b3UgaGF2ZSBsb2Fk ZWQgYSBTQ1NJIGRyaXZlciBmb3IgeW91ciBTQ1NJIGFkYXB0ZXIuXApcCnNlYXJjaGluZyBm b3IgVVNCIHNjYW5uZXJzOlwKdHJ5aW5nIGxpYnVzYjpcClwKPGRldmljZSBkZXNjcmlwdG9y IG9mIDB4MDVhYy8weDgwMDUgYXQgMDAxOjAwMS0wNWFjLTgwMDUtMDktMDAgKEFwcGxlIENv bXB1dGVyLCBJbmMuIE9IQ0kgUm9vdCBIdWIgU2ltdWxhdGlvbik+XApiTGVuZ3RoICAgICAg ICAgICAgICAgMThcCmJEZXNjcmlwdG9yVHlwZSAgICAgICAxXApiY2RVU0IgICAgICAgICAg ICAgICAgMS4wMFwKYkRldmljZUNsYXNzICAgICAgICAgIDlcCmJEZXZpY2VTdWJDbGFzcyAg ICAgICAwXApiRGV2aWNlUHJvdG9jb2wgICAgICAgMFwKYk1heFBhY2tldFNpemUwICAgICAg IDhcCmlkVmVuZG9yICAgICAgICAgICAgICAweDA1QUNcCmlkUHJvZHVjdCAgICAgICAgICAg ICAweDgwMDVcCmJjZERldmljZSAgICAgICAgICAgICAxLjkwXAppTWFudWZhY3R1cmVyICAg ICAgICAgMiAoQXBwbGUgQ29tcHV0ZXIsIEluYy4pXAppUHJvZHVjdCAgICAgICAgICAgICAg MSAoT0hDSSBSb290IEh1YiBTaW11bGF0aW9uKVwKaVNlcmlhbE51bWJlciAgICAgICAgIDAg KClcCmJOdW1Db25maWd1cmF0aW9ucyAgICAxXAogPGNvbmZpZ3VyYXRpb24gMD5cCiBiTGVu Z3RoICAgICAgICAgICAgICAxMFwKIGJEZXNjcmlwdG9yVHlwZSAgICAgIDJcCiB3VG90YWxM ZW5ndGggICAgICAgICAyN1wKIGJOdW1JbnRlcmZhY2VzICAgICAgIDFcCiBiQ29uZmlndXJh dGlvblZhbHVlICAxXAogaUNvbmZpZ3VyYXRpb24gICAgICAgMCAoKVwKIGJtQXR0cmlidXRl cyAgICAgICAgIDk2IChTZWxmLXBvd2VyZWRSZW1vdGUgV2FrZXVwKVwKIE1heFBvd2VyICAg ICAgICAgICAgIDAgbUFcCiAgPGludGVyZmFjZSAwPlwKICAgPGFsdHNldHRpbmcgMD5cCiAg IGJMZW5ndGggICAgICAgICAgICA5XAogICBiRGVzY3JpcHRvclR5cGUgICAgNFwKICAgYklu dGVyZmFjZU51bWJlciAgIDBcCiAgIGJBbHRlcm5hdGVTZXR0aW5nICAwXAogICBiTnVtRW5k cG9pbnRzICAgICAgMVwKICAgYkludGVyZmFjZUNsYXNzICAgIDlcCiAgIGJJbnRlcmZhY2VT dWJDbGFzcyAwXAogICBiSW50ZXJmYWNlUHJvdG9jb2wgMVwKICAgaUludGVyZmFjZSAgICAg ICAgIDAgKClcCiAgICA8ZW5kcG9pbnQgMD5cCiAgICBiTGVuZ3RoICAgICAgICAgICA4XAog ICAgYkRlc2NyaXB0b3JUeXBlICAgNVwKICAgIGJFbmRwb2ludEFkZHJlc3MgIDB4ODEgKGlu IDB4MDEpXAogICAgYm1BdHRyaWJ1dGVzICAgICAgMyAoaW50ZXJydXB0KVwKICAgIHdNYXhQ YWNrZXRTaXplICAgIDhcCiAgICBiSW50ZXJ2YWwgICAgICAgICAyNTUgbXNcCiAgICBiUmVm cmVzaCAgICAgICAgICAwXAogICAgYlN5bmNoQWRkcmVzcyAgICAgMFwKZGV2aWNlIDB4MDAw MC8weDAwMDAgaXMgbm90IGNvbmZpZ3VyZWRcClwKPGRldmljZSBkZXNjcmlwdG9yIG9mIDB4 MDVhYy8weDgwMDUgYXQgMDAyOjAwMS0wNWFjLTgwMDUtMDktMDAgKEFwcGxlIENvbXB1dGVy LCBJbmMuIE9IQ0kgUm9vdCBIdWIgU2ltdWxhdGlvbik+XApiTGVuZ3RoICAgICAgICAgICAg ICAgMThcCmJEZXNjcmlwdG9yVHlwZSAgICAgICAxXApiY2RVU0IgICAgICAgICAgICAgICAg MS4wMFwKYkRldmljZUNsYXNzICAgICAgICAgIDlcCmJEZXZpY2VTdWJDbGFzcyAgICAgICAw XApiRGV2aWNlUHJvdG9jb2wgICAgICAgMFwKYk1heFBhY2tldFNpemUwICAgICAgIDhcCmlk VmVuZG9yICAgICAgICAgICAgICAweDA1QUNcCmlkUHJvZHVjdCAgICAgICAgICAgICAweDgw MDVcCmJjZERldmljZSAgICAgICAgICAgICAxLjkwXAppTWFudWZhY3R1cmVyICAgICAgICAg MiAoQXBwbGUgQ29tcHV0ZXIsIEluYy4pXAppUHJvZHVjdCAgICAgICAgICAgICAgMSAoT0hD SSBSb290IEh1YiBTaW11bGF0aW9uKVwKaVNlcmlhbE51bWJlciAgICAgICAgIDAgKClcCmJO dW1Db25maWd1cmF0aW9ucyAgICAxXAogPGNvbmZpZ3VyYXRpb24gMD5cCiBiTGVuZ3RoICAg ICAgICAgICAgICAxMFwKIGJEZXNjcmlwdG9yVHlwZSAgICAgIDJcCiB3VG90YWxMZW5ndGgg ICAgICAgICAyN1wKIGJOdW1JbnRlcmZhY2VzICAgICAgIDFcCiBiQ29uZmlndXJhdGlvblZh bHVlICAxXAogaUNvbmZpZ3VyYXRpb24gICAgICAgMCAoKVwKIGJtQXR0cmlidXRlcyAgICAg ICAgIDk2IChTZWxmLXBvd2VyZWRSZW1vdGUgV2FrZXVwKVwKIE1heFBvd2VyICAgICAgICAg ICAgIDAgbUFcCiAgPGludGVyZmFjZSAwPlwKICAgPGFsdHNldHRpbmcgMD5cCiAgIGJMZW5n dGggICAgICAgICAgICA5XAogICBiRGVzY3JpcHRvclR5cGUgICAgNFwKICAgYkludGVyZmFj ZU51bWJlciAgIDBcCiAgIGJBbHRlcm5hdGVTZXR0aW5nICAwXAogICBiTnVtRW5kcG9pbnRz ICAgICAgMVwKICAgYkludGVyZmFjZUNsYXNzICAgIDlcCiAgIGJJbnRlcmZhY2VTdWJDbGFz cyAwXAogICBiSW50ZXJmYWNlUHJvdG9jb2wgMVwKICAgaUludGVyZmFjZSAgICAgICAgIDAg KClcCiAgICA8ZW5kcG9pbnQgMD5cCiAgICBiTGVuZ3RoICAgICAgICAgICA4XAogICAgYkRl c2NyaXB0b3JUeXBlICAgNVwKICAgIGJFbmRwb2ludEFkZHJlc3MgIDB4ODEgKGluIDB4MDEp XAogICAgYm1BdHRyaWJ1dGVzICAgICAgMyAoaW50ZXJydXB0KVwKICAgIHdNYXhQYWNrZXRT aXplICAgIDhcCiAgICBiSW50ZXJ2YWwgICAgICAgICAyNTUgbXNcCiAgICBiUmVmcmVzaCAg ICAgICAgICAwXAogICAgYlN5bmNoQWRkcmVzcyAgICAgMFwKXAo8ZGV2aWNlIGRlc2NyaXB0 b3Igb2YgMHgwNWFjLzB4ODAwNSBhdCAwMDM6MDAxLTA1YWMtODAwNS0wOS0wMCAoQXBwbGUg Q29tcHV0ZXIsIEluYy4gT0hDSSBSb290IEh1YiBTaW11bGF0aW9uKT5cCmJMZW5ndGggICAg ICAgICAgICAgICAxOFwKYkRlc2NyaXB0b3JUeXBlICAgICAgIDFcCmJjZFVTQiAgICAgICAg ICAgICAgICAxLjAwXApiRGV2aWNlQ2xhc3MgICAgICAgICAgOVwKYkRldmljZVN1YkNsYXNz ICAgICAgIDBcCmJEZXZpY2VQcm90b2NvbCAgICAgICAwXApiTWF4UGFja2V0U2l6ZTAgICAg ICAgOFwKaWRWZW5kb3IgICAgICAgICAgICAgIDB4MDVBQ1wKaWRQcm9kdWN0ICAgICAgICAg ICAgIDB4ODAwNVwKYmNkRGV2aWNlICAgICAgICAgICAgIDEuOTBcCmlNYW51ZmFjdHVyZXIg ICAgICAgICAyIChBcHBsZSBDb21wdXRlciwgSW5jLilcCmlQcm9kdWN0ICAgICAgICAgICAg ICAxIChPSENJIFJvb3QgSHViIFNpbXVsYXRpb24pXAppU2VyaWFsTnVtYmVyICAgICAgICAg MCAoKVwKYk51bUNvbmZpZ3VyYXRpb25zICAgIDFcCiA8Y29uZmlndXJhdGlvbiAwPlwKIGJM ZW5ndGggICAgICAgICAgICAgIDEwXAogYkRlc2NyaXB0b3JUeXBlICAgICAgMlwKIHdUb3Rh bExlbmd0aCAgICAgICAgIDI3XAogYk51bUludGVyZmFjZXMgICAgICAgMVwKIGJDb25maWd1 cmF0aW9uVmFsdWUgIDFcCiBpQ29uZmlndXJhdGlvbiAgICAgICAwICgpXAogYm1BdHRyaWJ1 dGVzICAgICAgICAgOTYgKFNlbGYtcG93ZXJlZFJlbW90ZSBXYWtldXApXAogTWF4UG93ZXIg ICAgICAgICAgICAgMCBtQVwKICA8aW50ZXJmYWNlIDA+XAogICA8YWx0c2V0dGluZyAwPlwK ICAgYkxlbmd0aCAgICAgICAgICAgIDlcCiAgIGJEZXNjcmlwdG9yVHlwZSAgICA0XAogICBi SW50ZXJmYWNlTnVtYmVyICAgMFwKICAgYkFsdGVybmF0ZVNldHRpbmcgIDBcCiAgIGJOdW1F bmRwb2ludHMgICAgICAxXAogICBiSW50ZXJmYWNlQ2xhc3MgICAgOVwKICAgYkludGVyZmFj ZVN1YkNsYXNzIDBcCiAgIGJJbnRlcmZhY2VQcm90b2NvbCAxXAogICBpSW50ZXJmYWNlICAg ICAgICAgMCAoKVwKICAgIDxlbmRwb2ludCAwPlwKICAgIGJMZW5ndGggICAgICAgICAgIDhc CiAgICBiRGVzY3JpcHRvclR5cGUgICA1XAogICAgYkVuZHBvaW50QWRkcmVzcyAgMHg4MSAo aW4gMHgwMSlcCiAgICBibUF0dHJpYnV0ZXMgICAgICAzIChpbnRlcnJ1cHQpXAogICAgd01h eFBhY2tldFNpemUgICAgOFwKICAgIGJJbnRlcnZhbCAgICAgICAgIDI1NSBtc1wKICAgIGJS ZWZyZXNoICAgICAgICAgIDBcCiAgICBiU3luY2hBZGRyZXNzICAgICAwXApcCjxkZXZpY2Ug ZGVzY3JpcHRvciBvZiAweDA0NzUvMHgwMTAwIGF0IDAwMzowMDItMDQ3NS0wMTAwLWZmLTAw PlwKYkxlbmd0aCAgICAgICAgICAgICAgIDE4XApiRGVzY3JpcHRvclR5cGUgICAgICAgMVwK YmNkVVNCICAgICAgICAgICAgICAgIDEuMDBcCmJEZXZpY2VDbGFzcyAgICAgICAgICAyNTVc CmJEZXZpY2VTdWJDbGFzcyAgICAgICAwXApiRGV2aWNlUHJvdG9jb2wgICAgICAgMjU1XApi TWF4UGFja2V0U2l6ZTAgICAgICAgOFwKaWRWZW5kb3IgICAgICAgICAgICAgIDB4MDQ3NVwK aWRQcm9kdWN0ICAgICAgICAgICAgIDB4MDEwMFwKYmNkRGV2aWNlICAgICAgICAgICAgIDEu MDBcCmlNYW51ZmFjdHVyZXIgICAgICAgICAwICgpXAppUHJvZHVjdCAgICAgICAgICAgICAg MCAoKVwKaVNlcmlhbE51bWJlciAgICAgICAgIDAgKClcCmJOdW1Db25maWd1cmF0aW9ucyAg ICAxXAogPGNvbmZpZ3VyYXRpb24gMD5cCiBiTGVuZ3RoICAgICAgICAgICAgICA5XAogYkRl c2NyaXB0b3JUeXBlICAgICAgMlwKIHdUb3RhbExlbmd0aCAgICAgICAgIDM5XAogYk51bUlu dGVyZmFjZXMgICAgICAgMVwKIGJDb25maWd1cmF0aW9uVmFsdWUgIDFcCiBpQ29uZmlndXJh dGlvbiAgICAgICAwICgpXAogYm1BdHRyaWJ1dGVzICAgICAgICAgMTI4ICgpXAogTWF4UG93 ZXIgICAgICAgICAgICAgNTAwIG1BXAogIDxpbnRlcmZhY2UgMD5cCiAgIDxhbHRzZXR0aW5n IDA+XAogICBiTGVuZ3RoICAgICAgICAgICAgOVwKICAgYkRlc2NyaXB0b3JUeXBlICAgIDRc CiAgIGJJbnRlcmZhY2VOdW1iZXIgICAwXAogICBiQWx0ZXJuYXRlU2V0dGluZyAgMFwKICAg Yk51bUVuZHBvaW50cyAgICAgIDNcCiAgIGJJbnRlcmZhY2VDbGFzcyAgICAyNTVcCiAgIGJJ bnRlcmZhY2VTdWJDbGFzcyAyNTVcCiAgIGJJbnRlcmZhY2VQcm90b2NvbCAyNTVcCiAgIGlJ bnRlcmZhY2UgICAgICAgICAwICgpXAogICAgPGVuZHBvaW50IDA+XAogICAgYkxlbmd0aCAg ICAgICAgICAgN1wKICAgIGJEZXNjcmlwdG9yVHlwZSAgIDVcCiAgICBiRW5kcG9pbnRBZGRy ZXNzICAweDAxIChvdXQgMHgwMSlcCiAgICBibUF0dHJpYnV0ZXMgICAgICAyIChidWxrKVwK ICAgIHdNYXhQYWNrZXRTaXplICAgIDhcCiAgICBiSW50ZXJ2YWwgICAgICAgICAwIG1zXAog ICAgYlJlZnJlc2ggICAgICAgICAgMFwKICAgIGJTeW5jaEFkZHJlc3MgICAgIDBcCiAgICA8 ZW5kcG9pbnQgMT5cCiAgICBiTGVuZ3RoICAgICAgICAgICA3XAogICAgYkRlc2NyaXB0b3JU eXBlICAgNVwKICAgIGJFbmRwb2ludEFkZHJlc3MgIDB4ODIgKGluIDB4MDIpXAogICAgYm1B dHRyaWJ1dGVzICAgICAgMiAoYnVsaylcCiAgICB3TWF4UGFja2V0U2l6ZSAgICA4XAogICAg YkludGVydmFsICAgICAgICAgMCBtc1wKICAgIGJSZWZyZXNoICAgICAgICAgIDBcCiAgICBi U3luY2hBZGRyZXNzICAgICAwXAogICAgPGVuZHBvaW50IDI+XAogICAgYkxlbmd0aCAgICAg ICAgICAgN1wKICAgIGJEZXNjcmlwdG9yVHlwZSAgIDVcCiAgICBiRW5kcG9pbnRBZGRyZXNz ICAweDgzIChpbiAweDAzKVwKICAgIGJtQXR0cmlidXRlcyAgICAgIDIgKGJ1bGspXAogICAg d01heFBhY2tldFNpemUgICAgNjRcCiAgICBiSW50ZXJ2YWwgICAgICAgICAwIG1zXAogICAg YlJlZnJlc2ggICAgICAgICAgMFwKICAgIGJTeW5jaEFkZHJlc3MgICAgIDBcClwKPHRyeWlu ZyB0byBmaW5kIG91dCB3aGljaCBVU0IgY2hpcCBpcyB1c2VkPlwKICAgIGNoZWNraW5nIGZv ciBHVC02ODAxIC4uLlwKICAgIHRoaXMgaXMgbm90IGEgR1QtNjgwMSAoYmNkVVNCID0gMHgx MDApXAogICAgY2hlY2tpbmcgZm9yIEdULTY4MTYgLi4uXAogICAgdGhpcyBpcyBub3QgYSBH VC02ODE2IChiRGV2aWNlQ2xhc3MgPSAyNTUsIGJJbnRlcmZhY2VDbGFzcyA9IDI1NSlcCiAg ICBjaGVja2luZyBmb3IgTUEtMTAxNyAuLi5cCiAgICB0aGlzIGlzIG5vdCBhIE1BLTEwMTcg KGJEZXZpY2VDbGFzcyA9IDI1NSwgYkludGVyZmFjZUNsYXNzID0gMjU1KVwKICAgIGNoZWNr aW5nIGZvciBNQS0xMDE1IC4uLlwKICAgIHRoaXMgaXMgbm90IGEgTUEtMTAxNSAoYkRldmlj ZVN1YkNsYXNzID0gMHgwKVwKICAgIGNoZWNraW5nIGZvciBNQS0xNTA5IC4uLlwKICAgIHRo aXMgaXMgbm90IGEgTUEtMTUwOSAoYmNkVVNCID0gMHgxMDApXAogICAgY2hlY2tpbmcgZm9y IExNOTgzWzEsMiwzXSAuLi5cCiAgICB0aGlzIGlzIG5vdCBhIExNOTgzeCAoYkVuZHBvaW50 QWRkcmVzcyA9IDB4MSwgYm1BdHRyaWJ1dGVzID0gMHgyLCB3TWF4UGFja2V0U2l6ZSA9IDB4 OCwgYkludGVydmFsID0gMHgwKVwKICAgIGNoZWNraW5nIGZvciBHTDY0NiAuLi5cCiAgICB0 aGlzIGlzIG5vdCBhIEdMNjQ2IChiRGV2aWNlQ2xhc3MgPSAyNTUsIGJJbnRlcmZhY2VDbGFz cyA9IDI1NSlcCiAgICBjaGVja2luZyBmb3IgR0w2NDZfSFAgLi4uXAogICAgdGhpcyBpcyBu b3QgYSBHTDY0Nl9IUCAoYmNkVVNCID0gMHgxMDApXAogICAgY2hlY2tpbmcgZm9yIEdMNjYw K0dMNjQ2IC4uLlwKICAgIHRoaXMgaXMgbm90IGEgR0w2NjArR0w2NDYgKGJEZXZpY2VDbGFz cyA9IDI1NSwgYkludGVyZmFjZUNsYXNzID0gMjU1KVwKICAgIGNoZWNraW5nIGZvciBHTDg0 MSAuLi5cCiAgICB0aGlzIGlzIG5vdCBhIEdMODQxIChiY2RVU0IgPSAweDEwMClcCiAgICBj aGVja2luZyBmb3IgSUNNNTMyQiAuLi5cCiAgY2hlY2sgMiwgdGhpcyBpcyBub3QgYSBJQ001 MzJCIChiY2RVU0IgPSAweDEwMClcCjxDb3VsZG4ndCBkZXRlcm1pbmUgdGhlIHR5cGUgb2Yg dGhlIFVTQiBjaGlwPlwKXApmb3VuZCBVU0Igc2Nhbm5lciAodmVuZG9yPTB4MDQ3NSwgcHJv ZHVjdD0weDAxMDApIGF0IGxpYnVzYjowMDM6MDAyLTA0NzUtMDEwMC1mZi0wMFwKXAo8ZGV2 aWNlIGRlc2NyaXB0b3Igb2YgMHgwNWFjLzB4ODAwNiBhdCAwMDQ6MDAxLTA1YWMtODAwNi0w OS0wMCAoQXBwbGUgQ29tcHV0ZXIsIEluYy4gRUhDSSBSb290IEh1YiBTaW11bGF0aW9uKT5c CmJMZW5ndGggICAgICAgICAgICAgICAxOFwKYkRlc2NyaXB0b3JUeXBlICAgICAgIDFcCmJj ZFVTQiAgICAgICAgICAgICAgICAyLjAwXApiRGV2aWNlQ2xhc3MgICAgICAgICAgOVwKYkRl dmljZVN1YkNsYXNzICAgICAgIDBcCmJEZXZpY2VQcm90b2NvbCAgICAgICAxXApiTWF4UGFj a2V0U2l6ZTAgICAgICAgNjRcCmlkVmVuZG9yICAgICAgICAgICAgICAweDA1QUNcCmlkUHJv ZHVjdCAgICAgICAgICAgICAweDgwMDZcCmJjZERldmljZSAgICAgICAgICAgICAyLjAwXApp TWFudWZhY3R1cmVyICAgICAgICAgMiAoQXBwbGUgQ29tcHV0ZXIsIEluYy4pXAppUHJvZHVj dCAgICAgICAgICAgICAgMSAoRUhDSSBSb290IEh1YiBTaW11bGF0aW9uKVwKaVNlcmlhbE51 bWJlciAgICAgICAgIDAgKClcCmJOdW1Db25maWd1cmF0aW9ucyAgICAxXAogPGNvbmZpZ3Vy YXRpb24gMD5cCiBiTGVuZ3RoICAgICAgICAgICAgICAxMFwKIGJEZXNjcmlwdG9yVHlwZSAg ICAgIDJcCiB3VG90YWxMZW5ndGggICAgICAgICAyN1wKIGJOdW1JbnRlcmZhY2VzICAgICAg IDFcCiBiQ29uZmlndXJhdGlvblZhbHVlICAxXAogaUNvbmZpZ3VyYXRpb24gICAgICAgMCAo KVwKIGJtQXR0cmlidXRlcyAgICAgICAgIDk2IChTZWxmLXBvd2VyZWRSZW1vdGUgV2FrZXVw KVwKIE1heFBvd2VyICAgICAgICAgICAgIDAgbUFcCiAgPGludGVyZmFjZSAwPlwKICAgPGFs dHNldHRpbmcgMD5cCiAgIGJMZW5ndGggICAgICAgICAgICA5XAogICBiRGVzY3JpcHRvclR5 cGUgICAgNFwKICAgYkludGVyZmFjZU51bWJlciAgIDBcCiAgIGJBbHRlcm5hdGVTZXR0aW5n ICAwXAogICBiTnVtRW5kcG9pbnRzICAgICAgMVwKICAgYkludGVyZmFjZUNsYXNzICAgIDlc CiAgIGJJbnRlcmZhY2VTdWJDbGFzcyAwXAogICBiSW50ZXJmYWNlUHJvdG9jb2wgMVwKICAg aUludGVyZmFjZSAgICAgICAgIDAgKClcCiAgICA8ZW5kcG9pbnQgMD5cCiAgICBiTGVuZ3Ro ICAgICAgICAgICA4XAogICAgYkRlc2NyaXB0b3JUeXBlICAgNVwKICAgIGJFbmRwb2ludEFk ZHJlc3MgIDB4ODEgKGluIDB4MDEpXAogICAgYm1BdHRyaWJ1dGVzICAgICAgMyAoaW50ZXJy dXB0KVwKICAgIHdNYXhQYWNrZXRTaXplICAgIDhcCiAgICBiSW50ZXJ2YWwgICAgICAgICAy NTUgbXNcCiAgICBiUmVmcmVzaCAgICAgICAgICAwXAogICAgYlN5bmNoQWRkcmVzcyAgICAg MFwKICAjIFlvdXIgVVNCIHNjYW5uZXIgd2FzIChwcm9iYWJseSkgZGV0ZWN0ZWQuIEl0IG1h eSBvciBtYXkgbm90IGJlIHN1cHBvcnRlZCBieVwKICAjIFNBTkUuIFRyeSBzY2FuaW1hZ2Ug LUwgYW5kIHJlYWQgdGhlIGJhY2tlbmQncyBtYW5wYWdlLlwKXAogICMgTm90IGNoZWNraW5n IGZvciBwYXJhbGxlbCBwb3J0IHNjYW5uZXJzLlwKXAogICMgTW9zdCBTY2FubmVycyBjb25u ZWN0ZWQgdG8gdGhlIHBhcmFsbGVsIHBvcnQgb3Igb3RoZXIgcHJvcHJpZXRhcnkgcG9ydHNc CiAgIyBjYW4ndCBiZSBkZXRlY3RlZCBieSB0aGlzIHByb2dyYW0uXApcCiAgIyBZb3UgbWF5 IHdhbnQgdG8gcnVuIHRoaXMgcHJvZ3JhbSBhcyByb290IHRvIGZpbmQgYWxsIGRldmljZXMu IE9uY2UgeW91XAogICMgZm91bmQgdGhlIHNjYW5uZXIgZGV2aWNlcywgYmUgc3VyZSB0byBh ZGp1c3QgYWNjZXNzIHBlcm1pc3Npb25zIGFzXAogICMgbmVjZXNzYXJ5LlwKZG9uZVwKW0xv bGl0YTp+XSBhbWthcGxhbiUgfQ== --------------050503010401050303030202-- --------------ms090808030104000206020707 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGbDCC AzIwggKboAMCAQICAgJ2MA0GCSqGSIb3DQEBBAUAME8xDTALBgNVBAoTBEdyaWQxEjAQBgNV BAoTCU5vcmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVHcmlkIENlcnRpZmljYXRpb24gQXV0aG9y aXR5MB4XDTA0MDUwNDE0MjY0MVoXDTA1MDUwNDE0MjY0MVowUDENMAsGA1UEChMER3JpZDES MBAGA1UEChMJTm9yZHVHcmlkMRIwEAYDVQQLEwl0c2wudXUuc2UxFzAVBgNVBAMTDk1hdHRp YXMgRWxsZXJ0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDV8f0oE9EY8Zc7W18Puyjc ZAZUPXqwDqMJigz+FKIy2Tqy3Xcv8hAXk/VM+wU+RZMpfwwRihb0TFYAvqsuHn6rV6Z4xUhn B5uUjlNp4vBomtPcXOwVBSpflFyMVdkUCTQls+rIoHo/jO07W1NZMRXxBTWoSC/YXfbV9MsP +6MsFwIDAQABo4IBGjCCARYwCQYDVR0TBAIwADARBglghkgBhvhCAQEEBAMCBaAwCwYDVR0P BAQDAgXgMCwGCWCGSAGG+EIBDQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBDZXJ0aWZpY2F0ZTAd BgNVHQ4EFgQUHC2rjql+Xupjzclc4OC8+kH0iQUwdwYDVR0jBHAwboAUGAXA/AvRtzr0ZZIJ +1mhX8eIxPChU6RRME8xDTALBgNVBAoTBEdyaWQxEjAQBgNVBAoTCU5vcmR1R3JpZDEqMCgG A1UEAxMhTm9yZHVHcmlkIENlcnRpZmljYXRpb24gQXV0aG9yaXR5ggEAMCMGA1UdEQQcMBqB GG1hdHRpYXMuZWxsZXJ0QHRzbC51dS5zZTANBgkqhkiG9w0BAQQFAAOBgQBJVHRvfXvI5bjp 2wX92F0MONzIxczNls3F1HBg/GSQ5zq89mGidKVNbbv61r0TztpWOew1r2DfuexFsdLG1mgH RPtLzWaYnEpAPcJx4DECHqm2cmp+NOP2eWv8hI3uL/279Lxm0B6wIU7V5v/I83kUVZ/JJrNs 5wvrsTRYaKyuVDCCAzIwggKboAMCAQICAgJ2MA0GCSqGSIb3DQEBBAUAME8xDTALBgNVBAoT BEdyaWQxEjAQBgNVBAoTCU5vcmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVHcmlkIENlcnRpZmlj YXRpb24gQXV0aG9yaXR5MB4XDTA0MDUwNDE0MjY0MVoXDTA1MDUwNDE0MjY0MVowUDENMAsG A1UEChMER3JpZDESMBAGA1UEChMJTm9yZHVHcmlkMRIwEAYDVQQLEwl0c2wudXUuc2UxFzAV BgNVBAMTDk1hdHRpYXMgRWxsZXJ0MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDV8f0o E9EY8Zc7W18PuyjcZAZUPXqwDqMJigz+FKIy2Tqy3Xcv8hAXk/VM+wU+RZMpfwwRihb0TFYA vqsuHn6rV6Z4xUhnB5uUjlNp4vBomtPcXOwVBSpflFyMVdkUCTQls+rIoHo/jO07W1NZMRXx BTWoSC/YXfbV9MsP+6MsFwIDAQABo4IBGjCCARYwCQYDVR0TBAIwADARBglghkgBhvhCAQEE BAMCBaAwCwYDVR0PBAQDAgXgMCwGCWCGSAGG+EIBDQQfFh1PcGVuU1NMIEdlbmVyYXRlZCBD ZXJ0aWZpY2F0ZTAdBgNVHQ4EFgQUHC2rjql+Xupjzclc4OC8+kH0iQUwdwYDVR0jBHAwboAU GAXA/AvRtzr0ZZIJ+1mhX8eIxPChU6RRME8xDTALBgNVBAoTBEdyaWQxEjAQBgNVBAoTCU5v cmR1R3JpZDEqMCgGA1UEAxMhTm9yZHVHcmlkIENlcnRpZmljYXRpb24gQXV0aG9yaXR5ggEA MCMGA1UdEQQcMBqBGG1hdHRpYXMuZWxsZXJ0QHRzbC51dS5zZTANBgkqhkiG9w0BAQQFAAOB gQBJVHRvfXvI5bjp2wX92F0MONzIxczNls3F1HBg/GSQ5zq89mGidKVNbbv61r0TztpWOew1 r2DfuexFsdLG1mgHRPtLzWaYnEpAPcJx4DECHqm2cmp+NOP2eWv8hI3uL/279Lxm0B6wIU7V 5v/I83kUVZ/JJrNs5wvrsTRYaKyuVDGCAn4wggJ6AgEBMFUwTzENMAsGA1UEChMER3JpZDES MBAGA1UEChMJTm9yZHVHcmlkMSowKAYDVQQDEyFOb3JkdUdyaWQgQ2VydGlmaWNhdGlvbiBB dXRob3JpdHkCAgJ2MAkGBSsOAwIaBQCgggF/MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEw HAYJKoZIhvcNAQkFMQ8XDTA0MDYxMTAxMTczNFowIwYJKoZIhvcNAQkEMRYEFKy5bAwfP3G1 28NbwvmU2khSnR6pMFIGCSqGSIb3DQEJDzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwIC AgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMGQGCSsGAQQBgjcQ BDFXMFUwTzENMAsGA1UEChMER3JpZDESMBAGA1UEChMJTm9yZHVHcmlkMSowKAYDVQQDEyFO b3JkdUdyaWQgQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkCAgJ2MGYGCyqGSIb3DQEJEAILMVeg VTBPMQ0wCwYDVQQKEwRHcmlkMRIwEAYDVQQKEwlOb3JkdUdyaWQxKjAoBgNVBAMTIU5vcmR1 R3JpZCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eQICAnYwDQYJKoZIhvcNAQEBBQAEgYBVsopQ pjvYdCrMBT/qkuZOBggxIqucUbCDXIvh1xd+eedDxGqeNMD7YswOZ2OfKOpwuuThKcL9rbgx apox1tS+pTEZjNqc6k1q3pLS+ZbJBv/n9qHnPrwn81DKizXvaSgtjpYX1wQujLQp3VwPRGNz 75c5f0Oka+Qd6Vyls1YU3QAAAAAAAA== --------------ms090808030104000206020707-- From olaf@epkowa.co.jp Fri Jun 11 05:50:39 2004 From: olaf@epkowa.co.jp (Olaf Meeuwissen) Date: Fri, 11 Jun 2004 13:50:39 +0900 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <87r7snudz2.fsf@zen.epkowa.co.jp> (Olaf Meeuwissen's message of "Fri, 11 Jun 2004 09:37:21 +0900") References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> <20040610170847.5c305388@expensive> <87r7snudz2.fsf@zen.epkowa.co.jp> Message-ID: <87zn7au28w.fsf@zen.epkowa.co.jp> Olaf Meeuwissen writes: > Tom Schutzer-Weissmann writes: > >> On Thu, 10 Jun 2004 05:36:52 -0400 >> Karl Heinz Kremer wrote: >> >>> I'm also reading sane-devel, so no need to take a detour with >>> any Epson backend related information :-) >>> I've never experienced any of the problem you describe, and I've >>> been running a 2.6.x kernel for some time now (SuSE 9.1 beta versions >>> and the final SuSE 9.1). >>> >>> I've tried this with two different USB controllers (USB-1.1 and high >>> speed USB-2) with a number of different Epson scanners. >>> >>> Karl Heinz >> >> Thank you for all your responses. >> >> I'm using Debian unstable, kernel 2.6.6 with ohci_usb, libusb-0-1.4 >> (0.1.8-11). The scanner is an Epson Perfection 2450. > > That's what you get for running bleeding edge ;-) > > I'm using Debian testing, kernel 2.6.6 with uhci_hcd (and ehci_hcd), > libusb-0.1-4 (0.1.8-11) and will see if I can lay my hands on a > Perfection 2450. > > The USB modules are autoprobed, I don't have anything USB related in > my /etc/modules-2.6. There is an usb-uhci in my /etc/modules but IIRC > that file is not used if /etc/modules-2.6 exists. > >> It seems libusb isn't working as it should - maybe future Debian >> updates will solve the problem; in the meantime I am happy with my >> hack, but if anyone would like me to try out some suggestions to get >> to the bottom of this mystery, I'd be happy to help off-list. > > As I'm using the same libusb as you do, I am sceptical about libusb > being the culprit. Apart from the usb module and scanner model, we > use the same setup. I'll get back with the results on the Perfection > 2450 ASAP. Problem confirmed for the GT-9700 (aka Perfection 2450) with both the epson and epkowa backends. Note that these same backends work fine with the GT-8200 (aka Perfection 1650) under identical conditions. Just starting a SANE frontend (tried with xsane and iscan) with the GT-9700 already takes "ages" and it just refuses to preview. BTW, the epson backend is from sane-backend-1.0.14 and the epkowa one from iscan-1.8.1. # The upcoming iscan-1.9.0 (due 2004-06-18), which adds support for # the ES-10000G (aka Expression 10000) and adds saving in JPEG format, # suffers from the same problem. Looks like Karl and/or I have some digging to do ;-( -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From misc@tomweissmann.org Fri Jun 11 14:21:16 2004 From: misc@tomweissmann.org (Tom Schutzer-Weissmann) Date: Fri, 11 Jun 2004 14:21:16 +0100 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <87zn7au28w.fsf@zen.epkowa.co.jp> References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> <20040610170847.5c305388@expensive> <87r7snudz2.fsf@zen.epkowa.co.jp> <87zn7au28w.fsf@zen.epkowa.co.jp> Message-ID: <20040611142116.7740e5d1@expensive> On Fri, 11 Jun 2004 13:50:39 +0900 Olaf Meeuwissen wrote: [...] > Problem confirmed for the GT-9700 (aka Perfection 2450) with both the > epson and epkowa backends. Note that these same backends work fine > with the GT-8200 (aka Perfection 1650) under identical conditions. > > Just starting a SANE frontend (tried with xsane and iscan) with the > GT-9700 already takes "ages" and it just refuses to preview. Aha. That's not at all what I expected - many apologies to any slighted libusb developer! Like I said, you can get it to work by calling usb_reset() whenever the scanner device is closed. My hacked code for sanei_usb_close() (in sanei/sanei_usb.c) is below. I hope you don't need it :) > Looks like Karl and/or I have some digging to do ;-( Maybe. It would be very interesting to know what's wrong. Is it perhaps that the scanner needs to be send a message before it is closed. Many thanks, Tom ----------------------------------------------------------- ----------------------------------------------------------- void sanei_usb_close (SANE_Int dn) { DBG (5, "sanei_usb_close: closing device %d\n", dn); if (dn >= MAX_DEVICES || dn < 0) { DBG (1, "sanei_usb_close: dn >= MAX_DEVICES || dn < 0\n"); return; } if (!devices[dn].open) { DBG (1, "sanei_usb_close: device %d already closed or never opened\n", dn); return; } if (devices[dn].method == sanei_usb_method_scanner_driver) close (devices[dn].fd); else #ifdef HAVE_LIBUSB { #if 0 /* Should only be done in case of a stall */ usb_clear_halt (devices[dn].libusb_handle, devices[dn].bulk_in_ep); usb_clear_halt (devices[dn].libusb_handle, devices[dn].bulk_out_ep); /* be careful, we don't know if we are in DATA0 stage now */ usb_resetep(devices[dn].libusb_handle, devices[dn].bulk_in_ep); usb_resetep(devices[dn].libusb_handle, devices[dn].bulk_out_ep); #endif /* HACK FOR PERFECTION 2450 */ usb_reset(devices[dn].libusb_handle) ; usb_release_interface (devices[dn].libusb_handle, devices[dn].interface_nr); usb_close (devices[dn].libusb_handle); } #else DBG (1, "sanei_usb_close: libusb support missing\n"); #endif devices[dn].open = SANE_FALSE; return; } ------------------------------------------------------------------ ------------------------------------------------------------------ From l.riso@tiscalinet.it Fri Jun 11 06:20:53 2004 From: l.riso@tiscalinet.it (Luca) Date: Fri, 11 Jun 2004 07:20:53 +0200 Subject: [sane-devel] Sonix SN9C101 and SN9C102 USB camera controllers - specifications Message-ID: <20040611072053.6e714b6a.l.riso@tiscalinet.it> I have been told by the TWAIN people that this is the best place where to ask for the detailed specifications of the above chips. Any help would be much appreciated. Sonix does not respond to my emails and google does not help (there's a 12-page long datasheets, but it is not detailed enough to write a driver) Thanks, please answer to l.riso@tiscalinet.it From Benjamin Lawetz Fri Jun 11 15:00:36 2004 From: Benjamin Lawetz (Benjamin Lawetz) Date: Fri, 11 Jun 2004 10:00:36 -0400 (EDT) Subject: [sane-devel] finally got UDS-IS11 working (Error in FAQ) Message-ID: Hi, I finally got the el cheapo SCSI card that came with my UMAX scanner to work. I was surprised to find instructions in your FAQ to get the card working (last time I had checked, everyone told me it was a lost cause) I tried without success, trying to insert it as a module (I think like the FAQ said, but I'm not sure) it worked, but no way to get in working in a monolithic kernel. After a checking the source, it seemed the driver wanted it's kernel options from dtc3181e, the FAQ mentionned dtc_3181e Once the little underscore removed, it worked like a charm. (I don't know if it changed for kernel 2.6, but maybe update the FAQ to help others down the line). Thanks for all your great work guys ! -- \\\|/// \\ - - // ( @ @ ) ---oOOo-(_)-oOOo------------------------------- If you suspect a man, don't employ him. --------------Oooo----------------------------- oooO ( ) Benjamin Benthos Lawetz ( ) ) / mailto:Benjamin.Lawetz@lqjr.qc.ca \ ( (_/ ICQ# 4269530 \_) From epl@unimelb.edu.au Fri Jun 11 15:30:46 2004 From: epl@unimelb.edu.au (epl@unimelb.edu.au) Date: Sat, 12 Jun 2004 00:30:46 +1000 (EST) Subject: [sane-devel] epson 2400 neg scans Message-ID: > The Perfection 1670 and the 2400 look interesting. It appears that the > former is not supported by sane and runs on a different chip set to > other Perfection scanners so I'll stike that from the list. > Peter, I've got an Epson Perfection 1670 Photo and I'd be glad to answer any questions you (or anyone else on this mailing list) have. Please Cc me as I haven't subscribed to this list. Pros: - Works under both Linux's scanner kernel module and libusb. - I've gotten it to work under both Debian unstable (very easy, glorious apt-get) and Red Hat 9.0 (heavily mangled with alien-converted debs). - I was also able to get the Epson firmware file using unshield (CVS version from the synce project). Else, you can get it from: http://www.commercialventvac.com/~jeffs/epson1670andFedora.html - Flatbed scanning (ie not transparency) works even up to the maximum resolution of 1600dpi. Jeff's result (above) maybe caused by the older sane-backend-1.0.13 -- shrugs. - The transparency scanning works to the extent that the fluorescence light can be controlled from sane. Cons: - A bit expensive IMHO. - The four scanner buttons doesn't have any effect. - Film scanning seems to introduce fine lines (only noticeable at high resolutions) that isn't due to the negative. - Not sure which component is at fault, but the colour of the film/negatives aren't properly calibrated. As far as I'm concerned, film scanning of the 1670 isn't usable under sane. Of course, it is distinctly possible that I haven't got things setup correctly as I've never played with film (35mm Kodak) scanning before. It is also possible that the CVS version of sane-backend fixes some of the above problems (currently using 1.0.14). BTW, thank you to the developers who integrated 1670 support into sane. Cheers Eddie From gerard@gkall.hobby.nl Sat Jun 12 02:31:59 2004 From: gerard@gkall.hobby.nl (gerard klaver) Date: Sat, 12 Jun 2004 01:31:59 +0000 Subject: [sane-devel] Sonix SN9C101 and SN9C102 USB camera controllers - specifications In-Reply-To: <20040611072053.6e714b6a.l.riso@tiscalinet.it> References: <20040611072053.6e714b6a.l.riso@tiscalinet.it> Message-ID: <1087003919.1488.4.camel@gk-lex3> On Fri, 2004-06-11 at 05:20, Luca wrote: > I have been told by the TWAIN people that this is the best place > where to ask for the detailed specifications of the above chips. > Any help would be much appreciated. Sonix does not respond to my emails > and google does not help (there's a 12-page long datasheets, but it is > not detailed enough to write a driver) > > Thanks, please answer to l.riso@tiscalinet.it Depends what sort of driver you want to write, kernel module or SANE backend. See also these links: http://www.mnementh.co.uk/sonix/ and http://sonix.sourceforge.net/ -- ---------- m.vr.gr. Gerard Klaver From david@2gen.com Sat Jun 12 12:03:29 2004 From: david@2gen.com (David =?iso-8859-1?Q?H=E4rdeman?=) Date: Sat, 12 Jun 2004 13:03:29 +0200 Subject: [sane-devel] Re: [Linux-usb-users] Problems with HP 6200C scanner and SANE In-Reply-To: References: <40BB5315.5000508@2gen.com> Message-ID: <20040612110326.GC652@hardeman.nu> On Mon, May 31, 2004 at 02:58:12PM -0400, Alan Stern wrote: >On Mon, 31 May 2004, David Härdeman wrote: >> I'm currently trying to get an HP 6200C USB scanner to work with SANE >> (1.0.14) under Linux (Debian woody with some backports, kernel 2.4.26). >> Whenever I scan something which requires a low amount of data (lineart >> picture at 100dpi for instance), everything works just fine. But when I >> scan a more bandwidth hungry pic, it never succeeds. I've tried this >> both with the "scanner" module in the kernel and with libusb but both >> seem to experience the same problems. >> >> I have tried sane's "dumb-read" option and all other option which were >> mentioned in the sane-hp man page but I'm running out of ideas. Any >> clues what might cause this (might later kernels be too picky with their >> timing requirements)? > >The most likely explanation is that some other program (possibly a hotplug >utility) is trying to access the scanner while you're using it, thereby >confusing the scanner and causing it to fail. I've seen reports from >other people where the "usbmodules" program did this. See what happens if >you turn off all hotplug support. Hi, and sorry for the delay in answering. I am running this on Debian Woody (with backported usblib and sane packages of recent versions), so there is no hotplug support on the system, the only other thing I could think of is the "nut" UPS daemon which checks the status of the UPS over USB. However, disabling nut and trying to scan did not help sort out the problem. Any other suggestions? Re, David From klemens.dickbauer@msk-informatik.at Sun Jun 13 00:27:28 2004 From: klemens.dickbauer@msk-informatik.at (Klemens Dickbauer) Date: Sun, 13 Jun 2004 01:27:28 +0200 Subject: [sane-devel] JSane In-Reply-To: References: Message-ID: <200406130127.28342.klemens.dickbauer@msk-informatik.at> Hi David, Hi Andi and Chris! After being off for quite a long time (sorry for not communicating!) I restarted my work on japi_sane again this week. The classes I have are based on the work of Silvio Vogt and what I did is mainly some refactoring work (moving into the org.saneproject package structure, moving into a interface/implementation classes desgin, changes on the gui part...). It's still ongoing, but at least I can compile it again. I just read all the messages on this list an realized that a few people are working on the same issue. Your approch, Andi, seems very promising to me using the TCP level to communicate, coding JNI is very hard for me unexperienced bloke. (-; Anyway, having a direct Java interface to the sane libs seems also desireable to me. David, what do you think about the changes I suggest? I had no close look into your classes so far, but I'll do tomorrow. Are you planning something more on these? I will include my few classes, though thei're not running yet. I get a segfault on every call, as I said before I am very unexperienced in system programming. Maybe someone can give me a hint on where to start. -- An unexpected exception has been detected in native code outside the VM. Unexpected Signal : 11 occurred at PC=0x4DE37B06 Function=sane_dll_control_option+0x56 Library=/usr/lib/libsane.so.1 Current Java thread: at org.saneproject.scan.sane.Sane.getControlOption(Native Method) [..] -- bye for now, ~klemens Am Mittwoch, 9. Juni 2004 13:54 schrieb David Neary: > Hi all, > > I know that some people were asking about a Java SANE API > recently. > > I did some work before 1.0.14 on getting it at least > compiling with at least a Sun SDK, and have since been > quite happily using these JNI bindings. There are still > some bugs in here, notably for lineart mode, and I have > been unashamedly messing about with stuff to make it work > just for me, for one particular task, so it's probably > not pretty. > > But perhaps people who need something now will be happy > with it. > > This is simply a tar of the japi directory after I did > a make clean. I also have a dllmain.c and a project file > for making a sanej.dll for Windows, if anyone would like > those. This is more or less untested, and ymmv. > > I also have a tarball of the javadocs, but I didn't do > anything particular to generate them except run javadoc > so there's no real point in sending those to the list. > > Cheers, > Dave. > > -- > David Neary > Phenix Engineering > 110 ave Jean Jaures, 69007 Lyon -- Klemens Dickbauer, MSK Informatik GesmbH A-1160 Wien, Zeillergasse 5/309 From vykk3@comcast.net Sun Jun 13 01:24:52 2004 From: vykk3@comcast.net (Victoria Welch) Date: Sat, 12 Jun 2004 17:24:52 -0700 Subject: [sane-devel] Help :-)! 2.6.5 kernel/ Agfa SnapScan 1212u USB - I'm lost :-(. Message-ID: <200406121724.52915.vykk3@comcast.net> Hi All and Thanks in advance! I've been trying to resolve this for the past two days and am turning to this list out of desperation, I'm completely baffled :-(. The scanner is fully supported according to the lists of suppored devices on the sane site. I'm not sure if the following is all the info needed, but as noted I am thoroughly confused at this point. The scanner is seen is /proc/bus/usb/devices: T: Bus=03 Lev=01 Prnt=01 Port=01 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=06bd ProdID=2061 Rev= 1.1e S: Manufacturer=AGFA S: Product= Snapscan1212u_2 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA 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= 8 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=16ms The docs make reference to a needed kernel driver, but if one exists in the kernel config I do not recognize it (per above: I: [ ... ] Driver=(none). I have emerged the sane back ends and xsane. I thought perhaps I needed the following in /etc/sane.d/snapscan.conf file: #------------------------------ General ----------------------------------- # Change to the fully qualified filename of your firmware file, if # firmware upload is needed by the scanner firmware /usr/lib/sane/SnapScan_1212U_2.bin [ ... ] I'm still not sure if it is necessary or not. Whatever is going on here, nothing in /dev gets created in any form I would recognize as to having to do with a scanner. All other USB devices are working fine (Joystick, usb filesystem camera and A Palm Pilot USB cradle) and the appropriate /dev entries exist. I've read until my eyes ache :-) and googled on everything I could think of that would help me resolve this issue. I'm embarrased to admit that I came up with nothing that seems to have been helpful, I have to have missed something there somewhere, maybe multiple times :-(. The only "progress" I get is that sane seems to pickup my tv tuner card which xsane won't work with anyhow and it is rather useless for scanning stuff this way :-). Any help, suggestions or pointers *greatly* appreciated. Thanks & take care, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From kpschrage@gmx.de Sun Jun 13 10:59:38 2004 From: kpschrage@gmx.de (Klaus-Peter Schrage) Date: Sun, 13 Jun 2004 11:59:38 +0200 Subject: [sane-devel] Help :-)! 2.6.5 kernel/ Agfa SnapScan 1212u USB - I'm lost :-(. In-Reply-To: <200406121724.52915.vykk3@comcast.net> References: <200406121724.52915.vykk3@comcast.net> Message-ID: <40CC258A.7020406@gmx.de> Victoria Welch wrote: > The docs make reference to a needed kernel driver, but if > one exists in the kernel config I do not recognize it (per > above: I: [ ... ] Driver=(none). > > I have emerged the sane back ends and xsane. I thought > perhaps I needed the following in /etc/sane.d/snapscan.conf > file: > > #------------------------------ General > ----------------------------------- > > # Change to the fully qualified filename of your firmware > file, if > # firmware upload is needed by the scanner > firmware /usr/lib/sane/SnapScan_1212U_2.bin > [ ... ] > > I'm still not sure if it is necessary or not. > > Whatever is going on here, nothing in /dev gets created in > any form I would recognize as to having to do with a > scanner. I have been using this very AGFA scanner for years in Linux, and it is really well supported. But with the 2.6 kernel series, the rationale has changed: no more kernel modules or /dev's, bus the scanner is addressed via libusb. So what does sane-find-scanner given in a console, reply? If you read something like: found USB scanner (vendor=0x06bd [AGFA], product=0x2061 [ Snapscan1212u_2]) at libusb:002:002 then your scanner is recognized and may be adressed by xsane or so via libusb. If not, then you probably don't have sane-frontends and/or libusb, so get it. The next step should be scanimage -L If you DON'T read device `snapscan:libusb:002:002' is a AGFA SNAPSCAN 1212U_2 flatbed scanner try the same as root. If there's success at last, then there is a permissions issue that allows only root to access the scanner. Getting it to work for normal users is another story ... As to the 'firmware' line in snapscan.conf: It's ok and should be there (if the .bin file really is in the indicated location) Klaus From jb@jblache.org Sun Jun 13 12:47:59 2004 From: jb@jblache.org (Julien BLACHE) Date: Sun, 13 Jun 2004 13:47:59 +0200 Subject: [sane-devel] Epson backend fix wrt USB IDs for Perfection 1250 and 1260 Message-ID: <87wu2bn0gg.fsf@frigate.technologeek.org> Hi, It seems the fix that went in regarding the USB IDs for Perfection 1250 and 1260 erroneously removed the USB IDs for the Perfection 1650 instead of removing the USB IDs for the Perfection 1250. khk ? (noticed by S=E9bastien Villemot) JB. --=20 Julien BLACHE =20 GPG KeyID 0xF5D65169 From khk@khk.net Sun Jun 13 13:42:00 2004 From: khk@khk.net (Karl Heinz Kremer) Date: Sun, 13 Jun 2004 08:42:00 -0400 Subject: [sane-devel] Epson backend fix wrt USB IDs for Perfection 1250 and 1260 In-Reply-To: <87wu2bn0gg.fsf@frigate.technologeek.org> References: <87wu2bn0gg.fsf@frigate.technologeek.org> Message-ID: <10998AE0-BD37-11D8-80D6-000A957E40E8@khk.net> Thanks. Looks like I picked the wrong line. I added the 1650 back in and finally removed the 1250. On Jun 13, 2004, at 7:47 AM, Julien BLACHE wrote: > Hi, > > It seems the fix that went in regarding the USB IDs for Perfection > 1250 and 1260 erroneously removed the USB IDs for the Perfection 1650 > instead of removing the USB IDs for the Perfection 1250. > > khk ? > > (noticed by S=E9bastien Villemot) > > JB. > > --=20 > Julien BLACHE =20 > > GPG KeyID 0xF5D65169 > > --=20 > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request@lists.alioth.debian.org From andi.mclean@ntlworld.com Sun Jun 13 15:25:56 2004 From: andi.mclean@ntlworld.com (Andi McLean) Date: Sun, 13 Jun 2004 15:25:56 +0100 Subject: [sane-devel] JSane In-Reply-To: <200406130127.28342.klemens.dickbauer@msk-informatik.at> References: <200406130127.28342.klemens.dickbauer@msk-informatik.at> Message-ID: <200406131525.56730.andi.mclean@ntlworld.com> Hi , On Sunday 13 June 2004 00:27, Klemens Dickbauer wrote: > Hi David, Hi Andi and Chris! > > After being off for quite a long time (sorry for not communicating!) I > restarted my work on japi_sane again this week. > The classes I have are based on the work of Silvio Vogt and what I did is > mainly some refactoring work (moving into the org.saneproject package > structure, moving into a interface/implementation classes desgin, changes > on the gui part...). It's still ongoing, but at least I can compile it > again. > I have designed a structure to split interface and implementation how does everyone feel about these? Dave what do you think about putting the JNI part in with my code? Does it fit with the design I've created? If not we can discuss what changes are needed. I designed the structure to mainly meet my needs but tried to make it so that a JNI, or other implementation could be used. As I needed to get it working for my main project. > I just read all the messages on this list an realized that a few people are > working on the same issue. Your approch, Andi, seems very promising to me > using the TCP level to communicate, coding JNI is very hard for me > unexperienced bloke. (-; I found the JNI difficult too, and needed to be able to port the client stuff to different hardware at a moments notice, so I went with a pure java implementation. As I said, I've tried to create the framework so it can accomodate other implementations. > Anyway, having a direct Java interface to the sane libs seems also > desireable to me. David, what do you think about the changes I suggest? I > had no close look into your classes so far, but I'll do tomorrow. Are you > planning something more on these? > > I will include my few classes, though thei're not running yet. I get a > segfault on every call, as I said before I am very unexperienced in system > programming. Maybe someone can give me a hint on where to start. > -- > An unexpected exception has been detected in native code outside the VM. > Unexpected Signal : 11 occurred at PC=0x4DE37B06 > Function=sane_dll_control_option+0x56 > Library=/usr/lib/libsane.so.1 > > Current Java thread: > at org.saneproject.scan.sane.Sane.getControlOption(Native Method) > [..] > -- > > bye for now, > ~klemens > > Am Mittwoch, 9. Juni 2004 13:54 schrieb David Neary: > > Hi all, > > > > I know that some people were asking about a Java SANE API > > recently. > > > > I did some work before 1.0.14 on getting it at least > > compiling with at least a Sun SDK, and have since been > > quite happily using these JNI bindings. There are still > > some bugs in here, notably for lineart mode, and I have > > been unashamedly messing about with stuff to make it work > > just for me, for one particular task, so it's probably > > not pretty. > > > > But perhaps people who need something now will be happy > > with it. > > > > This is simply a tar of the japi directory after I did > > a make clean. I also have a dllmain.c and a project file > > for making a sanej.dll for Windows, if anyone would like > > those. This is more or less untested, and ymmv. > > > > I also have a tarball of the javadocs, but I didn't do > > anything particular to generate them except run javadoc > > so there's no real point in sending those to the list. > > > > Cheers, > > Dave. > > > > -- > > David Neary > > Phenix Engineering > > 110 ave Jean Jaures, 69007 Lyon > > -- > Klemens Dickbauer, MSK Informatik GesmbH > A-1160 Wien, Zeillergasse 5/309 From l.riso@tiscalinet.it Sat Jun 12 03:39:40 2004 From: l.riso@tiscalinet.it (Luca) Date: Sat, 12 Jun 2004 04:39:40 +0200 Subject: [sane-devel] Sonix SN9C101 and SN9C102 USB camera controllers - specifications In-Reply-To: <1087003919.1488.4.camel@gk-lex3> References: <20040611072053.6e714b6a.l.riso@tiscalinet.it> <1087003919.1488.4.camel@gk-lex3> Message-ID: <20040612043940.2f154bbb.l.riso@tiscalinet.it> On Sat, 12 Jun 2004 01:31:59 +0000 gerard klaver wrote: > On Fri, 2004-06-11 at 05:20, Luca wrote: > > I have been told by the TWAIN people that this is the best place > > where to ask for the detailed specifications of the above chips. > > Any help would be much appreciated. Sonix does not respond to my emails > > and google does not help (there's a 12-page long datasheets, but it is > > not detailed enough to write a driver) > > > > Thanks, please answer to l.riso@tiscalinet.it > > Depends what sort of driver you want to write, kernel module or SANE > backend. > > See also these links: > http://www.mnementh.co.uk/sonix/ > > and > http://sonix.sourceforge.net/ That's the unuseful thing I was talking about From philip@digitalinfinity.biz Fri Jun 11 09:52:33 2004 From: philip@digitalinfinity.biz (Philip V. Neves) Date: Fri, 11 Jun 2004 01:52:33 -0700 Subject: [sane-devel] I can't get my scanner to work. Message-ID: <40C972D1.2060303@digitalinfinity.biz> I am trying to get my scanner to work with sane. I have a Canon LIDE20 usb scanner. sane-find-scanner sees the scanner but when I run scanimage -L nothing comes up. Its as if the scanner isn't there. 77 Here is what I get when I run sane-find-scanner. If someone could please point me in the right direction I would greately appreciateit. trying libusb: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 () iProduct 2 (USB UHCI-alt Root Hub) iSerialNumber 1 (d400) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 8 bInterval 255 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 bDeviceSubClass 0 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x04A9 idProduct 0x220D bcdDevice 1.00 iManufacturer 1 (Canon) iProduct 2 (CanoScan) iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 160 (Remote Wakeup) MaxPower 500 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 bInterfaceSubClass 0 bInterfaceProtocol 255 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 1 bInterval 16 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 checking for GT-6801 ... this is not a GT-6801 (bDeviceSubClass = 0x0) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bcdUSB = 0x110) checking for MA-1509 ... this is not a MA-1509 (bDeviceSubClass = 0x0) checking for LM983[1,2,3] ... Couldn't claim interface: could not claim interface 0: Device or resource busy found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan], chip=LM983x?) at libusb:001:002 bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046D idProduct 0xC20C bcdDevice 1.03 iManufacturer 1 (Logitech) iProduct 2 (WingMan Precision USB) iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 128 () MaxPower 30 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 3 bInterval 10 ms bRefresh 0 bSynchAddress 0 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. -- --------------------------------------------------------------- Philip V. Neves Email: philip@digitalinfinity.biz Phone: (250)372-8536 pneves@telus.net --------------------------------------------------------------- Nearly every man who develops an idea works at it up to the point where it looks impossible, and then gets discouraged. that's not the place to become discouraged. Thomas Alva Edison. From insane@piments.com Sun Jun 13 19:31:49 2004 From: insane@piments.com (insane@piments.com) Date: Sun, 13 Jun 2004 20:31:49 +0200 Subject: [sane-devel] epson 2400 neg scans In-Reply-To: References: Message-ID: Thanks for the detailed info on the 1670 photo. It seems odd that there are lines on the neg scan that are not on normal flatbed mode, I suppose it could just be a bug in the backend that it not picking up intermediate scan lines. You say that this only happens on high res but later that higher res is not availible on transparency. Could you be more specific? I sounds a bit contradictory. What res. works correctly (no lines) and what is the max you can scan a neg. even if the output is poor? Thanks for your help. Peter. On Sat, 12 Jun 2004 00:30:46 +1000 (EST), wrote: >> The Perfection 1670 and the 2400 look interesting. It appears that the >> former is not supported by sane and runs on a different chip set to >> other Perfection scanners so I'll stike that from the list. >> > Peter, > I've got an Epson Perfection 1670 Photo and I'd be glad to answer any > questions you (or anyone else on this mailing list) have. Please Cc me as > I haven't subscribed to this list. > > Pros: > - Works under both Linux's scanner kernel module and libusb. > - I've gotten it to work under both Debian unstable (very easy, glorious > apt-get) and Red Hat 9.0 (heavily mangled with alien-converted debs). > - I was also able to get the Epson firmware file using unshield (CVS > version from the synce project). Else, you can get it from: > http://www.commercialventvac.com/~jeffs/epson1670andFedora.html > - Flatbed scanning (ie not transparency) works even up to the maximum > resolution of 1600dpi. Jeff's result (above) maybe caused by the older > sane-backend-1.0.13 -- shrugs. > - The transparency scanning works to the extent that the fluorescence > light can be controlled from sane. > > Cons: > - A bit expensive IMHO. > - The four scanner buttons doesn't have any effect. > - Film scanning seems to introduce fine lines (only noticeable at high > resolutions) that isn't due to the negative. > - Not sure which component is at fault, but the colour of the > film/negatives aren't properly calibrated. > > As far as I'm concerned, film scanning of the 1670 isn't usable under > sane. Of course, it is distinctly possible that I haven't got things > setup > correctly as I've never played with film (35mm Kodak) scanning before. It > is also possible that the CVS version of sane-backend fixes some of the > above problems (currently using 1.0.14). > > BTW, thank you to the developers who integrated 1670 support into sane. > > Cheers > Eddie > > > -- Using M2, Opera's e-mail client: on Gentoo Linux From vykk3@comcast.net Sun Jun 13 21:05:24 2004 From: vykk3@comcast.net (Victoria Welch) Date: Sun, 13 Jun 2004 13:05:24 -0700 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! Message-ID: <200406131305.24125.vykk3@comcast.net> Hi folks! Just to let everyone know after about the 7,858,939,058th :-) google I found something that REALLY helped get me going! http://users.dslextreme.com/~craig.lawson/linux_notes/gentoo.2004.0.html The big secret was that I had to build sane/sane backends with: USE="usb" emerge sane-backends After that the scanner showed up and works GREAT! Happy, happy, joy, joy :-) :-) :-) ! Now I can dump the w98 partition with extreme prejudice and save that plustek for a trip to the shooting range :-). Klaus: Especially, thanks for the encouragement to keep me plugging away at it, turns out to have been well worth it. Really nice scanner under linux! Thanks & take care es 73, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From vykk3@comcast.net Sun Jun 13 23:38:10 2004 From: vykk3@comcast.net (Victoria Welch) Date: Sun, 13 Jun 2004 15:38:10 -0700 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! In-Reply-To: <20040613212021.GA16490@braveman.lan> References: <200406131305.24125.vykk3@comcast.net> <20040613212021.GA16490@braveman.lan> Message-ID: <200406131538.10735.vykk3@comcast.net> Hello Philipp, Thanks for the response! On Sunday 13 June 2004 14:20, root wrote: > > [ ... ] > > The big secret was that I had to build sane/sane > > backends with: > > > > USE="usb" emerge sane-backends > > try the '--verbose' option of emerge. this can help a > lot. and sometimes you can see a description of the > use-flags with 'etcat uses '. Thanks for that pointer. Love gentoo but there is indeed a bit to learn :-). Now if I can get it working as other than root, we'll be there. xsane insists on picking up that tv tuner card no matter what. I even copied over the AGFA:SNAPSCAN.drc over to my .sane directory and it is roundly ignored :-). Thanks & take care, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From vykk3@comcast.net Sun Jun 13 23:53:21 2004 From: vykk3@comcast.net (Victoria Welch) Date: Sun, 13 Jun 2004 15:53:21 -0700 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! In-Reply-To: <200406131538.10735.vykk3@comcast.net> References: <200406131305.24125.vykk3@comcast.net> <20040613212021.GA16490@braveman.lan> <200406131538.10735.vykk3@comcast.net> Message-ID: <200406131553.21883.vykk3@comcast.net> Great progress here today :-) On Sunday 13 June 2004 15:38, Victoria Welch wrote: > > Now if I can get it working as other than root, we'll be > there. xsane insists on picking up that tv tuner card no > matter what. I even copied over the AGFA:SNAPSCAN.drc > over to my .sane directory and it is roundly ignored :-). Turns out there is now a group "scanner". Added myself to that, logged out and back in and we were in business. I still have to choose between the tv tuner card and the flatbed. Would be just as happy if the tv tuner didn't show up since xsane doesn't seem to like it enough to do anything with it. If you delete the .drc for the tv card, it re-establishes itself as soon as you run xsane :-(. -d, --device-settings file load device settings from file (without ".drc") Seems to be ignored :-(. One last thing to fix now, but I can live with it if I have to. Any thoughts on this one appreciated. Thanks & take care, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From kaplanam1@comcast.net Mon Jun 14 01:08:09 2004 From: kaplanam1@comcast.net (Allan Kaplan) Date: Sun, 13 Jun 2004 17:08:09 -0700 Subject: [sane-devel] SANE driver for NEC Petiscan scanner Message-ID: Greetings again, Here is the progress I have made: The sketchy results of sane-find-scanner -v -v follow. NEC drivers for Win 95, 98, ME, 2000 (apparently), and MacOS 9.x (they say X, but not true) are at . The filenames are English even though this is a Japanese page. The files are the "8u3" files. At the bottom of the page is a link to "MultiReaderPetiScan800U2" which is the previous version of the PC drivers. As far as I can tell, without further digging into the guts of the scanner, there are two chips which say JIC (?) ES52099S 9919-LHIJ I was not able to find data on this chip. And Winbond W24512AJ-15 919SA290732601CE Chip specs: It occurred to me that this scanner will run off another computer I have access to, but only in MacOS9. Might there more data that I can access from a computer that will actually run the scanner, versus this laptop with which I want to ultimately run the scanner, but only uses MacOSX? Thanks everyone for your help. Please advise me on the next step I can take in this project. Allan bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 255 bDeviceSubClass 0 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x0475 idProduct 0x0100 bcdDevice 1.00 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 128 () MaxPower 500 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x01 (out 0x01) bmAttributes 2 (bulk) wMaxPacketSize 8 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 8 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 checking for GT-6801 ... this is not a GT-6801 (bcdUSB = 0x100) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bDeviceSubClass = 0x0) checking for MA-1509 ... this is not a MA-1509 (bcdUSB = 0x100) checking for LM983[1,2,3] ... this is not a LM983x (bEndpointAddress = 0x1, bmAttributes = 0x2, wMaxPacketSize = 0x8, bInterval = 0x0) checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x100) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... this is not a GL841 (bcdUSB = 0x100) checking for ICM532B ... check 2, this is not a ICM532B (bcdUSB = 0x100) found USB scanner (vendor=0x0475, product=0x0100) at libusb:003:002-0475-0100-ff-00 From henning@meier-geinitz.de Mon Jun 14 10:19:20 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 14 Jun 2004 11:19:20 +0200 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! In-Reply-To: <200406131553.21883.vykk3@comcast.net> References: <200406131305.24125.vykk3@comcast.net> <20040613212021.GA16490@braveman.lan> <200406131538.10735.vykk3@comcast.net> <200406131553.21883.vykk3@comcast.net> Message-ID: <20040614091920.GD8899@meier-geinitz.de> Hi, On Sun, Jun 13, 2004 at 03:53:21PM -0700, Victoria Welch wrote: > I still have to choose between the tv tuner card and the > flatbed. Would be just as happy if the tv tuner didn't > show up since xsane doesn't seem to like it enough to do > anything with it. If you delete the .drc for the tv card, > it re-establishes itself as soon as you run xsane :-(. To disable v4l completely, edit /etc/sane.d/dll.conf and comment out "v4l". To start xsane with your scanner directly (without chosing): xsane yourbackend (e.g. xsane plustek). > -d, --device-settings file load device settings from file > (without ".drc") > > Seems to be ignored :-(. Really? It justs loads the settings for one device. It doesn't set the default device to use. Bye, Henning From henning@meier-geinitz.de Mon Jun 14 10:36:50 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 14 Jun 2004 11:36:50 +0200 Subject: [sane-devel] I can't get my scanner to work. In-Reply-To: <40C972D1.2060303@digitalinfinity.biz> References: <40C972D1.2060303@digitalinfinity.biz> Message-ID: <20040614093650.GE8899@meier-geinitz.de> Hi, On Fri, Jun 11, 2004 at 01:52:33AM -0700, Philip V. Neves wrote: > I am trying to get my scanner to work with sane. I have a Canon LIDE20 > usb scanner. sane-find-scanner sees the scanner but when I run scanimage > -L nothing comes up. Its as if the scanner isn't there. > 77 > Here is what I get when I run sane-find-scanner. If someone could please > point me in the right direction I would greately appreciateit. Which operating system and version are you using? Which SANE version? [...] > [...] > > checking for GT-6801 ... > this is not a GT-6801 (bDeviceSubClass = 0x0) > checking for GT-6816 ... > this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) > checking for MA-1017 ... > this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) > checking for MA-1015 ... > this is not a MA-1015 (bcdUSB = 0x110) > checking for MA-1509 ... > this is not a MA-1509 (bDeviceSubClass = 0x0) > checking for LM983[1,2,3] ... > Couldn't claim interface: could not claim interface 0: Device or > resource busy > Something else is caliming the scanner. So either another program has already opened the scanner or there is a kernel bug. Or you are using Linux 2.4 and the kernel scanner driver has claimed the scanner. SANE_DEBUG_PLUSTEK=255 scanimage -L will print why scanimage doesn't detect the scanner. But I guess it's the same problem: device busy. Bye, Henning From henning@meier-geinitz.de Mon Jun 14 10:49:43 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 14 Jun 2004 11:49:43 +0200 Subject: [sane-devel] SANE driver for NEC Petiscan scanner In-Reply-To: References: Message-ID: <20040614094943.GG8899@meier-geinitz.de> Hi, On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: > As far as I can tell, without further digging into the guts of the scanner, > there are two chips which say > > JIC (?) > ES52099S > 9919-LHIJ > I was not able to find data on this chip. Google finds some references but no spec or explanation. > Winbond > W24512AJ-15 > 919SA290732601CE > Chip specs: > So that's RAM. No other chips? In this c ase the JIC must be the scan chip. > It occurred to me that this scanner will run off another computer I have > access to, but only in MacOS9. Might there more data that I can access from > a computer that will actually run the scanner, versus this laptop with which > I want to ultimately run the scanner, but only uses MacOSX? You need software that can listen to the USB commands send to the scanner ("sniffer"). While some programs are available for Windows I don't know if that's the case for MacOS9. Bye, Henning From Francois.Patte@math-info.univ-paris5.fr Mon Jun 14 11:18:17 2004 From: Francois.Patte@math-info.univ-paris5.fr (=?iso-8859-1?b?RnJhbudvaXM=?= Patte) Date: Mon, 14 Jun 2004 12:18:17 +0200 Subject: [sane-devel] scanner HP 4600 In-Reply-To: <20040614094943.GG8899@meier-geinitz.de> References: <20040614094943.GG8899@meier-geinitz.de> Message-ID: <1087208297.40cd7b69d643d@www.math-info.univ-paris5.fr> Bonjour, Is it possible to have a Hewlett-Packard Scanjet 4600 working under linu= x with sane? Thank you -- Fran=E7ois Patte Inde : Ecole fran=E7aise d'Extr=EAme-Orient Deccan College Pune 411006 T=E9l : (00 91) (0) 20 26 69 39 04 France : Universit=E9 Ren=E9 Descartes - Paris 5 UFR de math=E9matiques et informatique http://www.math-info.univ-paris5.fr/~patte From henning@meier-geinitz.de Mon Jun 14 11:28:18 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 14 Jun 2004 12:28:18 +0200 Subject: [sane-devel] scanner HP 4600 In-Reply-To: <1087208297.40cd7b69d643d@www.math-info.univ-paris5.fr> References: <20040614094943.GG8899@meier-geinitz.de> <1087208297.40cd7b69d643d@www.math-info.univ-paris5.fr> Message-ID: <20040614102818.GA1991@meier-geinitz.de> Hi, On Mon, Jun 14, 2004 at 12:18:17PM +0200, François Patte wrote: > Is it possible to have a Hewlett-Packard Scanjet 4600 working under linux with > sane? No. At least that's what our search engine says: http://www.sane-project.org/cgi-bin/driver.pl?manu=hew&model=4600&bus=any Bye, Henning From kaplanam1@comcast.net Mon Jun 14 18:14:01 2004 From: kaplanam1@comcast.net (Allan Kaplan) Date: Mon, 14 Jun 2004 10:14:01 -0700 Subject: [sane-devel] Re: SANE driver for NEC Petiscan scanner In-Reply-To: <20040614125025.7832.46018.Mailman@haydn.debian.org> Message-ID: Greetings, OK, I managed to take the scanner apart without damaging it, and found the the big chip hiding under a cover. TIS 2AX000 59S1998 F8W07-000 9939 I will see what other info I can find. Thanks, Allan > Message: 3 > Date: Mon, 14 Jun 2004 11:49:43 +0200 > From: Henning Meier-Geinitz > To: sane-devel@lists.alioth.debian.org > Subject: Re: [sane-devel] SANE driver for NEC Petiscan scanner > > Hi, > > On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: >> As far as I can tell, without further digging into the guts of the scanner, >> there are two chips which say >> >> JIC (?) >> ES52099S >> 9919-LHIJ >> I was not able to find data on this chip. > > Google finds some references but no spec or explanation. > >> Winbond >> W24512AJ-15 >> 919SA290732601CE >> Chip specs: >> > > So that's RAM. No other chips? In this c ase the JIC must be the scan > chip. > >> It occurred to me that this scanner will run off another computer I have >> access to, but only in MacOS9. Might there more data that I can access from >> a computer that will actually run the scanner, versus this laptop with which >> I want to ultimately run the scanner, but only uses MacOSX? > > You need software that can listen to the USB commands send to the > scanner ("sniffer"). While some programs are available for Windows I > don't know if that's the case for MacOS9. > > Bye, > Henning > > From vykk3@comcast.net Mon Jun 14 18:37:06 2004 From: vykk3@comcast.net (Victoria Welch) Date: Mon, 14 Jun 2004 10:37:06 -0700 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! In-Reply-To: <20040614091920.GD8899@meier-geinitz.de> References: <200406131305.24125.vykk3@comcast.net> <200406131553.21883.vykk3@comcast.net> <20040614091920.GD8899@meier-geinitz.de> Message-ID: <200406141037.06524.vykk3@comcast.net> Hello Henning, Thanks very much for the response! On Monday 14 June 2004 02:19, Henning Meier-Geinitz wrote: > [ ... ] > To disable v4l completely, edit /etc/sane.d/dll.conf and > comment out "v4l". I'm leaving this in for now, I am not sure there is a point to it since xsane doesn't seem to work with it and I have no need to scan from the tv tuner :-). > To start xsane with your scanner > directly (without chosing): > > xsane yourbackend (e.g. xsane plustek). > > > -d, --device-settings file load device settings from > > file (without ".drc") > > > > Seems to be ignored :-(. > > Really? It justs loads the settings for one device. It > doesn't set the default device to use. Thanks, that works now :-). I was taking the -d info literally and specifying: xsaneAGFA:SNAPSCAN1212U__2 (less .drc) from the ~/.sane/xsane directory. Just snapscan works fine :-). Thanks very much and take care, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From anoah@pfeiffer.edu Tue Jun 15 02:07:57 2004 From: anoah@pfeiffer.edu (m. allan noah) Date: Mon, 14 Jun 2004 21:07:57 -0400 (EDT) Subject: [sane-devel] Re: SANE driver for NEC Petiscan scanner In-Reply-To: References: Message-ID: TIS is teco image systems. 2ax000 must be part number. next is date code. there is a little hp that uses this chip (photo 1000 iirc). your best bet is going to be usb sniff from windows, and compare the data to what is used by the other teco backends, just on the off chance that it is similar or encapsulated version. allan On Mon, 14 Jun 2004, Allan Kaplan wrote: > Greetings, > > OK, I managed to take the scanner apart without damaging it, and found the > the big chip hiding under a cover. > > TIS > 2AX000 > 59S1998 > F8W07-000 > 9939 > > I will see what other info I can find. > > Thanks, > > Allan > > > > > Message: 3 > > Date: Mon, 14 Jun 2004 11:49:43 +0200 > > From: Henning Meier-Geinitz > > To: sane-devel@lists.alioth.debian.org > > Subject: Re: [sane-devel] SANE driver for NEC Petiscan scanner > > > > Hi, > > > > On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: > >> As far as I can tell, without further digging into the guts of the scanner, > >> there are two chips which say > >> > >> JIC (?) > >> ES52099S > >> 9919-LHIJ > >> I was not able to find data on this chip. > > > > Google finds some references but no spec or explanation. > > > >> Winbond > >> W24512AJ-15 > >> 919SA290732601CE > >> Chip specs: > >> > > > > So that's RAM. No other chips? In this c ase the JIC must be the scan > > chip. > > > >> It occurred to me that this scanner will run off another computer I have > >> access to, but only in MacOS9. Might there more data that I can access from > >> a computer that will actually run the scanner, versus this laptop with which > >> I want to ultimately run the scanner, but only uses MacOSX? > > > > You need software that can listen to the USB commands send to the > > scanner ("sniffer"). While some programs are available for Windows I > > don't know if that's the case for MacOS9. > > > > Bye, > > Henning > > > > > > > -- "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 olaf@epkowa.co.jp Tue Jun 15 05:31:18 2004 From: olaf@epkowa.co.jp (Olaf Meeuwissen) Date: Tue, 15 Jun 2004 13:31:18 +0900 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <20040609203310.GP7920@meier-geinitz.de> (Henning Meier-Geinitz's message of "Wed, 9 Jun 2004 22:33:11 +0200") References: <20040609164851.1fcddb78@expensive> <20040609203310.GP7920@meier-geinitz.de> Message-ID: <87brjljvc9.fsf@zen.epkowa.co.jp> Hi Tom, Henning Meier-Geinitz writes: > Hi, > > On Wed, Jun 09, 2004 at 04:48:51PM +0100, Tom Schutzer-Weissmann wrote: >> I had problems using the Epkowa libraries (libsane-epkowa) and the >> iscan frontend with my usb scanner in kernel 2.6. > >> The scanner was closed after each operation. Once closed, nothing >> could be read from it, and I got lots of BULK TIMEOUTs, although >> there were no errors when the device was reopened. >> >> By modifying the code so that usb_reset() was always called before >> usb_release_interface() and usb_close(), I solved the problem. > > Doesn't usb_reset() cause a renumeration and therefore the device gets > a new device file? I guess this isn't the default for closing USB > devices. Maybe the usb_reset just hides a bug in the SANE backend, > libusb or the kernel. Henning is right about the re-enumeration. As far as I understand the docs, that means that after calling usb_reset(), you may no longer use the handle you have. Problem is, it *is* used twice after that call. If the documentation is serious about this re-enumeration, than your "fix" is incorrect and has the potential to break support for *all* SANE supported USB devices. That it works for you is mere coincidence. FYI: http://libusb.sourceforge.net/doc/function.usbreset.html That leads us to a bug in the epson/epkowa backends, quite possibly caused by undocumented behaviour of this particular scanner. :-( -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From kaplanam1@comcast.net Tue Jun 15 06:42:04 2004 From: kaplanam1@comcast.net (Allan Kaplan) Date: Mon, 14 Jun 2004 22:42:04 -0700 Subject: [sane-devel] Re: SANE driver for NEC Petiscan scanner In-Reply-To: Message-ID: Thanks, I will work on finding a PC to check it from. Unfortunately, VirtualPC for Mac will not read the USB bus, or I wouldn't need Sane in the first place. Allan On 6/14/04 6:07 PM, "m. allan noah" wrote: > TIS is teco image systems. 2ax000 must be part number. next is date code. > > there is a little hp that uses this chip (photo 1000 iirc). > > your best bet is going to be usb sniff from windows, and compare the data > to what is used by the other teco backends, just on the off chance that it > is similar or encapsulated version. > > allan > > On Mon, 14 Jun 2004, Allan Kaplan wrote: > >> Greetings, >> >> OK, I managed to take the scanner apart without damaging it, and found the >> the big chip hiding under a cover. >> >> TIS >> 2AX000 >> 59S1998 >> F8W07-000 >> 9939 >> >> I will see what other info I can find. >> >> Thanks, >> >> Allan >> >> >> >>> Message: 3 >>> Date: Mon, 14 Jun 2004 11:49:43 +0200 >>> From: Henning Meier-Geinitz >>> To: sane-devel@lists.alioth.debian.org >>> Subject: Re: [sane-devel] SANE driver for NEC Petiscan scanner >>> >>> Hi, >>> >>> On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: >>>> As far as I can tell, without further digging into the guts of the scanner, >>>> there are two chips which say >>>> >>>> JIC (?) >>>> ES52099S >>>> 9919-LHIJ >>>> I was not able to find data on this chip. >>> >>> Google finds some references but no spec or explanation. >>> >>>> Winbond >>>> W24512AJ-15 >>>> 919SA290732601CE >>>> Chip specs: >>>> >>> >>> So that's RAM. No other chips? In this c ase the JIC must be the scan >>> chip. >>> >>>> It occurred to me that this scanner will run off another computer I have >>>> access to, but only in MacOS9. Might there more data that I can access >>>> from >>>> a computer that will actually run the scanner, versus this laptop with >>>> which >>>> I want to ultimately run the scanner, but only uses MacOSX? >>> >>> You need software that can listen to the USB commands send to the >>> scanner ("sniffer"). While some programs are available for Windows I >>> don't know if that's the case for MacOS9. >>> >>> Bye, >>> Henning >>> >>> >> >> >> From gerard@gkall.hobby.nl Tue Jun 15 09:41:55 2004 From: gerard@gkall.hobby.nl (gerard klaver) Date: Tue, 15 Jun 2004 08:41:55 +0000 Subject: [sane-devel] Re: SANE driver for NEC Petiscan scanner In-Reply-To: References: Message-ID: <1087288915.2089.21.camel@gk-lex3> Teco1, 2 and 3 are backends for SCSI scanners so don't expect that the codes are the same. Most teco scanners have a VM... nr. on the outside of the scanner and sometimes also placed somewhere in the software. Also some rebadged teco scanners have a VM.... on the outside or inside. See http://www.vic-corp.com/ download sections for some of the teco scanners with there VM.. number, (just for comparison) On Tue, 2004-06-15 at 01:07, m. allan noah wrote: > TIS is teco image systems. 2ax000 must be part number. next is date code. > > there is a little hp that uses this chip (photo 1000 iirc). > > your best bet is going to be usb sniff from windows, and compare the data > to what is used by the other teco backends, just on the off chance that it > is similar or encapsulated version. > > allan > > On Mon, 14 Jun 2004, Allan Kaplan wrote: > > > Greetings, > > > > OK, I managed to take the scanner apart without damaging it, and found the > > the big chip hiding under a cover. > > > > TIS > > 2AX000 > > 59S1998 > > F8W07-000 > > 9939 > > > > I will see what other info I can find. > > > > Thanks, > > > > Allan > > > > > > > > > Message: 3 > > > Date: Mon, 14 Jun 2004 11:49:43 +0200 > > > From: Henning Meier-Geinitz > > > To: sane-devel@lists.alioth.debian.org > > > Subject: Re: [sane-devel] SANE driver for NEC Petiscan scanner > > > > > > Hi, > > > > > > On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: > > >> As far as I can tell, without further digging into the guts of the scanner, > > >> there are two chips which say > > >> > > >> JIC (?) > > >> ES52099S > > >> 9919-LHIJ > > >> I was not able to find data on this chip. > > > > > > Google finds some references but no spec or explanation. > > > > > >> Winbond > > >> W24512AJ-15 > > >> 919SA290732601CE > > >> Chip specs: > > >> > > > > > > So that's RAM. No other chips? In this c ase the JIC must be the scan > > > chip. > > > > > >> It occurred to me that this scanner will run off another computer I have > > >> access to, but only in MacOS9. Might there more data that I can access from > > >> a computer that will actually run the scanner, versus this laptop with which > > >> I want to ultimately run the scanner, but only uses MacOSX? > > > > > > You need software that can listen to the USB commands send to the > > > scanner ("sniffer"). While some programs are available for Windows I > > > don't know if that's the case for MacOS9. > > > > > > Bye, > > > Henning > > > -- ---------- m.vr.gr. Gerard Klaver From epl@unimelb.edu.au Mon Jun 14 15:59:43 2004 From: epl@unimelb.edu.au (epl@unimelb.edu.au) Date: Tue, 15 Jun 2004 00:59:43 +1000 (EST) Subject: [sane-devel] epson 2400 neg scans In-Reply-To: Message-ID: On Sun, 13 Jun 2004 insane@piments.com wrote: > You say that this only happens on high res but later that higher res is > not availible on transparency. Could you be more specific? I sounds a bit > contradictory. > High res *is* available under transparency (up to 1600dpi), just not very useful due to lines appearing. > What res. works correctly (no lines) and what is the max you can scan a > neg. even if the output is poor? > Okay, I did more experiments and even at 200dpi, I can see lines. The weird thing is, these lines remain even if I simply scan an opaque piece of paper (while in transparency mode). Maybe the backend is buggy. Maybe there's some calibration that the scanner or scanner's firmware that weirds sane out. I haven't tried it under Windows either, so... Note that transparency mode does more than switching on the fluorescent light on the transparency cover. For example, in transparency mode, it isn't possible to scan an A4 page as you're limited to an (approx) A6 area. Whether this is a scanner or sane limitation I don't know. I'll see whether I can upload an sample image with lines onto a webpage in the coming days. === BTW Not related to the scanner or scanner backend itself, but I've been told off-list that due to a lack of accurate colour calibration under Linux, 35mm negative scanning doesn't work anyhow -- regardless of the scanner used. I'm *really* hoping someone will respond telling me how utterly wrong I am and that Free as in speech software is just an apt-get away and that it works flawlessly with my scanner... Cheers Eddie From stern@rowland.harvard.edu Mon Jun 14 16:54:34 2004 From: stern@rowland.harvard.edu (Alan Stern) Date: Mon, 14 Jun 2004 11:54:34 -0400 (EDT) Subject: [sane-devel] Re: [Linux-usb-users] Problems with HP 6200C scanner and SANE In-Reply-To: <20040612110326.GC652@hardeman.nu> Message-ID: On Sat, 12 Jun 2004, David Härdeman wrote: > On Mon, May 31, 2004 at 02:58:12PM -0400, Alan Stern wrote: > >On Mon, 31 May 2004, David Härdeman wrote: > >> I'm currently trying to get an HP 6200C USB scanner to work with SANE > >> (1.0.14) under Linux (Debian woody with some backports, kernel 2.4.26). > >> Whenever I scan something which requires a low amount of data (lineart > >> picture at 100dpi for instance), everything works just fine. But when I > >> scan a more bandwidth hungry pic, it never succeeds. I've tried this > >> both with the "scanner" module in the kernel and with libusb but both > >> seem to experience the same problems. > >> > >> I have tried sane's "dumb-read" option and all other option which were > >> mentioned in the sane-hp man page but I'm running out of ideas. Any > >> clues what might cause this (might later kernels be too picky with their > >> timing requirements)? > > > >The most likely explanation is that some other program (possibly a hotplug > >utility) is trying to access the scanner while you're using it, thereby > >confusing the scanner and causing it to fail. I've seen reports from > >other people where the "usbmodules" program did this. See what happens if > >you turn off all hotplug support. > > Hi, > and sorry for the delay in answering. > > I am running this on Debian Woody (with backported usblib and sane > packages of recent versions), so there is no hotplug support on the > system, the only other thing I could think of is the "nut" UPS daemon > which checks the status of the UPS over USB. > > However, disabling nut and trying to scan did not help sort out the > problem. > > Any other suggestions? Nothing much about 2.4.26 springs to mind. You might try turning on USB debugging in the kernel configuration to see if the system log contains any useful information when the fault occurs. Or you could try moving up to Linux 2.6, which has a more robust USB stack. Alan Stern From David@phenix.fr Tue Jun 15 15:19:37 2004 From: David@phenix.fr (David Neary) Date: Tue, 15 Jun 2004 16:19:37 +0200 Subject: [sane-devel] RE: JSane Message-ID: Andi McLean said: > On Sunday 13 June 2004 00:27, Klemens Dickbauer wrote: > Dave what do you think about putting the JNI part in with my code? If you can make sense of it, please feel free. The JNI wrappers are actually quite trivial. The hardest thing is figuring out how to avoid memory leaks. There are 2 ways to do this - expose allocation and deletion methods in the C, or communicate how much space is needed to the Java side, and let the jvm take care of garbage collection. The latter is the reason why I added the convenience method "getNumberOfDevices" in the JNI wrappers, I think it has a bug in it too. I think the correct implementation should have something like: devListLen = 0; while (device_list[devListLen] != NULL) devListLen ++; return devListLen; the one I have seems to have an off-by-one error when there is at least one device (I'm not sure I understand why, but it's the behaviour I'm seeing). > Does it fit with the design I've created? You're going to laugh, but because of continued problems with DLLs, I am now convinced that the nest thing for me to do is to use your pure Java implementation of the net protocol :) I like your design, even though some of the class names are a bit cumbersome, and I think that it's probably the best way to go for a Java implementation. > > Anyway, having a direct Java interface to the sane libs seems also > > desireable to me. David, what do you think about the > changes I suggest? I missed this mail (I'm on a digest, so I occasionally overlook mails I probably shouldn't). Sorry :) > > An unexpected exception has been detected in native code > outside the VM. > > Unexpected Signal : 11 occurred at PC=0x4DE37B06 > > Function=sane_dll_control_option+0x56 > > Library=/usr/lib/libsane.so.1 Looks like you're running on Linux or some other unix... > > Current Java thread: > > at > org.saneproject.scan.sane.Sane.getControlOption(Native Method) > > [..] Have you tried running the org.sane.Test class? Here's a sample usage of the Sane bindings: public class Test { public static void main(String[] args) throws IOException { Sane sane = new Sane(); int version[] = new int[1]; // Array to get version #. int status = sane.init(version); if (status != Sane.STATUS_GOOD) { System.out.println( "init() failed. Status= " + sane.strstatus(status)); return; } System.out.println("VersionMajor =" + sane.versionMajor(version[0])); System.out.println("VersionMinor =" + sane.versionMinor(version[0])); System.out.println("VersionBuild =" + sane.versionBuild(version[0])); // Get list of devices. // Allocate room for 50. SaneDevice devList[] = new SaneDevice[50]; status = sane.getDevices(devList, false); if (status != Sane.STATUS_GOOD) { System.out.println( "getDevices() failed. Status= " + sane.strstatus(status)); return; } for (int i = 0; i < 50 && devList[i] != null; i++) { System.out.println( "Device '" + devList[i].name + "' is a " + devList[i].vendor + " " + devList[i].model + " " + devList[i].type); } // Sanity test over... clean up sane.exit(); } } Your code should look very similar to the C code equivalent: sane.init (version); sane.open (device); sane.getOptionDescriptor(); sane.getControlOption(); // Get options sane.setControlOption(); // Set option value sane.start(); repeat sane.read(); return to sane.start() if we need more pages sane.cancel(); sane.close(); sane.exit(); You can also compile the C code with -g and run java in a debugger to get a better idea of what's going on. Hope this all helps, Cheers, Dave. From David@phenix.fr Tue Jun 15 16:17:44 2004 From: David@phenix.fr (David Neary) Date: Tue, 15 Jun 2004 17:17:44 +0200 Subject: [sane-devel] Re: JSane Message-ID: Hi Andi, Andi McLean said: > I have designed a structure to split interface and > implementation how does > everyone feel about these? Would it be possible for you to either include your java sources in the .jars you release, or release a source jar alongside them, please? I know they are available via CVS, but it would be nice to have the sources which were used to make the jar as well. Thanks, Dave. From David@phenix.fr Tue Jun 15 16:20:21 2004 From: David@phenix.fr (David Neary) Date: Tue, 15 Jun 2004 17:20:21 +0200 Subject: [sane-devel] RE: JSane Message-ID: Hi again, > Would it be possible for you to either include your java > sources in the .jars you release, or release a source jar > alongside them, please? I know they are available via CVS, > but it would be nice to have the sources which were used to > make the jar as well. Also, would you mind correcting the spelling of Descriptor please? Using sane option discriptors is going to drive me scatty :) Cheers, Dave. From jochen@penguin-breeder.org Tue Jun 15 16:10:24 2004 From: jochen@penguin-breeder.org (Jochen Eisinger) Date: Tue, 15 Jun 2004 17:10:24 +0200 Subject: [sane-devel] Question About Mustek 600CP scanner on Suse 9.1 In-Reply-To: References: Message-ID: <40CF1160.8040307@penguin-breeder.org> Hi, Neal Gamradt wrote: > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5 > from 'parport0' > [...] > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x00 > from 'parport0' the backend gets the correct value first, but later the scanner only returns the wrong value 0x00. To me this looks like the scanner got confused or something. Eddy, could you have a look at this? kind regards -- jochen From dlw@hei.net Wed Jun 16 18:54:31 2004 From: dlw@hei.net (Don) Date: Wed, 16 Jun 2004 10:54:31 -0700 Subject: [sane-devel] xsane -0.91 Message-ID: <40D08957.9060606@hei.net> Using xsane-0.91 with MDK 9.1 with KDE 2. I had xsane working fine with an Epson CX5400. However, the next time I booted the system, xsane no longer worked. Xsane could not find the scanner. The /etc/sane.d/epson.conf is the same as when it ran. - See below. lsusb and sane-find-scanner both return 04b8 0808 Seiko Epson Corp. /usr/bin/xsane said sane could not detect parallel devices as user and root. Any help getting xsane working again will be appreciated. Don The only lines in /etc/sane.d/epson.conf not disabled with an # are; usb 04b8 0808 usb /dev/usb/lb0 Xsane work like this before. -- Please do not send or forward HTML's. From info@linuxmaker.de Tue Jun 15 20:41:10 2004 From: info@linuxmaker.de (Andreas) Date: Tue, 15 Jun 2004 21:41:10 +0200 Subject: [sane-devel] PLUSTEK OpticPro 12000T do not work under Kernel 2.6.4-52 Message-ID: <200406152141.10202.info@linuxmaker.de> Hello, I need your help. I have upgraded my system from SuSE 8.2 to 9.1. Now I need for my Plustek parallelport-scanner the package sane-backends-2004-06-14.tar.gz. I have installed it correctly, so I mean. But my scanner can't be dectected. xsane shows errors and scanimage -L tells me "No scanners were identified". Shortly after the installation of the package and after making ./MakeModule.sh tells me dmesg parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] parport0: irq 7 detected ... pt_drv: no version for "struct_module" found: kernel tainted. ********************************************* pt_drv: init_module() pt_drv : driver version 0.43-3 .... MiscGetModelName - id = 15 pt_drv0: 9636T/12000T found on port 0x0378 pt_drv0: Lamp-Timer set to 180 seconds. pt_drv0: WarmUp period set to 30 seconds. pt_drv0: Lamp untouched on driver unload. Lamp-Timer started! pt_drv : init done, 1 device(s) found And the lamp at my scanner shutdown after 180s But I can't use the scanner which xsane or scanimage -L. After a reboot dmesg tells me only parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] parport0: irq 7 detected And lsmod shows me, pt_drv0 is no loaded. If I make now modprobe pt_drv I can see: Module Size Used by pt_drv 115796 0 ... parport_pc 35264 3 ppa 11656 0 parport 37704 4 pt_drv,lp,parport_pc,ppa And the lamp of the scanner is burning for 180s. But xsane and scanimage -L aren't possible. Can somebody tell, what I have to do, so pt_drv is correctly loaded at the booting and the scanner can use the devices? Perhaps I have forgotten something in the config-files. So, you can see the content of /etc/sane.d/plustek_pp.conf: ... #[direct] #device 0x378 # # leave the default values as specified in /etc/modules.conf # #option warmup -1 #option lOffOnEnd -1 #option lampOff -1 # model override switch, mostly for cosmetic changes, if the autodetection # does not work or could not work correctly #option mov 7 # # example for accessing the scanner via libieee1284 # #[direct] #device parport0 # # example for accessing the scanner via the kernel module # [kernel] device /dev/pt_drv option warmup -1 option lOffOnEnd -1 option lampOff -1 .... /etc/sane.d/dll.conf: ... pint plustek plustek_pp #pnm ... and /etc/modules.conf: alias char-major-40 pt_drv pre-install pt_drv modprobe -k parport options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0 slowIO=1 I hope somebody can help me at the solution of that problem. Thank you! Andreas From behnel_ml@gkec.tu-darmstadt.de Wed Jun 16 16:22:55 2004 From: behnel_ml@gkec.tu-darmstadt.de (Stefan Behnel) Date: Wed, 16 Jun 2004 17:22:55 +0200 Subject: [sane-devel] coloured gradient on scanned images Message-ID: <40D065CF.2020702@gkec.tu-darmstadt.de> This is a multi-part message in MIME format. --------------080509060209000004040706 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi! With my HP Scanjet 7400c, the scans all have a coloured gradient, as in the attached example. I first figured it might have to do with the warm up phase, but it doesn't change over time. I'm using sane 1.0.13 (the RPMs I found for 1.0.14 seem to be broken). Any idea what I could try? Gamma or contrasts in XSane don't change anything... Thanks in advance, Stefan --------------080509060209000004040706 Content-Type: image/jpeg; name="out.jpeg" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="out.jpeg" /9j/4AAQSkZJRgABAQEARgBGAAD/2wBDAAYEBQYFBAYGBQYHBwYIChAKCgkJChQODwwQFxQY GBcUFhYaHSUfGhsjHBYWICwgIyYnKSopGR8tMC0oMCUoKSj/2wBDAQcHBwoIChMKChMoGhYa KCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCj/wAAR CAPSAlADASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl 5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk 5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDzbxB8UvEOna5f2ls1oIoZ3jTMWTgMQM81 QX4w+Kf+elp/35/+vXHeMDnxVrB/6e5f/QjWSprKNKFtjuniavM1zM9LX4w+KRj95aHP/TH/ AOvUr/GDxQpG2W1/GH/69eZr2q0MNF05BocIroUq1R/aZ6CPjH4p2BhJa9cH9z/9enD4x+LD kK9nkdcwf/Xrz1FUhlH1pM4P1FLkj2F7Wp/Mz0H/AIXT4tH/AC0s/wDvx/8AXpB8bvFw6SWX /fj/AOvXmkh5IqLHNWqcexk69T+ZnqS/G/xfn/WWX/fj/wCvT/8AhePi4dJbL/vx/wDXrywD PSra2VykcckkLqkgyjOuA30J60+SHYFXqv7TPTIfjd4wZhmWyA/64/8A161bD4x+KbhjAz2g mf7jlQqr9fWvIbeA7st1B4XGcn0rdjRbDUJ47n/WrEy7RyA3aocI9EaQq1OrPTf+Fp+LBYGQ XNrJO1wII40i68ZbPP0qifjP4mWOXdNbhw21VCfnXELKumx2TZDzsjSsCfuM3A4+nNZI2xzS Lcr99Mrn36GhRRUq0l1PSLb41+J5ZmVpYMAE8JVi0+MniiSNzJJAGU5ACduleW2tqY5gWyC5 OORyOa0Vi2rCrMQzxkbT7c9amVkzB1p9z0FPjF4rKMS0GQwUfKamj+MXiZYz5zRtMGwY1XtX BWGdrqeTv646AVXZJGnlZJAjMRkngc9xU3voCrTXU9Bh+M/ic3JjcRBNuQStWW+MniMMwHkk D2HNc34d0vTLsTz6hd+ZMkY2RqCAPqemKzPHWn2ulXFp9mu4pzOu5kiI/dnPSmrN2sNzqKPN c7iT4y+IoSRMsat6bRwPemL8afEEpxAkchPQAD/CvKtUvmF/OVJwRjGPTj+lXtJtbi5lhubI EqMeaAeKrlSV2R7ao9Lnrh+KWvptMgjChlD4wcAj6etS6h8TtfjksBZxCWO5jDliB8vAyOnr mvPhaGNpRc3X73ZyiuD34B4o05rgQfvGcOpKxyHhVzxhfXkVNi1Vn1Z2tv8AFbxBNdvGbUeS rYMmOAPfimzfFzVFVFhiSaVjgheg/SucuV8izay8+Q3UpHmOUPP4CqFqi2bqAFlkkztJBx+l HyH7SV7XOzu/itrNrETJbJvOAigjLH8qoSfGTWE2+ZZIob7uWHP6VzmpWLXzmREKSx8KpOCw HXHaueutJmOWlChVHLBwV/McVcWuqE5z6M9APxn1Ldg2cZ/4GP8A4mlHxk1DvYR4/wB8f/E1 5mlqM5Vh+NTraLkqzBW9zxV+6Lnm+p6FJ8aL5Rj7BGWPQbx/8TUX/C578g/8S2Lj/poP/ia8 7NgsjFovmfHKk4/Kq7WLq37xSo9Ktcguap3PTf8Ahct4UyunQn6uP/iagPxqvf8AoFxf9/B/ 8TXlckDLKVAbZT0hjDYkRsHvVWiLnm+p6j/wuu7/AOgZFn/roP8A4mg/Gm84/wCJXFz/ANNB /wDE15dJZ4wUBx71WkjdG5GQO1O0ROU11PWf+F1XhIA0qLP/AF0H/wATTpfjTcLgJpkbN3+c YH/jteOsGJJNPdfJUA/fboPQUaE+0l3PXD8arsAZ0qLJ/wCmg/8AiaUfGm7IyNJiI6D94P8A 4mvHOSeTVrzEijBUkseBx096QvaS7nrbfGi7Vtp0qHd6eYP/AImmP8arvtpUPr/rB/8AE15I AoIYksO570rrkErzxxii4ueXc9X/AOF23ox/xKof+/g/+JrY8K/F+fU/EFjYT6RbiO4lEbNv ztz3xtrwfJDZPJrpPh/g+MtIK8fv1yDTuxqTufa9tBYyRq32SA5HeMVP9isSP+PO3/79iqWn H/R0+lXgetapI6bsUWVj/wA+dv8A9+xTvsVl/wA+dv8A9+xQDTs8VSiibjTZWXazt/8Av2KV bSz72dv/AN+xSsSBx1oEnGTx+FOyFdi/ZLMD/j0t/wDv2Kf9ls/+fWD/AL9ikyGAIP40BRx3 I55qrIV2O+zWmP8Aj1g/79igW1p/z6wf9+xQTz1pwq0kK7G+Ragj/RYfwjFBt7bHFtAP+ACl JOPlxn3oB4561SSC7G+Ragf8e0H/AHwKb9ntev2aD/v2Kfmm5PcVSSC4029r/wA+0H/fsUxo LUDJtoMf9cxUpNV7lZGQ+SVEg+7uGRn3q0kFxTBakcW0H/fsVHJFbKMm2hx7RinRhwF8wgvj DEcDP0pzc1okiLkPlWx6W8P/AHwKY8Nv/wA+8P8A3wKc8ak5xz1pqHcik00kS2MMNv1+zw/9 8CmmKAdIIv8AvgVKaY1OyJbIWih/54Rf98CoZbe3cYa3iP1QVYNManZE3IDDAOkEX/fAppih HSKP/vkVOw4pjU7Im5XZEHSNB/wEVGVX+6v5VO2KjYU7CuQMB2AqJhgVYYVEwp2A+O/F3/I0 6v8A9fcv/oZrJFbfiqJ38TasQv8Ay9S9/wDaNZJiYHBHNfOR2R2TT5mMVyCDV2H5s54yM02G ABlZuFzzmr8CREgRj5fepkxwdnqVMbJCCccVXd88Z6GtLV5lcIqgYXgEVRMBVGbaTjnpTXcb ZAME8jikZMvhehp4jL/MeMc4qzaW7SSgDAZvXpVXsQotjLe3zwy4U/xdqvbrq8VEkmeSOJdq q7cKPQVfg0tmiledwtrCcF1OcnBx/KrFpBHcabb21uyl5JWLMTjb0AqHI3jTa0JX02WzNnFZ qJJjskk54BIz+WKrXF2jPcmRC91M+QcdKmeZ7G/lit5syL+7WXOcDGKoxxvDdrJLneOcDnB9 aQ5StsV5oTLal0OZhJ5YTPORkk1Zt42ukWSbaHyFwOSQODgU+SNbUQSjDM5Jf2/EVPpilb4E LlScg+h70pPQxk1cpWMssdym5crzj6Z6GtGwjaaeASLlVc44689PypZohBdBggPznJ9/85q3 CxiZTkKYmMjkdx6D69Kyk76oixXhSaObfOCGnBIJ4wO1VbaLfdzo7dQVyDyKshi4fOflHAzT hFtlG1Dnhn46+1JOzEOsxNaylXceS67ZVwMlc8DNX/iPa6YdM0260mw+zPK7Bn3cuAO4rJtb oRzfaGhM0oYkiQ/Ln6elUNblmubt52Up5rFtiE7VJ9ARWsL3Gpe60UrAefMgnBfGcL/ebsK6 22SKziEck58xWy6Iu1BntmuXtVkhkab50ABKkr1NdVo2iy3EHn3crqrcqg4Le5qpkRfYlvp7 dbNFs0TLtvJC5O30qoWuHjigtQfOGVL9NvOevbrVqxsLmz1FJniP2dBleAxxjuKryJOls0oe adFbLnymU47YB6iloU3ctoWitFjkJZk3NuVvfGB+tSWtxHaJKcEsBkD1rPtpEuFJJkUxpnDj BIz29alS3LyEhgVZRh8/xe/pUjTJJbp7yMbpdqAFl45B+oqrd4IUJMFGOQvrV6Kwjt7CRLqR fNOdpyQOazZIVKboZEkXHKLndx35ptWGncLayVWDBsn9KdJ9nVACmT7Uuns0xCwlWlJ4BNFx ay2br5pwG6MO1Fnuw9othqW8SgGM7Xx0NLiLrKp6flTGu4g8aKoaR+wGOfrV+SHZGskpjwOq E8ilqaKa6FG5sowiOCrKy8AdQamuI1m05EmbDoMIoXnH+FMuJ5MbY0G1fUc49KiS4Xz90jYX GMc59wKtIzc+pjsnlyYKnj1p0sdsyA4IkPOe1bc1kLmETQAbTjCltxUe5rM1WwaxMPzo+7n5 c8VauLnsZTRLHIW2h+yioXi3FjIqu56kHpV1UQKSCxP0qrNHsYkZBqkRLuUGQ8lR+FI8L5zI CBjNWTtznB455qUuJYCoA3etUJamepbbgcg1MP8AViIffbqfakZSgwpx6kVFExW4Vj60CYoR FkKyAj3rovAiIPGWk9yJx3rAvwPMVl6MK2vAQLeMtHP/AE3Wga3Ps/TT/o6fSrwJxVDTf+Pd PpV9e9bI6R4NOzTRS1aEKM7ic8Ht6U4Y780gpRTQhwIFOzTKWqEODA556UhzvBB47igADoBS jvVoQ4GkyKM+1J+FUgEbkj09qAQBxxS02qQBkU0kUppjED8TVoAY00mlP1pjcd6tECMajbAw MYp7VG1UiWIaYSCOKcaYaZLGmmmlOcetNYmmSNbGKjOKc2cUwmmSMbFRNT3NROTjimA1jUTH ilOQeMdqaxoA+T/FLqniPVcKMm5kB/76NYUnC5Uc/wAq0/FLf8VLqoyCPtUv/oZrKk56fjXz UVodtR+8x0J8wEMenerkbhAQTn1qoFYJkjBPT3p8Ubuu4Yz6U2SizuVwx2Bsc1LbyPImFBUE 7CB6UsFk+7CsCMZ4q5bWIRMSMwJJIAFQ5I1jTl1Et7KJPvjdJk7VPTH1rSttNSOwlvFP3GAU Y6k1s6bY27aZbSSFUkZmYSYycDtXPXk91YQtBJIrRGUsB/WoTbOh8tNXaNDSZjJamyvItkbu ZGc/xADFUdT+zW3y6csgt/757+uKmhv1vp4BJhFhUBfTHUjFF7ewy28kW0RqvyqFHNPqYupf YpSWaDSIZlJNxPLlTnoqjJ/mKY9xvfdKpaVsKNowRipdEtylwp84yIgOFY4C5ppgIvHk2F8t u+UmqbM5yTSsP+zGYepJxtPFammRG2VkmjXdjIy3Ipm+5Gn7ZIgrBshSuQy/zrTWWNrQefEi fJncBz9BWEpOxKijGv2aSyN0M+YzfN256GrMMbTQPuX74DZPPTn/ABpXZZbR4irYAPC/1/Sl sGaNI0mz0OPpUN6AtyOwtUnuJpC5EXG4sduMenvS3NxtDR2sbQlTg/3j9TU0BJtfJAB3nc2O en+TUMUqSiWKSfIyCnGSOemaq4rGZvZ5SJGPzHp71bFtIm8PtZ1wE2jPXmqlnZGa/hh8wR+Z KFEjghRk9zXd+K/Ddz4YhguxIbm1YKjyKAMMfQZ9K1emwowbTlbQ5GSBoIjNJahhwAmeprS0 2+vpp2juU8ncD5aAYGK7LxhrPhy50HT/ALHNE15HtPyAK3A53V5jfeI2uZcSARvGSEdc4A9a cU2OpFQdkzXS51K1RlklEynJIPG1frSW3iL7LKWuZ47i3bCBI/vD1yKz4fENpb2x/wBI824Z cAtH90+571TeCys3jvLe5W+kfIlRm9e444qrdzPU1LnU4mm+VPlbJGOOKtafLbPaziFcGTkZ bjNY91ExtZZTCrKhMYZGwoJBPHc1Qjgu7W2juEcQqeUORzTWq0FqnqbQuJzDLG7FnkPy56gY PFVIRKXIIY45I2nis4TTm6DTFnfOcg1u6Tq4hmkS9jKQAfMQuST70WC5HExtZpHZfLcgr7gV c04RX8iJdSyBFGFxzmk1Z7fVLhfKkEUYHyOIyc5/velW7S2s9LdZ4LuSbeu07gCg9T061Epq Lsy4Q5nbYp6tpEslxA8KMUUYzjt61WvIp44UinZ2JPynJA69K6pbq7vrcLGiQ23GJGl3ZXJO cYHNZmrXMUBkZpEkVQdqZyc+tVGV0E4RWqZiWtrPdqRHghCd4zyKu3VjHHatM42RqdgOMnJ9 faoNPVWxcSSsjBdx2HAbPrT5NT+y6cZC3nM7fLCTx+NWjNMZYTWGlSSRLd4yQNjc9utWr25g kgU7Q7EYVscVymjKJ74SXcHmRA4APT6V10Rt7pliCiO3jOdoGAfaqbsT5GDJb/6YYoCZCeh6 Z9qpSKxdkl3LzjBrqruK0adY4mKgNhSv+NRT2FnLI7s7B8Z4PH1osO5yRt/lPHNVHhKn5Txm uhvbCWCISEqVY8KOTWY8QAy3y575p3KMzLDp9MUwnJwetX5IUAGOD6+tQSRYOBTuIgkJZAD1 Brf8AceMNHA/57isQxnHGK3/AAEGHjDSQR/y3XrQVHc+yNO/490+lX1xVHTv+PdPpV5a3R0i /nTqQU4VaJDp0HH1pw4pKOd3tTQh3pzS0mPalpiFpaTHWlFWhAMUdqB1pDVoBabS9uKSqQCH pTSKcaaatANNMYZqRqYatEkR696a1PamMelUiGMNMc4qQ1GTTJYw0xs546U48Z96a3TpTJGM ajfOeOlSMetRvznt7igRG9RMac4GMHJ96Y2KYiNqiftzUj9eKiagD5H8UEnxHq2QMfa5ef8A gZrOA24/WtTxIVXxFqnc/apfw+c1kyPlu1fOR2R21PiZIrZbDHAq9ZIUJ84gQkZye9ZZfIBz z6VoWtxGLZg5UsecHP4ClJOwoNJ3Z08MWbRHt9pZucL6Cq89zCbXKs2eu0e3vWTpOpfZXkV8 lWBwAcYOKjuojFJvDgo4yAKzVPXU6ZYjmWhrWeo/Z1iBB2qGJJz36YqrqV0bpGdVURLhR7fW sqNmZ8MxGDzn0qQzqD8o/dkYAPP/AOqr5Ve5zuo2rPYEnaKXCjp39a1LeO2niDhl8xiActgi srIAXABBPUVdhijMYwVyexoZmnYnndYHykmRntTo5W3h2beO2OlQXNkkUDSBgXHpk0afuhjk kcxuX4AHepe10DN6zke4ATeFBHOT0qVoY4y0Z3MuOMnODWWtyEVgAenQnJBp0N4wXDjB6jHr Wbi2NOxdg278GMrz9OKlmlSFY5U5G4xnPQGq6z78ghTxyfeqtvC6hwkm5mGQp9R0NZ8l2NSR YTVLiR2WFgAvOxVGcZp92tzCsVw1oyB8MrMhXODx9RVF7eO1uVflZFYHcORXX6d45vZtetJr uBbm2tgyJbxR98YDDrzWvKuhUbPSTOlsLOXxF8PUjWCCzeFixYjO4rz+Ga4K+1m8vrTydUuG lji+5zuVcfSn+NPE1xqN3OYVlt45CN0YcqMr6jpXN6TexPfwxXSvskDRPk8AMMAj3zz+FXGP UdWopNJf8OTC9ty6mfygd3zBwRzUkM+l3N0W2sxQ/cVPvVltaxoXM6yb1bBzjg561Zjtp9Od LuzkEhYAEgA4HfI71TSOdK5V1W0jhQTmExrK5CrnpRMp0wRm3uI2ZwVcoQcexqW8nlurwmWZ HWQYG5BgfT0/CoZLSG2gczup5JUKfWnfuG2xrRNc39rIlu8ZTaFOW4zxVWz0m/nuJbdY03oM nJ6e1QaVf2kJ2PbfMP8AlqWOQfoOlTWGuy21759yZJPmBKggZ57mhK2wN33H6cGsp3kv4HaN TtzjofrXUxy6ZqF0s7FYkt+ZA/RvT9a57xN4iTUZfKso1hsRhwrDJ3fWsC7vfNLCNNo43HPW mlcWzO38TvY2M0McFtFKZo+ShwcdsYp3hmWK4vordbaSFYstsdtwYHrkGuZ03TNR1QB7S2bb gYkZtv5Z61rQwT+F9VhWcm7WXn7xUI3rUSgmUpNHb30kcdr5MQwFGMY7V55qF+gupYigkbJC ueBXVajPNcRSzWl6rLjbhOgNc7BDb3MM7lxPqcQ3IrjA47e9NCeoxryGytfJmBZsYEq9Poai tJre9heBmQSleAKzze/aJWjcZRjjntzVFIzZ3qtiQbHyMDrVpEmtFebLVLdlQTRMV46kZ6mt G5njsbRVmQtI+AE579zWDcyy2kwnLGGZvmQFQWPufb2q3JKdQt1Mj7pSOSe59aTV3cResrjE bRFS8jcDnGKs6QjfaGhnB8zPI9Pc1gRboXImdgVBO4KTzW74anS6s55JpCsgzkEjc+B71TbE jS1i80+0hCSNlgOmMk/SuXurmEvwmE6gGtW90mWa2WYlTuOBH3H5Csu4tGt4k81ANwwPbB6U blxZWeSJydowMVXfnsSPXFDADoCD2pzFicKzEAetAXIGXDZya3vAin/hMNIz/wA9xWOuZGwx +761u+A3A8Y6Wu3cDOuDRccdz7C08f6On0q4BVWwH7hfpVwDiulHUFOopRVokKUUuKUU0ISl op1UIQUUtFUgEAxnknNBGRg04CkwatCGgYpKfimkVSAbTTin4NNxVoBhAycdaa2KewpjCrRJ G2KY1PaozTIY01HtC9BjNSHmo2FMljGpjdKe3SomBzkn9aZIjdKjansKjYUxEb1E1SNmomoE MeoWqV84qFulAHyJ4mkb/hItVzwTdS5/76NZnJ6DNaviZD/wkuqcdbqXr/vmq32pEgEZiG8c bs186tkdsl7zuVNny5PBHUHrSspXn070jyNK+5+TSFyRg4xVECq/zVYE7jarH5R0qlnnpUqN kHkcetDROpdR/wB7uGPY+lQTu5mO9gfp0p0bxoivuJkzymOMUstwsjkgbeeBjpSQO4kLZcKc +2KnlkdWXGPSqjMU+7tOeeRUhmLhGOAw60WEakc0bplnO7HIHbtSOMkGLnAxuHOKzRvfOPTF LGJBJ8u7d7UuUDWtrUsd5nGTx06Voiz3jAlxL0GV+9UFtpGphEla3YRvyrHjP+etWGgmhJWU uuMjnr/n8ayk7vc05J9UQQ8SlXkymOo7mr8RiYk7SAVwDnvVK3hi1A7YY2hkhGCDklj34NVb WRrWVi+dy9iccfSlvsQ1Y1XWFXDSqWQ9GPf8K1/Dms23hu9m1OK0a5RYvLKZxtyR82SDXJaj dPcTKRHiJTgHqTVOSWSPchPyycYFNRvuOMnF3Ro+KdZi1rU7m+MQhaVwdgJAQY/Wm21mjWiG R1XJBQjqfp71mrJZm7nN1C7hsBNpxkj/ABrsdMjh1SznS1RfPhAUwnHyZ9/zFW3axUYupLzM e/txNMZoiHdhlkdsZPeqVmLgpIIyqqzEFMfdPP8AQV1Nl4P1e6lYxwLGp5BMm3FaEHw/1K1c yXuoweUBltqs7fQVHOlpcfsZvocZbWb6nHeCBUAtIfNkzwTjr1qx4atUkOZ9L8yxfh55B0/3 TXQXX2PSrN9L0lzbz38gjmu7hdrFfYdhmpbDw7qtpBc2kl7bmyC7o0QFt3ckUnPQJU+Xbcks rTRrDSp5IvJkRt25ioZyD0A9K5yHw3DJYm9nnMVqgyS64L//AF6FnikDW+oKlts42cqx98Vl XWoTXVwY7feIlBQckjGeuO1EVLuZN3ZmzLG7SbCwjJGzPUDOKv8A9nJHHHsKyyuM+uB/jQ9h Itj57p8rZGT3qnbXLwkRCTavTsK2vfYk9R0PU7WLSbWPyySiheRgA+mareMrFJrRJo4mO8g8 881xOjax9k1e3VYxPCpOVdiBn1r0C58QRXLpD9ikBYbo/mGP/wBVRJNFbo522tl0y38t7ra7 EN5ZOcH/ACapLZJJcC7E7RRxZcuvb8K0taASWMC2AkkUBVXv7/SqNylyum+W5wiHJwvQc/nS VyDGv3t4dhhcls43EfeHPOPyp738SQiTDrJGcbkOM1HbwwtbeZcSKxcYX1yO1Ur+GSR41jwI wMEscAGtI66BYRWs7yXdM10jlvvswf8AMYFai402QmRFlt5BmOVD90Dr+PPSs9LJ4D85Gz1V sg1bt0MVzLZ3MQWGUANjn6EfpVMG7moNStr62eKG3kEP8LOoHPeotJkitRcEKpmBHzN0UVYm tY0tESB91uFx8ueKy5pvIBSBSD3PrUrUlnV2d5gtLcSRCFUG0FgPmNcvqt7Je3TblKIrHYoH qaRrqWNAjsCoHIJyc1T80vMAIyI++OKpIBWXacMVDenXH+FI0SY+Vnb2HAq1JAXIe3HyHjnt THRmOF4pjKhGCfl2sPXmtrwGM+MNJzj/AI+F6Vm7NyqshAPTOK2PA8e3xjpIByPtA6Urlrc+ w7AfuE+lXAMVWsB+4T6VbArpR1CU6lxS4q0SIKX8KWlApoTGrkqNwxTqXFLiqExtLTiKjOd+ O/aqQDhSUuGBHp3pce1WhDcU0ipCPam4qkAwimmntTBkgHFWgGt9aYwqRqYwq0SROKjYVI1R tTIZGeKY30qQ1G1MljGqMin/ADbfmxn2phzTJGNUTVK1RN160xEUgyDkVGae2ajagRG/I71C 1TNULZoA+RfE0jf8JHqgycC6lA/77NZTNnnH/wBetbxPj/hJNVz/AM/Uv/oZrMKL2PPpXz0d jsn8TI8mnmJwisR8p6GneVnp1ohk2MwChieOe1MgYsRIJOeKs28EcjIBuGexbr70L9z5sZpA zRTK6ttYcgjtSuCNhdGWKT94Ny8bSQcPk84+la974asYmkSGQZRMqSTlsgEdsd//ANVUbK/e Qgu25scYq+sriNV8zIGUC+nFYty3ubWjYx30eKNrfLsVZyrnb938ali0+1e3aMyAvgFWHUHp 0q9qYVYIwxxH5q7se4pZhbW1uDJHLEAfknOdrfSpUm0ZJFBtMYWv+jbXuOrBuoAyataNYG+u Ut/MghkJzukbaPwNaOnhYp4JINs6yIdzDkofen32jRy3SsiLGshDBk/hFLnu+Vm1OCb2PSbU aRpOlRi4v/PaRcM5OVYgYOB+GKxdWl06GAS3Dwx256Mccn8657VLeS/dAkp2oNigdNgGMY6e 9cfrtvFa3n2I3Ui7ADhySmT7dqzhS5nuehWxHLHRHW2l5aX9/LDCrC3jRpRJGytyBz0Oce1Z Gq6coaS5BxboAxbB79vWn/D62ne+uHlETW5iaMYG0OTxwRg1091Es13Z6XBCJI5pCkgPO1QO vPvTa9nLQ4JL2tr9TlYbVLqaK20hvtsshICxkBhj1yOnvxVy98OnTf8ARolXUdVI3vGGBWH6 46kEjk4GK6HWjYeCNGa20oKuoXed8/dEB5I/kK86Gp3MrJa2ZZI5G+5nLSt/ec9/X0rWKcld bEuMYaPc0l0B59Sgto5VnuUAXZCQFVu43Hqc56ce9dXb2mmeDkacj7fqz/KYlb93Ef8AaPc/ 54rmJtZHh5EggPmX7cyTHqgPUD3P6CooPEdpsIlRjk9DzTak15F03BO/U2r/AMf6kz4fCJ/c jyuKpyeO7w4EIYMeM5NR2WoaPeM7TyrCF5IYYz9Kjv8AVtItw0dunnE8qyrxn0pKK/lKcnb4 tDf0a8mv9Elm1+yjvUEhImcoCihScAk56ikg8R2UOlx3OiStLffdNtLyUXvn29xUljZS2WmS XtwJPKkQbIWQMAzDHGe3fms+TwcYtcsxbTrBb3KHeNw3ArjcKz91vUU6craIwdau7jUJpNSm X5wQoUJkL+NReH9bNhK8U9klwJBywOG59DWt4wlGnO0Fsy+SowFyCfrUXhmDRfMW8uZpFuFI kjQHgn3rbTl1RzuDizYsbnS9V0trdrgWku9vKilPO49smvO9RglgvpYJUAkViCFORXo/iO30 a6+z6jfyS20aqSYvLKvMw6YP9a4p4ItQnll88QRFjtVjubHvRSfUlxLXhLw9LqG+5eSKKCBg rtJnknsAOprrrzRFjt5H+2iMv1ZQRx6Dr+hqnottFpFon2mYuo5S2xjJP8TVHPc6lqt0YfKL q5KxgcY+vtiiUm3dDcdCKwXzWmWK6ka3gX5p3THQfdXrn/61Upy8/wA3EThSSpzhvXj+ldtD aWumW6ExhjANiRL1kdhyT/noBXG69fvHNIhVOPmIU5App32MpKxHY2cMemzXMwG+HICEdDjH 8zTLC1gvrSQ3EQ8yI8HeFwPXBPNbK29rHHDIXDi5MbsvVSMDP61lWNq1xqVykMhXypcMo6FC efyprUSlZ3I74w2C7EhUzFRuJzz+H+elSTMjafDcE/6WykYBxwOMAdPTiopHS8lW6gG5t5j2 4zkDp+lO8hLxEtJd1vKjFkJXhiQOPrxVJEkQu4ltY33MV3HKZ5z7Gs+5SVLgtI7CE8hgMj2q cvEls0MuElWT94zLnBqT7VqVpEVQwzw9cIoII+lVYCvHbW8kwfzJmB7bPlz9TjFXI57CKMxt G4ZThlLDj+dVYrmK8yCrRyH+6OB+FRahAy3VvIoUZXnuGIo3AuSS2bAxhZBg/wALjOT7VDIw iYKC5XrnHNUNq3Rbau2brjs3/wBerdtKSmyU544J/wAaYbDnl88g+aA46AjGR/KtzwMD/wAJ dpe5znz14xxWEMI43gg46461u+B5U/4S/SlGebhetTY0jufYViP3CfSrYFV7IfuE+lWgK6kd QmKXFOxRweM81aEIKcBS4pQOapEiYoxTsUuKYho5HSkwPSn4oAq0Aziin4pMcVSEM/CkNPxT apDGH6U01IRTCKtCGNUbVK1MNWiSFvrUb9qlao27VSIZE1RtUrVG1BJE1MapGqNqZJG30qNq kbFRsKYiFqibntUr9OKib9aBETVE2KlaomoA+RfE3/Iy6r/19S/+hms0dc1o+Jv+Ri1Xn/l6 l/8AQzWYASQPWvno7HZP4mDMSeaFOcADn1p/yhWDAE9mFBTCKe7UyBxf5BzwKXcGGOv071J9 mYRgsCoIyMjrTfLKSbR69aV0DLNpObdS2OTwP8avQXO6ZW+bbnJBOayiAz4B4HAq5bFYwC2S eeBUNCudFcTW+0iaHz4wAfLDY3EdBn+lZ11ci4HkTl3Cr8kSMSEPoOucVD5xlwWJAVSAD/jT NGuYra/EjndjoSeKiMLI0hLoaVqt7baUZ0jlhSIgsuzGQa17zURDDbF3IhYcZPAp934ghaGN IFiGQQwx1yD1/SufuZ1ntjHKAUGAMdBUuF2maT5abXKzqJr+1tYxILmINsBC5BJJGa5QWUuq 3AuJir4Lb2c4BIPQmkubUm+tLgkRQNCgMpGcY+XgdyccV2+iyWNhbXE1zayvDCzuka/Lkdyc 9TTi+RplOXtLX2M/QEmhlmvGTzhawrawRQ872PPb8K6XT7ix0qO1vb1Xe8m3oqhsCNRy7k+w q7Fc6XLb21vp9wtjNOfO2uo3EH7wXsDzjNVNaj0T7L9hu7ieynlUhHlIZQM9z2B4rOcuaWw7 cuqZ5z8Q9ck1LV2VP+PYKjxhkAIBUHHH171R0UjT7CfVpxumP7q3Dc5bufoKsav4cv4dTihu lBUqAs6HKSDsQfpWoNdttMEdtcaJBfaZD+58xwQS38WG6Zre6soxMXrJ8xwkrtLIzyMWdjkk 9SaTl+uK7fxB4f03UtNfWPCjMYkGbizY5eL3HtXEoCT05rWMk0RKNhqZVuPoc1dtJRBOJNuU yCpKbsEVWkXn0PcVOkuYQGdto4K5/Wm9RLTU9H1LxVY+INCmlNrJFe2uPLQMShHqcfyrg4Lu 4ur7O1WfBIBZgBkc9+KhW1mEbMqtt7HsfT61oaZBJBesxcW7LGSSy559MVioxhexpOpKo02U EtrieKdtrOsa5ZweB+NbFt4hi0/RYbCztEW5Vt0k5IYtz9OKseILiKPRLazxukZFd2jwFLZ6 nHXg4xXOtYyLZx3IU7HcjPYDPH9atWmtSZLleh0/ibxlHrsdpBLZ7/JQDDHaC/c5HOPyre0e 0SOxjvDHax7x8kawBwD67ie1cR4f0GfUrtWkDQ2nJaUg9PQV6vbvp0FjbwwW8ty6R7VU/KuB 1rKpyxXLEcEpO8jnpYZ7iT7Sz28+DyHh2j64zV+w3xSxssw2jL+Wq9T2BI6Crd7cPbr+6W1t k/55opZjx+VU729WPS5bp0VZZD5aFhtzgck47Vne5ErLYqXt493LJb8CZ1O+WPj5urf59q46 ZIpJLry2LCNeBnqv/wCvFbmj3QuL/YyoHmR1VlGAOD0rnY7gWV6ZCg2likinqR3reCtoZPUt aU09wlm8BLGNyjg+nUZ/A/pVvTLsw6/fB1+YEkA9x0P86z4WGnNdQo2UnceWwPBXrn+VMv7s pq4dgMnG1x156g+1Va4iaeL7JLdpbkrsKyoM5yByD+Rq9PexXscM0MpRmXa6PgqzDpn0PvVO /uLeF7eSZG3Y2Fl6/j68VnTL5e9IMSQE5UjqKFqBq6nNDM0iXaCNpVDCQD5l7YPqM1ltG8M7 hLjA7HkfiDTppWlsInk+Z0zGcj8RVRIi6l1b5R95T2PtVoRbiuJnIW6VZcdJEYBwP61a8ktG y/62AnIIHzIfXFYqSkSeXwwI4z61ctnuJQWgIJA6ZxihoGQ+XJFOyqkhfOPkFak1o9vGJpgq rLzs/iU+uO1V1uJklilkAMh5yG2n6Zq+moC8WSGJVhZv4du7P1JouBRMvksqP06cnNbvgJRL 4y0sKuNs6nrxXMyku8ZIJbO3pXe+DrZNP8S6RHkC4eVPMQnkfSpbsVBan1lZj9wn0q0B1qG0 H7lfpVjHWutHYGKXFKBTsVSEMxTgKXHSlxVIliYoxTsUuOKaENxRjk0gb5yjDB6j3p/erQDK TFSY65ppFUhDMU0rznJ+lSEUhFWgIyKYalIphFWgI2qNhUrCmMKtEkLdajbtUrgZzUbDpTIZ E2OKibFTMKiamSRNUb4qUio2oJImA59ajYCpXFRMOaYiFxULCpX4qNqBELAVEwqZhULCgD5E 8Tj/AIqLU/8Ar5l/9DNZ5OFxnI9K0fEoLeItUP8A09Sf+hGs3gdsn1r55bI7Z/EwzngdKkYj d8zYGMD1oj+cgNgCrEUMLsYzKm44CljgD6mhsgntJUNuUZ+nK7v88VWllJfCgZ6jaM5qLaqk gHGPxFWrSQR3KSsgYqc5BqbW1C9xsT/NiUMGHYirkccci54GOaZdyCfUHucnnsaVtpH3cAcD FTuTK19Ahl8u6REAwxwwz0zVkWkbSqhjKt/eB6jPWs8N9nkDpz8wODzV2TUmlct5Yy2Pwoaf QaY2bT1glZXYsoOOvNW0jEkMZiVdpXB+tQTypcLuZCpBxkd6RJ/KUfIViGQOOtLVoptFmKZ2 8sOvEZOMf5xXTTTNdQwyuoRWIDMpyxIxj27Vzdpc2m1gysMKQDnue9XLd44rQSxs25BtCuwz 9cVnNNu4RbVzZjsbe8vbW+vJ5I32MFHUKQTjgc9Kbr1/pEuntaX93cSRn5Y3EHzRt6g5yR7V nWN9J5SKBuZN2Se4PajVLazvSv2jEbgcLuAP1x3ofxK4+e+xq+G2t4tJe2OordWQyyNKhUxH plc9K5TV9UuoWFtC0culr8qxAhkf1Jx/EeuetdDJokz6Y2n6RJHOrso84sFGzrn8arnwlJZ3 Pl20kxnCbpLeWEsjewYcU4yim5FOMrHJ2N9d6NfrdWJeIZ+6w4IP8LeoqPVZLee8NxZxmFZf naIj7h7gHuPSuz8Q2c96UleNDuUjysDfx02gdal8H+Cpp7yOXWrSQQSxt5SucHII5I7DFaxq Ra5iOVvRHN+HdBu9UmjnWBvIBO524U4GcZPWnx+Ddee5CxabMQTw20bfz6V7jo/2C4tHs/L8 hIMhFK7QccZFXY3jChU3F4zkj1X1H+e1QqrcrI1jSTPnm6sb7TJ/IlV1mHytGAeRnp7/AIVc srCe8uYk+xyyOdyrCvys56k9OBXtOsW3mTRyRLFkSB97LnA789uK566u3XVRfKqlo22oIhub APB/HI4qpysDpWe5Q1rT9We1ktWS1tYmt0xbI4kkCr2AOMnio4rKzufD0FtFabTCyKfM5OQo zx0zkmt7WdRtd1rdCOX7au1mZh0BIBBA9qnvCDaxP5PkByzfKOc+p/GufZal1LNuzOPksZdR 1ZYoxttoQAkSHAyDkFj/AE69elT6pb3tksIREnEYwuCQE+gPU+5zW9BbvZrsgT7O553zdXzy So6n69KwtWvrWIzJDeJdXMf3nk3BQfQcYp3bZi0oor22xbe7vLwvM0AAWMnI3noPfmsHUrqS WCMTvyFYDB4yeuKu3M1x/ZTBV8qKSUklRwQAMVi3DLLa4jbcsRBxt9fetILqzGoU4dQntzAL bIZDu3Hv9aTV1SedroNtjk+YADOG7ik8uQP+7xk5GT2qOUIGkg3MY+MnPfvW3W6M0yG3AlEa QiSQ7s428L9KWdJPMkkZP9SMYPY9qdLdzxR+RGPIiH8KHBP1PeoZZylusYOfMyxz16YFWhii Y3VgVcZeM5Bz1FW3kiwLqOERDGyNccD1Y0+z0iRLSG5uJYoVmPyq2ckevFLuSfVY7eIqtuQc Eg4YY/8ArUtBEFpcq1vcRSqZVxuG88n/ADmoxNGg2bCoPJFMtWxPIzbSGJB+lRSOp3ySAZHC KByT707BYt29rELsor5B/eID61mqZLS4JK8g8g9DVqGVxCvB352r/hVsoEVPtJEhI6gYKfX1 phcYbgfJMMfP8uCOFFSafpc1xOiW0wVpDgFuBVS5jEY2KGGecEYxV2znJMUaqRIp7GgEddon gy5tnE+pPNJboVZBa4LFs+p+765rQSN7fx/okMm2ZftKvBPvBJjPbOOee9dV8MBPLZ3LXEzx wMQoUjLt649q4HRrGWy+JunW8hkZYr3aokOdq5OAKhr3rnRKKik0j7DtR+5X6VZAqK1X9yv0 qcCutGrEx7UuKdijFWhCYpQKcRQBTRLExRinYpcYqhDCPajHtT8UYqkAzFNxUmDSVaERkU3H vUpphpoCNhxTCKlNMarQETA1GwqVqY1WiSButRuKnaomqkQyEj2qI8jkY+tTtUbUyWQNmo2q ZqjamSyB/pUJUAlsc+tWG6VG1Aiu1RN1qdunaompiIGqJqnaoWpAfIniMkeIdUx0N1Ln/vs1 SRdwOOpGQaveJAf+Eh1LH/PzL/6GaqR/KvP1B9K+dWx2T+JkLqeMCmhMdW59qsqqSsSOD+lP MOCFJHI4OKLkFQqRnDDH86dCDuycjFTPGrfcXkjoD3pYV+QhR82epNO4E8aNt3SEgfrSokpD bM4HP0FMXzF5cZPvV2BPOgeJGYE8lfWs2JK5UEu5WGMlh1FS29pJKoaNQ5QjjHUVFHaslxsj bHYsf5VOjSW8ihMg84OeGxTfkM1E0+PyJGOFdcFVx15557dqjkimEK4jCKrdR3z2NJYXxDGO UEK5DN9BW1ZaoFkI8mKQNywkXNYNyi9R6GdHayTyCMzFG2q3fOc4I/rTtTjhtmZnVB5L4ZY8 kyV1BttP1hRLYym11PvG33ZD3KnsfauZFvLPfyR3ASAA4LTNtGfTnqaad2NppDrLZJcjaMRu FYAAjrVnUnt7i7DbShhQhh1B46j0qx9hVDHJBeW7IvUFtv5Vl3cE8MLXMo3b5SjJ7Dnr71K1 dybWHRbXvtPSR2QKpkZCuR/s8HjjFdboHiGbeI7t/NDPiNlwdtclNqMTQ7ERnZ1wAF3FRnPW t7w/bW9vbxSOeuGJYYpSWl2jXmt7qZtx6v8AZdaigmKsnGSBn/8AVWr4l8SnSbQPYxxzSu2x AwLFM98DqK5+4maPdJgy25PyzwjO0f7XpVGTV7O71KOK7SUF4zEk8XOeRz7fzojFLoPna0L2 m3Gow6mYtRuYsy/vWkTgZ9MH8K3I9WltdQInMckju3kiPunGVb0PesnUrJ49uy1eSIgDzTIG AOepxz+YqKSzlg1z7QJ0KkCXy9oIBC4z7nNXGorj5nE3tW1aKGVdPtvmuHxIwbny0Jrn7qzk m1ORIogdi732cEnPyjPpgDj2qxp5uG+0X1yEaR3J3beijt+dbsStFo93fSt9lu7hNwwoJQAY A9zj+dNy0Fzc5gIghf8A0hHnuJG2omAVPTJII9egrT065I0xHCmS6LsV8w8Dpyf8Oa5nQIri 5uVmhknklaUEyXC7AqjknGTz7e1dRBpr3EsLo+y0hYvkHliD6fnWM97BF31Iby3v74tB532e 5lUFyCckD1Pfr0rC1rwZqYmO3yZYiAzFPlx+ddZaxiG9lluC4DszIzkAAYXp+VPTWWdHmILB SN645AHtUqo4bDaV7s4TU7N9Oto43ACwkgo2OmaxraATW92FCrAvzkBRzgdPzrodduYneW8Z My4KpBMuQQe59xXLWdwIBc286tmVegI4710Qbauc1RWdzPZgsQlKbdp4UngGq9qvErEqSVJA PPQ1bmMUjkMpYAncAD8vuakS1kaWTyQJEEe1cDk56YFbJmZk6lMJmydqyEc4GATRb2kk8fnM hEMQ2s+e/atPTtMnu3jeKxkl2OfNB6YqezQ6fPdWl7sjhmPAbjHof6Vd0MxZLi4liLyuzbUK rnt/kVZYOqROBkxwbV57n/8AWaYDv1GSOX7oVsAD2pxePYXOSMBRR0EzKJKpjJ3E80ogb7Qi yfd6nB6DvTjgSEnOFbaPU1tppflTAHdIroGAI5Oewpt2GV4bHy4VmM6oSQ6gnn24qlqdx5ko bDLKCd4JyM5rWfR9SmmnTywz9FBHJx/Co602fT5AWS6SSK7IGQU+X8fQ1KqRbtcHFrVopWkk l7MPtMuyJsBmC5IA9K2LU2omCW5DBBuErDaT6is61tYYY3Ekm4E4546elXdOgEtr8y4jJI+v uDTbXQls6/UPGlwtpYx6RGIPJUq0anhz6/zqnpGuS618QdClmjiiYTRgsgwXPqx71zOmoqNI JC+1G+96Vr+EVifx9ozwbjm4UkEdKL3Zr7Rydj7Utf8AUr9KnFR2w/cr9Klddw46jmupHSxa UkDHucUtLirQhPSjvTwKOM9apEsbSmnUuBTEM7UU/ApPWqAZSGnjFNNUIYfpTcVIaaRTQyI0 1qkIphFWhETVG1TOKicetWiSJqjYVK1RtVohkRFRMKmbpUTdaZLIWFRMKmaomFMkiYcVEwqZ 6ibNAiF6hapnqJqYiJqgap2qFunNAHyN4iIPiHUgB1uZf/QjVF3JULgAD9at+JDjxBqeOpuZ f/QjVDadoOetfOJaHbPdlm3Xc2Fxu61MoDsAx4BqvGfLA2jJP8X9KerEMT1BpGZfihhSOSRy d2cIuaVoY3BGzCKp2+vt+tUDKze6j0q0H+Xqd3oTxUO4c1hod3kxgA9MY4NWo4iiMeVbqevF MYCNAflEnUbTkVOJXkmJUZ3j8jSbASC4SPT5reRSztJvX2OMGoZpUuEVWjVXXnIHBqe/tvJV HLeaxBL4P3fx6VWVhlY5QAT3xkijTcJXGW0TfbEQsfnPUGta4i8iQbyqsAMn1rJfdHKGRi+0 5DVNf3pkCyNguBg+tDTbEahV2hUq4GwZUZwfrmlu7175YDd4knUbRIOuPf396yBL9ojI37cA HJNPsJCs37xiTGCw7g4pcth36F/VGEcMsa4O1QfoaybS8mWGSCOVlRzuOD1x2qY3YMmW5yOQ akVYpv3ioAQCQFXqapLlWpLY+KO4+X7ZGY4pAGXB+9mt+3VhZLDAWAznL4IVfwrJuLmJpNl0 OUAjH+zgYq5MYmtUhgL4JGVzjFZzu7D2LVlcYA864PXyygUkMD2Ip82lQukzRSKYx83lfzx6 GqNn9nsIpRMztIWBVVIOD+dM1G5iM25XeGZsMAW6fl60JO409DvtO1USaXGA53BQjZIJ46E+ 9WIrGG9Zj5e2UHLk8ZwOufw6VyPh77Lc3jMpO91CTbQfl9GxWreXN3Dqk0BAidF2kBjl/TFZ yjZuxrdtJs7S1sYBDbyQFTbMpDbwG+Yc5/nVbUdZkgs1FlmIEZEfAd/9ommafeyr4XnVxsm2 +bEFHUD72Pzrh7szTx4lkLSnPllj90HqD9KUVcuT5VodXaXGpaiQk17EnmMQu9wWA9BjvT9S uGiVUhu0aJPkZmJy5HWue0/QNRdYHs5Ioyg/1krlfm6ccAcVq363VjYy2sYW6dPmMhTcqnvg mk/ISu1qOvbqLUoVe58xLeON0xGdoBBGMHv2FYNqb3y5ZLeZ5VDFSpfbu98elU7S5v7iX7Eh hDyHK4c429So647dKjivr2GVrea1kjIJIjKDAUnu1ChqZyl2EvlubiRUcLukyGD8n61WsvDU kjBhNFJvBUbmxg/StyS4jZF8iOITIMq7urMKrCZ2VnDgzZ49/wAq0UmlZGLKNz4Ye3BZ4Ebd 8oJbgH60khstIj33EJlvNuMlSIx+XWtiC9nkto2uY1+6VDbwC4/3TT9RjiGnIHUTxuRksRnr 2qlzdSbnKXmqXdzas9tILe3RB+5j+VFP0FR6xAmq6RFd2ij7Rbrtuogc8dnHt6+lXpGS2t0S 2RfKzyQMhsdM9jVAG9s2GoQjy4WOVGMdyCCPTrWifYaZibXKRu+AwzznrgU+N1jeEAbgzkNj tWtc2tvI8ksS7UUFgp5Ge4/CrawWMLQiS3XLfMWLbgDjOa0voJnJyJ/pqjHyRn9a072eWaOM KxSTaAD6CodYtktJmMMiyI7nn3qW4upLkfZYIkUBecDn1qt9RdQs7+40uYrBMBIrc4bO8VX1 e9utUuBN82zG0KrEgVb0547GxufPto7p542RGZBuiOOCDTJtEltoVZr2JRIvoV+buuTWfuKd 2tTZuXJa+hmrcXNvhfmC8AkDjFbYu9iocdskZBA+lULNzC5ivLpi2dqRKN2ff0xTLiExOJWK rngp2q203YycbJMvrgpJI/yq3JGeDW74AuY5fGGkR7DtFyrBh1zXLtcQvCUlVynH3DWt4CYR eO9EFtLmM3CdetNIUdz7ltx+5X6VLzuxjj1plqP3K/SpgOtdaO0MZpcU4DrRiqQhMe1LinYo AqkSxuBS44pSnTmhVILZORnimITFJjrSkPnK4I9zQuSSDwRTuA3HtTSKkxSEcU7gRnFMIFSk UxhVJgRtiozUpFMIq0Iiao3qZhUTCrRJCaY9SuKiYVoiGRkVE1SsKjYdKol7kDVGw4qVhx1q Nh70ySJqhbrUzComHvQSQPUTVM+ahYGgCJqhbFTNmomzQB8i+IYmGvak3GDdS4P/AAI1Exi+ zIjEbs5+WpvERLeINSAzj7TJx/wI1HBAZBkuhCDhS21h9BXzXRXO9q8mkQtIqOVi5GQRkUom HncLj0pVMefm3M/TGAMfU06KJVIMrEbiCMANxTJYpiQlWUEgnBHoag2EzbZCc9asziWN8EBE B3Hj+lV7h3eTeXJBA6+3ShENWJTIGwKvL+4jXy5truOh7CqFpGkjl2yEHJ56VOjo8rSzYKZH Geg9KmSEkWo508opKilCefU/jVWWWPzmfG5CMDParhMVxH+5g2Zzghieg96rSQ7EdV52/Ljr SVht2Ir2VWlUxqqh1Hyr0FWrfSL29WRrWNXSIDzHLABc9jVJdiTfOCSq8Y7Gui8OTwWVuZp5 XLBgQqcnPuCMEUSbitCoJSl7xi6lpd5ZIHljIiPG8crn0zVa3eRULhjheBz0rp9b199S0/7D sQx7gynZgk59un+elYE9sIfJhUkseWUjGDTi21aQTUU7wegihfIeRkCkcg+tQpcskg3Asp7H 0rRkkiQRpLCrkLgAk96oyRxQuwn3Dj5VAzn2PpTVupnylxl3X08hIWPcTuPvUyTmUGOAYzj5 u9ZU960yqkigIg+ULUsFyqoDsYAf7VJx7ila+hNci4tmLBDIoP3gc1TlcSDzSSWz0atWG6iy UlR9r8cng/yrF1BNk52g4zxg9B2qo6iNzw/czabcW9zbnKO+xh9f4TXomINXkgurosk8Uh4A 5kQ8jP06VwPhuzvIGaSWMNayqDJ5w2hD1Vs/X0r0Pw9Zo323UJhmKCGQFFGATk9D9DWFW3Nd HRBO1i0J2nuraA7Y48PlS3JQqeaxtO0t7SNpxLE0235Wf5UHofxp9uIvtCXszfZYoWBLCT5X Ho2abJc2bJBdy3nmJt+ZUQ7H5I6nHSs0uhT1Wo2/a5nZFl1INPvG9YAcL6AVoX+qrE0RWeQR FcPEq7gc/wCyfesuSxs72GW5tLmaziUqcupZcDkhBwc0xfEGnWGoRxtYvJtXYtxKN0hz32jg fSqtfYnVPclMsFxGLmG1ubcIRiRFAGM9QO3NVdTuI57mWScOyEFY4RwzH+8PWtvTbbVNQvS8 M4NgeSjAIB+AH6V0sOi2kDNJNGmAM7lGDTjDW7NIUZTPNf8AhFNQ1FjLp8QQRpko7/MR6Cna THDaybpY3S4jYLJE4+6a9dh8u3iElsioSMKVH9a4/wASaKbi8uNSsFH2548FSeJMd+nWtnsT Vw1leO5x3ieOBnE9okkUqkZyMAj2rmp9Ru1hZGBaINuXPY/Wr2pajeBo4NQidlBBLlNm04wR 1Ppmqsl201pNAgXIPyEjPHrmhLucTRHp15uL+aC+4jCk8D3Fal1KtzpsIVtpj3cMeOa5S0uA k5EpKOP4u35AVvw23nWsc6THDsFdUXJGOefr/SqcepSXQdEUFtJbSPmQjdnPfFMs7hfsBMhJ VSCSfQdhVCVJftKPAQzzHbgetT2kQikmtrjmOFi0h7dMDP50bIpK469it7wW8+dhJyw68Vkr LGl6Xty23vuPLVNJIXWXyzmIH5cDGBUEEbRSrJtJB+n6VaRB2FvpEA0GW4vL4RxspHlkDhuo /GuXudMubiNZfNL4GAnJIrSu9Ujm0/7NEJX2YOZTgKcdeOf1qnbSXM0caRMWfP8AH91R6k5r CnCcW5SZvOalaMUZ9mWidfMAzu+Unqp9/atBlhu3CykqQM7R1J9KW9ls2QxRq7Ogwz4xvb2H pSW8f2eZ96rLIqgksM9fStXK5k4PfsUpbaWFj8hHcBhzit/4cxmTxpopAAxdJ+PNYsVzm8Ml 2xx6Y6V1PgZkPjbRTEF2m6Tp9arUlaM+04/PXy1jUMp5LE9BV0DimW4/dL9KmFdaO1hijHNO pe9UiRCOaTacjmn0uKZLI8E9qdilI96UimIYQe1IV5z6U+jFFwI8U0g1LjrTT9aaYEZFMIqU 0w+1WmBDtwxPrTWqXBwM9famGrTAhf6VG1TuKjarTIZA30qJ6naonFaIhkTfSomqZqjYVaJZ A9RNjFTMKjYUySB+lRN3qdxxUTd6CSu9ROOlTOKhYUwIWqJqmYVC/SkB8ia2y/8ACQ6iHXcP tMnf/aNVHdN+UXIHJDHrVjxAf+J9qJHX7TJ/6EapRhpScnoOpNfNpaXO6W7HhWDZKKVY425r Tt3itzukj2huw5wKylOxgU6+tXrOUJulRlWRBkBlzn6GiSuJSsyS+uVnjC4AUdO5rOKFmVUb fnpiluJDJKznA3HJwMVPEws4yxA85vun+6PX607WWhPxO7JYvJEJg3iGXdliR19qJYVKF/MU rnGMVSYH775PPXvT3cEptUjI5HvSsJu5dgaGMoWkZh12jj8Ksz3MDOVjUIW6gGs4nLZCAHpx 3oiidplCD5u1Ty9WTfoTJC08jlMhRyxAzgUhDg4PyL71cSbyh5MfOTlyOpP+FGp7XgRtxPOM YH/66E9QK8M+x1EGA2chj1q7PC8z+ZO8cMeNoOQWbA7CqdlGpkXhh2ypqxOJYUkWVfMjzgb1 +bHrnrQ9yoNdS60SNbn7OqqmOZWILEY/Sq1ppT3F35AJeU/xY3Lj1zUETlyBG0iDHIxnFaVl qc1gsiW8oUkYIHUilqtjRWesitqWkQ2Z2ozSSpkP8vArMVVAbaqu4HTPArRvdQeUrtXapHzH +9TIQ6RYT7rfeI9PShN21MpNN6GXPLM4JkUFe2OgqRbd72a386QRhxhCRwQO/wCHrVptMNwQ YE/eHoOzGtyfwZqrQ/a55IkyozGvHy+g9Ku6Q4QctkVbbWpbRTpkNxFc6b91o3B5PdhxxXpv g2cSWNnGoDW0sUguFbndjgf0rgtEsoFEjNZR7U+Z5JhgZ7An07n1rsvh7cXkl1e3F7cLPEkZ wAhRQMjGBgcYB6Vzzs9UawvdXMW9S5v9dGnRRpHb3RARuCg56Z7fzqS/tTp19Pp91EsogceW mOGGOv48UnieZtH1Vho0Yka8bIdgDswemPWtbxNq0NnpcWpXEKy6girG+05wT0J/z3pJN2sD tr3MPU73yYxJqEEW1UJih5G0D0xVZPF0EVsqDSrTG0Ahhk5+tcneajNeXjTzOXeQYyf5ewqF lOzcTubvWygupkpvodpo3iZ7a+wjO1rJzGp/gPoa7ix8Txyy7J9qEDIJP6V4jby+XnGTzng4 wa6C3undVbBKjoM9Kvlsb06jtY9ej1m0mYAkjPfoKsFkZCYyPUGvM1nl8kM27ymX5iOCp9ad Fr93bMsKGScMdqyMcZ9qnc19p3NnxxoMVxi9KtvVdzhD94dcj35rhrRLa/iMMcEmyIFcpxnv ya9F/tKS4twtwoLlQrD8MVxMV7Hpr3kNtIElcldo4APrUt6aHPiIJNSKWraZYQx2j2aITyJC Wyc+uP61FaAQTOEZomLZQxt6D+vIq5rt9dPpcEl1Y2/mp8rXEZB3j6etYNlM8nmzCYokahjg YxyMcdzTjdx1OZ76EtzMI7mFxCIimDznjPc+9Z8lyz+YsTHy2bcxPc1pXdtcanHLLA6ku+9l U8gn29Ko3lhJZv5MTFo4wHYkY3NVxsF9LFcpIXlKY/dqGIz0FRSXTMsXygqp6n+L61ZvLHyB 5kEnmbh8yEbWX6iqqStFMEVVeOTBww61otQJFkWVifLWMDrtPX8Kck53hY3Kx9wRyTVdPLBO 8n6CrML20ciMIpJB3+fH9KQXuSTNv3MrAtjqahjumR3ZsOx45qbP70mGARofU7iR6HNLLZxt KSilAei5ziloF7FNpN+NpJ9c10vw9cjxvoSx4GbpA3vzWGLExHduPTpW38N3A8d6JGQP+PtM E9etV1HF6n3fAPkX6VOAajgGEX6VMBXUjqYY4pccUuKMVQhNtABp2KMUEsaRS4pSKKLgNIpN vWn4pPWncBhFNK1JimkU0xEZWmEVIwppqkxkRFMIqVqjNWhETio2FTNUTd60RDIWFRuDUzda iatEQyJhUTVM1RNVolkLio2qZqibmqJIG6VEwqdqiagkryHHWoWqeQc1C9MCBqhap2qFulAH x/rw3a/qIH/PzJ/6Eaou3AVeg7+taniFcaxqJ4Ba4k7/AO0ay1xjHevm47HdLdgxIx61NGw2 ndyTTAQccdKUfMVXG2mRYkQBN0jdB90Huaiy0jksMlutTTguVWMMQo7UqQzkD5Hz7CkDXQbP C6pGoUru5IJqNY8ruC8ggVYZbiVSTG5VRt3YojSVV4icuh3HjpTuKw5UnSJXdSidAW7n2p8s ghXEfyu/Jz1Ap9naXF3KjPlVZs736cdqbNbMJP3h+Y9frUNq4OLtcW0kXcrHqOeKs3LLM6M4 UkY5A/HmoUiRIyrSAHtjmpVMIXO1yw/DNS32IsEK4QE5EjE98g56DFSebvZlkJkc8cjgUxJ1 Mcm6Bd2eGLEGoUclSI5gh/ummtRofHZzpulH3RwTnpVm2sJmDSMSFI3EjuKpBm+46huexzXS 2mv2w0l7AW8iHYQD15xSnzW0Nqbj9o5zfsdl25A9elWI2D25OwBS3YcgYqjMDEF3D5uw/wAa u2IklVgqtIWHOOaq3UzWsiSy1WPT7yKXBeNWyy56iu2u/G1he2OxWaKMAbmAzj2x61xf9nXQ Dm4s5Qn98RkYq9pmi2rwxXDb18zMSqwGHJ447/jUvltqdPNKmvdNOeeLUPsyIVFssgHHIwTy T711LauTeXItHiUmEgIx5CDoMduM1y2g2X9n2F3fW9rISpEUYkG48H5j6dK2pbqG1K25hBa5 jLS3DAA7iMY/Drj3rGUeiIimldmddW07L9sd5JArE+YiEIrY9Tj0rAsb37TczxzuTA6mOU5y B7n8a7zUZRq1rDpbK0YiEe2RMgPkfMG+o715hcO9tLcpZRFIvMI6ZJwfetKepnUXLsQSWD21 28EjrkZIP05qe9CTahIbcokZGRjgHFKNQW6W3e5Ui5jO0nHUDpn+VV4JlEeyVNyA9dvNa2d7 mV7aIgfCEOvI61v6a4mjypG49Np/pWddWBnjE9s4Ft2U9ffjtVt5LPT3j8p5GtJEDAyLyG7i jmT0NYNG7C7iF0KsSeVGOKhhu9odpU5xlACPlrMS8yC0LgtJgAddo7mr80IWGNwse0dZC3AH vSZsu6C4v5I4BdRyS7hzjOT7ms2CRr6aG2lt03MGkaQZ3Y6jNN0+Z5JYjMrPDdErGynlSCR/ n6ValuLrRZXkaHzreQeXMx43j1BHQ0n26nPOTm7IiIht7UxBT5pJ3biSPqM1BPHbJaiNHBaR 90gPp2/r+dWBPaTKbS0PmRE7opJOqt6cjpVkQ2F06mZ0hlUbX47dOnpU3tuZJGbp0ZghmltN 8jdOxwPf607TLtRG8k6so37ShPH5GtW3srVWnt1EYkLKuN+MiqOuaHPp2+7YLJbM4U7ex9TQ pKTsFnuVNWiaC+DgmS2f/VyHngjp+BqqTbgFbhNwP/LRB909jWxcWccVpvaUMoUfKCTg+9Zc mWVQTmMjBJ6e4rWLui3HqiO5tP3JuGRZYtuBLF/UdvxqvMI4o4txVsDIVf4T2zWnpdzaxXKo 6sygHcCcq/4VVuLKCTzpUi8qUnIRWyv4Uc2tmRYzr2SRoPkLFM53Dp9KSxvSpCyguR93FaP9 nxixFzI6pvbaIs5OfXFZTQYkdS+0j1rTQbjZamzdzAoN5CKRnBPNaHw8mibx7oXlgM32tOfT muTuTNtWORRgdD6103wot2l8faI2DtW6Q8fWklbVjUVfQ++IR8i/SpgKZCPkH0qYCupHUxBz mginYFFMkbikVlLsoPzLjIp5pvljzA+OcYoEwJAI5oI5pxHFBFAhppCMg0+m4oAaaaRUnFMN UhDCKYRUhxTDVIZGRUZGKlNMbFWhETComFTNUbVaJZAw5qNu1Sv1qJuD61qjNkbCo3FSmomP pWiJZC1RuKlaomFUSQuOKiYVM/eompkldxULip5KhegCBh0qFqnaoX6UAfH+uDdrV/gnP2iT r/vGqQjxyzACr2tDGt3/AP18Sf8AoRqv5Qfvz1NfNrY7pbsjBjXszH8qfFKN6naMDqPWmPGV 57HpTFDb6ZNyzNLKjna5wTlcU2OWY4YM2frxTEl2thl3L/dqQKrsPKPP900gu3sIWmx95wue g6ULJN1DNkjnOatySqF8lk249exquJwSwGeTQS2x9tLcRyB0Z1I754xT5o2Lq7En3qS0VpJA +0sOm0dzVhrfYdsxALfwjqKlsltlaKFmI2leuMmpooyYyRnC5PPqO1TWdtJO+xSq7OpNQ3gK zkKyHHQD19aV7uwJEDTowBQfMCVKkdu1MKfvAVOd3tTLwOrDd8mRngVd0tIjJCZcuAdwVe59 6q1lcajzOxbtrFpAGCgE9Dnjiku4bqHa/mYVxkLjBx+XSpdXmUy7YI/KlLdN2ePQe1MimllO y6mKxNgHzOeP8Kzu9xpWdjPeFxNuYZBPJzXQaPYzgCWGRow4ITHXkcn8uKr6ld29m0IaBgpH Eg6MD3+lblvcWgsoZA4wqYz+oqZSbWxtRpc0mdp4enVdAuRfHK/MVVs9PfNeX6xMLPUdlvJv CEMjqcqnso/z0qx4h1+a4MkVvIy2+dzHPU1yoMjknkgnNVTp21ZvVqKyiuh61HrdjLawQrNc iKziMspbH75gAcfnXNNfXGsaoqfZRmUgJH6A85z+dZGiyHy5Lb7zyRNzngccCtrTLqO2WSeT y0dkMayr1ViMHj0FRycnmZpubLzaybfxjBFa7haIRHI4HDeuf6GuS1iaWz1e4EcwkikO9cjq p5BFaa6NqFtHE9o8dzbl8+anVR7ioV06G7hUSSpcS2g2ru+UHP8ACTVx5UZ1lLaSM6zj828j ixmJ2DdR160++SMXG+NiQx+bKYKn0IqlcXU1nO6NCqsGDbU6L7VoaXcA6fK+AqM5G0ctn+tW 01qc9mmQ6jJPAlpHIwILE4Q4Ug9j71JEh1HR54fszE25z5objHpUEuozizk0+aJCrNksw5Br StLe90zRHmSOKa2uUztBIKds0noiuUzL7S20uSymZ3jtLkLuZT2Na81hCkckECNKzA7TK/GP WqEs15r32KwmSGJY/lXHyj3Nb2j2kWmTTo12Jkjx5MvYN6UpSa33CzirlOysreXTxaRxiCdC xmDuSyHsVH5UHTrt9KkczJKsQLMkmSxA74rbvQdTL3PkKs8AwCy8Sc9cnn1rL1x5zaRRxSyo Sm1kJ4YfUdaiLbYk7PQ5i3hW4i8qBI0uckht+FQetWtE3Tyyo8wGAIy7YJ57D2OKkFvsQGNm UuMPtPWohp0TZIyGHOQa2auX7NPYv3Gp2Fva3FncWE32sNmOZSGyc1XXVpJzN9pB2gBVhQg7 j2OCcVHb20SXG6X72c7jyTU0lun2sXKR+Yiv86AYGKFBIPZthbtfHkW7SqU+cLzgetaGq6hp YsorRLNi4feWRSARjp/9etXS7jyonkjMb7+drEgqvoM1l6zfQuxWGIKcgkoBxV8uht7O0SrN Ja3otorS3aFY+2zO78c1Uvbb7LqbR2weWENwD1WmWsdwWDwOSVzjHBqCBntr/N8G2Snlu1Ll ZEk7ahdhoU8qaP5i2QS4yPwot7Nr6C5nWRSYgPkI6itrVvs720TSKxcj5SBz7VgJC105MSy7 mOMKpHP4UIzlGzsyi8ZVtsihsjjB4Fdv8H2X/hLNKjAG5bpeehxXLPamJGVomPHB6j61u/Di NF8faAFLZ+1IeOnWhq+gQ0Z93wghBz2qUCmRj5R9KkFdhuw6UYpaCOMUEibcEmjPIHOT7U6j FFxCYoxS0GkIbikI/KnH6U0A4OT3pgIfrTCKUopJOOfWg1QDSKjNSNx1ph6VSAiZASCeo6Uw ipTUbe1WhEbComqVqjYYrREkT1C4qZ6ifrWkTNkR6VG1SHio2rREshYVG9SvUTDAqySF/eom qZ6hamSQPULVM9QvQBC1QsMVMxz0qFxxzQB8ga2f+J1qAz/y8Sf+hGqq59asa5zreoY/5+JP /QjVQBjyGr5tbHdLdk+SRzzTcZYnHHtSo2DyRUhClAVBye1Igh2AgnHCioenK8dqsGRVzxSO VbaFFUhFeR2JyxJNCZzwaeY8DLH8KeoCkdwaBMsWlxJbkEMw9h6U95Nz7iCrZz1yKgUFWyRj FWUg89P3ZGcdKh2WoizbTSyXIKAsGG5iAOBUN0skt7GirnJwuB1p1spgZYWyGkIDdsCrs+om a4WdoljWL5EEZxgetLbYpJPchmspLdlEy5c5BU84FVSoifcgdHB4Pqfp6Vv6XcfbNQie9CyQ FghOcZ9s/jSeLba1t9Ya1s3VUjGcknHripUnezNOX3HJGLLetMWY4M5+85H+cU+1PmyYklyB wfp7VBJbvDIjFSrHkqRVsIMsXQAAgjbxVadDJt9SSfTzPpxiilZsf3sEgjsfSs3S45JLeZPn ZlOPlPQVZ1MRs4msWZExtcdDn3qpbpdWs4khYKW7dQfrTjsWovdCCCeT5XYDB6D1rRiQrCgW HaRwzbs7voKaHkclmxvbk+lbccNxd6QojsoyqsB5yEl+OuRSlK25uorch0e4ht4Z2uXiSJRw m3LsfajUnt5LWIwIrBxuBDHIJ6g1NDpxlttwVGYsFGTzn6VoweH7u1EUz6bLIqvkqY22kf4V m5RTD2TTuc9bSX9myyWEjqR2HSia6urv7QtxGFMjB2ZT3FdLfzMJyGs0tVxymMYqO3057hlc QuQMEgA4x60+ZbtFundWuYt3pbxJamRg8k8e/BHIHTmhNN2RbYly5PQdK6u4hh1C7luFd0hh xHGoAO/bxj8TU9nGsPnzxnypQdsaHG1j6Goda2hElHm5UcVc6ZNaXkEVziCSU8EsDgHjOR0r ZttBjilWG31B7hfuhScxhu4IznFW/Edtdz3cF5d2Em9uBFA2dh7Y9ai0m1lt9YKztcQyy5Mc zjIHHTFDnzLcxlvYy7qys7eC7ubtWS5tnAaONiAPof8APWtG1v7axaycSIPPGBHtLAA/xbu3 0qa4tImS6tYibi4nGZ3bhW91984rD1K6u444LFIws8S7ckgjHanpPRmUtNTrRHbOlwlveNJN MCfmI2Lx2FcxNPqdnZ3ETC2ZG7KMlfcZrEXUJrd/JuoS7MOdxwfqKvQ6qyNLDNABuTC5Y/KK pQa8ybk1pM1kv2gRGSMHaUk5P/16khuIlk3qrCSTgI64A/X+dZ1vJFPp3zSEyhsBTwRz1FMm M6bIHXzJMZ3VdhqbRp3LqSCpAZjjLdPzqGNdijaWy2SR0Bx/Oqq3KpbtEbwgABiu3nPcCnJM stsZvOJHZW/h9hVRdtzaM+5cWYOFySGx09KZa6Td397Ilkks0x+bYgyarxyMbaSSPqvIDd/W ug8Oae9wBdtcS20RUh3jBDbe+PWtFJM0euhi6lbahpVzs1C2ltbgjIyuNw9feqNxK1yhR2O0 gMoI4z/Sut8SXIl0OCLTmuLmOOXcslynzAdx9K5htIuZtrvBNGRzuCnZjtTfkJvTQrNctOyR SMhMKjbyc59K07XVBZYMMQikb7xwcHisee38ppJxuIUDIbHX8Khlldgivkn0qLXMJOUWXLy/ YxFcIfmJyT6+1afwylL+P9CLc5vE49OawlijJOQSMcAmug+HUKr8QfD5UHP2tM/nVISTbPvG P7o+lS1HGPlH0qUV0nSJSmg9KU0CExRS87vajvSJEPSgilNFAhtFLmm+vFMBp70hpxPWmmqQ DTTGp5pjdapARsM1G1StUbVaERN1qCYsBlcY7irDVE1aRJZE9RP61K9RSZrVGbImqJqlPIqJ uDWiJZE3eopCQOAT7CpmqJq0JIXqF+tTPUTUEld6hepn5qF6AIXqFulTPULUAfHuuZ/trUAR /wAvEn/oRqnzj0r6cbwL4dupnmn02NpJGLMcnknqamT4d+GD/wAwuP8AM18ksTHse/LLpt3u j5ghXLZboKeXJfcDgjoBX1Evw68L4/5BcePqakX4c+Fv+gVF+Zp/WI9iHl0+6Pl3cJ8BkG71 FE0axNtgbeMDcw9a+pk+HPhcdNKiGfc09fht4V/6BMX5mj267C/s+fdHycQxJ4xTgpyB+dfW g+HHhY/8wqL8zSj4aeE/+gRD+Zp/WF2I/s+fdHyqgHlNkctwCfSpIVYMeMKO/rX1Wnw28Kgq f7JiyOnJqRvhx4WdgX0qIkd8mp9uuwf2fPuj5fM0okgRihC8AsoNU7tpQcuqgHuAeRX1b/wr nwvx/wASqLjnqaG+HHhabiXSYnI6ZJP9aFWS6D+oT7o+UNOMkLq6l/KLdhnBrUE07PO06faF ck4HGGPQmvqO1+HPhSFAsekQgdcZOM1b/wCFd+FyG/4lUWG6gE0Ord7GsMK4LVnzE9nJ9miW CQbuCTt3sfb2H1qa/wBPjSEwxxMZ+m5RhyT6jBr6bg+HnhmEERaXGgJ52sR2+tWbbwH4dglE kWmxrJn72Tmo5mXOjFo+RP7D1iOeUQWFzNG2QpdMke9IPC2tZXGm3nPTKHAr7Lj8K6QMEWg7 fxGpf+EX0kgg2oI/3jWiqvsZfV6a6s+PbbQ9VicfadKuW2kbQUI3exrs/CPhWOWZknt9Qs7m VTv+coqgnqPX8c19GnwfojyK72Sl16HJ4q1H4Y0pHZ1tQGYYJyegqZyckNU6aepwXh3wvZ6F aLDax7wfmaV8FnPqa1zDGjYcZU+3FdmNHtP+eZ44+9T/AOyLQgAxnAP96suST1On6xTSskeG +KRpury3cGpaa8M8R8uCbAG/PQg/41zt1aSm2Fkk0aAL5ADEhjx13cYr6Du/BehXsyzXNgsk gIwSxpZPBOgTOGk0+NmwFySelPkb3OapOE3qfOB0Vo0gt4rfTgV+RGV9zBj3zjjjOTVZLC/t hI7GxfeeImJIXnqMDrj1r6XTwJ4dGSunRjIweTSN4D8PNkHToyD1+Y81XJ3MuWne6PnL7EZr C4SS9RJ1JECKzEoMcjOOMdsViDTntLSBRcO9xyUlJ3Yz1696+pf+Fe+Gt+/+zU3eu40ifDvw yjNt0yPLcnk803TdrIXubnypLpNzYsrm9274x5eBycnr/wDrp9utnaW00MpWcOQ4/djIP1P+ FfVEnw38LyEF9LRscDLHgVGfhn4TcgHSYuPc1pGHcc5RmtUfJN5HpsrCUWzNKOMSH5f0xUEk unWwaVbPbPjAZpHbH4E19dP8LPCDY3aPET/vH/Gom+E/g1vvaLEfqx/xrZIx5I9D49gurPzD NHYxrJkkkluPpzVuPUIhC2+3gnkB4MqdP8a+tv8AhUngzGBosPH+0f8AGgfCXwaoIGjRY/3j /jTswUUj491BoZ2VxaxB++OAB9Ks29ms9nCsEsEUsr7WLKAiL65/Cvrr/hU3g4bsaNFyMH5j QPhJ4NCbBo8YXOcb2/xotJltQPj64+waXOLfR7v+0b5m4k8ncmP9nJ4/EGtibXriK3s1jmZp BJtllUcu2enTBUdsV9SwfB7wTA++LRIlbGMhm7/jVuX4X+E5beKCTSYzFFgou48Vpyy6Ex0u fKcGoTTmUyMxERILDAyR3xS3FxKYFYSsznnZkEfgK+qR8K/CIDgaSgDHLfOeaYPhN4PByukq D04dv8afLIfMj461RluHdNqQl2wyrycViXEK20xw7txwK+3v+FReDC+46QhYZ5LtTX+Dvghm y2iRE+7t/jSVOVzGUb7Hw/HcJ5vzE811Xw02v8RNBKsSv2pMfnX1mfgv4EZtx0GHP+83+NWt J+E/g3Sr+C8sdGiiuIWDxuGbg/nVcjIVNrqdsi4A+lPApVAxxTsVrc1bGkf1oI604/40Hv8A jSuIQjmk707nv60d6BDaDTvSkzQIbQadnimmmA0immpKYaaAYeKYwqQ0xqtARMKjapWziom7 VaAifvUb1K9REYrWJDImqF6mbrUT9q0RmyJulQPVhqgbduxjj1zWqJZE3NRPUrdajetCSBgM k8/iaiap3qB+tBJA9QvU71A9AEDVC5qZ6hfFAFa2+6KvRiqNqSUH0q/F2r4Y+2ZMoqaNR6VG nWp0pkMcFqQCmrUijimSKFFShRzTQDnrxTwKZIoFPUUKKkUUCIwnPPTinheaeBSqtMLjfL6G rUYPOaYq+voamQdfxq0jOTJABn/PpUir0pFH8/6VIo5FWkc8mKq8D8KkVeOlIo6fhUiinYyb BVp4Xj86VRT8cfnTM2wC04L/AD/pSgU4Dn8f6U7GbYiqOKcAOPwpVHSnAHj8KZLYgX/P40u2 nL0/KnAVSJbGbf607bzT/wD69LVJE8wzb/n8KAvAqTHT6/0pR2q0ibkewY/Kk2CpQMDj2pO4 q0g5iMpRs4/OpSKDwCfrVWDmI9vXilCinjJXJGD6UtNBcjC0BakpKq4rjNoo2/1p9Hai47jN vX8aNvNSf/XoNFxXGBcGgDpT+9JzkYFFwuNxRjrTqSgdxp/xoPQ/jQzAEA980p6GmAhpO9Lj FGPegBKQilxwPWgigBDSetLjmk9aYCUxqf60000A01G1PNMarQyNqjapGqFu+eK0Qhj1E9SO KjetIkMheonqVqietYkMjaoWqVqg3bs+xxWqIZG9RtUj1E1aEsikOBULGpn96hYUySB6hepX HOc1C+aAImqFqkcmomzSArWv3Fz6VeiPFULU/u1+gq9HXwx9s9iynWplPNQLU6UyGSr7VKtR LUqmmSSKalGKiFSYpkkgp69u9MUdKkTt+FMTHKPT2qQCmr/hUqimiGwA/rUyjH60xfp2NSL3 q0ZNkq9f8+lPHFMHX8f6VIvaqRkx6dB9BUi/5/OmJ2/CpF6VRkx6in4/rTF6VIP8aZmx1OA/ n/SkFOH+fypmbHL70o7fhSL2pw7fhTIYEHHHtTkyQc8c0CnCqRLYvr+NL3NA7/jS1SJF9/8A PSjPzAYNKP8AP5Uo7VaJE7fgKSndh9BQKtAN5xz15oP+NOP0o9fxqkFxDRSk9aKYCUUoooAT HFGKWjt+dACY/rQaX/69KetADRQO1KKKAE7UlKOlIaBjHUN+GaU9/wAacf8AGkPf8aYCEc0D rSnrRjmgY30pDwM07HSkpgNz7cUhI5zTiKb68etMBDzTTT6Zk5PGMU0AxjjrTDUjVG1WhsYf pUTVK1RMatCInqJqleonrWJDIX61E9SyZ7VC/wDWtYkMjaoXHPFTNUTVqiWQt09aiepWqJ60 IInqFqlaoXoJIJOlQvUz1A9AELVCx4qZ6rtmgCrZnMUf+6KvxVm6ec20J/2B/KtGOvhz7Z7F pDU6VXQ1Mh6UyGTqalBqBakU0EkympQfWoQfSphTJJF61Knb8KiXtUqdvwpiZKv+FSL0qNOn 5VItUjORIP6GnimDp+dPHf8AGrRmyUdfx/pUi9qjHX8f6VInamjJj06D8KlWo07fhUi9KZlI etSD/GmCpB0/OqMmOFOHX8f6Ugpy/wCfypmbHL2py9vwpF7U4Dp+FMhi/wD1v50ooH0pRVIl i44P407HWk9fxp1UiQA/z+FKO1H+f0oHarRIDkdPSjFKQCuCPSgdKtAIcUv/ANej1o/+vVAI UU545pQKXuaKAuJRS0mKACk/+vQc0vagA7/nQRzR6/jSmgBB1/Gk9KGByCCc5oXmgBi5yc9K caWkpjuMAILbjkZ49hSmlP8AjQeh/GmMQ9aTd84XHvmlox8wOOaAE7Cg0vYUh6flQMaaafp6 0+mHv+NUgEJ60w080w00A0nOajY080xqtDI2NRsakaom9a0QiNjUTmpHqJ61iQyN6hepXqF6 1iQyM1E1SN1qJq0RLI2qF6laoXrQgifpUT1I561E5oJIHqBzzUzmoH60ARMQagep2qBzQBn6 Yc2luf8Apmv8q04jWTpB/wCJfan/AKZL/IVqxmvhz7XoWUNToarofap0PSmQyYE1KvSoVNSo eKZJKtTqagWpVoETLUqdvwqFKmTt+FMTJF/wqVaiX/CpFqkRIkHT86kHf8ajH+NSDvVoyZKO v4/0qReoqMdenf8ApUi9RTRkyRO34VItRr0H4VItMxkSLUg/xqNaeP8AGqM2SCnj/P5UwU4d fx/pTM2PTtTx0H4Uxe1PXoPwpkMUU7pmkHSlHeqRAqkkH8adSAdfxpatCY4f5/KgdqB/n8qU dqpEgOg/CkFL2/KitEIQ0v8A9eg0UABopfWigBBSYpwpB1oAQigj+tLR/wDXpjE/+vSnrR/9 elpCGlc45I57UKMUo60hOBk0xh2ptEbB0DAMB7jHelOOaAEP+NIe/wCNKwyPbmkPQ/jTKA9a O9B60dx9aAE7UjdOtL2pppgBph6U40w1SGNbPGMe9IaU0w1SAQ1G1OYZ65qMirQxrVG1Paom rRCGPUTVI1RPWiIZFJUT1I5qJ61iQyM9OaiapG6VExrVEMiaoXqV6gY84ANUSMfoagf61K/T pmonpkkD1C9SyVC1AET1XY1O9QPSAy9FOdMsz/0xT+QrWjNY2hHOk2X/AFwT/wBBFa8dfE9T 7ToWk7VOhquhqdD0oJZOpqVagQ1MtMkmWpVNQIMDFTL1pkk61KnaoFPNTIelAEq/4VKtQr/h Uq1SIZKDx+dSDvUQ/wAakHeqRkyUdf8APpUq9qhB5/H+lSr1FUjKRIh4H4VKpqJO34VItMyk SLUo/wAaiXpUgP8AWqMmSA09f8/lUYp4/r/SmZskSnDt+FMTtT16D8KZDHCnU0f5/OnDp0q0 QxQev4078aQd/wAaXvVIkd/j/SgdqQf1/pThjirRIdh+FJS8YH0FFWAUhpTQaAA96SlPQ0UA Iox3oFA96BQAhYZAJpT+NIUBIJGaX/69AwA5NLR/9ejvQIBSClpB2xQAdqSlppznrxTGB6H8 aQ/40rf400/400NAetHcUHrSd+lMYdhSHmjsKQ0DENMNKTSGqQDTTDTjimGrQDTUZNPao2q0 A1jUJ+tSNUTVogGNUTVI/tUTcCtEQyN+tQtUr1C5rWJmxjVC5qRjUTVqiWRNUL1I+c1E9Mki c+9RPUr9KgegkheoX9qmeoH60AQsTnnpUL/Wp2NQNzQBj+HjnRrA/wDTCP8A9BFbEVYfhw50 PTj/ANO8f/oIrbir4l7n2a+FFpKnSq6GpkoEydKmQ1ApqVOlMgnWpVNQKamU0xEy1MhqBTUy mgCZP8KlWoV/wqVapEskH+NSDv8AjUY/xp4NUjJkw6/j/SpF7VEOvX/OKlU9KpGUiROg/CpV qJOg+gqRaZlIlWpB/jUS1IP8aoyZIKcv9f6U0U8fX/OKZmx6U8dvwpidqevb6CmjNjhThTRT hVohjvX6GnetN7H8ad61SJFH+fypV7UClXtVokO35UlKeg+gpKsQH60GlNFAwpKWigQlFFNL gOq9yOKBjjRRRQAUp60UUhB/jTAfmxT6QUxify4pKWkpjGnp+dI3Q/jTj3/Gmt/jTQ0IetHc UHrUcRkLN5gULn5cdfxpjH+lIaCaQmmMQ0w96caYe9UhjSajYmn5GcUxjVoQ01GSaeTUZIq0 AxjURzUhIqMmtEIjcntUTnrUjmonNaRJZG5qFzUrn3qFzWsTNkbVE5qVjULVoiWQueKic1I1 QyMByfpTJI36VE1SP0qF6BET1A3WpnqFjQIheoGqZ6hagDD8Mn/iQ6b/ANe0f/oIrbjJxWD4 WOfD2mf9esX/AKCK3YjXxT3Psl8K9C2lTIaroanSgTJl7VMvSoFNSqeKCSdamWq61MtMRMp9 qmSoEqZKAJ0/wqVelQp/hUq/WmJko/xqQdKiH+NSDvVoyZKOv+fSpU7VCOv+fSpV7UzKRKnb 8KlXpUKHp+FSrVGMiVelSD/GolqQf40zJkgp6/5/KmCnjr/n0qjNj07U9c8fQU1O34U5eg+g pozY8U6mj/D+dOHeqRDHDofxp1IOh/Gl71aIYucdfX+lOXtSD/P5U4dvwq0SxO34Ckp3b8qS qADRzzxSmj/69ACUCloHWgBKjWNFkZwgDt1YDk1LxScUBcQ0dqWg0ANcsFyihj6E44707nml GP50HrQAg6/jSCnDrSUAMAOeTkUGnUhplDT/AI01u/404/40jdD+NUhoaetHeg9aTvTGIelN NKR05pCKaGNNNNONMNUhjTjNMNOPWozVoQw9TTG+lOY801q0QDGqJqeaiNaIQx6iepHNQsea 0iSxjnmoX7VI5qJzWqM2RtUL1KxqFzVksieonqRzULmmSRuaiapHNQsetAiF6hfrUrn3qFzQ IieoGqVjULUAYPhM58OaX/16xf8AoArej6Vz/hEAeG9Kx3tYv/QBXQR9K+Ke59jH4V6FlKnS qyVNE25QRnB9eKAZYWplPFQLUqUEk61KpqBamXrTJJlNTp2qutTJQBMp/pUy9BUC/wCFTJTB kq9PzqUd/wAaiH+NPHeqRmyUdf8APpUqdRUQPP4/0qROoqjKRKnQfhUq1Cnb8KkBpmUiZalH +NQqalB/rVGMiUU8f5/KoxT16/59KpGTJE7U9eg+gpiU9eg/CmZseKcKaKcKtEMd6/jT6b6/ jTu9UiGKKcOg/CkH+fypR2q0SAII4waSlVQBwMdKBVABo/8Ar0Gj/wCvQIDSig96BQAlFFA7 UDCk7UtFAB6/jQaP/r0HrQIAOR9aQUtIO1AxKQ0ppvcjmmNCN/jSHv8AjSn/ABpD0P41SKQh 603vTjSUxjT0ppocEgENig9KoY00wmnGmnvVIYxjUbGpDUZq0IjY1GTUjdaiJFWgGMajY1Ix qJq0QmRuahc1K9Qua1iQyNzzUTmntUT1qiGRtUTmpGqF6olkT989Kif2FSPUT0EkT96iapG6 GoXoERPULVK9QvTEQvULGpXqF6QGB4QP/FM6T/16Rf8AoAroI+1c94P/AORY0j/r0i/9AFdB FXxb3PsY/CvQspUyVAhqZDQJk61KpqFTUq9KZJMtSrUCmplNAiZSKmQ9KrqanQ9KAJkNTKeB UCGpkpgTL/Q1IO9RD+hqQHrVIhkoP86kQ8iolPP41IvUVRmyVTwPwp4NRKeB+FPU0GbROp4q dT/WqqfWrCngfjVIwkiYVIp/z+FRinr/AF/pVIxZIvanr2+gpiU9e34VRmx46U4U0U4VSM2P HQ/jTu9NB4P40/vVohig/wCfwpy9vwpB/n8qUdqtEsO35Ugp3b8qQVQgNH/16D3pfX8aAA0U HvQKQCUUvpSCmAdqO1FH/wBegYdj+NGc80ev40GgQDrSDtSikHagYlNNOpDTQ0NP+NNPf8ac 3T86a3eqRSENIe1Kc5pO9MY09BTWxTj2pp+tUhjTTCRTzTDVIZGSM0xjTzUZ71aEMYioiRUj VCa1iDGsRUZPtTmJ7UxzWiERuahcipXNQOa0iiGRvUT1I55qFz0rVEMjY1C9SsfeoXNMkiY8 VE9SOahY0Ekb1E/epHPFRMaBEL1C9Suahc0CImqF6laoWNAGB4O/5FfSP+vSL/0AV0Edc94O P/FL6R/16Rf+gCugj6V8W9z7CPwr0LKVMlQJUyUAydakWoFqVelMknFTLVdTUymgkmWpkqup qZDTAnQ1OnSqyHmpozQMnXp+FSA9aiX+lSA9fxqhMlB5/wA+lSKelRD/AD+VSLTMmPU5UfhT kNNTp+VKOKCGToeSKsIePzqsnNWE6fnVIxmWFqRf8/lUQNSL/X+lWjnZInapF7fhUa9qkXt+ FUjJjx/n86cKaKcKpEMeO/407vTex/GnjrVozYo/z+VOHakH+fypR2q0Sxe34CmindvypBVC A0f/AF6DS/8A16AA96KPWlFIBBSClAoFMBKD0/Olo/8Ar0AH/wBeg0hGQR9aMHPXI+lAAKKU daQZoGNpDSkUlMY1iB+tIe/40p/xpD3/ABqkUhD1pvenGm96Y0NOOKawFOJ4FNbpVIY01GcU 85qM1SAaajantUZrRAMbvULVK/tULVpEBpxUTYzTyaiatEIY9QvUjZqFzW0SGRvUD1K/WoXq 0QyNqhepHNQtmglkbVC9SOaiY0ySNzxUT09zUTGkIjeoHqVzUDGmAxqhapHNQuaQGF4N/wCR W0f/AK9Iv/QBXQR1z/g3/kVtH/69Iv8A0AV0EdfGPc+vj8K9CwlTJUC9KmQ0AyVR71KvSolq RaZJKtTLUC1MtBJIOtTJjNQg1KhpgTLU0Z5FQIelTRn2oGTg/wAqkHf8aiB/lUi96YEw6/j/ AEqROoqIdfx/pUq9RTRmyRO34U/HFMToPwqRf8KZkx8YqwvA/OoF6VMnPb1qkYyJ1qVev+fS ohUi9fx/pVowZKnanr0H4VGnapF7fQVSMmPHSnimA/5/GnCqRmyQd/xpw60wd/oad61aIY8f 5/KnL2pq/wCfypy9qtEMXt+VIKXt+ApBVCA0ev40Gl/+vQAUUpoH070hCCkpwpKBiGg9KWkP +NMA/wDr0po/+vQetIAFIKKQdqYxKQ0tIaYxrf401u/404/4009/xqkUgPWm96U0nemhjT0p jEU9ucUxqpDGk1GetPaoz1PPFWgGmocbQR15JqVqjarQEbGomNStUTYrVCImqNjUjEDmoWIr VCI3NQualc+1QufatIksic81A5qWSoXNWQyNjULGpGNQuaCWRtULYqRqhc0CI2NRsae9RMaC SKTpULVI9QsaAGPULVIxqFzQBi+DR/xS2kf9ekX/AKAK6COsDwd/yK2kf9ekX/oAroI6+Me5 9fH4V6EyVMtRJUq0AyRalXpUS1KvSmSPWphzUIqUYpkkgqZetQLUy0ATJUyVAlSpTAnWpV+t QpUq0DJgealQ8ioR1/GpU6imjORNH2/CpVqJO34VKlUYyJVqZf8AGoVqVf8AGqMZEy09f61G KkXr/n0poxZKvanpzj8KjTtT17fhVIyZIowKeKYD/SnirRmx47/jTx1pg6H8adVohjx1/wA+ lKvamj/P5U5e1WiGO7flSCjt+VJVAKaO350Gl/8Ar0CA96O9B70CkADtQKCOOKTGRTAWkoAw MUetAB6/jSnvR6/jQetIAFN9KcKaSAMmmAlIaXtSGmUNb/Gmnv8AjTj/AI0jd/xqkUhp60ne lPWm8Z6U0UNPamtTieBTWPtVIBjVGaexphNWgGHvUTdKkJqJjWiERvUTVKxqJq0QETGoWqZz UDHFbIRG/FQualc1C5rREkTmoHNTOaruRxTIZGxqFzUrEVC5oJZExqJzT2qJjTJI271E1SN0 qFqQiJ+tQyYIwalfrULdaYDGqFqkaompAZHg7/kV9I/69Iv/AEAV0EfSsDwf/wAivpH/AF6R f+gCt+OvjXufXx+FehOlTLUKVKtAMlWpFqIVItMgkFSrUIqUUxEgqRc8VGtSIaBEyVKlQp1q VKYydDxUy1Ah4qZTQMmXr+P9KlTqKhHWpk7UyJEsfQfhUqZqJOg/CpVqjGRKvSpV/wAaiWpR /jVGMiYVIv8An8qiWpV6/j/SmYskTtT17Z9qjWnr2/CqRkyQf4fzp65pi/4fzp4q0ZseD1/G nimDv+NOqkZseP8AP5U5e1NH+fypy9vwrREsXt+VHpR2/KgVQgNGev40ppP/AK9AhaBQaOM0 gDNAPFFA/wAKYB2o7fnRQf8AGgA/+vQetH/16DSABSelFFMBuMdKQ0tIaZQ0/wCNI3+NK3T8 6a3f8apFIQ9aQ9aU9aTvTGMbpTTTj0phqkMa1RmnmoyOTVoBp+tRN9aee9Rt0rRCI2qJvrUj ComrVAyJ6rv9anYVXk61rERG5qFz6c1K4qFulaIkifrUD1LJ1qB6ZDI3OBULVK1QPQSyN6ha pG6VE9Ahj9Kienv0NRMaCSJ6hapXNQtQBG1QtUrVC1AGd4RH/FM6T/16xf8AoArdjrD8Jj/i m9K/69Yv/QBW7H0r417n2EfhXoTLUq1EoqZaBMkWnr0qNakWmQPFSCmU8DvTESLUq9aiWpV7 UCJFNTL2qFalTmmMmTpUy1CnSpl6UDJl6/jUqdRUK9fxqZetNEMlTt+FTLUKdvwqZelUYyJV qUdPzqJTUin+tUjGRMtSL/n8qiFSL1/H+lMxZKlPXt+FRqelSL2/CqRkyRen+fWnrUa/4fzp 69KtGbJB3+hpwpo7/Q06rRDH9/8APpTl7fhTR/n8qcvb8KtEMXsPwoFGcL+AoFUIU0ev40Gj 1/GkIX1o70GigQUmKWkFABR/9eijt+dMYf8A16DR/wDXpT1pAIOtJ6UopPSmA3nPTikOcHFO NNNMoQ/4009/xpzD+tNbv+NUikNPX8aQ9acetNOMj60xjG7U1qce1NbFUhkbUw9TTzTDirQE bVExqVqiatEIibqc1ExqVsVE+K1QMic1XcDmp3xUL1rERA9Qv0qWTFRNWiJZBIagkqWZQy4J IHsahfAAFMhkTVC9TPUD0E9SJ6hY1K9QtQIjeom6mpHqJqCSJzULGpXqJqAI3qFqleoWoAo+ FP8AkXdL/wCvWL/0EVux9KxPC3/IvaZ/17R/+gittOgr417n2C+FehMlTLUS1KlAmSCpF6VG Kep4pkkgqQCogRUgNMkkFSrUINSqelAiVeamSoFNSqaYydKmX6VXU1MpoAnXr+NSp2qFTz+N SoelMlkydvwqVahToPwqVM461RlImX6VKOn51Cv1qUdOvrTMZEq1Kv8AX+lQrn1qVQc9e/8A SqRjIlTtT07fhUaZ9aeueOfSqRkyVen+fWnio1z/AC/nTxmqRmyQd/xp4HNRgH+dPGatGbJA P8/hTlHSoxn/AD9KcueK0RDQ8dPwFAAGKQZx+AoGaoQ7HWjFIaX/AOvSELjrQPag96RRgYFA h1IBRQKAFxSUtJ/9egAI60EUf/XoNABjmkx0/Cl7030oGJjikIpaQ1RSGsOPzppH9acf8aa3 f8aaKQh603vSnrSd6oY1unSmGnN0FNaqQxhqM96kaoz3q0BGw9qiapWFRMOK0QiJqicVKwqJ 61QMicVA4qdqgetYiIJBULippPeoHrREkMlQOKmeoJKZDInFQOKmbNQvQSQuKhcc1K4qJ6BE Tg1EwqRunNRN1NBJE9RNUr1C1AEbVCaleomoApeFOfDuln1tYv8A0EVuJgCsHwl/yLelf9es X/oArfj6V8a9z7BfCvQmWpUqJalWgTJBT1pgqRelMkcKkH0pgqQCmSOWpF7UxakXtQIkSpUH tUaCpUpjJV6dKlX6VGnT8KlUUDJVHPSpk7VEvWpUpkMkTt+FSrUcfb8KmWqMpEi1JkAc9KjX pUm0MpDDIpmLJVqVQM/j/So1qRev4/0qjFkiU9e34U1O1PXt+FUjJj1/w/nTxTV/z+dOXpVo yY8d/wAaeKbzz9DTlOc4INUiGOH+fypy9qQf1/pTl7VoiGA6D8KB1pe35UCqEKaD/jSE9aP/ AK9Ah1GaQ96AaQh2aQGgUlAC59qQn+tFH/16AFz/AFoPWj1/Gg9aAEHWj0/Cl9KT0/CgY3tS GnU00xoa3+NNPf8AGnN0/Omt3/GqRSEPWk7/AI0pHNJ3FUUMPQU1vrTiOKawqkMjamE08imE VaAjJ61ExqUiomFaIRExqJjUrCoWFaxBkTkVC9TOKgcVrERBJUDkYqxIKruK0RJDJUD1M4qF xTIZC9QPU7ioGFBJC9QtUzionoEQvUTVMw4NQtQSQvULVM9RNQBC1RNUzVC1ICj4SH/FN6V/ 16xf+gCt6PpWH4TH/FN6V/16xf8AoArejHFfHPc+wj8K9CVKmUCo1HNSrQJjwKeBTRUgFMkU CpAKaBUooJBRUqimqKlUc0wFQVKvamrUq0wHqOPwqVRTFHH4VKvSmBIBz+NSoOlRjr+P9KkT qKESySPoOPSpVqNB0/CpV6VRjIkWpAePzqNakXp+dMxZKtSr1/H+lRDNSrnP+fSqMpEiVIvb 8KjSpFzx+FUjJj16f59aeKYpOP8APrT1zVoyY8Hr+NPAx0po/oaeKpEMcP8AP5Uq9qQf5/Kl AzgkcjpWiIY7sPoKBQSce/FAqhCmg/40E0Zzn8aQhT3opTSDOTn14oEAFGKWgUAJ26UlO7UU AJ/9eg9aWigBB2pPT8Kd3pPTj0oAb2ppp3akNMoYf8aa3f8AGnt3/Gmnv+NUikNPWkPUU49a TvTKGHoKY3Snnp0prVSGRmoz3qU96jP0q0BGaiYVMaiatEIhbvULVO30qJq1QMgaoXqw1QtW sRFZxUDj0q09QOK1RJVkFQPVqQc1A9MhlZ+lQOKtMKgcUElZ6hYVYeomoEV3qF6sP0qFxzQS V3qJqncVEwoAgeoWqdqhagCn4UH/ABTml/8AXrF/6AK3o6xPCw/4p7S/+vWL/wBBFbkYr4x7 n2K+FehMlSrUaVKtMTHjGKkUcUxakFMgeKkApgqQUEj161ItRipUzmmA9RUqVGlSr2oAlWpB Uanjp2qVTx+dUgHjr+P9KlTqKjB5/H+lSIeRTIZKnb8KlWok7fhUq9KZjIkXpUg/xqNakH+N UZMlFSL1/H+lRjvUi9fx/pTRkyRDUi9vwqNKkXt+FUjJj16dP85p6mmj/P508VaMmPB6/jTg eaaO/wCNP71aIY4Hn/PpTl7fhTR/n8qcO1WjNi9vyoFL2/KkGfSqEKaP/r0HPpQT6+9IBx70 U3cMkZGeuKdmgQUUgJ9KBQAvaj/69H4UmaAFOKKM0E0AHek9PwoB5oz0oAbSHvS5ppNMoQ/4 01un504n+tNY9fxqkUhGpO4pSaTPNMY001ulOJ4ppPFUihh71GaeT1phPWrQEbVG1SsaiY1a AiYVC1TtULVqhMhaoWqdqietYiK71C9TvUL1tEllZ6gerMlV5KZDK5zjnr7VC9WGqF6CSu9Q vU71C5pkkL9KhfpUz9KibvQIgcVC1TOahY0AROKgap2PtULUgK3hgf8AFP6Z/wBe0f8A6CK2 4xWN4ZGNB03/AK9o/wD0EVtIK+Me59kvhXoTIKmWo0FSqKZLHCpFHFNUVKo4oIFUVKtMA61I BzTEOWpVHSmKKlUUxDlFTJUaLzUyLQMcv9KlUdce9MUH9KkA61SEPXr+P9KlTqKYBz/n0p6d RTRmyROg/CplHFRp0H4VIM0zGRIoqRQMfnUa1KB/WqMmSAVIo/n/AEpg+lPX+v8ASqRiyRB0 qRR0/Co07VIvb8KaM2PUf5/GnAU1f8P504VaM2SAdfxp3rTR3/GnVaM2P7f59KVe34UgpR0q 0Qx3b8qQUDlRxjgUAVQhTQcEEHpzQaU/40gIRAiylxnJGMZ4qaj1oAxQDd9xc0maWkFAhaSi j/69AAaU9aKDQAnej/61L3pB/hQA2kNOptMoaRx+dIR1/GnH/Gmt3qkUhCKb3px60ncUxjCO BSMKcaRulMZGwqMipGphq0MjIFRMKlYdajatEBCw55qJhU7VC4rSIiFhULipyOKibrWsRFeQ VC9WJKgcVtEkryCq8gqy4qCQVZDK7VA9WXFQuKCSswqFhU7jNRPQSV36VC4qw/eoWHNAiu4q F6nkFQvQBA4qFqncVA1ICLw0P+JFp3/XtH/6CK2oxWP4cGNE0/8A694//QRWzHXxj3Psl8KJ kFTKKjSpVoJY8VKoqNalWmSPAqQdaYtSgUyRVqVRTFqVBzQA9BUq0xKlWmA4Dj8KkHemj+hp 471SJY4dalTORTB1/wA+lSL2qkZsemcD8KlXNRp0H0FSDpxQYyJFzUgz/OmLUi/41RkyQU9c 5/H+lMFSKeenf+lUjJj07VIuePwpiHpxUinp+FNGUhy/4U8U1Tx/n1pwIHarRmx47/Q0/uaa Oh/GnZ5q0Qx69/8APalHakBHP1/pTl7VaIYdvypFz3FO7flSCmIWlNJS0CCg9elLSfSkIUUl JHuMa+YFD45CnIzS0ALSUtJQAUUtFACd6SloFMY2kNO/+tTTTGhp/wAaRj/Wlb/GkPemikIe tN7049aTvTGNPammn46U01RQw0w/SpDTD3qkMiao2FSkVG1WgImqF6naomFapgQMKiap2FRM K1iIgeoHFWHFQPWsSGV5BUEgqy45qCQVqiGV2FQPVlhUDimSVnFQtzVlxULigkrOKhIqw4qF qQitIKhYVYkFQvQBXcVA4qw9QtQBF4eH/EmsP+uEf/oIrYjHSsjQP+QRY/8AXBP/AEEVrxji vinufZrZFhBUqiokFTKKZLJFFSLUaipFFMgkUVKKiUYqUUySRakXB61EoqZBQBIvapV7VEoq VRTBjwf61ID1/Go8f1qQDr+NUiGSA8/59KkQ8iowOfxqRR0qjJkiHgfhUimmIOn0FSKKZlIe tSg/1qNRUgH9aoyZIDUi/wCfypgFSKP5/wBKaMmPTt+FPXt+FMQdKeo6fhVGbHqfb0/nTxTF FPAqkZseO/40/v0pgHX8afirRmxwPt/nFOB6U0D/AD+FOHarRDF7flSCl7D8KSmAuaM0UtAg oopaQgpKWkoAWkoooAKKKKACkzS96QCmMM000tIaBjW/xpCetK309aaygj6c1SKQE8/jSZ5p xFJjkUxjfSmseKce1IelNFDCaYT1qQ0wjr+NUhkZPtUbVKRUbCtEBEetRNUxFRMOatAQtULV OwqJhWqEQPUD/SrDioXFbRIZXf6VA5qw4OfaoJBWqIZA54qBzVhxUDiqJK71C5qw44qBxzQS QPULnmp3HBqFhQIruagc1YcVA9AiB6gerD9agkpDGaCMaTZf9cE/9BFa8fasrQx/xK7P/rin /oIrWjAwK+KPs+iJ1qVajQVMopkscvapVFMUdKlUcUyRQKlHWmqKlA64pkirUy9qjCniplFA Dl/wqVaYo/pUig0yWOH+NSAdaaP8aeB1/GrRDY8Dn8f6VIg5FMXr07/0qReopoyY9CBtB74q VaiVfukjkYqZaaMpD1FSD/GmLUg/xqjJjxUi/wBf6UwdakX+v9KpGTHp2p69vwpidqevb8KZ kx4py00U8VSIY71/Gnim+v40+rRmxR/n8qUdqB/n8qUdBVokO35UgpR0/KjFMQUHoaWjFAB6 0UtFIQlApaSgAopaSgApaKKACkpaSgBKQ06kNMY1v8aaae3+NNPf8aaKQnem96dSd6YxtNNO 9KQ9KopDDTCP61IaYe/PrVIoYRUbCpSKjaqQEbComFSmo2+taIGQsKhYVOw4qFhWsRED1C46 1YcVC/Q1tEllaQc1C4qxIKhetkZsruKhcVYYVXlyAcDJ9Kol7kDioHHWrD1C4oJK7jg1C9Tv UL96CSvJVd6svUDigCu9QOKsNUD0gG6IQdNtMEHESfyFa0fasvRhjTbUD/nkn8hWomRjAzXx R9r0LKVMlQoKnQUyWPXrUy9KjUVIOBQQSKKlHWo1FSgUxD1HNSoOlRrUq9vwpiY5f8KlWo1/ wqQVRDHj+hp4700dPzp471SM2PHX8f6VInamD+v9KkTqKpGTHp0H4U9elNQdPwqQUzKQ5akH +NNUVIB/WmZMePpT1Pt3/pTRT1xn8f6VSM2PQ9KenQcelNSnrjj8KZkxy/5/Onimgf0p4xVo hjgev40/PtTQOD+NOGKtGbHD/P5Uo7Uf40CqJCiiigApaKQ0CFooooAKKKKACiiigAooooAK KKSgApDilNIaYxD0/Omnv+NOPT86af8AGmhoQ9aKCBuzR3/GmUN7CkPSndh+FIaYxhph7/jU hFNI6/jVIojPemGpW71GwqkMiao2qU/Wo2HvWiGyFvpULfSp2GKhceprWIiF6hb6VO4qFxWs SGQP1PFQSCrD1A9bRM2QsKgcVYbmoHrREsruKhep3qF6ZJXcCoHFWXqB8UElZxUDirMlV3oA ruKgcVYcVA9IBNI/48Lb/rkv8hWpH0rL0rIsbXAz+7XP5Vqx9K+JPtehOlTLUSCp0FBLHqak XpTVFSqKogctSimKKlAoEOWpF7fhTQKkUdPwpiY5f8KkXNMUf0qVaozYo/xqQDrTR0/OpB3q 0ZscBz/n0qRB0po6/wCfSpF6imjJjkHT8KlUUxO34VKtMykxyipAP601akHT86oybHAU9Rz/ AJ9KaPpUi8du/wDSmZNjkHSnqOn0FInanr2/CqRm2KBxTwKRelOFUjNijv8AjT8Ug6H8ad61 aIYopfSk70DoKokKWkpaACiig0AFFFFABRRSUALRRRQAUUUUAFJS0UAJikIpaKYxpH9aQj+t OPT86Q/40x3GkUmOacaO/wCVA7jMcCkIp1If8KYxhFNI6/jTzTSP61SKTGEdaYwqU9DUZHvV IoiIqNhUzComFaIZCwqJwKnYVC4rSIiBxULjNTuKhcVtEhldxzUL1YcVA4raJmyBqharDCoH rVEsrvULip3FQuKZJXeoXqw9QPQSVnqB6sSVA9AFd6gf6VYeoHFIBNJz9ht8jB8tf5VqRdKz dMGLKAf7C/yrTjHFfEn23QnQVOlQoKnQUEskXpUq9OKjUc1MgpkDxUo61GBUy/1pkscKkXt+ FMUc1Ko6fhTRLFX/AAqQU1R/SpAKtGTFHQ/jUg7/AI00dPzqQd/xqkZscOv4/wBKkTqKaOv+ fSnp1FUjNsenb8KkXpTE7fhUq/4fzpmMhy1IP8aYtSD6etMzY8VIp/n/AEpgxUg/r/SqMmPU 09T0/CmL24p69Bx6U0ZscD/n8acOlIOnI9KcO9WiGOB6/jT80zsePWn1aIYUtJS0yQooooAK KKKACiiigAooooAKKKKACiiigAooooAKSlpKAE/+vQcc0f8A16D/AI0xiGk7ilNHcUDGntSG ndhSHp0pjGmmn/Gnmmnv+NUikRnHNNbFSEdeKYRz/n0qkUiJqjapjUZFWiiFqhap2FRMK1Qi vJz0qJx7VYcVA4rWLJK7ioXFWHFQyCtombK7CoXFWHFQOK2RDK7ioWFWH6VC3NWSV3HFQOKs PnFQP3oJKsg+tQOtWpKgekBVcVA4qy9QPQAmnD/RYf8AcH8q0YQvVccnmqFgMW0Q/wBkfyrR jr4c+2exYQVOg5qGP6VOlMlj1HSplFMUVKopkDwMCpVFRgcHFSrTJY9RzT1HT8KavUVInb8K pGbHKP6VIKYvt7VKBVIzY4Dj8DTwOv400D+Rp4HWrRk2PGAfx/pUiDpTAOf8+lSIORTRm2OT HH4VKvSmIBx9BUijimZSHrTx0/OmqOenFSAD+dUZMcKkX+v9KaBT1HP4/wBKZm2OXtTx2/Cm qOlPHb8KpGbHDH+frThikAH+frTgKpGbYvY/jTqTH9aWrRItFFFMQUUUUAFFFFABRRRQAUUU UAFFFFABRRRQAUUUUAFFFJQAn/16DS//AF6Q0xiMAeDQMcUuOfxoxzQAnp+FNJHTvj+tOx0p McUxiGmnofxpxFNI/rTRSGkdaY3WnkdaYetUikMb61EamIqMirRRC1RNUxFRMK0QEDioXqw9 QuK2iSyvJUL9qsOKgfqK2iZsgaoXqwwqB61iSyu9QvVhxUL1qQVn71A/WrLioHHWgkqyYqF6 sOKgcUAV3xVd6suKruKQDrL/AFMf+6K0I+gqjZjESf7oq/H2r4c+3exYjqdKhjqwgpkMelSr TEqVR/KmQx471IKZjrUoHP400Qxy9R/ntUi9vwpi53DjipF7fhVIzY5f8KkWmL/hUq/5/OqR nJjh/jTxTR/jUg6GrRkxw6/59KkXqKYOv+fSpU6iqMmOQdPoKlANMToPwqRaZlIcoqQDj86Y AT3IqQH+tMzY8CngH/P0poNSKf5/0qkZMVB0p6jp+FIvanKen4U0ZscAcf59aUA80CnDrVoh sOx/GnUlLVIkKKKKYBRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAJ/8AXoPQ0UHo aYxMc0d6XvR3oAZ6Udqd2FIT7UDGkU0j+tPNNP8AjVDQwjr+NNIqQ96Yf8/lTRaIyKjYdPpU pxmmHFWiiFhUTCp2qJgK0TGQOKhcVYcVA9axZDIHFQPmrDjmoXFbRM2QNULjNWGFQMK2iyWV 3FQuKsMKhetUQytJULirDjrUL1RJVkFV3FWZBUD0gK7iqz1aeoHFAC2g+RPoKvxjiqVqPlXj tV+IV8KfcMsRip1qGMc1OoqiJEiipl6fnUSiph0/OmZseKlH9f6VGKlA/n/SqRmxy9v89qev b8Kavanr2/CmjNjkOT+VSr/n86Yn+FSD/P51aMpDh0/OpB3pg/xqQd6tGbHd/wDPpUidRTAO f8+lSoOlNGTHp0H4VIDTEAwPwqRQMUzKQ5akH+NMGKkAH86oyY8VIuP1/pTAKeo5/H+lMzY5 e1PXt+FNQZ708AYH4VSM2OFKKavK5Ix/+unAVSJYtLSUtWSFFFFABRRRQAUUUUAFFFFABRRR QAUUUUAFFFFABRRRQAUc59qKKAEoPSlpDQAUd6KO9AB6Uh/wpccCkpjENNPf8acQaQj+tNDQ w96af8/lTyKaw/z+FUi0RmmEcCpCKYRxVIpERqJqmYcVEwrRFED55qJ6nYVC4FaxIZXeoXqw 45qBxW0TNkLVC/1qdhULitoksrtUL1O4FQvgEVsiGQSVA/WrDjg1C4qiSrJVd+vbFWZBUEgo ArPUD1YcVA4pAPtvuj6Vfiqjaj5VOMEitCIV8KfcPYnSp1qFO1Tp/hVESHpUy/41GtSj/GmZ seO/41IOp/z2pg7/AI1IOp+v9KpGTHL2qRe34U1eo/z2p6dvwqkZMen+FSKP8/jUcYOOf881 MKozkKB1/GpAOtNA/rTwOtWjJseBz/n0p6jpTQOf8+lSKOlMzbHoOB+FSAUxBwPwqQCqMpDl FSAf1piipAP60zJseBT1H8/6U0CnqOfx/pTM2OUU4Dp+FIo6U4DgfhVGbFA/pSgUYpRVIkKW iirEFFFFABRRRQAUUUUAFFFFABSA5HTFLRQAUUUUAFFFFABRRRQAUUUUAFB6UUGgApKWigBK KWkoAQ009/xpx6Uh/wAaZQxu9NI5/wA+lPPf8aRv8/lVIpEfemHpUnemEcCqRaImqNvpUrDi omFaIZC9ROPapnqJ61iSyu4qF+tTuKhcc1tEhkLVA4qwwqFhWsSGV2FQuKncVC4raJDIHHFQ PVlx1qBxWiJKslQOKsyVXcUAVn6VA9WXqBulAD7boKvR9KpW3QVejHSvhD7l7FhOlTJ/hUSd qlUf0qjORItSj/Go1FSAf1pmTJB3/GpB1P1/pUY/xqQf1/pVIzY9O31/pUi9vwpijp9akTt+ FUjKQ9f8P51Kv+fzqNR/SpF/z+dUjJjx/jUg7/jTB/jUg7/jVoyY8Dn8f6U9B0po6/j/AEqR OoqkZMeo6fhUgBpidvwqRaZkxwFSAf1pq08d/wAaozbHgU4D+f8ASkp46/j/AEpmbFQdKcM8 fhQvalHb8KZDFpQMUUdKtEi0UUVQgooooAKKKKACiiigAooooAKKDRQAUUUUAFFFFABRRRQA UUUUAFBooNABRRRQAUhpaSgApp/xp1IRx+dMaGnv+NNb/P5U49fzprYpopDO9NNP70wjpVot EbdKiY1MwqNhVooheoXNTOMVE461rETK8h9qhkNTuKhcVtEzZCxqFzU7CoXFbRIe5XeoWNTt ULitokMgfpUD1YcVC4rRElWTNV361akFVnFAFd6gbNWHFQNQBJbdBV+MdKo23QVfj6CvhD7l 7E6DpUyf4VEnUVMoyOfaqMpEiipF6fnUa9KlH+NUjJjx3/GpVFRev41KP600ZMeuM1Ig6fhU a9RUidvwqkZMkX/D+dSAVGv+H86kFWjNkgAx+dPHQ/jTB0/Onjv+NWjJkg6/59KkXtUY6/j/ AEqVR0poyY9McfhUi4x+VMQcD8KkUcVRlIeuKkGMfnUaipAOPzpmbHjFPXH6/wBKYBT1H8/6 UzJjlxxTh0/CmqMYpw7VSJYtLSUtWiQooopgFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFF ABRRRQAUUUUAFFFBoAKKKKACkpaQ0AFIe/40tIf8aY0If8aaQacf8aaetNFIbjmmEdKf3ph7 VSKQwioyKkYZxTGq0WiFxUT1M9QvWsRMgfrUL1O/WoXFbRM2QNUT1M1QuK1iQyBhUL1M3Son raJDIH6VE9TPUL9a1RJWcVXkFWZBUDiqEVnFQOKsvVd6QBanKitCLoKoWoOBWjEOlfCH3T2J 07VMvb8KiTt+FSp0/KqMpEi1IOn50xakA/rVIxY7pn8alHU/57UwDr+NSAc/j/SqRmxy9vr/ AEqVO34UxRyKkQdPwqkZSY5f8KlFRqDn24qVRVIykOHf8akHf8aYBwfoakA6/jVoyY8dfx/p UidRTAOfx/pUiDkU0Zsenb8KkFMQcD8KlA4/z61RjIVakH+NNUU8Dr+NMzY4U9ev4/0poFSK P5/0pmbFXtSjoKB2pRVIhhS0lLVoQUUUUwCiiigAooooAKKKKACiiigAooooAKKKKACiiigA ooooAKKKKACiiigAooooAKKKKACkpaSgBD3ppFOPemmmikNxzTCOn4U/vTew/CrRSIyOKjYV KelMIFUjREL1C9TsOtROK1iJleSoXqxIOelQuOlaxZmyu1ROKsMKgYVtFksrvUL1YYVC4raL Myu9QsOasOODULitoklWQdagerMgqBxViKzioHFWXFV3FIB1t0q/GOlUbYcCr8Y6V8Gj7uWx Mnb8KmX/AAqKMdPwqZB/SqMJDxUo/wAajWpB/jVGLHjofxqXnnH+eKYB1/GpAP5/0qkZNjl6 ipF7fhTVHT/PanoOB+FUjJscv+FSCmr/AIVIKtGbHDOD+NPGefxpo6fnUi45/GqRkxwzn8f6 VImcimDr+P8ASpE6iqRmx6ZwPwqQZxUadvoKkU8UzJki59aeM8/jTFp4P9aZmx4JzTx1/H+l NFPB56d/6UzNiqTxSihe1KOlUiGLRRRVoQUUUUwCiiigAooooAKKKKACiiigAooooAKKKKAC iiigAooooAKKKKACiiigAooooAQgHqM0tFFABSUtJQAHoaQ/5/KlPSkNMYw9RTPT8KfTfT8K pFoYelRtUhximGrRaIn+tROPepn+lRPVxAhce9QSDpzVh6hcdK2iZsgYVC4qdqiatYksrsKi cVM1RPWyIZA461C461O59qhetokMrOKgcc1ZkqBq1QitIKruKsvUD0AJbD5RV+MdKo2/3RV+ PtXwSPu5bE0fb8KlXp+VRx9vwqVO34VZzyJBUi/41Gv+fzqQf41RiyQd/wAalHWohnn8alGc n/PamjJj17fX+lSL2/Co16j6/wBKenb8KpGbJB/hUi1Euf5VKo/z+NWjJjx0/A08Y5/GmAcf gakA68etUjNjwef8+lSJ2qMDn/PpUijkVSMmSIeB+FPUimIOnHpUgH+fxpmbHqRUgI/nUa/S pAPb1pmTHg08EZ/H+lMAp6jnp3/pVGbHDHFANIO1KOgqkSOzRSYpapCCiiimAUUUUAFFFFAB RRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUlAAaQj/P4Up70h/z +VMaG96Ye1P702qRSGMOKYQakNMNUi0ROKicVM9RPWkRkL1C/ap3qF61iZshaoX7VO1QvWsS WQNULVO30qJ/6VsiGV371C1WH71C4rWJBWkqB6sSCoHFbIRXcVXerLioHFMBLboKux9qo2oI Aq/H2r4JH3U9iaPt+FTJ2/Cok7fhUq/4VZzyJF6f59akX/GoxUg/xqjJkg7/AI1IOv8An0qL 1/GpR1/z6U0ZMkXt/ntUidvwqJeo5NSL2/CqRlIkX/CpF/z+dRL/AIVKKtGciTPB+hp4PWox 0/A1IO/41aMmSA8/59KkU8iox1/H+lPXqKaMmSIeB+FSA8dKYnQfhUg6UzOQ5TUgP9aYKf8A /XqjNjgeaeDz+P8ASmDGakHX8f6UzNig9KUGkHagU0SOopKWrQgooopgBzg460UUUAFFFFAB RRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUlAAaQ0p70hpjE70z /wCtTuab6U0Uhp6Uw04001aLQxqiepGqN+lWhkT9agfNTOOwqJ/cVrEhkL+1RMeamaoXrWJD 3IGqJqlIqN62RDIH71C55qdx1qF62iQV3qF6ncdagcVshED1XerD1Xf8aYBbDgVdj7fWqdt0 FXY6+CR9zMlTt+FTJ/hUadvwqVBx+VWc8h4p46fnTVHH+fWngf1qjJj/AF/GpB1/H+lRgdfx qUD+f9KaMmOXt/ntUi9vwpij/P4U9VBA/CqRmx6kfyqRaYg/pUgHH+fWrRmx4OR+dSA9fxpg HHXsaeB1/GrRkx4PPXv/AEqROSOajAyfx/pUqDkU0ZsenQc9hUi8imIOn4VIopmUhwp46fnT VFPwcce9UZsdTx1/H+lMXJHIxTx1/H+lMzYq/pSigUoFNIlhS0UVaEFFFGOaYBRRRQAUUUUA FFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRSUABoNBoNMY3vTD2 /Cn96Ye1NFIaelNNPPSmGqRaI2qN6lamNVoZXfrUT1O4qFxWsSGQtUTDkVOwqFhitYkPcrtU T1OwqFx71smQyB+9QvVhx1qFwM4rWJJWkqF6sOKgcVvETKzioHqy4qu4zVCC3+6Kux9v89qp 2/3RVyMdP89q+CR9xMmTt+FSr/hUadvwqVf8Ks55D1PFPB/rTB0p46fnVIyZID1/GpAefx/p Ufr+NSDv/ntVIzY9TyPr/SpF6D8KjXt9f6VIvb8KpGTHqf6VIv8An86jX/CpB0/z61SM5D/X 8aeO/wCNMHPf1qQd/wAatGbHjr/n0p69RTB1/wA+lSL1FNGTHp0H4VKM1GnQfhUi9KZnIcM0 8f401af2/OqM2OGaeM55/wA8U0dOaeP6/wBKZmwUU4UgpR61SJYtFFFUhBRRRTAKKKKACiii gAooooAKKKKACiiigApBnvS0UAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFJQAHoaDQaQ0 xiA00ngUvcU3sKaKQh6Uw089KYapFIY/Wo3qR/amNVoohkqJ6leonFaohkRqJzUrVG9aIhld 6iapmFRMK2RDIJDgVE55qd+hqFxWsSSu/U1C9WJBUD1tETK71A9WXFV3FaiG2/3auxiqdv8A dFXI+31r4FH29QmTt+FSr/hUadvwqRRx+VWc8h4qQf40xaeP8aoyY/1/GpB3+v8ASox3/Gpe 5+v9KpGbHKOR9f6VIvb8KYvUfX+lPXt+FUjJj1/wqQf5/Oo1/wAKkH+fzqkZseB1/Gnjv+NM HQ/jTx3/ABq0ZseOv4/0qReoqMdfx/pUi9qaM2SJ0H4VIKjToPwqQUzNjh0p4/xpi0/t+dMz Y8U8f1/pTRTx1/H+lUZsUdqB0FA7UopokBS0UVaEFFFFMAooooAKKKKACiiigAooooAKKKKA CiiigAooooAKKKKACiiigAooooAKKKKACiiigAooFFACGilNIaAE70w44p+eabnpVIpDD0pr U8mmGqRaGN1/OmOKkb/GmN3qkUiFxUL1Ox61E9aohkLCoWqduoqJv61qiGQN71E1TNUT1qiW QPUT1MwqJxWsSCvIKhcVO4qFxzW0RMruKhcVPJx+lQtWqER2/Srsfb6/0qnB0q7H0H1r4NH2 1QlQdPwqVB/So07fhUq9vwqzmkPUU8D+tNX/AD+dPH+NUZMeB1/GpAOT9f6UzHX8aeO/1/pV IzY4dR/ntT07fhTVHIp69vwpozY5f8KeP8/nTVH9Keo/z+NWQxw6fgakHf8AGmAf1p4HX8ap GbHj/P5VIvUVHjnP+elPU46c+wqjNkijgfhUgqNO30FSgUGTHrTscfnTADjipO351Rmx4xTh 1popwpmbHCjpRQKpEi0UUVYBRRRQAUUUUAFFFFABRRRQAUUUUAFHfFFGKACiiigAooooAKKK KACiiigAooooAKKKKACiiigAooooADSUp6UlACd6aegp2eab6VRSG00049KaapFIY3f8aYae 3+NNbFUikRP3qF+1TPjmoXAzWkSWRmonqUgVG1aolkDVG9SuKjcVqiGQN3yKiYVM4qJhWsSC vJ7VA4qxJULj0raIiB6gcVO9QvW0REUHSrkfQfWqkFXI+g+tfBo+1qEydvwqVf8ACok7fhUy /wCFWc0hw/z+dSD/ABpgqQdPzqjJjvX8akHU/X+lM9fxqQdT9f6VSM2KvUf57U9c8fhTV6in qen4U0QxV/wqRc/5+tMU/wBKep/z+NWjNj+efxpwBwfxpueD+NPB6/jVIhjwOfx/pT06imA8 /j/Snr2+tUjNkidvwqQdKjQ9PwqQHigyY9RxT/8A69MU1Jn+tUZscBTx1/H+lNBpw/r/AEpk MUUopBSg1SJFoooqxBRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAU UUUAFFFFABRRRQAUUUUABpKWkoASmnHFO7imntTKQ09KacU40xqpFIRv8aY3enNTWq0UiN+9 RPUj4z1qJ/rWiJZG1ROD261K31qNu31rREshYVE9TNUTVqiGQuKicVM/eomrWJBXkFQPVh6h atoiZXYVA1WGqBumK2iIjg6Vbj7fX+lVIelW4+31r4SJ9rUJ07fhUq/4VEh6fhUqn+lWc0h4 HH+fWpB0/OogRxmpAePzqjJkg7/jUg7/AFqPufxp4PJ+tUjNj16j605e34UwHBH1p6np+FNE Mev+H86cv+fzpi/4VIP8/nVIhjx0/Onjv+NRjv8AjTxznGe9WjNkg6/59KkXGR0qMdfx/pT1 6iqRmyRBwPwqRelMQcD8KeooMmSLinDp+dNWngf1qjNjxThwfx/pTQOtOH+fypkMcKBQKBVI gWiiirAKKKKACiiigAooooAKKKKACiiigAooooAKKKRjgZ5/CgBaKKKACiiigAooooAKKKKA CiiigAooooAKKKKACkNLSUAJ3FNPandxTCTxTRSEPSmEU8001SKQ1v8AGmNT2PX8aY5q0UiJ 6ifqKlc1E9aIlkbY71G1SMfWo2rREsg9d3PNMb+lSNjvUTYxWqIZG+MVC1SvjBqJq1RBDIKh cVK9QvW0RETVA1TNUD9K2iIjhq3EcgH/AD0qpAOOKuR9v89q+ER9rUJk7fhUq/4VEnb8KlX/ AAqzmkPFPHT86Yv+fzp4I5H1qjJj/X8ak55x/nimZ6/jTxxke/8ASqM2Km7AzjNPjBwMnJ+l NB6f57U9T0/CmiGOUf0qUf5/Oo1PH5fzp4P+fxq0ZskA/rTsdaZu4P0NSA9fxqkZseB/P+lS IOn4VHnn8f6U9D0+tUjNkiDp+FSAf5/Go0bp+FSBuKDNj1FP/wDr1GDT8nH51RmyQCnDr+NM BNPB5/H+lMhjhQOlIDSg1SJFoooqxBRRRQAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUA FFFFABRRRQAUUUUAFFFFABRRRQAUUUHgUAFIev40dqKAE7030p3cU09qopDTTSacaYaaKQ1v 8aa3enNTG71aKRG/eon6VI/1qJ+1aRJYw/Wo2pxOe2PrTGrVEMiPSonqRjUTmtEQyJhyTUbV Ix4qJjWqJIXqFycipnNQt9K2iIhaoG6VO55qBjxzW0REcPQVbj/r/SqcNXI+1fCRPtahMnb8 KlX/AAqNO34VIv8AhVnNIeP8/nTvU/WkHT/PrTx/jVGbHDv+NSd/x/pTPX8aeCMkH/PFUjNh GwY8djipV7fhUSKFACDAHYU8ZGMYPSmQyVf8Kev+fzqFSc+3FSrzz/nrVIzkh4YEle4BP61K O9RgfyNPA61aM2Sjr/n0p644qIZz+P8ASpEHIqjNkidB9BUg/wAKjQcD8KkFBkx64p/b86Yo p49PrVGbHj/GlJIIABPfNIBTx1/H+lMhigjA96UU1h8uBTh0qkSxaKKKsQUUUUAFFFFABRRR QAUUUUAFFFFABRRRQAUUUUAFAzgZGDRRQAUUUUAFFFFABRRQaACiiigAooooAKSlpKAA9KP8 aD0NJ3pjEBBbAPIpvHFDLlgccik9KZQGmGnHpTTVIpDXA/nTG709v8ajbmqQ0RuBUT44qRz1 qJ+1aolkZIIyKiapWqJq0RDImqNx/KpG9aibpWqIZG9RPxmpX6VE9axJIXqBqnk61C/WtYiI GqFulTsagb6VtERDb8KM9f8A61XI+1U7fpVyPoK+ER9rUJ0PI/CpV/wqJO34VKo/pVnNIfnj /PrUg/xqMU8f41RmyT1/GpB3+v8ASo/X8aeP6/0qkZsUf5/KnqOh+lMQ7sHnr3p69AfYUyGK FBH5fzqZQf8AP1pi9B+FPH+fzqkZtjx3+hp47/jTBxn8aeSADn3q0ZskHX/PpT0zkVX85ecc n/61IJ2JXaBk0cyJ5WXU7fhUgqGEnAz7VMDVGMhwp+P600Gng9fxqjNjhmnjP6/0poNPH9f6 UzNggIzk5yacOlAoFUiWLRRRVCCiiimAUUUUAFFFFABRRRQAUUUUAFFFFABRRRQAUUUUAFFF FABRRRQAUUUGgAooooAKKKKACkpaSgAPekP+fypTSHrTGJ3pmKf360z05popCHpTDTz060w1 SKQ1+pqNgacU2s5yTu55PSkbpVoohYcn1qNxUrc81E/atEQyNgaiapWqNutaIhkDVE2amYVG 3StUQyB81A6sZM54xxVlu9ROQOtaxZLK755qFzyOank4qFq2iIheoG6VO+KgetYiIoOlXI+3 1qnB0q4nb6/0r4RH21QnTt+FSr/hUKdvwqVf8Ks5ZEg6VJ/9eowaeCP51RmyQcA9+tSDv9f6 VFnr+NP3cn/PaqRmx44Ix608dvwqNTz+P9Kep/pTRDJF7fhTwRj/AD61Gp4/KnZ4/wA+tUZt D93yk/Wq8xLE5b14pJpcKQvJ5qtuYuTjnB71MpdDSEOpbQhBj3qxCVLjp2rM3MWx1Ge/0qzZ kpIpc5PrRGQpw0ubEZ4H4VIOn5fzqvE4IH4VMrcVujhkiVaeP8aiVqkDf1pmTJB1p4/z+VRg 09Tz/n0qiGPFKKaD0pQaaIHUUlLVoQUUUUwCiiigAooooAKKKKACiiigAooooAKKKKACiiig AooooAKKKKACkNLSHpQAtFJnmloAKKKSgBaSgHOaM/1oGB70h7/57UE0h/z+VMEIDzTfTFLm m+lNFID0php3amk1SKQ1j/WmMacxpjH3q0UMc1E/anOajc9K0SIY1qiank1ExFaIhkbVE1SM aic1qiGMeonAI5Gae5qJjWsSSKSoX6+1SSc57VC5raIiNqrt0qZjULGtkIit/uj/AD2q5HRR XwaPtqhMnb8KkX/CiirOdki9KeOv50UUzJj/AP69P/x/pRRVIzY4dR9f6U9eg/CiiqRDGwk+ a/PcfyqbsaKKfQmW5Vb+ppY/vN9KKKz6mnQaf9YfrUx+8v1FFFNBIvw9F/CrS0UVutjhqbkq 9aeOn50UVRgx69acOv4/0ooqjNki/wCFKvQfQUUUyGLTqKKtEhRRRVAFFFFABRRRQAUUUUAF FFFABRRRQAUUUUAFFFFABRRRQAh6iloooASkaiimNC0UUUhB2FFFFACDpR2P40UUxidz+NIa KKEMb3pvp+FFFUUN7U00UVSKQx+tRt0ooq0MifvUbdaKK1RDIm6ion6UUVoiHuMaoWoorSJD Im6GomoorWJJA/U1C/aiitoiZE3SoGoorVCP/9k= --------------080509060209000004040706-- From henning@meier-geinitz.de Wed Jun 16 21:44:17 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 16 Jun 2004 22:44:17 +0200 Subject: [sane-devel] xsane -0.91 In-Reply-To: <40D08957.9060606@hei.net> References: <40D08957.9060606@hei.net> Message-ID: <20040616204417.GA31800@meier-geinitz.de> Hi, On Wed, Jun 16, 2004 at 10:54:31AM -0700, Don wrote: > Using xsane-0.91 with MDK 9.1 with KDE 2. The version of sane-backends is more interesting. --> scanimage --version > I had xsane working fine with an Epson CX5400. While the CX5400 isn't mentioned in our lists it looks like the epson backend knows it. > However, the next time I booted the system, xsane no longer worked. > Xsane could not find the scanner. Does "scanimage -L" as root find the scanner? > The /etc/sane.d/epson.conf is the same as when it ran. - See below. > lsusb and sane-find-scanner both return 04b8 0808 Seiko Epson Corp. > /usr/bin/xsane said sane could not detect parallel devices as user and > root. I guess that's what sane-find-scanner says (not xsane). SANE can work with parallel port devices but sane-find-scanner can't detect all of them. But how is this realeted to your USB scanner? > The only lines in /etc/sane.d/epson.conf not disabled with an # are; A single line containing just "usb" should be enough. > usb 04b8 0808 This won't work as the USB ids are hexadecimal, not decimal. Add a "0x" before the numbers. > usb /dev/usb/lb0 I'd be surprised if you had a "/dev/usb/lb0" device. I've never heard of such a device. > Xsane work like this before. Are you sure that you haven't changed the config file in the mean time? Bye, Henning From gerhard@gjaeger.de Thu Jun 17 07:11:28 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Thu, 17 Jun 2004 08:11:28 +0200 Subject: [sane-devel] PLUSTEK OpticPro 12000T do not work under Kernel 2.6.4-52 In-Reply-To: <200406152141.10202.info@linuxmaker.de> References: <200406152141.10202.info@linuxmaker.de> Message-ID: <200406170811.28832.gerhard@gjaeger.de> Hi Andreas, I'm not sure, why this mail took that long to reach the list - or - to reach me, but I think we have already discussed that on the linux-club.de forum... For the protocol: - something wnet wrong when buildingh the module, but in the end it is loaded - automatic loading is done via /etc/init.d/boot.local - although the module is loaded, SANE does not find the scanner - there are two concurrent SANE installations on Andreas' box... That's all, Gerhard On Tuesday 15 June 2004 21:41, Andreas wrote: > Hello, > > I need your help. I have upgraded my system from SuSE 8.2 to 9.1. Now I > need for my Plustek parallelport-scanner the package > sane-backends-2004-06-14.tar.gz. I have installed it correctly, so I mean. > But my scanner can't be dectected. xsane shows errors and scanimage -L > tells me "No scanners were identified". > > Shortly after the installation of the package and after making > ./MakeModule.sh tells me dmesg [SNIPSNAP] From gerhard@gjaeger.de Thu Jun 17 07:14:08 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Thu, 17 Jun 2004 08:14:08 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( In-Reply-To: <1086702292.2129.40.camel@Babylon7> References: <200406081215.54463.gerhard@gjaeger.de> <1086702292.2129.40.camel@Babylon7> Message-ID: <200406170814.08201.gerhard@gjaeger.de> Hi Oliver, thanx for the info, I'll test it.. - sorry for the late repsonse. On Tuesday 08 June 2004 15:44, Oliver Rauch wrote: [SNIPSNAP] > static void xsane_back_gtk_value_update(...) > > case SANE_TYPE_INT: > val = adj_data->value + 0.5; > > remove the "+ 0.5" and it should work. > > But I am not sure if this will cause other problems. > I think there has been a reason for adding the "+ 0.5" Probably yes ;-) but obviously the reason is not that important, that you've missed the comment on that workaround :-))) Ciao, Gerhard > > Oliver > > Am Die, 2004-06-08 um 12.15 schrieb Gerhard Jaeger: > > Hi, > > > > I'm currenlty trying to add more frontend configurable options to the > > Plustek backend and have some problems with xsane now. > > There's a value whose range is from -1..63. At the default state, when > > starting xsane, it is properly displayed: -1. > > When changing once to i.e. 6 and changing it back to -1, xsane stores > > it as 0 and also displays it after the next startup as 0.. > > Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, > > the contraint_type is SANE_CONTRAINT_RANGE... > > The configfile of xsane shows, that this value is stored as 0 and not as > > -1... > > > > Any ideas? > > Gerhard From gerhard@gjaeger.de Thu Jun 17 07:55:16 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Thu, 17 Jun 2004 08:55:16 +0200 Subject: [sane-devel] Installation oddities... Message-ID: <200406170855.16452.gerhard@gjaeger.de> Hi list, on my SuSE distributions, I used to overwrite the existing and always outdated SANE-RPMs, by using the following configure command: ./configure --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --infodir=/usr/share/info This works pretty well up to sane-1.0.13, while checking 1.0.14 I noticed, that the links in /usr/lib/sane to the new libs are no longer updated during the installation step - did anything change there? TIA, Gerhard From henning@meier-geinitz.de Wed Jun 16 12:13:42 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 16 Jun 2004 13:13:42 +0200 Subject: [sane-devel] xsane -0.91 In-Reply-To: <40D109E1.7010602@hei.net> References: <40D08957.9060606@hei.net> <20040616204417.GA31800@meier-geinitz.de> <40D109E1.7010602@hei.net> Message-ID: <20040616111342.GC31800@meier-geinitz.de> Hi, On Wed, Jun 16, 2004 at 08:02:57PM -0700, Don wrote: > Thank you for replying. Please reply to the mailing list, not me personally. > >The version of sane-backends is more interesting. > >--> scanimage --version > > > > > scanimage (sane-backends) 1.0.11; backend version 1.0.11 That's rather old. I don't know if your scanner was already supported in that version. > >Does "scanimage -L" as root find the scanner? > > > > > device 'epson:libusb:oo2:002' is an Epson Unknown model flatbed scanner. Ok. "Unknown" doesn't look correct but at least it's detected. If it doesn't work the same way as normal user, see man sane-usb and README.linux for setting permissions/using hotplug: http://www.sane-project.org/README.linux > >This won't work as the USB ids are hexadecimal, not decimal. Add a > >"0x" before the numbers. > > > >>usb /dev/usb/lb0 > >> > TYPO ERROR it is usb /dev/usb/lp0 in epson.conf Well, but it's a USB scanner not a parport printer, isn't it? Anyway, the scanner is detected so there is no need to change anything. Bye, Henning From keith@claytons.org Thu Jun 17 13:56:38 2004 From: keith@claytons.org (Keith Clayton) Date: Thu, 17 Jun 2004 05:56:38 -0700 (PDT) Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <1086882323.2126.4.camel@Babylon7> References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> <1086879836.2126.2.camel@Babylon7> <1086882323.2126.4.camel@Babylon7> Message-ID: Finally had some time to get back on this . . kid's birthday, end of school year, etc. Upgraded to xsane0.94 on the windows box and problems scanning multiple images are gone. My best guess is that the mismatch of sane versions between 1.0.14 on the scanners host machine and the sane version included with xsane-0.90 were the problem. Back when I upgraded my backends to 1.0.14, I upgraded xsane on the linux box to 0.94 and looked for an upgrade to xsane-win32 but blew it and didn't see one available. Sorry for that, thanks to Oliver for pointing out that I'd blown it :-) and many thanks to Henning for showing me the many troubleshooting steps I could take. Cheers, Keith On Thu, 10 Jun 2004, Oliver Rauch wrote: > Am Don, 2004-06-10 um 17.32 schrieb Keith Clayton: > > No, still running 0.90 on the windows box. I upgraded to 0.94 on the > > linux box and looked for windows binaries at the same time. Didn't see > > them. Did I miss it? > > > > Looks like it. > Oliver > > > K > > > > On Thu, 10 Jun 2004, Oliver Rauch wrote: > > > > > For windows you can not enable a debug output - at least I do not know > > > a way with the published binaries because they are compiled as GUI. > > > > > > BTW. Did you ever test xsane-0.94-win32? > > > > > > Oliver > > > > > > Am Don, 2004-06-10 um 16.09 schrieb Keith Clayton: > > > > What sort of steps are availble for me to take debugging-wise on the > > > > windows end? > > > > > > > > If xsane is started from the command prompt, are there any swithces > > > > available to generate debugging output at the command prompt? > > > > > > > > K > > > > > > > > > > > > > > > > On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > > > > > > > > > Hi, > > > > > > > > > > On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > > > > > > Hate when I do that . . here's the xsane logs described in my previous > > > > > > email > > > > > > > > > > Ok, let's look at the second log. The preview scan looks ok (but I > > > > > don't know the details of the plustek backend). The real scan also > > > > > starts fine and then we see this: > > > > > > > > > > [plustek] sane_read - read 3750 bytes > > > > > [saned] do_scan: read 3750 bytes from scanner > > > > > [plustek] usb_ScanReadImage() done, result: 0 > > > > > [plustek] usb_ReadData() > > > > > [plustek] usb_ScanReadImage(3760) > > > > > [plustek] usb_ScanReadImage() done, result: 0 > > > > > [saned] do_scan: trying to write 3754 bytes to client > > > > > [saned] do_scan: wrote 3754 bytes to client > > > > > [saned] do_scan: trying to read 1521 bytes from scanner > > > > > [plustek] sane_read - read 1521 bytes > > > > > [saned] do_scan: read 1521 bytes from scanner > > > > > > > > > > Now these 1521 bytes should be sent to the frontend... > > > > > > > > > > [saned] do_scan: processing RPC request on fd 4 > > > > > [saned] process_request: waiting for request > > > > > [saned] process_request: bad status 22 > > > > > > > > > > saned thinks something has been sent to it by the control (not data) > > > > > connection. But when trying to decode what was sent it gets an error > > > > > when reading the first word. 22 is "invalid argument". That means that > > > > > no data could be read. Maybe xsane has crashed on the clent side > > > > > meanwhile? > > > > > > > > > > Usually during the scan nothing is sent to the control file descriptor. > > > > > > > > > > Anyway. As sane_cancel isn't called the reader_process in the plustek > > > > > backend isn't killed and the plustek backend gets confused. > > > > > > > > > > So my impression is that the problem is with xsane (or the net > > > > > frontend on windows) and the scanner lockup is just a consequence. > > > > > But I don't know why xsane (or the net backend) crashes. So maybe > > > > > finding out the details here may help- E.g. gdb xsane on the client or > > > > > enabling debugging for xsane and the net backend and looking at the > > > > > last few lines before the crash. > > > > > > > > > > Maybe the xsane and plustek maintainers can have a look at the > > > > > logfiles, too? > > > > > > > > > > Bye, > > > > > Henning > > > > > > > > > > > > > > > > > > > > > From dlw@hei.net Thu Jun 17 14:40:57 2004 From: dlw@hei.net (Don) Date: Thu, 17 Jun 2004 06:40:57 -0700 Subject: [sane-devel] Re: xsane-0.91 Message-ID: <40D19F69.2070207@hei.net> chmod a+rw /proc/bus/usb/002/002 did the trick but I guess it's temporary. How do I make it permanent? Don -- Please do not send or forward HTML's. From peter.jamrisko@advantel.cz Thu Jun 17 14:56:04 2004 From: peter.jamrisko@advantel.cz (=?ISO-8859-2?Q?Peter_Jamri=B9ko?=) Date: Thu, 17 Jun 2004 15:56:04 +0200 Subject: [sane-devel] LaserJet 3380 Message-ID: <40D1A2F4.50600@advantel.cz> Hi, I have a problem with HP LaserJet 3380 printer. Hpoj recognized it successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find it at all. Can someone help me with this? Thanks for help. Peter From andi.mclean@ntlworld.com Thu Jun 17 14:56:03 2004 From: andi.mclean@ntlworld.com (Andi McLean) Date: Thu, 17 Jun 2004 14:56:03 +0100 Subject: [sane-devel] JSane In-Reply-To: References: Message-ID: <200406171456.03998.andi.mclean@ntlworld.com> Hi all JSane version 0.5 has been released. I've added colour support, though not tested as I don't have a colour scanner. Please report / send bug fixes directly to me. It can be dowloaded from www.jsane.com Thanks Andi From sane@burnsorama.com Thu Jun 17 16:59:18 2004 From: sane@burnsorama.com (Dave Burns) Date: Thu, 17 Jun 2004 11:59:18 -0400 Subject: [sane-devel] Canon FS4000: image data is sensor data, not RGB? In-Reply-To: <20040617124741.3387.51756.Mailman@haydn.debian.org> I am making good progress reverse-engineering the SCSI protocol for this film scanner. I now have a short test program in C that scans film and I now have the challenge of decoding the image data returned. It appears to be raw sensor data. I don't have experience with many other scanners: is this typical of scanners to return raw data? Or maybe typical of film scanners but not flatbed? I have seen Dave Coffin's page on dcraw (http://www.cybercom.net/~dcoffin/dcraw/) which can decode sensor data to RGB but want to consult this list before I start to integrate his code in case anyone here has already done this and can offer tips/advice. Also, the image data appears to contain more data than expected. I.e. there is more data then there should be if I consider the size of my scanning window and work out the math. Is this typical and is it normal to have to interpolate to provide the user with expected results? db From henning@meier-geinitz.de Thu Jun 17 17:16:05 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 17 Jun 2004 18:16:05 +0200 Subject: [sane-devel] Re: xsane-0.91 In-Reply-To: <40D19F69.2070207@hei.net> References: <40D19F69.2070207@hei.net> Message-ID: <20040617161605.GF31800@meier-geinitz.de> Hi, On Thu, Jun 17, 2004 at 06:40:57AM -0700, Don wrote: > chmod a+rw /proc/bus/usb/002/002 did the trick but I guess it's temporary. > How do I make it permanent? man sane-usb, README.linux: http://www.sane-project.org/README.linux Bye, Henning From henning@meier-geinitz.de Thu Jun 17 17:18:38 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 17 Jun 2004 18:18:38 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <40D1A2F4.50600@advantel.cz> References: <40D1A2F4.50600@advantel.cz> Message-ID: <20040617161838.GG31800@meier-geinitz.de> Hi, On Thu, Jun 17, 2004 at 03:56:04PM +0200, Peter Jamriško wrote: > I have a problem with HP LaserJet 3380 printer. Hpoj recognized it > successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find it > at all. Can someone help me with this? Which kind of device is it (USB)? Please show us the output from sane-find-scanner -v -v If the device is detected by the hpoj backend, there is no need for sane-find-scanner. Bye, Henning From henning@meier-geinitz.de Thu Jun 17 17:25:33 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 17 Jun 2004 18:25:33 +0200 Subject: [sane-devel] Canon FS4000: image data is sensor data, not RGB? In-Reply-To: References: <20040617124741.3387.51756.Mailman@haydn.debian.org> Message-ID: <20040617162533.GH31800@meier-geinitz.de> Hi, On Thu, Jun 17, 2004 at 11:59:18AM -0400, Dave Burns wrote: > I am making good progress reverse-engineering the SCSI protocol for this > film scanner. I now have a short test program in C that scans film and I now > have the challenge of decoding the image data returned. It appears to be raw > sensor data. I don't have experience with many other scanners: is this > typical of scanners to return raw data? Or maybe typical of film scanners > but not flatbed? What do you mean exactly by "raw sensor data"? The format of the image data varies with the scanner chipset. Some scanners provide the calibrated and even gamma corrected data in the resolution you have selected. For others , calibration and gamma correction must be done by the backend. > Also, the image data appears to contain more data than expected. I.e. there > is more data then there should be if I consider the size of my scanning > window and work out the math. Is this typical and is it normal to have to > interpolate to provide the user with expected results? Most scanners can only do some fixed resolutions, e.g. 100, 300, and 600 dpi. So other resolutions are done by using the higher resolution and downsampling the result. Well, some windows drivers use the lower resolution and interpolate the missing pixels... This downsampling is sometimes done in the scanner, som,etimes it must be done by the backend. Some scanners can only scan in fixed window steps, e.g. the number of pixels must be a multiple of 64 or similar. Bye, Henning From henning@meier-geinitz.de Thu Jun 17 17:34:44 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 17 Jun 2004 18:34:44 +0200 Subject: [sane-devel] Installation oddities... In-Reply-To: <200406170855.16452.gerhard@gjaeger.de> References: <200406170855.16452.gerhard@gjaeger.de> Message-ID: <20040617163444.GI31800@meier-geinitz.de> Hi, On Thu, Jun 17, 2004 at 08:55:16AM +0200, Gerhard Jaeger wrote: > on my SuSE distributions, I used to overwrite the existing and always > outdated SANE-RPMs, by using the following configure command: > ./configure --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --infodir=/usr/share/info > > This works pretty well up to sane-1.0.13, while checking 1.0.14 I noticed, > that the links in /usr/lib/sane to the new libs are no longer updated > during the installation step - did anything change there? No. As far as I can see there is no change in the install target of backend/Makefile.in that could cause such a behaviour. In 1.0.11 we created such links manually but this is done by libtool nowerdays: lrwxrwxrwx 1 root staff 17 2004-06-16 18:09 /usr/local/lib/libsane.so -> libsane.so.1.0.14 lrwxrwxrwx 1 root staff 17 2004-06-16 18:09 /usr/local/lib/libsane.so.1 -> libsane.so.1.0.14 -rwxr-xr-x 1 root staff 84752 2004-06-16 18:09 /usr/local/lib/libsane.so.1.0.14 Bye, Henning From till.kamppeter@gmx.net Thu Jun 17 20:51:28 2004 From: till.kamppeter@gmx.net (Till Kamppeter) Date: Thu, 17 Jun 2004 21:51:28 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <20040617161838.GG31800@meier-geinitz.de> References: <40D1A2F4.50600@advantel.cz> <20040617161838.GG31800@meier-geinitz.de> Message-ID: <40D1F640.9050104@gmx.net> Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 17, 2004 at 03:56:04PM +0200, Peter Jamriško wrote: > >>I have a problem with HP LaserJet 3380 printer. Hpoj recognized it >>successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find it >>at all. Can someone help me with this? > > > Which kind of device is it (USB)? Please show us the output from > sane-find-scanner -v -v > > If the device is detected by the hpoj backend, there is no need for > sane-find-scanner. > > Bye, > Henning > The LaserJet 3380 is for sure an HPOJ device and so SANE shows it only with "scanimage -L", and that only after you have done "ptal-init setup" and started HPOJ. Till From sane@burnsorama.com Thu Jun 17 20:00:28 2004 From: sane@burnsorama.com (Dave Burns) Date: Thu, 17 Jun 2004 15:00:28 -0400 Subject: [sane-devel] Canon FS4000: image data is sensor data, not RGB? In-Reply-To: <20040617124741.3387.51756.Mailman@haydn.debian.org> Sorry, ignore this post. It's not raw data as I can now see an image with different scanning parameters. --------------------------------------------------------- I am making good progress reverse-engineering the SCSI protocol for this film scanner. I now have a short test program in C that scans film and I now have the challenge of decoding the image data returned. It appears to be raw sensor data. I don't have experience with many other scanners: is this typical of scanners to return raw data? Or maybe typical of film scanners but not flatbed? I have seen Dave Coffin's page on dcraw (http://www.cybercom.net/~dcoffin/dcraw/) which can decode sensor data to RGB but want to consult this list before I start to integrate his code in case anyone here has already done this and can offer tips/advice. Also, the image data appears to contain more data than expected. I.e. there is more data then there should be if I consider the size of my scanning window and work out the math. Is this typical and is it normal to have to interpolate to provide the user with expected results? db From ukd@xenon.pc.Uni-Koeln.DE Fri Jun 18 07:22:19 2004 From: ukd@xenon.pc.Uni-Koeln.DE (Ulrich Deiters) Date: Fri, 18 Jun 2004 08:22:19 +0200 (METDST) Subject: [sane-devel] Canon FS4000: image data is sensor data, not RGB? Message-ID: <200406180622.IAA08608@xenon.pc.Uni-Koeln.DE> Do you receive 3 * 2 bytes per pixel? The FS2710S also produces 2 bytes, of which 12 bit are significant, in the order RRGGBB. The Canon-SCSI backend contains some portions that convert these raw data to the usual 8 bit representation. Perhaps this code can be modified to fit your case. Regards, Ulrich Deiters From C.W.J.Lemmens@its.tudelft.nl Fri Jun 18 08:47:15 2004 From: C.W.J.Lemmens@its.tudelft.nl (Kees Lemmens) Date: Fri, 18 Jun 2004 09:47:15 +0200 Subject: [sane-devel] strange rattle in epson 610 with 2.6.7 =?iso-8859-15?q?kernel=0A?= Message-ID: <200406180947.15367.C.W.J.Lemmens@its.tudelft.nl> Hi, I have an Epson Perfection 610 which worked fine for 2 years with 2.2.x and 2.4.x. Today I compiled 2.6.7 and now it suddenly produces strange and alarming sounds after the scan is finished and it returns to initial position. I thought the scanner failed, but after rebooting in 2.4.26 it works fine again, so I am afraid it must be something in the 2.6.x kernel combined with the sane 1.0.12 backend that I use (the one provided with Slackware 9.1). Any suggestions ? Should I just install the latest backend or is it something else ? -- Bye, Kees Lemmens. ----------------------------------------------------------------------- NOTICE: I consider all HTML based email as SPAM : forward => trash From peter.jamrisko@advantel.cz Fri Jun 18 10:00:03 2004 From: peter.jamrisko@advantel.cz (=?UTF-8?B?UGV0ZXIgSmFtcmnFoWtv?=) Date: Fri, 18 Jun 2004 11:00:03 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <40D1F640.9050104@gmx.net> References: <40D1A2F4.50600@advantel.cz> <20040617161838.GG31800@meier-geinitz.de> <40D1F640.9050104@gmx.net> Message-ID: <40D2AF13.4080705@advantel.cz> This is a multi-part message in MIME format. --------------060908000209020204000404 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi, Thanks for help. Printer is connected via parallel port. I tried scanimage -L, but with no result. I'm sending attachments. I hope you will see them (if you don't see them, let me know I'll resend them in body). There is output from ptal-init, rpm -qa | grep ptal / hpoj / sane, sane-find-scanner -v -v, scanimage -L and dll.conf from directory /etc/sane.d/. I'm using Mandrake 9.1, kernel 2.4.21-0.13mdk. I also installed xojpanel which correctly shows me display contents. Btw, dysplay messages are in czech language (maybe it doesn't relate to my prblem). Thanks. Peter. Till Kamppeter wrote: > Henning Meier-Geinitz wrote: > >> Hi, >> >> On Thu, Jun 17, 2004 at 03:56:04PM +0200, Peter Jamriško wrote: >> >>> I have a problem with HP LaserJet 3380 printer. Hpoj recognized it >>> successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find >>> it at all. Can someone help me with this? >> >> >> >> Which kind of device is it (USB)? Please show us the output from >> sane-find-scanner -v -v >> >> If the device is detected by the hpoj backend, there is no need for >> sane-find-scanner. >> >> Bye, >> Henning >> > > The LaserJet 3380 is for sure an HPOJ device and so SANE shows it only > with "scanimage -L", and that only after you have done "ptal-init > setup" and started HPOJ. > > Till > --------------060908000209020204000404 Content-Type: text/plain; name="scanimage" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="scanimage" c2NhbmltYWdlIC1MCgpObyBzY2FubmVycyB3ZXJlIGlkZW50aWZpZWQuIElmIHlvdSB3ZXJl IGV4cGVjdGluZyBzb21ldGhpbmcgZGlmZmVyZW50LApjaGVjayB0aGF0IHRoZSBzY2FubmVy IGlzIHBsdWdnZWQgaW4sIHR1cm5lZCBvbiBhbmQgZGV0ZWN0ZWQgYnkgdGhlCnNhbmUtZmlu ZC1zY2FubmVyIHRvb2wgKGlmIGFwcHJvcHJpYXRlKS4gUGxlYXNlIHJlYWQgdGhlIGRvY3Vt ZW50YXRpb24Kd2hpY2ggY2FtZSB3aXRoIHRoaXMgc29mdHdhcmUgKFJFQURNRSwgRkFRLCBt YW5wYWdlcykuCg== --------------060908000209020204000404 Content-Type: text/plain; name="dll.conf" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="dll.conf" IyBlbmFibGUgdGhlIG5leHQgbGluZSBpZiB5b3Ugd2FudCB0byBhbGxvdyBhY2Nlc3MgdGhy b3VnaCB0aGUgbmV0d29yazoKbmV0CmFiYXRvbgphZ2ZhZm9jdXMKYXBwbGUKYXZpc2lvbgph cnRlYwphcnRlY19lcGx1czQ4dQphczZlCmJoCmNhbm9uCmNhbm9uNjMwdQojY2Fub25fcHAK Y29vbHNjYW4KY29vbHNjYW4yCiNkYzI1CiNkYzIxMAojZGMyNDAKZG1jCmVwc29uCmZ1aml0 c3UKZ3Q2OHh4CmhwCmhwNDIwMApocHNqNXMKbGVvCm1hdHN1c2hpdGEKbWljcm90ZWsKbWlj cm90ZWsyCm11c3RlawojbXVzdGVrX3BwCm11c3Rla191c2IKbmVjCnBpZQpwaW50CnBsdXN0 ZWsKI3BubQpxY2FtCnJpY29oCnM5MDM2CnNjZXB0cmUKc2hhcnAKc20zNjAwCnNuYXBzY2Fu CnNwMTVjCiNzdDQwMAp0YW1hcmFjawp0ZWNvMQp0ZWNvMgp0ZWNvMwojdGVzdAp1bWF4CiN1 bWF4X3BwCnVtYXgxMjIwdQp2NGwKdmljZW8KIwojIFRoZSBmb2xsb3dpbmcgYmFja2VuZHMg YXJlIG5vdCBpbmNsdWRlZCBpbiB0aGUgc2FuZS1iYWNrZW5kcyBkaXN0cmlidXRpb24KIyBJ ZiB5b3Ugd2FudCB0byB1c2UgdGhlbSwgZG93bmxvYWQgdGhlbSBmcm9tIHRoZWlyIHdlYnBh Z2VzIGFuZCByZWFkIHRoZWlyCiMgZG9jdW1lbnRhdGlvbiAKIwojIEhQIE9mZmljZUpldCBi YWNrZW5kIGhvbWVwYWdlOiBodHRwOi8vaHBvai5zZi5uZXQvCiMgVW5jb21tZW50IHRoZSBm b2xsb3dpbmcgbGluZSBpZiBocG9qIGlzIGluc3RhbGxlZDoKI2hwb2oKbmlhc2gKaHBvago= --------------060908000209020204000404 Content-Type: text/plain; name="find_scan" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="find_scan" c2FuZS1maW5kLXNjYW5uZXIgLXYtdgoKc2VhcmNoaW5nIGZvciBTQ1NJIHNjYW5uZXJzOgpj aGVja2luZyAvZGV2L3NjYW5uZXIuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1l bnQpCmNoZWNraW5nIC9kZXYvc2cwLi4uIGZhaWxlZCB0byBvcGVuIChJbnZhbGlkIGFyZ3Vt ZW50KQpjaGVja2luZyAvZGV2L3NnMS4uLiBmYWlsZWQgdG8gb3BlbiAoSW52YWxpZCBhcmd1 bWVudCkKY2hlY2tpbmcgL2Rldi9zZzIuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJn dW1lbnQpCmNoZWNraW5nIC9kZXYvc2czLi4uIGZhaWxlZCB0byBvcGVuIChJbnZhbGlkIGFy Z3VtZW50KQpjaGVja2luZyAvZGV2L3NnNC4uLiBmYWlsZWQgdG8gb3BlbiAoSW52YWxpZCBh cmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZzUuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQg YXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2c2Li4uIGZhaWxlZCB0byBvcGVuIChJbnZhbGlk IGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3NnNy4uLiBmYWlsZWQgdG8gb3BlbiAoSW52YWxp ZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZzguLi4gZmFpbGVkIHRvIG9wZW4gKEludmFs aWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2c5Li4uIGZhaWxlZCB0byBvcGVuIChJbnZh bGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3NnYS4uLiBmYWlsZWQgdG8gb3BlbiAoSW52 YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZ2IuLi4gZmFpbGVkIHRvIG9wZW4gKElu dmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2djLi4uIGZhaWxlZCB0byBvcGVuIChJ bnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3NnZC4uLiBmYWlsZWQgdG8gb3BlbiAo SW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZ2UuLi4gZmFpbGVkIHRvIG9wZW4g KEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2dmLi4uIGZhaWxlZCB0byBvcGVu IChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3NnZy4uLiBmYWlsZWQgdG8gb3Bl biAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZ2guLi4gZmFpbGVkIHRvIG9w ZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2dpLi4uIGZhaWxlZCB0byBv cGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3Nnai4uLiBmYWlsZWQgdG8g b3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZ2suLi4gZmFpbGVkIHRv IG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2dsLi4uIGZhaWxlZCB0 byBvcGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3NnbS4uLiBmYWlsZWQg dG8gb3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZ24uLi4gZmFpbGVk IHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2dvLi4uIGZhaWxl ZCB0byBvcGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3NncC4uLiBmYWls ZWQgdG8gb3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZ3EuLi4gZmFp bGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2dyLi4uIGZh aWxlZCB0byBvcGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3Nncy4uLiBm YWlsZWQgdG8gb3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZ3QuLi4g ZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2d1Li4u IGZhaWxlZCB0byBvcGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3Nndi4u LiBmYWlsZWQgdG8gb3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9zZ3cu Li4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvc2d4 Li4uIGZhaWxlZCB0byBvcGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3Nn eS4uLiBmYWlsZWQgdG8gb3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi9z Z3ouLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCiAgIyBObyBTQ1NJIHNj YW5uZXJzIGZvdW5kLiBJZiB5b3UgZXhwZWN0ZWQgc29tZXRoaW5nIGRpZmZlcmVudCwgbWFr ZSBzdXJlIHRoYXQKICAjIHlvdSBoYXZlIGxvYWRlZCBhIFNDU0kgZHJpdmVyIGZvciB5b3Vy IFNDU0kgYWRhcHRlci4KICAjIEFsc28geW91IG5lZWQgc3VwcG9ydCBmb3IgU0NTSSBHZW5l cmljIChzZykgaW4geW91ciBvcGVyYXRpbmcgc3lzdGVtLgogICMgSWYgdXNpbmcgTGludXgs IHRyeSAibW9kcHJvYmUgc2ciLgoKc2VhcmNoaW5nIGZvciBVU0Igc2Nhbm5lcnM6CmNoZWNr aW5nIC9kZXYvdXNiL3NjYW5uZXIuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1l bnQpCmNoZWNraW5nIC9kZXYvdXNiL3NjYW5uZXIwLi4uIGZhaWxlZCB0byBvcGVuIChJbnZh bGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3VzYi9zY2FubmVyMS4uLiBmYWlsZWQgdG8g b3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi91c2Ivc2Nhbm5lcjIuLi4g ZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvdXNiL3Nj YW5uZXIzLi4uIGZhaWxlZCB0byBvcGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAv ZGV2L3VzYi9zY2FubmVyNC4uLiBmYWlsZWQgdG8gb3BlbiAoSW52YWxpZCBhcmd1bWVudCkK Y2hlY2tpbmcgL2Rldi91c2Ivc2Nhbm5lcjUuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQg YXJndW1lbnQpCmNoZWNraW5nIC9kZXYvdXNiL3NjYW5uZXI1Li4uIGZhaWxlZCB0byBvcGVu IChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3VzYi9zY2FubmVyNy4uLiBmYWls ZWQgdG8gb3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi91c2Ivc2Nhbm5l cjguLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYv dXNiL3NjYW5uZXI5Li4uIGZhaWxlZCB0byBvcGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVj a2luZyAvZGV2L3VzYi9zY2FubmVyMTAuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJn dW1lbnQpCmNoZWNraW5nIC9kZXYvdXNiL3NjYW5uZXIxMS4uLiBmYWlsZWQgdG8gb3BlbiAo SW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi91c2Ivc2Nhbm5lcjEyLi4uIGZhaWxl ZCB0byBvcGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3VzYi9zY2FubmVy MTMuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYv dXNiL3NjYW5uZXIxNC4uLiBmYWlsZWQgdG8gb3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hl Y2tpbmcgL2Rldi91c2Ivc2Nhbm5lcjE1Li4uIGZhaWxlZCB0byBvcGVuIChJbnZhbGlkIGFy Z3VtZW50KQpjaGVja2luZyAvZGV2L3VzYnNjYW5uZXIuLi4gZmFpbGVkIHRvIG9wZW4gKElu dmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvdXNic2Nhbm5lcjAuLi4gZmFpbGVkIHRv IG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvdXNic2Nhbm5lcjEuLi4g ZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvdXNic2Nh bm5lcjIuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9k ZXYvdXNic2Nhbm5lcjMuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNo ZWNraW5nIC9kZXYvdXNic2Nhbm5lcjQuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJn dW1lbnQpCmNoZWNraW5nIC9kZXYvdXNic2Nhbm5lcjUuLi4gZmFpbGVkIHRvIG9wZW4gKElu dmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvdXNic2Nhbm5lcjYuLi4gZmFpbGVkIHRv IG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvdXNic2Nhbm5lcjcuLi4g ZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvdXNic2Nh bm5lcjguLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9k ZXYvdXNic2Nhbm5lcjkuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNo ZWNraW5nIC9kZXYvdXNic2Nhbm5lcjEwLi4uIGZhaWxlZCB0byBvcGVuIChJbnZhbGlkIGFy Z3VtZW50KQpjaGVja2luZyAvZGV2L3VzYnNjYW5uZXIxMS4uLiBmYWlsZWQgdG8gb3BlbiAo SW52YWxpZCBhcmd1bWVudCkKY2hlY2tpbmcgL2Rldi91c2JzY2FubmVyMTIuLi4gZmFpbGVk IHRvIG9wZW4gKEludmFsaWQgYXJndW1lbnQpCmNoZWNraW5nIC9kZXYvdXNic2Nhbm5lcjEz Li4uIGZhaWxlZCB0byBvcGVuIChJbnZhbGlkIGFyZ3VtZW50KQpjaGVja2luZyAvZGV2L3Vz YnNjYW5uZXIxNC4uLiBmYWlsZWQgdG8gb3BlbiAoSW52YWxpZCBhcmd1bWVudCkKY2hlY2tp bmcgL2Rldi91c2JzY2FubmVyMTUuLi4gZmFpbGVkIHRvIG9wZW4gKEludmFsaWQgYXJndW1l bnQpCnRyeWluZyBsaWJ1c2I6CiAgIyBObyBVU0Igc2Nhbm5lcnMgZm91bmQuIElmIHlvdSBl eHBlY3RlZCBzb21ldGhpbmcgZGlmZmVyZW50LCBtYWtlIHN1cmUgdGhhdAogICMgeW91IGhh dmUgbG9hZGVkIGEgZHJpdmVyIGZvciB5b3VyIFVTQiBob3N0IGNvbnRyb2xsZXIgYW5kIGhh dmUgaW5zdGFsbGVkIGEKICAjIGtlcm5lbCBzY2FubmVyIG1vZHVsZS4KCiAgIyBTY2FubmVy cyBjb25uZWN0ZWQgdG8gdGhlIHBhcmFsbGVsIHBvcnQgb3Igb3RoZXIgcHJvcHJpZXRhcnkg cG9ydHMgY2FuJ3QgYmUKICAjIGRldGVjdGVkIGJ5IHRoaXMgcHJvZ3JhbS4KZG9uZQo= --------------060908000209020204000404 Content-Type: text/plain; name="ptal_init" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="ptal_init" CkN1cnJlbnRseSBkZWZpbmVkIGRldmljZSBuYW1lcyAoWypdPWRlZmF1bHQpOgpbKl0gIm1s YzpwYXI6aHBfTGFzZXJKZXRfMzM4MCIKICAgICAgICBNb2RlbCBpcyAiaHAgTGFzZXJKZXQg MzM4MCIuCiAgICAgICAgUGFyYWxsZWwtcG9ydCBiYXNlIGFkZHJlc3MgaXMgIjB4Mzc4Ii4K --------------060908000209020204000404 Content-Type: text/plain; name="rpm_hpoj" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="rpm_hpoj" bGliaHBvamlwMC0wLjkwLTRtZGsKbGlic2FuZS1ocG9qMC0wLjkwLTRtZGsKaHBvai0wLjkw LTRtZGsKbGliaHBvamlwMC1kZXZlbC0wLjkwLTRtZGsK --------------060908000209020204000404 Content-Type: text/plain; name="rpm_ptal" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="rpm_ptal" bGlicHRhbDAtMC45MC00bWRrCmxpYnB0YWwwLWRldmVsLTAuOTAtNG1kawo= --------------060908000209020204000404 Content-Type: text/plain; name="rpm_sane" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="rpm_sane" bGlic2FuZS1ocG9qMC0wLjkwLTRtZGsKeHNhbmUtMC45MC0ybWRrCmxpYnNhbmUxLTEuMC4x MS01bWRrCnNhbmVkLTEuMC4xMS01bWRrCmxpYnNhbmUxLWRldmVsLTEuMC4xMS01bWRrCnhz YW5lLWdpbXAtMC45MC0ybWRrCnNhbmUtYmFja2VuZHMtMS4wLjExLTVtZGsKc2FuZS1mcm9u dGVuZHMtMS4wLjEwLTFtZGsK --------------060908000209020204000404-- From henning@meier-geinitz.de Fri Jun 18 11:09:16 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 18 Jun 2004 12:09:16 +0200 Subject: [sane-devel] [ANNOUNCE] New release of gt68xx backend Message-ID: <20040618100916.GD28890@meier-geinitz.de> Hi everyone, I've just updated the gt68xx backend in CVS to version 1.0-61. The new version has quite a lot of changes so please test it if you own a scanner supported by this backend. Most important changes: - Mustek ScanExpress A3 USB is supported better now Warm-up and calibrationm should work now, however, some vertical stripes are still present - several minor fixes for other scanners - calibration in general avoids loops so it should be faster in some situations - CIS calibration should be better in avoiding stripes now. That work is not finished, however. - backtracking should occur less often - it's possible to select the color that's used to scan in gray/lineart mode now. More changes: http://www.meier-geinitz.de/sane/gt68xx-backend/gt68xx.CHANGES Unfortunately there are still some bugs. See the TODO list: http://www.meier-geinitz.de/sane/gt68xx-backend/gt68xx.TODO Download As usual from SANE CVS or the gt68xx page: http://www.meier-geinitz.de/sane/gt68xx-backend/ Or from a complete CVS snapshot: http://www.sane-project.org/snapshots/ Bye, Henning From Oliver.Rauch@Rauch-Domain.DE Sat Jun 19 12:44:12 2004 From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch) Date: 19 Jun 2004 13:44:12 +0200 Subject: [sane-devel] sane-backends-WIN32 Message-ID: <1087645452.3925.27.camel@Babylon7> Hello. Here a little experience report with sane-backends on WIN32. I used xsane-win32-0.94-sane-1.0.14-complete-no-gimp.zip for my tests with a UMAX Powerlook III SCSI-scanner on Windows 2000. I can create debugging messages with set SANE_DEBUG_UMAX=12 or set SANE_DEBUG_SANEI_SCSI=128 and scanimage. With xsane the stdout and sterr are not available because it is compiled as GUI. The status is: 1) xsane recognices the scanner without any changes. 2) The xsane interface comes up with correct options => INQUIRY is done without problems 3) Starting a scan or a preview makes two problems: a) SCSI Buffer size seems to be limited to 32KB, that is too small for this scanner in Color mode. Increasing the size by umax.conf options does not work. b) the START_SCAN command returns with I/O Error. The SET_WINDOW command and SEND_GAMMA_DATA in grayscale mode does not make any problems. It is encouraging that the INQUIRY, SET_WINDOW and SEND_GAMMA_DATA commands work without problems. I do not have an idea why the START_SCAN command fails. Please also report your experiences with sane-backends on WIN32. I think that we only have to do some little sourcecode changes to make it work. If we succeed with this then SANE gets the chance to be THE SCANNER DRIVER STANDARD and may be one day the manufacturers start writing their own (windows) drivers as SANE driver. Best regards Oliver From C.W.J.Lemmens@ewi.tudelft.nl Sat Jun 19 13:09:17 2004 From: C.W.J.Lemmens@ewi.tudelft.nl (Kees Lemmens) Date: Sat, 19 Jun 2004 14:09:17 +0200 Subject: [sane-devel] Re: strange rattle in epson 610 with 2.6.7 kernel In-Reply-To: <200406180940.03780.C.W.J.Lemmens@ewi.tudelft.nl> References: <200406180940.03780.C.W.J.Lemmens@ewi.tudelft.nl> Message-ID: <20040619120917.GA5840@dutind6.twi.tudelft.nl> Hi, First problem : rattle epson 610 (solved) ------------- Just installed sane 1.0.13 and this works fine under 2.6.7. However turning back to sane-1.0.12 immediately gives the alarming rattle back ... BTW: I used this script to test without having to reboot/reinstall : #################################################################### #!/bin/sh #SANE=/opt/sane-1.0.13 # Newer xsane release SANE=/usr/ # Standard sane-1.0.12 from Slackware 9.1 export LD_LIBRARY_PATH=$SANE/lib/ export LD_PRELOAD=$SANE/lib/libsane.so exec /usr/bin/xsane $* #################################################################### Second problem : compile 1.0.14 under Slackware fails -------------- Whatever I try sane-1.0.14 doesn't compile under Slackware 9.1 !! configure fails to detect the presence of basic routines like "strdup", "getenv" and others under Slackware 9.1, thereby making it impposible to compile (at least on my system). Any ideas ? giant:/tmp/sane-backends-1.0.14 252 % make making all in include make[1]: Entering directory /tmp/sane-backends-1.0.14/include' make[1]: Nothing to be done for all'. make[1]: Leaving directory /tmp/sane-backends-1.0.14/include' making all in lib make[1]: Entering directory /tmp/sane-backends-1.0.14/lib' gcc -c -DHAVE_CONFIG_H -I. -I. -I../include/sane -I../include -DPATH_SANE_CONFIG_DIR=/opt/sane-1.0.14//etc/sane.d -DPATH_SANE_DATA_DIR=/opt/sane-1.0.14//share -DV_MAJOR=1 -DV_MINOR=0 -I/usr/local/include/gphoto2 -g -O2 -W -Wall getenv.c getenv.c:13:4: #error "Missing getenv() on this platform. Please implement." getenv.c: In function getenv': getenv.c:6: warning: unused parameter name' make[1]: *** [getenv.o] Error 1 make[1]: Leaving directory /tmp/sane-backends-1.0.14/lib' make: *** [all-recursive] Error 1 giant:/tmp/sane-backends-1.0.14 254 % less include/sane/config.h ... /* Define to 1 if you have the getenv' function. */ /* #undef HAVE_GETENV */ ... /* Define to 1 if you have the strcasecmp' function. */ /* #undef HAVE_STRCASECMP */ /* Define to 1 if you have the strdup' function. */ /* #undef HAVE_STRDUP */ Bye, Kees Lemmens On Fri, Jun 18, 2004 at 09:40:03AM +0200, Kees Lemmens wrote: > Hi, > > I have an Epson Perfection 610 which worked fine for 2 years with 2.2.x > and 2.4.x. > > Today I compiled 2.6.7 and now it suddenly produces strange and alarming > sounds after the scan is finished and it returns to initial position. > > I thought the scanner failed, but after rebooting in 2.4.26 it works > fine again, so I am afraid it must be something in the 2.6.x kernel > combined with the sane 1.0.12 backend that I use (the one provided with > Slackware 9.1). > > Any suggestions ? Should I just install the latest backend or is it > something else ? > > -- > Bye, > Kees Lemmens. > ----------------------------------------------------------------------- > NOTICE: I consider all HTML based email as SPAM : forward => trash From C.W.J.Lemmens@ewi.tudelft.nl Sat Jun 19 14:48:11 2004 From: C.W.J.Lemmens@ewi.tudelft.nl (Kees Lemmens) Date: Sat, 19 Jun 2004 15:48:11 +0200 Subject: [sane-devel] Re: strange rattle in epson 610 / compile problem 1.0.14 on slackware 9.1 In-Reply-To: <20040619120917.GA5840@dutind6.twi.tudelft.nl> References: <200406180940.03780.C.W.J.Lemmens@ewi.tudelft.nl> <20040619120917.GA5840@dutind6.twi.tudelft.nl> Message-ID: <20040619134811.GA6200@dutind6.twi.tudelft.nl> Hi, My problem compiling sane-1.0.14 under Slackware 9.1 is solved : Someone added gphoto2 to the default libraries since 1.0.14 ! However, "configure" found libgphoto2 because of an old gphoto2-config in /usr/local/bin but WASN'T able to find libgphoto2.so at compile time ! This made the test compilation for getenv, strdup and others fail, thereby making it completely impossible to install the backends. What should be improved IMO : configure should only decide to use libgphoto2 if it is able to compile and link a program using these libraries and it should disable gphoto2 in all other cases. Relying on the presence of gphoto2-config is not enough IMO. For now I configured using : ./configure --prefix=/opt/sane-1.0.14 --without-gphoto2 BTW: sane-1.0.14 works fine now ;) Bye, Kees Lemmens. On Sat, Jun 19, 2004 at 02:09:17PM +0200, Kees Lemmens wrote: > Hi, > Second problem : compile 1.0.14 under Slackware fails > -------------- > > Whatever I try sane-1.0.14 doesn't compile under Slackware 9.1 !! > configure fails to detect the presence of basic routines like "strdup", > "getenv" and others under Slackware 9.1, thereby making it impposible to > compile (at least on my system). > > Any ideas ? > > giant:/tmp/sane-backends-1.0.14 252 % make > making all in include > make[1]: Entering directory /tmp/sane-backends-1.0.14/include' > make[1]: Nothing to be done for all'. > make[1]: Leaving directory /tmp/sane-backends-1.0.14/include' > making all in lib > make[1]: Entering directory /tmp/sane-backends-1.0.14/lib' > gcc -c -DHAVE_CONFIG_H -I. -I. -I../include/sane -I../include > -DPATH_SANE_CONFIG_DIR=/opt/sane-1.0.14//etc/sane.d > -DPATH_SANE_DATA_DIR=/opt/sane-1.0.14//share -DV_MAJOR=1 -DV_MINOR=0 > -I/usr/local/include/gphoto2 -g -O2 -W -Wall getenv.c > getenv.c:13:4: #error "Missing getenv() on this platform. Please implement." > getenv.c: In function getenv': > getenv.c:6: warning: unused parameter name' > make[1]: *** [getenv.o] Error 1 > make[1]: Leaving directory /tmp/sane-backends-1.0.14/lib' > make: *** [all-recursive] Error 1 > > giant:/tmp/sane-backends-1.0.14 254 % less include/sane/config.h > ... > /* Define to 1 if you have the getenv' function. */ > /* #undef HAVE_GETENV */ > ... > /* Define to 1 if you have the strcasecmp' function. */ > /* #undef HAVE_STRCASECMP */ > > /* Define to 1 if you have the strdup' function. */ > /* #undef HAVE_STRDUP */ > -- Bye, Kees Lemmens. From psfales@fales-lorenz.net Sun Jun 20 00:33:57 2004 From: psfales@fales-lorenz.net (Peter Fales) Date: Sat, 19 Jun 2004 18:33:57 -0500 Subject: [sane-devel] Re: strange rattle in epson 610 / compile problem 1.0.14 on slackware 9.1 In-Reply-To: <20040619134811.GA6200@dutind6.twi.tudelft.nl> References: <200406180940.03780.C.W.J.Lemmens@ewi.tudelft.nl> <20040619120917.GA5840@dutind6.twi.tudelft.nl> <20040619134811.GA6200@dutind6.twi.tudelft.nl> Message-ID: <20040619233357.GA4693@fales-lorenz.net> On Sat, Jun 19, 2004 at 03:48:11PM +0200, Kees Lemmens wrote: > What should be improved IMO : > > configure should only decide to use libgphoto2 if it is able to compile and > link a program using these libraries and it should disable gphoto2 in all > other cases. Relying on the presence of gphoto2-config is not enough IMO. The latest CVS uses pkgconfig instead of gphoto2-config, but is still presumably subject to the same problem. I've submitted a fix to CVS to check and make sure that a program can be linked using the gphoto2 libraries before the gphoto2 backend will be enabled. -- Peter Fales Peter "at" fales-lorenz.net From mattias.ellert@tsl.uu.se Sun Jun 20 13:16:12 2004 From: mattias.ellert@tsl.uu.se (Mattias Ellert) Date: Sun, 20 Jun 2004 14:16:12 +0200 Subject: [sane-devel] New MacOS X binary packages Message-ID: <9EBC0590-C2B3-11D8-8FC2-0003930D2AFC@tsl.uu.se> Hi! I have today created a new set of SANE binary packages for MacOS X. The reason for this is that many things have been fixed in the code since I created the previous version: 1. sanei_scsi now handles SCSI devices with multiple LUNs correctly on MacOS X. 2. sane-find-scanner now works for SCSI scanners on MacOS X. 3. the last backends that still used fork instead of sanei_thread have been converted. (At least I believe there is noone left, but I haven't read every line of code in the repository. If you find a backend still using fork please inform me.) If you have had problems due to any of the reasons above, please test the new packages. The packages are available at http://www.ellert.se/twain-sane/ Mattias From sietse@cs.rug.nl Sun Jun 20 13:44:19 2004 From: sietse@cs.rug.nl (Sietse Achterop) Date: Sun, 20 Jun 2004 14:44:19 +0200 Subject: [sane-devel] HP 7450C libusb problems (a little bit more info) Message-ID: <40D586A3.2060307@cs.rug.nl> Hello, Concerning the bulk timeouts seen with the avision backend amongst others here a little bit more info. It is a follow up of my earlier report in http://lists.alioth.debian.org/pipermail/sane-devel/2004-June/011182.html First: with SANE_DEBUG_SANEI_USB=255 some more info is given when the timeout occurs: (this is mostly after 1 or 2 successful bulk transfers) [sanei_usb] sanei_usb_read_bulk: trying to read 22656 bytes USB error: error reading from bulk endpoint 0x83: Invalid or incomplete multibyte or wide character [sanei_usb] sanei_usb_read_bulk: read failed: Invalid or incomplete multibyte or wide character USB error: could not clear/halt ep 131: Protocol error I found the "USB error" originating in libusb, but I can't find where the "Invalid or incomplete .." message comes from. So I can't see whether it maybe is significant. Second: after "modprobe uhci_hcd debug=2" (or 3) NO extra information is put into /var/log/kern.log Finally, is there anything else that I could do or test? I was hoping to make a smaller testcase than the test.c program in sane-backends/frontend Greetings, Sietse From Nikolas.Arend@gmx.net Sun Jun 20 17:48:54 2004 From: Nikolas.Arend@gmx.net (Nikolas.Arend@gmx.net) Date: Sun, 20 Jun 2004 18:48:54 +0200 (MEST) Subject: [sane-devel] Canoscan Lide 80 and 5200F Message-ID: <21831.1087750134@www11.gmx.net> Hi there, I found some rumours about someone having the canoscan lide 80 working under SuSE linux. He said he used a driver for the 5200F (which is relatively new and according to sane unsupported at the moment) and also others on the list reported that this worked fine. It sounds more like a hoax since I haven't found anything about lide 80 and a working sane backend/driver so far; however, if there would be a possibility to run the lide 80 under linux which was overlooked so far by most people, I'd rather appreciate to know about it. Unfortunately the mailing list is in German, you can find the post here: http://www.linux-club.de/viewtopic.php?p=9278#9278 Could someone please comment on this (tell me if you need help with an english translation)? Thanx, Nick. -- +++ Jetzt WLAN-Router für alle DSL-Einsteiger und Wechsler +++ GMX DSL-Powertarife zudem 3 Monate gratis* http://www.gmx.net/dsl From nathanaelnoblet@hotmail.com Sun Jun 20 18:30:41 2004 From: nathanaelnoblet@hotmail.com (Nathanael Noblet) Date: Sun, 20 Jun 2004 17:30:41 +0000 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. Message-ID: Hello I'm running a RHEL 3 clone (tao-linux). I've upgraded my sane-backends to 1.0.14, frontends to 1.0.12 and xsane to .91. I'm using plustek_pp in direct mode (with libieee1284). I can't seem to get any further along getting the scanner working. I've set the debug to max, but I don't know what it is doing. In both cases "xsane -d plustek_pp:/dev/parport0" and "scanimage -d plustek_pp:/dev/parport0" go through and seem to detect the scanner and stop at the CCD type I've included the debug log. What can I do? When it gets to the last line below, it just sits there, with xsane, I don't get any more dialog boxes, CPU usages is about 90% for that one program regardless of whether it is scanimage or xsane. DEBUGLOG= [sanei_debug] Setting debug level of plustek_pp to 255. [plustek_pp] PlustekPP backend V0.01-8, part of sane-backends 1.0.14 [plustek_pp] ># Plustek-PP SANE Backend configuration file< [plustek_pp] ># For use with Plustek parallel-port scanners< [plustek_pp] >#< [plustek_pp] >< [plustek_pp] >#< [plustek_pp] ># user either [direct] or [kernel] to access the scanner< [plustek_pp] ># when using [kernel], device specifies the device-node, which is created< [plustek_pp] ># by the kernel-module loader (applies only to Linux)< [plustek_pp] ># when using [direct], device is used to set the parallel-port base address< [plustek_pp] ># or a device-name suitable for libieee1284, i.e. parport0< [plustek_pp] >#< [plustek_pp] >#[direct]< [plustek_pp] >#device 0x378< [plustek_pp] >#device /dev/parport0< [plustek_pp] >#< [plustek_pp] ># leave the default values as specified in /etc/modules.conf< [plustek_pp] >#< [plustek_pp] >#option warmup 15< [plustek_pp] >#option lOffOnEnd 1< [plustek_pp] >#option lampOff 120< [plustek_pp] ># model override switch, mostly for cosmetic changes, if the autodetection< [plustek_pp] ># does not work or could not work correctly< [plustek_pp] >#option mov 7< [plustek_pp] >< [plustek_pp] >#< [plustek_pp] ># example for accessing the scanner via libieee1284< [plustek_pp] >#< [plustek_pp] >[direct]< [plustek_pp] >device parport0< [plustek_pp] Decoding device name >parport0< [plustek_pp] >option warmup 15< [plustek_pp] Decoding option >warmup< [plustek_pp] >option lOffOnEnd 1< [plustek_pp] Decoding option >lOffOnEnd< [plustek_pp] >option lampOff 120< [plustek_pp] Decoding option >lampOff< [plustek_pp] >< [plustek_pp] >#< [plustek_pp] ># example for accessing the scanner via the kernel module< [plustek_pp] >#< [plustek_pp] >#[kernel]< [plustek_pp] >#device /dev/pt_drv< [plustek_pp] >#< [plustek_pp] >#option warmup -1< [plustek_pp] >#option lOffOnEnd -1< [plustek_pp] >#option lampOff -1< [plustek_pp] attach (parport0, 0xbfffb140, (nil)) [plustek_pp] Device configuration: [plustek_pp] device name : >parport0< [plustek_pp] direct I/O : yes [plustek_pp] warmup : 15s [plustek_pp] lampOff : 120 [plustek_pp] lampOffOnEnd : yes [plustek_pp] model override: 0 [plustek_pp] --------------------- [plustek_pp] drvopen() [plustek_pp] ptdrvInit(0) [plustek_pp] Init settings done [plustek_pp] ScanData = 0x08054638 [plustek_pp] Assigning port handle 0 [plustek_pp] ptdrvOpen(port=0x0) [plustek_pp] Try to claim the parport [plustek_pp] Setting SPP-mode [plustek_pp] Setting PS/2-mode [plustek_pp] Setting EPP-mode [plustek_pp] We're using libIEEE1284 I/O [plustek_pp] Starting Scanner-Autodetection [plustek_pp] ************ DETECTP48xx ************ [plustek_pp] ModelSet4800() [plustek_pp] modelInitPageSettings() [plustek_pp] A4 set [plustek_pp] ModelSet4800() done. [plustek_pp] P48xxInitAsic() [plustek_pp] DacInitialize() [plustek_pp] ImageInitialize() [plustek_pp] IOFuncInitialize() [plustek_pp] IOInitialize() [plustek_pp] * using readfunction >fnEPPRead< [plustek_pp] MotorInitialize() [plustek_pp] ResetPort() [plustek_pp] Test 0x55 [plustek_pp] Test 0xAA [plustek_pp] Compare data=0x7f and status=0xf, port=0x0 [plustek_pp] p48xxReadWriteTest() [plustek_pp] Found a 96001 ASIC at Reg 0x13 [plustek_pp] ModelSet4800() [plustek_pp] modelInitPageSettings() [plustek_pp] A4 set [plustek_pp] ModelSet4800() done. [plustek_pp] Moving 32 bytes to scanner, IODELAY = 0... [plustek_pp] ... done. [plustek_pp] p48xxCheck4800Memory() [plustek_pp] Moving 1280 bytes to scanner, IODELAY = 0... [plustek_pp] ... done. [plustek_pp] Putting Scanner (ASIC 96001/3) into Idle-Mode [plustek_pp] detectScannerConnection() returns 0. [plustek_pp] p48xxSetupScannerVariables() [plustek_pp] No ASIC 97003 found. [plustek_pp] Status-Register = 0x8F [plustek_pp] Scanner has Full/Half Stepping drive [plustek_pp] CCD is SONY Type _________________________________________________________________ MSN Premium helps eliminate e-mail viruses. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines From mtropicl@optonline.net Sun Jun 20 19:47:15 2004 From: mtropicl@optonline.net (Fritz Lang) Date: Sun, 20 Jun 2004 14:47:15 -0400 Subject: [sane-devel] help with Epson 636U and Panther Message-ID: --Boundary_(ID_p+SPobHZmn0YVFoBUf7Imw) Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT Hello all, I tried getting this to work under Jag, but I've since stepped up to Panther. I installed: libusb.pkg sane-backends.pkg TWAIN-SANE-Interface.pkg I edited the sane.d/epson and added "usb" then: I ran: 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=0x04b8 [EPSON], product=0x0101 [Perfection636]) at libusb:001:002-04b8-0101-ff-ff # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. 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). scanimage > test.pnm scanimage: no SANE devices found I'd like to get this to work with OmniPage Pro X. Thanks for your help, Fritz -- Yes, I work in entertainment. It's not because I turned down the CEO spot on the NYSE. --Boundary_(ID_p+SPobHZmn0YVFoBUf7Imw) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT help with Epson 636U and Panther
Hello all,
I tried getting this to work under Jag, but I've since stepped up to Panther.

I installed:
libusb.pkg
sane-backends.pkg
TWAIN-SANE-Interface.pkg

I edited the sane.d/epson and added "usb"

then:

I ran:
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=0x04b8 [EPSON], product=0x0101 [Perfection636]) at libusb:001:002-04b8-0101-ff-ff
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

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).

scanimage > test.pnm
scanimage: no SANE devices found

I'd like to get this to work with OmniPage Pro X.

Thanks for your help,

Fritz
--
Yes, I work in entertainment.
It's not because I turned down the CEO spot on the NYSE.
--Boundary_(ID_p+SPobHZmn0YVFoBUf7Imw)-- From gerhard@gjaeger.de Mon Jun 21 08:51:47 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Mon, 21 Jun 2004 09:51:47 +0200 Subject: [sane-devel] Patching of maintained code by others... Message-ID: <200406210951.47667.gerhard@gjaeger.de> Hi list, while doing a CVS update this morning, I found my plustek code patched. In general, I do not have any problems on that, but I think that a short message on that would be of great help - or did I miss something? Ciao, Gerhard From peter.jamrisko@advantel.cz Mon Jun 21 09:10:35 2004 From: peter.jamrisko@advantel.cz (=?UTF-8?B?UGV0ZXIgSmFtcmnFoWtv?=) Date: Mon, 21 Jun 2004 10:10:35 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <40D2AF13.4080705@advantel.cz> References: <40D1A2F4.50600@advantel.cz> <20040617161838.GG31800@meier-geinitz.de> <40D1F640.9050104@gmx.net> <40D2AF13.4080705@advantel.cz> Message-ID: <40D697FB.1040609@advantel.cz> Hi all, This is output of scanimage -L (with export SANE_DEBUG_DLL=128 and export PTAL_DEBUG=2 ) with HP LaserJet 3380. I can print, but i cannot scan. /var/log/messages: ---------------------------------------------------- Jun 21 12:01:47 prtest ptal-mlcd: ERROR at ParPort.cpp:176, dev=, pid=1006, e=11 statusWaitSetClear(event=6) timed out, expected set/clear=0x40/0x00, got=0x38, currentMode=0x100! Jun 21 12:01:47 prtest ptal-mlcd: ERROR at ParPort.cpp:882, dev=, pid=1006, e=11 setModes: negotiate(0x10) failed! Jun 21 12:01:47 prtest ptal-mlcd: ERROR at ExMgr.cpp:3155, dev=, pid=1006, e=11 llioSetup: setModes failed! Jun 21 12:01:47 prtest ptal-mlcd: ERROR at ExMgr.cpp:2508, dev=, pid=1006, e=11 Couldn't find device: llioSetup failed! Jun 21 12:01:48 prtest ptal-mlcd: ERROR at ParPort.cpp:176, dev=, pid=1006, e=11 statusWaitSetClear(event=6) timed out, expected set/clear=0x40/0x00, got=0x38, currentMode=0x100! Jun 21 12:01:48 prtest ptal-mlcd: ERROR at ParPort.cpp:882, dev=, pid=1006, e=11 setModes: negotiate(0x10) failed! Jun 21 12:01:48 prtest ptal-mlcd: ERROR at ExMgr.cpp:3155, dev=, pid=1006, e=11 llioSetup: setModes failed! Jun 21 12:01:48 prtest ptal-mlcd: ERROR at ExMgr.cpp:2508, dev=, pid=1006, e=11 Couldn't find device: llioSetup failed! ---------------------------------------------------- stdoutput: ---------------------------------------------------- [sanei_debug] Setting debug level of dll to 128. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `hpoj' [dll] load: searching backend `hpoj' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-hpoj.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-hpoj.so.1' [dll] init: initializing backend `hpoj' ptalInit(): debug level set to 2. ptalInit() ptalDeviceAdd(mlc:par:hp_LaserJet_3380): dev=0x08052D70. ptalDeviceProbe: dev=<.>. ptalDeviceOpen(.): missing colon! ptalDeviceProbe: dev=<..>. ptalDeviceOpen(..): missing colon! ptalDeviceProbe: dev=. ptalMlcDeviceOpen(mlc:par:hp_LaserJet_3380): found matching dev=0x08052D70 (mlc:par:hp_LaserJet_3380). ptalDeviceProbe: dev=. ptalDeviceOpen(default-device): missing colon! [dll] init: backend `hpoj' is version 1.0.6 hpoj: sane_hpoj_get_devices hpoj:mlc:par:hp_LaserJet_3380: sane_hpoj_open ptalMlcDeviceOpen(mlc:par:hp_LaserJet_3380): found matching dev=0x08052D70 (mlc:par:hp_LaserJet_3380). ptalChannelAllocate(dev=0x08052D70): chan=0x08058480. ptalChannelSetRemoteService(chan=0x08058480,serviceType=2,socketID=0,serviceName=<>) ptalChannelSetPacketSizes(chan=0x08058480,desiredHPSize=256,desiredPHSize=8192) ptalChannelAllocate(dev=0x08052D70): chan=0x080584F0. ptalChannelSetRemoteService(chan=0x080584F0,serviceType=3,socketID=0,serviceName=) ptalChannelSetErrorHandling(chan=0x080584F0,retryCount=0,retryDelay=0) ptalMlcDeviceGetDeviceIDString(mlc:par:hp_LaserJet_3380): unsuccessful status=13! hpoj:mlc:par:hp_LaserJet_3380: device ID string=<> hpoj:mlc:par:hp_LaserJet_3380: hpojConnOpen ptalChannelOpen(chan=0x08058480): provider failed open! hpoj:mlc:par:hp_LaserJet_3380: hpojConnClose ptalChannelClose(chan=0x08058480) ptalChannelClose(chan=0x08058480): not open! ptalPmlClose(dev=0x08052D70) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! hpoj:mlc:par:hp_LaserJet_3380: hpojConnClose ptalChannelClose(chan=0x08058480) ptalChannelClose(chan=0x08058480): not open! ptalPmlClose(dev=0x08052D70) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! [dll] sane_exit: exiting [dll] sane_exit: calling backend `hpoj's exit function hpoj: sane_hpoj_exit ptalDone() ptalDeviceDelete(dev=0x08052D70) ptalDeviceClose(dev=0x08052D70) ptalChannelDeallocate(chan=0x08058480) ptalChannelClose(chan=0x08058480) ptalChannelClose(chan=0x08058480): not open! ptalChannelDeallocate(chan=0x080584F0) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! [dll] sane_exit: finished 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). ---------------------------------------------------- Any idea? Thanks for help. Peter. From peter.jamrisko@advantel.cz Mon Jun 21 09:53:42 2004 From: peter.jamrisko@advantel.cz (=?UTF-8?B?UGV0ZXIgSmFtcmnFoWtv?=) Date: Mon, 21 Jun 2004 10:53:42 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <40D697FB.1040609@advantel.cz> References: <40D1A2F4.50600@advantel.cz> <20040617161838.GG31800@meier-geinitz.de> <40D1F640.9050104@gmx.net> <40D2AF13.4080705@advantel.cz> <40D697FB.1040609@advantel.cz> Message-ID: <40D6A216.1040606@advantel.cz> Meanwhile I changed cable connected to the printer and I got another output: ------------------------------------------------------------------ [sanei_debug] Setting debug level of dll to 128. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `hpoj' [dll] load: searching backend `hpoj' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-hpoj.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-hpoj.so.1' [dll] init: initializing backend `hpoj' ptalInit(): debug level set to 2. ptalInit() ptalDeviceAdd(mlc:par:hp_LaserJet_3380): dev=0x08052D70. ptalDeviceProbe: dev=<.>. ptalDeviceOpen(.): missing colon! ptalDeviceProbe: dev=<..>. ptalDeviceOpen(..): missing colon! ptalDeviceProbe: dev=. ptalMlcDeviceOpen(mlc:par:hp_LaserJet_3380): found matching dev=0x08052D70 (mlc:par:hp_LaserJet_3380). ptalDeviceProbe: dev=. ptalDeviceOpen(default-device): missing colon! [dll] init: backend `hpoj' is version 1.0.6 hpoj: sane_hpoj_get_devices hpoj:mlc:par:hp_LaserJet_3380: sane_hpoj_open ptalMlcDeviceOpen(mlc:par:hp_LaserJet_3380): found matching dev=0x08052D70 (mlc:par:hp_LaserJet_3380). ptalChannelAllocate(dev=0x08052D70): chan=0x08058480. ptalChannelSetRemoteService(chan=0x08058480,serviceType=2,socketID=0,serviceName=<>) ptalChannelSetPacketSizes(chan=0x08058480,desiredHPSize=256,desiredPHSize=8192) ptalChannelAllocate(dev=0x08052D70): chan=0x080584F0. ptalChannelSetRemoteService(chan=0x080584F0,serviceType=3,socketID=0,serviceName=) ptalChannelSetErrorHandling(chan=0x080584F0,retryCount=0,retryDelay=0) hpoj:mlc:par:hp_LaserJet_3380: device ID string= hpoj:mlc:par:hp_LaserJet_3380: hpojConnOpen ptalChannelOpen(chan=0x08058480): fd=3. hpoj:mlc:par:hp_LaserJet_3380: hpojResetScanner hpoj:mlc:par:hp_LaserJet_3380: hpojSclSendCommand(cmd=11110, param=0, punc=<*>, letter1=, letter2=) hpoj:mlc:par:hp_LaserJet_3380: Sending SCL command <E>> ptalChannelWrite(chan=0x08058480,buffer=0xBFFFDDC0,count=2) ptalChannelWrite(chan=0x08058480,buffer=0xBFFFDDC0,count=2) returns 2. _ptalChannelSelect(chan=0x08058480) returns 0, errno=2, n=4, timeout=0xBFFFCAF0, tv_sec=0, tv_usec=0. ptalPmlAllocate(dev=0x08052D70) ptalPmlAllocate(dev=0x08052D70) returns obj=0x08058560. ptalPmlSetID(obj=0x08058560) ptalPmlSetID(obj=0x08058560) returns OK. ptalPmlOpen(dev=0x08052D70) ptalChannelAllocate(dev=0x08052D70): chan=0x08058DC0. ptalChannelSetRemoteService(chan=0x08058DC0,serviceType=4,socketID=0,serviceName=<>) ptalChannelOpen(chan=0x08058DC0): fd=4. hpoj:mlc:par:hp_LaserJet_3380: Using SCL protocol. hpoj:mlc:par:hp_LaserJet_3380: hpojSclSendCommand(cmd=10886, param=18, punc=<*>, letter1=, letter2=) _ptalChannelSelect(chan=0x08058480) returns 0, errno=2, n=4, timeout=0xBFFFC8D0, tv_sec=0, tv_usec=0. hpoj:mlc:par:hp_LaserJet_3380: Sending SCL command <*s18E>> ptalChannelWrite(chan=0x08058480,buffer=0xBFFFDBA0,count=6) ptalChannelWrite(chan=0x08058480,buffer=0xBFFFDBA0,count=6) returns 6. _ptalChannelSelect(chan=0x08058480) returns 0, errno=2, n=4, timeout=0xBFFFDA10, tv_sec=0, tv_usec=0. ptalSclChannelRead(chan=0x08058480): ptalChannelReadTimeout(buffer=0xBFFFDDF0,count=256) returns 0, errno=2. hpoj:mlc:par:hp_LaserJet_3380: Got response (len=0) <>. hpoj:mlc:par:hp_LaserJet_3380: hpojSclInquire(cmd=10886,param=18) didn't get expected response of <*s18d>! hpoj:mlc:par:hp_LaserJet_3380: hpojConnClose ptalChannelClose(chan=0x08058480) ptalPmlClose(dev=0x08052D70) ptalChannelClose(chan=0x08058DC0) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! [dll] sane_exit: exiting [dll] sane_exit: calling backend `hpoj's exit function hpoj: sane_hpoj_exit ptalDone() ptalDeviceDelete(dev=0x08052D70) ptalDeviceClose(dev=0x08052D70) ptalPmlDeallocate(obj=0x08058560) ptalChannelDeallocate(chan=0x08058480) ptalChannelClose(chan=0x08058480) ptalChannelClose(chan=0x08058480): not open! ptalChannelDeallocate(chan=0x080584F0) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! ptalChannelDeallocate(chan=0x08058DC0) ptalChannelClose(chan=0x08058DC0) ptalChannelClose(chan=0x08058DC0): not open! [dll] sane_exit: finished 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). ------------------------------------------------------------------ This looks better, but scanner still wasn't found. From pmsguevarra@yahoo.com Mon Jun 21 10:57:17 2004 From: pmsguevarra@yahoo.com (Peter Mark Guevarra) Date: Mon, 21 Jun 2004 02:57:17 -0700 (PDT) Subject: [sane-devel] different scan outputs for different Linux distributions Message-ID: <20040621095717.15033.qmail@web41015.mail.yahoo.com> --0-520547155-1087811837=:13124 Content-Type: text/plain; charset=us-ascii Hi, Has anyone encountered this problem wherein the same frontend, xsane or xscanimage for instance, has different outputs for RedHat, and SuSE or Mandrake? Same settings were used in the frontend but different outputs resulted for different distributions, one is darker/brighter than the other. Also, in the case of using only one Linux Distribution, RedHat for example, is it expected to have the same output for the different SANE frontends given the default settings for each frontend? Thanks in advance, PMG --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. --0-520547155-1087811837=:13124 Content-Type: text/html; charset=us-ascii
Hi,
 
Has anyone encountered this problem wherein the same frontend, xsane or xscanimage for instance, has different outputs for RedHat, and SuSE or Mandrake?  Same settings were used in the frontend but different outputs resulted for different distributions, one is darker/brighter than the other. 
 
Also, in the case of using only one Linux Distribution, RedHat for example,
is it expected to have the same output for the different SANE frontends given the default settings for each frontend?
 
Thanks in advance,
PMG

Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish. --0-520547155-1087811837=:13124-- From dave.burns@comcast.net Mon Jun 21 14:12:50 2004 From: dave.burns@comcast.net (Dave Burns) Date: Mon, 21 Jun 2004 09:12:50 -0400 Subject: [sane-devel] sane-backends-WIN32 In-Reply-To: <20040619124852.7560.90441.Mailman@haydn.debian.org> I hope I'm not completely out of context since I only get the digest and have not been following this thread. But the following caught my eye: "With xsane the stdout and sterr are not available because it is compiled as GUI." As a WIN32 programmer for years, I know this doesn't have to be true. Use the following code to open a Win32 console window and rewire stdout/stderr to its output. Wrap the whole thing in a conditional that's true if you want debug output. Hope this helps. If I'm off topic, apologies. db #include #include /* For _open_osfhandle( ) */ #include /* For _O_TEXT */ { int hCrt_StdOut; int hCrt_StdErr; FILE *hf_stdout; FILE *hf_stderr; /* First create the console. This only opens the window. This will fail if we are already running from a console window (which means we don't need to connect any output streams). */ if (AllocConsole()) { HANDLE stdoutBuffer; CONSOLE_SCREEN_BUFFER_INFO bufferInfo; /* Now connect the Win32 STD_OUTPUT pipe to the c-runtime stdout stream */ stdoutBuffer = GetStdHandle(STD_OUTPUT_HANDLE); hCrt_StdOut = _open_osfhandle((long) stdoutBuffer, _O_TEXT); hf_stdout = _fdopen(hCrt_StdOut, "w"); *stdout = *hf_stdout; /* setvbuf(stdout, NULL, _IONBF, 0);*/ /* Now connect the Win32 STD_ERROR pipe to the c-runtime stderr stream */ hCrt_StdErr = _open_osfhandle((long) GetStdHandle(STD_ERROR_HANDLE), _O_TEXT); hf_stderr = _fdopen(hCrt_StdErr, "w"); *stderr = *hf_stderr; setvbuf(stderr, NULL, _IONBF, 0); /* now we increase the buffer size to 9999 lines. We only do this if we created a console so that we don't mess with a user's existing console. */ GetConsoleScreenBufferInfo(stdoutBuffer, &bufferInfo); if (bufferInfo.dwSize.Y < 9999) bufferInfo.dwSize.Y = 9999; SetConsoleScreenBufferSize(stdoutBuffer, bufferInfo.dwSize); } } -----Original Message----- From: sane-devel-admin@lists.alioth.debian.org [mailto:sane-devel-admin@lists.alioth.debian.org] On Behalf Of sane-devel-request@lists.alioth.debian.org From: Oliver Rauch To: sane-devel Organization: Date: 19 Jun 2004 13:44:12 +0200 Subject: [sane-devel] sane-backends-WIN32 Hello. Here a little experience report with sane-backends on WIN32. I used xsane-win32-0.94-sane-1.0.14-complete-no-gimp.zip for my tests with a UMAX Powerlook III SCSI-scanner on Windows 2000. I can create debugging messages with set SANE_DEBUG_UMAX=12 or set SANE_DEBUG_SANEI_SCSI=128 and scanimage. With xsane the stdout and sterr are not available because it is compiled as GUI. The status is: 1) xsane recognices the scanner without any changes. 2) The xsane interface comes up with correct options => INQUIRY is done without problems 3) Starting a scan or a preview makes two problems: a) SCSI Buffer size seems to be limited to 32KB, that is too small for this scanner in Color mode. Increasing the size by umax.conf options does not work. b) the START_SCAN command returns with I/O Error. The SET_WINDOW command and SEND_GAMMA_DATA in grayscale mode does not make any problems. It is encouraging that the INQUIRY, SET_WINDOW and SEND_GAMMA_DATA commands work without problems. I do not have an idea why the START_SCAN command fails. Please also report your experiences with sane-backends on WIN32. I think that we only have to do some little sourcecode changes to make it work. If we succeed with this then SANE gets the chance to be THE SCANNER DRIVER STANDARD and may be one day the manufacturers start writing their own (windows) drivers as SANE driver. Best regards Oliver --__--__-- Message: 2 Date: Sat, 19 Jun 2004 14:09:17 +0200 From: Kees Lemmens To: sane-devel@lists.alioth.debian.org Subject: [sane-devel] Re: strange rattle in epson 610 with 2.6.7 kernel Hi, First problem : rattle epson 610 (solved) ------------- Just installed sane 1.0.13 and this works fine under 2.6.7. However turning back to sane-1.0.12 immediately gives the alarming rattle back ... BTW: I used this script to test without having to reboot/reinstall : #################################################################### #!/bin/sh #SANE=/opt/sane-1.0.13 # Newer xsane release SANE=/usr/ # Standard sane-1.0.12 from Slackware 9.1 export LD_LIBRARY_PATH=$SANE/lib/ export LD_PRELOAD=$SANE/lib/libsane.so exec /usr/bin/xsane $* #################################################################### Second problem : compile 1.0.14 under Slackware fails -------------- Whatever I try sane-1.0.14 doesn't compile under Slackware 9.1 !! configure fails to detect the presence of basic routines like "strdup", "getenv" and others under Slackware 9.1, thereby making it impposible to compile (at least on my system). Any ideas ? giant:/tmp/sane-backends-1.0.14 252 % make making all in include make[1]: Entering directory /tmp/sane-backends-1.0.14/include' make[1]: Nothing to be done for all'. make[1]: Leaving directory /tmp/sane-backends-1.0.14/include' making all in lib make[1]: Entering directory /tmp/sane-backends-1.0.14/lib' gcc -c -DHAVE_CONFIG_H -I. -I. -I../include/sane -I../include -DPATH_SANE_CONFIG_DIR=/opt/sane-1.0.14//etc/sane.d -DPATH_SANE_DATA_DIR=/opt/sane-1.0.14//share -DV_MAJOR=1 -DV_MINOR=0 -I/usr/local/include/gphoto2 -g -O2 -W -Wall getenv.c getenv.c:13:4: #error "Missing getenv() on this platform. Please implement." getenv.c: In function getenv': getenv.c:6: warning: unused parameter name' make[1]: *** [getenv.o] Error 1 make[1]: Leaving directory /tmp/sane-backends-1.0.14/lib' make: *** [all-recursive] Error 1 giant:/tmp/sane-backends-1.0.14 254 % less include/sane/config.h ... /* Define to 1 if you have the getenv' function. */ /* #undef HAVE_GETENV */ ... /* Define to 1 if you have the strcasecmp' function. */ /* #undef HAVE_STRCASECMP */ /* Define to 1 if you have the strdup' function. */ /* #undef HAVE_STRDUP */ Bye, Kees Lemmens On Fri, Jun 18, 2004 at 09:40:03AM +0200, Kees Lemmens wrote: > Hi, > > I have an Epson Perfection 610 which worked fine for 2 years with > 2.2.x and 2.4.x. > > Today I compiled 2.6.7 and now it suddenly produces strange and > alarming sounds after the scan is finished and it returns to initial position. > > I thought the scanner failed, but after rebooting in 2.4.26 it works > fine again, so I am afraid it must be something in the 2.6.x kernel > combined with the sane 1.0.12 backend that I use (the one provided > with Slackware 9.1). > > Any suggestions ? Should I just install the latest backend or is it > something else ? > > -- > Bye, > Kees Lemmens. > ---------------------------------------------------------------------- > - > NOTICE: I consider all HTML based email as SPAM : forward => trash --__--__-- _______________________________________________ sane-devel mailing list sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel End of sane-devel Digest From Oliver.Rauch@Rauch-Domain.DE Mon Jun 21 19:35:21 2004 From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch) Date: 21 Jun 2004 20:35:21 +0200 Subject: [sane-devel] sane-backends-WIN32 In-Reply-To: <200406211642.i5LGgf3E010181@mailin.webmailer.de> References: <200406211642.i5LGgf3E010181@mailin.webmailer.de> Message-ID: <1087842921.2122.3.camel@Babylon7> Thnaks for that hint. I will test if this works with cygwin. Oliver Am Mon, 2004-06-21 um 15.12 schrieb Dave Burns: > I hope I'm not completely out of context since I only get the digest and > have not been following this thread. But the following caught my eye: > > "With xsane the stdout and sterr are not available because it is compiled > as GUI." > > As a WIN32 programmer for years, I know this doesn't have to be true. Use > the following code to open a Win32 console window and rewire stdout/stderr > to its output. Wrap the whole thing in a conditional that's true if you want > debug output. Hope this helps. If I'm off topic, apologies. > > db > > > > #include > #include /* For _open_osfhandle( ) */ > #include /* For _O_TEXT */ > > { > int hCrt_StdOut; > int hCrt_StdErr; > FILE *hf_stdout; > FILE *hf_stderr; > > /* First create the console. This only opens the window. This will fail if > we are already running from a console window (which means we don't need > to connect any output streams). */ > > if (AllocConsole()) { > HANDLE stdoutBuffer; > CONSOLE_SCREEN_BUFFER_INFO bufferInfo; > > /* Now connect the Win32 STD_OUTPUT pipe to the c-runtime stdout stream > */ > > stdoutBuffer = GetStdHandle(STD_OUTPUT_HANDLE); > hCrt_StdOut = _open_osfhandle((long) stdoutBuffer, _O_TEXT); > hf_stdout = _fdopen(hCrt_StdOut, "w"); > *stdout = *hf_stdout; > /* setvbuf(stdout, NULL, _IONBF, 0);*/ > > /* Now connect the Win32 STD_ERROR pipe to the c-runtime stderr stream > */ > > hCrt_StdErr = _open_osfhandle((long) GetStdHandle(STD_ERROR_HANDLE), > _O_TEXT); > hf_stderr = _fdopen(hCrt_StdErr, "w"); > *stderr = *hf_stderr; > setvbuf(stderr, NULL, _IONBF, 0); > > /* now we increase the buffer size to 9999 lines. We only do this > if we created a console so that we don't mess with a user's > existing console. */ > > GetConsoleScreenBufferInfo(stdoutBuffer, &bufferInfo); > if (bufferInfo.dwSize.Y < 9999) > bufferInfo.dwSize.Y = 9999; > SetConsoleScreenBufferSize(stdoutBuffer, bufferInfo.dwSize); > } > } > > > -----Original Message----- > From: sane-devel-admin@lists.alioth.debian.org > [mailto:sane-devel-admin@lists.alioth.debian.org] On Behalf Of > sane-devel-request@lists.alioth.debian.org > From: Oliver Rauch > To: sane-devel > Organization: > Date: 19 Jun 2004 13:44:12 +0200 > Subject: [sane-devel] sane-backends-WIN32 > > Hello. > > Here a little experience report with sane-backends on WIN32. > I used xsane-win32-0.94-sane-1.0.14-complete-no-gimp.zip for my tests with a > UMAX Powerlook III SCSI-scanner on Windows 2000. > > I can create debugging messages with > set SANE_DEBUG_UMAX=12 > or > set SANE_DEBUG_SANEI_SCSI=128 > and scanimage. > > With xsane the stdout and sterr are not available because it is compiled as > GUI. > > The status is: > 1) xsane recognices the scanner without any changes. > 2) The xsane interface comes up with correct options > => INQUIRY is done without problems > 3) Starting a scan or a preview makes two problems: > a) SCSI Buffer size seems to be limited to 32KB, > that is too small for this scanner in Color mode. > Increasing the size by umax.conf options does not work. > b) the START_SCAN command returns with I/O Error. > > The SET_WINDOW command and SEND_GAMMA_DATA in grayscale mode does not make > any problems. > > It is encouraging that the INQUIRY, SET_WINDOW and SEND_GAMMA_DATA commands > work without problems. I do not have an idea why the START_SCAN command > fails. > > Please also report your experiences with sane-backends on WIN32. > I think that we only have to do some little sourcecode changes to make it > work. If we succeed with this then SANE gets the chance to be THE SCANNER > DRIVER STANDARD and may be one day the manufacturers start writing their own > (windows) drivers as SANE driver. > > Best regards > Oliver > > > > --__--__-- > > Message: 2 > Date: Sat, 19 Jun 2004 14:09:17 +0200 > From: Kees Lemmens > To: sane-devel@lists.alioth.debian.org > Subject: [sane-devel] Re: strange rattle in epson 610 with 2.6.7 kernel > > Hi, > > First problem : rattle epson 610 (solved) > ------------- > > Just installed sane 1.0.13 and this works fine under 2.6.7. However turning > back to sane-1.0.12 immediately gives the alarming rattle back ... > > BTW: I used this script to test without having to reboot/reinstall : > #################################################################### > #!/bin/sh > > #SANE=/opt/sane-1.0.13 # Newer xsane release > SANE=/usr/ # Standard sane-1.0.12 from Slackware 9.1 > > export LD_LIBRARY_PATH=$SANE/lib/ > export LD_PRELOAD=$SANE/lib/libsane.so > > exec /usr/bin/xsane $* > #################################################################### > > Second problem : compile 1.0.14 under Slackware fails > -------------- > > Whatever I try sane-1.0.14 doesn't compile under Slackware 9.1 !! > configure fails to detect the presence of basic routines like "strdup", > "getenv" and others under Slackware 9.1, thereby making it impposible to > compile (at least on my system). > > Any ideas ? > > giant:/tmp/sane-backends-1.0.14 252 % make making all in include > make[1]: Entering directory /tmp/sane-backends-1.0.14/include' > make[1]: Nothing to be done for all'. > make[1]: Leaving directory /tmp/sane-backends-1.0.14/include' > making all in lib > make[1]: Entering directory /tmp/sane-backends-1.0.14/lib' > gcc -c -DHAVE_CONFIG_H -I. -I. -I../include/sane -I../include > -DPATH_SANE_CONFIG_DIR=/opt/sane-1.0.14//etc/sane.d > -DPATH_SANE_DATA_DIR=/opt/sane-1.0.14//share -DV_MAJOR=1 -DV_MINOR=0 > -I/usr/local/include/gphoto2 -g -O2 -W -Wall getenv.c > getenv.c:13:4: #error "Missing getenv() on this platform. Please > implement." > getenv.c: In function getenv': > getenv.c:6: warning: unused parameter name' > make[1]: *** [getenv.o] Error 1 > make[1]: Leaving directory /tmp/sane-backends-1.0.14/lib' > make: *** [all-recursive] Error 1 > > giant:/tmp/sane-backends-1.0.14 254 % less include/sane/config.h ... > /* Define to 1 if you have the getenv' function. */ > /* #undef HAVE_GETENV */ > ... > /* Define to 1 if you have the strcasecmp' function. */ > /* #undef HAVE_STRCASECMP */ > > /* Define to 1 if you have the strdup' function. */ > /* #undef HAVE_STRDUP */ > > > Bye, > Kees Lemmens > > On Fri, Jun 18, 2004 at 09:40:03AM +0200, Kees Lemmens wrote: > > Hi, > > > > I have an Epson Perfection 610 which worked fine for 2 years with > > 2.2.x and 2.4.x. > > > > Today I compiled 2.6.7 and now it suddenly produces strange and > > alarming sounds after the scan is finished and it returns to initial > position. > > > > I thought the scanner failed, but after rebooting in 2.4.26 it works > > fine again, so I am afraid it must be something in the 2.6.x kernel > > combined with the sane 1.0.12 backend that I use (the one provided > > with Slackware 9.1). > > > > Any suggestions ? Should I just install the latest backend or is it > > something else ? > > > > -- > > Bye, > > Kees Lemmens. > > ---------------------------------------------------------------------- > > - > > NOTICE: I consider all HTML based email as SPAM : forward => trash > > > > > --__--__-- > > _______________________________________________ > sane-devel mailing list > sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > > > End of sane-devel Digest > > From degreef@imec.be Mon Jun 21 20:54:03 2004 From: degreef@imec.be (Eddy De Greef) Date: Mon, 21 Jun 2004 21:54:03 +0200 Subject: [sane-devel] Question About Mustek 600CP scanner on Suse 9.1 In-Reply-To: <40CF1160.8040307@penguin-breeder.org>; from jochen@penguin-breeder.org on di, jun 15, 2004 at 17:10:24 +0200 References: <40CF1160.8040307@penguin-breeder.org> Message-ID: <20040621195403.GA3373@reddot.erps-kwerps.be> On 15-06-04 17:10:24 Jochen Eisinger wrote: > Neal Gamradt wrote: > > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5 > > from 'parport0' > > [...] > > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x00 > > from 'parport0' > > the backend gets the correct value first, but later the scanner only > returns the wrong value 0x00. To me this looks like the scanner got > confused or something. > > Eddy, could you have a look at this? After he compiled everything from source, upgraded his kernel, and altered the parport BIOS settings, Neal's problem disappeared. It's impossible to say what was the real problem, unfortunately. Best regards, Eddy From jochen@penguin-breeder.org Mon Jun 21 21:00:52 2004 From: jochen@penguin-breeder.org (Jochen Eisinger) Date: Mon, 21 Jun 2004 22:00:52 +0200 Subject: [sane-devel] Question About Mustek 600CP scanner on Suse 9.1 In-Reply-To: <20040621195403.GA3373@reddot.erps-kwerps.be> References: <40CF1160.8040307@penguin-breeder.org> <20040621195403.GA3373@reddot.erps-kwerps.be> Message-ID: <40D73E74.2000903@penguin-breeder.org> Hi, Eddy De Greef wrote: > After he compiled everything from source, upgraded his kernel, > and altered the parport BIOS settings, Neal's problem disappeared. > It's impossible to say what was the real problem, unfortunately. >From what I read on parport-devel this is a bug in the SuSE kernel regards -- jochen From brook@biology.nmsu.edu Tue Jun 22 00:36:25 2004 From: brook@biology.nmsu.edu (brook@biology.nmsu.edu) Date: Mon, 21 Jun 2004 17:36:25 -0600 Subject: [sane-devel] Epson Perfection 2400 Photo scanner problems In-Reply-To: <20040528172802.GG5312@meier-geinitz.de> References: <16558.46498.623574.314930@viola.nmsu.edu> <87hdu6ek1h.fsf@zen.epkowa.co.jp> <16562.2593.523307.32174@viola.nmsu.edu> <87smdpwe1c.fsf@zen.epkowa.co.jp> <20040528172802.GG5312@meier-geinitz.de> Message-ID: <16599.28921.259988.645168@viola.nmsu.edu> I'm slowly tracking down parts of the problem with my scanner. When I tried the NetBSD kernel scanner devices (/dev/uscanner*) I identified an issue with sane-find-scanner. It lacks any definition for NetBSD-specific kernel devices. I submitted a bug report (category tools) that provides a patch that fixes that. The remaining issue with using the kernel devices is getting the scanner information from the device driver. I'm looking into that, but if I hack in a hard-coded response to match the correct scanner everything works perfectly. I'm still not sure what is wrong with libusb, but I can get this scanner to work just fine (at least in 8-bit mode). I would very much appreciate it if someone will take the initiative and commit the patch to sane-find-scanner to include the NetBSD kernel devices. Thanks for your help. Cheers, Brook From jgato@lambdaux.com Tue Jun 22 12:00:44 2004 From: jgato@lambdaux.com (jose) Date: Tue, 22 Jun 2004 13:00:44 +0200 Subject: [sane-devel] Backends Database Message-ID: <1087902032.330.2.camel@localhost> Hello, Im a developer of the Linux Hardware Database Unification Project(http://sourceforge.net/projects/linuxhard/), a part of this Database will include information about scanners and backends. I would like to know if there is some DB about this or if all the information is included on the frames of the webpage of sane, because It will be very dificult to mantein the hardware DB if we have to visit the tables of the web to see the changes... I wish we could work together... thanks. From andras@users.sourceforge.net Tue Jun 22 12:23:15 2004 From: andras@users.sourceforge.net (Major A) Date: Tue, 22 Jun 2004 12:23:15 +0100 Subject: [sane-devel] list Message-ID: <20040622112315.GH11187@ventus.lan> Hi all, Sorry I've been out of touch for a while. The main reason was that I was busy doing other things, but also that list message delivery stopped a while ago without me noticing. I've now subscribed with a different address and it appears to be working OK now. Have there been any major events recently, especially related to the Coolscan2 driver? Andras From gerhard@gjaeger.de Tue Jun 22 15:35:21 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Tue, 22 Jun 2004 16:35:21 +0200 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. In-Reply-To: References: Message-ID: <200406221635.22006.gerhard@gjaeger.de> Hi, On Sunday 20 June 2004 19:30, Nathanael Noblet wrote: > Hello > I'm running a RHEL 3 clone (tao-linux). I've upgraded my sane-backends > to 1.0.14, frontends to 1.0.12 and xsane to .91. I'm using plustek_pp in > direct mode (with libieee1284). I can't seem to get any further along > getting the scanner working. I've set the debug to max, but I don't know > what it is doing. In both cases "xsane -d plustek_pp:/dev/parport0" and > "scanimage -d plustek_pp:/dev/parport0" go through and seem to detect the > scanner and stop at the CCD type I've included the debug log. What can I > do? probably nothing :-( All seems to look okay - I will check this @ home... You can try and set the port to SPP in BIOS and try again..... Ciao, Gerhard [SNIPSNAP] From nathanaelnoblet@hotmail.com Tue Jun 22 15:38:20 2004 From: nathanaelnoblet@hotmail.com (Nathanael Noblet) Date: Tue, 22 Jun 2004 14:38:20 +0000 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. Message-ID: > >probably nothing :-( >All seems to look okay - I will check this @ home... >You can try and set the port to SPP in BIOS and try again..... Okay, as a side note, I installed windows onto this same machine, to see if perhaps the scanner was shot, it is rather old. Unfortunately it worked perfectly. So I'd REALLY like to try to get it working... _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN Premium http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines From gerhard@gjaeger.de Tue Jun 22 15:46:13 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Tue, 22 Jun 2004 16:46:13 +0200 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. In-Reply-To: References: Message-ID: <200406221646.13667.gerhard@gjaeger.de> On Tuesday 22 June 2004 16:38, Nathanael Noblet wrote: > >probably nothing :-( > >All seems to look okay - I will check this @ home... > >You can try and set the port to SPP in BIOS and try again..... > > Okay, as a side note, I installed windows onto this same machine, to see if > perhaps the scanner was shot, it is rather old. Unfortunately it worked > perfectly. You can't imagine how I hate this sentence ;-) > So I'd REALLY like to try to get it working... Yes, I can imagine... You can also try and make the backend a kernel module - download the latest CVS snapshot, unpack the sources and go to sane-backends/doc/plustek call as root usere MakeModule.sh script to compile install and load the ptdrv module - then after successful loading, you should change the plustek_pp.conf Building the kernel module needs the kernel-sources proberly installed and configured on your box... I'm just curious, if the module get's loaded - as it's the same code, maybe I made a mistake when putting something to user space.... Ciao, Gerhard From henning@meier-geinitz.de Tue Jun 22 16:50:07 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 17:50:07 +0200 Subject: [sane-devel] Backends Database In-Reply-To: <1087902032.330.2.camel@localhost> References: <1087902032.330.2.camel@localhost> Message-ID: <20040622155007.GB9053@meier-geinitz.de> Hi, On Tue, Jun 22, 2004 at 01:00:44PM +0200, jose wrote: > Hello, Im a developer of the Linux Hardware Database Unification > Project(http://sourceforge.net/projects/linuxhard/), a part of this > Database will include information about scanners and backends. > > I would like to know if there is some DB about this or if all the > information is included on the frames of the webpage of sane, because It > will be very dificult to mantein the hardware DB if we have to visit the > tables of the web to see the changes... The information about supported (and not supported) scanners is contained in the *.desc files (e.g. doc/descriptions/mustek.desc). These files come with the sane-backends distribution. The current ones are in SANE CVS. Documentation of the format is in doc/descriptions.txt. The lists on the website are automatically generated from these lists by the tools/sane-desc program. It can also produce ASCI output. Maybe you can uses this output or modify that program to print the data you are interested in. Bye, Henning From henning@meier-geinitz.de Tue Jun 22 16:56:16 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 17:56:16 +0200 Subject: [sane-devel] list In-Reply-To: <20040622112315.GH11187@ventus.lan> References: <20040622112315.GH11187@ventus.lan> Message-ID: <20040622155616.GC9053@meier-geinitz.de> Hi, On Tue, Jun 22, 2004 at 12:23:15PM +0100, Major A wrote: > Sorry I've been out of touch for a while. The main reason was that I > was busy doing other things, but also that list message delivery > stopped a while ago without me noticing. I've now subscribed with a > different address and it appears to be working OK now. Strange. Unfortunately, alioth still doesn't sent any administrative messages (e.g. about mail problems) to me and all mails to sane-devel-admin are bounced. So I don't know the reason. > Have there been any major events recently, especially related to the > Coolscan2 driver? There are two bugs assigned to you in the bug tracker :-) Bye, Henning From andras@onepointfour.net Tue Jun 22 17:24:46 2004 From: andras@onepointfour.net (Major A) Date: Tue, 22 Jun 2004 17:24:46 +0100 Subject: [sane-devel] list In-Reply-To: <20040622155616.GC9053@meier-geinitz.de> References: <20040622112315.GH11187@ventus.lan> <20040622155616.GC9053@meier-geinitz.de> Message-ID: <20040622162445.GA13068@ventus.lan> > Strange. Unfortunately, alioth still doesn't sent any administrative > messages (e.g. about mail problems) to me and all mails to > sane-devel-admin are bounced. So I don't know the reason. > > > Have there been any major events recently, especially related to the > > Coolscan2 driver? > > There are two bugs assigned to you in the bug tracker :-) Great. One is a mystery to me (the LS-5000 is definitely NOT supported as it is, I'm working on it), the other is a patch (submitted yesterday) that I've been looking for for a while... Damn, why do things have to be in so many different places? Thanks for resubmitting that Debian bug report over here. Andras From henning@meier-geinitz.de Tue Jun 22 18:34:08 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:34:08 +0200 Subject: [sane-devel] Canoscan Lide 80 and 5200F In-Reply-To: <21831.1087750134@www11.gmx.net> References: <21831.1087750134@www11.gmx.net> Message-ID: <20040622173408.GI9053@meier-geinitz.de> Hi, On Sun, Jun 20, 2004 at 06:48:54PM +0200, Nikolas.Arend@gmx.net wrote: > Could someone please comment on this (tell me if you need help with an > english translation)? I haven't ever gotten any reliable report that the Canon LiDE 50 or 80 do work. Some people told me that these scanners are supported but after looking at their log files I found out that their scanners had the USB ids of Canon Lide 20 or 30. And surprisingly the owners of these scanners noticed that they own a Lide 20 or 30 when I asked them to look again at the name plate. I've been also poited to that forum but nobody told me: "yes, my Canon Lide 50 or 80 works with sane with the ... backend". So I think it's a hoax. Bye, Henning From henning@meier-geinitz.de Tue Jun 22 18:36:36 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:36:36 +0200 Subject: [sane-devel] help with Epson 636U and Panther In-Reply-To: References: Message-ID: <20040622173636.GJ9053@meier-geinitz.de> Hi, On Sun, Jun 20, 2004 at 02:47:15PM -0400, Fritz Lang wrote: > found USB scanner (vendor=0x04b8 [EPSON], product=0x0101 > scanimage -L > > No scanners were identified. If you were expecting something different, SANE_DEBUG_EPSON=255 scanimage -L may print some more details. Bye, Henning From henning@meier-geinitz.de Tue Jun 22 18:41:04 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:41:04 +0200 Subject: [sane-devel] Patching of maintained code by others... In-Reply-To: <200406210951.47667.gerhard@gjaeger.de> References: <200406210951.47667.gerhard@gjaeger.de> Message-ID: <20040622174104.GK9053@meier-geinitz.de> Hi, On Mon, Jun 21, 2004 at 09:51:47AM +0200, Gerhard Jaeger wrote: > while doing a CVS update this morning, I found my plustek code patched. > In general, I do not have any problems on that, but I think that a short > message on that would be of great help - or did I miss something? I also don't mind if others fix obvious bugs in my backends and also think that a notice to the backend maintainer is better. While I read the sane-commit mails that show the changes, I've already overlooked some of them. If many backends are changed, a mail to sane-devel is also ok in my opinion. Also, if a backend is developed in an external CVS the maintainer may overlook the previous change and just upload his newest version. So the fix gets lost. Bye, Henning From henning@meier-geinitz.de Tue Jun 22 18:43:53 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:43:53 +0200 Subject: [sane-devel] different scan outputs for different Linux distributions In-Reply-To: <20040621095717.15033.qmail@web41015.mail.yahoo.com> References: <20040621095717.15033.qmail@web41015.mail.yahoo.com> Message-ID: <20040622174353.GL9053@meier-geinitz.de> Hi, On Mon, Jun 21, 2004 at 02:57:17AM -0700, Peter Mark Guevarra wrote: > Has anyone encountered this problem wherein the same frontend, xsane > or xscanimage for instance, has different outputs for RedHat, and > SuSE or Mandrake? Same settings were used in the frontend but > different outputs resulted for different distributions, one is > darker/brighter than the other. I haven't heard about such a behaviour. Can you reproduce it with scanimage? Maybe the scanner wasn't warmed up completely in one of the tests? > Also, in the case of using only one Linux Distribution, RedHat for > example, is it expected to have the same output for the different > SANE frontends given the default settings for each frontend? Yes, if you don't use any of the color enhancement settings. E.g. make sure that xsane doesn't modify your gamma settings automatically. Bye, Henning From henning@meier-geinitz.de Tue Jun 22 18:47:06 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:47:06 +0200 Subject: [sane-devel] Epson Perfection 2400 Photo scanner problems In-Reply-To: <16599.28921.259988.645168@viola.nmsu.edu> References: <16558.46498.623574.314930@viola.nmsu.edu> <87hdu6ek1h.fsf@zen.epkowa.co.jp> <16562.2593.523307.32174@viola.nmsu.edu> <87smdpwe1c.fsf@zen.epkowa.co.jp> <20040528172802.GG5312@meier-geinitz.de> <16599.28921.259988.645168@viola.nmsu.edu> Message-ID: <20040622174706.GM9053@meier-geinitz.de> Hi, On Mon, Jun 21, 2004 at 05:36:25PM -0600, brook@biology.nmsu.edu wrote: > I'm slowly tracking down parts of the problem with my scanner. When I > tried the NetBSD kernel scanner devices (/dev/uscanner*) I identified > an issue with sane-find-scanner. It lacks any definition for > NetBSD-specific kernel devices. I submitted a bug report (category > tools) that provides a patch that fixes that. I've added that patch to CVS. Next time, please attach the patch to the bug report ("upload"), that way the patch can be downloaded and applied directly. Could you try if it works in the CVS version of sane now? > The remaining issue with using the kernel devices is getting the > scanner information from the device driver. I'm looking into that, > but if I hack in a hard-coded response to match the correct scanner > everything works perfectly. Some backends can cope with the kernel scanner driver not returning USB ids. E.g. by setting options in backend.conf or by otherwise telling the backend which scanner is actually connected. Bye, Henning From gerhard@gjaeger.de Thu Jun 24 09:09:39 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Thu, 24 Jun 2004 10:09:39 +0200 Subject: [sane-devel] Automatic update of the Webpages... Message-ID: <200406241009.39040.gerhard@gjaeger.de> Hi, how can the following site: http://www.sane-project.org/lists/sane-mfgs-cvs.html be updated? It contains currently the following sentence: "The following table summarizes the devices supported by sane-backends-1.0.13-cvs.", which is wrong... Ciao, Gerhard From gerhard@gjaeger.de Thu Jun 24 09:16:30 2004 From: gerhard@gjaeger.de (Gerhard Jaeger) Date: Thu, 24 Jun 2004 10:16:30 +0200 Subject: [sane-devel] Comprehensive overview... Message-ID: <200406241016.30645.gerhard@gjaeger.de> Hi list, while searching for some info about the HP2400c, I noticed, that it is not included in the unsupported.desc file... The search engine delivers a result, but for "simple" users who are not using the search engine, the information about the scanner will be not available... I think we need one page, where all the information we have is available, even if the scanner is supported by an external, experimental or no backend. My two cents... Gerhard From timo@dspsrv.com Thu Jun 24 10:44:26 2004 From: timo@dspsrv.com (Tim O'Callaghan) Date: Thu, 24 Jun 2004 11:44:26 +0200 Subject: [sane-devel] Canon IS-12 Scanner head (for canon BJC 50,55 & 80 printers) Message-ID: <40DAA27A.8020603@dspsrv.com> Hi, I recently bought an IS-12 Scanner head for my BJC 50, and was a bit surprised to find that it was not supported by Sane. Rather than break the seal on the packaging, i thought I'd ask a few questions here. 1. is anybody working on a back end for it? 2. if so, do they want any help? 3. if not, does anyone have any idea on the internals of the device? the unsupported scanner information is empty. ta, Tim. From faide@alphacent.com Thu Jun 24 12:49:24 2004 From: faide@alphacent.com (Florent Aide) Date: Thu, 24 Jun 2004 11:49:24 +0000 Subject: [sane-devel] donation / scanner support Message-ID: <40DABFC4.9030102@alphacent.com> Hello list, I have a Dell A920 (rebranded Lexmark X1150) that is currently marked on the website as not supported. Since I have two of these little things I am willing to donate one of them to the project in order to see scanner support for it. How can I do that ? Is someone willing to accept this donation and work on the scanner part of the Dell A920 ? The printer/scanner is new and in its box with everything (there just is no USB cable). The donation would graciously be made by Alpha Centauri, we have already agreed upon it internally. Best regards, Florent AIDE Alpha Centauri From ukd@xenon.pc.Uni-Koeln.DE Thu Jun 24 11:27:54 2004 From: ukd@xenon.pc.Uni-Koeln.DE (Ulrich Deiters) Date: Thu, 24 Jun 2004 12:27:54 +0200 (METDST) Subject: [sane-devel] Canon IS-12 Scanner head (for canon BJC 50,55 & 80 printers) Message-ID: <200406241027.MAA23233@xenon.pc.Uni-Koeln.DE> Hi Tim, what exactly is this IS-12 - an add-on device for a printer? How is it controlled by the computer - SCSI, USB or parallel port? Perhaps one of the existing backends can be used. Regards, Ulrich Deiters From timo@dspsrv.com Thu Jun 24 12:02:47 2004 From: timo@dspsrv.com (Tim O'Callaghan) Date: Thu, 24 Jun 2004 13:02:47 +0200 Subject: [sane-devel] Canon IS-12 Scanner head (for canon BJC 50,55 & 80 printers) In-Reply-To: <200406241027.MAA23233@xenon.pc.Uni-Koeln.DE> References: <200406241027.MAA23233@xenon.pc.Uni-Koeln.DE> Message-ID: <40DAB4D7.3070807@dspsrv.com> Ulrich Deiters wrote: > Hi Tim, > > what exactly is this IS-12 - an add-on device for a printer? the IS-12 is a kind of a printer cartridge. You put it where the normal ink cartridge would go, and it turns your ink jet printer into a scanner. http://www.canon.co.uk/for_home/product_finder/printers/accessories/scanner_cartridges/index.asp by this question i can assume you're not working on it :) > How is it controlled by the computer - SCSI, USB or parallel > port? Perhaps one of the existing backends can be used. > Its controlled via the parallel port, and it would be safe to assume that a back end exists for the scanner chip set. I would guess its a chip set that supports single pass, and that its controlled by prefixing the control commands with a printer command. I don't know what the chip set is, and to be honest i don't want to take apart a my brand new IS-12 to find out. A cursory google for information on the internals has come up empty, so i don't know how to proceed other than running a port scanner under windows. Is there a method for matching command streams to a backed? Tim. From picos132004@yahoo.co.uk Thu Jun 24 12:05:26 2004 From: picos132004@yahoo.co.uk (=?iso-8859-1?q?Ioan-Cosmin=20Pop?=) Date: Thu, 24 Jun 2004 12:05:26 +0100 (BST) Subject: [sane-devel] check-usb-chip request for help Message-ID: <20040624110526.5365.qmail@web25106.mail.ukl.yahoo.com> Hello everyone! I started (some time ago) to modify the program check-usb-chip to detect my scanner. It's a Mustek BearPaw 4800TA ProII. I know, I'm slow, but it's the best I can :( I apologize to everyone. Anyway, I came across one problem and I don't know how to handle it. Let me explain. I created the function "check_SQ113" to check the chip (http://picosconsult.topcities.com/downloads/check-usb-chip.c). I test the device descriptor and the endpoints. After that, I try to write a value (a four bytes array), like this: req[0] = 0x64; req[1] = 0x64; req[2] = 0x64; req[3] = 0x64; result = usb_bulk_write (handle, 0x01, req, 4, TIMEOUT); if (result <= 0) { if (verbose > 2) printf (" this is not a SQ-113 (Error during bulk write)\n"); finish_interface (handle); return 0; } then read it: result = usb_bulk_read (handle, 0x82, &res, 1, 1000); if (result <= 0) { if (verbose > 2) printf (" this is not a SQ-113 (Error during bulk read)\n"); finish_interface (handle); return 0; } but I get an error in usb_bulk_write() no matter what I do. I tried to chage the endpoint (not to use bulk but interrupt) but to no avail. So, my question is: can I get rid of this test? I see there are other functions that don't try to write/read something from the device. Is it safe to do this? I mean, all the other tests ("device descriptor" and "endpoints" pass OK). After some time, I looked over the page http://www.sane-project.org/unsupported/mustek-bearpaw-4800ta-pro-ii.html and I saw some other chips: 1. SQ [brand] SQ100A A335-9901 --- 2. UTC QGOB L6219 TB [O in 1st line may be a Zero] --- 3. ISSI [brand] IS42S16100A1-7T X11882000D 0336 ---- 4. SQ [brand] SQ113C 0335-1408 D0KNS-013 [Zeroes may be O] Does this mean I have to include tests specific to those chips, or they behave exactly like SQ113C? Again, I apologise for being slow... Thank you Cosmin ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com From nathanaelnoblet@hotmail.com Thu Jun 24 15:57:54 2004 From: nathanaelnoblet@hotmail.com (Nathanael Noblet) Date: Thu, 24 Jun 2004 14:57:54 +0000 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. Message-ID: >On Tuesday 22 June 2004 16:38, Nathanael Noblet wrote: > > Okay, as a side note, I installed windows onto this same machine, to see >if > > perhaps the scanner was shot, it is rather old. Unfortunately it worked > > perfectly. > >You can't imagine how I hate this sentence ;-) I can, and I understand, really I do. The reason for it though was this scanner was gifted to me, and since it was so old, I needed to find out if it even worked at all. Since I couldn't get linux working with it, I had to try the other one... >You can also try and make the backend a kernel module - download the latest >CVS snapshot, unpack the sources and go to >sane-backends/doc/plustek >call as root usere MakeModule.sh script to compile install and load the >ptdrv >module - then after successful loading, you should change the >plustek_pp.conf >Building the kernel module needs the kernel-sources proberly installed and >configured on your box... >I'm just curious, if the module get's loaded - as it's the same code, maybe >I >made a mistake when putting something to user space.... Will do, I'll report back anything that happens, Thanks for the work, and the response. -- Nathanael _________________________________________________________________ http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines From tnorth@bluewin.ch Thu Jun 24 18:19:50 2004 From: tnorth@bluewin.ch (Thibault North) Date: Thu, 24 Jun 2004 19:19:50 +0200 Subject: [sane-devel] CanoScan5000F backend project beginning soon... Message-ID: <40DB0D36.5090508@bluewin.ch> Good afternoon, As I said it some time ago, I am going to try and make the scanner Canon canoscan5000F work... This will begin probably beginning of July, as soon as my exams are done. I have then time to work with a friend which knows more C than I do :) I wanted to know if some of you where interested in helping us (if you have this scanner) or be available to answer our questions (using IRC ?) : we have never done a project like that and it is a little frightening :) If it is the case, please answer here of @ tnorth@bluewin.ch. An adress used to communicate : http://gna.org/projects/canoscan5000F Thanks ! Thibault North P.S to Henning Meier-Geinitz : could you please send me the Perl script we spoke about which is able to filter the log file from SniffUSB ? Thank you very much, Here is the sane-find-scanner -v -v : searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Access to resource has been denied) checking /dev/sg2... failed to open (Access to resource has been denied) checking /dev/sg3... failed to open (Access to resource has been denied) checking /dev/sg4... failed to open (Access to resource has been denied) checking /dev/sg5... failed to open (Access to resource has been denied) checking /dev/sg6... failed to open (Access to resource has been denied) checking /dev/sg7... failed to open (Access to resource has been denied) checking /dev/sg8... failed to open (Access to resource has been denied) checking /dev/sg9... failed to open (Access to resource has been denied) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Access to resource has been denied) checking /dev/sgc... failed to open (Access to resource has been denied) checking /dev/sgd... failed to open (Access to resource has been denied) checking /dev/sge... failed to open (Access to resource has been denied) checking /dev/sgf... failed to open (Access to resource has been denied) checking /dev/sgg... failed to open (Access to resource has been denied) checking /dev/sgh... failed to open (Access to resource has been denied) checking /dev/sgi... failed to open (Access to resource has been denied) checking /dev/sgj... failed to open (Access to resource has been denied) checking /dev/sgk... failed to open (Access to resource has been denied) checking /dev/sgl... failed to open (Access to resource has been denied) checking /dev/sgm... failed to open (Access to resource has been denied) checking /dev/sgn... failed to open (Access to resource has been denied) checking /dev/sgo... failed to open (Access to resource has been denied) checking /dev/sgp... failed to open (Access to resource has been denied) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11... failed to open (Invalid argument) checking /dev/usbscanner12... failed to open (Invalid argument) checking /dev/usbscanner13... failed to open (Invalid argument) checking /dev/usbscanner14... failed to open (Invalid argument) checking /dev/usbscanner15... failed to open (Invalid argument) trying libusb: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 1 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.04 iManufacturer 3 ((null)) iProduct 2 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 2 bInterval 12 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x04A9 idProduct 0x2212 bcdDevice 3.03 iManufacturer 2 ((null)) iProduct 3 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 10 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 0 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 3 (interrupt) wMaxPacketSize 1 bInterval 8 ms bRefresh 0 bSynchAddress 0 found USB scanner (vendor=0x04a9, product=0x2212) at libusb:004:002 bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 () iProduct 2 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 8 bInterval 255 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 () iProduct 2 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 8 bInterval 255 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 () iProduct 2 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 8 bInterval 255 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046D idProduct 0xC00E bcdDevice 17.10 iManufacturer 1 ((null)) iProduct 2 ((null)) iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 160 (Remote Wakeup) MaxPower 98 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 bInterfaceSubClass 1 bInterfaceProtocol 2 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 4 bInterval 10 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 224 bDeviceSubClass 1 bDeviceProtocol 1 bMaxPacketSize0 64 idVendor 0x413C idProduct 0x8000 bcdDevice 5.65 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 193 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 () bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 16 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 254 bInterfaceSubClass 1 bInterfaceProtocol 0 iInterface 0 () # 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. done From henning@meier-geinitz.de Thu Jun 24 17:25:47 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 24 Jun 2004 18:25:47 +0200 Subject: [sane-devel] Automatic update of the Webpages... In-Reply-To: <200406241009.39040.gerhard@gjaeger.de> References: <200406241009.39040.gerhard@gjaeger.de> Message-ID: <20040624162547.GA9387@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 10:09:39AM +0200, Gerhard Jaeger wrote: > how can the following site: > http://www.sane-project.org/lists/sane-mfgs-cvs.html The contents itsself is updated automatically ... > be updated? It contains currently the following sentence: > "The following table summarizes the devices supported by > sane-backends-1.0.13-cvs.", which is wrong... True. The reason is that with every CVS upload that changes a .desc file, "make" is run in the doc directory. However, for changing the version string, "configure" is also necessary. I don't want to do that everytime a commit is done so it's done manually. It's fixed now. The scripts for the automaic update of these lists (and a few other things) are in CVS (module CVSROOT) by the way. Bye, Henning From henning@meier-geinitz.de Thu Jun 24 17:44:10 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 24 Jun 2004 18:44:10 +0200 Subject: [sane-devel] Comprehensive overview... In-Reply-To: <200406241016.30645.gerhard@gjaeger.de> References: <200406241016.30645.gerhard@gjaeger.de> Message-ID: <20040624164410.GB9387@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 10:16:30AM +0200, Gerhard Jaeger wrote: > while searching for some info about the HP2400c, I noticed, that it is not > included in the unsupported.desc file... I'm also not really sure if putting all these genesys scanners into the genesys.desc file before they really work is a good idea. > The search engine delivers a result, but for "simple" users who are not using > the search engine, the information about the scanner will be not available... > I think we need one page, where all the information we have is available, even > if the scanner is supported by an external, experimental or no backend. That "one page" is the search engine. Years ago we had one big page that includes all the data ordered by backend only. The problem with that was that many "simple" users didn't notice that their scanner needed an external backend so they complained about the scanner not working even after installing sane-backends. That's the reason for the split between external and internal. The scanner search engine provides answers to the questions: "What's known about that scanner"? or "Is my scanner supported at all?" Stable/CVS manufacturer lists: "Which scanners are (un)supported by the stable/CVS version of SANE?" or: "Is my scanner supported by the sane-backends distribution"? Stable/CVS backend lists: "Which scanners are supported by a specific backend?" (mostly for developers) External backend lists: "Which scanners don't work with sane-backends but have external backends?" Older lists: "Does my scanner work without updating my older version of sane?" A lot of different lists but there is also a lot of different questions. I appreciate suggestions for a better presentation of that data. Bye, Henning From henning@meier-geinitz.de Thu Jun 24 17:55:47 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 24 Jun 2004 18:55:47 +0200 Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <20040624110526.5365.qmail@web25106.mail.ukl.yahoo.com> References: <20040624110526.5365.qmail@web25106.mail.ukl.yahoo.com> Message-ID: <20040624165547.GC9387@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 12:05:26PM +0100, Ioan-Cosmin Pop wrote: > I created the function "check_SQ113" to check the > chip > (http://picosconsult.topcities.com/downloads/check-usb-chip.c). > I test the device descriptor and the endpoints. After > that, I try to write a value (a four bytes array), What is this command or data intended to do? > but I get an error in usb_bulk_write() no matter what > I do. I tried to chage the endpoint (not to use bulk > but interrupt) but to no avail. First you must know what to send. I.e. you must know the protocol of the scanner and what commands to use or registers to set. Use a simple command (e.g. read the device identification or write and read a register value). > So, my question is: > can I get rid of this test? I see there are other > functions that don't try to write/read something from > the device. Is it safe to do this? Not really, at least if you want to be sure that you have correctly identified a chipset. The whole idea of the descriptor test is to avoid sending commands to a scanner that doesn't understand them. However, the final test if we really have found a secific chipset is done by communicating with the chipset. > After some time, I looked over the page > http://www.sane-project.org/unsupported/mustek-bearpaw-4800ta-pro-ii.html > and I saw some other chips: [...] > Does this mean I have to include tests specific to > those chips, or they behave exactly like SQ113C? They are all in the same scanner. Well, they ought to be there as somebody told me that they are there :-) Probably these chips are "helper chips" like a CCD driver, analog frontend, motor driver, RAM, EPROM, USB interface etc. So you don't need (and probably can't) test for them. Bye, Henning From anoah@pfeiffer.edu Thu Jun 24 21:01:31 2004 From: anoah@pfeiffer.edu (m. allan noah) Date: Thu, 24 Jun 2004 16:01:31 -0400 (EDT) Subject: [sane-devel] CanoScan5000F backend project beginning soon... In-Reply-To: <40DB0D36.5090508@bluewin.ch> References: <40DB0D36.5090508@bluewin.ch> 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-263747728-1088107291=:13997 Content-Type: TEXT/PLAIN; charset=US-ASCII asking for help on this list, and posting your sniffer logs up on the web usually will get some helpful pointers, but you are going to have to do most of the work, since you own the scanner. the script that henning may have mentioned is called spike. you cant look for it online. however, it only works with certain older versions of usbsnoopy. i have written a replacement for it, called spike4, which is attached to this mail. spike4 understands benoit's usb sniffer (which i highly recommend) logs. it is availible after a little googling as well. allan On Thu, 24 Jun 2004, Thibault North wrote: > Good afternoon, > As I said it some time ago, I am going to try and make the scanner Canon > canoscan5000F work... This will begin probably beginning of July, as > soon as my exams are done. I have then time to work with a friend which > knows more C than I do :) > I wanted to know if some of you where interested in helping us (if you > have this scanner) or be available to answer our questions (using IRC ?) > : we have never done a project like that and it is a little frightening :) > > If it is the case, please answer here of @ tnorth@bluewin.ch. > An adress used to communicate : http://gna.org/projects/canoscan5000F > > Thanks ! > > Thibault North > > P.S to Henning Meier-Geinitz : could you please send me the Perl script > we spoke about which is able to filter the log file from SniffUSB ? > Thank you very much, > > Here is the sane-find-scanner -v -v : > > > searching for SCSI scanners: > checking /dev/scanner... failed to open (Invalid argument) > checking /dev/sg0... failed to open (Invalid argument) > checking /dev/sg1... failed to open (Access to resource has been denied) > checking /dev/sg2... failed to open (Access to resource has been denied) > checking /dev/sg3... failed to open (Access to resource has been denied) > checking /dev/sg4... failed to open (Access to resource has been denied) > checking /dev/sg5... failed to open (Access to resource has been denied) > checking /dev/sg6... failed to open (Access to resource has been denied) > checking /dev/sg7... failed to open (Access to resource has been denied) > checking /dev/sg8... failed to open (Access to resource has been denied) > checking /dev/sg9... failed to open (Access to resource has been denied) > checking /dev/sga... failed to open (Invalid argument) > checking /dev/sgb... failed to open (Access to resource has been denied) > checking /dev/sgc... failed to open (Access to resource has been denied) > checking /dev/sgd... failed to open (Access to resource has been denied) > checking /dev/sge... failed to open (Access to resource has been denied) > checking /dev/sgf... failed to open (Access to resource has been denied) > checking /dev/sgg... failed to open (Access to resource has been denied) > checking /dev/sgh... failed to open (Access to resource has been denied) > checking /dev/sgi... failed to open (Access to resource has been denied) > checking /dev/sgj... failed to open (Access to resource has been denied) > checking /dev/sgk... failed to open (Access to resource has been denied) > checking /dev/sgl... failed to open (Access to resource has been denied) > checking /dev/sgm... failed to open (Access to resource has been denied) > checking /dev/sgn... failed to open (Access to resource has been denied) > checking /dev/sgo... failed to open (Access to resource has been denied) > checking /dev/sgp... failed to open (Access to resource has been denied) > checking /dev/sgq... failed to open (Invalid argument) > checking /dev/sgr... failed to open (Invalid argument) > checking /dev/sgs... failed to open (Invalid argument) > checking /dev/sgt... failed to open (Invalid argument) > checking /dev/sgu... failed to open (Invalid argument) > checking /dev/sgv... failed to open (Invalid argument) > checking /dev/sgw... failed to open (Invalid argument) > checking /dev/sgx... failed to open (Invalid argument) > checking /dev/sgy... failed to open (Invalid argument) > checking /dev/sgz... failed to open (Invalid argument) > # No SCSI scanners found. If you expected something different, make > sure that > # you have loaded a SCSI driver for your SCSI adapter. > > searching for USB scanners: > checking /dev/usb/scanner... failed to open (Invalid argument) > checking /dev/usb/scanner0... failed to open (Invalid argument) > checking /dev/usb/scanner1... failed to open (Invalid argument) > checking /dev/usb/scanner2... failed to open (Invalid argument) > checking /dev/usb/scanner3... failed to open (Invalid argument) > checking /dev/usb/scanner4... failed to open (Invalid argument) > checking /dev/usb/scanner5... failed to open (Invalid argument) > checking /dev/usb/scanner5... failed to open (Invalid argument) > checking /dev/usb/scanner7... failed to open (Invalid argument) > checking /dev/usb/scanner8... failed to open (Invalid argument) > checking /dev/usb/scanner9... failed to open (Invalid argument) > checking /dev/usb/scanner10... failed to open (Invalid argument) > checking /dev/usb/scanner11... failed to open (Invalid argument) > checking /dev/usb/scanner12... failed to open (Invalid argument) > checking /dev/usb/scanner13... failed to open (Invalid argument) > checking /dev/usb/scanner14... failed to open (Invalid argument) > checking /dev/usb/scanner15... failed to open (Invalid argument) > checking /dev/usbscanner... failed to open (Invalid argument) > checking /dev/usbscanner0... failed to open (Invalid argument) > checking /dev/usbscanner1... failed to open (Invalid argument) > checking /dev/usbscanner2... failed to open (Invalid argument) > checking /dev/usbscanner3... failed to open (Invalid argument) > checking /dev/usbscanner4... failed to open (Invalid argument) > checking /dev/usbscanner5... failed to open (Invalid argument) > checking /dev/usbscanner6... failed to open (Invalid argument) > checking /dev/usbscanner7... failed to open (Invalid argument) > checking /dev/usbscanner8... failed to open (Invalid argument) > checking /dev/usbscanner9... failed to open (Invalid argument) > checking /dev/usbscanner10... failed to open (Invalid argument) > checking /dev/usbscanner11... failed to open (Invalid argument) > checking /dev/usbscanner12... failed to open (Invalid argument) > checking /dev/usbscanner13... failed to open (Invalid argument) > checking /dev/usbscanner14... failed to open (Invalid argument) > checking /dev/usbscanner15... failed to open (Invalid argument) > trying libusb: > > > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 9 > bDeviceSubClass 0 > bDeviceProtocol 1 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 2.04 > iManufacturer 3 ((null)) > iProduct 2 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 64 (Self-powered) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 2 > bInterval 12 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 255 > bDeviceSubClass 255 > bDeviceProtocol 255 > bMaxPacketSize0 64 > idVendor 0x04A9 > idProduct 0x2212 > bcdDevice 3.03 > iManufacturer 2 ((null)) > iProduct 3 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 39 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 192 (Self-powered) > MaxPower 10 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 0 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 2 (bulk) > wMaxPacketSize 512 > bInterval 0 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 (out 0x02) > bmAttributes 2 (bulk) > wMaxPacketSize 512 > bInterval 0 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 3 (interrupt) > wMaxPacketSize 1 > bInterval 8 ms > bRefresh 0 > bSynchAddress 0 > found USB scanner (vendor=0x04a9, product=0x2212) at libusb:004:002 > > > bLength 18 > bDescriptorType 1 > bcdUSB 1.00 > bDeviceClass 9 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 0.00 > iManufacturer 0 () > iProduct 2 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 64 (Self-powered) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 8 > bInterval 255 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 1.00 > bDeviceClass 9 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 0.00 > iManufacturer 0 () > iProduct 2 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 64 (Self-powered) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 8 > bInterval 255 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 1.00 > bDeviceClass 9 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 0.00 > iManufacturer 0 () > iProduct 2 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 64 (Self-powered) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 8 > bInterval 255 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 0 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x046D > idProduct 0xC00E > bcdDevice 17.10 > iManufacturer 1 ((null)) > iProduct 2 ((null)) > iSerialNumber 0 () > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 34 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 160 (Remote Wakeup) > MaxPower 98 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 > bInterfaceSubClass 1 > bInterfaceProtocol 2 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 4 > bInterval 10 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 224 > bDeviceSubClass 1 > bDeviceProtocol 1 > bMaxPacketSize0 64 > idVendor 0x413C > idProduct 0x8000 > bcdDevice 5.65 > iManufacturer 0 () > iProduct 0 () > iSerialNumber 0 () > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 193 > bNumInterfaces 3 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 224 (Self-poweredRemote Wakeup) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 16 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 (out 0x02) > bmAttributes 2 (bulk) > wMaxPacketSize 64 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 (in 0x02) > bmAttributes 2 (bulk) > wMaxPacketSize 64 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 2 > bAlternateSetting 0 > bNumEndpoints 0 > bInterfaceClass 254 > bInterfaceSubClass 1 > bInterfaceProtocol 0 > iInterface 0 () > # 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. > done > > > -- "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-263747728-1088107291=:13997 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="spike4.pl" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="spike4.pl" IyEgL3Vzci9iaW4vcGVybA0KDQojIHNpbXBsZSBsb2cgcmVmb3JtYXR0ZXIg Zm9yIGJlbm9pdCdzIHNuaWZmdXNiLmV4ZQ0KIyBwdWJsaWMgZG9tYWluLiBi eSBhbm9haEBwZmVpZmZlci5lZHUNCg0KdXNlIHN0cmljdDsNCg0KbXkgJGNv dW50PTA7DQpteSAkbGFzdFVyYkxUaW1lPTA7DQpteSBAYnVmZmVyOw0KDQp3 aGlsZSAobXkgJGxpbmUgPSA8U1RESU4+KSB7DQoNCiAgICAgICAgaWYgKCAk bGluZSA9fiBtLz4+Pi8gKSB7DQogICAgICAgICAgICBkdW1wZXIoQGJ1ZmZl cikgaWYgJGNvdW50Ow0KICAgICAgICAgICAgQGJ1ZmZlciA9ICgpOw0KICAg ICAgICAgICAgJGNvdW50Kys7DQogICAgICAgIH0NCiAgICAgICAgaWYgKCAk bGluZSA9fiBtL1VzYlNub29wLyApe25leHQ7fQ0KICAgICAgICBwdXNoKEBi dWZmZXIsJGxpbmUpOw0KDQp9DQpkdW1wZXIoQGJ1ZmZlcikgaWYgJGNvdW50 Ow0KDQpzdWIgZHVtcGVyIHsNCg0KICAgIG15ICRkaXI9J291dCc7DQogICAg bXkgJHR5cGU9J0MnOw0KICAgIG15ICRkYXRhPSgpOw0KICAgIG15ICR1cmI9 MDsNCiAgICBteSAkZXA9Jyc7DQogICAgbXkgJGZUaW1lPTA7DQogICAgbXkg JGxUaW1lPTA7DQoNCiAgICBmb3JlYWNoIG15ICRsaW5lIChAXykgew0KDQog ICAgICAgIGlmKCRsaW5lID1+IG0vXFsoXGQrKSBtc1xdIC4qIFVSQiAoXGQr KSBnb2luZyBkb3duLyl7DQogICAgICAgICAgJGZUaW1lPSQxOw0KICAgICAg ICAgICR1cmI9JDI7DQogICAgICAgICAgcHJpbnQgIlxucGF1c2UgIiAuICgk ZlRpbWUtJGxhc3RVcmJMVGltZSkgLiAiIG1zXG5cbiI7DQogICAgICAgIH0N CiAgICAgICAgZWxzaWYgKCAkbGluZSA9fiBtL1VTQkRfVFJBTlNGRVJfRElS RUNUSU9OX0lOLyApIHsNCiAgICAgICAgICAkZGlyPSdpbic7DQogICAgICAg ICAgJGRhdGE9KCk7DQogICAgICAgIH0NCiAgICAgICAgZWxzaWYgKCAkbGlu ZSA9fiBtLy0tIFVSQl9GVU5DVElPTl9CVUxLX09SX0lOVEVSUlVQVF9UUkFO U0ZFUi8gKSB7DQogICAgICAgICAgJHR5cGU9J0InOw0KICAgICAgICB9DQog ICAgICAgIGVsc2lmKCAkbGluZSA9fiBtL1BpcGVIYW5kbGUuKmVuZHBvaW50 ICgweFxkKykvKXsNCiAgICAgICAgICAkZXA9JDE7DQogICAgICAgIH0NCiAg ICAgICAgZWxzaWYgKCAkbGluZSA9fiBtIC8gIChbMC05YS1mXXs4fTogKShb MC05YS1mIF0qKS8gKSB7DQogICAgICAgICAgcHVzaChAeyRkYXRhfSwgJDEg LiAkMik7DQogICAgICAgIH0NCg0KICAgICAgICBpZiAoICRsaW5lID1+IG0v XFsoXGQrKSBtc1xdLyApew0KICAgICAgICAgICRsVGltZT0kMTsNCiAgICAg ICAgfQ0KDQogICAgICAgICRlcD1+cy9eMHgwKy8vOw0KICAgIH0NCg0KICAg IGlmKCRkaXIgZXEgJ2luJyl7DQogICAgICAgIHByaW50ICJVcmIgJHVyYiAo JHR5cGUpIGVwPSRlcCAocmVhZCkgIjsNCiAgICB9DQogICAgZWxzZXsNCiAg ICAgICAgcHJpbnQgIlVyYiAkdXJiICgkdHlwZSkgZXA9JGVwICh3cml0ZSkg IjsNCiAgICB9DQogICAgcHJpbnQgJGxUaW1lLSRmVGltZSAuICIgbXNcbiI7 DQoNCiAgICBmb3JlYWNoIG15ICRsaW5lIChAeyRkYXRhfSkgew0KICAgICAg ICAgICAgcHJpbnRmKCIgJXMiLCAkbGluZSk7DQogICAgICAgICAgICBwcmlu dCAiXG4iOw0KICAgIH0NCg0KICAgICRsYXN0VXJiTFRpbWU9JGxUaW1lOw0K DQp9DQoNCmV4aXQgMDsNCg== --1386611826-263747728-1088107291=:13997-- From news@vlado-do.de Thu Jun 24 23:12:04 2004 From: news@vlado-do.de (Vlado Plaga) Date: Fri, 25 Jun 2004 00:12:04 +0200 Subject: [sane-devel] plustek_pp backend doesn't like my parport scanner anymore Message-ID: <40DB51B4.2020109@vlado-do.de> Hi! Afer having updated my Debian "testing" distribution a few weeks ago my Plustek OpticPro 9636T suddenly stopped working. So far everything had worked fine but although I tried various combinations of diffenrent backend versions, module parameters and even a self-compiled sane I did only get scans with strange colors (which is better than nothing but not really helpful) and a lot of debugging information. The last kernel module that worked for me was from the file plustek-module-0_41_5.tar.gz but identified as pt_drv : driver version 0.41-6 I still have a Debian testing system (on a hard disk that I'm not using anymore) where the scanner works. But I don't want to continue using that system without updates, because Debian's testing systems change over time, which makes it impossible to install new packages (because of dependencies). Unfortunatley the updates I already made (now on a different hard disk) rendered the scanner unusable... I compiled with DEBUG=y and now I'll quote some output from syslog, but not everything, as it is quite long: Jun 24 09:04:26 koala kernel: ********************************************* Jun 24 09:04:26 koala kernel: pt_drv: init_module() Jun 24 09:04:26 koala kernel: pt_drv : driver version 0.41-6 Jun 24 09:04:26 koala kernel: ProcFsInitialize() Jun 24 09:04:26 koala kernel: ptdrvInit(0) Jun 24 09:04:26 koala kernel: Init settings done Jun 24 09:04:26 koala kernel: ScanData = 0xcdd68000 Jun 24 09:04:26 koala kernel: Using fast I/O Jun 24 09:04:26 koala kernel: Requested port at 0x378 Jun 24 09:04:26 koala kernel: Requested port (0x378) found Jun 24 09:04:26 koala kernel: Port mode reported: (0x005f) Jun 24 09:04:26 koala kernel: Port for device 0 registered Jun 24 09:04:26 koala kernel: ptdrvOpen(port=0x378) Jun 24 09:04:26 koala kernel: Try to claim the parport Jun 24 09:04:26 koala kernel: parport-modi: SPP PS/2 EPP ECP EPP(ECP) PS/2(ECP) Jun 24 09:04:26 koala kernel: Using EPP-mode Jun 24 09:04:26 koala kernel: Trying faster mode... Jun 24 09:04:26 koala kernel: Attempting to set EPP from ECP mode. Jun 24 09:04:26 koala kernel: Port is set to (ECP) EPP mode. Jun 24 09:04:26 koala kernel: Starting Scanner-Autodetection [...] Jun 24 09:04:26 koala kernel: ************* ASIC98001 ************* Jun 24 09:04:26 koala kernel: ModelSet9636() Jun 24 09:04:26 koala kernel: ModelSet9360() Jun 24 09:04:26 koala kernel: modelInitPageSettings() Jun 24 09:04:26 koala kernel: A4 set Jun 24 09:04:26 koala kernel: ModelSet9630() done. Jun 24 09:04:26 koala kernel: modelInitPageSettings() Jun 24 09:04:26 koala kernel: A4 set Jun 24 09:04:26 koala kernel: ModelSet9636() done. Jun 24 09:04:26 koala kernel: P9636InitAsic() Jun 24 09:04:26 koala kernel: DacInitialize() Jun 24 09:04:26 koala kernel: ImageInitialize() Jun 24 09:04:26 koala kernel: IOFuncInitialize() Jun 24 09:04:26 koala kernel: IOInitialize() Jun 24 09:04:26 koala kernel: MotorInitialize() Jun 24 09:04:26 koala kernel: 0x81 Jun 24 09:04:26 koala kernel: CCID = 0x00 Jun 24 09:04:26 koala kernel: P9636InitAsic() done. Jun 24 09:04:26 koala kernel: Dataport = 0x0378 Jun 24 09:04:26 koala kernel: Ctrlport = 0x037a Jun 24 09:04:26 koala kernel: Test 0x55 Jun 24 09:04:26 koala kernel: Test 0xAA Jun 24 09:04:26 koala kernel: Compare data=0x7e and status=0x1e, port=0x378 Jun 24 09:04:26 koala kernel: ioP98ReadWriteTest() Jun 24 09:04:26 koala kernel: Putting Scanner (ASIC 98001) into Idle-Mode Jun 24 09:04:26 koala kernel: detectScannerConnection() returns 0. Jun 24 09:04:26 koala kernel: p9636InitP98001(0) Jun 24 09:04:26 koala kernel: bData = 0x0000, PCB-ID = 0x00 Jun 24 09:04:26 koala kernel: CCD-ID = 0x00 = _CCD_3797 Jun 24 09:04:26 koala kernel: bSetScanModeFlag = 0 Jun 24 09:04:26 koala kernel: *** setupBuffers *** Jun 24 09:04:26 koala kernel: Driverbuf(147360 bytes) needed ! Jun 24 09:04:26 koala kernel: pColorRunTab = 0xd0a3652c - 0xd0a35fa0 Jun 24 09:04:26 koala kernel: Adjust for 98001 ASIC Jun 24 09:04:26 koala kernel: sb2 = 0xd0a12000, sb1 = 0xd0a1cbe0, Color = 0xd0a2cdb0 Jun 24 09:04:26 koala kernel: Pro = 0xd0a323a0, size = 147360 Jun 24 09:04:26 koala kernel: *** DETECTION DONE, result: 0 *** Now the failed detection: Jun 3 23:16:10 koala kernel: ********************************************* Jun 3 23:16:10 koala kernel: pt_drv: init_module() Jun 3 23:16:10 koala kernel: pt_drv : driver version 0.41-6 Jun 3 23:16:10 koala kernel: ProcFsInitialize() Jun 3 23:16:10 koala kernel: ptdrvInit(0) Jun 3 23:16:10 koala kernel: Init settings done Jun 3 23:16:10 koala kernel: ScanData = 0xce960000 Jun 3 23:16:10 koala kernel: Using fast I/O Jun 3 23:16:10 koala kernel: Requested port at 0x378 Jun 3 23:16:10 koala kernel: Requested port (0x378) found Jun 3 23:16:10 koala kernel: Port mode reported: (0x0047) Jun 3 23:16:10 koala kernel: Port for device 0 registered Jun 3 23:16:10 koala kernel: ptdrvOpen(port=0x378) Jun 3 23:16:10 koala kernel: Try to claim the parport Jun 3 23:16:10 koala kernel: parport-modi: SPP PS/2 EPP EPP(ECP) PS/2(ECP) Jun 3 23:16:10 koala kernel: Using EPP-mode Jun 3 23:16:10 koala kernel: Starting Scanner-Autodetection [...] Jun 3 23:16:10 koala kernel: ************* ASIC98001 ************* Jun 3 23:16:10 koala kernel: ModelSet9636() Jun 3 23:16:10 koala kernel: ModelSet9360() [...just like in the successful case before...] Jun 3 23:16:10 koala kernel: Test 0x55 Jun 3 23:16:10 koala kernel: Test 0xAA Jun 3 23:16:10 koala kernel: Compare data=0x7f and status=0x1f, port=0x378 Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: detectScannerConnection() returns -9020. Jun 3 23:16:10 koala kernel: *** DETECTION DONE, result: -9020 *** Now there already was a difference in the automatic parport mode selection. Detection does work when I tell the module to use the SPP mode (forceMode=1) - but then sane produces some pretty ugly colors. Hopefully someone can tell me how to fix this. I would really hate having done all this in vain and not being able to use the scanner without rebooting any more. Cheers, Vlado From jgato@lambdaux.com Thu Jun 24 10:37:15 2004 From: jgato@lambdaux.com (jose) Date: Thu, 24 Jun 2004 11:37:15 +0200 Subject: [sane-devel] sane-desc to xml Message-ID: <1088069835.3362.9.camel@localhost> Hi again, thanks for te information about sane-desc, very usefull tool. No Im thinking on add a new function to sane-desc to get a output in XML format (very easy to parser). I have the code done it but I need to know what should I do... I guess that I have to send the patch and then you say that its "ok" for including it... The new code is really very simple, cause is the same like ASCII but with tags. Bye... From jgato@lambdaux.com Thu Jun 24 13:05:57 2004 From: jgato@lambdaux.com (jose) Date: Thu, 24 Jun 2004 14:05:57 +0200 Subject: [sane-devel] a new function for sane-desc! Message-ID: <1088078757.3362.61.camel@localhost> --=-iNgj46R6siZP/InxV0Si Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi, finally I have made a new function in sane-desc to get an xml output. I think that only have to send the patch, if there is any problem please email me, this is the first time that I make something similar.. Bye, --=-iNgj46R6siZP/InxV0Si Content-Disposition: attachment; filename=sane-desc-xml.patch Content-Type: text/plain; name=sane-desc-xml.patch; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit --- sane-desc.c Thu Jun 24 13:43:48 2004 +++ sane-desc.c.new Thu Jun 24 11:55:34 2004 @@ -65,6 +65,7 @@ typedef enum output_mode { output_mode_ascii = 0, + output_mode_xml, output_mode_html_backends, output_mode_html_backends_split, output_mode_html_mfgs @@ -308,6 +309,11 @@ DBG_INFO ("Output mode: ascii\n"); mode = output_mode_ascii; } + else if (strcmp (optarg, "xml") ==0) + { + DBG_INFO ("Output mode: xml\n"); + mode = output_mode_xml; + } else if (strcmp (optarg, "html-backends-split") == 0) { DBG_INFO ("Output mode: html-backends-split\n"); @@ -1609,6 +1615,193 @@ } /* while (be) */ } +/* Print an XML list with all the information we have */ +static void +xml_print_backends (void) +{ + backend_entry *be; + + be = first_backend; + while (be) + { + url_entry *url = be->url; + type_entry *type = be->type; + + if (be->name) + printf ("\n",be->name); + else + printf ("\n"); + + if (be->version) + printf ("%s \n", be->version); + else + printf ("*none*\n"); + + if (be->new) + printf (" NEW!\n"); + + if (be->manpage) + printf (" %s\n", be->manpage); + else + printf (" *none*\n"); + + if (url) + while (url) + { + printf (" %s\n", url->name); + url = url->next; + } + else + printf (" *none*\n"); + + if (be->comment) + printf (" %s\n", be->comment); + else + printf (" *none*\n"); + + if (type) + while (type) + { + switch (type->type) + { + case type_scanner: + printf (" scanner\n"); + break; + case type_stillcam: + printf (" stillcam\n"); + break; + case type_vidcam: + printf (" vidcam \n"); + break; + case type_meta: + printf (" meta\n"); + break; + case type_api: + printf (" api\n"); + break; + default: + printf (" *unknown* \n"); + break; + } + if (type->desc) + { + url_entry *url = type->desc->url; + printf (" %s\n", type->desc->desc); + if (url) + while (url) + { + printf (" %s\n", url->name); + url = url->next; + } + else + printf (" *none*\n"); + + if (type->desc->comment) + printf (" %s\n", type->desc->comment); + else + printf (" *none*\n"); + } + else if (type->type >= type_meta) + printf (" *none*\n"); + + if (type->mfg) + { + mfg_entry *mfg = type->mfg; + while (mfg) + { + model_entry *model = mfg->model; + url_entry *url = mfg->url; + + printf (" \n", mfg->name); + if (url) + while (url) + { + printf (" `%s'\n", url->name); + url = url->next; + } + else + printf (" *none*\n"); + + if (mfg->comment) + printf (" %s\n", mfg->comment); + else + printf (" *none*\n"); + + if (model) + while (model) + { + url_entry *url = model->url; + printf (" \n", model->name); + if (model->interface) + printf (" %s\n", model->interface); + else + printf (" *none*\n"); + + if (model->status == status_unknown) + model->status = be->status; + switch (model->status) + { + case status_minimal: + printf (" minimal\n"); + break; + case status_basic: + printf (" basic\n"); + break; + case status_good: + printf (" good\n"); + break; + case status_complete: + printf (" complete\n"); + break; + case status_untested: + printf (" untested\n"); + break; + case status_unsupported: + printf (" unsupported\n"); + break; + default: + printf (" *unknown*\n"); + break; + } + + if (url) + while (url) + { + printf (" %s\n", url->name); + url = url->next; + } + else + printf (" *none*\n"); + + if (model->comment) + printf (" %s\n", model->comment); + else + printf (" *none*\n"); + + model = model->next; + printf(" \n"); + } /* while (model) */ + else + printf (" \n"); + + printf(" \n"); + mfg = mfg->next; + } /* while (mfg) */ + } + else if (type->type < type_meta) + printf (" *none*\n"); + type = type->next; + } /* while (type) */ + else + printf (" *none*\n"); + printf("\n"); + be = be->next; + + } /* while (be) */ +} + + + /* Generate a name used for HTML tags */ static char * html_generate_anchor_name (device_type dev_type, char *manufacturer_name) @@ -2296,6 +2489,9 @@ { case output_mode_ascii: ascii_print_backends (); + break; + case output_mode_xml: + xml_print_backends(); break; case output_mode_html_backends_split: html_print_backends_split (); --=-iNgj46R6siZP/InxV0Si-- From picos132004@yahoo.co.uk Fri Jun 25 12:16:27 2004 From: picos132004@yahoo.co.uk (=?iso-8859-1?q?Ioan-Cosmin=20Pop?=) Date: Fri, 25 Jun 2004 12:16:27 +0100 (BST) Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <20040624165547.GC9387@meier-geinitz.de> Message-ID: <20040625111628.34893.qmail@web25104.mail.ukl.yahoo.com> I looked again over the windows sources and I found that I was mistaken. I want to identify the chip so I was trying to use usb_bulk_write to send an array of 4 bytes then read them. Looking again over the windows sources (after about 2 months) revealed something I wasn't aware of. This proves the necessity of a vacation :) Oh, and btw, I have to restart hotplug after every unsuccesfull debug... I was innocent enough thinking I don't have to :( I was trying to write 'dddd', because I thought this is the test I should do. So I was trying to write this string and if I could read it succesfully, it would be OK. Wrong!! It's true, I have to send an array of 4 bytes, but this array has to be carefully crafted. Right now I'm looking over the sources. Henning, you keep telling me about the "protocol of the scanner", "commands" and "registers". Can you please tell me what they mean? OK, I know this sounds stupid. I know what a protocol, command or register is. Back in the good ol' DOS days (well, not so good, but old for sure) I used to read/write to a specific port and mess with the device registers (an aquisition device in my case). I can only make some suppositions. Please tell me if I'm correct and if I'm on the right way. - for the "protocol", I think this is something like: buffered or direct; - for commands, I have some "IOCTL functions" - as for "registers", I really have no idea. What I have so far, are some macros (taken from the windows sources), like IOCTL_GET_VERSION, IOCTL_WRITE_REGISTERS, IOCTL_READ_REGISTERS and so on. They combine information such as acces mode, device type (fixed as scanner in my case), function. I feel I can use much of this information. I believe we are using different words for the same thing. I'm currently away from my computer (and I'll come back sunday), so I don't have the chance to test this right now. If somebody can understand my rumble-mumble, please guide me. I feel lost :) Poor me! I think I really need some help, somebody to talk to. Ronald Humphries, do you read this? If you do have some spare time, can you please send me a message? I can't send you the windows sources because I am bound by an NDA (non-disclosure agreement) with Mustek, but I'm sure we can cut a deal with them to offer you the same info they gave me...:) Thank you Cosmin ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com From johnb51@earthlink.net Fri Jun 25 15:03:42 2004 From: johnb51@earthlink.net (John) Date: Fri, 25 Jun 2004 10:03:42 -0400 Subject: [sane-devel] hp psc1210 printer,scanner,copier Message-ID: <40DC30BE.1050109@earthlink.net> I have the above multi-function hooked up to mandrake 10 os. The scanner process doesn't work with gimp 2.0. It needs the updated xsane plugin. Gimp 1.2 and xsane .92 plugin returned message that it could not detect scanner. I would appreciate any help or info. on how to get the scanner going. Thanks (from linux newbie) John From henning@meier-geinitz.de Fri Jun 25 17:02:59 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 18:02:59 +0200 Subject: [sane-devel] sane-desc to xml In-Reply-To: <1088069835.3362.9.camel@localhost> References: <1088069835.3362.9.camel@localhost> Message-ID: <20040625160259.GB12809@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 11:37:15AM +0200, jose wrote: > No Im thinking on add a new function to sane-desc to get a output in XML > format (very easy to parser). I have the code done Ah, very nice. > it but I need to know > what should I do... I guess that I have to send the patch and then you > say that its "ok" for including it... Yes, please send a unified diff. Bye, Henning From henning@meier-geinitz.de Fri Jun 25 17:58:40 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 18:58:40 +0200 Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <20040625111628.34893.qmail@web25104.mail.ukl.yahoo.com> References: <20040624165547.GC9387@meier-geinitz.de> <20040625111628.34893.qmail@web25104.mail.ukl.yahoo.com> Message-ID: <20040625165840.GC12809@meier-geinitz.de> Hi, On Fri, Jun 25, 2004 at 12:16:27PM +0100, Ioan-Cosmin Pop wrote: > Henning, you keep telling me about the "protocol of > the scanner", "commands" and "registers". Can you > please tell me what they mean? OK, I know this sounds > stupid. I know what a protocol, command or register > is. Back in the good ol' DOS days (well, not so good, > but old for sure) I used to read/write to a specific > port and mess with the device registers (an aquisition > device in my case). I can only make some suppositions. > Please tell me if I'm correct and if I'm on the right > way. > - for the "protocol", I think this is something like: > buffered or direct; No. What I mean by "protocol" is how the driver/backend communicates with the scanner. As an example, I'll describe the protocol of the GrandTech GT6801 chipset. Your scanner's protocol will be completely different most probably. Commands and data are sent to the scanner as USB control messages with a data size of 64 bytes. The request, request_type, value etc. depend on the type of command. E.g. you can send commands, receive results from commands, write data to scanner's RAM (firmware) and read from the RAM. This is an example for a command sent to the scanner (from a sniffusb log of a Mustek BearPaw 2400 TA Plus: | >>> URB 525 going down >>> | -- URB_FUNCTION_VENDOR_DEVICE: | TransferFlags = 00000000 | (USBD_TRANSFER_DIRECTION_OUT, ~USBD_SHORT_TRANSFER The data is sent from the host to the scanner. | TransferBufferLength = 00000040 64 bytes of data. | TransferBuffer = c1b6b000 | TransferBufferMDL = 00000000 | 0000: 20 01 0f 01 29 05 a4 00 58 02 82 20 64 00 01 00 The data itself. For the gt6801, the first byte is the command code. 0x20 means "setup scan". The second byte is alway 01. Bytes 2+3 and 3+4 are the Y coordinates of the scan widow (Y0 + height). The first byte is the low byte. In this case the height is 0x0529 = 1321. As these coordinates are based on 1200 dpi, the height is 1.1 inches in this case. Byte 0x0a ("82") means gray mode. Byte 0x0c ("64") and 0x0d ("00") are the resolution: 0x0064 = 100 dpi. | 0010: 64 00 73 00 0b 00 64 00 3c 00 00 00 00 00 00 00 | 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 More settings like lamp, backtracking, bytes per line etc. | UrbLink = 00000000 | RequestTypeReservedBits = 00 | Request = 01 | Value = 2010 That means "send a command". For writing firmware "200b" would be used. | Index = 3f40 Not used here but for firmware writes that would be the memory address to write to. Now the data is sent. As confirmation you get the URB back from the (Windows) operating system (see the same URB number): | <<< URB 525 coming back <<< | -- URB_FUNCTION_CONTROL_TRANSFER: | PipeHandle = C1AD431C | TransferFlags = 00000002 | (USBD_TRANSFER_DIRECTION_OUT, USBD_SHORT_TRANSFER_OK) | TransferBufferLength = 00000040 | TransferBuffer = c1b6b000 | TransferBufferMDL = c1800880 | UrbLink = 00000000 | SetupPacket : 40 01 10 20 40 3f 40 00 The setup packet is the same as above but this time it's not split in request, value etc. See the USB spec for details. Now we ask for the result of the command we just sent: | >>> URB 526 going down >>> | -- URB_FUNCTION_VENDOR_DEVICE: | TransferFlags = 00000001 | (USBD_TRANSFER_DIRECTION_IN, ~USBD_SHORT_TRANSFER_ We want to receive data from the scanner (DIRECTION_IN). | TransferBufferLength = 00000040 We want to get 64 bytes. | TransferBuffer = e3c09d1c | TransferBufferMDL = 00000000 | UrbLink = 00000000 | RequestTypeReservedBits = 00 | Request = 01 | Value = 2011 That means: "Read result of command". | Index = 3f00 See above. Ok, now the result: | <<< URB 526 coming back <<< | -- URB_FUNCTION_CONTROL_TRANSFER: | PipeHandle = C1AD431C | TransferFlags = 00000003 | (USBD_TRANSFER_DIRECTION_IN, USBD_SHORT_TRANSFER_OK) | TransferBufferLength = 00000040 | TransferBuffer = e3c09d1c | TransferBufferMDL = c1800880 | 0000: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The first 00 means that the command succeeded. The second byte "20" repeats the command we sent ("setup scan"). Other commands may return more data (e.g. the status of scan buttons or a flag if the scan head is at its home position). The actual scan data is read by bulk reads. That's what I mean by a "protocol". Other chipsets don't use commands (or functions) like in this case but you can set registers. E.g. you could use a three byte block of data sent by bulk messages: 01 02 03 01 --> type = write register 02 --> register number 03 --> value to write to the register That's just a protocolo I made up :-) > - for commands, I have some "IOCTL functions" > - as for "registers", I really have no idea. The scanner's chipset may have a buch of registers to which you can write data. E.g. One register may contain the resolution. When setting a bit in another register you could start scanning. Think of registers as processor registers. > What I have so far, are some macros (taken from the > windows sources), like IOCTL_GET_VERSION, > IOCTL_WRITE_REGISTERS, IOCTL_READ_REGISTERS and so on. Probably that's how the Windows low level scanner driver is accessed. This low level driver is able to do basic stuff like writing the scaynners registers. The higher level software talks to it via ioctls. (Just a guess but that's similar to how it works with Linux). > I think I really need some help, somebody to talk > to. Ronald Humphries, do you read this? If you do have > some spare time, can you please send me a message? I > can't send you the windows sources because I am bound > by an NDA (non-disclosure agreement) with Mustek, but > I'm sure we can cut a deal with them to offer you the > same info they gave me...:) Try to go down to the lowest level of the Windows source code. Look for functions that actually write to the scanner. Bye, Henning From henning@meier-geinitz.de Fri Jun 25 18:03:32 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 19:03:32 +0200 Subject: [sane-devel] donation / scanner support In-Reply-To: <40DABFC4.9030102@alphacent.com> References: <40DABFC4.9030102@alphacent.com> Message-ID: <20040625170332.GD12809@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 11:49:24AM +0000, Florent Aide wrote: > I have a Dell A920 (rebranded Lexmark X1150) that is currently marked on > the website as not supported. Since I have two of these little things I > am willing to donate one of them to the project in order to see scanner > support for it. Thanks for your offer! > How can I do that ? Is someone willing to accept this donation and work > on the scanner part of the Dell A920 ? Unfortunately there is no SANE backend yet for the RTS8852B chipset as far as I know. So you can't just send it to the backend maintainer. Maybe someone wants to start writing a backend for that scanner? Bye, Henning From henning@meier-geinitz.de Fri Jun 25 18:09:17 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 19:09:17 +0200 Subject: [sane-devel] a new function for sane-desc! In-Reply-To: <1088078757.3362.61.camel@localhost> References: <1088078757.3362.61.camel@localhost> Message-ID: <20040625170917.GE12809@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 02:05:57PM +0200, jose wrote: > Hi, finally I have made a new function in sane-desc to get an xml > output. > > I think that only have to send the patch, if there is any problem please > email me, this is the first time that I make something similar.. Ah, there it is. I should really read all sane-devel messages before answering... Looks fine. If nobody objects I'll add it to CVS. Bye, Henning From henning@meier-geinitz.de Fri Jun 25 18:18:15 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 19:18:15 +0200 Subject: [sane-devel] CanoScan5000F backend project beginning soon... In-Reply-To: <40DB0D36.5090508@bluewin.ch> References: <40DB0D36.5090508@bluewin.ch> Message-ID: <20040625171815.GF12809@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 07:19:50PM +0200, Thibault North wrote: > I wanted to know if some of you where interested in helping us (if you > have this scanner) or be available to answer our questions (using IRC ?) Ask on this list or ask on IRC (#sane on freenode.net). On IRC, be patient as questions may be answered hours later when someone wakes up :-) > An adress used to communicate : http://gna.org/projects/canoscan5000F I have added a link to that page to our Canon 5000f page: http://www.sane-project.org/unsupported/canon-5000f.html > P.S to Henning Meier-Geinitz : could you please send me the Perl script > we spoke about which is able to filter the log file from SniffUSB ? I don't really remeber using such a perl script. I know that there is (or was) one, but I think I never really used it. Sometimes I use a C program to analyse sniffusb log files but that program is really specific for the GT6801 chipset and filters only some special commands so I think it's not useful for anyone else. Bye, Henning From rene@rocklinux-consulting.de Fri Jun 25 22:20:57 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Fri, 25 Jun 2004 23:20:57 +0200 (CEST) Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040609151818.GO7920@meier-geinitz.de> References: <20040601215656.GA3524@ffii.org> <20040609134039.GA3769@ffii.org> <20040609151818.GO7920@meier-geinitz.de> Message-ID: <20040625.232057.576037890.rene@rocklinux-consulting.de> Hi, On: Wed, 9 Jun 2004 17:18:18 +0200, Henning Meier-Geinitz wrote: > Timeouts: > - HP5370C (avision) on UHCI VIA, Linux 2.6.5 > - HP7450C (avision), sane-backends 1.0.14 (also tried latest avision > code), Linux 2.6.5 > - HP7400 (avision) on UHCI (Intel Corp. 82371AB/EB/MB PIIX4 USB) Asus= > board, sane-backends 1.0.14, Linux 2.6.3, 2.6.5, 2.6.6 and > 2.6.7-rc2-bk7 > - HP7450C (avision), there was a hint about the hpusbscsi driver > making trouble in that case > = > - Epson Perfection 1670 (snapscan) on UHCI VIA, sane-backends 1.0.14,= > Linux 2.6.5-mm2 > = > No timeouts: > - Several Mustek+Plustek scanners (mustek_usb, plustek, gt68xx), = > sane-backends 1.0.14, on OHCI + UHCI (VIA PCI card) on Linux 2.6.7-= rc2 > and Linux 2.4.26 > - Avision scanners, on OHCI, sane-backends 1.0.14 + latest avison cod= e on Linux > 2.6.3 (UltraSparc +iBook) I flushed my Avision TODO list a bit and so tested the Avision backend with a more recent kernel: 2.6.7 works fine on PowerPC OHCI. I still plan to find a box to test a UHCI. > An unrelated bug showed the same timeouts: > - Epson Perfection 1260 (plustek), sane-backends-1.0.14, on Linux 2.6= .7-rc2 = > and 2.4.25 with scanner.o(!) > Reason: the epson backend tries to talk to this scanner You mean "talking" directly using libusb while the scanner module is loaded or so? Although this gives a permission denied or so for me, maybe with ohci this behaves differently? People with problems could take a look if either scanner or hpsubscsi was / is loaded ... and unload it just in case ... Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene@rocklinux-consulting.de Sat Jun 26 00:52:52 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sat, 26 Jun 2004 01:52:52 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DCB61F.5070306@mykec.net> References: <40DC4DBF.7010004@mykec.net> <20040625.182333.719906209.rene@rocklinux-consulting.de> <40DCB61F.5070306@mykec.net> Message-ID: <20040626.015252.276767564.rene@rocklinux-consulting.de> Hi, On: Fri, 25 Jun 2004 18:32:47 -0500, Myke Carter wrote: > My currently installed RPM is "sane-backends-1.0.8-1.ximian.1". Yeah - forget this one - say goodbye to it ... > This, obviously, came to me from Ximian Gnome during some past = > install/upgrade to my stock Red Hat system. Ximian tends to play by = its = > own rules, so I'm kinda hesitant to use just any more recent RPM to = > upgrade what's been given me. There is not way to get your scanner working with this version. AFAIK the SANE/Backend pacakge is backward compaitible - just make sure your source packages replaces the RPM package files, so compile with the correct --sysconfdir and --prefix ... > > If you want to compile from source: > > = > > http://www.rocklinux-consulting.de/oss/avision/compiling.html > = > I am downloading this now but am curious as to what kinds of conflict= s I = > might encounter by mixing this with my current Ximian RPM installatio= n. Do not forget that you need the wohle sane-backend package (sane.alioth.debian.org). The current version is 1.0.14. Optionally you can replace the avision.{c,h} files with the one from my homepage. You scanner will work with 1.0.14 - but in my svn (Subversion) repository you get some newer fixes, like enhanced sharpness, more robust light detection and enhanced 16bit / channel support ... > > You only need to compile / install sane-backend and other sane > > packages can be left untouched. > = > Is it not enough to just replace my current /etc/sane.d/avision.conf = > file with the same one from a newer version? No. This is just a configuration file - which is even optional and can be completely missing for my Avision backend. My backend uses reasonable defaults and detects any setting for tested scanners. The config files is only available to overwrite setting during debugging. All the real funtionally is present in 6122 (pure wc) of C code ... You can not avoid updating it. > Thanks for your quick response, Sometimes my inbox is not that crowded and people get quick replies ;-) Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene@rocklinux-consulting.de Sat Jun 26 08:08:46 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sat, 26 Jun 2004 09:08:46 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DCCC41.3050606@mykec.net> References: <40DCB61F.5070306@mykec.net> <20040626.015252.276767564.rene@rocklinux-consulting.de> <40DCCC41.3050606@mykec.net> Message-ID: <20040626.090846.653234575.rene@rocklinux-consulting.de> Hi, On: Fri, 25 Jun 2004 20:07:13 -0500, Myke Carter wrote: > OK. Are you suggesting that I uninstall the RPM? > = > I guess it wouldn't matter if I did even if I couldn't replace it lat= er = > because it doesn't work anyway, huh? :) Yes - uninstalling is the cleaner solution since you can not accidently use an old file later. > > AFAIK the SANE/Backend pacakge is backward compaitible > = > Backward compatible with what? With previous SANE/Backends versions. > > - just make sure your source packages replaces the RPM package file= s, > = > I should just uninstall the package entirely then before compiling fr= om = > source. Yes - that is even cleaner. > > so compile with the correct --sysconfdir and --prefix ... > = > All I know right now is that the config files are in /etc/sane.d/. = > What's up with --prefix? Where the files will be placed in. I guess your current files are in /usr (/usr/lib/libsane* for example). The compile-from-source default is /usr/local. I suggest you specify --prefix=3D/usr for ./configure. Please see the sane-user mailing list archive for lenghty discussions and information. > > Do not forget that you need the whole sane-backend package > > (sane.alioth.debian.org). The current version is 1.0.14. > = > I now have "sane-backends-1.0.14.tar.gz" downloaded to my hard drive.= > = > > Optionally you can replace the avision.{c,h} files with the > > one from my homepage. > = > URLs? http://www.rocklinux-consulting.de/oss/avision/ http://svn.rocklinux-consulting.de/sane-avision/trunk/backend/ > > Your scanner will work with 1.0.14 - but in my svn > > (Subversion) repository you get some newer fixes, like enhanced > > sharpness, more robust light detection and enhanced 16bit / channel= > > support ... > = > One feature I get with the HP PrecisionScan software (for Windows) th= at = > came bundled on CD-ROM with my 5300C is an automatic image rotation = > adjustment that I don't believe exists in any Linux scanning software= . = > The MacOS 9 app that comes from the same CD-ROM doesn't even have it.= > = > That features makes it very easy to get perfectly vertical scans of = > rectangular things such as sports cards, business cards, books, etc. = - = > without having to use something like The Gimp later to slightly rotat= e = > each image (which invariably blurs them unnecessarily). If you rotate them in the driver you get the same blurs anyway - there is no way to get around this - the same algorithm needs to be applied on the data. Nevertheless the feature might be a nice to have in e.g. xsane ... Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From stan@saticed.me.uk Sat Jun 26 10:25:12 2004 From: stan@saticed.me.uk (stan@saticed.me.uk) Date: Sat, 26 Jun 2004 10:25:12 +0100 Subject: [sane-devel] fujitsu fi-4220 problem with 1.0.14 + patch Message-ID: <20040626092512.GA12998@nimitz.cehill.co.uk> --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Attached scanimage run with SANE_DEBUG_FUJITSU=20 set: fujitsu-13.log.gz: with sane-backends 1.0.13 fujitsu-14.log.gz: with sane-backends 1.0.14 fujitsu-14-2.log.gz: sane-backends 1.0.14 + small patch Seems to be working ok for the last couple of days with patch. The specificness of the error is impressive, thanks for all the hard work sane and fujitsu backend maintainers! :-) --6c2NcOVqGQ03X4Wi Content-Type: application/x-gunzip Content-Disposition: attachment; filename="fujitsu-14.log.gz" Content-Transfer-Encoding: base64 H4sICMeQ2UAAA2Z1aml0c3UtMTQubG9nAN1ZWW/bOBB+Tn/FoE+7wDbWacdGW2CbtEW6R4uk 2V2gKARKomw2kuiSlGP/+x1KdkqdttOgDw0E2+IcnBl+HM4wnyTJKQtiGhbzz3BNlWL5HMpX SOmKpsATSIovTMkCFAfHOn3yafv+GbRwwHKmusZmICiJtbqI5wmbQ8JSutN1qscMKaIUiRaB jEieUzGDUUxXIxlJNlpwqexRWEhrpIiYU+WP0iK3RnOKjCwa0MGXNNfTP1zXdaXqXtP1+fUl BmfFImrwRoUQNFewokIynhsUFuM4SzY7mwxSzDFIXwsmNiZ/a8SyrBnYDn5vn7H+NBiU2OzE wBx/HmXx82MUVUDQYQpQVC+eKkTp9XQM4UZROTO4XwqZqpdN/da4VO7oxw+3E9kWeGPwffAI eFPwPfBd/eqYs1s2io/HMJ6CE4PrgeuUD8q6MPZgTJC/8ZjiDopr5lB/utY3N5uPe//bFHe1 8QNSHY8p7n2fuP9d4m94kcfw5ubd5cfrG9giDTfbM89xrPP4yw6XYP2BovhdAfjwbfEbgoyS MjEQWSpe14KPAsGKKZIGS8HjIlJBTBQ5huEenDYkFTi9uo+9aO4T6EezjdyHwzmp4GyBn5Sg Ptt+2nbtFRlcpwnnchASzJ/Rbiu4QHe/PRuIBWdJJyI0nGOcl2gPG4tPEwgrKa8PUDs4O03Z Hw/nZOcg+ou+kDPw8PWsX1wqksdExJh0FaJWGiSAkEgWwRqXU2K6QNF4yToYNv0MUtFlpQDs buKmh5iR9VawS6+mbvqpLN/K+kOiHcQ7lsf8Dr9itQDHPvWnEGVdHCnN58gysU9xX9RYkiKP ylDOanIQspzgqVFmDNwZuKHq9LkgA9QFSZNniue0nyXiKRftaawurj1KumYz9bCMzClkNONi gyrGk8nEsbfnlsG2XGwQHyTtjQme9IIonHCJCSRt2hISEfGYNj2guABCYtJtjMfFMqXrppIk JSqkcXOYxEltqPIIyyQleL+9oWDzhcqplCV4ZSu6aoHAWvA03tEd328GGKcgUvUoyIss1CUQ Zp2CoRpE8pxkGcEIKUVFPiSBuMxTTuKWhOloxLMl2lgeUXg+RPon5uk+j032v6460HQ4eQ/9 3avLt8MMH97aHXitMTj7NLhdQD4gDmFKolvAXAl3C6Yo5g99ztOWPaRQPMPTO9ptxIuP5y2b JMuWKUsYwrIkt3WkDPceXSNSSmtaGiq7abZcYAaWA1ZIuiS4xbp0ZEwI3Hqlqhax8rLqSRKe pvxO1/gm0xPjtyC51mF7tjd1HAcr0LE1dSzXYDn5/eLNDPRSYJFujl9U2/am7GH66Ve4ZxDm 75NEUlW35OS8TFoDHM1eJcbU1myidNlU1WoSmrVNoFuS2dGlHKLka0HRqviR9CW6+Kx1MEwF 7ZPbHJ4hBFRtF5hY4be9pJoSfmumEJJGBaZVeoFGrWj8D0mLWt4/UXwZZOgAa6DuJKWJ6qbo tQnKc7eLsKA68dYp3WZgI2raehKRJbwA76Ah/zGGyvXdHiTb+FVrsNL2wVPJCxHRpz/OoAfY GIpn66c/csVty/Ynvatue5ZrH7byWm6b0YTeLJhiK5/0iYpeQSJ4hpWdX16v2P6pZe2J+wGx 2vyUsdpsYzWdlLGajk+nU68ZGOwfRC1d8/ALxZYzQoUKI1nzoqrQgkwXdS/g4ubDn6//C95c vf/7o8lVSBooPNqC8gbrBeS8c9I910RYTocdF0F3BLNaexjrVhUUOuPpW7TWldBQA9bZLA8J 9DfLHa2yaW8jtemjUqxoaXarWR8fafCQwFEGm3FvGKzXPZA0RXy0pvf1xdV27qgZPtcr77q6 m3d7F+69Lj7uHEdFBfNFIFNKlyX4G3HRxDI2ulTL5AMiRlveTBtdf6c3D4jbY810dPSMALXC V6uJ9GuD4yfa9DoU1RVEFQyD9G91M4EcPYbZ4ES7z0Nvl/QKOhNsl3fLPYYoMZj9wdul8mZt YK6zPbPrmzWnIeINKdy/SE6PvNd0oxfN3j11f0C7Y3FwQJuxGPS8HVBT/Nst48EBNcX9jgx4 4o/csxESLnOsG1gM2NFWVxYIzQxSJhWYvUaS4NbUkNeABybBjU/hl1f6xfW12PZuLaYyEmyp 74XClEe3vx62j9ZW9desUQ5PM/e1xQxeX129v5pBQrAGiXX9oyu+yj5DIuYB7tKIpsZYIijt SDYCsziRPaf15EgQDwkc5bJpbCPT3Ps2gyjlkpb/UPy2NGb1aAZuhwWsYous3spXlXQzXl0x rDj1rM1Busbw/Q+iX+AORx0AAA== --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sane-fujitsu.c-13-14.patch" --- sane-backends-1.0.14/backend/fujitsu.c.orig 2004-06-23 14:01:31.000000000 +0100 +++ sane-backends-1.0.14/backend/fujitsu.c 2004-06-23 14:17:44.000000000 +0100 @@ -4487,7 +4487,7 @@ if (!strncmp (product, "fi-4530C", 8) || !strncmp (product, "M3091", 5) || !strncmp (product, "M3092", 5) || - !strncmp (product, "fi-4120", 7) ) + s->model == MODEL_FI4x20) { /* These scanner don't support standard paper size specification * in bye 0x35 of the window descriptor block --6c2NcOVqGQ03X4Wi Content-Type: application/x-gunzip Content-Disposition: attachment; filename="fujitsu-13.log.gz" Content-Transfer-Encoding: base64 H4sICEBA3UAAA2Z1aml0c3UtMTMubG9nAO0ba4/bNvJz8iuIfuoBl11JluTHJQF6SVOkvWuD bHJ3QFEIlEjZTPSqSO3a9+tvSEm7FCXZ0u6maHsGDFsiZ4Yzw5nhjDX6meOMsoDQsNr+gq6o ECzbInWLEnpNE5THKK4+McErJHLkWBdPf27uf0ESOWAZE0NjG1RSTCS5KM9itkUxS2hL60KO aVhYCBztAh7hLKPlBl0Sen3JI84udzkX9mVYcetS4HJLhXeZVJl1uaUAyKIjNPKCZnL5+9O6 qkndUrp6dfUWlHPNIqrBRlVZ0kyga1pylmfaDCMwzuJDy5M2RXJQ0q8VKw86fG/EsqwNsh34 bT6+/NYARHlo0ZA+/jxKyfM5hGpDkGoKAFVunqhKJfXaR+FBUL7RoF+WPBEvTfqWr4g78uOF zUK2hVwfeR5yMXLXyHORt5C3jr66ZQO67yN/jRyCFi5aOOoDuAvku8jHAG98dHQH0CVwKL8X 1p2Y5mdxe62jLyTzR7AGPjq6+zB070Hob/IqI+jNx+/ffrj6iBpLA2d75jqO9Yp8au0SWT8A KvzWBjzdLf4KRkaxCgyYK8L7jvIBIbhmAidBUeakikRAsMBzAG6N00ZxbZxuV8ZRax5DGLdm G6Cnm3Ncm7OFvFgZ9ar5tu3OLQAsHNOc1SCKIX5GrSssEG2vXRthC63iQYuQ5kxgXSwlNDaf xiissdwxg2rN2TFxf3tzjlsBQV6QBa+QC7ercXQucEZwSSDoCrBark0hFGLOIrSH7eQQLgCV FGwA4DAOwAUtagLIHp48jEymeN8gDtGVs4fxWZY1uN4x1IHJG5aR/AZ+iNghx77w1ihKhyAS mm0BZGlfgF90QOIqi5QqNx08FLIMw6mhIgZ4BjhUd35b4iOzO5zEz0Se0XGQKE/ysr+MNQR1 gsjQajodluItRSlN8/IAJPzlcunYzbmlgRW7A9gHTkZ1Aid9iQUsWEAASUxeQlxGOaGmBBQ2 oOQQdI1xUhUJ3ZtE4gSLkBJzGJO4M1RLBGmSKPNxfsOSbXcio5wr4+U97YodGNYuT0g773ie qWBYAnMxQiCr0lCmQBB1KgZkwJK3OE0xaEgIWmbHMMAusyTHpIehCxrlaQE8qiMKzodIXkKc HpNYB//n+wFrmj59Yv77v7/97jjAu+/sAXvtADinKCyGDHmCHsIER58RxEp0s2OCQvyQ5zzt 8YMrkadweketI77+8KrHE2dpkbCYgVmq6T6NhIHv0T1YiuKmR6Hmm6bFDiIwP8IFpwUGFxui kbKyBNdTpHqTtZR1TRLnSZLfyBxfB3qqXZc4kzRs13bXjuNABupba8daaCBPvnn9ZoPkVkCS ro+/rt32o6phxuffg8+Amf8Ux5yKLidPXqmgdQTCrFUIhDaziJJpU52rcWTmNoEsSTazUzmw kl8rClyRR6IXy+SzU8EwEfRPbn14k3/WvR8nUQURkb4GeteU/AsnVSdkPxF5EaSwNjMM5klC YzE8I9UaqCNzaGJHZczszgyzATXkZ1NRTURupNnI5BZdS2j0FRS4CS2/0heMcIFeIPeLEJH2 URMAM+FRyQo4uDZDFB4TnOdVGdHJ4Cmcl5OB6wNzMji4Zp5UcnwyyuHZPZBmakgkz6bLAMCH ycBhOUD5iC2Z8I0leTPW6zN3fL3DQ9YrIPArt52sEYlR+/OX2k0MxyqGELOdsUttTjbdCtos bTJGm7VNdxYWzyB+m6JM910RcZrQaJZnqbxwMnRepyGT4dtsZPpeQ5Zyl59Mj3Eqb5ljIte4 ZDiLZK0xXZxbI4mq8no6GpRxZJ48PM1zsQN5ZgVv8CvIdmY5CmSw21JmEJNRspxBoQVlHkSc 6fuDRcn2zt6ZibHYL2ZiuHt3Joa39yZjqBRYZcB1AjwjShbyP8D/ztrML5hDgLNATj3PKEmZ FxAA1N8B0y0ZklYRVkJ8udM+wWkxj6kQzspc1QQzfJjSbCYOv8GFfOTyO9nzM/joRiWUwnA6 gHIk1zKzzLFc6ziJB6VrM0uBEXCTQX7H4ESMc/V0rp7O1dO5ejpXT+fq6Vw9naunc/V0rp7O 1dP/Cfjvvnp6BC4elNHy8Yz2iz98sy3bW/Ym2wdwtmst7JPsqIdwEq95LqyOPEoamWRfAkiF 4jJPkWN7qknV9i4sa85Dt4dWwpNSfT6e6v9pNuLQbMR6qTZi7V+s172NUOeKzkwefoLUFxRW ZQLU3pGirmoDmUzB1OuP7/7x7X+CN+9/+vGDDlVxGgjIWAPVZPwCZfngoic6eSHZCwd6dW8w EwPDgnIRVPLJtmx07nXtHuuRG+xnPIYgRRjuZxzoZtT5NR5hy24GSH8V2+b6tj+T4WMIsxjW 9W4wLPc9qEuj3vKe7C1u1o5M9S1c1Y483F9pt+o+KeLjrjFLKxAvAnW6KeM3exFgUulG1lsp v4fGaE+atdGYOSjNPfT2WCvN1p6moJ76Om0r8taA+BM5vVRF3SVaK0Ob+nfdPAoQI4zZyIna 76kNwHIHnSXCpN1uH0WxBuwdbQBWzc9H1lqdWF02PztdgKi9GOHq1CY57jArrinGqDW7t7On FTqsi8kKNXVxdNv6CtXR7xrBJytUR/ceIwLqhmvY9R8na9JIKCFRQUukWipfoKVvd9Yo2J4m PACIoIFwvMW6wzwMcxhfeFYHU2sG/lo2TMt+6b+Y+dRdQ/DXijxkRSaMSpVULDk1WMf6ULMN e5pHncCZZyW3nG367XpqcqiPT6byyqiooCX/o1sVgRp4h1Z9KzFtxLQu07aUdu+mDeOUZx5M Ne3JteY7vaRdgE0NIfcNqoH3337zGhlv/pjw8h4tLNdf1ftclxPwBYUBZ4QaqEEim1LV60RB mOTR57sGV53Kyfg+FMeXy/oNm0lmqS024b0iq2/8Ay/6DPiFmRxN+cw4Wk+hP+prcn15T6AP vSY3cjAPoHctLVAmtUFhFcf1uwq60UnYvyHH91fOwrObQbDgbf7bm+7T51c/vn338unDRHFW 8+TQEe4vh0blXi7oreXrnxNdUFvstAsSjJaw4lpd2M2FD4XKEpEILWNZ15EVhD/JBsGmC8rY 4CCyRkusAADSbS/87gjAkAEXlONRC0nqVVpqMGXp1EwXlAD1Kj5aeg2uTxpcP26mmgvPdMHl ul1OuaCUt6a2VDqpR1YtA0MuKBlYtRdei7tUF2FLFtcamGG3utHVdmuN2Kw6wSXIBhWsoChK ct5/pyGSDwkTbZTkR8Y26DNLEoNJDTAuKR0oCEuotDEf+UdlOR6PhtOiIwizciKdWSNX0ARW alPv5d/9m9lTooQxB+kehP0fNAHFbDxAAAA= --6c2NcOVqGQ03X4Wi Content-Type: application/x-gunzip Content-Disposition: attachment; filename="fujitsu-14-2.log.gz" Content-Transfer-Encoding: base64 H4sICI9A3UAAA2Z1aml0c3UtMTQtMi5sb2cA7Vvrb9w2Ev/s/BWDfOoBF1vvfVwSoBc3Rdq7 NoiT3gFFIVAStatYr4qU7f3vO6Qkm6Ieu+sYAZwaEGRpXhwOfxySo/XvjOQ08SMa1Js/4IJy nuQbkK+Q0iuaQhFDXH9OOKuBF2AZp89+b9//AKHsJ3nCx2hrqCiJhLmwyONkA3GS0s7WqaAp WoRzEm59FpI8p9UaziJ6dcZClpxtC8bNs6Bmxhkn1YZy9yytc+NsQ1EwCWdsFCXNRfP3t3XR mLq1dPHm4h0G5yoJqSIb1lVFcw5XtGJJkSucJEJ6Eu86nxRWVGCQ/qyTaqfKDyiGYazBtPBv e3nirgjwatepgUp/GWbRy2MMNUAQYfJRVQweryvZ65UHwY5TtlakX1cs5a91+4YnjVvicoO2 IdMAxwPXBYeAswLXAdcWr5baumGiuueBtwIrAtsB25IX6trgOeARlNcuVd1CdSEciLtt3HVT v+zbZ1XdFs7PaI1cqrrzZeruF6m/Leo8greffnr38eITtEjDyfbCsSzjTfS5wyUYP6Mq/m0A fPi0+CeCjBKZGAiThm96wUcF/yrhJPXLqojqkPsR4eQYgVtwmhA34HT6fZxE85TCNJpNlD4c znEDZwPcWIJ62d5Ns/eKAralw1kSIcb8GXZTwQbaPTsmEAOW8SgiBJwjbJeIHmqDT2MIGi1n ClAdnC1d9+vDOe46iP3FvpAlOPi6nFZnnOQRqSJMuhxRyxQWQEBYEsINDifDdIGqUZmMCOym BRinZWMAzHHmboKZkZtWccyu4O6muUne6rpzqiPM6ySPimv8E/EtWOapu4IwG5NIab5BkYV5 ivOiJxLXeShDue7pQZDkBFcNmTFwZuCE6vM3FZnhbkkav+BFTqdFwiItqmEzxpjUHiNjral2 koxsKGQ0K6odmvAWi4VltuuWIlZud4gPkk7GBFf6inBssMQEkuq+BKQKi4jqPaA4ABXDpKvR o7pM6Y1uJE4JD2ikk0kU90hNj3CbxKti2t+gSjZbnlPGJHjZILp8i8DaFmnU8S3X1QOMTRDG JwzkdRaILRBmnTpBM4jkDckyghHinFb5nAbiMk8LEg001I6GRVaij3KJwvUhFI+Yp6d6rIr/ 98MImg5n7+H/9O93P84LvP/RHMFrT8DaZ8EeA/IBcQhSEl4C5kq43iacYv4Q6zwd+ENqXmS4 eofdRDz/+GbgE0uyMk3iBGEp2UMbaYJzj94gUqQ3AwuN3zQrt5iB2YwXjJYEp9iYjSypKpx6 0tSA2fSyOZPERZoW12KPrwo9U54rkgsbpmM6K8uycAfqGSvLsBWRk+/P365BDAVu0lX6eTNt P8kzzDT/A84ZhPmvccwo73ty8kYmrRkJ/awSYWrTD1Fi29Ts1RjoextfHEnWR2/lECV/1hS9 ih7IXiw2n70TTML94cqtktcIAd6bBSpWistJVs9IcammEJKGNaZVeo5OXdHoN5LWvbx/wovS z7ADiYa6k5TGfJwjxsaX6+4YY0tF4u1zxt3Ag6jq60lISngFzkEk9yFIcnzbhaSNXzMGV8I/ eM6Kugrp86/n0D18DKoXN8+/5oibhukuJkfddAzbPGzkhV6b0SoxWTDFNn0SKyr2CuKqyHBn 58ryiumeGsaeuB8Qq903GatdG6vVQsZq5Z2uVo4eGDw/VL10XQSfKR45QzTIMZK9XjQ7ND8T m7pXcP7p/X9++L//9sOvv3xUpWpGfY5Lmy8rWK8gL0Yb3VMmwu10MFIIuiaY1YZk3LdyvxYZ T1TRBiWhuQPY6GF5TmH6sDxyVFb91VKbWCqrKyrdHhzWvSMdnlM4ymE17prDYtx9RlPEx6B5 VxSu2rZDPXy2I2td44d3swv33i4+bBtHRQXzhc9SSksJfi0ugiljI7ZqGbtHxOigNyvt1D/a m3vE7aFaOjp6SoAG4evticSrJvENTXoRiqYE0QRDYf2vqUygxIRjJlhhdz+0uiRG0Frgcbkb bg/CWBF2Z6tLsrI209ZyT+uismb1BcLuYcKrfYNkOeOuOHo3JtHs3HL3B3Q8FgcHVI/F7LAN A6qq31UZDw6oqu4+RAZUgavh+vHsmhQTspNQ4qFTntdfwcIze22UyQ1NmY8Sfithufaq5zyS GdJt1+hpKpWm70Q1ThTj/qHvp+6qTd9J87gr0mXkVknmkn3EJtcHCjbMw2bUHp3jUHLrWf/I ebft0/Nhd3SXoKKcVuyxoyqiJd/CcogSHSM6unRsyejesTVwijUPWW3tq4l8r1DRF1g3EmLc 8DTw4Yfvz0H7rKTLi3ewDcdbNuPcHCfwhgcDlkRUU/VTUfGQ36r8IC3Cy7vqiWplb34fy+OL RfP55iBYKo0d8NFqX0beu5zcV33P0jpyqeW4+eVk8BVsZjm5l/P9b7AHfTibRJovIbWGoI7j phCugk7I/gssz1tatmu2RETwpniC7uOB7jfz84F7Qdc1l0v7Cbp/P+hajx66lumY7hN0/37Q 1dUfHXTdlbFyFk/QfYLu44OuZziLVQ+6z15e/PLu/etnX2bZWh63hVYV7j8jFCv3mhHuSvys 9cAZoTS2f0bEHsRLiFcQu/KOz458WEjKUnlASU+fER29e3ClfGOkeTXlZUFs412fEYLldFpu dzUUryN6koLX4PTXqtvyvlAUPUl05b1xw9LUxYxode1O3upeze7B6ewIB/QZ0cp7t71Tetq8 GuKBLoASoDpc5nCrgq7BrTGBWVk8EiJrKJOSQpgWbPhbjZDkIU0ValTM0NZwmaSp5qQiGFeU jnyLqGhKCZv4mLeYTg/jFbkZhaPKcaqzWplK6bAMm/x/g4iysEpKXlSDIAoZnUhvsLN/AePU lCwUMQAA --6c2NcOVqGQ03X4Wi-- From henning@meier-geinitz.de Sat Jun 26 10:40:38 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 26 Jun 2004 11:40:38 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040625.232057.576037890.rene@rocklinux-consulting.de> References: <20040601215656.GA3524@ffii.org> <20040609134039.GA3769@ffii.org> <20040609151818.GO7920@meier-geinitz.de> <20040625.232057.576037890.rene@rocklinux-consulting.de> Message-ID: <20040626094038.GA22501@meier-geinitz.de> Hi, On Fri, Jun 25, 2004 at 11:20:57PM +0200, Rene Rebe wrote: > > An unrelated bug showed the same timeouts: > > - Epson Perfection 1260 (plustek), sane-backends-1.0.14, on Linux 2.6.7-rc2 > > and 2.4.25 with scanner.o(!) > > Reason: the epson backend tries to talk to this scanner > > You mean "talking" directly using libusb while the scanner module is > loaded or so? Although this gives a permission denied or so for me, > maybe with ohci this behaves differently? People with problems could > take a look if either scanner or hpsubscsi was / is loaded ... and > unload it just in case ... No, the problem in this case was that the epson backend thought that those scanners were supported by it. So the backend sent some commands to the scanner which the scanner didn't understand. --> timeout. That's fixed in CVS now. I haven't heard about any problem with scanner driver/ libusb interferences. However, there are problems with devices opened by libusb which are opened by other processed at the saame time. While the open fails, there still seems to be sent USB messages to the scanner and at least sometimes the scan process stops or images are corrupted. Bye, Henning From rene@rocklinux-consulting.de Sat Jun 26 13:55:13 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sat, 26 Jun 2004 14:55:13 +0200 (CEST) Subject: [sane-devel] Re: SANE/Avision the shifted image problem In-Reply-To: <1088252365.12036.5.camel@linux.site> References: <1088201812.7899.34.camel@linux.site> <20040626.002900.115919688.rene@rocklinux-consulting.de> <1088252365.12036.5.camel@linux.site> Message-ID: <20040626.145513.846957940.rene@rocklinux-consulting.de> Hi, On: Sat, 26 Jun 2004 14:19:25 +0200, Alberto Passalacqua wrote: > Thank you for your answer, > I installed the scanner on a clean SuSE 9.1 (Linux kernel 2.6.5-7.75= ) > installation in order to prevent problems due to my previous > experiments. > = > - usbfs is mounted to /proc/bus/usb > - /proc/bus/usb/001 contains two files 001 and 005, which I made > accessible by all users (chmod 666). > - hpusbscsi and scanner are not loaded (I can't find them). > = > If I start xsane both as root and as user, it still doesn't find the > scanner (No devices available message at startup). What is the output of: scanimage -L And versions of SANE are installed: scanimage -V ? Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene@rocklinux-consulting.de Sat Jun 26 18:03:21 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sat, 26 Jun 2004 19:03:21 +0200 (CEST) Subject: [sane-devel] Re: SANE/Avision the shifted image problem In-Reply-To: <1088266750.6477.24.camel@linux.site> References: <1088252365.12036.5.camel@linux.site> <20040626.145438.730575777.rene@rocklinux-consulting.de> <1088266750.6477.24.camel@linux.site> Message-ID: <20040626.190321.884032909.rene@rocklinux-consulting.de> Hi, On: Sat, 26 Jun 2004 18:19:11 +0200, Alberto Passalacqua wrote: > Hi Ren=C3=A9, > = > 1. scanimage -L gives: > = > device `avision:/dev/sg0' is a Hewlett-Packard ScanJet 5370C flatbed > scanner Ouhm - ok. Then make sure hpusbscsi is not loaded. Maybe just "rm" it from your system. The module is rather unstable and I have not even tested if recent backends work with it one bit. You _want_ to access your scanner from user-space using libusb. Neither hpusbscsi nor scanner must be loaded in order to do so. > P.S. If I do this twice, the first time I obtain the previous message= , > the second one I obtain the following one: Yep. The unstable hpusbscsi driver got stuck. Do not use it. > 2. scanimage -V gives: > = > scanimage (sane-backends) 1.0.13; backend version 1.0.1 Hm - I wonder how 1.0.13 and 1.0.1 get mixed here. I guess you have two version installed in parallel, where the binary is from e.g. /usr/local/bin and the library from /usr/lib ?!? (Henning?) Make sure you get 1.0.13 for both. Best by uninstalling both version and just installed the new one (e.g. from source). I usually recommend to use ./configure --prefix=3D/usr in order to install them into the location whre your distribution already placed the files. Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From anoah@pfeiffer.edu Sat Jun 26 19:33:06 2004 From: anoah@pfeiffer.edu (m. allan noah) Date: Sat, 26 Jun 2004 14:33:06 -0400 (EDT) Subject: [sane-devel] fujitsu fi-4220 problem with 1.0.14 + patch In-Reply-To: <20040626092512.GA12998@nimitz.cehill.co.uk> References: <20040626092512.GA12998@nimitz.cehill.co.uk> Message-ID: ah, yes. my fault. with older fujitsu models you have to look at the letters in the device model name to figure out of it has certain features, hence the string compair. with the 4x20's there are no such options, so i should have just looked at the model code we assigned. i will apply your fix to cvs on monday. allan On Sat, 26 Jun 2004 stan@saticed.me.uk wrote: > > Attached scanimage run with SANE_DEBUG_FUJITSU=20 set: > fujitsu-13.log.gz: with sane-backends 1.0.13 > fujitsu-14.log.gz: with sane-backends 1.0.14 > fujitsu-14-2.log.gz: sane-backends 1.0.14 + small patch > > Seems to be working ok for the last couple of days with patch. > The specificness of the error is impressive, thanks for all > the hard work sane and fujitsu backend maintainers! :-) > > -- "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 rene@rocklinux-consulting.de Sun Jun 27 10:29:11 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 11:29:11 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DE3F1A.9090803@mykec.net> References: <40DCCC41.3050606@mykec.net> <20040626.090846.653234575.rene@rocklinux-consulting.de> <40DE3F1A.9090803@mykec.net> Message-ID: <20040627.112911.576045809.rene@rocklinux-consulting.de> Hi, On: Sat, 26 Jun 2004 22:29:30 -0500, Myke Carter wrote: > OK. > = > First thing I tried was to uninstall "sane-backends-1.0.8-1.ximian.1"= .= > = > No go. There is some switch to "force" the uninstall ... - but just overwriting it is ok, too. > Try 2: > = > ./configure --sysconfigdir=3D/etc --prefix=3D/usr > = > This caused my Gnome panel applet to crash and made it so that I = > couldn't log out without hitting my reset button. Running "xsane" = > caused some kind of "relocation error" about a missing or bad = > ".so.1" file. The error revealed something about "/etc/li= b" = > so before I rebooted I tried it once more. This was the right configuration. When did the gnome-pannel crahs? During make install? > Try 3: > = > ./configure --sysconfdir=3D/etc --prefix=3D/usr/lib > = > This eliminated the previous problem but gave me new graphical dialog= = > box errors "No devices found." or something like that. So I rebooted= .= This configuration is very messy. /usr/lib is not a prefix you want ... Your binaries will be in /usrc/lib/bin and the libs in /usr/lib/lib. This will not produces results you want - neither the binaries nor libraries are found by your usual ld and PATH configuration ... > After rebooting, I restored my Gnome panel tasklist and tried again. > = > Now all I get is a dialogue box telling me "xsane: no devices availab= le". > = > Previously, with the old Ximian package that you said wouldn't work, = > xsane was at least able to find my scanner. > = > What now? You should install using your 2nd configuration. What does this give you: scanimage -L scanimage -V SANE_DEBUG_AVISION=3D7 xscanimage Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene@rocklinux-consulting.de Sun Jun 27 10:29:26 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 11:29:26 +0200 (CEST) Subject: [sane-devel] Re: SANE/Avision the shifted image problem In-Reply-To: <1088290427.15627.11.camel@linux.site> References: <1088266750.6477.24.camel@linux.site> <20040626.190321.884032909.rene@rocklinux-consulting.de> <1088290427.15627.11.camel@linux.site> Message-ID: <20040627.112926.596543533.rene@rocklinux-consulting.de> Hi, On: Sun, 27 Jun 2004 00:53:48 +0200, Alberto Passalacqua wrote: > Hi, > I removed the hpusbscsi and now "scanimage -L" properly tells that > "libusb" is used. It tells that also if I repeat the command a number= of > times. > As root, I can scan a preview which is Ok: the image has low quality = but > it is not shifted. Unfortunately, if I repeat the scan using for exam= ple > a 200dpi resolution, I obtain the shifted image again. > = > You gave me the link to three files (avision.conf, avision.c, > avision.h), but I don't know where to put them (hehe...not really a > linux expert here :-)). Should I recompile sane using those sources? Yes - place them in the sane-backends-$ver/backend directory and rebuild and reinstall the backends package. Unfortunately when 1.0.14 does produce a shifted image - my SVN snapshot will, too. But you can already rebuild the package as an exercise and I provide you whit custom patches to try to work around the problem after lunch. > Thanks a lot for your great help. Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene@rocklinux-consulting.de Sun Jun 27 10:29:37 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 11:29:37 +0200 (CEST) Subject: [sane-devel] Re: Undefined symbol in latest avision backend. In-Reply-To: <1088287482.2851.7.camel@epo.dk> References: <1088287482.2851.7.camel@epo.dk> Message-ID: <20040627.112937.115926508.rene@rocklinux-consulting.de> On: Sun, 27 Jun 2004 00:04:42 +0200, "Erik P. Olsen" wrote: > Hi Rene, > = > I downloaded today the avision backend from your svn repository, but > after installation I got from scanimage -L the following: > = > scanimage: error while loading shared libraries: > /usr/lib/sane/libsane-avision.so.1: undefined symbol: sanei_thread_in= it > = > In fact all sanei_thread_* are undefined symbols. > = > Do you have any cure for it? This also happend to me when I only did a partial sane-backends rebuild. Have you built the wohle sane-backends package from scratch? Maybe you have an old libsanei.so.* lying around in parallel to the new one? Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rohum@gmx.de Sat Jun 26 17:06:11 2004 From: rohum@gmx.de (Ronald Humphries) Date: Sat, 26 Jun 2004 18:06:11 +0200 Subject: [sane-devel] check-usb-chip request for help Message-ID: <1088265971.13295.15.camel@linux1.rohu.de> Hello Cosmin. I´m still here and reading this. Is the windows source the complete driver or a part of it? Anyway, if you need help, I will do my best. So far for me everything is clear, as Henning explained. Normally I have some time in the evening for programming, not much, because I´m alone with my 4 year old kid. -- Ronald Humphries From henning@meier-geinitz.de Sun Jun 27 10:48:43 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 27 Jun 2004 11:48:43 +0200 Subject: [sane-devel] Re: SANE/Avision the shifted image problem In-Reply-To: <20040626.190321.884032909.rene@rocklinux-consulting.de> References: <1088252365.12036.5.camel@linux.site> <20040626.145438.730575777.rene@rocklinux-consulting.de> <1088266750.6477.24.camel@linux.site> <20040626.190321.884032909.rene@rocklinux-consulting.de> Message-ID: <20040627094842.GA5025@meier-geinitz.de> Gi, On Sat, Jun 26, 2004 at 07:03:21PM +0200, Rene Rebe wrote: > > 2. scanimage -V gives: > > > > scanimage (sane-backends) 1.0.13; backend version 1.0.1 > > Hm - I wonder how 1.0.13 and 1.0.1 get mixed here. I guess you have > two version installed in parallel, where the binary is from > e.g. /usr/local/bin and the library from /usr/lib ?!? (Henning?) 1.0.13 is the version of sane-backends that was used to build scanimage. 1.0.1 is the SANE version number of the dll backend. At least on Linux scanimage is linked in a way that ensures linking with the correct libs. Therefore maybe it's just a cut-n-paste problem? Bye, Henning From rene@rocklinux-consulting.de Sun Jun 27 11:27:38 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 12:27:38 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DE9D11.4040609@mykec.net> References: <40DE3F1A.9090803@mykec.net> <20040627.112911.576045809.rene@rocklinux-consulting.de> <40DE9D11.4040609@mykec.net> Message-ID: <20040627.122738.28805691.rene@rocklinux-consulting.de> Hi, What does: SANE_DEBUG_AVISION=3D7 scanimage -L yield? > [root@sillygoose mykec]# sane-find-scanner > = > found SCSI scanner "HP ScanJet 5300C 4.00" at /dev/scanner > found SCSI scanner "HP ScanJet 5300C 4.00" at /dev/sg0 > found SCSI scanner "HP ScanJet 5300C 4.00" at /dev/sga > # Your SCSI scanner was detected. It may or may not be supported b= y > # SANE. Try scanimage -L and read the backend's manpage. Oh - you have the hpusbscsi module loaded. It is not very stable and therefore deprecated ... I had an report that it caused problems and locked up by another person just some days ago. Do you have libusb installed on your system? ls -l /usr/lib/libusb.so (rpm -q libusb or so - but I'm not used to rpm so --typos) Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene@rocklinux-consulting.de Sun Jun 27 11:52:51 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 12:52:51 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DEA54C.1030403@mykec.net> References: <40DE9D11.4040609@mykec.net> <20040627.122536.783397201.rene@rocklinux-consulting.de> <40DEA54C.1030403@mykec.net> Message-ID: <20040627.125251.971182931.rene@rocklinux-consulting.de> Hi, On: Sun, 27 Jun 2004 05:45:32 -0500, Myke Carter wrote: > [root@sillygoose sane]# SANE_DEBUG_AVISION=3D7 scanimage -L > = > No scanners were identified. If you were expecting something differen= t, > check that the scanner is plugged in, turned on and detected by the > sane-find-scanner tool (if appropriate). Please read the documentatio= n > which came with this software (README, FAQ, manpages). Hm - this is bad. This means for some reason the avision backend is not querried for devices present ... > [root@sillygoose sane]# rpm -q libusb > package libusb is not installed > > Oh - you have the hpusbscsi module loaded. It is not very stable an= d > > therefore deprecated ... I had an report that it caused problems an= d > > locked up by another person just some days ago. > = > With what should I replace it? You should use libusb to access the scanner from userspace. Can you take a look if libusb (and maybe libusb-devel) is present on your distribution CD - or available on the homepage? If you installed it, you need to recompile sane-backend to take advantage of libusb. What was the distribution you use and what is the version of the kernel (uname -a)? If the kernel is older - and libusb not easily available we can also focus on getting the backend working with the hpusbscsi module ... Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rob@bsdbox.homeunix.com Sun Jun 27 13:26:25 2004 From: rob@bsdbox.homeunix.com (Rob Mason) Date: Sun, 27 Jun 2004 13:26:25 +0100 Subject: [sane-devel] USB Scanning under FreeBSD Message-ID: <1088339184.33655.4.camel@dexter> This is a multi-part message in MIME format... ------------=_1088339175-191-176 Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-Disposition: inline After finally getting my BENQ USB scanner working under FreeBSD I thought I would share my solution for any FreeBSD users who would also struggling to get a workable scanning solution... http://bsdbox.homeunix.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=19&page=1 Hope this is useful... Rgds __________________________________________________ Rob's BSDBox Rob Mason's Weblog & Opensource Resource Pages http://bsdbox.homeunix.com ------------=_1088339175-191-176-- From rene@rocklinux-consulting.de Sun Jun 27 17:00:13 2004 From: rene@rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 18:00:13 +0200 (CEST) Subject: [sane-devel] Re: Undefined symbol in latest avision backend. In-Reply-To: <20040627.112937.115926508.rene@rocklinux-consulting.de> References: <1088287482.2851.7.camel@epo.dk> <20040627.112937.115926508.rene@rocklinux-consulting.de> Message-ID: <20040627.180013.336492724.rene@rocklinux-consulting.de> Hi, On: Sun, 27 Jun 2004 11:29:37 +0200 (CEST), Rene Rebe wrote: > This also happend to me when I only did a partial sane-backends > rebuild. Have you built the wohle sane-backends package from scratch?= > Maybe you have an old libsanei.so.* lying around in parallel to the > new one? Ah now I see why this happens, you need this line in your backend/Makefile in oder to link against the sanei_thread library: libsane-avision.la: ../sanei/sanei_thread.lo Just put it near the other libsane-avision.la: lines already present there ... (if you want to rerun ./configure you either need to put it again into the file - or also place it in the backends/Makefile.in - since the Makefile is generated from the .in one ... Can you test if scanning works well if you put this into the /etc/sane.d/avision.conf (or the config file used in your configuration): disable-calibration and tell me if the scans with disabled calibration are correct, without shifting? Sincerely yours, Ren=E9 Rebe - ROCK Linux stable release maintainer -- = Ren=E9 Rebe - Europe/Germany/Berlin rene@rocklinux.org rene@rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From joseos@okstate.edu Sun Jun 27 21:54:24 2004 From: joseos@okstate.edu (Jose Sanchez) Date: Sun, 27 Jun 2004 15:54:24 -0500 Subject: [sane-devel] Which are the modules to load for a scsi scanner in the kernel 2.6 Message-ID: <40DF3400.7050208@okstate.edu> Hi, I recently migrated from SUSE 9.0 Kernel 2.4.20 to SUSE 9.1 Kernel 2.6.4. I want to install my scsi scanner but I don't find the modules that I used to load before (onscsi and ppscsi). Could someone tell me which modules I have to load now? thanks Jose From jochen@penguin-breeder.org Sun Jun 27 22:17:06 2004 From: jochen@penguin-breeder.org (Jochen Eisinger) Date: Sun, 27 Jun 2004 23:17:06 +0200 Subject: [sane-devel] Which are the modules to load for a scsi scanner in the kernel 2.6 In-Reply-To: <40DF3400.7050208@okstate.edu> References: <40DF3400.7050208@okstate.edu> Message-ID: <40DF3952.3030000@penguin-breeder.org> Hi, i have ported the ppscsi driver suite to 2.6 and try to keep it working. You could submit a request to SuSE to include it in future kernels, if enough people ask for it, they will probably include it. The patch is available from my homepage: http://penguin-breeder.org/kernel/#ppscsi kind regards -- jochen From christoph.knauer@web.de Mon Jun 28 07:51:46 2004 From: christoph.knauer@web.de (Christoph Knauer) Date: Mon, 28 Jun 2004 08:51:46 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) Message-ID: <200406280851.54167.christoph.knauer@web.de> --Boundary-02=_KA83AJPnTl/H6cg Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi,=20 I've tried to compile and install xsane 0.94. When I start xsane from conso= le,=20 nothing happens, only the message "Speicherzugriffsfehler" (Memory access=20 error) appears. Next I've downloaded a rpm from packman, and there the eula pops up, but wi= th=20 the click on "accept" the message above appears again. With xsane 0.93 all works fine. My system: SuSE 9.1 prof. Kernel 2.6.5-7.75-default KDE 3.2.3 Thanx, Christoph =2D-=20 GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261 --Boundary-02=_KA83AJPnTl/H6cg Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBA38AJgy/nEXRCgmERAjjJAJsHSv+qPhv74Icy+7bZhL1/WKqGMgCfZHe+ G7dvaBREgYWF4WfSYiXUI+Y= =mKkx -----END PGP SIGNATURE----- --Boundary-02=_KA83AJPnTl/H6cg-- From picos132004@yahoo.co.uk Mon Jun 28 15:08:09 2004 From: picos132004@yahoo.co.uk (=?iso-8859-1?q?Ioan-Cosmin=20Pop?=) Date: Mon, 28 Jun 2004 15:08:09 +0100 (BST) Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <1088265971.13295.15.camel@linux1.rohu.de> Message-ID: <20040628140809.27363.qmail@web25108.mail.ukl.yahoo.com> Hi Ronald! Thank you for answering! --- Ronald Humphries wrote: > Hello Cosmin. > > I´m still here and reading this. Is the windows > source the complete > driver or a part of it? It's the complete driver. Anything needed to acces the scanner is there. > > Anyway, if you need help, I will do my best. So far > for me everything is > clear, as Henning explained. Yes, I need help, somebody to talk to. I thought I can do it all alone, but I can't. I would really like you to have also the windows sources, so we have a common ground. What do you think? > > Normally I have some time in the evening for > programming, not much, > because I´m alone with my 4 year old kid. Send him all the best from me :) > -- > Ronald Humphries > Cosmin ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com From henning@meier-geinitz.de Mon Jun 28 17:33:37 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 28 Jun 2004 18:33:37 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <200406280851.54167.christoph.knauer@web.de> References: <200406280851.54167.christoph.knauer@web.de> Message-ID: <20040628163336.GA12239@meier-geinitz.de> Hi, On Mon, Jun 28, 2004 at 08:51:46AM +0200, Christoph Knauer wrote: > I've tried to compile and install xsane 0.94. When I start xsane from console, > nothing happens, only the message "Speicherzugriffsfehler" (Memory access > error) appears. > Next I've downloaded a rpm from packman, and there the eula pops up, but with > the click on "accept" the message above appears again. http://www.xsane.org/ First news item. If that's not your problem, tell us more details (which scanner, which backend?). Bye, Henning From henning@meier-geinitz.de Mon Jun 28 18:06:45 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 28 Jun 2004 19:06:45 +0200 Subject: [sane-devel] Experience with brother backend? Message-ID: <20040628170645.GG12273@meier-geinitz.de> Hi, Has anyone already tested the brother backend? Link: http://solutions.brother.com/Library/sol/printer/linux/sane_drivers.html It seems to be based on an old SANE version without libusb support so it may be difficult to use on 2.6 :-/ It claims to supporte these models: DCP Models: DCP-1000 DCP-1400 DCP-8020 DCP-8025D FAX Models: FAX1815C FAX1820C FAX1920CN FAX-2850 FAX-2900 FAX-3800 FAX-4100 FAX-4750e FAX-5750e MFC Models: MFC3220C MFC3320CN MFC3420C MFC3820CN MFC-4800 MFC-6800 MFC-8220 MFC-8420 MFC-8500 MFC-8820D MFC-9030 MFC-9070 MFC-9160 MFC-9180 MFC-9660 MFC-9700 MFC-9760 MFC-9800 MFC-9860 MFC-9880 Any experiences with that backend? I'd like to add these scanners to our lists for external backends but first I want to know if the driver works at all. Bye, Henning From anoah@pfeiffer.edu Mon Jun 28 18:27:20 2004 From: anoah@pfeiffer.edu (m. allan noah) Date: Mon, 28 Jun 2004 13:27:20 -0400 (EDT) Subject: [sane-devel] Experience with brother backend? In-Reply-To: <20040628170645.GG12273@meier-geinitz.de> References: <20040628170645.GG12273@meier-geinitz.de> Message-ID: an objdump on the .so, plus some comments in the faq make me think it uses libusb. i have not used the code, though. i have a brother printer, but no mfc. i have a bigger question, though. is their packaging of gpl'd and lgpl'd and proprietary code together ok? allan On Mon, 28 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > Has anyone already tested the brother backend? Link: > http://solutions.brother.com/Library/sol/printer/linux/sane_drivers.html > > It seems to be based on an old SANE version without libusb support so > it may be difficult to use on 2.6 :-/ > > It claims to supporte these models: > DCP Models: > DCP-1000 DCP-1400 DCP-8020 DCP-8025D > FAX Models: > FAX1815C FAX1820C FAX1920CN FAX-2850 FAX-2900 > FAX-3800 FAX-4100 FAX-4750e FAX-5750e > MFC Models: > MFC3220C MFC3320CN MFC3420C MFC3820CN MFC-4800 > MFC-6800 MFC-8220 MFC-8420 MFC-8500 MFC-8820D > MFC-9030 MFC-9070 MFC-9160 MFC-9180 MFC-9660 > MFC-9700 MFC-9760 MFC-9800 MFC-9860 MFC-9880 > > Any experiences with that backend? > > I'd like to add these scanners to our lists for external backends but > first I want to know if the driver works at all. > > Bye, > Henning > > -- "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 Mon Jun 28 18:46:45 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 28 Jun 2004 19:46:45 +0200 Subject: [sane-devel] Experience with brother backend? In-Reply-To: References: <20040628170645.GG12273@meier-geinitz.de> Message-ID: <20040628174645.GK12273@meier-geinitz.de> Hi, On Mon, Jun 28, 2004 at 01:27:20PM -0400, m. allan noah wrote: > an objdump on the .so, plus some comments in the faq make me think it uses > libusb. Maybe it's used directly (without the use of sanei_usb). I haven't looked into the details. > i have not used the code, though. i have a brother printer, but no mfc. > > i have a bigger question, though. is their packaging of gpl'd and lgpl'd > and proprietary code together ok? I'm not really sure. Concerning the SANE license (e.g. sanei_usb.c) it *could* be ok, even if using parts of the sane distribution with proprietary backends wasn't the intention of the SANE exception. I haven't checked the implications of using their license in combination with GPL/SANE and LGPL, however. I'd never put such part of software on any of my website because of this license nightmare :-/ Bye, Henning From henning@meier-geinitz.de Mon Jun 28 19:45:38 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 28 Jun 2004 20:45:38 +0200 Subject: [sane-devel] a new function for sane-desc! In-Reply-To: <1088078757.3362.61.camel@localhost> References: <1088078757.3362.61.camel@localhost> Message-ID: <20040628184538.GL12273@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 02:05:57PM +0200, jose wrote: > Hi, finally I have made a new function in sane-desc to get an xml > output. > > I think that only have to send the patch, if there is any problem please > email me, this is the first time that I make something similar.. I've just comitted your patch to CVS. Thanks again! Bye, Henning From christoph.knauer@web.de Mon Jun 28 21:16:07 2004 From: christoph.knauer@web.de (Christoph Knauer) Date: Mon, 28 Jun 2004 22:16:07 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <1088442328.2125.8.camel@Babylon7> References: <200406280851.54167.christoph.knauer@web.de> <1088442328.2125.8.camel@Babylon7> Message-ID: <200406282216.07084.christoph.knauer@web.de> Hi, aber nur mit dem Binary-Package vom Packman. Zumindest scheint es wieder zu laufen ... Danke Am Montag, 28. Juni 2004 19:05 schrieb Oliver Rauch: > Hallo Christoph, > > ich vermute, Du musst ~/.sane/xsane/xsane.rc loeschen oder umbenennen. > > Gruss > Oliver -- GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261 ------------------------------------------------------------------ Bitte beachtet auch meinen Profiseller-Shop unter http://www.profiseller.de/shop/christoph-knauer From pmsguevarra@yahoo.com Tue Jun 29 02:54:29 2004 From: pmsguevarra@yahoo.com (Peter Mark Guevarra) Date: Mon, 28 Jun 2004 18:54:29 -0700 (PDT) Subject: [sane-devel] different scan outputs for different Linux distributions Message-ID: <20040629015429.77026.qmail@web41015.mail.yahoo.com> --0-149988181-1088474069=:76993 Content-Type: text/plain; charset=us-ascii Hello, Sorry for this late response..I have tested scanimage with Red Hat 8 and Red Hat 9. The output in Red Hat 9 is darker compared with that of Red Hat 8 but exactly the same settings were used.. You have said in your previous reply that xsane should not modify gamma settings automatically..I`m quite confused with the use of the options..How may I be able to do this? Thanks a lot, PMG Hi, On Mon, Jun 21, 2004 at 02:57:17AM -0700, Peter Mark Guevarra wrote: > Has anyone encountered this problem wherein the same frontend, xsane > or xscanimage for instance, has different outputs for RedHat, and > SuSE or Mandrake? Same settings were used in the frontend but > different outputs resulted for different distributions, one is > darker/brighter than the other. I haven't heard about such a behaviour. Can you reproduce it with scanimage? Maybe the scanner wasn't warmed up completely in one of the tests? > Also, in the case of using only one Linux Distribution, RedHat for > example, is it expected to have the same output for the different > SANE frontends given the default settings for each frontend? Yes, if you don't use any of the color enhancement settings. E.g. make sure that xsane doesn't modify your gamma settings automatically. Bye, Henning --------------------------------- Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! --0-149988181-1088474069=:76993 Content-Type: text/html; charset=us-ascii
Hello,
 
     Sorry for this late response..I have tested scanimage with Red Hat 8 and Red Hat 9.
The output in Red Hat 9 is darker compared with that of Red Hat 8 but exactly the same settings were used..
     You have said in your previous reply that xsane should not modify gamma settings automatically..I`m quite confused with the use of the options..How may I be able to do this?
 
Thanks a lot,
PMG
 
 
Hi,

On Mon, Jun 21, 2004 at 02:57:17AM -0700, Peter Mark Guevarra wrote:
> Has anyone encountered this problem wherein the same frontend, xsane
> or xscanimage for instance, has different outputs for RedHat, and
> SuSE or Mandrake?  Same settings were used in the frontend but
> different outputs resulted for different distributions, one is
> darker/brighter than the other. 

I haven't heard about such a behaviour. Can you reproduce it with
scanimage? Maybe the scanner wasn't warmed up completely in one of the
tests?

> Also, in the case of using only one Linux Distribution, RedHat for
> example, is it expected to have the same output for the different
> SANE frontends given the default settings for each frontend?

Yes, if you don't use any of the color enhancement settings. E.g. make
sure that xsane doesn't modify your gamma settings automatically.

Bye,
  Henning

Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out! --0-149988181-1088474069=:76993-- From C.W.J.Lemmens@ewi.tudelft.nl Tue Jun 29 09:52:16 2004 From: C.W.J.Lemmens@ewi.tudelft.nl (Kees Lemmens) Date: Tue, 29 Jun 2004 10:52:16 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <20040628163336.GA12239@meier-geinitz.de> References: <200406280851.54167.christoph.knauer@web.de> <20040628163336.GA12239@meier-geinitz.de> Message-ID: <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> Hi, I have the same problem with xsane 0.94, but although it indeed works for most users, with some other users the problem doesn't disappear by just removing the xsane.rc ! For those users where it still crashed we could fix the problem by changing the version number from 0.91 to 0.94 in xsane.rc and remove most of the remaining lines except the first 10 or so. However, as soon as you would rename the xsane.rc the seg faults occur again, so we really think there must be more wrong than only this minor xsane.rc problem. Attached a coredump analysis using gdb. Seems to be gdk related. Maybe something todo with their personalized Gdk/Gtk settings ? Bye, Kees Lemmens. TU Delft, Netherlands. On Monday 28 June 2004 18:33, Henning Meier-Geinitz wrote: > Hi, > > On Mon, Jun 28, 2004 at 08:51:46AM +0200, Christoph Knauer wrote: > > I've tried to compile and install xsane 0.94. When I start xsane > > from console, nothing happens, only the message > > "Speicherzugriffsfehler" (Memory access error) appears. > > Next I've downloaded a rpm from packman, and there the eula pops > > up, but with the click on "accept" the message above appears again. > > http://www.xsane.org/ > First news item. > > If that's not your problem, tell us more details (which scanner, > which backend?). > > Bye, > Henning testsys:/tmp 50 % gdb /opt/xsane/bin/xsane core GNU gdb 5.3 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-slackware-linux"... Core was generated by `/opt/xsane/bin/xsane -n'. Program terminated with signal 11, Segmentation fault. Reading symbols from /opt/sane/lib/libsane.so...done. Loaded symbols for /opt/sane/lib/libsane.so Reading symbols from /usr/lib/libusb-0.1.so.4...done. Loaded symbols for /usr/lib/libusb-0.1.so.4 Reading symbols from /lib/libnsl.so.1...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libm.so.6...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /usr/lib/libjpeg.so.62...done. Loaded symbols for /usr/lib/libjpeg.so.62 Reading symbols from /usr/lib/libieee1284.so.3...done. Loaded symbols for /usr/lib/libieee1284.so.3 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /usr/lib/libgimpui-1.2.so.0...done. Loaded symbols for /usr/lib/libgimpui-1.2.so.0 Reading symbols from /usr/lib/libgimp-1.2.so.0...done. Loaded symbols for /usr/lib/libgimp-1.2.so.0 Reading symbols from /usr/lib/libgtk-1.2.so.0...done. Loaded symbols for /usr/lib/libgtk-1.2.so.0 Reading symbols from /usr/lib/libgdk-1.2.so.0...done. Loaded symbols for /usr/lib/libgdk-1.2.so.0 Reading symbols from /usr/lib/libgmodule-1.2.so.0...done. Loaded symbols for /usr/lib/libgmodule-1.2.so.0 Reading symbols from /usr/lib/libglib-1.2.so.0...done. Loaded symbols for /usr/lib/libglib-1.2.so.0 Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Loaded symbols for /usr/X11R6/lib/libXext.so.6 Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Loaded symbols for /usr/X11R6/lib/libX11.so.6 Reading symbols from /usr/lib/libpng.so.3...done. Loaded symbols for /usr/lib/libpng.so.3 Reading symbols from /usr/lib/libtiff.so.3...done. Loaded symbols for /usr/lib/libtiff.so.3 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ xlcDef.so.2...done. Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 Reading symbols from /lib/libnss_files.so.2...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ ximcp.so.2...done. Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2 Reading symbols from /lib/libnss_compat.so.2...done. Loaded symbols for /lib/libnss_compat.so.2 Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done. Loaded symbols for /usr/X11R6/lib/libXcursor.so.1 Reading symbols from /usr/X11R6/lib/libXrender.so.1...done. Loaded symbols for /usr/X11R6/lib/libXrender.so.1 #0 0x40218451 in gdk_gc_new_with_values () from /usr/lib/ libgdk-1.2.so.0 From mlists@protocol.gr Tue Jun 29 13:57:40 2004 From: mlists@protocol.gr (Panos Katergiathis) Date: Tue, 29 Jun 2004 15:57:40 +0300 Subject: [sane-devel] Problem with Fedora Core 2 Message-ID: <40E16744.2010307@protocol.gr> Hello I have configured my scanner with sane running in Fedora Core 2. Whenever i try to run xsane or 'scanimage -L' the system does not find any scanner attached... until i unplug the usb cable, wait a couple of seconds and plug it back again. The whole time, the Fedora's hardware browser DOES detect the scanner attached properly. The symptom re-appears after rebooting. Each time, after replugging the cable everything works perfectly. Any help will be appreciated. Panos From twaugh@redhat.com Tue Jun 29 14:44:15 2004 From: twaugh@redhat.com (Tim Waugh) Date: Tue, 29 Jun 2004 14:44:15 +0100 Subject: [sane-devel] Problem with Fedora Core 2 In-Reply-To: <40E16744.2010307@protocol.gr> References: <40E16744.2010307@protocol.gr> Message-ID: <20040629134415.GZ1594@redhat.com> --xYxgRrcmUCOORODc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 29, 2004 at 03:57:40PM +0300, Panos Katergiathis wrote: > Hello >=20 > I have configured my scanner with sane running in Fedora Core 2.=20 > Whenever i try to run xsane or 'scanimage -L' the system does not find=20 > any scanner attached... until i unplug the usb cable, wait a couple of=20 > seconds and plug it back again. The whole time, the Fedora's hardware=20 > browser DOES detect the scanner attached properly. The symptom=20 > re-appears after rebooting. Each time, after replugging the cable=20 > everything works perfectly. >=20 > Any help will be appreciated. This has been discussed a-plenty on the fedora-list, for instance here: http://www.redhat.com/archives/fedora-list/2004-June/msg00279.html and also in bugzilla: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=3D121511 Short story: this needs a fix in the hotplug script of some sort, but it isn't yet clear what is needed. Tim. */ --xYxgRrcmUCOORODc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFA4XIu9gevn0C09XYRAjShAKCkME1y6YfJD10z5qMTigGLyvTFDwCgx7Tg QjPeQmcD3553wbGm+lwDOSo= =9T8E -----END PGP SIGNATURE----- --xYxgRrcmUCOORODc-- From C.W.J.Lemmens@ewi.tudelft.nl Tue Jun 29 16:09:10 2004 From: C.W.J.Lemmens@ewi.tudelft.nl (Kees Lemmens) Date: Tue, 29 Jun 2004 17:09:10 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> References: <200406280851.54167.christoph.knauer@web.de> <20040628163336.GA12239@meier-geinitz.de> <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> Message-ID: <200406291709.10943.C.W.J.Lemmens@ewi.tudelft.nl> Hi, The seg fault problem seems to be caused by an old ~/.gtkrc file with illegal content: as soon as I remove this file all problems are gone !! Don't know which line is responsible, but just decided to discard this file completely to avoid any xsane seg faults as it doesn't seem to be that important for KDE users ;) -- Bye, Kees Lemmens. On Tuesday 29 June 2004 10:52, Kees Lemmens wrote: > Hi, > > I have the same problem with xsane 0.94, but although it indeed > works for most users, with some other users the problem doesn't > disappear by just removing the xsane.rc ! > > For those users where it still crashed we could fix the problem by > changing the version number from 0.91 to 0.94 in xsane.rc and remove > most of the remaining lines except the first 10 or so. > > However, as soon as you would rename the xsane.rc the seg faults > occur again, so we really think there must be more wrong than only > this minor xsane.rc problem. > > Attached a coredump analysis using gdb. Seems to be gdk related. > Maybe something todo with their personalized Gdk/Gtk settings ? > > Bye, > Kees Lemmens. > TU Delft, Netherlands. > > On Monday 28 June 2004 18:33, Henning Meier-Geinitz wrote: > > Hi, > > > > On Mon, Jun 28, 2004 at 08:51:46AM +0200, Christoph Knauer wrote: > > > I've tried to compile and install xsane 0.94. When I start xsane > > > from console, nothing happens, only the message > > > "Speicherzugriffsfehler" (Memory access error) appears. > > > Next I've downloaded a rpm from packman, and there the eula pops > > > up, but with the click on "accept" the message above appears > > > again. > > > > http://www.xsane.org/ > > First news item. > > > > If that's not your problem, tell us more details (which scanner, > > which backend?). > > > > Bye, > > Henning > > testsys:/tmp 50 % gdb /opt/xsane/bin/xsane core > GNU gdb 5.3 > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-slackware-linux"... > Core was generated by `/opt/xsane/bin/xsane -n'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /opt/sane/lib/libsane.so...done. > Loaded symbols for /opt/sane/lib/libsane.so > Reading symbols from /usr/lib/libusb-0.1.so.4...done. > Loaded symbols for /usr/lib/libusb-0.1.so.4 > Reading symbols from /lib/libnsl.so.1...done. > Loaded symbols for /lib/libnsl.so.1 > Reading symbols from /lib/libm.so.6...done. > Loaded symbols for /lib/libm.so.6 > Reading symbols from /usr/lib/libjpeg.so.62...done. > Loaded symbols for /usr/lib/libjpeg.so.62 > Reading symbols from /usr/lib/libieee1284.so.3...done. > Loaded symbols for /usr/lib/libieee1284.so.3 > Reading symbols from /lib/libdl.so.2...done. > Loaded symbols for /lib/libdl.so.2 > Reading symbols from /usr/lib/libgimpui-1.2.so.0...done. > Loaded symbols for /usr/lib/libgimpui-1.2.so.0 > Reading symbols from /usr/lib/libgimp-1.2.so.0...done. > Loaded symbols for /usr/lib/libgimp-1.2.so.0 > Reading symbols from /usr/lib/libgtk-1.2.so.0...done. > Loaded symbols for /usr/lib/libgtk-1.2.so.0 > Reading symbols from /usr/lib/libgdk-1.2.so.0...done. > Loaded symbols for /usr/lib/libgdk-1.2.so.0 > Reading symbols from /usr/lib/libgmodule-1.2.so.0...done. > Loaded symbols for /usr/lib/libgmodule-1.2.so.0 > Reading symbols from /usr/lib/libglib-1.2.so.0...done. > Loaded symbols for /usr/lib/libglib-1.2.so.0 > Reading symbols from /usr/X11R6/lib/libXext.so.6...done. > Loaded symbols for /usr/X11R6/lib/libXext.so.6 > Reading symbols from /usr/X11R6/lib/libX11.so.6...done. > Loaded symbols for /usr/X11R6/lib/libX11.so.6 > Reading symbols from /usr/lib/libpng.so.3...done. > Loaded symbols for /usr/lib/libpng.so.3 > Reading symbols from /usr/lib/libtiff.so.3...done. > Loaded symbols for /usr/lib/libtiff.so.3 > Reading symbols from /usr/lib/libz.so.1...done. > Loaded symbols for /usr/lib/libz.so.1 > Reading symbols from /lib/libc.so.6...done. > Loaded symbols for /lib/libc.so.6 > Reading symbols from /lib/ld-linux.so.2...done. > Loaded symbols for /lib/ld-linux.so.2 > Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ > xlcDef.so.2...done. > Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 > Reading symbols from /lib/libnss_files.so.2...done. > Loaded symbols for /lib/libnss_files.so.2 > Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ > ximcp.so.2...done. > Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2 > Reading symbols from /lib/libnss_compat.so.2...done. > Loaded symbols for /lib/libnss_compat.so.2 > Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done. > Loaded symbols for /usr/X11R6/lib/libXcursor.so.1 > Reading symbols from /usr/X11R6/lib/libXrender.so.1...done. > Loaded symbols for /usr/X11R6/lib/libXrender.so.1 > #0 0x40218451 in gdk_gc_new_with_values () from /usr/lib/ > libgdk-1.2.so.0 From Oliver.Rauch@Rauch-Domain.DE Tue Jun 29 17:00:12 2004 From: Oliver.Rauch@Rauch-Domain.DE (Oliver Rauch) Date: 29 Jun 2004 18:00:12 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> References: <200406280851.54167.christoph.knauer@web.de> <20040628163336.GA12239@meier-geinitz.de> <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> Message-ID: <1088524811.2123.2.camel@Babylon7> Hello Kees, I do not understand how you can change the version from 0.91 to 0.94 in xsane.rc when you removed the file xsane.rc, in this case the file is deleted so you can not change anything in the file! When the problem still occurs then please do: rm ~/.sane/xsane/xsane.rc export XSANE_DEBUG=12 xsane 2>debug.txt gzip debug.txt and send debug.txt.gz to me (directly, not to the list). Oliver Am Die, 2004-06-29 um 10.52 schrieb Kees Lemmens: > Hi, > > I have the same problem with xsane 0.94, but although it indeed works > for most users, with some other users the problem doesn't disappear by > just removing the xsane.rc ! > > For those users where it still crashed we could fix the problem by > changing the version number from 0.91 to 0.94 in xsane.rc and remove > most of the remaining lines except the first 10 or so. > > However, as soon as you would rename the xsane.rc the seg faults occur > again, so we really think there must be more wrong than only this minor > xsane.rc problem. > > Attached a coredump analysis using gdb. Seems to be gdk related. Maybe > something todo with their personalized Gdk/Gtk settings ? > > Bye, > Kees Lemmens. > TU Delft, Netherlands. > > On Monday 28 June 2004 18:33, Henning Meier-Geinitz wrote: > > Hi, > > > > On Mon, Jun 28, 2004 at 08:51:46AM +0200, Christoph Knauer wrote: > > > I've tried to compile and install xsane 0.94. When I start xsane > > > from console, nothing happens, only the message > > > "Speicherzugriffsfehler" (Memory access error) appears. > > > Next I've downloaded a rpm from packman, and there the eula pops > > > up, but with the click on "accept" the message above appears again. > > > > http://www.xsane.org/ > > First news item. > > > > If that's not your problem, tell us more details (which scanner, > > which backend?). > > > > Bye, > > Henning > > testsys:/tmp 50 % gdb /opt/xsane/bin/xsane core > GNU gdb 5.3 > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-slackware-linux"... > Core was generated by `/opt/xsane/bin/xsane -n'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /opt/sane/lib/libsane.so...done. > Loaded symbols for /opt/sane/lib/libsane.so > Reading symbols from /usr/lib/libusb-0.1.so.4...done. > Loaded symbols for /usr/lib/libusb-0.1.so.4 > Reading symbols from /lib/libnsl.so.1...done. > Loaded symbols for /lib/libnsl.so.1 > Reading symbols from /lib/libm.so.6...done. > Loaded symbols for /lib/libm.so.6 > Reading symbols from /usr/lib/libjpeg.so.62...done. > Loaded symbols for /usr/lib/libjpeg.so.62 > Reading symbols from /usr/lib/libieee1284.so.3...done. > Loaded symbols for /usr/lib/libieee1284.so.3 > Reading symbols from /lib/libdl.so.2...done. > Loaded symbols for /lib/libdl.so.2 > Reading symbols from /usr/lib/libgimpui-1.2.so.0...done. > Loaded symbols for /usr/lib/libgimpui-1.2.so.0 > Reading symbols from /usr/lib/libgimp-1.2.so.0...done. > Loaded symbols for /usr/lib/libgimp-1.2.so.0 > Reading symbols from /usr/lib/libgtk-1.2.so.0...done. > Loaded symbols for /usr/lib/libgtk-1.2.so.0 > Reading symbols from /usr/lib/libgdk-1.2.so.0...done. > Loaded symbols for /usr/lib/libgdk-1.2.so.0 > Reading symbols from /usr/lib/libgmodule-1.2.so.0...done. > Loaded symbols for /usr/lib/libgmodule-1.2.so.0 > Reading symbols from /usr/lib/libglib-1.2.so.0...done. > Loaded symbols for /usr/lib/libglib-1.2.so.0 > Reading symbols from /usr/X11R6/lib/libXext.so.6...done. > Loaded symbols for /usr/X11R6/lib/libXext.so.6 > Reading symbols from /usr/X11R6/lib/libX11.so.6...done. > Loaded symbols for /usr/X11R6/lib/libX11.so.6 > Reading symbols from /usr/lib/libpng.so.3...done. > Loaded symbols for /usr/lib/libpng.so.3 > Reading symbols from /usr/lib/libtiff.so.3...done. > Loaded symbols for /usr/lib/libtiff.so.3 > Reading symbols from /usr/lib/libz.so.1...done. > Loaded symbols for /usr/lib/libz.so.1 > Reading symbols from /lib/libc.so.6...done. > Loaded symbols for /lib/libc.so.6 > Reading symbols from /lib/ld-linux.so.2...done. > Loaded symbols for /lib/ld-linux.so.2 > Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ > xlcDef.so.2...done. > Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 > Reading symbols from /lib/libnss_files.so.2...done. > Loaded symbols for /lib/libnss_files.so.2 > Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ > ximcp.so.2...done. > Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2 > Reading symbols from /lib/libnss_compat.so.2...done. > Loaded symbols for /lib/libnss_compat.so.2 > Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done. > Loaded symbols for /usr/X11R6/lib/libXcursor.so.1 > Reading symbols from /usr/X11R6/lib/libXrender.so.1...done. > Loaded symbols for /usr/X11R6/lib/libXrender.so.1 > #0 0x40218451 in gdk_gc_new_with_values () from /usr/lib/ > libgdk-1.2.so.0 > From henning@meier-geinitz.de Tue Jun 29 18:15:33 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 29 Jun 2004 19:15:33 +0200 Subject: [sane-devel] different scan outputs for different Linux distributions In-Reply-To: <20040629015429.77026.qmail@web41015.mail.yahoo.com> References: <20040629015429.77026.qmail@web41015.mail.yahoo.com> Message-ID: <20040629171533.GB16361@meier-geinitz.de> Hi, On Mon, Jun 28, 2004 at 06:54:29PM -0700, Peter Mark Guevarra wrote: > Sorry for this late response..I have tested scanimage with Red Hat 8 and Red Hat 9. > The output in Red Hat 9 is darker compared with that of Red Hat 8 but exactly the same settings were used.. Even if you use scanimage instead of xsane? scanimage doesn't do any automatic color correction. > You have said in your previous reply that xsane should not > modify gamma settings automatically..I`m quite confused with the > use of the options..How may I be able to do this? In Preferences-Setup-Enhancement, disable "autoenhance gamma" and "Autocorrect colors". Bye, Henning From eric.tanguy@physique.univ-nantes.fr Tue Jun 29 21:45:48 2004 From: eric.tanguy@physique.univ-nantes.fr (Eric Tanguy) Date: Tue, 29 Jun 2004 22:45:48 +0200 Subject: [sane-devel] Epson Perfection 1670 and high resolution Message-ID: <1088541948.4195.5.camel@localhost.localdomain> --=-Xiaxg9k3fvPLAHu4fHrf Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I use this scanner on fedora core 2 with sane-backends-1.0.13-7 and xsane-0.92-10. All works fine except when i try to use resolution greater than 600 (900 or 1200). In these cases, the result is malformed and the colours are wrong.=20 What's the problem and how to solve it ? Thanxes. Eric --=-Xiaxg9k3fvPLAHu4fHrf Content-Type: application/pgp-signature; name=signature.asc Content-Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e=2E?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBA4dT88EEyOKS4No8RAv7aAJ9fPtwjR/QeKaytHZLLtQVVsawBbwCfUrtF 7yo6E1ZQ0JM8LaTrGTCCe5A= =TMEb -----END PGP SIGNATURE----- --=-Xiaxg9k3fvPLAHu4fHrf-- From Oliver.Schwartz@gmx.de Tue Jun 29 22:31:44 2004 From: Oliver.Schwartz@gmx.de (Oliver Schwartz) Date: Tue, 29 Jun 2004 23:31:44 +0200 Subject: [sane-devel] Epson Perfection 1670 and high resolution In-Reply-To: <1088541948.4195.5.camel@localhost.localdomain> References: <1088541948.4195.5.camel@localhost.localdomain> Message-ID: <200406292331.50924.Oliver.Schwartz@gmx.de> =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 29 June 2004 22.45, Eric Tanguy wrote: > I use this scanner on fedora core 2 with sane-backends-1.0.13-7 and > xsane-0.92-10. All works fine except when i try to use resolution > greater than 600 (900 or 1200). In these cases, the result is > malformed and the colours are wrong. > What's the problem and how to solve it ? These resolutions are broken on the 1670. You need to upgrade to=20 sane-backends-1.0.14, it offers 800 dpi and 1600 dpi instead which=20 are supposed to work fine. /Oliver =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQFA4d/B/V6sbrmfIuMRAlk4AJsFmWvSAP69ZIcNxsnAu+KcUx82pwCffrMp b5wo5jFY64bZmBR7K7WTtHw=3D =3Da+nr =2D----END PGP SIGNATURE----- From moseley@hank.org Tue Jun 29 22:45:51 2004 From: moseley@hank.org (Bill Moseley) Date: Tue, 29 Jun 2004 14:45:51 -0700 Subject: [sane-devel] VIA chipset and HP4100C USB scanner Message-ID: <20040629214551.GB19339@hank.org> I've got a MSI KT266-Pro2 motherboard with a VIA chipset. I'm wondering if my hardware is the problem or if there's other things to check. I'm able to sync a USB Palm device with Jpilot without any problems, but my scanner generates errors. I have another machine (an older Toshiba laptop) which first reported errors (way below), but I'm now able to scan with the HP 4100C scanner. One difference is that on my desktop it seems that hotplug is loading videodev module, but that doesn't happen on my laptop. I'm not sure why. So basically, my qustion is if my hardware is just broken and will never work, or if there's something else I can try to resolve scanning problems. I have hope since Jpilot usb sync works. Here's some details: Both my Desktop (the KT266-Pro2 machine) and my laptop are running Debian Sid. The Desktop has 2.6.6 and the laptop 2.6.5. Otherwise, same software (below for sane and libusb versions). When I plug in my scanner into the KT266-PRO2 I see: Jun 28 21:30:25 bumby kernel: usb 1-2: new full speed USB device using address 2 Then I run sane-find-scanner and it reports: found USB scanner (vendor=0x03f0, product=0x0101) at libusb:001:002 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. and in syslog I see: Jun 28 21:30:41 bumby kernel: usb 1-2: control timeout on ep0in Jun 28 21:30:41 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 28 21:30:42 bumby kernel: usb 1-2: control timeout on ep0in Jun 28 21:30:42 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Sometimes this works: moseley@bumby:~$ scanimage -L device `hp:libusb:001:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner and entries in syslog from scanimage: Jun 28 21:34:11 bumby kernel: Linux video capture interface: v1.00 Jun 28 21:34:18 bumby kernel: usb 1-2: control timeout on ep0out Not sure why Linux video capture was loaded. I don't have any video capture cards. lsmod shows "videodev". Is hotplug confused about what module should be loaded? Sometimes syslog reports this again: Jun 28 21:37:34 bumby kernel: usb 1-2: control timeout on ep0out But sometimes scanimage -L reports that a scanner can't be found, and sometimes scanimage -L hangs with the process in "D" status which can't be kill -9'ed (requires a reboot, so it seems). I've also had scanimage -L do this: moseley@bumby:~$ scanimage -L Segmentation fault Finally: moseley@bumby:~$ scanimage >out.png scanimage: no SANE devices found or sometimes: meley@bumby:~$ scanimage >out.png scanimage: sane_start: Error during device I/O And that's where I'm stuck. Any suggestions? Here's more details on my setup. Probably more info than needed, but... Debian Sid with 2.6.6. MSI K7T266 main board. moseley@bumby:~$ dpkg -l | egrep '(sane|libusb|hotplug)' ii hotplug 0.0.20040329-8 Linux Hotplug Scripts ii libsane 1.0.14-2 API library for scanners ii libusb-0.1-4 0.1.8-11 Userspace USB programming library ii sane 1.0.12-2 scanner graphical frontends ii sane-utils 1.0.14-2 API library for scanners -- utilities ii xsane 0.93-1 GTK+-based X11 frontend for SANE (Scanner Ac ii xsane-common 0.93-1 GTK+-based X11 frontend for SANE (Scanner Ac Here's one of my usb entries from lspci -v (says USB2.0 but I think my USB is 1.1, according to the MSI motherboard manual). 0000:00:11.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 1b) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 64, IRQ 5 I/O ports at d400 [size=32] Capabilities: [80] Power Management version 2 moseley@bumby:~$ lsmod Module Size Used by videodev 9408 0 lp 10564 0 uhci_hcd 30672 0 w83627hf 28612 0 i2c_sensor 2944 1 w83627hf i2c_isa 2048 0 i2c_viapro 7052 0 i2c_core 23044 4 w83627hf,i2c_sensor,i2c_isa,i2c_viapro moseley@bumby:~$ fgrep USB /boot/config-2.6.6-xfs-athlon | grep -v ^# CONFIG_USB=y CONFIG_USB_DEVICEFS=y CONFIG_USB_UHCI_HCD=m CONFIG_USB_AUDIO=m CONFIG_USB_PRINTER=m CONFIG_USB_STORAGE=m CONFIG_USB_HID=m CONFIG_USB_HIDINPUT=y CONFIG_USB_HIDDEV=y CONFIG_USB_KBD=m CONFIG_USB_MOUSE=m CONFIG_USB_SERIAL=m CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m CONFIG_USB_SERIAL_KEYSPAN_PDA=m CONFIG_USB_SERIAL_KEYSPAN=m CONFIG_USB_SERIAL_KLSI=m CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_SERIAL_PL2303=m CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_OMNINET=m CONFIG_USB_EZUSB=y CONFIG_USB_RIO500=m I'm able to scan on my laptop, also runnning Debian Sid and same software. But, once in a while I do see similar problems -- so I wonder if it's a scanner issue. Jun 29 09:29:22 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r Jun 29 09:29:23 localhost kernel: usb 1-1: control timeout on ep0in Jun 29 09:29:23 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r Jun 29 09:29:44 localhost kernel: usb 1-1: control timeout on ep0out Jun 29 09:30:09 localhost kernel: usb 1-1: control timeout on ep0out Jun 29 09:30:41 localhost kernel: usb 1-1: bulk timeout on ep1in Jun 29 09:30:41 localhost kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x81 len 4096 ret -110 Jun 29 09:30:46 localhost kernel: usb 1-1: control timeout on ep0out Jun 29 09:31:16 localhost kernel: usb 1-1: bulk timeout on ep2out Jun 29 09:31:16 localhost kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x2 len 2 ret -110 -- Bill Moseley moseley@hank.org From anoah@pfeiffer.edu Wed Jun 30 00:34:08 2004 From: anoah@pfeiffer.edu (m. allan noah) Date: Tue, 29 Jun 2004 19:34:08 -0400 (EDT) Subject: [sane-devel] VIA chipset and HP4100C USB scanner In-Reply-To: <20040629214551.GB19339@hank.org> References: <20040629214551.GB19339@hank.org> Message-ID: when you run scanimage with no -d argument, sane will load all the backends that are listed in the dll.conf file, in an attempt to find your scanner. you can look for this file in /etc/sane.d or similar, and # out all the options other than the backend you are using. this should fix the video issues. as to the timeouts, that could have any number of causes, but seems really common with 2.6.x can you switch back to a 2.4 kernel just to test? allan On Tue, 29 Jun 2004, Bill Moseley wrote: > > I've got a MSI KT266-Pro2 motherboard with a VIA chipset. I'm wondering if > my hardware is the problem or if there's other things to check. I'm > able to sync a USB Palm device with Jpilot without any problems, but > my scanner generates errors. > > I have another machine (an older Toshiba laptop) which first reported > errors (way below), but I'm now able to scan with the HP 4100C scanner. > > One difference is that on my desktop it seems that hotplug is loading > videodev module, but that doesn't happen on my laptop. I'm not sure > why. > > So basically, my qustion is if my hardware is just broken and will never > work, or if there's something else I can try to resolve scanning > problems. I have hope since Jpilot usb sync works. > > Here's some details: > > Both my Desktop (the KT266-Pro2 machine) and my laptop are running > Debian Sid. The Desktop has 2.6.6 and the laptop 2.6.5. Otherwise, > same software (below for sane and libusb versions). > > > When I plug in my scanner into the KT266-PRO2 I see: > > Jun 28 21:30:25 bumby kernel: usb 1-2: new full speed USB device using address 2 > > > Then I run sane-find-scanner and it reports: > > found USB scanner (vendor=0x03f0, product=0x0101) at libusb:001:002 > # Your USB scanner was (probably) detected. It may or may not be supported by > # SANE. Try scanimage -L and read the backend's manpage. > > > and in syslog I see: > > Jun 28 21:30:41 bumby kernel: usb 1-2: control timeout on ep0in > Jun 28 21:30:41 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 > Jun 28 21:30:42 bumby kernel: usb 1-2: control timeout on ep0in > Jun 28 21:30:42 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 > > Sometimes this works: > > moseley@bumby:~$ scanimage -L > device `hp:libusb:001:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner > > and entries in syslog from scanimage: > > Jun 28 21:34:11 bumby kernel: Linux video capture interface: v1.00 > Jun 28 21:34:18 bumby kernel: usb 1-2: control timeout on ep0out > > Not sure why Linux video capture was loaded. I don't have any video > capture cards. lsmod shows "videodev". Is hotplug confused about what > module should be loaded? > > Sometimes syslog reports this again: > > Jun 28 21:37:34 bumby kernel: usb 1-2: control timeout on ep0out > > But sometimes scanimage -L reports that a scanner can't be found, and > sometimes scanimage -L hangs with the process in "D" status which can't > be kill -9'ed (requires a reboot, so it seems). I've also had scanimage > -L do this: > > moseley@bumby:~$ scanimage -L > Segmentation fault > > Finally: > > moseley@bumby:~$ scanimage >out.png > scanimage: no SANE devices found > > or sometimes: > > meley@bumby:~$ scanimage >out.png > scanimage: sane_start: Error during device I/O > > And that's where I'm stuck. Any suggestions? > > Here's more details on my setup. Probably more info than needed, but... > > Debian Sid with 2.6.6. MSI K7T266 main board. > > moseley@bumby:~$ dpkg -l | egrep '(sane|libusb|hotplug)' > ii hotplug 0.0.20040329-8 Linux Hotplug Scripts > ii libsane 1.0.14-2 API library for scanners > ii libusb-0.1-4 0.1.8-11 Userspace USB programming library > ii sane 1.0.12-2 scanner graphical frontends > ii sane-utils 1.0.14-2 API library for scanners -- utilities > ii xsane 0.93-1 GTK+-based X11 frontend for SANE (Scanner Ac > ii xsane-common 0.93-1 GTK+-based X11 frontend for SANE (Scanner Ac > > > Here's one of my usb entries from lspci -v (says USB2.0 but I think my > USB is 1.1, according to the MSI motherboard manual). > > 0000:00:11.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 1b) (prog-if 00 [UHCI]) > Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller > Flags: bus master, medium devsel, latency 64, IRQ 5 > I/O ports at d400 [size=32] > Capabilities: [80] Power Management version 2 > > > > > moseley@bumby:~$ lsmod > Module Size Used by > videodev 9408 0 > lp 10564 0 > uhci_hcd 30672 0 > w83627hf 28612 0 > i2c_sensor 2944 1 w83627hf > i2c_isa 2048 0 > i2c_viapro 7052 0 > i2c_core 23044 4 w83627hf,i2c_sensor,i2c_isa,i2c_viapro > > moseley@bumby:~$ fgrep USB /boot/config-2.6.6-xfs-athlon | grep -v ^# > CONFIG_USB=y > CONFIG_USB_DEVICEFS=y > CONFIG_USB_UHCI_HCD=m > CONFIG_USB_AUDIO=m > CONFIG_USB_PRINTER=m > CONFIG_USB_STORAGE=m > CONFIG_USB_HID=m > CONFIG_USB_HIDINPUT=y > CONFIG_USB_HIDDEV=y > CONFIG_USB_KBD=m > CONFIG_USB_MOUSE=m > CONFIG_USB_SERIAL=m > CONFIG_USB_SERIAL_GENERIC=y > CONFIG_USB_SERIAL_BELKIN=m > CONFIG_USB_SERIAL_WHITEHEAT=m > CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m > CONFIG_USB_SERIAL_EMPEG=m > CONFIG_USB_SERIAL_FTDI_SIO=m > CONFIG_USB_SERIAL_VISOR=m > CONFIG_USB_SERIAL_IPAQ=m > CONFIG_USB_SERIAL_IR=m > CONFIG_USB_SERIAL_EDGEPORT=m > CONFIG_USB_SERIAL_KEYSPAN_PDA=m > CONFIG_USB_SERIAL_KEYSPAN=m > CONFIG_USB_SERIAL_KLSI=m > CONFIG_USB_SERIAL_MCT_U232=m > CONFIG_USB_SERIAL_PL2303=m > CONFIG_USB_SERIAL_CYBERJACK=m > CONFIG_USB_SERIAL_XIRCOM=m > CONFIG_USB_SERIAL_OMNINET=m > CONFIG_USB_EZUSB=y > CONFIG_USB_RIO500=m > > I'm able to scan on my laptop, also runnning Debian Sid and same software. > But, once in a while I do see similar problems -- so I wonder if it's a > scanner issue. > > Jun 29 09:29:22 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r > Jun 29 09:29:23 localhost kernel: usb 1-1: control timeout on ep0in > Jun 29 09:29:23 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r > Jun 29 09:29:44 localhost kernel: usb 1-1: control timeout on ep0out > Jun 29 09:30:09 localhost kernel: usb 1-1: control timeout on ep0out > Jun 29 09:30:41 localhost kernel: usb 1-1: bulk timeout on ep1in > Jun 29 09:30:41 localhost kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x81 len 4096 ret -110 > Jun 29 09:30:46 localhost kernel: usb 1-1: control timeout on ep0out > Jun 29 09:31:16 localhost kernel: usb 1-1: bulk timeout on ep2out > Jun 29 09:31:16 localhost kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x2 len 2 ret -110 > > > > -- "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 avalev70@yahoo.com Wed Jun 30 09:37:51 2004 From: avalev70@yahoo.com (Alexandre Averyanov) Date: Wed, 30 Jun 2004 01:37:51 -0700 (PDT) Subject: [sane-devel] Epson Perfection 1670 and high resolution Message-ID: <20040630083751.52744.qmail@web53401.mail.yahoo.com> On Tuesday 29 June 2004 22.45, Eric Tanguy wrote: > I use this scanner on fedora core 2 with sane-backends-1.0.13-7 and > xsane-0.92-10. All works fine except when i try to use resolution > greater than 600 (900 or 1200). In these cases, the result is > malformed and the colours are wrong. > What's the problem and how to solve it ? These resolutions are broken on the 1670. You need to upgrade to=20 sane-backends-1.0.14, it offers 800 dpi and 1600 dpi instead which=20 are supposed to work fine. /Oliver I have the same problem but already with SANE 1.0.14: gray images obtained from scanner using 1600 dpi (only!) have strange vertical stripes. As for 800 dpi it's ok. __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail From picos132004@yahoo.co.uk Wed Jun 30 09:48:07 2004 From: picos132004@yahoo.co.uk (=?iso-8859-1?q?Ioan-Cosmin=20Pop?=) Date: Wed, 30 Jun 2004 09:48:07 +0100 (BST) Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <20040629143225.95772.qmail@web52207.mail.yahoo.com> Message-ID: <20040630084807.99047.qmail@web25103.mail.ukl.yahoo.com> Yes, I do have the sources of the windows driver for the scanner Mustek BearPaw 4800TA ProII. I contacted Mustek and they gave them to me. I had to sign a NDA, so I can't make them public. I can't even show portions of it... :( I want to write a backend for sane for this scanner. It's not a port to a specific OS (sane can be installed on a large number of OSs), but I am doing the development under linux. Cosmin --- j d wrote: > Hi > > I've gone through this mail, i am not clear about > what both of u talking but i guess, it seems one of > you is having the windows driver source code and > trying to port it to an another OS, may i know to > which OS you are trying to port it? > > JD > > Ioan-Cosmin Pop wrote: > Hi Ronald! > > Thank you for answering! > > --- Ronald Humphries wrote: > Hello > Cosmin. > > > > I´m still here and reading this. Is the windows > > source the complete > > driver or a part of it? > It's the complete driver. Anything needed to acces > the > scanner is there. > > > > Anyway, if you need help, I will do my best. So > far > > for me everything is > > clear, as Henning explained. > Yes, I need help, somebody to talk to. I thought I > can > do it all alone, but I can't. I would really like > you > to have also the windows sources, so we have a > common > ground. What do you think? > > > > Normally I have some time in the evening for > > programming, not much, > > because I´m alone with my 4 year old kid. > Send him all the best from me :) > > -- > > Ronald Humphries > > > > > Cosmin > > > > > > > ___________________________________________________________ALL-NEW > Yahoo! Messenger - sooooo many all-new ways to > express yourself http://uk.messenger.yahoo.com > > -- > sane-devel mailing list: > sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe > your_password" > to sane-devel-request@lists.alioth.debian.org > > > --------------------------------- > Do you Yahoo!? > New and Improved Yahoo! Mail - Send 10MB messages! ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com From my_techinfo_c@yahoo.com Wed Jun 30 10:03:59 2004 From: my_techinfo_c@yahoo.com (j d) Date: Wed, 30 Jun 2004 02:03:59 -0700 (PDT) Subject: [sane-devel] On what basis the device speciific structure will be defined?? Message-ID: <20040630090359.4969.qmail@web52210.mail.yahoo.com> Hi Henning, How are you? I have gone through the sample scanner drvier written by you, now my question for you is, on what basis you have been defined the "Structure to hold all of our device specific stuff", if I need to define a same kind of structure for an another scanner, what are the things I need to take into consideration or can i blindly follow the same structure, what you have been defined? or can I use the one which is defined in usb-skelton.c? Hope to see an early and positive reply from you, Thank you, Regards, JD __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail From eelke_klein@yahoo.com Wed Jun 30 17:38:24 2004 From: eelke_klein@yahoo.com (Eelke Klein) Date: Wed, 30 Jun 2004 09:38:24 -0700 (PDT) Subject: [sane-devel] Epson Perfection 660 Message-ID: <20040630163824.11893.qmail@web50908.mail.yahoo.com> Hello, I'm trying to get my epson perfection 660 scanner to work. I have had it working on SuSE 8.2 but I have switched to gentoo and can't get it to work anymore. sane-find-scanner can find it but scanimage -L doesn't. I have the permissions in /proc/bus/usb automatically set by a hotplug script and have checked that the rights are actually set. I also tried it as root so the rights shouldn't be a problem anyway. I have copied the firmware of my windows drivers and configured the location of it in the scapscan.conf. I have also checked that the id's of my scanner actually matched the id's in the snapscan.conf. snapscan is also enabled in the dll.conf. Here some version: Kernel 2.6.7 sane-backends 1.0.14-r3 libusb 0.1.7-r1 Eelke __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail From rohum@gmx.de Tue Jun 29 20:39:17 2004 From: rohum@gmx.de (Ronald Humphries) Date: Tue, 29 Jun 2004 21:39:17 +0200 Subject: [sane-devel] check-usb-chip request for help Message-ID: <1088537957.24804.10.camel@linux1.rohu.de> Hello Cosmin, >It's the complete driver. Anything needed to acces the >scanner is there. That´s good, that will make it not so difficult. So normally, we will find all parts what we will need in the sources. Do you got also some documentation from Mustek? >Yes, I need help, somebody to talk to. I thought I can >do it all alone, but I can't. I would really like you >ground. What do you think? Yes, I will need all informations. Then we will talk about the same things. Do you think it will be possible to get the same as you have? Can you ask them? >> Normally I have some time in the evening for >> programming, not much, >> because I´m alone with my 4 year old kid. >Send him all the best from me :) Many thanks. Do you have a step list for what has to be done, to get this into sane working? But I think first of all, we must get the check-usb-chip program working correctly for the scanner. Ronald From henning@meier-geinitz.de Wed Jun 30 18:48:58 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 30 Jun 2004 19:48:58 +0200 Subject: [sane-devel] Epson Perfection 660 In-Reply-To: <20040630163824.11893.qmail@web50908.mail.yahoo.com> References: <20040630163824.11893.qmail@web50908.mail.yahoo.com> Message-ID: <20040630174858.GA11478@meier-geinitz.de> Hi, On Wed, Jun 30, 2004 at 09:38:24AM -0700, Eelke Klein wrote: > I'm trying to get my epson perfection 660 scanner to work. I > have had it working on SuSE 8.2 but I have switched to gentoo > and can't get it to work anymore. > > sane-find-scanner can find it but scanimage -L doesn't. I have > the permissions in /proc/bus/usb automatically set by a hotplug > script and have checked that the rights are actually set. I also > tried it as root so the rights shouldn't be a problem anyway. Try enabling debug messages: SANE_DEBUG_SNAPSCAN=255 scanimage -L If you don't get any output, the snapscan backend isn't loaded for some reason. Bye, Henning From henning@meier-geinitz.de Wed Jun 30 18:55:42 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 30 Jun 2004 19:55:42 +0200 Subject: [sane-devel] VIA chipset and HP4100C USB scanner In-Reply-To: <20040629214551.GB19339@hank.org> References: <20040629214551.GB19339@hank.org> Message-ID: <20040630175542.GB11478@meier-geinitz.de> Hi, On Tue, Jun 29, 2004 at 02:45:51PM -0700, Bill Moseley wrote: > I've got a MSI KT266-Pro2 motherboard with a VIA chipset. I'm wondering if > my hardware is the problem or if there's other things to check. I'm > able to sync a USB Palm device with Jpilot without any problems, but > my scanner generates errors. Maybe it's hardware but I rather think it's a kernel problem. There have been many reports about similar trouble with 2.6 kernels and VIA hardware. > Then I run sane-find-scanner and it reports: > > found USB scanner (vendor=0x03f0, product=0x0101) at libusb:001:002 > # Your USB scanner was (probably) detected. It may or may not be supported by > # SANE. Try scanimage -L and read the backend's manpage. > > > and in syslog I see: > > Jun 28 21:30:41 bumby kernel: usb 1-2: control timeout on ep0in > Jun 28 21:30:41 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 > Jun 28 21:30:42 bumby kernel: usb 1-2: control timeout on ep0in > Jun 28 21:30:42 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 sane-find-scanner just looks for USB devices. It doesn't send any device-specific commands (at least in this case). So it's most probably not a SANE problem. > Sometimes this works: > > moseley@bumby:~$ scanimage -L > device `hp:libusb:001:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner > > and entries in syslog from scanimage: > > Jun 28 21:34:11 bumby kernel: Linux video capture interface: v1.00 > Jun 28 21:34:18 bumby kernel: usb 1-2: control timeout on ep0out > > Not sure why Linux video capture was loaded. I don't have any video > capture cards. lsmod shows "videodev". Is hotplug confused about what > module should be loaded? SANE can also "scan" from video cards that are supported by video4linux. > Jun 28 21:37:34 bumby kernel: usb 1-2: control timeout on ep0out > > But sometimes scanimage -L reports that a scanner can't be found, and > sometimes scanimage -L hangs with the process in "D" status which can't > be kill -9'ed (requires a reboot, so it seems). I've also had scanimage > -L do this: > > moseley@bumby:~$ scanimage -L > Segmentation fault Bad. I haven't seen reports about such behaviour until now. > And that's where I'm stuck. Any suggestions? Ask the Linux kernel guys. As a workaround, use kernel 2.4.* > I'm able to scan on my laptop, also runnning Debian Sid and same software. > But, once in a while I do see similar problems -- so I wonder if it's a > scanner issue. > > Jun 29 09:29:22 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r > Jun 29 09:29:23 localhost kernel: usb 1-1: control timeout on ep0in Control timeouts mean that something went wrong with the communication of the host and the scanner. The reason can be a wrong command, but as these problems only occur on 2.6 it looks like a kernel issue for me. Unfortunately nobody has yet found out the real cause. Bye, Henning From henning@meier-geinitz.de Wed Jun 30 18:58:56 2004 From: henning@meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 30 Jun 2004 19:58:56 +0200 Subject: [sane-devel] On what basis the device speciific structure will be defined?? In-Reply-To: <20040630090359.4969.qmail@web52210.mail.yahoo.com> References: <20040630090359.4969.qmail@web52210.mail.yahoo.com> Message-ID: <20040630175856.GC11478@meier-geinitz.de> Hi, On Wed, Jun 30, 2004 at 02:03:59AM -0700, j d wrote: > How are you? Fine. But there are other people on this list :-) > I have gone through the sample scanner drvier written by you, Could you explain which sample driver you mean? A specific SANE backend or the Linux kernel scanner driver? > now my question for you > is, on what basis you have been defined the "Structure > to hold all of our device specific stuff", if I need > to define a same kind of structure for an another > scanner, what are the things I need to take into > consideration or can i blindly follow the same > structure, what you have been defined? > or can I use > the one which is defined in usb-skelton.c? Hope to see > an early and positive reply from you, Thank you, usb-skeleton.c is part of the kernel. So this mail is about the kernel scanner driver? Can you explain what you intend to achieve? Bye, Henning From Oliver.Schwartz@gmx.de Wed Jun 30 21:31:49 2004 From: Oliver.Schwartz@gmx.de (Oliver Schwartz) Date: Wed, 30 Jun 2004 22:31:49 +0200 Subject: [sane-devel] Epson Perfection 1670 and high resolution In-Reply-To: <20040630083751.52744.qmail@web53401.mail.yahoo.com> References: <20040630083751.52744.qmail@web53401.mail.yahoo.com> Message-ID: <200406302232.02293.Oliver.Schwartz@gmx.de> =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > I have the same problem but already with SANE 1.0.14: > gray images obtained from scanner using 1600 dpi > (only!) have strange vertical stripes. As for 800 dpi > it's ok. That's a different bug then (which I haven't heard of before). It only=20 affects gray images? (i.e. 1600 dpi in color work fine?) /Oliver =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQFA4yM8/V6sbrmfIuMRAiCuAJ9SV0zK+l6HP5I0mh7ur64slPWSAgCfbMPN BJpYOgKmPPDH2DVqEXMupR8=3D =3D1ktK =2D----END PGP SIGNATURE----- From ukd at xenon.pc.Uni-Koeln.DE Tue Jun 1 08:15:54 2004 From: ukd at xenon.pc.Uni-Koeln.DE (Ulrich Deiters) Date: Tue, 1 Jun 2004 09:15:54 +0200 (METDST) Subject: [sane-devel] Canon FS4000 support Message-ID: <200406010715.JAA11254@xenon.pc.Uni-Koeln.DE> I once had an opportunity to look at an SCSI protocol of a FS4000. The protocol differs significantly from those of the SCSI flatbed scanners and the older film scanners. Moreover, there appear several SCSI commands which my handbook lists as "proprietary/undocumented". Reverse engineering will therefore require much experimental work. And who knows - perhaps Canon built some unconventional commands into the scanner ("eject light bulb", "burn the slide") to discourage people like us? :-) Regards, Ulrich Deiters From gilles at ffii.org Tue Jun 1 12:14:42 2004 From: gilles at ffii.org (gilles at ffii.org) Date: Tue, 1 Jun 2004 13:14:42 +0200 Subject: [sane-devel] HP5370C still not working Message-ID: <20040601111441.GA8138@ffii.org> Hello. In January, I reported that the HP5370C, supported by the "avision" back-end, was not behaving correctly (producing an image skewed by a 45 degree angle). I retried yesterday, and to my deep disappointment, the scanner doesn't even go that far anymore: trying scanimage -d avision:libusb:002:007 > image.pnm the scanner tray moves a little (but in the wrong direction), and after some 3 seconds, the light starts flashing. Best regards, Gilles P.S. Rene Rebe answered my previous post by offering to test newer, but I must have overlooked his mail at the time; sorry for that. Anyway, I've upgraded since then: Debian GNU/Linux 2.6.5 scanimage (sane-backends) 1.0.14; backend version 1.0.14 libusb-0.1-4 udev O.024 From henning at meier-geinitz.de Tue Jun 1 14:58:18 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 1 Jun 2004 15:58:18 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601111441.GA8138@ffii.org> References: <20040601111441.GA8138@ffii.org> Message-ID: <20040601135818.GC12076@meier-geinitz.de> Hi, On Tue, Jun 01, 2004 at 01:14:42PM +0200, gilles at ffii.org wrote: > I retried yesterday, and to my deep disappointment, the scanner > doesn't even go that far anymore: trying > > scanimage -d avision:libusb:002:007 > image.pnm > > the scanner tray moves a little (but in the wrong direction), > and after some 3 seconds, the light starts flashing. > Debian GNU/Linux 2.6.5 There have been reports about USB trouble with Linux 2.6.5 and 2.6.6. I don't know if that's valid for all USB scanners. As far as I can see the reports are mostly about Epson scanners. Nevertheless, have a look at syslog and check for bulk timeouts/errors. I'm using Linux 2.6.7-rc2 and don't see any USB errors but I'm using Mustek and Plustek scanners only and haven't tested 2.6.5 or 2.6.6. Bye, Henning From cward at go-integral.com Tue Jun 1 19:05:01 2004 From: cward at go-integral.com (Chris Ward) Date: Tue, 1 Jun 2004 13:05:01 -0500 Subject: [sane-devel] JSane Message-ID: <439FB88065E2FF4DB75E6DC5E19C2B2A087FBD@ibsmmex001.go-integral.net> Rainer, If there is any type of java scanning API, let Andi and I know. We aren't aware of any. I have been trying to use the existing japi classes for some time now, and they are kind of broken. Andi's classes look interresting, and I would like to try them soon (if I can ever get a saned damon running). Chris Ward >Hello Andi, > >isn't there a standard scanning API for Java? There could be >immplementations for twain AND for sane. > >Just my 2cents, >Rainer > From rene at rocklinux-consulting.de Tue Jun 1 19:41:44 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Tue, 01 Jun 2004 20:41:44 +0200 (CEST) Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601111441.GA8138@ffii.org> References: <20040601111441.GA8138@ffii.org> Message-ID: <20040601.204144.291475760.rene@rocklinux-consulting.de> Hi, On: Tue, 1 Jun 2004 13:14:42 +0200, gilles at ffii.org wrote: > Hello. > > In January, I reported that the HP5370C, supported by the > "avision" back-end, was not behaving correctly (producing > an image skewed by a 45 degree angle). > > I retried yesterday, and to my deep disappointment, the scanner > doesn't even go that far anymore: trying > > scanimage -d avision:libusb:002:007 > image.pnm > > the scanner tray moves a little (but in the wrong direction), > and after some 3 seconds, the light starts flashing. Oh. I never heared of s.th. like that. If it is ok for you I schedule a review of your logs for the weekend - I have two very important other things to do first ... > Best regards, > Gilles > > P.S. Rene Rebe answered my previous post by offering to test > newer, but I must have overlooked his mail at the time; > sorry for that. > Anyway, I've upgraded since then: > > Debian GNU/Linux 2.6.5 > scanimage (sane-backends) 1.0.14; backend version 1.0.14 > libusb-0.1-4 > udev O.024 Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene at rocklinux-consulting.de Tue Jun 1 19:43:23 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Tue, 01 Jun 2004 20:43:23 +0200 (CEST) Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601135818.GC12076@meier-geinitz.de> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> Message-ID: <20040601.204323.466679361.rene@rocklinux-consulting.de> Hi, On: Tue, 1 Jun 2004 15:58:18 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Tue, Jun 01, 2004 at 01:14:42PM +0200, gilles at ffii.org wrote: > > I retried yesterday, and to my deep disappointment, the scanner > > doesn't even go that far anymore: trying > > > > scanimage -d avision:libusb:002:007 > image.pnm > > > > the scanner tray moves a little (but in the wrong direction), > > and after some 3 seconds, the light starts flashing. > > > Debian GNU/Linux 2.6.5 > > There have been reports about USB trouble with Linux 2.6.5 and 2.6.6. > I don't know if that's valid for all USB scanners. As far as I can see > the reports are mostly about Epson scanners. > Nevertheless, have a look at syslog and check for bulk timeouts/errors. > > I'm using Linux 2.6.7-rc2 and don't see any USB errors but I'm using > Mustek and Plustek scanners only and haven't tested 2.6.5 or 2.6.6. Thanks for this hints Henning. Gilles, could you check if you hit this USB errors? Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From insane at piments.com Tue Jun 1 21:41:29 2004 From: insane at piments.com (insane at piments.com) Date: Tue, 01 Jun 2004 22:41:29 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601.204323.466679361.rene@rocklinux-consulting.de> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> Message-ID: I'm not sure how much of this can be laid at the door of "USB", I think it is more specifically trouble with SANE backends. I had wasted probably weeks trying to get my cannon FB630U to work under 2.6x kernels until some helpful sole suggested I try vuescan. This worked beautifully straight out of the box and produces better results that I had got with the sane backend when it did work under 2.4 I would like to work with open source solutions but there is a limit to how much time I can reasonably spend on a broken driver (and I have already over-stepped that mark by an order of magnitude. ) Emails to the maintainer remain unanswered. Big thanks to the guy who made me aware of vuescan. Regards to all. On Tue, 01 Jun 2004 20:43:23 +0200 (CEST), Rene Rebe wrote: > Hi, > > On: Tue, 1 Jun 2004 15:58:18 +0200, > Henning Meier-Geinitz wrote: >> Hi, >> >> On Tue, Jun 01, 2004 at 01:14:42PM +0200, gilles at ffii.org wrote: >> > I retried yesterday, and to my deep disappointment, the scanner >> > doesn't even go that far anymore: trying >> > >> > scanimage -d avision:libusb:002:007 > image.pnm >> > >> > the scanner tray moves a little (but in the wrong direction), >> > and after some 3 seconds, the light starts flashing. >> >> > Debian GNU/Linux 2.6.5 >> >> There have been reports about USB trouble with Linux 2.6.5 and 2.6.6. >> I don't know if that's valid for all USB scanners. As far as I can see >> the reports are mostly about Epson scanners. >> Nevertheless, have a look at syslog and check for bulk timeouts/errors. >> >> I'm using Linux 2.6.7-rc2 and don't see any USB errors but I'm using >> Mustek and Plustek scanners only and haven't tested 2.6.5 or 2.6.6. > > Thanks for this hints Henning. Gilles, could you check if you hit this > USB errors? > > Sincerely yours, > Ren? Rebe > - ROCK Linux stable release maintainer > > -- > Ren? Rebe - Europe/Germany/Berlin > rene at rocklinux.org rene at rocklinux-consulting.de > http://www.rocklinux.org http://www.rocklinux-consulting.de > > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org > -- Using M2, Opera's e-mail client: on Gentoo Linux From henning at meier-geinitz.de Tue Jun 1 21:52:43 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 1 Jun 2004 22:52:43 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> Message-ID: <20040601205243.GD12076@meier-geinitz.de> Hi, On Tue, Jun 01, 2004 at 10:41:29PM +0200, insane at piments.com wrote: > I'm not sure how much of this can be laid at the door of "USB", I think it > is more specifically trouble with SANE backends. If several sane backends fail with two specific kernel versions and those backends worked with older kernel versions then the conclusion that it might be a kernel issue isn't far-fetched. If you have facts that there is a bug in the backends that only showed up because of kernel changes, please tell us. Just to make one point clear: There is no general problem with SANE concerning Linux 2.6. > I had wasted probably weeks trying to get my cannon FB630U to work under > 2.6x kernels until some helpful sole suggested I try vuescan. Can someone else confirm that the canon630u backend does not work on Linux 2.6? So we can either add a warning about trouble with Linux 2.6 for this scanner? > I would like to work with open source solutions but there is a limit to > how much time I can reasonably spend on a broken driver (and I have > already over-stepped that mark by an order of magnitude. ) I'm sorry for that. Could you please send a summary of the problems and possible solutions/work-arounds you have found until now? Or if you have already done that, could you point me to that posting? This way your effort isn't wasted and other people with similar problems don't need to try the same things. > Emails to the maintainer remain unanswered. Unfortunately sometimes maintainers just vanish or ignore requests because they are not interested in the project any longer. I don't like that either but writing software is just a hobby for most people so it's understandable. The last change by Nathan Rutman in SANE CVS was on 2003-12-01, so at least at that hime he was still active. Bye, Henning From gilles at ffii.org Tue Jun 1 22:56:56 2004 From: gilles at ffii.org (gilles at ffii.org) Date: Tue, 1 Jun 2004 23:56:56 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601.204323.466679361.rene@rocklinux-consulting.de> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> Message-ID: <20040601215656.GA3524@ffii.org> Hi. > > > > There have been reports about USB trouble with Linux 2.6.5 and 2.6.6. > > Thanks for this hints Henning. Gilles, could you check if you hit this > USB errors? > When the command SANE_DEBUG_AVISION=7 scanimage -d avision:libusb:001:002 -l 5mm -t 5mm -x 15mm -y 15mm was run, here is the result from "tail -f kern.log" (so, the lines corresponding to the "scanimage" itself start at "Jun 1 17:49:11"): [...] Jun 1 17:44:30 dawn kernel: usb 1-1: registering 1-1:1.0 (config #1, interface 0) Jun 1 17:44:30 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:45:09 dawn kernel: usb 1-1: control timeout on ep0in Jun 1 17:45:09 dawn kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 1 17:45:10 dawn kernel: usb 1-1: control timeout on ep0in Jun 1 17:45:10 dawn kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 1 17:45:32 dawn kernel: usb 1-1: control timeout on ep0in Jun 1 17:45:32 dawn kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 1 17:45:33 dawn kernel: usb 1-1: control timeout on ep0in Jun 1 17:45:33 dawn kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 1 17:49:11 dawn kernel: usb 1-1: usb_disable_device nuking non-ep0 URBs Jun 1 17:49:11 dawn kernel: usb 1-1: unregistering interface 1-1:1.0 Jun 1 17:49:11 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:49:11 dawn kernel: usb 1-1: registering 1-1:1.0 (config #1, interface 0) Jun 1 17:49:11 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:49:12 dawn kernel: usb 1-1: usb_disable_device nuking non-ep0 URBs Jun 1 17:49:12 dawn kernel: usb 1-1: unregistering interface 1-1:1.0 Jun 1 17:49:12 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:49:12 dawn kernel: usb 1-1: registering 1-1:1.0 (config #1, interface 0) Jun 1 17:49:12 dawn kernel: drivers/usb/core/usb.c: usb_hotplug Jun 1 17:49:50 dawn kernel: usb 1-1: bulk timeout on ep3in Jun 1 17:49:50 dawn kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x83 len 4096 ret -110 [...] The "scanimage" didn't complete (and wasn't doing anything other than make the scanner produce clicking sounds) so that I had to "kill" it. Many thanks for trying to help. Gilles From oschirr at abm.de Wed Jun 2 18:23:13 2004 From: oschirr at abm.de (Oliver Schirrmeister) Date: Wed, 2 Jun 2004 19:23:13 +0200 Subject: [sane-devel] Fi-4120c duplex color In-Reply-To: <4092663a44c4e@wp.pl> References: <4092663a44c4e@wp.pl> Message-ID: <200406021923.13293.oschirr@abm.de> Am Freitag 30 April 2004 16:44 schrieb Krzysztof Cieniuch: > Hi, > > Is it possible to scan duplex in color with this scanner ? > I've tried scanadf --rif=yes --duplex=both --resoluton=72 -d > fujitsu:/dev/sg0 > but i've ended up with one properly scaned image and one > totally black. Is this feature missing in fujitsu backend ? > In what time if ever will be this functionality available in > fujitsu backend ? > That was a bug in the fujitsu backend. I've fixed that, checkout the latest version. Oliver From faxguy at howardsilvan.com Wed Jun 2 21:32:40 2004 From: faxguy at howardsilvan.com (Lee Howard) Date: Wed, 2 Jun 2004 13:32:40 -0700 Subject: [sane-devel] Fujitsu papersize problems, sane-backends-1.0.14 Message-ID: <20040602203240.GI12815@bilbo.x101.com> Hello. I have a Fujitsu M4097Ddm and am using sane-frontends-1.0.12 and sane-backends-1.0.14. I am having trouble when using the --papersize options other than A4/Letter. If I do: scanimage --source ADF --papersize Autodetect or: scanadf --source ADF --papersize Autodetect I get: sane_start: Invalid argument If I use "--papersize Legal" then the scanning is performed, but the image files are only letter/A4 size; the image is truncated at the bottom. I haven't tried any other options, but I would guess that all --papersize options other than letter/A4 will not result as expected. Is this something that is a known bug? Is it fixed in a development version? I'd be happy to provide verbose debugging information if it will help. Thanks. Lee. From fbakan at gmx.net Wed Jun 2 21:31:30 2004 From: fbakan at gmx.net (Franz Bakan) Date: Wed, 02 Jun 2004 22:31:30 +0200 (CEST) Subject: [sane-devel] OS/2 specific patch for sane-backends/backend/dll.c In-Reply-To: <20040529152106.GA30272@meier-geinitz.de> Message-ID: On Sat, 29 May 2004 17:21:06 +0200, Henning Meier-Geinitz wrote: ... >> What do you think? Could this script be added to >> sane-backends/ >> or >> sane-backends/backend/ > >What about tools/? There is already a script called by the Makefile. >You could call it from backend/Makefile if the install target is run >on OS/2. tools/ is fine. >I'd change the license to just GPL. E.g. at the moment, nobody is >allowed to use your script (only copy, distribute and modify it) :-) Change it to what you think is best. I am not shure if a license is necessary at all for such a short script, but I'm not a lawyer and don't know if there are sane-project-specific rules for these things. Ciao Franz From martin at mkcollins.org Thu Jun 3 09:07:19 2004 From: martin at mkcollins.org (Martin Collins) Date: Thu, 3 Jun 2004 09:07:19 +0100 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <20040530043040.5034a5e2.martin@mkcollins.org> References: <20040530043040.5034a5e2.martin@mkcollins.org> Message-ID: <20040603090719.45d7eb5b.martin@mkcollins.org> Can anyone (khk, Olaf) confirm that the GT10000 with ADF is supposed to be supported by a sane backend? If not what can I do to help it to become supported? Martin From olaf at epkowa.co.jp Thu Jun 3 10:35:38 2004 From: olaf at epkowa.co.jp (Olaf Meeuwissen) Date: Thu, 03 Jun 2004 18:35:38 +0900 Subject: [sane-devel] Epson GT10000 and ADF problems References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> Message-ID: <87aczloufp.fsf@zen.epkowa.co.jp> Martin Collins writes: > Can anyone (khk, Olaf) confirm that the GT10000 with ADF is supposed to > be supported by a sane backend? > If not what can I do to help it to become supported? Sorry Martin. I meant to follow up but forgot about it. As far as "Image Scan! for Linux" is concerned: 1.2.0 added support for the GT10000 1.5.1 added ADF support so you would say it should work. Our Q&A group has tested ADF support of this scanner for iscan-1.5.1 and didn't find any problems. However, it has not been tested since, so a bug *may* have crept in in a later release. Looking at the diff I don't see anything obvious though. Not much help, I'm afraid. -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From faxguy at howardsilvan.com Thu Jun 3 15:36:13 2004 From: faxguy at howardsilvan.com (Lee Howard) Date: Thu, 3 Jun 2004 07:36:13 -0700 Subject: [sane-devel] Fujitsu papersize problems, sane-backends-1.0.14 In-Reply-To: <200406031403.57151.oschirr@abm.de>; from oschirr@abm.de on Thu, Jun 03, 2004 at 05:03:56 -0700 References: <20040602203240.GI12815@bilbo.x101.com> <200406031403.57151.oschirr@abm.de> Message-ID: <20040603143613.GS12815@bilbo.x101.com> On 2004.06.03 05:03 Oliver Schirrmeister wrote: > Am Mittwoch 02 Juni 2004 22:32 schrieb Lee Howard: > > Hello. > > > > I have a Fujitsu M4097Ddm and am using sane-frontends-1.0.12 and > > sane-backends-1.0.14. > > > > I am having trouble when using the --papersize options other than > > A4/Letter. > > > > If I do: > > > > scanimage --source ADF --papersize Autodetect > > > > or: > > > > scanadf --source ADF --papersize Autodetect > > > > I get: > > > > sane_start: Invalid argument > > Seems that autodetect doesn't work with the 4097. I've tried that > option with > the 3093 but it wasn's reliable. Oh, alright. By your comments here I assume that --papersize is used solely to indicate to the ADF the size of the paper that it is supposed to pull through, but does not indicate the size of the area that is to be scanned. Is this correct? I don't really understand the value of the --papersize option, then, since the scanner seems to deal with mixed-size and other-size paper regardless of what --papersize option I use. E.g., if I use --papersize Letter, then it seems to be quite happy about scanning Letter and Legal sized paper mixed in the ADF. > > If I use "--papersize Legal" then the scanning is performed, but the > > image files are only letter/A4 size; the image is truncated at the > > bottom. > > > > Did you set the -x and -y option? These options specify the scanning > area. > The default of x and y is 210x297 mm (A4). > papersize specifies the page you enter in the adf (centered). -l -t -x > -y is > the scanning area relative to that page. No, I did not set -l -t -x -y. I had thought (hoped) that my --papersize indication would have made those indicators superfluous. I see now that's not the case. Thanks. Lee. From oschirr at abm.de Thu Jun 3 16:53:26 2004 From: oschirr at abm.de (Oliver Schirrmeister) Date: Thu, 3 Jun 2004 17:53:26 +0200 Subject: [sane-devel] Fujitsu papersize problems, sane-backends-1.0.14 In-Reply-To: <20040603143613.GS12815@bilbo.x101.com> References: <20040602203240.GI12815@bilbo.x101.com> <200406031403.57151.oschirr@abm.de> <20040603143613.GS12815@bilbo.x101.com> Message-ID: <200406031753.26352.oschirr@abm.de> Am Donnerstag 03 Juni 2004 16:36 schrieb Lee Howard: > > > I am having trouble when using the --papersize options other than > > > A4/Letter. > > > > > > If I do: > > > > > > scanimage --source ADF --papersize Autodetect > > > > > > or: > > > > > > scanadf --source ADF --papersize Autodetect > > > > > > I get: > > > > > > sane_start: Invalid argument > > > > Seems that autodetect doesn't work with the 4097. I've tried that > > option with > > the 3093 but it wasn's reliable. > > Oh, alright. > > By your comments here I assume that --papersize is used solely to > indicate to the ADF the size of the paper that it is supposed to pull > through, but does not indicate the size of the area that is to be > scanned. Is this correct? Correct. > I don't really understand the value of the --papersize option, then, > since the scanner seems to deal with mixed-size and other-size paper > regardless of what --papersize option I use. E.g., if I use > --papersize Letter, then it seems to be quite happy about scanning > Letter and Legal sized paper mixed in the ADF. Your scanner has a DIN A3 ADF and you use those plastic bars (how are they called?) to center your letter sized paper. The origin of the scanning area (-x -y -l -t) is 0/0 in the picture below if you use --papersize Letter, not the left side of the A3 ADF. | <----------- DIN A3 ---------->| | | 0/0 | | | | <- Letter -> | | | | | | | | | | | | If you put mixed-size paper in the adf with different paper width (e.g letter and A5) you'll more likely get a paper jam and the A5 paper will probably be skewed. The resulting image of the A5 paper will have letter size if -x and -y are set to letter size. I think this subject is better described in one of that guides of your scanner (have a look at the fujitsu home page). -- Oliver From martin at mkcollins.org Thu Jun 3 23:03:32 2004 From: martin at mkcollins.org (Martin Collins) Date: Thu, 3 Jun 2004 23:03:32 +0100 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <87aczloufp.fsf@zen.epkowa.co.jp> References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> Message-ID: <20040603230332.3dd7a5f6.martin@mkcollins.org> On Thu, 03 Jun 2004 18:35:38 +0900 Olaf Meeuwissen wrote: > As far as "Image Scan! for Linux" is concerned: > > 1.2.0 added support for the GT10000 > 1.5.1 added ADF support The Ekpowa website doesn't offer 1.5.1 for download. Is there an FTP site or something? Martin From olaf at epkowa.co.jp Fri Jun 4 00:50:38 2004 From: olaf at epkowa.co.jp (Olaf Meeuwissen) Date: Fri, 04 Jun 2004 08:50:38 +0900 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <20040603230332.3dd7a5f6.martin@mkcollins.org> (Martin Collins's message of "Thu, 3 Jun 2004 23:03:32 +0100") References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> Message-ID: <873c5c19rl.fsf@zen.epkowa.co.jp> Martin Collins writes: > On Thu, 03 Jun 2004 18:35:38 +0900 > Olaf Meeuwissen wrote: > >> As far as "Image Scan! for Linux" is concerned: >> >> 1.2.0 added support for the GT10000 >> 1.5.1 added ADF support > > The Ekpowa website doesn't offer 1.5.1 for download. Is there an FTP > site or something? Unfortunately, there is no FTP site or something. # And I much dislike company policy not to provide old versions :-( If you don't mind getting an RPM in the mail ... it's about 450kB. -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From martin at mkcollins.org Fri Jun 4 01:12:10 2004 From: martin at mkcollins.org (Martin Collins) Date: Fri, 4 Jun 2004 01:12:10 +0100 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <873c5c19rl.fsf@zen.epkowa.co.jp> References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> <873c5c19rl.fsf@zen.epkowa.co.jp> Message-ID: <20040604011210.240e6d85.martin@mkcollins.org> On Fri, 04 Jun 2004 08:50:38 +0900 Olaf Meeuwissen wrote: > If you don't mind getting an RPM in the mail ... it's about 450kB. No problem, I'd prefer the tar.gz though. Thanks Martin From olaf at epkowa.co.jp Fri Jun 4 01:35:08 2004 From: olaf at epkowa.co.jp (Olaf Meeuwissen) Date: Fri, 04 Jun 2004 09:35:08 +0900 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <20040604011210.240e6d85.martin@mkcollins.org> (Martin Collins's message of "Fri, 4 Jun 2004 01:12:10 +0100") References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> <873c5c19rl.fsf@zen.epkowa.co.jp> <20040604011210.240e6d85.martin@mkcollins.org> Message-ID: <87smdcyxc3.fsf@zen.epkowa.co.jp> Martin Collins writes: > On Fri, 04 Jun 2004 08:50:38 +0900 > Olaf Meeuwissen wrote: > >> If you don't mind getting an RPM in the mail ... it's about 450kB. > > No problem, I'd prefer the tar.gz though. Alright, I'll send the tarball for gcc-3.2 (or later) in a separate mail. -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From c0sga4a at euskalnet.net Fri Jun 4 15:48:58 2004 From: c0sga4a at euskalnet.net (JKD) Date: Fri, 4 Jun 2004 16:48:58 +0200 Subject: [sane-devel] planning to write abackend for HP scanjet 3970 Message-ID: <20040604144858.GA3006@JKDSoft.cjb.net> Hello every one, I'm new in this list. I own an HP Scanjet 3970 and I'm planning to write a backend for this scanner. I would like to know if anybody has started to analyze usb protocol of this scanner or if there is any developer who is already working on it. Sincerely, JKD From robelsner at ngfc.com Sat Jun 5 04:25:04 2004 From: robelsner at ngfc.com (Rob Elsner) Date: Fri, 04 Jun 2004 21:25:04 -0600 Subject: [sane-devel] Want to write HP 4570c Driver RFI Message-ID: <1086405903.5792.4087.camel@linux.site> Hello. I've tried to find out the current status of a driver for this scanner, but haven't seen anything on it. I would be interested in writing said driver, if anyone has any information about what needs to be done. Since I've just started trying to use it in Linux, I've gathered no developer info. There is some mention of it being compatible/similar to GL841/GL646, but sane doesn't seem to think so, at least for me. Will look into this. Rob Elsner From henning at meier-geinitz.de Sat Jun 5 10:49:07 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 11:49:07 +0200 Subject: [sane-devel] OS/2 specific patch for sane-backends/backend/dll.c References: <20040529152106.GA30272@meier-geinitz.de> Message-ID: <20040605094907.GC19373@meier-geinitz.de> Hi, On Wed, Jun 02, 2004 at 10:31:30PM +0200, Franz Bakan wrote: > On Sat, 29 May 2004 17:21:06 +0200, Henning Meier-Geinitz wrote: > >What about tools/? There is already a script called by the Makefile. > >You could call it from backend/Makefile if the install target is run > >on OS/2. > > tools/ is fine. I've added the script to the tools directory. If you want to call it automatically from backend/Makefile please send a patch for the install traget that only executes when os2 is used. > >I'd change the license to just GPL. E.g. at the moment, nobody is > >allowed to use your script (only copy, distribute and modify it) :-) > > Change it to what you think is best. I am not shure if a license is > necessary at all for such a short script, but I'm not a lawyer and > don't know if there are sane-project-specific rules for these things. Better add a license to everything to avoid discussions. I've used GPL in this case. Please check if the script still works. By the way, your website says: "Optionally you can remove support for scanners you don't need to make compiling faster and libsane.dll smaller. For this purpose you have to modify sane-backends-1.0.14/backend/Makefile.in and remove the scanners you don't need from the list which starts with: PRELOADABLE_BACKENDS = " That doesn't work anymore. Just run configure like this: BACKENDS="net mustek whatever" ./configure Or modify backend/Makefile after it was generated by configure. Also "--enable-translations" has been the default setting for some time now. Bye, Henning From henning at meier-geinitz.de Sat Jun 5 10:53:12 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 11:53:12 +0200 Subject: [sane-devel] canon lide 80 In-Reply-To: References: Message-ID: <20040605095312.GD19373@meier-geinitz.de> Hi, On Sun, May 30, 2004 at 07:56:07PM +0200, Mark Pustjens wrote: > i wanted to confirm that the canon lide 80 indeed has the GL841 chip > > output from sane-find-scanner -v -v: > > found USB scanner (vendor=0x04a9 [Canon], product=0x2214 [CanoScan], chip=GL841) at libusb:003:004 Thanks. I've added that to our lists. Bye, Henning From henning at meier-geinitz.de Sat Jun 5 11:02:40 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 12:02:40 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086025927.11981.15.camel@yoda> References: <1086025927.11981.15.camel@yoda> Message-ID: <20040605100240.GE19373@meier-geinitz.de> Hi, On Mon, May 31, 2004 at 10:52:11AM -0700, Keith Clayton wrote: > I'm at a bit of a loss as to how I can troubleshoot this further. > Unfortunately I don't have another linux box on my small network that I > can test with to determine whether the problem is with win32-xsane or > rather with saned. You have one, you just don't know :-) What happens if you scan over the local net? E.g. "scanimage -d net:localhost:plustek"? You can enable debugging on the client by using "export SANE_DEBUG_NET=255". On the server, disable saned in (x)inetd.conf, and start it manually e.g. like this for max debugging: SANE_DEBUG_PLUSTEK=255 saned -d255 This way you have to restart saned after each connection. > Any pointers for troubleshooting this further would be much appreciated! Maybe little/big endian problems? But in this case the first scan should also fail. Bye, Henning From henning at meier-geinitz.de Sat Jun 5 11:05:27 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 12:05:27 +0200 Subject: [sane-devel] planning to write abackend for HP scanjet 3970 In-Reply-To: <20040604144858.GA3006@JKDSoft.cjb.net> References: <20040604144858.GA3006@JKDSoft.cjb.net> Message-ID: <20040605100527.GF19373@meier-geinitz.de> Hi, On Fri, Jun 04, 2004 at 04:48:58PM +0200, JKD wrote: > I'm new in this list. I own an HP Scanjet 3970 and I'm planning > to write a backend for this scanner. I would like to know if anybody has > started to analyze usb protocol of this scanner or if there is any > developer who is already working on it. At least I don't remember anyone trying to write a backend. So go ahead :-) Please tell us when you have some more information, e.g. logs, chipset details, documentation. Put that info on a website so we can link to it. Thanks and good luck, Henning From henning at meier-geinitz.de Sat Jun 5 11:09:50 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 5 Jun 2004 12:09:50 +0200 Subject: [sane-devel] Want to write HP 4570c Driver RFI In-Reply-To: <1086405903.5792.4087.camel@linux.site> References: <1086405903.5792.4087.camel@linux.site> Message-ID: <20040605100950.GG19373@meier-geinitz.de> Hi, On Fri, Jun 04, 2004 at 09:25:04PM -0600, Rob Elsner wrote: > There is some mention of it being compatible/similar to GL841/GL646, but > sane doesn't seem to think so, at least for me. There is no test for the HP variant of the GL841 in sane-find-scanner yet. So as a first step you may have a look at tools/check-usb-scanner.c, copy the tests for the gl841 to e.g. gl841_hp, modify them so the scanner is detected. If the test that sends actual commands works it's most probably a GL841. See also the gl646/gl646_hp tests for an example. Please tell us about the result and send a patch when you are ready. Good luck! Bye, Henning From martin at mkcollins.org Sat Jun 5 18:01:07 2004 From: martin at mkcollins.org (Martin Collins) Date: Sat, 5 Jun 2004 18:01:07 +0100 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <87smdcyxc3.fsf@zen.epkowa.co.jp> References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> <873c5c19rl.fsf@zen.epkowa.co.jp> <20040604011210.240e6d85.martin@mkcollins.org> <87smdcyxc3.fsf@zen.epkowa.co.jp> Message-ID: <20040605180107.3dda0c3e.martin@mkcollins.org> On Fri, 04 Jun 2004 09:35:08 +0900 Olaf Meeuwissen wrote: > Alright, I'll send the tarball for gcc-3.2 (or later) in a separate > mail. Thanks for that. However it wouldn't make. Some C++ library or header mismatch. Could be my GTK is too new. In the process I discovered I had a tarball of 1.5.2 on one of my machines. That did compile cleanly but didn't work in a similar way to 1.8.1 I will try to get 1.5.1 compiled and do some testing later this week. Martin From keith at claytons.org Sat Jun 5 19:00:23 2004 From: keith at claytons.org (Keith Clayton) Date: Sat, 05 Jun 2004 11:00:23 -0700 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040605100240.GE19373@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> Message-ID: <1086458420.26103.10.camel@yoda> Ooops . . sorry Henning . . meant to send my reply to the list rather than directly to you. Ok . . reply . . take 2. Thanks for the reply Henning. Most helpful. Here's some results of testing. scanimage -d net:localhost:plustek works perfectly. Can scan as many times consecutively as I'd like. win32-xsane continues to fail on the 2nd scan. After power-cycling the scanner I ran win32-xsane first then scanimage from the local machine. Scanimage failed in this case. First pass of win32-xsane is evidently leaving the scanner in a bad state. Used the debug flags as you suggested and captured the output. Something is definitely going wrong at the end of the win32-xsane/saned scan. I've attached the gzip output of running saned as you suggested with debugging on and xinetd disabled. I X'd out any host, IP info from the top of the log files but otherwise they're exactly what the debug kicked out. I'm sure your busy . . seems like we all are! but if you could take a peek the the logs at some point it would be most appreciated. >From there, if you've got any other suggestions, let me know and I'll give it a shot. Thanks! Keith On Sat, 2004-06-05 at 12:02 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Mon, May 31, 2004 at 10:52:11AM -0700, Keith Clayton wrote: > > I'm at a bit of a loss as to how I can troubleshoot this further. > > Unfortunately I don't have another linux box on my small network that I > > can test with to determine whether the problem is with win32-xsane or > > rather with saned. > > You have one, you just don't know :-) > > What happens if you scan over the local net? E.g. > "scanimage -d net:localhost:plustek"? > > You can enable debugging on the client by using > "export SANE_DEBUG_NET=255". On the server, disable saned in > (x)inetd.conf, and start it manually e.g. like this for max debugging: > > SANE_DEBUG_PLUSTEK=255 saned -d255 > > This way you have to restart saned after each connection. > > > Any pointers for troubleshooting this further would be much appreciated! > > Maybe little/big endian problems? But in this case the first scan > should also fail. > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org -------------- next part -------------- A non-text attachment was scrubbed... Name: local_scan.txt.gz Type: application/x-gzip Size: 7049 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: win32_scan.txt.gz Type: application/x-gzip Size: 11261 bytes Desc: not available URL: From henning at meier-geinitz.de Sun Jun 6 11:07:16 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 12:07:16 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble Message-ID: <20040606100716.GH19373@meier-geinitz.de> Hi, Everyone who gets timeouts/USB errors with these two scanners and sane-backends 1.0.14 please use the following workaround: Comment out the "epson" line in dll.conf (/etc/sane.d/ or /usr/local/etc/sane.d/). The epson backend seems to try to talk to these scanners because they are Epson scanners. As they are supported by the plustek backend (not epson) the scanners don't like the epson commands and USB errors occur. See bug 300751 for details: https://alioth.debian.org/tracker/index.php?group_id=1308&atid=410366 I guess that bug didn't show up before the 1.0.14 release because the automatic detection for USB scanners in the epson backend wasn't turned on. Bye, Henning From serge at yotvata.com Sun Jun 6 14:12:29 2004 From: serge at yotvata.com (Serge) Date: Sun, 6 Jun 2004 13:12:29 +0000 Subject: [sane-devel] HP ScanJet 5370C - calibration Message-ID: <200406061312.29158.serge@yotvata.com> Hi everybody My HP scanjet 5370C scanner works. But i get vertical lines. I read somewhere here in the list that it seems to be a calibration problem. How do i calibrate the scanner? Thank you -- Serge. _______________________ Sent with KMail Powered by Gentoo Linux _______________________ From rene at rocklinux-consulting.de Sun Jun 6 12:14:24 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 13:14:24 +0200 (CEST) Subject: [sane-devel] HP ScanJet 5370C - calibration In-Reply-To: <200406061312.29158.serge@yotvata.com> References: <200406061312.29158.serge@yotvata.com> Message-ID: <20040606.131424.511742157.rene@rocklinux-consulting.de> Hi, On: Sun, 6 Jun 2004 13:12:29 +0000, Serge wrote: > Hi everybody > > My HP scanjet 5370C scanner works. But i get vertical lines. I read somewhere > here in the list that it seems to be a calibration problem. > How do i calibrate the scanner? The scanner is automatically calibrated when needed (for some scanners for each scan - for other the first time after power-on it is used). You just seem to run an old SANE/Avision backend version. Getting the last release should be enough - alternatively the current beta release code is at the homepage at: http://www.rocklinux-consulting.de/oss/avision/ Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene at rocklinux-consulting.de Sun Jun 6 15:33:42 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 6 Jun 2004 14:33:42 +0000 Subject: [sane-devel] HP ScanJet 5370C - calibration Message-ID: <200406061433.42682.rene@rocklinux-consulting.de> Thank you, Rene, for your quick answer. I do have the last sane version [not cvs], compiled from source [gentoo]. Having vertical lines... Hi, On: Sun, 6 Jun 2004 13:12:29 +0000, Serge wrote: > Hi everybody > > My HP scanjet 5370C scanner works. But i get vertical lines. I read > somewhere here in the list that it seems to be a calibration problem. > How do i calibrate the scanner? The scanner is automatically calibrated when needed (for some scanners for each scan - for other the first time after power-on it is used). You just seem to run an old SANE/Avision backend version. Getting the last release should be enough - alternatively the current beta release code is at the homepage at: http://www.rocklinux-consulting.de/oss/avision/ Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From gilles at ffii.org Sun Jun 6 14:20:40 2004 From: gilles at ffii.org (gilles at ffii.org) Date: Sun, 6 Jun 2004 15:20:40 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606100716.GH19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: <20040606132040.GA14021@ffii.org> > > Everyone who gets timeouts/USB errors with these two scanners and Is this what happens to the HP5370C too? (see my posting from June 1st "HP5370C still not working"). > sane-backends 1.0.14 please use the following workaround: > Comment out the "epson" line in dll.conf (/etc/sane.d/ or > /usr/local/etc/sane.d/). > What's the solution is my case? Thanks for your help. Gilles From khk at khk.net Sun Jun 6 14:25:29 2004 From: khk at khk.net (Karl Heinz Kremer) Date: Sun, 6 Jun 2004 09:25:29 -0400 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606100716.GH19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: I just left my comments in the bug report. The Epson backend does not have information about these scanners (this means no product ID), so they should not be recognized and therefore the backend should not try to send any data. The only way this would happen is, if somebody explicitly uses the "usb 0x4b8 0xXXX" entry in epson.conf to manually add this scanner to the list of known scanners. I don't have these scanners, so I cannot test this. I do however know that if I add an EPSON scanner that is not yet supported (this was e.g. the case with the Perfection 4850), the new scanner is not recognized, and skipped during the scanner detection. There may be something else doing on, but I don't know what yet. I need a debug log for this case to find out what's going on. Unfortunately the author of the bug report did not leave an email address, so I hope that either my comment in the bug database, or this mail reaches the author. Henning, do you know how to get in touch with Jan? Karl Heinz On Jun 6, 2004, at 6:07 AM, Henning Meier-Geinitz wrote: > Hi, > > Everyone who gets timeouts/USB errors with these two scanners and > sane-backends 1.0.14 please use the following workaround: > Comment out the "epson" line in dll.conf (/etc/sane.d/ or > /usr/local/etc/sane.d/). > > The epson backend seems to try to talk to these scanners because they > are Epson scanners. As they are supported by the plustek backend (not > epson) the scanners don't like the epson commands and USB errors occur. > > See bug 300751 for details: > https://alioth.debian.org/tracker/index.php?group_id=1308&atid=410366 > > I guess that bug didn't show up before the 1.0.14 release because the > automatic detection for USB scanners in the epson backend wasn't > turned on. > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org From henning at meier-geinitz.de Sun Jun 6 14:25:50 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 15:25:50 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606132040.GA14021@ffii.org> References: <20040606100716.GH19373@meier-geinitz.de> <20040606132040.GA14021@ffii.org> Message-ID: <20040606132550.GI19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 03:20:40PM +0200, gilles at ffii.org wrote: > > > > Everyone who gets timeouts/USB errors with these two scanners and > > Is this what happens to the HP5370C too? (see my posting from June 1st > "HP5370C still not working"). I don't think so. > > sane-backends 1.0.14 please use the following workaround: > > Comment out the "epson" line in dll.conf (/etc/sane.d/ or > > /usr/local/etc/sane.d/). > > > > What's the solution is my case? I don't know. Looks like a completely different problem. However, commenting out everything but "avision" in dll.conf may be worth a try. Bye, Henning From henning at meier-geinitz.de Sun Jun 6 14:58:01 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 15:58:01 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: <20040606135800.GJ19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 09:25:29AM -0400, Karl Heinz Kremer wrote: > The Epson backend does not have information about these scanners (this > means no product ID), You mean: no internal product id? The USB product id of these scanners are actually listed in your code. > so they should not be recognized and therefore > the backend should not try to send any data. The only way this would > happen is, if somebody explicitly uses the "usb 0x4b8 0xXXX" entry in > epson.conf to manually add this scanner to the list of known scanners. I'll try to understand what happens: "usb" is in epson.conf so sane_init() calls attach_one_usb(). By the way, the attach_string related code seems to be unused in that function. Now attach() is called. As isLibUSB is false and dev_name is empty, for every known device sanei_usb_find_devices() is called. As The 1260 and 1250 are known (see epson_usb.conf) attach_one_usb() and attach () is called again, this time with the full libusb name. There is another test if the scanner is in the list of ids and it actually is. After that, commands like reset() and get_identity_information() are sent to the scanner. These commands will crash scanners that don't speak the epson protocoll. I may have missed something in this analysis, however. So the ids of these scanners should just be removed from epson_usb.c. > I don't have these scanners, so I cannot test this. I do however know > that if I add an EPSON scanner that is not yet supported (this was e.g. > the case with the Perfection 4850), the new scanner is not recognized, > and skipped during the scanner detection. Maybe you added it to epson_usb.c but in epson.conf there was no "usb"? Or the scanner just didn't mind being sent some epson protocol commands? > There may be something else doing on, but I don't know what yet. > > I need a debug log for this case to find out what's going on. > Unfortunately > the author of the bug report did not leave an email address, so I hope > that either my comment in the bug database, or this mail reaches the > author. > > Henning, do you know how to get in touch with Jan? No. But as he has responded to my previous questions I guess he reads the bug tracker from time to time. By the way: there are some other bug/wish list reports for your backend that could use some comments (or fixes if possible): https://alioth.debian.org/tracker/index.php?group_id=1308&atid=410366 Thanks, Henning From tmwg-sane at inxservices.com Sun Jun 6 15:03:28 2004 From: tmwg-sane at inxservices.com (George Garvey) Date: Sun, 6 Jun 2004 07:03:28 -0700 Subject: [sane-devel] HP 7450C scan problem: color bar on one size of scan Message-ID: <20040606140328.GA11281@inxservices.com> I put a small sample at http://inxservices.com/scan_problem.png. The bars of colors on the left are an artifact. This was scanned with xsane on Fedora: xsane-0.92-11 and sane-backends-1.0.14-1. I replaced the avision files with the latest from Rene's SVN yesterday and rebuilt the RPMS. From tmwg-sane at inxservices.com Sun Jun 6 15:10:49 2004 From: tmwg-sane at inxservices.com (George Garvey) Date: Sun, 6 Jun 2004 07:10:49 -0700 Subject: [sane-devel] HP 7450C libusb problems Message-ID: <20040606141049.GB11281@inxservices.com> I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and 2.6.6-1.422 and this scanner. Jun 6 06:33:03 vanserver kernel: usb 1-1: bulk timeout on ep3in Jun 6 06:33:03 vanserver kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 Jun 6 06:33:33 vanserver kernel: usb 1-1: bulk timeout on ep2in Jun 6 06:33:33 vanserver kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 1 ret -110 Jun 6 06:34:03 vanserver kernel: usb 1-1: bulk timeout on ep3in Jun 6 06:34:03 vanserver kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 22 ret -110 Jun 5 16:46:21 vanserver kernel: usb 1-1: bulk timeout on ep3in Jun 5 16:46:21 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x83 len 2528 ret -110 Jun 5 16:46:49 ns named[870]: XX+/127.0.0.1/mwg.inxservices.lan/A/IN Jun 5 16:46:49 ns named[870]: XX+/192.168.1.3/3.1.168.192.in-addr.arpa/PTR/IN Jun 5 16:46:49 ns named[870]: XX+/192.168.1.3/12.1.168.192.in-addr.arpa/PTR/IN Jun 5 16:46:51 vanserver kernel: usb 1-1: bulk timeout on ep2in Jun 5 16:46:51 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x82 len 1 ret -110 Jun 5 16:46:55 vanserver kernel: usb 1-1: bulk timeout on ep1out Jun 5 16:46:55 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x1 len 10 ret -110 Jun 5 16:46:55 vanserver kernel: usb 1-1: usbfs: interface 0 claimed while 'saned' sets config #1 Jun 5 16:46:55 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x1 len 6 ret -108 Jun 5 16:46:55 vanserver kernel: usb 1-1: usbfs: interface 0 claimed while 'saned' sets config #1 Jun 5 16:46:55 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x82 len 1 ret -108 Jun 5 16:47:10 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 3 ep 0x1 len 6 ret -71 Jun 5 16:47:10 vanserver kernel: usb 1-1: USB disconnect, address 3 Jun 5 16:47:23 vanserver kernel: usb 1-1: new full speed USB device using address 4 Jun 5 23:34:54 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 10 ret -71 Jun 5 23:34:54 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -84 Jun 5 23:34:54 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -71 Jun 5 23:34:57 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 10 ret -71 Jun 5 23:34:57 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x82 len 1 ret -84 Jun 5 23:34:57 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x1 len 6 ret -71 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x83 len 4096 ret -84 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x82 len 1 ret -84 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x1 len 6 ret -71 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x1 len 10 ret -71 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x82 len 1 ret -84 Jun 5 23:06:42 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 14 ep 0x1 len 6 ret -71 Jun 5 23:06:59 vanserver kernel: usb 1-1: USB disconnect, address 14 Jun 5 23:07:10 vanserver kernel: usb 1-1: new full speed USB device using address 15 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x83 len 4096 ret -84 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x82 len 1 ret -84 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x1 len 6 ret -71 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x1 len 10 ret -71 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x82 len 1 ret -84 Jun 5 23:08:41 vanserver kernel: usbfs: USBDEVFS_BULK failed dev 15 ep 0x1 len 6 ret -71 These are with Fedora sane-backends-1.0.14-1. I replaced the avision files with the latest from Rene's SVN yesterday and rebuilt the RPMS. These messages are from after using this newly built RPM. The problem was happening before, with the standard RPM from Fedora. This is what prompted trying the beta version. From tmwg-sane at inxservices.com Sun Jun 6 15:13:09 2004 From: tmwg-sane at inxservices.com (George Garvey) Date: Sun, 6 Jun 2004 07:13:09 -0700 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606132550.GI19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> <20040606132040.GA14021@ffii.org> <20040606132550.GI19373@meier-geinitz.de> Message-ID: <20040606141309.GC11281@inxservices.com> On Sun, Jun 06, 2004 at 03:25:50PM +0200, Henning Meier-Geinitz wrote: > On Sun, Jun 06, 2004 at 03:20:40PM +0200, gilles at ffii.org wrote: > > Is this what happens to the HP5370C too? (see my posting from June 1st > > "HP5370C still not working"). > > However, commenting out everything but "avision" in dll.conf may be > worth a try. I just posted kernel messages about this. In my case, dll.conf only has net and avision. From henning at meier-geinitz.de Sun Jun 6 15:21:54 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 16:21:54 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606141049.GB11281@inxservices.com> References: <20040606141049.GB11281@inxservices.com> Message-ID: <20040606142154.GK19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 07:10:49AM -0700, George Garvey wrote: > I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and > 2.6.6-1.422 and this scanner. > > Jun 6 06:33:03 vanserver kernel: usb 1-1: bulk timeout on ep3in > Jun 6 06:33:03 vanserver kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 110 is "connection timed out". I still think this type of problem is kernel-related as it only seems to happen with 2.6.5 and 2.6.6. Please try 2.6.7-rc2. It works for me (with different scanners) but I haven't tested 2.6.5 nor 2.6.6. Bye, Henning From khk at khk.net Sun Jun 6 15:41:26 2004 From: khk at khk.net (Karl Heinz Kremer) Date: Sun, 6 Jun 2004 10:41:26 -0400 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606135800.GJ19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> <20040606135800.GJ19373@meier-geinitz.de> Message-ID: <20040606144126.GA6798@khk.net> On Sun, Jun 06, 2004 at 03:58:01PM +0200, Henning Meier-Geinitz wrote: > Hi, > > On Sun, Jun 06, 2004 at 09:25:29AM -0400, Karl Heinz Kremer wrote: > > The Epson backend does not have information about these scanners (this > > means no product ID), > > You mean: no internal product id? > The USB product id of these scanners are actually listed in your code. Guilty. This was a copy&paste error. I never intended to get these into the production code. I'll take them out right away. Thanks for doing my work :-) Karl Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From rene at rocklinux-consulting.de Sun Jun 6 15:42:53 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 16:42:53 +0200 (CEST) Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606141049.GB11281@inxservices.com> References: <20040606141049.GB11281@inxservices.com> Message-ID: <20040606.164253.572697249.rene@rocklinux-consulting.de> Hi, On: Sun, 6 Jun 2004 07:10:49 -0700, George Garvey wrote: > I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and > 2.6.6-1.422 and this scanner. > These are with Fedora sane-backends-1.0.14-1. I replaced the avision > files with the latest from Rene's SVN yesterday and rebuilt the RPMS. These > messages are from after using this newly built RPM. The problem was > happening before, with the standard RPM from Fedora. This is what prompted > trying the beta version. Hm - works here on 2.6.3 on an UltraSPARC and an iBook. I can test 2.6.6 in the next days - but I heared here on this list that recent 2.6 kernels have some USB problem(s)? Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From keith at claytons.org Sun Jun 6 17:36:42 2004 From: keith at claytons.org (Keith Clayton) Date: Sun, 6 Jun 2004 09:36:42 -0700 (PDT) Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: <20040606100716.GH19373@meier-geinitz.de> References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: In my case, w/problems scanning from win32-xsane across the network using an Epson Perfection 1250, I commented out all backends except net and plustek from dll.conf. This had no impact on my problem, where I could sucessfully scan once but then the scanner is left in an unusable state and and additional scan from any other machine fails. Keith On Sun, 6 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > Everyone who gets timeouts/USB errors with these two scanners and > sane-backends 1.0.14 please use the following workaround: > Comment out the "epson" line in dll.conf (/etc/sane.d/ or > /usr/local/etc/sane.d/). > > The epson backend seems to try to talk to these scanners because they > are Epson scanners. As they are supported by the plustek backend (not > epson) the scanners don't like the epson commands and USB errors occur. > > See bug 300751 for details: > https://alioth.debian.org/tracker/index.php?group_id=1308&atid=410366 > > I guess that bug didn't show up before the 1.0.14 release because the > automatic detection for USB scanners in the epson backend wasn't > turned on. > > Bye, > Henning > > From henning at meier-geinitz.de Sun Jun 6 17:41:31 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 18:41:31 +0200 Subject: [sane-devel] sane-backends 1.0.14 and Epson Perfection 1250 and 1260 trouble In-Reply-To: References: <20040606100716.GH19373@meier-geinitz.de> Message-ID: <20040606164131.GL19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 09:36:42AM -0700, Keith Clayton wrote: > In my case, w/problems scanning from win32-xsane across the network using > an Epson Perfection 1250, I commented out all backends except net and > plustek from dll.conf. > > This had no impact on my problem, where I could > sucessfully scan once but then the scanner is left in an unusable state > and and additional scan from any other machine fails. Not all problems are caused by that bug :-) If your problem was caused by that bug, you wouldn't be able to scan locally. Bye, Henning From henning at meier-geinitz.de Sun Jun 6 17:50:23 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 18:50:23 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086458420.26103.10.camel@yoda> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> Message-ID: <20040606165023.GM19373@meier-geinitz.de> Hi, On Sat, Jun 05, 2004 at 11:00:23AM -0700, Keith Clayton wrote: > scanimage -d net:localhost:plustek works perfectly. Can scan as many > times consecutively as I'd like. > > win32-xsane continues to fail on the 2nd scan. After power-cycling the > scanner I ran win32-xsane first then scanimage from the local machine. > Scanimage failed in this case. First pass of win32-xsane is evidently > leaving the scanner in a bad state. Used the debug flags as you > suggested and captured the output. Something is definitely going wrong > at the end of the win32-xsane/saned scan. > > I've attached the gzip output of running saned as you suggested with > debugging on and xinetd disabled. I X'd out any host, IP info from the > top of the log files but otherwise they're exactly what the debug kicked > out. Local: [...] [plustek] sane_cancel [plustek] do_cancel [plustek] TIME END 2: 20s [saned] process_request: waiting for request [saned] process_request: got request 3 [plustek] sane_close [saned] process_request: waiting for request [saned] process_request: got request 10 [plustek] sane_exit [plustek] Shutdown called (dev->fd=-1, libusb:001:013) [plustek] Waiting for scanner-ready... [plustek] Switching lamp off... [plustek] REG[0x5b] = 0x94 (msk=0x80) [plustek] REG[0x59] = 0x41 (msk=0x08) [plustek] LAMP-STATUS: 0x00000001 [plustek] Switching Lamp off [plustek] usb_switchLampX(ON=0,TPA=0) [plustek] Switch Lamp: 0, regs[0x5b] = 0x14 [plustek] REG[0x5b] = 0x14 (msk=0x80) [plustek] REG[0x59] = 0x41 (msk=0x08) [plustek] LAMP-STATUS: 0x00000000 [plustek] Lamp-Timer stopped [saned] quit: exiting Looks sane :-) The scan is cancelled, the device is closed and then sane_exit is called. net: [plustek] sane_cancel [plustek] do_cancel [plustek] TIME END 2: 88s [saned] process_request: waiting for request [saned] process_request: got request 5 [saned] process_request: waiting for request [saned] process_request: got request 5 [...] After sane-cancel() neither sane_close nor sane_exit() is called. That may cause a scanner to hang. The rquest 5 which is repeated some times is sane_control_option. Not too unusual, but xsane just seems to crash at that point so sane isn't closed correctly. Or saned crashes but you should get a segmentation fault or similar at that point. However, it's strange that "[saned] quit: exiting" is missing. Bye, Henning From sietse at cs.rug.nl Sun Jun 6 18:21:07 2004 From: sietse at cs.rug.nl (Sietse Achterop) Date: Sun, 06 Jun 2004 19:21:07 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606.164253.572697249.rene@rocklinux-consulting.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> Message-ID: <40C35283.1090507@cs.rug.nl> Rene Rebe wrote: > >> I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and >>2.6.6-1.422 and this scanner. > ...... > > Hm - works here on 2.6.3 on an UltraSPARC and an iBook. I can test > 2.6.6 in the next days - but I heared here on this list that recent > 2.6 kernels have some USB problem(s)? > Hi, Indeed, and I just retried it using the latest kernel (2.6.7-rc2-bk7) and the problem stays the same; somehow a bulk transport in usb falls in a timeout. Now the /var/log/kernel mentions: Jun 6 19:05:01 localhost kernel: usb 1-1: new full speed USB device using address 3 Jun 6 19:06:11 localhost kernel: usb 1-1: bulk timeout on ep3in Jun 6 19:06:11 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 Jun 6 19:06:41 localhost kernel: usb 1-1: bulk timeout on ep2in Jun 6 19:06:41 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 1 ret -110 Jun 6 19:06:44 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 22 ret -84 Jun 6 19:06:44 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x1 len 10 ret -71 Jun 6 19:06:44 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 1 ret -84 Jun 6 19:06:44 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x1 len 6 ret -71 See also my report from May 10, see: http://lists.alioth.debian.org/pipermail/sane-devel/2004-May/010985.html So I am afraid the problem still persists, with my HP7400C anyway. Greetings, Sietse Achterop From keith at claytons.org Sun Jun 6 18:27:57 2004 From: keith at claytons.org (Keith Clayton) Date: Sun, 6 Jun 2004 10:27:57 -0700 (PDT) Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040606165023.GM19373@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> Message-ID: No seg fault on the saned end. Its happily running, waiting to finish up. Xsane itself remains responsive. I can open menus, quit the app, etc. Not knowing the xsane code, does it start a child process to initiate scanning and maybe that process has crashed/hung? I'll look at the windows machine more. I can do a tcpdump capture of the communication if that would be helpful. K On Sun, 6 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > On Sat, Jun 05, 2004 at 11:00:23AM -0700, Keith Clayton wrote: > > scanimage -d net:localhost:plustek works perfectly. Can scan as many > > times consecutively as I'd like. > > > > win32-xsane continues to fail on the 2nd scan. After power-cycling the > > scanner I ran win32-xsane first then scanimage from the local machine. > > Scanimage failed in this case. First pass of win32-xsane is evidently > > leaving the scanner in a bad state. Used the debug flags as you > > suggested and captured the output. Something is definitely going wrong > > at the end of the win32-xsane/saned scan. > > > > I've attached the gzip output of running saned as you suggested with > > debugging on and xinetd disabled. I X'd out any host, IP info from the > > top of the log files but otherwise they're exactly what the debug kicked > > out. > > Local: > [...] > [plustek] sane_cancel > [plustek] do_cancel > [plustek] TIME END 2: 20s > [saned] process_request: waiting for request > [saned] process_request: got request 3 > [plustek] sane_close > [saned] process_request: waiting for request > [saned] process_request: got request 10 > [plustek] sane_exit > [plustek] Shutdown called (dev->fd=-1, libusb:001:013) > [plustek] Waiting for scanner-ready... > [plustek] Switching lamp off... > [plustek] REG[0x5b] = 0x94 (msk=0x80) > [plustek] REG[0x59] = 0x41 (msk=0x08) > [plustek] LAMP-STATUS: 0x00000001 > [plustek] Switching Lamp off > [plustek] usb_switchLampX(ON=0,TPA=0) > [plustek] Switch Lamp: 0, regs[0x5b] = 0x14 > [plustek] REG[0x5b] = 0x14 (msk=0x80) > [plustek] REG[0x59] = 0x41 (msk=0x08) > [plustek] LAMP-STATUS: 0x00000000 > [plustek] Lamp-Timer stopped > [saned] quit: exiting > > Looks sane :-) The scan is cancelled, the device is closed and then > sane_exit is called. > > net: > [plustek] sane_cancel > [plustek] do_cancel > [plustek] TIME END 2: 88s > [saned] process_request: waiting for request > [saned] process_request: got request 5 > [saned] process_request: waiting for request > [saned] process_request: got request 5 > [...] > > After sane-cancel() neither sane_close nor sane_exit() is called. That > may cause a scanner to hang. The rquest 5 which is repeated some times > is sane_control_option. Not too unusual, but xsane just seems to crash > at that point so sane isn't closed correctly. Or saned crashes but you > should get a segmentation fault or similar at that point. However, > it's strange that "[saned] quit: exiting" is missing. > > Bye, > Henning > > From rene at rocklinux-consulting.de Sun Jun 6 18:42:42 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 19:42:42 +0200 (CEST) Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <40C35283.1090507@cs.rug.nl> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> Message-ID: <20040606.194242.85423590.rene@rocklinux-consulting.de> Hi, On: Sun, 06 Jun 2004 19:21:07 +0200, Sietse Achterop wrote: > Hi, > > Indeed, and I just retried it using the latest kernel (2.6.7-rc2-bk7) and > the problem stays the same; somehow a bulk transport in usb falls in a timeout. > So I am afraid the problem still persists, with my HP7400C anyway. Have you tried if it works on your side with an older kernel? Say 2.6.3 or so? Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From sietse at cs.rug.nl Sun Jun 6 19:03:57 2004 From: sietse at cs.rug.nl (Sietse Achterop) Date: Sun, 06 Jun 2004 20:03:57 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606.194242.85423590.rene@rocklinux-consulting.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> Message-ID: <40C35C8D.7040401@cs.rug.nl> Rene Rebe wrote: > >>So I am afraid the problem still persists, with my HP7400C anyway. > > > Have you tried if it works on your side with an older kernel? Say > 2.6.3 or so? > No, I made the change to 2.6 after that one I think. Would it be usefull to test it with that version? If so I could test that. Regards, Sietse From insane at piments.com Sun Jun 6 19:12:51 2004 From: insane at piments.com (insane at piments.com) Date: Sun, 06 Jun 2004 20:12:51 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <40C35283.1090507@cs.rug.nl> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> Message-ID: Hi, Yes this seems to be a pretty broad issue with sane/libusb and more recent 2.6.x kernels I am getting very similar behaviour from my canoscan FB636U on Athlon-XP/Gentoo/2.6.6 kernel. [ebuild R ] media-gfx/xsane-0.93 [ebuild R ] media-gfx/sane-backends-1.0.14-r2 [ebuild R ] dev-libs/libusb-0.1.8 It was scanning briefly at one stage and I think I was running early 2.6 kernels at that time although I can not be precise. I does not appear to be a problem in the kernel itself since vuescan works perfectly on this system. If sane is going to continue to be an option it appears some dev work is needed to resolve this issue. I emailed Oliver Rauch and he indicated I should contact the backend maintainer (who apparently no longer replies to bug reports). But it seems from some of the posts here that the issue is much larger. Could someone remind me what the debug line is for this scanner so I can get more detailed output. Thanks, Peter. On Sun, 06 Jun 2004 19:21:07 +0200, Sietse Achterop wrote: > Rene Rebe wrote: >> >>> I'm getting a lot of problems with Fedora kernels 2.6.5-1.358 and >>> 2.6.6-1.422 and this scanner. >> > ...... >> Hm - works here on 2.6.3 on an UltraSPARC and an iBook. I can test >> 2.6.6 in the next days - but I heared here on this list that recent >> 2.6 kernels have some USB problem(s)? >> > > Hi, > > Indeed, and I just retried it using the latest kernel (2.6.7-rc2-bk7) and > the problem stays the same; somehow a bulk transport in usb falls in a > timeout. > Now the /var/log/kernel mentions: > > Jun 6 19:05:01 localhost kernel: usb 1-1: new full speed USB device > using address 3 > Jun 6 19:06:11 localhost kernel: usb 1-1: bulk timeout on ep3in > Jun 6 19:06:11 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed > ep 0x83 len 4096 ret -110 > Jun 6 19:06:41 localhost kernel: usb 1-1: bulk timeout on ep2in -- Using M2, Opera's e-mail client: on Gentoo Linux From henning at meier-geinitz.de Sun Jun 6 19:03:54 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 20:03:54 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606.194242.85423590.rene@rocklinux-consulting.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> Message-ID: <20040606180354.GO19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 07:42:42PM +0200, Rene Rebe wrote: > > So I am afraid the problem still persists, with my HP7400C anyway. > > Have you tried if it works on your side with an older kernel? Say > 2.6.3 or so? The gt68xx backend once had a bug that caused timeouts and frozen scanners. However, that bug only occured with some scanners and only with UHCI host controllers. As I used an OHCI controller at that time, I couldn't reproduce the bug at all. But it did exist. So looking at which kind of host controller the bug shows up and even which mainboard is used may help to find out what's actually going on. Bye, Henning From rene at rocklinux-consulting.de Sun Jun 6 19:24:22 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 20:24:22 +0200 (CEST) Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <40C35C8D.7040401@cs.rug.nl> References: <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> <40C35C8D.7040401@cs.rug.nl> Message-ID: <20040606.202422.805788455.rene@rocklinux-consulting.de> Hi, On: Sun, 06 Jun 2004 20:03:57 +0200, Sietse Achterop wrote: > No, I made the change to 2.6 after that one I think. > Would it be usefull to test it with that version? Yes - please test it. Also, what USB host controler type fo you have? Ohci, uhci or ehci? It can be obtained from /proc/bus/usb/devices - maybe just mail it if you are unsure ... > If so I could test that. > > Regards, > Sietse Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From henning at meier-geinitz.de Sun Jun 6 19:25:52 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 20:25:52 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> Message-ID: <20040606182552.GP19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 08:12:51PM +0200, insane at piments.com wrote: > Yes this seems to be a pretty broad issue with sane/libusb and more recent > 2.6.x kernels > > I am getting very similar behaviour from my canoscan FB636U on > Athlon-XP/Gentoo/2.6.6 kernel. That scanner is listed as "untested" so you were lucky if it worked. > [ebuild R ] media-gfx/xsane-0.93 > [ebuild R ] media-gfx/sane-backends-1.0.14-r2 > [ebuild R ] dev-libs/libusb-0.1.8 Some more data points: Linux 2.6.7rc2, ohci host controller, libusb 0.1.8 The following scanners do work without any trouble: Mustek 1200 CU (mustek_usb) Mustek BearPaw 1200 CU (gt68xx) Mustek BearPaw 2400 CU Plus (gt68xx) Plustek OpticPro U16B (gt68xx) Plustek Opticpro UT16 (plustek) > It was scanning briefly at one stage and I think I was running early 2.6 > kernels at that time although I can not be precise. > > I does not appear to be a problem in the kernel itself since vuescan works > perfectly on this system. That may be a hint, but needn't as SANE may trigger a bug in the kernel by accessing the scanner differently. > If sane is going to continue to be an option it appears some dev work is > needed to resolve this issue. First, we need to find out when this bug happens and in which part of SANE or the kernel it is. > Could someone remind me what the debug line is for this scanner so I can > get more detailed output. export SANE_DEBUG_CANON630U=255 For USB debug messages try also: export SANE_DEBUG_SANEI_USB=255 Bye, Henning From henning at meier-geinitz.de Sun Jun 6 20:12:18 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 21:12:18 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606182552.GP19373@meier-geinitz.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606182552.GP19373@meier-geinitz.de> Message-ID: <20040606191218.GQ19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 08:25:52PM +0200, Henning Meier-Geinitz wrote: > > Yes this seems to be a pretty broad issue with sane/libusb and more recent > > 2.6.x kernels As already mentioned on this list and in the bug tracking system (https://alioth.debian.org/tracker/index.php?func=detail&aid=300759&group_id=1308&atid=410366) scanning fails with libusb if the scanner is accessed during that scan. This access can even be caused by sane-find-scanner. Maybe these two problems are in fact the same? E.g. when some hotplugscript tries to access the scanner while it's opened by sane? I don't know if it's at least theoretically possible to cause the double access bug by a bug in sane. As the libusb device is claimed by sane, it shouldn't be possible to send anything to the device while the interface is claimed. Bye, Henning From insane at piments.com Sun Jun 6 20:35:56 2004 From: insane at piments.com (insane at piments.com) Date: Sun, 06 Jun 2004 21:35:56 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606182552.GP19373@meier-geinitz.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606182552.GP19373@meier-geinitz.de> Message-ID: Thanks Henning, > That scanner is listed as "untested" so you were lucky if it worked. True but it seems to be very close to the FB630U for which the backend was written. Anyway it has worked with sane at one stage, and pretty well. Hopefully I can soon provide some feedback and it will be classed as tested! > SANE may trigger a bug in the > kernel by accessing the scanner differently. Fair point, vuescan does not prove anything more that the hardware is good and CAN work on Linux. 0000:00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) 0000:00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23) So I am on UHCI, seems like others having pbs are using this driver as well (I also compiled ehci as module but it did not change the bahaviour). Here's an end snip of the USB debug output. [sanei_usb] 0000: 01 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132, index = 0, len = 1 [sanei_usb] 0000: 00 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 12, value = 131, index = 0, len = 1 [sanei_usb] 0000: 01 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132, index = 0, len = 1 [sanei_usb] 0000: 00 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 12, value = 131, index = 0, len = 1 [sanei_usb] 0000: 01 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132, index = 0, len = 1 [sanei_usb] 0000: 00 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0x40, req = 12, value = 131, index = 0, len = 1 [sanei_usb] 0000: 01 ................ [sanei_usb] sanei_usb_control_msg: rtype = 0xc0, req = 12, value = 132, index = 0, len = 1 This is the loop it gets stuck in and hangs sane. xsane xscanimage etc. all lock up. I Cntl-C out at this point. Now here's the end of the Canon_bebug output: [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ I dont know if that enables you to see more of what is happening. Regards, Peter. On Sun, 6 Jun 2004 20:25:52 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Sun, Jun 06, 2004 at 08:12:51PM +0200, insane at piments.com wrote: >> Yes this seems to be a pretty broad issue with sane/libusb and more >> recent >> 2.6.x kernels >> >> I am getting very similar behaviour from my canoscan FB636U on >> Athlon-XP/Gentoo/2.6.6 kernel. > > That scanner is listed as "untested" so you were lucky if it worked. > >> [ebuild R ] media-gfx/xsane-0.93 >> [ebuild R ] media-gfx/sane-backends-1.0.14-r2 >> [ebuild R ] dev-libs/libusb-0.1.8 > > Some more data points: Linux 2.6.7rc2, ohci host controller, libusb 0.1.8 > > The following scanners do work without any trouble: > > Mustek 1200 CU (mustek_usb) > Mustek BearPaw 1200 CU (gt68xx) > Mustek BearPaw 2400 CU Plus (gt68xx) > Plustek OpticPro U16B (gt68xx) > Plustek Opticpro UT16 (plustek) > >> It was scanning briefly at one stage and I think I was running early 2.6 >> kernels at that time although I can not be precise. >> >> I does not appear to be a problem in the kernel itself since vuescan >> works >> perfectly on this system. > > That may be a hint, but needn't as SANE may trigger a bug in the > kernel by accessing the scanner differently. > >> If sane is going to continue to be an option it appears some dev work is >> needed to resolve this issue. > > First, we need to find out when this bug happens and in which part of > SANE or the kernel it is. > >> Could someone remind me what the debug line is for this scanner so I can >> get more detailed output. > > export SANE_DEBUG_CANON630U=255 > > For USB debug messages try also: > > export SANE_DEBUG_SANEI_USB=255 > > Bye, > Henning > -- Using M2, Opera's e-mail client: on Gentoo Linux From sietse at cs.rug.nl Sun Jun 6 20:47:03 2004 From: sietse at cs.rug.nl (Sietse Achterop) Date: Sun, 06 Jun 2004 21:47:03 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606.202422.805788455.rene@rocklinux-consulting.de> References: <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> <40C35C8D.7040401@cs.rug.nl> <20040606.202422.805788455.rene@rocklinux-consulting.de> Message-ID: <40C374B7.6010806@cs.rug.nl> Rene Rebe wrote: > Yes - please test it. Hi, just tested kernel 2.6.3 and it has exactly the same problem:(. > > Also, what USB host controler type fo you have? Ohci, uhci or ehci? > It can be obtained from /proc/bus/usb/devices - maybe just mail it if > you are unsure ... > Uhci is used and a 440LX chipset with a Pentium II (333 MHz). It is an Asus P2L-B motherboard. Regards, Sietse ================================================== From /proc/bus/usb/devices : S: Manufacturer=Linux 2.6.7-rc2-bk7 uhci_hcd S: Product=Intel Corp. 82371AB/EB/MB PIIX4 USB And from lspci: 0000:00:00.0 Host bridge: Intel Corp. 440LX/EX - 82443LX/EX Host bridge (rev 03) 0000:00:01.0 PCI bridge: Intel Corp. 440LX/EX - 82443LX/EX AGP bridge (rev 03) 0000:00:04.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 01) 0000:00:04.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01) 0000:00:04.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01) 0000:00:04.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 01) 0000:00:0b.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) 0000:00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) 0000:01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 4400] (rev a2) From r3ddr at yahoo.com Sun Jun 6 20:49:23 2004 From: r3ddr at yahoo.com (Ciprian Manea) Date: Sun, 6 Jun 2004 12:49:23 -0700 (PDT) Subject: [sane-devel] sane :: plustek opticslim m12 In-Reply-To: <1086435353.11282.ezmlm@linuxhacker.org> Message-ID: <20040606194923.78653.qmail@web50405.mail.yahoo.com> Now I have another problem :| ps. yes, OpticSlim M12 it's an AutoFeed scanner (small format, marketted as a notebook scanner :) I tried to "fix" the source, and make scanimage ignore this 'power' stuff, but then the "scanning" is verry erratic. it will feed the page, too fast to do any scanning I guess (indicator light will be solid green. usually under Win the light is blinking during operation/scanning); then it will properly eject the page (that is, feeding it much faster to the 'exit' :) Any advice on what should be done from this point? thanks! # scanimage [gt68xx] sane_open: power control failure: check power plug! scanimage: open of device gt68xx:/dev/usb/scanner0 failed: Error during device I/O output with SANE_DEBUG_GT68XX=255 in the attached file ===== http://nou.surse.ro - Portalul tau cu stiri, informatii si resurse online. __________________________________ Do you Yahoo!? Friends. Fun. Try the all-new Yahoo! Messenger. http://messenger.yahoo.com/ -------------- next part -------------- [sanei_debug] Setting debug level of gt68xx to 255. [gt68xx] SANE GT68xx backend version 1.0 build 60 from sane-backends 1.0.14-cvs [gt68xx] sane_init: authorize != null [gt68xx] sane_init: debug options are enabled, handle with care [gt68xx] sane_init: little endian machine [gt68xx] sane_init: reading config file `gt68xx.conf' [gt68xx] sane_init: config file line 1: ignoring empty line [gt68xx] sane_init: config file line 2: ignoring comment line [gt68xx] sane_init: config file line 3: ignoring comment line [gt68xx] sane_init: config file line 4: ignoring empty line [gt68xx] sane_init: config file line 5: ignoring comment line [gt68xx] sane_init: config file line 6: ignoring comment line [gt68xx] sane_init: config file line 7: ignoring comment line [gt68xx] sane_init: config file line 8: ignoring comment line [gt68xx] sane_init: config file line 9: ignoring empty line [gt68xx] sane_init: config file line 10: ignoring comment line [gt68xx] sane_init: config file line 11: ignoring comment line [gt68xx] sane_init: config file line 12: ignoring comment line [gt68xx] sane_init: config file line 13: trying to attach `usb 0x05d8 0x4002' [gt68xx] sane_init: config file line 14: ignoring empty line [gt68xx] sane_init: config file line 15: ignoring comment line [gt68xx] sane_init: config file line 16: ignoring empty line [gt68xx] sane_init: config file line 17: ignoring comment line [gt68xx] sane_init: config file line 18: ignoring comment line [gt68xx] sane_init: config file line 19: ignoring empty line [gt68xx] sane_init: config file line 20: ignoring comment line [gt68xx] sane_init: config file line 21: ignoring comment line [gt68xx] sane_init: config file line 22: ignoring comment line [gt68xx] sane_init: config file line 23: ignoring comment line [gt68xx] sane_init: config file line 24: ignoring empty line [gt68xx] sane_init: config file line 25: ignoring comment line [gt68xx] sane_init: config file line 26: ignoring comment line [gt68xx] sane_init: config file line 27: ignoring comment line [gt68xx] sane_init: config file line 28: ignoring comment line [gt68xx] sane_init: config file line 29: ignoring empty line [gt68xx] sane_init: config file line 30: ignoring comment line [gt68xx] sane_init: config file line 31: ignoring comment line [gt68xx] sane_init: config file line 32: ignoring empty line [gt68xx] sane_init: config file line 33: ignoring comment line [gt68xx] sane_init: config file line 34: ignoring comment line [gt68xx] sane_init: config file line 35: ignoring comment line [gt68xx] sane_init: config file line 36: ignoring empty line [gt68xx] sane_init: config file line 37: ignoring comment line [gt68xx] sane_init: config file line 38: ignoring comment line [gt68xx] sane_init: config file line 39: ignoring comment line [gt68xx] sane_init: config file line 40: ignoring comment line [gt68xx] sane_init: config file line 41: ignoring empty line [gt68xx] sane_init: config file line 42: ignoring comment line [gt68xx] sane_init: config file line 43: ignoring comment line [gt68xx] sane_init: config file line 44: ignoring comment line [gt68xx] sane_init: config file line 45: ignoring comment line [gt68xx] sane_init: config file line 46: ignoring empty line [gt68xx] sane_init: config file line 47: ignoring comment line [gt68xx] sane_init: config file line 48: ignoring comment line [gt68xx] sane_init: config file line 49: ignoring comment line [gt68xx] sane_init: config file line 50: ignoring comment line [gt68xx] sane_init: config file line 51: ignoring empty line [gt68xx] sane_init: config file line 52: ignoring comment line [gt68xx] sane_init: config file line 53: ignoring comment line [gt68xx] sane_init: config file line 54: ignoring comment line [gt68xx] sane_init: config file line 55: ignoring comment line [gt68xx] sane_init: config file line 56: ignoring empty line [gt68xx] sane_init: config file line 57: ignoring comment line [gt68xx] sane_init: config file line 58: ignoring comment line [gt68xx] sane_init: config file line 59: ignoring empty line [gt68xx] sane_init: config file line 60: ignoring comment line [gt68xx] sane_init: config file line 61: ignoring comment line [gt68xx] sane_init: config file line 62: ignoring comment line [gt68xx] sane_init: config file line 63: ignoring comment line [gt68xx] sane_init: config file line 64: ignoring empty line [gt68xx] sane_init: config file line 65: ignoring comment line [gt68xx] sane_init: config file line 66: ignoring comment line [gt68xx] sane_init: config file line 67: trying to attach `usb 0x055f 0x021e' [gt68xx] sane_init: config file line 68: ignoring empty line [gt68xx] sane_init: config file line 69: ignoring comment line [gt68xx] sane_init: config file line 70: ignoring empty line [gt68xx] sane_init: config file line 71: ignoring comment line [gt68xx] sane_init: config file line 72: ignoring comment line [gt68xx] sane_init: config file line 73: ignoring empty line [gt68xx] sane_init: config file line 74: ignoring comment line [gt68xx] sane_init: config file line 75: ignoring comment line [gt68xx] sane_init: config file line 76: trying to attach `usb 0x055f 0x0218' [gt68xx] sane_init: config file line 77: ignoring empty line [gt68xx] sane_init: config file line 78: ignoring comment line [gt68xx] sane_init: config file line 79: ignoring empty line [gt68xx] sane_init: config file line 80: ignoring comment line [gt68xx] sane_init: config file line 81: ignoring comment line [gt68xx] sane_init: config file line 82: ignoring empty line [gt68xx] sane_init: config file line 83: ignoring comment line [gt68xx] sane_init: config file line 84: ignoring comment line [gt68xx] sane_init: config file line 85: trying to attach `usb 0x055f 0x0219' [gt68xx] sane_init: config file line 86: ignoring empty line [gt68xx] sane_init: config file line 87: ignoring comment line [gt68xx] sane_init: config file line 88: ignoring comment line [gt68xx] sane_init: config file line 89: trying to attach `usb 0x055f 0x021a' [gt68xx] sane_init: config file line 90: ignoring empty line [gt68xx] sane_init: config file line 91: ignoring comment line [gt68xx] sane_init: config file line 92: ignoring comment line [gt68xx] sane_init: config file line 93: ignoring empty line [gt68xx] sane_init: config file line 94: ignoring comment line [gt68xx] sane_init: config file line 95: ignoring comment line [gt68xx] sane_init: config file line 96: trying to attach `usb 0x055f 0x021d' [gt68xx] sane_init: config file line 97: ignoring empty line [gt68xx] sane_init: config file line 98: ignoring comment line [gt68xx] sane_init: config file line 99: ignoring comment line [gt68xx] sane_init: config file line 100: trying to attach `usb 0x055f 0x021c' [gt68xx] sane_init: config file line 101: ignoring empty line [gt68xx] sane_init: config file line 102: ignoring comment line [gt68xx] sane_init: config file line 103: ignoring empty line [gt68xx] sane_init: config file line 104: ignoring comment line [gt68xx] sane_init: config file line 105: ignoring comment line [gt68xx] sane_init: config file line 106: ignoring comment line [gt68xx] sane_init: config file line 107: ignoring empty line [gt68xx] sane_init: config file line 108: ignoring comment line [gt68xx] sane_init: config file line 109: ignoring comment line [gt68xx] sane_init: config file line 110: trying to attach `usb 0x055f 0x0210' [gt68xx] sane_init: config file line 111: ignoring empty line [gt68xx] sane_init: config file line 112: ignoring comment line [gt68xx] sane_init: config file line 113: ignoring empty line [gt68xx] sane_init: config file line 114: ignoring comment line [gt68xx] sane_init: config file line 115: ignoring comment line [gt68xx] sane_init: config file line 116: trying to attach `usb 0x043d 0x002d' [gt68xx] sane_init: config file line 117: ignoring empty line [gt68xx] sane_init: config file line 118: ignoring comment line [gt68xx] sane_init: config file line 119: ignoring comment line [gt68xx] sane_init: config file line 120: trying to attach `usb 0x07b3 0x0401' [gt68xx] sane_init: config file line 121: trying to attach `usb 0x07b3 0x0400' [gt68xx] sane_init: config file line 122: ignoring empty line [gt68xx] sane_init: config file line 123: ignoring comment line [gt68xx] sane_init: config file line 124: ignoring empty line [gt68xx] sane_init: config file line 125: ignoring comment line [gt68xx] sane_init: config file line 126: ignoring comment line [gt68xx] sane_init: config file line 127: ignoring comment line [gt68xx] sane_init: config file line 128: ignoring empty line [gt68xx] sane_init: config file line 129: ignoring comment line [gt68xx] sane_init: config file line 130: ignoring comment line [gt68xx] sane_init: config file line 131: trying to attach `usb 0x07b3 0x0402' [gt68xx] sane_init: config file line 132: trying to attach `usb 0x07b3 0x0403' [gt68xx] sane_init: config file line 133: ignoring empty line [gt68xx] sane_init: config file line 134: ignoring comment line [gt68xx] sane_init: config file line 135: ignoring empty line [gt68xx] sane_init: config file line 136: ignoring comment line [gt68xx] sane_init: config file line 137: ignoring comment line [gt68xx] sane_init: config file line 138: ignoring empty line [gt68xx] sane_init: config file line 139: ignoring comment line [gt68xx] sane_init: config file line 140: ignoring comment line [gt68xx] sane_init: config file line 141: trying to attach `usb 0x07b3 0x0412' [gt68xx] attach: start: devp != NULL, may_wait = 0 [gt68xx] attach: trying to open device `/dev/usb/scanner0' [gt68xx] gt68xx_device_new: enter [gt68xx] gt68xx_device_new:: leave: ok [gt68xx] gt68xx_device_open: enter: dev=0x80859e0 [gt68xx] gt68xx_device_open: leave: ok [gt68xx] attach: device `/dev/usb/scanner0' successfully opened [gt68xx] attach: found Plustek flatbed scanner OpticSlim M12 at /dev/usb/scanner0 [gt68xx] gt68xx_device_close: enter: dev=0x80859e0 [gt68xx] gt68xx_device_close: leave: ok [gt68xx] attach: exit [gt68xx] attach: start: devp != NULL, may_wait = 0 [gt68xx] attach: trying to open device `libusb:001:011' [gt68xx] gt68xx_device_new: enter [gt68xx] gt68xx_device_new:: leave: ok [gt68xx] gt68xx_device_open: enter: dev=0x8085a58 [gt68xx] gt68xx_device_open: sanei_usb_open failed: Device busy [gt68xx] attach: couldn't open device `libusb:001:011': Device busy [gt68xx] gt68xx_device_free: enter: dev=0x8085a58 [gt68xx] gt68xx_device_free: freeing dev [gt68xx] gt68xx_device_free: leave: ok [gt68xx] somewhere: attach (devname, &dev, 0): Device busy [gt68xx] sane_init: config file line 142: ignoring empty line [gt68xx] sane_init: config file line 143: ignoring comment line [gt68xx] sane_init: config file line 144: ignoring comment line [gt68xx] sane_init: config file line 145: trying to attach `usb 0x07b3 0x0413' [gt68xx] sane_init: config file line 146: ignoring empty line [gt68xx] sane_init: config file line 147: ignoring comment line [gt68xx] sane_init: config file line 148: ignoring comment line [gt68xx] sane_init: config file line 149: trying to attach `usb 0x07b3 0x0422' [gt68xx] sane_init: config file line 150: ignoring empty line [gt68xx] sane_init: config file line 151: ignoring comment line [gt68xx] sane_init: config file line 152: ignoring comment line [gt68xx] sane_init: config file line 153: trying to attach `usb 0x0458 0x2011' [gt68xx] sane_init: config file line 154: ignoring empty line [gt68xx] sane_init: config file line 155: ignoring comment line [gt68xx] sane_init: config file line 156: ignoring empty line [gt68xx] sane_init: config file line 157: ignoring comment line [gt68xx] sane_init: config file line 158: ignoring comment line [gt68xx] sane_init: config file line 159: trying to attach `usb 0x0458 0x201b' [gt68xx] sane_init: config file line 160: ignoring empty line [gt68xx] sane_init: config file line 161: ignoring comment line [gt68xx] sane_init: config file line 162: ignoring comment line [gt68xx] sane_init: config file line 163: trying to attach `usb 0x0458 0x2017' [gt68xx] sane_init: config file line 164: ignoring empty line [gt68xx] sane_init: config file line 165: ignoring comment line [gt68xx] sane_init: config file line 166: ignoring comment line [gt68xx] sane_init: config file line 167: trying to attach `usb 0x0458 0x201a' [gt68xx] sane_init: config file line 168: ignoring empty line [gt68xx] sane_init: config file line 169: ignoring comment line [gt68xx] sane_init: config file line 170: ignoring comment line [gt68xx] sane_init: config file line 171: trying to attach `usb 0x0458 0x201f' [gt68xx] sane_init: config file line 172: ignoring empty line [gt68xx] sane_init: config file line 173: ignoring comment line [gt68xx] sane_init: config file line 174: ignoring comment line [gt68xx] sane_init: config file line 175: trying to attach `usb 0x0458 0x2014' [gt68xx] sane_init: config file line 176: ignoring empty line [gt68xx] sane_init: config file line 177: ignoring comment line [gt68xx] sane_init: config file line 178: ignoring comment line [gt68xx] sane_init: config file line 179: trying to attach `usb 0x04a7 0x0444' [gt68xx] sane_init: config file line 180: ignoring empty line [gt68xx] sane_init: config file line 181: ignoring comment line [gt68xx] sane_init: exit [gt68xx] sane_get_devices: start: local_only = false [gt68xx] sane_get_devices: exit [gt68xx] sane_open: start (devicename = `/dev/usb/scanner0') [gt68xx] sane_open: found `plustek-opticslim-m12' in devlist [gt68xx] gt68xx_device_open: enter: dev=0x80859e0 [gt68xx] gt68xx_device_open: leave: ok [gt68xx] gt68xx_device_activate: model "plustek-opticslim-m12" [gt68xx] download_firmware: trying /usr/local/share/sane/gt68xx/cism216.fw [gt68xx] firmware size: 8192 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x0, size=0x40, data=0x8095968 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x40, size=0x40, data=0x80959a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x80, size=0x40, data=0x80959e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xc0, size=0x40, data=0x8095a28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x100, size=0x40, data=0x8095a68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x100, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x140, size=0x40, data=0x8095aa8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x140, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x180, size=0x40, data=0x8095ae8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x180, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1c0, size=0x40, data=0x8095b28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x200, size=0x40, data=0x8095b68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x200, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x240, size=0x40, data=0x8095ba8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x240, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x280, size=0x40, data=0x8095be8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x280, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x2c0, size=0x40, data=0x8095c28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x2c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x300, size=0x40, data=0x8095c68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x300, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x340, size=0x40, data=0x8095ca8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x340, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x380, size=0x40, data=0x8095ce8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x380, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x3c0, size=0x40, data=0x8095d28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x3c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x400, size=0x40, data=0x8095d68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x400, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x440, size=0x40, data=0x8095da8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x440, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x480, size=0x40, data=0x8095de8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x480, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x4c0, size=0x40, data=0x8095e28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x4c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x500, size=0x40, data=0x8095e68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x500, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x540, size=0x40, data=0x8095ea8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x540, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x580, size=0x40, data=0x8095ee8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x580, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x5c0, size=0x40, data=0x8095f28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x5c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x600, size=0x40, data=0x8095f68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x600, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x640, size=0x40, data=0x8095fa8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x640, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x680, size=0x40, data=0x8095fe8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x680, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x6c0, size=0x40, data=0x8096028 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x6c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x700, size=0x40, data=0x8096068 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x700, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x740, size=0x40, data=0x80960a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x740, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x780, size=0x40, data=0x80960e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x780, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x7c0, size=0x40, data=0x8096128 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x7c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x800, size=0x40, data=0x8096168 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x800, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x840, size=0x40, data=0x80961a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x840, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x880, size=0x40, data=0x80961e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x880, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x8c0, size=0x40, data=0x8096228 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x8c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x900, size=0x40, data=0x8096268 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x900, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x940, size=0x40, data=0x80962a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x940, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x980, size=0x40, data=0x80962e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x980, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x9c0, size=0x40, data=0x8096328 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x9c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xa00, size=0x40, data=0x8096368 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xa00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xa40, size=0x40, data=0x80963a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xa40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xa80, size=0x40, data=0x80963e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xa80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xac0, size=0x40, data=0x8096428 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xac0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xb00, size=0x40, data=0x8096468 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xb00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xb40, size=0x40, data=0x80964a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xb40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xb80, size=0x40, data=0x80964e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xb80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xbc0, size=0x40, data=0x8096528 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xbc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xc00, size=0x40, data=0x8096568 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xc00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xc40, size=0x40, data=0x80965a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xc40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xc80, size=0x40, data=0x80965e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xc80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xcc0, size=0x40, data=0x8096628 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xcc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xd00, size=0x40, data=0x8096668 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xd00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xd40, size=0x40, data=0x80966a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xd40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xd80, size=0x40, data=0x80966e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xd80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xdc0, size=0x40, data=0x8096728 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xdc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xe00, size=0x40, data=0x8096768 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xe00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xe40, size=0x40, data=0x80967a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xe40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xe80, size=0x40, data=0x80967e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xe80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xec0, size=0x40, data=0x8096828 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xec0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xf00, size=0x40, data=0x8096868 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xf00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xf40, size=0x40, data=0x80968a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xf40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xf80, size=0x40, data=0x80968e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xf80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0xfc0, size=0x40, data=0x8096928 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0xfc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1000, size=0x40, data=0x8096968 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1000, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1040, size=0x40, data=0x80969a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1040, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1080, size=0x40, data=0x80969e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1080, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x10c0, size=0x40, data=0x8096a28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x10c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1100, size=0x40, data=0x8096a68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1100, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1140, size=0x40, data=0x8096aa8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1140, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1180, size=0x40, data=0x8096ae8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1180, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x11c0, size=0x40, data=0x8096b28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x11c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1200, size=0x40, data=0x8096b68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1200, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1240, size=0x40, data=0x8096ba8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1240, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1280, size=0x40, data=0x8096be8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1280, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x12c0, size=0x40, data=0x8096c28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x12c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1300, size=0x40, data=0x8096c68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1300, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1340, size=0x40, data=0x8096ca8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1340, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1380, size=0x40, data=0x8096ce8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1380, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x13c0, size=0x40, data=0x8096d28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x13c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1400, size=0x40, data=0x8096d68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1400, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1440, size=0x40, data=0x8096da8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1440, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1480, size=0x40, data=0x8096de8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1480, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x14c0, size=0x40, data=0x8096e28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x14c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1500, size=0x40, data=0x8096e68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1500, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1540, size=0x40, data=0x8096ea8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1540, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1580, size=0x40, data=0x8096ee8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1580, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x15c0, size=0x40, data=0x8096f28 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x15c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1600, size=0x40, data=0x8096f68 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1600, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1640, size=0x40, data=0x8096fa8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1640, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1680, size=0x40, data=0x8096fe8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1680, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x16c0, size=0x40, data=0x8097028 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x16c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1700, size=0x40, data=0x8097068 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1700, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1740, size=0x40, data=0x80970a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1740, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1780, size=0x40, data=0x80970e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1780, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x17c0, size=0x40, data=0x8097128 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x17c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1800, size=0x40, data=0x8097168 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1800, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1840, size=0x40, data=0x80971a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1840, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1880, size=0x40, data=0x80971e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1880, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x18c0, size=0x40, data=0x8097228 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x18c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1900, size=0x40, data=0x8097268 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1900, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1940, size=0x40, data=0x80972a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1940, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1980, size=0x40, data=0x80972e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1980, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x19c0, size=0x40, data=0x8097328 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x19c0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1a00, size=0x40, data=0x8097368 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1a00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1a40, size=0x40, data=0x80973a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1a40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1a80, size=0x40, data=0x80973e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1a80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1ac0, size=0x40, data=0x8097428 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1ac0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1b00, size=0x40, data=0x8097468 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1b00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1b40, size=0x40, data=0x80974a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1b40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1b80, size=0x40, data=0x80974e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1b80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1bc0, size=0x40, data=0x8097528 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1bc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1c00, size=0x40, data=0x8097568 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1c00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1c40, size=0x40, data=0x80975a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1c40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1c80, size=0x40, data=0x80975e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1c80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1cc0, size=0x40, data=0x8097628 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1cc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1d00, size=0x40, data=0x8097668 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1d00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1d40, size=0x40, data=0x80976a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1d40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1d80, size=0x40, data=0x80976e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1d80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1dc0, size=0x40, data=0x8097728 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1dc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1e00, size=0x40, data=0x8097768 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1e00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1e40, size=0x40, data=0x80977a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1e40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1e80, size=0x40, data=0x80977e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1e80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1ec0, size=0x40, data=0x8097828 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1ec0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1f00, size=0x40, data=0x8097868 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1f00, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1f40, size=0x40, data=0x80978a8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1f40, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1f80, size=0x40, data=0x80978e8 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1f80, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_memory_write: dev=0x80859e0, addr=0x1fc0, size=0x40, data=0xbfffaa00 [gt68xx] gt68xx_device_memory_read: dev=0x80859e0, addr=0x1fc0, size=0x40, data=0xbfffa9c0 [gt68xx] gt68xx_device_generic_req: command=0x69 [gt68xx] >> 69 01 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] << 00 69 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] gt68xx_device_generic_req: command=0x2e [gt68xx] >> 2e 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] << 00 2e 12 04 b3 07 05 00 00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] get_id: vendor id=0x0412, product id=0x07B3, DID=0x04000005, FID=0x0000 [gt68xx] gt68xx_device_generic_req: command=0x3f [gt68xx] >> 3f 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] << 00 3f 3f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [gt68xx] sane_open: power control failure: check power plug! scanimage: open of device gt68xx:/dev/usb/scanner0 failed: Error during device I/O [gt68xx] sane_exit: start [gt68xx] gt68xx_device_free: enter: dev=0x80859e0 [gt68xx] gt68xx_device_close: enter: dev=0x80859e0 [gt68xx] gt68xx_device_close: leave: ok [gt68xx] gt68xx_device_free: freeing dev [gt68xx] gt68xx_device_free: leave: ok [gt68xx] sane_exit: exit From henning at meier-geinitz.de Sun Jun 6 20:53:24 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 6 Jun 2004 21:53:24 +0200 Subject: [sane-devel] sane :: plustek opticslim m12 In-Reply-To: <20040606194923.78653.qmail@web50405.mail.yahoo.com> References: <1086435353.11282.ezmlm@linuxhacker.org> <20040606194923.78653.qmail@web50405.mail.yahoo.com> Message-ID: <20040606195324.GR19373@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 12:49:23PM -0700, Ciprian Manea wrote: > ps. yes, OpticSlim M12 it's an AutoFeed scanner (small > format, marketted as a notebook scanner :) This is the first autofeed scanner that will (hopefully) be supported by the gt68xx backend so you'll need some more effort than for a flatbed scanner. > I tried to "fix" the source, Please send a patch of the changes you did so far, especially gt68xx_devices.c. > and make scanimage ignore this 'power' stuff, The next gt68xx version will have a flag to disable that test as it doesn't work with other Plustek scanners, either. > but then the "scanning" is verry > erratic. it will feed the page, too fast to do any > scanning I guess (indicator light will be solid green. > usually under Win the light is blinking during > operation/scanning); then it will properly eject the > page (that is, feeding it much faster to the 'exit' :) > > > Any advice on what should be done from this point? > thanks! Make a logfile of the windows scan process using the sniffusb program. Anaylze the log file and add the changes to the gt68xx backend. Check especially the "20 01" (setup scan) command and the move mohme commands. > [gt68xx] gt68xx_device_generic_req: command=0x3f > [gt68xx] >> 3f 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > [gt68xx] << 00 3f 3f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > [gt68xx] sane_open: power control failure: check power plug! Just disable this test. Bye, Henning From rene at rocklinux-consulting.de Sun Jun 6 21:43:20 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 06 Jun 2004 22:43:20 +0200 (CEST) Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <40C374B7.6010806@cs.rug.nl> References: <40C35C8D.7040401@cs.rug.nl> <20040606.202422.805788455.rene@rocklinux-consulting.de> <40C374B7.6010806@cs.rug.nl> Message-ID: <20040606.224320.558917180.rene@rocklinux-consulting.de> Hi, On: Sun, 06 Jun 2004 21:47:03 +0200, Sietse Achterop wrote: > just tested kernel 2.6.3 and it has exactly the same problem:(. > > > > > Also, what USB host controler type fo you have? Ohci, uhci or ehci? > > It can be obtained from /proc/bus/usb/devices - maybe just mail it if > > you are unsure ... > > > > Uhci is used and a 440LX chipset with a Pentium II (333 MHz). > It is an Asus P2L-B motherboard. Ok - then it might be a generic UHCI problem. I only have OHCI hardware around. I try to find s.th. to test - maybe some colleagues box if I find a UHCI one ... Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From olaf at epkowa.co.jp Mon Jun 7 01:52:36 2004 From: olaf at epkowa.co.jp (Olaf Meeuwissen) Date: Mon, 07 Jun 2004 09:52:36 +0900 Subject: [sane-devel] Epson GT10000 and ADF problems In-Reply-To: <20040605180107.3dda0c3e.martin@mkcollins.org> (Martin Collins's message of "Sat, 5 Jun 2004 18:01:07 +0100") References: <20040530043040.5034a5e2.martin@mkcollins.org> <20040603090719.45d7eb5b.martin@mkcollins.org> <87aczloufp.fsf@zen.epkowa.co.jp> <20040603230332.3dd7a5f6.martin@mkcollins.org> <873c5c19rl.fsf@zen.epkowa.co.jp> <20040604011210.240e6d85.martin@mkcollins.org> <87smdcyxc3.fsf@zen.epkowa.co.jp> <20040605180107.3dda0c3e.martin@mkcollins.org> Message-ID: <87smd88a0b.fsf@zen.epkowa.co.jp> Martin Collins writes: > On Fri, 04 Jun 2004 09:35:08 +0900 > Olaf Meeuwissen wrote: > >> Alright, I'll send the tarball for gcc-3.2 (or later) in a separate >> mail. > > Thanks for that. However it wouldn't make. Some C++ library or header > mismatch. Could be my GTK is too new. "Image Scan! for Linux" still has to add GTK 2.x support :-( > In the process I discovered I had a tarball of 1.5.2 on one of my > machines. That did compile cleanly but didn't work in a similar way to > 1.8.1 but if 1.5.2 (a backend bugfix release) compiles cleanly, I doubt that is the cause. Looks more like some of the modifications to the build machinery fixed whatever makes the compile of 1.5.1 fail for you. > I will try to get 1.5.1 compiled and do some testing later this week. Rather than getting 1.5.1 to compile, I'd suggest you drop epkowa.c from 1.5.1 into the source tree of 1.5.2 if you really want to test with 1.5.1. All other changes are not related to the backend. HTH, -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From tmwg-sane at inxservices.com Mon Jun 7 07:42:08 2004 From: tmwg-sane at inxservices.com (George Garvey) Date: Sun, 6 Jun 2004 23:42:08 -0700 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: <20040606180354.GO19373@meier-geinitz.de> References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606.194242.85423590.rene@rocklinux-consulting.de> <20040606180354.GO19373@meier-geinitz.de> Message-ID: <20040607064208.GA4324@inxservices.com> On Sun, Jun 06, 2004 at 08:03:54PM +0200, Henning Meier-Geinitz wrote: > So looking at which kind of host controller the bug shows up and even > which mainboard is used may help to find out what's actually going on. Mine is an ASUS A7V333. This is proc/bus/usb/devices: 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.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.6-1.422 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=0000:00:11.3 C:* #Ifs= 1 Cfg#= 1 Atr=c0 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= 2 Ivl=255ms T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0 D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=0000 ProdID=0000 Rev= 2.06 S: Manufacturer=Linux 2.6.6-1.422 uhci_hcd S: Product=UHCI Host Controller S: SerialNumber=0000:00:11.2 C:* #Ifs= 1 Cfg#= 1 Atr=c0 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= 2 Ivl=255ms T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 3 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=SCN2A9S0330LZ 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 From linux at defi.hu Mon Jun 7 12:01:45 2004 From: linux at defi.hu (Nyitrai Tamas) Date: Mon, 7 Jun 2004 13:01:45 +0200 (CEST) Subject: [sane-devel] scanimage: timeout Message-ID: Hello, I have got an Epson Perfection 1260 scanner. It always work right, but about a month ago it stopped working under Linux. I receive the following error messages: # scanimage -L usb 2-1: bulk timeout on ep2in usb 2-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 1 ret -110 usb 2-1: bulk timeout on ep2in usb 2-1: usbfs: USBDEVFS_BULK failed ep 0x82 len 4 ret -110 device `v4l:/dev/video0' is a Noname BT878 video (Pinnacle PCTV Stud virtual device device `plustek:libusb:002:002' is a Epson Perfection 1260/Photo USB flatbed scanner usb 2-1: usbfs: interface 0 claimed while 'scanimage' sets config #1 If I try to scan an image with quiteinsane, the I get usb 2-1: usbfs: interface 0 claimed while 'quiteinsane' sets config #1 I am running linux 2.6.7-rc2 at the moment but the situation is the same under 2.4.25 (with scanner.o inserted). After receiving these error message I have tried this scanner with an other machine with Windows98 running on it and it worked! What could cause the promlem? I have Debian/unstable installed. libsane 1.0.14-2 quiteinsane 0.10-4 sane 1.0.12-2 sane-utils 1.0.14-2 Thanking you in advance, Tamas From henning at meier-geinitz.de Mon Jun 7 12:14:46 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 7 Jun 2004 13:14:46 +0200 Subject: [sane-devel] scanimage: timeout In-Reply-To: References: Message-ID: <20040607111446.GC3351@meier-geinitz.de> Hi, On Mon, Jun 07, 2004 at 01:01:45PM +0200, Nyitrai Tamas wrote: > I have got an Epson Perfection 1260 scanner. It always work right, > but about a month ago it stopped working under Linux. Edit /etc/sane.d/dll.conf (or /usr/local/etc/sane.d/dll.conf) and comment out "epson". See the postings in this mailing list and the bug tracking systems for the reason. Bye, Henning From linux at defi.hu Mon Jun 7 12:25:45 2004 From: linux at defi.hu (Nyitrai Tamas) Date: Mon, 7 Jun 2004 13:25:45 +0200 (CEST) Subject: [sane-devel] scanimage: timeout In-Reply-To: <20040607111446.GC3351@meier-geinitz.de> References: <20040607111446.GC3351@meier-geinitz.de> Message-ID: On Mon, 7 Jun 2004, Henning Meier-Geinitz wrote: > > I have got an Epson Perfection 1260 scanner. It always work right, > > but about a month ago it stopped working under Linux. > Edit /etc/sane.d/dll.conf (or /usr/local/etc/sane.d/dll.conf) and > comment out "epson". See the postings in this mailing list and the bug > tracking systems for the reason. Thank you. That helped. Regards, Tamas From christophe.delivois at free.fr Mon Jun 7 22:20:38 2004 From: christophe.delivois at free.fr (Christophe de Livois) Date: Mon, 7 Jun 2004 23:20:38 +0200 Subject: [sane-devel] niash:libusb:002:005 failed: Device busy Message-ID: <1086643238.40c4dc2663514@imp3-q.free.fr> Hi, My HP scanjet 3400C scanner works well with a 2.4.2X kernel but I can't have it working on a 2.6.3 kernel (root or not, whatever the permisions of /proc/usb/002/005 are). Here are the messages that I get. Do you have any clues for me? chris at home:~$ scanimage scanimage: open of device niash:libusb:002:005 failed: Device busy chris at home:~$ scanimage -L device `niash:libusb:002:005' is a Hewlett-Packard ScanJet 3400C flatbed scanner chris at home:~$ strace scanimage 2>&1| grep -A5 -B5 busy close(38) = 0 munmap(0x40789000, 4096) = 0 open("/proc/bus/usb/002/005", O_RDWR) = 38 ioctl(38, USBDEVFS_SETCONFIGURATION, 0xbfffe704) = -1 ETIMEDOUT (Connection timed out) close(38) = 0 write(2, "scanimage: open of device niash:"..., 67scanimage: open of device niash:libusb:002:005 failed: Device busy ) = 67 munmap(0x401d5000, 1348000) = 0 munmap(0x4032d000, 503648) = 0 munmap(0x403af000, 75136) = 0 munmap(0x403a8000, 27524) = 0 chris at home:~$ lsmod | grep hcd ehci_hcd 22532 0 ohci_hcd 17412 0 usbcore 94044 5 ehci_hcd,hid,ohci_hcd Thanks a lot, Chris From fbakan at gmx.net Mon Jun 7 23:24:51 2004 From: fbakan at gmx.net (Franz Bakan) Date: Tue, 08 Jun 2004 00:24:51 +0200 (CEST) Subject: [sane-devel] OS/2 specific patch for sane-backends/backend/dll.c In-Reply-To: <20040605094907.GC19373@meier-geinitz.de> Message-ID: Hi, On Sat, 5 Jun 2004 11:49:07 +0200, Henning Meier-Geinitz wrote: >I've added the script to the tools directory. If you want to call it >automatically from backend/Makefile please send a patch for the >install traget that only executes when os2 is used. I'll see what I can do. >Please check if the script still works. It still works, only a cosmetic issue: Linebreaks now are (hex) 0D 0D 0A instead of 0D 0A (after getting the .cmd via cvs) >By the way, your website says: >"Optionally you can remove support for scanners you don't need to make >compiling faster and libsane.dll smaller. >For this purpose you have to modify >sane-backends-1.0.14/backend/Makefile.in and remove the scanners you >don't need from the list which starts with: >PRELOADABLE_BACKENDS = >" > >That doesn't work anymore. Just run configure like this: >BACKENDS="net mustek whatever" ./configure > >Or modify backend/Makefile after it was generated by configure. > >Also "--enable-translations" has been the default setting for some >time now. thanks for the info, I'll correct this when I update the pages. Bye, Franz From us at bernafon.ch Tue Jun 8 08:04:51 2004 From: us at bernafon.ch (Ullrich Sigwanz) Date: Tue, 8 Jun 2004 09:04:51 +0200 Subject: [sane-devel] niash:libusb:002:005 failed: Device busy Message-ID: <2ED257AB11E3D84B8526737E255288EE14FB4F@brnnt12.bernafon.ch> Hi Chris, You must compile the kernel to solve the problem. The NIASH00019 chips return an old string-length-descriptor and the kernel code cannot handle this symptom any longer, alas. I posted several times to the guys who wrote the linux usb code, to revert a change they did when trading the 2.4 code into 2.6 They are successfully refusing. There is a statement in the kernel-sources in the file drivers/usb/core/messages.c (about line 1200) which reads len=tbuf[0]; when you change this to len=255; your 3400C will work again . but as I sayed, the kernel must be compiled. Perhaps you can also mail to linux-usb-devel? The more, the better. Good luck Ullrich From henning at meier-geinitz.de Tue Jun 8 09:34:27 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 10:34:27 +0200 Subject: [sane-devel] OS/2 specific patch for sane-backends/backend/dll.c In-Reply-To: References: <20040605094907.GC19373@meier-geinitz.de> Message-ID: <20040608083427.GF3351@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 12:24:51AM +0200, Franz Bakan wrote: > It still works, only a cosmetic issue: > > Linebreaks now are (hex) > 0D 0D 0A > instead of > 0D 0A > > (after getting the .cmd via cvs) Hehe, CVS is not intelligent enough, emacs is too intelligent :-) I used your file with 0d 0a and edited it so emacs thought "ha, that's for DOS, I'll keep 0d 0a". I checked it into CVS and it has "0d 0a" in cvs. cvs on your local system knows that all this crap is unix (0a only) and converts every 0a to a 0d 0a even if it already is a 0d 0a. It's fixed in CVS now (0a only). Bye, Henning From henning at meier-geinitz.de Tue Jun 8 09:52:34 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 10:52:34 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> Message-ID: <20040608085234.GG3351@meier-geinitz.de> Hi, On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: > No seg fault on the saned end. Its happily running, waiting to finish > up. Xsane itself remains responsive. Ok. So you sent the logfile when both xsane and saned were still running? In this case the log file looks ok. Can you please retry and after the scan, close xsane? saned should also closes itsself. Thanks. > I can open menus, quit the app, > etc. Not knowing the xsane code, does it start a child process to > initiate scanning and maybe that process has crashed/hung? As far as I know it doesn't start a child process. However, it uses the gtk facilities to call the read function when data is available (something like select(), I don't remember the gtk function name. There has been trouble with that, but I think it looked differently (freezes of the scan or cancel process). > I'll look at the windows machine more. I can do a tcpdump capture of the > communication if that would be helpful. If there is an error that causes the scanner not to be detected anymore, I guess it must be visible in the saned or backend log. If that fails, we can look at tcp logs later. Bye, Henning From esoterican at freenet.de Tue Jun 8 11:05:06 2004 From: esoterican at freenet.de (esoterican at freenet.de) Date: Tue, 08 Jun 2004 12:05:06 +0200 Subject: [sane-devel] saned only run once Message-ID: An HTML attachment was scrubbed... URL: From gerhard at gjaeger.de Tue Jun 8 11:15:54 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Tue, 8 Jun 2004 12:15:54 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( Message-ID: <200406081215.54463.gerhard@gjaeger.de> Hi, I'm currenlty trying to add more frontend configurable options to the Plustek backend and have some problems with xsane now. There's a value whose range is from -1..63. At the default state, when starting xsane, it is properly displayed: -1. When changing once to i.e. 6 and changing it back to -1, xsane stores it as 0 and also displays it after the next startup as 0.. Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, the contraint_type is SANE_CONTRAINT_RANGE... The configfile of xsane shows, that this value is stored as 0 and not as -1... Any ideas? Gerhard From henning at meier-geinitz.de Tue Jun 8 11:20:55 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 12:20:55 +0200 Subject: [sane-devel] saned only run once In-Reply-To: References: Message-ID: <20040608102055.GA3504@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 12:05:06PM +0200, esoterican at freenet.de wrote: > hello list!
>
Could you please use plain text (not HTML) when writing to mailing lists? Thanks. > i'm using a microtek scanmaker 9600 xl. everything works fine... except one feature:
>
> when i want to use this scanner in the network and adjust everthing mentioned in
>
> http://www.penguin-breeder.org/sane/saned/
>
> it runs when i start "saned -d" only once and the exited. That's not a bug. -d is the debug mode. In fact, saned also exits after each connection if it's not in debug mode but is restarted by (x)inetd automatically. > i've tried the "cover" method mentioned in the article, but it doesn't work.
By cover method you mean using xinetd or inetd? Which one did you use? > the central error message is "[net] connect_dev: [0] failed to connect (Connection refused)".
> where's my fault?
Connection refused means that saned isn't running on the server or (x)inetd isn't configured correctly and therefore doesn't listen to the sane port (6566). You can try that yourself: "telnet server-ip-address 6566". If you get "connection refused" it's the above mentioned problem. Double-check your (x)inetd configuration and look for error messages in syslog. The "connection refused" comes from the kernel, not from saned. Also check that there is no firewall or kernel filter involved, that blocks port 6566. Bye, Henning From henning at meier-geinitz.de Tue Jun 8 11:22:32 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 12:22:32 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( In-Reply-To: <200406081215.54463.gerhard@gjaeger.de> References: <200406081215.54463.gerhard@gjaeger.de> Message-ID: <20040608102232.GB3504@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 12:15:54PM +0200, Gerhard Jaeger wrote: > I'm currenlty trying to add more frontend configurable options to the Plustek > backend and have some problems with xsane now. > There's a value whose range is from -1..63. At the default state, when > starting xsane, it is properly displayed: -1. > When changing once to i.e. 6 and changing it back to -1, xsane stores > it as 0 and also displays it after the next startup as 0.. > Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, > the contraint_type is SANE_CONTRAINT_RANGE... > The configfile of xsane shows, that this value is stored as 0 and not as -1... How does the definition of the constraint look like? Bye, Henning From gerhard at gjaeger.de Tue Jun 8 12:16:28 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Tue, 8 Jun 2004 13:16:28 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( In-Reply-To: <20040608102232.GB3504@meier-geinitz.de> References: <200406081215.54463.gerhard@gjaeger.de> <20040608102232.GB3504@meier-geinitz.de> Message-ID: <200406081316.28349.gerhard@gjaeger.de> On Tuesday 08 June 2004 12:22, Henning Meier-Geinitz wrote: > Hi, > > On Tue, Jun 08, 2004 at 12:15:54PM +0200, Gerhard Jaeger wrote: > > I'm currenlty trying to add more frontend configurable options to the > > Plustek backend and have some problems with xsane now. > > There's a value whose range is from -1..63. At the default state, when > > starting xsane, it is properly displayed: -1. > > When changing once to i.e. 6 and changing it back to -1, xsane stores > > it as 0 and also displays it after the next startup as 0.. > > Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, > > the contraint_type is SANE_CONTRAINT_RANGE... > > The configfile of xsane shows, that this value is stored as 0 and not as > > -1... > > How does the definition of the constraint look like? static const SANE_RANGE gain_range = { -1, 63, 1 }; should be okay - shouldn't it? Okay, some more investigations on that show, that when reducing the range from -1 to -2 and I set -2 in the dialogue, I will be internally set to -1... I also checked this with the quiteinsane backend, which seems to have no problems on that, so I thinks it's a bug in xsane... Ciao, Gerhard From philipp.neubeck at epost.de Tue Jun 8 13:58:12 2004 From: philipp.neubeck at epost.de (philipp.neubeck at epost.de) Date: Tue, 8 Jun 2004 14:58:12 +0200 Subject: [sane-devel] HP 7450C libusb problems In-Reply-To: References: <20040606141049.GB11281@inxservices.com> <20040606.164253.572697249.rene@rocklinux-consulting.de> <40C35283.1090507@cs.rug.nl> <20040606182552.GP19373@meier-geinitz.de> Message-ID: <20040608125812.GA3350@braveman.lan> Hi, perhaps this can help you, but i'm not sure if these errors are related: https://alioth.debian.org/tracker/index.php?func=detail&aid=300756&group_id=1308&atid=410366 bye Philipp Neubeck From Oliver.Rauch at Rauch-Domain.DE Tue Jun 8 14:44:52 2004 From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch) Date: 08 Jun 2004 15:44:52 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( In-Reply-To: <200406081215.54463.gerhard@gjaeger.de> References: <200406081215.54463.gerhard@gjaeger.de> Message-ID: <1086702292.2129.40.camel@Babylon7> Hello Gerhard. This is caused by a rounding in xsane-back-gtk.c line 2218 in function: static void xsane_back_gtk_value_update(...) case SANE_TYPE_INT: val = adj_data->value + 0.5; remove the "+ 0.5" and it should work. But I am not sure if this will cause other problems. I think there has been a reason for adding the "+ 0.5" Oliver Am Die, 2004-06-08 um 12.15 schrieb Gerhard Jaeger: > Hi, > > I'm currenlty trying to add more frontend configurable options to the Plustek > backend and have some problems with xsane now. > There's a value whose range is from -1..63. At the default state, when > starting xsane, it is properly displayed: -1. > When changing once to i.e. 6 and changing it back to -1, xsane stores > it as 0 and also displays it after the next startup as 0.. > Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, > the contraint_type is SANE_CONTRAINT_RANGE... > The configfile of xsane shows, that this value is stored as 0 and not as -1... > > Any ideas? > Gerhard > From kaplanam1 at comcast.net Tue Jun 8 16:21:27 2004 From: kaplanam1 at comcast.net (Allan Kaplan) Date: Tue, 08 Jun 2004 08:21:27 -0700 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? Message-ID: Greetings, Having recently purchased an NEC Petiscan unit, I've discovered the driver is not supported by MacOSX, and the Classic emulator won't hook up through the USB port. Please forgive my naivete, but is it possible to use SANE to fabricate one, and is there anyone out there who might be game to do it?? And if it is possible but no one's interested, any chance of getting some coaching? This is a fantastic little portable unit and it would be nice to be able to use it! Many thanks in advance, Allan From keith at claytons.org Tue Jun 8 16:31:51 2004 From: keith at claytons.org (Keith Clayton) Date: Tue, 08 Jun 2004 08:31:51 -0700 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040608085234.GG3351@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> Message-ID: <1086708706.641.4.camel@yoda> On Tue, 2004-06-08 at 10:52 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: > > No seg fault on the saned end. Its happily running, waiting to finish > > up. Xsane itself remains responsive. > > Ok. So you sent the logfile when both xsane and saned were still > running? In this case the log file looks ok. Can you please retry and > after the scan, close xsane? saned should also closes itsself. Thanks. I would expect xsane to close the fd used to access the scanner though. Anyway, generated a log with a scan followed by closing xsane. saned exited as expected. As you'll see in the log, saned quits however, I never see any entry regarding the closing of the active fd. gzipped log is attached. thanks for all your work . . looks like you've been busy as of late 8^( Keith > > I can open menus, quit the app, > > etc. Not knowing the xsane code, does it start a child process to > > initiate scanning and maybe that process has crashed/hung? > > As far as I know it doesn't start a child process. However, it uses > the gtk facilities to call the read function when data is available > (something like select(), I don't remember the gtk function name. > There has been trouble with that, but I think it looked differently > (freezes of the scan or cancel process). > > > I'll look at the windows machine more. I can do a tcpdump capture of the > > communication if that would be helpful. > > If there is an error that causes the scanner not to be detected > anymore, I guess it must be visible in the saned or backend log. If > that fails, we can look at tcp logs later. > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org -------------- next part -------------- A non-text attachment was scrubbed... Name: remote_scan_quit.log.gz Type: application/x-gzip Size: 4400 bytes Desc: not available URL: From henning at meier-geinitz.de Tue Jun 8 16:31:27 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 17:31:27 +0200 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? In-Reply-To: References: Message-ID: <20040608153127.GA7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 08:21:27AM -0700, Allan Kaplan wrote: > Having recently purchased an NEC Petiscan unit, I've discovered the driver > is not supported by MacOSX, and the Classic emulator won't hook up through > the USB port. Please forgive my naivete, but is it possible to use SANE to > fabricate one, Uaually it's possible to write a backend for any scanner. > and is there anyone out there who might be game to do it?? I guess that would be you :-) > And if it is possible but no one's interested, any chance of getting some > coaching? Just ask this list, if you have specific questions. Some docu about backend writing is here: http://www.sane-project.org/contrib.html Could you please send us more information about this device so we can add it to our lists? E.g. if "NEC Petiscan" is the full name and the output of "sane-find-scanner -v -v" when the scanner is connceted to your computer? Bye, Henning From henning at meier-geinitz.de Tue Jun 8 16:40:42 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 17:40:42 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086708706.641.4.camel@yoda> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> Message-ID: <20040608154042.GB7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 08:31:51AM -0700, Keith Clayton wrote: > On Tue, 2004-06-08 at 10:52 +0200, Henning Meier-Geinitz wrote: > > Hi, > > > > On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: > > > No seg fault on the saned end. Its happily running, waiting to finish > > > up. Xsane itself remains responsive. > > > > Ok. So you sent the logfile when both xsane and saned were still > > running? In this case the log file looks ok. Can you please retry and > > after the scan, close xsane? saned should also closes itsself. Thanks. > > I would expect xsane to close the fd used to access the scanner though. sane_close() will be called when xsane is closed. Some backends close the device file (or use the equivalent call to libusb) after the scan has finished but not all. > Anyway, generated a log with a scan followed by closing xsane. saned > exited as expected. As you'll see in the log, saned quits however, I > never see any entry regarding the closing of the active fd. Please try again with SANE_DEBUG_PLUSTEK=255. saned doesn't print messages about closing but from your log I expect that the devices are actually closed. The plustek messages should show that. In that case we must have a closer look at the communication. > thanks for all your work . . looks like you've been busy as of late 8^( Fortunately I've two weeks of holidays and a lot of that time is used for SANE :-) Bye, Henning From keith at claytons.org Tue Jun 8 16:55:55 2004 From: keith at claytons.org (Keith Clayton) Date: Tue, 08 Jun 2004 08:55:55 -0700 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040608154042.GB7920@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> <20040608154042.GB7920@meier-geinitz.de> Message-ID: <1086710152.643.7.camel@yoda> Did use SANE_DEBUG_PLUSTEK=255 when starting saned. Cmd line was SANE_DEBUG_PLUSTEK=255 saned -d255 1>&2 2>remote_scan_quit.log So in that regard, was quite strange to not see any closing of the scanner's fd. Cheers, Keith PS: So your saying debugging mailing list issues is a holiday ?!? Heh, heh On Tue, 2004-06-08 at 17:40 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Tue, Jun 08, 2004 at 08:31:51AM -0700, Keith Clayton wrote: > > On Tue, 2004-06-08 at 10:52 +0200, Henning Meier-Geinitz wrote: > > > Hi, > > > > > > On Sun, Jun 06, 2004 at 10:27:57AM -0700, Keith Clayton wrote: > > > > No seg fault on the saned end. Its happily running, waiting to finish > > > > up. Xsane itself remains responsive. > > > > > > Ok. So you sent the logfile when both xsane and saned were still > > > running? In this case the log file looks ok. Can you please retry and > > > after the scan, close xsane? saned should also closes itsself. Thanks. > > > > I would expect xsane to close the fd used to access the scanner though. > > sane_close() will be called when xsane is closed. Some backends close > the device file (or use the equivalent call to libusb) after the scan > has finished but not all. > > > Anyway, generated a log with a scan followed by closing xsane. saned > > exited as expected. As you'll see in the log, saned quits however, I > > never see any entry regarding the closing of the active fd. > > Please try again with SANE_DEBUG_PLUSTEK=255. saned doesn't print > messages about closing but from your log I expect that the devices are > actually closed. The plustek messages should show that. In that case > we must have a closer look at the communication. > > > thanks for all your work . . looks like you've been busy as of late 8^( > > Fortunately I've two weeks of holidays and a lot of that time is used > for SANE :-) > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org From henning at meier-geinitz.de Tue Jun 8 17:01:40 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 18:01:40 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086710152.643.7.camel@yoda> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> <20040608154042.GB7920@meier-geinitz.de> <1086710152.643.7.camel@yoda> Message-ID: <20040608160140.GE7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 08:55:55AM -0700, Keith Clayton wrote: > Did use SANE_DEBUG_PLUSTEK=255 when starting saned. Cmd line was > > SANE_DEBUG_PLUSTEK=255 saned -d255 1>&2 2>remote_scan_quit.log > > > So in that regard, was quite strange to not see any closing of the > scanner's fd. Your first two logs contained the plustek messages. However, the log you have just sent didn't contain any plustek messages. So maybe the command line had a typo? Bye, Henning From insane at piments.com Tue Jun 8 18:42:04 2004 From: insane at piments.com (insane at piments.com) Date: Tue, 08 Jun 2004 19:42:04 +0200 Subject: [sane-devel] niash:libusb:002:005 failed: Device busy In-Reply-To: <2ED257AB11E3D84B8526737E255288EE14FB4F@brnnt12.bernafon.ch> References: <2ED257AB11E3D84B8526737E255288EE14FB4F@brnnt12.bernafon.ch> Message-ID: Nice post. Sadly this does not seem to help for all scanners. I did the change you suggested , recomp, reboot and my scanner locks up just the same. Shame it did not do it for canoscan. I would suggest you look into the code a bit more seriously before suggesting it as a fix to be integrated into the kernel. You cant just hack code like that without looking at the consenquences. At least not if you expect to have a stable kernel. I'd rather have a scanner the dont scan than an OS like win9x. Get the point? Maybe that is why devs at that have not done it yet. The evenual code fix will need to be more thorough. Regards. On Tue, 8 Jun 2004 09:04:51 +0200, Ullrich Sigwanz wrote: > Hi Chris, > > You must compile the kernel to solve the problem. > The NIASH00019 chips return an old string-length-descriptor and the > kernel > code cannot handle this > symptom any longer, alas. > > I posted several times to the guys who wrote the linux usb code, > to revert a change they did when trading the 2.4 code into 2.6 > They are successfully refusing. > > There is a statement in the kernel-sources in the file > drivers/usb/core/messages.c (about line 1200) > which reads > > len=tbuf[0]; > > when you change this to > > len=255; > > your 3400C will work again . > > but as I sayed, the kernel must be compiled. > > Perhaps you can also mail to linux-usb-devel? The more, the better. > > Good luck > > Ullrich > > -- Using M2, Opera's e-mail client: on Gentoo Linux From henning at meier-geinitz.de Tue Jun 8 20:34:00 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 8 Jun 2004 21:34:00 +0200 Subject: [sane-devel] niash:libusb:002:005 failed: Device busy In-Reply-To: References: <2ED257AB11E3D84B8526737E255288EE14FB4F@brnnt12.bernafon.ch> Message-ID: <20040608193400.GG7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 07:42:04PM +0200, insane at piments.com wrote: > Nice post. > > Sadly this does not seem to help for all scanners. You can't fix a problem that doesn't exist. As most scanners don't return wrong lengths of string descriptors, that workaround is just not necessary for most scanners. > I did the change you suggested , recomp, reboot and my scanner locks up > just the same. He suggested that workaround for niash users. > Shame it did not do it for canoscan. I thought you got timeouts, not EBUSY? > I would suggest you look into the code a bit more seriously before > suggesting it as a fix to be integrated into the kernel. You cant just > hack code like that without looking at the consenquences. At least not if > you expect to have a stable kernel. That's true. As the kernel has conatined the code that is proposed here earlier, it doesn't seem to be that far off. Maybe a more intelligent way is needed, e.g. inspect the contents of tbuf[0] and if it's invalid, use 255. > Maybe that is why devs at that have not done it yet. The evenual code fix > will need to be more thorough. As far as I can see the proposed code does actually fix the problem for niash users. It may not be good enough for general use but that shouldn't stop niash users from trying it. Bye, Henning From erik at epo.dk Wed Jun 9 00:26:58 2004 From: erik at epo.dk (Erik P. Olsen) Date: Wed, 09 Jun 2004 01:26:58 +0200 Subject: [sane-devel] Howto update sane and xsane? Message-ID: <1086737218.8819.13.camel@epo.dk> I am running FC2 and want to upgrade xsane and sane-?ends to latest level, but being new to linux I am unsure of how I should do this. Since they exist as rpm installed packages should they then be removed from the system before installation or is it safe to let them stay and install the new levels on top of them? The latest levels do not yet come in rpm format so I assume that if I let them stay then the up2date process may later catch up if an even newer level comes out in rpm format - or is this a false assumption? -- Regards, Erik P. Olsen From kaplanam1 at comcast.net Wed Jun 9 06:17:36 2004 From: kaplanam1 at comcast.net (Allan Kaplan) Date: Tue, 08 Jun 2004 22:17:36 -0700 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? Message-ID: Subject: Re: [sane-devel] NEC Petiscan driver for MacOSX possible? Hi Henning, Thanks for your response. Yes, NEC Petiscan is the name of the scanner. As far as "sane-find-scanner" goes, am I to assume that I have to be running Linux, or can I use the Terminal program on the Mac and do this in Unix? And can I further assume that Mattias Ellert's MacOSX downloads will not be applicable in this case? Thanks, Allan > Hi, > > On Tue, Jun 08, 2004 at 08:21:27AM -0700, Allan Kaplan wrote: >> Having recently purchased an NEC Petiscan unit, I've discovered the driver >> is not supported by MacOSX, and the Classic emulator won't hook up through >> the USB port. Please forgive my naivete, but is it possible to use SANE to >> fabricate one, > > Uaually it's possible to write a backend for any scanner. > >> and is there anyone out there who might be game to do it?? > > I guess that would be you :-) > >> And if it is possible but no one's interested, any chance of getting some >> coaching? > > Just ask this list, if you have specific questions. Some docu about > backend writing is here: http://www.sane-project.org/contrib.html > > Could you please send us more information about this device so we can > add it to our lists? E.g. if "NEC Petiscan" is the full name and the > output of "sane-find-scanner -v -v" when the scanner is connceted to > your computer? > > Bye, > Henning From henning at meier-geinitz.de Wed Jun 9 07:42:08 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 08:42:08 +0200 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? In-Reply-To: References: Message-ID: <20040609064208.GJ7920@meier-geinitz.de> Hi, On Tue, Jun 08, 2004 at 10:17:36PM -0700, Allan Kaplan wrote: > As far as "sane-find-scanner" goes, am I to assume that I have to be running > Linux, or can I use the Terminal program on the Mac and do this in Unix? MacOS X is ok. Any system that runs SANE should work. > And can I further assume that Mattias Ellert's MacOSX downloads will not be > applicable in this case? If they conatin sane-find-scanner, they should work. Bye, Henning From henning at meier-geinitz.de Wed Jun 9 08:02:33 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 09:02:33 +0200 Subject: [sane-devel] Howto update sane and xsane? In-Reply-To: <1086737218.8819.13.camel@epo.dk> References: <1086737218.8819.13.camel@epo.dk> Message-ID: <20040609070233.GK7920@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 01:26:58AM +0200, Erik P. Olsen wrote: > I am running FC2 and want to upgrade xsane and sane-?ends to latest > level, but being new to linux I am unsure of how I should do this. > > Since they exist as rpm installed packages should they then be removed > from the system before installation or is it safe to let them stay and > install the new levels on top of them? Maybe you can use the RPMs from http://rpmfind.net/linux/rpm2html/search.php?query=sane-backends ? Even if you can't, building your own RPM based on the 1.0.14 source RPM is probably the cleanest way. > The latest levels do not yet come in rpm format so I assume that if I > let them stay then the up2date process may later catch up if an even > newer level comes out in rpm format - or is this a false assumption? If you do not want or can't make an RPM yourself there are some other options: 1) Remove the existing SANE RPMs. You may get trouble trying this as other software may depend on them. You can try to force rpm to remove the packages that will break dependencies and you may get trouble later. 2) Overwrite the current installation. Linux distributions usually put their software into /usr, so "configure --prefix=/usr --sysconfdir=/etc" should work (check the syntax). This isn't a clean solution either and your sane installation may be destroyed when your distribution is updated. 3) Ignore the current installation and install SANE in /usr/local/. That's the default. It works but graphical frontends generally use the old installation in /usr, not the new one in /usr/local. /usr/local/bin/scanimage knows where to find the new libs, however. You can try some tricks to use the new libs, e.g. change the search order in /etc/ld.so.conf, use "LD_PRELOAD=/usr/local/lib/libcane.so xsane" or link /usr/lib/libsane.so to /usr/local/lib/libsane.so. Bye, Henning From Francois.Patte at math-info.univ-paris5.fr Wed Jun 9 09:22:48 2004 From: Francois.Patte at math-info.univ-paris5.fr (=?iso-8859-1?b?RnJhbudvaXM=?= Patte) Date: Wed, 9 Jun 2004 10:22:48 +0200 Subject: [sane-devel] How to configure sane, xsane, etc. In-Reply-To: <20040609070233.GK7920@meier-geinitz.de> References: <1086737218.8819.13.camel@epo.dk> <20040609070233.GK7920@meier-geinitz.de> Message-ID: <1086769368.40c6c8d8aaf7d@www.math-info.univ-paris5.fr> Bonjour, I am facing a big problem with xsane from fedora C1. (xsane-0.91-1): 1- I have a scanner Nikon LS-2000. The first person who ran xsane was not root and it now impossible to change the owner and right of the device /dev/sg0. This device has been set with owner didier and group root with permissions 600 and whatever root can do to change this is destroyed by the next use of xsane: ownership, group and permission are reset as previously defined!!!! So nobody but didier can use xsane and the scanner! man sane-scsi : When using a SCSI scanner, ensure that the access permission for the generic SCSI device is 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 generic SCSI device /dev/sg0, then the following two commands would set the permission correctly: $ chgrp scanner /dev/sg0 $ chmod 660 /dev/sg0 This is now impossible to do! Where are the configuration files responsible for this awful behavior? 2- Even for didier the use of xsane is not easy: every time he asks for xsane he has to accept the license and to wait about 10/15 minutes for the research of peripherics.... And, worse, he has to wait also if he wants to use gimp: gimp hangs on xsane plug-ins.... I would like to understand how this can happen and how to corrct this windows like behavior: unix systems were done for many users, it is more and more difficult to use them like this. Thank you for attention. -- Fran?ois Patte Inde : Ecole fran?aise d'Extr?me-Orient Deccan College Pune 411006 T?l : (00 91) (0) 20 26 69 39 04 France : Universit? Ren? Descartes - Paris 5 UFR de math?matiques et informatique http://www.math-info.univ-paris5.fr/~patte From henning at meier-geinitz.de Wed Jun 9 10:49:22 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 11:49:22 +0200 Subject: [sane-devel] Re: How to configure sane, xsane, etc. Message-ID: <20040609094922.GN7920@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 10:08:32AM +0200, Fran?ois Patte wrote: > I am facing a big problem with xsane from fedora C1. (xsane-0.91-1): > > 1- I have a scanner Nikon LS-2000. The first person who ran xsane was not root > and it now impossible to change the owner and right of the device /dev/sg0. > > This device has been set with owner didier and group root with permissions 600 > and whatever root can do to change this is destroyed by the next use of xsane: > ownership, group and permission are reset as previously defined!!!! So nobody > but didier can use xsane and the scanner! xsane doesn't change any access permissions. In fact it doesn't even know which device file to use. The sane libraries ("sane-backends") themselves also don't touch permissions. So your problem is most probably caused by some automatic procedure introduced by Fedora. I remember that there is some stuff to change permissions based on who logs into the computer locally. > man sane-scsi : > > When using a SCSI scanner, ensure that the access permission for the > generic SCSI device is 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 generic SCSI device /dev/sg0, then the following two commands would > set the permission correctly: > > $ chgrp scanner /dev/sg0 > $ chmod 660 /dev/sg0 > > This is now impossible to do! Where are the configuration files responsible for > this awful behavior? It works quite fine, I'm doing it on this system. Really looks like a Fedora problem. Better look at their docs or ask on their mailing lists for help. > 2- Even for didier the use of xsane is not easy: every time he asks for xsane he > has to accept the license xsane asks for accepting the liability exclusion only on the first start (and when xsane is updated to a newer version). So if that happens more than once, maybe the directoriy ~/.sane/xsane can't be written? > and to wait about 10/15 minutes for the research of > peripherics.... That shouldn't happen. Which version of sane do you use (scanimage --version)? The scan takes about 1 to5 seconds at least with newer versions of SANE. As a workaround, you can disable everything but "coolscan" in /etc/sane.d/dll.conf. > And, worse, he has to wait also if he wants to use gimp: gimp hangs > on xsane plug-ins.... If you don't need the xsane gimp plugin, remove the link to xsane. > I would like to understand how this can happen and how to corrct this windows > like behavior: unix systems were done for many users, it is more and more > difficult to use them like this. The behaviour you describe isn't the normal SANE behaviour. 1) is not cause by SANE and 2) is caused by the kernel trying to load drivers for hardware that doesn't exist. That shouldn't happen with current sane versions anymore. Bye, Henning From David at phenix.fr Wed Jun 9 12:54:57 2004 From: David at phenix.fr (David Neary) Date: Wed, 9 Jun 2004 13:54:57 +0200 Subject: [sane-devel] JSane Message-ID: Hi all, I know that some people were asking about a Java SANE API recently. I did some work before 1.0.14 on getting it at least compiling with at least a Sun SDK, and have since been quite happily using these JNI bindings. There are still some bugs in here, notably for lineart mode, and I have been unashamedly messing about with stuff to make it work just for me, for one particular task, so it's probably not pretty. But perhaps people who need something now will be happy with it. This is simply a tar of the japi directory after I did a make clean. I also have a dllmain.c and a project file for making a sanej.dll for Windows, if anyone would like those. This is more or less untested, and ymmv. I also have a tarball of the javadocs, but I didn't do anything particular to generate them except run javadoc so there's no real point in sending those to the list. Cheers, Dave. -- David Neary Phenix Engineering 110 ave Jean Jaures, 69007 Lyon -------------- next part -------------- A non-text attachment was scrubbed... Name: jsane.tar.bz2 Type: application/octet-stream Size: 22921 bytes Desc: not available URL: From David at phenix.fr Wed Jun 9 13:10:52 2004 From: David at phenix.fr (David Neary) Date: Wed, 9 Jun 2004 14:10:52 +0200 Subject: [sane-devel] Re: How to configure sane, xsane, etc. Message-ID: Hi Fran?ois, Fran?ois Patte said: > I am facing a big problem with xsane from fedora C1. (xsane-0.91-1): > > 1- I have a scanner Nikon LS-2000. The first person who ran > xsane was not= > root > and it now impossible to change the owner and right of the > device /dev/sg0. I have just come across more or less the same problem, and have tracked down the answer. It seems to be a problem with the default PAM set-up on redhat. When you start a console, you can use PAM to control access to system resources (such as a flash card, or scanner, etc) for the duration of the session, and on finishing the session have the permissions revert to sane defaults. The file which configures how this is done is in /etc/security/console.perms. You should look for a line which says something like 0600 0600 root This says that if a user logged on to a console tries to access a file in the scanner class, the permissions on the file will be set to 0600, with his ownership, and when he's finished they'll revert to 0600 and root ownership (at least, I think that's what it means, I don't understand it too well). If you remove this line, restart pam, and change the permissions on /dev/sg0 to what you want, they should stick. Cheers, Dave. -- David Neary Phenix Engineering 110 ave Jean Jaures, 69007 Lyon From yannig.perre at ext.anpe.fr Wed Jun 9 13:40:08 2004 From: yannig.perre at ext.anpe.fr (PERRE yannig (DSI NOISIEL)) Date: Wed, 9 Jun 2004 14:40:08 +0200 Subject: [sane-devel] Re: How to configure sane, xsane, etc. Message-ID: Hi, I think, you'd better try to change the permission for this device in the /etc/security/console.perms file. Change your previous scanner line with this : 0660 0660 root.scan_group Then add user to scan_group group (or whatever_group_you_want) to enable access to the scanner. Also, you can look at the hotplug daemon. For an USB scanner, you need to change /etc/hotplug/usb/usbscanner script. I guess, you can look at /etc/hotplug/scsi/(.*)scanner for a scsi scanner. Cheers, Yannig -----Message d'origine----- De : sane-devel-admin at lists.alioth.debian.org [mailto:sane-devel-admin at lists.alioth.debian.org]De la part de David Neary Envoy? : mercredi 9 juin 2004 14:11 ? : 'sane-devel at lists.alioth.debian.org' Objet : [sane-devel] Re: How to configure sane, xsane, etc. Hi Fran?ois, Fran?ois Patte said: > I am facing a big problem with xsane from fedora C1. (xsane-0.91-1): > > 1- I have a scanner Nikon LS-2000. The first person who ran > xsane was not= > root > and it now impossible to change the owner and right of the > device /dev/sg0. I have just come across more or less the same problem, and have tracked down the answer. It seems to be a problem with the default PAM set-up on redhat. When you start a console, you can use PAM to control access to system resources (such as a flash card, or scanner, etc) for the duration of the session, and on finishing the session have the permissions revert to sane defaults. The file which configures how this is done is in /etc/security/console.perms. You should look for a line which says something like 0600 0600 root This says that if a user logged on to a console tries to access a file in the scanner class, the permissions on the file will be set to 0600, with his ownership, and when he's finished they'll revert to 0600 and root ownership (at least, I think that's what it means, I don't understand it too well). If you remove this line, restart pam, and change the permissions on /dev/sg0 to what you want, they should stick. Cheers, Dave. -- David Neary Phenix Engineering 110 ave Jean Jaures, 69007 Lyon -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-request at lists.alioth.debian.org From esoterican at freenet.de Wed Jun 9 13:54:15 2004 From: esoterican at freenet.de (esoterican at freenet.de) Date: Wed, 09 Jun 2004 14:54:15 +0200 Subject: [sane-devel] saned only run once Message-ID: An HTML attachment was scrubbed... URL: From gilles at ffii.org Wed Jun 9 14:40:39 2004 From: gilles at ffii.org (Gilles Sadowski) Date: Wed, 9 Jun 2004 15:40:39 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040601215656.GA3524@ffii.org> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> <20040601215656.GA3524@ffii.org> Message-ID: <20040609134039.GA3769@ffii.org> Hello. So, what is the final word about this "timeout" problem? Is it caused by the "uhci" driver? The one I must use, according to the following: Jun 9 13:06:27 dawn kernel: usb usb2: Product: VIA Technologies, Inc. USB (#2) Jun 9 13:06:27 dawn kernel: usb usb2: Manufacturer: Linux 2.6.5+g6 uhci_hcd Jun 9 13:06:27 dawn kernel: usb usb2: SerialNumber: 0000:00:04.3 Jun 9 13:06:27 dawn kernel: hub 2-0:1.0: USB hub found Jun 9 13:06:27 dawn kernel: hub 2-0:1.0: 2 ports detected Jun 9 13:06:27 dawn kernel: usb 1-1: new full speed USB device using address 2 Jun 9 13:06:27 dawn kernel: gameport: pci0000:00:0a.1 speed 1242 kHz Jun 9 13:06:27 dawn kernel: usb 1-1: Product: Hewlett Packard ScanJet 5300C/5370C Jun 9 13:06:27 dawn kernel: usb 1-1: Manufacturer: Hewlett Packard Jun 9 13:06:27 dawn kernel: usb 1-1: SerialNumber: 0000000000000000 Best regards, Gilles From henning at meier-geinitz.de Wed Jun 9 16:18:18 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 17:18:18 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040609134039.GA3769@ffii.org> References: <20040601111441.GA8138@ffii.org> <20040601135818.GC12076@meier-geinitz.de> <20040601.204323.466679361.rene@rocklinux-consulting.de> <20040601215656.GA3524@ffii.org> <20040609134039.GA3769@ffii.org> Message-ID: <20040609151818.GO7920@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 03:40:39PM +0200, Gilles Sadowski wrote: > So, what is the final word about this "timeout" problem? The reason is unknown as of now. It's not that easy as these timeouts may have several reason. Every wrong command that's sent to the scanner can cause timeouts. It doesn't seem to be a general SANE problem. I've tried several scanners on Linux 2.6.7-rc2 with UHCI, OHCI and EHCI USB host controllers and can't reproduce the timeouts. So someone who does see the timeouts needs to investigate the details. E.g. if there is a specific SANE version that does work without trouble. If that's the case, identify the change that causes problems. If it depends on kernel versions, identify the kernel version that started showing those timeouts. I'll try to summarize what I've read here and in the bug tracking system: Timeouts: - HP5370C (avision) on UHCI VIA, Linux 2.6.5 - HP7450C (avision), sane-backends 1.0.14 (also tried latest avision code), Linux 2.6.5 - HP7400 (avision) on UHCI (Intel Corp. 82371AB/EB/MB PIIX4 USB) Asus board, sane-backends 1.0.14, Linux 2.6.3, 2.6.5, 2.6.6 and 2.6.7-rc2-bk7 - HP7450C (avision), there was a hint about the hpusbscsi driver making trouble in that case - Epson Perfection 1670 (snapscan) on UHCI VIA, sane-backends 1.0.14, Linux 2.6.5-mm2 No timeouts: - Several Mustek+Plustek scanners (mustek_usb, plustek, gt68xx), sane-backends 1.0.14, on OHCI + UHCI (VIA PCI card) on Linux 2.6.7-rc2 and Linux 2.4.26 - Avision scanners, on OHCI, sane-backends 1.0.14 + latest avison code on Linux 2.6.3 (UltraSparc +iBook) Typical log: Jun 6 19:06:11 localhost kernel: usb 1-1: bulk timeout on ep3in Jun 6 19:06:11 localhost kernel: usb 1-1: usbfs: USBDEVFS_BULK failed ep 0x83 len 4096 ret -110 An unrelated bug showed the same timeouts: - Epson Perfection 1260 (plustek), sane-backends-1.0.14, on Linux 2.6.7-rc2 and 2.4.25 with scanner.o(!) Reason: the epson backend tries to talk to this scanner There are some other reports about USB trouble but it's unclear if they are related. All these bug reports are newer than 6 weeks. So it's either the new SANE, kernel, libusb release or some other part of software that got changed recently. All but one reports are about the avision backend. Maybe the trouble is located there and the Epson 1670 problem has a different reason? Bye, Henning From misc at tomweissmann.org Wed Jun 9 16:48:51 2004 From: misc at tomweissmann.org (Tom Schutzer-Weissmann) Date: Wed, 9 Jun 2004 16:48:51 +0100 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. Message-ID: <20040609164851.1fcddb78@expensive> I had problems using the Epkowa libraries (libsane-epkowa) and the iscan frontend with my usb scanner in kernel 2.6. The scanner was closed after each operation. Once closed, nothing could be read from it, and I got lots of BULK TIMEOUTs, although there were no errors when the device was reopened. By modifying the code so that usb_reset() was always called before usb_release_interface() and usb_close(), I solved the problem. For libusb developers, my question is, should this be the case? There is nothing in the API docs to indicate that it's necessary - perhaps it is self-evident? Farideh - in the belief that you are a point of contact for Epson developers - could you make them aware of this issue, if they aren't already. I think this is relevant to SANE because although I had some success scanning with xsane and xscanimage, using the libsane-epson libraries, I still got timeouts if I closed, say, xsane, and then restarted it - for lack of a usb_reset() I believe. Apologies if this is old news. Tom SW From insane at piments.com Wed Jun 9 19:15:01 2004 From: insane at piments.com (insane at piments.com) Date: Wed, 09 Jun 2004 20:15:01 +0200 Subject: [sane-devel] Fwd: [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ In-Reply-To: References: Message-ID: Hi Henning, here's a copy of the email I sent to the maintainer of the fb630u backend. It gives the full debug output, the last lines where it blocks being the same as those I already posted on this list. I got no reply from Nathan so I have nothing more to contriute from him. As you can see communication seems to go quite well at first but then gets stuck in a loop with no apparent timeout. regards, Peter. ------- Forwarded message ------- From: peter at piments.com To: "Nathan Rutman" Subject: [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ Date: Sun, 23 May 2004 22:27:03 +0200 Hi, here is the full debug output from scanimage. The final line just repeats until I kill the process or unplug the scanner. This should give you a good idea of what is happening. I'm an active member of forums.gentoo.org and there seem to be quite a lot of posts with very similar pbs. So once I get it working will post the solution. Thanks again for any help or suggestions. Regards, Peter. bash-2.05b# !! SANE_DEBUG_CANON630U=255 scanimage -d canon630u [sanei_debug] Setting debug level of canon630u to 255. [canon630u] sane_init: version_code != 0, authorize != 0 [canon630u] sane_init: SANE Canon630u backend version 1.0.1 from sane-backends 1.0.14-cvs [canon630u] reading configure file canon630u.conf [canon630u] attach_matching_devices(usb 0x04a9 0x2204) [canon630u] attach_scanner: libusb:001:012 [canon630u] attach_scanner: opening libusb:001:012 [canon630u] CANON_open_device: `libusb:001:012' [canon630u] CANON_close_device: [canon630u] finished reading configure file [canon630u] sane_open [canon630u] sane_open: no devicename, opening first device [canon630u] CANON_open_device: `libusb:001:012' [canon630u] sane_control_option: handle=0x8056d60, opt=0, act=0, val=0xbfffe780, info=(nil) [canon630u] sane_control_option: handle=0x8056d60, opt=0, act=0, val=0xbfffe6e8, info=(nil) [canon630u] sane_get_option_descriptor: option = 0 [canon630u] sane_get_option_descriptor: option = 1 [canon630u] sane_get_option_descriptor: option = 2 [canon630u] sane_get_option_descriptor: option = 3 [canon630u] sane_get_option_descriptor: option = 4 [canon630u] sane_get_option_descriptor: option = 5 [canon630u] sane_get_option_descriptor: option = 6 [canon630u] sane_get_option_descriptor: option = 7 [canon630u] sane_control_option: handle=0x8056d60, opt=7, act=0, val=0x80544b8, info=(nil) [canon630u] sane_get_option_descriptor: option = 8 [canon630u] sane_control_option: handle=0x8056d60, opt=8, act=0, val=0x80544bc, info=(nil) [canon630u] sane_control_option: handle=0x8056d60, opt=5, act=0, val=0xbfffe6e4, info=(nil) [canon630u] sane_control_option: handle=0x8056d60, opt=6, act=0, val=0xbfffe6e4, info=(nil) [canon630u] sane_control_option: handle=0x8056d60, opt=5, act=0, val=0xbfffe77c, info=(nil) [canon630u] sane_get_option_descriptor: option = 7 [canon630u] sane_control_option: handle=0x8056d60, opt=7, act=1, val=0xbfffe778, info=0xbfffe774 [canon630u] sane_control_option: handle=0x8056d60, opt=6, act=0, val=0xbfffe77c, info=(nil) [canon630u] sane_get_option_descriptor: option = 8 [canon630u] sane_control_option: handle=0x8056d60, opt=8, act=1, val=0xbfffe778, info=0xbfffe774 [canon630u] sane_start [canon630u] CANON_set_scan_parameters: [canon630u] cal = 0 [canon630u] gray = 0 (ignored) [canon630u] res = 75 [canon630u] gain = 1 [canon630u] gamma = 1.599991 [canon630u] in 600dpi pixels: [canon630u] left = 0, top = 0 [canon630u] right = 5099, bottom = 6999 [canon630u] CANON_start_scan called [canon630u] init query: 4 [canon630u] write_byte(fd, 0x42, 0x06); [canon630u] write_byte(fd, 0x0b, 0x0d); [canon630u] write_byte(fd, 0x0c, 0x4c); [canon630u] write_byte(fd, 0x0d, 0x2f); [canon630u] read_byte(fd, 0x0b, &result); /* got 0d */ [canon630u] read_byte(fd, 0x0c, &result); /* got 4c */ [canon630u] read_byte(fd, 0x0d, &result); /* got 2f */ [canon630u] write_byte(fd, 0x70, 0x73); [canon630u] init post-reset: 4 [canon630u] Calibrating [canon630u] read_byte(fd, 0x69, &result); /* got 02 */ [canon630u] write_byte(fd, 0x42, 0x06); [canon630u] multi write 32 [canon630u] 0008:04[canon630u] write_byte(fd, 0x08, 0x04); [canon630u] 0009:1a[canon630u] write_byte(fd, 0x09, 0x1a); [canon630u] 000a:00[canon630u] write_byte(fd, 0x0a, 0x00); [canon630u] 000b:0d[canon630u] write_byte(fd, 0x0b, 0x0d); [canon630u] 000c:4c[canon630u] write_byte(fd, 0x0c, 0x4c); [canon630u] 000d:2f[canon630u] write_byte(fd, 0x0d, 0x2f); [canon630u] 000e:00[canon630u] write_byte(fd, 0x0e, 0x00); [canon630u] 000f:01[canon630u] write_byte(fd, 0x0f, 0x01); [canon630u] 0010:07[canon630u] write_byte(fd, 0x10, 0x07); [canon630u] 0011:04[canon630u] write_byte(fd, 0x11, 0x04); [canon630u] 0012:05[canon630u] write_byte(fd, 0x12, 0x05); [canon630u] 0013:06[canon630u] write_byte(fd, 0x13, 0x06); [canon630u] 0014:07[canon630u] write_byte(fd, 0x14, 0x07); [canon630u] 0015:00[canon630u] write_byte(fd, 0x15, 0x00); [canon630u] 0016:00[canon630u] write_byte(fd, 0x16, 0x00); [canon630u] 0017:00[canon630u] write_byte(fd, 0x17, 0x00); [canon630u] 0018:03[canon630u] write_byte(fd, 0x18, 0x03); [canon630u] 0019:00[canon630u] write_byte(fd, 0x19, 0x00); [canon630u] 001a:00[canon630u] write_byte(fd, 0x1a, 0x00); [canon630u] 001b:00[canon630u] write_byte(fd, 0x1b, 0x00); [canon630u] 001c:03[canon630u] write_byte(fd, 0x1c, 0x03); [canon630u] 001d:25[canon630u] write_byte(fd, 0x1d, 0x25); [canon630u] 001e:00[canon630u] write_byte(fd, 0x1e, 0x00); [canon630u] 001f:4b[canon630u] write_byte(fd, 0x1f, 0x4b); [canon630u] 0020:15[canon630u] write_byte(fd, 0x20, 0x15); [canon630u] 0021:e0[canon630u] write_byte(fd, 0x21, 0xe0); [canon630u] 0022:00[canon630u] write_byte(fd, 0x22, 0x00); [canon630u] 0023:4b[canon630u] write_byte(fd, 0x23, 0x4b); [canon630u] 0024:14[canon630u] write_byte(fd, 0x24, 0x14); [canon630u] 0025:37[canon630u] write_byte(fd, 0x25, 0x37); [canon630u] 0026:15[canon630u] write_byte(fd, 0x26, 0x15); [canon630u] 0027:00[canon630u] write_byte(fd, 0x27, 0x00); [canon630u] [canon630u] multi write 55 [canon630u] 0029:02[canon630u] write_byte(fd, 0x29, 0x02); [canon630u] 002a:00[canon630u] write_byte(fd, 0x2a, 0x00); [canon630u] 002b:00[canon630u] write_byte(fd, 0x2b, 0x00); [canon630u] 002c:03[canon630u] write_byte(fd, 0x2c, 0x03); [canon630u] 002d:ff[canon630u] write_byte(fd, 0x2d, 0xff); [canon630u] 002e:00[canon630u] write_byte(fd, 0x2e, 0x00); [canon630u] 002f:01[canon630u] write_byte(fd, 0x2f, 0x01); [canon630u] 0030:03[canon630u] write_byte(fd, 0x30, 0x03); [canon630u] 0031:ff[canon630u] write_byte(fd, 0x31, 0xff); [canon630u] 0032:00[canon630u] write_byte(fd, 0x32, 0x00); [canon630u] 0033:01[canon630u] write_byte(fd, 0x33, 0x01); [canon630u] 0034:03[canon630u] write_byte(fd, 0x34, 0x03); [canon630u] 0035:ff[canon630u] write_byte(fd, 0x35, 0xff); [canon630u] 0036:00[canon630u] write_byte(fd, 0x36, 0x00); [canon630u] 0037:01[canon630u] write_byte(fd, 0x37, 0x01); [canon630u] 0038:00[canon630u] write_byte(fd, 0x38, 0x00); [canon630u] 0039:00[canon630u] write_byte(fd, 0x39, 0x00); [canon630u] 003a:00[canon630u] write_byte(fd, 0x3a, 0x00); [canon630u] 003b:01[canon630u] write_byte(fd, 0x3b, 0x01); [canon630u] 003c:01[canon630u] write_byte(fd, 0x3c, 0x01); [canon630u] 003d:01[canon630u] write_byte(fd, 0x3d, 0x01); [canon630u] 003e:00[canon630u] write_byte(fd, 0x3e, 0x00); [canon630u] 003f:00[canon630u] write_byte(fd, 0x3f, 0x00); [canon630u] 0040:00[canon630u] write_byte(fd, 0x40, 0x00); [canon630u] 0041:00[canon630u] write_byte(fd, 0x41, 0x00); [canon630u] 0042:06[canon630u] write_byte(fd, 0x42, 0x06); [canon630u] 0043:1d[canon630u] write_byte(fd, 0x43, 0x1d); [canon630u] 0044:00[canon630u] write_byte(fd, 0x44, 0x00); [canon630u] 0045:13[canon630u] write_byte(fd, 0x45, 0x13); [canon630u] 0046:04[canon630u] write_byte(fd, 0x46, 0x04); [canon630u] 0047:1a[canon630u] write_byte(fd, 0x47, 0x1a); [canon630u] 0048:01[canon630u] write_byte(fd, 0x48, 0x01); [canon630u] 0049:04[canon630u] write_byte(fd, 0x49, 0x04); [canon630u] 004a:00[canon630u] write_byte(fd, 0x4a, 0x00); [canon630u] 004b:00[canon630u] write_byte(fd, 0x4b, 0x00); [canon630u] 004c:00[canon630u] write_byte(fd, 0x4c, 0x00); [canon630u] 004d:00[canon630u] write_byte(fd, 0x4d, 0x00); [canon630u] 004e:57[canon630u] write_byte(fd, 0x4e, 0x57); [canon630u] 004f:02[canon630u] write_byte(fd, 0x4f, 0x02); [canon630u] 0050:00[canon630u] write_byte(fd, 0x50, 0x00); [canon630u] 0051:3c[canon630u] write_byte(fd, 0x51, 0x3c); [canon630u] 0052:35[canon630u] write_byte(fd, 0x52, 0x35); [canon630u] 0053:94[canon630u] write_byte(fd, 0x53, 0x94); [canon630u] 0054:00[canon630u] write_byte(fd, 0x54, 0x00); [canon630u] 0055:10[canon630u] write_byte(fd, 0x55, 0x10); [canon630u] 0056:08[canon630u] write_byte(fd, 0x56, 0x08); [canon630u] 0057:3f[canon630u] write_byte(fd, 0x57, 0x3f); [canon630u] 0058:2b[canon630u] write_byte(fd, 0x58, 0x2b); [canon630u] 0059:91[canon630u] write_byte(fd, 0x59, 0x91); [canon630u] 005a:00[canon630u] write_byte(fd, 0x5a, 0x00); [canon630u] 005b:00[canon630u] write_byte(fd, 0x5b, 0x00); [canon630u] 005c:01[canon630u] write_byte(fd, 0x5c, 0x01); [canon630u] 005d:00[canon630u] write_byte(fd, 0x5d, 0x00); [canon630u] 005e:80[canon630u] write_byte(fd, 0x5e, 0x80); [canon630u] 005f:00[canon630u] write_byte(fd, 0x5f, 0x00); [canon630u] [canon630u] multi read 32 [canon630u] read_byte(fd, 0x08, &result); /* got 04 */ [canon630u] 0008:04[canon630u] read_byte(fd, 0x09, &result); /* got 1a */ [canon630u] 0009:1a[canon630u] read_byte(fd, 0x0a, &result); /* got 00 */ [canon630u] 000a:00[canon630u] read_byte(fd, 0x0b, &result); /* got 0d */ [canon630u] 000b:0d[canon630u] read_byte(fd, 0x0c, &result); /* got 4c */ [canon630u] 000c:4c[canon630u] read_byte(fd, 0x0d, &result); /* got 2f */ [canon630u] 000d:2f[canon630u] read_byte(fd, 0x0e, &result); /* got 00 */ [canon630u] 000e:00[canon630u] read_byte(fd, 0x0f, &result); /* got 01 */ [canon630u] 000f:01[canon630u] read_byte(fd, 0x10, &result); /* got 07 */ [canon630u] 0010:07[canon630u] read_byte(fd, 0x11, &result); /* got 04 */ [canon630u] 0011:04[canon630u] read_byte(fd, 0x12, &result); /* got 05 */ [canon630u] 0012:05[canon630u] read_byte(fd, 0x13, &result); /* got 06 */ [canon630u] 0013:06[canon630u] read_byte(fd, 0x14, &result); /* got 07 */ [canon630u] 0014:07[canon630u] read_byte(fd, 0x15, &result); /* got 00 */ [canon630u] 0015:00[canon630u] read_byte(fd, 0x16, &result); /* got 00 */ [canon630u] 0016:00[canon630u] read_byte(fd, 0x17, &result); /* got 00 */ [canon630u] 0017:00[canon630u] read_byte(fd, 0x18, &result); /* got 03 */ [canon630u] 0018:03[canon630u] read_byte(fd, 0x19, &result); /* got 00 */ [canon630u] 0019:00[canon630u] read_byte(fd, 0x1a, &result); /* got 00 */ [canon630u] 001a:00[canon630u] read_byte(fd, 0x1b, &result); /* got 00 */ [canon630u] 001b:00[canon630u] read_byte(fd, 0x1c, &result); /* got 03 */ [canon630u] 001c:03[canon630u] read_byte(fd, 0x1d, &result); /* got 25 */ [canon630u] 001d:25[canon630u] read_byte(fd, 0x1e, &result); /* got 00 */ [canon630u] 001e:00[canon630u] read_byte(fd, 0x1f, &result); /* got 4b */ [canon630u] 001f:4b[canon630u] read_byte(fd, 0x20, &result); /* got 15 */ [canon630u] 0020:15[canon630u] read_byte(fd, 0x21, &result); /* got e0 */ [canon630u] 0021:e0[canon630u] read_byte(fd, 0x22, &result); /* got 00 */ [canon630u] 0022:00[canon630u] read_byte(fd, 0x23, &result); /* got 4b */ [canon630u] 0023:4b[canon630u] read_byte(fd, 0x24, &result); /* got 14 */ [canon630u] 0024:14[canon630u] read_byte(fd, 0x25, &result); /* got 37 */ [canon630u] 0025:37[canon630u] read_byte(fd, 0x26, &result); /* got 15 */ [canon630u] 0026:15[canon630u] read_byte(fd, 0x27, &result); /* got 00 */ [canon630u] 0027:00[canon630u] [canon630u] multi read 55 [canon630u] read_byte(fd, 0x29, &result); /* got 02 */ [canon630u] 0029:02[canon630u] read_byte(fd, 0x2a, &result); /* got 00 */ [canon630u] 002a:00[canon630u] read_byte(fd, 0x2b, &result); /* got 00 */ [canon630u] 002b:00[canon630u] read_byte(fd, 0x2c, &result); /* got 03 */ [canon630u] 002c:03[canon630u] read_byte(fd, 0x2d, &result); /* got ff */ [canon630u] 002d:ff[canon630u] read_byte(fd, 0x2e, &result); /* got 00 */ [canon630u] 002e:00[canon630u] read_byte(fd, 0x2f, &result); /* got 01 */ [canon630u] 002f:01[canon630u] read_byte(fd, 0x30, &result); /* got 03 */ [canon630u] 0030:03[canon630u] read_byte(fd, 0x31, &result); /* got ff */ [canon630u] 0031:ff[canon630u] read_byte(fd, 0x32, &result); /* got 00 */ [canon630u] 0032:00[canon630u] read_byte(fd, 0x33, &result); /* got 01 */ [canon630u] 0033:01[canon630u] read_byte(fd, 0x34, &result); /* got 03 */ [canon630u] 0034:03[canon630u] read_byte(fd, 0x35, &result); /* got ff */ [canon630u] 0035:ff[canon630u] read_byte(fd, 0x36, &result); /* got 00 */ [canon630u] 0036:00[canon630u] read_byte(fd, 0x37, &result); /* got 01 */ [canon630u] 0037:01[canon630u] read_byte(fd, 0x38, &result); /* got 00 */ [canon630u] 0038:00[canon630u] read_byte(fd, 0x39, &result); /* got 00 */ [canon630u] 0039:00[canon630u] read_byte(fd, 0x3a, &result); /* got 00 */ [canon630u] 003a:00[canon630u] read_byte(fd, 0x3b, &result); /* got 01 */ [canon630u] 003b:01[canon630u] read_byte(fd, 0x3c, &result); /* got 01 */ [canon630u] 003c:01[canon630u] read_byte(fd, 0x3d, &result); /* got 01 */ [canon630u] 003d:01[canon630u] read_byte(fd, 0x3e, &result); /* got 00 */ [canon630u] 003e:00[canon630u] read_byte(fd, 0x3f, &result); /* got 00 */ [canon630u] 003f:00[canon630u] read_byte(fd, 0x40, &result); /* got 00 */ [canon630u] 0040:00[canon630u] read_byte(fd, 0x41, &result); /* got 00 */ [canon630u] 0041:00[canon630u] read_byte(fd, 0x42, &result); /* got 06 */ [canon630u] 0042:06[canon630u] read_byte(fd, 0x43, &result); /* got 1d */ [canon630u] 0043:1d[canon630u] read_byte(fd, 0x44, &result); /* got 00 */ [canon630u] 0044:00[canon630u] read_byte(fd, 0x45, &result); /* got 13 */ [canon630u] 0045:13[canon630u] read_byte(fd, 0x46, &result); /* got 04 */ [canon630u] 0046:04[canon630u] read_byte(fd, 0x47, &result); /* got 1a */ [canon630u] 0047:1a[canon630u] read_byte(fd, 0x48, &result); /* got 01 */ [canon630u] 0048:01[canon630u] read_byte(fd, 0x49, &result); /* got 04 */ [canon630u] 0049:04[canon630u] read_byte(fd, 0x4a, &result); /* got 00 */ [canon630u] 004a:00[canon630u] read_byte(fd, 0x4b, &result); /* got 00 */ [canon630u] 004b:00[canon630u] read_byte(fd, 0x4c, &result); /* got 00 */ [canon630u] 004c:00[canon630u] read_byte(fd, 0x4d, &result); /* got 00 */ [canon630u] 004d:00[canon630u] read_byte(fd, 0x4e, &result); /* got 57 */ [canon630u] 004e:57[canon630u] read_byte(fd, 0x4f, &result); /* got 02 */ [canon630u] 004f:02[canon630u] read_byte(fd, 0x50, &result); /* got 00 */ [canon630u] 0050:00[canon630u] read_byte(fd, 0x51, &result); /* got 3c */ [canon630u] 0051:3c[canon630u] read_byte(fd, 0x52, &result); /* got 35 */ [canon630u] 0052:35[canon630u] read_byte(fd, 0x53, &result); /* got 94 */ [canon630u] 0053:94[canon630u] read_byte(fd, 0x54, &result); /* got 00 */ [canon630u] 0054:00[canon630u] read_byte(fd, 0x55, &result); /* got 10 */ [canon630u] 0055:10[canon630u] read_byte(fd, 0x56, &result); /* got 08 */ [canon630u] 0056:08[canon630u] read_byte(fd, 0x57, &result); /* got 3f */ [canon630u] 0057:3f[canon630u] read_byte(fd, 0x58, &result); /* got 2b */ [canon630u] 0058:2b[canon630u] read_byte(fd, 0x59, &result); /* got 91 */ [canon630u] 0059:91[canon630u] read_byte(fd, 0x5a, &result); /* got 00 */ [canon630u] 005a:00[canon630u] read_byte(fd, 0x5b, &result); /* got 00 */ [canon630u] 005b:00[canon630u] read_byte(fd, 0x5c, &result); /* got 01 */ [canon630u] 005c:01[canon630u] read_byte(fd, 0x5d, &result); /* got 00 */ [canon630u] 005d:00[canon630u] read_byte(fd, 0x5e, &result); /* got 80 */ [canon630u] 005e:80[canon630u] read_byte(fd, 0x5f, &result); /* got 00 */ [canon630u] 005f:00[canon630u] [canon630u] write_byte(fd, 0x70, 0x73); [canon630u] write_byte(fd, 0x2c, 0x3f); [canon630u] write_byte(fd, 0x2d, 0xff); [canon630u] write_byte(fd, 0x2e, 0x00); [canon630u] write_byte(fd, 0x2f, 0x01); [canon630u] write_byte(fd, 0x30, 0x3f); [canon630u] write_byte(fd, 0x31, 0xff); [canon630u] write_byte(fd, 0x32, 0x00); [canon630u] write_byte(fd, 0x33, 0x01); [canon630u] write_byte(fd, 0x34, 0x3f); [canon630u] write_byte(fd, 0x35, 0xff); [canon630u] write_byte(fd, 0x36, 0x00); [canon630u] write_byte(fd, 0x37, 0x01); [canon630u] read_byte(fd, 0x02, &result); /* got 2d */ [canon630u] write_byte(fd, 0x07, 0x02); [canon630u] read_poll_flag... [canon630u] read_byte(fd, 0x02, &result); /* got 2c */ [canon630u] read_byte(fd, 0x02, &result); /* got 0e */ [canon630u] write_byte(fd, 0x07, 0x01); [canon630u] read_byte(fd, 0x02, &result); /* got 0c */ [canon630u] read_byte(fd, 0x02, &result); /* got 0c */ [canon630u] write_byte(fd, 0x07, 0x02); [canon630u] write_byte(fd, 0x03, 0x00); [canon630u] write_byte(fd, 0x04, 0x00); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] write_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x02); [canon630u] write_byte(fd, 0x04, 0x00); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] write_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x04); [canon630u] write_byte(fd, 0x04, 0x00); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] write_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x00); [canon630u] write_byte(fd, 0x04, 0x20); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] read_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x02); [canon630u] write_byte(fd, 0x04, 0x20); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] read_bulk(fd, 0x06, buf, 0x0400); [canon630u] write_byte(fd, 0x03, 0x04); [canon630u] write_byte(fd, 0x04, 0x20); [canon630u] write_byte(fd, 0x05, 0x00); [canon630u] read_bulk(fd, 0x06, buf, 0x0400); [canon630u] read_byte(fd, 0x02, &result); /* got 0e */ [canon630u] write_byte(fd, 0x07, 0x01); [canon630u] read_byte(fd, 0x02, &result); /* got 0e */ [canon630u] read_byte(fd, 0x08, &result); /* got 04 */ [canon630u] write_byte(fd, 0x08, 0x04); [canon630u] read_byte(fd, 0x46, &result); /* got 04 */ [canon630u] write_byte(fd, 0x46, 0x3f); [canon630u] read_byte(fd, 0x47, &result); /* got 1a */ [canon630u] write_byte(fd, 0x47, 0xff); [canon630u] read_byte(fd, 0x48, &result); /* got 01 */ [canon630u] write_byte(fd, 0x48, 0x01); [canon630u] read_byte(fd, 0x49, &result); /* got 04 */ [canon630u] write_byte(fd, 0x49, 0x04); [canon630u] read_byte(fd, 0x4a, &result); /* got 00 */ [canon630u] write_byte(fd, 0x4a, 0x00); [canon630u] read_byte(fd, 0x4b, &result); /* got 00 */ [canon630u] write_byte(fd, 0x4b, 0xc8); [canon630u] read_byte(fd, 0x4e, &result); /* got 57 */ [canon630u] write_byte(fd, 0x4e, 0x04); [canon630u] read_byte(fd, 0x4f, &result); /* got 02 */ [canon630u] write_byte(fd, 0x4f, 0x02); [canon630u] read_byte(fd, 0x50, &result); /* got 00 */ [canon630u] write_byte(fd, 0x50, 0x00); [canon630u] write_byte(fd, 0x57, 0x1f); [canon630u] write_byte(fd, 0x07, 0x08); [canon630u] write_byte(fd, 0x07, 0x00); [canon630u] write_byte(fd, 0x07, 0x03); [canon630u] waiting... [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ ....................... this continues until I cntl-C or kill the process. -- Using M2, Opera's e-mail client: on Gentoo Linux From henning at meier-geinitz.de Wed Jun 9 21:33:11 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 9 Jun 2004 22:33:11 +0200 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <20040609164851.1fcddb78@expensive> References: <20040609164851.1fcddb78@expensive> Message-ID: <20040609203310.GP7920@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 04:48:51PM +0100, Tom Schutzer-Weissmann wrote: > I had problems using the Epkowa libraries (libsane-epkowa) and the > iscan frontend with my usb scanner in kernel 2.6. > The scanner was closed after each operation. Once closed, nothing > could be read from it, and I got lots of BULK TIMEOUTs, although > there were no errors when the device was reopened. > > By modifying the code so that usb_reset() was always called before > usb_release_interface() and usb_close(), I solved the problem. Doesn't usb_reset() cause a renumeration and therefore the device gets a new device file? I guess this isn't the default for closing USB devices. Maybe the usb_reset just hides a bug in the SANE backend, libusb or the kernel. Bye, Henning From olaf at epkowa.co.jp Thu Jun 10 03:26:55 2004 From: olaf at epkowa.co.jp (Olaf Meeuwissen) Date: Thu, 10 Jun 2004 11:26:55 +0900 Subject: [sane-devel] Re: How to configure sane, xsane, etc. In-Reply-To: <20040609094922.GN7920@meier-geinitz.de> (Henning Meier-Geinitz's message of "Wed, 9 Jun 2004 11:49:22 +0200") References: <20040609094922.GN7920@meier-geinitz.de> Message-ID: <87y8mw87ww.fsf@zen.epkowa.co.jp> Henning Meier-Geinitz writes: > On Wed, Jun 09, 2004 at 10:08:32AM +0200, Fran?ois Patte wrote: > >> and to wait about 10/15 minutes for the research of >> peripherics.... > > That shouldn't happen. Which version of sane do you use > (scanimage --version)? The scan takes about 1 to5 seconds at least > with newer versions of SANE. As a workaround, you can disable > everything but "coolscan" in /etc/sane.d/dll.conf. That should do the trick, but if the net backend is enabled, you could in principle get pretty long delays depending on the settings in your net.conf (and your network latency). However, 10 to 15 minutes is a bit too long, if you ask me. -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From olaf at epkowa.co.jp Thu Jun 10 05:02:21 2004 From: olaf at epkowa.co.jp (Olaf Meeuwissen) Date: Thu, 10 Jun 2004 13:02:21 +0900 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <20040609164851.1fcddb78@expensive> (Tom Schutzer-Weissmann's message of "Wed, 9 Jun 2004 16:48:51 +0100") References: <20040609164851.1fcddb78@expensive> Message-ID: <87u0xk83hu.fsf@zen.epkowa.co.jp> Hi Tom, I am the lead developer of iscan and the sane-epkowa backend that comes with it. Farideh has also contacted me about your issue, but I think that my reply is better sent to sane-devel (at least it'll be archived :-). Tom Schutzer-Weissmann writes: > I had problems using the Epkowa libraries (libsane-epkowa) and the > iscan frontend with my usb scanner in kernel 2.6. > > The scanner was closed after each operation. Once closed, nothing > could be read from it, and I got lots of BULK TIMEOUTs, although there > were no errors when the device was reopened. Sorry to say, but I can't reproduce your problem. I've tried with a GT-8200 (aka Perfection 1650) on SuSE 9.1 and Debian (testing). FWIW, the version of relevant packages: SuSE Debian iscan 1.8.1-0.redhat.8.0 1.8.1-0.redhat.8.0 sane 1.0.13-73 -- libsane -- 1.0.14-2 libusb 0.1.8-31 -- libusb-0.1-4 -- 0.1.8-11 kernel-default 2.6.4-52 -- kernel-image-2.6.6-1-686 -- 2.6.6-1 with the note that I compiled iscan from sources on Debian. Can you give more information about your setup? Things like scanner and distribution used as well as version of relevant software might help me in reproducing your problem. When you say that "Once closed, nothing could be read ...", do you mean the calls to sanei_usb_close? I've looked at the debugging USB output and don't see any bulk timeouts. My system logs also show nothing. > By modifying the code so that usb_reset() was always called before > usb_release_interface() and usb_close(), I solved the problem. The epkowa backend does not call the usb_* functions directly, so I presume you have been mucking around in sanei_usb, right? This would seem to indicate that you think the problem is not specific to the epkowa backend. I see below that you also get BULK TIMEOUTs with the epson backend. Both backends share a lot of code, so this is not an indication that your problem is not backend specific. Has anyone seen this with other backends? > For libusb developers, my question is, should this be the case? There > is nothing in the API docs to indicate that it's necessary - perhaps > it is self-evident? > > Farideh - in the belief that you are a point of contact for Epson > developers - could you make them aware of this issue, if they aren't > already. I read sane-devel ;-) > I think this is relevant to SANE because although I had some success > scanning with xsane and xscanimage, using the libsane-epson libraries, > I still got timeouts if I closed, say, xsane, and then restarted it - > for lack of a usb_reset() I believe. I have no problems closing iscan and restarting it (for the setups listed above). > Apologies if this is old news. Tom SW Hope this helps, -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From keith at claytons.org Thu Jun 10 05:16:13 2004 From: keith at claytons.org (Keith Clayton) Date: Wed, 09 Jun 2004 21:16:13 -0700 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <20040608160140.GE7920@meier-geinitz.de> References: <1086025927.11981.15.camel@yoda> <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> <20040608154042.GB7920@meier-geinitz.de> <1086710152.643.7.camel@yoda> <20040608160140.GE7920@meier-geinitz.de> Message-ID: <1086840970.8298.19.camel@yoda> Very right . . must have had a typo in the command line. I re-did my tests. First test: used xsane to do a remote full scan and quit. Everything worked fine. gzipped log: xsane_regscan_quit_log.txt.gz 2nd test: used xsane to do a remote preview scan then attempt a regular scan once the preview has completed and the scanner head returned to starting position. preview scan is fine, regular scan dies. xsane bails completely. saned is left running. scanner is inaccesible even from host box and needs to be power cycled. One interesting thing I recognized in the process table of the host box is that there where *2* saned processes running. Looks like the preview scan in xsane uses the saned process started with SANE_DEBUG_PLUSTEK=255 saned -d255 but then the subsequent regular scan attempt forks the saned process so there are 2 saned -d255 processing running and then it dies. Note: saned is disabled in xinetd so its not getting started that way. gzipped log: xsane_previewscan_regscan_die_log.txt.gz Note in the case of the first test, when I quit, the single instance of saned running is closed out. Don't know if this sheds any light on the situation or not. Hope my description is clear enough. Sorry took me a couple of days to get back on this. Lots of life the past couple of days Cheers, Keith On Tue, 2004-06-08 at 18:01 +0200, Henning Meier-Geinitz wrote: > Hi, > > On Tue, Jun 08, 2004 at 08:55:55AM -0700, Keith Clayton wrote: > > Did use SANE_DEBUG_PLUSTEK=255 when starting saned. Cmd line was > > > > SANE_DEBUG_PLUSTEK=255 saned -d255 1>&2 2>remote_scan_quit.log > > > > > > So in that regard, was quite strange to not see any closing of the > > scanner's fd. > > Your first two logs contained the plustek messages. However, the log > you have just sent didn't contain any plustek messages. So maybe the > command line had a typo? > > Bye, > Henning > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org From henning at meier-geinitz.de Thu Jun 10 09:10:36 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 10 Jun 2004 10:10:36 +0200 Subject: [sane-devel] saned + win32-xsane problem In-Reply-To: <1086840970.8298.19.camel@yoda> References: <20040605100240.GE19373@meier-geinitz.de> <1086458420.26103.10.camel@yoda> <20040606165023.GM19373@meier-geinitz.de> <20040608085234.GG3351@meier-geinitz.de> <1086708706.641.4.camel@yoda> <20040608154042.GB7920@meier-geinitz.de> <1086710152.643.7.camel@yoda> <20040608160140.GE7920@meier-geinitz.de> <1086840970.8298.19.camel@yoda> Message-ID: <20040610081036.GC1513@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 09:16:13PM -0700, Keith Clayton wrote: > I re-did my tests. Nice. But it looks like you forgot to attach the results :-) > 2nd test: used xsane to do a remote preview scan then attempt a regular > scan once the preview has completed and the scanner head returned to > starting position. preview scan is fine, regular scan dies. xsane > bails completely. saned is left running. scanner is inaccesible even > from host box and needs to be power cycled. One interesting thing I > recognized in the process table of the host box is that there where *2* > saned processes running. Looks like the preview scan in xsane uses the > saned process started with SANE_DEBUG_PLUSTEK=255 saned -d255 but then > the subsequent regular scan attempt forks the saned process so there are > 2 saned -d255 processing running and then it dies. Note: saned is > disabled in xinetd so its not getting started that way. The plustek backend uses fork() (or rather sanei_thread_begin() ) to start a reader process after the start of the scan. So you get two processes everytime a scan is ongoing. So if you see two saned processes that just means that the plustek backend is still scanning (or trying to scan). Bye, Henning From henning at meier-geinitz.de Thu Jun 10 09:35:14 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 10 Jun 2004 10:35:14 +0200 Subject: [sane-devel] Fwd: [canon630u] read_byte(fd, 0x01, &result); /* got 00 */ In-Reply-To: References: Message-ID: <20040610083514.GA1580@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 08:15:01PM +0200, insane at piments.com wrote: > As you can see communication seems to go quite well at first but then gets > stuck in a loop with no apparent timeout. I have had a quick look at the sourcecode and think the loop happens at backend/canon630u-common.c, line 374 ff. The backend asks the scanner how many scan data it can provide. The scanner say "0". The backend tries for 60 seconds but the scanner still doesn't have any scan data. So it should time out after 60 seconds. But that's just my guess. However, I don't know why there is no scan data. Bye, Henning From keith at claytons.org Thu Jun 10 05:18:11 2004 From: keith at claytons.org (Keith Clayton) Date: Wed, 09 Jun 2004 21:18:11 -0700 Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) Message-ID: <1086841087.8304.22.camel@yoda> Hate when I do that . . here's the xsane logs described in my previous email -------------- next part -------------- A non-text attachment was scrubbed... Name: xsane_previewscan_regscan_die_log.txt.gz Type: application/x-gzip Size: 14392 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xsane_regscan_quit_log.txt.gz Type: application/x-gzip Size: 38569 bytes Desc: not available URL: From khk at khk.net Thu Jun 10 10:36:52 2004 From: khk at khk.net (Karl Heinz Kremer) Date: Thu, 10 Jun 2004 05:36:52 -0400 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <87u0xk83hu.fsf@zen.epkowa.co.jp> References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> Message-ID: I'm also reading sane-devel, so no need to take a detour with any Epson backend related information :-) I've never experienced any of the problem you describe, and I've been running a 2.6.x kernel for some time now (SuSE 9.1 beta versions and the final SuSE 9.1). I've tried this with two different USB controllers (USB-1.1 and high speed USB-2) with a number of different Epson scanners. Karl Heinz On Jun 10, 2004, at 12:02 AM, Olaf Meeuwissen wrote: > Hi Tom, > > I am the lead developer of iscan and the sane-epkowa backend that > comes with it. Farideh has also contacted me about your issue, but I > think that my reply is better sent to sane-devel (at least it'll be > archived :-). > > Tom Schutzer-Weissmann writes: > >> I had problems using the Epkowa libraries (libsane-epkowa) and the >> iscan frontend with my usb scanner in kernel 2.6. >> >> The scanner was closed after each operation. Once closed, nothing >> could be read from it, and I got lots of BULK TIMEOUTs, although there >> were no errors when the device was reopened. > > Sorry to say, but I can't reproduce your problem. I've tried with a > GT-8200 (aka Perfection 1650) on SuSE 9.1 and Debian (testing). FWIW, > the version of relevant packages: > > SuSE Debian > iscan 1.8.1-0.redhat.8.0 1.8.1-0.redhat.8.0 > sane 1.0.13-73 -- > libsane -- 1.0.14-2 > libusb 0.1.8-31 -- > libusb-0.1-4 -- 0.1.8-11 > kernel-default 2.6.4-52 -- > kernel-image-2.6.6-1-686 -- 2.6.6-1 > > with the note that I compiled iscan from sources on Debian. > > Can you give more information about your setup? Things like scanner > and distribution used as well as version of relevant software might > help me in reproducing your problem. > > When you say that "Once closed, nothing could be read ...", do you > mean the calls to sanei_usb_close? I've looked at the debugging USB > output and don't see any bulk timeouts. My system logs also show > nothing. > >> By modifying the code so that usb_reset() was always called before >> usb_release_interface() and usb_close(), I solved the problem. > > The epkowa backend does not call the usb_* functions directly, so I > presume you have been mucking around in sanei_usb, right? This would > seem to indicate that you think the problem is not specific to the > epkowa backend. I see below that you also get BULK TIMEOUTs with the > epson backend. Both backends share a lot of code, so this is not an > indication that your problem is not backend specific. > > Has anyone seen this with other backends? > >> For libusb developers, my question is, should this be the case? There >> is nothing in the API docs to indicate that it's necessary - perhaps >> it is self-evident? >> >> Farideh - in the belief that you are a point of contact for Epson >> developers - could you make them aware of this issue, if they aren't >> already. > > I read sane-devel ;-) > >> I think this is relevant to SANE because although I had some success >> scanning with xsane and xscanimage, using the libsane-epson libraries, >> I still got timeouts if I closed, say, xsane, and then restarted it - >> for lack of a usb_reset() I believe. > > I have no problems closing iscan and restarting it (for the setups > listed above). > >> Apologies if this is old news. Tom SW > > Hope this helps, > -- > Olaf Meeuwissen EPSON KOWA Corporation, PF1 > FSF Associate Member #1962 sign up at http://member.fsf.org/ > GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 > Penguin's lib! -- I hack, therefore I am -- LPIC-2 > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org From henning at meier-geinitz.de Thu Jun 10 14:44:04 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 10 Jun 2004 15:44:04 +0200 Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <1086841087.8304.22.camel@yoda> References: <1086841087.8304.22.camel@yoda> Message-ID: <20040610134404.GB2294@meier-geinitz.de> Hi, On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > Hate when I do that . . here's the xsane logs described in my previous > email Ok, let's look at the second log. The preview scan looks ok (but I don't know the details of the plustek backend). The real scan also starts fine and then we see this: [plustek] sane_read - read 3750 bytes [saned] do_scan: read 3750 bytes from scanner [plustek] usb_ScanReadImage() done, result: 0 [plustek] usb_ReadData() [plustek] usb_ScanReadImage(3760) [plustek] usb_ScanReadImage() done, result: 0 [saned] do_scan: trying to write 3754 bytes to client [saned] do_scan: wrote 3754 bytes to client [saned] do_scan: trying to read 1521 bytes from scanner [plustek] sane_read - read 1521 bytes [saned] do_scan: read 1521 bytes from scanner Now these 1521 bytes should be sent to the frontend... [saned] do_scan: processing RPC request on fd 4 [saned] process_request: waiting for request [saned] process_request: bad status 22 saned thinks something has been sent to it by the control (not data) connection. But when trying to decode what was sent it gets an error when reading the first word. 22 is "invalid argument". That means that no data could be read. Maybe xsane has crashed on the clent side meanwhile? Usually during the scan nothing is sent to the control file descriptor. Anyway. As sane_cancel isn't called the reader_process in the plustek backend isn't killed and the plustek backend gets confused. So my impression is that the problem is with xsane (or the net frontend on windows) and the scanner lockup is just a consequence. But I don't know why xsane (or the net backend) crashes. So maybe finding out the details here may help- E.g. gdb xsane on the client or enabling debugging for xsane and the net backend and looking at the last few lines before the crash. Maybe the xsane and plustek maintainers can have a look at the logfiles, too? Bye, Henning From keith at claytons.org Thu Jun 10 15:09:36 2004 From: keith at claytons.org (Keith Clayton) Date: Thu, 10 Jun 2004 07:09:36 -0700 (PDT) Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <20040610134404.GB2294@meier-geinitz.de> References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> Message-ID: What sort of steps are availble for me to take debugging-wise on the windows end? If xsane is started from the command prompt, are there any swithces available to generate debugging output at the command prompt? K On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > > Hate when I do that . . here's the xsane logs described in my previous > > email > > Ok, let's look at the second log. The preview scan looks ok (but I > don't know the details of the plustek backend). The real scan also > starts fine and then we see this: > > [plustek] sane_read - read 3750 bytes > [saned] do_scan: read 3750 bytes from scanner > [plustek] usb_ScanReadImage() done, result: 0 > [plustek] usb_ReadData() > [plustek] usb_ScanReadImage(3760) > [plustek] usb_ScanReadImage() done, result: 0 > [saned] do_scan: trying to write 3754 bytes to client > [saned] do_scan: wrote 3754 bytes to client > [saned] do_scan: trying to read 1521 bytes from scanner > [plustek] sane_read - read 1521 bytes > [saned] do_scan: read 1521 bytes from scanner > > Now these 1521 bytes should be sent to the frontend... > > [saned] do_scan: processing RPC request on fd 4 > [saned] process_request: waiting for request > [saned] process_request: bad status 22 > > saned thinks something has been sent to it by the control (not data) > connection. But when trying to decode what was sent it gets an error > when reading the first word. 22 is "invalid argument". That means that > no data could be read. Maybe xsane has crashed on the clent side > meanwhile? > > Usually during the scan nothing is sent to the control file descriptor. > > Anyway. As sane_cancel isn't called the reader_process in the plustek > backend isn't killed and the plustek backend gets confused. > > So my impression is that the problem is with xsane (or the net > frontend on windows) and the scanner lockup is just a consequence. > But I don't know why xsane (or the net backend) crashes. So maybe > finding out the details here may help- E.g. gdb xsane on the client or > enabling debugging for xsane and the net backend and looking at the > last few lines before the crash. > > Maybe the xsane and plustek maintainers can have a look at the > logfiles, too? > > Bye, > Henning > > From henning at meier-geinitz.de Thu Jun 10 15:10:41 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 10 Jun 2004 16:10:41 +0200 Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> Message-ID: <20040610141041.GD2294@meier-geinitz.de> Hi, On Thu, Jun 10, 2004 at 07:09:36AM -0700, Keith Clayton wrote: > What sort of steps are availble for me to take debugging-wise on the > windows end? > > If xsane is started from the command prompt, are there any swithces > available to generate debugging output at the command prompt? I don't know how setting environment variables works on windows but with bash you'd do export XSANE=DEBUG=255 export SANE_DEBUG_NET=255 XSANE_DEBUG will produce a huge amount of debug messages. Bye, Henning From keith at claytons.org Thu Jun 10 15:30:24 2004 From: keith at claytons.org (Keith Clayton) Date: Thu, 10 Jun 2004 07:30:24 -0700 (PDT) Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <20040610141041.GD2294@meier-geinitz.de> References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> <20040610141041.GD2294@meier-geinitz.de> Message-ID: I don't know much about windows side either. Guess I'll plug away a bit and see if I can coax some debug output out of xsane Cheers, Keith On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 10, 2004 at 07:09:36AM -0700, Keith Clayton wrote: > > What sort of steps are availble for me to take debugging-wise on the > > windows end? > > > > If xsane is started from the command prompt, are there any swithces > > available to generate debugging output at the command prompt? > > I don't know how setting environment variables works on windows but > with bash you'd do > > export XSANE=DEBUG=255 > export SANE_DEBUG_NET=255 > > XSANE_DEBUG will produce a huge amount of debug messages. > > Bye, > Henning > > From Oliver.Rauch at Rauch-Domain.DE Thu Jun 10 16:03:56 2004 From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch) Date: 10 Jun 2004 17:03:56 +0200 Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> Message-ID: <1086879836.2126.2.camel@Babylon7> For windows you can not enable a debug output - at least I do not know a way with the published binaries because they are compiled as GUI. BTW. Did you ever test xsane-0.94-win32? Oliver Am Don, 2004-06-10 um 16.09 schrieb Keith Clayton: > What sort of steps are availble for me to take debugging-wise on the > windows end? > > If xsane is started from the command prompt, are there any swithces > available to generate debugging output at the command prompt? > > K > > > > On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > > > Hi, > > > > On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > > > Hate when I do that . . here's the xsane logs described in my previous > > > email > > > > Ok, let's look at the second log. The preview scan looks ok (but I > > don't know the details of the plustek backend). The real scan also > > starts fine and then we see this: > > > > [plustek] sane_read - read 3750 bytes > > [saned] do_scan: read 3750 bytes from scanner > > [plustek] usb_ScanReadImage() done, result: 0 > > [plustek] usb_ReadData() > > [plustek] usb_ScanReadImage(3760) > > [plustek] usb_ScanReadImage() done, result: 0 > > [saned] do_scan: trying to write 3754 bytes to client > > [saned] do_scan: wrote 3754 bytes to client > > [saned] do_scan: trying to read 1521 bytes from scanner > > [plustek] sane_read - read 1521 bytes > > [saned] do_scan: read 1521 bytes from scanner > > > > Now these 1521 bytes should be sent to the frontend... > > > > [saned] do_scan: processing RPC request on fd 4 > > [saned] process_request: waiting for request > > [saned] process_request: bad status 22 > > > > saned thinks something has been sent to it by the control (not data) > > connection. But when trying to decode what was sent it gets an error > > when reading the first word. 22 is "invalid argument". That means that > > no data could be read. Maybe xsane has crashed on the clent side > > meanwhile? > > > > Usually during the scan nothing is sent to the control file descriptor. > > > > Anyway. As sane_cancel isn't called the reader_process in the plustek > > backend isn't killed and the plustek backend gets confused. > > > > So my impression is that the problem is with xsane (or the net > > frontend on windows) and the scanner lockup is just a consequence. > > But I don't know why xsane (or the net backend) crashes. So maybe > > finding out the details here may help- E.g. gdb xsane on the client or > > enabling debugging for xsane and the net backend and looking at the > > last few lines before the crash. > > > > Maybe the xsane and plustek maintainers can have a look at the > > logfiles, too? > > > > Bye, > > Henning > > > > From ngamradt at hotmail.com Thu Jun 10 16:16:45 2004 From: ngamradt at hotmail.com (Neal Gamradt) Date: Thu, 10 Jun 2004 15:16:45 +0000 Subject: [sane-devel] Question About Mustek 600CP scanner on Suse 9.1 Message-ID: Hello All, First off I would like to thank you all for the the work you have put into scanner support for Linux, I have a Mustek 600CP and historically I have never had much trouble setting it up thanks to the great work you have done. I recently upgraded from Suse 8.2 to Suse 9.1. Currently I am having trouble with scanimage not finding my scanner. I have tested the scanner on a Windows 2000 machine and it is working fine on there. I never had this problem on Suse 8.2. In the dll.conf file I have commented out everything except for the "mustek_pp" and in the mustek_pp.conf file I have commented out everything except for the line "scanner mustek-cis600 * cis600". The following is what I get when I run "scanimage -L" after setting SANE_DEBUG_MUSTEK_PP=128 and SANE_DEBUG_SANEI_PA4S2=128: [sanei_debug] Setting debug level of mustek_pp to 128. [mustek_pp] sane-mustek_pp, version 0.13-beta. build for SANE 1.0.14 [mustek_pp] backend by Jochen Eisinger [sanei_debug] Setting debug level of sanei_pa4s2 to 128. [sanei_pa4s2] sanei_pa4s2: interface called for the first time [sanei_pa4s2] sanei_pa4s2_devices: invoked [sanei_pa4s2] pa4s2_init: static int first_time = 1 [sanei_pa4s2] pa4s2_init: called for the first time [sanei_pa4s2] pa4s2_init: initializing libieee1284 [sanei_pa4s2] pa4s2_init: 1 ports reported by IEEE 1284 library [sanei_pa4s2] pa4s2_init: port 0 is `parport0` [sanei_pa4s2] pa4s2_init: allocating port list [sanei_pa4s2] pa4s2_init: initialized successfully [mustek_pp] sanei_init: auto probing port [sanei_pa4s2] sanei_pa4s2_open: called for device 'parport0' [sanei_pa4s2] sanei_pa4s2_open: trying to connect to port [sanei_pa4s2] pa4s2_open: trying to attach dev `parport0` [sanei_pa4s2] pa4s2_init: static int first_time = 0 [sanei_pa4s2] pa4s2_init: sanei already initalized [sanei_pa4s2] pa4s2_open: looking up port in list [sanei_pa4s2] pa4s2_open: port is in list at port[0] [sanei_pa4s2] pa4s2_open: setting up port data [sanei_pa4s2] pa4s2_open: name=parport0 in_use=SANE_TRUE [sanei_pa4s2] pa4s2_open: enabled=SANE_FALSE mode=PA4S2_MODE_NIB [sanei_pa4s2] pa4s2_open: opening device [sanei_pa4s2] pa4s2_open: device `parport0` opened... [sanei_pa4s2] pa4s2_open: returning SANE_STATUS_GOOD [sanei_pa4s2] pa4s2_open: open dev `parport0` as fd 0 [sanei_pa4s2] sanei_pa4s2_open: connected to device using fd 0 [sanei_pa4s2] sanei_pa4s2_open: checking for scanner [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1 [sanei_pa4s2] sanei_pa4s2_enable: enable port 'parport0' [sanei_pa4s2] pa4s2_enable: prelock[] = {0xff, 0x47, 0x0c} [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: reading ASIC id [sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0 [sanei_pa4s2] sanei_pa4s2_readbegin: NIB readbegin [sanei_pa4s2] pa4s2_readbegin_nib: selecting register 0 at 'parport0' [sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0 [sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readbyte: read in NIB mode [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5 from 'parport0' [sanei_pa4s2] sanei_pa4s2_readbyte: read finished [sanei_pa4s2] sanei_pa4s2_readbyte: got value 0xa5 [sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readend: called for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readend: NIB mode readend [sanei_pa4s2] pa4s2_readend_nib: end of reading sequence for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: detected ASIC id 1015 [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0 [sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0' [sanei_pa4s2] pa4s2_disable: state restored [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: trying better modes [sanei_pa4s2] sanei_pa4s2_open: trying mode 0 [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1 [sanei_pa4s2] sanei_pa4s2_enable: enable port 'parport0' [sanei_pa4s2] pa4s2_enable: prelock[] = {0xff, 0x47, 0x0c} [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0 [sanei_pa4s2] sanei_pa4s2_readbegin: NIB readbegin [sanei_pa4s2] pa4s2_readbegin_nib: selecting register 0 at 'parport0' [sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0 [sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readbyte: read in NIB mode [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5 from 'parport0' [sanei_pa4s2] sanei_pa4s2_readbyte: read finished [sanei_pa4s2] sanei_pa4s2_readbyte: got value 0xa5 [sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readend: called for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readend: NIB mode readend [sanei_pa4s2] pa4s2_readend_nib: end of reading sequence for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0 [sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0' [sanei_pa4s2] pa4s2_disable: state restored [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: mode works [sanei_pa4s2] sanei_pa4s2_open: skipping mode UNI [sanei_pa4s2] sanei_pa4s2_open: trying mode 2 [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1 [sanei_pa4s2] sanei_pa4s2_enable: enable port 'parport0' [sanei_pa4s2] pa4s2_enable: prelock[] = {0xff, 0x47, 0x0c} [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0 [sanei_pa4s2] sanei_pa4s2_readbegin: EPP readbegin [sanei_pa4s2] pa4s2_readbegin_epp: selecting register 0 at 'parport0' [sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0 [sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readbyte: read in EPP mode [sanei_pa4s2] pa4s2_readbyte_epp: reading value 0xfd from 'parport0' [sanei_pa4s2] sanei_pa4s2_readbyte: read finished [sanei_pa4s2] sanei_pa4s2_readbyte: got value 0xfd [sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readend: called for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readend: EPP mode readend [sanei_pa4s2] pa4s2_readend_epp: end of reading sequence [sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0 [sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0' [sanei_pa4s2] pa4s2_disable: state restored [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_open: mode failed [sanei_pa4s2] sanei_pa4s2_open: returned ASIC-ID 0xfd [sanei_pa4s2] sanei_pa4s2_open: using mode 0 [sanei_pa4s2] sanei_pa4s2_open: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1 [sanei_pa4s2] sanei_pa4s2_enable: enable port 'parport0' [sanei_pa4s2] pa4s2_enable: prelock[] = {0xff, 0x8f, 0x0c} [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0 [sanei_pa4s2] sanei_pa4s2_readbegin: NIB readbegin [sanei_pa4s2] pa4s2_readbegin_nib: selecting register 0 at 'parport0' [sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0 [sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readbyte: read in NIB mode [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x00 from 'parport0' [sanei_pa4s2] sanei_pa4s2_readbyte: read finished [sanei_pa4s2] sanei_pa4s2_readbyte: got value 0x00 [sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_readend: called for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called [sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok... [sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's [sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down. [sanei_pa4s2] sanei_pa4s2_readend: NIB mode readend [sanei_pa4s2] pa4s2_readend_nib: end of reading sequence for fd 0 [sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0 [sanei_pa4s2] sanei_pa4s2_enable: disable port 'parport0' [sanei_pa4s2] pa4s2_disable: state restored [sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_close: fd = 0 [sanei_pa4s2] sanei_pa4s2_close: freeing resources [sanei_pa4s2] pa4s2_close: fd=0 [sanei_pa4s2] pa4s2_close: this is port 'parport0' [sanei_pa4s2] pa4s2_close: checking whether port is enabled [sanei_pa4s2] pa4s2_close: trying to free io port [sanei_pa4s2] pa4s2_close: marking port as unused [sanei_pa4s2] pa4s2_close: returning SANE_STATUS_GOOD [sanei_pa4s2] sanei_pa4s2_close: finished [mustek_pp] cis_attach: asic id (0x00) not recognized 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). [mustek_pp] sane_exit: all drivers unloaded From keith at claytons.org Thu Jun 10 16:32:26 2004 From: keith at claytons.org (Keith Clayton) Date: Thu, 10 Jun 2004 08:32:26 -0700 (PDT) Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <1086879836.2126.2.camel@Babylon7> References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> <1086879836.2126.2.camel@Babylon7> Message-ID: No, still running 0.90 on the windows box. I upgraded to 0.94 on the linux box and looked for windows binaries at the same time. Didn't see them. Did I miss it? K On Thu, 10 Jun 2004, Oliver Rauch wrote: > For windows you can not enable a debug output - at least I do not know > a way with the published binaries because they are compiled as GUI. > > BTW. Did you ever test xsane-0.94-win32? > > Oliver > > Am Don, 2004-06-10 um 16.09 schrieb Keith Clayton: > > What sort of steps are availble for me to take debugging-wise on the > > windows end? > > > > If xsane is started from the command prompt, are there any swithces > > available to generate debugging output at the command prompt? > > > > K > > > > > > > > On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > > > > > Hi, > > > > > > On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > > > > Hate when I do that . . here's the xsane logs described in my previous > > > > email > > > > > > Ok, let's look at the second log. The preview scan looks ok (but I > > > don't know the details of the plustek backend). The real scan also > > > starts fine and then we see this: > > > > > > [plustek] sane_read - read 3750 bytes > > > [saned] do_scan: read 3750 bytes from scanner > > > [plustek] usb_ScanReadImage() done, result: 0 > > > [plustek] usb_ReadData() > > > [plustek] usb_ScanReadImage(3760) > > > [plustek] usb_ScanReadImage() done, result: 0 > > > [saned] do_scan: trying to write 3754 bytes to client > > > [saned] do_scan: wrote 3754 bytes to client > > > [saned] do_scan: trying to read 1521 bytes from scanner > > > [plustek] sane_read - read 1521 bytes > > > [saned] do_scan: read 1521 bytes from scanner > > > > > > Now these 1521 bytes should be sent to the frontend... > > > > > > [saned] do_scan: processing RPC request on fd 4 > > > [saned] process_request: waiting for request > > > [saned] process_request: bad status 22 > > > > > > saned thinks something has been sent to it by the control (not data) > > > connection. But when trying to decode what was sent it gets an error > > > when reading the first word. 22 is "invalid argument". That means that > > > no data could be read. Maybe xsane has crashed on the clent side > > > meanwhile? > > > > > > Usually during the scan nothing is sent to the control file descriptor. > > > > > > Anyway. As sane_cancel isn't called the reader_process in the plustek > > > backend isn't killed and the plustek backend gets confused. > > > > > > So my impression is that the problem is with xsane (or the net > > > frontend on windows) and the scanner lockup is just a consequence. > > > But I don't know why xsane (or the net backend) crashes. So maybe > > > finding out the details here may help- E.g. gdb xsane on the client or > > > enabling debugging for xsane and the net backend and looking at the > > > last few lines before the crash. > > > > > > Maybe the xsane and plustek maintainers can have a look at the > > > logfiles, too? > > > > > > Bye, > > > Henning > > > > > > > > > From David at phenix.fr Thu Jun 10 16:46:29 2004 From: David at phenix.fr (David Neary) Date: Thu, 10 Jun 2004 17:46:29 +0200 Subject: [sane-devel] RE: sane-devel digest, Vol 1 #365 - 11 msgs Message-ID: Hi, Keith Clayton wrote: > What sort of steps are availble for me to take debugging-wise on the > windows end? > > If xsane is started from the command prompt, are there any swithces > available to generate debugging output at the command prompt? As Henning said, you just need to set your environment variables XSANE_DEBUG and SANE_DEBUG_NET. You can set these as: set XSANE_DEBUG=255 set SANE_DEBUG_NET=255 and then run scanimage.exe or xsane.exe to see what's happenning. Make sure you have set the SANE_CONFIG_DIR environment variable to point to where your dll.conf and net.conf are on the disk, otherwise nothing will work (set SANE_CONFIG_DIR=C:\xsane for example). In case this gives you a problem, check your version of sane, since 1.0.13 didn't have the path separators and directory separators set correctly for win32. Cheers, Dave. From misc at tomweissmann.org Thu Jun 10 17:08:47 2004 From: misc at tomweissmann.org (Tom Schutzer-Weissmann) Date: Thu, 10 Jun 2004 17:08:47 +0100 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> Message-ID: <20040610170847.5c305388@expensive> On Thu, 10 Jun 2004 05:36:52 -0400 Karl Heinz Kremer wrote: > I'm also reading sane-devel, so no need to take a detour with > any Epson backend related information :-) > I've never experienced any of the problem you describe, and I've > been running a 2.6.x kernel for some time now (SuSE 9.1 beta versions > and the final SuSE 9.1). > > I've tried this with two different USB controllers (USB-1.1 and high > speed USB-2) with a number of different Epson scanners. > > Karl Heinz Thank you for all your responses. I'm using Debian unstable, kernel 2.6.6 with ohci_usb, libusb-0-1.4 (0.1.8-11). The scanner is an Epson Perfection 2450. It seems libusb isn't working as it should - maybe future Debian updates will solve the problem; in the meantime I am happy with my hack, but if anyone would like me to try out some suggestions to get to the bottom of this mystery, I'd be happy to help off-list. Regards, Tom From mattias.ellert at tsl.uu.se Thu Jun 10 21:14:02 2004 From: mattias.ellert at tsl.uu.se (Mattias Ellert) Date: Thu, 10 Jun 2004 22:14:02 +0200 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? In-Reply-To: References: Message-ID: <40C8C10A.5080500@tsl.uu.se> Allan Kaplan wrote: > Hi Mattias, > > I am happy to report a little progress. Once I installed the proper files > I did recognize the scanner, but that's all. I tried the other commands > with no progress. I am suspicious that the codes returned by sane are > generic "we really don't know anything about this scanner" information. So > what's what you say my next step is? Crack open the scanner and post the > info on the chipset and pray? Am I really out of luck? > > Thanks for all your help, > > Allan > > Here's the transcript. I took out most of the annotations. > > Last login: Thu Jun 10 00:25:37 on ttyp1 > Welcome to Darwin! > [Lolita:~] amkaplan% /usr/local/bin/sane-find-scanner > > > found USB scanner (vendor=0x0475, product=0x0100) at > libusb:003:002-0475-0100-ff-00 > # Your USB scanner was (probably) detected. It may or may not be supported > by > # SANE. Try scanimage -L and read the backend's manpage. > Could you run sane-find-scanner in very verbose mode (as suggested by Henning in his answer to the mailing list): sane-find-scanner -v -v This should hopefully give some information. According to http://www.linux-usb.org/usb.ids the vendor ID 0475 is "Relisys/Teco Information System" and not NEC, but this is probably not significant -- there are a lot of scanners that are produced by one company and sold by an other. According to http://www.sane-project.org/sane-mfgs.html there only seem to exist SANE drivers for Relisys SCSI scanners. The Relisys USB scanners mentioned in the list (0475-0103, 0475-0270) are all listed as "probably unsupported". And this one is (0475-0100) not mentioned, either under Relisys or NEC. Mattias -- ________________________________________________________________________ mattias.ellert at tsl.uu.se tel: +46 18 471 32 58 http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13 ________________________________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2344 bytes Desc: S/MIME Cryptographic Signature URL: From olaf at epkowa.co.jp Fri Jun 11 01:37:21 2004 From: olaf at epkowa.co.jp (Olaf Meeuwissen) Date: Fri, 11 Jun 2004 09:37:21 +0900 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <20040610170847.5c305388@expensive> (Tom Schutzer-Weissmann's message of "Thu, 10 Jun 2004 17:08:47 +0100") References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> <20040610170847.5c305388@expensive> Message-ID: <87r7snudz2.fsf@zen.epkowa.co.jp> Tom Schutzer-Weissmann writes: > On Thu, 10 Jun 2004 05:36:52 -0400 > Karl Heinz Kremer wrote: > >> I'm also reading sane-devel, so no need to take a detour with >> any Epson backend related information :-) >> I've never experienced any of the problem you describe, and I've >> been running a 2.6.x kernel for some time now (SuSE 9.1 beta versions >> and the final SuSE 9.1). >> >> I've tried this with two different USB controllers (USB-1.1 and high >> speed USB-2) with a number of different Epson scanners. >> >> Karl Heinz > > Thank you for all your responses. > > I'm using Debian unstable, kernel 2.6.6 with ohci_usb, libusb-0-1.4 > (0.1.8-11). The scanner is an Epson Perfection 2450. That's what you get for running bleeding edge ;-) I'm using Debian testing, kernel 2.6.6 with uhci_hcd (and ehci_hcd), libusb-0.1-4 (0.1.8-11) and will see if I can lay my hands on a Perfection 2450. The USB modules are autoprobed, I don't have anything USB related in my /etc/modules-2.6. There is an usb-uhci in my /etc/modules but IIRC that file is not used if /etc/modules-2.6 exists. > It seems libusb isn't working as it should - maybe future Debian > updates will solve the problem; in the meantime I am happy with my > hack, but if anyone would like me to try out some suggestions to get > to the bottom of this mystery, I'd be happy to help off-list. As I'm using the same libusb as you do, I am sceptical about libusb being the culprit. Apart from the usb module and scanner model, we use the same setup. I'll get back with the results on the Perfection 2450 ASAP. HTH, -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From mattias.ellert at tsl.uu.se Fri Jun 11 02:17:33 2004 From: mattias.ellert at tsl.uu.se (Mattias Ellert) Date: Fri, 11 Jun 2004 03:17:33 +0200 Subject: [sane-devel] NEC Petiscan driver for MacOSX possible? Message-ID: <40C9082D.9030200@tsl.uu.se> Hi! I forward this to sane-devel.... Mattias -------- Original Message -------- Subject: Re: [sane-devel] NEC Petiscan driver for MacOSX possible? Date: Thu, 10 Jun 2004 17:58:02 -0700 From: Allan Kaplan To: Mattias Ellert Hi Mattias, I did the verbose command and got back a verbose response. Here's what applies to the scanner, with the whole thing as an attachment. I hope it makes some sense to you, because all I found was that it doesn't recognize the chipset. Does this help at all? What do you suggest as a next step? Many thanks, Allan bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 255 bDeviceSubClass 0 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x0475 idProduct 0x0100 bcdDevice 1.00 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 128 () MaxPower 500 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x01 (out 0x01) bmAttributes 2 (bulk) wMaxPacketSize 8 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 8 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 checking for GT-6801 ... this is not a GT-6801 (bcdUSB = 0x100) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bDeviceSubClass = 0x0) checking for MA-1509 ... this is not a MA-1509 (bcdUSB = 0x100) checking for LM983[1,2,3] ... this is not a LM983x (bEndpointAddress = 0x1, bmAttributes = 0x2, wMaxPacketSize = 0x8, bInterval = 0x0) checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x100) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... this is not a GL841 (bcdUSB = 0x100) checking for ICM532B ... check 2, this is not a ICM532B (bcdUSB = 0x100) found USB scanner (vendor=0x0475, product=0x0100) at libusb:003:002-0475-0100-ff-00 -- ________________________________________________________________________ mattias.ellert at tsl.uu.se tel: +46 18 471 32 58 http://www.tsl.uu.se/~ellert/ fax: +46 18 471 35 13 ________________________________________________________________________ -------------- next part -------------- A non-text attachment was scrubbed... Name: -v -v.rtf Type: application/octet-stream Size: 10009 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2344 bytes Desc: S/MIME Cryptographic Signature URL: From olaf at epkowa.co.jp Fri Jun 11 05:50:39 2004 From: olaf at epkowa.co.jp (Olaf Meeuwissen) Date: Fri, 11 Jun 2004 13:50:39 +0900 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <87r7snudz2.fsf@zen.epkowa.co.jp> (Olaf Meeuwissen's message of "Fri, 11 Jun 2004 09:37:21 +0900") References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> <20040610170847.5c305388@expensive> <87r7snudz2.fsf@zen.epkowa.co.jp> Message-ID: <87zn7au28w.fsf@zen.epkowa.co.jp> Olaf Meeuwissen writes: > Tom Schutzer-Weissmann writes: > >> On Thu, 10 Jun 2004 05:36:52 -0400 >> Karl Heinz Kremer wrote: >> >>> I'm also reading sane-devel, so no need to take a detour with >>> any Epson backend related information :-) >>> I've never experienced any of the problem you describe, and I've >>> been running a 2.6.x kernel for some time now (SuSE 9.1 beta versions >>> and the final SuSE 9.1). >>> >>> I've tried this with two different USB controllers (USB-1.1 and high >>> speed USB-2) with a number of different Epson scanners. >>> >>> Karl Heinz >> >> Thank you for all your responses. >> >> I'm using Debian unstable, kernel 2.6.6 with ohci_usb, libusb-0-1.4 >> (0.1.8-11). The scanner is an Epson Perfection 2450. > > That's what you get for running bleeding edge ;-) > > I'm using Debian testing, kernel 2.6.6 with uhci_hcd (and ehci_hcd), > libusb-0.1-4 (0.1.8-11) and will see if I can lay my hands on a > Perfection 2450. > > The USB modules are autoprobed, I don't have anything USB related in > my /etc/modules-2.6. There is an usb-uhci in my /etc/modules but IIRC > that file is not used if /etc/modules-2.6 exists. > >> It seems libusb isn't working as it should - maybe future Debian >> updates will solve the problem; in the meantime I am happy with my >> hack, but if anyone would like me to try out some suggestions to get >> to the bottom of this mystery, I'd be happy to help off-list. > > As I'm using the same libusb as you do, I am sceptical about libusb > being the culprit. Apart from the usb module and scanner model, we > use the same setup. I'll get back with the results on the Perfection > 2450 ASAP. Problem confirmed for the GT-9700 (aka Perfection 2450) with both the epson and epkowa backends. Note that these same backends work fine with the GT-8200 (aka Perfection 1650) under identical conditions. Just starting a SANE frontend (tried with xsane and iscan) with the GT-9700 already takes "ages" and it just refuses to preview. BTW, the epson backend is from sane-backend-1.0.14 and the epkowa one from iscan-1.8.1. # The upcoming iscan-1.9.0 (due 2004-06-18), which adds support for # the ES-10000G (aka Expression 10000) and adds saving in JPEG format, # suffers from the same problem. Looks like Karl and/or I have some digging to do ;-( -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From misc at tomweissmann.org Fri Jun 11 14:21:16 2004 From: misc at tomweissmann.org (Tom Schutzer-Weissmann) Date: Fri, 11 Jun 2004 14:21:16 +0100 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <87zn7au28w.fsf@zen.epkowa.co.jp> References: <20040609164851.1fcddb78@expensive> <87u0xk83hu.fsf@zen.epkowa.co.jp> <20040610170847.5c305388@expensive> <87r7snudz2.fsf@zen.epkowa.co.jp> <87zn7au28w.fsf@zen.epkowa.co.jp> Message-ID: <20040611142116.7740e5d1@expensive> On Fri, 11 Jun 2004 13:50:39 +0900 Olaf Meeuwissen wrote: [...] > Problem confirmed for the GT-9700 (aka Perfection 2450) with both the > epson and epkowa backends. Note that these same backends work fine > with the GT-8200 (aka Perfection 1650) under identical conditions. > > Just starting a SANE frontend (tried with xsane and iscan) with the > GT-9700 already takes "ages" and it just refuses to preview. Aha. That's not at all what I expected - many apologies to any slighted libusb developer! Like I said, you can get it to work by calling usb_reset() whenever the scanner device is closed. My hacked code for sanei_usb_close() (in sanei/sanei_usb.c) is below. I hope you don't need it :) > Looks like Karl and/or I have some digging to do ;-( Maybe. It would be very interesting to know what's wrong. Is it perhaps that the scanner needs to be send a message before it is closed. Many thanks, Tom ----------------------------------------------------------- ----------------------------------------------------------- void sanei_usb_close (SANE_Int dn) { DBG (5, "sanei_usb_close: closing device %d\n", dn); if (dn >= MAX_DEVICES || dn < 0) { DBG (1, "sanei_usb_close: dn >= MAX_DEVICES || dn < 0\n"); return; } if (!devices[dn].open) { DBG (1, "sanei_usb_close: device %d already closed or never opened\n", dn); return; } if (devices[dn].method == sanei_usb_method_scanner_driver) close (devices[dn].fd); else #ifdef HAVE_LIBUSB { #if 0 /* Should only be done in case of a stall */ usb_clear_halt (devices[dn].libusb_handle, devices[dn].bulk_in_ep); usb_clear_halt (devices[dn].libusb_handle, devices[dn].bulk_out_ep); /* be careful, we don't know if we are in DATA0 stage now */ usb_resetep(devices[dn].libusb_handle, devices[dn].bulk_in_ep); usb_resetep(devices[dn].libusb_handle, devices[dn].bulk_out_ep); #endif /* HACK FOR PERFECTION 2450 */ usb_reset(devices[dn].libusb_handle) ; usb_release_interface (devices[dn].libusb_handle, devices[dn].interface_nr); usb_close (devices[dn].libusb_handle); } #else DBG (1, "sanei_usb_close: libusb support missing\n"); #endif devices[dn].open = SANE_FALSE; return; } ------------------------------------------------------------------ ------------------------------------------------------------------ From l.riso at tiscalinet.it Fri Jun 11 06:20:53 2004 From: l.riso at tiscalinet.it (Luca) Date: Fri, 11 Jun 2004 07:20:53 +0200 Subject: [sane-devel] Sonix SN9C101 and SN9C102 USB camera controllers - specifications Message-ID: <20040611072053.6e714b6a.l.riso@tiscalinet.it> I have been told by the TWAIN people that this is the best place where to ask for the detailed specifications of the above chips. Any help would be much appreciated. Sonix does not respond to my emails and google does not help (there's a 12-page long datasheets, but it is not detailed enough to write a driver) Thanks, please answer to l.riso at tiscalinet.it From benthos at lqjr.qc.ca Fri Jun 11 15:00:36 2004 From: benthos at lqjr.qc.ca (Benjamin Lawetz) Date: Fri, 11 Jun 2004 10:00:36 -0400 (EDT) Subject: [sane-devel] finally got UDS-IS11 working (Error in FAQ) Message-ID: Hi, I finally got the el cheapo SCSI card that came with my UMAX scanner to work. I was surprised to find instructions in your FAQ to get the card working (last time I had checked, everyone told me it was a lost cause) I tried without success, trying to insert it as a module (I think like the FAQ said, but I'm not sure) it worked, but no way to get in working in a monolithic kernel. After a checking the source, it seemed the driver wanted it's kernel options from dtc3181e, the FAQ mentionned dtc_3181e Once the little underscore removed, it worked like a charm. (I don't know if it changed for kernel 2.6, but maybe update the FAQ to help others down the line). Thanks for all your great work guys ! -- \\\|/// \\ - - // ( @ @ ) ---oOOo-(_)-oOOo------------------------------- If you suspect a man, don't employ him. --------------Oooo----------------------------- oooO ( ) Benjamin Benthos Lawetz ( ) ) / mailto:Benjamin.Lawetz at lqjr.qc.ca \ ( (_/ ICQ# 4269530 \_) From epl at unimelb.edu.au Fri Jun 11 15:30:46 2004 From: epl at unimelb.edu.au (epl at unimelb.edu.au) Date: Sat, 12 Jun 2004 00:30:46 +1000 (EST) Subject: [sane-devel] epson 2400 neg scans Message-ID: > The Perfection 1670 and the 2400 look interesting. It appears that the > former is not supported by sane and runs on a different chip set to > other Perfection scanners so I'll stike that from the list. > Peter, I've got an Epson Perfection 1670 Photo and I'd be glad to answer any questions you (or anyone else on this mailing list) have. Please Cc me as I haven't subscribed to this list. Pros: - Works under both Linux's scanner kernel module and libusb. - I've gotten it to work under both Debian unstable (very easy, glorious apt-get) and Red Hat 9.0 (heavily mangled with alien-converted debs). - I was also able to get the Epson firmware file using unshield (CVS version from the synce project). Else, you can get it from: http://www.commercialventvac.com/~jeffs/epson1670andFedora.html - Flatbed scanning (ie not transparency) works even up to the maximum resolution of 1600dpi. Jeff's result (above) maybe caused by the older sane-backend-1.0.13 -- shrugs. - The transparency scanning works to the extent that the fluorescence light can be controlled from sane. Cons: - A bit expensive IMHO. - The four scanner buttons doesn't have any effect. - Film scanning seems to introduce fine lines (only noticeable at high resolutions) that isn't due to the negative. - Not sure which component is at fault, but the colour of the film/negatives aren't properly calibrated. As far as I'm concerned, film scanning of the 1670 isn't usable under sane. Of course, it is distinctly possible that I haven't got things setup correctly as I've never played with film (35mm Kodak) scanning before. It is also possible that the CVS version of sane-backend fixes some of the above problems (currently using 1.0.14). BTW, thank you to the developers who integrated 1670 support into sane. Cheers Eddie From gerard at gkall.hobby.nl Sat Jun 12 02:31:59 2004 From: gerard at gkall.hobby.nl (gerard klaver) Date: Sat, 12 Jun 2004 01:31:59 +0000 Subject: [sane-devel] Sonix SN9C101 and SN9C102 USB camera controllers - specifications In-Reply-To: <20040611072053.6e714b6a.l.riso@tiscalinet.it> References: <20040611072053.6e714b6a.l.riso@tiscalinet.it> Message-ID: <1087003919.1488.4.camel@gk-lex3> On Fri, 2004-06-11 at 05:20, Luca wrote: > I have been told by the TWAIN people that this is the best place > where to ask for the detailed specifications of the above chips. > Any help would be much appreciated. Sonix does not respond to my emails > and google does not help (there's a 12-page long datasheets, but it is > not detailed enough to write a driver) > > Thanks, please answer to l.riso at tiscalinet.it Depends what sort of driver you want to write, kernel module or SANE backend. See also these links: http://www.mnementh.co.uk/sonix/ and http://sonix.sourceforge.net/ -- ---------- m.vr.gr. Gerard Klaver From david at 2gen.com Sat Jun 12 12:03:29 2004 From: david at 2gen.com (David =?iso-8859-1?Q?H=E4rdeman?=) Date: Sat, 12 Jun 2004 13:03:29 +0200 Subject: [sane-devel] Re: [Linux-usb-users] Problems with HP 6200C scanner and SANE In-Reply-To: References: <40BB5315.5000508@2gen.com> Message-ID: <20040612110326.GC652@hardeman.nu> On Mon, May 31, 2004 at 02:58:12PM -0400, Alan Stern wrote: >On Mon, 31 May 2004, David H?rdeman wrote: >> I'm currently trying to get an HP 6200C USB scanner to work with SANE >> (1.0.14) under Linux (Debian woody with some backports, kernel 2.4.26). >> Whenever I scan something which requires a low amount of data (lineart >> picture at 100dpi for instance), everything works just fine. But when I >> scan a more bandwidth hungry pic, it never succeeds. I've tried this >> both with the "scanner" module in the kernel and with libusb but both >> seem to experience the same problems. >> >> I have tried sane's "dumb-read" option and all other option which were >> mentioned in the sane-hp man page but I'm running out of ideas. Any >> clues what might cause this (might later kernels be too picky with their >> timing requirements)? > >The most likely explanation is that some other program (possibly a hotplug >utility) is trying to access the scanner while you're using it, thereby >confusing the scanner and causing it to fail. I've seen reports from >other people where the "usbmodules" program did this. See what happens if >you turn off all hotplug support. Hi, and sorry for the delay in answering. I am running this on Debian Woody (with backported usblib and sane packages of recent versions), so there is no hotplug support on the system, the only other thing I could think of is the "nut" UPS daemon which checks the status of the UPS over USB. However, disabling nut and trying to scan did not help sort out the problem. Any other suggestions? Re, David From klemens.dickbauer at msk-informatik.at Sun Jun 13 00:27:28 2004 From: klemens.dickbauer at msk-informatik.at (Klemens Dickbauer) Date: Sun, 13 Jun 2004 01:27:28 +0200 Subject: [sane-devel] JSane In-Reply-To: References: Message-ID: <200406130127.28342.klemens.dickbauer@msk-informatik.at> Hi David, Hi Andi and Chris! After being off for quite a long time (sorry for not communicating!) I restarted my work on japi_sane again this week. The classes I have are based on the work of Silvio Vogt and what I did is mainly some refactoring work (moving into the org.saneproject package structure, moving into a interface/implementation classes desgin, changes on the gui part...). It's still ongoing, but at least I can compile it again. I just read all the messages on this list an realized that a few people are working on the same issue. Your approch, Andi, seems very promising to me using the TCP level to communicate, coding JNI is very hard for me unexperienced bloke. (-; Anyway, having a direct Java interface to the sane libs seems also desireable to me. David, what do you think about the changes I suggest? I had no close look into your classes so far, but I'll do tomorrow. Are you planning something more on these? I will include my few classes, though thei're not running yet. I get a segfault on every call, as I said before I am very unexperienced in system programming. Maybe someone can give me a hint on where to start. -- An unexpected exception has been detected in native code outside the VM. Unexpected Signal : 11 occurred at PC=0x4DE37B06 Function=sane_dll_control_option+0x56 Library=/usr/lib/libsane.so.1 Current Java thread: at org.saneproject.scan.sane.Sane.getControlOption(Native Method) [..] -- bye for now, ~klemens Am Mittwoch, 9. Juni 2004 13:54 schrieb David Neary: > Hi all, > > I know that some people were asking about a Java SANE API > recently. > > I did some work before 1.0.14 on getting it at least > compiling with at least a Sun SDK, and have since been > quite happily using these JNI bindings. There are still > some bugs in here, notably for lineart mode, and I have > been unashamedly messing about with stuff to make it work > just for me, for one particular task, so it's probably > not pretty. > > But perhaps people who need something now will be happy > with it. > > This is simply a tar of the japi directory after I did > a make clean. I also have a dllmain.c and a project file > for making a sanej.dll for Windows, if anyone would like > those. This is more or less untested, and ymmv. > > I also have a tarball of the javadocs, but I didn't do > anything particular to generate them except run javadoc > so there's no real point in sending those to the list. > > Cheers, > Dave. > > -- > David Neary > Phenix Engineering > 110 ave Jean Jaures, 69007 Lyon -- Klemens Dickbauer, MSK Informatik GesmbH A-1160 Wien, Zeillergasse 5/309 From vykk3 at comcast.net Sun Jun 13 01:24:52 2004 From: vykk3 at comcast.net (Victoria Welch) Date: Sat, 12 Jun 2004 17:24:52 -0700 Subject: [sane-devel] Help :-)! 2.6.5 kernel/ Agfa SnapScan 1212u USB - I'm lost :-(. Message-ID: <200406121724.52915.vykk3@comcast.net> Hi All and Thanks in advance! I've been trying to resolve this for the past two days and am turning to this list out of desperation, I'm completely baffled :-(. The scanner is fully supported according to the lists of suppored devices on the sane site. I'm not sure if the following is all the info needed, but as noted I am thoroughly confused at this point. The scanner is seen is /proc/bus/usb/devices: T: Bus=03 Lev=01 Prnt=01 Port=01 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=06bd ProdID=2061 Rev= 1.1e S: Manufacturer=AGFA S: Product= Snapscan1212u_2 C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA 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= 8 Ivl=0ms E: Ad=83(I) Atr=03(Int.) MxPS= 8 Ivl=16ms The docs make reference to a needed kernel driver, but if one exists in the kernel config I do not recognize it (per above: I: [ ... ] Driver=(none). I have emerged the sane back ends and xsane. I thought perhaps I needed the following in /etc/sane.d/snapscan.conf file: #------------------------------ General ----------------------------------- # Change to the fully qualified filename of your firmware file, if # firmware upload is needed by the scanner firmware /usr/lib/sane/SnapScan_1212U_2.bin [ ... ] I'm still not sure if it is necessary or not. Whatever is going on here, nothing in /dev gets created in any form I would recognize as to having to do with a scanner. All other USB devices are working fine (Joystick, usb filesystem camera and A Palm Pilot USB cradle) and the appropriate /dev entries exist. I've read until my eyes ache :-) and googled on everything I could think of that would help me resolve this issue. I'm embarrased to admit that I came up with nothing that seems to have been helpful, I have to have missed something there somewhere, maybe multiple times :-(. The only "progress" I get is that sane seems to pickup my tv tuner card which xsane won't work with anyhow and it is rather useless for scanning stuff this way :-). Any help, suggestions or pointers *greatly* appreciated. Thanks & take care, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From kpschrage at gmx.de Sun Jun 13 10:59:38 2004 From: kpschrage at gmx.de (Klaus-Peter Schrage) Date: Sun, 13 Jun 2004 11:59:38 +0200 Subject: [sane-devel] Help :-)! 2.6.5 kernel/ Agfa SnapScan 1212u USB - I'm lost :-(. In-Reply-To: <200406121724.52915.vykk3@comcast.net> References: <200406121724.52915.vykk3@comcast.net> Message-ID: <40CC258A.7020406@gmx.de> Victoria Welch wrote: > The docs make reference to a needed kernel driver, but if > one exists in the kernel config I do not recognize it (per > above: I: [ ... ] Driver=(none). > > I have emerged the sane back ends and xsane. I thought > perhaps I needed the following in /etc/sane.d/snapscan.conf > file: > > #------------------------------ General > ----------------------------------- > > # Change to the fully qualified filename of your firmware > file, if > # firmware upload is needed by the scanner > firmware /usr/lib/sane/SnapScan_1212U_2.bin > [ ... ] > > I'm still not sure if it is necessary or not. > > Whatever is going on here, nothing in /dev gets created in > any form I would recognize as to having to do with a > scanner. I have been using this very AGFA scanner for years in Linux, and it is really well supported. But with the 2.6 kernel series, the rationale has changed: no more kernel modules or /dev's, bus the scanner is addressed via libusb. So what does sane-find-scanner given in a console, reply? If you read something like: found USB scanner (vendor=0x06bd [AGFA], product=0x2061 [ Snapscan1212u_2]) at libusb:002:002 then your scanner is recognized and may be adressed by xsane or so via libusb. If not, then you probably don't have sane-frontends and/or libusb, so get it. The next step should be scanimage -L If you DON'T read device `snapscan:libusb:002:002' is a AGFA SNAPSCAN 1212U_2 flatbed scanner try the same as root. If there's success at last, then there is a permissions issue that allows only root to access the scanner. Getting it to work for normal users is another story ... As to the 'firmware' line in snapscan.conf: It's ok and should be there (if the .bin file really is in the indicated location) Klaus From jb at jblache.org Sun Jun 13 12:47:59 2004 From: jb at jblache.org (Julien BLACHE) Date: Sun, 13 Jun 2004 13:47:59 +0200 Subject: [sane-devel] Epson backend fix wrt USB IDs for Perfection 1250 and 1260 Message-ID: <87wu2bn0gg.fsf@frigate.technologeek.org> Hi, It seems the fix that went in regarding the USB IDs for Perfection 1250 and 1260 erroneously removed the USB IDs for the Perfection 1650 instead of removing the USB IDs for the Perfection 1250. khk ? (noticed by S?bastien Villemot) JB. -- Julien BLACHE GPG KeyID 0xF5D65169 From khk at khk.net Sun Jun 13 13:42:00 2004 From: khk at khk.net (Karl Heinz Kremer) Date: Sun, 13 Jun 2004 08:42:00 -0400 Subject: [sane-devel] Epson backend fix wrt USB IDs for Perfection 1250 and 1260 In-Reply-To: <87wu2bn0gg.fsf@frigate.technologeek.org> References: <87wu2bn0gg.fsf@frigate.technologeek.org> Message-ID: <10998AE0-BD37-11D8-80D6-000A957E40E8@khk.net> Thanks. Looks like I picked the wrong line. I added the 1650 back in and finally removed the 1250. On Jun 13, 2004, at 7:47 AM, Julien BLACHE wrote: > Hi, > > It seems the fix that went in regarding the USB IDs for Perfection > 1250 and 1260 erroneously removed the USB IDs for the Perfection 1650 > instead of removing the USB IDs for the Perfection 1250. > > khk ? > > (noticed by S?bastien Villemot) > > JB. > > -- > Julien BLACHE > > GPG KeyID 0xF5D65169 > > -- > sane-devel mailing list: sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-request at lists.alioth.debian.org From andi.mclean at ntlworld.com Sun Jun 13 15:25:56 2004 From: andi.mclean at ntlworld.com (Andi McLean) Date: Sun, 13 Jun 2004 15:25:56 +0100 Subject: [sane-devel] JSane In-Reply-To: <200406130127.28342.klemens.dickbauer@msk-informatik.at> References: <200406130127.28342.klemens.dickbauer@msk-informatik.at> Message-ID: <200406131525.56730.andi.mclean@ntlworld.com> Hi , On Sunday 13 June 2004 00:27, Klemens Dickbauer wrote: > Hi David, Hi Andi and Chris! > > After being off for quite a long time (sorry for not communicating!) I > restarted my work on japi_sane again this week. > The classes I have are based on the work of Silvio Vogt and what I did is > mainly some refactoring work (moving into the org.saneproject package > structure, moving into a interface/implementation classes desgin, changes > on the gui part...). It's still ongoing, but at least I can compile it > again. > I have designed a structure to split interface and implementation how does everyone feel about these? Dave what do you think about putting the JNI part in with my code? Does it fit with the design I've created? If not we can discuss what changes are needed. I designed the structure to mainly meet my needs but tried to make it so that a JNI, or other implementation could be used. As I needed to get it working for my main project. > I just read all the messages on this list an realized that a few people are > working on the same issue. Your approch, Andi, seems very promising to me > using the TCP level to communicate, coding JNI is very hard for me > unexperienced bloke. (-; I found the JNI difficult too, and needed to be able to port the client stuff to different hardware at a moments notice, so I went with a pure java implementation. As I said, I've tried to create the framework so it can accomodate other implementations. > Anyway, having a direct Java interface to the sane libs seems also > desireable to me. David, what do you think about the changes I suggest? I > had no close look into your classes so far, but I'll do tomorrow. Are you > planning something more on these? > > I will include my few classes, though thei're not running yet. I get a > segfault on every call, as I said before I am very unexperienced in system > programming. Maybe someone can give me a hint on where to start. > -- > An unexpected exception has been detected in native code outside the VM. > Unexpected Signal : 11 occurred at PC=0x4DE37B06 > Function=sane_dll_control_option+0x56 > Library=/usr/lib/libsane.so.1 > > Current Java thread: > at org.saneproject.scan.sane.Sane.getControlOption(Native Method) > [..] > -- > > bye for now, > ~klemens > > Am Mittwoch, 9. Juni 2004 13:54 schrieb David Neary: > > Hi all, > > > > I know that some people were asking about a Java SANE API > > recently. > > > > I did some work before 1.0.14 on getting it at least > > compiling with at least a Sun SDK, and have since been > > quite happily using these JNI bindings. There are still > > some bugs in here, notably for lineart mode, and I have > > been unashamedly messing about with stuff to make it work > > just for me, for one particular task, so it's probably > > not pretty. > > > > But perhaps people who need something now will be happy > > with it. > > > > This is simply a tar of the japi directory after I did > > a make clean. I also have a dllmain.c and a project file > > for making a sanej.dll for Windows, if anyone would like > > those. This is more or less untested, and ymmv. > > > > I also have a tarball of the javadocs, but I didn't do > > anything particular to generate them except run javadoc > > so there's no real point in sending those to the list. > > > > Cheers, > > Dave. > > > > -- > > David Neary > > Phenix Engineering > > 110 ave Jean Jaures, 69007 Lyon > > -- > Klemens Dickbauer, MSK Informatik GesmbH > A-1160 Wien, Zeillergasse 5/309 From l.riso at tiscalinet.it Sat Jun 12 03:39:40 2004 From: l.riso at tiscalinet.it (Luca) Date: Sat, 12 Jun 2004 04:39:40 +0200 Subject: [sane-devel] Sonix SN9C101 and SN9C102 USB camera controllers - specifications In-Reply-To: <1087003919.1488.4.camel@gk-lex3> References: <20040611072053.6e714b6a.l.riso@tiscalinet.it> <1087003919.1488.4.camel@gk-lex3> Message-ID: <20040612043940.2f154bbb.l.riso@tiscalinet.it> On Sat, 12 Jun 2004 01:31:59 +0000 gerard klaver wrote: > On Fri, 2004-06-11 at 05:20, Luca wrote: > > I have been told by the TWAIN people that this is the best place > > where to ask for the detailed specifications of the above chips. > > Any help would be much appreciated. Sonix does not respond to my emails > > and google does not help (there's a 12-page long datasheets, but it is > > not detailed enough to write a driver) > > > > Thanks, please answer to l.riso at tiscalinet.it > > Depends what sort of driver you want to write, kernel module or SANE > backend. > > See also these links: > http://www.mnementh.co.uk/sonix/ > > and > http://sonix.sourceforge.net/ That's the unuseful thing I was talking about From philip at digitalinfinity.biz Fri Jun 11 09:52:33 2004 From: philip at digitalinfinity.biz (Philip V. Neves) Date: Fri, 11 Jun 2004 01:52:33 -0700 Subject: [sane-devel] I can't get my scanner to work. Message-ID: <40C972D1.2060303@digitalinfinity.biz> I am trying to get my scanner to work with sane. I have a Canon LIDE20 usb scanner. sane-find-scanner sees the scanner but when I run scanimage -L nothing comes up. Its as if the scanner isn't there. 77 Here is what I get when I run sane-find-scanner. If someone could please point me in the right direction I would greately appreciateit. trying libusb: bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 () iProduct 2 (USB UHCI-alt Root Hub) iSerialNumber 1 (d400) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 8 bInterval 255 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 255 bDeviceSubClass 0 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x04A9 idProduct 0x220D bcdDevice 1.00 iManufacturer 1 (Canon) iProduct 2 (CanoScan) iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 160 (Remote Wakeup) MaxPower 500 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 bInterfaceSubClass 0 bInterfaceProtocol 255 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 1 bInterval 16 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 checking for GT-6801 ... this is not a GT-6801 (bDeviceSubClass = 0x0) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bcdUSB = 0x110) checking for MA-1509 ... this is not a MA-1509 (bDeviceSubClass = 0x0) checking for LM983[1,2,3] ... Couldn't claim interface: could not claim interface 0: Device or resource busy found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan], chip=LM983x?) at libusb:001:002 bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046D idProduct 0xC20C bcdDevice 1.03 iManufacturer 1 (Logitech) iProduct 2 (WingMan Precision USB) iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 128 () MaxPower 30 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 3 bInterval 10 ms bRefresh 0 bSynchAddress 0 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. -- --------------------------------------------------------------- Philip V. Neves Email: philip at digitalinfinity.biz Phone: (250)372-8536 pneves at telus.net --------------------------------------------------------------- Nearly every man who develops an idea works at it up to the point where it looks impossible, and then gets discouraged. that's not the place to become discouraged. Thomas Alva Edison. From insane at piments.com Sun Jun 13 19:31:49 2004 From: insane at piments.com (insane at piments.com) Date: Sun, 13 Jun 2004 20:31:49 +0200 Subject: [sane-devel] epson 2400 neg scans In-Reply-To: References: Message-ID: Thanks for the detailed info on the 1670 photo. It seems odd that there are lines on the neg scan that are not on normal flatbed mode, I suppose it could just be a bug in the backend that it not picking up intermediate scan lines. You say that this only happens on high res but later that higher res is not availible on transparency. Could you be more specific? I sounds a bit contradictory. What res. works correctly (no lines) and what is the max you can scan a neg. even if the output is poor? Thanks for your help. Peter. On Sat, 12 Jun 2004 00:30:46 +1000 (EST), wrote: >> The Perfection 1670 and the 2400 look interesting. It appears that the >> former is not supported by sane and runs on a different chip set to >> other Perfection scanners so I'll stike that from the list. >> > Peter, > I've got an Epson Perfection 1670 Photo and I'd be glad to answer any > questions you (or anyone else on this mailing list) have. Please Cc me as > I haven't subscribed to this list. > > Pros: > - Works under both Linux's scanner kernel module and libusb. > - I've gotten it to work under both Debian unstable (very easy, glorious > apt-get) and Red Hat 9.0 (heavily mangled with alien-converted debs). > - I was also able to get the Epson firmware file using unshield (CVS > version from the synce project). Else, you can get it from: > http://www.commercialventvac.com/~jeffs/epson1670andFedora.html > - Flatbed scanning (ie not transparency) works even up to the maximum > resolution of 1600dpi. Jeff's result (above) maybe caused by the older > sane-backend-1.0.13 -- shrugs. > - The transparency scanning works to the extent that the fluorescence > light can be controlled from sane. > > Cons: > - A bit expensive IMHO. > - The four scanner buttons doesn't have any effect. > - Film scanning seems to introduce fine lines (only noticeable at high > resolutions) that isn't due to the negative. > - Not sure which component is at fault, but the colour of the > film/negatives aren't properly calibrated. > > As far as I'm concerned, film scanning of the 1670 isn't usable under > sane. Of course, it is distinctly possible that I haven't got things > setup > correctly as I've never played with film (35mm Kodak) scanning before. It > is also possible that the CVS version of sane-backend fixes some of the > above problems (currently using 1.0.14). > > BTW, thank you to the developers who integrated 1670 support into sane. > > Cheers > Eddie > > > -- Using M2, Opera's e-mail client: on Gentoo Linux From vykk3 at comcast.net Sun Jun 13 21:05:24 2004 From: vykk3 at comcast.net (Victoria Welch) Date: Sun, 13 Jun 2004 13:05:24 -0700 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! Message-ID: <200406131305.24125.vykk3@comcast.net> Hi folks! Just to let everyone know after about the 7,858,939,058th :-) google I found something that REALLY helped get me going! http://users.dslextreme.com/~craig.lawson/linux_notes/gentoo.2004.0.html The big secret was that I had to build sane/sane backends with: USE="usb" emerge sane-backends After that the scanner showed up and works GREAT! Happy, happy, joy, joy :-) :-) :-) ! Now I can dump the w98 partition with extreme prejudice and save that plustek for a trip to the shooting range :-). Klaus: Especially, thanks for the encouragement to keep me plugging away at it, turns out to have been well worth it. Really nice scanner under linux! Thanks & take care es 73, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From vykk3 at comcast.net Sun Jun 13 23:38:10 2004 From: vykk3 at comcast.net (Victoria Welch) Date: Sun, 13 Jun 2004 15:38:10 -0700 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! In-Reply-To: <20040613212021.GA16490@braveman.lan> References: <200406131305.24125.vykk3@comcast.net> <20040613212021.GA16490@braveman.lan> Message-ID: <200406131538.10735.vykk3@comcast.net> Hello Philipp, Thanks for the response! On Sunday 13 June 2004 14:20, root wrote: > > [ ... ] > > The big secret was that I had to build sane/sane > > backends with: > > > > USE="usb" emerge sane-backends > > try the '--verbose' option of emerge. this can help a > lot. and sometimes you can see a description of the > use-flags with 'etcat uses '. Thanks for that pointer. Love gentoo but there is indeed a bit to learn :-). Now if I can get it working as other than root, we'll be there. xsane insists on picking up that tv tuner card no matter what. I even copied over the AGFA:SNAPSCAN.drc over to my .sane directory and it is roundly ignored :-). Thanks & take care, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From vykk3 at comcast.net Sun Jun 13 23:53:21 2004 From: vykk3 at comcast.net (Victoria Welch) Date: Sun, 13 Jun 2004 15:53:21 -0700 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! In-Reply-To: <200406131538.10735.vykk3@comcast.net> References: <200406131305.24125.vykk3@comcast.net> <20040613212021.GA16490@braveman.lan> <200406131538.10735.vykk3@comcast.net> Message-ID: <200406131553.21883.vykk3@comcast.net> Great progress here today :-) On Sunday 13 June 2004 15:38, Victoria Welch wrote: > > Now if I can get it working as other than root, we'll be > there. xsane insists on picking up that tv tuner card no > matter what. I even copied over the AGFA:SNAPSCAN.drc > over to my .sane directory and it is roundly ignored :-). Turns out there is now a group "scanner". Added myself to that, logged out and back in and we were in business. I still have to choose between the tv tuner card and the flatbed. Would be just as happy if the tv tuner didn't show up since xsane doesn't seem to like it enough to do anything with it. If you delete the .drc for the tv card, it re-establishes itself as soon as you run xsane :-(. -d, --device-settings file load device settings from file (without ".drc") Seems to be ignored :-(. One last thing to fix now, but I can live with it if I have to. Any thoughts on this one appreciated. Thanks & take care, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From kaplanam1 at comcast.net Mon Jun 14 01:08:09 2004 From: kaplanam1 at comcast.net (Allan Kaplan) Date: Sun, 13 Jun 2004 17:08:09 -0700 Subject: [sane-devel] SANE driver for NEC Petiscan scanner Message-ID: Greetings again, Here is the progress I have made: The sketchy results of sane-find-scanner -v -v follow. NEC drivers for Win 95, 98, ME, 2000 (apparently), and MacOS 9.x (they say X, but not true) are at . The filenames are English even though this is a Japanese page. The files are the "8u3" files. At the bottom of the page is a link to "MultiReaderPetiScan800U2" which is the previous version of the PC drivers. As far as I can tell, without further digging into the guts of the scanner, there are two chips which say JIC (?) ES52099S 9919-LHIJ I was not able to find data on this chip. And Winbond W24512AJ-15 919SA290732601CE Chip specs: It occurred to me that this scanner will run off another computer I have access to, but only in MacOS9. Might there more data that I can access from a computer that will actually run the scanner, versus this laptop with which I want to ultimately run the scanner, but only uses MacOSX? Thanks everyone for your help. Please advise me on the next step I can take in this project. Allan bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 255 bDeviceSubClass 0 bDeviceProtocol 255 bMaxPacketSize0 8 idVendor 0x0475 idProduct 0x0100 bcdDevice 1.00 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 128 () MaxPower 500 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 255 bInterfaceSubClass 255 bInterfaceProtocol 255 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x01 (out 0x01) bmAttributes 2 (bulk) wMaxPacketSize 8 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 8 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 0 ms bRefresh 0 bSynchAddress 0 checking for GT-6801 ... this is not a GT-6801 (bcdUSB = 0x100) checking for GT-6816 ... this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1017 ... this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) checking for MA-1015 ... this is not a MA-1015 (bDeviceSubClass = 0x0) checking for MA-1509 ... this is not a MA-1509 (bcdUSB = 0x100) checking for LM983[1,2,3] ... this is not a LM983x (bEndpointAddress = 0x1, bmAttributes = 0x2, wMaxPacketSize = 0x8, bInterval = 0x0) checking for GL646 ... this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL646_HP ... this is not a GL646_HP (bcdUSB = 0x100) checking for GL660+GL646 ... this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255) checking for GL841 ... this is not a GL841 (bcdUSB = 0x100) checking for ICM532B ... check 2, this is not a ICM532B (bcdUSB = 0x100) found USB scanner (vendor=0x0475, product=0x0100) at libusb:003:002-0475-0100-ff-00 From henning at meier-geinitz.de Mon Jun 14 10:19:20 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 14 Jun 2004 11:19:20 +0200 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! In-Reply-To: <200406131553.21883.vykk3@comcast.net> References: <200406131305.24125.vykk3@comcast.net> <20040613212021.GA16490@braveman.lan> <200406131538.10735.vykk3@comcast.net> <200406131553.21883.vykk3@comcast.net> Message-ID: <20040614091920.GD8899@meier-geinitz.de> Hi, On Sun, Jun 13, 2004 at 03:53:21PM -0700, Victoria Welch wrote: > I still have to choose between the tv tuner card and the > flatbed. Would be just as happy if the tv tuner didn't > show up since xsane doesn't seem to like it enough to do > anything with it. If you delete the .drc for the tv card, > it re-establishes itself as soon as you run xsane :-(. To disable v4l completely, edit /etc/sane.d/dll.conf and comment out "v4l". To start xsane with your scanner directly (without chosing): xsane yourbackend (e.g. xsane plustek). > -d, --device-settings file load device settings from file > (without ".drc") > > Seems to be ignored :-(. Really? It justs loads the settings for one device. It doesn't set the default device to use. Bye, Henning From henning at meier-geinitz.de Mon Jun 14 10:36:50 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 14 Jun 2004 11:36:50 +0200 Subject: [sane-devel] I can't get my scanner to work. In-Reply-To: <40C972D1.2060303@digitalinfinity.biz> References: <40C972D1.2060303@digitalinfinity.biz> Message-ID: <20040614093650.GE8899@meier-geinitz.de> Hi, On Fri, Jun 11, 2004 at 01:52:33AM -0700, Philip V. Neves wrote: > I am trying to get my scanner to work with sane. I have a Canon LIDE20 > usb scanner. sane-find-scanner sees the scanner but when I run scanimage > -L nothing comes up. Its as if the scanner isn't there. > 77 > Here is what I get when I run sane-find-scanner. If someone could please > point me in the right direction I would greately appreciateit. Which operating system and version are you using? Which SANE version? [...] > [...] > > checking for GT-6801 ... > this is not a GT-6801 (bDeviceSubClass = 0x0) > checking for GT-6816 ... > this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255) > checking for MA-1017 ... > this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255) > checking for MA-1015 ... > this is not a MA-1015 (bcdUSB = 0x110) > checking for MA-1509 ... > this is not a MA-1509 (bDeviceSubClass = 0x0) > checking for LM983[1,2,3] ... > Couldn't claim interface: could not claim interface 0: Device or > resource busy > Something else is caliming the scanner. So either another program has already opened the scanner or there is a kernel bug. Or you are using Linux 2.4 and the kernel scanner driver has claimed the scanner. SANE_DEBUG_PLUSTEK=255 scanimage -L will print why scanimage doesn't detect the scanner. But I guess it's the same problem: device busy. Bye, Henning From henning at meier-geinitz.de Mon Jun 14 10:49:43 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 14 Jun 2004 11:49:43 +0200 Subject: [sane-devel] SANE driver for NEC Petiscan scanner In-Reply-To: References: Message-ID: <20040614094943.GG8899@meier-geinitz.de> Hi, On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: > As far as I can tell, without further digging into the guts of the scanner, > there are two chips which say > > JIC (?) > ES52099S > 9919-LHIJ > I was not able to find data on this chip. Google finds some references but no spec or explanation. > Winbond > W24512AJ-15 > 919SA290732601CE > Chip specs: > So that's RAM. No other chips? In this c ase the JIC must be the scan chip. > It occurred to me that this scanner will run off another computer I have > access to, but only in MacOS9. Might there more data that I can access from > a computer that will actually run the scanner, versus this laptop with which > I want to ultimately run the scanner, but only uses MacOSX? You need software that can listen to the USB commands send to the scanner ("sniffer"). While some programs are available for Windows I don't know if that's the case for MacOS9. Bye, Henning From Francois.Patte at math-info.univ-paris5.fr Mon Jun 14 11:18:17 2004 From: Francois.Patte at math-info.univ-paris5.fr (=?iso-8859-1?b?RnJhbudvaXM=?= Patte) Date: Mon, 14 Jun 2004 12:18:17 +0200 Subject: [sane-devel] scanner HP 4600 In-Reply-To: <20040614094943.GG8899@meier-geinitz.de> References: <20040614094943.GG8899@meier-geinitz.de> Message-ID: <1087208297.40cd7b69d643d@www.math-info.univ-paris5.fr> Bonjour, Is it possible to have a Hewlett-Packard Scanjet 4600 working under linux with sane? Thank you -- Fran?ois Patte Inde : Ecole fran?aise d'Extr?me-Orient Deccan College Pune 411006 T?l : (00 91) (0) 20 26 69 39 04 France : Universit? Ren? Descartes - Paris 5 UFR de math?matiques et informatique http://www.math-info.univ-paris5.fr/~patte From henning at meier-geinitz.de Mon Jun 14 11:28:18 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 14 Jun 2004 12:28:18 +0200 Subject: [sane-devel] scanner HP 4600 In-Reply-To: <1087208297.40cd7b69d643d@www.math-info.univ-paris5.fr> References: <20040614094943.GG8899@meier-geinitz.de> <1087208297.40cd7b69d643d@www.math-info.univ-paris5.fr> Message-ID: <20040614102818.GA1991@meier-geinitz.de> Hi, On Mon, Jun 14, 2004 at 12:18:17PM +0200, Fran?ois Patte wrote: > Is it possible to have a Hewlett-Packard Scanjet 4600 working under linux with > sane? No. At least that's what our search engine says: http://www.sane-project.org/cgi-bin/driver.pl?manu=hew&model=4600&bus=any Bye, Henning From kaplanam1 at comcast.net Mon Jun 14 18:14:01 2004 From: kaplanam1 at comcast.net (Allan Kaplan) Date: Mon, 14 Jun 2004 10:14:01 -0700 Subject: [sane-devel] Re: SANE driver for NEC Petiscan scanner In-Reply-To: <20040614125025.7832.46018.Mailman@haydn.debian.org> Message-ID: Greetings, OK, I managed to take the scanner apart without damaging it, and found the the big chip hiding under a cover. TIS 2AX000 59S1998 F8W07-000 9939 I will see what other info I can find. Thanks, Allan > Message: 3 > Date: Mon, 14 Jun 2004 11:49:43 +0200 > From: Henning Meier-Geinitz > To: sane-devel at lists.alioth.debian.org > Subject: Re: [sane-devel] SANE driver for NEC Petiscan scanner > > Hi, > > On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: >> As far as I can tell, without further digging into the guts of the scanner, >> there are two chips which say >> >> JIC (?) >> ES52099S >> 9919-LHIJ >> I was not able to find data on this chip. > > Google finds some references but no spec or explanation. > >> Winbond >> W24512AJ-15 >> 919SA290732601CE >> Chip specs: >> > > So that's RAM. No other chips? In this c ase the JIC must be the scan > chip. > >> It occurred to me that this scanner will run off another computer I have >> access to, but only in MacOS9. Might there more data that I can access from >> a computer that will actually run the scanner, versus this laptop with which >> I want to ultimately run the scanner, but only uses MacOSX? > > You need software that can listen to the USB commands send to the > scanner ("sniffer"). While some programs are available for Windows I > don't know if that's the case for MacOS9. > > Bye, > Henning > > From vykk3 at comcast.net Mon Jun 14 18:37:06 2004 From: vykk3 at comcast.net (Victoria Welch) Date: Mon, 14 Jun 2004 10:37:06 -0700 Subject: [sane-devel] Success! 2.6.5 kernel, Agfa Snapscan 1212u! In-Reply-To: <20040614091920.GD8899@meier-geinitz.de> References: <200406131305.24125.vykk3@comcast.net> <200406131553.21883.vykk3@comcast.net> <20040614091920.GD8899@meier-geinitz.de> Message-ID: <200406141037.06524.vykk3@comcast.net> Hello Henning, Thanks very much for the response! On Monday 14 June 2004 02:19, Henning Meier-Geinitz wrote: > [ ... ] > To disable v4l completely, edit /etc/sane.d/dll.conf and > comment out "v4l". I'm leaving this in for now, I am not sure there is a point to it since xsane doesn't seem to work with it and I have no need to scan from the tv tuner :-). > To start xsane with your scanner > directly (without chosing): > > xsane yourbackend (e.g. xsane plustek). > > > -d, --device-settings file load device settings from > > file (without ".drc") > > > > Seems to be ignored :-(. > > Really? It justs loads the settings for one device. It > doesn't set the default device to use. Thanks, that works now :-). I was taking the -d info literally and specifying: xsaneAGFA:SNAPSCAN1212U__2 (less .drc) from the ~/.sane/xsane directory. Just snapscan works fine :-). Thanks very much and take care, V. -- Victoria Welch, WV9K/7. "If we knew what we were doing, it would not be called research, would it?" --Albert Einstein "Engineering is the art of making what you want from things you can get."- Jerry Avins From anoah at pfeiffer.edu Tue Jun 15 02:07:57 2004 From: anoah at pfeiffer.edu (m. allan noah) Date: Mon, 14 Jun 2004 21:07:57 -0400 (EDT) Subject: [sane-devel] Re: SANE driver for NEC Petiscan scanner In-Reply-To: References: Message-ID: TIS is teco image systems. 2ax000 must be part number. next is date code. there is a little hp that uses this chip (photo 1000 iirc). your best bet is going to be usb sniff from windows, and compare the data to what is used by the other teco backends, just on the off chance that it is similar or encapsulated version. allan On Mon, 14 Jun 2004, Allan Kaplan wrote: > Greetings, > > OK, I managed to take the scanner apart without damaging it, and found the > the big chip hiding under a cover. > > TIS > 2AX000 > 59S1998 > F8W07-000 > 9939 > > I will see what other info I can find. > > Thanks, > > Allan > > > > > Message: 3 > > Date: Mon, 14 Jun 2004 11:49:43 +0200 > > From: Henning Meier-Geinitz > > To: sane-devel at lists.alioth.debian.org > > Subject: Re: [sane-devel] SANE driver for NEC Petiscan scanner > > > > Hi, > > > > On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: > >> As far as I can tell, without further digging into the guts of the scanner, > >> there are two chips which say > >> > >> JIC (?) > >> ES52099S > >> 9919-LHIJ > >> I was not able to find data on this chip. > > > > Google finds some references but no spec or explanation. > > > >> Winbond > >> W24512AJ-15 > >> 919SA290732601CE > >> Chip specs: > >> > > > > So that's RAM. No other chips? In this c ase the JIC must be the scan > > chip. > > > >> It occurred to me that this scanner will run off another computer I have > >> access to, but only in MacOS9. Might there more data that I can access from > >> a computer that will actually run the scanner, versus this laptop with which > >> I want to ultimately run the scanner, but only uses MacOSX? > > > > You need software that can listen to the USB commands send to the > > scanner ("sniffer"). While some programs are available for Windows I > > don't know if that's the case for MacOS9. > > > > Bye, > > Henning > > > > > > > -- "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 olaf at epkowa.co.jp Tue Jun 15 05:31:18 2004 From: olaf at epkowa.co.jp (Olaf Meeuwissen) Date: Tue, 15 Jun 2004 13:31:18 +0900 Subject: [sane-devel] Timeouts: usb_reset seems necessary to avoid bulk timeouts. In-Reply-To: <20040609203310.GP7920@meier-geinitz.de> (Henning Meier-Geinitz's message of "Wed, 9 Jun 2004 22:33:11 +0200") References: <20040609164851.1fcddb78@expensive> <20040609203310.GP7920@meier-geinitz.de> Message-ID: <87brjljvc9.fsf@zen.epkowa.co.jp> Hi Tom, Henning Meier-Geinitz writes: > Hi, > > On Wed, Jun 09, 2004 at 04:48:51PM +0100, Tom Schutzer-Weissmann wrote: >> I had problems using the Epkowa libraries (libsane-epkowa) and the >> iscan frontend with my usb scanner in kernel 2.6. > >> The scanner was closed after each operation. Once closed, nothing >> could be read from it, and I got lots of BULK TIMEOUTs, although >> there were no errors when the device was reopened. >> >> By modifying the code so that usb_reset() was always called before >> usb_release_interface() and usb_close(), I solved the problem. > > Doesn't usb_reset() cause a renumeration and therefore the device gets > a new device file? I guess this isn't the default for closing USB > devices. Maybe the usb_reset just hides a bug in the SANE backend, > libusb or the kernel. Henning is right about the re-enumeration. As far as I understand the docs, that means that after calling usb_reset(), you may no longer use the handle you have. Problem is, it *is* used twice after that call. If the documentation is serious about this re-enumeration, than your "fix" is incorrect and has the potential to break support for *all* SANE supported USB devices. That it works for you is mere coincidence. FYI: http://libusb.sourceforge.net/doc/function.usbreset.html That leads us to a bug in the epson/epkowa backends, quite possibly caused by undocumented behaviour of this particular scanner. :-( -- Olaf Meeuwissen EPSON KOWA Corporation, PF1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2 From kaplanam1 at comcast.net Tue Jun 15 06:42:04 2004 From: kaplanam1 at comcast.net (Allan Kaplan) Date: Mon, 14 Jun 2004 22:42:04 -0700 Subject: [sane-devel] Re: SANE driver for NEC Petiscan scanner In-Reply-To: Message-ID: Thanks, I will work on finding a PC to check it from. Unfortunately, VirtualPC for Mac will not read the USB bus, or I wouldn't need Sane in the first place. Allan On 6/14/04 6:07 PM, "m. allan noah" wrote: > TIS is teco image systems. 2ax000 must be part number. next is date code. > > there is a little hp that uses this chip (photo 1000 iirc). > > your best bet is going to be usb sniff from windows, and compare the data > to what is used by the other teco backends, just on the off chance that it > is similar or encapsulated version. > > allan > > On Mon, 14 Jun 2004, Allan Kaplan wrote: > >> Greetings, >> >> OK, I managed to take the scanner apart without damaging it, and found the >> the big chip hiding under a cover. >> >> TIS >> 2AX000 >> 59S1998 >> F8W07-000 >> 9939 >> >> I will see what other info I can find. >> >> Thanks, >> >> Allan >> >> >> >>> Message: 3 >>> Date: Mon, 14 Jun 2004 11:49:43 +0200 >>> From: Henning Meier-Geinitz >>> To: sane-devel at lists.alioth.debian.org >>> Subject: Re: [sane-devel] SANE driver for NEC Petiscan scanner >>> >>> Hi, >>> >>> On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: >>>> As far as I can tell, without further digging into the guts of the scanner, >>>> there are two chips which say >>>> >>>> JIC (?) >>>> ES52099S >>>> 9919-LHIJ >>>> I was not able to find data on this chip. >>> >>> Google finds some references but no spec or explanation. >>> >>>> Winbond >>>> W24512AJ-15 >>>> 919SA290732601CE >>>> Chip specs: >>>> >>> >>> So that's RAM. No other chips? In this c ase the JIC must be the scan >>> chip. >>> >>>> It occurred to me that this scanner will run off another computer I have >>>> access to, but only in MacOS9. Might there more data that I can access >>>> from >>>> a computer that will actually run the scanner, versus this laptop with >>>> which >>>> I want to ultimately run the scanner, but only uses MacOSX? >>> >>> You need software that can listen to the USB commands send to the >>> scanner ("sniffer"). While some programs are available for Windows I >>> don't know if that's the case for MacOS9. >>> >>> Bye, >>> Henning >>> >>> >> >> >> From gerard at gkall.hobby.nl Tue Jun 15 09:41:55 2004 From: gerard at gkall.hobby.nl (gerard klaver) Date: Tue, 15 Jun 2004 08:41:55 +0000 Subject: [sane-devel] Re: SANE driver for NEC Petiscan scanner In-Reply-To: References: Message-ID: <1087288915.2089.21.camel@gk-lex3> Teco1, 2 and 3 are backends for SCSI scanners so don't expect that the codes are the same. Most teco scanners have a VM... nr. on the outside of the scanner and sometimes also placed somewhere in the software. Also some rebadged teco scanners have a VM.... on the outside or inside. See http://www.vic-corp.com/ download sections for some of the teco scanners with there VM.. number, (just for comparison) On Tue, 2004-06-15 at 01:07, m. allan noah wrote: > TIS is teco image systems. 2ax000 must be part number. next is date code. > > there is a little hp that uses this chip (photo 1000 iirc). > > your best bet is going to be usb sniff from windows, and compare the data > to what is used by the other teco backends, just on the off chance that it > is similar or encapsulated version. > > allan > > On Mon, 14 Jun 2004, Allan Kaplan wrote: > > > Greetings, > > > > OK, I managed to take the scanner apart without damaging it, and found the > > the big chip hiding under a cover. > > > > TIS > > 2AX000 > > 59S1998 > > F8W07-000 > > 9939 > > > > I will see what other info I can find. > > > > Thanks, > > > > Allan > > > > > > > > > Message: 3 > > > Date: Mon, 14 Jun 2004 11:49:43 +0200 > > > From: Henning Meier-Geinitz > > > To: sane-devel at lists.alioth.debian.org > > > Subject: Re: [sane-devel] SANE driver for NEC Petiscan scanner > > > > > > Hi, > > > > > > On Sun, Jun 13, 2004 at 05:08:09PM -0700, Allan Kaplan wrote: > > >> As far as I can tell, without further digging into the guts of the scanner, > > >> there are two chips which say > > >> > > >> JIC (?) > > >> ES52099S > > >> 9919-LHIJ > > >> I was not able to find data on this chip. > > > > > > Google finds some references but no spec or explanation. > > > > > >> Winbond > > >> W24512AJ-15 > > >> 919SA290732601CE > > >> Chip specs: > > >> > > > > > > So that's RAM. No other chips? In this c ase the JIC must be the scan > > > chip. > > > > > >> It occurred to me that this scanner will run off another computer I have > > >> access to, but only in MacOS9. Might there more data that I can access from > > >> a computer that will actually run the scanner, versus this laptop with which > > >> I want to ultimately run the scanner, but only uses MacOSX? > > > > > > You need software that can listen to the USB commands send to the > > > scanner ("sniffer"). While some programs are available for Windows I > > > don't know if that's the case for MacOS9. > > > > > > Bye, > > > Henning > > > -- ---------- m.vr.gr. Gerard Klaver From epl at unimelb.edu.au Mon Jun 14 15:59:43 2004 From: epl at unimelb.edu.au (epl at unimelb.edu.au) Date: Tue, 15 Jun 2004 00:59:43 +1000 (EST) Subject: [sane-devel] epson 2400 neg scans In-Reply-To: Message-ID: On Sun, 13 Jun 2004 insane at piments.com wrote: > You say that this only happens on high res but later that higher res is > not availible on transparency. Could you be more specific? I sounds a bit > contradictory. > High res *is* available under transparency (up to 1600dpi), just not very useful due to lines appearing. > What res. works correctly (no lines) and what is the max you can scan a > neg. even if the output is poor? > Okay, I did more experiments and even at 200dpi, I can see lines. The weird thing is, these lines remain even if I simply scan an opaque piece of paper (while in transparency mode). Maybe the backend is buggy. Maybe there's some calibration that the scanner or scanner's firmware that weirds sane out. I haven't tried it under Windows either, so... Note that transparency mode does more than switching on the fluorescent light on the transparency cover. For example, in transparency mode, it isn't possible to scan an A4 page as you're limited to an (approx) A6 area. Whether this is a scanner or sane limitation I don't know. I'll see whether I can upload an sample image with lines onto a webpage in the coming days. === BTW Not related to the scanner or scanner backend itself, but I've been told off-list that due to a lack of accurate colour calibration under Linux, 35mm negative scanning doesn't work anyhow -- regardless of the scanner used. I'm *really* hoping someone will respond telling me how utterly wrong I am and that Free as in speech software is just an apt-get away and that it works flawlessly with my scanner... Cheers Eddie From stern at rowland.harvard.edu Mon Jun 14 16:54:34 2004 From: stern at rowland.harvard.edu (Alan Stern) Date: Mon, 14 Jun 2004 11:54:34 -0400 (EDT) Subject: [sane-devel] Re: [Linux-usb-users] Problems with HP 6200C scanner and SANE In-Reply-To: <20040612110326.GC652@hardeman.nu> Message-ID: On Sat, 12 Jun 2004, David H?rdeman wrote: > On Mon, May 31, 2004 at 02:58:12PM -0400, Alan Stern wrote: > >On Mon, 31 May 2004, David H?rdeman wrote: > >> I'm currently trying to get an HP 6200C USB scanner to work with SANE > >> (1.0.14) under Linux (Debian woody with some backports, kernel 2.4.26). > >> Whenever I scan something which requires a low amount of data (lineart > >> picture at 100dpi for instance), everything works just fine. But when I > >> scan a more bandwidth hungry pic, it never succeeds. I've tried this > >> both with the "scanner" module in the kernel and with libusb but both > >> seem to experience the same problems. > >> > >> I have tried sane's "dumb-read" option and all other option which were > >> mentioned in the sane-hp man page but I'm running out of ideas. Any > >> clues what might cause this (might later kernels be too picky with their > >> timing requirements)? > > > >The most likely explanation is that some other program (possibly a hotplug > >utility) is trying to access the scanner while you're using it, thereby > >confusing the scanner and causing it to fail. I've seen reports from > >other people where the "usbmodules" program did this. See what happens if > >you turn off all hotplug support. > > Hi, > and sorry for the delay in answering. > > I am running this on Debian Woody (with backported usblib and sane > packages of recent versions), so there is no hotplug support on the > system, the only other thing I could think of is the "nut" UPS daemon > which checks the status of the UPS over USB. > > However, disabling nut and trying to scan did not help sort out the > problem. > > Any other suggestions? Nothing much about 2.4.26 springs to mind. You might try turning on USB debugging in the kernel configuration to see if the system log contains any useful information when the fault occurs. Or you could try moving up to Linux 2.6, which has a more robust USB stack. Alan Stern From David at phenix.fr Tue Jun 15 15:19:37 2004 From: David at phenix.fr (David Neary) Date: Tue, 15 Jun 2004 16:19:37 +0200 Subject: [sane-devel] RE: JSane Message-ID: Andi McLean said: > On Sunday 13 June 2004 00:27, Klemens Dickbauer wrote: > Dave what do you think about putting the JNI part in with my code? If you can make sense of it, please feel free. The JNI wrappers are actually quite trivial. The hardest thing is figuring out how to avoid memory leaks. There are 2 ways to do this - expose allocation and deletion methods in the C, or communicate how much space is needed to the Java side, and let the jvm take care of garbage collection. The latter is the reason why I added the convenience method "getNumberOfDevices" in the JNI wrappers, I think it has a bug in it too. I think the correct implementation should have something like: devListLen = 0; while (device_list[devListLen] != NULL) devListLen ++; return devListLen; the one I have seems to have an off-by-one error when there is at least one device (I'm not sure I understand why, but it's the behaviour I'm seeing). > Does it fit with the design I've created? You're going to laugh, but because of continued problems with DLLs, I am now convinced that the nest thing for me to do is to use your pure Java implementation of the net protocol :) I like your design, even though some of the class names are a bit cumbersome, and I think that it's probably the best way to go for a Java implementation. > > Anyway, having a direct Java interface to the sane libs seems also > > desireable to me. David, what do you think about the > changes I suggest? I missed this mail (I'm on a digest, so I occasionally overlook mails I probably shouldn't). Sorry :) > > An unexpected exception has been detected in native code > outside the VM. > > Unexpected Signal : 11 occurred at PC=0x4DE37B06 > > Function=sane_dll_control_option+0x56 > > Library=/usr/lib/libsane.so.1 Looks like you're running on Linux or some other unix... > > Current Java thread: > > at > org.saneproject.scan.sane.Sane.getControlOption(Native Method) > > [..] Have you tried running the org.sane.Test class? Here's a sample usage of the Sane bindings: public class Test { public static void main(String[] args) throws IOException { Sane sane = new Sane(); int version[] = new int[1]; // Array to get version #. int status = sane.init(version); if (status != Sane.STATUS_GOOD) { System.out.println( "init() failed. Status= " + sane.strstatus(status)); return; } System.out.println("VersionMajor =" + sane.versionMajor(version[0])); System.out.println("VersionMinor =" + sane.versionMinor(version[0])); System.out.println("VersionBuild =" + sane.versionBuild(version[0])); // Get list of devices. // Allocate room for 50. SaneDevice devList[] = new SaneDevice[50]; status = sane.getDevices(devList, false); if (status != Sane.STATUS_GOOD) { System.out.println( "getDevices() failed. Status= " + sane.strstatus(status)); return; } for (int i = 0; i < 50 && devList[i] != null; i++) { System.out.println( "Device '" + devList[i].name + "' is a " + devList[i].vendor + " " + devList[i].model + " " + devList[i].type); } // Sanity test over... clean up sane.exit(); } } Your code should look very similar to the C code equivalent: sane.init (version); sane.open (device); sane.getOptionDescriptor(); sane.getControlOption(); // Get options sane.setControlOption(); // Set option value sane.start(); repeat sane.read(); return to sane.start() if we need more pages sane.cancel(); sane.close(); sane.exit(); You can also compile the C code with -g and run java in a debugger to get a better idea of what's going on. Hope this all helps, Cheers, Dave. From David at phenix.fr Tue Jun 15 16:17:44 2004 From: David at phenix.fr (David Neary) Date: Tue, 15 Jun 2004 17:17:44 +0200 Subject: [sane-devel] Re: JSane Message-ID: Hi Andi, Andi McLean said: > I have designed a structure to split interface and > implementation how does > everyone feel about these? Would it be possible for you to either include your java sources in the .jars you release, or release a source jar alongside them, please? I know they are available via CVS, but it would be nice to have the sources which were used to make the jar as well. Thanks, Dave. From David at phenix.fr Tue Jun 15 16:20:21 2004 From: David at phenix.fr (David Neary) Date: Tue, 15 Jun 2004 17:20:21 +0200 Subject: [sane-devel] RE: JSane Message-ID: Hi again, > Would it be possible for you to either include your java > sources in the .jars you release, or release a source jar > alongside them, please? I know they are available via CVS, > but it would be nice to have the sources which were used to > make the jar as well. Also, would you mind correcting the spelling of Descriptor please? Using sane option discriptors is going to drive me scatty :) Cheers, Dave. From jochen at penguin-breeder.org Tue Jun 15 16:10:24 2004 From: jochen at penguin-breeder.org (Jochen Eisinger) Date: Tue, 15 Jun 2004 17:10:24 +0200 Subject: [sane-devel] Question About Mustek 600CP scanner on Suse 9.1 In-Reply-To: References: Message-ID: <40CF1160.8040307@penguin-breeder.org> Hi, Neal Gamradt wrote: > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5 > from 'parport0' > [...] > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x00 > from 'parport0' the backend gets the correct value first, but later the scanner only returns the wrong value 0x00. To me this looks like the scanner got confused or something. Eddy, could you have a look at this? kind regards -- jochen From dlw at hei.net Wed Jun 16 18:54:31 2004 From: dlw at hei.net (Don) Date: Wed, 16 Jun 2004 10:54:31 -0700 Subject: [sane-devel] xsane -0.91 Message-ID: <40D08957.9060606@hei.net> Using xsane-0.91 with MDK 9.1 with KDE 2. I had xsane working fine with an Epson CX5400. However, the next time I booted the system, xsane no longer worked. Xsane could not find the scanner. The /etc/sane.d/epson.conf is the same as when it ran. - See below. lsusb and sane-find-scanner both return 04b8 0808 Seiko Epson Corp. /usr/bin/xsane said sane could not detect parallel devices as user and root. Any help getting xsane working again will be appreciated. Don The only lines in /etc/sane.d/epson.conf not disabled with an # are; usb 04b8 0808 usb /dev/usb/lb0 Xsane work like this before. -- Please do not send or forward HTML's. From info at linuxmaker.de Tue Jun 15 20:41:10 2004 From: info at linuxmaker.de (Andreas) Date: Tue, 15 Jun 2004 21:41:10 +0200 Subject: [sane-devel] PLUSTEK OpticPro 12000T do not work under Kernel 2.6.4-52 Message-ID: <200406152141.10202.info@linuxmaker.de> Hello, I need your help. I have upgraded my system from SuSE 8.2 to 9.1. Now I need for my Plustek parallelport-scanner the package sane-backends-2004-06-14.tar.gz. I have installed it correctly, so I mean. But my scanner can't be dectected. xsane shows errors and scanimage -L tells me "No scanners were identified". Shortly after the installation of the package and after making ./MakeModule.sh tells me dmesg parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] parport0: irq 7 detected ... pt_drv: no version for "struct_module" found: kernel tainted. ********************************************* pt_drv: init_module() pt_drv : driver version 0.43-3 .... MiscGetModelName - id = 15 pt_drv0: 9636T/12000T found on port 0x0378 pt_drv0: Lamp-Timer set to 180 seconds. pt_drv0: WarmUp period set to 30 seconds. pt_drv0: Lamp untouched on driver unload. Lamp-Timer started! pt_drv : init done, 1 device(s) found And the lamp at my scanner shutdown after 180s But I can't use the scanner which xsane or scanimage -L. After a reboot dmesg tells me only parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE] parport0: irq 7 detected And lsmod shows me, pt_drv0 is no loaded. If I make now modprobe pt_drv I can see: Module Size Used by pt_drv 115796 0 ... parport_pc 35264 3 ppa 11656 0 parport 37704 4 pt_drv,lp,parport_pc,ppa And the lamp of the scanner is burning for 180s. But xsane and scanimage -L aren't possible. Can somebody tell, what I have to do, so pt_drv is correctly loaded at the booting and the scanner can use the devices? Perhaps I have forgotten something in the config-files. So, you can see the content of /etc/sane.d/plustek_pp.conf: ... #[direct] #device 0x378 # # leave the default values as specified in /etc/modules.conf # #option warmup -1 #option lOffOnEnd -1 #option lampOff -1 # model override switch, mostly for cosmetic changes, if the autodetection # does not work or could not work correctly #option mov 7 # # example for accessing the scanner via libieee1284 # #[direct] #device parport0 # # example for accessing the scanner via the kernel module # [kernel] device /dev/pt_drv option warmup -1 option lOffOnEnd -1 option lampOff -1 .... /etc/sane.d/dll.conf: ... pint plustek plustek_pp #pnm ... and /etc/modules.conf: alias char-major-40 pt_drv pre-install pt_drv modprobe -k parport options pt_drv lampoff=180 warmup=15 port=0x378 lOffonEnd=0 mov=0 slowIO=1 I hope somebody can help me at the solution of that problem. Thank you! Andreas From behnel_ml at gkec.tu-darmstadt.de Wed Jun 16 16:22:55 2004 From: behnel_ml at gkec.tu-darmstadt.de (Stefan Behnel) Date: Wed, 16 Jun 2004 17:22:55 +0200 Subject: [sane-devel] coloured gradient on scanned images Message-ID: <40D065CF.2020702@gkec.tu-darmstadt.de> Hi! With my HP Scanjet 7400c, the scans all have a coloured gradient, as in the attached example. I first figured it might have to do with the warm up phase, but it doesn't change over time. I'm using sane 1.0.13 (the RPMs I found for 1.0.14 seem to be broken). Any idea what I could try? Gamma or contrasts in XSane don't change anything... Thanks in advance, Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: out.jpeg Type: image/jpeg Size: 44201 bytes Desc: not available URL: From henning at meier-geinitz.de Wed Jun 16 21:44:17 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 16 Jun 2004 22:44:17 +0200 Subject: [sane-devel] xsane -0.91 In-Reply-To: <40D08957.9060606@hei.net> References: <40D08957.9060606@hei.net> Message-ID: <20040616204417.GA31800@meier-geinitz.de> Hi, On Wed, Jun 16, 2004 at 10:54:31AM -0700, Don wrote: > Using xsane-0.91 with MDK 9.1 with KDE 2. The version of sane-backends is more interesting. --> scanimage --version > I had xsane working fine with an Epson CX5400. While the CX5400 isn't mentioned in our lists it looks like the epson backend knows it. > However, the next time I booted the system, xsane no longer worked. > Xsane could not find the scanner. Does "scanimage -L" as root find the scanner? > The /etc/sane.d/epson.conf is the same as when it ran. - See below. > lsusb and sane-find-scanner both return 04b8 0808 Seiko Epson Corp. > /usr/bin/xsane said sane could not detect parallel devices as user and > root. I guess that's what sane-find-scanner says (not xsane). SANE can work with parallel port devices but sane-find-scanner can't detect all of them. But how is this realeted to your USB scanner? > The only lines in /etc/sane.d/epson.conf not disabled with an # are; A single line containing just "usb" should be enough. > usb 04b8 0808 This won't work as the USB ids are hexadecimal, not decimal. Add a "0x" before the numbers. > usb /dev/usb/lb0 I'd be surprised if you had a "/dev/usb/lb0" device. I've never heard of such a device. > Xsane work like this before. Are you sure that you haven't changed the config file in the mean time? Bye, Henning From gerhard at gjaeger.de Thu Jun 17 07:11:28 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Thu, 17 Jun 2004 08:11:28 +0200 Subject: [sane-devel] PLUSTEK OpticPro 12000T do not work under Kernel 2.6.4-52 In-Reply-To: <200406152141.10202.info@linuxmaker.de> References: <200406152141.10202.info@linuxmaker.de> Message-ID: <200406170811.28832.gerhard@gjaeger.de> Hi Andreas, I'm not sure, why this mail took that long to reach the list - or - to reach me, but I think we have already discussed that on the linux-club.de forum... For the protocol: - something wnet wrong when buildingh the module, but in the end it is loaded - automatic loading is done via /etc/init.d/boot.local - although the module is loaded, SANE does not find the scanner - there are two concurrent SANE installations on Andreas' box... That's all, Gerhard On Tuesday 15 June 2004 21:41, Andreas wrote: > Hello, > > I need your help. I have upgraded my system from SuSE 8.2 to 9.1. Now I > need for my Plustek parallelport-scanner the package > sane-backends-2004-06-14.tar.gz. I have installed it correctly, so I mean. > But my scanner can't be dectected. xsane shows errors and scanimage -L > tells me "No scanners were identified". > > Shortly after the installation of the package and after making > ./MakeModule.sh tells me dmesg [SNIPSNAP] From gerhard at gjaeger.de Thu Jun 17 07:14:08 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Thu, 17 Jun 2004 08:14:08 +0200 Subject: [sane-devel] XSane tweaks settings by its own :-( In-Reply-To: <1086702292.2129.40.camel@Babylon7> References: <200406081215.54463.gerhard@gjaeger.de> <1086702292.2129.40.camel@Babylon7> Message-ID: <200406170814.08201.gerhard@gjaeger.de> Hi Oliver, thanx for the info, I'll test it.. - sorry for the late repsonse. On Tuesday 08 June 2004 15:44, Oliver Rauch wrote: [SNIPSNAP] > static void xsane_back_gtk_value_update(...) > > case SANE_TYPE_INT: > val = adj_data->value + 0.5; > > remove the "+ 0.5" and it should work. > > But I am not sure if this will cause other problems. > I think there has been a reason for adding the "+ 0.5" Probably yes ;-) but obviously the reason is not that important, that you've missed the comment on that workaround :-))) Ciao, Gerhard > > Oliver > > Am Die, 2004-06-08 um 12.15 schrieb Gerhard Jaeger: > > Hi, > > > > I'm currenlty trying to add more frontend configurable options to the > > Plustek backend and have some problems with xsane now. > > There's a value whose range is from -1..63. At the default state, when > > starting xsane, it is properly displayed: -1. > > When changing once to i.e. 6 and changing it back to -1, xsane stores > > it as 0 and also displays it after the next startup as 0.. > > Bug or feature? What is wrong. The type of this option is SANE_TYPE_INT, > > the contraint_type is SANE_CONTRAINT_RANGE... > > The configfile of xsane shows, that this value is stored as 0 and not as > > -1... > > > > Any ideas? > > Gerhard From gerhard at gjaeger.de Thu Jun 17 07:55:16 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Thu, 17 Jun 2004 08:55:16 +0200 Subject: [sane-devel] Installation oddities... Message-ID: <200406170855.16452.gerhard@gjaeger.de> Hi list, on my SuSE distributions, I used to overwrite the existing and always outdated SANE-RPMs, by using the following configure command: ./configure --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --infodir=/usr/share/info This works pretty well up to sane-1.0.13, while checking 1.0.14 I noticed, that the links in /usr/lib/sane to the new libs are no longer updated during the installation step - did anything change there? TIA, Gerhard From henning at meier-geinitz.de Wed Jun 16 12:13:42 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 16 Jun 2004 13:13:42 +0200 Subject: [sane-devel] xsane -0.91 In-Reply-To: <40D109E1.7010602@hei.net> References: <40D08957.9060606@hei.net> <20040616204417.GA31800@meier-geinitz.de> <40D109E1.7010602@hei.net> Message-ID: <20040616111342.GC31800@meier-geinitz.de> Hi, On Wed, Jun 16, 2004 at 08:02:57PM -0700, Don wrote: > Thank you for replying. Please reply to the mailing list, not me personally. > >The version of sane-backends is more interesting. > >--> scanimage --version > > > > > scanimage (sane-backends) 1.0.11; backend version 1.0.11 That's rather old. I don't know if your scanner was already supported in that version. > >Does "scanimage -L" as root find the scanner? > > > > > device 'epson:libusb:oo2:002' is an Epson Unknown model flatbed scanner. Ok. "Unknown" doesn't look correct but at least it's detected. If it doesn't work the same way as normal user, see man sane-usb and README.linux for setting permissions/using hotplug: http://www.sane-project.org/README.linux > >This won't work as the USB ids are hexadecimal, not decimal. Add a > >"0x" before the numbers. > > > >>usb /dev/usb/lb0 > >> > TYPO ERROR it is usb /dev/usb/lp0 in epson.conf Well, but it's a USB scanner not a parport printer, isn't it? Anyway, the scanner is detected so there is no need to change anything. Bye, Henning From keith at claytons.org Thu Jun 17 13:56:38 2004 From: keith at claytons.org (Keith Clayton) Date: Thu, 17 Jun 2004 05:56:38 -0700 (PDT) Subject: [sane-devel] Oops . . here's the logs (xsane-win32/saned + epson 1650 prob) In-Reply-To: <1086882323.2126.4.camel@Babylon7> References: <1086841087.8304.22.camel@yoda> <20040610134404.GB2294@meier-geinitz.de> <1086879836.2126.2.camel@Babylon7> <1086882323.2126.4.camel@Babylon7> Message-ID: Finally had some time to get back on this . . kid's birthday, end of school year, etc. Upgraded to xsane0.94 on the windows box and problems scanning multiple images are gone. My best guess is that the mismatch of sane versions between 1.0.14 on the scanners host machine and the sane version included with xsane-0.90 were the problem. Back when I upgraded my backends to 1.0.14, I upgraded xsane on the linux box to 0.94 and looked for an upgrade to xsane-win32 but blew it and didn't see one available. Sorry for that, thanks to Oliver for pointing out that I'd blown it :-) and many thanks to Henning for showing me the many troubleshooting steps I could take. Cheers, Keith On Thu, 10 Jun 2004, Oliver Rauch wrote: > Am Don, 2004-06-10 um 17.32 schrieb Keith Clayton: > > No, still running 0.90 on the windows box. I upgraded to 0.94 on the > > linux box and looked for windows binaries at the same time. Didn't see > > them. Did I miss it? > > > > Looks like it. > Oliver > > > K > > > > On Thu, 10 Jun 2004, Oliver Rauch wrote: > > > > > For windows you can not enable a debug output - at least I do not know > > > a way with the published binaries because they are compiled as GUI. > > > > > > BTW. Did you ever test xsane-0.94-win32? > > > > > > Oliver > > > > > > Am Don, 2004-06-10 um 16.09 schrieb Keith Clayton: > > > > What sort of steps are availble for me to take debugging-wise on the > > > > windows end? > > > > > > > > If xsane is started from the command prompt, are there any swithces > > > > available to generate debugging output at the command prompt? > > > > > > > > K > > > > > > > > > > > > > > > > On Thu, 10 Jun 2004, Henning Meier-Geinitz wrote: > > > > > > > > > Hi, > > > > > > > > > > On Wed, Jun 09, 2004 at 09:18:11PM -0700, Keith Clayton wrote: > > > > > > Hate when I do that . . here's the xsane logs described in my previous > > > > > > email > > > > > > > > > > Ok, let's look at the second log. The preview scan looks ok (but I > > > > > don't know the details of the plustek backend). The real scan also > > > > > starts fine and then we see this: > > > > > > > > > > [plustek] sane_read - read 3750 bytes > > > > > [saned] do_scan: read 3750 bytes from scanner > > > > > [plustek] usb_ScanReadImage() done, result: 0 > > > > > [plustek] usb_ReadData() > > > > > [plustek] usb_ScanReadImage(3760) > > > > > [plustek] usb_ScanReadImage() done, result: 0 > > > > > [saned] do_scan: trying to write 3754 bytes to client > > > > > [saned] do_scan: wrote 3754 bytes to client > > > > > [saned] do_scan: trying to read 1521 bytes from scanner > > > > > [plustek] sane_read - read 1521 bytes > > > > > [saned] do_scan: read 1521 bytes from scanner > > > > > > > > > > Now these 1521 bytes should be sent to the frontend... > > > > > > > > > > [saned] do_scan: processing RPC request on fd 4 > > > > > [saned] process_request: waiting for request > > > > > [saned] process_request: bad status 22 > > > > > > > > > > saned thinks something has been sent to it by the control (not data) > > > > > connection. But when trying to decode what was sent it gets an error > > > > > when reading the first word. 22 is "invalid argument". That means that > > > > > no data could be read. Maybe xsane has crashed on the clent side > > > > > meanwhile? > > > > > > > > > > Usually during the scan nothing is sent to the control file descriptor. > > > > > > > > > > Anyway. As sane_cancel isn't called the reader_process in the plustek > > > > > backend isn't killed and the plustek backend gets confused. > > > > > > > > > > So my impression is that the problem is with xsane (or the net > > > > > frontend on windows) and the scanner lockup is just a consequence. > > > > > But I don't know why xsane (or the net backend) crashes. So maybe > > > > > finding out the details here may help- E.g. gdb xsane on the client or > > > > > enabling debugging for xsane and the net backend and looking at the > > > > > last few lines before the crash. > > > > > > > > > > Maybe the xsane and plustek maintainers can have a look at the > > > > > logfiles, too? > > > > > > > > > > Bye, > > > > > Henning > > > > > > > > > > > > > > > > > > > > > From dlw at hei.net Thu Jun 17 14:40:57 2004 From: dlw at hei.net (Don) Date: Thu, 17 Jun 2004 06:40:57 -0700 Subject: [sane-devel] Re: xsane-0.91 Message-ID: <40D19F69.2070207@hei.net> chmod a+rw /proc/bus/usb/002/002 did the trick but I guess it's temporary. How do I make it permanent? Don -- Please do not send or forward HTML's. From peter.jamrisko at advantel.cz Thu Jun 17 14:56:04 2004 From: peter.jamrisko at advantel.cz (=?ISO-8859-2?Q?Peter_Jamri=B9ko?=) Date: Thu, 17 Jun 2004 15:56:04 +0200 Subject: [sane-devel] LaserJet 3380 Message-ID: <40D1A2F4.50600@advantel.cz> Hi, I have a problem with HP LaserJet 3380 printer. Hpoj recognized it successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find it at all. Can someone help me with this? Thanks for help. Peter From andi.mclean at ntlworld.com Thu Jun 17 14:56:03 2004 From: andi.mclean at ntlworld.com (Andi McLean) Date: Thu, 17 Jun 2004 14:56:03 +0100 Subject: [sane-devel] JSane In-Reply-To: References: Message-ID: <200406171456.03998.andi.mclean@ntlworld.com> Hi all JSane version 0.5 has been released. I've added colour support, though not tested as I don't have a colour scanner. Please report / send bug fixes directly to me. It can be dowloaded from www.jsane.com Thanks Andi From dave.burns at comcast.net Thu Jun 17 16:59:18 2004 From: dave.burns at comcast.net (Dave Burns) Date: Thu, 17 Jun 2004 11:59:18 -0400 Subject: [sane-devel] Canon FS4000: image data is sensor data, not RGB? In-Reply-To: <20040617124741.3387.51756.Mailman@haydn.debian.org> Message-ID: I am making good progress reverse-engineering the SCSI protocol for this film scanner. I now have a short test program in C that scans film and I now have the challenge of decoding the image data returned. It appears to be raw sensor data. I don't have experience with many other scanners: is this typical of scanners to return raw data? Or maybe typical of film scanners but not flatbed? I have seen Dave Coffin's page on dcraw (http://www.cybercom.net/~dcoffin/dcraw/) which can decode sensor data to RGB but want to consult this list before I start to integrate his code in case anyone here has already done this and can offer tips/advice. Also, the image data appears to contain more data than expected. I.e. there is more data then there should be if I consider the size of my scanning window and work out the math. Is this typical and is it normal to have to interpolate to provide the user with expected results? db From henning at meier-geinitz.de Thu Jun 17 17:16:05 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 17 Jun 2004 18:16:05 +0200 Subject: [sane-devel] Re: xsane-0.91 In-Reply-To: <40D19F69.2070207@hei.net> References: <40D19F69.2070207@hei.net> Message-ID: <20040617161605.GF31800@meier-geinitz.de> Hi, On Thu, Jun 17, 2004 at 06:40:57AM -0700, Don wrote: > chmod a+rw /proc/bus/usb/002/002 did the trick but I guess it's temporary. > How do I make it permanent? man sane-usb, README.linux: http://www.sane-project.org/README.linux Bye, Henning From henning at meier-geinitz.de Thu Jun 17 17:18:38 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 17 Jun 2004 18:18:38 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <40D1A2F4.50600@advantel.cz> References: <40D1A2F4.50600@advantel.cz> Message-ID: <20040617161838.GG31800@meier-geinitz.de> Hi, On Thu, Jun 17, 2004 at 03:56:04PM +0200, Peter Jamri?ko wrote: > I have a problem with HP LaserJet 3380 printer. Hpoj recognized it > successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find it > at all. Can someone help me with this? Which kind of device is it (USB)? Please show us the output from sane-find-scanner -v -v If the device is detected by the hpoj backend, there is no need for sane-find-scanner. Bye, Henning From henning at meier-geinitz.de Thu Jun 17 17:25:33 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 17 Jun 2004 18:25:33 +0200 Subject: [sane-devel] Canon FS4000: image data is sensor data, not RGB? In-Reply-To: References: <20040617124741.3387.51756.Mailman@haydn.debian.org> Message-ID: <20040617162533.GH31800@meier-geinitz.de> Hi, On Thu, Jun 17, 2004 at 11:59:18AM -0400, Dave Burns wrote: > I am making good progress reverse-engineering the SCSI protocol for this > film scanner. I now have a short test program in C that scans film and I now > have the challenge of decoding the image data returned. It appears to be raw > sensor data. I don't have experience with many other scanners: is this > typical of scanners to return raw data? Or maybe typical of film scanners > but not flatbed? What do you mean exactly by "raw sensor data"? The format of the image data varies with the scanner chipset. Some scanners provide the calibrated and even gamma corrected data in the resolution you have selected. For others , calibration and gamma correction must be done by the backend. > Also, the image data appears to contain more data than expected. I.e. there > is more data then there should be if I consider the size of my scanning > window and work out the math. Is this typical and is it normal to have to > interpolate to provide the user with expected results? Most scanners can only do some fixed resolutions, e.g. 100, 300, and 600 dpi. So other resolutions are done by using the higher resolution and downsampling the result. Well, some windows drivers use the lower resolution and interpolate the missing pixels... This downsampling is sometimes done in the scanner, som,etimes it must be done by the backend. Some scanners can only scan in fixed window steps, e.g. the number of pixels must be a multiple of 64 or similar. Bye, Henning From henning at meier-geinitz.de Thu Jun 17 17:34:44 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 17 Jun 2004 18:34:44 +0200 Subject: [sane-devel] Installation oddities... In-Reply-To: <200406170855.16452.gerhard@gjaeger.de> References: <200406170855.16452.gerhard@gjaeger.de> Message-ID: <20040617163444.GI31800@meier-geinitz.de> Hi, On Thu, Jun 17, 2004 at 08:55:16AM +0200, Gerhard Jaeger wrote: > on my SuSE distributions, I used to overwrite the existing and always > outdated SANE-RPMs, by using the following configure command: > ./configure --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --infodir=/usr/share/info > > This works pretty well up to sane-1.0.13, while checking 1.0.14 I noticed, > that the links in /usr/lib/sane to the new libs are no longer updated > during the installation step - did anything change there? No. As far as I can see there is no change in the install target of backend/Makefile.in that could cause such a behaviour. In 1.0.11 we created such links manually but this is done by libtool nowerdays: lrwxrwxrwx 1 root staff 17 2004-06-16 18:09 /usr/local/lib/libsane.so -> libsane.so.1.0.14 lrwxrwxrwx 1 root staff 17 2004-06-16 18:09 /usr/local/lib/libsane.so.1 -> libsane.so.1.0.14 -rwxr-xr-x 1 root staff 84752 2004-06-16 18:09 /usr/local/lib/libsane.so.1.0.14 Bye, Henning From till.kamppeter at gmx.net Thu Jun 17 20:51:28 2004 From: till.kamppeter at gmx.net (Till Kamppeter) Date: Thu, 17 Jun 2004 21:51:28 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <20040617161838.GG31800@meier-geinitz.de> References: <40D1A2F4.50600@advantel.cz> <20040617161838.GG31800@meier-geinitz.de> Message-ID: <40D1F640.9050104@gmx.net> Henning Meier-Geinitz wrote: > Hi, > > On Thu, Jun 17, 2004 at 03:56:04PM +0200, Peter Jamri?ko wrote: > >>I have a problem with HP LaserJet 3380 printer. Hpoj recognized it >>successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find it >>at all. Can someone help me with this? > > > Which kind of device is it (USB)? Please show us the output from > sane-find-scanner -v -v > > If the device is detected by the hpoj backend, there is no need for > sane-find-scanner. > > Bye, > Henning > The LaserJet 3380 is for sure an HPOJ device and so SANE shows it only with "scanimage -L", and that only after you have done "ptal-init setup" and started HPOJ. Till From dave.burns at comcast.net Thu Jun 17 20:00:28 2004 From: dave.burns at comcast.net (Dave Burns) Date: Thu, 17 Jun 2004 15:00:28 -0400 Subject: [sane-devel] Canon FS4000: image data is sensor data, not RGB? In-Reply-To: <20040617124741.3387.51756.Mailman@haydn.debian.org> Message-ID: Sorry, ignore this post. It's not raw data as I can now see an image with different scanning parameters. --------------------------------------------------------- I am making good progress reverse-engineering the SCSI protocol for this film scanner. I now have a short test program in C that scans film and I now have the challenge of decoding the image data returned. It appears to be raw sensor data. I don't have experience with many other scanners: is this typical of scanners to return raw data? Or maybe typical of film scanners but not flatbed? I have seen Dave Coffin's page on dcraw (http://www.cybercom.net/~dcoffin/dcraw/) which can decode sensor data to RGB but want to consult this list before I start to integrate his code in case anyone here has already done this and can offer tips/advice. Also, the image data appears to contain more data than expected. I.e. there is more data then there should be if I consider the size of my scanning window and work out the math. Is this typical and is it normal to have to interpolate to provide the user with expected results? db From ukd at xenon.pc.Uni-Koeln.DE Fri Jun 18 07:22:19 2004 From: ukd at xenon.pc.Uni-Koeln.DE (Ulrich Deiters) Date: Fri, 18 Jun 2004 08:22:19 +0200 (METDST) Subject: [sane-devel] Canon FS4000: image data is sensor data, not RGB? Message-ID: <200406180622.IAA08608@xenon.pc.Uni-Koeln.DE> Do you receive 3 * 2 bytes per pixel? The FS2710S also produces 2 bytes, of which 12 bit are significant, in the order RRGGBB. The Canon-SCSI backend contains some portions that convert these raw data to the usual 8 bit representation. Perhaps this code can be modified to fit your case. Regards, Ulrich Deiters From C.W.J.Lemmens at its.tudelft.nl Fri Jun 18 08:47:15 2004 From: C.W.J.Lemmens at its.tudelft.nl (Kees Lemmens) Date: Fri, 18 Jun 2004 09:47:15 +0200 Subject: [sane-devel] strange rattle in epson 610 with 2.6.7 =?iso-8859-15?q?kernel=0A?= Message-ID: <200406180947.15367.C.W.J.Lemmens@its.tudelft.nl> Hi, I have an Epson Perfection 610 which worked fine for 2 years with 2.2.x and 2.4.x. Today I compiled 2.6.7 and now it suddenly produces strange and alarming sounds after the scan is finished and it returns to initial position. I thought the scanner failed, but after rebooting in 2.4.26 it works fine again, so I am afraid it must be something in the 2.6.x kernel combined with the sane 1.0.12 backend that I use (the one provided with Slackware 9.1). Any suggestions ? Should I just install the latest backend or is it something else ? -- Bye, Kees Lemmens. ----------------------------------------------------------------------- NOTICE: I consider all HTML based email as SPAM : forward => trash From peter.jamrisko at advantel.cz Fri Jun 18 10:00:03 2004 From: peter.jamrisko at advantel.cz (=?UTF-8?B?UGV0ZXIgSmFtcmnFoWtv?=) Date: Fri, 18 Jun 2004 11:00:03 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <40D1F640.9050104@gmx.net> References: <40D1A2F4.50600@advantel.cz> <20040617161838.GG31800@meier-geinitz.de> <40D1F640.9050104@gmx.net> Message-ID: <40D2AF13.4080705@advantel.cz> Hi, Thanks for help. Printer is connected via parallel port. I tried scanimage -L, but with no result. I'm sending attachments. I hope you will see them (if you don't see them, let me know I'll resend them in body). There is output from ptal-init, rpm -qa | grep ptal / hpoj / sane, sane-find-scanner -v -v, scanimage -L and dll.conf from directory /etc/sane.d/. I'm using Mandrake 9.1, kernel 2.4.21-0.13mdk. I also installed xojpanel which correctly shows me display contents. Btw, dysplay messages are in czech language (maybe it doesn't relate to my prblem). Thanks. Peter. Till Kamppeter wrote: > Henning Meier-Geinitz wrote: > >> Hi, >> >> On Thu, Jun 17, 2004 at 03:56:04PM +0200, Peter Jamri?ko wrote: >> >>> I have a problem with HP LaserJet 3380 printer. Hpoj recognized it >>> successfully (as hp_LaserJet_3380), but sane-find-scaner didn't find >>> it at all. Can someone help me with this? >> >> >> >> Which kind of device is it (USB)? Please show us the output from >> sane-find-scanner -v -v >> >> If the device is detected by the hpoj backend, there is no need for >> sane-find-scanner. >> >> Bye, >> Henning >> > > The LaserJet 3380 is for sure an HPOJ device and so SANE shows it only > with "scanimage -L", and that only after you have done "ptal-init > setup" and started HPOJ. > > Till > -------------- next part -------------- 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). -------------- next part -------------- # enable the next line if you want to allow access through the network: net abaton agfafocus apple avision artec artec_eplus48u as6e bh canon canon630u #canon_pp coolscan coolscan2 #dc25 #dc210 #dc240 dmc epson fujitsu gt68xx hp hp4200 hpsj5s leo matsushita microtek microtek2 mustek #mustek_pp mustek_usb nec pie pint plustek #pnm qcam ricoh s9036 sceptre sharp sm3600 snapscan sp15c #st400 tamarack teco1 teco2 teco3 #test umax #umax_pp umax1220u v4l viceo # # The following backends are not included in the sane-backends distribution # If you want to use them, download them from their webpages and read their # documentation # # HP OfficeJet backend homepage: http://hpoj.sf.net/ # Uncomment the following line if hpoj is installed: #hpoj niash hpoj -------------- next part -------------- sane-find-scanner -v-v searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Invalid argument) checking /dev/sg2... failed to open (Invalid argument) checking /dev/sg3... failed to open (Invalid argument) checking /dev/sg4... failed to open (Invalid argument) checking /dev/sg5... failed to open (Invalid argument) checking /dev/sg6... failed to open (Invalid argument) checking /dev/sg7... failed to open (Invalid argument) checking /dev/sg8... failed to open (Invalid argument) checking /dev/sg9... failed to open (Invalid argument) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Invalid argument) checking /dev/sgc... failed to open (Invalid argument) checking /dev/sgd... failed to open (Invalid argument) checking /dev/sge... failed to open (Invalid argument) checking /dev/sgf... failed to open (Invalid argument) checking /dev/sgg... failed to open (Invalid argument) checking /dev/sgh... failed to open (Invalid argument) checking /dev/sgi... failed to open (Invalid argument) checking /dev/sgj... failed to open (Invalid argument) checking /dev/sgk... failed to open (Invalid argument) checking /dev/sgl... failed to open (Invalid argument) checking /dev/sgm... failed to open (Invalid argument) checking /dev/sgn... failed to open (Invalid argument) checking /dev/sgo... failed to open (Invalid argument) checking /dev/sgp... failed to open (Invalid argument) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. # Also you need support for SCSI Generic (sg) in your operating system. # If using Linux, try "modprobe sg". searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11... failed to open (Invalid argument) checking /dev/usbscanner12... failed to open (Invalid argument) checking /dev/usbscanner13... failed to open (Invalid argument) checking /dev/usbscanner14... failed to open (Invalid argument) checking /dev/usbscanner15... failed to open (Invalid argument) trying libusb: # 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. done -------------- next part -------------- Currently defined device names ([*]=default): [*] "mlc:par:hp_LaserJet_3380" Model is "hp LaserJet 3380". Parallel-port base address is "0x378". -------------- next part -------------- libhpojip0-0.90-4mdk libsane-hpoj0-0.90-4mdk hpoj-0.90-4mdk libhpojip0-devel-0.90-4mdk -------------- next part -------------- libptal0-0.90-4mdk libptal0-devel-0.90-4mdk -------------- next part -------------- libsane-hpoj0-0.90-4mdk xsane-0.90-2mdk libsane1-1.0.11-5mdk saned-1.0.11-5mdk libsane1-devel-1.0.11-5mdk xsane-gimp-0.90-2mdk sane-backends-1.0.11-5mdk sane-frontends-1.0.10-1mdk From henning at meier-geinitz.de Fri Jun 18 11:09:16 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 18 Jun 2004 12:09:16 +0200 Subject: [sane-devel] [ANNOUNCE] New release of gt68xx backend Message-ID: <20040618100916.GD28890@meier-geinitz.de> Hi everyone, I've just updated the gt68xx backend in CVS to version 1.0-61. The new version has quite a lot of changes so please test it if you own a scanner supported by this backend. Most important changes: - Mustek ScanExpress A3 USB is supported better now Warm-up and calibrationm should work now, however, some vertical stripes are still present - several minor fixes for other scanners - calibration in general avoids loops so it should be faster in some situations - CIS calibration should be better in avoiding stripes now. That work is not finished, however. - backtracking should occur less often - it's possible to select the color that's used to scan in gray/lineart mode now. More changes: http://www.meier-geinitz.de/sane/gt68xx-backend/gt68xx.CHANGES Unfortunately there are still some bugs. See the TODO list: http://www.meier-geinitz.de/sane/gt68xx-backend/gt68xx.TODO Download As usual from SANE CVS or the gt68xx page: http://www.meier-geinitz.de/sane/gt68xx-backend/ Or from a complete CVS snapshot: http://www.sane-project.org/snapshots/ Bye, Henning From Oliver.Rauch at Rauch-Domain.DE Sat Jun 19 12:44:12 2004 From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch) Date: 19 Jun 2004 13:44:12 +0200 Subject: [sane-devel] sane-backends-WIN32 Message-ID: <1087645452.3925.27.camel@Babylon7> Hello. Here a little experience report with sane-backends on WIN32. I used xsane-win32-0.94-sane-1.0.14-complete-no-gimp.zip for my tests with a UMAX Powerlook III SCSI-scanner on Windows 2000. I can create debugging messages with set SANE_DEBUG_UMAX=12 or set SANE_DEBUG_SANEI_SCSI=128 and scanimage. With xsane the stdout and sterr are not available because it is compiled as GUI. The status is: 1) xsane recognices the scanner without any changes. 2) The xsane interface comes up with correct options => INQUIRY is done without problems 3) Starting a scan or a preview makes two problems: a) SCSI Buffer size seems to be limited to 32KB, that is too small for this scanner in Color mode. Increasing the size by umax.conf options does not work. b) the START_SCAN command returns with I/O Error. The SET_WINDOW command and SEND_GAMMA_DATA in grayscale mode does not make any problems. It is encouraging that the INQUIRY, SET_WINDOW and SEND_GAMMA_DATA commands work without problems. I do not have an idea why the START_SCAN command fails. Please also report your experiences with sane-backends on WIN32. I think that we only have to do some little sourcecode changes to make it work. If we succeed with this then SANE gets the chance to be THE SCANNER DRIVER STANDARD and may be one day the manufacturers start writing their own (windows) drivers as SANE driver. Best regards Oliver From C.W.J.Lemmens at ewi.tudelft.nl Sat Jun 19 13:09:17 2004 From: C.W.J.Lemmens at ewi.tudelft.nl (Kees Lemmens) Date: Sat, 19 Jun 2004 14:09:17 +0200 Subject: [sane-devel] Re: strange rattle in epson 610 with 2.6.7 kernel In-Reply-To: <200406180940.03780.C.W.J.Lemmens@ewi.tudelft.nl> References: <200406180940.03780.C.W.J.Lemmens@ewi.tudelft.nl> Message-ID: <20040619120917.GA5840@dutind6.twi.tudelft.nl> Hi, First problem : rattle epson 610 (solved) ------------- Just installed sane 1.0.13 and this works fine under 2.6.7. However turning back to sane-1.0.12 immediately gives the alarming rattle back ... BTW: I used this script to test without having to reboot/reinstall : #################################################################### #!/bin/sh #SANE=/opt/sane-1.0.13 # Newer xsane release SANE=/usr/ # Standard sane-1.0.12 from Slackware 9.1 export LD_LIBRARY_PATH=$SANE/lib/ export LD_PRELOAD=$SANE/lib/libsane.so exec /usr/bin/xsane $* #################################################################### Second problem : compile 1.0.14 under Slackware fails -------------- Whatever I try sane-1.0.14 doesn't compile under Slackware 9.1 !! configure fails to detect the presence of basic routines like "strdup", "getenv" and others under Slackware 9.1, thereby making it impposible to compile (at least on my system). Any ideas ? giant:/tmp/sane-backends-1.0.14 252 % make making all in include make[1]: Entering directory /tmp/sane-backends-1.0.14/include' make[1]: Nothing to be done for all'. make[1]: Leaving directory /tmp/sane-backends-1.0.14/include' making all in lib make[1]: Entering directory /tmp/sane-backends-1.0.14/lib' gcc -c -DHAVE_CONFIG_H -I. -I. -I../include/sane -I../include -DPATH_SANE_CONFIG_DIR=/opt/sane-1.0.14//etc/sane.d -DPATH_SANE_DATA_DIR=/opt/sane-1.0.14//share -DV_MAJOR=1 -DV_MINOR=0 -I/usr/local/include/gphoto2 -g -O2 -W -Wall getenv.c getenv.c:13:4: #error "Missing getenv() on this platform. Please implement." getenv.c: In function getenv': getenv.c:6: warning: unused parameter name' make[1]: *** [getenv.o] Error 1 make[1]: Leaving directory /tmp/sane-backends-1.0.14/lib' make: *** [all-recursive] Error 1 giant:/tmp/sane-backends-1.0.14 254 % less include/sane/config.h ... /* Define to 1 if you have the getenv' function. */ /* #undef HAVE_GETENV */ ... /* Define to 1 if you have the strcasecmp' function. */ /* #undef HAVE_STRCASECMP */ /* Define to 1 if you have the strdup' function. */ /* #undef HAVE_STRDUP */ Bye, Kees Lemmens On Fri, Jun 18, 2004 at 09:40:03AM +0200, Kees Lemmens wrote: > Hi, > > I have an Epson Perfection 610 which worked fine for 2 years with 2.2.x > and 2.4.x. > > Today I compiled 2.6.7 and now it suddenly produces strange and alarming > sounds after the scan is finished and it returns to initial position. > > I thought the scanner failed, but after rebooting in 2.4.26 it works > fine again, so I am afraid it must be something in the 2.6.x kernel > combined with the sane 1.0.12 backend that I use (the one provided with > Slackware 9.1). > > Any suggestions ? Should I just install the latest backend or is it > something else ? > > -- > Bye, > Kees Lemmens. > ----------------------------------------------------------------------- > NOTICE: I consider all HTML based email as SPAM : forward => trash From C.W.J.Lemmens at ewi.tudelft.nl Sat Jun 19 14:48:11 2004 From: C.W.J.Lemmens at ewi.tudelft.nl (Kees Lemmens) Date: Sat, 19 Jun 2004 15:48:11 +0200 Subject: [sane-devel] Re: strange rattle in epson 610 / compile problem 1.0.14 on slackware 9.1 In-Reply-To: <20040619120917.GA5840@dutind6.twi.tudelft.nl> References: <200406180940.03780.C.W.J.Lemmens@ewi.tudelft.nl> <20040619120917.GA5840@dutind6.twi.tudelft.nl> Message-ID: <20040619134811.GA6200@dutind6.twi.tudelft.nl> Hi, My problem compiling sane-1.0.14 under Slackware 9.1 is solved : Someone added gphoto2 to the default libraries since 1.0.14 ! However, "configure" found libgphoto2 because of an old gphoto2-config in /usr/local/bin but WASN'T able to find libgphoto2.so at compile time ! This made the test compilation for getenv, strdup and others fail, thereby making it completely impossible to install the backends. What should be improved IMO : configure should only decide to use libgphoto2 if it is able to compile and link a program using these libraries and it should disable gphoto2 in all other cases. Relying on the presence of gphoto2-config is not enough IMO. For now I configured using : ./configure --prefix=/opt/sane-1.0.14 --without-gphoto2 BTW: sane-1.0.14 works fine now ;) Bye, Kees Lemmens. On Sat, Jun 19, 2004 at 02:09:17PM +0200, Kees Lemmens wrote: > Hi, > Second problem : compile 1.0.14 under Slackware fails > -------------- > > Whatever I try sane-1.0.14 doesn't compile under Slackware 9.1 !! > configure fails to detect the presence of basic routines like "strdup", > "getenv" and others under Slackware 9.1, thereby making it impposible to > compile (at least on my system). > > Any ideas ? > > giant:/tmp/sane-backends-1.0.14 252 % make > making all in include > make[1]: Entering directory /tmp/sane-backends-1.0.14/include' > make[1]: Nothing to be done for all'. > make[1]: Leaving directory /tmp/sane-backends-1.0.14/include' > making all in lib > make[1]: Entering directory /tmp/sane-backends-1.0.14/lib' > gcc -c -DHAVE_CONFIG_H -I. -I. -I../include/sane -I../include > -DPATH_SANE_CONFIG_DIR=/opt/sane-1.0.14//etc/sane.d > -DPATH_SANE_DATA_DIR=/opt/sane-1.0.14//share -DV_MAJOR=1 -DV_MINOR=0 > -I/usr/local/include/gphoto2 -g -O2 -W -Wall getenv.c > getenv.c:13:4: #error "Missing getenv() on this platform. Please implement." > getenv.c: In function getenv': > getenv.c:6: warning: unused parameter name' > make[1]: *** [getenv.o] Error 1 > make[1]: Leaving directory /tmp/sane-backends-1.0.14/lib' > make: *** [all-recursive] Error 1 > > giant:/tmp/sane-backends-1.0.14 254 % less include/sane/config.h > ... > /* Define to 1 if you have the getenv' function. */ > /* #undef HAVE_GETENV */ > ... > /* Define to 1 if you have the strcasecmp' function. */ > /* #undef HAVE_STRCASECMP */ > > /* Define to 1 if you have the strdup' function. */ > /* #undef HAVE_STRDUP */ > -- Bye, Kees Lemmens. From psfales at fales-lorenz.net Sun Jun 20 00:33:57 2004 From: psfales at fales-lorenz.net (Peter Fales) Date: Sat, 19 Jun 2004 18:33:57 -0500 Subject: [sane-devel] Re: strange rattle in epson 610 / compile problem 1.0.14 on slackware 9.1 In-Reply-To: <20040619134811.GA6200@dutind6.twi.tudelft.nl> References: <200406180940.03780.C.W.J.Lemmens@ewi.tudelft.nl> <20040619120917.GA5840@dutind6.twi.tudelft.nl> <20040619134811.GA6200@dutind6.twi.tudelft.nl> Message-ID: <20040619233357.GA4693@fales-lorenz.net> On Sat, Jun 19, 2004 at 03:48:11PM +0200, Kees Lemmens wrote: > What should be improved IMO : > > configure should only decide to use libgphoto2 if it is able to compile and > link a program using these libraries and it should disable gphoto2 in all > other cases. Relying on the presence of gphoto2-config is not enough IMO. The latest CVS uses pkgconfig instead of gphoto2-config, but is still presumably subject to the same problem. I've submitted a fix to CVS to check and make sure that a program can be linked using the gphoto2 libraries before the gphoto2 backend will be enabled. -- Peter Fales Peter "at" fales-lorenz.net From mattias.ellert at tsl.uu.se Sun Jun 20 13:16:12 2004 From: mattias.ellert at tsl.uu.se (Mattias Ellert) Date: Sun, 20 Jun 2004 14:16:12 +0200 Subject: [sane-devel] New MacOS X binary packages Message-ID: <9EBC0590-C2B3-11D8-8FC2-0003930D2AFC@tsl.uu.se> Hi! I have today created a new set of SANE binary packages for MacOS X. The reason for this is that many things have been fixed in the code since I created the previous version: 1. sanei_scsi now handles SCSI devices with multiple LUNs correctly on MacOS X. 2. sane-find-scanner now works for SCSI scanners on MacOS X. 3. the last backends that still used fork instead of sanei_thread have been converted. (At least I believe there is noone left, but I haven't read every line of code in the repository. If you find a backend still using fork please inform me.) If you have had problems due to any of the reasons above, please test the new packages. The packages are available at http://www.ellert.se/twain-sane/ Mattias From sietse at cs.rug.nl Sun Jun 20 13:44:19 2004 From: sietse at cs.rug.nl (Sietse Achterop) Date: Sun, 20 Jun 2004 14:44:19 +0200 Subject: [sane-devel] HP 7450C libusb problems (a little bit more info) Message-ID: <40D586A3.2060307@cs.rug.nl> Hello, Concerning the bulk timeouts seen with the avision backend amongst others here a little bit more info. It is a follow up of my earlier report in http://lists.alioth.debian.org/pipermail/sane-devel/2004-June/011182.html First: with SANE_DEBUG_SANEI_USB=255 some more info is given when the timeout occurs: (this is mostly after 1 or 2 successful bulk transfers) [sanei_usb] sanei_usb_read_bulk: trying to read 22656 bytes USB error: error reading from bulk endpoint 0x83: Invalid or incomplete multibyte or wide character [sanei_usb] sanei_usb_read_bulk: read failed: Invalid or incomplete multibyte or wide character USB error: could not clear/halt ep 131: Protocol error I found the "USB error" originating in libusb, but I can't find where the "Invalid or incomplete .." message comes from. So I can't see whether it maybe is significant. Second: after "modprobe uhci_hcd debug=2" (or 3) NO extra information is put into /var/log/kern.log Finally, is there anything else that I could do or test? I was hoping to make a smaller testcase than the test.c program in sane-backends/frontend Greetings, Sietse From Nikolas.Arend at gmx.net Sun Jun 20 17:48:54 2004 From: Nikolas.Arend at gmx.net (Nikolas.Arend at gmx.net) Date: Sun, 20 Jun 2004 18:48:54 +0200 (MEST) Subject: [sane-devel] Canoscan Lide 80 and 5200F Message-ID: <21831.1087750134@www11.gmx.net> Hi there, I found some rumours about someone having the canoscan lide 80 working under SuSE linux. He said he used a driver for the 5200F (which is relatively new and according to sane unsupported at the moment) and also others on the list reported that this worked fine. It sounds more like a hoax since I haven't found anything about lide 80 and a working sane backend/driver so far; however, if there would be a possibility to run the lide 80 under linux which was overlooked so far by most people, I'd rather appreciate to know about it. Unfortunately the mailing list is in German, you can find the post here: http://www.linux-club.de/viewtopic.php?p=9278#9278 Could someone please comment on this (tell me if you need help with an english translation)? Thanx, Nick. -- +++ Jetzt WLAN-Router f?r alle DSL-Einsteiger und Wechsler +++ GMX DSL-Powertarife zudem 3 Monate gratis* http://www.gmx.net/dsl From nathanaelnoblet at hotmail.com Sun Jun 20 18:30:41 2004 From: nathanaelnoblet at hotmail.com (Nathanael Noblet) Date: Sun, 20 Jun 2004 17:30:41 +0000 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. Message-ID: Hello I'm running a RHEL 3 clone (tao-linux). I've upgraded my sane-backends to 1.0.14, frontends to 1.0.12 and xsane to .91. I'm using plustek_pp in direct mode (with libieee1284). I can't seem to get any further along getting the scanner working. I've set the debug to max, but I don't know what it is doing. In both cases "xsane -d plustek_pp:/dev/parport0" and "scanimage -d plustek_pp:/dev/parport0" go through and seem to detect the scanner and stop at the CCD type I've included the debug log. What can I do? When it gets to the last line below, it just sits there, with xsane, I don't get any more dialog boxes, CPU usages is about 90% for that one program regardless of whether it is scanimage or xsane. DEBUGLOG= [sanei_debug] Setting debug level of plustek_pp to 255. [plustek_pp] PlustekPP backend V0.01-8, part of sane-backends 1.0.14 [plustek_pp] ># Plustek-PP SANE Backend configuration file< [plustek_pp] ># For use with Plustek parallel-port scanners< [plustek_pp] >#< [plustek_pp] >< [plustek_pp] >#< [plustek_pp] ># user either [direct] or [kernel] to access the scanner< [plustek_pp] ># when using [kernel], device specifies the device-node, which is created< [plustek_pp] ># by the kernel-module loader (applies only to Linux)< [plustek_pp] ># when using [direct], device is used to set the parallel-port base address< [plustek_pp] ># or a device-name suitable for libieee1284, i.e. parport0< [plustek_pp] >#< [plustek_pp] >#[direct]< [plustek_pp] >#device 0x378< [plustek_pp] >#device /dev/parport0< [plustek_pp] >#< [plustek_pp] ># leave the default values as specified in /etc/modules.conf< [plustek_pp] >#< [plustek_pp] >#option warmup 15< [plustek_pp] >#option lOffOnEnd 1< [plustek_pp] >#option lampOff 120< [plustek_pp] ># model override switch, mostly for cosmetic changes, if the autodetection< [plustek_pp] ># does not work or could not work correctly< [plustek_pp] >#option mov 7< [plustek_pp] >< [plustek_pp] >#< [plustek_pp] ># example for accessing the scanner via libieee1284< [plustek_pp] >#< [plustek_pp] >[direct]< [plustek_pp] >device parport0< [plustek_pp] Decoding device name >parport0< [plustek_pp] >option warmup 15< [plustek_pp] Decoding option >warmup< [plustek_pp] >option lOffOnEnd 1< [plustek_pp] Decoding option >lOffOnEnd< [plustek_pp] >option lampOff 120< [plustek_pp] Decoding option >lampOff< [plustek_pp] >< [plustek_pp] >#< [plustek_pp] ># example for accessing the scanner via the kernel module< [plustek_pp] >#< [plustek_pp] >#[kernel]< [plustek_pp] >#device /dev/pt_drv< [plustek_pp] >#< [plustek_pp] >#option warmup -1< [plustek_pp] >#option lOffOnEnd -1< [plustek_pp] >#option lampOff -1< [plustek_pp] attach (parport0, 0xbfffb140, (nil)) [plustek_pp] Device configuration: [plustek_pp] device name : >parport0< [plustek_pp] direct I/O : yes [plustek_pp] warmup : 15s [plustek_pp] lampOff : 120 [plustek_pp] lampOffOnEnd : yes [plustek_pp] model override: 0 [plustek_pp] --------------------- [plustek_pp] drvopen() [plustek_pp] ptdrvInit(0) [plustek_pp] Init settings done [plustek_pp] ScanData = 0x08054638 [plustek_pp] Assigning port handle 0 [plustek_pp] ptdrvOpen(port=0x0) [plustek_pp] Try to claim the parport [plustek_pp] Setting SPP-mode [plustek_pp] Setting PS/2-mode [plustek_pp] Setting EPP-mode [plustek_pp] We're using libIEEE1284 I/O [plustek_pp] Starting Scanner-Autodetection [plustek_pp] ************ DETECTP48xx ************ [plustek_pp] ModelSet4800() [plustek_pp] modelInitPageSettings() [plustek_pp] A4 set [plustek_pp] ModelSet4800() done. [plustek_pp] P48xxInitAsic() [plustek_pp] DacInitialize() [plustek_pp] ImageInitialize() [plustek_pp] IOFuncInitialize() [plustek_pp] IOInitialize() [plustek_pp] * using readfunction >fnEPPRead< [plustek_pp] MotorInitialize() [plustek_pp] ResetPort() [plustek_pp] Test 0x55 [plustek_pp] Test 0xAA [plustek_pp] Compare data=0x7f and status=0xf, port=0x0 [plustek_pp] p48xxReadWriteTest() [plustek_pp] Found a 96001 ASIC at Reg 0x13 [plustek_pp] ModelSet4800() [plustek_pp] modelInitPageSettings() [plustek_pp] A4 set [plustek_pp] ModelSet4800() done. [plustek_pp] Moving 32 bytes to scanner, IODELAY = 0... [plustek_pp] ... done. [plustek_pp] p48xxCheck4800Memory() [plustek_pp] Moving 1280 bytes to scanner, IODELAY = 0... [plustek_pp] ... done. [plustek_pp] Putting Scanner (ASIC 96001/3) into Idle-Mode [plustek_pp] detectScannerConnection() returns 0. [plustek_pp] p48xxSetupScannerVariables() [plustek_pp] No ASIC 97003 found. [plustek_pp] Status-Register = 0x8F [plustek_pp] Scanner has Full/Half Stepping drive [plustek_pp] CCD is SONY Type _________________________________________________________________ MSN Premium helps eliminate e-mail viruses. Get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines From mtropicl at optonline.net Sun Jun 20 19:47:15 2004 From: mtropicl at optonline.net (Fritz Lang) Date: Sun, 20 Jun 2004 14:47:15 -0400 Subject: [sane-devel] help with Epson 636U and Panther Message-ID: Hello all, I tried getting this to work under Jag, but I've since stepped up to Panther. I installed: libusb.pkg sane-backends.pkg TWAIN-SANE-Interface.pkg I edited the sane.d/epson and added "usb" then: I ran: 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=0x04b8 [EPSON], product=0x0101 [Perfection636]) at libusb:001:002-04b8-0101-ff-ff # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. 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). scanimage > test.pnm scanimage: no SANE devices found I'd like to get this to work with OmniPage Pro X. Thanks for your help, Fritz -- Yes, I work in entertainment. It's not because I turned down the CEO spot on the NYSE. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerhard at gjaeger.de Mon Jun 21 08:51:47 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Mon, 21 Jun 2004 09:51:47 +0200 Subject: [sane-devel] Patching of maintained code by others... Message-ID: <200406210951.47667.gerhard@gjaeger.de> Hi list, while doing a CVS update this morning, I found my plustek code patched. In general, I do not have any problems on that, but I think that a short message on that would be of great help - or did I miss something? Ciao, Gerhard From peter.jamrisko at advantel.cz Mon Jun 21 09:10:35 2004 From: peter.jamrisko at advantel.cz (=?UTF-8?B?UGV0ZXIgSmFtcmnFoWtv?=) Date: Mon, 21 Jun 2004 10:10:35 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <40D2AF13.4080705@advantel.cz> References: <40D1A2F4.50600@advantel.cz> <20040617161838.GG31800@meier-geinitz.de> <40D1F640.9050104@gmx.net> <40D2AF13.4080705@advantel.cz> Message-ID: <40D697FB.1040609@advantel.cz> Hi all, This is output of scanimage -L (with export SANE_DEBUG_DLL=128 and export PTAL_DEBUG=2 ) with HP LaserJet 3380. I can print, but i cannot scan. /var/log/messages: ---------------------------------------------------- Jun 21 12:01:47 prtest ptal-mlcd: ERROR at ParPort.cpp:176, dev=, pid=1006, e=11 statusWaitSetClear(event=6) timed out, expected set/clear=0x40/0x00, got=0x38, currentMode=0x100! Jun 21 12:01:47 prtest ptal-mlcd: ERROR at ParPort.cpp:882, dev=, pid=1006, e=11 setModes: negotiate(0x10) failed! Jun 21 12:01:47 prtest ptal-mlcd: ERROR at ExMgr.cpp:3155, dev=, pid=1006, e=11 llioSetup: setModes failed! Jun 21 12:01:47 prtest ptal-mlcd: ERROR at ExMgr.cpp:2508, dev=, pid=1006, e=11 Couldn't find device: llioSetup failed! Jun 21 12:01:48 prtest ptal-mlcd: ERROR at ParPort.cpp:176, dev=, pid=1006, e=11 statusWaitSetClear(event=6) timed out, expected set/clear=0x40/0x00, got=0x38, currentMode=0x100! Jun 21 12:01:48 prtest ptal-mlcd: ERROR at ParPort.cpp:882, dev=, pid=1006, e=11 setModes: negotiate(0x10) failed! Jun 21 12:01:48 prtest ptal-mlcd: ERROR at ExMgr.cpp:3155, dev=, pid=1006, e=11 llioSetup: setModes failed! Jun 21 12:01:48 prtest ptal-mlcd: ERROR at ExMgr.cpp:2508, dev=, pid=1006, e=11 Couldn't find device: llioSetup failed! ---------------------------------------------------- stdoutput: ---------------------------------------------------- [sanei_debug] Setting debug level of dll to 128. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `hpoj' [dll] load: searching backend `hpoj' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-hpoj.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-hpoj.so.1' [dll] init: initializing backend `hpoj' ptalInit(): debug level set to 2. ptalInit() ptalDeviceAdd(mlc:par:hp_LaserJet_3380): dev=0x08052D70. ptalDeviceProbe: dev=<.>. ptalDeviceOpen(.): missing colon! ptalDeviceProbe: dev=<..>. ptalDeviceOpen(..): missing colon! ptalDeviceProbe: dev=. ptalMlcDeviceOpen(mlc:par:hp_LaserJet_3380): found matching dev=0x08052D70 (mlc:par:hp_LaserJet_3380). ptalDeviceProbe: dev=. ptalDeviceOpen(default-device): missing colon! [dll] init: backend `hpoj' is version 1.0.6 hpoj: sane_hpoj_get_devices hpoj:mlc:par:hp_LaserJet_3380: sane_hpoj_open ptalMlcDeviceOpen(mlc:par:hp_LaserJet_3380): found matching dev=0x08052D70 (mlc:par:hp_LaserJet_3380). ptalChannelAllocate(dev=0x08052D70): chan=0x08058480. ptalChannelSetRemoteService(chan=0x08058480,serviceType=2,socketID=0,serviceName=<>) ptalChannelSetPacketSizes(chan=0x08058480,desiredHPSize=256,desiredPHSize=8192) ptalChannelAllocate(dev=0x08052D70): chan=0x080584F0. ptalChannelSetRemoteService(chan=0x080584F0,serviceType=3,socketID=0,serviceName=) ptalChannelSetErrorHandling(chan=0x080584F0,retryCount=0,retryDelay=0) ptalMlcDeviceGetDeviceIDString(mlc:par:hp_LaserJet_3380): unsuccessful status=13! hpoj:mlc:par:hp_LaserJet_3380: device ID string=<> hpoj:mlc:par:hp_LaserJet_3380: hpojConnOpen ptalChannelOpen(chan=0x08058480): provider failed open! hpoj:mlc:par:hp_LaserJet_3380: hpojConnClose ptalChannelClose(chan=0x08058480) ptalChannelClose(chan=0x08058480): not open! ptalPmlClose(dev=0x08052D70) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! hpoj:mlc:par:hp_LaserJet_3380: hpojConnClose ptalChannelClose(chan=0x08058480) ptalChannelClose(chan=0x08058480): not open! ptalPmlClose(dev=0x08052D70) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! [dll] sane_exit: exiting [dll] sane_exit: calling backend `hpoj's exit function hpoj: sane_hpoj_exit ptalDone() ptalDeviceDelete(dev=0x08052D70) ptalDeviceClose(dev=0x08052D70) ptalChannelDeallocate(chan=0x08058480) ptalChannelClose(chan=0x08058480) ptalChannelClose(chan=0x08058480): not open! ptalChannelDeallocate(chan=0x080584F0) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! [dll] sane_exit: finished 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). ---------------------------------------------------- Any idea? Thanks for help. Peter. From peter.jamrisko at advantel.cz Mon Jun 21 09:53:42 2004 From: peter.jamrisko at advantel.cz (=?UTF-8?B?UGV0ZXIgSmFtcmnFoWtv?=) Date: Mon, 21 Jun 2004 10:53:42 +0200 Subject: [sane-devel] LaserJet 3380 In-Reply-To: <40D697FB.1040609@advantel.cz> References: <40D1A2F4.50600@advantel.cz> <20040617161838.GG31800@meier-geinitz.de> <40D1F640.9050104@gmx.net> <40D2AF13.4080705@advantel.cz> <40D697FB.1040609@advantel.cz> Message-ID: <40D6A216.1040606@advantel.cz> Meanwhile I changed cable connected to the printer and I got another output: ------------------------------------------------------------------ [sanei_debug] Setting debug level of dll to 128. [dll] sane_init: SANE dll backend version 1.0.8 from sane-backends 1.0.11 [dll] add_backend: adding backend `hpoj' [dll] load: searching backend `hpoj' in `/usr/lib/sane' [dll] load: trying to load `/usr/lib/sane/libsane-hpoj.so.1' [dll] load: dlopen()ing `/usr/lib/sane/libsane-hpoj.so.1' [dll] init: initializing backend `hpoj' ptalInit(): debug level set to 2. ptalInit() ptalDeviceAdd(mlc:par:hp_LaserJet_3380): dev=0x08052D70. ptalDeviceProbe: dev=<.>. ptalDeviceOpen(.): missing colon! ptalDeviceProbe: dev=<..>. ptalDeviceOpen(..): missing colon! ptalDeviceProbe: dev=. ptalMlcDeviceOpen(mlc:par:hp_LaserJet_3380): found matching dev=0x08052D70 (mlc:par:hp_LaserJet_3380). ptalDeviceProbe: dev=. ptalDeviceOpen(default-device): missing colon! [dll] init: backend `hpoj' is version 1.0.6 hpoj: sane_hpoj_get_devices hpoj:mlc:par:hp_LaserJet_3380: sane_hpoj_open ptalMlcDeviceOpen(mlc:par:hp_LaserJet_3380): found matching dev=0x08052D70 (mlc:par:hp_LaserJet_3380). ptalChannelAllocate(dev=0x08052D70): chan=0x08058480. ptalChannelSetRemoteService(chan=0x08058480,serviceType=2,socketID=0,serviceName=<>) ptalChannelSetPacketSizes(chan=0x08058480,desiredHPSize=256,desiredPHSize=8192) ptalChannelAllocate(dev=0x08052D70): chan=0x080584F0. ptalChannelSetRemoteService(chan=0x080584F0,serviceType=3,socketID=0,serviceName=) ptalChannelSetErrorHandling(chan=0x080584F0,retryCount=0,retryDelay=0) hpoj:mlc:par:hp_LaserJet_3380: device ID string= hpoj:mlc:par:hp_LaserJet_3380: hpojConnOpen ptalChannelOpen(chan=0x08058480): fd=3. hpoj:mlc:par:hp_LaserJet_3380: hpojResetScanner hpoj:mlc:par:hp_LaserJet_3380: hpojSclSendCommand(cmd=11110, param=0, punc=<*>, letter1=, letter2=) hpoj:mlc:par:hp_LaserJet_3380: Sending SCL command <E>> ptalChannelWrite(chan=0x08058480,buffer=0xBFFFDDC0,count=2) ptalChannelWrite(chan=0x08058480,buffer=0xBFFFDDC0,count=2) returns 2. _ptalChannelSelect(chan=0x08058480) returns 0, errno=2, n=4, timeout=0xBFFFCAF0, tv_sec=0, tv_usec=0. ptalPmlAllocate(dev=0x08052D70) ptalPmlAllocate(dev=0x08052D70) returns obj=0x08058560. ptalPmlSetID(obj=0x08058560) ptalPmlSetID(obj=0x08058560) returns OK. ptalPmlOpen(dev=0x08052D70) ptalChannelAllocate(dev=0x08052D70): chan=0x08058DC0. ptalChannelSetRemoteService(chan=0x08058DC0,serviceType=4,socketID=0,serviceName=<>) ptalChannelOpen(chan=0x08058DC0): fd=4. hpoj:mlc:par:hp_LaserJet_3380: Using SCL protocol. hpoj:mlc:par:hp_LaserJet_3380: hpojSclSendCommand(cmd=10886, param=18, punc=<*>, letter1=, letter2=) _ptalChannelSelect(chan=0x08058480) returns 0, errno=2, n=4, timeout=0xBFFFC8D0, tv_sec=0, tv_usec=0. hpoj:mlc:par:hp_LaserJet_3380: Sending SCL command <*s18E>> ptalChannelWrite(chan=0x08058480,buffer=0xBFFFDBA0,count=6) ptalChannelWrite(chan=0x08058480,buffer=0xBFFFDBA0,count=6) returns 6. _ptalChannelSelect(chan=0x08058480) returns 0, errno=2, n=4, timeout=0xBFFFDA10, tv_sec=0, tv_usec=0. ptalSclChannelRead(chan=0x08058480): ptalChannelReadTimeout(buffer=0xBFFFDDF0,count=256) returns 0, errno=2. hpoj:mlc:par:hp_LaserJet_3380: Got response (len=0) <>. hpoj:mlc:par:hp_LaserJet_3380: hpojSclInquire(cmd=10886,param=18) didn't get expected response of <*s18d>! hpoj:mlc:par:hp_LaserJet_3380: hpojConnClose ptalChannelClose(chan=0x08058480) ptalPmlClose(dev=0x08052D70) ptalChannelClose(chan=0x08058DC0) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! [dll] sane_exit: exiting [dll] sane_exit: calling backend `hpoj's exit function hpoj: sane_hpoj_exit ptalDone() ptalDeviceDelete(dev=0x08052D70) ptalDeviceClose(dev=0x08052D70) ptalPmlDeallocate(obj=0x08058560) ptalChannelDeallocate(chan=0x08058480) ptalChannelClose(chan=0x08058480) ptalChannelClose(chan=0x08058480): not open! ptalChannelDeallocate(chan=0x080584F0) ptalChannelClose(chan=0x080584F0) ptalChannelClose(chan=0x080584F0): not open! ptalChannelDeallocate(chan=0x08058DC0) ptalChannelClose(chan=0x08058DC0) ptalChannelClose(chan=0x08058DC0): not open! [dll] sane_exit: finished 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). ------------------------------------------------------------------ This looks better, but scanner still wasn't found. From pmsguevarra at yahoo.com Mon Jun 21 10:57:17 2004 From: pmsguevarra at yahoo.com (Peter Mark Guevarra) Date: Mon, 21 Jun 2004 02:57:17 -0700 (PDT) Subject: [sane-devel] different scan outputs for different Linux distributions Message-ID: <20040621095717.15033.qmail@web41015.mail.yahoo.com> Hi, Has anyone encountered this problem wherein the same frontend, xsane or xscanimage for instance, has different outputs for RedHat, and SuSE or Mandrake? Same settings were used in the frontend but different outputs resulted for different distributions, one is darker/brighter than the other. Also, in the case of using only one Linux Distribution, RedHat for example, is it expected to have the same output for the different SANE frontends given the default settings for each frontend? Thanks in advance, PMG --------------------------------- Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave.burns at comcast.net Mon Jun 21 14:12:50 2004 From: dave.burns at comcast.net (Dave Burns) Date: Mon, 21 Jun 2004 09:12:50 -0400 Subject: [sane-devel] sane-backends-WIN32 In-Reply-To: <20040619124852.7560.90441.Mailman@haydn.debian.org> Message-ID: I hope I'm not completely out of context since I only get the digest and have not been following this thread. But the following caught my eye: "With xsane the stdout and sterr are not available because it is compiled as GUI." As a WIN32 programmer for years, I know this doesn't have to be true. Use the following code to open a Win32 console window and rewire stdout/stderr to its output. Wrap the whole thing in a conditional that's true if you want debug output. Hope this helps. If I'm off topic, apologies. db #include #include /* For _open_osfhandle( ) */ #include /* For _O_TEXT */ { int hCrt_StdOut; int hCrt_StdErr; FILE *hf_stdout; FILE *hf_stderr; /* First create the console. This only opens the window. This will fail if we are already running from a console window (which means we don't need to connect any output streams). */ if (AllocConsole()) { HANDLE stdoutBuffer; CONSOLE_SCREEN_BUFFER_INFO bufferInfo; /* Now connect the Win32 STD_OUTPUT pipe to the c-runtime stdout stream */ stdoutBuffer = GetStdHandle(STD_OUTPUT_HANDLE); hCrt_StdOut = _open_osfhandle((long) stdoutBuffer, _O_TEXT); hf_stdout = _fdopen(hCrt_StdOut, "w"); *stdout = *hf_stdout; /* setvbuf(stdout, NULL, _IONBF, 0);*/ /* Now connect the Win32 STD_ERROR pipe to the c-runtime stderr stream */ hCrt_StdErr = _open_osfhandle((long) GetStdHandle(STD_ERROR_HANDLE), _O_TEXT); hf_stderr = _fdopen(hCrt_StdErr, "w"); *stderr = *hf_stderr; setvbuf(stderr, NULL, _IONBF, 0); /* now we increase the buffer size to 9999 lines. We only do this if we created a console so that we don't mess with a user's existing console. */ GetConsoleScreenBufferInfo(stdoutBuffer, &bufferInfo); if (bufferInfo.dwSize.Y < 9999) bufferInfo.dwSize.Y = 9999; SetConsoleScreenBufferSize(stdoutBuffer, bufferInfo.dwSize); } } -----Original Message----- From: sane-devel-admin at lists.alioth.debian.org [mailto:sane-devel-admin at lists.alioth.debian.org] On Behalf Of sane-devel-request at lists.alioth.debian.org From: Oliver Rauch To: sane-devel Organization: Date: 19 Jun 2004 13:44:12 +0200 Subject: [sane-devel] sane-backends-WIN32 Hello. Here a little experience report with sane-backends on WIN32. I used xsane-win32-0.94-sane-1.0.14-complete-no-gimp.zip for my tests with a UMAX Powerlook III SCSI-scanner on Windows 2000. I can create debugging messages with set SANE_DEBUG_UMAX=12 or set SANE_DEBUG_SANEI_SCSI=128 and scanimage. With xsane the stdout and sterr are not available because it is compiled as GUI. The status is: 1) xsane recognices the scanner without any changes. 2) The xsane interface comes up with correct options => INQUIRY is done without problems 3) Starting a scan or a preview makes two problems: a) SCSI Buffer size seems to be limited to 32KB, that is too small for this scanner in Color mode. Increasing the size by umax.conf options does not work. b) the START_SCAN command returns with I/O Error. The SET_WINDOW command and SEND_GAMMA_DATA in grayscale mode does not make any problems. It is encouraging that the INQUIRY, SET_WINDOW and SEND_GAMMA_DATA commands work without problems. I do not have an idea why the START_SCAN command fails. Please also report your experiences with sane-backends on WIN32. I think that we only have to do some little sourcecode changes to make it work. If we succeed with this then SANE gets the chance to be THE SCANNER DRIVER STANDARD and may be one day the manufacturers start writing their own (windows) drivers as SANE driver. Best regards Oliver --__--__-- Message: 2 Date: Sat, 19 Jun 2004 14:09:17 +0200 From: Kees Lemmens To: sane-devel at lists.alioth.debian.org Subject: [sane-devel] Re: strange rattle in epson 610 with 2.6.7 kernel Hi, First problem : rattle epson 610 (solved) ------------- Just installed sane 1.0.13 and this works fine under 2.6.7. However turning back to sane-1.0.12 immediately gives the alarming rattle back ... BTW: I used this script to test without having to reboot/reinstall : #################################################################### #!/bin/sh #SANE=/opt/sane-1.0.13 # Newer xsane release SANE=/usr/ # Standard sane-1.0.12 from Slackware 9.1 export LD_LIBRARY_PATH=$SANE/lib/ export LD_PRELOAD=$SANE/lib/libsane.so exec /usr/bin/xsane $* #################################################################### Second problem : compile 1.0.14 under Slackware fails -------------- Whatever I try sane-1.0.14 doesn't compile under Slackware 9.1 !! configure fails to detect the presence of basic routines like "strdup", "getenv" and others under Slackware 9.1, thereby making it impposible to compile (at least on my system). Any ideas ? giant:/tmp/sane-backends-1.0.14 252 % make making all in include make[1]: Entering directory /tmp/sane-backends-1.0.14/include' make[1]: Nothing to be done for all'. make[1]: Leaving directory /tmp/sane-backends-1.0.14/include' making all in lib make[1]: Entering directory /tmp/sane-backends-1.0.14/lib' gcc -c -DHAVE_CONFIG_H -I. -I. -I../include/sane -I../include -DPATH_SANE_CONFIG_DIR=/opt/sane-1.0.14//etc/sane.d -DPATH_SANE_DATA_DIR=/opt/sane-1.0.14//share -DV_MAJOR=1 -DV_MINOR=0 -I/usr/local/include/gphoto2 -g -O2 -W -Wall getenv.c getenv.c:13:4: #error "Missing getenv() on this platform. Please implement." getenv.c: In function getenv': getenv.c:6: warning: unused parameter name' make[1]: *** [getenv.o] Error 1 make[1]: Leaving directory /tmp/sane-backends-1.0.14/lib' make: *** [all-recursive] Error 1 giant:/tmp/sane-backends-1.0.14 254 % less include/sane/config.h ... /* Define to 1 if you have the getenv' function. */ /* #undef HAVE_GETENV */ ... /* Define to 1 if you have the strcasecmp' function. */ /* #undef HAVE_STRCASECMP */ /* Define to 1 if you have the strdup' function. */ /* #undef HAVE_STRDUP */ Bye, Kees Lemmens On Fri, Jun 18, 2004 at 09:40:03AM +0200, Kees Lemmens wrote: > Hi, > > I have an Epson Perfection 610 which worked fine for 2 years with > 2.2.x and 2.4.x. > > Today I compiled 2.6.7 and now it suddenly produces strange and > alarming sounds after the scan is finished and it returns to initial position. > > I thought the scanner failed, but after rebooting in 2.4.26 it works > fine again, so I am afraid it must be something in the 2.6.x kernel > combined with the sane 1.0.12 backend that I use (the one provided > with Slackware 9.1). > > Any suggestions ? Should I just install the latest backend or is it > something else ? > > -- > Bye, > Kees Lemmens. > ---------------------------------------------------------------------- > - > NOTICE: I consider all HTML based email as SPAM : forward => trash --__--__-- _______________________________________________ sane-devel mailing list sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel End of sane-devel Digest From Oliver.Rauch at Rauch-Domain.DE Mon Jun 21 19:35:21 2004 From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch) Date: 21 Jun 2004 20:35:21 +0200 Subject: [sane-devel] sane-backends-WIN32 In-Reply-To: <200406211642.i5LGgf3E010181@mailin.webmailer.de> References: <200406211642.i5LGgf3E010181@mailin.webmailer.de> Message-ID: <1087842921.2122.3.camel@Babylon7> Thnaks for that hint. I will test if this works with cygwin. Oliver Am Mon, 2004-06-21 um 15.12 schrieb Dave Burns: > I hope I'm not completely out of context since I only get the digest and > have not been following this thread. But the following caught my eye: > > "With xsane the stdout and sterr are not available because it is compiled > as GUI." > > As a WIN32 programmer for years, I know this doesn't have to be true. Use > the following code to open a Win32 console window and rewire stdout/stderr > to its output. Wrap the whole thing in a conditional that's true if you want > debug output. Hope this helps. If I'm off topic, apologies. > > db > > > > #include > #include /* For _open_osfhandle( ) */ > #include /* For _O_TEXT */ > > { > int hCrt_StdOut; > int hCrt_StdErr; > FILE *hf_stdout; > FILE *hf_stderr; > > /* First create the console. This only opens the window. This will fail if > we are already running from a console window (which means we don't need > to connect any output streams). */ > > if (AllocConsole()) { > HANDLE stdoutBuffer; > CONSOLE_SCREEN_BUFFER_INFO bufferInfo; > > /* Now connect the Win32 STD_OUTPUT pipe to the c-runtime stdout stream > */ > > stdoutBuffer = GetStdHandle(STD_OUTPUT_HANDLE); > hCrt_StdOut = _open_osfhandle((long) stdoutBuffer, _O_TEXT); > hf_stdout = _fdopen(hCrt_StdOut, "w"); > *stdout = *hf_stdout; > /* setvbuf(stdout, NULL, _IONBF, 0);*/ > > /* Now connect the Win32 STD_ERROR pipe to the c-runtime stderr stream > */ > > hCrt_StdErr = _open_osfhandle((long) GetStdHandle(STD_ERROR_HANDLE), > _O_TEXT); > hf_stderr = _fdopen(hCrt_StdErr, "w"); > *stderr = *hf_stderr; > setvbuf(stderr, NULL, _IONBF, 0); > > /* now we increase the buffer size to 9999 lines. We only do this > if we created a console so that we don't mess with a user's > existing console. */ > > GetConsoleScreenBufferInfo(stdoutBuffer, &bufferInfo); > if (bufferInfo.dwSize.Y < 9999) > bufferInfo.dwSize.Y = 9999; > SetConsoleScreenBufferSize(stdoutBuffer, bufferInfo.dwSize); > } > } > > > -----Original Message----- > From: sane-devel-admin at lists.alioth.debian.org > [mailto:sane-devel-admin at lists.alioth.debian.org] On Behalf Of > sane-devel-request at lists.alioth.debian.org > From: Oliver Rauch > To: sane-devel > Organization: > Date: 19 Jun 2004 13:44:12 +0200 > Subject: [sane-devel] sane-backends-WIN32 > > Hello. > > Here a little experience report with sane-backends on WIN32. > I used xsane-win32-0.94-sane-1.0.14-complete-no-gimp.zip for my tests with a > UMAX Powerlook III SCSI-scanner on Windows 2000. > > I can create debugging messages with > set SANE_DEBUG_UMAX=12 > or > set SANE_DEBUG_SANEI_SCSI=128 > and scanimage. > > With xsane the stdout and sterr are not available because it is compiled as > GUI. > > The status is: > 1) xsane recognices the scanner without any changes. > 2) The xsane interface comes up with correct options > => INQUIRY is done without problems > 3) Starting a scan or a preview makes two problems: > a) SCSI Buffer size seems to be limited to 32KB, > that is too small for this scanner in Color mode. > Increasing the size by umax.conf options does not work. > b) the START_SCAN command returns with I/O Error. > > The SET_WINDOW command and SEND_GAMMA_DATA in grayscale mode does not make > any problems. > > It is encouraging that the INQUIRY, SET_WINDOW and SEND_GAMMA_DATA commands > work without problems. I do not have an idea why the START_SCAN command > fails. > > Please also report your experiences with sane-backends on WIN32. > I think that we only have to do some little sourcecode changes to make it > work. If we succeed with this then SANE gets the chance to be THE SCANNER > DRIVER STANDARD and may be one day the manufacturers start writing their own > (windows) drivers as SANE driver. > > Best regards > Oliver > > > > --__--__-- > > Message: 2 > Date: Sat, 19 Jun 2004 14:09:17 +0200 > From: Kees Lemmens > To: sane-devel at lists.alioth.debian.org > Subject: [sane-devel] Re: strange rattle in epson 610 with 2.6.7 kernel > > Hi, > > First problem : rattle epson 610 (solved) > ------------- > > Just installed sane 1.0.13 and this works fine under 2.6.7. However turning > back to sane-1.0.12 immediately gives the alarming rattle back ... > > BTW: I used this script to test without having to reboot/reinstall : > #################################################################### > #!/bin/sh > > #SANE=/opt/sane-1.0.13 # Newer xsane release > SANE=/usr/ # Standard sane-1.0.12 from Slackware 9.1 > > export LD_LIBRARY_PATH=$SANE/lib/ > export LD_PRELOAD=$SANE/lib/libsane.so > > exec /usr/bin/xsane $* > #################################################################### > > Second problem : compile 1.0.14 under Slackware fails > -------------- > > Whatever I try sane-1.0.14 doesn't compile under Slackware 9.1 !! > configure fails to detect the presence of basic routines like "strdup", > "getenv" and others under Slackware 9.1, thereby making it impposible to > compile (at least on my system). > > Any ideas ? > > giant:/tmp/sane-backends-1.0.14 252 % make making all in include > make[1]: Entering directory /tmp/sane-backends-1.0.14/include' > make[1]: Nothing to be done for all'. > make[1]: Leaving directory /tmp/sane-backends-1.0.14/include' > making all in lib > make[1]: Entering directory /tmp/sane-backends-1.0.14/lib' > gcc -c -DHAVE_CONFIG_H -I. -I. -I../include/sane -I../include > -DPATH_SANE_CONFIG_DIR=/opt/sane-1.0.14//etc/sane.d > -DPATH_SANE_DATA_DIR=/opt/sane-1.0.14//share -DV_MAJOR=1 -DV_MINOR=0 > -I/usr/local/include/gphoto2 -g -O2 -W -Wall getenv.c > getenv.c:13:4: #error "Missing getenv() on this platform. Please > implement." > getenv.c: In function getenv': > getenv.c:6: warning: unused parameter name' > make[1]: *** [getenv.o] Error 1 > make[1]: Leaving directory /tmp/sane-backends-1.0.14/lib' > make: *** [all-recursive] Error 1 > > giant:/tmp/sane-backends-1.0.14 254 % less include/sane/config.h ... > /* Define to 1 if you have the getenv' function. */ > /* #undef HAVE_GETENV */ > ... > /* Define to 1 if you have the strcasecmp' function. */ > /* #undef HAVE_STRCASECMP */ > > /* Define to 1 if you have the strdup' function. */ > /* #undef HAVE_STRDUP */ > > > Bye, > Kees Lemmens > > On Fri, Jun 18, 2004 at 09:40:03AM +0200, Kees Lemmens wrote: > > Hi, > > > > I have an Epson Perfection 610 which worked fine for 2 years with > > 2.2.x and 2.4.x. > > > > Today I compiled 2.6.7 and now it suddenly produces strange and > > alarming sounds after the scan is finished and it returns to initial > position. > > > > I thought the scanner failed, but after rebooting in 2.4.26 it works > > fine again, so I am afraid it must be something in the 2.6.x kernel > > combined with the sane 1.0.12 backend that I use (the one provided > > with Slackware 9.1). > > > > Any suggestions ? Should I just install the latest backend or is it > > something else ? > > > > -- > > Bye, > > Kees Lemmens. > > ---------------------------------------------------------------------- > > - > > NOTICE: I consider all HTML based email as SPAM : forward => trash > > > > > --__--__-- > > _______________________________________________ > sane-devel mailing list > sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > > > End of sane-devel Digest > > From degreef at imec.be Mon Jun 21 20:54:03 2004 From: degreef at imec.be (Eddy De Greef) Date: Mon, 21 Jun 2004 21:54:03 +0200 Subject: [sane-devel] Question About Mustek 600CP scanner on Suse 9.1 In-Reply-To: <40CF1160.8040307@penguin-breeder.org>; from jochen@penguin-breeder.org on di, jun 15, 2004 at 17:10:24 +0200 References: <40CF1160.8040307@penguin-breeder.org> Message-ID: <20040621195403.GA3373@reddot.erps-kwerps.be> On 15-06-04 17:10:24 Jochen Eisinger wrote: > Neal Gamradt wrote: > > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0xa5 > > from 'parport0' > > [...] > > [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x00 > > from 'parport0' > > the backend gets the correct value first, but later the scanner only > returns the wrong value 0x00. To me this looks like the scanner got > confused or something. > > Eddy, could you have a look at this? After he compiled everything from source, upgraded his kernel, and altered the parport BIOS settings, Neal's problem disappeared. It's impossible to say what was the real problem, unfortunately. Best regards, Eddy From jochen at penguin-breeder.org Mon Jun 21 21:00:52 2004 From: jochen at penguin-breeder.org (Jochen Eisinger) Date: Mon, 21 Jun 2004 22:00:52 +0200 Subject: [sane-devel] Question About Mustek 600CP scanner on Suse 9.1 In-Reply-To: <20040621195403.GA3373@reddot.erps-kwerps.be> References: <40CF1160.8040307@penguin-breeder.org> <20040621195403.GA3373@reddot.erps-kwerps.be> Message-ID: <40D73E74.2000903@penguin-breeder.org> Hi, Eddy De Greef wrote: > After he compiled everything from source, upgraded his kernel, > and altered the parport BIOS settings, Neal's problem disappeared. > It's impossible to say what was the real problem, unfortunately. From brook at biology.nmsu.edu Tue Jun 22 00:36:25 2004 From: brook at biology.nmsu.edu (brook at biology.nmsu.edu) Date: Mon, 21 Jun 2004 17:36:25 -0600 Subject: [sane-devel] Epson Perfection 2400 Photo scanner problems In-Reply-To: <20040528172802.GG5312@meier-geinitz.de> References: <16558.46498.623574.314930@viola.nmsu.edu> <87hdu6ek1h.fsf@zen.epkowa.co.jp> <16562.2593.523307.32174@viola.nmsu.edu> <87smdpwe1c.fsf@zen.epkowa.co.jp> <20040528172802.GG5312@meier-geinitz.de> Message-ID: <16599.28921.259988.645168@viola.nmsu.edu> I'm slowly tracking down parts of the problem with my scanner. When I tried the NetBSD kernel scanner devices (/dev/uscanner*) I identified an issue with sane-find-scanner. It lacks any definition for NetBSD-specific kernel devices. I submitted a bug report (category tools) that provides a patch that fixes that. The remaining issue with using the kernel devices is getting the scanner information from the device driver. I'm looking into that, but if I hack in a hard-coded response to match the correct scanner everything works perfectly. I'm still not sure what is wrong with libusb, but I can get this scanner to work just fine (at least in 8-bit mode). I would very much appreciate it if someone will take the initiative and commit the patch to sane-find-scanner to include the NetBSD kernel devices. Thanks for your help. Cheers, Brook From jgato at lambdaux.com Tue Jun 22 12:00:44 2004 From: jgato at lambdaux.com (jose) Date: Tue, 22 Jun 2004 13:00:44 +0200 Subject: [sane-devel] Backends Database Message-ID: <1087902032.330.2.camel@localhost> Hello, Im a developer of the Linux Hardware Database Unification Project(http://sourceforge.net/projects/linuxhard/), a part of this Database will include information about scanners and backends. I would like to know if there is some DB about this or if all the information is included on the frames of the webpage of sane, because It will be very dificult to mantein the hardware DB if we have to visit the tables of the web to see the changes... I wish we could work together... thanks. From andras at users.sourceforge.net Tue Jun 22 12:23:15 2004 From: andras at users.sourceforge.net (Major A) Date: Tue, 22 Jun 2004 12:23:15 +0100 Subject: [sane-devel] list Message-ID: <20040622112315.GH11187@ventus.lan> Hi all, Sorry I've been out of touch for a while. The main reason was that I was busy doing other things, but also that list message delivery stopped a while ago without me noticing. I've now subscribed with a different address and it appears to be working OK now. Have there been any major events recently, especially related to the Coolscan2 driver? Andras From gerhard at gjaeger.de Tue Jun 22 15:35:21 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Tue, 22 Jun 2004 16:35:21 +0200 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. In-Reply-To: References: Message-ID: <200406221635.22006.gerhard@gjaeger.de> Hi, On Sunday 20 June 2004 19:30, Nathanael Noblet wrote: > Hello > I'm running a RHEL 3 clone (tao-linux). I've upgraded my sane-backends > to 1.0.14, frontends to 1.0.12 and xsane to .91. I'm using plustek_pp in > direct mode (with libieee1284). I can't seem to get any further along > getting the scanner working. I've set the debug to max, but I don't know > what it is doing. In both cases "xsane -d plustek_pp:/dev/parport0" and > "scanimage -d plustek_pp:/dev/parport0" go through and seem to detect the > scanner and stop at the CCD type I've included the debug log. What can I > do? probably nothing :-( All seems to look okay - I will check this @ home... You can try and set the port to SPP in BIOS and try again..... Ciao, Gerhard [SNIPSNAP] From nathanaelnoblet at hotmail.com Tue Jun 22 15:38:20 2004 From: nathanaelnoblet at hotmail.com (Nathanael Noblet) Date: Tue, 22 Jun 2004 14:38:20 +0000 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. Message-ID: > >probably nothing :-( >All seems to look okay - I will check this @ home... >You can try and set the port to SPP in BIOS and try again..... Okay, as a side note, I installed windows onto this same machine, to see if perhaps the scanner was shot, it is rather old. Unfortunately it worked perfectly. So I'd REALLY like to try to get it working... _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN Premium http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines From gerhard at gjaeger.de Tue Jun 22 15:46:13 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Tue, 22 Jun 2004 16:46:13 +0200 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. In-Reply-To: References: Message-ID: <200406221646.13667.gerhard@gjaeger.de> On Tuesday 22 June 2004 16:38, Nathanael Noblet wrote: > >probably nothing :-( > >All seems to look okay - I will check this @ home... > >You can try and set the port to SPP in BIOS and try again..... > > Okay, as a side note, I installed windows onto this same machine, to see if > perhaps the scanner was shot, it is rather old. Unfortunately it worked > perfectly. You can't imagine how I hate this sentence ;-) > So I'd REALLY like to try to get it working... Yes, I can imagine... You can also try and make the backend a kernel module - download the latest CVS snapshot, unpack the sources and go to sane-backends/doc/plustek call as root usere MakeModule.sh script to compile install and load the ptdrv module - then after successful loading, you should change the plustek_pp.conf Building the kernel module needs the kernel-sources proberly installed and configured on your box... I'm just curious, if the module get's loaded - as it's the same code, maybe I made a mistake when putting something to user space.... Ciao, Gerhard From henning at meier-geinitz.de Tue Jun 22 16:50:07 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 17:50:07 +0200 Subject: [sane-devel] Backends Database In-Reply-To: <1087902032.330.2.camel@localhost> References: <1087902032.330.2.camel@localhost> Message-ID: <20040622155007.GB9053@meier-geinitz.de> Hi, On Tue, Jun 22, 2004 at 01:00:44PM +0200, jose wrote: > Hello, Im a developer of the Linux Hardware Database Unification > Project(http://sourceforge.net/projects/linuxhard/), a part of this > Database will include information about scanners and backends. > > I would like to know if there is some DB about this or if all the > information is included on the frames of the webpage of sane, because It > will be very dificult to mantein the hardware DB if we have to visit the > tables of the web to see the changes... The information about supported (and not supported) scanners is contained in the *.desc files (e.g. doc/descriptions/mustek.desc). These files come with the sane-backends distribution. The current ones are in SANE CVS. Documentation of the format is in doc/descriptions.txt. The lists on the website are automatically generated from these lists by the tools/sane-desc program. It can also produce ASCI output. Maybe you can uses this output or modify that program to print the data you are interested in. Bye, Henning From henning at meier-geinitz.de Tue Jun 22 16:56:16 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 17:56:16 +0200 Subject: [sane-devel] list In-Reply-To: <20040622112315.GH11187@ventus.lan> References: <20040622112315.GH11187@ventus.lan> Message-ID: <20040622155616.GC9053@meier-geinitz.de> Hi, On Tue, Jun 22, 2004 at 12:23:15PM +0100, Major A wrote: > Sorry I've been out of touch for a while. The main reason was that I > was busy doing other things, but also that list message delivery > stopped a while ago without me noticing. I've now subscribed with a > different address and it appears to be working OK now. Strange. Unfortunately, alioth still doesn't sent any administrative messages (e.g. about mail problems) to me and all mails to sane-devel-admin are bounced. So I don't know the reason. > Have there been any major events recently, especially related to the > Coolscan2 driver? There are two bugs assigned to you in the bug tracker :-) Bye, Henning From andras at onepointfour.net Tue Jun 22 17:24:46 2004 From: andras at onepointfour.net (Major A) Date: Tue, 22 Jun 2004 17:24:46 +0100 Subject: [sane-devel] list In-Reply-To: <20040622155616.GC9053@meier-geinitz.de> References: <20040622112315.GH11187@ventus.lan> <20040622155616.GC9053@meier-geinitz.de> Message-ID: <20040622162445.GA13068@ventus.lan> > Strange. Unfortunately, alioth still doesn't sent any administrative > messages (e.g. about mail problems) to me and all mails to > sane-devel-admin are bounced. So I don't know the reason. > > > Have there been any major events recently, especially related to the > > Coolscan2 driver? > > There are two bugs assigned to you in the bug tracker :-) Great. One is a mystery to me (the LS-5000 is definitely NOT supported as it is, I'm working on it), the other is a patch (submitted yesterday) that I've been looking for for a while... Damn, why do things have to be in so many different places? Thanks for resubmitting that Debian bug report over here. Andras From henning at meier-geinitz.de Tue Jun 22 18:34:08 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:34:08 +0200 Subject: [sane-devel] Canoscan Lide 80 and 5200F In-Reply-To: <21831.1087750134@www11.gmx.net> References: <21831.1087750134@www11.gmx.net> Message-ID: <20040622173408.GI9053@meier-geinitz.de> Hi, On Sun, Jun 20, 2004 at 06:48:54PM +0200, Nikolas.Arend at gmx.net wrote: > Could someone please comment on this (tell me if you need help with an > english translation)? I haven't ever gotten any reliable report that the Canon LiDE 50 or 80 do work. Some people told me that these scanners are supported but after looking at their log files I found out that their scanners had the USB ids of Canon Lide 20 or 30. And surprisingly the owners of these scanners noticed that they own a Lide 20 or 30 when I asked them to look again at the name plate. I've been also poited to that forum but nobody told me: "yes, my Canon Lide 50 or 80 works with sane with the ... backend". So I think it's a hoax. Bye, Henning From henning at meier-geinitz.de Tue Jun 22 18:36:36 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:36:36 +0200 Subject: [sane-devel] help with Epson 636U and Panther In-Reply-To: References: Message-ID: <20040622173636.GJ9053@meier-geinitz.de> Hi, On Sun, Jun 20, 2004 at 02:47:15PM -0400, Fritz Lang wrote: > found USB scanner (vendor=0x04b8 [EPSON], product=0x0101 > scanimage -L > > No scanners were identified. If you were expecting something different, SANE_DEBUG_EPSON=255 scanimage -L may print some more details. Bye, Henning From henning at meier-geinitz.de Tue Jun 22 18:41:04 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:41:04 +0200 Subject: [sane-devel] Patching of maintained code by others... In-Reply-To: <200406210951.47667.gerhard@gjaeger.de> References: <200406210951.47667.gerhard@gjaeger.de> Message-ID: <20040622174104.GK9053@meier-geinitz.de> Hi, On Mon, Jun 21, 2004 at 09:51:47AM +0200, Gerhard Jaeger wrote: > while doing a CVS update this morning, I found my plustek code patched. > In general, I do not have any problems on that, but I think that a short > message on that would be of great help - or did I miss something? I also don't mind if others fix obvious bugs in my backends and also think that a notice to the backend maintainer is better. While I read the sane-commit mails that show the changes, I've already overlooked some of them. If many backends are changed, a mail to sane-devel is also ok in my opinion. Also, if a backend is developed in an external CVS the maintainer may overlook the previous change and just upload his newest version. So the fix gets lost. Bye, Henning From henning at meier-geinitz.de Tue Jun 22 18:43:53 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:43:53 +0200 Subject: [sane-devel] different scan outputs for different Linux distributions In-Reply-To: <20040621095717.15033.qmail@web41015.mail.yahoo.com> References: <20040621095717.15033.qmail@web41015.mail.yahoo.com> Message-ID: <20040622174353.GL9053@meier-geinitz.de> Hi, On Mon, Jun 21, 2004 at 02:57:17AM -0700, Peter Mark Guevarra wrote: > Has anyone encountered this problem wherein the same frontend, xsane > or xscanimage for instance, has different outputs for RedHat, and > SuSE or Mandrake? Same settings were used in the frontend but > different outputs resulted for different distributions, one is > darker/brighter than the other. I haven't heard about such a behaviour. Can you reproduce it with scanimage? Maybe the scanner wasn't warmed up completely in one of the tests? > Also, in the case of using only one Linux Distribution, RedHat for > example, is it expected to have the same output for the different > SANE frontends given the default settings for each frontend? Yes, if you don't use any of the color enhancement settings. E.g. make sure that xsane doesn't modify your gamma settings automatically. Bye, Henning From henning at meier-geinitz.de Tue Jun 22 18:47:06 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 22 Jun 2004 19:47:06 +0200 Subject: [sane-devel] Epson Perfection 2400 Photo scanner problems In-Reply-To: <16599.28921.259988.645168@viola.nmsu.edu> References: <16558.46498.623574.314930@viola.nmsu.edu> <87hdu6ek1h.fsf@zen.epkowa.co.jp> <16562.2593.523307.32174@viola.nmsu.edu> <87smdpwe1c.fsf@zen.epkowa.co.jp> <20040528172802.GG5312@meier-geinitz.de> <16599.28921.259988.645168@viola.nmsu.edu> Message-ID: <20040622174706.GM9053@meier-geinitz.de> Hi, On Mon, Jun 21, 2004 at 05:36:25PM -0600, brook at biology.nmsu.edu wrote: > I'm slowly tracking down parts of the problem with my scanner. When I > tried the NetBSD kernel scanner devices (/dev/uscanner*) I identified > an issue with sane-find-scanner. It lacks any definition for > NetBSD-specific kernel devices. I submitted a bug report (category > tools) that provides a patch that fixes that. I've added that patch to CVS. Next time, please attach the patch to the bug report ("upload"), that way the patch can be downloaded and applied directly. Could you try if it works in the CVS version of sane now? > The remaining issue with using the kernel devices is getting the > scanner information from the device driver. I'm looking into that, > but if I hack in a hard-coded response to match the correct scanner > everything works perfectly. Some backends can cope with the kernel scanner driver not returning USB ids. E.g. by setting options in backend.conf or by otherwise telling the backend which scanner is actually connected. Bye, Henning From gerhard at gjaeger.de Thu Jun 24 09:09:39 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Thu, 24 Jun 2004 10:09:39 +0200 Subject: [sane-devel] Automatic update of the Webpages... Message-ID: <200406241009.39040.gerhard@gjaeger.de> Hi, how can the following site: http://www.sane-project.org/lists/sane-mfgs-cvs.html be updated? It contains currently the following sentence: "The following table summarizes the devices supported by sane-backends-1.0.13-cvs.", which is wrong... Ciao, Gerhard From gerhard at gjaeger.de Thu Jun 24 09:16:30 2004 From: gerhard at gjaeger.de (Gerhard Jaeger) Date: Thu, 24 Jun 2004 10:16:30 +0200 Subject: [sane-devel] Comprehensive overview... Message-ID: <200406241016.30645.gerhard@gjaeger.de> Hi list, while searching for some info about the HP2400c, I noticed, that it is not included in the unsupported.desc file... The search engine delivers a result, but for "simple" users who are not using the search engine, the information about the scanner will be not available... I think we need one page, where all the information we have is available, even if the scanner is supported by an external, experimental or no backend. My two cents... Gerhard From timo at dspsrv.com Thu Jun 24 10:44:26 2004 From: timo at dspsrv.com (Tim O'Callaghan) Date: Thu, 24 Jun 2004 11:44:26 +0200 Subject: [sane-devel] Canon IS-12 Scanner head (for canon BJC 50,55 & 80 printers) Message-ID: <40DAA27A.8020603@dspsrv.com> Hi, I recently bought an IS-12 Scanner head for my BJC 50, and was a bit surprised to find that it was not supported by Sane. Rather than break the seal on the packaging, i thought I'd ask a few questions here. 1. is anybody working on a back end for it? 2. if so, do they want any help? 3. if not, does anyone have any idea on the internals of the device? the unsupported scanner information is empty. ta, Tim. From faide at alphacent.com Thu Jun 24 12:49:24 2004 From: faide at alphacent.com (Florent Aide) Date: Thu, 24 Jun 2004 11:49:24 +0000 Subject: [sane-devel] donation / scanner support Message-ID: <40DABFC4.9030102@alphacent.com> Hello list, I have a Dell A920 (rebranded Lexmark X1150) that is currently marked on the website as not supported. Since I have two of these little things I am willing to donate one of them to the project in order to see scanner support for it. How can I do that ? Is someone willing to accept this donation and work on the scanner part of the Dell A920 ? The printer/scanner is new and in its box with everything (there just is no USB cable). The donation would graciously be made by Alpha Centauri, we have already agreed upon it internally. Best regards, Florent AIDE Alpha Centauri From ukd at xenon.pc.Uni-Koeln.DE Thu Jun 24 11:27:54 2004 From: ukd at xenon.pc.Uni-Koeln.DE (Ulrich Deiters) Date: Thu, 24 Jun 2004 12:27:54 +0200 (METDST) Subject: [sane-devel] Canon IS-12 Scanner head (for canon BJC 50,55 & 80 printers) Message-ID: <200406241027.MAA23233@xenon.pc.Uni-Koeln.DE> Hi Tim, what exactly is this IS-12 - an add-on device for a printer? How is it controlled by the computer - SCSI, USB or parallel port? Perhaps one of the existing backends can be used. Regards, Ulrich Deiters From timo at dspsrv.com Thu Jun 24 12:02:47 2004 From: timo at dspsrv.com (Tim O'Callaghan) Date: Thu, 24 Jun 2004 13:02:47 +0200 Subject: [sane-devel] Canon IS-12 Scanner head (for canon BJC 50,55 & 80 printers) In-Reply-To: <200406241027.MAA23233@xenon.pc.Uni-Koeln.DE> References: <200406241027.MAA23233@xenon.pc.Uni-Koeln.DE> Message-ID: <40DAB4D7.3070807@dspsrv.com> Ulrich Deiters wrote: > Hi Tim, > > what exactly is this IS-12 - an add-on device for a printer? the IS-12 is a kind of a printer cartridge. You put it where the normal ink cartridge would go, and it turns your ink jet printer into a scanner. http://www.canon.co.uk/for_home/product_finder/printers/accessories/scanner_cartridges/index.asp by this question i can assume you're not working on it :) > How is it controlled by the computer - SCSI, USB or parallel > port? Perhaps one of the existing backends can be used. > Its controlled via the parallel port, and it would be safe to assume that a back end exists for the scanner chip set. I would guess its a chip set that supports single pass, and that its controlled by prefixing the control commands with a printer command. I don't know what the chip set is, and to be honest i don't want to take apart a my brand new IS-12 to find out. A cursory google for information on the internals has come up empty, so i don't know how to proceed other than running a port scanner under windows. Is there a method for matching command streams to a backed? Tim. From picos132004 at yahoo.co.uk Thu Jun 24 12:05:26 2004 From: picos132004 at yahoo.co.uk (=?iso-8859-1?q?Ioan-Cosmin=20Pop?=) Date: Thu, 24 Jun 2004 12:05:26 +0100 (BST) Subject: [sane-devel] check-usb-chip request for help Message-ID: <20040624110526.5365.qmail@web25106.mail.ukl.yahoo.com> Hello everyone! I started (some time ago) to modify the program check-usb-chip to detect my scanner. It's a Mustek BearPaw 4800TA ProII. I know, I'm slow, but it's the best I can :( I apologize to everyone. Anyway, I came across one problem and I don't know how to handle it. Let me explain. I created the function "check_SQ113" to check the chip (http://picosconsult.topcities.com/downloads/check-usb-chip.c). I test the device descriptor and the endpoints. After that, I try to write a value (a four bytes array), like this: req[0] = 0x64; req[1] = 0x64; req[2] = 0x64; req[3] = 0x64; result = usb_bulk_write (handle, 0x01, req, 4, TIMEOUT); if (result <= 0) { if (verbose > 2) printf (" this is not a SQ-113 (Error during bulk write)\n"); finish_interface (handle); return 0; } then read it: result = usb_bulk_read (handle, 0x82, &res, 1, 1000); if (result <= 0) { if (verbose > 2) printf (" this is not a SQ-113 (Error during bulk read)\n"); finish_interface (handle); return 0; } but I get an error in usb_bulk_write() no matter what I do. I tried to chage the endpoint (not to use bulk but interrupt) but to no avail. So, my question is: can I get rid of this test? I see there are other functions that don't try to write/read something from the device. Is it safe to do this? I mean, all the other tests ("device descriptor" and "endpoints" pass OK). After some time, I looked over the page http://www.sane-project.org/unsupported/mustek-bearpaw-4800ta-pro-ii.html and I saw some other chips: 1. SQ [brand] SQ100A A335-9901 --- 2. UTC QGOB L6219 TB [O in 1st line may be a Zero] --- 3. ISSI [brand] IS42S16100A1-7T X11882000D 0336 ---- 4. SQ [brand] SQ113C 0335-1408 D0KNS-013 [Zeroes may be O] Does this mean I have to include tests specific to those chips, or they behave exactly like SQ113C? Again, I apologise for being slow... Thank you Cosmin ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com From nathanaelnoblet at hotmail.com Thu Jun 24 15:57:54 2004 From: nathanaelnoblet at hotmail.com (Nathanael Noblet) Date: Thu, 24 Jun 2004 14:57:54 +0000 Subject: [sane-devel] OpticPro 4800P... plustek_pp kinda hangs. Message-ID: >On Tuesday 22 June 2004 16:38, Nathanael Noblet wrote: > > Okay, as a side note, I installed windows onto this same machine, to see >if > > perhaps the scanner was shot, it is rather old. Unfortunately it worked > > perfectly. > >You can't imagine how I hate this sentence ;-) I can, and I understand, really I do. The reason for it though was this scanner was gifted to me, and since it was so old, I needed to find out if it even worked at all. Since I couldn't get linux working with it, I had to try the other one... >You can also try and make the backend a kernel module - download the latest >CVS snapshot, unpack the sources and go to >sane-backends/doc/plustek >call as root usere MakeModule.sh script to compile install and load the >ptdrv >module - then after successful loading, you should change the >plustek_pp.conf >Building the kernel module needs the kernel-sources proberly installed and >configured on your box... >I'm just curious, if the module get's loaded - as it's the same code, maybe >I >made a mistake when putting something to user space.... Will do, I'll report back anything that happens, Thanks for the work, and the response. -- Nathanael _________________________________________________________________ http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines From tnorth at bluewin.ch Thu Jun 24 18:19:50 2004 From: tnorth at bluewin.ch (Thibault North) Date: Thu, 24 Jun 2004 19:19:50 +0200 Subject: [sane-devel] CanoScan5000F backend project beginning soon... Message-ID: <40DB0D36.5090508@bluewin.ch> Good afternoon, As I said it some time ago, I am going to try and make the scanner Canon canoscan5000F work... This will begin probably beginning of July, as soon as my exams are done. I have then time to work with a friend which knows more C than I do :) I wanted to know if some of you where interested in helping us (if you have this scanner) or be available to answer our questions (using IRC ?) : we have never done a project like that and it is a little frightening :) If it is the case, please answer here of @ tnorth at bluewin.ch. An adress used to communicate : http://gna.org/projects/canoscan5000F Thanks ! Thibault North P.S to Henning Meier-Geinitz : could you please send me the Perl script we spoke about which is able to filter the log file from SniffUSB ? Thank you very much, Here is the sane-find-scanner -v -v : searching for SCSI scanners: checking /dev/scanner... failed to open (Invalid argument) checking /dev/sg0... failed to open (Invalid argument) checking /dev/sg1... failed to open (Access to resource has been denied) checking /dev/sg2... failed to open (Access to resource has been denied) checking /dev/sg3... failed to open (Access to resource has been denied) checking /dev/sg4... failed to open (Access to resource has been denied) checking /dev/sg5... failed to open (Access to resource has been denied) checking /dev/sg6... failed to open (Access to resource has been denied) checking /dev/sg7... failed to open (Access to resource has been denied) checking /dev/sg8... failed to open (Access to resource has been denied) checking /dev/sg9... failed to open (Access to resource has been denied) checking /dev/sga... failed to open (Invalid argument) checking /dev/sgb... failed to open (Access to resource has been denied) checking /dev/sgc... failed to open (Access to resource has been denied) checking /dev/sgd... failed to open (Access to resource has been denied) checking /dev/sge... failed to open (Access to resource has been denied) checking /dev/sgf... failed to open (Access to resource has been denied) checking /dev/sgg... failed to open (Access to resource has been denied) checking /dev/sgh... failed to open (Access to resource has been denied) checking /dev/sgi... failed to open (Access to resource has been denied) checking /dev/sgj... failed to open (Access to resource has been denied) checking /dev/sgk... failed to open (Access to resource has been denied) checking /dev/sgl... failed to open (Access to resource has been denied) checking /dev/sgm... failed to open (Access to resource has been denied) checking /dev/sgn... failed to open (Access to resource has been denied) checking /dev/sgo... failed to open (Access to resource has been denied) checking /dev/sgp... failed to open (Access to resource has been denied) checking /dev/sgq... failed to open (Invalid argument) checking /dev/sgr... failed to open (Invalid argument) checking /dev/sgs... failed to open (Invalid argument) checking /dev/sgt... failed to open (Invalid argument) checking /dev/sgu... failed to open (Invalid argument) checking /dev/sgv... failed to open (Invalid argument) checking /dev/sgw... failed to open (Invalid argument) checking /dev/sgx... failed to open (Invalid argument) checking /dev/sgy... failed to open (Invalid argument) checking /dev/sgz... failed to open (Invalid argument) # No SCSI scanners found. If you expected something different, make sure that # you have loaded a SCSI driver for your SCSI adapter. searching for USB scanners: checking /dev/usb/scanner... failed to open (Invalid argument) checking /dev/usb/scanner0... failed to open (Invalid argument) checking /dev/usb/scanner1... failed to open (Invalid argument) checking /dev/usb/scanner2... failed to open (Invalid argument) checking /dev/usb/scanner3... failed to open (Invalid argument) checking /dev/usb/scanner4... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner5... failed to open (Invalid argument) checking /dev/usb/scanner7... failed to open (Invalid argument) checking /dev/usb/scanner8... failed to open (Invalid argument) checking /dev/usb/scanner9... failed to open (Invalid argument) checking /dev/usb/scanner10... failed to open (Invalid argument) checking /dev/usb/scanner11... failed to open (Invalid argument) checking /dev/usb/scanner12... failed to open (Invalid argument) checking /dev/usb/scanner13... failed to open (Invalid argument) checking /dev/usb/scanner14... failed to open (Invalid argument) checking /dev/usb/scanner15... failed to open (Invalid argument) checking /dev/usbscanner... failed to open (Invalid argument) checking /dev/usbscanner0... failed to open (Invalid argument) checking /dev/usbscanner1... failed to open (Invalid argument) checking /dev/usbscanner2... failed to open (Invalid argument) checking /dev/usbscanner3... failed to open (Invalid argument) checking /dev/usbscanner4... failed to open (Invalid argument) checking /dev/usbscanner5... failed to open (Invalid argument) checking /dev/usbscanner6... failed to open (Invalid argument) checking /dev/usbscanner7... failed to open (Invalid argument) checking /dev/usbscanner8... failed to open (Invalid argument) checking /dev/usbscanner9... failed to open (Invalid argument) checking /dev/usbscanner10... failed to open (Invalid argument) checking /dev/usbscanner11... failed to open (Invalid argument) checking /dev/usbscanner12... failed to open (Invalid argument) checking /dev/usbscanner13... failed to open (Invalid argument) checking /dev/usbscanner14... failed to open (Invalid argument) checking /dev/usbscanner15... failed to open (Invalid argument) trying libusb: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 1 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 2.04 iManufacturer 3 ((null)) iProduct 2 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 2 bInterval 12 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 255 bDeviceSubClass 255 bDeviceProtocol 255 bMaxPacketSize0 64 idVendor 0x04A9 idProduct 0x2212 bcdDevice 3.03 iManufacturer 2 ((null)) iProduct 3 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 39 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 192 (Self-powered) MaxPower 10 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 0 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize 512 bInterval 0 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 3 (interrupt) wMaxPacketSize 1 bInterval 8 ms bRefresh 0 bSynchAddress 0 found USB scanner (vendor=0x04a9, product=0x2212) at libusb:004:002 bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 () iProduct 2 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 8 bInterval 255 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 () iProduct 2 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 8 bInterval 255 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass 9 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0000 idProduct 0x0000 bcdDevice 0.00 iManufacturer 0 () iProduct 2 ((null)) iSerialNumber 1 ((null)) bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 64 (Self-powered) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 8 bInterval 255 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x046D idProduct 0xC00E bcdDevice 17.10 iManufacturer 1 ((null)) iProduct 2 ((null)) iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 () bmAttributes 160 (Remote Wakeup) MaxPower 98 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 bInterfaceSubClass 1 bInterfaceProtocol 2 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 4 bInterval 10 ms bRefresh 0 bSynchAddress 0 bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 224 bDeviceSubClass 1 bDeviceProtocol 1 bMaxPacketSize0 64 idVendor 0x413C idProduct 0x8000 bcdDevice 5.65 iManufacturer 0 () iProduct 0 () iSerialNumber 0 () bNumConfigurations 1 bLength 9 bDescriptorType 2 wTotalLength 193 bNumInterfaces 3 bConfigurationValue 1 iConfiguration 0 () bmAttributes 224 (Self-poweredRemote Wakeup) MaxPower 0 mA bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x81 (in 0x01) bmAttributes 3 (interrupt) wMaxPacketSize 16 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x02 (out 0x02) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x82 (in 0x02) bmAttributes 2 (bulk) wMaxPacketSize 64 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 bInterfaceSubClass 1 bInterfaceProtocol 1 iInterface 0 () bLength 7 bDescriptorType 5 bEndpointAddress 0x03 (out 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 7 bDescriptorType 5 bEndpointAddress 0x83 (in 0x03) bmAttributes 1 (isochronous) wMaxPacketSize 0 bInterval 1 ms bRefresh 0 bSynchAddress 0 bLength 9 bDescriptorType 4 bInterfaceNumber 2 bAlternateSetting 0 bNumEndpoints 0 bInterfaceClass 254 bInterfaceSubClass 1 bInterfaceProtocol 0 iInterface 0 () # 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. done From henning at meier-geinitz.de Thu Jun 24 17:25:47 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 24 Jun 2004 18:25:47 +0200 Subject: [sane-devel] Automatic update of the Webpages... In-Reply-To: <200406241009.39040.gerhard@gjaeger.de> References: <200406241009.39040.gerhard@gjaeger.de> Message-ID: <20040624162547.GA9387@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 10:09:39AM +0200, Gerhard Jaeger wrote: > how can the following site: > http://www.sane-project.org/lists/sane-mfgs-cvs.html The contents itsself is updated automatically ... > be updated? It contains currently the following sentence: > "The following table summarizes the devices supported by > sane-backends-1.0.13-cvs.", which is wrong... True. The reason is that with every CVS upload that changes a .desc file, "make" is run in the doc directory. However, for changing the version string, "configure" is also necessary. I don't want to do that everytime a commit is done so it's done manually. It's fixed now. The scripts for the automaic update of these lists (and a few other things) are in CVS (module CVSROOT) by the way. Bye, Henning From henning at meier-geinitz.de Thu Jun 24 17:44:10 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 24 Jun 2004 18:44:10 +0200 Subject: [sane-devel] Comprehensive overview... In-Reply-To: <200406241016.30645.gerhard@gjaeger.de> References: <200406241016.30645.gerhard@gjaeger.de> Message-ID: <20040624164410.GB9387@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 10:16:30AM +0200, Gerhard Jaeger wrote: > while searching for some info about the HP2400c, I noticed, that it is not > included in the unsupported.desc file... I'm also not really sure if putting all these genesys scanners into the genesys.desc file before they really work is a good idea. > The search engine delivers a result, but for "simple" users who are not using > the search engine, the information about the scanner will be not available... > I think we need one page, where all the information we have is available, even > if the scanner is supported by an external, experimental or no backend. That "one page" is the search engine. Years ago we had one big page that includes all the data ordered by backend only. The problem with that was that many "simple" users didn't notice that their scanner needed an external backend so they complained about the scanner not working even after installing sane-backends. That's the reason for the split between external and internal. The scanner search engine provides answers to the questions: "What's known about that scanner"? or "Is my scanner supported at all?" Stable/CVS manufacturer lists: "Which scanners are (un)supported by the stable/CVS version of SANE?" or: "Is my scanner supported by the sane-backends distribution"? Stable/CVS backend lists: "Which scanners are supported by a specific backend?" (mostly for developers) External backend lists: "Which scanners don't work with sane-backends but have external backends?" Older lists: "Does my scanner work without updating my older version of sane?" A lot of different lists but there is also a lot of different questions. I appreciate suggestions for a better presentation of that data. Bye, Henning From henning at meier-geinitz.de Thu Jun 24 17:55:47 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Thu, 24 Jun 2004 18:55:47 +0200 Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <20040624110526.5365.qmail@web25106.mail.ukl.yahoo.com> References: <20040624110526.5365.qmail@web25106.mail.ukl.yahoo.com> Message-ID: <20040624165547.GC9387@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 12:05:26PM +0100, Ioan-Cosmin Pop wrote: > I created the function "check_SQ113" to check the > chip > (http://picosconsult.topcities.com/downloads/check-usb-chip.c). > I test the device descriptor and the endpoints. After > that, I try to write a value (a four bytes array), What is this command or data intended to do? > but I get an error in usb_bulk_write() no matter what > I do. I tried to chage the endpoint (not to use bulk > but interrupt) but to no avail. First you must know what to send. I.e. you must know the protocol of the scanner and what commands to use or registers to set. Use a simple command (e.g. read the device identification or write and read a register value). > So, my question is: > can I get rid of this test? I see there are other > functions that don't try to write/read something from > the device. Is it safe to do this? Not really, at least if you want to be sure that you have correctly identified a chipset. The whole idea of the descriptor test is to avoid sending commands to a scanner that doesn't understand them. However, the final test if we really have found a secific chipset is done by communicating with the chipset. > After some time, I looked over the page > http://www.sane-project.org/unsupported/mustek-bearpaw-4800ta-pro-ii.html > and I saw some other chips: [...] > Does this mean I have to include tests specific to > those chips, or they behave exactly like SQ113C? They are all in the same scanner. Well, they ought to be there as somebody told me that they are there :-) Probably these chips are "helper chips" like a CCD driver, analog frontend, motor driver, RAM, EPROM, USB interface etc. So you don't need (and probably can't) test for them. Bye, Henning From anoah at pfeiffer.edu Thu Jun 24 21:01:31 2004 From: anoah at pfeiffer.edu (m. allan noah) Date: Thu, 24 Jun 2004 16:01:31 -0400 (EDT) Subject: [sane-devel] CanoScan5000F backend project beginning soon... In-Reply-To: <40DB0D36.5090508@bluewin.ch> References: <40DB0D36.5090508@bluewin.ch> Message-ID: asking for help on this list, and posting your sniffer logs up on the web usually will get some helpful pointers, but you are going to have to do most of the work, since you own the scanner. the script that henning may have mentioned is called spike. you cant look for it online. however, it only works with certain older versions of usbsnoopy. i have written a replacement for it, called spike4, which is attached to this mail. spike4 understands benoit's usb sniffer (which i highly recommend) logs. it is availible after a little googling as well. allan On Thu, 24 Jun 2004, Thibault North wrote: > Good afternoon, > As I said it some time ago, I am going to try and make the scanner Canon > canoscan5000F work... This will begin probably beginning of July, as > soon as my exams are done. I have then time to work with a friend which > knows more C than I do :) > I wanted to know if some of you where interested in helping us (if you > have this scanner) or be available to answer our questions (using IRC ?) > : we have never done a project like that and it is a little frightening :) > > If it is the case, please answer here of @ tnorth at bluewin.ch. > An adress used to communicate : http://gna.org/projects/canoscan5000F > > Thanks ! > > Thibault North > > P.S to Henning Meier-Geinitz : could you please send me the Perl script > we spoke about which is able to filter the log file from SniffUSB ? > Thank you very much, > > Here is the sane-find-scanner -v -v : > > > searching for SCSI scanners: > checking /dev/scanner... failed to open (Invalid argument) > checking /dev/sg0... failed to open (Invalid argument) > checking /dev/sg1... failed to open (Access to resource has been denied) > checking /dev/sg2... failed to open (Access to resource has been denied) > checking /dev/sg3... failed to open (Access to resource has been denied) > checking /dev/sg4... failed to open (Access to resource has been denied) > checking /dev/sg5... failed to open (Access to resource has been denied) > checking /dev/sg6... failed to open (Access to resource has been denied) > checking /dev/sg7... failed to open (Access to resource has been denied) > checking /dev/sg8... failed to open (Access to resource has been denied) > checking /dev/sg9... failed to open (Access to resource has been denied) > checking /dev/sga... failed to open (Invalid argument) > checking /dev/sgb... failed to open (Access to resource has been denied) > checking /dev/sgc... failed to open (Access to resource has been denied) > checking /dev/sgd... failed to open (Access to resource has been denied) > checking /dev/sge... failed to open (Access to resource has been denied) > checking /dev/sgf... failed to open (Access to resource has been denied) > checking /dev/sgg... failed to open (Access to resource has been denied) > checking /dev/sgh... failed to open (Access to resource has been denied) > checking /dev/sgi... failed to open (Access to resource has been denied) > checking /dev/sgj... failed to open (Access to resource has been denied) > checking /dev/sgk... failed to open (Access to resource has been denied) > checking /dev/sgl... failed to open (Access to resource has been denied) > checking /dev/sgm... failed to open (Access to resource has been denied) > checking /dev/sgn... failed to open (Access to resource has been denied) > checking /dev/sgo... failed to open (Access to resource has been denied) > checking /dev/sgp... failed to open (Access to resource has been denied) > checking /dev/sgq... failed to open (Invalid argument) > checking /dev/sgr... failed to open (Invalid argument) > checking /dev/sgs... failed to open (Invalid argument) > checking /dev/sgt... failed to open (Invalid argument) > checking /dev/sgu... failed to open (Invalid argument) > checking /dev/sgv... failed to open (Invalid argument) > checking /dev/sgw... failed to open (Invalid argument) > checking /dev/sgx... failed to open (Invalid argument) > checking /dev/sgy... failed to open (Invalid argument) > checking /dev/sgz... failed to open (Invalid argument) > # No SCSI scanners found. If you expected something different, make > sure that > # you have loaded a SCSI driver for your SCSI adapter. > > searching for USB scanners: > checking /dev/usb/scanner... failed to open (Invalid argument) > checking /dev/usb/scanner0... failed to open (Invalid argument) > checking /dev/usb/scanner1... failed to open (Invalid argument) > checking /dev/usb/scanner2... failed to open (Invalid argument) > checking /dev/usb/scanner3... failed to open (Invalid argument) > checking /dev/usb/scanner4... failed to open (Invalid argument) > checking /dev/usb/scanner5... failed to open (Invalid argument) > checking /dev/usb/scanner5... failed to open (Invalid argument) > checking /dev/usb/scanner7... failed to open (Invalid argument) > checking /dev/usb/scanner8... failed to open (Invalid argument) > checking /dev/usb/scanner9... failed to open (Invalid argument) > checking /dev/usb/scanner10... failed to open (Invalid argument) > checking /dev/usb/scanner11... failed to open (Invalid argument) > checking /dev/usb/scanner12... failed to open (Invalid argument) > checking /dev/usb/scanner13... failed to open (Invalid argument) > checking /dev/usb/scanner14... failed to open (Invalid argument) > checking /dev/usb/scanner15... failed to open (Invalid argument) > checking /dev/usbscanner... failed to open (Invalid argument) > checking /dev/usbscanner0... failed to open (Invalid argument) > checking /dev/usbscanner1... failed to open (Invalid argument) > checking /dev/usbscanner2... failed to open (Invalid argument) > checking /dev/usbscanner3... failed to open (Invalid argument) > checking /dev/usbscanner4... failed to open (Invalid argument) > checking /dev/usbscanner5... failed to open (Invalid argument) > checking /dev/usbscanner6... failed to open (Invalid argument) > checking /dev/usbscanner7... failed to open (Invalid argument) > checking /dev/usbscanner8... failed to open (Invalid argument) > checking /dev/usbscanner9... failed to open (Invalid argument) > checking /dev/usbscanner10... failed to open (Invalid argument) > checking /dev/usbscanner11... failed to open (Invalid argument) > checking /dev/usbscanner12... failed to open (Invalid argument) > checking /dev/usbscanner13... failed to open (Invalid argument) > checking /dev/usbscanner14... failed to open (Invalid argument) > checking /dev/usbscanner15... failed to open (Invalid argument) > trying libusb: > > > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 9 > bDeviceSubClass 0 > bDeviceProtocol 1 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 2.04 > iManufacturer 3 ((null)) > iProduct 2 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 64 (Self-powered) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 2 > bInterval 12 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 255 > bDeviceSubClass 255 > bDeviceProtocol 255 > bMaxPacketSize0 64 > idVendor 0x04A9 > idProduct 0x2212 > bcdDevice 3.03 > iManufacturer 2 ((null)) > iProduct 3 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 39 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 192 (Self-powered) > MaxPower 10 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 0 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 2 (bulk) > wMaxPacketSize 512 > bInterval 0 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 (out 0x02) > bmAttributes 2 (bulk) > wMaxPacketSize 512 > bInterval 0 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 3 (interrupt) > wMaxPacketSize 1 > bInterval 8 ms > bRefresh 0 > bSynchAddress 0 > found USB scanner (vendor=0x04a9, product=0x2212) at libusb:004:002 > > > bLength 18 > bDescriptorType 1 > bcdUSB 1.00 > bDeviceClass 9 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 0.00 > iManufacturer 0 () > iProduct 2 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 64 (Self-powered) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 8 > bInterval 255 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 1.00 > bDeviceClass 9 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 0.00 > iManufacturer 0 () > iProduct 2 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 64 (Self-powered) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 8 > bInterval 255 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 1.00 > bDeviceClass 9 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x0000 > idProduct 0x0000 > bcdDevice 0.00 > iManufacturer 0 () > iProduct 2 ((null)) > iSerialNumber 1 ((null)) > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 25 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 64 (Self-powered) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 9 > bInterfaceSubClass 0 > bInterfaceProtocol 0 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 8 > bInterval 255 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 2.00 > bDeviceClass 0 > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 8 > idVendor 0x046D > idProduct 0xC00E > bcdDevice 17.10 > iManufacturer 1 ((null)) > iProduct 2 ((null)) > iSerialNumber 0 () > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 34 > bNumInterfaces 1 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 160 (Remote Wakeup) > MaxPower 98 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 > bInterfaceSubClass 1 > bInterfaceProtocol 2 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 4 > bInterval 10 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 224 > bDeviceSubClass 1 > bDeviceProtocol 1 > bMaxPacketSize0 64 > idVendor 0x413C > idProduct 0x8000 > bcdDevice 5.65 > iManufacturer 0 () > iProduct 0 () > iSerialNumber 0 () > bNumConfigurations 1 > > bLength 9 > bDescriptorType 2 > wTotalLength 193 > bNumInterfaces 3 > bConfigurationValue 1 > iConfiguration 0 () > bmAttributes 224 (Self-poweredRemote Wakeup) > MaxPower 0 mA > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 3 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 (in 0x01) > bmAttributes 3 (interrupt) > wMaxPacketSize 16 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x02 (out 0x02) > bmAttributes 2 (bulk) > wMaxPacketSize 64 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 (in 0x02) > bmAttributes 2 (bulk) > wMaxPacketSize 64 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 2 > bInterfaceClass 224 > bInterfaceSubClass 1 > bInterfaceProtocol 1 > iInterface 0 () > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x03 (out 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 (in 0x03) > bmAttributes 1 (isochronous) > wMaxPacketSize 0 > bInterval 1 ms > bRefresh 0 > bSynchAddress 0 > > > bLength 9 > bDescriptorType 4 > bInterfaceNumber 2 > bAlternateSetting 0 > bNumEndpoints 0 > bInterfaceClass 254 > bInterfaceSubClass 1 > bInterfaceProtocol 0 > iInterface 0 () > # 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. > done > > > -- "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 -------------- #! /usr/bin/perl # simple log reformatter for benoit's sniffusb.exe # public domain. by anoah at pfeiffer.edu use strict; my $count=0; my $lastUrbLTime=0; my @buffer; while (my $line = ) { if ( $line =~ m/>>>/ ) { dumper(@buffer) if $count; @buffer = (); $count++; } if ( $line =~ m/UsbSnoop/ ){next;} push(@buffer,$line); } dumper(@buffer) if $count; sub dumper { my $dir='out'; my $type='C'; my $data=(); my $urb=0; my $ep=''; my $fTime=0; my $lTime=0; foreach my $line (@_) { if($line =~ m/\[(\d+) ms\] .* URB (\d+) going down/){ $fTime=$1; $urb=$2; print "\npause " . ($fTime-$lastUrbLTime) . " ms\n\n"; } elsif ( $line =~ m/USBD_TRANSFER_DIRECTION_IN/ ) { $dir='in'; $data=(); } elsif ( $line =~ m/-- URB_FUNCTION_BULK_OR_INTERRUPT_TRANSFER/ ) { $type='B'; } elsif( $line =~ m/PipeHandle.*endpoint (0x\d+)/){ $ep=$1; } elsif ( $line =~ m / ([0-9a-f]{8}: )([0-9a-f ]*)/ ) { push(@{$data}, $1 . $2); } if ( $line =~ m/\[(\d+) ms\]/ ){ $lTime=$1; } $ep=~s/^0x0+//; } if($dir eq 'in'){ print "Urb $urb ($type) ep=$ep (read) "; } else{ print "Urb $urb ($type) ep=$ep (write) "; } print $lTime-$fTime . " ms\n"; foreach my $line (@{$data}) { printf(" %s", $line); print "\n"; } $lastUrbLTime=$lTime; } exit 0; From news at vlado-do.de Thu Jun 24 23:12:04 2004 From: news at vlado-do.de (Vlado Plaga) Date: Fri, 25 Jun 2004 00:12:04 +0200 Subject: [sane-devel] plustek_pp backend doesn't like my parport scanner anymore Message-ID: <40DB51B4.2020109@vlado-do.de> Hi! Afer having updated my Debian "testing" distribution a few weeks ago my Plustek OpticPro 9636T suddenly stopped working. So far everything had worked fine but although I tried various combinations of diffenrent backend versions, module parameters and even a self-compiled sane I did only get scans with strange colors (which is better than nothing but not really helpful) and a lot of debugging information. The last kernel module that worked for me was from the file plustek-module-0_41_5.tar.gz but identified as pt_drv : driver version 0.41-6 I still have a Debian testing system (on a hard disk that I'm not using anymore) where the scanner works. But I don't want to continue using that system without updates, because Debian's testing systems change over time, which makes it impossible to install new packages (because of dependencies). Unfortunatley the updates I already made (now on a different hard disk) rendered the scanner unusable... I compiled with DEBUG=y and now I'll quote some output from syslog, but not everything, as it is quite long: Jun 24 09:04:26 koala kernel: ********************************************* Jun 24 09:04:26 koala kernel: pt_drv: init_module() Jun 24 09:04:26 koala kernel: pt_drv : driver version 0.41-6 Jun 24 09:04:26 koala kernel: ProcFsInitialize() Jun 24 09:04:26 koala kernel: ptdrvInit(0) Jun 24 09:04:26 koala kernel: Init settings done Jun 24 09:04:26 koala kernel: ScanData = 0xcdd68000 Jun 24 09:04:26 koala kernel: Using fast I/O Jun 24 09:04:26 koala kernel: Requested port at 0x378 Jun 24 09:04:26 koala kernel: Requested port (0x378) found Jun 24 09:04:26 koala kernel: Port mode reported: (0x005f) Jun 24 09:04:26 koala kernel: Port for device 0 registered Jun 24 09:04:26 koala kernel: ptdrvOpen(port=0x378) Jun 24 09:04:26 koala kernel: Try to claim the parport Jun 24 09:04:26 koala kernel: parport-modi: SPP PS/2 EPP ECP EPP(ECP) PS/2(ECP) Jun 24 09:04:26 koala kernel: Using EPP-mode Jun 24 09:04:26 koala kernel: Trying faster mode... Jun 24 09:04:26 koala kernel: Attempting to set EPP from ECP mode. Jun 24 09:04:26 koala kernel: Port is set to (ECP) EPP mode. Jun 24 09:04:26 koala kernel: Starting Scanner-Autodetection [...] Jun 24 09:04:26 koala kernel: ************* ASIC98001 ************* Jun 24 09:04:26 koala kernel: ModelSet9636() Jun 24 09:04:26 koala kernel: ModelSet9360() Jun 24 09:04:26 koala kernel: modelInitPageSettings() Jun 24 09:04:26 koala kernel: A4 set Jun 24 09:04:26 koala kernel: ModelSet9630() done. Jun 24 09:04:26 koala kernel: modelInitPageSettings() Jun 24 09:04:26 koala kernel: A4 set Jun 24 09:04:26 koala kernel: ModelSet9636() done. Jun 24 09:04:26 koala kernel: P9636InitAsic() Jun 24 09:04:26 koala kernel: DacInitialize() Jun 24 09:04:26 koala kernel: ImageInitialize() Jun 24 09:04:26 koala kernel: IOFuncInitialize() Jun 24 09:04:26 koala kernel: IOInitialize() Jun 24 09:04:26 koala kernel: MotorInitialize() Jun 24 09:04:26 koala kernel: 0x81 Jun 24 09:04:26 koala kernel: CCID = 0x00 Jun 24 09:04:26 koala kernel: P9636InitAsic() done. Jun 24 09:04:26 koala kernel: Dataport = 0x0378 Jun 24 09:04:26 koala kernel: Ctrlport = 0x037a Jun 24 09:04:26 koala kernel: Test 0x55 Jun 24 09:04:26 koala kernel: Test 0xAA Jun 24 09:04:26 koala kernel: Compare data=0x7e and status=0x1e, port=0x378 Jun 24 09:04:26 koala kernel: ioP98ReadWriteTest() Jun 24 09:04:26 koala kernel: Putting Scanner (ASIC 98001) into Idle-Mode Jun 24 09:04:26 koala kernel: detectScannerConnection() returns 0. Jun 24 09:04:26 koala kernel: p9636InitP98001(0) Jun 24 09:04:26 koala kernel: bData = 0x0000, PCB-ID = 0x00 Jun 24 09:04:26 koala kernel: CCD-ID = 0x00 = _CCD_3797 Jun 24 09:04:26 koala kernel: bSetScanModeFlag = 0 Jun 24 09:04:26 koala kernel: *** setupBuffers *** Jun 24 09:04:26 koala kernel: Driverbuf(147360 bytes) needed ! Jun 24 09:04:26 koala kernel: pColorRunTab = 0xd0a3652c - 0xd0a35fa0 Jun 24 09:04:26 koala kernel: Adjust for 98001 ASIC Jun 24 09:04:26 koala kernel: sb2 = 0xd0a12000, sb1 = 0xd0a1cbe0, Color = 0xd0a2cdb0 Jun 24 09:04:26 koala kernel: Pro = 0xd0a323a0, size = 147360 Jun 24 09:04:26 koala kernel: *** DETECTION DONE, result: 0 *** Now the failed detection: Jun 3 23:16:10 koala kernel: ********************************************* Jun 3 23:16:10 koala kernel: pt_drv: init_module() Jun 3 23:16:10 koala kernel: pt_drv : driver version 0.41-6 Jun 3 23:16:10 koala kernel: ProcFsInitialize() Jun 3 23:16:10 koala kernel: ptdrvInit(0) Jun 3 23:16:10 koala kernel: Init settings done Jun 3 23:16:10 koala kernel: ScanData = 0xce960000 Jun 3 23:16:10 koala kernel: Using fast I/O Jun 3 23:16:10 koala kernel: Requested port at 0x378 Jun 3 23:16:10 koala kernel: Requested port (0x378) found Jun 3 23:16:10 koala kernel: Port mode reported: (0x0047) Jun 3 23:16:10 koala kernel: Port for device 0 registered Jun 3 23:16:10 koala kernel: ptdrvOpen(port=0x378) Jun 3 23:16:10 koala kernel: Try to claim the parport Jun 3 23:16:10 koala kernel: parport-modi: SPP PS/2 EPP EPP(ECP) PS/2(ECP) Jun 3 23:16:10 koala kernel: Using EPP-mode Jun 3 23:16:10 koala kernel: Starting Scanner-Autodetection [...] Jun 3 23:16:10 koala kernel: ************* ASIC98001 ************* Jun 3 23:16:10 koala kernel: ModelSet9636() Jun 3 23:16:10 koala kernel: ModelSet9360() [...just like in the successful case before...] Jun 3 23:16:10 koala kernel: Test 0x55 Jun 3 23:16:10 koala kernel: Test 0xAA Jun 3 23:16:10 koala kernel: Compare data=0x7f and status=0x1f, port=0x378 Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: ioP98ReadWriteTest() Jun 3 23:16:10 koala kernel: Error in memory test at pos 0 (0 != 255) Jun 3 23:16:10 koala kernel: detectScannerConnection() returns -9020. Jun 3 23:16:10 koala kernel: *** DETECTION DONE, result: -9020 *** Now there already was a difference in the automatic parport mode selection. Detection does work when I tell the module to use the SPP mode (forceMode=1) - but then sane produces some pretty ugly colors. Hopefully someone can tell me how to fix this. I would really hate having done all this in vain and not being able to use the scanner without rebooting any more. Cheers, Vlado From jgato at lambdaux.com Thu Jun 24 10:37:15 2004 From: jgato at lambdaux.com (jose) Date: Thu, 24 Jun 2004 11:37:15 +0200 Subject: [sane-devel] sane-desc to xml Message-ID: <1088069835.3362.9.camel@localhost> Hi again, thanks for te information about sane-desc, very usefull tool. No Im thinking on add a new function to sane-desc to get a output in XML format (very easy to parser). I have the code done it but I need to know what should I do... I guess that I have to send the patch and then you say that its "ok" for including it... The new code is really very simple, cause is the same like ASCII but with tags. Bye... From jgato at lambdaux.com Thu Jun 24 13:05:57 2004 From: jgato at lambdaux.com (jose) Date: Thu, 24 Jun 2004 14:05:57 +0200 Subject: [sane-devel] a new function for sane-desc! Message-ID: <1088078757.3362.61.camel@localhost> Hi, finally I have made a new function in sane-desc to get an xml output. I think that only have to send the patch, if there is any problem please email me, this is the first time that I make something similar.. Bye, -------------- next part -------------- --- sane-desc.c Thu Jun 24 13:43:48 2004 +++ sane-desc.c.new Thu Jun 24 11:55:34 2004 @@ -65,6 +65,7 @@ typedef enum output_mode { output_mode_ascii = 0, + output_mode_xml, output_mode_html_backends, output_mode_html_backends_split, output_mode_html_mfgs @@ -308,6 +309,11 @@ DBG_INFO ("Output mode: ascii\n"); mode = output_mode_ascii; } + else if (strcmp (optarg, "xml") ==0) + { + DBG_INFO ("Output mode: xml\n"); + mode = output_mode_xml; + } else if (strcmp (optarg, "html-backends-split") == 0) { DBG_INFO ("Output mode: html-backends-split\n"); @@ -1609,6 +1615,193 @@ } /* while (be) */ } +/* Print an XML list with all the information we have */ +static void +xml_print_backends (void) +{ + backend_entry *be; + + be = first_backend; + while (be) + { + url_entry *url = be->url; + type_entry *type = be->type; + + if (be->name) + printf ("\n",be->name); + else + printf ("\n"); + + if (be->version) + printf ("%s \n", be->version); + else + printf ("*none*\n"); + + if (be->new) + printf (" NEW!\n"); + + if (be->manpage) + printf (" %s\n", be->manpage); + else + printf (" *none*\n"); + + if (url) + while (url) + { + printf (" %s\n", url->name); + url = url->next; + } + else + printf (" *none*\n"); + + if (be->comment) + printf (" %s\n", be->comment); + else + printf (" *none*\n"); + + if (type) + while (type) + { + switch (type->type) + { + case type_scanner: + printf (" scanner\n"); + break; + case type_stillcam: + printf (" stillcam\n"); + break; + case type_vidcam: + printf (" vidcam \n"); + break; + case type_meta: + printf (" meta\n"); + break; + case type_api: + printf (" api\n"); + break; + default: + printf (" *unknown* \n"); + break; + } + if (type->desc) + { + url_entry *url = type->desc->url; + printf (" %s\n", type->desc->desc); + if (url) + while (url) + { + printf (" %s\n", url->name); + url = url->next; + } + else + printf (" *none*\n"); + + if (type->desc->comment) + printf (" %s\n", type->desc->comment); + else + printf (" *none*\n"); + } + else if (type->type >= type_meta) + printf (" *none*\n"); + + if (type->mfg) + { + mfg_entry *mfg = type->mfg; + while (mfg) + { + model_entry *model = mfg->model; + url_entry *url = mfg->url; + + printf (" \n", mfg->name); + if (url) + while (url) + { + printf (" `%s'\n", url->name); + url = url->next; + } + else + printf (" *none*\n"); + + if (mfg->comment) + printf (" %s\n", mfg->comment); + else + printf (" *none*\n"); + + if (model) + while (model) + { + url_entry *url = model->url; + printf (" \n", model->name); + if (model->interface) + printf (" %s\n", model->interface); + else + printf (" *none*\n"); + + if (model->status == status_unknown) + model->status = be->status; + switch (model->status) + { + case status_minimal: + printf (" minimal\n"); + break; + case status_basic: + printf (" basic\n"); + break; + case status_good: + printf (" good\n"); + break; + case status_complete: + printf (" complete\n"); + break; + case status_untested: + printf (" untested\n"); + break; + case status_unsupported: + printf (" unsupported\n"); + break; + default: + printf (" *unknown*\n"); + break; + } + + if (url) + while (url) + { + printf (" %s\n", url->name); + url = url->next; + } + else + printf (" *none*\n"); + + if (model->comment) + printf (" %s\n", model->comment); + else + printf (" *none*\n"); + + model = model->next; + printf(" \n"); + } /* while (model) */ + else + printf (" \n"); + + printf(" \n"); + mfg = mfg->next; + } /* while (mfg) */ + } + else if (type->type < type_meta) + printf (" *none*\n"); + type = type->next; + } /* while (type) */ + else + printf (" *none*\n"); + printf("\n"); + be = be->next; + + } /* while (be) */ +} + + + /* Generate a name used for HTML tags */ static char * html_generate_anchor_name (device_type dev_type, char *manufacturer_name) @@ -2296,6 +2489,9 @@ { case output_mode_ascii: ascii_print_backends (); + break; + case output_mode_xml: + xml_print_backends(); break; case output_mode_html_backends_split: html_print_backends_split (); From picos132004 at yahoo.co.uk Fri Jun 25 12:16:27 2004 From: picos132004 at yahoo.co.uk (=?iso-8859-1?q?Ioan-Cosmin=20Pop?=) Date: Fri, 25 Jun 2004 12:16:27 +0100 (BST) Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <20040624165547.GC9387@meier-geinitz.de> Message-ID: <20040625111628.34893.qmail@web25104.mail.ukl.yahoo.com> I looked again over the windows sources and I found that I was mistaken. I want to identify the chip so I was trying to use usb_bulk_write to send an array of 4 bytes then read them. Looking again over the windows sources (after about 2 months) revealed something I wasn't aware of. This proves the necessity of a vacation :) Oh, and btw, I have to restart hotplug after every unsuccesfull debug... I was innocent enough thinking I don't have to :( I was trying to write 'dddd', because I thought this is the test I should do. So I was trying to write this string and if I could read it succesfully, it would be OK. Wrong!! It's true, I have to send an array of 4 bytes, but this array has to be carefully crafted. Right now I'm looking over the sources. Henning, you keep telling me about the "protocol of the scanner", "commands" and "registers". Can you please tell me what they mean? OK, I know this sounds stupid. I know what a protocol, command or register is. Back in the good ol' DOS days (well, not so good, but old for sure) I used to read/write to a specific port and mess with the device registers (an aquisition device in my case). I can only make some suppositions. Please tell me if I'm correct and if I'm on the right way. - for the "protocol", I think this is something like: buffered or direct; - for commands, I have some "IOCTL functions" - as for "registers", I really have no idea. What I have so far, are some macros (taken from the windows sources), like IOCTL_GET_VERSION, IOCTL_WRITE_REGISTERS, IOCTL_READ_REGISTERS and so on. They combine information such as acces mode, device type (fixed as scanner in my case), function. I feel I can use much of this information. I believe we are using different words for the same thing. I'm currently away from my computer (and I'll come back sunday), so I don't have the chance to test this right now. If somebody can understand my rumble-mumble, please guide me. I feel lost :) Poor me! I think I really need some help, somebody to talk to. Ronald Humphries, do you read this? If you do have some spare time, can you please send me a message? I can't send you the windows sources because I am bound by an NDA (non-disclosure agreement) with Mustek, but I'm sure we can cut a deal with them to offer you the same info they gave me...:) Thank you Cosmin ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com From johnb51 at earthlink.net Fri Jun 25 15:03:42 2004 From: johnb51 at earthlink.net (John) Date: Fri, 25 Jun 2004 10:03:42 -0400 Subject: [sane-devel] hp psc1210 printer,scanner,copier Message-ID: <40DC30BE.1050109@earthlink.net> I have the above multi-function hooked up to mandrake 10 os. The scanner process doesn't work with gimp 2.0. It needs the updated xsane plugin. Gimp 1.2 and xsane .92 plugin returned message that it could not detect scanner. I would appreciate any help or info. on how to get the scanner going. Thanks (from linux newbie) John From henning at meier-geinitz.de Fri Jun 25 17:02:59 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 18:02:59 +0200 Subject: [sane-devel] sane-desc to xml In-Reply-To: <1088069835.3362.9.camel@localhost> References: <1088069835.3362.9.camel@localhost> Message-ID: <20040625160259.GB12809@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 11:37:15AM +0200, jose wrote: > No Im thinking on add a new function to sane-desc to get a output in XML > format (very easy to parser). I have the code done Ah, very nice. > it but I need to know > what should I do... I guess that I have to send the patch and then you > say that its "ok" for including it... Yes, please send a unified diff. Bye, Henning From henning at meier-geinitz.de Fri Jun 25 17:58:40 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 18:58:40 +0200 Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <20040625111628.34893.qmail@web25104.mail.ukl.yahoo.com> References: <20040624165547.GC9387@meier-geinitz.de> <20040625111628.34893.qmail@web25104.mail.ukl.yahoo.com> Message-ID: <20040625165840.GC12809@meier-geinitz.de> Hi, On Fri, Jun 25, 2004 at 12:16:27PM +0100, Ioan-Cosmin Pop wrote: > Henning, you keep telling me about the "protocol of > the scanner", "commands" and "registers". Can you > please tell me what they mean? OK, I know this sounds > stupid. I know what a protocol, command or register > is. Back in the good ol' DOS days (well, not so good, > but old for sure) I used to read/write to a specific > port and mess with the device registers (an aquisition > device in my case). I can only make some suppositions. > Please tell me if I'm correct and if I'm on the right > way. > - for the "protocol", I think this is something like: > buffered or direct; No. What I mean by "protocol" is how the driver/backend communicates with the scanner. As an example, I'll describe the protocol of the GrandTech GT6801 chipset. Your scanner's protocol will be completely different most probably. Commands and data are sent to the scanner as USB control messages with a data size of 64 bytes. The request, request_type, value etc. depend on the type of command. E.g. you can send commands, receive results from commands, write data to scanner's RAM (firmware) and read from the RAM. This is an example for a command sent to the scanner (from a sniffusb log of a Mustek BearPaw 2400 TA Plus: | >>> URB 525 going down >>> | -- URB_FUNCTION_VENDOR_DEVICE: | TransferFlags = 00000000 | (USBD_TRANSFER_DIRECTION_OUT, ~USBD_SHORT_TRANSFER The data is sent from the host to the scanner. | TransferBufferLength = 00000040 64 bytes of data. | TransferBuffer = c1b6b000 | TransferBufferMDL = 00000000 | 0000: 20 01 0f 01 29 05 a4 00 58 02 82 20 64 00 01 00 The data itself. For the gt6801, the first byte is the command code. 0x20 means "setup scan". The second byte is alway 01. Bytes 2+3 and 3+4 are the Y coordinates of the scan widow (Y0 + height). The first byte is the low byte. In this case the height is 0x0529 = 1321. As these coordinates are based on 1200 dpi, the height is 1.1 inches in this case. Byte 0x0a ("82") means gray mode. Byte 0x0c ("64") and 0x0d ("00") are the resolution: 0x0064 = 100 dpi. | 0010: 64 00 73 00 0b 00 64 00 3c 00 00 00 00 00 00 00 | 0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | 0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 More settings like lamp, backtracking, bytes per line etc. | UrbLink = 00000000 | RequestTypeReservedBits = 00 | Request = 01 | Value = 2010 That means "send a command". For writing firmware "200b" would be used. | Index = 3f40 Not used here but for firmware writes that would be the memory address to write to. Now the data is sent. As confirmation you get the URB back from the (Windows) operating system (see the same URB number): | <<< URB 525 coming back <<< | -- URB_FUNCTION_CONTROL_TRANSFER: | PipeHandle = C1AD431C | TransferFlags = 00000002 | (USBD_TRANSFER_DIRECTION_OUT, USBD_SHORT_TRANSFER_OK) | TransferBufferLength = 00000040 | TransferBuffer = c1b6b000 | TransferBufferMDL = c1800880 | UrbLink = 00000000 | SetupPacket : 40 01 10 20 40 3f 40 00 The setup packet is the same as above but this time it's not split in request, value etc. See the USB spec for details. Now we ask for the result of the command we just sent: | >>> URB 526 going down >>> | -- URB_FUNCTION_VENDOR_DEVICE: | TransferFlags = 00000001 | (USBD_TRANSFER_DIRECTION_IN, ~USBD_SHORT_TRANSFER_ We want to receive data from the scanner (DIRECTION_IN). | TransferBufferLength = 00000040 We want to get 64 bytes. | TransferBuffer = e3c09d1c | TransferBufferMDL = 00000000 | UrbLink = 00000000 | RequestTypeReservedBits = 00 | Request = 01 | Value = 2011 That means: "Read result of command". | Index = 3f00 See above. Ok, now the result: | <<< URB 526 coming back <<< | -- URB_FUNCTION_CONTROL_TRANSFER: | PipeHandle = C1AD431C | TransferFlags = 00000003 | (USBD_TRANSFER_DIRECTION_IN, USBD_SHORT_TRANSFER_OK) | TransferBufferLength = 00000040 | TransferBuffer = e3c09d1c | TransferBufferMDL = c1800880 | 0000: 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 The first 00 means that the command succeeded. The second byte "20" repeats the command we sent ("setup scan"). Other commands may return more data (e.g. the status of scan buttons or a flag if the scan head is at its home position). The actual scan data is read by bulk reads. That's what I mean by a "protocol". Other chipsets don't use commands (or functions) like in this case but you can set registers. E.g. you could use a three byte block of data sent by bulk messages: 01 02 03 01 --> type = write register 02 --> register number 03 --> value to write to the register That's just a protocolo I made up :-) > - for commands, I have some "IOCTL functions" > - as for "registers", I really have no idea. The scanner's chipset may have a buch of registers to which you can write data. E.g. One register may contain the resolution. When setting a bit in another register you could start scanning. Think of registers as processor registers. > What I have so far, are some macros (taken from the > windows sources), like IOCTL_GET_VERSION, > IOCTL_WRITE_REGISTERS, IOCTL_READ_REGISTERS and so on. Probably that's how the Windows low level scanner driver is accessed. This low level driver is able to do basic stuff like writing the scaynners registers. The higher level software talks to it via ioctls. (Just a guess but that's similar to how it works with Linux). > I think I really need some help, somebody to talk > to. Ronald Humphries, do you read this? If you do have > some spare time, can you please send me a message? I > can't send you the windows sources because I am bound > by an NDA (non-disclosure agreement) with Mustek, but > I'm sure we can cut a deal with them to offer you the > same info they gave me...:) Try to go down to the lowest level of the Windows source code. Look for functions that actually write to the scanner. Bye, Henning From henning at meier-geinitz.de Fri Jun 25 18:03:32 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 19:03:32 +0200 Subject: [sane-devel] donation / scanner support In-Reply-To: <40DABFC4.9030102@alphacent.com> References: <40DABFC4.9030102@alphacent.com> Message-ID: <20040625170332.GD12809@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 11:49:24AM +0000, Florent Aide wrote: > I have a Dell A920 (rebranded Lexmark X1150) that is currently marked on > the website as not supported. Since I have two of these little things I > am willing to donate one of them to the project in order to see scanner > support for it. Thanks for your offer! > How can I do that ? Is someone willing to accept this donation and work > on the scanner part of the Dell A920 ? Unfortunately there is no SANE backend yet for the RTS8852B chipset as far as I know. So you can't just send it to the backend maintainer. Maybe someone wants to start writing a backend for that scanner? Bye, Henning From henning at meier-geinitz.de Fri Jun 25 18:09:17 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 19:09:17 +0200 Subject: [sane-devel] a new function for sane-desc! In-Reply-To: <1088078757.3362.61.camel@localhost> References: <1088078757.3362.61.camel@localhost> Message-ID: <20040625170917.GE12809@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 02:05:57PM +0200, jose wrote: > Hi, finally I have made a new function in sane-desc to get an xml > output. > > I think that only have to send the patch, if there is any problem please > email me, this is the first time that I make something similar.. Ah, there it is. I should really read all sane-devel messages before answering... Looks fine. If nobody objects I'll add it to CVS. Bye, Henning From henning at meier-geinitz.de Fri Jun 25 18:18:15 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Fri, 25 Jun 2004 19:18:15 +0200 Subject: [sane-devel] CanoScan5000F backend project beginning soon... In-Reply-To: <40DB0D36.5090508@bluewin.ch> References: <40DB0D36.5090508@bluewin.ch> Message-ID: <20040625171815.GF12809@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 07:19:50PM +0200, Thibault North wrote: > I wanted to know if some of you where interested in helping us (if you > have this scanner) or be available to answer our questions (using IRC ?) Ask on this list or ask on IRC (#sane on freenode.net). On IRC, be patient as questions may be answered hours later when someone wakes up :-) > An adress used to communicate : http://gna.org/projects/canoscan5000F I have added a link to that page to our Canon 5000f page: http://www.sane-project.org/unsupported/canon-5000f.html > P.S to Henning Meier-Geinitz : could you please send me the Perl script > we spoke about which is able to filter the log file from SniffUSB ? I don't really remeber using such a perl script. I know that there is (or was) one, but I think I never really used it. Sometimes I use a C program to analyse sniffusb log files but that program is really specific for the GT6801 chipset and filters only some special commands so I think it's not useful for anyone else. Bye, Henning From rene at rocklinux-consulting.de Fri Jun 25 22:20:57 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Fri, 25 Jun 2004 23:20:57 +0200 (CEST) Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040609151818.GO7920@meier-geinitz.de> References: <20040601215656.GA3524@ffii.org> <20040609134039.GA3769@ffii.org> <20040609151818.GO7920@meier-geinitz.de> Message-ID: <20040625.232057.576037890.rene@rocklinux-consulting.de> Hi, On: Wed, 9 Jun 2004 17:18:18 +0200, Henning Meier-Geinitz wrote: > Timeouts: > - HP5370C (avision) on UHCI VIA, Linux 2.6.5 > - HP7450C (avision), sane-backends 1.0.14 (also tried latest avision > code), Linux 2.6.5 > - HP7400 (avision) on UHCI (Intel Corp. 82371AB/EB/MB PIIX4 USB) Asus > board, sane-backends 1.0.14, Linux 2.6.3, 2.6.5, 2.6.6 and > 2.6.7-rc2-bk7 > - HP7450C (avision), there was a hint about the hpusbscsi driver > making trouble in that case > > - Epson Perfection 1670 (snapscan) on UHCI VIA, sane-backends 1.0.14, > Linux 2.6.5-mm2 > > No timeouts: > - Several Mustek+Plustek scanners (mustek_usb, plustek, gt68xx), > sane-backends 1.0.14, on OHCI + UHCI (VIA PCI card) on Linux 2.6.7-rc2 > and Linux 2.4.26 > - Avision scanners, on OHCI, sane-backends 1.0.14 + latest avison code on Linux > 2.6.3 (UltraSparc +iBook) I flushed my Avision TODO list a bit and so tested the Avision backend with a more recent kernel: 2.6.7 works fine on PowerPC OHCI. I still plan to find a box to test a UHCI. > An unrelated bug showed the same timeouts: > - Epson Perfection 1260 (plustek), sane-backends-1.0.14, on Linux 2.6.7-rc2 > and 2.4.25 with scanner.o(!) > Reason: the epson backend tries to talk to this scanner You mean "talking" directly using libusb while the scanner module is loaded or so? Although this gives a permission denied or so for me, maybe with ohci this behaves differently? People with problems could take a look if either scanner or hpsubscsi was / is loaded ... and unload it just in case ... Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene at rocklinux-consulting.de Sat Jun 26 00:52:52 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sat, 26 Jun 2004 01:52:52 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DCB61F.5070306@mykec.net> References: <40DC4DBF.7010004@mykec.net> <20040625.182333.719906209.rene@rocklinux-consulting.de> <40DCB61F.5070306@mykec.net> Message-ID: <20040626.015252.276767564.rene@rocklinux-consulting.de> Hi, On: Fri, 25 Jun 2004 18:32:47 -0500, Myke Carter wrote: > My currently installed RPM is "sane-backends-1.0.8-1.ximian.1". Yeah - forget this one - say goodbye to it ... > This, obviously, came to me from Ximian Gnome during some past > install/upgrade to my stock Red Hat system. Ximian tends to play by its > own rules, so I'm kinda hesitant to use just any more recent RPM to > upgrade what's been given me. There is not way to get your scanner working with this version. AFAIK the SANE/Backend pacakge is backward compaitible - just make sure your source packages replaces the RPM package files, so compile with the correct --sysconfdir and --prefix ... > > If you want to compile from source: > > > > http://www.rocklinux-consulting.de/oss/avision/compiling.html > > I am downloading this now but am curious as to what kinds of conflicts I > might encounter by mixing this with my current Ximian RPM installation. Do not forget that you need the wohle sane-backend package (sane.alioth.debian.org). The current version is 1.0.14. Optionally you can replace the avision.{c,h} files with the one from my homepage. You scanner will work with 1.0.14 - but in my svn (Subversion) repository you get some newer fixes, like enhanced sharpness, more robust light detection and enhanced 16bit / channel support ... > > You only need to compile / install sane-backend and other sane > > packages can be left untouched. > > Is it not enough to just replace my current /etc/sane.d/avision.conf > file with the same one from a newer version? No. This is just a configuration file - which is even optional and can be completely missing for my Avision backend. My backend uses reasonable defaults and detects any setting for tested scanners. The config files is only available to overwrite setting during debugging. All the real funtionally is present in 6122 (pure wc) of C code ... You can not avoid updating it. > Thanks for your quick response, Sometimes my inbox is not that crowded and people get quick replies ;-) Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene at rocklinux-consulting.de Sat Jun 26 08:08:46 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sat, 26 Jun 2004 09:08:46 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DCCC41.3050606@mykec.net> References: <40DCB61F.5070306@mykec.net> <20040626.015252.276767564.rene@rocklinux-consulting.de> <40DCCC41.3050606@mykec.net> Message-ID: <20040626.090846.653234575.rene@rocklinux-consulting.de> Hi, On: Fri, 25 Jun 2004 20:07:13 -0500, Myke Carter wrote: > OK. Are you suggesting that I uninstall the RPM? > > I guess it wouldn't matter if I did even if I couldn't replace it later > because it doesn't work anyway, huh? :) Yes - uninstalling is the cleaner solution since you can not accidently use an old file later. > > AFAIK the SANE/Backend pacakge is backward compaitible > > Backward compatible with what? With previous SANE/Backends versions. > > - just make sure your source packages replaces the RPM package files, > > I should just uninstall the package entirely then before compiling from > source. Yes - that is even cleaner. > > so compile with the correct --sysconfdir and --prefix ... > > All I know right now is that the config files are in /etc/sane.d/. > What's up with --prefix? Where the files will be placed in. I guess your current files are in /usr (/usr/lib/libsane* for example). The compile-from-source default is /usr/local. I suggest you specify --prefix=/usr for ./configure. Please see the sane-user mailing list archive for lenghty discussions and information. > > Do not forget that you need the whole sane-backend package > > (sane.alioth.debian.org). The current version is 1.0.14. > > I now have "sane-backends-1.0.14.tar.gz" downloaded to my hard drive. > > > Optionally you can replace the avision.{c,h} files with the > > one from my homepage. > > URLs? http://www.rocklinux-consulting.de/oss/avision/ http://svn.rocklinux-consulting.de/sane-avision/trunk/backend/ > > Your scanner will work with 1.0.14 - but in my svn > > (Subversion) repository you get some newer fixes, like enhanced > > sharpness, more robust light detection and enhanced 16bit / channel > > support ... > > One feature I get with the HP PrecisionScan software (for Windows) that > came bundled on CD-ROM with my 5300C is an automatic image rotation > adjustment that I don't believe exists in any Linux scanning software. > The MacOS 9 app that comes from the same CD-ROM doesn't even have it. > > That features makes it very easy to get perfectly vertical scans of > rectangular things such as sports cards, business cards, books, etc. - > without having to use something like The Gimp later to slightly rotate > each image (which invariably blurs them unnecessarily). If you rotate them in the driver you get the same blurs anyway - there is no way to get around this - the same algorithm needs to be applied on the data. Nevertheless the feature might be a nice to have in e.g. xsane ... Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From stan at saticed.me.uk Sat Jun 26 10:25:12 2004 From: stan at saticed.me.uk (stan at saticed.me.uk) Date: Sat, 26 Jun 2004 10:25:12 +0100 Subject: [sane-devel] fujitsu fi-4220 problem with 1.0.14 + patch Message-ID: <20040626092512.GA12998@nimitz.cehill.co.uk> Attached scanimage run with SANE_DEBUG_FUJITSU=20 set: fujitsu-13.log.gz: with sane-backends 1.0.13 fujitsu-14.log.gz: with sane-backends 1.0.14 fujitsu-14-2.log.gz: sane-backends 1.0.14 + small patch Seems to be working ok for the last couple of days with patch. The specificness of the error is impressive, thanks for all the hard work sane and fujitsu backend maintainers! :-) -------------- next part -------------- A non-text attachment was scrubbed... Name: fujitsu-14.log.gz Type: application/x-gunzip Size: 1747 bytes Desc: not available URL: -------------- next part -------------- --- sane-backends-1.0.14/backend/fujitsu.c.orig 2004-06-23 14:01:31.000000000 +0100 +++ sane-backends-1.0.14/backend/fujitsu.c 2004-06-23 14:17:44.000000000 +0100 @@ -4487,7 +4487,7 @@ if (!strncmp (product, "fi-4530C", 8) || !strncmp (product, "M3091", 5) || !strncmp (product, "M3092", 5) || - !strncmp (product, "fi-4120", 7) ) + s->model == MODEL_FI4x20) { /* These scanner don't support standard paper size specification * in bye 0x35 of the window descriptor block -------------- next part -------------- A non-text attachment was scrubbed... Name: fujitsu-13.log.gz Type: application/x-gunzip Size: 2510 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: fujitsu-14-2.log.gz Type: application/x-gunzip Size: 2166 bytes Desc: not available URL: From henning at meier-geinitz.de Sat Jun 26 10:40:38 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sat, 26 Jun 2004 11:40:38 +0200 Subject: [sane-devel] HP5370C still not working In-Reply-To: <20040625.232057.576037890.rene@rocklinux-consulting.de> References: <20040601215656.GA3524@ffii.org> <20040609134039.GA3769@ffii.org> <20040609151818.GO7920@meier-geinitz.de> <20040625.232057.576037890.rene@rocklinux-consulting.de> Message-ID: <20040626094038.GA22501@meier-geinitz.de> Hi, On Fri, Jun 25, 2004 at 11:20:57PM +0200, Rene Rebe wrote: > > An unrelated bug showed the same timeouts: > > - Epson Perfection 1260 (plustek), sane-backends-1.0.14, on Linux 2.6.7-rc2 > > and 2.4.25 with scanner.o(!) > > Reason: the epson backend tries to talk to this scanner > > You mean "talking" directly using libusb while the scanner module is > loaded or so? Although this gives a permission denied or so for me, > maybe with ohci this behaves differently? People with problems could > take a look if either scanner or hpsubscsi was / is loaded ... and > unload it just in case ... No, the problem in this case was that the epson backend thought that those scanners were supported by it. So the backend sent some commands to the scanner which the scanner didn't understand. --> timeout. That's fixed in CVS now. I haven't heard about any problem with scanner driver/ libusb interferences. However, there are problems with devices opened by libusb which are opened by other processed at the saame time. While the open fails, there still seems to be sent USB messages to the scanner and at least sometimes the scan process stops or images are corrupted. Bye, Henning From rene at rocklinux-consulting.de Sat Jun 26 13:55:13 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sat, 26 Jun 2004 14:55:13 +0200 (CEST) Subject: [sane-devel] Re: SANE/Avision the shifted image problem In-Reply-To: <1088252365.12036.5.camel@linux.site> References: <1088201812.7899.34.camel@linux.site> <20040626.002900.115919688.rene@rocklinux-consulting.de> <1088252365.12036.5.camel@linux.site> Message-ID: <20040626.145513.846957940.rene@rocklinux-consulting.de> Hi, On: Sat, 26 Jun 2004 14:19:25 +0200, Alberto Passalacqua wrote: > Thank you for your answer, > I installed the scanner on a clean SuSE 9.1 (Linux kernel 2.6.5-7.75) > installation in order to prevent problems due to my previous > experiments. > > - usbfs is mounted to /proc/bus/usb > - /proc/bus/usb/001 contains two files 001 and 005, which I made > accessible by all users (chmod 666). > - hpusbscsi and scanner are not loaded (I can't find them). > > If I start xsane both as root and as user, it still doesn't find the > scanner (No devices available message at startup). What is the output of: scanimage -L And versions of SANE are installed: scanimage -V ? Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene at rocklinux-consulting.de Sat Jun 26 18:03:21 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sat, 26 Jun 2004 19:03:21 +0200 (CEST) Subject: [sane-devel] Re: SANE/Avision the shifted image problem In-Reply-To: <1088266750.6477.24.camel@linux.site> References: <1088252365.12036.5.camel@linux.site> <20040626.145438.730575777.rene@rocklinux-consulting.de> <1088266750.6477.24.camel@linux.site> Message-ID: <20040626.190321.884032909.rene@rocklinux-consulting.de> Hi, On: Sat, 26 Jun 2004 18:19:11 +0200, Alberto Passalacqua wrote: > Hi Ren??, > > 1. scanimage -L gives: > > device `avision:/dev/sg0' is a Hewlett-Packard ScanJet 5370C flatbed > scanner Ouhm - ok. Then make sure hpusbscsi is not loaded. Maybe just "rm" it from your system. The module is rather unstable and I have not even tested if recent backends work with it one bit. You _want_ to access your scanner from user-space using libusb. Neither hpusbscsi nor scanner must be loaded in order to do so. > P.S. If I do this twice, the first time I obtain the previous message, > the second one I obtain the following one: Yep. The unstable hpusbscsi driver got stuck. Do not use it. > 2. scanimage -V gives: > > scanimage (sane-backends) 1.0.13; backend version 1.0.1 Hm - I wonder how 1.0.13 and 1.0.1 get mixed here. I guess you have two version installed in parallel, where the binary is from e.g. /usr/local/bin and the library from /usr/lib ?!? (Henning?) Make sure you get 1.0.13 for both. Best by uninstalling both version and just installed the new one (e.g. from source). I usually recommend to use ./configure --prefix=/usr in order to install them into the location whre your distribution already placed the files. Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From anoah at pfeiffer.edu Sat Jun 26 19:33:06 2004 From: anoah at pfeiffer.edu (m. allan noah) Date: Sat, 26 Jun 2004 14:33:06 -0400 (EDT) Subject: [sane-devel] fujitsu fi-4220 problem with 1.0.14 + patch In-Reply-To: <20040626092512.GA12998@nimitz.cehill.co.uk> References: <20040626092512.GA12998@nimitz.cehill.co.uk> Message-ID: ah, yes. my fault. with older fujitsu models you have to look at the letters in the device model name to figure out of it has certain features, hence the string compair. with the 4x20's there are no such options, so i should have just looked at the model code we assigned. i will apply your fix to cvs on monday. allan On Sat, 26 Jun 2004 stan at saticed.me.uk wrote: > > Attached scanimage run with SANE_DEBUG_FUJITSU=20 set: > fujitsu-13.log.gz: with sane-backends 1.0.13 > fujitsu-14.log.gz: with sane-backends 1.0.14 > fujitsu-14-2.log.gz: sane-backends 1.0.14 + small patch > > Seems to be working ok for the last couple of days with patch. > The specificness of the error is impressive, thanks for all > the hard work sane and fujitsu backend maintainers! :-) > > -- "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 rene at rocklinux-consulting.de Sun Jun 27 10:29:11 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 11:29:11 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DE3F1A.9090803@mykec.net> References: <40DCCC41.3050606@mykec.net> <20040626.090846.653234575.rene@rocklinux-consulting.de> <40DE3F1A.9090803@mykec.net> Message-ID: <20040627.112911.576045809.rene@rocklinux-consulting.de> Hi, On: Sat, 26 Jun 2004 22:29:30 -0500, Myke Carter wrote: > OK. > > First thing I tried was to uninstall "sane-backends-1.0.8-1.ximian.1". > > No go. There is some switch to "force" the uninstall ... - but just overwriting it is ok, too. > Try 2: > > ./configure --sysconfigdir=/etc --prefix=/usr > > This caused my Gnome panel applet to crash and made it so that I > couldn't log out without hitting my reset button. Running "xsane" > caused some kind of "relocation error" about a missing or bad > ".so.1" file. The error revealed something about "/etc/lib" > so before I rebooted I tried it once more. This was the right configuration. When did the gnome-pannel crahs? During make install? > Try 3: > > ./configure --sysconfdir=/etc --prefix=/usr/lib > > This eliminated the previous problem but gave me new graphical dialog > box errors "No devices found." or something like that. So I rebooted. This configuration is very messy. /usr/lib is not a prefix you want ... Your binaries will be in /usrc/lib/bin and the libs in /usr/lib/lib. This will not produces results you want - neither the binaries nor libraries are found by your usual ld and PATH configuration ... > After rebooting, I restored my Gnome panel tasklist and tried again. > > Now all I get is a dialogue box telling me "xsane: no devices available". > > Previously, with the old Ximian package that you said wouldn't work, > xsane was at least able to find my scanner. > > What now? You should install using your 2nd configuration. What does this give you: scanimage -L scanimage -V SANE_DEBUG_AVISION=7 xscanimage Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene at rocklinux-consulting.de Sun Jun 27 10:29:26 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 11:29:26 +0200 (CEST) Subject: [sane-devel] Re: SANE/Avision the shifted image problem In-Reply-To: <1088290427.15627.11.camel@linux.site> References: <1088266750.6477.24.camel@linux.site> <20040626.190321.884032909.rene@rocklinux-consulting.de> <1088290427.15627.11.camel@linux.site> Message-ID: <20040627.112926.596543533.rene@rocklinux-consulting.de> Hi, On: Sun, 27 Jun 2004 00:53:48 +0200, Alberto Passalacqua wrote: > Hi, > I removed the hpusbscsi and now "scanimage -L" properly tells that > "libusb" is used. It tells that also if I repeat the command a number of > times. > As root, I can scan a preview which is Ok: the image has low quality but > it is not shifted. Unfortunately, if I repeat the scan using for example > a 200dpi resolution, I obtain the shifted image again. > > You gave me the link to three files (avision.conf, avision.c, > avision.h), but I don't know where to put them (hehe...not really a > linux expert here :-)). Should I recompile sane using those sources? Yes - place them in the sane-backends-$ver/backend directory and rebuild and reinstall the backends package. Unfortunately when 1.0.14 does produce a shifted image - my SVN snapshot will, too. But you can already rebuild the package as an exercise and I provide you whit custom patches to try to work around the problem after lunch. > Thanks a lot for your great help. Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene at rocklinux-consulting.de Sun Jun 27 10:29:37 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 11:29:37 +0200 (CEST) Subject: [sane-devel] Re: Undefined symbol in latest avision backend. In-Reply-To: <1088287482.2851.7.camel@epo.dk> References: <1088287482.2851.7.camel@epo.dk> Message-ID: <20040627.112937.115926508.rene@rocklinux-consulting.de> On: Sun, 27 Jun 2004 00:04:42 +0200, "Erik P. Olsen" wrote: > Hi Rene, > > I downloaded today the avision backend from your svn repository, but > after installation I got from scanimage -L the following: > > scanimage: error while loading shared libraries: > /usr/lib/sane/libsane-avision.so.1: undefined symbol: sanei_thread_init > > In fact all sanei_thread_* are undefined symbols. > > Do you have any cure for it? This also happend to me when I only did a partial sane-backends rebuild. Have you built the wohle sane-backends package from scratch? Maybe you have an old libsanei.so.* lying around in parallel to the new one? Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rohum at gmx.de Sat Jun 26 17:06:11 2004 From: rohum at gmx.de (Ronald Humphries) Date: Sat, 26 Jun 2004 18:06:11 +0200 Subject: [sane-devel] check-usb-chip request for help Message-ID: <1088265971.13295.15.camel@linux1.rohu.de> Hello Cosmin. I?m still here and reading this. Is the windows source the complete driver or a part of it? Anyway, if you need help, I will do my best. So far for me everything is clear, as Henning explained. Normally I have some time in the evening for programming, not much, because I?m alone with my 4 year old kid. -- Ronald Humphries From henning at meier-geinitz.de Sun Jun 27 10:48:43 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Sun, 27 Jun 2004 11:48:43 +0200 Subject: [sane-devel] Re: SANE/Avision the shifted image problem In-Reply-To: <20040626.190321.884032909.rene@rocklinux-consulting.de> References: <1088252365.12036.5.camel@linux.site> <20040626.145438.730575777.rene@rocklinux-consulting.de> <1088266750.6477.24.camel@linux.site> <20040626.190321.884032909.rene@rocklinux-consulting.de> Message-ID: <20040627094842.GA5025@meier-geinitz.de> Gi, On Sat, Jun 26, 2004 at 07:03:21PM +0200, Rene Rebe wrote: > > 2. scanimage -V gives: > > > > scanimage (sane-backends) 1.0.13; backend version 1.0.1 > > Hm - I wonder how 1.0.13 and 1.0.1 get mixed here. I guess you have > two version installed in parallel, where the binary is from > e.g. /usr/local/bin and the library from /usr/lib ?!? (Henning?) 1.0.13 is the version of sane-backends that was used to build scanimage. 1.0.1 is the SANE version number of the dll backend. At least on Linux scanimage is linked in a way that ensures linking with the correct libs. Therefore maybe it's just a cut-n-paste problem? Bye, Henning From rene at rocklinux-consulting.de Sun Jun 27 11:27:38 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 12:27:38 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DE9D11.4040609@mykec.net> References: <40DE3F1A.9090803@mykec.net> <20040627.112911.576045809.rene@rocklinux-consulting.de> <40DE9D11.4040609@mykec.net> Message-ID: <20040627.122738.28805691.rene@rocklinux-consulting.de> Hi, What does: SANE_DEBUG_AVISION=7 scanimage -L yield? > [root at sillygoose mykec]# sane-find-scanner > > found SCSI scanner "HP ScanJet 5300C 4.00" at /dev/scanner > found SCSI scanner "HP ScanJet 5300C 4.00" at /dev/sg0 > found SCSI scanner "HP ScanJet 5300C 4.00" at /dev/sga > # Your SCSI scanner was detected. It may or may not be supported by > # SANE. Try scanimage -L and read the backend's manpage. Oh - you have the hpusbscsi module loaded. It is not very stable and therefore deprecated ... I had an report that it caused problems and locked up by another person just some days ago. Do you have libusb installed on your system? ls -l /usr/lib/libusb.so (rpm -q libusb or so - but I'm not used to rpm so --typos) Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rene at rocklinux-consulting.de Sun Jun 27 11:52:51 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 12:52:51 +0200 (CEST) Subject: [sane-devel] Re: HP 5300C Xsane Failure In-Reply-To: <40DEA54C.1030403@mykec.net> References: <40DE9D11.4040609@mykec.net> <20040627.122536.783397201.rene@rocklinux-consulting.de> <40DEA54C.1030403@mykec.net> Message-ID: <20040627.125251.971182931.rene@rocklinux-consulting.de> Hi, On: Sun, 27 Jun 2004 05:45:32 -0500, Myke Carter wrote: > [root at sillygoose sane]# SANE_DEBUG_AVISION=7 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). Hm - this is bad. This means for some reason the avision backend is not querried for devices present ... > [root at sillygoose sane]# rpm -q libusb > package libusb is not installed > > Oh - you have the hpusbscsi module loaded. It is not very stable and > > therefore deprecated ... I had an report that it caused problems and > > locked up by another person just some days ago. > > With what should I replace it? You should use libusb to access the scanner from userspace. Can you take a look if libusb (and maybe libusb-devel) is present on your distribution CD - or available on the homepage? If you installed it, you need to recompile sane-backend to take advantage of libusb. What was the distribution you use and what is the version of the kernel (uname -a)? If the kernel is older - and libusb not easily available we can also focus on getting the backend working with the hpusbscsi module ... Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From rob at bsdbox.homeunix.com Sun Jun 27 13:26:25 2004 From: rob at bsdbox.homeunix.com (Rob Mason) Date: Sun, 27 Jun 2004 13:26:25 +0100 Subject: [sane-devel] USB Scanning under FreeBSD Message-ID: <1088339184.33655.4.camel@dexter> After finally getting my BENQ USB scanner working under FreeBSD I thought I would share my solution for any FreeBSD users who would also struggling to get a workable scanning solution... http://bsdbox.homeunix.com/modules.php?op=modload&name=Sections&file=index&req=viewarticle&artid=19&page=1 Hope this is useful... Rgds __________________________________________________ Rob's BSDBox Rob Mason's Weblog & Opensource Resource Pages http://bsdbox.homeunix.com From rene at rocklinux-consulting.de Sun Jun 27 17:00:13 2004 From: rene at rocklinux-consulting.de (Rene Rebe) Date: Sun, 27 Jun 2004 18:00:13 +0200 (CEST) Subject: [sane-devel] Re: Undefined symbol in latest avision backend. In-Reply-To: <20040627.112937.115926508.rene@rocklinux-consulting.de> References: <1088287482.2851.7.camel@epo.dk> <20040627.112937.115926508.rene@rocklinux-consulting.de> Message-ID: <20040627.180013.336492724.rene@rocklinux-consulting.de> Hi, On: Sun, 27 Jun 2004 11:29:37 +0200 (CEST), Rene Rebe wrote: > This also happend to me when I only did a partial sane-backends > rebuild. Have you built the wohle sane-backends package from scratch? > Maybe you have an old libsanei.so.* lying around in parallel to the > new one? Ah now I see why this happens, you need this line in your backend/Makefile in oder to link against the sanei_thread library: libsane-avision.la: ../sanei/sanei_thread.lo Just put it near the other libsane-avision.la: lines already present there ... (if you want to rerun ./configure you either need to put it again into the file - or also place it in the backends/Makefile.in - since the Makefile is generated from the .in one ... Can you test if scanning works well if you put this into the /etc/sane.d/avision.conf (or the config file used in your configuration): disable-calibration and tell me if the scans with disabled calibration are correct, without shifting? Sincerely yours, Ren? Rebe - ROCK Linux stable release maintainer -- Ren? Rebe - Europe/Germany/Berlin rene at rocklinux.org rene at rocklinux-consulting.de http://www.rocklinux.org http://www.rocklinux-consulting.de From joseos at okstate.edu Sun Jun 27 21:54:24 2004 From: joseos at okstate.edu (Jose Sanchez) Date: Sun, 27 Jun 2004 15:54:24 -0500 Subject: [sane-devel] Which are the modules to load for a scsi scanner in the kernel 2.6 Message-ID: <40DF3400.7050208@okstate.edu> Hi, I recently migrated from SUSE 9.0 Kernel 2.4.20 to SUSE 9.1 Kernel 2.6.4. I want to install my scsi scanner but I don't find the modules that I used to load before (onscsi and ppscsi). Could someone tell me which modules I have to load now? thanks Jose From jochen at penguin-breeder.org Sun Jun 27 22:17:06 2004 From: jochen at penguin-breeder.org (Jochen Eisinger) Date: Sun, 27 Jun 2004 23:17:06 +0200 Subject: [sane-devel] Which are the modules to load for a scsi scanner in the kernel 2.6 In-Reply-To: <40DF3400.7050208@okstate.edu> References: <40DF3400.7050208@okstate.edu> Message-ID: <40DF3952.3030000@penguin-breeder.org> Hi, i have ported the ppscsi driver suite to 2.6 and try to keep it working. You could submit a request to SuSE to include it in future kernels, if enough people ask for it, they will probably include it. The patch is available from my homepage: http://penguin-breeder.org/kernel/#ppscsi kind regards -- jochen From christoph.knauer at web.de Mon Jun 28 07:51:46 2004 From: christoph.knauer at web.de (Christoph Knauer) Date: Mon, 28 Jun 2004 08:51:46 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) Message-ID: <200406280851.54167.christoph.knauer@web.de> Hi, I've tried to compile and install xsane 0.94. When I start xsane from console, nothing happens, only the message "Speicherzugriffsfehler" (Memory access error) appears. Next I've downloaded a rpm from packman, and there the eula pops up, but with the click on "accept" the message above appears again. With xsane 0.93 all works fine. My system: SuSE 9.1 prof. Kernel 2.6.5-7.75-default KDE 3.2.3 Thanx, Christoph -- GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: signature URL: From picos132004 at yahoo.co.uk Mon Jun 28 15:08:09 2004 From: picos132004 at yahoo.co.uk (=?iso-8859-1?q?Ioan-Cosmin=20Pop?=) Date: Mon, 28 Jun 2004 15:08:09 +0100 (BST) Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <1088265971.13295.15.camel@linux1.rohu.de> Message-ID: <20040628140809.27363.qmail@web25108.mail.ukl.yahoo.com> Hi Ronald! Thank you for answering! --- Ronald Humphries wrote: > Hello Cosmin. > > I??m still here and reading this. Is the windows > source the complete > driver or a part of it? It's the complete driver. Anything needed to acces the scanner is there. > > Anyway, if you need help, I will do my best. So far > for me everything is > clear, as Henning explained. Yes, I need help, somebody to talk to. I thought I can do it all alone, but I can't. I would really like you to have also the windows sources, so we have a common ground. What do you think? > > Normally I have some time in the evening for > programming, not much, > because I??m alone with my 4 year old kid. Send him all the best from me :) > -- > Ronald Humphries > Cosmin ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com From henning at meier-geinitz.de Mon Jun 28 17:33:37 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 28 Jun 2004 18:33:37 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <200406280851.54167.christoph.knauer@web.de> References: <200406280851.54167.christoph.knauer@web.de> Message-ID: <20040628163336.GA12239@meier-geinitz.de> Hi, On Mon, Jun 28, 2004 at 08:51:46AM +0200, Christoph Knauer wrote: > I've tried to compile and install xsane 0.94. When I start xsane from console, > nothing happens, only the message "Speicherzugriffsfehler" (Memory access > error) appears. > Next I've downloaded a rpm from packman, and there the eula pops up, but with > the click on "accept" the message above appears again. http://www.xsane.org/ First news item. If that's not your problem, tell us more details (which scanner, which backend?). Bye, Henning From henning at meier-geinitz.de Mon Jun 28 18:06:45 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 28 Jun 2004 19:06:45 +0200 Subject: [sane-devel] Experience with brother backend? Message-ID: <20040628170645.GG12273@meier-geinitz.de> Hi, Has anyone already tested the brother backend? Link: http://solutions.brother.com/Library/sol/printer/linux/sane_drivers.html It seems to be based on an old SANE version without libusb support so it may be difficult to use on 2.6 :-/ It claims to supporte these models: DCP Models: DCP-1000 DCP-1400 DCP-8020 DCP-8025D FAX Models: FAX1815C FAX1820C FAX1920CN FAX-2850 FAX-2900 FAX-3800 FAX-4100 FAX-4750e FAX-5750e MFC Models: MFC3220C MFC3320CN MFC3420C MFC3820CN MFC-4800 MFC-6800 MFC-8220 MFC-8420 MFC-8500 MFC-8820D MFC-9030 MFC-9070 MFC-9160 MFC-9180 MFC-9660 MFC-9700 MFC-9760 MFC-9800 MFC-9860 MFC-9880 Any experiences with that backend? I'd like to add these scanners to our lists for external backends but first I want to know if the driver works at all. Bye, Henning From anoah at pfeiffer.edu Mon Jun 28 18:27:20 2004 From: anoah at pfeiffer.edu (m. allan noah) Date: Mon, 28 Jun 2004 13:27:20 -0400 (EDT) Subject: [sane-devel] Experience with brother backend? In-Reply-To: <20040628170645.GG12273@meier-geinitz.de> References: <20040628170645.GG12273@meier-geinitz.de> Message-ID: an objdump on the .so, plus some comments in the faq make me think it uses libusb. i have not used the code, though. i have a brother printer, but no mfc. i have a bigger question, though. is their packaging of gpl'd and lgpl'd and proprietary code together ok? allan On Mon, 28 Jun 2004, Henning Meier-Geinitz wrote: > Hi, > > Has anyone already tested the brother backend? Link: > http://solutions.brother.com/Library/sol/printer/linux/sane_drivers.html > > It seems to be based on an old SANE version without libusb support so > it may be difficult to use on 2.6 :-/ > > It claims to supporte these models: > DCP Models: > DCP-1000 DCP-1400 DCP-8020 DCP-8025D > FAX Models: > FAX1815C FAX1820C FAX1920CN FAX-2850 FAX-2900 > FAX-3800 FAX-4100 FAX-4750e FAX-5750e > MFC Models: > MFC3220C MFC3320CN MFC3420C MFC3820CN MFC-4800 > MFC-6800 MFC-8220 MFC-8420 MFC-8500 MFC-8820D > MFC-9030 MFC-9070 MFC-9160 MFC-9180 MFC-9660 > MFC-9700 MFC-9760 MFC-9800 MFC-9860 MFC-9880 > > Any experiences with that backend? > > I'd like to add these scanners to our lists for external backends but > first I want to know if the driver works at all. > > Bye, > Henning > > -- "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 Mon Jun 28 18:46:45 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 28 Jun 2004 19:46:45 +0200 Subject: [sane-devel] Experience with brother backend? In-Reply-To: References: <20040628170645.GG12273@meier-geinitz.de> Message-ID: <20040628174645.GK12273@meier-geinitz.de> Hi, On Mon, Jun 28, 2004 at 01:27:20PM -0400, m. allan noah wrote: > an objdump on the .so, plus some comments in the faq make me think it uses > libusb. Maybe it's used directly (without the use of sanei_usb). I haven't looked into the details. > i have not used the code, though. i have a brother printer, but no mfc. > > i have a bigger question, though. is their packaging of gpl'd and lgpl'd > and proprietary code together ok? I'm not really sure. Concerning the SANE license (e.g. sanei_usb.c) it *could* be ok, even if using parts of the sane distribution with proprietary backends wasn't the intention of the SANE exception. I haven't checked the implications of using their license in combination with GPL/SANE and LGPL, however. I'd never put such part of software on any of my website because of this license nightmare :-/ Bye, Henning From henning at meier-geinitz.de Mon Jun 28 19:45:38 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Mon, 28 Jun 2004 20:45:38 +0200 Subject: [sane-devel] a new function for sane-desc! In-Reply-To: <1088078757.3362.61.camel@localhost> References: <1088078757.3362.61.camel@localhost> Message-ID: <20040628184538.GL12273@meier-geinitz.de> Hi, On Thu, Jun 24, 2004 at 02:05:57PM +0200, jose wrote: > Hi, finally I have made a new function in sane-desc to get an xml > output. > > I think that only have to send the patch, if there is any problem please > email me, this is the first time that I make something similar.. I've just comitted your patch to CVS. Thanks again! Bye, Henning From christoph.knauer at web.de Mon Jun 28 21:16:07 2004 From: christoph.knauer at web.de (Christoph Knauer) Date: Mon, 28 Jun 2004 22:16:07 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <1088442328.2125.8.camel@Babylon7> References: <200406280851.54167.christoph.knauer@web.de> <1088442328.2125.8.camel@Babylon7> Message-ID: <200406282216.07084.christoph.knauer@web.de> Hi, aber nur mit dem Binary-Package vom Packman. Zumindest scheint es wieder zu laufen ... Danke Am Montag, 28. Juni 2004 19:05 schrieb Oliver Rauch: > Hallo Christoph, > > ich vermute, Du musst ~/.sane/xsane/xsane.rc loeschen oder umbenennen. > > Gruss > Oliver -- GPG-Fingerprint: 171A 6F66 52E5 A6CE D664 2427 832F E711 7442 8261 ------------------------------------------------------------------ Bitte beachtet auch meinen Profiseller-Shop unter http://www.profiseller.de/shop/christoph-knauer From pmsguevarra at yahoo.com Tue Jun 29 02:54:29 2004 From: pmsguevarra at yahoo.com (Peter Mark Guevarra) Date: Mon, 28 Jun 2004 18:54:29 -0700 (PDT) Subject: [sane-devel] different scan outputs for different Linux distributions Message-ID: <20040629015429.77026.qmail@web41015.mail.yahoo.com> Hello, Sorry for this late response..I have tested scanimage with Red Hat 8 and Red Hat 9. The output in Red Hat 9 is darker compared with that of Red Hat 8 but exactly the same settings were used.. You have said in your previous reply that xsane should not modify gamma settings automatically..I`m quite confused with the use of the options..How may I be able to do this? Thanks a lot, PMG Hi, On Mon, Jun 21, 2004 at 02:57:17AM -0700, Peter Mark Guevarra wrote: > Has anyone encountered this problem wherein the same frontend, xsane > or xscanimage for instance, has different outputs for RedHat, and > SuSE or Mandrake? Same settings were used in the frontend but > different outputs resulted for different distributions, one is > darker/brighter than the other. I haven't heard about such a behaviour. Can you reproduce it with scanimage? Maybe the scanner wasn't warmed up completely in one of the tests? > Also, in the case of using only one Linux Distribution, RedHat for > example, is it expected to have the same output for the different > SANE frontends given the default settings for each frontend? Yes, if you don't use any of the color enhancement settings. E.g. make sure that xsane doesn't modify your gamma settings automatically. Bye, Henning --------------------------------- Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! -------------- next part -------------- An HTML attachment was scrubbed... URL: From C.W.J.Lemmens at ewi.tudelft.nl Tue Jun 29 09:52:16 2004 From: C.W.J.Lemmens at ewi.tudelft.nl (Kees Lemmens) Date: Tue, 29 Jun 2004 10:52:16 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <20040628163336.GA12239@meier-geinitz.de> References: <200406280851.54167.christoph.knauer@web.de> <20040628163336.GA12239@meier-geinitz.de> Message-ID: <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> Hi, I have the same problem with xsane 0.94, but although it indeed works for most users, with some other users the problem doesn't disappear by just removing the xsane.rc ! For those users where it still crashed we could fix the problem by changing the version number from 0.91 to 0.94 in xsane.rc and remove most of the remaining lines except the first 10 or so. However, as soon as you would rename the xsane.rc the seg faults occur again, so we really think there must be more wrong than only this minor xsane.rc problem. Attached a coredump analysis using gdb. Seems to be gdk related. Maybe something todo with their personalized Gdk/Gtk settings ? Bye, Kees Lemmens. TU Delft, Netherlands. On Monday 28 June 2004 18:33, Henning Meier-Geinitz wrote: > Hi, > > On Mon, Jun 28, 2004 at 08:51:46AM +0200, Christoph Knauer wrote: > > I've tried to compile and install xsane 0.94. When I start xsane > > from console, nothing happens, only the message > > "Speicherzugriffsfehler" (Memory access error) appears. > > Next I've downloaded a rpm from packman, and there the eula pops > > up, but with the click on "accept" the message above appears again. > > http://www.xsane.org/ > First news item. > > If that's not your problem, tell us more details (which scanner, > which backend?). > > Bye, > Henning testsys:/tmp 50 % gdb /opt/xsane/bin/xsane core GNU gdb 5.3 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-slackware-linux"... Core was generated by `/opt/xsane/bin/xsane -n'. Program terminated with signal 11, Segmentation fault. Reading symbols from /opt/sane/lib/libsane.so...done. Loaded symbols for /opt/sane/lib/libsane.so Reading symbols from /usr/lib/libusb-0.1.so.4...done. Loaded symbols for /usr/lib/libusb-0.1.so.4 Reading symbols from /lib/libnsl.so.1...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libm.so.6...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /usr/lib/libjpeg.so.62...done. Loaded symbols for /usr/lib/libjpeg.so.62 Reading symbols from /usr/lib/libieee1284.so.3...done. Loaded symbols for /usr/lib/libieee1284.so.3 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /usr/lib/libgimpui-1.2.so.0...done. Loaded symbols for /usr/lib/libgimpui-1.2.so.0 Reading symbols from /usr/lib/libgimp-1.2.so.0...done. Loaded symbols for /usr/lib/libgimp-1.2.so.0 Reading symbols from /usr/lib/libgtk-1.2.so.0...done. Loaded symbols for /usr/lib/libgtk-1.2.so.0 Reading symbols from /usr/lib/libgdk-1.2.so.0...done. Loaded symbols for /usr/lib/libgdk-1.2.so.0 Reading symbols from /usr/lib/libgmodule-1.2.so.0...done. Loaded symbols for /usr/lib/libgmodule-1.2.so.0 Reading symbols from /usr/lib/libglib-1.2.so.0...done. Loaded symbols for /usr/lib/libglib-1.2.so.0 Reading symbols from /usr/X11R6/lib/libXext.so.6...done. Loaded symbols for /usr/X11R6/lib/libXext.so.6 Reading symbols from /usr/X11R6/lib/libX11.so.6...done. Loaded symbols for /usr/X11R6/lib/libX11.so.6 Reading symbols from /usr/lib/libpng.so.3...done. Loaded symbols for /usr/lib/libpng.so.3 Reading symbols from /usr/lib/libtiff.so.3...done. Loaded symbols for /usr/lib/libtiff.so.3 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ xlcDef.so.2...done. Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 Reading symbols from /lib/libnss_files.so.2...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ ximcp.so.2...done. Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2 Reading symbols from /lib/libnss_compat.so.2...done. Loaded symbols for /lib/libnss_compat.so.2 Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done. Loaded symbols for /usr/X11R6/lib/libXcursor.so.1 Reading symbols from /usr/X11R6/lib/libXrender.so.1...done. Loaded symbols for /usr/X11R6/lib/libXrender.so.1 #0 0x40218451 in gdk_gc_new_with_values () from /usr/lib/ libgdk-1.2.so.0 From mlists at protocol.gr Tue Jun 29 13:57:40 2004 From: mlists at protocol.gr (Panos Katergiathis) Date: Tue, 29 Jun 2004 15:57:40 +0300 Subject: [sane-devel] Problem with Fedora Core 2 Message-ID: <40E16744.2010307@protocol.gr> Hello I have configured my scanner with sane running in Fedora Core 2. Whenever i try to run xsane or 'scanimage -L' the system does not find any scanner attached... until i unplug the usb cable, wait a couple of seconds and plug it back again. The whole time, the Fedora's hardware browser DOES detect the scanner attached properly. The symptom re-appears after rebooting. Each time, after replugging the cable everything works perfectly. Any help will be appreciated. Panos From twaugh at redhat.com Tue Jun 29 14:44:15 2004 From: twaugh at redhat.com (Tim Waugh) Date: Tue, 29 Jun 2004 14:44:15 +0100 Subject: [sane-devel] Problem with Fedora Core 2 In-Reply-To: <40E16744.2010307@protocol.gr> References: <40E16744.2010307@protocol.gr> Message-ID: <20040629134415.GZ1594@redhat.com> On Tue, Jun 29, 2004 at 03:57:40PM +0300, Panos Katergiathis wrote: > Hello > > I have configured my scanner with sane running in Fedora Core 2. > Whenever i try to run xsane or 'scanimage -L' the system does not find > any scanner attached... until i unplug the usb cable, wait a couple of > seconds and plug it back again. The whole time, the Fedora's hardware > browser DOES detect the scanner attached properly. The symptom > re-appears after rebooting. Each time, after replugging the cable > everything works perfectly. > > Any help will be appreciated. This has been discussed a-plenty on the fedora-list, for instance here: http://www.redhat.com/archives/fedora-list/2004-June/msg00279.html and also in bugzilla: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=121511 Short story: this needs a fix in the hotplug script of some sort, but it isn't yet clear what is needed. Tim. */ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From C.W.J.Lemmens at ewi.tudelft.nl Tue Jun 29 16:09:10 2004 From: C.W.J.Lemmens at ewi.tudelft.nl (Kees Lemmens) Date: Tue, 29 Jun 2004 17:09:10 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> References: <200406280851.54167.christoph.knauer@web.de> <20040628163336.GA12239@meier-geinitz.de> <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> Message-ID: <200406291709.10943.C.W.J.Lemmens@ewi.tudelft.nl> Hi, The seg fault problem seems to be caused by an old ~/.gtkrc file with illegal content: as soon as I remove this file all problems are gone !! Don't know which line is responsible, but just decided to discard this file completely to avoid any xsane seg faults as it doesn't seem to be that important for KDE users ;) -- Bye, Kees Lemmens. On Tuesday 29 June 2004 10:52, Kees Lemmens wrote: > Hi, > > I have the same problem with xsane 0.94, but although it indeed > works for most users, with some other users the problem doesn't > disappear by just removing the xsane.rc ! > > For those users where it still crashed we could fix the problem by > changing the version number from 0.91 to 0.94 in xsane.rc and remove > most of the remaining lines except the first 10 or so. > > However, as soon as you would rename the xsane.rc the seg faults > occur again, so we really think there must be more wrong than only > this minor xsane.rc problem. > > Attached a coredump analysis using gdb. Seems to be gdk related. > Maybe something todo with their personalized Gdk/Gtk settings ? > > Bye, > Kees Lemmens. > TU Delft, Netherlands. > > On Monday 28 June 2004 18:33, Henning Meier-Geinitz wrote: > > Hi, > > > > On Mon, Jun 28, 2004 at 08:51:46AM +0200, Christoph Knauer wrote: > > > I've tried to compile and install xsane 0.94. When I start xsane > > > from console, nothing happens, only the message > > > "Speicherzugriffsfehler" (Memory access error) appears. > > > Next I've downloaded a rpm from packman, and there the eula pops > > > up, but with the click on "accept" the message above appears > > > again. > > > > http://www.xsane.org/ > > First news item. > > > > If that's not your problem, tell us more details (which scanner, > > which backend?). > > > > Bye, > > Henning > > testsys:/tmp 50 % gdb /opt/xsane/bin/xsane core > GNU gdb 5.3 > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-slackware-linux"... > Core was generated by `/opt/xsane/bin/xsane -n'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /opt/sane/lib/libsane.so...done. > Loaded symbols for /opt/sane/lib/libsane.so > Reading symbols from /usr/lib/libusb-0.1.so.4...done. > Loaded symbols for /usr/lib/libusb-0.1.so.4 > Reading symbols from /lib/libnsl.so.1...done. > Loaded symbols for /lib/libnsl.so.1 > Reading symbols from /lib/libm.so.6...done. > Loaded symbols for /lib/libm.so.6 > Reading symbols from /usr/lib/libjpeg.so.62...done. > Loaded symbols for /usr/lib/libjpeg.so.62 > Reading symbols from /usr/lib/libieee1284.so.3...done. > Loaded symbols for /usr/lib/libieee1284.so.3 > Reading symbols from /lib/libdl.so.2...done. > Loaded symbols for /lib/libdl.so.2 > Reading symbols from /usr/lib/libgimpui-1.2.so.0...done. > Loaded symbols for /usr/lib/libgimpui-1.2.so.0 > Reading symbols from /usr/lib/libgimp-1.2.so.0...done. > Loaded symbols for /usr/lib/libgimp-1.2.so.0 > Reading symbols from /usr/lib/libgtk-1.2.so.0...done. > Loaded symbols for /usr/lib/libgtk-1.2.so.0 > Reading symbols from /usr/lib/libgdk-1.2.so.0...done. > Loaded symbols for /usr/lib/libgdk-1.2.so.0 > Reading symbols from /usr/lib/libgmodule-1.2.so.0...done. > Loaded symbols for /usr/lib/libgmodule-1.2.so.0 > Reading symbols from /usr/lib/libglib-1.2.so.0...done. > Loaded symbols for /usr/lib/libglib-1.2.so.0 > Reading symbols from /usr/X11R6/lib/libXext.so.6...done. > Loaded symbols for /usr/X11R6/lib/libXext.so.6 > Reading symbols from /usr/X11R6/lib/libX11.so.6...done. > Loaded symbols for /usr/X11R6/lib/libX11.so.6 > Reading symbols from /usr/lib/libpng.so.3...done. > Loaded symbols for /usr/lib/libpng.so.3 > Reading symbols from /usr/lib/libtiff.so.3...done. > Loaded symbols for /usr/lib/libtiff.so.3 > Reading symbols from /usr/lib/libz.so.1...done. > Loaded symbols for /usr/lib/libz.so.1 > Reading symbols from /lib/libc.so.6...done. > Loaded symbols for /lib/libc.so.6 > Reading symbols from /lib/ld-linux.so.2...done. > Loaded symbols for /lib/ld-linux.so.2 > Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ > xlcDef.so.2...done. > Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 > Reading symbols from /lib/libnss_files.so.2...done. > Loaded symbols for /lib/libnss_files.so.2 > Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ > ximcp.so.2...done. > Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2 > Reading symbols from /lib/libnss_compat.so.2...done. > Loaded symbols for /lib/libnss_compat.so.2 > Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done. > Loaded symbols for /usr/X11R6/lib/libXcursor.so.1 > Reading symbols from /usr/X11R6/lib/libXrender.so.1...done. > Loaded symbols for /usr/X11R6/lib/libXrender.so.1 > #0 0x40218451 in gdk_gc_new_with_values () from /usr/lib/ > libgdk-1.2.so.0 From Oliver.Rauch at Rauch-Domain.DE Tue Jun 29 17:00:12 2004 From: Oliver.Rauch at Rauch-Domain.DE (Oliver Rauch) Date: 29 Jun 2004 18:00:12 +0200 Subject: [sane-devel] Xsane 0.94 Memory access error (Speicherzugriffsfehler) In-Reply-To: <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> References: <200406280851.54167.christoph.knauer@web.de> <20040628163336.GA12239@meier-geinitz.de> <200406291052.16302.C.W.J.Lemmens@ewi.tudelft.nl> Message-ID: <1088524811.2123.2.camel@Babylon7> Hello Kees, I do not understand how you can change the version from 0.91 to 0.94 in xsane.rc when you removed the file xsane.rc, in this case the file is deleted so you can not change anything in the file! When the problem still occurs then please do: rm ~/.sane/xsane/xsane.rc export XSANE_DEBUG=12 xsane 2>debug.txt gzip debug.txt and send debug.txt.gz to me (directly, not to the list). Oliver Am Die, 2004-06-29 um 10.52 schrieb Kees Lemmens: > Hi, > > I have the same problem with xsane 0.94, but although it indeed works > for most users, with some other users the problem doesn't disappear by > just removing the xsane.rc ! > > For those users where it still crashed we could fix the problem by > changing the version number from 0.91 to 0.94 in xsane.rc and remove > most of the remaining lines except the first 10 or so. > > However, as soon as you would rename the xsane.rc the seg faults occur > again, so we really think there must be more wrong than only this minor > xsane.rc problem. > > Attached a coredump analysis using gdb. Seems to be gdk related. Maybe > something todo with their personalized Gdk/Gtk settings ? > > Bye, > Kees Lemmens. > TU Delft, Netherlands. > > On Monday 28 June 2004 18:33, Henning Meier-Geinitz wrote: > > Hi, > > > > On Mon, Jun 28, 2004 at 08:51:46AM +0200, Christoph Knauer wrote: > > > I've tried to compile and install xsane 0.94. When I start xsane > > > from console, nothing happens, only the message > > > "Speicherzugriffsfehler" (Memory access error) appears. > > > Next I've downloaded a rpm from packman, and there the eula pops > > > up, but with the click on "accept" the message above appears again. > > > > http://www.xsane.org/ > > First news item. > > > > If that's not your problem, tell us more details (which scanner, > > which backend?). > > > > Bye, > > Henning > > testsys:/tmp 50 % gdb /opt/xsane/bin/xsane core > GNU gdb 5.3 > Copyright 2002 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-slackware-linux"... > Core was generated by `/opt/xsane/bin/xsane -n'. > Program terminated with signal 11, Segmentation fault. > Reading symbols from /opt/sane/lib/libsane.so...done. > Loaded symbols for /opt/sane/lib/libsane.so > Reading symbols from /usr/lib/libusb-0.1.so.4...done. > Loaded symbols for /usr/lib/libusb-0.1.so.4 > Reading symbols from /lib/libnsl.so.1...done. > Loaded symbols for /lib/libnsl.so.1 > Reading symbols from /lib/libm.so.6...done. > Loaded symbols for /lib/libm.so.6 > Reading symbols from /usr/lib/libjpeg.so.62...done. > Loaded symbols for /usr/lib/libjpeg.so.62 > Reading symbols from /usr/lib/libieee1284.so.3...done. > Loaded symbols for /usr/lib/libieee1284.so.3 > Reading symbols from /lib/libdl.so.2...done. > Loaded symbols for /lib/libdl.so.2 > Reading symbols from /usr/lib/libgimpui-1.2.so.0...done. > Loaded symbols for /usr/lib/libgimpui-1.2.so.0 > Reading symbols from /usr/lib/libgimp-1.2.so.0...done. > Loaded symbols for /usr/lib/libgimp-1.2.so.0 > Reading symbols from /usr/lib/libgtk-1.2.so.0...done. > Loaded symbols for /usr/lib/libgtk-1.2.so.0 > Reading symbols from /usr/lib/libgdk-1.2.so.0...done. > Loaded symbols for /usr/lib/libgdk-1.2.so.0 > Reading symbols from /usr/lib/libgmodule-1.2.so.0...done. > Loaded symbols for /usr/lib/libgmodule-1.2.so.0 > Reading symbols from /usr/lib/libglib-1.2.so.0...done. > Loaded symbols for /usr/lib/libglib-1.2.so.0 > Reading symbols from /usr/X11R6/lib/libXext.so.6...done. > Loaded symbols for /usr/X11R6/lib/libXext.so.6 > Reading symbols from /usr/X11R6/lib/libX11.so.6...done. > Loaded symbols for /usr/X11R6/lib/libX11.so.6 > Reading symbols from /usr/lib/libpng.so.3...done. > Loaded symbols for /usr/lib/libpng.so.3 > Reading symbols from /usr/lib/libtiff.so.3...done. > Loaded symbols for /usr/lib/libtiff.so.3 > Reading symbols from /usr/lib/libz.so.1...done. > Loaded symbols for /usr/lib/libz.so.1 > Reading symbols from /lib/libc.so.6...done. > Loaded symbols for /lib/libc.so.6 > Reading symbols from /lib/ld-linux.so.2...done. > Loaded symbols for /lib/ld-linux.so.2 > Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ > xlcDef.so.2...done. > Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/xlcDef.so.2 > Reading symbols from /lib/libnss_files.so.2...done. > Loaded symbols for /lib/libnss_files.so.2 > Reading symbols from /usr/X11R6/lib/X11/locale/lib/common/ > ximcp.so.2...done. > Loaded symbols for /usr/X11R6/lib/X11/locale/lib/common/ximcp.so.2 > Reading symbols from /lib/libnss_compat.so.2...done. > Loaded symbols for /lib/libnss_compat.so.2 > Reading symbols from /usr/X11R6/lib/libXcursor.so.1...done. > Loaded symbols for /usr/X11R6/lib/libXcursor.so.1 > Reading symbols from /usr/X11R6/lib/libXrender.so.1...done. > Loaded symbols for /usr/X11R6/lib/libXrender.so.1 > #0 0x40218451 in gdk_gc_new_with_values () from /usr/lib/ > libgdk-1.2.so.0 > From henning at meier-geinitz.de Tue Jun 29 18:15:33 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Tue, 29 Jun 2004 19:15:33 +0200 Subject: [sane-devel] different scan outputs for different Linux distributions In-Reply-To: <20040629015429.77026.qmail@web41015.mail.yahoo.com> References: <20040629015429.77026.qmail@web41015.mail.yahoo.com> Message-ID: <20040629171533.GB16361@meier-geinitz.de> Hi, On Mon, Jun 28, 2004 at 06:54:29PM -0700, Peter Mark Guevarra wrote: > Sorry for this late response..I have tested scanimage with Red Hat 8 and Red Hat 9. > The output in Red Hat 9 is darker compared with that of Red Hat 8 but exactly the same settings were used.. Even if you use scanimage instead of xsane? scanimage doesn't do any automatic color correction. > You have said in your previous reply that xsane should not > modify gamma settings automatically..I`m quite confused with the > use of the options..How may I be able to do this? In Preferences-Setup-Enhancement, disable "autoenhance gamma" and "Autocorrect colors". Bye, Henning From eric.tanguy at physique.univ-nantes.fr Tue Jun 29 21:45:48 2004 From: eric.tanguy at physique.univ-nantes.fr (Eric Tanguy) Date: Tue, 29 Jun 2004 22:45:48 +0200 Subject: [sane-devel] Epson Perfection 1670 and high resolution Message-ID: <1088541948.4195.5.camel@localhost.localdomain> I use this scanner on fedora core 2 with sane-backends-1.0.13-7 and xsane-0.92-10. All works fine except when i try to use resolution greater than 600 (900 or 1200). In these cases, the result is malformed and the colours are wrong. What's the problem and how to solve it ? Thanxes. Eric -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Ceci est une partie de message num?riquement sign?e. URL: From Oliver.Schwartz at gmx.de Tue Jun 29 22:31:44 2004 From: Oliver.Schwartz at gmx.de (Oliver Schwartz) Date: Tue, 29 Jun 2004 23:31:44 +0200 Subject: [sane-devel] Epson Perfection 1670 and high resolution In-Reply-To: <1088541948.4195.5.camel@localhost.localdomain> References: <1088541948.4195.5.camel@localhost.localdomain> Message-ID: <200406292331.50924.Oliver.Schwartz@gmx.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 29 June 2004 22.45, Eric Tanguy wrote: > I use this scanner on fedora core 2 with sane-backends-1.0.13-7 and > xsane-0.92-10. All works fine except when i try to use resolution > greater than 600 (900 or 1200). In these cases, the result is > malformed and the colours are wrong. > What's the problem and how to solve it ? These resolutions are broken on the 1670. You need to upgrade to sane-backends-1.0.14, it offers 800 dpi and 1600 dpi instead which are supposed to work fine. /Oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQFA4d/B/V6sbrmfIuMRAlk4AJsFmWvSAP69ZIcNxsnAu+KcUx82pwCffrMp b5wo5jFY64bZmBR7K7WTtHw= =a+nr -----END PGP SIGNATURE----- From moseley at hank.org Tue Jun 29 22:45:51 2004 From: moseley at hank.org (Bill Moseley) Date: Tue, 29 Jun 2004 14:45:51 -0700 Subject: [sane-devel] VIA chipset and HP4100C USB scanner Message-ID: <20040629214551.GB19339@hank.org> I've got a MSI KT266-Pro2 motherboard with a VIA chipset. I'm wondering if my hardware is the problem or if there's other things to check. I'm able to sync a USB Palm device with Jpilot without any problems, but my scanner generates errors. I have another machine (an older Toshiba laptop) which first reported errors (way below), but I'm now able to scan with the HP 4100C scanner. One difference is that on my desktop it seems that hotplug is loading videodev module, but that doesn't happen on my laptop. I'm not sure why. So basically, my qustion is if my hardware is just broken and will never work, or if there's something else I can try to resolve scanning problems. I have hope since Jpilot usb sync works. Here's some details: Both my Desktop (the KT266-Pro2 machine) and my laptop are running Debian Sid. The Desktop has 2.6.6 and the laptop 2.6.5. Otherwise, same software (below for sane and libusb versions). When I plug in my scanner into the KT266-PRO2 I see: Jun 28 21:30:25 bumby kernel: usb 1-2: new full speed USB device using address 2 Then I run sane-find-scanner and it reports: found USB scanner (vendor=0x03f0, product=0x0101) at libusb:001:002 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. and in syslog I see: Jun 28 21:30:41 bumby kernel: usb 1-2: control timeout on ep0in Jun 28 21:30:41 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Jun 28 21:30:42 bumby kernel: usb 1-2: control timeout on ep0in Jun 28 21:30:42 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 Sometimes this works: moseley at bumby:~$ scanimage -L device `hp:libusb:001:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner and entries in syslog from scanimage: Jun 28 21:34:11 bumby kernel: Linux video capture interface: v1.00 Jun 28 21:34:18 bumby kernel: usb 1-2: control timeout on ep0out Not sure why Linux video capture was loaded. I don't have any video capture cards. lsmod shows "videodev". Is hotplug confused about what module should be loaded? Sometimes syslog reports this again: Jun 28 21:37:34 bumby kernel: usb 1-2: control timeout on ep0out But sometimes scanimage -L reports that a scanner can't be found, and sometimes scanimage -L hangs with the process in "D" status which can't be kill -9'ed (requires a reboot, so it seems). I've also had scanimage -L do this: moseley at bumby:~$ scanimage -L Segmentation fault Finally: moseley at bumby:~$ scanimage >out.png scanimage: no SANE devices found or sometimes: meley at bumby:~$ scanimage >out.png scanimage: sane_start: Error during device I/O And that's where I'm stuck. Any suggestions? Here's more details on my setup. Probably more info than needed, but... Debian Sid with 2.6.6. MSI K7T266 main board. moseley at bumby:~$ dpkg -l | egrep '(sane|libusb|hotplug)' ii hotplug 0.0.20040329-8 Linux Hotplug Scripts ii libsane 1.0.14-2 API library for scanners ii libusb-0.1-4 0.1.8-11 Userspace USB programming library ii sane 1.0.12-2 scanner graphical frontends ii sane-utils 1.0.14-2 API library for scanners -- utilities ii xsane 0.93-1 GTK+-based X11 frontend for SANE (Scanner Ac ii xsane-common 0.93-1 GTK+-based X11 frontend for SANE (Scanner Ac Here's one of my usb entries from lspci -v (says USB2.0 but I think my USB is 1.1, according to the MSI motherboard manual). 0000:00:11.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 1b) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller Flags: bus master, medium devsel, latency 64, IRQ 5 I/O ports at d400 [size=32] Capabilities: [80] Power Management version 2 moseley at bumby:~$ lsmod Module Size Used by videodev 9408 0 lp 10564 0 uhci_hcd 30672 0 w83627hf 28612 0 i2c_sensor 2944 1 w83627hf i2c_isa 2048 0 i2c_viapro 7052 0 i2c_core 23044 4 w83627hf,i2c_sensor,i2c_isa,i2c_viapro moseley at bumby:~$ fgrep USB /boot/config-2.6.6-xfs-athlon | grep -v ^# CONFIG_USB=y CONFIG_USB_DEVICEFS=y CONFIG_USB_UHCI_HCD=m CONFIG_USB_AUDIO=m CONFIG_USB_PRINTER=m CONFIG_USB_STORAGE=m CONFIG_USB_HID=m CONFIG_USB_HIDINPUT=y CONFIG_USB_HIDDEV=y CONFIG_USB_KBD=m CONFIG_USB_MOUSE=m CONFIG_USB_SERIAL=m CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_BELKIN=m CONFIG_USB_SERIAL_WHITEHEAT=m CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m CONFIG_USB_SERIAL_EMPEG=m CONFIG_USB_SERIAL_FTDI_SIO=m CONFIG_USB_SERIAL_VISOR=m CONFIG_USB_SERIAL_IPAQ=m CONFIG_USB_SERIAL_IR=m CONFIG_USB_SERIAL_EDGEPORT=m CONFIG_USB_SERIAL_KEYSPAN_PDA=m CONFIG_USB_SERIAL_KEYSPAN=m CONFIG_USB_SERIAL_KLSI=m CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_SERIAL_PL2303=m CONFIG_USB_SERIAL_CYBERJACK=m CONFIG_USB_SERIAL_XIRCOM=m CONFIG_USB_SERIAL_OMNINET=m CONFIG_USB_EZUSB=y CONFIG_USB_RIO500=m I'm able to scan on my laptop, also runnning Debian Sid and same software. But, once in a while I do see similar problems -- so I wonder if it's a scanner issue. Jun 29 09:29:22 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r Jun 29 09:29:23 localhost kernel: usb 1-1: control timeout on ep0in Jun 29 09:29:23 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r Jun 29 09:29:44 localhost kernel: usb 1-1: control timeout on ep0out Jun 29 09:30:09 localhost kernel: usb 1-1: control timeout on ep0out Jun 29 09:30:41 localhost kernel: usb 1-1: bulk timeout on ep1in Jun 29 09:30:41 localhost kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x81 len 4096 ret -110 Jun 29 09:30:46 localhost kernel: usb 1-1: control timeout on ep0out Jun 29 09:31:16 localhost kernel: usb 1-1: bulk timeout on ep2out Jun 29 09:31:16 localhost kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x2 len 2 ret -110 -- Bill Moseley moseley at hank.org From anoah at pfeiffer.edu Wed Jun 30 00:34:08 2004 From: anoah at pfeiffer.edu (m. allan noah) Date: Tue, 29 Jun 2004 19:34:08 -0400 (EDT) Subject: [sane-devel] VIA chipset and HP4100C USB scanner In-Reply-To: <20040629214551.GB19339@hank.org> References: <20040629214551.GB19339@hank.org> Message-ID: when you run scanimage with no -d argument, sane will load all the backends that are listed in the dll.conf file, in an attempt to find your scanner. you can look for this file in /etc/sane.d or similar, and # out all the options other than the backend you are using. this should fix the video issues. as to the timeouts, that could have any number of causes, but seems really common with 2.6.x can you switch back to a 2.4 kernel just to test? allan On Tue, 29 Jun 2004, Bill Moseley wrote: > > I've got a MSI KT266-Pro2 motherboard with a VIA chipset. I'm wondering if > my hardware is the problem or if there's other things to check. I'm > able to sync a USB Palm device with Jpilot without any problems, but > my scanner generates errors. > > I have another machine (an older Toshiba laptop) which first reported > errors (way below), but I'm now able to scan with the HP 4100C scanner. > > One difference is that on my desktop it seems that hotplug is loading > videodev module, but that doesn't happen on my laptop. I'm not sure > why. > > So basically, my qustion is if my hardware is just broken and will never > work, or if there's something else I can try to resolve scanning > problems. I have hope since Jpilot usb sync works. > > Here's some details: > > Both my Desktop (the KT266-Pro2 machine) and my laptop are running > Debian Sid. The Desktop has 2.6.6 and the laptop 2.6.5. Otherwise, > same software (below for sane and libusb versions). > > > When I plug in my scanner into the KT266-PRO2 I see: > > Jun 28 21:30:25 bumby kernel: usb 1-2: new full speed USB device using address 2 > > > Then I run sane-find-scanner and it reports: > > found USB scanner (vendor=0x03f0, product=0x0101) at libusb:001:002 > # Your USB scanner was (probably) detected. It may or may not be supported by > # SANE. Try scanimage -L and read the backend's manpage. > > > and in syslog I see: > > Jun 28 21:30:41 bumby kernel: usb 1-2: control timeout on ep0in > Jun 28 21:30:41 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 > Jun 28 21:30:42 bumby kernel: usb 1-2: control timeout on ep0in > Jun 28 21:30:42 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 > > Sometimes this works: > > moseley at bumby:~$ scanimage -L > device `hp:libusb:001:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner > > and entries in syslog from scanimage: > > Jun 28 21:34:11 bumby kernel: Linux video capture interface: v1.00 > Jun 28 21:34:18 bumby kernel: usb 1-2: control timeout on ep0out > > Not sure why Linux video capture was loaded. I don't have any video > capture cards. lsmod shows "videodev". Is hotplug confused about what > module should be loaded? > > Sometimes syslog reports this again: > > Jun 28 21:37:34 bumby kernel: usb 1-2: control timeout on ep0out > > But sometimes scanimage -L reports that a scanner can't be found, and > sometimes scanimage -L hangs with the process in "D" status which can't > be kill -9'ed (requires a reboot, so it seems). I've also had scanimage > -L do this: > > moseley at bumby:~$ scanimage -L > Segmentation fault > > Finally: > > moseley at bumby:~$ scanimage >out.png > scanimage: no SANE devices found > > or sometimes: > > meley at bumby:~$ scanimage >out.png > scanimage: sane_start: Error during device I/O > > And that's where I'm stuck. Any suggestions? > > Here's more details on my setup. Probably more info than needed, but... > > Debian Sid with 2.6.6. MSI K7T266 main board. > > moseley at bumby:~$ dpkg -l | egrep '(sane|libusb|hotplug)' > ii hotplug 0.0.20040329-8 Linux Hotplug Scripts > ii libsane 1.0.14-2 API library for scanners > ii libusb-0.1-4 0.1.8-11 Userspace USB programming library > ii sane 1.0.12-2 scanner graphical frontends > ii sane-utils 1.0.14-2 API library for scanners -- utilities > ii xsane 0.93-1 GTK+-based X11 frontend for SANE (Scanner Ac > ii xsane-common 0.93-1 GTK+-based X11 frontend for SANE (Scanner Ac > > > Here's one of my usb entries from lspci -v (says USB2.0 but I think my > USB is 1.1, according to the MSI motherboard manual). > > 0000:00:11.2 USB Controller: VIA Technologies, Inc. VT6202 [USB 2.0 controller] (rev 1b) (prog-if 00 [UHCI]) > Subsystem: VIA Technologies, Inc. (Wrong ID) USB Controller > Flags: bus master, medium devsel, latency 64, IRQ 5 > I/O ports at d400 [size=32] > Capabilities: [80] Power Management version 2 > > > > > moseley at bumby:~$ lsmod > Module Size Used by > videodev 9408 0 > lp 10564 0 > uhci_hcd 30672 0 > w83627hf 28612 0 > i2c_sensor 2944 1 w83627hf > i2c_isa 2048 0 > i2c_viapro 7052 0 > i2c_core 23044 4 w83627hf,i2c_sensor,i2c_isa,i2c_viapro > > moseley at bumby:~$ fgrep USB /boot/config-2.6.6-xfs-athlon | grep -v ^# > CONFIG_USB=y > CONFIG_USB_DEVICEFS=y > CONFIG_USB_UHCI_HCD=m > CONFIG_USB_AUDIO=m > CONFIG_USB_PRINTER=m > CONFIG_USB_STORAGE=m > CONFIG_USB_HID=m > CONFIG_USB_HIDINPUT=y > CONFIG_USB_HIDDEV=y > CONFIG_USB_KBD=m > CONFIG_USB_MOUSE=m > CONFIG_USB_SERIAL=m > CONFIG_USB_SERIAL_GENERIC=y > CONFIG_USB_SERIAL_BELKIN=m > CONFIG_USB_SERIAL_WHITEHEAT=m > CONFIG_USB_SERIAL_DIGI_ACCELEPORT=m > CONFIG_USB_SERIAL_EMPEG=m > CONFIG_USB_SERIAL_FTDI_SIO=m > CONFIG_USB_SERIAL_VISOR=m > CONFIG_USB_SERIAL_IPAQ=m > CONFIG_USB_SERIAL_IR=m > CONFIG_USB_SERIAL_EDGEPORT=m > CONFIG_USB_SERIAL_KEYSPAN_PDA=m > CONFIG_USB_SERIAL_KEYSPAN=m > CONFIG_USB_SERIAL_KLSI=m > CONFIG_USB_SERIAL_MCT_U232=m > CONFIG_USB_SERIAL_PL2303=m > CONFIG_USB_SERIAL_CYBERJACK=m > CONFIG_USB_SERIAL_XIRCOM=m > CONFIG_USB_SERIAL_OMNINET=m > CONFIG_USB_EZUSB=y > CONFIG_USB_RIO500=m > > I'm able to scan on my laptop, also runnning Debian Sid and same software. > But, once in a while I do see similar problems -- so I wonder if it's a > scanner issue. > > Jun 29 09:29:22 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r > Jun 29 09:29:23 localhost kernel: usb 1-1: control timeout on ep0in > Jun 29 09:29:23 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r > Jun 29 09:29:44 localhost kernel: usb 1-1: control timeout on ep0out > Jun 29 09:30:09 localhost kernel: usb 1-1: control timeout on ep0out > Jun 29 09:30:41 localhost kernel: usb 1-1: bulk timeout on ep1in > Jun 29 09:30:41 localhost kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x81 len 4096 ret -110 > Jun 29 09:30:46 localhost kernel: usb 1-1: control timeout on ep0out > Jun 29 09:31:16 localhost kernel: usb 1-1: bulk timeout on ep2out > Jun 29 09:31:16 localhost kernel: usbfs: USBDEVFS_BULK failed dev 2 ep 0x2 len 2 ret -110 > > > > -- "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 avalev70 at yahoo.com Wed Jun 30 09:37:51 2004 From: avalev70 at yahoo.com (Alexandre Averyanov) Date: Wed, 30 Jun 2004 01:37:51 -0700 (PDT) Subject: [sane-devel] Epson Perfection 1670 and high resolution Message-ID: <20040630083751.52744.qmail@web53401.mail.yahoo.com> On Tuesday 29 June 2004 22.45, Eric Tanguy wrote: > I use this scanner on fedora core 2 with sane-backends-1.0.13-7 and > xsane-0.92-10. All works fine except when i try to use resolution > greater than 600 (900 or 1200). In these cases, the result is > malformed and the colours are wrong. > What's the problem and how to solve it ? These resolutions are broken on the 1670. You need to upgrade to=20 sane-backends-1.0.14, it offers 800 dpi and 1600 dpi instead which=20 are supposed to work fine. /Oliver I have the same problem but already with SANE 1.0.14: gray images obtained from scanner using 1600 dpi (only!) have strange vertical stripes. As for 800 dpi it's ok. __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail From picos132004 at yahoo.co.uk Wed Jun 30 09:48:07 2004 From: picos132004 at yahoo.co.uk (=?iso-8859-1?q?Ioan-Cosmin=20Pop?=) Date: Wed, 30 Jun 2004 09:48:07 +0100 (BST) Subject: [sane-devel] check-usb-chip request for help In-Reply-To: <20040629143225.95772.qmail@web52207.mail.yahoo.com> Message-ID: <20040630084807.99047.qmail@web25103.mail.ukl.yahoo.com> Yes, I do have the sources of the windows driver for the scanner Mustek BearPaw 4800TA ProII. I contacted Mustek and they gave them to me. I had to sign a NDA, so I can't make them public. I can't even show portions of it... :( I want to write a backend for sane for this scanner. It's not a port to a specific OS (sane can be installed on a large number of OSs), but I am doing the development under linux. Cosmin --- j d wrote: > Hi > > I've gone through this mail, i am not clear about > what both of u talking but i guess, it seems one of > you is having the windows driver source code and > trying to port it to an another OS, may i know to > which OS you are trying to port it? > > JD > > Ioan-Cosmin Pop wrote: > Hi Ronald! > > Thank you for answering! > > --- Ronald Humphries wrote: > Hello > Cosmin. > > > > I??m still here and reading this. Is the windows > > source the complete > > driver or a part of it? > It's the complete driver. Anything needed to acces > the > scanner is there. > > > > Anyway, if you need help, I will do my best. So > far > > for me everything is > > clear, as Henning explained. > Yes, I need help, somebody to talk to. I thought I > can > do it all alone, but I can't. I would really like > you > to have also the windows sources, so we have a > common > ground. What do you think? > > > > Normally I have some time in the evening for > > programming, not much, > > because I??m alone with my 4 year old kid. > Send him all the best from me :) > > -- > > Ronald Humphries > > > > > Cosmin > > > > > > > ___________________________________________________________ALL-NEW > Yahoo! Messenger - sooooo many all-new ways to > express yourself http://uk.messenger.yahoo.com > > -- > sane-devel mailing list: > sane-devel at lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe > your_password" > to sane-devel-request at lists.alioth.debian.org > > > --------------------------------- > Do you Yahoo!? > New and Improved Yahoo! Mail - Send 10MB messages! ___________________________________________________________ALL-NEW Yahoo! Messenger - sooooo many all-new ways to express yourself http://uk.messenger.yahoo.com From my_techinfo_c at yahoo.com Wed Jun 30 10:03:59 2004 From: my_techinfo_c at yahoo.com (j d) Date: Wed, 30 Jun 2004 02:03:59 -0700 (PDT) Subject: [sane-devel] On what basis the device speciific structure will be defined?? Message-ID: <20040630090359.4969.qmail@web52210.mail.yahoo.com> Hi Henning, How are you? I have gone through the sample scanner drvier written by you, now my question for you is, on what basis you have been defined the "Structure to hold all of our device specific stuff", if I need to define a same kind of structure for an another scanner, what are the things I need to take into consideration or can i blindly follow the same structure, what you have been defined? or can I use the one which is defined in usb-skelton.c? Hope to see an early and positive reply from you, Thank you, Regards, JD __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail From eelke_klein at yahoo.com Wed Jun 30 17:38:24 2004 From: eelke_klein at yahoo.com (Eelke Klein) Date: Wed, 30 Jun 2004 09:38:24 -0700 (PDT) Subject: [sane-devel] Epson Perfection 660 Message-ID: <20040630163824.11893.qmail@web50908.mail.yahoo.com> Hello, I'm trying to get my epson perfection 660 scanner to work. I have had it working on SuSE 8.2 but I have switched to gentoo and can't get it to work anymore. sane-find-scanner can find it but scanimage -L doesn't. I have the permissions in /proc/bus/usb automatically set by a hotplug script and have checked that the rights are actually set. I also tried it as root so the rights shouldn't be a problem anyway. I have copied the firmware of my windows drivers and configured the location of it in the scapscan.conf. I have also checked that the id's of my scanner actually matched the id's in the snapscan.conf. snapscan is also enabled in the dll.conf. Here some version: Kernel 2.6.7 sane-backends 1.0.14-r3 libusb 0.1.7-r1 Eelke __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail From rohum at gmx.de Tue Jun 29 20:39:17 2004 From: rohum at gmx.de (Ronald Humphries) Date: Tue, 29 Jun 2004 21:39:17 +0200 Subject: [sane-devel] check-usb-chip request for help Message-ID: <1088537957.24804.10.camel@linux1.rohu.de> Hello Cosmin, >It's the complete driver. Anything needed to acces the >scanner is there. That?s good, that will make it not so difficult. So normally, we will find all parts what we will need in the sources. Do you got also some documentation from Mustek? >Yes, I need help, somebody to talk to. I thought I can >do it all alone, but I can't. I would really like you >ground. What do you think? Yes, I will need all informations. Then we will talk about the same things. Do you think it will be possible to get the same as you have? Can you ask them? >> Normally I have some time in the evening for >> programming, not much, >> because I??m alone with my 4 year old kid. >Send him all the best from me :) Many thanks. Do you have a step list for what has to be done, to get this into sane working? But I think first of all, we must get the check-usb-chip program working correctly for the scanner. Ronald From henning at meier-geinitz.de Wed Jun 30 18:48:58 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 30 Jun 2004 19:48:58 +0200 Subject: [sane-devel] Epson Perfection 660 In-Reply-To: <20040630163824.11893.qmail@web50908.mail.yahoo.com> References: <20040630163824.11893.qmail@web50908.mail.yahoo.com> Message-ID: <20040630174858.GA11478@meier-geinitz.de> Hi, On Wed, Jun 30, 2004 at 09:38:24AM -0700, Eelke Klein wrote: > I'm trying to get my epson perfection 660 scanner to work. I > have had it working on SuSE 8.2 but I have switched to gentoo > and can't get it to work anymore. > > sane-find-scanner can find it but scanimage -L doesn't. I have > the permissions in /proc/bus/usb automatically set by a hotplug > script and have checked that the rights are actually set. I also > tried it as root so the rights shouldn't be a problem anyway. Try enabling debug messages: SANE_DEBUG_SNAPSCAN=255 scanimage -L If you don't get any output, the snapscan backend isn't loaded for some reason. Bye, Henning From henning at meier-geinitz.de Wed Jun 30 18:55:42 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 30 Jun 2004 19:55:42 +0200 Subject: [sane-devel] VIA chipset and HP4100C USB scanner In-Reply-To: <20040629214551.GB19339@hank.org> References: <20040629214551.GB19339@hank.org> Message-ID: <20040630175542.GB11478@meier-geinitz.de> Hi, On Tue, Jun 29, 2004 at 02:45:51PM -0700, Bill Moseley wrote: > I've got a MSI KT266-Pro2 motherboard with a VIA chipset. I'm wondering if > my hardware is the problem or if there's other things to check. I'm > able to sync a USB Palm device with Jpilot without any problems, but > my scanner generates errors. Maybe it's hardware but I rather think it's a kernel problem. There have been many reports about similar trouble with 2.6 kernels and VIA hardware. > Then I run sane-find-scanner and it reports: > > found USB scanner (vendor=0x03f0, product=0x0101) at libusb:001:002 > # Your USB scanner was (probably) detected. It may or may not be supported by > # SANE. Try scanimage -L and read the backend's manpage. > > > and in syslog I see: > > Jun 28 21:30:41 bumby kernel: usb 1-2: control timeout on ep0in > Jun 28 21:30:41 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 > Jun 28 21:30:42 bumby kernel: usb 1-2: control timeout on ep0in > Jun 28 21:30:42 bumby kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 rq 6 len 100 ret -110 sane-find-scanner just looks for USB devices. It doesn't send any device-specific commands (at least in this case). So it's most probably not a SANE problem. > Sometimes this works: > > moseley at bumby:~$ scanimage -L > device `hp:libusb:001:002' is a Hewlett-Packard ScanJet 4100C flatbed scanner > > and entries in syslog from scanimage: > > Jun 28 21:34:11 bumby kernel: Linux video capture interface: v1.00 > Jun 28 21:34:18 bumby kernel: usb 1-2: control timeout on ep0out > > Not sure why Linux video capture was loaded. I don't have any video > capture cards. lsmod shows "videodev". Is hotplug confused about what > module should be loaded? SANE can also "scan" from video cards that are supported by video4linux. > Jun 28 21:37:34 bumby kernel: usb 1-2: control timeout on ep0out > > But sometimes scanimage -L reports that a scanner can't be found, and > sometimes scanimage -L hangs with the process in "D" status which can't > be kill -9'ed (requires a reboot, so it seems). I've also had scanimage > -L do this: > > moseley at bumby:~$ scanimage -L > Segmentation fault Bad. I haven't seen reports about such behaviour until now. > And that's where I'm stuck. Any suggestions? Ask the Linux kernel guys. As a workaround, use kernel 2.4.* > I'm able to scan on my laptop, also runnning Debian Sid and same software. > But, once in a while I do see similar problems -- so I wonder if it's a > scanner issue. > > Jun 29 09:29:22 localhost kernel: usbfs: USBDEVFS_CONTROL failed cmd sane-find-scann dev 2 rqt 128 r > Jun 29 09:29:23 localhost kernel: usb 1-1: control timeout on ep0in Control timeouts mean that something went wrong with the communication of the host and the scanner. The reason can be a wrong command, but as these problems only occur on 2.6 it looks like a kernel issue for me. Unfortunately nobody has yet found out the real cause. Bye, Henning From henning at meier-geinitz.de Wed Jun 30 18:58:56 2004 From: henning at meier-geinitz.de (Henning Meier-Geinitz) Date: Wed, 30 Jun 2004 19:58:56 +0200 Subject: [sane-devel] On what basis the device speciific structure will be defined?? In-Reply-To: <20040630090359.4969.qmail@web52210.mail.yahoo.com> References: <20040630090359.4969.qmail@web52210.mail.yahoo.com> Message-ID: <20040630175856.GC11478@meier-geinitz.de> Hi, On Wed, Jun 30, 2004 at 02:03:59AM -0700, j d wrote: > How are you? Fine. But there are other people on this list :-) > I have gone through the sample scanner drvier written by you, Could you explain which sample driver you mean? A specific SANE backend or the Linux kernel scanner driver? > now my question for you > is, on what basis you have been defined the "Structure > to hold all of our device specific stuff", if I need > to define a same kind of structure for an another > scanner, what are the things I need to take into > consideration or can i blindly follow the same > structure, what you have been defined? > or can I use > the one which is defined in usb-skelton.c? Hope to see > an early and positive reply from you, Thank you, usb-skeleton.c is part of the kernel. So this mail is about the kernel scanner driver? Can you explain what you intend to achieve? Bye, Henning From Oliver.Schwartz at gmx.de Wed Jun 30 21:31:49 2004 From: Oliver.Schwartz at gmx.de (Oliver Schwartz) Date: Wed, 30 Jun 2004 22:31:49 +0200 Subject: [sane-devel] Epson Perfection 1670 and high resolution In-Reply-To: <20040630083751.52744.qmail@web53401.mail.yahoo.com> References: <20040630083751.52744.qmail@web53401.mail.yahoo.com> Message-ID: <200406302232.02293.Oliver.Schwartz@gmx.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, > I have the same problem but already with SANE 1.0.14: > gray images obtained from scanner using 1600 dpi > (only!) have strange vertical stripes. As for 800 dpi > it's ok. That's a different bug then (which I haven't heard of before). It only affects gray images? (i.e. 1600 dpi in color work fine?) /Oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQFA4yM8/V6sbrmfIuMRAiCuAJ9SV0zK+l6HP5I0mh7ur64slPWSAgCfbMPN BJpYOgKmPPDH2DVqEXMupR8= =1ktK -----END PGP SIGNATURE-----