[sane-devel] Epson Perfection 3490 PHOTO

2005-12-27 Thread Henning Meier-Geinitz
Hi,

On Sat, Dec 24, 2005 at 07:07:28PM -0600, Trevor Cordes wrote:
 On Sun, Dec 18, 2005 at 03:18:05PM +0100, Henning Meier-Geinitz wrote:
  
   5. *** THE BIG PAIN *** I'm not sure if anyone knows why this happened: It
   might be FC3 specific.  The problem was something in the system (I still
   don't know what) makes a symlink from /usr/local/lib/sane/libsane.so.1 -
   libsane-v4l.so.1.0.16.  That's totally bogus.  If I rm the symlink it just
  
  IIRC this is caused by the libtool --finish call in backend/Makefile.
  In CVS there is a workaround that removes these links. At least it
  should...
 
 I was using the latest CVS from Dec 17 and it still did it.

It does not happen here. Maybe it's caused by running ldconfig when
/usr/local/lib/sane is in ld.so.conf? This would be quite logical as
the name of all SANE backends is libsane.so internally and the V4L
backend just happens to be the last one in the alphabet.

 My system was FC1 upgraded to 2 upgraded to 3 (actually, I may have 
 started with RH9!)... the entry must have been around from way back when.  
 I have deleted the line.  At least now this change is documented in 
 something that may show up in a google search.

I'll also mention it somewhere in the SANE readme or other
documentation.

This mistake was common about five years ago but I haven't heard about
it recenetly.

Bye,
  Henning


[sane-devel] Epson Perfection 3490 PHOTO

2005-12-25 Thread Trevor Cordes
n Sun, Dec 18, 2005 at 03:04:06PM +0100, Oliver Schwartz wrote:
 
  1. Someone should change the sane compatibility list to show that
  it does NOT work as of sane-backends-1.0.16.  It should be noted
  you need CVS or .17 once it's released.
 
 Where did you get the information that it does work with 
 sane-backends-1.0.16? The device list for 1.0.16 doesn't list the 
 3490, as far as I can see. It only shows up in the CVS list. The 
 Snapscan homepage on http://snapscan.sf.net also mentions that you 
 need at least 1.0.16-CVS.

Oops, you're right.  It was the snapscan chart that I was talking about 
and it does indeed say 1.0.16-CVS.  However, that labelling system *was* 
confusing to me and I think my brain just read it as get .16 or newer 
instead of get newer than .16.  I'm an experience unix user and I messed 
that up... my post was more for the noobs seeing this in the future to not 
have the headaches I did.

 Most of your other points are FC3 related, as far as I can tell. It 
 may be a good idea to post these issues on a FC3 mailing list.

OK.  FC5 will probably have .17 anyways so it's not a big whoop.

Thanks.


[sane-devel] Epson Perfection 3490 PHOTO

2005-12-25 Thread Trevor Cordes
On Sun, Dec 18, 2005 at 03:18:05PM +0100, Henning Meier-Geinitz wrote:
 
  5. *** THE BIG PAIN *** I'm not sure if anyone knows why this happened: It
  might be FC3 specific.  The problem was something in the system (I still
  don't know what) makes a symlink from /usr/local/lib/sane/libsane.so.1 -
  libsane-v4l.so.1.0.16.  That's totally bogus.  If I rm the symlink it just
 
 IIRC this is caused by the libtool --finish call in backend/Makefile.
 In CVS there is a workaround that removes these links. At least it
 should...

I was using the latest CVS from Dec 17 and it still did it.

 /usr/local/lib/sane should NEVER be listed in /etc/ld.so.conf. This
 has been obsolete for five (?) years now. Don't do that. If your
 distribution does that, tell the maintainers to stop it immediately.

My system was FC1 upgraded to 2 upgraded to 3 (actually, I may have 
started with RH9!)... the entry must have been around from way back when.  
I have deleted the line.  At least now this change is documented in 
something that may show up in a google search.

Thanks.


[sane-devel] Epson Perfection 3490 PHOTO

2005-12-18 Thread Trevor Cordes
Hi, I'm new to the list.  I just bought an Epson 3490 as it looked 
possible to make it work with linux and it got good reviews.

It's working now, but with 3 hours of fighting...

Help for other people trying this in the future:

0. A good site that helped me is:
http://www.michaelminn.com/index.php?linux/peripherals.html

1. Someone should change the sane compatibility list to show that it does 
NOT work as of sane-backends-1.0.16.  It should be noted you need CVS or 
.17 once it's released.

2. It's quite a bit of work for a FC3 user: must rpm -e sane-backends, 
sane-frontends, xsane and xsane-gimp and then compile/install yourself the 
first 3 packages from CVS source.

3. Must manually move the 2 hotplug files from sane-be source to 
/etc/hotplug trees.

4. Must get the firmware file from a Windows install of the scanner and 
put it somewhere in linux and change snapscan.conf to point to it.  File 
is esfw52.bin in C:\WINDOWS\SYSTEM32

5. *** THE BIG PAIN *** I'm not sure if anyone knows why this happened: It
might be FC3 specific.  The problem was something in the system (I still
don't know what) makes a symlink from /usr/local/lib/sane/libsane.so.1 -
libsane-v4l.so.1.0.16.  That's totally bogus.  If I rm the symlink it just
instantly pops back into existence!!  Weird!  This wouldn't have been a
problem, but my /etc/ld.so.conf had /usr/local/lib/sane listed BEFORE
/usr/local/lib and so this bogus libsane.so was being used instead of the
real one in /usr/local/lib!  Reversing the order in ld.so.conf solved the
problem.  Scanner works great now.

If anyone knows WTF is up with #5, let me know.

The scanner scans quick and looks good.  I did a test at 600 dpi and it 
looks fine.  Someone else reported it looked pixelated?  Please email me 
if this appears to still occur as I want to make sure my scans are 
perfect.  I haven't tried the TPU yet as I don't really need that feature.

I'm willing to run whatever tests the devs may want and report back if 
that would help.  Thanks to all the coders for their fine work.


[sane-devel] Epson Perfection 3490 PHOTO

2005-12-18 Thread Oliver Schwartz
Hi,

 1. Someone should change the sane compatibility list to show that
 it does NOT work as of sane-backends-1.0.16.  It should be noted
 you need CVS or .17 once it's released.

Where did you get the information that it does work with 
sane-backends-1.0.16? The device list for 1.0.16 doesn't list the 
3490, as far as I can see. It only shows up in the CVS list. The 
Snapscan homepage on http://snapscan.sf.net also mentions that you 
need at least 1.0.16-CVS.

Most of your other points are FC3 related, as far as I can tell. It 
may be a good idea to post these issues on a FC3 mailing list.

/Oliver


[sane-devel] Epson Perfection 3490 PHOTO

2005-12-18 Thread Henning Meier-Geinitz
Hi,

On Sun, Dec 18, 2005 at 06:42:58AM -0600, Trevor Cordes wrote:
 Hi, I'm new to the list.  I just bought an Epson 3490 as it looked 
 possible to make it work with linux and it got good reviews.

In addition to what Oliver wrote:

 5. *** THE BIG PAIN *** I'm not sure if anyone knows why this happened: It
 might be FC3 specific.  The problem was something in the system (I still
 don't know what) makes a symlink from /usr/local/lib/sane/libsane.so.1 -
 libsane-v4l.so.1.0.16.  That's totally bogus.  If I rm the symlink it just

IIRC this is caused by the libtool --finish call in backend/Makefile.
In CVS there is a workaround that removes these links. At least it
should...

 instantly pops back into existence!!  Weird!  This wouldn't have been a
 problem, but my /etc/ld.so.conf had /usr/local/lib/sane listed BEFORE

/usr/local/lib/sane should NEVER be listed in /etc/ld.so.conf. This
has been obsolete for five (?) years now. Don't do that. If your
distribution does that, tell the maintainers to stop it immediately.

/usr/local/lib/ may be necessary, however.

 /usr/local/lib and so this bogus libsane.so was being used instead of the
 real one in /usr/local/lib!  Reversing the order in ld.so.conf solved the
 problem.  Scanner works great now.

Just remove the entry from ld.so.conf.

Bye,
  henning


[sane-devel] Epson Perfection 3490 PHOTO

2005-08-22 Thread Bjorn Solberg
Bjorn Solberg writes:

 Oliver Schwartz writes:
 Hi,
 I found the driver in c:/WINDOWS/system32/esfw52.bin, copied it to
 /etc/sane.d and modified the firmware entry in snapscan.conf, and
 now it works even after rebooting both the scanner and the
 computer.

 Very good. Can you do some tests, e.g. do all resolutions work? Does 
 the transparency unit work?

 There seems to be something odd about the geometry calculations for the
 driver.  I.e. when I try to scan a full page, whether I specify the full
 -x and -y or simply say scanimage, it only gets the first 16.5cm for the
 width and 22cm for the length rather than the full 21.5cm x 27.5cm (US
 letter size).  In Windows it correctly scans the whole page though.

[That being with the Windows software that came with the scanner, of
course.]

Do you think this is a problem that is related to the firmware, to how
SANE talks to the firmware or just with SANE itself?  Just so I have a
better idea to start looking into this myself - I'd like to have the
issue resolved one way or the other before the time is up for returning
the scanner...

Thank you,

Bjorn.


[sane-devel] Epson Perfection 3490 PHOTO

2005-08-18 Thread Bjorn Solberg
Oliver Schwartz writes:

 Hi,
 I found the driver in c:/WINDOWS/system32/esfw52.bin, copied it to
 /etc/sane.d and modified the firmware entry in snapscan.conf, and
 now it works even after rebooting both the scanner and the
 computer.

 Very good. Can you do some tests, e.g. do all resolutions work? Does 
 the transparency unit work?

There seems to be something odd about the geometry calculations for the
driver.  I.e. when I try to scan a full page, whether I specify the full
-x and -y or simply say scanimage, it only gets the first 16.5cm for the
width and 22cm for the length rather than the full 21.5cm x 27.5cm (US
letter size).  In Windows it correctly scans the whole page though.

It wouldn't take 3200 resolution, instead giving the message scanimage:
rounded value of resolution from 3200 to 2400 and then giving a
scanimage: sane_start: Error during device I/O message.  Unplugging and
replugging the USB cable was required to do another scan after that.
2400 only gives the scanimage: sane_start: Error during device I/O
message and it hangs for a while again.  The next step down is 1200 which
works fine, albeit slow.

I haven't tried the transparency unit yet.

The most critical issue thus seems to be that the driver doesn't copy the
whole page.  Is this something that's easy to fix, is there any way I
can help out?

Thank you,

Bjorn.


[sane-devel] Epson Perfection 3490 PHOTO

2005-08-16 Thread Olaf Meeuwissen
Oliver Schwartz oliver.schwa...@gmx.de writes:

 Hi,

 the code is in CVS now. Please try it and let me know if it works for 
 you.

 I currently don't have any information on the firmware filename. 
 Usually there is only one supplied with the windows driver. Look for 
 any *.bin file in the twain32 directory.

esfw51.bin, IIRC.
-- 
Olaf Meeuwissen
FSF Associate Member #1962   sign up at http://member.fsf.org/
GnuPG key: 30EF893A/2774 815B DE83 06C8 D733  6B5B 033C C857 30EF 893A
Penguin's lib!   -- I hack, therefore I am --   LPIC-2



[sane-devel] Epson Perfection 3490 PHOTO

2005-08-16 Thread Bjorn Solberg
Olaf Meeuwissen writes:

 Oliver Schwartz oliver.schwa...@gmx.de writes:
 Hi,
 
 the code is in CVS now. Please try it and let me know if it works for 
 you.
 
 I currently don't have any information on the firmware filename. 
 Usually there is only one supplied with the windows driver. Look for 
 any *.bin file in the twain32 directory.

 esfw51.bin, IIRC.

Does all this mean that I need to load some firmware onto the scanner
before I can use it, or should it work out-of-the-box with the snapscan
backend?

I'll try the CVS code a little later.

Bjorn.


[sane-devel] Epson Perfection 3490 PHOTO

2005-08-16 Thread Oliver Schwartz
Hi,

 Does all this mean that I need to load some firmware onto the
 scanner before I can use it, or should it work out-of-the-box with
 the snapscan backend?

Yes and no. The backend will download the firmware to the scanner 
automatically (as does the windows driver). See 
http://snapscan.sourceforge.net for more information.

The firmware is only loaded into the internal RAM of the scanner. Once 
you switch off the scanner it is restored to it's original state.

/Oliver



[sane-devel] Epson Perfection 3490 PHOTO

2005-08-16 Thread Bjorn Solberg
Oliver Schwartz writes:

 Hi,
 Does all this mean that I need to load some firmware onto the
 scanner before I can use it, or should it work out-of-the-box with
 the snapscan backend?

 Yes and no. The backend will download the firmware to the scanner 
 automatically (as does the windows driver). See 
 http://snapscan.sourceforge.net for more information.

 The firmware is only loaded into the internal RAM of the scanner. Once 
 you switch off the scanner it is restored to it's original state.

I see.  It looks like I had to install the driver under Windows, then.
Did a test scan in Windows and it worked.  Then rebooted to Linux, and
scanimage -L found

device `snapscan:libusb:001:003' is a EPSON EPSON Scanner1 flatbed scanner

and scanimage ran just fine, both the RPM version and the CVS version
from 20050815.

I found the driver in c:/WINDOWS/system32/esfw52.bin, copied it to
/etc/sane.d and modified the firmware entry in snapscan.conf, and now it
works even after rebooting both the scanner and the computer.

Thank you Olaf and Oliver for the help,

Bjorn.


[sane-devel] Epson Perfection 3490 PHOTO

2005-08-16 Thread Oliver Schwartz
Hi,

 I found the driver in c:/WINDOWS/system32/esfw52.bin, copied it to
 /etc/sane.d and modified the firmware entry in snapscan.conf, and
 now it works even after rebooting both the scanner and the
 computer.

Very good. Can you do some tests, e.g. do all resolutions work? Does 
the transparency unit work?

Happy scanning,

Oliver



[sane-devel] Epson Perfection 3490 PHOTO

2005-08-15 Thread Oliver Schwartz
Hi,

the code is in CVS now. Please try it and let me know if it works for 
you.

I currently don't have any information on the firmware filename. 
Usually there is only one supplied with the windows driver. Look for 
any *.bin file in the twain32 directory.

/Oliver



[sane-devel] Epson Perfection 3490 PHOTO

2005-08-10 Thread Bjorn Solberg
I recently got the Epson Perfection 3490 PHOTO scanner.  It's connected
through USB to my computer running Fedora Core 3, my SANE versions are

# rpm -q -a | grep -i sane
xsane-0.92-13
xsane-gimp-0.92-13
sane-frontends-1.0.12-4
sane-backends-1.0.15-1.4

sane-find-scanner finds the scanner at libusb:001:003, but scanimage -L
just returns without finding anything (No scanners were
identified.[...]).  

I added

usb 0x04b8 0x0122

to /etc/sane.d/epson.conf, which made scanimage -L take longer ( 10
seconds) to return the same answer (No scanners were identified).

Does anyone else have any experience with this scanner, and/or can tell
me whether it is (or will be in the near future) supported by SANE?  Any
pointers on how I can make it work with SANE is much appreciated.

Thank you,

Bjorn.


[sane-devel] Epson Perfection 3490 PHOTO

2005-08-10 Thread Oliver Schwartz
Hi,

 I recently got the Epson Perfection 3490 PHOTO scanner.  

 Does anyone else have any experience with this scanner, and/or can
 tell me whether it is (or will be in the near future) supported by
 SANE?  Any pointers on how I can make it work with SANE is much
 appreciated.

I got some infos and a patch concerning this scanner. I'll add support 
for it to the snapscan backend in the next few days. I'll let you 
know if the code is in CVS, so you can test it.

/Oliver