[sane-devel] artec 48u
Skipped content of type multipart/alternative-- next part -- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 1856 bytes Desc: not available Url : http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060925/edb3c957/attachment.jpe From c...@orcon.net.nz Tue Sep 26 19:35:09 2006 From: c...@orcon.net.nz (cr) Date: Tue Sep 26 07:49:31 2006 Subject: [sane-devel] artec 48u In-Reply-To: References: Message-ID: <200609270735.10186...@orcon.net.nz> On Mon, 25 Sep 2006 06:16, dave case wrote: > Hi,I bought a scanner from a yard sale for 4 bucks and no disc.Is there a > way to down load without one or do you know were to get one and the > cost.Thanks,Dave I've got a 48u running OK with Sane under Debian Sarge. From what I can recall, it only needs one very small 8k file from the disc. Called Artec48.usb. For info on using the Artec try here: http://www.fifi.org/cgi-bin/man2html/usr/share/man/man5/sane-artec_eplus48u.5.gz And I've just uploaded the file to my site at http://cr.qc1.net/misc/Artec48.usb Good luck! cr
[sane-devel] artec 48u
Hi,I bought a scanner from a yard sale for 4 bucks and no disc.Is there a way to down load without one or do you know were to get one and the cost.Thanks,Dave -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20060924/640e2162/attachment.html From trmitch...@hotmail.co.uk Mon Sep 25 07:42:49 2006 From: trmitch...@hotmail.co.uk (Tom Mitchell) Date: Mon Sep 25 17:06:27 2006 Subject: [sane-devel] Epson 2450 found by sane-find-scanner but not by scanimage In-Reply-To: <87hcyw4wbd@geek.avasys.jp> Message-ID: Hi Olaf, 1) I am not sure how the distro handles usb hotplug or scanner users. I will try and check on this. It has a reputation for things to just work and apart from the scanner they do. They have been helpful in trying to sort this out. As I mentioned I have had the same problem with Xandros4 whereas the scanner works with Xandros3. 2) the output of the file is below [sanei_debug] Setting debug level of sanei_usb to 127. [sanei_usb] sanei_usb_init: can't stat /dev/usb/: No such file or directory usb_set_debug: Setting debugging level to 255 (on) usb_os_find_busses: Found 004 usb_os_find_busses: Found 003 usb_os_find_busses: Found 002 usb_os_find_busses: Found 001 usb_os_find_busses: Skipping non bus directory devices usb_os_find_devices: Found 003 on 004 usb_os_find_devices: Found 001 on 004 error obtaining child information: Inappropriate ioctl for device usb_os_find_devices: Found 001 on 003 usb_os_find_devices: Found 001 on 002 usb_os_find_devices: Found 003 on 001 skipped 1 class/vendor specific interface descriptors skipped 1 class/vendor specific interface descriptors usb_os_find_devices: Found 001 on 001 error obtaining child information: Inappropriate ioctl for device [sanei_usb] sanei_usb_init: found libusb device (0x04b8/0x0112) interface 0 at libusb:004:003 [sanei_usb] sanei_usb_init: device 0x/0x looks like a root hub [sanei_usb] sanei_usb_init: device 0x/0x looks like a root hub [sanei_usb] sanei_usb_init: device 0x/0x looks like a root hub [sanei_usb] sanei_usb_init: device 0x03f0/0x050c, interface 0 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: device 0x03f0/0x050c, interface 1 doesn't look like a scanner (0/3) [sanei_usb] sanei_usb_init: device 0x03f0/0x050c: no suitable interfaces [sanei_usb] sanei_usb_init: device 0x/0x looks like a root hub [sanei_usb] sanei_usb_init: found 1 devices [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0101 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0103 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0104 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0106 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0107 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0109 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010a [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010b [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010c [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x010e [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0110 [sanei_usb] sanei_usb_find_devices: vendor=0x04b8, product=0x0112 [sanei_usb] sanei_usb_open: trying to open device `libusb:004:003' [sanei_usb] sanei_usb_open: found bulk-in endpoint (address 1) [sanei_usb] sanei_usb_open: found bulk-out endpoint (address 2) [sanei_usb] sanei_usb_open: opened usb device `libusb:004:003' (*dn=0) [sanei_usb] sanei_usb_get_vendor_product: device 0: vendorID: 0x04b8, productID: 0x0112 [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes [sanei_usb] : 1B 40 .@.. [sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 1 bytes [sanei_usb] : 06 [sanei_usb] sanei_usb_read_bulk: wanted 1 bytes, got 1 bytes [sanei_usb] sanei_usb_write_bulk: trying to write 2 bytes [sanei_usb] : 1B 49 .I.. [sanei_usb] sanei_usb_write_bulk: wanted 2 bytes, wrote 2 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 4 bytes [sanei_usb] : 02 02 6A 00 ..j. [sanei_usb] sanei_usb_read_bulk: wanted 4 bytes, got 4 bytes [sanei_usb] sanei_usb_read_bulk: trying to read 106 bytes [sanei_usb] : 42 38 52 32 00 52 3C 00 52 48 00 52 4B 00 52 50 B8R2.R<.RH.RK.RP [sanei_usb] 0010: 00 52 5A 00 52 64 00 52 78 00 52 85 00 52 90 00 .RZ.Rd.Rx.R..R.. [sanei_usb] 0020: 52 96 00 52 A0 00 52 AF 00 52 B4 00 52 C8 00 52 R..R..R..R..R..R [sanei_usb] 0030: D8 00 52 F0 00 52 0A 01 52 2C 01 52 40 01 52 5E ..R..R..R,.R@.R^ [sanei_usb] 0040: 01 52 68 01 52 90 01 52 E0 01 52 58 02 52 D0 02 .Rh.R..R..RX.R.. [sanei_usb] 0050: 52 20 03 52 84 03 52 B0 04 52
[sane-devel] scanning slowness
Hello, having moved from a old version of xsane (ca. 2001) to the latest one in Ubuntu, I am faced with serious speed problems: - in the old xsane, when I previewed a page, I was able to select the scanning area as soon as the carriage was moving backwards, and therefore before the scanner was at rest; now, I have to wait that the scanner (an old Epson Perfection 1240U) has the carriage in the initial position; this is a huge waste of time for me; can this be changed? - once a file is scanned, it is saved, but saving takes a huge amount of time, something that didn't happen with the old xsane, and with the same scanner and the same computer; can this be improved? Thanks, Denis
[sane-devel] scanner model report
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Per request in /etc/udev/libsane.rules ,
I'm sending the entry I added for my Brother all-in-one.
# Brother MFC 5440cn
SYSFS{idVendor}=="04f9", SYSFS{idProduct}=="016d", MODE="664",
OWNER="saned", GROUP="scanner"
non-free driver provided by Brother (for amd64 - had to debianize the
rpm) works fine for me.
Regards.
Amit Aronovitch
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFFcDGVV5PHbGSb3YRAngUAJ97NyungtT7LyV97mkNR51eZiZOswCfRUOT
C53h7tfTajvIuwI1gqwjB44=
=vEsv
-END PGP SIGNATURE-
[sane-devel] Saving scanned files in the current directory
Hello, this question has been asked previously, but I find it very clumsy to go in a menu to set the saving directory as the current directory. The current directory can be down a complex hierarchy, and saving one day in this directory and another in that directory makes scanning a real nightmare. I have long used an old version of xsane, which naturally saved in the current directory. I understand that the current way the directory is stored may be convenient, but I very much would like a command line option to set the saving directory, something like xsane -saveto . and I would save where I am, or somewhere else. Thanks, Denis
[sane-devel] User set up instr.?
Is there a step by step instruction for setting up sane? This equipment did work some time ago when using FC4 Linux but has not worked with FC5. sane-find-scanner shows: found USB scanner (vendor=0x03f0, product=0x0701) at libusb:001:002 and 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). Yes, yes, and yes, and I have read a lot of material but nothing that makes clear what I need to do next. The scanner is an HP5370c Scanjet for which I gather that I need the avision.conf file but I'm not sure I have that in the right place or that it is commented correctly. /etc/sane.d/avision.conf # This are the possible options. Normally any scanner # should work just fine without them - and they are only # needed for test and debugging. So if you experience problems # and you solve them with enabling options here, please notify # the SANE/Avision maintainer: Rene Rebe #option disable-gamma-table #option disable-calibration #option force-a4 #scsi AVISION #scsi FCPA #scsi MINOLTA #scsi MITSBISH MCA-S600C #scsi MITSBISH MCA-SS600 #scsi HP #scsi hp #scsi /dev/scanner #usb libusb:002:003 usb 0x03f0 0x0701 As I said this same set of equipment did work perhaps a year ago but I can't seem to get things right again with this up to date FC5 system as root. Any help will be much appreciated. Bob Goodwin
[sane-devel] Re: my elaberation
markanderson writes: > i go to http://www.linuxjournal.com/article/2395 and have dun all things > up to the part that tells me to type ( scanimage --list-devices )and > when i do (in root terminal) i get this > root@msa-desktop:/home/msa# scanimage --list-devices Hi Mark, Please send your requests for help to the sane-devel mailing list. There are many more people hanging out there that may be able to help. mailto:sane-devel@lists.alioth.debian.org As for the URL you mention, that is a story from 1998. While the basics haven't changed (much) a lot of other things have. Please visit: http://sane.alioth.debian.org/ for more recent information. > 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). > root@msa-desktop:/home/msa# > can you help Not without more information, for example the distribution and scanner model you are using and maybe even some debugging information. 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" writes: > Hi Olaf, > Sorry for the delay in replying I appreciate your help. > > 1)I have put all files back to their originals. > > 2)You asked > > "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." > > I didnt have the backend disabled. Both lines do not have an # in > front of them. Weird that you don't see epson:libusb:004:005 then. > 3) I have tried to run as user and got permission denied. # I'm not familiar with your distribution, so I don't know how its # *libsane.rules looks and how it handles hotplugging of scanners. Hmm, is user part of the appropriate group (scanner, by default)? > 4) As root the output of SANE_DEBUG_EPKOWA=127 scanimage > image.pnm > 2> epkowa.log > > is > > [snip]> [epkowa] EPKOWA SANE Backend 2.1.0 - 2006-05-22 > [epkowa] attach(, 3) > [epkowa] attach: opening > [epkowa] attach_one_usb(libusb:004:004) > [epkowa] EPKOWA SANE Backend 2.1.0 - 2006-05-22 > [epkowa] attach(libusb:004:004, 3) > [epkowa] attach: opening libusb:004:004 > [epkowa] Found valid EPSON scanner: 0x4b8/0x112 (vendorID/productID) > [epkowa] reset() > [epkowa] send buf, size = 2 > [epkowa] buf[0] 1b . > [epkowa] buf[1] 40 @ > [epkowa] receive buf, expected = 1, got = 0 Ouch! The device is not talking back to you. You should get a one byte reply here, either 0x06 (ACK) or 0x15 (NAK). > [snip] Tom, can you repeat the scanimage command to get the USB debugging info? Like so: SANE_DEBUG_SANEI_USB=127 scanimage > image.pnm 2> epkowa-usb.log Hope this helps, >>"Tom Mitchell" 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
[sane-devel] Problem Scanning with Epson RX520
"Paul Smedley" writes: > Hi Guys, > > I got a report from a user of the OS/2 version of Sane that the Epson > RX520 isn't working. Debug log is at http://smedley.ingo/debug.txt FWIW, the epson backend doesn't claim it's supported in any way. The epkowa backend does. # Is that URL valid? Looks like my DNS server doesn't know about # smedley.ingo ... > Scan ends with: > scanimage.exe: sane_start: Operation not supported > > Only real hints (to me) in the log are: > [epson] sane_start() > [epson] scanner is already open: fd = 0 > [epson] You may have to power off your TPU > [epson] Also you may have to restart the Sane frontend. > [epson] open_scanner() > [epson] scanner is already open: fd = 0 > [epson] You may have to power off your TPU > [epson] Also you may have to restart the Sane frontend. > > Any clues on how to get this working? Wow! This is the same behaviour I saw when I mentioned in http://lists.alioth.debian.org/pipermail/sane-devel/2006-September/017763.html that not all epkowa supported devices are supported by the epson backend, even if you don't need a binary-only non-free plugin. FTR, that happened with Debian GNU/Linux (testing/unstable) on i386 and amd64. With the epkowa backend things work fine on i386 (haven't tried amd64) and the code that is responsible for the TPU related message is the same for both backends ... I've compared the ESC/I command sequence of both backends and the only difference I noticed (from memory) is the use of 'ESC i' in the epkowa backend whereas the epson backend didn't. Logically, that should not matter though. 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
