9 replies to this topic

[tension]

Is "kernel" item (kernel version string) not yet implemented in system info component?

Cause i do not see it in about screen (system information).

And openwebif plugin returns an IndexError to the call of kernel version string:

 

  File "/usr/lib/enigma2/python/Plugins/Extensions/OpenWebif/controllers/models/owibranding.py", line 835, in getAllInfo
IndexError: string index out of range

 

 

Perhaps the old code in about component was not ported to systeminfo?

def getKernelVersionString():
	try:
		return open("/proc/version", "r").read().split(' ', 4)[2].split('-', 2)[0]
	except:
		return _("unknown")

 

 

 

 

[40H3X]

Which receiver are we talking about?

The kernel version should be visable in the About also have a look at https://wiki.openpli...Kernel_Versions
 

[WanWizard]

Which image? Self build?

 

This can happen if, during the build of enigma-info, the kernel version detection fails. Since OE-A introduced enigma.info (and the Boxinfo class), and we had to follow for compatibility reasons, runtime detection is no longer used.

 

A quick fix:

 

Edit /usr/lib/enigma.info.

 

Find the kernel version string and enter it manually, between the quotes, and remove the last line with the checksum. Save your changes.

 

Then add a new checksum using

printf "checksum=%s\n" $(md5sum "/usr/lib/enigma.info" | awk '{print $1}') >> /usr/lib/enigma.info

 

[tension]

First..... thanks for the answers.

 

On my old vuduo2, kernel 3.13.5, yes self build images.

 

Surely an issue with the enigma.info stuff, with empty string for "kernel" variable...... and WanWizard proposed fix solved the problem.

 

I will take a look around kernel version detection.

[WanWizard]

The kernel version is retrieved from the build data, and depending on what is build how and when, it sometimes isn't available.

 

It is determined like so:

inherit linux-kernel-base
KERNEL_VERSION = "${@get_kernelversion_headers('${STAGING_KERNEL_DIR}') or oe.utils.read_file('${PKGDATA_DIR}/kernel-depmod/kernel-abiversion')}"

perhaps it should be extended with or "0.0" to have a default in case the kernel headers aren't in the staging directory of the abiversion file can't be found.

 

I haven't yet found why these files aren't there sometimes. Maybe it is a dependency thing, the order in which the packages are build. I've already added a

DEPENDS = "virtual/kernel"

to make sure it runs after the kernel is built, but that didn't fix the problem.

 

[Beeker]

From my experience this happens when you flash the image directly after a build from scratch(build dir deleted).

So I have to re-run the build before flash.

 

With DEPENDS = "virtual/kernel", enigma-info waits until do_install() kernel is ready.

It seems that's  too soon.

 

STAGING_KERNEL_DIR does exist quit early in the build.

${PKGDATA_DIR}/kernel-depmod/kernel-abiversion is created by kernel.bbclass

emit_depmod_pkgdata() {
	# Stash data for depmod
	install -d ${PKGDESTWORK}/${KERNEL_PACKAGE_NAME}-depmod/
	echo "${KERNEL_VERSION}" > ${PKGDESTWORK}/${KERNEL_PACKAGE_NAME}-depmod/${KERNEL_PACKAGE_NAME}-abiversion
	cp ${B}/System.map ${PKGDESTWORK}/${KERNEL_PACKAGE_NAME}-depmod/System.map-${KERNEL_VERSION}
}

PACKAGEFUNCS += "emit_depmod_pkgdata"

emit_depmod_pkgdata() will be executed in package.bbclass

   for f in (d.getVar('PACKAGEFUNCS') or '').split():
        bb.build.exec_func(f, d)

    oe.qa.exit_if_errors(d)

So I try this patch now.

diff --git a/meta-openpli/recipes-openpli/enigma2/enigma-info.bb b/meta-openpli/recipes-openpli/enigma2/enigma-info.bb
index d15422fa..f9eab9ef 100644
--- a/meta-openpli/recipes-openpli/enigma2/enigma-info.bb
+++ b/meta-openpli/recipes-openpli/enigma2/enigma-info.bb
@@ -3,7 +3,7 @@ SUMMARY = "enigma.info used by BoxInfo"
 PRIORITY = "required"
 MAINTAINER = "OpenPLi team"
 
-DEPENDS = "virtual/kernel"
+do_install[depends] += "virtual/kernel:do_rm_work"
 
 require conf/license/openpli-gplv2.inc
 

enigma-info waits until the kernel has been built completely then.

[WanWizard]

Good we have people with a lot more knowledge then I have looking at this! Thanks.

 

Can you create a PR on develop or commit it to kirkstone and I'll backport it?

[Beeker]

I'll do. After some fine-tuning and new build.

Edited by Beeker, 25 June 2024 - 12:15.

[Beeker]

https://github.com/O...33c5df3c24c31da

[WanWizard]

Thanks, cherry picked into develop.