Posts by heitbaum

No LE11 docker updates are planned. There have been changes in the addon that were not suitable for stable. For a self build, you will probably be ok with the bump and dependencies - but untested.

LE12 already has this up to date

# docker version
Client:
Version: 24.0.7
API version: 1.43
Go version: go1.21.5
Git commit: afdd53b4e341be38d2056a42113b938559bb1d94
Built: Fri Dec 15 06:32:26 UTC 2023
OS/Arch: linux/amd64
Context: default

Server:
Engine:
Version: library-import
API version: 1.43 (minimum version 1.12)
Go version: go1.21.5
Git commit: library-import
Built: library-import
OS/Arch: linux/amd64
Experimental: true
containerd:
Version: 1.7.11
GitCommit: 4e1fe7492b9df85914c389d1f15a3ceedbb280ac
runc:
Version: 1.1.10
GitCommit: 18a0cb0f32bcac2ecc9a10f327d282759c144dab
docker-init:
Version: 0.19.0
GitCommit:

Quote from _emanuel_

First I've tested "y", but also no install.

https://github.com/LibreELEC/Libr…s/checkdeps#L41

If you update your docker container to the latest, you should be fine.
https://github.com/LibreELEC/Libr…/Dockerfile#L24

Also I don’t know if the firmware / comments on “however for a stable link at 1Gbps firmware revision ….” are relevant.

- https://git.kernel.org/pub/scm/linux/…c/rtl8125b-2.fw

- https://git.kernel.org/pub/scm/linux/…91af16d140ce2ef

I can see the eth0 and eth1 in your dmesg too. And nothing untoward.

This post goes through the particular card. It would be worth checking each step.

eth1 is a bit strange - in that it shows an MTU of 9000.

Both eth0 and eth1 are not showing any traffic and I can’t see the cable “connect” / “disconnect”
I’m not sure where this script is from? /storage/.config/system.d/mtuchange.service from the 02_System log.

The N100/AX101 is loading firmware.

iwlwifi 0000:00:14.3: loaded firmware version 83.e8f84e98.0 so-a0-hr-b0-83.ucode op_mode iwlmvm

The failure is occurring on wireless association. FW error in SYNC CMD STA_CONFIG_CMD

Nov 14 19:44:38.999359 LibreELEC kernel: wlan0: RX AssocResp from 50:e6:36:1d:72:77 (capab=0x1011 status=0 aid=37)
Nov 14 19:44:39.002677 LibreELEC kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
Nov 14 19:44:39.003129 LibreELEC kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Nov 14 19:44:39.003348 LibreELEC kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
Nov 14 19:44:39.003544 LibreELEC kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 83.e8f84e98.0 so-a0-hr-b0-83.ucode
Nov 14 19:44:39.003734 LibreELEC kernel: iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
Nov 14 19:44:39.003913 LibreELEC kernel: iwlwifi 0000:00:14.3: 0x00A08200 | trm_hw_status0
Nov 14 19:44:39.004079 LibreELEC kernel: iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
Nov 14 19:44:39.004246 LibreELEC kernel: iwlwifi 0000:00:14.3: 0x004D9024 | branchlink2
Nov 14 19:44:39.004426 LibreELEC kernel: iwlwifi 0000:00:14.3: 0x004CF2F2 | interruptlink1
Nov 14 19:44:39.004591 LibreELEC kernel: iwlwifi 0000:00:14.3: 0x004CF2F2 | interruptlink2


Nov 14 19:44:39.014491 LibreELEC kernel: ieee80211 phy0: Hardware restart was requested
Nov 14 19:44:39.014637 LibreELEC kernel: iwlwifi 0000:00:14.3: FW error in SYNC CMD STA_CONFIG_CMD
Nov 14 19:44:39.014787 LibreELEC kernel: CPU: 2 PID: 40 Comm: kworker/u8:1 Tainted: PO6.6.0 #1
Nov 14 19:44:39.014810 LibreELEC kernel: Hardware name: AZW MINI S/MINI S, BIOS ADLNV104 02/06/2023
Nov 14 19:44:39.014843 LibreELEC kernel: Workqueue: events_unbound cfg80211_wiphy_work [cfg80211]
Nov 14 19:44:39.014863 LibreELEC kernel: Call Trace:
Nov 14 19:44:39.014882 LibreELEC kernel:  <TASK>
Nov 14 19:44:39.014900 LibreELEC kernel:  dump_stack_lvl+0x71/0x90
Nov 14 19:44:39.014917 LibreELEC kernel:  dump_stack+0x14/0x20
Nov 14 19:44:39.014934 LibreELEC kernel:  iwl_trans_txq_send_hcmd+0x318/0x430 [iwlwifi]
Nov 14 19:44:39.014951 LibreELEC kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Nov 14 19:44:39.014969 LibreELEC kernel:  iwl_trans_send_cmd+0x6a/0xf0 [iwlwifi]
Nov 14 19:44:39.014951 LibreELEC kernel:  ? __pfx_autoremove_wake_function+0x10/0x10
Nov 14 19:44:39.014969 LibreELEC kernel:  iwl_trans_send_cmd+0x6a/0xf0 [iwlwifi]
Nov 14 19:44:39.014985 LibreELEC kernel:  iwl_mvm_send_cmd_pdu+0x58/0xa0 [iwlmvm]
Nov 14 19:44:39.015002 LibreELEC kernel:  iwl_mvm_mld_cfg_sta.isra.0+0x1b5/0x260 [iwlmvm]
Nov 14 19:44:39.015018 LibreELEC kernel:  iwl_mvm_mld_update_sta+0x7a/0xf0 [iwlmvm]
Nov 14 19:44:39.015035 LibreELEC kernel:  iwl_mvm_mac_sta_state_common+0x16b/0x940 [iwlmvm]
Nov 14 19:44:39.015055 LibreELEC kernel:  iwl_mvm_mld_mac_sta_state+0x19/0x20 [iwlmvm]
Nov 14 19:44:39.015072 LibreELEC kernel:  drv_sta_state+0xf0/0x570 [mac80211]
Nov 14 19:44:39.015090 LibreELEC kernel:  _sta_info_move_state+0x1dd/0x2c0 [mac80211]
Nov 14 19:44:39.015106 LibreELEC kernel:  sta_info_move_state+0x17/0x20 [mac80211]
Nov 14 19:44:39.015122 LibreELEC kernel:  ieee80211_rx_mgmt_assoc_resp+0xe2a/0x2130 [mac80211]
Nov 14 19:44:39.015140 LibreELEC kernel:  ieee80211_sta_rx_queued_mgmt+0xae/0xad0 [mac80211]
Nov 14 19:44:39.015157 LibreELEC kernel:  ? newidle_balance.isra.0+0x30a/0x3a0
Nov 14 19:44:39.015173 LibreELEC kernel:  ? trace_hardirqs_off.part.0+0x20/0x70
Nov 14 19:44:39.015189 LibreELEC kernel:  ? trace_hardirqs_off+0x1d/0x30
Nov 14 19:44:39.015205 LibreELEC kernel:  ? trace_hardirqs_on+0x2f/0x80
Nov 14 19:44:39.015221 LibreELEC kernel:  ieee80211_iface_work+0x30b/0x400 [mac80211]
Nov 14 19:44:39.015238 LibreELEC kernel:  ? trace_hardirqs_off.part.0+0x20/0x70
Nov 14 19:44:39.015257 LibreELEC kernel:  cfg80211_wiphy_work+0xae/0xd0 [cfg80211]
Nov 14 19:44:39.015274 LibreELEC kernel:  process_one_work+0x145/0x2d0
Nov 14 19:44:39.015291 LibreELEC kernel:  worker_thread+0x304/0x450
Nov 14 19:44:39.015307 LibreELEC kernel:  ? __pfx_worker_thread+0x10/0x10
Nov 14 19:44:39.015324 LibreELEC kernel:  kthread+0xdb/0x110
Nov 14 19:44:39.015341 LibreELEC kernel:  ? __pfx_kthread+0x10/0x10
Nov 14 19:44:39.015357 LibreELEC kernel:  ret_from_fork+0x3e/0x60
Nov 14 19:44:39.015373 LibreELEC kernel:  ? __pfx_kthread+0x10/0x10
Nov 14 19:44:39.015389 LibreELEC kernel:  ret_from_fork_asm+0x1b/0x30
Nov 14 19:44:39.015405 LibreELEC kernel:  </TASK>
Nov 14 19:44:39.015422 LibreELEC kernel: iwlwifi 0000:00:14.3: STA_CONFIG_CMD send failed, ret=0xfffffffb
Nov 14 19:44:39.015578 LibreELEC kernel: iwlwifi 0000:00:14.3: Failed to update sta link 0
Nov 14 19:44:39.015718 LibreELEC kernel: wlan0: failed to move station 50:e6:36:1d:72:77 to desired state
Nov 14 19:44:39.015741 LibreELEC kernel: iwlwifi 0000:00:14.3: Failed to trigger RX queues sync (-5)
Nov 14 19:44:39.015884 LibreELEC kernel: iwlwifi 0000:00:14.3: Couldn't send the SESSION_PROTECTION_CMD: -5
Nov 14 19:44:39.016037 LibreELEC kernel: iwlwifi 0000:00:14.3: Failed to send flush command (-5)
Nov 14 19:44:39.438697 LibreELEC iwd[446]: connect event timed out, reason=3
Nov 14 19:44:39.439273 LibreELEC kernel: iwlwifi 0000:00:14.3: Failed to send MAC_CONFIG_CMD (action:2): -5

smf007 they look right. My first response was which images and I reread the title. amlogic. The builds of the kernel are currently failing - thus no images.

libfuse and libfuse3 are included in the network-tools addon package.

libfuse is included in the system-tools addon package.

You will need to reboot after the addon is installed

For LE12 we are moving RPi4 and ARMv8 Allwinner to 64bit userland.

For liso it reads that they have stopped updating their 32 bit images.

please use

systemctl status service.rsyslog

to test, as it sets up the environment and configs.

● service.rsyslog.service - System Logging Service
Loaded: loaded (/storage/.config/system.d/service.rsyslog.service; enabled; preset: disabled)
Active: active (running) since Thu 2023-09-14 08:20:34 UTC; 20s ago
Docs: http://www.rsyslog.com/doc/
Process: 4131670 ExecStartPre=/bin/sh /storage/.kodi/addons/service.rsyslog/bin/rsyslog.init (code=exited, status=0/SUCCESS)
Main PID: 4131684 (rsyslogd)
Tasks: 4 (limit: 36592)
Memory: 5.6M
CPU: 257ms
CGroup: /system.slice/service.rsyslog.service
└─4131684 /storage/.kodi/addons/service.rsyslog/bin/rsyslogd -n -f /storage/.kodi/userdata/addon_data/service.rsysl

Quote from chevy54

Just a FYI using a AMD Ryzen 9 7900X3D on version 11.0.3 will not boot but 11.0.1 will though i can not get the screen refresh rate over 60 Hz . im assuming this is also a driver issue.

is there a work around for this or should i stick with 11.0.1?

Please run latest nightly 11 - it fixes an AMD bug that was in 11.0.3 - RE: Kodi does not start after upgrade from 11.0.1 to 11.0.3 Generic

iwlwifi is only wifi firmware - not BT firmware.

For the firmwares - they are directly matched to kernels, (we don’t include previous versions of iwlwifi - only the matched kernel one) so if you are using the git master tree to build you will have the matched iwlwifi firmware.

Duplicate of https://github.com/LibreELEC/LibreELEC.tv/issues/8125

Supported mechanism to start rsyslog is via addons/systemctl.

I did some looking into this today.

I cant see dmesg for the device (not that that would help me directly.) but good to get all the info.

Here is the code that is being run - just after this (I believe at the time of the crash). debug logs - would be required next. Also what the log would normally say after the last "info <general>: CAESinkALSA - Unable to open device "surround71" for playback"

xbmc/xbmc/cores/AudioEngine/Sinks/AESinkALSA.cpp at 4d639b82d1c9830eb4a010690432f75cc4d756af · xbmc/xbmc

Kodi is an award-winning free and open source home theater/media center software and entertainment hub for digital media. With its beautiful interface and…

github.com

There is nothing in the issues or git since 1.2.10 that looks like it "fixes this."

Arch: armv7l

Release: LibreELEC nightly-20230904-e2439c5

Core was generated by `/usr/lib/kodi/kodi.bin --standalone -fs --audio-backend=alsa+pulseaudio'.

Program terminated with signal SIGSEGV, Segmentation fault.

#0 0x76edf440 in ?? () from /usr/lib/libasound.so.2

Program terminated with signal SIGSEGV, Segmentation fault.

#0 0x76f4d440 in ?? () from /usr/lib/libasound.so.2

2023-09-07 19:07:31.868 T:1080 info <general>: GLES: Maximum texture width: 2048

2023-09-07 19:07:33.630 T:1080 info <general>: load keymapping

2023-09-07 19:07:33.633 T:1080 info <general>: Loading special://xbmc/system/keymaps/appcommand.xml

2023-09-07 19:07:33.636 T:1080 info <general>: Loading special://xbmc/system/keymaps/customcontroller.AppleRemote.xml

2023-09-07 19:07:33.638 T:1080 info <general>: Loading special://xbmc/system/keymaps/customcontroller.Harmony.xml

2023-09-07 19:07:33.642 T:1080 info <general>: Loading special://xbmc/system/keymaps/customcontroller.SiriRemote.xml

2023-09-07 19:07:33.644 T:1080 info <general>: Loading special://xbmc/system/keymaps/gamepad.xml

2023-09-07 19:07:33.648 T:1080 info <general>: Loading special://xbmc/system/keymaps/joystick.xml

2023-09-07 19:07:33.652 T:1080 info <general>: Loading special://xbmc/system/keymaps/keyboard.xml

2023-09-07 19:07:33.659 T:1080 info <general>: Loading special://xbmc/system/keymaps/mouse.xml

2023-09-07 19:07:33.661 T:1080 info <general>: Loading special://xbmc/system/keymaps/remote.xml

2023-09-07 19:07:33.666 T:1080 info <general>: Loading special://xbmc/system/keymaps/touchscreen.xml

2023-09-07 19:07:33.673 T:1080 info <general>: GUI format 1920x1200, Display 1920x1200 @ 60.000000 Hz

2023-09-07 19:07:33.750 T:1086 info <general>: CAESinkALSA - Unable to open device "surround71" for playback

2023-09-07 19:07:33.752 T:1086 info <general>: CAESinkALSA - Unable to open device "surround51" for playback

2023-09-07 19:07:33.752 T:1086 info <general>: CAESinkALSA - Unable to open device "surround71" for playback

2023-09-07 19:07:33.753 T:1086 info <general>: CAESinkALSA - Unable to open device "surround40" for playback

2023-09-07 19:07:33.753 T:1086 info <general>: CAESinkALSA - Unable to open device "surround51" for playback

2023-09-07 19:07:33.754 T:1086 info <general>: CAESinkALSA - Unable to open device "surround71" for playback

** CRASH **

No missing issue. Just change of driver. Please review previous posts. Chkdsk is your friend.

Hi racko - not exactly - we use the standard upstream kernel - which ntfs3 is part of. If you can pinpoint a how to get the failure - then log it with the upstream ntfs3 filesystem kernel - once a fix is in upstream - the LE will pick it up.

Note: I have production ntfs3 and exfat file systems and have not been able to reproduce what is reported. (I have had other ntfs3 issues which I have worked with the kernel and fs developers - but not the “unable to mount” - I do write to this disk.)

Note2: ntfs3 in kernel 6.2-6.5 has had a number patches (some are backported to 6.1 which is used be LE11.) these updated kernels are in the LE12 nightlies - it would be best to test the “reproducible issue” on the current 6.5 kernel before reporting upstream.

Quote from edenmedia

I hope that the developers of Libreelec will collaborate in order to find a solution

Hi edenmedia - all across it

You need to do a chkdsk under windows. The ntfs drivers are different between LE10/11 and some would say “more pedantic”