AVerMedia AVerTV Hybrid+FM PCI (A16AR): Difference between revisions
m (AVerMedia AVerTV Hybrid-FM PCI moved to AVerMedia AVerTV Hybrid+FM PCI: Name) |
(starting overall (intermediate save)) |
||
Line 1: | Line 1: | ||
There are actually two different [[DVB-T]] [[DVB-T PCI Cards|PCI cards]] produced by [[AVerMedia]] that bear the identical name AVerTV Hybrid+FM PCI. The first, model A16D is currently not supported by LinuxTV (but experimental support for the device does exist; see below), but the second, model A16A, is supported by LinuxTV drivers. Coincidently, both versions are the sole recipients of direct Linux support from AVerMedia (however, at that, it is very limited/constrained). |
|||
==A16D== |
|||
http://mcentral.de/wiki/index.php/AVerMedia_AverTV_Hybrid_FM_PCI_A16D |
|||
[http://www.hardwareportal.ru/Multimedia/Aver.hybridfmpci/index.html Russian Review] |
|||
==A16A== |
|||
To determine whether you have it setup correctly or not run "<tt>dmesg | grep saa</tt>" and if you see this you need to do the following steps: |
To determine whether you have it setup correctly or not run "<tt>dmesg | grep saa</tt>" and if you see this you need to do the following steps: |
||
Revision as of 22:41, 24 June 2007
There are actually two different DVB-T PCI cards produced by AVerMedia that bear the identical name AVerTV Hybrid+FM PCI. The first, model A16D is currently not supported by LinuxTV (but experimental support for the device does exist; see below), but the second, model A16A, is supported by LinuxTV drivers. Coincidently, both versions are the sole recipients of direct Linux support from AVerMedia (however, at that, it is very limited/constrained).
A16D
http://mcentral.de/wiki/index.php/AVerMedia_AverTV_Hybrid_FM_PCI_A16D
A16A
To determine whether you have it setup correctly or not run "dmesg | grep saa" and if you see this you need to do the following steps:
[ 39.847928] saa7130/34: v4l2 driver version 0.2.14 loaded [ 39.848432] saa7133[0]: found at 0000:01:05.0, rev: 209, irq: 21, latency: 32, mmio: 0xe8002000 [ 39.848437] saa7133[0]: subsystem: 1461:2c00, board: UNKNOWN/GENERIC [card=0,autodetected] [/code]
If you see this then why are you looking at this guide!
[ 555.864000] saa7130/34: v4l2 driver version 0.2.14 loaded [ 555.864000] saa7133[0]: found at 0000:01:05.0, rev: 209, irq: 21, latency: 32, mmio: 0xe8002000 [ 555.864000] saa7133[0]: subsystem: 1461:2c00, board: AVerMedia TV Hybrid A16AR [card=99,insmod option][/code]
Getting it to work
The avermedia drivers are built into the recent kernels (Since version 2.6.11 I think). For this step you need the right kernel options i believe. Ubuntu has them by default however if anyone wants to drop by and bless this wiki with some guidance please help!
To make sure you have a A16AR type in "lspci -v" and you should see:
01:05.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) Subsystem: Avermedia Technologies Inc Unknown device 2c00 Flags: bus master, medium devsel, latency 32, IRQ 21 Memory at e8002000 (32-bit, non-prefetchable) [size=2K] Capabilities: <access denied>[/code]
Then type
sudo rmmod saa7134_alsa saa7134-dvb saa7134
If you can't close them (which will likely happen because saa1734 will be used by any mixers and artsd)
fuser -v /dev/snd/* /dev/dsp/*
and then
killall -9 <process names>.
Now you need to load the correct modules
sudo modprobe saa7134 card=99 sudo modprobe saa7134_alsa sudo modprobe saa7134-dvb
For all those who do not know what sudo is it is used to elevate ones self to root user :P used with Ubuntu.
now load your favorite TV application and watch TV!
I am yet to test this after a reboot but good luck!
Also for anyone who is concerned about the similarities between this guide and the one on the Ubuntu forums they are both by me ;)