USB scanner not attached when connected after system startup]

Harald Weis hawei at
Wed Jan 5 13:41:48 PST 2005

On Mon, Jan 03, 2005 at 09:32:20PM +0100, Roland Smith wrote:
> That's not good. AFAICT, the code that reports a new scanner to dmesg is
> also present in 4.x, so if you don't see a message, it looks like the
> scanner is not found for one reason or another.
> Do you see anything in dmesg if it is available at boot? If so, it would
> look like a definite bug to me. 

algol{me} ~ > dmesg | grep EPSON
uscanner0: EPSON EPSON Scanner, rev 1.10/3.02, addr 2
> But since it works on 5.3, I don't know what the value would be of
> sending a Problem Report on 4.9, since 5.3 is now STABLE.

Agree, not worth while.

> Have you considered upgrading to 5.3?

Yes, sure, I hope before the end of the month.
> See 'man core' for more info about coredumps. Core is an old term for
> memory (dating from the time of ferrite core memory). See the jargon file.

jargon file: thanks a lot for that one too, Roland.

> > > If it does appear, the scanner is found by the kernel. If the scanner
> > > does not work in this case, what exactly is the reported error? If

No error whatsoever is reported in dmesg. As to sane and scanimage, they just can't see any scanner.
On the other hand, if the scanner is disconnected from the working environment, sane-find-scanner continues to `find' the scanner as before (when it was really connected), scanimage is cleverer and says `there is no scanner', dmesg doesn't signal anything. Of course, if you want the scanner working again you must reboot. 

I'm afraid it's better to forget the problem again.

Many thanks, Roland, for all your patience and advice.

Next time I'll report 5.3 bugs only :-)

FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003

More information about the freebsd-stable mailing list