forum.pistar.uk

@KE7FNS
You wanted the error message, voila here it comes:
I have flashed an older version (4.1.0RC7) onto the SD and the Nextion worked fine again.
Then I ran an update an here is the error message concerning the Nextion Drivers (starts in Line 10)
*********************

Update Running
Starting update, please wait...
Stopping Services...
Done
Updating DV Binaries...
Updating /usr/local/bin...
From https://github.com/AndyTaylorTweet/Pi-S ... naries_Bin
* branch master -> FETCH_HEAD
448ec19..2997ba0 master -> origin/master
error: The following untracked working tree files would be overwritten by merge:
NextionDriver
Please move or remove them before you merge.
Aborting
Updating 448ec19..2997ba0
Updates were not successfull, reverting to Pi-Star original files...
HEAD is now at 2997ba0 Adding Nextion Driver binary
Done
Updating Pi-Star Binaries...
Updating /usr/local/sbin...
From https://github.com/AndyTaylorTweet/Pi-S ... aries_sbin
* branch master -> FETCH_HEAD
429bd9b..ad2da0d master -> origin/master
error: The following untracked working tree files would be overwritten by merge:
nextiondriver.service
Please move or remove them before you merge.
Aborting
Updating 429bd9b..ad2da0d
Updates were not successfull, reverting to Pi-Star original files...
HEAD is now at ad2da0d Update pistar-upgrade
Done
Updating Hostfiles...
Done
Updating Dashboard...
Updating /var/www/dashboard...
From https://github.com/AndyTaylorTweet/Pi-Star_DV_Dash
* branch master -> FETCH_HEAD
f3390e2..c4392cc master -> origin/master
Updating f3390e2..c4392cc
Fast-forward
admin/admin.php | 2 +-
admin/config_backup.php | 3 +
admin/configure.php | 278 ++++++++++++++++++++++++++++++++++++-----
admin/download_modem_log.php | 7 +-
admin/expert/ssh_access.php | 6 +-
admin/expert/upgrade.php | 4 +-
admin/live_modem_log.php | 4 +-
admin/sysinfo.php | 4 +-
admin/update.php | 4 +-
admin/wifi.php | 72 ++++++-----
admin/wifi/phpincs.php | 32 ++++-
admin/wifi/styles.php | 2 +
config/version.php | 2 +-
css/pistar-css-mini.php | 16 +++
css/pistar-css.php | 16 +++
dstarrepeater/link_manager.php | 2 +-
index.php | 37 +++++-
lang/catalan_es.php | 5 +
lang/chinese_cn.php | 5 +
lang/chinese_hk.php | 5 +
lang/chinese_tw.php | 5 +
lang/dutch_nl.php | 5 +
lang/english_uk.php | 5 +
lang/english_us.php | 5 +
lang/french_fr.php | 5 +
lang/german_de.php | 5 +
lang/greek_gr.php | 5 +
lang/italian_it.php | 5 +
lang/japanese_jp.php | 5 +
lang/norwegian_no.php | 5 +
lang/portuguese_br.php | 5 +
lang/portuguese_pt.php | 5 +
lang/romanian_ro.php | 5 +
lang/slovenian_sl.php | 5 +
lang/spanish_es.php | 5 +
lang/spanish_mx.php | 5 +
lang/thai_th.php | 5 +
lang/turkish_tr.php | 5 +
mmdvmhost/functions.php | 45 +++----
mmdvmhost/lh.php | 15 ++-
mmdvmhost/localtx.php | 11 +-
mmdvmhost/nxdn_manager.php | 111 ++++++++++++++++
mmdvmhost/p25_manager.php | 111 ++++++++++++++++
mmdvmhost/repeaterinfo.php | 14 +--
mmdvmhost/tgif_links.php | 94 ++++++++++++++
mmdvmhost/tgif_manager.php | 163 ++++++++++++++++++++++++
mmdvmhost/ysf_manager.php | 136 ++++++++++++++++++++
47 files changed, 1181 insertions(+), 115 deletions(-)
create mode 100755 mmdvmhost/nxdn_manager.php
create mode 100755 mmdvmhost/p25_manager.php
create mode 100755 mmdvmhost/tgif_links.php
create mode 100755 mmdvmhost/tgif_manager.php
create mode 100755 mmdvmhost/ysf_manager.php
Done
Updating PiStar-Firewall...
Done
Starting Services...
Done
Updates complete, sleeping for a few seconds before making the disk Read-Only

I have done a few tests, its even worse, its not only the display, the hotspot itself is dead also

I have flashed a 4.1.0 RC7 - everything works fine, display and Hotspot
--- ran update, lots of messages, some error messages but still everything works
upgraded to 4.1.0 RC8 - everything works fine
--- lots of messages, some error messages but still everything works
upgraded to 4.1.0 Final - everything works fine
--- lots of messages but still everything works
upgraded to 4.1.1 - everything works fine
--- lots of messages but still everything works
upgraded to 4.1.2 - Display and Hotspot dead

-- this is the Upgrade Message from 4.1.1 to 4.1.2
*********
Starting upgrade, please wait...
Detected Pi-Star 4.1.1 running on RPi hardware, attached to mmdvmhsdualhatgpio modem...
Created symlink /etc/systemd/system/systemd-rfkill.service → /dev/null.
Created symlink /etc/systemd/system/systemd-rfkill.socket → /dev/null.
Created symlink /etc/systemd/system/multi-user.target.wants/mobilegps.service → /lib/systemd/system/mobilegps.service.
Upgraded from 4.1.1 to 4.1.2...
Sleeping a few seconds before making the disk Read-Only...
Finished*

FINAL CONCLUSION: the upgrade from 4.1.1 to 4.1.2 killed all my 7 Hotspots and their displays
I will now revert back to 4.1.1 on all Hotspots for now.

I think this needs a closer look. Almighty Andy where are you? (again looking over my shoulder while I type??

Uli
DJ5UW

DJ5UW wrote: ↑Wed May 27, 2020 4:28 pm FINAL CONCLUSION: the upgrade from 4.1.1 to 4.1.2 killed all my 7 Hotspots and their displays
I will now revert back to 4.1.1 on all Hotspots for now.

I think this needs a closer look. Almighty Andy where are you? (again looking over my shoulder while I type??

Uli
DJ5UW

Yup almost...

So the stuff in the upgrade to 4.1.2, has new services for the MobileGPS stuff, that should not kill your screens, unless maybe you turned it on.
I cleaned out some old services like RFKill and exim, those have been dead a long time - again, should have 0 side effects.
Added a whole bunch of captive portal stuff - again should not touch serial ports or screens

So - my only guess at this point is the mobile GPS feature - is that "on" in your config page?
And what is the Nextion port set to at the top of the config page?

There where a bunch of error and system messages popping up during the update/upgrades from 4.1.0RC7 to 4.1.2. I have copied them to textfiles
They might be interesting for you to go through. If you want, I can send you an email with the textfiles.

The whole process from 4.1.0 RC7 to 4.1.2 is reproducable, I have done it a few times.
In 4.1.2 the display AND the Hotspot are dead meaning no RF reception from the HT into the Pi and nothing coming in from the net.

The mobile GPS feature is turned off, I did not touch it as I do not have a GPS receiver. Nextion port is set to /dev/ttyUSB0 as it was before, didnt touch that either.

Uli
DJ5UW

can we do a TeamViewer session or give me SSH access please - either way - I am sure we can get you back on the air in no time
Please make sure you DM/PM me rather than posting information here...

I have MMDVMHSHat and MMDVMHS-Dual Hat modem JumboSpots, and they also have failed with installation of 4.1.2 PiStar.

I have Oled3 Oleds on the MMDVM modem boards.

The OLED is attached through /dev/ttyAMA0 port.

After the 4.1.2 update, I noticed that there are TWO of these ports listed on the configuration options list.

Also, while the new GPS option is off, it also lists devices /dev/ttyAMA0 and (defaults to) /dev/ttyACM0.

I've tried selecting the second AMA0 port for the Oled3 and that also hangs up when PiStar tries to communicate to MMDVM.

I've tried setting display type to "None" and Port to "None" and rebooting.

None of this has resolved the problem.

One of the symptoms is that under the Radio Info window, the FW and TXCO frequency information is NOT displayed after the R4.1.2 upgrade because initialization hangs up when PiStar tries to communicate with the MMDVM modem.

The resolution for me (brute force) was to shut OFF the OLED and port selections in MMDVMHost then backup the configuration. I then downloaded the new R4.1.2 system, rebuilt the SD Card (with the configuration .zip file in the BOOT directory of the SD card) and let the node rebuild itself.

Once it's done with rebuilding, the WiFi should be working as before, and you can login to the node then change the display back to OLED3 and the correct /dev/AMA0 port. There will only be one of these listed in the dropdown within MMDVMHost Configuration.

I suspect something damaged the /dev/ttyAMA0 port definition in Raspian.

Note that my OpenGD77 based hotspot was not damaged (it doesn't use the MMDVMHats through GPIO, instead connecting via USB).

KE7FNS wrote: ↑Thu May 28, 2020 12:36 am

kd2lh wrote: ↑Wed May 27, 2020 11:55 pm The OLED is attached through /devttyAMA0 port.

After the 4.1.2 update, I noticed that there are TWO of these ports listed on the configuration options list.

Its been a while since I've tinkered with an OLED but I'm pretty sure /dev/ttyAMA0 is the incorrect port for an OLED, it should be set to modem.

The MMDVM should be using i2c to communicate with the OLED board, not serial communications.

/dev/ttyAMA0 is the RPi serial port that should only be connected to the MMDVM.

Maybe try setting the display to none, and seeing if things magically work all the sudden.

I suspect you have two things trying to access the same serial port causing the failure.

The OLED IS attached through the /dev/ttyAMA0 port. Once I rebuilt the Raspian system from the R4.1.2 download image, and restored the configuration, then added back Oled3 and /dev/ttyAMA0 to the MMDVM Display Type configuration it started working fine again.

After some digging, what seems to be happening is that NextionDriver is starting when it's not necessary wanted.

At which point, it steals the control away from MMDVMhost, and MMDVMhost can't reliably get signals to/from the board.

Just for giggles, on a broken one, try this:

Drop to shell.
rpi-rw
sudo -s
! kill any running NextionDriver
killall NextionDriver
! make sure it's really dead
ps -aef | grep -i nextion
! Start MMDVMHost manually
MMDVMHost /etc/mmdvmhost

Then watch the log and see if it still times out:

tail -f /var/log/pi-star/MMDVM*

I've already refreshed and fixed my broken ones, so I can't send you it as it was unfortunately. So now I'm trying to walk through from 4.1.0 to try and reproduce.

One thing I've noticed in walking through is that at one point in updating to 4.1.1, it appears to change from 'modem' to '/dev/modem'. Problem is, /dev/modem isn't actually a tty device. It should just be 'modem'.

I: 2020-05-28 02:51:31.252 Display Parameters
I: 2020-05-28 02:51:31.252 Type: Nextion
I: 2020-05-28 02:51:31.252 Port: /dev/modem
I: 2020-05-28 02:51:31.252 Brightness: 50
I: 2020-05-28 02:51:31.252 Clock Display: yes
I: 2020-05-28 02:51:31.252 Display UTC: no
I: 2020-05-28 02:51:31.252 Idle Brightness: 20
I: 2020-05-28 02:51:31.252 Temperature in Fahrenheit: no
I: 2020-05-28 02:51:31.252 Screen Layout: DIY by ON7LDS
I: 2020-05-28 02:51:31.252 Display baudrate: 9600
E: 2020-05-28 02:51:31.252 Cannot open device - /dev/modem
E: 2020-05-28 02:51:31.252 Cannot open the port for the Nextion display

Not sure yet if that cascades into more failures in the next run of update. Still walking through it.