Contribute
Register

Anyone resolved the 10.8.3 AppleIntelFrameBuffer problem?

Status
Not open for further replies.
Joined
Jul 3, 2012
Messages
52
Motherboard
Gigabyte Z77-DS3H (1.0)
CPU
i5-3570K
Graphics
ATI 5850
Mac
  1. iMac
  2. MacBook Air
Classic Mac
  1. Quadra
Mobile Phone
  1. Other
The 10.8.3 on ATI/NVidia graphic card with HD4000 will encounter the AppleIntelFrameBuffer problem.

Debugger called: </SourceCache/GraphicsDrivers/GraphicsDrivers-8.10.44/Common/IONDRV/Intel/IVB/AppleIntelFrameBuffer/AppleINtelController.cpp:12351 Assertion failed: (0 == i) || ((pfbInfo->rangeStolen.phyBase - pfbInfoPrev->rangeSt"

Anyone resolved the problem?

BTW: We need the HD4000 to get the airplay mirroring feature.
 
Hey All,

I now resolve my problem with the boot after 10.8.3 update.

I have only 1 screen.

After trying various options(disabling IGFX, etc.), none of them worked for me. I decided to press the CMOS button in my MB, it cleared it and loaded the default values.

I now can boot without a problem.

Cheers

Edit: Typo
 
Could please show me your BUILD, BIOS settings and boot settings?
 
Could please show me your BUILD, BIOS settings and boot settings?

My Boot plist:
Code:
        <key>DropSSDT</key>
	<string>Yes</string>
	<key>EthernetBuiltIn</key>
	<string>Yes</string>
	<key>GenerateCStates</key>
	<string>Yes</string>
	<key>GeneratePStates</key>
	<string>Yes</string>
	<key>Graphics Mode</key>
	<string>1920x1080x32</string>
	<key>GraphicsEnabler</key>
	<string>Yes</string>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Kernel Flags</key>
	<string>npci=0x3000</string>
	<key>Legacy Logo</key>
	<string>Yes</string>
	<key>Timeout</key>
	<string>2</string>
	<key>UseKernelCache</key>
	<string>Yes</string>


I'm using MacMini6,2 SMBios
MB: Asrock Z77 Extreme 6
CPU: i7-3770

In my bios all my setting are defaults. Only thing I changed is my memory setting from "Auto" to "Profile 2 XMP"

U can try to reset your bios, maybe it can help you. But we have 2 different MB.

Cheers
 
It works for 4 days, then the kernel assertion happens again and again.
I have no idea now.
 
Status
Not open for further replies.
Back
Top