SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
All of the above are common issues when installing Slackware with the 2.6.x kernels (huge26 or test26). The fix is simple.
The answer?
You didn't read the instructions when you chose huge26.s or test26.s and install the modules!!
'Install' plainly tells you that you must install the kernel modules in /extra/linux-2.6.17.13 (for huge26.s) or /testing/packages/linux-2.6.18 (for test26.s)
modules are the "drivers" (I know, not really) for the kernel to tell what kind of hardware you have and how to use it.
***Edited for clarification
Last edited by cwwilson721; 12-29-2006 at 01:12 PM.
Yes. The instructions about this are in the readme on the first install CD. To mount your cdrom drive at run level three to install the modules issue this command:
# mount /mnt/cdrom
then navigate to the directory where the modules are located.
cw, cw, cw... if people would actually read the instructions on the cd, read the changelogs, read the archives here or elsewhere, how many questions would there actually be here. Not to mention the information hidden on their own system in the man pages or /usr/doc section (especially Linux-How-Tos).
Well, it happened to me that I forgot to install the modules (yes, I didn't read anything), but the fix was quite obvious to me... before I even noticed any trouble I went into /extra to install the few "missing" things (like checkinstall,...), saw the kernel dir, looked into it and said: "Oh, look, I don't have the modules installed!". Upon saying this installed the package.
So: you don't really have to read a lot, just think. Nothing gets installed from extra during setup. So, if something's there, you don't have it installed by default...
I don't know if this post meets the criteria... but it should get a sticky. It's just a common oversight.
Hi,
Not an oversight! Just plain 'LAZY' or just that most people want to be spoon fed the M$ way. Slackware is not a gui based user know nothing based distro. Thankfully PV, put a lot of reference and background information into the distro.
A lot of the new users expect slackware to be like their experience with a so called 'main line linux', be it mandrake, fc or whatever. The silver spoon is not available with slackware. A little reading and effort is required to find the right tools. Then to learn how to use that tool!
Just look at most of the urgent posts on this forum. A little common sense would get most the answers that are presented via a search on LQ or google.
It's not so clear to me.
If I look on disk 1 - I see the huge26.s and test26.s kernels but no /extra
If I look on disk 2 - I see /extra with 2.6.17 directory that contains the generic kernel, modules etc. Is this the also modules package for huge26?
I am using "generic" with initrd on some of my machines but I am trying to triple boot with Ubuntu on a new box so I wanted to avoid initrd.
If I look on disk 3 there is another /extra with the ham programs etc
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,644
Rep:
The 2.6.17.13 folder you see on your second disc is the one Install the modules and maybe the kernel source from it. Don't install the generic kernel package (if you have chosen huge26.s when installing) or your chances that you have something important not compiled right into the kernel are high.
It's not so clear to me.
If I look on disk 1 - I see the huge26.s and test26.s kernels but no /extra
If I look on disk 2 - I see /extra with 2.6.17 directory that contains the generic kernel, modules etc. Is this the also modules package for huge26?
I am using "generic" with initrd on some of my machines but I am trying to triple boot with Ubuntu on a new box so I wanted to avoid initrd.
If I look on disk 3 there is another /extra with the ham programs etc
Confusing...
If you are installing the huge kernel 2.6.17.13 then you will need to install the modules located on install CD#2.
If you are installing the test kernel 2.6.18 then you will need to install the kernels located on CD#4.
Which disk does not matter. Why? I make my own install cds from the dvd, and my /extra is on disk 4.
But /extra is /extra, and /testing is /testing.
True. Point well-taken:-) Thank you for the correction:-)
My comments work for the stock CD install. Some of us don't have them new fangled dvd drives yet:-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.