Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
HDMI sound on GeForce 8400GS
2,543 views
Skip to first unread message
buck
Jan 20, 2012, 3:26:23 PM1/20/12
to
I suppose I could test this by installing XP on a hard drive to see what
XP does with it...
Does anyone know if the PNY VCG84512D3SPPB video card will produce sound
on the monitor when connected via an HDMI cable?
It does not for me when the proprietary NVIDIA 290.10 drivers are
loaded, but I wonder if that's because I've messed up.
If it matters, this video card is PCI, not Express.
--
buck
XP does with it...
Does anyone know if the PNY VCG84512D3SPPB video card will produce sound
on the monitor when connected via an HDMI cable?
It does not for me when the proprietary NVIDIA 290.10 drivers are
loaded, but I wonder if that's because I've messed up.
If it matters, this video card is PCI, not Express.
--
buck
root
Jan 20, 2012, 3:35:52 PM1/20/12
to
that I have spent months, off and on, trying to get sound
from my NVidia video card. I know that the card is capable
of hdmi sound out because someone here has posted that his
identical card does output sound. Nothing for me, I have
tried buying a different mother board even.
I thought that if it were merely screwing up some config
file then I could get sound if I booted up Knoppix:
nope no sound there either.
I tried defeating the onboard sound, no luck.
Nothing I have done with alsaconfig has made any difference.
I can see the correct modules are loaded, still no sound.
I wish you the best of luck. Post here if you succeed.
J G Miller
Jan 20, 2012, 4:10:38 PM1/20/12
to
On Friday, January 20th, 2012, at 20:35:52h +0000, rOOt explained:
> but I can tell you that I have spent months, off and on,
> trying to get sound from my NVidia video card.
And did you connect a cable from the SPDIF digital out pins of your
sound card or mainboard sound to the SPDIF digital in pins of your
nVidia graphics card?
> but I can tell you that I have spent months, off and on,
> trying to get sound from my NVidia video card.
sound card or mainboard sound to the SPDIF digital in pins of your
nVidia graphics card?
root
Jan 20, 2012, 4:41:51 PM1/20/12
to
video card is an EVGA GeForce 210. I just took the card out
and I don't see any place that an external cable could be
connected to the card. My card is exactly the same as the
one that someone (Terry?) said worked for him.
BTW, when I disabled motherboard sound, alsaconf only
sees SPDIF sound out for NVidia.
root
Jan 20, 2012, 4:49:22 PM1/20/12
to
On this site, the third reviewer says he gets hdmi sound:
http://www.newegg.com/Product/Product.aspx?Item=N82E16814130536
J G Miller
Jan 20, 2012, 5:47:25 PM1/20/12
to
On Friday, January 20th, 2012, 21:41:51h +0000, rOOt wrote:
> Duh, no I didn't because I didn't know anything about that. My video
> card is an EVGA GeForce 210. I just took the card out and I don't see
> any place that an external cable could be connected to the card.
Well maybe it does not need one after all. I based my comments on
> Duh, no I didn't because I didn't know anything about that. My video
> card is an EVGA GeForce 210. I just took the card out and I don't see
> any place that an external cable could be connected to the card.
experience with an nVidia GTS 250 which came with an SPDIF cable
in the box that required the connection, and was thus under the
impression that it was generally required.
It seems that some AMD/ATI graphics cards have an actual "sound card"
on board so no connection is needed to anything else to get sound.
See discusion about SPDIF cable and not needed for AMD/ATI at
<http://www.techspot.COM/vb/topic139061.html>
and see the tutorial about SPDIF cables specifically for GeForce cards at
<http://www.hardwaresecrets.COM/article/How-to-Use-The-SPDIF-Connector-Available-on-GeForce-Video-Cards/600>
But that was dated August 2008, so maybe newer GeForce cards do not
need the cable to get sound routed from the sound card to the graphics
card and it is done in software.
> BTW, when I disabled motherboard sound, alsaconf only sees SPDIF sound
> out for NVidia.
According to the sequence in detection and loading of the different sound cards,
the ALSA system numbers them sequentially hw:0, hw:1 etc, or the order can
be specified as an option in the modprobe.d conf file eg
options snd-sbawe index=0
options snd-pcsp index=1
options snd-bt87x index=2
options snd-usb-audio index=3 pid=0x0329 vid=0x0471
You can then adjust the levels appropriately using alsamixer
which defaults to the default specified in /etc/asound.conf if
present otherwise hw:0. You can go directly to each device using
alsamixer -D hw:1
or from within an already running alsamixer by hitting F6 to select card.
Scott Alfter
Jan 20, 2012, 5:50:27 PM1/20/12
to
In article <jfcn2v$ghk$1...@news.albasani.net>, root <NoE...@home.org> wrote:
>J G Miller <mil...@yoyo.ORG> wrote:
>> And did you connect a cable from the SPDIF digital out pins of your
>> sound card or mainboard sound to the SPDIF digital in pins of your
>> nVidia graphics card?
>
>Duh, no I didn't because I didn't know anything about that. My
>video card is an EVGA GeForce 210.
I recently upgraded the video card in my MythTV box from a 9500GT to a 210.
>J G Miller <mil...@yoyo.ORG> wrote:
>> And did you connect a cable from the SPDIF digital out pins of your
>> sound card or mainboard sound to the SPDIF digital in pins of your
>> nVidia graphics card?
>
>Duh, no I didn't because I didn't know anything about that. My
>video card is an EVGA GeForce 210.
The former has a 2-pin header that you can connect to a S/PDIF header on the
motherboard (or on a sound card); this input is muxed with the video.
The latter has sound-generating capability built in; AFAIK, all you need to
do is make sure (1) you're using a recent version of nVIDIA's binary-blob
driver and not the open-source driver and (2) make sure it's unmuted. It
shows up as four different output devices, but with MythTV at least, you
want to make sure the second is selected. I've tested it with AC3 and DTS
output so far...haven't tried feeding it PCM (either stereo or multichannel)
yet. It's supposed to handle multichannel PCM, Dolby TrueHD, and DTS-HD
Master Audio, which are big wins over what you can do with feeding S/PDIF to
an older card. I haven't tested those capabilities to see if they work.
(That the 210 is fanless is a nice bonus, even if the fat heatsink does
intrude into the neighboring slot's space.)
_/_
/ v \ Scott Alfter (remove the obvious to send mail)
(IIGS( http://alfter.us/ Top-posting!
\_^_/ >What's the most annoying thing on Usenet?
--- Posted via news://freenews.netfront.net/ - Complaints to ne...@netfront.net ---
root
Jan 20, 2012, 7:07:23 PM1/20/12
to
J G Miller <mil...@yoyo.ORG> wrote:
> On Friday, January 20th, 2012, 21:41:51h +0000, rOOt wrote:
>
>> Duh, no I didn't because I didn't know anything about that. My video
>> card is an EVGA GeForce 210. I just took the card out and I don't see
>> any place that an external cable could be connected to the card.
>
> Well maybe it does not need one after all. I based my comments on
> experience with an nVidia GTS 250 which came with an SPDIF cable
> in the box that required the connection, and was thus under the
> impression that it was generally required.
>
> It seems that some AMD/ATI graphics cards have an actual "sound card"
> on board so no connection is needed to anything else to get sound.
>
> See discusion about SPDIF cable and not needed for AMD/ATI at
>
> <http://www.techspot.COM/vb/topic139061.html>
>
>
> and see the tutorial about SPDIF cables specifically for GeForce cards at
>
><http://www.hardwaresecrets.COM/article/How-to-Use-The-SPDIF-Connector-Available-on-GeForce-Video-Cards/600>
>
Thanks for the references. The GeForce 210 is about that age. About 15
>
>> Duh, no I didn't because I didn't know anything about that. My video
>> card is an EVGA GeForce 210. I just took the card out and I don't see
>> any place that an external cable could be connected to the card.
>
> Well maybe it does not need one after all. I based my comments on
> experience with an nVidia GTS 250 which came with an SPDIF cable
> in the box that required the connection, and was thus under the
> impression that it was generally required.
>
> It seems that some AMD/ATI graphics cards have an actual "sound card"
> on board so no connection is needed to anything else to get sound.
>
> See discusion about SPDIF cable and not needed for AMD/ATI at
>
> <http://www.techspot.COM/vb/topic139061.html>
>
>
> and see the tutorial about SPDIF cables specifically for GeForce cards at
>
><http://www.hardwaresecrets.COM/article/How-to-Use-The-SPDIF-Connector-Available-on-GeForce-Video-Cards/600>
>
years ago I had a terrible time with an ATI card and vowed never to
go that route again. Maybe I will give them another chance.
>
> Remember that for each sound card you need an appropriate kernel module loaded.
>
that "Terry" says were loaded for him.
>
> You can then adjust the levels appropriately using alsamixer
> which defaults to the default specified in /etc/asound.conf if
> present otherwise hw:0. You can go directly to each device using
>
> alsamixer -D hw:1
>
> or from within an already running alsamixer by hitting F6 to select card.
and no level change is possible.
As I said, this has been a nightmare for me.
root
Jan 20, 2012, 7:12:53 PM1/20/12
to
Scott Alfter <sc...@alfter.diespammersdie.us> wrote:
> In article <jfcn2v$ghk$1...@news.albasani.net>, root <NoE...@home.org> wrote:
>>J G Miller <mil...@yoyo.ORG> wrote:
>>> And did you connect a cable from the SPDIF digital out pins of your
>>> sound card or mainboard sound to the SPDIF digital in pins of your
>>> nVidia graphics card?
>>
>>Duh, no I didn't because I didn't know anything about that. My
>>video card is an EVGA GeForce 210.
>
> I recently upgraded the video card in my MythTV box from a 9500GT to a 210.
>
> The former has a 2-pin header that you can connect to a S/PDIF header on the
> motherboard (or on a sound card); this input is muxed with the video.
>
> The latter has sound-generating capability built in; AFAIK, all you need to
> do is make sure (1) you're using a recent version of nVIDIA's binary-blob
> driver and not the open-source driver and (2) make sure it's unmuted. It
> shows up as four different output devices, but with MythTV at least, you
> want to make sure the second is selected. I've tested it with AC3 and DTS
> output so far...haven't tried feeding it PCM (either stereo or multichannel)
> yet. It's supposed to handle multichannel PCM, Dolby TrueHD, and DTS-HD
> Master Audio, which are big wins over what you can do with feeding S/PDIF to
> an older card. I haven't tested those capabilities to see if they work.
>
> (That the 210 is fanless is a nice bonus, even if the fat heatsink does
> intrude into the neighboring slot's space.)
When I last played with the 210, a couple of months ago, I did have the
> In article <jfcn2v$ghk$1...@news.albasani.net>, root <NoE...@home.org> wrote:
>>J G Miller <mil...@yoyo.ORG> wrote:
>>> And did you connect a cable from the SPDIF digital out pins of your
>>> sound card or mainboard sound to the SPDIF digital in pins of your
>>> nVidia graphics card?
>>
>>Duh, no I didn't because I didn't know anything about that. My
>>video card is an EVGA GeForce 210.
>
> I recently upgraded the video card in my MythTV box from a 9500GT to a 210.
>
> The former has a 2-pin header that you can connect to a S/PDIF header on the
> motherboard (or on a sound card); this input is muxed with the video.
>
> The latter has sound-generating capability built in; AFAIK, all you need to
> do is make sure (1) you're using a recent version of nVIDIA's binary-blob
> driver and not the open-source driver and (2) make sure it's unmuted. It
> shows up as four different output devices, but with MythTV at least, you
> want to make sure the second is selected. I've tested it with AC3 and DTS
> output so far...haven't tried feeding it PCM (either stereo or multichannel)
> yet. It's supposed to handle multichannel PCM, Dolby TrueHD, and DTS-HD
> Master Audio, which are big wins over what you can do with feeding S/PDIF to
> an older card. I haven't tested those capabilities to see if they work.
>
> (That the 210 is fanless is a nice bonus, even if the fat heatsink does
> intrude into the neighboring slot's space.)
latest NVidia driver. I am running Slackware 13.37 with 2.6.37.6 kernel.
I only see one sound device when the MB sound is disabled.
I have neglected to mention that the only tests I have ever done is
with mplayer originating the sound, either from playing video or
mp3 sources. Wait, no I did try Xine on one video source.
Here I feel sorry that I have hijacked the OP's thread, but I
think my experience and the suggested solutions will be of
value to the OP.
root
Jan 20, 2012, 7:25:12 PM1/20/12
to
root <NoE...@home.org> wrote:
>
> Here I feel sorry that I have hijacked the OP's thread, but I
> think my experience and the suggested solutions will be of
> value to the OP.
To the OP: just to show how sorry I am, I have pulled up
>
> Here I feel sorry that I have hijacked the OP's thread, but I
> think my experience and the suggested solutions will be of
> value to the OP.
everything I saved from the guy who tried to help me get
going. I was wrong about the name, it wasn't Terry it was Todd.
Here is what I have:
Todd <To...@invalid.com> wrote:
> First, a dumb question: do you have your video playing through
> your HDMI cable to your monitor? Do not proceed until you
> get to that point.
Yes, I have video playing. Up to now I have had to connect
video directly to one input on the TV and have sound coming
from a separate input on the audio receiver.
>
> And, make sure you have the latest nVidia drivers installed.
> My audio completely corked when I installed this card without
> upgrading the driver. The "Audio" component of the HDMI section
> is part of the video driver.
Well I didn't have the latest, but I just downloaded and installed
NVIDIA-Linux-x86-285.05.09.run
with no change in result. I get a good picture and no sound.
>
> Next set your default sound card to HDMI. I do this with:
> /usr/bin/system-config-soundcard
Here we have distribution differences, I don't have that file.
In current versions of Slackware the sound module to be loaded
is found in /etc/modprobe.d/sound
but that entry is snd_hda_intel.
>
> You will find the "Default audio device" setting under the "Settings"
> tab. My HDMI card is called "nVidia Corporation High Definition
> Audio Controller".
>
> You can do a double check with:
> $ cat /etc/asound.conf
>
> While you are in system-config-soundcard, make sure both your Master
> and PCM sound are turned up. Also make sure you speakers are
> turned up.
>
> And on the system-config-soundcard "Sound Test" tab, there is a
> test sound to test things with.
>
> HTH,
From To...@invalid.com Tue Nov 15 15:35:13 2011
Path: eternal-september.org!mx04.eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail
From: Todd <To...@invalid.com>
Newsgroups: comp.os.linux.misc
Subject: Re: Anyone get arecord to work?
Date: Mon, 14 Nov 2011 18:13:12 -0800
Organization: A noiseless patient Spider
Lines: 147
Message-ID: <j9shro$42k$1...@dont-email.me>
References: <j9rocn$u8t$1...@dont-email.me> <f7ewq.37745$Ra6....@newsfe07.iad> <j9rrtv$k2j$1...@dont-email.me> <j9s2b3$55e$1...@dont-email.me> <j9sbg3$n6n$1...@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 15 Nov 2011 02:13:12 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="oNG4F7wI40wwxD9FNZv9OA"; logging-data="4180"; mail-complaints-to="ab...@eternal-september.org"; posting-account="U2FsdGVkX1+toaVtSGDNkoLn0C6DohKFAkqIuOFIBD0="
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:8.0) Gecko/20111105 Thunderbird/8.0
In-Reply-To: <j9sbg3$n6n$1...@dont-email.me>
Cancel-Lock: sha1:LuxaOPNMp1fXOpClmvHXgiNlvXw=
Xref: feeder.eternal-september.org comp.os.linux.misc:22487
On 11/14/2011 04:24 PM, J G Miller wrote:
> On Mon, 14 Nov 2011 13:48:15 -0800, Todd wrote:
>
>> # ps ax | grep -i pulse
>> 17515 pts/1 S+ 0:00 grep -i pulse
>
> That will not show all processes.
>
> You need to do
>
> ps -aefw | egrep pulse
# ps -aefw | egrep pulse
root 14000 13977 0 18:00 pts/1 00:00:00 egrep pulse
>
>> I am using the old gnome. Who do I get at the level meter?
>
> So what happened when you tried to run gnome-volume-control
> or if I have misremembered the name, go to gnome-control-center
> and then double click on sound.
# ps -aefw | egrep pulse
root 14000 13977 0 18:00 pts/1 00:00:00 egrep pulse
# ps -aefw | egrep gnome
todd 14009 1 0 18:01 ? 00:00:00
/usr/bin/gnome-volume-control
I can turn the mic on and off. Off kills the pass through
to my speakers
>
>> I actually have a second HDMI sound card on my nVidia GT210
>> video card.
>
> As far as I understand, that is NOT a cound card. It is just
> a way of taking the sound feed from your actual sound card or
> onboard sound and piping it through through the HDMI output
> of the video card.
This one will stand on its own. You do not need an extra sound card
if your have an HDMI monitor with build in speakers. No mic
or line input though.
> It would be helpful if you could do the following checks
>
> dmesg
>
> just after boot up and look to through the lines to see if
> your onboard sound card is there and any relevant details.
# dmesg | grep -i esb2
ESB2: IDE controller at PCI slot 0000:00:1f.1
ESB2: chipset revision 9
ESB2: not 100% native mode: will probe irqs later
>
> Now as you say you can hear sounds, this means that something
> has been found so
>
> lsmod | egrep snd
# lsmod | egrep snd
snd_hda_codec_hdmi 28420 4
snd_hda_intel 35808 0
snd_intel8x0 37404 2
snd_hda_codec 84480 2 snd_hda_codec_hdmi,snd_hda_intel
snd_ac97_codec 98596 1 snd_intel8x0
snd_hwdep 12932 1 snd_hda_codec
ac97_bus 6272 1 snd_ac97_codec
snd_seq_dummy 7940 0
snd_seq_oss 31360 0
snd_seq_midi_event 11008 1 snd_seq_oss
snd_seq 50416 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 11788 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 42624 0
snd_mixer_oss 19840 1 snd_pcm_oss
snd_pcm 75780 6
snd_hda_codec_hdmi,snd_hda_intel,snd_intel8x0,snd_hda_codec,snd_ac97_codec,snd_pcm_oss
snd_timer 25348 2 snd_seq,snd_pcm
snd 61892 18
snd_hda_codec_hdmi,snd_hda_intel,snd_intel8x0,snd_hda_codec,snd_ac97_codec,snd_hwdep,snd_seq_dummy,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 11553 1 snd
snd_page_alloc 14984 3 snd_hda_intel,snd_intel8x0,snd_pcm
> would be useful to see what ALSA modules have been loaded.
>
> And you did not give any indication of what happened when you
> did
>
> alsamixer -D hw:0
Went straight into alsamixer. All my previous setting were still intact
>
> If nothing happens as ordinary user, try doing that as root,
No joy (means nothing changed as root).
> because there may be a permissions problem on the audio device
> files.
>
> Also check
>
> cat /dev/sndstat
# cat /dev/sndstat
cat: /dev/sndstat: No such file or directory
>
> and ls -aFls /dev/snd/*# ls -aFls /dev/snd/*
0 crw------- 1 todd audio 116, 8 Nov 14 17:42 /dev/snd/controlC0
0 crw------- 1 todd audio 116, 17 Nov 14 17:42 /dev/snd/controlC1
0 crw------- 1 todd audio 116, 16 Nov 14 17:42 /dev/snd/hwC1D0
0 crw------- 1 todd audio 116, 15 Nov 14 17:42 /dev/snd/hwC1D1
0 crw------- 1 todd audio 116, 14 Nov 14 17:42 /dev/snd/hwC1D2
0 crw------- 1 todd audio 116, 13 Nov 14 17:42 /dev/snd/hwC1D3
0 crw------- 1 todd audio 116, 7 Nov 14 17:42 /dev/snd/pcmC0D0c
0 crw------- 1 todd audio 116, 6 Nov 14 17:45 /dev/snd/pcmC0D0p
0 crw------- 1 todd audio 116, 5 Nov 14 17:42 /dev/snd/pcmC0D1c
0 crw------- 1 todd audio 116, 4 Nov 14 17:42 /dev/snd/pcmC0D2c
0 crw------- 1 todd audio 116, 3 Nov 14 17:42 /dev/snd/pcmC0D3c
0 crw------- 1 todd audio 116, 2 Nov 14 17:42 /dev/snd/pcmC0D4p
0 crw------- 1 todd audio 116, 12 Nov 14 17:42 /dev/snd/pcmC1D3p
0 crw------- 1 todd audio 116, 11 Nov 14 17:42 /dev/snd/pcmC1D7p
0 crw------- 1 todd audio 116, 10 Nov 14 17:42 /dev/snd/pcmC1D8p
0 crw------- 1 todd audio 116, 9 Nov 14 17:42 /dev/snd/pcmC1D9p
0 crw------- 1 todd audio 116, 1 Nov 14 17:42 /dev/snd/seq
0 crw------- 1 todd audio 116, 33 Nov 14 17:42 /dev/snd/timer
>> when I can play music through my (non-hdmi) speakers.
>
> Presumably you have the speakers plugged into the green socket.
Yes
>
> Do you plug the microphone into the pink socket?
Yes
------------------------------------------------------------------------
Hope something in there helps you.
Clark Smith
Jan 21, 2012, 11:05:20 AM1/21/12
to
I have a setup that seems to be quite similar to yours, and I am
getting sound from my 210 card using the HDMI connector all right. This
is under Slackware 13.1, and with one year old nVidia drivers; I can't
quite remember the exact version right now. I'll let you now, if
necessary, but first do the following:
Take a look at /proc/asound/card0/eld*. Which file contains your
monitor information? The files are numbered 0, 1, 2, 3, and correspond to
ALSA device IDs 3, 7, 8, 9. Then, try the following command:
speaker-test -c 2 -r 48000 -D hw:0,N
where N is 3/7/8/9 as mentioned above, until you get sound.
Also, you can try:
aplay -D hw:0,N filename.wav
if you have a wav file to test with.
Alternatively, try
mplayer -ao alsa:device=hw=0.N
In my case, the device number N I had to use was 8. Until I did this I
could get no sound whatsoever through the HDMI connector.
I wonder if this could also work for 8400GS cards without SPDIF
connector?
getting sound from my 210 card using the HDMI connector all right. This
is under Slackware 13.1, and with one year old nVidia drivers; I can't
quite remember the exact version right now. I'll let you now, if
necessary, but first do the following:
Take a look at /proc/asound/card0/eld*. Which file contains your
monitor information? The files are numbered 0, 1, 2, 3, and correspond to
ALSA device IDs 3, 7, 8, 9. Then, try the following command:
speaker-test -c 2 -r 48000 -D hw:0,N
where N is 3/7/8/9 as mentioned above, until you get sound.
Also, you can try:
aplay -D hw:0,N filename.wav
if you have a wav file to test with.
Alternatively, try
mplayer -ao alsa:device=hw=0.N
In my case, the device number N I had to use was 8. Until I did this I
could get no sound whatsoever through the HDMI connector.
I wonder if this could also work for 8400GS cards without SPDIF
connector?
root
Jan 21, 2012, 1:29:39 PM1/21/12
to
Clark Smith <noad...@nowhere.net> wrote:
Thanks for responding.
> I have a setup that seems to be quite similar to yours, and I am
> getting sound from my 210 card using the HDMI connector all right. This
> is under Slackware 13.1, and with one year old nVidia drivers; I can't
> quite remember the exact version right now. I'll let you now, if
> necessary, but first do the following:
>
> Take a look at /proc/asound/card0/eld*.
Well I don't have such eld* entries. Here is what I see:
via:/proc/asound/card0>ls -l /proc/asound/card0
total 0
-r--r--r-- 1 root root 0 2012-01-21 11:11 codec#2
-r--r--r-- 1 root root 0 2012-01-21 11:11 id
-rw-r--r-- 1 root root 0 2012-01-21 11:11 oss_mixer
dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm0c/
dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm0p/
dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm1c/
dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm1p/
The id is Intel.
The file codec#2 contains lots of information like this:
Codec: Realtek ALC662 rev1
Address: 2
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0662
Subsystem Id: 0x15650000
Revision Id: 0x100101
No Modem Function Group found
Default PCM:
rates [0x160]: 44100 48000 96000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=2, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
Node 0x02 [Audio Output] wcaps 0x1d: Stereo Amp-Out
Control: name="Front Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC662 rev1 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
Amp-Out vals: [0x2c 0x2c]
Converter: stream=0, channel=0
<LOTS MORE STUFF DELETED>
This motherboard has onboard sound and the device is not disabled.
> Which file contains your
> monitor information? The files are numbered 0, 1, 2, 3, and correspond to
> ALSA device IDs 3, 7, 8, 9. Then, try the following command:
>
> speaker-test -c 2 -r 48000 -D hw:0,N
>
> where N is 3/7/8/9 as mentioned above, until you get sound.
>
> Also, you can try:
>
> aplay -D hw:0,N filename.wav
>
> if you have a wav file to test with.
>
> Alternatively, try
>
> mplayer -ao alsa:device=hw=0.N
>
> In my case, the device number N I had to use was 8. Until I did this I
> could get no sound whatsoever through the HDMI connector.
>
> I wonder if this could also work for 8400GS cards without SPDIF
> connector?
>
I have to change connections around to run your speaker-test cases.
I will get back to you.
>
Thanks for responding.
> I have a setup that seems to be quite similar to yours, and I am
> getting sound from my 210 card using the HDMI connector all right. This
> is under Slackware 13.1, and with one year old nVidia drivers; I can't
> quite remember the exact version right now. I'll let you now, if
> necessary, but first do the following:
>
> Take a look at /proc/asound/card0/eld*.
via:/proc/asound/card0>ls -l /proc/asound/card0
total 0
-r--r--r-- 1 root root 0 2012-01-21 11:11 codec#2
-r--r--r-- 1 root root 0 2012-01-21 11:11 id
-rw-r--r-- 1 root root 0 2012-01-21 11:11 oss_mixer
dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm0c/
dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm0p/
dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm1c/
dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm1p/
The id is Intel.
The file codec#2 contains lots of information like this:
Codec: Realtek ALC662 rev1
Address: 2
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0662
Subsystem Id: 0x15650000
Revision Id: 0x100101
No Modem Function Group found
Default PCM:
rates [0x160]: 44100 48000 96000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
GPIO: io=2, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
Node 0x02 [Audio Output] wcaps 0x1d: Stereo Amp-Out
Control: name="Front Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC662 rev1 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
Amp-Out vals: [0x2c 0x2c]
Converter: stream=0, channel=0
<LOTS MORE STUFF DELETED>
This motherboard has onboard sound and the device is not disabled.
> Which file contains your
> monitor information? The files are numbered 0, 1, 2, 3, and correspond to
> ALSA device IDs 3, 7, 8, 9. Then, try the following command:
>
> speaker-test -c 2 -r 48000 -D hw:0,N
>
> where N is 3/7/8/9 as mentioned above, until you get sound.
>
> Also, you can try:
>
> aplay -D hw:0,N filename.wav
>
> if you have a wav file to test with.
>
> Alternatively, try
>
> mplayer -ao alsa:device=hw=0.N
>
> In my case, the device number N I had to use was 8. Until I did this I
> could get no sound whatsoever through the HDMI connector.
>
> I wonder if this could also work for 8400GS cards without SPDIF
> connector?
>
I will get back to you.
>
root
Jan 21, 2012, 1:40:48 PM1/21/12
to
I tried speaker-test -c 2 -r 48000 -D hw:0,[3789]
and in each case the resulting message was:
Playback open error:-2 No such file or directory.
In the course of screwing with this card I have
gone from 13.0,13.1, and now 13.37. I suppose
the difference between our /proc/asound/card* stuff
is due to 13.1->13.37
buck
Jan 21, 2012, 2:23:05 PM1/21/12
to
root <NoE...@home.org> wrote in news:jfcj78$8q0$1...@news.albasani.net:
> buck <bu...@private.mil> wrote:
>> I suppose I could test this by installing XP on a hard drive to see
>> what XP does with it...
>>
>> Does anyone know if the PNY VCG84512D3SPPB video card will produce
>> sound on the monitor when connected via an HDMI cable?
>>
>> It does not for me when the proprietary NVIDIA 290.10 drivers are
>> loaded, but I wonder if that's because I've messed up.
>>
>> If it matters, this video card is PCI, not Express.
>> --
>> buck
>
>
In order to find out if the NVidia card had sound, I installed XP Pro
SP2 on a spare HD. The MoBo is Intel with onboard sound. At first, I
thought the Intel audio drivers had failed because Device Manager had
"?" for several lines of sound devices, so I downloaded the most
recent drivers from Intel for this MoBo. No Joy; still "?".
Because onboard sound isn't important to me, I installed the NVidia
DVD, which added the drivers for BOTH the sound and video. Since I
like it, I downloaded and ran Media Player Classic and VOILA, my movie
(Halfblood Prince) is displayed with audio, and the monitor volume
works as expected. So far, I have had no success in moving the
subtitles below the picture, which is discouraging. But not as
discouraging as having to run WinBLOWS to play DVD movies! What is
REALLY discouraging is all the freakin' reboots required to install
XP. This setup took several hours to accomplish and it is just a
throwaway, needed only to prove/disprove an audio device on the video
card. I suppose it is A Good Thing that I heard the HDMI monitor's
speakers at every stinking reboot???
Thus encouraged, I forged ahead with the Linux setup. At the end of
/usr/share/doc/NVIDIA_GLX-1.0/html/audiosupport.html
I found a link to a very thorough - to the point of tedious -
explanation:
gpu-hdmi-audio.html
Using that, I found that my NVidia audio was the second device, so I
created /etc/asound.conf containing
pcm.!default hdmi:NVidia
to set it as the default sound card, and restarted alsa. alsamixer
found the device and allowed me to unmute all 4 S/PDIFs, and showed me
that the onboard Intel audio was now the second device. This was
"necessary" because it is A Royal Pain to configure VLC or mplayer to
use a non-default sound card. For those who use gpu-hdmi-audio.html,
do be careful to note the difference between the upper and lower case
"L" in the "aplay -l" / "aplay -L" references. I stumbled here
<shrug>. At least I didn't forget to run
alsactl store
after unmuting.
Still following gpu-hdmi-audio.html, speaker-test showed that only one
of the 4 DEVs produced sound, but now I do get white noise from each
of the 2 stereo speakers - which is my "relative success" to this
point.
When running
aplay tada.wav
the resulting display complains that the sampling rate is too low, and
sound is garbled. Having no other .wav file to test with, I shrugged
that off. Using mplayer, Halfblood Prince displays beautifully and I
can turn on subtitles, but there is no audio. DAMN. I'll see if
changes to .mplayer/config in my home directory help, but I've given
up for now.
I'm ashamed to admit it, but I've spent all the time I can afford for
now, so I'm keeping the dual boot and using XP to play movies. fsck.
--
buck
> buck <bu...@private.mil> wrote:
>> I suppose I could test this by installing XP on a hard drive to see
>> what XP does with it...
>>
>> Does anyone know if the PNY VCG84512D3SPPB video card will produce
>> sound on the monitor when connected via an HDMI cable?
>>
>> It does not for me when the proprietary NVIDIA 290.10 drivers are
>> loaded, but I wonder if that's because I've messed up.
>>
>> If it matters, this video card is PCI, not Express.
>> --
>> buck
>
>
> I wish you the best of luck. Post here if you succeed.
Well, "success" is relative...
In order to find out if the NVidia card had sound, I installed XP Pro
SP2 on a spare HD. The MoBo is Intel with onboard sound. At first, I
thought the Intel audio drivers had failed because Device Manager had
"?" for several lines of sound devices, so I downloaded the most
recent drivers from Intel for this MoBo. No Joy; still "?".
Because onboard sound isn't important to me, I installed the NVidia
DVD, which added the drivers for BOTH the sound and video. Since I
like it, I downloaded and ran Media Player Classic and VOILA, my movie
(Halfblood Prince) is displayed with audio, and the monitor volume
works as expected. So far, I have had no success in moving the
subtitles below the picture, which is discouraging. But not as
discouraging as having to run WinBLOWS to play DVD movies! What is
REALLY discouraging is all the freakin' reboots required to install
XP. This setup took several hours to accomplish and it is just a
throwaway, needed only to prove/disprove an audio device on the video
card. I suppose it is A Good Thing that I heard the HDMI monitor's
speakers at every stinking reboot???
Thus encouraged, I forged ahead with the Linux setup. At the end of
/usr/share/doc/NVIDIA_GLX-1.0/html/audiosupport.html
I found a link to a very thorough - to the point of tedious -
explanation:
gpu-hdmi-audio.html
Using that, I found that my NVidia audio was the second device, so I
created /etc/asound.conf containing
pcm.!default hdmi:NVidia
to set it as the default sound card, and restarted alsa. alsamixer
found the device and allowed me to unmute all 4 S/PDIFs, and showed me
that the onboard Intel audio was now the second device. This was
"necessary" because it is A Royal Pain to configure VLC or mplayer to
use a non-default sound card. For those who use gpu-hdmi-audio.html,
do be careful to note the difference between the upper and lower case
"L" in the "aplay -l" / "aplay -L" references. I stumbled here
<shrug>. At least I didn't forget to run
alsactl store
after unmuting.
Still following gpu-hdmi-audio.html, speaker-test showed that only one
of the 4 DEVs produced sound, but now I do get white noise from each
of the 2 stereo speakers - which is my "relative success" to this
point.
When running
aplay tada.wav
the resulting display complains that the sampling rate is too low, and
sound is garbled. Having no other .wav file to test with, I shrugged
that off. Using mplayer, Halfblood Prince displays beautifully and I
can turn on subtitles, but there is no audio. DAMN. I'll see if
changes to .mplayer/config in my home directory help, but I've given
up for now.
I'm ashamed to admit it, but I've spent all the time I can afford for
now, so I'm keeping the dual boot and using XP to play movies. fsck.
--
buck
TheGunslinger
Jan 21, 2012, 2:34:22 PM1/21/12
to
Pebble High Definition Audio, and the NVidia High Definition Audio.
HDMI supports video and sound, and I get full functionality on my HDTV
via the HDMI connectors.
I, also, have a desktop with HDMI, and no problems there. It's not
booted atm: so, I am unable to tell you the hardware installed. But it
has an NVidia video card with HDMI connectors, and I have used it with
my HDTV, also.
You might try re-installing the hardware drivers and/or upgrading.
IMHO,
MJR
Clark Smith
Jan 21, 2012, 4:43:40 PM1/21/12
to
On Sat, 21 Jan 2012 18:29:39 +0000, root wrote:
> Clark Smith <noad...@nowhere.net> wrote:
>
> Thanks for responding.
>
>
>> I have a setup that seems to be quite similar to yours, and I am
>> getting sound from my 210 card using the HDMI connector all right. This
>> is under Slackware 13.1, and with one year old nVidia drivers; I can't
>> quite remember the exact version right now. I'll let you now, if
>> necessary, but first do the following:
>>
>> Take a look at /proc/asound/card0/eld*.
>
> Well I don't have such eld* entries. Here is what I see:
>
> via:/proc/asound/card0>ls -l /proc/asound/card0 total 0
> -r--r--r-- 1 root root 0 2012-01-21 11:11 codec#2 -r--r--r-- 1 root root
> 0 2012-01-21 11:11 id -rw-r--r-- 1 root root 0 2012-01-21 11:11
> oss_mixer dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm0c/ dr-xr-xr-x 3
> root root 0 2012-01-21 11:11 pcm0p/ dr-xr-xr-x 3 root root 0 2012-01-21
> 11:11 pcm1c/ dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm1p/
>
> The id is Intel.
>
> The file codec#2 contains lots of information like this: Codec: Realtek
> ALC662 rev1
> Address: 2
> AFG Function Id: 0x1 (unsol 1)
That does not seem to be the nVidia card, but some other (built-
> Clark Smith <noad...@nowhere.net> wrote:
>
> Thanks for responding.
>
>
>> I have a setup that seems to be quite similar to yours, and I am
>> getting sound from my 210 card using the HDMI connector all right. This
>> is under Slackware 13.1, and with one year old nVidia drivers; I can't
>> quite remember the exact version right now. I'll let you now, if
>> necessary, but first do the following:
>>
>> Take a look at /proc/asound/card0/eld*.
>
> Well I don't have such eld* entries. Here is what I see:
>
> via:/proc/asound/card0>ls -l /proc/asound/card0 total 0
> -r--r--r-- 1 root root 0 2012-01-21 11:11 codec#2 -r--r--r-- 1 root root
> 0 2012-01-21 11:11 id -rw-r--r-- 1 root root 0 2012-01-21 11:11
> oss_mixer dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm0c/ dr-xr-xr-x 3
> root root 0 2012-01-21 11:11 pcm0p/ dr-xr-xr-x 3 root root 0 2012-01-21
> 11:11 pcm1c/ dr-xr-xr-x 3 root root 0 2012-01-21 11:11 pcm1p/
>
> The id is Intel.
>
> The file codec#2 contains lots of information like this: Codec: Realtek
> ALC662 rev1
> Address: 2
> AFG Function Id: 0x1 (unsol 1)
in?) audio device. What do you get when you do
cat /proc/asound/cards
?
root
Jan 21, 2012, 6:55:42 PM1/21/12
to
Clark Smith <noad...@nowhere.net> wrote:
>
> cat /proc/asound/cards
>
> ?
>
Here is what I get:
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xfb620000 irq 66
>
> cat /proc/asound/cards
>
> ?
>
Here is what I get:
0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xfb620000 irq 66
root
Jan 21, 2012, 8:14:02 PM1/21/12
to
Following an earlier suggestion I went to:
ftp://download.nvidia.com/XFree86/gpu-hdmi-audio-document/gpu-hdmi-audio.html
This site led me step by step. First:
aplay -L
lists all the sound devices. My video card came up as
the second.
Then the document said:
For GPUs, which are typically ALSA card 1:
speaker-test -c 2 -r 48000 -D hw:1,3
speaker-test -c 2 -r 48000 -D hw:1,7
speaker-test -c 2 -r 48000 -D hw:1,8
speaker-test -c 2 -r 48000 -D hw:1,9
This one did it for me:
speaker-test -c 2 -r 48000 -D hw:1,7
I got sound for the white noise test.
You must be under X to get sound. I had tried this
under a console with no success. I vaguely remember
doing the same (console) test several months ago.
Under the console it seems as if the test is running,
stuff comes up on the screen, but no sound comes out.
Now, I know that I have to pass hw:1,7 to the sound
configuration, but I have tried several forms of
asound.conf and nothing makes mplayer work.
I did try
aplay aplay -D hw:1,7 somefile.wav
and sound came out.
Can someone please fill in the final gap:
what should either .asoundrc or /etc/asound.conf
be to have sound come out from mplayer?
Is it possible to have console sound come out
of the motherboard audio and video sound come
out of the hdmi without tweaking the config
file?
Clark Smith
Jan 21, 2012, 10:23:58 PM1/21/12
to
pcm.!default {
type plug
slave.pcm {
type hw
card 0
device 8
}
}
I guess for you it'd be card 1 and device 7.
root
Jan 21, 2012, 11:04:01 PM1/21/12
to
Clark Smith <noad...@nowhere.net> wrote:
> This is what I have in my /etc/asound.conf file:
>
> pcm.!default {
> type plug
> slave.pcm {
> type hw
> card 0
> device 8
> }
> }
>
> I guess for you it'd be card 1 and device 7.
>
For this particular machine I have the onboard sound going
> This is what I have in my /etc/asound.conf file:
>
> pcm.!default {
> type plug
> slave.pcm {
> type hw
> card 0
> device 8
> }
> }
>
> I guess for you it'd be card 1 and device 7.
>
to one of the inputs of my receiver, while the hdmi output
goes to an hdmi input of the same receiver. I was afraid
setting the default audio out to the hdmi would disrupt
all the uses I had programmed for onboard output.
I decided that I only invoked mplayer under X in
a few places so it was best for me to just include
-ao alsa:device=hw=1.7
in those scripts.
It now seems so simple to get hdmi sound running
I am ashamed it took me several months of off/on
work. A tribute to all who helped me and the OP
who started this thread.
Thanks.
>
Henrik Carlqvist
Jan 22, 2012, 7:02:20 AM1/22/12
to
root <NoE...@home.org> wrote:
> I decided that I only invoked mplayer under X in
> a few places so it was best for me to just include
> -ao alsa:device=hw=1.7
> in those scripts.
Or you could try putting the following in ~/.mplayer/config
> I decided that I only invoked mplayer under X in
> a few places so it was best for me to just include
> -ao alsa:device=hw=1.7
> in those scripts.
ao=alsa:device=hw=1.7
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc123(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
root
Jan 22, 2012, 9:54:10 AM1/22/12
to
Henrik Carlqvist <Henrik.C...@deadspam.com> wrote:
> root <NoE...@home.org> wrote:
>> I decided that I only invoked mplayer under X in
>> a few places so it was best for me to just include
>> -ao alsa:device=hw=1.7
>> in those scripts.
>
> Or you could try putting the following in ~/.mplayer/config
> ao=alsa:device=hw=1.7
I use this particular machine as both a music and video server.
> root <NoE...@home.org> wrote:
>> I decided that I only invoked mplayer under X in
>> a few places so it was best for me to just include
>> -ao alsa:device=hw=1.7
>> in those scripts.
>
> Or you could try putting the following in ~/.mplayer/config
> ao=alsa:device=hw=1.7
When I play mp3 files I use mplayer and I want the sound to
come out of the onboard audio device. When I play video I
also use mplayer but then I want the sound to come out of
the hdmi connection.
>
> regards Henrik
buck
Jan 22, 2012, 12:41:23 PM1/22/12
to
Henrik Carlqvist <Henrik.C...@deadspam.com> wrote in
news:pan.2012.01.22....@deadspam.com:
> root <NoE...@home.org> wrote:
>> I decided that I only invoked mplayer under X in
>> a few places so it was best for me to just include
>> -ao alsa:device=hw=1.7
>> in those scripts.
>
> Or you could try putting the following in ~/.mplayer/config
> ao=alsa:device=hw=1.7
>
> regards Henrik
It appears to me that the key is /etc/asound.conf
Would all of you (root, Clark & Henrik) be so kind as to post the
content of asound.conf along with a description of your sound card(s)?
In .mplayer/config are the section headers honored? By that I mean
that if [gnome-mplayer] and [mplayer] both exist, will each
corresponding software only use the entries specific to it? I get the
feeling that since gnome-mplayer is only a front end, it will look at
everything...
--
buck
news:pan.2012.01.22....@deadspam.com:
> root <NoE...@home.org> wrote:
>> I decided that I only invoked mplayer under X in
>> a few places so it was best for me to just include
>> -ao alsa:device=hw=1.7
>> in those scripts.
>
> Or you could try putting the following in ~/.mplayer/config
> ao=alsa:device=hw=1.7
>
> regards Henrik
Would all of you (root, Clark & Henrik) be so kind as to post the
content of asound.conf along with a description of your sound card(s)?
In .mplayer/config are the section headers honored? By that I mean
that if [gnome-mplayer] and [mplayer] both exist, will each
corresponding software only use the entries specific to it? I get the
feeling that since gnome-mplayer is only a front end, it will look at
everything...
--
buck
buck
Jan 22, 2012, 12:55:12 PM1/22/12
to
buck <bu...@private.mil> wrote in news:jfhho...@news2.newsguy.com:
It occurs to me that it might help to understand that I'd like
gnome-mplayer to be the only thing using the NVidia sound card, while
mplayer, aplay, arecord etc. use the Intel onboard sound.
That might also alter the content of asound.conf?
--
buck
gnome-mplayer to be the only thing using the NVidia sound card, while
mplayer, aplay, arecord etc. use the Intel onboard sound.
That might also alter the content of asound.conf?
--
buck
root
Jan 22, 2012, 1:02:48 PM1/22/12
to
buck <bu...@private.mil> wrote:
> Henrik Carlqvist <Henrik.C...@deadspam.com> wrote in
> news:pan.2012.01.22....@deadspam.com:
>
>> root <NoE...@home.org> wrote:
>>> I decided that I only invoked mplayer under X in
>>> a few places so it was best for me to just include
>>> -ao alsa:device=hw=1.7
>>> in those scripts.
>>
>> Or you could try putting the following in ~/.mplayer/config
>> ao=alsa:device=hw=1.7
>>
>> regards Henrik
>
> It appears to me that the key is /etc/asound.conf
>
> Would all of you (root, Clark & Henrik) be so kind as to post the
> content of asound.conf along with a description of your sound card(s)?
root: I have removed both /etc/asound.conf and .asoundrc so that
> Henrik Carlqvist <Henrik.C...@deadspam.com> wrote in
> news:pan.2012.01.22....@deadspam.com:
>
>> root <NoE...@home.org> wrote:
>>> I decided that I only invoked mplayer under X in
>>> a few places so it was best for me to just include
>>> -ao alsa:device=hw=1.7
>>> in those scripts.
>>
>> Or you could try putting the following in ~/.mplayer/config
>> ao=alsa:device=hw=1.7
>>
>> regards Henrik
>
> It appears to me that the key is /etc/asound.conf
>
> Would all of you (root, Clark & Henrik) be so kind as to post the
> content of asound.conf along with a description of your sound card(s)?
I could control which sound device works with each application
independently. Getting sound does not depend on the contents
of those files.
root
Jan 22, 2012, 1:07:42 PM1/22/12
to
as mplayer -ao [whatever], and elsewhere you simply
use mplayer. Create an alias for mplayer with the audio
device hardwired in. It even work out, if your other
uses for mplayer, aplay,arecord,.... run under console
mode, that you don't have anything to worry about.
Henrik Carlqvist
Jan 22, 2012, 2:01:25 PM1/22/12
to
buck <bu...@private.mil> wrote:
> It appears to me that the key is /etc/asound.conf
>
> Would all of you (root, Clark & Henrik) be so kind as to post the
> content of asound.conf along with a description of your sound card(s)?
Most of my machines does not have any asound.conf. However, I used to have
> It appears to me that the key is /etc/asound.conf
>
> Would all of you (root, Clark & Henrik) be so kind as to post the
> content of asound.conf along with a description of your sound card(s)?
that file on my previous motherboard in my mythtv frontend machine.
-8<-------------------
pcm.!default {
type plug
slave {
pcm "spdif"
rate 48000
format S16_LE
}
}
-8<-------------------
The machine only had a builtin soundcard on the (now broken) motherboard,
it is described at http://poolhem.se/video/
Maybe I will have to add such a file again when I get mythtv running on
the new motherboard.
0 new messages