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 am having a similar problem too. I have yet to find the answer but seem to have identified the source of the problem. The problem is probably the kernel. With the Slack 9 iso that I downloaded and installed I noticed that no modules were being loaded. For some reason 2 kernels were installed in /boot:
both are the same file size (the correct size for a 2.4.20 kernel) but with different md5 checks.
However kernel 2.4.18 is loaded!
uname -a says 2.4.18
the welcome message on the first tty says 2.4.18
insmod is looking for 2.4.18 modules and will not accept 2.4.20 modules - appropriately for a 2.4.18 kernel
Something important to note here is that these two kernel files have different md5 checks - but both load a 2.4.18 kernel!?!
However it is a slackware 9 install (my welcome to Slackware 9 email tells me so ;-) ). I have tried 3 different mirrors with the same results, and the md5 check out ok on each and are identical (as they should be). I'm lost as to what the problem is or more importantly what the solution is!
I managed to fix mine by copying the kernels from the CD and changing LILO to reflect it.
I used bootdisks for mine as the CD wouldn't boot, not sure what your setup was. I think the problem occured when I chose to use the kernel from the bootdisk instead of one from the CDROM. If thats what you did as well, that is probably the source of the problem.
I also had problems when loading slackware 9 from a bootdisk. The kernel loaded from the disk is 2.4.18, instead of the 2.4.20 that is installed ... this causes all kinds of problems. If anyone else has this problem and has to use a bootdisk, I would boot from a slack cd, and make a new bootdisk using the kernal that is installed on your system.