Re: xsane doesn't see USB scanner

On Sunday 29 August 2004 22:54, Patrick Shanahan wrote:
> So you didn't look to see if it was supported, but you say it worked
> with 9.0, so it is/was supported.  And you did not check to see if the
> config file was correct or even there.

I am not trying to waste your time - however I now realise I was being 
elliptical.  www.sane-project.org reported that the scanner was fully 
supported by the plustek driver (but this was something that I knew because 
it used to work under 9.0)

YaST correctly applied the driver and successfully performed a test scan 

I had also tried this:

linux:/ # sane-find-scanner

found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan], 
chip=LM9832/3) at libusb:002:002

# Your USB scanner was (probably) detected. It may or may not be supported by
# SANE. Try scanimage -L and read the backend's manpage.

and this

linux:/ # scanimage -L
device `plustek:libusb:002:002' is a Canon N670U/N676U/LiDE20 USB flatbed 
scanner

> libusb is a library "that allows userspace access to USB devices", not
> a device.  libusb provides access to the device, probably
> /dev/usb/scanner0 or /dev/usbscanner
>
> btw, I did not know what libusb was, I looked it up.  Some interest
> *is* required.

thank you for the information - I made an assumption based on ignorance, not 
laziness.   I am running  libusb 0.1.8-31     


> 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

#
# 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

> 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.  

However I ran it from the console, it was not recognised and I cannot find 
another reference to "device" the command      

> yes, there is also, /dev/usbscanner

all devices lists start with devicetype0 rather than devicetype - do you think 
that is an issue here?

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 

Gerry