Having issues finding a distribution that will work for me in VMWare... Latest to fail has been Idenub 1.6_1058 (booted up the install fine, things went well... On reboot however it pops up with "efi_inject_get_devprop_string NULL trying stringdata" and then shuts down)...
Wondering if it's the distro, or some sort of patch I need that I havn't found the answer for yet... Hoping someone can help :D
AMD Athlon 64 X2 Dual Core 5000+
2.61 Ghz, 3.0gb Ram
NVIDIA GeForce 7900GS
Booted the install disk using Daemon tools.
booting with -v leads to same message as above plus:
Patched DMI TAble.
No DSDT replacement found. Leaving ACPI data as is
Starting Darwin x86
Then it shuts down.
I don't use VMWare so not much help could be offered. But that error message is in the very early stage.
What kernel did you select for it?
Don't remember seeing an option on install to select a kernel (might have missed it) so just Vanilla is my guess
Originally Posted by ratvn
Ok, my friend, your AMD CPU can not run vanilla kernel (that is for Intel), and if you select it then a KP will follow for sure. It does look like wrong kernel from that error message.
Originally Posted by egrog1717
The closest one is Voodoo kernel. So my suggestion would be trying it again to see.
At installer screen, there should be a tab for customization before going to the next installation screen.
It's my best suggestion as I don't use VM.
Try it and keep us posted.
Hey now that would make sense! LOL...
(Knew I missed a step in installation somewhere!)
Thanks for the help, will give it a shot when I get home.
So I go it reinstalled no problem, but when I went to boot up after the restart it grey screen of death'd me...
Originally Posted by ratvn
Booting up with -v gave the following errors:
Booted up in safemode, got past the previous two errors but kicked out here:
(And I'm sorry, I know this isn't a distro issue anymore... Mayhap a mod can kick it over to the install forum for me please?)
Now that's much better.
The true error you got there is not those lines. It's the beginning of "waiting for root device error", which means that OSX can not see your hdd/partition using your selection of SATA/PATA controller drivers. It can only output what's going through, and not for something that OSX's working on and has not finished yet.
So, what is your choice under chipsets/SATA/PATA controllers?
Keep in mind that for a direct installation to a physical partition, this process only involves drivers for system hardware. Under Windows host as in VM, there are more steps, maybe, and the other consideration is that windows and OSX use these controllers in different modes.
The best suggestion there is to watch the installation process again closely. After those lines about waiting for boot volume so and so, there should be a line saying got boot device with UUID.....then OSX should tell you what kexts/drivers it loads for hdd/DVD recognition, and that what you should try to select during your custom choices.
You may have to set your BIOS for OSX to work, and what is your board chipsets/SATA controllers? Should be either ATI or Nforce, and the series? AHCI supported?
Should also try to boot with these options: -x -v cpus=1 (and/or busratio=20).