From: Miles Lane <miles@speakeasy.org>
To: linux-hotplug@vger.kernel.org
Subject: README in the hotplug release needs updating. We should also include the pci-utils/usbutils patches
Date: Thu, 22 Feb 2001 07:38:06 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98282742531827@msgid-missing> (raw)
Hi,
On my Athlon running 2.4.1-ac20, with the pci-utils and
usbutils patches applied and the latest hotplug release
from the sourceforge site installed from RPM, I still
don't get usb-ohci auto-loaded at boot time to enable
my AMD-756 USB host-controller. I enabled debugging
in all the hotplug agent and script files.
When I run the patched pcimodules, I get:
emu10k1
3c59x
usb-ohci
Since usb-ohci appears in the list, doesn't this mean
that the driver ought to be getting loaded?
The only /sbin/hotplug related message I see in my
/var/log/messages file is:
Feb 21 23:22:13 aerie /sbin/hotplug: arguments (net) env
(PWD=/etc/hotplug HOSTNAME®rie INTERFACE=eth0 ACTION=register
DEBUG=yes MACHTYPE=i586-mandrake-linux-gnu OLDPWD=/ SHLVL=1
SHELL=/bin/bash HOSTTYPE=i586 OSTYPE=linux-gnu HOME=/ TERM=dumb
PATH=/bin:/sbin:/usr/sbin:/usr/bin _=/usr/bin/env)
Feb 21 23:22:13 aerie /sbin/hotplug: invoke /etc/hotplug/net.agent
Feb 21 23:22:13 aerie /etc/hotplug/net.agent: invoke ifup eth0
Feb 21 23:22:13 aerie network: Bringing up interface eth0: succeeded
Any clues?
Miles
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2001-02-22 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-22 7:38 Miles Lane [this message]
2001-02-26 19:14 ` README in the hotplug release needs updating. We should also David Brownell
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=marc-linux-hotplug-98282742531827@msgid-missing \
--to=miles@speakeasy.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.