From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: problem with 3com 3CRWE62092B wlan card (atmel chipset)
Date: Tue, 03 May 2005 18:13:24 +0000 [thread overview]
Message-ID: <1115144004.21105.96.camel@localhost.localdomain> (raw)
In-Reply-To: <200505031347.22041.infodude@gmx.de>
On Tue, 2005-05-03 at 13:47 +0200, Alexander harsch wrote:
> Hello developers,
>
> when I plug in my 3com 3CRWE62092B wlan card, I find the logs appended
> in /var/log/messages. Sometimes, the card does not get recognized at all.
> Sometimes, I can work with it without problems. If the card does not get
> recognized during start, it can be used by simpy re-plugging it in. The logs
> say, that you might be interested in this debug messages, so this is why I
> send it to you. If you have any further questions, I will certainly answer
> them if I can.
> May 3 13:12:31 nb-harsch wait_for_sysfs[7303]: error: unknown bus, please
> report to <linux-hotplug-devel@lists.sourceforge.
> net> 'pcmcia'
That must be an ancient version of udev. You may upgrade it to get rid
of this message. But updating udev will not make your card working
better, cause it's more a driver- and not a hotplug issue.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
_______________________________________________
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-05-03 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 11:47 problem with 3com 3CRWE62092B wlan card (atmel chipset) Alexander harsch
2005-05-03 18:13 ` 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=1115144004.21105.96.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).