Search results

Thanks as always RehabMan for the clear instructions. I had been running my Skull Canyon NUC with macOS 10.12.6 and just upgraded to Mojave 10.14.0. I have a Samsung PM961 NVMe boot drive, which required the HackrNVMeFamily.kext in 10.12.6. 10.14 supports the PM961 natively. My NUC failed to...

Heads up on the macOS Sierra 10.2.6 Security Update 2017-001 vs. NVMe boot: After installing the update, my Skull Canyon NUC6i7KYK failed to boot from NVMe. (I am using HackrNVMeFamily.kext.) The boot would kernel panic in com.apple.iokit.IOSCSIArchitectureModelFamily. To resolve, I booted...

First, correction, I made a typo. 3840 x 2160 doesn’t work at 60 Hz. (I updated my post above.) If I create corresponding resolutions in SwitchResX, they come up as “invalid”. The highest I can take 3840 x 2160 is 45 Hz. 3200 x 1800 and lower do work at 60 Hz. Second, when I open System...

What I haven’t figured out is how to create scaled HiDPI resolutions. I’d like to run my 4K monitor at 3008 x 1692 or 3200 x 1800 HiDPI scaled down to 3840 x 2160. (I. e., everything drawn in 2x at 6016 x 3384 or 6400 x 3600 and scaled down by the Intel HD 5000.) I’ve tried creating scaled...

Thanks Sebinouse, good work as always. I can confirm: Haswell NUC 16 GB RAM (2 x Samsung M471B1G73DB0-YK0) Samsung 850 EVO mSATA 1 TB HGST HTS541515A9E630 1.5 TB Brcm4331 Wi-Fi ASUS PB287Q 4K monitor Kernel panic in the Brcm driver until I removed SSDT-4.aml as noted by PaulyGlocke. I removed...

Sebinouse, thanks for the great work! I’ll be trying your new guide soon. Has anyone successfully enabled 4K resolutions on the Haswell NUC with El Capitan? To recap, I was able to drive my ASUS PB287Q over DisplayPort 1.1 at 3840 x 2160 @30 Hz from my Haswell NUC under Mavericks, but never...

The panic references the graphics drivers, so perhaps you can boot in safe mode (by adding -x to your clover boot options), which will disable GPU acceleration. You might find some hints in this thread starting with post #559 and replies by Sebinouse. In particular, note that Sebinouse...

10.10.5 update My Haswell i5 NUC setup is based on MiniHack’s Clover build but with Macmini7,1 SMBIOS based on Sebinouse’s suggestions. I updated from 10.10.4 to 10.10.5 through Software Update with no issues, but the available resolutions are unchanged. Apple has updated...

Oh, my. I patched AppleIntelFramebufferAzul with the Piker-Alpha script 3.0, setting the BiOS-allocated memory to 64 MB and the framebuffer size to 34 MB (the maximum), but no change. Then I patched IOKit using the Perl command mentioned (as applicable to Yosemite) in the comments of the Google...

Thanks, those are very interesting links, particularly the comments on the first one. I’m thinking I should try the pixel clock patch to IOKit, and maybe try replacing just AppleIntelFramebufferAzul with the one from Mavericks. I should also probably try installing El Cap on the second...

I don’t quite follow—I was just thinking along these lines: 1. Apple advertises 3840 x 2160 @ 30 Hz for the MacMini7,1 (Intel HD 5000) but only 2560 x 1600 @ 60 Hz for the MacBookAir6,1 (also Intel HD 5000). 2. The Haswell i5 NUC hardware is perfectly capable of 3840 x 2160 @ 30 Hz. It works...

Yes, interesting, but I doubt it applies to the NUC. All the Intel documentation seems to suggest that the HD 5000 only supports SST displays. While it does apparently support MST for multiple displays, all the resolutions mentioned are achievable individually over SST, as are the resolution...

OK, thanks. That's what I thought. I wasn’t able to get MaciASL to save the file. Since you say that doesn’t necessarily indicate an error with the SSDT, I patched the binary with Hex Fiend, but I can’t get the NUC to boot with the patched SSDT-1.aml. It hangs shortly after DSMOS. Here are the...

Yes, in fact I think I may have been running that over HDMI in Mavericks. I was just quoting the Intel specs for the Haswell i5 NUC, which say that higher resolutions may or may not be supported. Maybe that’s a hedge against any resolution limits imposed by Windows.

Thanks, that’s a nice tool. But AFAICS it just offers the same resolutions I can get in the Monitors system preference by holding the option key when I click on “Scaled”.

Thanks... but I’m a bit out of my depth here. How should I edit the SSDT? I’m assuming I need to edit MiniHack’s SSDT-1.aml, and I’m using MaciASL 1.3 (246). However, even when I try to open the unmodified SSDT-1.aml and save it again with no edits, I get an error starting at line 223: 223...

So who would have guessed. They don’t work. :) kernel[0]: kxld[com.apple.driver.AppleIntelHD5000Graphics]: The vtable '__ZTV15IGAccelResource' is malformed. Make sure your kext has been built against the correct headers.

Oh, good point. I tried that just now (before downgrading to the Mavericks kexts), but it didn’t change anything, except that with the altfb SSDT-1.aml I get the problem with the invisible first login screen even when the monitor is set to DP 1.1. So reverting to the regular SSDT-1. Now for the...

A resolution of 3840 x 2160 @ 59 Hz defined with SwitchResX also shows up as “not active – invalid?” Intel specifies a maximum resolution of 3840 x 2160 @ 30 Hz over DisplayPort and 1920 x 1200 @ 60 Hz over HDMI. The ASUS PB287Q monitor can be switched between DisplayPort 1.1 and 1.2, but that...

Exactly. I now have my D54250WYKH running 10.10.4 using MiniHack’s guide with a Macmini7,1 SMBIOS based on your SMBIOS settings: Note that I’m using a CK7wwrrrG1HV serial, based on a real number found on Craigslist, as the CK2wwrrrGCVH you suggest is not recognized by any of the lookup sites...