From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Cc: Alex Schuster <wonko@wonkology.org>
Subject: Re: [gentoo-user] My PC died. What should I try?
Date: Tue, 28 Aug 2012 23:21:09 +0200 [thread overview]
Message-ID: <3001606.K5Lv976dz7@energy> (raw)
In-Reply-To: <503D30C7.1000209@wonkology.org>
Am Dienstag, 28. August 2012, 22:57:43 schrieb Alex Schuster:
> I wrote:
> > Well, all I can do now is to get a new board and see if things will be
> > okay then.
>
> This took longer than expected. The board I wanted (the same I already
> have) was not available, I had to order it. Strange, there is only one
> that has the features I want - AMD3+ chipset, four memory banks, USB 3,
> and on-board graphics.
>
> So I had to wait. And when it became available, I wondered if it might
> be the processor instead that has the problem, so I let the PC shop
> diagnose CPU and board. This took until today, and they confirmed it was
> the board indeed, not the CPU. Fine, I bought the board, installed it in
> the PC, and guess what - it doesn't work. On the first boot I saw some
> BIOS status messages, hard drives and such, but the keyboard did not
> react, and then it did not boot, I got a black screen only. And on
> subsequent tries, with everything (2 ISDN cards, 4 hard drives) except
> for the DVD drive removed, the screen does not even turn on. All fans
> spin, and the DVD-ROM tray opens when I press the eject button. That's
> all. No keyboard LEDs.
>
> This sucks. Is it a faulty board again? Is something (the PSU?) killing
> the board once I turn the thing on? What will happen when I have the
> next board and try again? Argh.
so - instead of changing the PSU, the obvious culprit, you got a new board AND
USED THE SAME PSU?
I am just saying - one faulty PSU fried three of my boards. Enermax... will
never buy again.
The fans spin, so not all hope is lost. Keyboard, ps/2? usb?
But before you do anything else, change the PSU.
--
#163933
next prev parent reply other threads:[~2012-08-28 21:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 7:50 [gentoo-user] My PC died. What should I try? Alex Schuster
2012-08-17 8:25 ` meino.cramer
2012-08-17 9:39 ` Alex Schuster
2012-08-17 9:07 ` Volker Armin Hemmann
2012-08-17 18:16 ` Alex Schuster
2012-08-17 19:12 ` Paul Hartman
2012-08-17 19:41 ` Alex Schuster
2012-08-28 20:57 ` Alex Schuster
2012-08-28 14:23 ` Edward M
2012-08-28 22:02 ` Paul Hartman
2012-08-28 22:08 ` Michael Mol
2012-08-28 22:57 ` Paul Hartman
2012-08-28 21:21 ` Volker Armin Hemmann [this message]
2012-08-29 11:46 ` Alex Schuster
2012-08-29 0:15 ` Peter Humphrey
2012-08-29 0:28 ` Michael Mol
2012-08-29 0:37 ` Alan McKinnon
2012-08-29 0:43 ` Michael Mol
2012-08-29 1:57 ` Alan McKinnon
2012-08-29 0:29 ` Alan McKinnon
2012-08-29 1:04 ` Dale
2012-08-29 1:55 ` Alan McKinnon
2012-08-29 2:20 ` Dale
2012-08-29 11:09 ` Alex Schuster
2012-08-29 1:09 ` Peter Humphrey
2012-08-29 9:41 ` Alex Schuster
2012-08-17 9:40 ` v_2e
2012-08-17 17:25 ` Alex Schuster
2012-08-17 12:33 ` Dale
2012-08-19 21:09 ` Alex Schuster
2012-08-17 17:54 ` Mark Knecht
2012-08-17 19:55 ` [gentoo-user] " Nikos Chantziaras
2012-08-17 23:27 ` [gentoo-user] " felix
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=3001606.K5Lv976dz7@energy \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=wonko@wonkology.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