Grab the firmware from rtw88 - kernel/git/firmware/linux-firmware.git - Repository of firmware blobs for use with the Linux kernel and put it in the firmware directory. https://wiki.libreelec.tv/how-to/add-firmware , rtw88/
Will look at adding this to the next LE10 release - kernel-firmware: add rtw88/rtw8821c_fw.bin to image by heitbaum · Pull Request #5337 · LibreELEC/LibreELEC.tv · GitHub
Please confirm that the firmware does indeed fix your WiFi
[ 3.858805] rtw_8821ce 0000:04:00.0: enabling device (0000 -> 0003)
[ 3.858844] rtw_8821ce 0000:04:00.0: Direct firmware load for rtw88/rtw8821c_fw.bin failed with error -2
[ 3.858849] rtw_8821ce 0000:04:00.0: failed to request firmware
[ 3.861724] rtw_8821ce 0000:04:00.0: failed to load firmware
[ 3.861727] rtw_8821ce 0000:04:00.0: failed to setup chip efuse info
[ 3.861729] rtw_8821ce 0000:04:00.0: failed to setup chip information
[ 3.866169] rtw_8821ce: probe of 0000:04:00.0 failed with error -22
[ 4.777343] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000c lmp_ver=08 lmp_subver=8821
[ 4.778322] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_fw.bin
[ 4.782257] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821c_config.bin
Missing firmware - rtw8821c_fw.bin
Ok. Lucky last idea.
This is my nuc11 - what does Bt*/Bluetooth show.
# lsmod
Module Size Used by
macvlan 24576 0
veth 28672 0
xt_nat 16384 18
xt_tcpudp 20480 30
xt_conntrack 16384 2
xt_MASQUERADE 20480 8
nf_conntrack_netlink 36864 0
nfnetlink 20480 2 nf_conntrack_netlink
xt_addrtype 16384 2
iptable_filter 16384 1
iptable_nat 16384 4
nf_nat 36864 3 xt_nat,iptable_nat,xt_MASQUERADE
nf_conntrack 90112 5 xt_conntrack,nf_nat,xt_nat,nf_conntrack_netlink,xt_MASQUERADE
nf_defrag_ipv6 24576 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
ip_tables 28672 2 iptable_filter,iptable_nat
x_tables 32768 7 xt_conntrack,iptable_filter,xt_tcpudp,xt_addrtype,xt_nat,ip_tables,xt_MASQUERADE
br_netfilter 28672 0
bridge 167936 1 br_netfilter
stp 16384 1 bridge
llc 16384 2 bridge,stp
8021q 24576 0
overlay 118784 11
snd_hda_codec_hdmi 61440 1
iwlmvm 327680 0
wl 6385664 0
mac80211 688128 1 iwlmvm
intel_rapl_msr 20480 0
snd_hda_codec_realtek 118784 1
iwlwifi 307200 1 iwlmvm
snd_hda_codec_generic 73728 1 snd_hda_codec_realtek
ledtrig_audio 16384 1 snd_hda_codec_generic
x86_pkg_temp_thermal 20480 0
intel_powerclamp 20480 0
intel_rapl_common 24576 1 intel_rapl_msr
exfat 73728 3
snd_hda_intel 45056 0
snd_hda_codec 114688 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_hwdep 16384 1 snd_hda_codec
snd_hda_core 73728 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_intel_dspcfg 20480 1 snd_hda_intel
idma64 20480 0
btusb 57344 0
btrtl 24576 1 btusb
btbcm 16384 1 btusb
btintel 24576 1 btusb
bluetooth 524288 5 btrtl,btintel,btbcm,btusb
ftdi_sio 57344 0
usbserial 40960 1 ftdi_sio
cfg80211 696320 4 wl,iwlmvm,iwlwifi,mac80211
ecdh_generic 16384 1 bluetooth
ecc 28672 1 ecdh_generic
rfkill 24576 4 bluetooth,cfg80211
pkcs8_key_parser 16384 0
fuse 114688 1Hmmm. Your dmesg does not show the same as mine. (No hci0)
[ 4.080620] Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
[ 4.081621] Bluetooth: hci0: Device revision is 2
[ 4.081623] Bluetooth: hci0: Secure boot is enabled
[ 4.081624] Bluetooth: hci0: OTP lock is enabled
[ 4.081625] Bluetooth: hci0: API lock is enabled
[ 4.081626] Bluetooth: hci0: Debug lock is disabled
[ 4.081626] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 4.085839] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-4.sfi
[ 5.740089] Bluetooth: hci0: Waiting for firmware download to complete
[ 5.741653] Bluetooth: hci0: Firmware loaded in 1622776 usecs
[ 5.741674] Bluetooth: hci0: Waiting for device to boot
[ 5.756628] Bluetooth: hci0: Device booted in 14622 usecs
[ 5.759722] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
[ 5.761690] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 5.764722] Bluetooth: hci0: Firmware revision 0.0 build 121 week 7 2021
What does this show?
# lshw -C network
# lspci -knn | grep Net; rfkill list
00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 [8086:a0f0] (rev 20)
0: hci0: bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: wlan
Soft blocked: no
Hard blocked: no
Also - as below (fast boot in bios)
drivers - Intel Wi-fi 6 AX200 adapter not found on Ubuntu 20.04 - Ask Ubuntu
Looking at the logs, I can see that the AX200 looks ok. I’m using an AX201 on TGL, that needs the fw59 too. You are correct the AX200 is standalone, though the AX210 I purchased to test with does not work in my test systems. Locks them up. In my day job we have over 4000 AX200/AX201 windows devices that the 21.x driver is shocking and until 22.30/40 pretty poor. 22.20 was ok ish. I would like to see you running the LE10b2 code (kernel 5.10.30) which has had a number of little fixes both settings app / kernel ...
Regarding 5.1 kernel - 202085 – iwlwifi: 9560: ASSERT 2B80 unsure on the state of that kernel / this bug / that firmware.
We need to check the revision of the BT firmware in the firmware file ibt-20-1-3 - linux-firmware: Update firmware file for Intel Bluetooth AX200 · pop-os/linux-firmware@9e96e50 · GitHub
nuc11:/usr/lib/kernel-overlays/base/lib/firmware/intel # ls -la ibt-20-1-3.*
-rw-rw-r-- 1 root root 9 Apr 17 00:13 ibt-20-1-3.ddc
-rw-rw-r-- 1 root root 773896 Apr 17 00:13 ibt-20-1-3.sfi
nuc11:/usr/lib/kernel-overlays/base/lib/firmware/intel # md5sum ibt-20-1-3.*
ad54af0edef90047fd14d01517f3c8db ibt-20-1-3.ddc
3d65048d633b0960615976852355280e ibt-20-1-3.sfi
That being all the low level stuff. Within the LE10 settings app. What is Bluetooth doing/showing in terms of devices?
Can you please share your dmesg from the J5005. There have been quite a large number of updates in the kernels with WiFi. But would like to see what versions of BT/WiFi you are running.
Hi all, same here.
Can you give me some more instructions. I noticed that I don't have make, or cant use apt-get on libreelec ... so how I am supposed to build something?
Thanks.
Hi pajzinka LibreELEC does not have an apt-get function. You can add addons through Kodi. If you are looking to develop or compile a custom LibreELEC- the follow link from the wiki will get you started. https://wiki.libreelec.tv/development-1/build-basics
tried it several times. it crashes after playing 2-3 songs. doesn't matter which song.
Codefull kod.log: http://ix.io/2VSdwould be great if someone can look into it!
(after a quick search it looks like a utf-8 problem: python - UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 23: ordinal not in range(128) - Stack Overflow )
thx very much!
jomir could you please check @ Issues · librespot-org/librespot · GitHub and
Commits · librespot-org/librespot · GitHub And see if this a know bug or if there is a known fix? otherwise - can you please raise it as an issue. Do any of your song titles have extended characters?
Supposedly : Manage Chrome Browser updates (Linux) - Google Chrome Enterprise Help
To stop Chrome Browser auto-updating, take one of the following actions:
$ sudo touch /etc/default/google-chromerepo_add_once=falseDoes this require adding to the base image? Or will / does it use the addon home?
Good morning Saale - it doesn’t work on RPi LE10 see LE 10 b1 - Hyperion NG also some other background is you search for Hyperion
Apr 04 20:20:32.259050 HTPC kernel: usbcore: registered new interface driver ftdi_sio
Apr 04 20:20:32.259086 HTPC kernel: usbserial: USB Serial support registered for FTDI USB Serial Device
Apr 04 20:20:32.259099 HTPC kernel: ftdi_sio 1-1.5.1:1.0: FTDI USB Serial Device converter detected
Apr 04 20:20:32.259255 HTPC kernel: usb 1-1.5.1: Detected FT232RL
Apr 04 20:20:32.262619 HTPC kernel: usb 1-1.5.1: FTDI USB Serial Device converter now attached to ttyUSB0Apr 04 20:21:02.981781 HTPC systemd[1]: service.lcdd.service: Scheduled restart job, restart counter is at 4.
Apr 04 20:21:02.982293 HTPC systemd[1]: Stopped LCDProc.
Apr 04 20:21:02.984274 HTPC systemd[1]: Started LCDProc.
Apr 04 20:21:02.992908 HTPC sh[1066]: LCDd 0.5dev, LCDproc Protocol 0.4
...
Apr 04 20:21:02.995331 HTPC sh[1066]: irtrans: unable to init client socket
Apr 04 20:21:02.995331 HTPC sh[1066]: Driver [irtrans] init failed, return code -1
Apr 04 20:21:02.995331 HTPC sh[1066]: Could not load driver irtrans
Apr 04 20:21:02.995410 HTPC sh[1066]: There is no output driver
Apr 04 20:21:02.995410 HTPC sh[1066]: Critical error while initializing, abort.
Apr 04 20:21:02.995743 HTPC systemd[1]: service.lcdd.service: Main process exited, code=exited, status=1/FAILURE
Apr 04 20:21:02.995853 HTPC systemd[1]: service.lcdd.service: Failed with result 'exit-code'.
Apr 04 20:21:03.527916 HTPC systemd[1]: systemd-hostnamed.service: Succeeded.
Apr 04 20:21:08.231772 HTPC systemd[1]: service.lcdd.service: Scheduled restart job, restart counter is at 5.
Apr 04 20:21:08.232308 HTPC systemd[1]: Stopped LCDProc.
Apr 04 20:21:08.232358 HTPC systemd[1]: service.lcdd.service: Start request repeated too quickly.
Apr 04 20:21:08.232377 HTPC systemd[1]: service.lcdd.service: Failed with result 'exit-code'.
Apr 04 20:21:08.232817 HTPC systemd[1]: Failed to start LCDProc.Looking at the logs this is what I can see. Is the RT232RL your ir receiver?
What does lsusb -t and lsusb -v show? Where / have you configured the ttyUSB0?
Of course, changing the 'y' for a 1 in
/storage/.kodi/addons/service.system.syncthing/bin/syncthing-service works great, but just wanted to let you know
.
Including your find in the addon bump - syncthing: update to 1.15.1 by heitbaum · Pull Request #5306 · LibreELEC/LibreELEC.tv · GitHub
tekhop - look for updated addons tomorrow - kodi-binary-addons: update to latest versions by heitbaum · Pull Request #5304 · LibreELEC/LibreELEC.tv · GitHub - let us know how you go.
Added to my dev build / run tree. So far so good.
Hi matthuo - search for “widevine 32” in the forum. But a good response from one of the posts is:
“arm" is 64-bit kernel and 32-bit userspace for compatibilty with add-ons that need software widevine (DRM) support, and aarch64 is 64-bit kernel and 64-bit userspace which means no widevine support (as only 32-bit libs are sourceable).
There are a number of community members / builds that build aarch64 user space. But not in the main, so as to support the widevine.
