[wellylug] I think my motherboards gone.... :-(

[Jethro Carr]

hi brent,

I just tried the following:

Took out 1 ram chip & tried with the remain 1. Then did the same with
the other chip. With only 1 chip, the system didn't even report how much
ram there is.

I found that the whine comes from my hard disk. I unplugged it, and the
whine stopped, but the system still locks after ram check. Maybe I had
just never noticed it before.

I've also tried taking out the add in cards, including the video card.
No luck. :-(

The CPU tempature is fine, I managed to check it in the bios. (sometimes
I can get in, sometimes I can't.)

I'll have to take it into ascent tomorrow. (custom built system).

I'll get them to try diffent ram, power supply & cpu, before replacing
the motherboard.

I hope I can get it back before christmas day...

thanks to all the people who gave their ideas.


On Sun, 2004-12-19 at 11:42, Brent Wood wrote:
> > Yesterday, I turned it on. Just after grub started the kernel, the
> > system locked up. I had booted it up the day before, and I had made no
> > changes to any configuration. I turned it off & started it again. This
> > time it locked up, just after the ram test, before the drive test.
> > 
> > I've noticed a slight whiny noise too, which never existed before.
> 
> Whine suggests a cap, maybe just a fan. Try stopping each fan for a sec or two,
> to make sure it isn't a bearing whine. If you can, swap the power supply to
> make sure that isn't the problem (or the source of the whine). Ditto graphics
> card. 
> 
> Also note that you can sometimes hear memory when under load, a slight whine
> there. The whine, if slight, may be misleading, as you may not have noticed it
> until you have a problem, then you tend to notice everything!!
> 
> Depending on where you purchased the motherboard I can get a forward replacemnt
> for Gigabyte stuff, usually within a couple of hours during working hours.
> There is a local importer as well as a couple in Auckland.
> 
> Also, check the cpu temp in the BIOS as you boot. If you can get into the BIOS
> OK, & muck around for a while, then it fails after you reboot, it suggests that
> perhaps the fault is elsewhere.
> 
> So, disconnect drives, swap power supply, graphics card, if you have more than
> 1 memory module, use just one at a time.
> 
> Note that if you purchased it (shock, horror) as a system, rather than
> components, you should prob contact the supplier ASAP, as you mucking about, if
> they find out, may have warranty implications.
> 
> 
> The power down helping with a cap would apply to power supply, graphics card &
> motherboard, so while it may well be the m/b, it isn't necessarily so.
> 
> 
> I've stuck with socket 939 & Nvidia for A64 systems, socket 754 seems to be a
> very short term beast between 32 & 64 bit. AMD are already talking about
> phasing it out. Touch wood, no hardware problems yet, but A64 Linux & SATA are
> not always very friendly :-)
> 
> 
> 
> 
> Cheers,
> 
>    Brent
-- 
-- Jethro

dodocaptain at paradise.net.nz
jethro.carr at jedolinux.com

http://www.jedolinux.com
http://homepages.paradise.net.nz/jethroc
http://homepages.paradise.net.nz/jethroc/cv.html

http://www.wellylug.org.nz