Jump to content

10.10.1 - Hanging on boot - 30% of time


mickeyd453
 Share

11 posts in this topic

Recommended Posts

Hi

 

I am running a system that was upgraded from 10.8 > 10.9 and most recently to 10.10 and in fact now 10.10.1

 

Before moving to 10.10 it was super stable but since moving to Yosemite there are times when the machine hangs on boot and i have to power cycle it at which point it generally boots OK. Once booted it is 100% fine and stable. I would say the boot hangs occur maybe 30% of the time therefore 70% of the time its no problem. There are no differences during these random boot failures and no hardware is added or removed.

 

About the only thing i can see in the logs is the following and during a -v boot i noted this is where the machine seemed to hang, however succesful boots also seem to have this 'error'

MAC Framework successfully initialized
Nov 30 00:22:35 localhost kernel[0]: using 16384 buffer headers and 10240 cluster IO buffer headers
Nov 30 00:22:35 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Nov 30 00:22:35 localhost kernel[0]: ACPI: sleep states S3 S4 S5
Nov 30 00:22:35 localhost kernel[0]: pci (build 00:11:20 Sep 19 2014), flags 0xe3000, pfm64 (36 cpu) 0xf80000000, 0x80000000
Nov 30 00:22:35 localhost kernel[0]: waitForSystemMapper
Nov 30 00:22:35 localhost kernel[0]: Backtrace 0xffffff80008e5f54 0xffffff80008e6a64 0xffffff80008e72f6 0xffffff80008e9e1d 0xffffff7f82231245 0xffffff80008b57ed 0xffffff80008b530f
Nov 30 00:22:35 localhost kernel[0]: Kernel Extensions in backtrace:
Nov 30 00:22:35 localhost kernel[0]: com.apple.driver.AppleRTC(2.0)[B89EF128-7207-3CB1-B843-D0BE6499B7A7]@0xffffff7f8222f000->0xffffff7f82239fff
Nov 30 00:22:35 localhost kernel[0]: dependency: com.apple.iokit.IOACPIFamily(1.4)[70E2B65E-A91A-3522-A1A0-79FD63EABB4C]@0xffffff7f81909000
Nov 30 00:22:35 localhost kernel[0]: FakeSMC v6.11.1328 Copyright 2014 netkas, slice, usr-sse2, kozlek, navi, THe KiNG, RehabMan. All rights reserved.
Nov 30 00:22:35 localhost kernel[0]: FakeSMC: 13 preconfigured keys added
Nov 30 00:22:35 localhost kernel[0]: SMC: successfully initialized
Nov 30 00:22:35 localhost kernel[0]: RTC: Only single RAM bank (128 bytes)
Nov 30 00:22:35 localhost kernel[0]: [ PCI configuration begin ]
Nov 30 00:22:35 localhost kernel[0]: console relocated to 0xf89000000
Nov 30 00:22:35 localhost kernel[0]: mcache: 4 CPU(s), 64 bytes CPU cache line size
Nov 30 00:22:35 localhost kernel[0]: mbinit: done [96 MB total pool size, (64/32) split]
Nov 30 00:22:35 localhost kernel[0]: [ PCI configuration end, bridges 5, devices 14 ]

so i am not sure how relevant that error is but its about the only thing i can see thats 'wrong' - Any clues? I tried the 10.9.5 IOACPI rollback but it seems to make no difference.

 

thanks!

 

 

Link to comment
Share on other sites

You need to list, your hardware, cpu ,MB, Graphic

list your loader and loader version.

 

Current Clover is very good for older machine in MBR installation,

no so go with SOME UEFI machine.

 

Chameleon Current Version Ok for legacy machine.

 

I suggest you use.  Clover 2795 for UEFI

Chameleon 2510,  Clover 3033 for legacy machine.

Link to comment
Share on other sites

remove applertc kext from /s/l/e and install patched rtc kext,

delete fakesmc kext, nullapplecpupower management kext.

reinstall again  fakesmc kext for yosemite

and nullapllecpu power management kexts.

Evoreboot kext

 

delete kernel cache, use following command in teriminal

 

sudo rm -r /System/Library/Caches/com.apple.kext.caches

 

use kexthelper to rebuild caches, and reboot.

Link to comment
Share on other sites

Hi

 

Thanks for the help - When i removed AppleRTC.kext the machine would not boot at all even if i had ElliottForceLegacyRTC.kext installed. Is this the kext you were referring to when you say patched rtc kext? I restored that kext and i am back at the same error, even though the machine boots.

 

When i remove AppleRTC.kext the boot stops at the following

 

post-841024-0-99591800-1417732697_thumb.jpg

 

Thanks for any further advice!

 

Link to comment
Share on other sites

you do not want to list your HW and loader,

Let me guess,  installer with UNI-{censored},  I-{censored}, N-{censored}.

 

Since 27xx series,  Clover loader is able to boot legacy machine, without EVOreboot,  PatchedRTC.

 

Use Generic USB installation Guides. HERE.

Use Clover.

Link to comment
Share on other sites

Hi - Nope not censoring anything - bootloader is latest chameleon 2400:2404 according to chameleon wizard and it was installed via UNI-xxx as myhack 4 was not available, my usual method.

 

Hardware is 3.32 GHz Intel Core i5, 16 GB 1333 MHz DDR3, NVIDIA GeForce GT 610 1024 MB running on a Dell Optiplex 980 SFF

 

I have never played with clover and as everything runs good, generally, under chameleon then i thought i'd stick with that.

 

thanks!

Link to comment
Share on other sites

Once again, no hassle with Clover. I switched from Chameleon to Clover, less patching/hacking and everything runs even better than before. Clover is really good boot loader and will become even better. Clover provides very solid configuration system too. So, my suggestion, use Clover.

Link to comment
Share on other sites

Hi

 

Well i finally got around to trying clover - i installed it to replace Chameleon and now when i select boot OS X then the screen just goes blank.

 

Booting using verbose mode also produces nothing but a blank screen - This is booting from a USB HDD

 

All suggestions i have found so far dont get my far so any ideas?

 

cheers

Link to comment
Share on other sites

Well i can get it to boot but there is a huge delay from picking the disk to boot from and then actually the machine booting - like 20 minute delay

 

I will start a new thread on that one but interestingly the backtrace issue is still present so it seems clover does not help anyway

 

cheers

Link to comment
Share on other sites

Well i can get it to boot but there is a huge delay from picking the disk to boot from and then actually the machine booting - like 20 minute delay

 

I will start a new thread on that one but interestingly the backtrace issue is still present so it seems clover does not help anyway

 

cheers

 

You must make sure you are running clover with BIOS block access not SATA otherwise it takes forever to boot.

Link to comment
Share on other sites

 Share

×
×
  • Create New...