Jump to content
199 posts in this topic

Recommended Posts

53 minutes ago, chris1111 said:

Easy Update Kepler machine and Probook 6570b HD 4000

  Hide contents

scree437.png.478df1b0eec486196bc0cc5b35bd4291.pngscree438.png.2fe65f35c5296643551f4069529c63eb.png

 

Thanks for your GeoForce Kepler Patcher.

After apply GeoForce Kepler Patches V2 to GT-730 of P5Q hackintosh during reboot it got reboot by OC 0.7.8 and KP by Clover 5141.

Any fix for this issue ?

IMG-0126.thumb.JPG.b783d89bee2a4309b65d1ee72d70d811.JPG

Edited by jsl2000
9 hours ago, jsl2000 said:

Thanks for your GeoForce Kepler Patcher.

After apply GeoForce Kepler Patches V2 to GT-730 of P5Q hackintosh during reboot it got reboot by OC 0.7.8 and KP by Clover 5141.

Any fix for this issue ?

 

make sur the good value is set to NVRAM

See the guide Here its of topic, open issue on Github

  • Like 3
On 2/1/2022 at 5:52 AM, jm26200 said:

After multiple attempts impossible to complete the installation of 12.3.
So made the decision to wait for a next update, and on mo Z590 very slow too so not interesting
have a nice day waiting
Regards

 

 

Same issue with b2 and b3 😕

1 hour ago, Skyfallkavu said:

Anyone else having issues staying asleep, and kernel panicking during sleep with this one? I just had to disable vt-d to increase my RAM past 32GB. Trying to rule out causes.

There is a patch against the issue.

Screenshot 2022-02-18 at 22.12.57.png

  • Like 2
2 hours ago, Slice said:

There is a patch against the issue.

Screenshot 2022-02-18 at 22.12.57.png

Didn't seem to do the trick. Implemented it via my opencore config, but still getting wakes. Will have to test longer term.

 

Oddly, wake reason is:

2022-02-18 16:15:50 -0500 Assertions          	PID 259(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00  id:0x0xd00008475 [System: PrevIdle DeclUser BGTask SRPrevSleep IntPrevDisp kCPU kDisp]
2022-02-18 16:15:50 -0500 Assertions          	PID 259(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00  id:0x0xd00008475 [System: PrevIdle DeclUser BGTask IntPrevDisp kDisp]
2022-02-18 16:15:53 -0500 DarkWake            	DarkWake from Normal Sleep [CDN] : due to XDCI/ Using AC (Charge:0%) 5 secs
2022-02-18 16:15:53 -0500 WakeTime            	WakeTime: 3.934 sec
2022-02-18 16:15:53 -0500 Kernel Client Acks  	Delays to Wake notifications: [en0 driver is slow(msg: DidChangeState to 1)(686 ms)] [AirPort_BrcmNIC driver is slow(msg: SetState to 2)(830 ms)] [SS01 driver is slow(msg: WillChangeState to 3)(394 ms)] [PRT5 driver is slow(msg: SetState to 2)(1179 ms)] [PRT4 driver is slow(msg: SetState to 2)(1180 ms)] [PRT3 driver is slow(msg: SetState to 2)(3031 ms)]
2022-02-18 16:15:58 -0500 Wake                	DarkWake to FullWake from Normal Sleep [CDNVA] : due to UserActivity Assertion Using AC (Charge:0%)
2022-02-18 16:15:58 -0500 WakeTime            	WakeTime: 1.462 sec

 

10 hours ago, Skyfallkavu said:

Didn't seem to do the trick. Implemented it via my opencore config, but still getting wakes. Will have to test longer term.

 

Oddly, wake reason is:

2022-02-18 16:15:50 -0500 Assertions          	PID 259(mDNSResponder) Created MaintenanceWake "mDNSResponder:maintenance" 00:00:00  id:0x0xd00008475 [System: PrevIdle DeclUser BGTask SRPrevSleep IntPrevDisp kCPU kDisp]
2022-02-18 16:15:50 -0500 Assertions          	PID 259(mDNSResponder) Released MaintenanceWake "mDNSResponder:maintenance" 00:00:00  id:0x0xd00008475 [System: PrevIdle DeclUser BGTask IntPrevDisp kDisp]
2022-02-18 16:15:53 -0500 DarkWake            	DarkWake from Normal Sleep [CDN] : due to XDCI/ Using AC (Charge:0%) 5 secs
2022-02-18 16:15:53 -0500 WakeTime            	WakeTime: 3.934 sec
2022-02-18 16:15:53 -0500 Kernel Client Acks  	Delays to Wake notifications: [en0 driver is slow(msg: DidChangeState to 1)(686 ms)] [AirPort_BrcmNIC driver is slow(msg: SetState to 2)(830 ms)] [SS01 driver is slow(msg: WillChangeState to 3)(394 ms)] [PRT5 driver is slow(msg: SetState to 2)(1179 ms)] [PRT4 driver is slow(msg: SetState to 2)(1180 ms)] [PRT3 driver is slow(msg: SetState to 2)(3031 ms)]
2022-02-18 16:15:58 -0500 Wake                	DarkWake to FullWake from Normal Sleep [CDNVA] : due to UserActivity Assertion Using AC (Charge:0%)
2022-02-18 16:15:58 -0500 WakeTime            	WakeTime: 1.462 sec

 

You asked about kernel panic after wake. Now I see the wake is successful?

 

Guest
This topic is now closed to further replies.
×
×
  • Create New...