Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 03 Jul 2002 23:59:15 -0700
From:      Peter Wemm <peter@wemm.org>
To:        Chuck Robey <chuckr@chuckr.org>
Cc:        "David O'Brien" <obrien@FreeBSD.ORG>, "George V. Neville-Neil" <gnn@neville-neil.com>, freebsd-current@FreeBSD.ORG
Subject:   Re: Recommended MP development machines... 
Message-ID:  <20020704065915.8FDA2390F@overcee.wemm.org>
In-Reply-To: <20020703233926.N66398-100000@april.chuckr.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Robey wrote:
> On Wed, 3 Jul 2002, David O'Brien wrote:
> 
> > On Wed, Jul 03, 2002 at 07:43:22PM -0700, George V. Neville-Neil wrote:
> > > 	I know everyone says "they all work" but i'd like some recommendations 
    on
> > > MP machines for -CURRENT work.  I'll be ordering one this week.
> >
> > There is but _1_ dual system to get -- Tyan Thunder K7 (code name Guinness)
    .
> > http://www.tyan.com/products/html/thunderk7.html.  It comes in multiple
> > flavors, but mine is the dual-channel Ultra160, dual-3com 10/100, 5-64bit
> > PCI, 1 AGP version.  You can cheap out and not get the non-SCSI S2462NG
> > model.  Match this bad-boy up with a pair of fast Athlon `MP' (not `XP')
> > CPU's and it is a totally solid system.  Various FreeBSD committers also
> > have this system.
> >
> > There is a newer [more economic] version called the Thunder K7X.
> > http://www.tyan.com/products/html/thunderk7x.html
> 
> "more economic" is a poor way to describe it, seeing as it has all the
> features, plus (1) an updated version of the AMD mp chipset and (2) a
> fixed onboard usb port.  The K7 had a broken on-board usb (the AMD
> chipset had a PCI contention bug for the usb port, so the tin back panel
> of the board blocked out the usb, and the K7 came with a PCI usb card,
> which ate up one of your PCI slots.  The K7X has a repaired on-board usb,
> so you get that PCI slot back.

Hmmmmm.....  Do you have any details on this?  I've had occasional strange
USB-related things happen on this box.  Of course, it runs -current which
puts me into the USB danger-zone enough as it is.. but what happens when
this bug is triggered?

Cheers,
-Peter
--
Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020704065915.8FDA2390F>