All RAM not recognized by 64-bit install
-
do you have an option to run a memtest86? edit: (regardless of everything)
https://www.memtest86.com/while, I recommend this to your attention as well:
https://forum.netgate.com/topic/141147/tsc-p-state-invariant-performance-statistics -
Hmm, not much there.
You might try booting in verbose mode. Create the file /boot/loader.conf.local then add to it:
boot_verbose="YES"
.That will give you a lot more output at boot. It may show you some ACPI errors or similar responsible for this.
Steve
-
Since the OS can't possibly be 32-bit your next culprit is the BIOS.
FreeBSD shows you what hardware is there (8GB) and then what has been made available to the OS (~3GB).
Check for things like memory allocated to onboard video, any kind of memory management that might be geared toward a 32-bit OS, and other things of that nature.
-
@jimp How could the video memory card allocate that much ram?
-
Ask the BIOS. I've seen onboard "gaming" video cards that would happily claim multiple GB of RAM if given permission in the BIOS.
-
@hoopin4you Hi, did you ever solve this issue?
I've just install a 64bit pfsense v2.5.2 and pfsense is only using 3.3gb of RAM.
BIOS and pfsense logs both show 8gb.
Real = 8192MB
Available = 3317MBHow did you get around this?
-
What hardware are you installing on? Some early 64bit systems had some interesting BIOS 'quirks'.
Steve
-
@chas said in All RAM not recognized by 64-bit install:
@hoopin4you Hi, did you ever solve this issue?
I've just install a 64bit pfsense v2.5.2 and pfsense is only using 3.3gb of RAM.
BIOS and pfsense logs both show 8gb.
Real = 8192MB
Available = 3317MBHow did you get around this?
I never figured it out, and since then, I am now using a Cisco router.
-
@stephenw10 said in All RAM not recognized by 64-bit install:
What hardware are you installing on? Some early 64bit systems had some interesting BIOS 'quirks'.
Steve
It was an HP Pavilion 64-bit tower. I know the full 8GB was showing available when I had Windows installed, and the BIOS showed the same thing.
-
Mmm, well I would definitely try booting verbose to check the ACPI errors if you're seeing this as I said previously. There's a good chance the BIOS is passing some values to FreeBSD that Windows never sees because most manufacturers don't care about anything else.
Steve