From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Error: unknown bus 'pcmcia'
Date: Sat, 02 Apr 2005 08:28:17 +0000 [thread overview]
Message-ID: <1112430497.6108.42.camel@localhost.localdomain> (raw)
In-Reply-To: <ad4aa5a8050401183115d447db@mail.gmail.com>
On Fri, 2005-04-01 at 21:31 -0500, David Jaquay wrote:
> I'm getting this message ("Error: unknown bus 'pcmcia'") in my dmesg
> on boot of my new 2.6.11 kernel. I searched archives of this list,
> and saw mention of upgrading udev (I'm on 045). I was wondering:
>
> 1) I'm running Gentoo, and udev 045 is the latest stable release.
> Should I move into testing territory for this?
>
> 2) I'm getting a message below the "unknown bus" of "irq 11: nobody
> cared!" Are these related, and if so, will upgrading udev fix the
> "nobody cared" message? The end result of this seems to be that my
> pcmcia network card has stopped working, whereas it works fine under
> my 2.4 kernel.
That isn't udev related. We don't handle IRQ's. :)
There happened a lot of changes to pcmcia recently. Would be nice, if
you could try out the lastest -mm version of the kernel and see if that
shows the same behavior. If you still get the same, you may want to ask
the pcmcia maintainers for help.
Good luck,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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
prev parent reply other threads:[~2005-04-02 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 2:31 Error: unknown bus 'pcmcia' David Jaquay
2005-04-02 8:28 ` 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=1112430497.6108.42.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).