anybody with X8DA6? strange graphics problems in mav

[fotiskam]

I would give a shot on 10.6.8. For me, the last good mac os version, just like ios 6. But, if you need newer software, like logic X , then you have to go at least to 10.8 I think...

I have an asus board which goes 100% stable on 10.6.8 , but has major stability issues (with graphics) on 10.9 and 10.10 on the identical build... what to say...

 

[hlrsellsout]

im going to try that this weekend as well. I prefer Mavericks, simply because of the dual-screen menu and dock options, but I was on Snow Leopard for a long time prior to that because it works perfectly with my TC cards (last official supported OS is 10.6)

I wasnt even able to get a booted installer with my 10.6 stick, it kept KPing immediately on boot. But now that i have fixed DSDTs and SSDTs for the machine I may give it a whirl again this weekend.

thanks for all of your input, just having somebody to bounce ideas off of has been super helpful.

 

[hlrsellsout]

alright! so, had the machine on last night, just doing some things, had some crashes and managed to actually catch it in the logs this time. perhaps this might shed some light on what's going on?

7/24/15 9:47:10.000 PM kernel[0]: NVDA(OpenGL): Channel exception! Exception type = 0x8 DMA Engine Error (FIFO Error 8)
7/24/15 9:47:10.000 PM kernel[0]: 4443564e 00000110 b5973462 01e89979 00000001 00000014 d3793533 46d3a4a6
7/24/15 9:47:10.000 PM kernel[0]: 4614f297 e71edccf 00088301 000000dc 12f24e0a 081d0a4b 1002a0ad 20001801
7/24/15 9:47:10.000 PM kernel[0]: 30002800 02803800 0c828040 00500048 00600d58 01080b22 808e8010 81022202
7/24/15 9:47:10.000 PM kernel[0]: 080d2201 8a841001 04220280 30948280 01080e22 81808410 80052202 088180b6
7/24/15 9:47:10.000 PM kernel[0]: 149a030a 82200a00 00081d13 02182a10 28088d20 480fa0d6 58015000 78646001
7/24/15 9:47:10.000 PM kernel[0]: 01019000 0a150198 00138a03 13923d0a 24380a3a 0e000000 01000000 490000e0
7/24/15 9:47:10.000 PM kernel[0]: 01000000 49000000 0000000e 47000000 21000104 26000600 200034bc 22000000
7/24/15 9:47:10.000 PM kernel[0]: 48006415 3b007336 0a0001f4 1c13c21f 00100008 f480a818 0d200bf7 03300828
7/24/15 9:47:10.000 PM kernel[0]: aabae038 4041d281 02481480 4443564e
7/24/15 9:47:11.569 PM com.apple.launchd[1]: (com.apple.DumpGPURestart) Throttling respawn: Will start in 9 seconds
7/24/15 9:47:15.000 PM kernel[0]: NVDA: Unable to make context resident prior to start of command buffer processing!
7/24/15 9:47:15.000 PM kernel[0]: NVDA: Calling glrKillClient for task 0xffffff806a1dc840
7/24/15 9:47:15.537 PM ReportCrash[534]: DebugSymbols was unable to start a spotlight query: spotlight is not responding or disabled.
7/24/15 9:47:15.765 PM com.apple.appkit.xpc.openAndSavePanelService[499]: HIToolbox: received notification of WindowServer event port death.
7/24/15 9:47:15.765 PM Finder[344]: HIToolbox: received notification of WindowServer event port death.
7/24/15 9:47:15.765 PM NotificationCenter[365]: HIToolbox: received notification of WindowServer event port death.
7/24/15 9:47:15.765 PM SystemUIServer[343]: HIToolbox: received notification of WindowServer event port death.
7/24/15 9:47:15.765 PM TextEdit[497]: HIToolbox: received notification of WindowServer event port death.
7/24/15 9:47:15.765 PM com.apple.dock.extra[385]: HIToolbox: received notification of WindowServer event port death.
7/24/15 9:47:15.765 PM Console[402]: HIToolbox: received notification of WindowServer event port death.
7/24/15 9:47:15.765 PM EscrowSecurityAlert[423]: HIToolbox: received notification of WindowServer event port death.
7/24/15 9:47:15.765 PM com.apple.appkit.xpc.openAndSavePanelService[499]: port matched the WindowServer port created in BindCGSToRunLoop
7/24/15 9:47:15.765 PM Finder[344]: port matched the WindowServer port created in BindCGSToRunLoop
7/24/15 9:47:15.766 PM Dock[341]: HIToolbox: received notification of WindowServer event port death.
7/24/15 9:47:15.766 PM NotificationCenter[365]: port matched the WindowServer port created in BindCGSToRunLoop
7/24/15 9:47:15.766 PM SystemUIServer[343]: port matched the WindowServer port created in BindCGSToRunLoop
7/24/15 9:47:15.766 PM Console[402]: port matched the WindowServer port created in BindCGSToRunLoop
7/24/15 9:47:15.766 PM com.apple.dock.extra[385]: port matched the WindowServer port created in BindCGSToRunLoop
7/24/15 9:47:15.766 PM EscrowSecurityAlert[423]: port matched the WindowServer port created in BindCGSToRunLoop
7/24/15 9:47:15.766 PM Dock[341]: port matched the WindowServer port created in BindCGSToRunLoop
7/24/15 9:47:15.766 PM Dock[341]: Lost connection with usernoted.
7/24/15 9:47:15.766 PM NotificationCenter[365]: Connection interrupted.
7/24/15 9:47:15.767 PM UserEventAgent[11]: Captive: [UserAgentDied:142] User Agent @port=56587 Died
7/24/15 9:47:15.770 PM imagent[374]: Quit - notifying about shutdown
7/24/15 9:47:15.770 PM identityservicesd[375]: Quit - notifying about shutdown
7/24/15 9:47:15.770 PM identityservicesd[375]: Quit - shutting down daemon
7/24/15 9:47:15.771 PM com.apple.launchd[1]: (com.apple.WebKit.Networking.A57F758F-889E-48EF-AD46-490F7DFF62EC[359]) Could not terminate job: 3: No such process
7/24/15 9:47:15.771 PM com.apple.launchd[1]: (com.apple.WebKit.Networking.A57F758F-889E-48EF-AD46-490F7DFF62EC[359]) Using fallback option to terminate job...
7/24/15 9:47:15.772 PM imagent[374]: Quit - shutting down daemon
7/24/15 9:47:15.782 PM com.apple.launchd[1]: (com.apple.WebKit.Networking.A57F758F-889E-48EF-AD46-490F7DFF62EC[359]) Exited with code: 1
7/24/15 9:47:15.800 PM loginwindow[535]: Login Window Application Started
7/24/15 9:47:15.860 PM ReportCrash[534]: Saved crash report for WindowServer[321] version 599.7 to /Library/Logs/DiagnosticReports/WindowServer_2015-07-24-214715_MachineX.crash
7/24/15 9:47:15.967 PM com.apple.launchd[1]: (com.apple.WindowServer[321]) Job appears to have crashed: Abort trap: 6
7/24/15 9:47:15.974 PM WindowServer[536]: Server is starting up
7/24/15 9:47:15.975 PM WindowServer[536]: Session 256 retained (2 references)
7/24/15 9:47:15.975 PM WindowServer[536]: Session 256 released (1 references)
7/24/15 9:47:15.977 PM WindowServer[536]: Session 256 retained (2 references)
7/24/15 9:47:15.978 PM WindowServer[536]: init_page_flip: page flip mode is on
7/24/15 9:47:15.995 PM WindowServer[536]: Found 66 modes for display 0x00000000 [39, 27]
7/24/15 9:47:15.998 PM WindowServer[536]: Found 1 modes for display 0x00000000 [1, 0]
7/24/15 9:47:16.000 PM WindowServer[536]: Found 1 modes for display 0x00000000 [1, 0]
7/24/15 9:47:16.002 PM WindowServer[536]: Found 1 modes for display 0x00000000 [1, 0]
7/24/15 9:47:16.003 PM WindowServer[536]: mux_initialize: Couldn't find any matches
7/24/15 9:47:16.004 PM WindowServer[536]: Found 66 modes for display 0x00000000 [39, 27]
7/24/15 9:47:16.015 PM com.apple.launchd.peruser.501[180]: (com.apple.Dock.agent[341]) Exited with code: 1
7/24/15 9:47:16.016 PM WindowServer[536]: Found 1 modes for display 0x00000000 [1, 0]
7/24/15 9:47:16.016 PM WindowServer[536]: Found 1 modes for display 0x00000000 [1, 0]
7/24/15 9:47:16.017 PM WindowServer[536]: Found 1 modes for display 0x00000000 [1, 0]
7/24/15 9:47:16.154 PM WindowServer[536]: WSMachineUsesNewStyleMirroring: false
7/24/15 9:47:16.155 PM WindowServer[536]: Display 0x2b28498c: GL mask 0x1; bounds (0, 0)[1280 x 1024], 66 modes available
Main, Active, on-line, enabled, boot, Vendor 10ac, Model a00b, S/N 314a4b4c, Unit 0, Rotation 0
UUID 0xf12c686822c4d7fb19132f31e97c2bb4
7/24/15 9:47:16.155 PM WindowServer[536]: Display 0x003f003f: GL mask 0x8; bounds (0, 0)[0 x 0], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
7/24/15 9:47:16.155 PM WindowServer[536]: Display 0x003f003e: GL mask 0x4; bounds (0, 0)[0 x 0], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
7/24/15 9:47:16.155 PM WindowServer[536]: Display 0x003f003d: GL mask 0x2; bounds (0, 0)[0 x 0], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
7/24/15 9:47:16.156 PM WindowServer[536]: WSSetWindowTransform: Singular matrix
7/24/15 9:47:16.156 PM WindowServer[536]: WSSetWindowTransform: Singular matrix
7/24/15 9:47:16.156 PM WindowServer[536]: WSSetWindowTransform: Singular matrix
7/24/15 9:47:16.157 PM WindowServer[536]: Display 0x2b28498c: GL mask 0x1; bounds (0, 0)[1280 x 1024], 66 modes available
Main, Active, on-line, enabled, boot, Vendor 10ac, Model a00b, S/N 314a4b4c, Unit 0, Rotation 0
UUID 0xf12c686822c4d7fb19132f31e97c2bb4
7/24/15 9:47:16.158 PM WindowServer[536]: Display 0x003f003f: GL mask 0x8; bounds (2304, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 3, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
7/24/15 9:47:16.158 PM WindowServer[536]: Display 0x003f003e: GL mask 0x4; bounds (2305, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 2, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
7/24/15 9:47:16.158 PM WindowServer[536]: Display 0x003f003d: GL mask 0x2; bounds (2306, 0)[1 x 1], 1 modes available
off-line, enabled, Vendor ffffffff, Model ffffffff, S/N ffffffff, Unit 1, Rotation 0
UUID 0xffffffffffffffffffffffffffffffff
7/24/15 9:47:16.158 PM WindowServer[536]: CGXPerformInitialDisplayConfiguration
7/24/15 9:47:16.158 PM WindowServer[536]: Display 0x2b28498c: Unit 0; Vendor 0x10ac Model 0xa00b S/N 826952524 Dimensions 13.31 x 10.63; online enabled, Bounds (0,0)[1280 x 1024], Rotation 0, Resolution 1
7/24/15 9:47:16.158 PM WindowServer[536]: Display 0x003f003f: Unit 3; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (2304,0)[1 x 1], Rotation 0, Resolution 1
7/24/15 9:47:16.158 PM WindowServer[536]: Display 0x003f003e: Unit 2; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (2305,0)[1 x 1], Rotation 0, Resolution 1
7/24/15 9:47:16.158 PM WindowServer[536]: Display 0x003f003d: Unit 1; Vendor 0xffffffff Model 0xffffffff S/N -1 Dimensions 0.00 x 0.00; offline enabled, Bounds (2306,0)[1 x 1], Rotation 0, Resolution 1
7/24/15 9:47:16.165 PM WindowServer[536]: GLCompositor: GL renderer id 0x01022727, GL mask 0x0000000f, accelerator 0x000045cb, unit 0, caps QEX|MIPMAP, vram 2048 MB
7/24/15 9:47:16.171 PM WindowServer[536]: GLCompositor: GL renderer id 0x01022727, GL mask 0x0000000f, texture max 16384, viewport max {16384, 16384}, extensions FPRG|NPOT|GLSL|FLOAT
7/24/15 9:47:16.171 PM WindowServer[536]: GLCompositor enabled for tile size [256 x 256]
7/24/15 9:47:16.171 PM WindowServer[536]: CGXGLInitMipMap: mip map mode is on

 

[hlrsellsout]

hmmmm i may have found something here.

i noticed that on bootup with Clover, it was giving an error about AGPM Unknown Controller. Doing some forum searching I found somebody who was talking about it, apparently its because the system is expecting either GFX0 or IGPU depending on what SMBIOS you're using. I looked through my DSDT and SSDT and could find no reference to either, so based off what Ive found so far it seems like perhaps the system or some component of it is having trouble finding the graphics card?

i messed up my clover reinstall earlier so im re-installing now, once im done, im going to use IORegistryExplorer to determine what slot my graphics card is in and either modify the config.plist to patch it on the fly, or edit my DSDT. right now its looking like its expecting a string "NPEx" depending on what slot its in. the DSDT is showing NPE1 through NPEA. (10 entries). Looking at the motherboard block diagram, there are 10 PCI lanes breaking out from the 5520 northbridge on this board. It shows ports 3-6 as being allocated for the graphics card so im not sure which one I will need to use. But i guess i'll find out!

 

[fotiskam]

To tell you the truth I am not a tech guru, I usually use google to solve my problems.. However you seem to be in a good way. Just to mention a couple of things from my experience, maybe they can help you:

1. About AGPM KEXT. I recently edited this kext in I got speedstep working for my GPU GTS 450 . You can copy the file to desktop, right click and show contents. There you will find a "info" file I think, which has power managemet information. It includes all the real macs there. This unfortunately means it doesnt inlude your GPU. So, all you have to do is find the spot where it talks about e.g mac pro 4.1 ( it depends from your current smbios) and just replace the GPU ID with yours. You can find your on system profiler on about this mac. It should be a 4 digit code. After that , save the file and install the modified kext with kext utility. Also , repair disk permissions too with disk utility.. If your mod works, on the next boot it should load correctly the agpm.kext

2. Somewhere in the log I saw entries about NVDA.KEXT. I havent done much research on it but I remember having issues with it in the past with gts 450 (fermi card). The solution was the freezefix I told you before.. Also, I think that NVDA kext holds some GPU IDs too, maybe a same modification as above would correct the trick ( I havent done this myself so its up to you...)

3. As I told you before, it seems that your MB is not cooperating well with the mac os. That probably means not 100% good DSDT. So keep on the good work and dont lose faith! Sometimes the solution is just a different letter or number ......

 

[hlrsellsout]

To tell you the truth I am not a tech guru, I usually use google to solve my problems.. However you seem to be in a good way. Just to mention a couple of things from my experience, maybe they can help you:

3. As I told you before, it seems that your MB is not cooperating well with the mac os. That probably means not 100% good DSDT. So keep on the good work and dont lose faith! Sometimes the solution is just a different letter or number ......

just want to say THANK YOU for at least responding to my posts! and thanks for the encouragement. i'll figure it out eventually.

The dsdt thing was kind of strange.. Ive tried playing around with DSDTs before and always had trouble. my current system, a DZ77RE-75K board, has an impossible DSDT... try to compile that thing and it throws like 45 hard errors. the DSDT for this board was remarkably clean! it had a few warnings which were easily patched (although, perhaps i should take another look at just what it was patching) and the SSDT had no compile errors at all.


the problem is, i really dont understand this stuff at all, so while i can edit to my heart's content, i still dont really know what im doing. its like using google translate to have a conversation with someone in german. i see the words, i can see the mechanics of the word, but ive no idea why its being used in that way in that place.

thanks again for the encouragement, that alone is motivation to keep going

 

[slim.jim]

just want to say THANK YOU for at least responding to my posts! and thanks for the encouragement. i'll figure it out eventually.

The dsdt thing was kind of strange.. Ive tried playing around with DSDTs before and always had trouble. my current system, a DZ77RE-75K board, has an impossible DSDT... try to compile that thing and it throws like 45 hard errors. the DSDT for this board was remarkably clean! it had a few warnings which were easily patched (although, perhaps i should take another look at just what it was patching) and the SSDT had no compile errors at all.


the problem is, i really dont understand this stuff at all, so while i can edit to my heart's content, i still dont really know what im doing. its like using google translate to have a conversation with someone in german. i see the words, i can see the mechanics of the word, but ive no idea why its being used in that way in that place.

thanks again for the encouragement, that alone is motivation to keep going

If you are using MaciASL for DSDT editing then make sure you have it set to 5.0 instead of 4.0 in the preferences. Generally it will greatly reduce the errors when trying to compile.

 

[fotiskam]

thanks again for the encouragement, that alone is motivation to keep going

You are welcome friend.. Only by sharing our thought there can be better "hackintosh"!!!

As for DSDT, is indeed a little bit confusing, is Pure programming Stuff. The SSDTs usually dont bring errors. As slim.jim suggested, you can try to set 5 instead of 4 (which is default). Keep it where it brings you less errors.... Also, in bios there is a value, at least in an asus mobo I have, where you specify your ACPI language and things like that....

An error free DSDT doesnt always indicate a good DSDT. There are extra patches that you can apply and add extra lines of codes. Without these extra lines, the DSDT maybe error free, but WITH these lines it may give precious info to the Os ( mavericks) about how it will cooperate with the motherboard and your hardware.

 

[hlrsellsout]

If you are using MaciASL for DSDT editing then make sure you have it set to 5.0 instead of 4.0 in the preferences. Generally it will greatly reduce the errors when trying to compile.

thank you, i double-checked, its set on 5.

You are welcome friend.. Only by sharing our thought there can be better "hackintosh"!!!

As for DSDT, is indeed a little bit confusing, is Pure programming Stuff. The SSDTs usually dont bring errors. As slim.jim suggested, you can try to set 5 instead of 4 (which is default). Keep it where it brings you less errors.... Also, in bios there is a value, at least in an asus mobo I have, where you specify your ACPI language and things like that....

yes i did find that. by default on my system its set to 2.0. My available options there are 1, 2, and 3.0.

An error free DSDT doesnt always indicate a good DSDT. There are extra patches that you can apply and add extra lines of codes. Without these extra lines, the DSDT maybe error free, but WITH these lines it may give precious info to the Os ( mavericks) about how it will cooperate with the motherboard and your hardware.

good point, I should look into that some more. I suppose the fact that the graphics card shows up under NPE3 is not an indication that the system is trying to address it directly or that simply changing it to GFX0 will have its intended effect - perhaps there needs to be a separate entry entirely for GFX0 with more relevant data for the card.

i did also manage to get an export from lspci in Ubuntu with all my devices installed. perhaps this too will be of use.
in the process of doing this, i discovered something: The 5520 chipset is basically a modified X58 chipset. This may be of great use to me and provide more leads as I was able to google some search results of people experiencing lag on X58s. Perhaps there may be of something of use there.

ive attached new files, these are pure as they were output by ubuntu; dsdt, ssdt and lspci output.

 

[hlrsellsout]

well, weeks later and still no progress what so ever.

ive learned a lot about DSDT editing and such in the meantime. I've now got a DSDT with fixes for Nvidia 500 series cards in place, its seeing my card, its pulling the monitor device ID properly, everything is recognized as it should.... and yet the graphics lockups continue.
Ive also modified my AGPM kext for nvidia 500 series cards, which too made no difference.

im going to try to get a BIOS downgrade from supermicro. ive found people from a couple years ago using these boards on SL but nothing since. im also going to try doing SL in 32-bit since the only references ive found to people getting these working was in 32-bit mode. from this thread - http://www.tonymacx86.com/buying-advice/17949-what-if-i-just-buy-apple-motherboard-2.html