On Sun, Nov 07, 2004 at 11:36:48AM -0500, Karl Heinz Kremer wrote:
> So it's not that the scanner all of a sudden did stop to work, you did=20
> change the configuration of your system? Recompiling the kernel=20
> certainly qualifies for this.
I haven't used my scanner for a while, possibly a few months, until
yesterday. So, yes, although I did not change my SANE configuration
(and I'm in fact using the same version as several months ago), other
things have changed. I run Debian unstable and keep my kernel current,
so anything from the kernel to glibc to any other libraries could be at
fault.
> What is /dev/scanner linked to? (Does not really play a role if you get=
=20
/dev/sg0. (Yes, it's the right device. <g>)
> the same behavor with "scsi EPSON", but if you have not tried to run as=
=20
> root when you are using "scsi EPSON" in the config file, it could be=20
> important).
I reverted to "scsi EPSON", tried it as root, and it worked. Then I
tried it as fbriere, and it worked too. Figures.
Just for fun, I put "scsi /dev/generic" again, and it indeed didn't work
that way. So, I re-reverted to "scsi EPSON". And it didn't work
either, root or otherwise.
I blame gremlins. Or the phase of the moon. That's the only way it
makes sense.
Anyway, I power-cycled the scanner, and it appears to be working again
at first glance. Maybe it was a hardware glitch? Knock on wood.
--=20
Fr=E9d=E9ric Bri=E8re <*> [email protected]
=3D> <[email protected]> IS NO MORE: <http://www.abacomsucks.com> <=3D
