[sane-devel] Martin passed away
With deep sadness, I have to inform you that my brother Martin has passed away last Saturday. Most of the time, he enjoyed working with you. Keep up the good work, Rob -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] lexmark cx310n on ubuntu 17.10
Hi, after an upgrade from ubuntu 16.04 to ubuntu 17.10, my scanner is not reconized anymore. I've tried sur install the latest sane backends but there is nothing to do. Can anyone help me please ? Thanks. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] CanoScan LiDE 220 can't scan dpi over 1200
Hey folks, I just bought a CanoScan LiDE 220. Unfortunately scanning with 2400 or 4800 dpi doesn't work as claimed on your website. scanimage just hangs, not printing any errors and the sensor doesn't move an inch. Scanning with 1200 dpi works fine though. $ scanimage -V scanimage (sane-backends) 1.0.27; backend version 1.0.27 I appreciate any help. Best regards, Martin -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Canon TS8050 not working correctly
Hi, I installed my new Canon TS8050 on Ubuntu 16.4 LTS with the PPA ppa:rolfbensch/sane-git The scanner is connected by USB. It is correctly detected. The command SANE_DEBUG_BJNP=4 scanimage -L 2>log detects the scanner as well. The command scanimage -T passes all tests. A first pre-scan with XSane works, but afterward the scanner does not respond any more. The display says “scanning”. A scan without a pre-scan results in the same error. Simple Scan produces this same error on the first scan. SANE_DEBUG_PIXMA=11 xsane &> pixma.log shows pixma is compiled with pthread support. [pixma] pixma version 0.17.42 [pixma] pixma_collect_devices() found Canon PIXMA TS8000 Series at libusb:001:005 [pixma] pixma_find_scanners() found 1 devices [pixma] pixma_collect_devices() found Canon PIXMA TS8000 Series at libusb:001:005 [pixma] pixma_open(): Canon PIXMA TS8000 Series [pixma] *mp150_open* This is a generation 5 scanner. * [pixma] INTR T=5.782 len=32 [pixma] :00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] 0010:00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [pixma] [pixma] WARNING:send_time() disabled! ... [pixma] pixma_scan(): start [pixma] line_size=3828 image_size=6714312 channels=3 depth=8 [pixma] dpi=150x150 offset=(0,0) dimension=1276x1754 [pixma] gamma_table=0x56123178b848 source=0 [pixma] threshold=127 threshold_curve=0 [pixma] adf-wait=0 [pixma] ADF page count: 0 [pixma] OUT T=24.435 len=288 ... xmlns:ivec="http://www.canon.com/ns/cmd/2008/07/common/;>StartJobservicetype="scan">00011 [pixma] XML response back from scanner: http://www.canon.com/ns/cmd/2008/07/common/;> StartJobResponse NG PCScanning [pixma] pixma_scan() failed EPROTO [pixma] Reader task terminated: EPROTO [pixma] Setting non-blocking mode [pixma] read_image():reader task closed the pipe:0 bytes received, 6714312 bytes expected [pixma] pixma_close(): Canon PIXMA TS8000 Series If it helps I could analyze the communication in a Windows-system. Do you know a good and safe analyzer? I had used USB-lyzer some years ago and can’t use the new version any more without buying it. Any help is appreciated Martin -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Updated dutch translation
Hi, May be a little late, but I hope not too late. In the attachment you'll find an update to the dutch translation. It completely replaces the current po- file. B.t.w. the source was taken from git d.d. May 17, 2017 Hope someone can take care of my translation, thanks Martin Kho nl.po.gz Description: application/gzip -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] pixma 5300 series not working because of sanei_bjnp_open return status
Le 19/06/2016 04:22, Olaf Meeuwissen a écrit : Louis Lagendijk writes: On Sat, 2016-06-18 at 10:14 +0200, Martin wrote: Hi, I am looking for someone to merge the proposed change to upstream in https://alioth.debian.org/tracker/index.php?func=detail=315219 oup_id=30186=410366 So we can get a new package/release and make the 5300's scanner to work again ! It doesn't work in ubuntu since a long time now : https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1526198 Thanks this bug has been fixed in git for almost a year and was included in the 1.0.25 release of sane. Are you using 1.0.25 or a git checkout? If so, this issue cannot be the reason for the fault you are seeing. I assume Martin is using the libsane package from Ubuntu. Unfortunately, that package has a *very* misleading version number (in wily, xenial and yakkety). It reads: 1.0.25+git20150528-1ubuntu2. This gives the impression that you're using something *after* the 1.0.25 release while in fact you are using something from the git repository *before* the 1.0.25 release. In terms of Debian/Ubuntu versioning, the package should be using: 1.0.25~git20150528-1ubuntu2 Part of the confusion is probably to blame on the way we specify the version in configure.ac. As for Martin's problem, that was fixed on 20150627 so it's not in the regular Ubuntu package. The easiest way to solve this would probably be to use the *snapshot* packages from Rolf's PPA https://launchpad.net/~rolfbensch/+archive/ubuntu/sane-git @Rolf> You may want to change the versioning of your packages to use the tilde (~) too. That way, an official 1.0.26 will take precedence when available. Hope this helps, Hi, Thank you for the helpful answer, and for the provided workaround. I hope the official ubuntu package will be updated soon ! :D -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] pixma 5300 series not working because of sanei_bjnp_open return status
Hi, I am looking for someone to merge the proposed change to upstream in https://alioth.debian.org/tracker/index.php?func=detail=315219_id=30186=410366 So we can get a new package/release and make the 5300's scanner to work again ! It doesn't work in ubuntu since a long time now : https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1526198 Thanks -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] saned does not find hpaio scanner
I traced the problem to https://sourceforge.net/p/hplip/mailman/hplip-devel/thread/46a1257e.5060...@cab.cnea.gov.ar/ tl;dr: hplip changed and now the hpaio backend no longer ignores the local_only flag. In the past, saned/hpaio was able to access network printers, even though saned asked it to search local_only. This has now been "fixed" to avoid a deadlock situation: https://bugzilla.redhat.com/show_bug.cgi?id=743593#c18 The question now becomes: how can I tell saned to please also consider non-local devices, i.e. pass local_only=0 to the sane_hpaio_get_devices() call? Or is there a better solution? -- .''`. martin f. krafft <madduck@d.o> @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems fashions have done more harm than revolutions. -- victor hugo digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] saned does not find hpaio scanner
Hey, We have a scanner available through a network and since we wanted to avoid having to install the hplip drivers on all workstations, we thought we'd employ saned to make the scanner available on the network. This worked fine until we upgraded to Debian jessie / sane 1.0.24 (from 1.0.22). Now, while I can access the scanner from the "scan server" just fine: # scanimage -L device `hpaio:/net/HP_LaserJet_3052?ip=192.168.14.30' is a Hewlett-Packard HP_LaserJet_3052 all-in-one saned does not know about it anymore: # SANE_DEBUG_DLL=255 SANE_DEBUG_NET=255 SANE_DEBUG_HPAIO=255 sudo -Eu saned saned -d [saned] main: starting debug mode (level 2) [saned] saned (AF-indep+IPv6) from sane-backends 1.0.24 starting up [saned] check_host: access by remote host: 192.168.14.33 [saned] init: access granted to madduck@192.168.14.33 [sanei_debug] Setting debug level of dll to 255. [dll] sane_init: SANE dll backend version 1.0.13 from sane-backends 1.0.24 [dll] sane_init/read_dlld: attempting to open directory `./dll.d' [dll] sane_init/read_dlld: attempting to open directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: using config directory `/etc/sane.d/dll.d' [dll] sane_init/read_dlld: considering /etc/sane.d/dll.d/libsane-extras [dll] sane_init/read_config: reading dll.d/libsane-extras [dll] add_backend: adding backend `ls5000' [dll] sane_init/read_dlld: considering /etc/sane.d/dll.d/hplip [dll] sane_init/read_config: reading dll.d/hplip [dll] add_backend: adding backend `hpaio' [dll] sane_init/read_dlld: done. [dll] sane_init/read_config: reading dll.conf [dll] sane_get_devices [dll] load: searching backend `hpaio' in `/usr/lib/x86_64-linux-gnu/sane:/usr/lib/sane' [dll] load: trying to load `/usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1' [dll] load: dlopen()ing `/usr/lib/x86_64-linux-gnu/sane/libsane-hpaio.so.1' [dll] init: initializing backend `hpaio' [sanei_debug] Setting debug level of hpaio to 255. [hpaio] sane_hpaio_init(): scan/sane/hpaio.c 323 [dll] init: backend `hpaio' is version 1.0.0 [hpaio] sane_hpaio_get_devices(local=1): scan/sane/hpaio.c 342 [dll] load: searching backend `ls5000' in `/usr/lib/x86_64-linux-gnu/sane:/usr/lib/sane' [dll] load: trying to load `/usr/lib/x86_64-linux-gnu/sane/libsane-ls5000.so.1' [dll] load: dlopen()ing `/usr/lib/x86_64-linux-gnu/sane/libsane-ls5000.so.1' [dll] init: initializing backend `ls5000' [dll] init: backend `ls5000' is version 1.0.0 [dll] sane_get_devices: found 0 devices [saned] bailing out, waiting for children... [saned] bail_out: all children exited Why is the libsane-hpaio.so backend not finding the scanner that scanimage can access? Thanks, -- @martinkrafft | http://madduck.net/ | http://two.sentenc.es/ "we did rate the microsoft security researcher as less-bad than the people who prepare the carcasses for dissection in biology laboratories." -- michael moyer, executive editor of _popular science_ spamtraps: madduck.bo...@madduck.net digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Canon LiDE 120 git commit 128c8931b3
Thanks for the update. Worked for me too. Keep up the good work. Martin - Mail original - De: "Pavel Sayekat" <pavelsaye...@gmail.com> À: sane-devel@lists.alioth.debian.org Envoyé: Vendredi 26 Février 2016 11:24:52 Objet: Re: [sane-devel] Canon LiDE 120 git commit 128c8931b3 Hi, Now its working, atleast at 300 dpi, I tried with frontend gscan2pdf with latest backend from sane-git, thanks to Stef. regards Pavel Steven Honeyman wrote > On 4 April 2015 at 06:46, Stef > stef.dev@ > wrote: >> On 30/03/2015 23:37, Steven Honeyman wrote: >>> >>> Hi, >>> >>> I noticed the commit for supporting this scanner appear a couple of >>> weeks ago, and I recompiled and tested it today. Unfortunately it >>> doesn't work. >>> >>> It's detected correctly. (the following is all using xsane, just using >>> preview button) >>> >>> At 75dpi default, preview button does nothing - generic error message >>> 300dpi, the scanner flashes for a while but doesn't move, then generic >>> error message. >>> 300dpi again (just in case it was warming up the first time) and it >>> moves! and keeps moving, and keeps moving, until it gets to the end >>> and is still moving (making a horrible noise) >>> >>> I pulled the USB, reconnected to a Windows PC and luckily it still >>> works OK. The driver needs some adjustment though for sure! >>> >>> >>> Thanks, >>> Steven. >> >> Hello, >> >> I haven't been able to generate a scan log with my LiDE 110 close >> enough >> to the 120 logs sent to me. So currently I don't know how much code is >> needed to bring support for this model, since I don't have similar scans >> to >> compare. >> I really need a log done with the WIA driver (NOT the shipped >> scanning >> suite) at 150 dpi. >> >> Regards, >> Stef > > Hi, > > No problem, here you go: > > https://drive.google.com/file/d/0B7D9SMSeoCQ9NGJDUW8tLVQ0RjQ/view?usp=sharing > > Hope that helps! > > > Thanks, > Steven > > -- > sane-devel mailing list: > sane-devel@.debian > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to > sane-devel-request@.debian -- View this message in context: http://sane.10972.n7.nabble.com/Canon-LiDE-120-git-commit-128c8931b3-tp19613p20665.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Updated dutch translation
Hi, In the attachment you'll find an update to the dutch translation. This isn't in the form of a patch, like Yuri did. It completely replaces the current po-file. If you need a patch version, please let me know. B.t.w. the source was taken from git d.d. September 24, 2015 Hope someone can take care of my translation, thanks Martin Kho nl.po.gz Description: application/gzip -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Missing Resolution for Canon MG7550
Hi Rolf, The sane backend does not provide all resolutions of the scanner: Xsane offers 75, 150, 300, 600, 1200 and 2400 ppi. Canon's scangear however offers 75, 100, 150, 200, 300, 400, 600 and 1200 ppi. In order to reduce the Moiré effect it is necessary to scan with a resolution which is not a power of 2 of the bad resolution. Cheers, Martin -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] pixma mg7500 testing
Hi Camilo, I just checked my GIT-repo. The latest commit is d0e7675e60dc5073437d4745277ec4f8934c8fd1. git status tells me that my branch corresponds to origin/master. Before I built the new version I deleted the following files in order to make sure that the old version does not interfere: /usr/lib/sane/* /usr/lib/sane* /usr/lib64/sane/* /usr/lib64/sane* /usr/local/lib/sane/* /usr/local/lib/libsane* /usr/local/lib64/sane/* /usr/local/lib64/libsane* Regards, Martin On, 2015-08-10, 21.39:28 Camilo Schöningh wrote: Hey! I am not sure. But for me it looks like the latest pixma changes, made my scanner not working anymore. :-( Regards, Camilo On 10.08.2015 21:29, Martin wrote: Hi Rolf I've tested the latest version of the sane backend for Canon Pixma MG7550 with USB-connection. For me it works fine. xsane and the Gimp-plugin initialize all right and the picture is as it should be. Many thanks for your work. Best regards, Martin Am Donnerstag, 6. August 2015, 12.38:09 schrieb Jonathan Anderson: I have tested network connections for Canon Pixma MG7550 Connected by cable to router, it was detected and scanned.scanimage -Ldevice `pixma:MG7500_192.168.1.212' is a CANON Canon PIXMA MG7500 Series multi-function peripheral However, the scanner was not found by Simple Scan so I had to scan from command line.scanimage -x 100 -y 100 --format=tiff image.tiff The original was grey / white and the resulting scan was in striped colors. Not sure what to make of that. I did crop this image in GIMP to make the size acceptable for the list but it qualitatively shows the appeared colors. When using wifi connection to the router, the scanner is not found by scanimage -L or by sane-find-scanner.It is found and scans correctly using Canons own scangearmp2 resulting in a nice greyscale picture true to the original. Kind regardsJonathan From: Rolf Bensch r...@bensch-online.de To: Jonathan Anderson emailjonathananderson- n...@yahoo.com Cc: Sane Development sane-devel@lists.alioth.debian.org Sent: Wednesday, July 29, 2015 7:25 PM Subject: Re: [sane-devel] pixma mg7500 testing Hi Jonathan, I just committed the patch Sane's development sources. Maybe you want to test ethernet or wifi connection (bjnp). Please read the manpage for details (man sane-pixma). Don't hesitate to ask the mailing list for help, if you may need some. Sorry, but I cannot help with bjnp. Many thanks for your help. Cheers, Rolf Am 27.07.2015 um 14:32 schrieb Jonathan Anderson: Hi, that patch made all the stripes go away and 1200 and 2400 dpi scans now look great. Scanning is very slow but I suppose that comes down to the scan -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] pixma mg7500 testing
Hi Rolf I've tested the latest version of the sane backend for Canon Pixma MG7550 with USB-connection. For me it works fine. xsane and the Gimp-plugin initialize all right and the picture is as it should be. Many thanks for your work. Best regards, Martin Am Donnerstag, 6. August 2015, 12.38:09 schrieb Jonathan Anderson: I have tested network connections for Canon Pixma MG7550 Connected by cable to router, it was detected and scanned.scanimage -Ldevice `pixma:MG7500_192.168.1.212' is a CANON Canon PIXMA MG7500 Series multi-function peripheral However, the scanner was not found by Simple Scan so I had to scan from command line.scanimage -x 100 -y 100 --format=tiff image.tiff The original was grey / white and the resulting scan was in striped colors. Not sure what to make of that. I did crop this image in GIMP to make the size acceptable for the list but it qualitatively shows the appeared colors. When using wifi connection to the router, the scanner is not found by scanimage -L or by sane-find-scanner.It is found and scans correctly using Canons own scangearmp2 resulting in a nice greyscale picture true to the original. Kind regardsJonathan From: Rolf Bensch r...@bensch-online.de To: Jonathan Anderson emailjonathananderson-...@yahoo.com Cc: Sane Development sane-devel@lists.alioth.debian.org Sent: Wednesday, July 29, 2015 7:25 PM Subject: Re: [sane-devel] pixma mg7500 testing Hi Jonathan, I just committed the patch Sane's development sources. Maybe you want to test ethernet or wifi connection (bjnp). Please read the manpage for details (man sane-pixma). Don't hesitate to ask the mailing list for help, if you may need some. Sorry, but I cannot help with bjnp. Many thanks for your help. Cheers, Rolf Am 27.07.2015 um 14:32 schrieb Jonathan Anderson: Hi, that patch made all the stripes go away and 1200 and 2400 dpi scans now look great. Scanning is very slow but I suppose that comes down to the scan process and the usb2 connection and not the software. Thank you for helping open source forward :-) Just a short question, as you seem alert and working on this project, how come there has been no official release since 2013? Cheers jonathan *From:* Rolf Bensch r...@bensch-online.de *To:* Jonathan Anderson emailjonathananderson- n...@yahoo.com *Cc:* Sane Development sane-devel@lists.alioth.debian.org *Sent:* Saturday, July 25, 2015 12:12 PM *Subject:* Re: [sane-devel] pixma mg7500 testing Hi Jonathan, Attached patch should fix the 1200 and 2400 dpi issue. This file patches backend/pixma_mp150.c. Please copy attached file into the folder backend/ and process from inside backend/ this command: patch pixma_mp150.c pixma_mp150.c.patch1 Then 'cd ..' and 'make sudo make install'. Please report your results again. If this patch is working, I'll update Sane's development sources. Cheers, Rolf Am 24.07.2015 um 16:58 schrieb Jonathan Anderson: Hi, I've tested the sane-backends-git20150724 with Fedora 22. The scanner was correctly detected and scanned 600 dpi good as you said. It showed stripes on 1200 and 2400 just as you said. Do you need to see the scans or can I give you any additional info to help you? Kind regards Jonathan *From:* Rolf Bensch r...@bensch-online.de mailto:r...@bensch-online.de *To:* Jonathan Anderson emailjonathananderson- n...@yahoo.com mailto:emailjonathananderson-...@yahoo.com *Cc:* sane-devel@lists.alioth.debian.org mailto:sane-devel@lists.alioth.debian.org sane-devel@lists.alioth.debian.org mailto:sane-devel@lists.alioth.debian.org *Sent:* Friday, July 24, 2015 9:08 AM *Subject:* Re: [sane-devel] pixma mg7500 testing Hi Jonathan, Please install SANE Development (git) Version as described in README.linux (I assume you're using Linux): http://www.sane-project.org/docs.html http://www.sane-project.org/docs.html. Then your scanner should scan up to 600dpi without any problems.-- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Canon LiDE 120 Black Image
Hello, I tested the latest build (SANE Genesys backend version 1.0 build 2507 from sane-backends 1.0.25 git) on my LIDE 120. Scanner is recognized, stepper motor are moving but the scan image is 'all black'. I have set the debug level of Genesys to 255 Any idea what I am doing wrong ? Thanks, Martin - Mail original - De: Stef stef@free.fr À: martin gallezot martin.galle...@free.fr, sane-devel@lists.alioth.debian.org Envoyé: Mercredi 17 Juin 2015 20:44:23 Objet: Re: [sane-devel] LiDE 120, small changes pushed in git On 16/06/2015 11:41, martin.galle...@free.fr wrote: Hello, I have tested the latest build available from git. Unfortunately I wasn't able to check the version number. which debug logs are you referring to ? Anyway with the latest build, my LiDe 120 is not supported at all (even with resolution under 600 dpi). It may well be that I made a mistake at compile or forgot to update a configuration file. Anyone else had a chance to try it ? Thanks, Martin - Mail original - De: Stef stef@free.fr À: Sane Development sane-devel@lists.alioth.debian.org Envoyé: Jeudi 11 Juin 2015 21:55:07 Objet: [sane-devel] LiDE 120, small changes pushed in git Hello, I have pushed some small changes that should improve support for the LiDE 120 for resolutions up to 600 dpi. Please test this build 2507 of the geneys backend (check this version number in debug logs when testing). Working with some logs sent, then throwing back some code to someone else to test isn't practical. I don't feel like going on that way. So people interested by adding support for this model (or another one) should clone SANE's git tree and syseneg project (which provides a tool to analyze pcap usb logs), and start hacking it. I'd be happy to improve genesys backend's doc to help, and will gladly apply patches. Regards, Stef Hello, the backend generates traces when these environment variables are set: export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_LOW=255 export SANE_DEBUG_GENESYS_GL124=255 then run your frontend from the same command prompt where you typed these commands, for instance you can run scanimage like this: scanimage -d genesys --resolution 75 --preview --mode Color 2rl.log rl.pnm rl.pnm will be the scan, while rl.log will contain all debug traces. Regards, Stef -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] LiDE 120, small changes pushed in git
Stef, Ok got it. Thanks. will try this asap and let you know. Martin. - Mail original - De: Stef stef@free.fr À: martin gallezot martin.galle...@free.fr, sane-devel@lists.alioth.debian.org Envoyé: Mercredi 17 Juin 2015 20:44:23 Objet: Re: [sane-devel] LiDE 120, small changes pushed in git On 16/06/2015 11:41, martin.galle...@free.fr wrote: Hello, I have tested the latest build available from git. Unfortunately I wasn't able to check the version number. which debug logs are you referring to ? Anyway with the latest build, my LiDe 120 is not supported at all (even with resolution under 600 dpi). It may well be that I made a mistake at compile or forgot to update a configuration file. Anyone else had a chance to try it ? Thanks, Martin - Mail original - De: Stef stef@free.fr À: Sane Development sane-devel@lists.alioth.debian.org Envoyé: Jeudi 11 Juin 2015 21:55:07 Objet: [sane-devel] LiDE 120, small changes pushed in git Hello, I have pushed some small changes that should improve support for the LiDE 120 for resolutions up to 600 dpi. Please test this build 2507 of the geneys backend (check this version number in debug logs when testing). Working with some logs sent, then throwing back some code to someone else to test isn't practical. I don't feel like going on that way. So people interested by adding support for this model (or another one) should clone SANE's git tree and syseneg project (which provides a tool to analyze pcap usb logs), and start hacking it. I'd be happy to improve genesys backend's doc to help, and will gladly apply patches. Regards, Stef Hello, the backend generates traces when these environment variables are set: export SANE_DEBUG_GENESYS=255 export SANE_DEBUG_GENESYS_LOW=255 export SANE_DEBUG_GENESYS_GL124=255 then run your frontend from the same command prompt where you typed these commands, for instance you can run scanimage like this: scanimage -d genesys --resolution 75 --preview --mode Color 2rl.log rl.pnm rl.pnm will be the scan, while rl.log will contain all debug traces. Regards, Stef -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Your message to sane-devel awaits moderator approval
On Friday 05 June 2015 13:36:09 sane-devel-ow...@lists.alioth.debian.org wrote: Your mail to 'sane-devel' with the subject Re: pidora 5.21.7-13.11beta4 WOW, please don't let this message go trough. My mail client bites me. sorry Martin Kho Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://lists.alioth.debian.org/cgi-bin/mailman/confirm/sane-devel/fa01061d0 dd9f291989279cb2c4acf2494b31d63 -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error: Canon Pixma MG7550 hangs
On 03/03/2015 03:49 PM, Troels Thomsen wrote: Hi Martin, Good work Martin! Any missing commands would be a smoking gun imho. Rolf, are you following this thread ? /Troels 2015-02-24 23:09 GMT+01:00 Martin martin...@intergga.ch mailto:martin...@intergga.ch: Troels I don't have access to another computer. But I have installed OpenSUSE 13.2 and the result is the same as on 13.1. I did not (yet) test with short delays between the commands, but I compared the communication of the Canon software scangear on Windows with the one of SANE: At start ScanGear sends the following (linebreaks added by me): ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; xmlns:vcn=http://www.canon.com/ns/cmd/2008/07/canon/;  ivec:contentsivec:operationVendorCmd/ivec:operation   ivec:param_set servicetype=scan    ivec:jobID /ivec:jobID    vcn:ijoperationModeShift/vcn:ijoperation    vcn:ijmode1/vcn:ijmode   /ivec:param_set  /ivec:contents /cmd response: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; xmlns:vcn=http://www.canon.com/ns/cmd/2008/07/canon/;  ivec:contents   ivec:operationVendorCmdResponse/ivec:operation   ivec:param_set servicetype=scan    ivec:responseOK/ivec:response    ivec:response_detail/    vcn:ijoperationModeShiftResponse/vcn:ijoperation    vcn:ijresponseOK/vcn:ijresponse    vcn:ijresponse_detail/   /ivec:param_set  /ivec:contents /cmd ScanGear starts a scan with the following command sequece: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;  ivec:contents   ivec:operationStartJob/ivec:operation   ivec:param_set servicetype=scan    ivec:jobID0001/ivec:jobID    ivec:bidi1/ivec:bidi   /ivec:param_set  /ivec:contents /cmd response: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;  ivec:contents   ivec:operationStartJobResponse/ivec:operation   ivec:param_set servicetype=scan    ivec:responseOK/ivec:response    ivec:response_detail/    ivec:jobID0001/ivec:jobID   /ivec:param_set  /ivec:contents /cmd command: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; xmlns:vcn=http://www.canon.com/ns/cmd/2008/07/canon/;  ivec:contents   ivec:operationVendorCmd/ivec:operation   ivec:param_set servicetype=scan   ivec:jobID0001/ivec:jobID   vcn:ijoperationModeShift/vcn:ijoperation   vcn:ijmode1/vcn:ijmode   /ivec:param_set  /ivec:contents /cmd response: some data command: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;  ivec:contents   ivec:operationEndJob/ivec:operation   ivec:param_set servicetype=scan    ivec:jobID0001/ivec:jobID   /ivec:param_set  /ivec:contents /cmd response: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/;  ivec:contents   ivec:operationEndJobResponse/ivec:operation   ivec:param_set servicetype=scan    ivec:responseOK/ivec:response    ivec:response_detail/    ivec:jobID0001/ivec:jobID   /ivec:param_set  /ivec:contents /cmd SANE does not send the VendorCmd. Do you think incorporating the missing command sequence could solve the issue? I do not want to damage my MG7550 with wrong commands, that's why I am reluctant to experiment with code-changes. Many thanks for your help Martin Am Sonntag, 11. Januar 2015, 14.52:06 schrieb Troels Thomsen: Martin, ad 1) I'm sorry I have no understanding of the protocol what so ever, and have spent max ½ hour in the code, to see what the patches I was sent, did. ad 2) I agree , this IS strange ... ad 3) I agree , this IS strange ... ad 4) Frankly, you have so many strange phenomenons going on, so ... you could try (not that this a satisfactory solution at all...) At this point, I think I would try to test it on another computer, to see if all these really strange phenomenons (e.g. 'enabling Ethernet on the device, makes usb scanning work' ) somehow is related to hardware or the Linux installation. Just to make sure Sorry, its not much help. /Troels 2015
Re: [sane-devel] Error: Canon Pixma MG7550 hangs
Troels I don't have access to another computer. But I have installed OpenSUSE 13.2 and the result is the same as on 13.1. I did not (yet) test with short delays between the commands, but I compared the communication of the Canon software scangear on Windows with the one of SANE: At start ScanGear sends the following (linebreaks added by me): ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; xmlns:vcn=http://www.canon.com/ns/cmd/2008/07/canon/; ivec:contentsivec:operationVendorCmd/ivec:operation ivec:param_set servicetype=scan ivec:jobID /ivec:jobID vcn:ijoperationModeShift/vcn:ijoperation vcn:ijmode1/vcn:ijmode /ivec:param_set /ivec:contents /cmd response: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; xmlns:vcn=http://www.canon.com/ns/cmd/2008/07/canon/; ivec:contents ivec:operationVendorCmdResponse/ivec:operation ivec:param_set servicetype=scan ivec:responseOK/ivec:response ivec:response_detail/ vcn:ijoperationModeShiftResponse/vcn:ijoperation vcn:ijresponseOK/vcn:ijresponse vcn:ijresponse_detail/ /ivec:param_set /ivec:contents /cmd ScanGear starts a scan with the following command sequece: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; ivec:contents ivec:operationStartJob/ivec:operation ivec:param_set servicetype=scan ivec:jobID0001/ivec:jobID ivec:bidi1/ivec:bidi /ivec:param_set /ivec:contents /cmd response: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; ivec:contents ivec:operationStartJobResponse/ivec:operation ivec:param_set servicetype=scan ivec:responseOK/ivec:response ivec:response_detail/ ivec:jobID0001/ivec:jobID /ivec:param_set /ivec:contents /cmd command: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; xmlns:vcn=http://www.canon.com/ns/cmd/2008/07/canon/; ivec:contents ivec:operationVendorCmd/ivec:operation ivec:param_set servicetype=scan ivec:jobID0001/ivec:jobID vcn:ijoperationModeShift/vcn:ijoperation vcn:ijmode1/vcn:ijmode /ivec:param_set /ivec:contents /cmd response: some data command: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; ivec:contents ivec:operationEndJob/ivec:operation ivec:param_set servicetype=scan ivec:jobID0001/ivec:jobID /ivec:param_set /ivec:contents /cmd response: ?xml version=1.0 encoding=utf-8 ? cmd xmlns:ivec=http://www.canon.com/ns/cmd/2008/07/common/; ivec:contents ivec:operationEndJobResponse/ivec:operation ivec:param_set servicetype=scan ivec:responseOK/ivec:response ivec:response_detail/ ivec:jobID0001/ivec:jobID /ivec:param_set /ivec:contents /cmd SANE does not send the VendorCmd. Do you think incorporating the missing command sequence could solve the issue? I do not want to damage my MG7550 with wrong commands, that's why I am reluctant to experiment with code-changes. Many thanks for your help Martin Am Sonntag, 11. Januar 2015, 14.52:06 schrieb Troels Thomsen: Martin, ad 1) I'm sorry I have no understanding of the protocol what so ever, and have spent max ½ hour in the code, to see what the patches I was sent, did. ad 2) I agree , this IS strange ... ad 3) I agree , this IS strange ... ad 4) Frankly, you have so many strange phenomenons going on, so ... you could try (not that this a satisfactory solution at all...) At this point, I think I would try to test it on another computer, to see if all these really strange phenomenons (e.g. 'enabling Ethernet on the device, makes usb scanning work' ) somehow is related to hardware or the Linux installation. Just to make sure Sorry, its not much help. /Troels 2015-01-07 23:26 GMT+01:00 Martin martin...@intergga.ch: Troels I agree with you, we have to be careful on the test methodology. My knowledge in c is limited since I wrote my last c-program about 20 years ago. But I could try. But before trying to modify the source code I have some questions: 1) Did you analyze the USB-calls of the Canon-software on windows and compare them to the SANE-sequence? What is the meaning of the first sequece 55 53 42 43 F0 36 04 0B...? 2) What is the difference between scanimage and xsane? Is it only the timing? 3) What is the difference between xsane and the gimp plugin? Is it only the timing? Why does the gimp plugin only work after xsane? 4) Would it be worth while to make a few tests with the printer mode, i.e. to try to start xsane after printing? Martin If the scanner does not work on a USB port it is quite unlikely to work over the network: the bjnp network code just carries the USB
[sane-devel] Out of memory (Brother MFC-9465CDN)
[repost, in dire hope of someone who can help…] Hey there, I have a problem with a Brother MFC-9465CDN that I access through a scanner server running saned. The problem is that most scans fail with an out of memory message. However, I can scan fine when using scanimage on the server directly, the problem is when going through saned. This machine does not have a whole lot of ooomph, but 1Gb of RAM should be enough. In any case, there is still free memory (according to top) at the time of the error. Is this a problem with saned or the machine it's running on, or a problem with the scanner? To me, it seems that the out-of-memory message comes from the scanner, but maybe I am misinterpreting the debug output (see below). Thanks for any help! Here is the client output: % scanimage -d 'net:scanner.is:brother4:net1;dev0' -p --mode 'Black White' --resolution 300 --source 'Automatic Document Feeder(left aligned)' | /tmp/s scanimage: rounded value of br-x from 215.9 to 215.88 scanimage: rounded value of br-y from 355.6 to 355.567 scanimage: sane_read: Out of memory Here is the server debug output: [saned] start_scan: trying to bind data port 0 [saned] start_scan: using port 36052 for data [saned] process_request: waiting for data connection [saned] process_request: access to data port from 2001:a60:f10a:0:224:d7ff:fe04:c82c [saned] do_scan: start [saned] do_scan: trying to read 8188 bytes from scanner [saned] do_scan: read 8188 bytes from scanner [saned] do_scan: processing RPC request on fd 4 [saned] process_request: waiting for request [saned] process_request: got request 6 [saned] do_scan: trying to write 8192 bytes to client [saned] do_scan: wrote 8192 bytes to client [saned] do_scan: trying to read 8188 bytes from scanner [saned] do_scan: read 8188 bytes from scanner […] [saned] do_scan: trying to write 7976 bytes to client [saned] do_scan: wrote 7976 bytes to client [saned] do_scan: trying to read 212 bytes from scanner [saned] do_scan: read 0 bytes from scanner [saned] do_scan: status = `Out of memory' [saned] do_scan: statuscode `Out of memory' was added to buffer [saned] do_scan: trying to write 9 bytes to client [saned] do_scan: wrote 9 bytes to client [saned] do_scan: done, status=Out of memory -- .''`. martin f. krafft madduck@d.o @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems the stripes on the highway began to unreel beneath her in a dizzying blur as if all those grains of sand had lost their bearings and were falling all over each other just trying to get out of the way to make room for the next moment, or instant, or tick of the clock -- mc 900 ft jesus (http://stuff.madduck.net/pub/misc/fun/newmoon.txt) -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] scanimage --resolution 200; the resolution seems to be ignored
Hi, this was it! Now the result is ok, thank you very much! Matten -Ursprüngliche Nachricht- Von: sane-devel [mailto:sane-devel-bounces+martimc2000=freenet...@lists.alioth.debian.org] Im Auftrag von JF Straeten Gesendet: Mittwoch, 28. Januar 2015 20:07 An: sane-devel@lists.alioth.debian.org Betreff: Re: [sane-devel] scanimage --resolution 200; the resolution seems to be ignored Martin, On Wed, Jan 28, 2015 at 07:55:27PM +0100, Martin wrote: [...] scanimage --format=tiff --resolution 200 --mode Color --source ADF $scanfile creates a tiff file with 75 dpi Everytime I use --source ADF, the result is 75 dpi, although the resolution is set to something else. Could you retry with resolution *after* the source ? scanimage --format=tiff --mode Color --source ADF --resolution 200 Hih, -- JFS. -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] scanimage --resolution 200; the resolution seems to be ignored
Hello, I am using scanimage, to obtain scans from my hp officejet 6700 from the commandline resp. script. Everything works fine by scanning from the Flatbed. If scanning using ADF, for some reason the resolution will be ignored. scanimage --format=tiff --resolution=200 --mode Color $scanfile creates a tiff with 200 dpi scanimage --format=tiff --resolution 200 --mode Color --source ADF $scanfile creates a tiff file with 75 dpi Everytime I use --source ADF, the result is 75 dpi, although the resolution is set to something else. scanimage (sane-backends) 1.0.22; backend version 1.0.22 raspbian os runs on raspberrypi b+ allinone scanner hp officejet 6700 Best regards, Matten -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Canon MX-924
Hi, I have recently purchased one of these printers. I see that the entry in the supported devices list requests testers. I am willing to help with any required testing. I currently use the Canon supplied drivers for both scanning and printing. The printer has the capability of connecting via USB, wired and wireless and I have the facilities of connecting over all 3 connection types, should this be required. Cheers Martin -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Error: Canon Pixma MG7550 hangs
Troels I agree with you, we have to be careful on the test methodology. My knowledge in c is limited since I wrote my last c-program about 20 years ago. But I could try. But before trying to modify the source code I have some questions: 1) Did you analyze the USB-calls of the Canon-software on windows and compare them to the SANE-sequence? What is the meaning of the first sequece 55 53 42 43 F0 36 04 0B...? 2) What is the difference between scanimage and xsane? Is it only the timing? 3) What is the difference between xsane and the gimp plugin? Is it only the timing? Why does the gimp plugin only work after xsane? 4) Would it be worth while to make a few tests with the printer mode, i.e. to try to start xsane after printing? Martin If the scanner does not work on a USB port it is quite unlikely to work over the network: the bjnp network code just carries the USB exchange over IP. I mostly agree, though Rolf asks specifically for the USB trace, because (as I understood) it differs slightly from the IP traces I had already submitted. (fix usb first , then patch it for IP, if need be) One advice: Be very paranoid on your test methodology. I looked stupid a couple of times (sorry Rolf!), because I was fooled by the USB interface and/or the Canon firmware. When testing a new patch, I tried some settings in random (DPI , colour/black-n-white etc) and reported the success/failures. BUT the thing is, that the Canon MF8230 firmware can go into bad-mode, when it has received some strange commands, and the following scans might work slightly strange for that reason. I was even fooled by the phenomenon, that scanning a 1 by 1 cm square works, but scanning the whole A4 didn't. (Well ... there WERE some differences between what worked through USB and IP at this point in time. I'm guessing it was something timing-critical, but I never dissected that last patch from Rolf which fixed it) So I started rebooting the scanner whenever I was in doubt. (disconnect/connect the USB interface plus move Cannon unit from to printer mode and back to scanner mode was normally enough) So what do we do? / What is status? Since scanning CAN work , one could argue the back-end DOES send all the necessary+correct commands to the printer. If timing is the critical parameter (backed by the fact that something as stupid as enabling IP on the printer-side, suddenly makes it work now and then), maybe we should try to insert an ugly time-delay before every USB write? If that changes anything to the better, we can start to hunt down where it is really necessary, and hopefully find a nicer approach afterwards? Martin, are you comfortable with pulling the code out of the GIT repository, compile , install and experiment with inserting delays? I think there is something called SANE interface USB sanei_usb.c/h. That was maybe a place to start. Louis, what is the odds of success for this approach? :-) /Troels 2015-01-03 20:43 GMT+01:00 Martin martin...@intergga.ch: Am Samstag, 3. Januar 2015, 11.16:10 schrieb Louis Lagendijk: On Fri, 2015-01-02 at 22:59 +0100, Martin wrote: Hi Troels *Is it USB3 (on the computer)? no, it is USB2 *Do you have access to another computer, where you can try it - Does it work excactly the same strange way ... ? No,I don't have access to another computer. But I have also Windows 7 installed. With Windows 7 and the Canon-software it works OK. *Does unit have ethernet connection / can you try that way? Yes. With the ethernet connection the printer works. Thus the IP-address below is correct. But I cannot access the scanner. xsane pixma:MG7500_192.168.0.3 results in the error message illegal argument. Same thing with scanimage --help -d bnjp://192.168.0.3:8612 Hi Martin If the scanner does not work on a USB port it is quite unlikely to work over the network: the bjnp network code just carries the USB exchange over IP. Anyhow, you can find the name with scanimage -L (but make sure that port 8612 is not blocked by a firewall (see the man-page for sane-pixma in the latest sources from GIT. you need to enable port 8612 for both incoming and outgoing traffic. Louis Hi Louis The necessary ports on the firewall are open, yet scanimage -L does not find the scanner. But this lead to another discovery: I enabled LAN on the MG7550. And although the unit is connected via USB 2 xsane sometimes works?! But with LAN disabled xsane never works without prior scanimage -T. And once xsane or scanimage -T failed all succeeding calls fail until the scanner is switched off and on again. Log of xsane working: [sanei_debug] Setting debug level of pixma to 21. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.13 [pixma] pixma_collect_devices
[sane-devel] Error: Canon Pixma MG7550 hangs
Hi, Today I built Sane 1.0.25 from the development repository. But a software that tries to use the pixma backend hangs. I tried scanimage --format tiff -x 10 -y10 /dev/null, xsane and Gimp. The scanner works if the first command after power-up is scanimage -T. After that the mentioned programs work fine. Could anyone please look into this problem? Martin -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Canon Pixma MX525
Hi, I' got the same Pixma, but I'd like to have it with the LAN to scan. It seems to work with the new version, using ubuntu I use sane 1.0.25 from the Rolf Bensch https://launchpad.net/~rolfbensch/+archive/sane-git[1] I also find the scangearmp a little bit bad, I'm not excited from its results. For adf it just makes gray pdf files from white paper, and its a bit bad to work with that further. scanadf works, but when it comes to an end (no more paper in the feeder) it comes with an error. Then the driver or scanner or something else is in a bad state so I cannot use the scanner anymore - but a restart of my computer seems to solve the problem. Ok, I don't want to restart the computer for every scan. If I can help you (have also little programming experience) I would do that. Martin Trygve Flathen writes: Hi I am now the owner of a Canon Pixma MX525, and I see that this is listed as untested in the supported devices list. I bought it specifically for its duplex ADF scanner and the impression that they support Linux after seeing the scangearmp software offered by Canon. However, while scangearmp does allow you to scan in Linux, the program is buggy and very mouse-based and manual in use. I need scanning to work from various programs/script in a more automated manner. I am a programmer and would like to help getting it supported by SANE. I will provide some initial info below, and hope the SANE project can point me in a useful direction for further work. -Trygve The scanner is connected to a Mint 16 system via usb and network. ScanGear MP v2.10 for Linux: (select software, linux) http://www.canon.co.uk/Support/Consumer_Products/products/Fax__Multifunctionals/InkJet/PIXMA_MX_series/MX525.aspx Another owner: http://lists.alioth.debian.org/pipermail/sane-devel/2014-January/032018.html See http://flathen.net/ext/sane/info1.html for output from: lsusb lsusb -s 001:003 -v -v ls -l /dev/bus/usb/001/003 sane-find-scanner -v -v /dev/bus/usb/001/003 nmap -A 10.0.124.76 export SANE_DEBUG_PIXMA=21 scanimage -L lsmod|grep scanner dpkg --get-selections|grep sane dpkg --get-selections|grep libusb scanimage --version sane-find-scanner -v -v -- Mag. Martin Kaffanke http://www.kaffanke.at +43 650 4514224
[sane-devel] Updated Dutch translations
Hi, See attachment. I've used git source (09/23) for these translations. Can someone commit the update? Hope I'm not too late. Thanks, Martin Kho -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130930/b69c240c/attachment-0001.html -- next part -- A non-text attachment was scrubbed... Name: nl.po.gz Type: application/gzip Size: 32184 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130930/b69c240c/attachment-0001.bin
[sane-devel] Canon ImageFormula P-208
Hi Allan, I just got sane-backends from the git repository and I couldn't find the P-150 code. Has this been committed? Regards. -- Original Message -- From: Simon Martin smar...@milliways.cl To: sane-devel at lists.alioth.debian.org Sent: 25/07/2013 10:02:34 Subject: Re[2]: [sane-devel] Canon ImageFormula P-208 Fantastic news. Thanks. Are you getting scans from the sheet feeder and the small document scanner as well? If so, can I have a version to test (knowing that the colours are not quite right) as I need to integrate this. Regards. -- Original Message -- From: m. allan noah kitno455 at gmail.com To: Simon Martin smartin at milliways.cl Cc: sane-devel at lists.alioth.debian.org Sent: 25/07/2013 09:43:20 Subject: Re: [sane-devel] Canon ImageFormula P-208 We are getting scans from both the P-215 and the P-208, but they are uncalibrated, so the colors are not quite right. These two scanners seem to use a different calibration format from other machines, so it will take some time to reverse engineer that. allan On Thu, Jul 25, 2013 at 9:36 AM, Simon Martin smartin at milliways.cl wrote: Hi Allan, Any news on this? TIA. -- Original Message -- From: m. allan noah kitno455 at gmail.com To: Simon Martin smartin at milliways.cl Cc: sane-devel at lists.alioth.debian.org Sent: 07/07/2013 17:02:29 Subject: Re: [sane-devel] Canon ImageFormula P-208 Gerhard Pfeffer and I are working on this as we speak. Sometimes we hit roadblocks, but I think a week or two and we should have it working. allan On Sun, Jul 7, 2013 at 4:23 PM, Simon Martin smartin at milliways.cl wrote: Hi Allan, Sorry I should have been clearer. I am testing on a P-215. Any idea how soon soon is? If you need any help I would love to be of assistance. I'm new to sane, but I've been working in C/C++ for the last 28 years, and have been working on Linux for the last 15. Regards. -- View this message in context: http://sane.10972.n7.nabble.com/Canon-ImageFormula-P-208-tp17581p17757.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130728/e3215981/attachment.html -- next part -- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2136 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130728/e3215981/attachment.bin
[sane-devel] Canon ImageFormula P-208
Hi Allan, Any news on this? TIA. -- Original Message -- From: m. allan noah kitno...@gmail.com To: Simon Martin smartin at milliways.cl Cc: sane-devel at lists.alioth.debian.org Sent: 07/07/2013 17:02:29 Subject: Re: [sane-devel] Canon ImageFormula P-208 Gerhard Pfeffer and I are working on this as we speak. Sometimes we hit roadblocks, but I think a week or two and we should have it working. allan On Sun, Jul 7, 2013 at 4:23 PM, Simon Martin smartin at milliways.cl wrote: Hi Allan, Sorry I should have been clearer. I am testing on a P-215. Any idea how soon soon is? If you need any help I would love to be of assistance. I'm new to sane, but I've been working in C/C++ for the last 28 years, and have been working on Linux for the last 15. Regards. -- View this message in context: http://sane.10972.n7.nabble.com/Canon-ImageFormula-P-208-tp17581p17757.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130725/a0dfe1e3/attachment.html -- next part -- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2136 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130725/a0dfe1e3/attachment.bin
[sane-devel] Canon ImageFormula P-208
Fantastic news. Thanks. Are you getting scans from the sheet feeder and the small document scanner as well? If so, can I have a version to test (knowing that the colours are not quite right) as I need to integrate this. Regards. -- Original Message -- From: m. allan noah kitno...@gmail.com To: Simon Martin smartin at milliways.cl Cc: sane-devel at lists.alioth.debian.org Sent: 25/07/2013 09:43:20 Subject: Re: [sane-devel] Canon ImageFormula P-208 We are getting scans from both the P-215 and the P-208, but they are uncalibrated, so the colors are not quite right. These two scanners seem to use a different calibration format from other machines, so it will take some time to reverse engineer that. allan On Thu, Jul 25, 2013 at 9:36 AM, Simon Martin smartin at milliways.cl wrote: Hi Allan, Any news on this? TIA. -- Original Message -- From: m. allan noah kitno455 at gmail.com To: Simon Martin smartin at milliways.cl Cc: sane-devel at lists.alioth.debian.org Sent: 07/07/2013 17:02:29 Subject: Re: [sane-devel] Canon ImageFormula P-208 Gerhard Pfeffer and I are working on this as we speak. Sometimes we hit roadblocks, but I think a week or two and we should have it working. allan On Sun, Jul 7, 2013 at 4:23 PM, Simon Martin smartin at milliways.cl wrote: Hi Allan, Sorry I should have been clearer. I am testing on a P-215. Any idea how soon soon is? If you need any help I would love to be of assistance. I'm new to sane, but I've been working in C/C++ for the last 28 years, and have been working on Linux for the last 15. Regards. -- View this message in context: http://sane.10972.n7.nabble.com/Canon-ImageFormula-P-208-tp17581p17757.html Sent from the SANE - Dev mailing list archive at Nabble.com. -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130725/65d6ab59/attachment-0001.html -- next part -- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2136 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130725/65d6ab59/attachment-0001.bin
[sane-devel] Canon ImageFormula P-208
Hi, I'm currently looking at this. The P-150 driver off of the Canon website works OK for the main sheet feeder as long as you set the Auto switch to off, however there are a few things that don't work: 1.- The front card reader slot, 2.- Simultaneous anverse and reverse scanning. I am trying to fix this, however I can't find any decent documentation on the sane backend which is making life difficult. Is there any documentation for this or is it just code browsing? Regards. -- View this message in context: http://sane.10972.n7.nabble.com/Canon-ImageFormula-P-208-tp17581p17755.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] Canon ImageFormula P-208
Hi Allan, Sorry I should have been clearer. I am testing on a P-215. Any idea how soon soon is? If you need any help I would love to be of assistance. I'm new to sane, but I've been working in C/C++ for the last 28 years, and have been working on Linux for the last 15. Regards. -- View this message in context: http://sane.10972.n7.nabble.com/Canon-ImageFormula-P-208-tp17581p17757.html Sent from the SANE - Dev mailing list archive at Nabble.com.
[sane-devel] Out of memory (Brother MFC-9465CDN)
[repost, in dire hope of someone who can help?] Hey there, I have a problem with a Brother MFC-9465CDN that I access through a scanner server running saned. The problem is that most scans fail with an out of memory message. However, I can scan fine when using scanimage on the server directly, the problem is when going through saned. This machine does not have a whole lot of ooomph, but 1Gb of RAM should be enough. In any case, there is still free memory (according to top) at the time of the error. Is this a problem with saned or the machine it's running on, or a problem with the scanner? To me, it seems that the out-of-memory message comes from the scanner, but maybe I am misinterpreting the debug output (see below). Thanks for any help! Here is the client output: % scanimage -d 'net:scanner.is:brother4:net1;dev0' -p --mode 'Black White' --resolution 300 --source 'Automatic Document Feeder(left aligned)' | /tmp/s scanimage: rounded value of br-x from 215.9 to 215.88 scanimage: rounded value of br-y from 355.6 to 355.567 scanimage: sane_read: Out of memory Here is the server debug output: [saned] start_scan: trying to bind data port 0 [saned] start_scan: using port 36052 for data [saned] process_request: waiting for data connection [saned] process_request: access to data port from 2001:a60:f10a:0:224:d7ff:fe04:c82c [saned] do_scan: start [saned] do_scan: trying to read 8188 bytes from scanner [saned] do_scan: read 8188 bytes from scanner [saned] do_scan: processing RPC request on fd 4 [saned] process_request: waiting for request [saned] process_request: got request 6 [saned] do_scan: trying to write 8192 bytes to client [saned] do_scan: wrote 8192 bytes to client [saned] do_scan: trying to read 8188 bytes from scanner [saned] do_scan: read 8188 bytes from scanner [?] [saned] do_scan: trying to write 7976 bytes to client [saned] do_scan: wrote 7976 bytes to client [saned] do_scan: trying to read 212 bytes from scanner [saned] do_scan: read 0 bytes from scanner [saned] do_scan: status = `Out of memory' [saned] do_scan: statuscode `Out of memory' was added to buffer [saned] do_scan: trying to write 9 bytes to client [saned] do_scan: wrote 9 bytes to client [saned] do_scan: done, status=Out of memory -- .''`. martin f. krafft madduck at d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems this message represents the official view of the voices in my head. -- next part -- A non-text attachment was scrubbed... Name: digital_signature_gpg.asc Type: application/pgp-signature Size: 1124 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130423/5d2ca8c4/attachment-0001.pgp
[sane-devel] Out of memory (Brother MFC-9465CDN)
also sprach Upscope upscope at nwi.net [2013.03.27.1915 +0100]:
Also you mentioned you had to put an entery in 56-sane-backends. I have
no entry there but I did have to put one in 55-libsane.rules. Their
instructions dropped adding ATTR{idProduct}== part. Once I added it
things worked fine.
I never mentioned 56-sane-backends and I am also not using USB but
network access.
Please post if you find solution. Oh have you tried Brothers email
Linux support. They were helpful when I first got my printer and
there were a couple of bugs in the driver. Don't have the link
handy, still on my 12.2 side.
I am pretty sure this is a problem with saned, not with Brother?
--
.''`. martin f. krafft madduck at d.o Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
fashions have done more harm than revolutions.
-- victor hugo
-- next part --
A non-text attachment was scrubbed...
Name: digital_signature_gpg.asc
Type: application/pgp-signature
Size: 1124 bytes
Desc: Digital signature (see
http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
URL:
http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130330/4b97a782/attachment.pgp
[sane-devel] Out of memory (Brother MFC-9465CDN)
Also using the brscan- skey works from command line. You don't say what OS your on but make sure? you have the correct driver for your unit. I am running Debian stable and I am running the right drivers from the brother.com website. As I said, scanning works. What does not work is relaying via saned, and I want to figure out whether that's the printer's fault or the driver. Btw, brscan-skey does not really work for me, if I run % brscan-skey -l mfc9465cdn: brother4:net1;dev0 : 192.168.17.30 Not responded I am told that it does not respond. Yet, pings work, of course. -- .''`. martin f. krafft madduck at d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems i'd give my right arm to be ambidextrous. -- next part -- A non-text attachment was scrubbed... Name: digital_signature_gpg.asc Type: application/pgp-signature Size: 1124 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130327/f9099e8b/attachment.pgp
[sane-devel] Out of memory (Brother MFC-9465CDN)
Hey there, I have a problem with a Brother MFC-9465CDN that I access through a scanner server running saned. The problem is that most scans fail with an out of memory message. However, I can scan fine when using scanimage on the server directly, the problem is when going through saned. This machine does not have a whole lot of ooomph, but 1Gb of RAM should be enough. In any case, there is still free memory (according to top) at the time of the error. Is this a problem with saned or the machine it's running on, or a problem with the scanner? To me, it seems that the out-of-memory message comes from the scanner, but maybe I am misinterpreting the debug output (see below). Thanks for any help! Here is the client output: % scanimage -d 'net:scanner.is:brother4:net1;dev0' -p --mode 'Black White' --resolution 300 --source 'Automatic Document Feeder(left aligned)' | /tmp/s scanimage: rounded value of br-x from 215.9 to 215.88 scanimage: rounded value of br-y from 355.6 to 355.567 scanimage: sane_read: Out of memory Here is the server debug output: [saned] start_scan: trying to bind data port 0 [saned] start_scan: using port 36052 for data [saned] process_request: waiting for data connection [saned] process_request: access to data port from 2001:a60:f10a:0:224:d7ff:fe04:c82c [saned] do_scan: start [saned] do_scan: trying to read 8188 bytes from scanner [saned] do_scan: read 8188 bytes from scanner [saned] do_scan: processing RPC request on fd 4 [saned] process_request: waiting for request [saned] process_request: got request 6 [saned] do_scan: trying to write 8192 bytes to client [saned] do_scan: wrote 8192 bytes to client [saned] do_scan: trying to read 8188 bytes from scanner [saned] do_scan: read 8188 bytes from scanner [?] [saned] do_scan: trying to write 7976 bytes to client [saned] do_scan: wrote 7976 bytes to client [saned] do_scan: trying to read 212 bytes from scanner [saned] do_scan: read 0 bytes from scanner [saned] do_scan: status = `Out of memory' [saned] do_scan: statuscode `Out of memory' was added to buffer [saned] do_scan: trying to write 9 bytes to client [saned] do_scan: wrote 9 bytes to client [saned] do_scan: done, status=Out of memory -- .''`. martin f. krafft madduck at d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems the condition of perfection is idleness. the aim of perfection is youth. -- oscar wilde -- next part -- A non-text attachment was scrubbed... Name: digital_signature_gpg.asc Type: application/pgp-signature Size: 1124 bytes Desc: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130326/9197c5e2/attachment.pgp
[sane-devel] Canon DR-2580C only low resolutions
Hi, I (linux-newbie) want to use sane (libsane 1.0.23-0ubuntu1) under Ubuntu 12.10 to scan with a Canon DR-2580C scanner. After installation sane displayed invalid argument every time I tried to scan. Via try and error I found out that I'm able to scan if I set resolution to 240dpi, 300dpi and above gives the invalid-argument-error (scanner is able to scan up to 600dpi). This happens with gscan2pdf als well als xsane. With gscan2pdf (libsane perl frontend) there is another issue: the scan result is always the same, no matter on how I change brightness and contrast settings. With xsane it seems to me that only the settings on the main window have any effekt, but not the settings in standard options (sometimes changes in standard options lead to completely black scans until new start of xsane, though). Any hints what's going on (or going wrong) here? Any help would be greatly appreciated! Martin
[sane-devel] scanning for archival and OCR
On Tue, Jan 22, 2013 at 12:34:05PM -0500, David H. Durgee wrote: I am trying to determine how best to scan and save these documents. I have found the following process to be useful: Scanner input, jpg (or pdf) | v tidy up image using 'unpapered' | v convert to grayscale via ppmtopgm - pamtotiff | v OCR using tesseract Tesseract can embed the OCR in the PDF (search for tesseract hocr), too. This is a makefile I use to automate that process, starting from a PDF (image only) generated by my scanner: http://www.martindengler.com/proj/scan-post-process-Makefile ...like so: make -f scan-post-process-Makefile $(basename input.pdf .pdf)-processed Tesseract isn't perfect, but it's pretty good. Dave Martin -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20130122/f38c93f3/attachment.pgp
[sane-devel] MX712 and Linux
On 11/01/12 18:17, Gernot Hassenpflug wrote: On Fri, Nov 2, 2012 at 4:28 AM, Kevin Martin ktmdms at gmail.com mailto:ktmdms at gmail.com wrote: Recently purchased a Canon Pixma MX712 and have the following working: Hello Kevin, /../ ? scanning not using the adf from gimp using xsane scanning from adf for first page only It looks like you are using the network connection. To debug the pixma driver, you should first try with a direct USB connection. Also, what is the version of SANE and the pixma libraries you are using? Preferebly with be 1.0.23 or the git CVS code. Regards, Gernot Hassenpflug These are my sane related rpms: sane-backends-drivers-cameras-1.0.23-4.fc19.x86_64 sane-backends-1.0.23-4.fc19.x86_64 sane-backends-drivers-scanners-1.0.23-4.fc19.x86_64 sane-frontends-1.0.14-15.fc18.x86_64 sane-backends-libs-1.0.23-4.fc19.x86_64 xsane-gimp-0.998-12.fc19.x86_64 xsane-common-0.998-12.fc19.x86_64 sane-backends-devel-1.0.23-4.fc19.x86_64 The pixma libraries were downloaded from the Canon Europe site since the Canon USA site didn't have Linux files for the MX712 (I downloaded the files for the MX715 (cnijfilter-source-3.70) and had to do a fair amount of changing of source code to get them to compile on the latest Fedorashould I post the diff's for the changes for that here do you think?). As for debugging via USB, I'm not sure now to go about doing that. I can easily tcpdump and windump from my Linux and Windows boxes and compare the conversations that go on between the scanner and the two machines, I can strace gimp while I'm trying this or strace the scanning pid and see what it's getting (not sure how to do that on Windows) but debugging via USB I'm not sure how to do exactly. Thanks. Kevin
[sane-devel] MX712 and Linux
Recently purchased a Canon Pixma MX712 and have the following working: printing under cups scanning not using the adf from gimp using xsane scanning from adf for first page only When I try to scan multiple pages from the 712 using gimp/xsane the first page scans and then I see: [pixma] bjnp_recv_header: could not read response header (select timed out): Success! [pixma] Could not read response to command! and the MX712 forces me to clear the adf using the button. Subsequent attempts to scan result in the error: [pixma] bjnp_open_tcp: Can not connect to scanner: Connection refused I have tested the following to see if I can somehow reset the connection in the Pixma: power off the pixma for 30+ seconds - no joy, still can't scan scan from Windows using the adf - results in a perfect scan into Windows but no reset of the Pixma related to my Linux machine. power off and unplug the Pixma for 20+ seconds - allows me to scan again. Until I do this I can't reconnect to the scanner *at all* from gimp using xsane (not even to scan from the flatbed). I'm not sure now to capture log information about this as I've tried setting the following variables and doing a redirect with no success: SANE_DEBUG_PIXMA=21 SANE_DEBUG=255 PIXMA_EXPERIMENT=1 SANE_DEBUG_UMAX1220U=255 Am glad to assist in getting this working if somebody can give me a lead as to how to do so. -- Regards, Kevin Martin
[sane-devel] sane-backends vs backend version missmatch
Sorry if this is not exactly a dev-question, but it seems to me that with Ubuntu Precise Pangolin it is all but easy to do a proper install of SANE from source. I noticed another question that had similar version mismatch which might be at the root of that problem as well. If I run on a fresh install of Ubuntu with compiled SANE source from the git I get: $ scanimage -V scanimage (sane-backends) 1.0.24git; backend version 1.0.22 (I basically followed the instructions on http://ubuntuportal.com/2012/02/how-to-get-an-canon-canoscan-lide-100-scanner-to-work-in-ubuntu-11-10linux-mint-12.html since I didn't find any other information making sure that sane was not installed prior to installation.) My primary interest is the epson2-backend. In 1.0.22 it offer the wrong TPU settings for Epson V700 (which TPU2-mode wasn't supported in 1.0.22). Since it shows 1.0.22 behaviour, it implies that the epson2-backend comes from 1.0.22 and not 1.0.24. If I install SANE with prefix to a local folder and run that version of scanimage it still produces the mismatch. However, on another computer where I installed a custom 1.0.22 build of SANE last winter and since have upgraded to Ubuntu 12.04, I can install the same SANE-git locally and have it correctly match backends: $ ./SANE/bin/scanimage -V scanimage (sane-backends) 1.0.24git; backend version 1.0.24 $ scanimage -V scanimage (sane-backends) 1.0.22; backend version 1.0.22 On this computer the 1.0.24 works correctly in finding TPU2 on Epson V700. So what am I missing/doing wrong? /Martin Zackrisson -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20121015/4d5c1831/attachment.html
[sane-devel] Updated Dutch translation
Hi, See attachment. I've used the git-source pulled August 14 for these translations. Can someone commit the update? Thanks, Martin Kho -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20120818/2a0cfd37/attachment-0001.html -- next part -- A non-text attachment was scrubbed... Name: nl.po.tar.gz Type: application/x-compressed-tar Size: 31930 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20120818/2a0cfd37/attachment-0001.bin
[sane-devel] [PATCH] Fix epson2 driver problem with color shuffling using an Epson Perfection 610
# HG changeset patch
# User Martin Kr?ger martin.krueger at gmx.com
# Date 1340227497 -7200
# Node ID d0e710afdc035dfb05f2b9e8a6898ca44ce6a42a
# Parent 99d490b6ca089eb4240793af8f19460748b94f3e
Fix epson2 driver problem with color shuffling using an Epson Perfection 610
Using xsane to aquire an preview-scan over the full plane in color mode
fails. If you aquire an preview in bw/grayscale-Mode or over a part of
the plain works well. The extra lines added dont fit in the scan-plane.
The scanner fails to start with an invalid argument.
This is a port of the corresponding check in the epson driver:
No color shuffling if not enough space on the plane.
diff -r 99d490b6ca08 -r d0e710afdc03 backend/epson2-ops.c
--- a/backend/epson2-ops.c Tue Jun 19 23:58:44 2012 +
+++ b/backend/epson2-ops.c Wed Jun 20 23:24:57 2012 +0200
@@ -1212,6 +1212,15 @@
unsigned int lines = s-params.lines + (2 * s-line_distance);
int top = s-top - (1 * s-line_distance);
+/*
+ * If (top + s-params.lines) is larger than the max scan
area, reset
+ * the number of scan lines:
+ */
+if (SANE_UNFIX (s-val[OPT_BR_Y].w) / 25.4 *s-
val[OPT_RESOLUTION].w ( lines + top)){
+ top=s-top;
+ lines=s-params.lines;
+}
+
if (top 0)
top = 0;
[sane-devel] Completing epson backend deprecation
On 06/13/2012 01:30 PM, sane-devel-request at lists.alioth.debian.org wrote: There is a solution now i en epson2 backend that gives you 2 TPU with different size. It is working for the epson 4990 (GT-X800) and for GT-X900, which should bee both v700 and v750 (I am not totally sure). I have only tested 4990 and I think there is no confirmed test for the GT-X900 - has any one a v700 and v750 please test it, but remember to use the git version of sane, I don't think it is in any released version. I don't have the possibility of verifying from the git now, but I think this refers back to my issues with the TPU2 on v700. The solution got committed according to http://lists.alioth.debian.org/pipermail/sane-devel/2011-December/029234.html and I can verify that using my own build (from which the diff is produced) works on v700. -- Martin Zackrisson Dept. Chemistry Molecular Biologi University of Gothenburg Medecinaregatan 9e SE-413 90 G?teborg Sweden Phone +46 (0)31 786 3753
[sane-devel] HP G4010/G4050 listed as unsupported and supported
The web site lists the HP G4010/G4050 both as unsupported as well as supported by the genesys drive. Remove them from the list of unsupported scanners. diff --git a/doc/descriptions/unsupported.desc b/doc/descriptions/unsupported.desc index 51dfabe..fcce4ae 100644 --- a/doc/descriptions/unsupported.desc +++ b/doc/descriptions/unsupported.desc @@ -863,20 +863,6 @@ :comment Probably not supported. See link for details. :status :unsupported -:model ScanJet G4010 -:url /unsupported/hp-g4000.html -:interface USB -:usbid 0x03f0 0x4505 -:comment Probably not supported. See link for details. -:status :unsupported - -:model ScanJet G4050 -:url /unsupported/hp-g4050.html -:interface USB -:usbid 0x03f0 0x4605 -:comment gl843 scanner, support is currently being work on in the genesys backend -:status :unsupported - ; :mfg IBM -- Martin Michlmayr http://www.cyrius.com/
[sane-devel] Identifying identical scanners dynamically turned on and off
On 03/23/2012 12:37 AM, Olaf Meeuwissen wrote: These days the USB devices stay at the same place below /sys/ even when power cycled. Only when replugging to a *different* USB port will this location change. I'm not sure what happens when you reboot. Assuming that you know which scanner shows up where in /sys/, you can then use the busnum and devnum files to construct the device names that the epson2 backend groks. So with $ cat /sys/bus/usb/devices/usb2/2-4/busnum 2 $ cat /sys/bus/usb/devices/usb2/2-4/devnum 3 you'd use `epson2:libusb:002:003` for the device name. When power cycling, on the `devnum` will change. Note that there is a libsysfs-dev package which may be useful here. Hope this helps, The path on my machine was similar but didn't have the files you specified but your guidance led to this command which gives me the proper addresses of all attached scanners: $ sane-find-scanner -v -v | sed -n -E 's/^found USB.*(libusb.*$)/\1/p' Thanks for the help, Martin
[sane-devel] Identifying identical scanners dynamically turned on and off
My problem is this: I will have 2-4 identical scanners attached to the same computer. Due to the needs of the application, the power to the scanners will be cut and turned on automatically by the computer when they are to scan. All scanners will be doing this, turn on - scan - turn off, in parallel several times per hour. I can not know if they will be on at the same time nor if the order will stay the same. So what I'd like to do, since they will be plugged into specific USB-ports, is to identify them by their physical port. But how to do this so a normal user has rights to communicate with the scanner in a safe manner? I haven't seen any information when investigating the scanner(s) as to their physical port/position. It might be that I haven't succeeded fully to agree with udev. At present only one scanner is attached and that works wonderfully but I call it without specifying device. Scanner-brand: Epson V700
[sane-devel] Identifying identical scanners dynamically turned on and off
It is a modified version of the epson2-backend (don't know if the patch of last fall has made its way into the main dist). The OS is Ubuntu, the latest I think or the latest long-term (not sitting close to that computer at present). My first thought was to look for the serial too, and unfortunately fujitsu don't have any scanner that fits our needs (A4 TPU + many more things), so they all have to be Epson v700. Reading its Programming Guide. Rev. C it seems to agree with you - that the best it can do is to send its 'Product Name' and 'ROM Version'. I suppose it must be question of learning the inner workings of udev then? On 2012-03-22 12:13, m. allan noah wrote: This would depend upon the backend, hardware and OS that you use. The fujitsu backend is capable of reading the serial number of the scanner, and uses that as part of the device name. Other backends cannot do this because the hardware does not know its own serial number. In that case, you would have to give the device a consistent name at the OS level, and somehow get the backend to use that name. allan
[sane-devel] [PATCH] scanbd: Makefile-001 ensure target dirs exist
Hi Wilhelm, On Sat, Mar 03, 2012 at 12:10:13PM +0100, Wilhelm wrote: Hi Martin, thank you for the patches. They are merged to trunk and into release/1.2. Also make a file release scanbd-1.2.tgz on SF. Thanks for merging so quickly -- that's excellent. Thanks, Wilhelm Martin -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20120307/c8a28aa3/attachment.pgp
[sane-devel] [PATCH] scanbd: Makefile-001 ensure target dirs exist
Hi, I am packaging scanbd for Fedora (someone stop me if it's done) and I came across two things I would like to add to the Makefile: 1) 'make install' should not assume all its target dirs exist (it doesn't for two of the three dirs it targets but it assumes /etc/dbus-1/system.d exists) and 2) 'make install' should respect $PREFIX and / or $DESTDIR if set, DESTDIR being the conventional one RPM will set when doing mock builds / installs for various purposes during the RPM packaging process. Would you please consider these two patches and let me know if they are acceptable or if I can improve them to make them so? The patches were created by 'svn diff' against SVN trunk (checked out a few minutes ago). The first patch follows and the second will be set as a reply (with changed subject) to this mail. Thanks, Martin Index: Makefile === --- Makefile(revision 77) +++ Makefile(working copy) @@ -160,11 +174,12 @@ cp scanadf.script $(SCANBD_DIR) cp test.script $(SCANBD_DIR) echo Copy scanbd to $(BIN_DIR) + mkdir -p $(BIN_DIR) cp scanbd $(BIN_DIR) echo Copy scanbuttond backends to $(SCANBD_DIR)/scanbuttond/backends mkdir -p $(SCANBD_DIR)/scanbuttond/backends - -cp scanbuttond/backends/*.so $(SCANBD_DIR)/scanbuttond/backends + -cp scanbuttond/backends/*.so $(SCANBD_DIR)/scanbuttond/backends || /bin/true echo Copy scanbd_dbus.conf to /etc/dbus-1/system.d/ cp scanbd_dbus.conf $(DBUS_PREFIX)/etc/dbus-1/system.d - -cp scanbuttond/backends/meta.conf $(SCANBD_DIR)/scanbuttond/backends + -cp scanbuttond/backends/meta.conf $(SCANBD_DIR)/scanbuttond/backends || /bin/true echo Edit /etc/inetd.conf -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20120302/2096b74f/attachment.pgp
[sane-devel] [PATCH] scanbd: Makefile-002 support DESTDIR and PREFIX envvars if set
2) 'make install' should respect $PREFIX and / or $DESTDIR if set, DESTDIR being the conventional one RPM will set when doing mock builds / installs for various purposes during the RPM packaging process. Would you please consider these two patches and let me know if they are acceptable or if I can improve them to make them so? The patches were created by 'svn diff' against SVN trunk (checked out a few minutes ago). Index: Makefile === --- Makefile(revision 77) +++ Makefile(working copy) @@ -29,14 +29,28 @@ DBUS_INCLUDE= endif +ifndef PREFIX PREFIX = /usr/local +endif + +ifndef DESTDIR SCANBD_DIR = $(PREFIX)/etc/scanbd +else +PREFIX = $(DESTDIR)/usr +SCANBD_DIR = $(DESTDIR)/etc/scanbd +endif + BIN_DIR = $(PREFIX)/bin + ifeq ($(OSTYPE),FreeBSD) DBUS_PREFIX = /usr/local else +ifndef DESTDIR DBUS_PREFIX = +else +DBUS_PREFIX = $(DESTDIR) endif +endif ifeq ($(OSTYPE),Linux) USE_LIBUDEV=yes -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20120302/b127e1a8/attachment.pgp
[sane-devel] TPU functionality in epson2-backend.
On 2011-12-05 04:48, Olaf Meeuwissen wrote: Martin Zackrissonmartin.zackrisson at cmb.gu.se writes: On 11/30/2011 05:51 PM, m. allan noah wrote: SANE_DEBUG_EPSON2=255 scanimage [args here] 2tpu.log then look in tpu.log allan Thanks. Just for reference, I now have the programming guide for the scanner and it seems that the capability that I'm looking to implement in fact is structured as a second TPU-mode and not a setting in the current TPU mode. So I'll get back to scratch and see if I can push it into TPU 2 instead. FTR, the device indeed has two TPU modes. In my earlier mail I only mentioned one, having completely missed the information on the second TPU which allows for 8 x 10 scans (the first TPU does 5.8 x 9.74). Sorry for the incomplete information earlier. # Next time I'll reply after my second coffee ;-) Hope this helps, When I realized it was a second TPU and got some pointers from the guy who wrote the backend originally, it took me less than five minutes to fix it. He also submitted the patch so everything is perfect. Thanks for all the help. /Martin
[sane-devel] TPU functionality in epson2-backend.
On 11/30/2011 05:51 PM, m. allan noah wrote: SANE_DEBUG_EPSON2=255 scanimage [args here] 2tpu.log then look in tpu.log allan Thanks. Just for reference, I now have the programming guide for the scanner and it seems that the capability that I'm looking to implement in fact is structured as a second TPU-mode and not a setting in the current TPU mode. So I'll get back to scratch and see if I can push it into TPU 2 instead. /Martin
[sane-devel] TPU functionality in epson2-backend.
Just for reference, I now have the programming guide for the scanner
and it seems that the capability that I'm looking to implement in fact
is structured as a second TPU-mode and not a setting in the current
TPU mode. So I'll get back to scratch and see if I can push it into
TPU 2 instead.
Solved!
The following changes is ALL that is required for the V700 (or GT-X900
as it also is called) to implement the full TPU area.
Is there a possibility of getting that into the official epson2 backend?
epson2-ops.c:
673c673
if (e2_model(s, GT-X800) || e2_model(s, GT-X900)) {
---
if (e2_model(s, GT-X800)) {
1223c1223
if (s-lcount 3 (e2_model(s, GT-X800) || e2_model(s,
GT-X900))) {
---
if (s-lcount 3 e2_model(s, GT-X800)) {
/Martin
--
Martin Zackrisson
G?teborgs Universitet / Cell Molekyl?rbiologi
Medecinaregatan 9e
SE-413 90 G?teborg
Sweden
Phone +46 (0)31 786 3753
[sane-devel] TPU functionality in epson2-backend.
On 11/30/2011 04:53 PM, m. allan noah wrote: Are you sure you are really running your modified version of the backend? have you enabled debugging at runtime? I use prefix in ./configure and then in the folder I install it i run ./scanimage so I should be using my modified version as far as I can understand. As for debugging I haven't really understood how to enable runtime debugging (sorry for my newbieness) /Martin
[sane-devel] TPU functionality in epson2-backend.
On 11/22/2011 01:05 AM, Martin Zackrisson wrote: On 2011-11-21 00:56, Olaf Meeuwissen wrote: No clue what capability 32829 is, but the scanner protocol command that selects whether you use the flatbed or TPU option uses the same values. That is, 0 will do a flatbed scan, 1 a TPU scan. I'm not versed in c++, so I wonder if such a capability could be included in SANE? It could, but I seriously doubt it should as it would drive the scanner outside of its spec. Update: I now have the spec for the Epson TWAIN capabilities and the feature I was referring to above does have a name: ICAP_UNDEFINEDIMAGESIZEMSG_SET to TRUE to apply auto size dropping And it is implemented in Epson Scan 3.66 or later. I don't really have words for my lack of understanding of such a feature, but anyways... I'll try my best to get that into the backend. The following is also a candidate, since it seems to cause the same behaviour: ICAP_AUTOMATICBOADERDETECTIONMSG_SET to TRUE to apply auto size dropping -- Martin Zackrisson G?teborgs Universitet / Cell Molekyl?rbiologi Medecinaregatan 9e SE-413 90 G?teborg Sweden
[sane-devel] TPU functionality in epson2-backend.
On 11/24/2011 12:27 AM, Olaf Meeuwissen wrote:
Martin Zackrissonmartin.zackrisson at cmb.gu.se writes:
I've dug through the code and made copy/paste/rename adjustments
everywhere it seemed reasonable (first day with c-code...). This will
probably more show how lost I am than anything else, but below are the
diffs for all files I've been poking around (don't think I forgot
any). I think my main issue is that I have no clue how to connect the
static that I made (SANE_EPSON_CAP_FULL_SENSOR_IN_TPU) to what is
being sent in the scanner in define esci_set_full_sensor(s,v)
e2_esc_cmd( s,(s)-hw-cmd-set_full_sensor, v). That is to give
set_full_sensor the value of SANE_EPSON_CAP_FULL_SENSOR_IN_TPU.
Your SANE_EPSON_CAP_FULL_SENSOR_IN_TPU defines a two byte value but
s-hw-cmd-set_full_sensor is only a single byte. The e2_esc_cmd()
route will not work as it was written for scanner commands that all
start with an ESC (0x1b).
You have to write your own esci_set_full_sensor() (see esci_set_zoom()
in epson2-cmd.c for inspiration) and make that send the two bytes of
SANE_EPSON_CAP_FULL_SENSOR_IN_TPU as well as the 0 or 1 value you want
to set. BTW, I have no clue as to the command handshake but expect it
to be similar to that of esci_set_zoom().
Here's my new take on the code, it compiles and everything but scanimage
--all-options doesn't report my feature. I really don't get where that
happens so it's hard to know if what I've done makes any sense or not to
the scanner... (sorry for all the code, renamed everything to match the
name of the capability description from Epson)
diff ./epson2.c ../../sane-backends-1.0.22/backend//epson2.c
1340a1341,1354
/* full sensor in TPU */
s-opt[OPT_UNDEFINEDIMAGESIZE].name = undefinedimagesize;
s-opt[OPT_UNDEFINEDIMAGESIZE].title = SANE_I18N(Undefined Image
Size);
s-opt[OPT_UNDEFINEDIMAGESIZE].desc = SANE_I18N(In TPU mode some
scanners (e.g. V700) apply auto size dropping for the scanning area.
This option by-passes that 'functionality');
s-opt[OPT_UNDEFINEDIMAGESIZE].type = SANE_TYPE_BOOL;
s-val[OPT_UNDEFINEDIMAGESIZE].w = SANE_FALSE;
s-opt[OPT_UNDEFINEDIMAGESIZE].cap |= SANE_CAP_ADVANCED;
if (s-hw-undefinedimagesize == SANE_TRUE)
s-opt[OPT_UNDEFINEDIMAGESIZE].cap = ~SANE_CAP_INACTIVE;
else
s-opt[OPT_UNDEFINEDIMAGESIZE].cap |= SANE_CAP_INACTIVE;
1622a1637
case OPT_UNDEFINEDIMAGESIZE:
1715a1731
/*s-fullSensor = SANE_FALSE; since this option isn't
documented best not always activate */
1734a1751,1752
deactivateOption(s, OPT_UNDEFINEDIMAGESIZE, dummy);
1746a1765,1772
/* enable full size scanning */
if (s-hw-cmd-set_undefinedimagesize != 0) {
/*s-hw-x_range = s-hw-x_range;
s-hw-y_range = s-hw-y_range;*/
activateOption(s, OPT_UNDEFINEDIMAGESIZE, dummy);
} else {
deactivateOption(s, OPT_UNDEFINEDIMAGESIZE, dummy);
}
1772a1799
deactivateOption(s, OPT_UNDEFINEDIMAGESIZE, dummy);
1958a1986
case OPT_UNDEFINEDIMAGESIZE:
2059a2088,2089
s-hw-cmd-set_undefinedimagesize[0] = 0x80;
s-hw-cmd-set_undefinedimagesize[1] = 0x3D;
diff ./epson2-commands.c
../../sane-backends-1.0.22/backend//epson2-commands.c
56a57,84
/* Test implementation of ICAP_UNDEFINEDIMAGESIZE */
SANE_Status
esci_set_undefinedimagesize(Epson_Scanner * s, SANE_Bool x)
{
SANE_Status status;
unsigned char handshake[2];
SANE_Bool params[1];
DBG(8, %s: undefinedimagesize = %d\n, __func__, x);
if (!s-hw-cmd-set_undefinedimagesize) {
DBG(1, %s: not supported\n, __func__);
return SANE_STATUS_GOOD;
}
handshake[0] = s-hw-cmd-set_undefinedimagesize[0];
handshake[1] = s-hw-cmd-set_undefinedimagesize[1];
status = e2_cmd_simple(s, handshake, 2);
if (status != SANE_STATUS_GOOD)
return status;
params[0] = x;
return e2_cmd_simple(s, params, 1);
}
diff ./epson2-commands.h
../../sane-backends-1.0.22/backend//epson2-commands.h
31a32
/*#define esci_set_undefinedimagesize(s,v)e2_esc_cmd(
s,(s)-hw-cmd-set_undefinedimagesize, v)*/
38a40
SANE_Status esci_set_undefinedimagesize(Epson_Scanner * s, SANE_Bool x);
diff ./epson2.h ../../sane-backends-1.0.22/backend//epson2.h
99a100,102
/* undocumented sensor feature for V700 */
#define SANE_EPSON_CAP_UNDEFINEDIMAGESIZE 0x803D
220a224
unsigned char set_undefinedimagesize[2]; /* For scanning the full
area in TPU on V700*/
262a267
OPT_UNDEFINEDIMAGESIZE,
340a346
SANE_Bool undefinedimagesize; /* does the scanner have support
for full sensor mode when TPU is source? */
393a400
SANE_Bool undefinedimagesize;
diff ./epson2-ops.c ../../sane-backends-1.0.22/backend//epson2-ops.c
152a153,155
dev-cmd-set_undefinedimagesize[0] = 0x80;
dev-cmd-set_undefinedimagesize[1] = 0x3D
[sane-devel] TPU functionality in epson2-backend.
On 2011-11-21 00:56, Olaf Meeuwissen wrote: No clue what capability 32829 is, but the scanner protocol command that selects whether you use the flatbed or TPU option uses the same values. That is, 0 will do a flatbed scan, 1 a TPU scan. I'm not versed in c++, so I wonder if such a capability could be included in SANE? It could, but I seriously doubt it should as it would drive the scanner outside of its spec. Thanks very much for your reply. I suspect that the scanner has a TPU capability limit is set lower since Epson must have assumed that people are not interested in scanning the full area in TPU mode (you are meant to use their fixtures to scan negatives etc. which all fall inside the standard TPU capability range). However, under Windows it is indeed possible to extend it. In fact the reason I found out about the 32829 was because I monitored what settings were changed when I launched Epson's own scanning interface (Two more did, but I never found any functionality connected to them). And changing this value to 1 does the trick/allows full size scanning. I've gotten many images that way, and I don't see any significant quality drop outside the standard max-range. Swithing it back to 0 and you get the smaller scanning area - all other settings equal. The setting could mean something like use full sensor width/length. Unfortunately for me, my use of the scanner demands that I succeed in getting the full image. So I would very much appreciate having this feature included or directions for how I could build it myself. Else, I would have to surrender back to Windows and TWAIN again. Also, my brute-force solution to the lamp-issue below is by simply cutting power to the scanner. This requires me to work in Linux. So I'm in a bit of a tight spot here. Best regards, Martin Zackrisson
[sane-devel] TPU functionality in epson2-backend.
Hello, I've got an Epson Perfection V700 Photo with a TPU. When selecting the TPU as source in SANE, the allowed scan area shrinks compared to regular scanning. scanimage: rounded value of br-x from 215.9 to 149.86 scanimage: rounded value of br-y from 297.18 to 246.38 I know this behaviour from TWAIN where in my python application self.SD.SetCapability(32829, 4, 1) resolves the issue and gives back full scanning area while still using the TPU. Syntax for the command is simply to set capability 32829 to 1 (probably instead of being 0). As far as I can see this is not a documented capability in TWAIN. I'm not versed in c++, so I wonder if such a capability could be included in SANE? (On the side, If anybody had a clue as to how one could force the scanner-lamp to be turned off without waiting the 15 minutes that is the standard time-out) Regards, Martin Zackrisson
[sane-devel] Canon LiDE 200 scanning fails with backends from PPA
I just tried to scan with xsane, that seems to work. Very interesting ? -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 554 bytes Desc: OpenPGP digital signature URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110430/18d52823/attachment.pgp
[sane-devel] Canon LiDE 200 scanning fails with backends from PPA
Hi Everyone, I tried to use the new sane-backend from the Robert Ancell PPA as described in the [ubuntuforums post](http://ubuntuforums.org/showpost.php?p=10526638postcount=31). According to that post, I should be able to scan with my Canon LiDE 200 using the `sudo simple-scan` command. The first attempt to scan after attaching the scanner to the computer (Apple iMac, Intel Core 2 Duo, Ubuntu 10.10 32-Bit) yields some sounds from the motor of the scanner, but the scanner head barely moves. The terminal I launched simple-scan from displays the following message: ** (simple-scan:4209): WARNING **: Unable to start device: Error during device I/O When I started another scan, it would do nothing and just block the program for a while. Today, I tried the same on another computer (Asus Eee, Intel Atom, Ubuntu 10.10 32-Bit), and I managed to scan one single page without any errors. After that, simple-scan showed the message. I attached the `simple-scan -d` output of a first and a subsequent scan. If there is anything else I can do to diagnose the problem, please let me know. How can I get my scanner to work on either computer? Regards, Martin -- next part -- A non-text attachment was scrubbed... Name: debug-1.txt.gz Type: application/x-gzip Size: 2578 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110425/79c460de/attachment.bin -- next part -- A non-text attachment was scrubbed... Name: debug-2.txt.gz Type: application/x-gzip Size: 2457 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110425/79c460de/attachment-0001.bin
[sane-devel] Canon LiDE 200 scanning fails with backends from PPA
Dear Stef, I tried your command, it did not work the first time, the second time returned a reasonable looking image. First try: $ scanimage -d genesys --resolution 100 --mode Color scan100dpi.pnm scanimage: sane_start: Error during device I/O Second try: $ scanimage -d genesys --resolution 100 --mode Color scan100dpi.pnm # no output The [image](http://img851.imageshack.us/img851/7334/scan100.jpg) looks good to me. When I tried to scan an A4 document, it worked on the third try. And the scanner seemed slower to me. Additionally, it made some strange noises that sounded like the head would move in two directions at once. The error was the same ?Error during device I/O?. The image quality seems lower than the results that I got with Canon's MP Navigator EX 2.0 on Mac OS X 10.5 before. I there used 200 DPI, grayscale and textdocument as a source, writing a JPEG. Now I used scanimage --mode Gray -x 210 -y 297 --resolution 200 and the [result](http://img708.imageshack.us/img708/8666/10543314.jpg) does not look too good. This is better than before, but the I/O errors are still strange. Is there anything else, that I can do about that? Martin
[sane-devel] problem with scsi interface on Epson GT7000 (ubuntu 10.10)
Hello Olaf, Olaf Meeuwissen [2011-03-03 13:14 +0900]: I [...] will be filing a bug report to get this fixed. It is not a SANE problem. Done. See https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/727696 Thanks for pointing that out! I'll look into this ASAP. Olaf Meeuwissen [2011-03-02 9:06 +0900]: The cause is in the Ubuntu modifications to the upstream sources. They rip out the udev SCSI support, claiming that 70-acl.rules already takes care of that. It doesn't, at least not for a few select SCSI scanners. These scanner do not advertise themselves as a SCSI scanner but as some kind of processor (mostly). The SANE *.desc files have support for these special devices insofar known but the Ubuntu modifications conveniently yanked that :-(( in debian/patches/ubuntu_udev_noperm.patch. A quick search through the Ubuntu bug reports on scsi scanner shows that there are more people with the same problem: https://bugs.launchpad.net/ubuntu/+source/sane-frontends/+bug/378989 https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/440150 Duped these two to #727696. https://bugs.launchpad.net/ubuntu/+source/sane-frontends/+bug/650474 This seems to be something else. The reporter says the permissions are crw-rw+ 1 root root 21, 0 2010-09-28 18:59 /dev/sg0 Which already seems correct (the '+' is the automatic ACL). So I didn't dupe that one. Thanks! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
[sane-devel] Sane backends in feature freeze
Hi, Attached you'll find the updated/corrected Dutch translations. Can someone commit these, please. Thanks. Martin Kho And uh, Reinhold, it wasn't much work to add the magicolor backend translations ;) On Monday 31 January 2011 14:28:31 you wrote: yes- you are correct. I've committed a fix. allan On Mon, Jan 31, 2011 at 11:59 AM, Martin Kho lists.kho at gmail.com wrote: On Monday 31 January 2011 08:45:14 m. allan noah wrote: Sane-backends is now in feature freeze in preparation for release of 1.0.22. Please only commit bug fixes and documentation updates. Feb 06, 2011: Code freeze (only horrible bugs + documentation updates) Feb 13, 2011: Release allan Hi, Will the Magicolor backend be part of the next release? It's not called in the /po/POTFILES file. Thanks, Martin Kho -- 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: nl.po.gz Type: application/x-gzip Size: 27651 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20110203/2851b00d/attachment-0001.bin
[sane-devel] Sane backends in feature freeze
On Monday 31 January 2011 08:45:14 m. allan noah wrote: Sane-backends is now in feature freeze in preparation for release of 1.0.22. Please only commit bug fixes and documentation updates. Feb 06, 2011: Code freeze (only horrible bugs + documentation updates) Feb 13, 2011: Release allan Hi, Will the Magicolor backend be part of the next release? It's not called in the /po/POTFILES file. Thanks, Martin Kho
[sane-devel] Troubles with PIXMA MX870 and USB
To scan in Duplex ADF mode, you need to set 2 pages to scan in Xsane. Otherwise, it will stop at the first page. Did you try that ? Nicolas Le lundi 31 janvier 2011 ? 12:08 +0100, Stephan Ritscher a ?crit : Hi folks, I just got a new Canon Pixma MX870, but it doesn't work completely, yet. Let me start with my setup. I run Gentoo with kernel 2.6.36-gentoo-r5 on an Intel(R) Core(TM)2 Duo CPU T9300. I use the latest sane-backends from GIT and sane-frontends-1.0.14. I want to run the scanner in two different configurations - via wireless network and via usb. I'll start with the wireless setup. First of all, it recognizes my printer - kind of. My router (EasyBox 803) resolves all ip addresses in the local network as localhost and thereby confuses SANE. # /usr/libexec/cups/backend/bjnp network bjnp://localhost:8611 Canon MX870 series Canon MX870 series localhost MFG:Canon;CMD:BJL,BJRaster3,BSCCe,NCCe,IVEC,IVECPLI;SOJ:TXT01,BJNP2;MDL:MX870 series;CLS:PRINTER;DES:Canon MX870 series;VER:1.030;STA:10;FSI:04;HRI:EU;MSI:DAT,E3,HFSF;PDR:4; If I add the line bjnp://192.168.2.101:8612 to /etc/sane.d/pixma.conf, scanimage and other applications recognize my scanner and work properly. I attached the log file corresponding to # export SANE_DEBUG_PIXMA=3 # scanimage -T 2 scan-net.log ADF is working, too, but I didn't get ADF Duplex running (Xsane scans one page and then stops - is this supposed to work, anyways?). Now trying USB cable, I removed the extra line from /etc/sane.d/pixma.conf. After attaching the USB cable, I get # dmesg -c usb 2-2.1: new high speed USB device using ehci_hcd and address 8 usblp0: USB Bidirectional printer dev 8 if 1 alt 0 proto 2 vid 0x04A9 pid 0x1743 scsi7 : usb-storage 2-2.1:1.2 usblp1: USB Bidirectional printer dev 8 if 3 alt 0 proto 2 vid 0x04A9 pid 0x1743 scsi 7:0:0:0: Direct-Access CanonMX870 series 0103 PQ: 0 ANSI: 2 sd 7:0:0:0: Attached scsi generic sg2 type 0 sd 7:0:0:0: [sdb] Attached SCSI removable disk I also attached the gzipped output of # lsusb -v lsusb.log Now I ran # scanimage -T 2 scan-usb.log The scanner makes some noises, but the command returns immediately. Xsane fails with Error during read: Error during device I/O. In some forum I read that unloading ehci_hcd helps. Thus I tried # sudo rmmod ehci_hcd # scanimage -T 2 scan-usb2.log The scanner shows Processing... Please wait momentarily., but makes no noises of activity. Since scanimage gets stuck, I terminated it with kill -9. The Processing... message only disappears on unplugging the USB connection. Do you have any suggestions? Best regards Stephan Ritscher -- 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
[sane-devel] Success: Canon Pixma MX320 (previously untested)
Hi all,
i like to state that i was able to sucessfully scan images using my new Canon
Pixma MX320 device. Things not tested yet:
- ADF
- Button mode
Resolutions: 75, 150, 300, 600 and 1200 DPI
Linux: Debian Squeeze (Testing)
Interface: USB
Drivers: Canon Scangear 1.30-1 (from their website)
Backend: Pixma
Entry in /etc/udev/rules/60-libsane.rules:
# Canon PIXMA MX320
ATTRS{idVendor}==04a9, ATTRS{idProduct}==1736, MODE=0664,
GROUP=scanner, ENV{libsane_matched}=yes
Worth mentioning: The drivers install a 80-canon_mfp.rules. That one is
redundant, the scangear-software works as long as the scanner is in the
libsane rules (see above). On my system the canon-rulesfile even generates a
lot of warnings in syslog (due to old rules-syntax) so you better remove it
after the scanner works.
I will try to fiddle a bit with ADF and button mode but they are not very
important to me so don't hold your breath for an update :-)
If you need further information please contact me.
Best regards
Martin Trenz, Frankfurt, Germany
[sane-devel] diffs sent to support MP810, MP960, Canoscan 9000F
I checked that it currently compiles with gcc 4.4.3, but this statement gies a warning message telling %llu is not supported. If this is not advisable to leave PRIu64 here, for compatibility with all systems, then we will need to remove it. Nicolas Le lundi 17 janvier 2011 ? 02:17 +0900, Gernot Hassenpflug a ?crit : On Sun, Jan 16, 2011 at 7:58 PM, m. allan noah kitno455 at gmail.com wrote: Is PRlu64 C89? If not, you will have to drop that change. Someday sane will use C99 :) Hi Allan, Nicolas already added the PRIu64 to the pixma backend, so I guess it is okay. I think it is C90, but have not checked myself. Regards, Gernot -- 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
[sane-devel] still segmentation fault on MP900, MP950
Hopefully, code and declarations for those 2 old models, MP900 and MP950, is not part of the git version, probably this is from a test version you're currently using for debugging. Those 2 Pixma models are more than 5 years old, so probably not strategic to have them supported for the next Sane release, as nobody asked for support to these models, since I'm working on the pixma backend. Let us know anyway when this issue will be fixed, and when these models will be ready for support. Nicolas Le dimanche 09 janvier 2011 ? 17:13 +0900, Gernot Hassenpflug a ?crit : Hi, I did not have time to invetigate segmentation problems on the MP900, MP950 before now. They still exist. With SANE_DEBUG_PIXMA set to 11, I get the following output from running xsane (sane-find-scanner finds the scanner also, no problem): ... [pixma] scanner discovery finished... [pixma] pixma_open(): Canon PIXMA MP900 [pixma] OUT T=3.637 len=16 [pixma] :f3 20 00 00 00 00 00 00 00 00 00 00 00 00 00 0c [pixma] [pixma] IN T=3.641 len=2 [pixma] :15 15 [pixma] [pixma] WARNING: result len=2 expected 20 [pixma] :15 15 [pixma] INTR T=3.671 len=16 [pixma] :00 00 00 00 00 00 00 00 00 00 00 00 40 00 00 00 [pixma] Segmentation fault It only occurs with these two models of scanners as far as I can tell. My OS uname details: Linux 2.6.32-5-686-bigmem #1 SMP Fri Dec 10 16:59:53 UTC 2010 i686 GNU/Linux Using SANE CVS Best regards, Gernot
[sane-devel] Canon Image Class MF4150 scanner with Automatic Docment Feeder as Source
Well, for all ImageClass MFPs, the maximum width and height scan is currently set to 640 x 877 pixels at 75 dpi, this corresponds to: 640 / 75 * 2.54 cm = 21,67 cm in width 877 / 75 * 2.54 cm = 29,70 cm in height Those values are set in the backend, file pixma_imageclass.c, at the end of the file, separately for each model supported in this file. There's a line corresponding to MF4150. Although never tested, you could try to change those values to bigger ones corresponding to A3, and see if the scanner accepts them : This would be, a size like : 877 x 1280 instead of 640 x 877 DEV (Canon imageCLASS MF4150, MF4100, MF4100_PID, 600, 877, 1280, PIXMA_CAP_ADF) Let us know then. N Le dimanche 09 janvier 2011 ? 14:52 +0100, Tomas Pospisek a ?crit : On Wed, 5 Jan 2011, Mohammed Rashid wrote: I am using Canon Image Class MF4150 scanner with Automatic Docment Feeder as Source. My OS is OpenSuSE 11.2. But I am unable to the get the whole image. From bottom I am missing few lines. How can set the A3 etc?? Could this be the same problem as this one here? : http://lists.alioth.debian.org/pipermail/sane-devel/2010-December/027876.html *t -- 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
[sane-devel] Schedule for release of sane-backends 1.0.22
Hi, Thanks for this pointer, very interesting and commented So we have to be double careful when using memcpy though, even if it acts faster than its cousin memmove ! Nicolas Le samedi 08 janvier 2011 ? 09:43 +0100, Julien BLACHE a ?crit : Nicolas Martin nicolas0martin at gmail.com wrote: Hi, What is weird here, is that the effect of overlap in memcpy does not seem to produce the same effect on different systems ! Using memcpy() on overlapping memory areas is undefined behaviour per spec. glibc has several memcpy() implementations optimized for different hardware capabilities. A recent implementation for Atom/Core2 CPUs performs the copy from tail to head (giving a nice 4x/5x speedup on these CPUs), which breaks with overlapping memory areas. Using memmove() is the correct way to handle overlapping areas, as documented. See http://lwn.net/Articles/414467/ for more (links/comments). HTH, JB.
[sane-devel] Schedule for release of sane-backends 1.0.22
Thanks Dustin for your feedback. The issue of memmove vs memcpy appears in the last phase of image processing, to reduce the scanned line width, in order to get an exact scanned area width, and get rid of the Pixma modulo 32 line width. Il this case, the cropped line is copied above the scanned line, that explains the overlap situation, but the cropped line is always smaller, so no risk of buffer overflow. When the width is an exact multiple of 32, the cropped and original lines are exactly identical. What is weird here, is that the effect of overlap in memcpy does not seem to produce the same effect on different systems ! Looks some systems have memcpy to copy correctly above the original line, but not others. Anyway, the memmove here handles correctly the overlap situation, so this issue should be solved now. Nicolas Le vendredi 07 janvier 2011 ? 00:46 -0500, Dustin DeWeese a ?crit : After pulling commit e72c0f548eebfae0171ab8a2e2a74174c1bd96ae, the pixma backend works correctly with my MX850; there is no corruption, even on widths indivisible by 32. Thanks! - Dustin DeWeese On 01/06/2011 04:19 PM, Nicolas Martin wrote: AFAIK, I've currently only heard about this pending issue for the pixma backend, reported by Dustin DeWeese: https://alioth.debian.org/tracker/?func=detailatid=410366aid=312874group_id=30186 Maybe Dustin could give us more info about his current test status, using the latest git ? Nicolas Le jeudi 06 janvier 2011 ? 21:03 +0100, Tomas Pospisek a ?crit : On Wed, 5 Jan 2011, Julien BLACHE wrote: m. allan noahkitno455 at gmail.com wrote: I also have a report for the AV120 (#548731). I've not heard from Nicholas. The pixma fix is still in work, IIRC we should hear back from Gernot in the coming weeks. I think Gernot has confirmed that the one-line fix does fix the machines he has access to. It does also fix my own pixma mp600. We do not know though about generation 1 machines. Aren't we waiting for Nicholas' word on the issue? *t -- 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
[sane-devel] Schedule for release of sane-backends 1.0.22
AFAIK, I've currently only heard about this pending issue for the pixma backend, reported by Dustin DeWeese: https://alioth.debian.org/tracker/?func=detailatid=410366aid=312874group_id=30186 Maybe Dustin could give us more info about his current test status, using the latest git ? Nicolas Le jeudi 06 janvier 2011 ? 21:03 +0100, Tomas Pospisek a ?crit : On Wed, 5 Jan 2011, Julien BLACHE wrote: m. allan noah kitno455 at gmail.com wrote: I also have a report for the AV120 (#548731). I've not heard from Nicholas. The pixma fix is still in work, IIRC we should hear back from Gernot in the coming weeks. I think Gernot has confirmed that the one-line fix does fix the machines he has access to. It does also fix my own pixma mp600. We do not know though about generation 1 machines. Aren't we waiting for Nicholas' word on the issue? *t -- 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
[sane-devel] maximum image size for a scan for Canon pixma backend
Le vendredi 31 d?cembre 2010 ? 02:55 +0900, Gernot Hassenpflug a ?crit : On Fri, Dec 31, 2010 at 2:50 AM, Robert Krawitz rlk at alum.mit.edu wrote: On Fri, 31 Dec 2010 02:41:10 +0900, Gernot Hassenpflug wrote: On Fri, Dec 31, 2010 at 2:19 AM, Gerard Klaver gerard.klaver at xs4all.nl wrote: On Fri, 2010-12-31 at 01:29 +0900, Gernot Hassenpflug wrote: Dear all, I have been involved in trying to support the Canoscan 9000F, and the testing community has grown to about 15 individuals. A few of them have programming knowledge and tonight one individual send in corrected code to handle the final hurdle: correctly aligning the sub-images in the 9600dpi TPU mode. So the scanner is now supported for all modes. However, for large images at both 4800dpi and 9600dpi modes, it seems the max size of the image is limited in some way, so that only a section of the desired image is delivered. Is this something that can be set in the individual driver files (like pixma_mp150.c) or in some of the generic pixma driver .c or .h files (which I do not want to touch if possible)? I don't see a problem in the linesize or dimensions, only in the image_size value seen by [pixma] debugging output. Best regards, Gernot Hassenpflug -- 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 One possible solution (if not yet done), is to check the declaration of the image_size parameter, for a 9600 dpi A4 scan (color) size is about 550 000 000 000 bytes. (long long is needed) Hi, thank you for that. I see that image_size is currently declared as unsigned. I imagine that changing the declaration will need to be checked in all places where the calculations using image_size are done, or not? Currently, from the report I obtain from a test user, a 4800x4800dpi image with dimensions: 32824 px (width) * 47248 px (height) should have a image_size of 4652605056 bytes (W*H*3 for channel number) whereas the actual image_size used is 357637760 bytes (approximately 341.1 MiB). I am still trying to ascertain whether for some reason the wrong calculation for image_size might have been made, but certainly the width and height are correctly there. 32824 * 47248 * 3 - 357637760 = 4294967296 which is exactly 2^32. So that suggests exactly the problem described above. Ah! I suspected it was that, but forgot I had to take the difference to get this number. Fantastic! Well, that sounds like somewhat of a issue then for the SANE Canon maintainer to comment on. I guess this issue had to come up eventually. Should be possible to extend the image size in pixma backend by declaring uint64_t instead of unsigned the following variables: image_byte_read (in pixma.c), image_size (in pixma.h) cur_image_size (in pixma_common.h) Debug statements should also to be adjusted, %llu instead of %u in the different format strings, although this gives a compilation warning anyway, as the gcc compile statement uses the -pedantic flag. Unless someone has a better solution for sprintf 64 bits integers ? Anyway, could you give a try on 9000F with those changes ? Nicolas
[sane-devel] maximum image size for a scan for Canon pixma backend
Le vendredi 31 d?cembre 2010 ? 14:11 +0900, Gernot Hassenpflug a ?crit : On Fri, Dec 31, 2010 at 8:11 AM, Gernot Hassenpflug aikishugyo at gmail.com wrote: On Fri, Dec 31, 2010 at 8:05 AM, Nicolas Martin nicolas0martin at gmail.com wrote: Le vendredi 31 d?cembre 2010 ? 02:55 +0900, Gernot Hassenpflug a ?crit : On Fri, Dec 31, 2010 at 2:50 AM, Robert Krawitz rlk at alum.mit.edu wrote: On Fri, 31 Dec 2010 02:41:10 +0900, Gernot Hassenpflug wrote: On Fri, Dec 31, 2010 at 2:19 AM, Gerard Klaver gerard.klaver at xs4all.nl wrote: On Fri, 2010-12-31 at 01:29 +0900, Gernot Hassenpflug wrote: Dear all, I have been involved in trying to support the Canoscan 9000F, and the testing community has grown to about 15 individuals. A few of them have programming knowledge and tonight one individual send in corrected code to handle the final hurdle: correctly aligning the sub-images in the 9600dpi TPU mode. So the scanner is now supported for all modes. However, for large images at both 4800dpi and 9600dpi modes, it seems the max size of the image is limited in some way, so that only a section of the desired image is delivered. Is this something that can be set in the individual driver files (like pixma_mp150.c) or in some of the generic pixma driver .c or .h files (which I do not want to touch if possible)? I don't see a problem in the linesize or dimensions, only in the image_size value seen by [pixma] debugging output. Best regards, Gernot Hassenpflug -- 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 One possible solution (if not yet done), is to check the declaration of the image_size parameter, for a 9600 dpi A4 scan (color) size is about 550 000 000 000 bytes. (long long is needed) Hi, thank you for that. I see that image_size is currently declared as unsigned. I imagine that changing the declaration will need to be checked in all places where the calculations using image_size are done, or not? Currently, from the report I obtain from a test user, a 4800x4800dpi image with dimensions: 32824 px (width) * 47248 px (height) should have a image_size of 4652605056 bytes (W*H*3 for channel number) whereas the actual image_size used is 357637760 bytes (approximately 341.1 MiB). I am still trying to ascertain whether for some reason the wrong calculation for image_size might have been made, but certainly the width and height are correctly there. 32824 * 47248 * 3 - 357637760 = 4294967296 which is exactly 2^32. So that suggests exactly the problem described above. Ah! I suspected it was that, but forgot I had to take the difference to get this number. Fantastic! Well, that sounds like somewhat of a issue then for the SANE Canon maintainer to comment on. I guess this issue had to come up eventually. Should be possible to extend the image size in pixma backend by declaring uint64_t instead of unsigned the following variables: image_byte_read (in pixma.c), image_size (in pixma.h) cur_image_size (in pixma_common.h) Debug statements should also to be adjusted, %llu instead of %u in the different format strings, although this gives a compilation warning anyway, as the gcc compile statement uses the -pedantic flag. Unless someone has a better solution for sprintf 64 bits integers ? Anyway, could you give a try on 9000F with those changes ? Hi Nicolas, Thanks, I'll implement that and send away for testing (I do not have the scanner myself), and report back. Dear all, It seems that fix has not broken anything yet (stil awaiting results from testers on how large images go). However, I have a report from a tester that might be of interest: I also replaced a memcpy() by a memmove() because the areas are overlapping. The spec says that memcpy should not be used for overlapping regions, and in recent glibc versions code relying on this behaviour doesn't work any more. (Valgrind reported this.) This is the line near the end of the post_process_image_data funtion in pixma_mp150.c: /* Crop line to selected borders */ memmove(cptr, sptr + cx, cw); I have this in my code now, and it seems not to break my scans with MP460, MP960, MP810, CS8800F. Nicolas, do you have a comment on this? This line is also part of the crop enhancement code proposed, that was committed in January. Yet, I did not investigate deeply how it works, but the memmove in this case is certainly better if zones overlap, although I did not notice any problems by myself with memcpy. So I'll change this statement to memmove. One point is that overlapping should not occur here, as line buffer sizes
[sane-devel] Problem with color shuffling using an Epson Perfection 610 ,
Hallo I found another Bug introduced between sane 1.0.19 and 1.0.21. Using xsane to aquire an preview-scan over the full plane in color mode fails. If you aquire an preview in bw/grayscale-Mode or over a part of the plain works well. I did a bisection wich led to this commit: author Alessandro Zummo a.zummo at towertech.it Sat, 9 Jan 2010 14:13:50 + (15:13 +0100) committer Alessandro Zummo a.zummo at towertech.it Sat, 9 Jan 2010 14:25:27 + (15:25 +0100) commit dd0e0dd7d4203a3a3ec356629e47e95bc6af7461 epson2: fixed color shuffling bug for Perfection 610, added more debugging Without further investigation i suggest: To increase the plane to scan for some lines to compensate the color-shuffling fails when you already selected to scan over the whole plane. best regards Martin Kr?ger
[sane-devel] Pixma MP600 broken by 1430217e1919801fa6418c36589cc4360e5f1779
2010/11/30 Gernot Hassenpflug aikishugyo at gmail.com On Tue, Nov 30, 2010 at 5:53 AM, Nicolas Martin nicolas0martin at gmail.com wrote: Le lundi 29 novembre 2010 ? 19:54 +0100, Tomas Pospisek a ?crit : On Mon, 29 Nov 2010, Tom?? Posp??ek wrote: [...] The same patch seems also to have broken Canon Pixma MP160 [1] and Pixma MP780 [2]. Could you try first to change, in the current git version of Sane, the following line in backend/pixma_mp150.c, at line 683: if (s-cfg-pid == MP460_PID || s-cfg-pid == MP510_PID) pixma_set_be32 (s-param-x - s-param-xs, data + 0x08); Take out the if condition, and leave only the second line: pixma_set_be32 (s-param-x - s-param-xs, data + 0x08); Hi Nicolas, That is quite strange. This is one of the patches which I believe I submitted during testing of various scanners, including the MP760/780. The MP460 and MP510 required a new addition (condition) which only have applied to them (for now) and no other devices, so I do not understand exactly how this affects unrelated devices. Unfortunately I now no longer have any of these machines, but I will compare the code I still have. Regards, Gernot Hassenpflug Originaly, the patch provided by Christian Scholtz for fine cropping adjustment, and uploaded in January 2010, was designed and tested on gen 3 devices, but I guess not on gen 2 devices, and was probably not working for any gen 2 devices. You probably noticed it when testing MP460 and MP510, that's why you fixed the above line (s-param-x - s-param-xs instead of s-param-x) but added a restriction for those 2 models. I'm just guessing here this fix is necessary for any gen 2 device as well. nicolas -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20101130/b79419b8/attachment-0001.htm
[sane-devel] Pixma MP600 broken by 1430217e1919801fa6418c36589cc4360e5f1779
Le lundi 29 novembre 2010 ? 22:08 +0100, Tomas Pospisek a ?crit : I will, however I ask you to please bear with me until in a few days when I'll be able to test the scanner again. Ok
[sane-devel] Problem using an Epson Perfection 610 with sane-backends 1.0.21
The right thing to do is disable the ESC m command for all D levels in epson2-ops.c. Patch attached. Patch works fine . Thanks . Best regards martin
[sane-devel] Problem using an Epson Perfection 610 with sane-backends 1.0.21
Hello
I am owner of an Epson Perfection 610. It did his work very well until i
switched from debian-stable using sane 1.0.19 to debian-testing 1.0.21.
So i pulled the sane-repository and did a bisection. This led to this
commit introducing the problem:
author Alessandro Zummo a.zummo at towertech.it
Sat, 9 Jan 2010 16:24:33 + (17:24 +0100)
committer Alessandro Zummo a.zummo at towertech.it
Sat, 9 Jan 2010 16:24:33 + (17:24 +0100)
commit 503f9a6d464fe592881e7c748203f40abeb02b81
epson2: simplified color correction, built in profiles active by default
I did further examinations with the sane debug-output:
[epson2] esci_set_color_correction_coefficients
[epson2] e2_cmd_simple: size = 2
[epson2] e2_send: size = 2, reply = 1
[epson2] e2_send: ESC m
[epson2] buf[0] 1b .
[epson2] buf[1] 6d m
[epson2] e2_send: cmd count, r = 41, w = 38
[epson2] e2_recv: size = 1, buf = 0x76fabc4b
[epson2] e2_recv: cmd count, r = 42, w = 38
[epson2] buf[0] 15 .
[epson2] e2_cmd_simple: NAK
The problem rises when calling the function
esci_set_color_correction_coefficients().
A little more examination led to this patch after which the scanner does
his work as he should:
diff -r 7599778c24df backend/epson2.c
--- a/backend/epson2.c Sat Jan 09 17:24:33 2010 +0100
+++ b/backend/epson2.c Sat Nov 27 22:59:20 2010 +0100
@@ -200,7 +200,7 @@
static const SANE_Bool correction_userdefined[] = {
SANE_FALSE,
- SANE_TRUE,
+ SANE_FALSE,
SANE_TRUE,
};
Best regards
Martin Kr?ger
[sane-devel] NO scanner is now recognized. :(
Could you describe a little bit more what was the issue with grayscale scan on MX310 ? BTW, BW is currently not supported on this model, some more details about how you were proceeding would be useful to step further. Nicolas Le lundi 27 septembre 2010 ? 14:36 -0400, m. allan noah a ?crit : I don't see any indication that grayscale or binary modes have been added to the MX310 (pixma) backend. It is possible that the backend only exposes the actual capabilites of the scanner.- hopefully one of the pixma authors can comment further. allan On Mon, Sep 27, 2010 at 1:07 AM, Mr Fair Go mrfairgo at mrfairgo.com wrote: I compiled and installed the latest sane-backends-1.0.21 and tried to use it with a Canon DR-2010C scanner, G'day! I have a Canon MX310 which was scanning OK, but only in colour. There was some sort of bug in Greyscale and BW. I attempted to compile and install the newer sane backends also, but as a newbie I clearly did something wrong, because now none of my Linux scanning software will find the Canon or any other scanner (I have 3). I even uninstalled and reinstalled SANE and gscan2pdf via the Package Manager, but still Can someone point me to a very basic Linux how-to that explains for a newbie exactly how to compile and install with Linux? Everything I look at assumes I have more knowledge about compiling than I actually have. Running LinuxMint 9 (Isadora) which is built on Ubuntu, for nearly a year now. Up to this point upgrading and installing packages via Package Manager has been adequate for my needs, but the newer version is not available this way, thus I attempted the more challenging route, but can not find instructions anywhere. Thanks Mr Fair Go (They call me Mr Fair Go) http://mrfairgo.com fairgohomes.com.au --a Fair Go for aspiring homeowners, sellers, investors, renovators. fairgocom.net.au --a Fair Go for Getting Your Life Privacy Back! eservers.com.au --Professional Internet Hosting On Mon, Sep 27, 2010 at 1:12 PM, Ori Koren ori at paperact.com wrote: On Sat, Sep 25, 2010 at 8:28 PM, Simon Matter simon.matter at invoca.ch wrote: Hi, I compiled and installed the latest sane-backends-1.0.21 and tried to use it with a Canon DR-2010C scanner, but the scanner is not recognized (by scanadf -L, or scanimage -L). sane-find-scanner and lsusb can see the device. snipped Am I missing some option in one of the config files? snipped I am using an ubuntu 8.04.3. The libusb-0.1-4, libusb-dev versions are both 2:0.1.12-8 What about permissions? Did you try as root also? And is the backend in question enabled in your sane config? OK, it's working now. The thing that was missing was to add canon_dr to /etc/sane.d/dll.conf Simon Thanks, Ori -- 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 -- 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
[sane-devel] question about SANE backend fill_buffer function
Le mardi 07 septembre 2010 ? 19:47 +0900, Gernot Hassenpflug a ?crit : Dear all, I am working on the pixma backend for Canon devices (variation: pixma_mp150.c), and have a question about registration of pixels in the y dimension. Each backend I believe has variations on a filename_fill_buffer function called between file_scan and _finish_scan. The function reads sections of data from the scanner, and processes it line by line. Thus, pixels can be reorganized in the x-dimension. I am not sure if the amount of data read at once is controllable. I now have a problem where the pixels also need to be rearranged vertically. In particular, the first half of a line corresponds to the second half of a line much further along in the data. Is there any backend that has support for such processing, that I can look at for help? Or have I misunderstood what can be done with the current mp150_fill_buffer function in pixma_mp150.c? Yes, as I answered you, the pixma_mp150 implements a vertical shift reassembling that is needed by the CCD devices, as they produce scans with vertically shifted color planes. Maybe you can just use this, or use some modified version. Nicolas
[sane-devel] Need help with Canon DR-3080CII
The scanner will be returned tomorrow (I had it much longer than planned already). Anything left to try out? Am 29.07.2010 20:42, schrieb m. allan noah: Sorry, i've been really busy this week. I don't think I will get to it in the next couple days. allan On Tue, Jul 27, 2010 at 5:27 AM, Martin Kouba martin at kouba.at wrote: i will have the scanner only for a few more days. do you want to try something else? Am 23.07.2010 01:35, schrieb m. allan noah: Ok, this looks very similar to the windows log you took. I see a couple differences in the order of commands, and one additional command that we are not sending- no other canon_dr machine has used it yet, so I don't know the meaning. But, we can try to replicate it, and see if it works. allan On Thu, Jul 22, 2010 at 6:32 PM, Martin Kouba martin at kouba.at wrote: still no scan Am 2010-07-22 17:11, schrieb m. allan noah: can you try this: SANE_DEBUG_CANON_DR=30 scanimage --contrast -127 --mode Lineart --threshold 128 23080.log 3080.pnm That should more closely match your windows log. allan On Wed, Jul 21, 2010 at 4:31 PM, Martin Kouba martin at kouba.at wrote: well first it did something i guess it was moving the feeder but no scanning then i tried again ... nothing i power cycled the scanner and tried again ... nothing Am 2010-07-19 19:51, schrieb m. allan noah: ahh- leave out the --threshold option, and try again. allan On Mon, Jul 19, 2010 at 1:48 PM, Martin Kouba martin at kouba.at wrote: Am 2010-07-19 19:18, schrieb m. allan noah: Oh, something happens :) The scanner is mad about our set window command. This is the same place I got with the DR-3080C user. Try this: SANE_DEBUG_CANON_DR=30 scanimage --mode Gray --threshold 128 --contrast -127 23080.log 3080.pnm allan On Mon, Jul 19, 2010 at 12:48 PM, Martin Kouba martin at kouba.at wrote: nothing happens - martin at pc03:~$ SANE_DEBUG_CANON_DR=30 scanimage --mode Gray --resolution 100 [sanei_debug] Setting debug level of canon_dr to 30. [canon_dr] sane_init: start [canon_dr] sane_init: canon_dr backend 1.0.35, from sane-backends 1.0.22git [canon_dr] sane_init: finish [canon_dr] sane_get_devices: start [canon_dr] sane_get_devices: reading config file canon_dr.conf [canon_dr] sane_get_devices: looking for 'scsi CANON CR' [canon_dr] sane_get_devices: looking for 'scsi CANON DR' [canon_dr] sane_get_devices: setting vendor-name to CANON [canon_dr] sane_get_devices: setting model-name to DR-2080C [canon_dr] sane_get_devices: setting version-name to [canon_dr] sane_get_devices: setting padded-read to 1 [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1601' [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1602' [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1603' [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1604' [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1606' [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1607' [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1608' [canon_dr] sane_get_devices: setting padded-read to 1 [canon_dr] sane_get_devices: looking for 'usb 0x04a9 0x1609' [canon_dr] attach_one: start [canon_dr] attach_one: looking for 'libusb:001:003' [canon_dr] connect_fd: start [canon_dr] connect_fd: opening USB device [canon_dr] wait_scanner: start [canon_dr] do_usb_cmd: start [canon_dr] cmd: writing 24 bytes, timeout 500 [canon_dr] cmd: [canon_dr] 000: 00 00 00 14 00 01 90 00 00 00 00 00 00 00 00 00 [canon_dr] 010: 00 00 00 00 00 00 00 00 [canon_dr] cmd: wrote 24 bytes, retVal 0 [canon_dr] stat: reading 16 bytes, timeout 500 [canon_dr] stat: read 16 bytes, retval 0 [canon_dr] stat: [canon_dr] 000: 00 00 00 0c 00 03 a0 00 00 00 00 00 00 00 00 00 [canon_dr] do_usb_cmd: finish [canon_dr] wait_scanner: finish [canon_dr] connect_fd: finish [canon_dr] init_inquire: start [canon_dr] do_usb_cmd: start [canon_dr] cmd: writing 24 bytes, timeout 3 [canon_dr] cmd: [canon_dr] 000: 00 00 00 14 00 01 90 00 00 00 00 00 12 00 00 00 [canon_dr] 010: 30 00 00 00 00 00 00 00 0... [canon_dr] cmd: wrote 24 bytes, retVal 0 [canon_dr] in: reading 60 bytes, timeout 3 [canon_dr] in: read 60 bytes, retval 0 [canon_dr] in: [canon_dr] 000: 00 00 00 38 00 02 b0 00 00 00 00 00 06 00 02 02 ...8 [canon_dr] 010: 1f 00 00 10 43 41 4e 4f 4e 20 20 20 44 52 2d 33 CANON DR-3 [canon_dr] 020: 30 38 30 43 49 49 20 20 20 20 20 20 33 2e 31 39 080CII 3.19 [canon_dr] 030: 00 00 00 00 32 30 30 36 31 31 31 35 20061115 [canon_dr] stat: reading 16 bytes, timeout 3 [canon_dr] stat: read 16 bytes, retval 0 [canon_dr] stat: [canon_dr] 000: 00 00 00 0c 00 03 a0 00 00 00 00 00 00 00 00 00 [canon_dr] do_usb_cmd: finish [canon_dr] init_inquire: Found CANON scanner DR-3080CII version 3.19 at libusb:001:003
[sane-devel] Canon MF8030c
Le samedi 24 juillet 2010 ? 00:00 +0200, Mickael Profeta a ?crit : Hmm, that's funny indeed. Maybe to clarify, I do not know if it is related or not. The scanner has two modes, distant scan and connected to a computer. Not quite sure of the translation. I attach a new log in computer mode under windows, but I fear the log is incomplete, even if the scan was ok. I compile your modified version of pixma_imageclass.c and attach a new log (scan.log). The scanner has the same behaviour as before. Hope you could find some clue. Well, the attached usb snoop you last sent is unfortunately even worse and totally unusable, only a few bytes exchanged are shown here. I'm very skeptical if we can come to some success using the current ImageClass protocol, I'm afraid a rewrite of this new protocol is necessary. With understanding of new messages, how they are formated and of the data they content, this requires having access to a real device for testing. But first, if you could produce this alternate usb snoop, this may help, Regards, Nicolas
[sane-devel] Canon PIXMA MX870
Le jeudi 22 juillet 2010 ? 00:05 +0200, Matthias Pannek a ?crit : On Wed, 21 Jul 2010 20:23:16 +0200 Nicolas Martin nicolas0martin at gmail.com wrote: Yes, there was an error in the limiting to 600 dpi formula, hopefully, should be fixed in the new file attached. Works fine now. Ok So I've canceled any Pixma protocol change here, do you have the possibility to try the same with a usb cable ? Yeah, i can try it with via USB. Any special parameter needed for that? Nothing special, test it the same way as you did with network connexion. USB might require you to set some perms or udev rule tweak, so that you can scan as normal user (often usb perms are natively given only to root). In the meantime, I'll commit those first changes for MX870, this will be easier then to investigate the ADF empty issue Nicolas
[sane-devel] Canon PIXMA MX870
Note sure either what it means, but after some googling, it looks linked to some versions of kernel Did you try to modprobe -r the modules usblp and usb_storage ? Nicolas 2010/7/22 Nicolas Martin nicolas0martin at gmail.com Not sure either wha 2010/7/22 Matthias Pannek matthias at pannek.de On Thu, 22 Jul 2010 07:45:52 +0200 Nicolas Martin nicolas0martin at gmail.com wrote: Yeah, i can try it with via USB. Any special parameter needed for that? Nothing special, test it the same way as you did with network connexion. USB might require you to set some perms or udev rule tweak, so that you can scan as normal user (often usb perms are natively given only to root). I could scan.but there is a problem with usblp: $ scanimage -L device `pixma:04A91743_3052EF' is a CANON Canon PIXMA MX870 multi-function peripheral $ scanimage -T scanimage: scanning image of size 638x877 pixels at 24 bits/pixel scanimage: acquiring RGB frame, 8 bits/sample scanimage: reading one scanline, 1914 bytes... FAIL Error: Error during device I/O $ dmesg |tail -1 [ 5880.817977] usb 2-1.5: usbfs: interface 1 claimed by usblp while 'scanimage' sets config #1 I found many threads about this, but not sure what's wrong :( In the meantime, I'll commit those first changes for MX870, this will be easier then to investigate the ADF empty issue Thanks :-) Matthias -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100722/4ab9d9f5/attachment.htm
[sane-devel] Canon PIXMA MX870
Le mercredi 21 juillet 2010 ? 00:03 +0200, Matthias Pannek a ?crit : 600 DPI scan works perfectly, but 1200 and 2400 crashes with Floating point exception. 601 DPI seems to work too. Logs are cash.log and strace.log Yes, there was an error in the limiting to 600 dpi formula, hopefully, should be fixed in the new file attached. I tested a scan with an empty ADF but the scanner is still stuck after that. And this makes me wonder if this is due to the Pixma protocol, or to the network exchanges. So I've canceled any Pixma protocol change here, do you have the possibility to try the same with a usb cable ? Nicolas -- next part -- A non-text attachment was scrubbed... Name: pixma_mp150.c Type: text/x-csrc Size: 49991 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100721/da776c96/attachment-0001.c
[sane-devel] Canon MF8030c
Do you have the possibility to get a Windows usb snoop log using SnoopyPro.exe, to check if the protocol this model uses is a Pixma one ? I can give you instructions on how to do this if needed. Nicolas Le mercredi 21 juillet 2010 ? 14:09 +0200, Mickael Profeta a ?crit : Le Wed, 21 Jul 2010 12:56:33 +0200, Mickael Profeta mike at alezan.org a ?crit : Hi! I am in touch with a friend who bought a Canon MF8030c scanner/printer. I try to make the scanner work in usb. Hi, I forget to tell you what's happening when you start a scan. The scanner starts, the screen of the scanner writes read and then it hangs, no data on the computer. Thanks for help. Mike -- 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
[sane-devel] Canon MF8030c
You can use Snoopypro.exe to get a usb snoop on Windows, this is a very old program, but hopefully, still working on Vista. Download from Snoopypro from sourceforge.net here: http://sourceforge.net/projects/usbsnoop/ Read and follow exactly the instructions in SnoopyPro.exe, then try to record a scan session. = Select the device corresponding to the scanner, using its USB address 04A9:2707 There will be ~4 devices holding this address. The scanner should be the one indicated by: MF8030 ser You can recognize that it's the correct one, if you look at the frame counter in SnoopyPro, it should increment only when MF8030 is scanning. This is important ... in order to avoid having huge log files filled up with useless data! Also, choose a **small** area to scan, otherwise, there will be huge amount of data. Then, Save As ... the file (in menu), zip the log and send it back to me. Nicolas Le mercredi 21 juillet 2010 ? 21:13 +0200, Mickael Profeta a ?crit : Le Wed, 21 Jul 2010 20:25:39 +0200, Nicolas Martin nicolas0martin at gmail.com a ?crit : Do you have the possibility to get a Windows usb snoop log using SnoopyPro.exe, to check if the protocol this model uses is a Pixma one ? I can give you instructions on how to do this if needed. I do not have direct access to the scanner, but if you give reasonnable simple instructions, I think my friend can do this. And yes, there is a windows machine which can be connected with usb cable. Thanks for your answer, and if you can send me some instructions, I'll try to get that. Mike -- 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
[sane-devel] Canon PIXMA MX870
Ok, I try to imitate best the net traffic seen in Windows that you sent in the file traffic.txt on 18/7. But I made a mistake with the xml messages, so here is another try. The changes are to see if the scanner recovers from adf empty (again, seen from the Pixma dialog exchanged in the net logs) and also, limit the scan to 600dpi. let us know about the results Nicolas Le mardi 20 juillet 2010 ? 20:28 +0200, Matthias Pannek a ?crit : On Tue, 20 Jul 2010 02:12:20 +0200 Matthias Pannek matthias at pannek.de wrote: Flatbed scan is still working, but ADF not. Here a log: http://files.pannek.de/sane/adf.log Tried it again with the last pixma_mp150.c and it's working again, so it should be a problem with the new version. Thanks, Matthias -- 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: pixma_mp150.c Type: text/x-csrc Size: 50071 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100720/f06c4a61/attachment-0001.c
[sane-devel] Canon PIXMA MX870
Le dimanche 18 juillet 2010 ? 23:25 +0200, Matthias Pannek a ?crit : On Sun, 18 Jul 2010 21:34:59 +0200 Nicolas Martin nicolas0martin at gmail.com wrote: Slightly modified again file pixma_mp150.c (new attached) to add: - maximum 600 dpi for generation 4 scanners in ADF/ADF duplex mode - try to fix ADF empty scanner hanging. Not sure this will fix it, but worth a try. Could you send back the scanimage.log you get now when ADF is empty. Done, but can't access the scanner. [pixma] bjnp_open_tcp: Can not connect to scanner: Connection refused [pixma] pixma_connect() failed EINVAL [pixma] pixma_open() failed EINVAL [pixma] pixma_close(): Canon PIXMA MX870 scanimage: open of device pixma:MX870_canon.saberhage failed: Invalid argument Not sure what's wrong :( Logfiles: http://files.pannek.de/sane/failed.zip But the fail occurs before it reaches any of yesterday's modifications! Did you try to set back the last pixma_mp150.c file I sent on 16 July ? Nicolas
[sane-devel] Canon MP700 support (partially OK)
Le lundi 19 juillet 2010 ? 23:11 +0900, Gernot Hassenpflug a ?crit : Dear list, I'm currently testing a Canon PIXUS all-in-one MP700 which is similar in structure to the MP710 I had until recently (power failed, thrown out). I am using CVS, as shown by scanimage -V: scanimage (sane-backends) 1.0.22git; backend version 1.0.22 Results: Here the apparent capabilities as exposed to Xsane scanimage: Modes: Color Grayscale (no lineart, i.e. B/W) Resolutions: 75, 150, 300, 600, 1200 dpi (appears to be correct for max resolution for this device) I could successfully test color all resolutions. 300dpi I went up to A4 size, then 600 1200 half a page and 1/4 page to save time. All worked flawlessly. For Grayscale, I could work perfectly with all resolutions *except* 1200 dpi. Problem: for 1200dpi, the scanner starts to scan, perhaps 0.5 cm movement, and then it hangs, light dimly on, and power button no longer responds. With scanimage I can use Ctrl-C to cancel the scan and the scanner recovers properly: ^Cscanimage: received signal 2 scanimage: trying to stop scanner scanimage: sane_read: Operation was cancelled Looking at the partial image scanned at 1200dpi shows that it is probably not in the right format, as there are diagonal stripes to be seen (the image as such is not recognizable). I had a look at pixma_mp730.c and it is not clear to me if this is a known error or owing to untested resolution mode perhaps? I can state from memory that I did not have this issue with the MP710 which seems to follow the same protocol. On the other hand, the man page for the pixma protocol lists the Multipass MP700 and 730 rather than PIXMA MP700 730, so perhaps there is some slight difference between the models depending on where they are sold? PIXMA, PIXUS, Multipass...? Logs: The log is too large to attach here, so I am sending a tgz version to Nicolas. The log shows that suddenly the scan values become ff and in fact the USB logs with SANE_DEBUG_PIXMA=21 shows that the last line does not complete scanning, but immediately goes to some kind of error. This repeats (see below) until I press Ctrl-C and cancel the scan. Recovery is good and I can use the scanner without having to power it off and on again. [pixma] 3d70:86 80 7b 6f 6a 6a 6d 72 7a 78 7a 78 74 77 7f 7e [pixma] 3d80:7e 75 6d 69 6e 77 78 7a 79 75 74 76 7d 7d 80 7b [pixma] 3d90:75 70 6d 71 78 78 7a 78 79 7c 82 83 84 77 75 6f [pixma] 3da0:6b 70 75 78 7a 76 74 6f 73 77 79 72 6d 54 3a 35 [pixma] 3db0:30 30 ff ff ff ff ff ff ff ff ff ff ff ff ff ff [pixma] 3dc0:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [pixma] 3dd0:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [pixma] 3de0:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [pixma] 3df0:ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [pixma] 3e00:ff ff ff ff ff ff [pixma] [pixma] OUT T=7.369 len=10 [pixma] :d4 20 00 00 00 00 00 c0 04 00 [pixma] [pixma] IN T=7.372 len=6 [pixma] :06 06 00 00 00 00 [pixma] [pixma] OUT T=7.475 len=10 [pixma] :d4 20 00 00 00 00 00 c0 04 00 [pixma] [pixma] IN T=7.478 len=6 [pixma] :06 06 00 00 00 00 [pixma] [pixma] OUT T=7.581 len=10 [pixma] :d4 20 00 00 00 00 00 c0 04 00 [pixma] [pixma] IN T=7.584 len=6 [pixma] :06 06 00 00 00 00 Any comments and things to try most welcome, Regards, Gernot Hassenpflug Unless I'm wrong, 1200 dpi is not offered basically by Canon's drivers on their Pixma models, so I guess the scanner may or may not work correctly using these resolutions. MP700 is also a rather old model, and it looks performances at greater resolutions have been improved somehow, on more recent models. However, sudden change in scanned data ressembles to some hardware discrepancy, did you try maybe with another computer, is this reproducible ? Nicolas
[sane-devel] Canon PIXMA MX870
Le dimanche 18 juillet 2010 ? 00:04 +0200, Matthias Pannek a ?crit : On Sat, 17 Jul 2010 21:17:44 +0200 Nicolas Martin nicolas0martin at gmail.com wrote: Problem is, I don't see yet a solution to exit from this pitfall, need to think it over. Ok. ADF: Working until 600 DPI, i tried it with 1200 DPI and i just got a Error during read: Error during device I/O. Error and the scanner stuck with a Processing... message until Power off/on. (I know, max ADF resolution is 600 DPI) Could you take a log of this 1200 dpi sequence, normally, even if an error arises, the scan sequence should be fulfilled until the end, so maybe there's something else wrong here. In the meantime, I can add a simple a test for this model, to limit ADF scan to 600 dpi. Good idea. Here the log: http://files.pannek.de/sane/1200dpi.zip If you need a (big) log from an successful 600 dpi scan: http://files.pannek.de/sane/600dpi.zip The log show clearly that although the 1200 dpi parameter is accepted by the scanner, the ready bit never comes up (like in the 600 dpi scan), and the scan fails after the 60s timeout. I've just added some lines to force max scan when using ADF to 600 dpi, even if higher resolution is selected in the frontend. To be tested. is not executed. I will propose a fix for that to be tested. Thanks. Point is, I did not have yet any windows usb snoops for those particular cases, to confirm how the Canon driver behaves in those error situations. Can i help somehow? I have a Wireshark-log while running Windows in a VM using Canon Scangear. There is a info box while scanning without a document in the feeder and i clicked two times OK (without a document in it): http://files.pannek.de/sane/traffic.zip Strange, this Wireshark log show the Pixma protocol dialog is very short, as in the pixma backend. Unless something else is requested by the frontend, so could you get a scanimage log in the same situation, with ADF empty, so that I can compare both logs. Nicolas
[sane-devel] Canon PIXMA MX870
Slightly modified again file pixma_mp150.c (new attached) to add: - maximum 600 dpi for generation 4 scanners in ADF/ADF duplex mode - try to fix ADF empty scanner hanging. Not sure this will fix it, but worth a try. Could you send back the scanimage.log you get now when ADF is empty. Nicolas Le dimanche 18 juillet 2010 ? 16:30 +0200, Matthias Pannek a ?crit : On Sun, 18 Jul 2010 15:44:50 +0200 Nicolas Martin nicolas0martin at gmail.com wrote: I've just added some lines to force max scan when using ADF to 600 dpi, even if higher resolution is selected in the frontend. To be tested. Good :-) Strange, this Wireshark log show the Pixma protocol dialog is very short, as in the pixma backend. Unless something else is requested by the frontend, so could you get a scanimage log in the same situation, with ADF empty, so that I can compare both logs. ADF-Log: http://files.pannek.de/sane/adf.zip First ADF-Scan without paper: adf.log + wire.log After that, the scanner is stuck with Processing... Second ADF-Scan without paper: adf2.log + wire2.log The scanner itself is ready again. Third ADF-Scan: adf3.log +wire3.log Nothing happens, but scanner is still usable via Display. Thanks, Matthias -- next part -- A non-text attachment was scrubbed... Name: pixma_mp150.c Type: text/x-csrc Size: 50101 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100718/b551124a/attachment-0001.c
[sane-devel] Canon PIXMA MX870
Le vendredi 16 juillet 2010 ? 23:46 +0200, Matthias Pannek a ?crit : On Fri, 16 Jul 2010 21:51:08 +0200 Nicolas Martin nicolas0martin at gmail.com wrote: Ok, so ready for a test ? Sure :-) Then, replace the file sane-backends/backend/pixma_mp150.c with the one I've attached. I've just added a declaration for the MX870 in there. Done. Then give a try. Be careful if you have a webcam attached, it may mess up the detection and better disable in this case the v4l backend in /etc/sane.d/dll.conf Ok. Zip send back the result of scanimage.log to check how it's going. Here is the Zip: http://files.pannek.de/sane/scanimage.zip This look satisfactory at first glance, the Pixma dialog is confirmed to be a generation 4 format here. pannek at veerle ~ $ scanimage -L device `pixma:MX870_canon.saberhage' is a CANON Canon PIXMA MX870 multi-function peripheral pannek at veerle ~ $ scanimage -T scanimage: scanning image of size 638x877 pixels at 24 bits/pixel scanimage: acquiring RGB frame, 8 bits/sample scanimage: reading one scanline, 1914 bytes... PASS scanimage: reading one byte... PASS scanimage: stepped read, 2 bytes... PASS scanimage: stepped read, 4 bytes... PASS scanimage: stepped read, 8 bytes... PASS scanimage: stepped read, 16 bytes...PASS scanimage: stepped read, 32 bytes...PASS scanimage: stepped read, 64 bytes...PASS scanimage: stepped read, 128 bytes... PASS scanimage: stepped read, 256 bytes... PASS scanimage: stepped read, 512 bytes... PASS scanimage: stepped read, 1024 bytes... PASS scanimage: stepped read, 2048 bytes... PASS scanimage: stepped read, 2047 bytes... PASS scanimage: stepped read, 1023 bytes... PASS scanimage: stepped read, 511 bytes... PASS scanimage: stepped read, 255 bytes... PASS scanimage: stepped read, 127 bytes... PASS scanimage: stepped read, 63 bytes...PASS scanimage: stepped read, 31 bytes...PASS scanimage: stepped read, 15 bytes...PASS scanimage: stepped read, 7 bytes... PASS scanimage: stepped read, 3 bytes... PASS Played a little bit with skanlite and it worked nice, but after a successful 1200 DPI scan I restarted the client and now I only see a No device found message : ( pannek at veerle ~ $ 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). So could you try to get the same log file with scanimage -T , there may be something in there showing where the bjnp dialog blocks. Could you double check also if it's not a firewall issue for the 4 bjnp ports ? Nicolas
[sane-devel] Canon PIXMA MX870
Sounds good then ;-) Matthias, before I commit the changes and update the docs, did you try the ADF and ADF duplex features, and do they work fine ? (remember to set 2 pages to scan per sheet of paper in ADF when in duplex mode) Louis, nice to read from you, hope you spent good holidays, and congrats to the Netherlands who played the soccer final in South Africa! Nicolas Le samedi 17 juillet 2010 ? 13:51 +0200, Matthias Pannek a ?crit : On Sat, 17 Jul 2010 12:12:36 +0200 Louis Lagendijk louis at lagendijk.xs4all.nl wrote: This looks like a case where the scanner messed up internally. What happens when you take it of the power for 30 seconds or so and reconnect? I tried anything on the hardware (restart, ..), but it was my faul :/ So could you try to get the same log file with scanimage -T , there may be something in there showing where the bjnp dialog blocks. Could you double check also if it's not a firewall issue for the 4 bjnp ports ? Looking at the traces, BJNP works as expected, so I do not believe that the firewall may be blocking. A detailed trace withv ONLY pixma logging would be nice though. Sanei and usb logging make only for more noise and are irrelevant as you are using BJNP anyhow, so only: export SANE_DEBUG_PIXMA=11 before the actual scanning Sorry, i think there was an old dependency on the sane-backends package of my distribution because it was installed again :-( Used the patched git version again and every works fine now :-) Thanks again, Matthias -- 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
[sane-devel] Canon PIXMA MX870
Le samedi 17 juillet 2010 ? 17:36 +0200, Matthias Pannek a ?crit : On Sat, 17 Jul 2010 14:44:00 +0200 Nicolas Martin nicolas0martin at gmail.com wrote: Matthias, before I commit the changes and update the docs, did you try the ADF and ADF duplex features, and do they work fine ? (remember to set 2 pages to scan per sheet of paper in ADF when in duplex mode) First test was ADF Duplex but I forgot to set the page-count to 2, then the printer stopped after 1 page but the paper was still in the feeder. (waiting for the reverse feeder) After that the scanner/printer worked fine via the Display, but I couldn't connect to the scanner. ERROR: [pixma] pixma_collect_devices() found Canon PIXMA MX870 at bjnp://canon.saberhagen:8612 [pixma] pixma_open(): Canon PIXMA MX870 [pixma] sanei_bjnp_open(bjnp://canon.saberhagen:8612, 16843009): [pixma] bjnp_allocate_device(bjnp://canon.saberhagen:8612)[pixma] udp_command: Sending UDP command to 10.0.0.101:8612 [pixma] bjnp_open_tcp: Can not connect to scanner: Connection refused [pixma] pixma_connect() failed EINVAL [pixma] pixma_open() failed EINVAL [pixma] pixma_close(): Canon PIXMA MX870 scanimage: open of device pixma:MX870_canon.saberhage failed: Invalid argument Scanimage logfiles: http://files.pannek.de/sane/scanimage2.zip Nmap scan report for canon.saberhagen (10.0.0.101) Host is up (0.0051s latency). Not shown: 9992 closed ports PORT STATE SERVICE 137/udp open netbios-ns 138/udp open|filtered netbios-dgm 500/udp open|filtered isakmp 3702/udp open|filtered unknown 5353/udp open zeroconf 8611/udp open unknown 8612/udp open unknown 8613/udp open unknown MAC Address: 00:1E:8F:99:BD:B7 (Canon) I turned the power off and onsame problem. Then i unplugged the scanner for ~10 seconds and it worked again. Actually, this looks logical the way duplex adf scanning is implemented in Sane, as the scanner seems to be locked until it receives its start sequence, then two scan sequences for recto and verso, and then an end of scan sequence to finish. Here, it received a start, and only a single scan sequence. And no end of scan sequence. From there, the scanner seems to refuse any new network connection, as it did not finish completely the current one. So any attempts afterwards to detect and reconnect to the scanner seem to fail. Problem is, I don't see yet a solution to exit from this pitfall, need to think it over. Now for the test (xsane): Flatbed: working fine (preview/scan/cancel/) up to 2400 DPI. Ok. ADF: Working until 600 DPI, i tried it with 1200 DPI and i just got a Error during read: Error during device I/O. Error and the scanner stuck with a Processing... message until Power off/on. (I know, max ADF resolution is 600 DPI) Could you take a log of this 1200 dpi sequence, normally, even if an error arises, the scan sequence should be fulfilled until the end, so maybe there's something else wrong here. In the meantime, I can add a simple a test for this model, to limit ADF scan to 600 dpi. ADF without a paper in the feeder: Error message Error during read: Document feeder out of documents. But the scanner itself is stuck with the Processing... screen. After 5 minutes still at processing, seems there is no timeout for this. The abort key don't work, so only Power off/on helps again. I think this is because when there's no paper in ADF, the end of scan sequence (especially for generation 4 which uses an XML encapsulation) is not executed. I will propose a fix for that to be tested. Point is, I did not have yet any windows usb snoops for those particular cases, to confirm how the Canon driver behaves in those error situations. ADF Duplex 600 DPI (page count 2): working fine without a problem. Ok, nominal cases work, but some tweaks are apparently needed when error conditions are met. So let's see how we can improve that. Nicolas
[sane-devel] Canon PIXMA MX870
Ok, so ready for a test ? Let's assume MX870 is a somehow a MX860, and uses the generation 4 Pixma protocol. First, download the latest Sane git version. You should get a sane-backends folder. Then, replace the file sane-backends/backend/pixma_mp150.c with the one I've attached. I've just added a declaration for the MX870 in there. ./configure with the correct options, make, install. Help here for that: http://mp610.blogspot.com/2008/04/give-your-scanner-new-freshly-sane.html Then give a try. Be careful if you have a webcam attached, it may mess up the detection and better disable in this case the v4l backend in /etc/sane.d/dll.conf Use the following commands to get logs: $ export SANE_DEBUG_SANEI_USB=255 $ export SANE_DEBUG=255 $ export SANE_DEBUG_PIXMA=11 $ scanimage -L 2 scanimage1.log $ scanimage -T 2 scanimage2.log Zip send back the result of scanimage.log to check how it's going. Nicolas Le vendredi 16 juillet 2010 ? 09:24 +0200, Matthias Pannek a ?crit : Hello, i'm a owner of a PIXMA MX870 and it would be really nice to have Sane support for this scanner :-( The MX870 should be a slightly modified MX860 (who is supported right now). I'm not sure about the bjnp-Protocol, because there is no TCP port 8612 open on this device. But the devices uses UDP 8612 for communication. Host is up (0.00045s latency). Not shown: 131060 closed ports PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 137/udp open netbios-ns 138/udp open|filtered netbios-dgm 500/udp open|filtered isakmp 3702/udp open|filtered unknown 5353/udp open zeroconf 8611/udp open unknown 8612/udp open unknown 8613/udp open unknown MAC Address: 00:1E:8F:99:BD:xx (Canon) Here a tcpdump of a Preview-scan using Windows in a VM: http://files.pannek.de/log.txt Here a tcpdump after the start of xsane: http://files.pannek.de/xsane.txt There is communication between sane and my scanner. This is the Printer Identiy: %E at zr e !BmBJNP0UUMFG:Canon;CMD:MultiPass 2.1,IVEC;MDL:MX870 series;CLS:IMAGE;DES:Canon MX870 series; Thank you, Matthias -- 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: pixma_mp150.c Type: text/x-csrc Size: 49567 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100716/58632411/attachment-0001.c
[sane-devel] Testing on Canon MF6580PL
I took a look at the process list you sent, but difficult for me to tell which one is involved with the usb port used by the Pixma device, as I don't know anything about 50% of them, and the names do not help too much to know what they are used for. Unfortunately, no other idea for the moment, on how to locate this process, which seems to lock the usb port. Nicolas Le mercredi 14 juillet 2010 ? 09:13 +, twain43 at hotmail.com a ?crit : Morning, here are some results, along with the steps I took to obtain them: 1. Uninstalled the canon printer from System Preferences, trashed the drivers and killed the UFR II Backgrounder service; 2. Make uninstalled all frontends and backends (I'm keeping the source, just in case); 3. Rebooted; 4. Pulled down yesterday's git snapshot, added the ugly pixma patch, modded the NDEBUG statements for pixma files; 5. Compiled and installed both frontends and backends; 6. Ran Activity Monitor and kept it on the background; 7. Ran scanimage in Terminal as superuser, while using Activity Monitor to save the list of running processes and daemons at the moment of the test. Not posting the usual pixma and all-export logs, since they read as usual. Instead, I'm attaching Activity Monitor's log: maybe you'll spot something more than I didAFAICS, there's nothing wrong: the only two suspicious processes are TWAINBridge and Image Capture Extension. The first one appears as soon as I connect the printer to the USB, and can't be killed, so I'm guessing it must be OS-related. I killed the second one and rerun the scantest, but got no different log results. Hope you can spot something more out of it. Twain28 __ From: twain43 at hotmail.com To: nicolas0martin at gmail.com Date: Tue, 13 Jul 2010 14:32:44 + CC: sane-devel at lists.alioth.debian.org Subject: Re: [sane-devel] Testing on Canon MF6580PL I'm not a Mac expert myself, but I'll poke around things and see what I can do Twain28 __ Date: Tue, 13 Jul 2010 10:35:51 +0200 Subject: Re: [sane-devel] Testing on Canon MF6580PL From: nicolas0martin at gmail.com To: twain43 at hotmail.com CC: sane-devel at lists.alioth.debian.org The process here under is probably not an application, but runs in background, it may be a printing daemon or service started after boot, which locks access to the usb port. I really know nothing about Mac OS X, to help you find it, maybe stop a printing service would help. Nicolas 2010/7/13 twain43 at hotmail.com I'm running the command from terminal at system boot, so there really should not be anything else openis there some way to check this, anyway, so that I might be sure of it? Thank you for your patience Twain28 __ Date: Mon, 12 Jul 2010 18:45:03 +0200 Subject: Re: [sane-devel] Testing on Canon MF6580PL From: nicolas0martin at gmail.com To: twain43 at hotmail.com CC: sane-devel at lists.alioth.debian.org Well, not exactly something new, the 2 logs are somehow equivalent, but one gives a little bit more details: [pixma] en1 is not a valid IPv4 interface, skipping... [pixma] en1 is IPv4 capable, sending broadcast.. [pixma] scanner discovery finished... [pixma] pixma_open(): Canon imageClass MF6500 [sanei_usb] sanei_usb_open: trying to open device `libusb:005:002-04a9-2686-00-00' usb_os_open: 04a9:2686 usb_os_open(USBDeviceOpenSeize): another process has device opened for exclusive access usb_set_configuration: called for config 1 USB error: usb_set_configuration(SetConfiguration): device not opened for exclusive access [sanei_usb] sanei_usb_open: libusb complained: usb_set_configuration(SetConfiguration): device not opened for exclusive access usb_os_close: 04a9:2686 [pixma] pixma_connect() failed EINVAL [pixma] pixma_open() failed EINVAL [pixma] pixma_close(): Canon imageClass MF6500 scanimage: open of device pixma:04A92686 failed: Invalid argument And I think we're back to a few messages ago in this thread, so first, could you locate this other process (maybe printer ?) which locks the usb device, and stop it ? Nicolas 2010/7/12 twain43 at hotmail.com Ditto: here are the new logs. Something new sprouted out, at their very endhope it's useful. Twain28
[sane-devel] Testing on Canon MF6580PL
The process here under is probably not an application, but runs in background, it may be a printing daemon or service started after boot, which locks access to the usb port. I really know nothing about Mac OS X, to help you find it, maybe stop a printing service would help. Nicolas 2010/7/13 twain43 at hotmail.com I'm running the command from terminal at system boot, so there really should not be anything else openis there some way to check this, anyway, so that I might be sure of it? Thank you for your patience Twain28 -- Date: Mon, 12 Jul 2010 18:45:03 +0200 Subject: Re: [sane-devel] Testing on Canon MF6580PL From: nicolas0martin at gmail.com To: twain43 at hotmail.com CC: sane-devel at lists.alioth.debian.org Well, not exactly something new, the 2 logs are somehow equivalent, but one gives a little bit more details: [pixma] en1 is not a valid IPv4 interface, skipping... [pixma] en1 is IPv4 capable, sending broadcast.. [pixma] scanner discovery finished... [pixma] pixma_open(): Canon imageClass MF6500 [sanei_usb] sanei_usb_open: trying to open device `libusb:005:002-04a9-2686-00-00' usb_os_open: 04a9:2686 usb_os_open(USBDeviceOpenSeize): *another process has device opened for exclusive access* usb_set_configuration: called for config 1 USB error: usb_set_configuration(SetConfiguration): device not opened for exclusive access [sanei_usb] sanei_usb_open: libusb complained: usb_set_configuration(SetConfiguration): device not opened for exclusive access usb_os_close: 04a9:2686 [pixma] pixma_connect() failed EINVAL [pixma] pixma_open() failed EINVAL [pixma] pixma_close(): Canon imageClass MF6500 scanimage: open of device pixma:04A92686 failed: Invalid argument And I think we're back to a few messages ago in this thread, so first, could you locate this other process (maybe printer ?) which locks the usb device, and stop it ? Nicolas 2010/7/12 twain43 at hotmail.com Ditto: here are the new logs. Something new sprouted out, at their very endhope it's useful. Twain28 -- Non sei a casa? Accedi a Messenger dal Web.http://www.messenger.it/web/default.aspx -- 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 -- Non sei a casa? Accedi a Messenger dal Web.http://www.messenger.it/web/default.aspx -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100713/e8b28038/attachment.htm
