<!DOCTYPE html><html><head><style type="text/css">body { font-family:'DejaVu Sans Mono'; font-size:12px}</style></head><body><div>On Fri, 29 Jul 2016 16:15:34 +1200, Stephen Worthington <stephen_agent@jsw.gen.nz> wrote:<br><br>> On Fri, 29 Jul 2016 13:53:05 +1200, you wrote:<br>><br>>><br>>> Hi all,<br>>><br>>> I'm working on a new install of mythbuntu 16.04.I have my previous <br>>> install<br>>> of 12.04 on another drive.Both systems use the same 1TB storage.I <br>>> restored<br>>> the db backup from 12.04 onto 16.04 and everything looks correct,I<br>>> carefully confirmed this against the 12.04 settings.On 16.04 I can watch<br>>> recordings and videos.I can also do channel scans with no apparent <br>>> errors.<br>>><br>>> If I try live tv I get a message saying all tuners are busy.If I try to<br>>> record a program in the guide I get a "recorder off_line" message.In the<br>>> Information menu section all tuners show "error".<br>>><br>>> The tuners are a Haupauge 2200 and a HDHR and using HDHR config GUI and<br>>> Me-TV I have confirm the tuners are working.<br>>><br>>> Mythbackend.log has a lot of these errors:<br>>><br>>> Jul 29 11:58:03 myth mythbackend: mythbackend[2547]: E ProcessRequest<br>>> mainserver.cpp:4718 (HandleRemoteEncoder) MainServer:<br>>> HandleRemoteEncoder(cmd GET_STATE) Unknown encoder: 46<br>>><br>>> Also,this may be totally unrelated, the directories and files on the<br>>> storage drive (/var/lib/mythtv) all had the owner and group listed as <br>>> ntp.<br>>> I changed this to owner: mythtv ;group:mythtv in accordance with what <br>>> the<br>>> 12.04 install has. I was getting "unable to create file<br>>> "var/lib/mythtv/recordings/.test" directory is not writable" messages on<br>>> startup.Changing the owner to mythtv eliminated these.<br>>><br>>> Any suggestions will be much appreciated.<br>>><br>>> -Paul<br>><br>> When you install a Linux system, the group ids and user ids are<br>> assigned to the various groups and users. But they can vary from one<br>> Linux install to another, even if you use the same version of Linux.<br>> So if you move a drive from one system to another, you often find that<br>> the ids do not match and you get the wrong group or user. So you may<br>> need to chown all the directories and files to what they should be.<br>> The chown command has a -R option to recurse directories, which helps.</div><div><br></div><div>The only changes in the hardware are the two system drives: an old HDD with 12.04 and a new SSD for 16.04 It isn't a duel boot I am swapping the sata cable while I'm getting 16.04 sorted.Once that is done I'll delete 12.04 off the old drive.</div><div>/var/lib/mythtv is on the 3rd drive and after changing the owner (chown -R) for 16.04 I have just found I need to change it back when I booted 12.04.It works - no problem.<br>><br>> As for your tuners, did you just restore the database without checking<br>> the order the tuners are in? Tuners can move in order between boots,<br>> and they certainly move when installed in different slots or USB<br>> ports, let alone when moved to a different motherboard. So you need<br>> to see which tuner should be on which /dev/dvb address and make sure<br>> they are on the same ones that your old system had them. This command<br>> will show you what the database says the tuner addresses are:</div><div><br></div><div>I'll have to check this.As I stated above cards and mobo have not changed.</div><div><br>><br>> select<br>> cardid,parentid,videodevice,cardtype,defaultinput,tunechan,startchan,displayname,channel_timeout<br>> from capturecard order by videodevice;</div><div><br></div><div>Are these mysql commands?<br>><br>> The videodevice field gives the address of the tuner. So then you<br>> need to use the adapter_nr option in your tuner driver setup to assign<br>> the tuners to the correct address. Not all tuners have the adapter_nr<br>> option, and if any of yours do not, you will need to use udev rules to<br>> assign them to the correct address. But check first for adapter_nr as<br>> that is much easier to use.<br>><br>> The modinfo command followed by the device driver name gives the<br>> options for drivers. Here is what my DVB-T drivers say:<br>><br>> root@mypvr:/etc/modprobe.d# modinfo dvb_usb_dib0700 | grep parm<br>> parm: force_lna_activation:force the activation of<br>> Low-Noise-Amplifyer(s) (LNA), if applicable for the device (default:<br>> 0=automatic/off). (int)<br>> parm: debug:set debugging level (1=info,2=fw,4=fwdata,8=data<br>> (or-able)). (int)<br>> parm: nb_packet_buffer_size:Set the dib0700 driver data<br>> buffer size. This parameter corresponds to the number of TS packets.<br>> The actual size of the data buffer corresponds to this parameter<br>> multiplied by 188 (default: 21) (int)<br>> parm: adapter_nr:DVB adapter numbers (array of short)<br>><br>> To use the adapter_nr option, you need to create a .conf file in<br>> /etc/modprobe.d. I have mine in options-dvb.conf. This is what I<br>> have for my tuners:<br>><br>> #Set adapter numbers for Nova-TD 500 DVB-T card (dual tuners), and<br>> AverMedia AverTV DVB-T Volar USB tuner (they use the same driver).<br>> options dvb_usb_dib0700 adapter_nr=0,1,2<br>><br>> #Set adapter number for TurboSight TBS5922 QBOX S2 DVB-S2 USB tuner.<br>> options dvb-usb-tbsqbox22 adapter_nr=3<br>><br>> #Set adapter number for TeVii S470 DVB-S2 PCIe x1 card.<br>> options cx23885 adapter_nr=4<br>><br>> Finding the name of your tuner driver can be a bit difficult. If you<br>> do not know what it is, looking through the kern.log file for what<br>> happens at boot time will normally tell you, but there are some<br>> (fortunately rare) drivers that do not actually post any messages that<br>> have the driver name in them.<br>><br>> If you can not use adapter_nr, let us know and we can try to help with<br>> udev rules.<br>><br>> It is also possible that your tuner order is stable with each boot, in<br>> which case you could just delete all your tuners in mythtv-setup and<br>> re-create them.</div><div>I did this - it did not change the problem</div><div><br></div><div>Does this apply to the HDHR as well?</div><div>Thanks for the help.I've set it back to 12.04 for the evening and will look at it again tomorrow.<br></div><div>I also ran into this bug:<a href="https://bugs.launchpad.net/ubuntu/+source/mythbuntu-common/+bug/1576767">https://bugs.launchpad.net/ubuntu/+source/mythbuntu-common/+bug/1576767</a> after changing a database setting in mythbuntu control center.It looks like that is sorted,though.</div></body></html>