<div dir="ltr"><div><div><div><div>Hi Janina,<br><br></div>Is it possible to set your default card by modifying or creating a new ~/.asoundrc file? Doing this you should be able to create an alias for "default."<br>
<br></div>If I'm recalling correctly, I've done this before to make my USB sound card the default audio device. I'm not sure how Speakup selects its device, but maybe doing this would help?<br><br></div>The .asoundrc setup will vary depending on setup, but there is some documentation here: <a href="http://www.alsa-project.org/main/index.php/Asoundrc#The_default_plugin">http://www.alsa-project.org/main/index.php/Asoundrc#The_default_plugin</a><br>
<br></div><div>I hope it helps,<br></div>Brian Fay<br><div><div><br></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Aug 16, 2014 at 5:06 PM, Janina Sajka <span dir="ltr"><<a href="mailto:janina@rednote.net" target="_blank">janina@rednote.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
Something about the Linux kernel appears to me to have changed sometime<br>
after kernel-3.13.10. I'm not certain just exactly when, but all the<br>
kernels Fedora has released since 3.13.10 force the HDMI device as the<br>
default ALSA audio device.<br>
<br>
3.13.10 is the last kernel release where my carefully constructed ALSA<br>
audio device ordering identifiers, in /etc/modprobe.d/local.conf, work as<br>
expected.<br>
Any kernel beyond puts the onboard hdmi device as the default ALSA<br>
device, which is simply untenable in my setup. For me it's not even that<br>
I have nothing hanging off my HDMI port, I need the default device for<br>
the Speakup screen reader, and I can't affect that on the Speakup side,<br>
regretably. So, in effect,the system becomes unusable.<br>
<br>
I note the CCRMA kernels for Fedora 20 are now also well behind current<br>
Fedora releases and wonder if what I'm seeing is just one part of a<br>
number of changes relating to audio.<br>
<br>
Anyone know anything about this? Is there possibly a bug here that<br>
should be tagged sooner rather than later? This is a 3-month old issue<br>
now.<br>
<br>
tia<br>
<br>
Janina<br>
<br>
--<br>
<br>
Janina Sajka, Phone: +1.443.300.2200<br>
<a href="mailto:sip%3Ajanina@asterisk.rednote.net">sip:janina@asterisk.rednote.net</a><br>
Email: <a href="mailto:janina@rednote.net">janina@rednote.net</a><br>
<br>
Linux Foundation Fellow<br>
Executive Chair, Accessibility Workgroup: <a href="http://a11y.org" target="_blank">http://a11y.org</a><br>
<br>
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)<br>
Chair, Protocols & Formats <a href="http://www.w3.org/wai/pf" target="_blank">http://www.w3.org/wai/pf</a><br>
Indie UI <a href="http://www.w3.org/WAI/IndieUI/" target="_blank">http://www.w3.org/WAI/IndieUI/</a><br>
<br>
_______________________________________________<br>
PlanetCCRMA mailing list<br>
<a href="mailto:PlanetCCRMA@ccrma.stanford.edu">PlanetCCRMA@ccrma.stanford.edu</a><br>
<a href="http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma" target="_blank">http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma</a><br>
<br>
</blockquote></div><br></div>