[mythtv-users] Indoor HD antenna question

[Stephen Worthington]

On Fri, 13 Apr 2018 14:26:59 +0000, you wrote:

>On Thu, Apr 12, 2018 at 11:03 PM Stephen Worthington <
>stephen_agent at jsw.gen.nz> wrote:

>
>> When you get messages like the ones you are getting such as "disagrees
>> about version of symbol snd_ctl_add" and then "Unknown symbol
>> snd_ctl_add", it normally means that your drivers are not compatible
>> with your kernel version and need to be recompiled for the current
>> kernel.  The symbol table for that symbol now says it has a different
>> size or format in the kernel from what your driver file has in its
>> symbol table.  Since the drivers for your card are supposed to be
>> built into the kernel, that should not be happening.
>>
>
>Is this maybe because the antenna wasn't connected at the time? Or should
>the driviers showing up regardless?

No, the drivers should load without any aerial connected.

But - the Avermedia AVerTVHD card is the one with the saa7134 chip, so
the problem is with the drivers for that card.  Which is not the tuner
you are trying to use in MythTV.  The ATSC tuner, Air2PC v2, does not
use that driver, and should therefore not be affected by the problem
with the saa7134 driver.  If the AVerTVHD tuner was working, I would
expect that you would have two tuners showing up as /dev/dvb/adapter0
and /dev/dvb/adapter1.

I do have to wonder what on Earth someone in North America is doing
with a DVB-T tuner that can not receive the TV in that part of the
world.  Maybe it is the tuner that has a decent remote control?  The
remote is not tied to the tuner - they are separate devices and the
remote probably works even though the AVerTVHD tuner driver is not
loading.  Although I would have thought that the PVR-150 tuner would
have the best remote, if it was the model that came with one.  My
PVR-500 (dual PVR-150) came with the excellent remote I am still using
even though the PVR-500 itself is long retired.

>>
>> However, it is possible that those messages are referring to a
>> different device, as you did not post enough of your logs to be able
>> to tell.  It might be a good idea to post the entire section of the
>> logs from start of bootup until the system is running.  Put it on
>> pastebin.com and post a link.
>>
>> Is it possible you have other DVB devices in that PC?  The name
>> "Air2PC v2" does not match an AverMedia card.  That name appears to be
>> for a TecniSat ATSC USB tuner for the US market:
>>
>> https://www.linuxtv.org/wiki/index.php/TechniSat_Air2PC-ATSC-USB
>>
>> What does this command show:
>>
>> ls -al /dev/dvb
>>
>
>ls -al /dev/dvb
>total 0
>drwxr-xr-x  3 root root   60 Mar 29 04:37 .
>drwxr-xr-x 23 root root 4140 Apr  9 20:01 ..
>drwxr-xr-x  2 root root  120 Mar 29 04:37 adapter0
>
>
>>
>> So where are you - are you trying to receive DVB-T signals (eg UK,
>> Europe, Australia, New Zealand) or are you trying to receive ATSC
>> (USA)?
>> ___________
>
>
>I am in US - Chicago area.

I am going to make a wild guess here, as to what your real problem is.
I think that you have your aerial connected to the one of the PCI
cards in your PC.  You have two that have aerial connectors, the
PVR-500 and the AVerTVHD.  Neither of which is the correct tuner to
have the aerial cable on.  The ATSC tuner, the only one that will now
work for you, is a USB tuner.  So it will be on the end of a USB cable
plugged into one of the PC's USB ports, which might even be on the
front of the PC instead of the back.  It is also possible that it is
draped somewhere inside the PC with its USB connected to a header on
the motherboard internally.  So you need to find it and plug the
aerial into it.