By Raspberry Pi quietly shipped a firmware change in late 2024 that prevents users from swapping RAM chips on the Raspberry Pi 5. Jeff Geerling published his full analysis on September 21, 2026, and the Hacker News thread that followed confirmed the community had not forgotten the platform’s founding promise. The lockdown is enforced through the Pi 5’s closed-source EEPROM bootloader. The fraud problem it addresses is real. The way Raspberry Pi chose to solve it is wrong — and there is a better option the Foundation has used before.
What Raspberry Pi 5 Locked Down
EEPROM firmware versions dated 2024-09-23 or later include a RAM chip validation check. When the Pi 5 detects a chip that does not match its allowlist, it refuses to boot: the green ACT LED blinks eight times, which is the SDRAM failure code. This blocks not just cheap counterfeits — it also blocks legitimate same-capacity RAM chips transplanted from other Pi 5 boards, which is particularly frustrating for repair use cases.
The restriction is enforced through the Pi 5’s EEPROM, which stores its bootloader as a closed-source binary blob. There is no configuration option to disable the check, no documentation explaining exactly which chips are permitted, and no way to inspect the validation logic without reverse engineering the firmware. The only current workaround is downgrading to EEPROM firmware 2024-09-10-2712 or earlier — which also means forgoing every security patch and bug fix Raspberry Pi has shipped since.
# Check your current EEPROM firmware version
rpi-eeprom-updateThe Problem Raspberry Pi Is Trying to Solve
The fraud issue is documented and real. Resellers were buying 1GB or 2GB Pi 5 boards — the cheapest configurations — soldering in cheap, sometimes QA-rejected 8GB RAM chips, and selling the results as genuine 8GB units at significant markup. LPDDR memory timing is legitimately tricky: incompatible chips cause instability that is hard to diagnose, particularly under thermal stress. Customers with these modified boards were contacting the Raspberry Pi Foundation for warranty support, not the resellers who sold them.
That is a real problem. However, it does not justify locking down a hardware platform that built its entire reputation on the idea that you own it and can modify it.
The Wrong Solution — and the Right One
As Geerling points out, Raspberry Pi has already solved this kind of problem before. The Pi 3B included an overclocking “warranty bit” — a one-time flag that users could set, permanently voiding their warranty in exchange for unlocking overclocking. The Pi Foundation provided the tool, documented the consequence, and let users make the choice. That approach respected hardware ownership while managing the support liability.
The same model works here. A one-time firmware flag — “I am swapping RAM; I forfeit warranty support for this unit” — would neutralize the reseller fraud problem. Raspberry Pi could reject RMA requests from boards with the flag set. Legitimate tinkerers could still perform hardware modifications. The only people who cannot live with that tradeoff are the fraudulent resellers, which is precisely the group Raspberry Pi wants to stop.
Alternatively, Pi already publishes model codes that identify board configuration. Displaying a warning at boot (“RAM mismatch detected — support unavailable”) would achieve the same accountability without a hard block. A warning is not a lockdown.
What This Signals
Raspberry Pi went public in June 2024. Since then: multiple price increases tied to memory shortages, a growing range of SKUs with large price gaps between RAM tiers, and now a firmware restriction enforced through a closed-source bootloader. The Pi 5 8GB costs substantially more than the 1GB model. When someone can buy three 1GB Pi 5s, perform a RAM swap, and end up with a functional 8GB unit for less money — that is a direct threat to a revenue stream a public company’s shareholders notice. While this speculation is unconfirmed, the Hacker News thread put it plainly: “Whose hardware is it anyways? Yours, when you pay for it.”
This pattern has appeared elsewhere. The maker community saw similar tensions when Arduino moved away from open-source commitments and when embedded platforms added commercial licensing layers. Hardware platforms built on hacker trust are especially fragile when commercial incentives start overriding community values.
What to Do
If you have a Pi 5 and want to preserve hardware modification capability, stay on EEPROM firmware 2024-09-10-2712 or earlier. The tradeoff is real: you will not receive firmware bug fixes or security updates from any later release. For production deployments, that is not acceptable. For a home lab or development board where you plan to modify the hardware, it may be a deliberate choice worth making.
If you are buying a new Pi 5 and expect to need 8GB, buy the 8GB model today. The firmware lock makes the cheaper-SKU-plus-upgrade path unreliable and potentially impossible on future boards.
The Pi community built this platform into what it is by pushing boundaries and tinkering at every level. Raspberry Pi Foundation should hear clearly that a firmware restriction enforced through a closed binary is not acceptable when a warranty-void flag would accomplish the same goal. Submit feedback on the rpi-eeprom GitHub repository. The old approach was better, and it is worth asking for it back.
