From owner-freebsd-questions Wed Feb 1 10:47:51 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id KAA01794 for questions-outgoing; Wed, 1 Feb 1995 10:47:51 -0800 Received: from inet-gw-1.pa.dec.com (inet-gw-1.pa.dec.com [16.1.0.22]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id KAA01788 for ; Wed, 1 Feb 1995 10:47:45 -0800 Received: from rks32.pcs.dec.com by inet-gw-1.pa.dec.com (5.65/10Aug94) id AA20380; Wed, 1 Feb 95 09:42:01 -0800 Received: by rks32.pcs.dec.com (Smail3.1.27.1 #16) id m0rZj3P-0005M7C; Wed, 1 Feb 95 18:41 MEZ Message-Id: To: questions%freebsd.org@inet-gw-1.pa.dec.com In-Reply-To: Message from "Michael C. Newell" of Wed, 01 Feb 95 09:06:10 EST. Reply-To: gj@FreeBSD.org Subject: Re: Discouraged... Date: Wed, 01 Feb 95 17:41:19 GMT From: "gj%pcs.dec.com@inet-gw-1.pa.dec.com" Sender: questions-owner@FreeBSD.org Precedence: bulk Mike wrote: > Wasn't there a problem reported some time back with AMD 486 chips? I > don't have one so I didn't pay much attention, but I seem to remember a > thread about problems caused by a bug in the chip itself [no, I'm NOT > confusing it with the dePentia chip!] Anyway, might be worth a look > through the Email archives... This might have been me. I reported that an AMD 486DX2 didn't work in my mother board in so far that the npx probe hung. Apparently an incompatibility between the AMD chip and my MB (an i486DX2 works just fine). Since the npx probe hangs it's quite obvious if there's a problem ! Gary J.