Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!cancer.vividnet.com!hunter.premier.net!newsfeed.internetmci.com!in3.uu.net!world!dfisk From: dfisk@world.std.com (David Fisk) Subject: Re: FP Message-ID: <DwwL87.C5t@world.std.com> Organization: The World Public Access UNIX, Brookline, MA X-Newsreader: TIN [version 1.2 PL2] References: <32109F45.28D3@alaska.net> <4v4a7f$au3@uriah.heep.sax.de> <321820C1.75B6@aloha.net> <321EE52B.39F5@alaska.net> Date: Thu, 29 Aug 1996 14:21:43 GMT Lines: 20 hmmm (hmmm@alaska.net) wrote: : according to my boss, he took a 387 in and out of a at&t wgs 386/25 : and that made the difference between it running or not (crashed @ : npx0). i saw it crash & then work, but didn't do it myself. : the best answer i got was that the standard FPU emulation isn't : very good, and that it's a good idea to include the other FPU : emulation (which isn't normally compiled in because of licensing) : and to rebuild the kernel. but i don't have time to chack all : that. Just checking, but when he removed the the 387 did he change the appropriate jumpers/switches to let the motherboard know that the co-processor was gone? FreeBSD might be locking up when it can't find the co-processor that it thinks should still be there. Just a thought.... Dave -- ------------------------------------------------------------------- David Fisk dfisk@world.std.com