LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-03-2007, 10:31 AM   #1
kairen
Member
 
Registered: Oct 2006
Location: Bulgaria
Distribution: Slackware64 14.1, CentOS 7
Posts: 108

Rep: Reputation: 15
Epson V200 PHOTO Scanner and Slackware 12


Hi,
I have trouble with Epson perfection V200 photo scanner. I tried to install it on Slackware 12 box but no luck.

>sane-find-scanner
>found USB scanner (vendor=0x04b8 [EPSON], product=0x012e [EPSON Scanner]) at libusb:1:3

>scanimage -L
>No scanners were identified. If you were expecting something different,check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages).


I downloaded the recommended driver from avasys website and installed it. Then added epkowa to dll.conf - as I have read in the net. The ubuntu user said that should be enough but obviously that is not enough in Slackware.

If anybody has any experience with this scanner model (or V100) I would be glad to get some sort of advise on this stuff.

Thanks in advans
 
Old 12-03-2007, 12:56 PM   #2
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
Did you add yourself to the right groups, like 'scanner'. Check '/etc/group'.
 
Old 12-03-2007, 02:49 PM   #3
fcaraballo
Member
 
Registered: Feb 2004
Location: WA
Distribution: Slackware
Posts: 230

Rep: Reputation: 31
You are most likely missing a configuration file not installed by default. Copy iscan-2.8.0/backend/epkowa.conf from the source to /etc/sane.d . You will also need to add your user to the scanner group.

MagicMan

P.S. There is a slackbuild for iscan at SlackBuilds.org. Just change the Version to 2.8.0 in the iscan.SlackBuild script.

Last edited by fcaraballo; 12-03-2007 at 02:54 PM.
 
Old 12-05-2007, 11:23 AM   #4
kairen
Member
 
Registered: Oct 2006
Location: Bulgaria
Distribution: Slackware64 14.1, CentOS 7
Posts: 108

Original Poster
Rep: Reputation: 15
I tried to scan as root. do I have to add root to scanner group as well?

there is an epkowa.conf file in /etc/sane.d and it is sort of cofigured
 
Old 12-05-2007, 12:19 PM   #5
H_TeXMeX_H
LQ Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301Reputation: 1301
root is the super user ... the member of all groups, the ruler of all things, emperor of the machine
 
Old 12-10-2007, 03:36 PM   #6
Alien_Hominid
Senior Member
 
Registered: Oct 2005
Location: Lithuania
Distribution: Hybrid
Posts: 2,247

Rep: Reputation: 53
It still should be added.
 
Old 03-17-2008, 04:19 PM   #7
Stroker
Member
 
Registered: Dec 2006
Location: The Nature Coast
Distribution: Slackware 01001101
Posts: 83

Rep: Reputation: 18
Was this ever resolved? I'm stuck at the exact same point as kairen was.

Thanks.
 
Old 03-18-2008, 06:17 AM   #8
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,371

Rep: Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750Reputation: 2750
Can you scan as the root user?
If not, then there is a problem with the installation.
If you can scan as root, but not as an ordinary user, then there is a permissions problem.
 
Old 03-19-2008, 11:09 AM   #9
dissociative
Member
 
Registered: Jul 2007
Posts: 42

Rep: Reputation: 15
I think that it's because the respective udev rules need to be updated additionally, I did that before and then got my Epson scanner working flawlessly but I can't remember how.
 
Old 03-19-2008, 09:39 PM   #10
Stroker
Member
 
Registered: Dec 2006
Location: The Nature Coast
Distribution: Slackware 01001101
Posts: 83

Rep: Reputation: 18
Quote:
Originally Posted by dissociative View Post
I think that it's because the respective udev rules need to be updated additionally, I did that before and then got my Epson scanner working flawlessly but I can't remember how.
Thank you for the replies allend and dissociative.

root doesn't help. I added udev rules when I installed it.

Today I resorted to trying it on a MS box ((hangs head in shame)) to avoid wasting time if the scanner was defective.

I've made some progress, but it's not there yet. I'll let y'all know the solution when(if) I find it.
 
Old 03-27-2008, 04:18 PM   #11
Stroker
Member
 
Registered: Dec 2006
Location: The Nature Coast
Distribution: Slackware 01001101
Posts: 83

Rep: Reputation: 18
Thumbs up Epson V200 SOLVED -

Epson V200 SOLVED -

THE SHORT ANSWER

The two available iscan SlackBuilds will not get the job done for an Epson V200 on a 2.6.x system.

You must use the Epson Avasys Iscan Utility WITH the Epson Avasys Iscan plugin for the V200 (GT-F670 model plugin which is the Non-US version of the V200).

iscan-2.8.0-1.c2.i386.rpm
iscan-plugin-gt-f670-2.0.0-1.c2.i386.rpm

Available at
http://www.avasys.jp/lx-bin2/linux_e/scan/DL1.do

SlackBuild.org has a script for the Iscan Utility but nothing for the complete plugin.

Here is my SlackBuild (it's slackbuild.README explains the plugin): iscan+plugin_2.25.0-1.tgz

EDIT: Buildscript updated Sept 11 2010 for Iscan v2.25-1

NOTE: parts of this post have become obsolete!!



If you want the details keep reading.
_________________________________________________

THE LONG ANSWER

PITFALLS OF A NOOB

I made some bad assumptions, some bad choices, and even hosed my OS at one point, but I finally got the V200 working.

So, Epson Avasys makes available four files to download regarding the V200 scanner; 2 RPM's, Source Code, User Guide:

iscan-2.8.0-1.c2.i386.rpm
iscan-plugin-gt-f670-2.0.0-1.c2.i386.rpm
iscan-2.8.0-1.c2.tar.gz
userg_revG_e.pdf


SlackBuild.org offers:

iscan.SlackBuild
iscan-firmware.SlackBuild

iscan.SlackBuild compiles from the source code and says:

"Image Scan! for Linux" is a scanner utility that makes
it easy to obtain high quality images on Linux with your
EPSON scanner or all-in-one.

Cool, so this is all I need right? (Mistake number one. I should have read the source code README)

Installing the package from that build resulted in no scanner operation.

So, I must need the iscan-firmware.SlackBuild right? (I must have taken a stupid pill that morning)

The iscan-firmware.SlackBuild tells me that my scanner will work with the FOSS Snapscan backend that comes with Sane; all I need is the firmware for my scanner. It even lists specific instruction to configure Snapscan for the V200 scanner. Great, open source is a beautiful thang, lets just use that.

The iscan-firmware.SlackBuild just repacks an OpenSUSE Package which contains Epson Avasys iscan plugins for all of the available scanner models. I only need one so I'll just drop the firmware into the proper directory, tell Snapscan to use it, all done right?

Trying to make the Snapscan backend work with my V200 is where I really started getting my butt kicked. Essentially, Sane was telling me it did not recognize the scanners USB chip. I was running down one dark alley and dead end after another. Finally I decide, maybe this scanner is just broken. So I hook it up to a friends Vista box and it runs like a pickle seeder.

So, maybe this Snapscan backend just won't work. I go the Snapscan site and the last update listed is 11/27/05. Hummm.

Then I find this tidbit on the Snapscan site:

_____________________________________________

http://snapscan.sourceforge.net/#usb

You can also upload the firmware to your scanner manually.
You need to launch one of agfafirm or acerfirm perl scripts:

acerfirm /dev/usbscanner u34v101.bin

Note: acerfirm and agfafirm will only work if you use the
scanner module to access your USB scanner. It does not work
with libusb.

_____________________________________________

Perhaps this is why Snapscan would not work with my 2.6.x
kernel as there is no scanner module for it. 2.6.x kernels
only use libusb. The Snapscan site does not elaborate as to
whether their backend also requires the module to upload the
firmware. I didn't bother looking at the code so this is all just speculation on my part. All I can say for sure is the Snapscan backend for Sane would not work for the V200 on my system.

The Sane backend database also does NOT list the V200 for use with the Snapscan backend. For the V200 it lists only iscan and it's required plugin.

Drop back and punt. I explode the Avasys and OpenSUSE packages to see what goes where and compare it to my install.

Everything looks good, except for one little problem. The OpenSUSE package used by the iscan-firmware.SlackBuild only has half of the plugin. What!?! Yup, OpenSUSE gathers all of the Epson Avasys plugins for the different model scanners and SPLITS THEM INTO TWO SEPARATE PACKAGES:

iscan-firmware
iscan-proprietary-drivers

To put an end to this long sad story. As far as I can tell the Snapscan backend will not work with V200 Scanner (at least with a 2.6 kernel). Thus the iscan-firmware.SlackBuild is of no use for the V200.

You must use the Epson Avasys Iscan Utility with the GT-F670 iscan plugin.

Technically, you don't need all of the Iscan package. You need the epkowa Sane backend from the Iscan package and the plugin (both are binary only). But the Iscan package has a nice frontend and I would recommend it. Besides, the frontend is open source anyway.

You could use the iscan.SlackBuild but there is nothing available to make a slackpackage for the complete GT-F670 iscan plugin. So, that really doesn't help.

Using rpm2tgz on the Epson Avasys Packages doesn't get the job done. It's close, but there are some rpm scripts that do not get run, so it still needs some manual labor. Mostly udev rules and gimp plug. If you know how to write udev rules and make links you can go that route if you'd like.

I ended up writing a new SlackBuild that will repack iscan and the plugin RPM's into one Slackpackage. It should repack as many plugins as you include (but that is untested). It generates an iscan udev rules file and The Gimp plugin.

There is a link to my SlackBuild at the top of this post.

THE END


Robby,

In my n00b opinion, template.SlackBuild at Line 63 needs:
-o -perm 700

When repacking RPM's cpio seems to use 0700 a lot and it will really foobar a persons system if it is missed. Yeah, like I said I'm a n00b. It really pisses off X when you tell it not to play in /etc or /usr. X has no sense of humor at all. CLI just gets stupid. You can login (as a user) but that's about it. It was a great learning experience at least.

You're welcome to use my SlackBuild if you think it's worthy of SlackBuild.org

Last edited by Stroker; 09-11-2010 at 02:41 PM.
 
Old 04-14-2008, 06:26 AM   #12
kairen
Member
 
Registered: Oct 2006
Location: Bulgaria
Distribution: Slackware64 14.1, CentOS 7
Posts: 108

Original Poster
Rep: Reputation: 15
Thank you.

Hi again,

I just want to say THANK YOU to Stroker.
His instruction worked fine for me on Slackware 11 and Fedora 8.

on Fedora just installed the rpm's, typed iscan and that is all.

on Slackware I used Stroker's slackbuild script and it all went nice and easy.

Again Thanks a lot buddy for sharing your success.

Kairen
 
Old 04-14-2008, 01:38 PM   #13
Stroker
Member
 
Registered: Dec 2006
Location: The Nature Coast
Distribution: Slackware 01001101
Posts: 83

Rep: Reputation: 18
Kairen,

You're welcome. I'm glad it helped you.


-------------------------

rworkman,

Did you miss the note to you at the very end of my 'SOLVED' post?

Or perhaps it was just not worthy of a reply.
 
Old 09-07-2008, 04:55 AM   #14
brixtoncalling
Member
 
Registered: Jul 2008
Location: British Columbia
Distribution: Slackware current
Posts: 403

Rep: Reputation: 67
Thanks. Worked great on 12.1 with a Epson Stylus DX4450.
 
Old 05-27-2009, 11:57 PM   #15
kernel-P4N1C
Member
 
Registered: Nov 2007
Location: Panama city, Republic of Panmaa
Posts: 167

Rep: Reputation: 18
Hello

I'm trying to set up a TX100 printer/scanner with no luck at all...

this is what i get..
Code:
root@weput:/etc/sane.d# iscan
iscan: error while loading shared libraries: libesmod.so.2: cannot open shared object file: No such file or directory
attempt to look for the li9besmod.so and didn't find a thing... (missing too for the pips)
 
  


Reply

Tags
epson



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
EPSON PERFECTION 3170 PHOTO SCANNER on FC1 cjagdish69 Fedora 1 11-03-2007 11:27 PM
Epson Prefection 3170 Photo scanner in RHEL 3/4 cjagdish69 Linux - Hardware 1 08-13-2007 03:34 AM
USB Scanner (Epson perfection 2480 photo) littletaff Linux - Hardware 0 03-09-2006 11:10 AM
Epson stylus photo RX425 scanner not found pag Mandriva 1 08-10-2005 03:17 AM
Epson Perfection 3170 Photo Scanner !? FreakboY Linux - Hardware 0 06-13-2004 10:47 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:27 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration