yes...without them it's only guessing. And I would recommend to start a new thread. Users who might be able to answer this probably won't look at a thread which is IP related
Posts by DaVu
-
-
I am writing images on Win XP SP3 if it matters. Normally, I use
.gz -> 7zip -> Win32DiskImager and that works with OpenElec and OSMC.Are you sure you took the correct image?
As I said...don't extract the files with 7zip. Use the img.gz file with Rufus directly.
But if you are able to install openelec in that way, then just install this for now and update it to LibreELEC by copying the specific *.tar file to your update folder....
So get the OpenELEC disk image from here:
install it and then update it with the file from here:
The update process is explained here:
Accessing LibreELEC - LibreELEC
HOW TO:Update LibreELEC - LibreELEC -
If that fails, try the other way explained here:
- Download Rufus: Rufus - Create bootable USB drives the easy way
- write the *.img.gz file WITHOUT extracting it before.Please report back if that works for you then.
-
could you get us a screenshot from those settings, please?
-
The log is not complete....
enable debug logging at systems settings->system->logging->enable debug logging
and try to reproduce your issue. After that ssh in and do:pastebinit /storage/.kodi/temp/kodi.log
and get us the URL you got back
And there should be 7.90.003 available now...you should also try that and see if your problem is fixed already
-
if that openelec bootable works fine. Just install that and then migrate to LE by updating it with:
LibreELEC-Generic.x86_64-7.0.2.tar
Download that
and put it to your update folder and reboot.
-
Hello Stockfisch
Please choose english the next time you start a thread. Many of the users in here who might be able to help don't speak german. So the chance for getting your problem solved decreases.
But I guess it will be solved.... CvH ^^....your turn, I guess
-
Not sure if that's related, but it seems you have a bunch of 'invalid xml files' errors. Do you use nfo files and do they have a <Details> tag inside?
-
So you tried both? Current Alpha _and_ latest Milhouse build?
Probably you need to provide logfiles:
-
If SSH is permanently connected and to see if the installation went fine and you only have problems with your DBs, just rename the /storage/.kodi folder to something else. That's like a factory reset, but all old settings and configs are stored in the folder you renamed .kodi to. So I would try:
The problem might be, that kodi seems to restart permanently, if you always get a new Kodi splash. So I don't know if
will work to avoid kodi from restarting. Probably it's "kill" instead of "stop". I'm not sure. But maybe Kodi needs to be stopped from restarting to properly mv the .kodi folder.
If it boots fine after that, we know the installation went fine and you can dig deeper.
For the note....always provide the full logs. Maybe that's more helpful for the devs.
-
i write this for people who search for an solution or fix... like me before.. its the only way today.
but some bad ass m. f. like you needs to comment this...get yourself an employmenti would never say anything bad against the developer of libreelec
what everyone wants to say is, that you have to give more informations (which add-ons are installed, which skin is in use...etc...). Probably a logfile from a runing OE might help.
IIRC sometimes a boot loop might be caused if a different skin then the default one is used. So please confirm you have confluence as your standard skin while doing the update. As the update from OE to LE works for a lot of people it's not a general issue. It might depend on a setting or maybe on an add-on. You could (for a test) rename your .kodi folder to something else ('kodi-backup' for example) while you are at OE and then try the update to LE. If that works, it "might" depend on an add-on you have installed. After you confirmed it works, just switch back to OE, rename your "kodi-backup' to '.kodi' again and probably remove some of your add-ons. I would start with the skin, if it's not the default one.
That would help a lot.
-
Quote
Do you know any command to restart this resizing process ?Regarding to this:
LibreELEC.tv/fs-resize at master · LibreELEC/LibreELEC.tv · GitHub
you have to ssh in and do:
that´s the first step. Don´t reboot after that command. It won´t just work because of that line:
Codeif [ -d /storage/.kodi -o -d /storage/.config -o -d /storage/.cache ] ; then rm -f /storage/.please_resize_me
That means, if one of those directories "/storage/.kodi" and/or "/storage/.config" and/or "/storage/.cache" exists, remove the file "/storage/.please_resize_me".
So you have to rename either those directories mentioned above before the boot, or (and that would be even better) rename the complete ".kodi" folder to something else, which is the same as a complete backup of the most important parts. This is done by:
After that you should reboot the machine and the resize should be done again.
Hopefully that works.
Greetings.
-
Ah, ok...Thanks for the link
-
and the wiki has videos now \o/
-
debug log, I would guess
PCM has nothing to do with passthrough
-
Check out OpenELEC Mediacenter - OpenELEC Forum - Addon to configure Raspberry Pi config.txt (1/6)I haven't had to make any changes to my config recently, but as far as I know, it still works fine with LibreElec.
From the link above it refers to: OpenELEC RPi Config
From this howto, I tried to:
and got a 404, because the repo was at Dropbox and obviously removed now.
So I doubt that works.
Last question from an user and answer from 'gda' in that thread is:
Quote
Is there any special reason why this great Add-On is'nt part of either official or unofficial OpenELEC repository?
-
-
Maybe because there is no need for an addon that helps a little with a task that will be done one or two times in a life of a Pi? -
absolutely, yes. Already thought about it
-