Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #212385 > unrolled thread

Re: Buster on laptop cannot find Nokia 3 hotspot...

Started bybw <bwtnguy@yahoo.com>
First post2019-08-07 21:10 +0200
Last post2019-08-24 18:00 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.debian.user

Contents

  Re: Buster on laptop cannot find Nokia 3 hotspot... bw <bwtnguy@yahoo.com> - 2019-08-07 21:10 +0200
    Re: Buster on laptop cannot find Nokia 3 hotspot... Nimrod <nimrod@virgilio.it> - 2019-08-07 23:10 +0200
      Re: Buster on laptop cannot find Nokia 3 hotspot... nektarios <nektarios@mail.nektarioskatakis.xyz> - 2019-08-08 02:10 +0200
        Re: Buster on laptop cannot find Nokia 3 hotspot... Nimrod <nimrod@virgilio.it> - 2019-08-24 18:00 +0200

#212385 — Re: Buster on laptop cannot find Nokia 3 hotspot...

Frombw <bwtnguy@yahoo.com>
Date2019-08-07 21:10 +0200
SubjectRe: Buster on laptop cannot find Nokia 3 hotspot...
Message-ID<ysztU-3qn-11@gated-at.bofh.it>
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.

Good Luck,
bw

[toc] | [next] | [standalone]

#212388

FromNimrod <nimrod@virgilio.it>
Date2019-08-07 23:10 +0200
Message-ID<ysBm2-4B2-13@gated-at.bofh.it>
In reply to#212385

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [next] | [standalone]

#212391

Fromnektarios <nektarios@mail.nektarioskatakis.xyz>
Date2019-08-08 02:10 +0200
Message-ID<ysEad-6mV-3@gated-at.bofh.it>
In reply to#212388
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

[toc] | [prev] | [next] | [standalone]

#213187

FromNimrod <nimrod@virgilio.it>
Date2019-08-24 18:00 +0200
Message-ID<yyGCl-2Iu-7@gated-at.bofh.it>
In reply to#212391

[Multipart message — attachments visible in raw view] — view raw

On Thu, 2019-08-08 at 01:02 +0100, nektarios wrote:
> On Wed, 07 Aug 2019 23:05:13 +0200Nimrod <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
> > > > > youre  looking for is detected from the hardware.  
> > > > This is interesting, I didn't know this command. It would
> > > > ratherstrange if the hotspot is shown by the above command but
> > > > not byNetwork Manager.  
> > > 
> > > No, it would not be strange at all.  Network-manager is in it's
> > > owntime-zone, and is often rather strange and hard to
> > > figureout.  Sometimes you must be patient, it does not scan
> > > immediately.For CLI tools I prefer 'iw' to the older iwlist
> > > command, but eithermay help you.  If the device is scanning and
> > > finding other ap, thenit probably is a network-manager quirk.  It
> > > oftenmisses/adds/deletes aps from the list IME.  
> > 
> > I tried iw while Network Manager was not finding my hotspot, and
> > iwfound it instead.But suddenly NM found it too! Last time it
> > worked was several daysago. I really can't understand. I'm happy
> > it's working now, but I'mafraid it will stop working sooner or
> > later. I restarted severaltimes both laptop and hotspot, using both
> > Gnome Shell and Mate, andthe hotspot always appeared almost
> > immediately, as it was used to dobefore. I then turned on another
> > Nokia 3 hotspot (I have threeidentical smartphone, mine and those
> > of my sons). The second one isstill invisible, while other devices,
> > including my own smartphone, canconnect 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 WirelessController
> > 6.30.223.271 (r587334)[   11.084358] wl 0000:02:00.0 wls1:renamed
> > from wlan0[   16.562792] IPv6: ADDRCONF(NETDEV_UP): wls1: linkis
> > not ready[   17.614802] IPv6: ADDRCONF(NETDEV_UP): wls1: link isnot
> > ready[  161.102549] IPv6: ADDRCONF(NETDEV_CHANGE): wls1:
> > linkbecomes ready[  725.746601] IPv6: ADDRCONF(NETDEV_UP): wls1:
> > link isnot 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, andreenabled 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
> piwith failing wireless adapter (networks appearing and
> disappearing).

Sorry for the long delay, I had no connection till now.
iwlist doesn't show the Nokia 3 hotspot, while it shows any other kind
of hotspot, AP, SSID etc... round here.
> 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
> (itmaybe 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
> thelaptop as a driver/device mismatch might cause the device not work
> verywell (I ve seen it once only with usb wireless adapter).

Here is the output of lshw, limited to the wireless interface:
*-network             description: Wireless
interface                product: BCM4312 802.11b/g LP-
PHY                vendor: Broadcom Limited                physical id:
0                bus info: pci@0000:02:00.0                logical
name: wls1                version: 01                serial:
00:21:00:81:d9:85                width: 64 bits                clock:
33MHz                capabilities: pm msi pciexpress bus_master
cap_list ethernet physical wireless                configuration:
broadcast=yes driver=wl0 driverversion=6.30.223.271 (r587334) latency=0
multicast=yes wireless=IEEE 802.11                resources: irq:17
memory:d4700000-d4703fff
Best regards.
> Regards

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web