Posts by ilmich

Hi alexwhites can you please try with another build (for example this one https://drive.google.com/file/d/1omh0Yz…cSuIILHqf43DgPu)?!.

In recent builds I have tried to change the cpu voltages a bit. Maybe that's the problem.

Hi all,

I've released an updated build with a new kernel and some little optimizations. See changelog in the first post.

hi alexwhites,

I'm trying to upgrade the kernel, and in the meantime see if I can backport any patches from the rockchip kernel. But the box, despite the unwatchable screen, still works !? Can you send the output of the dmesg command ?!

JoeEdison although old, with libreelec my box is still usable. And I think with libreelec 11 things could get even better

Hi alexwhites,

after some research, i realized that maybe the problem lies in the rgb <--> yuv conversion.

In practice, the TV communicates, via edid, that this resolution is in a format and therefore the driver behaves accordingly.

In your case it looks like the TV sets itself in one format, but the driver in another and hence the colors busted.

I did not understand if the problem is in the kernel or in the TV, however the legacy driver should force the output in rgb format.

I try to do the same thing and see if it works.

EDIT: try this kernel

testing – Google Drive

Hi alexwhites

according to the edid you have an ACER full hd monitor(or tv), probably with some bugs.

I have enabled a kernel hack for your particular device which prefer a particular frequency. Put this kernel inside the first partition of sdcard (obviously remove the resolution forcing)

testing – Google Drive

and let me known.

Regarding ssv6051 thanks to jock2 there is a driver for mainline but with libreelec I've experienced some problems.

Maybe in the future there will be a better driver, but for now I recommend you to use a usb wifi device. Sorry

Hi all,

I've released an updated build with several stability fixes. See changelog in the first post.

dale, unfortunately NAND is a complicated thing. But I'll do my best

Hi alexwhites

do you have a 4k tv ?!?! green screen usually indicates a resolution not supported by the driver.

try to edit the extlinux / extlinux.conf file present in the fat partition of the sd card by adding

video=HDMI-A-1:1280x720

if works, in a ssh session launch this command

cat /sys/class/drm/card1-HDMI-A-1/edid > /storage/edid

and share the file /storage/edid

thanks

Hi juliomm64,

thanks for the feedback, i have restored my gdrive folder

hi JoeEdison, Lajos

with my latest build, I've fixed some small issue, updated libreelec upstream code, and I've also fixed and enabled suspend to ram with wakeup with remote(that should be better than virtual power off)

edit: virtual power off is not abandoned, just I need more time.

Hi Lajos, thanks for your feedback.

Quote from Lajos

Hello! V88K Plus, The remote control works at startup but if I turn it off it can't be turned on afterwards, it works well in version 9.

I known, I'm working on backport the 'virtual poweroff' driver from legacy kernel.

Libreelec 10

FEATURES

- kodi matrix 19.5

- mainline kernel 5.10.186

- mainline opensource gpu driver

- legacy u-boot

- ddr3 frequency scaling

- boot from SD

- boot from EMMC (thanks to jock2 for testing)

- boot from NAND

- ir receiver (it works, but if your remote is not recognized, follow this guide https://wiki.libreelec.tv/configuration/ir-remotes and share results)

- wifi/bluetooth only if there is a mainline driver (I'll do my best for others, but is more safe eventually to buy an external adapter)

- hardware accelerated video decoding (mpeg2/h264/hvec/vp9). only FullHD tested, because I don't own a 4k tv.

- virtualpoweroff with wakeup with remote

- analog audio

DOWNLOADS

- older builds (< september 2022): https://drive.google.com/drive/folders/…0IoQVjQdlMaafNx

- builds: https://ilmich.libreelec.tv/libreelec-10/

- source: https://github.com/ilmich/LibreELEC.tv/tree/libreelec-10.0

INSTALLATION

- for boot from SD see https://wiki.libreelec.tv/installation/create-media

MANUAL UPDATE

Copy (via ssh,samba, etc etc) the desired build into folder

/storage/.update

and reboot device.

INITIAL SETUP

To allow booting in most cases, the image uses a generic device tree. This device tree doesn't have support for ddr3 ram, doesn't turn on any LEDs, etc etc.

However, it's possible to change the device tree by choosing from the supported devices list with rk322x-dtb-switch.sh command.

rkelec:~ # rk322x-dtb-switch.sh
usage: /usr/bin/rk322x-dtb-switch.sh [list|switch|help]


show                      show current device tree
list                      show available device trees
switch [device tree]      switch to a device tree
help                      show this help

sample session

rkelec:~ # rk322x-dtb-switch.sh switch rk3229-box-v88mars
Device tree rk3229-box-v88mars founded
Are you sure(y/n)?y
Mounting flash rw
Switching dtb
Mounting flash ro
Switching is ok, now you need to reboot!!

SUPPORTED DEVICES

The following table shows the supported devices (with device trees).

Device trees with the suffix -ovclk contain some changes to slightly overclock cpu/ram. Overclocks are tested, but may make your board unstable. So use them at your own risk.

KNOWN ISSUES

- gui may not be smooth (it also depends a lot on the skin used, like legacy builds)

- for drm contents, resolutions >= 720p are not guaranteed. This is because decoding is software and the cpu/gpu may not make it

- analogic video not works (and maybe never will)

- let me known

SUGGESTIONS

- if you have problems with pvr clients during channel switch, set a delay of around 200ms in order to let kodi and gpu release resources correctly.

- stay at 720p and let kodi switch resolution when play something

- without your logs, I can't try to fix anything

CHANGELOG

2022/02/03: Initial release

2022/02/10: added ddr3 support, spdif output, other fixes

2022/02/17: updated to latest libreelec source code, fix suspend to ram and wakeup with remote, other small fixes

2022/02/21: undervolt cpu/gpu to avoid random freeze, disabled dmabuf because lima driver seems buggy, other small fixes

2022/02/26: bump kernel to 5.10.102, new remote (thanks to shMatrix), changed default cpu governor, enabled RTL8192CU and RTL8XXXU wifi drivers

2022/03/05: bump kernel to 5.10.103, updated to latest libreelec source code with kodi 19.4, backported (and fixed) NAND driver from rockchip bsp kernel 5.10.x, other stability fixes

2022/03/08: updated mesa to 21.3.7, legacy device tree added, some kernel and boot optimizations

2022/03/10: updated to latest libreelec source code (10.0.2), added ssv6051p wireless driver

2022/03/20: kernel 5.10.107, mesa 22.0.0, updated to latest libreelec source code, dmabuf, new hk1mini device, new remote, removed wakeup from remote, various fixes

2022/03/29: kernel 5.10.109, updated to latest libreelec source, backported rockchip remotectl, various fixes

2022/04/22: kernel 5.10.111, updated to latest libreelec source, mesa 22.0.1, various fixes/improvements

2022/05/14: kernel 5.10.116, updated to latest libreelec source, mesa 22.0.2, various fixes/improvements

2022/06/15: kernel 5.10.120, updated to latest libreelec source, mesa 22.0.5, various fixes/improvements

2022/07/07: kernel 5.10.128, updated to latest libreelec source, experimental esp8089 wireless driver, analog audio codec, various fixes/improvements

2022/09/21: kernel 5.10.142, updated to latest libreelec source, mesa 22.2.0, added rtl8192fu driver, various fixes/improvements

2022/10/03: kernel 5.10.146, updated to latest libreelec source, fix regression in hardware deinterlace filter

2022/10/17: kernel 5.10.148, updated to latest libreelec source, fix for a remote controller, fix HDMI alsa card name

2022/11/02: kernel 5.10.152, updated to latest libreelec source, mesa 22.2.2, fix for ssv6051p arp issue, various small fixes

2022/11/22: kernel 5.10.155, updated to latest libreelec source, mesa 22.2.4, various small fixes, added RTL8188FU driver

2022/12/15: kernel 5.10.158, updated to latest libreelec source, mesa 22.3.0, various small fixes

2023/01/13: kernel 5.10.162, updated to latest libreelec source, mesa 22.3.2, kodi 19.5

2023/02/06: kernel 5.10.167, updated to latest libreelec source, mesa 23.0.0-rc4

2023/03/06: kernel 5.10.172, updated to latest libreelec source, mesa 23.0.0, new t95vpro box, various fixes, supports USB Bluetooth dongle

2023/04/02: kernel 5.10.176, mesa 23.0.1, backported some kodi Nexus patches

on mainline kernel there is no need to edit dts, because wifi should be recognized automatically via the sdio bus.

hi bluetako , my tips is for libreelec 9.2. On mainline kernel works different.

Try my unofficial build of libreelec 10 with kernel 5.10.x

Thread

[UNOFFICIAL][Le11-10][RK3228/RK3229][box]Libreelec builds

Hi,

thanks to the experience gained with my builds of libreelec 9.2.x and the work of the community (rockchip and more), I'm sharing my unofficial build of libreelec for boxes with soc rockchip 322x.

** BIG FAT WARNING **
** I won't waste too much time on the subject of pirate streaming. Know that it's not tolerated by me. **
** I will try to help with legal addons (which I don't develop directly anyway). But if you have problems **
** with other kinds of addons, nothing personal, I will ignore you.…

ilmich

February 3, 2022 at 10:10 AM

hi bluetako

on legacy rockchip kernel there is a module called rfkill that is responsible for the wifi wakeup and probe.

So in your dtb leave the 'wlan-platdata' in the WiFi node (this autoload rfkill) and change the wifi chip type according to your chip (for example rtl8723as).

If works let me known, because I'm not working anymore on this build, but I know that for some users LE 9.2 is better. So maybe I'll try to add also this device

cheers

Hi,

thanks to the experience gained with my builds of libreelec 9.2.x and the work of the community (rockchip and more), I'm sharing my unofficial build of libreelec for boxes with soc rockchip 322x.

** BIG FAT WARNING **
** I won't waste too much time on the subject of pirate streaming. Know that it's not tolerated by me. **
** I will try to help with legal addons (which I don't develop directly anyway). But if you have problems **
** with other kinds of addons, nothing personal, I will ignore you. **

Libreelec 11

FEATURES
- Kodi Nexus 20.4
- mainline kernel 6.1.74
- mainline opensource GPU driver
- legacy u-boot
- boot from SD
- ir receiver (it works, but if your remote is not recognized, follow this guide https://wiki.libreelec.tv/configuration/ir-remotes and share results)
- support for wifi chip SSV6051p, ESP8089, AP6255, and others if supported by mainline kernel.
- hardware accelerated video decoding (mpeg2/h264/hvec/vp9). only FullHD tested because I don't own a 4k tv.
- analog audio
- DDR3 frequency scaling

DOWNLOADS
- builds: https://ilmich.libreelec.tv/libreelec-11/
- source: https://github.com/ilmich/LibreELEC.tv/tree/libreelec-11.0

INSTALLATION
- for boot from SD see https://wiki.libreelec.tv/installation/create-media

MANUAL UPDATE
Copy (via ssh,samba, etc etc) the desired build into a folder
Code

/storage/.update

and reboot the device.

INITIAL SETUP
To allow booting in most cases, the image uses a generic device tree. This device tree doesn't have support for ddr3 ram, doesn't turn on any LEDs, etc etc.
However, it's possible to change the device tree by choosing from the supported devices list with rk322x-dtb-switch.sh command.

rkelec:~ # rk322x-dtb-switch.sh
usage: /usr/bin/rk322x-dtb-switch.sh [list|switch|help]


show                      show current device tree
list                      show available device trees
switch [device tree]      switch to a device tree
help                      show this help

sample session

rkelec:~ # rk322x-dtb-switch.sh switch rk3229-box-v88mars
Device tree rk3229-box-v88mars founded
Are you sure(y/n)?y
Mounting flash rw
Switching dtb
Mounting flash ro
Switching is ok, now you need to reboot!!

SUPPORTED DEVICES

KNOWN ISSUES
- some strange wifi chip
- some strange USB Wi-Fi chip (I can add it if you help me)
- NAND (this is the hard part and the only legacy piece that remains)

SUGGESTIONS
- without your logs, I can't try to fix anything

CHANGELOG
2023/03/15: Initial release (announcement)
2023/03/22: updated to latest Libreelec commit, reverted https://github.com/xbmc/xbmc/pull/22919, estuary skin optimization (read here)
2023/12/02: updated mesa 23.3.0, added bcm43342 wireless firmware, raise ddr3 clock, added simple irqbalancer, added 2 new mxq4k and mxq4kpro variant, various fixes and improvements
2023/12/30: mesa 23.3.2 and kernel 6.1.68, preemptive kernel for better performance, various fixes and improvements, updated to latest libreelec source
2024/02/18: mesa 23.3.6 and kernel 6.1.74, added RTL8812CU usb wifi driver (untested), various fixes and improvements, updated to latest libreelec source (11.0.6)

THANKS TO
knaerzche , jock2, fabiobassa, oneillb, Habitual6824, ochentay4 and the libreelec community.

DONATE
If you like this project help:
- by first donating to Libreelec main project https://opencollective.com/libreelec/donate
- and secondly by helping me to buy/repair rk322x hardware https://www.paypal.com/paypalme/ilmich6502 or https://revolut.me/ilmich

I don't know if officially there are devices with mali 4xx, but I solved it by applying this patch to mesa 21.0.3.

lima: limit number of draws per job (!10121) · Merge requests · Mesa / mesa

Otherwise we may hit tile heap size limit if an app issues too many draws per job. Fixes

gitlab.freedesktop.org

this patch is now also upstream.

Quote from bluetako

Looks like it's bcm4329.

Code

h96miniv8:/ # cat /sys/firmware/devicetree/base/dwmmc@30010000/wifi@1/compatible
brcm,bcm4329-fmac

EDIT: this seems to be wrong - it's coming straight from the dts. Is it possible to get the wifi card model from the sysfs, or do I have to open up the box?

unfortunately yes, you have to open the box and read the label of the wifi chip, or if you have another working SO (like Android), retrieve the information in another way.

ilovefly if you have a spare sd card why not but keep in mind that often info about ram can be faked on Android (on libreelec instead it's the real one)

I updated mesa to the latest version and saw that there are several improvements and bugfixes for lima driver.

the problem seems to have disappeared

cheers

Michele