Jump to content

itdoesnotwork

Members
  • Content count

    110
  • Joined

  • Last visited

About itdoesnotwork

  • Rank
    InsanelyMac Geek
  1. I finally managed getting my Fusion Drive Setup up and running with clover and yosemite. Thought I share my experiences: 1. My boot problems have been caused by a corrupted fusion drive. At least this is what it seems like. 2. When starting over, I was not able to delete / create Fusion Drive via Terminal in OS X Install. As soon as it started making changes to a core storage volume, my pc resetted. This corrupted FD even further, I had to manually write to both FD disks and the unlink them. So do not use Install OS X Media to create / split a Fusion Drive! 3. There is no complete guide on how to make the EFI partition of the Fusion drive bootable on a legacy BIOS board. You can't use clover installer on a Fusion drive. Thus I wrote down what worked for me: See this post Everything seems to be working now, using FakeSMC, Miezes Kext and Toledas patch. Sleep works, but also wakes after about 2 hours for a short time. Not using DSDT until now. Edit: I forgot I have some kind of "sound issue": after sleep, sometimes internal speaker out changes to "headphones" while no headphones are plugged in. It also stops output then until reboot. Ideas?
  2. itdoesnotwork

    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.
  3. itdoesnotwork

    Clover General discussion

    Thank you. "Something like that" is regrettably the problem I run into, because I'm not familiar with the boot files and needed terminal commands. Clover does not have boot0 in its files... @jamiethemorris already mentioned it. Fusion Drive is only a logical partition. The installer let's you choose partitions, not drives, and there is no EFI partition on the virtual FD drive. It also wouldn't know which FD member partition to choose, because clover installer can't figure out what's your BIOS boot drive... So I also tried copying the install to /EFI partition, also formatted it as FAT32. There still seems to be a problem in telling my board where clover is installed...
  4. itdoesnotwork

    Clover General discussion

    In case anyone wonders, theres problems seem to have been caused by a corrupted Fusion Drive Setup. After a complete reformat, Clover boots the FD like a charm. But: no I have the complete opposite problem: I cannot manage to load clover from Fusion Drive without the thumbdrive. There is plenty information on how to get it loaded in newer EFI boards, but I can't get the boot chain working on my old GA EX58-UD5. Could anyone point out how I can load Clover using the EFI Partition of one of the FD Drives formatted as FAT, EFI Folder and "boot" copied to the partition on a "legacy BIOS board"? The problem is, you can't use Clover installer, because it won't find the ESD but instead install it to the FD main directory. I can't get past boot0 / boot1 / .... errors.
  5. itdoesnotwork

    Clover General discussion

    Hi there, I'm fairly new to clover and try to find my way through it's logic... Is there a way to boot a Fusion Drive with an older non-UEFI board (-> BIOS; Gigabyte EX-58UD5) with clover installed on a thumbdrive? It does not seem to find the Fusion Drive, even with EFI/Clover folder copied to both EFI partitions and FD UUID added as default volume. Do I have to add "boot" to the EFI partition if I want to have clover ONLY on the tumbdrive so I don't break the chameleon bootloader installed on Fusion Drive (stored on seperate boot helper partitions)? Thank you!
  6. kext dev mode does not seem to do any harm. Could successfully boot into my recovery install using your clover settings and my current dsdt.aml. Don't know yet exactly what caused my problems and have to investigate. However, trying to install Yosemite results in an apple error report after install... Still did not manage to boot into my fusion drive install via clover on usb drive. All guides out there seem to be useless for non-UEFI boards. Only thing I did not try is installing the whole bootloader to the FD efi partitions, because I'm afraid I could loose access to chameleon. Don't know if this is a problem with the way my FD was made bootable by hackinstaller. Strange thing is that I only manage to get the Boot OS X helper partition (only 1 of them) to show in clover. Probably this is the problem, because clover only sees the "boot" files there and does not manage to make use of those partitions like chameleon does...
  7. So, now it is november meaning i have at (at least a little bit of) time to try the upgrade. Goal is to get clover running on a thumb drive and use it for my Mavericks Fusion Drive install, the do a upgrade to Yosemite. So far, no success with clover: can get into clover boot menu, but when booting i quits after loading mach kernel and states "error loading drivers". Booting my maintenance 10.9 install (non-fusion drive!) is more successfull, meaning it completes boot process without errors, then screen goes black and pc reboots -.- Any ideas on how to boot the fusion drive set up? Already added UUID to clovers plist - didn't help... What I did: - installed clover to Fat 32 thumbdrive - copied FakeSMC.kext to 10.9 / 10.10 folders - set boot flag (kext dev mode, verbose)
  8. Wow thanks for the quick answer So I think I'll move to clover too within the Yosemite update... Hope that Hackinstaller Script will support this bootloader at some future point. I really enjoy using it! Will have too look carefully into this though - I don't really want to screw my fusion drive up. BTW: I can remember you requested some logs on Fusion Drive some time ago. I somehow did not have the time - sorry. If you still require anything on this let me know and I'll try to gather the information during the update (in november). @jc84 Handoff is not only about iCloud sync, but your Mac should notify you of open apps on your iphone and offer you to continue directly. For me, this would be the most adorable feature of Yosemite, so I'll definitely do one thing or another to get this working!
  9. Support for 10.10. is really great news! Thank you for your effort - having the script supporting a new, critical update on day 1 is really incredible! @ROBASEFR so Clover seems to have significant advantages over chameleon for this release. Could you point out the differences between chameleon and clover at it's core? Seems like I missed that development. Is it just a different injection method allowing smoother updates or are there other differences (provided I still use EX-58UD5 and no EFI board). Did anyone have a look into handoff/continuity yet? Seems like there are different opinions on what is required to get this running on a hack. Is a WIFI adapter needed even if the devices are in the same network? Is bluetooth 4.0 LE sufficient or are only some devices supported? Any kind of kext-hack necessary and can it be injected with chameleon/clover? Seems like I will have to wait a little bit though since I use my computer in a productive environment...
  10. Updated to 10.9.4 - went smooth as usual. Needed to re-run kext installer in order to get sound back.
  11. Thanks MAJ for your detailed answers! Will try to support you with feedback. All issues so far are just cosmetically, my System is working 100% now - REALLY happy about this (sleep is so cool!) Thanks you so I know this is normal. Seems like I can't hide the second helper partition via chameleon though... Please see e-mail. This happens correctly. However, I wonder if /Extra also needs to be on the main Fusion Drive partition I can see in finder? (It is present there) As far as I understand, only boot helper partitions are relevant for boot. Please see mail. It seems to be possible to install to a wrong "ghost" target drive after "changing target". Now, that I now duplicate partitions in chameleon are correct behavior, it's not really relevant anymore. Please, see mail. Kind regards and thank you for all the support. Hackinstaller already achieved 99.9% perfection for me
  12. The components are still fine fore a hackint0sh installation. Corncerning your graphics card, ic can't help, but the rest of it will work quite OOTB if you follow this guide. Provided you only want a OS X installation so you can use GUID partition scheme, it's really rather simple. The script now is so stable and usable with this motherboard - really no miracle installing Mavericks. Personally, I prefer doing the first clean installation of an OS on an external hard drive though. I partition it as MBR (installer won't boot from GUID USB HDD) and create 2 partitions: 1 installer partition (this is where the boot cd created by the script goes) and 1 service partition (this is a clean OS X install). You can create all this from your running install - you have to make sure to patch the boot cd image though, to support install on an MBR HDD. You then boot the installer environment and install OSX to the second partition. If you have to install some kexts while getting a KP for example, you can always do this from the running installation. Once it works, the hardest part is done. You can now back up and delete your current installation. Then you just repeat the process and install to your final target drive. Now your USB install can serve as a service OS if something goes wrong. Finally, you should have a clean OS running. Provided you have a time machine backup, simply use built in migration assistent and transfer your data. With a little practice new installations, updates etc. are really no problem.
  13. Which version of the script are you running? What's your HDD setup? @Locus Good to hear it worked I can't exactly remember how I got my Appstore running again in Mavericks (it didn't accept my ID first). Regarding iWork download, I just created a spare user account on a real Mac with old iWork, "purchased" the new apps and swoosh - they appeared on my hackint0sh Remember you have to change system language to english temporarily.
  14. So sleep works for me now partially after enabling C and P states in bootloader. But I get a CMOS reset at first restart after sleep (system wakes correctly and works until i restart the mac). Hackinstaller analysis claims: Checking for required kexts: AppleLPC.kext is loaded. AppleHPET.kext is loaded. AppleIntelCPUPowerManagementClient.kext is loaded. All three required kexts are loaded! The following are relevant bootloader messages: Found ACPI CPU: CPU0 Found ACPI CPU: CPU1 Found ACPI CPU: CPU2 Found ACPI CPU: CPU3 Found ACPI CPU: CPU4 Found ACPI CPU: CPU5 Found ACPI CPU: CPU6 Found ACPI CPU: CPU7 Found ACPI CPU: CPU8 Found ACPI CPU: CPU9 Found ACPI CPU: CPUA Found ACPI CPU: CPUB Found ACPI CPU: CPUC Found ACPI CPU: CPUD Found ACPI CPU: CPUE Found ACPI CPU: CPUF SSDT with CPU C-States generated successfully P-States: min 0xc, max 0x15 SSDT with CPU P-States generated successfully The following are compiled from kernel.log messages: ./HackInstaller_Utilities.sh: line 357: /var/log/kernel.log: No such file or directory Checking AppleIntelCPUPowerManagement: Failed ./HackInstaller_Utilities.sh: line 357: /var/log/kernel.log: No such file or directory Checking LPC device: Okay P-States in the ioreg (decimal): 21 20 19 18 17 16 15 14 13 12 Installed kexts: FakeSMC, AppleRTC, JMicron36xSATA, IONetworkingFamily, ApleHDA, HDAEnabler1 Patched DSDT with hackinstaller - no errors. Applied iMessages and Sata fix when installing bootloader. Any suggestions? Edit: CMOS Reset was fixed by installing AppleRTC.kext to S/L/E instead of /Extra! Autosleep works too. Power management: Hard drives: checked; Wake on Ethernet: not checked; reboot on power failure: checked; Since sleep didn't work for me for a long time, IMO MBR partition scheme could possibly break sleep. Still can see duplicate "Fusion HD", they identify as hd(0,3) and hd(1,3), which are "Boot OS X" partitions. Also: should there be UUID applied to bootloader plist? Hackinstaller created boot-UUID flag, but did not apply UUID.
  15. Had a CMOS reset today to when trying to sleep manually. Didn't have that for a long time but installed a fusion drive too.. maybe 10.9.1 brought that back? I wonder what's the best method to get sleep working. Never succeeded since 10.5 or so. At least I now got Powermanagement and LPC kext to load. Do you use sleepenabler?
×