Re: ARDOP modem not stopping
When this happens, can you run:
kill ardopcf
from the terminal and clear the problem?
?
--
73, de KM4ACK
|
|
|
Re: Can the new Evolve III be upgraded?
Brian,
You¡¯re making me want to buy a new one as well now¡I absolutely enjoy the one I have now and it¡¯s only 5 or 6months old. It doesn¡¯t have the cell modem but I did install a 256gb Micro SD card, and now I use it exclusively with my TT891 and the ATAS120A antenna installed in my car¡works Incredibly well! I¡¯ll hopefully get one that has the cell modem so I can uograde it a bit. Thanks OM!!
73, Danny NF4J?
Sent using the mail.com mail app
On 11/28/24 at 16:04, Brian Dale via groups.io wrote:
From: "Brian Dale via groups.io" <bdale.droid@...> Date: November 28, 2024 To: [email protected]Cc: Subject: Re: [KM4ACK-Pi] Can the new Evolve III be upgraded?
FYI it's not an old/new thing...people have been saying that the "new" ones don't have the cell modem but that's not true. It's luck of the draw. I bought 2 new ones from MicroCenter very recently this year and they both had the cell modems.
toggle quoted message
Show quoted text
Does anybody have any experience running the new Evolve III laptop with the USB-C jack?? Can you upgrade the SDD in this model or only on the older model with the Cellular modem?
?
Old ones are hard to find and the new ones on Amazon all have the USB-C port where the cellular modem(SIM Card) was located?? I have two of the older ones that have a 128GB drive installed where the factory 64 GB drive was located.
?
I want to pickup another Evolve but would like some feedback first
?
Thanks
Dave
|
Re: Can the new Evolve III be upgraded?
FYI it's not an old/new thing...people have been saying that the "new" ones don't have the cell modem but that's not true. It's luck of the draw. I bought 2 new ones from MicroCenter very recently this year and they both had the cell modems.
Does anybody have any experience running the new Evolve III laptop with the USB-C jack?? Can you upgrade the SDD in this model or only on the older model with the Cellular modem?
?
Old ones are hard to find and the new ones on Amazon all have the USB-C port where the cellular modem(SIM Card) was located?? I have two of the older ones that have a 128GB drive installed where the factory 64 GB drive was located.
?
I want to pickup another Evolve but would like some feedback first
?
Thanks
Dave
|
Does current (Nov 2024) 73Linux successfully install Vara on Pi4/64 bit bookworm?
What is the state of installation scripts for VarAC on Pi 4 with 73Linux? ?I believe Wayland was a problem earlier, but now that Raspberry has changed the graphics manager is that still a problem? Do I need to use 32-bit applications, or can I use 64-bit?
?
Ideally, I'm hoping to just run 73Linux update and have everything needed (Wine, etc.) installed, but not sure if that is the current state.
?
P.S. I tried using 73Linux on a new Bookworm OS install, and saw the note about sometimes Vara doesn't install on first try.? I ran 73Linux again with only Vara selected, but it still doesn't appear on Ham apps menu. Is this a known issue?
?
--
---
Steve Johnson
K0OIL
|
When stopping the ARDOP modem from PATMENU it doesn't shutdown.? This is happening on a Wo-We and an Evolve running Mint 22 and a recent 73 Linux build.?
?
Trying to start a packet modem in this condition results in a Direwolf message (run in command window) of "Could not open audio device plughw: 3,0 for input: Device or resource busy? This means some other application is using that device,? The solution is to identify that other application nd stop it.? Pointless to continue without audio device
?
This is using an Evolve laptop or Wo-We.
?
How can I identify what has plughw: 3,0 open?? To get out of this condition takes an extended power down on the computer and powering off the IC-705 for a similar time.
?
Thanks
Dave
?
?
?
|
Can the new Evolve III be upgraded?
Does anybody have any experience running the new Evolve III laptop with the USB-C jack?? Can you upgrade the SDD in this model or only on the older model with the Cellular modem?
?
Old ones are hard to find and the new ones on Amazon all have the USB-C port where the cellular modem(SIM Card) was located?? I have two of the older ones that have a 128GB drive installed where the factory 64 GB drive was located.
?
I want to pickup another Evolve but would like some feedback first
?
Thanks
Dave
|
I've run across this quirk and curious if anyone else has...? ?
?
I use Tri-mode but this also happens with LinBPQ.? ? VARA doesn't accept incoming connections when using a 64 bit system.? ?Below is a screen shot of the VARA virtual TNC on a 32 bit system.? ?You'll notice at the top of the TNC, and highlighted in red, my callsign.? ?When using a 64 bit system, my call doesn't show.? ?Both systems use LABWC / Wayland.
?
Incoming connections work fine with LinBPQ or Tri-mode with 32 bit.? ?Connections are ignored with 64 bit.
?
thanks...
?
Richard? ? ko0ooo
?
?
|
Re: Winlink - Piardopc error
Bryan,
?
FWIW I had the same issue, I downloaded piardopc64 and piardop_GUI64 from here and dropped them into the ardop directory, chmod +x them both then point the pat settings in pat menu at those files instead of the 32 bit versions.? Works great.? I still have problems with rigctl being recognized by pat so I use rigctld and I've actually just bypassed the pat menu altogether and I have two scripts on my desktop.
First is startARDOP.sh contents:
?
#This line is for Xiegu G90
/usr/local/bin/rigctld -m 3070 -s 19200 -r /dev/ttyUSB0 -C rts_state=OFF,stop_bits=2&
?
#Make sure plughw matches card listed under aplay -l
/home/mateo/ardop/piardopc64 8515 plughw:3,0 plughw:3,0&
/home/mateo/ardop/piARDOP_GUI64&
Second is stopAll.sh contents:
?
killall rigctld
killall piardopc64
killall piARDOP_GUI64
?
I also have a standalone startRigCtld.sh that just has the first line to fire up rigctld and then I can still stop it with stopAll.sh
?
|
Re: New Mint on Wo-We 73 Linux build - Packet modem failed to start
Final Update to this problem (I hope)
?
If I start the Wo-We BEFORE powering up a connected IC-705 the Packet modem will fail to start with a Direwolf message that the Audio Codec devices are in use by another process.? Rebooting does not clear this condition even with the IC-705 left powered on.? What clears this condition is if I shut the power off the Wo-We and let it sit for several minutes.? Make sure the 705 is powered up and then power up the Wo-We and it will work again.
?
I don't know how but the Wo-We is maintaining the busy status of the audio codec device after a restart or a short power down,
?
Any thoughts?
?
Thanks.
Dave
?
|
Re: New Mint on Wo-We 73 Linux build - Packet modem failed to start
My problem of starting the Packet modem with PAT Menu is back.? It turns out that it isn't a KISSATTACH issue but a Wo-We PC/Direwolf issue.? Direwolf says that the audio codec for my IC-70r is in use by another process so it quits.? If I unplug my IC-705 and power off the Wo-We and power it on without connecting the IC-705, a aplay -l command still shows the audio codec available.? The codec I am using is:
?
card 3: Device [USB Audio Device], device 0: USB Audio [USB Audio]
? Subdevices: 0/1
? Subdevice #0: subdevice #0
?
The Audio Codec for the IC-705 shows in a aplay -l command even when the radio is not connected and stays listed across reboots and power offs of the PC with the radio disconnected.? Leaving the PC powered off for some period still shows the audio codec there with the radio disconnected but will allow Direwolf to startup OK.
?
A couple of questions:
1.? Is there a command to list processes attached to a device and how would I specify plughw 3:0 as the device I am interested in?
2.? Is there something in Mint that leaves a process attached to the codec?
3.? Is there something in the PC hardware that leaves the device busy from the last boot?
?
This is a total mystery to me
Thanks
Dave
?
|
Re: Autostart JS8Call attached to QDX/QRP radio
My guess would be that the cron is running?as root or some other user, instead of the username that set it up so you are not accessing the config file at startup typically?this is in your home directory at ~/.js8call/js8call.cfg and houses your settings including audio settings adding your username or the user that originally?configured JS8call will fix it.?
something like: @reboot sleep 40 && export DISPLAY=:0 &&? <myusername> /usr/bin/js8call >> /home/pi/js8_start.log 2>&1
would likely yield?the desired results
Just guessing as I don't have a box available to test that theory?on at the moment.
Thanks, Ralph Shepard KE0SWK
On Wed, Nov 20, 2024 at 11:15?AM Jerry P via <jlpainter2014= [email protected]> wrote:
Thanks Dan.? I think you likely on target.? Even if it fails with the Cron job, clicking on the Mic or Speaker icons in the taskbar still show the QDX devices selected as the defaults.
I¡¯ll check out the articles and continue pursuing this.? Will let you know how it turns out.
?
73
Jerry
KD0UXW
?
?
I'm really out of my league here, but feel your pain trying to understand sound devices under Linux with my own QDX, QMX, and X6100 radios and vanilla Debian.
It's probably, first of all, an environment thing.? Cron jobs run under their own limited environment that comes and goes with the job.? Apparently the display environment is available to the job or else you wouldn't even have the JS8/WSJT-X
GUI show up.? I'm guessing that you're logged in as a user with a graphical environment when the cron job launches, otherwise there would be no display environment, either.
Again merely guessing, the ALSA devices are:? a) unavailable to the user under which the job runs;? b) considered busy and not made available to the temporary environment set during the job;? or c) available under the job environment, but
the "connection" to them ends when the job environment disappears and JS8Call is left with some null reference.? Regarding (a), believe it or not, root is blocked from some system services - I presume for the sake of security - so could very well NOT have
access to audio services when executing a job.
These threads might be helpful:?
The solution may basically be getting your login environment shared with the job so the devices are seen persistently.? The threads above have some troubleshooting suggestions that show whether the ALSA devices are even available when the
job runs.
Good luck!? Let us know when you figure it out.
|
Re: Autostart JS8Call attached to QDX/QRP radio
Thanks Dan.? I think you likely on target.? Even if it fails with the Cron job, clicking on the Mic or Speaker icons in the taskbar still show the QDX devices selected as the defaults.
I¡¯ll check out the articles and continue pursuing this.? Will let you know how it turns out.
?
73
Jerry
KD0UXW
?
toggle quoted message
Show quoted text
From: [email protected] <[email protected]>
On Behalf Of N7SHM via groups.io
Sent: Wednesday, November 20, 2024 10:25 AM
To: [email protected]
Subject: Re: [KM4ACK-Pi] Autostart JS8Call attached to QDX/QRP radio
?
I'm really out of my league here, but feel your pain trying to understand sound devices under Linux with my own QDX, QMX, and X6100 radios and vanilla Debian.
It's probably, first of all, an environment thing.? Cron jobs run under their own limited environment that comes and goes with the job.? Apparently the display environment is available to the job or else you wouldn't even have the JS8/WSJT-X
GUI show up.? I'm guessing that you're logged in as a user with a graphical environment when the cron job launches, otherwise there would be no display environment, either.
Again merely guessing, the ALSA devices are:? a) unavailable to the user under which the job runs;? b) considered busy and not made available to the temporary environment set during the job;? or c) available under the job environment, but
the "connection" to them ends when the job environment disappears and JS8Call is left with some null reference.? Regarding (a), believe it or not, root is blocked from some system services - I presume for the sake of security - so could very well NOT have
access to audio services when executing a job.
These threads might be helpful:?
The solution may basically be getting your login environment shared with the job so the devices are seen persistently.? The threads above have some troubleshooting suggestions that show whether the ALSA devices are even available when the
job runs.
Good luck!? Let us know when you figure it out.
|
Re: Autostart JS8Call attached to QDX/QRP radio
I'm really out of my league here, but feel your pain trying to understand sound devices under Linux with my own QDX, QMX, and X6100 radios and vanilla Debian.
?
It's probably, first of all, an environment thing.? Cron jobs run under their own limited environment that comes and goes with the job.? Apparently the display environment is available to the job or else you wouldn't even have the JS8/WSJT-X GUI show up.? I'm guessing that you're logged in as a user with a graphical environment when the cron job launches, otherwise there would be no display environment, either.
?
Again merely guessing, the ALSA devices are:? a) unavailable to the user under which the job runs;? b) considered busy and not made available to the temporary environment set during the job;? or c) available under the job environment, but the "connection" to them ends when the job environment disappears and JS8Call is left with some null reference.? Regarding (a), believe it or not, root is blocked from some system services - I presume for the sake of security - so could very well NOT have access to audio services when executing a job.
?
These threads might be helpful:?
?
?
The solution may basically be getting your login environment shared with the job so the devices are seen persistently.? The threads above have some troubleshooting suggestions that show whether the ALSA devices are even available when the job runs.
?
Good luck!? Let us know when you figure it out.
?
73,
?
?? Dan
?
?
|
Re: New Mint on Wo-We 73 Linux build - Packet modem failed to start
Marty,
I had a real problem getting into the Bios on my Wo-We.? I can confirm it is the F2 key but it didn't work until I unplugged my radio USB connection from the Wo-We.? I should note that I was using a mouse and keyboard that uses a USB Dongle and I was running the monitor on USBC.? I never could get the HDMI ports to work.? I suspect a driver issue.
|
Re: Winlink - Piardopc error
That video is dated. Ardopc has been forked. For the latest development, see this forum -
?
--
73, de KM4ACK
|
|
|
Re: Wo-We PC running Nomachine on it and my Windows PC - Resolution issues
Thanks for the report Dave. Good to know that still works on Mint 22. Since I run mainly laptops theses days, I haven't had need to test that script.
?
--
73, de KM4ACK
|
|
|
I am following the directions in this video (yes.. I did go through the part 1 video)...
?
?
So I did type this command in accordance with the part 2 video:??
bryan@hampi:~/ardop $ ./piardopc 8515 plughw:2,0 plughw:2,0
?
Response I get is:
./piardopc: error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory
?
Any suggestions on how I should resolve this issue?? Any assistance is appreciated.
?
Thanks.
?
Bryan
KI5HAV
|
Re: Wo-We PC running Nomachine on it and my Windows PC - Resolution issues
I just discovered this video that Jason did a year ago: ?
?
Headless VNC Linux Mint/Ubuntu
?
At the top of the Github page click Repositories and then Pi-Scripts and then down to the Monitor-Check file.? Follow the video for installation instructions.? I am running Mint 22.
?
Thanks
Dave
?
It works on a Mint PC just fine.? Thanks for the work.? You do have to go to the Pi-Scripts to find it.
|
Autostart JS8Call attached to QDX/QRP radio
I've been trying to autostart (CRONTAB) JS8Call on a Pi4B running either Bookworm or Bullseye attached to a QDX/QRP radio.? I can start JS8Call fine from the command line or via the menu but if I attempt to start it from Crontab it no longer sees the audio devices.
crontab entry is:
#start js8call
@reboot sleep 40 && export DISPLAY=:0 && /usr/bin/js8call >> /home/pi/js8_start.log 2>&1
(js8_start.log to aid in troubleshooting)
?
Starting js8call (or wsjtx for that matter) from command line or menu? shows alsa_input.usb-QRP_Labs_QDX_Transceiver-02.analog-stereo for input and the corresponding alsa/QRP Labs output for output.
Running via CRONTAB statement above will launch JS8Call (or wsjtx) but Audio input and output listings are empty and neither of the alsa xxxx QRP_Labs devices exist.
?
Any thoughts?
Thanks
Jerry
|
Wo-We PC running Nomachine on it and my Windows PC - Resolution issues
When I access the Wo-We from my Windows 10 PC with the Roadom monitor attached to the Wo-We via a USBC cable if comes up OK.? Attaching the HDMI cable from the Wo-We to the monitor I get a little video during the boot process and then Black Screen.? I think this may be a HDMI driver issue on Mint/Wo-We?
?
Back the the USBC connection issue.? Nomachine VNC works great and I get a display that is running 1920x1024 and the Nomachine app on my Windows PC looks great.? Disconnect the monitor from the Wo-We to run headless and the Windows PC resolution is so large I can't see the bottom of the screen and Conky and a few Icons is all that displays.? Does anyone know how to get Nomachine VNC to stay at 1920x1024 when no monitor is hooked to the Wo-We PC?
?
Thanks
Dave
?
|
km4ack
Danny NF4J
Brian Dale
Ralph Shepard