[sane-devel] Sane doesn't create a scanner device
On Wednesday 26 October 2005 13:59, dark_m...@gmx.net wrote: It finally works fully. I had to export the /usr/local/bin path and put the sane-config script there. Then it worked all well. Finally it was worth all the effort ... :D which versions of sane and iscan or epson are you using. Which cvs and where did you get it?
[sane-devel] SANE will not recognize scanner device
Hello, On Oct 26 22:01 Thuis wrote (shortened): I get a [plustek] sanei_access_lock failed: 11 See http://lists.alioth.debian.org/pipermail/sane-devel/2005-August/014301.html Which exact lock directory it is in your case may depend on how your particular RPM was built. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de 90409 Nuernberg, GermanyWWW: http://www.suse.de/
[sane-devel] Sane doesn't create a scanner device
Hello, On Oct 26 18:38 Henning Meier-Geinitz wrote (shortened): On Wed, Oct 26, 2005 at 05:14:43PM +0200, dark_m...@gmx.net wrote: [sanei_usb] sanei_usb_open: trying to open device `libusb:001:002' USB error: could not set config 1: Device or resource busy [sanei_usb] sanei_usb_open: libusb complained: could not set config 1: Device or resource busy [sanei_usb] Maybe the kernel scanner driver claims the scanner's interface? See bug report #302207: https://alioth.debian.org/tracker/index.php?func=detailaid=302207group_id=30186atid=410366 I would like to have you informed about what I found out, see https://bugzilla.novell.com/show_bug.cgi?id=127524#c17 For some all-in-one devices (like the Epson Stylus Photo RX420) which have also a cardreader unit included there is additionally the usb_storage kernel module which gets in conflict with SANE. In particular for me the ignoring EBUSY from USB in SANE didn't work when both usblp and usb_storage are loaded but it works when only usblp is loaded. At least for me for printing and scanning ignoring EBUSY from USB is a good workaround but it seems to be not the final solution. From my point of view the problem lies somehow deeper in the USB system (or how the USB system is used) but I am no USB expert so that I don't know at the moment what exactly causes the conflict and what a clean solution would be. Olaf, regarding Iscan: The Iscan sources contain sanei/sanei_usb.c and this must also be changed so that the epkowa backend also ignores EBUSY from USB, see http://cvs.alioth.debian.org/cgi-bin/cvsweb.cgi/sane-backends/sanei/sanei_usb.c.diff?r1=1.42r2=1.43cvsroot=sane Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de 90409 Nuernberg, GermanyWWW: http://www.suse.de/
[sane-devel] Still trying to get Epson CX6600 to work.
Hello, On Oct 25 13:09 russbucket wrote (shortened): On Monday 24 October 2005 23:55, Johannes Meixner wrote: On Oct 24 15:49 russbucket wrote (shortened): I tried iscan 17.0, Iscan-free 17.0 and the iscan that came with my SuSE 10.0 DVD. ... The printer woks, and the scanner was working under SuSE 9.1 Do you know about https://bugzilla.novell.com/show_bug.cgi?id=127524 Try if you can scan after rmmod usblp which will make printing impossible. See https://bugzilla.novell.com/show_bug.cgi?id=127524#c17 Try if you can scan with the original Suse Linux 10.0 sane and iscan packages after rmmod usblp rmmod usb-storage Probably it doesn't help to only install new package versions. You must watch the messages in /var/log/messages which show you which kernel module is in conflict with SANE in your particular case, see the initial comment in https://bugzilla.novell.com/show_bug.cgi?id=127524 and comment #17 https://bugzilla.novell.com/show_bug.cgi?id=127524#c17 Alternatively install the new packages ftp://ftp.suse.com/pub/people/jsmeix/unsupported/sane/10.0/RPMS/ sane-1.0.15-20.1.i586.ignore-EBUSY-from-USB.rpm ftp://ftp.suse.com/pub/people/jsmeix/unsupported/iscan/10.0/RPMS/ iscan-1.15.0.2-4.1.i586.ignore-EBUSY-from-USB.rpm and try if scanning works out-of-the-box and if not, try if scanning works after rmmod usb-storage or after rmmod whatever_is_in_conflict_with_SANE. Furthermore: Regarding hotplug,udev,HAL,resmgr,whatever,... for scanners and Suse Linux, see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html Basics and libusb + resmgr + PAM and http://portal.suse.com/sdb/en/2005/09/jsmeix_scanner-setup-100.html Change regarding the access permissions for USB scanners via resmgr For scanner access as normal user with Suse Linux we use resmgr in our version of libusb to grant the access. As resmgr runs as root only resmgr must be configured to grant access for normal users (i.e. there is no need for hotplug). Therefore regarding scanner access with resmgr see http://portal.suse.com/sdb/en/2004/10/jsmeix_scanner-setup-92.html for Suse Linux 9.1 9.2 and 9.3 and http://portal.suse.com/sdb/en/2005/09/jsmeix_scanner-setup-100.html for Suse Linux 10.0 Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsm...@suse.de 90409 Nuernberg, GermanyWWW: http://www.suse.de/
[sane-devel] Need suggestion for a good debugger
On Wed, 26 Oct 2005 08:44:46 -0400 Patrick Lessard patrick.less...@cogeco.com wrote: Any suggestion for a good debugger so I can trace the program step by step? I use gdb and its GUI ddd, I'm not aware of any alternatives. You'll want to turn off optimisation when compiling sane, and it's much easier to use a command-line sane frontend than a GUI one. Martin
[sane-devel] Need suggestion for a good debugger
On 10/27/05, Martin Collins mar...@mkcollins.org wrote: I use gdb and its GUI ddd, I'm not aware of any alternatives. If you have the kde libs installed, kdbg is a nice frontend to gdb too. -- Miguel Bazdresch
[sane-devel] Need suggestion for a good debugger
I'll take a look at that Thanks everyone. Patrick. -Message d'origine- De : sane-devel-boun...@lists.alioth.debian.org [mailto:sane-devel-boun...@lists.alioth.debian.org]De la part de Miguel Bazdresch Envoy? : 27 octobre, 2005 07:50 ? : sane-devel@lists.alioth.debian.org Objet : Re: [sane-devel] Need suggestion for a good debugger On 10/27/05, Martin Collins mar...@mkcollins.org wrote: I use gdb and its GUI ddd, I'm not aware of any alternatives. If you have the kde libs installed, kdbg is a nice frontend to gdb too. -- Miguel Bazdresch -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] Supported =3200 dpi scanners
Which current USB, =3200 dpi scanners able to scan films/slides are well supported by SANE (or by other, possibly proprietary but freely available frontends)? I know of Epson PF 3490 and 3590 which work more or less according to recent posts, but how about other types/brands? Levente PS: It would be nice if the scanner search engine would list the maximal working resolution of each scanner it contains.
[sane-devel] TR: Calibration, need infos, comments, screenshots included
Hello, I'm beginning understanding the backend code for my Umax scanner. Now I've included 2 screenshots, one is the find_zero.pgm, which is where is detect the black stripe and the other is the calibration strip, both under the scanner's lid. The find_zero.pgm seems fine, but not the calibration.pgm. My question is, what should the calibration.pgm image should look like? Should it be a plain grey image all the way long? Thank you. Patrick. -- next part -- A non-text attachment was scrubbed... Name: calibration.zip Type: application/octet-stream Size: 33109 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051027/b827095f/calibration-0001.obj From patrick.less...@cogeco.com Thu Oct 27 15:49:34 2005 From: patrick.less...@cogeco.com (Patrick Lessard) Date: Thu Oct 27 15:56:57 2005 Subject: [sane-devel] Calibration, need infos, comments, screenshots included Message-ID: 76c55c5a07e6584697014a0b710bdabb05e20...@tr-exch-1.intranet.cgocable.ca Hello, I'm beginning understanding the backend code for my Umax scanner. Now I've included 2 screenshots, one is the find_zero.pgm, which is where is detect the black stripe and the other is the calibration strip, both under the scanner's lid. The find_zero.pgm seems fine, but not the calibration.pgm. My question is, what should the calibration.pgm image should look like? Should it be a plain grey image all the way long? Thank you. Patrick. -- next part -- A non-text attachment was scrubbed... Name: calibration.zip Type: application/octet-stream Size: 42919 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051027/bff2ce88/calibration-0001.obj From gar...@iwr.fzk.de Thu Oct 27 15:58:12 2005 From: gar...@iwr.fzk.de (Ariel Garcia) Date: Thu Oct 27 15:58:44 2005 Subject: [sane-devel] Nikon LS50 In-Reply-To: 200510170956.59265.gar...@iwr.fzk.de References: 200510170956.59265.gar...@iwr.fzk.de Message-ID: 200510271758.12647.gar...@iwr.fzk.de Hi, here is the patch for adding support for the Nikon LS50/LS5000. It applies on top of the backends/coolscan2.c file of sane-1.0.16 I also uploaded a precompiled library to http://cvs.fzk.de/~ariel/linux/libsane-coolscan2.so.1.0.16 it is only one file which you could use to replace the one in /usr/lib/sane/libsane-coolscan2.so.1.0.16 No warranties that this will work, but you can try if you want to avoid patching and compiling sane. This patch worked for me and should in principle enable for the LS50/5000 exactly the same functionality that the older LS40/4000 scanners have in Sane.I tested it only with scanimage, because kooka and xscanimage were not behaving correctly (although that has nothing to do with LS50 support), and getting the right exposure with scanimage seems to be tricky. Also, it seemed to me that the scans i made were not correctly in focus, but that could be some other issue. Testers welcome! :-) Cheers, Ariel -- next part -- A non-text attachment was scrubbed... Name: cs2-ls50-full.patch Type: text/x-diff Size: 7274 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20051027/e97f1129/cs2-ls50-full.bin From lan...@gmail.com Thu Oct 27 20:33:18 2005 From: lan...@gmail.com (lando) Date: Thu Oct 27 20:33:26 2005 Subject: [sane-devel] HP Scanjet 4890 Message-ID: 9210553f0510271333l220b58c5hff7f5e433229c...@mail.gmail.com It appears that there is not a driver for the HP 4890 scanner... I'll write one up. Can someone direct me to a skeleton program from which to build from? ie, what functions do I need to support with what interface etc? Lando
[sane-devel] Epson 2480/2580: Testers needed
Hi, Argh, my 2480 is changing to 5.5cm by 7.5cm (judging from the preview window). Debug log attached. That's very strange. It can either be 5.5 cm x 8 cm or 5.5 cm x 12.0 cm. Everything else is, well, extremely unlikely. Please send me the file scanimage.txt, resulting from executing scanimage --source=Transparency Adapter --help 1scanimage.txt BTW, is this correct: $ sane-config --version 1.0.16 I installed today's cvs over 1.0.16; I did 'make uninstall' first. Yes, your installation is fine. You're definitely using the new version. /Oliver
[sane-devel] Canon CanoScan LiDE 35
Today, I checked out a CVS copy of the sane-backends, and compiled it all with genesys support. Unfortunately it hangs when i try scanimage (debug output:) [genesys] sanei_genesys_create_slope_table: 8 steps, step_type = 0, exposure_time = 250, same_speed =0 [genesys] sanei_genesys_create_slope_table: yres = 600.00 [genesys] sanei_genesys_create_slope_table: returns sum_time=371, completed [genesys] sanei_genesys_create_slope_table: 255 steps, step_type = 1, exposure_time = 250, same_speed =0 [genesys] sanei_genesys_create_slope_table: yres = 600.00 [genesys] sanei_genesys_create_slope_table: returns sum_time=9767, completed [genesys] sanei_genesys_write_register (0x0e, 0x00) completed [genesys] sanei_genesys_bulk_write_register (size = 162) *hang* [genesys] sanei_genesys_bulk_write_register: failed while writing bulk data: Error during device I/O scanimage: open of device genesys:libusb:004:006 failed: Error during device I/O The problem seems to be occuring in genesys_gl841.c, ~4390: /* Write initial registers */ RIE (sanei_genesys_bulk_write_register (dev, dev-reg, GENESYS_GL841_MAX_REGS * 2)); Any ideas? I think read previously in the mailing list that gl841 support is nearing completion... Thanks in advance :) -- Cameron Harris
