Tag: raspberry pi

Posted on

Raspbian Buster – fixing “The repository ‘http://raspbian.raspberrypi.org/raspbian buster Release’ no longer has a Release file”

I have a number of Raspberry Pis that I tinker with every now and then, but not on a regular basis. On my Pi400 I have Rasbian Buster. I just tried a ‘sudo apt update’ and got this error:

E: The repository 'http://raspbian.raspberrypi.org/raspbian buster Release' no longer has a Release file.

From this post, apparently the apt repos for Buster have changed, so you need to edit /etc/apt/sources.list.d/raspi.list and replace

deb http://archive.raspberrypi.org/debian/ buster main

with

deb https://legacy.raspbian.org/raspbian/ buster main contrib non-free rpi

apt update again and all should be good.

Posted on

Running Direwolf on Mac vs Raspberry Pi – using a FTX-1 for Packet

I’ve been taking a look at running Direwolf on my Mac to use my new FTX-1 for some Packet Radio. I’m currently stuck trying to diagnose whether Direwolf is getting any audio or not – it’s not decoding anything so I’m suspecting it’s not. The FTX-1 over USB is working flawlessly with WSJT-X so I know audio over USB is reaching the Mac, I’m just not sure what’s going on with Direwolf yet, despite configuring it to use the same “USB Audio Device” as input and output.

I’ve spent a lot of time using Direwolf on the Raspberry Pi – it’s interesting that my previous summary of steps to build and install Direwolf from source still work perfectly.

Posted on

Serial connection to a Raspberry Pi: more useful info

From my previous post I noticed that I couldn’t re-connect to the Pi using screen after I’d disconnected using Ctrl-A Ctrl-D. Reading additional suggestions here, Ctrl-D is just a disconnect, it doesn’t end the process that’s attached.

Instead, use Ctrl-A Ctrl-\ and it will ask if you want to terminate processes using screen.

If you do detach, from here you can use this command to list processes attached to the serial port:

fuser /dev/tty.usbserial-11240

This will show a pid that you can kill, and then you can reattach again.

Posted on

Raspberry Pi “Temporary failure in name resolution” errors every couple of days

I have a Raspberry Pi running PiAware headless (no monitor/keyboard/mouse) that I moved from wired ethernet to wifi, and every few days it becomes unreachable over wifi, but the activity lights appear to show it’s still up.

Looking through the syslog entries, around the time it appears to drop off the network there is this error that starts repeating:

Aug 31 00:00:09 piaware ntpd[14162]: error resolving pool 3.debian.pool.ntp.org: Temporary failure in name resolution (-3)

This post appears to see the same thing, and there’s a suggestion to turn off the power save function on the wifi:

sudo iwconfig wlan0 power off

I’ve given this a go and will monitor over the next few days.

Proudly powered by WordPress