Fwd: Problems with 3CRWE154G72 v1.0 in FC2/FC3

Any hints or guesses where I could begin to look?

-EE

--- Emil Eifrem <[email protected]> wrote:
> Date: Tue, 8 Feb 2005 17:05:09 -0800 (PST)
> From: Emil Eifrem <[email protected]>
> To: [email protected]
> Subject: [Prism54-users] Problems with 3CRWE154G72 v1.0 in FC2/FC3
> 
> Ok, so I've been struggling to get my 3CRWE154G72 ("3Com OfficeConnect 11g")
> working in Fedora Core 2 and 3 for quite some time. Bottom line is that I
> could
> get it to work (albeit not perfectly) in FC2, but I'm unable to get it to
> work
> in FC3. I've followed all the guidelines and howtos and tutorials and
> what-have-you that I've been able to find.
> 
> In FC2 I had frequent connection hickups, indicated by "timeout waiting for
> mgmt response" in syslog and a CPU spike while all the lights on the card
> went
> out and connection was dropped. After upgrading to FC3, I'm unable to get it
> to
> work at all. I tried to follow the instructions for Fedora on the Wiki, but I
> never did see the card in the "Hardware" tab in system-config-network --
> however, I see it in hwbrowser. When I tried inserting it and rebooting the
> machine, kudzu detected it properly and I could see it and change settings in
> system-config-network.
> 
> Now after that I observe the following behavior on ifup (parts of which is
> similar to what others have experienced... I would drop the bugzilla ids but
> the prism54 bugzilla is down atm):
> 
> Console:
> 
>    [emil@jango firmware]$ sudo /sbin/ifup eth1
>    Error for wireless request "Set Bit Rate" (8B20) : SET failed
>    on device eth1 ; Input/output error.
> 
>    Determining IP information for eth1...SIOCSIFFLAGS: Connection
>    timed out
>    SIOCSIFFLAGS: Connection timed out failed.
>    [emil@jango firmware]$
> 
> Meanwhilst in syslog:
> 
>    Jan 23 17:04:52 jango kernel: eth1: timeout waiting for mgmt response
>    Jan 23 17:04:52 jango kernel: eth1: mgt_commit_list: failure.
>    oid=ff020003 err=-110
>    [repeat 4-5 times]
>    Jan 23 17:04:56 jango kernel: eth1: interface reset failure
>    Jan 23 17:04:56 jango kernel: prism54: Your card/socket may be
>    faulty, or IRQ line too busy :(
>    Jan 23 17:04:57 jango kernel: eth1: timeout waiting for mgmt response
>    Jan 23 17:04:57 jango kernel: eth1: mgt_commit_list: failure.
>    oid=ff020003 err=-110
>    [snip]
>    Jan 23 17:05:01 jango kernel: eth1: interface reset failure
>    Jan 23 17:05:07 jango kernel: prism54: Your card/socket may be
>    faulty, or IRQ line too busy :(
>    Jan 23 17:05:08 jango dhclient: receive_packet failed on eth1:
>    Network is down
>    Jan 23 17:05:10 jango dhclient: DHCPDISCOVER on eth1 to
>    255.255.255.255 port 67 interval 8
>    Jan 23 17:05:10 jango dhclient: send_packet: Network is down
> 
>    And then it keeps going with dhcp discovery (to find nothing, of course,
> since we have no connection).
> 
> Visually on the card:
> 
>    o On "Determining IP" at the console, the lights on the card starts to
> blink.
>    o The blinking stops and the card goes dead after the second
> "SIOCSIFFLAGS: Connection timed out".
> 
> In dmesg:
> 
>    eth1: resetting device...
>    eth1: uploading firmware...
>    eth1: firmware version: 1.0.4.3
>    eth1: firmware upload complete
>    eth1: expecting oid 0xff020003, received 0x0.
>    eth1: timeout waiting for mgmt response 1000, triggering device
>    eth1: timeout waiting for mgmt response 900, triggering device
>    eth1: timeout waiting for mgmt response 800, triggering device
>    eth1: timeout waiting for mgmt response 700, triggering device
>    eth1: timeout waiting for mgmt response 600, triggering device
>    eth1: timeout waiting for mgmt response 500, triggering device
>    eth1: timeout waiting for mgmt response 400, triggering device
>    eth1: timeout waiting for mgmt response 300, triggering device
>    eth1: timeout waiting for mgmt response 200, triggering device
>    eth1: timeout waiting for mgmt response 100, triggering device
>    eth1: timeout waiting for mgmt response
>    eth1: mgt_commit_list: failure. oid=ff020003 err=-110
>    eth1: Out of memory, cannot handle oid 0x18c07814
>    eth1: timeout waiting for mgmt response 1000, triggering device
>    eth1: timeout waiting for mgmt response 900, triggering device
>    [snip]
>    eth1: timeout waiting for mgmt response
>    eth1: mgt_commit_list: failure. oid=ff02000c err=-110
>    eth1: mgt_commit: failure
>    eth1: interface reset failure
>    prism54: Your card/socket may be faulty, or IRQ line too busy :(
>    eth1: resetting device...
>    [...]
> 
> On my AP's logs:
> 
>    21 day(s) 10 hour(s) 10 min(s) 36 sec(s) after system power on :
>    Wireless MAC address 00:0D:54:9D:EE:DC has connected with the device
>    21 day(s) 10 hour(s) 10 min(s) 42 sec(s) after system power on :
>    Wireless MAC address 00:0D:54:9D:EE:DC has connected with the device
> 
>    (It's interesting to note that the AP only reports this if I have "Mode"
> set
> to "Managed". If I set it to "Auto" it won't report anything at all in its
> logs. But when I had it "semi-working" in FC2 (definitely a connection, but
> an
> unreliable one) it was with Mode set to "Auto.")
> 
> System information:
> 
>    [emil@jango ~]$ uname -a
>    Linux jango 2.6.10-1.741_FC3 #1 Thu Jan 13 16:38:22 EST 2005 i686
>    athlon i386 GNU/Linux
>    [emil@jango ~]$ sudo /sbin/cardctl ident
>    Password:
>    Socket 0:
>      product info: "3Com", "3CRSHPW15496 Wireless PC Card", "-", "-"
>      manfid: 0x01bf, 0x4301
>      function: 254 ((null))
>    [emil@jango ~]$ strings /lib/firmware/isl3890 | grep -i version
>    Version 1.0.4.3 built on Wed Jul 16 11:16:29 CEST 2003 by nlbuild@tix
> 
>    (Note that cardctl ident reports a different product string for the card
> than what's on the cover.)
> 
> I'm out of ideas. I've looked pretty much everywhere (prism54 forums,
> wiki, list archives, bugzilla, red hat's lists, fedoraforums.org, google,
> etc).
> Can anyone clue me in?
> 
> -EE



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250