From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Can't make udev load kernel modules
Date: Mon, 21 Nov 2005 06:15:13 +0000 [thread overview]
Message-ID: <20051121061513.GA31497@vrfy.org> (raw)
In-Reply-To: <43816321.4000408@terra.com.br>
On Mon, Nov 21, 2005 at 04:03:13AM -0200, Piter PUNK wrote:
> Hi,
>
> I am using kernel 2.6.15-rc2 and udev-075. I put one little
> modified SuSE's boot.udev as rc.udev in my distro and changes all
> udev/rules.d by the rules in SuSE's package.
>
> But i can't make the udev to loads kernel modules. I think
> it's only a boot problem, try to play uevent after boot:
>
> for i in `find /sys -name "uevent"`; do
> echo "add" > $i
> done
>
> And look with udevmonitor. Many events happens, but no module
> are loaded. I recheck the rules dir, the /lib/udev dir and if udev are
> running. After almost one hour searching for the bug i try:
>
> echo "/sbin/hotplug" > /proc/sys/kernel/hotplug
> for i in `find /sys -name "uevent"`; do
> echo "add" > $i
> done
>
> And look with udevmonitor again. Much more events happens, and
> all modules are loaded!
You probably need to tell udev to run modprobe :)
ACTION="add", ENV{MODALIAS}="?*", RUN+="/sbin/modprobe $modalias"
Kay
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc. Get Certified Today
Register for a JBoss Training Course. Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_idv28&alloc_id\x16845&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2005-11-21 6:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 6:03 Can't make udev load kernel modules Piter PUNK
2005-11-21 6:15 ` Kay Sievers [this message]
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=20051121061513.GA31497@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.