From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gigabyte wont boot
Date: Fri, 11 Jan 2013 16:58:14 -0600 [thread overview]
Message-ID: <50F09906.6090000@gmail.com> (raw)
In-Reply-To: <loom.20130111T211551-446@post.gmane.org>
James wrote:
> Dale <rdalek1967 <at> gmail.com> writes:
>
>
>
>> http://www.gigabyte.us/products/product-page.aspx?pid=3996#manual
> I got a second identical mobo delivered today, so now I have
> a book. Check the connectors to the Front panel, all is correct.
> The mobo is Rev. 1.1. Swapped out ram, too, just to test.
>
That's a start. lol
>> Does it beep?
> NO. Would that suggest a dead mobo? The little speaker is attached
> but does not beep or anything...... The power supply is plugged into
> the mobo correctly. It's a new power supply and cables.
It should beep even if everything is fine. I think mine gives one long
beep when all is good but do NOT take that as golden. It's been over 3
months since I rebooted. I can't recall exactly.
>> If so, is it the normal beep or a error code beep? If
>> error code, then check to see if it sheds light on the problem. I would
>> also unplug, give the connectors a good looking over then plug it back
>> up. I'd do that for everything I could.
> Yep, verified wiring 3 times. Might have a bad cable, so I'm going to replace
> them all one at a time and see if that makes any difference. The mobo
> is just not even trying to boot. No video signal to monitor.
I would remove anything I could and see if it beeps. First, get it to
beep tho. Unless it is dead, it should have some sort of beep. Remove
all but one stick of ram, video card, drives and anything else.
Basically, mobo itself, CPU and a stick of memory.
>
>> The only other thing I can think of, does the BIOS version support that
>> CPU? I have always wondered what would happen if you put a CPU on a
>> mobo that the BIOS doesn't support but would with a newer BIOS. I
>> *think* the BIOS version is on the box with the serial number and such.
> The book does say the processor must be installed. This mobo is for
> the fx8350 so something is bad. I'm gonna build up the second machine
> and see what happens....
>
> This mobo appears to be borked, right out of the box.
>
> any other ideas?
>
>
> James
>
Yea, it has to have a CPU on it to make it do something. My thought
was, what if the version of BIOS that is installed does not support the
specific CPU you have on there. I know that mine will support a lot of
CPUs IF it has the latest version of BIOS. If it still had the BIOS
that came on it, it does not see the newer CPUs. I would have to
upgrade the BIOS first then upgrade.
If all else fails, maybe it is dead.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
next prev parent reply other threads:[~2013-01-11 23:00 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 [this message]
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 ` [gentoo-user] " James
2013-01-12 20:10 ` 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=50F09906.6090000@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