Slackware64-current Kernel 2.6.32.3: No sound on CLI and in Browsers
Hi everyone,
I just upgraded my Slackware64-current version to the latest kernel 2.6.32.3. Almost everything works just fine, except that I have no sound on the command line and in web browsers, anymore. I don't get any sound out of the command line program play and Flash. For example, I have a few .wav files, that I can play with Kaffeine and Amarok, but when I try to play them with play on the command line, the program runs and displays that it plays the file, but I don't hear any sound. The same happens with XMMS, too: It displays the usual graphics showing the dynamics and the progress, but my speakers remain silent. Also, alsaconf doesn't detect my audio hardware, anymore. I have onboard sound and a Creative X-Fi PCI card. Usually both were "seen" by alsaconf. Now it tells me, that it can't identify any audio cards. On the other hand, when I go into the multimedia section of the KDE system settings, I can "Test" the audio hardware, and the onboard sound works great and I can hear the KDE welcome sound. I have already remove all packages withe 'alsa' in their name and re-installed them, including their compat32 peers, and rebooted several times. Up to now to no avail. Does anyone have a clue, what the problem is caused by? Thanks a lot, best regards gargamel |
Hi everyone,
this is just a rephrased version of my original post --- no reply received means probably that the question was unclear. Hope, it's better now. ;) Problem is after applying the recent update for Slackware64-current to kernel version 2.6.32.3 sound isn't working properly anymore. I have onboard sound plus a Creative X-Fi Platinum (yes, pretty much useless under Linux, but it's there, anyway). After the kernel upgrade I made the suggested changes to /etc/mkinitrd.conf and /etc/lilo.conf and ran mkinitrd -F and lilo, then rebooted. Everything seemed to work fine, with one exception: There was no sound from Flash in web browsers. I tried Firefox, Seamonkey and Konqueror. I tried to find out what the problem was caused by, re-installed the whole ALSA stuff (lib, plugins, utils and OSS compatibility things) and ran alsaconf. To my amazement, this is what alsaconf said: Code:
No supported PnP or PCI card found. Code:
# kdesu systemsettings Finally, I tried Code:
# play postgresql.wav Result: The file was played, but my speakers remained silent. Same with media players of all kinds: MPlayer, Kaffeine, Xine, Gxine and XMMS. But now, surprise: Watching TV or movies recorded with Kaffeine before, are played by Kaffeine with excellent sound. Also, Amarok doesn't output sound to my speakers, although it seems to play the files, except internet FM radio. E. g., I can hear Virgin radio, while I am writing these lines. So online audio streams seem to work fine, while playing audio files fails. So what can be the reason for this problem, that I get sound for .m2t files and from DVB-T television, and that I can hear online radio, on the one hand, while I don't get sound from audio files that just worked fine before the kernel upgrade? BTW, I am not sure, if the new kernel has anything to do with it, it may be a conincidence, as the sound stuff wasn't actually changed (no new ALSA version or something, as far as I can tell). Am I the only one seeing this? gargamel |
Does "lspci | grep -i Audio" display your card?
I had a sound problem here http://www.linuxquestions.org/questi...elated-768483/ that no one was able to help me with. It went away when I upgraded from 12.2 to 13.0. I never did figure it out. Here is another thread that may be useful http://www.linuxquestions.org/questi...nstall-779083/ |
I get:
Code:
# lspci | grep -i Audio Code:
# alsamixer -c 0 I have also changed priority/sequence using the trick with setting options in /etc/modprobe.d/sound to Code:
options snd_ctxfi index=-2 Code:
# cat /proc/asound/cards Regarding your links, yes, it seems to be the very same problem you described in your thread: http://www.linuxquestions.org/questi...elated-768483/ Only difference is, that I didn't have the problem a couple of days ago, before the upgrade to the latest kernel. As I said, I am not sure, if the kernel upgrade is the real cause, or if it is just a conincidence. Currently I am clueless, and would appreciate any ideas, how to track this down further. gargamel |
Finally got it, and maybe it helps you, too, Z038!
I did: Code:
# aconnect -i Code:
# aconnect -o Code:
# aconnect -x What I still don't understand, however, is why there was sound from DVB-T and internet radio. Probably I simply don't understand how ALSA works. Anyway, for me it's solved now. @Z038: I'd be interested to hear if this is of any help for you, too! gargamel |
gargamel, this seems like a promising avenue of attack, but the commands you listed didn't do the trick for me. I will play with this some more this evening.
Here's what I have, and it looks like your output: Code:
# aconnect -i Code:
# aconnect -o Code:
root@ixian1:/home/s# aconnect -x aconnect -il shows this: Code:
# aconnect -il |
Hmmm, as far as I remember, I stopped and restarted the ALSA daemon, but unfortunately I don't recall exactly at which point.
Also, sound is one of the very few areas, where a reboot sometimes seem to be help in Linux, too. ;) Otherwise I am clueless. As I said, I don't understand ALSA well enough, as it turns out. gargamel |
gargamel, what alsa daemon are you referring to? I cannot find one. alsa is part of the kernel, no? There is an rc.alsa in /etc/rc.d, but it just loads some drivers and restores settings and so forth. It doesn't support a START, STOP, or RESTART.
|
Hmm, you are probably right.
I did: Code:
# cd /etc/rc.d Code:
Loading ALSA mixer settings: /usr/sbin/alsactl restore Code:
# ./rc.alsa start Code:
# aconnect -x BTW, I did this as root. If not, I am out of ideas. Unfortunately I don't know enough about ALSA to explain why this has cured my system. All I know, is that it did. Maybe someone else can help, here? Good luck! gargamel |
Rebooting does seem to fix it for a little while. But it doesn't stay fixed. I rarely boot this machine, but I'll try it this coming weekend. If you boot frequently you may not see the problem come back either, but you might if you stay up for several weeks at a time. I'd be interested in knowing if your problem re-emerges again, and if you find that rebooting fixes it again for a time.
|
Interesting. Usually, I reboot the machine, where I had this problem, several times a week, if not daily. But occasionally it's up longer. However, the problem didn't occur before, here, but immediately after upgrading to kernel 2.6.32.3 --- but as I said, this might be a coincidence. Perhaps I can try, what happens, if I don't reboot the machines for several weeks.
gargamel |
All times are GMT -5. The time now is 01:38 AM. |