Memory problem

General system Kernel, boot, graphics & hardware
1

Hi all. When I boot up my EOS box, the first message I get is the following: “cannot unprotect memory range…”, and then I get two very long numbers in hexadecimal, which I assume is the address range. What does this mean and how can I fix it?

GR

2

Seems to be related to BIOS…

This issue has been mentioned on the MSI Forums and the ASRock Forums as well.

3

@UncleSpellbinder, From what I’ve been reading, you may be right. I have a Gigabyte B850I AORUS PRO (32GB DDR5 RAM), which I updated not long ago. Now, on their website, there seems to be another update to fix a DDR5 memory problem. I’ll see what the new update is about and let you know how I fared.

GR

4

@UncleSpellbinder
I installed the new BIOS update but it didn’t solve the problem. I’m thinking that I may have to join the Gigabyte forum to see if I can get an answer. At least it isn’t causing any problems for me while I’m using this computer.

GR

5

So just finished flashing my Gigabyte Bios to the latest version and got the same error, but it did also just boot after the error. If I understand this correctly the memory update had something to do with Hynix memory chips, which as far as I know are not on my memory sticks (Corsair) , so maybe that causes the error ?

6

I contacted Gigabyte and asked if that error could be harmful and they replied that it often happens with Arch and Arch-based installations, but it’s inconsequential and causes no harmful effects either to the hardware or software. If I find a way to fix it, I’ll post the fix on the EOS forum. BTW, I have 2x16GB Corsair memory sticks.

GR

7

I have an older MSi Z370 GAMING M5 board with Corsair Vengeance LPX 32GB (2 x 16GB) DDR4 DRAM @ 3000MHz. The latest available BIOS is version 7B58v1B dated 2024-08-09. So I have the latest BIOS update already for my board. Hopefully, if/when another BIOS update for my board is released, the issue will be addressed.

8

Hmm this is kind of weird because the error does not show up on Artix (Arch based but uses Openrc instead of systemd) or any other distros I have installed. So it could be a combination of Arch with systemd thing.