On 5/6/21 7:14 PM, Carlos E. R. wrote:
On 07/05/2021 01.15, -pj wrote:
On 5/6/21 5:30 PM, Carlos E. R. wrote:
On 06/05/2021 23.17, -pj wrote:
On 5/6/21 2:53 PM, Carlos E. R. wrote:
On 06/05/2021 20.39, Felix Miata wrote:
-pj composed on 2021-05-06 07:12 (UTC-0500):
12 The Boot Loader GRUB 2
In particular, you may need to use the variable "GRUB_DEFAULT". Pr using YaST, see "12.3.3.1 Boot Loader Options Tab", there is a "default boot section" entry. Thank you for the links above: I really like this "Configuring boot loader with YaST" capability. :|
Then, a trick.
To force YaST bootloader module to write and update all the boot files, just change 1 second up or down the timeout (figure 12.4)
That's a neat trick above. So if I were to only click "OK" which then leads to YaST exiting. I should go to Bootloader Options adjust the timeout then click ok (Just for certain).
Yep :-)
Now the following question is I feel still on topic for the post in a way perhaps I am incorrect on this:
1. What about now being able to enable "Trusted Boot Support"? Since the issue (for this terminal/computer) has in fact been repaired upstream (see here): > https://bugzilla.opensuse.org/show_bug.cgi?id=1185023 < I can verify on my terminal/computer that the (TDE) installation DOES COMPLETE NOW while connected to the mirrors/internet. The only problem of course being kernel 5.12.0-2-pae will fail to load once being selected at bootmenu. That is why I installed (TDE) offline with a kernel 5.11.series .iso then was able to use " zypper install https://download.opensuse.org/repositories/home:/tiwai:/kernel:/5.11/standar..." to draw in the most current (kernel 5.11.16-1.ge06d321-default) and use
YaST to lock the package.
I know nothing about Trusted Boot Support, sorry. It scares me a bit, though.
I assume it is not the same thing as signed boot files and kernels used by EFI. But your machine being 32 bits, it can not have EFI. You are correct I believe. The machine has legacy boot option with no UEFI capability nor does it have secure boot capability.
2. So I believe I can use the YaST bootloader module to enable "Trusted
Boot Support" at this point. Then change timeout - tick OK....Powercycle....Without issues?
3. Would this be a fairly safe assumption?
I don't know, and it is not something I want to test on real hardware. Maybe on a virtual machine.
That's a good point. Setup a Container with Virtualbox. hmm Thanks for all the advice on this matter.