Bug 751 – Driver seems to require manual scans

Bug 751 - Driver seems to require manual scans

Summary:

Driver seems to require manual scans

Status:	VERIFIED FIXED

Product:	IPW2200
Component:	SSID scan
Version:	1.0.6
Platform:	All Gentoo

Importance:	P2 normal
Assigned To:	Zhu Yi
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-08-10 14:40 by Rich
Modified:	2005-10-25 19:29 (History)

Attachments
fix patch (896 bytes, patch) 2005-08-10 21:38, Zhu Yi	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note

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

Description From Rich 2005-08-10 14:40:22

I have a generic Intel IPW2200 miniPCI card. I upgraded to ipw2200 1.0.6, and I
had the oddest problem. I started the driver, waited for it to find my nearby
Linksys WRT54G access point, and lo, it did not, for a bit. I attempted an
iwlist scanning, and lo, the AP was detected. I thought nothing of it, at the time.

This has become the normal behavior on boot, even if I build from the sources on
this site, and not using a Gentoo ebuild.

Often, after the initial detection, the card will not detect new access points
until another manual iwlist scanning.

Is this expected behavior, or a bug?

------- Comment #1 From Yan, Yechun 2005-08-10 18:46:26 -------

Could you please start your driver with "modprobe ipw2200 debug=0x43fff" and 
repeat the steps you have experienced, then post your dmesg here?

Thanks

------- Comment #2 From Zhu Yi 2005-08-10 21:38:19 -------

Created an attachment (id=493) [details]
fix patch

------- Comment #3 From Rich 2005-08-18 00:53:15 -------

(In reply to comment #1)
> Could you please start your driver with "modprobe ipw2200 debug=0x43fff" and 
> repeat the steps you have experienced, then post your dmesg here?
> 
> Thanks

The level of dmesg output is rather excessive, though I'll post it if it is
somehow still troublesome.

The above patch resolves my difficulties nicely. Thank you.

Was there a reason for the behavior change?

------- Comment #4 From Zhu Yi 2005-09-06 06:59:13 -------

(In reply to comment #3)
> Was there a reason for the behavior change?

No, it's a bug. Fixed in our git now.

------- Comment #5 From Mi, Jun 2005-10-25 19:25:40 -------

Verify on 2200 V1.0.8, fm 2.4, kernel 2.6.13.

------- Comment #6 From Rich 2005-10-25 19:29:16 -------

Verified fixed. on 2.6.13 1.0.8 fw 2.4.