Less than 64M RAM available?, on 5500 w/ cacko 64-0 and new kernel Options

[javamatte]

I reflashed my 5500 for the first time last night, and everything went fairly
smoothly (once I realized that my first SD card would be faster if I set it
on fire )

I am using the Cacko/Crow 64-0 ROM (for sl-5500) and the updated Cacko kernel.
Everything seems to be running great, but when I pull up the System Info app,
it shows the Total Memory as 46280k.

Shouldn't this be much closer to 64000k?

[lpetroni]

I reflashed my 5500 for the first time last night, and everything went fairly
smoothly (once I realized that my first SD card would be faster if I set it
on fire  )

I am using the Cacko/Crow 64-0 ROM (for sl-5500) and the updated Cacko kernel.
Everything seems to be running great, but when I pull up the System Info app,
it shows the Total Memory as 46280k.

Shouldn't this be much closer to 64000k?

Old question with no reply but recently flashed Cacko/Crow and was surprised to see the same behaviour. Why?

Any clues?

[lardman]

Is the missing memory allocated as a ram-disk in the same way the original Sharp images worked?

what does 'cat /proc/meminfo' show?

I'd expect a small amount of memory to be missing in an OZ image to mount things like /tmp, /var in a tmpfs (though I don't know whether Cacko does this), but certainly not 17Mb straight after boot (I assume that's where you are). If you've actually been doing things, and do have a tmpfs, then (on OZ at least) it's allowed to grow up to half the available memory, so you might want to check this too.


Si