Jump to content
InsanelyMac Forum


  • Content count

  • Joined

  • Last visited

About drivemusicnow

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Location
  • Interests
    DIY Audio, auto racing, learning German
  1. drivemusicnow

    Variety of issues with working Mavericks install

    So I decided I wanted to at least figure the situation out with chameleon before re-installing windows... and I seem to have gotten almost everything to work properly. I've created an ssdt in order to try A) learn about it try to get more than just 8, 35, and 37, and C) eventually overclock the cpu. The problem is that I still only have 8-35 and 37... and I'm not entirely sure why. I've attached an IOREG copy and my ssdt and I was hoping someone might be able to point me in the right direction. Thanks!!! /* * Intel ACPI Component Architecture * AML Disassembler version 20130725-64 [Jul 30 2013] * Copyright (c) 2000 - 2013 Intel Corporation * * Disassembly of iASLzioRoP.aml, Tue Mar 25 21:39:25 2014 * * Original Table Header: * Signature "SSDT" * Length 0x00000391 (913) * Revision 0x01 * Checksum 0x71 * OEM ID "APPLE " * OEM Table ID "CpuPm" * OEM Revision 0x00001000 (4096) * Compiler ID "INTL" * Compiler Version 0x20130725 (538117925) */ DefinitionBlock ("iASLzioRoP.aml", "SSDT", 1, "APPLE ", "CpuPm", 0x00001000) { External (_PR_.CPU0, DeviceObj) External (_PR_.CPU1, DeviceObj) External (_PR_.CPU2, DeviceObj) External (_PR_.CPU3, DeviceObj) External (_PR_.CPU4, DeviceObj) External (_PR_.CPU5, DeviceObj) External (_PR_.CPU6, DeviceObj) External (_PR_.CPU7, DeviceObj) Scope (_PR.CPU0) { Name (APSN, 0x04) Name (APSS, Package (0x18) { Package (0x06) { 0x0F3C, 0x000130B0, 0x0A, 0x0A, 0x2700, 0x2700 }, Package (0x06) { 0x0ED8, 0x000130B0, 0x0A, 0x0A, 0x2600, 0x2600 }, Package (0x06) { 0x0E74, 0x000130B0, 0x0A, 0x0A, 0x2500, 0x2500 }, Package (0x06) { 0x0E10, 0x000130B0, 0x0A, 0x0A, 0x2400, 0x2400 }, Package (0x06) { 0x0DAC, 0x000130B0, 0x0A, 0x0A, 0x2300, 0x2300 }, Package (0x06) { 0x0D48, 0xFABF, 0x0A, 0x0A, 0x2200, 0x2200 }, Package (0x06) { 0x0CE4, 0xF088, 0x0A, 0x0A, 0x2100, 0x2100 }, Package (0x06) { 0x0C80, 0xE682, 0x0A, 0x0A, 0x2000, 0x2000 }, Package (0x06) { 0x0C1C, 0xDCAB, 0x0A, 0x0A, 0x1F00, 0x1F00 }, Package (0x06) { 0x0BB8, 0xD304, 0x0A, 0x0A, 0x1E00, 0x1E00 }, Package (0x06) { 0x0B54, 0xC98C, 0x0A, 0x0A, 0x1D00, 0x1D00 }, Package (0x06) { 0x0AF0, 0xC042, 0x0A, 0x0A, 0x1C00, 0x1C00 }, Package (0x06) { 0x0A8C, 0xB727, 0x0A, 0x0A, 0x1B00, 0x1B00 }, Package (0x06) { 0x0A28, 0xAE39, 0x0A, 0x0A, 0x1A00, 0x1A00 }, Package (0x06) { 0x09C4, 0xA579, 0x0A, 0x0A, 0x1900, 0x1900 }, Package (0x06) { 0x0960, 0x9CE6, 0x0A, 0x0A, 0x1800, 0x1800 }, Package (0x06) { 0x08FC, 0x9480, 0x0A, 0x0A, 0x1700, 0x1700 }, Package (0x06) { 0x0898, 0x8C46, 0x0A, 0x0A, 0x1600, 0x1600 }, Package (0x06) { 0x0834, 0x8438, 0x0A, 0x0A, 0x1500, 0x1500 }, Package (0x06) { 0x07D0, 0x7C55, 0x0A, 0x0A, 0x1400, 0x1400 }, Package (0x06) { 0x076C, 0x749E, 0x0A, 0x0A, 0x1300, 0x1300 }, Package (0x06) { 0x0708, 0x6D11, 0x0A, 0x0A, 0x1200, 0x1200 }, Package (0x06) { 0x06A4, 0x65AF, 0x0A, 0x0A, 0x1100, 0x1100 }, Package (0x06) { 0x0640, 0x5E76, 0x0A, 0x0A, 0x1000, 0x1000 } }) Method (ACST, 0, NotSerialized) { Return (Package (0x06) { One, 0x04, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000000, // Address 0x01, // Access Size ) }, One, 0x03, 0x03E8 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000010, // Address 0x03, // Access Size ) }, 0x03, 0xCD, 0x01F4 }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000020, // Address 0x03, // Access Size ) }, 0x06, 0xF5, 0x015E }, Package (0x04) { ResourceTemplate () { Register (FFixedHW, 0x01, // Bit Width 0x02, // Bit Offset 0x0000000000000030, // Address 0x03, // Access Size ) }, 0x07, 0xF5, 0xC8 } }) } } Scope (\_PR.CPU1) { Method (APSS, 0, NotSerialized) { Return (\_PR.CPU0.APSS) } } Scope (\_PR.CPU2) { Method (APSS, 0, NotSerialized) { Return (\_PR.CPU0.APSS) } } Scope (\_PR.CPU3) { Method (APSS, 0, NotSerialized) { Return (\_PR.CPU0.APSS) } } Scope (\_PR.CPU4) { Method (APSS, 0, NotSerialized) { Return (\_PR.CPU0.APSS) } } Scope (\_PR.CPU5) { Method (APSS, 0, NotSerialized) { Return (\_PR.CPU0.APSS) } } Scope (\_PR.CPU6) { Method (APSS, 0, NotSerialized) { Return (\_PR.CPU0.APSS) } } Scope (\_PR.CPU7) { Method (APSS, 0, NotSerialized) { Return (\_PR.CPU0.APSS) } } } Looks like it won't let me upload the ioreg file...
  2. drivemusicnow

    Cannot install Mavericks cause of error

    This website doesn't support using distros so you're not going to get a lot of responses. I would reading here http://www.insanelymac.com/forum/topic/280756-guide-the-all-in-one-guide-to-vanilla-os-x-including-chameleon-dsdt-for-beginners-updated-for-mavericks/ And then searching out dualboot on the same disk guides as there are a few tricks to make it work on an MBR partition.
  3. First, I'm absolutely not super knowledgeable about this stuff... but my recommendation would be: A) check BIOS settings. I would start here http://www.insanelymac.com/forum/topic/294837-vanilla-mountain-lion-install-intel-hd4600-onboard-graphics/ b )While you're in your BIOS, change it to boot the USB stick first. It appears to be trying to boot from your main drive, and you have diskutility/terminal from the installer.
  4. drivemusicnow

    Variety of issues with working Mavericks install

    First off, thanks for replying! I think something I've learned is that when I do this, I should keep a log regarding what I did, and how the computer behaved. I have done so many things now, that it's difficult to keep track of whether a problem was solved by a specific action. I previously applied the DSDT with Pjalm patches for my board, and perhaps directly related or not, the problem does not appear as often. I also believe that the freezing during booting problem happens less often now, but I don't think I can say it's gone away completely yet... I have basically given up on getting the nvidia web driver to work, but I might tackle that again later. I think the issue with clover is that while I created the partition as GUID prior to installing windows, I don't think it's actually booting EFI. It is also on it's own SSD. I may try to reinstall windows7 on that partition and see if I can't get it to work UEFI. What is very confusing, is looking at my windows drive, I have a 200mb partition in front that is a "GPT protective partition". I didn't think windows would install BIOS onto a GUID partition, but it appears to have. I guess this makes sense, because I can boot it from chameleon, and my understanding is that chameleon couldn't boot it if it was installed UEFI. I do believe clover can launch non UEFI, however I don't have it installed that way. The next question is whether I'll be able to virtualize that partition within OSX as well. Reading on some of the other forums, it seems that virtualizing an EFI partition is more difficult, but not impossible. Perhaps I'm better off sticking with chameleon/bios booting. The boot speed improvement on the OSX side is nice and in general, there does seem to be a lot more flexibility with clover, but I'm not sure at this point whether I want to do it that way.
  5. drivemusicnow

    Variety of issues with working Mavericks install

    Bit of an update. Installed osx and clover onto a large usb drive.. I now have it booting from clover from the USB and can then boot to my OSX SSD, and the OSX USB drive with no problems. It shows the Windows drive, however it won't boot to it saying that no bootable disk was found. I think the issue is because I need to do one of the following in my EFI partition: 1) For Windows 7 you need to copy the folder efi\microsoft\boot to efi\boot (one level up), copy the file bootmgfw.efi to that folder and rename it to bootx64.efi (from here http://www.md0mdi.com/uefi-multi-boot-clover/ ) or 2) Mount the main EFI with Clover configurator; Open the main EFI file drive on the desktop, browse to EFI/Clover and copy CLOVERX64.efi to /EFI/Mircosoft/Boot. In EFI/Microsoft/Boot rename the file bootmgrfw.efi to bootmgfw-orig.efi In EFI/Microsoft/Boot rename the file CLOVERX64.EFI to bootmgfw.efi Reboot without the Clover USB From here: (http://www.insanelymac.com/forum/topic/293574-beginners-guide-to-uefi-tripledual-boot-os-x-windows-and-linux-kali-on-an-single-true-gpt-ssd/?p=1968818) The second one makes more sense to me, as the first one is talking about doing this prior to windows installation, and I obviously already have windows installed.... Would love some form of confirmation that this second option is correct. It's been a little silent in here. Currently, I can also boot from chameleon on the OSX SSD, which then has no problem booting into windows. FYI, all my partiitons are GUID, and I followed the standard windows installation procedure, after removing my OSX ssd.
  6. drivemusicnow

    Variety of issues with working Mavericks install

    So the experiment with clover has begun. I managed to install OSX onto a USB drive, and get it booting normally from UEFI with Clover. Then it all kind of went crazy. I think it was because I was trying to define some of the SMBIOS parameters and hoping that clover would fill in the rest. Then I removed both USB sticks that clover was installed on, and it was still managing to boot with clover... my only thought is that it's generating a mountable efi portion from my SSD? Quite confusing. Either way, I think I have the general hang of the tools, and I was hoping to get a bit of feedback on the following. Here is the latest version of my config.plist file and I was hoping perhaps someone who is more familiar could see if this is appropriate. I had it running without the fixhpet, c-states/p-states, so obviously those aren't necessary, but I'm not sure if I should include them. I'm specifically curious if the "KernalPM" is necessary for my board. The only other very curious thing to me is that I typed into clover configurator the IOAHCIBlockStorage patch with the exact values from here http://www.skylineosx.com/post-installation/enable-trim-on-your-ssd/ and obviously that isn't what shows up in the file... Any help would be appreciated!!!! <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>DropOEM_DSM</key> <false/> <key>Fixes</key> <dict> <key>AddDTGP_0001</key> <false/> <key>AddHDMI_8000000</key> <false/> <key>AddIMEI_80000</key> <false/> <key>AddMCHC_0008</key> <false/> <key>AddPNLF_1000000</key> <false/> <key>DeleteUnused_400000</key> <false/> <key>FIX_ACST_4000000</key> <false/> <key>FIX_ADP1_800000</key> <false/> <key>FIX_INTELGFX_100000</key> <false/> <key>FIX_RTC_20000</key> <false/> <key>FIX_S3D_2000000</key> <false/> <key>FakeLPC_0020</key> <false/> <key>FiX_TMR_40000</key> <false/> <key>FiX_WAK_200000</key> <false/> <key>FixAirport_4000</key> <false/> <key>FixDarwin_0002</key> <false/> <key>FixDisplay_0100</key> <false/> <key>FixFirewire_0800</key> <false/> <key>FixHDA_8000</key> <false/> <key>FixHPET_0010</key> <true/> <key>FixIDE_0200</key> <false/> <key>FixIPIC_0040</key> <false/> <key>FixLAN_2000</key> <false/> <key>FixRegions_10000000</key> <false/> <key>FixSATA_0400</key> <false/> <key>FixSBUS_0080</key> <false/> <key>FixShutdown_0004</key> <false/> <key>FixUSB_1000</key> <false/> <key>NewWay_80000000</key> <false/> </dict> <key>Name</key> <string>dsdt.aml</string> <key>ReuseFFFF</key> <false/> </dict> <key>SSDT</key> <dict> <key>DropOem</key> <false/> <key>Generate</key> <dict> <key>CStates</key> <true/> <key>PStates</key> <true/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>-v dart=0</string> <key>Legacy</key> <string>LegacyBiosDefault</string> <key>Log</key> <false/> <key>Secure</key> <false/> <key>Timeout</key> <integer>5</integer> <key>XMPDetection</key> <string>Yes</string> </dict> <key>Devices</key> <dict> <key>USB</key> <dict> <key>FixOwnership</key> <false/> <key>Inject</key> <false/> </dict> <key>UseIntelHDMI</key> <false/> </dict> <key>GUI</key> <dict> <key>Language</key> <string>en:0</string> <key>Mouse</key> <dict> <key>Enabled</key> <false/> </dict> <key>Scan</key> <true/> <key>ScreenResolution</key> <string>2560x1440</string> <key>Theme</key> <string>Mavs Style</string> </dict> <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <true/> <key>NVidia</key> <false/> </dict> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <false/> <key>KernelPm</key> <true/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string></string> <key>Find</key> <data> sOAQ6qA= </data> <key>Name</key> <string>IOAHCIBlockStorage</string> <key>Replace</key> <data> qqqqqqqqqg== </data> </dict> </array> </dict> <key>RtVariables</key> <dict> <key>MLB</key> <string>C02LY948F8JC60014</string> </dict> <key>SMBIOS</key> <dict> <key>ProductName</key> <string>iMac14,2</string> <key>SerialNumber</key> <string>C0XXXXXXXXX</string> <key>Trust</key> <false/> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Yes</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist>
  7. drivemusicnow

    Variety of issues with working Mavericks install

    So some additional information. I reloaded kexts, booted twice without problem, third time, it hangs up. I reboot with -f, GraphicsEnabler=No, nv-disable=1 and it still it hangs up where you see it in the attached pictures. (Long pause at 0265, then quickly drops the 5 bluetooth transport messages) It boots with -x without problems. I do not know how to start troubleshooting this. I'm thinking I might try clover... It is quite intimidating and I'm going to try to read up on the zetam.org wiki to learn as much as possible, but I feel like even with an "easy" build like mine, it should be able to get me closer to the "perfect" setup I am hoping for. It seems like a pretty impressive tool, but I'm concerned about the fact that clover itself seems to be constantly evolving at a fairly rapid pace. It seems a bit like an uphill battle to try and absorb a base level knowledge, stay up to date, and not manage to do something stupid. That said, I'm curious if anyone could offer some advice on a config.plist starter file?
  8. So, several pieces of information to preface, I'm very new at this, and I don't have any CS background. I have an Z87x- UD7-TH/4770K/GTX770 computer dual booting windows 7 and OSX 10.9.2 I use "the program group that shall not be named"(MB) and myHack. In general, everything works very smoothly. I have three issues that I'm seeing. 1) Occasionally I'll run into a boot issue where it freezes after the bluetooth IOcontroller transport. I believe this is a graphics related issue from the plethora of reading I've done. I spoke with Rampage, and he recommended loading the Nvidia retail drivers. I've installed those, which have updated and gives me the control panel option to select use apple or nvidia drivers. Trying to select the nvidia drivers after restart, it again freezes at the previously mentioned bluetooth iocontroller transport line. Rebooting with -x, rerunning MB, repairing permissions with disk utility, then restarting will allow it to restart without any bootflags. Then I run myHack myfix, and the computer runs properly again, but it is not actually using the nvidia driver (checked in console, as well as shown in the control panel) I've tried this with and without the .dylib file in modules that is recommended by Rampage's guide, no difference. I haven't seen anyone explicitly mention this, but I am curious if the nvidia graphics card issue could be related to my system definition. It's my understanding that for overclocking of the CPU to work on the OSX side, the system definition must be an iMac which is how I have it set up (No OC yet, but I would like to in the future). Does the nvidia driver need a MacPro definition? 2) Also, from the windows 7 side, the computer powers off and restarts as expected. From the OSX side, about 70% of the time, when I click restart or shutdown, the computer won't actually completely shut down. It powers off the display, it spins down the fans, but the computer is still "on". I then have to hard power off or restart. Wake on Lan is off in BIOS, and I'm really not sure what else it might be. I've tried with and without anything plugged into the USB ports, and I still run into this issue. Lastly, the setup was done using the combination of myHack and MB, and based on the hardware, went very smoothly. Since doing this (over the past several weeks) I understand the communities issues with Tony profiting off other peoples work, and I would much prefer to try and support the actual developers. But how? Now that I have a running system, I have no idea how I would migrate from chimera to chameleon, or how to have myHack do a similar "rescue" reload of kexts that has been helpful to me as I mess about. I would appreciate any help anyone might be able to provide. Thanks!