*BSD News Article 99219


Return to BSD News archive

Newsgroups: comp.sys.ibm.pc.hardware.chips,comp.unix.bsd.freebsd.misc,comp.hardware
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!DIALix!melbourne.dialix.com.au!seeware!usenet
From: mark@putte.seeware.DIALix.oz.au (Mark Hannon)
Subject: Re: sporadic problems with FreeBSD 2.2.2-box
Content-Type: text/plain; charset=us-ascii
Sender: usenet@seeware.DIALix.oz.au (Charlie Root)
Nntp-Posting-Host: putte.seeware.dialix.oz.au
Organization: Private FreeBSD site
Message-ID: <ED0590.HC8.L.doorway@seeware.DIALix.oz.au>
References: <868191978.12011@dejanews.com>
Mime-Version: 1.0
Date: Tue, 8 Jul 1997 13:24:36 GMT
Lines: 52
Xref: euryale.cc.adfa.oz.au comp.sys.ibm.pc.hardware.chips:157301 comp.unix.bsd.freebsd.misc:44107

Hi there,

In article <868191978.12011@dejanews.com>,
	dburr@POBoxes.com writes:
> I am having weird problems with my new FreeBSD 2.2.2 machine.
> 
> CPU: Intel i486DX2/66 oveclocked to DX2/80 (i.e. the bus is running at
> 40MHz)
> 
> * CPU and overclocking: This is probably the problem, no?  This CPU
>   belongs to a friend of mine, who ran it overclocked to 80 using Win95
>   and Linux, with no problems (but he has a different motherboard
>   altogether).  Maybe I should just bite the bullet and either live with
>   66MHz or get a DX4/133 or something.
> 

I would suggest that you try to bring the clock back to 33MHz.  I
had similar problems getting an AMD3/120 Mhz chip to work.  My
motherboard refused to behave itself running at 40Mhz, dropping
it back to 33Mhz and I haven't had a problem since (over a year
ago).




> * Memory: I discovered while roooting around in the system that my memory
>   was EDO.  When looking at the motherboard manual, it does not mention
>   anything about EDO.  I heard some very scary stories about using EDO
>   memory in a non-EDO motherboard, that it could cause hardware failure,
>   fry your memory chips, etc.  Can anyone supply more information about
>   this for me?  And could this really be causing my problem?

No idea.

> 
> * PCI and PCI BIOS: This is my first PCI system.  And I know next to
>   nothing about PCI.  Nor do I know about any of the dozens of BIOS
>   settings (the motherboard manual did not shed any light on this).  Could
>   a mis-configuration thereabouts be causing my problems?  FYI, I did set
>   bus timings, wait states, etc. to "default" (auto-configure) settings.
> 

This should be OK as long as you are using defaults.

/mark

-- 
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| Mark Hannon,| FreeBSD, Free Unix for your PC | mark@seeware.DIALix.oz.au|
| Melbourne,  | See http://www.freebsd.org     | Unsolicited commercial   |
| Australia   |                                | email not welcome!       |
+-=-=-=-=-=-=-+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+