Jump to content

itdoesnotwork

itdoesnotwork

Member Since 06 May 2007
Offline Last Active Jul 21 2014 09:36 PM
-----

Posts I've Made

In Topic: [GUIDE] Scripted Retail Mavericks/Mountain Lion Install on Gigabyte Mobos

21 July 2014 - 09:37 PM

Updated to 10.9.4 - went smooth as usual. Needed to re-run kext installer in order to get sound back.

In Topic: [GUIDE] Scripted Retail Mavericks/Mountain Lion Install on Gigabyte Mobos

21 January 2014 - 08:36 PM

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!)
 

That's a feature, not a bug. :P Seriously, it's normal.
The bootloader is going to list/show all the helper partitions you can boot from. A RAID or FUSION drive will have, at minimum, two helper partitions and that's what you are seeing. The helper partitions are the actual partitions that contain the booting files, like the booter, kexts/kext cache/kernel cache, boot plist, DSDT, etc. The Finder will ignore them, as they don't contain user files.


Thanks you so I know this is normal. Seems like I can't hide the second helper partition via chameleon though...
 

Okay, two things:
1. You should only be able to choose ONE install target for the Fusion drive. So, that is working correctly.
2. The two "Fusion HD" showing up in the plist editor is a bug. The one with "(Fusion Drive)" should be the correct one.
Now, this is what I'd like to fix. However, it's really hard to script in support for a Fusion drive when you don't have one. So, getting feedback, like this one, really helps. If you can provide me your install log, that will be even more helpful. (#15 View logs; #6 Copy all logs to desktop; zip and send to digital (underscore) dreamer (at) mac (dot) com)


Please see e-mail.
 

The "Boot OSX" partition is the default name of the helper partition.
The script should be placing/installing the same /Extra files at the root directory of each helper partition.
If this is not happening, you will not be able to boot from that helper partition when you select it at the bootloader screen.
Let me know if you are experiencing issues here and provide your install log.


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.
 

Not sure I understand exactly what you are experiencing here. Can you elaborate on this further? What do you mean by 'installing correctly when not changing install target?' And, are you getting the "no OS installed" error on a drive that has the OS installed?


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.

 

For a Fusion drive setup, yes. Is that not happening?
If you are able to boot your Fusion drive setup, then the UUID is doing its job pointing the booter on the helper partition to the partition where the OS is installed.
What do you mean by creating a boot-UUID flag, but not applying the UUID? Note that UUIDs are used for different purposes. In this case, the boot UUID is used to identify the drive the OS is located on and should boot to. This is not to be confused with the Platform UUID, which is a unique identifier for your system.


Please, see mail.

 

Kind regards and thank you for all the support. Hackinstaller already achieved 99.9% perfection for me :)

In Topic: [GUIDE] Scripted Retail Mavericks/Mountain Lion Install on Gigabyte Mobos

06 January 2014 - 08:53 PM

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.

In Topic: [GUIDE] Scripted Retail Mavericks/Mountain Lion Install on Gigabyte Mobos

03 January 2014 - 05:22 PM

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.

In Topic: [GUIDE] Scripted Retail Mavericks/Mountain Lion Install on Gigabyte Mobos

27 December 2013 - 03:00 PM

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.

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy