Motherboard Forums


Reply
Thread Tools Display Modes

K7S5A Pro Won't POST

 
 





















Eric Wolfe
Guest
Posts: n/a

 
      10-29-2004, 12:20 AM


"Buffalo" <eric(nospam)@nada.com.invalid> wrote in message

> Good job.
>
> "Eric Wolfe" <> wrote in message


> > Forgive the top posting but I wanted to follow up on my original post.

I
> > just got a notice from AMD that they are sending out a new processor.


Thanks! Now I have a new problem with the machine that I *would* have torn
down to test the duff processor. (Proving that you can't beat Fate!) I
decided to connect it to the network and when I configured it as a member of
a domain, that triggered the W2K Ctrl+alt+del login screen. The problem is
that the machine (a non-Pro K7S5A) will not recognize that key combo and
just sits there. I am sure the keys themselves work because they work if I
boot from a floppy or CD.

Another oddity is that when I tried to enable the power on from keyboard
feature, it won't turn on when I enter my password. The newer K7S5a Pro
board handles both tasks with no problem using the same Lite-On Classic
keyboard. I'm about to try swapping the Lite-On keyboard with a cheaper
"Windows" keyboard to see if that makes any difference. Has anyone
experienced these problems before?

Eric


 
Reply With Quote
 
Eric Wolfe
Guest
Posts: n/a

 
      10-29-2004, 12:50 AM
"PJX" <> wrote in message

> On Tue, 26 Oct 2004 16:40:34 -0400, "Eric Wolfe"
> <> wrote:
>
> >Forgive the top posting but I wanted to follow up on my original post. I
> >just got a notice from AMD that they are sending out a new processor.

The
> >one I returned apparently was DOA so I did the right thing in not tearing
> >down a working machine to try to test the CPU further when it failed to

POST
> >in the K7S5A. I figured if the old Duron booted with no problems, it was
> >pretty likely that the Athlon was dead.
> >
> >Eric

>
> I disagree.
>
> The quickest and easiest way would have been to stick the bad
> processer in the good board and watched it not boot.


If I had done that I STILL would have had to send the processor back to AMD.
Since it's my time, I feel it was well spent not hauling a working machine
out from under the desk, pulling all the cables, popping the case,
connecting a monitor, mouse and keyboard, popping the CPU (a process that's
caused more than one person problems that ended with a banged-up or cracked
or blown core), popping the working CPU back in, sealing it up, crawling
back under the desk, reconnecting all the cables and then testing to make
sure I didn't screw something up.

I'm sorry, but I just don't see how is that easier than taking an educated
guess that the CPU was dead, throwing it in a box, quick printing a label
from the email they sent on my Seiko and spending 2 minutes on line
arranging a USPS carrier pickup by cutting and pasting address info from the
AMD email and leaving it in the mailbox. If I was do this as a business or
even a serious hobby, I would have had a "hangar queen" (any Air Force guys
out there?) to perform such tests. The irony here is that I would have had
to do all that machine jackassing around *anyway* when the CPU failed to
boot in machine #2.

> 5 minutes max troubleshooting time and your good system is back up
> and running and you send off the bad processor.


If you can do everything I outlined above (dismounting it from the computer
desk, etc) in 5 minutes then the United Nations needs your superpowers! <g>
That's an hour job if you don't happen to have a convenient bench test
machine running with the case off and nothing gets mucked up during the
testing procedure.

Had it been a Gigabyte board or some other such MB that doesn't
automagically detect the CPU and configure itself, I might have taken those
steps. The reason I have the old, slow Duron is because I needed that to
boot the Gigabyte to change the BIOS settings to accomodate the faster chip
I had purchased for it. It was a real Catch 22 and one of the reasons I
switched to ECS. In this case, from what I have read here and elsewhere,
the default settings in the ECS BIOS would boot any chip it was capable of
running. That made it seem pretty clear that the CPU was very likely DOA.

> Time is money.


And two wrongs don't make a right, but three left turns do! (-: The best
part is I am getting a faster processor as a result of having waited a year
to finally get around to building the thing. They were out of the 2400's so
they are shipping a 2600. That will just about make up for the cost of
shipping the sucker out to them!

Eric



 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Re: S2722 will POST but not run BIOS setup or boot. The Doctor Tyan 0 11-30-2008 01:55 AM
Re: S2722 will POST but not run BIOS setup or boot. Paul Tyan 0 11-29-2008 10:11 PM
New MOBO, no POST.....what's the deal with socket 775? Marty_KN0CK Elitegroup 6 07-30-2008 03:08 PM
K7S5A has delayed POST. Googi Elitegroup 0 07-25-2007 09:38 PM
Odd problem with K7S5A BIOS/POST Mike Tomlinson Elitegroup 8 12-20-2006 10:20 PM


All times are GMT. The time now is 05:30 AM.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43