From: janusz borowski <bor@fuw.edu.pl>
To: linux-hotplug@vger.kernel.org
Subject: ENV{MODALIAS}=="?*"->ONLY modprobe????,how to trap kernel events
Date: Thu, 16 Feb 2006 13:29:58 +0000 [thread overview]
Message-ID: <dt1u8p$ltl$1@sea.gmane.org> (raw)
Hi,
I have changed the original line (in z55_hotplug.rules):
ENV{MODALIAS}="?*", RUN+="/sbin/modprobe $env{MODALIAS}"
to "my line":
ENV{MODALIAS}="?*", RUN+="/usr/local/lib/udev/t52.sh"
and the t52.sh is:
#!/bin/sh
echo "********t2********">>/usr/local/lib/udev/wyn52
set>>/usr/local/lib/udev/wyn52
echo "********end t2********">>/usr/local/lib/udev/wyn52
However,
1)after booting with "my line" the wyn52 is empty (and of course
modules are not loaded)
2)after booting with "original line" modules are loaded (so the rule
ENV{MODALIAS}="?*" "detects" events)
3)when the boot process is ended "my rule" works ok (eg.: I have
information in wyn52 after plugging a usb-modem).
My question is:
WHY MY "DIAGNOSTIC TOOL" DOES NOT WORK DURING BOOT?
I have tried similar "trap":
KERNEL="?*" -> "log %k". This time my diagnostic file is not empty
after booting,
however it contains mostly information about /dev/vcs*,
usb buses and almost nothing about pci devices - I do not believe
that ALL kernel events were registered.
Why?
What kind of rule could give information about pci devices (during boot
time)?I would like to know how to log to a file ALL %k, %b considering
by udevd during boot time
(to take appropriate action for my device like d-link pci wifi card or
usb modem,... - I do not want to do this by configuring modprobe).
I am using udev 0.084-4 (not 0.085 yet), kernel 2.6.15, debian unstable.
(udev_log="info or debug" gives only messages to console, one cannot
read them, and system crash after a few minutes - I must start another
linux and change back to udev_log="err"....)
Thanks in advance
janusz
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
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
next reply other threads:[~2006-02-16 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 13:29 janusz borowski [this message]
2006-02-17 3:40 ` ENV{MODALIAS}=="?*"->ONLY modprobe????,how to trap kernel events during boot Greg KH
2006-02-17 9:12 ` ENV{MODALIAS}=="?*"->ONLY modprobe????,how to trap kernel events janusz borowski
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='dt1u8p$ltl$1@sea.gmane.org' \
--to=bor@fuw.edu.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).