=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
> > I'm not a hacker at all so I'm not > > proficient in interpreting the log, but it seems that sane tries > > to add simultaneously a SCSI (bad) as well as a USB device > > (good).=20 That's not a problem. The backend will try to autodetect supported=20 devices, regardless of SCSI and USB.=20 > > Trying to add SCSI seems to be the problem. So I think > > the solution will be to out-comment adding the scsi device, but > > where and how? What exactly is your problem? The log you sent looks fine, but it's=20 incomplete. Your scanner is detected correctly. BTW, what scanner=20 model are you using? > > Or do I need to go into a total different direction? Check if you need to specify a firmware file for your scanner (see=20 http://snapscan.sourceforge.net ). If so, place the filename with=20 full path of the firmware file in snapscan.conf (after the keyword=20 firmware), e.g. firmware /usr/local/sane/u34v110.bin The firmware part of your snapscan.conf looks a bit messed up,=20 although all entries are commented out. You do not need to include a=20 reference to acerfirm or agfafirm. Other sources of information is the output of "scanimage -L" and=20 "SANE_DEBUG_SNAPSCAN=3D255 xsane 2>debug.log" (which will create a file=20 "debug.log" with all the debugging information from the backend. =2D -Oliver =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) iD8DBQFAL8Rb/V6sbrmfIuMRAr0fAJ9nVkZZvXg7c4jfns3rr6YxL4l7AgCfRgm9 tP5uOQieiGHCdYgOw/ZnqGM=3D =3DXbNZ =2D----END PGP SIGNATURE-----
