[sane-devel] saned.c - path to saned.conf
Hi, The past weekend I installed/added sane to the linux thinstation available packages. Everything went very well, except for saned (starting from xinetd) not allowing clients to access. Some checking (starting saned manually with -d128) showed that saned could not find saned.conf, which did exist in /etc/sane.d/ If I started saned -d128 in the /etc/sane.d/ folder, it worked 100%. Checking the code in saned.c I found : #define SANED_CONFIG_FILE saned.conf and changed it to #define SANED_CONFIG_FILE /etc/sane.d/saned.conf this change made it work properly, as it can now find the conf file. Any better fix for this ? Maybe I am missing a configure setting ? I used ./configure --prefix=/ --bindir=/bin --sbindir=/bin --libdir=/lib to configure for the compile. Regards Lucas
[sane-devel] Umax astra 4500
I am getting an error - apparently the scanner will not warm up. USB cable is connected - mains is on and light shows when you lift the cover -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070625/aaa2a4ad/attachment.htm
[sane-devel] Epson 640U and sane1.0.18+cvs20061127-1
Hello! I trying to use an EPSON 640U with sane 1.0.18+cvs20061127-1. The platform is a WL500gp running Oleg?s firmware (Linux 2.4.20/mips). I have sane-backend installed and ?scanner.o? module is recognizing the scanner: ... scanner.c: USB scanner device (0x04b8/0x010c) now attached to scanner0 scanner.c: 0.4.16:USB Scanner Driver sane-find-scanner results: ... found USB scanner (vendor=0x04b8, product=0x010c) at /dev/usb/scanner0 ... Access rights to /dev/usb/scanner0 are fine ? a ?SANE_DEBUG_EPSON='255' scanimage ?L? results: [sanei_debug] Setting debug level of epson to 255. [epson] sane_init: sane-backends 1.0.18-cvs [epson] sane_init, # epson.conf [epson] sane_init, # [epson] sane_init, # here are some examples for how to configure the EPSON backend [epson] sane_init, # [epson] sane_init, # SCSI scanner: [epson] sane_init, #scsi EPSON [epson] sane_init, # for the GT-6500: [epson] sane_init, #scsi EPSON SC [epson] sane_init, # [epson] sane_init, # Parallel port scanner: [epson] sane_init, #pio 0x278 [epson] sane_init, #pio 0x378 [epson] sane_init, #pio 0x3BC [epson] sane_init, # [epson] sane_init, # USB scanner: [epson] sane_init, # There are two different methods of configuring a USB scanner: libusb and the kernel module [epson] sane_init, # For any system with libusb support (which is pretty much any recent Linux distribution) the [epson] sane_init, # following line is sufficient. This however assumes that the connected scanner (or to be more [epson] sane_init, # accurate, it's device ID) is known to the backend. [epson] sane_init, #usb [epson] sane_init, # For libusb support for unknown scanners use the following command [epson] sane_init, # usb product ID device ID [epson] sane_init, # e.g.: [epson] sane_init, #usb 0x4b8 0x110 [epson] sane_init, #usb 0x010c 0x04b8 [epson] sane_init, # And for the scanner module, use the following configuration: [epson] sane_init, #usb /dev/usb/scanner0 [epson] sane_init, usb /dev/usb/scanner0 [epson] attach_one_usb(/dev/usb/scanner0) [epson] SANE Epson Backend v0.2.47 - 2006-08-21 [epson] attach(/dev/usb/scanner0, 3) [epson] attach: opening /dev/usb/scanner0 [epson] Found valid EPSON scanner: 0x4b8/0x10c (vendorID/productID) [epson] reset() [epson] send buf, size = 2 [epson] buf[0] 1b . [epson] buf[1] 40 @ [epson] w_cmd_count = 1 [epson] r_cmd_count = 0 [epson] w_cmd_count = 1 [epson] r_cmd_count = 1 [epson] receive buf, expected = 1, got = 1 [epson] buf[0] 06 . [epson] get_identity_information() [epson] send buf, size = 2 [epson] buf[0] 1b . [epson] buf[1] 49 I [epson] w_cmd_count = 2 [epson] r_cmd_count = 1 [epson] w_cmd_count = 2 [epson] r_cmd_count = 2 [epson] receive buf, expected = 4, got = 4 [epson] buf[0] 02 . [epson] buf[1] 00 . [epson] buf[2] 13 . [epson] buf[3] 00 . [epson] code 02 [epson] status 00 [epson] count 19 [epson] w_cmd_count = 2 [epson] r_cmd_count = 3 [epson] receive buf, expected = 19, got = 19 [epson] buf[0] 44 D [epson] buf[1] 31 1 [epson] buf[2] 52 R [epson] buf[3] 4b K [epson] buf[4] 00 . [epson] buf[5] 52 R [epson] buf[6] 96 . [epson] buf[7] 00 . [epson] buf[8] 52 R [epson] buf[9] 2c , [epson] buf[10] 01 . [epson] buf[11] 52 R [epson] buf[12] 58 X [epson] buf[13] 02 . [epson] buf[14] 41 A [epson] buf[15] ec . [epson] buf[16] 13 . [epson] buf[17] 7c | [epson] buf[18] 1b . [epson] typeD 0x44 [epson] level 1 0x31 [epson] type 0x00 [epson] level T 0x54 [epson] forced [epson] no option equipment installed [epson] out of memory (line 5960) [epson] sane_get_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).
[sane-devel] Can't build SANE on Ubuntu Feisty 7.04
i can confirm this issue- it seems that lib/liblib.a is empty- the command used to create it: ar cru liblib.a ranlib liblib.a should probably be: ar cru liblib.a .libs/* ranlib liblib.a and sanei/libsanei.a is also empty ar cru libsanei.a ranlib libsanei.a should be: ar cru libsanei.a .libs/* ranlib libsanei.a this is on a fedora core 6 box that has successfully built sane many times, until a recent cvs up make clean ./configure if you run those repaired commands manually from the right dir, your build should succeed. any libtool experts out there? allan On 6/25/07, Simon Glass sglass at bluewatersys.com wrote: Hi, I am keen to test out my new Fujitsu FI-5750C but it doesn't seem to work out of the box. While trying to build SANE from CVS I initially got an error about md5 which I got around by adding a library explicitly to the Makefile. making all in frontend make[1]: Entering directory `/pub/software/drivers/sane/sane-backends/frontend' make[1]: Warning: File `Makefile' has modification time 0.83 s in the future gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a ../backend/.libs/libsane.so -ldl /usr/lib/libusb.so -lpthread /usr/lib/libtiff.so /usr/lib/libjpeg.so -lz -lm -lc /usr/lib/libieee1284.so -Wl,--rpath -Wl,/usr/local/lib scanimage.o: In function `auth_callback': /pub/software/drivers/sane/sane-backends/frontend/scanimage.c:291: undefined reference to `md5_buffer' collect2: ld returned 1 exit status make[1]: *** [scanimage] Error 1 make[1]: Leaving directory `/pub/software/drivers/sane/sane-backends/frontend' But now I get: ... making all in frontend make[1]: Entering directory `/pub/software/drivers/sane/sane-backends/frontend' make[1]: Warning: File `Makefile' has modification time 0.4 s in the future gcc-4.0 -o .libs/saned saned.o ../sanei/libsanei.a ../lib/liblib.a ../backend/.libs/libsane.so -ldl /usr/lib/libusb.so -lpthread /usr/lib/libtiff.so /usr/lib/libjpeg.so -lz -lm -lc /usr/lib/libieee1284.so -Wl,--rpath -Wl,/usr/local/lib saned.o: In function `decode_handle': /pub/software/drivers/sane/sane-backends/frontend/saned.c:461: undefined reference to `sanei_w_word' saned.o: In function `init': /pub/software/drivers/sane/sane-backends/frontend/saned.c:1254: undefined reference to `sanei_w_set_dir' /pub/software/drivers/sane/sane-backends/frontend/saned.c:1261: undefined reference to `sanei_w_word' ... It seems that the tools are not producing object files properly or something. Before I dive into something I don't understand does anyone have a simple solution? I did see this from ./configure checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory GNU/Linux ld.so Regards, Simon -- 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] saned.c - path to saned.conf
Lucas van Staden lvanstaden at lizearle.com wrote: Any better fix for this ? Maybe I am missing a configure setting ? I used ./configure --prefix=/ --bindir=/bin --sbindir=/bin --libdir=/lib --sysconfdir JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] saned.c - path to saned.conf
Julien BLACHE wrote: Lucas van Staden lvanstaden at lizearle.com wrote: Any better fix for this ? Maybe I am missing a configure setting ? I used ./configure --prefix=/ --bindir=/bin --sbindir=/bin --libdir=/lib --sysconfdir JB. Hi, Yeah, I did see that one, but did not set it...marked as 'read only', so figure I cannot change it.. configure --help gives: --sysconfdir=DIR read-only single-machine data [PREFIX/etc] ... so...using my prefix it set to //etc I noticed the double slash, and also tried the configure with --prefix= (blank) which then set sysconfdir to /etc. A make install installed all files to correct folders, including /etc/sane.d/ prefix set to either blank or / had the same effect, saned could not find the saned.conf file. Sorry about the two different posting emails, I forgot to change from my default (work) profile on my first post. Regards Lucas
[sane-devel] Can't build SANE on Ubuntu Feisty 7.04
On 6/25/07, m. allan noah kitno455 at gmail.com wrote: i can confirm this issue- it seems that lib/liblib.a is empty- the command used to create it: ar cru liblib.a ranlib liblib.a should probably be: ar cru liblib.a .libs/* ranlib liblib.a and sanei/libsanei.a is also empty ar cru libsanei.a ranlib libsanei.a should be: ar cru libsanei.a .libs/* ranlib libsanei.a this is on a fedora core 6 box that has successfully built sane many times, until a recent cvs up make clean ./configure if you run those repaired commands manually from the right dir, your build should succeed. any libtool experts out there? allan lib/Makefile runs this line: ../libtool --mode=link gcc getopt.lo getopt1.lo md5.lo -o liblib.a which produces the incorrect output. using the system libtool instead: libtool --mode=link gcc getopt.lo getopt1.lo md5.lo -o liblib.a gives: ar cru liblib.a .libs/getopt.o .libs/getopt1.o .libs/md5.o ranlib liblib.a indicating that it correctly read the .lo files. the weird thing, is that this seems to happen even with older copies of configure, and ltmain.sh has not been changed in 2 years? help? allan On 6/25/07, Simon Glass sglass at bluewatersys.com wrote: Hi, I am keen to test out my new Fujitsu FI-5750C but it doesn't seem to work out of the box. While trying to build SANE from CVS I initially got an error about md5 which I got around by adding a library explicitly to the Makefile. making all in frontend make[1]: Entering directory `/pub/software/drivers/sane/sane-backends/frontend' make[1]: Warning: File `Makefile' has modification time 0.83 s in the future gcc -o .libs/scanimage scanimage.o stiff.o ../lib/liblib.a ../backend/.libs/libsane.so -ldl /usr/lib/libusb.so -lpthread /usr/lib/libtiff.so /usr/lib/libjpeg.so -lz -lm -lc /usr/lib/libieee1284.so -Wl,--rpath -Wl,/usr/local/lib scanimage.o: In function `auth_callback': /pub/software/drivers/sane/sane-backends/frontend/scanimage.c:291: undefined reference to `md5_buffer' collect2: ld returned 1 exit status make[1]: *** [scanimage] Error 1 make[1]: Leaving directory `/pub/software/drivers/sane/sane-backends/frontend' But now I get: ... making all in frontend make[1]: Entering directory `/pub/software/drivers/sane/sane-backends/frontend' make[1]: Warning: File `Makefile' has modification time 0.4 s in the future gcc-4.0 -o .libs/saned saned.o ../sanei/libsanei.a ../lib/liblib.a ../backend/.libs/libsane.so -ldl /usr/lib/libusb.so -lpthread /usr/lib/libtiff.so /usr/lib/libjpeg.so -lz -lm -lc /usr/lib/libieee1284.so -Wl,--rpath -Wl,/usr/local/lib saned.o: In function `decode_handle': /pub/software/drivers/sane/sane-backends/frontend/saned.c:461: undefined reference to `sanei_w_word' saned.o: In function `init': /pub/software/drivers/sane/sane-backends/frontend/saned.c:1254: undefined reference to `sanei_w_set_dir' /pub/software/drivers/sane/sane-backends/frontend/saned.c:1261: undefined reference to `sanei_w_word' ... It seems that the tools are not producing object files properly or something. Before I dive into something I don't understand does anyone have a simple solution? I did see this from ./configure checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... cat: /etc/ld.so.conf.d/*.conf: No such file or directory GNU/Linux ld.so Regards, Simon -- 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 -- The truth is an offense, but not a sin
[sane-devel] Scanner 'reset scan head' utilities (plustek, Canon Lide20)
I'm starting to look more closely at scanner troubleshooting issues for deployment. Is there a utility or command parameter that will instruct a scanner to park the head back in the home position and generally reset itself to a safe/ready state? My everyday flatbed scanner ((vendor=0x04a9 [Canon], product=0x220d [CanoScan], chip=LM9832/3) at libusb:002:002) got out of sorts today. The scan head wasn't returned to the home position (it is now), but XSane scans now just return solid black data. The Lide20 has been pretty reliable. The only thing out of the ordinary today was that I ran the scanimage program for scanner information. I usually use xsane with gimp, and unplug the scanner shortly thereafter. Is this a hardware state problem, or a crashed kernel module that must be purged (and how to do so?) Nothing sane-related shows up with lsmod. Thanks.
[sane-devel] Scanner 'reset scan head' utilities (plustek, Canon Lide20)
Jeff Kowalczyk wrote: My everyday flatbed scanner ((vendor=0x04a9 [Canon], product=0x220d [CanoScan], chip=LM9832/3) at libusb:002:002) got out of sorts today. The scan head wasn't returned to the home position (it is now), but XSane scans now just return solid black data. I see that it's a known problem, since I have (recently) enabled CONFIG_USB_SUSPEND to try powertop, and this is using the plustek backend.
[sane-devel] fujitsu 5120c --souce error invalid argument
Hi, first, thanks to the sane team and the fujitsu backenders. 1.0.18 builds on ubuntu 6.06.1 and scanimage works well w/ most options that i tested so far - color, batch... and i'm still testing different options to scanimage. however, the ADF Front, ADF Back, ADF Duplex option of course defaults to ADF Front and any option passed to scanimage --source foo returns an invalid arg. I think this is the reason why xscanner is broken btw, because it tries to pass --source and returns an error. also, i am using scsi, and have set scsi eeprom to the lowest async settings available. i'm testing for synchronous and higher speeds right now so here is my question. will you help me configure or change makefile to build just for fujitsu 5120c? or, even better, to help me debug the backend so the --source option works? fwiw, i work w/ embedded systems and use simple makefiles only. however, i am reading the auto* toolset documentation because i have an interest in porting some of my projects. i plan on working this fujitsu backend as a learning tool for the auto* toolset. also, this fujitsu 5120c was chosen for it's duplex and insurance card scanning ability - and specifically requested by a client for intallation into a medical clinic. i don't really need xscanner to work but it would be nice and i think once the --source option is working then xscanner will too. thanks again to any and all replies. -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20070625/c2c3d3fc/attachment.htm
