Skip to content
Small team, full backlog, zero orders dropped. Support replies are slower than we’d like. Read our status update → Zero orders dropped. Status → 📬 Check your spam folder — most of our replies land there. We do answer. Status update → 📬 Check your spam folder. Status →
Uncategorized

DCENT_OS 0.9.0 Experimental Downloads: 19 Exact-Board Artifact Sets

· D-Central · ⏱ 5 min read

DCENT_OS 0.9.0 — beta20261002 now provides 20 exact-board Experimental artifact sets across 19 model names on the beta channel: 17 native raw SD images, two route-restricted archives and one BeagleBone AM335x SD-payload archive. These development-key downloads are not a production-stable release; physical qualification is pending.

Development signing key: select it explicitly

This Experimental distribution uses an explicitly approved development key. Its raw Ed25519 public key is 131d0f0830b9a4118fe2bfb0670babef628a9611aa186d05db081ce0d1599bec; the SHA-256 fingerprint of those raw key bytes is 372a5c3e8a85110ef322b1bccf79187bfe801cea890c89bdc35ad6b35abb2fbc. The July public beta key and default installer trust pins remain unchanged. Verify this release using the separately published development public key, not a key selected implicitly from the package.

The new release record provides the exact public-key file checksum, original artifact names, bytes, SHA-256 receipts, signatures, current source availability and coverage and read-only verification instructions. All 20 sets passed the supported full producer verifier under this explicitly selected development key before publication.

Clean matching DCENT_OS project source is now published with 4,614 exact source-file receipts. Dependency and third-party boot coverage is partial or unverified; this is not a complete firmware corresponding-source or GPL-compliance claim.

Choose the exact model and controller

The two archives target S9 Xilinx (am1-s9) and S19j Pro Xilinx (am2-s19j, build/package filename target am2-s19jpro). The S9 archive declares first-install-only package permission and advertises no self-update command; a runnable source-firmware route must be confirmed separately. The S19j Pro archive is limited to its guarded existing-DCENT_OS target-update route, including its inactive-slot and verified-restore prerequisites. The running firmware must already accept this development signing authority; selecting the key for host verification does not change miner trust. This publication does not authorize changing miner runtime trust settings. Neither archive is a raw SD image or an authorization for another controller.

The native SD sets target S9i, S9j, S9 SE, S9k, S15, T15, S17 (am2-s17p only; no S17 Pro inference), S17+, T17, T17+, T17e, S17e, S19 Pro, S19, T19, S19a and S19+. Preserve each supplied image’s original filename and all adjacent signed media/runtime sidecars. These sets authorize external-media boot preparation, not NAND installation.

Start with controller identification, then follow the exact board’s download and recovery card. Never rename an image to a sibling model or treat the standardized release label as the signed original filename.

S19j Pro BeagleBone: a separate developer payload

No supported consumer installation path is provided here. The required lab-approved external boot assets and exact media-preparation route are not supplied as a verified public consumer boot set. A developer download is not a bootable-card claim.

The am3-bb-s19jpro Experimental package is an SD-payload tar, not a complete raw SD image, Xilinx existing-runtime update, stock-web update or NAND installer. It requires separately verified AM335x MLO, u-boot.img, uImage and a carrier-aware DTB, with exact media preparation. Keep original firmware and media if those prerequisites cannot be met. See the separate BeagleBone controller guide.

The sixth cleaned source bundle adds 13 upstream source archives and 15 exact license-record files for this member. Its retained legal inventory has 199 of 279 records supplied, 79 unmatched and one restricted compiler input withheld. This separate inventory does not replace the original 17-set or T17e/S17e inventories, and does not establish complete source, reproducibility or third-party redistribution permission. Missing external boot assets remain distinct prerequisites.

Verification and hardware qualification are separate

Checksums verify file bytes; signatures authenticate those bytes under the explicitly selected development key. Host verification does not prove cold boot, accepted pool shares, endurance, safe power lifecycle or recovery on this exact artifact. Physical qualification remains pending. Keep full unit backups and controller-specific recovery preparation where a route requires persistent writes.

The October 3, 19:14 UTC build snapshot recorded 17 completed outputs and 12 pending targets. The initial publication covered 17 individually verified sets; T17e was subsequently added after full verification and settlement. It does not claim that all 29 targets have finished. Pending targets in that snapshot were T17e, S17e, BeagleBone S19j Pro and nine Amlogic lanes: S19j Pro Classic, S19j Pro A126, S19j Pro+, S19j XP, S19k Pro, S19 XP, S21, S21 Pro and S21 XP. Apart from the subsequently verified T17e and S17e sets and the BeagleBone developer SD payload, their files are not added by this publication.

The immutable July release record retains its original dates, hashes, signature scope and route limitations. The new Experimental release is documented separately so development-key packages cannot inherit the July trust or installation contract. Release index · Documentation · Installation boundaries

Source withdrawal and redistribution limits

Matching DCENT_OS project source is provided with partial dependency coverage. Third-party boot/kernel source correspondence and finished-image redistribution permission are unverified. Development signing-key approval does not establish redistribution permission or license clearance. One restricted compiler payload was withdrawn and is excluded from the replacement source bundle. No complete firmware corresponding-source, GPL-compliance or reproducibility claim is made. Fifteen unrelated raw vendor fixture files are excluded from the clean project-source replacement.

Current public source coverage and withdrawal status

T17e addition: The exact am2-t17e native SD set is now public after full producer/media/runtime verification and a stable settlement check. Its distinct stock OM boot/kernel/fabric group has source correspondence and redistribution permission unverified, with 185 of 257 target-specific legal records matched, 71 unmatched and one restricted input withheld. Physical qualification remains pending.

S17e addition: The exact am2-s17e Xilinx native SD set is public after full producer/media/runtime verification and a stable settlement check. Preserve dcentos-sd.img and all supplied companions. Its source legal inventory is separately 185 of 257 matched, 71 unmatched and one restricted input withheld; third-party boot/kernel/fabric source correspondence and redistribution permission remain unverified. External SD boot requires the card to remain inserted and does not authorize NAND writes. Mining defaults off; physical qualification remains pending.

D-Central

Bitcoin Mining Experts Since 2016

ASIC Repair Bitaxe Pioneer Open-Source Mining Space Heaters Home Mining

D-Central Technologies is a Canadian Bitcoin mining company making institutional-grade mining technology accessible to home miners. Thousands of miners repaired, 490+ products shipped from Canada.

About D-Central →

Related Posts

Start Mining Smarter

Whether you are heating your home with sats, building a Bitaxe, or scaling up — D-Central has the hardware, repairs, and expertise you need.

Browse Products Talk to a Mining Expert