Contents

Quick start

The *latest revision*(PCI ID 1461:f31f) of the Avermedia AVerTV GO 007 FM works "out of the box" in recent kernels. Earlier revisions WILL work, but you must currently use them once on Windows with the official drivers to load the internal EEPROM, and manually specify the card type as 57 and tuner as 54. Otherwise, to prepare the card to work, type in two lines:

It may work better some day, but for now I had to stick to saa7134-oss module. In a matter of fact modprobe saa7134 may be totally skipped, because while probing for saa7134-oss or saa7134-alsa the main module will be automatically loaded in the background.

The hardware is now perfectly ready, but although you can watch TV, the sound is still not there. As found in AVerMedia Cardbus E500 instructions I did the simple trick, which dumps the sound from TV card (/dev/dsp1) to the real sound card (/dev/dsp):

MythTV and AC '97 Issues (SBLive)

With the equivalent Bona/Mentor TV-PCI card connected via the line input of a Creative Labs Sound Blaster Live! Platinum sound card, I had some issues getting MythTV to capture the audio. The tvtime application worked flawlessly without any of these procedures. I couldn't get the audio working for MythTV with the saa7134-alsa module and the sox workarounds.

On every boot-up, the card must be unmuted and the automute turned off. Some people had the same problems in similar reports for the Avermedia card. Consider putting the following on a boot-up script.

v4lctl setattr automute off
v4lctl setattr mute off

For the Sound Blaster Live card, the AC '97 volume playback control (through a card mixer, such as alsamixer) is to be completely put to 0 (zero), or else you hear the audio being played back twice (loopback). The AC '97 volume capture control should be put as high as possible. This information can be found in the Linux kernel documentation in the Documentation/sound/alsa/SB-Live-mixer.txt file.

I also had issues with the audio captured with MythTV because I was hear crackling noises constantly. The reason was how loaded the system was, so I reduced the capture resolution and quality, as put audio at 32kHz.