Jack McGill
--- On Wed, 11/5/08, Jack McGill <jmcgill85258 at yahoo.com> wrote: > From: Jack McGill <jmcgill85258 at yahoo.com> > Subject: Re: [sane-devel] Can't seem to find config files > To: "Igor G Novikov" <septagramm at gmail.com> > Date: Wednesday, November 5, 2008, 6:20 AM > --- On Wed, 11/5/08, Igor G Novikov > <septagramm at gmail.com> wrote: > > > From: Igor G Novikov <septagramm at gmail.com> > > Subject: Re: [sane-devel] Can't seem to find > config files > > To: sane-devel at lists.alioth.debian.org > > Date: Wednesday, November 5, 2008, 3:35 AM > > Thanks to both Jack and Olaf for advice. > > > > Now all configuration files are in place, except one, > sadly > > being > > mustek_usb2.conf... Which is just like it was when > sane was > > installed > > from an rpm package. That's strange, because > > ./configure clearly says > > that backend will be built: > > > I'm just guessing here, but the mustek_usb2 backend > probably doesn't need a .conf file because it only > supports one scanner at the present time. You could try the > change the product id in the source code to your scanner, in > the file that I mentioned previously and rebuild sane, and I > bet that your scanner will then be recognized by scanimage > -L. > > Also, read this > http://www.sane-project.org/man/sane-mustek_usb2.5.html > http://www.meier-geinitz.de/sane/mustek_usb2-backend/ > and > http://www.meier-geinitz.de/sane/gt68xx-backend/adding.html > the last reference describes how to add a device to a > different backend, so the details will be different, but > some of the principles will be the same. > > > > Also sane-find-scanner and scanimage -L still > don't > > identify my scanner > > (i did change sources as Jack suggested). However, > > sane-find-scanner > > output changed slightly from when i was running it > from rpm > > package. It > > now only says my scanner is Hewlett Packard when run > as > > root, otherwise > > it doesn't say anything except vendor, product and > chip > > id: > > > > found USB scanner (vendor=0x055f, product=0x0408, > > chip=SQ113?) at > > libusb:001:004 > > --instead of-- > > found USB scanner (vendor=0x055f [Hewlett-Packard. > > > ], > > product=0x0408 [USB2.0 Scanner ], > chip=SQ113) at > > libusb:001:004 > > > > So i suppose support for BearPaw, even though actually > > present in > > sources, should be somehow enabled? How can it be > done? > > > > P.S. It's maybe offtopic, but i feel very curious. > > Jack, you are > > precisely right about my cdma modem, where did you > look it > > up? > > I googled the product ID and vendor ID. > > Good luck and keep us updated. > > Jack