Hi keesijp60
I don't quite understand, does your box go to maskrom because you deleted the internal memory? or does it go there on its own, a sign that your internal memory is broken?
Another question, does the multitool tell you that your box has NAND as storage type? Because in that case, you can't install libreelec in the internal memory, but you can only boot it from the SD card. Let me know
hi chaconet, please send me some log, wifi model etc etc
Your box seems a clone of tanix x2 that should works.
Hi areq1987, Libreelec is an optimized for kodi linux distribution, not an Android custom rom.
You must
- create a bootable sd card (follow instructions in the first post)
- connect the box to a network and login as root with ssh
- switch from generic box to mxq pro 4k(or the one that works for you)(follow instructions in the first post)
- enjoy/report bugs
hi thisispatrick unfortunately without an open source driver it's impossible for me
.
regarding ethernet, have you also tried with libreelec (installed on the SD card) and saw that it doesn't work?
Can i clean install libreelec 11 on the emmc or it can run only from SD.
hi presko, yes of course, my build no longer works if you have a device with NAND storage type. but with the emmc it works like previous builds
Its most likely that wifi will start when i update to ibreelec 11. Or the firmware shoud be integrated in future update of the build.
for the RTL8821CU chip I will try to include it in the next build, which I have planned soon, but you will have to help me because I can't test it.
edit: try this build https://ilmich.libreelec.tv/libreelec-11/test/
hi LynxChaus , the legacy rockchip kernel (used by libreelec 9.2 builds) sets the resolution to 1280x720 if it doesn't read the edid. the mainline kernel instead (used by my builds) does the same thing but sets a lower and more compatible resolution.
Some users have had the same problem as you in the past, but I preferred not to change the behavior of the kernel because you can follow this guide (read carefully because some commands are exclusively for x86/x86_64 architectures)
https://wiki.libreelec.tv/configuration/edid
taking a pre-compiled edid like this
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
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 source
Some 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 image
I'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.
