[sane-devel] HP ScanJet 6300c on Mac OS X 10.3
Hi. I have the exact same problem than in the SnapScan on Mac OS X 10.3 mail... However, the DEBUG flag doesn't make it work better. I can detect my scanner correctly (a ScanJet 6300C) but it will not work using the usual scanimage frontend. Here is (part) of a log while trying to make it work, both DEBUGs for Sanei and Hp to 255/3D255 [hp] hp_read_config: attach usb 0x03f0 0x0601 [hp] hp_attach_matching_devices: usb attach matching "usb 0x03f0 0x0601" [sanei_usb] sanei_usb_find_devices: vendor=0x03f0, product=0x0601 [hp] hp_attach: "libusb:025:007" [hp] sanei_hp_device_info_get: searching libusb:025:007 [hp] sanei_hp_device_info_get: check /dev/scanner [hp] sanei_hp_device_info_get: check libusb:025:007 [hp] hp_get_dev: New device libusb:025:007, connect-usb, scsi-request=0 [hp] sanei_hp_device_new: libusb:025:007 [hp] sanei_hp_device_info_get: searching libusb:025:007 [hp] sanei_hp_device_info_get: check /dev/scanner [hp] sanei_hp_device_info_get: check libusb:025:007 [hp] hp_nonscsi_open: open usb with "libusb:025:007" [sanei_usb] sanei_usb_open: libusb complained: usb_claim_interface: couldn't claim interface [hp] hp_nonscsi_open: open device libusb:025:007 failed [hp] nonscsi_new: open failed (Invalid argument) [hp] libusb:025:007: Can't open nonscsi device [hp] hp_read_config: reset to default config [hp] sane_get_devices will finish with Success ... This is using the Twain Sane packages by Mattias Ellert, on Mac OS X 10.3 (Panther), latest updates. I use this on a Powerbook G3/400 256RAM Thanks Mike
[sane-devel] Visioneer Onetouch 4400 USB (Visioneer/Primax Primascan Colorado 2600u, Memorex 6142u)
Sorry for the delay in replying. The Christmas festivities sort of caught up with me! (most enjoyable! :o) ). I'm doing a crash course in Apache so I can sort out my web page without going online each time (yes I know I can always load the html file directly into Mozilla but there are things I need to use a proper server for :o) ). So don't go away. On Thu, 11 Dec 2003 09:28:43 -0500 (EST) "m. allan noah" wrote: > hah hah. now you see why i said to use the business card instead of 4x6 :) unfortunately that was business card! :o( > > cat foo.log | perl spike3.pl > foo.out > > less foo.out > OK > 1. do you see any sort of packets repeating every few seconds? should be a > clear pattern, that is usually the system asking the scanner it's current > status (paper status, lid status, buttons status, lamp hot status, etc) > > 2. go down through those repeated packets and look for a change in the > contents of a packet from the scanner. that will be lamp getting hot, or > you doing something to the scanner. see how the system responds... > > you should be able to get a feel for what a 'command' looks like. ie: on a > fujitsu, you see something like: > > 31 byte command goes down to scanner, another block of varying length goes > either back to the system or down to the scanner, and a 13 byte status > command is read back from the scanner. > > so then you can build a list of 'this command writes a block, this one > reads, etc' > > allan Right, many thanks. Keith
[sane-devel] HP ScanJet 4200 backend ("hp4200") and SANE 1.0.13
Hi, On Mon, Dec 15, 2003 at 12:33:45AM +, adria...@users.sourceforge.net wrote: > I have tested latest patch and solving the bug that make the hp4200 backed > to > detect the scanner if any usb scanner was plugged in even if it was not a > hp4200. Maybe that one is not really solved but I need somebody's help > (Till?) > to try out a patched SANE and to tell me if the problem is now solved (if > not, a > debug trace will be welcomed; I don't own any other usb scanner to test). > > BTW, can anybody or has anybody tested the backend? You can download it > before public release from (this is the latest and updated patch): Ok, I'll take a look at it. I don't have such a scanner so I can't comment on if it really works. I'm rather looking for formal problems concerning inclusion in sane-backends. I guess this patch should be included in the sane-backends distribution? Would you be able to be the maintainer of that backend in this case? backend/hp4200.c: * The license is GPL only. There is no SANE clause. While this doesn't stop the backend from beeing included into SANE it may give vendors who provide non-GPL frontends together with SANE some headaches. Would you consider using the SANE license so we have the same license for all (?) backends? * #include "lm9830.h" This file should be called something like "hp4200-lm9830.h" to make clear that it's part of the hp4200 backend. If it's intended to be used by other backends it should go to the sanei directory. * int pv8630_reset_buttons (int fd) Should be static as everything but the sane_ API functions. If a symbol needs to be visible for others, please use sanei_hp4200_* as a name. To find out about "illegal" symbols: ./configure --enable-static make make libcheck --> | Libraries exporting 'illegal' symbols: | *** backend/.libs/libsane-gt68xx.a: | 75c0 T gt6801_u16b_download_firmware Ooops. This nasty author of the gt68xx backend, I'll kick him! :-) *** backend/.libs/libsane-hp4200.a: 1e30 T do_coarse_calibration 2950 T do_fine_calibration 0100 T hp4200c_what_button 3ec0 T hp4200_init_scanner 3850 T prepare_for_a_scan 0090 T pv8630_read_buttons 0040 T pv8630_reset_buttons 0ce0 T read_available_data 1b90 T read_required_bytes 13a0 T write_gamma 00d0 T lm9830_dump_registers 02a0 T lm9830_ini_scanner 0160 T lm9830_lamp_off 0200 T lm9830_lamp_on T lm9830_read_register 03f0 T lm9830_reset 0070 T lm9830_write_register * open/close on USB devices | static SANE_Status | add_device (SANE_String_Const name, HP4200_Device **argpd) [...] | fd = open (name, O_RDONLY); | if (fd == -1) [...] This won't work with libusb devices. You can't just use open() for them. Use the sanei_usb functions intead. The same is true for every read(), write(), open(), close() etc. E.g. you should not close() a "fd" opened with sanei_usb. In fact, that's not a file descriptor but some random number. lm9830.c: * see comment about name above * see comment about name of symbols above tools/Makefile.in: * update DISTFILES Compilation: I'm getting the following warnings: hp4200.c:164: warning: no previous prototype for `pv8630_reset_buttons' hp4200.c:172: warning: no previous prototype for `pv8630_read_buttons' hp4200.c: In function `hp4200_goto_home': hp4200.c:545: warning: implicit declaration of function `usleep' hp4200.c: At top level: hp4200.c:595: warning: no previous prototype for `read_available_data' hp4200.c: In function `read_available_data': hp4200.c:625: warning: pointer targets in passing arg 2 of `sanei_usb_read_bulk' differ in signedness hp4200.c:625: warning: pointer targets in passing arg 3 of `sanei_usb_read_bulk' differ in signedness hp4200.c: At top level: hp4200.c:825: warning: no previous prototype for `write_gamma' hp4200.c: In function `write_default_offset_gain': hp4200.c:901: warning: pointer targets in passing arg 2 of `sanei_usb_write_bulk' differ in signedness hp4200.c:916: warning: pointer targets in passing arg 2 of `sanei_usb_read_bulk' differ in signedness hp4200.c: At top level: hp4200.c:1098: warning: no previous prototype for `read_required_bytes' hp4200.c: In function `read_required_bytes': hp4200.c:1131: warning: pointer targets in passing arg 2 of `sanei_usb_read_bulk' differ in signedness hp4200.c:1131: warning: pointer targets in passing arg 3 of `sanei_usb_read_bulk' differ in signedness hp4200.c: In function `scanner_buffer_read': hp4200.c:1182: warning: pointer targets in passing arg 2 of `read_available_data' differ in signedness hp4200.c: At top level: hp4200.c:1193: warning: no previous prototype for `do_coarse_calibration' hp4200.c: In function `do_coarse_calibration': hp4200.c:1339: warning: pointer targets in passing arg 3 of `read_required_bytes' differ in signedness hp4200.c: At top level: hp4200.c:1521: warning: no previous prototype for `do_fine_calibration' hp4200.c: In function `do_fin
[sane-devel] saned doesn't release the parallel port when finished
Hi, On Tue, Dec 16, 2003 at 03:10:46PM -, Jim George wrote: > Can anyone give me an idea what is going wrong? > Dec 15 10:54:51 tassi saned[6609]: decode_handle: cancel: error while > decoding handle argument (h=0, Success) Ooops. That shouldn't happen. That lloks like a communication problem betwwen the net backend and saned. Or something else disturbs the flow of communication between saned and net. Such an error will end saned so the backend may not be able to "close" the parport. You have done a normal scan and have not cancelled it? Can you please try the following: disable saned in inetd.conf, restart inetd to apply that change, and start saned manually with debugging enabled: saned -d128 Please show us the output when you do a scan with scanimage. Bye, Henning
[sane-devel] Epson 1640SU, no devices found, RH 8.0
Hi, On Tue, Dec 16, 2003 at 09:32:19AM +, Tim Waugh wrote: > > If you remove the ltmain.sh hack, how do you want to get the linking > > independent of the the dll backend working? > > > > Most people won't use that feature but it's advertised in the SANE > > standard so it's a basic feature of SANE. I wouldn't call removing a > > feature "a fix". Well, it may be a temporary workaround but we all > > know how long "temporary" can take :-) > > If you would rather I start the errata process all over again with the > better fix (of removing the ld.so.conf stuff) -- which will lead to a > longer time before fixed packages are ready -- I will do that. Let me > know. It's your decision. I just wanted to point out that that it's not a bug fix but rather removing a (seldomly used) feature. I guess it's ok if you reenable it with the next release or whenever you change the package anyway. We'll see if anyone notice it at all. Bye, Henning
[sane-devel] has feeder loaded
The fujitsu backend offers a SOFT_DETECT, HARD_SELECT option 'startbutton' to query button1. The same thing could be done with 'paper in hopper' or else. But these options should have the same name for all backends. Is there such a known name or other interface? Oliver Am Dienstag 16 Dezember 2003 15:41 schrieben Sie: > there was some discussion about having one or more sane options that could > provide scanner status. they would have to be in a specific group, or have > specific indexes into the options array, or have specific names, so > finding them could be sort of ugly. > > i can think of a few things that the fujitsu scanners tell us: > > button1 pressed > button2 pressed > character on 'function' readout > number on 'copy' wheel > paper in hopper > cover open > lamp warm > > is there a general purpose way to expose this? > > allan > > On Tue, 16 Dec 2003, Oliver Schirrmeister wrote: > > is there a function in sane to ask if the document feeder > > is loaded (like the 'has feeder loaded' option in TWAIN)? > > > > Thanks > > > > Oliver
[sane-devel] saned doesn't release the parallel port when finished
Hi, I have now installed the 1.0.13 RPM build for SuSE 8.1 on my box and it appeared to work in that I could do a scan. However I've since discovered that it isn't releasing the parallel port when a scan is finished (snip from /var/log/messages at the bottom). I have a Mustek 1200CP (CIS) scanner on parport0. I have saned running from inetd.conf as sane.sane and the /dev/parport0 has crw-rw-rw permissions. Can anyone give me an idea what is going wrong? Dec 15 10:52:15 tassi kernel: ppdev0: registered pardevice Dec 15 10:52:15 tassi kernel: ppdev0: unregistered pardevice Dec 15 10:52:15 tassi kernel: ppdev0: registered pardevice Dec 15 10:52:15 tassi kernel: ppdev0: negotiated back to compatibility mode because user-space forgot Dec 15 10:52:15 tassi kernel: ppdev0: unregistered pardevice Dec 15 10:52:15 tassi kernel: ppdev0: registered pardevice Dec 15 10:52:46 tassi kernel: ppdev0: you've already got it! Dec 15 10:52:46 tassi kernel: ppdev0: you've already got it! Dec 15 10:52:46 tassi kernel: ppdev0: negotiated back to compatibility mode because user-space forgot Dec 15 10:52:46 tassi kernel: ppdev0: released pardevice because user-space forgot Dec 15 10:52:46 tassi kernel: ppdev0: unregistered pardevice Dec 15 10:54:49 tassi saned[6609]: saned (AF-indep+IPv6) from sane-backends 1.0.13 ready Dec 15 10:54:49 tassi saned[6609]: check_host: access by remote host: 192.168.0.4 Dec 15 10:54:49 tassi saned[6609]: init: access granted to jgeorge@192.168.0.4 Dec 15 10:54:49 tassi saned[6609]: [sanei_debug] Setting debug level of mustek_pp to 2. Dec 15 10:54:49 tassi kernel: ppdev0: registered pardevice Dec 15 10:54:49 tassi kernel: ppdev0: unregistered pardevice Dec 15 10:54:49 tassi kernel: ppdev0: registered pardevice Dec 15 10:54:49 tassi kernel: ppdev0: negotiated back to compatibility mode because user-space forgot Dec 15 10:54:49 tassi kernel: ppdev0: unregistered pardevice Dec 15 10:54:51 tassi saned[6609]: decode_handle: cancel: error while decoding handle argument (h=0, Success) Thanks and Regards, Jim
[sane-devel] has feeder loaded
Oliver wrote: > is there a function in sane to ask if the document feeder > is loaded (like the 'has feeder loaded' option in TWAIN)? But hopefully more reliable. Here's two typical TWAIN conversations (with an HP): Do you have a feeder? -Yes Can you tell me if the feeder is loaded? -Yes Is the feeder loaded? -I don't know Is the feeder enabled? -No Please enable the feeder. -OK Is the feeder enabled? -Yes Please disable the feeder. -OK Is the feeder enabled? -Yes Phil
[sane-devel] has feeder loaded
is there a function in sane to ask if the document feeder is loaded (like the 'has feeder loaded' option in TWAIN)? Thanks Oliver
[Fwd: Re: [sane-devel] Epson Stylus CX-6400]
On Wed, Nov 26, 2003 at 04:22:09PM -0100, gerard klaver wrote: > > On Wed, 2003-11-26 at 13:40, Bernie Gardner wrote: > > I am trying to get an Epson Stylus CX6400 to work in SuSE Linux 9.0. > > [snip] > > > > But scanimage -L says no scanners were identified. If I try to use > > Kooka as a front end, it identifies: > > > > epkowa:/dev/usb/scanner0 > > Epson PX-A650 > > > > but doesn't actually do anything. > > > > I can't figure where the PX-A650 identification is coming from. > > Some Epson scanners have a different name for different part of the > world but the software can handle only one name. > The Epson perfection 1660 photo for example is when used with XSANE > named GT8300. > > with sane-find-scanner -v -v (as root) or with lsusb -v you can collect > more data The Perfection 1660 Photo (a.k.a. GT-8300UF) is supported by the epson and epkowa backends. The latter is distributed as part of "Image Scan! for Linux". The reason behind the puzzling names is that EPSON markets the same scanner under different names in different parts of the world. That used to be no problem for backend writers because the scanner nicely identified itself with something that resembled the label on the scanner. However, for some time now, the scanner returns the same name no matter what it says on the label. Generally, this is the name the scanner is marketed under in Japan. For the epkowa backend we are cooking up some ESP to at least try to show you the right name. Note, this has not been released yet and is necessarily not fool-proof (because the scanner doesn't provide any clue). > if you send this information to the list or fill in the form see data on > http://www.sane-project.org/contrib.html > > then this can be added to the unsupported list and can speed up the > proces of getting a working backend. -- Olaf MeeuwissenEPSON KOWA Corporation, ECS 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] Sane only available to Super User - Canon FP330P
On Tue, Dec 16, 2003 at 12:59:24AM +, Till Kamppeter wrote: > Matthew Duggan wrote: > > ... > >trying both methods, because depending on your hardware setup, > >xsane through saned may be faster than running xsane directly. > > > > Why is X-Sane through saned faster than direct scanner access with > X-Sane? Should I modify scannerdrake (scanner setup tool of Mandrake > Linux) so that all scanners get configured via saned? > >Till Hi, I think this comment only really applies if you have a very slow X server. I noticed the behaviour myself when I was running an X server on a remote machine and xsane was running on the machine with the scanner. It appeared to block while rendering the scanned image to the window (which was a slow operation over a 10MBit network). I haven't looked closely at the xsane code so I'm not sure if it's multithreaded, but I assume not. I noticed that running xsane to saned through loopback considerably improved the speed of scanning, because it kept buffering and reading as fast as it could while the slow network transfers were happening. I also gained speed through saned by changing the backend code to always read as much as the scanner's internal buffer could hold, then feeding that data to the frontend as it asked for it. This reduced the number of reads from the parallel port. With a non-buffering backend, saned could actually end up considerably slower because it asks for small scan segments at a time. Cheers, - Matthew Duggan
[sane-devel] has feeder loaded
there was some discussion about having one or more sane options that could provide scanner status. they would have to be in a specific group, or have specific indexes into the options array, or have specific names, so finding them could be sort of ugly. i can think of a few things that the fujitsu scanners tell us: button1 pressed button2 pressed character on 'function' readout number on 'copy' wheel paper in hopper cover open lamp warm is there a general purpose way to expose this? allan On Tue, 16 Dec 2003, Oliver Schirrmeister wrote: > is there a function in sane to ask if the document feeder > is loaded (like the 'has feeder loaded' option in TWAIN)? > > Thanks > > Oliver > > > -- "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] Epson 1640SU, no devices found, RH 8.0
--HB4mHL4PVvkpZAgW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 15, 2003 at 11:35:38PM +0100, Henning Meier-Geinitz wrote: > If you remove the ltmain.sh hack, how do you want to get the linking > independent of the the dll backend working? >=20 > Most people won't use that feature but it's advertised in the SANE > standard so it's a basic feature of SANE. I wouldn't call removing a > feature "a fix". Well, it may be a temporary workaround but we all > know how long "temporary" can take :-) If you would rather I start the errata process all over again with the better fix (of removing the ld.so.conf stuff) -- which will lead to a longer time before fixed packages are ready -- I will do that. Let me know. Thanks, Tim. */ --HB4mHL4PVvkpZAgW Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/3tEi9gevn0C09XYRAiTgAKCMiH5Piw9zhgLCDhEOOvSv5xGfVACgumqc SvoZrmr0JQJxRnsEjrErY6Q= =gBPY -END PGP SIGNATURE- --HB4mHL4PVvkpZAgW--
[sane-devel] Sane only available to Super User - Canon FP330P
On Mon, Dec 15, 2003 at 07:22:37PM +1300, Kim L. Mantle wrote: > Matthew > > Many thanks for your advice. > > I have taken heed of your advice and completed those changes to the > canon_pp.conf file and all works sweetly. > > Tell me though Matthew - is option 2 an option, as such, or can the changes > be made in conjunction with Till's suggestion plus your amendment (option > 1)? > > Kind regards > > Kimbo Hi, Sorry, I should have explained more clearly. Setting up your user to have access to the parport will allow you to access the backend directly without the need for running saned. The changes can be made independently so you can do both if you want. I'd recommend trying both methods, because depending on your hardware setup, xsane through saned may be faster than running xsane directly. Cheers, Matthew
[sane-devel] sanei_usb.h header with errors
> I've been trying to compile a simple little app. for a while, but > whenever I try to include the "sanei_usb.h" header, it returns an > error about certain parsing errors before size_t declarations. Has > anyone else seen this? Such reports aren't much use without a verbatim copy of the actual error message. Anyway, parsing errors mean literally just that: the compiler found something it can't make sense of. In your case, it's probably an unknown type (i.e. a missing typedef). Remedy (guess off the top of my head): include sane/sane.h and sane/sanei.h before sane/sanei_usb.h, in that order. Andras === Major Andras e-mail: and...@users.sourceforge.net www:http://andras.webhop.org/ ===
[sane-devel] Sane only available to Super User - Canon FP330P
Matthew Duggan wrote: > On Mon, Dec 15, 2003 at 07:22:37PM +1300, Kim L. Mantle wrote: > >>Matthew >> >>Many thanks for your advice. >> >>I have taken heed of your advice and completed those changes to the >>canon_pp.conf file and all works sweetly. >> >>Tell me though Matthew - is option 2 an option, as such, or can the changes >>be made in conjunction with Till's suggestion plus your amendment (option >>1)? >> >>Kind regards >> >>Kimbo > > > Hi, > > Sorry, I should have explained more clearly. Setting up your user to > have access to the parport will allow you to access the backend > directly without the need for running saned. The changes can be > made independently so you can do both if you want. I'd recommend > trying both methods, because depending on your hardware setup, > xsane through saned may be faster than running xsane directly. > Why is X-Sane through saned faster than direct scanner access with X-Sane? Should I modify scannerdrake (scanner setup tool of Mandrake Linux) so that all scanners get configured via saned? Till
[sane-devel] Epson 1640SU, no devices found, RH 8.0
On Monday 15 December 2003 23:00, Tim Waugh wrote: > Oliver, > > It is a buggy configuration in redhat 9.0 and this also causes > > problems when the rpm is uninstalled and sane-backends is > > installed from source with -prefix=3D/usr because the entry /usr/lib/= sane > > is not removed from /etc/ld.so.conf when the sane-backends rpm > > is uninstalled. > > Did you test this? I believe it to be incorrect, and I think that the > entry is removed. You are right. The entry is removed when I do rpm --nodeps -e sane-backends > > In any case, I already explained that future sane-backends packages > will omit the ld.so.conf tampering. In fact, the current development > Fedora package has this removed right now. > > At present there is a sane-backends package in the works which undoes > the hacky (IMHO) libsane.so.1-force in ltmain.sh. I understand that > your preferred solution would be to remove the incorrect ld.so.conf > tampering; however starting with new fixed packages at this stage > would only delay things, while the difference between the two fixes is > quite minimal and will be largely unnoticed. At this stage I'd rather > get SANE working again on Red Hat Linux systems. Ok. Because the bad entry in /etc/ld.so.conf is removed when sane-backend= s.rpm=20 is erased I do not see a big problem. The only bad thing I see is that if= =20 someone replaces /usr/lib/libsane.so.1 by a library from /usr/lib/sane/=20 (which has a different soname) and then compiles a frontend he gets in=20 trouble. But with a bit luck this will not happen at all. Oliver --=20 http://www.xsane.org http://www.mostang.com/sane http://www.rauch-domain.de mailto:oliver.ra...@rauch-domain.de
