Search the Community: Showing results for tags 'Web Driver'.
Found 3 results
doctorhackintosh posted a topic in nVidiaI have an ASUS GTX 750 Ti PH Series 2GB DDR5 (ASUS GTX750TI-PH-2GD5) with VBIOS 82.07.25.00.13 (or VBIOS 82.07.25.AS11). I have tried this card out on both Yosemite 10.10 and 10.10.1 with NVIDIA Web Drivers 343.01.01f01 through f03 and 343.02.01f01. I have 1xHDMI port, 2xDVI-D Dual Link and 1xVGA ports on the card. I have 1xHDMI and 1xVGA ports on my monitor Dell S2440L. The card is installed correctly and is detected in System Report > Graphics/Displays and even in NVIDIA Driver Manager's ECC tab (of course, ECC not supported though). While I have all ports functional in Windows and for my gaming needs, I'm not able to get any port to work with Yosemite. I get a blank screen with a 'No Signal' message on the HDMI and both the DVI ports with Yosemite, after the Apple logo boot screen or after NVIDIA Drivers have been loaded in verbose boot. I have tried 3 different HDMI cables and even a DVI2HDMI adapter. Apparently, VGA works on this card for a lot of people but I haven't been able to try it out. I have tried PCIRootUID=1 as one of the bootflags, as suggested in other solved threads in this forum for the ASUS GTX 750 Ti, but I get the same result. (i.e. No Signal). I have tried PCIRootUID=0, GraphisEnabler=No/Yes and all other sorts of boot flag permutations and combinations but NOTHING. My hackintosh works fine with the on-board Intel HD 4600 (1536MB VRAM) graphics (Motherboard: Gigabyte GA-B85M-D3H, supported as per the HCL). From my extensive discussions on other forums, I have gathered that this problem is not faced by cards sold by other vendors such as Palit, Gigabyte, EVGA, MSI - if any problems have been faced by these cards, they have been solved/fixed. The problem is mainly limited to ASUS cards, the ASUS Strix OC card with VBIOS 82.07.32.00.xx being the only exception which has even the HDMI port working. toleda analysed a bunch of IOREGs for us folks stuck with non-functioning GTX 750 Ti cards and he's ruled out any issue with the NVCAP or the framebuffers. The problem seems to be only with the ASUS VBIOS for every ASUS card except the ASUS Strix OC. Some people who have flashed the ASUS Strix OC VBIOS on their non-functioning cards have reported success in getting all the ports working. I personally am skeptical since the cards that have been experimented with as well as the ASUS Strix OC are bigger cards with two fans, while mine is smaller card with a single fan. I'm not sure if it'll be safe to flash my card with the ASUS Strix OC VBIOS because it obviously has a very different component layout/structure. I'm really at my wit's end and I would appreciate any inputs whatsoever. I'm attaching my card's VBIOS in case somebody can disassemble/analyse it to figure out exactly what is different between that VBIOS and the one on the ASUS Strix OC 750 Ti which can be found here. I have also attached my IOREG, NVCAP screenshots and a GPU-Z screenshot comparison of my card to an NVIDIA Reference 750 Ti. Can't the NVIDIA kexts be somehow edited to help recognise the non-functioning ports on these problematic ASUS cards & their baffling VBIOS? If you require me to provide any more information pertaining to my case, ask away; I'll upload ASAP. Any insight is appreciated? Help me solve this puzzle.
12,974 downloadsThis is a simple Applescript app that will back up the AppleGraphicsControl.kex to your desktop in a folder called KextBackUp. It will then patch the /System/Library/Extensions/AppleGraphicsControl.kext/Contents/PlugIns/AppleGraphicsDevicePolicy.kext/Contents/Info.plist and change "Config1" to "none" for the MacPro6,1 board ID. This ensures that your GPU will not be effected by the MacPro6,1's AMD FirePro device policy that causes your GPU not to send a signal to your monitor at boot. This app is only useful if you are using the MacPro6,1 system definition. Credit to PikeRAlpha: https://pikeralpha.wordpress.com/2014/05/01/os-x-mavericks-10-9-3-build-13d55-seeded/
Hello everyone! This is a new user to InsanelyMac, although I've built my Hackintosh long ago with the information on this forum But it seems like the problem I encountered has no solution posted here, I would like to share my solution to that. I have an i7 6700k, a GIGABYTE Z170 motherboard (though these two are not important at all in this problem), and a GTX970. I recently updated my Hackintosh from 10.11 to 10.13.1 (I think it should also work for 10.13) through App Store. The system was successfully installed, but I found that it was impossible to log in the system with my GTX970 plugged in -- it always led to black screen (no signal) before the login screen was shown. There are some discussion on InsanelyMac, but none of the solutions proposed worked for me. Here are my experiments: Since I am using iMac 15, 1 SMBIOS, I manually modified the AppleGraphicsDevicePolicy.kext so that it would not use the "Config2," or I can't even boot into the system with my IGFX (as we all know, it causes black screen / no signal before login). AppleGraphicsDevicePolicy.kext is NOT the cause of the problem in my case, although they have the same symptom; before using this solution, check your SMBIOS and AppleGraphicsDevicePolicy.kext. I also put Lilu.kext and NvidiaGraphicsFixup.kext in my Clover, but since they do the same thing as manually modifying Info.plist, I don't think it really matters here. In case of installing a broken Web Driver to my Hackintosh, I enabled SIP before the installation of Nvidia driver. It seemed like it worked: the first time I installed the Web Driver with SIP disabled, as well as after I accidentally removed a kext from /S/L/E and broke the driver, it produced a "gIOScreenLockState 3" problem. One of my guesses: the "gIOScreenLockState 3" is due to a broken or disabled (i.e. forgot to add NvidiaWeb in Clover config) web driver. NVwebDriverLibValFix.kext has no effect. It changed nothing but caused reboot before login when I was using IGFX. At last, I tried injecting a fake ID for Nvidia (0x00000000) and it WORKS! Go to "Devices" section in Clover Configurator (if you use it) and put 0x00000000 to "NVidia" in the "Fake ID" section, or modify the text of Config.plist like this: ... <key>Devices</key> <dict> ... <key>FakeID</key> <dict> <key>NVidia</key> <string>0x00000000</string> </dict> ... </dict> ... Then save, reboot. It should work if you have the same problem with me. Hope this help. If you have any question, leave a reply. I would be glad if I can help someone solve the problem.