From: James <bjlockie@lockie.ca>
To: Video 4 Linux Mailing List <video4linux-list@redhat.com>
Subject: Re: upgraded software and audio stopped working
Date: Thu, 19 Aug 2010 20:54:19 -0400 [thread overview]
Message-ID: <4C6DD23B.1030404@lockie.ca> (raw)
In-Reply-To: <4C630CEE.7000200@lockie.ca>
On 08/11/10 16:49, James wrote:
> It could just be coincidental that the audio stopped working after I
> upgrade software.
> I didn't try it right after I upgraded the system software so it could
> be the hardware just failed.
> I can still tune channels, I just don't get audio.
>
> bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
> bttv0: Hauppauge eeprom indicates model#44981
> bttv0: tuner type=50
> bttv0: audio absent, no audio device found!
> tuner 2-0061: chip found @ 0xc2 (bt878 #0 [sw])
I upgraded the kernel and the audio out works.
bttv: driver version 0.9.18 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
bttv 0000:02:08.0: PCI INT A -> Link[LNKA] -> GSI 17 (level, low) -> IRQ 17
bttv0: Bt878 (rev 17) at 0000:02:08.0, irq: 17, latency: 32, mmio:
0xcffff000
bttv0: detected: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00ffffdb [init]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
bttv0: Hauppauge eeprom indicates model#44981
bttv0: tuner type=50
bttv0: audio absent, no audio device found!
tuner 2-0061: chip found @ 0xc2 (bt878 #0 [sw])
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: PLL: 28636363 => 35468950 .. ok
bttv0: PLL can sleep, using XTAL (28636363).
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
prev parent reply other threads:[~2010-08-20 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 20:49 upgraded software and audio stopped working James
2010-08-20 0:54 ` James [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C6DD23B.1030404@lockie.ca \
--to=bjlockie@lockie.ca \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.