[SOLVED] Slackware64-current Kernel 184.108.40.206: No sound on CLI and in Browsers
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Slackware64-current Kernel 220.127.116.11: No sound on CLI and in Browsers
I just upgraded my Slackware64-current version to the latest kernel 18.104.22.168. 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
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 22.214.171.124 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:
No supported PnP or PCI card found.
Would you like to probe legacy ISA sound cards/chips?
Then I did
# kdesu systemsettings
and navigated to the multimedia section. Both hardware sound sources were there, and clicking on the "Test" button gave sound from the Intel HDA onboard sound.
Finally, I tried
# play postgresql.wav
(a small wave file that tells how to pronounce PostgreSQL).
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).
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, 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.
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 126.96.36.199 --- 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.