Jump to content

[Guide] Installing Mountain Lion.


  • Please log in to reply
116 replies to this topic

#41
BisDak

BisDak

    InsanelyMac Protégé

  • Members
  • Pip
  • 6 posts
DIdn't work in my case. After typing -v (for verbose) in the initial part of the install, of course lots of cryptic text whizzes by. But before I could see what's wrong, it reboots. Tried doing it from scratch the 2nd time, same result. Using the GM, by the way, on an Asrock G41M-VS3 + Q9550 + 4gbx2 ram + 9500GT.

The process is very similar the way I did it in Lion, using MaLd0n's guide. I din't have a problem on that one.

Oh well ... back to work in the meantime ... and will wait for someone who could install this on the same hardware as mine.

#42
yonyz

yonyz

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 244 posts
I tried The Tech Erra's guide and it only boots once. After the first boot, it stops booting because it fails to find an SMC driver.
So I can re-copy-paste the FakeSMC and NullCPU... kexts, which will only give me another single boot.
Dunno why it doesn't work for more then one.

It was the same with DP4...

--- EDIT ---
Fixed by installing the FakeSMC kext with Kext Wizard. Apparently copy-paste and fixing permissions doesn't cut it.

#43
Hackintosh2000

Hackintosh2000

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 171 posts
  • Gender:Male
  • Location:Unites States of America

I faced this error and solved after restoring back the original OSInstall file from the original DP dmg.


I have the same problem here. I looked in the packages folder and there is a file called essentials.pkg wich is 2,54 Go



And when I start the installation of Mountain Lion, the installer says this:
Posted Image


Hardware:
Asus P6T Deluxe v2
Intel Core i7 920 2,67Ghz
Nvidia GTX 260
8Gb RAM DDR3 1069Mhz


Guys are you installing OS X Mountain Lion on a MBR disk or a GPT disk? The problem with a lot of these guides is they miss steps and they leave out critical information. The so called "fixed" files (OSInstall) are only necessary if you are installing on a MBR disk. Mountain Lion is designed to be installed on a GPT disk but in certain setups it must be "tricked" into installing on a MBR disk. My understanding is only EFI motherboards can boot directly off of GPT disks. So perhaps the new Gigabyte boards can boot a GPT OS X install directly. Anyway I don't have much experience with GPT, but if you are installing to a GPT drive you do NOT need to mess with the two OSInstall files. Leave them as is.

I appreciate people posting guides but they really need to be better researched and explained.

When I start the installation partition Mountain Lion, Chameleon returns this:
Posted Image


Chameleon no longer uses com.apple.Boot.plist file in the Extra folder. It now uses org.chameleon.Boot.plist instead. Actually it hasn't used the com.apple.Boot.plist file for quite some time... in hackintosh years. There was a time you could still use the com.apple.Boot.plist file. Chameleon would just complain. I don't know if that is still the case. Anyway let us know if you found this advice useful and if it solved your problems.

#44
yonyz

yonyz

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 244 posts
Good information, Hackintosh2000. I myself had to restore the original OSInstall file. However, on the GM ML guide, I did replace the original and it worked perfectly. My SSD only has ML installed, it's partitioned as GUID.

#45
jrdnlc

jrdnlc

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts
  • Gender:Male
  • Location:Burbank,CA
I installed it Sucessfully on my GA-EP45-UD3R motherboard but after running ##### and installing my DSDT it wont boot without the usb stick.

It just stuck in the grey apple loading screen any idea why? Thanks

#46
phsilver

phsilver

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts

Thanks EvgeniX. Just managed to boot without the usb, fixed through terminal. I would like to have a wireless connection. Any advise would be helpful. Internet is the only problem for me now.

Thanks EvgeniX. Just managed to boot without the usb, fixed through terminal. I would like to have a wireless connection. Any advise would be helpful. Internet is the only problem for me now.


Hi there...
Can you explain how to solve the fact booting without USB?
Thanxs!

#47
yonyz

yonyz

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 244 posts

I installed it Sucessfully on my GA-EP45-UD3R motherboard but after running ##### and installing my DSDT it wont boot without the usb stick.

It just stuck in the grey apple loading screen any idea why? Thanks


Boot with '-v' so we will know where it's stuck.

#48
Hackintosh2000

Hackintosh2000

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 171 posts
  • Gender:Male
  • Location:Unites States of America

DIdn't work in my case. After typing -v (for verbose) in the initial part of the install, of course lots of cryptic text whizzes by. But before I could see what's wrong, it reboots. Tried doing it from scratch the 2nd time, same result. Using the GM, by the way, on an Asrock G41M-VS3 + Q9550 + 4gbx2 ram + 9500GT.

The process is very similar the way I did it in Lion, using MaLd0n's guide. I din't have a problem on that one.

Oh well ... back to work in the meantime ... and will wait for someone who could install this on the same hardware as mine.


Start over and follow THIS guide carefully. If you are installing Mountain Lion to a GPT hard drives (as opposed to MBR) then do NOT mess with the OSinstall files. Skip that step.

I found that only using the two kexts that they recommend (FakeSMC.kext and NullCPUPowerManagement.kext) was enough to get me installed. You can go back and add kexts later. I used their Chameleon installer and a very basic org.chameleon.Boot.plist. I did not use Generat P states or Generate C states. I did use GraphicsEnabler=Yes. I chose a more up to date Mac for my SMBIOS. I didn't go crazy though. I chose an iMac with a processor that was close to what i have. I did use my dsdt though. To be honest with you I changed all these settings at once and my restart loop problems were solved. What individual thing solved it is anyone's guess. Frankly I may have actually left out some other change I made.

My advice is to start very basic and follow the guide. I initially dove in and used a more up to date Chameleon, a number of kexts, and my org.chameleon.Boot from my lion setup and I got endless booting. I decided to back off a bit and use something simpler. I don't like the NullCPUPowerManagement.kext but I figured I could try it for the install phase and remove it later.

#49
yonyz

yonyz

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 244 posts

Start over and follow THIS guide carefully. If you are installing Mountain Lion to a GPT hard drives (as opposed to MBR) then do NOT mess with the OSinstall files. Skip that step.

I found that only using the two kexts that they recommend (FakeSMC.kext and NullCPUPowerManagement.kext) was enough to get me installed. You can go back and add kexts later. I used their Chameleon installer and a very basic org.chameleon.Boot.plist. I did not use Generat P states or Generate C states. I did use GraphicsEnabler=Yes. I chose a more up to date Mac for my SMBIOS. I didn't go crazy though. I chose an iMac with a processor that was close to what i have. I did use my dsdt though. To be honest with you I changed all these settings at once and my restart loop problems were solved. What individual thing solved it is anyone's guess. Frankly I may have actually left out some other change I made.

My advice is to start very basic and follow the guide. I initially dove in and used a more up to date Chameleon, a number of kexts, and my org.chameleon.Boot from my lion setup and I got endless booting. I decided to back off a bit and use something simpler. I don't like the NullCPUPowerManagement.kext but I figured I could try it for the install phase and remove it later.


I use a DSDT that I found on OSX86.net. It's meant for a mobo that's similar to mine. Can I create one that fits my board perfectly? And what's a patched DSDT?

#50
Stathman

Stathman

    InsanelyMac Protégé

  • Members
  • Pip
  • 20 posts
  • Gender:Male

Hi there...
Can you explain how to solve the fact booting without USB?
Thanxs!


Hi,
I followed this guide

#51
jrdnlc

jrdnlc

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts
  • Gender:Male
  • Location:Burbank,CA

Boot with '-v' so we will know where it's stuck.



How do i boot with '-v' ?

#52
yonyz

yonyz

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 244 posts

How do i boot with '-v' ?

Before you press Enter to boot the selected partition, type "-v" and then press Enter.

#53
monto

monto

    InsanelyMac Protégé

  • Members
  • Pip
  • 20 posts
  • Gender:Male
I've tried 3 different methods (John Cash, MyHack & Tech Erra Brian) to build ML 10.8 GM, and they all got stuck at around the same place during booting. If I put the Atheros network kext in /E/E, the last line I see at booting (from -v) is related to it being loaded successfully. If I put NVEnabler in /S/L/E via kext wizard, the last thing I would see is about 20 lines of NVEnabler probing. Prior to the logs from these two kexts (or if I removed these two kexts), I was getting the followings:

DSMOS has arrived
[IOBluetoothHCIController]....
[IOBluetoothHCIController][start] -- completed
[IOBluetoothHCIController].... calling registerService

It seemed the booting got stuck here and the hard disk LED light would stop flashing at this point. My same hardware is currently running 10.7.4 fine with vanilla build (ML staging was built on a separate HDD.)

Does anyone know after IOBluetooth and kexts mentioned above, what's the booting doing at this stage? It was failing without giving any further useful logging. The main suspect was probably NVidia 8400GS 256MB card but 1. it has been working fine on 10.7 fully (2 monitors at full res) and 2. someone at OSX86 compatibility list suggested this card should work OOTB. I have tried graphicsenabler=yes and npci=0x2000 & 0x3000 with no avail.

Any suggestion of where to go next to boot to ML? I don't mind buying a new video card if this card is not supported, but I'd hate to spend the money and find out the culprit is something else.


(Tried uploading the system.log but the forum wouldn't let me... I've pasted the last 100 lines or so)


Jul 14 01:36:51 localhost kernel[0]: Pin sense: cad 2 nid=28 res=1
Jul 14 01:36:51 localhost kernel[0]: setDesc change description Line-out (Green Rear) channel 0 assoc 0
Jul 14 01:36:51 localhost kernel[0]: Pin sense: cad 2 nid=29 res=0
Jul 14 01:36:51 localhost kernel[0]: Pin sense: cad 2 nid=30 res=0
Jul 14 01:36:51 localhost kernel[0]: switch nid 23 conn 0 on
Jul 14 01:36:51 localhost kernel[0]: switch nid 23 conn 1 on
Jul 14 01:36:51 localhost kernel[0]: switch nid 23 conn 2 on
Jul 14 01:36:51 localhost kernel[0]: switch nid 23 conn 3 off
Jul 14 01:36:51 localhost kernel[0]: setDesc change description CD (Analog) channel 1 assoc 1
Jul 14 01:36:51 localhost kernel[0]: [BroadcomBluetoothHCIControllerUSBTransport][start] -- completed
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: init : begin
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : probe
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : ROM shadow enable
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : patch PRAMIN
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: False ROM signature: 0x0100
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : patch PROM
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: dcb table at offset 0xbb70
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: dcb numentries 16
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Raw DCB entry 0: 02000300
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Raw DCB entry 1: 01000302
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Raw DCB entry 2: 04011310
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Raw DCB entry 3: 010223f1
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: numentries = 16 num_outputs = 4
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: 2 not grouped
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: 3 not grouped
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Channel 1: 03
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: Channel 2: 0c
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Model found: GeForce 8400 GS
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG VRAM: 256
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,name
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,display-cfg
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,name
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property hda-gfx
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property device_type
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: DEBUG Setting property vbios
Jul 14 01:36:52 localhost kernel[0]: NVEnabler::probe fails
Jul 14 01:36:52 localhost loginwindow[64]: Login Window Application Started
Jul 14 01:36:52 localhost kernel[0]: DSMOS has arrived
Jul 14 01:36:52 localhost kernel[0]: [IOBluetoothHCIController][staticBluetoothHCIControllerTransportShowsUp] -- Received Bluetooth Controller register service notification
Jul 14 01:36:52 localhost kernel[0]: [IOBluetoothHCIController][start] -- completed
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: init : begin
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : probe
Jul 14 01:36:52 localhost kernel[0]: NVEnabler: probe : ROM shadow enable
Jul 14 01:36:52 localhost com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
Jul 14 01:36:52 localhost mds[60]: (Normal) FMW: FMW 0 0
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: probe : patch PRAMIN
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: False ROM signature: 0x0100
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: probe : patch PROM
Jul 14 01:36:53 localhost kernel[0]: [IOBluetoothHCIController::setConfigState] calling registerService
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: dcb table at offset 0xbb70
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: dcb numentries 16
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Raw DCB entry 0: 02000300
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Raw DCB entry 1: 01000302
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Raw DCB entry 2: 04011310
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Raw DCB entry 3: 010223f1
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: numentries = 16 num_outputs = 4
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: 2 not grouped
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: 3 not grouped
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Channel 1: 03
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: Channel 2: 0c
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Model found: GeForce 8400 GS
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG VRAM: 256
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,compatible
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,device_type
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,compatible
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,name
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,device_type
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,display-cfg
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @1,display-cfg
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property @0,name
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property hda-gfx
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property device_type
Jul 14 01:36:53 localhost kernel[0]: NVEnabler: DEBUG Setting property vbios
Jul 14 01:36:53 localhost kernel[0]: NVEnabler::probe fails
Jul 14 01:36:53 localhost configd[18]: New network configuration saved
Jul 14 01:36:53 localhost configd[18]: network changed: v4(en0!:192.168.1.142) DNS! Proxy- SMB
Jul 14 01:36:53 localhost configd[18]: network changed: v4(en0-:192.168.1.142) DNS- Proxy SMB
Jul 14 01:36:57 localhost apsd[80]: CGSLookupServerRootPort: Failed to look up the port for "com.apple.windowserver.active" (1102)
Jul 14 01:36:57 localhost configd[18]: network changed: v4(en0+:192.168.1.142) DNS+ Proxy+ SMB
Jul 14 01:36:57 localhost mDNSResponder[61]: mDNS_RegisterInterface: Frequent transitions for interface en0 (192.168.1.142)

#54
macq

macq

    InsanelyMac Geek

  • Members
  • PipPipPip
  • 119 posts

I've tried 3 different methods (John Cash, MyHack & Tech Erra Brian) to build ML 10.8 GM, and they all got stuck at around the same place during booting. If I put the Atheros network kext in /E/E, the last line I see at booting (from -v) is related to it being loaded successfully. If I put NVEnabler in /S/L/E via kext wizard, the last thing I would see is about 20 lines of NVEnabler probing. Prior to the logs from these two kexts (or if I removed these two kexts), I was getting the followings:

DSMOS has arrived
[IOBluetoothHCIController]....
[IOBluetoothHCIController][start] -- completed


mine is a laptop but my install also stalls with the follwing lines at boot,

DSMOS has arrived
[IOBluetoothHCIController]....
[IOBluetoothHCIController][start] -- completed

Dont know why but 10.7.4 works fine .
This started from dp2 before that everything worked fine till dp1.
my build is in my signature

#55
jrdnlc

jrdnlc

    InsanelyMac Protégé

  • Members
  • Pip
  • 19 posts
  • Gender:Male
  • Location:Burbank,CA
I reinstalled 10.8 GM and aftee running ####### with the options below it boots up without usb stick but then i get this error message. Anyone know what it means? I have a GA-EP45-UD3R and using a DSDT for thos especific motherboard.



Posted Image

Before you press Enter to boot the selected partition, type "-v" and then press Enter.


I dont press enter or anything it just boots up. I used ##### to create my usb install flash drive.

#56
Stathman

Stathman

    InsanelyMac Protégé

  • Members
  • Pip
  • 20 posts
  • Gender:Male
I would like to thank the community for helping me compile my 1st hackintosh.

Everything works just fine and i couldn't be more happy than i am.

I don't have much knowledge about all this stuff but it would be my pleasure to help someone.

Thanks.
(sorry for the off topic)

#57
yonyz

yonyz

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 244 posts

I dont press enter or anything it just boots up. I used ##### to create my usb install flash drive.


But there's a point where you select the partition you wanna boot, and there's a blue bar that gives you a few seconds to make a selection (or maybe there's no timer). Before the selected partition loads automatically or before you press Enter to boot it, you need to type '-v'.
If this doesn't make it any clearer, read about boot options for Chameleon.

#58
monto

monto

    InsanelyMac Protégé

  • Members
  • Pip
  • 20 posts
  • Gender:Male
Tried to boot up in safe mode with -x for the first time, and to my surprise it actually boot up successfully but with low res video. It seemed one of the kexts was causing the problem as safe mode doesn't load all the kexts. I'm not sure how to isolate which of the kext was the culprit. Any suggestions?

#59
yonyz

yonyz

    InsanelyMac Geek

  • Members
  • PipPipPipPip
  • 244 posts

Tried to boot up in safe mode with -x for the first time, and to my surprise it actually boot up successfully but with low res video. It seemed one of the kexts was causing the problem as safe mode doesn't load all the kexts. I'm not sure how to isolate which of the kext was the culprit. Any suggestions?


How many have you installed?
Move one by one to the desktop and restart, see which one solves the problem when moved out of the Extensions folder.

Also, what tool did you use to install the kexts?

#60
The Real Deal

The Real Deal

    InsanelyMac Legend

  • Donators
  • 886 posts
  • Gender:Male
  • Location:France
Installation quite tricky on my Rampage III Formula.
I have never struggled so mush to install and run SL and Lion on Rampage III Extreme and Formula :/


Installation done, but after the restart a lot of trial and errors during the verbose boot. It gives me headaches :wallbash:

Plus problems, with C2RC5 rev 2013, rollback to rev 2005 to recognize my HDD/SSD. Some kexts switched with SL ones, etc,.

ouch :moil:



EDIT : almost done to reach the desktop... stuck at "IOBluetoothHCI controller ..... start completed"

No KP, no error, just stucked :/





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

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