![]() ![]() : 07:48:35.753 gfxCardStatus _displayReconfigurationCallback_block_invoke_0() Notification: GPU changed. Here's the console and my actions from this morningħ/23/12 7:48:26.748 AM. as i mentioned in my original report on this thread, i was observing similar behavior with reeder. that's just the discrete-requesting app that i happen to leave running when i shut down the machine. and i don't think it is only path finder. is it possible that on the prior machine shutdown, gfxCS is leaving the card switching in some unusual state that messes up apps that would normally cause a switch to the discrete card and so sometimes on the next boot (depending on the load order, which would explain the intermittence of what i see), if path finder tries to start before gfxCS, it encounters that strange state and chokes, whereas if gfxCS loads first and takes over the dynamic switching then everything is ok? So given the order of things here with path finder hanging before gfxCS seems to have started loading. Energy saver pref pane confirms that graphics are on "Higher Performance". Path finder still hung, but i am able to start reeder, which is another app that wants the discrete card and which will not start if gfxCS is in the "stuck" state and set to dynamic switching, which leads me to conclude that even though the UI for gfxCS looks weird, the card has been switched. Menubar icon = i, menu indicates Discrete only, but identifies card as Intel HD Graphics 4000 : 08:25:19.315 gfxCardStatus - Setting Discrete only. Long pause (40 seconds) in startup after i log in and before the following lines hit the console - i think this is when path finder is trying to launch and hangs.ħ/21/12 8:19:45.137 AM. ![]() here are notes and console logs and an image of the gfxCS menu while it is in the "stuck" state. booted this morning and had the same issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |