I have no idea what to do. So… the short story is…
SSD [1TB] is fully formated by the QubeOS installer with disk encryption enabled and LUX2 option enabled also.
Before this process the running of the UEFI BIOS was normal
“Del > BIOS”; or from “boot menu [F11] > Enter Setup > BIOS”, also worked in the past with the Arch Linux who have booted up from manually created UEFI BOOT MENU > Enter Setup > BIOS
I decided to change my main distro, and install QubeOS, on the fully formated SSD.
QubeOS installer created new LUX2 encrypted partitions with, of course, necessary UEFI boot partition, and /home, and /data partitions wich was also LUX…
… this is the point when my headache begun … the UEFI BIOS wan’t run (Delete button, boot menu [F11], and from QubeOS menu either i can’t access BIOS)
Whichever option I choose to enter the bios, it happens that only the black screen appears, while in the upper left corner the “white cursor-line” blinks once, the monitor does not turn off, and the black screen does not disappear
… After this I’ve reinstalled QubeOS, but this time I’ve formatted the partitions with ext4 partitions and no encryption. The installation was successful, but the problem is still the same.
… I’ve tried Debian and reformatted the entire SSD and created new partitions without encryption again. That didn’t work either.
… The last thing I did was installing another distro, which I “asked to automatically create partitions for me”. (I’m not planing to change the distro again, of course, just in the case that I must to do it in the name of: “fixing this problem with the BIOS”).
New distro has its own boot menu also, which can be launched:
“EXCLUSIVELY AFTER PRESSING THE F11 KEY (boot menu) > UEFI OS (SATA1: CT1000BX500SSD1)”,
… If NOT, THEN that “mystical black screen” appears again (see the attached picture of the F11 boot menu below, that’s where the “last piece of the mystic puzzle” is hidden…
The 1st option on the picture is going streight in the same black screen problem. The last option, also is going to black screen problem. Both option is trying to start BIOS (that is my opinion). Is there some elegant solution for solving this headache?
The motherboard is "MS-7D14" with "12 × AMD Ryzen 5 3600 6-Core Processor" and "NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2".
I don’t think it’s related to Qubes OS but rather to your motherboard BIOS.
Try to access the BIOS by pressing F2 instead of Del.
Try to update your BIOS if it’s possible without accessing the BIOS menu, if it’s supported by your BIOS.
Try asking this question on your motherboard manufacturer forum.
Thank You for your advice "apparatus*". I will write to MS. My opinion is that You told right, and this all is not about QubeOS.*
My opinion is that the problem is somewhere between “luxcrypt” and “hardware firmware from uefi bios”. I have a pretty good understanding of how it works, but not so well that I understand the “key connection” between these two entities. However, the fact is that the creation of lux2 encryption did something that the firmware did not like. It is possible that the error exists in the LUXCRYPT code or in the MS UEFI BIOS firmware code. At the end, the question remains: “who is weaker, and who will admit a mistake, and do something to solve the problem”.
If this forum is interested in being informed about further developments in this case, I would be happy to share.
LUKS disk encryption is not touching anything in the firmware so it shouldn’t be related at all.
You can physically disconnect your disk and boot without it for a test.
That’s exactly right, Lux is not “the devil”.
…Now I also understood what the problem was.
…By the way, disconnecting the SSD didn’t help. I’ve also disconnected the other peripherals (DVD-ROM, USB).
I forgot to mention that a few years ago I had windows and one data partition on which “BITLOCKER” was activated.
…After installing Arch Linux, I left that Windows partition with bitlocker intact. I used it without any problems.
…The BIOS problem begins to occur after formatting the entire SSD.
So, let’s get to the point. I was very happy to find that the motherboard also has a BIOS flash option that is not dependent on the BIOS and can be accessed via the CTRL+F5 key. More importantly, I didn’t see the black background after that. On the next picture You can see the “Warning from the FLASH UTILITY itself!”. I need to say, that at this point no disks and drives was attached on PC. BitLocker is a “LITTLE FIRMWARE WORM”.
I’ve installed the latest version of the firmware and now the boot menu is so beautiful to see - with just 2 options: UEFI OS (SATA SSD) and 2nd option for going to BIOS Firmware.
My opinion is the next: no matter what formatting method I did, the same thing would have happened. I’m still amazed at how deep that “BitLocker” is able to go. But it also has a big security hole, because when formatting, if you wipe all partitions except the one with BitLocker, BitLocker’s encryption is lost and you have access to all data, without entering the password for decryption. That was tested with LIVE Deb Disk (I accidentally discovered it).
Cheers and thank you very much for your assistance and help.
