Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
05-18-2006, 11:17 PM
|
#1
|
Member
Registered: Nov 2005
Location: Ottawa, Canada
Distribution: none yet
Posts: 96
Rep:
|
Can't start my Athlon 4000+
Specs:
AN8 SLI mobo
Athlon 4000+ 2.2ghz cpu
ATI RADEON 800XL pci-E video card
I give my computer power and things seem ok. when i press the power button it turns on for a fraction of a second and then turns back off. I read the dual seven segment display on my mother board, the POST code is 8.3. and i get the old school Morris code beep, 1 long followed by 1 short. I looked up the POST code in my manual. 8.3. is "save all data in stack back to CMOS".
here is what i have tried already to solve it on my own:
Flashed the BIOS
dissembled the ENTIRE computer and reassembled in on my desk, (not in the case, just bare on the desk) in case it was somthing to do with a short somewhere (like a screw on the mobo or somehting).
I am not currently running linux on this system (i'm sorry i know....) but this problem has nothing to do with OS.
CAN ANYBODY HELP PLEASE?
I personnally am thinking right now that my cpu is cooked. But i have never overclocked it before or ever, but I also never really turn off my system so it never gets a break, and I live in Ottawa, Canada. So it can get kind hot up here some days.
anyways please tose some advise my way. ANYTHING. I really don't want to admit that my cpu is toast before i have to. If you need anymore info from me just ask for it and i'll be more than willing to give it out for some help with this problem.
Thanks guys and gals,
ALEX CHISHOLM
|
|
|
05-19-2006, 12:07 AM
|
#2
|
LQ Addict
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian stable
Posts: 5,908
|
You could try running memtest86 to verify that RAM is/is not the problem. I have it on my SuSE install cd; it's on my Knoppix cd; it's included in my Debian iso which I downloaded and burned today, so you may have in on your Slackware install media. It's best to run memtest from cd (before the system is booted and using RAM).
There is also a utility called cpuburn. Warning: it will stress test the cpu, and may cause damage to other components because of temperatures generated during the test.
www.google.com/linux, search words "cpu testing" may turn up other utilities.
|
|
|
05-19-2006, 12:26 AM
|
#3
|
Member
Registered: Nov 2005
Location: Ottawa, Canada
Distribution: none yet
Posts: 96
Original Poster
Rep:
|
bigrigdriver, don't take this the wrong way but, did you read my initial post??? My computer only powers up for a FRACTION of a second, then powers off and gives me the post and beep codes. how exactly do I run MEMTEST if i can't turn it on at all??
like I said, no offense, maybe i just didn't make myself clear in my initial post.
|
|
|
05-19-2006, 01:04 AM
|
#4
|
LQ Addict
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian stable
Posts: 5,908
|
Memtext86 runs from the CD, if it's in the drive when you power up. Hopefully, your BIOS is setup to poll the cd drive before hard drives. You should then see options: install, boot from cd, memtest86, etc. Also hopefully, the boot process hasn't progressed to the point that the system balks and you can run memtest or other diagnostics from cd before the crash.
The point here is diagnostics. If the cd doesn't get you to the point of being able to run memtest, you have diagnosed part of the problem, even if you don't know what the problem is. Pass that on to your local computer repair techie.
If you can't get the cd to display the menu of options, I'd suggest that it's time to take the box back to whomever you bought it from, and say "fix it".
No hard feelings; no offense taken; no offense given. Just stating the facts.
Sorry if I'm not more helpful. I recently had a similar problem with a new box. Ram lasted part of one day then fried. Memtest run from the cd gave me enough info to convince the store techies to run their own diagnostics, which returned similar results. 1 Gig of ram had to be replaced (lifetime warranty, thank goodness).
Last edited by bigrigdriver; 05-19-2006 at 01:07 AM.
|
|
|
05-19-2006, 01:29 AM
|
#5
|
Member
Registered: Apr 2006
Location: Vancouver, Canada
Distribution: Slackware, Ubuntu
Posts: 168
Rep:
|
Well, it sounds like things aren't getting to the point of actually booting anything so I would suggest starting from scratch. Take everything off the board and try booting with only the CPU. You should get a POST message compaining about memory. If you don't, chances are that the CPU is shot. Next try booting with only the CPU and memory installed, which could result in a lot of error messages depending on how the BIOS steps through the boot proceedure. Also, be sure to clear the cmos by either setting the jumper or removing the battery for a few minutes.
The other possibility is a bad motherboard. With that processor it may be cheaper to try to rma the board, if all else fails, and see what happens.
Edit: Actually, upon looking at the post code for this board (assuming it is, in fact, an Abit AN8) it looks like it's hanging before it checks the RAM voltage, maybe while it checks the status of the power supply. Try testing your setup with a PSU that you know works, if possible. Hope you get it figured out.
Last edited by zytsef; 05-19-2006 at 01:49 AM.
|
|
|
05-19-2006, 04:46 AM
|
#6
|
Member
Registered: Nov 2005
Location: Ottawa, Canada
Distribution: none yet
Posts: 96
Original Poster
Rep:
|
As of right now, not possible for a new PSU, but i did Power up with out memory, or anything in....no luck, still POST code 8.3. so unless there are any other ideas out there, I'm thining (and assuming) that my CPU is toast.
ALEX CHISHOLM
P.S.
knowing my mobo is an AN8 SLI, what is the best CPU i can get??
thanks again,
Alex Chisholm
|
|
|
05-19-2006, 07:13 PM
|
#7
|
Member
Registered: Nov 2005
Location: Ottawa, Canada
Distribution: none yet
Posts: 96
Original Poster
Rep:
|
FOUND THE PROBLEM
apperantly somehow my power supply just gave out on me, so i bought a new one and everything runs as slick as ice now.
Thanks for the help though everybody!
|
|
|
All times are GMT -5. The time now is 07:22 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|