[mythtv-users] Getting it to Work > Hauppauge WinTV-quadHD (DVB-T/T2/C)

[Stephen Worthington]

On Fri, 11 Nov 2016 14:11:19 -0500, you wrote:

>Ok i am having the same issue with the atsc model 01609 it only works with
>the 4.9rc1 kernel. I am stuck with the 4.4.0.47 kernel in linux mint. I
>have a rx460 card and the amdgpu-pro driver only works with it. Can not use
>open-source because no sound until dal is sorted out. I have tried what you
>had listed had to  change it a little but, I did get all my tuners working
>by backporting build from git.
>
>The only issue now is I have to cd into media_build folder an run  sudo
>make load every reboot. other wise they dont load at startup.this is what i
>did
>
>git clone git://linuxtv.org/media_build.git
>cd media_build
>./build
>
>sudo make install
>
>
>sudo make unload
>
>sudo make load
>
>It work fine until i reboot that is when i have to
>cd media_build
>sudo make load
>then it works how do i get it to load at boot?

That sounds like you need a modprobe line to load the driver.  In
Ubuntu, to get modprobes done at boot you put a .conf file in
/etc/modprobe.d and put the appropriate modprobe line inside it.  The
name of the .conf file only matters if the order of loading of the
drivers matters, as the .conf files are read in alphanumeric order.
Files in /etc/modprobe.d should be chown root:root and chmod a=r,u=rw.
As many drivers as you like can be loaded in each .conf file, and
there are other commands such as "blacklist" that can be used there
also.  See "man modprobe.d".

In order to work out the correct modprobe command, you first need to
know the name of the driver you need to load.  You work that out by
various means, starting with looking at the logs (dmesg, kern.log,
syslog, or using the journalctl command on systemd systems).  Drivers
do not always identify themselves in a log though - you can have to
google for an answer.  The driver files are *.ko files, found under
/lib/modules/$(uname -r).  Once you know the name of the driver you
want, do a "modinfo <drivername>".  The modinfo command with
<driverfile>.ko will show the information about any driver file you
provide the path to, and with just the driver name without path or .ko
will show the information about that driver in the current kernel
installation.  At the bottom of the modinfo output is normally a list
of parameters that can be given to the driver.  These are put in the
/etc/modprobe.d .conf file you are creating.

For each driver you want to load, you add a line in your .conf file
like this:

options <drivername> <driver options>

The <drivername> does not have the .ko on it.  The <driver options> is
a space separated list of the options that modinfo showed were allowed
for the driver.  It is optional - if there are no options specified,
the driver will load with its default options.  Good tuner drivers
will always have an "adapter_nr" option to allow specification of the
adapter number or numbers for the devices it creates under /dev.  As
an example, here is my current /etc/modprobe.d/options-dvb.conf file
from my test PC:

# KWorld DVB-T TV Stick II 395UR USB tuner.
options dvb_usb_af9015 adapter_nr=0

# Pinnacle PCTV Nano Stick 73e USB tuner.
options dvb_usb_dib0700 adapter_nr=1

# TBS5922 QBOX S2 DVB-S2 USB tuner.
options dvb-usb-tbsqbox22 adapter_nr=3

# Set number of loopback adapters for use with sasc-ng/ffdecsawrapper
card decryption software, and set the adapter numbers to use.
options dvbloopback num_adapters=2 adapter_nr=5,6 dvblb_debug=3

# TBS6909 8 tuner DVB-S2 card
options mxl5xx mode=1 inputs=3,3,3,3
options tbsecp3 adapter_nr=3,4,7,8,9,10,11,12

# vtuner virtual devices, for SAT>IP
options vtunerc adapter_nr=13,14,15,16,17,18,19,20 devices=8 tscheck=1
debug=1

Note that in the above, I have two different tuners with adapter_nr=3
specified.  The TBS5922 is a USB tuner that is not plugged in at the
moment, so this does not cause any problems.  If an adapter_nr is
already taken, the driver will just put itself on the next available
adapter_nr.

From the command line, you can also load drivers in the same way,
using a modprobe command.  So to load my TBS5922 from the command
line, I would use:

modprobe dvb-usb-tbsqbox22 adapter_nr=3

Such modprobe commands can be used, for example, in /etc.rc.local or
in systemd .service files.

However, most drivers will normally load anyway if their hardware is
present, without any specific modprobe commands.  But to do that, the
tables for driver dependencies have to be set up.  I thought that the
"make install" command would be doing that automatically, but if it is
not, you can just try manually doing it, then rebooting and seeing if
the drivers load automatically.  The command to rebuild the driver
dependency tables is "depmod".