SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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
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.
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
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
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
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
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).
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.