Jump to content

One last Problem.


21 posts in this topic

Recommended Posts

OK Now I have Mac OS X 10.6.2 working pretty nicely on my computer I have one really weird issue.

 

It doesn't necessarily mean it's a big problem, but Every time I boot into mac os x the screen shows up as blue... you can tell mac os x is running in the background but it's not showing it... My solution so far has been to press the power button, wait for sleep, then press the power button again and it wakes showing the desktop in all it's glory... I have full acceleration on my GT220 just this weird boot issue. Everything else works perfectly well on my HP Pavilion P6235uk.

 

I noticed it worked ok the first time it booted and the fans were quiet, but it was in 1024x768... so I went into display properties and changed the screen to my native 1280x1024 and the gfx card restarted and now the fans are on full with this problem every time it starts. very weird. changing it back down to 1024x768 doesn't rectify the issue.

 

So every time OS X starts, fans are quiet but blue screen, allow to sleep, wake it, fans louder but desktop showing.

 

BTW this is Hazard OS X 10.6.2... I didn't install the OS X server part though as that's optional.

Link to comment
Share on other sites

New problem that surfaced... I thought i'd go repair my disk permissions but it said "NO packages can be found for this disk"

 

Also when I try and run tinker tool it says

 

"Warning: The code verification Subsystem of this operating system is damaged"

 

43f629557d5305da80c56fe5499ed3a0.png

 

I'm stumped on that one, It's only ever showed up trying to launch tinkertool, any ideas?

 

Also Mac OS X 10.6.2 is reporting that my Core i5 750 is actually a 2.66GHz Quad-Core intel Xeon - I though 10.6.2 would understand a core i5 as it is a supported processor :) .

 

The good thing is it recognizes there are 4 cores... but it only really appears to be using the one of them... it reports 1 core as being 47*C whilst the other three cores it's saying are 100*C which is obviously wrong.

Link to comment
Share on other sites

Bump!

 

This start up issue is pretty annoying, ans also having no repair permissions in disk utility isn't that great.

 

Is the core i5 750 I have safe to be running at 40 - 50 *C? it seems warmer in OS X than windows.

Link to comment
Share on other sites

having no repair permissions in disk utility isn't that great.

That's normal, you can't repair permissions on a running system with Disk Utility, you need to boot from your OS X install DVD to do that.

 

The blue screen is caused by the Nvidia driver's display detection not working correctly on your configuration. You need to do some research on your "injection method" because that's where the problem is.

 

First make sure your primary display is plugged in to the output that's closest to the motherboard. Use a a DVI <> VGA adapter if you have to. After doing that, try booting with no other displays connected.

 

If it still does the blue screen thing, visit the Project OS X forums and read Krazubu's 'guide to all Nvidia boards'. There's also a lot of interesting information hiding in the NVEnabler release thread in the same forum. Experiment.

 

I have no ideas regarding the other stuff you mention.

Link to comment
Share on other sites

Thank you.

 

The Disk utility isn't normal, even booting from disk to repair permissions it gives the Error "No installer packages can be found for this disk"

 

The blue screen isn't too much of a problem. I didn't have to do anything to get my GT220 to work with this distro... I wil wait until I can get a new screen before trying anything, it may be looking for the DVI as you say, DVI is closest to the board on this card, HDMI in middle VGA on the outside.

 

I think with Tinkertool refusing to work could be because of incorrect permissions but I cannot repair the permissions even booting from the DVD.

 

0c64e1deef1aff07194ee4126c8a41b9.png

 

That may not be good, it doesn't understand my S-ATA controller, could that be causing the disk utility issues?

 

The board is an OEM MSI MS-7613 or in HP's terms an Indio-UL8E and I can't find what SATA controller it has or :/

Link to comment
Share on other sites

maybe you should take a look at your system log

 

if the system does not start up correct, messages should tell you that

( console > system log)

 

"unknown ahci" isnt a big thing, if it would not work, you wont see that window.

 

some install versions have the crazy behaviour to set wrong owners, respectively give the everyone owner special rights.

and then neither system nor you can save any changes to this files.

Link to comment
Share on other sites

Mar 18 15:57:14 Ricky-Mallorys-Mac-Pro shutdown[210]: reboot by inklin:

Mar 18 15:57:14 Ricky-Mallorys-Mac-Pro shutdown[210]: SHUTDOWN_TIME: 1268927834 310912

Mar 18 15:57:14 Ricky-Mallorys-Mac-Pro mDNSResponder[27]: mDNSResponder mDNSResponder-214.0.2 (Dec 15 2009 16:58:04) stopping

Mar 18 15:57:14 Ricky-Mallorys-Mac-Pro WindowServer[67]: hidd died. Reestablishing connection.

Mar 18 15:57:14 Ricky-Mallorys-Mac-Pro WindowServer[67]: bootstrap_look_ip failed: Unknown service name

Mar 18 15:57:31 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***

Mar 18 15:57:32 localhost com.apple.launchd[1]: *** Verbose boot, will log to /dev/console. ***

Mar 18 15:57:40 localhost bootlog[38]: BOOT_TIME: 1268927851 0

Mar 18 15:57:42 localhost mDNSResponder[27]: mDNSResponder mDNSResponder-214.0.2 (Dec 15 2009 16:58:04) starting

Mar 18 15:57:42 localhost com.apple.usbmuxd[20]: usbmuxd-176 built for iTunesNineDot on Sep 24 2009 at 16:11:05, running 32 bit

Mar 18 15:57:42 localhost iStatLocalDaemon[47]: Waiting for connections on port 5204.

Mar 18 15:57:44 Ricky-Mallorys-Mac-Pro configd[13]: setting hostname to "Ricky-Mallorys-Mac-Pro.local"

Mar 18 15:57:44 Ricky-Mallorys-Mac-Pro configd[13]: network configuration changed.

Mar 18 15:57:46: --- last message repeated 2 times ---

Mar 18 15:57:46 Ricky-Mallorys-Mac-Pro /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[28]: Login Window Application Started

Mar 18 15:57:49 Ricky-Mallorys-Mac-Pro configd[13]: network configuration changed.

Mar 18 15:57:58 Ricky-Mallorys-Mac-Pro loginwindow[28]: Login Window Started Security Agent

Mar 18 15:57:58 Ricky-Mallorys-Mac-Pro loginwindow[28]: Login Window - Returned from Security Agent

Mar 18 15:57:58 Ricky-Mallorys-Mac-Pro loginwindow[28]: USER_PROCESS: 28 console

Mar 18 15:57:58 Ricky-Mallorys-Mac-Pro com.apple.launchd.peruser.501[88] (com.apple.ReportCrash): Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self

Mar 18 15:58:00 Ricky-Mallorys-Mac-Pro com.apple.launchd.peruser.501[88] (com.apple.Kerberos.renew.plist[108]): Exited with exit code: 1

Mar 18 15:58:02 Ricky-Mallorys-Mac-Pro SystemUIServer[93]: MenuCracker 2.0 (/Library/Application Support/iStat local/extras/MenuCracker.menu)\n See http://sourceforge.net/projects/menucracker\n MenuCracker is now loaded. Ready to accept new menu extras. Ignore the failure message that follows.

Mar 18 15:58:02 Ricky-Mallorys-Mac-Pro SystemUIServer[93]: failed to instantiate and get the principal class of bundle: NSBundle </Library/Application Support/iStat local/extras/MenuCracker.menu> (loaded)

Mar 18 15:58:02 Ricky-Mallorys-Mac-Pro SystemUIServer[93]: MenuCracker: Allowing "iStatMenusTemps".

Mar 18 15:58:03 Ricky-Mallorys-Mac-Pro SystemUIServer[93]: MenuCracker: Allowing "iStatMenusCPU".

Mar 18 15:58:03 Ricky-Mallorys-Mac-Pro SystemUIServer[93]: MenuCracker: Allowing "iStatMenusDisks".

Mar 18 15:58:03 Ricky-Mallorys-Mac-Pro SystemUIServer[93]: MenuCracker: Allowing "iStatMenusMemory".

Mar 18 15:58:08 Ricky-Mallorys-Mac-Pro warmd[19]: [fetcher_open_file:936] open("/var/db/dyld/dyld_shared_cache_x86_64") => -1 (errno: 2)

Mar 18 15:58:08 Ricky-Mallorys-Mac-Pro warmd[19]: [fetcher_open_file:936] open("/var/db/dyld/dyld_shared_cache_i386") => -1 (errno: 2)

Mar 18 15:58:12 Ricky-Mallorys-Mac-Pro loginwindow[28]: loginwindow SleepWakeCallback WILL sleep

Mar 18 15:58:18 Ricky-Mallorys-Mac-Pro com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[81]): Exit timeout elapsed (20 seconds). Killing

Mar 18 15:58:18 Ricky-Mallorys-Mac-Pro com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[81]): Job has overstayed its welcome. Forcing removal.

Mar 18 15:58:18 Ricky-Mallorys-Mac-Pro com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow): Bug: launchd_core_logic.c:1111 (23932):0

Mar 18 15:58:44 Ricky-Mallorys-Mac-Pro configd[13]: network configuration changed.

Mar 18 15:58:50 Ricky-Mallorys-Mac-Pro loginwindow[28]: loginwindow SleepWakeCallback will power on, Currenttime:3/18/2010 3:58:50.003 PM - Waketime:3/18/2010 3:58:50.000 PM = Deltatime:0.002882063

Mar 18 15:58:53 Ricky-Mallorys-Mac-Pro mDNSResponder[27]: RegisterInterface: Frequent transitions for interface en0 (192.168.0.100)

Mar 18 15:58:53 Ricky-Mallorys-Mac-Pro mDNSResponder[27]: RegisterInterface: Frequent transitions for interface en0 (FE80:0000:0000:0000:4261:86FF:FE2D:DFF9)

Mar 18 15:58:58 Ricky-Mallorys-Mac-Pro configd[13]: network configuration changed.

Mar 18 15:58:58 Ricky-Mallorys-Mac-Pro configd[13]: Sleep: Success - AC - Power Button Sleep

Mar 18 15:58:58 Ricky-Mallorys-Mac-Pro configd[13]: Wake: Success - AC -

Mar 18 15:58:58 Ricky-Mallorys-Mac-Pro configd[13]: Hibernate Statistics

Mar 18 15:58:58 Ricky-Mallorys-Mac-Pro configd[13]: Kernel UserEventAgent com.apple.powermanagement.applicationresponse.timedout 30000 ms

Mar 18 15:59:09 Ricky-Mallorys-Mac-Pro ntpd[18]: time reset +0.873030 s

Mar 18 15:59:22 Ricky-Mallorys-Mac-Pro loginwindow[28]: spins were reported for this wake

 

Anything abnormal in that log?

 

I had to get rid of the cleanapp daemon as it was causing the log to be filled up as it was still running even though cleanapp was long removed.

Link to comment
Share on other sites

OK, I ran Geekbench 64-bit to see what kinda score it would give me and it gave a measly 3366 No way should a core i5 machine be way down that low should it?

 

Leads me to think something isn't right somewhere. Mac OS X thinks the processor is a quad core Xeon with 4 cores (but only appears to use the one even though it enables 4 at boot)... Geekbench thinks it's a Core i5 750 @ 2.66GHz which is correct, but it says 0 processors, 1 core which is obviously wrong.

 

Everything has been fine... I noticed the other day I hit 100% cpu usage and I looked at the iStat menus I have in the menu bar and the CPU image only showed 25% as if all 4 cores of my core i5 processor are working as they should be but mac OS X cannot see that. Activity monitor showed core 1 maxed out but no load on 2, 3 and 4. Mac os x didn't seem maxed out at all either. it was still running fast.

 

It also reports 1 core between 40 and 50 Celsius whilst the other 3 are stuck at 100 Celsius... something is bodged and I cannot think what - it's working as quite a fast computer but some things aren't quite as they should be.

 

Any Ideas?

 

EDIT: here's the geekbench result http://browse.geekbench.ca/geekbench2/view/230837

 

It says the RAM is DDR2 SDRAM when it's DDR3 so there's another issue.

Link to comment
Share on other sites

Did you fix the blue screen at startup problem?

I have the same problem with a completely different setup.

I also get round it the same way as you, after coming out of sleep I have to unplug and replug the keyboard.

Mike

 

I haven't yet but I don't notice it much as I usually just put the computer to sleep which it does perfectly.

 

My current screen is VGA and that is the furthest port away from the Mobo on the GT220 so I don't think it detects it at first and is looking for the DVI which is the closest port to the mobo.

 

My current screen is VGA so I'm hoping to buy a new screen with DVI compatibility and I'm hoping that is the fix I'm looking for.

 

I have not had the keyboard issue which you mention. I am using the HP wireless keyboard and mouse which come with my HP Pavilion P6235uk and they work out of the box with no issues for me on OS X, even volume controls on the keyboard work as expected!

 

----

@ kexic, I don't think that is the solution I'm looking for really. If I do reinstall these problems will most likely still be there. it has to be something else.

 

-----

 

EDIT: For some reason sleep has given quits on me now... I sleep the computer and 10 seconds to a few minutes later it wakes again - it doesn't do it every time, say 1 in 3 sleeps. strange though. :o

Link to comment
Share on other sites

Did you fix the blue screen at startup problem?

I have the same problem with a completely different setup.

I also get round it the same way as you, after coming out of sleep I have to unplug and replug the keyboard.

Mike

 

 

I have managed to fix this by connecting my monitor to the other output on my card.

 

Mike

Link to comment
Share on other sites

you need to restart with -x -v flag to reload all kexts,

then report the log

 

did you edit your dsdt ?

which kexts do you use in extra or SE ?

have you repaired permissions within running SnowLeo with kextutility ?

 

 

ioreg-explorer, you can see how many cores are registered and all other hardware

 

you must look for it, till you find it.

Link to comment
Share on other sites

here's a log from a boot with -v -x

Mar 24 13:54:04 Ricky-Mallorys-Mac-Pro shutdown[31745]: reboot by inklin: 
Mar 24 13:54:04 Ricky-Mallorys-Mac-Pro shutdown[31745]: SHUTDOWN_TIME: 1269438844 748679
Mar 24 13:54:05 Ricky-Mallorys-Mac-Pro mDNSResponder[28]: mDNSResponder mDNSResponder-214.0.2 (Dec 15 2009 16:58:04) stopping
Mar 24 13:54:05 Ricky-Mallorys-Mac-Pro WindowServer[66]: hidd died. Reestablishing connection.
Mar 24 13:54:05 Ricky-Mallorys-Mac-Pro WindowServer[66]: bootstrap_look_ip failed: Unknown service name
Mar 24 13:54:05 Ricky-Mallorys-Mac-Pro hdiejectd[15682]: processSIGTERM_DA: calling exit(0)
Mar 24 13:54:56 localhost com.apple.kextd[9]: Safe boot mode detected; invalidating system extensions caches.
Mar 24 13:54:36 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***
Mar 24 13:54:36 localhost com.apple.launchd[1]: *** Verbose boot, will log to /dev/console. ***
Mar 24 13:55:01 localhost bootlog[37]: BOOT_TIME: 1269438875 0
Mar 24 13:55:11 localhost com.apple.kextd[9]: Cache file /System/Library/Caches/com.apple.kext.caches/Directories//System/Library/Extensions/IOKitPersonalities_x86_64.ioplist.gz is out of date; not using.
Mar 24 13:55:12 localhost mDNSResponder[26]: mDNSResponder mDNSResponder-214.0.2 (Dec 15 2009 16:58:04) starting
Mar 24 13:55:12 Ricky-Mallorys-Mac-Pro configd[13]: setting hostname to "Ricky-Mallorys-Mac-Pro.local"
Mar 24 13:55:12 Ricky-Mallorys-Mac-Pro configd[13]: network configuration changed.
Mar 24 13:55:15: --- last message repeated 3 times ---
Mar 24 13:55:15 Ricky-Mallorys-Mac-Pro com.apple.usbmuxd[18]: usbmuxd-176 built for iTunesNineDot on Sep 24 2009 at 16:11:05, running 32 bit
Mar 24 13:55:23 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleLPC.kext - validation problems.
Mar 24 13:55:23 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleLPC.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:23 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AppleLPC failed; removing personalities.
Mar 24 13:55:23 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleSMBusPCI.kext - validation problems.
Mar 24 13:55:23 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleSMBusPCI.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:23 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AppleSMBusPCI failed; removing personalities.
Mar 24 13:55:23 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleProfileFamily.kext - validation problems.
Mar 24 13:55:23 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleProfileFamily.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:23 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.iokit.AppleProfileFamily failed; removing personalities.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load GeForce.kext - validation problems.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load GeForce.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.GeForce failed; removing personalities.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleIntelMeromProfile.kext - validation problems.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleIntelMeromProfile.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AppleIntelMeromProfile failed; removing personalities.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleHDAController.kext - validation problems.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleHDAController.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AppleHDAController failed; removing personalities.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AudioIPCDriver.kext - validation problems.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AudioIPCDriver.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AudioIPCDriver failed; removing personalities.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleHDAController.kext - validation problems.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleHDAController.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AppleHDAController failed; removing personalities.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleUpstreamUserClient.kext - validation problems.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleUpstreamUserClient.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AppleUpstreamUserClient failed; removing personalities.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleIntelNehalemProfile.kext - validation problems.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleIntelNehalemProfile.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AppleIntelNehalemProfile failed; removing personalities.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleIntelPenrynProfile.kext - validation problems.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleIntelPenrynProfile.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AppleIntelPenrynProfile failed; removing personalities.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load IOBluetoothSerialManager.kext - validation problems.
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load IOBluetoothSerialManager.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:24 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.iokit.IOBluetoothSerialManager failed; removing personalities.
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load IOSurface.kext - validation problems.
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load IOSurface.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.iokit.IOSurface failed; removing personalities.
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load IOSurface.kext - validation problems.
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load IOSurface.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.iokit.IOSurface failed; removing personalities.
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Can't load AppleTyMCEDriver.kext - validation problems.
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Failed to load AppleTyMCEDriver.kext - (libkern/kext) validation failure (plist/executable).
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro com.apple.kextd[9]: Load com.apple.driver.AppleTyMCEDriver failed; removing personalities.
Mar 24 13:55:29 Ricky-Mallorys-Mac-Pro /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[27]: Login Window Application Started
Mar 24 13:55:33 Ricky-Mallorys-Mac-Pro com.apple.fontd[54]: FODBCheck: foRec->annexNumber != kInvalidAnnexNumber (0)
Mar 24 13:55:36 Ricky-Mallorys-Mac-Pro loginwindow[27]: Login Window Started Security Agent
Mar 24 13:55:37 Ricky-Mallorys-Mac-Pro WindowServer[59]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 24 13:55:37 Ricky-Mallorys-Mac-Pro com.apple.WindowServer[59]: Wed Mar 24 13:55:37 Ricky-Mallorys-Mac-Pro.local WindowServer[59] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 24 13:55:44 Ricky-Mallorys-Mac-Pro warmd[17]: [fetcher_open_file:936] open("/var/db/dyld/dyld_shared_cache_x86_64") => -1 (errno: 2)
Mar 24 13:55:44 Ricky-Mallorys-Mac-Pro warmd[17]: [fetcher_open_file:936] open("/var/db/dyld/dyld_shared_cache_i386") => -1 (errno: 2)
Mar 24 13:55:45 Ricky-Mallorys-Mac-Pro SecurityAgent[72]: NSSecureTextFieldCell detected a field editor ((null)) that is not a NSTextView subclass designed to work with the cell. Ignoring...
Mar 24 13:55:45 Ricky-Mallorys-Mac-Pro loginwindow[27]: Login Window - Returned from Security Agent
Mar 24 13:55:45 Ricky-Mallorys-Mac-Pro loginwindow[27]: USER_PROCESS: 27 console
Mar 24 13:55:46 Ricky-Mallorys-Mac-Pro com.apple.launchd.peruser.501[75] (com.apple.ReportCrash): Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
Mar 24 13:55:53 Ricky-Mallorys-Mac-Pro SystemUIServer[80]: 	MenuCracker 2.0 (/Library/Application Support/iStat local/extras/MenuCracker.menu)\n	See http://sourceforge.net/projects/menucracker\n	MenuCracker is now loaded. Ready to accept new menu extras. Ignore the failure message that follows.
Mar 24 13:55:53 Ricky-Mallorys-Mac-Pro SystemUIServer[80]: failed to instantiate and get the principal class of bundle: NSBundle </Library/Application Support/iStat local/extras/MenuCracker.menu> (loaded)
Mar 24 13:55:53 Ricky-Mallorys-Mac-Pro SystemUIServer[80]: Could not load menu extra NSBundle </System/Library/CoreServices/Menu Extras/Volume.menu> (not yet loaded)
Mar 24 13:55:53 Ricky-Mallorys-Mac-Pro SystemUIServer[80]: MenuCracker: Allowing "iStatMenusTemps".
Mar 24 13:55:53 Ricky-Mallorys-Mac-Pro com.apple.launchd.peruser.501[75] (com.apple.Kerberos.renew.plist[95]): Exited with exit code: 1
Mar 24 13:55:56 Ricky-Mallorys-Mac-Pro SystemUIServer[80]: MenuCracker: Allowing "iStatMenusCPU".
Mar 24 13:55:56 Ricky-Mallorys-Mac-Pro SystemUIServer[80]: MenuCracker: Allowing "iStatMenusDisks".
Mar 24 13:55:56 Ricky-Mallorys-Mac-Pro SystemUIServer[80]: MenuCracker: Allowing "iStatMenusMemory".
Mar 24 13:56:00 Ricky-Mallorys-Mac-Pro mds[25]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputerIndexed"
Mar 24 13:56:06 Ricky-Mallorys-Mac-Pro com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[67]): Exit timeout elapsed (20 seconds). Killing
Mar 24 13:56:06 Ricky-Mallorys-Mac-Pro com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[67]): Job has overstayed its welcome. Forcing removal.
Mar 24 13:56:06 Ricky-Mallorys-Mac-Pro com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow): Bug: launchd_core_logic.c:1111 (23932):0
M

 

I tried to use ioreg-explorer in xcode but for me it keeps freezing and I have to force quit it.

 

I didn't edit a DSDT as I haven't really needed to yet...

Link to comment
Share on other sites

I had to reinstall just recent for some reason.. I was just casually using the computer and then finder froze, relaunched it and it would no longer open, so I rebooted and got a KP on boot - it was fine before and nothing had changed which is the weird thing.

 

Since reinstalling I've had to install no extra kexts as I found the ones I needed on the iHazard 10.6.2DVD and checked them... Disk utility is still broken (No packages found for the disk) and OS X still appears to only be using a single core even though it has enabled all 4. :)

Link to comment
Share on other sites

I have all 4 cores working now... I was wondering why it wouldn't work. I looked in the boot file within S/L/E and there was nothing in it so then something 'clicked'... I looked in my extra folder and behold.... another boot file that must be the one OS X is using... in there it had -v cpus=1 ... I removed those entries and I now have all 4 cores working.

 

The other day I updated to 10.6.3 and it was a success, even more of a success than I thought it would be! Permission fixing now works in disk utility and I no longer get a blue screen when booting requiring a sleep.

 

I couldn't be happier right now.

Link to comment
Share on other sites

Hi Rick,

 

I have the same computer as you, and I have the same DVD in front of me. Before I give this a go, would you be kind enough to inform me of what drivers etc you chose during install?

 

Also, are there any BIOS considerations on this machine?

 

Bjorn

 

I had to reinstall just recent for some reason.. I was just casually using the computer and then finder froze, relaunched it and it would no longer open, so I rebooted and got a KP on boot - it was fine before and nothing had changed which is the weird thing.

 

Since reinstalling I've had to install no extra kexts as I found the ones I needed on the iHazard 10.6.2DVD and checked them... Disk utility is still broken (No packages found for the disk) and OS X still appears to only be using a single core even though it has enabled all 4. ^_^

Link to comment
Share on other sites

  • 2 weeks later...

I am very sorry about not replying for a while BjornAn, I forgot about this topic.

 

There are few considerations when it comes to the BIOS, the only thing I have had to change as is the case for many (if not all) is setting the SATA Mode from RAID to AHCI.

 

I chose:

Chamaleon RC4 bootloader

I also selected the option "Graphicsenabler=y"

 

you also need the select the option that prevents it rebooting in a loop, I can't remember what it's called because I haven't reinstalled snow leopard in a while now.

 

The kexts I have are:

RealtekR1000SL.kext for your Ethernet

Sleepenabler.Kext

FakeSMC.kext - v2.5 (Needed by everyone otherwise it will not boot as FakeSMC emulates the SMC device in apple computers)

 

I removed NullCPUPowerManagement.kext (EDIT:) I had to put it back in the end. I found it to be causing choppy youtube video without it, once I put it back everything was normal again.

 

Only thing I am having HUGE difficulties with is sound right now, it worked perfectly in 10.6.2 but in 10.6.3 the kext I was using kept KP'ing and I haven't found a working solution since, apart from voodooHDA which isn't overly impressive right now.

Link to comment
Share on other sites

Disk Utility Permission fix error – If you get this error in Disk Utility , “ No Installer packages can be found for this disk” whenever you want to verify permission and fix permission. This is caused when you run Snow Leopard installer within Leopard itself. Its a simple fix. You’ll have to re-run BSD.pkg , it could be found in /Volumes/Mac OS X Install DVD/System/Installation/Packages or /Volumes/OSX86/System/Installation/Packages . Just run it and voila it should be fixed ! Now you can use Disk Utility to repair permissions ! This can be found here.

Link to comment
Share on other sites

Disk Utility Permission fix error – If you get this error in Disk Utility , “ No Installer packages can be found for this disk” whenever you want to verify permission and fix permission. This is caused when you run Snow Leopard installer within Leopard itself. Its a simple fix. You’ll have to re-run BSD.pkg , it could be found in /Volumes/Mac OS X Install DVD/System/Installation/Packages or /Volumes/OSX86/System/Installation/Packages . Just run it and voila it should be fixed ! Now you can use Disk Utility to repair permissions ! This can be found here.

 

Good tip!

 

my disk utility fixed itself when I upgraded to 10.6.3 so all is good for me now :unsure:

Link to comment
Share on other sites

 Share

×
×
  • Create New...