Releases: milas/rock5-talos
v1.4.6
Installer Image
docker.io/milas/rock5-talos:v1.4.6-rock-5b@sha256:b6ca9e8d6c930660020f8577ed5dcf74019bd6c8e76fc0feeeff32551958f0ce
Rock 5 Specific Upgrade Nodes
- Added kernel options for iSCSI support (#9)
- Experimental Rock 5A support
- NOTE: I do not yet have a Rock 5A so this is untested!
Known Issues
- No way to customize kernel args (#3)
Full Changelog
Since last release for Rock 5: v1.4.5..v1.4.6
Compared to upstream: siderolabs/talos@v1.4.6...milas:rock5-talos:v1.4.6
v1.4.5
Installer Image
docker.io/milas/rock5-talos:v1.4.5-rock-5b@sha256:4b997113886b353c7f408a9e9e9d564cab33285f46253f22f8ca5825014426ca
Rock 5 Specific Upgrade Nodes
- None! It should be a smooth upgrade from v1.4.4 (or v1.3.x)
Known Issues
- No way to customize kernel args (#3)
Full Changelog
Since last release for Rock 5: v1.4.4..v1.4.5
Compared to upstream: siderolabs/talos@v1.4.5...milas:rock5-talos:v1.4.5
v1.4.4
Installer Image
docker.io/milas/rock5-talos:v1.4.4-rock-5b@sha256:17837fd3a86047b80b3f69661eaed9c1ef234f6d2f54b2f91364628ce1ed561c
Rock 5 Specific Upgrade Nodes
- None! It should be a smooth upgrade from v1.3.x
Known Issues
- No way to customize kernel args (#3)
Full Changelog
Since last release for Rock 5: v1.3.7..v1.4.4
Compared to upstream: siderolabs/talos@v1.4.4...milas:rock5-talos:v1.4.4
v1.3.7
Installer Image
docker.io/milas/rock5-talos:v1.3.7-rock-5b@sha256:d05230a196772b0cb6a556b940325710d33c63c0e19493fdf0709f11b293d652
Rock 5 Specific Upgrade Nodes
- Trying yet another tagging/naming strategy 😅
Known Issues
- No way to customize kernel args (#3)
Full Changelog
Since last release for Rock 5: v1.3.5-rock5..v1.3.7
Compared to upstream: siderolabs/talos@v1.3.7...milas:rock5-talos:v1.3.7
v1.3.5-rock5
Installer Image
docker.io/milas/rock5-talos:v1.3.5-rock5-rock-5b@sha256:05e95a87073034fc73bde233a7564d56b1f8522f763ed0d800bf5d364b986135
Rock 5 Specific Upgrade Nodes
- Docker image name changed to
rock5-talos
- Docker tag now includes board (will fix the redundancy here in the next version)
- Added
rbd
kernel driver (#6)
Known Issues
- No way to customize kernel args (#3)
🚨 Upgrade Notes
Radxa switched /dev/mmcblk0
and /dev/mmcblk1
in radxa/kernel@ad338f4b after having previously swapped them in radxa/kernel@ad338f4b! 🥲
Version | eMMC | SD Card |
---|---|---|
v1.3.1 | /dev/mmcblk0 |
/dev/mmcblk1 |
v1.3.2 - v1.3.3 | /dev/mmcblk1 |
/dev/mmcblk0 |
v.1.3.4+ | /dev/mmcblk0 |
/dev/mmcblk1 |
This means it's not really straightforward to upgrade from between some of these versions, as once applied, it'll fail the next boot as it's unable to find the install.disk
.
The most practical option is to wipe your device and flash it from scratch, losing any state/data in the process. The flip was an interim mistake for a period on the Radxa kernel branch, but what is there now as of the v1.3.4 Rock 5 release matches mainline kernel behavior so should hopefully not change again
Full Changelog
Since last release for Rock 5: v1.3.4-rock5b..v1.3.5-rock5
Compared to upstream: v1.3.5...v1.3.5-rock5
v1.3.4-rock5b
Installer Image
docker.io/milas/rock5b-talos:v1.3.4-rock5b@sha256:383d74914b0fc6709a313fb2bfc9741ee7d1ba18e871d418af3098fff2b8950e
Known Issues
- No way to customize kernel args (#3)
🚨 Upgrade Notes
Radxa switched /dev/mmcblk0
and /dev/mmcblk1
in radxa/kernel@ad338f4b after having previously swapped them in radxa/kernel@ad338f4b! 🥲
Version | eMMC | SD Card |
---|---|---|
v1.3.1 | /dev/mmcblk0 |
/dev/mmcblk1 |
v1.3.2 - v1.3.3 | /dev/mmcblk1 |
/dev/mmcblk0 |
v.1.3.4+ | /dev/mmcblk0 |
/dev/mmcblk1 |
This means it's not really straightforward to upgrade from between some of these versions, as once applied, it'll fail the next boot as it's unable to find the install.disk
.
The most practical option is to wipe your device and flash it from scratch, losing any state/data in the process. The flip was an interim mistake for a period on the Radxa kernel branch, but what is there now as of v1.3.4-rock5b
matches mainline kernel behavior so should hopefully not change again
Full Changelog
v1.3.3-rock5b
Installer Image
docker.io/milas/rock5b-talos:v1.3.3-rock5b@sha256:745ca63c1e716510eb003694b7ac8fc4878a186e9cba911a8cdaf9b9ff78998a
Known Issues
- No way to customize kernel args (#3)
Full Changelog
v1.3.2-rock5b
Installer Image
docker.io/milas/rock5b-talos:v1.3.2-rock5b@sha256:78ba37a2c0f1556e769bff20db7d94cba6f256092ff48e5b16e68e5cf5f16669
Known Issues
- No way to customize kernel args (#3)
🚨 Upgrade Notes
Radxa switched /dev/mmcblk0
and /dev/mmcblk1
in radxa/kernel@ad338f4b!
This means it's not really straightforward to upgrade from v1.3.1-rock5b
, as once applied, it'll fail the next boot as it's unable to find the install.disk
.
The most practical option is to wipe your device and flash it from scratch, losing any state/data in the process.
Full Changelog
v1.3.1-rock5b
Installer Image
docker.io/milas/rock5b-talos:v1.3.1-rock5b@sha256:88edf6e94154bb09d6f8fecf984525f19704ddf9b9f1ad4ab74ebc2df2d7cb9d
Known Issues
- No way to customize kernel args
Upgrade Notes
- Use
--preserve
(see #5)
Differences from Upstream Talos
- Uses Dockerized toolchain for Radxa BSP kernel @ milas/rock5b-docker-build
- HACK: Refactor partition offset logic to align with Rockchip docs
- HACK: Remove BIOS/EFI partitions entirely
- HACK: Change Talos root partition to ext4 from xfs (vendor U-Boot does not support XFS)
- HACK: Add
rk3588-rock-5b.dtb
(&rk3588-uart7-m2.dtbo
) directly to Talos root partition (these would normally be in the EFI partition) - HACK: Add (hardcoded)
/extlinux/extlinux.conf
directly to Talos root partition - HACK: Remove
proc.sys.kernel.yama.ptrace_scope
from KSPP list - HACK: Disable IMA policy
- HACK: Add new step to
systemRequirements
phase to forcibly load ther8125
ethernet driver - HACK: Increase minimum installer size to account for the BSP kernel being ~1GB
- HACK: Disable
SystemInfoController
(no SMBIOS support)