Hi, I had the same problem with my SNAPSCAN 1236s, the solution was to edit /etc/sane.d/snapscan.conf and replace '/dev/scanner' (or whatever is in there) through the proper device ( /dev/sg1 in your case ).
Another hint to make recognition faster with xscanimage/xsane/kooka: DISABLE all backends in /etc/sane.d/dll.conf you don't need! So obviously you'll need 'snapscan' and maybe 'net' if you want to work with 'saned'. If you don't have any other type of scanner, that's enough. So I hope it works for you too! Good luck, Heinz [EMAIL PROTECTED] schrieb am 21.01.02: > Hi, > > I just configured my SCSI adapter (old AVA1505 ISA card), to use my > scanner. Now sane-find-scanner does find it: > > [root@Jupiter dev]# 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. > > sane-find-scanner: found SCSI scanner "AGFA SNAPSCAN 1236 1.20" at > device /dev/sg1 > [root@Jupiter dev]# ll /dev/sg1 > lr-xr-xr-x 1 root root 36 Jan 21 18:01 /dev/sg1 -> > scsi/host1/bus0/target2/lun0/generic > > But when running scanimage or xsane, it says it can't find a scanner, > and I should make sure the scanner is detected by sane-find-scanner. > Could this be a devfs problem, or something wrong with sane? Are there > others who can use their scanner? > > libsane1-1.0.6-2mdk > devfsd-1.3.20-1mdk > > Frederik > > ______________________________________________________________________________ Eine Klasse f�r sich - der WEB.DE Club. High End Kommunikation & MEHR. Mehr Speicher, mehr Leistung, mehr Vorteile - http://club.web.de
