On Thu, 26 Jan 2006 18:41:16 +0800 "Joe Morris (NTM)" <Joe_Morris@ntm.org> wrote:
ken wrote:
Probably the same reason "sane-find-scanner" works:
# sane-find-scanner ... found USB scanner (vendor=0x05da, product=0x20b0) at libusb:002:002 ...
Which just basically tells you lsusb found it on the usb bus, but doesn't mean it will work or has a driver.
Okay. So we could say that we have connectivity from the scanner to the USB bus, yes?
but "scanimage -L" fails.
# scanimage -L
No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate)....
What's the next step? Edit /etc/sane.d/dll.conf and comment out microtek2, then retry.
I checked and ascertained that a dozen attempts ago. I've even rebooted a couple times since then. In the interest of expediency, I should also mention that /etc/sane.d/microtek2.conf contains: option dump 1 #option strip-height 14.0 option no-backtrack-option on option lightlid-35 on option toggle-lamp on option lineart-autoadjust on option backend-calibration on #option colorbalance-adjust on scsi * * Scanner These are listed in the suse doc referred to earlier as the default/recommended settings.
According to the sane website, it is supported good (flatbed mode only?). BTW, it does not seem to be listed in usb.ids, you might want to send an email to the maintainer (check /usr/share/usb.ids for email address.) to get its id (20b0) added.
20b0 is listed in /usr/share/usb.ids, but under "04a5 Acer Peripherals Inc. (now BenQ Corp.)" as: 20b0 S2W 3300U/4300U A quick look at this file tells me that the IDs don't have to be unique, so could I just add 20b0 to it along with the name of the scanner? Something like: 20b0 ScanMaker X12USL ??? That's what I just did anyway. Doing this didn't change the output of "scanimage -L" though; it's still not finding a scanner. So do I now need to rerun some hotplug script? If so, which? I also took your advice, am CCing the maintainer of usb.ids and the Suse package maintainers as well. Thanks again for the good tips. Suse HR should be noting all this. :) Regards, ken -- "This world ain't big enough for the both of us," said the big noema to the little noema.