Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • It feels like there could be a middle ground here where the Pi would show some annoying error message at boot that the RAM doesn't match the CPU's anticipated spec.

    Any sellers caught doing this would quickly be flagged by the community as unreliable; also purchase protection is pretty strong these days.

  • It would be much more user friendly if there was a way to check the serial of a particular PI and see it's original hardware config, manufacture date, and so on.
  • I love how we think we own our hardware, but secretly we don't. Surprised though that even a Raspberry Pi now thinks this as well. They grew big _because_ of tinkering...
  • Reading through the EEPROM repo issue[1] makes me a little more sympathetic to the "feature", but I still don't like it at all.

    It might help in the short term to stop dodgy resellers who mod the boards with cheap upgraded RAM to make a buck or two...

    But the Pi itself is always taking one step forward, one step back in terms of firmware. I've been tinkering with some Qualcomm boards from Radxa and things are slightly better there, though you don't have anywhere near the ecosystem you get with Pi (or onboarding niceties).

    [1] https://github.com/raspberrypi/rpi-eeprom/issues/761

  • They frame this as fraud-prevention but I don't really buy it.

    I think of I this way. As a casual/hobbyist user, maybe I'm happy to accept a 10% risk of the device failing prematurely in exchange for saving $20 on a memory upgrade. Ok, so these unscrupulous sellers will never tell me that info up-front...but this defective-by-design system doesn't help me either. The sellers playing this shady game might not accept returns (one example of this already in the github issue linked from the main thread) and there's no sign anything's wrong until you receive and boot up. So the user is left holding the bag, with kneecapped memory capacity, and the same stability risks anyway!

    If these DRAM-upgraders are really so clever, they'll find a way to bypass this (patched firmware or hacked serial in the CPU). At least, it'll work until the user is out of the 30-day period when they finally update the firmware.

    Or if the CPU/mainboard can really detect this in a non-defeatable manner, why cut the usable memory? Just print something to dmesg or stderr when the user logs in. "This device's memory has been modified and may be unstable, warranty blah blah"

    Apple locks down fingerprint/camera module swaps, but at least there's a plausible (afaik) security rationale for it. Seems like Raspberry just got tired of being undercut on price.

  • The real story here is that people are selling modded Pis as higher-memory versions. And this check actually caught them + is circumventable. The restriction is somewhat annoying to a small subset of enthusiasts but seems to catch genuine fraud.
  • I think they should instead just introduce a clear system for verifying that a Raspberry Pi is genuine. For example, a code printed directly on the device. If you enter that code on the website, you can see exactly which model it belongs to and how often it has been used. That way, you could determine whether a Raspberry Pi is new or used and whether it has been modified. I saw that once at a thermal paste manufacturer. They used it to solve the problem of counterfeit thermal paste.You just have to get people to actually use the system and tell anyone else who asks for support but doesn't have an original copy to GTFO.This would allow them to avoid the increased support burden without limiting people's ability to upgrade their Raspberry Pi.
  • There were sellers buying the smallest RAM units, changing the RAM chips, and then reselling them as the higher RAM SKUs. The sellers who do this don’t always care to use good RAM chips and may even use QA reject parts. When the unit doesn’t work correctly, the anger and RMA requests are directed back at the Raspberry Pi foundation.

Explore Birbla archives