From: Wojciech Zabolotny <wzab01@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] SOLVED! Re: Buildroot 2011.11 on x86_64 - neither udev nor mdev loads needed modules at startup
Date: Tue, 27 Dec 2011 00:59:35 +0100 [thread overview]
Message-ID: <4EF90A67.7030202@gmail.com> (raw)
In-Reply-To: <4EF8FABB.9060104@gmail.com>
I've tested yet another configuration. With modprobe provided by busybox and without external module-init-tools.
In this setup the modprobe is located correctly in /sbin, so the only modification needed to assure automatic loading of modules is addition of "udevadm trigger --action=add" to the
/etc/init.d/S10udev file right after the $UDEV_BIN -d || (echo "FAIL" && exit 1) line.
It could be interesting to check if the automatic loading of modules with mdev may be achieved using the recipe described in: https://bugs.busybox.net/show_bug.cgi?id=2377
i.e. by writing the script:
#!/bin/sh
[ "$ACTION" = add ]&& [ "$MODALIAS" != "" ]&& modprobe $MODALIAS
[ "$ACTION" = remove ]&& [ "$MODALIAS" != "" ]&& modprobe -r $MODALIAS
/sbin/mdev $@
and passing it's path to the /sys/kernel/uevent_helper
(or simply to the CONFIG_UEVENT_HELPER_PATH in the kernel configuration).
If someone verifies it, please let me know. I think, I'll stay with my udev based setup ;-).
--
Regards,
Wojtek
next prev parent reply other threads:[~2011-12-26 23:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 0:10 [Buildroot] Buildroot 2011.11 on x86_64 - neither udev nor mdev loads needed modules at startup Wojciech Zabolotny
2011-12-26 13:42 ` Wojciech Zabolotny
2011-12-26 15:45 ` Wojciech Zabolotny
2011-12-26 15:50 ` Diego Iastrubni
2011-12-26 17:53 ` [Buildroot] SOLVED! " Wojciech Zabolotny
2011-12-26 22:52 ` Wojciech Zabolotny
2011-12-26 23:57 ` wzab
2011-12-26 23:59 ` Wojciech Zabolotny [this message]
2011-12-27 11:56 ` Diego Iastrubni
2011-12-27 12:09 ` Wojciech Zabolotny
2012-01-12 22:47 ` [Buildroot] strace doesn't compile on x86_64 Arnout Vandecappelle
2012-01-14 19:02 ` vbr vbr
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=4EF90A67.7030202@gmail.com \
--to=wzab01@gmail.com \
--cc=buildroot@busybox.net \
/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