> When I boot the system and log in, connman does not immediately scan the
> wifi network looking for access points. Instead, it waits some minutes.
>
> To workaround the problem, I've downloaded the source using "apt-get
> source connman" and launched the script test/start-scanning, just after
> the log in. The access points are found after just a few seconds.
Btw, if you use indicator-network you can just run 'cmcc scan' to
trigger a scan.
> NonfreeKernelModules: wl
This is a bug in the wl driver you are using, the first scan always
fails. As the driver is proprietary we can't fix it. But there's a
workaround for wpasupplicant, see bug #638303 for more.
Andrea Corbellini <email address hidden> writes:
> When I boot the system and log in, connman does not immediately scan the scanning, just after
> wifi network looking for access points. Instead, it waits some minutes.
>
> To workaround the problem, I've downloaded the source using "apt-get
> source connman" and launched the script test/start-
> the log in. The access points are found after just a few seconds.
Btw, if you use indicator-network you can just run 'cmcc scan' to
trigger a scan.
> NonfreeKernelMo dules: wl
This is a bug in the wl driver you are using, the first scan always
fails. As the driver is proprietary we can't fix it. But there's a
workaround for wpasupplicant, see bug #638303 for more.
--
Kalle Valo