hello everybody, > > This really looks like a SCSI problem. Maybe a bug in the 2.4.5 kernel > > SCSI driver for your controller or a problem with cabling/termination? > > you might be right with your suggestion that the problem is > a bug in the scsi-modul. i'll upgrade to the latest kernel tomorrow and > write to the list wether it helps or not.
now ive upgraded to the latest kernel 2.4.14 but sane-fined-scanner or scanimage -L cant still find the scanner. ive also tried to load the modul in async mode, but this not helps either. here is some system-output: Nov 17 09:38:01 rayman kernel: PCI: Found IRQ 11 for device 00:11.0 Nov 17 09:38:01 rayman kernel: sym53c8xx: at PCI bus 0, device 17, function 0 Nov 17 09:38:01 rayman kernel: sym53c8xx: 53c875 detected Nov 17 09:38:01 rayman kernel: sym53c875-0: rev 0x3 on pci bus 0 device 17 function 0 irq 11 Nov 17 09:38:01 rayman kernel: sym53c875-0: ID 7, Fast-20, Parity Checking Nov 17 09:38:01 rayman kernel: scsi0 : sym53c8xx-1.7.3c-20010512 Nov 17 09:38:03 rayman kernel: Vendor: MUSTEK Model: MSF-06000CZ Rev: 4.00 Nov 17 09:38:03 rayman kernel: Type: Scanner ANSI SCSI revision: 00 Nov 17 09:38:03 rayman kernel: Vendor: TEAC Model: CD-ROM CD-532S Rev: 3.0A Nov 17 09:38:03 rayman kernel: Type: CD-ROM ANSI SCSI revision: 02 Nov 17 09:38:10 rayman kernel: Attached scsi generic sg0 at scsi0, channel 0, id 1, lun 0, type 6 after a scanimage -L in the syslog: Nov 17 09:38:58 rayman kernel: sym53c875-0-<1,*>: target did not report SYNC. Nov 17 09:38:58 rayman kernel: sym53c875-0-<1,0>: COMMAND FAILED (1 ff) @ca5f3000. now i tried to load the modul in async mode: modprobe sym53c8xx sym53c8xx=sync:255 after a scanimage -L in the syslog: Nov 17 09:31:36 rayman kernel: sym53c875-0-<1,*>: target did not report SYNC. Nov 17 09:31:36 rayman kernel: sym53c875-0-<1,0>: COMMAND FAILED (1 ff) @ca76d000. Nov 17 09:31:36 rayman last message repeated 3 times Nov 17 09:31:36 rayman kernel: sym53c875-0-<2,*>: asynchronous. any more hints ? tanx, rayman.
