Regarding high cpu usage, I've
- increased kernel tick
- changed cpu governor to ondemand
this is necessary for a better UI experience.
Regarding high cpu usage, I've
- increased kernel tick
- changed cpu governor to ondemand
this is necessary for a better UI experience.
Hi, I try to briefly explain the problems you are looking at.
Unfortunately, although I receive boxes from time to time, I don't have all the variants
Anyway if
- the box does not start or you see errors --> cpu voltages
- the box freezes after a while (you notice this because the led that usually flashes when you use the remote control, stays still) --> gpu voltages.
- kodi restarts --> generic bug that may depend on corrupted file, unstable network, etc etc. However bugs that do not directly depend on the build (almost 80% of the times).
To solve the overheating problems, over time I have experimented with different voltages from the official ones and I thought I had found working ones more or less everywhere.
Instead, some time ago I received a box that crashed on boot and therefore with the January release I fixed a little bit.
Unfortunately in February I did another experiment and now you have problems.
My suggestion is to stick with the January release and better specify what happens to you (if it falls into one of the cases that I have indicated to you).
I also ask you to send me the output of this command (from an ssh shell inside the box)
this is the internal rk3229 efuse, and inside there is the information to check if your box tolerate some voltages or not.
Cheers
Michele
thanks for logs.
try to switch dtb (according to 1stpost) in order to match your hardware.
default dtb is generic and without (for example) ddr3 frequency scaling
4k contents are unplayable with that dtb (and in general with boxes without ddr3)
make sure that also your network are reliable.
I don't see hardware errors in your logs
Hi Habitual6824,
try with my January build( archive folder ).
In the eternal search of optimal voltages settings, in my last build I've changed something.
Hi ilmich ,
Would you be interested in supporting the Grandstream GVC3212 perchance? Here is its vendor page, firmware, FCC documentation, and it appears to have an RK3228H chip onboard.
Hi dan25
all Rockchip devices work pretty much the same, so it wouldn't be impossible to do.
And it would be nice to do so, unfortunately without the device available it's difficult to test everything.
I found a tool
that explodes the firmware you linked, but it needs a decryption key.
However the rk3228h should be the 64bit version of the rk3228.
Cheers
Michele
Hi all,
new build available with:
- linux 5.10.167
- mesa 23.0.0-rc4
- updated libreelec to the latest upstream changes
I started working on libreelec-11, but you have to be patient, private life is slowing me down.
Cheers
Michele
Hi all,
new build available with:
- linux 5.10.162
- mesa 22.3.2
- kodi 19.5
- updated libreelec to the latest upstream changes
This may be the latest build of Libreelec 10.0
Kodi Nexus is around the corner, and I will start working on Libreelec 11.
Cheers
Michele
Hi punter,
thanks for the logs
Feb 02 15:29:48.501460 LibreELEC kernel: mmcblk2: mmc2:0001 M8G2FA 7.45 GiB
Feb 02 15:29:48.501580 LibreELEC kernel: mmcblk2boot0: mmc2:0001 M8G2FA partition 1 512 KiB
Feb 02 15:29:48.501699 LibreELEC kernel: mmcblk2boot1: mmc2:0001 M8G2FA partition 2 512 KiB
Feb 02 15:29:48.501831 LibreELEC kernel: mmcblk2rpmb: mmc2:0001 M8G2FA partition 3 128 KiB, chardev (243:0)
the internal emmc was successfully detected.
So which tool doesn't work, the multitool?!
Anyway, you can try to install the build directly from sd card. Copy the desired Libreelec build somewhere in the storage partition of sdcard and do something like this
and if you want to make a backup first (which I suggest)
There is a script to automate everything in my to-do list, but installing Libreelec in internal memory is a procedure for those who know what to do. So I preferred to wait for the builds to become more stable.
Try and let me known.
Michele
hi punter,
please, reboot the board because the kernel log is rotated and the first messages are lost.
thank you
please, could you share a full dmesg log?! The best way to do that is described here (https://wiki.libreelec.tv/support/log-files)
thanks a lot.
Michele
Hello anjarys
I'm glad you like it. What kind of box do you have!?!
Anyway, I haven't written a tutorial (yet), but the best tool is the multitool made by jock2 for armbian.
You can find it here https://forum.armbian.com/topic/12656-cs…k322x-tv-boxes/.
Basically, it's a small operating system that allows you to backup/restore internal memory and flash images. It works perfectly and you can find the details in the excellent guide by jock2. (clearly the guide is for armbian, but it also applies to libreelec images)
Let me know if you have any problems.
Cheers
Michele
other news.
I'm working on a fork of rkflashtool improving it as much as possible:
The goal is to create a tool (also graphical and for windows) to facilitate flash operations on internal memory (especially nand). The multitool is the best tool, but for those with nand devices, not the most optimal(yet).
Hi all,
new build available with:
- linux 5.10.158
- mesa 22.3.0
- upgraded and fixed legacy bootloader
- updated libreelec to the latest upstream changes
There's good news. Thanks to the libreelec community, I have official space for my builds. The new link can be found in the first post.
I'm starting to remove some old builds (gdrive for sure).
Cheers
Michele
Hi SN33KY
don't worry, I didn't take it personally.
But for users reading, you were just unlucky and impatient.
By the way, in my region (europe) the hardware you mentioned seems out of production and even looking for it used it costs much more than 100€ (and often sold without hard disk and with 16GB of ram).
Could you please tell me where did you buy the box you returned?! I'm also looking for one with emcp.
thank you
Michele
Hi SN33KY,
the important thing is that you have satisfied your need, even if I'm sorry because with your contribution I could have fixed something.
For me, it makes little sense to compare an Android box to a PC (although I prefer boxes because they are silent and consume very little electricity).
However, in my experience, you pay for what you get. What gets sacrificed to keep costs down with the Android boxes I see around is the quality of the software. For example, Amazon products have an even older soc than rk3229. But the software is of good quality and therefore works.
My project aims to fill the gap by bringing high quality software (libreelec) to these devices. Unfortunately time, skills, and availability of devices for tests... sometimes makes it difficult to please everyone
hi SN33KY, do you have an A-to-A USB cable!? Do you normally use linux or windows!?
I recently discovered a problem with the boot and NAND memory (which is not your case) that prevent libreelec from starting correctly (it was necessary to flash an ad-hoc loader afterward). I'm currently on a short vacation and can't share the fix with you. But if you have what I asked you can try to flash a loader using rockchip tools in order to better understand the problem.
Hi SN33KY,
thanks for the log.
Feb 02 15:29:48.943159 LibreELEC kernel: mmc0: new high speed SDHC card at address 0007
Feb 02 15:29:48.944287 LibreELEC kernel: mmc_host mmc1: Bus speed (slot 0) = 2343750Hz (slot req 300000Hz, actual 292968HZ div = 4)
Feb 02 15:29:48.944589 LibreELEC kernel: mmcblk0: mmc0:0007 SD04G 3.74 GiB
Feb 02 15:29:48.944790 LibreELEC kernel: mmcblk0: p1 p2
Feb 02 15:29:48.945774 LibreELEC kernel: mmc_host mmc1: Bus speed (slot 0) = 2343750Hz (slot req 200000Hz, actual 195312HZ div = 6)
Feb 02 15:29:48.946896 LibreELEC kernel: mmc_host mmc2: Bus speed (slot 0) = 12000000Hz (slot req 25000000Hz, actual 12000000HZ div = 0)
Feb 02 15:29:48.947349 LibreELEC kernel: mmc2: new MMC card at address 0001
Feb 02 15:29:48.947572 LibreELEC kernel: mmcblk2: mmc2:0001 Q72SMB 7.28 GiB
Feb 02 15:29:48.947755 LibreELEC kernel: mmcblk2boot0: mmc2:0001 Q72SMB partition 1 4.00 MiB
Feb 02 15:29:48.948035 LibreELEC kernel: mmcblk2boot1: mmc2:0001 Q72SMB partition 2 4.00 MiB
Feb 02 15:29:48.948216 LibreELEC kernel: mmcblk2rpmb: mmc2:0001 Q72SMB partition 3 512 KiB, chardev (243:0)
Feb 02 15:29:48.948374 LibreELEC kernel: mmcblk2: p1 p2
Feb 02 15:29:48.949322 LibreELEC kernel: mmc_host mmc1: Bus speed (slot 0) = 2343750Hz (slot req 100000Hz, actual 97656HZ div = 12)
Display More
Here I see that you are using a 4GB sd card and your internal memory is 8GB (which is the norm for these boxes and probably the seller put in false characteristics).
Then everything is detected correctly.
As for the installation via multitool, the procedure is
- erase the internal memory with the dedicated option
- flash the image
did you do it this way?!
Hi SN33KY,
you probably have a box that mounts an internal EMCP memory.
This type of memory differs slightly from the classic emmc (on the board you should see a single chip for internal and ddr memory).
Unfortunately, I do not have a box of this type, but it would be helpful a log(https://wiki.libreelec.tv/support/log-files) generated starting from the SD card.
I want to check if it's a detection problem or something else.
thanks
Michele