can you try
1. reboot
2. after start try to install something from kodi repo
3. post a log
can't find anything obvious
Posts by CvH
-
-
It is mostly a temporal problem, if it does not work after 2-3 days something else might be borked.
An Kodi.log might help then.
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem.Note: Full logs only. No partial or modified logs.Do not post your logs directly into the forum, use pastebin.com and post the link. -
from which version of LE do you have an backup ?
Better clean install that LE Version and restore the the backup, then update to whatever you like
-
afaik the kodi repo is mirrored, I already had strange behaviours with it, not sure if the repo hits bandwith limits or anything else is going on
-
-
ok so just be patient
-
"Official" VNC app from VNC Company or whatever.
okay its already RealVNC and not the legacy one
just to be sure, you installed the vnc addon from the LE repository and changed their settings ?
-
-
Is there a workaround?
Its likely a EDID issue, depending on the TV it may be a problem or not.
Video options in config.txt - Raspberry Pi Documentation
You may create an edid.dat file and then tell the RPi to use it instead of auto detect the settings at every start.
We have also Custom EDID [LibreELEC.wiki] , but I am not sure if the RPi is supported there.
-
actually no, I didn't saw this at all
We start a build asap and see what happens
-
You can direct me to this provisional situation.
basically take LE master, activate the dvb modules
LibreELEC.tv/options at master · LibreELEC/LibreELEC.tv · GitHub
add to make_target an command that deletes all modules that you are not interested in, so all that just dvb modules are there at the build folder
you need to compile the full stack and remove it afterwards, if you disable it at compile time it won't work at all
LibreELEC.tv/package.mk at master · LibreELEC/LibreELEC.tv · GitHub
thats it basically, then it might work, but the crazycat version needs no be compatible with the current used kernel or it won't build at all
because AML is likely always very close to the very latest kernel it might break
so to get an idea what you need
Use an LE version where the driver works, lsmod and have a look at the dvb driver that are in use and what dependencies it has. Then you know what drivers you actually need. Of course you could include everything else too but for a quick hacky try better delete all and just keep the files you need.
basically the folder here
/usr/lib/kernel-overlays/driver.dvb.crazycat/lib/modules/5.123.123/updates/driver.dvb.crazycat/ should only include the dvb drivers you are interested in at the LE image
I try to setup some test PR soonish, but I still wait for my new PC to properly build LE. Can't tell you if this takes a week or a month.
-
Using the official VNC app
not sure what is actually the "official" app at all but try the tigervnc, the vanilla vnc is known to be outdated
-
Any other ideas?
Video calibration settings changes are lost after Kodi restart · Issue #15165 · xbmc/xbmc · GitHub
sounds like issue is still not fixed
feel free to comment there, its no usecase for me
-
i can't beleave what's going on there...
To followup the discussion at scummvm github, we don't know either whats going on and have no fix for it at the moment.
-
With driver media_build-2020-01-02
The main problem is that media_build (or more specific the media_tree that is build by media_build) includes a lot drivers around the new mainline stack for decoding and whatnot at the gpu/soc. So if you use some media_build with some version of media_tree you loose all patches/fixes/improvements that are avaibvle at the normal kernel.
The situation gets better and better with more stuff is finally merged at the kernel. We have also a idea how to fix the remaining parts but that is highly hacky - but is likely working (just copy DVB modules instead the whole media_tree stuff build by media_build).
Of course you could merge it all down into a single kernel, but this is basically not maintainable.
-
you can also use EXT4 at windows, less headache is the extFat way
-
the updated chrome addon is at 9.2 and master since a ~week
-
