[SOLVED] Scanner not recognized on Epson Workforce 633 with Slackware 13.37 32-bit

tfrei · 05-17-2011, 01:19 PM

I had a similar problem on 13.1, but was solved by this forum by copying 80-sane.rules to /etc/udev/rules.d/ . With 13.37 the same trick doesn't work. Here is my scanimage output:

Code:

root@Shuttle:/home/tfrei# 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).

Here is my sane-find-scanner output:

Code:

root@Shuttle:/home/tfrei# sane-find-scanner 

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

could not fetch string descriptor: Pipe error
could not fetch string descriptor: Pipe error
  # No USB scanners found. If you expected something different, make sure that
  # you have loaded a kernel driver for your USB host controller and have setup
  # the USB system correctly. See man sane-usb for details.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

What do you think?

sparkyhall · 05-18-2011, 06:41 AM

Check to see if your scanner is detected as root. If it is you may need to add your users to the scanner group.

tfrei · 05-18-2011, 08:48 AM

Thanks. I did do the commands above as root and the scanner was not recognized. I do have my user in the scanner group. Also, I am able to print as a regular user as well. I'm stumped since usually I can recognize the scanner as root and I have to fiddle with permissions in order to make the scanner available to regular users. This time, using 13.37, I can't do that.

bassplayer69 · 05-18-2011, 09:41 PM

I have an Epson Workforce 630 that is on my network that works fine when I use XSane version 0.998 (GUI). This is on Slackware 13.37 32-bit. This is what I get when I tried your command line command:

Code:

root@kermit:/# ls -l /etc/rules.d
ls: cannot access /etc/rules.d: No such file or directory
root@kermit:/# sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

  # No USB scanners found. If you expected something different, make sure that
  # you have loaded a kernel driver for your USB host controller and have setup
  # the USB system correctly. See man sane-usb for details.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.
root@kermit:/#

Notice I don't have an /etc/rules.d directory, but I can scan without any issues using the XSane software (GUI).

Is yours on the network or USB? If its on the network or parallel port then these lines apply:

Code:

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

My only issue I have with the Workforce is when I try printing in landscape mode. The driver stretches the printout to fit the landscape width. Portrait printing works just fine. I'm using the Epson driver for Workforce 615 since that's the closest model # I can find.

tfrei · 05-19-2011, 09:43 AM

Thanks bassplayer. I mistakenly said "/etc/rules.d" above when I should have said "/etc/udev/rules.d"

My scanner is on a usb connection. Looking in the 80-libsane.rules file in /lib/udev/rules.d/ directory, I see that my specific model is listed with all the proper information.

When I call up xsane, it does a search for the scanner and comes up empty.

I am stumped. Is there something different with the way slackware configures printers in this new version?

bassplayer69 · 05-21-2011, 08:14 PM

That I don't know. I didn't install 13.1. I had 13.0 installed before, but back then I was using a HP 1200 laserjet and didn't have a scanner. I switched to the EPSON when my toner cartridge went dry. The EPSON printer was the same price as the cartridge. :-)

I see the /etc/udev/rules.d/80-libsane.rules file, but I didn't touch it. I looked in the file and this is what I found for WorkForce 630 Series:

Code:

# EPSON Stylus SX620FW Series | EPSON WorkForce 630 Series
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="085d", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"

# EPSON WorkForce 630
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="085d", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"

Just a thought, are you part of the "plugdev" group since its USB? And, of course, the "scanner" group?

giberg · 10-28-2011, 05:04 AM

Similar problem here with Slackware 64 current and an old Trust EasyWebscan 19200 (artec_eplus48u).

Code:

root@darkstar:/home/gianni# sane-find-scanner 

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

  # No USB scanners found. If you expected something different, make sure that
  # you have loaded a kernel driver for your USB host controller and have setup
  # the USB system correctly. See man sane-usb for details.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.

But as normal user there are these lines too:

Code:

could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 003:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 004:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 005:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 006:001: Access denied (insufficient permissions)
could not open USB device 0x1d6b/0x0001 at 007:001: Access denied (insufficient permissions)
could not open USB device 0x5986/0x0102 at 002:002: Access denied (insufficient permissions)

My groups:

Code:

gianni@darkstar:~$ groups
users lp floppy audio video cdrom plugdev power netdev scanner

Udev rule:

Code:

# Trust Easy Webscan 19200
ATTRS{idVendor}=="05d8", ATTRS{idProduct}=="4006", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"

Skanlite and Xsane show my scanner as found device but it doesn'work. No permission.

Edit
SOLVED: I forgot to copy "Artec48.usb" from the original cd to /usr/share/sane/artec_eplus48u

giberg · 10-28-2011, 09:42 AM

Quote:

Originally Posted by giberg

Edit
SOLVED: I forgot to copy "Artec48.usb" from the original cd to /usr/share/sane/artec_eplus48u

Damn! It works only for root...

Well... better than nothing.

Edit: SOLVED
chmod a+r /usr/share/sane/artec_eplus48u/Artec48.usb

now it works not only for root.

tfrei · 12-17-2011, 12:10 PM

Just updating this thread. Situation same as before. [ I'm able to scan things by scanning to a thumbdrive and then transfer, however.]

Maybe someone has solved this by now?

allend · 12-17-2011, 06:51 PM

Have you downloaded and installed the necessary drivers?
http://www.avasys.jp/lx-bin2/linux_e/spc/DL2.do

tfrei · 12-18-2011, 11:50 AM

Thanks allend. I didn't download any drivers, but I did start to think more basic and looked at /etc/sane.d/epson2.conf and found that if I supplied the right device vendor and product id as the file recommends everything works fine.

This happens all the time to me. Something doesn't work right away and I overlook a simple solution in search of something more difficult.

Thank you all for your help.