LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 03-08-2018, 09:31 AM   #16
lecho
Member
 
Registered: Jan 2013
Location: Warsaw, Poland
Distribution: Slackware
Posts: 32

Rep: Reputation: Disabled

The name is "conf",
Code:
-rwxr-xr-x 1 root root 7 Dec 17  2013 conf
This file appeared as a result of running a POSTIN script from
Code:
iscan-2.29.3-1.usb0.1.ltdl7.x86_64.rpm
(most probably, it was 4 years ago).
 
Old 03-08-2018, 09:47 AM   #17
vonbiber
Member
 
Registered: Apr 2009
Distribution: slackware 14.1 64-bit, slackware 14.2 64-bit, SystemRescueCD
Posts: 533

Original Poster
Rep: Reputation: 129Reputation: 129
Quote:
Originally Posted by lecho View Post
The name is "conf",
ok, I ran this
Code:
# echo epkowa > /etc/sane.d/dll.d/conf
I'm gonna turn off the computer and check later, and maybe look more closely
at the files in the RPM archive
 
Old 03-08-2018, 09:57 AM   #18
lecho
Member
 
Registered: Jan 2013
Location: Warsaw, Poland
Distribution: Slackware
Posts: 32

Rep: Reputation: Disabled
BTW, have you converted rpms using rpm2tgz or a similar program? I had problems 4 years ago because at that time I didn't know options "-S" or at least "-s" dealing with postinstallation scripts from rpm.
As fido_dogstoyevsky wrote in his post in this thread
Quote:
NOTE the txz files were converted from rpm files using rpm2txz -c -S -n -d
 
Old 03-08-2018, 01:28 PM   #19
vonbiber
Member
 
Registered: Apr 2009
Distribution: slackware 14.1 64-bit, slackware 14.2 64-bit, SystemRescueCD
Posts: 533

Original Poster
Rep: Reputation: 129Reputation: 129
Quote:
Originally Posted by lecho View Post
BTW, have you converted rpms using rpm2tgz or a similar program? I had problems 4 years ago because at that time I didn't know options "-S" or at least "-s" dealing with postinstallation scripts from rpm.
No, I did this
Code:
mkdir tmp; cd tmp
tar xf ../iscan-perfection-v370-bundle-1.0.1.x64.rpm.tar.gz
mv iscan-perfection-v370-bundle-1.0.1.x64.rpm/* .
rmdir iscan-perfection-v370-bundle
rm install.sh README.rst
for d in core data plugins
do
  mv $d/*.* .
  rmdir $d
done
mv *.rpm ..; cd ..; rmdir tmp
Then for each RPM I wrote a SlackBuild. In each SlackBuild I used this
Code:
rpm2cpio $CWD/$archive | \
     cpio -i --make-directories --no-absolute-filenames
I moved some files around ...

I just looked at the debian bundle archive.
It has some files that are not in the RPM.
For instance, it has this file
Code:
etc/sane.d/dll.d/iscan
that contains this
Code:
# iscan -- enables the SANE backend(s) required
# Any changes to this file will be lost when upgrading iscan.

epkowa

Last edited by vonbiber; 03-08-2018 at 01:29 PM. Reason: typo
 
Old 03-13-2018, 06:08 AM   #20
vonbiber
Member
 
Registered: Apr 2009
Distribution: slackware 14.1 64-bit, slackware 14.2 64-bit, SystemRescueCD
Posts: 533

Original Poster
Rep: Reputation: 129Reputation: 129
Quote:
Originally Posted by vonbiber View Post
But now I got another issue:
Code:
Makefile:388: recipe for target 'all-recursive' failed
make[2]: *** No rule to make target '../non-free/libesmod.so', needed by 'iscan'.  Stop.
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
Well, I've been able to figure out this one.
Now I can build iscan from source and it's a more
recent version than the one in the binary distribution.
I doubt this will fix the issue but I'll try to install this instead
and I'll make a recap of what I've done later.
 
Old 03-23-2018, 08:22 AM   #21
vonbiber
Member
 
Registered: Apr 2009
Distribution: slackware 14.1 64-bit, slackware 14.2 64-bit, SystemRescueCD
Posts: 533

Original Poster
Rep: Reputation: 129Reputation: 129
I installed devuan (it's a fork of debian without systemd) as a VirtualBox guest
and installed the 3 deb packages, rebooted and it's working.
I noticed that in their iscan.rules they set the group ownership to scanner
Code:
ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m g:scanner:rw $env{DEVNAME}"
and I didn't notice an entry in their libsane.rules for this product (014a)
whereas my slackware libsane.rules does have an entry for it but sets the group to lp
Also, when the scanner is plugged-in and turned on when I check the appropriate device
in /dev/bus/usb
in slackware it's set to root:lp
but in devuan it's set to root:root
Unfortunately I wasn't able to install the guest additions to devuan, so right
now there's no possibility of retrieving the scanned files through a shared folder.
So, I guess, until I'll figure out how to install to slackware, I'll email them or
post them in a web server

Last edited by vonbiber; 03-23-2018 at 08:22 AM. Reason: typo
 
Old 03-28-2018, 01:17 PM   #22
vonbiber
Member
 
Registered: Apr 2009
Distribution: slackware 14.1 64-bit, slackware 14.2 64-bit, SystemRescueCD
Posts: 533

Original Poster
Rep: Reputation: 129Reputation: 129
I installed centos as a VBox guest. Now I can scan and retrieve the scanned files.
I don't know why it doesn't work in slackware. I pretty much set the same kind of configs
(/etc/sane.d/epkowa.conf /etc/sane.d/dll.conf and /var/lib/iscan/interpreter), the permissions
look ok (lp group).
I give up for the time being and use the centos guest when I need to scan
 
Old 10-28-2018, 07:54 AM   #23
przemo
Member
 
Registered: Feb 2016
Location: cork.ie
Distribution: Slackware-current
Posts: 162

Rep: Reputation: Disabled
i got it running by adding epkowa to dll.conf and editing epkowa.conf
Code:
interpreter usb 0x04b8 0x014a /usr/lib64/iscan/libiscan-plugin-perfection-v370
 
1 members found this post helpful.
Old 10-29-2018, 06:18 AM   #24
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 973

Rep: Reputation: 238Reputation: 238Reputation: 238
Quote:
Originally Posted by przemo View Post
i got it running by ... editing epkowa.conf
Fab, I had problems with the Epson V330 on current using the 14.2 install described here.

Following the above described order (first install data, then iscan then plugin) and - instead of only "usb 0x04b8 0x0142" - having "interpreter usb 0x04b8 0x0142 /usr/lib64/esci/libesci-interpreter-perfection-v330" in /etc/sane.d/epkowa.conf this scanner is recognized by my linux box again ;-)

EDIT: I tried the set-up described by Toutatis below as well, but that did not make the V330 work at my end

Last edited by brobr; 10-30-2018 at 07:29 AM.
 
Old 10-29-2018, 08:10 AM   #25
Toutatis
Member
 
Registered: Feb 2013
Posts: 411

Rep: Reputation: Disabled
I have a epson V370 photo that works perfectly with slackware64-current.

In dll.conf I have (among other things) :
epson
#epson2
epkowa

in epkowa.conf :
usb
scsi

in epson.conf :
usb 0x04b8 0x014a

/var/lib/iscan/interpreter contains :
interpreter usb 0x04b8 0x014a /usr/lib64/iscan/libiscan-plugin-perfection-v370 /usr/share/isca/esfwdd.bin
 
Old 11-02-2018, 04:18 AM   #26
przemo
Member
 
Registered: Feb 2016
Location: cork.ie
Distribution: Slackware-current
Posts: 162

Rep: Reputation: Disabled
what iscan packages you have installed???

i do not have /var/lib/iscan/interpreter file

it does not work for me on current now on 14.2 was ok

Code:
 ls /var/log/packages | grep iscan
iscan-2.30.1-x86_64-1alien
iscan-data-1.36.0-x86_64-1alien
iscan-plugin-perfection-v370-1.0.0-2.x86_64
from xsane i am getting
failed to start scanner: invalid argument

Last edited by przemo; 11-02-2018 at 04:36 AM.
 
Old 11-02-2018, 10:49 AM   #27
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 973

Rep: Reputation: 238Reputation: 238Reputation: 238
The packages of Alien for current/iscan are from July 2015. Since, there have been a lot of changes in current, which might explain the problem. You might have some luck by compiling it yourself. You could try Aliens build-scripts or those from the website mentioned on my previous post for the V330 (but make sure that all V330-specific stuff is corrected for the V370).

hth

rob
 
Old 11-02-2018, 12:05 PM   #28
przemo
Member
 
Registered: Feb 2016
Location: cork.ie
Distribution: Slackware-current
Posts: 162

Rep: Reputation: Disabled
i did no luck, is it the same packages you have???


packages in epson iscan bundle are from 2015 to

Last edited by przemo; 11-02-2018 at 12:25 PM.
 
Old 11-03-2018, 01:27 PM   #29
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 973

Rep: Reputation: 238Reputation: 238Reputation: 238
Well, on current iscan stopped working for me last year. I had used the slackbuilds by Simone Giustetti. Comparing the slackbuild for iscan that one can download from his website for Iscan_and_Slackware_14.2 and the one I used just the other day shows that you might need an extra patch from archlinux. Inserted just after the "# Change user permission" section ending in "-exec chmod 644 {} \;" is:
Code:
# From https://git.archlinux.org/svntogit/community.git/tree/trunk?h=packages/iscan
 patch -p0 -i ${SRCDIR}/jpegstream.cc.patch
Then, check the usb_id.patch for the iscan-data package. This needs the code for the V370. Changing the line for the V330 "+ usb 0x04b8 0x0142" to "+ usb 0x04b8 0x014a" should do the job. As mentioned above and on the site I compiled and installed this package before compiling iscan itself, and then at last the plugin.

For the plugin you need to adapt the slackbuild for the v370. The rpm file to use for the build is another rpm that comes in the plugin-folder inside the V370 "All-in-one package" distribution-rpm (not the source, as this lacks the plugins) from the epson site.

Further the adaptations to /etc/sane.dl etc. as mentioned, but should be in place when working through the advice given on giustetti.net.

Then you might need to follow your own advice above as this made it work for me. Don't ask me why. It's been a continuous struggle with epson-ware at my end.

hth

Last edited by brobr; 11-03-2018 at 01:29 PM.
 
Old 11-04-2018, 01:40 AM   #30
Toutatis
Member
 
Registered: Feb 2013
Posts: 411

Rep: Reputation: Disabled
@przemo

The file /var/lib/iscan/interpreter seems to be created by the command iscan registry
https://manned.org/iscan-registry/95af4de7

I don't remember if dit run it or if this was done automatically. I did not use alienbob's packages, but the epson rpm in http://download.ebz.epson.net/dsc/du...23b746b0ae2360
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
problem with scanner Epson perfection v370 Toutatis Slackware 6 11-20-2015 09:53 PM
[SOLVED] Epson Perfection 350 Scanner driver will not recognize the scanner Mikech Linux - Hardware 4 10-25-2012 12:09 PM
[SOLVED] Epson Perfection 1270 Scanner Lexus45 Linux - Hardware 2 09-04-2011 11:35 PM
epson perfection 3490 scanner mtb Linux - Hardware 2 11-16-2005 02:13 PM
epson perfection 636 scanner... vance Linux - Hardware 1 12-15-2002 11:15 AM

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

All times are GMT -5. The time now is 02:16 PM.

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