From owner-freebsd-questions Tue Nov 5 15:44:46 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA03208 for questions-outgoing; Tue, 5 Nov 1996 15:44:46 -0800 (PST) Received: from burdell.cc.gatech.edu (root@burdell.cc.gatech.edu [130.207.3.207]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA03196 for ; Tue, 5 Nov 1996 15:44:40 -0800 (PST) Received: from oscar.cc.gatech.edu (cau@oscar.cc.gatech.edu [130.207.107.12]) by burdell.cc.gatech.edu (8.8.Beta.5/8.6.9) with ESMTP id SAA16373; Tue, 5 Nov 1996 18:44:33 -0500 (EST) Received: (from cau@localhost) by oscar.cc.gatech.edu (8.8.Beta.5/8.6.9) id SAA08125; Tue, 5 Nov 1996 18:44:28 -0500 (EST) From: cau@cc.gatech.edu (Carlos Ugarte) Message-Id: <199611052344.SAA08125@oscar.cc.gatech.edu> Subject: Re: Cyrix vs. Intel To: pechter@shell.monmouth.com (Bill/Carolyn Pechter) Date: Tue, 5 Nov 1996 18:44:28 -0500 (EST) Cc: dwlewis@intervista.com, FreeBSD-questions@freebsd.org In-Reply-To: <199611051442.JAA15608@shell.monmouth.com> from "Bill/Carolyn Pechter" at Nov 5, 96 09:42:32 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Well, my VESA motherboard came with the Cyrix chip -- (the 586-100) -- but > the board wouldn't run with the 586. The problem was it would recognize > and identify the Adaptec 1542 controller and SCSI drives -- but wouldn't > read/write the busmastering controller. IT worked fine with the IDE > C: drive (dos/os2). I dropped a 486/DX2 66 in and it all works. > With internal and external cache off -- it worked SLOWLY... and not from the > OS/2 boot mgr... I had the same problem, but I believe the blame lies with the manufacturer of the motherboard and not Cyrix. In my case, the motherboard was even listed as one of the "golden" certified mobo's for the 5x86... Basically, it didn't like the combination of a high bus/CPU speed, a DMA busmaster (1542CF), and a write back cache. Lowering the bus speed from 40 MHz to 33 MHz (and thus the CPU from 120 MHz to 100 MHz) was one way to get around it. Disabling the cache (ugh! might as well use a 486-33...) was another. Carlos -- Carlos A. Ugarte cau@cc.gatech.edu Author of PageMage, a virtual desktop util for OS/2 http://www.cc.gatech.edu/people/home/cau/ If you understand what you're doing, you are not learning anything