Abel Deuring and I have made some progress on this problem (he's doing the lion's share of the work): there seems to be some communication problem between the kernel's scsi interface and SANE. The kernel and some scsi probing tools see the scanner while SANE 1.0.7 cannot. Abel sent me some debug code that allows sane-find-scanner to return the correct information about the scanner, but only with the "-v" argument. Without it, there's no difference.
results: sane-find-scanner: checking /dev/uk0... open ok result of first INQUIRY: 06 08 02 02 9c 00 00 00 result of second INQUIRY: 06 08 02 02 9c 00 00 00 55 4d 41 58 20 20 20 20 41 73 74 72 61 20 31 32 30 30 53 20 20 20 20 20 56 32 2e 37 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 76 be 00 00 a3 00 05 00 05 00 00 00 00 e1 00 03 7c 00 00 06 06 0c 03 52 05 78 00 00 00 00 03 52 04 92 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 52 00 00 00 00 00 00 40 00 00 08 00 00 00 sane-find-scanner: found SCSI scanner "UMAX Astra 1200S V2.7" at device /dev/uk0 without "-v" we just get this: result of first INQUIRY: result of second INQUIRY: 06 08 02 02 00 sane-find-scanner: found SCSI scanner " " at device /dev/uk0 [sanei_debug] Setting debug level of sanei_scsi to 255. We'll get there yet . . .
