Hi, On Tue, Dec 23, 2003 at 04:24:13AM +0100, Henrik Rintala wrote: > With both versions the problem is that scanimage does not seem to be > able to connect to the scanner.
[...] > Henrik-Rintala:/usr/local/bin shr$ ./sane-find-scanner > found USB scanner (vendor=0x04a9 [Canon], product=0x2206 [CanoScan], > chip=LM983x?) at libusb:024:002 The question mark after the chip id is a bad sign. It means, that sane-find-scanner was unable to actuall talk to the scanner. It could get its didentification but sending commands failed (usually because the interface couldn't be claimed). > Henrik-Rintala:/usr/local/bin shr$ ./scanimage -L > > No scanners were identified. If you were expecting something different, [...] Try enabling debug message. E.g. export SANE_DEBUG_PLUSTEK=255 export SANE_DEBUG_SANEI_USB=255 To reduce the number of USB messages, diable everything but plustek in dll.conf. There have been some reports that enabling debugging "fixes" libusb problems on MacOS X in some cases. Even if it doesn't, you should get a debug log that shows the exact error message. Also have a look at the archive of the last few weeks of sane-devel. There have been some similar reports. Bye, Henning
