> > > driver bug in bcm43xx_phy_setupg() (line 333 bcm43xx_phy.c) but the code
> > > seems to carry on successfully in that case. Do you see something like
> > > that as well?
> >
> > Yes, same thing here.
>
> That's bogus. the code there is correct afaict.
I still see the message. After adding wireless options to my kernel config
I now have the wireless tools working (my bad, sorry). I can set essid and
so forth, but no AP shows up.
> > So to sum up, I can load bcm43xx, it identifies eth1 as a wireless
> > device, I can assign it my essid/channel and a static ip-address, but
> > can't reach my router anymore (no ping, http, ssh, telnet, etc... I
> > always get a 'no route to host').
>
> Hmm. I'll look into it. Are you associated (see dmesg)?
Nope. There's a few other FIXMEs that show up; I'll send a log soonish.
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
