2017-02-18, 11:23
(2017-02-17, 23:21)Milhouse Wrote:(2017-02-17, 10:41)esco Wrote:(2017-02-14, 21:05)Milhouse Wrote: Can you provide log information? "journalctl -a", "dmesg" and "kodi.log"?
Is #0101 the last build that has this working mux, or just the last working build you've used? Can you identify when this mux problem started in the normal daily builds?
We switched to using the media_build package in #0108 so you might be able to confirm that is when the problem started (ie. #0107 works, #0108 doesn't).
#0107 is fine, no issues at all. With #0108 I am able to scan muxes (however some "poll timeout" errors appear) but unable to watch TV - the log is full of MPEG2AUDIO/ H264 "Invalid start code" and "Continuity counter" errors. Am I supposed to send the logs with the latest #____x build?
Thank you.
Logs from latest build is fine, yes. In build #0108 we switched to the media_build package for DVB support so it's possible some hardware isn't fully supported in the media_build package. This will need input from a media_build expert - post your logs and I'll ping someone.
As requested:
dmesg: http://pastebin.com/f1DCtsZa
journal: http://pastebin.com/p52rvz6t
kodi.log http://pastebin.com/91sid8Z2
Thank you Milhouse.
