Under 512MB of RAM detected. Not enabling APC
-
Bad ram? Bad ram slot?
-
Would watch the POST messages in the first place. Chances are the board does not detect the incompatible chip properly at all.
-
Look in /var/log/dmesg.boot, in the first few lines it prints the amount of memory detected/available/etc.
-
To avoid other upgrade problems, I decided not to update from gui and did full new install from usb. but same problem as subject. I check
/var/log/dmesg.boot showing…real memory = 3221225472 (3072 MB)
avail memory = 3127234560 (2982 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <ptltd apic ="">FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 2 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1</ptltd > -
What do you see if you run this at the command line:
sysctl hw.physmem
Steve
-
$ sysctl hw.physmem
hw.physmem: 3185926144 -
Hmm, odd.
So you originally said you had 2GB but it looks like you have 3GB now, did you add more?Steve
-
yes…I did add ram...I missed to mention it...
-
Facing the same issue system is showing
hw.physmem: 3587276800but still getting the same error. I do upgraded RAM FROM 2GB TO 4GB.
any help is highly appreciated.
-
Facing the same issue system is showing
hw.physmem: 3587276800but still getting the same error. I do upgraded RAM FROM 2GB TO 4GB.
In your case it's highly likely the BIOS is reserving part of your 4GB for something else….
If you have a motherboard based graphics card, the BIOS often will share 512MB for graphics.With pfSense, you can safely reduce this in the BIOS to the minimum allowed as the console is text only (no graphics required).
-
Had this same issue. Turns out my solution was to install the 64-bit version. IDK why that made the difference but it did!
-
2gb of DDR1? 64bit system? That must be a really old server .