HP nw8240 Dapper Flight 4: ipw2200 wireless not working

Bug #32551 reported by Tolstoy
8
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Medium
Unassigned
xorg (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I booted the Live CD for Dapper Flight 4 and, aside from some X and installer problems, things work.

Except wireless.

The machine uses the ipw2200. Everything gets detected just fine and the applet reports a 99% signal strength. However, opening a terminal and typing, say, "ping google.com" returns host not found.

I have this exact same problem on the Breezy kernel and can only solve it by downloading the 0.19 ipw2200 drivers (and associated firmware) and using that instead. 0.19 is what shipped with Hoary, which works out of the box.

FC4 also works fine.

I would try using the 0.19 drivers on the Live CD, but I'm not sure if that's possible, and I do use this machine and don't want to remove breezy. However, if I can help debug this, I'll do it!

Revision history for this message
Tolstoy (keith-irwin) wrote :

Sorry, didn't realize I was under xorg. Launchpad is confusing! How to I move this to the kernel package?

Revision history for this message
Luka Renko (lure) wrote :

Same is on my Kubuntu Flight 4 install (also on nw8240) - I have to note that ipw2200 have worked out-of-box with Flight 3 and all daily updates up to Flight 4 (when I did a clean reinstall).

I have however found workaround for my system:
you need to specify hwcrypto=0 option to ipw2200 module.

Easiest to do that is to add the following line:

options ipw2200 hwcrypto=0

to your /etc/modprobe.d/ipw2200 file (you will probably need to create this file).
Then remove module (modprobe -r ipw2200) and reload (modprobe ipw2200) or reboot the system.

Revision history for this message
Tolstoy (keith-irwin) wrote :

I went through weeks mucking about with that (and other) settings. Some people with an nw8240 have the 2200BG card (which I have), and it doesn't work with any driver older than ipw2200 0.19.

Others have the 2915ABG card which, I've heard, does work. I work at HP and have talked to people who also have the machine (it's a standard issue for this cycle), and most of them have the 2915ABG card and didn't seem to have a prob, or, rather, they just updated to the latest drivers on ipw2200.sourceforge.net and things worked.

Not so for me.

But, again, when I installed FC4 on this machine (and yum updated), the wireless worked just fine.

The latest Debian (as of a month or two ago) didn't work either.

The Hoary Live CD worked, but it's using the 0.19 driver.

Revision history for this message
Tolstoy (keith-irwin) wrote :

By the way: has this been moved to somewhere the Ubuntu developers can find it? I've no idea if they've seen it at all.

Revision history for this message
Luka Renko (lure) wrote :

Are there any plans to replace current driver version (1.0.10) with latest version (1.1.0) - there were many fixes, including the one with firmware loading (where hwcrypto=0 helps).

Revision history for this message
Tolstoy (keith-irwin) wrote :

I bought a new wireless access point, and the "stock" drivers in Breezy now "just work". In fact, I've not even configured the device yet.

My /etc/modprobe.d/ipw2200 has the following line:

   option ipw2200 led=1 hycrypto=0

For the record, the access point that wasn't working for me was:

  D-Link DWL-900AP+

I haven't tried to get any encryption working yet, but we'll see. At least I don't have to recompile drivers anymore!

Revision history for this message
Luka Renko (lure) wrote :

Initial reported has resolved the issue by changing AP.
Latest dapper kernel also includes ipw2200 1.1.1 driver with several fixes.

Changed in linux-image-2.6.15-15-386:
status: Unconfirmed → Rejected
Revision history for this message
Luka Renko (lure) wrote :

wrong package

Changed in xorg:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.