On Fri, Nov 12, 2021 at 08:49 AM, Richard Kimmerling LICW # 890 SKCC # 23774 wrote:

Side note - bullseye did not see my ic-7300 when I plugged it in. Maybe it doesn’t come with the silicon graphics driver anymore(?)

It recognized my 705. At one point during testing yesterday, I did have to unplug and plug the 705 back in before it saw it.
?
--

What makes you think it isn't powering up without the monitor attached? After applying power, how are your trying to connect (VNC or SSH)? Assuming you have just flashed the OS to the card, you will need to enable SSH first. Then SSH into the Pi, run sudo raspi-config and enable VNC. You will now be able to VNC into the pi using a VNC client. If you get the "can't display desktop" error, see this video

--

Trying to power up my raspberry pi 4 headless. The issue I'm having is I need to have my
7 in monitor plugged in for the headless to work.
?I would like to have the pi to power up headless without having the monitor connected. How do I
make this happen?

? Wayne? VE1NR

Hi,

Maybe you know that recently Raspberry Pi OS got a next stable upgrade, which is based on Debian 11 (codename Bullseye). That is nice, because a lot of new stuff is packaged in the distro and bugs are fixed. Our hamradio use of Raspberry Pi computer relied on some really nice programs and Build-a-Pie script to install them. Alas the new version of the Raspberry Pi OS makes things a little bit difficult for a while. For example we can't install recent version of wsjtx on Bullseye, because the binary package from the author is compiled for older Raspberry Pi OS version and the libraries needed for running wsjtx are old and not available in Bullseye.
But there is some good news - we can install both js8call and wsjtx from source. The build process is similar for both of them and we need about 45-60 minutes for the task. Most of the time is spent on actual compiling and we doesn't have to stay in front of the computer.

So let's begin

JS8CALL

First we need to allow installing source packages in Raspberry Pi OS

sudo nano /etc/apt/sources.list

Look for these lines:

# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src bullseye main contrib non-free rpi

Remove the #? sign in front of deb-src so the line becomes like this:

deb-src bullseye main contrib non-free rpi

Save and exit.


Next we need to make sure the system is up to date:

sudo apt update

sudo apt upgrade -y


Let's install the needed libraries for js8call building:

sudo apt-get build-dep js8call -y

Last command installs everything including hamlib. If we are happy with older version of hamlib, provided by Raspberry Pi OS we doesn't need to remove it. But if we use hamlib via BAP we need to remove hamlib:

OPTIONAL STEP, see above

sudo apt remove libhamlib4 libhamlib-dev


Next steps are well documented in js8call source code:

mkdir ~/hamlib-prefix

cd ~/hamlib-prefix

git clone src


### Get the JS8Call Source

mkdir ~/js8call-prefix

cd ~/js8call-prefix

git clone src


Compile hamlib:

cd ~/hamlib-prefix/src

./bootstrap

mkdir ../build

cd ../build

../src/configure --prefix=$HOME/hamlib-prefix \

??? --disable-shared --enable-static \

??? --without-cxx-binding --disable-winradio \

??? CFLAGS="-g -O2 -fdata-sections -ffunction-sections" \

??? LDFLAGS="-Wl,--gc-sections"

make

make install-strip


I prefer to run make command with -j 4 option to utilize all 4 cores of the RPi 4

if you like execute

make -j 4

instead of

make


### Compile JS8Call


cd ~/js8call-prefix/src

mkdir ../build

cd ../build

cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix -D CMAKE_INSTALL_PREFIX=~/usr/local ../src

make

make package


again if we need speed execute make -j 4 instead of make

Upon finishing there is a message like this:

CPack: - package: /home/pi/js8call-prefix/build/js8call_2.2.1-devel_armhf.deb generated.

The package is ready for install via apt command:

cd ~/js8call-prefix/build/

sudo apt install -y ./js8call_2.2.1-devel_armhf.deb


Congratulations we have built and installed JS8Call. We can save the .deb package for later use in Bullseyeor to share it with a friend.


###WSJTX


The process is similar. Most of the tasks are done in js8call steps.

Install the needed libraries:

sudo apt install qtmultimedia5-dev libqt5serialport5-dev qttools5-dev qttools5-dev-tools libboost-all-dev libfftw3-dev libreadline-dev libusb-1.0-0-dev libudev-dev portaudio19-dev


Then we prepare a directory for compiling, download the source and unzip it and start the compiling. At the end we have a .deb package again, ready for install:


mkdir ~/wsjtx-build

cd ~/wsjtx-build

wget

tar xzf wsjtx-2.5.2.tgz

mkdir build

cd build

cmake -DWSJT_SKIP_MANPAGES=ON -DWSJT_GENERATE_DOCS=OFF ../wsjtx-2.5.2

cmake --build .

cmake --build . --target package


The last command produces our .deb file and shows it's location in the terminal window:

CPack: - package: /home/pi/wsjtx-build/build/wsjtx-prefix/src/wsjtx-build/wsjtx_2.5.2_armhf.deb generated.

It can be installed by apt command:
sudo apt install /home/pi/wsjtx-build/build/wsjtx-prefix/src/wsjtx-build/wsjtx_2.5.2_armhf.deb

We could also save the .deb file for future use.


OK that's was all, I hope you can get js8call and wsjtx running on your Raspberry Pi computers powered by Bullseye.

If you have questions please don't hesitate to ask me.

--
73 Daff, LZ1DAF

I ran the BAP update, and it seems to have fixed itself. And you're right, I wasn't using the KISS version. All is well! Thanks a billion!!!

On Fri, Nov 12, 2021 at 01:27 PM, Dafcho Tabakov wrote:

Good news - js8call compiles with latest hamlib 4.3.1 on Bullseye RPi OS
I have documented my steps and the best part of all is that we end with a .deb file ready for install. I may distribute mine deb file if somebody wants it for test purposes (I didn't put any exploits :) ) And if we may save the deb file for future use or reinstall. I will attach the howto in another email later.

Now it's time for wsjtx

Dang! I was hoping you worked on WSJTX first. I got JS8 working as well.



--

I've been using a Pi-zero W as a portable digital station, running on a battery and connected via a small USB hub to a sound card, my rig, and a GPS dongle. I connect with VNC to a small Kindle tablet either on a network or running as a hotspot out in the field. It works, but barely. When in WSJT-X on FT-8 the time to decode a signal, even overclocked by 10% and with Conky shut off, was close to 20 seconds. Since the cycle time is 15 seconds...well, as you might imagine there are a number of repeats. I never could get FLdigi to load, but had a lot of success with a program called LinPSK for PSK modes and RTTY. The difference is probably because LinPSK can only decode one signal at a time. To show the load on this original Pi-zero, just starting it up in graphical mode with Conky running and nothing else consumed about 50% of the CPU, which is why I had to shut that down when operating.

So got a Pi-zero 2 W this past week, after finding someone that had them in stock, and it was only $12 plus almost that in shipping, but I have it. I started up the old Pi and commented out all my overclocking commands, then just swapped the SD card over to the new Pi-zero 2 W. I got nothing on boot up, but connected a monitor, keyboard, and mouse and found it had actually booted, but had WiFi turned off. The WiFi country code was also blank. So I fixed that and turned WiFi back on only to find the IP address had changed. I fixed that, and now it was operating headless again, and WOW! The boot up is now very fast and just sitting with Conky running it is only using about 6% of the CPU. I started FT-8, leaving Conky on, and it is decoding almost immediately, within a few seconds of the cycle end or right at the end. The CPU doesn't get over 40% or so when decoding, either. Fantastic! I will be trying to load Fldigi again and see if that works, but so far this is a huge improvement.

=Vic=

Good news - js8call compiles with latest hamlib 4.3.1 on Bullseye RPi OS
I have documented my steps and the best part of all is that we end with a .deb file ready for install. I may distribute mine deb file if somebody wants it for test purposes (I didn't put any exploits :) ) And if we may save the deb file for future use or reinstall. I will attach the howto in another email later.

Now it's time for wsjtx

--
73! Daff, LZ1DAF

Thanks Jason. I keep all my Pis on the same OS and configuration, I backed off of Buster to Stretch a while back because of various issues. With Bullseye out it is probably time to think about Buster again. Thanks again for your help.? -Fred KD9CCE?

开云体育

Side note - bullseye did not see my ic-7300 when I plugged it in. Maybe it doesn’t come with the silicon graphics driver anymore(?)

Hey hivemind,

Anyone using a serial gps module, like a Bietian? Is their any additional scripts that have to be written? If not how do I get the information for the serial # for the GPS Update Tool?

Thanks,
de K2PMD Paul

On Fri, Nov 12, 2021 at 02:54 AM, Dafcho Tabakov wrote:

I'm going to build from source js8call and wsjtx later today. There are a lot of dependencies for the build process and we need to pull some dev packages.

There is a possible workaround for these 2, but then we need to install hamlib via bullseye repository and don't build it via BAP. There is a js8call latest version and wsjtx is v.2.3.0. They can be installed via apt command:
sudo apt install js8call wsjtx

This is for people who have installed Bullseye and doesn't want to wait for fixes.

it would be a huge help if you documented and posted each step you take when compiling each from source.
?
--

Update- Everything Works!!! Thanks for all the spot-on advice.
’73 ?fer now
best to you & yours.
hope to catch you down the log.

Glad you are back up and running. For the record, I haven't gotten WSJTX to load on Bullseye yet either.

--

You got me on this one Fred. I don't think I ever used conky with Stretch. If might be something specific to that version of Pi OS. I haven't had issues with Buster in quite a while now. It is running stable. I can't say the same for the latest version Bullseye.
--

It's fine to run it on port 8080. The only reason for running it on 5000 is to also allow you to run the Emergency Email Server on the same Pi which requires port 8080. If 8080 is working for you, change your Pat Port in Pat Menu settings to 8080 and you should be in business.
--

It is quite possible that the beta mobilinkd in Pat Menu isn't working correctly and I don't have a TNC3 to test with. If you start it manually from the command line, are you able to send/receive winlink messages? If not, what's the output of your direwolf?

--

Hi Larry,

This sounds specific to FLDIGI. You might try asking in their forum as well. /g/linuxham/topics

--

I'm going to build from source js8call and wsjtx later today. There are a lot of dependencies for the build process and we need to pull some dev packages.

There is a possible workaround for these 2, but then we need to install hamlib via bullseye repository and don't build it via BAP. There is a js8call latest version and wsjtx is v.2.3.0. They can be installed via apt command:
sudo apt install js8call wsjtx

This is for people who have installed Bullseye and doesn't want to wait for fixes.

--
73 Daff, LZ1DAF

Glad you got the sound card figured out. Changing your call is easy. Just click on Conky-Prefs from the main pi menu?
--

Thanks for the suggestion, Jason,?

When I checked the sound card settings in WSJTX after plugging in the second monitor and rebooting - the sound card disappeared and was no longer an option in the selection list and the original sound card entries for microphone and speaker were showing not found (see picture), I went back to a single monitor and the sound card reappeared.

I then tried to overcome the problem with the status window in Build-a-Pi which was no longer transparent when using two monitors - please see the attached photo. I thought that by swapping it might correct this problem, so I swapped the monitor connections to the HDMI ports so that the monitor connected to HDMI-1 was now connected to HDMI-2 and vice versa. On reboot the sound card was now recognized and WSJTX works :) I can't explain why but if this worked for me then maybe someone else can benefit from trying the same.

BTW is there an easy way to change your callsign on the status panel as mine has changed to my US call since I originally installed build-a-Pi.

Thanks again and great work.

Richard W5ARH