Hi,

I am struggling with integrating some (unfortunately proprietary) wifi kernel
modules, which are build outside the kernel sources. In fact, I only need to
call depmod after the targetinstall step. However, I'm not feeling too lucky
with my results so far.

The imho most promising way lead me to /etc/rc.once.d, so I created a little
shell script which calls depmod on the first bootup of my target, and added it
to rc.once.d. It turned out that this triggers a reboot (!) after the prelink
step was executed:

[   13.747106] systemd-journald[110]: Received SIGTERM from PID 1
(systemd-shutdow).

I played around a bit and recognized, that this reboot only occurs if my depmod
script is executed _after_ the prelink step. If I prepend a '0_' to my depmod
script name, then no reboot occurs. In both cases, modprobe finds my modules
after having the system fully booted up, so depmod was _definitely_ executed.

I have no explanation for that rebooting behaviour, and I also noticed that
none of my "echo" calls were printed out. Maybe executing depmod during the
system boot process is not the best idea, so I am looking for a more safe way
to do that.

I had no luck with google, the ptxdist mailing lists and the ptxdist git
history, so does anyone know what to do in such a situation? Is the
rc.once.d-way okay for my purpose, or is there a less blunt option? Could I
somehow call depmod at the postinst stage?


I am using:
- ptxdist 2014.11.0
- OSELAS.toolchain() 2013.12.2
- linux kernel 3.16 (with some minor modifications)
- freescale i.mx6 target


My script for executing depmod from rc.once.d:
#!/bin/sh
echo -n "running depmod..."
depmod
echo done


Many thanks in advance!


Cheers,
Stefan