Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
I have a Promise SATA 376 controller and I have successfully
compiled the drivers. The load fine once the system has booted
and I can use the drive without problems. I would, however, like
to boot directly from the drive. After unsuccessfully trying to
compile the driver into the kernel, I am now attempting to
use initrd to load the module. I am using gentoo, and have
installed mkinitrd. It successfully creates the initrd image, and
when the system boots, I see that the correct modules are
being loaded successfully because I get the tainted kernel
warning about non-gpl code.
The system eventually hangs and the last 4 lines look like:
Freeing unused kernel 116k (not sure about this line)
insmod: a module named sr_mod already exists
insmod: a module named ft3xx already exists
Kernel panic: Attempt to kill init
Why would I get the insmod errors after both modules were
successfully installed. Initrd completes several other tasks after
the initial successful install of the two modules. It completes all
other remaining tasks in linuxrc and then gives the error. I don't
understand what could be causing this.