Messages in this thread | | | Date | Thu, 28 Sep 2006 22:16:48 -0700 | From | Andrew Morton <> | Subject | Re: 2.6.18-mm2 -- EIP: [<c11a962e>] klist_node_init+0x2b/0x3a SS:ESP 0068:f63a5f80 |
| |
On Thu, 28 Sep 2006 22:04:00 -0700 "Miles Lane" <miles.lane@gmail.com> wrote:
> > > but either ipw2200 or > > > NetworkManager is still not working. I am running Fedora development > > > (rawhide). For some reason, NM still cannot establish a connection > > > with this kernel build (this failed with 2.6.18-mm2 previously, but I > > > thought it was related to the BUG). "iwlist scan" can corrently > > > detect my access point. Also, I can use iwconfig and dhclient to > > > establish a working connection. NM fails with this output in the > > > message log (I'll try getting a more detailed debug log out of NM): > > > > Another reporter mentioned that he could only get his wireless to associate > > with his AP by using essid "any". But that was a different type of card. > > > > ipw2200 works OK for me, fwiw. > > Shall I send you my .config?
argh. I'm afraid my head pointer keeps on wrapping past my tail pointer recently.
But what the heck, yes please. I'm sure James will appreciate it ;)
> > There's a largeish ipw2200 update in mainline now. That'd be worth testing. > > > > It looks like that ipw2200 update was in 2.6.18-mm1 though. Did that work? > > Yes, it did. My main problem with mm1 was the broken CPUFreq, which > is still busted in mm2.
Oh. Is anyone looking into that?
> I am rebuilding with debugging enabled in the > ipw2200 driver. I'll see if I can capture any useful information when > I try to associate using NM.
Testing mainline would be useful. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |