On Mon, Dec 15, 2008 at 4:41 PM, Nick Rout <span dir="ltr"><<a href="mailto:nick.rout@gmail.com">nick.rout@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="Wj3C7c">On Tue, Dec 16, 2008 at 10:36 AM, Mary Strimel <<a href="mailto:mary.strimel@gmail.com">mary.strimel@gmail.com</a>> wrote:<br>
><br>
><br>
> On Mon, Dec 15, 2008 at 4:22 PM, Michael T. Dean <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>><br>
> wrote:<br>
>><br>
>> On 12/15/2008 04:11 PM, Nick Rout wrote:<br>
>> > On Tue, Dec 16, 2008 at 8:20 AM, Mary Strimel wrote:<br>
>> ><br>
>> >> My myth box has been running happily for 70+ days, but now after<br>
>> >> rebooting<br>
>> >> there is no sound. I don't think it's a myth-specific problem but<br>
>> >> since my<br>
>> >> hardware is similar to other myth users I hope someone here can help me<br>
>> >> -<br>
>> >> other routes have failed.<br>
>> >><br>
>> >> I have onboard Via sound using Alsa's snd_via82xx driver. I also have<br>
>> >> a<br>
>> >> PC-HDTV 5500 and a WinTV PVR 250 installed.<br>
>> >><br>
>> >> There are two weird things I noticed after the reboot (besides the<br>
>> >> eerie<br>
>> >> quiet):<br>
>> >><br>
>> >> 1) there no /dev/dsp device anymore. I think myth was using /dev/dsp<br>
>> >> for<br>
>> >> sound; the myth setting is now defaulted to "adsp" but I have no idea<br>
>> >> what<br>
>> >> that is.<br>
>> >><br>
>> >> 2) under xmms, sound *does* work if I select, under the ALSA output,<br>
>> >> "hw<br>
>> >> 1,0" but there is no sound in any other program. Alsamixer shows the<br>
>> >> Via<br>
>> >> sound controller as device 1, and all channels are unmuted / top<br>
>> >> volume.<br>
>> >><br>
>> >> I am aware that people on this mailing list have solved issues with PCI<br>
>> >> cards being recognized in a different order at boot time, but I how do<br>
>> >> I<br>
>> >> tell if this is actually the problem? I don't want to be messing<br>
>> >> around<br>
>> >> with settings in "blind" fashion and break something else.<br>
>> >><br>
>> >> Also, if I determine that it's an issue with the card order, how would<br>
>> >> I<br>
>> >> know which card "should" be detected first? And why aren't any<br>
>> >> /dev/dsp<br>
>> >> devices being created at all?<br>
>> >><br>
>> >> Any help with the ANY of the above would be much appreciated! If it<br>
>> >> matters, I have Ubuntu Gutsy 64.<br>
>> > A few preliminary tests would be to run<br>
>> ><br>
>> > aplay -l<br>
>> > aplay -L<br>
>> > ls /proc/asound (I think thats the path)<br>
>> ><br>
>> > to see what is recognised.<br>
>><br>
>> Yeah, specifically:<br>
>><br>
>> cat /proc/asounds/cards<br>
>><br>
>> where I think you'll find you have a sound card you don't know about<br>
>> (perhaps the analog capture portion of the HD-5500?). The problem is<br>
>> that the cards get different device numbers depending on when they<br>
>> initialize, so they could change at every boot. You need to lock the<br>
>> desired card to card 0.<br>
>><br>
>> Mike<br>
>> _______________________________________________<br>
>> mythtv-users mailing list<br>
>> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
>> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
><br>
> OK, I think I found on the Ubuntu forum how to force the order of the sound<br>
> cards. I'll give that a try and report back. Thanks!<br>
<br>
<br>
</div></div>probably the correct way is to write some udev rules :)<br>
<div><div></div><div class="Wj3C7c">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div>Thanks everyone! Problem appears to be solved. Apparently ubuntu lets you force the order by adding "options snd-via82xx index 0" (or equivalent) to /etc/modules.d/alsa-base. <br>
<br>If my system starts getting confused about the two capture cards I'll be in real trouble, but I'll just try to avoid ever rebooting in future :)<br><br>