Jesse> Hey ho.
Jesse> Okay, so now I know that I wasn't specifying the proper device.
Jesse> Here's what has happened, following your advice:
Jesse> root:/home/jesse$ scanimage -d mustek:/dev/sga
Jesse> scanimage: open of device mustek:/dev/sga failed
Jesse> root:/home/jesse$ scanimage -d umax:/dev/sga
Jesse> scanimage: open of device umax:/dev/sga failed
Jesse> root:/home/jesse$ scanimage -d hp:/dev/sga
Jesse> scanimage: open of device hp:/dev/sga failed
Jesse> Now, does this mean that the driver is wrong or that the device
Jesse> specification is wrong?
Could be either. Try setting the environment variables I mentioned before
to get more info. E.g., try:
SANE_DEBUG_MUSTEK=128 SANE_DEBUG_DLL=128 SANE_DEBUG_SANEI_SCSI=128 \
scanimage -d mustek:/dev/sdga
Jesse> On bootup, it's clear the my BIOS notices the scanner (I think -- the
Jesse> screen is cleared right after it mentions a plug-and-play device that
Jesse> I assume must be the scanner). I can't find any mention of the
Jesse> scanner using setserial (would that work normally?) or by checking out
Jesse> /proc/interrupts or any other way. Should this mean anything to me?
Jesse> Or am I barking up the wrong tree?
Umh, if the scanner does not appear in /var/log/messages then the
kernel does not recognize it. See sane-scsi(5) and sane-mustek(5) for
various hints on configuring the kernel SCSI driver.
--david
-- Source code, list archive, and docs: http://www.azstarnet.com/~axplinux/sane/ To unsubscribe: mail -s unsubscribe sane-devel-request@listserv.azstarnet.com