Jump to content

Cosmin Petre

Members
  • Content Count

    155
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Cosmin Petre reacted to itdoesnotwork in Fusion Drive - Easy Step With Clover EFI   
    So, I tried to switch from chameleon to cover with my fusion drive setup. I found, that there is no complete guide for legacy BIOS boards, so I thought I might complete the first post:
     
    Making Clover bootable on Fusion Drive without UEFI
     
    Follow the guide above until 5.
    1. Format EFI partition of a FD member drive (1 is sufficient - I chose my main SSD) to FAT 32. Find the correct drive via diskutil list:
    diskutil list sudo newfs_msdos -v EFI -F 32 /dev/rdiskXs1 where X is the drive number of your SSD
     
    2. Mount EFI partition:
    sudo mkdir /Volumes/EFI sudo mount -t msdos /dev/disk0s1 /Volumes/EFI 2. Copy clover from your working USB install. In case you installed it to the EFI Partition of the usb drive mount it to a different directory (see step 2, use e.g. EFIUSB). Otherwise just copy the files like:
    sudo cp -r /Volumes/[USBDRIVE]/ /Volumes/EFI/ You can verify that everything went fine typing
    ls /Volumes/EFI/ and check if boot file, EFI folder and also usr folder are present. If not manually copy them using terminal
    sudo cp -r /Volumes/USBDRIVE/boot /Volumes/EFI/ sudo cp -r /Volumes/USBDRIVE/EFI /Volumes/EFI/ sudo cp -r /Volumes/USBDRIVE/usr /Volumes/EFI/ 3. unmount EFI partition
    sudo umount -f /Volumes/EFI/ 4. Make the EFI partition bootable, using the Clover files from your working USB install. diskX is again your desired boot drive
    fdisk440 -f boot0ss -u -y /dev/rdiskX fdisk440 -f /Volumes/[USBDRIVE]/usr/standalone/i386/boot0ss -u -y /dev/rdiskX dd if=/dev/rdiskXs1 count=1 bs=512 of=origbs cp /Volumes/[USBDRIVE]/usr/standalone/i386/boot1f32alt newbs dd if=origbs of=newbs skip=3 seek=3 bs=1 count=87 conv=notrunc dd if=newbs of=/dev/rdiskXs1 count=1 bs=512 cp BOOT /Volumes/EFI/ Restart and cross fingers
     
     
    I'm not entirely sure if every step is needed, but this is the procedure that worked for me. Please correct if I missed anything.
  2. Like
    Cosmin Petre got a reaction from @ROBASEFR in [GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos   
    I'd just like to say a massive THANKS from everyone on this forum MAJ. This script and your support has made hackintosh use a joy for many of us.
     
    It feels like an end of an era - but best wishes for the future.
     
    tom.

    Are we able to use Chimera 4.0 on Yosemite or is Chameleon the recommended bootloader? (I noticed 4.0 says it's Yosemite compatible but the install instructions recommend Chameleon)
  3. Like
    Cosmin Petre got a reaction from @ROBASEFR in [GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos   
    I'd just like to say a massive THANKS from everyone on this forum MAJ. This script and your support has made hackintosh use a joy for many of us.
     
    It feels like an end of an era - but best wishes for the future.
     
    tom.

    Are we able to use Chimera 4.0 on Yosemite or is Chameleon the recommended bootloader? (I noticed 4.0 says it's Yosemite compatible but the install instructions recommend Chameleon)
  4. Like
    Cosmin Petre reacted to digital_dreamer in [GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos   
    SCRIPT UPDATE:
    UPDATE: 10/8/14 - version 8.5.0
    Support for OS X 10.10 Yosemite: Lots of script changes were required, mostly dealing with the kernel path being changed from the drive's root directory to /System/Library/Kernels, as well as the kernel's default name from "mach_kernel" to "kernel". Much of the script has been rewritten and commented. Another issue creating more work is the new compression type used for the OS install packages and kernelcache. This means that the script is unable to unpack the install packages to extract the kernel, as is usually done. So, the vanilla kernel (version 14.0.0), located in Kernels, needs to be installed separately.
    Making Yosemite bootable in the Chameleon bootloader would not be possible without the dedication and hard work of a number of developers: Andy Vandijck, Pike R. Alpha, and MinusZwel, to mention a few.
    Enabling/disabling TRIM support for third-party SSDs has been added for OS X 10.10 Yosemite - located in Utilities. Check native power management status on running system in Utilities: Fixed some bugs and updated script to show Turbo Boost calculations for both Nehalem and Sandy Bridge/Ivy Bridge microarchitecture in log. Create Fusion drive: Reworked the confirmation reply to be safer. This is one area where mistakes cannot be tolerated. After confirmation, the selected drive(s) will be destroyed to create or defuse a drive. Updated VoodooHDA.kext to 2.8.5 for Mavericks. Updated FakeSMC.kext to 6.10.1323 for compatibility with OS X 10.10 Yosemite. Added and updated the following themes: Mavs, Mavs Style, Universe, idisplay, and LoginToLion. kind regards, MAJ
  5. Like
    Cosmin Petre got a reaction from iCore in [GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos   
    Icore- make sure you have Start up automatically after a power failure selected in system prefs > energy saving
  6. Like
    Cosmin Petre got a reaction from VirusX in [GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos   
    Can anyone shine any light on what it is that this plugin does? Any loss of functionality after removal?
  7. Like
    Cosmin Petre got a reaction from VirusX in [GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos   
    Works a treat here on ML - sleep, audio & power management all working fine.
     
    Re: Cruisar - I think he got himself a real Mac and left the Hack scene. His DSDT lives on though!
×