Contribute
Register

[Updated] Stork's Thunderbolt Build: i5-3570K | GA-Z77X-UP5-TH | GTX 760

Status
Not open for further replies.
Before updating, use MultiBeast for your current OS X to just change your System Definition to iMac14,2. We've found that SysDef works well. Matter-of-fact, iMac14,2 is the default SysDef for MultiBeast for Sierra.

Thanks Stork ... Final query I note that on the latest El Capitan you state to use:

:ch: Quick Start > UEFI Boot Mode <--- See page 3 of the MultiBeast Features document for the default items
:ch: Drivers > Audio Realtek ALCxxx > ALC898
:ch: Drivers > Disk > 3rd Party eSATA
:ch: Drivers > Misc > FakeSMC Plugins
:ch: Drivers > Misc > FakeSMC HWMonitor
:ch: Drivers > Network > Intel > AppleIntelE1000e <--- Use the latest version
:ch: Drivers > Misc > USB > 7/8/9 Series USB Support
:ch: Drivers > Misc > USB Increase Max Port Limit

With the Sierra test drive I haven't installed 3rd Party eSATA NOR any of the USB, even though they do exist in the Multibeast for Sierra, and don't seem to be having any issues. All USB ports seem to be working and same with the 3rd party SATA.
 
...
Mobo - gigabyte Z170x ud5th
...
This thread is for a different and older motherboard based system. Since I don't have your Z170 TH motherboard, I recommend you continue to seek help in other build descriptions and guide threads.

To properly set up a multi-booting system, see the Going Bald's sticky threads in the Multi-Booting forum section > https://www.tonymacx86.com/forums/multi-booting.153

Thanks Stork ... Final query I note that on the latest El Capitan you state to use:
...
:ch: Drivers > Disk > 3rd Party eSATA
...
:ch: Drivers > Misc > USB > 7/8/9 Series USB Support
:ch: Drivers > Misc > USB Increase Max Port Limit

With the Sierra test drive I haven't installed 3rd Party eSATA NOR any of the USB, even though they do exist in the MultiBeast for Sierra, and don't seem to be having any issues. All USB ports seem to be working and same with the 3rd party SATA.
Thanks for the update. Did you install Sierra over El Capitan or was it fresh install on your test drive?
 
Thanks for the update. Did you install Sierra over El Capitan or was it fresh install on your test drive?

A fresh install on test drive ... as I've been involved since Mountain Lion I've found the earliest versions are fraught with issues. So currently looking at doing a complete fresh install of El Capitan 10.11.6 as a stable base. Play with the Sierra recent install. Quick observation is that Sierra is slower but solves a few issues such as USB ports and a annoying audio pop on wake up.

I'll be spending time looking for issues and will give what observations and advice that I can.

Edit - Annoying audio pop still exists on sounds after wake up.
 
Last edited:
Great! I've been busy traveling and have only been updating my two 100-series motherboard systems. I'll get to this build next week. I'll do a fresh install on a test system with your above advise, then, once it works, I'll use Migration Assistant to bring over my applications and data files.
 
I will note that the two SATA non Intel controllers are labelled generic ... One being the onboard Marvell 88SE9172 and I also have an ASmedia 1601(?) 4 port. They seem to be operating correctly including trim when forced to enable.

Generic AHCI Controller:

Vendor: Generic
Product: AHCI Controller
Link Speed: 6 Gigabit
Negotiated Link Speed: 3 Gigabit
Physical Interconnect: SATA
Description: AHCI Version 1.20 Supported
 
Well, according to my User Manual:

USB
Chipset:
- Up to 2 USB 3.0/2.0 ports (available through the internal USB headers)
- Up to 6 USB 2.0/1.1 ports (2 ports on the back panel, 4 ports available through internal USB headers)

Chipset + 2 VIA VL810 Hubs:
- Up to 8 USB 3.0/2.0 ports (4 ports on the back panel, 4 ports available through the internal USB headers)

4 = 2x2
6 = 8x1
----
10

16 = 8x2
-----
26 total port count per Apple's method of treating USB port


So, increasing the port count to 30 is not inappropriate for our motherboard.
 
Well what an interesting couple of days. Firstly an apology ... I failed to notice that Stork's MultiBeast build included "eSATA" not "SATA". As I don't use eSATA I can't comment on the need with my Sierra test drive and our MB.

Now the last days. Having been on El Capitan I decided to do a clean install and use Multibeast as I had upgraded from Yosemite to get a clean reliable 10.11.6 install with the latest drivers rather than the original pre Multibeast build using the starting Clover package and composite kext installer. What a mistake. Despite having carbon copy clone and a time machine backup I had forgotten that I did a migrate from a smaller drive to a larger one and had no EFI clover setup on the 500Gb Samsung EVO 850 SSD that I used for the El Capitan main drive. Having worked that out and starting with a clean install, I re-partitioned the Samsung 850. Now the issue is ... MultiBeast WILL not install anything on this drive. Neither would a Clover bootloader install only.

I've been through every incarnation of attempts, confirm the right MultiBeast versions, mounted EFI before install attempts, etc. In the end, the only way around the issue is to continue was to boot off USB install, then use the original "smaller" 120 Gb Samsung 840 drive and I did a migration to get all the info onto the 850 and finally I have a working El Capitan system.

I have read everything I can regarding this and was wondering if anyone here can point me in the right direction to get the Clover bootloader onto the EFI partition of the 500 Gb EVO 850 drive preferably with the latest El Capitan Multibeast.

The only advantage is I did upgrade to the modified F12j BIOS from Tweaktowns and have found it to be much better in many aspects including boot screens in full res .. boot speeds etc.

Feeling very stupid and extremely frustrated ...

Edit - Got it going again. Copied original EFI over from backup El Capitan to clean rebuild. Now to get Imessage working again.
 
Last edited:
Before updating, use MultiBeast for your current OS X to just change your System Definition to iMac14,2. We've found that SysDef works well. Matter-of-fact, iMac14,2 is the default SysDef for MultiBeast for Sierra.

What happens to the previous board serial numbers, rom, Hardware UUIID etc... ?

Considering the requirements (at least previously) to get Messages & Face Time working etc..
 
Status
Not open for further replies.
Back
Top