Tvheadend

greg kimnach wrote:

I discovered that TVH is not a service (i.e., not listed in /etc/init.d or with "service --status-all") and, therefore, cannot be stopped or restarted (e.g., "sudo systemctl stop tvheadend" results in "Failed to stop tvheadend.service: Unit tvheadend.service not loaded."). If I pkill TVH, then after restarting it I cannot log back into the web interface. So, if there is another app using the adapters and causing TVH to not load them, then I am at a loss.

Debian and Ubuntu ten years ago start to use service command to control services read systemd vs init
So rediscover Linux

service tvheadend start/stop/restart/status

pkill on multithreaded application ??? whay not killall

What OS you used before redhat/slackware with kernel 2.13 ?

If TVH not get tuners then some other software use it.

lsof /dev/dvb/adapter0/frontend0

thanks for the response.

let me simplify the course of actions, without the HDHomerun connected to the network. Only the two types of internal Hauppauge cards are installed.

1) clean install of Ubuntu 19.04 by erasing disk with the minimal packages installation
2) copy WinTV-HVR-1600 and -2250 firmware files to /lib/firmware
2a) tried all of the listed steps with and without adding "options saa7164 card=8" to /etc/modprobe.d/options
3) lspci results in
Multimedia video controller: Conexant Systems, Inc. CX23418 Single-Chip MPEG-2 Encoder with Integrated Analog Video/Broadcast Audio Decoder
Multimedia video controller: Conexant Systems, Inc. CX23418 Single-Chip MPEG-2 Encoder with Integrated Analog Video/Broadcast Audio Decoder
Multimedia controller: Philips Semiconductors SAA7164 (rev 81)
4) install TVH from via Ubuntu Software (NOTE that no other software which should grab the tuners is installed!)
3a) Configure
3b) No TV Adapters listed under the Congig>DVB Inputs tab
5) Try--among others, including example I gave above--to stop the TVH "service":
service tvheadend start
Failed to start tvheadend.service: Unit tvheadend.service not found.
6) Output of "ls /etc/init.d" is:
acpid avahi-daemon cups-browsed hwclock.sh networking pppd-dns speech-dispatcher uuidd
alsa-utils bluetooth dbus irqbalance network-manager procps spice-vdagent whoopsie
anacron console-setup.sh dns-clean kerneloops openvpn rsync udev x11-common
apparmor cron gdm3 keyboard-setup.sh plymouth rsyslog ufw
apport cups grub-common kmod plymouth-log saned unattended-upgrades
NOTE TVH not in there
7) Go into the Ubuntu Software folder and hit "Launch" TVH and terminal window pops up with among other lines:
[ ERROR] linuxdvb: unable to open /dev/dvb/adapter3/frontend0
[ ERROR] linuxdvb: unable to open /dev/dvb/adapter2/frontend0
[ ERROR] linuxdvb: unable to open /dev/dvb/adapter1/frontend0
[ ERROR] linuxdvb: unable to open /dev/dvb/adapter0/frontend0
8) pkill (this did not output an error, unlike "service tvheadend stop", for example)
9) then try to restart with
service tvheadend start
Failed to start tvheadend.service: Unit tvheadend.service not found.
10) Re-launch from Ubuntu Software:
terminal pops up with
[ ERROR] linuxdvb: unable to open /dev/dvb/adapter3/frontend0
[ ERROR] linuxdvb: unable to open /dev/dvb/adapter2/frontend0
[ ERROR] linuxdvb: unable to open /dev/dvb/adapter1/frontend0
[ ERROR] linuxdvb: unable to open /dev/dvb/adapter0/frontend0
and the web interface does not recognize the password.
11) Install Kaffeine from Ubuntu Software and the four tuners (two from the 2250, and one each from the two 1600) are recognized, configured, and tune in stations.
12) Repeat steps above, with same results, using the full Ubuntu 19.04 installation.
13) The command "lsof /dev/dvb/adapterX/frontend0" (for X=0,1,2, and 3) lists nothing!
greg@HTPC:~$ lsof /dev/dvb/adapter0/frontend0
greg@HTPC:~$

Again, what baffles me is that there is no other s/w that should be using the tuners until after I install Kaffeine!
As Foreigner sang: Headknocker.

Perhaps I'll just go back to 18.04LTS and determine which patch inhibits Kodi from displaying anything at all.

BTW: Ubuntu 16.04 was the first distro that I used for any given amount of time, and I am by no means a "linux user." I just google as I stumble across issues on my HTPC--hence the use of pkill as a last resort. I had previously only dabbled with linux on my Amiga (early 90s) and tried a few distros here and there prior to 16.04. Not sure why you asked about redhat/slackware.

thanks again.

May I guess that you use SNAP packages and Desktop Ubuntu

https://forum.snapcraft.io/t/supported-interfaces/7744
https://forum.snapcraft.io/t/new-interface-requirement-dvb/3497

sudo rm -rf /var/cache/snapd/

sudo apt autoremove --purge snapd gnome-software-plugin-snap

sudo rm -fr ~/snap