Contribute
Register

X58 and OS X El Capitan? (X58A-UD3r)

Status
Not open for further replies.
I notice I seem to be booting from a different config after I shut down clover. The second start of clover makes my windows 10 volume bootable and the Tonymac theme is in my monitor's native resolution. They no longer look squished. That is another thing... I can't figure out. There are at least 3 clover config.plists on my hard drive. Which one(s) matter?

Question - did you have Chimera with tonymacx86 theme installed previously?
Did you clean the Chimera from the drive before installing Clover?
Did you delete the /Extra folder from your OS X drive root?
If these things were not done, what is happening is that on exiting Clover it is rebooting with Chimera, which is legacy booting your Windows.
 

Attachments

  • SSDT.aml
    1.2 KB · Views: 165
Question - did you have Chimera with tonymacx86 theme installed previously?
Did you clean the Chimera from the drive before installing Clover?
Did you delete the /Extra folder from your OS X drive root?
If these things were not done, what is happening is that on exiting Clover it is rebooting with Chimera, which is legacy booting your Windows.

No this drive was wiped clean of all that. I wanted to go for a clean clover install of El Capitan. I did get it installed with this method and got audio going with the kexts in this thread. Even iMessage. Does the config.plist in the EFI partition matter or do I use the one in the folder? should I make all my clover folders the same?
 
No this drive was wiped clean of all that. I wanted to go for a clean clover install of El Capitan. I did get it installed with this method and got audio going with the kexts in this thread. Even iMessage. Does the config.plist in the EFI partition matter or do I use the one in the folder? should I make all my clover folders the same?

Your config.plist should be edited for your hardware.

Which folder? Which Clover folders?
 
I have a EVGA X58 SLI LE with Nvidia 280 I was able to boot the installer using the first config.plist in this thread with using the extra flags -x -v, but the system hangs without those. Even sleep seems to work within the installer. However, after the install if I try to boot with safe mode -x then the login screen will come up and the system reboots itself directly afterwards. I am unable to boot any other way or continue past at this point. Without using -x I get stuck at AppleTyMCEDriver: :start coreVIDPID = 0xffffffff Number of packages =1 Number of CPUs = 8 memory monitor through MCA.
 
The clover folder in the EFi partition and the clover folder in the Mac OS partition.
If the Mac OS partition is root, then you have Clover installed in Legacy mode - if you also have Clover installed in the EFI partition, you need to make up your mind how you want to boot: Legacy or UEFI.

Try this experiment - copy the EFI partition EFI folder to your desktop and delete it from the EFI partition.
Boot up. Will it now boot OS X and legacy Windows?

You need to delete either the Clover in the root or the one in the EFI partition - you do not need both.
 
Has anyone been able to get the USB 3.0 PCIe card to work with this motherboard? As soon as I plugged mine in, all the other USB ports stopped working. I could not use my keyboard or Bluetooth mouse.
 
Hey all X58 system owners, I need some ideas.

I have hit this panic when trying to boot into the freshly installed El Capitan after the “Boot OS X Install from MacHD” . Clover starts to load from the target drive and hits this error every time and reboots.

err.jpg


Yosemite 10.10.5 boots great with Clover using the same kexts and config.plist.

This is on my system:

Motherboard is MSI X58M
CPU is Xeon X5560 2.8GHz
Memory 6 GB 1066 MHz DDR3
GPU 9600 GT
System drive 160GB Maxtor HDD

Note this is my Mac Pro hack that has several drives with various versions of OS X built with UniBeast/MultiBeast/Chimera. These other drives have been removed for this activity with Clover where the target drive is partitioned with two partitions and Yosemite with Clover is up and running.

The project is to run the upgrade from Yosemite to El Capitan. The first El Capitan install portion runs well and completes, and upon the restart where the system should boot from the install target, it hits this error.

Note that I have run this same process on two of my other legacy systems and have not seen this problem. And I am using a form of the config.plist that Tony posted with the Nvidia set to be injected.

Ideas?

Good modding,
neil
 
Status
Not open for further replies.
Back
Top