Click to See Complete Forum and Search --> : 2g of RAM = Hugemem Kernel?
shad0w
10-12-2005, 02:54 PM
I'm getting this warning:
Linux version 2.4.21-27.0.2.EL (buildsys@bob) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-49)) #1 Wed Jan 19 17:56:28 EST 2005
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007fff0000 (usable)
BIOS-e820: 000000007fff0000 - 000000007fff3000 (ACPI NVS)
BIOS-e820: 000000007fff3000 - 0000000080000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Warning only 896MB will be used.
Use a HIGHMEM enabled kernel.
896MB LOWMEM available.
Its only 2g of RAM, but its not being used... Will the Highmem kernel fix this?
Thanks!
ph34r
10-12-2005, 03:10 PM
Yup, the bigmem should fix it
Icarus
10-12-2005, 03:12 PM
It should, I think RH basic kernels only support 1Gb of memory and the highmem kernel is for 2GB or more which sounds exactly like what you need ;)
shad0w
10-12-2005, 03:59 PM
Memory: 2052904k/2097088k available (1703k kernel code, 41620k reserved, 1287k data, 232k init, 0k highmem)
That was it. Thanks guys. Now my NIC is broken, says it can't load 8139too
shad0w
10-12-2005, 05:21 PM
NIC problem solved. I'm running Redhat 9 and I upgraded to the hugemem CentOS 3.x kernel. The hugemem kernel doesn't have all the NIC modules (or other modules for that matter), it requires the unsupported kernel rpm as well.
Side note: When searching google with a search of hugemem, please do NOT hit the spell correction link. Bad things will happen... Thats what I get for having an itchy trigger finger. :eek:
aNoob
10-13-2005, 04:28 AM
I have same message.Question is where do I enable this in my config :
#
# Firmware Drivers
#
CONFIG_EDD=m
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
CONFIG_SELECT_MEMORY_MODEL=y
Icarus
10-13-2005, 07:47 AM
CONFIG_NOHIGHMEM=n
aNoob
10-13-2005, 09:02 AM
Thx,I'll recompile it again.Any idea why this is left off by default?Can something go so wrong to let this one not enabled?
Icarus
10-13-2005, 11:19 AM
makes for a smaller kernel so it uses less memory, most though because you don't want the kernel to set addresses for 1GB of memory when you only have 128MB available ;)
If you look at the help for it in menuconfig it goes into a lot more detail
shad0w
10-13-2005, 01:30 PM
Here are some useful links for the memory question(s) in this thread:
http://www.linux.com/howtos/IO-Perf-HOWTO/overview.shtml
http://kerneltrap.org/node/2450
bwkaz
10-13-2005, 07:02 PM
CONFIG_NOHIGHMEM=n I'm pretty sure you'll have to turn on one of CONFIG_HIGHMEM4G and CONFIG_HIGHMEM64G, too.
In fact, I'd just use menuconfig to do it. ;)
Icarus
10-13-2005, 07:32 PM
I'm pretty sure you'll have to turn on one of CONFIG_HIGHMEM4G and CONFIG_HIGHMEM64G, too.
In fact, I'd just use menuconfig to do it. ;)
So would I :)
aNoob
10-14-2005, 09:19 AM
Thanks alot for the tips. I'll check it ASAP.I really don't want to bring down my machine now that I have almost a month uptime.Neverthless,it will come down at the end of this month when I will have to install new fans and cooling system for the next summer heat :)
BTW: I always use menuconfig.I just feel safer ;)
Icarus
10-14-2005, 10:48 AM
As a note also, when you set CONFIG_NOHIGHMEM=n You have two options
CONFIG_HIGHMEM4G
CONFIG_HIGHMEM64G
Use the first one unless you happen to have 4GB or more of memory, memuconfig won't let you select both as that would be silly and the kernel won't compile ;)