[mythtvnz] New install setup - recording problem

[Paulgir]

> Mythbackend seems to be saying it can not see
> /dev/dvb/adapter0/frontend0. But presumably mythtv-setup can see the
> device, or it could not scan for channels. Does
> /dev/dvb/adapter0/frontend0 show up if you look for it with the ll or
> ls commands? What do these commands show:
>
> ll /dev/dvb
> ll /dev/dvb/adapter0
> ll /dev/dvb/adapter1
>
> What permissions does mythbackend have? What does this command show:
>
> ps -ef | grep myth
>
> That should show how mythbackend is being run (in particular, as which
> user).
>
> There is also one obvious problem in that log snippet. Both Card 1
> and Card 2 are referencing adapter0/frontend0. I do not know how the
> HVR-2200 does its devices, but there should be either two completely
> separate devices /dev/dvb/adapter0 and /dev/dvb/adapter1 or one device
> with two frontends, /dev/dvb/adapter0/frontend0 and
> /dev/dvb/adapter0/frontend1. Both Card1 and Card2 should not be using
> the same frontend device /dev/dvb/adapter0/frontend0.
>
> Also, check that the firmware for the card is installed (see
> https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-2200). Does
> it show up in the logs as being loaded? There are some cards that
> will do a channel scan but will not record without the firmware. But I
> would have expected it to fail in Me-TV if that was the case.
>
> How does Me-TV run? Is it running when mythbackend tries to access
> the devices? If so, it could own the devices and not be allowing
> mythbackend access. Is there any other TV software installed that
> could be using the devices?
>

Firmware is installed as per the wiki.
The log snippet was recorded prior to MeTV installation (this time).So I  
did extensive testing without MeTV installed.
I have a complete backend.log from a restart onwards that you can look  
at:https://drive.google.com/open?id=0B5RRWPLTmilhN3Bta2xmQWEwQU0

One thing I haven't mentioned much is that 16.04 is on a SSD and 12.04 is  
on a slow HDD.I saw mention online that problems have been seen if  
mythbackend starts before the capture cards can initialise.So far none of  
the fixes I have found work for this install.

~$ ll /dev/dvb
total 0
drwxr-xr-x 4 root root 80 Aug 11 13:57 ./
drwxr-xr-x 22 root root 4580 Aug 11 13:57 ../
drwxr-xr-x 2 root root 120 Aug 11 13:57 adapter0/
drwxr-xr-x 2 root root 120 Aug 11 13:57 adapter1/

~$ ll /dev/dvb/adapter1
total 0
drwxr-xr-x 2 root root 120 Aug 11 13:57 ./
drwxr-xr-x 4 root root 80 Aug 11 13:57 ../
crw-rw----+ 1 root video 212, 5 Aug 11 13:57 demux0
crw-rw----+ 1 root video 212, 6 Aug 11 13:57 dvr0
crw-rw----+ 1 root video 212, 4 Aug 11 13:57 frontend0
crw-rw----+ 1 root video 212, 7 Aug 11 13:57 net0

~$ ll /dev/dvb/adapter0
total 0
drwxr-xr-x 2 root root 120 Aug 11 13:57 ./
drwxr-xr-x 4 root root 80 Aug 11 13:57 ../
crw-rw----+ 1 root video 212, 1 Aug 11 13:57 demux0
crw-rw----+ 1 root video 212, 2 Aug 11 13:57 dvr0
crw-rw----+ 1 root video 212, 0 Aug 11 13:57 frontend0
crw-rw----+ 1 root video 212, 3 Aug 11 13:57 net0

~$ ps -ef | grep myth
avahi 1971 1 0 13:57 ? 00:00:00 avahi-daemon: running [mythpc.local]
mythpc 2397 1 0 13:57 ? 00:00:00 /lib/systemd/systemd --user
mythpc 2398 2397 0 13:57 ? 00:00:00 (sd-pam)
mythpc 2402 2391 0 13:57 ? 00:00:00 /bin/sh /etc/xdg/xfce4/xinitrc --  
/etc/X11/xinit/xserverrc
mythpc 2448 2402 0 13:57 ? 00:00:00 /usr/bin/ssh-agent  
/usr/bin/dbus-launch --exit-with-session /usr/share/mythbuntu/session.sh
mythpc 2451 1 0 13:57 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session  
/usr/share/mythbuntu/session.sh
mythpc 2452 1 0 13:57 ? 00:00:00 /usr/bin/dbus-daemon --fork --print-pid 5  
--print-address 7 --session
mythpc 2464 2402 0 13:57 ? 00:00:00 xfce4-session
mythpc 2468 1 0 13:57 ? 00:00:00  
/usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd
mythpc 2472 1 0 13:57 ? 00:00:00 gnome-keyring-daemon --start
mythpc 2477 1 0 13:57 ? 00:00:00 xfwm4
mythpc 2479 1 0 13:57 ? 00:00:01 xfce4-panel
mythpc 2481 1 0 13:57 ? 00:00:05 Thunar --daemon
mythpc 2483 1 0 13:57 ? 00:00:00 xfdesktop
mythpc 2488 2464 2 13:57 ? 00:01:03 /usr/lib/vino/vino-server --sm-disable
mythpc 2492 2464 0 13:57 ? 00:00:00 update-notifier
mythpc 2493 2464 0 13:57 ? 00:00:00  
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
mythpc 2495 2464 0 13:57 ? 00:00:00 xscreensaver -no-splash
mythpc 2505 2464 0 13:57 ? 00:00:00 nm-applet
mythpc 2508 1 0 13:57 ? 00:00:00 xfce4-volumed
mythpc 2512 1 0 13:57 ? 00:00:00 /usr/bin/pulseaudio --start  
--log-target=syslog
mythpc 2518 1 0 13:57 ? 00:00:00 xfsettingsd
mythtv 2521 1 0 13:57 ? 00:00:03 /usr/bin/mythbackend --quiet --syslog  
local7
mythpc 2559 1 0 13:57 ? 00:00:00 /usr/lib/gvfs/gvfsd
mythpc 2575 1 0 13:57 ? 00:00:00 /usr/lib/at-spi2-core/at-spi-bus-launcher
mythpc 2581 2575 0 13:57 ? 00:00:00 /usr/bin/dbus-daemon  
--config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
mythpc 2584 1 0 13:57 ? 00:00:00 /usr/lib/at-spi2-core/at-spi2-registryd  
--use-gnome-session
mythpc 2606 1 0 13:57 ? 00:00:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
mythpc 2610 2479 0 13:57 ? 00:00:00  
/usr/lib/x86_64-linux-gnu/xfce4/panel/wrapper-1.0  
/usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libsystray.so 4 12582955  
systray Notification Area Area where notification icons appear
mythpc 2703 1 0 13:57 ? 00:00:00 /usr/lib/x86_64-linux-gnu/notify-osd
mythpc 3095 1 0 13:57 ? 00:00:00 /usr/lib/gvfs/gvfsd-metadata
mythpc 3099 1 0 13:57 ? 00:00:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.13  
/org/gtk/gvfs/exec_spaw/0
mythpc 3113 1 0 13:58 ? 00:00:00 /usr/lib/dconf/dconf-service
mythpc 3601 1 0 14:27 ? 00:00:00 /usr/lib/x86_64-linux-gnu/gconf/gconfd-2
mythpc 3857 2479 0 14:39 ? 00:00:01 xfce4-terminal
mythpc 3861 3857 0 14:39 ? 00:00:00 gnome-pty-helper
mythpc 3862 3857 0 14:39 pts/0 00:00:00 bash
mythpc 3929 3862 0 14:43 pts/0 00:00:00 ps -ef
mythpc 3930 3862 0 14:43 pts/0 00:00:00 grep --color=auto myt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ourshack.com/pipermail/mythtvnz/attachments/20160811/5f3b217f/attachment-0001.html>