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.
I am looking for a tool to diagnose my PC/Laptop/Server in one shot and tell me exactly what is defective/broken/not-working etc.....
Is there an application or tool that I can use to know EXACTLY what hardware issues are present on the equipment?
Tested the RAM using memory test via LiveCD, but what about the other components, hard disk, video card, CPU???
But, I am NOT looking for a LiveCD version to test my hardware.
I am looking for an application or tool to install with apt-get or yum or synaptic on a machine that is already running linux.
Preferably, ONE application that can do ALL diagnostics.
Either way you will have to init the hardware independent of a running OS for certain hardware. One, testing the filesystem will require you to be in single user mode. Two, hardware tickling of a HDD sometimes requires that you are in protected mode. I can can continue but the point of having a LiveCD is to be sure that the hardware can be tested without introducing potential problems or errors.
Sure some none critical sub-systems can be checked via tools on a live system. Things like video, printers and even network interfaces but then interruption to the production(s) will be involved. Overall testing of the system on a live operating system will be very dangerous.
As for testing all hardware, the system or kernel does work at the initial start-up. Auto-recovery methods are still going to require that you have the means to physically respond after power down or modifications after corrections.
Reading your referenced link brings up several things. Shotgunning sometimes is the only solution but not the best. You can introduce other problems or possibly damage if not sure about the diagnosis. Sure if it's a obvious indicator like a popped chip or shorted component then swap will be the best choice. Sometimes the fault won't even be the obvious. Intermittent problems are the worst nightmare to diagnose.
My point to the OP is in that problems cannot always be diagnosed via a live system. Proper techniques should be followed to prevent introduction of additional errors or problems.
I've been in the field for over 40 years and still learn something new everyday. But I do follow techniques that were introduced years ago. These original techniques have been refined & polished to allow enhanced diagnostic methods that can be applied to modern technology over the years. Be it hardware or software based you must find a methodology that works for the task at hand for you. I always break things down to the simplest term or element. That way the problem can be associated and hopefully repeatable. If not then the problem is even deeper and further interpretation or diagnosis methods are required.
Somewhere I've got a diagnostic flow chart that aids in diagnosis. I've got this imprinted so I rarely have to go back to the original. It's second nature to do this now. I've been able to refine steps to be applicable to a term within the current piece that is being diagnosed.
One needs to be able to look at things holistically yet able to understand how each subsystem functions to enable the system to operate. Intrinsic knowledge of components is important but sometimes you just have to treat that subsystem as utility to the system until it's necessary to break down the subsystem if at all.