ASRockRack E3C246D4U BIOS L2.32

"Advanced" -> "Chipset...." -> "IGFX" = "Enabled"

https://1drv.ms/u/s!Ai85RsJjyec28DOAHvhhRJ2BYsEw

 

Edited September 23, 20205 yr by int2e

ooh so now they've added this on the official firmware? At last!!

 

@int2e

Where did you get this firmware from it doesn't show for me on their website.

Did this reset any of your existing settings?

 

 

Edited September 23, 20205 yr by parisv

1 hour ago, int2e said:

ASRockRack E3C246D4U BIOS L2.32

"Advanced" -> "Chipset...." -> "IGFX" = "Enabled"

https://1drv.ms/u/s!Ai85RsJjyec28DOAHvhhRJ2BYsEw

 

Thanks for sharing the link to this bios, int2e! I take it you received this directly from William? Any idea what has been fixed/changed?

@int2e  Your screenshot of BIOS also shows a BMC version that is not publicly available (1.72.00).  Is that needed in conjunction with the 2.32 BIOS to support some changes?  1.80 BMC and 2.30 BIOS are still the versions publicly available on the ASRock website.

4 hours ago, parisv said:

 

 

2 hours ago, kaiguy said:

 

 

2 hours ago, Hoopster said:

 

 

I got her from the official technical support mailbox，photo from email。

I don't understand English, I use Google Translate.

Hi 呂:


請問您是要使用CPU的GPU效能嗎? 在BIOS裡有一個選項是"IGFX",Enabled後應該就可以使用了


這是BIOS L2.32的功能,以下提供BIOS給您

=======================================================================================================================

Hi Lu:


Do you want to use the GPU performance of the CPU? There is an option in the BIOS that is "IGFX", it should be available after Enabled


This is the function of BIOS L2.32, the following provides BIOS for you

 

There is a set of FTP address and password in the email, sorry I don’t know if I should disclose it, so I uploaded the firmware to onedrive.

 

 

email screenshot:

 

 

 

My own BCM firmware:

 

 

Everything is fine so far

Edited September 23, 20205 yr by int2e

4 hours ago, parisv said:

ooh so now they've added this on the official firmware? At last!!

 

@int2e

Where did you get this firmware from it doesn't show for me on their website.

Did this reset any of your existing settings?

 

 

I upgraded on the basis of 2.21a and kept the original configuration perfectly without any changes.
But the premise is that the upgrade is to choose to retain the BIOS configuration.

2 hours ago, kaiguy said:

Thanks for sharing the link to this bios, int2e! I take it you received this directly from William? Any idea what has been fixed/changed?

I don't know what it has updated. Of course, the most obvious is IGFX. I don't know the others. The official technical support did not inform me.

2 hours ago, Hoopster said:

@int2e  Your screenshot of BIOS also shows a BMC version that is not publicly available (1.72.00).  Is that needed in conjunction with the 2.32 BIOS to support some changes?  1.80 BMC and 2.30 BIOS are still the versions publicly available on the ASRock website.

These two screenshots were sent to me via official technical support email. I used BCM 1.80.00 which can be downloaded from the official website. It seems that they are completely compatible.

Thank you very much for this topic. Before that, I used the 2.21a bios in the current topic, and everything was normal. The official emails were late, but they brought updated bios.

 

 

Edited September 23, 20205 yr by int2e

thanks for sharing.

Has anyone else updated to this new bios?

I've been running L2.32 since setting up my new hardware around the 25th. Seamless operation here

On 10/11/2020 at 9:36 AM, JM2005 said:

Has anyone else updated to this new bios?

I did about several weeks ago, no issues to report in my case.

Does the new firmware fix the turbo boost problem?

On 10/17/2020 at 12:42 AM, jbear said:

I did about several weeks ago, no issues to report in my case.

I am assuming that it is still an either/or type scenario with that the iKVM functions until the iGPU starts up in the OS? No way to run both simultaneously.

On 10/16/2020 at 10:06 PM, Shane01638 said:

Does the new firmware fix the turbo boost problem?

I tried re-enabling turbo on my unraid setup and it locked up after 2-3 days, I'm running 6.9 Beta 30.  Is this a motherboard issue?  Unraid issue?  Does anyone even know?, it is bothersome that I can't enable turbo mode.

On 10/19/2020 at 10:20 PM, Plaidy said:

I am assuming that it is still an either/or type scenario with that the iKVM functions until the iGPU starts up in the OS? No way to run both simultaneously.

Correct, really no change, other than not needing a special BIOS now.  If you enable iGFX, it will work exactly how the special unreleased BIOS did.

Still no L2.32 BIOS on the ASRock site.  I may try another MB at some point, seems like we shouldn't have to throttle the CPU.

Edited October 29, 20205 yr by jbear

For what it’s worth, I have never disabled turbo boost and have not had a hang. Granted though I rarely ever hit anywhere close to my CPU Max.  But I have put it through some stress tests though without issue (Folding, for example). 

52 minutes ago, kaiguy said:

For what it’s worth, I have never disabled turbo boost and have not had a hang. Granted though I rarely ever hit anywhere close to my CPU Max.  But I have put it through some stress tests though without issue (Folding, for example). 

Same here, minus the stress tests.  Turbo boost is still active on my system, and has been running fine (touch wood).

1 hour ago, kaiguy said:

For what it’s worth, I have never disabled turbo boost and have not had a hang. Granted though I rarely ever hit anywhere close to my CPU Max.  But I have put it through some stress tests though without issue (Folding, for example). 

It only crashed on me when I was running BIONC 24x7.  That was a real stress test.  It would crash in anywhere from 16 hours to 3-4 days of continuous high CPU usage.

 

When I disabled Turbo Boost, the crashes went away and I ran it for weeks on end with no problem. 

 

I have had Turbo Boost re-enabled for months now with no problems.  There is nothing in my normal use of the CPU (including several  consecutive HandBrake encodes) that comes anywhere near the stress of BOINC/Folding.

1 hour ago, Hoopster said:

It only crashed on me when I was running BIONC 24x7.  That was a real stress test.  It would crash in anywhere from 16 hours to 3-4 days of continuous high CPU usage.

 

When I disabled Turbo Boost, the crashes went away and I ran it for weeks on end with no problem. 

 

I have had Turbo Boost re-enabled for months now with no problems.  There is nothing in my normal use of the CPU (including several  consecutive HandBrake encodes) that comes anywhere near the stress of BOINC/Folding.

I've been using Handbrake to transcode about 200 older ISO's, after about a day or so of heavy use, it locked.  When I'm done with this project, I will try and re-enable Turbo, and see if I experience issues under more "normal" use.

I've had Turbo disabled but decided to re-enable it again last night. Server crashed overnight. I wasn't running anything that should stress the server. 

¯\_(ツ)_/¯

 

Quote

<13>Oct 29 20:17:58 DeathStar tips.and.tweaks: Tweaks Applied
<4>Oct 29 20:46:26 DeathStar kernel: mdcmd (237): spindown 4
<4>Oct 29 20:46:36 DeathStar kernel: mdcmd (238): spindown 0
<4>Oct 29 20:46:37 DeathStar kernel: mdcmd (239): spindown 2
<4>Oct 29 20:46:38 DeathStar kernel: mdcmd (240): spindown 3
<4>Oct 29 20:46:38 DeathStar kernel: mdcmd (241): spindown 5    
<4>Oct 29 20:46:39 DeathStar kernel: mdcmd (242): spindown 6
<4>Oct 29 20:46:40 DeathStar kernel: mdcmd (243): spindown 8
<4>Oct 29 21:01:01 DeathStar kernel: mdcmd (244): spindown 1    
<4>Oct 29 21:36:33 DeathStar kernel: mdcmd (245): spindown 7
<4>Oct 29 22:53:26 DeathStar kernel: mdcmd (246): spindown 1    
<4>Oct 29 23:28:42 DeathStar kernel: mdcmd (247): spindown 7
<4>Oct 29 23:56:41 DeathStar kernel: mdcmd (248): spindown 6
<6>Oct 30 00:10:36 DeathStar kernel: veth983241a: renamed from eth0
<6>Oct 30 00:10:36 DeathStar kernel: docker0: port 2(vethca62111) entered disabled state
<6>Oct 30 00:10:36 DeathStar kernel: docker0: port 2(vethca62111) entered disabled state    
<6>Oct 30 00:10:36 DeathStar kernel: device vethca62111 left promiscuous mode
<6>Oct 30 00:10:36 DeathStar kernel: docker0: port 2(vethca62111) entered disabled state
<6>Oct 30 00:10:37 DeathStar kernel: docker0: port 2(veth5dc5130) entered blocking state
<6>Oct 30 00:10:37 DeathStar kernel: docker0: port 2(veth5dc5130) entered disabled state
<6>Oct 30 00:10:37 DeathStar kernel: device veth5dc5130 entered promiscuous mode
<6>Oct 30 00:10:37 DeathStar kernel: IPv6: ADDRCONF(NETDEV_UP): veth5dc5130: link is not ready
<6>Oct 30 00:10:37 DeathStar kernel: docker0: port 2(veth5dc5130) entered blocking state
<6>Oct 30 00:10:37 DeathStar kernel: docker0: port 2(veth5dc5130) entered forwarding state
<6>Oct 30 00:10:37 DeathStar kernel: docker0: port 2(veth5dc5130) entered disabled state
<6>Oct 30 00:10:37 DeathStar kernel: eth0: renamed from vethba80b6a
<6>Oct 30 00:10:37 DeathStar kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth5dc5130: link becomes ready    
<6>Oct 30 00:10:37 DeathStar kernel: docker0: port 2(veth5dc5130) entered blocking state
<6>Oct 30 00:10:37 DeathStar kernel: docker0: port 2(veth5dc5130) entered forwarding state
<13>Oct 30 01:00:01 DeathStar Plugin Auto Update: Checking for available plugin updates
<13>Oct 30 01:00:03 DeathStar Plugin Auto Update: Community Applications Plugin Auto Update finished
<77>Oct 30 04:00:49 DeathStar crond[2213]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null    
<4>Oct 30 04:35:21 DeathStar kernel: mdcmd (249): spindown 0

 

This is probably a long shot but will this board, with a Core series processor take this TEAMGROUP Elite DDR4 32GB Single (1 x 32GB) 3200MHz RAM?

It is most definitely not listed as supported on the Asrock site but I know the compatibility list is not always the end alI be all and was wondering if it would clock down to 2666MHz and work anyway. Will this board even accept 32 GB sticks of Non-ECC ram or is 4x16gb the max when using commercially sold memory?

 

Are there any other things to take into consideration when running this board without a Xeon CPU and ECC memory? I want the lowest TDP possible which seems to be the T series Core processors at 35w but have a board that is capable of IPMI and quicksync.

Edited November 18, 20205 yr by Plaidy

3 hours ago, Plaidy said:

Will this board even accept 32 GB sticks of Non-ECC ram or is 4x16gb the max when using commercially sold memory?

It will accept 32GB non-ECC RAM according to spec on MB web page.

 

I cannot comment on that specific RAM, however, I have used RAM in the past on ASRock boards that were not on the RAM QVL.  ASRock support told me directly that as long as the RAM meets the general RAM specs for the board, there is a high probability that it will work just fine whether or not it is on the QVL.

 

3 hours ago, Plaidy said:

I want the lowest TDP possible which seems to be the T series Core processors at 35w but have a board that is capable of IPMI and quicksync

 

There are lots of T Core processors on the supported CPU list for the board as I am sure you already checked.

 

There are really no special considerations for using a non-Xeon CPU and non-ECC RAM.  You just don't get whatever "features" those parts support but it does not change the behavior of the system or require any special configuration or consideration.

 

My backup server (also an ASRock board with IPMI) is running with a core i5-4590 CPU with QuickSync and non-ECC RAM (not on the QVL for that board) and there are zero issues, concerns or special considerations.