Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Resolved OS X Yosemite on Unsupported Macs [Guide]
- Thread starter TMRJIJ
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
imessages facetime
hola mi nombre es fran,tengo un macbook 2008 blanco instalado yosemite ,tengo problemas con imessages y facetime,dices que tu lo tienes todo bien , me podrías decir como lo hiciste,gracias
Call Apple support, provide the Macbook's serial number, explain that Yosemite was installed using our guide and that iMessage isn't working and provide the validation code. Apple then unblocks your Macbook, allowing iMessage and FaceTime login immediately and in the future updates without other issues.
Llame al soporte de Apple, proporcionar el número de serie de la Macbook, explique que Yosemite se instaló con nuestro guía y que iMessage no está funcionando y proporcione el código de validación. Apple y luego desbloquea tu Macbook, permitiendo iMessage y FaceTime acceso inmediato y en las futuras actualizaciones sin otras cuestiones.
Unfortunately, Maps does not work well without support for the new OpenGL framework. You can however use the app to send directions to other devices but that's just how useful it will be on your model. Other bugs are stated in Post 1
Desafortunadamente, Mapas no funciona bien sin el apoyo al nuevo marco OpenGL. Sin embargo, puede utilizar la aplicación para enviar direcciones a otros dispositivos, pero eso es lo útil que será el modelo. Otros errores se indican en Post 1
Audio Card Not Working on MacBook 4.1
I tried everything I could, follwing the guide and following others, but I still have troubles with Audio Card, which is not working at all, not with AppleHDA.kext nor with VoodooHDA.kext
The VoodooHDA app doesn't seem recognize any VoodooHDA device.
Any help would be much appreciated.
Thank you for the guide
EDIT: Just reinstalling AppleHDA.kext and IOAudioFamily.kext it actually works but only with headphones. That's odd.
I tried everything I could, follwing the guide and following others, but I still have troubles with Audio Card, which is not working at all, not with AppleHDA.kext nor with VoodooHDA.kext
The VoodooHDA app doesn't seem recognize any VoodooHDA device.
Any help would be much appreciated.
Thank you for the guide
EDIT: Just reinstalling AppleHDA.kext and IOAudioFamily.kext it actually works but only with headphones. That's odd.
Last edited:
I tried everything I could, follwing the guide and following others, but I still have troubles with Audio Card, which is not working at all, not with AppleHDA.kext nor with VoodooHDA.kext
The VoodooHDA app doesn't seem recognize any VoodooHDA device.
Any help would be much appreciated.
Thank you for the guide
EDIT: Just reinstalling AppleHDA.kext and IOAudioFamily.kext it actually works but only with headphones. That's odd.
Go to System Preferences > Sound > Output then change the output to Complex . Go back to System Preferences and play around with the complex settings in the VoodooHDA Pref pane
I was hoping to upgrade my late-2008 MacBook to Yosemite, but after reading this thread I'm doubtful that doing so will leave me with the level of usability I want from my main computer. Just to double check, though: do the problems people are listing here (inability to use sleep function normally, play videos in VLC, etc.) occur on all machines with GMA graphics cards or just those that can't support 64bit operating systems?
These issues normally occur with all machines without Graphics Acceleration. We are always editing the guide in Post 1/Post 2 with ways to work around these limitations however until us or someone else figures out how to make full OpenGL support work without WindowsServer crashes during startup, you'll have to work with what we got here in this thread.
There was a post somewhere that has a link to an app that prevents your Macbook from sleeping and I will have add additional list of terminal commands to disable all excess animations soon.
Wow, thanks for the fast reply. I'm assuming that "all machines without Graphics Acceleration" includes all machines with GMA graphics cards. Am I right to assume that? I'm a little confused because some of the problems are being talked about as 64-bit kext issues, and while I'm pretty sure my MacBook can run the 64-bit EFI, I thiiink the issue with the kexts is not solely a problem for 32-bit EFI users but for all users with older graphics cards. Again, correct me if I'm wrong.
For me, deal-breakers that would prevent me from upgrading include:
It sounds like at least a couple of these issues are going to be around for the foreseeable future on machines like mine, though. Am I understanding correctly? And if so, do you happen to know if Mavericks can be installed on unsupported Macs without some of these issues?
For me, deal-breakers that would prevent me from upgrading include:
- No video in programs like DVD Player or VLC
- Inability to adjust screen brightness
- Inability to put computer to sleep normally
- Significant slowness
- Ugly/broken graphics
It sounds like at least a couple of these issues are going to be around for the foreseeable future on machines like mine, though. Am I understanding correctly? And if so, do you happen to know if Mavericks can be installed on unsupported Macs without some of these issues?
You are correct. The 64 bit kexts, we and hackerwanye provide are beta kexts from Snow Leopard which Apple dropped later on. Although your model won't need Tiamo's boot.efi because it already supports 64-bit EFI, your Integrated Graphics (GMA) is the real issue here. Mavericks will be the same way.
DVD not working at all, Audio kext working but only with headphones
Hi, I had to install again VoodooHDA.kext because for some reason it was unloaded. It's impossible to hear anything with the speakers, because either you have very low volume to the speakers or they begin to emit high frequency whistle. We are currently using headphones and external speakers.
Instead, we have big issues concerning power management and expecially the DVD drive. Any suggestion in how to fix at least the DVD drive?
Hi, I had to install again VoodooHDA.kext because for some reason it was unloaded. It's impossible to hear anything with the speakers, because either you have very low volume to the speakers or they begin to emit high frequency whistle. We are currently using headphones and external speakers.
Instead, we have big issues concerning power management and expecially the DVD drive. Any suggestion in how to fix at least the DVD drive?
Hello,
When your speakers emit high frequency whistle, you must use VoodooHDA to readjust the microphone volume.
We will look into your power management problem.
On the subject of audio, I got all the audio working perfectly on a MacBookAir1,1 without using VoodooHDA. (after many attempts at that route!)
I have an original Snow Leopard install disc, so using remote disc from my MBP I grabbed the Snow Leopard versions of AppleHDA.kext and IOAudioFamily.kext and loaded those into the Yosemite install using Kext Utility. Once complete I rebooted and presto, audio input/output working perfectly and correctly displayed as "Internal Speakers" within System Prefs.
If only it was that simple for sleep/wake and graphics acceleration!
Even with the problems, 10.10.1 runs much faster than 10.7.5 on the Air! Just have to remember not to let it sleep if it's being used...
I have an original Snow Leopard install disc, so using remote disc from my MBP I grabbed the Snow Leopard versions of AppleHDA.kext and IOAudioFamily.kext and loaded those into the Yosemite install using Kext Utility. Once complete I rebooted and presto, audio input/output working perfectly and correctly displayed as "Internal Speakers" within System Prefs.
If only it was that simple for sleep/wake and graphics acceleration!
Even with the problems, 10.10.1 runs much faster than 10.7.5 on the Air! Just have to remember not to let it sleep if it's being used...
On the subject of audio, I got all the audio working perfectly on a MacBookAir1,1 without using VoodooHDA. (after many attempts at that route!)
I have an original Snow Leopard install disc, so using remote disc from my MBP I grabbed the Snow Leopard versions of AppleHDA.kext and IOAudioFamily.kext and loaded those into the Yosemite install using Kext Utility. Once complete I rebooted and presto, audio input/output working perfectly and correctly displayed as "Internal Speakers" within System Prefs.
If only it was that simple for sleep/wake and graphics acceleration!
Even with the problems, 10.10.1 runs much faster than 10.7.5 on the Air! Just have to remember not to let it sleep if it's being used...
We will look into the original sound Kexts today and test multiple models. What version of Snow Leopard did yours come from?
The sleep issue can be 'kinda' remedied with the NoSleep extension. it will prevent your Macbook from turning off the display when closing the screen lid.
They came from an original 10.6 retail disc.
Edit: would this solution work for the sleep/wake issue? Seems to work for the hackintoshers?
Last edited:
The solution I see there involves works for hackintosh users. We have real Macs built to run these UNIX based operating system. This solution will likely not work.
OSXH update available now.
The Update will include:
- NoSleep Extension
- New AppleHDA.kext that fixes the No Sound Issues for all older Macbook Models. (Mac Mini and Mac Pro models need more testing)
- ATI Radeon X1600 kexts
- New Boot.efi for Mavericks
Addresses Issues with Power Management and Battery Issues
Last edited:
I don't pretending understanding everything in that thread but it may be a similar issue.
My understanding is that our Macs do support power management in Yosemite, the issue being that the beta graphics drivers don't properly handle the wake event and the screen remains black, even though the machine has properly waken up. At least that is what appears to happen on my late 2007 MacBook. If that's indeed the issue we're back to the beta graphics driver problem, which is unlikely to be ever solved.
No Sleep works a treat, thanks!
Finally took the plunge, backed up Lion, erased the internal drive and permanently moved the Air over to Yosemite. Removing the animations from Mission Control and Launchpad has made them both very usable (not that I ever really use launchpad anyway!)
Overall I find the little old MacBook Air to run 10.10.1 adequately, but it struggles with video content. It is capable of mirroring the screen/extending the desktop to my AppleTV with AirParrot, and audio Airplay is already natively supported.
Now that I have played with it for a while, I think the next step is to throw in a 128GB SSD. As well as the benefits in booting/loading applications, I'm hoping it will speed up general operation due to much faster virtual memory.
You don't think there would be any way to modify OpenGL.Framework to enable hardware acceleration do you? I recall reading something about MLforAll doing something of that nature with Mountain Lion to enable QE/CI.
Finally took the plunge, backed up Lion, erased the internal drive and permanently moved the Air over to Yosemite. Removing the animations from Mission Control and Launchpad has made them both very usable (not that I ever really use launchpad anyway!
)Overall I find the little old MacBook Air to run 10.10.1 adequately, but it struggles with video content. It is capable of mirroring the screen/extending the desktop to my AppleTV with AirParrot, and audio Airplay is already natively supported.
Now that I have played with it for a while, I think the next step is to throw in a 128GB SSD. As well as the benefits in booting/loading applications, I'm hoping it will speed up general operation due to much faster virtual memory.
You don't think there would be any way to modify OpenGL.Framework to enable hardware acceleration do you? I recall reading something about MLforAll doing something of that nature with Mountain Lion to enable QE/CI.
No Sleep works a treat, thanks!
Finally took the plunge, backed up Lion, erased the internal drive and permanently moved the Air over to Yosemite. Removing the animations from Mission Control and Launchpad has made them both very usable (not that I ever really use launchpad anyway!
Overall I find the little old MacBook Air to run 10.10.1 adequately, but it struggles with video content. It is capable of mirroring the screen/extending the desktop to my AppleTV with AirParrot, and audio Airplay is already natively supported.
Now that I have played with it for a while, I think the next step is to throw in a 128GB SSD. As well as the benefits in booting/loading applications, I'm hoping it will speed up general operation due to much faster virtual memory.
You don't think there would be any way to modify OpenGL.Framework to enable hardware acceleration do you? I recall reading something about MLforAll doing something of that nature with Mountain Lion to enable QE/CI.
MLforAll had a beta of the OpenGL.framework for Mavericks and Yosemite that we been looking at for a couple of months. It is now available on MacPostFactor and we'll release it in the next update in post 1 soon. It will likely cause WindowServer crashes immediately at the login screen so we encourage only people who know what their doing (I.e. Developers) to work on it.
Awesome. I'll give it a whirl when released.
Edit: I'm not a developer by any sense of the word, but I have 4 bootable installs available for the Air, plus my MBP if something goes catastrophically wrong! I'll update here how I get on with it
Following on from my comment above about changing the drive, I unloaded com.apple.dynamic_pager and removed the swap file - this has resulted in a much swifter experience. Not really relevant if you have over 4GB RAM or you already have a fast HDD or SSD, but with a 4200rpm HDD it makes quite a difference.
Completely disabling Spotlight is another thing that really freed up resources. mdworker and mds_stores were consistently gobbling up over 40% of available processing power and generally a significant amount of memory.
I did find it quite comical when trying to explain to AppleCare why I needed them to enable iMessage. For some reason he couldn't wrap his head around the fact that the Mac with that serial number was running Yosemite. He was a very nice guy though, so I gave him a glowing review!
Last edited: