[3823] in linux-scsi channel archive
Re: PCI NCR875 Detection breakage?
daemon@ATHENA.MIT.EDU (Richard Waltham)
Thu Apr 30 17:53:24 1998
From: Richard Waltham <dormouse@farsrobt.demon.co.uk>
To: kernel@nls.net
Date: Thu, 30 Apr 1998 22:38:43 +0100 (BST)
Cc: linux-scsi@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.96.980430164656.440A-100000@vmlinuz> from "Phil's Kernel Account" at Apr 30, 98 04:51:21 pm
Phil's Kernel Account wrote:
>
> This is happening in 2.1.98 and 2.0.33
>
> First off, a quick overview of the Tekram DC390F's behaviour at boot.
>
> BIOS POST.
> Blah. Stuff.
> Tekram DC390F Bootthingy
> F2 or F6 for config..
> Depending upon configuration, it will follow one of two steps at this
> point.
> - Probe each ID, 0 through 15.
> - Probe each ID, starting at 0, and probe each LUN, starting at 0.
> If no disks found, "BIOS NOT INSTALLED"
>
> So, it won't install BIOS with just a cd-rom attached. Okay? Now that
> that's clear...
>
That's OK.
> Hanging off my DC390F;
>
> ID0: Pioneer DRM-624x SCSI Changer
> ID1: IBM DCAS 2.0G HDD
> ID2: Toshiba 2x SCSI CD-ROM
>
> BIOS *IS* installed.
>
Right as there is now a hard disk attached.
> dmesg time!
>
> scsi : 0 hosts.
> scsi : detected total.
> early initialization of device whitehole is deferred
> Evaluating net profiler cost ...49 units
>
> Now, I've never seen this 'whitehole' thing. I suspect it has something to
> do with the DC390F. Anyways, it's NOT detecting with the NCR drivers. Any
> ideas at this point? It looks to me like it's not handling something
> correctly.
>
> Bus 0, device 10, function 0:
> SCSI storage controller: NCR 53c875 (rev 3).
> Medium devsel. IRQ 9. Master Capable. Latency=32. Min Gnt=17.Max
> Lat=64.
> I/O at 0x6200 [0x6201].
> Non-prefetchable 32 bit memory at 0xe1020000 [0xe1020000].
> Non-prefetchable 32 bit memory at 0xe1021000 [0xe1021000].
>
> There it is in /proc/pci, so it's just not picking up at boot. Any ideas?
> This is driving me nuts! :(
>
The ncr53c7,8xx driver does not support the 53c875. Use the ncr53c8xx
(ncrBsd2Linux) driver. This is probably why the controller is not detected.
Enable support for nvram and disable Symbios compatibility mode when
selecting the driver options with make config etc.
This is based on my DC390W which if using Symbios drivers _could_ be set up
as a DIFFERENTIAL controller, although this will not happen if Tekram
drivers and/or bios are used. If the hardware configuration is similar to
the DC390W there is a hardware incompatibility with Symbios standard drivers
which will set up the controller as a differential device and the controller
will then hang when attempting to detect devices.
The ncr53c8xx driver takes care of this incompatibility and sets up the
Tekram cards correctly if the Tekram card has nvram and support for the
nvram is enabled when configuring compile options and I have used the DC390W
with genuine Symbios 875 controllers in the same machine without problems.
The latest ncr53c8xx drivers can be found at ftp://gwyn.tux.org/pub/roudier/
along with boot disk images and a very useful readme file.
Bye for now
Richard
> -Phil R. Jaenke (kernel@nls.net / prj@nls.net)
> TheGuyInCharge(tm), Ketyra Designs - We get paid to break stuff :)
> Linux pkrea.ketyra.INT 2.0.33 #15 Sat Apr 18 00:40:21 EDT 1998 i586
> Linux eiterra.nls.net 2.0.33 #15 Fri Apr 17 00:22:13 EDT 1998 i586
> - Linus says for 'brave people only.' I say 'keep a backup.' - :)
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.rutgers.edu
>
--
Richard Waltham | Work: richard@digtalinterface.demon.co.uk
At home in | Home: dormouse@farsrobt.demon.co.uk
Southampton UK | 100421.1276@compuserve.com
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.rutgers.edu
