Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Not just 'proc' hardware information but you should have the documented information for the hardware.
You could use 'lspci','dmidecode' or even 'lshw' if installed then you can garnish as much detailed information as possible to aid in configuring your kernel.
lspci is a utility for displaying information about PCI buses in the system and devices connected to them.
By default, it shows a brief list of devices. Use the options described below to request either a more verbose
output or output intended for parsing by other programs.
If you are going to report bugs in PCI device drivers or in lspci itself, please include output of "lspci -vvx"
or even better "lspci -vvxxx" (however, see below for possible caveats).
Some parts of the output, especially in the highly verbose modes, are probably intelligible only to experienced
PCI hackers. For exact definitions of the fields, please consult either the PCI specifications or the header.h
and /usr/include/linux/pci.h include files.
dmidecode is a tool for dumping a computer's DMI (some say SMBIOS) table contents in a human-readable format.
This table contains a description of the system's hardware components, as well as other useful pieces of infor-
mation such as serial numbers and BIOS revision. Thanks to this table, you can retrieve this information without
having to probe for the actual hardware. While this is a good point in terms of report speed and safeness, this
also makes the presented information possibly unreliable.
The DMI table doesn't only describe what the system is currently made of, it also can report the possible evolu-
tions (such as the fastest supported CPU or the maximal amount of memory supported).
SMBIOS stands for System Management BIOS, while DMI stands for Desktop Management Interface. Both standards are
tightly related and developed by the DMTF (Desktop Management Task Force).
lshw is a small tool to extract detailed information on the hardware configuration of the machine. It can report exact memory configuration, firmware version, mainboard configuration, CPU version and speed, cache configuration, bus speed, etc. on DMI-capable x86 or IA-64 systems and on some PowerPC machines (PowerMac G4 is known to work).
It currently supports DMI (x86 and IA-64 only), OpenFirmware device tree (PowerPC only), PCI/AGP, CPUID (x86), IDE/ATA/ATAPI, PCMCIA (only tested on x86), SCSI and USB.
You can control each command via options, so 'man command'. Notice the utility of dmidecode & lshw.
Don't forget the manufacture hardware information documents that are available for a user.
You can even use your 'dmesg' for information to show things as recognized & configured for a working kernel. 'proc' is great but I also like to use other commands to aid in setting things up for the '.config' for a kernel.