ergot Posted September 3, 2017 Share Posted September 3, 2017 one thing I noticed although NVME is native on 10.13 the speed performance is lower than using patch. With patch I am getting higher R/W results than native support...is that something related to native drivers? Link to comment Share on other sites More sharing options...
alfaSZ Posted September 3, 2017 Share Posted September 3, 2017 So in other words this is just a different manifestation of the usual MacPro6,1 AGDP issue? I'll try booting with MacPro5,1 to check .. Possibly. Real empiricists test! I'm using iMac17,1 so I have the black screen issue after each update. Sent from my iPhone using Tapatalk Nope - no joy using MacPro5,1 to avoid the AGDP/black screen issue Link to comment Share on other sites More sharing options...
Cyberdevs Posted September 3, 2017 Share Posted September 3, 2017 Nope - no joy using MacPro5,1 to avoid the AGDP/black screen issue if you have black screen issue see this post Link to comment Share on other sites More sharing options...
alfaSZ Posted September 3, 2017 Share Posted September 3, 2017 if you have black screen issue see this post Thanks but what I really have is "WindowServer process keeps respawning" issue (during installation of dp6+) This was just a test to see if the two are somehow linked Link to comment Share on other sites More sharing options...
Cyberdevs Posted September 3, 2017 Share Posted September 3, 2017 Thanks but what I really have is "WindowServer process keeps respawning" issue (during installation of dp6+) This was just a test to see if the two are somehow linked Can you give me the link for your first post on the issue? I just want to know more about the issue. Link to comment Share on other sites More sharing options...
alfaSZ Posted September 3, 2017 Share Posted September 3, 2017 Can you give me the link for your first post on the issue? I just want to know more about the issue. Sure #3486 Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Cyberdevs Posted September 3, 2017 Share Posted September 3, 2017 Sure #3486 Sent from my iPhone using Tapatalk I'm sorry man I'm not sure what can be the cause for your problem. because there's no official nVidia web drivers for macOS High Sierra I haven't tested macOS High Sierra on my SkyLake machine which has a 1070 GPU. Link to comment Share on other sites More sharing options...
niknod Posted September 3, 2017 Share Posted September 3, 2017 hi niknod, I had the same problem, and I've solved it by patching DSDT and SSDTs, following RehabMan's guides: cheers! thanks sandro I was hoping I wouldn't have to fix dsdt and ssdts. I did disable gpu with DSDT reg fix but don't think thats enough.will have another go later cheers! Link to comment Share on other sites More sharing options...
sandro_desktop Posted September 3, 2017 Share Posted September 3, 2017 thanks sandro I was hoping I wouldn't have to fix dsdt and ssdts. I did disable gpu with DSDT reg fix but don't think thats enough.will have another go later cheers! I know it takes some patience, but it's the only effective method to solve the problem; and you don't need any other graphics kexts, like Lilu.kext or IntelGraphicsFixup.kext, nor you have to modify ig-platform-id; just patching dsdt and ssdts is required cheers! Link to comment Share on other sites More sharing options...
dehjomz Posted September 3, 2017 Share Posted September 3, 2017 Nope - no joy using MacPro5,1 to avoid the AGDP/black screen issue Have you tried booting high Sierra with only one card? Link to comment Share on other sites More sharing options...
alfaSZ Posted September 3, 2017 Share Posted September 3, 2017 Have you tried booting high Sierra with only one card? Fair point - I thought of it too but would rather not dismantle my waterloop etc if I don't absolutely have too so am waiting for a workaround and using 12.6 in the meantime (which has proper drivers to begin with...) Link to comment Share on other sites More sharing options...
dehjomz Posted September 3, 2017 Share Posted September 3, 2017 Fair point - I thought of it too but would rather not dismantle my waterloop etc if I don't absolutely have too so am waiting for a workaround and using 12.6 in the meantime (which has proper drivers to begin with...) Fair point. There may be a way to use a SSDT to disable one of the cards via software as OSX High Sierra boots... Link to comment Share on other sites More sharing options...
alfaSZ Posted September 3, 2017 Share Posted September 3, 2017 Fair point. There may be a way to use a SSDT to disable one of the cards via software as OSX High Sierra boots... yes indeed - will look into that as soon as I get some time Link to comment Share on other sites More sharing options...
aushack Posted September 3, 2017 Share Posted September 3, 2017 Hi Guys would appreciate any help. I'm getting a kernel panic as attached when booting the installer for High Sierra dev beta 9. I've tried also tried the Public beta. USB installer with createinstallmedia Clover r4189 Only FakeSMC kext (no plugins) in Other apfs.efi from BaseSystem in drivers64UEFI Boot arguments: -v kext-dev-mode=1 maxmem=4096 BIOS options: XMP Memory - Profile1 Internal Graphics: Disabled xHCI - Auto xHCI Hand-off / EHCI Hand-off - Enabled OS Type: Other Boot mode selection: UEFI Only VT-d - Disabled Edit: Serial port - Disabled EFI with debug.log attached and specs are in my sig. If this helps anyone I got past this KP with the following under ACPI <key>DropTables</key> <array> <dict> <key>Signature</key> <string>MATS</string> </dict> </array> 1 Link to comment Share on other sites More sharing options...
mnfesq Posted September 3, 2017 Share Posted September 3, 2017 So DP9, like DP8 works great on my laptop except that, when I use the Generic Brightness kext, the laptop crashes and restarts when I wake from sleep. The Generic Brightness kext can load without problem and works fine. But the laptop wakes from sleep and about 1-2 seconds later restarts. What makes the Generic Brightness kext work is an entry in my DSDT for my LCD screen that reads "Name (_HID, EisaId ("LCD1234")) // _HID: Hardware ID". When I remove that entry, the Generic Brightness kext stops working but, even though it is loaded, its presence does not cause the wake-from-sleep crash. I have tried both IntelBacklightFix.kext and ACPIBacklightFix.kext by RehabMan and can't get either of them to work, even when I remove the DSDT entry, LCD1234 and use his PNLF patch. I use the simple PNLF patch in order to get the slider to show up in Display Preferences and there's no problem with that as far as I can see. Looking for suggestions. Link to comment Share on other sites More sharing options...
TheRacerMaster Posted September 3, 2017 Share Posted September 3, 2017 IntelBacklight/ACPIBacklight have been broken since 10.12.4 IIRC... the proper method now is to use an AppleBacklight injector + a Clover patch + a PNLF SSDT (Google for more info). Link to comment Share on other sites More sharing options...
niknod Posted September 3, 2017 Share Posted September 3, 2017 I know it takes some patience, but it's the only effective method to solve the problem; and you don't need any other graphics kexts, like Lilu.kext or IntelGraphicsFixup.kext, nor you have to modify ig-platform-id; just patching dsdt and ssdts is required cheers! ok sandro sorted with disabled Nvidia gpu in ssdt files high Sierra is installed just need to get HD4600 gpu running good.thanks for all your help. Dave Link to comment Share on other sites More sharing options...
mnfesq Posted September 4, 2017 Share Posted September 4, 2017 IntelBacklight/ACPIBacklight have been broken since 10.12.4 IIRC... the proper method now is to use an AppleBacklight injector + a Clover patch + a PNLF SSDT (Google for more info). Unfortunately, so far, this makes things worse, not better. I couldn't use the SSDT-PNLF because it prevented my graphics from loading. I changed the references to IGPU to GFX0 in the SSDT-PNLF and added it to my DSDT. Graphics loaded without the custom SSDT but I lost my slider that I had with previous entries for PNLF and I lost battery function (Yes, I am using the most current version of ACPIBatteryManager.kext.). I tried removing LCD1234 and I tried putting it back. It made no difference. I used the Clover patch and installed the injector kext to L/E. When it comes to screen brightness, none of RehabMan's methods have worked on my laptop. It's rather frustrating although it is not an absolutely critical feature to have working. I wish I understood what was going on from a technical standpoint and not just trying fixes created for other laptops by other people. While I can follow instructions, I'm not learning anything about the nature of this problem. Thanks for your help so far. Don't give up on me just yet if you have any other ideas. Link to comment Share on other sites More sharing options...
Sherlocks Posted September 4, 2017 Share Posted September 4, 2017 clean installation hs beta9. all is working like sierra. really thanks to rehabman. battery indication was fixed by him 5 Link to comment Share on other sites More sharing options...
SavageAUS Posted September 4, 2017 Share Posted September 4, 2017 Unfortunately, so far, this makes things worse, not better. I couldn't use the SSDT-PNLF because it prevented my graphics from loading. I changed the references to IGPU to GFX0 in the SSDT-PNLF and added it to my DSDT. Graphics loaded without the custom SSDT but I lost my slider that I had with previous entries for PNLF and I lost battery function (Yes, I am using the most current version of ACPIBatteryManager.kext.). I tried removing LCD1234 and I tried putting it back. It made no difference. I used the Clover patch and installed the injector kext to L/E. When it comes to screen brightness, none of RehabMan's methods have worked on my laptop. It's rather frustrating although it is not an absolutely critical feature to have working. I wish I understood what was going on from a technical standpoint and not just trying fixes created for other laptops by other people. While I can follow instructions, I'm not learning anything about the nature of this problem. Thanks for your help so far. Don't give up on me just yet if you have any other ideas. As far as i can see all i'm using for brightness on my laptop is SSDT-PNLF.aml and thats on Sierra and High Sierra. Nothing else. I'll attach the and my dsdt if you wanna check. patched.zip And this patch <dict> <key>Comment</key> <string>change F%uT%04x to F%uTxxxx in AppleBacklightInjector.kext (credit RehabMan)</string> <key>Disabled</key> <false/> <key>Name</key> <string>com.apple.driver.AppleBacklight</string> <key>Find</key> <data>RiV1VCUwNHgA</data> <key>Replace</key> <data>RiV1VHh4eHgA</data> </dict> </plist> Even if i add in AppleBacklightInjector.kext i can still boot and it gives me more brightness ranges. Hopefully some of this info helps. Link to comment Share on other sites More sharing options...
Sherlocks Posted September 4, 2017 Share Posted September 4, 2017 i saw difference of csractiveconfig between 0x67 and 0x3e7 on hs dp9 0x3e7 shown enabled SIP 0x67 shown disabled SIP 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted September 4, 2017 Share Posted September 4, 2017 i saw difference of csractiveconfig between 0x67 and 0x3e7 on hs dp9 0x3e7 shown enabled SIP Screen Shot 2017-09-04 at 12.45.00 PM.png 0x67 shown disabled SIP Screen Shot 2017-09-04 at 1.19.36 PM.png Will we stay with 0x3e7 or return with 0x67? Link to comment Share on other sites More sharing options...
LockDown Posted September 4, 2017 Share Posted September 4, 2017 i thought it was 0x3FF to disable, not 0x3e7? Link to comment Share on other sites More sharing options...
Sherlocks Posted September 4, 2017 Share Posted September 4, 2017 Will we stay with 0x3e7 or return with 0x67? Not sure.But i now return 0x67. It show "disabled" SIP 나의 LG-F800S 의 Tapatalk에서 보냄 i thought it was 0x3FF to disable, not 0x3e7?0x3ff? Where is get this values? 나의 LG-F800S 의 Tapatalk에서 보냄 Link to comment Share on other sites More sharing options...
LockDown Posted September 4, 2017 Share Posted September 4, 2017 나의 LG-F800S 의 Tapatalk에서 보냄 0x3ff? Where is get this values? 나의 LG-F800S 의 Tapatalk에서 보냄 in here 1 Link to comment Share on other sites More sharing options...
Recommended Posts