linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander harsch <infodude@gmx.de>
To: linux-hotplug@vger.kernel.org
Subject: problem with 3com 3CRWE62092B wlan card (atmel chipset)
Date: Tue, 03 May 2005 11:47:21 +0000	[thread overview]
Message-ID: <200505031347.22041.infodude@gmx.de> (raw)

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:30 nb-harsch cardmgr[7301]: watching 2 sockets
May  3 13:12:30 nb-harsch cs: IO port probe 0xc00-0xcff: clean.
May  3 13:12:30 nb-harsch cs: IO port probe 0xc00-0xcff: clean.
May  3 13:12:30 nb-harsch cs: IO port probe 0x800-0x8ff: clean.
May  3 13:12:30 nb-harsch cs: IO port probe 0x800-0x8ff: clean.
May  3 13:12:30 nb-harsch cs: IO port probe 0x100-0x4ff: excluding 0x158-0x15f 
0x360-0x367 0x4d0-0x4d7
May  3 13:12:30 nb-harsch cs: IO port probe 0x100-0x4ff: excluding 0x158-0x15f 
0x360-0x367 0x4d0-0x4d7
May  3 13:12:30 nb-harsch cs: IO port probe 0xa00-0xaff: clean.
May  3 13:12:30 nb-harsch cs: IO port probe 0xa00-0xaff: clean.
May  3 13:12:30 nb-harsch cardmgr[7301]: starting, version is 3.2.5
May  3 13:12:30 nb-harsch cardmgr[7301]: socket 0: 3Com 3CRWE62092B 11Mbps 
WLAN PC Card
May  3 13:12:31 nb-harsch eth1: MAC address 00:04:75:cc:6a:46
May  3 13:12:31 nb-harsch eth1: Atmel at76c50x wireless. Version 0.96 
simon@thekelleys.org.uk
May  3 13:12:31 nb-harsch eth1: 3com 3CRWE62092B index 0x01: Vcc 3.3, irq 3, 
io 0x0100-0x011f
May  3 13:12:31 nb-harsch wait_for_sysfs[7303]: error: unknown bus, please 
report to <linux-hotplug-devel@lists.sourceforge.
net> 'pcmcia'
May  3 13:12:31 nb-harsch wait_for_sysfs[7303]: either wait_for_sysfs (udev 
045) needs an update to handle the device '/devi
ces/pci0000:00/0000:00:1e.0/0000:01:0f.0/0.0' properly (unknown bus) or the 
sysfs-support of your device's driver needs to b
e fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
May  3 13:12:31 nb-harsch cardmgr[7301]: executing: './network start eth1'
May  3 13:12:31 nb-harsch cardmgr[7301]: +  * Bringing eth1 up 
(192.168.99.2)...  [ ok ]
May  3 13:12:31 nb-harsch cardmgr[7301]: unsupported card in socket 1


-------------------------------------------------------
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

             reply	other threads:[~2005-05-03 11:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03 11:47 Alexander harsch [this message]
2005-05-03 18:13 ` problem with 3com 3CRWE62092B wlan card (atmel chipset) Kay Sievers

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=200505031347.22041.infodude@gmx.de \
    --to=infodude@gmx.de \
    --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).