Return to BSD News archive
Xref: sserve comp.sys.intel:12985 comp.os.386bsd.misc:2396 Newsgroups: comp.sys.intel,comp.os.386bsd.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!dog.ee.lbl.gov!ihnp4.ucsd.edu!library.ucla.edu!csulb.edu!csus.edu!netcom.com!raveling From: raveling@netcom.com (Paul Raveling) Subject: DMA bug? Intel/Pentium vs BSD Message-ID: <ravelingCp22z4.9zK@netcom.com> Organization: NETCOM On-line Communication Services (408 241-9760 guest) Date: Sat, 30 Apr 1994 04:54:40 GMT Lines: 33 In trying to configure a new system to run bsd386 on a an Intel Pentium motherboard (Baby-AT, BP5D60AT), and have what appears to be a DMA-related problem. The key question is... -- Is the problem in the Intel motherboad? -- Is it in bsd386? -- What else do I need to know? Symptoms are software detonation early in trying to install bsd386, usually leaving hash on the display that's typical of rampant memory clobber. It happens with 16MB installed on the mother board, but not with 8 MB. (I expect to need 16MB immediately and to add more RAM later... 8MB isn't a viable option except possibly as a stopgap.) Symptoms are identical on two different specimens of the Intel motherboard, and I've heard that it doesn't happen on one or more non-Intel motherboards that use the same chip set. So far it suggests a high severity bug but it's not clear yet whose bug it is. If this sounds familiar and you know more about it than I do. I'd be radically grateful for any additional info and advice. ------------------- Paul Raveling Raveling@netcom.com