Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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've got a bit of a problem adding a kernel patch to my SuSE 8.2 distro, which uses 2.4.20 kernel.
I need to add the patch to allow support for Via VT8237 South Bridge chipset on my mobo.
In brief, here's what I did -
1. Patched kernel source according to Via's instructions - no problems.
2. Used default configuration, did 'make oldconfig', and checked config file. all seemed ok.
3. Edited Makefile to create a 'test' kernel / modules directory (added -test EXTRAVERSION)
4. Make dep, make bzImage, make modules, make modules_install. All went fine, without hitch and no funny messages..
5. Copied bzImage to /boot, renaming it as vmlinuz-test
6. Edited /boot/grub/menu.lst to include new kernel. I simply copied existing kernel and changed label and kernel image name.
7. Rebooted machine.
All went fine, until the following error appeared -
loading module reiserfs ...
insmod : reiserfs : no module by that name found
kernel panic : VFS : Unable to mount root fs on 03 : 03
Oh dear - I rebooted using vanilla kernel, and check locations of modules - all appeared OK.
So what's happening here? How does a kernel know where to look for modules? I'm a bit
confused. Any help would be much appreciated.
Your root filesystem is a Reiser filesystem and the module is not include in the inital ram disk. This is a kinda catch 22 the module is stored on the root file system, but the module needs to be loaded in order to read the filesystem.
Try running make install that should copy the kernel to the boot partition, build the initrd, modify grub...
mkinitrd /boot/initrd-2.4.20-test.img 2.4.20-test
and add the initrd to your grub config.