zachg

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.

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.

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

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?

Whoops, the attachment didn't attach. Here it is again. EFI.zip

Wahoo! I just successfully booted without safe mode using the files in my attached zip. Not saying they are all correct, but...baby steps. I made a number of tweaks so I'm not sure exactly which it was, but I think it may have been the verde.kext. I'll test it out more for isolation. My system report is correctly reading the AMD m6000 as a Radeon HD 7870m. QE/CI seems to be active as HD video and screen saver good to go. The final thing before I settle down to just tweaking drivers, etc...the display! Still nothing out from the primary laptop display. Only video out on HDMI external monitor. Is this an EDID thing?

Okay, state of the union. I used ssdtPRGen.sh to generate an ssdt while in the m6700 via safe mode, and I was able to use Clover configurator in safe mode to create a config.plist. I also used MaciASL to add some patches to my CloverF4 DSDT.aml file. I mostly just added stuff that was relevant to HD 4000 graphics. Regarding the Clover configurator, it created a plist that seemed to have a lot of irrelevant and gibberish things. I tried booting with it, but it still went to black screen after boot, so I went back to a simpler plist. Now, when I boot with verbose, I'm seeing a much faster boot process with a lot less hangs, but it eventually appears to initialize graphics, then back to black screen. HDMI out also is a black screen, unless I'm in safe mode. Bronxteck, I did check out the Cloud Clover editor. It seems to be a plist editor where, if you know where you need to be, it could get you there, but there's not much automation or device detection.

If I boot the USB from Legacy Boot rather than UEFI Boot (in the F12 Boot Options), that is the error I get.

Thanks Bronxteck. I got into the Sierra install and ran the shell script to generate an ssdt. I wasn't able to run the clover configurator due to only being able to boot in safe mode. I should mention also that even in Safe Mode I am only getting video with hdmi out to an external monitor. Nothing so far on the primary screen.

Update: I've got a successful Sierra install and I can successfully boot to the installed disk Safe Mode. Still troubleshooting. So far I am using the files from this thread: https://osxlatitude.com/index.php?/topic/9487-need-help-with-sierra-on-m6700/ The only potential issue I see with using that DSDT is that I have an i7 vs the i5. We have the same graphics.

You aren't even getting to the clover menu? Did you install clover to a USB, and did it create an EFI partition? This might be obvious to anyone else, but I'm still getting used to UEFI and I didn't realize for a while to select the UEFI option during boot. After hitting F12, make sure you are using the UEFI option to get to clover, rather than just selecting the name of your USB drive among the other drives. FWIW, I have an m6700 and if I use the USB ports on the right side of my machine, I get weird boot errors, but if I use one of the two ports on the left side, those errors go away. I think this has to do with USB3 support. As far as BIOS settings, I think the only ones I toggled were AHCI and Legacy with secure boot off. Not sure if m6600 BIOS is similar, but I imagine so. Take any of this advice with a grain of salt, as I still haven't gotten a fully booted system due to what seems to be graphics driver issues.

I'm currently working on getting Sierra installed on my m6700. Here's my specs: Precision M6700 CPU: i7-3740qm (ivy bridge) HD: SSD main drive Graphics: AMD Firepro m6000 (~7870m) and intel HD 4000 (seems to be disabled when m6000 present) Display: 1920x1080 Wifi: Atheros AR9820 wifi So far I've tried Clover as well as other installers, with as many boot flag combinations as I could come up with. I've tried using other's DSDT.aml and config files that have been successful for them. No luck yet. The farthest I've been able to get to is the initial boot seems to initialize the graphics and I get a black screen (black but not off). If I plug in hdmi out to an external monitor, I get a funky aqua green screen on the secondary monitor, but no cursors or anything. Here's some of the threads that give me hope I'm working toward something possible. https://osxlatitude.com/index.php?/topic/9680-need-help-with-a-precision-m6600-sierra-install/ https://osxlatitude.com/index.php?/topic/9136-m6600-setup/ https://osxlatitude.com/index.php?/topic/9487-need-help-with-sierra-on-m6700/ http://www.insanelymac.com/forum/topic/286953-dell-precision-m6700-osx-installation/ In one of the threads I included above, an admin (Jake Lo) patches an m6700 DSDT file for a user. I did try using that file, but no luck. I'm thinking I should try patching my own DSDT and SSDT files, but I'm not sure which patches to use. I've extracted my ACPI files with CloverF4 and attached them below. In MaciASL, I have RehabMan's Laptop repo I'm sort of haphazardly selecting the patches and so far I haven't been able to compile without errors. Any suggestions would be welcome, whether it is regarding the DSDT patching or my approach in general. Thanks. DSDT and SSDT.zip