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.
In the Slack 11 release notes, Pat (BDFL) tells us that if we use a 2.6 kernel, that we can use a 2.4 sound driver. Question is, how do I do that.
How do I identify what I need from the
Code:
/lib/modules/2.4.33.3/build/drivers
directory and do I simply copy them to the /lib/modules/2.6.x/build/drivers directory?
My understanding is that Pat said to keep the "alsa-driver" package and "kernel-headers" from the 2.4.x kernel. So you just don't remove these packages and install the 2.6.x kernel and all should work.
My understanding is that Pat said to keep the "alsa-driver" package and "kernel-headers" from the 2.4.x kernel. So you just don't remove these packages and install the 2.6.x kernel and all should work.
Thanks for the quick response.
So the system will find them even thoughthey are not below the /lib/modules/linux-2.6.x tree? Guess I'm unclear how this works.
But they will be under that tree, because you have 2 options of getting a 2.6.x kernel.
1. - use the packages provided by Pat ( huge26.s = 2.6.17.13 or test26.s = 2.6.18 ) and ofcourse you'll have to install the 'kernel-modules*.tgz' package from either /extra or /testing directory acordingly to the kernel you've used.
2. - compile your own kernel by downloading the source from kernel.org and selecting the proper module for your sound card when configuring it so when issuing the command 'make modules_install' they will create that tree containing the proper modules.
In the Slack 11 release notes, Pat (BDFL) tells us that if we use a 2.6 kernel, that we can use a 2.4 sound driver. Question is, how do I do that.
If you use a 2.6.x Linux kernel, you must install the kernel-generic and kernel-modules packages from either testing/packages/linux-2.6.18 or extra/linux-2.6.17.13 depending on which kernel version you wish. ALSA modules for each kernel are included in the kernel-modules package.
If you use a 2.6.x Linux kernel, you must install the kernel-generic and kernel-modules packages from either testing/packages/linux-2.6.18 or extra/linux-2.6.17.13 depending on which kernel version you wish. ALSA modules for each kernel are included in the kernel-modules package.
Thanks - I did install the kernel-modules for the 2.6.17.13-smp kernel.
If you use a 2.6.x Linux kernel, you must install the kernel-generic and kernel-modules packages from either testing/packages/linux-2.6.18 or extra/linux-2.6.17.13 depending on which kernel version you wish. ALSA modules for each kernel are included in the kernel-modules package.
LiNuCe, you shouldn't guide people at installing the 'kernel-generic*.tgz' package from the /extra or /testing directory against the default 'huge26.s' without letting them know what could happen... that is if you know.
The 'huge26.s' kernel which you install at first from the CD is a complete kernel with lots of built in support (especially fs's) and a few modules (soundcards, NICs, and few others)... on the other hand if someone installs 'kernel-generic*.tgz' package it will have a small kernel with very few built in options (only ext2 and ext3 as fs's) and lots of modules. So if one would have their partitions formated as 'reiserfs' , 'xfs' , 'jfs' ... they will have an unbootable system and have to use initrd image... something that newbies don't understand very well from what I've seen and theards asking 'why, what, who' will appear all over again.
I've said it quite a few times in other threads too, please, if you tell someone to use that package make sure to let him know the whole deal (maybe he will refuse that and keep the safe 'huge26.s') or if you don't know it either, then start reading so you won't misguide someone in the future. Thanks for understanding and I'm sorry if I may sounded rude... it wasn't the intention, I just get ichy when I see that for sooooo long time we have these kernels and issues and people couldn't observe the difference by their own.
So if one would have their partitions formated as 'reiserfs' , 'xfs' , 'jfs' ... they will have an unbootable system and have to use initrd image... something that newbies don't understand very well from what I've seen and theards asking 'why, what, who' will appear all over again.
There is a README.initrd with each set of 2.6.x kernel packages : it explains why people needs a initrd image. Someone who install 2.6.x kernel packages for the first time MUST read this file : if he doesn't, he gets in trouble and he will learn from it. If he wants a system which works out of the box with minimal, manual configuration, he does not use Slackware, he must obviously uses Ubuntu or Mandriva. If he is bored to read the same questions asked over and over on a forum, he does not read that forum.
... on the other hand if someone installs 'kernel-generic*.tgz' package it will have a small kernel with very few built in options (only ext2 and ext3 as fs's) and lots of modules. So if one would have their partitions formated as 'reiserfs' , 'xfs' , 'jfs' ... they will have an unbootable system and have to use initrd image... something that newbies don't understand very well from what I've seen and theards asking 'why, what, who' will appear all over again.
This explains the problem I was having on my slack 11rc5 system. I installed kernel generic (not because of LinCE advice...) but because it was in the directory with the 2.6 kernel modules. I wonder if there needs to be more info in a readme in that directory. I've since reinstalled from scratch with v11 and followed the right path (with everyone's help. Huge26.s is doing well.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
