Posts by rdorsch

Hello,

I was not entirely sure if I should submit this under Bug Reports or Rockchip. I decided for Rockchip since the issue might be limited to Rockchip or even rock64.

My setup

• Hardware: pine rock64
• Libreelec: 12.0.1
• Network: Ethernet

The problem occurs when playing a stream file with inputstream.adaptive (it also occurs in the ARDundZDF plugin, but I thought it is easier to debug if it can be reproed with just a simple stream file):

rock64b:~ # cat fs/videos/Streams/TV/04_ard_one.strm
#KODIPROP:inputstream=inputstream.adaptive
#KODIPROP:inputstream.adaptive.manifest_type=hls
https://mcdn.one.ard.de/ardone/hls/master.m3u8

rock64b:~ #

Issues observed:

• when navigating forward and backward, the video often plays for one or two seconds and then pauses for tens of seconds (during this time the OSD shows a high CPU load and one core is at 100%)
• the video flickers somewhat (also the reported fps on the OSD is less than the 50 Hz of the video stream reported by the "o" key)
• sometimes the systems hangs entirely (not in the attached debuglog)

The problem started to show up quite sometime back, but I cannot tell if it is due to a change in LibreELEC or due to a change in the stream.

In the logs, I see warnings like

<general>: OutputPicture - timeout waiting for buffer

Full kodi debug log is here:

https://paste.libreelec.tv/cool-jaybird.log

Any idea or hint is welcome.

Thanks

Rainer

For the wifi problem there is a long thread here (I see the same with a wetek play 2):

[BUG] Invalid-key while connecting to wifi - LE11 · Issue #7166 · LibreELEC/LibreELEC.tv

Describe the bug Hello :) Since upgrading to LireElec 10 (10.0.3) the wifi is really unstable. Every now and then, LibreElec will forget the wifi password and…

github.com

Hello,

while I was trying to track down https://github.com/LibreELEC/LibreELEC.tv/issues/8446 I wrote a small bisecting script for LibreELEC. Although it needs source modifications for at least the test condition and IP address, it might be useful for somebody, therefore I uploaded it to

https://bokomoko.de/~rd/Libreelec/le-bisect.sh

Quote from Cissou

Nope sorry only ethernet

And for now I'm still using Coreelec 9, as LE11 don't shut off, using LE 11 as test

LE12 power off works now for me (e.g. LibreELEC-AMLGX.arm-12.0-nightly-20231130-0d2323e-box.img.gz) and wifi as long as the router has FT disabled as well.

An issue I see with LE12: If I scroll in a stream (e.g. ARD Mediathek), the player freezes immediately and sound stops somewhat later. But maybe that is also a settings issue, I just used the default config, I just configured wifi.

Thanks, let's see, how it goes: https://lore.kernel.org/connman/2928343.uEfu3JUVZN@h370/T/#u

w46n3r : No libreelec is not a router. But I give it direct access to an internal vlan and a separate vlan for internet connection (this is rather a workaround for a router limitation).

But where is it defined that eth0.1 is the default route to the internet? I recently had internet not working until I brought eth0.7 down, probably eth0.7 was configured as default route. Is it the first network which gets configured? In this case I would need to introduce an ordering dependency into the eth*.service files.

Hi,

I setup three VLANs on Libreelec 11.0.3

rock64:~/.config/system.d # cat eth0-1.service
[Unit]
Description=Set VLAN interface for direct internet VLAN
Before=network.target multi-user.target
After=dbus.service network-base.service


[Service]
ExecStart=/sbin/vconfig add eth0 1


[Install]
WantedBy=multi-user.target
rock64:~/.config/system.d # cat eth0-2.service
[Unit]
Description=Set VLAN interface for direct internet VLAN
Before=network.target multi-user.target
After=dbus.service network-base.service


[Service]
ExecStart=/sbin/vconfig add eth0 2


[Install]
WantedBy=multi-user.target
rock64:~/.config/system.d # cat eth0-7.service
[Unit]
Description=Set VLAN interface for direct internet VLAN
Before=network.target multi-user.target
After=dbus.service network-base.service


[Service]
ExecStart=/sbin/vconfig add eth0 7


[Install]
WantedBy=multi-user.target
rock64:~/.config/system.d # route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth0.1
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0.1
192.168.0.1     0.0.0.0         255.255.255.255 UH    0      0        0 eth0.1
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0.2
192.168.2.1     0.0.0.0         255.255.255.255 UH    0      0        0 eth0.2
192.168.7.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0.7
192.168.7.1     0.0.0.0         255.255.255.255 UH    0      0        0 eth0.7
rock64:~/.config/system.d #

Can anybody tell how I can control which network interface becomes the default route?

Thanks

Rainer

Many thanks for the explanation.

I already configured the wireless regdomain in the LE settings add-on, but channel 1 did not work.

Now I just booted the system again, confirmed that the wireless regdomain is set and I saw channel 1 w/o any issues.

Wetek:~ # iw dev wlan0 scan
BSS c8:d3:a3:5e:9d:48(on wlan0)
last seen: 967.449s [boottime]
TSF: 0 usec (0d, 00:00:00)
freq: 2412
beacon interval: 100 TUs
capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
signal: -68.00 dBm
last seen: 0 ms ago
SSID: DLAN
Supported rates: 6.0* 9.0 12.0* 18.0 24.0* 36.0 48.0 54.0
DS Parameter set: channel 1
TIM: DTIM Count 1 DTIM Period 2 Bitmap Control 0x0 Bitmap[0] 0x0
ERP: <no flags>
RSN:     * Version: 1
* Group cipher: CCMP
* Pairwise ciphers: CCMP
* Authentication suites: PSK FT/PSK
* Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
BSS Load:
* station count: 4
* channel utilisation: 24/255
* available admission capacity: 0 [*32us]
Supported operating classes:
* current operating class: 81
HT capabilities:
Capabilities: 0x116e
HT20/HT40
SM Power Save disabled
RX HT20 SGI
RX HT40 SGI
RX STBC 1-stream
Max AMSDU length: 3839 bytes
DSSS/CCK HT40
Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
Minimum RX AMPDU time spacing: 8 usec (0x06)
HT TX/RX MCS rate indexes supported: 0-7
HT operation:
* primary channel: 1
* secondary channel offset: no secondary
* STA channel width: 20 MHz
* RIFS: 0
* HT protection: no
* non-GF present: 1
* OBSS non-GF present: 0
* dual beacon: 0
* dual CTS protection: 0
* STBC beacon: 0
* L-SIG TXOP Prot: 0
* PCO active: 0
* PCO phase: 0
Extended capabilities:
* Extended Channel Switching
* QoS Map
* UTF-8 SSID
* Operating Mode Notification
WMM:     * Parameter version 1
* u-APSD
* BE: CW 15-1023, AIFSN 3
* BK: CW 15-1023, AIFSN 7
* VI: CW 7-15, AIFSN 2, TXOP 3008 usec
* VO: CW 3-7, AIFSN 2, TXOP 1504 usec
Wetek:~ #

I still experience the invalid-key issue reported in https://github.com/LibreELEC/LibreELEC.tv/issues/7166 though.

Boots fine, dmesg output is here

https://bokomoko.de/~rd/Libreelec/2023-08-01-wetek-play-2-dmesg.out

I noticed that it does not see my wlan AP on channel 1. Switching the AP to channel 6 makes the network visible.

In the dmesg output I find

[ 10.369177] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available

Can anybody tell if that has something todo with the wifi channels?

Wow, Amlogic builds are back in LE12. Many thanks.

Are you using wifi with your wetek play? If yes, is you wifi signal strength OK? If yes, did you do something to get to an OK signal strength?

Quote from chewitt

[...] NB: I'm not sure what advantage you're expecting with aarch64, but it's not going to noticeably improve anything and you will have to reinstall or remove binary add-ons) as they are not aarch64 compatible; and there will be no replacement binary add-ons in the repo as there are no ARM aarch64 releases for LE11 so the add-ons weren't built/don't exist. [...]

I was not sure what the right architecture is and I found quite a few references to aarch64, therefore I build for aarch64. I saw no obvious glitches or issues with it in my very basic tests. But honestly they were limited to the wifi invalid-key issue, I did not even attempt to play any content.

Do I understand you correctly that ARCH=arm is used for the nightly builds and the LE11 releases?

Quote from chewitt

The kernel patchset is ridiculously large but will reduce if I ever find the enthusiasm to rebase it on a newer kernel. I have no plans to do that in the near-term future though.

I think that after you completed the Ironman your enthusiasm for everything will dramatically increase even further

I tried https://test.libreelec.tv/12.0/NXP/cubox…06-cubox.img.gz on a cubox-i.

Initially everything went fine, I downloaded a plugin (ARD aktuell) and played the latest Tagesschau stream. It started to play well, but after moving forth and back in the stream, kodi hang very soon (not the system itself, could still ssh into it).

I thought I paste the output of dmesg, which reports warnings and bugs, just in case it is useful for anybody.

Thanks

Rainer

[Moderator edit: Log file moved from insecure link to attachment.]

Would

iwd: update to 2.6 · LibreELEC/LibreELEC.tv@97e1ced

log: - https://git.kernel.org/pub/scm/network/wireless/iwd.git/log/

github.com

and

connman: update to 24180d1 (1.41+/2022-04-11) · LibreELEC/LibreELEC.tv@5680288

log: - https://git.kernel.org/pub/scm/network/connman/connman.git/log/

github.com

be enough to apply on LE11?

And

PROJECT=Amlogic DEVICE=AMLGX ARCH=aarch64 UBOOT_SYSTEM=box make image

the right build command?

I just saw the list of kernel patches for Amlogic. The three digits list is very impressive. That a significant part contains FROMGIT-6.2 or FROMGIT-6.3 gives some hope, that eventually that gets more managable. But there are still many patches remaining. Thanks for all the effort you put into extending the life these devices.

Thanks for your reply and enjoy the Ironman triathlon

I am most interested in the wifi updates mentioned here

[BUG] Invalid-key while connecting to wifi - LE11 · Issue #7166 · LibreELEC/LibreELEC.tv

Describe the bug Hello :) Since upgrading to LireElec 10 (10.0.3) the wifi is really unstable. Every now and then, LibreElec will forget the wifi password and…

github.com

Will they also be added to LE11 eventually? Or is it more likely to see Amlogic in LE12 again?

Hello everybody,

I see no Amlogic builds in

https://test.libreelec.tv/12.0/

Does LE12 not build on Amlogic or is it just a build time issue and building it locally on my machine should work fine?

Thanks

Rainer

I had the same issue sometime back. You need to manage to select once boot from SD card, then it does it automatically in the subsequent boots.

Unfortunately, I don't recall anymore what I did wrong, but try to read

https://wiki.libreelec.tv/hardware/amlogic/wetek-hub-play2

carefully and follow the procedure, it worked for me at the end.

That's more complex than I thought or I don't know enough to understand it:

• Both drivers are under the GPL.
• The Debian driver has these items in modinfo
  • version: v4.1.4_6773.20130222 (entry is missing in kernel 6.1)
  • author: Realtek Semiconductor Corp.
  • description: Realtek Wireless Lan Driver
  • license: GPL
  • staging: Y
  • retpoline: Y
  • intree: Y
  • name: r8188eu
• The libreelec driver has these items in modinfo
  • license: GPL
  • description: RTL8XXXu USB mac80211 Wireless LAN Driver
  • author: Jes Sorensen <[email protected]>
  • intree: Y
  • name: rtl8xxxu

What I don't understand:

• Both drivers are GPL, why are there two drivers and what is the benefit of the rtl8xxxu driver?
• According to modinfo and the Debian kernel package, the Debian module is from staging:
  rd@h370:/lib/modules/5.10.0-21-amd64$ find -name r8188eu.ko
  
  ./kernel/drivers/staging/rtl8188eu/r8188eu.ko
  rd@h370:/lib/modules/5.10.0-21-amd64$ dpkg -S /lib/modules/5.10.0-21-amd64/kernel/drivers/staging/rtl8188eu/r8188eu.ko
  linux-image-5.10.0-21-amd64: /lib/modules/5.10.0-21-amd64/kernel/drivers/staging/rtl8188eu/r8188eu.ko
  rd@h370:/lib/modules/5.10.0-21-amd64$
  
  This rather seems to be that Debian is enabling staging whereas libreelec has just the intree module, correct?