The AM53/79C974 driver does not work correctly with the AM53C974 SCSI
system on the HP Vectra XU 5/90.
The DC390 module works just fine for this implementation, but is not
detected as such because the XU 5/90 has no DC390 BIOS (obviously). This
makes getting the system running difficult because the SCSI driver goes
into endless bus-resetting on boot. The DC390 driver works just fine, if
it is selected.
The DC390 driver appears to be a superset of the functionality provided by
the AM53/79C974 driver. If this is the case, why not disable the original
AM53/79C974 driver and make its use optional?
Alan, what do you think?
If we should switch drivers, say so and assign this to kudzu.
If not, any idea what (if anything) we should do to fix this
The DC390 is a superset, but it isnt a generic superset. I'd be wary of this
although if we can do some testing and gather more info it might be wise.
To clarify - hand selecting DC390 driver just works with no changes or errors
reported on this box ?
Correct - manually selecting the DC390 module works without errors or
modifications on this machine, where the AM53/79C974 causes endless SCSI bus
resets immediately after the drives are detected.
DC390_init: No EEPROM found!
DC390_init: Trying default EEPROM settings:
DC390: Used defaults: AdaptID=7, SpeedIdx=1 (8.0 MHz), DevMode=0x1f, AdaptMode=0
x2f, TaggedCmnds=3 (16)
PCI: Increasing latency timer of device 00:20 to 64
DC390: 1 adapters found
scsi0 : Tekram DC390/AM53C974 V2.0d 1998/12/25
scsi : 1 host.
And it works without problem.
OK I agree we should switch - for next release
What does lspci say on the system, so we know exactly
which card to associate it with?
00:04.0 SCSI storage controller: Advanced Micro Devices [AMD] 53c974 [PCscsi] (r
(Remember this is an on-board controller)
Do you have the lspci -v output?
I have included the '-vv' output below.
00:04.0 SCSI storage controller: Advanced Micro Devices [AMD] 53c974 [PCscsi]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+
Stepping+ SERR+ FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr+ DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR+
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at ff00
Ugh, there doesn't appear to be any subsystem/subvendor device
id info, so there's no way to distinguish this from other
Oh well, will be switched as of kudzu-0.90-1.