wlan0 turn on very slow (about 3 minutes)

[maxwux]

My wlan0 turn on very slow (about 3 minutes), I don't know why.
this is my dmesg
http://paste.ideaslabs.com/show/VSj78ucekb
line no.1248 to 1249 spend 200 secends.
any idea??

[oshunluvr]

Re: wlan0 turn on very slow (about 3 minutes)

These kind of errors can be very hard to trouble shoot. In the past, wifi-n would de-authenticate if ipv6 was enabled.

Try this https://help.ubuntu.com/community/We...ngSlowIPv6IPv4

EDIT:

Sorry - I didn't notice how old that article was. Here's what to do:

All in a terminal:

lsmod |grep ipv6

If this returns nothing, then ipv6 is already off. If not, edit /etc/sysctl.conf and at the end add the following line:

net.ipv6.conf.all.disable_ipv6 = 1

Reload sysctl.conf by:

sudo sysctl -p.

or rebooting.

[maxwux]

Re: wlan0 turn on very slow (about 3 minutes)

hmmmm
did't work
when I open wicd and press reload
the wlan0 will turn on
but when I boot and wait 3 minutes,
wlan0 will turn on automatically
and wicd will auto connect to ap.

[GreyGeek]

Re: wlan0 turn on very slow (about 3 minutes)

While you are waiting for your wlan0 to connect, open the System Monitor, sort by CPU%, and see what is eating most of your CPU cycles.

[maxwux]

Re: wlan0 turn on very slow (about 3 minutes)

nothing...
cpu usage about 0%~5%
I can not find any strange process

[SteveRiley]

Re: wlan0 turn on very slow (about 3 minutes)

Has it always taken your computer a full minute to boot up? That seems very slow. There's an odd AppArmor message at the end (of course, that could be normal for all I know; AppArmor is one of the first things I purge when I build a system).

I think there's more going on here than what dmesg can show us. Syslog has more detail, including the output of NetworkManager, wpasupplicant, and dhclient. Would you mind posting /var/log/syslog and /var/log/syslog.1 on Pastebin for us to examine? Thanks.

[GreyGeek]

Re: wlan0 turn on very slow (about 3 minutes)

...
AppArmor is one of the first things I purge when I build a system.
....

Ditto.

If someone owns your root you have problems AppArmor cannot solve and isn't immune to. If not, AppArmor isn't necessary. Rkhunter or chkrootkit called from a cron script with email notification of something funny is sufficient.

[SteveRiley]

Re: wlan0 turn on very slow (about 3 minutes)

Mandatory access controls have their place. Home computers are not included in this list of places. The class of attacks that MACs are designed to circumvent rarely threatens the average Internet surfer; accordingly, the typical threats we do need to worry about can easily circumvent most MACs -- because of their complexity, MACs have bugs.

Read the Wikipedia article, especially the section on implications of the term mandatory.

[maxwux]

Re: wlan0 turn on very slow (about 3 minutes)

Has it always taken your computer a full minute to boot up? That seems very slow. There's an odd AppArmor message at the end (of course, that could be normal for all I know; AppArmor is one of the first things I purge when I build a system).

I think there's more going on here than what dmesg can show us. Syslog has more detail, including the output of NetworkManager, wpasupplicant, and dhclient. Would you mind posting /var/log/syslog and /var/log/syslog.1 on Pastebin for us to examine? Thanks.

here is my log http://dl.dropbox.com/u/10859073/log.tar.gz
I just remove AppArmor
didn't work

[SteveRiley]

Re: wlan0 turn on very slow (about 3 minutes)

Your syslog is spammed with a zillion udevd errors. I really don't know what to think of that right now -- udev appears to be having trouble identifying your devices. Let's take a look at /var/log/udev.

And tell us more about your computer. It's a ThinkPad R400, I know that. Did you do a clean install of Oneiric, or an upgrade? Are you running only Kubuntu, or dual-booting with something else? What peripherals do you have connected to the various ports on your computer?

[maxwux]

Re: wlan0 turn on very slow (about 3 minutes)

I resolve this problem.
I remove wicd and install network-manager.
everything is fine....

[maxwux]

I totatlly resolve this problem.
I remove network-magager and install wicd again.
and add driver rtl8192se to /etc/modules

$ cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp
rtl8192se

then kernel will load this drive every time at boot