开云体育

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,

Glad you got the sound card figured out. Changing your call is easy. Just click on Conky-Prefs from the main pi menu -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar (

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

I always recommend starting from scratch when a new major version of Pi OS is released. This will avoid issues that may pop up with the OS itself if you try to upgrade. -- 73, de KM4ACK YouTube (

edit: The stability issues mentioned below were my own doings. I had used a power supply that was inadequate for the Pi. Apparently Bullseye is much more sensitive to the "low voltage" warnings and

Hello Jason. Both the Pi display and the laptop are the same, 1920x1080 60hz 16:9. The issue is still there, any other ideas I can try? I am running Stretch, I had some problems with Buster a while

Hello everyone, I am having three issues which I believe are related. I am using BAP version 3.1 (Latest). The beta version of Mobilinkd is able to connect to my TNC, but it looks like I am not

Direwolf compiles and runs fine: Dire Wolf DEVELOPMENT version 1.7 B (Nov 11 2021) Includes optional support for:? gpsd hamlib cm108-ptt NOTE - i have used gpsd and hamlib dev packages from the

Are you recommending that we start from scratch with bullseye? I got error(s) during the upgrade.? I haven't tried BAP (I see others are having problems with BAP). It looks like BULLSEYE is running,

gpsd-3.23.2 is compiling and working fine There is a issue with some of the digi? packages - it installs hamlib via the repository. And at the same time hamlib is installed from source code. There

The following packages did not install on bullseye Hamlib 4.3?Cqrlog 2.52?Js8call 2.0?wsjtx 2.5.2 Flrig and Fldigi installed an ran ok Pat installed an daemon runs, did not test pat as yet Ken

Hamlib (rigctl) won't install on Bullseye SOLVED - https://github.com/km4ack/pi-build/issues/338 -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack

I have tried both a signalink and a easy digi for my sound card interface.? In both cases after I perform an "arecord -l" command I verified that? "card 2: Device [USB Audio Device], device 0: USB

Right now I am going through each package available in BAP to see which ones won't compile/install correctly. I will post issues here as they are found. Currently I know that Chirp isn't working (

I have 9 Pi,s 12 mem chips and time. How can i help you. Warren W. Stickney

Chirp will not build on Bullseye. See https://github.com/km4ack/pi-build/issues/337 -- 73, de KM4ACK YouTube ( https://youtube.com/km4ack ) | Tip Jar ( https://www.paypal.me/km4ack ) Twitter (

Again, didn't work. [image: Screen Shot 2021-11-11 at 08.29.09 .png] Left the terminal window open and opened Chromium and navigated to Pat ( 127.0.0.1:5000) and I still get the same error that it

I, too, am hip deep in 'gators with motioneye/motionEyeOS, Bullseye, and Python2 -> Python3 conversions. I've had other issues with gridsquare and time and GPS, and didn't want to start learning yet

Thanks Kevin. It may be a while before I can get to this. The new Bullseye release has a whole new set of challenges that I will be focused on for now. Having the issue ticket created will be the

Build a Pi is different from other Pi images as it builds/installs everything on the fly. This is a great asset but also has potential to create headaches each time a new Pi OS is released every two