Welcome! This group is primarily for discussing my scripts and how to configure them for different setups. However, all Raspberry Pi conversation is encouraged. Please be respectful at ALL TIMES. Let's try to help one another out without demeaning anyone. I will jump in and answer as many questions as I can but may not be able to respond to everyone. It is near impossible for me to help setup a radio that I don't own and have no experience with. By building community, others with similar setups may be able to offer a helping hand. This is the purpose of community. A few helpful links YouTube Channel ( https://youtube.com/km4ack ) KM4ACK FAQ ( https://tiny.cc/km4ack-faq ) KM4ACK GitHub ( https://github.com/km4ack ) How To Guides :: Radio Setups ( https://groups.io/g/KM4ACK-Pi/message/5794 ) -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack ) Twitter ( https://twitter.com/km4ack ) | Store ( https://km4ack.square.site/ ) Patreon ( https://patreon.com/km4ack )

Conky Custom Settings - https://groups.io/g/KM4ACK-Pi/message/4678 Icom 7100 Setup - https://groups.io/g/KM4ACK-Pi/topic/85692067 Icom 7300 Setup - https://groups.io/g/KM4ACK-Pi/message/3838 Lab599 TX500 - https://groups.io/g/KM4ACK-Pi/message/5518 -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack ) Twitter ( https://twitter.com/km4ack ) | Store ( https://km4ack.square.site/ ) Patreon ( https://patreon.com/km4ack )

This has occurred on a Raspberry Pi 4B It looks like Bullseye has added another quirk when trying to run headless. You will get a message like "Cannot currently display the desktop". What is happening is the Pi has booted with Composite video enabled which will not work with VNC. There is no way to turn it off with the current downloaded version of Bullseye raspi-config so do the following: 1. SSH into your Pi 2. Run sudo raspi-config 3. Update raspi-config. This adds the ability to turn off the composite video and also 4k-HDMI under option 4. Select Display options and you can change the VNC resolution now AND Composite options. 5, Set composite options to default which disables composite video and 4k HDMI All should work now. The key is to update raspi-config as soon as you get control of your pi under SSH.

If you upgrade to Bullseye you will likely notice that Conky is not comfortable on the right hand side of your VNC (and attached) monitor. For some reason the screen size is changing randomly at boot time to a smaller screen even though the wallpaper keeps the full resolution. You can also observe that the long dropdown menus don't expand like they should. The menu thinks the screen is shorter than it is. The fix I found was to do the following: 1. Once booted, place the mouse over a blank area on the display and right click 2. Select Desktop 3. Set layout to "Centre image on screen" 4. Click OK You will still be running the new video subsystem which has it's own set of quirks right now. One is a slow VNC connection and behavior from time to time, although once fully BAP built I have not noticed the sluggish VNC response. It can be really bad on the initial setup from a clean install. Jason has another option that removes the new video subsystem by editing the /boot/config.txt file. Both seem to work. His video for that can be found at: https://youtu.be/-7rlLJmNmfA 73, Dave - KD7UM

I have put together a list of FAQ about various scripts that helps resolve common problems. There is also a few setup guides submitted by viewers. You can find the list here. -- 73, de KM4ACK YouTube | Tip Jar Twitter | Store Patreon

There's an issue that occurs after updating Bullseye that causes piardopc to lockup in TX mode during the first transmit cycle. This isn't a Build a Pi issue and the issue has been reported to the piardopc developer here ( https://groups.io/g/bpq32/topic/piardopc_locks_up/90161705?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,90161705,previd%3D1648795599466057711,nextid%3D1647591672695225472&previd=1648795599466057711&nextid=1647591672695225472 ). While not the best solution, for now I would avoid updating your Pi if you rely on ARDOP. Also, don't use the BAP update tool as it will automatically update the OS as well. As soon as I find out more or a solution is developed, I'll let you guys know. Personally, I have only tested with the 32 bit Pi OS but others have said it also impacts the 64 bit version. If you have already updated, revert to your backup image until this is sorted out. *Update 25APRIL2022* -------------------- Wanted to give you guys an update on the ARDOP issue that was causing rigs to lock up in transmit. John Wiseman (piardopc developer) has released a test version that eliminated the issue. However, Build a Pi won't install it yet as it is still in the testing phase. It should go without saying but backup your Pi before proceeding. This should work for all Build a Pi builds. If you would like to test it on your Pi, follow these steps to install: *cd ~/ardop* *rm piardopc* *wget https://www.cantab.net/users/john.wiseman/Downloads/Test/piardopc* *chmod +x piardopc* You will also need to remove the hold and update the kernel if you did that step previously. A few more commands will accomplish this: *sudo apt-mark unhold raspberrypi-kernal* *sudo apt update* *sudo apt upgrade* After testing, please post your results in the forum ( https://groups.io/g/bpq32/topic/piardopc_locks_up/90161705?p=,,,20,0,0,0::recentpostdate/sticky,,,20,2,0,90161705,previd%3D1649851861632164029,nextid%3D1648897807475058627&previd=1649851861632164029&nextid=1648897807475058627 ) (good or bad) so we can give John some feedback. -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack ) Twitter ( https://twitter.com/km4ack ) | Store ( https://km4ack.square.site/ ) Patreon ( https://patreon.com/km4ack )