*BSD News Article 54606


Return to BSD News archive

Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.uoknor.edu!news.nodak.edu!netnews1.nwnet.net!news.u.washington.edu!news.alt.net!nntp1.jpl.nasa.gov!nntp.et.byu.edu!news.byu.edu!acs2.byu.edu!news.cuny.edu!news.sprintlink.net!newsfeed.internetmci.com!in1.uu.net!EU.net!Germany.EU.net!zib-berlin.de!news.tu-chemnitz.de!irz401!theatre.pandora.sax.de!mw
From: mw@theatre.pandora.sax.de (Martin Welk)
Subject: Re: Am I having Mother Board problems? (long)
Organization: Private Site, Member of Individual Network e. V.
Message-ID: <DHz7DC.CG@theatre.pandora.sax.de>
References: <480g74$s8o@central.ro.com> <30A60969.2CAC87E8@freebsd.org>
Date: Mon, 13 Nov 1995 09:51:11 GMT
Lines: 51

In article <30A60969.2CAC87E8@freebsd.org>,
Jordan K. Hubbard <jkh@FreeBSD.org> wrote:

>This *definitely* points to a bad motherboard, bad cache or bad memory.

Jordan, IMO it is _not_ !

I have similar problems and they are drive depending.

My FreeBSD adventure started a while ago. My PC was a 386DX-40 with
128 K cache and 8 meg RAM, Adaptec 1542B SCSI host adapter, Trident 8900
based 1 meg graphics adapter, WD8013 compatible network adapter, some
serial and parallel ports. I have a Toshiba XM3401B CD-ROM, Wangtek
5150ES tape, there was a Rodime 210 meg drive, a Maxtor 245 meg drive
and a Seagate ST41200N (about 1 gig, 5.25" FH.)

I had problems like those described in the source posting and no-one
was able to explain why. Even Joerg had no idea :-)

Since then the following changed:

-	I replaced the motherboard. I have now a Soyo board, 486DX2-66,
	with 4 meg RAM on one PS/2 SIMM and 4 meg on 1 meg standard
	SIMMs.

-	I replaced the Rodime disk because it died.

-	I replaced the complete memory by one 16 meg PS/2 SIMM.

It still appears.

I believe it's a problem of that Seagate disk (it's firmware still
tells me that it was made by Imprimis) but I wonder how CRCs can be
correct and why FreeBSD doesn't take any notice.

This points to a bad motherboard, bad cache or bad memory.
But not *definitely*

I am very satisfied with FreeBSD and we're using it as a CD-ROM
server (with NFS and Samba) on our network, for two routers and
there is my private machine. In our company's network we don't
have those problems.

Bye,
    Martin
-- 
 /| /|        | /| /       \      ,,You know, there's a lot of opportunities,
/ |/ | artin  |/ |/ elk     \                 if you're knowing to take them,
                             \      you know, there's a lot of opportunities,
Meissen, Germany, Europe      \            if there aren't you can make them,
mw@theatre.pandora.sax.de      \         make or break them!'' (Tennant/Lowe)