Posts by heitbaum

Quote from yamcenutzer

Thanks for the info. I am glad to hear that Nucs are still extensively used for testing. I am however sorry to learn, that especially the 11gen have issues. The reason I got myself a nuc11 after years of happy using a nuc5 was that the nuc11 are the last ones with CIR. Also the nuc12 seemed even more overkill. I guess I'll now have to wait for the ASUS p42 with a n100 to start working, although I'd rather prefer my Nuc11. It's the smallest i3 (the pentiums don't have CIR). Any chance the nuc11 issues (what are they one you know about?) get resolved. I have issues with Audio coming and going and passthrouh not working as mentioned above near the starting posts of this thread.
The other issue has to do with the tv.hts client not playing uhd streams with VAAPI, which, I guess, is not really related to the chip.

I haven’t tested nuc11 for ages but the pass through “issue” I was able to reproduce on the NUC11PAHi7 regularly. The coming and going audio I have not experienced. The issue I experienced was “audio goes” and a reboot was required.

Some clarification - Intel NUC is used heavily and extensively in testing of all LE releases - specifically a NUC12WSKi7, and previously NUC6,10,11. There are known “issues” with audio on NUC11 that I have personally experienced, but are not occurring on a NUC12WSKi7. So not sure what issues are being referenced. There are LSPCON issues in some NUC devices that have caused issue.

Note: when using “new” (not yet upstreamed hardware) e.g. the AX100 wireless, some of the N100 chips … there will be 12-18 months of pain for the purchaser (note - I run bleeding edge software (and release candidate / patches) - to allow testing and running on these newer generations of hardware.) so LE is pretty much up to date as much as possible for support of newer hardware. But if the hardware being purchased is not fully supported by Kernel 6.6.y for Intel equipment (I can only vouch for the NUC mentioned) then you will have issues as this is the release that we are going with for LE12.

Next thing is unfortunately Intel has left the NUC business, and as an avid NUC users, have not decided on my next Intel direction. But after LE12 is released - I will probably be focussed on using the AMD Beelink SER7 - but this will bring its own challenges.

You will want to start here. So not a generic or generic-legacy image.

To be forewarned - scripts/build Kodi is currently failing in this make image.

PROJECT=Generic ARCH=x86_64 DEVICE=wayland make image

ghtester addon is updated now

The plugins are not built (except the pulse ones - but then only from the snapcast addon)

GitHub - alsa-project/alsa-plugins: The Advanced Linux Sound Architecture (ALSA) - plugins

The Advanced Linux Sound Architecture (ALSA) - plugins - GitHub - alsa-project/alsa-plugins: The Advanced Linux Sound Architecture (ALSA) - plugins

github.com

packages/addons/service/snapclient/package.mk:PKG_DEPENDS_TARGET="toolchain alsa-plugins snapcast"

LibreELEC.tv/packages/addons/addon-depends/snapcast-depends/alsa-plugins/package.mk at master · LibreELEC/LibreELEC.tv

Just enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.

github.com

smbus.so fixed in https://github.com/LibreELEC/Libr…dc4b3779a9a4eab

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.