They’d never do that.
They SHOULD. Everyone had too much memory and it’s too dense. We should all have ECC by now.
Unless AMD does it I don’t think it will happen. Even if they do I feel like OEMs wouldn’t want it because memory would suddenly cost 2¢ per GB (or whatever) and refuse.
Any ATX solutions are super expensive: https://solidrun.atlassian.net/wiki/spaces/developer/pages/5...
https://www.intel.com/content/www/us/en/products/docs/proces...
Will it help at all or is it a waste of time?
Nevertheless, this will rarely matter for the kind of applications typically run on small computers with Atom CPUs, which are rarely more demanding than a router/firewall or a network-attached storage server.
You can see examples of performance decrease with IBECC here:
https://www.cnx-software.com/2024/05/26/odroid-h4-plus-revie...
For most applications the performance decrease should be less than 10%. The Intel IBECC controller includes a special cache memory, to decrease the number of additional memory accesses required by IBECC. Otherwise the memory performance would have been halved.
Besides the Alder Lake N or Amston Lake CPUs that are branded as the Atom x7000 series, some of the models branded as N CPUs, e.g. N97 and i3-N305 also have a functional IBECC controller, if the computer BIOS provides means to enable it.
[ 8.485808] [ T703] caller igen6_probe+0x138/0x780 [igen6_edac] mapping multiple BARs
[ 8.487601] [ T703] EDAC MC0: Giving out device to module igen6_edac controller Intel_client_SoC MC#0: DEV 0000:00:00.0 (INTERRUPT)
[ 8.487625] [ T67] EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR
[ 8.487626] [ T67] EDAC igen6 MC0: ADDR 0x7fffffffe0
[ 8.487664] [ T703] EDAC igen6: v2.5.1https://liliputing.com/aoostar-launches-a-ryzen-7-5825u-vers...
It is? How so? I don't see it anywhere outside their server and embedded products. The server-grade stuff isn't appropriate for "the little NAS boxes" used at home because of both expense and more importantly power consumption, and the embedded stuff just isn't really available to consumers (so it might be potentially great for a company like Synology that builds consumer-friendly pre-built NAS boxes running on proprietary software, but it's not useful to people building their own DIY NAS boxes running open-source software).
Yeah, that cost puts it out of reach for the typical home users building relatively inexpensive little DIY media server boxes, and places it firmly in "server" territory. A standard motherboard for these CPUs (typically using a B760 chipset) is a very small fraction of that cost.
It's good to know this factoid, but it still basically supports my prior assertion that on Intel, ECC support is basically only for servers.
The Gen7 things would never be useful for transcoding on cpu though, waaaaaay too underpowered.
But they did have a PCIe slot for add-in cards (ie small gpu or network card).
They at least used to support ECC on some models of i3 chips as well.
My understanding was that was specifically to support ECC on lower power NAS systems.
Random examples:
• https://ark.intel.com/content/www/us/en/ark/products/90729/i... (6th gen i3)
• https://ark.intel.com/content/www/us/en/ark/products/97455/i... (7th gen i3)
• https://ark.intel.com/content/www/us/en/ark/products/129944/... (8th gen i3)
• https://ark.intel.com/content/www/us/en/ark/products/190886/... (9th gen i3)
• https://ark.intel.com/content/www/us/en/ark/products/203899/... (10th gen i3)
Looking over random i3 pages from 11th gen onwards though, I'm not even seeing ECC mentioned on the pages at all.
It's not a "yes/no" item like on the older generation ones pages, it's completely absent (from the ones I just checked). :(
You can still see it even in 13th generation CPUs: https://ark.intel.com/content/www/us/en/ark/products/232105/...
But as you can see here, this is an embedded variant; you're not going to find it at Amazon, as it's probably only sold directly to manufacturers.
That's not really relevant to the point of them only allowing ECC on Xeon chips though. They do (or at least did) support ECC on non-Xeon chips.
These days though, people are probably better off buying an appropriate Ryzen processor and motherboard that explicitly supports ECC. That's what I did anyway. :)
As I pointed out before, you can't do that for a media server. Transcoding is necessary for many (most?) users.
>That's not really relevant to the point of them only allowing ECC on Xeon chips though. They do (or at least did) support ECC on non-Xeon chips.
That's a distinction without a difference: those other non-Xeon chips aren't useful if you can't even buy them because you're not an OEM.
https://www.ebay.com/itm/305342386279 (note: I don't know the seller)
Seriously, if you can't just buy it at Best Buy/NewEgg/Amazon (not from 3rd-party overseas sellers), then it's not applicable to this discussion at all.
Maybe the problems you were having with sourcing the cpus you wanted have something to do with the arbitrary limitations you were working under?
Meanwhile, other people (as per sibling comment) were able to buy these same chips without issue. ;)
That's not correct. I literally linked to some non-suffixed processors that support ECC in the comment you're replying to.
There are a huge number of models of cheap small NUC-like computers with AMD Phoenix or Hawk Point (Ryzen 8000 series) CPUs.
https://jellyfin.org/docs/general/clients/codec-support/#vid...
That doesn't work if you use subtitles. With many formats, the subtitles have to be transcoded on-the-fly into the video, even if the source and destination resolution and codec are the same.
Also, the Intel NUC might be fine just running Jellyfin (without transcoded subtitles) using separate file storage, but if you try to combine that with a NAS box running 4-8 drives using ZFS and perhaps a few other services as well, it's probably just not enough.
First, the quality of output of hardware accelerated transcoding is in most instances noticeably worse than CPU transcoding, as in most people can discern the difference watching two videos side-by-side.
Second, CPU transcoding is more than enough to keep up with most streams. For instance, 1920x1080 h.264 streams can be done in real time by even a modest 4 core processor. People who want 4K h.265 can buy a fancier CPU.
Third, most people are served perfectly fine by pre-transcoded files. Your comment about subtitles isn't correct - most streaming devices can accept subtitle metadata, and even if subtitles need to be burned in, they can be burned in to a static file and/or generated in real time by a CPU.
What's interesting is that the same people who want Intel Quicksync claim they want to transcode to the best quality that a device can support, then say they don't want to transcode to a static file because they don't want to transcode to a lower resolution / bitrate than what their best device can support, but want to be able to view things at the highest quality wherever they want. They've been tricked, because if they really cared about quality, they'd care about the difference in quality between QuickSync and CPU encoding.
That's why I tell people that if the really want highest quality real time transcoding and have sources that are ultra high quality, they'd be much happier with a Ryzen 7900 than with Intel QuickSync. Side-by-side comparisons would bear this out every time.
Or they can just get an N95
The cpu doesnt generally matter for #1. For #2 you are already making tradeoffs so its a bit of a non-argument that "you are losing quality". Its not the primary usecase (either its other users, or streaming on the go).
I do not know if the IBECC controller is functional in all models, but it is usable at least in the models that are marked by Intel (in Intel Ark) as suitable for embedded use, like N97 and i3-N305.
The IBECC controller requires BIOS support. Among the computers known to have BIOS support for IBECC is ODROID H4/H4+/H4 Ultra (the 3 models differ in the CPU model or the number of Ethernet ports and SATA support).
IBECC works with non-ECC DDR5 or LPDDR5 memories, but it reduces the available memory capacity and performance in comparison with traditional ECC. Because no memory vendor offers LPDDR memory with ECC, IBECC is the only way to implement ECC in the CPUs like Alder Lake N or Amston Lake, which are intended to be used with LPDDR5 memory.