AVerMedia AVerTV Hybrid+FM PCI (A16AR): Difference between revisions
(grammer) |
m (grammar!) |
||
| Line 1: | Line 1: | ||
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: |
||
[ 39.847928] saa7130/34: v4l2 driver version 0.2.14 loaded |
[ 39.847928] saa7130/34: v4l2 driver version 0.2.14 loaded |
||
| Line 11: | Line 11: | ||
==Getting it to work== |
==Getting it to work== |
||
The avermedia drivers are built into the recent kernels (Since 2.6.11 |
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: |
To make sure you have a A16AR type in "<tt>lspci -v</tt>" and you should see: |
||
01:05.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) |
01:05.0 Multimedia controller: Philips Semiconductors SAA7133/SAA7135 Video Broadcast Decoder (rev d1) |
||
Subsystem: Avermedia Technologies Inc Unknown device 2c00 |
Subsystem: Avermedia Technologies Inc Unknown device 2c00 |
||
| Line 21: | Line 21: | ||
Then type |
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) |
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/* |
fuser -v /dev/snd/* /dev/dsp/* |
||
Revision as of 22:22, 23 June 2007
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 ;)