From owner-freebsd-hackers Sun Oct 19 19:58:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA20542 for hackers-outgoing; Sun, 19 Oct 1997 19:58:58 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from postoffice.onu.edu (postoffice.onu.edu [140.228.10.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA20529 for ; Sun, 19 Oct 1997 19:58:47 -0700 (PDT) (envelope-from n-ludban@onu.edu) Received: from austin.onu.edu (austin.onu.edu [140.228.10.1]) by postoffice.onu.edu (8.8.5/8.8.5) with SMTP id WAA18391 for ; Sun, 19 Oct 1997 22:58:30 -0400 (EDT) Date: Sun, 19 Oct 1997 22:58:34 -0400 (EDT) From: Neil Ludban To: freebsd-hackers@freebsd.org Subject: NCR 53c875j support? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I've ruled out everything I could think of on this problem, and what's left points to a question about the ncr driver for -hackers. I'm trying to get FreeBSD 2.2.2-RELEASE to recognize a Diamond FirePort40 SCSI adapter, which uses the NCR 53c875j chip. A borrowed Asus PCI-SC875 is recognized correctly on the same system (53c875 chip, no j). I looked through the ncr code and found the identification numbers for different chip numbers, but didn't see anything about the 875j or even different revisions of other chips. Can anyone tell me if this should already work (I got a bad card, or a messed up BIOS), or explain where to start to add support? According to Symbios' web site, the j suffix means it "supports JTAG boundary scan for onboard testing." I assume that if the current driver were to recognize it, it would act like a plain 875, which would be good enough for me. I've double checked all the BIOS settings, moved cards around, and removed everything except the PCI video card (Graphics Blaster, CL5462 chip). The motherboard is a HOT-433, with 486 PCI/ISA BIOS from AMI (copyright 1993), and UMC 8881/8886 chipset. The only thing I have not done is install Win95 to verify that the card works with its own drivers. A possibly related problem is that having both SCSI cards installed at once, or the Asus with a PCI NIC (ed2, RealTek 8029) causes the boot to hang after the imasks line. The next thing should have been the BIOS disk geometries. FWIW, the geometry of the SCSI disk is correct for either controller. Thanks for any help-- --Neil Here'e the BIOS message from the FirePort40: Diamond Multimedia Systems, Inc. SDMS (TM) V 4.0 PCI SCSI BIOS Copyright 1995, 1996 Symbios Logic. FirePort40 SCSI Host Adapter DIAMOND-4.03.08c And here's the pci section from dmesg after a boot -v with the 875j: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.2-RELEASE #0: Thu Oct 2 20:49:53 EDT 1997 nludban@austin2.onu.edu:/usr/src/sys/compile/TIGGER Calibrating clock(s) ... i8254 clock: 1193365 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CPU: AMD Am5x86 Write-Back (486-class CPU) Origin = "AuthenticAMD" Id = 0x4f4 Stepping=4 Features=0x1 real memory = 33554432 (32768K bytes) avail memory = 30351360 (29640K bytes) pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x80009040 pcibus_setup(1a): mode1res=0x80000000 (0x80000000) pcibus_check: device 0 1 2 3 4 5 6 7 8 9 10 11 12 is there (id=008f1000) Probing for devices on PCI bus 0: configuration mode 1 allows 32 devices. pci0:12: NCR/Symbios, device=0x008f, class=storage (scsi) int a irq 11 [no driver assigned] map(10): io(fc00) map(14): mem32(ffbebf00) map(18): mem32(ffbea000) vga0 rev 1 on pci0:13 mapreg[10] type=0 addr=ffbec000 size=4000. mapreg[14] type=0 addr=fc000000 size=2000000. chip0 rev 4 on pci0:16 chip1 rev 14 on pci0:18:0 pci0:18:1: UMC, device=0x673a, class=storage (ide) [no driver assigned] map(10): io(ffe0) map(14): io(fff0) map(18): io(ffa8) map(1c): io(ffa4) map(20): io(ff90) pci0: uses 33570816 bytes of memory from fc000000 upto ffbeffff. Probing for devices on the ISA bus: