ASRock Forums : Q1900TM UEFI frustration!

ASRock Forums : Q1900TM UEFI frustration! https://forum.asrock.com/ Copyright (c) 2006-2013 Web Wiz Forums - All Rights Reserved. Mon, 22 Jun 2026 14:54:00 +0000 Mon, 12 Dec 2016 15:54:15 +0000 http://blogs.law.harvard.edu/tech/rss Web Wiz Forums 12.04 360 https://forum.asrock.com/RSS_post_feed.asp?TID=3969 <![CDATA[ASRock Forums]]> https://forum.asrock.com/forum_images/web_wiz_forums_black.png https://forum.asrock.com/ <![CDATA[Q1900TM UEFI frustration! : Now I found what causes few wierd...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20543&title=q1900tm-uefi-frustration#20543 Author: Alexius_777
Subject: 3969
Posted: 12 Dec 2016 at 3:54pm

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]]> Mon, 12 Dec 2016 15:54:15 +0000 https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20543&title=q1900tm-uefi-frustration#20543 <![CDATA[Q1900TM UEFI frustration! : Xaltar wrote:OK this has me...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20336&title=q1900tm-uefi-frustration#20336 Author: Alexius_777
Subject: 3969
Posted: 09 Dec 2016 at 1:04am

Xaltar wrote:

OK this has me intrigued.

I only have one thought on the matter:

What RAM are you using?

Based on your description I get the feeling it may not be properly supported by the board and could be what keeps flagging Boot Failure Guard. If the RAM is higher than default DDR3 voltage, 1.65v vs 1.5v or 1.3v (low votlage) it could be triggering BFG. If you have not already I would try some standard DDR3 1333 or 1600 in there and see if it still causes the error. Even if the voltage is 1.3v or 1.5v the module might not be fully supported.

Just my 2c on the issue, please feel free to ignore if you have already tried multiple RAM brands and models.

Kingston KVR16LS11/4 as recommended http://www.asrock.com/mb/Intel/Q1900TM-ITX/?cat=Memory but only one slot - so it is single channel 4GB.

But dunno is it worth of hassle, I should stick with Gigabyte, the only manufacturer which never, ever disapointed me.
]]> Fri, 09 Dec 2016 01:04:17 +0000 https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20336&title=q1900tm-uefi-frustration#20336 <![CDATA[Q1900TM UEFI frustration! : OK this has me intrigued.I only...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20328&title=q1900tm-uefi-frustration#20328 Author: Xaltar
Subject: 3969
Posted: 08 Dec 2016 at 7:19pm

OK this has me intrigued.

I only have one thought on the matter:

What RAM are you using?

Just my 2c on the issue, please feel free to ignore if you have already tried multiple RAM brands and models.

]]> Thu, 08 Dec 2016 19:19:28 +0000 https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20328&title=q1900tm-uefi-frustration#20328 <![CDATA[Q1900TM UEFI frustration! : parsec wrote:Given the manual...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20326&title=q1900tm-uefi-frustration#20326 Author: Alexius_777
Subject: 3969
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.

]]> Thu, 08 Dec 2016 18:41:39 +0000 https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20326&title=q1900tm-uefi-frustration#20326 <![CDATA[Q1900TM UEFI frustration! : Alexius_777 wrote:I got my...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20291&title=q1900tm-uefi-frustration#20291 Author: parsec
Subject: 3969
Posted: 08 Dec 2016 at 9:20am

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. !!!!!!!!!!! Angry

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.
]]> Thu, 08 Dec 2016 09:20:38 +0000 https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20291&title=q1900tm-uefi-frustration#20291 <![CDATA[Q1900TM UEFI frustration! : Alexius_777 wrote:@wardog,...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20281&title=q1900tm-uefi-frustration#20281 Author: wardog
Subject: 3969
Posted: 08 Dec 2016 at 12:51am

Alexius_777 wrote:

@wardog, sorry. I wasted lot of time in vain and I'm annoyed, shouldn't have to annoy the others. Excuse me, please. Confused

No problems Alexius.
]]> Thu, 08 Dec 2016 00:51:08 +0000 https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20281&title=q1900tm-uefi-frustration#20281 <![CDATA[Q1900TM UEFI frustration! : Don't worry, we see a lot...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20272&title=q1900tm-uefi-frustration#20272 Author: Xaltar
Subject: 3969
Posted: 07 Dec 2016 at 10:34pm

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

Wardog referred you to Tech Support because there is nothing we moderators or other forum members can really do to help you here, the issue you mentioned in your first post has to do with the UEFI which we can't correct for you as we do not work for ASRock and thus cannot provide altered UEFI updates. Tech support should be able to help you out with whatever you are trying to do.

I must note however that ASRock (or any other manufacturer for that matter) does not officially support linux. This is not because they want you to use windows but because of the sheer number of distros out there and the lack of a unified driver and support system. It is all but impossible to support an OS that has so many variants. Proper support requires collaboration between the OS vendor and the manufacturer which will likely never happen with linux given it's open source nature.

]]> Wed, 07 Dec 2016 22:34:57 +0000 https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20272&title=q1900tm-uefi-frustration#20272 <![CDATA[Q1900TM UEFI frustration! : @wardog, sorry. I wasted lot of...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20267&title=q1900tm-uefi-frustration#20267 Author: Alexius_777
Subject: 3969
Posted: 07 Dec 2016 at 10:14pm

@wardog, sorry. I wasted lot of time in vain and I'm annoyed, shouldn't have to annoy the others. Excuse me, please. Confused

]]> Wed, 07 Dec 2016 22:14:33 +0000 https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20267&title=q1900tm-uefi-frustration#20267 <![CDATA[Q1900TM UEFI frustration! : Alexius_777 wrote: wardog...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20264&title=q1900tm-uefi-frustration#20264 Author: wardog
Subject: 3969
Posted: 07 Dec 2016 at 9:31pm

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? Disapprove

Please Contact ASRock Tech Support and inquire at:
http://event.asrock.com/tsd.asp
]]> Wed, 07 Dec 2016 21:31:46 +0000 https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20264&title=q1900tm-uefi-frustration#20264 <![CDATA[Q1900TM UEFI frustration! : wardog wrote:Not for one second...]]> https://forum.asrock.com/forum_posts.asp?TID=3969&PID=20263&title=q1900tm-uefi-frustration#20263 Author: Alexius_777
Subject: 3969
Posted: 07 Dec 2016 at 9:14pm