linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: PCI hotplug/udev problem
Date: Tue, 18 Jan 2005 17:12:24 +0000	[thread overview]
Message-ID: <1106068344.6373.7.camel@localhost.localdomain> (raw)
In-Reply-To: <1105692480.4134.1.camel@allblack.org>

On Tue, 2005-01-18 at 07:41 +0200, Jan Zwiegers wrote:
> After a new boot the driver is loaded, but there is no nodes. But
> hotplug got fired.
> rmmod removes the driver. modprobe add the module, hotplug gets fired,
> but no nodes are created. class tree appears as per tree.txt file that
> I have sent you.

Please set
  udev_log="yes"

in /etc/udev/udev.conf and look if something is printed to syslog while
inserting/removing the module.

If you don't find anything here, please make sure that other modules are
working this way. modprobe/rmmod loop is nice to check if udev is
working by watching the creation/removal of /dev/loop*.

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

      parent reply	other threads:[~2005-01-18 17:12 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
2005-01-17 11:38 ` Jan Zwiegers
2005-01-18 17:12 ` 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=1106068344.6373.7.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).