wireless, Broadcom & jaunty

[NoOp]

On 05/01/2009 02:56 PM, Joep L. Blom wrote:
> NoOp wrote:
>> On 05/01/2009 06:11 AM, Joep L. Blom wrote:
>>> As so many on this list I finally found the courage to upgrade one of my 
>>> systems - a 64-bit AMD 3000 - to jaunty. Although rather cumbersome 
>>> (first upgrading to Intrepid which took 5 hours over a slow wireless 
>>> link in Hardy) and then using wired (as wireless didn't work) I upgraded 
>>> to jaunty. This went rather well to my surprise.
>>> However, my Broadcom BCM4306 won't work as expected.
>>> Yes, I can see many routers (including my own), however, wicd tries to 
>>> connect but can't.
>>> dmesg tells me:
>>> ____________________________________________________
>>> [   16.070566] b43-phy0: Broadcom 4306 WLAN found
>>> [   16.117038] phy0: Selected rate control algorithm 'pid'
>>> [   16.187063] Broadcom 43xx driver loaded [ Features: PLR, Firmware-ID: 
>>> FW13 ]
>>> [   16.193112] udev: renamed network interface wlan0 to eth0
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> 
>> 1. Check to ensure that your wicd was updated:
>> $ apt-cache policy wicd
>> Should return 1.5.9-2
>> 
>> 2. Open wicd and check your default preferences. They should show wlan0
>> and eth0.
>> 
>> 3. Check /etc/udev/rules.d/70-persistent-net_rules to see if the proper
>> mac address (00:c0:49:54:77:9e?) is associated with eth0 and wlan0.
>> 
>> 
>> 
> Noop, thanks.
> ad 1.	Yes that is equal
> ad 2. I think the default is correct as it says:
> 	wireless interface eth0
> 	wired interface eth1
> and in dmesg:
> 	[   16.193112] udev: renamed network interface wlan0 to eth0
> ad 3. There was a problem as the MAC-address was not the correct one. It 
> was: "00:0c:76:71:bd:44". Why that was I don't know. I have corrected it 
> to the one you correctly assumed was the right one but I assume I have 
> to restart networking? or ifup? or what else? When I opened wicd it 
> didn't work yet.

Typically it will be wlan0 and the first ethernet wired port will be
eth0. There were some issues with Ubuntu mixing the mac assignements &
even incrementing the ethx. There is a way to clear it, but I can't put
my finger on it just now (it's here in the archives). The fact that udev
is reassigning wlan0 to eth0 is a bit of a puzzle (to me) & worth
looking into further.

To restart networking:

$ sudo /etc/init.d/networking restart

You can do the same for wicd if you'd like - but I've found that wicd
isn't too happy about it afterwards. Networking will still work, but
wicd panel icon doesn't work unless you log out/in again. I suppose
there is a better way to get it (the wicd panel applet) kick started
again - but I've not bothered to find it.

You might also check:

$ iwconfig
$ ifconfig

afterwards & post the results.

> By the way, I never use /etc/init.d/<any_service parameter> but sudo 
> service <any_service parameter>. Service is a small wrapper utιlity in 
> /usr/bin. I used it always in Fedora.

You can see what commands are available via 'ls /etc/init.d/' - init.d
is quite handy.