help debian sound issue after kernel upgrade

Lleb_KCir · 07-02-2005, 03:54 PM

just ran apt-get install on the newer kernel 2.6.11-1 for the intel chip on my game box at the house. after installing the headers and reinstalling the vid drivers (nvidia) i fire up KDE and get an error something about wrong permissions and the sound will continue with the 'null output'

umm i did not change my sound permissions so the kernel upgrade must of done something. how and were do i go to fix this issue?

Lleb_KCir · 07-02-2005, 06:09 PM

time to add more details.

1. i can no longer install the Nvidia drivers in my older 2.6.8 kernel as it just up and dies for what ever reason.... /rude

Code:

ray@p4ssmahome:~$ uname -a
Linux p4ssmahome 2.6.11-1-686 #1 Fri May 20 07:34:54 UTC 2005 i686 GNU/Linux

that is the current code, yes i am running a P4. it was installed via apt-get.

3. the Nvidia performance is piss pore compaired to a much slower system (slower cpu, ram speed, hd, and vid card) running the 2.6.11-1-k7 kernel and the exact same vid drive set. both downloaded today. yes it is an AMD Athlon XP 2000+

4. the exact sound error i am getting now is as follows:

Quote:

Sound server informational message:

Error while initializing the sound driver:

device /dev/dsp can't be opened (No such device or address)

side note that last reboot said not enough permissions so i set it to 777 i now have full permissions i also added my user to the audio group

The sound server will continue, using the null output device.

now when i ls that path i get the following:

Code:

ray@p4ssmahome:~$ ls -la /dev/dsp
lrwxrwxrwx  1 root root 4 2005-07-03 12:49 /dev/dsp -> dsp0

so it is there without a doubt, but if i understand what the -> is it is a symlink to dsp0, now dsp0 does not exsist or at least i can not find it.

what steps do i need to take now to get this fixed?

Lleb_KCir · 07-02-2005, 06:14 PM

ok did a little more digging and found that the dsp0 is there in the /dev directory:

Code:

p4ssmahome:/dev# ls -la d*
crw-rw----  1 root disk   10, 252 Feb 26 01:45 dac960_gam
crw-rw----  1 root audio  14,  10 Jul  3 12:49 dmfm0
crw-rw----  1 root audio  14,  26 Jul  3 12:49 dmfm1
crw-rw----  1 root audio  14,  42 Jul  3 12:49 dmfm2
crw-rw----  1 root audio  14,  58 Jul  3 12:49 dmfm3
crw-rw----  1 root audio  14,   9 Jul  3 12:49 dmmidi0
crw-rw----  1 root audio  14,  25 Jul  3 12:49 dmmidi1
crw-rw----  1 root audio  14,  41 Jul  3 12:49 dmmidi2
crw-rw----  1 root audio  14,  57 Jul  3 12:49 dmmidi3
crw-rw----  1 root disk  151,   0 Feb 26 01:41 dpti1
crw-rw----  1 root disk  151,   1 Feb 26 01:41 dpti2
crw-rw----  1 root disk  151,   2 Feb 26 01:41 dpti3
crw-rw----  1 root disk  151,   3 Feb 26 01:41 dpti4
crw-rw----  1 root disk  151,   4 Feb 26 01:41 dpti5
crw-rw----  1 root disk  151,   5 Feb 26 01:41 dpti6
crw-rw----  1 root disk  151,   6 Feb 26 01:41 dpti7
lrwxrwxrwx  1 root root         4 Jul  3 12:49 dsp -> dsp0
crwxrwxrwx  1 root audio  14,   3 Jul  3 12:49 dsp0
crw-rw----  1 root audio  14,  19 Jul  3 12:49 dsp1
crw-rw----  1 root audio  14,  35 Jul  3 12:49 dsp2
crw-rw----  1 root audio  14,  51 Jul  3 12:49 dsp3

what does the c mean at the front of the line? i know d stands for directory, but what is c.

Lleb_KCir · 07-02-2005, 06:29 PM

last step attempted made the sound no longer accessable to ANYONE.

i rebooted the box, and after that still gave same error after putting the /dev/dsp in the audio group i added root to audio group as root for a short bit had access to sound, now no account has access to sound. did i ever screw this up.

dieing for help .

harrygraham · 07-02-2005, 09:57 PM

It doesn't surprise me that the sound got mucked up when you changed kernels. Back when I was using Slackware, the only way to get my sound card to work was to:

1 Compile the kernel so all the headers would be there. (with only the sound checked as M)
2 Downoad the Alsa packages
3 Make the Alsa modules with options specific to your card
4 Use alsaconf to set up your soundcard

This has the advantage of getting all the features possible, such as recording in duplex mode etc. that you sometimes don't get with straight out of the box setups. The down side to Debian is that everything is so modular that you can replace any part of the OS, it seems. It would be a little much to ask for them to have all the Alsa drivers working no matter what kernel you pop in there. I guess the question remains - to compile the kernel or not?

I'm new to Debian and am thoroughly enjoying it, but if sound is important you may have to do things the long way.

Lleb_KCir · 07-03-2005, 12:09 AM

Code:

p4ssmahome:~# alsaconf
modinfo: could not find module snd
modinfo: could not find module snd
modinfo: could not find module snd
Unloading ALSA sound driver modules: (none loaded).
Building card database...
modinfo: could not find module snd-opl3sa2
modinfo: could not find module snd-cs4236
modinfo: could not find module snd-cs4232
modinfo: could not find module snd-cs4231
modinfo: could not find module snd-es18xx
modinfo: could not find module snd-es1688
modinfo: could not find module snd-sb16
modinfo: could not find module snd-sb8

looks like i might be up that perverbial creek...

*grumbles*

worst thing is i can get alsa drivers for the card on my MB, but the debian kernel that comes with apt-get does not install any alsa support so it would seem and i can not get past make install

/rude

basileus · 07-11-2005, 10:34 AM

Make sure you have appropriate alsa-modules installed. If your kernel is named

kernel-image-2.6.11-blabla,

you should also install

alsa-modules-2.6.11-blabla

Same goes with the nvidia drivers.

Btw. the "crwxrwxrwx" mean that current file is a "(C)haracter device" with read/write/execute permissions for all users.

"B" mean "(B)lock device (if I remember correctly)

Hope this helps you.