¿ªÔÆÌåÓý

update/upgrade


 

So, before I bothered to find out what the repercussions of doing a update/upgrade, I went ahead and did it. Now I see that the OS upgrade to Bookworm has thrashed the operation of the IO on the RPi. The general consensus for repair appears to be an upgrade to 1.8 Direwolf, and a re-compile. As there seems to be no tutorial, and I am not a programmer, I am effectively no longer providing the only area two way APRS internet gateway access. At this point I am not willing to continue this fight, so I am QRT, at least until a tutorial appears, and then I will have to see if I want to spend a lot of time going through all the pain and suffering of a rebuild.
Thanks to everyone who answered my questions. 73 to all. ve7bul, QRT.


 

¿ªÔÆÌåÓý

Hello Gil,

So, before I bothered to find out what the repercussions of doing a update/upgrade, I went ahead and did it. Now I see that the OS upgrade to Bookworm has thrashed the operation of the IO on the RPi. The general consensus for repair appears to be an upgrade to 1.8 Direwolf, and a re-compile.

Yup.. a serious bummer.? Blame the stewards of the Raspberry Pi OS for doing major changes mid-release to the Bookworm version.? <sigh>


As there seems to be no tutorial, and I am not a programmer, I am effectively no longer providing the only area two way APRS internet gateway access. At this point I am not willing to continue this fight, so I am QRT, at least until a tutorial appears, and then I will have to see if I want to spend a lot of time going through all the pain and suffering of a rebuild.

This has been documented in the Direwolf User Guide ( ) for many years - Section 5.? I know it sounds intimidating but it's not difficult and once you do it a few times, it's really not a big deal.? If you would like more of a Cookbook style set of instructions of how to do this which also creates proper Debian-style packages, you can follow my guide at:

?
???? - Follow section 17, then 24.c

--David
KI6ZHD


 

It is easy to accommodate this new type of GPIO access.
See Radio Interface Guide, section 7.2.2.


Let us know if you have any problems following the instructions.

73,
John WB2OSZ


 

David, your instructions at section 24c do not work as they are.
sudo mv create-new-direwolf-deb.sh /usr/local/bin

This works and creates the file but when I go to execute, after cd /usr/local/bin and ./, I get,
ERROR: Direwolf source directory not found.? Aborting

This line does not appear to exist yet:
cd /usr/src/archive/Rpi-scratch/direwolf/direwolf  There is no .../archive/....
This line does exist, and a create-new...sh does exist. Is this the script I should execute from this location?
/usr/local/bin/create-new-direwolf-deb.sh

Does this have anything to do with the RPi OS as opposed to Centos? I see Centos is mentioned a few times. This could be me just messing it up somewhere too. 
Thanks.


On Sat, Jul 13, 2024 at 1:58?PM WB2OSZ via <wb2osz=[email protected]> wrote:
It is easy to accommodate this new type of GPIO access.
See Radio Interface Guide, section 7.2.2.


Let us know if you have any problems following the instructions.

73,
John WB2OSZ


 

It appears that the .pdf recommended is for connecting the radio to the interface. The interface being whatever method is decided upon. I very much do not need information on how to connect a radio to the computer for instance. My problem is the OS upgrade disabling the IO on the RPi. The problem is software, not hardware. This gateway WAS working fine until I did an update/upgrade and then it was AFO.

On Sun, Jul 14, 2024 at 11:34?AM Gil Rand via <gilrand=[email protected]> wrote:
David, your instructions at section 24c do not work as they are.
sudo mv create-new-direwolf-deb.sh /usr/local/bin

This works and creates the file but when I go to execute, after cd /usr/local/bin and ./, I get,
ERROR: Direwolf source directory not found.? Aborting

This line does not appear to exist yet:
cd /usr/src/archive/Rpi-scratch/direwolf/direwolf  There is no .../archive/....
This line does exist, and a create-new...sh does exist. Is this the script I should execute from this location?
/usr/local/bin/create-new-direwolf-deb.sh

Does this have anything to do with the RPi OS as opposed to Centos? I see Centos is mentioned a few times. This could be me just messing it up somewhere too. 
Thanks.

On Sat, Jul 13, 2024 at 1:58?PM WB2OSZ via <wb2osz=[email protected]> wrote:
It is easy to accommodate this new type of GPIO access.
See Radio Interface Guide, section 7.2.2.


Let us know if you have any problems following the instructions.

73,
John WB2OSZ


 


Gil -

See Radio Interface Guide, section 7.2.2.


Section 7.2.2 describes exactly what you need to do to solve the issue with the latest OS changing the method needed to access GPIO.

73,
John WB2OSZ


 

I see what you are saying. I did not download the file and I have now. I did not get as far as I needed to to find the pertinent information. Maybe I'll give it a spin and see what happens. Thanks.

On Sun, Jul 14, 2024 at 6:54?PM WB2OSZ via <wb2osz=[email protected]> wrote:

Gil -

See Radio Interface Guide, section 7.2.2.


Section 7.2.2 describes exactly what you need to do to solve the issue with the latest OS changing the method needed to access GPIO.

73,
John WB2OSZ


 

Thanks John for the input and the patience to point me in the right direction. I followed the instructions in 7.2.2 and used Filezilla to transfer my original .conf to the Rpi and modified it with nano. The PTT GPIOD gpiochip0 25, and DCD GPIOD gpiochip0 24. I did a systemctl restart direwolf and it restarted. I checked and I was already up and running again. It actually was not as hard as I had anticipated, but I would have been SOL without the guide. So far so good, thanks again.


On Sun, Jul 14, 2024 at 7:01?PM Gil Rand via <gilrand=[email protected]> wrote:
I see what you are saying. I did not download the file and I have now. I did not get as far as I needed to to find the pertinent information. Maybe I'll give it a spin and see what happens. Thanks.

On Sun, Jul 14, 2024 at 6:54?PM WB2OSZ via <wb2osz=[email protected]> wrote:

Gil -

See Radio Interface Guide, section 7.2.2.


Section 7.2.2 describes exactly what you need to do to solve the issue with the latest OS changing the method needed to access GPIO.

73,
John WB2OSZ


 

¿ªÔÆÌåÓý


Hello Gil,

David, your instructions at section 24c do not work as they are.

Ok.. thanks for the report


sudo mv create-new-direwolf-deb.sh /usr/local/bin

This works and creates the file but when I go to execute, after cd /usr/local/bin and ./, I get,
ERROR: Direwolf source directory not found.? Aborting

This line does not appear to exist yet:
cd /usr/src/archive/Rpi-scratch/direwolf/direwolf  There is no .../archive/....
This line does exist, and a create-new...sh does exist. Is this the script I should execute from this location?
/usr/local/bin/create-new-direwolf-deb.sh

A challenge with my documentation and arguably ANY documentation is that it makes assumptions that certain things exist from a previous section.? This is covered in Section 16 but it's probably not obvious enough.? I will make some improvements here to make sure people creates the required base directory:

?? sudo mkdir -p /tmp/usr/src/archive/Rpi-scratch



Does this have anything to do with the RPi OS as opposed to Centos? I see Centos is mentioned a few times. This could be me just messing it up somewhere too. 

No.. has nothing to do with Centos.? The "centos" you see is probably just in the URL itself.? It's a long standing holdover that I need to clean up.? Sorry for the confusion here.

--David


 

Thanks for the info David. My programming expertise ends after cut/copy/paste with Linux, so I was not successful as the steps were written. The
did work for me. ve7bul-10 is back on the air. Thanks again to all for the assistance.


On Mon, Jul 15, 2024 at 9:09?AM David Ranch via <direwolf-groupsio=[email protected]> wrote:

Hello Gil,

David, your instructions at section 24c do not work as they are.

Ok.. thanks for the report


sudo mv create-new-direwolf-deb.sh /usr/local/bin

This works and creates the file but when I go to execute, after cd /usr/local/bin and ./, I get,
ERROR: Direwolf source directory not found.? Aborting

This line does not appear to exist yet:
cd /usr/src/archive/Rpi-scratch/direwolf/direwolf  There is no .../archive/....
This line does exist, and a create-new...sh does exist. Is this the script I should execute from this location?
/usr/local/bin/create-new-direwolf-deb.sh

A challenge with my documentation and arguably ANY documentation is that it makes assumptions that certain things exist from a previous section.? This is covered in Section 16 but it's probably not obvious enough.? I will make some improvements here to make sure people creates the required base directory:

?? sudo mkdir -p /tmp/usr/src/archive/Rpi-scratch



Does this have anything to do with the RPi OS as opposed to Centos? I see Centos is mentioned a few times. This could be me just messing it up somewhere too. 

No.. has nothing to do with Centos.? The "centos" you see is probably just in the URL itself.? It's a long standing holdover that I need to clean up.? Sorry for the confusion here.

--David