D820 nVidia - "Panic" error upon reboot

[epic2015]

Lots of progress.  Started from scratch.  Rebuild USB from scratch. 

Did build from scratch.  I babied the install and moved the mouse for 30 min.  I saw screens with prompts that I had never seen before.  (which was good)  

Sound and Display was an issue. 

I looked via trial and error and found the folder using finder than using terminal once it gets hosed. 

I could not figure out how you directly extracted kexts from EDP using the folders.  I ran EDP 

  The EDP failed at the ACPIPlatform like before.  I located the Extra / Extensions folder in both the USB and the install drive 

I copied pasted all the kexts from the USB Extra / extensions to the hard drive extra extensions. 

I ran my fix from the My hack app.  

Sound suddenly worked.  

I was able to reboot and boot up successfully and not have it fail on boot. 

I did run the sudo command to fix the hibernation.  It did not solve the problem.  I removed the options for the display to sleep to never in the preferences.  Is there any way to fix that?  On a laptop having a recoverable sleep would help with battery life.  

 

Once we get this fixed I am going to write up a full end to end instructions (so if there are others like me they can just have those and not drive you guys crazy like I have)   I started to write them tonight.  

 

Thank you for your patience and continued support. 

[Hervé]

There's no need for additional instructions you know, it's just the EDP which is broken on the ACPIPlatform kext.

[epic2015]

Any other suggestions for the hibernation  / sleep issue?    (Yes I did the sudo command)  Is there any kexts which control that or other settings? 

 

Thanks 

[Hervé]

There should not be any sleep/hibernation/wake issues.

 

The D620 nVidia was known for its unrecoverable dark gray screen after screen sleep, but that could be recovered by putting the computer to sleep and then wake it; screen would then return to life.

 

I'll go and check what I have on my D620 NV for sleep&wake; can't remember if it's using the SleepEnabler kext or not.

[Hervé]

Ok, nothing specific for Sleep/Wake on the D620 nVidia. It's just running on native CPU power management with MBP5,1 settings (SMBIOS + SMC keys)

 

Can you list the kexts you have in /E/E and the version you use for FakeSMC? Is there a string of characters in your Chameleon boot plist Properties field?

[epic2015]

Thank you again for all your help.  Here are the items you were asking for  

 

Your question: Can you list the kexts you have in /E/E and the version you use for FakeSMC? Is there a string of characters in your Chameleon boot plist Properties field?

 

Kexts in E/ E Are: (Manually listed so bear with me if there are type-o's)

 

AppleACPIPlatform.kext

AppleACPIPS2Nub.kext

AppleBCM5751Ethernet.kext

AppleHDADisabler.kext

FakeSMC.kext

IntelCPUMonitor.kext

NullCPUPowerManagement.kext

SleepEnabler.kext

VoodooBattery.kext

VoodooHDA.kext

VoodooPState.kext

VoodooTSCSync.kext

 

 

FakeSMC Version is:   Version 4 

 

 

String of Characters in Chameleon boot plist - properties?  (was trying to figure out what you were looking for.  Here is the content of the file I have) 

 

There were actually two listed.  This is for the first one: org.chameleon.Boot.plist

 

 

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

<key>EHCIacquire</key>

<string>Yes</string>

<key>EthernetBuiltIn</key>

<string>Yes</string>

<key>ForceHPET</key>

<string>Yes</string>

<key>GenerateCStates</key>

<string>Yes</string>

<key>GeneratePStates</key>

<string>Yes</string>

<key>GraphicsEnabler</key>

<string>Yes</string>

<key>Kernel</key>

<string>mach_kernel</string>

<key>Kernel Flags</key>

<string></string>

<key>PciRoot</key>

<string>1</string>

<key>SystemType</key>

<string>2</string>

<key>Theme</key>

<string>Default</string>

<key>Timeout</key>

<string>2</string>

<key>UHCIreset</key>

<string>Yes</string>

<key>USBBusFix</key>

<string>Yes</string>

<key>UseKernelCache</key>

<string>Yes</string>

<key>arch</key>

<string>i386</string>

<key>device-properties</key>

<string>5c0400000100000001000000500400001700000002010c00d041030a000000000101060000010101060000007fff04000e0000004e00560050004d00000020000000010000000000000000000000000000000000000000000000000000001c000000400030002c00660062006f006600660073006500740000000800000000000200360000004100410050004c002c006100750078002d0070006f007700650072002d0063006f006e006e0065006300740065006400000008000000010000001c0000006400650076006900630065005f00740079007000650000000f0000004e5644412c506172656e74240000004100410050004c00300030002c0069006e0076006500720074006500720000000800000000000000220000004100410050004c002c0067007200610079002d00700061006700650000000800000001000000320000004100410050004c002c006200610063006b006c0069006700680074002d0063006f006e00740072006f006c0000000800000001000000420000004100410050004c00300030002c0062006c00610063006b00730063007200650065006e002d0070007200650066006500720065006e0063006500730000000800000000000008100000006d006f00640065006c0000001e0000006e56696469612051756164726f204e5653203131304d20454649160000006200750069006c0074002d0069006e000000050000000022000000400030002c006400650076006900630065005f00740079007000650000000b000000646973706c61791c000000400031002c006200750069006c0074002d0069006e0000000400000022000000400031002c006400650076006900630065005f00740079007000650000000b000000646973706c617920000000400031002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616314000000400030002c006e0061006d0065000000120000004e5644412c446973706c61792d411c000000400030002c006200750069006c0074002d0069006e0000000400000014000000400030002c004e0056004d00540000005c0000000a037f204c2d1c0278051a044807d0056006000041041d0421040000f0c1410700000100000000ff00000000000000000000000000000000000000000000000000000000ffff00000000000000000000010000000000000014000000400031002c006e0061006d0065000000120000004e5644412c446973706c61792d421200000049004f004e0061006d00650000000b000000646973706c617920000000400030002c0063006f006d00700061007400690062006c00650000000e0000004e5644412c4e564d616324000000400031002c00630061006e002d0068006f0074002d0070006c0075006700000004000000100000004e00560043004100500000001800000004000100000003000c0000000000000a000000002a00000049004f0050004d004900730050006f007700650072004d0061006e00610067006500640000000500000001</string>

</dict>

</plist>

 

=================

=================

 

This is now the content for the second one: org.chameleon.Boot.plist.plist

 

bplist00—^UseKernelCacheSYes

[Hervé]

Everything looks Ok to me. However you could try to temporarily remove the VoodooHDA+HDADisabler kexts in case the KP comes from Voodoo (has caused issues in the past, depending on the version you have). You'd have no audio of course, but at least you'd know if that was the source of the problem.

 

Forget about that org.chameleon.Boot.plist.plist, you can delete that file.