Just to compare, follow the debug from the scanimage command: marcio@mama:~> SANE_DEBUG_SNAPSCAN=255 scanimage -L [sanei_debug] Setting debug level of snapscan to 255. [snapscan] sane_snapscan_init [snapscan] sane_snapscan_init: Snapscan backend version 1.4.50 [snapscan] add_usb_device(libusb:005:003) [snapscan] add_usb_device: Detected (kind of) an USB device [snapscan] snapscani_usb_open(libusb:005:003) [snapscan] add_usb_device: Checking if 0x04b8 is a supported USB vendor ID [snapscan] snapscani_check_device() [snapscan] mini_inquiry [snapscan] snapscan_cmd [snapscan] snapscani_usb_cmd(0,0x7fff04fef750,6,0x7fff04fef720,0x7fff04fef748 (3 6)) [snapscan] atomic_usb_cmd(0,0x7fff04fef750,6,0x7fff04fef720,0x7fff04fef748 (36)) [snapscan] usb_cmd(0,0x7fff04fef750,6,0x7fff04fef720,0x7fff04fef748 (36)) [snapscan] usb_cmd: cmdlen=6, datalen=0 [snapscan] usb_write: writing: 0x12 0x00 0x00 0x00 0x24 0x00 [snapscan] Written 6 bytes [snapscan] usb_read: reading: 0xf9 0x00 0x00 0x00 0x00 0x00 0x00 0x00 [snapscan] Read 8 bytes [snapscan] usb_read: reading: 0x06 0x00 0x02 0x02 0x49 0x00 0x00 0x00 0x45 0x50 ... [snapscan] Read 36 bytes [snapscan] usb_read: reading: 0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00 [snapscan] Read 8 bytes [snapscan] snapscani_check_device: Is vendor "EPSON" model "EPSON Scanner" a sup ported scanner? [snapscan] snapscani_get_model_id(EPSON Scanner, 0, 2) [snapscan] snapscani_get_model_id: looking up scanner for ID 0x04b8,0x0122. [snapscan] snapscani_get_model_id: scanner identified [snapscan] snapscani_check_device: Autodetected driver: Perfection 3490 [snapscan] snapscani_usb_close(0) [snapscan] 1st read 3 write 1 [snapscan] snapscani_usb_cmd(0,0x7fff04fef7d0,6,0x0,0x0 (0)) [snapscan] atomic_usb_cmd(0,0x7fff04fef7d0,6,0x0,0x0 (0)) [snapscan] usb_cmd(0,0x7fff04fef7d0,6,0x0,0x0 (0)) [snapscan] usb_cmd: cmdlen=6, datalen=0 [snapscan] usb_write: writing: 0x00 0x00 0x00 0x00 0x00 0x00 [snapscan] Written 6 bytes [snapscan] usb_read: reading: 0xfb 0x00 0x00 0x00 0x00 0x00 0x00 0x00 [snapscan] Read 8 bytes [snapscan] 2nd read 4 write 2 [snapscan] snapscani_init_device_structure() [snapscan] sane_snapscan_get_devices (0x7fff04ff0930, 0) device `snapscan:libusb:005:003' is a EPSON EPSON Scanner flatbed scanner [snapscan] sane_snapscan_exit
-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061119/a144ce8e/attachment.htm From azummo-li...@towertech.it Mon Nov 20 00:33:48 2006 From: azummo-li...@towertech.it (Alessandro Zummo) Date: Mon Nov 20 00:34:13 2006 Subject: [sane-devel] [PATCH] sanei_tcp Message-ID: <20061120003348.26d559bb@inspiron> This patch adds tcp networking capabilities to sane. It's required for the epson2 driver to work with the Epson CX11 printer/scanner. -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it -------------- next part -------------- A non-text attachment was scrubbed... Name: sanei-tcp.patch Type: text/x-patch Size: 6343 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061120/70913e57/sanei-tcp.bin From azummo-li...@towertech.it Mon Nov 20 00:40:16 2006 From: azummo-li...@towertech.it (Alessandro Zummo) Date: Mon Nov 20 00:40:42 2006 Subject: [sane-devel] [PATCH] epson2 driver Message-ID: <20061120004016.399821da@inspiron> This driver has basic support for the Epson FilmScan 200 (scsi) Epson CX11NF / LP-A500 (network) "basic" means that scanimage -L works correctly and that I still have to write the actual scanning routines. The CX11NF works correctly via usb. setting the env SANE_DEBUG_EPSON2 to 12 or 20 will show you a lot of info about your scanner. Support for other epson scanners should work the same as the current epson driver. The CX11 is the only network-capable I've been able to test the driver on. I know that some other scanners can be fitted with a network card, but those are untested. So.. I someone of you has one, it's the time to test it or send me one :) I'd appreciate having feedback. -- Best regards, Alessandro Zummo, Tower Technologies - Turin, Italy http://www.towertech.it -------------- next part -------------- A non-text attachment was scrubbed... Name: epson2.patch.bz2 Type: application/x-bzip Size: 31243 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20061120/7251bc6c/epson2.patch-0001.bin From olaf.meeuwis...@avasys.jp Mon Nov 20 02:11:43 2006 From: olaf.meeuwis...@avasys.jp (Olaf Meeuwissen) Date: Mon Nov 20 02:16:45 2006 Subject: [sane-devel] Out of Memory error when scanning at high DPI In-Reply-To: <200611171129.06857.mark.richa...@gmail.com> (Mark Richards's message of "Fri, 17 Nov 2006 11:29:02 -0500") References: <b5120b0e0611151634y324169bdxdba12f9d2e33...@mail.gmail.com> <200611162118.34969.mark.richa...@gmail.com> <87wt5upwhk....@geek.avasys.jp> <200611171129.06857.mark.richa...@gmail.com> Message-ID: <873b8e53cg....@geek.avasys.jp> Mark Richards <mark.richa...@gmail.com> writes: > Thanks again for the prompt response. I have one question: when you > say "your scanner breaks", do you mean that my physical scanner > would be damaged? Or do you mean that the sane backend would be > broken and I'd have to revert the change? I'm willing to help get > this driver working but I'm not in a position to risk damage to the > scanner, unfortunately. > [snip] Although the risk is probably quite small, I mean physically break. # I can't afford telling you do this, try that and then have you # complain when your scanner gets damaged, now can I? 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
