Posts by DaVu

It's still a WIP. We have some workarounds but not a real solution yet. But there will be. Just be a bit patient, please.

It might not get its way into Beta but hopefully in the final/stable version.

AFAICT you have to install deluge via apt-get on raspbian. That's not possible with LibreELEC as it has no apt-get. LibreELEC can't install any software beside Kodi unless you compile from source and add what you want or it's probably available as an add-on.

I can't find anything on the official repositories, so I guess, we can say it's not possible.

Sorry

Greetings

Thanks for reporting and glad it worked for you ;). But still have absolutely no idea why you won´t get a screen while connecting LE directly to your TV. As there aren t any known problems. Anyway...what really counts is, that it now works

We will cover that in our own wiki as well.

Have fun with it.

It comes from a banned repo....as far as I understand the Kodi Wiki it either comes from a banned repo 'or' it's on the list of banned add-ons. The statement doesn't need to fit both options. It's enough if it fits one. At least that's the way we handle it at IRC.

Greetings

Hence:

Quote

This list is only an example, and does not include all add-ons or services that violate the forum rules.

Yes, please report back....I'm curious, too

check this for "custom EDID" for intel based hardware: Configuring a Custom xorg.conf - OpenELEC

Puuuh...tbh, I'm out of ideas now. Let me sleep over it...maybe I might have an idea tomorrow.

Acestream is one of those banned Addons which comes from superrepo, guess....see:

Official:Forum rules/Banned add-ons - Official Kodi Wiki

So as you won't get support for this at Kodi Forums, you won't get support for it it in here.

If Installation fails, ask where you get it from, please.

best would be to mention the hardware you are using. Then, after you tried to upgrade, check if you are able to ssh in and maybe get the logfile

Do it as following:

- power down the HTPC
- connect the HTPC directly to the TV
- be sure, the TV is switched on and you are on the correct source
- power up your HTPC

Normally you should get a screen. If not, don´t power down or reboot or anything else...just SSH in and get me

xrandr

and a new debuglog:

pastebinit /storage/.kodi/temp/kodi.log

The difference is:

"Thanks David. I did do this. Both with LE and OE versions after they were up and running."

If you connect an already running HTPC to a TV it probably won´t get the EDID and therefore you don´t get a screen. So the HTPC has to be ALWAYS the last device in chain that has to be powered on. So please try it again the way I explained above.

If you have a screen, please get me xrandr and the kodi logfile, too.

What we will do after you have a screen?....we will hardcode your EDID to your HTPC. So it won´t need the info from the connected device anymore. Probably we need openelec for this, as we might need the EDID from the Pio. But let´s get a screen first with the TV directly connected to your machine

Could you do me a favour...I see, that you have an amp between your HTPC and your TV. At least that is show in your OE installation, that a Pioneer VSX-60 is connected. Could you please try to connect the HTPC directly to your TV? Like this:

HTPC---HDMI---->TV

There are some known bugs with Intel and Pioneer and I want to rule the Pioneer out probably being the culprit. My guess is, that the HDMI handshake doesn´t work because the Pioneer sends shitty EDID informations.

We can workaround this later, not a huge deal, but I want to be sure first.

The G45 should be fine. At least the "Kodi supported hardware - Wiki" says so: Supported hardware - Official Kodi Wiki

If you have a lot of junk installed on your machine, I would recommend a fresh install or remove the .kodi folder and reboot. That would be like a factory reset.

If it still doesn´t work then we might need some more info....

output of:

dmesg

xrandr

The link you will get from:

pastebinit /storage/.kodi/temp/kodi.log

absolutely ok

No offense taken.

I edited my posting already

Good points!!!

edit: all I've written was nonsense....what grimson told will test both

If I may, grimson

fuckme.sh

#!/bin/sh
ping -c4 192.168.178.43 > test.txt

I don't have any idea anymore. If the fuckme.sh script works fine and we know that shutdown.sh is called from inside LE, and fuckme.sh is called while you call shutdown.sh manually from command line, I'm absolutely out of ideas why it shouldn't work.

Here is someone with more sh foo needed.

Sorry, I can't help anymore.

Any reasond you don't put that command directly to the shutdown.sh? So it might look like this:

case "$1" in
  halt)
    # your commands here
    ;;
  poweroff)
    /usr/bin/ssh -i /storage/.ssh/id_rsa 192.168.178.43 /sbin/poweroff
    ;;
  reboot)
    # your commands here
    ;;
  *)
    # your commands here
    ;;
 esac

Could you please show both scripts again as they are now?