Date   

Re: Draws image

Basil Gunn
 

You most likely didn't do a 'sync' after the dd command.

Could you please ssh into your pi from another computer that has email so you can
cut & paste the console output of your dd command and email it to us.

/Basil n7nix

Douglas KI7LIK <KI7LIK.AZ@GMAIL.COM> writes:

I was able to get it to write the image to the sd card. When i start the
boot, it won't boot to login.
The last line in the boot process is
[ 0.957101] ---[ end Kernel panic: not syncing: VFS: Unable to mount fs
on unknown-block(179,2)


Re: Draws image

 

I am suspecting the card may be bad -- is there any way you can burn it using Etcher on a Windows or Mac computer?  (Did you unzip it before copying it?)

If you try dd again, copy the command and output so we can see what happens.


On Sat, Mar 30, 2019 at 9:44 PM Douglas KI7LIK <KI7LIK.AZ@...> wrote:
I used the same pny 32GB card i qas using before, just using a usb adapter rather than a full size sd card adapter.

As far as writing the image, i used the raspbian linux and the getting started steps provided.   The only exception is that for the write command, is used sudo dd.

KI7LIK
Granada Estates Neighborhood Watch

On Sat, Mar 30, 2019, 21:36 John D Hays - K7VE <john@...> wrote:
Please provide the exact steps you followed (program, SDCARD type/size, etc.) -- did you have the program verify the write?

On Sat, Mar 30, 2019 at 8:05 PM Douglas KI7LIK <KI7LIK.AZ@...> wrote:
I was able to get it to write the image to the sd card.  When i start the boot, it won't boot to login.
The last line in the boot process is 
[    0.957101] ---[ end Kernel panic: not syncing: VFS:  Unable to mount fs on unknown-block(179,2)


KI7LIK
Granada Estates Neighborhood Watch



--


John D. Hays
Edmonds, WA
K7VE

   



--


John D. Hays
Edmonds, WA
K7VE

   


Re: Draws image

Douglas
 

I used the same pny 32GB card i qas using before, just using a usb adapter rather than a full size sd card adapter.

As far as writing the image, i used the raspbian linux and the getting started steps provided.   The only exception is that for the write command, is used sudo dd.

KI7LIK
Granada Estates Neighborhood Watch


On Sat, Mar 30, 2019, 21:36 John D Hays - K7VE <john@...> wrote:
Please provide the exact steps you followed (program, SDCARD type/size, etc.) -- did you have the program verify the write?

On Sat, Mar 30, 2019 at 8:05 PM Douglas KI7LIK <KI7LIK.AZ@...> wrote:
I was able to get it to write the image to the sd card.  When i start the boot, it won't boot to login.
The last line in the boot process is 
[    0.957101] ---[ end Kernel panic: not syncing: VFS:  Unable to mount fs on unknown-block(179,2)


KI7LIK
Granada Estates Neighborhood Watch



--


John D. Hays
Edmonds, WA
K7VE

   


Re: Draws image

 

Please provide the exact steps you followed (program, SDCARD type/size, etc.) -- did you have the program verify the write?

On Sat, Mar 30, 2019 at 8:05 PM Douglas KI7LIK <KI7LIK.AZ@...> wrote:
I was able to get it to write the image to the sd card.  When i start the boot, it won't boot to login.
The last line in the boot process is 
[    0.957101] ---[ end Kernel panic: not syncing: VFS:  Unable to mount fs on unknown-block(179,2)


KI7LIK
Granada Estates Neighborhood Watch



--


John D. Hays
Edmonds, WA
K7VE

   


Draws image

Douglas
 

I was able to get it to write the image to the sd card.  When i start the boot, it won't boot to login.
The last line in the boot process is 
[    0.957101] ---[ end Kernel panic: not syncing: VFS:  Unable to mount fs on unknown-block(179,2)


KI7LIK
Granada Estates Neighborhood Watch


Re: gpsd Running But No Satellite Info #gpsd #gps

 

No worries -- a good data point!

On Thu, Mar 28, 2019 at 3:21 PM Tom General via Groups.Io <ke5icx=yahoo.com@groups.io> wrote:
Welp!  Color me stupid.  As it turns out, I inserted the battery backwards on the DRAWS board.  I assumed the FLAT end of the battery is negative and the "button" side was positive. 

Nope...

Reversed the battery and the GPS info come up immediately.

I'm sorry to have bothered this group for such a basic mistake.

Thank you all who helped me.  

73,

Tom



--


John D. Hays
Edmonds, WA
K7VE

   


Re: gpsd Running But No Satellite Info #gpsd #gps

Tom General
 

Welp!  Color me stupid.  As it turns out, I inserted the battery backwards on the DRAWS board.  I assumed the FLAT end of the battery is negative and the "button" side was positive. 

Nope...

Reversed the battery and the GPS info come up immediately.

I'm sorry to have bothered this group for such a basic mistake.

Thank you all who helped me.  

73,

Tom


Re: gpsd Running But No Satellite Info #gpsd #gps

Tom General
 

Will do.  Thanks!

Tom


Re: gpsd Running But No Satellite Info #gpsd #gps

Basil Gunn
 

Tom,
Could you please do the following:
1. Take a close up picture of your DRAWS hat installed on the RPi
- Send as an attachment to my email only.
- In the picture be sure to include the battery & antenna connector.
2. Power down the RPi, take DRAWS board off the RPi & take the battery
out of the DRAWS board.
3. Put DRAWS hat back on the RPi without the battery, power up and run cgps
4. Post results

Thanks,
/Basil

Tom General via Groups.Io <ke5icx=yahoo.com@groups.io> writes:

Hello All,

I tried these two things last night. I even hustled the DRAWS/Pi
outside and placed the GPS in an open spot in my backyard.

I ran cgps, gpsmon, and gpspipe. They all queried gpsd and it responded with the metatag info which everyone says is normal. I left gpsmon on for about an hour and tried cgps several times (it times out after a couple of minutes). No changes.

Is there a way to directly test the antenna hardware? As I've never seen one of these working normally I'm not sure what behavior I should see, excepting just waiting for the screen to come alive with new information.

Also, the cgps never changes from this:


Re: gpsd Running But No Satellite Info #gpsd #gps

Tom General
 

Hello All,

I tried these two things last night.  I even hustled the DRAWS/Pi outside and placed the GPS in an open spot in my backyard.   

I ran cgps, gpsmon, and gpspipe.  They all queried gpsd and it responded with the metatag info which everyone says is normal.  I left gpsmon on for about an hour and tried cgps several times (it times out after a couple of minutes).  No changes.

Is there a way to directly test the antenna hardware?  As I've never seen one of these working normally I'm not sure what behavior I should see, excepting just waiting for the screen to come alive with new information.   

Also, the cgps never changes from this:

┌───────────────────────────────────────────┐┌──────────────────Seen  0/Used  0┐
│ Time:          n/a                        ││    PRN  Elev   Azim   SNR  Use  │
│ Latitude:      n/a                        ││                                 │
│ Longitude:     n/a                        ││                                 │
│ Altitude:      n/a                        ││                                 │
│ Speed:         n/a                        ││                                 │
│ Heading:         n/a                      ││                                 │
│ Climb:         n/a                        ││                                 │
│ Status:         NO FIX (2 secs)           ││                                 │
│ Long Err  (XDOP, EPX):  n/a ,  n/a        ││                                 │
│ Lat Err   (YDOP, EPY):  n/a ,  n/a        ││                                 │
│ Alt Err   (VDOP, EPV):  n/a ,  n/a        ││                                 │
│ 2D Err    (HDOP, CEP):  n/a ,  n/a        ││                                 │
│ 3D Err    (PDOP, SEP):  n/a ,  n/a        ││                                 │
│ Time Err  (TDOP):       n/a               ││                                 │
│ Geo Err   (GDOP):       n/a               ││                                 │
│ Speed Err (EPS):               n/a        ││                                 │
│ Head Err  (EPD):        n/a               ││                                 │
│ Time offset:            n/a               ││                                 │
│ Grid Square:            n/a               ││                                 │
└───────────────────────────────────────────┘└─────────────────────────────────┘
03-27T22:18:13.424Z"}]}
{"class":"WATCH","enable":true,"json":true,"nmea":false,"raw":0,"scaled":false,"timing":false,"split24":false,"pps":false}r":3,"proto_minor"



1. What you are seeing when starting gpsmon is JSON that is coming from gpsd.  It looks right/normal.  If you want to see gps sentences, use the command gpspipe (man gpspipe)
2. Make sure the antenna has a clear view of the sky, and first startup is going to take some time for lock.  Once it has lock, it will store your position in it's memory (which stays as long as you have power applied and/or the battery installed (40 days backup, with power disconnected), and future boot ups will go much quicker.
 

 


Re: Cant compile fldigi on Beta9 #fldigi

Joseph Vilardo
 

Basil

A good idea to not include the alpha releases of fldigi. They change often when Dave is debuging problems.

Joe

On 3/27/2019 5:13 PM, Basil Gunn wrote:

What repository are you using to get 4.1.02.29?
4.1.02.29 is a test release of the .02 version that has an added feature
or features and not yet verified as fully functional. Dave W1HKJ makes
them available for those that want to try them and report what results
they get.

I found them here http://www.w1hkj.com/alpha.
Thanks. I probably will not include alpha version on the DRAWS image.

Next I will try your suggestion and use the script
"n7nix/hfprogs/hf_verchk.sh" and n7nix/hfprogs/hf_verchk.sh -u to update
to the latest stable versions.
You need to increase the swap file before you run the update since it
compiles fldigi.

From a learning point of view I will also try editing the swap file and
try to build the latest alpha of fldigi from source.

I will let you know what happens.

Thanks Basil,

Joe K3JV


I use the script at n7nix/hfprogs/hf_verchk.sh to show the latest
versions of all the hf HAM programs on the DRAWS image. You can use
hf_verchk.sh -u to update all the hf programs to their current
version. They change weekly.

Before you build from source you will need to increase the swap file
size in config file: /etc/dphys-swapfile

Change CONF_SWAPSIZE=100
to
CONF_SWAPSIZE=1000

then reboot.
Verify swap file size with

swapon -s
or run
n7nix/hfprogs/hf_verchk.sh -s

/Basil n7nix


Joseph Vilardo via Groups.Io <jvilardo=verizon.net@groups.io> writes:

The DRAWS beta 9 image comes with FLDIGI-4.0.18 installed. There are
much newer FLDIGI release available so I tried to compile and install
FLDIGI-4.1.02.29 and that failed. I downloaded the
FLDIGI-4.1.02.29.tar.gz to /usr/local/src directory where I also found
the original fldigi-4.0.18.tar.gz The ./configure runs fine and
doesn't show any errors. The "make" command produces an error at the
end of its compile. I was successful in compiling and installing
flamp-2.22.05.12 using the procedure I followed for fldigi. I did un
comment sources file in /etc/apt/sources.list and up dated the apt
package cache with sudo "aptitude update". I also updated "aptitude
install build-essentials" and "aptitude build-dep fldigi"

Has anyone had success with beta 9 and the new fldigi releases?

Following the described procedure above on a plain Raspbian Stretch
current release on a different PI 3B+ I was able to compile and
install FLDIGI-4.1.02.29 without issue.

I am looking for some guidance on how to get the more recent versions
of fldigi installed and operating on DRAWS,


Re: Cant compile fldigi on Beta9 #fldigi

Gayland Gump
 

I suspect that the amount of increase needed was far below what Basil threw out.  I went with 512 and even at the time was thinking that it was probably excessive.  Like I said, I suspect that 256 MB would probably ample and maybe even excessive but since I didn't try it at that level I can't confirm that it would work.  The practical impact of changing to 1000 as I understand it you are allocating about a 1 GB of storage on the SD card to swap space which I believe would rarely ever be required.  On the other hand, what do I know.
Gayland
KG7GCF


On Wed, Mar 27, 2019 at 5:12 PM Joseph Vilardo via Groups.Io <jvilardo=verizon.net@groups.io> wrote:

Gayland

Basil also said to increase the swapfile size. It was set at 100 his advise was to set it to 1000. I did that and the build for fldigi-4.1.01 worked fine no errors this time in the compile.  So now I have fldigi-4.1.01 working and will add FLMSG and the stable release of FLAMP.

Thanks for the help.

Joe K3JV

On 3/26/2019 11:51 PM, Gayland Gump wrote:
I just did a build on the latest stretch raspbian of the a current version of fldigi.  It was necessary to increase the swap space on the current system to get a successful build.  The default swap appears to be 100, I assume MB, I bumped it to 512 which was probably excessive, 256 might have been way more reasonable but that is just a guess on my part.

Gayland
KG7GCF


On Tue, Mar 26, 2019 at 7:18 PM Joseph Vilardo via Groups.Io <jvilardo=verizon.net@groups.io> wrote:
The DRAWS beta 9 image comes with FLDIGI-4.0.18 installed. There are much newer FLDIGI release available so I tried to compile and install FLDIGI-4.1.02.29 and that failed. I downloaded the FLDIGI-4.1.02.29.tar.gz to /usr/local/src directory where I also found the original fldigi-4.0.18.tar.gz  The ./configure runs fine and doesn't show any errors. The "make" command produces an error at the end of its compile. I was successful in compiling and installing flamp-2.22.05.12 using the procedure I followed for fldigi.
I did un comment sources file in /etc/apt/sources.list and up dated the apt package cache with sudo "aptitude update". I also updated "aptitude install build-essentials"  and "aptitude build-dep fldigi"

Has anyone had success with beta 9 and the new fldigi releases? 

Following the described procedure above on a plain Raspbian Stretch current release on a different PI 3B+ I was able to compile and install FLDIGI-4.1.02.29 without issue.

I am looking for some guidance on how to get the more recent versions of fldigi installed and operating on DRAWS,

Thanks,
K3JV


Re: Cant compile fldigi on Beta9 #fldigi

Joseph Vilardo
 

Gayland

Basil also said to increase the swapfile size. It was set at 100 his advise was to set it to 1000. I did that and the build for fldigi-4.1.01 worked fine no errors this time in the compile.  So now I have fldigi-4.1.01 working and will add FLMSG and the stable release of FLAMP.

Thanks for the help.

Joe K3JV

On 3/26/2019 11:51 PM, Gayland Gump wrote:
I just did a build on the latest stretch raspbian of the a current version of fldigi.  It was necessary to increase the swap space on the current system to get a successful build.  The default swap appears to be 100, I assume MB, I bumped it to 512 which was probably excessive, 256 might have been way more reasonable but that is just a guess on my part.

Gayland
KG7GCF


On Tue, Mar 26, 2019 at 7:18 PM Joseph Vilardo via Groups.Io <jvilardo=verizon.net@groups.io> wrote:
The DRAWS beta 9 image comes with FLDIGI-4.0.18 installed. There are much newer FLDIGI release available so I tried to compile and install FLDIGI-4.1.02.29 and that failed. I downloaded the FLDIGI-4.1.02.29.tar.gz to /usr/local/src directory where I also found the original fldigi-4.0.18.tar.gz  The ./configure runs fine and doesn't show any errors. The "make" command produces an error at the end of its compile. I was successful in compiling and installing flamp-2.22.05.12 using the procedure I followed for fldigi.
I did un comment sources file in /etc/apt/sources.list and up dated the apt package cache with sudo "aptitude update". I also updated "aptitude install build-essentials"  and "aptitude build-dep fldigi"

Has anyone had success with beta 9 and the new fldigi releases? 

Following the described procedure above on a plain Raspbian Stretch current release on a different PI 3B+ I was able to compile and install FLDIGI-4.1.02.29 without issue.

I am looking for some guidance on how to get the more recent versions of fldigi installed and operating on DRAWS,

Thanks,
K3JV


Re: Cant compile fldigi on Beta9 #fldigi

Basil Gunn
 

What repository are you using to get 4.1.02.29?
4.1.02.29 is a test release of the .02 version that has an added feature
or features and not yet verified as fully functional. Dave W1HKJ makes
them available for those that want to try them and report what results
they get.

I found them here http://www.w1hkj.com/alpha.
Thanks. I probably will not include alpha version on the DRAWS image.

Next I will try your suggestion and use the script
"n7nix/hfprogs/hf_verchk.sh" and n7nix/hfprogs/hf_verchk.sh -u to update
to the latest stable versions.
You need to increase the swap file before you run the update since it
compiles fldigi.

From a learning point of view I will also try editing the swap file and
try to build the latest alpha of fldigi from source.

I will let you know what happens.

Thanks Basil,

Joe K3JV



I use the script at n7nix/hfprogs/hf_verchk.sh to show the latest
versions of all the hf HAM programs on the DRAWS image. You can use
hf_verchk.sh -u to update all the hf programs to their current
version. They change weekly.

Before you build from source you will need to increase the swap file
size in config file: /etc/dphys-swapfile

Change CONF_SWAPSIZE=100
to
CONF_SWAPSIZE=1000

then reboot.
Verify swap file size with

swapon -s
or run
n7nix/hfprogs/hf_verchk.sh -s

/Basil n7nix


Joseph Vilardo via Groups.Io <jvilardo=verizon.net@groups.io> writes:

The DRAWS beta 9 image comes with FLDIGI-4.0.18 installed. There are
much newer FLDIGI release available so I tried to compile and install
FLDIGI-4.1.02.29 and that failed. I downloaded the
FLDIGI-4.1.02.29.tar.gz to /usr/local/src directory where I also found
the original fldigi-4.0.18.tar.gz The ./configure runs fine and
doesn't show any errors. The "make" command produces an error at the
end of its compile. I was successful in compiling and installing
flamp-2.22.05.12 using the procedure I followed for fldigi. I did un
comment sources file in /etc/apt/sources.list and up dated the apt
package cache with sudo "aptitude update". I also updated "aptitude
install build-essentials" and "aptitude build-dep fldigi"

Has anyone had success with beta 9 and the new fldigi releases?

Following the described procedure above on a plain Raspbian Stretch
current release on a different PI 3B+ I was able to compile and
install FLDIGI-4.1.02.29 without issue.

I am looking for some guidance on how to get the more recent versions
of fldigi installed and operating on DRAWS,


Re: Cant compile fldigi on Beta9 #fldigi

Joseph Vilardo
 

On 3/27/2019 1:30 AM, Basil Gunn wrote:
I download the fldigi source from http://www.w1hkj.com/files
for the DRAWS image which has fldigi version at 4.1.01
What repository are you using to get 4.1.02.29?
4.1.02.29 is a test release of the .02 version that has an added feature or features and not yet verified as fully functional. Dave W1HKJ makes them available for those that want to try them and report what results they get.

I found them here http://www.w1hkj.com/alpha.

I first tried to build on DRAWS  from the stable version fldigi-4.1.02 but couldn't get it to compile properly. I didn't know about expanding the swap file. I then tried the alpha version FLDIGI-4.1.02.29 on a standalone RPi 3B+ and the build went ok and installed without issue.  I then tried a build with fldigi-4.1.02.29 on the DRAWS ver 9 release and as I reported that failed.

Probably more info than you needed but I wanted you know the progression I went through.

Next I will try your suggestion and use the script "n7nix/hfprogs/hf_verchk.sh" and n7nix/hfprogs/hf_verchk.sh -u to update to the latest stable versions.

From a learning point of view I will also try editing the swap file and try to build the latest alpha of fldigi  from source.

I will let you know what happens.

Thanks Basil,

Joe K3JV



I use the script at n7nix/hfprogs/hf_verchk.sh to show the latest
versions of all the hf HAM programs on the DRAWS image. You can use
hf_verchk.sh -u to update all the hf programs to their current
version. They change weekly.

Before you build from source you will need to increase the swap file
size in config file: /etc/dphys-swapfile

Change CONF_SWAPSIZE=100
to
CONF_SWAPSIZE=1000

then reboot.
Verify swap file size with

swapon -s
or run
n7nix/hfprogs/hf_verchk.sh -s

/Basil n7nix


Joseph Vilardo via Groups.Io <jvilardo=verizon.net@groups.io> writes:

The DRAWS beta 9 image comes with FLDIGI-4.0.18 installed. There are
much newer FLDIGI release available so I tried to compile and install
FLDIGI-4.1.02.29 and that failed. I downloaded the
FLDIGI-4.1.02.29.tar.gz to /usr/local/src directory where I also found
the original fldigi-4.0.18.tar.gz The ./configure runs fine and
doesn't show any errors. The "make" command produces an error at the
end of its compile. I was successful in compiling and installing
flamp-2.22.05.12 using the procedure I followed for fldigi. I did un
comment sources file in /etc/apt/sources.list and up dated the apt
package cache with sudo "aptitude update". I also updated "aptitude
install build-essentials" and "aptitude build-dep fldigi"

Has anyone had success with beta 9 and the new fldigi releases?

Following the described procedure above on a plain Raspbian Stretch
current release on a different PI 3B+ I was able to compile and
install FLDIGI-4.1.02.29 without issue.

I am looking for some guidance on how to get the more recent versions
of fldigi installed and operating on DRAWS,


Re: gpsd Running But No Satellite Info #gpsd #gps

Basil Gunn
 

Tom,

I have Beta 9 running for my DRAWS hat.
I don't think you are running the Beta9 image because the image version
is not being displayed from /var/log/udr_install.log file.
My bad. The line wrapped. You are running BETA9 image confirmed.

/Basil


Re: gpsd Running But No Satellite Info #gpsd #gps

Basil Gunn
 

Thank you for providing the output of showudrc.sh.

I have Beta 9 running for my DRAWS hat.
I don't think you are running the Beta9 image because the image version
is not being displayed from /var/log/udr_install.log file.

So far things are working fine with regard to operation. I'm using an
FT-8900 with the DIN 6 and able to successfully run "listen" and
transmit via Xastir, and AX.25 stuff. Yeah!
Excellent!

My problem is with the GPS and gpsd. The service seems to be running
fine, but there's nothing to suggest the gps antenna I got with the
package is picking anything up.
Run program 'cgps' and provide the numbers from 'Seen /Used' in top
right corner. ie. I see Seen 20/Used 9
Are you in a building with a metal roof?
Can you put your gps antenna close to a window.
Verify the gps antenna is tightly screwed onto the sma connector on the
DRAWS hat.

I've included my showurdc output and the strange looking gpsmon
output...
Thanks for that.

I've disabled the bluetooth and recompiled ax.25 suggested in other
postings.
NOT required.

The strange gpsmon token output leaves me to believe I've no loaded something into the Rpi I need to.
The gps daemon loaded & is running OK.

Thanks in advance for your help and for producing such a great product! I'm really enjoying it!

Tom KE5ICX

*
gpsmon
/Basil n7nix


Re: gpsd Running But No Satellite Info #gpsd #gps

 

Hi Tom,

Two things:

1. What you are seeing when starting gpsmon is JSON that is coming from gpsd.  It looks right/normal.  If you want to see gps sentences, use the command gpspipe (man gpspipe)
2. Make sure the antenna has a clear view of the sky, and first startup is going to take some time for lock.  Once it has lock, it will store your position in it's memory (which stays as long as you have power applied and/or the battery installed (40 days backup, with power disconnected), and future boot ups will go much quicker.


On Wed, Mar 27, 2019 at 9:48 AM Tom General via Groups.Io <ke5icx=yahoo.com@groups.io> wrote:
Hello all.

I have Beta 9 running for my DRAWS hat.  So far things are working fine with regard to operation.  I'm using an FT-8900 with the DIN 6 and able to successfully run "listen" and transmit via Xastir, and AX.25 stuff.  Yeah!

My problem is with the GPS and gpsd.  The service seems to be running fine, but there's nothing to suggest the gps antenna I got with the package is picking anything up.  I've included my showurdc output and the strange looking gpsmon output...  I've disabled the bluetooth and recompiled ax.25 suggested in other postings.  The strange gpsmon token output leaves me to believe I've no loaded something into the Rpi I need to.  

Thanks in advance for your help and for producing such a great product!  I'm really enjoying it!

Tom KE5ICX


  • gpsmon
     

    tcp://localhost:2947          JSON slave driver>
    (84) {"class":"VERSION","release":"3.16","rev":"3.16-4","proto_major":3,"proto_minor":11}
    (263) {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttySC0","activated":"201
    9-03-27T12:47:27.071Z","native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00},{"clas
    s":"DEVICE","path":"/dev/pps0","driver":"PPS","activated":"2019-03-27T12:47:27.082Z"}]}
    (122) {"class":"WATCH","enable":true,"json":false,"nmea":false,"raw":2,"scaled":false,"timi
    ng":false,"split24":false,"pps":true}


    pi@draws:~/bin $ sudo ./showudrc.sh
    ==== Sound Card ====
    udrc card number line: card 0: udrc [udrc], device 0: Universal Digital Radio Controller tlv320aic32x4-hifi-0 []
    udrc is sound card #0
    ==== ALSA Controls for Radio Tansmit ====
    LO Driver Gain  L:[-6.00dB]    R:[-6.00dB]
    PCM            L:[-25.00dB]    R:[-25.00dB]
    DAC Playback PT    L:[PTM_P3]    R:[PTM_P3]
    LO Playback CM    [Full Chip CM]
    ==== ALSA Controls for Radio Receive ====
    ADC Level    L:[0.00dB]    R:[0.00dB]
    IN1        L:[Off]        R:[Off]
    IN2        L:[10 kOhm]    R:[10 kOhm]
    ==== Pi Ver ====
     Pi 3 Model B+ Mfg by Sony UK
     Has WiFi
    ==== udrc Ver ====
    Found a DRAWS

         HAT ID EEPROM
    Name:        hat
    Product:     Digital Radio Amateur Work Station
    Product ID:  0x0004
    Product ver: 0x0204
    UUID:        d9890635-8955-4610-95ba-3a7ebd43b642
    Vendor:      NW Digital Radio

    ==== sys Ver ====
    ----- image version
    2019 02 27 12:34:54 PST: SD image version: beta9
    ----- /proc/version
    Linux version 4.14.98-v7+ (dom@dom-XPS-13-9370) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1200 SMP Tue Feb 12 20:27:48 GMT 2019

    ----- /etc/*version: 9.8

    ----- /etc/*release
    PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
    NAME="Raspbian GNU/Linux"
    VERSION_ID="9"
    VERSION="9 (stretch)"
    ID=raspbian
    ID_LIKE=debian
    HOME_URL="http://www.raspbian.org/"
    SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
    BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

    ----- lsb_release
    ./showudrc.sh: line 375: lsb_release: command not found

    ---- systemd
       Static hostname: draws
             Icon name: computer
            Machine ID: 2f51e140e908474eaa86ae805f03a6d8
               Boot ID: d99ef32aaf944e0f9d23b2e2e51b4e8a
      Operating System: Raspbian GNU/Linux 9 (stretch)
                Kernel: Linux 4.14.98-v7+
          Architecture: arm

    ---- modules
    tlv320aic32x4_i2c      16384  1
    tlv320aic32x4          32768  1 tlv320aic32x4_i2c
    udrc                   16384  2
    snd_soc_core          188416  3 tlv320aic32x4,snd_soc_bcm2835_i2s,udrc
    snd_pcm                98304  6 snd_pcm_dmaengine,tlv320aic32x4,snd_soc_bcm2835_i2s,snd_soc_core

    -rw-r--r-- 1 root  6388 Feb 26 17:24 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-i2c.ko
    -rw-r--r-- 1 root 39084 Feb 26 17:24 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4.ko
    -rw-r--r-- 1 root  6408 Feb 26 17:24 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-spi.ko
    -rw-r--r-- 1 root  8332 Feb 26 17:24 /lib/modules/4.14.98-v7+/updates/dkms/udrc.ko

    ---- kernel
    ||/ Name               Version      Architecture Description
    +++-==================-============-============-=================================
    ii  raspberrypi-kernel 1.20190215-1 armhf        Raspberry Pi bootloader
    ii  udrc-dkms          1.0.5        armhf        DKMS source for the UDRC driver

    Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay

    ---- syslog
    Mar 27 07:47:24 draws kernel: [    2.912481] udrc: loading out-of-tree module taints kernel.
    Mar 27 07:47:24 draws kernel: [    2.913017] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
    Mar 27 07:47:24 draws kernel: [    2.913026] snd-udrc soc:sound: snd_soc_register_card() failed: -517
    Mar 27 07:47:24 draws kernel: [    2.982732] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
    Mar 27 07:47:24 draws kernel: [    2.982744] snd-udrc soc:sound: snd_soc_register_card() failed: -517
    Mar 27 07:47:24 draws kernel: [    3.037491] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
    Mar 27 07:47:24 draws kernel: [    3.037502] snd-udrc soc:sound: snd_soc_register_card() failed: -517
    Mar 27 07:47:24 draws kernel: [    3.042634] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
    Mar 27 07:47:24 draws kernel: [    3.042640] snd-udrc soc:sound: snd_soc_register_card() failed: -517
    Mar 27 07:47:24 draws kernel: [    3.180273] snd-udrc soc:sound: tlv320aic32x4-hifi <-> 3f203000.i2s mapping ok
    Mar 27 07:47:25 draws bash[407]: UDRC_PROD: Digital Radio Amateur Work Station, ID: 4
    Mar 27 07:47:25 draws bash[407]: UDRC II or DRAWS installed
    Mar 27 07:47:25 draws bash[407]: using mkiss with UDRC II and pseudo term_1: /dev/pts/2 pseudo term_2: /dev/pts/3

    ---- compass
    Compass preference file not found: /etc/apt/preferences.d/compass
    ---- compass apt sources list file
    deb [arch=armhf,amd64] http://archive.compasslinux.org/ cedar main
    ---- compass package files
    -rw-r--r-- 1 root  2201 Dec 31 12:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_InRelease
    -rw-r--r-- 1 root 17567 Jul  2  2018 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-amd64_Packages
    -rw-r--r-- 1 root 43316 Dec 31 12:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-armhf_Packages

    ----- Dire Wolf DEVELOPMENT version 1.6 B (Feb 27 2019)

    ==== Filesystem ====
    /dev/root        15G  5.0G  8.6G  37% /

    ==== boot config ====
    #dtparam=i2c_arm=on
    #dtparam=i2s=on
    #dtparam=spi=on

    # Uncomment this to enable the lirc-rpi module
    #dtoverlay=lirc-rpi

    # Additional overlays and parameters are documented /boot/overlays/README

    # Enable audio (loads snd_bcm2835)
    # dtparam=audio=on

    force_turbo=1
    dtoverlay=
    dtoverlay=draws

    ---- gpsd
    ● gpsd.service - GPS (Global Positioning System) Daemon
       Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
       Active: active (running) since Wed 2019-03-27 07:47:26 CDT; 34min ago
     Main PID: 590 (gpsd)
       CGroup: /system.slice/gpsd.service
               └─590 /usr/sbin/gpsd -N -n /dev/ttySC0 /dev/pps0

    Mar 27 07:47:26 draws systemd[1]: Started GPS (Global Positioning System) Daemon.

    ---- chrony
    ● gpsd.service - GPS (Global Positioning System) Daemon
       Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
       Active: active (running) since Wed 2019-03-27 07:47:26 CDT; 34min ago
     Main PID: 590 (gpsd)
       CGroup: /system.slice/gpsd.service
               └─590 /usr/sbin/gpsd -N -n /dev/ttySC0 /dev/pps0

    Mar 27 07:47:26 draws systemd[1]: Started GPS (Global Positioning System) Daemon.
    crw-rw---- 1 root root    243, 0 Mar 27 07:47 /dev/pps0
    crw------- 1 root root    243, 1 Mar 27 07:47 /dev/pps1
    crw-rw---- 1 root dialout 242, 0 Mar 27 07:47 /dev/ttySC0
    crw-rw---- 1 root dialout 242, 1 Mar 27 07:47 /dev/ttySC1
    -- chrony sources
    210 Number of sources = 6
    MS Name/IP address         Stratum Poll Reach LastRx Last sample               
    ===============================================================================
    #? GPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
    #? PPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
    ^- ntp.xtom.com                  2   8   377    75  -11830s[-11830s] +/-   60ms
    ^- time.richiemcintosh.com       2   8   377    72  -11830s[-11830s] +/-   70ms
    ^- time.no-such-agency.net       2   8   377   138  -11830s[-11830s] +/-   52ms
    ^- ns3.weiszhosting.com          2   7   377     9  -11830s[-11830s] +/-   79ms
    -- chrony tracking
    Reference ID    : 00000000 ()
    Stratum         : 0
    Ref time (UTC)  : Thu Jan 01 00:00:00 1970
    System time     : 0.000000020 seconds fast of NTP time
    Last offset     : +0.000000000 seconds
    RMS offset      : 0.000000000 seconds
    Frequency       : 9.928 ppm fast
    Residual freq   : +0.000 ppm
    Skew            : 0.000 ppm
    Root delay      : 1.000000 seconds
    Root dispersion : 1.000000 seconds
    Update interval : 0.0 seconds
    Leap status     : Not synchronised
    -- chrony sourcestats
    210 Number of sources = 6
    Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
    ==============================================================================
    GPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
    PPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
    ntp.xtom.com               22  11   29m     -0.534      0.991  -11830s   559us
    time.richiemcintosh.com    24  12   32m     -0.501      0.543  -11830s   351us
    time.no-such-agency.net    25  13   31m     -0.634      0.346  -11830s   246us
    ns3.weiszhosting.com        6   3   649     +2.857     18.273  -11830s  1162us

    ---- sensors
    -rw-r--r-- 1 root root 171 Nov 11 13:39 /etc/sensors.d/draws
    ads1015-i2c-1-48
    Adapter: bcm2835 I2C adapter
    User ADC Differential:  +0.00 V  
    +12V:                  +13.84 V  
    User ADC 1:             +0.00 V  
    User ADC 2:             +0.00 V  

    ---- locale
    Locale country codes consistent between WiFi & X11, US


     
     
    •  
    •  
    •  
    •  

 
 
 
 
 
 
 
 



--


John D. Hays
Edmonds, WA
K7VE

   


gpsd Running But No Satellite Info #gpsd #gps

Tom General
 

Hello all.

I have Beta 9 running for my DRAWS hat.  So far things are working fine with regard to operation.  I'm using an FT-8900 with the DIN 6 and able to successfully run "listen" and transmit via Xastir, and AX.25 stuff.  Yeah!

My problem is with the GPS and gpsd.  The service seems to be running fine, but there's nothing to suggest the gps antenna I got with the package is picking anything up.  I've included my showurdc output and the strange looking gpsmon output...  I've disabled the bluetooth and recompiled ax.25 suggested in other postings.  The strange gpsmon token output leaves me to believe I've no loaded something into the Rpi I need to.  

Thanks in advance for your help and for producing such a great product!  I'm really enjoying it!

Tom KE5ICX


  • gpsmon
     

    tcp://localhost:2947          JSON slave driver>
    (84) {"class":"VERSION","release":"3.16","rev":"3.16-4","proto_major":3,"proto_minor":11}
    (263) {"class":"DEVICES","devices":[{"class":"DEVICE","path":"/dev/ttySC0","activated":"201
    9-03-27T12:47:27.071Z","native":0,"bps":9600,"parity":"N","stopbits":1,"cycle":1.00},{"clas
    s":"DEVICE","path":"/dev/pps0","driver":"PPS","activated":"2019-03-27T12:47:27.082Z"}]}
    (122) {"class":"WATCH","enable":true,"json":false,"nmea":false,"raw":2,"scaled":false,"timi
    ng":false,"split24":false,"pps":true}


    pi@draws:~/bin $ sudo ./showudrc.sh
    ==== Sound Card ====
    udrc card number line: card 0: udrc [udrc], device 0: Universal Digital Radio Controller tlv320aic32x4-hifi-0 []
    udrc is sound card #0
    ==== ALSA Controls for Radio Tansmit ====
    LO Driver Gain  L:[-6.00dB]    R:[-6.00dB]
    PCM            L:[-25.00dB]    R:[-25.00dB]
    DAC Playback PT    L:[PTM_P3]    R:[PTM_P3]
    LO Playback CM    [Full Chip CM]
    ==== ALSA Controls for Radio Receive ====
    ADC Level    L:[0.00dB]    R:[0.00dB]
    IN1        L:[Off]        R:[Off]
    IN2        L:[10 kOhm]    R:[10 kOhm]
    ==== Pi Ver ====
     Pi 3 Model B+ Mfg by Sony UK
     Has WiFi
    ==== udrc Ver ====
    Found a DRAWS

         HAT ID EEPROM
    Name:        hat
    Product:     Digital Radio Amateur Work Station
    Product ID:  0x0004
    Product ver: 0x0204
    UUID:        d9890635-8955-4610-95ba-3a7ebd43b642
    Vendor:      NW Digital Radio

    ==== sys Ver ====
    ----- image version
    2019 02 27 12:34:54 PST: SD image version: beta9
    ----- /proc/version
    Linux version 4.14.98-v7+ (dom@dom-XPS-13-9370) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1200 SMP Tue Feb 12 20:27:48 GMT 2019

    ----- /etc/*version: 9.8

    ----- /etc/*release
    PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
    NAME="Raspbian GNU/Linux"
    VERSION_ID="9"
    VERSION="9 (stretch)"
    ID=raspbian
    ID_LIKE=debian
    HOME_URL="http://www.raspbian.org/"
    SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
    BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

    ----- lsb_release
    ./showudrc.sh: line 375: lsb_release: command not found

    ---- systemd
       Static hostname: draws
             Icon name: computer
            Machine ID: 2f51e140e908474eaa86ae805f03a6d8
               Boot ID: d99ef32aaf944e0f9d23b2e2e51b4e8a
      Operating System: Raspbian GNU/Linux 9 (stretch)
                Kernel: Linux 4.14.98-v7+
          Architecture: arm

    ---- modules
    tlv320aic32x4_i2c      16384  1
    tlv320aic32x4          32768  1 tlv320aic32x4_i2c
    udrc                   16384  2
    snd_soc_core          188416  3 tlv320aic32x4,snd_soc_bcm2835_i2s,udrc
    snd_pcm                98304  6 snd_pcm_dmaengine,tlv320aic32x4,snd_soc_bcm2835_i2s,snd_soc_core

    -rw-r--r-- 1 root  6388 Feb 26 17:24 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-i2c.ko
    -rw-r--r-- 1 root 39084 Feb 26 17:24 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4.ko
    -rw-r--r-- 1 root  6408 Feb 26 17:24 /lib/modules/4.14.98-v7+/updates/dkms/tlv320aic32x4-spi.ko
    -rw-r--r-- 1 root  8332 Feb 26 17:24 /lib/modules/4.14.98-v7+/updates/dkms/udrc.ko

    ---- kernel
    ||/ Name               Version      Architecture Description
    +++-==================-============-============-=================================
    ii  raspberrypi-kernel 1.20190215-1 armhf        Raspberry Pi bootloader
    ii  udrc-dkms          1.0.5        armhf        DKMS source for the UDRC driver

    Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay

    ---- syslog
    Mar 27 07:47:24 draws kernel: [    2.912481] udrc: loading out-of-tree module taints kernel.
    Mar 27 07:47:24 draws kernel: [    2.913017] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
    Mar 27 07:47:24 draws kernel: [    2.913026] snd-udrc soc:sound: snd_soc_register_card() failed: -517
    Mar 27 07:47:24 draws kernel: [    2.982732] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
    Mar 27 07:47:24 draws kernel: [    2.982744] snd-udrc soc:sound: snd_soc_register_card() failed: -517
    Mar 27 07:47:24 draws kernel: [    3.037491] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
    Mar 27 07:47:24 draws kernel: [    3.037502] snd-udrc soc:sound: snd_soc_register_card() failed: -517
    Mar 27 07:47:24 draws kernel: [    3.042634] snd-udrc soc:sound: ASoC: CODEC DAI tlv320aic32x4-hifi not registered - will retry
    Mar 27 07:47:24 draws kernel: [    3.042640] snd-udrc soc:sound: snd_soc_register_card() failed: -517
    Mar 27 07:47:24 draws kernel: [    3.180273] snd-udrc soc:sound: tlv320aic32x4-hifi <-> 3f203000.i2s mapping ok
    Mar 27 07:47:25 draws bash[407]: UDRC_PROD: Digital Radio Amateur Work Station, ID: 4
    Mar 27 07:47:25 draws bash[407]: UDRC II or DRAWS installed
    Mar 27 07:47:25 draws bash[407]: using mkiss with UDRC II and pseudo term_1: /dev/pts/2 pseudo term_2: /dev/pts/3

    ---- compass
    Compass preference file not found: /etc/apt/preferences.d/compass
    ---- compass apt sources list file
    deb [arch=armhf,amd64] http://archive.compasslinux.org/ cedar main
    ---- compass package files
    -rw-r--r-- 1 root  2201 Dec 31 12:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_InRelease
    -rw-r--r-- 1 root 17567 Jul  2  2018 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-amd64_Packages
    -rw-r--r-- 1 root 43316 Dec 31 12:44 /var/lib/apt/lists/archive.compasslinux.org_dists_cedar_main_binary-armhf_Packages

    ----- Dire Wolf DEVELOPMENT version 1.6 B (Feb 27 2019)

    ==== Filesystem ====
    /dev/root        15G  5.0G  8.6G  37% /

    ==== boot config ====
    #dtparam=i2c_arm=on
    #dtparam=i2s=on
    #dtparam=spi=on

    # Uncomment this to enable the lirc-rpi module
    #dtoverlay=lirc-rpi

    # Additional overlays and parameters are documented /boot/overlays/README

    # Enable audio (loads snd_bcm2835)
    # dtparam=audio=on

    force_turbo=1
    dtoverlay=
    dtoverlay=draws

    ---- gpsd
    ● gpsd.service - GPS (Global Positioning System) Daemon
       Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
       Active: active (running) since Wed 2019-03-27 07:47:26 CDT; 34min ago
     Main PID: 590 (gpsd)
       CGroup: /system.slice/gpsd.service
               └─590 /usr/sbin/gpsd -N -n /dev/ttySC0 /dev/pps0

    Mar 27 07:47:26 draws systemd[1]: Started GPS (Global Positioning System) Daemon.

    ---- chrony
    ● gpsd.service - GPS (Global Positioning System) Daemon
       Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
       Active: active (running) since Wed 2019-03-27 07:47:26 CDT; 34min ago
     Main PID: 590 (gpsd)
       CGroup: /system.slice/gpsd.service
               └─590 /usr/sbin/gpsd -N -n /dev/ttySC0 /dev/pps0

    Mar 27 07:47:26 draws systemd[1]: Started GPS (Global Positioning System) Daemon.
    crw-rw---- 1 root root    243, 0 Mar 27 07:47 /dev/pps0
    crw------- 1 root root    243, 1 Mar 27 07:47 /dev/pps1
    crw-rw---- 1 root dialout 242, 0 Mar 27 07:47 /dev/ttySC0
    crw-rw---- 1 root dialout 242, 1 Mar 27 07:47 /dev/ttySC1
    -- chrony sources
    210 Number of sources = 6
    MS Name/IP address         Stratum Poll Reach LastRx Last sample               
    ===============================================================================
    #? GPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
    #? PPS                           0   3     0     -     +0ns[   +0ns] +/-    0ns
    ^- ntp.xtom.com                  2   8   377    75  -11830s[-11830s] +/-   60ms
    ^- time.richiemcintosh.com       2   8   377    72  -11830s[-11830s] +/-   70ms
    ^- time.no-such-agency.net       2   8   377   138  -11830s[-11830s] +/-   52ms
    ^- ns3.weiszhosting.com          2   7   377     9  -11830s[-11830s] +/-   79ms
    -- chrony tracking
    Reference ID    : 00000000 ()
    Stratum         : 0
    Ref time (UTC)  : Thu Jan 01 00:00:00 1970
    System time     : 0.000000020 seconds fast of NTP time
    Last offset     : +0.000000000 seconds
    RMS offset      : 0.000000000 seconds
    Frequency       : 9.928 ppm fast
    Residual freq   : +0.000 ppm
    Skew            : 0.000 ppm
    Root delay      : 1.000000 seconds
    Root dispersion : 1.000000 seconds
    Update interval : 0.0 seconds
    Leap status     : Not synchronised
    -- chrony sourcestats
    210 Number of sources = 6
    Name/IP Address            NP  NR  Span  Frequency  Freq Skew  Offset  Std Dev
    ==============================================================================
    GPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
    PPS                         0   0     0     +0.000   2000.000     +0ns  4000ms
    ntp.xtom.com               22  11   29m     -0.534      0.991  -11830s   559us
    time.richiemcintosh.com    24  12   32m     -0.501      0.543  -11830s   351us
    time.no-such-agency.net    25  13   31m     -0.634      0.346  -11830s   246us
    ns3.weiszhosting.com        6   3   649     +2.857     18.273  -11830s  1162us

    ---- sensors
    -rw-r--r-- 1 root root 171 Nov 11 13:39 /etc/sensors.d/draws
    ads1015-i2c-1-48
    Adapter: bcm2835 I2C adapter
    User ADC Differential:  +0.00 V  
    +12V:                  +13.84 V  
    User ADC 1:             +0.00 V  
    User ADC 2:             +0.00 V  

    ---- locale
    Locale country codes consistent between WiFi & X11, US


     
     
    •  
    •  
    •  
    •  

 
 
 
 
 
 
 
 


Re: Cant compile fldigi on Beta9 #fldigi

Basil Gunn
 

I download the fldigi source from http://www.w1hkj.com/files
for the DRAWS image which has fldigi version at 4.1.01
What repository are you using to get 4.1.02.29?

I use the script at n7nix/hfprogs/hf_verchk.sh to show the latest
versions of all the hf HAM programs on the DRAWS image. You can use
hf_verchk.sh -u to update all the hf programs to their current
version. They change weekly.

Before you build from source you will need to increase the swap file
size in config file: /etc/dphys-swapfile

Change CONF_SWAPSIZE=100
to
CONF_SWAPSIZE=1000

then reboot.
Verify swap file size with

swapon -s
or run
n7nix/hfprogs/hf_verchk.sh -s

/Basil n7nix


Joseph Vilardo via Groups.Io <jvilardo=verizon.net@groups.io> writes:

The DRAWS beta 9 image comes with FLDIGI-4.0.18 installed. There are
much newer FLDIGI release available so I tried to compile and install
FLDIGI-4.1.02.29 and that failed. I downloaded the
FLDIGI-4.1.02.29.tar.gz to /usr/local/src directory where I also found
the original fldigi-4.0.18.tar.gz The ./configure runs fine and
doesn't show any errors. The "make" command produces an error at the
end of its compile. I was successful in compiling and installing
flamp-2.22.05.12 using the procedure I followed for fldigi. I did un
comment sources file in /etc/apt/sources.list and up dated the apt
package cache with sudo "aptitude update". I also updated "aptitude
install build-essentials" and "aptitude build-dep fldigi"

Has anyone had success with beta 9 and the new fldigi releases?

Following the described procedure above on a plain Raspbian Stretch
current release on a different PI 3B+ I was able to compile and
install FLDIGI-4.1.02.29 without issue.

I am looking for some guidance on how to get the more recent versions
of fldigi installed and operating on DRAWS,

2401 - 2420 of 5337