[sane-devel] AGFA SnapScan e20: It's not in the scanimage list and don't work.
Carlos M. Buj Ribas
karlosbuj@terra.es
Sat, 9 Feb 2002 11:36:08 +0100
On Saturday 09 February 2002 12:26 am, Philippe Reis wrote:
Hi,
the Scanner must work!!. I use the same and is working perfectly.
My success history after checking and asking quite a lot...
I installed the last sane package, the 1.0.7 and just the backends.
You need also the package usbmgr, you can get it from here:
http://www.wondernetworkresources.com/staff/shuu/linux/usbmgr/#GET_USBMGR
I installed the version 0.4.8.1
You need as well the file Snape20.bin and agfafirm. Snape20.bin you can find
in the CD that comes with the Scanner and agfafirm can find here:
http://snapscan.sourceforge.net/agfafirm .
Ok, now comes the installation:
1. Remove the old sane packages. Remove /dev/scanner and /dev/usbscanner
2. Install the new ones; cd sane-x.x.x; ./configure; make; make install
3. Install the usbmgr
4. Copy the packages Snape20.bin and agfafirm in the directory
/usr/local/bin/agfa or where you want, I just made like this... The files
must have execute permissions.
5. Create the device: mknod /dev/usbscanner c 180 48
6. Modify the following file: /etc/modules.conf add the following lines:
options scanner vendor=0x6bd product=0x2091
post-install scanner /usr/local/bin/agfa/agfafirm /dev/usbscanner
/usr/local/bin/agfa/Snape20.bin ==========> the last two lines are just one
line!!!
7. Modify the file /usr/local/etc/sane.d/snapscan.conf It must look like
this:
# If not automatically found from above, then you may manually specify
# a device name.
# For USB devices, make sure that the name contains 'usb' somewhere, as in
# '/dev/usbscanner' or '/dev/usb/scanner0'. Do not use a link
# from /dev/scanner to your USB device.
# For SCSI, use the generic device (e.g. /dev/sg0 in Linux).
#/dev/sg0
/dev/usbscanner
# Change to the fully qualified filename of your firmware file, if
# firmware upload is needed by the scanner
firmware /usr/local/bin/agfa/Snape20.bin
8. Reboot the system. If everything is OK when you restart the system the
Scanner must begin to make something...
9. execute sane-find-scanner, the result must be something like this:
karlosbuj@linux:/usr/local/etc/sane.d> sane-find-scanner
# Note that sane-find-scanner will find any scanner that is connected
# to a SCSI bus and some scanners that are connected to the Universal
# Serial Bus (USB) depending on your OS. It will even find scanners
# that are not supported at all by SANE. It won't find a scanner that
# is connected to a parallel or proprietary port.
# You may want to run this program as super-user to find all devices.
# Once you found the scanner devices, be sure to adjust access
# permissions as necessary.
sane-find-scanner: found USB scanner (vendor = 0x06bd, product = 0x2091) at
device /dev/usbscanner
11. Now you can make a test:
scanimage -d snapscan:/dev/usbscanner >test.pnm
But the best is to try xscanimage or kooka.
Bye
> Hi
>
> First, thanks to Olivier Schwartz for his previous response.
>
> After having read the response of O. Schwartz,
>
> 1,2,3) I deleted all the files concerning SANE on my system with the
> command ( #find / -mount -iname "*sane*" -exec rm -rf {} \; ) and the files
> resting. Then I reinstalled SANE with "./configure, make and make install"
> in root user.
>
> 4) I modified the snapscan.conf file with the correct device and firmware
> path.
>
> 5) After I rebooted my PC
>
> 6) After I set the right on /dev/usb/scanner0 to "crw-rw---- 1 philippe
> usb 180, 48 avr 14 2001 scanner0" and on /dev/usb to "drwxrwxrwx
> 2 root root 4096 jan 29 19:46 usb/".
>
> 7) After as root, I launched "sane-find-scanner -v". The scanner was
> detected on /dev/usb/scanner0 as set in snapscan.conf.
>
> sane-find-scanner: searching for USB scanners:
> sane-find-scanner: checking /dev/usb/scanner... failed to open (status 4)
> sane-find-scanner: checking /dev/usb/scanner0... open ok, vendor and
> product ids were identified sane-find-scanner: found USB scanner (vendor =
> 0x06bd, product = 0x2091) at device /dev/usb/scanner0 sane-find-scanner:
> checking /dev/usb/scanner1... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner2... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner3... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner4... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner5... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner5... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner7... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner8... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner9... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner10... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner11... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner12... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner13... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner14... failed to open (status 4) sane-find-scanner:
> checking /dev/usb/scanner15... failed to open (status 4) sane-find-scanner:
> checking /dev/usbscanner... open ok, but vendor and product could NOT be
> identified sane-find-scanner: found USB scanner (UNKNOWN vendor and
> product) at device /dev/usbscanner sane-find-scanner: checking
> /dev/usbscanner0... failed to open (status 4) Why does sane-find-scanner
> find a scanner at /dev/usbscanner ?
> If I delete this device, that could resolve my problem ???
>
>
>
> 8) After that I verified my environnemental variable:
> SANE_DEFAULT_DEVICE=snapscan:/dev/usb/scanner0
> SANE_CONFIG_DIR=/usr/local/etc/sane.d/snapscan.conf
> SANE_DEBUG_SNAPSCAN=255
>
> I launched the "scanimage > test10.pgm" but it didn't work:
>
> [root@localhost /tmp]# scanimage > test10.pgm
> [sanei_debug] Setting debug level of snapscan to 255.
> [snapscan] sane_snapscan_init
> [snapscan] sane_snapscan_init: Snapscan backend version 1.4.7
> [snapscan] sane_snapscan_init: configuration file not found, defaulting to
> /dev/scanner. [snapscan] add_device(/dev/scanner)
> [snapscan] add_device: Detected (kind of) a SCSI device
> [snapscan] add_device: error opening device /dev/scanner: Invalid argument
> [snapscan] sane_snapscan_init: failed to add device
> "/usr/local/lib/sane/libsane-snapscan.so.1" [snapscan] sane_snapscan_open
> (/dev/usb/scanner0, 0xbffff4a4)
> [snapscan] find_device
> [snapscan] sane_snapscan_open: device "/dev/usb/scanner0" not in current
> device list. scanimage: open of device snapscan:/dev/usb/scanner0 failed:
> Invalid argument [snapscan] sane_snapscan_exit
> [root@localhost /tmp]#
>
> This error message is the same for user root or other.
>
> 9) After I launched "sane-find-scanner /dev/usb/scanner0" and the result
> was a segmentation error (core dump):
>
> [root@localhost /tmp]# sane-find-scanner /dev/usb/scanner0
> # Note that sane-find-scanner will find any scanner that is connected
> # to a SCSI bus and some scanners that are connected to the Universal
> # Serial Bus (USB) depending on your OS. It will even find scanners
> # that are not supported at all by SANE. It won't find a scanner that
> # is connected to a parallel or proprietary port.
>
> Erreur de segmentation (core dumped)
> [root@localhost /tmp]#
>
> 10) It can remarked that after executing scanimage, the info show with USB
> Viewer are not the same that before. The name of the scanner changed !
>
> Before using scanimage:
>
> SNAPSCAN e20
> Manufacturer: AGFA
> Speed: 12Mb/s (full)
> USB Version: 1.00
> Device Class: ff(vend.)
> Device Subclass: ff
> Device Protocol: ff
> Maximum Default Endpoint Size: 8
> Number of Configurations: 1
> Vendor Id: 06bd
> Product Id: 2091
> Revision Number: 0.62
>
> After using scanimage:
>
> usbscanner
> Speed: 12Mb/s (full)
> USB Version: 1.00
> Device Class: ff(vend.)
> Device Subclass: ff
> Device Protocol: ff
> Maximum Default Endpoint Size: 8
> Number of Configurations: 1
> Vendor Id: 06bd
> Product Id: 2091
> Revision Number: 0.62
>
>
> Is it possible that the problem comes from right privileges on the sane
> file ??? What must be the privileges of all files (directories) concerning
> SANE ?
>
>
> Ok these are all of the tentitave I made this evening.
> I think that it would be easier to use WINDOSSSSsssssss.....
>
> Thanks for your help !!!
>
> Best Regards
> Philippe
>
>
>
> ___________________________________________________________________________
>___ ifrance.com, l'email gratuit le plus complet de l'Internet ! vos emails
> depuis un navigateur, en POP3, sur Minitel, sur le WAP...
> http://www.ifrance.com/_reloc/email.emailif
> _______________________________________________ Sane-devel mailing list
> Sane-devel@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel