Bug 209392 - ipw2200 non-functional on Thinkpad T43p
Summary: ipw2200 non-functional on Thinkpad T43p
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-05 01:21 UTC by David Miller
Modified: 2007-11-30 22:11 UTC (History)
3 users (show)

Clone Of:
Last Closed: 2006-10-13 06:38:27 UTC

Attachments (Terms of Use)

Description David Miller 2006-10-05 01:21:39 UTC
Description of problem:

Although the driver assosciates properly before the interface
is brought up, upon "ifup" the ipw2200 link goes down and
the device becomes totally non-functional.  Even rmmod'ing
the ipw2200 driver and reloading it does not bring the link
back.  Only a full reboot gets the link back, but it again
dies as soon as one tries to ifup the ipw2200 interface.

Version-Release number of selected component (if applicable):

How reproducible:

Every time.

Steps to Reproduce:
2.ifup eth1
Actual results:

ipw2200 device wedges

Expected results:

ipw2200 interface comes up properly

Additional info:

I am using the current firmware from Intel's ipw2200 sourceforge
site.  This problem has been happening ever since FC6 post-Test3
rawhide became installable on this laptop.  I do remember FC6 test1
and test2 working with the wireless interface on this system.

Comment 1 David Miller 2006-10-05 01:25:50 UTC
There was one strange message in the kernel logs when the ipw2200 device
tries to come up, from the ieee80211 stack:

eth1: NETDEV_TX_BUSY returned; driver should report queue full via

I notice that this debugging message has been removed from the current
ieee80211 stack sources in Linus's GIT tree.

Comment 2 John W. Linville 2006-10-05 12:44:50 UTC
Does it work if you change the ESSID by adding a space on the end?  So for 



   ESSID="davem "

Comment 3 David Miller 2006-10-13 06:38:27 UTC
I finally was able to get an install on my laptop using rawhide to start
playing this again, and the problem has gone away.  My wireless works

I wonder if I had a broken 3.0 firmware image.

Note You need to log in before you can comment on or make changes to this bug.