wireless, Broadcom & jaunty

[Joep L. Blom]

NoOp wrote:

> 
> Nah. I use it on this laptop (Intrepid w/Dynex PCMCIA wireless card):
> 
> $ dmesg |grep Broadcom
> [   38.556072] b43-phy0: Broadcom 4318 WLAN found
> [   38.751214] Broadcom 43xx driver loaded [ Features: PLR, Firmware-ID:
> FW13 ]
> 
> and it works without issue (I'm using it now).

Yes, that is exactly the same string I have.

> $ iwconfig
> lo        no wireless extensions.
> 
> eth0      no wireless extensions.
> 
> irda0     no wireless extensions.
> 
> wmaster0  no wireless extensions.
> 
> wlan0     IEEE 802.11bg  ESSID:"glg"
>           Mode:Managed  Frequency:2.412 GHz  Access Point:
> 00:1B:2F:E4:28:80
>           Bit Rate=1 Mb/s   Tx-Power=20 dBm
>           Retry min limit:7   RTS thr:off   Fragment thr=2352 B
>           Power Management:off
>           Link Quality=56/100  Signal level:-54 dBm  Noise level=-71 dBm
>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Here I have a difference as in my case it says:
... Access Point: Not-Associated
And I think that there the problem is shown.
When looking in dmesg it shows eth0 associated with the MAC-address of 
the wireless router but apparently it loses it shortly thereafter.
I think due to the fact it can't get an IP-address.
It's something in the kernel modules that doesn't work correctly.
The problem is that in Hardy it worked although I had to restart the 
network with ifdown eth0, followed by ifup eth0 every time the system 
awakened.
I suspect that in one of the many config scripts something is not right, 
but which one I don't know as I don't know all scripts related to 
networking.
Maybe Derek or Gary has an idea?

Joep