Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Announcements and updates #1

Open
nakato opened this issue Jan 17, 2024 · 3 comments
Open

Announcements and updates #1

nakato opened this issue Jan 17, 2024 · 3 comments

Comments

@nakato
Copy link
Owner

nakato commented Jan 17, 2024

Subscribe to this issue to get notifications about releases, breaking changes, or any other noteworthy comments.

Repository owner locked and limited conversation to collaborators Jan 17, 2024
@nakato nakato pinned this issue Jan 17, 2024
@nakato
Copy link
Owner Author

nakato commented Jan 25, 2024

sbc.version == 0.2

sbc.version 0.2 has been added to the flake.
This switches the defaults to using BTRFS with sub-volumes for the disk format, which is the target state for the repository.
First boot may take a bit more time as files are moved in a CoW friendly way into the subvols on first boot,

BTRFS compression is enabled, if space is important run a defragment manually to compress files created during image creation. Reduction when I tested it was ~600MB on the bootstrap image.

@nakato
Copy link
Owner Author

nakato commented Jul 5, 2024

There is a bug in u-boot with BTRFS that can result in boot getting caught in a boot-loop. To prevent this or get out of this situation, build the latest uboot for your board and write it to the appropriate partition.

If you use ext4 for boot, then this can be ignored.

See the boards sd-image file for details on individual board boot-loader layouts.
BPiR3 example:

nix build '.#ubootBananaPiR3'
dd if=result/bl2.img of=/dev/xxx1
dd if=result/fip.bin of=/dev/xxx4

Updated uboot's have only been tested on the BPiR3.

@nakato
Copy link
Owner Author

nakato commented Sep 2, 2024

sbc.version == 0.3

sbc.version 0.3 has been added to support the enabling of the binaryCache.

As this is new, 0.3 has been created as to not surprise anyone by opting them in where it previously did not exist.

If you are migrating from 0.2 and wish to keep the binaryCache disabled, set the following options before setting sbc.version to "0.3".

config.sbc.binaryCache.enable = false;

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant