Topics

Ran update.. now PI won't boot #draws

Kevin K. - N7KJK
 

Hi, 
Ran through the following and now the PI won't boot.  Does not even appear to try.  This is a PI 3.  I did enable the HDMI Safe flag just in case it would help. 

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

There were no errors during this process, there were no unexpected results. All the stages seemed to complete as they should.
This was a working RMS gateway, which took me a long time to get working...
Anyone have any thoughts before I reformat the SD card and start over.??..

Kevin
N7KJK

Basil Gunn
 

I wouldn't reformat the SD card & start over. Technically you don't
reformat the SD card you just write a sector by sector image.

What exactly are your symptoms?
Is it that your RPi monitor didn't initialize properly so your screen is
blank?
Can you ssh into your RPi?
Get a second mSD card put plain Raspbian or the latest NWDR16 image on
it. Does it show the same symptom?


Kevin K. - N7KJK <kkutzera@...> writes:

Hi, Ran through the following and now the PI won't boot. Does not even
appear to try. This is a PI 3. I did enable the HDMI Safe flag just in
case it would help.

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

There were no errors during this process, there were no unexpected results. All the stages seemed to complete as they should.
This was a working RMS gateway, which took me a long time to get working...
Anyone have any thoughts before I reformat the SD card and start over.??..

Kevin
N7KJK

Kevin K. - N7KJK
 

Hey Basil, 
Hope you're doing well.. 

So I've had the RMS gateway running smoothly for months.  There was a power failure event here some weeks ago.  Power came back on , PI and radio booted up and everything seemed fine.  Then one of my friends noticed they couldn't get message through my system anymore. Also noticed on the sysops log that there were no messages through my system for the past couple weeks.   I ran some tests and listened to the frequency on another radio, and had another friend attempt a message.  Apparently my system was opening the frequency , but not creating any decodable sound to establish a connection. I did a test wl2kax25 to a non-existent call sign to listen and the output did sound strange..  almost muddy.. not typical digital tones.

So i went through the update process since it had been a while just to get a clean base line system.  Now it doesn't boot.. symptoms are, well, nothing.  No display change at all , as if the PI was still powered down,  I checked the SD card in my PC, and it seems to be OK.  edited the config.txt file and uncommented the HDMI security flag...  (this is a PI 3b not a 4)..   

I was working on creating a new beta16 (in anticipation of my new DRAWS), so I'll try to boot this unit to that image later today.  I'll also try and boot the PI without a DRAWS on it as another test.   

I'm hoping that the power failure (and subsequent power restoration) did somehow tweak the sound card, or something..  It seems to me the unit would either be completely fried by a surge, or completely unharmed...

I'll update this thread with whatever interesting information I come up with.  

73
Kevin










On Mon, Jul 6, 2020 at 10:20 PM Basil Gunn <basil@...> wrote:

I wouldn't reformat the SD card & start over. Technically you don't
reformat the SD card you just write a sector by sector image.

What exactly are your symptoms?
Is it that your RPi monitor didn't initialize properly so your screen is
blank?
Can you ssh into your RPi?
Get a second mSD card put plain Raspbian or the latest NWDR16 image on
it. Does it show the same symptom?


Kevin K. - N7KJK <kkutzera@...> writes:

> Hi, Ran through the following and now the PI won't boot. Does not even
> appear to try. This is a PI 3. I did enable the HDMI Safe flag just in
> case it would help.
>
> sudo apt-get update
> sudo apt-get dist-upgrade
> cd
> cd n7nix
> git pull
> cd config
> ./bin_refresh.sh
>
> There were no errors during this process, there were no unexpected results. All the stages seemed to complete as they should.
> This was a working RMS gateway, which took me a long time to get working...
> Anyone have any thoughts before I reformat the SD card and start over.??..
>
> Kevin
> N7KJK





--
Kevin J. Kutzera CISSP, CISM, CEH
Cell: 206-850-7762

 

Having been burned too many times from power events and SDCARD failures:

Once you have it running, archive a copy of the image.

For infrastructure, like Echolink and RMS Gateways, we burn a second SDCARD and tape it to the unit.

Upgrades, particularly dist-upgrades, are another time to save your hard work.

Basil has bailed me out a couple of times, but I’m getting more religious about backups.

Bryan K7UDR

Basil Gunn
 

Hi Kevin,
I can help you get your RMS Gateway running from a clean install if it
comes down to that.

From your description it sounds like the ALSA settings for your
particular radio changed at some point.

Try to ssh into your RPi from another computer that would give a good
data point.

I'll try to boot this unit to that image later today. I'll also try
and boot the PI without a DRAWS on it as another test.
Yes, both good ideas.

I'll update this thread with whatever interesting information I come up
with.
Thanks.

Kevin K. - N7KJK <kkutzera@...> writes:

Hey Basil,
Hope you're doing well..

So I've had the RMS gateway running smoothly for months. There was a power
failure event here some weeks ago. Power came back on , PI and radio
booted up and everything seemed fine. Then one of my friends noticed they
couldn't get message through my system anymore. Also noticed on the sysops
log that there were no messages through my system for the past couple
weeks. I ran some tests and listened to the frequency on another radio,
and had another friend attempt a message. Apparently my system was opening
the frequency , but not creating any decodable sound to establish a
connection. I did a test wl2kax25 to a non-existent call sign to listen and
the output did sound strange.. almost muddy.. not typical digital tones.

So i went through the update process since it had been a while just to get
a clean base line system. Now it doesn't boot.. symptoms are, well,
nothing. No display change at all , as if the PI was still powered down,
I checked the SD card in my PC, and it seems to be OK. edited the
config.txt file and uncommented the HDMI security flag... (this is a PI 3b
not a 4)..

I was working on creating a new beta16 (in anticipation of my new DRAWS),
so I'll try to boot this unit to that image later today. I'll also try and
boot the PI without a DRAWS on it as another test.

I'm hoping that the power failure (and subsequent power restoration) did
somehow tweak the sound card, or something.. It seems to me the unit would
either be completely fried by a surge, or completely unharmed...

I'll update this thread with whatever interesting information I come up
with.

73
Kevin










On Mon, Jul 6, 2020 at 10:20 PM Basil Gunn <@basil860> wrote:


I wouldn't reformat the SD card & start over. Technically you don't
reformat the SD card you just write a sector by sector image.

What exactly are your symptoms?
Is it that your RPi monitor didn't initialize properly so your screen is
blank?
Can you ssh into your RPi?
Get a second mSD card put plain Raspbian or the latest NWDR16 image on
it. Does it show the same symptom?


Kevin K. - N7KJK <kkutzera@...> writes:

Hi, Ran through the following and now the PI won't boot. Does not even
appear to try. This is a PI 3. I did enable the HDMI Safe flag just in
case it would help.

sudo apt-get update
sudo apt-get dist-upgrade
cd
cd n7nix
git pull
cd config
./bin_refresh.sh

There were no errors during this process, there were no unexpected
results. All the stages seemed to complete as they should.
This was a working RMS gateway, which took me a long time to get
working...
Anyone have any thoughts before I reformat the SD card and start
over.??..

Kevin
N7KJK


Kevin K. - N7KJK
 

Thanks Basil., 
Can't SSH to the PI.  Doesn't appear to be on the network, I really think it's not booting.  SD card in another PI equals same results (nothing). 
New SD card boots just fine with DRAWS.. Clearly something weird happened to this SD card. 

I appreciate your offer of help to get new gateway up and running.  
If you wouldn't mine a brief outline of the higher level steps I'll use that and the history from our previous support thread and get back in working order. 
I did keep notes on config files, and things....  I'll start with the getting started document..  

The practice at setting this up will do me good.  I'm trying to move from a "documentation follower"  ,  up to someone that actually understands what I'm doing. . . 
I will certainly reach out if I run into something that doesn't follow with the documentation.

Kevin   N7KJK

Kevin K. - N7KJK
 

OK so I think I'm really close to working system. (unless we really have a hardware issue which I don't think so).  
A friend is trying to connect when I ask.  I've been working on audio levels because I think everything else is working.  
In our most recent tests we'll get what I think is a brief connection, but something drops it out before there's any data sent. 
I'm using a Yaesu FT-7800 with the 6-pin connected to udr1 (the socket closest to the clock battery). 

Hopefully something really stands out as incorrect here.  


This is from the listen command......
000  N7KJK-10 Linux RMS Gateway 2.5.1, Kenmore, WA.
udr1: fm N7KJK-10 to K7RMZ ctl DISC+ 
udr1: fm K7RMZ to N7KJK-10 ctl SABM+ 
udr1: fm N7KJK-10 to K7RMZ ctl DM- 
udr1: fm N7KJK-10 to K7RMZ ctl DISC+ 
udr1: fm K7RMZ to N7KJK-10 ctl RR2- 
udr1: fm K7RMZ to N7KJK-10 ctl UA- 
udr1: fm K7RMZ to N7KJK-10 ctl DM- 
 

Here's the output of showudrc.sh
 
pi@N7KJK-PI:~ $ showudrc.sh
==== Sound Card ====
udrc card number line: card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #2
==== ALSA Controls for Radio Tansmit ====
LO Driver Gain  L:[-6.00dB]     R:[-6.00dB]
PCM             L:[-20.00dB]    R:[-20.00dB]
DAC Playback PT L:[P1]  R:[P1]
LO Playback CM  [Full Chip]
==== ALSA Controls for Radio Receive ====
ADC Level       L:[-2.00dB]     R:[-2.00dB]
IN1             L:[Off]         R:[Off]
IN2             L:[10 kOhm]     R:[10 kOhm]
 
==== Pi Ver ====
 Pi 3 Model B, Rev 1.2, Mfg by Embest
 Has WiFi
 
==== Pi Firmware VideoCore Ver ====
Apr 15 2020 11:43:08
Copyright (c) 2012 Broadcom
version 82f9bb929ce2186eb1824178c1ae82902ad6275c (clean) (release) (start)
 
==== Pi Firmware EEPROM Ver ====
error=1 error_msg="Command not registered"
 
==== Pi Firmware EEPROM Config ====
error=1 error_msg="Command not registered"
 
==== udrc Ver ====
Found a DRAWS
 
     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0305
UUID:        21c8d4ee-2b1b-4570-bb39-d9da8d8876ae
Vendor:      NW Digital Radio
 
==== sys Ver ====
----- image version
2020 06 08 11:50:00 PDT: SD image version: nwdr16
----- /proc/version
Linux version 4.19.118-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1311 SMP Mon Apr 27 14:21:24 BST 2020
 
----- /etc/*version: 10.4
 
----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
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
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 10 (buster)
Release:        10
Codename:       buster
 
---- systemd
   Static hostname: N7KJK-PI
         Icon name: computer
        Machine ID: 27ac1f0c20904cb7a960920e966db545
           Boot ID: ac173e148e5f4c249be834f1048b156b
  Operating System: Raspbian GNU/Linux 10 (buster)
            Kernel: Linux 4.19.118-v7+
      Architecture: arm
 
---- modules
snd_soc_tlv320aic32x4_i2c    16384  171
snd_soc_tlv320aic32x4    40960  1 snd_soc_tlv320aic32x4_i2c
snd_soc_core          192512  4 snd_soc_simple_card_utils,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_simple_card
snd_pcm               102400  7 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core
snd                    73728  16 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core,snd_pcm
 
---- kernel
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version      Architecture Description
+++-==================-============-============-=================================
ii  raspberrypi-kernel 1.20200601-1 armhf        Raspberry Pi bootloader
 
---- Codec drivers
Found: snd-soc-tlv320aic32x4-i2c.ko, OK
Found: snd-soc-tlv320aic32x4.ko, OK
Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay
 
---- syslog
 
---- dmesg
 
 
----- Dire Wolf DEVELOPMENT version 1.6 E (May 11 2020)
 
==== Filesystem ====
/dev/root        30G  5.2G   23G  19% /
 
==== boot config ====
 
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
 
[all]
#dtoverlay=vc4-fkms-v3d
 
# Flush all overlays, ie. deprecated overlays loaded from eeprom
dtoverlay=
# enable udrc/draws if no eeprom
dtoverlay=draws,alsaname=udrc
force_turbo=1
# Enable audio (loads snd_bcm2835)
dtparam=audio=on
 
---- gpsd
/usr/local/sbin/gpsd
gpsd: 3.20 (revision 3.20)
● gpsd.service - GPS (Global Positioning System) Daemon
   Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2020-07-08 10:15:31 PDT; 6h ago
 Main PID: 601 (gpsd)
    Tasks: 3 (limit: 2200)
   Memory: 1.7M
   CGroup: /system.slice/gpsd.service
           └─601 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
 
Jul 08 10:15:31 N7KJK-PI systemd[1]: Starting GPS (Global Positioning Syste…n...
Jul 08 10:15:31 N7KJK-PI systemd[1]: Started GPS (Global Positioning System…mon.
Hint: Some lines were ellipsized, use -l to show in full.
 
---- chrony
crw-rw---- 1 root root    241, 0 Jul  8 10:15 /dev/pps0
crw------- 1 root root    241, 1 Jul  8 10:15 /dev/pps1
crw-rw---- 1 root dialout 239, 0 Jul  8 10:15 /dev/ttySC0
crw-rw---- 1 root dialout 239, 1 Jul  8 10:15 /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
^+ 12.167.151.1                  3  10   377   323  -3228us[-3621us] +/-  146ms
^+ ns1.backplanedns.org          2  10   377   438  -8191us[-8582us] +/-  133ms
^* 198-20-172-38-host.coloc>     2  10   377   168  -4019us[-4415us] +/-   85ms
^+ acheron.bitsrc.net            3  10   377   493  -2819us[-3209us] +/-   87ms
-- chrony tracking
Reference ID    : C62EF824 (198-20-172-38-host.colocrossing.com)
Stratum         : 3
Ref time (UTC)  : Wed Jul 08 23:53:00 2020
System time     : 0.001281736 seconds slow of NTP time
Last offset     : -0.000395995 seconds
RMS offset      : 0.000787869 seconds
Frequency       : 1.458 ppm fast
Residual freq   : -0.004 ppm
Skew            : 0.067 ppm
Root delay      : 0.084276654 seconds
Root dispersion : 0.026646379 seconds
Update interval : 1028.4 seconds
Leap status     : Normal
-- 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
12.167.151.1               49  24  394m     +0.026      0.079   +244us  1194us
ns1.backplanedns.org       44  22  392m     -0.124      0.122  +3472us  1689us
198-20-172-38-host.coloc>   7   5  120m     -0.537      0.531  -2464us   492us
acheron.bitsrc.net         44  27  391m     +0.114      0.105   -274us  1444us
 
---- sensors
-rw-r--r-- 1 root root 171 Sep 19  2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0:              N/A
 
ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V:        +13.69 V
in5:          +0.55 V
User ADC 1:   +0.00 V
User ADC 2:   +0.01 V
 
 
---- throttle
temp=62.3'C
throttled=0x0
 
---- locale
Locale country codes consistent among WiFi cfg file, iw reg & X11: US
core_config.sh has been run 1 time(s)
pi@N7KJK-PI:~ $
 

Basil Gunn
 

Kevin,
Looks like you are using the right hand mDin6 connector.
Try using the left hand connector, udr0, since the configuration scripts
assume that.


Kevin K. - N7KJK <kkutzera@...> writes:

OK so I think I'm really close to working system. (unless we really have a hardware issue which I don't think so).
A friend is trying to connect when I ask. I've been working on audio levels because I think everything else is working.
In our most recent tests we'll get what I think is a brief connection, but something drops it out before there's any data sent.
I'm using a Yaesu FT-7800 with the 6-pin connected to udr1 (the socket closest to the clock battery).

Hopefully something really stands out as incorrect here.

This is from the listen command......
000 N7KJK-10 Linux RMS Gateway 2.5.1, Kenmore, WA.
udr1: fm N7KJK-10 to K7RMZ ctl DISC+
udr1: fm K7RMZ to N7KJK-10 ctl SABM+
udr1: fm N7KJK-10 to K7RMZ ctl DM-
udr1: fm N7KJK-10 to K7RMZ ctl DISC+
udr1: fm K7RMZ to N7KJK-10 ctl RR2-
udr1: fm K7RMZ to N7KJK-10 ctl UA-
udr1: fm K7RMZ to N7KJK-10 ctl DM-

Here's the output of showudrc.sh

pi@N7KJK-PI:~ $ showudrc.sh
==== Sound Card ====
udrc card number line: card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
udrc is sound card #2
==== ALSA Controls for Radio Tansmit ====
LO Driver Gain L:[-6.00dB] R:[-6.00dB]
PCM L:[-20.00dB] R:[-20.00dB]
DAC Playback PT L:[P1] R:[P1]
LO Playback CM [Full Chip]
==== ALSA Controls for Radio Receive ====
ADC Level L:[-2.00dB] R:[-2.00dB]
IN1 L:[Off] R:[Off]
IN2 L:[10 kOhm] R:[10 kOhm]

==== Pi Ver ====
Pi 3 Model B, Rev 1.2, Mfg by Embest
Has WiFi

==== Pi Firmware VideoCore Ver ====
Apr 15 2020 11:43:08
Copyright (c) 2012 Broadcom
version 82f9bb929ce2186eb1824178c1ae82902ad6275c (clean) (release) (start)

==== Pi Firmware EEPROM Ver ====
error=1 error_msg="Command not registered"

==== Pi Firmware EEPROM Config ====
error=1 error_msg="Command not registered"

==== udrc Ver ====
Found a DRAWS

HAT ID EEPROM
Name: hat
Product: Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0305
UUID: 21c8d4ee-2b1b-4570-bb39-d9da8d8876ae
Vendor: NW Digital Radio

==== sys Ver ====
----- image version
2020 06 08 11:50:00 PDT: SD image version: nwdr16
----- /proc/version
Linux version 4.19.118-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1311 SMP Mon Apr 27 14:21:24 BST 2020

----- /etc/*version: 10.4

----- /etc/*release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
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
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster

---- systemd
Static hostname: N7KJK-PI
Icon name: computer
Machine ID: 27ac1f0c20904cb7a960920e966db545
Boot ID: ac173e148e5f4c249be834f1048b156b
Operating System: Raspbian GNU/Linux 10 (buster)
Kernel: Linux 4.19.118-v7+
Architecture: arm

---- modules
snd_soc_tlv320aic32x4_i2c 16384 171
snd_soc_tlv320aic32x4 40960 1 snd_soc_tlv320aic32x4_i2c
snd_soc_core 192512 4 snd_soc_simple_card_utils,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_simple_card
snd_pcm 102400 7 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core
snd 73728 16 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core,snd_pcm

---- kernel
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==================-============-============-=================================
ii raspberrypi-kernel 1.20200601-1 armhf Raspberry Pi bootloader

---- Codec drivers
Found: snd-soc-tlv320aic32x4-i2c.ko, OK
Found: snd-soc-tlv320aic32x4.ko, OK
Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay

---- syslog

---- dmesg

----- Dire Wolf DEVELOPMENT version 1.6 E (May 11 2020)

==== Filesystem ====
/dev/root 30G 5.2G 23G 19% /

==== boot config ====

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d

[all]
#dtoverlay=vc4-fkms-v3d

# Flush all overlays, ie. deprecated overlays loaded from eeprom
dtoverlay=
# enable udrc/draws if no eeprom
dtoverlay=draws,alsaname=udrc
force_turbo=1
# Enable audio (loads snd_bcm2835)
dtparam=audio=on

---- gpsd
/usr/local/sbin/gpsd
gpsd: 3.20 (revision 3.20)
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2020-07-08 10:15:31 PDT; 6h ago
Main PID: 601 (gpsd)
Tasks: 3 (limit: 2200)
Memory: 1.7M
CGroup: /system.slice/gpsd.service
└─601 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0

Jul 08 10:15:31 N7KJK-PI systemd[1]: Starting GPS (Global Positioning Syste…n...
Jul 08 10:15:31 N7KJK-PI systemd[1]: Started GPS (Global Positioning System…mon.
Hint: Some lines were ellipsized, use -l to show in full.

---- chrony
crw-rw---- 1 root root 241, 0 Jul 8 10:15 /dev/pps0
crw------- 1 root root 241, 1 Jul 8 10:15 /dev/pps1
crw-rw---- 1 root dialout 239, 0 Jul 8 10:15 /dev/ttySC0
crw-rw---- 1 root dialout 239, 1 Jul 8 10:15 /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
^+ 12.167.151.1 3 10 377 323 -3228us[-3621us] +/- 146ms
^+ ns1.backplanedns.org 2 10 377 438 -8191us[-8582us] +/- 133ms
^* 198-20-172-38-host.coloc> 2 10 377 168 -4019us[-4415us] +/- 85ms
^+ acheron.bitsrc.net 3 10 377 493 -2819us[-3209us] +/- 87ms
-- chrony tracking
Reference ID : C62EF824 (198-20-172-38-host.colocrossing.com)
Stratum : 3
Ref time (UTC) : Wed Jul 08 23:53:00 2020
System time : 0.001281736 seconds slow of NTP time
Last offset : -0.000395995 seconds
RMS offset : 0.000787869 seconds
Frequency : 1.458 ppm fast
Residual freq : -0.004 ppm
Skew : 0.067 ppm
Root delay : 0.084276654 seconds
Root dispersion : 0.026646379 seconds
Update interval : 1028.4 seconds
Leap status : Normal
-- 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
12.167.151.1 49 24 394m +0.026 0.079 +244us 1194us
ns1.backplanedns.org 44 22 392m -0.124 0.122 +3472us 1689us
198-20-172-38-host.coloc> 7 5 120m -0.537 0.531 -2464us 492us
acheron.bitsrc.net 44 27 391m +0.114 0.105 -274us 1444us

---- sensors
-rw-r--r-- 1 root root 171 Sep 19 2019 /etc/sensors.d/draws
rpi_volt-isa-0000
Adapter: ISA adapter
in0: N/A

ads1015-i2c-1-48
Adapter: bcm2835 I2C adapter
+12V: +13.69 V
in5: +0.55 V
User ADC 1: +0.00 V
User ADC 2: +0.01 V

---- throttle
temp=62.3'C
throttled=0x0

---- locale
Locale country codes consistent among WiFi cfg file, iw reg & X11: US
core_config.sh has been run 1 time(s)
pi@N7KJK-PI:~ $

Kevin K. - N7KJK
 

Thanks Basil, 
I'll make that change.. see what happens. Two questions:

1.  Is there a single (or couple) of documents that describe all the components of a Gateway system (specific to the DRAWS technology)?
2.  Is there some description of the file structure (like a programmer's guide) that discusses which folders are for what purpose, and perhaps where all the various .conf files are (where they should be)..  I know some of this is default locations for Unix but there's also stuff specific to the DRAWS image. 

I'm documenting all my efforts in the hopes of completing  step by step guide for the gateway setup. 

Thanks

On Wed, Jul 8, 2020 at 9:40 PM Basil Gunn <basil@...> wrote:

Kevin,
Looks like you are using the right hand mDin6 connector.
Try using the left hand connector, udr0, since the configuration scripts
assume that.


Kevin K. - N7KJK <kkutzera@...> writes:

> OK so I think I'm really close to working system. (unless we really have a hardware issue which I don't think so).
> A friend is trying to connect when I ask. I've been working on audio levels because I think everything else is working.
> In our most recent tests we'll get what I think is a brief connection, but something drops it out before there's any data sent.
> I'm using a Yaesu FT-7800 with the 6-pin connected to udr1 (the socket closest to the clock battery).
>
> Hopefully something really stands out as incorrect here.
>
> This is from the listen command......
> 000 N7KJK-10 Linux RMS Gateway 2.5.1, Kenmore, WA.
> udr1: fm N7KJK-10 to K7RMZ ctl DISC+
> udr1: fm K7RMZ to N7KJK-10 ctl SABM+
> udr1: fm N7KJK-10 to K7RMZ ctl DM-
> udr1: fm N7KJK-10 to K7RMZ ctl DISC+
> udr1: fm K7RMZ to N7KJK-10 ctl RR2-
> udr1: fm K7RMZ to N7KJK-10 ctl UA-
> udr1: fm K7RMZ to N7KJK-10 ctl DM-
>
> Here's the output of showudrc.sh
>
> pi@N7KJK-PI:~ $ showudrc.sh
> ==== Sound Card ====
> udrc card number line: card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]
> udrc is sound card #2
> ==== ALSA Controls for Radio Tansmit ====
> LO Driver Gain L:[-6.00dB]  R:[-6.00dB]
> PCM      L:[-20.00dB]  R:[-20.00dB]
> DAC Playback PT L:[P1] R:[P1]
> LO Playback CM [Full Chip]
> ==== ALSA Controls for Radio Receive ====
> ADC Level   L:[-2.00dB]  R:[-2.00dB]
> IN1      L:[Off]    R:[Off]
> IN2      L:[10 kOhm]  R:[10 kOhm]
>
> ==== Pi Ver ====
> Pi 3 Model B, Rev 1.2, Mfg by Embest
> Has WiFi
>
> ==== Pi Firmware VideoCore Ver ====
> Apr 15 2020 11:43:08
> Copyright (c) 2012 Broadcom
> version 82f9bb929ce2186eb1824178c1ae82902ad6275c (clean) (release) (start)
>
> ==== Pi Firmware EEPROM Ver ====
> error=1 error_msg="Command not registered"
>
> ==== Pi Firmware EEPROM Config ====
> error=1 error_msg="Command not registered"
>
> ==== udrc Ver ====
> Found a DRAWS
>
> HAT ID EEPROM
> Name:    hat
> Product:  Digital Radio Amateur Work Station
> Product ID: 0x0004
> Product ver: 0x0305
> UUID:    21c8d4ee-2b1b-4570-bb39-d9da8d8876ae
> Vendor:   NW Digital Radio
>
> ==== sys Ver ====
> ----- image version
> 2020 06 08 11:50:00 PDT: SD image version: nwdr16
> ----- /proc/version
> Linux version 4.19.118-v7+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1311 SMP Mon Apr 27 14:21:24 BST 2020
>
> ----- /etc/*version: 10.4
>
> ----- /etc/*release
> PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
> NAME="Raspbian GNU/Linux"
> VERSION_ID="10"
> VERSION="10 (buster)"
> VERSION_CODENAME=buster
> 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
> No LSB modules are available.
> Distributor ID: Raspbian
> Description:  Raspbian GNU/Linux 10 (buster)
> Release:    10
> Codename:   buster
>
> ---- systemd
> Static hostname: N7KJK-PI
> Icon name: computer
> Machine ID: 27ac1f0c20904cb7a960920e966db545
> Boot ID: ac173e148e5f4c249be834f1048b156b
> Operating System: Raspbian GNU/Linux 10 (buster)
> Kernel: Linux 4.19.118-v7+
> Architecture: arm
>
> ---- modules
> snd_soc_tlv320aic32x4_i2c  16384 171
> snd_soc_tlv320aic32x4  40960 1 snd_soc_tlv320aic32x4_i2c
> snd_soc_core     192512 4 snd_soc_simple_card_utils,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_soc_simple_card
> snd_pcm       102400 7 snd_pcm_dmaengine,snd_soc_bcm2835_i2s,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core
> snd          73728 16 snd_compress,snd_timer,snd_soc_tlv320aic32x4,snd_bcm2835,snd_soc_core,snd_pcm
>
> ---- kernel
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name       Version   Architecture Description
> +++-==================-============-============-=================================
> ii raspberrypi-kernel 1.20200601-1 armhf    Raspberry Pi bootloader
>
> ---- Codec drivers
> Found: snd-soc-tlv320aic32x4-i2c.ko, OK
> Found: snd-soc-tlv320aic32x4.ko, OK
> Directory: /proc/device-tree/soc/i2c@7e804000/tlv320aic32x4@18 exists and status is okay
>
> ---- syslog
>
> ---- dmesg
>
> ----- Dire Wolf DEVELOPMENT version 1.6 E (May 11 2020)
>
> ==== Filesystem ====
> /dev/root    30G 5.2G 23G 19% /
>
> ==== boot config ====
>
> [pi4]
> # Enable DRM VC4 V3D driver on top of the dispmanx display stack
> dtoverlay=vc4-fkms-v3d
>
> [all]
> #dtoverlay=vc4-fkms-v3d
>
> # Flush all overlays, ie. deprecated overlays loaded from eeprom
> dtoverlay=
> # enable udrc/draws if no eeprom
> dtoverlay=draws,alsaname=udrc
> force_turbo=1
> # Enable audio (loads snd_bcm2835)
> dtparam=audio=on
>
> ---- gpsd
> /usr/local/sbin/gpsd
> gpsd: 3.20 (revision 3.20)
> ● gpsd.service - GPS (Global Positioning System) Daemon
> Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor preset: enabled)
> Active: active (running) since Wed 2020-07-08 10:15:31 PDT; 6h ago
> Main PID: 601 (gpsd)
> Tasks: 3 (limit: 2200)
> Memory: 1.7M
> CGroup: /system.slice/gpsd.service
> └─601 /usr/local/sbin/gpsd -n /dev/ttySC0 /dev/pps0
>
> Jul 08 10:15:31 N7KJK-PI systemd[1]: Starting GPS (Global Positioning Syste…n...
> Jul 08 10:15:31 N7KJK-PI systemd[1]: Started GPS (Global Positioning System…mon.
> Hint: Some lines were ellipsized, use -l to show in full.
>
> ---- chrony
> crw-rw---- 1 root root  241, 0 Jul 8 10:15 /dev/pps0
> crw------- 1 root root  241, 1 Jul 8 10:15 /dev/pps1
> crw-rw---- 1 root dialout 239, 0 Jul 8 10:15 /dev/ttySC0
> crw-rw---- 1 root dialout 239, 1 Jul 8 10:15 /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
> ^+ 12.167.151.1         3 10 377 323 -3228us[-3621us] +/- 146ms
> ^+ ns1.backplanedns.org     2 10 377 438 -8191us[-8582us] +/- 133ms
> ^* 198-20-172-38-host.coloc>  2 10 377 168 -4019us[-4415us] +/- 85ms
> ^+ acheron.bitsrc.net      3 10 377 493 -2819us[-3209us] +/- 87ms
> -- chrony tracking
> Reference ID  : C62EF824 (198-20-172-38-host.colocrossing.com)
> Stratum    : 3
> Ref time (UTC) : Wed Jul 08 23:53:00 2020
> System time  : 0.001281736 seconds slow of NTP time
> Last offset  : -0.000395995 seconds
> RMS offset   : 0.000787869 seconds
> Frequency   : 1.458 ppm fast
> Residual freq : -0.004 ppm
> Skew      : 0.067 ppm
> Root delay   : 0.084276654 seconds
> Root dispersion : 0.026646379 seconds
> Update interval : 1028.4 seconds
> Leap status  : Normal
> -- 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
> 12.167.151.1       49 24 394m  +0.026   0.079 +244us 1194us
> ns1.backplanedns.org   44 22 392m  -0.124   0.122 +3472us 1689us
> 198-20-172-38-host.coloc> 7 5 120m  -0.537   0.531 -2464us 492us
> acheron.bitsrc.net    44 27 391m  +0.114   0.105 -274us 1444us
>
> ---- sensors
> -rw-r--r-- 1 root root 171 Sep 19 2019 /etc/sensors.d/draws
> rpi_volt-isa-0000
> Adapter: ISA adapter
> in0:       N/A
>
> ads1015-i2c-1-48
> Adapter: bcm2835 I2C adapter
> +12V:    +13.69 V
> in5:     +0.55 V
> User ADC 1: +0.00 V
> User ADC 2: +0.01 V
>
> ---- throttle
> temp=62.3'C
> throttled=0x0
>
> ---- locale
> Locale country codes consistent among WiFi cfg file, iw reg & X11: US
> core_config.sh has been run 1 time(s)
> pi@N7KJK-PI:~ $





--
Kevin J. Kutzera CISSP, CISM, CEH
Cell: 206-850-7762

Basil Gunn
 

I will work on your file request, it will take me a few days.

Also there is a script n7nix/rmsgw/chk_gateway.sh that you should
run. It will produce a lot of output that will help me solve any
problems you have. Just send it to me directly it contains the output of
all the files that you are requesting.


Kevin K. - N7KJK <kkutzera@...> writes:

I'll make that change.. see what happens. Two questions:

1. Is there a single (or couple) of documents that describe all the
components of a Gateway system (specific to the DRAWS technology)?
2. Is there some description of the file structure (like a
programmer's guide) that discusses which folders are for what purpose, and
perhaps where all the various .conf files are (where they should be).. I
know some of this is default locations for Unix but there's also stuff
specific to the DRAWS image.

I'm documenting all my efforts in the hopes of completing step by step
guide for the gateway setup.

Kevin K. - N7KJK
 

I'll send that output.   You don't have to go to a bunch of trouble on the list.  I can probably figure it out from the output of that script.

I have the UDR0 working except for a Permission denied on /wl3k/mid.db.. Kind of weird
guess I can manually reset permissions on that file..??

I successfully sent an message through another gateway using    >sudo wl2kax25 -c W7AUX-10
everything talk via udr0

KK

On Thu, Jul 9, 2020 at 10:27 AM Basil Gunn <basil@...> wrote:

I will work on your file request, it will take me a few days.

Also there is a script  n7nix/rmsgw/chk_gateway.sh that you should
run. It will produce a lot of output that will help me solve any
problems you have. Just send it to me directly it contains the output of
all the files that you are requesting.


Kevin K. - N7KJK <kkutzera@...> writes:

> I'll make that change.. see what happens. Two questions:
>
> 1.  Is there a single (or couple) of documents that describe all the
> components of a Gateway system (specific to the DRAWS technology)?
> 2.  Is there some description of the file structure (like a
> programmer's guide) that discusses which folders are for what purpose, and
> perhaps where all the various .conf files are (where they should be)..  I
> know some of this is default locations for Unix but there's also stuff
> specific to the DRAWS image.
>
> I'm documenting all my efforts in the hopes of completing  step by step
> guide for the gateway setup.





--
Kevin J. Kutzera CISSP, CISM, CEH
Cell: 206-850-7762

Kevin K. - N7KJK
 

successfully received an email message.  Sender is using an "experimental system" of his own.  there were some delays and retries, but the email made it through.  I'll get some more test traffic in the next few days.
Thanks for you help on this Basil...

Yes,,   I will backup this SD card...  :)
KK

On Thu, Jul 9, 2020 at 10:36 AM Kevin K. - N7KJK via groups.io <kkutzera=gmail.com@groups.io> wrote:
I'll send that output.   You don't have to go to a bunch of trouble on the list.  I can probably figure it out from the output of that script.

I have the UDR0 working except for a Permission denied on /wl3k/mid.db.. Kind of weird
guess I can manually reset permissions on that file..??

I successfully sent an message through another gateway using    >sudo wl2kax25 -c W7AUX-10
everything talk via udr0

KK

On Thu, Jul 9, 2020 at 10:27 AM Basil Gunn <basil@...> wrote:

I will work on your file request, it will take me a few days.

Also there is a script  n7nix/rmsgw/chk_gateway.sh that you should
run. It will produce a lot of output that will help me solve any
problems you have. Just send it to me directly it contains the output of
all the files that you are requesting.


Kevin K. - N7KJK <kkutzera@...> writes:

> I'll make that change.. see what happens. Two questions:
>
> 1.  Is there a single (or couple) of documents that describe all the
> components of a Gateway system (specific to the DRAWS technology)?
> 2.  Is there some description of the file structure (like a
> programmer's guide) that discusses which folders are for what purpose, and
> perhaps where all the various .conf files are (where they should be)..  I
> know some of this is default locations for Unix but there's also stuff
> specific to the DRAWS image.
>
> I'm documenting all my efforts in the hopes of completing  step by step
> guide for the gateway setup.





--
Kevin J. Kutzera CISSP, CISM, CEH
Cell: 206-850-7762



--
Kevin J. Kutzera CISSP, CISM, CEH
Cell: 206-850-7762

Basil Gunn
 

I have the UDR0 working except for a Permission denied on /wl3k/mid.db..
Kind of weird guess I can manually reset permissions on that file..??
This is a common problem.
Check if there is a script called chk_perm.sh in your local bin
directory. /home/pi/bin
Run that script.

If you can not find the script then just.

cd /usr/local/var
sudo chown -R pi:mail wl2k