Hi H3N7R1K,
Yo ilmich does Libreelec 11 work on nand 3229q board?
not yet. Currently the best version of libreelec is 10.
Hi H3N7R1K,
Yo ilmich does Libreelec 11 work on nand 3229q board?
not yet. Currently the best version of libreelec is 10.
Hi everyone,
it's been a long time since the experimental builds of Libreelec 11.
I want to tell you that the project is progressing slower than expected, but it's not abandoned.
Maybe in the next few days, I'll release an updated build.
Hi all,
new build of libreelec-10 available with:
- linux 5.10.186
- mesa 23.1.3
- fix ssv6051p connection error on some wifi AP/Router (https://github.com/armbian/build/pull/5448)
Cheers
Michele
chewitt you are right. but looking at the logs, the kernel sees the SD card correctly. so by exclusion that error might appear if the installation encountered some problem.
Hi all,
new build of libreelec-10 available with:
- linux 5.10.186
- mesa 23.0.4
- fix remote key mapping (thanks @dmladenov)
- enabled audio passthrough (thansk jaum20 for testing)
Cheers
Michele
seems correct to me, but I don't use Windows so I'm not 100% sure. But you should see two partitions with blkid, with output similar to this (it's an experimental box, partition names are not real)
tvchiptryp:~ # blkid
/dev/rknand0p1: LABEL_FATBOOT="SYSTEM" LABEL="SYSTEM" UUID="3003-4337" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="22aeff87-01"
/dev/rknand0p2: LABEL="STORAGE" UUID="7e1f7cb6-2d57-45d8-bc99-ac316c2f31f6" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="22aeff87-02"
Have you tried using a rufus alternative!?
try another sd card/reinstall libreelec.
There should be two partitions, the fact that there is only one makes me think that something went wrong with your installation.
let me know
it's very strange.. from these logs I see you have a 4gb sd card (mmc0) and internal memory (mmc2) of 8GB.
please post output of
- blkid
- content of file extlinux/extlinux.conf from first fat32 partition
In practice, when booting, libreelec tries to mount the partitions by recognizing them via an id (which you will see with the blkid output) written in the extlinux.conf file.
So another reason is that there is something wrong with this association.
hi JefersonBP2801,
please:
- start libreelec 10 and from the prompt with the error send a photo of the output of ` dmesg | grep mmc
- if you still have Android send the full version of the build that works for you
- if you can, get a CPU heatsink of at least 20x20mm because otherwise, you will have overheating problems
googling a bit I've discovered that:
- your soc is rk3228A
- your board has an mmc (which is better than nand),
- your board has an unsupported wifi chip (ssv6256p which you can confirm by analyzing your board)edit
edit: the problem you are having is related to the fact that after loading the kernel from the sd card, the kernel itself seems to disable/fault the sd controller.
This can depend on many factors (damaged sd card, particular wifi chip, etc). So having information about your operating system I can see how the hardware is configured.
HI, EmilB
your problem is not that strange. There are other cases of boxes not booting armbian or libreelec.
This depends on the android/bootloader version you have installed. In fact, bootloader from internal memory very often takes precedence, therefore old bootloaders cannot start the system correctly from the SD card.
This is why on the armbian forum it's recommended to clear the device's internal memory or to update the bootloader as you did then. But in fact, apart from some exceptional cases that I don't know about, it is difficult for a box not to boot from sd.
Regarding libreelec 11, it's not stable. Have you tried using Libreelec 10?!
In any case, I would need a log/screenshot of the problem, otherwise, it's impossible to try to help you
jaum20 I tried but it doesn't give me any problems. Can you test by creating the swap manually with something like this
jaum20 I've never tried it but theoretically you shouldn't have any problems if you use the storage partition.
Do you have some logs to show me and maybe the procedure you followed!?
EmilB please try to be more specific. Won't boot from sd card!? What kind of problem?! (black screen but leds on, no leds on, screen errors).Do you have an android operating system installed on internal memory!? If so what version?!
All my libreelec builds share the same bootloader so if it won't boot your problem is elsewhere.
Thank you
Michele
jaum20 I tried with a DVD (ac3 audio codec) and everything seems to work. The only flaw is that in the passthrough section several hdmi connectors are listed, but only one works (the other doesn't make any sound).
I still haven't figured out how to best configure the audio devices but let's say it's a marginal problem.
If you can do some testing too I would be grateful. In any case, I'll release this little update in a few days.
jaum20, try this build:
https://ilmich.libreelec.tv/test/LibreELEC-RK322x.arm-10.0-nightly-20230607-43c4ed8-rk322x.img.gz
If I understand correctly, in order for the HDMI passthrough to work, the audio track must have a certain codec (ac3 for example) in order to be sent unprocessed. At the moment I don't have files to test
Thank you
Michele
Hi jaum20
what version are you using!? Android doesn't support passthrough (and so in theory the legacy kernel that libreelec 9 is based on shouldn't either)
Hi
dmladenov I thank you because my build is better with to your contribution.
jaum20 audio passthrough is disabled because
- spdif output: I have no way to test it.
- hdmi outputs: I imported some patches taken from the allwinner port (which has more or less the same driver for hdmi output) but it doesn't work, so I disabled it, for now, to focus on something else.
Hi camelator,
to add a new board (not a new soc/architecture) after downloading the source of libreelec edit this file by adding the right information
and then launch the build specifying the new board (and if all works make an official pull request )
Of course, the dts must exist in the kernel (upstream or patched).
edit: this is the basic step, clearly things get complicated based on how a board is more or less similar to others already present
Technically KEY_XXXX are kernel 'keyboard' events.. so you have to bind remote buttons to something that kodi recognizes (for example the 'o' key if you want information about the playback).
For my remote controls I had to do this (for example with the 'o' key and the 'i' key).
But I thought the mapping you sent was tested with kodi.
No problem though, you're helping me make a better build. The only thing is that I can make you a new version maybe tomorrow, if not in the next few days (it's holidays in my country)
Cheers
Michele