[sane-devel] (no subject)
Cc:d sane-devel, again. markanderson ma.aaander...@xtra.co.nz writes: yes that worked thanks you the man now what do i do iv tryed to use gimp and aquire no luck What did you try? What happened? What did you expect? We're not clairvoyant. On Tue, 2006-09-19 at 08:57 +0900, Olaf Meeuwissen wrote: markanderson ma.aaander...@xtra.co.nz writes: how do i fix this email me at msax...@hotmail.com thanks mark Perfer to keep this on list. root@msa-desktop:/home/msa# make [snip] making all in tools make[1]: Entering directory `/home/msa/tools' gcc -c -g -O2 -W -Wall -DHAVE_CONFIG_H -I. -I/home/msa/Desktop/sane-backends-1.0.1 8/tools -I../include -I/home/msa/Desktop/sane-backends-1.0.18/include -D_REENTRANT -I/usr/include/gphoto2 -DPATH_SANE_CONFIG_DIR=/usr/local/etc/sane.d -DPATH_S ANE_DATA_DIR=/usr/local/share -DPATH_SANE_LOCK_DIR= -DV_MAJOR=1 -DV_ MINOR=0 ../backend/umax_pp_low.c -o ../backend/umax_pp_low.o \ -DBACKEND_NAME=umax_pp_low gcc: ../backend/umax_pp_low.c: No such file or directory gcc: no input files make[1]: *** [../backend/umax_pp_low.o] Error 1 make[1]: Leaving directory `/home/msa/tools' make: *** [all-recursive] Error 1 root@msa-desktop:/home/msa# Looks like you have the source tarball unpacked in /home/msa/Desktop/sane-backends-1.0.18 (as per include flag) and build in /home/msa. Are your sources there as well? Maybe you are doing a VPATH build (./configure --srcdir=Desktop/sane-backends-1.0.18)? I'm not sure this is supported. $ cd /home/mas/Desktop/sane-backends-1.0.18 $ ./configure $ make should do the trick. Hope this helps, -- Olaf Meeuwissen EPSON AVASYS Corporation, SE1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] Epson 2450 found by sane-find-scanner but not by scanimage
Tom Mitchell trmitch...@hotmail.co.uk writes: Hi, I am using an Asrock dual sata motherboard with AMD939 64 processor and sataII drive. I have installed PClinuxos minime0.93a a Mandriva based system on to a clean partion. I have also installed an Epson r220 usb printer which works really well. The Distro uses xsane 0.991_2tex sane-backends 1.0.18-1tex libusb 1.0.18-1tex kernel is 2.6.16.27.tex1.lve for i686 kde version 3.5.3 I am unable to get the scanner to work. It has worked before with Xandros3.0.2 and does with the simplymepis6 livecd. So I know that the cables etc are ok. When booted with the scanner on sane-find-scanner results in found USB scanner (vendor=0x04b8 [EPSON], product=0x0112 [EPSON Scanner]) at libusb:004:004 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. 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). this is both as root and as normal user. I have tried specifying the usb vendor and device in the epson.conf and epkowa.conf files in /etc/sane.d That is not necessary for either backend. I have also modified /etc/udev/rules.d/70-libsane.rules ACTION!=add, GOTO=libsane_rules_end SUBSYSTEM!=usb_device, GOTO=libsane_rules_end as suggested for Iscan at http://www.avasys.jp/english/linux_e/faq_scan.html ACTION!=add, GOTO=libsane_rules_end SUBSYSTEM!=usb, GOTO=libsane_rules_end but this doesnt work. Do NOT change the *libsane.rules file. Your distribution should have done the right thing. This change is only needed for *iscan.rules and then only on those distributions that do not use usb_device for the udev SUBSYSTEM name. So far, we know about Mandriva 2006.0. BTW, this will be fixed in the next iscan release. #lsusb states Bus 004 Device 004: ID 04b8:0112 Seiko Epson Corp. Perfection 2450 Bus 004 Device 001: ID : Bus 003 Device 001: ID : Bus 002 Device 001: ID : Bus 001 Device 003: ID 03f0:050c Hewlett-Packard 5219 Wireless Keyboard Bus 001 Device 001: ID : If I switch the scanner off and on I then get # scanimage -L device `epkowa:libusb:004:005' is a Epson Perfection 2450 flatbed scanner # scanimage image.pnm scanimage: no SANE devices found Do you have the epson backend disabled in /etc/sane.d/dll.conf? I'd expect to see `epson:libusb:004:005' listed in the scanimage -L output as well. Can you provide debugging output? The following command will put the debugging output in epkowa.log. SANE_DEBUG_EPKOWA=127 scanimage image.pnm 2 epkowa.log Whatever I try I cant seem to get to see the device. I would be grateful for any help to resolve this. Similar problems exist with Xandros4.0 Hope this helps, -- Olaf Meeuwissen EPSON AVASYS Corporation, SE1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] epson backend for the Stylus CX4800
Johannes Meixner jsm...@suse.de writes: Hello, On Sep 21 16:06 Olaf Meeuwissen wrote (shortened): Johannes Meixner jsm...@suse.de writes: a user reported to us that the Epson Stylus CX4800 (0x4b8/0x419) Unless there is yet another USB product ID I've never heard of, I think that should be 0x4b8/0x819. At least, that's what's in epkowa.desc ;-) You are right. There was a typo of the user. His Epson Stylus CX4800 has 0x4b8/0x819. Thanks a lot for pointing out the error! sane-find-scanner shows it as vendor=0x04b8 [EPSON], product=0x0819 [USB2.0 MFP(Hi-Speed)] note the user-friendly USB model string ;-) Point well taken and I also wish it would be more informative but I'm afraid there not much that can be done about it. Even the firmware's scanner part only says CX4800 which is not very helpful if you bought it someplace where it is marketed as a Stylus CX4700, Stylus DX4800 or even PX-A650 ... For details (like lsusb -v for his scanner) see https://bugzilla.novell.com/show_bug.cgi?id=206428#c3 Hey, at least the vendor specific interface mentions: iInterface 5 EPSON Scanner ;-P Hope this helps, -- Olaf Meeuwissen EPSON AVASYS Corporation, SE1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] epson dx3800
V?ctor e Inma vin...@telefonica.net writes: hello, i do not speak english well. I have a problem with epson stylus dx3800. I cannot scan because I don't know install it. In the xsane program is installing LogitechQuickCamExpressII.drc. I am searching the usb epson but I don't install. I get install the ubuntu-linux OS 6.06.01. The scanner part of your all-in-one is supported by the epson backend of sane-backends-1.0.17. This is the version that is part of ubuntu 6.06.1. Your device is also supported by iscan. You can download iscan from: http://www.avasys.jp/english/linux_e/index.html thank you. I'm sorry for me level english Hope this helps, -- Olaf Meeuwissen EPSON AVASYS Corporation, SE1 FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90 Penguin's lib! -- I hack, therefore I am -- LPIC-2
[sane-devel] new to the list
On Thu, 2006-09-21 at 16:37 -0400, James Newlin wrote: Hello all, I'm looking into creating a backend/driver for a EDT BizCardReader 900C USB 2.0 card scanner. It is using a SQ113C USB chip. The vendor ID is 0xA53 and device ID is 0x5001. Any pointers or help would be greatly appreciated. I do not know how much time I can devote to the creation of the new driver, but I am willing to try. How would I know if it needs to be a low-level driver or not? Thanks, James See this page, http://www.meier-geinitz.de/sane/mustek_usb2-backend/ this backend uses the same chip accoording to this page, the page is a bit old, the backend is already included in sane 1.0.18. -- m.vr.gr. Gerard Klaver
[sane-devel] new to the list
I seem to be missing the mustek_usb2.conf file. Downloaded sane-backend-1.0.18 and installed. No mustek_usb2.conf, downloaded the latest mustek_usb2 file from the web site below and installed. No mustek_usb2.conf file. If I understand correctly from sane-usb(5) man page, I might be able to add usb 0x0a53 0x5001 in the .conf file and the backend might work? Thanks, James - Original Message - From: Gerard Klaver ger...@gkall.hobby.nl To: James Newlin jnew...@medmate.com Cc: sane-devel@lists.alioth.debian.org Sent: Friday, September 22, 2006 11:38 AM Subject: Re: [sane-devel] new to the list On Thu, 2006-09-21 at 16:37 -0400, James Newlin wrote: Hello all, I'm looking into creating a backend/driver for a EDT BizCardReader 900C USB 2.0 card scanner. It is using a SQ113C USB chip. The vendor ID is 0xA53 and device ID is 0x5001. Any pointers or help would be greatly appreciated. I do not know how much time I can devote to the creation of the new driver, but I am willing to try. How would I know if it needs to be a low-level driver or not? Thanks, James See this page, http://www.meier-geinitz.de/sane/mustek_usb2-backend/ this backend uses the same chip accoording to this page, the page is a bit old, the backend is already included in sane 1.0.18. -- m.vr.gr. Gerard Klaver
[sane-devel] new to the list
On Fri, 2006-09-22 at 13:46 -0400, James Newlin wrote: I seem to be missing the mustek_usb2.conf file. Downloaded sane-backend-1.0.18 and installed. No mustek_usb2.conf, downloaded the latest mustek_usb2 file from the web site below and installed. No mustek_usb2.conf file. If I understand correctly from sane-usb(5) man page, I might be able to add usb 0x0a53 0x5001 in the .conf file and the backend might work? Thanks, James - Original Message - From: Gerard Klaver ger...@gkall.hobby.nl To: James Newlin jnew...@medmate.com Cc: sane-devel@lists.alioth.debian.org Sent: Friday, September 22, 2006 11:38 AM Subject: Re: [sane-devel] new to the list On Thu, 2006-09-21 at 16:37 -0400, James Newlin wrote: Hello all, I'm looking into creating a backend/driver for a EDT BizCardReader 900C USB 2.0 card scanner. It is using a SQ113C USB chip. The vendor ID is 0xA53 and device ID is 0x5001. Any pointers or help would be greatly appreciated. I do not know how much time I can devote to the creation of the new driver, but I am willing to try. How would I know if it needs to be a low-level driver or not? Thanks, James See this page, http://www.meier-geinitz.de/sane/mustek_usb2-backend/ this backend uses the same chip accoording to this page, the page is a bit old, the backend is already included in sane 1.0.18. -- m.vr.gr. Gerard Klaver man sane_mustek_usb2 no information about mustek_usb2.conf.in file. It seems you have to patch the mustek_usb2 backend file to add your vendor and product id, but be carefull with testing because i think your scanner has a different setup (cardreader), usb sniff files should give you an idea about some of the parameters. Contact also the maintainer of the backend (with info on sane-find-scanner -v -v) -- m.vr.gr. Gerard Klaver
[sane-devel] Out of memory in sanei_scsi_cmd [was: Annoying Out of MEmory Error...]
Hi SCSI experts, a user reported a problem with an Acer 620ST plugged into a Artop Electronic Corp AEC6712D SCSI controller (atp870u driver). The system causing problems is running linux-2.6.17-gentoo-r8, gcc 4.1.1 and glibc-2.4, sane-backends-1.0.18. On this system the following error occurs: ... [snapscan] open_scanner [sanei_debug] Setting debug level of sanei_scsi to 255. [sanei_scsi] sanei_scsi_open: SG driver version: 30533 [sanei_scsi] sanei_scsi_open_extended: using 131072 bytes as SCSI buffer [sanei_scsi] trying to enable low level command queueing [sanei_scsi] sanei_scsi_open: Host adapter queue depth: 1 [sanei_scsi] sanei_scsi_open: SG driver can change buffer size at run time [sanei_scsi] sanei_scsi_open: using new SG header structure [snapscan] sane_snapscan_open: waiting for scanner to warm up. [snapscan] wait_scanner_ready ... [snapscan] send [snapscan] snapscan_cmd [sanei_scsi] scsi_req_enter: entered 0xb7c5e008 [sanei_scsi] sanei_scsi.issue: 0xb7c5e008 dev_max(currently)=32 max_active_device=1 (origin 1) def_reserved_size=32768 device=sg0 scsi1 chan=0 id=2 lun=0 em=0 sg_tablesize=128 excl=1 FD(1): timeout=12ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 rb act: id=9 blen=1024 t_o/elap=12/8ms sgat=1 op=0x2a [sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c5e008 [sanei_scsi] sanei_scsi.issue: 0xb7c5e008 dev_max(currently)=32 max_active_device=1 (origin 1) def_reserved_size=32768 device=sg0 scsi1 chan=0 id=2 lun=0 em=0 sg_tablesize=128 excl=1 FD(1): timeout=12ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 rb rcv: id=9 blen=1024 dur=108ms sgat=1 op=0x2a [sanei_scsi] sanei_scsi_req_wait: read 64 bytes [snapscan] measure_transfer_rate: have ring buffer [snapscan] scsi_read [snapscan] snapscan_cmd [sanei_scsi] scsi_req_enter: entered 0xb7c5e008 [sanei_scsi] sanei_scsi.issue: 0xb7c5e008 dev_max(currently)=32 max_active_device=1 (origin 1) def_reserved_size=32768 device=sg0 scsi1 chan=0 id=2 lun=0 em=0 sg_tablesize=128 excl=1 FD(1): timeout=12ms bufflen=131072 (res)sgat=4 low_dma=0 cmd_q=1 f_packid=0 k_orphan=0 closed=0 No requests active [sanei_scsi] sanei_scsi.issue: bad write (errno=12) Cannot allocate memory -1 [sanei_scsi] sanei_scsi.issue: SG_BIG_BUF inconsistency? Check file PROBLEMS. [sanei_scsi] scsi_req_enter: queue_used: 0, queue_max: 1 [sanei_scsi] sanei_scsi_req_wait: waiting for 0xb7c5e008 [sanei_scsi] sanei_scsi.issue: 0xb7c5e008 [snapscan] scsi_read: snapscan_cmd command failed: Out of memory [snapscan] measure_transfer_rate: scsi_read command failed: Out of memory [snapscan] sane_snapscan_start: measure_transfer_rate command failed: Out of memory scanimage: sane_start: Out of memory ... As far as I can tell I'm issuing a sanei_scsi_cmd with a send buffer of ten bytes and a receive buffer of 130176 bytes. Both should fit into the SCSI buffer of 131072 bytes easily. To make matters even stranger, the same SCSI card and scanner works fine on Ubuntu 6.06 LTS, kernel: 2.6.15-23-386 gcc: GCC 4.0.3 (Ubuntu 4.0.3-1ubuntu5) glibc:2.3.6 sane-backends: 1.0.17 Does anybody of the experts have any idea what's going on? Regards, Oliver