On 18/11/2020 21:54, John Nelson via wsjt-devel wrote:
Hi Bill,
Further to the WSJT-X + Big Sur + M1 problem, three conclusions have been
reached following tests with my correspondent:
1. The M1 page size is 4k and not 16k
2. It seems that the M1 version of Big Sur does not get the shared memory
information from /etc/sysctl.conf
3. If kern.sysv.shmmax and kern.sysv.shmall are directly written to via
terminal commands (104857600 and 25600 respectively) then WSJT-X loads and
runs.
The snag here is that these kern.sysv values do not survive a reboot - although
this has to be tested. Next step is to find out how to set the shared memory
configuration in a permanent way. Tomorrow’s job…
— John G4KLA
Hi John,
I finally have a Big Sur upgrade completed on a VM. I note that the
upgrade relocates the original /etc/sysctl.conf which implies it is no
longer supported, but as you say putting it back and rebooting does
update the shared memory settings on x86_64 hardware. So far I can find
any information on why the sysctl.conf file doesn't work on arm64
hardware or what the equivalent mechanism is for that platform.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
