[sane-devel] HP 7450C USB scanner failure with ADF

[Thomas Frayne]

On Wed, 2003-06-25 at 11:36, m. allan noah wrote:
> tom, did you do an 'rpm -e --force --nodeps sane-backends' first?

Yes.

> 
> when you compiled the new sane backends, did you do:
> 
> ./configure --prefix=/usr --sysconfdir=/etc

No. I'll uninstall and verify that no sign of sane-backends remains,
then install again.

> make

Yes.

> make install

Yes.

> 
> if not, start with those two things. then we can be sure that the version 
> of sane you are using is the one you compiled.

Thanks.  I'll do it.

> 
> allan
> 
> On 25 Jun 2003, Thomas Frayne wrote:
> 
> > On Tue, 2003-06-24 at 12:41, Henning Meier-Geinitz wrote:
> > > Hi,
> > > > Then I rebooted to determine if the scanner would be detected as a usb
> > > > device.  The hardware browser still showed no browser, and xsane found
> > > > no scanner device on startup.
> > > > 
> > > > How can I get the scanner recognized as a USB device?
> > > 
> > > That's done automatically. If it's not detected as USB device by the
> > > kernel, it can't be used by hpusbscsi.
> > > 
> > > Is it found by sane-find-scanner as root?
> > > Is it found by scanimage -L as root?
> > > If yes, you may need to set up permissions for libusb correctly.
> > > That's explained in man sane-usb.
> > > 
> > 
> > Thanks.  I read the manual, found that permissions were not set
> > correctly, set them in fstab as recommended.  Then sane-find-scanner and
> > scanimage -L worked as a normal user.  However, the scanner still does
> > not work.  I think I am closer, but I am lost.
> > 
> > Messages indicated failure of usbdevfs, which is supposed to be
> > obsolete.  /usr/local/etc/sane.d/avision.conf lists devices which do not
> > exist.  I suspect that there is a mismatches among the sane
> > configuration which was set up for the initial Redhat 9, the sane
> > configuration set up when I installed sane-backends-1.0.12.tar.gz and
> > xsane-0.91.tar.gz, and the kernel 2.4.20-18.9, which was upgraded by
> > Up2date, but I can't figure out how to straighten it out.
> > 
> > I'll keep trying.  I have just done 
> > modprobe scanner vendor=0x0001  product=0x0002,
> > and I plan to reboot and continue debugging, starting with why
> > /dev/usbscanner does not exist.
> > 
> > Any help would be appreciated.
> > 
> > Tom Frayne
> >