[sane-devel] problem launching sane

Oliver Schwartz Oliver.Schwartz@gmx.de
Sun, 15 Feb 2004 22:27:22 +0100


=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

> # Change to the fully qualified filename of your firmware file, if
> # firmware upload is needed by the scanner
>    firmware /usr/local/agfafirm

There should be no spaces at the beginning of the line. Also this line=20
will only work if "agfafirm" is the renamed "Snapscan e20.bin" from=20
the windows driver installation.

> #/etc/sane.d/snapscan.conf
>
> # If not automatically found you may manually specify a device
> name.
>
> # For USB scanners also specify bus=3Dusb, e.g.
> /dev/usb/scanner0 bus=3Dusb

You shouldn't need this line.

> > "SANE_DEBUG_SNAPSCAN=3D255 xsane 2>debug.log" (which will create a
> > file "debug.log" with all the debugging information from the
> > backend.
>
> Here it is:
> [sanei_debug] Setting debug level of snapscan to 3.
> [snapscan] add_usb_device: error opening device libusb:001:002:
> Access to resource has been denied [snapscan] usb_read Only 8 bytes
> read

The file permission on /proc/bus/usb/001/* are not set correctly, the=20
backend cannot open the device files through libusb. Either correct=20
the permissions or use the scanner kernel module=20
("modprobe scanner vendor=3D0x06bd product=3D0x2091"). In your first post=20
you used the kernel module, since the scanner was detected at=20
/dev/usb/scanner0.

=2D -Oliver
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFAL+Q6/V6sbrmfIuMRAlxrAJ4sIBHqBFAI9aW9r67VIE/gmu+1vgCfdLAu
Pe7dEujYqCds7AhgwgtolVQ=3D
=3D/xp8
=2D----END PGP SIGNATURE-----