Hi Esad,
On 26.04.22 10:22, esad ergül wrote:
> Hi all,
>
> I build an efi based image with Elbe tool and use dual copy(A/B)
> approach to always have a running system on the device. The hard disk
> image (Buster) has 3 partitions (efi,root1,config). The other 2
> partitions(root2,data) are created during the first init procedure. As
> updater client I want to use the SWUpdate (from the official Debian
> repository). For updating I created swu image file as described in the
> documentation
> (
https://sbabic.github.io/swupdate/sw-description.html#software-collections-and-operation-modes).
> When I update the device, SWupdate says that the installation is
> successful and does not give an error message. But switching between
> root partitions does not happen because SWupdate somehow did not create
> the environment variables on the grub environment block. That's why the
> grub bootloader can't read a variable from the environment block and
> change the default menu entry in the grub configuration file. What I
> noticed is that the file structure of the Efi partition is different
> from standard Debian. The Efi partition that the Elbe created has only
> BOOTX64.EFI (boot/efi/EFI/BOOT/BOOTX64.efi) file.
BOOTX64.efi is the UEFI bootloader - it is ok. Anyway, you need to add
your *own* grub.cfg, else grub does not know what to do.
You should see :
√ ~ # ls /boot/EFI/BOOT
bootx64.efi grub.cfg grubenv
Not required to create grubenv - if not provided, SWUpdate will raises a
warning, but then it will create the file.
If you do not see it, there is something wrong in your configuration or
ELBE setup. Please note that SWUpdate has a configuration file and this
activateswhich bootloader is selected. If the Debian package has not
activated GRUB support, of course it cannot work.
> Standard Debian has here grubx64.efi and grub.cfg file which contains
> the partition UUID where the actual grub.cfg file with the menu entries
> is located.
>
> My questions are;
> 1)Why SWupdate does not write the variables on the grub environment block ?
You have something wrong in SWUpdate configuration or Elbe setup.
> 2)Is it possible that the path of the environment block file
> (/boot/grub/grubenv) is wrong ?
/boot/efi/EFI/BOOT/grub/grubenv is the default path, and you can change
it by reconfiguring SWUpdate.
> --
> You received this message because you are subscribed to the Google
> Groups "swupdate" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
swupdate+u...@googlegroups.com
> <mailto:
swupdate+u...@googlegroups.com>.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/swupdate/7488d166-48ae-45fc-982d-ac1e3ac69fffn%40googlegroups.com
> <
https://groups.google.com/d/msgid/swupdate/7488d166-48ae-45fc-982d-ac1e3ac69fffn%40googlegroups.com?utm_medium=email&utm_source=footer>.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone:
+49-8142-66989-53 Fax:
+49-8142-66989-80 Email:
sba...@denx.de
=====================================================================