You are not logged in.
Hello.
Yesterday, I managed to get my wireless network working.
My network card is:
~/ lspci | grep Network
03:00.0 Network controller: Broadcom Corporation BCM4321 802.11a/b/g/n (rev 03)systemd-analyze show me that some service takes about 30 seconds:
~/ systemd-analyze blame
31.543s NetworkManager-wait-online.service
850ms NetworkManager.service
166ms systemd-udev-trigger.service
153ms alsa-restore.service
151ms systemd-logind.service
147ms systemd-fsck@dev-sdb1.service
147ms var.mount
113ms systemd-tmpfiles-setup.service
113ms systemd-sysctl.service
102ms home.mount
100ms systemd-fsck@dev-sdb3.service
100ms dev-hugepages.mount
99ms systemd-random-seed-load.service
98ms systemd-vconsole-setup.service
96ms systemd-modules-load.service
92ms dev-mqueue.mount
90ms sys-kernel-debug.mount
67ms tmp.mount
65ms systemd-remount-fs.service
65ms polkit.service
50ms systemd-udevd.service
50ms udisks2.service
43ms sys-kernel-config.mount
25ms rtkit-daemon.service
24ms wpa_supplicant.service
16ms systemd-journal-flush.service
13ms systemd-user-sessions.service
12ms upower.service
11ms dev-sdb2.swapIf I disable the 30-seconds service, I still have the same problem.
And lshw -C network show:
~/ lshw -C network
*-network
description: Ethernet interface
produit: MCP65 Ethernet
fabriquant: NVIDIA Corporation
identifiant matériel: 6
information bus: pci@0000:00:06.0
nom logique: enp0s6
version: a3
numéro de série: 0a:f1:56:59:50:d4
capacité: 1Gbit/s
bits: 32 bits
horloge: 66MHz
fonctionnalités: bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=forcedeth driverversion=0.64 latency=0 link=no maxlatency=20 mingnt=1 multicast=yes port=MII
ressources: irq:20 mémoire:f2487000-f2487fff portE/S:30e0(taille=8)
*-network
description: Network controller
produit: BCM4321 802.11a/b/g/n
fabriquant: Broadcom Corporation
identifiant matériel: 0
information bus: pci@0000:03:00.0
version: 03
bits: 64 bits
horloge: 33MHz
fonctionnalités: bus_master cap_list
configuration: driver=b43-pci-bridge latency=0
ressources: irq:16 mémoire:f2000000-f2003fff mémoire:f2500000-f25fffff
*-network
description: Interface réseau sans fil
identifiant matériel: 1
nom logique: wlan0
numéro de série: 00:1a:73:e7:45:69
fonctionnalités: ethernet physical wireless
configuration: broadcast=yes driver=b43 driverversion=3.8.7-1-ARCH firmware=666.2 ip=192.168.1.119 link=yes multicast=yes wireless=IEEE 802.11bgThe only difference in the latest command before I get connected is that the last *-network got the configuration
link=noinstead of:
link=yesDo you know how I can get my wireless network to start instantly instead of waiting 30 seconds?
Thanks for your help.
Offline
I know this thread is several days old, but I figure the lack of feedback indicates this problem is still present.
You have a broadcom card, so have you gone through the broadcom wiki page and tried alternative modules/firmware? There is a reverse engineered setup called b43. The module is in the kernel I think, but the firmware can be installed from the AUR. Maybe this might work better.
Just as a sanity check, can you disable NeworkManager, then connect to the network manually? Then you should see if, when doing ti manually, any step takes a ridiculously long time, particularly getting the dhcp lease.
Also, a side note, the service you tried to disable is pulled in as a dependency of NetworkManager. So unless you disable NetworkManager, it will continue to run this service. It is simply a service that doens't actually complete until the network is fully connected, so that other services that depend on the network being connected (and don't deal well with starting while not connected) will have a service dependency to start against.
Offline
Hello, thanks for your answer.
Perhaps it was not really obvious from what I posted in my first post but I am actually using the b43 module. I also tried the other modules without any success.
And yes, I read the Broadcom wiki page.
I managed to reduce the connection time from 30 seconds to 15 seconds by using netcfg/netctl.
It is actually way better because I just have to wait a few seconds after seeing the desktop.
I will try to do the connection process manually to see what is so long.
Once again, thanks for your help.
Offline
I hope you can find something, as I can see no reason why NetworkManager would be considerably slower than netctl. Typically dhclient is about as fast as dhcpcd.
Maybe you could try connman-git from the AUR. It is controlled with connmanctl, for which there is no included man page, but looking therough the --help output I was able to figure it out just fine. There ia also connman_dmenu-git in the AUR as well as connman-ui-git.
Offline