Re: [wsjt-devel] WSJT and MLDX

[Adrian]

Check you have a time sync service running, eg ntp, and check your time 
at time.is for accuracy.



https://community.spiceworks.com/topic/332293-how-to-setup-max-os-x-ntp-server-and-synchronise-with-ad


On 28/10/20 10:41 am, Michael Sanford wrote:

I tried to get started on WSJT today and use MacLoggerDX and for some reason my 
radio setting on MLDX got all screwed up. I tried to turn on radio using MLDX 
and it didn’t turn on WHILE I was running WSJT and all my settings apparently 
got corrupted. I sent the debug log and several screen shots to MLDX for help. 
Apparently there can be a logging connection to MLDX from WSJT but since I 
screwed up my settings I can’t get the CAT of MLDX to work.

Also, I cannot seem to decode on WSJT. WSJT is recognizing my radio and 
connects and I see waveforms on the window but no decoding. I assume that the 
signals may not be in the WSJT digital decoding purview.

Thanks Mike
K0CCP

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT and MLDX

[Michael Sanford]

I tried to get started on WSJT today and use MacLoggerDX and for some reason my 
radio setting on MLDX got all screwed up. I tried to turn on radio using MLDX 
and it didn’t turn on WHILE I was running WSJT and all my settings apparently 
got corrupted. I sent the debug log and several screen shots to MLDX for help. 
Apparently there can be a logging connection to MLDX from WSJT but since I 
screwed up my settings I can’t get the CAT of MLDX to work.

Also, I cannot seem to decode on WSJT. WSJT is recognizing my radio and 
connects and I see waveforms on the window but no decoding. I assume that the 
signals may not be in the WSJT digital decoding purview.

Thanks Mike
K0CCP

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Shared memory error

[David Kaplan via wsjt-devel]

Quite a difference, thanks.

I had hoped that the distro at the WSJT-X site had been updated, but I guess 
not.

73,

David, WA1OUI

On Oct 27, 2020, at 4:31 PM, Black Michael via wsjt-devel 
 wrote:

https://wsjtx.groups.io/g/main/message/16844 


Mike W9MDB




On Tuesday, October 27, 2020, 03:27:05 PM CDT, David Kaplan via wsjt-devel 
 wrote:


I’m running Catalina 10.15.7 and a few weeks ago saw a notice that for the new 
beta the shmmax had to be increased. I carefully flagged and saved that email. 
Now that I am ready to install the beta, the email is nowhere to be found.

I had completely erased and re-installed everything on my iMac to clean off 6 
years of crud buildup.

I downloaded a fresh copy, have increased my shmmax to the14680064 listed in 
the readme and sample sysctl.conf. This is confirmed with the sysctl command. 
However I still get an error “Shared Memory Error, Unable to create shared 
segment”… and this is after reboot.

Thanks & 73,

David, WA1OUI

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Shared memory error

[Alois Windpassinger]

I have exactly the Same Problem on my imac running mac-os high sierra with
wsjtx v... rc1, while v. 2.2.1 of wsjt-X runs without any problem on my
imac.

73 de dl8rbl

David Kaplan via wsjt-devel  schrieb am
Di., 27. Okt. 2020, 21:27:

> I’m running Catalina 10.15.7 and a few weeks ago saw a notice that for the
> new beta the shmmax had to be increased. I carefully flagged and saved that
> email. Now that I am ready to install the beta, the email is nowhere to be
> found.
>
> I had completely erased and re-installed everything on my iMac to clean
> off 6 years of crud buildup.
>
> I downloaded a fresh copy, have increased my shmmax to the14680064 listed
> in the readme and sample sysctl.conf. This is confirmed with the sysctl
> command. However I still get an error “Shared Memory Error, Unable to
> create shared segment”… and this is after reboot.
>
> Thanks & 73,
>
> David, WA1OUI
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Shared memory error

[Black Michael via wsjt-devel]

https://wsjtx.groups.io/g/main/message/16844

Mike W9MDB

 

On Tuesday, October 27, 2020, 03:27:05 PM CDT, David Kaplan via wsjt-devel 
 wrote:  
 
 I’m running Catalina 10.15.7 and a few weeks ago saw a notice that for the new 
beta the shmmax had to be increased. I carefully flagged and saved that email. 
Now that I am ready to install the beta, the email is nowhere to be found.

I had completely erased and re-installed everything on my iMac to clean off 6 
years of crud buildup.

I downloaded a fresh copy, have increased my shmmax to the14680064 listed in 
the readme and sample sysctl.conf. This is confirmed with the sysctl command. 
However I still get an error “Shared Memory Error, Unable to create shared 
segment”… and this is after reboot.

Thanks & 73,

David, WA1OUI

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Shared memory error

[David Kaplan via wsjt-devel]

I’m running Catalina 10.15.7 and a few weeks ago saw a notice that for the new 
beta the shmmax had to be increased. I carefully flagged and saved that email. 
Now that I am ready to install the beta, the email is nowhere to be found.

I had completely erased and re-installed everything on my iMac to clean off 6 
years of crud buildup.

I downloaded a fresh copy, have increased my shmmax to the14680064 listed in 
the readme and sample sysctl.conf. This is confirmed with the sysctl command. 
However I still get an error “Shared Memory Error, Unable to create shared 
segment”… and this is after reboot.

Thanks & 73,

David, WA1OUI

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] compilation using Debian Stable

[Christoph Berg]

Re: Claude Frantz
> Now, the question which occurs for me is "is it better to switch to Debian
> stable ?". The sublevels (stable, testing, etc.) are not the same in Debian
> and Fedora. For me, it's difficult to understand which are the matching
> sublevels.
> 
> At the present state, I think that the switching to Debian stable, with the
> backports option, could be a good choice. Today, I'm not more a big software
> designer, but I'm only a little one.

Stable ("buster" at the moment) is a good choice if you aren't
interested in getting the newest things all the time, but prefer a
stable system. The -backports suites have selected packages from
"testing" for use on stable.

I'll keep the wsjtx backport in buster-backports updated.

Testing ("bullseye") is continually being updated from unstable
("sid") with a delay of a few days. That is a good choice if you are
willing to upgrade the system every (few) week(s).

Unstable is really only recommended if you are following Debian
development closely and want to be the first to find bugs before
packages migrate to testing.

73,
Christoph DF7CB


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] compilation using Debian Stable

[Claude Frantz]

On 10/26/20 8:47 PM, Paul Bramscher wrote:

Hi Paul, Christoph & all,

Many thanks for this very interesting information.

I'm a long time user of the Red Hat, then Fedora distribution. At the 
decision time of the distribution to use, this was probably not the 
wrong choice, but time has gone and I'm less and less convinced that 
this is not more the best choice for me. Today, Fedora is really an 
experimental distribution. The introduction of pulseaudio and systemd 
have been difficult. Now, the introduction of btrfs as standard 
filesystem is planned for the next release. Further, the support 
dropping of the i386 architecture is another problem.


Now, the question which occurs for me is "is it better to switch to 
Debian stable ?". The sublevels (stable, testing, etc.) are not the same 
in Debian and Fedora. For me, it's difficult to understand which are the 
matching sublevels.


At the present state, I think that the switching to Debian stable, with 
the backports option, could be a good choice. Today, I'm not more a big 
software designer, but I'm only a little one.


Many thanks to you for your valuable advice.

Best wishes,
Claude (DJ0OT)


I've recently added wsjtx 2.2.2 to buster-backports. So you can just
install from there, or "apt build-dep wsjtx".


I've compiled WSJT-X for a number of years now on Debian without
significant issues.  I was able to resolve all dependencies from within
the regular repo.

Currently running Debian 10 Buster, fully patched to the current
version.  If you search the forum archives for my callsign you should be
able to see a couple related discussion threads with specific information.

Yesterday I compiled 2.3.0-rc1 on my Debian 10 machine that runs WSJT-X
2.2.2 and encountered no new dependency issues.  So once you get the
initial dependencies met, it becomes smoother sailing.

I am currently working 30M FT8 with a Kenwood TS-590.  No issues
encountered yet.

73, KD0KZE / Paul



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel