From: Todd Musall <tmusall@comcast.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: 3-11-04 hotplug error
Date: Sat, 13 Mar 2004 17:08:15 +0000 [thread overview]
Message-ID: <1079197695.10031.9.camel@parents> (raw)
In-Reply-To: <Pine.LNX.4.58.0403130809500.1581@ryanr.aptchi.homelinux.org>
All,
I'm getting similar errors using hotplug 2004-03-11 and kernel 2.6.4.
Here's a small sample: (most of these are repeated many times)
ieee1394.agent[834]: ... no drivers for IEEE1394 product 0x/0x/0x
input.agent[697]: ... no modules for INPUT product
input.agent[1489]: ... no modules for INPUT product 0011/0001/0001/ab41
pci.agent[1861]: ... no modules for PCI slot
usb.agent[1892]: ... no modules for USB product 0/0/0
scsi.agent[2370]: how to add device type= at
/devices/pci0000:00/0000:00:14.2/usb5/5-3/5-3:1.0/host0/0:0:0:0 ??
-Todd
On Sat, 2004-03-13 at 09:15, Ryan Reich wrote:
> Hi,
>
> Please CC me on response.
>
> When I boot, the hotplug script spits out quite a few annoying errors. Most of
> them appear to be "...no driver for INPUT" or something like that, which is not
> surprising on an investigation of /lib/modules/`uname -r`/modules.inputmap,
> since there's nothing there (this isn't to say I like it; clearly I have some
> device whose driver is not listed. In particular, psmouse.ko is not loaded).
> However, there are three that seem to be errors in the script. They say
> (roughly)
>
> ieee1394.agent: [ 0x{hex number}: integer expected
>
> A glance at that script shows that apparently, the hex-to-decimal conversion
> didn't work, though I'm not sure why. Strangely, when gpm starts I get another
> message (which appears to be from the module itself rather than hotplug) about
> the 1394 modules loading, this time correctly, which is odd because my mouse
> obviously isn't firewire. psmouse does not load.
--
Todd Musall <tmusall@comcast.net>
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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:[~2004-03-13 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-13 14:15 3-11-04 hotplug error Ryan Reich
2004-03-13 17:08 ` Todd Musall [this message]
2004-03-13 18:46 ` Ryan Reich
2004-03-26 23:07 ` Greg KH
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=1079197695.10031.9.camel@parents \
--to=tmusall@comcast.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).