Olivier Sessink wrote:
>
> Hi all,
>
> did anyone found problems when switching to 2.4 kernels?
>
> I have a HP scanner on a sym53c860 scsi card:
> scsi0 : sym53c8xx - version 1.6b
> Vendor: HP Model: C5110A Rev: 3701
> Type: Processor ANSI SCSI revision: 02
> Detected scsi generic sg0 at scsi0, channel 0, id 6, lun 0, type 3
>
> When running, I get this error (both 2.2 and 2.4 kernels):
> sym53c860-0-<6,*>: target did not report SYNC.
>
> however, on 2.2 kernels xsane just continues scanning, but on 2.4 kernels
> (tested 2.4.2) it is followed by this error (and xsane aborts):
>
> scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 6, lun
> 0 Read (6) 00 00 80 00 00
> sym53c8xx_abort: pid=0 serial_number=965 serial_number_at_timeout=965
> scsi : aborting command due to timeout : pid 0, scsi0, channel 0, id 6, lun
> 0 Read (6) 00 00 80 00 00
> sym53c8xx_abort: pid=0 serial_number=966 serial_number_at_timeout=966
> sym53c860-0: restart (scsi reset).
>
> Other scsi devices work without any problem (tested: CD reader and writer)
> with kernel 2.4.2, only the scanner doesn't.
>
> Does anyone have a good idea? What changed in 2.4?
The SG driver changed. But the guilty one is me; I used a too short
timeout value for the new SG driver. In sanei/sanei_scsi.c, look for a
line like
req->sgdata.sg3.hdr.timeout = 10000;
(line 1892 for Sane 1.0.4), and change it to
req->sgdata.sg3.hdr.timeout = 1000 * 10 * 60;
Abel
-- 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 : Wed Feb 28 2001 - 15:40:57 PST