- Joined
- Jun 14, 2012
- Messages
- 15
- Motherboard
- Computer
- CPU
- i7-3770K
- Graphics
- MSI GTX 660 Ti 2GB
- Mac
- Classic Mac
- Mobile Phone
[SOLVED] Mixed Success/Login Issues - GA-Z77N-WIFI - 3770K - GTX 660 Ti
Hello everyone
I've been having having some success with Mountain Lion, but also some unexplainable issues.
Components:
1. GA-Z77N-WIFI Motherboard
2. Intel i7 3770K
3. MSI GTX 660 Ti
4. Corsair Vengeance DDR3 16GB (2 x 8GB) 1600MHz
5. Intel 330 Series 180GB SSD for boot
6. Seagate Barracuda 1TB 7200RPM Hard Drive for storage
7. OCZ ZT Series 550W Modular PSU
8. Corsair H60 Cooler
9. Cooler Master Elite 120 Advanced case
Method of Install:
1. Install Mountain Lion
Boot from Unibeast USB with no arguments
Format Drive with GUID Partition Table
Install Mountain Lion
2. 10.8.2 Update
Boot into Mountain Lion (I had to use the Unibeast USB bootloader because of Boot0 error)
Install the 10.8.2 Combo Update
Reboot
3. Configuring the Install
Open up Multibeast (5.2.3) and check the following-
I could not use the UserDSDT Installation option as it results in a kernal panic at login (see below)
Drivers -> Audio -> Without DSDT -> ALC892
Drivers -> Disk -> TRIM Enabler -> 10.8.1+ TRIM Patch (Or use Trim Enabler (http://goo.gl/eGJ8W))
Drivers ->Network -> Lnx2Mac RealtekRTL81xx
Drivers -> Miscellaneous -> FakeSMC
Drivers -> Miscellaneous -> FakeSMC Plugins
Bootloaders -> Chimera v1.11.1 r1394 (Only because of the Boot0 error I get when booting of the SSD)
Reboot
Current Standstill & problem(s):
The machine is able to boot into Mountain Lion to the login screen. Logging in either results in a Kernel Panic (no output, just frozen display) or once in a while, a successful desktop displayed. I have tried booting with "-x" which yields the same chance of displaying a desktop or Kernel Panic.
Just when I tried to login in this time, I finally got a Kernel Panic with an output over the desktop! The error makes mention to FakeSMC, hwsensors, and GPUSensors. Looks like I will be uninstalling FakeSMC and HWMonitor and see where it goes from here.
Not sure wether a DSDT is needed or not. When I tried running Multibeast and just using the "UserDSD or DSDT-Free Installation" option with or without a the DSDT on the Desktop, it results in a frozen screen seconds after logging in. From my experience so far with it, I have just avoided touching that setting. I am not using HD4000 HDMI anyway so it is no big deal for now. Hopefully this does not effect the DVI port on the motherboard which I want to use in the future.
By default Mountain Lion has the system definitions as a Mac Pro 2,2 (I think). Is there any benefit of changing it to iMac 12,2? Does it really matter what it is?
Sleep! Somehow when I was able to login, I tried Sleep. I was surprised to see that it actually worked! Before I was only left with the screen turning off and the hard disks turning off. Upon wakening it by hitting the keyboard, I was faced with the dreaded login screen. I attempted to login and had the usual Kernel Panic. Some success at least.
Last but not least, how can I backup a basic 10.8.2 install on my SSD to an external hard drive for when I need to jump back to a working setup.
Hello everyone
I've been having having some success with Mountain Lion, but also some unexplainable issues.
Components:
1. GA-Z77N-WIFI Motherboard
2. Intel i7 3770K
3. MSI GTX 660 Ti
4. Corsair Vengeance DDR3 16GB (2 x 8GB) 1600MHz
5. Intel 330 Series 180GB SSD for boot
6. Seagate Barracuda 1TB 7200RPM Hard Drive for storage
7. OCZ ZT Series 550W Modular PSU
8. Corsair H60 Cooler
9. Cooler Master Elite 120 Advanced case
Method of Install:
1. Install Mountain Lion
Boot from Unibeast USB with no arguments
Format Drive with GUID Partition Table
Install Mountain Lion
2. 10.8.2 Update
Boot into Mountain Lion (I had to use the Unibeast USB bootloader because of Boot0 error)
Install the 10.8.2 Combo Update
Reboot
3. Configuring the Install
Open up Multibeast (5.2.3) and check the following-
I could not use the UserDSDT Installation option as it results in a kernal panic at login (see below)
Drivers -> Audio -> Without DSDT -> ALC892
Drivers -> Disk -> TRIM Enabler -> 10.8.1+ TRIM Patch (Or use Trim Enabler (http://goo.gl/eGJ8W))
Drivers ->Network -> Lnx2Mac RealtekRTL81xx
Drivers -> Miscellaneous -> FakeSMC
Drivers -> Miscellaneous -> FakeSMC Plugins
Bootloaders -> Chimera v1.11.1 r1394 (Only because of the Boot0 error I get when booting of the SSD)
Current Standstill & problem(s):
The machine is able to boot into Mountain Lion to the login screen. Logging in either results in a Kernel Panic (no output, just frozen display) or once in a while, a successful desktop displayed. I have tried booting with "-x" which yields the same chance of displaying a desktop or Kernel Panic.
Just when I tried to login in this time, I finally got a Kernel Panic with an output over the desktop! The error makes mention to FakeSMC, hwsensors, and GPUSensors. Looks like I will be uninstalling FakeSMC and HWMonitor and see where it goes from here.
Not sure wether a DSDT is needed or not. When I tried running Multibeast and just using the "UserDSD or DSDT-Free Installation" option with or without a the DSDT on the Desktop, it results in a frozen screen seconds after logging in. From my experience so far with it, I have just avoided touching that setting. I am not using HD4000 HDMI anyway so it is no big deal for now. Hopefully this does not effect the DVI port on the motherboard which I want to use in the future.
By default Mountain Lion has the system definitions as a Mac Pro 2,2 (I think). Is there any benefit of changing it to iMac 12,2? Does it really matter what it is?
Sleep! Somehow when I was able to login, I tried Sleep. I was surprised to see that it actually worked! Before I was only left with the screen turning off and the hard disks turning off. Upon wakening it by hitting the keyboard, I was faced with the dreaded login screen. I attempted to login and had the usual Kernel Panic. Some success at least.
Last but not least, how can I backup a basic 10.8.2 install on my SSD to an external hard drive for when I need to jump back to a working setup.