[sane-devel] (no subject)
Hi, I have been trying to use the latest saned trough busybox inetd. And I have ran across some serious problems, if i run saned -d it works just fine both to find and use the scanner, but as soon as i try to use it trough inetd it refuses. I running a cross compiler for saned.My run environment is:i386,Uclibc 0.9.18,kernel linux 2.4.25. I have followed the saned guide on the website, this is what i have added: /etc/services: sane6566/tcpsaned # scanning service /etc/inetd.conf: sanestream tcp nowait root/usr/sbin/saned saned /etc/sane.d/net.conf: localhost 192.168.0.1(my computer IP) /etc/sane.d/saned.conf: + (when i tried without tcpd i used localhost and the IP of my workstation) When i try to run SANE_DEBUG_NET=128 scanimage -L from my workstation (or from the server itself) i get: [sanei_debug] Setting debug level of net to 128. [net] sane_init: authorize = 0x8049260, version_code = 0xb548 [net] sane_init: SANE net backend version 1.0.6 from sane-backends-1.0.7 [net] sane_init: Client has little endian byte order [net] sane_init: determining sane service port [net] sane_init: found port 6566 [net] sane_init: searching for config file [net] sane_init: trying to add 192.168.0.1 [net] add_device: adding backend 192.168.0.1 [net] add_device: backend 192.168.0.1 added [net] sane_init: done reading config [net] sane_init: evaluating environment variable SANE_NET_HOSTS [net] sane_init: done [net] sane_get_devices: local_only = 0 [net] connect_dev: trying to connect to 192.168.0.1 [net] connect_dev: connection succeeded [net] connect_dev: sanei_w_init [net] connect_dev: net_init (user=(null), local version=1.0.3) [net] connect_dev: argument marshalling error (Connection reset by peer) [net] connect_dev: closing connection to 192.168.0.1 [net] sane_get_devices: ignoring failure to connect to 192.168.0.1 [net] sane_get_devices: finished (0 devices) 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). [net] sane_exit: exiting [net] sane_exit: closing dev 0x805e5b8, ctl=-1 [net] sane_exit: finished. When i try to run telnet 192.168.0.1 from other PC. [root@localhost ~]# telnet 192.168.0.1 6566 Trying 192.168.0.1... Connected to 192.168.0.1 (192.168.0.1). Escape character is '^]'. Connection closed by foreign host. But I run ./busybox telnet 127.0.0.1 6566 on my PC .It is fine.The saned can run. why ? Thanks for a great app anyways. Jacket _ ÂÊÏȳ¢ÊÔ Windows Live Mail¡£ http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
[sane-devel] inetd and saned problem
Hi, I have been trying to use the latest saned trough busybox inetd. And I have ran across some serious problems, if i run saned -d it works just fine both to find and use the scanner, but as soon as i try to use it trough inetd it refuses. I running a cross compiler for saned.My run environment is:i386,Uclibc 0.9.18,kernel linux 2.4.25. I have followed the saned guide on the website, this is what i have added: /etc/services: sane6566/tcpsaned # scanning service /etc/inetd.conf: sanestream tcp nowait root/usr/sbin/saned saned /etc/sane.d/net.conf: localhost 192.168.0.1(my computer IP) /etc/sane.d/saned.conf: + (when i tried without tcpd i used localhost and the IP of my workstation) When i try to run SANE_DEBUG_NET=128 scanimage -L from my workstation (or from the server itself) i get: [sanei_debug] Setting debug level of net to 128. [net] sane_init: authorize = 0x8049260, version_code = 0xb548 [net] sane_init: SANE net backend version 1.0.6 from sane-backends-1.0.7 [net] sane_init: Client has little endian byte order [net] sane_init: determining sane service port [net] sane_init: found port 6566 [net] sane_init: searching for config file [net] sane_init: trying to add 192.168.0.1 [net] add_device: adding backend 192.168.0.1 [net] add_device: backend 192.168.0.1 added [net] sane_init: done reading config [net] sane_init: evaluating environment variable SANE_NET_HOSTS [net] sane_init: done [net] sane_get_devices: local_only = 0 [net] connect_dev: trying to connect to 192.168.0.1 [net] connect_dev: connection succeeded [net] connect_dev: sanei_w_init [net] connect_dev: net_init (user=(null), local version=1.0.3) [net] connect_dev: argument marshalling error (Connection reset by peer) [net] connect_dev: closing connection to 192.168.0.1 [net] sane_get_devices: ignoring failure to connect to 192.168.0.1 [net] sane_get_devices: finished (0 devices) 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). [net] sane_exit: exiting [net] sane_exit: closing dev 0x805e5b8, ctl=-1 [net] sane_exit: finished. When i try to run telnet 192.168.0.1 from other PC. [root@localhost ~]# telnet 192.168.0.1 6566 Trying 192.168.0.1... Connected to 192.168.0.1 (192.168.0.1). Escape character is '^]'. Connection closed by foreign host. But I run ./busybox telnet 127.0.0.1 6566 on my PC .It is fine.The saned can run. why ? Thanks for a great app anyways. Jacket _ ÂÊÏȳ¢ÊÔ Windows Live Mail¡£ http://ideas.live.com/programpage.aspx?versionId=5d21c51a-b161-4314-9b0e-4911fb2b2e6d
[sane-devel] Debug output from Lexmark X1270 scanner
Le mardi 25 juillet 2006 01:00, Fred Odendaal a ?crit?: The X1270 is not supported by the X1100 backend. You are somewhat correct in your assumption of what is happening. The scanner is trying to find the home position by scanning in the reverse direction - looking for a set pattern off the glass. If it can't find it, it will make a loud noise as the scan head bangs against the end. This is bad for your scanner, so I'd advise against continuing to try it. regards, Fred Odendaal Hello Fred, by the way, what are your plans regarding the experimental version of the lexmark backend ? It has the inital groundwork needed for multi-models support. Also it has some improvements such as calibration and arbitrary scan size area. As far I understood, the blocking point you got was calibration tuning for your model. Did you have some time to give a look ? Regards, Stef
[sane-devel] gl646 doc update
Hello, I've put up an updated (codeflow+some tricks to extract picturs from usblogs) documention for genesys backend -for the GL646 part- at: http://perso.modulonet.fr/~stefdev/sane/gl646-wip02.odt I plan to add howt to fill the Genesys_Sensor struct with valeus from usb log, allthough fields name are allready explanatory. Regards, Stef
[sane-devel] gl646 doc update
Hi, On 7/27/06, St?phane VOLTZ stef...@modulonet.fr wrote: Hello, I've put up an updated (codeflow+some tricks to extract picturs from usblogs) documention for genesys backend -for the GL646 part- at: http://perso.modulonet.fr/~stefdev/sane/gl646-wip02.odt I plan to add howt to fill the Genesys_Sensor struct with valeus from usb log, allthough fields name are allready explanatory. Any work for me? I want to complete HP2400 backend as early as possible. I have hardware but the only problem i am facing is warmup time exceed and head moves further scan area. Still not understood how can i solve after taking so many logs and observing slope and gamma values. Regards, Parag. -- 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] Front Configuration.
I would like to know, how front-end gets the list of all available backends on the system? does it look directly into dll.conf file or communicates with sane daemon to get the list of available backends? Rupesh -- Message: 5 Date: Wed, 26 Jul 2006 07:50:04 -0400 (EDT) From: m. allan noah an...@pfeiffer.edu Subject: Re: [sane-devel] backend configuration error. To: sane-devel@lists.alioth.debian.org Message-ID: pine.lnx.4.61.0607260745200.31...@limos.pfeiffer.edu Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed try using the DBG macro in your backend to print some messages from within sane_init() and sane_get_devices(). then call: SANE_DEBUG_BACKENDNAME=255 scanimage -L Replace BACKENDNAME with name of your backend in all caps. if you dont see your messages, then the dll backend may not be loading your backend. try using `strace scanimage -L` to be sure. allan On Wed, 26 Jul 2006, Rupesh Tarpara wrote: Hi, I have hand held image scanner which is a USB-ACM device and uses standard ACM driver (serial communication protocol over USB interface). The device file created by driver is /dev/input/ttyACM0 (virtual serial device). Following is the build procedure I have followed. I have downloaded sane-backends 1.0.18 source and made the following changes to incorporate my device: 1. I have created a new backend source file for this device. 2. I have modified sane-backends-1.0.18/configure.in and sane-backends-1.0.18/backend/Makefile.in files to include my backend. 3. executed autoconf, ./configure, make and make install 4. all libraries were installed at /usr/local/lib/sane I modified the /usr/local/etc/sane.d/dll.conf file to include my backend name. I am using Xsane as frontend. When I run Xsane, it gives error message as no devices available --- My queries, 1) are there any backend configuration steps which I might have skipped? 2) What is the procedure frontend follows when it is executed? 3) How does the communication happens (or initiates) between Frontend backend -- device? 4) What are the steps to be followed for new backend installation? - Additional information about OS and sane version I am using. I am using RedHat AS3 OS, following is the output of uname -a [root@mypc root]# uname -a Linux mypc.home.com 2.4.21-40.EL #1 Thu Feb 2 22:32:00 EST 2006 i686 i686 i386 GNU/Linux [root@mypc root]# scanimage --version scanimage (sane-backends) 1.0.18; backend version 1.0.18 Regards, Rupesh http://www.patni.com World-Wide Partnerships. World-Class Solutions. _ This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netad...@patni.com and delete this mail. _ -- so don't tell us it can't be done, putting down what you don't know. money isn't our god, integrity will free our souls - Max Cavalera -- ___ sane-devel mailing list sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel End of sane-devel Digest, Vol 13, Issue 32 ** http://www.patni.com World-Wide Partnerships. World-Class Solutions. _ This e-mail message may contain proprietary, confidential or legally privileged information for the sole use of the person or entity to whom this message was originally addressed. Any review, e-transmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this e-mail in error kindly delete this e-mail from your records. If it appears that this mail has been forwarded to you without proper authority, please notify us immediately at netad...@patni.com and delete this mail. _ From panem...@gmail.com Thu Jul 27 12:23:19 2006 From: panem...@gmail.com (=?UTF-8?Q?Parag_N(=E0=A4=AA=E0=A4=B0=E0=A4=BE=E0=A5=9A)?=) Date: Thu Jul 27 12:23:32 2006 Subject: [sane-devel] Front Configuration. In-Reply-To: 002501c6b174$662e4970$9c09a...@patni.com
[sane-devel] Mustek 1200 CP not working with sane 1.0.17 on FreeBSD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
I've got an Mustek 1200 CP Scanner wich is connected to my computers
parallelport. I'm using FreeBSD 6.0 and the sane-version from the ports
collection. This is actually version 1.0.17. According to
http://sane-project.org/sane-backends.html#S-MUSTEK-PP the scanner
should be supported good.
I have libieee1284 on my system installed.
I compiled my sane with libieee1284 and --enable-parport-directio
Now, when I run sane-find-scanner -p it can't find my scanner. I get
same result when I run scanimage -L
I'm doing all this as root, so there should no access/rights problem.
Parallelport support is enabled in my kernel and according to dmesg my
port (0x378 / EPP (tried without EPP too)) is recognized by the system.
I modified dll.conf to activate mustek_pp and made an entry in
mustek_pp.conf:
scanner mustek * cis1200
I also tried 0x378, ppi0, /dev/ppi0 instead of the asterisk for the device.
After fiddeling with the debuglevels I got the result following result.
Sorry for the large block: I didn't know wich part is important. This
run was with autoprobing in my mustek_pp.conf.
If anyone has an idea what to do I would appreciate this very much.
Greetings, Sven
su-2.05b# scanimage -L
[sanei_debug] Setting debug level of mustek_pp to 128.
[mustek_pp] sane-mustek_pp, version 0.13-beta. build for SANE 1.0.17
[mustek_pp] backend by Jochen Eisinger jochen.eisin...@gmx.net
[sanei_debug] Setting debug level of sanei_pa4s2 to 128.
[sanei_pa4s2] sanei_pa4s2_devices: interface called for the first time
[sanei_pa4s2] sanei_pa4s2_devices: invoked
[sanei_pa4s2] pa4s2_init: static int first_time = 1
[sanei_pa4s2] pa4s2_init: called for the first time
[sanei_pa4s2] pa4s2_init: initializing libieee1284
[sanei_pa4s2] pa4s2_init: 3 ports reported by IEEE 1284 library
[sanei_pa4s2] pa4s2_init: port 0 is `0x278`
[sanei_pa4s2] pa4s2_init: port 1 is `0x378`
[sanei_pa4s2] pa4s2_init: port 2 is `0x3bc`
[sanei_pa4s2] pa4s2_init: allocating port list
[sanei_pa4s2] pa4s2_init: initialized successfully
[mustek_pp] sanei_init: auto probing port
[sanei_pa4s2] sanei_pa4s2_open: called for device '0x278'
[sanei_pa4s2] sanei_pa4s2_open: trying to connect to port
[sanei_pa4s2] pa4s2_open: trying to attach dev `0x278`
[sanei_pa4s2] pa4s2_init: static int first_time = 0
[sanei_pa4s2] pa4s2_init: sanei already initalized
[sanei_pa4s2] pa4s2_open: looking up port in list
[sanei_pa4s2] pa4s2_open: port is in list at port[0]
[sanei_pa4s2] pa4s2_open: setting up port data
[sanei_pa4s2] pa4s2_open: name=0x278 in_use=SANE_TRUE
[sanei_pa4s2] pa4s2_open: enabled=SANE_FALSE mode=PA4S2_MODE_NIB
[sanei_pa4s2] pa4s2_open: opening device
[sanei_pa4s2] pa4s2_open: device `0x278` opened...
[sanei_pa4s2] pa4s2_open: returning SANE_STATUS_GOOD
[sanei_pa4s2] pa4s2_open: open dev `0x278` as fd 0
[sanei_pa4s2] sanei_pa4s2_open: connected to device using fd 0
[sanei_pa4s2] sanei_pa4s2_open: checking for scanner
[sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 1
[sanei_pa4s2] sanei_pa4s2_enable: enable port '0x278'
[sanei_pa4s2] pa4s2_enable: prelock[] = {0xf8, 0xf8, 0x05}
[sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_open: reading ASIC id
[sanei_pa4s2] sanei_pa4s2_readbegin: called for fd 0 and register 0
[sanei_pa4s2] sanei_pa4s2_readbegin: NIB readbegin
[sanei_pa4s2] pa4s2_readbegin_nib: selecting register 0 at '0x278'
[sanei_pa4s2] sanei_pa4s2_readbegin: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_readbyte: called with fd 0
[sanei_pa4s2] sanei_pa4s2_readbyte: we hope, the backend called
[sanei_pa4s2] sanei_pa4s2_readbyte: readbegin, so the port is ok...
[sanei_pa4s2] sanei_pa4s2_readbyte: this means, I did not check it - it's
[sanei_pa4s2] sanei_pa4s2_readbyte: not my fault, if your PC burns down.
[sanei_pa4s2] sanei_pa4s2_readbyte: read in NIB mode
[sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x77 from '0x278'
[sanei_pa4s2] sanei_pa4s2_readbyte: read finished
[sanei_pa4s2] sanei_pa4s2_readbyte: got value 0x77
[sanei_pa4s2] sanei_pa4s2_readbyte: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_readend: called for fd 0
[sanei_pa4s2] sanei_pa4s2_readend: we hope, the backend called
[sanei_pa4s2] sanei_pa4s2_readend: readbegin, so the port is ok...
[sanei_pa4s2] sanei_pa4s2_readend: this means, I did not check it - it's
[sanei_pa4s2] sanei_pa4s2_readend: not my fault, if your PC burns down.
[sanei_pa4s2] sanei_pa4s2_readend: NIB mode readend
[sanei_pa4s2] pa4s2_readend_nib: end of reading sequence for fd 0
[sanei_pa4s2] sanei_pa4s2_readend: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_open: could not find scanner
[sanei_pa4s2] sanei_pa4s2_open: reported ASIC id 0x77
[sanei_pa4s2] sanei_pa4s2_enable: called for fd 0 with value 0
[sanei_pa4s2] sanei_pa4s2_enable: disable port '0x278'
[sanei_pa4s2] pa4s2_disable: state restored
[sanei_pa4s2] sanei_pa4s2_enable: returning SANE_STATUS_GOOD
[sanei_pa4s2] sanei_pa4s2_open: closing port
[sane-devel] Mustek 1200 CP not working with sane 1.0.17 on FreeBSD
Hi, Dura-Zell wrote: [sanei_pa4s2] pa4s2_open: device `0x378` opened... this looks good... [sanei_pa4s2] pa4s2_readbyte_nib: reading value 0x77 from '0x378' and this looks very bad. should be A5 or A8 or similar. is your parallel port configured in EPP mode (maybe you can configure that in the BIOS? regards -- jochen
