HP Computer - MotherBoard or Cpu fried? How can i tell?
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
umm when i installed the driver for windows, it did not work, but immediately something wierd happened, the disc drive started to act wierd. go here there are 2 avi videos of what started to happen, don't know if it is due to the driver or something else, seeing as it happens in windows, in linux, and during boot / power off etc. (of course not when the system is powered off.), what do you think the problem is?
i'm leaving that system off over night, by the way Crito, i didn't even use the modem... thanks for all the help, it would be great to get that LAN working, but if not, i think i saw some cheap cards at a local store here in El Salvador, thanks again, couldn't of done it without your help. If i continue with drive issues i may post here again. Thanks,
I missed my oppurtunity to help out... oh, well. Here's a list for anyone, that may have this problem in the future.
Some additional information: (for future reference)
First of all, power supplies will 'crow-bar'. Meaning, they will shut themselves off if they sense a short. The only way to reset this crowbar, is to unplug the a/c cord for a while (10 sec's or so). Otherwise, it won't come back again until you do. Your power supply is probably still good. The way to see if the power supply is in fact crowbarring, is, with a 'reset' powersupply, watch the rear fan (through the metal cage of the PS). When you hit the power button, the fan inside the ps will 'jump' (appear to want to turn, but stop immediatly). This is a crowbar.
Next, CPU's rarely go out, compared to a motherboard. To test a system as was initially indicated in this thread, one should remove everything from the Motherboard. Everything -except the CPU and heat sink (without a heatsink, the CPU will stop functioning even before it has a chance to post because of heat). Also, the system will not post if no processor is in the board. ALso, make sure the power supply is only connect to the motherboard, not any drives, etc).
At this point, your power supply should start up, and the speaker output should give a loooong beep, followed by another looong beep. (you keep you speaker plugged in right?)
This is a memory failure (you have removed your mem sticks).
Next, insert mem and repeat power on. You will then get some beeps (long, short, short). This is video (lack of). Some video firmware is written to give you this beep if no monitor is plugged into the card (ie: in case of onboard vid).
Next, plug in video card. Repeat... (you should see video at this point, but will get a beep(short,short) becuase no keyboard. Keep adding until you get a crowbar.
The whole idea here, is to start from scratch and work your way up. I wouldn't neccesarily remove the motherboard from the metal foundation (or even the chassis) unless it still crowbar's with just the CPU.
The most common things that cause crowbar's are;
Misconnected floppy drive power connectors (what's a 'floppy drive'?)
Bad periphial (ie: modem ).
Self assembled computer that has metal chassis /screw lugs shorted to the Motherboard somewhere.
Note: if the power supply won't reset when pulling power plug, there's a glass fuse internally that could have blown.
In addition, before trying this, it's wise to reset the bios by using the jumper method, or just removing the battery (and shorting the batt terminals). The reason for this, is the system could have accidentally been configured for wrong clocking scheme. Also, sometimes, its neccesary to 're-seat' the CPU, in case of bad contact with the zif socket.
(I used to design MB's back in the slot-1 days. Man those were fast...)
Only addition is on many asus mb's the when i have had problems in the past with seemingly fried mb's the recommendation from asus was to remove everything (including processor) and clear the bios, then power on and off the system. The support lines explaination was that the bios needed to detect the mb type. Don't ask me why unless they use a general bios for a few differing types of mb's .