June 14, 20233 yr Friends, I have seen some posts on the subject. I have a Huananzhi x99 f8 gaming, I have 128GB installed and a Xeon 2680 v4 processor as per my attached BIOS images. On UNRAID console I have correct information too... But on the dashboard I have only 64GB, can anyone tell me what could be happening? I saw some posts and some broken links but nothing conclusive, I heard that it is simple to solve in the Huananzhi bios, but the solution link is off. Does anyone know anything? Edited June 14, 20233 yr by gomezz
June 14, 20233 yr Community Expert It's using 128GB, the other value usually suggests a BIOS bug, look for an update, but it is using the installed RAM, so nothing to worry about.
June 14, 20233 yr Author 6 minutes ago, JorgeB said: It's using 128GB, the other value usually suggests a BIOS bug, look for an update, but it is using the installed RAM, so nothing to worry about. Wouldn't that be the correct information?
June 14, 20233 yr Community Expert 2 minutes ago, gomezz said: Wouldn't that be the correct information? I believe that is what the BIOS is reporting.
June 14, 20233 yr Author 3 minutes ago, itimpi said: I believe that is what the BIOS is reporting. But my friend, the UNRAID console shows the correct information... 🤷♂️
June 14, 20233 yr Community Expert 3 minutes ago, gomezz said: But my friend, the UNRAID console shows the correct information... 🤷♂️ You are assuming that they are getting it from the same source.
June 14, 20233 yr Author 3 minutes ago, itimpi said: You are assuming that they are getting it from the same source. I dont know If on terminal shows correct information from BIOS, why the dashboard not? Edited June 14, 20233 yr by gomezz
June 14, 20233 yr Community Expert 20 minutes ago, gomezz said: Wouldn't that be the correct information? No, that's the one that comes from DMIDECODE, and it's wrong for the board, only a BIOS update can fix that, but like mentioned it doesn't really matter.
June 14, 20233 yr Author 5 minutes ago, JorgeB said: No, that's the one that comes from DMIDECODE, and it's wrong for the board, only a BIOS update can fix that, but like mentioned it doesn't really matter. The member "crenn" have a solution, but the link is broken
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.