Difference between revisions of "AVerMedia AVerTV Hybrid+FM PCI (A16AR)"

From LinuxTVWiki
Jump to: navigation, search
(another intermediate save (before I forget what I'm doing))
Line 3: Line 3:
 
==A16D==
 
==A16D==
  
[http://mcentral.de/wiki/index.php/AVerMedia_AverTV_Hybrid_FM_PCI_A16D experimental support on mcentral]
+
insert hardware details here
  
[http://www.avermedia.com/EN/Default.aspx?TYPE=vipplayercard.htm&PT=product&tv_TCAT_POS=0&CATNO0=B&CATNO1=BA&CATNO2=BAA&CATNO3=BAA1&CATNO4=BAA1d&CNT=4&PID=4710710671396 AVer link]
+
* [http://mcentral.de/wiki/index.php/AVerMedia_AverTV_Hybrid_FM_PCI_A16D Experimental support on mcentral]
  
[http://www.hardwareportal.ru/Multimedia/Aver.hybridfmpci/index.html Russian Review]
+
* [http://www.avermedia.com/EN/Default.aspx?TYPE=vipplayercard.htm&PT=product&tv_TCAT_POS=0&CATNO0=B&CATNO1=BA&CATNO2=BAA&CATNO3=BAA1&CATNO4=BAA1d&CNT=4&PID=4710710671396 AVer product link]
 +
 
 +
* [http://www.hardwareportal.ru/Multimedia/Aver.hybridfmpci/index.html Russian Review]
  
 
==A16A==
 
==A16A==
 
Support for this card was added to kernel 2.6.19.
 
Support for this card was added to kernel 2.6.19.
 +
 +
insert hardware details here
 +
 +
====Section that needs work====
 +
{{Note|these two examples are less then ideal:
 +
* we need output from lspci that shows the card being properly detected ... what is currently shown is what would be output when the card is NOT automagically recognized!  Second, the capabilities section is incomplete
 +
* the grep of dmesg shows a case where the card was automagically detected (this is good), however, the info really isn't providing anymore insight then  what lspci would provide if the card was properly being detected.}}
  
 
If you have an A16AR then "<tt>lspci -v</tt>" should reveal:
 
If you have an A16AR then "<tt>lspci -v</tt>" should reveal:
Line 25: Line 34:
 
  [  555.864000] saa7133[0]: subsystem: 1461:2c00, board: AVerMedia TV Hybrid A16AR [card=99,insmod option][/code]
 
  [  555.864000] saa7133[0]: subsystem: 1461:2c00, board: AVerMedia TV Hybrid A16AR [card=99,insmod option][/code]
  
[http://www.avermedia.com/EN/Default.aspx?TYPE=vipplayercard.htm&PT=product&tv_TCAT_POS=0&CATNO0=B&CATNO1=BA&CATNO2=BAA&CATNO3=BAA1&CATNO4=BAA1d&CNT=4&PID=4710710671099 Aver link]
+
* [http://www.avermedia.com/EN/Default.aspx?TYPE=vipplayercard.htm&PT=product&tv_TCAT_POS=0&CATNO0=B&CATNO1=BA&CATNO2=BAA&CATNO3=BAA1&CATNO4=BAA1d&CNT=4&PID=4710710671099 Aver link]
[http://www.avermedia.com/cgi-bin/support_driverbympdpro.asp?category=TV%20Card&category2=Hybrid&proname=12&modelno=A16AR link to Vendor's Linux Driver]
+
* [http://www.avermedia.com/cgi-bin/support_driverbympdpro.asp?category=TV%20Card&category2=Hybrid&proname=12&modelno=A16AR AVer's Linux drivers for the card]
 
+
  
On the other hand, if the card is not automagically detected, when you run "<tt>dmesg | grep saa</tt>"  you  
+
====If you're using a kernel >2.6.19 and the card is not automagically detected====
you will see:  
+
If the card is not automagically detected, when you run "<tt>dmesg | grep saa</tt>"  you you will see:  
 
  [  39.847928] saa7130/34: v4l2 driver version 0.2.14 loaded
 
  [  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.848432] saa7133[0]: found at 0000:01:05.0, rev: 209, irq: 21, latency: 32, mmio: 0xe8002000

Revision as of 02:09, 25 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 (though experimental support for the device does exist; see below), but the second, model A16A, is supported by LinuxTV drivers. Coincidently, the second version is also the sole recipient of direct Linux support from AVerMedia (however, at that, it is very limited/constrained).

A16D

insert hardware details here

A16A

Support for this card was added to kernel 2.6.19.

insert hardware details here

Section that needs work

Note: these two examples are less then ideal:
  • we need output from lspci that shows the card being properly detected ... what is currently shown is what would be output when the card is NOT automagically recognized! Second, the capabilities section is incomplete
  • the grep of dmesg shows a case where the card was automagically detected (this is good), however, the info really isn't providing anymore insight then what lspci would provide if the card was properly being detected.

If you have an A16AR then "lspci -v" should reveal:

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]

If the card is setup correctly, then if you run "dmesg | grep saa" you will see:

[  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]

If you're using a kernel >2.6.19 and the card is not automagically detected

If the card is not automagically detected, when you run "dmesg | grep saa" you you will see:

[   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] 

In this case, you will need to do the following steps. Type:

sudo rmmod saa7134_alsa saa7134-dvb saa7134
Note: For all those who do not know what sudo is, it is used to elevate one's self to root user. rmmod removes loaded modules from memory.

If you can't remove the running modules from memory (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 reload the modules with the following:

sudo modprobe saa7134 card=99
sudo modprobe saa7134_alsa
sudo modprobe saa7134-dvb

Now you should be able load your favorite TV application and watch TV!