Jump to content

Search the Community: Showing results for tags 'display'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • InsanelyMac Lounge
    • Front Page News and Rumors
    • Reader News and Reviews
    • Forum Information and Feedback
  • OSx86 Project
    • New Releases and Updates
    • New Users Lounge
    • Developers Corner
    • Tutorials (The Genius Bar)
    • Technical FAQ
    • Installation
    • Post-Installation
    • DSDT and SSDT
    • Hardware Components and Drivers
    • Desktops
    • Notebooks
    • Netbooks
    • Tablets
    • MacMod of the Month
    • Multi-booting and Virtualisation
  • International
    • Your Language
    • Deutsch
    • Español
    • Français
    • Italiano
    • Português
    • Русский
  • Apple World
    • Mac OS X
    • Apple Computers and Hardware
    • iOS Devices
    • Mac Applications
    • Mac Programming and Development
    • iOS Programming and Development
    • Mac Gaming
    • Mac Accessories
  • Discuss and Learn
    • Windows Discussion
    • *nix
    • Apple Opinions and Discussion
    • The Great Debates
    • Internet(s), Servers, and Networks
    • Buying Thoughts, Reviews, and Recommendations
    • Mods and Overclocking
    • The Big Issues [Real Life]
  • Everything Else
    • Creativity
    • Thunderdome (Random Stuff)
    • Laughs
    • The Marketplace


  • Kexts
    • Graphics Cards
    • Audio
    • LAN and Wireless
    • Other
  • Kernels
  • Bootloaders
  • DSDTs
    • Patches
  • Pandora
  • Apps
  • Miscellaneous
  • Customization

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Website URL







Found 31 results

  1. My rig is working great driving a single display from Vega 64 via DisplayPort, but I'm having a devil of a time getting a TV monitor working via HDMI on the same card. My TV lights up an input icon when I plug it to the Vega (see attached--notice the next port w/ nothing plugged in is grayed out). So I know some electrons are flowing (maybe EDID?), but it never gets a signal. I've tried several HDMI 2.0 cables. I'm running a vanilla install of 10.14.6, as iMac19,1, with just Lilu (1.3.8) + Whatevergreen (1.3.1). System recognizes the Vega and seems to be correctly using the UHD630 headlessly. I just can't get HDMI out of the dGPU... I've tried the "-raddvi" and "agdpmod=vit9696" boot args, no dice. I've tried the kext patch workaround for disabling board verification, also no go (not surprising as I think that method is now obsolete for my setup). I hit the same wall running 10.14.2 as iMac18,3 with a different platform-id before updating. Here's my whole EFI. Any assistance at all is hugely appreciated!! Thanks y'all.
  2. Hello there, here is my spec: Asus 15" K73sv 1600x900 internal screen is completely destroyed i5 Sandy 2410M NVidia 540M 1GB Display output via HDMI & VGA Using 10.9.3 and latest Chameleon (78) No custom DSDT ---------------------------------------- I have really strange display issues. When I connect a display via HDMI everything just works perfect and I can use a resolution up to 1080p on my BenQ. Put I'am setting this Asus up for a friend and he only got a VGA Screen with a reso auf 1600x1050. When I connect the laptop via VGA the screen is stretched and flickering like hell. This does not appear with a HDMI display. After I started looking where the problem is coming from I noticed that in the systemsettings the external monitor is listed as an internal so I can set a maximum resolution of 1600x900. While the bootloaders GUI is shown in the native resolution of 1600x1050 but as soon as the loading sun disappears the resolution is setted to 1600x900. So there are different ways to help me. First thing will be to set the internal resolution easily to 1600x1050 or say the bootloader to load the whole system in this resolution. Second thing is to get the 540M fully functional (what is impossible i think?). Third thing would be loading a custom EDID into the system. (I could extract the EDID via VGA with a other Mac) Here is the EDID from the external screen extracted with the Asus and the screen is clearly listed as "AppleDisplay": ioreg -l | grep -5 IODisplayEDID | | | | | { | | | | | "IOClass" = "AppleDisplay" | | | | | "CFBundleIdentifier" = "com.apple.iokit.IOGraphicsFamily" | | | | | "IOProviderClass" = "IODisplayConnect" | | | | | "DisplayProductID" = 721 | | | | | "IODisplayEDID" = <00ffffffffffff0030e4d1020000000000140103802615780a88a59d5f579c261c5054000000010101010101010101010101010101012f2640b860840c30303023007ed710000019000000000000000000000000000000000000000000fe004c4720446973706c61790a2020000000fe004c503137335744312d544c4e32002b> | | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/GFX0@2/AppleIntelFramebuffer@0/display0/AppleDisplay-30e4-2d1" | | | | | "IOPowerManagement" = {"MaxPowerState"=3,"CurrentPowerState"=3} | | | | | "IOProbeScore" = 2000 | | | | | "IODisplayParameters" = {"bgsc"={"min"=0,"max"=65536,"value"=65536},"rgsc"={"min"=0,"max"=65536,"value"=65536},"bklt"={"min"=0,"max"=1808,"value"=0},"ggsc"={"min"=0,"max"=65536,"value"=65536}} | | | | | "IOMatchCategory" = "IODefaultMatchCategory" Thanks to everyone who read my rock of a post
  3. Hey, I'm developing an application which frequently handles low resolution bitmaps. I often want to display a very small image (Let's say 12x12 pixels) on a much larger surface (Let's say 480x480) so the user can see every individual pixel. I use [context setImageInterpolation: NSImageInterpolationNone] to disable bilinear/bicubic filtering, which works great on normal displays. However, when using HiDPI mode, OS X first scales 12x12 to 24x24 using (what appears to be) bilinear, and then 24x24 to 960x960 using nearest neighbor. This is an unwanted result since I get 4 blurry "pixels" instead of one. How can I stop OS X from filtering my bitmaps? I attached an image explaining the issue. Thanks in advance!
  4. I have a samsung NP530U3C extract DSDT by clover and made the edit following the guide https://www.tonymacx86.com/threads/guide-patching-laptop-dsdt-ssdts.152573/ I also did following this guide https: // www. tonymacx86.com/threads/fixing-brightness-with-custom-edid.219413/ the fix of my EDID and followed the guide to put the brightness to work https://www.tonymacx86.com/threads/guide-laptop-backlight -control-using-applebacklightinjector-kext.218222 / I have the brightness to work but I have a problem in the screen I leave the image to see the problem. Clover + IOREG + kextcache -i https://ufile.io/z61kh
  5. Hi all. I have a Lenovo Ideapad Y510p that runs with Intel HD4600. I found there is a big problem with IGPU driver initialisation/re-initialisation and was hoping some of you who have experience with drivers and graphic can help me out. Problem description If I started the system with Legacy support disabled in BIOS (i.e. UEFI-Only / CSM-OFF), the whole system boots fine. Whenever anything causes display off/on (like change resolution, connect external display, set display to sleep, or set system to sleep) then On while using OS X, something big change with graphics. At this event there is no symptoms visible inside OS X but once I choose to reboot display goes off (part of any reboot process) but never wakes. Therefore, Lenovo logo is not visible, so is Clover bootloader (while functioning), the same is for any OS I choose to boot to (blindly). I was able to force the display to wake again by re-initialising GFX once I am inside operating system using this trick: For OS X, I turn the display Off then On (Ctrl+Shift+Eject) ... or set the system to sleep then wake it For Windows I set the system to sleep then wake it. The next figure shows the process and I hope it make the problem clearer. I want to note that shutdown is not affected since UEFI will initialise the graphics correctly on cold boot. Now if I started the system with Legacy support enabled in BIOS (i.e. UEFI + Legacy / CSM-ON), the whole system boots fine too. But there is no need to turn display OFF then ON to test the change with graphics while in OS X. Once I choose to reboot display goes off but never wakes and all the other consequences happens as with the other case. Other things I tried that replicates the same issue: Booting the system (regardless of CSM mode) while having CsmVideoDxe-64.efi installed with Clover. The system boots with blinking cursor and no GUI for clover but still functioning and I am able to boot OS X blindly. Once I boot OS X I make the trick above to re-initialise GFX then display is back On but reboot is flawed. Booting the system (regardless of CSM mode) while having PatchVBios=true set in config.plist. The system boots with no display no GUI for clover of course but still functioning and I am able to boot OS X blindly. Once I boot OS X I again make the trick above to re-initialise GFX then display is back On but reboot is flawed. I understand that both CsmVideoDxe-64.efi driver and PatchVBios setting have their own purpose but it is still interesting to see how they can trigger the problem by their own. Experimenting with Intel Registers: The first thing I tried while investigating is to dump and analyse Intel GPU Registers. I dumped the registers using AppleIntelInfo in four situations: While booting in UEFI-Only / CSM-OFF mode (before IGPU is re-initialised) While booting in UEFI-Only / CSM-OFF mode (after IGPU is re-initialised) While booting in UEFI+Legacy / CSM-ON mode (before IGPU is re-initialised) While booting in UEFI+Legacy / CSM-ON mode (after IGPU is re-initialised) And the following results are what I found: These registers will always change (even on different boots with the same configuration) so I guess they are not relevant: AICPUPMI: InitialTSC AICPUPMI: IA32_MPERF AICPUPMI: IA32_APERF AICPUPMI: IA32_THERM_STATUS AICPUPMI: MSR_PKG_ENERGY_STATUS AICPUPMI: MSR_PP0_ENERGY_STATUS AICPUPMI: MSR_PP1_ENERGY_STATUS AICPUPMI: MSR_PKG_C2_RESIDENCY AICPUPMI: MSR_PKG_C3_RESIDENCY AICPUPMI: IA32_TSC_DEADLINE DSPASURF RC6_RESIDENCY_TIME UEFI-Only-Before vs. UEFI-Only-After, the following additional registers will change: DP_TP_CTL_A DDI_BUF_CTL_A UEFI+Legacy-Before vs. UEFI+Legacy-After, no additional registers changes! UEFI-Only-Before vs UEFI+Legacy-Before, the following additional registers will change: DP_TP_CTL_A DDI_BUF_CTL_A BLC_PWM_CPU_CTL2 BLC_PWM_CPU_CTL UEFI-Only-Before vs UEFI+Legacy-After, the following additional registers will change: DP_TP_CTL_A DDI_BUF_CTL_A BLC_PWM_CPU_CTL2 BLC_PWM_CPU_CTL UEFI-Only-After vs UEFI+Legacy-Before, the following additional registers will change: BLC_PWM_CPU_CTL2 BLC_PWM_CPU_CTL UEFI-Only-After vs UEFI+Legacy-After, the following additional registers will change: BLC_PWM_CPU_CTL2 BLC_PWM_CPU_CTL Before this becomes messy, I want to note that the only case that IGPU are fine is UEFI-Only-Before. This means the question is why the other cases have differences/changes in registers. we have four registers to look at: DP_TP_CTL_A DDI_BUF_CTL_A BLC_PWM_CPU_CTL2 BLC_PWM_CPU_CTL Let's start with the last two of them BLC_PWM_CPU_CTL2 and BLC_PWM_CPU_CTL. Their values are different based on the boot mode. That is, these two registers will have a specific values if we boot in UEFI-only mode and other values if we boot in Legacy support mode but in both cases the registers values does not change on IGPU re-initialisation. Therefore, I believe they are not much relevant but they serve as evidence that OS X initialise IGPU differently depending on CSM mode in BIOS. The other two registers are DP_TP_CTL_A and DDI_BUF_CTL_A. These two registers change once IGPU is re-initialised if we boot in UEFI-Only mode and the change in these registers are: DP_TP_CTL_A : 0x80040300 -> 0x80040340 DDI_BUF_CTL_A : 0x80000003 -> 0x80000013 If we boot in Legacy support mode, however, we find that these registers are already set to the wrong values right from the start. That is on cold boot while Legacy support enabled in BIOS, DP_TP_CTL_A = 0x80040340 and DDI_BUF_CTL_A = 0x80000013. In this scenario, no matter how many times IGPU is further re-initialised these two registers will not change anymore. So the conclusions here is: OS X initialise IGPU differently depending on whether BIOS enables CSM or not. This is visible through the values of the two registers BLC_PWM_CPU_CTL2 and BLC_PWM_CPU_CTL. Whenever DP_TP_CTL_A = 0x80040340 and DDI_BUF_CTL_A = 0x80000013, the system will restart with display off and reproduce the issue presented above. So I would name the initialisation that led to this an incorrect initialisation. OS X initialise IGPU incorrectly while in CSM-ON mode with wrong values assigned for DP_TP_CTL_A and DDI_BUF_CTL_A registers. If OS X booted in CSM-OFF mode and IGPU is re-initialised, the values of the two registers DP_TP_CTL_A and DDI_BUF_CTL_A will change to match their values in CSM-ON case (which are wrong according to 3). We need to find the reason why the two registers DP_TP_CTL_A and DDI_BUF_CTL_A are initialised incorrectly for CSM-On mode (this will affect IGPU re-initialisation while on CSM-OFF mode). Let’s start with DP_TP_CTL_A which have a value that corresponds ‘good-mode’ is 0x80040300. This value changes on ‘bad-mode’ to 0x80040340 which means a single change to the bit number 6 for this register. This bit changes from 0 to 1 and according to Intel PRM it is defined as: Moreover, the PRM states that value 0 for this bit means disabled while 1 for enabled. So on IGPU re-initialisation, the IGPU driver accidentally enable DisplayPort Alternate Scrambler Reset which should not happen. Now with the other register DDI_BUF_CTL_A that have a ‘good-mode’ value of 0x80000003. This value changes on ‘bad-mode’ to 0x80000013 which means a single change to the bit number 4 for this register. This bit changes from 0 to 1 and according to Intel PRM it is defined as: Moreover, the PRM states that value 0 for this bit means ”DDI A supports 2 lanes and DDI E supports 2 lanes” while 1 means “DDI A supports 4 lanes and DDI E is not used”. So on IGPU re-initialisation, the IGPU driver accidentally switch DDI A support to 4 lanes and disables DDI E which, again, should not happen. I also read from the PRM that the questionable bits in both registers should not be changed manually. I can deliberately change the values via ACPI but I tried this before on other IGPU register and it didn't work (the register did changed but display went out). Therefor, I was wondering if there should be something to fix the registers at boot-time (fixing the cause of course). We had a problem before with colour gradients that occur as well after IGPU re-initialisation (or if boot in CSM-ON mode) and resulted in an incorrect change to the register PIPE_DDI_FUNC_CTL_EDP. It was found that using a custom EDID was enough to fix the visible symptoms and also prevent the infected registers from change incorrectly. So this is what I found so far ... I will keep searching and trying things but was hoping to get any help. I am attaching a copy of Intel registers dump for all four cases discussed above for reference. Thanks in advance. Intel Registers Dump.zip
  6. Hello! I'm Italian, so I'm sorry if my English is not good. I have a Toshiba C660 and I installed OS X Mavericks using the retail distro. I successfully got almost everything to work except for iMessage, my Bluetooth and my display brightness (most annoying problem). I have no slider for brightness in the preference panel. I know I should create my DSDT but I always fail on it. Could you please help me?
  7. The display sleep does not work correctly. Starting with Mac 10.12.4, the display sometimes does not wake up. The backlight works, there is no image, a black screen. Currently installed 10.14.1. All the same. If the display is sent to sleep, then sometimes it can wake up in a black screen with a working backlight. From the description, it is not difficult to guess that the display sometimes wakes up correctly and sometimes wakes up in a black screen. In the course of the experiments, I also saw that the display sometimes woke up and showed the boot screen (the Apple logo and progress bar), a second after that the desktop appeared. This behavior occurs only when the display wakes up on a black screen and then I close and open the laptop cover again, after which the boot screen sometimes appears for a second, but sometimes nothing appears, the system just hangs. I hope I clearly described the symptoms of the problem. The screenshot was taken after the experiment. I sent the display to sleep, then woke it up. He woke up in a black image with burning lights. Then I closed and opened the laptop bucket, pressed the space bar and waited a few seconds. After a few seconds, the boot screen with the Apple logo appeared and then the desktop appeared. Immediately made a screenshot. Asus k501lb Intel HD 5500 Core i-5 5200U ( Broadwell ) Display: au optronics B156HTN03.8
  8. Hello all, I am getting prepared to build another hackintosh, and I have run into something that is puzzling me. I have 2 Western Digital My Book Thunderbolt Duo external hard drives that I've used for years with my MacBook Pro. It is my intent to begin moving away from using my MacBook Pro whenever I finish my hackintosh. As the title of this thread suggests, I am building a dual boot system with Win7 and OS X. I want to be able to use my external hard drives seamlessly between the two operating systems, but I'm having trouble finding a way that I can plug my drives into when the system is finally built(or perhaps I'm having trouble understanding the concept in its entirety). If you were not already aware, the My Book Thunderbolt Duo's I/O consists only of 2 thunderbolt ports on the rear for connection, no USB. And even if it did have USB ports, I wouldn't be able to daisy chain the two drives, as I do now, which is at the moment also daisy chained in with the monitor I'm using. So, is there anything I can buy(like a pci card or hub) that will allow me to plug my thunderbolt hard drives into my computer, that will give me full thunderbolt functionality between both operation systems? Once I get my hackintosh built, I'll be plugging the monitor into the gfx card(obviously), so thunderbolt storage is the main functionality desired. But if there is something out there that supports thunderbolt video and storage in a hackintosh like mine, don't neglect to let me know. Here is my pcpartpicker list: https://pcpartpicker.com/list/R2j2nn I am building a custom water loop for this hackintosh, so certain otherwise essential components may be left blank in this list. Thanks is advance!
  9. Hi all, I'm install Hackintosh 10.12.6, everything work fine but sometimes my screen appear some square (see the attachment). Anyone here can help me fix this ? My hack is: Core I5 - Sandybrigde Intel HD3000 Thanks.
  10. Hello, I installed El Capitan according to the guide at http://x220.mcdonnelltech.com on my Thinkpad x220. While the system runs mostly fine so far, I have the problem that the display exhibits a subtle but noticeable blinking/flickering. One example where this is clearly visible is the screenshot at https://upload.wikimedia.org/wikipedia/commons/f/f4/Twm-screenshot-20050401.png. The title bar of the xterm window (more specifically, the dotted bar right of the "xterm" label) flickers on my X220 LCD on Mac OS X. There's no flickering when displaying the same screenshot on Linux. I thought this could be somehow related to the refresh rate. I tried the "cscreen" utility (http://www.pyehouse.com/cscreen/), which shows a refresh rate of 0. When trying to change it, nothing happens (no apparent change in behaviour, cscreen still shows "0") It also seems I'm not alone with this problem. The author of the aforementioned x220 guide could reproduce the behaviour on his x220. User "janohan" at He-Who-Must-Not-Be-Named seems to have a similar problem (topic "Blinking screen elements - low refresh rate?"). Any ideas what could be the cause for this behaviour? Has anybody else have a display flickering problem like that on their hackintosh? Any hints greatly appreciated I suspect this must be somehow related to the graphics driver? Is there any other component besides the graphics driver which could be responsible for this behaviour? Could this be the backlight? (in what extent does the operating system control the backlight?)
  11. UPDATE Hm sorry I forgot to update this topic. This tutorial works only in 10.8 here on my hackintosh. I have read that some people made it work in 10.9, but only with Intel's intergrated GPU. Cheers -------------------------- Hi. Excuse me for my English. I'm trying to make it simple. 1, Prepare SwitchResX, PlistEdit Pro and IORegExplorer. SwitchResX is not a must but I recommend it. 2, Enable HiDPI if you haven't done it sudo defaults write /Library/Preferences/com.apple.windowserver DisplayResolutionEnabled -bool YES; sudo defaults delete /Library/Preferences/com.apple.windowserver DisplayResolutionDisabled; Log out and log back in if you'd like to be sure. Also works if you have Quartz Debug. 3, Extract EDID in SwitchResX. Or from IOReg as in Picture A. 4, In Terminal, run ioreg -l Use Edit - Find to get your DisplayProductID and DisplayVendorID. In my case, I got DisplayVendorID = 14499 DisplayProductID = 26609 You also need to find IODisplayPrefsKey but it would must easier to get that in IOReg, as shown in Picture A. In my case I got this IODisplayPrefsKey = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PEG0@1/IOPCI2PCIBridge/PEGP@0/ATY,Ipomoea@0/ATIFramebufferNI/display0/AppleDisplay-38a3-67f1 Hence the value: AppleDisplay-38a3-67f1 5, Create a folder on the desktop and name it DisplayVendorID-****. In my case it was DisplayVendorID-38a3 And then create a blank text file named DisplayProductID-***. In my case it was DisplayProductID-67f1 Use the Get Info panel to make sure this text file HAS NO EXTENSION. 6, Edit this DisplayProductID-*** file in PlistEdit Pro. Add the following children and edit their values with your own DisplayProductID DisplayVendorID and EDID data. <key>DisplayProductID</key> <integer>****</integer> <key>DisplayVendorID</key> <integer>****</integer> <key>IODisplayEDID</key> <data> **** </data> In my case, it was like <key>DisplayProductID</key> <integer>26609</integer> <key>DisplayVendorID</key> <integer>14499</integer> <key>IODisplayEDID</key> <data> AP///////wA4o/FnAQEBAQYWAQOAMBt4KpLFollVnicOUFS/7wCBQIGAlQCzANHAAQEB AQEBAjqAGHE4LUBYLEUA3QwRAAAeAAAA/QA4Sx5QEQAKICAgICAgAAAA/ABWRTIyMDFY RwogICAgAAAA/wAyMjExMTUzME5DCiAgAFM= </data> 7, To add your custom resolution, create a new child like this <key>scale-resolutions</key> <array> </array> And add a new sibling <data></data> 8, Convert your custom resolution with a Hexadecimal Converter/Decimal Converter My GPU supports 2560 x 1600 max. My display supports 1920 x 1080 max. So I will need 2560 x 1440 for retina. 00000A00 000005A0 00000001 00000A00 = 2560 000005A0 = 1440 00000001 This one doesn't really matter. I also added 1366 x 768 because I could not stand 1360 x 768 provided by OS X. 00000556 00000300 00000001 Someone with 780 SLI or 7990 Cross-Fire may set 3840 x 2160 for 1920 x 1080 HiDPI. lol Therefore, in your PlistEdit Pro it should look similar to mine: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>DisplayProductID</key> <integer>26609</integer> <key>DisplayVendorID</key> <integer>14499</integer> <key>IODisplayEDID</key> <data> AP///////wA4o/FnAQEBAQYWAQOAMBt4KpLFollVnicOUFS/7wCBQIGAlQCzANHAAQEB AQEBAjqAGHE4LUBYLEUA3QwRAAAeAAAA/QA4Sx5QEQAKICAgICAgAAAA/ABWRTIyMDFY RwogICAgAAAA/wAyMjExMTUzME5DCiAgAFM= </data> <key>scale-resolutions</key> <array> <data> AAAKAAAABaAAAAAB </data> <data> AAAFVgAAAwAAAAAB </data> </array> </dict> </plist> 9, Copy your DisplayVendorID folder to /System/Library/Displays/Overrides Now you can take a look in SwitchResX. Your custom resolutions should show up as "scaled" and "system-inactive". If you don't have SwitchResX it doesn't matter either. Restart and voila! Picture B Picture C Do NOT try to choose 2560 x 1440, though. You will get a white screen or worse. Choose 1280 x 720 HiDPI instead. Note: A. Some other tutorial shows how to add custom resolutions with Switchres and Quartz Debug. It seems for laptops only. I was unable to add resolutions on my Hackintosh. Instead I got irrelevant DisplayVendorID folders in /System/Library/Displays/Overrides . Make sure you delete these folders before applying this tutorial. B. I have not tested it with multiple displays, laptops or even TV. It is possible to be the same and, following this tutorial, you can add multiple EDID profiles to /System/Library/Displays/Overrides C. Known issues: Lag a tiny bit when switching spaces. Also white screen for less than a second after logging in but before your retina desktop shows up. But it works fine on my Hackintosh now. D. Do tell me if it would burn your GPU when you play games. lol A lot of thanks to Apple, Steve, Hackintosh hackers, this forum, and especially authors of these two posts http://www.insanelymac.com/forum/topic/208410-fixing-scrambledstretched-or-wrong-resolution-laptop-display-problems/ Fixing Scrambled,Stretched, or Wrong Resolution Laptop Display Problems http://www.insanelymac.com/forum/topic/281412-how-to-advanced-edid-injection/ HOW TO: Advanced EDID Injection Ciao Henry Pentium G840 Gigabyte H61M-DS2 rev.2.2 F8 Samsung DDR3 1600 4G MSI R6670-MD2GD3v2 Hitachi 320 GB (WIN 7 X86 SP1) Seagate 500 GB (10.8.4) NEC VE2201XG Display 1280x720 HiDPI
  12. hi all, looking for help regarding a weird display problem I have three displays connected to my hackintosh (1x dvi, 1x hdmi, 1x displayport). all three work fine - except when I wake the computer from sleep: then all of a sudden the third one, which is my main display, is using the wrong refresh rate (37 hz according to the display's on-screen-menu, instead of the usual 60 hz). the result is sluggish behaviour of everything that's on that display. the other ones are fine. the only thing that helps to solve the issue is a reboot. what I tried to fix the problem: graphicsenabler=yes/no several framebuffer personalities using different ports (though I only got all three displays working when using 1x dvi, 1x hdmi and 1x displayport) search the forum my hardware: ati 5870 asus p8p67 pro software: ML 10.8.2 edit: the display that has the issue is connected via displayport. any is help greatly appreciated n.
  13. Hi all, Having some trouble with fitting my 10.9 install to my monitor. Currently, I have Windows 7 set to 2560 x 1440 when running Workstation 10.0.3. Configuration is currently as follows: Virtual Machine > Display: Auto detect, 3D graphics acceleration disabled, use host setting for monitors. 10.9 guest > Displays: Resolution set to Scaled 1600 x 1200 Workstation > View: Console View enabled, Autosize: Autofit Guest and Autofit Window selected. Problem is both 'Fit Guest Now' and 'Fit Window Now' options are disabled (grey). The VM will only show at 1600 x 1200 without having to scroll, but will show up to 2360 x 1770. How can I set this to fill the available black space in Workstation? Thanks. Jeremy.
  14. I have an odd issue - basically, if I disconnect the display, the computer stays on and is working normally. When running without display connected, it reports the display to be "internal display", which I guess is to be expected. However, when I re-connect the display to the computer, it crashes. I tried the same thing under Windows on the same computer where it works fine, so it seems to be some OS X issue. An interesting thing is that if I connect with Screen Sharing to the computer from another mac and leave that running when unplugging / replugging, everything works fine. I suspect there is some issue with reconnecting a display when it's the only display output there is. I'm running an AMD 290X GPU, but I don't think that's the problem as I get the same behavior on all ports, and also on the IGPU (HD4600). Also, the system.log shows no entries at all when the crash happens. Has anyone else had this problem, or got any suggestions or where to start looking? I have tried some minor things like changing system definition, set internal display resolution to same as the screens, tried hotkey for detecting displays when replugging monitor and such, but no luck so far. Any ideas?
  15. I managed to install OS X after some problems, but the maximum resolution I can set is 1024 x 768, and, in "About This Mac" it says I only have 3 MB display graphics memory. I actually have 2 Sapphire R9 290s, which each have 4 GB memory, so what's the problem here, and how can I fix it? Thanks,
  16. Hey there So I managed to do a vanilla install of 10.14 on my new machine. I have 2 exact same displays hooked up to my ASUS STRIX RX470 8G. Display 1: connected via HDMI Display 2: connected via DVI to HDMI cable Display #1 works perfectly fine, but display #2 has a really ugly pink/ magenta tint to it. In Clover (in fact even in the first half of booting) the second display has the colors just right. Then, my screen glitches/ flashes for a second The display #1 continues to work properly, #2 turns pink. Any help would be very much appreciated!
  17. Alexandru

    Serious colour banding

    Hello InsanelyMacForum, I managed to boot into Mac OS Sierra with my Intel Core 2 Duo, Nvidia 9400 GT and 4 GB of Ram machine, got internet and sound working, but the issue appears when I boot with Nvidia Web Driver. I get these acid colours, but Graphics Acceleration is working fine. I tried to inject EDID from my display, but no results as well. Would be really grateful if someone could provide some help. Thank you!
  18. Does the DVI port work for anyone running Snow Leopard or Lion on Dell D630 laptop in a dock? I can use the VGA port just fine but I cannot use the DVI port for another monitor. I have tried both - 10.6.8 as well as 10.7.5. Is there a fix for this?
  19. I have a three-monitor hackintosh setup running on a GeForce GTX 660 video card. It's working just fine, and this problem is mostly just an aesthetics thing. I have a center monitor connected to HDMI and two side monitors on DVI. I was wondering if it was possible to force chameleon and OSX to boot onto the center monitor. Currently it's booting on the left DVI monitor.
  20. rongafni222

    Problem with two display!

    Hello, I have nvidia geforce 250 gts, i5,4gb ram and two display: philips 247el and 239cl. When i tried to connect the second screen with vga cable or dvi cable its stay in black screen and post the message on screen:"Check cable connection". I tried to use graphicsEnabler=Yes and No but its not working, also tried to install nvidia web driver and it stuck my computer. what can i do? thank you very much!!!!!!!
  21. Hey guys, I'm working on a Samsung serie 5 ultra hackintosh, and I can't get my built-in display to work in any way. I add some strings to my org.chameleon.boot.plist like: <key>HD4000PlatformId</key> <string>9</string> <key>device-properties</key> <string>5e0000000100000001000000520000000100000002 010c00d041030a000000000101060000027fff04002c000000 4100410050004c002c00690067002d0070006c006100740066 006f0072006d002d006900640000000800000003006601</string> Also tried with GraphicsEnabler Yes and No, same thing. And with these strings, I could get my graphics and acceleration to work, but only in a external display (HDMI). Could anybody give me a hand out? Thanks!
  22. Hi everyone, 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. Cheers
  23. I've been trying to figure this out for a while now, I'm open to any and all suggestions including re-installing Lion. So, I have Lion 10.7.3 installed and my Compaq NC6400 is hooked up to the docking station. With the laptop lid open I can use Dual Monitor no problem. I have set the external LCD as the primary so the Dock and Menu can be used from that display. If I try and enable Mirror, the display goes nuts and I have to manually delete the preferences file before I can boot properly again. So I'm trying to run the notebook lid closed and in the docking station and simply using the external monitor as an extended display. If I run the laptop this way the monitor does initialize, at the correct resolution, but nothing but a desktop background. No dock, no menu bar. So I tried enabling screen sharing so I could connect from my other Hackintosh and force it to move the display over, but it refuses to connect as if the other display is disabled or sleeping. I also notice if I run the notebook with display open I can hit the power button and it will prompt me if I want to shut down. But when the display is closed it won't respond. (Hitting power button will pop-up the shutdown message and activate the "Shut Down" button so all you have to do is hit enter.) Any suggestions? I'm not using a DSDT at the moment, but I'm not 100% sure it would help in this situation. Or maybe if someone had info on enabling video mirroring on the GMA950 without issues then I could use that approach.