Q1900TM UEFI frustration!

Now I found what causes few wierd errors...

Battery (CMOS) died and every hardware setup causes loading default, because I pull out adapter jack every time when do some hardware job. I do it on every pc weather or not is switched off  as precaution.

But why almost new CMOS battery died?
Following factory recommandations "The DC-In jack is compatible with the 19V power adapter", I connected power supply and motherboard step-down DC to DC converters (which are poor designed) dissipated huge amount of heat to destroy near placed CMOS battery in short time. That is both buck converters design and MB design layout failure. Pitty, because AsRock makes very good MBs, and the company is very inventive.

I solve it by, ofcourse, replacing battery and new AC adapter of 12V output!!!! This is what NOT should be done, because common buck converters can't handle same input-output voltage. That achieved veeerrrryyyy low dissipated heat, and 12V trail is now at about 9V, but while is not needed for attached SSD, or any other job, it is boilerplate solution.

STILL we have an issue with Grub erasal which is not tolerable :(



Edited by Alexius_777 - 12 Dec 2016 at 3:59pm

OK this has me intrigued.

Alexius_777 wrote: I got my hands at upper mentioned MB - and have such issues that I can't beleive!!! I'm testing some stuff for furter consultation about issues with my partners. My goal was to test Linux distros and compatibility with this board. Every time I changed hardware setup (i.e. changing memory slot) UEFI  erases Grub2 bootloader, and load UEFI defaults which completely erases my setup and [oh, this is special] PUT WINDOWS BOOTLOADING option as 1st default. !!!!!!!!!!! Windows wasn't installed and never ment to be! Why do you sabotage your customers to use any other OS than Windows???? Who give you the rights to erase my UEFI settings without permission? Who give you the rights to erase Grub bootloader from my disk? Who give you the rights to force customers to use the OS which they don't want? Please explain. Thank you, Alex

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.

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?

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

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.

I'm wondering if that is happening in your situation, as if this feature is enabled by default but not user configurable.

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?

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?

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.

Don't worry, we see a lot of people come through here angry, it is the technical support section of the forum after all 

Alexius_777 wrote: wardog wrote: Not for one second do I believe, nor have I seen, the BIOS would resort to that action unless Windows is or was installed on one of the drives you have connected. Are you positive there are no Windows boot files residing in the root of one of your drives? Dear friend, I have 54 years and was administrator since 8086 and M6800 and I am 100% sure that I don't have any of MS OS, just Arch based Antergos Linux distro. However, my son bought Lenovo 17' laptop two months ago and experience similar problems with Win 8.1 and Xubuntu dual boot [just for the record]. # EDIT: I cannot be sure that current SSD wasn't used with Windows, but if it was, and automagically left some records there....how it should erase Grub with FORCED - UNNEEDED uefi defaults loading!?

You took offense to what I posted?

Please Contact ASRock Tech Support and inquire at:
http://event.asrock.com/tsd.asp