* Gerry Gavigan <gg@gerryg.uklinux.net> [08-29-04 12:28]:
On Sunday 29 August 2004 14:14, Patrick Shanahan wrote:
Have you gone to http://www.xsane.org to see if xsane supports your scanner? XSane is just a graphical user interface for sane and the applications that you cited as not seeing your scanner are all graphical. If your scanner is not supported by xsane, you can still scan from the command line, or there are other scanner gui's available, such as: vuescan http://www.hamrick.com/vsm.html
What brand/model of scanner do you have? Have you checked in /etc/scan.d/ for the config file and does it require modification?
(I know you realise) I was posting to indicate that between upgrades some devices that were working, stop working (it is my experience that they start working again one upgrade later).
A scientific observation
The scanner is the canoscan 670u and is auto detected by YaST and assigned the plustek driver. It successfully acquired a test image during set up. The scanner used to work through kooka in 9.0. Until 9.1 I have not needed to touch xsane.
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.
Currently Yast describes the device as "libusb"
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. rpm -q libusb will tell you if you have libusb installed Yast *may* be telling you that libusb *is* required. Yast2 -> Install Software -> libusb will do it.
However I cannot find that device in /dev/usb to test xsane [plustek:/dev/usb/libusb] [-s] from the command line (so kooka and indeed the gimp are irrelevant at this time)
http://www.sane-project.org/man/sane-plustek.5.html says (you should read as it is somewhat long): To use your scanner with this backend, you need at least two entries in the configuration file (there are more you might want): /usr/local/etc/sane.d/plustek.conf [usb] vendor-id product-id device /dev/usbscanner so you should have at least: /etc/sane.d/plustek.conf usb 0x04a9 0x220d /dev/usb/scanner0 or /etc/sane.d/canonusb.conf or /etc/sane.d/canon670u.conf with the same lines, usb... & /dev/usb/scanner0 the /dev/usb/scanner0 line might want to be /dev/usbscanner, you will need to experiment
The entries dev/usb/ contains are [scanner0] [scanner1] etc.
yes, there is also, /dev/usbscanner
It reminds me of the printer problem that I couldn't solve when I upgraded
not related.... and will confuse the issue
I cannot find libusb anywhere so even if I had confidence in my ability to correctly create a symbolic link, I am not sure that it would be any use.
Why would you want to 'create a symbolic link'? Use rpm to see if it is installed and/or look for it with 'locate'. From what you have told me here, it seems that it needs to be installed, if it is not. It will not hurt anything to have it installed anyway, except use a little disk space, so install it. -- 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