Date   

DRAWS™ Case Update #case

 

Thanks to one of our customers, the DRAWS™ case is moving forward again. The latest CAD Files have been sent and the "hopefully" final prototypes have been ordered.

Thanks to all of those who responded to our request for help!

Bryan K7UDR


Re: RPi kernel upgrade problem

J P Watters <kc9kko@...>
 

Basil,

Maybe we should add to the “Getting Started” adding that command to prevent kernel updates on a Draws SD Card Image? ie 
sudo apt-mark hold linux-image-$(uname -r)
 
On the NWDigitalRadio Getting Started for DRAWS it shows running two commands the I think will get us in trouble since they will upgrade the kernel. (apt-get update and apt-get dist-upd
I think that running the command 
sudo apt-mark hold linux-image-$(uname -r)
 
before any other commands, would prevent the kernel from being upgraded while obtaining all the others. 
 
And to remove that “HOLD” run the command 
 
sudo apt-mark unhold linux-image-$(uname -r)
 
My process is to write a SD card with the NWDR16.zip image. 
Boot from that card. 
Before acknowledging any dialog box. ie the update that auto runs.
Execute from a terminal window ( open a terminal session )
      the command   sudo apt-mark hold linux-image-$(uname -r)
Exit the terminal session.
 
Then proceed with the auto run update that was triggered.
 
Maybe we should add to the “Getting Started” adding that command to prevent kernel updates on a Draws SD Card Image?
 
..jpw J P Watters
KC9KKO
Morris, IL
 
 
 
 

 

 

Initial Configuration

Initial Config Summary

  • First boot:
    • Verify that required drivers for the DRAWS codec are loaded
    • Follow 'Welcome to Raspberry Pi' piwiz screens.
    • Update the configuration scripts
  • Second boot: run script: app_config.sh core
  • Third boot: Set your ALSA config
  • For packet turn on Direwolf & AX.25

Check for required drivers first

  • First open a console and type:

    aplay -l
  • You should see a line in the output that looks something like this:

    card 0: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 []
  • If you do not see udrc enumerated do not continue

Initial Config Detail

  • If you are running with an attached monitor you should see the Raspbian 'Welcome to Raspberry Pi' piwiz splash screen
    • Follow the screens as you would on any other Raspbian install.
    • When prompted to restart the RPi please do so.
Update configurations scripts
cd
cd n7nix
git pull

sudo su
apt-get update
apt-get dist-upgrade
# revert back to normal user
exit
Configure core functionality
  • Whether you want direwolf for packet functionality or run HF apps with the draws HAT do the following:
cd
cd n7nix/config
# Become root
sudo su
./app_config.sh core
  • The above script sets up the following:

    • iptables
    • RPi login password
    • RPi host name
    • mail host name
    • time zone
    • current time via chrony
    • AX.25
    • direwolf
    • systemd
  •  
 
 

On Jul 29, 2020, at 2:53 PM, Basil Gunn <basil@...> wrote:


Until further notice please do not upgrade the kernel on your RPi.

Linux kernel 4.19.118 is OK
Linux kernel 5.4.51 has MANY problems

Run this to get your current kernel version:
uname -r

The following commands will upgrade your kernel.
Do NOT use them for a while:

apt-get dist-upgrade
apt full-upgrade

/Basil N7NIX


Re: RPi kernel upgrade problem

Thomas KF7RSF <tnoel@...>
 

Nice to find what broke in new kernel. I can live with 4.19.118 until fixed.
Tom

On Jul 29, 2020, at 22:13, Basil Gunn <basil@pacabunga.com> wrote:


So, I ran "sudo rpi-upgrade e1050e94821a70b2e4c72b318d6c6c968552e9a2”
with the hex string for the 4.19.118 kernel coming from the GitHub
raspbian kernel repository.

Ran with no reported errors, rebooted and “uname -a” reporting correct
kernel. All my prior configuration is intact, and the few apps already
configured seem to run correctly.
Thanks for that Thomas. Very good to know!

The following is from Anna NH6Z condensed from a couple of emails:

Removal of ADS1015 driver explained here:
https://www.spinics.net/lists/linux-hwmon/msg06097.html

The ads1015 driver name has changed to “ti_ads1015” and it’s now
loading “industrialio” and not “hwmon”. The upstream Linux guys
deprecated and removed the ads1015 driver from the hwmon subsystem as
being “redundant.” That means that the device tree is matching the
IIO (Industrial IO) driver now, and that’s getting loaded.

That means that the hwmon subsystem that lm-sensors uses to probe no
longer sees the device because there’s no driver.

There is a bridge from the iio subsystem to the hwmon subsystem (the
iio-hwmon driver), but it needs DT (Device Tree) support to be
instantiated.

The iio-hwmon driver is not shipped by default with Raspbian, so it’s
not fixable with merely a DT change. I have to get a fresh kernel and
modules compiled to test it out. When I can get it to work, I’ll PR the
whole thing and add the iio-hwmon driver to the bcm*_defconfig files for
RPi. That’ll get it in Raspbian for the next kernel release.

Dunno when I’m going to get to that, but I’ll push it out when I can.


Thomas KF7RSF via groups.io <tnoel=mac.com@groups.io> writes:

I had nothing to lose; facing re-burning and re-configuring the
correct image, so I gave it a shot. I’ve previously used “rpi-upgrade
commitID’ to both advance and to roll-back kernels in raspbian
distributions.

So, I ran "sudo rpi-upgrade e1050e94821a70b2e4c72b318d6c6c968552e9a2”
with the hex string for the 4.19.118 kernel coming from the GitHub
raspbian kernel repository.

Ran with no reported errors, rebooted and “uname -a” reporting correct
kernel. All my prior configuration is intact, and the few apps already
configured seem to run correctly.

I’ll let you know if I find anything broken.

Thomas Noel
KF7RSF

On Jul 29, 2020, at 5:42 PM, Basil Gunn <basil@pacabunga.com> wrote:

Will the command "sudo rpi-upgrade "commitID"" revert the kernel
successfully if correct Commit ID hex value from GitHub is used for
the 4.19.118 kernel release?
I don't think so.

When I read the documentation for rpi-update
(https://github.com/Hexxeh/rpi-update) it distinguishes between kernel &
RPi firmware.

To upgrade/downgrade to a specific firmware revision, specify its Git
hash
I think that is only for RPi firmware and not the kernel and kernel
modules but I could be wrong.

I have a script somewhere that puts whatever kernel in the right
location. Files in /boot are not the only place that need updating and
it is not entirely safe to do that.

/Basil n7nix


Re: RPi kernel upgrade problem

Basil Gunn
 

So, I ran "sudo rpi-upgrade e1050e94821a70b2e4c72b318d6c6c968552e9a2”
with the hex string for the 4.19.118 kernel coming from the GitHub
raspbian kernel repository.

Ran with no reported errors, rebooted and “uname -a” reporting correct
kernel. All my prior configuration is intact, and the few apps already
configured seem to run correctly.
Thanks for that Thomas. Very good to know!

The following is from Anna NH6Z condensed from a couple of emails:

Removal of ADS1015 driver explained here:
https://www.spinics.net/lists/linux-hwmon/msg06097.html

The ads1015 driver name has changed to “ti_ads1015” and it’s now
loading “industrialio” and not “hwmon”. The upstream Linux guys
deprecated and removed the ads1015 driver from the hwmon subsystem as
being “redundant.” That means that the device tree is matching the
IIO (Industrial IO) driver now, and that’s getting loaded.

That means that the hwmon subsystem that lm-sensors uses to probe no
longer sees the device because there’s no driver.

There is a bridge from the iio subsystem to the hwmon subsystem (the
iio-hwmon driver), but it needs DT (Device Tree) support to be
instantiated.

The iio-hwmon driver is not shipped by default with Raspbian, so it’s
not fixable with merely a DT change. I have to get a fresh kernel and
modules compiled to test it out. When I can get it to work, I’ll PR the
whole thing and add the iio-hwmon driver to the bcm*_defconfig files for
RPi. That’ll get it in Raspbian for the next kernel release.

Dunno when I’m going to get to that, but I’ll push it out when I can.


Thomas KF7RSF via groups.io <tnoel=mac.com@groups.io> writes:

I had nothing to lose; facing re-burning and re-configuring the
correct image, so I gave it a shot. I’ve previously used “rpi-upgrade
commitID’ to both advance and to roll-back kernels in raspbian
distributions.

So, I ran "sudo rpi-upgrade e1050e94821a70b2e4c72b318d6c6c968552e9a2”
with the hex string for the 4.19.118 kernel coming from the GitHub
raspbian kernel repository.

Ran with no reported errors, rebooted and “uname -a” reporting correct
kernel. All my prior configuration is intact, and the few apps already
configured seem to run correctly.

I’ll let you know if I find anything broken.

Thomas Noel
KF7RSF

On Jul 29, 2020, at 5:42 PM, Basil Gunn <basil@pacabunga.com> wrote:


Will the command "sudo rpi-upgrade "commitID"" revert the kernel
successfully if correct Commit ID hex value from GitHub is used for
the 4.19.118 kernel release?
I don't think so.

When I read the documentation for rpi-update
(https://github.com/Hexxeh/rpi-update) it distinguishes between kernel &
RPi firmware.

To upgrade/downgrade to a specific firmware revision, specify its Git
hash
I think that is only for RPi firmware and not the kernel and kernel
modules but I could be wrong.

I have a script somewhere that puts whatever kernel in the right
location. Files in /boot are not the only place that need updating and
it is not entirely safe to do that.

/Basil n7nix


Re: RPi kernel upgrade problem

Thomas KF7RSF <tnoel@...>
 

I had nothing to lose; facing re-burning and re-configuring the correct image, so I gave it a shot. I’ve previously used “rpi-upgrade commitID’ to both advance and to roll-back kernels in raspbian distributions.

So, I ran "sudo rpi-upgrade e1050e94821a70b2e4c72b318d6c6c968552e9a2” with the hex string for the 4.19.118 kernel coming from the GitHub raspbian kernel repository.

Ran with no reported errors, rebooted and “uname -a” reporting correct kernel. All my prior configuration is intact, and the few apps already configured seem to run correctly.

I’ll let you know if I find anything broken.

Thomas Noel
KF7RSF

On Jul 29, 2020, at 5:42 PM, Basil Gunn <basil@pacabunga.com> wrote:


Will the command "sudo rpi-upgrade "commitID"" revert the kernel
successfully if correct Commit ID hex value from GitHub is used for
the 4.19.118 kernel release?
I don't think so.

When I read the documentation for rpi-update
(https://github.com/Hexxeh/rpi-update) it distinguishes between kernel &
RPi firmware.

To upgrade/downgrade to a specific firmware revision, specify its Git
hash
I think that is only for RPi firmware and not the kernel and kernel
modules but I could be wrong.

I have a script somewhere that puts whatever kernel in the right
location. Files in /boot are not the only place that need updating and
it is not entirely safe to do that.

/Basil n7nix



Re: RPi kernel upgrade problem

Basil Gunn
 

Will the command "sudo rpi-upgrade "commitID"" revert the kernel
successfully if correct Commit ID hex value from GitHub is used for
the 4.19.118 kernel release?
I don't think so.

When I read the documentation for rpi-update
(https://github.com/Hexxeh/rpi-update) it distinguishes between kernel &
RPi firmware.

To upgrade/downgrade to a specific firmware revision, specify its Git
hash
I think that is only for RPi firmware and not the kernel and kernel
modules but I could be wrong.

I have a script somewhere that puts whatever kernel in the right
location. Files in /boot are not the only place that need updating and
it is not entirely safe to do that.

/Basil n7nix


Re: DRAWS not found

Keating Floyd
 

Hi,  Basil (et al).

I did as you suggested, and did not even do the "Welcome to the Raspberry Pi Desktop" setup.

aplay -l reports "aplay: device_list:272: no soundcards found..."

udrcver.sh reports:

     HAT ID EEPROM
Name:       hat
Product:    Digital Radio Amateur Work Station
Product ID: 0x0004
Product ver: 0x0204
UUID: 7499df1d-8bc8-401d-b978-97518d36967e
Vendor: NW Digital Radio

Thanks,

Keating

On Wed, Jul 29, 2020 at 1:03 PM Keating Floyd via groups.io <kc4hsi=gmail.com@groups.io> wrote:
I believe I was following the getting started guide - but it is possible I did an upgrade first.  I will do exactly as you suggest!

Keating

On Wed, Jul 29, 2020 at 11:40 AM Basil Gunn <basil@...> wrote:
Keating,

Using the same Raspberry Pi version & DRAWS hat version as you I booted
a fresh NWDR16 image and could not replicate your symptom.

The first thing to do after booting a new image is to run
aplay -l
which will tell you if the driver and overlays have loaded properly.
This is described in the Getting Started Guide
https://nw-digital-radio.groups.io/g/udrc/wiki/8921

What where the steps you took after your first boot of a new image?
ie. did you run apt-get update, or raspi-config, or pi-wiz setup?

I would like you to try and replicate what I did which is to burn the
image, boot & run aplay -l so that we can figure out what is causing
your problem.

 $ udrcver.sh
Found a DRAWS

     HAT ID EEPROM
Name:        hat
Product:     Digital Radio Amateur Work Station
Product ID:  0x0004
Product ver: 0x0204
UUID:        4a0b1dce-358e-4b50-a372-1118a9ecbfed
Vendor:      NW Digital Radio

pi@raspberrypi:~ $ piver.sh
 Pi 4 Model B, Rev 1.1, 4GB mem, Mfg by Sony UK
 Has WiFi

pi@raspberrypi:~ $ aplay -l | grep udrc
card 2: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0 [bcm2835-i2s-tlv320aic32x4-hifi tlv320aic32x4-hifi-0]

/Basil n7nix

Keating Floyd <kc4hsi@...> writes:

> Hi, Basil, and thanks!
>
> Yes, I have a wireless keyboard dongle plugged in there.
>
> Keating
>
>
> On Tue, Jul 28, 2020, 9:36 PM Basil Gunn <basil@...> wrote:
>
>>
>> Keating,
>> I am looking into your problem.
>> Could you please tell me if you have anything plugged into the USB
>> ports on your RPi 4.
>> Thanks,
>> /Basil
>>
>> Keating Floyd <kc4hsi@...> writes:
>>
>> > Included is the output from showudrc.sh. I was concerned that I had a
>> problem with my image perhaps, but I own a second DRAWS, and it shows up
>> just fine.
>> >
>> > Thanks for a great product, and for your help.
>> >
>> > Keating
>> >
>> > ===
>> >
>> > root@pi4b4g01:/home/pi/n7nix/hfprogs# cat showudrc.sh_out
>> > ==== Sound Card ====
>> > No udrc sound card found.
>> > ==== Pi Ver ====
>> > Pi 4 Model B, Rev 1.1, 4GB mem, 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




Re: RPi kernel upgrade problem

Thomas KF7RSF <tnoel@...>
 

Basil,

Will the command "sudo rpi-upgrade "commitID"" revert the kernel successfully if correct Commit ID hex value from GitHub is used for the 4.19.118 kernel release?
Thomas


Re: DRAWS™ Manager Demo #drawsmanager

Charlie Hein
 

I'll say!  Needed to flash a new card with just the raw image on it.  I'm guessing that it's been maybe a half hour from the time I put the card into the Pi, and I'm seeing packets off the air and DRAWS-Manager is functional.  Got almost no errors coming through the setup, either.  

Charlie


Re: DRAWS™ Manager Demo #drawsmanager

Basil Gunn
 

4.19.118 good
5.4.51 BAD

Charlie Hein <chein@bellsouth.net> writes:

If you skip that update the kernel is at "4.19.118-v7+"

Charlie


Re: DRAWS™ Manager Demo #drawsmanager

Charlie Hein
 

If you skip that update the kernel is at "4.19.118-v7+"

Charlie


Re: DRAWS™ Manager Demo #drawsmanager

Charlie Hein
 

Basil - that includes the "Welcome to Raspberry Pi" automated configuration where it asks to update Software as well, correct?

Charlie 


Re: DRAWS™ Manager Demo #drawsmanager

Charlie Hein
 

Okay, start over from scratch it is!  A little repetition never hurt the learning curve!

Thanks,
Charlie


Re: DRAWS™ Manager Demo #drawsmanager

Basil Gunn
 

Yes that is what I get as well.
The sensors command (along with a bunch of other things) is not working
in kernel 5.4.51, that is what is causing draws-manager to fail.

The only solution I have at the moment is to start over with NWDR16 and NOT do
a kernel update (ie. do not do apt-get dist-upgrade or rpi-update)

There are a lot of forums complaining about the new kernel. I will post
any news as I hear it.

/Basil


Charlie Hein <chein@bellsouth.net> writes:

Here you go, Basil:

pi@nvdpi:~ $ uname -a
Linux nvdpi 5.4.51-v7+ #1327 SMP Thu Jul 23 10:58:46 BST 2020 armv7l GNU/Linux
pi@nvdpi:~ $ journalctl -u draws-manager.service
-- Logs begin at Thu 2019-02-14 04:11:59 CST, end at Wed 2020-07-29 15:11:07 CDT
Jul 29 11:21:34 nvdpi systemd[1]: Started DRAWS™ Manager - A web application to
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm npm does not support Node.js v10.21
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You should probably upgrade to a ne
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm can't make any promises that npm wi
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm Supported releases of Node.js are t
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You can find the latest version at
Jul 29 11:21:43 nvdpi npm[542]: > webapp@0.0.1 start /usr/local/var/draws-manage
Jul 29 11:21:43 nvdpi npm[542]: > node ./bin/www
Jul 29 11:21:51 nvdpi npm[542]: ::
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: child_process.js:669
Jul 29 11:21:52 nvdpi npm[542]: throw err;
Jul 29 11:21:52 nvdpi npm[542]: ^
Jul 29 11:21:52 nvdpi npm[542]: Error: Command failed: /usr/bin/sensors *-i2c-1-
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: at checkExecSyncError (child_process.js:629:
Jul 29 11:21:52 nvdpi npm[542]: at execSync (child_process.js:666:13)
Jul 29 11:21:52 nvdpi npm[542]: at getSensors (/usr/local/var/draws-manager/
Jul 29 11:21:52 nvdpi npm[542]: at Timeout._onTimeout (/usr/local/var/draws-
Jul 29 11:21:52 nvdpi npm[542]: at ontimeout (timers.js:436:11)
Jul 29 11:21:52 nvdpi npm[542]: at tryOnTimeout (timers.js:300:5)
Jul 29 11:21:52 nvdpi npm[542]: at listOnTimeout (timers.js:263:5)
lines 1-23...skipping...
-- Logs begin at Thu 2019-02-14 04:11:59 CST, end at Wed 2020-07-29 15:11:07 CDT. --
Jul 29 11:21:34 nvdpi systemd[1]: Started DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration..
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm npm does not support Node.js v10.21.0
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You should probably upgrade to a newer version of node as we
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm can't make any promises that npm will work with this version.
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You can find the latest version at https://nodejs.org/
Jul 29 11:21:43 nvdpi npm[542]: > webapp@0.0.1 start /usr/local/var/draws-manager/webapp
Jul 29 11:21:43 nvdpi npm[542]: > node ./bin/www
Jul 29 11:21:51 nvdpi npm[542]: ::
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: child_process.js:669
Jul 29 11:21:52 nvdpi npm[542]: throw err;
Jul 29 11:21:52 nvdpi npm[542]: ^
Jul 29 11:21:52 nvdpi npm[542]: Error: Command failed: /usr/bin/sensors *-i2c-1-48
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: at checkExecSyncError (child_process.js:629:11)
Jul 29 11:21:52 nvdpi npm[542]: at execSync (child_process.js:666:13)
Jul 29 11:21:52 nvdpi npm[542]: at getSensors (/usr/local/var/draws-manager/webapp/io.js:45:15)
Jul 29 11:21:52 nvdpi npm[542]: at Timeout._onTimeout (/usr/local/var/draws-manager/webapp/io.js:118:27)
Jul 29 11:21:52 nvdpi npm[542]: at ontimeout (timers.js:436:11)
Jul 29 11:21:52 nvdpi npm[542]: at tryOnTimeout (timers.js:300:5)
Jul 29 11:21:52 nvdpi npm[542]: at listOnTimeout (timers.js:263:5)
Jul 29 11:21:52 nvdpi npm[542]: at Timer.processTimers (timers.js:223:10)
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! code ELIFECYCLE
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! errno 1
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! Exit status 1
Jul 29 11:21:52 nvdpi npm[542]: npm ERR!
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! Failed at the webapp@0.0.1 start script.
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! A complete log of this run can be found in:
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! /root/.npm/_logs/2020-07-29T16_21_52_279Z-debug.log
Jul 29 11:21:52 nvdpi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Jul 29 11:21:52 nvdpi systemd[1]: draws-manager.service: Failed with result 'exit-code'.
Jul 29 11:31:35 nvdpi systemd[1]: Started DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration..
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm npm does not support Node.js v10.21.0
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm You should probably upgrade to a newer version of node as we
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm can't make any promises that npm will work with this version.
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm You can find the latest version at https://nodejs.org/
Jul 29 11:31:39 nvdpi npm[1709]: > webapp@0.0.1 start /usr/local/var/draws-manager/webapp
Jul 29 11:31:39 nvdpi npm[1709]: > node ./bin/www
Jul 29 11:31:45 nvdpi npm[1709]: ::
Jul 29 11:31:46 nvdpi npm[1709]: Specified sensor(s) not found!
Jul 29 11:31:46 nvdpi npm[1709]: child_process.js:669
Jul 29 11:31:46 nvdpi npm[1709]: throw err;
Jul 29 11:31:46 nvdpi npm[1709]: ^
Jul 29 11:31:46 nvdpi npm[1709]: Error: Command failed: /usr/bin/sensors *-i2c-1-48
Jul 29 11:31:46 nvdpi npm[1709]: Specified sensor(s) not found!
Jul 29 11:31:46 nvdpi npm[1709]: at checkExecSyncError (child_process.js:629:11)
Jul 29 11:31:46 nvdpi npm[1709]: at execSync (child_process.js:666:13)
Jul 29 11:31:46 nvdpi npm[1709]: at getSensors (/usr/local/var/draws-manager/webapp/io.js:45:15)
Jul 29 11:31:46 nvdpi npm[1709]: at Timeout._onTimeout (/usr/local/var/draws-manager/webapp/io.js:118:27)
Jul 29 11:31:46 nvdpi npm[1709]: at ontimeout (timers.js:436:11)
Jul 29 11:31:46 nvdpi npm[1709]: at tryOnTimeout (timers.js:300:5)
Jul 29 11:31:46 nvdpi npm[1709]: at listOnTimeout (timers.js:263:5)
Jul 29 11:31:46 nvdpi npm[1709]: at Timer.processTimers (timers.js:223:10)
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! code ELIFECYCLE
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! errno 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Exit status 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Failed at the webapp@0.0.1 start script.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! A complete log of this run can be found in:
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! /root/.npm/_logs/2020-07-29T16_31_46_715Z-debug.log
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Failed with result 'exit-code'.
lines 30-69/69 (END)


Re: DRAWS™ Manager Demo #drawsmanager

Charlie Hein
 

Here you go, Basil:

pi@nvdpi:~ $ uname -a
Linux nvdpi 5.4.51-v7+ #1327 SMP Thu Jul 23 10:58:46 BST 2020 armv7l GNU/Linux
pi@nvdpi:~ $ journalctl -u draws-manager.service
-- Logs begin at Thu 2019-02-14 04:11:59 CST, end at Wed 2020-07-29 15:11:07 CDT
Jul 29 11:21:34 nvdpi systemd[1]: Started DRAWS™ Manager - A web application to 
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm npm does not support Node.js v10.21
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You should probably upgrade to a ne
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm can't make any promises that npm wi
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm Supported releases of Node.js are t
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You can find the latest version at 
Jul 29 11:21:43 nvdpi npm[542]: > webapp@0.0.1 start /usr/local/var/draws-manage
Jul 29 11:21:43 nvdpi npm[542]: > node ./bin/www
Jul 29 11:21:51 nvdpi npm[542]: ::
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: child_process.js:669
Jul 29 11:21:52 nvdpi npm[542]:     throw err;
Jul 29 11:21:52 nvdpi npm[542]:     ^
Jul 29 11:21:52 nvdpi npm[542]: Error: Command failed: /usr/bin/sensors *-i2c-1-
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]:     at checkExecSyncError (child_process.js:629:
Jul 29 11:21:52 nvdpi npm[542]:     at execSync (child_process.js:666:13)
Jul 29 11:21:52 nvdpi npm[542]:     at getSensors (/usr/local/var/draws-manager/
Jul 29 11:21:52 nvdpi npm[542]:     at Timeout._onTimeout (/usr/local/var/draws-
Jul 29 11:21:52 nvdpi npm[542]:     at ontimeout (timers.js:436:11)
Jul 29 11:21:52 nvdpi npm[542]:     at tryOnTimeout (timers.js:300:5)
Jul 29 11:21:52 nvdpi npm[542]:     at listOnTimeout (timers.js:263:5)
lines 1-23...skipping...
-- Logs begin at Thu 2019-02-14 04:11:59 CST, end at Wed 2020-07-29 15:11:07 CDT. --
Jul 29 11:21:34 nvdpi systemd[1]: Started DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration..
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm npm does not support Node.js v10.21.0
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You should probably upgrade to a newer version of node as we
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm can't make any promises that npm will work with this version.
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
Jul 29 11:21:42 nvdpi npm[542]: npm WARN npm You can find the latest version at https://nodejs.org/
Jul 29 11:21:43 nvdpi npm[542]: > webapp@0.0.1 start /usr/local/var/draws-manager/webapp
Jul 29 11:21:43 nvdpi npm[542]: > node ./bin/www
Jul 29 11:21:51 nvdpi npm[542]: ::
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]: child_process.js:669
Jul 29 11:21:52 nvdpi npm[542]:     throw err;
Jul 29 11:21:52 nvdpi npm[542]:     ^
Jul 29 11:21:52 nvdpi npm[542]: Error: Command failed: /usr/bin/sensors *-i2c-1-48
Jul 29 11:21:52 nvdpi npm[542]: Specified sensor(s) not found!
Jul 29 11:21:52 nvdpi npm[542]:     at checkExecSyncError (child_process.js:629:11)
Jul 29 11:21:52 nvdpi npm[542]:     at execSync (child_process.js:666:13)
Jul 29 11:21:52 nvdpi npm[542]:     at getSensors (/usr/local/var/draws-manager/webapp/io.js:45:15)
Jul 29 11:21:52 nvdpi npm[542]:     at Timeout._onTimeout (/usr/local/var/draws-manager/webapp/io.js:118:27)
Jul 29 11:21:52 nvdpi npm[542]:     at ontimeout (timers.js:436:11)
Jul 29 11:21:52 nvdpi npm[542]:     at tryOnTimeout (timers.js:300:5)
Jul 29 11:21:52 nvdpi npm[542]:     at listOnTimeout (timers.js:263:5)
Jul 29 11:21:52 nvdpi npm[542]:     at Timer.processTimers (timers.js:223:10)
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! code ELIFECYCLE
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! errno 1
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! Exit status 1
Jul 29 11:21:52 nvdpi npm[542]: npm ERR!
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! Failed at the webapp@0.0.1 start script.
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Jul 29 11:21:52 nvdpi npm[542]: npm ERR! A complete log of this run can be found in:
Jul 29 11:21:52 nvdpi npm[542]: npm ERR!     /root/.npm/_logs/2020-07-29T16_21_52_279Z-debug.log
Jul 29 11:21:52 nvdpi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Jul 29 11:21:52 nvdpi systemd[1]: draws-manager.service: Failed with result 'exit-code'.
Jul 29 11:31:35 nvdpi systemd[1]: Started DRAWS™ Manager - A web application to manage the DRAW™ HAT configuration..
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm npm does not support Node.js v10.21.0
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm You should probably upgrade to a newer version of node as we
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm can't make any promises that npm will work with this version.
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
Jul 29 11:31:39 nvdpi npm[1709]: npm WARN npm You can find the latest version at https://nodejs.org/
Jul 29 11:31:39 nvdpi npm[1709]: > webapp@0.0.1 start /usr/local/var/draws-manager/webapp
Jul 29 11:31:39 nvdpi npm[1709]: > node ./bin/www
Jul 29 11:31:45 nvdpi npm[1709]: ::
Jul 29 11:31:46 nvdpi npm[1709]: Specified sensor(s) not found!
Jul 29 11:31:46 nvdpi npm[1709]: child_process.js:669
Jul 29 11:31:46 nvdpi npm[1709]:     throw err;
Jul 29 11:31:46 nvdpi npm[1709]:     ^
Jul 29 11:31:46 nvdpi npm[1709]: Error: Command failed: /usr/bin/sensors *-i2c-1-48
Jul 29 11:31:46 nvdpi npm[1709]: Specified sensor(s) not found!
Jul 29 11:31:46 nvdpi npm[1709]:     at checkExecSyncError (child_process.js:629:11)
Jul 29 11:31:46 nvdpi npm[1709]:     at execSync (child_process.js:666:13)
Jul 29 11:31:46 nvdpi npm[1709]:     at getSensors (/usr/local/var/draws-manager/webapp/io.js:45:15)
Jul 29 11:31:46 nvdpi npm[1709]:     at Timeout._onTimeout (/usr/local/var/draws-manager/webapp/io.js:118:27)
Jul 29 11:31:46 nvdpi npm[1709]:     at ontimeout (timers.js:436:11)
Jul 29 11:31:46 nvdpi npm[1709]:     at tryOnTimeout (timers.js:300:5)
Jul 29 11:31:46 nvdpi npm[1709]:     at listOnTimeout (timers.js:263:5)
Jul 29 11:31:46 nvdpi npm[1709]:     at Timer.processTimers (timers.js:223:10)
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! code ELIFECYCLE
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! errno 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! webapp@0.0.1 start: `node ./bin/www`
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Exit status 1
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! Failed at the webapp@0.0.1 start script.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR! A complete log of this run can be found in:
Jul 29 11:31:46 nvdpi npm[1709]: npm ERR!     /root/.npm/_logs/2020-07-29T16_31_46_715Z-debug.log
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Main process exited, code=exited, status=1/FAILURE
Jul 29 11:31:46 nvdpi systemd[1]: draws-manager.service: Failed with result 'exit-code'.
lines 30-69/69 (END)
 


Re: RPi kernel upgrade problem

Basil Gunn
 

Until further notice please do not upgrade the kernel on your RPi.

Linux kernel 4.19.118 is OK
Linux kernel 5.4.51 has MANY problems

Run this to get your current kernel version:
uname -r

The following commands will upgrade your kernel.
Do NOT use them for a while:

apt-get dist-upgrade
apt full-upgrade

/Basil N7NIX


Re: DRAWS™ Manager Demo #drawsmanager

Basil Gunn
 

I believe the problem is with one of the drivers using i2c in the latest
kernel which causes the sensors command to not run. Could you please
post the console output of these 2 commands:

uname -a
journalctl -u draws-manager.service

Thanks,
/Basil n7nix

Charlie Hein <chein@bellsouth.net> writes:

OH! Thanks for the grace applied to my ignorance, Gayland!

John: Here is the output:

pi@nvdpi:/etc $ cd
pi@nvdpi:~ $ which node
/usr/bin/node
pi@nvdpi:~ $ which npm
/usr/local/bin/npm
pi@nvdpi:~ $

Charlie (N4NVD)


Re: DRAWS™ Manager Demo #drawsmanager

Gayland Gump
 

No, problem.  Been there, done that and am still there more often than I care to admit.

Gayland
KG7GCF


On Wed, Jul 29, 2020 at 11:13 AM Charlie Hein <chein@...> wrote:
OH!  Thanks for the grace applied to my ignorance, Gayland!  

John:  Here is the output:

pi@nvdpi:/etc $ cd
pi@nvdpi:~ $ which node
/usr/bin/node
pi@nvdpi:~ $ which npm
/usr/local/bin/npm
pi@nvdpi:~ $ 

Charlie (N4NVD)


Re: DRAWS™ Manager Demo #drawsmanager

Charlie Hein
 

OH!  Thanks for the grace applied to my ignorance, Gayland!  

John:  Here is the output:

pi@nvdpi:/etc $ cd
pi@nvdpi:~ $ which node
/usr/bin/node
pi@nvdpi:~ $ which npm
/usr/local/bin/npm
pi@nvdpi:~ $ 

Charlie (N4NVD)


Re: which instance of 'direwolf.conf' should I be using?

Charlie Hein
 

Yes, I all set - now we see if it actually runs!

Charlie

601 - 620 of 5630