Posts by thebakker

Hello,

I'm using moonlight to stream games from my main pc to libreelec. Previous I had an intel j3445 CPU. But I upgraded the box to N100.

But I'm getting an error that no hardware is supported. According to their github it should be supported: https://github.com/moonlight-stre…ment-1821975596

I already have ffmpeg installed. Any other addons?

I was using LE 11.0.3. But because it is a new cpu, I thought to update to nightly (20231119 12.0) (kernel 6.6.0). But still no luck. ANything I need to extra install?

Hello,

I'm trying to add my dualshock 4 to libreelec, but it keeps geving errors. I tried it with the build-in bluetooth of the mini pc, and also with a ble dongle

Here are my logs: http://ix.io/3vZn

It seems it creates an exception

                                                   Exception type  : DBusError
                                                   Exception value : org.bluez.Error.Failed -- No discovery started
                                                   System info     : uname_result(system='Linux', node='LibreELEC', release='5.10.47', version='#1 SMP Thu Jul 15 01:45:06 CEST 2021', machine='x86_64', processor='')
                                                   Python version  : 3.8.9 (default, Jul 15 2021, 01:46:40)  [GCC 10.2.0]
                                                   Kodi version    : 19.1 (19.1.0) Git:6402a50950ff6463042f8891ec4029c782730391
                                                   sys.argv        : ['']

Quote from mglae

Code

2021-08-14 07:27:28.069 T:991      INFO <general>: CAESinkALSA - Unable to open device "default" for playback
2021-08-14 07:27:28.131 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=0" may be unconnected (no ELD data)
2021-08-14 07:27:28.132 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=1" may be unconnected (no ELD data)
2021-08-14 07:27:28.132 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=2" may be unconnected (no ELD data)
2021-08-14 07:27:28.133 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=3" may be unconnected (no ELD data)
2021-08-14 07:27:28.133 T:991     DEBUG <general>: CAESinkALSA - HDMI device "hdmi:CARD=PCH,DEV=4" may be unconnected (no ELD data)

There are no audio devices detected. What are you using?

HDMI#2 seem to be connected. xrandr --verbose|paste may show more details.

For the failing pastekodi use pastekodi -c >mylog and put the file manually to a paste site.

I'm using this: NiPoGi Mini PC, Intel Celeron J3455 8GB RAM/128GB ROM Mini Computer met Windows 10 Pro, Micro PC ondersteuning Dual HDMI 4K, Wake On LAN, Tiny Desktop PC voor business, vergadering, kantoor, school en HTPC: Amazon.de: Computers & accessoires

It is a mini pc with 2 HDMI outputs. I have the stuttering on both ports.

This is the output from xrandr: http://ix.io/3vZ4

Currently I have the mini pc connected to my regular display (it has no sound) (samsung S24D340) to configure everything. When everything works, I want to connect it to my TV

EDIT: so, I have some more test. When I connect the mini pc to my display without sound, and then the video is very choppy, and sometimes just freezes.

mglae response, made me test it at my tv. When I connect it to the tv everything works. So I guess that there is a bug(?) when there is no audio device.

Quote from Klojum

Sadly both links are not working for me, but I'm having some internet connection problems myself lately, so who knows.

But there is also hastebin (with 60 days retension)

It was too big for pastebin. This is my hastebin link:

hastebin

In case that doesn't work: this is a google drive link:

https://docs.google.com/document/d/1nTPG4XRuYbyXHUyHu_kbM2HQkbytSQXddPWKrwW2YWU/edit?usp=sharing

Yeah, sorry, I completely forgot about nightly.

I have 9.97.1 generic.x86_x64 installed

I tried a local file, it starts quicker. But it stutters even more than through plex

I noticed LE only uses 1 core (core 1: 100%, the rest is only 10%)

Here are my logs: (the pastekodi command didn't return anything, so I uploaded the logs to my nas)

Synology Drive

https://lodenas.duckdns.org:5001/d/s/l1anzR4EPt…ICI-5reATmqg1Qg

I see these errors in my logs:

2021-08-14 07:30:19.760 T:1139    DEBUG <general>: Thread JobWorker 140047516943936 terminating (autodelete)
2021-08-14 07:30:19.862 T:992      INFO <general>: CActiveAESink::OpenSink - initialize sink
2021-08-14 07:30:19.862 T:992     DEBUG <general>: CActiveAESink::OpenSink - trying to open device ALSA:hdmi:CARD=PCH,DEV=0
2021-08-14 07:30:19.862 T:992      INFO <general>: CAESinkALSA::Initialize - Attempting to open device "hdmi:CARD=PCH,DEV=0"
2021-08-14 07:30:19.873 T:992      INFO <general>: CAESinkALSA::Initialize - Opened device "hdmi:CARD=PCH,DEV=0,AES0=0x04,AES1=0x82,AES2=0x00,AES3=0x00"
2021-08-14 07:30:19.875 T:992      INFO <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2021-08-14 07:30:19.875 T:992      INFO <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S32NE
2021-08-14 07:30:19.875 T:992     DEBUG <general>: CAESinkALSA::InitializeHW - Request: periodSize 2205, bufferSize 8820
2021-08-14 07:30:19.876 T:992     DEBUG <general>: CAESinkALSA::InitializeHW - Got: periodSize 2205, bufferSize 8820
2021-08-14 07:30:19.876 T:992     DEBUG <general>: CAESinkALSA::InitializeHW - Setting timeout to 200 ms
2021-08-14 07:30:19.876 T:992     DEBUG <general>: CAESinkALSA::GetChannelLayout - Input Channel Count: 2 Output Channel Count: 2
2021-08-14 07:30:19.876 T:992     DEBUG <general>: CAESinkALSA::GetChannelLayout - Requested Layout: FL, FR
2021-08-14 07:30:19.876 T:992     DEBUG <general>: CAESinkALSA::GetChannelLayout - Got Layout: UNKNOWN1, UNKNOWN1 (ALSA: UNKNOWN UNKNOWN)
2021-08-14 07:30:19.876 T:992     DEBUG <general>: CActiveAESink::OpenSink - trying to open device ALSA:hdmi:CARD=PCH,DEV=0
2021-08-14 07:30:19.876 T:992      INFO <general>: CAESinkALSA::Initialize - Attempting to open device "hdmi:CARD=PCH,DEV=0"
2021-08-14 07:30:19.887 T:992      INFO <general>: CAESinkALSA::Initialize - Opened device "hdmi:CARD=PCH,DEV=0,AES0=0x04,AES1=0x82,AES2=0x00,AES3=0x00"
2021-08-14 07:30:19.888 T:992      INFO <general>: CAESinkALSA::InitializeHW - Your hardware does not support AE_FMT_FLOAT, trying other formats
2021-08-14 07:30:19.888 T:992      INFO <general>: CAESinkALSA::InitializeHW - Using data format AE_FMT_S32NE
2021-08-14 07:30:19.888 T:992     DEBUG <general>: CAESinkALSA::InitializeHW - Request: periodSize 2205, bufferSize 8820
2021-08-14 07:30:19.889 T:992     DEBUG <general>: CAESinkALSA::InitializeHW - Got: periodSize 2205, bufferSize 8820
2021-08-14 07:30:19.889 T:992     DEBUG <general>: CAESinkALSA::InitializeHW - Setting timeout to 200 ms
2021-08-14 07:30:19.889 T:992     DEBUG <general>: CAESinkALSA::GetChannelLayout - Input Channel Count: 2 Output Channel Count: 2
2021-08-14 07:30:19.889 T:992     DEBUG <general>: CAESinkALSA::GetChannelLayout - Requested Layout: FL, FR
2021-08-14 07:30:19.889 T:992     DEBUG <general>: CAESinkALSA::GetChannelLayout - Got Layout: UNKNOWN1, UNKNOWN1 (ALSA: UNKNOWN UNKNOWN)
2021-08-14 07:30:19.889 T:992     ERROR <general>: CActiveAESink::OpenSink - no sink was returned
2021-08-14 07:30:19.889 T:991     ERROR <general>: ActiveAE::InitSink - returned error

Hello.

I had an Intel j3455 box laying around. And decided to use that one instead of my rpi4 for libreelec. But the performance is terrible.

I use kodi Plex Connect to watch my movies from my server.

My rpi starts a movie in 20s. But the j3455 does more than a minute to start. It also stutters on my j3455. The movie is just a h264 1080p movie

I just did a clean install of the latest kodi and latest kodi plex connect.

The passmark score of the j3455 is more than double of the rpi4. Is there something I'm missing? Do I need to do more configuration for x86?

Thanks in advance

Yeah, but someone on github commented this:

Quote

I'm closing the ticket because this is not a bug, it's the expected behaviour now RPi devices in LE10 no longer use legacy vendor drivers (behaviour is now consistent with other LE devices since ~2012).

Follow the section on Intel GPUs https://wiki.libreelec.tv/configuration/edid and repeat for your RPi4. If you need further support please start a thread in the forums.

So I'm looking at that now.

I fixed it, see edit

Edit: it is fixed:

I followed this https://wiki.libreelec.tv/configuration/edid#intel and follwed the intel steps, but the extlinux.conf or syslinux.cfg didn't exist, so instead I added

drm.edid_firmware=HDMI-A-1:edid/edid-HDMI-A-1.bin video=HDMI-A-1:1920x1080M@60D

To /flash/cmdline.txt

Orifinal problem:

I made a git bug report, but I wanted to know if someone else has the same problem?

Describe the bug

When I boot my raspberry pi an afterwards start my tv, I don't get video out. Even when I unplug and plug in the hdmi after they both are started.

But when I first start my tv, and then boot my rpi it works fine

To Reproduce

Steps to reproduce the behavior:

1. Install 9.95.5
2. start RPi4
3. Start soundbar (HEOS) and tv

Informations

• LE Version: 9.95.5
• Hardware Platform: RPI4

Log file

Log from when the problem exists: http://ix.io/3rP7

Log from when I first start the tv: http://ix.io/3rPa

Additional context

It worked fine when using LE 9.2.X

I have my rpi4 connected to my soundbar, and the soundbar to the tv

Quote from thankarezosLB

Can somone provide the steamlink.sh file? The pastebin is down

edit:Is it still not working with RPi4?

No, still the same error as user burny02 has. But like chewitt says, it probably isn't possible on the pi4 without sudo

I couldn' get it working, so I made a node-red flow on my server that creates a HTTP api, and converts the http data to MQTT

And put a wget in my startup and shutdown script:

wget -T 2 http://192.168.0.209:1880/endpoint/plexBox/state?state=OFF

Quote from lrusak

check the output of

Code

systemctl status kodi-autostart.service

You might need to wait until you have a network connection and docker is started

Thanks, I got the error

Mar 14 09:25:36 LibreELEC sh[724]: the input device is not a TTY

This was an error from my docker command, I fixed it by removing the "-it" argument

Is there also a log from the shutdown script?

Quote from chewitt

Quote from ghtester I know, maybe I am wrong but I still believe in this case these commands should not be queued.

autostart.sh is run at the very start of usespace boot, so the network is not started, kodi (which runs docker via an add-on) is not started. So running the docker command at that point will *allways* fail, and (backgrounding)& is the correct approach.

The case statement ^ above was incorrect, not sure if it was copy/paste typo or what but I edited it to be correct.

As lrusak says, look at systemd logs

But the shutdown doesn't. I think I have the problem you describe: docker gets closed and after that the shutdown script gets called.

Any idea where I can see the shutdown log?

EDIT I found a workaround:

Quote from thebakker

I couldn' get it working, so I made a node-red flow on my server that creates a HTTP api, and converts the http data to MQTT

And put a wget in my startup and shutdown script:

wget -T 2 http://192.168.0.209:1880/endpoint/plexBox/state?state=OFF

Hello,

I followed the guide for creating autostart and shutdown commands (This guide). But my commands dont run

I autostart.sh I have the following code:

(
 sleep 50
 docker run -it --rm eclipse-mosquitto mosquitto_pub -h 192.168.0.100 -t plexBox/state -m "ON"
)&

And in the shutdown.sh:

case "$1" in
  halt)
    # your commands here
    ;;
  poweroff)
    # your commands here
    ;;
  reboot)
    # your commands here
    ;;
  *)
    docker run -it --rm eclipse-mosquitto mosquitto_pub -h 192.168.0.100 -t plexBox/state -m "OFF"
    sleep 50
    ;;
esac

I have docker installed through libreelec. And when I run these commands manually, they work.

Anyone a suggestion?