Hello all,
I can't scan to my Epson WF-2540 printer/scanner. About 1 nanosecond after running skanlite a dialog box comes up saying no devices were found. Of course it prints fine. This printer is shown as compatible for both printing and scanning on the Linux Foundation site (where I got the driver for it).
I have tried this so far:
- turned off firewalld
- ran tcpdump between the computer and printer, then ran skanlite again. There is no indication that there was ever any communication between them.
- ran skanlite with strace. Lot's of output (duh) but no smoking gun that I could see.
My old Fedora 14 system can find the scanner just fine, and you can see the network traffic pretty clearly. If anyone has any ideas I would sure like to hear them.
Jim Lewis
On 14.12.2014 04:46, Jim Lewis wrote:
Hello all,
I can't scan to my Epson WF-2540 printer/scanner.
http://www.epson.com/cgi-bin/Store/support/supDetail.jsp?oid=209708&BV_U... http://download.ebz.epson.net/faq/linux/faq_ls_00002.html http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX
On 14.12.2014 04:46, Jim Lewis wrote:
Hello all,
I can't scan to my Epson WF-2540 printer/scanner.
http://www.epson.com/cgi-bin/Store/support/supDetail.jsp?oid=209708&BV_U... http://download.ebz.epson.net/faq/linux/faq_ls_00002.html http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX
Hello all,
I followed the steps given by poma without any errors or problems. Same result, skanlite doesn't even attempt to look for the Epson via the network (as verified by tcpdump). Note that it IS there because my Fedora 14 system sees it.
Doug, I'm not sure what you mean by Epson 1 and 2.
I am thinking that there is another piece to this that I am missing.
Jim Lewis
On 12/14/2014 09:07 PM, Jim Lewis wrote:
On 14.12.2014 04:46, Jim Lewis wrote:
Hello all,
I can't scan to my Epson WF-2540 printer/scanner.
http://www.epson.com/cgi-bin/Store/support/supDetail.jsp?oid=209708&BV_U... http://download.ebz.epson.net/faq/linux/faq_ls_00002.html http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX
Hello all,
I followed the steps given by poma without any errors or problems. Sameresult, skanlite doesn't even attempt to look for the Epson via the network (as verified by tcpdump). Note that it IS there because my Fedora 14 system sees it.
Doug, I'm not sure what you mean by Epson 1 and 2. I am thinking that there is another piece to this that I am missing.Jim Lewis
I find in my records a directory which show a list of files.
[doug@dell2 etc]$ cd ./sane.d [doug@dell2 sane.d]$ ls -la total 348 drwxr-xr-x 3 root root 4096 Jun 18 10:39 ./ drwxr-xr-x 139 root root 12288 Dec 13 23:28 ../ -rw-r--r-- 1 root root 25 Jun 18 05:28 abaton.conf -rw-r--r-- 1 root root 14 Jun 18 05:28 agfafocus.conf -rw-r--r-- 1 root root 24 Jun 18 05:28 apple.conf -down to- -rw-r--r-- 1 root root 12 Jun 18 05:28 dmc.conf -rw-r--r-- 1 root root 1378 Jun 18 05:28 epjitsu.conf -rw-r--r-- 1 root root 1993 Jun 18 05:28 epkowa.conf -rw-r--r-- 1 root root 376 Jun 18 05:28 epson2.conf <<< -rw-r--r-- 1 root root 793 Jun 18 05:28 epson.conf <<< -rw-r--r-- 1 root root 2196 Jun 18 05:28 fujitsu.conf -rw-r--r-- 1 root root 1902 Jun 18 05:28 genesys.conf -down to- -rw-r--r-- 1 root root 1684 Jun 18 05:28 umax_pp.conf -rw-r--r-- 1 root root 204 Jun 18 05:28 v4l.conf -rw-r--r-- 1 root root 3424 Jun 18 05:28 xerox_mfp.conf [doug@dell2 sane.d]$ pwd /etc/sane.d
Notice the items I marked <<< . Also notice the file above that: epkowa. That works for me also, with some extra capability. Notice there is epson.conf and epson2.conf. I need epson2.conf, or epkowa.conf.
This would be the list of files on the Epson scanner driver file.
This directory shows up as a list of drivers in /etc/sane.d/dll.conf, as follows:
[doug@linux64 ~]$ cd /etc/sane.d/ [doug@linux64 sane.d]$ cat dll.conf # enable the next line if you want to allow access through the network: net (In my case, I enabled this line) abaton agfafocus apple avision artec artec_eplus48u as6e bh canon canon630u canon_dr #canon_pp cardscan coolscan #coolscan2 coolscan3 #dc25 #dc210 #dc240 dell1600n_net dmc epjitsu epson epson2 fujitsu #gphoto2 genesys gt68xx hp hp3900 hpsj5s hp3500 hp4200 hp5400 hp5590 hpljm1005 hs2p ibm kodak kvs1025 kvs20xx leo lexmark ma1509 magicolor matsushita microtek microtek2 mustek #mustek_pp mustek_usb mustek_usb2 nec niash #p5 pie pint pixma plustek #plustek_pp #pnm qcam ricoh rts8891 s9036 sceptre sharp sm3600 sm3840 snapscan sp15c #st400 #stv680 tamarack teco1 teco2 teco3 #test u12 umax #umax_pp umax1220u v4l xerox_mfp # The epkowa backend is provided by the iscan-free package: #epkowa hpaio [doug@linux64 sane.d]$
The next thing is to comment out ONE of the epsons. In my case, I left epson2 so as to make it work.
Hope this helps.
doug
On Sun, Dec 14, 2014 at 9:11 PM, Doug dmcgarrett@optonline.net wrote:
On 12/14/2014 09:07 PM, Jim Lewis wrote:
On 14.12.2014 04:46, Jim Lewis wrote:
Hello all,
I can't scan to my Epson WF-2540 printer/scanner.
http://www.epson.com/cgi-bin/Store/support/supDetail.jsp? oid=209708&BV_UseBVCookie=yes&infoType=Downloads&platform=OSF_O_LINUX http://download.ebz.epson.net/faq/linux/faq_ls_00002.html http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX
Hello all,
I followed the steps given by poma without any errors or problems.Same result, skanlite doesn't even attempt to look for the Epson via the network (as verified by tcpdump). Note that it IS there because my Fedora 14 system sees it.
Doug, I'm not sure what you mean by Epson 1 and 2. I am thinking that there is another piece to this that I am missing.Jim Lewis
I find in my records a directory which show a list of files.
[doug@dell2 etc]$ cd ./sane.d [doug@dell2 sane.d]$ ls -la total 348 drwxr-xr-x 3 root root 4096 Jun 18 10:39 ./ drwxr-xr-x 139 root root 12288 Dec 13 23:28 ../ -rw-r--r-- 1 root root 25 Jun 18 05:28 abaton.conf -rw-r--r-- 1 root root 14 Jun 18 05:28 agfafocus.conf -rw-r--r-- 1 root root 24 Jun 18 05:28 apple.conf -down to- -rw-r--r-- 1 root root 12 Jun 18 05:28 dmc.conf -rw-r--r-- 1 root root 1378 Jun 18 05:28 epjitsu.conf -rw-r--r-- 1 root root 1993 Jun 18 05:28 epkowa.conf -rw-r--r-- 1 root root 376 Jun 18 05:28 epson2.conf <<< -rw-r--r-- 1 root root 793 Jun 18 05:28 epson.conf <<< -rw-r--r-- 1 root root 2196 Jun 18 05:28 fujitsu.conf -rw-r--r-- 1 root root 1902 Jun 18 05:28 genesys.conf -down to- -rw-r--r-- 1 root root 1684 Jun 18 05:28 umax_pp.conf -rw-r--r-- 1 root root 204 Jun 18 05:28 v4l.conf -rw-r--r-- 1 root root 3424 Jun 18 05:28 xerox_mfp.conf [doug@dell2 sane.d]$ pwd /etc/sane.d
Notice the items I marked <<< . Also notice the file above that: epkowa. That works for me also, with some extra capability. Notice there is epson.conf and epson2.conf. I need epson2.conf, or epkowa.conf.
This would be the list of files on the Epson scanner driver file.
This directory shows up as a list of drivers in /etc/sane.d/dll.conf, as follows:
[doug@linux64 ~]$ cd /etc/sane.d/ [doug@linux64 sane.d]$ cat dll.conf # enable the next line if you want to allow access through the network: net (In my case, I enabled this line) abaton agfafocus apple avision artec artec_eplus48u as6e bh canon canon630u canon_dr #canon_pp cardscan coolscan #coolscan2 coolscan3 #dc25 #dc210 #dc240 dell1600n_net dmc epjitsu epson epson2 fujitsu #gphoto2 genesys gt68xx hp hp3900 hpsj5s hp3500 hp4200 hp5400 hp5590 hpljm1005 hs2p ibm kodak kvs1025 kvs20xx leo lexmark ma1509 magicolor matsushita microtek microtek2 mustek #mustek_pp mustek_usb mustek_usb2 nec niash #p5 pie pint pixma plustek #plustek_pp #pnm qcam ricoh rts8891 s9036 sceptre sharp sm3600 sm3840 snapscan sp15c #st400 #stv680 tamarack teco1 teco2 teco3 #test u12 umax #umax_pp umax1220u v4l xerox_mfp # The epkowa backend is provided by the iscan-free package: #epkowa hpaio [doug@linux64 sane.d]$
The next thing is to comment out ONE of the epsons. In my case, I left epson2 so as to make it work.
Hope this helps.
doug
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
so, xsane doesnt load? i got a epson wp-4530 scanning fine on f17,...
On 15.12.2014 03:07, Jim Lewis wrote:
On 14.12.2014 04:46, Jim Lewis wrote:
Hello all,
I can't scan to my Epson WF-2540 printer/scanner.
http://www.epson.com/cgi-bin/Store/support/supDetail.jsp?oid=209708&BV_U... http://download.ebz.epson.net/faq/linux/faq_ls_00002.html http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX
Hello all,
I followed the steps given by poma without any errors or problems. Same result, skanlite doesn't even attempt to look for the Epson via the network (as verified by tcpdump). Note that it IS there because my Fedora 14 system sees it.
FAQ - Linux - Scanner http://download.ebz.epson.net/faq/linux/scanner.html
How do I set up and use the network plugin to scan via the network? http://download.ebz.epson.net/faq/linux/faq_ls_00007.html
Sane - For Epson hardware https://wiki.archlinux.org/index.php/sane#For_Epson_hardware
With the above mentioned settings, is it does it via 'iscan'?
On 15.12.2014 03:07, Jim Lewis wrote:
On 14.12.2014 04:46, Jim Lewis wrote:
Hello all,
I can't scan to my Epson WF-2540 printer/scanner.
http://www.epson.com/cgi-bin/Store/support/supDetail.jsp?oid=209708&BV_U... http://download.ebz.epson.net/faq/linux/faq_ls_00002.html http://download.ebz.epson.net/dsc/search/01/search/?OSC=LX
Hello all,
I followed the steps given by poma without any errors or problems. Same result, skanlite doesn't even attempt to look for the Epson via the network (as verified by tcpdump). Note that it IS there because my Fedora 14 system sees it.
FAQ - Linux - Scanner http://download.ebz.epson.net/faq/linux/scanner.html
How do I set up and use the network plugin to scan via the network? http://download.ebz.epson.net/faq/linux/faq_ls_00007.htmlSane - For Epson hardware https://wiki.archlinux.org/index.php/sane#For_Epson_hardware
With the above mentioned settings, is it does it via 'iscan'?
Success! Well at least I think so, I'm scared to try another scan for fear it will screw up again. Here are some details:
- When I followed the steps above the scanner worked, but ONLY with iscan.
- The sane-find-scanner program doesn't even look for the scanner.
- skanlite now finds it, displays the panel showing what is found, and then immediately shows a dialog saying "Opening the selected scanner failed". Of course you can't actually see what device it's trying to use because that info goes away too fast to read. I'll assume there's a REALLY GOOD technical reason for that (or an option I don't know about).
- I made some mistakes too. I had put an original copy of dll.conf in my /temp directory, and was running skanlite from there. Oops, Bad Jim! I noticed with strace that it was reading that one (instead of in /etc/sane.d). I don't normally do stupid things like that, but when I do ...
- I still had tcpdump going when this finally worked. On my previous 9000 attempts it just sat there, so when it started spewing out packets I must have jumped 2 feet out of my chair.
I am going to clean up my notes and put out a detailed account of how I got this to work. Thanks to everyone for their help, I hope to return the favor very soon. I should have joined this group a long time ago.
Jim Lewis
Unlike the case with a network capable scanner i.e. the scanner connected directly to the network, these are the settings for sharing across a network scanner connected to a computer via USB.
As root, on *server*:
1. Create 'saned' user & group
# getent group saned >/dev/null 2>&1 || groupadd -r saned 2>&1 # getent passwd saned >/dev/null 2>&1 || useradd -r -l -g saned -d /dev/null -s /sbin/nologin -c "SANE network daemon" saned >/dev/null 2>&1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2. Create template unit configuration service file
/etc/systemd/system/saned@.service [Unit] Description=SANE network daemon Requires=saned.socket
[Service] ExecStart=/usr/sbin/saned User=saned Group=saned StandardInput=socket Environment=SANE_CONFIG_DIR=/etc/sane.d # Debug: #Environment=SANE_DEBUG_DLL=128 SANE_DEBUG_NET=128
[Install] Also=saned.socket
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3. Create unit configuration socket file
/etc/systemd/system/saned.socket [Unit] Description=saned incoming socket
[Socket] ListenStream=6566 Accept=yes MaxConnections=1
[Install] WantedBy=sockets.target
~~~~~~~~~~~~~~~~~~~~~~~~
4. Create udev rule file
/etc/udev/rules.d/70-saned.rules ACTION=="add", ENV{libsane_matched}=="yes", GROUP="saned", MODE="0660"
~~~~~~~~~~~~~~~~~~
5. Apply udev rule
# udevadm trigger --action=add
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
6. Add clinet name, client IP address, or IP subnet to saned configuration file, within 'Access list' section. In this example clinet IP address is used
/etc/sane.d/saned.conf 192.168.1.2
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
7. Firewall - open SANE control port 6566/tcp
~~~~ ~~~~\ /~~~~/ ~~~~\ /~~~~/ ~~~~/~~~~/ /~~~~/~~~~\ /~~~~/ ~~~~\ /~~~~/ ~~~~\ ~~~~
As root, on *client*:
1. Add server name or server IP address to net backend configuration file, within 'saned hosts' section. In this example server IP address is used
/etc/sane.d/net.conf 192.168.1.1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2. Fire up your favorite frontend, xsane, scanimage, simple-scan, skanlite, ...
~~~~
Tested and works.
poma
Ref. saned systemd support https://bugzilla.redhat.com/show_bug.cgi?id=1091566
On 16.12.2014 08:18, poma wrote:
Unlike the case with a network capable scanner i.e. the scanner connected directly to the network, these are the settings for sharing across a network scanner connected to a computer via USB.
As root, on *server*:
- Create 'saned' user & group
# getent group saned >/dev/null 2>&1 || groupadd -r saned 2>&1 # getent passwd saned >/dev/null 2>&1 || useradd -r -l -g saned -d /dev/null -s /sbin/nologin -c "SANE network daemon" saned >/dev/null 2>&1
2. Create template unit configuration service file /etc/systemd/system/saned@.service [Unit] Description=SANE network daemon Requires=saned.socket [Service] ExecStart=/usr/sbin/saned User=saned Group=saned StandardInput=socket Environment=SANE_CONFIG_DIR=/etc/sane.d # Debug: #Environment=SANE_DEBUG_DLL=128 SANE_DEBUG_NET=128 [Install] Also=saned.socket ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3. Create unit configuration socket file /etc/systemd/system/saned.socket [Unit] Description=saned incoming socket [Socket] ListenStream=6566 Accept=yes MaxConnections=1 [Install] WantedBy=sockets.target ~~~~~~~~~~~~~~~~~~~~~~~~ 4. Create udev rule file /etc/udev/rules.d/70-saned.rules ACTION=="add", ENV{libsane_matched}=="yes", GROUP="saned", MODE="0660" ~~~~~~~~~~~~~~~~~~ 5. Apply udev rule # udevadm trigger --action=add
- Add clinet name, client IP address, or IP subnet to saned configuration file, within 'Access list' section. In this example clinet IP address is used
/etc/sane.d/saned.conf 192.168.1.2
7. Firewall - open SANE control port 6566/tcp ~~~~ \~~~~\ /~~~~/ \~~~~\ /~~~~/ \~~~~\/~~~~/ /~~~~/\~~~~\ /~~~~/ \~~~~\ /~~~~/ \~~~~\ ~~~~ As root, on *client*: 1. Add server name or server IP address to net backend configuration file, within 'saned hosts' section. In this example server IP address is used /etc/sane.d/net.conf 192.168.1.1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2. Fire up your favorite frontend, xsane, scanimage, simple-scan, skanlite, ... ~~~~ Tested and works. poma Ref. saned systemd support https://bugzilla.redhat.com/show_bug.cgi?id=1091566
The above mentioned setup is OK for the case of standalone scanner. However in case of multifunction device i.e. combined printer and scanner sharing a common device node, the following settings are technically correct:
On *server*:
1. Create 'saned' user & add to already defined 'lp' group (see 'setup' package)
# getent passwd saned >/dev/null 2>&1 || useradd -r -l -g lp -d /dev/null -s /sbin/nologin -c "SANE network daemon" saned >/dev/null 2>&1
2. & 3. are OK
4. Create udev rule file
/etc/udev/rules.d/70-saned-cupsd.rules ACTION=="add", ENV{libsane_matched}=="yes", GROUP="lp", MODE="0660"
5. - 7. are OK
~~~~
On *client*:
1. & 2. are OK
Tested and works.
poma
On 12/13/2014 10:46 PM, Jim Lewis wrote:
Hello all,
I can't scan to my Epson WF-2540 printer/scanner. About 1 nanosecond after running skanlite a dialog box comes up saying no devices were found. Of course it prints fine. This printer is shown as compatible for both printing and scanning on the Linux Foundation site (where I got the driver for it).
I have tried this so far:
turned off firewalld
ran tcpdump between the computer and printer, then ran skanlite again.
There is no indication that there was ever any communication between them.
- ran skanlite with strace. Lot's of output (duh) but no smoking gun that
I could see.
My old Fedora 14 system can find the scanner just fine, and you can see the network traffic pretty clearly. If anyone has any ideas I would sure like to hear them.
Jim Lewis
Have you downloaded the scanner driver from Epson? Also, do you have the SANE app? (I'm not familiar with the guts of Fedora--I used it years ago, but I'm not using it now.) It may be that skanlite is just another sane front-end. Anyway, I have found that sometimes the scanner "just works"--perhaps there's some generic drivier in the OS, and sometimes it doesn't, in which case you have to go to Epson's Linux download section, and find your all-in-one machine and download the scanner portion. (It seems you have the printer part working OK, but if there are things there that don't work, you can download printer driver software form the same site.)
If there is more than one Epson listed in the driver for your machine--i.e. Epson 1 and Epson 2, try both. My setup is networked on a LAN, and I had to select Epson 2. (I have a different model Epson all-in-one, the WP4530, but I imagine my experience may be common to other machines also.) You will need to open the driver and select 1 or 2 and see what happens. (If you have 1 and 2. I do.)
When you get it to work, it should do a real nice job. Epson practically invented the scanner and their scanners work really nicely.
Good luck--doug
-
Doug -
Jack Craig -
Jim Lewis -
poma