Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Francois Newsgroups: comp.sys.mac.hardware.misc Subject: Re: Memory lock failed Date: Sat, 20 Aug 2011 17:08:34 +0200 Lines: 28 Message-ID: <9ba0viF192U1@mid.individual.net> References: <9b7u9sFgmsU1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net D2CFq8gdm+R476rp1pNUrgFnPjry/IFZvgTjiIEOvdQqQkUxGu Cancel-Lock: sha1:xl/v1JX4uATxiVoGcL/tkZg5hf4= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.1.16) Gecko/20101125 Thunderbird/3.0.11 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.sys.mac.hardware.misc:173 On 20/08/2011 14:45, philo wrote: > > > > More than likely you are booting to single mode using the 32bit kernel > which cannot address more than 4 gigs of ram. > > To access the full amount of ram you will need to boot to the 64bit kernel > > > > Supposedly you can boot the the 64 bit kernel by holding down the "6" > and the "4" keys while booting > > I am no mac expert though You are right on, philo. When I ran those memtest tests, I was under Snow Leopard, and maybe the kernel that appeared in Single User Mode (SUM) was 32 bits. Nevertheless memtest took nearly all the memory fro testing it (about 23 GB) but could not, of course lock it. Now I am under Lion ( OS X 10.7.1 ) and, when under SUM, it is well specified that the kernel is 64 bits : "Kernel is LP64" When running memtest, it says : "Attempting memory lock ... locked successfully". Thanks to you this "lock mystery" is solved and I'll be much more confident in memtest results in the future. Very best regards.