zachg Posted March 22, 2017 Author Share Posted March 22, 2017 Thanks Bronxteck. I'll go through the ioreg dump tonight to see if I can pin down the primary display in ioreg. In BootDisplay, I tried both 0 and 1, but no luck so far. I'll try iterating through the number of ports (currently set at four?) to see if I can pin down the internal display. Is the connector type for an internal display LVDS? Also, do you have an idea of what to look for in ioreg? Link to comment Share on other sites More sharing options...
zachg Posted March 23, 2017 Author Share Posted March 23, 2017 So here's so excerpts from my ioreg. I think they are relevant, but not too confident.What I see is that there are four ports (0-3). I think my external display is on port 3. I have a feeling that the internal display is port 0, as port 1 and port 2 have a couple of similarities that aren't shared with port 0. I have no idea how to effect these values. Graphics flags? Clover plist addons? I changed my BootDisplay flag to 1 to see if it mattered. No change. I also tried injecting my EDID and other display values with Clover. No luck. I'll keep trying. I had a hackintosh desktop about five years ago and recall that persistence was the key. -o ATY,Buri@0 <class AtiFbStub, id 0x100000374, registered, matched, active, busy 0 (4 ms), retain 8> | | | | | | { | | | | | | "backlight-control" = <01000000> | | | | | | "ATY,ActiveFlags" = 1 | | | | | | "audio-codec-info" = <00010300> | | | | | | "AAPL,gray-page" = <01000000> | | | | | | "display-dither-support" = <00000000> | | | | | | "connector-type" = 2 | | | | | | "IOFBDependentID" = 4294967749 | | | | | | "name" = "ATY,Buri" | | | | | | "ATY,ControlFlags" = 256 | | | | | | "display-connect-flags" = <00000000> | | | | | | "display-pixel-component-bits" = <06000000> | | | | | | "compatible" = <"ATY,Buri"> | | | | | | "av-signal-type" = <00000000> | | | | | | "VRAM,memsize" = <0000008000000080> | | | | | | "IOFBDependentIndex" = 0 | | | | | | "AAPL,gray-value" = <00000000> | | | | | | "display-type" = "NONE" | | | | | | "port-number" = 0 | | | | | | "device_type" = "display" | | | | | | "AAPL,boot-display" = <01000000> | | | | | | "display-link-component-bits" = <06000000> | | | | +-o ATY,Buri@1 <class AtiFbStub, id 0x100000375, registered, matched, active, busy 0 (1 ms), retain 8> | | | | | | { | | | | | | "display-type" = "NONE" | | | | | | "compatible" = <"ATY,Buri"> | | | | | | "connector-type" = 1024 | | | | | | "ATY,ActiveFlags" = 1 | | | | | | "IOFBDependentIndex" = 1 | | | | | | "audio-codec-info" = <00010700> | | | | | | "IOFBDependentID" = 4294967749 | | | | | | "ATY,ControlFlags" = 772 | | | | | | "VRAM,memsize" = <0000000000000080> | | | | | | "AAPL,gray-page" = <01000000> | | | | | | "device_type" = "display" | | | | | | "av-signal-type" = <00000000> | | | | | | "AAPL,gray-value" = <00000000> | | | | | | "display-connect-flags" = <00000000> | | | | | | "name" = "ATY,Buri" | | | | | | "port-number" = 1 | | | | | | } | | | | +-o ATY,Buri@2 <class AtiFbStub, id 0x100000376, registered, matched, active, busy 0 (1 ms), retain 8> | | | | | | { | | | | | | "display-type" = "NONE" | | | | | | "compatible" = <"ATY,Buri"> | | | | | | "connector-type" = 1024 | | | | | | "ATY,ActiveFlags" = 1 | | | | | | "IOFBDependentIndex" = 2 | | | | | | "audio-codec-info" = <00010900> | | | | | | "IOFBDependentID" = 4294967749 | | | | | | "ATY,ControlFlags" = 772 | | | | | | "VRAM,memsize" = <0000000000000080> | | | | | | "AAPL,gray-page" = <01000000> | | | | | | "device_type" = "display" | | | | | | "av-signal-type" = <00000000> | | | | | | "AAPL,gray-value" = <00000000> | | | | | | "display-connect-flags" = <00000000> | | | | | | "name" = "ATY,Buri" | | | | | | "port-number" = 2 | | | | | | } | | | | +-o ATY,Buri@3 <class AtiFbStub, id 0x100000377, registered, matched, active, busy 0 (1 ms), retain 8> | | | | | | { | | | | | | "display-type" = "LCD" | | | | | | "compatible" = <"ATY,Buri"> | | | | | | "connector-type" = 2048 | | | | | | "ATY,ActiveFlags" = 4 | | | | | | "IOFBDependentIndex" = 3 | | | | | | "audio-codec-info" = <00010b00> | | | | | | "IOFBDependentID" = 4294967749 | | | | | | "ATY,ControlFlags" = 516 | | | | | | "VRAM,memsize" = <0000000000000080> | | | | | | "AAPL,gray-page" = <01000000> | | | | | | "device_type" = "display" | | | | | | "av-signal-type" = <02000000> | | | | | | "AAPL,gray-value" = <00000000> | | | | | | "display-connect-flags" = <00000000> | | | | | | "name" = "ATY,Buri" | | | | | | "port-number" = 3 | | | | | | } ioreg.rtf Link to comment Share on other sites More sharing options...
zachg Posted March 23, 2017 Author Share Posted March 23, 2017 I also added the readable version of ioreg as an attachment. This is a copy paste from terminal, but clips the ends of a lot of hex values. Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted March 23, 2017 Administrators Share Posted March 23, 2017 yeah looks like apple boot display is on port 0 but it says display type is none yet port 3 is LCD so maybe try 3. if not it looks like you might need to patch connector types? i am not familiar with that part. Link to comment Share on other sites More sharing options...
zachg Posted March 27, 2017 Author Share Posted March 27, 2017 So, no luck yet. I started all over at one point with a different clover version and made a note of every step I took. Still can't get anything but a black screen on LVDS. I pulled an EDID from linux, but no change. I'll probably go back to linux until I have more time to tinker. He he. There's some irony in there some where. Link to comment Share on other sites More sharing options...
antrieb Posted December 24, 2017 Share Posted December 24, 2017 Any luck with your m6700 yet? What BIOS version does your m6700 have? I have got m6700 with i7-3470qm + HD4000 + k3000M, BIOS A18. Unfortunately, having graphics glitches right now after updating the BIOS from A10 to A18. Shall I downgrade the BIOS? I am looking for a DDST that works with my hardware... Link to comment Share on other sites More sharing options...
Administrators Bronxteck Posted December 25, 2017 Administrators Share Posted December 25, 2017 it might be the same bios glitch issue as the E6X30 series. that machine glitches after bios A11 or A12 you have to downgrade bios to I think A03 then back up to A11 or A12. its documented on the site somewhere. 1 Link to comment Share on other sites More sharing options...
antrieb Posted March 17, 2018 Share Posted March 17, 2018 all right...yes, the issue was related to the high bios version. I downgraded to A12 -> no more graphic glitches ever since. Link to comment Share on other sites More sharing options...
Recommended Posts