Intel NUC Hardware WatchDog Enabling ERROR fixdep

[rquant]

Hello,
I would like to enable watchdog services on my Intel NUC.

Start Watchdog Services

RUN modprobe i2c-i801
RUN modprobe i2c-smbus
RUN modprobe iTCO-wdt

When trying to activate I get this:

[main] Step 23/26 : RUN modprobe i2c-i801
[main] —> Running in bbb2103a4165
[main] modprobe: ERROR: …/libkmod/libkmod.c:586 kmod_search_moddep() could not open moddep file ‘/lib/modules/4.14.11-coreos/modules.dep.bin’
[main] modprobe: FATAL: Module i2c-i801 not found in directory /lib/modules/4.14.11-coreos
[main]
[main] Removing intermediate container bbb2103a4165
[main] The command ‘/bin/sh -c modprobe i2c-i801’ returned a non-zero code: 1

What can I do? Do I have to build kernel modules and how do I obtain these? On Ubuntu 16.04 LTS non-resin/balea it works. Thanks

– Error Message is below —

[shaunmulligan]

Hi @rquant, It looks like you are running your modprobes in the RUN commands, which are executed in a non-privileged container on our build servers. To properly check that the modprobe is working, you would need to run the modprobe from a script or from your CMD so that it runs on the device rather than on the cloud build server. Another way to test this is to use the webterminal into your running container and then run modprobe i2c-i801 etc from the webterminal to check that they are available.

[rquant]

Great thanks for the answer will use it in my device script not on build servers.

[rquant]

I tried to run it in my start.sh file. Can I somehow build this using:

GitHub - balena-os/kernel-module-build: Example project for building an OOT kernel module in balena

• watchdog « drivers - linux-yocto-4.12 - Linux 4.12 Embedded Kernel

• https://resin-production-img-cloudformation.s3.amazonaws.com/images/intel-nuc/2.13.6%2Brev2.dev/kernel_modules_headers.tar.gz

  Test executed on the standard image from balen.io shell main:

    root@5435ab0:/usr/src/app# modprobe i2c-i801
    root@5435ab0:/usr/src/app# modprobe i2c-smbus
    root@5435ab0:/usr/src/app# modprobe iTCO-wdt
    modprobe: FATAL: Module iTCO-wdt not found in directory/lib/modules/4.12.12-yocto-standard
  

Tried to build with the balena kernel sample:
I created a folder called iTCO-wdt and placed the iTCO-wdt.c,``iTCO_vendor.h, iTCO_vendor_support.c file inside there with the Makefile:

KERNEL_TREE_PATH?=/lib/modules/$(shell uname -r)/build
EXTRA_CFLAGS="-DDEBUG"

obj-m+=iTCO_wdt.o

all: iTCO_wdt.ko

iTCO_wdt.ko: iTCO_wdt.c
	make -C $(KERNEL_TREE_PATH) M=$(PWD) modules

clean:
	make -C $(KERNEL_TREE_PATH) M=$(PWD) clean

.PHONY: all clean

and calling

RUN ./build.sh %%RESIN_MACHINE_NAME%% ‘2.13.6+rev2.dev’ iTCO-wdt

in my dockerfile.

2018-11-21 22:35:58 (68.2 MB/s) - ‘kernel_modules_headers.tar.gz’ saved [10331481/10331481]
[main]     
[main]     make: Entering directory '/tmp/tmp.BPRxUQjNfP'
[main]       CC [M]  /usr/src/app/iTCO-wdt_intel-nuc_2.13.6+rev2.dev/iTCO_wdt.o
[main]     /bin/sh: 1: scripts/basic/fixdep: not found
[main]     
[main]     scripts/Makefile.build:308: recipe for target '/usr/src/app/iTCO-wdt_intel-nuc_2.13.6+rev2.dev/iTCO_wdt.o' failed
[main]     make[1]: *** [/usr/src/app/iTCO-wdt_intel-nuc_2.13.6+rev2.dev/iTCO_wdt.o] Error 127
[main]     
[main]     Makefile:1515: recipe for target '_module_/usr/src/app/iTCO-wdt_intel-nuc_2.13.6+rev2.dev' failed
[main]     make: Leaving directory '/tmp/tmp.BPRxUQjNfP'
[main]     make: *** [_module_/usr/src/app/iTCO-wdt_intel-nuc_2.13.6+rev2.dev] Error 2

I saw some threads similar with fixdep issues:

Missing `/scripts/basic/fixdep` file during build

Hi, checking it out, I’m able to reproduce this in general, and doesn’t look like the problem of the module. It appears to me, that fixdep is at the right place but not executable properly (right flags are setup, etc, checking with the devices team for details, this is preliminary check) There are also other issues for newer releases, I believe, that we are still hunting down as well, see https://github.com/balena-io-playground/kernel-module-build/issues/7 We are working on resolving this, an…

Unable to build kernel module, not even the example

I was trying to add wireless firmware to my application but kept getting errors. Therefore I tried the example_module as is without any modifications and I am still getting the same errors. Here is part of my Docker file. Please let me know anything else that is needed and I appreciate the assistance. FROM resin/%%RESIN_MACHINE_NAME%%-node:8 ENV DEBIAN_FRONTEND noninteractive RUN apt-get update && apt-get install -y \ curl \ wget \ build-essential \ rsync \ scrot \ xdotool \ cu…

kernel_modules_headers/scripts/basic$ file fixdep
fixdep: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=31dcb0219bb5a2f2113663344ca3543804d082ee, not stripped

[rquant]

I tried with nearly every yocto kernel version, but always get fixdep error. Does anyone know how to solve it?

[zubairlk]

Hi @rquant,

I looked at kernel module headers in detail last week and found a few bugs. I’ve merged a PR with fixes that will reach future versions of balenaOS in due course. [1]

For past versions, there are workarounds.
Please correct me if I’m wrong, you are using balenaOS v2.13.6 on an Intel NUC? each version/device requires a different workaround

For that version on that device, the tools inside the header tarball such as fixdep have the following dynamic interpreter path /lib/ld-linux-x86-64.so.2 which is the balenaOS baselib path. However, the intel-nuc-debian image uses /lib64/ld-linux-x86-64.so.2 as the baselib path. The issue manifests as fixdep file not found. We need a symlink from /lib64/ld-linux-x86-64.so.2 to /lib/ld-linux-x86-64.so.2. This lets the tools find the right library and continue working.

ln -s /lib64/ld-linux-x86-64.so.2  /lib/ld-linux-x86-64.so.2

This workaround probably should be applied inside build.sh somewhere (and probably committed too before building)

Check out the following snippet where I can’t run the tool before the symlink and can after the symlink

root@5e4a1ab8b9ad:/usr/src/app# file kernel_modules_headers/scripts/basic/fixdep
kernel_modules_headers/scripts/basic/fixdep: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=31dcb0219bb5a2f2113663344ca3543804d082ee, not stripped
root@5e4a1ab8b9ad:/usr/src/app# ./kernel_modules_headers/scripts/basic/fixdep
bash: ./kernel_modules_headers/scripts/basic/fixdep: No such file or directory
root@5e4a1ab8b9ad:/usr/src/app# ln -s /lib64/ld-linux-x86-64.so.2  /lib/ld-linux-x86-64.so.2
root@5e4a1ab8b9ad:/usr/src/app# ./kernel_modules_headers/scripts/basic/fixdep
Usage: fixdep [-e] <depfile> <target> <cmdline>
 -e  insert extra dependencies given on stdin
root@5e4a1ab8b9ad:/usr/src/app# 

Regards
ZubairLK

[1] https://github.com/balena-os/meta-balena/pull/1304

[rquant]

Thank you very much for the answer.
I will try using symlinking.
I am using balenaOS 2.26.0+rev1 with ubuntu 16.04 on Intel NUC.
Is the command the same as you mentioned?

[zubairlk]

Hi @rquant,

That version has a tool missing. objtool.

Issue: No rule to make target 'tools/objtool/objtool' when compiling kernel module on intel-nuc

Fix is in the same PR I linked earlier.

[zubairlk]

but I don’t have an easy workaround to share at the moment.

[zubairlk]

Hi @rquant,

I’ve uploaded a build of kernel-module-headers tarball with my fixes. That should let you build your module.

Have a look at the last commit in the zlk/nuc branch in the repo.

balena-os/kernel-module-build

It has the symlink workaround and references my build which has objtool as well.

This should let you proceed with your work at least.

Regards
ZubairLK