Re: Buster on laptop cannot find Nokia 3 hotspot...
On Wed, 07 Aug 2019 23:05:13 +0200
Nimrod <nimrod@virgilio.it> wrote:
> On Wed, 2019-08-07 at 14:45 -0400, bw wrote:
> > In-Reply-To:
> > <[🔎] c5618c98-2bad-490f-8ae5-61191e1d9e7d@email.android.com>
> > > > 2) The output of `iwlist scan` to see if the network you
> > > > re looking for is detected from the hardware.
> > > This is interesting, I didn't know this command. It would rather
> > > strange if the hotspot is shown by the above command but not by
> > > Network Manager.
> >
> > No, it would not be strange at all. Network-manager is in it's own
> > time-zone, and is often rather strange and hard to figure
> > out. Sometimes you must be patient, it does not scan immediately.
> > For CLI tools I prefer 'iw' to the older iwlist command, but either
> > may help you. If the device is scanning and finding other ap, then
> > it probably is a network-manager quirk. It often
> > misses/adds/deletes aps from the list IME.
>
> I tried iw while Network Manager was not finding my hotspot, and iw
> found it instead.
> But suddenly NM found it too! Last time it worked was several days
> ago. I really can't understand. I'm happy it's working now, but I'm
> afraid it will stop working sooner or later. I restarted several
> times both laptop and hotspot, using both Gnome Shell and Mate, and
> the hotspot always appeared almost immediately, as it was used to do
> before. I then turned on another Nokia 3 hotspot (I have three
> identical smartphone, mine and those of my sons). The second one is
> still invisible, while other devices, including my own smartphone, can
> connect to it with no problems.
> Issuing iw scan now has no effect.
> For everyone who answered here is the output of dmesg | grep wl:
> [ 10.811861] wlan0: Broadcom BCM4315 802.11 Hybrid Wireless
> Controller 6.30.223.271 (r587334)[ 11.084358] wl 0000:02:00.0 wls1:
> renamed from wlan0[ 16.562792] IPv6: ADDRCONF(NETDEV_UP): wls1: link
> is not ready[ 17.614802] IPv6: ADDRCONF(NETDEV_UP): wls1: link is
> not ready[ 161.102549] IPv6: ADDRCONF(NETDEV_CHANGE): wls1: link
> becomes ready[ 725.746601] IPv6: ADDRCONF(NETDEV_UP): wls1: link is
> not ready[ 725.770340] ERROR @wl_cfg80211_scan : [ 729.858749] IPv6:
> ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready[ 1264.074169] IPv6:
> ADDRCONF(NETDEV_UP): wls1: link is not ready[ 1537.300735] IPv6:
> ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready[ 1540.111204] IPv6:
> ADDRCONF(NETDEV_UP): wls1: link is not ready[ 1655.286877] IPv6:
> ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready[ 1821.082896] IPv6:
> ADDRCONF(NETDEV_UP): wls1: link is not ready[ 1845.425123] IPv6:
> ADDRCONF(NETDEV_CHANGE): wls1: link becomes ready[ 1849.392169] IPv6:
> ADDRCONF(NETDEV_UP): wls1: link is not ready[ 1909.187372] IPv6:
> ADDRCONF(NETDEV_UP): wls1: link is not ready[ 1909.219378] ERROR
> @wl_cfg80211_scan : [ 1909.248580] ERROR @wl_cfg80211_scan :
> After the link became ready, I disabled wifi intentionally, and
> reenabled after some seconds. Also, I tried many time "iw scan".
> I can provide other data if you need it, just tell me.
> Many thanks.
> > Good Luck,bw
>
>
`iwlist` command was very useful to me once debugging a raspberi pi
with failing wireless adapter (networks appearing and disappearing).
Tbh the errors there don't look good but not serious either.
If the related output from `iwlist scan` shows only 2.4 Ghz networks (it
maybe detecting only networks in the 2.4 GHz - if your nic is old).
`lshw` output might be of use if you know what hardware you have in the
laptop as a driver/device mismatch might cause the device not work very
well (I ve seen it once only with usb wireless adapter).
Regards
--
Nektarios Katakis
Reply to: