hi szczur3k, can you send me a log, please? I saw that that driver is now included in the kernel and I enabled it. I can also enable another one but I would first like to understand what problems it has. Thank you
Posts by ilmich
-
-
Hi usr4864 piotrekg1984 , in the next build I'll try to go back/improve some changes. In the meantime, can you point me to a better version by trying the previous ones?
usr4864 from the log I see, Kodi crashed while you were configuring something, but I don't rule out a bug. It also happened to me once while configuring the IPTV client and I 'solved' it by reformatting the SD card.
-
Hi all,
a new build of libreelec 11 available with:
- mesa 23.3.2 and kernel 6.1.68
- preemptive kernel for better performance
- various fixes and improvements
- updated to latest libreelec sourceSome features are missing (like NAND).
My build of Libreelec 11 has some breaking changes that make it incompatible with previous Libreelec 10 builds. In other words, there is no easy way to upgrade your Libreelec 10 setup to Libreelec 11.
Cheers
Michele -
fsdonato I'm very sorry, however you can continue to use libreelec via SD card (which is much better because you have no space limitations given that there are SD cards of 128GB and above). it's a shame to throw it away
-
Hi punter, update libre11 from libre10 is not supported because I've renamed the device trees.
you must manually reselect the specific device tree of your box as described in first post
-
Now I have Armbian with kernel 6.1 working fine (my falut, I didn't reset internal eMMC; I thought sdcard had priority during boot process).
If I remember correctly, the boot sequence always starts from internal memory, and then from a certain point onwards, it goes to the SD card. This causes problems with old bootloaders (as in your case). So either you update what is in the internal memory, or you reset it so that it takes everything from the SD.
Librelec is still stopping a few rows after kernel start, but now I have a working dtb to try and compare, so I think I know how to proceed.
Good, from the error I see that it could be a problem with the cpu frequencies. Try removing the cpu0_opp node.
-
Should I expect to have also the early boot (minloader-ddrbin-trustos) at 115200? Now this is 1500000.
Trust is a closed binary, but for ddrbin there is a tool that configures these things. so I would tell you that if everything went well everything is now at 115200.
Don't worry, you already helped a lot. I will continue by cutting branches on dtb (or merging from the one I've extracted) and maybe also trying to boot Armbian (if it really works) to compare things. I will keep you updated.
If you get Armbian with kernel 6.1 (should be the stable one) the dtb is compatible, jock2 and I exchange information.
-
Btw, the log of uboot is still at 115200bps, maybe something is missing...
it's normal, now everything is at 115200 (as it should be). regarding the device tree you have probably studied, but they are files that describe the device (how many USB ports it has.. if it has HDMI.. internal storage.. etc etc)
Unfortunately this week I'm busy at work, and I don't know how much I can help you (having said that without device was hard for me). However, I advise you to take the dtb of the latest build that I sent you, decompile it (there is a tool called dtc), and try to remove some pieces (for example the part that indicates the CPU frequencies).
However, if I think of anything else I'll let you know. -
There was no need to rebuild the image, you could just overwrite the file on the sdcard. However, if you want to compile the images update my repo to the latest commit. I'm updating based on your feedback.
Please try this test imageI've fixed uboot, uart baudrare, and include the suggested dtb.
-
digicroxx try this dtb please.
edit: dased on the uart log it seems like a CPU voltage problem. I'm trying to extract the dtb of the firmware you sent.
-
I hope I have not messed something up with the tests in the last days, but it seems that the new uboot behaviour it's similar to what I've got with the multitool's uboot.
Great, so now my uboot is ok for your board, I see it loads the kernel. Now I'll try to understand what jock2 suggested to you and I'll make you an ad-hoc dtb.
Also this one switches serial to 115200bps, was this expected?
I'll fix this too. I'll ask you to flash a test image again to clean up any dirty tests.
-
Hi FurmanSK thanks to Chewitt and Da from Librecomputer, I have ordered this board and it should arrive soon so I can do the necessary tests. I will keep you updated, surely if I can improve something it will happen in libreelec 12.
-
digicroxx A thousand thanks!! I'm glad that the problem isn't trust, because your fw version doesn't work well on my boxes. At this point, I think the problem is my bootloader. Try this when you can and let me know.
-
Hi FurmanSK, try
just to verify that my intuition is correct, I reused the legacy bootloader and ported a couple of kodi patches that are in Omega that increase performance.
Remember that decoding 4k contents and smooth UI at 4k resolution are different. So please try with a lower UI resolution, and let kodi player switch to 4k when needed.
Cheers
Micheleedit: if works share the output of cat /sys/kernel/debug/clk/clk_summary
-
hi digicroxx, try this
and let me know. In the meantime, I'm testing this oldest trust with my boxes.
Michele
-
-
ilmich , I know your build are unofficial and some things are different, but since I'm not expert of official librelec either, it's not a big deal for me... From my point of view yours is the official repo
.
it was to tell you that, for example, mogrify is a tool that I use to reduce the textures of the estuary skin so for those who build my repo it is normal.
And google is my friend expecially when I'm able to ask questions with enough details to filter out misleading links, so do you maybe have a good starting point to suggest for me to learn how to unpack h20 fw?
I apologize, but you have to understand that giving a hand to everyone by guiding them step by step sometimes becomes difficult for me (lack of time). however you can use rkunpackfw tool from this
https://github.com/ilmich/rkflashtoolif you want to try to insert it into the build you have to change here
https://github.com/ilmich/LibreEL…der/install#L16 -
fsdonato sorry, can you please explain better your use case(better if step by step)? I want to reproduce your issue.