skysea76 Posted August 13, 2012 Share Posted August 13, 2012 I just got this MB, updated with patched bios, configured the BIOS correctly (AHCI, HPET, disabled ASMedia SATA3, etc), installed ML on my SSD, made a DSDT and some kexts (latest fakesmc + monitoring, Realtek kext). The only problem I'm having is that if I put a PCIe GPU in I get a KP. Tried both with my 9800GT and a 6870. I also tried with GE=Y and GE=No + Device properties for 9800GT + HD 4000. Always the same KP. Tried ncpi=0x2000 & ncpi=0x3000 with no luck. I just can't get it to boot. Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/ Share on other sites More sharing options...
Rampage Dev Posted August 13, 2012 Share Posted August 13, 2012 It looks like you need to install nullcpupowermanagment kext.... Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1843575 Share on other sites More sharing options...
skysea76 Posted August 13, 2012 Author Share Posted August 13, 2012 It looks like you need to install nullcpupowermanagment kext.... but I have a patched BIOS that should take care of that! http://bios.zmac.net...30_modified.zip (from http://www.tonymacx8...-thread-34.html ) Also, I played with my DSDT a little more, I think the previous one was trash, with the new one this is what I get (edit: forgot to attach image to large) dsdt.txt Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1843584 Share on other sites More sharing options...
Rampage Dev Posted August 13, 2012 Share Posted August 13, 2012 Just try it with that kext and report the results... I don't know why the patched BIOS is not working for you. Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1843585 Share on other sites More sharing options...
skysea76 Posted August 13, 2012 Author Share Posted August 13, 2012 I get the same kp i'd say Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1843601 Share on other sites More sharing options...
Rampage Dev Posted August 13, 2012 Share Posted August 13, 2012 Boot with -v -s and then when you can type then type this code one line at a time to delete AppleTyMCEDriver.kext, mount / rm -rf /System/Library/Extensions/AppleTyMCEDriver.kext sudo rm -rf /System/Library/Caches/* schutdown -r now Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1843607 Share on other sites More sharing options...
skysea76 Posted August 13, 2012 Author Share Posted August 13, 2012 I'll try when I get home, but are you troubleshooting or "fixing" (if so, is there a more vanilla way)? What does the kext do exactly? Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1843733 Share on other sites More sharing options...
Rampage Dev Posted August 13, 2012 Share Posted August 13, 2012 That kext is for Triple Chanel Memory. If you do not have Triple Chanel Memory it can cause a KP. Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1843792 Share on other sites More sharing options...
skysea76 Posted August 15, 2012 Author Share Posted August 15, 2012 Ok I completely solved that and the graphics. Now I only need to fix sleep and the sensors (5v reports random value, some are missing -in comparison to windows- etc), which I understand is done by editing the DSDT and something about ACPISensors.kext -or whatever it's called, part of fakesmc monitoring kexts; could someone elaborate on this? Extra.zip Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844145 Share on other sites More sharing options...
Rampage Dev Posted August 15, 2012 Share Posted August 15, 2012 What is happening with sleep? Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844153 Share on other sites More sharing options...
skysea76 Posted August 15, 2012 Author Share Posted August 15, 2012 What is happening with sleep? It goes "down" but I can't wake it up thru bluetooth (I don't really care about this), and if I press a key on my USB keyboard it goes thru the motions of coming on, but the screen never goes "on" Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844209 Share on other sites More sharing options...
Rampage Dev Posted August 15, 2012 Share Posted August 15, 2012 I will take a look at the DSDT today and get back to you. 1 Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844287 Share on other sites More sharing options...
skysea76 Posted August 15, 2012 Author Share Posted August 15, 2012 No rush, thanks. Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844297 Share on other sites More sharing options...
Rampage Dev Posted August 16, 2012 Share Posted August 16, 2012 After looking at the DSDT I am not sure what is happening. I have never been good at trouble shooting waking issues other then if the system wakes right away. Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844423 Share on other sites More sharing options...
skysea76 Posted August 16, 2012 Author Share Posted August 16, 2012 Hmm... I miss the LED on my x58 Extreme... I never got sleep to work but someone with ACPI knowledge would have been able to real easy, it showed every single process in the boot sequence... You could easily know if video wasn't posting, RAM, etc... Back on topic: would the original DSDT + the rest of the tables help? Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844425 Share on other sites More sharing options...
Rampage Dev Posted August 16, 2012 Share Posted August 16, 2012 Hmm... I miss the LED on my x58 Extreme... I never got sleep to work but someone with ACPI knowledge would have been able to real easy, it showed every single process in the boot sequence... You could easily know if video wasn't posting, RAM, etc... Back on topic: would the original DSDT + the rest of the tables help? Like I said I just don;t know... Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844431 Share on other sites More sharing options...
skysea76 Posted August 16, 2012 Author Share Posted August 16, 2012 Ok, thanks for your help anyhow! How do you recommend I proceed, just leave this thread open and wait, bump it every so often, open a new thread...? Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844449 Share on other sites More sharing options...
Rampage Dev Posted August 16, 2012 Share Posted August 16, 2012 Open a new thread and with great detail explain what the system is doing. Then post your DSDT and IOreg (From IOreg App) and see what other users say. You could try manually testing the different sleep modes in the BIOS by enabling only one at a time an see which ones work. Try S1 and S3 first. 1 Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844453 Share on other sites More sharing options...
skysea76 Posted August 16, 2012 Author Share Posted August 16, 2012 I actually just figured out sleep IS working. It just takes ~1m to wake up (and about 20s to go to sleep). IDK if I was too impatient before, or I changed something in the BIOS that helped (I wasn't too methodical about this). It would still be nice to get that down to a couple seconds (as it should be), as currently I can boot faster than I can wake up from sleep, making the latter kind of pointless. Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844568 Share on other sites More sharing options...
Rampage Dev Posted August 17, 2012 Share Posted August 17, 2012 Look at this: http://osxdaily.com/2010/07/17/why-mac-wakes-from-sleep/ Run the code in terminal and post the output. Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844754 Share on other sites More sharing options...
skysea76 Posted August 17, 2012 Author Share Posted August 17, 2012 8/15/12 11:40:47.506 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/15/12 11:40:47.509 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/15/12 11:40:48.041 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/15/12 11:40:48.128 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/15/12 11:40:48.537 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:25.052 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:25.054 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:25.520 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:25.624 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:26.111 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 10:02:37.000 AM kernel[0]: Sleep failure code 0x00000000 0x21006700 8/16/12 10:13:48.000 AM kernel[0]: Sleep failure code 0x00000000 0x21006700 8/16/12 10:15:45.501 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:15:45.503 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:15:46.154 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:17:58.477 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:17:58.479 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:17:59.663 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:29:50.480 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:29:50.482 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 12:27:30.000 PM kernel[0]: RTC: Maintenance 2012/8/16 15:26:14, sleep 2012/8/16 14:53:08 8/16/12 2:16:51.000 PM kernel[0]: RTC: Maintenance 2012/8/16 17:15:35, sleep 2012/8/16 15:27:53 8/16/12 4:06:13.000 PM kernel[0]: RTC: Maintenance 2012/8/16 19:04:57, sleep 2012/8/16 17:17:49 8/16/12 5:55:34.000 PM kernel[0]: RTC: Maintenance 2012/8/16 20:54:18, sleep 2012/8/16 19:06:36 8/16/12 7:44:55.000 PM kernel[0]: RTC: Maintenance 2012/8/16 22:43:39, sleep 2012/8/16 20:55:57 8/16/12 9:34:16.000 PM kernel[0]: RTC: Maintenance 2012/8/17 00:33:00, sleep 2012/8/16 22:45:17 8/16/12 10:34:25.638 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:34:25.639 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:34:26.285 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 Here is some more from logs (I've been monitoring them): 8/15/12 11:40:47.506 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/15/12 11:40:47.509 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/15/12 11:40:48.041 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/15/12 11:40:48.128 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/15/12 11:40:48.537 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:25.052 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:25.054 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:25.520 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:25.624 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 8:41:26.111 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no lock state data 8/16/12 10:02:37.000 AM kernel[0]: Sleep failure code 0x00000000 0x21006700 8/16/12 10:13:48.000 AM kernel[0]: Sleep failure code 0x00000000 0x21006700 8/16/12 10:15:45.501 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:15:45.503 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:15:46.154 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:17:58.477 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:17:58.479 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:17:59.663 AM WindowServer[105]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:29:50.480 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:29:50.482 AM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 12:27:30.000 PM kernel[0]: RTC: Maintenance 2012/8/16 15:26:14, sleep 2012/8/16 14:53:08 8/16/12 2:16:51.000 PM kernel[0]: RTC: Maintenance 2012/8/16 17:15:35, sleep 2012/8/16 15:27:53 8/16/12 4:06:13.000 PM kernel[0]: RTC: Maintenance 2012/8/16 19:04:57, sleep 2012/8/16 17:17:49 8/16/12 5:55:34.000 PM kernel[0]: RTC: Maintenance 2012/8/16 20:54:18, sleep 2012/8/16 19:06:36 8/16/12 7:44:55.000 PM kernel[0]: RTC: Maintenance 2012/8/16 22:43:39, sleep 2012/8/16 20:55:57 8/16/12 9:34:16.000 PM kernel[0]: RTC: Maintenance 2012/8/17 00:33:00, sleep 2012/8/16 22:45:17 8/16/12 10:34:25.638 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:34:25.639 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 10:34:26.285 PM WindowServer[103]: handle_will_sleep_auth_and_shield_windows: no action for lock state 1 8/16/12 8:52:51.842 AM com.apple.time[11]: Next maintenance wake [backup Interval]: <date: 0x7fbdc490f1e0> Thu Aug 16 09:25:26 2012 ART (approx) 8/16/12 8:52:51.842 AM com.apple.time[11]: Requesting maintenance wake [backup Interval]: <date: 0x7fbdc490f1e0> Thu Aug 16 09:25:26 2012 ART (approx) 8/16/12 10:10:33.201 AM com.apple.time[11]: Next maintenance wake [backup Interval]: <date: 0x7fadaa43bc30> Thu Aug 16 11:02:39 2012 ART (approx) 8/16/12 10:10:33.201 AM com.apple.time[11]: Requesting maintenance wake [backup Interval]: <date: 0x7fadaa43bc30> Thu Aug 16 11:02:39 2012 ART (approx) 8/16/12 10:14:15.590 AM com.apple.time[11]: Next maintenance wake [backup Interval]: <date: 0x7fbfec90c960> Thu Aug 16 11:13:50 2012 ART (approx) 8/16/12 10:14:15.590 AM com.apple.time[11]: Requesting maintenance wake [backup Interval]: <date: 0x7fbfec90c960> Thu Aug 16 11:13:50 2012 ART (approx) 8/16/12 10:14:23.689 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 10:15:45.000 AM kernel[0]: Wake reason: GLAN XHC 8/16/12 10:15:45.000 AM kernel[0]: The USB device iMate, USB To ADB Adaptor (Port 1 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2) 8/16/12 10:15:45.074 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 10:15:49.095 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 10:15:50.304 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 10:16:31.165 AM com.apple.time[11]: Next maintenance wake [backup Interval]: <date: 0x7fbfec910a30> Thu Aug 16 11:13:50 2012 ART (approx) 8/16/12 10:16:31.165 AM com.apple.time[11]: Requesting maintenance wake [backup Interval]: <date: 0x7fbfec910a30> Thu Aug 16 11:13:50 2012 ART (approx) 8/16/12 10:17:58.000 AM kernel[0]: Wake reason: power-button XHC (User) 8/16/12 10:17:58.000 AM kernel[0]: The USB device iMate, USB To ADB Adaptor (Port 1 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2) 8/16/12 10:17:58.136 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 10:17:58.160 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 10:18:02.120 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 10:28:20.344 AM com.apple.time[11]: Next maintenance wake [backup Interval]: <date: 0x7f9c20602c00> Thu Aug 16 11:27:20 2012 ART (approx) 8/16/12 10:28:20.344 AM com.apple.time[11]: Requesting maintenance wake [backup Interval]: <date: 0x7f9c20602c00> Thu Aug 16 11:27:20 2012 ART (approx) 8/16/12 10:28:26.469 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 10:29:50.027 AM com.apple.backupd-helper[302]: Not starting Time Machine backup after wake - less than 60 minutes since last backup completed. 8/16/12 10:29:50.000 AM kernel[0]: Wake reason: GLAN XHC 8/16/12 10:29:50.000 AM kernel[0]: The USB device iMate, USB To ADB Adaptor (Port 1 of Hub at 0x14000000) may have caused a wake by issuing a remote wakeup (2) 8/16/12 11:53:03.498 AM com.apple.time[11]: Next maintenance wake [backup Interval]: <date: 0x7f9c20608d30> Thu Aug 16 12:27:21 2012 ART (approx) 8/16/12 11:53:03.498 AM com.apple.time[11]: Requesting maintenance wake [backup Interval]: <date: 0x7f9c20608d30> Thu Aug 16 12:27:21 2012 ART (approx) 8/16/12 11:53:05.965 AM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 12:27:30.000 PM kernel[0]: Wake reason: RTC (Alarm) 8/16/12 12:27:50.328 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 2:16:51.000 PM kernel[0]: Wake reason: RTC (Alarm) 8/16/12 2:17:45.855 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 4:06:13.000 PM kernel[0]: Wake reason: RTC (Alarm) 8/16/12 4:06:33.174 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 5:55:34.000 PM kernel[0]: Wake reason: RTC (Alarm) 8/16/12 5:55:55.218 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 7:44:55.000 PM kernel[0]: Wake reason: RTC (Alarm) 8/16/12 7:45:15.281 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 9:34:16.000 PM kernel[0]: Wake reason: RTC (Alarm) 8/16/12 9:34:37.321 PM awacsd[56]: InnerStore GetWakeInfoForZone: zero address for 1019589403.members.btmm.icloud.com. 8/16/12 10:34:25.000 PM kernel[0]: Wake reason: GLAN EHC1 8/16/12 10:34:25.000 PM kernel[0]: The USB device HubDevice (Port 1 of Hub at 0x1d000000) may have caused a wake by issuing a remote wakeup (2) 8/16/12 10:34:25.000 PM kernel[0]: The USB device USB Optical Mouse (Port 6 of Hub at 0x1d100000) may have caused a wake by issuing a remote wakeup (3) Link to comment https://www.insanelymac.com/forum/topic/281772-asrock-pro4-m/#findComment-1844755 Share on other sites More sharing options...
Recommended Posts