LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
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


View Poll Results: What's knackered?
Mobo - FIC AE31 0 0%
CPU - Duron 800Mhz 0 0%
something else.... 0 0%
Voters: 0. You may not vote on this poll

Reply
  Search this Thread
Old 08-08-2003, 06:08 AM   #1
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Rep: Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984
What's bit of hardware is stuffed?


right, got a duff old duron 800 and similarily low end mobo, and FIC AE31, which dispite having been running winme fineish for a few months has been a complete bugger on trying to install gentoo, possibly provoked by compiling heavy shit ....

what's happened is that during emerge glibc or something, occasionally it has hard locked, or generated a panic. After this though, NOTHING happens.... reboot... everythign spinds up, so not a power issue, but there is no successful POST and such... and no beeps either. If i remove the RAM, then the board will beep and complain, but otherwise nothing.. with NO peripherals / cards connected.

if i remove the cpu and turn it on.... nothing
if i then replace the cpu and turn it on... it (normally) loads.
sometimes it will then reboot again normally, sometimes it will die totally again.. until i remove the CPU.

So who's to blame? a shit mobo or a low end cpu? they may be cheap to replace but i'm not going to replace something that's technically ok....
 
Old 08-08-2003, 06:59 AM   #2
jharris
Senior Member
 
Registered: May 2001
Location: Bristol, UK
Distribution: Slackware, Fedora, RHES
Posts: 2,243

Rep: Reputation: 47
I would go for either dodgy CPU or heat problems personally. How hot is the CPU/memory/chipset running? Perhaps http://www.1coolpc.com is your friend in this situation?

cheers

Jamie...
 
Old 08-08-2003, 07:10 AM   #3
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Original Poster
Rep: Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984
no heat issues, cool as a long green salad vegetable... i can leave it off for hours at a time, but it still doesn't come back on without removing the cpu and replacing it again.....
 
Old 08-08-2003, 11:08 AM   #4
moses
Senior Member
 
Registered: Sep 2002
Location: Arizona, US, Earth
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152

Rep: Reputation: 50
Could you possibly have some sort of crud causing a short on the CPU pins? Take a can of compressed air and carefully clean the MB, CPU, and ZIF socket for the CPU.
Maybe a bad capacitor on the MB; try disconnecting the power cable (but leave the CPU in) and leaving it off for a while so all capacitors can discharge.
 
Old 08-08-2003, 11:39 AM   #5
kev82
Senior Member
 
Registered: Apr 2003
Location: Lancaster, England
Distribution: Debian Etch, OS X 10.4
Posts: 1,263

Rep: Reputation: 51
i dont know how likely this is but a few years ago i had some gold pinned ram and the socket it went in had zinc(i think) contacts what happend was the gold and zinc with electricity caused some sort of oxidation making a thin layer of crud on the pins which eventually built up to a perfuct insulator crashing the computer, once i removed/reset the ram chip, it cleared all the crap of the pins and it worked again for a while until enough crud built up.
 
Old 08-08-2003, 04:26 PM   #6
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Original Poster
Rep: Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984
Biggest pointer would seem to be that it's compiling heavy sh*t that has locked it each time so far anyway... ahh i'm confused.

thanks for those pointers moses.... compressed air here we come...
 
Old 08-08-2003, 04:31 PM   #7
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 72
Checked to see if the BIOS has tarded itself out? Reseting BIOS to flat defaults and setting it not to auto-detect the chip clock but setting it manually?

If the chip has to be pulled to boot it every time it sounds more like BIOS is violently stupid, especially if its running fine once its booted and BIOS is off the job.

Cheers,

Finegan
 
Old 08-08-2003, 05:56 PM   #8
Capt_Caveman
Senior Member
 
Registered: Mar 2003
Distribution: Fedora
Posts: 3,658

Rep: Reputation: 69
>Biggest pointer would seem to be that it's compiling heavy sh*t that has locked it each time

That's actually the best way to see if you have a memory defect or a short in the mb/cpu. You might have one of those weird situations where you're losing a bit here and there due to a short or bad RAM. Under normal usage, you can handle losing a bit now and again, but when you compile, you stress the hardware so much that you start losing bits to the point that it's fatal. Supposedly compiling something is a much better way to detect those types of errors; even better than "RAM testers" like memtest86. If you're really interested, check out this link , it actually has some interesting stuff on memory corruption and the weird things that cause it.
 
Old 08-08-2003, 06:42 PM   #9
finegan
LQ Guru
 
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700

Rep: Reputation: 72
oh, that reminded me, I was building a linuxfromscratch the other day and noticed that in the middle of it, for glibc, they recommend turning off CPFLAGS for the build, apparently optimizing for arch on an AMD leads to a broken glibc... dunno how much truth there is that...

Cheers,

Finegan
 
Old 08-09-2003, 12:07 AM   #10
moses
Senior Member
 
Registered: Sep 2002
Location: Arizona, US, Earth
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152

Rep: Reputation: 50
Quote:
Originally posted by Capt_Caveman
>Biggest pointer would seem to be that it's compiling heavy sh*t that has locked it each time

That's actually the best way to see if you have a memory defect or a short in the mb/cpu.
Right, if he's got something on/in the ZIF socket that expands just enough under a "small" Delta T, it could short the CPU. If he's got a slightly flaky component (like a capacitor, which isn't terribly uncommon) on the MB, it won't matter much until he starts really working the CPU.
Of course, we're working with limited data (not acid's fault), so it's going to be an interesting journey. . .
Does the crash happen at the same spot every time you try a compile (fresh after make clean)? I seem to remember having similar problems when I had some flaky memory, but that was some time ago, and I didn't have to remove the CPU. . .
 
Old 08-09-2003, 04:00 AM   #11
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,417

Original Poster
Rep: Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984Reputation: 1984
Quote:
Originally posted by finegan
oh, that reminded me, I was building a linuxfromscratch the other day and noticed that in the middle of it, for glibc, they recommend turning off CPFLAGS for the build, apparently optimizing for arch on an AMD leads to a broken glibc... dunno how much truth there is that...

Cheers,

Finegan
well each time (2 or three.. can't really rememebr) it was during glibc.... everythign else compiled fine, kernel et al... we'll have wait wait and see what i can come up with this afternoon, cheers for the tips one and all.

Last edited by acid_kewpie; 08-09-2003 at 04:13 AM.
 
Old 08-09-2003, 04:12 AM   #12
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu ; CentOS ; Raspbian
Posts: 12,613

Rep: Reputation: 69
Just to sorta "second" Fin's suggestion:
I had a dorked up glibc going, turned off my CFLAGS/CXXFLAGS and it worked like a champ.
CFLAGS="" emerge -U glibc

?

Anyway, I'm tired, just wanted to look cool and all

Cool
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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 Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
64 Bit Linux Hardware Support linux-rulz Linux - Software 7 06-13-2005 05:09 AM
I've completely stuffed up X -- help! theMonkeY Slackware 2 11-01-2004 10:04 AM
stuffed up X (or maybe stuffed up terminal) JediMasterTux Linux - Newbie 3 07-24-2004 07:08 PM
is it possible for me to achieve a 32 bit graphics with this hardware? spyghost Solaris / OpenSolaris 1 03-27-2004 05:21 AM
Really stuffed deejayqf Linux - Newbie 3 01-13-2004 06:47 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 04:04 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration