+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Skins Support (https://forum.kodi.tv/forumdisplay.php?fid=67)
+---- Forum: Aeon Nox: Silvo (https://forum.kodi.tv/forumdisplay.php?fid=142)
+---- Thread: Bug Screen goes blank after refresh rate switches back from 24hz to 60hz (/showthread.php?tid=331836)
Screen goes blank after refresh rate switches back from 24hz to 60hz - N01tra - 2018-05-12
Hi,
I upgraded my NUC from a 2820 celeron and ubuntu 16.04 to an new J4005 celeron (7CJYH) with Ubuntu 18.04.
When using the Aeon Nox skin, my TV screen goes blank (blue) when I stop a movie and the refreshrate goes from 24hz back to 60hz (I use change refreshrate on start/stop).
When I switch from the NUC's HDMI-1 to HDMI-2 output, the screen goes back to normal.
I'v tested this procedure with a few other skins and they don't have this issue.
In short:
NUC7CJYH
Ubuntu 18.04
Kodi 17.6 - Aeon Nox skin
Blank screen on refresh rate switch; 24hz to 60hz
Reproducibleon:
- Arctic: Zephyr
Not reproducible
- Estuary
Here is my debug log:
https://paste.ubuntu.com/p/cD7Hkzpr92/
-- edit / update
Turns out, it's a known issue: https://bugs.freedesktop.org/show_bug.cgi?id=105887#c17
However; it is strange it seems to be skin related in my case. Also, HD and SD seems to make a difference.
RE: Screen goes blank after refresh rate switches back from 24hz to 60hz - Roby77 - 2018-05-30
Yes it's a known issue (almost for me)
I have also this problem(with krypon and Leia) on my beebox N3150 connected through my avr with edid forced
Already opened a bug note on free desktop already one year ago with no luck
RE: Screen goes blank after refresh rate switches back from 24hz to 60hz - N01tra - 2018-05-30
In my case, it was a bug related to the GeminiLake hardware (J4005 / J5005 CPU).
There's a workaround (modified kernel) posted in the bug thread: https://bugs.freedesktop.org/show_bug.cgi?id=105887
That solved the problem for me (and other J4005/J5005) users.
Also; after further testing I learned that the issue was not skin related at all.
As it turns out, the issue affected all tested skins if I waited a bit longer before pressing 'stop'. Somehow the issue only became 'active' after the refresh rate was active for a while.. Ofcourse I didn't time it, at all, so the 'active time' varied across tested skins.
