Hello,

I had a bit similar issue. I'm not sure whether it's caused by the same 
bug or not. 

On Fri, 17 Mar 2006, Wouter Verhelst wrote:
> On Fri, Mar 10, 2006 at 18:53:45 +0100, Robert Jordens wrote:
> > On Fri, 2006-03-10 at 10:57 +0100, Wouter Verhelst wrote:
> > > Building zd1211-source against vanilla 2.6.15.6 works, but the resulting
> > > driver does not seem to work; it loads, it associates, but I don't get a
> > > DHCP reply that works.

Do you have "We Lose AP for 5 seconds" message in dmesg output? I had it 
after association during the DHCP exchange. If you have it, my bug is very 
likely related to this.

I tried removing deassociation caused by that 5 seconds thing but it 
didn't help.

> > > Downgrading to the version in testing, rebuilding, and reloading the
> > > driver fixes this.

I created a patch for myself which removes 2.4.0.0 driver WPA related 
stuff, and also tried the for-loop fix from 2.5.0.0. Basically its 
downgrade to r52 with 2.5.0.0 bugfix. With downgrade, it worked right 
away. I think there is serious regression in the 2.0.0.0 -> 2.4.0.0 
upgrade but I haven't tried to pinpoint the trouble, whereas for some 
people it is much better to have r59 based driver.

Both firmwares worked with downgrade, whereas neither helped with r59.

> > > (Not too sure about 'grave' severity; if you feel something else is
> > > better, please change as appropriate)
> > 
> > Works fine here on an: 2.6.15-1-amd64-k8. DHCP works.
> 
> Perhaps it's an endianness issue then? (ppc here)

Mine is K7 1GHz, so for my instance there is nothing fancy.

> > Could you try withouf fancy encryption stuff if you are using that?
> >
> > If you add an IP manually, can you ping?
> 
> I think I tried that too, and it didn't work.

For me, static IPed ping: negative with Open WEP128. I didn't try without 
encryption.


-- 
 i.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to