You set the paths in the addon settings. Keep in mind that the remote paths should already be mounted and you use the local mount point.
If you want to add multiple paths, you can add additional docker parameters in the addon settings as well
would that be the same as in Swagger?
<setting id="E_additional" default="true" />
but I cannot find anything like this in libreelec-addon-repo/docker.linuxserver.portainer at master · linuxserver/libreelec-addon-repo (github.com)
Hello,
would you mind updating LinuxServer.io docker addons and general docker info - Add-on Support - LibreELEC Forum as docker-letsencrypt/README.md at master · linuxserver/docker-letsencrypt (github.com)
THIS IMAGE HAS BEEN DEPRECATED AND THE PROJECT IS MOVED TO A NEW REPO
which is linuxserver/docker-swag: ...
Moreover, how do I add
docker run -d \
....
-e EXTRA_DOMAINS= `#optional` \
....to /storage/.kodi/userdata/addon_data/docker.linuxserver.swag/settings.xml?
Is it <setting id="E_extrad">wildcard</setting>?
Damm it, so all manually, using command line and ensure that the updater (chron job) is deactivated?
(besides testing beta of v11 on my lab device)
Hi there, I'm running the "docker / linuxserver" add-on on LibreELEC: LinuxServer.io docker addons and general docker info The docker engine is outdated to run the newest portainer image: https://github.com/portainer/portainer/issues/8455
How do I safely downgrade to portainer v2.16.2, ensuring that auto update won't update it straight away?
thank you
thx for the update, I'll give a shot on the weekend
alright so I have to either wait for an update on Portainer or manually install an older version
(or could you share when you expect roughly LE11 RC1?)
looks like that I can answer it by my own, docker will be updated by LE 11, see Issues · LibreELEC/LibreELEC.tv (github.com)
Any chance to use the package with LE10?
Hello,
is it possible to update to version >20 as staying on 19 gives me an error on Portainer: RE: How to access portainer?
thank you
Hi there,
seems there is another issue
journalctl -u docker.linuxserver.portainer -f
logs
FTL github.com/portainer/portainer/api/cmd/portainer/main.go:730 > failed initializing upgrade service | error="failed to determine container platform: failed to retrieve docker info: Error response from daemon: client version 1.41 is too new. Maximum supported API version is 1.40" stack_trace=[{"func":"NewService","line":"55","source":"upgrade.go"},{"func":"buildServer","line":"728","source":"main.go"},{"func":"main","line":"801","source":"main.go"},{"func":"main","line":"250","source":"proc.go"},{"func":"goexit","line":"831","source":"asm_arm.s"}]anyone else having the same issue?
Seems to pretty new portainer-ce crashing, will not start · Issue #8455 · portainer/portainer (github.com)
For anyone who is trying to control externals via RS232 (I'm about, to begin with, it), the Delock Products 62960 Delock Adapter USB 2.0 Type-A > 1 x Serial RS-232 RJ45 1.8 m is detected well.
The following is just for your information, if someone has to go through logs and needs some reference
====================== Kernel Message Log ===================
LibreELEC:~ # dmesg
[ 2.243580] usb 1-1.4: new full-speed USB device number 3 using xhci_hcd
[ 2.349864] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
[ 2.349878] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.349889] usb 1-1.4: Product: FT232R USB UART
[ 2.349900] usb 1-1.4: Manufacturer: FTDI
[ 2.349910] usb 1-1.4: SerialNumber: A10K5SV4
...
[ 5.085449] usbcore: registered new interface driver usbserial_generic
[ 5.085474] usbserial: USB Serial support registered for generic
[ 5.087747] usbcore: registered new interface driver ftdi_sio
[ 5.087783] usbserial: USB Serial support registered for FTDI USB Serial Device
[ 5.087857] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected
[ 5.087921] usb 1-1.4: Detected FT232RL
[ 5.098474] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0LibreELEC:~ # lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Bus 001 Device 014: ID 0d8c:0102 C-Media Electronics, Inc. CM106 Like Sound Device
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubswapping out your HDMI cable.
as soon as I have the second one, but the PIs work without any problem using the same HDMI cable. The problem even occurs, when no HDMI cable is connected at all, so I would not blame it.
Alright thx for the quick reply
Christmas is close, so let's keep hope up 😃
So far no change on the intention to support VNC, right?
So everything works now?
on the borrowed and 8 GB one
Do you still have the "firmware transaction" error in dmesg log on either original
I gues but I have not checked the logs yesterday, I was just happy to make the family enjoy Spotify Connect on our HiFi-System
By the way, MERCI to make this happen.
I'll check the logs tonight and can share them.
I have filled out my warranty claim. I was told that I can keep the detective device, so we could do a detail investigation on it if you are interested.
I've read you post several times but I'm still confused what does and doesn't work.
I0m sorry, I forgot "borrowed" in my list.
I updated my post, hope it is clearer now.
In nutshell, it runs on my 8 GB and the borrowed 4 GB. The borrowed 4 GB had some hick-ups as it booted the very first time being connected to the TV (not the HP Screen anymore)
sbs is a 3d mode
it could be related to the fact, that the TV sometimes detect 3D content although there is not any
I could borrow a Pi 4B 4GB, it is around the same age. I included that in my tests
Test #1
Same SD-Card, used in different PIs. During each test run, each Pi were only connected to the network by wire and my HP Screen:
As it worked with the 1 and 2, I installed Librespot addon - Add-on Support - LibreELEC Forum
Test #2:
Booting the borrowed Pi 4B 4 GB but being connected to my Panasonic Viera Plasma TV (TX-P55VT30J
TV is showing Kodi 
even after booting it again and again, so it is stable
That hardware defect is bizarre as Pi OS and OSMC don't mind that defect.
Anyway, the warranty claim is filled.
More words would be useful.
it did the thing just before I went to bed, sorry, I just want to keep the stone rolling. I don't know in which time zone you are located, I'm in CET.
"failed" is mentioned eight times in Ubuntu Pastebin (I used in Ubuntu's service as I could not register at PasteBin) in addition to timeouts
[ 0.123750] raspberrypi-firmware soc:firmware: Attached to firmware from 2022-10-05T15:52:04, variant start_x
[ 0.127087] raspberrypi-firmware soc:firmware: Firmware hash is 6c57d97fa8066929a2fee6e4fac6d64ad62506c9
...
[ 5.722785] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 6.826628] ------------[ cut here ]------------
[ 6.826639] Firmware transaction timeout
[ 6.826687] WARNING: CPU: 0 PID: 32 at rpi_firmware_property_list+0x1ec/0x26c
[ 6.826689] Modules linked in: brcmfmac brcmutil cfg80211 bcm2835_isp(C+) rpivid_hevc(C) bcm2835_codec(C+) videobuf2_dma_contig bcm2835_mmal_vchiq(C) v4l2_mem2mem videobuf2_memops videobuf2_v4l2 videobuf2_common videodev rfkill mc bcm2835_gpiomem nvmem_rmem fuse
[ 6.826726] CPU: 0 PID: 32 Comm: kworker/0:1 Tainted: G C 5.10.110 #1
[ 6.826728] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT)
[ 6.826736] Workqueue: events get_values_poll
...
[ 6.826863] hwmon hwmon0: Failed to get throttled (-110)
...
[ 9.519968] raspberrypi-clk soc:firmware:clocks: Failed to change fw-clk-v3d frequency: -110
...
[ 12.559984] cpu cpu0: dev_pm_opp_set_rate: failed to find current OPP for freq 18446744073709551506 (-34)
[ 13.573300] raspberrypi-clk soc:firmware:clocks: Failed to change fw-clk-core frequency: -110
[ 32.053290] cam-dummy-reg: disabling
[ 185.531482] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=1)
[ 185.531551] bcm2835_mmal_vchiq: Failed to open VCHI service connection (status=1)
[ 185.531614] : Unregister from media controller
[ 185.531620] (efault): Unregistering node (null)[0] device node /dev/video0
[ 185.531624] (efault): Unregistering node (null)[0] device node /dev/video0
[ 185.531628] (efault): Unregistering node (null)[0] device node /dev/video0
[ 185.531631] (efault): Unregistering node (null)[0] device node /dev/video0
[ 185.532540] bcm2835-codec bcm2835-codec: Removing bcm2835-codec, encode
[ 185.532699] bcm2835_mmal_vchiq: mmal-vchiq: VCHIQ close failed
[ 185.533009] bcm2835-codec bcm2835-codec: Removing bcm2835-codec, decode
[ 185.533114] bcm2835_mmal_vchiq: mmal-vchiq: VCHIQ close failed
[ 2689.839524] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 2689.839546] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 2689.855354] 8021q: 802.1Q VLAN Support v1.8Can you confirm that you installed Ubuntu on your pi that has problems with libreelec,
and it produces that error in dmesg?
I took the Pi out of the box and used LibreELEC USB-SD Creator, as that failed, I opened this thread, nothing else, no modification etc.
I took the SD Card with "Raspberry Pi OS using Raspberry Pi Imager" from my running Pi 4 8 GB. That booted and was usable.
Afterwards, I tried OSMC (OSMC Installer), which runs well.
I can try to boot it up with Ubuntu if you like.
Doing a swap test (with a different pi4) could also confirm this
I should be able to do this tomorrow (maybe tonight, childcare is on me tonight)
Could you borrow one or use one from another appliance you already have connected up.
I have to check in office tomorrow, I could be lucky
Error message visible? No my.log file created? Empty my.log file created?
creates only a file pastekodi.log with a single line:
System log output for: LibreELEC (official): 10.0.3
Can you post output of "vcgencmd log msg" (e.g. piped through paste if that working).
vcgencmd log msg >vcgencmd.log creates an empty file named vcgencmd.log
Can you confirm you have no custom settings (like overclock) in config.txt?
nothing done, all default
Ideally it should. But the log shows:
Code Feb 02 15:29:50 LibreELEC kernel: Firmware transaction timeoutwhich means firmware isn't responding to requests (it has likely crashed).
that exists log is here: Ubuntu Pastebin
