Linux - HardwareThis 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.
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.
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....
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?
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.....
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
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.
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.
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.
>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.
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...
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152
Rep:
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. . .
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.
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
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.