New "Bullseye" OS for the Nexus DR-X System Available

[Steve Magnuson]

See the wiki for instructions: https://github.com/NexusDR-X/nexus-bootstrap/wiki

I lost count of the number of changes I had to make to the Nexus applications due to the large number of changes in the underlying operating system, so some things might not work correctly. For those who want to try it, visit the link above for instructions. Please post your questions/problems here.

As I mentioned in the last meeting, there is no longer a special Nexus image. It was just too time consuming to maintain.

Steve
AG7GN

[Dave McMakin]

Steve, so, your saying that some things me not work.. Should I just wait for the final project before I do this? Knowing how much problem I cause you when it doesn’t work right????

I tried to add the sstv that budd was talking about, did not work., had an error appear… It might be worth me waiting, at least for now…

Dave

W7WDM

 

Sent from Mail for Windows

--

You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.

To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/110735DE-15CB-4FE8-B3A1-99D458AF7679%40gmail.com.

 

[Steve Magnuson]

Dave,

There are applications (LinBPQ, piardop, etc.) that I know don’t work with the 64 bit version of Bullseye and there are other applications that seem to work but generate error messages when in operation (Direwolf, for example).

The 32 bit version of Bullseye, which I and the Raspberry Pi team recommends, seems to work fine in the rather limited testing I’ve done (Fldigi, Flmsg, Direwolf, wsjtx, js8call all work). The Wiki provides instructions for installing the 32 bit version. Anytime the underlying OS changes, there are bound to be problems with certain apps. I can’t uncover these problems on my own. I encourage you and others to try the 32 bit version of Bullseye because it’s the only way we’ll uncover and fix any problems.

QSSTV requires some configuration and the setup is unique to each radio model. I know that Budd and Peter both have it working on the previous image (“Buster”). I tested it briefly months ago and it worked fine. As I recall, it was tricky to get the settings right.

See this thread for how I set up mine back in March. Peter followed my lead and said his worked, too: https://groups.google.com/g/nwwdigi/c/Nn-1QvpYcrI/m/dJbZZ2baAwAJ

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/61cfc82f.1c69fb81.6d606.c6f0%40mx.google.com.

[Dave McMakin]

Sounds good I'll give it try.  Happy New Year.

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/9B421523-46F0-4E5A-A43C-826ADBD08D53%40gmail.com.

[Dave McMakin]

Steve,, what happen if it does NOT reboot after the 7 seconds and go to the auto config of part 2 bootstrap??? It is still waiting… power is on but will not show up on the display/

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/9B421523-46F0-4E5A-A43C-826ADBD08D53%40gmail.com.

 

[Steve Magnuson]

...and right out of the gate, Dave finds a bug.  This bug prevented 3B/3B+ Pis from booting correctly after running the first bootstrap script. It's fixed now, so if you're up for it Dave (and others), please try again.  Burn a fresh RaspiOS Desktop image to your microSD card - in other words, start at the beginning of the procedure.

Steve

AG7GN

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/61d0b261.1c69fb81.7cddf.ace4%40mx.google.com.

[Dave McMakin]

I’ll give it a go again in the morning during the morning BS net… see how it goes.. fingers crossed…

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/375c993c-260c-1488-0705-00844334578b%40gmail.com.

 

[Dave McMakin]

Ok steve here we go again… made it up the the terminal entry… double and triple checked the spelling etc… comes op with an error when I hit return…    

Syntax error near unexpected token ‘newline’

‘<!DOCTYPE html>’

 

Now what???

FYI I’m on fsq with the boys…

 

 

Sent from Mail for Windows

 

From: Steve Magnuson
Sent: Saturday, January 1, 2022 6:36 PM
To: nww...@googlegroups.com

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/375c993c-260c-1488-0705-00844334578b%40gmail.com.

 

[Steve Magnuson]

When you type the command, make sure you are using “.io” in the URL, not “.com”:

bash <(curl -sL "https://nexusdr-x.github.io/nexus-bootstrap/bootstrap0”)

If you use “.com”, it’ll download the HTML web page instead of the script.

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/61d1de21.1c69fb81.9046d.f7cf%40mx.google.com.

[Steve Magnuson]

Also, with this error you’re seeing now, you do not need to re-burn the RaspiOS to your card. Simply run the command below again.

Steve

[Dave McMakin]

Thanks steve.. yes it was .io     ran it 3 times same result….  I am right now at the terminal entry point again and will try again….  Will let you know…

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/C53DFAC5-AFAF-4C45-9260-A8B10ED58FAB%40gmail.com.

 

[Dave McMakin]

Well I already burned another one and just hit return and so far it is working… I’ll let you know one way or the other … still downloading lots of characters to the screen right now…

 

 

Sent from Mail for Windows

 

From: Steve Magnuson
Sent: Sunday, January 2, 2022 9:54 AM

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/C53DFAC5-AFAF-4C45-9260-A8B10ED58FAB%40gmail.com.

 

[Dave McMakin]

Ok steve… it looks done… just finished the part that you say DO NOT TOUC KEYBOARD….  After a few min you will see…   well,, it went to the main screen of the pi… you know, the bexus dr-x display… and I am assuming it is done… it did not go the  bootstrap complete display… I will wait here for a bit then try testing….

 

Sent from Mail for Windows

 

From: Steve Magnuson
Sent: Sunday, January 2, 2022 9:54 AM

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/C53DFAC5-AFAF-4C45-9260-A8B10ED58FAB%40gmail.com.

 

[Steve Magnuson]

I don't know way you didn’t see the “Complete” window. Did you see various Fldigi/Flmsg, etc. screens open and close before the Terminal window closed? If you see the Fldigi and related apps in the Hamradio menu, then it completed despite the absence of the “Completed” window.

I used the procedure on a 4B and a 3B this morning and it works as documented.

If you want to arrange the menu layout, the Wiki has step=by=step instructions at https://github.com/NexusDR-X/nexus-bootstrap/wiki/1.-Installation#part-3-nexus-dr-x-setup step 5.

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/61d1f1c0.1c69fb81.3673d.07e9%40mx.google.com.

[Dave McMakin]

All looks good so far Steve… I will have to re-enter all the fldigi info and I will copy what settings I have on the go-kit to the new desktop pi.  So I should have it all up and running by tonight.. have a few things to take care of so I;’ll make the changes later today…

Thanks again for all the help.. 

Dave

W7wdm

 

Sent from Mail for Windows

 

From: Steve Magnuson
Sent: Sunday, January 2, 2022 9:54 AM

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/C53DFAC5-AFAF-4C45-9260-A8B10ED58FAB%40gmail.com.

 

[Steve Magnuson]

As is mentioned in the Wiki, you can back up your home folder on your other Pi and restore it on your new Pi so all your Fldigi, etc. settings will work on your new Pi.

See https://github.com/NexusDR-X/nexus-bootstrap/wiki/0.-Preparation#a-special-note-for-users-of-previous-nexus-images

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/61d1fc4e.1c69fb81.3985c.5592%40mx.google.com.

[Dave McMakin]

Well, e-mail is not updating quickly… Yes, I was watching fldigi screen fly by before it was finished… That’s why I assumed it was all good and done… I have already moved the features around on the display screen… I tested the fsq, but alas I still have to reprogram the settings… I’ll just copy what settings I have for the go-kit. It will take a while but hey, it looks like it is working… I’ll get with you later to get the piano switches working again…

I’ll get everything up and running before I try the update again for the go-kit and the Pi4.

Again  Thank you for all you have done,

Dave

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/BDE592D7-B973-41B5-BC46-E2BAFDEA6D1D%40gmail.com.

 

[Dave McMakin]

HEY mail was late again…. I DID THAT…. The backup copy anyway.. I guess I could do the updater and all good… I’ll try that this afternoon…

Thanks for the millionth time

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/CF54D22E-F6FB-44D0-A525-DBABE3626678%40gmail.com.

 

[Dave McMakin]

Steve. Thought you would like to know.   IT WORKS!!!! Ended copying settings from go-kit only to have no receive on waterfall… found your notes on the alsamixer and tried… again copied the same settings from go-kit and it worked… had no right side audio…  Oh well… it is working… now just have to so it again with the go-kit on the pi4….   I may wait a little for that one…

Thanks again.

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/CF54D22E-F6FB-44D0-A525-DBABE3626678%40gmail.com.

 

[Steve Magnuson]

Glad to hear it Dave. Now there are 2 of us using Nexus DR-X with Bullseye ;)

Steve

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/61d22b34.1c69fb81.45daf.38c7%40mx.google.com.

[Steve Stroh]

Steve:

I'm #3.

Used Raspberry Pi Imager for Mac. Usual precautions of shutdown,
removed power before changing uSD card, etc. were all observed.

(The following is for amusement - After more than 90 minutes, I'm not
YET to the point of AG7GN's instructions).

First hurdle... Lost the Bullseye 16 GB uSD card on my desk. It...
just... vanished (into the ephemera). I looked for 30 minutes then
gave up and dug into the 3-pack of 16 GB uSD cards and grabbed a
second one.

"Flashed" the second uSD card - worked fine.

Second hurdle... Inserted it into the Nexus and it just... wouldn't... boot.

Brought it back to my Mac and re-flashed the second uSD card, checked
out fine. Took it over to the Nexus and this time it booted.

Third hurdle... Ran the "Update software" routine and it timed out
looking for updated software. I clicked Back, and retried, and this
time it proceeded to "Installing Updates".

Fourth hurdle... I rebooted and something borked (probably one of my
tweaks per my preferences) and when it rebooted, the OS is there (VNC
will connect), but on the display, there's only a tiny blinking _ in
the upper left corner. Sigh...

Broke out the third 16 GB uSD card and back to Raspberry Pi Imager for
another try. Did almost no changes to the desktop and it booted up
successfully and I was able to launch the script and it completed (to
displaying Nexus DR-X desktop - see Issues).

Notes:
* One change I made was to enable VNC as soon as possible so I could
work from my comfortable office, instead of the chilly shop / shack.
Of course, that broke towards the end of the configuration cycle when
I noted the VNC key was changed. I was able to quickly re-establish
VNC.
* I skipped the menu reconfiguration that Steve suggested.
* As mentioned, as much as possible, I managed the install from
another computer using VNC.
* Once the script completed, I did a restore from my previous setup.
No errors reported.

Document suggestion:
* State that in Part 3, Step 3, there must be a space between "-sL"
and "https//..." (not obvious given that these are two separate lines
in the document).

Issues:
* I did not see the "Nexus DR-X bootstrap complete" window. When the
configuration was complete, I was looking at the desktop.
* One minor casualty is that the Hamradio > Start TX Audio Monitor
does not work. Previously I would hear tx audio from my (HDMI)
monitor. Yes, audio is enabled in the upper right task bar.
* Budd's Smart Monitor isn't happy - it's continually scrolling an
error message:
/home/pi/WB7FHC/smart_heard.sh: line 435: [: ==: unary operator expected
Eventually it crashed. I've restarted it a couple of times.

Neither the TX audio or Budd's Smart Monitor are showstoppers (but
nice if they could be fixed).

I tested my system briefly with pings and one signal report to Budd. I
can transmit and be heard, and receive.

My system is online on 145.580 MHz if anyone wants to test against it.

Thanks Steve! Your documentation is fantastic!

Steve N8GNJ

On Sun, Jan 2, 2022 at 3:54 PM Steve Magnuson <steve.m...@gmail.com> wrote:
>
> Glad to hear it Dave. Now there are 2 of us using Nexus DR-X with Bullseye ;)
>
> Steve

--
Steve Stroh N8GNJ
Editor
Zero Retries Newsletter - https://zeroretries.substack.com
Twitter - @zeroretries / https://twitter.com/zeroretries

[Steve Magnuson]

Thanks for your detailed report, Steve. This is very helpful. Additional comments below.

Steve
AG7GN

Sent from mobile device.

> On Jan 5, 2022, at 6:00 PM, Steve Stroh <steve...@gmail.com> wrote:
>
> Steve:

>
> I'm #3.
>
> Used Raspberry Pi Imager for Mac. Usual precautions of shutdown,
> removed power before changing uSD card, etc. were all observed.
>
> (The following is for amusement - After more than 90 minutes, I'm not
> YET to the point of AG7GN's instructions).
>
> First hurdle... Lost the Bullseye 16 GB uSD card on my desk. It...
> just... vanished (into the ephemera). I looked for 30 minutes then
> gave up and dug into the 3-pack of 16 GB uSD cards and grabbed a
> second one.
>
> "Flashed" the second uSD card - worked fine.
>
> Second hurdle... Inserted it into the Nexus and it just... wouldn't... boot.
>
> Brought it back to my Mac and re-flashed the second uSD card, checked
> out fine. Took it over to the Nexus and this time it booted.
>
> Third hurdle... Ran the "Update software" routine and it timed out
> looking for updated software. I clicked Back, and retried, and this
> time it proceeded to "Installing Updates".

Likely a problem reaching one of the many RasiOS repository mirror servers. While I appreciate that “Wizard” app (‘PiWiz’), it doesn’t give you any feedback as to what’s going on.

>
> Fourth hurdle... I rebooted and something borked (probably one of my
> tweaks per my preferences) and when it rebooted, the OS is there (VNC
> will connect), but on the display, there's only a tiny blinking _ in
> the upper left corner. Sigh...
>
> Broke out the third 16 GB uSD card and back to Raspberry Pi Imager for
> another try. Did almost no changes to the desktop and it booted up
> successfully and I was able to launch the script and it completed (to
> displaying Nexus DR-X desktop - see Issues).

That’s quite a list! What brand of uSD card? I’ve tried many different brands and I now only use SanDisk or Samsung.

>
> Notes:
> * One change I made was to enable VNC as soon as possible so I could
> work from my comfortable office, instead of the chilly shop / shack.
> Of course, that broke towards the end of the configuration cycle when
> I noted the VNC key was changed. I was able to quickly re-establish
> VNC.

Yes, that’s by design to ensure a unique VNC (and SSH) key.

> * I skipped the menu reconfiguration that Steve suggested.
> * As mentioned, as much as possible, I managed the install from
> another computer using VNC.
> * Once the script completed, I did a restore from my previous setup.
> No errors reported.
>
> Document suggestion:
> * State that in Part 3, Step 3, there must be a space between "-sL"
> and "https//..." (not obvious given that these are two separate lines
> in the document).

Noted. I’ll fix that.

>
> Issues:
> * I did not see the "Nexus DR-X bootstrap complete" window. When the
> configuration was complete, I was looking at the desktop.

I fixed that this afternoon. Dave reported the same. The problem is that it takes just a few seconds longer to start Fldigi on the 3B than it does on the 4B, so about 50% of the time the Flamp startup (which must have Fldigi already running to work) would fail on the 3B. I increased the timer and it works reliably now on 3B Pis. It’s not a showstopper if you don’t see the “complete” window - it’s simply setting some default values in the Fldigi (and suite) configuration files. And, if you restore your home folder from backup, those script changes are overwritten in any case.

> * One minor casualty is that the Hamradio > Start TX Audio Monitor
> does not work. Previously I would hear tx audio from my (HDMI)

I made a change earlier today to those scripts due to significant changes in Bullseye of the audio/video driver. Does the RX audio monitor work OK? I’ll investigate the TX monitor tomorrow. I greatly simplified the PulseAudio configuration over the weekend so that it would work on both the 4B and the 3B Pis (which have very different HDMI audio/video systems).

> monitor. Yes, audio is enabled in the upper right task bar.
> * Budd's Smart Monitor isn't happy - it's continually scrolling an
> error message:
> /home/pi/WB7FHC/smart_heard.sh: line 435: [: ==: unary operator expected
> Eventually it crashed. I've restarted it a couple of times.

I’ll let Budd look into that one. Could be a change in Bullseye is causing his script to fail. I had not tested his script under Bullseye.

>
> Neither the TX audio or Budd's Smart Monitor are showstoppers (but
> nice if they could be fixed).
>
> I tested my system briefly with pings and one signal report to Budd. I
> can transmit and be heard, and receive.
>
> My system is online on 145.580 MHz if anyone wants to test against it.
>
> Thanks Steve! Your documentation is fantastic!
>

You’re welcome, and welcome to Bullseye!

> Steve N8GNJ
>
>
>> On Sun, Jan 2, 2022 at 3:54 PM Steve Magnuson <steve.m...@gmail.com> wrote:
>>
>> Glad to hear it Dave. Now there are 2 of us using Nexus DR-X with Bullseye ;)
>>
>> Steve
>
>
> --
> Steve Stroh N8GNJ
> Editor
> Zero Retries Newsletter - https://zeroretries.substack.com
> Twitter - @zeroretries / https://twitter.com/zeroretries
>

> --
> You received this message because you are subscribed to the Google Groups "Northwest Washington Digital Amateur Radio" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to nwwdigi+u...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/CAGh1Bg5%3DnAVfewciRdWY4g5f7PHAs2ac_qew0wDV-5f6AH%3DBUg%40mail.gmail.com.

[Steve Stroh]

Steve:

I saw a good deal for 3 packs of Sandisk 16 GB uSD cards on Amazon. It was just the uSD cards only - no SD adapters.

When I buy SD cards I only buy units sold and shipped by Amazon. Otherwise it’s too easy to end up with counterfeits. 

PS - backup and restore worked GREAT!

Thanks,

Steve

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/1292AF21-C467-4BCC-A8FF-1DB8EA0CACD6%40gmail.com.

[Steve Magnuson]

Steve,

RE: No TX audio monitor

I suspect that your restore from backup overwrote the changes in a PulseAudio file that’s in your home folder. Open a Terminal and run:

nexus-updater.sh -f nexus-audio

When that completes, make sure “HDMI” audio is checked as your output device (Right-click on speaker icon in task bar, select Output devices). Then run this command:

speaker-test -c 2 -t wav

You should hear “front left”, “front right”, etc. from your HDMI monitor speakers. Press CTRL-C to quit.

Then test the RX and TX monitors.

Steve

AG7GN

Sent from mobile device.

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/CAGh1Bg4Tm56tkn98fVyB-XQqRNxrhCuF8_pRO7fd0cHE%2B_tteA%40mail.gmail.com.

[Steve Stroh]

Steve:

Did a trial by fire on the Wednesday evening net on 145.740 repeater that flushed out a few new issues.

1. Ran the nexus-update.sh script. Probably not a good idea to run that with fldigi open. 

The volume control icon disappeared from the task bar. Figured out how to get that back. 

Changed Audio output to HDMI and that seemed to break fldigi / fsq. Still no audio from the monitor (worked on previous image) and setting audio output back to Fe-Pi Audio, and a cold shutdown / power cycle seems to have fldigi / fsq working again. 

Might be a one off, but I composed some text and pushed enter and someone else started transmitting (displaying on the main window) and fldigi locked up - waterfall halted, no text displayed in main or monitor. Had to restart the system. 

One minor thing that didn’t transfer from my backup / restore was the radio name. I had called it TM-V71A but now it’s back to (left radio) and (right radio). 

Thanks,

Steve N8GNJ

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/F9BAECDA-A83F-4931-B271-E84E6FE6EA81%40gmail.com.

[Steve Stroh]

One other issue - Dave reported I had an “echo” and I’m guessing that was because I turned on Start TX monitor, but per the volume control Audio Output set to Fe-Pi Audio, I bet it was sending “double audio” into the radio 

[Steve Magnuson]

Thanks again for your detailed report, Steve. I can see that I need more documentation.

Updating PulseAudio while an app (Fldigi, for example) is using it will cause unstable behavior. I should’ve explicitly stated to close all other apps when running the Updater.

The Radio Names and Desktop Text data is stored in a new location, so you’ll need to run the “Name Your Radios” and “Edit Desktop Text” apps again. I’ll add that to the documentation too.

I have RX and TX audio monitoring working on a 3B+ and a 4B running Bullseye.

Steve
AG7GN

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/CAGh1Bg7nMvh8T%3DE3pGt_P6f3EE6ED%3DZnXm%2B-99Z2X9_VFPYa9w%40mail.gmail.com.

[Steve Magnuson]

Steve,

I think I see why you had some of the problems you did. I omitted an argument in one of the commands I gave you earlier - one that installs the latest version of the Updater. Here’s the revised procedure to fix TX/RX audio monitor.

1) Open a Terminal and CLOSE ALL OTHER APPS!

2) Run this command in the Terminal:

nexus-updater.sh -s -f nexus-audio

3) If that command returns "A new version of this script has been installed. Please run it again.”, then run it again. Otherwise, go to the next step.

4) You should see this output:

===== nexus-update install/update requested =====
HEAD is now at 2d3c25d Improve GUI vs. terminal checking
Already up to date.
===== nexus-update up to date =====
Checking dependencies...
Done.
===== nexus-audio install/update requested =====
HEAD is now at a8f826c Update monitor-audio-tx.desktop
Already up to date.
===== nexus-audio up to date =====
-----> Adding Fe-Pi dtoverlay if needed...
-----> Done.
______
-----> Copying ALSA and pulseaudio configuration files...
-----> Done.
______
-----> Copying audio monitor desktop files...
-----> Done.
______
===== nexus-audio installed/updated =====
Restarting pulseaudio...
Done.

5) When that completes, make sure “HDMI” audio is checked as your output device (Right-click on speaker icon in task bar, select Output devices). Or, if using speakers connected to the TRS jack on the side of the Pi, select “AV Jack”.

6) Run this command in the Terminal:

speaker-test -c 2 -t wav

You should hear “front left”, “front right”, ... from your speakers. Press CTRL-C to quit.

7) Turn on your radio(s) and start Fldigi, then test the RX and TX monitors (Raspberry > Ham Radio > Start [RX|TX] Monitor.) If you are using the 9600 audio tap in your radio, you are almost certainly going to hear an open squelch sound when the RX Monitor is enabled. You can run both the RX and the TX monitor at the same time.

8) Shut off the monitors using Raspberry > Ham radio > Stop Audio Monitors.

Steve
AG7GN

[Steve Stroh]

Steve:

Success!

The newest instructions restored the RX Audio Monitor (static as you expected as I do use the 6-pin MiniDIN input on the TM-V71A) and TX Audio Monitor (outgoing fldigi audio).

The test script also worked fine to output the test audio. 

System is working normally now. 

I renamed the Left Radio back to TM-V71A.

The desktop text was already correct (N8GNJ with the box checked).

Now if I could get Budd’s revised Smart Monitor…

Thanks,

Steve N8GNJ

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/A200222E-1DA9-41F3-8195-907ACFAAAECF%40gmail.com.

[Steve Magnuson]

Wonderful. I just pushed updates to the Wiki based on your feedback and experience.

https://github.com/NexusDR-X/nexus-bootstrap/wiki

Steve
AG7GN

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/CAGh1Bg76KX9nCc5j9vqddDzeWfJDDq-z9qh%3Db4qMsHv%2BG5YMBQ%40mail.gmail.com.

[Gayland Gump]

Steve,

I had problems with Budd's App lately too.  Make sure you download his most recent iteration as that is what I had to do to correct my issues.

Gayland

KG7GCF

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/2DDE83E8-A334-4015-B419-ACB09FF3E8DC%40gmail.com.

[Steve Magnuson]

Where can I download that script?

Steve
AG7GN

> To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/CAA_2G1JKzWwrvT58iX915v7Yws_37dj%3DxVtAuXU_zP2-xFLaxg%40mail.gmail.com.

[Gayland Gump]

Steve (AG7GN),

Want to let you know I followed the wiki instructions for bullseye.  I'd only a couple of issues that turned up for me and they very well may have been because I did the installation on a pi4 without the fe-pi and nexus hats.  During the download I did get a warning that the fe-pi was not detected.  When I ran fldigi initially neither the receive nor the transmit were working.  I selected the HDMI output and tones were being generated but were not being transmitted.  I launched alsamixer and determined that lineout was not enabled and the mic in rather than line in was selected.  I corrected those issues and I appear to be good to go.

I have a fair number of other customization's I've made.  One of which was a couple of Yadd scripts that I've set up to manage a variety of 710.sh scripts.  Yadd is working so it appears to be installed but the location of the button icons must be different than they were on Buster as they are not being found by my script.  I was wondering if you have any idea where they might be installed in bullseye.  If not I'll dive in and see if I can find them.

Attached is a screenshot of the running system.

Compliments on another great job serving all of us Nexus users. 

Thank you so much.

Gayland

KG7GCF

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/2DDE83E8-A334-4015-B419-ACB09FF3E8DC%40gmail.com.

[Gayland Gump]

Budd emailed it to me. 

# Smart List for fsq
# Budd Churchward WB7FHC
# email: wb7...@arrl.net
V_DATE="11/01/21"

The file should be attached below.

Gayland

KG7GCF

To view this discussion on the web visit https://groups.google.com/d/msgid/nwwdigi/74BD6156-7702-4CDB-8DF2-6DC7DFDA40F9%40gmail.com.