Arch Linux

meggark

Member

Registered: 2009-05-28

Posts: 5

Removed

Removed

Last edited by meggark (2017-04-25 16:32:47)

panuh

Member

From: X :ɯoɹℲ

Registered: 2009-11-24

Posts: 144

Re: Removed

I seem to have the exact same behaviour as you do except I'm using an iwl3945 device.

My rc.conf is set up quite similar but I am declaring wlan0 beforethe INTERFACES string in which it is disabled though.

In addition I have recognized, that after the first attempt to connect (both if it was automatically or manually) the ESSID of the router will be applied for the router already but it will not be associated. After 'ifconfig wlan0 down/up' it will beassociated immediately though.

I think lsmod looks about the same before and after doing this.

Dmesg looks like this. I think after ifconfig down/up is when the led devices are registered (and, of course, association takes place)

EDIT: my bad: after ifconfig down/up the led devices will only be registered again. Already happens before. Only association takes place
         oh, and I've had that for a while now. so for me it's not a real upgrade problem. maybe somewhen back in pre-2.6.32...

Last edited by panuh (2010-02-03 12:11:56)

gladstone

Member

Registered: 2009-01-03

Posts: 74

Re: Removed

I think I'm experiencing the same.

I have netcfg to auto-connect on boot in /etc/rc.conf but it's sporadically failing. When it does, manually connecting gives me this error log, after rebooting it's fine.