Contribute
Register

[Advices needed] ASUS P8Z68-V PRO/GEN3 with patched bios, how many devices still need DSDT?

Status
Not open for further replies.
Joined
Apr 18, 2012
Messages
17
Motherboard
Mac OS 10.7.2 Lion
CPU
2550k
Graphics
GTX470
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hi all fellow, sorry to bother you but I am a newbie of hackintosh who wish to ask for some advices before I started. I am planning to get a ASUS P8Z68-V PRO/GEN3 and wish it to dual boot Win7/MLion for my little project. So search a lot and found out ASUS patched bios and create DSDT article in here. But I have few things not sure so can you help me to point out what is wrong?

1) If using patched bios on http://biosrepo.wordpress.com/asus/z68/, it can use native AppleIntelCPUPM. Is this the only effect that the bios will provide? Will it also included patch for the other on-board devices like ALC892, ASMedia USB3, Marvell SATA3, Intel LAN, VIA 1394, etc?

2) To extract the DSDT of my board, should I use stock bios or patched bios also work?

3) If I extract from patched bios, do I still need to patch the DSDT with "P8 (generic) BIOS 3xxx" patch?

4) For these on-board devices (ALC892, ASMedia USB3, Marvell SATA3, Intel LAN, VIA 1394), Any of them can be handled by DSDT alone? Or they all need specific drivers? Can ALC892 be handled solely by DSDT (including 7.1 audio)?

5) I will put a i5 2550k that can OC from 3.4G to 4.8G so OC is quite a critical performance boost :p . Is OC needed to be done on bios setting, SSDT setting or combining these two? Is SSDT cannot be generic and must be individual CPU dependent? (need to change SSDT if using different CPU?)

6) If I use GTX470 with HDMI sound, which driver I should use? The one from NVIDIA (http://www.nvidia.com/object/macosx-304.00.05f02-driver.html) or multibeast? Are they has power management that will clock down when no loading (www.tonymacx86.com/graphics/69009-apple-graphics-power-management-display-sleep.html)?

7) from this: http://www.tonymacx86.com/mountain-...dual-nvidia-gtx-560ti-448-gfx-3-monitors.html , I saw the selection "ALC892 without DSDT" <= is it meant handle it with driver instead of DSDT? Or the bios has the corresponding DSDT already? And the selection "SSDT i5 overclocked", will it fixed the OC max? If I want to OC more, I need to further modify it?

8) When should I use PCI Root ID fix? Should all ASUS boards use it?

9) Will SpeedStep related to OC or SSDT?

Sorry for so many question. Please kindly help to point me to the correct way~ Thanks a lot!
 
1) only allows native aicpupm to load
2) makes no difference
3) either edit your dsdt or dont. extracting the native dsdt and doing nothing to it....does nothing.
4) all of those except the via firewire need drivers/kexts. audio injection can be done through the dsdt, rather than a hdaenabler, but you still need a patched applehda.kext
5) o/c is of course done in the bios. you need an ssdt to match the o/c speed. make your own ssdt to match the o/c http://www.tonymacx86.com/ssdt/56186-revogirl-ssdt-generation-script.html
6) for audio, see the hdmi audio subforum
7) see number 4. you need patched applehda.kext regardless. but you can chose to edit the dsdt for audio layout, or you can use a hdenabler.kext. ''without dsdt'' in multi adds the hdaenabler
8)depending on graphics card and/or motherboard. i dont think you need it.
9) see 5
 
1) only allows native aicpupm to load
2) makes no difference
3) either edit your dsdt or dont. extracting the native dsdt and doing nothing to it....does nothing.
4) all of those except the via firewire need drivers/kexts. audio injection can be done through the dsdt, rather than a hdaenabler, but you still need a patched applehda.kext
5) o/c is of course done in the bios. you need an ssdt to match the o/c speed. make your own ssdt to match the o/c http://www.tonymacx86.com/ssdt/56186-revogirl-ssdt-generation-script.html
6) for audio, see the hdmi audio subforum
7) see number 4. you need patched applehda.kext regardless. but you can chose to edit the dsdt for audio layout, or you can use a hdenabler.kext. ''without dsdt'' in multi adds the hdaenabler
8)depending on graphics card and/or motherboard. i dont think you need it.
9) see 5

Hi samisnake, thank you so much for your reply~ Still wanna further clarify somethings (sorry~ :$)
3) so if I use patched bios, I don't need to extract dsdt at all, right?
5) before I install, shall I remove all OC setting first? then when running Multibeast, should I select "i5 Overclocked" to get the system running with SSDT? (then replace the standard SSDT from Multibeast by the one I made myself?)
6) I saw enabling GTX470's HDMI audio need DSDT. So if I really need GTX470's HDMI audio, I will need to extract the dsdt, patched the p8(3xxx) and the corresponding audio patch then put the dsdt.aml on desktop rerun multibeast?
7) if use ALC892 only then I will use HDAEnabler to easier manage~ :p
8) I saw some said PCIRootIDFix is related to App Store verification?

10) BTW, will the AppleGraphicPowerManagement work with Femi display card by default? Any specific procedures in order to get it work?

Many thanks~ :-D
 
3) has nothing to do with the 'patched' part of it whether or not you need to edit the dsdt. its all down the the way the uefi works with osx. the 3xxx bioses for your board can run 'dsdt-free' as some call it (isnt strictly true, as you are still using a dsdt-the native dsdt, its just that you arent editing it). if you want hdmi audio though, you will need dsdt edits for audio.
5) thats a good idea, to give you a starting base which you can learn from.
6) technically you wont need that p8 generic patch, although it wont hurt. essentially though, yes thats how you could do it. alternatively, all the needed edits are easily laid out in toleda's hdmi audio thread.
7) if you want hdmi audio you cant use a hdaenabler, youve gotta use dsdt edits (in place of the hdaenabler- its either dsdt edit for audio, or hdaenabler. if you want hdmi you must use dsdt)
8) that pcirootid=1 fix for app store is only one possible fix for it. there are other alternatives, if you find your appstore doesnt work
10) no idea. im not an nvidia user
 
Hi Middleman,

Thanks a lot! I tried to follow exactly to your guide. Everything works except:
- Unibeast 1st boot with "GraphicsEnabler=Yes npci=0x2000" black screen, need to use "PCIRootUID=0" instead

The installation is smooth and after initialized and Multibeast, I found the following parts doesn't work yet:
0) Background in: My hardware is ASUS P8Z68-V PRO/GEN3 (patched 3603 bios) + i5 Sandy Bridge 2550k + Inno3D GTX 470
1) SpeedStep - If I haven't enabled SpeedStep in bios then Geekbench at 12200pt. If enabled SpeedStep then only 5000pt.
2) SSDT - If I choose "SSDT with i5/i7 OC to 4.2G" in Multibeast then the Geekbench also drop to 5000pt.
3) JMicron 36x SATA - Installed Multibeast's "3rd Party eSATA". Can see Intel Z68 SATA and Marvell SATA controller only.
4) Sleep - As I am using patched bios so I assume I don't need DSDT.aml also can get Power Management works natively. I pressed physical power button and it does try to put itself to sleep for 1-2 seconds (the power LED will change rotate between dim and light in circle) then auto wake up by itself. Not really stay at sleep
5) AppleACPIPlatform Rollback Option - is it needed if using patched bios? Also is it works with Z68 chipset (as it said it is for X58 boards). I tried with and without it anyway but both cannot get the system into long sleep. Also auto wake up in 1-2 seconds.
6) System Definition - Tried MacPro4,1 and MacPro5,1 both cannot boot in OSX. I thought Z68 is similar to X58 platform than the aged MacPro3,1?

Can you give me some more advices on this mainboard? Many thanks!!!! ^_^
 
1) ssdt is wrong/doesnt match your speed.
2) make your own ssdt. link is above
3)dunno, i dont use them
4) could be graphics card, or something which is attached to the pc. what happens if you select 'sleep' from the apple menu?
in terminal type 'pmset -g assertions'. paste output here.
also in console, search for 'Wake reason' (search box in the top right of console).
5) dont need to use it, unless you need to use it. you used it for the sake of it, not out of need ;)
it doesnt help with sleep
6) z68 isnt the same as x58. you arent using ecc ram. most people have to delete appletymcedriver.kext (or use a disabler kext) in order to use macpro4,1 or 5,1. for now stick with 3,1 anyway
 
Hi Samisnake, thanks a lot for your advise! JMB36x is not important to me either so by now only 3 issues left:

1) Overclock & SpeedStep (I suppose proper SSDT will able to OC to max in high loading and clock down to save power when idle? I will try to edit my SSDT in this weekend ^_^)

2) HWMonitor and "iStat Menus" not work. Installed FakeSMC and plugins from Multibeast 5.2.1 but only HDD temperture can be seen in HWMonitor. I found ACPISensors.kext, CPUSensors.kext, LPCSensors.kext and GPUSensors.kext are in /S/L/E/FakeSMC.kext/Contents/Plugins/ already. Is ASUS P8Z68-V PRO/GEN3 cannot support HW Monitoring? (any other ways that I can find out the current system CPU frequency or CState/PState?)
jhui_macpro_z68: Plugins jhui$ ioreg -lwo | grep PerformanceStateArray
| | "PerformanceStateArray" = (<490d0000187301000a0000000a00000000ff000000ff0000>,<480d0000187301000a0000000a0000000022000000220000>,<e40c0000de6301000a0000000a0000000021000000210000>,<1c0c00003e4601000a0000000a000000001f0000001f0000>,<b80b0000d73701000a0000000a000000001e0000001e0000>,<540b0000b42901000a0000000a000000001d0000001d0000>,<f00a0000e51b01000a0000000a000000001c0000001c0000>,<280a0000f30001000a0000000a000000001a0000001a0000>,<c4090000def300000a0000000a0000000019000000190000>,<600900000be700000a0000000a0000000018000000180000>,<9808000035ce00000a0000000a0000000016000000160000>,<3408000025c200000a0000000a0000000015000000150000>,<d007000055b600000a0000000a0000000014000000140000>,<6c070000c4aa00000a0000000a0000000013000000130000>,<a40600006e9700000a0000000a0000000011000000110000>,<400600008d8c00000a0000000a0000000010000000100000>)
jhui_macpro_z68: Plugins jhui$
Is this related?

(just tried to replace the latest FakeSMC&Plugins binary rev633 also no luck (already chosen the NuvotonNCT677x.kext to match with the Super IO chip of this board)
drwxr-xr-x 3 jhui staff 102 Feb 16 19:34 ACPISensors.kext
drwxr-xr-x 3 jhui staff 102 Feb 16 23:37 GeForceSensors.kext
drwxr-xr-x 3 jhui staff 102 Feb 16 19:34 IntelCPUMonitor.kext
drwxr-xr-x 3 jhui staff 102 Feb 16 19:34 NuvotonNCT677x.kext
3) Sleep - After dozen of reinstall, I figured out that it was the ASMedia USB 3.0 (Caldigit). Disable it can stable sleep. I suppose there is something wrong with the Caldigit come with Multibeast which need fix or update (some said need DSDT to fix as well). By now the problem is can stay sleep, but if I press the power button or keyboard to try to wake it up, the fans in cases still running, but no screen (eventually need to restart). I am using Apple wireline keyboard. My 'pmset -g assertions' is as follow:

jhui_macpro_z68: Plugins jhui$
Last login: Sun Feb 17 00:20:08 on console
jhui_macpro_z68: Plugins jhui$ pmset -g assertions
17/2/13 12:20:14 AM HKT
Assertion status system-wide:
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
PreventUserIdleSystemSleep 0
ExternalMedia 0
UserIsActive 0
ApplePushServiceTask 0
BackgroundTask 1

Listed by owning process:
pid 36(mds): [0x0000000c0000012c] 00:00:14 BackgroundTask named: "com.apple.metadata.mds"

Kernel Assertions: 0x0004
* Kernel Assertion ID = 500
Created At = 17/2/13 12:19:39 AM HKT
Modified At = 17/2/13 12:24:22 AM HKT
Owner ID = 0xffffff801f64d000
Level = 255
Assertions Set = None (4)

* Kernel Assertion ID = 501
Created At = 17/2/13 12:19:41 AM HKT
Modified At = 17/2/13 12:24:22 AM HKT
Owner ID = 0xffffff801f6d4000
Level = 255
Assertions Set = None (4)

jhui_macpro_z68: Plugins jhui$

Can you see anything I got it wrong? Seems these means I can get into sleep, but cannot tell why cannot wake up properly?

Thanks!
 
1) yep
2) yours should work with hwmonitor.
currently using it with those plugins you mentioned, and it shows all the right info. something youll have to mess with
3) right, i forgot to ask if you were using the usb3 kext. that is known to kill sleep. delete the kext if you still have it.
atm it would seem its your graphics card preventing wake up (has all the signs of gfx card). have you got another one to test with?
 
Status
Not open for further replies.
Back
Top