Jump to content

Stuck after multiple trys and a lost week


5 posts in this topic

Recommended Posts

Hey guys so this is my first post, I apologize if I leave something out or this has been answered, but I cant seem to find it.

So I have been trying to get os x 10.9.4 or later installed on my PC. Specs

 

Windows 7 SP1 X64

AMD Phenom II X6 1055T 2.8 GHz

Gigabyte GA-880GMA-UD2H

DDR3 4GB Ram

ATI Radeon HD 4250

AMD High Definition Audio Device

 

I installed VMware Workstation 10 and used the Unlocker 1.3. Added the VM for OS X 10.9, Removed the "firmware = efi" when I attempt to boot using the .vmx IDE torrent "os x mavericks 10 9 retail vmware image" I get to Loading Darwin/X86 screen and it just keeps spooling. I don't know how to get past that screen and get to the installation.

 

I installed Virtualbox 4.3.12 and used the Niresh ISO. I finally got OS X installed using the amd64 flag and added the graphics for 1080p. It runs pretty slow in Virtualbox but at least it boots. When I try to upgrade to 10.9.5 uding the app store, the purpose of having OS X is to use Xcode which needs 10.9.4+, it boots to the Guru Meditation error. I am really lost here and have been reading forums and install guides for the past week. Any help would be greatly appreciated! Thanks for everything so far guys.

 

P.S what is the fasting more stable software to use VMware or Virtualbox? Can I install OS X 10.9.5 on either one using AMD?


 

 

Link to comment
Share on other sites

I was able to combo upgrade to 10.9.4 with this kernel:

http://www.insanelymac.com/forum/files/file/299-mach-kernel-10-9-4-rc3-for-amd/

 

I'm using workstation 10, but i think it would work with virtualbox as well.

I did not need to change any kext, just the mach_kernel, but if you do you can try first the System.kext included in the download or

the kexts in this link:

http://www.insanelymac.com/forum/files/file/304-replace-mav-kext-for-amd/

 

use Kext Wizard to repair permissions.

 

By the way:

 

AMD Athlon II X2 240e Processor × 2

4 gb ram

using 2 for the vm.

 

Best of luck.

Link to comment
Share on other sites

I suggest that until there's a reason, leave the system at 10.9.4 since that's compliant for XCode, and use snapshots and/or clones to test an upgrade to 10.9.5. Get it working first, then consider the 10.9.5. All indications I'm reading to this point state that while 10.9.4. kernels are available, 10.9.5. may still be a "RC" level - that changes by the day at this point.

 

From my own experience VMWare is a superior product. There's a lot of enthusiastic support for Virtual Box, and I'm not knocking it. For OS X virtual machines there's not much difference, except in configuration details. For other VM's (non-OSX) I find VMWare has better performance and better stability.

 

I'm on an AMD Phenom II 955 at 3.7 GHz, Windows 7 host, VMWare Workstation 10, with VM's of OS X going back to 10.4.8, though lately I'm only using 10.8.4 and 10.9.4, where 10.8.4 (limited to XCode 5.1.1) has been rock stable for over a year, and I'm still setting up 10.9.4. to my liking.

 

Have you yet run into the XCode segmentation fault when compiling under XCode 5.1.1 and/or 6.0.1? I would be interested in comparing notes. I have a solution, considering a thread on the subject.

 

So far my 10.8.4. runs XCode 5.0.2 and 5.1.1 well, including the simulator and USB debugging. My 10.9.4 is still under the tweaking stage, but so far XCode 5.1.1 and 6.0.1 are running fine now, while the Simulator exhibits a display problem. It works, but it appears I have the VMSvga2 driver installed, and that's not the same version that's on my working 10.8.4. I've noticed that the screen saver shows the same display issue, so I'm considering driver fixes at the moment. Once I have that I think my 10.9.4 will be ready for work.

Link to comment
Share on other sites

Yesterday when I wrote the post, I just managed to upgrade to 10.9.4 and I was so exited about it, because I was going to be able to test Xcode 6.0.1 and tinker with Swift playgrounds, then YES, I had the segmentation fault. I tried to search about it and then read your post at:

http://www.insanelymac.com/forum/topic/291140-application-support-amd/?p=2064373

where you say that part of your solution was to use LLVM 3.5 (Xcode 6) from LLVM.org.

I downloaded the pre-built binaries for darwin of course and tried to symlinking the new clang into /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin but as you say there are lots of missing libraries and headers errors; I've tried to change paths and compiler arguments from within Xcode and changed the .profile file updating the PATH variable to include some binaries that reside into Xcode.app.

No luck. This is all over my head, so yes, I think it would be great if you open a thread on the subject and let us know how you managed to make it work please.

About the VMSvga2 driver, I tried to install the Mavericks version that you can get from sourceforge, but the vm could not reboot, so I've done nothing further about it, yet.

Thanks.

Link to comment
Share on other sites

Yesterday when I wrote the post, I just managed to upgrade to 10.9.4 and I was so exited about it, because I was going to be able to test Xcode 6.0.1 and tinker with Swift playgrounds, then YES, I had the segmentation fault. I tried to search about it and then read your post at:

http://www.insanelymac.com/forum/topic/291140-application-support-amd/?p=2064373

where you say that part of your solution was to use LLVM 3.5 (Xcode 6) from LLVM.org.

I downloaded the pre-built binaries for darwin of course and tried to symlinking the new clang into /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin but as you say there are lots of missing libraries and headers errors; I've tried to change paths and compiler arguments from within Xcode and changed the .profile file updating the PATH variable to include some binaries that reside into Xcode.app.

No luck. This is all over my head, so yes, I think it would be great if you open a thread on the subject and let us know how you managed to make it work please.

About the VMSvga2 driver, I tried to install the Mavericks version that you can get from sourceforge, but the vm could not reboot, so I've done nothing further about it, yet.

Thanks.

 

Good.

 

Here's the new thread

Link to comment
Share on other sites

 Share

×
×
  • Create New...