[mythtv-users] upgrading to kenel 3.16? (PCTV 292e triplestick supported)

[Mike Perkins]

On 01/09/14 10:31, Andre Newman wrote:
>
> On 31 Aug 2014, at 22:38, Mike Perkins <mikep at randomtraveller.org.uk> wrote:
>
>> I've been using a T290e for two years now on a stock Debian Wheezy server with no problems at all. Don't overlook other factors like location, heat, cable / connector quality, signal strength and so on.
>
> This is interesting, I’ve been trying to get this running stably for some time.
>
> Location is in free air using the short extension cable.
>
> It’s not getting hot.
>
> The cabling and connectors are very high grade, well screened, I work with satellite uplink guys so I tend to use their offcuts for home stuff.
>
> Signal strength is very good, it’s a communal system I specified, in fact I’ve tried testing with attenuators in case there is too much signal.
>
> I also used the same T290e over at a friend’s place to capture the BBC Ultra HD tests from the World Cup and Commonwealth Games. It was used on a laptop running Ubuntu 14.0.4 built specially for the task and I had to reboot three times over the 4 or 5 week period of those two events. This was using TVHeadend to record as MythTV doesn’t know about H265 yet so I can’t blame MythTV code triggering a problem.
>
> I’ve discovered that swapping USB ports until I find one that gets it’s own interrupt makes it more reliable and it was even better with none of the other USB ports used but that’s not really a viable solution.
>
> The only other discovery I had was that the stock 12.0.4 kernel (3.2.something) gave glitchy recordings, upgrading to the HWE kernel 3.5.something fixed that and also the current 12.0.4.5 Trusty HWE kernel is ok too, 3.13.0-32.
>
> Mike what USB chip does your system have, I think that might be a big factor? Mine is an Intel 82801JI (ICH10).
>
> Andre
>
As my system is 24/7 it may be a short while before I can verify the chip 
details for you. In the meantime:

micheal at ruby:~$ uname -a
Linux ruby 3.2.0-4-amd64 #1 SMP Debian 3.2.60-1+deb7u1 x86_64 GNU/Linux
micheal at ruby:~$

micheal at ruby:~$ mythbackend --version
Please attach all output as a file in bug reports.
MythTV Version : v0.26.1
MythTV Branch :
Network Protocol : 75
Library API : 0.26.20131221-1
QT Version : 4.8.2
Options compiled in:
  linux profile use_hidesyms using_alsa using_jack using_oss using_pulse 
using_pulseoutput using_backend using_bindings_perl using_bindings_python 
using_bindings_php using_crystalhd using_dvb using_firewire using_frontend 
using_hdhomerun using_ceton using_hdpvr using_iptv using_ivtv 
using_joystick_menu using_libcec using_libcrypto using_libdns_sd using_libfftw3 
using_libxml2 using_lirc using_mheg using_opengl_video using_qtwebkit 
using_qtscript using_qtdbus using_v4l2 using_x11 using_xrandr using_xv 
using_bindings_perl using_bindings_python using_bindings_php using_mythtranscode 
using_opengl using_vaapi using_vdpau using_ffmpeg_threads using_live using_mheg 
using_libass using_libxml2
micheal at ruby:~$

There are also two Hauppuage Nova-T USB sticks in there and all appear to be 
connected to the same USB motherboard hub. Despite this, I have (infrequently) 
recorded using all three at once with no problems.

Fortunately or unfortunately, depending on one's point of view, I'll have to 
take the system down to retune on Wednesday, since apparently some changes to 
EIT are causing some channels to move muxes (WTF?). I'll take the opportunity to 
open it up and give it a thorough clean, etc. and I can give you details of 
motherboard and chipset, etc. Don't expect anything fancy.

You'll notice the old mythtv version. When I take the system down I'll rebuild 
it using the deb-multimedia/backports repository to get 0.27-something. We'll 
see if that makes any difference.

-- 

Mike Perkins