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
Posts by heitbaum
-
-
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.
Code
Display More● 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 -
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/xbmcKodi 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.comThere 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.
-
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”
-
-
Yup - Kodi update. I have kicked off the pvr builds. They should be there in the morning. If there are other addons then we might need to increment the addons (was hoping that alpha3 and the xcrypt updates aligned with this)
-
Hello,
I have the same problem, it only works for me ( LibreELEC-Generic.x86_64-11.0-nightly-20230816-1d807c8.img ).
there will be a new revision where it works ?
my hardware: AMD Ryzen 7 5800h with AMD Radeon Graphics
The nightly release 20230816 you are running is pretty much 11.0.3 with the amd fix. You will not have any compatibility issues compared to users using the 11.0.3 release.
Here is a full changelog (but note - most of the commits are addon updates)
Comparing 11.0.3...1d807c80fe38998046b676ff4528e7a4773a2661 · LibreELEC/LibreELEC.tvJust enough OS for KODI. Contribute to LibreELEC/LibreELEC.tv development by creating an account on GitHub.github.com -
I figured out maybe connect with cat5 to router is my only way. Viola!
Ok. Problem is here. There have been lots of changes in the rtw88 driver into kernel 6.4. So would suggest you try the Generic LE12 nightly.
Code
Display More[ 7.057419] EXT4-fs (sda6): mounted filesystem with ordered data mode. Quota mode: disabled. [ 7.166430] BUG: unable to handle page fault for address: ffffa8fed1850014 [ 7.166469] #PF: supervisor read access in kernel mode [ 7.166486] #PF: error_code(0x0000) - not-present page [ 7.166501] PGD 110000067 P4D 110000067 PUD 110238067 PMD 0 [ 7.166521] Oops: 0000 [#1] SMP NOPTI [ 7.166537] CPU: 1 PID: 393 Comm: (udev-worker) Not tainted 6.1.45 #1 [ 7.166558] Hardware name: LENOVO 81H5/LNVNB161216, BIOS 8ZCN27WW(V2.06) 01/12/2021 [ 7.166580] RIP: 0010:rtw_pci_read32+0x16/0x20 [rtw88_pci] [ 7.166603] Code: 48 03 b7 a0 7a 00 00 48 89 e5 66 8b 06 5d e9 a1 b7 62 d7 90 f3 0f 1e fa 0f 1f 44 00 00 55 89 f6 48 03 b7 a0 7a 00 00 48 89 e5 <8b> 06 5d e9 82 b7 62 d7 66 90 f3 0f 1e fa 0f 1f 44 00 00 55 89 f6 [ 7.166646] RSP: 0018:ffffa8fec157b8f8 EFLAGS: 00010286 [ 7.166662] RAX: ffffffffc03d8040 RBX: ffffffffc04cf040 RCX: 0000000000000000 [ 7.166682] RDX: 0000000000000000 RSI: ffffa8fed1850014 RDI: ffff9c435d502060 [ 7.166701] RBP: ffffa8fec157b8f8 R08: 000000000000019e R09: 000000000000002d [ 7.166727] R10: 0000000001406bd9 R11: 00000000f5257d14 R12: 00000000c03dc000 [ 7.166746] R13: ffff9c435d505660 R14: ffff9c435d5069b8 R15: ffff9c435d502060 [ 7.166764] FS: 00007fea80dce800(0000) GS:ffff9c462f480000(0000) knlGS:0000000000000000 [ 7.166786] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 7.166803] CR2: ffffa8fed1850014 CR3: 0000000114f5a000 CR4: 00000000001506a0 [ 7.166822] Call Trace: [ 7.166834] <TASK> [ 7.166848] ? __die_body.cold+0x1a/0x1f [ 7.166866] ? __die+0x2e/0x39 [ 7.166880] ? page_fault_oops+0xaf/0x260 [ 7.166895] ? __module_address+0x2f/0x90 [ 7.166912] ? search_module_extables+0x16/0x50 [ 7.166930] ? rtw_pci_read32+0x16/0x20 [rtw88_pci] [ 7.166951] ? search_exception_tables+0x57/0x70 [ 7.166970] ? kernelmode_fixup_or_oops+0xa2/0x120 [ 7.166986] ? __bad_area_nosemaphore+0x167/0x1c0 [ 7.167001] ? trace_hardirqs_on+0x3a/0xe0 [ 7.167016] ? bad_area_nosemaphore+0x16/0x20 [ 7.167031] ? do_kern_addr_fault+0x65/0x80 [ 7.167045] ? exc_page_fault+0xbc/0x140 [ 7.167061] ? asm_exc_page_fault+0x2b/0x30 [ 7.167079] ? rtw_pci_read16+0x20/0x20 [rtw88_pci] [ 7.167097] ? rtw_pci_read32+0x16/0x20 [rtw88_pci] [ 7.167116] rtw_mac_power_switch+0xbc/0x440 [rtw88_core] [ 7.167145] ? __schedule+0x1d5/0x5c0 [ 7.167159] rtw_mac_power_on+0x36/0x280 [rtw88_core] [ 7.167180] rtw_chip_info_setup+0x131/0x580 [rtw88_core] [ 7.167201] rtw_pci_probe+0x610/0x906 [rtw88_pci] [ 7.167219] local_pci_probe+0x4b/0x90 [ 7.167237] pci_device_probe+0xb5/0x1b0 [ 7.167255] really_probe+0xe7/0x390 [ 7.167272] ? pm_runtime_barrier+0x5f/0xa0 [ 7.167288] __driver_probe_device+0x7d/0x130 [ 7.167933] driver_probe_device+0x24/0xa0 [ 7.168585] __driver_attach+0xdd/0x1d0 [ 7.169213] ? __device_attach_driver+0x120/0x120 [ 7.169886] bus_for_each_dev+0x80/0xc0 [ 7.170530] driver_attach+0x22/0x30 [ 7.171223] bus_add_driver+0x1ba/0x210 [ 7.171835] ? trace_hardirqs_on+0x3a/0xe0 [ 7.172423] driver_register+0x93/0xf0 [ 7.173040] ? 0xffffffffc03ff000 [ 7.173589] __pci_register_driver+0x66/0x70 [ 7.174213] rtw_8821ce_driver_init+0x27/0x1000 [rtw88_8821ce] [ 7.174776] do_one_initcall+0x4e/0x1f0 [ 7.175347] ? kmalloc_trace+0x2e/0xa0 [ 7.175893] do_init_module+0x50/0x1e0 [ 7.176415] load_module+0x1d17/0x1e70 [ 7.176973] ? 0xffffffffc03ff000 [ 7.177521] ? kernel_read+0x29/0x60 [ 7.178054] ? kernel_read_file+0x121/0x270 [ 7.178592] __do_sys_finit_module+0xbd/0x130 [ 7.179088] ? __do_sys_finit_module+0xbd/0x130 [ 7.179590] __x64_sys_finit_module+0x1c/0x30 [ 7.180105] do_syscall_64+0x3e/0x90 [ 7.180614] entry_SYSCALL_64_after_hwframe+0x69/0xd3 [ 7.181119] RIP: 0033:0x7fea80ec3079 [ 7.181639] Code: 08 89 e8 5b 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 57 3d 0c 00 f7 d8 64 89 01 48 [ 7.182774] RSP: 002b:00007ffe83eab6d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 [ 7.183339] RAX: ffffffffffffffda RBX: 0000000001726210 RCX: 00007fea80ec3079 [ 7.183945] RDX: 0000000000000000 RSI: 00007fea80ff9573 RDI: 0000000000000014 [ 7.184534] RBP: 00007fea80ff9573 R08: 0000000000000000 R09: 0000000000000000 [ 7.185134] R10: 0000000000000014 R11: 0000000000000246 R12: 0000000000020000 [ 7.185710] R13: 0000000000000000 R14: 000000000171fd60 R15: 0000000000000000 [ 7.186281] </TASK> [ 7.186860] Modules linked in: rtw88_8821ce(+) rtw88_8821c rtw88_pci rtw88_core mac80211 btusb btrtl btbcm libarc4 btintel btmtk uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 bluetooth snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic videobuf2_common ledtrig_audio k10temp fam15h_power cfg80211 videodev snd_hda_intel snd_intel_dspcfg mc ecdh_generic ecc snd_hda_codec snd_hda_core snd_hwdep rfkill pkcs8_key_parser fuse dmi_sysfs [ 7.187104] ACPI BIOS Error (bug): [ 7.188596] CR2: ffffa8fed1850014 [ 7.188599] ---[ end trace 0000000000000000 ]--- [ 7.188602] RIP: 0010:rtw_pci_read32+0x16/0x20 [rtw88_pci] [ 7.188615] Code: 48 03 b7 a0 7a 00 00 48 89 e5 66 8b 06 5d e9 a1 b7 62 d7 90 f3 0f 1e fa 0f 1f 44 00 00 55 89 f6 48 03 b7 a0 7a 00 00 48 89 e5 <8b> 06 5d e9 82 b7 62 d7 66 90 f3 0f 1e fa 0f 1f 44 00 00 55 89 f6 [ 7.188617] RSP: 0018:ffffa8fec157b8f8 EFLAGS: 00010286 [ 7.188621] RAX: ffffffffc03d8040 RBX: ffffffffc04cf040 RCX: 0000000000000000 [ 7.188622] RDX: 0000000000000000 RSI: ffffa8fed1850014 RDI: ffff9c435d502060 [ 7.188624] RBP: ffffa8fec157b8f8 R08: 000000000000019e R09: 000000000000002d [ 7.189273] Could not resolve symbol [\_PR.C002.PPCV], AE_NOT_FOUND [ 7.189894] R10: 0000000001406bd9 R11: 00000000f5257d14 R12: 00000000c03dc000 [ 7.190541] (20220331/psargs-330) [ 7.191121] R13: ffff9c435d505660 R14: ffff9c435d5069b8 R15: ffff9c435d502060 [ 7.192412] ACPI Error: [ 7.193086] FS: 00007fea80dce800(0000) GS:ffff9c462f480000(0000) knlGS:0000000000000000 [ 7.199612] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 7.200438] CR2: ffffa8fed1850014 CR3: 0000000114f5a000 CR4: 00000000001506a0 [ 7.201236] note: (udev-worker)[393] exited with irqs disabled [ 7.204926] rtw_8821ce 0000:02:00.0: Firmware version 24.11.0, H2C version 12 -
The network card is a rtl8821ce based on the attached. And we have CONFIG_RTW88_8821CE=m in the LE configuration. so in dmesg it should show the card being made active.
Code*-network description: Wireless interface product: RTL8821CE 802.11ac PCIe Wireless Network Adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@0000:02:00.0 logical name: wlp2s0 version: 00 serial: 28:39:26:09:95:31 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtl8821ce driverversion=5.15.0-79-generic ip=192.168.0.61 latency=0 multicast=yes wireless=IEEE 802.11AC resources: irq:42 ioport:2000(size=256) memory:f1000000-f100ffff -
I updated the drivers to the latest available but so far still no luck. I'll try a fresh install later and see if there is difference. As always thanks for the help.
I’ll need to see the logs/especially dmesg. As we don’t know what network cards are in this device.
Other ways to share what the device is:
lshw -class network # this is in the system tools addon
lsusb
lspci
-
First log is a kodi on mint log.
Second log is the LE Kodi.log, but does not include the dmesg/lspci/lsusb that we need to check what is happening on the network/hardware side. Based on the spec sheet it is a Realtek or Qualcomm wireless.
