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.
Notices
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 just installed MD 8.2, formatting all partitions. When it boots up, at and the console it tells me kernel is 2.4.8-26. The kernel I have installed in /boot is 2.4.18-6, and the modules to be loaded from /lib/modules are in 2.4.18-6.
Due to the mismatch (I'm assuming) all modules that attempt to be loaded at boot time fail. I've edited lilo.conf and it all points to the newer kernel (the old one was from 8.1 install). I ran /sbin/lilo as root to make sure the effect of the editing worked, but when I boot, there are no changes and the old kernel is booted??
Can someone give me some help on this one?
Thanks.
I can make changes in here and they are just ignored when I reboot and see the lilo menu. For example, if I change the lable of linux to linux24186, it will still simply show up as linux.
vmlinuz and initrd are symbolic links to the 2.4.18-6 file.
Yes, I did all that, the entries are listed in the console window, but when I actually reboot, the changes aren't there.
It seems as though LILO is just not picking up any changes I make.
Looking at your lilo.conf, it appears that no matter which linux selection you choose on boot, you're loading the image /boot/vmlinuz. The question I have is who is vmlinuz symlinked to in /boot? -mk
The only kernel that existed was the 2.4.18-6. Still, it was not doing this.
Pretty much trashed my laptop, I now no longer have XP installed and won't unless I can buy a CD since they don't give out bootable CD's when you buy OEM. Spent the whole of today trying to get something back on here, so now it's 100% linux. I don't know if that's totally the best thing, but until I get my win2k cd from Australia, it will have to do.
Probably would be happy with this, if the sound would work without hassles and it was easy to play videos. I was able to watch videos using xine when logged in as root, no sound however. I can't imagine the sound problems will be fixed with a different version though. Pretty yanked, so will give it a rest for the moment, I'm sure I read something about AC97 being made workable, will see.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.