<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Disabling NVIDIA&#8217;s HDMI Audio Under Linux</title>
	<atom:link href="http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/feed/" rel="self" type="application/rss+xml" />
	<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=disabling_nvidias_hdmi_audio_under_linux</link>
	<description>PC enthusiasts one-stop resource for high-quality reviews, articles and current technology news.</description>
	<lastBuildDate>Thu, 23 May 2013 16:29:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Rob Williams</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1338</link>
		<dc:creator>Rob Williams</dc:creator>
		<pubDate>Fri, 03 May 2013 04:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1338</guid>
		<description><![CDATA[If it can work for a slacker, it can work for anyone! Glad it worked ;-)]]></description>
		<content:encoded><![CDATA[<p>If it can work for a slacker, it can work for anyone! Glad it worked ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slacker</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1337</link>
		<dc:creator>slacker</dc:creator>
		<pubDate>Fri, 03 May 2013 04:34:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1337</guid>
		<description><![CDATA[Thanks much! The blacklist method worked flawlessly for me with newly installed Slackware 14.]]></description>
		<content:encoded><![CDATA[<p>Thanks much! The blacklist method worked flawlessly for me with newly installed Slackware 14.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Williams</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1283</link>
		<dc:creator>Rob Williams</dc:creator>
		<pubDate>Wed, 17 Apr 2013 01:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1283</guid>
		<description><![CDATA[I am glad you got things working! Thanks a ton for the information. Sorry for your hassles... I know how it is.]]></description>
		<content:encoded><![CDATA[<p>I am glad you got things working! Thanks a ton for the information. Sorry for your hassles&#8230; I know how it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DrLex</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1278</link>
		<dc:creator>DrLex</dc:creator>
		<pubDate>Mon, 15 Apr 2013 15:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1278</guid>
		<description><![CDATA[All right, I fixed it. The trick is that when giving module parameters to snd-hda-intel, it is possible to give comma-separated lists to pass the arguments to the different cards. Otherwise, when giving only a single argument, it will always be applied to the first card. Passing an argument to the second card only can be done by starting the argument with a comma.
Because I cannot be sure that the HDMI card will always be at position 0, I simply spam the magical fix parameter to both cards like this in /etc/modprobe.d/alsa-base.conf:

options snd-hda-intel position_fix=3,3

At first I thought it was possible to select a certain card (the one I needed is &quot;SB&quot;) by using e.g. “snd-hda-intel id=SB position_fix=3”, but what this will do is renaming the first card to “SB”, which is of course enormously confusing.]]></description>
		<content:encoded><![CDATA[<p>All right, I fixed it. The trick is that when giving module parameters to snd-hda-intel, it is possible to give comma-separated lists to pass the arguments to the different cards. Otherwise, when giving only a single argument, it will always be applied to the first card. Passing an argument to the second card only can be done by starting the argument with a comma.<br />
Because I cannot be sure that the HDMI card will always be at position 0, I simply spam the magical fix parameter to both cards like this in /etc/modprobe.d/alsa-base.conf:</p>
<p>options snd-hda-intel position_fix=3,3</p>
<p>At first I thought it was possible to select a certain card (the one I needed is &#8220;SB&#8221;) by using e.g. “snd-hda-intel id=SB position_fix=3”, but what this will do is renaming the first card to “SB”, which is of course enormously confusing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DrLex</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1277</link>
		<dc:creator>DrLex</dc:creator>
		<pubDate>Mon, 15 Apr 2013 10:43:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1277</guid>
		<description><![CDATA[Nice try, but no cigar. The snd_hda_codec_hdmi module is gone alright, but the device is still there, only without controls.
I found out that it is possible to disable specific cards by supplying the probe_mask parameter to modprobe, but there is no way to disable the HDMI device without disabling the Realtek, it seems they are fused together. There should be a way to prevent the GPU from presenting its HDMI audio device at all. Theoretically, using the kernel parameter radeon.audio=0 should work, but it does not.
In the meantime I have verified that we did not have the distorted audio with an older kernel in Debian Squeeze. We may revert to that one, or simply plug in an USB sound card.]]></description>
		<content:encoded><![CDATA[<p>Nice try, but no cigar. The snd_hda_codec_hdmi module is gone alright, but the device is still there, only without controls.<br />
I found out that it is possible to disable specific cards by supplying the probe_mask parameter to modprobe, but there is no way to disable the HDMI device without disabling the Realtek, it seems they are fused together. There should be a way to prevent the GPU from presenting its HDMI audio device at all. Theoretically, using the kernel parameter radeon.audio=0 should work, but it does not.<br />
In the meantime I have verified that we did not have the distorted audio with an older kernel in Debian Squeeze. We may revert to that one, or simply plug in an USB sound card.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Williams</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1274</link>
		<dc:creator>Rob Williams</dc:creator>
		<pubDate>Sat, 13 Apr 2013 18:16:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1274</guid>
		<description><![CDATA[Enjoy your weekend. If you need some help next week just hit-me-up.]]></description>
		<content:encoded><![CDATA[<p>Enjoy your weekend. If you need some help next week just hit-me-up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DrLex</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1273</link>
		<dc:creator>DrLex</dc:creator>
		<pubDate>Sat, 13 Apr 2013 17:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1273</guid>
		<description><![CDATA[That looks promising, I&#039;ll look into it when I get back to work. Thanks! But first, a relaxing weekend without fighting snd-hda-intel.]]></description>
		<content:encoded><![CDATA[<p>That looks promising, I&#8217;ll look into it when I get back to work. Thanks! But first, a relaxing weekend without fighting snd-hda-intel.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Williams</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1268</link>
		<dc:creator>Rob Williams</dc:creator>
		<pubDate>Fri, 12 Apr 2013 19:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1268</guid>
		<description><![CDATA[Alright, so I&#039;m not sure when this change happened, but in recent kernels, the Intel HDA driver has gone module, as this screenshot shows. Here, you could disable the HDMI/DisplayPort portion while leaving everything else intact (like the Realtek). If you&#039;re able to upgrade your kernel to a recent version and recompile, that should solve your problem.]]></description>
		<content:encoded><![CDATA[<p>Alright, so I&#8217;m not sure when this change happened, but in recent kernels, the Intel HDA driver has gone module, as this screenshot shows. Here, you could disable the HDMI/DisplayPort portion while leaving everything else intact (like the Realtek). If you&#8217;re able to upgrade your kernel to a recent version and recompile, that should solve your problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob Williams</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1267</link>
		<dc:creator>Rob Williams</dc:creator>
		<pubDate>Fri, 12 Apr 2013 19:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1267</guid>
		<description><![CDATA[That&#039;s beyond frustrating. I&#039;m at a loss at the moment as to how to bypass this, unless there&#039;s ANOTHER switch that specifically disables the HDMI portion of the driver. It&#039;s easy to suggest just going the add-in route as well to ignore the GPU entirely, but so many audio cards simply use the snd-hda-intel driver. My main audio card is an ASUS Xonar, so I&#039;m fortunate enough to be able to avoid that hassle.


If I think of anything I&#039;ll post here again.]]></description>
		<content:encoded><![CDATA[<p>That&#8217;s beyond frustrating. I&#8217;m at a loss at the moment as to how to bypass this, unless there&#8217;s ANOTHER switch that specifically disables the HDMI portion of the driver. It&#8217;s easy to suggest just going the add-in route as well to ignore the GPU entirely, but so many audio cards simply use the snd-hda-intel driver. My main audio card is an ASUS Xonar, so I&#8217;m fortunate enough to be able to avoid that hassle.</p>
<p>If I think of anything I&#8217;ll post here again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DrLex</title>
		<link>http://techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1266</link>
		<dc:creator>DrLex</dc:creator>
		<pubDate>Fri, 12 Apr 2013 14:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://beta.techgage.com/news/disabling_nvidias_hdmi_audio_under_linux/#comment-1266</guid>
		<description><![CDATA[Guess what: I have an ATI-based board with a built-in Realtek ALC892 sound card that needs snd-hda-intel to work. But the first sound card is always set to the built-in HDMI. I can fix this through asound.conf, no problem. But there is another typical Linux sound problem.

Typical for these Realtek things is that some voodoo parameters need to be passed to the kernel module to fix clicking sounds while recording. Adding something like &quot;options snd-hda-intel position_fix=2&quot; to modprobe.d/alsa-base.conf should work. But it does nothing, because it seems that all options are applied to the first snd-hda-intel based card, which is of course the useless HDMI.

I have been fighting for hours to either get that HDMI thing obliterated, or to force the ALC892 to get ID 0 instead of 1. It seems hopeless. The intro to your article is perfectly accurate: configuring sound in Linux is a nightmare.]]></description>
		<content:encoded><![CDATA[<p>Guess what: I have an ATI-based board with a built-in Realtek ALC892 sound card that needs snd-hda-intel to work. But the first sound card is always set to the built-in HDMI. I can fix this through asound.conf, no problem. But there is another typical Linux sound problem.</p>
<p>Typical for these Realtek things is that some voodoo parameters need to be passed to the kernel module to fix clicking sounds while recording. Adding something like &#8220;options snd-hda-intel position_fix=2&#8243; to modprobe.d/alsa-base.conf should work. But it does nothing, because it seems that all options are applied to the first snd-hda-intel based card, which is of course the useless HDMI.</p>
<p>I have been fighting for hours to either get that HDMI thing obliterated, or to force the ALC892 to get ID 0 instead of 1. It seems hopeless. The intro to your article is perfectly accurate: configuring sound in Linux is a nightmare.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching using memcached
Object Caching 251/253 objects using memcached

 Served from: techgage.com @ 2013-05-23 13:02:04 by W3 Total Cache -->