Thanks all for your help with my Vuego 610 scanner problem. I've done a write-up for the ones that come after me. Please correct any obvious mistakes.
keywords for our Googling friends: Vuego 610s, Benq 610s, Acer 610s, scanner, Linux, Mandrake 9.0, sane, xsane Installing a Vuego 610s scanner under Mandrake Linux 9.0 The short answer: A typo in the SANE configuration files on Mandrake causes the device only to be recognized if explicitly specified. e.g. "scanimage -d /dev/sg0" will work but "xsane" will give a "No devices found" error. Check /etc/sane.d/dll.conf and replace all occurences of "SnapScan" with "snapscan". If "/etc/sane.d/SnapScan.conf" exists it can safely be deleted/moved out of the way. I also had to uncomment all references to usb devices in /etc/sane.d/snapscan.conf. More details: In the process of moving my girlfriend from Win98 to Mandrake 9.0 I had to get her Vuego 610s SCSI scanner working, preferably under KDE. First of all, make sure you SCSI card (Adaptec 2906, using aic7xxx driver) is recognized by the system. Check if /proc/scsi lists your card, in my case /proc/scsi/aic7xxx. Control the hardware: is the scsi bus correctly terminated, scanner properly connected to SCSI interface, was the scanner powered on during boot? Vuego 610 scanners seem to require termination in Linux though this is NOT the case in Windows. Check if your scanner is properly recognized by the system. "cat /proc/scsi/scsi" should list entries for all SCSI devices on the bus. I found two devices: my CD-RW and 'Flatbedscanner_4'. Bingo! If the scanner is not found, try reloading the scsi modules and disabling the ide-scsi module if you have a CD-R/RW. Removing modules: "rmmod aic7xxx; rmmod sg; rmmod ide-scsi". Reloading aic7xxx module only: "modprobe sg; modprobe aic7xxx". "cat /proc/scsi/scsi" again. If the scanner still isn't found, you may have a kernel problem. Next, you need to modify you "/etc/sane.d/snapscan.conf" file. I had to remove all references to usb and uncomment the line where my scsi device is defined. I also removed the "firmware" line because I didn't see the point in keeping it. Thus, I have only one line reading "/dev/sg0", everything else is commented out. If you have a "/etc/sane.d/SnapScan.conf" file you can safely delete it. It's a crud Harddrake probably spit out and doesn't do anything anyway. By now, you should be able to perform scans from the command-line by explicitly specifying the SANE backend you want to use, like this: "scanimage --device-name=snapscan:/dev/sg0 > outputfile.ppm". The same typo in the SnapScan.conf file shows up in "/etc/sane.d/dll.conf". Replace all occurences of "Snapscan" with "snapscan" and you should be able to scan without explicitly specifying the device name: xsane works! Cheers & Thanks for your help. Francis Dierick [email protected]
