From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: No Hotplug Events
Date: Thu, 06 Jan 2005 19:47:33 +0000 [thread overview]
Message-ID: <1105040853.6646.11.camel@localhost.localdomain> (raw)
In-Reply-To: <BJENLMGHDPAAAGKKPOFOCEKLCFAA.richard.simpson@wgint.com>
On Thu, 2005-01-06 at 10:58 -0700, Richard Simpson wrote:
> I am having no luck getting hotplug events to fire on a Gentoo hardened
> system with a 2.6.7 kernel. Everything is installed and configured according
> to your documentation. I have all the hotplug script debug messages enabled,
> and verbose USB messages enabled in the kernel. When I plug in a USB device,
> the USB subsystem recognizes it and puts appropriate entries in /sys, but
> the chain of events ends there. No hotplug messages, no udev messages, no
> changes made to /dev. Nothing in the log file that would indicate any
> problem. As near as I can tell, the kernel is never calling /sbin/hotplug.
>
> Are there known issues with the hotplug implementation in the 2.6.7 kernel?
> I've googled the internet for 3 days now and no one seems to have this
> problem. Hope you can shed some light.
What does:
cat /proc/sys/kernel/hotplug
print?
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
prev parent reply other threads:[~2005-01-06 19:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 17:58 No Hotplug Events Richard Simpson
2005-01-06 19:47 ` 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=1105040853.6646.11.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