• Spontaneous locale change on Bookworm

    From bp@bp@www.zefox.net to comp.sys.raspberry-pi on Saturday, September 21, 2024 15:53:58
    From Newsgroup: comp.sys.raspberry-pi

    This morning, after a few minutes' use of my Pi5 running Bookworm,
    the WiFi connection abruptly dropped. Couldn't bring it back up,
    so I rebooted the access point. No luck. Then I rebooted the Pi5
    and noticed something about rfkill stopping wifi in the boot messages.
    At this point the last reboot was several days past, wifi hadn't been
    touched or given any trouble.

    Went to raspi-config and rebuilt all of the locales, still couldn't
    connect. Finally I opened the system preferences and set locales,
    which were already correct according to the selections shown.

    The machine then proceeded to work normally, as I write this.
    I've had trouble before with rfkill turning on out of the blue,
    but hadn't seen the problem for a month or two and thought it
    resolved.

    Is this a widespread problem, and is there a fix? The fact that
    it happened days after the most recent reboot seems very strange.

    Thanks for reading,

    bob prohaska

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From bp@bp@www.zefox.net to comp.sys.raspberry-pi on Saturday, September 21, 2024 17:04:06
    From Newsgroup: comp.sys.raspberry-pi

    bp@www.zefox.net wrote:
    This morning, after a few minutes' use of my Pi5 running Bookworm,
    the WiFi connection abruptly dropped. Couldn't bring it back up,
    so I rebooted the access point. No luck. Then I rebooted the Pi5
    and noticed something about rfkill stopping wifi in the boot messages.
    At this point the last reboot was several days past, wifi hadn't been
    touched or given any trouble.


    The disconnect repeated after about an hour. No further references
    to rfkill, but the boot messages grumble about NetworkManager....

    bob@raspberrypi:~$ systemctl status NetworkManager-wait-online.service
    × NetworkManager-wait-online.service - Network Manager Wait Online
    Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service; en>
    Active: failed (Result: exit-code) since Sat 2024-09-21 09:52:43 PDT; 7min>
    Docs: man:nm-online(1)
    Process: 866 ExecStart=/usr/bin/nm-online -s -q (code=exited, status=1/FAIL>
    Main PID: 866 (code=exited, status=1/FAILURE)
    CPU: 33ms

    It unclear to me if this is even relevant to the disconnect event, since
    at the moment wifi is connected and working.

    Anybody got a suggestion? apt update reports all up to date....

    Thanks for reading

    bob prohaska

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Saturday, September 21, 2024 19:31:53
    From Newsgroup: comp.sys.raspberry-pi

    On 21/09/2024 18:04, bp@www.zefox.net wrote:
    bp@www.zefox.net wrote:
    This morning, after a few minutes' use of my Pi5 running Bookworm,
    the WiFi connection abruptly dropped. Couldn't bring it back up,
    so I rebooted the access point. No luck. Then I rebooted the Pi5
    and noticed something about rfkill stopping wifi in the boot messages.
    At this point the last reboot was several days past, wifi hadn't been
    touched or given any trouble.


    The disconnect repeated after about an hour. No further references
    to rfkill, but the boot messages grumble about NetworkManager....

    bob@raspberrypi:~$ systemctl status NetworkManager-wait-online.service
    × NetworkManager-wait-online.service - Network Manager Wait Online
    Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service; en>
    Active: failed (Result: exit-code) since Sat 2024-09-21 09:52:43 PDT; 7min>
    Docs: man:nm-online(1)
    Process: 866 ExecStart=/usr/bin/nm-online -s -q (code=exited, status=1/FAIL>
    Main PID: 866 (code=exited, status=1/FAILURE)
    CPU: 33ms

    It unclear to me if this is even relevant to the disconnect event, since
    at the moment wifi is connected and working.

    Anybody got a suggestion? apt update reports all up to date....

    Thanks for reading

    bob prohaska


    Well it may be completely irrelevant Bob, but my Pi Zero 2 W issues seem
    to have been solved by use of a bigger power supply.
    It may be that the wifi chip is the most sensitive to inadequate voltages.
    --
    Those who want slavery should have the grace to name it by its proper
    name. They must face the full meaning of that which they are advocating
    or condoning; the full, exact, specific meaning of collectivism, of its logical implications, of the principles upon which it is based, and of
    the ultimate consequences to which these principles will lead. They must
    face it, then decide whether this is what they want or not.

    Ayn Rand.

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From bp@bp@www.zefox.net to comp.sys.raspberry-pi on Saturday, September 21, 2024 23:53:21
    From Newsgroup: comp.sys.raspberry-pi

    [subject updated to reflect recent observations]

    The Natural Philosopher <tnp@invalid.invalid> wrote:

    Well it may be completely irrelevant Bob, but my Pi Zero 2 W issues seem
    to have been solved by use of a bigger power supply.
    It may be that the wifi chip is the most sensitive to inadequate voltages.

    The wifi dropout has repeated three or four times since the initial case. Usually it dropped after an hour or so of uptime and couldn't reconnect
    on its own, the Pi had to be rebooted. Haven't seen anything more about
    rfkill after the first incident.

    I put a voltmeter on the GPIO power pins, it looks steady at 5.09-5.10 volts. The meter isn't what I'd call a precision unit, but it's likely within 50 mV, so the voltage isn't obviously wrong.

    Just a few minutes ago the WiFi dropped, then came back up on its own a
    couple or three minutes later. Wasn't watching the voltmeter, unfortunately. I'll keep an eye peeled more carefully, perhaps it can be caught in the act.

    Thanks for writing,

    bob prohaska


    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Saturday, September 21, 2024 23:59:39
    From Newsgroup: comp.sys.raspberry-pi

    On Sat, 21 Sep 2024 17:04:06 -0000 (UTC), bp wrote:

    ... the boot messages grumble about NetworkManager....

    bob@raspberrypi:~$ systemctl status NetworkManager-wait-online.service × NetworkManager-wait-online.service - Network Manager Wait Online
    Loaded: loaded
    (/lib/systemd/system/NetworkManager-wait-online.service; en>
    Active: failed (Result: exit-code) since Sat 2024-09-21 09:52:43
    PDT; 7min>
    Docs: man:nm-online(1)
    Process: 866 ExecStart=/usr/bin/nm-online -s -q (code=exited,
    status=1/FAIL>
    Main PID: 866 (code=exited, status=1/FAILURE)
    CPU: 33ms

    I would look for more detailed error messages from NetWorkManager with journalctl. It’s having trouble with something, you need to find out what. --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From David Taylor@david-taylor@blueyonder.co.uk.invalid to comp.sys.raspberry-pi on Sunday, September 22, 2024 06:54:58
    From Newsgroup: comp.sys.raspberry-pi

    On 21/09/2024 19:31, The Natural Philosopher wrote:
    Well it may be completely irrelevant Bob, but my Pi Zero 2 W issues seem
    to have been solved by use of a bigger power supply.
    It may be that the wifi chip is the most sensitive to inadequate voltages.

    It certainly is voltage sensitive on the RPi Pico W, although there I'm comparing 5V power with 3.7V.

    David
    --
    Cheers,
    David
    Web: https://www.satsignal.eu
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Sunday, September 22, 2024 09:48:15
    From Newsgroup: comp.sys.raspberry-pi

    On 22/09/2024 00:53, bp@www.zefox.net wrote:
    [subject updated to reflect recent observations]

    The Natural Philosopher <tnp@invalid.invalid> wrote:

    Well it may be completely irrelevant Bob, but my Pi Zero 2 W issues seem
    to have been solved by use of a bigger power supply.
    It may be that the wifi chip is the most sensitive to inadequate voltages.

    The wifi dropout has repeated three or four times since the initial case. Usually it dropped after an hour or so of uptime and couldn't reconnect
    on its own, the Pi had to be rebooted. Haven't seen anything more about rfkill after the first incident.

    I put a voltmeter on the GPIO power pins, it looks steady at 5.09-5.10 volts. The meter isn't what I'd call a precision unit, but it's likely within 50 mV, so the voltage isn't obviously wrong.


    Mmm. if you have a scope, also check for noise.

    Just a few minutes ago the WiFi dropped, then came back up on its own a couple or three minutes later. Wasn't watching the voltmeter, unfortunately. I'll keep an eye peeled more carefully, perhaps it can be caught in the act.

    That is the sort of behaviour an 'on the edge' wifi subsystem displays.

    My router has 'connection time' and 'reconnection time' set to 1 hour
    and 1 day.

    I think that after the reconnection time is up, it wants a re-send of
    the secret keys.

    That is, you will, by design, get disconnected every so often,. The
    issue is whether the reconnect succeeds.

    Low voltage and/or local noise seem to be issues for the wifi chips in use.



    Thanks for writing,

    bob prohaska


    --
    Any fool can believe in principles - and most of them do!



    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From bp@bp@www.zefox.net to comp.sys.raspberry-pi on Sunday, September 22, 2024 17:12:08
    From Newsgroup: comp.sys.raspberry-pi

    The Natural Philosopher <tnp@invalid.invalid> wrote:
    On 22/09/2024 00:53, bp@www.zefox.net wrote:
    [subject updated to reflect recent observations]

    The Natural Philosopher <tnp@invalid.invalid> wrote:

    Well it may be completely irrelevant Bob, but my Pi Zero 2 W issues seem >>> to have been solved by use of a bigger power supply.
    It may be that the wifi chip is the most sensitive to inadequate voltages. >>
    The wifi dropout has repeated three or four times since the initial case.
    Usually it dropped after an hour or so of uptime and couldn't reconnect
    on its own, the Pi had to be rebooted. Haven't seen anything more about
    rfkill after the first incident.

    I put a voltmeter on the GPIO power pins, it looks steady at 5.09-5.10 volts.
    The meter isn't what I'd call a precision unit, but it's likely within 50 mV,
    so the voltage isn't obviously wrong.


    Mmm. if you have a scope, also check for noise.


    I do have a 'scope, but learned something new in the meantime.

    Overnight the connection dropped and would not reconnect. Watching
    wavemon showed cyclic behavior, trying 5 GHz, then 2.4 GHz, then
    giving up over several attempts. Opening the "edit connection"
    settings showed device to be blank. When I set it to wlan0 and
    hit "save" the connection immediately came up.

    Wlan0 is the only possibility on this Pi: there's no cable conneted,
    so how the device setting could matter, if in fact it did, is unclear.

    There are quite a few competing access points in the neighborhood,
    but mine is still the closest and, usually, the strongest. However,
    it's limited to 2.4 GHz only. Wavemon shows considerable time spent
    trying to establish a 5 GHz connecting before falling back to 2.4.

    Perhaps this is some kind of negotiating failure. I'm using a preset
    ssid with password, so there's no question of which AP to negotiate
    with. I haven't set DHCP to use a reserved MAC address simply because
    the Pi generally gets the same address anyway and I seldom run any
    services on this Pi that require access from the LAN.

    Is there some way to force the Pi to not bother attempting a 5 GHz
    connection?

    Thanks for reading,

    bob prohaska




    Just a few minutes ago the WiFi dropped, then came back up on its own a
    couple or three minutes later. Wasn't watching the voltmeter, unfortunately. >> I'll keep an eye peeled more carefully, perhaps it can be caught in the act. >>
    That is the sort of behaviour an 'on the edge' wifi subsystem displays.

    My router has 'connection time' and 'reconnection time' set to 1 hour
    and 1 day.

    I think that after the reconnection time is up, it wants a re-send of
    the secret keys.

    That is, you will, by design, get disconnected every so often,. The
    issue is whether the reconnect succeeds.

    Low voltage and/or local noise seem to be issues for the wifi chips in use.



    Thanks for writing,

    bob prohaska



    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From bp@bp@www.zefox.net to comp.sys.raspberry-pi on Sunday, September 22, 2024 17:27:40
    From Newsgroup: comp.sys.raspberry-pi

    Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
    On Sat, 21 Sep 2024 17:04:06 -0000 (UTC), bp wrote:

    ... the boot messages grumble about NetworkManager....

    bob@raspberrypi:~$ systemctl status NetworkManager-wait-online.service ×
    NetworkManager-wait-online.service - Network Manager Wait Online
    Loaded: loaded
    (/lib/systemd/system/NetworkManager-wait-online.service; en>
    Active: failed (Result: exit-code) since Sat 2024-09-21 09:52:43
    PDT; 7min>
    Docs: man:nm-online(1)
    Process: 866 ExecStart=/usr/bin/nm-online -s -q (code=exited,
    status=1/FAIL>
    Main PID: 866 (code=exited, status=1/FAILURE)
    CPU: 33ms

    I would look for more detailed error messages from NetWorkManager with journalctl. It’s having trouble with something, you need to find out what.

    If I'm reading the man page correctly, the "failure" in NetworkManager
    is very likely that the network isn't coming up.

    It must be admitted that systemctl's man page is somewhat opaque 8-)

    Thanks for writing!

    bob prohaska

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Sunday, September 22, 2024 20:47:05
    From Newsgroup: comp.sys.raspberry-pi

    On Sun, 22 Sep 2024 17:27:40 -0000 (UTC), bp wrote:

    If I'm reading the man page correctly, the "failure" in NetworkManager
    is very likely that the network isn't coming up.

    Don’t guess. Check.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From druck@news@druck.org.uk to comp.sys.raspberry-pi on Monday, September 23, 2024 12:06:44
    From Newsgroup: comp.sys.raspberry-pi

    On 22/09/2024 18:12, bp@www.zefox.net wrote:
    Is there some way to force the Pi to not bother attempting a 5 GHz connection?

    Not that I know of. I use different SSIDs for my 2.4 and 5 GHz WiFi, to
    be able to select the one I want for each device.

    Where 5 GHz is marginal I also include the 2.4 GHz SSID in the wpa_supplicant.conf with a lower priority, so it will fail over to that.

    ---druck
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From bp@bp@www.zefox.net to comp.sys.raspberry-pi on Monday, September 23, 2024 16:38:25
    From Newsgroup: comp.sys.raspberry-pi

    Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
    On Sun, 22 Sep 2024 17:27:40 -0000 (UTC), bp wrote:

    If I'm reading the man page correctly, the "failure" in NetworkManager
    is very likely that the network isn't coming up.

    Don’t guess. Check.

    Just rebooted, with the network device in Network Connections >
    preconfigured > Device set to wlan0. Networking came up immediately, bob@raspberrypi:~$ systemctl status NetworkManager-wait-online.service
    ● NetworkManager-wait-online.service - Network Manager Wait Online
    Loaded: loaded (/lib/systemd/system/NetworkManager-wait-online.service; enabled; preset: enabled)
    Active: active (exited) since Mon 2024-09-23 09:12:57 PDT; 7min ago
    Docs: man:nm-online(1)
    Process: 858 ExecStart=/usr/bin/nm-online -s -q (code=exited, status=0/SUCCESS)
    Main PID: 858 (code=exited, status=0/SUCCESS)
    CPU: 27ms

    Sep 23 09:12:49 raspberrypi systemd[1]: Starting NetworkManager-wait-online.service - Network Manager Wait Online...
    Sep 23 09:12:57 raspberrypi systemd[1]: Finished NetworkManager-wait-online.service - Network Manager Wait Online.
    bob@raspberrypi:~$

    It's very hard to understand how explicitly setting wlan0 as the active interface could matter when that's the only interface with connectivity.
    But, for the moment, the visible problem is gone.

    It should be said that I've had intermittent problems with WiFi for some
    time now. For a while it seemed to be interference-like, varying seemingly
    by time of day. After an update to Bookworm a couple weeks ago reported
    signal strength went up, (~80% to ~90%) but that didn't prevent disconnect problems. Now the disconnect issue seems to have abated.

    Why is still unclear.

    Thanks for writing!

    bob prohaska


    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Monday, September 23, 2024 22:41:46
    From Newsgroup: comp.sys.raspberry-pi

    On Mon, 23 Sep 2024 16:38:25 -0000 (UTC), bp wrote:

    Why is still unclear.

    You didn’t check the logs with journalctl, as I suggested?
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From bp@bp@www.zefox.net to comp.sys.raspberry-pi on Tuesday, September 24, 2024 00:37:59
    From Newsgroup: comp.sys.raspberry-pi

    Lawrence D'Oliveiro <ldo@nz.invalid> wrote:
    On Mon, 23 Sep 2024 16:38:25 -0000 (UTC), bp wrote:

    Why is still unclear.

    You didn’t check the logs with journalctl, as I suggested?

    I don't know what to look for.

    The problem seemed solved by explicitly requiring wlan0
    in Network > Advanced Options > preconfigured > Device.

    At your prompting I did run
    journalctl | grep -i wlan0 | grep -i failed
    which yielded a repeating pattern of messages ending with:

    Sep 22 09:30:54 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=1 duration=10 reason=CONN_FAILED
    Sep 22 09:31:11 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=2 duration=20 reason=CONN_FAILED
    Sep 22 09:31:27 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=1 duration=10 reason=CONN_FAILED
    Sep 22 09:31:44 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=2 duration=20 reason=CONN_FAILED
    Sep 22 09:31:45 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=1 duration=10 reason=CONN_FAILED
    Sep 22 09:32:02 raspberrypi wpa_supplicant[823]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="d-link.zefox.net" auth_failures=2 duration=20 reason=CONN_FAILED
    Sep 22 09:32:10 raspberrypi NetworkManager[821]: <info> [1727022730.2605] device (wlan0): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed')
    Sep 22 09:32:10 raspberrypi NetworkManager[821]: <warn> [1727022730.2612] device (wlan0): Activation: failed for connection 'preconfigured'
    Sep 22 09:32:10 raspberrypi NetworkManager[821]: <info> [1727022730.2614] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
    as the last block of text. No errors after
    roughly the time I changed the network settings to add Device wlan0,
    which was done mid-morning on the 22nd, I think.

    Running
    journalctl | grep -i wlan0 | grep -i success
    produced much output, ending with
    Sep 22 09:35:14 raspberrypi NetworkManager[821]: <info> [1727022914.3489] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "d-link.zefox.net"
    Sep 22 09:35:14 raspberrypi NetworkManager[821]: <info> [1727022914.5427] device (wlan0): Activation: successful, device activated.
    Sep 23 09:12:57 raspberrypi NetworkManager[819]: <info> [1727107977.4602] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "d-link.zefox.net"
    Sep 23 09:12:57 raspberrypi NetworkManager[819]: <info> [1727107977.6547] device (wlan0): Activation: successful, device activated.

    The timestamp gap from Sep 22 to Sep 23 matches the pause before I
    made the Device wlan0 change.

    This isn't very clever use of journalctl, admittedly, and I don't really understand what it's showing me now.

    Running
    journalctl | grep -i wlan0 | grep -i supplicant-failed
    produces just three lines:
    Sep 21 07:36:41 raspberrypi NetworkManager[826]: <info> [1726929401.0115] device (p2p-dev-wlan0): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')
    Sep 21 07:38:51 raspberrypi NetworkManager[826]: <info> [1726929531.4462] device (p2p-dev-wlan0): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')
    Sep 22 08:05:07 raspberrypi NetworkManager[821]: <info> [1727017507.7245] device (p2p-dev-wlan0): state change: disconnected -> unavailable (reason 'supplicant-failed', sys-iface-state: 'managed')

    If any of this makes sense please clue me in. Meanwhile wifi seems to work,
    so I can get back to wrestling with your TLS exercises.

    Thanks for all your help!

    bob prohaska


    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Tuesday, September 24, 2024 01:16:43
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 24 Sep 2024 00:37:59 -0000 (UTC), bp wrote:

    At your prompting I did run
    journalctl | grep -i wlan0 | grep -i failed
    which yielded a repeating pattern of messages ending with:

    That’s the sort of idea, yes. Though note that journalctl has its own filtering options, to save you generating a whole lot of output most
    of which you might be throwing away with the grep (might make a
    difference to speed of output, that’s all).

    Sep 22 09:32:10 raspberrypi NetworkManager[821]: <info> [1727022730.2605] device (wlan0): state change: config -> failed (reason 'no-secrets', sys-iface-state: 'managed')
    Sep 22 09:32:10 raspberrypi NetworkManager[821]: <warn> [1727022730.2612] device (wlan0): Activation: failed for connection 'preconfigured'
    Sep 22 09:32:10 raspberrypi NetworkManager[821]: <info> [1727022730.2614] device (wlan0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

    These are certainly mysterious, particularly as you have success
    messages both earlier and later than this.

    Just a wild guess, but could you have two different networks with SSID “d-link.zefox.net”, with different authentication info? So what you
    are seeing is failures connecting to one and successes with the other?
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From bp@bp@www.zefox.net to comp.sys.raspberry-pi on Tuesday, September 24, 2024 15:25:35
    From Newsgroup: comp.sys.raspberry-pi

    Lawrence D'Oliveiro <ldo@nz.invalid> wrote:

    Just a wild guess, but could you have two different networks with SSID “d-link.zefox.net”, with different authentication info? So what you
    are seeing is failures connecting to one and successes with the other?

    Physically I don't see how that's possible, unless there's another
    access point within range using the same SSID set up by somebody
    else. My router has no documented ability to use more than one SSID
    and has been in use for several years, long before the Bookworm setup.

    Putting wavemon in scan mode shows something like:
    ┌─Scan window──────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
    │ │
    │d-link.zefox.net 00:13:46:86:6D:0C 93%, -45 dBm, ch 2, 2417 MHz ESS │
    │millerhome2 F0:72:EA:49:C6:4A 63%, -66 dBm, ch 6, 2437 MHz ESS, Radio Measure │
    │ATT5Zavd8s 08:9B:B9:01:B7:14 63%, -66 dBm, ch 6, 2437 MHz 7 sta, 16% chan, Radio Measure, Spectrum Mgmt │
    │ATTKXEBVbA DC:8D:8A:5A:D6:D4 64%, -65 dBm, ch 6, 2437 MHz 17% chan, Radio Measure, Spectrum Mgmt │
    │<hidden ESSID> 7C:9A:54:FC:7E:7A 73%, -59 dBm, ch 6, 2437 MHz ESS, Radio Measure, Spectrum Mgmt │
    │<hidden ESSID> 7C:9A:54:FC:7E:7E 73%, -59 dBm, ch 6, 2437 MHz ESS, Radio Measure, Spectrum Mgmt │
    │cross 7C:9A:54:FC:7E:79 73%, -59 dBm, ch 6, 2437 MHz ESS, Radio Measure, Spectrum Mgmt │
    │<hidden ESSID> 7C:9A:54:FC:7E:7C 74%, -58 dBm, ch 6, 2437 MHz ESS, Radio Measure, Spectrum Mgmt │
    │millerhome2 F0:72:EA:49:C6:4D 41%, -81 dBm, ch 149, 5745 MHz ESS, Radio Measure │
    │Xfinity Mobile 7C:9A:54:FC:7E:85 40%, -82 dBm, ch 157, 5785 MHz 1% chan, Radio Measure, Spectrum Mgmt │
    │<hidden ESSID> 7C:9A:54:FC:7E:84 50%, -75 dBm, ch 157, 5785 MHz ESS, Radio Measure, Spectrum Mgmt │
    │cross 7C:9A:54:FC:7E:81 50%, -75 dBm, ch 157, 5785 MHz ESS, Radio Measure, Spectrum Mgmt │
    │<hidden ESSID> 7C:9A:54:FC:7E:86 51%, -74 dBm, ch 157, 5785 MHz ESS, Radio Measure, Spectrum Mgmt │

    These entries change every few scans, and I don't know what the hidden ESSID entries represent.

    Thanks for writing, and any insights!

    bob prohaska

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Tuesday, September 24, 2024 16:33:51
    From Newsgroup: comp.sys.raspberry-pi

    On 24/09/2024 16:25, bp@www.zefox.net wrote:
    These entries change every few scans, and I don't know what the hidden ESSID entries represent.

    Men In Black outside your door in black Crown Vic cars?
    --
    Labour - a bunch of rich people convincing poor people to vote for rich
    people by telling poor people that "other" rich people are the reason
    they are poor.

    Peter Thompson

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From bp@bp@www.zefox.net to comp.sys.raspberry-pi on Tuesday, September 24, 2024 19:24:09
    From Newsgroup: comp.sys.raspberry-pi

    The Natural Philosopher <tnp@invalid.invalid> wrote:
    On 24/09/2024 16:25, bp@www.zefox.net wrote:
    These entries change every few scans, and I don't know what the hidden ESSID entries represent.

    Men In Black outside your door in black Crown Vic cars?

    Doubtful 8-)

    A quick web search suggests it's some sort of deprecated security protocol.
    If wavemon can see them they aren't very well hidden. I suppose it would require an interloper to correctly guess both the SSID and the password.
    That's certainly harder than just guessing a password.

    Still, for a long time (months) there's been a consistent pattern of my
    wifi getting flaky in the evening and then returning to "normal" the
    next day. That strongly suggested some kind of adjacent channel inteference when neighbors came home from work and started using their own wifi.

    Seems to me it got better after going to Bookworm for a while,
    then after an upgrade it got much worse. The moment I set the
    network device to wifi explitly the connection came up and stayed up.

    Having a single network device specified would skip any searching
    algorithms used to find a usable access point. If the search
    routine had some difficulty, that might explain at least part
    of the problem and the unexpected "solution".

    Thanks for writing,

    bob prohaska
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From druck@news@druck.org.uk to comp.sys.raspberry-pi on Tuesday, September 24, 2024 21:13:29
    From Newsgroup: comp.sys.raspberry-pi

    On 24/09/2024 02:16, Lawrence D'Oliveiro wrote:
    Though note that journalctl has its own filtering options

    Yes, throw away everything you've ever learnt on Linux, and bow to the
    will of Poettering.

    Replies to /dev/null (or should that be SystemD:NULL) please.

    ---druck
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From druck@news@druck.org.uk to comp.sys.raspberry-pi on Tuesday, September 24, 2024 21:19:34
    From Newsgroup: comp.sys.raspberry-pi

    On 24/09/2024 16:33, The Natural Philosopher wrote:
    On 24/09/2024 16:25, bp@www.zefox.net wrote:
    These entries change every few scans, and I don't know what the hidden
    ESSID entries represent.

    Men In Black outside your door in black Crown Vic cars?

    Possibly, but could be things like Amazon Firesticks. I got quite
    concerned when a couple of hidden ESSIDs with fairly high strength on
    the channel I was using followed me around when I switched channels on
    the router. But I then tracked it down to the couple of Firesticks on
    the non smart TVs, I've no idea why they do this though.

    ---druck
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Tuesday, September 24, 2024 20:57:10
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 24 Sep 2024 21:13:29 +0100, druck wrote:

    On 24/09/2024 02:16, Lawrence D'Oliveiro wrote:

    Though note that journalctl has its own filtering options

    Yes, throw away everything you've ever learnt on Linux, and bow to the
    will of Poettering.

    systemd myth number 20: “systemd makes it impossible to run syslog”.

    <http://0pointer.de/blog/projects/the-biggest-myths.html>
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From druck@news@druck.org.uk to comp.sys.raspberry-pi on Wednesday, September 25, 2024 10:30:01
    From Newsgroup: comp.sys.raspberry-pi

    On 24/09/2024 21:57, Lawrence D'Oliveiro wrote:
    On Tue, 24 Sep 2024 21:13:29 +0100, druck wrote:

    On 24/09/2024 02:16, Lawrence D'Oliveiro wrote:

    Though note that journalctl has its own filtering options

    Yes, throw away everything you've ever learnt on Linux, and bow to the
    will of Poettering.

    systemd myth number 20: “systemd makes it impossible to run syslog”.

    No, you can run rsyslog, what you can't do is only run rsyslog and get
    rid of journald.

    You are stuck with it either spaffing 2GB of unfiltered binary logs over
    your disc, or configuring it to RAM only and having it ignore the vacuum settings, so things stop working when /run gets full.

    In all a total shitshow that just isn't needed on Linux.

    ---druck

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Wednesday, September 25, 2024 11:21:47
    From Newsgroup: comp.sys.raspberry-pi

    On 24/09/2024 21:19, druck wrote:
    On 24/09/2024 16:33, The Natural Philosopher wrote:
    On 24/09/2024 16:25, bp@www.zefox.net wrote:
    These entries change every few scans, and I don't know what the
    hidden ESSID entries represent.

    Men In Black outside your door in black Crown Vic cars?

    Possibly, but could be things like Amazon Firesticks. I got quite
    concerned when a couple of hidden ESSIDs with fairly high strength on
    the channel I was using followed me around when I switched channels on
    the router. But I then tracked it down to the couple of Firesticks on
    the non smart TVs, I've no idea why they do this though.

    ---druck
    I was amazed sitting in an airport to notice 'amandasIPhone'...
    --
    No Apple devices were knowingly used in the preparation of this post.

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From druck@news@druck.org.uk to comp.sys.raspberry-pi on Wednesday, September 25, 2024 11:55:05
    From Newsgroup: comp.sys.raspberry-pi

    On 25/09/2024 11:21, The Natural Philosopher wrote:
    On 24/09/2024 21:19, druck wrote:
    On 24/09/2024 16:33, The Natural Philosopher wrote:
    On 24/09/2024 16:25, bp@www.zefox.net wrote:
    These entries change every few scans, and I don't know what the
    hidden ESSID entries represent.

    Possibly, but could be things like Amazon Firesticks. I got quite
    concerned when a couple of hidden ESSIDs with fairly high strength on
    the channel I was using followed me around when I switched channels on
    the router. But I then tracked it down to the couple of Firesticks on
    the non smart TVs, I've no idea why they do this though.

    I was amazed sitting in an airport to notice 'amandasIPhone'...

    That's just someone with network sharing on their phone.

    ---druck
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Wednesday, September 25, 2024 11:59:08
    From Newsgroup: comp.sys.raspberry-pi

    On 25/09/2024 11:55, druck wrote:
    On 25/09/2024 11:21, The Natural Philosopher wrote:
    On 24/09/2024 21:19, druck wrote:
    On 24/09/2024 16:33, The Natural Philosopher wrote:
    On 24/09/2024 16:25, bp@www.zefox.net wrote:
    These entries change every few scans, and I don't know what the
    hidden ESSID entries represent.

    Possibly, but could be things like Amazon Firesticks. I got quite
    concerned when a couple of hidden ESSIDs with fairly high strength on
    the channel I was using followed me around when I switched channels
    on the router. But I then tracked it down to the couple of Firesticks
    on the non smart TVs, I've no idea why they do this though.

    I was amazed sitting in an airport to notice 'amandasIPhone'...

    That's just someone with network sharing on their phone.

    Yes, but she wasnt. She was just doing something I-phoneish oblivious
    to the fact that her phone was severely compromised by leaving it in
    access point mode

    ---druck
    --
    Outside of a dog, a book is a man's best friend. Inside of a dog it's
    too dark to read.

    Groucho Marx



    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Wednesday, September 25, 2024 21:52:22
    From Newsgroup: comp.sys.raspberry-pi

    On Wed, 25 Sep 2024 10:30:01 +0100, druck wrote:

    On 24/09/2024 21:57, Lawrence D'Oliveiro wrote:

    On Tue, 24 Sep 2024 21:13:29 +0100, druck wrote:

    On 24/09/2024 02:16, Lawrence D'Oliveiro wrote:

    Though note that journalctl has its own filtering options

    Yes, throw away everything you've ever learnt on Linux, and bow to the
    will of Poettering.

    systemd myth number 20: “systemd makes it impossible to run syslog”.

    No, you can run rsyslog, what you can't do is only run rsyslog and get
    rid of journald.

    Just configure it not to save anything in the journal, if you really want.
    You know it’s configurable, right?

    <https://www.freedesktop.org/software/systemd/man/latest/journald.conf.html> --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From nev young@newsforpasiphae1953@yahoo.co.uk to comp.sys.raspberry-pi on Thursday, September 26, 2024 10:00:07
    From Newsgroup: comp.sys.raspberry-pi

    On 21/09/2024 16:53, bp@www.zefox.net wrote:
    This morning, after a few minutes' use of my Pi5 running Bookworm,
    the WiFi connection abruptly dropped. Couldn't bring it back up,
    so I rebooted the access point. No luck. Then I rebooted the Pi5
    and noticed something about rfkill stopping wifi in the boot messages.
    At this point the last reboot was several days past, wifi hadn't been
    touched or given any trouble.

    Went to raspi-config and rebuilt all of the locales, still couldn't
    connect. Finally I opened the system preferences and set locales,
    which were already correct according to the selections shown.

    The machine then proceeded to work normally, as I write this.
    I've had trouble before with rfkill turning on out of the blue,
    but hadn't seen the problem for a month or two and thought it
    resolved.

    Is this a widespread problem, and is there a fix? The fact that
    it happened days after the most recent reboot seems very strange.


    During my attempt to run bookworm over the last 3 months I had the
    problem of the wifi dropping as well.
    Couldn't be arsed to find out why. Real life gets in the way.
    My Hammer / nut solution is run a cron job every 5 min.
    If I can't ping the router then sleep 10
    If I still can't ping the router sleep 20
    If I still can't ping the router sleep 30
    If I still can't ping the router reboot.

    I suspect this won't help you but all my pi zeroes are headless and this
    does (did) work. See my bookworm resolution in the other thread.
    --
    Nev
    It causes me a great deal of regret and remorse
    that so many people are unable to understand what I write.

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From druck@news@druck.org.uk to comp.sys.raspberry-pi on Thursday, September 26, 2024 21:25:40
    From Newsgroup: comp.sys.raspberry-pi

    On 26/09/2024 10:00, nev young wrote:
    During my attempt to run bookworm over the last 3 months I had the
    problem of the wifi dropping as well.
    Couldn't be arsed to find out why. Real life gets in the way.
    My Hammer / nut solution is run a cron job every 5 min.
    If I can't ping the router then    sleep 10
    If I still can't ping the router sleep 20
    If I still can't ping the router sleep 30
    If I still can't ping the router reboot.

    I suspect this won't help you but all my pi zeroes are headless and this does (did) work. See my bookworm resolution in the other thread.

    This is a very poor solution. If you must do an automatic reboot when
    network connectivity fails, install and configure the watchdog package.

    Getting to the bottom of the problem is the best thing to do.

    ---druk
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Thursday, September 26, 2024 20:37:36
    From Newsgroup: comp.sys.raspberry-pi

    On Thu, 26 Sep 2024 21:25:40 +0100, druck wrote:

    Getting to the bottom of the problem is the best thing to do.

    “Have you tried turning it off and on again?” is something they do in the Windows world, we try to avoid that in the Linux world.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Friday, September 27, 2024 02:11:11
    From Newsgroup: comp.sys.raspberry-pi

    On 26/09/2024 21:25, druck wrote:
    On 26/09/2024 10:00, nev young wrote:
    During my attempt to run bookworm over the last 3 months I had the
    problem of the wifi dropping as well.
    Couldn't be arsed to find out why. Real life gets in the way.
    My Hammer / nut solution is run a cron job every 5 min.
    If I can't ping the router then    sleep 10
    If I still can't ping the router sleep 20
    If I still can't ping the router sleep 30
    If I still can't ping the router reboot.

    I suspect this won't help you but all my pi zeroes are headless and
    this does (did) work. See my bookworm resolution in the other thread.

    This is a very poor solution. If you must do an automatic reboot when network connectivity fails, install and configure the watchdog package.

    Getting to the bottom of the problem is the best thing to do.

    ---druk

    Apropos that, since the more powerful power supply, my Bookworm on the
    PXZW has been rock solid on Wifi.
    --
    “Some people like to travel by train because it combines the slowness of
    a car with the cramped public exposure of 
an airplane.”

    Dennis Miller


    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Friday, September 27, 2024 10:09:53
    From Newsgroup: comp.sys.raspberry-pi

    On 27/09/2024 02:11, The Natural Philosopher wrote:
    On 26/09/2024 21:25, druck wrote:
    On 26/09/2024 10:00, nev young wrote:
    During my attempt to run bookworm over the last 3 months I had the
    problem of the wifi dropping as well.
    Couldn't be arsed to find out why. Real life gets in the way.
    My Hammer / nut solution is run a cron job every 5 min.
    If I can't ping the router then    sleep 10
    If I still can't ping the router sleep 20
    If I still can't ping the router sleep 30
    If I still can't ping the router reboot.

    I suspect this won't help you but all my pi zeroes are headless and
    this does (did) work. See my bookworm resolution in the other thread.

    This is a very poor solution. If you must do an automatic reboot when
    network connectivity fails, install and configure the watchdog package.

    Getting to the bottom of the problem is the best thing to do.

    ---druk

    Apropos that, since the more powerful power supply, my Bookworm on the
    PXZW has been rock solid on Wifi.

    ...make that PZ2W..I plead BC - Before Caffeine
    --
    You can get much farther with a kind word and a gun than you can with a
    kind word alone.

    Al Capone



    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From nev young@newsforpasiphae1953@yahoo.co.uk to comp.sys.raspberry-pi on Friday, September 27, 2024 11:47:38
    From Newsgroup: comp.sys.raspberry-pi

    On 26/09/2024 21:25, druck wrote:
    On 26/09/2024 10:00, nev young wrote:
    During my attempt to run bookworm over the last 3 months I had the
    problem of the wifi dropping as well.
    Couldn't be arsed to find out why. Real life gets in the way.
    My Hammer / nut solution is run a cron job every 5 min.
    If I can't ping the router then    sleep 10
    If I still can't ping the router sleep 20
    If I still can't ping the router sleep 30
    If I still can't ping the router reboot.

    I suspect this won't help you but all my pi zeroes are headless and
    this does (did) work. See my bookworm resolution in the other thread.

    This is a very poor solution. If you must do an automatic reboot when network connectivity fails, install and configure the watchdog package.

    Oddly the name I gave to the script was lan_watchdog :-)
    Don't need it now. I'm back on buster and the wifi is solid.

    Getting to the bottom of the problem is the best thing to do.
    I'm happy to just accept that someone somewhere sometime fscked up and
    broke it.
    I wouldn't be at all surprised if they now stand in a dole queue next to someone from Crowdstrike. :-!


    ---druk
    --
    Nev
    It causes me a great deal of regret and remorse
    that so many people are unable to understand what I write.

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From nev young@newsforpasiphae1953@yahoo.co.uk to comp.sys.raspberry-pi on Friday, September 27, 2024 11:55:48
    From Newsgroup: comp.sys.raspberry-pi

    On 26/09/2024 21:37, Lawrence D'Oliveiro wrote:
    On Thu, 26 Sep 2024 21:25:40 +0100, druck wrote:

    Getting to the bottom of the problem is the best thing to do.

    “Have you tried turning it off and on again?” is something they do in the Windows world, we try to avoid that in the Linux world.

    OMG. I was going to say I haven't touched a windows machine this
    century. Then I realised we're only 3 months from being 1/4 the way
    through it. 2025 already! Where did the time go and why didn't I enjoy
    it more?
    --
    Nev
    It causes me a great deal of regret and remorse
    that so many people are unable to understand what I write.

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Friday, September 27, 2024 23:05:58
    From Newsgroup: comp.sys.raspberry-pi

    On Fri, 27 Sep 2024 11:55:48 +0100, nev young wrote:

    Then I realised we're only 3 months from being 1/4 the way
    through it. 2025 already!

    Yeah. The 21st century began in 2000. Don’t listen to those who try to say it didn’t start until 2001.

    Where did the time go and why didn't I enjoy it more?

    For me, this century has been my journey away from being an Apple Mac enthusiast/expert/fanatic to being a Linux enthusiast/somewhat-expert/ slightly-fanatic.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Single Stage to Orbit@alex.buell@munted.eu to comp.sys.raspberry-pi on Saturday, September 28, 2024 09:59:53
    From Newsgroup: comp.sys.raspberry-pi

    On Fri, 2024-09-27 at 23:05 +0000, Lawrence D'Oliveiro wrote:
    On Fri, 27 Sep 2024 11:55:48 +0100, nev young wrote:

    Then I realised we're only 3 months from being 1/4 the way
    through it. 2025 already!

    Yeah. The 21st century began in 2000. Don’t listen to those who try
    to say it didn’t start until 2001.

    There's no year zero. So the first century didn't start until the year
    1. :-p
    --
    Tactical Nuclear Kittens
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Deloptes@deloptes@gmail.com to comp.sys.raspberry-pi on Saturday, September 28, 2024 11:25:34
    From Newsgroup: comp.sys.raspberry-pi

    bp@www.zefox.net wrote:

    This morning, after a few minutes' use of my Pi5 running Bookworm,
    the WiFi connection abruptly dropped. Couldn't bring it back up,
    so I rebooted the access point. No luck. Then I rebooted the Pi5
    and noticed something about rfkill stopping wifi in the boot messages.
    At this point the last reboot was several days past, wifi hadn't been
    touched or given any trouble.

    do you have NTP configured and do you have networkmanager in use?

    If not get them running and see if it solved the issues.

    (been there seen it all)

    BR
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Saturday, September 28, 2024 11:55:12
    From Newsgroup: comp.sys.raspberry-pi

    On 28/09/2024 10:25, Deloptes wrote:
    bp@www.zefox.net wrote:

    This morning, after a few minutes' use of my Pi5 running Bookworm,
    the WiFi connection abruptly dropped. Couldn't bring it back up,
    so I rebooted the access point. No luck. Then I rebooted the Pi5
    and noticed something about rfkill stopping wifi in the boot messages.
    At this point the last reboot was several days past, wifi hadn't been
    touched or given any trouble.

    do you have NTP configured and do you have networkmanager in use?

    If not get them running and see if it solved the issues.

    (been there seen it all)

    BR

    Hard to get NTP to run without a network connection

    My PICO pi Ws dont even have calendar clocks, and they connect OK.
    Let me list all the things that people have said fucked up their wifi on
    PI Zeros Ws...and other Pis...

    - power saving mode (one existing Pi Zero W had it, the other did not.
    No difference connecting to same wifi access point)
    - different wifi chipset (eventually I discovered all my pis were
    running the same chipset)
    - interference from HDMI (Headless. HDMI disabled)
    - random allocation of MAC addresses. (disabled - no difference)
    - No NTP configured (you) [always configured by me anyway]
    - network manager not running (you) [it's part of the default bookworm installation]
    - various odd 802.11 modes on their router.. (my other two Pis connected
    to my main wifi point just fine. I changed the Pi to run on a different
    one and the problem persisted)
    - crappy power supply (me, and others) [ changing the power supply has resulted in no drops since connected to any WiFi access point]

    (pifi2:~ $ uptime
    11:52:12 up 1 day, 22:49, 2 users, load average: 0.00, 0.00, 0.00

    That now running against the access point that it had when dropping out
    at least once every 24 hours

    I will leave it a few more days to make sure...)

    As you can see I went through *every single one*.

    And fixed it one way or another, (I didn't worry about ntp: If I am
    running linux on a network there is no way that wont be enabled by me,
    and Bookworm defaults to network manager anyway, so that is also default)

    The *only* one that actually fixed the problem and made Bookworm Pi Z 2W
    as rock stable as all my other Pi's was putting a larger PSU on it.

    I am not saying that other people's problems are the same cause, but I
    am saying that hairy ass guesses are simply no substitute for trying
    *all* of the above systematically.

    Because the log files - systemd or otherwise -, are simply full of
    useless detail. There to help the programmer debug his code, not to help
    Joe Ordinary find out why his wifi is fucked.

    For us, its a matter of trial and error until a stable system is arrived at.

    Now my *conjecture* is that both a Zero 2W, a Pi 5 and indeed Bookworm
    on it, use more power. And a marginal PSU will fail more readily, and
    the wifi is the first point of failure

    Because this problem is not in general related to Bookworm on any other platform. And the wifi chips themselves are pretty much the same

    But in the end, my original thread was not 'give me your hairy assed
    guesses' but 'how do I solve this issue algorithmically'

    And the answer was that the log files were useless, and trial and error
    and eliminating one issue at a time was the only pragmatic approach.

    And everyone had a 'this worked for me' fix and none of them were the same.

    Now I too have a 'this worked for me' fix, but I *also* have a pragmatic approach to bug hunting this one.
    --
    "Anyone who believes that the laws of physics are mere social
    conventions is invited to try transgressing those conventions from the
    windows of my apartment. (I live on the twenty-first floor.) "

    Alan Sokal

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.sys.raspberry-pi on Sunday, September 29, 2024 04:26:08
    From Newsgroup: comp.sys.raspberry-pi

    On 2024-09-28, Single Stage to Orbit <alex.buell@munted.eu> wrote:

    On Fri, 2024-09-27 at 23:05 +0000, Lawrence D'Oliveiro wrote:

    On Fri, 27 Sep 2024 11:55:48 +0100, nev young wrote:

    Then I realised we're only 3 months from being 1/4 the way
    through it. 2025 already!

    Yeah. The 21st century began in 2000. Don’t listen to those who try
    to say it didn’t start until 2001.


    There's no year zero. So the first century didn't start until the year
    1. :-p

    So how many years are there in a century? Does it depend on
    which century it is?
    --
    /~\ Charlie Gibbs | We'll go down in history as the
    \ / <cgibbs@kltpzyxm.invalid> | first society that wouldn't save
    X I'm really at ac.dekanfrus | itself because it wasn't cost-
    / \ if you read it the right way. | effective. -- Kurt Vonnegut
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Richard Kettlewell@invalid@invalid.invalid to comp.sys.raspberry-pi on Sunday, September 29, 2024 09:26:51
    From Newsgroup: comp.sys.raspberry-pi

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the
    year 1. :-p

    So how many years are there in a century? Does it depend on
    which century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or
    100(n+1) BCE to 100n+1 BCE inclusive).
    --
    https://www.greenend.org.uk/rjk/
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Single Stage to Orbit@alex.buell@munted.eu to comp.sys.raspberry-pi on Sunday, September 29, 2024 09:12:20
    From Newsgroup: comp.sys.raspberry-pi

    On Sun, 2024-09-29 at 04:26 +0000, Charlie Gibbs wrote:
    On 2024-09-28, Single Stage to Orbit <alex.buell@munted.eu> wrote:

    On Fri, 2024-09-27 at 23:05 +0000, Lawrence D'Oliveiro wrote:

    On Fri, 27 Sep 2024 11:55:48 +0100, nev young wrote:

    Then I realised we're only 3 months from being 1/4 the way
    through it. 2025 already!

    Yeah. The 21st century began in 2000. Don’t listen to those who
    try to say it didn’t start until 2001.


    There's no year zero. So the first century didn't start until the
    year
    1. :-p

    So how many years are there in a century?  Does it depend on
    which century it is?
    It goes from 1 to 100 for the first century. Then 101 to 200.
    1 2 3 4 5 6 7 8 9 10
    ..
    ..
    ..
    91 92 93 94 95 96 97 98 99 100
    --
    Tactical Nuclear Kittens
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Sunday, September 29, 2024 23:44:47
    From Newsgroup: comp.sys.raspberry-pi

    On Sun, 29 Sep 2024 09:26:51 +0100, Richard Kettlewell wrote:

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or 100(n+1) BCE to 100n+1 BCE inclusive).

    Fun fact: astronomers include a “year zero”.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Pancho@Pancho.Jones@proton.me to comp.sys.raspberry-pi on Monday, September 30, 2024 13:21:50
    From Newsgroup: comp.sys.raspberry-pi

    On 29/09/2024 09:26, Richard Kettlewell wrote:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the
    year 1. :-p

    So how many years are there in a century? Does it depend on
    which century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or 100(n+1) BCE to 100n+1 BCE inclusive).


    What about the century containing the Big Bang?
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Monday, September 30, 2024 14:21:49
    From Newsgroup: comp.sys.raspberry-pi

    On 30/09/2024 13:21, Pancho wrote:
    On 29/09/2024 09:26, Richard Kettlewell wrote:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the
    year 1. :-p

    So how many years are there in a century?  Does it depend on
    which century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or
    100(n+1) BCE to 100n+1 BCE inclusive).


    What about the century containing the Big Bang?

    I dont think anyone was counting then
    --
    Microsoft : the best reason to go to Linux that ever existed.

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From nev young@newsforpasiphae1953@yahoo.co.uk to comp.sys.raspberry-pi on Monday, September 30, 2024 14:57:25
    From Newsgroup: comp.sys.raspberry-pi

    On 30/09/2024 14:21, The Natural Philosopher wrote:
    On 30/09/2024 13:21, Pancho wrote:
    On 29/09/2024 09:26, Richard Kettlewell wrote:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the
    year 1. :-p

    So how many years are there in a century?  Does it depend on
    which century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or
    100(n+1) BCE to 100n+1 BCE inclusive).


    What about the century containing the Big Bang?

    I dont think anyone was counting then

    What year is it anyway?
    Assyrian-6,772
    Hebrew-5,784
    Chinese-4,721
    Julian-2,777
    Buddhist-2,564
    Gregorian-2,024
    Hindu-1,945
    Islamic-1,445
    Persian-1,402
    French Revolutionary-231

    stolen from https://www.statista.com/statistics/1034385/current-year-various-calendars/
    --
    Nev
    It causes me a great deal of regret and remorse
    that so many people are unable to understand what I write.

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From David Higton@dave@davehigton.me.uk to comp.sys.raspberry-pi on Monday, September 30, 2024 19:15:43
    From Newsgroup: comp.sys.raspberry-pi

    In message <vde54u$27ol9$2@dont-email.me>
    Pancho <Pancho.Jones@proton.me> wrote:

    On 29/09/2024 09:26, Richard Kettlewell wrote:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the
    year 1. :-p

    So how many years are there in a century? Does it depend on which century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or 100(n+1) BCE to 100n+1 BCE inclusive).


    What about the century containing the Big Bang?

    Which century was that, then?

    David
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Monday, September 30, 2024 21:07:11
    From Newsgroup: comp.sys.raspberry-pi

    On Mon, 30 Sep 2024 14:21:49 +0100, The Natural Philosopher wrote:

    On 30/09/2024 13:21, Pancho wrote:

    What about the century containing the Big Bang?

    I dont think anyone was counting then

    Nobody looked around and said “let’s count this as 1 A.D.”, either.

    I always thought the Big Bang was a much more rational basis for a time reference point than some ill-defined mythological/religious not-quite- sure-when-it-was-supposed-to-have-happened-anyway fictional event.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Monday, September 30, 2024 21:09:53
    From Newsgroup: comp.sys.raspberry-pi

    On Mon, 30 Sep 2024 19:15:43 +0100, David Higton wrote:

    In message <vde54u$27ol9$2@dont-email.me>
    Pancho <Pancho.Jones@proton.me> wrote:

    What about the century containing the Big Bang?

    Which century was that, then?

    Astronomers already use Julian days. Go back to Julian day zero, and set
    your Big Bang zero point exactly, say, 13.7 billion years before that. Doesn’t matter if future measurements cause some adjustments to the actual moment of the Big Bang: this is just meant as an arbitrary reference point anyway, meant to get rid of awkward “B.C.” dates.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Pancho@Pancho.Jones@proton.me to comp.sys.raspberry-pi on Monday, September 30, 2024 22:45:45
    From Newsgroup: comp.sys.raspberry-pi

    On 9/30/24 19:15, David Higton wrote:
    In message <vde54u$27ol9$2@dont-email.me>
    Pancho <Pancho.Jones@proton.me> wrote:

    On 29/09/2024 09:26, Richard Kettlewell wrote:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the
    year 1. :-p

    So how many years are there in a century? Does it depend on which
    century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or
    100(n+1) BCE to 100n+1 BCE inclusive).


    What about the century containing the Big Bang?

    Which century was that, then?

    David

    One assumes time is well ordered, so even if I don't know what the least century is, I know there was one.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Pancho@Pancho.Jones@proton.me to comp.sys.raspberry-pi on Monday, September 30, 2024 22:48:50
    From Newsgroup: comp.sys.raspberry-pi

    On 9/30/24 14:21, The Natural Philosopher wrote:
    On 30/09/2024 13:21, Pancho wrote:
    On 29/09/2024 09:26, Richard Kettlewell wrote:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the
    year 1. :-p

    So how many years are there in a century?  Does it depend on
    which century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or
    100(n+1) BCE to 100n+1 BCE inclusive).


    What about the century containing the Big Bang?

    I dont think anyone was counting then

    Nonsense, lots going on in that first century. Particularly the first
    few minutes.

    <https://www.physicsoftheuniverse.com/topics_bigbang_timeline.html>
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Monday, September 30, 2024 22:06:28
    From Newsgroup: comp.sys.raspberry-pi

    On Mon, 30 Sep 2024 22:45:45 +0100, Pancho wrote:

    One assumes time is well ordered, so even if I don't know what the least century is, I know there was one.

    Integers are well ordered, but there is no least integer.

    All we want, I think, is a zero point far enough back that there is less real-world need to deal with negative time points.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Pancho@Pancho.Jones@proton.me to comp.sys.raspberry-pi on Monday, September 30, 2024 23:16:21
    From Newsgroup: comp.sys.raspberry-pi

    On 9/30/24 23:06, Lawrence D'Oliveiro wrote:
    On Mon, 30 Sep 2024 22:45:45 +0100, Pancho wrote:

    One assumes time is well ordered, so even if I don't know what the least
    century is, I know there was one.

    Integers are well ordered, but there is no least integer.


    No they aren't, precisely because the don't have a least integer.
    Perhaps you are confusing having a total ordering with well ordered?

    All we want, I think, is a zero point far enough back that there is less real-world need to deal with negative time points.

    That is basically what well-ordered implies. Obviously I was
    bullshitting as I have no idea if time is totally-ordered, let alone
    well ordered :-).
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Monday, September 30, 2024 23:16:58
    From Newsgroup: comp.sys.raspberry-pi

    On Mon, 30 Sep 2024 23:16:21 +0100, Pancho wrote:

    On 9/30/24 23:06, Lawrence D'Oliveiro wrote:

    On Mon, 30 Sep 2024 22:45:45 +0100, Pancho wrote:

    One assumes time is well ordered, so even if I don't know what the
    least century is, I know there was one.

    Integers are well ordered, but there is no least integer.


    No they aren't, precisely because the don't have a least integer.
    Perhaps you are confusing having a total ordering with well ordered?

    You were the one who used the term “well ordered”, and then said that, because of this, there had to be a least century.

    All we want, I think, is a zero point far enough back that there is
    less real-world need to deal with negative time points.

    That is basically what well-ordered implies. Obviously I was
    bullshitting as I have no idea if time is totally-ordered, let alone
    well ordered :-).

    Einstein’s Special Relativity says time is not totally ordered, unfortunately ...
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Pancho@Pancho.Jones@proton.me to comp.sys.raspberry-pi on Tuesday, October 01, 2024 09:34:09
    From Newsgroup: comp.sys.raspberry-pi

    On 10/1/24 00:16, Lawrence D'Oliveiro wrote:
    On Mon, 30 Sep 2024 23:16:21 +0100, Pancho wrote:

    On 9/30/24 23:06, Lawrence D'Oliveiro wrote:

    On Mon, 30 Sep 2024 22:45:45 +0100, Pancho wrote:

    One assumes time is well ordered, so even if I don't know what the
    least century is, I know there was one.

    Integers are well ordered, but there is no least integer.


    No they aren't, precisely because the don't have a least integer.
    Perhaps you are confusing having a total ordering with well ordered?

    You were the one who used the term “well ordered”, and then said that, because of this, there had to be a least century.


    Well ordered is a text book definition, an important one in maths. Not a particularly "well" named one, as people do tend to confuse the meaning
    with total ordering. It should also be known in computer science, as the assumption that the positive integers are well ordered is equivalent to
    the assumption that induction works and induction is a similar concept
    to recursion.

    All we want, I think, is a zero point far enough back that there is
    less real-world need to deal with negative time points.

    That is basically what well-ordered implies. Obviously I was
    bullshitting as I have no idea if time is totally-ordered, let alone
    well ordered :-).

    Einstein’s Special Relativity says time is not totally ordered, unfortunately ...

    Well, possibly. In banking software we assumed time was totally ordered,
    (but times from different clocks wasn't). In GPS software I don't know.
    In general, given we are all terrestrial observers, I'm not sure
    relativity matters, when discussing centuries. I'm not a physicist.

    The joke was meant to be that it is totally unreasonable to assume that
    time did start with the big bang and that it was a stupid special case
    anyway.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Tuesday, October 01, 2024 08:39:56
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 1 Oct 2024 09:34:09 +0100, Pancho wrote:

    The joke was meant to be that it is totally unreasonable to assume that
    time did start with the big bang and that it was a stupid special case anyway.

    Some think time may have started with the Big Bang, but there are hints
    that there may be, or have been, other Bangs, before, since, elsewhere, elsewhen.

    One thing is true: our Big Bang is the biggest single event to have
    happened in our little observable corner of the Universe over the entire timespan that we’re aware of. So it makes sense to use that, more than anything else, as our calendar reference for measuring all of time -- certainly more sense than some fictional religious event that only has significance to one small part of our species. At least until we come up
    with a better one.

    “The Universe is such a fascinating place, don’t you think? I wouldn’t want to live anywhere else.”
    -- half-remembered quote from I don’t know where
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Tuesday, October 01, 2024 13:31:44
    From Newsgroup: comp.sys.raspberry-pi

    On 30/09/2024 22:45, Pancho wrote:
    On 9/30/24 19:15, David Higton wrote:
    In message <vde54u$27ol9$2@dont-email.me>
               Pancho <Pancho.Jones@proton.me> wrote:

    On 29/09/2024 09:26, Richard Kettlewell wrote:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the
    year 1. :-p

    So how many years are there in a century?  Does it depend on which
    century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or >>>> 100(n+1) BCE to 100n+1 BCE inclusive).


    What about the century containing the Big Bang?

    Which century was that, then?

    David

    One assumes

    Arr. That be Metaphysics them, that be

    time is well ordered, so even if I don't know what the least
    century is, I know there was one.
    --
    Climate Change: Socialism wearing a lab coat.

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From The Natural Philosopher@tnp@invalid.invalid to comp.sys.raspberry-pi on Tuesday, October 01, 2024 13:32:56
    From Newsgroup: comp.sys.raspberry-pi

    On 30/09/2024 22:48, Pancho wrote:
    On 9/30/24 14:21, The Natural Philosopher wrote:
    On 30/09/2024 13:21, Pancho wrote:
    On 29/09/2024 09:26, Richard Kettlewell wrote:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the
    year 1. :-p

    So how many years are there in a century?  Does it depend on
    which century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or >>>> 100(n+1) BCE to 100n+1 BCE inclusive).


    What about the century containing the Big Bang?

    I dont think anyone was counting then

    Nonsense, lots going on in that first century. Particularly the first
    few minutes.


    What has that got to do with the fact that no one was counting, then?

    <https://www.physicsoftheuniverse.com/topics_bigbang_timeline.html>
    --
    Climate Change: Socialism wearing a lab coat.

    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Pancho@Pancho.Jones@proton.me to comp.sys.raspberry-pi on Tuesday, October 01, 2024 16:09:15
    From Newsgroup: comp.sys.raspberry-pi

    On 10/1/24 13:32, The Natural Philosopher wrote:
    On 30/09/2024 22:48, Pancho wrote:
    On 9/30/24 14:21, The Natural Philosopher wrote:
    On 30/09/2024 13:21, Pancho wrote:
    On 29/09/2024 09:26, Richard Kettlewell wrote:
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> writes:
    Single Stage to Orbit <alex.buell@munted.eu> wrote:
    There's no year zero. So the first century didn't start until the >>>>>>> year 1. :-p

    So how many years are there in a century?  Does it depend on
    which century it is?

    No, all one hundred years, from 100n+1 CE to 100(n+1) CE inclusive (or >>>>> 100(n+1) BCE to 100n+1 BCE inclusive).


    What about the century containing the Big Bang?

    I dont think anyone was counting then

    Nonsense, lots going on in that first century. Particularly the first
    few minutes.


    What has that got to do with the fact that no one was counting, then?

    <https://www.physicsoftheuniverse.com/topics_bigbang_timeline.html>


    Well, no one was counting in year zero either, when baby Jesus was born. Otherwise they wouldn't have forgotten to put that year in a century. AD
    was devised in AD 525, I just looked it up.

    Hindu-Arabic numerals didn't make 0 explicit until much later, maybe
    11th century.
    --- Synchronet 3.19b-Win32 NewsLink 1.113
  • From Lawrence D'Oliveiro@ldo@nz.invalid to comp.sys.raspberry-pi on Tuesday, October 01, 2024 21:33:06
    From Newsgroup: comp.sys.raspberry-pi

    On Tue, 1 Oct 2024 13:32:56 +0100, The Natural Philosopher wrote:

    What has that got to do with the fact that no one was counting, then?

    Let’s just say, we have more evidence for what happened in the first few minutes of the Big Bang, then we have for any religious creation myth.
    --- Synchronet 3.19b-Win32 NewsLink 1.113