Help with Alsa Sound on Slack14
Until recently I had but one sound device on my main Slack system, an onboard Intel HDA. That suddenly changed when I upgraded from the Ivy Bridge onboard video to a real video card, an nVidia GTX 760. At the same time that I installed the new video card I also installed my old faithful ESI Juli@ PCI soundcard. I understand that I now have 3 sound devices and I have gone so far as to Blacklist both the snd-hda-intel and the snd-hda-intel-hdmi. In fact I tried blacklisting individually every snd module NOT associated with the Juli@ pci card and I'm still having problems as long as I choose to not use Pulseaudio.
Presently if I look in KDE's System Settings > Multimedia there are only 3 listings... well 4 since the maiin device is also listed as "Default". It looks like this Code:
ESI Juli@ (ICE1724) Code:
lsmod |grep snd Code:
lspci |grep audio Code:
cat /proc/asound/cards I miss "alsaconf" but I did try "alsactl init 0" which didn't help. Any help on LQ? |
You have PulseAudio installed you say? And you wonder where your sound went? I would check there first. Slackware does not install PulseAudio.
Eric |
NO! I do not have pulseaudio installed on my Slackware system. I apologize for the confusion. I should have mentioned that Pulse is default on Ubuntu and Suse and there, sound works.
It does exist on other systems (multi-boot system) until I can safely purge it. I suspected this would be a problem ahead of time as I've read about issues with HDMI, so I researched fairly carefully before I changed hardware. I didn't expect this level of hassle but then I'm probably just missing something silly I've overlooked. However I feel blinded now. Thats why I posted here. I need outside eyes. |
If you have ALSA running only with dmix, check your default output in alsamixer and see if you have a secondary device connected. If so, you'll need to setup an ALSA modules.conf file as described such as here:
http://www.alsa-project.org/main/ind...dule-hda-intel as well as an .asoundrc file for each user also described there. |
Thanks Reaper, but I've done all those things and specifically to ice1724 too. For awhile I had intended to use the Intel onboard for voice microphone detail, as in TeamSpeak etc. so I had an .asoundrc I found to do just that. I even pared that down to just Ice1724 once I had difficulties.
I've been trying to follow alsa's troubleshooting path but I feel hindered w/o alsaconf - alsactl init 0 seems awfully generic to me. The error messages I get when trying "speaker-test" or Code:
aplay -D default /usr/share/sounds/alsa/Front_Center.wav |
Well I logged in as root and found that all sound works fine so apparently I have some borked permissions or bad group assignment. I went over all my $HOME permissions making sure they were not root, and now the "aplay" command works as it should. However I'm still getting this error on speaker-test when run as user...
Code:
speaker-test |
Can you post the output of 'aplay -l'.
You can set the default card by creating the file '~/.asoundrc' with something like: Code:
defaults.ctl.card 1 |
Greetz
I've been using Jack and Ardour for many years so my .asoundrc tends to be quite a bit more complex than just the defaults, but to troubleshoot, I first tried a simple default backup style (I just rename them) and then none altogether. As requested, and as it may help someone else here is aplay -l Code:
bash-4.2$ aplay -l 1 - MPlayer 2 - Xine 3- Gstreamer Simply by putting Xine in the top spot, the test button now works as it should. Apparently some problem in MPlayer had a wide-ranging effect. The command "speaker-test" still does not work (same error message) and I have a lot of apps to check before I mark this solved, but it is looking good now... or rather, sounding good again. |
Final Note -
I can't in good conscience mark this solved because I am still having some issues which seem oddly connected to MPlayer. ( I say "oddly" because "smplayer" works now, but "mplayer" won't even launch ) Having seen some other threads about MPlayer makes me wonder if this isn't a growing problem. We shall see I guess. Unless I see activity here I intend to stop reporting since the problem is at least no longer an urgent one. Sound works properly in all I care about or for which I have an alternative. |
All times are GMT -5. The time now is 07:24 AM. |