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.
dvd and cdrom seek read errors will appear in "dmesg" as well as a lot of the common network cards failures (which aren't all that common). In the case of the drives, unless there are A LOT of seek errors, I wouldn't worry much about it.
Thanks for all replies.
Maybe I should be more descriptive.
I am building this machine that doesn't have any monitor or keyboard. I just want to output when something happen to any hardware I am using.
Seems like really hard task to do this.
I think I am gonna output to printer(only if something happen).
I could write a small program to write to the printer when any hardware failure detected.
I just don't know how to check these failures.. I guess I will buy a book and read(sigh).
Offhand about every PC BIOS I know won't let the machine boot without a keyboard attached. You can boot the machine, yank the keyboard, and go from there, but its a quirk to a lot of BIOSes.
If this thing is going to be networked, the easiest way to have error reports is have a script called from cron that checks through the various logs: /var/log/messages for instance, for certain errors, like the word "error" and then mails someone about it.
At the moment my good old pentium 133 is running smoothwall
and its booting without keyboard and i use the
webinterface to shut it down. Just had to turn it of
in the bios.
When i recall it was: halt on all errors, except keyboard
OK.. booting without keyboard is no problem since I am going to build it from picking up the board.
I am just wondering is there any (like windows) signal from hardwares when something goes wrong.
I see some program like GKRELLM that I could adapt.
GKRELLM has UI and I don't have any monitor.
I want my machine to be as simple as possible.
I can look at GKRELLM and change it to no graphic??
I don't know. ..
What I want to know is.. I think. If something happen to any hardware, it'll log to /var/log/messages. That means it knows before log the error..
How does it know? There must be something like "watchdog" for hardware in order to log the error. I think I can catch the signal before logging.