Bernhard Mogens Ege wrote:
> I have a problem using sane-1.0.2. I have compiled with debug enabled
> and have run it with debug levels set at 128 (maximum). This I did as
> sane takes a long time to complete its job (which is to list the
> scanner devices attached).
>
> This is the command:
>
> SANE_DEBUG_SANEI_SCSI=128 SANE_DEBUG_HP=128 LD_LIBRARY_PATH=lib bin/scanimage --list-devices
>
> and it gives this output (only the part is shown):
>
> [sanei_init_debug]: Setting debug level of hp to 128.
> [hp] init called
> [hp] get_devices called
> [hp] hp_read_config: hp backend v0.86 starts reading config file
> [hp] hp_read_config: processing line <scsi HP>
> [hp] hp_read_config: processing line </dev/scanner>
> [hp] hp_read_config: attach scsi HP
> [sanei_init_debug]: Setting debug level of sanei_scsi to 128.
> [sanei_scsi] searched device is /dev/sga
> [hp] hp_get_dev: New device /dev/sga, connect-scsi, scsi-request=1
> [sanei_init_debug]: Setting debug level of sanei_scsi to 128.
> [sanei_scsi] sanei_scsi_open: SG driver version: 20138
[snip]
>
>
> What seems to be the problem here?
>
> I know sane-1.0.1 worked (and still does) fine with this SCSI card
> (sym53c416) and this scanner (HP PhotoSmart Photo Scanner).
Bernhard,
There is an linux kernel issue with the sane_1.0.2/sg_2.1.38/sym53c416
combination. Trying going to:
http://www.torque.net/sg
and get the sg_2.1.39 tarball from the table and building it. That should
cure your problem. [If you look in your log (/var/log/messages) you will
probably find some nasty oopses corresponding to those pauses.]
Please tell me if that cures your problem.
For those it don't like rebuilding their kernel or modules, defining the
environmental variable SANE_SG_BUFFERSIZE to 32768 will also
fix this problem.
Doug Gilbert
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Fri Jul 28 2000 - 16:28:29 PDT