DMC390 and Astra 1220 scsi



Hi,

I am using linux kernel 2.6.22.2 with the tmscsim driver for
a Tekram DC390(T) scsi card that is connected to a Astra
1220S scanner using a new DB25 to HPD50 cable. I get the
following error on boot up (dmesg) or using "scsiadd -s"
and the scanner is not initialized.

----------------------ERROR-------------------------------

SCSI subsystem initialized
scsi 0:0:5:0: DC390: Abort command (pid 69)
DC390: SRB: Xferred 00000000, Remain 00000000, State 00000040, Phase 05
DC390: AdpaterStatus: 00, SRB Status 00
DC390: Status of last IRQ (DMA/SC/Int/IRQ): 0080c020
DC390: Register dump: SCSI block:
DC390: XferCnt Cmd Stat IntS IRQS FFIS Ctl1 Ctl2 Ctl3 Ctl4
DC390: 120000 42 06 50 00 06 17 48 08 84
DC390: FIFO: 12 00 00 00 24 00
DC390: Register dump: DMA engine:
DC390: Cmd STrCnt SBusA WrkBC WrkAC Stat SBusCtrl
DC390: 00 3df27f6d 207c0113 00000000 ffffffff 00 031b4d00
DC390: Register dump: PCI Status: 0200
DC390: In case of driver trouble read Documentation/scsi/tmscsim.txt
DC390: Aborted pid 69
DC390: Illegal Operation detected (00c0c020)!
DC390: SRB: Xferred 00000000, Remain 00000000, State 00000040, Phase 05
DC390: AdpaterStatus: 00, SRB Status 00
DC390: Status of last IRQ (DMA/SC/Int/IRQ): 00c0c020
DC390: Register dump: SCSI block:
DC390: XferCnt Cmd Stat IntS IRQS FFIS Ctl1 Ctl2 Ctl3 Ctl4
DC390: 120000 42 00 c0 00 07 17 48 08 84
DC390: FIFO: c0 00 00 00 00 00 00
DC390: Register dump: DMA engine:
DC390: Cmd STrCnt SBusA WrkBC WrkAC Stat SBusCtrl
DC390: 00 3df27f6d 207c0113 00000000 ffffffff 00 03080000
DC390: Register dump: PCI Status: 0200
DC390: In case of driver trouble read Documentation/scsi/tmscsim.txt
scsi 0:0:5:0: scsi: Device offlined - not ready after error recovery
----------------------------------------------------------

I would be grateful if you could kindly help me identify and
or fix the problem.

The tmsscim.txt documentation does mention in case of problem
with ASTRA 1220S scanner "Sync Negotiation" must be disabled
but I am not sure how this is done.

sincerely
thomas

.



Relevant Pages

  • Re: help me with SCSI ID and scanner
    ... SCSI is definitely not hot-swapable. ... Turn the scanner on BEFORE the PC. ... the driver it came with, but the computer won't recognize the scanner. ... > NT SCSI driver installation ...
    (microsoft.public.windowsxp.hardware)
  • Re: Kodak Digital Science Scanner Problem
    ... SCSI devices do not have to use ... ASPI today. ... use the Windows SCSI API too, but very few scanner drivers were rewritten to ... ASPI was the classic interface between the Adaptec SCSI driver ...
    (comp.periphs.scanners)
  • Re: Addressing a SCSI film-scanner - SUCCESS!
    ... There are two scsi connectors on the back of the scanner, ... documentation does not make it clear which one I should use. ... README.tmscsim (it is included in the driver distribution and can be found ... I have had somewhat similar problems with a Umax 1200S SCSI scanner. ...
    (Fedora)
  • Re: Addressing a SCSI film-scanner - long, sorry.
    ... You could try "rmmod tmscsim" and then do the modprobe ... I believe that it is the correct driver. ... Hardware Browser could see an attached scanner. ... SCSI chip AM53C974A, which ties in with the info I got from tailing messages. ...
    (Fedora)
  • [PATCH 18-rc2] Fix typos in /Documentation : N-P
    ... Again, if you're not gonna do synchronization with disk drives (dang, ... -the kernel. ... There are two options specific to PSX driver portion. ... The driver uses the settings from the EEPROM set in the SCSI BIOS ...
    (Linux-Kernel)