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.
Hi!
I´ve just compiled and successfully install my first usable kernel (2.6.16)
everything works the same it did in 2.4.31, the only difference is the lack of sound under new kernel.
i have VIAŽ VT1612A inbuilt audiocodec which worked perfectly under old kernel.
now alsaconf can´t detect it...
what can be the point here?
With the 2.6 series you need to be aware that you should compile your sound modules from the kernel (ie: in make menuconfig) or you will need to recreate the sound module package that Slack uses by default. I personally prefer compiling it all from my kernel, but, different strokes and so on =)
So, have you selected your sound modules in your kernel?
when configuring new kernel i checked that alsa is installed,
i can run alsaconf from the command line, but it doesn´t want to detect my sound card.
when i configured 2.6.16 (before compiling) soundconf looked like that:
Almost sure this will help, maybe you're only missing PCI section http://www.gentoo.org/doc/en/alsa-guide.xml
beware of gentoo's distro specifics, Glad we don't need them in Slack. gl
thanks, i was probably missing the driver from the pci section (i have inbuilt soundcard so i thought this section is not for me :-), now i see very similar device in there, so i am going to install it now)
I have slack10.2, kernel 2.4.31 and a Intel ICH6 Family PCI soundcard(on a asus laptop). After recompiling kernel, the sound disappeared. I decided to recompile again the kernel paying attention to the sound drivers... When i got the make menuconfig operation in the Sound Section there was no OSS or ALSA sections, only a bunch of drivers... actually there was something with the OSS but no ALSA... well, i ended up modprobing my sound driver at startup in rc.alsa (i had to change a line there, because linux wouldn't detect automatically my i810_audio driver) .. my question is: why there was no ALSA or OSS section like i've seen on some screenshots?
I have slack10.2, kernel 2.4.31 and a Intel ICH6 Family PCI soundcard(on a asus laptop). After recompiling kernel, the sound disappeared. I decided to recompile again the kernel paying attention to the sound drivers... When i got the make menuconfig operation in the Sound Section there was no OSS or ALSA sections, only a bunch of drivers... actually there was something with the OSS but no ALSA... well, i ended up modprobing my sound driver at startup in rc.alsa (i had to change a line there, because linux wouldn't detect automatically my i810_audio driver) .. my question is: why there was no ALSA or OSS section like i've seen on some screenshots?
linux 2.4 doesn't come with alsa... only linux 2.6 does... so basically to get alsa with linux 2.4 you *need* to get the alsa source code from http://www.alsa-project.org/ and then build it yourself... of course, on slackware it's quite easy to do, cuz you have the build scripts already provided by patrick...
i actually installed alsa just yesterday... before that i was using OSS for sound... i just used the alsa-driver, alsa-lib, and alsa-utils SlackBuild scripts from slackware 10.2, but i replaced the 1.0.9b tarballs with the 1.0.10 ones from alsa-project.org (and did the respective version adjustments to the scripts of course)...
i haven't recompiled my kernel yet (it's not necessary) but i plan to do so today, eliminating the OSS options i had there, as they are pointless now... AFAIK you just need to have the CONFIG_SOUND option set and nothing else in order for your 2.4 kernel to work with the "third-party" alsa drivers...
i am using linux 2.4.33-pre2, by the way, cuz there's been like way too many bugfixes since the release of the 2.4.31 which shipped with slackware 10.2...
PS: after you compile/install alsa, make sure you comment your old OSS modprobes from /etc/rc.d/rc.modules (then unload the modules or reboot) and then run "alsaconf" as root, which will detect your sound card and then prompt you to make the necessary adjustments to /etc/modules.conf for you... you don't need to touch anything in /etc/rc.d/rc.alsa...
PS2: compile and INSTALL alsa-driver before compiling alsa-lib... then compile alsa-utils last... i didn't compile alsa-oss as i have no need for it now...
PS3: make sure that when you compile your alsa packages you are running the kernel that you want to use them with...
thanx a lot, win32sux...
for the moment i use the sound driver as a module... i think i will wait till slac 11 comes out and then try alsa there... or i should play with it...
I just upgraded from 2.4.31 to 2.6.16.2 and I can't find any ALSA drivers to load. The latest seems to be 2.6.15. How can I get audio support?
When you say compile it into the kernel, what exactly do I have to do? I have been recompiling my 2.4 kernel for months now getting it just right and I've always reinstalled the alsa drivers after.
When you say compile it into the kernel, what exactly do I have to do?
it means that instead of building the option as a separate module, you build it inside the kernel (nothing to modprobe)... i've never compiled linux 2.6, but on linux 2.4 this is done by setting the option to "*" instead of "m" in menuconfig... it's probably the same for 2.6... when you look at your .config you should be able to see options like FOO=y and BAR=m, meaning FOO was built into the kernel while BAR was built as a module...
Quote:
I have been recompiling my 2.4 kernel for months now getting it just right and I've always reinstalled the alsa drivers after.
yeah, but linux 2.6 comes with it's own alsa, unlike 2.4, with which you compile it on the side...
BTW, i'm pretty sure 2.6 still gives you the option of opting for the alsa drivers from alsa-project.org if you want...
There is no need to compile alsa tools as a standalone package for 2.6 kernel. You should compile ALSA support into the kernel (IMHO, it's the best), there is an option for it. Look carefully and you won't miss it.
Last edited by Alien_Hominid; 04-08-2006 at 02:39 PM.
Cool, thanks for that. I copied the 2.4 kernel .config file to use with my 2.6 menuconfig, and for some reason it didnt compile alsa at all. No wonder sound wasnt working! 1 quick compile and now its fine.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.