Item 1 "git grep estouchy" should help you find the places you need to edit to prevent it being bundled. Items 2/3/4 are addressed via advancedsettings.xml configuration (more git grep will help that). Item 5 you can add packages to the image if they are LE add-ons. If they are third party add-ons it can be done, but we intentionally avoid providing instructions as there are people out there keen to bundle pirate add-ons and repos and that shitware is bad for our name. Item 6 is solved by adding "UBOOT_SYSTEM=box" to the build command.
Posts by chewitt
-
-
Kodi does not support interlaced output, only progressive. Anything you force via kernel DRM during boot will be overriden later.
-
We aren't fans of RTL chips that have no upstream support (assuming that's the issue).
-
Code
Feb 16 18:10:58.938037 LibreELEC kernel: Linux version 6.1.14 (docker@af3b48037063) (aarch64-none-elf-gcc-12.2.0 (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39) #1 SMP PREEMPT Mon Feb 27 21:44:00 UTC 2023^ This tells me that you aren't booting the LE 11.0.0 image that I linked so there is no Realtek driver included. There is no support for the RTL chip in our main releases and that is unlikely to change. It is currently included in my private image.
https://chewitt.libreelec.tv/testing/LibreE….arm-11.0.2.tar <= don't pay too much attention to the version number, it just means it's ahead of LE 11.0.1 official images.
-
Note that "xrandr" is no longer available in the default Generic (x86_64) image as it switched to GBM/V4L2 graphics with LE11. You would need to use the "Generic Legacy" image which uses the older Xorg graphics stack.
-
I'm sure there are many happy users, and it's been a popular case. However our (forum moderator) experience with it is mostly all-bad. The case requires internal connections between HDMI and other connections on the board and the external ports on the case and these cause problems. The standard protocol when we see 'Argon' anywhere in the issue report is "remove the board from the case, all working now?" and in 9/10 situations users refuse to believe it's the case, but when we insist and they finally cave in and remove the board; the problem was the case. Caveat Emptor
-
There's a DNS resolution error with api.pluto.tv and then a series of Python errors with missing dependencies; all of which are quite obvious if you search for 'error' in the logfile. It's not an issue with LE code, so the errors need to be reported to the respective add-on authors via the add-on support threads in the Kodi forum.
-
The "invalid-key" error is probably bugs in iwd affecting a small number of users. We've bumped iwd to the latest release in LE11 nightlies and this appears to resolve it for most users. Update to the latest nightly here: https://test.libreelec.tv/11.0/Amlogic/wetek-play2/ and report back. The issue is tracked here: https://github.com/LibreELEC/LibreELEC.tv/issues/7166
The dmesg messages are correct and harmless.
For double results; an educated guess is that connman is scanning in the background so its results are visible to the dbus agent in the LE settings add-on, and then you're running scans via iwd and its results are also visible. If you don't run the manual iwd scan do you still see duplicates?
-
If reverting the kernel change on your NAS eliminates the issue, then you need to bisect the changes between the working and non-working kernel versions to pinpoint the problem commit; then report this to the upstream kernel maintainers to pursue a fix. Before sending emails to mailing lists I'd suggest you also check that fixes are not already merged into newer (and current development) kernels to avoid reporting a problem that's already resolved.
-
Why my wetek hub boot only from generic box img? This version https://releases.libreelec.tv/LibreELEC-AMLG…etek-hub.img.gz doesn’t work.
It does work, but it's a board image designed to be installed to emmc (overwriting Android). The box image is the correct image to use if you're booting the device from an SD card. Read: https://wiki.libreelec.tv/hardware/amlogic
-
The dmesg log looks fine, the WiFi NIC is probed without errors. Some German users (a guess based on your name) need to have the 80211 regdomain configured in LE settings (under Network) before networks can be seen. See if setting to 'DE' makes a difference?
-
In the absence of a debug log it's hard to comment, but some add-ons are geolocked and only accessible to users in specific countries; is my guess at the probable cause. If the add-on requires a subscription (and some do) that's normally obvious; the add-on settings panel will have options for adding login credentials.
-
One of the niceties of the upstream kernel is that we don't ever need to care about 1G/2G/3G RAM configurations of boards; the kernel works with whatever u-boot makes available. And yes the boot process is different (which is clearly stated in release notes and wiki, but not all users read them). The differences are in part to align with other LE platforms; but also deliberate to force clean installs and thus sidestep the carnage that comes with the Kodi Python2 > Python3 changes between legacy and current images.
-
-
I really hope to make LE work and install to internal in the future.
^ that is NOT going to happen, even if you do manage to install something: https://wiki.libreelec.tv/hardware/amlogic#install2internal
-
You have banned add-ons installed. No support will be offered.
-
Ahh, okay. Amlogic chips support multiple video output layers. The OSD (GUI) layer is 1080p max while the video layer can be 4K. The 1080p OSD limit is a silicon limitation but legacy images allow you to set 4K .. which the hardware then ignores and outputs at 1080p, while the user feels smug because they have a 4K TV and their Android box configured for 4K. It's a bit like the S905 being advertised with 2GHz CPU speed; which is 1.5`GHz if you want more than one CPU core active, but the firmware lies and reports 2GHz
TL/DR; 1080p is the correct resolution for the GUI (hence it's the default). If you configure 4K the OSD layer is still 1080p and some TVs might stretch it, and others will render it to 1/4 of the screen. NB: We don't support 4K H264 on S905 (it works on S905X and up, but not S905) but that's prob. not an issue as 99.99999% of 4K media is HEVC. There is no HDR to SDR conversion.
-
H264 and HEVC are both hardware decoded. H264 playback/seeking works well. HEVC playback works wel, but seeking doesn't always work so great - the decoder is unfinished. AMLGX will not be for all users and all media, but it's easy to experiement on a spare SD card.
