[GMA 950 / 10.6.2 64-bit] Blank Gray Screen with Dr. Hurt's DSDT fix

[dreamdust]

I have an ASUS P5L8L motherboard that uses the Intel GMA 950 onboard GPU (device id 2772).

 

I have installed Snow Leopard successfully using a patched DSDT and can boot into 10.6.2 64-bit mode without problems. Snow Leopard recognizes my GMA950 without a DSDT patch but QL/QE/3D Acceleration is not enabled and it's stuck in VESA with a max resolution of 1280x1024. My monitor's native resolution is 1680x1050.

 

I followed Dr. Hurt's DSDT patching guide, and when booting with the patched DSDT everything boots fine but when the GUI loads it just displays a blank gray screen (no apple logo, nothing but gray).

 

What does the blank gray screen mean?

 

I've attached the DSDT in question:P5L8L.zip

 

Any help would be much appreciated!

[dreamdust]

I was able to get full display detection and acceleration by removing Dr. Hurt's DSDT patch, replacing the AppleIntelIntegratedFramebuffer.kext from 10.6.2 with the one from 1.5.1 (ver. 1.4.20.28), booted into 32-bit mode (because of old kext), and everything works flawlessly.

 

But the question remains... why is this?

 

- What changed from the old framebuffer kext to the new?

- What language is the framebuffer kext written in or how can I decompile it to compare with the new one

- Why is DSDT patching insufficient?

[riws]

FrameBuffer does not detect the Display correctly, you need EFI String with HasPanel Info.

[dreamdust]

Isn't the HasPanel fix for laptops with external displays? This is a desktop with an smbios.plist mirroring the Mac Mini (same chipset, graphics, etc). Using google and forum searches I cannot find any EFI string that works for desktops.

 

I added this "HasPanel" info to my com.apple.Boot.plist, but it doesn't seem to change anything.

 

I still don't understand why DSDT is not sufficient to fix this issue, the same chipset and device-id is used in the Mac Mini and Macbook Pro.

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>

<key>GUI</key>
<string>no</string>

<key>Timeout</key>
<string>1</string>

<key>DSDT</key>
<string>DSDT-v4.aml</string>

<key>arch</key>
<string>i386</string>

<key>USBBusFix</key>
<string>Yes</string>

<key>ForceHPET</key>
<string>Yes</string>

<key>Graphics Mode</key>
<string>1680x1050x32</string>

<key>PciRoot(0x0)/Pci(0x2,0x1)</key>
<dict>
<key>AAPL,HasPanel</key>
<string>0x00000001</string>
<key>model</key>
<string>GMA 950</string>
</dict>

</dict>
</plist>

[riws]

Does your DSDT have Outputs?

[riws]

Isn't the HasPanel fix for laptops with external displays? This is a desktop with an smbios.plist mirroring the Mac Mini (same chipset, graphics, etc). Using google and forum searches I cannot find any EFI string that works for desktops.

 

I added this "HasPanel" info to my com.apple.Boot.plist, but it doesn't seem to change anything.

 

I still don't understand why DSDT is not sufficient to fix this issue, the same chipset and device-id is used in the Mac Mini and Macbook Pro.

 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>

<key>GUI</key>
<string>no</string>

<key>Timeout</key>
<string>1</string>

<key>DSDT</key>
<string>DSDT-v4.aml</string>

<key>arch</key>
<string>i386</string>

<key>USBBusFix</key>
<string>Yes</string>

<key>ForceHPET</key>
<string>Yes</string>

<key>Graphics Mode</key>
<string>1680x1050x32</string>

<key>PciRoot(0x0)/Pci(0x2,0x1)</key>
<dict>
<key>AAPL,HasPanel</key>
<string>0x00000001</string>
<key>model</key>
<string>GMA 950</string>
</dict>

</dict>
</plist>

 

 

I Think you need that part as String/device-properties:

 

<key>PciRoot(0x0)/Pci(0x2,0x1)</key>
<dict>
<key>AAPL,HasPanel</key>
<string>0x00000001</string>
<key>model</key>
<string>GMA 950</string>
</dict>

 

	<key>device-properties</key>
<string>6d0000000100000001000000610000000200000002010c00d041030a00000000010106000002
7fff0400100000006d006f00640065006c0000000b000000474d4120393530200000004100410050
0
04c002c00480061007300500061006e0065006c0000000800000001000000</string>

[dreamdust]

Thanks for all your help on this. It's much appreciated.

 

I've tried that EFI string but it's for laptops. I can't find one that works for my setup. How are they generated? I downloaded EFI Studio and OSX86Tools but both of those programs have preselected EFI strings.

 

My DSDT compile (using iasl) outputs 0 errors, 0 warnings, and 44 optimizations. DSDT patching doesn't seem to make a difference because even without a patch OS X detects my GMA950. I guess something in the framebuffer driver has changed to where it doesn't detect my display and initialize hardware acceleration.

 

What I'd like to understand is why my display isn't detected after framebuffer 1.4.2? Even the latest 64-bit AppleIntelIntegratedFramebuffer.kext includes my device id (2772 8086)!

[riws]

Its done with gfxutil. Try to add LCD/CRT Device to your DSDT?

[IvanMS]

Hi, i'm rookie on Hackintosh and MacOsx. I have an acer notebook running a Hack Leopard 10.5.8 very well and trying to run Snow Leopard on my netbook Atom 2GB 250GB. I can run the iPortable SL version a i am trying to install the Snow_Leopard_10.6.1-10.6.2_SSE2_SSE3_Intel_AMD_by_Hazard version on it.

 

I could do it, fixed the first kernel panic IOATAFamily (during the second installation) and the AppleTyMCEDrive, deleting it. But what is happening is, when i boot this version, all comes to a gray screen, not that gray screen stuck with that cicle, etc. It comes only as a gray screen, no signals or anything, with the music when you receive the Welcome first screen after a good istallation booting for the first time. Even at Security mode.

 

When i had installed Leopard on it, it worked with a graphic controler drive for Intel GMA950.

 

I know how to go in (-s) user and i have how to access these SL partition booting with iPortable but that's all i konw to do.

 

Anyone could help me with these?

I think it can be a matter with graphic video controller but i don't know much more even what and how to do.

Thank you very much.

 

Ivan SInigaglia (Brazil)

 

 

 

Its done with gfxutil. Try to add LCD/CRT Device to your DSDT?

[Ash P]

Hi, I've done alot of reading and realised the best way to apply the intel GMA950 EFI string lets say, for snow leopard is to use OSX86Tools which is old and discontinued but does apply this patch properly.

 

1. Download and Open OSX86Tools

2. Click Add "Add EFI Strings/Boot Flags"

3. Click "GFX Strings" opens new window

4. Choose Graphics Card: - "Intel GMA 950 (Laptop)"

5. Click "Import String to Boot Editor" New window opens

6. Click "Apply changes to com.apple.boot.plist"

 

Now I assume you have a near vanilla snow leopard installation. therefore your probably using PC-EFI, chameleon or similar and have your kexts, themes, DSDT and real com.apple.boot.plist in /Extra. So at this point you could go to /Library/Preferences/SystemConfiguration/ if your com.apple.boot.plist was modified properly you should see a bootbackup.plist. remove the hex key generated from here into your proper boot.plist in extra using textedit or plist editor if you have xcode tools installed

 

here's my one: -

Note!!!!!! don't go using it in your machine might not work, carry out steps above

 

	<key>device-properties</key>
<string>6d0000000100000001000000610000000200000002010c00d041030a000000000101060000027
fff0400100000006d006f00640065006c0000000b000000474d41203935302000000041004100500
0
4c002c00480061007300500061006e0065006c0000000800000001000000</string>

 

save you com.apple.boot.plist in /Extra

 

and Reboot

 

make sure you have vanilla kext in S/L/E and there you go snow leopard 32-bit should load on your main monitor

as far as i know there is no appleintelgma950.kext that is 64-bit compatible unless somebody knows. but AppleIntelIntegratedFramebuffer.kext is 64-bit so there is a chance I could get this to work with 64-bit 950 kext

 

OSX86Tools can also be used if Quartz GL is not enabled and System Profiler shows it is supported

 

Regards,

Ash

 

 

please let me know if anybody has GMA950 loading in 64-bit