* Gerry Gavigan <gg@gerryg.uklinux.net> [08-30-04 07:33]:
On Sunday 29 August 2004 22:54, Patrick Shanahan wrote:
linux:/ # sane-find-scanner found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan], chip=LM9832/3) at libusb:002:002
linux:/ # scanimage -L device `plustek:libusb:002:002' is a Canon N670U/N676U/LiDE20 USB flatbed scanner
so you should have at least: /etc/sane.d/plustek.conf usb 0x04a9 0x220d /dev/usb/scanner0
These are the last few lines of plustek.conf (sic)
# # and of course the device-name # # device /dev/usbscanner device auto
I would change this to 'device /dev/usbscanner'
# # to define a new device, start with a new section: # [usb] # usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d usb 0x4a9 0x220d
and delete all but one of these 'usb 0x4a9 0x220d'
the /dev/usb/scanner0 line might want to be /dev/usbscanner, you will need to experiment
If I understand correctly "device auto" picks up the device.
why leave it to chance?
yes, there is also, /dev/usbscanner
all devices lists start with devicetype0 rather than devicetype - do you think that is an issue here?
no, reference plustek.conf (sited above).
Although you suggest the printer comment was irrelevant I notice that plustek.conf seems to be looking for "usbscanner" rather than "scanner" in usb/ similar to the formats that did/didn't work for testing usb printers
usb is relevant, printer is not, just happens to be usb?? make the changes to the plustek.conf and try xsane report -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos