From: Lars Oliver Hansen <lars.hansen@yahoo.co.uk>
To: linux-media@vger.kernel.org
Subject: Re: saa7134-alsa and snd_card_new only error with alsa 1.0.19 / ubuntu 9.04 jaunty - tracked down, further help appreciated
Date: Wed, 06 May 2009 22:38:52 +0200 [thread overview]
Message-ID: <1241642332.4042.15.camel@lars-laptop> (raw)
In-Reply-To: <1241552015.7752.29.camel@lars-laptop>
Hi again,
Am Dienstag, den 05.05.2009, 21:33 +0200 schrieb Lars Oliver Hansen:
> So I would have instead of a wrapped call to a non-existant snd_card_new
> a direct call to an exported snd_card_create.
me adding snd_card_create to the Ubuntu sources (headers to be precise)
obviously means it wasn't present before and Ubuntus kernel was compiled
with that code missing, thus "no symbol_version" error message then!
I now opted for disabling the call to snd_card_new and letting v4l s
snd_card_create return -NOEMEM or so.
Now I get "saa7134 ALSA driver for DMA sound loaded" message in dmesg
but I have no sound in tvtime and neither aplay -L nor aplay -l list a
tv-card related sound device and I don't find any audio0 or sound0
device in /dev/.
Is NEED_SND_CARD_CREATE needed for my tv card? It was defined and the
~_new couldn't be found on loading the module, but would it have been
used? If not (or if), is there a way to get (still) sound in tvtime (or
mplayer)? My card is AVerMedia Cardbus TV/Radio (E506R) correctly
autodetected (if I can trust packaging and labelling of my card ;-)) :-)
(it's a hybrid dvb-t / analog device. Yes, dvb-t works, but the channel
I'm interested in occasionally has signal troubles (I'm at a triangle
vertex of the covered area)).
Thank you very much!
B&KR
Lars
prev parent reply other threads:[~2009-05-06 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 19:33 saa7134-alsa and snd_card_new only error with alsa 1.0.19 / ubuntu 9.04 jaunty - tracked down, further help appreciated Lars Oliver Hansen
2009-05-06 20:38 ` Lars Oliver Hansen [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=1241642332.4042.15.camel@lars-laptop \
--to=lars.hansen@yahoo.co.uk \
--cc=linux-media@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox