Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!gatech!swrinde!elroy.jpl.nasa.gov!decwrl!netcomsv!netcom.com!hvozda From: hvozda@netcom.com (Eric S. Hvozda) Subject: Re: FreeBSD 2.0R fails on npx 387 Message-ID: <hvozdaD0KpuC.FGA@netcom.com> Organization: NETCOM On-line Communication Services (408 261-4700 guest) References: <T54mwc2w165w@oasys.pc.my> <3brhji$apt@pdq.coe.montana.edu> <3bviv1$28p@idefix.eunet.fi> Date: Sat, 10 Dec 1994 02:34:59 GMT Lines: 20 In article <3bviv1$28p@idefix.eunet.fi>, Bror 'Count' Heinola <count@snafu.muncca.fi> wrote: > Then you haven't been listening hard enough. I know that I've > reported a few times that FreeBSD didn't work with my 386SX/ > IIT 387SX combination. 1.0 didn't, 1.1 didn't, 1.1.5 didn't, > 2.0-ALPHA didn't, don't know about 2.0-release because I > junked that motherboard and bought a 486DX2/80. :) There are a set of 386 chips out there with a documented problem that involves a 387 and a page hit; it locks the CPU dead and a power reset is required. Intel has even published a way to distinguish these chips from other 386 chips. This info can be found in most PC repair/hardware books. > NetBSD didn't work either, but Linux did. Does linux do demand paging? I dunno... -- Ack! Creek, not creek; Pop not soda; Car needs washed...