Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 98239 - ipw2100 incompatible with gentoo-sources-2.6.12-r4?
Summary: ipw2100 incompatible with gentoo-sources-2.6.12-r4?
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Unspecified (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Mobile Herd (OBSOLETE)
Depends on:
Reported: 2005-07-07 10:02 UTC by Frank Lomax
Modified: 2005-07-08 13:32 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

emerge --info (,2.35 KB, text/plain)
2005-07-08 07:26 UTC, Frank Lomax
dmesg output (dmesg.txt,13.37 KB, text/plain)
2005-07-08 07:27 UTC, Frank Lomax

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Lomax 2005-07-07 10:02:01 UTC
I just updated my laptop to gentoo-source-2.6.12-r4 from 2.6.11-r11 and now my
ipw2100 wireless card seems to be broken.  Whenever I update my kernel I always
have to re-emerge ipw2100 to get it to build against the new kernel.  Did that
again this time and all seems to go okay, except that after rebooting, the
kernel module gets loaded fine but I can never get a DHCP lease.  It's not a
local problem because rebooting back to 2.6.11-r11 works just fine, as before.

Reproducible: Always
Steps to Reproduce:
1.emerge --update gentoo-sources
3.emerge ipw2100
4.reboot to 2.6.12-r4

Actual Results:  
System hangs attempting to get DHCP lease, then gives up with no wireless

Expected Results:  
Same as with 2.6.11-r11, the system should get DHCP.
Comment 1 Henrik Brix Andersen 2005-07-07 10:53:42 UTC
Please provide the relevant output of `dmesg` and the output of `emerge --info`.
You also failed to tell us which version of the ipw2100 you are using...
Comment 2 Frank Lomax 2005-07-08 07:25:08 UTC
ipw2100 version 1.1.0

emerge --info and dmesg output to be attached
Comment 3 Frank Lomax 2005-07-08 07:26:53 UTC
Created attachment 62930 [details]
emerge --info
Comment 4 Frank Lomax 2005-07-08 07:27:17 UTC
Created attachment 62931 [details]
dmesg output
Comment 5 Frank Lomax 2005-07-08 07:28:46 UTC
Reopening with requested information
Comment 6 Henrik Brix Andersen 2005-07-08 07:38:38 UTC
The dmesg output doesn't show any errors - it does however show that you are
using WEP. Please see if you can reproduce the problem with WEP disabled.
Comment 7 Frank Lomax 2005-07-08 08:19:31 UTC
Disabling WEP won't work because the access point is definitely configured for
WEP.  I tried it for grins, but as expected, it refused to associate.
Comment 8 Frank Lomax 2005-07-08 08:20:35 UTC
BTW, I don't have control over the access point to disable WEP there.  I'll see
if I can dig up a test access point though.
Comment 9 Henrik Brix Andersen 2005-07-08 09:17:25 UTC
Please report back when you've tested against a non-WEP AP.
Comment 10 Henrik Brix Andersen 2005-07-08 12:38:04 UTC
Reporter, please see if ipw2100-1.1.1_pre11, which can be found in my overlay,
fixes this issue:
Comment 11 Henrik Brix Andersen 2005-07-08 13:32:23 UTC
This might be a similar race condition as the one reported upstream at

Please try the patch from the above bug report, and report if it solves your

Unfortunately, I can not reproduce it here...