Hi

I am running Ubuntu 22.04 LTS 64 bit on a Raspberry Pi 4. The
installation has worked perfect with WiFi for 2-3 months since I
installed it.
While working on the Pi yesterday morning, I got a pop-up about a
pending update. I started the update, let in run in the backgrund
continuing my work. When finished turned the system off.
A few hours later the wifi would not connect to my local router (same
as it is always connecting to. Tried the usual fidling with no help,
so I settled for a restart. No help in the restart, but after a little
while wifi connected OK, and I could work on the machine.
Today I have had problems 2 times with the wifi. Have of course
checked all settings for this connection in Ubuntu, and all are
correct. Also tried changing a setting to the wrong one and then
change back to the correct, but still dead wifi. And the suddenly it
connects. And while it tries to connect with no luck, it says "Strong
signal", so the signal is fine. he Pi is sitting just 2 meters from
the router.
No change done on the router, and all other devices (phones, laptop,
++) is working as usual.

So have others experienced similar trouble after the updates. Any
suggestions to what I can do.

PS: I am a long time beginner in Linux, so please be patient :-)
--
Jesper Kaas - jesperk@neindanke.online.no

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 30/06/2022 19:34, Jesper Kaas wrote:

Hi

I am running Ubuntu 22.04 LTS 64 bit on a Raspberry Pi 4. The
installation has worked perfect with WiFi for 2-3 months since I
installed it.
While working on the Pi yesterday morning, I got a pop-up about a
pending update. I started the update, let in run in the backgrund
continuing my work. When finished turned the system off.
A few hours later the wifi would not connect to my local router (same
as it is always connecting to. Tried the usual fidling with no help,
so I settled for a restart. No help in the restart, but after a little
while wifi connected OK, and I could work on the machine.
Today I have had problems 2 times with the wifi. Have of course
checked all settings for this connection in Ubuntu, and all are
correct. Also tried changing a setting to the wrong one and then
change back to the correct, but still dead wifi. And the suddenly it connects. And while it tries to connect with no luck, it says "Strong signal", so the signal is fine. he Pi is sitting just 2 meters from
the router.
No change done on the router, and all other devices (phones, laptop,
++) is working as usual.

So have others experienced similar trouble after the updates. Any
suggestions to what I can do.

PS: I am a long time beginner in Linux, so please be patient :-)

No actual trouble with updates per se, but wifi on the Pi has not been a
hugely reliable experience for me at least on the Pi Zero-W.

Under rather weaker signal conditions it would sometimes not connect
drop or go very slowly.

But I had no problems when iwconfig showed the signal was strong, so my
first step would be to use iwconfig [wlan0] to probe the interface to
see what was happening and if there are any dropped packets etc


--
Canada is all right really, though not for the whole weekend.

"Saki"

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Thu, 30 Jun 2022 20:38:13 +0100, The Natural Philosopher <tnp@invalid.invalid> wrote:

But I had no problems when iwconfig showed the signal was strong, so my
first step would be to use iwconfig [wlan0] to probe the interface to
see what was happening and if there are any dropped packets etc

Thank you for presenting iwconfig. I will check its possibilities in
som manual.
But for a quick go i ran iwconfig while the wifi was "connecting" (but
didnot succeed) and got this output (moved to PC via later connected
cabled ethernet):
jyttejesper@jkrp4:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on

jyttejesper@jkrp4:~$ ^C
jyttejesper@jkrp4:~$

After the cabled net was on, also the wifi connected. A new iwconfig
run on the pi showed this:

jyttejesper@jkrp4:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on

jyttejesper@jkrp4:~$ ^C
jyttejesper@jkrp4:~$


Unplugged the cable, and the wifi still worked.

I tried "iwconfig help", "iwconfig /?", "iwconfig man", and at last
succeeded with "man iwconfig". But the output is overwhelming.
Do you have some more advice?

Best regards
-jesper
--
Jesper Kaas - jesperk@neindanke.online.no

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On Thu, 30 Jun 2022 22:29:11 +0200, Jesper Kaas
<jesperk@neitakk.online.no> wrote:

On Thu, 30 Jun 2022 20:38:13 +0100, The Natural Philosopher ><tnp@invalid.invalid> wrote:

But I had no problems when iwconfig showed the signal was strong, so my >>first step would be to use iwconfig [wlan0] to probe the interface to
see what was happening and if there are any dropped packets etc

Thank you for presenting iwconfig. I will check its possibilities in
som manual.
But for a quick go i ran iwconfig while the wifi was "connecting" (but
didnot succeed) and got this output (moved to PC via later connected
cabled ethernet):
jyttejesper@jkrp4:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on

jyttejesper@jkrp4:~$ ^C
jyttejesper@jkrp4:~$

After the cabled net was on, also the wifi connected. A new iwconfig
run on the pi showed this:

jyttejesper@jkrp4:~$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on

jyttejesper@jkrp4:~$ ^C
jyttejesper@jkrp4:~$

Unplugged the cable, and the wifi still worked.

I tried "iwconfig help", "iwconfig /?", "iwconfig man", and at last
succeeded with "man iwconfig". But the output is overwhelming.
Do you have some more advice?

Best regards
-jesper

Now I get this when running "iwconfig wlan0":
jyttejesper@jkrp4:~$ iwconfig wlan0
wlan0 IEEE 802.11 ESSID:"12Com"
Mode:Managed Frequency:2.412 GHz Access Point:
FC:E3:3C:BE:6E:E4
Bit Rate=24 Mb/s Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Link Quality=56/70 Signal level=-54 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:2 Invalid misc:0 Missed beacon:0

jyttejesper@jkrp4:~$

So it looks like wifi started working after the cable was unplugged.
--
Jesper Kaas - jesperk@neindanke.online.no

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

On 30/06/2022 20:38, The Natural Philosopher wrote:

No actual trouble with updates per se, but wifi on the Pi has not been a hugely reliable experience for me at least on the Pi Zero-W.

Under rather weaker signal conditions it would sometimes not connect
drop or go very slowly.

Try doing a:

iw wlan0 set power_save off

This improved reliability and significantly lowered latency for me under
those conditions.

Note that is command transient, and needs to be put in a udev rule to
make persistent over reboots.

---druck

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)