Search results

After getting Yosemite running on my desktop, I figured now would be as good of a time as ever to pursue getting Yosemite on my laptop. I'm currently rocking a Thinkpad X230i. This is the same as Lenovo's X230, except it runs an i3 (i3-3120M) instead of an i5 or higher like in the other models...

I figure now is a good time as ever to break down my Clover install here. I actually performed the install using my Unibeast drive. I performed the install, same as always, except I did NOT run MultiBeast after I got a desktop. Rather, I ran Clover and followed the Yosemite/Clover guide...

I've been a little out of touch with this thread, so I apologize, but thank you for pointing this out. I'll give this a try. I just recently switched over to using Clover, and while it took a while for me to stumble through everything it's really fairly straightforward. The only thing I don't...

I used Toleda's CloverALC script over here, with some caveats: https://github.com/toleda/audio_CloverALC I have a motherboard with the 889 on it, and I wanted onboard to work so I could connect my headset that way. The script works, but I had to do some initial setup. Before it would work, I...

I made the jump to the Clover bootloader, and while the initial road was bumpy, I'm loving it a lot more than Chimera/Chameleon. I had to call Apple with the 12-digit code, and while the hold time was a little long (about 20 minutes), they identified and solved the issue in less than 2 minutes...

Ah, now that I admit I'm a cheater with. I have a USB DAC that I use for music. I can see if I can get onboard working tonight though! EDIT: From what I can see, the board uses the ALC889, and Kext Dev Mode needs to be enabled. Will peek at this, especially since this may be the root of my USB...

When I did my initial install I only had the keyboard, mouse, and my thumbdrive connected. On the F12 BIOS I had to disable all other devices; upgrading to the beta UEFI BIOS allowed me to install with only a couple settings changed.

Glad to hear you're up and running! :) I'm having the USB 3.0 issues as well on my end.

I'm currently not using any special boot flags. Gigabyte has a beta BIOS for UEFI. Updating to that removed the DSDT requirement and fixed a lot of my problems. After I finished my install, I was able to boot using my thumbdrive for an initial setup (username, first-run of Multibeast). When...

I'll be honest when I say I'm probably following some old guides, haha. I had always used the DSDT file, since...I want to say Snow Leopard or Lion/ML. Granted, Gigabyte's definition of "UEFI" in the Sandy Bridge era is kinda weird, period. EDIT: Well hey, that might help. I didn't realize that...

I did keep the board in UEFI mode, since I've never had an issue with it otherwise. I don't have any more time tonight to mess with it, but thank you for pointing out the rollback. I think that rollback is where that HPET fix is at. I'll try my current config with a fresh install, MultiBeast...

This will be rough, but I'm documenting additional things I'm doing to get things working. Disabled ALL extra hardware (audio, built-in video, firewire, serial, etc.), unplugged all but USB drive, keyboard, mouse. I was able to boot without other flags! And now I'm getting the HPET error that I...

Currently working on getting my Sandy Bridge setup running with Yosemite. Current process (EDITED for working process!): Boot 0: * Updated board to beta UEFI BIOS (since Gigabyte finally decided to get with the program \o/) * Loaded defaults, made a couple changes (will point out once finished)...

Just switch it over to a USB2 port and boot from that, that worked for me. :)

I was having that same issue, i5 2500k with a Z68X-UD3H-B3. Turns out that I had my drive plugged into a USB 3.0 port, not a USB 2 port. Switching to a USB 2 port solved the issue. Now if I can only figure out why my install keeps stopping at mbinit...