SlackwareThis Forum is for the discussion of Slackware 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.
I'm running Slack 9.1 and had been using ReiserFS when I tried to install the 2.6.4 Kernel from 2.4.22 when neither my new kernel compile or my old one from the install would boot up so I decided to re-install. This time around I used ext2 FS instead of RFS due to some various problems with it and I also changed up my partition setup yet after the install and I reboot I get my old lilo menu (It has two choices, old kernel and new) and whichever choice I select boots but it is flodded with a error throughout the process, it is as follows:
FATAL: Could not load /lib/modules/2.6.4/modules.dep: No such file or directory
I've logged in and went to check out my lilo.conf in /etc to find that it didn't hold any of the selections I was shown when the computer booted up. Does anyone have an idea where I might find the file and also if this is what is causing it to check for 2.6.4 modules instead of the 2.4.22 it actualy needs? Thanks in advance.
At boot it only reads what was put in the MBR the last time lilo.conf was installed to the MBR.
Thats a correct statement but its not very helpful. Lilo will not pay heed to any changes in /etc/lilo.conf UNTIL you run /sbin/lilo to commit the changes to the mbr, then it hoots all it wants.
To the original posters problem and module warnings, the 2.6 kernel series need updated modutils, my guess is you installed them to compile your 2.6 kernel but forgot to update them after you re-installed.
As to the lilo issue I think Cerbere has hit the nail on the head.
I've ran /sbin/lilo multiple times to no avail. Also the 2.6.4 kernel isn't even findable anymore so when the system boots it is booting 2.4.22 but thinks it is booting 2.6.4 (or so it seems). Is there a way to override the write? Again, thanks in advance.
Actually another reading of the original post does not say after he reinstalled that he reinstalled lilo to the mbr. Further he states that it boots up with his old lilo choices. This would be another indication that he did not in fact install lilo to mbr on the reinstall. In his second post he states that he ran lilo several times but still does not say that he installed it to mbr. I did see cerebre's post but thought that a website that gave a more detailed explanation might help him. I am not sure what upset you so much by this.
I can't honestly remember if I had installed lilo to the MBR on my first install as I had only been using linux for but a week back then and didn't really think about what I wanted but rather what would work.
You can tell by opening up /etc/lilo.conf. The line that says boot=/dev/hda. If it is hdax with x being a number then you installed to your root partition and not mbr. You can edit this and change to hda. Then run lilo and that will install to mbr. Hope that helps.