mkreisl
commented
8 years ago Do you overclocking your RPi2?
Closed rupaschomaker closed 8 years ago
mkreisl
commented
8 years ago Do you overclocking your RPi2?
rupaschomaker
commented
8 years ago I was, but I turned off overclocking and tried again. Same problem.
rupaschomaker
commented
8 years ago I upgraded another RPI2 and it doesn't have this problem. Gonna close this one out.
vondrt4
commented
8 years ago I'm having this issue on my Raspberry Pi 1. Any clue about what may be causing it?
rupaschomaker
commented
8 years ago @vondrt - I have two rpi2 devices. One shows this and one doesn't. Only wanted kodi on one (use Nexus player for watching, RPI for indexing and dB maintenance) so use the good one.
mkreisl
commented
8 years ago Never seen this. No idea how I could help you.
Perhaps you could rename folder /home/xbian/.kodi so kodi starts with an empty configuration
vondrt4
commented
8 years ago I only have one piece and there is an MPEG2 license on it, so I would really like to keep it as long as there is MPEG2 DVB-T in this country. Then it will probably get replaced by an Orange PI or whatever comes next, because there are plans to move to HEVC DVB-T2 in about 2.5 years from now. Testing broadcasts are already running.
I could try re-imaging it, but I'd be very angry if that helped, because I have some mods on it, most importantly an unsupported build of MythTV, and would have to collect them all and install them again :-|.
What I've read, it may be absolutely anything, the asserts are enabled as long as Kodi is built with some debug flags, but the reports are mainly concerned with wrong or missing dependencies. What has changed in that regard since 15.2, which works for me?
And could the new version have greater requirements e.g. on video RAM? I have set it to 64 MB as I only do SDTV. 50 MB of ZRAM on .kodi/temp will do?
mkreisl
commented
8 years ago I could try re-imaging it, but I'd be very angry if that helped, because I have some mods on it, most importantly an unsupported build of MythTV, and would have to collect them all and install them again :-|.
Hopefully you'll have a proper backup :smile:
Re-imaging is IMO not necessary. Try moving your .kodi and see what happens. And increase your video RAM (see below)
And could the new version have greater requirements e.g. on video RAM? I have set it to 64 MB as I only do SDTV.
That' a very low value. I'm using 128MB on my RPi1's
50 MB of ZRAM on .kodi/temp will do?
32MB here
rupaschomaker
commented
8 years ago Are you seeing it fail for the exact same reason as I opened on this issue?
On Wed, Apr 6, 2016, 8:47 AM Manfred Kreisl notifications@github.com wrote:
I could try re-imaging it, but I'd be very angry if that helped, because I have some mods on it, most importantly an unsupported build of MythTV, and would have to collect them all and install them again :-|.
Hopefully you'll have a proper backup [image: :smile:]
Re-imaging is IMO not necessary. Try moving your .kodi and see what happens. And increase your video RAM (see below)
And could the new version have greater requirements e.g. on video RAM? I have set it to 64 MB as I only do SDTV.
That' a very low value. I'm using 128MB on my RPi1's
50 MB of ZRAM on .kodi/temp will do? 32MB here
— You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub https://github.com/xbianonpi/xbian/issues/812#issuecomment-206380122
vondrt4
commented
8 years ago Yes, I believe so. It's exactly the same assert failure and the process kills itself with SIGABRT. I tried adding video ram and disabling overclock, but it didn't help. I've run it as root -> without configuration, and it did the same.
The log ends after loading fonts. Maybe it is significant. kodi.txt
Looking on the net, are you building directly from source? I see that in Ubuntu they disable assembler optimizations for MathUtils:round_int and trunc_int for some reason on small architectures such as ARM. http://buildroot-busybox.2317881.n4.nabble.com/PATCH-v9-00-18-package-kodi-Bump-version-to-14-0-Helix-td88777.html --do not open in browser, too long-- http://package-import.ubuntu.com/diffs/kodi
mkreisl
commented
8 years ago @vondrt4 would be very helpful if you make an image from your installation (xbian-config->xbian copier) for investigation
mkreisl
commented
8 years ago @vondrt4 flashed your image and after some testing found the culprit for your issue: You are using composite output / sdtv
It seems that sdtv is not supported very well since kodi 16. I got it running on my Rpi1 installation, but videos are always in wrong aspect ratio (getting 'egg heads'). When using 'vanilla' kodi 16, AR is also wrong, but getting no 'egg heads', getting 'fat heads' now. Already tested kod 17, getting more issues: wrong aspect ratio and omx player always displaying black window.
So it seems you'll have to stay on 15.2 and waiting for any solution (but can't promise that there will be an solution in future)
vondrt4
commented
8 years ago That's not nice. So no more bleeding edge for me :-|. Well, there won't be much development for the Pi 1, will it? While you have the image, could you have a look at a few other bad things my instalation developed? a) Kodi 15.2 crashes when you open a long running dialog, e.g. language selection or theme selection. It may have something to do with the fact I enabled the hardware watchdog. That was because of the Afatech 9015 DVB-T dongle, which has some problems with USB transfers dropping out, after which the whole USB subsystem sometimes freezes, about once a week. You helped me debug that by building a kernel with Netconsole, if you remember. It also reboots when I select Exit Kodi in its main screen. b) xbian-config, the curses set-up program, is broken. There are menu entries interleaved with numbers. And I did upgrade regularly. c) And have a look at the way I modified the xbmc start-up scripts. They are disabled and there is a curses prompt called askxbmc.sh spawned on the first console which lets you (by default, just by pressing Enter) launch Kodi, or drop to the shell (and use xinit from there). I think it is a good idea. My Raspberry mostly runs as MythTV backend and more CPU usage from Kodi means more dropped USB frames, so I launch it only when I need it.
All in all, I have found that the Raspberry Pi is a bad choice for a TV headend / PVR. Is the version 2 or 3 better? If you, e.g., dedicate one core to interrupts, it could work without dropouts..
vondrt4
commented
8 years ago @mkreisl
It seems that sdtv is not supported very well since kodi 16.
You were talking about wrong aspect ratios, but my problem is that I cannot launch Kodi 16 at all.
Progress: Flashed a clean Xbian image - the same error. Flashed a clean image of two major competitors od Xbian - both worked. Finally: Installed Kodi 16.1 from OSMC over Xbian - the same firmware, kernel, library environment - works. You build of Kodi must have something set the wrong way.
And I have tried playing a 16:9 and 4:3 movie on my 4:3 TV and had no aspect ratio problems.
mkreisl
commented
8 years ago @vondrt4 Please try this version http://apt.xbian.org/pool/devel/rpi-jessie/x/xbian-package-xbmc/xbian-package-xbmc_16.1-1462796680_armhf.deb and report back.
This version works in standard environment (1080p HDMI) and should work with SDTV also (can not test it with RPi1, but build for RP2 works here)
mkreisl
commented
8 years ago This is test version for RPi2 and RPi3 http://apt.xbian.org/pool/devel/rpi2-jessie/x/xbian-package-xbmc/xbian-package-xbmc_16.1-1462731607_armhf.deb
vondrt4
commented
8 years ago Yes, this version (RPi1) starts fine, plays video with correct aspect ratio (on 4:3 TV), and crashed once on some Czech TV video plugin that blocked for too long (with watchdog). Overall, it's not worse than 15.2 :-).
Rpi 2, running staging though saw the same with stable: