136 replies to this topic

[WanWizard]

I can reproduce the issue on an Edision OS Mini +. Flashes fine, boots fine, shows the OpenPLi bootlogo, crashes with a green screen, loops, no network.

 

I'll try to find the time to dive into it.

[rantanplan]

RPROVIDES:kernel-image = "kernel-image-${KERNEL_VERSION} kernel-${KERNEL_IMAGETYPE}"

please try with build add this to linux-kernel.

Something is wrong with the Vmlinux and the package and the Ubinize.

follow this commit Oe-Alliance
https://github.com/o...23357a2808f1c41
 

Edited by rantanplan, 19 May 2025 - 14:43.

[WanWizard]

What does this do, and why is this not in issue with other builds, which use exactly the same kernel?

[rantanplan]

There were error messages when switching from Kirkstone to Scarthgap.
The errors have been removed, the kernel is built and the UBI is created.
But only that eliminating an error does not mean that the kernel image is now also chosen correctly.
 

# By default, kernel.bbclass modifies package names to allow multiple kernels

# to be installed in parallel. We revert this change and rprovide the versioned

# package names instead, to allow only one kernel to be installed.

RPROVIDES:${KERNEL_PACKAGE_NAME}-base = "kernel-${KERNEL_VERSION}"

RPROVIDES:${KERNEL_PACKAGE_NAME}-image = "kernel-image-${KERNEL_VERSION}"

 

You should consider this as a whole.
This has also been done to create a real core.
It affects everything that is built via UBI if I understand that correctly.

Maybe I'm completely wrong.

https://github.com/O...7e5cef5fdac7be8
https://github.com/O...ae4ce6e8ad449ea

follow this commits in our BSP
 

Edited by rantanplan, 19 May 2025 - 15:15.

[hoolman]

OpenPLi Enigma2 crash log

 

crashdate=Thu Jan  1 01:03:23 1970

compiledate=May 15 2025

skin=Default Skin

sourcedate=2025-05-15

branch=scarthgap

rev=d3fe377

component=enigma2

 

stbmodel=formuler1

stbmodel=formuler1

kernelcmdline=libata.force=1:3.0G,2:3.0G,3:3.0G ubi.mtd=rootfs rootfstype=ubifs root=ubi0:rootfs bmem=240M@16M bmem=450M@512M console=ttyS0,115200n8

nimsockets=NIM Socket 0:

imageissue=openpli scarthgap %h

 

[eDVBDB] couldn't save lame channel db!

 

dmesg

[WanWizard]

Flash full ?

[hoolman]

Flash with openmultiboot

I have green screen on boot

Edited by hoolman, 24 May 2025 - 23:26.

[littlesat]

Clarification openmultiboot. This will guaranteed not work with totally Different builds…. Openmultiboot not.a real multiboot… it starts partly with that first image… and then you can get issues indeed.

Edited by littlesat, 25 May 2025 - 07:28.

[hoolman]

I have no problem with the other openpli images on openmultiboot, on facebook I saw other people having the same problem with this image, can anyone comfirm

[WanWizard]

OpenMultiboot always had an issue with "multibooting" a more recent image while the base image was older.

 

Chances are you have a root image that is using a more recent OE that OpenPLi release images, as they tend to be behind images of others, notably OE-A based images.

 

And this is because it is not a strict multiboot, the root image "bleeds" through into the others, causing issues with fox example glibc versions...

 

If the root/base image is newer, you run less of a risk, as libraries tend to be backwards compatible (but not always).

[hoolman]

Thanks for your clarification, I'll try to install the image as a base image

Edited by hoolman, 26 May 2025 - 01:38.

[hoolman]

I installed the Scarthgap as a base image and still have the same green screen problem

I think, It would be better to wait next updates, Thanks a lot

[rantanplan]

Where is the error-log?
Simply add your log here as a code.

[hoolman]

Crash log, please see above - #85 - posted 23 May 2025 - 23:36 - Thanks

[WanWizard]

To which I replied:

 

Flash full ?

 

I can't see any other reason why lamedb couldn't be written.

[hoolman]

To which I replied:

 

Flash full ?

 

I can't see any other reason why lamedb couldn't be written.

 

   My answer is for rantanplan (#93) who is asking for log, sorry

[WanWizard]

Yes, I know that.

 

My point was I gave a reply when you posted it, and you've ignored it.

 

You get that error either because your flash is full, or /etc/enigma2 does not exist.

[rantanplan]

I'd add
or because the existing lamdb is buggy and can't be read.
So an old faulty file was fed back into the system.

But the above log doesn't seem complete to me

 

[WanWizard]

The error is triggered by a C fopen() call for the file in write mode. Which should succeed regardless of the contents of the current file.

 

I think even in the case of a full filesystem, in which case it would crash on the first write. So my guess is /etc/enigma does not exist.

[hoolman]

Effectively,  /etc/enigma2 doesn't exist