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.
If you start Firefox from the console, could not do it a clue?
I don't follow you...
I think what afreitascs is trying to say is that, if you start Firefox from an xterm or KDE Konsole, you might see some error messages that point to where the problem is.
I would check if some process is already using libasound:
I'm running out of ideas. Flash sound in Firefox doesn't work at all. In Konqueror it's lottery; sometimes it works and sometimes it doesn't. This is maddening.
Okay, check this out... I uninstalled both flasplayer-plugin and libflashsupport, then re-installed them. So check this out: flash sound now works great in Firefox, but not at all in Konqueror! Any ideas?
libflashsupport is available through slackbuilds.org and reputed to help solve no sound problems in flash. Anyway, it doesn't seem to matter... I now have no sound in either firefox or konqueror. This is ridiculous. I've never had this much trouble with a new hardware device before...
libflashsupport is a very poor substitute and is never necessary IMO...are you actually using Gnome and/or pulseaudio? Flash attempts to output to the first audio device through ALSA. Assuming nothing is locking up your sound device (by using OSS compatibility, for example) Flash should output to ALSA by default. You can try switching your sound device to the first slot and see if that makes a difference (see here for information on how to do that). This theoretically should work through .asoundrc as well so I'm not sure why it isn't. I'm not sure if the spaces between . and ! in your lines make a difference but for the record I have always used pcm.!default and ctl.!default.
libflashsupport is a very poor substitute and is never necessary IMO...are you actually using Gnome and/or pulseaudio? Flash attempts to output to the first audio device through ALSA. Assuming nothing is locking up your sound device (by using OSS compatibility, for example) Flash should output to ALSA by default. You can try switching your sound device to the first slot and see if that makes a difference (see here for information on how to do that). This theoretically should work through .asoundrc as well so I'm not sure why it isn't. I'm not sure if the spaces between . and ! in your lines make a difference but for the record I have always used pcm.!default and ctl.!default.
I'd rather eat my own buns than use Gnome or Pulseaudio. I'll uninstall libflashsupport and see what happens.
libflashsupport is a very poor substitute and is never necessary IMO...are you actually using Gnome and/or pulseaudio? Flash attempts to output to the first audio device through ALSA. Assuming nothing is locking up your sound device (by using OSS compatibility, for example) Flash should output to ALSA by default. You can try switching your sound device to the first slot and see if that makes a difference (see here for information on how to do that). This theoretically should work through .asoundrc as well so I'm not sure why it isn't. I'm not sure if the spaces between . and ! in your lines make a difference but for the record I have always used pcm.!default and ctl.!default.
That article you linked to looks like what I'm looking for but there's one problem... I don't have a /etc/modprobe.d/alsa.conf file. I have a /usr/share/alsa/alsa.conf, but ti doesn't look much like what's described in that article. I'll try editing the .asoundrc file, but I'd really rather set up a global solution.
Uninstalling libflashsupport and making those modifications to my .asoundrc file got everything working! I'd still like to get the alsa configuration configured globally if anyone can provide any guidance. Thanks!
That article you linked to looks like what I'm looking for but there's one problem... I don't have a /etc/modprobe.d/alsa.conf file. I have a /usr/share/alsa/alsa.conf, but ti doesn't look much like what's described in that article. I'll try editing the .asoundrc file, but I'd really rather set up a global solution.
Did you run alsaconf as root after you installed the new card?
Quote:
Originally Posted by man alsaconf
Alsaconf is a simple shell script which tries to detect the sound cards on your system and writes a suitable configuration file for ALSA. It
will try to guess what GNU/Linux distribution you're running, and will act accordingly to the standards of that distribution, if specific sup-
port is available.
Alsaconf will write a module-init-tools (or modutils) snippet which can be then used by module-init-tools (or modutils) to load the correct
parameters for your sound card.
---edit---
Add the .conf to the file alsaconf produces in /etc/modprobe.d/ or else you'll get a warning on reboot. This has been fixed in -current with an update to alsa-utils.
Last edited by disturbed1; 06-19-2010 at 08:26 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.