From: "stefan kratochwil" <stefankratochwil@inovel.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Running depmod after deploying some extra kernel modules
Date: Wed, 9 Mar 2016 15:48:51 +0000 [thread overview]
Message-ID: <00056508.56E053F2@mail.ino.local> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1713 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 2078 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2016-03-09 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 15:48 stefan kratochwil [this message]
2016-03-11 11:09 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00056508.56E053F2@mail.ino.local \
--to=stefankratochwil@inovel.de \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox