* Ralph Slooten <[EMAIL PROTECTED]> [2006-06-21 04:12]: > Sorry, but one thing remains unclear. Ignoring the fact that adding > embedded extras to your kernel on a non-embedded system just to get the > the VMSPLIT options is (in my opinion) confusing and unlogical, is this > step actually needed considering I (according to your advice) would take > the default VMSPLIT anyway? > What I mean is simply: If I enable HIGHMEM4GB to allow the kernel to use > my 2GB of RAM, do I still need to add the embedded options (as you > explain above), or is simply using HIGHMEM4GB enough? It's maybe a tough > question is ask, but you definitely seem to know exactly what you are > talking about ;-)
Right; the right thing to do here is to not touch VMSPLIT at all, which means there's no reason to be messing around with CONFIG_EMBEDDED. Just set HIGHMEM4GB and be done with it (but, if you're editing a config where you've already done so, make sure that you still have all of the CONFIG_EMBEDDED dependent options set correctly before you unset it: enable every one of the "standard kernel features" except for the extra pass, and then make sure you have the default 3/1 VMSPLIT) > > Hope this helps. > > Is sure does! Any advice to the above question? With that I should be > complete I think ;-) Where do you get your information from btw (I'm > curious as I didn't find much via Google explaining as clear as you did)? I did some googling about a year and a half ago, when I finally upgraded my desktop from 512MB to 1GB and ran into these issues for the first time, and I've spent some time poking around the kernel sources before. -- David Klempner
pgpy6jT8opukm.pgp
Description: PGP signature
