| 1 |
On Sunday 26 February 2012 10.52:58 Willie WY Wong wrote: |
| 2 |
> On Sun, Feb 26, 2012 at 11:34:01AM +0200, Penguin Lover Alan McKinnon squawked: |
| 3 |
> > On Sun, 26 Feb 2012 10:19:56 +0100 |
| 4 |
> > Dan Johansson <Dan.Johansson@×××.nu> wrote: |
| 5 |
> > > After running an update yesterday (about 50 packages) on my ~x86 |
| 6 |
> > > laptop, wicd stopped working, and no wicd was not updated neither was |
| 7 |
> > > any other network related packages. Today after a reboot my wireless |
| 8 |
> > > network refused to start from wicd, starting it manually works. This |
| 9 |
> > > is a part of the wicd.log: |
| 10 |
> > > |
| 11 |
> > I'm having similar issues with an Intel N6300 since a reboot. |
| 12 |
> > |
| 13 |
> > In my case it fails with this: |
| 14 |
> > |
| 15 |
> > [ 76.232020] wlan0: deauthenticating from |
| 16 |
> > xx:xx:xx:xx:xx:xx by local choice (reason=3) |
| 17 |
> > |
| 18 |
> > Which means something deauthed the connection in the meantime. This |
| 19 |
> > happens with kernel 3.2.6, but rebooting into 3.2.5 works just fine. |
| 20 |
> > |
| 21 |
> |
| 22 |
> You guys are almost certainly running into the same problem as the one |
| 23 |
> I mentioned in the thread I just started. |
| 24 |
> |
| 25 |
> Try `pkill dhcpcd` and associate again. |
| 26 |
> |
| 27 |
> Unfortunately I couldn't figure out why all of a sudden dhcpcd decides |
| 28 |
> to start on boot. |
| 29 |
|
| 30 |
Yes, that was it, killing the dhcpcd made it possible to bring the interface up and associate with the AP. |
| 31 |
As openrc was one of the packages upgraded yesterday (0.9.8.4 -> 0.9.9.1) I assume (guess) that is why dhcpcd gets started at boot. |
| 32 |
Now I just have to figure out a way to stop this from happening. |
| 33 |
|
| 34 |
-- |
| 35 |
Dan Johansson, <http://www.dmj.nu> |
| 36 |
*************************************************** |
| 37 |
This message is printed on 100% recycled electrons! |
| 38 |
*************************************************** |
Archives