Jump to content
InsanelyMac Forum

ohsht

Members
  • Content count

    13
  • Joined

  • Last visited

About ohsht

  • Rank
    InsanelyMac Protégé
  1. ohsht

    Clover General discussion

    Yes it's a wired Microsoft Natural Keyboard Pro. It works without any problem for Chameleon. Which BIOS settings in particular should I look at? (This is a BIOS - not UEFI - boot on the Asus board in my signature).
  2. ohsht

    Clover General discussion

    Is those connected via Bluetooth, or a proprietary wireless connection? are you booting from a BIOS motherboard, or UEFI?
  3. ohsht

    Clover General discussion

    After a lot of trial and error I got Clover to work. I needed FakeSMC.kext in /EFI/kexts/10.8 One odd thing that doesn't yet work is using a USB keyboard in Clover's boot menu. The only way I can interact with the menu is if I plug in a PS/2 keyboard. Is this a known problem? I use Apple's wireless bluetooth trackpad for a mouse, so I wasn't expecting to be able to use it when booting. Is there a way? Thanks for all the hard work!
  4. ohsht

    AppleHDA patching in Mountain Lion

    Thank you! I've been struggling with this since I upgraded from Lion to ML several weeks ago. Finally my system is fully functional again.
  5. ohsht

    ASUS P6T 10.6.5 update no Ethernet

    Worked for me, too. thanks!
  6. I have the exact same thing, using an Nvidia 9400GT card. Has anyone managed to get past this?
  7. I've successfully upgraded to 10.5.7 with the combo updater. All I had to do to get back to the previous functionality was fix the Yukon kext as indicated in the tutorial. So now I'm still running the 9.5.0 voodoo kernel on my Chameleon 2 RC EFI partition. Whenever I try to boot using the new vanilla kernel, even with -v -f -s, it ultimately just reboots before getting to the login screen. I can see that it's loading a lot of stuff, but it doesn't panic - it just reboots. The problem is it goes by too quickly for me to see what's going on. Is there any log file where we can look at to trace what's happening as the kernel loads, and what could be going wrong? Any other ideas? Thanks.
  8. The only way I've found to reliably boot on any given volume (either the installation DVD, or the partition I eventually managed to install on) was if I used the "boot-uuid={your UUID}" instead of the "rd=diskXsY" method. You'll need a running mac to get the UUID for the install DVD you're using (get info from disk utility), but after you get it to work once, you can get the new UUID of your new installation, and put that in your boot.plist in the kernel flags. My BSD drive names still change pretty randomly, but it doesn't affect my booting.
  9. I don't really know how to fix your EFI parition. You might be able to do it in single user mode, using fdisk that comes with the chameleon or EFI_boot installations, but I'm no expert. About the vista bootloader - I did nothing. I actually tried some stuff with EasyBCD, but eventually undid everything. My main bootloader is chameleon 2 RC1 on the Leopard drive's EFI partition - that's where I can choose to boot from the Vista partition which only has the single Vista entry in its boot loader. The only guide I followed is the one for installing Chameleon on the EFI partition.
  10. it replaces the part about the EFI partition, I think. make sure to copy all your extensions, kernel, and plist properly. I suggest looking into the Boot.plist file that you have on your EFI partition. if it uses the diskXsY format to identify the root device for the kernel, then that will always change if you change your drive configuration. what I did was use "boot-uuid={my leopard installation UUID}" insted of "rd=diskXsy". diskXsY may change, but the UUID will always stay the same. you can get your UUID by getting the info for your leopard install partition from Disk Utility.
  11. are they on the same drive? I got vista and leopard to dual boot on two different drives by installing Chameleon 2 RC1 on the EFI partition of the OS-X drive. works like a charm. I followed this guide: http://www.insanelymac.com/2009/04/how-to-...ameleon-20-rc1/ I tried EasyBCD but got nowhere.
  12. P6T Deluxe V2 I eventually had to disable all CPU settings in the BIOS before i could successfully run the installation. Otherwise it would hang during the DVD consistency check. now I'm up and running, and dual booting with vista on a second HD, using Chameleon on my EFI partition.
  13. I had two issues: One: The attached Slimbuild-Preboot.iso didn't work for me. it failed with the "isolinux: image checksum error". I had to: 1. download the boot-132 slimbuild installation 2. download and build CDRTools, to get mkisofs 3. mod the slimbuild2.sh script to use mkisofs instead of hdiutil 4. rebuild a new Slimbuild-Preboot.iso with all my extensions, plist, etc. Two: I spent a lot of time trying to figure out the right diskXsY/boot-uuid code for my PATA DVD drive. I was constantly hitting the dreaded "still waiting for root device". I eventually realized that it's because there was no support for the Marvell controller. I found the solution here: http://my.ukrweb.info/en/node/73 just throw that kext into your Slimbuild and you can install from a PATA DVD. I eventually got it to work using boot-uuid. now I just need to figure out how where to install it alongside my working vista.
×