[sane-devel] Epson 4490 in Debian

[Olaf Meeuwissen]

Fredrik Sandstrom  writes:

> Olaf Meeuwissen  writes:
>> If you're using iscan, then it's an arguably stupid limitation in the
>> frontend.  If you also hit this when using other frontend let me know
>> what
>> 
>>   $ SANE_DEBUG_EPKOWA=10 scanimage 2> perfection-4490.log
>> 
>> barfs into the perfection-4490.log file.
>> 
>> There should be a list of the resolutions that the device claims to be
>> able to handle.
>
> It only gives these resolutions:
> [epkowa] resolution (dpi): 300
> [epkowa] resolution (dpi): 600
> [epkowa] resolution (dpi): 1200
> [epkowa] resolution (dpi): 2400
>
> But iscan gives a lot more options, but alas 2400 is the highest
> resolution there too. The scanner is however advirtised as being
> capable of 4800x9600.

Your scanner can scan at 4800dpi optical.  However, the support level
of the epkowa (and epson) backend only allow settings in the list you
included :-(  The iscan frontend does the other ones in software.

To add support for resolutions > 3200 modifications in both the
frontend as well as the backend are required.

If you want this supported, I suggest you file a support request with

  pipsnews at avasys.jp

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 3170 in Kubuntu

[Olaf Meeuwissen]

Adrian Jadic  writes:

> My mistake: I had installed the libsane-extras but not the iscan plugin.
>
> Now it works only with iscan.

If you have the plugin installed, it ought to work with other SANE
frontends as well.  But wait!  You run on AMD64, right?  It won't work
with 64bit.  You will need to run all your SANE stuff in 32bit mode.

> Since I see you are at avasys could you explain to me why in SUSE 9.3 kooka 
> works just fine with this scanner (w epkowa installed) and in later suse 
> releases as well as in Kubuntu (as I found out) I cannot get Kooka to fire up 
> the scanner?

Up until iscan-1.17.0, the source and binary packages included all
plugins.  The list of plugins kept growing, leading to ever larger
source tarballs and binary packages.  So with iscan-1.18.0 we split
the binary package into a core package and several plugin packages.
With iscan-2.0.0 we also dropped the plugins from the source tarball.

This leads to a situation where now you just install the core package
and have out-of-the-box support for the majority of EPSON devices.
Only a select few require a single plugin to get the same kind of
support.  You only install what you really need now and are no longer
"burdened" with a load of non-free binary stuff you don't need anyway.

FTR, the binary packages went down from close to a megabyte to about
one third of that and the source tarballs from about two megabyte to
half that.

> I managed to make kooka see the scanner by inserting a line with the data for 
> this scanner in the etc/udev/rules.d/45-libsane.rules. Before it would only 
> see it if run in root.

The upcoming release will have (experimental) udev support as well,
making things even easier.

> So now kooka displays that small window with "choosing device" and the Epson 
> 3170 is listed correctly.
> But when I press "preview" or "scan" nothing happens.

Hmm, that's weird.  If listed in the window to choose a device, the
backend did see the device allright.  Could you take a look at the
debugging output?

  $ SANE_DEBUG_EPKOWA=50 iscan 2> debug.log

The output will end up in the debug.log file.

> Thank you,
> A Jadic
>
> On Tuesday 13 June 2006 00:54, you wrote:
>> Adrian Jadic  writes:
>> > I have trouble using the Epson Perfection 3170 Photo in Kubuntu 6.06
>> >
>> > Kooka and scanimage recognise the scanner. However when I try to scan I
>> > am getting the following errors:
>> > =
>> > ~$ scanimage -L
>> > device `epson:libusb:001:004' is a Epson  flatbed scanner
>>
>> This scanner is NOT supported by the epson backend.  It is also not
>> supported by the plustek or snapscan backends.  If you want to use
>> this scanner, you will have to use the epkowa backend together with a
>> non-free binary-only plugin.  Some distributions now include this
>> backend but the plugin is probably only available via:
>>
>>   http://www.avasys.jp/english/linux_e/index.html
>>
>> > ~$ scanimage
>> > scanimage: sane_start: Invalid argument
>> > ~$ kooka
>> > libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
>> > libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
>> > ScimInputContextPlugin()
>> > ~ScimInputContextPlugin()
>> > ~$
>> > =
>> > This happens in both root and user.
>> > Can anyone help me get further here? This scanner works fine in SUSE 9.3
>> >
>> > metricus
>> > AMD 3000+, 1GB RAM, Kubuntu 6.06
>>
>> The plugin is only available for i386 ...
>>
>> Hope this helps,

As always, 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] Microtek Scanmaker 35t+ "Error during device I/O"

[Matt Henley]

se-1 Support? yes
> [microtek] Can Disable Linearization Table? no
> [microtek] Can Disable Start-of-Scan Recalibration? no
> [microtek] Internal expanded expansion? no
> [microtek] == End of Scanner Inquiry Report ===
> [microtek] attach_scanner:  happy.
> [microtek] sane_init:  config-> /dev/sg2
> [microtek] attach_scanner:  /dev/sg2
> [microtek] sane_get_devices
> [microtek] sane_open
> [microtek] sane_open:  find device...
> [microtek] sane_open:  create scanner...
> [microtek] sane_open:  initialize scanner dependent stuff...
> [microtek] sane_open:  All calibration routines disabled.
> [microtek] sane_open:  init gamma tables...
> [microtek] sane_open:  init pass-time variables...
> [microtek] sane_open:  init clever cache...
> [microtek] sane_open:  initialize options:
> [microtek] init_options...
> [microtek] init_options:  quant yes
> [microtek] init_options:  done.
> [microtek] sane_control_option (opt=0,act=0,val=0xbfd3078c,info=(nil))
> [microtek] sane_control_option (opt=0,act=0,val=0xbfd27668,info=(nil))
> [microtek] sane_get_option_descriptor (0)...
> [microtek] sane_get_option_descriptor (1)...
> [microtek] sane_get_option_descriptor (2)...
> [microtek] sane_get_option_descriptor (3)...
> [microtek] sane_get_option_descriptor (4)...
> [microtek] sane_get_option_descriptor (5)...
> [microtek] sane_get_option_descriptor (6)...
> [microtek] sane_get_option_descriptor (7)...
> [microtek] sane_get_option_descriptor (8)...
> [microtek] sane_get_option_descriptor (9)...
> [microtek] sane_get_option_descriptor (10)...
> [microtek] sane_get_option_descriptor (11)...
> [microtek] sane_get_option_descriptor (12)...
> [microtek] sane_get_option_descriptor (13)...
> [microtek] sane_get_option_descriptor (14)...
> [microtek] sane_control_option (opt=14,act=0,val=0x8051684,info=(nil))
> [microtek] sane_get_option_descriptor (15)...
> [microtek] sane_control_option (opt=15,act=0,val=0x8051688,info=(nil))
> [microtek] sane_get_option_descriptor (16)...
> [microtek] sane_get_option_descriptor (17)...
> [microtek] sane_get_option_descriptor (18)...
> [microtek] sane_get_option_descriptor (19)...
> [microtek] sane_get_option_descriptor (20)...
> [microtek] sane_get_option_descriptor (21)...
> [microtek] sane_get_option_descriptor (22)...
> [microtek] sane_get_option_descriptor (23)...
> [microtek] sane_get_option_descriptor (24)...
> [microtek] sane_get_option_descriptor (25)...
> [microtek] sane_get_option_descriptor (26)...
> [microtek] sane_get_option_descriptor (27)...
> [microtek] sane_get_option_descriptor (28)...
> [microtek] sane_get_option_descriptor (29)...
> [microtek] sane_get_option_descriptor (30)...
> [microtek] sane_get_option_descriptor (31)...
> [microtek] sane_get_option_descriptor (32)...
> [microtek] sane_get_option_descriptor (33)...
> [microtek] sane_control_option (opt=12,act=0,val=0xbfd27664,info=(nil))
> [microtek] sane_control_option (opt=13,act=0,val=0xbfd27664,info=(nil))
> [microtek] sane_control_option (opt=12,act=0,val=0xbfd30780,info=(nil))
> [microtek] sane_get_option_descriptor (14)...
> [microtek] sane_control_option
> (opt=14,act=1,val=0xbfd30784,info=0xbfd27668)
> [microtek] sane_control_option (opt=13,act=0,val=0xbfd30780,info=(nil))
> [microtek] sane_get_option_descriptor (15)...
> [microtek] sane_control_option
> (opt=15,act=1,val=0xbfd30784,info=0xbfd27668)
> [microtek] sane_start...
> [microtek] sane_get_parameters...
> [microtek] sane_get_parameters:  regular 1-pass color
> [microtek] sane_get_parameters:  res_code = 5 ( 5)
> [microtek] bright_r of 0 set to 0x0
> [microtek] sane_get_parameters:  dots_per_mm:  3.937008
> [microtek] sane_get_parameters:  units_per_mm:  76.771654
> [microtek] WIDTHPIX:  before exp: 136
> [microtek] sane_get_parameters:  lines: 137  ppl: 136  bpl: 408
> [microtek] .wait_ready 5...
> [microtek] finagle_precal...
> [microtek] .scanning_frame...
> [microtek] .scanning_frame:  in- 0,0  2686,2686
> [microtek] .scanning_frame: out- 0,0  2686,2686
> [microtek] .accessory...
> [microtek] .download_gamma...
> [microtek] .download_gamma:  1024 entries of 2 bytes, max 255
> [microtek] .download_gamma: by default
> [microtek] end_scan...
> scanimage: sane_start: Error during device I/O
> [microtek] sane_cancel...
> [microtek] end_scan...
> [microtek] sane_close...
> [microtek] sane_exit...
> [microtek] sane_exit:  MICROTEK says goodbye.
>
>
>
> --
> sane-devel mailing list: sane-devel@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
> Unsubscribe: Send mail with subject "unsubscribe your_password"
>  to sane-devel-requ...@lists.alioth.debian.org
>
>
>
-- next pa

[sane-devel] Epson 4490 in Debian

[Johannes Meixner]

Hello,

On Jun 13 15:13 Julien BLACHE wrote (shortened):
> >> What I have done
> >> now is suggesting to the upstream developers to make two packages, one
> >> with the frontend and one with the backend, to be more distro-friendly.
> >> I have no answer yet, lets see what they say.
> >
> > Be prepared to be very patient - I asked this since 14 Jul 2004,
> > see the shortened mail at the bottom :-(
> 
> And the answer will probably be "it would confuse our users even
> more"

Of course it must be terrible confusing for the poor users,
when they have out of the box Linux support for their devices
in all Linux distributions on all hardware platforms ;-)

Some more what I already wrote in my above mentioned mail:
##
See
http://portal.suse.com/sdb/en/2003/11/jsmeix_print-info-for-manufacturers.html
for the advantages for manufacturers of free software
(of course it applies also for scanners):
-
The advantage for the ... manufacturer is that he will receive
comprehensive Linux support for his devices in all products ...
on all hardware platforms for which these products are available
and for new versions of the products ... without any extra expenses
for the ... manufacturer.
-
##


> but then, so does using japanese model names all over the
> place. I'm a bit fed up with trying to remember which japanese model
> name matches which non-japanese model name :/
> (It's painful enough with all those rebranded scanners, so if
> manufacturers like Epson could stick to having only one model name...)

I don't care about model names or whatever else when I get a free
normal working driver for all those models ;-)


> > Perhaps it helps the Epson Avasys decision makers to make the right
> > decisions when all (or at least almost all) Linux distributors
> > demand the same thing.
> 
> It'd be nice if something could be organised between Epson's
> management, SANE developers (Henning ? khk ? Oliver Schwartz ?) and
> some key distributions to discuss the situation and see what can be
> done to improve it as much as possible. (obviously I'd have no problem
> attending such a meeting, as long as I am available on that day and
> can make it to the meeting).

Same for me.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5  Mail: jsm...@suse.de
90409 Nuernberg, GermanyWWW: http://www.suse.de/

[sane-devel] How to detect USB scanners on linux?

[m. allan noah]

rupesh- commands you might be interested in:

tail /var/log/messages
dmesg | tail
lsusb
lsusb -v

use these before and after you connect the device, to make sure it shows 
up. if it does not, you have basic usb issues that you need to address 
first. i would suggest moving to a more recent linux, something with a 2.6 
kernel :)

if the device shows up, then i would suggest that you try to build a 
little libusb program, entirely outside of sane, that can find and talk to 
the scanner.

allan

On Tue, 13 Jun 2006, Rupesh Tarpara wrote:

> Hi,
>
> I am using Redhat AS 3, update 7. kernel string 2.4.21-40.EL.
>
> I am developing sane backend for USB hand held image scanner.
>
> Problem :-
>
> When I connect the USB device and run 'sane-find-scanner' command, it does
> not detect my usb scanner. It displays error message as, 'make sure usb host
> controller driver is installed and kernel scanner module is loaded'.
>
> 1) The files present in /dev/usb are :-
>
> scanner0   scanner10  scanner12  scanner14  scanner2   scanner4   scanner6
> scanner8
> scanner1   scanner11  scanner13  scanner15  scanner3   scanner5   scanner7
> scanner9
>
> 2) the files present in /etc/hotplug are :-
>
> blacklist  ieee1394.agent  pcipci.rc  usb.agent
> usb.handmap  usb.usermap
> hotplug.functions  net.agent   pci.agent  usb usb.distmap  usb.rc
>
> 3) output of lsmod is:-
>
> Module  Size  Used byNot tainted
> ide-cd 33920   0  (autoclean)
> cdrom  32416   0  (autoclean) [ide-cd]
> i810_audio 29784   0  (autoclean)
> ac97_codec 17736   0  (autoclean) [i810_audio]
> soundcore   6436   2  (autoclean) [i810_audio]
> agpgart57752   6  (autoclean)
> audit  89944   2  (autoclean)
> usbserial  23420   0  (autoclean) (unused)
> parport_pc 18756   1  (autoclean)
> lp  8964   0  (autoclean)
> parport36832   1  (autoclean) [parport_pc lp]
> autofs416152   0  (autoclean) (unused)
> e100   28264   1
> mii 4516   0  [e100]
> floppy 56624   0  (autoclean)
> sg 36236   0  (autoclean) (unused)
> scsi_mod  107180   1  (autoclean) [sg]
> microcode   5688   0  (autoclean)
> keybdev 2944   0  (unused)
> mousedev5524   1
> hid22244   0  (unused)
> input   5888   0  [keybdev mousedev hid]
> ehci-hcd   20008   0  (unused)
> usb-uhci   25740   0  (unused)
> usbcore77408   1  [usbserial hid ehci-hcd usb-uhci]
> ext3   85864   2
> jbd50956   2  [ext3]
>
> ===\
>
> can anyone guide me what is wrong? Where to look for usb scanner device
> file?
> is it necessary to install, usb-serial port emulator driver(kernel module)
> for scanner device on linux? (as usbserial module is already present)
>
> Thanks in advance,
>
> Rupesh Tarpara
>
>
>
>
>
> http://www.patni.com
> World-Wide Partnerships. World-Class Solutions.
> _
>
> This e-mail message may contain proprietary, confidential or legally
> privileged information for the sole use of the person or entity to
> whom this message was originally addressed. Any review, e-transmission
> dissemination or other use of or taking of any action in reliance upon
> this information by persons or entities other than the intended
> recipient is prohibited. If you have received this e-mail in error
> kindly delete  this e-mail from your records. If it appears that this
> mail has been forwarded to you without proper authority, please notify
> us immediately at netad...@patni.com and delete this mail.
> _
>

-- 
"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 4490 in Debian

[Fredrik Sandstrom]

Olaf Meeuwissen  writes:
> If you're using iscan, then it's an arguably stupid limitation in the
> frontend.  If you also hit this when using other frontend let me know
> what
> 
>   $ SANE_DEBUG_EPKOWA=10 scanimage 2> perfection-4490.log
> 
> barfs into the perfection-4490.log file.
> 
> There should be a list of the resolutions that the device claims to be
> able to handle.

It only gives these resolutions:
[epkowa] resolution (dpi): 300
[epkowa] resolution (dpi): 600
[epkowa] resolution (dpi): 1200
[epkowa] resolution (dpi): 2400

But iscan gives a lot more options, but alas 2400 is the highest
resolution there too. The scanner is however advirtised as being
capable of 4800x9600.

-- 
Fredrik Sandstr?m
f...@iki.fi

[sane-devel] Epson 4490 in Debian

[Julien BLACHE]

Johannes Meixner  wrote:

Hi,

> I would appreciate it if the free version of Iscan would
> be as much as possible the same on Debian and on Suse
> (and on any other distribution).
> If you (or any other distribution package maintainer) are
> interested, please contact me.

Of course. I think I'm going to split epkowa from libsane-extras
anyway, as libsane-extras was intended as a collection of experimental
backends in the first place.

JB.

-- 
Julien BLACHE    
  GPG KeyID 0xF5D65169

[sane-devel] Epson 4490 in Debian

[Julien BLACHE]

Johannes Meixner  wrote:

Hi,

>> What I have done
>> now is suggesting to the upstream developers to make two packages, one
>> with the frontend and one with the backend, to be more distro-friendly.
>> I have no answer yet, lets see what they say.
>
> Be prepared to be very patient - I asked this since 14 Jul 2004,
> see the shortened mail at the bottom :-(

And the answer will probably be "it would confuse our users even
more", but then, so does using japanese model names all over the
place. I'm a bit fed up with trying to remember which japanese model
name matches which non-japanese model name :/

(It's painful enough with all those rebranded scanners, so if
manufacturers like Epson could stick to having only one model name...)

> I like to emphasize that it is not Olaf Meeuwissen who is to blame
> that there is almost no progress here.

Indeed, Olaf does as much as humanly possible to improve the
situation, but even sending patches to him doesn't help as he doesn't
have the time to merge them due to tight deadlines and schedule (he's
sending patches to himself to queue them until management allocates a
time frame to merge them in, IIRC).

And management is, well, management, aggravated by the fact that this
is a japanese company, the development is split between two entities
and includes IP from some other entities, with horrible communication
between the parties involved.

Basically, this is the situation as I get it, correct me if I'm wrong :)

> Perhaps it helps the Epson Avasys decision makers to make the right
> decisions when all (or at least almost all) Linux distributors
> demand the same thing.

It'd be nice if something could be organised between Epson's
management, SANE developers (Henning ? khk ? Oliver Schwartz ?) and
some key distributions to discuss the situation and see what can be
done to improve it as much as possible. (obviously I'd have no problem
attending such a meeting, as long as I am available on that day and
can make it to the meeting).

JB.

-- 
Julien BLACHE    
  GPG KeyID 0xF5D65169

[sane-devel] Epson 3170 in Kubuntu

[Adrian Jadic]

My mistake: I had installed the libsane-extras but not the iscan plugin.

Now it works only with iscan.

Since I see you are at avasys could you explain to me why in SUSE 9.3 kooka 
works just fine with this scanner (w epkowa installed) and in later suse 
releases as well as in Kubuntu (as I found out) I cannot get Kooka to fire up 
the scanner?
I managed to make kooka see the scanner by inserting a line with the data for 
this scanner in the etc/udev/rules.d/45-libsane.rules. Before it would only 
see it if run in root.
So now kooka displays that small window with "choosing device" and the Epson 
3170 is listed correctly.
But when I press "preview" or "scan" nothing happens.

Thank you,
A Jadic

On Tuesday 13 June 2006 00:54, you wrote:
> Adrian Jadic  writes:
> > I have trouble using the Epson Perfection 3170 Photo in Kubuntu 6.06
> >
> > Kooka and scanimage recognise the scanner. However when I try to scan I
> > am getting the following errors:
> > =
> > ~$ scanimage -L
> > device `epson:libusb:001:004' is a Epson  flatbed scanner
>
> This scanner is NOT supported by the epson backend.  It is also not
> supported by the plustek or snapscan backends.  If you want to use
> this scanner, you will have to use the epkowa backend together with a
> non-free binary-only plugin.  Some distributions now include this
> backend but the plugin is probably only available via:
>
>   http://www.avasys.jp/english/linux_e/index.html
>
> > ~$ scanimage
> > scanimage: sane_start: Invalid argument
> > ~$ kooka
> > libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
> > libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
> > ScimInputContextPlugin()
> > ~ScimInputContextPlugin()
> > ~$
> > =
> > This happens in both root and user.
> > Can anyone help me get further here? This scanner works fine in SUSE 9.3
> >
> > metricus
> > AMD 3000+, 1GB RAM, Kubuntu 6.06
>
> The plugin is only available for i386 ...
>
> Hope this helps,

[sane-devel] Epson 4490 in Debian

[Johannes Meixner]

Hello,

On Jun 13 13:30 Till Kamppeter wrote (shortened):
> Johannes Meixner wrote:
> > Some time ago I got a nice patch from Dirk O. Siebnich
> > from which I made our patch to build our iscan-free package
> > which is a really free version of the epkowa backend
> > (this means the /usr/bin/iscan frontend was also removed
> > because it requires a non-free library).
...
> I have seen it on our OpenSuSE mirror here at Mandrive.

Note that our current iscan-free is still based upon
iscan-1.18.0-1.c2.tar.gz - i.e. it is not yet updated
to the current Iscan version.


> What I have done
> now is suggesting to the upstream developers to make two packages, one
> with the frontend and one with the backend, to be more distro-friendly.
> I have no answer yet, lets see what they say.

Be prepared to be very patient - I asked this since 14 Jul 2004,
see the shortened mail at the bottom :-(
I like to emphasize that it is not Olaf Meeuwissen who is to blame
that there is almost no progress here.

Perhaps it helps the Epson Avasys decision makers to make the right
decisions when all (or at least almost all) Linux distributors
demand the same thing.


By the way:
The same problem exists for the Epson Avasys printer drivers
"pips" and "pipslite".


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5  Mail: jsm...@suse.de
90409 Nuernberg, GermanyWWW: http://www.suse.de/

#
Date: Wed, 14 Jul 2004 15:09:51 +0200 (CEST)
From: Johannes Meixner 
To: Olaf Meeuwissen <[...]>
Cc:  
Subject: Re: [lsm-printing] Summary of the printing summit


Hello Olaf,

[...]

I have a request for the future:

[...]

Shouldn't it be possible that Epson Kowa does a package split
into the free part and the proprietary part
and change the free part software so that it can work with
and without the proprietary modules.

Then we could add this free package to our default system.
Then we could install the free package by default.
Then the free package would work on any hardware architecture.

[...]
#

[sane-devel] Scanjet 3400C and cygwin

[Jon Chambers]

Hi,

On Tue, 13 Jun 2006, Matthias Appel wrote:
>> Possibly the niash backend is not specified in dll.conf(the configuration
>> file for the dynamic backend loader). Do you see any references to niash
>> when you do 'export SANE_DEBUG_DLL=255' and then run 'scanimage -L' again?
> I just did that and i got the following error:
> [dll] load: searching backend `nec' in `/usr/local/lib/sane'
> [dll] load: trying to load `/usr/local/lib/sane/cygsane-niash-1.dll'
> [dll] load: couldn't open `/usr/local/lib/sane/cygsane-niash-1.dll' (No such 
> file
> or directory)
> [dll] load: couldn't find backend `niash' (No such file or directory)
> I checked the directory and I only found libsane-niash.a and libsane-niash.la

That's interesting: I just had the same experience with yesterday's CVS 
snapshot (12 June), trying to test dell1600n_net on WinXP/cygwin.

The problem first shows up in some build messages which appear to come 
from libtool saying that a compatible version of phtreads could not be 
found to link dynamically and so only a static version of the backend 
would be built.  The dll backend clearly can't load this!  I will try to 
dig deeper this evening.

On a different note, when i unpacked the snapshot and just did 
"./configure && make" it failed to compile like:

coolscan.c: In function `attach_scanner':
coolscan.c:2096: warning: implicit declaration of function `strdup'
coolscan.c:2096: warning: assignment makes pointer from integer without a cast
coolscan.c: In function `reader_process':
coolscan.c:2574: warning: implicit declaration of function `fdopen'
coolscan.c:2574: warning: assignment makes pointer from integer without a cast
coolscan.c:2593: error: structure has no member named `sa_handler'
make[1]: *** [coolscan.lo] Error 1
make[1]: Leaving directory `/cygdrive/c/downloads/sane-backends/backend'
make: *** [all-recursive] Error 1

I'm not at home now so I can't tell you the exact version of gcc but it is 
whatever is the newest cygwin version.  (I updated cygwin before 
starting.)

I got around this by just compiling the backends I needed but I guess this 
should be addressed prior to the release.

cheers,
Jon

== Jon Chambers =
  http://www.jon.demon.co.uk, 020 8575 7097, 07931 961669
=

[sane-devel] Epson 3170 in Kubuntu

[Adrian Jadic]

I also had installed iscan 2.0 and I was getting the message: could not 
connect to scanner. please check..something
I the way I installed it was to convert the rpm to deb and then installed it.

metricus


On Tuesday 13 June 2006 00:54, you wrote:
> Adrian Jadic  writes:
> > I have trouble using the Epson Perfection 3170 Photo in Kubuntu 6.06
> >
> > Kooka and scanimage recognise the scanner. However when I try to scan I
> > am getting the following errors:
> > =
> > ~$ scanimage -L
> > device `epson:libusb:001:004' is a Epson  flatbed scanner
>
> This scanner is NOT supported by the epson backend.  It is also not
> supported by the plustek or snapscan backends.  If you want to use
> this scanner, you will have to use the epkowa backend together with a
> non-free binary-only plugin.  Some distributions now include this
> backend but the plugin is probably only available via:
>
>   http://www.avasys.jp/english/linux_e/index.html
>
> > ~$ scanimage
> > scanimage: sane_start: Invalid argument
> > ~$ kooka
> > libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
> > libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
> > ScimInputContextPlugin()
> > ~ScimInputContextPlugin()
> > ~$
> > =
> > This happens in both root and user.
> > Can anyone help me get further here? This scanner works fine in SUSE 9.3
> >
> > metricus
> > AMD 3000+, 1GB RAM, Kubuntu 6.06
>
> The plugin is only available for i386 ...
>
> Hope this helps,

[sane-devel] How to detect USB scanners on linux?

[Rupesh Tarpara]

Hi,

I am using Redhat AS 3, update 7. kernel string 2.4.21-40.EL.

I am developing sane backend for USB hand held image scanner.

Problem :-

When I connect the USB device and run 'sane-find-scanner' command, it does
not detect my usb scanner. It displays error message as, 'make sure usb host
controller driver is installed and kernel scanner module is loaded'.

1) The files present in /dev/usb are :-

scanner0   scanner10  scanner12  scanner14  scanner2   scanner4   scanner6
scanner8
scanner1   scanner11  scanner13  scanner15  scanner3   scanner5   scanner7
scanner9

2) the files present in /etc/hotplug are :-

blacklist  ieee1394.agent  pcipci.rc  usb.agent
usb.handmap  usb.usermap
hotplug.functions  net.agent   pci.agent  usb usb.distmap  usb.rc

3) output of lsmod is:-

Module  Size  Used byNot tainted
ide-cd 33920   0  (autoclean)
cdrom  32416   0  (autoclean) [ide-cd]
i810_audio 29784   0  (autoclean)
ac97_codec 17736   0  (autoclean) [i810_audio]
soundcore   6436   2  (autoclean) [i810_audio]
agpgart57752   6  (autoclean)
audit  89944   2  (autoclean)
usbserial  23420   0  (autoclean) (unused)
parport_pc 18756   1  (autoclean)
lp  8964   0  (autoclean)
parport36832   1  (autoclean) [parport_pc lp]
autofs416152   0  (autoclean) (unused)
e100   28264   1
mii 4516   0  [e100]
floppy 56624   0  (autoclean)
sg 36236   0  (autoclean) (unused)
scsi_mod  107180   1  (autoclean) [sg]
microcode   5688   0  (autoclean)
keybdev 2944   0  (unused)
mousedev5524   1
hid22244   0  (unused)
input   5888   0  [keybdev mousedev hid]
ehci-hcd   20008   0  (unused)
usb-uhci   25740   0  (unused)
usbcore77408   1  [usbserial hid ehci-hcd usb-uhci]
ext3   85864   2
jbd50956   2  [ext3]

===\

can anyone guide me what is wrong? Where to look for usb scanner device
file?
is it necessary to install, usb-serial port emulator driver(kernel module)
for scanner device on linux? (as usbserial module is already present)

Thanks in advance,

Rupesh Tarpara





http://www.patni.com
World-Wide Partnerships. World-Class Solutions.
_

This e-mail message may contain proprietary, confidential or legally
privileged information for the sole use of the person or entity to
whom this message was originally addressed. Any review, e-transmission
dissemination or other use of or taking of any action in reliance upon
this information by persons or entities other than the intended
recipient is prohibited. If you have received this e-mail in error
kindly delete  this e-mail from your records. If it appears that this
mail has been forwarded to you without proper authority, please notify
us immediately at netad...@patni.com and delete this mail. 
_
From till.kamppe...@gmx.net  Tue Jun 13 11:30:52 2006
From: till.kamppe...@gmx.net (Till Kamppeter)
Date: Tue Jun 13 11:31:32 2006
Subject: [sane-devel] Epson 4490 in Debian
In-Reply-To: 
References: 
<87u06rtdmt@geek.avasys.jp> 
<87r71u1sep@frigate.technologeek.org>   <873beahs1b@geek.avasys.jp> 
<873be9tv87@frigate.technologeek.org>   <87u06pfq4p@geek.avasys.jp>

Message-ID: <448ea1ec.7010...@gmx.net>

Johannes Meixner wrote:
> Hello,
> 
> On Jun 13 16:53 Olaf Meeuwissen wrote (shortened):
> 
>>Julien BLACHE  writes:
>>
>>>Ah thanks, that'll make my life easier :) The amount of work required
>>>to get the backend in shape for inclusion is one of the reasons why
>>>I'm not updating it more often
> 
> 
> Some time ago I got a nice patch from Dirk O. Siebnich
> from which I made our patch to build our iscan-free package
> which is a really free version of the epkowa backend
> (this means the /usr/bin/iscan frontend was also removed
> because it requires a non-free library).
> 
> Julien,
> I would appreciate it if the free version of Iscan would
> be as much as possible the same on Debian and on Suse
> (and on any other distribution).
> If you (or any other distribution package maintainer) are
> interested, please contact me.

I have seen it on our OpenSuSE mirror here at Mandrive. What I have done
now is suggesting to the upstream developers to make two packages, one
with the frontend and one with the backend, to be more distro-friendly.
I have no answer yet, lets see what they say.

   Till

[sane-devel] Epson 4490 in Debian

[Johannes Meixner]

Hello,

On Jun 13 16:53 Olaf Meeuwissen wrote (shortened):
> Julien BLACHE  writes:
> >
> > Ah thanks, that'll make my life easier :) The amount of work required
> > to get the backend in shape for inclusion is one of the reasons why
> > I'm not updating it more often

Some time ago I got a nice patch from Dirk O. Siebnich
from which I made our patch to build our iscan-free package
which is a really free version of the epkowa backend
(this means the /usr/bin/iscan frontend was also removed
because it requires a non-free library).

Julien,
I would appreciate it if the free version of Iscan would
be as much as possible the same on Debian and on Suse
(and on any other distribution).
If you (or any other distribution package maintainer) are
interested, please contact me.


> >> There is also a ./configure option to turn building of the frontend
> >> off to cater to non-i386 builds.
...
> I got a halfway sane patch (it ditched the frontend sources from the
> tarball :-{) and Johannes Meixner was bugging me at about the same
> time, so ...

Such a ./configure option is nice for internal testing but
it doesn't help us ("us" means at least Novell/Suse but I guess
it is the same for any distribution which provides sources)
to solve the license problem because the sources are the
crucial part regarding the license.

It doesn't help to have free binary packages built with whatever
kind of official or non-official "trick" when there is still
any kind of whatever non-free stuff left in the sources.
E.g. only mention a non-free license in some help-text in the
source even if there is actually no non-free program code
in the sources makes free sources tainted.

The only thing which makes us (same meaning as above) happy
are well seperated free sources and non-free stuff.


Olaf,
by the way:

Since the non-free model-specific stuff was split from the
Iscan sources (very many thanks for this!), I packaged
the non-free model-specific stuff into a seperated
"iscan-proprietary-drivers" RPM.

Unfortunately there seems to be no easy to use download
directory at Epson Avasys from which I could directly
download all your non-free model-specific RPMs.
At the moment I downloaded them by inspecting the docs
which models require non-free stuff and then I did
one or tow zillions of clicks in your Epson Avasys web-site
to download them :-(

Up to now I manually collected the following RPMs with non-free
model-specific stuff (from my iscan-proprietary-drivers.spec):
--
# How to get the sources:
# See the README or epkowa.desc from the iscan package which models
# require proprietary driver libraries (in epkowa.desc those models
# have "non-free" in the comment).
# Go to http://www.avasys.jp/english/linux_e/dl_scan.html
# and select each of those models and download the iscan-plugin-*
# RPM (for gcc 3.4 or later).
# At the moment this are the following models and iscan-plugin-* RPMs:
# Perfection 1250 / Perfection 1250 PHOTO / GT-7200U
Source0:  iscan-plugin-gt-7200-1.0.0-1.c2.i386.rpm
# Perfection 1260 / Perfection 1260 PHOTO / GT-7300U
Source1:  iscan-plugin-gt-7300-1.0.0-1.c2.i386.rpm
# Perfection 2480 PHOTO / Perfection 2580 PHOTO / GT-F500 / GT-F550
Source2:  iscan-plugin-gt-f500-1.0.0-1.c2.i386.rpm
# Perfection 3170 PHOTO / GT-9400UF
Source3:  iscan-plugin-gt-9400-1.0.0-1.c2.i386.rpm
# Perfection 3490 PHOTO / Perfection 3590 PHOTO / GT-F520 / GT-F570
Source4:  iscan-plugin-gt-f520-1.0.0-1.c2.i386.rpm
# Perfection 4180 PHOTO / GT-F600
Source5:  iscan-plugin-gt-f600-1.0.0-1.c2.i386.rpm
# Perfection 4490 PHOTO / GT-X750
Source6:  iscan-plugin-gt-x750-1.0.0-1.c2.i386.rpm
--
Is this list complete or did I miss something?

For example a nice tar archive which includes all the non-free
model-specific stuff would be nice.


Kind Regards
Johannes Meixner
-- 
SUSE LINUX Products GmbH, Maxfeldstrasse 5  Mail: jsm...@suse.de
90409 Nuernberg, GermanyWWW: http://www.suse.de/

[sane-devel] Scanjet 3400C and cygwin

[Matthias Appel]

>Possibly the niash backend is not specified in dll.conf(the configuration
>file for the dynamic backend loader). Do you see any references to niash
>when you do 'export SANE_DEBUG_DLL=255' and then run 'scanimage -L' again?


I just did that and i got the following error:

[dll] load: searching backend `nec' in `/usr/local/lib/sane'
[dll] load: trying to load `/usr/local/lib/sane/cygsane-niash-1.dll'
[dll] load: couldn't open `/usr/local/lib/sane/cygsane-niash-1.dll' (No such 
file
or directory)
[dll] load: couldn't find backend `niash' (No such file or directory)

I checked the directory and I only found libsane-niash.a and 
libsane-niash.la .

What can I do, to get these dll files or tell sane to use the libraries 
which where built by sane.

Regards Matthias 

[sane-devel] Epson 4490 in Debian

[Olaf Meeuwissen]

Julien BLACHE  writes:

> Olaf Meeuwissen  wrote:
>
> Hi,
>
>> I had a look at the source package since, and, yes, you did change the
>> path to /usr/lib/epkowa.  Since I've done some reorganising WRT to the
>> interpreters (libesint*.so), you may find that 2.0.0 (and the upcoming
>> 2.1.0) will be smoother sailing when packaging.  All interpreters are
>> now installed in $pkglibdir and the backend will now work both with
>> and without the interpreters installed.
>
> Ah thanks, that'll make my life easier :) The amount of work required
> to get the backend in shape for inclusion is one of the reasons why
> I'm not updating it more often (that's me being lazy wrt
> semi-proprietary stuff :p)

I won't hold that against you ;-)  After all, you're just volunteering.

>> There is also a ./configure option to turn building of the frontend
>> off to cater to non-i386 builds.  The default is to test for the
>> architecture and turn it off if non-i386, but you can override on the
>> command-line.
>
> That's nice too :)

I got a halfway sane patch (it ditched the frontend sources from the
tarball :-{) and Johannes Meixner was bugging me at about the same
time, so ...

>> I guess that for Debian that doesn't really matter much because there
>> is still a BLOB in the source tarball :-(
>> # The good news is that there only one now, instead of seven ;-)
>
> IIRC the license for the frontend isn't DFSG-free, though I'd need to
> re-read it. So it'd have to go to non-free, which isn't autobuilt
> anyway. (hmm, does the license allow for redistribution of the binary
> parts ?)

The frontend is GPL + exception.  However, same frontend won't work
without libesmod.so which is EAPL and distributed WITHOUT source.
Redistributing EAPL'd binary parts is allowed.  You may even modify
them ;-)  and reverse engineer for debugging purposes and debugging
purposes only (to meet the requirement at the top of section 6. of
the LGPL).

BTW, you want to look at non-free/EAPL.en.txt for the exact
conditions.

>> Note that iscan-2.1.0 is slated for release at approximately the same
>> schedule as the upcoming sane-backends.  If you have any questions WRT
>> packaging for libsane-extras, you know where to find me ;-)
>
> Thanks for the hint :)

You're welcome.
-- 
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 4490 in Debian

[Julien BLACHE]

Olaf Meeuwissen  wrote:

Hi,

> I had a look at the source package since, and, yes, you did change the
> path to /usr/lib/epkowa.  Since I've done some reorganising WRT to the
> interpreters (libesint*.so), you may find that 2.0.0 (and the upcoming
> 2.1.0) will be smoother sailing when packaging.  All interpreters are
> now installed in $pkglibdir and the backend will now work both with
> and without the interpreters installed.

Ah thanks, that'll make my life easier :) The amount of work required
to get the backend in shape for inclusion is one of the reasons why
I'm not updating it more often (that's me being lazy wrt
semi-proprietary stuff :p)

> There is also a ./configure option to turn building of the frontend
> off to cater to non-i386 builds.  The default is to test for the
> architecture and turn it off if non-i386, but you can override on the
> command-line.

That's nice too :)

> I guess that for Debian that doesn't really matter much because there
> is still a BLOB in the source tarball :-(
> # The good news is that there only one now, instead of seven ;-)

IIRC the license for the frontend isn't DFSG-free, though I'd need to
re-read it. So it'd have to go to non-free, which isn't autobuilt
anyway. (hmm, does the license allow for redistribution of the binary
parts ?)

> Note that iscan-2.1.0 is slated for release at approximately the same
> schedule as the upcoming sane-backends.  If you have any questions WRT
> packaging for libsane-extras, you know where to find me ;-)

Thanks for the hint :)

JB.

-- 
Julien BLACHE    
  GPG KeyID 0xF5D65169

[sane-devel] Epson 3170 in Kubuntu

[Olaf Meeuwissen]

Adrian Jadic  writes:

> I have trouble using the Epson Perfection 3170 Photo in Kubuntu 6.06
>
> Kooka and scanimage recognise the scanner. However when I try to scan I am 
> getting the following errors:
> =
> ~$ scanimage -L
> device `epson:libusb:001:004' is a Epson  flatbed scanner

This scanner is NOT supported by the epson backend.  It is also not
supported by the plustek or snapscan backends.  If you want to use
this scanner, you will have to use the epkowa backend together with a
non-free binary-only plugin.  Some distributions now include this
backend but the plugin is probably only available via:

  http://www.avasys.jp/english/linux_e/index.html

> ~$ scanimage
> scanimage: sane_start: Invalid argument
> ~$ kooka
> libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
> libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
> ScimInputContextPlugin()
> ~ScimInputContextPlugin()
> ~$
> =
> This happens in both root and user.
> Can anyone help me get further here? This scanner works fine in SUSE 9.3
>
> metricus
> AMD 3000+, 1GB RAM, Kubuntu 6.06

The plugin is only available for i386 ...

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 3170 in Kubuntu

[Adrian Jadic]

I have trouble using the Epson Perfection 3170 Photo in Kubuntu 6.06

Kooka and scanimage recognise the scanner. However when I try to scan I am 
getting the following errors:
=
~$ scanimage -L
device `epson:libusb:001:004' is a Epson  flatbed scanner
~$ scanimage
scanimage: sane_start: Invalid argument
~$ kooka
libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
ScimInputContextPlugin()
~ScimInputContextPlugin()
~$
=
This happens in both root and user.
Can anyone help me get further here? This scanner works fine in SUSE 9.3

metricus
AMD 3000+, 1GB RAM, Kubuntu 6.06