[sane-devel] can not initialize sane when linux system booting up

Henning Meier-Geinitz henning at meier-geinitz.de
Tue May 20 10:53:13 BST 2003


Hi,

I'm sending a cc to the sane-devel mailing list.

On Mon, May 19, 2003 at 11:04:46PM +0700, T.M.Thanh wrote:
> >Does sane-find-scanner fin the scanner? If not, it's a kernel issue.
> 
> I think so but do not know exactly what it is. Probably due to the 
> kernel 2.4.x load modules dynamically.

So the scanner is not found by sane-find-scanner?

That would be quite unusual. On the other hand, someone else just
reported that his scanner is not detected by the kernel at all. If
it's really a kernel issue, you may want to write to the
linux-usb-users mailing list with more info like the output of
/proc/bus/usb/devices, lsmod, and dmesg. The list can be found at
http://www.linux-usb.org.

> >If it's found by sane-find-scanner but not "scanimage -L", maybe you
> >haven't given the correct path to the firmware filr in snapscan.conf?
> 
> When my scanner being initialized (by the way I described), it works 
> well . Thanks God !

Well, if my suspicion abou the firmware is correct, the firmware is
loaded by the Windows driver and it won't go away until you
power-cycle the scanner.

Hace you setup snapscan.conf to point to the correct firmware?

Bye,
  Henning



More information about the sane-devel mailing list