Jump to content

OS X compatible motherboard -> QUO

meklort

By meklort,
in New Releases and Updates

 Share
4,397 posts in this topic

Recommended Posts

dwdrummer0
dwdrummer0
Posted
Posted

Decided to take on a partition with El Capitan since updating to most updated BIOS. Installed from USB Drive and booted right into 10.11.2 without any issues. Even installed 10.11.3 beta 1 on top of 10.11.2 and everything booted up great. Very nice!! 

 

Edit: did a migration over from Mavericks and now El Capitan will not boot. Working on the issue..

 

Edit: Reinstalled OS over migration and all is well. Still testing

Link to comment
Share on other sites
^andromedar^
^andromedar^
Posted
Posted

Folks, I need to ask the community for a bit of help. Has anybody of you folks run into issues with connected drives (either SSD or HDD) that got corrupted? 

 

I have spent the better part of the new year holidays reformatting drives and trying to restore info from different backups. I have tried several different SDDs after the first has been beyond what diskutil could repair (a120GB OWC SDD) and after a while they all came out as corrupted after the system freezing.

 

I have tried our both the X-Mass BIOS and the Z77MXQUOAOS.H3C.1669M.ROM to see if that would change the behaviour, but it did not (last trial was with the 1669M). Of course the usual things (exchanging SATA cables, checked RAM) has been done.   

 

I do remember I had a similar issue way back then, when I got the board, but in the meantime it was behaving very well so I had plainly forgotten about the issue. Is there any way to triage the onboard SATA controller?

 

The reason for me to have and love this system is to dual boot it with a highly customized Linux and run it with OS X SL alternatively.  

 

Any hints would be highly appreciated!

Link to comment
Share on other sites
Bernard Leclerc
Bernard Leclerc
Posted
Posted

Hi  and Happy New year to @ll !

 

I have been using this board since 2013 in OSX mode only without problem. A few days ago, I gave my Windows tower to my daughter who had an older system. I kept the Windows SSD with Windows 10 installation wishing to use it as a dual system. So, yesterday, after disconnecting both my drives in my OSX tower, I tried to connect my Windows SSD. IT did not work. I guess it was not the way to go. So I decided to go back to my old setting and took out the Windows SSD. I then reconnected my OS X SSD and my data disk. It did not boot to OSX and booted to Shell. I did not know what to do and after tinkering in the bios without success, I went back to original settings, and went back to Shell booting. I decided to try exiting from Shell with exit command and it worked. System booted to OSX as before and working well. The only thing is that if I close the system or reboot, it always go back to Shell and I have to go through the exiting procedure to go to OSX system.

I understand it is a noobie error but I need some help. Can somebody tell me how to solve this problem so system boot directly to OS as before

Thank in advance for any help you can provide.

 

P.S.: After thinking... could it be that Windows system was not installed originally in (U)EFI mode ?

 

My Windows system was build on a Z77X-UD5H Gigabyte motherboard so I thought my Z77MX Quo board would take easily accept my installation. Noobie, noobie !!!!

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

Hi Bernard,

 

   Once you are are back in OS X  with the Windows SSD connected , go in terminal and type 

diskutil list

 .. it will list your partition and the partitioning scheme  it should show GUID_partition_scheme for your Windows Drive .. if not then it is not a UEFI install.

Link to comment
Share on other sites
Bernard Leclerc
Bernard Leclerc
Posted
Posted

Once booted into OS X, go to Preferences/Starup Disk and select your OS X partition.

Thanks. It did solve my problem.

Hi Bernard,

 

   Once you are are back in OS X  with the Windows SSD connected , go in terminal and type 

diskutil list

 .. it will list your partition and the partitioning scheme  it should show GUID_partition_scheme for your Windows Drive .. if not then it is not a UEFI install.

Hi IronmanJFF,

I'll try that later on. I have an other question. I think I read earlier in the posts that you were using Parallells. I tried in the last days to install Parallels 11 trial version. Installation went right but when I tried to import my Windows 10 installation (Lan connection), when the installation was almost complete, I got an error message from Windows saying that installation could not be completed because my system was not a 64 bits system.  You can see by my signature that it is not the case. Any idea ? Should I try an earlier version of parallels ? 

Link to comment
Share on other sites
Bernard Leclerc
Bernard Leclerc
Posted
Posted (edited)

Migration of Win 10 installation is not yet supported in Parallels.

http://kb.parallels.com/en/119172

 

However if you have a dual-boot system you can tell Parallels to run it off the Win HD/SSD

Hi,

Thanks for answering my questions.

 

I tough the new  Parallels 11 could do it. It's what they say on their site. Anyway, I did the diskutil command and indeed my Windows 10 is not an UEFI installation: see

diskutil.png   - seems my picture does not show !

 

From where I stand, how do I create a dual-boot system. Do I need to start anew or can I go from here( OS X installation) and build the dual-boot ? If too complicated, I may just return to my two separate systems.

Edited by Bernard Leclerc
Link to comment
Share on other sites
dwdrummer0
dwdrummer0
Posted
Posted

getting kernal panics in El Capitan 10.11.2. This was after I reinstalled my Apogee Symphony drivers (audio device). Device connects through Thunderbolt. Suspecting something to do with thunderbolt? The log stops right at at.. Or maybe this Watchdog Timeout?

 

Here is the log.

 

Anonymous UUID:       

 

Mon Jan 11 11:52:15 2016

 

*** Panic Report ***

panic(cpu 2 caller 0xffffff7f81f2650b): "OSX Watchdog Timeout: "@/BuildRoot/Library/Caches/com.apple.xbs/Sources/OSXWatchdog/OSXWatchdog-22/Source/AppleOSXWatchdog/AppleOSXWatchdog.cpp:234

Backtrace (CPU 2), Frame : Return Address

0xffffff83acd13ec0 : 0xffffff80002de792 

0xffffff83acd13f40 : 0xffffff7f81f2650b 

0xffffff83acd13f80 : 0xffffff7f81f2662d 

0xffffff83acd13fb0 : 0xffffff80003cbf77 

      Kernel Extensions in backtrace:

         com.apple.driver.AppleOSXWatchdog(1.0)[b92C030B-3065-3493-B9FA-EB08EB973E04]@0xffffff7f81f25000->0xffffff7f81f28fff

            dependency: com.apple.iokit.IOPCIFamily(2.9)[6ADFE830-2986-35D2-8C2F-6ABEDBC94F6A]@0xffffff7f80a9c000

 

BSD process name corresponding to current thread: kernel_task

Boot args: slide=0

 

Mac OS version:

15C50

 

Kernel version:

Darwin Kernel Version 15.2.0: Fri Nov 13 19:56:56 PST 2015; root:xnu-3248.20.55~2/RELEASE_X86_64

Kernel UUID: 17EA3101-D2E4-31BF-BDA9-931F51049F93

__HIB  text base: 0xffffff8000100000

System model name: MacPro3,1 (Mac-F42C88C8)

 

System uptime in nanoseconds: 106539826742

last loaded kext at 39885727800: com.Cycling74.driver.Soundflower 1.6.6 (addr 0xffffff7f8100a000, size 40960)

last unloaded kext at 654629631: org.netkas.FakeSMC 1111 (addr 0xffffff7f81125000, size 53248)

loaded kexts:

com.Cycling74.driver.Soundflower 1.6.6

com.evosx86.driver.lspcidrv 1111

com.apogeedigital.driver.Symphony64ThunderBridge 1.4.24

com.digidesign.iokit.DigiDal 10.3.10d4

com.squirrels.airparrot.framebuffer 5

com.squirrels.driver.AirParrotSpeakers 1.8

com.intel.driver.EnergyDriver 2.0

at.obdev.nke.LittleSnitch 4352

org.hwsensors.driver.LPCSensors 1394

org.hwsensors.driver.CPUSensors 1394

org.netkas.driver.FakeSMC 1394

org.tgwbd.driver.NullCPUPowerManagement 1111

com.apple.driver.pmtelemetry 1

com.apple.iokit.IOUserEthernet 1.0.1

com.apple.iokit.IOBluetoothSerialManager 4.4.3f4

com.apple.driver.AudioAUUC 1.70

com.apple.driver.AppleTyMCEDriver 1.0.2d2

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.AppleOSXWatchdog 1

com.apple.driver.AppleUpstreamUserClient 3.6.1

com.apple.driver.AppleMCCSControl 1.2.13

com.apple.driver.AppleHV 1

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.4.3f4

com.apple.driver.AppleIntelHD4000Graphics 10.1.2

com.apple.driver.AppleLPC 3.1

com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0

com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0

com.apple.driver.AppleFIVRDriver 4.1.0

com.apple.driver.AppleIntelFramebufferCapri 10.1.2

com.apple.driver.AppleUSBODD 3.7.1

com.apple.driver.MaxTranserSizeOverrideDriver 3.7.1

com.apple.iokit.SCSITaskUserClient 3.7.7

com.apple.driver.AppleFileSystemDriver 3.0.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0

com.apple.BootCache 38

com.apple.iokit.IOAHCIBlockStorage 2.8.5

com.apple.driver.Intel82574L 2.7.0b1

com.apple.driver.AppleFWOHCI 5.5.2

com.apple.driver.AppleAHCIPort 3.1.8

com.apple.driver.usb.AppleUSBEHCIPCI 1.0.1

com.apple.driver.AppleACPIButtons 4.0

com.apple.driver.AppleRTC 1111

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleSMBIOS 2.1

com.apple.driver.AppleAPIC 1.7

com.apple.nke.applicationfirewall 163

com.apple.security.quarantine 3

com.apple.security.TMSafetyNet 8

com.apple.driver.AppleIntelCPUPowerManagement 218.0.0

com.apple.iokit.IOSerialFamily 11

com.apple.driver.AppleSMBusController 1.0.14d1

com.apple.iokit.IOSMBusFamily 1.1

com.apple.driver.CoreCaptureResponder 1

com.apple.driver.corecapture 1.0.4

com.apple.iokit.IOFireWireIP 2.2.6

com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.4.3f4

com.apple.iokit.IOBluetoothFamily 4.4.3f4

com.apple.iokit.IOSurface 108.0.1

com.apple.driver.AppleSMBusPCI 1.0.14d1

com.apple.driver.AppleSMC 3.1.9

com.apple.driver.IOPlatformPluginLegacy 1.0.0

com.apple.driver.IOPlatformPluginFamily 6.0.0d7

com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0

com.apple.iokit.IONDRVSupport 2.4.1

com.apple.iokit.IOAcceleratorFamily2 203.14

com.apple.AppleGraphicsDeviceControl 3.12.6

com.apple.iokit.IOGraphicsFamily 2.4.1

com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.7

com.apple.iokit.IOBDStorageFamily 1.8

com.apple.iokit.IODVDStorageFamily 1.8

com.apple.iokit.IOCDStorageFamily 1.8

com.apple.driver.AppleUSBHIDMouse 185.3

com.apple.iokit.IOUSBHIDDriver 900.4.1

com.apple.driver.AppleHIDMouse 185.3

com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.7

com.apple.driver.AppleHIDKeyboard 181

com.apple.driver.usb.IOUSBHostHIDDevice 1.0.1

com.apple.driver.AppleUSBAudio 302.15

com.apple.iokit.IOAudioFamily 204.3

com.apple.vecLib.kext 1.2.0

com.apple.iokit.IOUSBMassStorageDriver 1.0.0

com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.7

com.apple.driver.usb.AppleUSBHostCompositeDevice 1.0.1

com.apple.driver.usb.AppleUSBHub 1.0.1

com.apple.driver.AppleXsanScheme 3

com.apple.iokit.IONetworkingFamily 3.2

com.apple.iokit.IOFireWireFamily 4.5.8

com.apple.iokit.IOUSBFamily 900.4.1

com.apple.iokit.IOAHCIFamily 2.8.1

com.apple.driver.usb.AppleUSBEHCI 1.0.1

com.apple.driver.usb.AppleUSBXHCIPCI 1.0.1

com.apple.driver.usb.AppleUSBXHCI 1.0.1

com.apple.iokit.IOUSBHostFamily 1.0.1

com.apple.driver.AppleUSBHostMergeProperties 1.0.1

com.apple.driver.AppleEFINVRAM 2.0

com.apple.driver.AppleEFIRuntime 2.0

com.apple.iokit.IOHIDFamily 2.0.0

com.apple.security.sandbox 300.0

com.apple.kext.AppleMatch 1.0.0d1

com.apple.driver.AppleKeyStore 2

com.apple.driver.AppleMobileFileIntegrity 1.0.5

com.apple.driver.AppleCredentialManager 1.0

com.apple.driver.DiskImages 417.1

com.apple.iokit.IOStorageFamily 2.1

com.apple.iokit.IOReportFamily 31

com.apple.driver.AppleFDEKeyStore 28.30

com.apple.driver.AppleACPIPlatform 4.0

com.apple.iokit.IOPCIFamily 2.9

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.pthread 1

com.apple.kec.corecrypto 1.0

com.apple.kec.Libm 1

Model: MacPro3,1, BootROM MP31.006C.B05, 4 processors, Intel Core i7, 4.6 GHz, 32 GB, SMC 1.30f3

Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, Corsair, CMZ32GX3M4X1600C1

Memory Module: BANK 0/DIMM2, 8 GB, DDR3, 1600 MHz, Corsair, CMZ32GX3M4X1600C1

Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1600 MHz, Corsair, CMZ32GX3M4X1600C1

Memory Module: BANK 0/DIMM3, 8 GB, DDR3, 1600 MHz, Corsair, CMZ32GX3M4X1600C1

Bluetooth: Version 4.4.3f4 16616, 3 services, 27 devices, 1 incoming serial ports

Network Service: Ethernet, Ethernet, en0

PCI Card: Symphony 64 | ThunderBridge, Audio, Thunderbolt@220,0,0

Serial ATA Device: Samsung SSD 840 EVO 1TB, 1 TB

Serial ATA Device: ST1000DM003-1CH162, 1 TB

Serial ATA Device: ST1000DM003-1CH162, 1 TB

USB Device: USB 2.0 Bus

USB Device: Hub

USB Device: Integrated USB Bridge

USB Device: USB 2.0 Bus

USB Device: Hub

USB Device: Hub

USB Device: BCM20702A0

USB Device: MT1887

USB Device: Symphony I/O : Symphony

USB Device: USB Axiom 25

USB Device: USB 3.0 Bus

USB Device: USB3.0 Hub

USB Device: USB3.0 Hub

USB Device: Backup+  Desk

USB Device: USB2.0 Hub

USB Device: USB2.0 Hub

USB Device: FreeAgent GoFlex

USB Device: Keyboard Hub

USB Device: Apple Optical USB Mouse

USB Device: Apple Keyboard

USB Device: USB Storage

FireWire Device: unknown_device, Unknown

Thunderbolt Bus: 

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

Hi,

Thanks for answering my questions.

 

I tough the new  Parallels 11 could do it. It's what they say on their site. Anyway, I did the diskutil command and indeed my Windows 10 is not an UEFI installation: see

diskutil.png   - seems my picture does not show !

 

From where I stand, how do I create a dual-boot system. Do I need to start anew or can I go from here( OS X installation) and build the dual-boot ? If too complicated, I may just return to my two separate systems.

 

Parallels 10 & 11 support Win 10 VM or thru the Bootcamp partition, it just does not support importing it yet.

 

To create a dual-boot system, you could 

1) Plug the Windows drive int your QUO

2) in BIOS enable UEFI & Legacy boot

3) at Boot press F12 and choose the Windows Boot Manager to boot into Windows

Now this may or may not work depending on what hardware was present in your Windows system

getting kernal panics in El Capitan 10.11.2. This was after I reinstalled my Apogee Symphony drivers (audio device). Device connects through Thunderbolt. Suspecting something to do with thunderbolt? The log stops right at at.. Or maybe this Watchdog Timeout?

 

Here is the log.

 

Anonymous UUID:       

 

Mon Jan 11 11:52:15 2016

 

*** Panic Report ***

panic(cpu 2 caller 0xffffff7f81f2650b): "OSX Watchdog Timeout: "@/BuildRoot/Library/Caches/com.apple.xbs/Sources/OSXWatchdog/OSXWatchdog-22/Source/AppleOSXWatchdog/AppleOSXWatchdog.cpp:234

Backtrace (CPU 2), Frame : Return Address

0xffffff83acd13ec0 : 0xffffff80002de792 

0xffffff83acd13f40 : 0xffffff7f81f2650b 

0xffffff83acd13f80 : 0xffffff7f81f2662d 

0xffffff83acd13fb0 : 0xffffff80003cbf77 

      Kernel Extensions in backtrace:

         com.apple.driver.AppleOSXWatchdog(1.0)[b92C030B-3065-3493-B9FA-EB08EB973E04]@0xffffff7f81f25000->0xffffff7f81f28fff

            dependency: com.apple.iokit.IOPCIFamily(2.9)[6ADFE830-2986-35D2-8C2F-6ABEDBC94F6A]@0xffffff7f80a9c000

 

Are all your audio drivers El Cap certified ?

 

Mac OS version:

15C50

 

loaded kexts:

....

com.evosx86.driver.lspcidrv 1111

...

com.intel.driver.EnergyDriver 2.0

...

org.tgwbd.driver.NullCPUPowerManagement 1111

 

Why are you having these kexts ? 

Link to comment
Share on other sites
dwdrummer0
dwdrummer0
Posted
Posted

Parallels 10 & 11 support Win 10 VM or thru the Bootcamp partition, it just does not support importing it yet.

 

To create a dual-boot system, you could 

1) Plug the Windows drive int your QUO

2) in BIOS enable UEFI & Legacy boot

3) at Boot press F12 and choose the Windows Boot Manager to boot into Windows

Now this may or may not work depending on what hardware was present in your Windows system

Are all your audio drivers El Cap certified ?

Why are you having these kexts ? 

 

Hey Jeff,

 

Drivers are certified. My other partition (mavericks) everything works great. But the issue comes with El Capitan.

 

As far as the Kext's, I haven't installed any extra so i'm not sure if those are needed or not. 

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

Hey Jeff,

 

Drivers are certified. My other partition (mavericks) everything works great. But the issue comes with El Capitan.

 

As far as the Kext's, I haven't installed any extra so i'm not sure if those are needed or not. 

You ever did a Clover/[url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url]/[url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] install  on this machine ? because it looks like stuff that would be install by those other tools that are not needed with Ozmosis.

 

 

Now your kernel panics are probably cause by Soundflower and it looks like you don't have the latest version. You can get the latest version here

If you don't have a use for it .. simply un-install it. But I suspect you do have a use just by looking at the audio equipment you got there....

Link to comment
Share on other sites
dwdrummer0
dwdrummer0
Posted
Posted

You ever did a Clover/#####/##### install  on this machine ? because it looks like stuff that would be install by those other tools that are not needed with Ozmosis.

 

 

Now your kernel panics are probably cause by Soundflower and it looks like you don't have the latest version. You can get the latest version here

If you don't have a use for it .. simply un-install it. But I suspect you do have a use just by looking at the audio equipment you got there....

 

Thanks brotha! I did a migration from Mavericks so thats prob where those kexts are coming from. Im doing a clean install now of El Capitan. 

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

That is default behaviour for the board/CPU combo as it was designed.

To enable Ivy Bridge Power Management you need to put in custom SSDT.

Lucky you, I already did it....just need find a way to send to you...

PM valid email address


Thanks brotha! I did a migration from Mavericks so thats prob where those kexts are coming from. Im doing a clean install now of El Capitan. 

They are not Apple kext and OZ only needs vanilla install so they were installed by some tool ..i suspect M___Beast

  • Like 1
Link to comment
Share on other sites
dwdrummer0
dwdrummer0
Posted
Posted

That is default behaviour for the board/CPU combo as it was designed.

To enable Ivy Bridge Power Management you need to put in custom SSDT.

Lucky you, I already did it....just need find a way to send to you...

PM valid email address

They are not Apple kext and OZ only needs vanilla install so they were installed by some tool ..i suspect M___Beast

Yep, your probably right about M___Beast

Link to comment
Share on other sites
ledude
ledude
Posted
Posted

Hi all, hi team,

 

this is my first post here I'm David I'm from Paris (France).

 

First of all thank you for that nice ChristmasBios ^^ the H3C.1669M

It work great for El Capitan & windows 8.1 in uefi mode for me.

The only thing i can't do is the ability to boot with a bootable USB in legacy mode.

I've lost it since H3B.894M.

 

Another thing that I would like to know,

Is it important to change my system spec ? the macpro3,1 work great

 

thanks

 

 

 

my spec

windows 8.1

Yosemite 10.10.5

ElCapitan 10.11.2

Quo Z77MXQUOAOS with H3C.1669M

i7 3770T

PNY GTX660

16GB of Corsair Vengence @1600Mhz

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

 

The only thing i can't do is the ability to boot with a bootable USB in legacy mode.

 

Another thing that I would like to know,

Is it important to change my system spec ? the macpro3,1 work great

 

thanks

 

BIOS -> Boot Option -> UEFI and Legacy if you want to be able to boot Legacy (or you could create a UEFI stick)

 

You don,t have to change the System Definition, if it works great for you, leave it as it is

Link to comment
Share on other sites
ledude
ledude
Posted
Posted

Hi,

 

I know how to change my bios boot option

 

I've got an USB key who work great in legacy mode with the H3B.894M bios version.

With the H3C.1669M bios version even if I choose "lecacy" or "UEFI & legacy" only UEFI device are seen.

Link to comment
Share on other sites
Bernard Leclerc
Bernard Leclerc
Posted
Posted

Hi @all

Need Help !

 

Trying to install Parallels Desktop software to my OS X Yosemite, I had that error message saying that Virtualization technology was not enabled on my computer. So I went to Bios and changed the setting to "enabled". Saved changes and system rebooted. To Black screen !!! I can't even go back to bios. Forced closing of computer, tried to boot to bios, nothing, black screen...Did something wrong ?  A bit desperate there ! Solution, some one ? Resetting bios ? Will I need to reinstall bios version ?  :help:

Link to comment
Share on other sites
Bernard Leclerc
Bernard Leclerc
Posted
Posted

See if you can get into the Firmware Setup by holding ESC till the screen turns red and after holding the key to enter fw.

If that doesn't work, reset from the 2nd firmware chip.

Holding ESC when computer start does nothing. After some time computer closes.

Thanks for answer

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...