[SOLVED] xsane can't find scanner

fatlarry · 2008-05-23 11:55:27

Bummer: I had initially this scanner working on ARch (it works fine in Suse 10.0)- an old HP ScanJet 6200C, then I put a PCI TV card in and a capture card, and now I cannot find the scanner anymore. I bet it's a problem with udev and libusb, but I don't know enough to digg some more and I'm fed up reinventing the wheel. Anyway ...

Reading the docs, I understand there is a deprecated way of using this scanner, without using libusb (and therefore the shaky udev stuff). Could someone point me in the right direction to disable the use of libusb and use that instead?

Last edited by fatlarry (2008-06-26 17:33:14)

fatlarry · 2008-05-23 13:34:19

More specifically: is there a sane-backends package for Arch? I was able to find and install sane-frontends, but not sane-backends. The latter has the sane-hp driver for said scanner, then I could probably comment out the libusb option in the hp.conf file

vacant · 2008-05-23 14:26:10

sane no longer finds my scanner (epson 1260) unless it is powered on before I boot.

fatlarry · 2008-05-27 17:49:59

vacant wrote:

sane no longer finds my scanner (epson 1260) unless it is powered on before I boot.

Mine is always powered on; "sane-find-scanner" finds it, but xsane doesn't (or "scanimage" or xsanimage for that matter!

These days I'll try and disable libusb and see how that works.

vacant · 2008-05-27 18:48:42

If I switch on the scanner after boot it still works for root.

As an ordinary user:

 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.

found USB scanner (vendor=0x04b8, product=0x011d, chip=LM983x?) at libusb:004:003
found USB scanner (vendor=0x0c45, product=0x60c0) at libusb:004:002
(snipped)

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).

If I change /dev/bus/usb/004/003 so that my user can write to that device, then kooka and scanimage -L are happy

scanimage -L
device `plustek:libusb:004:003' is a Epson Perfection 1260/Photo flatbed scanner

Allan · 2008-05-27 20:13:14

What group permissions is your scanner given?

vacant · 2008-05-27 20:34:02

/dev/usbdev4.3 is given permissions -rw-rw-r-- owner:root, group:scanner, as expected from 53-sane.rules

# Epson Perfection 1260 | Epson Perfection 1260Photo
ATTRS{idVendor}=="04b8", ATTRS{idProduct}=="011d", MODE="0664", GROUP="scanner", ENV{libsane_matched}="yes"

but /dev/bus/usb/004/003 is -rw-r--r-- owner:root, group:root

My user is in the scanner group.

azleifel · 2008-05-27 22:10:45

Just on the off-chance, libgphoto and sane don't sit well together (there's an old bug report about the interaction between sane.rules and gphoto.rules somewhere in the tracker, but I cannot find it at the moment). If you have both installed then try temporarily moving 54-gphoto.rules out of /etc/udev/rules.d. If the scanner group gets set properly in /dev/bus/usb when udev is restarted then the quickest solution will probably be to do what I did and create a 91-local.rules file in /etc/udev/rules.d to contain the scanner rule.

vacant · 2008-05-28 08:01:08

Moving 54-gphoto.rules made no difference. I was unaware of sane/ghoto conflict but I think I tried adding a late local rule a month or so ago, though gave up when I realised that the sane rule was being picked up and applied to usbdev4.3 but not 003. I'm used to turning the scanner on before boot when I need it.

fatlarry · 2008-06-02 17:19:09

fatlarry wrote:

More specifically: is there a sane-backends package for Arch? I was able to find and install sane-frontends, but not sane-backends. The latter has the sane-hp driver for said scanner, then I could probably comment out the libusb option in the hp.conf file

OK, finally works: there is a /etc/sane.d/hp.conf and there I just commented out the net and scsi support, left only the

/dev/scanner

# and the device lines (with HP's vendor code 0x03f0 and various devices ... from 0x0101 to 0x0601 )

usb 0x03f0 0x0101
usb 0x03f0 0x0401
usb 0x03f0 0x0201
usb 0x03f0 0x0601

# and THEN un-commented the next line, which specifically disables the use of libusb:

/dev/usb/scanner0

Now xsane can find the scanner and I can scan as root, for now.

Last edited by fatlarry (2008-06-04 11:48:38)

Arch Linux

#1 2008-05-23 11:55:27

[SOLVED] xsane can't find scanner

#2 2008-05-23 13:34:19

Re: [SOLVED] xsane can't find scanner

#3 2008-05-23 14:26:10

Re: [SOLVED] xsane can't find scanner

#4 2008-05-27 17:49:59

Re: [SOLVED] xsane can't find scanner

#5 2008-05-27 18:48:42

Re: [SOLVED] xsane can't find scanner

#6 2008-05-27 20:13:14

Re: [SOLVED] xsane can't find scanner

#7 2008-05-27 20:34:02

Re: [SOLVED] xsane can't find scanner

#8 2008-05-27 22:10:45

Re: [SOLVED] xsane can't find scanner

#9 2008-05-28 08:01:08

Re: [SOLVED] xsane can't find scanner

#10 2008-06-02 17:19:09

Re: [SOLVED] xsane can't find scanner

Board footer