Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Slow boot? Try this. If still slow, check your startupitems and launch daemon and launch agent folders for what is loading:


Clear the dynamic loader shared cache by booting one time is Safe mode.
Rebuild Kernel Extension Caches with a few terminal commands

The whole process will take you approximately 4 to 5 minutes to perform and you might just feel like your system is new again!

Step 1 : Clear the dynamic loader shared cache

So First: boot in safe mode by restarting your mac by holding the SHIFT key immediately after hearing the boot chime. When you reach the login window, don’t even log in, just hit restart.
Step 2 : Rebuild Kernel Extension Caches

Open a terminal window and type the following commands:

sudo chown root:admin /

(the system will ask your password to grant access to the sudo chown command as this requires admin privileges)

sudo kextcache -system-prelinked-kernel

sudo kextcache -system-caches

That’s all there is to it!

Where is this article from? I want to read it before messing around with terminal. Thanks
 
Where is this article from? I want to read it before messing around with terminal. Thanks


This has been around for years. I just googled "prelinked kernel" to quickly find it to paste here. people have been using this method here with no ill effects and it has helped some here and there with slow boot issues. It just clears out the kernel caches.

http://www.cnet.com/news/fix-slow-start-ups-in-os-x/

Here is some Apple Dev info on these commands:
https://developer.apple.com/library...rwin/Reference/ManPages/man8/kextcache.8.html
 
Feedback to Apple (and please do so before erasing information)

… they really should. yes they would have to wade through a lot of crud, but, there is a whole lot of valuable feedback here as well. ;)

We can't expect Apple to methodically process stuff from third party areas such as this. Feedback is best sent to Apple.

Unfortunately 50% of the machines are clean installs …

Worth remembering, people: performing a clean installation erases information that may be required by Apple. Before erasure, send feedback on the problem.
 
Apple continues to ask developers to focus their testing on Wi-Fi, Mail, and VoiceOver. Wi-Fi in particular has been an issue for some OS X Yosemite users since the operating system's October launch, and OS X 10.10.1 released in November failed to resolve all of those problems.

Article Link: Apple Seeds OS X Yosemite 10.10.2 Build 14C94b to Developers

I've noticed a couple of issues that don't seem to be making headlines.
1. I'm getting Read errors from the hdd frequently. This didn't happen with 10.10.1 Now usually that's caused by physical, hardware problems with the disk. But not always.

2. If I plug in my USB3 external HDD. Brand new drive, works fine, brand new self powered enclosure by Orico, it shuts down the WiFi. I mean stops it dead in the water. Only a reboot gets it back up. Doesn't seem to affect anything else.

otherwise - apart from lots of mysterious messages in the Console logging, it seems to be running fairly well. I wouldn't say it's stable - but seems to be ok.
 
1. I'm getting Read errors from the hdd frequently. This didn't happen with 10.10.1 Now usually that's caused by physical, hardware problems with the disk. But not always.
You should assume this is your disk failing. It's definitely not inherent in these 10.10.2 updates.

2. If I plug in my USB3 external HDD. Brand new drive, works fine, brand new self powered enclosure by Orico, it shuts down the WiFi. I mean stops it dead in the water. Only a reboot gets it back up. Doesn't seem to affect anything else.
USB 3.0 devices can interfere with 2.4 GHz wifi networks. You should try to move the disk further away from your computer, and/or switch the network to 5GHz if you can.
 
Mavericks

Mountain Lion. And Snow Leopard before then.

Having since done a clean install of Mountain Lion I must say it felt like a warm welcome to how things used to be for a decade. I used Mountain Lion fully for two days but encountered a few niggles that made me research Mavericks a little further.

Main issue is that in my small company we have been using iWork for many years and many documents got upgraded to the new iWorks 2013 (pages 5) format (pages.zip instead of .pages) and there is no way to install the latest version on Mountain Lion, sadly. This was the main reason to research Mavericks a bit further and I have since upgraded to Mavericks for the following reasons:
- supported OS
- supported current version of iWorks (and other applications)
- it's fast. The memory compression and other improvements make it run really well on my MacBook Pro C2D 2.4/8GB Ram/256SSD.

No glitches, no wifi issues - "It just works"tm.

For all the respect I have for Jonathan Ives as an industrial designer I must say the operating systems have taken a turn for the worse.

I buy the relatively more expensive Apple products precisely because they can last longer (and they do in my hands) and need less frequent upgrading which is a good thing. However Yosemite and IOS 8 are not up to the standard I have come to expect from Apple.
 
Safari is a disaster under Yosemite for me.
Crashes at least once a day versus never before under every other OSX
 
Safari is a disaster under Yosemite for me.
Crashes at least once a day versus never before under every other OSX

The only issue i've had with Safari in Yosemite (2012 Mac Mini) is the intermittent beach ball which requires a force close. A restart fixes it. It's been that way since day 1 on Yosemite.
 
The only issue i've had with Safari in Yosemite (2012 Mac Mini) is the intermittent beach ball which requires a force close. A restart fixes it. It's been that way since day 1 on Yosemite.

I've got that as well. Very frustrating that Apple hasn't come up with an update for this long.
Multi billion dollar company and they can't figure out something so basic. Pathetic
 
This seed solves the awaking problem that happened in my Macbook Mid-2012.
The only annoying problem that I still have is with the Exchange Server. I can't accept or declined an event from the mail.app (the buttons don't do anything) and in the calendar app the replies for the events are not sent.

Also, everytime I delete or move messages from my exchange account to a local folder and leave the exchange view and then get back to it, the messages return to this account.

Anyone else with these problems?

Where can I submit feedback to Apple
 
Last edited:

Attachments

  • ind.jpg
    ind.jpg
    9.4 KB · Views: 390
I consistently send feedback to Apple in the spirit of cooperation and good faith. Hearing from consistently calm fair customers will benefit everyone.
 
After reading through this thread I followed the advice of one of the posters regarding re-running the pre-linking of the kernel. When I did the Terminal came back with the fact that some plists were missing and that a kext from Sony was in the "hash exception list". The only thing I ever recall installing that was Sony related was a driver for a camera that I no longer have. Obviously, if I don't need it, I'd like to get rid of it.

The output from the Terminal is pasted below with X's and Y's obscuring the computer name.
Can someone have a look and let me know if the SONY KEXT is required for something that's standard to Apple and do I need to do something for the missing plist files?

If I should post this separately, where would that be?

XXXs-iMac:~ XXXYYYY$ sudo kextcache -system-prelinked-kernel
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
kext file:///System/Library/Extensions/SONYDeviceType01.kext/ is in hash exception list, allowing to load
XXXs-iMac:~ XXXYYYY$


XXXs-iMac:~ XXXYYYY$ sudo kextcache -system-caches
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
IOBluetoothHostControllerUARTTransport.kext has no Info.plist file.
JMicronATA.kext has no Info.plist file.
XXXs-iMac:~ XXXYYYY$


Thanks
 
Just to answer my own question

Mountain Lion. And Snow Leopard before then.

Having installed ML I must say I was happy to upgrade to Mavericks which proves rock solid on my MacBook Pro.

I am hoping now for a "no new feature but fix everything" release like Snow Leopard was. Leopard was slow and bloated, SL fixed that. We're there again with Yosemite.
 
I also got the "IOBluetoothHostControllerUARTTransport.kext has no Info.plist file" messages, but I just added the info.plist from my TM backup in the appropriate spot and the terminal stopped complaining about it. Not sure why the 10.10.2 info.plist file is missing for that bluetooth kext. Doesn't seem to hurt anything that I can tell.

Miltekk: you should be able to go into that directory and just delete the obsolete file:
System/Library/Extensions/SONYDeviceType01.kext
 
What WIFI Problems?

I have been testing Yosemite from the beginning of the new AppleSeed Beta testing program and I have yet experience any WIFI problems - connectivity, sleep reconnect, airplay skips, etc. I have installed the lastest Beta versions on two MacBook Airs and an aged iMac 2010.

I am using a Airport Extreme current model.

Am I alone in my Yosemite WIFI experiences?
 
Am I alone in my Yosemite WIFI experiences?
My wife got a new MacBook Pro for Christmas and her WiFi is rock solid. I don't understand why WiFi is such a problem for a lot of people. But I haven't updated my MackBook Pro or iMac because I am afraid. :D
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.