From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI hotplug/udev problem
Date: Mon, 17 Jan 2005 10:40:44 +0000 [thread overview]
Message-ID: <1105958444.6336.52.camel@localhost.localdomain> (raw)
In-Reply-To: <1105692480.4134.1.camel@allblack.org>
On Mon, 2005-01-17 at 11:31 +0200, Jan Zwiegers wrote:
> Hi Kay
>
> Just a quick question, maybe you know the answer off-hand.
> If I reboot my machine and then load my driver the device nodes are
> not created.
> However the /sys/class/edredaq directory appear correctly.
>
> If I then run udevstart the nodes gets created.
> Do you maybe have any ideas?
Please place the following executable script as:
/etc/hotplug.d/default/00-log.hotplug
========
#!/bin/sh
echo -e "--------$SEQNUM--------\n"\
`date +%s` $ACTION $DEVPATH"\n"\
`env`\
"\n--------$SEQNUM--------\n" >> /dev/.hotplug_d.log
========
remove and load your module and look at/post the logfile.
How does:
tree /sys/class/edredaq
look like?
Kay
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
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 prev parent reply other threads:[~2005-01-17 10:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 8:48 PCI hotplug/udev problem Jan Zwiegers
2005-01-14 9:00 ` Kay Sievers
2005-01-14 9:17 ` Kay Sievers
2005-01-17 10:40 ` Kay Sievers [this message]
2005-01-17 11:38 ` Jan Zwiegers
2005-01-18 17:12 ` Kay Sievers
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=1105958444.6336.52.camel@localhost.localdomain \
--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 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).