[sane-devel] scanimage cannot see Umax Astra 2100S scanner.

[abel deuring]

Russ,
> 
> Just in case I missed the intention I will repeat.
> 
> a. run 'SANE_DEBUG_UMAX=255 scanimage -d umax:/dev/scanner'
> b. run 'SANE_DEBUG_SANEI_SCSI=255 scanimage -d umax:/dev/scanner'

These nearly the comamnd I meant ;) But I'd like to see the _combined_
output from SANE_DEBUG_UMAX and SANE_DEBUG_SANEI_SCSI, so the command
would be:

SANE_DEBUG_UMAX=255 SANE_DEBUG_SANEI_SCSI=255 scanimage -d
umax:/dev/scanner

> 
> I have run each of these commands seperately several times.
> When first run after installing the scanner from the command line
> either command completes with a long pause near the end of the run
> and the scanner activity led out.

That's the situation, about which we'll hopefulls get better information
from the debug output.

> Running another command finally reports 'Device busy' and to get the led to
> light I have to repower the scanner. At all times cat /proc/scsi/scsi
> shows the scanner installed.
> 
> How can I get the output of the command written to file? 'command > (somename)'
> doesn't work for me. There is copious output, do you really want all of that
> in an email?

The '>' redirection catches data sent to stdout, while the debug
messages are sent to stderr. You can redirect stderr into a file using
'2>' instead of '>', i.e.:

SANE_DEBUG_UMAX=255 SANE_DEBUG_SANEI_SCSI=255 scanimage -d
umax:/dev/scanner 2> debug.txt

And yes, I'd indeed like to see the whole stuff ;) While most lines are
not that interesting, it is not that difficult to find the revelant
part(s) of the output. And the debug output is quite well compressed by
gzip or similar programs. So if you attach a compressed file to the
mail, nobody should complain. And if you think that the mail it is too
large for mailing list, send it only to me.

> Sorry for any misunderstanding.

never mind.

Abel