Jump to content

[pre-release] macOS High Sierra

fantomas

By fantomas,
in New Releases and Updates

 Share
3735 posts in this topic

Recommended Posts

Cyberdevs
Cyberdevs
Posted
Posted

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.

Cyberdevs
Cyberdevs
Posted
Posted

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.

niknod
niknod
Posted
Posted

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!

sandro_desktop
sandro_desktop
Posted
Posted

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!

alfaSZ
alfaSZ
Posted
Posted

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...)

dehjomz
dehjomz
Posted
Posted

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...

aushack
aushack
Posted
Posted
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.

 

post-114155-0-54813300-1504341671_thumb.jpg

 

 

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>
  • Like 1
mnfesq
mnfesq
Posted
Posted

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.  

niknod
niknod
Posted
Posted

 

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

mnfesq
mnfesq
Posted
Posted

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.

SavageAUS
SavageAUS
Posted
Posted

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.

Matgen84
Matgen84
Posted
Posted

i saw difference of csractiveconfig between 0x67 and 0x3e7 on hs dp9

 

0x3e7 shown enabled SIP

attachicon.gifScreen Shot 2017-09-04 at 12.45.00 PM.png

 

0x67 shown disabled SIP

attachicon.gifScreen Shot 2017-09-04 at 1.19.36 PM.png

 

Will we stay with 0x3e7 or return with 0x67? 

Sherlocks
Sherlocks
Posted
Posted

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에서 보냄

Sherlocks
Sherlocks
Posted
Posted

in here

 

thank you for info

but 0x3ff is no luck like 0x3e7

 

Sherlocksui-MacBook-Pro:~ sherlocks$ csrutil status

System Integrity Protection status: enabled (Custom Configuration).

 

Configuration:

Apple Internal: disabled

Kext Signing: disabled

Filesystem Protections: disabled

Debugging Restrictions: disabled

DTrace Restrictions: disabled

NVRAM Protections: disabled

BaseSystem Verification: disabled

 

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

Sherlocksui-MacBook-Pro:~ sherlocks$ 

 

  • Like 1
Matgen84
Matgen84
Posted
Posted

thank you for info

but 0x3ff is no luck like 0x3e7

 

In find cecekpawon'post http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/page-691?do=findComment&comment=2467180 And try this tool: csrstat. Give me your opinion on the results for csrutil status?

 

Under Sierra with 0x3e7

 

 

post-1110743-0-14698200-1504502020_thumb.png

  • Like 1
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...