¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: FLdigi is slow and has a framerate

 

Turns out it's Wayland. For most other apps, it's fine, but Fldigi shows how hard it's keeping up.

Switched back to X.org as the screen renderer, no further issues.


FLdigi is slow and has a framerate

 

I just installed Fldigi on a fresh install of Raspbian on a 4GB Pi 4 with 73 Linux. When I run Fldigi, the mouse has a frame rate and it behaves like there's a graphics issue. As soon as I try to run a top command, Wayland is the resource hog followed by Fldigi. Not sure where to go next, but I know that on my other machines, it doesn't do this, just on this Pi 4. Not sure what else to look at or if there's another way to build it.

Any thoughts or hints would be helpful.


Random issues I've been coming across this week - multiple boards

 

I'm trying three different builds to see what type of board PC I want to use in a go box with a Xiegu G90 as my main POTA kit. All other hardware is a Digirig and the same screen.

First board: Le Potato == Installed their build of Raspbian, then 73 Linux. The first time I try to TX on any app, radio locks up with 0W TX
Second PC - Dell Inspiron I had lying around - Ubuntu 22.04 with 73 Linux - Can't install JS8Call and wsjt-x at the same time due to repo conflicts
Third board - RasPi 4B 4GB with 64bit Raspbian and 73 Linux - Fldigi is extremely slowing down the machine.

I don't want to use a laptop as my main POTA machine, so I'm going to work on figuring out what the issue is with the Pi 4 first. I'm not seeing much about Fldigi slowing down on Pi 4, but I'll throw a separate thread out for it.


Re: 73 Linux failed to install VARA

 

On Sat, Feb 17, 2024 at 06:37 PM, Kelly K7MHI wrote:
/g/KM4ACK-Pi/message/12128
Thanks?
I didn't read past pi5 the first time.? In a meeting distracted and on a phone wasn't the best use of your advice.


Re: 73 Linux failed to install VARA

Ericson - J73ESL
 

Was that in responce to what i wrote??


On Mon, Feb 19, 2024, 7:32 AM simona <simona.pisano.70@...> wrote:
and I find this to be rather absurd for the ham radio world where theoretically open and collaborative policies and systems should be privileged. in this sense I believe that the class of amateur radio programmers lives a little disconnected from the world of software. Windows should not be an acceptable alternative and certainly not the only alternative. only commercial logic is what I push for the adoption and use of Windows as an operating system. it seems that the ham world is not aware of what windows means and what logic drives it.
?


Re: 73 Linux failed to install VARA

 

and I find this to be rather absurd for the ham radio world where theoretically open and collaborative policies and systems should be privileged. in this sense I believe that the class of amateur radio programmers lives a little disconnected from the world of software. Windows should not be an acceptable alternative and certainly not the only alternative. only commercial logic is what I push for the adoption and use of Windows as an operating system. it seems that the ham world is not aware of what windows means and what logic drives it.
?


Re: 73 Linux failed to install VARA

 

Bookworm or not the wheezy script is not functioning which is called by this project and you will need to manually install with the provided how to.

k


Re: 73 Linux failed to install VARA

 

¿ªÔÆÌåÓý

Then you would follow the Pi only section.

?

Greg

NZ6E

?

From: [email protected] <[email protected]> On Behalf Of Mark Hogan
Sent: Saturday, February 17, 2024 7:33 PM
To: [email protected]
Subject: Re: [KM4ACK-Pi] 73 Linux failed to install VARA

?

Thanks but im on bullseye not bookworm.


Re: 73 Linux failed to install VARA

Ericson - J73ESL
 

Personally i see BAP/73Linux as a touch and go software... one time it works, u turn on the pi and it stops...?
I have long since given up on that and just do individual software installs.
It would also be important to note that ham radio software still has a long way to go when moving over to the linux world.. Toooo many of the most common software is written and developed for windows based machines, and the developers have no inclination to move to linux.
This is a big issue.

On Sat, Feb 17, 2024, 7:18 PM Mark Hogan <ml.hogan@...> wrote:
I¡¯ve tried twice on two fresh bullseye pi installs and both time I see this, what am I doing wrong.?

Mark Hogan


Re: 73 Linux failed to install VARA

 

Thanks but im on bullseye not bookworm.


Re: 73 Linux failed to install VARA

 


73 Linux failed to install VARA

 

I¡¯ve tried twice on two fresh bullseye pi installs and both time I see this, what am I doing wrong.?

Mark Hogan

_._,_._,_


Old radio/pi help on VARA

 

Im going to be long winded here at my first post to try to describe my station and issues/opportunities :)

I have a Pi4 running KM4ACKs 73 linux into a digirig for js8call and wsjtx.? Antenna is a AG6IF Talated Balun Loop 254' in a NVIS configuration. Im using a SGC-2020 for the rig.? I have great results with the js8 and ft8, but they use rts to key the radio.??
I also use the same digirig to my 2980 for VARA FM, which is how I did my Winlink Wednesday checkin last week and this morning, (my first two ever).
I can not get pat to key the radio on VARA or ardop. Tried true and false.
If I install flrig, it breaks my VARA FM.? Tried that and had to unload and reload pat, vars ardop etc.??
In his videos Jason says to use pat, not winlink on the PI, and Im not savy enough to setup winlink in wine without some guidance.??
Any ideas for me would be apreciated.? I burned two new SD cards last night and setup the full suite of 73 linux on them so I can try this.? I enjoy JS8/FT8 and leave the rig running on 40 JS8 when its free (most of the time) so if I can get VARA HF running I'd like to keep the JS8 available.??

I tried my KX3 and signalink on the windos machine last night.? I have good sounding tones (to me) and pskreporter shows I was heard in a fair smattering of states last night, but no winlink VARA HF connections were able to be made at 10watts.??

Im new to this whole new digital world, ran a multi rig bbs in the early 90's but this is a new world to me.

Of no interest here I also am running an APRS digi with DIGIPI and a digirig to a 2980 because there is not APRS digi NW of Tulsa in Osage County and I'm at 1018' with mine so its a good neighbor coverage thing.??

Thanks?
Mark Hogan N5OBC EM16ve


"/home/pi/tempardop/tempardop1.txt: No such file or directory" after running an update in pi-build

 

It's basically just that.
Ran an update on BAP. Just keeping things fresh and up to date

The config.json got borked, but I always keep backup of that.

Now when I try and run pat connect/autopat, I get the above error.

I'm assuming it's from some place in the autopat script it's being called, likely the cached file that defines the 80/40/20m for auto connections, but I'm uncertain of where that process might be breaking.

Pat from the web UI does work, and I can dial other stations, so I know the pat config itself is functional.

?

Any hints?


Re: GPS / winlink issue with 73linux & bookworm 64 bit

 

Finally getting back to this GPS issue - progress!!

Kelly, thanks for your input. It's greatly appreciated. I was able to search the BAP forum and I think I found what you are referring to.

First, for some reason, Ruby wasn't installed when I ran the 73linux?script.? No big deal I though, so I just?did a sudo apt-get install ruby and moved on.

For reference, here is what I have found so far. I was able to get the grid square to display in conky by running the following:

sudo apt-get install rubygems
sudo gem install gpsd_client
sudo gem install maidenhead

I also read somewhere someone added this too. So I did as well. Not sure if it's needed though.
git clone

So all of the above gets my conky to display my grid. Now when I try to set my grid square in Pat Menu, it doesn't seem to save it.

When I click on GPS grid update, it shows my grid. When I click on Update Pat, it appears to save but it really doesn't. Same with Manual Grid Update. Also on Pat's main menu grid is normally displayed in the lower left corner but nothing is there.

Thanks in advance for your help!
?
-- Mike WB8ERJ

Geeze! What is he up to now?


Re: GPS / winlink issue with 73linux & bookworm 64 bit

 

Need to make sure ruby and the gems for maidenhead install if I recall, few threads on it and there is an expanded script to also update all your apps.?


few threads in groups?


k


GPS / winlink issue with 73linux & bookworm 64 bit

 

Hello,

Just made a fresh install of Bookworm 64bit on a Pi4 8GB ram with a GPS dongle. I am having a couple of problems with respect to GPS.

First of all, I watched this video titled "Gridsquare in Conky :: 73Linux":


Everything looks good there. cgps works fine and properly picks up my Lat / Long info. However Conky shows no grid data. Additionally when I go into Manage Pat Menu and try to do a Manual Grid Update, I enter my grid, and it says that it has updated the grid, but nothing is shown for the grid when I return to the main menu. I tried exiting out of Pat Menu and going back in but the grid square data isn't being saved.

One clue though, when I open a terminal window and run ./bin/conky/grid I get the following error:

/usr/bin/env: "ruby": No such file or directory

grid is in the directory and it is marked as executable

Thanks in advance for any help.

-- Mike WB8ERJ


Geeze! What is he up to now?


Re: New Pi 5 Build

 

With the new sd imaged I did a full system update.? This time it found a bunch of things to update.? After a reboot the command like for Build a Pi and it worked perfectly as it has on my Pi 4 units.

Not sure what happened, maybe corrupt image or bad card.? Either way its working.

Thanks for your help


Re: New Pi 5 Build

 

I just booted a fresh SD, my only suggestion would be make sure ¡°apt-get update¡± is getting all the distribution lists??


K


Re: New Pi 5 Build

 

I uploaded the stock 64 bit image from the raspberry pi imager.? I have a spare sd card, so I'll try and load a fresh image incase something went wrong with the first one.