Contribute
Register

[Solved] OSX10.8.5 stuck at apple logo after RAM upgrade

Status
Not open for further replies.
orson.wouters said:
Sorry, I numbered them like I remembered them visually, editted!
Click to expand...
Still makes no sense, for instance two modules should be installed in slots 1 and 3.
 
Now it's correct, sorry for confusion. I did install them correctly anyway, because I checked in the manual and got an alert from osx saying that my memory was installed in the correct way. Problem is not there.

I'm wondering what that "/n" kernel is and why it can't be found if I use different RAM sticks...
Also wondering why I can boot in safe mode with these new ram sticks, why can't it just work in normal mode as well?
 
orson.wouters said:
Now it's correct, sorry for confusion. I did install them correctly anyway, because I checked in the manual and got an alert from osx saying that my memory was installed in the correct way. Problem is not there.

I'm wondering what that "/n" kernel is and why it can't be found if I use different RAM sticks...
Also wondering why I can boot in safe mode with these new ram sticks, why can't it just work in normal mode as well?
Click to expand...

It is still wrong :
orson.wouters said:
1 New RAM 4GB
2 New RAM 4GB
3 Old RAM 2GB
4 Old RAM 2GB
-> System stops booting when at apple logo. No spinning wheel appears.
Click to expand...

Should be :
1 Old RAM 2GB
2 New RAM 4GB
3 Old RAM 2GB
4 New RAM 4GB

But the bottom line is if it won't boot with just one DIMM of the new RAM in slot 1 or slot 3 then the new RAM is probably incompatible or your BIOS is incorrectly configured.
 
Last edited:
orson.wouters said:
Also wondering why I can boot in safe mode with these new ram sticks, why can't it just work in normal mode as well?
Click to expand...

If as you say you are able to boot in safe mode then make sure that Trust is selected in your config.plist :

Trust.png
 
orson.wouters said:
Can we learn something from this?
Are they identified incorrectly?
Click to expand...
F2 at Clover boot menu saves preboot.log in /efi/clover/misc. Your system profiler screenshot seems to show a single channel of RAM over 4 sockets.

From this pre-boot log (or sudo bdmesg output) we can see that Clover initially detected RAM from (an example) native SMBIOS like this:
Code: 
0:100  0:000  === [ Get Smbios ] ========================================
0:100  0:000  Type 16 Index = 0
0:100  0:000  Total Memory Slots Count = 2
0:100  0:000  Type 17 Index = 0
0:100  0:000  SmbiosTable.Type17->Speed = 1600MHz
0:100  0:000  SmbiosTable.Type17->Size = 4096MB
0:100  0:000  SmbiosTable.Type17->Bank/Device = BANK 0 ChannelA-DIMM0
0:100  0:000  SmbiosTable.Type17->Vendor = 0000
0:100  0:000  SmbiosTable.Type17->SerialNumber = 00000000
0:100  0:000  SmbiosTable.Type17->PartNumber =              
0:100  0:000  Type 17 Index = 1
0:100  0:000  Ignoring insane frequency value 0MHz
0:100  0:000  SmbiosTable.Type17->Speed = 0MHz
0:100  0:000  SmbiosTable.Type17->Size = 0MB
0:100  0:000  SmbiosTable.Type17->Bank/Device = BANK 1 ChannelA-DIMM1
0:100  0:000  SmbiosTable.Type17->Vendor = <null string>
0:100  0:000  SmbiosTable.Type17->SerialNumber = <null string>
0:100  0:000  SmbiosTable.Type17->PartNumber = <null string>
Which is incorrect. It is necessary to specify the memory modules in config plist.
Code: 
<key>SMBIOS</key>
<dict>
...
<key>Memory</key>
        <dict>
            <key>Channels</key>
            <integer>2</integer>
            <key>Modules</key>
            <array>
                <dict>
                    <key>Frequency</key>
                    <string>1600</string>
                    <key>Part</key>
                    <string>0x4B485831363030433953334C2F3847202020</string>
                    <key>Serial</key>
                    <string>0x00000000</string>
                    <key>Size</key>
                    <string>4096</string>
                    <key>Slot</key>
                    <string>0</string>
                    <key>Type</key>
                    <string>DDR3</string>
                    <key>Vendor</key>
                    <string>0x0198</string>
                </dict>
                <dict>
                    <key>Frequency</key>
                    <string>1600</string>
                    <key>Part</key>
                    <string>0x4B485831363030433953334C2F3847202020</string>
                    <key>Serial</key>
                    <string>0x00000000</string>
                    <key>Size</key>
                    <string>4096</string>
                    <key>Slot</key>
                    <string>2</string>
                    <key>Type</key>
                    <string>DDR3</string>
                    <key>Vendor</key>
                    <string>0x0198</string>
                </dict>
            </array>
            <key>SlotCount</key>
            <integer>4</integer>
        </dict>
...
</dict>

The final values used for patching before boot:

Code: 
16:994  0:000  === [ PatchSmbios ] =======================================
16:994  0:000  insert table 9 for dev 0:0
16:994  0:000  insert table 9 for dev 0:1
16:994  0:000  insert table 9 for dev 0:0
16:995  0:000  Injecting user memory modules to SMBIOS
16:995  0:000  Channels: 2
16:995  0:000  Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23
16:995  0:000  BANK0 DIMM0 1600MHz 4096MB
16:995  0:000  BANK1 DIMM0 1600MHz 4096MB
16:995  0:000  BANK0 DIMM1 EMPTY
16:995  0:000  BANK1 DIMM1 EMPTY
16:995  0:000  mTotalSystemMemory = 8192
16:995  0:000  NumberOfMemoryDevices = 4
16:995  0:000  Type20[0]->End = 0x3FFFFF, Type17[0] = 0x1000
16:995  0:000  Type20[1]->End = 0x7FFFFF, Type17[1] = 0x3000
16:995  0:000  Table 131 is present, CPUType=35
16:995  0:000  Change to: 605
 
Where can I find this config.plist?
 
Ok, must have been a compatibility issue...

I traded my 2x4GB sticks for my brothers 2x2GB sticks that are the very same RAM sticks as my originals.
I can fill 4 slots with 2Gb sticks from Apacer now and system boots and works fine.
The 4GB sticks work on my brothers Windows computer (which has a gigabyte mobo as well from the same era but with AMD processor).
I think I'm going to settle with this.

Thanks a lot for helping me everybody!
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top