I am new, I hope I am posting in the correct forum.
My specs: Processor: Core i5 6500 Skylake 3.2ghz
Mobo: Gigabyte h170-d3h
M2SSD: WD Black 256gb PCIe (Mac OSx)
SSD: Samsung 860 Evo (WIndows 10)
HDD: WD Blue 1TB
GPU: Radeon RX 480
Monitor: BenQ RL2460 24"
I was able to install High Sierra on a new m2 drive, that I added to the above configuration with windows 10 already installed.
I had a few issues during install, including the monitor turning off at boot screen.
Unfortunately, this persists even now. It turns off at about 60% of the progress bar, and to turn it on again I have to unplug/plug back my hdmi.
Additionally, while all of the usb ports worked during install and while running it out of the clover I had on the usb stick, only the rear ones appear to work now.
The audio doesn't work either, though I added the correct patch according to my mobo
Lastly, my other drives are not recognized in the bios anymore. They run fine from boot override but they don't show up in the boot priority (while multiple entries of mac OS do, and they seem to increase in number at every reboot)
Hi, I wanted to install macOs 10.13 on my notebook. Here are the technical specifications:
-Intel i7 6500U 2.50GHz Skylake (CPU)
-12GB ram dd4 (RAM)
-hp 81EC (MOTHERBOARD) with BIOS insyde F09
-Intel HD Graphics 520 - AMD Radeon R7 M440 (Graphics cards)
-Realtek PCIe FE Family Controller (Ethernet)
-Broadcom BCM43142 802.11 bgn Wi-Fi M.2 Adapter (Wifi and Bluetooth)
-Realtek High Definition Audio - Audio Intel® per schermi(HDMI)
After successful Sierra 10.12.6 install, the internal display is not recognized post boot. However, external display through HDMI works fine. Trying to use Intel 630HD graphics. The internal display works when booting with 0x123456789 as Fake ID but not when using ig-platform-id of 0x59120000 and no Fake ID. SMBIOS is MacBook Pro 14,3. Thanks in advance.
I have a Mac Mini 2006 (upgraded) with Intel GMA950 graphics, running MLPostFactor 10.8.5. It is connected to an ASUS VS197 LCD panel using DVI-D. This is natively a 1366x768 panel that is recognized and works fine.
However, the other choices for resolution are 4:3 800x600 and 1024x768, and then the oddballs 832x624 and 1360x768. None of these are useful as a low-resolution widescreen for gaming or watching DVD content. Specifically I want to get access to 848x480 or 854x480, and also 1024x576. SwitchResX makes these choices available, but it doesn't work with a "full screen" game, presumably because the game directly queries OSX Display to get a list of valid resolutions and SwitchResX is bypassing that system instead.
So the solution is obvious: buy a new computer pull the monitor's EDID data, hack it to enable new resolutions, and then tell OSX to use this custom EDID instead of the one retrieved from the monitor.
Following the steps of the EDID injection guide, here is where I am:
* Retrieve EDID, DisplayVendorID etc from ioreg.
00 FF FF FF FF FF FF 00 04 69 F2 19 24 94 00 00 31 16 01 03 80 29 17 78 EA F5 45 A4 55 50 9E 27 0F 50 54 BD EE 00 81 C0 01 01 01 01 01 01 01 01 01 01 01 01 01 01 66 21 56 AA 51 00 1E 30 46 8F 33 00 9A E6 10 00 00 1E 00 00 00 FD 00 32 4B 18 53 11 00 0A 20 20 20 20 20 20 00 00 00 FC 00 41 53 55 53 20 56 53 31 39 37 0A 20 20 00 00 00 FF 00 43 43 4C 4D 54 46 30 33 37 39 32 34 0A 00 F1
* Use an EDID editor to enable new 848x477 and 1024x576 resolutions. (Verify with an online EDID tool, and compare to the previous version)
00 FF FF FF FF FF FF 00 04 69 F2 19 24 94 00 00 31 16 01 03 80 29 17 78 EA F5 45 A4 55 50 9E 27 0F 50 54 BD EE 00 81 C0 4B C0 4B CA 4B CF 61 C0 61 CA 61 CF 01 01 66 21 56 AA 51 00 1E 30 46 8F 33 00 9A E6 10 00 00 1E 00 00 00 FD 00 32 4B 18 53 11 00 0A 20 20 20 20 20 20 00 00 00 FC 00 41 53 55 53 20 56 53 31 39 37 0A 20 20 00 00 00 FF 00 43 43 4C 4D 54 46 30 33 37 39 32 34 0A 00 47
* Create a new subfolder and plist within /System/Library/Overrides/Display/ containing the new EDID string and monitor name.
Now the problems begin. Even though the plist file is being read (which I know because the Monitor Name has changed in Displays), the custom EDID is not being used. When I dig into IORegExplorer I am able to come up with AAPL00,EDID string and it is the unmodified one read from the monitor. I even tried a plug-and-unplug while OSX is running, and also tried to reset the SMC and NVRAM, but no dice.
Do I need to start digging into DSDT hacking? Is the Intel driver pulling down EDID during boot and I need to override it somewhere else? What am I missing here?
I got a very odd problem after updating to 10.12.5 and I'll try explaining it to the best I can along all troubleshooting I did...
I have a Macbook Pro retina 13" (early 2015) that I've always used with two Samsung external monitors (both are the same model). One of them is connected directly through the HDMI port located on the right side of the Macbook Pro, the other one connected through a thunderbolt-to-HDMI cable. It has always worked until last week when I updated to 10.12.5.
After the update, I quickly noticed that my Macbook Pro wouldn’t detect any external display via thunderbolt-to-HDMI. Thus, I started a long process of troubleshooting, and here’s all I’ve tried:
Assuming it could have been a defective cable, I’ve tried 3 different ones, still no luck
I’ve tried both thunderbolt entry, still no luck
I’ve tried thunderbolt-to-VGA, it WORKS, yes, I know this is insane.
I’ve tried to connect thunderbolt-to-HDMI (still with all 3 cables) on older Samsung monitors (again two older monitors were the same model, it was my old setup)… it worked
Then, I assumed it was the Samsung monitors that were broken (the two of them at the same time…? Odd, isn’t it?). Thus, I tried to connect them on my mac mini, the same way I always did on my Macbook pro… And it works…
Then I tried to reproduce the problem on my mom’s Macbook Pro retina 13” (exact same model I have the problem with and same update)... It works
Then I assumed the problem must be coming from my Macbook Pro. Thus, I booted on Windows 8 (bootcamp), it works.
Starting to lose my mind… I booted from an external hard drive I have (running an early sierra version), it didn’t work either (I had used this external hard drive in the past and it was WORKING)
I've done a factory reset, still not working
EDIT (forgot to mention):
SMC, no luck
NVRAM, no luck
So in a nutshell, the problem seems to appear only via thunderbolt-to-HDMI, only on this specific Macbook Pro, and specifically on macOS.
I’m no expert and I don’t know what else I can do. Of course I've tried contacting Apple many times but they keep blaming me for updating my mac and/or Samsung for making the environment not compatible, which I believe is a total nonsense.
Has anyone encounter any similar problem? Does anyone know what it could be?
I’m desperate so I’d like to thank y’all in advance for your help.