I still see
this issue with latest builds (including the kernel 4.10-rc3 test build). The last good build for me was based on 4.8 kernel so I'm pretty sure that this is a linux kernel rather than a Kodi issue.
Can anyone point me in the right direction on how to build from the latest master using an older kernel?
I installed Ubuntu and I can build an image with no issues following those instructions -
https://wiki.libreelec.tv/index.php?title=Compile
However, I can't figure out how to build with an older 4.8 kernel instead of the current default 4.9. I tried to modify package.mk file but that didn't work.
#0112 boot from USB works, but now at boot is animation(logo LE and KODI) loop.
crash log here:
http://sprunge.us/cIQU
(2017-01-12, 23:57)radekson5 Wrote: [ -> ]#0112 boot from USB works, but now at boot is animation(logo LE and KODI) loop.
crash log here: http://sprunge.us/cIQU
Seems to be perhipheral/joystick related - can you try booting without any joysticks connected?
(2017-01-12, 23:48)smp1 Wrote: [ -> ]I still see this issue with latest builds (including the kernel 4.10-rc3 test build). The last good build for me was based on 4.8 kernel so I'm pretty sure that this is a linux kernel rather than a Kodi issue.
Can anyone point me in the right direction on how to build from the latest master using an older kernel?
I installed Ubuntu and I can build an image with no issues following those instructions - https://wiki.libreelec.tv/index.php?title=Compile
However, I can't figure out how to build with an older 4.8 kernel instead of the current default 4.9. I tried to modify package.mk file but that didn't work.
I'd suggest opening a thread on the LibreELEC forum - non-standard self-builds can require a fair amount of hand holding if you're not familiar with the LE build system, and that discussion would be OT for this thread. Other than reverting the linux package you may need to also revert various patches in the linux/4.8.x folder, plus you'll need the correct RPi linux backport patches for the kernel you are building, not to mention the config options. I would advise you to use the LibreELEC github history to find the patches and commits that were merged with each kernel bump since 4.8 so that you know what you need to change However building LE master with a 4.8.x kernel should be possible, it just won't be easy.
(2017-01-12, 23:17)Milhouse Wrote: [ -> ]Your core voltage (vcgencmd measure_volts core) is reading a little higher in #0109x (4.10-rc3) than it is in #0109 (4.9.2). Is dynamic frequency working with 4.10-rc3, ie. does the ARM frequency switch between 600MHz and 1200MHz according to CPU load?
Yes, dynamic frequency is working...
Time ARM Core H264 Core Temp (Max) IRQ/s RX B/s TX B/s
======== ======= ======= ======= ===============
23:16:22 1200Mhz 400Mhz 300Mhz 59.07C (59.07C) 3,432 50 179
23:16:24 1200Mhz 400Mhz 300Mhz 58.53C (59.07C) 3,446 248 125
23:16:26 1200Mhz 400Mhz 300Mhz 59.07C (59.07C) 3,431 236 320
23:16:28 1200Mhz 400Mhz 300Mhz 55.84C (59.07C) 3,541 25 127
23:16:30 600Mhz 250Mhz 250Mhz 55.84C (59.07C) 3,436 25 124
23:16:32 600Mhz 250Mhz 250Mhz 54.77C (59.07C) 3,438 102 325
23:16:34 600Mhz 250Mhz 250Mhz 54.77C (59.07C) 3,443 246 124
23:16:36 600Mhz 250Mhz 250Mhz 54.23C (59.07C) 3,439 49 178
I will investigate in further tests tomorow. Maybe the CPU load is higher in 4.10rc3 than in 4.9
(2017-01-13, 00:08)Milhouse Wrote: [ -> ] (2017-01-12, 23:57)radekson5 Wrote: [ -> ]#0112 boot from USB works, but now at boot is animation(logo LE and KODI) loop.
crash log here: http://sprunge.us/cIQU
Seems to be perhipheral/joystick related - can you try booting without any joysticks connected?
I had the same issue with a DualShock 4 controller, ended up removing device to prevent reboot loop.
(2017-01-13, 00:08)Milhouse Wrote: [ -> ] (2017-01-12, 23:57)radekson5 Wrote: [ -> ]#0112 boot from USB works, but now at boot is animation(logo LE and KODI) loop.
crash log here: http://sprunge.us/cIQU
Seems to be perhipheral/joystick related - can you try booting without any joysticks connected?
yes I can try.
Without connected joystick - boot works fine. But when I connect joystick, kodi freezes and restarts to animation boot loop.
Since the 1209 build, I've been getting an error with picture slideshow screensaver. When it displays an image, i get a round overlay over the image, a circle made up of smaller circles rotating.
This happens with both pi2 and generic.
pi log:
http://sprunge.us/USPQ
(2017-01-13, 00:34)weppa Wrote: [ -> ]I had the same issue with a DualShock 4 controller, ended up removing device to prevent reboot loop.
(2017-01-13, 00:35)radekson5 Wrote: [ -> ]Without connected joystick - boot works fine. But when I connect joystick, kodi freezes and restarts to animation boot loop.
And this issue only started with #0112? That seems a little odd... or was it also present in earlier builds (can you identify the first problem build)?
Unfortunately I did not try the Dualshock until #0109 or #0110, @
radekson5 might be able to provide more info.
Sent from my iPhone
@
radekson5 based on your crashlog, it seems to be having an issue while accessing the VFS. There is a VFS related update in #0110:
(2017-01-11, 00:21)Milhouse Wrote: [ -> ]
- XBMC:
- Add support for VFS addons (PR:8966, 4 commits, 27 files changed)
@
garbear any thoughts?
@
radekson5 & @weppa: I've uploaded a debug-enabled build #0112x which can be used to produce a more detailed crashlog:
RPi2 - this might be useful if @
garbear (or anyone else) requires it.
(2017-01-13, 02:00)khaoohs Wrote: [ -> ]Since the 1209 build, I've been getting an error with picture slideshow screensaver. When it displays an image, i get a round overlay over the image, a circle made up of smaller circles rotating.
This happens with both pi2 and generic.
pi log:
http://sprunge.us/USPQ
I assume you mean
this addon?
Any chance of a video of this behaviour?
So you don't have this problem with #1208, and the problem is first seen with #1209b? In #1209b there appears to be only a kernel bump and and minor Kodi updates.
To me, #1209b doesn't seem likely as the cause of this issue, so either it first appeared in an earlier build, or is an add-on issue (is the add-on still Kodi 18 compatible?), or maybe even a corrupt setting.
Can you also test with a clean .kodi - this will help eliminate corrupt setting and influence of any other addons:
Code:
systemctl stop kodi
mv .kodi .kodi.bak
reboot
then configure your pictures and test the slideshow.
Assuming you still have the issue, please identify the first build with the abnormal behaviour, as we should then hopefully be able to narrow down the issue.
Pinging @
ronie.
The problem I described in
Post 498 (thumbnail extraction does not work) still persists with devel-20170112210208-#0112-gd210441. Additionally I tried the latest Kodi L****** nightlies on Windows and Android. They don't have this issue.
(2017-01-13, 03:45)Milhouse Wrote: [ -> ]@radekson5 based on your crashlog, it seems to be having an issue while accessing the VFS. There is a VFS related update in #0110:
(2017-01-11, 00:21)Milhouse Wrote: [ -> ]
- XBMC:
- Add support for VFS addons (PR:8966, 4 commits, 27 files changed)
@garbear any thoughts?
@radekson5 & @weppa: I've uploaded a debug-enabled build #0112x which can be used to produce a more detailed crashlog: RPi2 - this might be useful if @garbear (or anyone else) requires it.
I had only builds #0107, #0109 and #0112. Builds #0110 and #0111 had a bug in the firmware (USB boot), and I jumped over the builds .. So that build # 0112 was the first for me where the problem began.
Now I try # 0112x for more information.
edit:
crash log on connect joysticks
http://sprunge.us/ZGBC
crash log after kodi restart loop
http://sprunge.us/UMCd
dmesg
http://sprunge.us/NPaT
1209b is the last version to NOT show this behavior, it starts in 1210.
I can install a newer version and see the issue, then revert back to 1209b and have no problems.
Link to a video of the issue
I will try the suggestions below and report back.
(2017-01-13, 03:57)Milhouse Wrote: [ -> ]I assume you mean this addon?
Any chance of a video of this behaviour?
So you don't have this problem with #1208, and the problem is first seen with #1209b? In #1209b there appears to be only a kernel bump and and minor Kodi updates.
To me, #1209b doesn't seem likely as the cause of this issue, so either it first appeared in an earlier build, or is an add-on issue (is the add-on still Kodi 18 compatible?), or maybe even a corrupt setting.
Can you also test with a clean .kodi - this will help eliminate corrupt setting and influence of any other addons:
Code:
systemctl stop kodi
mv .kodi .kodi.bak
reboot
Assuming you still have the issue, please identify the first build with the abnormal behaviour, as we should then hopefully be able to narrow down the issue.
Pinging @ronie.