[sane-devel] epson 4180 epkowa
Mickael Profeta writes: >>> Hi >>> I would like to use scanimage with my epson 4180. It is supported by epkowa backend, and iscan works. But I would like to do some scans on command line, without any gui, is it possible? >>> >> > Some more informations: > > I Have juste tried this > > fjord:/var/log# SANE_DEBUG_EPKOWA=255 scanimage -L > [sanei_debug] Setting debug level of epkowa to 255. > [... snip ...] > [epkowa] attach(libusb:004:005, 3) > [epkowa] attach: opening libusb:004:005 > [epkowa] Found valid EPSON scanner: 0x4b8/0x118 (vendorID/productID) > [epkowa] /usr/lib/libesint43.so: undefined symbol: __gxx_personality_v0 > [epkowa] sane_get_devices() Now, here is some useful information. > /usr/lib/libesint43.so: undefined symbol: __gxx_personality_v0 > May this line explain why I can not use scanimage > -depkowa:libusb:004:005 or xscanimage? Yes, it does. It indicates a dependency problem with the standard C++ libraries that libesint43.so needs and the ones that are installed on your system. The odd things is though, that you report that you can use your scanner when using iscan ... Hmm, iscan itself is written in C++ (nominally at least) so it probably loads the required library in time for libesint43.so (which is loaded dynamically) to use. When you use scanimage (written in pure C), this does not happen so ... I guess we need to review how our libesint*s get build and make them take care of loading the libraries they require on their own so that the epkowa backend is fully usable with pure C SANE frontends again. Note, this problem should only affect the following scanners: - GT-7200 / Perfection 1250 - GT-7300 / Perfection 1260 - GT-9400 / Perfection 3170 - GT-F600 / Perfection 4180 as these are the only ones that use libesint* modules. I know this does not solve your problem, but at least you know what is wrong. I'll file an internal bug report. -- Olaf MeeuwissenEPSON KOWA Corporation, PF1 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] Update Genius ColorPage-Vivid Pro II status to "supported"
Hi Anderson, On Monday 14 February 2005 00:31, Anderson Lizardo wrote: > Hi, > > Some days ago I've released the first version of the SANE backend for the > Genius ColorPage-Vivid Pro II scanner (geniusvp2). The backend is available > at: > > http://sourceforge.net/projects/geniusvp2/ > > So can some SANE developer update its status? The .desc file is attached. Okay - added with one small change: http://www.geniusnet.com.tw/ --> http://www.genius-kye.com > > For now I'd like to keep the backend external because there are some issues > to > fix (like the filename reorganization to get rid of the geniusvp2-misc.c > file). Also the backend is currently Linux-only because it uses ppdev > directly instead of libieee1284. Therefore I'd like to make it more portable > before asking for SANE addition. You might have a look at the sanei_pp library, which is supposed to be used for parallel-port devices. Currently only the plustek_pp backend uses it, maybe you find it useful. Ciao, Gerhard
[sane-devel] unique device infos
Hi, does sane currently export device informations like: manufacturer, model and ID/serial number? This would help me in further processing the output of sane. thanks Kai-Uwe Behrmann + development for color management + imaging / panoramas + email: k...@gmx.de + http://www.behrmann.name
[sane-devel] Re: SANE & LS50ED
Hubert Figuiere wrote: >Can we have the documentation of the scanner protocol ? :-) > > Yes. Call Nikon, they'll point you to the application forms. You have to sign a NDA and they send you the docs on CDs. johannes
[sane-devel] epson 4180 epkowa
Hi, >>/usr/lib/libesint43.so: undefined symbol: __gxx_personality_v0 >>May this line explain why I can not use scanimage >>-depkowa:libusb:004:005 or xscanimage? >> >> > >Yes, it does. It indicates a dependency problem with the standard C++ >libraries that libesint43.so needs and the ones that are installed on >your system. The odd things is though, that you report that you can >use your scanner when using iscan ... Hmm, iscan itself is written in >C++ (nominally at least) so it probably loads the required library in >time for libesint43.so (which is loaded dynamically) to use. When you >use scanimage (written in pure C), this does not happen so ... > > Ok, Thanks for the information. I manage to compile a version of scanimage which is compatible with the epkowa backend by replacing LINK = $(CC) $(LDFLAGS) -o $@ to LINK = g++ $(LDFLAGS) -o $@ in the frontend/Makefile of sane-backends. This a temporary good solution ;-) Some more questions now that I can scan with scanimage. Why the brightness option is not activate? # ./scanimage --help -d epkowa [...] --brightness 0..0 [inactive] Selects the brightness. [...] Is it possible to tune contrast/brightness in another way? Many thanks for your help! Mike
[sane-devel] Primax 400 (plustek_pp) only detected by kernel module
On Thu, 10 Feb 2005 16:02:22 +0100 Gerhard Jaeger wrote: > On Monday 07 February 2005 20:31, john wrote: > > On Mon, 7 Feb 2005 08:31:47 +0100 > > Gerhard Jaeger wrote: > > > > > On Friday 04 February 2005 22:57, john wrote: > > > > Hello, > > > > > > > > I've got an antique "Primax 4800 Driect 30 bit" which is > > > > supported by the plustek_pp module. > > > > > > > > If I load the kernel module, everything works fine. But using > > > > the[direct] user-mode driver, I get this from scanimage -L: > > > > > > > > > > > > [plustek_pp] Compare data=0x7f and status=0xf, port=0x0 > > > > [plustek_pp] p48xxReadWriteTest() > > > > [plustek_pp] Can't find your model, asic = 0x77 > > > > [plustek_pp] detectScannerConnection() returns -9031. > > > > [plustek_pp] * ASIC9800x * > > > > [plustek_pp] ResetPort() > > > > [plustek_pp] IOInitialize() > > > > [plustek_pp] * using readfunction >fnBiDirRead< > > > > [plustek_pp] ASIC = 0x00 > > > > [plustek_pp] Unknown ASIC-ID > > > > [plustek_pp] *** DETECTION DONE, result: -9020 *** > > > > > > > > No scanners were identified. > > > > > > > > I've tested on Debian unstable (2.4 kernel) and Slackware > > > > current(2.6 kernel) with the same results. Cn anyone point me to > > > > where I should start looking for the problem? > > > > > > > Hi, > > > > > > this could be because of different timing behaviour, when > > > accessing a device via kernel directly or via user-mode > > > application. As you didn't send the complete debug stuff, I simply > > > guess, that the parport didn't run in EPP mode (or is not detected > > > correctly), please make sure to have it in EPP mode (check BIOS > > > settings), also check the options for the parport_pc modules (no > > > IRQ should be assigned)... > > > > Gerhard, > > > > Thanks for the suggestions. Sadly, it's still not working. Here's > > the complete debugging output from "scanimage -L". My apologies to > > the list for posting such a long message. > > > [SNIPSNAP] > > [plustek_pp] Assigning port handle 0 > > [plustek_pp] ptdrvOpen(port=0x0) > > [plustek_pp] Try to claim the parport > > [plustek_pp] Setting SPP-mode > > [plustek_pp] Setting PS/2-mode > > [plustek_pp] We're using libIEEE1284 I/O > > [plustek_pp] Starting Scanner-Autodetection > > Hmmm, did you really check your BIOS settings? Please make sure, that > NO ECP is enabled. You might try and set the port to SPP mode. Also > set the parport_pc modules parameter, i.e. > options parport_pc io=0x378 irq=none > This seems to be necessary on some boards, esp. with VIA chipset. Gerhard, No, sorry, I've tried every combination, and nothing works. I would be happy to try to debug this myself (and to send you a patch, if I could find one). Is there any way I can get hold of any documentation to understand the conversation between the PC and the scanner? John
[sane-devel] [Epson 3170] Options for scanimage
Hi all, I bought this week-end an Epson 3170 and I am quite disppointed with scanimage's behaviour. Scans can be made all right, but several critical options seem to have no effect: --brightness --sharpness --threshold --speed Oddly, --preview makes the scan twice as long (making it 50s for --mode Color in 300dpi). On the other hand, --resolution does work. Is this a know problem with the 3170? Since --resolution works, I guess the problem does not stem from a faulty install, but I can make tests as needed. Thanks for your help. Seb.
[sane-devel] Best choice for an ADF
Hello, I need to buy an ADF-capable scanner; I guess not all models are fully supported, so a tip would be much appreciated. Its work will be to scan batches of up to 30 pages in color, 300 dpi, from the command line only (Debian, USB). I have used a HP 6300C for this job for quite some time but it is now broken. HP's 7450C looks like a good replacement, but support for the ADF is not clearly mentionned on the web site. I could not find a related thread in the archives as well (I checked the last six months). Would you recommend it for the job? Would another model fit the job better (or cheaper) ? (As my previous post shows, I have tried the Epson 3170 but unless the options problem can be solved quickly I'll just bring it back.) Thanks a lot for your advice! Seb.
[sane-devel] Update Genius ColorPage-Vivid Pro II status to "supported"
On Monday 14 February 2005 04:14, Gerhard Jaeger wrote: > On Monday 14 February 2005 00:31, Anderson Lizardo wrote: > > For now I'd like to keep the backend external because there are some > > issues to fix (like the filename reorganization to get rid of the > > geniusvp2-misc.c file). Also the backend is currently Linux-only because > > it uses ppdev directly instead of libieee1284. Therefore I'd like to make > > it more portable before asking for SANE addition. > > You might have a look at the sanei_pp library, which is supposed to be used > for parallel-port devices. Currently only the plustek_pp backend uses it, > maybe you find it useful. Hi, Okay, I'll try to use it. Thanks, -- Anderson Lizardo
