Jump to content
93 posts in this topic

Recommended Posts

hello.

 

i find something log

 

i'm working to solve glitch. but still no luck.

 

here is my try

 

i see log

 

2016-11-01 10:12:09.010084+0900 0x38d      Fault       0x0                  0      kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(uint32_t, IOAccelResource2 *): getPixelInformation for framebuffer 0 failed

2016-11-01 10:12:09.019726+0900 0x38d      Fault       0x0                  0      kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(uint32_t, IOAccelResource2 *): getCurrentDisplayMode for framebuffer 1 failed

2016-11-01 10:12:09.029511+0900 0x38d      Fault       0x0                  0      kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(uint32_t, IOAccelResource2 *): getCurrentDisplayMode for framebuffer 2 failed

2016-11-01 10:12:09.099103+0900 0x634      Default     0x0                  0      kernel: (HFS) hfs: mounted Mac Data on device disk0s6

2016-11-01 10:12:09.119939+0900 0x38d      Default     0x0                  0      kernel: kPEDisableScreen 1

2016-11-01 10:12:09.130988+0900 0x38d      Fault       0x0                  0      kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(uint32_t, IOAccelResource2 *): getCurrentDisplayMode for framebuffer 1 failed

2016-11-01 10:12:09.140496+0900 0x38d      Fault       0x0                  0      kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(uint32_t, IOAccelResource2 *): getCurrentDisplayMode for framebuffer 2 failed

2016-11-01 10:12:09.152664+0900 0x38d      Default     0x0                  0      kernel: kPEEnableScreen 1

2016-11-01 10:12:09.249559+0900 0x38d      Default     0x0                  0      kernel: kPEDisableScreen 1

2016-11-01 10:12:09.266084+0900 0x38d      Fault       0x0                  0      kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(uint32_t, IOAccelResource2 *): getCurrentDisplayMode for framebuffer 1 failed

2016-11-01 10:12:09.275634+0900 0x38d      Fault       0x0                  0      kernel: (IOAcceleratorFamily2) bool IOAccelDisplayPipe2::init_framebuffer_resource(uint32_t, IOAccelResource2 *): getCurrentDisplayMode for framebuffer 2 failed

 

i didnt see this log in el capitan. so i need to pass this routin.

IOAcceleratorFamily2
 
pass entire routin of above log
00 48 89 45 D0 45 85 FF 0F 84 AD 00 00 00 49 8B
00 48 89 45 D0 45 85 FF 0F 85 AD 00 00 00 49 8B
 
 

pass only getCurrentDisplayMode

FF 90 F0 09 00 00 85 C0 74 37 45 8B 8E 14 04 00
FF 90 F0 09 00 00 85 C0 EB 37 45 8B 8E 14 04 00
 

pass only getPixelInformation

FF 90 E8 09 00 00 85 C0 0F 84 8B 00 00 00 45 8B
FF 90 E8 09 00 00 85 C0 0F 85 8B 00 00 00 45 8B

 

pass entire routin is no effect with glitch window

pass only getCurrentDisplayMode is get osx but same now

pass only getPixelInformation stop apple logo

 

thank you

I updated to 10.12.2 on my desktop, patched adgp, patched nvidiarequiredos and when I boot it's black and white and doesn't load anything. GTX 960.

 

Sent from my SM-G930F using Tapatalk

Booting with nv_disable=1 results in poor performance obviously but at least its colour and working lol

I updated to 10.12.2 on my desktop, patched adgp, patched nvidiarequiredos and when I boot it's black and white and doesn't load anything. GTX 960

 

 

Same here. Fortunately, I have a GTX 650 Ti which doesn't need webdrivers so it's working fine using macOS stock kexts.

 

But as for 2nd 10.12.1 beta, my USB keyboard doesn't work anymore. None of the keys actually (just 3 were disabled in 16B2333a).

 

[EDIT]

 

Karabiner Elements was the culprit :P !

I updated to 10.12.2 on my desktop, patched adgp, patched nvidiarequiredos and when I boot it's black and white and doesn't load anything. GTX 960.

 

Sent from my SM-G930F using Tapatalk

Booting with nv_disable=1 results in poor performance obviously but at least its colour and working lol

 

The previous patch for NVDAStartupWeb.kext (16C32e) is still working at 10.12.2

post-70188-0-10644700-1478086769_thumb.png

post-70188-0-95163700-1478086779_thumb.png

post-70188-0-51125800-1478086818_thumb.png

  • Like 1

@jsl

 

May I ask you what drivers are selected in NVIDIA Driver Manager > Graphics Driver ?

 

It appears that as soon I select NVIDIA's one and reboot, the B&W display returns back ! So patching the NVDAStartupWeb.kext works but not when NVDIA's Graphics drivers are selected.

 

PS : Sorry for the first screenshot but that's all I can display since the system is barely usable.

post-1163891-0-78136800-1478095982_thumb.png

post-1163891-0-68150000-1478096035_thumb.png

Which build were you on before? The combo update or app store?

 

Sent from my SM-G930F using Tapatalk

I have updated from 10.12.1(16B2555) via App Store.

The latest Nvidia Web Driver should be installed at 10.12.1

After update need patch NVDAStartupWeb.kext to 16C32e (or 16C32f) dependent upon your new version.

How are the nvidia drivers in the new beta?

 

Sent from my SM-G930F using Tapatalk

Working well without any problem for my applications.

Edited by jsl

About EFI and SMC firmware updates for Intel-based Mac computers

 

https://support.apple.com/en-us/HT201518

 

This kext only appeared in the last update. It contains the ID of the LPC chipsets, a large list. There is not even supported by Mac OS.

 

post-1203014-0-15228400-1478169546_thumb.jpg

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