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.
Just built a new PC, got it up and running with Slackware 9.1, and compiled a working 2.6.7 kernel for it. However, I have a few issues:
1. Though I configured module autoloading into the kernel, only agpart and ide-scsi load. I have to manually loadthe other modules I need after bootup. Looking at rc.modules, I notice that it is commented out, except for agpart and ide-scsi. Can I just uncomment the lines for the modules I need or is there more involved?
2. After manually loading the proper drivers for my sound card(SB Live 5.1), I tried alsaconf and was greeted with a message saying that it can't find any cards. However, if I go to alsamixeer, the card is there. The sound works with certain things(xmms, xine), but not with others(AIM). I'm very confused.
3. Any other things I ought to watch out for when moving from 2.4 to 2.6? All I've done so far is simply compile the kernel and booted it up.
1. I guess you're not running hotplug, so the solutions is to uncomment those lines on rc.modules
2. Maybe when compiling the kernel you selected OSS instead of ALSA? The best aproach to get alsa running ok is to select sound support on the kernel without selecting alsa or oss, and then compiling and installing alsa-driver from their page.
3. I can't think of any right now since i moved long ago, but there are different things, i guess you'll ask when u discover them
For some reason in Slack 9.1, installing a new kernel messes with ALSA. What I ended up doing was compiling a kernel with ALSA support, and the approprate sound card drivers as modules, then forced it to load the sound card driver module with rc.modules(as apposed to how it normally loads them). It was kind of ghetto, but sound worked.
Happily, however, the problem seems to be fixed in Slackware 10.0.
Originally posted by gbonvehi
2. Maybe when compiling the kernel you selected OSS instead of ALSA? The best aproach to get alsa running ok is to select sound support on the kernel without selecting alsa or oss, and then compiling and installing alsa-driver from their page.
That worked, I think. I'm having random locks and crashes that I am currently investigating, which may be ALSA related. So, to anyone else having problems with ALSA after going with 2.6.7, try just enabling the generic sound support in the kernel, and just installing ALSA manually.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.