From owner-freebsd-hackers Tue Jan 11 11:30:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (prism.flugsvamp.com [208.139.222.230]) by hub.freebsd.org (Postfix) with ESMTP id 4897A154B4; Tue, 11 Jan 2000 11:29:31 -0800 (PST) (envelope-from jlemon@prism.flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id NAA00549; Tue, 11 Jan 2000 13:31:23 -0600 (CST) (envelope-from jlemon) Date: Tue, 11 Jan 2000 13:31:23 -0600 From: Jonathan Lemon To: Andrew Gallatin , hackers@freebsd.org, smp@freebsd.org Subject: Re: Dell PowerEdge 2400 & RCC PCI chipset? Message-ID: <20000111133123.C409@prism.flugsvamp.com> References: <200001111922.NAA07463@free.pcs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001111922.NAA07463@free.pcs> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 11, 2000 at 01:22:49PM -0600, Jonathan Lemon wrote: > > We're thinking of purchasing some Dell PowerEdge 2400 servers. I'm a > bit nervous because the 2400 uses a non-Intel server chipset made by a > company called RCC Reliance. > > The chipset is called the "LE-64 ver 3.0". and I cannot seem to find > any info about it. The most I've been able to turn up is somebody > else looking for info. I was wondering if anybody was currently using > a PowerEdge 2400 (or any other server products with this PCI chipset) > with FreeBSD > > So -- does FreeBSD work with RCC chipsets? Is the chipset robust & > reliable? We've been badly burned a few times by buggy DEC PCI > chipsets & we're hoping to not repeat the experience with an x86 ;-) It doesn't currently seem to boot with the RCC chipset. I get the following: pci unknown vendor = 0x9005, dev = 0x00cf This is with a RCC-186566-PO3. As for stability, I have another box running Linux with an RCC-xxxx-PO2 that seems fairly stable. The RCC chips are supposed to allow better memory bandwidth @ 133Mhz. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message