Oh ok then, thanks!
Edit:
Just tried the latest LE11 nightly 20221126.
Can confirm the sensors show up after adding jc42.conf to modules-load.d. No further setup required.
Oh ok then, thanks!
Edit:
Just tried the latest LE11 nightly 20221126.
Can confirm the sensors show up after adding jc42.conf to modules-load.d. No further setup required.
Hi again.
Is it correctly understood that this change was included in 10.0.3?
Because I upgraded to that and am not able to install or find the jc42 driver.
It is working. Thanks a lot!
Follow below commands.
Although with this manual load of jc42 it seems like all the steps have to be done after each reboot.
NUC11TNBi7:~ # modprobe i2c_dev
NUC11TNBi7:~ # i2cdetect -l
i2c-0 i2c i915 gmbus dpa I2C adapter
i2c-1 i2c i915 gmbus dpb I2C adapter
i2c-2 i2c i915 gmbus dpc I2C adapter
i2c-3 i2c i915 gmbus tc1 I2C adapter
i2c-4 i2c i915 gmbus tc2 I2C adapter
i2c-5 i2c i915 gmbus tc3 I2C adapter
i2c-6 i2c i915 gmbus tc4 I2C adapter
i2c-7 i2c i915 gmbus tc5 I2C adapter
i2c-8 i2c i915 gmbus tc6 I2C adapter
i2c-9 i2c AUX D/port D I2C adapter
i2c-10 i2c AUX E/port E I2C adapter
i2c-11 i2c AUX F/port F I2C adapter
i2c-12 i2c AUX G/port G I2C adapter
i2c-13 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-14 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-15 smbus SMBus I801 adapter at efa0 SMBus adapter
NUC11TNBi7:~ # i2cdetect -y 15
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 08 -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- 18 -- 1a -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: 30 31 -- -- 34 35 UU UU -- -- -- -- -- -- -- --
40: -- -- -- -- 44 -- -- -- -- -- 4a 4b -- -- -- --
50: UU -- 52 -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
NUC11TNBi7:~ # insmod jc42.ko
NUC11TNBi7:~ # echo jc42 0x18 > /sys/bus/i2c/devices/i2c-15/new_device
NUC11TNBi7:~ # echo jc42 0x1a > /sys/bus/i2c/devices/i2c-15/new_device
NUC11TNBi7:~ # sensors
jc42-i2c-15-18
Adapter: SMBus I801 adapter at efa0
temp1: +47.0 C (low = +0.0 C) ALARM (HIGH, CRIT)
(high = +0.0 C, hyst = +0.0 C)
(crit = +0.0 C, hyst = +0.0 C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +39.0 C (crit = +119.0 C)
jc42-i2c-15-1a
Adapter: SMBus I801 adapter at efa0
temp1: +48.0 C (low = +0.0 C) ALARM (HIGH, CRIT)
(high = +0.0 C, hyst = +0.0 C)
(crit = +0.0 C, hyst = +0.0 C)
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +39.0 C (high = +100.0 C, crit = +100.0 C)
Core 0: +33.0 C (high = +100.0 C, crit = +100.0 C)
Core 1: +37.0 C (high = +100.0 C, crit = +100.0 C)
Core 2: +35.0 C (high = +100.0 C, crit = +100.0 C)
Core 3: +37.0 C (high = +100.0 C, crit = +100.0 C)
Display More
Awesome. Could you let me know where to put the file too ? 😅
That sound great. Thanks!
NUC11TNBi7:~ # uname -a
Linux NUC11TNBi7 5.10.76 #1 SMP Sat Mar 5 19:12:54 CET 2022 x86_64 GNU/Linux
NUC11TNBi7:~ # cat /etc/release
Generic.x86_64-10.0.2
NUC11TNBi7:~ # head .kodi/temp/kodi.log
2022-03-16 00:40:44.072 T:1084 INFO <general>: -----------------------------------------------------------------------
2022-03-16 00:40:44.072 T:1084 INFO <general>: Starting Kodi (19.4 (19.4.0) Git:19.4-Matrix). Platform: Linux x86 64-bit
2022-03-16 00:40:44.072 T:1084 INFO <general>: Using Release Kodi x64
2022-03-16 00:40:44.072 T:1084 INFO <general>: Kodi compiled 2022-03-05 by GCC 10.2.0 for Linux x86 64-bit version 5.10.76 (330316)
2022-03-16 00:40:44.072 T:1084 INFO <general>: Running on LibreELEC (official): 10.0.2, kernel: Linux x86 64-bit version 5.10.76
2022-03-16 00:40:44.072 T:1084 INFO <general>: FFmpeg version/source: 4.3.2-Kodi
2022-03-16 00:40:44.072 T:1084 INFO <general>: Host CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz, 8 cores available
2022-03-16 00:40:44.072 T:1084 INFO <general>: special://xbmc/ is mapped to: /usr/share/kodi/
2022-03-16 00:40:44.072 T:1084 INFO <general>: special://xbmcbin/ is mapped to: /usr/lib/kodi
2022-03-16 00:40:44.072 T:1084 INFO <general>: special://xbmcbinaddons/ is mapped to: /usr/lib/kodi/addons
Display More
Hi heitbaum
This is what I get. So I assume there are sensors at 18 and 1a.
NUC11TNBi7:~ # i2cdetect -l
i2c-0 i2c i915 gmbus dpa I2C adapter
i2c-1 i2c i915 gmbus dpb I2C adapter
i2c-2 i2c i915 gmbus dpc I2C adapter
i2c-3 i2c i915 gmbus tc1 I2C adapter
i2c-4 i2c i915 gmbus tc2 I2C adapter
i2c-5 i2c i915 gmbus tc3 I2C adapter
i2c-6 i2c i915 gmbus tc4 I2C adapter
i2c-7 i2c i915 gmbus tc5 I2C adapter
i2c-8 i2c i915 gmbus tc6 I2C adapter
i2c-9 i2c AUX D/port D I2C adapter
i2c-10 i2c AUX E/port E I2C adapter
i2c-11 i2c AUX F/port F I2C adapter
i2c-12 i2c AUX G/port G I2C adapter
i2c-13 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-14 i2c Synopsys DesignWare I2C adapter I2C adapter
i2c-15 smbus SMBus I801 adapter at efa0 SMBus adapter
NUC11TNBi7:~ # i2cdetect -y 15
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 08 -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- 18 -- 1a -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: 30 31 -- -- 34 35 UU UU -- -- -- -- -- -- -- --
40: -- -- -- -- 44 -- -- -- -- -- 4a 4b -- -- -- --
50: UU -- 52 -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
Display More
Hi
Running LE10 on a NUC11TNBi7. I also run some unrelated stuff in docker on the same machine.
I was trying to read RAM DIMM's temperature sensors. But it seems a module called jc42 is not included.
I followed this guide: https://wiki.archlinux.org/title/Lm_senso…erature_sensors
This guide works fine for me in Debian btw.
So I then made my very first attempt in compiling LE with this module included. But it is also the first time I try to compile anything at all so now after 3 days I give up.
Would it be possible to include the jc42 module in the Generic image? Or if someone can build a test image to begin with since I am not even sure that just including that module is enough to make it work.
I got a new NUC, NUC11TNBi7. It's running LE 10. Also got new Supra HD5 HDMI cables. Otherwise same setup.
Yesterday I wanted to watch some TrueHD stuff but as soon as the video started the audio just stopped, the audio output signal "froze"and nothing I did would change it except a reboot.
Eventually I switched the HDMI cable to the second port on the NUC. And now everything just works! The two HDMI ports on the NUC are 100% identical according to the specs as I read it.
Is this some mechanical issue with HDMI hardware? That it is just not robust enough in some way.
Or is it Intel HDMI hardware specifically which is poor quality?
I am just mystified by this behavior.
Edit:
It's getting pretty annoying...
HDMI port 1: Only 50, 59.94 and 60 Hz refresh rates work at 3840x2160, but TrueHD works fine.
HDMI port 2: All refresh rates at 3840x2160 works, but TrueHD does NOT work.
Edit 2:
Ok this is perhaps slightly embarrasing, apart from the fact I am debating myself here.
In my ignorance I had set the video signal format on the Marantz reciever to "Enhanced". I had also tried the "8K enhanced" which didn't make any difference by the way.
Only now I get the idea to set it to "Standard", and voilà all the refresh rates at 3840x2160 works and TrueHD also works.
So yeah I guess I didn't know what I was doing without realising it.
Alright I think I have solved the issue now.
I just spent a few hours where I tried nearly all combinations of HDMI cables, HDMI inputs on the reciever, HDMI inputs on the TV, running HDMI through the reciever, and directly from NUC to TV.
I know that not all HDMI cables are equally good. But the cables I have been using recently until I upgraded the NUC, had worked just fine. But apparently they are no longer good enough for the NUC. They were even bought specifically on the 4K/8K specs!
But I am now back to my old Supra HF100 HDMI cables bought in 2018.
As if that wasn't enough, not all the HDMI ports on my TV are allowing the NUC to set >30 Hz refresh rates. Sigh..
And by the way I also still have TrueHD in passthrough.
I have tried adding custom 50 Hz and 60 Hz refresh rates with xrandr but none of them were accepted by the system. It just reverted back to 30 Hz.
I have also tried creating kodi.conf with different parameters e.g.:
But I didn't notice any difference at all.
In an attempt to get TrueHD working in passthrough I decided to update both BIOS and HDMI firmware on my NUC.
So now I actually got TrueHD passthrough, yay!
But instead I am now missing refresh rates above 30 Hz for 4K resolution 3840x2160, which I am pretty sure was working before the upgrade.
I found this thread from Thomas_AR discussing HDMI firmware on the NUC8 too but they were not mentioning refresh rates I think: Intel NUC 8i5BEH - HDMI Sound problem
Current setup
LibreELEC-Generic.x86_64-9.95.4
Intel NUC8i7BEH -> Marantz SR8015 -> Sony XF90
BIOS: BECFL357.86A.0088.2021.0330.1431
HDMI firmware: 1.78.4.0.4 (MCDP2800_C21_C22_V1.78.4.0.4_LSPCON_MP_FHC_SIGNED_CMDB_BE_210309)
Thanks mglae ! That seemed to do the trick.
I'm on 10 beta / 9.95.1 and I have the same issue. However I do not even get an output with systemctl status docker it just displays Unit docker.service could not be found.
Did you find a fix ghstudio ?
I got it working.
BEWARE OF SECURITY ISSUES
The below guide is an un-secured and un-authenticated method.
I am using this on a LAN with myself as the only user with access.
On the libreelec host go to the folder:
cd /storage/.config/system.d/
edit the docker.service config file:
nano docker.service
Add
-H unix:///var/run/docker.sock/
and
-H tcp://0.0.0.0:2375/
to the ExecStart option.
E.g. my docker.service file now looks like this:
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network.target
[Service]
Type=notify
Environment=PATH=/bin:/sbin:/usr/bin:/usr/sbin:/storage/.kodi/addons/service.system.docker/bin
ExecStartPre=/storage/.kodi/addons/service.system.docker/bin/docker-config
EnvironmentFile=-/storage/.kodi/userdata/addon_data/service.system.docker/config/docker.conf
ExecStart=/storage/.kodi/addons/service.system.docker/bin/dockerd --exec-opt native.cgroupdriver=systemd \
--log-driver=journald \
--group=root \
$DOCKER_DAEMON_OPTS \
$DOCKER_STORAGE_OPTS \
-H unix:///var/run/docker.sock \
-H tcp://0.0.0.0:2375
ExecReload=/bin/kill -s HUP $MAINPID
TasksMax=8192
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity
TimeoutStartSec=0
Restart=on-abnormal
[Install]
WantedBy=multi-user.target
Alias=docker.service
Display More
Test the connection from the client machine:
docker -H 0.0.0.0:2375 info
(where 0.0.0.0 should be the actual ip of the libreelec host.)
If the connection works you will get a bunch of info printed and as mentioned initially a warning about security:
WARNING: API is accessible on http://0.0.0.0:2375 without encryption.
Access to the remote API is equivalent to root access on the host. Refer
to the 'Docker daemon attack surface' section in the documentation for
more information: https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
Hi elonesna. Thank you for that suggestion. It might be slightly overdoing it for my initial plan though. Maybe I should have elaborated a bit.
I have a portainer on another server. On that I have 2 "homes" as seen here, one on the local machine an another on an odroid.
So I just wanted to be able to add the docker service running on libreeelec to this list as well. But it is somehow setup in a different way than all the guides are explaining.
Hi
I have been trying to enable remote management of docker but the guide I try to follow seem to not work for libreeelec. dockerd | Docker Documentation
So how can I manage the docker containers on libreelec from a remote portainer?