public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] motherboard died?
Date: Thu, 15 Jan 2009 04:19:52 -0600	[thread overview]
Message-ID: <496F0DC8.6020701@gmail.com> (raw)
In-Reply-To: <496F0BC8.2030401@genestate.com>

Matt Harrison wrote:
> Dale wrote:
>> Matt Harrison wrote:
>>> Hi all,
>>>
>>> A few weeks ago there was a discussion about audio interference when
>>> running 3d applications.
>>>
>>> Well mine kept getting worse (it didn't to it at all a month ago)
>>> until I got fed up. I opened the side and (gently!) moved some of the
>>> power cables away from the data cables to see if that was a cause of
>>> interference.
>>>
>>> Well I did manage to reduce the noise by moving cables around but a
>>> couple of minutes later the machine bombed out with a big oops that I
>>> can't produce now.
>>>
>>> I didn't think it was a big problem, I thought I had just pulled an
>>> hdd cable a bit too hard or something.
>>>
>>> Now however, the machine won't post or even power up. It is an Asus
>>> Crosshair SKT AM2 nForce 590 SLI DDR2 which has a debug display on the
>>> back panel.
>>>
>>> As soon as you turn on the power to the motherboard, it displays "CPU
>>> INIT" which is the very first stage. Now trying to turn on the machine
>>> yields absolutely nothing, it just doesn't do a thing.
>>>
>>> I have removed all additional devices, just leaving 1 hdd. I've also
>>> reseated the CPU, RAM and all cables.
>>>
>>> I can't see how I could have properly killed some hardware just by
>>> moving a cable an inch to one side.
>>>
>>> If anyone has any ideas I'd be so grateful, I really don't want to
>>> have to return parts, I should be working on stuff right now :(
>>>
>>> Thanks
>>>
>>> Matt
>>>
>>>
>>
>> Is it possible that a wire come a loose when you moved it?  Maybe a
>> power wire or something?  Also, I don't think this could be it but could
>> it be that the CPU fan isn't turning?  It doesn't sound like it gets
>> that far so that may not matter.
>>
>> Dale
>>
>> :-)  :-)
>
> I think I have reseated all the cables but I am happy to try again for
> luck :P
>
>
>
>


I was thinking maybe a wire came loose inside the connector itself. 
Reseating the cables may not work.  Maybe unplug them and look inside to
see if they have come loose.  I ran into this a while back with my
central heater.  It came loose where it was crimped inside the connector
and I had to solder it back on.  May be a long shot tho.

Dale

:-)  :-) 



  reply	other threads:[~2009-01-15 10:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15  9:32 [gentoo-user] motherboard died? Matt Harrison
2009-01-15  9:47 ` Neil Bothwick
2009-01-15  9:56   ` Matt Harrison
2009-01-15 10:00 ` Dale
2009-01-15 10:11   ` Matt Harrison
2009-01-15 10:19     ` Dale [this message]
2009-01-15 10:23       ` Matt Harrison
2009-01-15 12:24 ` Dan Cowsill
2009-01-15 13:01   ` Matt Harrison
2009-01-15 13:24     ` Dan Cowsill
2009-01-15 22:30       ` David Relson
2009-01-15 22:48         ` Paul Hartman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=496F0DC8.6020701@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox