I’m on KDE4.1 and networkmanager is really slow to start up after logging in.
I timed it from when the splash screen disappears & the desktop shows up, and knetworkmanager takes ~3-4 minutes to shw up & connect to my wireless.
Laptop doesn’t seem to be doing much else while I’m waiting - no huge cpu usage or hdd activity, the network isn’t connected so it’s not just that the app takes a while to appear in the tray.
Is this a known problem? I can post more details re versions & hardware if anyone wants.
weighty foe wrote:
> Is this a known problem? I can post more details re versions &
> hardware if anyone wants.
It is definitely not normal. Mine connects within 20-30 seconds of
when my desktop is ready. I use KDE3, but I don’t think it should be
any different.
What does the output of dmesg show about your wireless?
Larry
dredd@jmtop:~> dmesg | grep wlan
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:ed:ba:99
wlan0: RX authentication from 00:90:d0:ed:ba:99 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:90:d0:ed:ba:99
wlan0: RX AssocResp from 00:90:d0:ed:ba:99 (capab=0x411 status=0 aid=1)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:90:d0:ed:ba:99)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
wlan0: no IPv6 routers present
dredd@jmtop:~> dmesg | grep wlan
ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: Initial auth_alg=0
wlan0: authenticate with AP 00:90:d0:ed:ba:99
wlan0: RX authentication from 00:90:d0:ed:ba:99 (alg=0 transaction=2 status=0)
wlan0: authenticated
wlan0: associate with AP 00:90:d0:ed:ba:99
wlan0: RX AssocResp from 00:90:d0:ed:ba:99 (capab=0x411 status=0 aid=1)
wlan0: associated
wlan0: switched to short barker preamble (BSSID=00:90:d0:ed:ba:99)
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
wlan0: no IPv6 routers present
dredd@jmtop:~> dmesg | grep b43
b43-phy0: Broadcom 4311 WLAN found
input: b43-phy0 as /devices/virtual/input/input8
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
Thanks, James
weighty foe wrote:
> Code:
> --------------------
> dredd@jmtop:~> dmesg | grep wlan
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
> wlan0: Initial auth_alg=0
> wlan0: authenticate with AP 00:90:d0:ed:ba:99
> wlan0: RX authentication from 00:90:d0:ed:ba:99 (alg=0 transaction=2 status=0)
> wlan0: authenticated
> wlan0: associate with AP 00:90:d0:ed:ba:99
> wlan0: RX AssocResp from 00:90:d0:ed:ba:99 (capab=0x411 status=0 aid=1)
> wlan0: associated
> wlan0: switched to short barker preamble (BSSID=00:90:d0:ed:ba:99)
> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
> wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
> wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
> wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
> wlan0: no IPv6 routers present
The only thing that shows is that you still have IPV6 enabled. That
may be slowing the connection down. Disable it with YaST.
Larry
Ah yeah, I do remember seeing something about IPV6.
I’ll try this evening when I’m at home with it.
Thanks for your help
James
Right, disabling ipv6 has helped a bit - startup is down to about a minute or just over which is OK for me.
I think I might put it down to the fact that I’m on kde4 and using kde3’s knetworkmanager, so it probbaly has to load some kde3 libraries and that’s what’s taking more time. When kde4 gets its own version I’ll see how that works out.
Thankyou for your help,
James