![]() |
I've seen too many of thoes, but in my system it seems fine, no slowdowns or hd activity and the messages still appears even when it's idle.
|
yes i think everyone is having these error but the question is why are they showing up what is causing them
|
I used to receive those messages sometime ago, but after updating to the latest kernel from the #10.5 channel on irc.osx86.hu and the latest AppleSMBios from Macdotnub, they have since disappeared. It's definitely worth a shot.
|
Interesting, because I am also running latest kernel (9.2.0 w/ shutdown fix) and AppleSMBios-27 from macdotnub. Oh, but which AppleSMBios exactly? There are many different ones for different RAM types and Mac identities. I am using the "default" one. Also, what are your specs?
|
Actually yesterday I upgraded AppleSMBios to the new version from netkas. The previous version I had installed was the hardcoded 667Mhz version. I'm also running the latest 9.2.0 with shutdown fix.
|
Ah, good to know. Haven't tried that one yet. I'll give it a spin right now.
|
Running the new AppleSMBIOS right now. Reported RAM speed is wrong of course, but that is always the case for me and Netkas' versions of the file. No biggie. Runs good. Can't say that it did anything for these "code signing" messages, but I think it did cut down on the number of mDNSresponder messages I'm getting, which would be a plus. I could be mistaken though.
|