Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!pipex!sunic!news.funet.fi!news.eunet.fi!KremlSun!satisfy.kiae.su!kiae!relcom!elvisti!store!office.elvisti.kiev.ua!stesin From: stesin@elvisti.kiev.ua (Andrew V. Stesin) Subject: Re: FreeBSD 2.0R fails on npx 387 X-Newsreader: TIN [version 1.2 PL2] Sender: usenet@store.elvisti.kiev.ua (USENET subsystem) Nntp-Posting-Host: office.elvisti.kiev.ua Organization: Electronni Visti InformAgency (ElVisti) Message-ID: <D0IHD0.2LM@store.elvisti.kiev.ua> References: <T54mwc2w165w@oasys.pc.my> <3brhji$apt@pdq.coe.montana.edu> <3bviv1$28p@idefix.eunet.fi> <3c29jb$mif@pdq.coe.montana.edu> Date: Thu, 8 Dec 1994 21:36:33 GMT Lines: 37 Hi, Nate Williams (nate@bsd.coe.montana.edu) wrote: : 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. : Ahh, I had assumed 387 == Intel 387. All I know is that certain 387 : clones work, and others don't. Which ones work and which don't I can't : remember anymore, and my article implied that all 387 worked, when I : meant all Intel 387s. Sorry for the confusion. As about the NPUs. I can add that the piece of stone marked as "ULSI" didn't work, btw it _seemed_ to be working but later the machine falled asleep totally and silently, without any visible reasons! Replacing it with Cyrix chip did the job. That story was my headache, and now it has become my experience :) : Nate : -- : nate@bsd.coe.montana.edu | FreeBSD dude and all around tech. : nate@cs.montana.edu | weenie. : work #: (406) 994-4836 | Unemployed, looking for permanant work in : home #: (406) 586-0579 | CS/EE field. -- With best wishes -- Andrew.