Well, cool. Thanks. I got in to the installer now.
If it's ok with everybody, I'll just keep asking questions.
I can't use my keyboard nor touchpad on my laptop in the installer. I have to use a cheapo Dell keyboard and Microsoft mouse, both of which work in the installer. I don't even know what to look for to make that work.
Wifi doesn't work. Which is fine for now, but I'd like to get it fixed at some point.
Finally, my hard drive isn't showing up in the "Install OS X" screen when it's in the computer. I plugged it into an external SATA adapter and that works well enough, albeit slowly. But at this point, I have a laptop turned desktop with a small part of OS X on it. Yay.
Yes, that seems to get passed that particular problem. So, that's cool.
But now there's another problem! You can see it in the attached image. Attached Files IMG_20120808_142512.jpg 1.44MB 93 downloads
Here are the options I used to install Chameleon to my jump drive using Enoch-rev.2039.pkg.
1) I set the Destination to the correct drive.
Chameleon BootloaderStandardModulesResolutionSettingsGeneral OptionsEthernetBuiltIn=YesKernel FlagsVerbose ModeIgnore Caches
Sorry for the poor image quality. I can't exactly say I was in a well-lit room. Attached Files IMG_20120807_115141.jpg 1.53MB 53 downloads
I'm trying to install Mountain Lion on my Dell Inspiron 1545. There is a 160GB hard drive in it that I don't mind wiping out.
Prodedure I used:
Used the Disk Utility in OS X to copy the Base System image to a 32GB jump drive
Ran the newest version of Chameleon I could find (r2039), and used the "Built-in Ethernet=Yes" flag (along with a few others in various configurations)
Nicely ejected the jump drive and popped it in my laptop
Upon boot into Chameleon, I chose the "Boot Verbose" option
What went wrong:
About 10 seconds into the boot sequence, I see the following message:
AppleYukon2 - RomlessInit - getProperty failedafter which is a stack trace. I can put up a picture of the stack trace if it would help. (Or if there is a way of putting up the complete boot log, I'd be willing to do that if somebody would tell me how.)
Has anybody see this kind of error before? How might I go about figuring out what...