From owner-freebsd-scsi Wed Apr 7 11:27:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from carme.eclipse.net.uk (carme.eclipse.net.uk [195.188.32.33]) by hub.freebsd.org (Postfix) with ESMTP id 8B2C814FE6 for ; Wed, 7 Apr 1999 11:27:38 -0700 (PDT) (envelope-from stuart@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by carme.eclipse.net.uk (8.9.3/8.9.3) with ESMTP id TAA52761; Wed, 7 Apr 1999 19:25:21 +0100 (BST) Message-ID: <370BA37F.5ABAF8F7@eclipse.net.uk> Date: Wed, 07 Apr 1999 19:27:11 +0100 From: Stuart Henderson Organization: Eclipse Networking Ltd. X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en-GB MIME-Version: 1.0 To: "Christopher R. Bowman" Cc: "Daniel C. Sobral" , freebsd-scsi@FreeBSD.ORG Subject: Re: 3.1 problem References: <199904071845.OAA44394@quark.ChrisBowman.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>Is ncr 53c875 one of the cards not supported any longer on 3.x? If >>it is supported, any ideas on why a 3.1-RELEASE would not find any >>hard drives where a 2.2.8 has no problems? Is this generic or a custom kernel? Is the 875 listed in dmesg output of the pci bus[1]? If you have built a custom kernel, which SCSI-related devices and options have you used? (nb the scsi device is now called da - it used to be called sd - that bit me the first time I tried moving to v3 and tried to build a new kernel with the config file from v2 - obviously *not* a very good idea - at least now you probably won't even get it built properly with the console changes :) > Both my 53c875 and my 53c876 (dual channel) cards work fine > under 3.1-RELEASE using the ncr driver. I think quite a few people would have noticed if 53c8xx based cards had been broken, they seem to be very popular. Stuart [1] like: Probing for devices on PCI bus 1: ncr0: rev 0x01 int a irq 10 on pci1.4.0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message