Return to BSD News archive
#! rnews 3338 bsd Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!news.vbc.net!alpha.sky.net!news.sprintlink.net!news-chi-13.sprintlink.net!news.mathworks.com!newsfeed.internetmci.com!in3.uu.net!ott.istar!istar.net!van.istar!west.istar!n1van.istar!van-bc!unixg.ubc.ca!rover.ucs.ualberta.ca!scanner.worldgate.com!news.insinc.net!econ4.econnect.net!dave@econnect.net From: "Matthew Mung" <matthew@econnect.net> Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: Strange message on older BSDi system Date: 24 Aug 1996 23:55:56 GMT Organization: Matthew Mung Lines: 63 Message-ID: <01bb9216$f6f667e0$53d632cc@matthew.econnect.net> References: <4vhsfcINNop5@duncan.cs.utk.edu> NNTP-Posting-Host: 204.50.214.83 Mime-Version: 1.0 Content-Type: text/plain; charset=CN-BIG5 Content-Transfer-Encoding: 8bit X-Newsreader: Microsoft Internet News 4.70.1132 Hi, I do not know it is the reason. Whatever you change on any EISA system (same as PS/2 MCA system) you have to run the system configuration utility for your system. Otherwise, you system cannot recognize any new and changed hardware. And it will crash every 5 mins. It is normal ;> Matthew ---------------------------------------------------------------- Matthew Mung ^u^ | eConnect Network Manager | Smart Building Advanced Internet Sevices Phone Language Inc. | www: http://www.econnect.net/ ---------------------------------------------------------------- eConnect Calgary eConnect Montreal eConnect Toronto 1-800-826-6137 1-800-826-6135 1-800-826-6131 ---------------------------------------------------------------- JOHN FARMER <jfarmer@cs.utk.edu> 次寫入到主題 <4vhsfcINNop5@duncan.cs.utk.edu>... > Ok, > > I know that this is an older system (BSDi v1.1) but it really can't be > taken down long enough to build a 2.x system... > > It's a 486dx50 on an EISA motherboard with the Opti chipset. 8 30-pin simm > slots. Up until recently, it had 16mb of memory (4, 4x9-60 sims). I > then added memory to it (4 more, 4x9-60 simms) and while the new ram passes > POST, I keep getting the the following messages during boot: > > Aug 22 02:31:38 sabre kernel: > Aug 22 02:31:38 sabre kernel: NMI port 61 b0, port 70 ff > Aug 22 02:31:44 sabre root: Configuration changed: > Aug 22 02:31:44 sabre root: 36c36 > Aug 22 02:31:44 sabre root: < NMI port 61 a0, port 70 ff > Aug 22 02:31:44 sabre root: --- > Aug 22 02:31:44 sabre root: > NMI port 61 b0, port 70 ff > > I'm also getting "random" re-boots and more than "normal" core-dumps > of applications. > > All of this does seen to be tied to the new memory, but I'm trying to pin > it down so I can swap them for replacements if need be. I've tried moving > the new simms around, but the above msgs stay the same. Any ideas? > I would boot a dos floppy & run a ramtest, but it appears that the A: > drive died sometime in the last year (the last time it was used...). > > Please reply to Jfarmer@cs.utk.edu or jfarmer@goldsword.com. > > Thanks > John > > > -- > John T. Farmer, Jr. jfarmer@cs.utk.edu > Full-time Daddy, Some-time Grad Student, Ask me about Internet > Full-time wage slave, Wood butcher when I can. Access in East Tenn. > My son's hero's are Capt. Jean Luc Picard, Norm Abrams, and Mr. Rogers! >