Intel Motherboards : Q1900TM UEFI frustration!

Author: Alexius_777
Subject: Q1900TM UEFI frustration!
Posted: 08 Dec 2016 at 6:41pm

parsec wrote: Given the manual for this board, it seems you are unable to save a UEFI/BIOS profile of the option settings? That option does not exist? A shame you cannot do that. What UEFI/BIOS version are you currently using? 1.20? I'm curious about some of the things you've said occur with the UEFI used with this board.

I haven't here the board, but I can tell you that I few days ago updated UEFI, and now it is updated with same symptoms. Online updating from UEFI is one excellent option, which I can commend.
UEFI profile backup is not necessarily unless you encounter this wierd problems.

parsec wrote: You said any time you do a hardware change, the UEFI default values are applied, over writing the non-default options you have selected. This happens to any and all of the UEFI options? Meaning even options like the fan speed configuration options, if set to a non-default value, will be changed back to the default value?

Yes, to all options, including fan configuration options.

parsec wrote: May I ask which specific UEFI options that you use are being reset to their default values?

As being said all of them :(

parsec wrote: Some ASRock boards have an feature/option called Boot Failure Guard, which I don't see in this board's manual. This option will prevent a failure to POST situation caused by a UEFI option setting. It will set the offending UEFI option value to one that will allow POST to occur, but then displays the UEFI/BIOS screen.

Yes, it has Boot Failure Guard, but, nevertheless when I disable this option, it will overwrite setup cause i.e. changing memory slot. I'm warned that defaults is loaded, my options are to proceed or to go to setup and see how all options are default!

But I hate that "user-friendly" option, because I can clear CMOS any time I want.

parsec wrote: The UEFI erasing the Grub2 bootloader sounds unbelievable to me, but I cannot say that it doesn't, since I have not experienced what you have. You are saying that the Grub2 bootloader, which exists in a partition on a SATA drive, is literally over written, or the file system addresses are deleted? You also said that loading UEFI defaults caused the Grub2 boot loader to be erased? What options cause that? I'm simply trying to understand what is happening. What drive are you using, and how is it formatted?

Kingston SSD - GPT with all partition needed for UEFI job....uefi-FAT, linux-boot-EXT, linux-root-EXT, linux-swap.
With MBR Grub first part of record added to MBR, but with GPT I have no nerves to dig....there's no  point.

parsec wrote: You wrote that the Windows boot loader entry/option is set as the first default in the boot order, in the situation you described. What is that entry in the boot order, the exact text?

Newborn setup is like that:
1. Windows bootloader
2. KINGSTON_blahblahblah...(production code)

...both options ends nowhere, system failed to boot either way.

parsec wrote: A drive can be listed in the boot order, and have no Windows System/boot partition on it, and be completely unable to boot an OS. That normally happens when the CSM option is Enabled.

I left CSM Enabled for compatibility issues...maybe shouldn't. I cried more than once for BIOS return, and I will use CMS and preformat drive in MBR if it would give me the peace.

B U T, the most annoying fork in the eye is the defaults autoloading, I would gladly hack UEFI to eliminate any further sabotage.

Thank you for trying to help.