Posts by ilmich

jock2 is the greatest expert on these boxes (and beyond). Without him, these builds wouldn't exist because he taught me a lot. So the options he used are 100% the best.

I'll try to make some changes and send you a build to test.

For the options you can use in the dts unfortunately u-boot legacy is not well documented so the only way is to look at the driver

u-boot/drivers/mmc/rockchip_dw_mmc.c at next-dev · rockchip-linux/u-boot

U-Boot tree for pending commits. Contribute to rockchip-linux/u-boot development by creating an account on GitHub.

github.com

However, from what I understand, the emmc that your box has is of a particular type and requires some precautions (I think the option that makes it work is the max-frequency option)

Hi pocng looks promising. I'll try to make the changes to the emmc node of dts or if you have time, feel free to send me a pull request on github

Quote from pocng

PS : in my previous post when i say "multiboot" = U-Boot form multitool => https://github.com/paolosabatino/…tepnand-patches)

So you're saying that
- libreelec flashed in emmc
- replaced the bootloader with the one of multitool
does boot work?

If so, I'll try to check the jock2 patches and understand what needs to be done to fix your problem.

hi pocng are you sure you have an mmc and not a NAND?

When you start the multitool it should alert you to the difference. This is because libreelec 11 does not work with NAND so the behavior you are complaining about is normal.

Quote from pocng

Which parameters did you modify in U-Boot?

I disabled NAND because since it doesn't work, there's no point in having it enabled in u-boot

pocng try this test image

Index of /libreelec-11/test/

let me know

hi pocng it's strange because in both cases the emmc memory is detected by the miniloader

Boot1 Release Time: May 13 2019 17:02:59, version: 2.56
ChipType = 0xc, 380
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=1000
UserCapSize=7456MB

I'll try to make some changes to the bootloader and send you a test image.

Hi,

I don't have this board, but with the help of deleonkikkoI produced this test build.

rock-4c-plus

If anyone can do more testing (especially with the 2k display port connector) before officially releasing it and report the problems to me that would be great.

deleonkikko Regarding the Rock pi 4C+ I saw that the device trees in u-boot and mainline kernel are present. So a porting attempt is possible. Unfortunately, I don't have that board so if you can help me with tests I can propose it as a new device (to be included in libreelec 13, to check if it can also be added later in libreelec 12)

Quote from SixSixTwo

It's a bit baffling that an older beta was working good (well, crashes aside) while not one but two releases are crippled and the current beta is just as broken.

It's a little disconcerting until you go in and see how much code has changed.

As for the slowness with 4K, the subject of this thread which I imagine you haven't read to the end, it has been written that it also depends (but not only) on the DDR4 clock. the fix in question is being tested and will be released as soon as possible.

in the meantime, you can try this old test build and see if it improves anything

roc-3328-cc

SixSixTwo what resolution? I imagine 4k. however there are known problems with the 3328 and unfortunately you have to be patient for the fixes. In the meantime, try with a lower resolution and/or try with another HDMI cable.

Hi luisfp

Quote from luisfp

I just have a question about the Python version these builds are using?

the same as the official libreelec 11 which is 3.11.2.

Quote from luisfp

I am trying to install Zach's repo for games and am not able to get it working. I've installed v1.0.4. Installs but does nothing. I'm not able to install Advance Emulator Launcher or Internet Archive Game Launcher due to Python dependency not met. Any ideas what I might be doing wrong?

it's strange, could you kindly send some logs?

Quote from tonitrus

hello there, ive figured out the solution which is to change the resolution and refresh rate in the kodi settings, tho now idk why but my connections tab is completely empty, it works with wired as ive tested(tho i wouldnt wanna use it since my router is half broken) but when theres no wired connection is it purely blank

maybe your box has an unsupported wireless chip. To confirm I would need photos of the internal board, or some photos taken from the Android settings. In any case if you don't want to use the ethernet card I recommend a USB wifi adapter

Quote from carlosed

ilmich are you creating a new post on libreelec 12 or do you plan to keep this topic? I'll keep an eye on your progress.

I think I'll make a new post.

rk3318 is the little brother of the rk3328.. try the official ones for this soc. It's not guaranteed that everything will work but they should almost boot.

Hi, actually in the librecomputer source repositories I saw that I can try to increase the clock a little more.I'll do some tests.
Regarding the resolution problem with my monitor, everything works correctly with libreelec 9.2 (which has the vendor kernel). With all other subsequent versions it doesn't switch me to 720p (I don't have a 4k device). When you can, can you also do some tests with libreelec 9.2? Just to better understand if it supports all resolutions and therefore be on the safe side by trying to understand the differences between vendor and mainline (the drivers have been rewritten but the starting point is the kernel vendor)

chaconet please without logs I can't help you

on my boxes WiFi works as usual.

chaconet without logs I can't help you.

ham-egg-and-chips wich model of box? no particolar issue for me at 24hz.

Hi FurmanSK your observations are correct, in many cases the operations are accelerated via hardware (gpu, decoding) so before the bottleneck was the ram which at low speeds kept the cpu busy which had the task of waiting and synchronizing the texture movements and video streams. the ram now runs at 800mhz and the bottleneck has moved (even if with estuary I reach 30fps)
the resolution problem is known, from the little I've seen there is a regression in kernel 6.6 which has impacts almost everywhere. I'm trying to understand more

Hi FurmanSK,

try this test image, https://ilmich.libreelec.tv/test-images/roc-3328-cc/

source code

GitHub - rockchip-with-unofficial-love/LibreELEC.tv at roc-cc-le12-wip

Just enough OS for KODI. Contribute to rockchip-with-unofficial-love/LibreELEC.tv development by creating an account on GitHub.

github.com

let me know.

Michele