From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: newbie questions on hotplug with IBM X20
Date: Wed, 12 Dec 2001 19:34:47 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-100818589431229@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-100815770223799@msgid-missing>
> 1) When a Targus PAUM003 USB mouse is plugged in,
> the following is printed /var/log/messages: ...
> Dec 12 13:38:26 mike-laptop /etc/hotplug/usb.agent: ... can't load module mousedev
>
> What needs to do next in order to use this mouse from Linux?
Did you verify that you can't use it? If "mousedev" is statically
linked into your kernel, you should be able to use it already.
I often get that message when I connect a USB mouse; it's
still usable
So far as I know, there's no standard way for the hotplug
scripts to tell when the reason a module can't be loaded
is that it's been statically linked. "lsmod" only shows the
dynamically linked modules, not the statically linked ones,
and "modprobe" fails when it can't be dynamically linked,
even if the module is already statically linked.
- Dave
_______________________________________________
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:[~2001-12-12 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-12 11:46 newbie questions on hotplug with IBM X20 Michael Greenberg
2001-12-12 15:49 ` Greg KH
2001-12-12 19:34 ` David Brownell [this message]
2001-12-12 20:03 ` Brad Hards
2001-12-12 20:24 ` 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-100818589431229@msgid-missing \
--to=david-b@pacbell.net \
--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).