lasasrescue.blogg.se

1. #DSDT EDITOR WINDOWS 8.1 INSTALL#
2. #DSDT EDITOR WINDOWS 8.1 DRIVERS#
3. #DSDT EDITOR WINDOWS 8.1 DRIVER#
4. #DSDT EDITOR WINDOWS 8.1 CRACK#

#DSDT EDITOR WINDOWS 8.1 DRIVERS#

It does appear that both drivers seem to make an incorrect assumption that the display will be on pipe 0. Lo and behold, as soon as they load up, the screen goes off in exactly the same way. At the time, only Ubuntu 12.10 and Mint 14 have support for HD4000 out of the box.

#DSDT EDITOR WINDOWS 8.1 INSTALL#

Windows has no such issues, so i thought i would give a Linux install a go, seen what happens. So from this I can conclude, that its sending the displayport signal down pipe 0 which is physically the VGA output, and the VGA signal down pipe 1 which is the display port output. the resulted in the internal display suddenly coming to life! sadly, it was the garbled VGA display pipe I was seeing.

I’ve tried swapping the devices around and it doesn’t fix my issue.īut, from here i can see that the VGA uses AAPL,DisplayPipe 01 00 00 00.įor my next experiment, I decided to edit out the internal display 0406, and just try and run on VGA only. It’s worth noting that the first entry is always seen as ‘built-in’. So with that change made, it made no difference to the output on both screens, even though both displays are now detected. I’ve found the tables in the file by searching for ‘05006201’ and changed the entries to that the first port so 0602 (VGA) the second is 0406 (DisplayPort) and the third is 0304, which i think is HDMI, i just shuffled it there to fill up the space.

#DSDT EDITOR WINDOWS 8.1 DRIVER#

The Apple driver has VGA support, but its not enabled in any of the Platform IDs, which means i needed to edit the file with a Hex Editor for the platform ID i am using.

#DSDT EDITOR WINDOWS 8.1 CRACK#

So I plugged a monitor into this port to see what happened, and as soon as the display enables, garbage is output onto the VGA screen! The reason for this, I can only assume, is that display pipe 00 00 00 00 is actually the VGA port, not the internal display, and its garbled because its sending the wrong signal type, DisplayPort.īy searching around the internet, and thanks to various hackintosh folks around the forums eep357, toledo, bcc7 et al, i’ve been able to crack on with some tests. The only other output port available on this All-in-One is, oddly, VGA. It seems that the driver outputs the display on AAPL,DisplayPipe 00 00 00 00 which is where it expects the display on port 04 06 to be. Instead my problem is that the display IS detected, but the output to the panel isn’t being activated. It normally ends with a post saying ‘i fixed it by injecting this string (which actually injects the correct platform id) or “i ended up using chimera 1.11.something” (which again actually just injects the correct platform id). There are many posts around the internet from people having no display, but this almost always turns out to be people not using the correct platform id on their laptop. which at the time of updating, it every version. The problem exists in the following versions so far… This has nothing to do with the Intel HD4000 Graphics kext it seems, instead it the AppleIntelFrameBufferCapri.kext.

So despite my efforts so far, i’m plagued by this problem of the screen going blank when the Intel HD 4000 Framebuffer driver loads.