▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
   ██ ████▄ ▄██ ▄▄▀██ ▄▄▀██ ▄▄▄██ ▄▄▀██ ▄▄▄ ██ ▄▄▄ █▄▄ ▄▄█
   ██ █████ ███ ▄▄▀██ ▀▀▄██ ▄▄▄██ ▄▄▀██ ███ ██ ███ ███ ███
   ██ ▀▀ █▀ ▀██ ▀▀ ██ ██ ██ ▀▀▀██ ▀▀ ██ ▀▀▀ ██ ▀▀▀ ███ ███
   ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀

Hello . Please tell me a program that can draw such drawings, I want to draw the Hyperbola logo and inscription and paste it into GRUB

and

https://git.hyperbola.info:50100/~team/ … /wallpaper

https://git.hyperbola.info:50100/~team/ … /finalized

We find the desired picture that you like in jpg or png format, I tried to find a beautiful picture of Hyperbola but found nothing ((
Don't forget to rename your photo from test.png to background.png

Using the cbfstool utility, remove the Libreboot theme with the command:

root@test# ./cbfstool grub_t440pmrc_12mb_libgfxinit_corebootfb_usqwerty.rom  remove -n background.png

we have already renamed our new theme, now let's add it to our rom

root@test# ./cbfstool grub_t440pmrc_12mb_libgfxinit_corebootfb_usqwerty.rom add -n background.png -f background.png -t raw

great, now we need to flash our rom with a new theme using the iomem=relaxed kernel parameter

root@test# flashrom -p internal 

if there are no errors, enter:

root@test# flashrom -p internal -w grub_t440pmrc_12mb_libgfxinit_corebootfb_usqwerty.rom

...and wait for the message “Verifying flash... VERIFIED.”.

reboot your computer and you will be greeted with a new theme)

Another useful feature can be kernel and initramfs signing.

I don't know how often the kernel is updated and whether there will be any consequences, but for the sake of testing, let's do it https://libreboot.org/docs/linux/grub_h … l#gpg-keys

It is unclear where libreboot_grub.cfg came from in this instruction, there is no explanation...

Create a directory where you will store the keys:

gpg --gen-key generates a public/private key pair. The private key is used to sign GRUB configuration files and Libreboot binaries. The public key will be built into GRUB and will be used to validate GRUB configuration files or binaries that GRUB attempts to load.

login: root
password: *****

root@test# mkdir --mode 0700 keys

root@test# gpg --homedir keys  --gen-key

backup secret key

root@test# gpg --homedir keys --export-secret-keys --armor > boot.secret.key

export the public key

root@test# gpg --homedir keys --export > boot.key

Now that we have a key, we can sign:

root@test# gpg --homedir keys --detach-sign /boot/vmlinuz-linux-libre-lts

root@test# gpg --homedir keys --detach-sign /boot/initramfs-linux-libre-lts.img

root@test# gpg --homedir keys --detach-sign grubtest.cfg

Let's check

  root@test#  tree  /boot 

   ├── config-linux-libre-lts 
   ├── grubtest.cfg
   ├── grubtest.cfg.sig
   ├── initramfs-linux-libre-lts-fallback.img
   ├── initramfs-linux-libre-lts.img
   ├── initramfs-linux-libre-lts.img.sig
   ├── vmlinuz-linux-libre-lts
   └── vmlinuz-linux-libre-lts.sig

We need to trust the key and enable signature enforcement (put this before menuentries)
The environment variable check_signatures=enforce tells GRUB to enable digital signatures

trust (cbfsdisk)/boot.key
set check_signatures=enforce

This is what the configuration file grubtest.cfg looks like:

.......
  echo #Insert newline
}


set superusers="root"
password_pbkdf2 root grub.pbkdf2.sha512.10000.RWE3274682SHFJSDF34820349023LJFSD08082049284.....


menuentry 'Load Hyperbola GNU/Linux-Libre (LTS)' {

trust (cbfsdisk)/boot.key
set check_signatures=enforce

insmod ahci
insmod part_msdos
insmod lvm
insmod cryptodisk
cryptomount -a
set root='lvm/matrix-rootvol'
linux /boot/vmlinuz-linux-libre root=/dev/matrix/rootvol cryptdevice=/dev/sda1:lvm
initrd /boot/initramfs-linux-libre.img
}


menuentry 'Search ISOLINUX menu (AHCI) [a]' --hotkey='a' {
......

Now let's put grubtest.cfg and boot.key into our flash memory using the cbfstool utility

root@test#  ./cbfstool grub_t440pmrc_12mb_libgfxinit_corebootfb_usqwerty.rom add -n boot.key -f boot.key -t raw

root@test# ./cbfstool grub_t440pmrc_12mb_libgfxinit_corebootfb_usqwerty.rom  add -n grubtest.cfg -f my.grubtest.cfg -t raw

root@test# ./cbfstool grub_t440pmrc_12mb_libgfxinit_corebootfb_usqwerty.rom  add -n grubtest.cfg.sig -f my.grubtest.cfg.sig -t raw

If you forgot to put boot.key in grubtest.cfg after entering your grub password, you will get this error:

error: file 'boot.key' not found.

Even if you enter the password for the encrypted partition, you will also receive the error:

error: public key 1h2y3p4e5r678 not found

If something went wrong, restart your computer and after turning it on, press “c”, enter the system and change

After we have placed all the files in flash memory, we need to boot our computer with the kernel parameter iomem=relaxed

next:

root@test# flashrom -p internal 

if there are no errors, enter:

root@test# flashrom -p internal -w grub_t440pmrc_12mb_libgfxinit_corebootfb_usqwerty.rom

...and wait for the message “Verifying flash... VERIFIED.”.

*Load test configuration (grubtest.cfg) inside of CBFS(t)

If everything went well, do the same trick by changing grubtest.cfg to grub.cfg

Nice words)) written by Tthrogh : I love to help because Hyperbola has such a nice, little community with outstanding people helping each other. smile Let's learn together so you can create a nice, minimalistic installation at all - that's also a major goal as I even see bloated packages back in the BSD-world and the idea behind HyperbolaBSD is even more great under this perspective.

This I appreciate most of the time. There are a few times here and there where its annoying, but more than not, its what I want as well.

many of the linux frameworks are just over-engineered wastes of space. But Hyperbola, kicked all of them out of their projects hence my love for it.

1. https://git.sr.ht/~heckyel/hyperfi/blob/master/hyperfi 
2. https://www.zerocat.org/projects/zeroca … perbola.sh