CoreELEC 21.3-Omega Amlogic-ng Discussion

Right - but it turns out @vpeter was right ( not a big surprise lol ) and there seems to be an issue - my 21.3-ng coreelec installation always needs the reboot update option - i.e. the First Boot option and just starting up the box (or a regular reboot) causes bootloops. coreelec to boot but NOT initialize the display - i.e. the display stays white.

4 posts were merged into an existing topic: Learning about Dolby Vision and CoreELEC development

A post was merged into an existing topic: Learning about Dolby Vision and CoreELEC development

I went ahead and applied this patch to the amlogic-4.9-20 branch then used the resulting sha to build coreelec.

diff --git a/block/partition-generic.c b/block/partition-generic.c
index 09e61778700b..e1342eca8a89 100644
--- a/block/partition-generic.c
+++ b/block/partition-generic.c
@@ -337,6 +337,17 @@ struct hd_struct *add_partition(struct gendisk *disk, int partno,
        else
                dev_set_name(pdev, "%s%d", dname, partno);

+       /*
+        * make block special file using partition name
+        * instead of device name with partition number
+        */
+       if (!strcmp(dname, "mmcblk0") && info && info->volname[0]) {
+               pr_info("[%sp%02d] %20s  offset 0x%012llx, size 0x%012llx add\n",
+                       dname, partno, info->volname, start << 9, len << 9);
+
+               dev_set_name(pdev, "%s", info->volname);
+       }
+
        device_initialize(pdev);
        pdev->class = &block_class;
        pdev->type = &part_type;

The boot behavior didn’t change

1 Like

ce-ng is already EOL, discussing it further won’t change anything, just give up.

A post was merged into an existing topic: Help, support CPM build

Turns out, this is an issue with how the box saves boot parameters.
I removed the coreelec usb drive and set the right preferences - i.e. don’t start with dolby vision enabled and then i rebooted the homatics box.
After that I reinserted the coreelec usb drive (while in android) and just rebooted the box - and what do you know it booted correctly (without the white screen).
So, while the newer kernels in ne and no are able to initialize the output of the box at boot time even while in the DV state, configuring the box properly mitigates this!

A post was merged into an existing topic: Homatics Box R 4K Plus

Is Amlogic’s issue with real TV-Led dolby vision fixed on this release?

I think you’re a year late with that question.

1 Like

Sorry! Just found out that it was fixed in March last year, thank you!

Eheh, no problem!