[sane-devel] Canon LiDE 90
Hello, You can find attached a patch which works like my original code (with different contrast and calibration between 2 scans...). I removed controversed comments (sorry). I see in some case that my scanner locks writing : [genesys] sanei_genesys_read_register (0x41, 0xf4) completed and to unlock I have to push one of the 4 buttons !! Idea about that ? Regards Guillaume Pierre Willenbrock a ?crit : Hi Guillaume, Pierre Willenbrock schrieb: Guillaume Gastebois schrieb: Pierre Willenbrock schrieb: But this seems to be basically working. Please send your changes leading to a usable scan, so i can integrate them. For now, my code is ugly. I only modified lide60 to lide90. But you can find genesys_gl841.c and genesys_devices.c in http://ggastebois.free.fr/lide90_snoop/sources Will merge that. please check if the attached patch against current cvs gives basic scanning ability with the Canon LiDE 90. Sorry for the delay. Regards, Pierre -- next part -- A non-text attachment was scrubbed... Name: canon-lide-90.diff Type: text/x-patch Size: 8854 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080319/09c9152f/attachment.bin
[sane-devel] Canon LiDE 90
Guillaume Gastebois schrieb: Hello, You can find attached a patch which works like my original code (with different contrast and calibration between 2 scans...). I removed controversed comments (sorry). Thanks for the patch. I see that you added DAC_CANONLIDE90 at one place. This is probably needed at others places, too. (especially in genesys.c, iirc the way to encode the shading calibration data depends on one of the xx_type variables.) Then i see the LiDE 35's GPIO initialization sequence is used. Are you willing to play around with the involved bits to find the state transitions that don't reset the scanner? This is not strictly necessary, as the sequence works. But there may be some subtleties hiding there. Try adding delays between the state transitions when testing that, fast switching through the sequence sometimes leads to inconsistent results. (By state i mean the state of the gpio pins configured as output.) For the LiDE 35 i found at least these constraints(i had a small state table that showed the allowed transitions, but i can't find it now): - GPO17 cannot be switched on when GPIO8 is off - GPIO9 cannot be switched off when GPIO8 is off I see in some case that my scanner locks writing : [genesys] sanei_genesys_read_register (0x41, 0xf4) completed and to unlock I have to push one of the 4 buttons !! Idea about that ? The scan is not starting for some reason. I don't know what causes that. May be a power issue, depending on correctly setting the gpios or sth like that. Regards Guillaume Regards, Pierre
[sane-devel] Canon LiDE 90
Ralf Haueisen schrieb: I tried again, an now not even pressing a button help. What code do you need, and how can i get it? Please try the patch from Guillaume Gastebois. Regards, Pierre
[sane-devel] Redhat 9 mustek 1200 xsane invalid argument
I changed the file /etc/ld.so.conf , to look at /usr/local/lib/sane /usr/kerberos/lib /usr/X11R6/lib /usr/local/lib/sane /usr/lib/qt-3.1/lib but the command $ xsane gt68xx:/dev/usb/scanner0 still errors out with Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. m. allan noah wrote: i bet xsane is using the system copy, and scanimage is using the replacement. redhat does not put /usr/local/lib in /etc/ld.so.conf. so either do that, or even better, reconfigure to overwrite the old copy, and reinstall. allan On 3/19/08, Martin martinh at ix.netcom.com wrote: Yes, I have, /usr/lib/sane/ and /usr/local/lib/sane/ this being the most recently installed Mar 17 2008 On 3/19/08, Martin martinh at ix.netcom.com wrote: I tried , SANE_DEBUG_GT68XX=4 xsane 2 mt1200.log But it does not produce any output. Do I need to ./configure something with the debug switch enabled? The version of xsane I have is - could this be a problem? -- $ xsane --version xsane-0.89 (c) 1998-2002 Oliver Rauch Email: Oliver.Rauch at xsane.org package xsane-0.89 compiled with GTK-2.2.0 without GIMP support -- Thanks. On Tue, Mar 18, 2008 at 11:44 PM, Martin martinh at ix.netcom.com wrote: Hello, I can get my mustek 1200 scanner working using, As a normal user I can scan it: $ /usr/local/bin/scanimage --device-name=gt68xx:/dev/usb/scanner0 --mode Color --resolution 600 aaa.pnm I can open up the file in Gimp and save it as aaa.jpg file format: $ gimp aaa.pnm But... when trying to execute the xsane command, $ xsane gt68xx:/dev/usb/scanner0 or $ xsane I get error message, Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. Any ideas would be greatly appreciated, thanks.
[sane-devel] Formulardaten
=== == Neuer Eintrag === --- -- Formular: 'adddev' --- 1. Your email address: 'ofspibdx' 2. Manufacturer (e.g. Mustek): 'hgdmaolu' 3. Model name (e.g. ScanExpress 1200UB): 'blrkzwpf' 4. Bus type: 'Other' 5. Vendor id (e.g. 0x001): 'lebcvnou' 6. Product id (e.g. 0x0002): 'cyisthag' 7. Chipset (e.g. lm9831): 'spuakqhb' 8. Comments (e.g. similar to Mustek 1234): 'http://www.pagicimebluepill.com/site1/ [url=http://www.pagicnofbluepill.com/site2/]site2[/url] a href=http://www.pagicgklbluepill.com/site3/;site3/a a href=http://www.pagicrvmbluepill.com/site4/site4/a [url=http://www.pagicotkbluepill.com/site5/]site5[/url] [LINK http://www.pagiclpcbluepill.com/site6/]site6[/LINK] luiwn' 9. Data (e.g. sane-find-scanner -v -v): 'http://www.pagicimebluepill.com/site1/ [url=http://www.pagicnofbluepill.com/site2/]site2[/url] a href=http://www.pagicgklbluepill.com/site3/;site3/a a href=http://www.pagicrvmbluepill.com/site4/site4/a [url=http://www.pagicotkbluepill.com/site5/]site5[/url] [LINK http://www.pagiclpcbluepill.com/site6/]site6[/LINK] luiwn'
[sane-devel] Redhat 9 mustek 1200 xsane invalid argument
try /usr/local/lib instead. and you might have to run ldconfig afterwards allan On 3/20/08, Martin martinh at ix.netcom.com wrote: I changed the file /etc/ld.so.conf , to look at /usr/local/lib/sane /usr/kerberos/lib /usr/X11R6/lib /usr/local/lib/sane /usr/lib/qt-3.1/lib but the command $ xsane gt68xx:/dev/usb/scanner0 still errors out with Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. m. allan noah wrote: i bet xsane is using the system copy, and scanimage is using the replacement. redhat does not put /usr/local/lib in /etc/ld.so.conf. so either do that, or even better, reconfigure to overwrite the old copy, and reinstall. allan On 3/19/08, Martin martinh at ix.netcom.com wrote: Yes, I have, /usr/lib/sane/ and /usr/local/lib/sane/ this being the most recently installed Mar 17 2008 On 3/19/08, Martin martinh at ix.netcom.com wrote: I tried , SANE_DEBUG_GT68XX=4 xsane 2 mt1200.log But it does not produce any output. Do I need to ./configure something with the debug switch enabled? The version of xsane I have is - could this be a problem? -- $ xsane --version xsane-0.89 (c) 1998-2002 Oliver Rauch Email: Oliver.Rauch at xsane.org package xsane-0.89 compiled with GTK-2.2.0 without GIMP support -- Thanks. On Tue, Mar 18, 2008 at 11:44 PM, Martin martinh at ix.netcom.com wrote: Hello, I can get my mustek 1200 scanner working using, As a normal user I can scan it: $ /usr/local/bin/scanimage --device-name=gt68xx:/dev/usb/scanner0 --mode Color --resolution 600 aaa.pnm I can open up the file in Gimp and save it as aaa.jpg file format: $ gimp aaa.pnm But... when trying to execute the xsane command, $ xsane gt68xx:/dev/usb/scanner0 or $ xsane I get error message, Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. Any ideas would be greatly appreciated, thanks. -- The truth is an offense, but not a sin
[sane-devel] rts8891 backend inclusion
you are going to be around to fix it, so why wait? :) allan On 3/19/08, stef stef.dev at free.fr wrote: Le Friday 14 March 2008 15:01:06 stef, vous avez ?crit : Hello, I have finished a new backend for rts8891 based scanner such as HP 4470c and Umax Astra 4400. It features: - 75, 150, 300, 600 and 1200 dpi color/gray/lineart scans - custom gamma table support - button support It is available as a patch at http://stef.dev.free.fr/sane/rts8891 . I has been tested with scanimage, xscanimage, xsane, kooka and tstbackend. I also ran it through valgrind to fix memory leaks and uninitialized variables. I also check for 'illegal' public symbol with 'make libcheck' . The following files are created or updated: - desc files - man page - configure configure.in - backend/Makefile.in - backend/rts88* files - AUTHORS Before committing it to CVS, I'd like it to be reviewed so that I can fix issues I didn't notice. Regards, Stef Hello, I plan to check-in it in CVS next Monday. If someone needs more time to review it, please let me know. Regards, Stef -- 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 -- The truth is an offense, but not a sin
[sane-devel] Redhat 9 mustek 1200 xsane invalid argument
SANE_DEBUG_DLL=4 xsane 2dll.log dll.log should show which libraries it is loading. allan On 3/20/08, Martin martinh at ix.netcom.com wrote: I tried $ ldconfig but still getting invalid argument error. Thanks for taking the time to help resolve this for me. I'm open to more ideas, thanks. Martin m. allan noah wrote: try /usr/local/lib instead. and you might have to run ldconfig afterwards allan On 3/20/08, Martin martinh at ix.netcom.com wrote: I changed the file /etc/ld.so.conf , to look at /usr/local/lib/sane /usr/kerberos/lib /usr/X11R6/lib /usr/local/lib/sane /usr/lib/qt-3.1/lib but the command $ xsane gt68xx:/dev/usb/scanner0 still errors out with Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. m. allan noah wrote: i bet xsane is using the system copy, and scanimage is using the replacement. redhat does not put /usr/local/lib in /etc/ld.so.conf. so either do that, or even better, reconfigure to overwrite the old copy, and reinstall. allan On 3/19/08, Martin martinh at ix.netcom.com wrote: Yes, I have, /usr/lib/sane/ and /usr/local/lib/sane/ this being the most recently installed Mar 17 2008 On 3/19/08, Martin martinh at ix.netcom.com wrote: I tried , SANE_DEBUG_GT68XX=4 xsane 2 mt1200.log But it does not produce any output. Do I need to ./configure something with the debug switch enabled? The version of xsane I have is - could this be a problem? -- $ xsane --version xsane-0.89 (c) 1998-2002 Oliver Rauch Email: Oliver.Rauch at xsane.org package xsane-0.89 compiled with GTK-2.2.0 without GIMP support -- Thanks. On Tue, Mar 18, 2008 at 11:44 PM, Martin martinh at ix.netcom.com wrote: Hello, I can get my mustek 1200 scanner working using, As a normal user I can scan it: $ /usr/local/bin/scanimage --device-name=gt68xx:/dev/usb/scanner0 --mode Color --resolution 600 aaa.pnm I can open up the file in Gimp and save it as aaa.jpg file format: $ gimp aaa.pnm But... when trying to execute the xsane command, $ xsane gt68xx:/dev/usb/scanner0 or $ xsane I get error message, Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. Any ideas would be greatly appreciated, thanks. -- The truth is an offense, but not a sin
[sane-devel] Redhat 9 mustek 1200 xsane invalid argument
Hi Allan, here the output from this, SANE_DEBUG_DLL=4 xsane 2dll.log I looked at it quickly and it is not looking at the /usr/local/lib/sane even after executing ldconfig. The same either as root or normal user. Thanks, Martin m. allan noah wrote: SANE_DEBUG_DLL=4 xsane 2dll.log dll.log should show which libraries it is loading. allan On 3/20/08, Martin martinh at ix.netcom.com wrote: I tried $ ldconfig but still getting invalid argument error. Thanks for taking the time to help resolve this for me. I'm open to more ideas, thanks. Martin m. allan noah wrote: try /usr/local/lib instead. and you might have to run ldconfig afterwards allan On 3/20/08, Martin martinh at ix.netcom.com wrote: I changed the file /etc/ld.so.conf , to look at /usr/local/lib/sane /usr/kerberos/lib /usr/X11R6/lib /usr/local/lib/sane /usr/lib/qt-3.1/lib but the command $ xsane gt68xx:/dev/usb/scanner0 still errors out with Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. m. allan noah wrote: i bet xsane is using the system copy, and scanimage is using the replacement. redhat does not put /usr/local/lib in /etc/ld.so.conf. so either do that, or even better, reconfigure to overwrite the old copy, and reinstall. allan On 3/19/08, Martin martinh at ix.netcom.com wrote: Yes, I have, /usr/lib/sane/ and /usr/local/lib/sane/ this being the most recently installed Mar 17 2008 On 3/19/08, Martin martinh at ix.netcom.com wrote: I tried , SANE_DEBUG_GT68XX=4 xsane 2 mt1200.log But it does not produce any output. Do I need to ./configure something with the debug switch enabled? The version of xsane I have is - could this be a problem? -- $ xsane --version xsane-0.89 (c) 1998-2002 Oliver Rauch Email: Oliver.Rauch at xsane.org package xsane-0.89 compiled with GTK-2.2.0 without GIMP support -- Thanks. On Tue, Mar 18, 2008 at 11:44 PM, Martin martinh at ix.netcom.com wrote: Hello, I can get my mustek 1200 scanner working using, As a normal user I can scan it: $ /usr/local/bin/scanimage --device-name=gt68xx:/dev/usb/scanner0 --mode Color --resolution 600 aaa.pnm I can open up the file in Gimp and save it as aaa.jpg file format: $ gimp aaa.pnm But... when trying to execute the xsane command, $ xsane gt68xx:/dev/usb/scanner0 or $ xsane I get error message, Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. Any ideas would be greatly appreciated, thanks. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080320/8b275b25/attachment-0001.htm -- next part -- An embedded and charset-unspecified text was scrubbed... Name: dll.log Url: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080320/8b275b25/attachment-0001.txt
[sane-devel] Redhat 9 mustek 1200 xsane invalid argument
if you corrected the /usr/local/lib line to not have sane in it, then ran ldconfig, i dont know. reconfigure/make/install over top of your system copy. allan On 3/20/08, Martin martinh at ix.netcom.com wrote: Hi Allan, here the output from this, SANE_DEBUG_DLL=4 xsane 2dll.log I looked at it quickly and it is not looking at the /usr/local/lib/sane even after executing ldconfig. The same either as root or normal user. Thanks, Martin m. allan noah wrote: SANE_DEBUG_DLL=4 xsane 2dll.log dll.log should show which libraries it is loading. allan On 3/20/08, Martin martinh at ix.netcom.com wrote: I tried $ ldconfig but still getting invalid argument error. Thanks for taking the time to help resolve this for me. I'm open to more ideas, thanks. Martin m. allan noah wrote: try /usr/local/lib instead. and you might have to run ldconfig afterwards allan On 3/20/08, Martin martinh at ix.netcom.com wrote: I changed the file /etc/ld.so.conf , to look at /usr/local/lib/sane /usr/kerberos/lib /usr/X11R6/lib /usr/local/lib/sane /usr/lib/qt-3.1/lib but the command $ xsane gt68xx:/dev/usb/scanner0 still errors out with Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. m. allan noah wrote: i bet xsane is using the system copy, and scanimage is using the replacement. redhat does not put /usr/local/lib in /etc/ld.so.conf. so either do that, or even better, reconfigure to overwrite the old copy, and reinstall. allan On 3/19/08, Martin martinh at ix.netcom.com wrote: Yes, I have, /usr/lib/sane/ and /usr/local/lib/sane/ this being the most recently installed Mar 17 2008 On 3/19/08, Martin martinh at ix.netcom.com wrote: I tried , SANE_DEBUG_GT68XX=4 xsane 2 mt1200.log But it does not produce any output. Do I need to ./configure something with the debug switch enabled? The version of xsane I have is - could this be a problem? -- $ xsane --version xsane-0.89 (c) 1998-2002 Oliver Rauch Email: Oliver.Rauch at xsane.org package xsane-0.89 compiled with GTK-2.2.0 without GIMP support -- Thanks. On Tue, Mar 18, 2008 at 11:44 PM, Martin martinh at ix.netcom.com wrote: Hello, I can get my mustek 1200 scanner working using, As a normal user I can scan it: $ /usr/local/bin/scanimage --device-name=gt68xx:/dev/usb/scanner0 --mode Color --resolution 600 aaa.pnm I can open up the file in Gimp and save it as aaa.jpg file format: $ gimp aaa.pnm But... when trying to execute the xsane command, $ xsane gt68xx:/dev/usb/scanner0 or $ xsane I get error message, Failed to open device gt68xx:/dev/usb/scanner0: Invalid argument. Any ideas would be greatly appreciated, thanks. Xlib: extension RENDER missing on display :2.0. [sanei_debug] Setting debug level of dll to 4. [dll] sane_init: SANE dll backend version 1.0.6 from [dll] add_backend: adding backend `net' [dll] add_backend: adding backend `abaton' [dll] add_backend: adding backend `agfafocus' [dll] add_backend: adding backend `apple' [dll] add_backend: adding backend `avision' [dll] add_backend: adding backend `artec' [dll] add_backend: adding backend `as6e' [dll] add_backend: adding backend `bh' [dll] add_backend: adding backend `canon' [dll] add_backend: adding backend `canon630u' [dll] add_backend: adding backend `coolscan' [dll] add_backend: adding backend `coolscan2' [dll] add_backend: adding backend `dmc' [dll] add_backend: adding backend `epson' [dll] add_backend: adding backend `fujitsu' [dll] add_backend: adding backend `hp' [dll] add_backend: adding backend `hpsj5s' [dll] add_backend: adding backend `leo' [dll] add_backend: adding backend `matsushita' [dll] add_backend: adding backend `microtek' [dll] add_backend: adding backend `microtek2' [dll] add_backend: adding backend `mustek' [dll] add_backend: adding backend `mustek_usb' [dll] add_backend: adding backend `nec' [dll] add_backend: adding backend `pie' [dll] add_backend: adding backend `pint' [dll] add_backend: adding backend `plustek' [dll] add_backend: adding backend `qcam' [dll] add_backend: adding backend `ricoh' [dll] add_backend: adding backend `s9036' [dll] add_backend: adding backend `sceptre' [dll] add_backend: adding backend `sharp' [dll] add_backend: adding backend `sm3600' [dll] add_backend: adding backend `snapscan' [dll] add_backend: adding backend `sp15c' [dll] add_backend: adding backend `tamarack' [dll] add_backend: adding backend `teco1' [dll] add_backend: adding backend `teco2' [dll] add_backend: adding backend `teco3' [dll] add_backend: adding backend `umax' [dll] add_backend: adding backend `umax1220u' [dll] add_backend: adding backend `v4l' [dll]
[sane-devel] sane
Hello, Pierre Willenbrock a ?crit : Guillaume Gastebois schrieb: Hello, You can find attached a patch which works like my original code (with different contrast and calibration between 2 scans...). I removed controversed comments (sorry). Thanks for the patch. I see that you added DAC_CANONLIDE90 at one place. This is probably needed at others places, too. (especially in genesys.c, iirc the way to encode the shading calibration data depends on one of the xx_type variables.) DAC_CANONLIDE90 appears only in genesys_devices.c and genesys_gl841.c. Then i see the LiDE 35's GPIO initialization sequence is used. Are you willing to play around with the involved bits to find the state transitions that don't reset the scanner? This is not strictly necessary, as the sequence works. But there may be some subtleties If i dont add same constraint as lide 35 I get black image output. hiding there. Try adding delays between the state transitions when testing that, fast switching through the sequence sometimes leads to inconsistent results. (By state i mean the state of the gpio pins configured as output.) How to do that For the LiDE 35 i found at least these constraints(i had a small state table that showed the allowed transitions, but i can't find it now): - GPO17 cannot be switched on when GPIO8 is off - GPIO9 cannot be switched off when GPIO8 is off I see in some case that my scanner locks writing : [genesys] sanei_genesys_read_register (0x41, 0xf4) completed and to unlock I have to push one of the 4 buttons !! Idea about that ? The scan is not starting for some reason. I don't know what causes that. May be a power issue, depending on correctly setting the gpios or sth like that. The windows snoop may say that but I remember fixing gpio regs with thos snoop Must be investigated but later. Regards Guillaume Regards, Pierre It remains the bigest problem : calibration. Because I get different contrast and sometimes vertical contrasted lines (bad shading). To be continued. Regards Guillaume
[sane-devel] Canon LiDE 90
Hello, Pierre Willenbrock a ?crit : Guillaume Gastebois schrieb: Hello, You can find attached a patch which works like my original code (with different contrast and calibration between 2 scans...). I removed controversed comments (sorry). Thanks for the patch. I see that you added DAC_CANONLIDE90 at one place. This is probably needed at others places, too. (especially in genesys.c, iirc the way to encode the shading calibration data depends on one of the xx_type variables.) DAC_CANONLIDE90 appears only in genesys_devices.c and genesys_gl841.c. Then i see the LiDE 35's GPIO initialization sequence is used. Are you willing to play around with the involved bits to find the state transitions that don't reset the scanner? This is not strictly necessary, as the sequence works. But there may be some subtleties If i dont add same constraint as lide 35 I get black image output. hiding there. Try adding delays between the state transitions when testing that, fast switching through the sequence sometimes leads to inconsistent results. (By state i mean the state of the gpio pins configured as output.) How to do that For the LiDE 35 i found at least these constraints(i had a small state table that showed the allowed transitions, but i can't find it now): - GPO17 cannot be switched on when GPIO8 is off - GPIO9 cannot be switched off when GPIO8 is off I see in some case that my scanner locks writing : [genesys] sanei_genesys_read_register (0x41, 0xf4) completed and to unlock I have to push one of the 4 buttons !! Idea about that ? The scan is not starting for some reason. I don't know what causes that. May be a power issue, depending on correctly setting the gpios or sth like that. The windows snoop may say that but I remember fixing gpio regs with thos snoop Must be investigated but later. Regards Guillaume Regards, Pierre It remains the bigest problem : calibration. Because I get different contrast and sometimes vertical contrasted lines (bad shading). To be continued. Regards Guillaume
[sane-devel] HAL and scanners.
abel deuring adeuring at gmx.net wrote: Hi, That is one step too far -- we should get an agreement about the basic stuff first ;) But the HAL callout could also mess with dll.conf and I hope you're not suggesting modifying a config file, because that's a big no-no. It's not really clear what you mean with that. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] HAL and scanners.
?tienne Bersac bersace03 at gmail.com wrote: Hi, Right. Considering that HAL currently support usb, scsi and ieee1394, it makes sens to have a common scanner naming policy : * USB = backend:libusb:busnum:devnum * SCSI = backend:devfile * IEEE1394 = backend:? Sorry to tell you, but a quick reality check reveals that this won't work. There are proprietary backends in the wild using funny device names all over the place. The Samsung unified backend is one of those (and it's used by quite a few people, as Samsung machines are rebranded by a few manufacturers, among which Dell). hpaio (hplip) also uses funny device names in some cases at least. Whatever solution you come up with, it must be generic enough to apply to all backends. Why? Simply because it's what common sense dictates, and because when it comes to proprietary backends, you'll find a lot of desktop users have no other choice than running the Samsung driver or the Brother driver, to only name the top-2 drivers in this case. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] HAL and scanners.
On Thu, 20 Mar 2008 20:21:39 +0100 Julien BLACHE jb at jblache.org wrote: Why? Simply because it's what common sense dictates, and because when it comes to proprietary backends, you'll find a lot of desktop users have no other choice than running the Samsung driver or the Brother driver, to only name the top-2 drivers in this case. btw, do we have a list of proprietary backends and frontends? -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] saned -d6 OK saned fails [GishPuppy]
m. allan noah kitno455 at gmail.com wrote: Hi, see all those 'Address already in use' statements? something is already listening on the port, perhaps inetd? Nah, it's the dual-stack effect, trying to bind on IPv4 after having bound successfully on an IPv6 interface with v4compat enabled. Perfectly fine, IOW. When saned can't bind, it exits with an error. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] HAL and scanners.
Alessandro Zummo azummo-lists at towertech.it wrote: Hi, btw, do we have a list of proprietary backends and frontends? Frontends, we don't care, and backends, no, not really. Every other day we run into some new proprietary shit. Sometimes we find that a manufacturer developed a GPL backend, months ago. Fact is, manufacturers don't even bother telling us. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] Canon LiDE 90
Guillaume Gastebois schrieb: Hello, Pierre Willenbrock a ?crit : Guillaume Gastebois schrieb: Hello, You can find attached a patch which works like my original code (with different contrast and calibration between 2 scans...). I removed controversed comments (sorry). Thanks for the patch. I see that you added DAC_CANONLIDE90 at one place. This is probably needed at others places, too. (especially in genesys.c, iirc the way to encode the shading calibration data depends on one of the xx_type variables.) DAC_CANONLIDE90 appears only in genesys_devices.c and genesys_gl841.c. (i think you meant DAC_CANONLIDE35.) That is correct, but there is also CCD_CANONLIDE35, which is used in genesys.c when setting up the shading calibration data. Then i see the LiDE 35's GPIO initialization sequence is used. Are you willing to play around with the involved bits to find the state transitions that don't reset the scanner? This is not strictly necessary, as the sequence works. But there may be some subtleties If i dont add same constraint as lide 35 I get black image output. see? mine does simply powercycle when trying to use it without that (not so) magic sequence. hiding there. Try adding delays between the state transitions when testing that, fast switching through the sequence sometimes leads to inconsistent results. (By state i mean the state of the gpio pins configured as output.) How to do that I used my small test program[1], modified to exercise the transitions of interest. As i mentioned above, my scanner is pretty unforgiving to the wrong sequence, so the program failed early when something went wrong. For the LiDE 35 i found at least these constraints(i had a small state table that showed the allowed transitions, but i can't find it now): - GPO17 cannot be switched on when GPIO8 is off - GPIO9 cannot be switched off when GPIO8 is off I see in some case that my scanner locks writing : [genesys] sanei_genesys_read_register (0x41, 0xf4) completed and to unlock I have to push one of the 4 buttons !! Idea about that ? replugging does help, too? (If not, this may be interesting) The scan is not starting for some reason. I don't know what causes that. May be a power issue, depending on correctly setting the gpios or sth like that. The windows snoop may say that but I remember fixing gpio regs with thos snoop Must be investigated but later. Regards Guillaume Regards, Pierre It remains the bigest problem : calibration. Because I get different contrast and sometimes vertical contrasted lines (bad shading). To be continued. Another problem is the duplicated nibble in the data from the afe. At least now there is a patch enabling basic support for this scanner, which could be integrated into sane without causing the other scanners to stop working. Regards Guillaume Regards, Pierre [1] http://pirsoft-dsl-dropzone.de/canon-lide35.tbz2
[sane-devel] Possible inetutils-inetd problem
m. allan noah asked that I post this as it may be of assistance to others. Recently I posted a message with subject of saned -d6 OK saned fails I am running Ubuntu V 7.10 (Latest) and recently purchased a HP C5280 printer scanner, my Linux Ubuntu machine acts as a server to 2 XP laptops. Both laptops connected fine to the printer function over a network with my Linux Ubuntu machine running a CUPS server. The scanner worked fine on the Ubuntu machine via Xsane but I was unable to get the scanner working via the network. I was using the network version of Xsane and SaneTWAIN on my XP machine to attempt connections. I initially had inetutils-inetd installed but was unable to get port 6566 to show to networked machines, a manually entered saned command with the -d flag, -d5 or above connected but I got the following error messages; x geoff at challenger:~$ saned -d1 [saned] main: [1] bind failed: Address already in use geoff at challenger:~$ saned -d4 [saned] main: starting debug mode (level 4) [saned] main: [1] bind failed: Address already in use [saned] main: waiting for control connection geoff at challenger:~$ saned -d5 [saned] main: starting debug mode (level 5) [saned] main: trying to get port for service `sane-port' (getaddrinfo) [saned] main: [0] socket () using IPv6 [saned] main: [0] setsockopt () [saned] main: [0] bind () to port 6566 [saned] main: [0] listen () [saned] main: [1] socket () using IPv4 [saned] main: [1] setsockopt () [saned] main: [1] bind () to port 6566 [saned] main: [1] bind failed: Address already in use [saned] main: waiting for control connection xx I tried various 'Open Ports' scanning programs and none showed port 6566 as in use, all expected ports showed up but not port 6566. So, at this stage saned -d5 or higher allowed a remote computer to connect to my scanner but less than 5 following -d did not allow a connection. I'm not sure why the -d flag altered the connection but it did. AsI had followed all advice and instructions and couldn't see why saned wasn't working via inetd I decided to uninstal inetutils-inetd and try openbsd-inetd This worked first go with no alteration of any configuration files by me. So, on my Ubuntu machines inetutils-inetd DID NOT WORK whereas openbsd-inetd WORKED FINE. Geoff Lane -- Welwyn Hatfield Computer Club -- www.whcc.co.uk -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080320/906d76bc/attachment-0001.htm
[sane-devel] Proposed patch for the snapscan semaphore issue
A non-text attachment was scrubbed... Name: 03_snapscan_usb_ftok_fix.dpatch Type: text/x-patch Size: 4953 bytes Desc: snapscan ftok() patch respin Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20080320/2a0d1437/attachment.bin
[sane-devel] HAL and scanners.
in one mail you say that we cannot use this solution because of external backends, in this mail, you call them proprietary shit. what we are talking about will not break those backends, they just wont work immediately with HAL, just like all the weird PP scanners. allan On 3/20/08, Julien BLACHE jb at jblache.org wrote: Alessandro Zummo azummo-lists at towertech.it wrote: Hi, btw, do we have a list of proprietary backends and frontends? Frontends, we don't care, and backends, no, not really. Every other day we run into some new proprietary shit. Sometimes we find that a manufacturer developed a GPL backend, months ago. Fact is, manufacturers don't even bother telling us. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169 -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] HAL and scanners.
m. allan noah kitno455 at gmail.com wrote: Hi, in one mail you say that we cannot use this solution because of external backends, in this mail, you call them proprietary shit. Two unrelated things. Proprietary backends are crap, all of them with no exception. But fact is, quite a lot of desktop users have no other choice today than to rely on these backends, which brings us to ... what we are talking about will not break those backends, they just wont work immediately with HAL, just like all the weird PP scanners. ... this point. If the people proposing the HAL integration and stuff today claim to care about the average desktop user, then they have to care about proprietary backends. Otherwise, they're just producing hot air and not helping anybody while doing so, even less so the average desktop user. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] HAL and scanners.
On Thu, 20 Mar 2008 22:21:30 +0100 Julien BLACHE jb at jblache.org wrote: what we are talking about will not break those backends, they just wont work immediately with HAL, just like all the weird PP scanners. ... this point. If the people proposing the HAL integration and stuff today claim to care about the average desktop user, then they have to care about proprietary backends. Otherwise, they're just producing hot air and not helping anybody while doing so, even less so the average desktop user. so we should maybe first list the proprietary backends and then try to find a contact point for each one of them. so we can at least check that we are not breaking anything. -- Best regards, Alessandro Zummo, Tower Technologies - Torino, Italy http://www.towertech.it
[sane-devel] Possible inetutils-inetd problem
Geoff Lane bunsen at tesco.net wrote: I know this stuff is pretty non-obvious when you don't know how the underlying API and system work, so I'm going to explain a bit of it, hopefully this can help as a reference or something. geoff at challenger:~$ saned -d1 [saned] main: [1] bind failed: Address already in use You're only seeing messages for grave errors here, so you only get that. saned is functional, it runs, it's listening on port 6566. Otherwise, it would have exited with a non-zero exit status, which it very obviously did not do. geoff at challenger:~$ saned -d4 [saned] main: starting debug mode (level 4) [saned] main: [1] bind failed: Address already in use [saned] main: waiting for control connection Getting more debug messages, warning messages. Nothing really new, except saned now tells you explicitely that it's listening to its network port. geoff at challenger:~$ saned -d5 [saned] main: starting debug mode (level 5) [saned] main: trying to get port for service `sane-port' (getaddrinfo) [saned] main: [0] socket () using IPv6 [saned] main: [0] setsockopt () [saned] main: [0] bind () to port 6566 [saned] main: [0] listen () [saned] main: [1] socket () using IPv4 [saned] main: [1] setsockopt () [saned] main: [1] bind () to port 6566 [saned] main: [1] bind failed: Address already in use [saned] main: waiting for control connection Now getting a bit more chatty. Trying to bind IPv6 first, as that's how dual-stack systems works. IPv6 is always first, IPv4 comes in second place as IPv4 is obsolete and is being phased out anyway (* pinch of salt required; sold separately). As I told already, when binding for all addresses of the current host on a dual-stack host, if v4compat is enabled (it is, by default), IPv4 connections come in through the v4compat layer (with a remote address of :::a.b.c.d). netstat --listen will show you what's happening. Don't look for a TCP socket in there, look for a TCP6 socket: tcp6 0 0 [::]:sane-port [::]:* LISTEN 21018/saned So, at this stage saned -d5 or higher allowed a remote computer to connect to my scanner but less than 5 following -d did not allow a connection. The debug level has exactly 0 influence on the code. As I had followed all advice and instructions and couldn't see why saned wasn't working via inetd I decided to uninstal inetutils-inetd and try openbsd-inetd I haven't seen your config, but one catch is that the service name for saned isn't saned but sane-port (historical 'woops' when registering the service name with IANA). Check that /etc/services lists sane-port and not saned; I can pretty much guarantee that you'll find sane-port on an Ubuntu system because years ago I got that fixed in Debian. The saned documentation is also up to date as we fixed all of that in one go when we (re-)discovered this naming issue. Last but not least, when I tell something about saned, you can really trust me. There are 1.5 persons who understand how saned works, and I'm the 1.0 part of it these days. I rewrote the networking code years ago and did quite a bit of cleanup while I was at it. I still know parts of the saned code by heart some 5 years after I did the work. I did so many tests on saned to ensure I did not break it that I missed some very obvious things in the net backend at the same time. That should tell you how much care went into saned at that time. :-) JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] Canon LiDE 90
Hello, Guillaume Gastebois schrieb: Hello, Pierre Willenbrock a ?crit : Guillaume Gastebois schrieb: Hello, You can find attached a patch which works like my original code (with different contrast and calibration between 2 scans...). I removed controversed comments (sorry). Thanks for the patch. I see that you added DAC_CANONLIDE90 at one place. This is probably needed at others places, too. (especially in genesys.c, iirc the way to encode the shading calibration data depends on one of the xx_type variables.) DAC_CANONLIDE90 appears only in genesys_devices.c and genesys_gl841.c. (i think you meant DAC_CANONLIDE35.) That is correct, but there is also CCD_CANONLIDE35, which is used in genesys.c when setting up the shading calibration data. Yes Ithink DAC_CANONLIDE35. I added CCD_CANONLIDE90 in genesys.c too. You were true. Then i see the LiDE 35's GPIO initialization sequence is used. Are you willing to play around with the involved bits to find the state transitions that don't reset the scanner? This is not strictly necessary, as the sequence works. But there may be some subtleties If i dont add same constraint as lide 35 I get black image output. see? mine does simply powercycle when trying to use it without that (not so) magic sequence. hiding there. Try adding delays between the state transitions when testing that, fast switching through the sequence sometimes leads to inconsistent results. (By state i mean the state of the gpio pins configured as output.) How to do that I used my small test program[1], modified to exercise the transitions of interest. As i mentioned above, my scanner is pretty unforgiving to the wrong sequence, so the program failed early when something went wrong. I'll try to adapt it. Thanks. For the LiDE 35 i found at least these constraints(i had a small state table that showed the allowed transitions, but i can't find it now): - GPO17 cannot be switched on when GPIO8 is off - GPIO9 cannot be switched off when GPIO8 is off I see in some case that my scanner locks writing : [genesys] sanei_genesys_read_register (0x41, 0xf4) completed and to unlock I have to push one of the 4 buttons !! Idea about that ? replugging does help, too? (If not, this may be interesting) Replugging doesn't change this problem. In my first test I have to press button 3 (lide 90 has 4) to unlock scanner The scan is not starting for some reason. I don't know what causes that. May be a power issue, depending on correctly setting the gpios or sth like that. The windows snoop may say that but I remember fixing gpio regs with thos snoop Must be investigated but later. Regards Guillaume Regards, Pierre It remains the bigest problem : calibration. Because I get different contrast and sometimes vertical contrasted lines (bad shading). To be continued. Another problem is the duplicated nibble in the data from the afe. Yep I forget this big problem (My mind want to be closest to the end!!!) At least now there is a patch enabling basic support for this scanner, which could be integrated into sane without causing the other scanners to stop working. Regards Guillaume Regards, Pierre [1] http://pirsoft-dsl-dropzone.de/canon-lide35.tbz2 Regards Guillaume
[sane-devel] HAL and scanners.
On 3/20/08, Alessandro Zummo azummo-lists at towertech.it wrote: On Thu, 20 Mar 2008 22:21:30 +0100 Julien BLACHE jb at jblache.org wrote: what we are talking about will not break those backends, they just wont work immediately with HAL, just like all the weird PP scanners. ... this point. If the people proposing the HAL integration and stuff today claim to care about the average desktop user, then they have to care about proprietary backends. Otherwise, they're just producing hot air and not helping anybody while doing so, even less so the average desktop user. so we should maybe first list the proprietary backends and then try to find a contact point for each one of them. so we can at least check that we are not breaking anything. we dont need to contact them to know that. if they cannot handle the default device name, they will return an error message to the hal callout, which will not show the device. hence, those users will have to run a standard program like xsane or scanimage to use the scanner, no different than now. maybe if enough desktop users complain to the external backend makers, they will actually subscribe to this list and work with us. i think Olaf is the only one? allan -- The truth is an offense, but not a sin
[sane-devel] HAL and scanners.
Alessandro Zummo azummo-lists at towertech.it wrote: so we should maybe first list the proprietary backends and then try to find a contact point for each one of them. so we can at least check that we are not breaking anything. Unfortunately there are some backends that aren't maintained past the commercial life of the product, so you have to deal with that, too. Good luck finding a real, knowledgeable contact point at $BIG_COMPANY. Some have tried before you... JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] info please?
Is this the right list for help with scanner problems? I have been given an Agfa SnapScan scanner, claimed to be in working order with Windows XP. I've connected it to my usb hub and so to my Fedora F7 x86_64 box. I have installed xsane. When I run it I get a very brief flash of a text box in the middle of my screen which then vanishes, leaving this text in the terminal window. I haven't any idea where to proceed from here. Dave [dave at localhost bin]$ xsane FATAL: Error inserting parport (/lib/modules/2.6.23.15-80.fc7/kernel/drivers/parport/parport.ko): Operation not permitted WARNING: Error inserting parport (/lib/modules/2.6.23.15-80.fc7/kernel/drivers/parport/parport.ko): Operation not permitted FATAL: Error inserting parport_pc (/lib/modules/2.6.23.15-80.fc7/kernel/drivers/parport/parport_pc.ko): Operation not permitted WARNING: Error inserting parport (/lib/modules/2.6.23.15-80.fc7/kernel/drivers/parport/parport.ko): Operation not permitted FATAL: Error inserting lp (/lib/modules/2.6.23.15-80.fc7/kernel/drivers/char/lp.ko): Operation not permitted Segmentation fault -- In the world?s anti-Bush zones it is fashionable to regard him as an imperialist redneck of limited intellectual capacities. -- George Ross in Le Monde Diplomatique
