Jump to content

eep357

Retired
  • Content Count

    2,497
  • Joined

  • Last visited

  • Days Won

    60

Reputation Activity

  1. Like
    eep357 got a reaction from C.Frio in FAQ-Start Here   
    TECHNICAL FAQ
    The FAQ is set up to answer many of the technical questions that are commonly asked! This is not a place to ask for help. Use the forum instead.
    Frequently Asked Questions:
     
    1) Q: What is OSx86?
    2) Q: Is it legal?
    3) Q: What minimum hardware specs should have to install Mac OS X on a PC?
    4) Q: What versions of Mac OS X can be installed?
    5) Q: What is a kext and how to install?
    6) Q: What is a kernel?
    7) Q: What is a bootloader?
    8) Q: What is "vanilla"?
    9) Q: What is "native"?
    10) Q: How do I install Mac OS X on my PC?
    11) Q: I get only a grey screen or a grey screen with the Apple logo when trying to boot, how can I fix this?
    12) Q: I get this message "Still waiting for root device" when booting, what are the solutions?
    13) Q: When I boot, I get the error: "HFS + partition error". Before I booted without problem!
    14) Q: What is "boot0: error"?
    15) Q: How to change the display resolution?
    16) Q: How to show hidden files and folders?
    17) Q: Retail? / Release?
    18) Q: What is DSDT?
    19) Q: What is QE/CI?
    20) Q: What is "Natit"? - Outdated
    21) Q: What is "Aty_init.kext"? - Outdated
    22) Q: What is "com.apple.Boot.plist" / "org.chameleon.Boot.plist"?
    23) Q: What. "DS_Store"?
    24) Q: MBR, GPT, what is it and what are the differences?
    25) Q: How to fix Unknown CPU Error in About This Mac
    2012-original by fantomas_1
     
     
  2. Like
    eep357 got a reaction from Gringo Vermelho in What is Speedstep and how do I patch it?   
    appleHDA's you have should be fine. Adult ADD for the winz!
  3. Like
    eep357 got a reaction from Gringo Vermelho in What is Speedstep and how do I patch it?   
    add DTGP method to devices?
     
    Edit: found this, although cheaters never win, at the very least it may help as a reference to assist with some entries. Patch from Olarila.com for Intel DP43TF mobo, and of course patch is for use with DSDT Editor, where as Real Men use DSDTSE
    DP43TF.txt
  4. Like
    eep357 got a reaction from Micky1979 in Bug Reporting   
    Hello Pandora's Box Beta testers! Here is a location to report any bugs, and as a beta, there will be bugs.
     
    Please keep the comments here on topic, there are other topics to discuss any suggestions, opinions or support issues not related to a bug in the application.
     
    Note: Please include any possible photos, screenshots, installation or system logs, etc so that we may be able to determine the cause and/or solution to your problem.
  5. Like
    eep357 got a reaction from C.Frio in FAQ-Start Here   
    TECHNICAL FAQ
    The FAQ is set up to answer many of the technical questions that are commonly asked! This is not a place to ask for help. Use the forum instead.
    Frequently Asked Questions:
     
    1) Q: What is OSx86?
    2) Q: Is it legal?
    3) Q: What minimum hardware specs should have to install Mac OS X on a PC?
    4) Q: What versions of Mac OS X can be installed?
    5) Q: What is a kext and how to install?
    6) Q: What is a kernel?
    7) Q: What is a bootloader?
    8) Q: What is "vanilla"?
    9) Q: What is "native"?
    10) Q: How do I install Mac OS X on my PC?
    11) Q: I get only a grey screen or a grey screen with the Apple logo when trying to boot, how can I fix this?
    12) Q: I get this message "Still waiting for root device" when booting, what are the solutions?
    13) Q: When I boot, I get the error: "HFS + partition error". Before I booted without problem!
    14) Q: What is "boot0: error"?
    15) Q: How to change the display resolution?
    16) Q: How to show hidden files and folders?
    17) Q: Retail? / Release?
    18) Q: What is DSDT?
    19) Q: What is QE/CI?
    20) Q: What is "Natit"? - Outdated
    21) Q: What is "Aty_init.kext"? - Outdated
    22) Q: What is "com.apple.Boot.plist" / "org.chameleon.Boot.plist"?
    23) Q: What. "DS_Store"?
    24) Q: MBR, GPT, what is it and what are the differences?
    25) Q: How to fix Unknown CPU Error in About This Mac
    2012-original by fantomas_1
     
     
  6. Like
    eep357 got a reaction from satishvish5 in Help Cannot get iatkos l2 to see ethernet on ASUS P5KPL-AM/PS Realtek RTL8111C Gigabit LAN   
    Try this one, works for 10.7 and 10.8, is NOT lyn2mac version
    RTL81xx.zip
  7. Like
    eep357 got a reaction from Jeffrey.C in iCloud/Facetime/AppStore login errors   
    Fixing Login Errors For Apps That Connect To Apple's Servers


     

    These steps should fix 98% of login errors, but some specific exceptions still exist and are omitted to avoid unnecessary confusion. Since this is a FAQ and not a full manual on all things Ethernet, it's not feasible to detail every method mentioned here, but hopefully at least it will let you know where to go next. So always start here!:


     

    To sign into any of the Apple services/apps that require authentication through Apple run servers, there are a few conditions that must be met when first logging in. For apps such as iCloud, once logged in the first time you will stay logged in even after reboots and configuration changes until manually logged out, at which point to log back in the same conditions will again apply.


     

    1) Must have a working ethernet adapter that can at least show up as a possible network connection. It must also work, but you might be able to get away with mostly working if your lucky.







    You'll need a kext that supports your NIC to proceed.


     

    2) It must also show as "Built In".







    Three possible ways of doing this which are all different ways of achieving the same result.



    Easy way, add following to Chameleon's org.chameleon.Boot.plist in /Extra folder:





    <key>EthernetBuiltIn</key>
    <string>Yes</string>

     

    Medium way, add EFI string to Chameleon's org.chameleon.Boot.plist in /Extra folder using tool such as "EFI Studio"


     

    Hard way, edit DSDT to have NIC device, i.e. LAN0 show as internal


     

    3) It needs to be listed as en0. i.e. The first, or primary, network device recognized by OSX






    Issue here will usually be that your wifi got enabled first and thus became en0, making your ethernet en1. To correct the issue: First if your wifi device or whatever is currently listed as en0 can be removed/unplugged from your PC by removing 3 screws or less, and you own a screwdriver, remove/unplug it. Next go to System Preferences > Network (as seen above in #1) and click the minus button to remove all the listed network devices, then reboot. Upon reboot return to System Preferences > Network and hit the plus button, add only your ethernet, open System Information (as pictured directly above) and verify Ethernet is now en0, if it is you can add your other devices now too.



    If ethernet is still showing as en1, you should then repeat the above steps, but this time just prior to reboot navigate to /Library/Preferences/SystemConfiguration/ and delete Networkinterfaces.plist and reboot.


     

    Extreeme cases only:



    If failure is still an option, and overkill seems necessary, it's possible to manually edit this plist. Again repeat initial steps, then copy plist to your desktop so it will be writable and open it with a text editor, cut an paste your ethernet so it appears first in the list, change every occurrence in it's section of en1 to en0, and vice versa for your prior en0 device, changing all it's en0 occurrences' to en1. Also verify here that ethernet shows:




    <key>IOBuiltin</key>
    <true/>



    and not




    <key>IOBuiltin</key>
    <false/>



    Once your satisfied with your edits (in simpler terms, your basically just swapping the two interfaces in the plist), launch Terminal from Applications/Utilities, enable root user by typing sudo -s and hitting enter, then entering your password when requested. Next enter the following, hitting return after each line:



    cp -R ~/Desktop/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/


    chown root:wheel /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    chmod 644 /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    reboot

     

    4) You need to have a SMBIOS which includes a valid serial number for the Mac model listed.







    For this, just use
    Chameleon Wizard to generate one for you and save to /Extra folder.

     
     

    WHEN ALL ELSE FAILS, BUT IS ALSO RIGHT, AKA-LAST RESORT:


     

    If you've met all the above requirements and ethernet works perfectly to browse the webs, but still can't log into these services, although it shouldn't need to be done manually, you may need to....


     

    First Open IORegistryExplorer (found in Xcode tools)






    Copy to Text Edit then get your ethernet MAC address






    Add results to org.chameleon.Boot.plist and after reboot you should see something like this



     
    And hopefully that will be it. Again, this won't cover every last possibility, but should be more than a good start.
  8. Like
    eep357 got a reaction from C.Frio in FAQ-Start Here   
    TECHNICAL FAQ
    The FAQ is set up to answer many of the technical questions that are commonly asked! This is not a place to ask for help. Use the forum instead.
    Frequently Asked Questions:
     
    1) Q: What is OSx86?
    2) Q: Is it legal?
    3) Q: What minimum hardware specs should have to install Mac OS X on a PC?
    4) Q: What versions of Mac OS X can be installed?
    5) Q: What is a kext and how to install?
    6) Q: What is a kernel?
    7) Q: What is a bootloader?
    8) Q: What is "vanilla"?
    9) Q: What is "native"?
    10) Q: How do I install Mac OS X on my PC?
    11) Q: I get only a grey screen or a grey screen with the Apple logo when trying to boot, how can I fix this?
    12) Q: I get this message "Still waiting for root device" when booting, what are the solutions?
    13) Q: When I boot, I get the error: "HFS + partition error". Before I booted without problem!
    14) Q: What is "boot0: error"?
    15) Q: How to change the display resolution?
    16) Q: How to show hidden files and folders?
    17) Q: Retail? / Release?
    18) Q: What is DSDT?
    19) Q: What is QE/CI?
    20) Q: What is "Natit"? - Outdated
    21) Q: What is "Aty_init.kext"? - Outdated
    22) Q: What is "com.apple.Boot.plist" / "org.chameleon.Boot.plist"?
    23) Q: What. "DS_Store"?
    24) Q: MBR, GPT, what is it and what are the differences?
    25) Q: How to fix Unknown CPU Error in About This Mac
    2012-original by fantomas_1
     
     
  9. Like
    eep357 got a reaction from C.Frio in FAQ-Start Here   
    TECHNICAL FAQ
    The FAQ is set up to answer many of the technical questions that are commonly asked! This is not a place to ask for help. Use the forum instead.
    Frequently Asked Questions:
     
    1) Q: What is OSx86?
    2) Q: Is it legal?
    3) Q: What minimum hardware specs should have to install Mac OS X on a PC?
    4) Q: What versions of Mac OS X can be installed?
    5) Q: What is a kext and how to install?
    6) Q: What is a kernel?
    7) Q: What is a bootloader?
    8) Q: What is "vanilla"?
    9) Q: What is "native"?
    10) Q: How do I install Mac OS X on my PC?
    11) Q: I get only a grey screen or a grey screen with the Apple logo when trying to boot, how can I fix this?
    12) Q: I get this message "Still waiting for root device" when booting, what are the solutions?
    13) Q: When I boot, I get the error: "HFS + partition error". Before I booted without problem!
    14) Q: What is "boot0: error"?
    15) Q: How to change the display resolution?
    16) Q: How to show hidden files and folders?
    17) Q: Retail? / Release?
    18) Q: What is DSDT?
    19) Q: What is QE/CI?
    20) Q: What is "Natit"? - Outdated
    21) Q: What is "Aty_init.kext"? - Outdated
    22) Q: What is "com.apple.Boot.plist" / "org.chameleon.Boot.plist"?
    23) Q: What. "DS_Store"?
    24) Q: MBR, GPT, what is it and what are the differences?
    25) Q: How to fix Unknown CPU Error in About This Mac
    2012-original by fantomas_1
     
     
  10. Like
    eep357 got a reaction from sugarface in iCloud/Facetime/AppStore login errors   
    If iCloud and Appstore work, then your done here. Your issue is with the iMessage specific fix. I haven't used the Chameleon method, only Clover cause it plays nicer with my GPU, and no reason to switch from what already works.
  11. Like
    eep357 got a reaction from YungRaj in mouse and keyboad not working   
    super secret ninja feature
  12. Like
    eep357 got a reaction from Jeffrey.C in iCloud/Facetime/AppStore login errors   
    Fixing Login Errors For Apps That Connect To Apple's Servers


     

    These steps should fix 98% of login errors, but some specific exceptions still exist and are omitted to avoid unnecessary confusion. Since this is a FAQ and not a full manual on all things Ethernet, it's not feasible to detail every method mentioned here, but hopefully at least it will let you know where to go next. So always start here!:


     

    To sign into any of the Apple services/apps that require authentication through Apple run servers, there are a few conditions that must be met when first logging in. For apps such as iCloud, once logged in the first time you will stay logged in even after reboots and configuration changes until manually logged out, at which point to log back in the same conditions will again apply.


     

    1) Must have a working ethernet adapter that can at least show up as a possible network connection. It must also work, but you might be able to get away with mostly working if your lucky.







    You'll need a kext that supports your NIC to proceed.


     

    2) It must also show as "Built In".







    Three possible ways of doing this which are all different ways of achieving the same result.



    Easy way, add following to Chameleon's org.chameleon.Boot.plist in /Extra folder:





    <key>EthernetBuiltIn</key>
    <string>Yes</string>

     

    Medium way, add EFI string to Chameleon's org.chameleon.Boot.plist in /Extra folder using tool such as "EFI Studio"


     

    Hard way, edit DSDT to have NIC device, i.e. LAN0 show as internal


     

    3) It needs to be listed as en0. i.e. The first, or primary, network device recognized by OSX






    Issue here will usually be that your wifi got enabled first and thus became en0, making your ethernet en1. To correct the issue: First if your wifi device or whatever is currently listed as en0 can be removed/unplugged from your PC by removing 3 screws or less, and you own a screwdriver, remove/unplug it. Next go to System Preferences > Network (as seen above in #1) and click the minus button to remove all the listed network devices, then reboot. Upon reboot return to System Preferences > Network and hit the plus button, add only your ethernet, open System Information (as pictured directly above) and verify Ethernet is now en0, if it is you can add your other devices now too.



    If ethernet is still showing as en1, you should then repeat the above steps, but this time just prior to reboot navigate to /Library/Preferences/SystemConfiguration/ and delete Networkinterfaces.plist and reboot.


     

    Extreeme cases only:



    If failure is still an option, and overkill seems necessary, it's possible to manually edit this plist. Again repeat initial steps, then copy plist to your desktop so it will be writable and open it with a text editor, cut an paste your ethernet so it appears first in the list, change every occurrence in it's section of en1 to en0, and vice versa for your prior en0 device, changing all it's en0 occurrences' to en1. Also verify here that ethernet shows:




    <key>IOBuiltin</key>
    <true/>



    and not




    <key>IOBuiltin</key>
    <false/>



    Once your satisfied with your edits (in simpler terms, your basically just swapping the two interfaces in the plist), launch Terminal from Applications/Utilities, enable root user by typing sudo -s and hitting enter, then entering your password when requested. Next enter the following, hitting return after each line:



    cp -R ~/Desktop/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/


    chown root:wheel /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    chmod 644 /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    reboot

     

    4) You need to have a SMBIOS which includes a valid serial number for the Mac model listed.







    For this, just use
    Chameleon Wizard to generate one for you and save to /Extra folder.

     
     

    WHEN ALL ELSE FAILS, BUT IS ALSO RIGHT, AKA-LAST RESORT:


     

    If you've met all the above requirements and ethernet works perfectly to browse the webs, but still can't log into these services, although it shouldn't need to be done manually, you may need to....


     

    First Open IORegistryExplorer (found in Xcode tools)






    Copy to Text Edit then get your ethernet MAC address






    Add results to org.chameleon.Boot.plist and after reboot you should see something like this



     
    And hopefully that will be it. Again, this won't cover every last possibility, but should be more than a good start.
  13. Like
    eep357 got a reaction from nolimitedude in Re-Branded Atheros AR5007 ( AR242x / AR542x ) not working on Snow Leopard   
    Sure yours shouldnt be 0086? A/b/g vs b/g? Maybe double check that part, cause the rest looks good
  14. Like
    eep357 got a reaction from silverfir in What is Speedstep and how do I patch it?   
    OK, no problem. We're all here to learn right? UHCI is USB 1.1 and EHCI is USB 2.0. 1394 is Firewire. Thats all for that part.
     
    Now motherboard manufacturers, will call them all kinds of different names in their ACPI tables, because they can. But they really like them to be 4 digits, and when having more than one of the same type of device, they usually will want one of those 4 digits to be a number, because numbering things is a good way to count them last I checked. So, you almost always have 2 separate EHCI devices and therefore can't call them both EHCI. So rather than call one EHCI and the next one something that doesn't make sense like EHCJ, Apple and some other mobo makers just use the first 3 digits or a 3 digit abbreviation of the device's name, followed by a number, and then only the number needs to be changed for each additional device. If it's a device that you would not have more than one of, the it get a full 4 digit abbreviation, and sometimes just a 3 digit abbreviation. Still with me? Ok, so Intel or ASUS or whoever may make a motherboard, don't care if these 4 digit names make sense to you or not, so don't always expect them to, and don't expect them to match what the device may be called in your bios settings or even in a DSDTSE patch. The naming used in DSDT is mostly cosmetic, but you can't just go renaming stuff without all the other references to that device being changed as well, so no need to go renaming things just for fun, because it probably won't turn out all that fun. So because the device names vary from board to board, tools like lspci become very useful, as hardware addresses are set in stone (or at least in thick mud). So if your applying your changes to the correct hardware address, your applying it to the right device too, no mater what it may be called. There are a few device hardware addresses that are almost always the same regardless of what mobo you have. For example. HDEF at 0x001B0000, LPC at 0x001F0000(note LPC is 3 digits, so it may have another digit, usually a letter tacked onto it), your GPU can be called a million different names in DSDT like POP1, PEG1, or PEGP if you renamed it for HDMI. On desktop it's hardware address will usually be either 0x0001000 or 0x0003000. and at 0x0002000 for laptop/onboard GPU's.
     
    Now in your case, your 2 EHCI entries are named EUSB and USBE respectively. Why are they named this you ask? Because that's what they named them. Your UHCI devices are named USB0, USB1 etc. Again, that's just what they decided to call them, and felt zero was a good number to start with since it's not technically even a real number. Apple would call them UHC1, UHC2, etc. If I was making the mobo, since they are USB 1.1 they would have been called OLD1, OLD2, OLD3, or SLO1, SLO2, etc, and everyone would know all they need too right there
     
    So, there you have in 2 minutes, what took me at least a month or more to learn, and of course I'm still learning too.
     
    My last bit of advice...Don't beat yourself up trying to get something working that you didn't even know wtf it was a couple days ago, You can always give it another go a bit later when you not feeling overwhelmed by all this new stuff and just take it one step at a time, no need to learn to run before you learn to walk. Leaving your PC on won't hurt it. If your fans are too loud, maybe your fans are too loud? They make quieter ones, fan controllers to slow down the loud ones when temps aren't high, vibration dampers, sound padding, water cooling, etc, etc. A computer does not need to be asleep to be quiet. Shutting it down and starting it up is also something people have been doing since shortly after the caveman days, and it's seemed to work pretty well too. Things like "not having my computer do such and such is not an option!" means your in the wrong place all together, and need to be on Apple support forums talking about your real mac, cause a thing or two not working on a hackintosh, comes with the territory.
  15. Like
    eep357 got a reaction from Dmos in Permanently Banned From Tonymacx86   
    Yup! I think it's fair to say most of us who started around the time 10.5/10.6 were released used a distro our first install. There was no "restore BaseSystem.dmg to USB, blah, blah done" to make easy retail as there is now. But, since those days have passed, I can assure there are no distro's in my file system
  16. Like
    eep357 got a reaction from fusion71au in iMessage/Messages Fix-How To   
    HOW TO FIX MESSAGES APP
    work in progress-subject to change


     

    This is only for those of you who are running Mountain Lion and getting this error since the Messages Beta for Lion ended on 12/14/12, but can still sign into other services like iCloud, App Store, etc.
     




    To fix this, we need an added value to the NVRAM which as of the time of this writing, can only be done by using the latest revision (r980) of boot loader by Slice, dmazar and others:
    To get the most recent installer package, we"ll use the tool created by STLVNUB: "Clover Grower" which can be downloaded here. You'll need Xcode's Command Line Tools installed, available for download in Xcode's preferences. The full list of instructions and options can be found here. Highly recommend reading them since every person's setup is different and there are many additional features you may want to explore. Only the basics here.
     
    Once you've downloaded Clover Grower, open Terminal.app from /Application/Utilities/Terminal.app. From your downloaded Clover Grower, drag and drop CloverGrower.command into terminal window and hit enter. Follow the prompts and enter password, Yes, etc. when asked. I recommend using all default settings unless you know what your doing. The process may take a little while as additional tools to compile are installed by the script. Once it's all done you should now have a folder with the package installer in it looking like this:

     
    Next prepare a USB thumb drive to install it onto. Use Disk Utility and format it as FAT32 with a MBR partition scheme. You can install the boot loader to your main hard drive later once your sure it all works and are comfortable with the configuration.
     
    Run the Clover package installer, leaving all settings as default except choose your thumb drive as the install location.






    Once the install is complete navigate to your new Clover USB drive and open the config.plist with text editor (RT Click and "Open With")

     
    This plist is like org.chameleon.Boot.plist and smbios.plist all in one file. Some options are the same, some are similar but have different names, and some are new for added config ability. This is where some system specific changes maybe needed, but first try simple leaving everything as is, and will only add info from our current smbios and what's needed for messages fix. Copy all info from your smbios into config.plist, and then you will need to change the names of the values inside each to match the new format. Here is how they need to be named in Clover:

     
    Additional examples can be found in /EFI/doc/ inside Clover drive.
     
    For UEFI boot and additional Graphics config, follow dmazar's instructions here
     
    For the Message part, first get your current serial which is in the smbios you just copied, and can also be found in system information:

     
    Now we add a new entry to config.plist that includes that 11 digit serial #, but we need to append 6 more digits onto it to make it a 17 digit #. So for example RM9MYSERIAL becomes RM9MYSERIAL234567 and the entry looks like this:
     


    <key>RtVariables</key>
    <dict>
    <key>MLB</key>
    <string>RM916W05EEP3574PC</string>
    </dict>

     
    In the image below you can see inserted into the list with some of the entry before and after visible to give an idea how it should look.
    This is mine for my own PC, not yours, it's for frame of reference on how the code is inserted and should not to be copied in full if you want anything to work!

    If you use a patched DSDT, copy it to the root of your main OSX drive.
     
    Try it!
     
    Please, please, please read all the instructions for Clover here before asking any Clover related questions!
     
    Edit or maybe Warning: One note, a few people have had message saying "account locked, call customer service" either right away or even after a successful login and a reboot. Not sure the cause, but I recommend rebooting twice before trying to log into Messages incase there are nvram values such as platform-uuid that if you are not specifying them in config.plist, Clover will set them at shutdown to be applied on the next reboot, which would then be the second time your booting using Clover.--Further reports on this have indicated success after a credit card has been tied to appleID account through the appstore, or when a small $1 app is purchased.
     
    Credits: The testing, brainstorming and collaborating involved was an unprecedented (in recent history) effort by the entire community, with valued efforts by too many people to list, but a special thank you to ElNono and flux84 for putting the final pieces together, to Slice for Clover and dmazar for pushing and update so quickly! Great work everyone!!!


  17. Like
    eep357 got a reaction from Jeffrey.C in iCloud/Facetime/AppStore login errors   
    Fixing Login Errors For Apps That Connect To Apple's Servers


     

    These steps should fix 98% of login errors, but some specific exceptions still exist and are omitted to avoid unnecessary confusion. Since this is a FAQ and not a full manual on all things Ethernet, it's not feasible to detail every method mentioned here, but hopefully at least it will let you know where to go next. So always start here!:


     

    To sign into any of the Apple services/apps that require authentication through Apple run servers, there are a few conditions that must be met when first logging in. For apps such as iCloud, once logged in the first time you will stay logged in even after reboots and configuration changes until manually logged out, at which point to log back in the same conditions will again apply.


     

    1) Must have a working ethernet adapter that can at least show up as a possible network connection. It must also work, but you might be able to get away with mostly working if your lucky.







    You'll need a kext that supports your NIC to proceed.


     

    2) It must also show as "Built In".







    Three possible ways of doing this which are all different ways of achieving the same result.



    Easy way, add following to Chameleon's org.chameleon.Boot.plist in /Extra folder:





    <key>EthernetBuiltIn</key>
    <string>Yes</string>

     

    Medium way, add EFI string to Chameleon's org.chameleon.Boot.plist in /Extra folder using tool such as "EFI Studio"


     

    Hard way, edit DSDT to have NIC device, i.e. LAN0 show as internal


     

    3) It needs to be listed as en0. i.e. The first, or primary, network device recognized by OSX






    Issue here will usually be that your wifi got enabled first and thus became en0, making your ethernet en1. To correct the issue: First if your wifi device or whatever is currently listed as en0 can be removed/unplugged from your PC by removing 3 screws or less, and you own a screwdriver, remove/unplug it. Next go to System Preferences > Network (as seen above in #1) and click the minus button to remove all the listed network devices, then reboot. Upon reboot return to System Preferences > Network and hit the plus button, add only your ethernet, open System Information (as pictured directly above) and verify Ethernet is now en0, if it is you can add your other devices now too.



    If ethernet is still showing as en1, you should then repeat the above steps, but this time just prior to reboot navigate to /Library/Preferences/SystemConfiguration/ and delete Networkinterfaces.plist and reboot.


     

    Extreeme cases only:



    If failure is still an option, and overkill seems necessary, it's possible to manually edit this plist. Again repeat initial steps, then copy plist to your desktop so it will be writable and open it with a text editor, cut an paste your ethernet so it appears first in the list, change every occurrence in it's section of en1 to en0, and vice versa for your prior en0 device, changing all it's en0 occurrences' to en1. Also verify here that ethernet shows:




    <key>IOBuiltin</key>
    <true/>



    and not




    <key>IOBuiltin</key>
    <false/>



    Once your satisfied with your edits (in simpler terms, your basically just swapping the two interfaces in the plist), launch Terminal from Applications/Utilities, enable root user by typing sudo -s and hitting enter, then entering your password when requested. Next enter the following, hitting return after each line:



    cp -R ~/Desktop/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/


    chown root:wheel /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    chmod 644 /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    reboot

     

    4) You need to have a SMBIOS which includes a valid serial number for the Mac model listed.







    For this, just use
    Chameleon Wizard to generate one for you and save to /Extra folder.

     
     

    WHEN ALL ELSE FAILS, BUT IS ALSO RIGHT, AKA-LAST RESORT:


     

    If you've met all the above requirements and ethernet works perfectly to browse the webs, but still can't log into these services, although it shouldn't need to be done manually, you may need to....


     

    First Open IORegistryExplorer (found in Xcode tools)






    Copy to Text Edit then get your ethernet MAC address






    Add results to org.chameleon.Boot.plist and after reboot you should see something like this



     
    And hopefully that will be it. Again, this won't cover every last possibility, but should be more than a good start.
  18. Like
    eep357 got a reaction from Jeffrey.C in iCloud/Facetime/AppStore login errors   
    Fixing Login Errors For Apps That Connect To Apple's Servers


     

    These steps should fix 98% of login errors, but some specific exceptions still exist and are omitted to avoid unnecessary confusion. Since this is a FAQ and not a full manual on all things Ethernet, it's not feasible to detail every method mentioned here, but hopefully at least it will let you know where to go next. So always start here!:


     

    To sign into any of the Apple services/apps that require authentication through Apple run servers, there are a few conditions that must be met when first logging in. For apps such as iCloud, once logged in the first time you will stay logged in even after reboots and configuration changes until manually logged out, at which point to log back in the same conditions will again apply.


     

    1) Must have a working ethernet adapter that can at least show up as a possible network connection. It must also work, but you might be able to get away with mostly working if your lucky.







    You'll need a kext that supports your NIC to proceed.


     

    2) It must also show as "Built In".







    Three possible ways of doing this which are all different ways of achieving the same result.



    Easy way, add following to Chameleon's org.chameleon.Boot.plist in /Extra folder:





    <key>EthernetBuiltIn</key>
    <string>Yes</string>

     

    Medium way, add EFI string to Chameleon's org.chameleon.Boot.plist in /Extra folder using tool such as "EFI Studio"


     

    Hard way, edit DSDT to have NIC device, i.e. LAN0 show as internal


     

    3) It needs to be listed as en0. i.e. The first, or primary, network device recognized by OSX






    Issue here will usually be that your wifi got enabled first and thus became en0, making your ethernet en1. To correct the issue: First if your wifi device or whatever is currently listed as en0 can be removed/unplugged from your PC by removing 3 screws or less, and you own a screwdriver, remove/unplug it. Next go to System Preferences > Network (as seen above in #1) and click the minus button to remove all the listed network devices, then reboot. Upon reboot return to System Preferences > Network and hit the plus button, add only your ethernet, open System Information (as pictured directly above) and verify Ethernet is now en0, if it is you can add your other devices now too.



    If ethernet is still showing as en1, you should then repeat the above steps, but this time just prior to reboot navigate to /Library/Preferences/SystemConfiguration/ and delete Networkinterfaces.plist and reboot.


     

    Extreeme cases only:



    If failure is still an option, and overkill seems necessary, it's possible to manually edit this plist. Again repeat initial steps, then copy plist to your desktop so it will be writable and open it with a text editor, cut an paste your ethernet so it appears first in the list, change every occurrence in it's section of en1 to en0, and vice versa for your prior en0 device, changing all it's en0 occurrences' to en1. Also verify here that ethernet shows:




    <key>IOBuiltin</key>
    <true/>



    and not




    <key>IOBuiltin</key>
    <false/>



    Once your satisfied with your edits (in simpler terms, your basically just swapping the two interfaces in the plist), launch Terminal from Applications/Utilities, enable root user by typing sudo -s and hitting enter, then entering your password when requested. Next enter the following, hitting return after each line:



    cp -R ~/Desktop/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/


    chown root:wheel /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    chmod 644 /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    reboot

     

    4) You need to have a SMBIOS which includes a valid serial number for the Mac model listed.







    For this, just use
    Chameleon Wizard to generate one for you and save to /Extra folder.

     
     

    WHEN ALL ELSE FAILS, BUT IS ALSO RIGHT, AKA-LAST RESORT:


     

    If you've met all the above requirements and ethernet works perfectly to browse the webs, but still can't log into these services, although it shouldn't need to be done manually, you may need to....


     

    First Open IORegistryExplorer (found in Xcode tools)






    Copy to Text Edit then get your ethernet MAC address






    Add results to org.chameleon.Boot.plist and after reboot you should see something like this



     
    And hopefully that will be it. Again, this won't cover every last possibility, but should be more than a good start.
  19. Like
    eep357 got a reaction from Jeffrey.C in iCloud/Facetime/AppStore login errors   
    Fixing Login Errors For Apps That Connect To Apple's Servers


     

    These steps should fix 98% of login errors, but some specific exceptions still exist and are omitted to avoid unnecessary confusion. Since this is a FAQ and not a full manual on all things Ethernet, it's not feasible to detail every method mentioned here, but hopefully at least it will let you know where to go next. So always start here!:


     

    To sign into any of the Apple services/apps that require authentication through Apple run servers, there are a few conditions that must be met when first logging in. For apps such as iCloud, once logged in the first time you will stay logged in even after reboots and configuration changes until manually logged out, at which point to log back in the same conditions will again apply.


     

    1) Must have a working ethernet adapter that can at least show up as a possible network connection. It must also work, but you might be able to get away with mostly working if your lucky.







    You'll need a kext that supports your NIC to proceed.


     

    2) It must also show as "Built In".







    Three possible ways of doing this which are all different ways of achieving the same result.



    Easy way, add following to Chameleon's org.chameleon.Boot.plist in /Extra folder:





    <key>EthernetBuiltIn</key>
    <string>Yes</string>

     

    Medium way, add EFI string to Chameleon's org.chameleon.Boot.plist in /Extra folder using tool such as "EFI Studio"


     

    Hard way, edit DSDT to have NIC device, i.e. LAN0 show as internal


     

    3) It needs to be listed as en0. i.e. The first, or primary, network device recognized by OSX






    Issue here will usually be that your wifi got enabled first and thus became en0, making your ethernet en1. To correct the issue: First if your wifi device or whatever is currently listed as en0 can be removed/unplugged from your PC by removing 3 screws or less, and you own a screwdriver, remove/unplug it. Next go to System Preferences > Network (as seen above in #1) and click the minus button to remove all the listed network devices, then reboot. Upon reboot return to System Preferences > Network and hit the plus button, add only your ethernet, open System Information (as pictured directly above) and verify Ethernet is now en0, if it is you can add your other devices now too.



    If ethernet is still showing as en1, you should then repeat the above steps, but this time just prior to reboot navigate to /Library/Preferences/SystemConfiguration/ and delete Networkinterfaces.plist and reboot.


     

    Extreeme cases only:



    If failure is still an option, and overkill seems necessary, it's possible to manually edit this plist. Again repeat initial steps, then copy plist to your desktop so it will be writable and open it with a text editor, cut an paste your ethernet so it appears first in the list, change every occurrence in it's section of en1 to en0, and vice versa for your prior en0 device, changing all it's en0 occurrences' to en1. Also verify here that ethernet shows:




    <key>IOBuiltin</key>
    <true/>



    and not




    <key>IOBuiltin</key>
    <false/>



    Once your satisfied with your edits (in simpler terms, your basically just swapping the two interfaces in the plist), launch Terminal from Applications/Utilities, enable root user by typing sudo -s and hitting enter, then entering your password when requested. Next enter the following, hitting return after each line:



    cp -R ~/Desktop/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/


    chown root:wheel /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    chmod 644 /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist


    reboot

     

    4) You need to have a SMBIOS which includes a valid serial number for the Mac model listed.







    For this, just use
    Chameleon Wizard to generate one for you and save to /Extra folder.

     
     

    WHEN ALL ELSE FAILS, BUT IS ALSO RIGHT, AKA-LAST RESORT:


     

    If you've met all the above requirements and ethernet works perfectly to browse the webs, but still can't log into these services, although it shouldn't need to be done manually, you may need to....


     

    First Open IORegistryExplorer (found in Xcode tools)






    Copy to Text Edit then get your ethernet MAC address






    Add results to org.chameleon.Boot.plist and after reboot you should see something like this



     
    And hopefully that will be it. Again, this won't cover every last possibility, but should be more than a good start.
  20. Like
    eep357 reacted to blackosx in OS X 10.9 DP's builds   
    They've finally fixed the window list view in Finder. The columns now resize to show the complete filename (within reason) (or rather, the set column widths are now remembered) and not stay at a fixed width forcing me to manually resize the column. A small but important change (for me).
  21. Like
    eep357 reacted to TH3L4UGH1NGM4N in OS X 10.9 DP's builds   
    Running 3 monitors here and when I restart I don't experience any issues with the screens playing with themselves and changing places.
     
    Also resuming the machine from sleep works for me rather quickly, no noticeable delays when waking from sleep.
  22. Like
    eep357 got a reaction from MNSiw in TP-Link WN727N (RT2870USBWirelessDriver.kext) Restart / Shutdown Problem   
    If everything except sound works otb, why install RT2870USBWirelessDriver.kext?  Anyway, after usual stuff like restart fix in boot loader or DSDT has been tried, check kext's dependancies, maybe need to roll back another kext like IOUSBFamily, etc.. If this is UHCI (USB 1.1) and all other devices are EHCI (USB 2.0) or 3.0, see if another USB 1.0 device that works otb can cause same problem. Process of elimination will eventually lead you to the cure.
  23. Like
    eep357 reacted to toleda in Crackling Sound With ALC 892 And SSE2   
    Pinarek did not mention that he posted the ML Alpha AppleHDA.kext.  For the current Realtek ALC892 AppleHDA.kext see Mountain Lion Realtek ALC AppleHDA Audio - OSx86 10.8 (Mountain Lion) - InsanelyMac Forum
    Platforms.xml/Pathmaps/Item 10/PathMapID: 892. What is different?
     
    Platforms.xml after the edits:
    A suggestion, credit the source of the kexts you attach.  Post #7 illustrates the problem of replying to a kext support question when you don't know the answer. 

  24. Like
    eep357 reacted to artur_pt in kext cache and gpu issue   
    hello
     
    run in teminal
     
    sudo kextcache -prelinked-kernel
     
    and see what is the problem
     
    good hack
  25. Like
    eep357 got a reaction from theconnactic in Chameleon stuck at boot0:done with HD 7770 (on 10.8.3)   
    It's due to larger vbios on 7xxx cards. It cause a bunch of alien looking text after Boot0:Done. Newest Chameleon helps for some, but for me the only way to get past this was to install Chameleon/Clover onto a mbr formatted drive instead of guid. I used a USB when first testing to get it working. Once you get past that, your next problem will be booting to a blank screen, the trick to get past this is to sleep and wake the computer. If you have automatic login enabled, disable it so you don't have to wait for all the desktop stuff to load before you can sleep and make screen work. Also make sure sleep works with your 5770 first so you know your system can sleep/wake. I had a 5770 I had to switch back to a few times while figuring all this stuff out
×