LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-10-2005, 07:26 PM   #1
Macky
LQ Newbie
 
Registered: Apr 2005
Location: Stockholm
Distribution: Slackware 10.2, 2.6.15 kernel
Posts: 28

Rep: Reputation: 15
Alsa problems, 2.6 kernel


Hi, I have seen alsa drive some people crazy, and now it is my turn...

Here is the situation. Installed Slackware 10.2 with 2.4 kernel. I then compiled and installed my custom 2.6.14 kernel, configuring yes to alsa support, and my soundcard. Also installed udev and hotplug before I rebooted. Making sure udev is executable. So, after reboot everything is fine, except that there is no sound.

I run alsaconf, and it seems to find my soundcard. It writes some lines to modprobe.conf. Then I run alsamixer to tune the settings, and get "function snd_ctl_open failed for default: No such file or directory". And when starting KDE I get the message "Error while initializing the sound driver: device /dev/dsp can't be opened (No such file or directory)".

My lsmod:

Module Size Used by
snd_pcm_oss 48320 0
snd_mixer_oss 17024 1 snd_pcm_oss
uhci_hcd 31184 0
i2c_i801 7660 0
ehci_hcd 29800 0
usbcore 110624 3 uhci_hcd,ehci_hcd
snd_intel8x0 30048 0
snd_ac97_codec 93596 1 snd_intel8x0
snd_ac97_bus 1760 1 snd_ac97_codec
snd_pcm 82440 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 21412 1 snd_pcm
snd 46084 6 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 7584 1 snd
snd_page_alloc 8456 2 snd_intel8x0,snd_pcm
yenta_socket 24492 1
rsrc_nonstatic 11776 1 yenta_socket
pcmcia_core 36368 2 yenta_socket,rsrc_nonstatic

As far as I can see, the 2.6 kernel autoloads the correct modules for my soundcard. The problem seems to be that there are no sound devices created by udev in the /dev directory. So I then tried to create these devices by hand with help of the snddevices script found in the alsa driver source. Then I got no errormessages anymore, but still, no sound could be heard. And after a reboot, the devices were no longer there, of course. Back to square one again.

I have read a bit about reinstalling alsa-drivers, utils, and libraries after a custom kernel compile. However, what exactly does the alsa-drivers package do? Are they not just the alsa kernel modules for all soundcards? Which I configured and compiled in the kernel already. Look at my lsmod, the modules are there and loaded.

What do I need to do? This really drives me crazy...

Thanks for any help provided!

Last edited by Macky; 11-10-2005 at 07:27 PM.
 
Old 11-10-2005, 07:30 PM   #2
freakyg
Member
 
Registered: Apr 2005
Distribution: LFS 5.0 and 6.1
Posts: 705

Rep: Reputation: 30
add root and your users to the "audio" group.........
 
Old 11-10-2005, 07:46 PM   #3
Macky
LQ Newbie
 
Registered: Apr 2005
Location: Stockholm
Distribution: Slackware 10.2, 2.6.15 kernel
Posts: 28

Original Poster
Rep: Reputation: 15
Thanks, but it did not change anything. I still get the mentioned error messages.
 
Old 11-10-2005, 09:00 PM   #4
rkelsen
Senior Member
 
Registered: Sep 2004
Distribution: slackware
Posts: 1,748

Rep: Reputation: 159Reputation: 159
Re: Alsa problems, 2.6 kernel

Quote:
Originally posted by Macky
I have read a bit about reinstalling alsa-drivers, utils, and libraries after a custom kernel compile. However, what exactly does the alsa-drivers package do? Are they not just the alsa kernel modules for all soundcards? Which I configured and compiled in the kernel already. Look at my lsmod, the modules are there and loaded.
You are right. You don't need the alsa-driver package if you've compiled your own kernel.

The other two - alsa-utils and alsa-libs should be installed already.
 
Old 11-10-2005, 09:13 PM   #5
Macky
LQ Newbie
 
Registered: Apr 2005
Location: Stockholm
Distribution: Slackware 10.2, 2.6.15 kernel
Posts: 28

Original Poster
Rep: Reputation: 15
rkelsen, thanks for the clarification. Wish I knew why no sound devices are created in /dev.
 
Old 11-10-2005, 09:57 PM   #6
Macky
LQ Newbie
 
Registered: Apr 2005
Location: Stockholm
Distribution: Slackware 10.2, 2.6.15 kernel
Posts: 28

Original Poster
Rep: Reputation: 15
Got the sound to work, suddenly. I manually executed "udevstart", and the neccessary sound devices got created. Sound worked perfectly in KDE after that. So I guess that for some reason, udev fails to recognize the alsa sound kernel modules at boot. Maybe because the autoloaded alsa modules are delayed in their initialization... and simply not finished by the time udev is executed?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
2.6.7 kernel and alsa problems. FLOODS Linux - Hardware 12 07-23-2004 02:49 PM
problems alsa 1.0.3 kernel 2.6.4 no sound phoenix Linux - Software 7 04-05-2004 09:34 AM
Problems with ALSA in Kernel 2.6.3 jironimo Linux - Software 7 03-14-2004 10:39 PM
Nforce sound problems with ALSA and 2.6 Kernel! britishnemesis Linux - Hardware 4 11-29-2003 08:47 PM
Could upgrading kernel 2.4.20-> 2.4.22 help w alsa and nvidia problems? wahwah Linux - Newbie 1 11-15-2003 05:29 PM


All times are GMT -5. The time now is 06:57 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration