Hallo Oliver, > Strange, that should work even with sane-1.0.4. Can you send me a debug log > (Run "export SANE_DEBUG_SNAPSCAN=255", then "scanimage -L 2>debug.log"). > scanimage detects the scanner, but ...
Here comes the log-file: [sanei_debug] Setting debug level of snapscan to 255. [snapscan] sane_snapscan_init [snapscan] add_device(/dev/scanner) [snapscan] add_device: Detected (kind of) a SCSI device [snapscan] mini_inquiry [snapscan] snapscan_cmd [snapscan] add_device: Is vendor "Color" model "FlatbedScanner17" a supported scanner? [snapscan] add_device: "Color FlatbedScanner17" is not one of AGFA SnapScan 300, 310, 600 or 1236s, Acer VUEGO 300, 310S, 610S, or 610plus, Acer PRISA model 620S [snapscan] sane_snapscan_get_devices (0xbffff2c8, 0) [snapscan] sane_snapscan_exit Is there a binary package of sane-1.0.6 for use with SuSE 7.3 available on the net? I always relied on the setup tool "yast", which probably won't work with a self compiled sane-version not using the same directories as SuSE. I'm not that much into that stuff to do it manually. By the way I've realized that at least one of my SCSI Cdrom-drives doesn't work correctly anymore, since I've installed the scanner on the external SCSI bus. It's a pretty old 12x Philipps. Could there be a problem regarding termination? Termination is set at the last drive (CD-Writer) of my internal bus. But there is no termination at the scanner on the external bus, which I thought wouldn't be necessary. Kind regards Rainer
