Jump to content

OS X Yosemite DP's builds!


2,033 posts in this topic

Recommended Posts

I think +ira's guide is good.

Olarila's one (http://olarila.com/forum/viewtopic.php?f=35&t=4621#p41128) makes it more compatible with this little change:

 

fsck -fy
mount -uw /
nvram boot-args="kext-dev-mode=1"
chown -R 0:0 /kexts/*.kext
chmod -R 755 /kexts/*.kext
cp -R /kexts/*.kext /System/Library/Extensions
kextcache -m /System/Library/Caches/com.apple.kext.caches/Startup/Extensions.mkext /System/Library/Extensions
exit

 

Thanks for everybody that helped! 

Link to comment
Share on other sites

FakeSMC.kext NullCPUPowerManagement.kext obligatory, than VoodooHDA, Lan Card, Display Override , DVD Apple;

 

Clover drivers > http://cl.ly/image/3J2n1f0G243A

 

 

~40MB, uploading...

 

Here it goes... https://mega.co.nz/#!UAAxhTyR!h-ZtKN7N3nkO7filKvnnaxQ5vUS99k-VcdZ7tDuGYIg

Is it possible to use the boot args from the clover or chameleon, rather than the nvram thing?

I mean just add kext-dev-mode=1 to clover or chameleon.

It is strange. Several people in the Chinese forum succeed and others don't. I failed because of not loading the fakesmc...even we use the same one...

Link to comment
Share on other sites

Is it possible to use the boot args from the clover or chameleon, rather than the nvram thing?

I mean just add kext-dev-mode=1 to clover or chameleon.

It is strange. Several people in the Chinese forum succeed and others don't. I failed because of not loading the fakesmc...even we use the same one...

Then use booth i would suggest...

Link to comment
Share on other sites

I don't use the nvram thing. Added kext-dev-mode=1 to Clover config.plist arguments option and after change the kext permissions, before type exit kextload from /System/Library/Extensions/FakeSMC.kext!

<key>Boot</key>
   <dict>
      <key>Arguments</key>
      <string>kext-dev-mode=1</string>
   </dict>
  • Like 1
Link to comment
Share on other sites

Now I installed but got stuck here:

 

When I do this command:

mount -t hfs /dev/diskXsY /Volumes/temp

I got the Resource Busy error.

 

Of Course I changed X and Y to mine (disk3s2)

Link to comment
Share on other sites

I don't use the nvram thing. Added kext-dev-mode=1 to Clover config.plist arguments option and after change the kext permissions, before type exit kextload from /System/Library/Extensions/FakeSMC.kext!

 

<key>Boot</key>
   <dict>
      <key>Arguments</key>
      <string>kext-dev-mode=1</string>
   </dict>

The kextload did the trick!!! Thx

 

TO EVERYONE who has the ball spining problem just add in clover boot options: -v -s kext-dev-mode=1 and when younget to bash just type kextload /kexts/FakeSMC.kext then type exit :)

  • Like 1
Link to comment
Share on other sites

What exactly is the point of changing the name from mach_kernel to kernel? How strange... Just to confirm, any third party kexts will work without any boot flags after it's installed, it's just just the installer that doesn't load third party kexts right? Leave it to netkas to figure out how to get them working the day after it comes out! :-)

Link to comment
Share on other sites

What exactly is the point of changing the name from mach_kernel to kernel? How strange... Just to confirm, any third party kexts will work without any boot flags after it's installed, it's just just the installer that doesn't load third party kexts right? Leave it to netkas to figure out how to get them working the day after it comes out! :-)

The kext-dev-mode=1 flag is described by Apple in the release notes... (as well as the issues involving kernel cache).

  • Like 2
Link to comment
Share on other sites

The kext-dev-mode=1 flag is described by Apple in the release notes... (as well as the issues involving kernel cache).

Lol leave it to me to not realize that... Thanks rehabman.

 

 

Another thing i don't get, if the kexts just need to be in the kernel cache with that boot flag, how come injecting kexts into the kernel cache with clover doesn't work? Shouldn't that effectively be the same thing as having them in sle?

Link to comment
Share on other sites

Please check /usr/standalone/BootCaches.plist:

        <key>Kernelcache v1.3</key>
        <dict>
            <key>ExtensionsDir</key>
            <array>
                <string>/System/Library/Extensions</string>
                <string>/Library/Extensions</string>
            </array>
            <key>Path</key>
            <string>/System/Library/Caches/com.apple.kext.caches/Startup/kernelcache</string>
            <key>KernelPath</key>
            <string>/System/Library/Kernels/kernel</string>
            <key>KernelsDir</key>
            <string>/System/Library/Kernels</string>
            <key>Archs</key>
            <array>
                <string>x86_64</string>
            </array>
            <key>Preferred Compression</key>
            <string>lzvn</string>
        </dict>

The kernel uses kernelcache – for quite some time already – and not Extensions.mkext

  • Like 1
Link to comment
Share on other sites

installed Yosemite on top of Mavericks via the tutorials in this thread and removed the Intel HD kexts as they aren't compatible with my Celeron IGPU and makes OS X to not boot So no QE/CI and no GPU rendering, I've ordered an hd5450 to replace my broken one

 

The screen draws horribly slow as well as the mouse cursor (Mavericks was faster without GPU support!!!) You can see the windows/panels being rendered like an old 1990's computer  lol

 

The top menu is the same as mavericks instead of the flat one I saw on Yosemite shoots and the dock background color is white instead of the gradient (I hope  all of this is due to the lack of QE/CI)

 

post-767483-0-74636800-1401815098_thumb.png

Some dock icons (Launchpad, FaceTime, iTunes) are blank and PhotoBooth shows a question Mark   fixed after removing and reading them, Photo Booth is removed.

Sound doesn't work (VoodooHDA).

Clover shows two Macintosh HD icons, one of them just KPs the other boots Yosemite

Now instead of the apple logo screen at boot, only a black screen with a progress bar appears

 

I will keep an eye on all this :)

Link to comment
Share on other sites

8sCP9hl.jpg

 

This is where I get stuck after first boot after install.  Any ideas?  It just sits here...

If Caps Lock key works and/or the HD light shows activity then it's likely a graphic issue

 

In my case I had got the same with my unsupported Celeron G530 GPU and solved it by removing the Intel HD kexts,

Link to comment
Share on other sites

I managed to mount the necessary partition using the single mode and system is running.

 

We can use Kext Utility to install a new kext or is it better to do via single user mode like the instructions for FakeSMC and other essential kexts?

 

S1udBPb.jpg

 

7yGMI6m.jpg

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...