public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Gigabyte wont boot
Date: Fri, 11 Jan 2013 21:28:18 +0000 (UTC)	[thread overview]
Message-ID: <loom.20130111T222342-630@post.gmane.org> (raw)
In-Reply-To: 50F0768E.3010000@coolmail.se

pk <peterk2 <at> coolmail.se> writes:


> Are you sure it's a new mobo and not a replacement that someone had
> problems with and "RMA'd" it (and you got it instead)? 

Newegg said it was new

> I've had one of those... I've never seen a mobo without the install manual.
> It may of course also be brand new and still be D.O.A. Or some other
> parts may be faulty/incompatible (memory modules would be my first guess)...

Ram is as spec'd:  G.skill Ares F-1866C10D-16BAB. 4 modules all
slots full summing to 32G.........

I think the mobo is BORKED....

> Btw, there seems to be two revisions of the mobo in question. At
> Gigabytes homepage you can find manuals for both.

This one is rev 1.1

I've got the parts to build 3 systems, so I'll move on to the
second one. Get it to work and verify the compoents, one system
at a time. If all else fails, it's the mobo or the CPU. Which of
the 2 will be hard to pinpoint without a hassle.


Looks like Newegg passed me a turd or 2......


James






  reply	other threads:[~2013-01-11 21:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 18:48 [gentoo-user] Gigabyte wont boot James
2013-01-11 19:21 ` Dale
2013-01-11 21:23   ` [gentoo-user] " James
2013-01-11 22:58     ` Dale
2013-01-13 21:49       ` Kevin Chadwick
2013-01-13 23:58         ` Hung Dang
2013-01-11 20:31 ` [gentoo-user] " pk
2013-01-11 21:28   ` James [this message]
2013-01-12 20:10     ` [gentoo-user] " pk
2013-01-11 22:43 ` [gentoo-user] " Bruce Hill

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=loom.20130111T222342-630@post.gmane.org \
    --to=wireless@tampabay.rr.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