Portsdown 5 Installation

[NJ6E]

Hello,

I have been attempting to install Portsdown 5 from https://github.com/davecrump/portsdown5 and have run into a problem when Stage 2 installation begins. My setup is a Raspberry Pi 5 4GB with the DSI 7" touchscreen attached. The installation proceeds as expected until the end of Stage 1, when the installer reboots to begin Stage 2 installation. At that point, reboot begins, the screen backlight comes on, and then all apparent installation activity stops. There is no text on the screen and no LEDs on the Pi 5 flash to indicate activity. I have left it in this state for several hours, with no apparent activity. At that point I can log into the Pi via the terminal, and I note that the installation log does include a "Stage 2 started" entry.

Any ideas on how to proceed with the installation would be appreciated. The DSI touchscreen is nominally functionally equivalent to the official Raspberry Pi screen (V1), so I was wondering if the presence of this screen could be related to the problem.

Thanks and 73,
Stan NJ6E

[G8GKQ]

Hi Stan

The Portsdown 5 is not yet formally released and does not have even 50% of the Portsdown 4 functionality. DATV transmit capability is proving particularly difficult to implement.

During the development process occasionally I have released builds that have been broken, and you have caught one of those.

I am about to push a new release that fixes the stage 2 build problem, but there are still quite a few other bugs that cause the system to stop responding. However, DATV receive, Stream Viewer and LimeSDR BandViewer are quite robust as long as you do not try to use the "View Snap" functionality.

More details in my talk in CAT 25 on Saturday.

73

Dave

[g0mjw]

Might be worth hiding the builds to avoid this.

[g8lce]

If you hide the pages then people will not know how much effort and time is being spent on this project. There might be some useful support and feedback from unexpected sources.

Martin G8LCE

[g0mjw]

If you hide the pages then people will not know how much effort and time is being spent on this project. There might be some useful support and feedback from unexpected sources.

Martin G8LCE

I only meant hide until they are ready for a general release. Hide is more don't publish than hide. Otherwise, it is common for non-software developers to have an expectation that things work because they are there, even though incomplete.

Mike

[ZL3TCM]

Hi everyone greetings from down under, having run Langstone for a few weeks I decided to up grade to Portsdown 5 and I too get the same issues as the first msg on this list. So I assume just wait till a version comes out that works, in the meantime is there any issue that will stop me running Portsdown v4 on my Pi5 setup? I have spent a few hours already getting this far until I read the forum and im not the only one.

Regards Rob ZL3TCM Christchurch NZ

[g0mjw]

Hi everyone greetings from down under, having run Langstone for a few weeks I decided to up grade to Portsdown 5 and I too get the same issues as the first msg on this list. So I assume just wait till a version comes out that works, in the meantime is there any issue that will stop me running Portsdown v4 on my Pi5 setup? I have spent a few hours already getting this far until I read the forum and im not the only one.

Regards Rob ZL3TCM Christchurch NZ

Hi Bob

Specifically what gave you the idea that upgrading to a PI5 was a good idea? It is an honest question, not a criticism, as we need to prevent people from thinking this, wasting time and money, getting frustrated etc.

Also to be clear, the PI5 does not work with Portsdown4 and never will. The PI5 is very different hardware. Key parts like hardware video encoders and decoders are missing. It is faster, has some nice new features, but it is most definitively not an upgrade, at least not yet. It needs a complete re-write of the code and it isn't clear yet it can be made to encode video in software as well as the PI4 can in hardware.

Mike