Re: Maximum RAM configured in kernel
On Wed, May 23 2007, at 18:30 +1000, Evan Clarke wrote:
[ ... ]
> evan@bender:/boot$ uname -a
> Linux bender 2.6.18-4-powerpc #1 Fri May 4 01:05:19 UTC 2007 ppc GNU/Linux
>
> evan@bender:/boot$ grep GHME config-2.6.18-4-powerpc
> CONFIG_HIGHMEM=y
> CONFIG_HIGHMEM_START=0xfe000000
> evan@bender:/boot$
>
> Any ideas?
This is new for me, too. But this is what I would do:
*** 1
Checking whether OSX recognises RAM correctly - If you don't have OSX
installed, taking some OSX rescue CD for hardware diagnostics might
help.
*** 2
If you use yaboot:
yaboot.conf, as it seems,
- see http://lists.debian.org/debian-powerpc/2005/10/msg00452.html - eats
a line like this:
append="mem=<your-RAM-size>"
(Please check whether this is true ... I just found it via Google ...)
*** 3
Then I've made a mistake when giving you the 'grep' line in my
previous email - Sorry. Something like this one should be more
appropriate:
$ grep MEM /boot/config-2.6.18-rc4-060811-dirty
CONFIG_SHMEM=y
# CONFIG_TINY_SHMEM is not set
CONFIG_HIGHMEM=y
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ARCH_FLATMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
CONFIG_FLATMEM_MANUAL=y
# CONFIG_DISCONTIGMEM_MANUAL is not set
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_FLATMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
# CONFIG_SPARSEMEM_STATIC is not set
CONFIG_HIGHMEM_START=0xfe000000
CONFIG_LOWMEM_SIZE=0x30000000
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_DEBUG_HIGHMEM is not set
*** 4
Recompiling the kernel if you think changing switches like the ones in
'3' might help.
I only know how to compile git kernels. I believe that's easy on
Debian. A short description how to do
that is here:
http://wolfgangpfeiffer.com/kernel.html
Please note the part that starts with:
"Important update - Wed, 06 Dec 2006"
*** 5
Last, not least: Google
HTH
Good luck!
Wolfgang
--
Wolfgang Pfeiffer: /ICQ: 286585973/ + + + /AIM: crashinglinux/
http://profiles.yahoo.com/wolfgangpfeiffer
I made slight changes on Key ID: E3037113. Please refresh it.
http://keyserver.mine.nu/pks/lookup?search=0xE3037113&fingerprint=on
Reply to: