<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 14, 2018, at 1:10 PM, Ashu Desai <<a href="mailto:ashu.desai@gmail.com" class="">ashu.desai@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class=""><div class=""><br class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Sat, Apr 14, 2018, 3:41 AM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz" class="">stephen_agent@jsw.gen.nz</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sat, 14 Apr 2018 09:01:11 +0100, you wrote:<br class="">
<br class="">
>On 14/04/18 05:23, Stephen Worthington wrote:<br class="">
>> On Fri, 13 Apr 2018 20:32:52 +0000, you wrote:<br class="">
>> <br class="">
><br class="">
>> <br class="">
>> The "demux0 dvr0 frontend0 net0" devices are all correct for a<br class="">
>> normal DVB or ATSC tuner. What we are not sure of now is if they all<br class="">
>> work correctly. Trying the "scan" command should tell us whether the<br class="">
>> tuner works at a basic level, and then if that works, once scan has<br class="">
>> created a channels.conf file, that can be used with an "azap -r<br class="">
>> <channel name>" command to tune the tuner to one channel and make that<br class="">
>> play on the /dev/dvb/adapter0/dvr0 device. You leave azap running and<br class="">
>> in another command prompt run a command line player program like<br class="">
>> mplayer to play from the dvr0 device:<br class="">
>> <br class="">
>> mplayer /dev/dvb/adapter0/dvr0<br class="">
>> <br class="">
>> Mplayer should pop up a window and play the channel. It will also log<br class="">
>> to the console to show what is happening, and tell us what went wrong<br class="">
>> if it can not play the channel.<br class="">
><br class="">
>The centosplus kernel is, IIRC, an el6 kernel with extra drivers for <br class="">
>non-el-type stuff like multimedia. The current kernel is<br class="">
><br class="">
><a href="http://mirror.centos.org/centos/6/centosplus/x86_64/Packages/kernel-2.6.32-696.23.1.el6.centos.plus.x86_64.rpm" rel="noreferrer noreferrer" target="_blank" class="">http://mirror.centos.org/centos/6/centosplus/x86_64/Packages/kernel-2.6.32-696.23.1.el6.centos.plus.x86_64.rpm</a><br class="">
><br class="">
>with a build date of 2018-03-14, probably for the spectre security fix.<br class="">
><br class="">
>Your dmesg shows<br class="">
><br class="">
>Linux version 2.6.32-220.17.1.el6.centos.plus.x86_64 <br class="">
>(<a href="mailto:mockbuild@c6b5.bsys.dev.centos.org" target="_blank" rel="noreferrer" class="">mockbuild@c6b5.bsys.dev.centos.org</a>) (gcc version 4.4.6 20110731 (Red <br class="">
>Hat 4.4.6-3) (GCC) ) #1 SMP Wed May 16 05:20:13 BST 2012<br class="">
><br class="">
>I doubt that saa7134 stuff has been updated much since then, but<br class="">
>you probably ought to think about doing some updating, anyway :-)<br class="">
<br class="">
2.6!!!! Is that really the kernel version? That is ancient! There<br class="">
has been a lot of development of V4L since then, so I hope it has<br class="">
updates for that. My Mythbuntu 16.04 LTS is running<br class="">
4.4.0-119-generic, and that is quite old - the new 18.04 LTS build is<br class="">
due out in a few days and will be running 4.15.<br class=""></blockquote></div></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Yes. it is old. I am afraid of breaking my "working" backend if I try to upgrade so I am shying away from an upgrade. I have been using this only for movies (videos), music and pictures (nothing a plex server won't do - but I love my association with myth and the community and it gives me a chance to learn new stuff and expand my limited Linux knowledge)</div><div dir="auto" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="">
Not to mention that a kernel that old will not run SSDs properly (no<br class="">
TRIM), and will not run NVMe SSDs at all. And will likely not work<br class="">
with shingled drives like my 8 TByte Seagates. And will not work<br class="">
properly with new CPUs like Ryzens.<br class=""></blockquote></div></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">I have it working with my 8Tb drive and raided 8Tb mount. but I should upgrade, just scared...</div><div dir="auto" class=""><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
_______________________________________________<br class="">
mythtv-users mailing list<br class="">
<a href="mailto:mythtv-users@mythtv.org" target="_blank" rel="noreferrer" class="">mythtv-users@mythtv.org</a><br class="">
<a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer noreferrer" target="_blank" class="">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a><br class="">
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer noreferrer" target="_blank" class="">http://wiki.mythtv.org/Mailing_List_etiquette</a><br class="">
MythTV Forums: <a href="https://forum.mythtv.org/" rel="noreferrer noreferrer" target="_blank" class="">https://forum.mythtv.org</a><br class="">
</blockquote></div></div></div>
_______________________________________________<br class="">mythtv-users mailing list<br class=""><a href="mailto:mythtv-users@mythtv.org" class="">mythtv-users@mythtv.org</a><br class="">http://lists.mythtv.org/mailman/listinfo/mythtv-users<br class="">http://wiki.mythtv.org/Mailing_List_etiquette<br class="">MythTV Forums: <a href="https://forum.mythtv.org" class="">https://forum.mythtv.org</a><br class=""></div></blockquote><br class=""></div><div>I don’t see a reason to fear an upgrade, really. I recently jumped from CentOS 6 and 0.27 to CentOS 7 and v29, compiling from source, and all works well. The only thing I would like to do is use the custom “driver” for HDPVR2 recording, which requires some packages I couldn’t locate and haven’t had time to pursue, but other than that, it was a simple, direct upgrade. Backup your database, and go to town.</div><div><br class=""></div><div>Mike</div><br class=""></body></html>