[sane-devel] HP4c & Buslogic BT-958

Ray Curtis Ray Curtis <ray@ccux.com>
Sat, 24 Nov 2001 00:51:23 -0500


>>>>> "sl" == Steven Lembark <lembark@wrkhors.com> writes:

sl> -- Ray Curtis <ray@ccux.com>

>> 
>> Anyone on this list using this combination with the 2.4 kernel ? I am
>> still playing around trying to find out why sane can't seem to find my
>> scanner.
>> I have added the lines to hp.conf:
>> /dev/scanner
>> option connect-scsi
>> option disable-scsi-request
>> 
>> However it still refuses to find it with:
>> 
>> [root@bugs:/etc]/% scanimage
>> [sanei_debug] Setting debug level of hp to 255.
>> [hp] sane_init called
>> [hp] sane_init will finish with Success
>> [hp] sane_get_devices called
>> [hp] hp_read_config: hp backend v0.94 starts reading config file
>> [hp] hp_read_config: processing line </dev/scanner>
>> [hp] hp_read_config: processing line <option connect-scsi>
>> [hp] hp_read_config: processing line <option disable-scsi-request>
>> [hp] hp_read_config: attach /dev/scanner
>> [hp] hp_get_dev: New device /dev/scanner, connect-scsi, scsi-request=0
>> [hp] sanei_hp_device_new: /dev/scanner
>> [hp] scsi_inquire: sending INQUIRE
>> [hp] scsi_new: sending TEST_UNIT_READY
>> [hp] scsi_flush: writing 2 bytes:
>> [hp]  0x0000  1B 45                                            .E
>> [hp] scsi_flush: writing 7 bytes:
>> [hp]  0x0000  1B 2A 73 32 35 37 45                             .*s257E
>> [hp] scl_inq: read failed (Error during device I/O)
>> [hp] scl_errcheck: Can't read SCL error stack: Error during device I/O
>> [hp] sanei_hp_device_new: SCL reset failed
>> [hp] scsi_close: closing fd 4
>> [hp] sane_get_devices will finish with Success
>> scanimage: no SANE devices found
>> [hp] sane_exit called
>> [hp] sane_exit will finish
>> 
>> This combo used to work just fine with the 2.2 kernel and still works
>> under windows, but the I need it to work under linux if possible.
>> 
>> I am using a later kernel, just to see it that would help,
>> 
>> Linux bugs 2.4.13-0.5 #1 Sat Nov 3 15:08:02 EST 2001 i686 unknown
>> 
>> But no luck,
>> 

sl> Just for the fun of it try:

sl>     export SANE_DEBUG_HP=17
sl>     export SANE_DEBUG_SANEI_SCSI=255
sl>     scanimage -L 2>&1 | tee a;
[sanei_debug] Setting debug level of hp to 17.
[hp] sane_init called
[hp] sane_init will finish with Success
[hp] sane_get_devices called
[hp] hp_read_config: hp backend v0.94 starts reading config file
[hp] hp_read_config: processing line </dev/scanner>
[hp] hp_read_config: processing line <option connect-scsi>
[hp] hp_read_config: processing line <option disable-scsi-request>
[hp] hp_read_config: attach /dev/scanner
[hp] hp_get_dev: New device /dev/scanner, connect-scsi, scsi-request=0
[hp] sanei_hp_device_new: /dev/scanner
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_debug] Setting debug level of sanei_scsi to 255.
[sanei_scsi] sanei_scsi_find_devices: vendor=(null) model=(null) type=Processor
	bus=0 chan=0 id=4 lun=0  num=1
[sanei_scsi] lx_chk_id: 0,0  0,0  4,4  0,0
[sanei_scsi] lx_chk_devicename: matched device(direct): /dev/sg1
[sanei_scsi] get_max_buffer_size for /dev/sg1: 131072
[sanei_scsi] sanei_scsi_open: sanei_scsi_max_request_size=131072 bytes
[sanei_scsi] sanei_scsi_open: SG driver version: 30121
[sanei_scsi] sanei_scsi_open_extended: using 131072 bytes as SCSI buffer
[sanei_scsi] trying to enable low level command queueing
[sanei_scsi] sanei_scsi_open: Host adapter queue depth: 3
[sanei_scsi] sanei_scsi_open: SG driver can change buffer size at run time
[sanei_scsi] sanei_scsi_open: low level command queueing enabled
[sanei_scsi] sanei_scsi_open: using new SG header structure
[hp] scsi_inquire: sending INQUIRE
[sanei_scsi] scsi_req_enter: entered 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rb>> rcv: id=0 blen=36 dur=0ms sgat=0 op=0x12
[sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 3
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rb>> rcv: id=0 blen=36 dur=0ms sgat=0 op=0x12
[sanei_scsi] sanei_scsi_req_wait: read 64 bytes
[hp] scsi_new: sending TEST_UNIT_READY
[sanei_scsi] scsi_req_enter: entered 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rcv: id=1 blen=0 dur=0ms sgat=0 op=0x00
[sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 3
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rcv: id=1 blen=0 dur=0ms sgat=0 op=0x00
[sanei_scsi] sanei_scsi_req_wait: read 64 bytes
[hp] scsi_flush: writing 2 bytes:
[hp]  0x0000  1B 45                                            .E
[sanei_scsi] scsi_req_enter: entered 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rb>> rcv: id=2 blen=2 dur=20ms sgat=0 op=0x0a
[sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 3
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rb>> rcv: id=2 blen=2 dur=20ms sgat=0 op=0x0a
[sanei_scsi] sanei_scsi_req_wait: read 64 bytes
[hp] scsi_flush: writing 7 bytes:
[hp]  0x0000  1B 2A 73 32 35 37 45                             .*s257E
[sanei_scsi] scsi_req_enter: entered 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rb>> rcv: id=3 blen=7 dur=0ms sgat=0 op=0x0a
[sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 3
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rb>> rcv: id=3 blen=7 dur=0ms sgat=0 op=0x0a
[sanei_scsi] sanei_scsi_req_wait: read 64 bytes
[sanei_scsi] scsi_req_enter: entered 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rb>> rcv: id=4 blen=16 dur=0ms sgat=0 op=0x08
[sanei_scsi] scsi_req_enter: queue_used: 1, queue_max: 3
[sanei_scsi] sanei_scsi_req_wait: waiting for 0x8055068
[sanei_scsi] sanei_scsi.issue: 0x8055068
dev_max(currently)=10 max_active_device=4 (origin 1)
 scsi_dma_free_sectors=304 sg_pool_secs_aval=320 def_reserved_size=32768
 >>> device=sg1 scsi0 chan=0 id=4 lun=0   em=0 sg_tablesize=128 excl=1
   FD(1): timeout=600000ms bufflen=131072 (res)sgat=4 low_dma=0
   cmd_q=1 f_packid=0 k_orphan=0 closed=0
     rb>> rcv: id=4 blen=16 dur=0ms sgat=0 op=0x08
[sanei_scsi] sanei_scsi_req_wait: read 64 bytes
[sanei_scsi] sanei_scsi_req_wait: SCSI command complained: Success
[sanei_scsi] sense buffer: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[sanei_scsi] target status: 00 host status: 0007 driver status: 0027
[hp] scl_inq: read failed (Error during device I/O)
[hp] scl_errcheck: Can't read SCL error stack: Error during device I/O
[hp] sanei_hp_device_new: SCL reset failed
[hp] scsi_close: closing fd 4
[hp] sane_get_devices will finish with Success
[hp] sane_exit called
[hp] sane_exit will finish

No scanners were identified. If you were expecting something different,
check that the scanner is plugged in, turned on and detected by the
sane-find-scanner tool (if appropriate). Please read the documentation
which came with this software (README, FAQ, manpages).

sl> and see what happens. It would also be interesting to see if
sl> your /proc/scsi/sg/device_strs has anything in it that looks
sl> like an HP scanner.

[root@bugs:/root]/% cat /proc/scsi/sg/device_strs 
IBM             DGVS09U                 03B0 
HP              C2520A                  3503 
HP              C1533A                  A708 
ATAPI           CD-R/RW 4X4X32          3.DS


sl> I'm having a rather similar problem with another BusLogic
sl> card -- problem might not be the just the 958.

Don't really think its the controller since it works fine under
windows, and has a drive on it that works just fine.

-- 
Ray Curtis         Curtis Consulting         http://www.ccux.com