What does "cat /proc/asound/modules" give you? If it lists two different modules, maybe the driver you don't want is loading before the good one, causing alsa to pick the bad one as the primary. In which case you might just be able to fix that by placing the following in /etc/modprobe.d/modprobe.conf: "options module_name_here index=-2" which should make the bad module load after the good one. That happened on my system, and this fix worked perfectly for me. -- Andy On Thu, Dec 2, 2010 at 5:45 PM, Samuel Martín Moro <faust64@gmail.com>wrote:
I added this .asoundrc:
pcm.!default { type hw card 0 }
ctl.!default { type hw card 0 }
It fixed at least a problem: I've no more warning about snd_pcm_dmix_open. But, still no sound while banshee's operating...
On Fri, Dec 3, 2010 at 1:22 AM, Samuel Martín Moro <faust64@gmail.com
wrote:
I've seen that. But I did not seen anything about using a specific output of the card. as I only have one detected device, how can I set HDMI as default output? (or: how can I see my graphic card as a audio device too?) Is it that 'bindings' keyword, that's not explained on the wiki?
2010/12/3 Cédric Girard <girard.cedric@gmail.com>
On Fri, Dec 3, 2010 at 12:06 AM, Samuel Martín Moro <faust64@gmail.com
wrote:
What can I do? Setting HDMI as default (only) output? How to do so? Wait for a patch? Is it a kernel-related bug? Or with nvidia driver? Would that even fix the banshee/browser troubles accessing device?
You can control Alsa routing with the asoundrc [1] config file.
[1] http://alsa.opensrc.org/.asoundrc
-- Cédric Girard
-- Samuel Martín Moro {EPITECH.} tek5 CamTrace S.A.S (+033) 1 41 38 37 60 1 Allée de la Venelle 92150 Suresnes FRANCE
"Nobody wants to say how this works. Maybe nobody knows ..." Xorg.conf(5)
-- Samuel Martín Moro {EPITECH.} tek5 CamTrace S.A.S (+033) 1 41 38 37 60 1 Allée de la Venelle 92150 Suresnes FRANCE
"Nobody wants to say how this works. Maybe nobody knows ..." Xorg.conf(5)