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 )

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

#### EDIT #### PATCHING IS NO LONGER REQUIRED ##### However, until the next binary kernel release of 5.15.*, the syncing source and building of the kernel still apply. The latches linked to bellow have already been applied to the current tree in the GIT repository linked below. As far as I can tell this gets the kernel up to the latest patch level for the AX.25 code in the kernel. This is only necessary if you are using pat with the native Linux AX.25 (kissattach). 1. Back up your stuff: 2. Get the kernel source: sudo apt install git bc bison flex libssl-dev make git clone --depth=1 https://github.com/raspberrypi/linux 3. Apply the patches here found here: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=7d8a3a477b3e This is done by cutting and pasting the deltas from the original tree into a text file with a name of your choice. The deltas look like this: @@ -228,6 +228,7 @@ typedef struct ax25_dev { ax25_dama_info dama; #endif refcount_t refcount; + bool device_up; } ax25_dev; typedef struct ax25_cb { Say you named your text file ax25.h.patch then apply like: patch ax25.h ax25.h.patch You may want to make a copy of the original pre patched file in case something goes awry. There are four patches and the 2nd one needs a larger fuzz factor for it not to fail, so apply it with a fuzz of 3 like this: patch -F 3 af_ax25.c af_ax25.c.patch You will need to descend into the source tree directories to find them, but their locations are under the folders "a" and "b" on the patch authors original post. I put my source in /usr/src so that the tree becomes /usr/src/linux 4. Apply the default configuration. This tells the compiler to setup the kernel the way it was before (except it won't be in a deb package). Choose the one that is appropriate for your architecture, so you need to make sure you are running 32 or 64 bit system or it won't work. I am going to paste the relevant sections from this website: https://www.raspberrypi.com/documentation/computers/linux_kernel.html ( https://www.raspberrypi.com/documentation/computers/linux_kernel.html ) Apply the Default Configuration First, prepare the default configuration by running the following commands, depending on your Raspberry Pi model: For Raspberry Pi 1, Zero and Zero W, and Raspberry Pi Compute Module 1 default (32-bit only) build configuration cd linux KERNEL=kernel make bcmrpi_defconfig For Raspberry Pi 2, 3, 3+ and Zero 2 W, and Raspberry Pi Compute Modules 3 and 3+ default 32-bit build configuration cd linux KERNEL=kernel7 make bcm2709_defconfig For Raspberry Pi 4 and 400, and Raspberry Pi Compute Module 4 default 32-bit build configuration cd linux KERNEL=kernel7l make bcm2711_defconfig For Raspberry Pi 3, 3+, 4, 400 and Zero 2 W, and Raspberry Pi Compute Modules 3, 3+ and 4 default 64-bit build configuration cd linux KERNEL=kernel8 make bcm2711_defconfig 5. Rename your custom kernel (from the pi page): Customising the Kernel Version Using LOCALVERSION In addition to your kernel configuration changes, you may wish to adjust the LOCALVERSION to ensure your new kernel does not receive the same version string as the upstream kernel. This both clarifies you are running your own kernel in the output of uname and ensures existing modules in /lib/modules are not overwritten. To do so, change the following line in.config : CONFIG_LOCALVERSION="-v7l-MY_FIXED_AX25" You can also change that setting graphically as shown in the kernel configuration instructions ( https://www.raspberrypi.com/documentation/computers/linux_kernel.html#configuring-the-kernel ). It is located in "General setup" => "Local version - append to kernel release". 6. Compile and install (also from the RP page): Building the Kernel Build and install the kernel, modules, and Device Tree blobs; this step can take a *long* time depending on the Raspberry Pi model in use. For the 32-bit kernel: make -j4 zImage modules dtbs sudo make modules_install sudo cp arch/arm/boot/dts/*.dtb /boot/ sudo cp arch/arm/boot/dts/overlays/*.dtb* /boot/overlays/ sudo cp arch/arm/boot/dts/overlays/README /boot/overlays/ sudo cp arch/arm/boot/zImage /boot/$KERNEL.img For the 64-bit kernel: make -j4 Image.gz modules dtbs sudo make modules_install sudo cp arch/arm64/boot/dts/broadcom/*.dtb /boot/ sudo cp arch/arm64/boot/dts/overlays/*.dtb* /boot/overlays/ sudo cp arch/arm64/boot/dts/overlays/README /boot/overlays/ sudo cp arch/arm64/boot/Image.gz /boot/$KERNEL.img NOTE On a Raspberry Pi 2/3/4, the -j4 flag splits the work between all four cores, speeding up compilation significantly. If you now reboot, your Raspberry Pi should be running your freshly-compiled kernel! Maybe someone could make deb packages that install the patched and compiled binary modules, or possibly even include in the build-a-pi script. That would make it a lot easier. I think I have messed with it as much as I am going to. 73 de Chris KQ6UP

Hi all, I've reloaded Ham Clock, however, i can't get it to the far right of my screen. apparently, it thinks my screen is much smaller than it is. i have tried to adjust it without success. any help will be greatly appreciated. Brett -- 73 de K5BEZ

Hi when I try an update from the menu i get this error invalid desktop entry file /usr/local/share/applications/build-a-pi.desktop any ideas please Lee

I'm new to the group, but found a lot of great information here! I'm hoping someone can point me in the right direction on a configuration issue I'm having. I'm trying to run Winlink Express (Packet) under wine (64-bit WINEPREFIX which I understand may be an issue) on a Raspberry Pi 5 with an ICOM 7100 radio. Using much of the information found in this group, I think I'm close, but I can't get the radio to transmit. My latest configuration attempt is using flrig: - Winlink Express works with telnet so the basic installation is OK -> Winlink Express Packet setttings: KISS, NORMAL, TCP, 127.0.0.0 port 8001 - Winlink Express (Packet) is sending traffic to Direwolf - flrig can successfully change frequencies and other configurations on the ICOM 7100 - I can successfully transmit using other ham radio applications on the ICOM 7100 with the PI 5 - Note: separate from using flrig, I was able to configure Direwolf to receive APRS packets Issue: - I can hear the Winlink Express audio and can see traffic logged in DireWolf, but the IC 7100 doesn't transmit Additional Configuration Info: - I tried several direwolf.conf iterations, but current config is: -> CHANNEL 0; ADEVICE plughw:0,0; MYCALL KM6YKT; MODEM 1200; PTT RIG 2 localhost:4532 -> arecord -l shows card 0 device 0 is CODEC [USB Audio CODEC] -> rgctld -m 4 is running I've tried other methods (separate from using flrig) and configurations including: various direwolf.conf settings; kissattach; links; digirig; regedit for COM ports; baud rate settings, paging size, ax25 port configs, etc., but I'm missing something. I'm very new to Linux so any guidance is much appreciated. I think I may have missed something simple. Thanks, Greg

Trying to get conky to display my grid square. I am running 32bit bullseye 73linux the gps puck is a VK-162 G-Mouse USB I can see data when I run cat /dev/ttyACM0 but the puck doesn't list in GPS updater pulldown CGPS doesn't see it either anyone run into this or have an idea where to go from here? tnx Rick ..

I'm running an Evolve with Linux Mint and gone through all the install that Jason has on YouTube and all works well except VARA for Winlink. When I start the VARA modem I get the message "Listener varahf failed: vara initialization failed: couldn't connect to VARA command port: dial tcp 127.0.0.1:8300: connect: connection refused" I have done research and looked through my system put can't find a solution. Any help would be greatly appreciated. Thanks, Kevin KD9DXT

I am using packet (ax25) in build a pi for winlink on the Raspberry pi with a sound cart and a relay to let the ptt react on my HT (wouxun kg-uvd1). Direwolf is responsible for giving a signal over gpio pin 26 to activate de ptt of the HT. This is working very well and reliable. For the winlink vara-FM mode in build a pi, I want also to let it work on the same HT and a gpio pin of the raspberry pi. When I look in the menu of Vara-FM I can only chose for a comport and nothing like another external possibility. Is there an option to use the vara-fm comport over a gpio pin of the raspberry pi? So that I can use this signal to activate the relay which activates the ptt. I know I can use a digirig, but first I want to see if this is possible. I hope someone can give me a tip if this is possible and how to do it. 73 Ron PD7RON

installed BAP on buster to try and compensate for the ARDOP kernel issue on Bullseye. Ham clock did not install from the build a pi git hub- even though I chose it. Installed HAMCLOCK from home site and tried to use. Says Failed to start RESTful server on port 8080: bind:address already in use. Tried to change port number on page 2 of setup to 5000 but to no avail. I am sure this is a simple answer- but I need help . Thank you, Joseph KD2JO

hi all, i had to reload build a pi (linux 73)on my pi-4. now ham clock is too big for my 7" screen. any way to fix that? thx -- 73 de K5BEZ

Hello, I performed a fresh install of Bookworm and BAP on a PI4 and CONKY is in the center of the screen. There are a few screen issues. The "HAM RADIO" tab will not scroll down and HAM CLOCK is too big for the screen. I found a past post for this issue with Bullseye and was unable to remedy this concern. I know it has to be a screen setting issue. -73 Andrew

Hi has anyone done an install of 73 on top of build a pi, looking to update,but just wondering if its easy or a painful expriance Lee

Will BAP or 73Linux work OK with the 64bit Raspberry Pi OS? If so what would be the better choice? 73 Glenn VE9GJ

Don't have time to test this but wanted to share what was posted on GitHub. Please let us know if you test and it works for you. To use Conky on wayland, add these two lines on your Conky script. conky.config = { out_to_x = false, out_to_wayland = true, Change own_window_type to ‘override’ ( own_window_type = ‘override’,) If you add these lines, Conky will works on Wayland without any issue. But Conky will not load on Xorg . -- 73, de KM4ACK YouTube | Tip Jar Twitter | Store Patreon

I don't know if the evolve has the same issue, but the wo-we sure does! After some hunting about, it is apparently the generic kernel ending in "86", and, on my recent update, it is the generic "87" update, with these issues, at least on the wo-we. IOW, since the problem was first reported with the generic "86" kernel, a generic "87" kernel was released. The "86" kernel presented with the green screen. The latest "87 kernel presents the jumpy digital static pattern. Summarizing, after the final login, when all looks like it will finish booting into 73linux, the screen goes all catawampus, a digital jumpy static pattern not readable by a baseline human computer user. So per a posting here... https://forums.linuxmint.com/viewtopic.php?t=405203 when the first LM logo appears after a cold boot, do the 'ol CTRL ALT DELETE This brings you into advanced options. After selecting advanced options, per the postings, I selected it to boot using the Kernel genric "84". It is now running with a viewable screen, and all seems to be working with the 73Linux installs. Before switching back to the "84" kernel, that is, before doing the CTRL ALT DELETE procedure, I was able to click on the options in the normal Linux Mint login dialog, and select Cinnamon (software render), and that was able to draw the screen properly, with (I imagine) even the generic "87" kernel, but it is slower and laggy due to the software rendering option. Software rendering puts more load on the already very busy two cores in the 12VDC WO-WE. If anyone encounters the updated fix in a new kernel, a fix that does not require loading an older kernel or the option of software rendering, please post that the Linux Mint devs have fixed this definite problem. I'll be checking this thread daily to see if anyone posts here that the fix is now available by another apt update upgrade cycle. Thank you. 73 K4GMV Karl