841 replies to this topic

[Dojomann]

eep357, on 09 October 2012 - 06:20 PM, said:

maybe DP3 Nvidia kexts is the problem? What Nvidia card? Check console logs after it does this as soon a you reboot and see if any error shows

GeForce 560Ti. Other kexts cause even more regular amounts of freezing (especially the latest 10.8.2 kexts.. there's a big thread about it on tony mac site for the 550ti)

as a general guideline, should I enable p and c state generation? use the cst using sysIO ? USB bus fix? force HPET? what settings could fix this?

also, i think I modified my AppleRTC kext. Some places i've seen saydelete the Apple TyMCE driver. Should this make a difference? What does that driver do, anyway?

Finally, I have a weird feeling that it might have something to do with the USB drivers. Are there any DSDT fixes?

Also here's the log (I left the house earlier in the day, and just now in the evening I had to reboot it)

 Screen Shot 2012-10-09 at 10.00.47 PM.png   844.86K   16 downloads

[eep357]

Nothing that appears GPU related, looks like your USB devices might be ejecting on sleep, maybe just the UHCI (USB 1.1) devices, USBBusFix is supposed to fix that if DSDT doesn't. Most patched DSDT only have extensive edits for EHCI and sometimes UHCI gets overlooked, which has caused some problems in ML for people where in Lion it was not a problem. I use it because for some unknown reason it also increases my benchmark scores 5-10%. P&C states or Cstates using sysIO would apply to speed step, which can also be enabled via DSDT and/or SSDT. If you have HWmonitor installed with FakeSMC monitoring plug-ins, there is a CPU frequency option where you can see it go from the low x12 multiplier to whatever you set as your high multiplier in bios. Even though you'll likely have more than 2 states enabled, it will only show the high/low but in graph view can see it hitting the different states in-between. Try with and without P&C states and see if any difference in this behavior and if any difference in the cpu temps. Prob don't need force HPET, but won't hurt to use it. If you use the Perl command I posted a few posts back, that will patch AppleRTC. Some systems if using MacPro 5,1 smbios will KP during boot from AppleTyMCE, so you would know if you need to remove it

Here's my org.chameleon.Boot.plist, some of which is not 100% necessary and graphics stuff specific to my card, UUID stuff specific to RAID-0 booting:

<dict>
<key>AtiConfig</key>
<string>Uakari</string>
<key>AtiPorts</key>
<string>4</string>
<key>Default Partition</key>
<string>hd(0,3)</string>
<key>DropSSDT</key>
<string>Yes</string>
<key>EthernetBuiltIn</key>
<string>Yes</string>
<key>ForceHPET</key>
<string>Yes</string>
<key>Graphics Mode</key>
<string>1440x900x32</string>
<key>GraphicsEnabler</key>
<string>Yes</string>
<key>GUI</key>
<string>No</string>
<key>Kernel</key>
<string>mach_kernel</string>
<key>Kernel Flags</key>
<string>rd=uuid boot-uuid=92496DB5-5DB1-365B-B82B-533C19F4945B -v npci=0x3000</string>
<key>SystemType</key>
<string>1</string>
<key>Timeout</key>
<string>3</string>
<key>USBBusFix</key>
<string>Yes</string>
<key>UseKernelCache</key>
<string>Yes</string>
</dict>

Disabling the pretty GUI speeds up the Chameleon boot time between selecting boot drive in Chameleon and Chameleon's pass off to OSX bootloader quite a bit. Also purposely using wrong resolution for Graphics Mode because if I do enable the GUI, LogIn to Lion theme has a artifact in bottom right corner at 1920x1200.

[Dojomann]

okay! I did a whole host of things, so I'm not sure which has totally fixed it.. I re-compiled my DSDT with the latest iasl, and am not using usbbusfix, and that seemed to fix it

[eep357]

whole bunch of stuff FTW!

[Dojomann]

random question: what would forceHPET do? Also, let's say we wanted to generate C and P states. There's the two separate options, and then theres the newer CST using system io option. Does that replace both of the older bits, or would I need to still have those flags enabled for sysio to work as well? (unrelated, as my DSDT seems to have all of these pre-defined, and I get speedstepping without using chameleon's flags)

[banini_jeque]

I have sound working on my P6T WS Pro, but I don't have a line-in since using the updated method for 10.8. I'm using layout-id, Unicode("c"), which shows as 99 in System Report. I really want line in.

Also, did anyone get a proper DSDT going for one of these so we don't have to use the old ACPI kext? I finally gave up and started using it, but I'd rather not have to.

[eep357]

instead of layout ID 12, 0x0C in hex, try layout ID 1, 0x01 in hex

will depend on codec and which HDA your using if it will work or not

[taylorsyn]

If you want to use the stock ACPI kext you will need to patch the AppleRTC.Kext:


To patch  AppleRTC.kext in 10.8 just move it to the /Extra/Extensions and run:

sudo perl -pi -e 's|\x75\x30\x89\xd8|\xeb\x30\x89\xd8|' /Extra/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

This keeps it nice and vanilla, and yes it must be in /Extra/Extensions or it wont load!

[slowlaris]

banini_jeque, on 13 October 2012 - 06:35 AM, said:

I have sound working on my P6T WS Pro, but I don't have a line-in since using the updated method for 10.8. I'm using layout-id, Unicode("c"), which shows as 99 in System Report. I really want line in.

Also, did anyone get a proper DSDT going for one of these so we don't have to use the old ACPI kext? I finally gave up and started using it, but I'd rather not have to.

Hey! I got a P6T6 WS Pro and sound is still not working. Did you use the system provided AppleHDA with custom .xml definition files or an entirely new kext ?  

thx in advance

[eep357]

taylorsyn, on 15 October 2012 - 07:51 AM, said:

If you want to use the stock ACPI kext you will need to patch the AppleRTC.Kext:


To patch  AppleRTC.kext in 10.8 just move it to the /Extra/Extensions and run:

sudo perl -pi -e 's|\x75\x30\x89\xd8|\xeb\x30\x89\xd8|' /Extra/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

This keeps it nice and vanilla, and yes it must be in /Extra/Extensions or it wont load!

AppleRTC can be patched without moving it by changing the path

sudo perl -pi -e 's|\x75\x30\x89\xd8|\xeb\x30\x89\xd8|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

And loads fine and also included in kernel cache which can't be done from /Extra. Fixes possible sleep issues, but personally have not seen this impact ACPI one way or another, stock AppleACPIPlatform only causes large boot delay for me however and not a KP, so maybe a difference there

[pepegonzales]

Hi!,

In my case, i succeded to install 10.8.2 on my P6T SE + i7 930 + AMD Radeon HD 6450 Silent with the server.app

I've got a big hard reset problem... computer reset every 3 minuts or so, or when I login or when I launch a program... I've tried to patch the AppleRTC.kext... Any idea how I can find the problem? Console doesn't seems to tell something but I'm a newbie in this.
Any help?

[eep357]

Overclocked?

Turbo enabled?

VT-d enabled?

[pepegonzales]

eep357, on 17 October 2012 - 11:45 AM, said:

Overclocked?

Turbo enabled?

VT-d enabled?

Well, as a newbie, what I can tell is I don't think so... the bios is almost configured by default, with the last 0908 bios update (not patched) and I didn't followed or installed specific stuffs with this kinds of objectives. (except VT-Enabled, is it a bios option?)


For the moment, I've just succeed to install Tuxera NTFS (one of the hard disk (only datas) is NTFS) and for the last 5 minuts, I don't have a reset. Maybe the solution... I'm trying it at the moment.


EDIT: 10 more minuts without reset and normal use... but NEW RESET AGAIN... damned!
EDIT: now the system is a little bit more stable (less resets) but the problem still exist.

Is there a way to get a AppleRTC patched for a P6T SE?

[eep357]

VT-d is a bios option. There is VT-x and VT-d, not all x58's have VT-d, but most do. Both of them are virtualization related (running another OS virtually from inside your booted OS, like Parallels or VMware) VT-d gives added ability for virtual machine to have more direct control over various hardware. It's is not needed to run in VM and can sometimes cause stability issues. Same with turbo, which IS usually enabled by default, so unless you went into the BIOS and disabled it, it may be enabled still.

To patch appleRTC run the same command in terminal I posted earlier

sudo perl -pi -e 's|\x75\x30\x89\xd8|\xeb\x30\x89\xd8|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

This is the same for any Intel 64bit system, although some motherboards may need it more than others, and generally is only done to prevent cmos reset (all bios settings going back to default) when waking from sleep

[pepegonzales]

eep357, on 17 October 2012 - 02:24 PM, said:

sudo perl -pi -e 's|\x75\x30\x89\xd8|\xeb\x30\x89\xd8|' /System/Library/Extensions/AppleRTC.kext/Contents/MacOS/AppleRTC

This is the same for any Intel 64bit system, although some motherboards may need it more than others, and generally is only done to prevent cmos reset (all bios settings going back to default) when waking from sleep

Thanx a lot for the help.

- Original appleRTC.kext patched (original kept before, reinstaled y re-patched) using kext wizard. Rebuilt system cache.
- Bios Option VT-d not enable.
- Bios Option Turbo mode Tech was indeed enabled and is now desactivated.

The problem persist... unfortunately. It crashed and reset on login... as usual for 50% of the cases.

My question: the appleRTC patch is only to prevent CMOS reset when waking from sleep? In my case, it occure when system is awake!!!
Also, I'm trying the patch on a 10.8.2 version... is it there a problem?

[eep357]

unless you change something in the bios, then after the reset go back and the bios changed it's self back to how it was before, it's not the problem.

No reset's in Windows?
Try installing NullCPUPowerManagement.kext, if it stops the resets, we'll know it's a problem with native power management and then what to fix.

Also in bios, be sure voltage for your ram is set correctly. It will be in the intelligent tweaker section. Some ram requires 1.65 volts and others 1.5v, I have 1.65v ram and have always had to set this manually. Leave all other settings on auto.

[pepegonzales]

eep357, on 17 October 2012 - 03:37 PM, said:

unless you change something in the bios, then after the reset go back and the bios changed it's self back to how it was before, it's not the problem.

No reset's in Windows?
Try installing NullCPUPowerManagement.kext, if it stops the resets, we'll know it's a problem with native power management and then what to fix.

Also in bios, be sure voltage for your ram is set correctly. It will be in the intelligent tweaker section. Some ram requires 1.65 volts and others 1.5v, I have 1.65v ram and have always had to set this manually. Leave all other settings on auto.

Thanx again for the help.
Never had problems with windows7 before. (except that at this moment I'm uninstalling my datas to format the Windows7 disk for a apple format). This time, and for the first time, the system freezed.

I'm gonna give a try to NullCPuPowerManagement and make a check of the ram.

[eep357]

When back in OSX, also go to System Preferences>Energy Saver and move both sliders all the way to the right

[pepegonzales]

eep357, on 17 October 2012 - 04:19 PM, said:

When back in OSX, also go to System Preferences>Energy Saver and move both sliders all the way to the right

Done it... I've rebuilt the cache, permissions et restarted. Now it has past 10 minuts before doing another reset.
after that, I've used Multi**** 5.2 for the NullPCI. Repaired permissions and rebuilt cache.

8Gb Ram = 2 x Kingston KVR1333D3N9/4G : I've founded that this need a 1,5V supply but it is quite more compicated to be sure not modifying something wrong in the bios supply options. For the Ram, is it the QPI/DRAM CORE VOLTAGE or the Voltage DRAM BUS that I need to change to 1.5V?


EDIT: no reset since 30 minuts... NullPCI seems to works!!! In anycase, this is much more stable now!!! THANX!!!

EDIT: 1h30... and no reset... problem should be solved I think! Gosh I love this forum! Thanx eep357!!!

[eep357]

If you have 1.5v ram, don't worry about it, it's probably already set fine. Run with NullCPUPowerManagement for a day and see if it remains stable, then if it does, can look into properly enabling native power management and speedstep, maybe even sleep too