|
04-17-2010, 01:19 PM
|
 |
|
|
Join Date: Apr 2009
Location: Tienen
Posts: 515
|
|
Quote:
Originally Posted by fxwizrd
Thank you for the new kernel. Everything seems to work fine.
Only I noticed that CPU frequency shows incorrectly in dmesg:
TSC: Frequency = 0.0000MHz, FSB frequency = 201.30763MHz, bus ratio = 10
Also I still get the following messages in the logfile:
CODE SIGNING: cs_invalid_page(0x1000): p=42[ptmd] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=45[loginwindow] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=43[mds] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=72[fontd] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=103[Dock] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=105[Finder] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=104[SystemUIServer] clearing CS_VALID
CODE SIGNING: cs_invalid_page(0x1000): p=108[fontd] clearing CS_VALID
Is it something bad and if yes what can be done about it?
Thanks,
FX
Edit: It also seems the reboot fix does not work well. I had to restore old OpenHaltRestart.kext in order to get machine restart automatically.
|
That is because the patched binaries still have code signatures inside.
I once released on InsanelyMac a tutorial on how to remove them from the binaries (No more clearing CS_VALID messages...)
I suppose those messages aren't the worst but if I had an AMD system I would patch up....
As for the rebooting problem: why not fix it with a customized FADT.aml ACPI table override?
|