DebianThis forum is for the discussion of Debian 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.
i have this very annoying problem, and am going crazy for spending hours of trial and error on this the last 2 days...
I had a debian 3.0rc2 woody install, did
to upgrade dist to sarge
Then downloaded kernel 2.6.5 source, meeting all software requirements, performed
apt-get install module-init-tools
cp arch/... blah to /boot, same for System.map and ln -s ...
But when i boot into the newly added kernel 2.6.5, no modules are loaded. When i perform a lsmod it just gives me the header with module name etc, but none is in there.
Also during boot errors are reported about eth1 being nonexistent device, same for the aliases for the terminals etc (therefore really pointing to the modprobe.conf/modconfig.conf as being the cause?)
I've found info on the net about the same problem combined with "QM_MODULES" not implemented, and this is solved by installing module-init-tools. But for those other persons installing that fixed their empty modules list, apparently for me it just fixed the error report but i still remain with the empty list...
Gonna try those later on tonight. Already upgraded to sid and then put kernel 2.6.4-1 into place and with that one is do have my modules loaded but still no network interface... gonna look up the error later