Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1204 comp.os.linux:56064 Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!sunic!isgate!veda.is!adam From: adam@veda.is (Adam David) Newsgroups: comp.os.386bsd.misc,comp.os.linux Subject: Re: FYI.. benchmarks on linux and 386bsd Message-ID: <CEq8q0.M3A@veda.is> Date: 11 Oct 93 09:51:21 GMT References: <28tn7i$fl8@usenet.INS.CWRU.Edu> <CEH3Dp.A7I@dragon.dsh.org> <1993Oct6.184325.11583@finbol.toppoint.de> <750282279.25432@minster.york.ac.uk> Organization: Veda Systems, Iceland Lines: 19 al-b@minster.york.ac.uk writes: >386BSD will only boot off the harddisk if the internal cache is disabled AND the >external cache is disabled AND the turbo button is disabled. To be quite frank, your motherboard is garbage. It would be possible for 386bsd to jump through hoops (and take a performance hit) to run on it, just like I presume Linux does, but you would be better off with a motherboard that has working cache hardware. Sometime later, it is likely that the current versions of *BSD will support broken hardware, but not yet. In the meantime, make sure motherboards do caching correctly and make sure IDE cards handle things correctly. Otherwise you will see nothing but grief. I have been through both of these pitfalls and now have a stable *BSD system that is running on _working_ hardware. The bad hardware cannot be returned to the store, but someone will want to run DOS on it. -- adam@veda.is