From: TCP/IP <t-cp@gmx.net>
To: linux-media@vger.kernel.org
Subject: saa7134-alsa.ko and alsa-driver-1.0.19
Date: Thu, 22 Jan 2009 14:51:25 +0100 [thread overview]
Message-ID: <497879DD.5020303@gmx.net> (raw)
In-Reply-To: <S1752508AbZAVNYE/20090122132404Z+405@vger.kernel.org>
Hi everybody
Has anyone of you got the saa7134-alsa module running with
alsa-driver-1.0.19 ?
root@MythTV:~# modprobe -v saa7134-alsa
insmod
/lib/modules/2.6.27.8/kernel/drivers/media/video/saa7134/saa7134-alsa.ko
FATAL: Error inserting saa7134_alsa
(/lib/modules/2.6.27.8/kernel/drivers/media/video/saa7134/saa7134-alsa.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
root@MythTV:~# dmesg |less
[ 7543.401381] Linux video capture interface: v2.00
[ 7543.412129] saa7130/34: v4l2 driver version 0.2.14 loaded
[ 7543.412157] saa7133[0]: found at 0000:04:00.0, rev: 209, irq: 16,
latency: 64, mmio: 0xfebff800
[ 7543.412162] saa7133[0]: subsystem: 1043:4845, board: ASUSTeK P7131
Analog [card=146,insmod option]
[ 7543.412170] saa7133[0]: board init: gpio is 0
[ 7543.412210] input: saa7134 IR (ASUSTeK P7131 Analo as
/devices/pci0000:00/0000:00:1e.0/0000:04:00.0/input/input9
[ 7543.558005] saa7133[0]: i2c eeprom 00: 43 10 45 48 54 20 1c 00 43 43
a9 1c 55 d2 b2 92
[ 7543.558022] saa7133[0]: i2c eeprom 10: 00 ff e2 0f ff 20 ff ff ff ff
ff ff ff ff ff ff
[ 7543.558038] saa7133[0]: i2c eeprom 20: 01 40 01 02 03 01 01 03 08 ff
00 88 ff ff ff ff
[ 7543.558054] saa7133[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558071] saa7133[0]: i2c eeprom 40: ff 22 00 c2 96 ff 02 30 15 ff
ff ff ff ff ff ff
[ 7543.558086] saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558102] saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558118] saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558136] saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558152] saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558168] saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558184] saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558195] saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558206] saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558216] saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.558227] saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff
ff ff ff ff ff ff
[ 7543.578071] tuner 1-004b: chip found @ 0x96 (saa7133[0])
[ 7543.613005] tda829x 1-004b: setting tuner address to 61
[ 7543.649006] tda829x 1-004b: type set to tda8290+75a
[ 7546.226225] saa7133[0]: registered device video0 [v4l2]
[ 7546.226270] saa7133[0]: registered device vbi0
[ 7546.226312] saa7133[0]: registered device radio0
[ 7546.258185] saa7134_alsa: Unknown symbol snd_card_new
i needed to upgrade the alsa driver in order to get the
00:1b.0 Audio device: Intel Corporation ICH10 HD Audio Controller
soundcard propperly running, so using the alsa out of the kernel source
(using 2.6.27.8 right now) is not an option
do you have any ideas?
i have read somthing about editing the #ifdef-s in compat.h but i have
to admit that i don-t understand what to do there.
Thanks a lot in advance!
Ben
next parent reply other threads:[~2009-01-22 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1752508AbZAVNYE/20090122132404Z+405@vger.kernel.org>
2009-01-22 13:51 ` TCP/IP [this message]
2009-01-22 15:43 ` saa7134-alsa.ko and alsa-driver-1.0.19 TCP/IP
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=497879DD.5020303@gmx.net \
--to=t-cp@gmx.net \
--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