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.
NOTE -- Other articles date from three or more years back... forever in internet time.
Can someone direct me to a details description of how linux hardware detection works? I need some understanding and lack the knowledge to read kernel and driver code and discover some details. Any help will be valuable and appreciated.
I run Linux Mint-12 (derived from Ubuntu 11.10) which is a Debian family distro so that you have more context. I know that each distro family has its own details.
I understand some behavior at the tree-top level:
power-on does hardware init; parts wake up
something causes some BIOS code to run
BIOS knows some and learns some hardware details
BIOS code loads first parts from boot device
first parts know some and learn some about hardware
"events" start dealing with found hardware
first parts load second parts from boot device
second parts add smarts to event processing
full system running -- devices come and go at end-user discretion
The "dynamic kernel module" process loads device drivers for found hardware. How do we get from HARDWARE_INIT to LOAD_MODULE( "moduleName" )?
Once loaded, do the events originate in the driver or does whatever loaded the driver throw the events when it see successful load and init completed?
I have hardware that works as advertised with win-dose, but that linux does not seem to grok well. (I get some behavior that is different, less, poor, on linux compared with win-dose.)
Lastly, if I must read about the kernel or boot loaders or elsewhere, can someone offer suggestions for recommended places to start? Are there blueprints or specs or similar before I start reading code?
Thanks for the reading references. Like much in this open community world, one needs some knowledge before one can ask reasonable questions. I have hopes for The Linux Documentation Project as a clearing house and go-to point to find 'yellowBrick==1' on the road to information.
If you know of other documentation collections, would you kindly mention those in a follow-up post?