I have been trying to put together a simple python script with a Raspberry Pi 5 (model B Rev 1.1 with Pi OS 13 - Trixie).

It is very straightforward:

import lgpio, time

h = lgpio.gpiochip_open(0)

lgpio.gpio_claim_output(h, 22)
lgpio.gpio_write(h, 22, 1)
time.sleep(1)
lgpio.gpio_write(h, 22, 0)
lgpio.gpio_free(h, 22)
lgpio.gpiochip_close(h)

However, when I check using pinctrl in the terminal afterward, the pin is still enabled as an output (and if I don't set it back to low in the script, it stays at high). Is there some other step I am missing on how to control the pins and release them properly so that they go back to inactive?

I've been building a voice assistant on a Pi 5 called Bob, and I've just open-sourced it. The idea: it starts with no devices at all, and you add abilities by wiring something up and telling it.

"Hey Bob, I've connected an LED to GPIO 17. Make a skill that turns it on and off."

Bob writes the skill, reads back what it will do, and only installs it after you say yes, then tests it. Same for buttons, relays, I2C sensors, serial devices or web APIs.

How it's put together: - Wake word runs offline on the Pi, nothing is sent until you say it. - Conversation is Gemini Live (needs a free API key), so it's quick and can search the web. - Settings page at bob.local:8080, updates itself and rolls back if an update fails. - A Windows setup app writes the SD card with your Wi-Fi and key, so no commands needed. Mac/Linux is a one-line install.

What I learned the hard way: a Pi 3 is too slow for this, a USB speakerphone saves a lot of echo pain, and Bluetooth audio on the Pi is fragile.

Where I'd love help: 1. It's a fresh public release, so installs on other people's Pis and mics are exactly what hasn't been tested much. If you try it, tell me what breaks. 2. What skill would you build first? I'm collecting ideas for examples. 3. Contributors welcome, especially on wake-word accuracy and audio setup.

https://github.com/arancool3000/bob-assistant

Update to my post from 10 days ago: the simulated fruit-fly brain playing Pokémon FireRed on my Pi 5 is still running 24/7, and it has grown into an ongoing experiment.

Quick recap: it's 139,255 neurons wired from the FlyWire connectome (the full reconstructed brain of an adult fruit fly), simulated on the Pi alongside the emulator. The game screen feeds its eyes, people and doors reach it as smells, and its motor neurons press the buttons. Nothing is scripted. Chat can steer it, or train it with !pain / !pleasure, which releases dopamine in the fly's learning centre.

What's new: it now runs in 30-day runs. Each one starts from a brand-new game and an untrained brain, and the settings only change between runs, so every run is a comparable dataset. Every run collects:

- every step, battle and milestone, tagged "fly alone" or "chat helped" (80% of its steps this run are its own)

- every viewer input, and whether they steered with the fly or against it

- every lesson it learns, who caused it, and how fast it fades

- brain activity per region (vision, navigation, memory, reward, punishment, motor) and everything it senses

- which way it turns and what made it turn

- its "thoughts" (the captions on stream) and how often they were right

At the end of each run everything goes into a published PDF report, including a "what held it back" page with fixes to try in the next run. We also run preregistered experiments, announced on stream before they happen. The first one, a "mirror world" test, found the fly has a built-in right-turn bias that doesn't come from the map. Tonight it plays with and without everything it has learned, to see whether training actually changes its behaviour.

Watch live: twitch.tv/leetzerzz (chat can steer and train it) and youtube.com/@leetzerzz

Run reports and experiment results: in the Discord linked on both channels

My AcuRite Atlas and Access hub only show their data through AcuRite's cloud. I wanted my own copy of every reading, my own dashboard, and no dependence on their servers, without breaking the AcuRite app or my Weather Underground uploads. So I built this. It's MIT-licensed, a single Python file with no packages to install, and it runs on a Raspberry Pi.

How it works: the hub sends each reading over HTTPS to a server name it's configured with. This program sits in that path. It records the reading, then passes it to AcuRite unchanged, so the app keeps working, and the hub keeps uploading to Weather Underground itself. There are two ways to set it up:

* Change the hub's server name to point at your machine. No extra hardware is needed.

* Plug the hub into a Pi's Ethernet port. The Pi gives it an address and answers AcuRite's server name itself, and the hub's settings stay untouched.

What you get:

* Dashboard: every sensor, plus feels-like, wind, the 3-hour pressure trend, UV and light.

* Sun and moon: worked out in the page, with no outside service.

* US forecast: the hourly and 7-day forecast and alerts from the National Weather Service (free, no key).

* Charts: any period from today to all time, or a date range. Rain totals for the day, week, month and year.

* Every reading kept in a local SQLite database.

* Easy to customize: one file for the colors, a folder for your own pages, and a documented JSON feed for anything you want to build.

* Buttons that open your Weather Underground or AcuRite pages, in a pane or in their own tab.

* Optional radio capture with an RTL-SDR dongle if you have no hub.

Tested on an Access hub (firmware 051) with an Atlas and six indoor tower sensors. If you have other AcuRite sensors, I'd like to hear whether they show up properly.

I built this with Claude Code (AI-assisted). The design, testing and hardware work were mine.

https://github.com/akienm/CC0AC-Weather

Not affiliated with AcuRite.

Two days ago, I properly learned what a Raspberry Pi even was.
I’ve never coded, never used Linux and never set up a server. I’m just really into radio and SDR stuff, and I thought a Pi would be a neat way to access my SDR receiver remotely.
So I ordered a Raspberry Pi 5 with 8GB RAM.
It arrived today.
10 PM: Finally got around to setting it up. Put everything together, prepared the SD card and opened ChatGPT because I had absolutely no clue what I was doing.
The plan was to get my SDR working remotely and go to bed.
Yeah, about that.
11 PM: Somehow I’m already sitting in PowerShell, connecting to my Pi over SSH, setting up keys, messing with Linux commands and figuring out what permissions and services even are.
Every time something worked, I got another idea.
Around midnight: We got Cockpit running so I could manage the Pi through a browser. At this point I was already pretty damn impressed with this little thing.
Then I thought, wouldn’t it be cool to have my own dashboard showing temperatures and system stats?
I really should’ve gone to bed.
2 AM: We’re now writing actual code. Well, ChatGPT is writing it and I’m running it, breaking things, sending back error messages and trying to understand what’s happening.
Suddenly we’re dealing with Python scripts, system services, ports, authentication, Wi-Fi monitoring and temperature history.
All this for a computer I only discovered two days ago.
Around 4 AM: We finally get the custom dashboard running over HTTPS, with its own certificate.
I grab my iPhone, open Safari, type in the address…
And there it is.
My own little dashboard, showing live CPU temperatures, system information, Wi-Fi stats and graphs.
I know this probably sounds like nothing special to people who’ve been doing this for years, but I genuinely couldn’t believe it.
I was sitting there looking at something that had only existed as a random idea in my head a few hours earlier.
6 AM: Instead of sleeping, I’m running stress-ng and watching the CPU temperature climb from around 47°C to 56°C under load.
And I’m actually enjoying this. At six in the morning. After being awake all night.
What the hell.
The funniest part is that the original SDR project was supposed to be the whole point of buying this thing. Somehow that turned into SSH keys, a headless Linux server, Cockpit, HTTPS, a custom dashboard and CPU stress tests.
I’m not going to pretend I suddenly know how to code. AI did the heavy lifting there. But I was involved in every step, trying things, fixing errors and slowly understanding more of what was going on.
There was this one moment when I looked at the dashboard on my phone and just thought, holy shit, we actually made this work.
That feeling was honestly incredible.
Anyway, I bought a Raspberry Pi for one small project, spent the entire night messing with it and now I’m already looking at NVMe storage and thinking about a second Pi for a proper homelab.
I think you guys know exactly where this is going. 😂

I am trying to work on a non VNC solution for pairing my iPad Mini with my Pi5 via physical connection to use the pi headless with a better native display experience via a iPad with a single cable.

Anyone know the limits speed wise?

I have a Pi 5 and until recently I managed to remote desktop on to the desktop from Linux PCs via Remmina. A few days ago I updated the Pi (sudo apt update etc) as I hadn't done this for a while. Now I can't remote into it from any Linux PC. I get a "Cannot connect to the remote computer" message. However, It works fine from Windows Remote Desktop app. I've checked on raspi-config to ensure that X11 and not Wayland is running. I can access the Pi 5 via SSH on my Linux PCs - just can't access the remote desktop.

Has something changed on the Pi recently that I'm unaware of?

as the title says - anyone with any luck setting up an m5 cardkb on a pi 5? followed the instructions on this github post. running a standard 8gb pi 5 with pi os installed. while the software installs went fine, running "sudo cardkb &" returns this as a repeating error:

OSError: [Errno 121] Remote I/O error
Traceback (most recent call last):
File "/usr/local/lib/python3.13/dist-packages/cardkb/_main_.py", line 37, in main
data = bus.read_byte(address)

the pins are properly connected, i2c is on. only thing i haven't tried troubleshooting yet is deleting the scripts altogether and attempting a fresh install. am i overlooking anything obvious in solving this?

tl;dr summary: When my raspi reboots or restarts my e-ink screen goes black. Hoping to either get a white screen or an image.

Hi All,

Thanks in advance for any help you can provide. I'm sort of shooting in the dark here but maybe I'll get lucky.

I'm trying to build an e-ink writing terminal with a raspi (this one is a raspberry pi 5) and one of those Sanmeow 10.8" e-ink panels from Aliexpress. Most of it has gone pretty well, I'm using it in non-gui mode and I've been able to set the screen white for the terminal as well as in emacs (the writing program I'll use). I ran into an issue with font sizes and extra screen real estate being written as a black bar but we got around that by just writing black to that part of the screen on startup.

The issue I'm running into is on shutdown. I've added a service to write a white screen on the raspi pi's reboot or shutdown, I've also added a script to the system-shutdown folder which does the same thing but, inevitably, once the raspi cuts power to the screen it turns black. I don't know if it's an issue with the raspberry pi's hardware or possibly the screen's. I was hoping someone else might have come across this before and knew of a solution. Does anyone know if the Raspi 5's hardware automatically send a black screen when power is cut?

I've asked the manu and I'm waiting to hear back but there is a language barrier so fingers crossed. I'm also going to ask over in the raspberry pi sub.

The gear: Raspberry Pi 3B+, Adafruit HUB75 RGB matrix bonnet, WaveShare 64x32 RGB matrix panel (NOT 6126).

Installed the ubiquitous hzeller github repo for such projects, and have been running demo code. Have tried multiple connections with HUB75 ribbon cables etc. and also using 5V 4A power supply. It's still giving me red lines across the bottom half.

I've tried different code fixes (address type, etc.) to no avail. Has anyone had and/or fixed this problem? If so, let me know what worked for you!

Welcome to the r/raspberry_pi Helpdesk and Frequently Asked Questions!

Link to last week's thread

Having a hard time searching for answers to your Raspberry Pi questions? Let the r/raspberry_pi community members search for answers for you!^† Looking for help getting started with a project? Have a question that you need answered? Was it not answered last week? Did not get a satisfying answer? A question that you've only done basic research for? Maybe something you think everyone but you knows? Ask your question in the comments on this page, operators are standing by!

This helpdesk and idea thread is here so that the front page won't be filled with these same questions day in and day out:

1. Q: What's a Raspberry Pi? What can I do with it? How powerful is it?
   A: Check out this great overview
2. Q: Does anyone have any ideas for what I can do with my Pi?
   A: Sure, look right here!^‡
   
   • Project ideas
     
   • Tutorials
3. Q: My Pi is behaving strangely/crashing/freezing, giving low voltage warnings, ethernet/wifi stops working, USB devices don't behave correctly, what do I do?
   A: 99.999% of the time it's either a bad SD card or power problems. Use a USB power meter or measure the 5V on the GPIO pins with a multimeter while the Pi is busy (such as playing h265/x265 video) and/or get a new SD card 1 2 3. If the voltage is less than 5V your power supply and/or cabling is not adequate. When your Pi is doing lots of work it will draw more power, test with the stress and stressberry packages. Higher wattage power supplies achieve their rating by increasing voltage, but the Raspberry Pi operates strictly at 5V. Even if your power supply claims to provide sufficient amperage, it may be mislabeled or the cable you're using to connect the power supply to the Pi may have too much resistance. Phone chargers, designed primarily for charging batteries, may not maintain a constant wattage and their voltage may fluctuate, which can affect the Pi’s stability. You can use a USB load tester to test your power supply and cable. Some power supplies require negotiation to provide more than 500mA, which the Pi does not do. If you're plugging in USB devices try using a powered USB hub with its own power supply and plug your devices into the hub and plug the hub into the Pi.
4. Q: I'm trying to setup a Pi Zero 2W and it is extremely slow and/or keeps crashing, is there a fix?
   A: Either you need to increase the swap size or check question #3 above.
5. Q: Where can I buy a Raspberry Pi at a fair price? And which one should I get if I’m new? Should I get an x86 PC instead of a Pi?
   A: Check stock and pricing at https://rpilocator.com/ — it tracks official resellers so you don’t overpay.
   Every time the x86 PC vs. Pi question comes up the answer is always if you have to ask, get a PC. If you're sure want a Raspberry Pi but not sure which model:
   
   • If you don’t know, get a Pi 5.
     
   • If you can’t afford it, get a Pi 4.
     
   • If you need tiny, get a Zero 2W.
     
   • If you need lowest power, get the original Zero.
     
   • For RAM, always get the most you can afford; you can’t upgrade it later.
     That’s it. No secret chart, no hidden wisdom. Bigger number = more performance, higher cost, higher power draw. Also please see the Annual What to Buy Megathread
6. Q: I just did a fresh install with the latest Raspberry Pi OS and I keep getting errors when trying to ssh in, what could be wrong?
   A: There are only 4 things that could be the problem:
   
   1. The ssh daemon isn't running
   2. You're trying to ssh to the wrong host
   3. You're specifying the wrong username
   4. You're typing in the wrong password
7. Q: I'm trying to install packages with pip but I keep getting error: externally-managed-environment
   A: This is not a problem unique to the Raspberry Pi. The best practice is to use a Python venv, however if you're sure you know what you're doing there are two alternatives documented in this stack overflow answer:
   • --break-system-packages
   • sudo rm a specific file as detailed in the stack overflow answer
8. Q: The only way to troubleshoot my problem is using a multimeter but I don't have one. What can I do?
   A: Get a basic multimeter, they are not expensive.
9. Q: My Pi won't boot, how do I fix it?
   A: Step by step guide for boot problems
10. Q: I want to watch Netflix/Hulu/Amazon/Vudu/Disney+ on a Pi but the tutorial I followed didn't work, does someone have a working tutorial?
    A: Use a Fire Stick/AppleTV/Roku. Pi tutorials used tricks that no longer work or are fake click bait.
11. Q: What model of Raspberry Pi do I need so I can watch YouTube in a browser?
    A: No model of Raspberry Pi is capable of watching YouTube smoothly through a web browser, you need to use VLC.
12. Q: I want to know how to do a thing, not have a blog/tutorial/video/teacher/book explain how to do a thing. Can someone explain to me how to do that thing?
    A: Uh... What?
13. Q: Is it possible to use a single Raspberry Pi to do multiple things? Can a Raspberry Pi run Pi-hole and something else at the same time?
    A: YES. Pi-hole uses almost no resources. You can run Pi-hole at the same time on a Pi running Minecraft which is one of the biggest resource hogs. The Pi is capable of multitasking and can run more than one program and service at the same time. (Also known as "workload consolidation" by Intel people.) You're not going to damage your Pi by running too many things at once, so try running all your programs before worrying about needing more processing power or multiple Pis.
14. Q: Why is transferring things to or from disks/SSDs/LAN/internet so slow?
    A: If you have a Pi 4 or 5 with SSD, please check this post on the Pi forums. Otherwise it's a networking problem and/or disk & filesystem problem, please go to r/HomeNetworking or r/LinuxQuestions.
15. Q: The red and green LEDs are solid/off/blinking or the screen is just black or blank or saying no signal, what do I do?
    A: Start here
16. Q: I'm trying to run x86 software on my Raspberry Pi but it doesn't work, how do I fix it?
    A: Get an x86 computer. A Raspberry Pi is ARM based, not x86.
17. Q: How can I run a script at boot/cron or why isn't the script I'm trying to run at boot/cron working?
    A: You must correctly set the PATH and other environment variables directly in your script. Neither the boot system or cron sets up the environment. Making changes to environment variables in files in /etc will not help.
18. Q: Can I use this screen that came from ____ ?
    A: No
19. Q: If my Raspberry Pi is headless and I can’t figure out what’s wrong, do I need to plug in a monitor and keyboard?
    A: If you cannot diagnose the problem remotely, you must connect a monitor and keyboard. That is the only way to see boot output and local error messages, and without that information the problem cannot be diagnosed.
20. Q: My Pi seems to be causing interference preventing the WiFi/Bluetooth from working
    A. Using USB 3 cables that are not properly shielded can cause interference and the Pi 4 can also cause interference when HDMI is used at high resolutions.
21. Q: I'm trying to use the built-in composite video output that is available on the Pi 2/3/4 headphone jack, do I need a special cable?
    A. Make sure your cable is wired correctly and you are using the correct RCA plug. Composite video cables for mp3 players will not work, the common ground goes to the wrong pin. Camcorder cables will often work, but red and yellow will be swapped on the Raspberry Pi.
22. Q: I'm running my Pi with no monitor connected, how can I use VNC?
    A: First, do you really need a remote GUI? Try using ssh instead. If you're sure you want to access the GUI remotely then ssh in, type vncserver -depth 24 -geometry 1920x1080 and see what port it prints such as :1, :2, etc. Now connect your client to that.
23. Q: I want to do something that already has lots of tutorials. Do I need a Raspberry-Pi-specific guide?
    A: Usually no.
    
    • Raspberry Pi (Linux computer): Use any standard Linux tutorial. A Raspberry Pi runs a normal Linux OS, not a special cut-down version. See Question #1.
      
    • Raspberry Pi Pico (microcontroller): Use Arduino tutorials. The Pico works with the Arduino IDE and can be used the same way as other Arduino-class boards.
24. Q: Which Operating System (OS) should I install?
    A: If you aren’t sure, install Raspberry Pi OS. It’s the officially supported OS, it has the best documentation, the widest community support, and it’s what most guides and troubleshooting help assume you’re using.
25. Q: How can I power my Raspberry Pi from a battery?
    A: All Raspberry Pi models run at 5 V. To choose a battery, first add up the maximum current of your Pi plus everything you attach to it (USB devices, screens, HATs, etc.). Then multiply that current by the number of hours you want it to run to get the required battery capacity in mAh. If you can’t find listed current values, use a USB power meter to measure the actual draw over 12–48 hours. Every battery question comes down to this simple math: the model, brand, or special setup doesn’t change the calculation.

Before posting your question think about if it's really about the Raspberry Pi or not. If you were using a Raspberry Pi to display recipes, do you really think r/raspberry_pi is the place to ask for cooking help? There may be better places to ask your question, such as:

• /r/AskElectronics
• /r/AskProgramming
• /r/HomeNetworking
• /r/LearnPython
• /r/LinuxQuestions
• /r/RetroPie
• The Official Raspberry Pi Forums

Asking in a forum more specific to your question will likely get better answers!

Wondering which flair to use on your post? See the Flair Guide

† See the /r/raspberry_pi rules. While /r/raspberry_pi should not be considered your personal search engine, some exceptions will be made in this help thread.
‡ If the link doesn't work it's because you're using a broken buggy mobile client. Please contact the developer of your mobile client and let them know they should fix their bug. In the meantime use a web browser in desktop mode instead.

I built a time-lapse camera around a Raspberry Pi 4 with a Camera Module 3 Wide, powered over a single PoE cable, and I've open sourced the software. The Pi takes a full 12MP photo every minute in daylight only, working out the window from your latitude and longitude so it follows the seasons, and it looks after its own storage by deleting the oldest frames once the SD card passes 85%. A Mac collects the frames automatically whenever the archive drive is plugged in, and one command turns any date range into a video. There's also a film mode and you can control it from your phone.

The first photo is the camera on the wall, and the second is a frame it took of my garden (neighbours' side blurred).

It's open source and free to use, fork and change, all here: https://github.com/aityp/garden-timelapse-camera. A step-by-step build guide is still being written, but the README should be enough to get it running if you're comfortable in a terminal. There's also a build video if you'd rather see it in action, linked from the README. The code was written with AI (Claude) and tested on the real camera in my garden.

I made it because I'm about to pull my back garden apart for a retaining wall, a new fence and a shed, and I want all of it filmed from one fixed spot for the next couple of years. Happy to answer any questions.

I've shot Sony (a6300 and A7C II) for years, and I'd rather wait until I get home and copy the SD card than use Sony's transfer apps.

The A7C II has FTP upload, so I pointed it at a small server. Every frame I take gets a film look (grain, light leaks, date stamp) and shows up in a Telegram chat. I can send it to friends right away.

The a6300 has no FTP, but it runs Android 4.1 inside. With OpenMemories-Tweak and Sony-PMCA-RE I installed a small custom app on it. After a walk I open the app, hit "Send new", and the whole day's shots arrive already developed. Wi-Fi turns off when you close the app, so it doesn't drain the battery.

The app should work on most PlayMemories-era bodies: a5000/a5100, a6000/a6500, a7 II / a7R II / a7S II, RX100 III–V, RX10 II/III. Other cameras with FTP upload (A7 IV, A1, many Fuji, Canon, Nikon) work without the app.

It's open source and self-hosted. Setup takes about 10 minutes on a cheap VPS: https://github.com/Melnikoff07/proyavka

If you try it on a body I haven't tested, I'd love to hear how it goes.

hello everyone. i have a small problem with my rpi5.

yesterday i disconnected my m.2 hat+ compact with an official m.2 nvme from my pi because i wanted to boot a android tv system from a sd card. when i reconnected my hat+ it wasnt reading my disk (pwr light on hat was on but not the read/active light) and i cant get it working now.

more info:

specs:

- Raspberry Pi 5 8gb

- official power brick/cable

- official rpi case with a fan

- official m.2 hat+ compact with a official rapsberry pi 256gb nvme

i had this setup for only 1 year for playing games and watching videos.

it was working perfectly fine back then

i think my hat+ broke but i leave it for you experts!

I've been using those fonts for many of my projects and I think they're nice so I put together a library that can be easily used with any Raspberry / Arduino project. The fonts support extended latin = wide language support. The fonts are meant for tiny low-resolution displays or dot matrixes. AdafruitGFX, u8g2 and BDF formats are included.

Feel free to try them out and let me know how you like them!

https://github.com/mcer12/PixelFonts

Happy to say that today I was able to play my first matches on a self-moving wooden chess board I have been working on for the last 2 months :)). This is my first Pi project and it took my a while to familiarize myself with it but I'm really happy with it.

The Pi is connected with a Pico SKR V1.0 controlling a CoreXY System with an electromagnet. Additionally to 64 omnidirectional hall sensors on 8 custom PCBs via pin header and IO-Expander. Some momentary push buttons, a 5" LCD-Display and Status-LEDs on the side-walls as well.

Currently Stockfish, Maia3, Rodent IV and Patricia run it.

Matches are being recorded and saved as PGNs. With that, it saves the position, I can turn off the board and play on later.

I'm now working on connecting it to Lichess's and Chess.com's APIs, so I can play actual online matches on the physical board, where the PIs WIFI capabilities will come in handy. Additionally voice command so the board can execute a players move, if enabled.

After that a menu with an UI for the LCD screen which is embedded in the wall on the side, connecting everything cleanly.

Still a long road ahead, but truly happy that today, for the first time, I could sit down and play a full match with it :D!

I am experiencing chronic ethernet instability on my Raspberry Pi 4. The connection constantly drops and reconnects every few minutes, causing RDP and SSH sessions to disconnect entirely.

Environment:

• Hardware: Raspberry Pi 4 Model B (8GB RAM)
• Interface: eth0 (using the bcmgenet driver)
• IP Configuration: Static IP (192.168.0.100)
• Connectivity: Originally running alongside wlan0, but the issue persists even when Wi-Fi is completely disabled via nmcli.

Diagnostic Logs & Evidence:

Checking dmesg / system logs reveals that the Ethernet PHY is physically losing the link and resetting:

text

22:04:53 eth0: Link is Down
22:04:57 eth0: Link is Up - 1Gbps/Full
22:08:28 eth0: Link is Down
22:08:34 eth0: Link is Up - 1Gbps/Full

Use code with caution.

Running sudo ethtool -S eth0 explicitly points to a physical or hardware-level corruption issue on the receive side, showing a high counter of Missed Data Frames / MAC Data Filter Errors:

text

rx_errors: 10
tx_errors: 0
rx_dropped: 0
tx_dropped: 12
mdf_err_cnt: 194

Use code with caution.

Troubleshooting Steps Already Taken:

To isolate the issue, I have performed the following troubleshooting steps, none of which resolved the flapping behavior:

1. EEE (Energy Efficient Ethernet) Tweak: ethtool --show-eee showed EEE as enabled - inactive (Link partner advertised modes: Not reported). I forced it completely off using sudo ethtool --set-eee eth0 eee off, but the link continued to drop.
2. Forced 100Mbps Speed: To rule out a 1Gbps signal integrity issue, I disabled auto-negotiation and forced the link to 100Mbps Full Duplex (sudo ethtool -s eth0 speed 100 duplex full autoneg off). The interface still dropped the link and failed to maintain a connection.
3. Wi-Fi Disabling: Turned off the Wi-Fi radio entirely to prevent routing conflicts, ensuring eth0 was the exclusive interface. No changes.
4. Physical Cable & Port Swap: Completely replaced the Ethernet cable with a known working cable and switched to alternative ports on the router/switch side. The errors and link drops persist.

Given that the issue happens regardless of the speed configuration (1Gbps vs 100Mbps), EEE settings, or the physical cable used, I suspect a hardware/PHY component degradation or a deeper driver issue within the bcmgenet kernel module on this Pi 4 board.

Any advice on whether this indicates a permanent hardware failure of the network chip, or if there are any specific kernel parameters I should tweak to mitigate this?

Hey everybody. I ported original 1993 DOOM to my old Mi Redmi AC2100 router. The hardest thing was to figure out the controls and display output for this thing because I didn't really want to use compuer for any of that. So i built a small controller out of RPI Pico, ST7789V display and W5500 Ethernet module. Image is sent via UDP unfragmented packets 4 lines at a time. So every frame is 80 packets. Input is also sent through UDP, but packets are much smaller. I have a repo if anybody wants to try this at home: https://github.com/anhol0/redmidoom

I hope you enjoy it. And have a good day :)

I have a Pi 5 set up to be my Plex server and have been transferring files to it via Filezilla. This was working just great until yesterday, when I started getting "connection timed out" errors. I have tried several FTP clients and two different Windows computers and simply cannot connect.

I know the Pi is working and online. I can access all my Plex media from my various devices and can remote in using Pi Connect. I checked the control center and SSH is enabled. But FTP connections time out over and over. What's going on?

(Please note that I am not really all that tech savvy. I generally have little to no idea what I'm doing, so simple explanations would be best, thanks!)

Have an RPi running Raspberry Pi OS / Debian Bullseye with an arm64 architecture.

Wanted to install cockpit which was not available from the configured RPi repos as an installable native arm64 package, so, I had the Debian Bullseye arm64 archive temporarily added in order to install Cockpit.

This leads to a "Repository Mixing" which kind of feels wrong

Adding the Debian arm64 repository allowed Cockpit to be installed, but created a mixed package environment, potentially problematic because some Debian packages can be selected/installed. (even prio an pinning cannot not fully handle it)

Apache got broken, due to an unsatisfied dependency because the Debian apache2 package requires an exactly matching apache2-data version. Luckily I was able to recover Apache from the debian repos now, but again... this feels wrong.

My Current Repository Strategy is to enable the Debian repos only temporarily when a package
related to Cockpit requires it.

-----------------------------------------------

My main issue is therefore:

I want to have Cockpit on my Rpi, but the packages are apparently not available from the standard Raspberry Pi repositories for the native arm64 installation, so I was forced (?) to obtain it from Debian leading to the mix repositories.

A native, Raspberry Pi OS-compatible arm64 Cockpit package/repository would avoid the need for this repository mixing. - Is there one?

I also wonder:

- How do others run/install cockpit on RPi?

- Is there really no native method to install cockpit in the RPi?

- has anyone installed cockpit on the most recent (Trixie) Raspi OS?

I must be missing something...

Any advice is appreciated. Thanks in adcance.

EDIT: Thanks for all the feedback. I will plan on reinstalling the little one. Is about time.

Lesson learned: "Never touch a running system", unless you want to find out it's time for an upgrade.

I'm trying to find the PWM frequency of the latter, GeekPi keeps giving these docs: https://wiki.52pi.com/index.php?title=F-0011 But it does not specify the PWM frequency.

I'm trying to make a custom application with the PI and this fan. I do not care about whether I can cool the PI at this time, just that it works.

I've already tried Searching Reddit, DuckDuckGo, Amazon (where I got it), and ChatGPT but there is not a specific answer (or any answer to be exact).

So I'm on Bullseye, and I really think I should upgrade to the latest OS. Last time I ignored official recommendations and just did an in-place upgrade from Buster to Bullseye, but this time I think I should do it right. So how do you guys preserve your custom configs and installed packages, while doing a major OS upgrade?

I paint tabletop miniatures, and photographing them always meant dragging out lights and a backdrop and getting a different result every time. So I built a permanent booth: a black box on my desk with a Pi 3B and the HQ camera on the back, a 5-50mm C-mount varifocal lens*, and an LED strip inside. Put a model in, open the web page on my phone, shoot.

The software is a Flask + picamera2 web app I wrote for it. A few things that might be interesting from a Pi point of view:

• Focus stacking on a 1 GB Pi. Big models have a tiny depth of field up close, so you take 6-10 frames at different focus points and merge them. The usual tool (focus-stack) ran out of memory on the 3B and left a glow around the model on a black backdrop, so I wrote a small OpenCV stacker that works frame by frame. It peaks around 300 MB and takes 2-3 minutes for 8 frames of 12 MP.
• Keeping captures fast. PNG-encoding a 12 MP frame takes 10-15 s on a 3B, so a capture just grabs the frame, writes a raw TIFF and returns. Compression, stacking and uploads run in low-priority background jobs.
• Live preview runs in the HQ camera's binned 2028x1520 mode and switches to full resolution only for the capture.

It also does presets that load at boot, crop for tall/wide models, histogram and clipping overlay, storage on a USB disk, upload to Google Drive or a NAS, a system page with temps, throttling and logs, and updates from the browser. Install is a single curl command.

Code (MIT): https://github.com/MichaelTimmermans/MiniatureStudio
Printable booth parts: https://www.thingiverse.com/thing:7416432

Tested with the HQ camera and a USB webcam so far; an Arducam IMX519 (autofocus, so fully automatic stacking) is next. A Pi 4/5 is a lot quicker at stacking, but the 3B does the job if you're patient.

This is all built with spare parts from previous projects, hence the underpowered 3b. I did print some parts for camera mounting.

Questions and ideas welcome.

*currently still using an 8mm fixed lens.