Jump to content


  • Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    angelol reacted to Dr. Hurt in [Guide] Mount and Access EFI partition on Windows 10   
    After upgrading to Windows 10, I realized that I could no longer access the mounted EFI partition even when explorer is running with admin privileges!!
    It took me some time to find a workaround so I thought I share it.
    1- Mount the EFI partition to a free mount point:
    -- Run command prompt as administrator
    -- Type "mountvol X: /s" (without the quotes, X being an unused mount point)
    2- Use Explorer++ (Free, Open Source app) to manipulate the files on the partition:
    -- https://explorerplusplus.com/
    -- Run Explorer++ with administrative privileges
    Hope you find this useful
  2. Like
    angelol reacted to malgkas in ATI to nVidia Graphic Problems   
    Hi Angelol,
    My GT740 worked without any fixes, however important was symbios used. On my Haswell PC with i5-4670K iMac 14.2 symbios worked but iMac 15.1 hanged on black screen every time.
    Unfortunately I've sold this card and can't check it for you. Now I'm using GTX 1050 Ti with iMac 15.1 symbios , but to make it working I need to use NvidiaGraphicsFixup.kext + Lilu.kext.
    You might try that. I'm guess yours GT740 is used in desktop PC so I think best symbios for i7-2600 would be iMac 12.1. Good luck.
  3. Like
    angelol reacted to fabiosun in ATI to nVidia Graphic Problems   
    Your gfx card should be supported by integrated mac os drivers
    if you use instead web driver (nvidiaweb=true in config) you could have need of patching applegraphics policy (it depends from SMBIOS used in config.plist)
    if SMBIOS needs of this patch you should have a black screen when login page comes
  4. Like
    angelol reacted to fantomas in ATI to nVidia Graphic Problems   
    If your nvidia graphics card has native support in osx, you even do not have to bother with web drivers. Uninstall web drivers and reboot w/o any nvidia related boot flag.
    If it does not work then check Inject Nvidia in config.plist and reboot again.
  5. Like
    angelol got a reaction from fabiosun in ATI to nVidia Graphic Problems   
    Hi mate. I'm sorry, I forgot to provide info. I'm using an iMac12.2 SMBIOS and 10.11.6.
  6. Like
    angelol got a reaction from J Lamp in Clover CustomIcon   
    In clover configurator,drag and drop your custom icon in your clover custom entry.Remove the word Volumes from the path and then change every / character to \
    Save and reboot.
  7. Like
    angelol reacted to 0000-1248 in Toshicba laptop i3 330m - No   
    Have you determined what display connector your computer uses? If it uses eDP, you're out of luck, but if you use LVDS, QE/CI can work. My Lenovo G560 uses the LVDS connector, so I get full resolution and Quartz Extreme support. You can find it out here.  Also be sure to try the kexts that they patched. I use these with my Lenovo and the Integrated GPU works fine (although, VGA out is patchy. They said it works great in clamshell mode, however).
    Hope I could help,
    - Matt
  8. Like
    angelol reacted to Say Heading in Clover hates Cinema Display   
    The time saving and also very effective solution to my problem was to buy a new display...
  9. Like
    angelol reacted to WaldMeister in OS X 10.11 question about rootless=0   
    These boot flags are obsolete. I use clover myself, and you need to set CSRActiveConfig to a value when kexts need to be loaded/injected. 
    <key>RtVariables</key> <dict> <key>CsrActiveConfig</key> <string>0x67</string> <key>ROM</key> <string>UseMacAddr1</string> </dict> 0x67 Disables al protection. To just enable unsigned kext loading, 0x03 will be enough (same as kext-dev-mode=1)
  10. Like
    angelol reacted to Renard45 in OS X 10.11 question about rootless=0   
    you don't need this boot flag anymore, there are others boot flags now like slide=0, for me for boot on El Capitan the only boot flag i have is slide=10.
  11. Like
    angelol reacted to alex.daoud in i2c-hid touchscreens, trackpads and more   
    VoodooI2C is a kext that brings support for I2C controlled input devices to OS X. For a list of compatible controllers and devices, see the github page: https://github.com/alexandred/VoodooI2C .
    Where we stand right now
    Haswell, Broadwell and Skylake are fully functional as controllers. On the device side, most (if not all) i2c-hid devices have basic functionality (sometimes with minor changes to the code). Various proprietary interfaces are also supported such as the ELAN I2C interface which brings native multitouch to a variety of ELAN trackpads and touchscreens.
    What will be supported?
    I envisage only 3 classes of i2c-hid support by code I have written. Touchscreens, touchpads and sensor hubs. Sensor hubs contain information from the accelerometer (and possibly the fingerprint reader if your device has one, based on my research). This will allow us to get screen rotation on tablets.
    Do you have a device with a touchscreen or trackpad that refuses to work no matter what drivers you throw it at? You might be a good candidate for this driver, simply post your DSDT, SSDTs and IOReg in this thread, along with your device's model number and OS X version and I will confirm if you will be able to use it or not.
    Technical Data
    Apple actually has drivers for the Intel LynxPoint LPSS I2C devices (as can be found in /System/Library/Extensions) but these are not compatible with our devices. Apple's drivers expect the interrupts to occur over GPIO whereas the ones found on our devices do not use this. Hence it cannot find the necessary pin data and that is why we get "probe fails" (also applies to SPI, UART etc).
    Source Code
    The source code can be found at http://www.github.com/alexandred/VoodooI2C . 
    I am in no way affiliated with the VoodooProject. VoodooI2C was an internal name as I couldn't think of what to name it. Suggestions?
  12. Like
    angelol reacted to arsradu in [HOW TO] Fix second stage boot logo and loading bar for some dedicated desktop video cards   
    You're welcome.
    If there's anything that's not clear enough or if you have any suggestions to make this tutorial clearer/better, please, don't hesitate to tell me and I'll see what I can do.
  13. Like
    angelol reacted to arsradu in [HOW TO] Fix second stage boot logo and loading bar for some dedicated desktop video cards   
    Hey guys,

    This is a tutorial on how to fix (or at least try to fix) the second stage boot, when you're having these issues: missing logo and loading bar being displayed on the bottom left corner of the screen.
    Might or might not work for other issues. So proceed with caution.

    This is an issue that I experienced starting with early stages of development in Yosemite. Still continued in El Capitan. So this thread is primarily for these two versions of Mac OS X. Not sure it will work on earlier versions, cause I never tried it. So far it worked in Yosemite, El Capitan and Sierra.

    Please, note that I did not test this on all video cards. So it might or might not work, depending on that. Don't take this as a final solution for everything. Also, I'm pretty sure this won't work with iGPUs. So I would strongly suggest to look around for solutions if that's your case.

    This tutorial is not for multiple display setups! Please, don't use it for that! Especially not in iGPU + dedicated GPU combos.
    Known issue: if you're using the auto-login feature, try to disable it and use the regular login screen. Otherwise you won't get the second stage boot (confirmed as fixed in Sierra).
    This tutorial would have not been possible without the help and insight of:
    Pike R. Alpha
    Riley Freeman
    So all the credit goes to them. I just put this together based on my successes and failures.

    Succesfully tested with:
    NVidia cards:
    GeForce 210 GT 640 GTX 650 GTX 660 GTX 670 Superclocked+ 4GB - works partially (ok for 1080p, with CSM disabled, but no second stage in higher resolutions) GTX 750 Ti - works partially (ok for 1080p, but no Apple logo for second stage in higher resolutions) GTX 760 GTX 780 GTX 960 GTX 970 - works partially (ok for 1080p, and 1440p with CSM disabled, but no second stage in higher resolutions) ATI cards:
    Sapphire Toxic R9 270X Might work on other graphic cards, as well. But these are the ones that worked so far. Please, share if you got good results with another video card.

    Also, the same thing can be achieved by modding your DSDT. Unfortunately this thread does not make the object of that method, nor am I able to help you with that, since I really have no idea how to mod a DSDT, so far. Also, to be honest, this method seems a bit easier.

    Nonetheless, try this at your own risk! I'm not responsible for any damage that you might cause to your computer/components etc.
    Also, please, note that this tutorial is not perfect. I'm doing my best to make it as easy to understand as possible. Also, I'm opened to suggestions and I'm doing my best to improve this in the future. Still, it's not perfect. So keep that in mind. Suggestions are appreciated though.

    Please, note that, if you've got a video card with GOP UEFI Bios, you most likely don't need this tutorial in the first place. All you need is to disable CSM in BIOS (motherboard dependent). Note that, by doing this, only GPT drives will be loaded. So if you've got Windows installed on another drive, for example, you won't be able to select it anymore, if it's installed in "legacy" mode.

    With that being said, let's get to work.


    a computer running Mac OS X Yosemite or newer Clover bootloader (changes are gonna be saved to the config.plist file) IORegistryExplorer v 2.1 (attached) gfxutil (attached) gfx_hex (attached) - script credit to cecekpawon Optional:
    Sublime Text Editor Clover Configurator a Windows PC for reading the graphic card's VBios version. So far, I couldn't find a way to do it from OS X. But if you know how to do it, please, share. I'll update this accordingly. An alternative (though not really the same thing) is this. an USB installer might come in handy, so keep one close by. Extra:
    If you want to try the modded Bootx64.efi (rev 3279), thanks to cecekpawon, featuring an option to easily enable/disable string injection in Clover (in case you're stuck outside your OS, and don't have a USB drive or something else to boot from), click here to get it. Please, note that this revision might not work with newer versions of OS X/macOS.
    You will need to replace the one in your EFI/EFI/CLOVER folder. If you want to revert to the previous one, you can either reinstall Clover, or make a backup of your current one before replacing it. I would recommend creating a single folder with all the necessary files and tools and putting it on your Desktop, just to have all the needed things in one place.

    Note: If you use a custom SSDT/DSDT, I would try first without it, and using Clover's patches instead, so that you minimize the risk for failure due to custom DSDTs. I don't use a custom DSDT, didn't test in collaboration with a custom DSDT, so I don't know if it will work. If you wanna try it this way, I would love to know your results.

    What to do:

    Step 1 (establishing the port):

    Open up your IOreg file (or just open IORegistryExplorer if you don't want to save it as a separate file), and search for "display".

    You should see something like this:

    Now, depending on your card, you might have more or less ports. The important thing is to note the one that has the AppleDisplay attached to it. In this example, the second port (B@1) is the one in use. So that's the one we need to set as default. Please, note that they start at 0, so first port is A@0, the second one is B@1 and so on so forth.

    Step 2 (extracting device-properties.hex):

    Open up a terminal window, navigate to the desktop folder you're using, and do this (make sure gfxutil is present into that folder):
    ioreg -lw0 -p IODeviceTree -n efi -r -x | grep device-properties | sed 's/.*<//;s/>.*//;' > "device-properties.hex" && ./gfxutil -s -n -i hex -o xml "device-properties.hex" "device-properties.xml" This will extract two new files into that folder: device-properties.hex and device-properties.xml

    Step 3 (modding the device-properties.xml):

    Open up the xml file using any text editor (I'm gonna use Sublime here) and ADD the number of ports you need for your card (the same number of ports, with the same name as in the IOreg) and the rest of the information, as described in the example below (use the attached xml as reference):

    Don't forget that the first port is port 0!

    In this example, we're using an MSi GTX 650 OC with 2GB of RAM, which has 3 ports, and we want to set as default port #2 (B@1).
    Attached you can find my device-properties.xml file, if you wanna use it as reference.

    The first section will set port B@1 as default. Change this according to your case.
    <!-- Primary display --> <key>@1,AAPL,boot-display</key> <string>0x00000001</string> Whereas on the bottom you can see regular values. Here we can set the amount of VRAM, the name of the card and the VBios version.
    <key>VRAM,totalMB</key> <string>0x00000800</string> // for 2048 MB or 2 GB of RAM <key>device_type</key> <string>NVDA,Parent</string> <key>model</key> <string>MSi GeForce GTX 650</string> // Name of your card <key>rom-revision</key> <string></string> //VBIOS version In my experience, these values are rather cosmetic than anything else. For an accurate version of your VBios, you can use either the Nvidia driver on Windows, or any hardware information software like GPU-Z, aida64 or nvflash.
    Here's a little table with hex values for different amounts of RAM. If you need other values than the ones specified in this table, please, ask. Also, if you spot a mistake, let me know so I can correct it.
    Amount of memory  Hex value
    128 MB                      0x00000080
    256 MB                      0x00000100
    512 MB                      0x00000200
    1024 MB (1 GB)        0x00000400
    2048 MB (2 GB)        0x00000800
    3072 MB (3 GB)        0x00000C00
    4096 MB (4 GB)        0x00001000
    5120 MB (5 GB)        0x00001400
    6144 MB (6 GB)        0x00001800
    7168 MB (7 GB)        0x00001C00
    8192 MB (8 GB)        0x00002000
    9216 MB (9 GB)        0x00002400
    10240 MB (10 GB)    0x00002800
    11264 MB (11 GB)    0x00002C00
    12288 MB (12 GB)    0x00003000
    13312 MB (13 GB)    0x00003400
    14336 MB (14 GB)    0x00003800
    15360 MB (15 GB)    0x00003C00
    16384 MB (16 GB)    0x00004000
    Once we're done modding, we're gonna save the changes and convert the xml file back into hex, using this command:
    ./gfxutil -i xml -o hex device-properties.xml device-properties.hex Step 4 (reading the modded hex):

    Unpack gfx_hex (attached) file into your working directory and double click to run it.
    It should output the content of your modded hex into a terminal window, and it should look something like this:

    Select and copy that code. After that, open up Clover Configurator and paste that hex code in Devices -> Properties section (see below) and check the box for Inject. You can also add this manually into the config.plist file, if that's more of your thing.

    Step 5 (setting up final arrangements):

    We're almost done. But, if your experience is the same as mine, at this point you only got the loading bar back centered. Which, of course is a step forward. But we're not quite there yet.

    So, to add the logo as well, we will check the boxes for Patch VBios and Inject EDID in Clover Configurator (Graphics section). You can inject your own EDID if you have one. Though, in my experience, Clover does a really good job in adding the correct one itself. So you don't really need to add a custom EDID. Just to use Clover's InjectEDID feature.

    Also, in my experience, you don't need CsmVideoDrv.efi for this to work. And I've got pretty similar results with and without it. So, if you have issues with it, you can try without it, and vice-versa.

    When it's all done, save the changes to your config.

    Now, I would highly recommend you to make a backup of your current config.plist from EFI/EFI/Clover/config.plist anywhere you want. You might need it later.

    When that's done too, replace the config.plist in your Clover folder with the one you just modded, and restart.

    Keep your fingers crossed (toes too). And hope for the best. If everything ok, you should have a pretty close to perfect second stage boot. If not, you might have nothing or an unbootable system.

    To fix this, boot from your USB installer, or use boot flag nv_disable=1 (for Nvidia cards), upon booting, and revert the changes. Or, if you already know where is the problem, fix that and restart.

    That's it.

    Please, let me know if it worked for you.
  14. Like
    angelol got a reaction from Andy Vandijck in AMD APU Graphics Accelerator creation info   
    You made my day mate!!! God bless you and congratulations for such a great deal of work!!!
  15. Like
    angelol reacted to Andy Vandijck in AMD APU Graphics Accelerator creation info   
    Yes, we could make kexts for any graphics cards....
    If somebody would be willing to use the info and tools posted above it is definitely possible...
  16. Like
    angelol reacted to fantomas in Best Wishes 2015!   
    Best Wishes 2015 to our great community! :thumbsup_anim:
    Click here to view the article
  17. Like
    angelol reacted to Alien::X in Pattern of MLB (Main Logic Board)   
    MLB Cloner V4
    This tool is only clone MLB
    Not Create real (White Listed) MLB
    New :This tool is more specific with Model...
             Its also extract Production week number from Serial...
  18. Like
    angelol reacted to pac-man in Pattern of MLB (Main Logic Board)   
    Just a suggestion, can you please try following:
    You should then see a section called "Base Board Information" and in this section you will find an entry called "Serial Number" which is your MLB (Main Board Serial Number).
  19. Like
    angelol reacted to Vlada. in [HOW TO] Modification of AMD FB + Clover injection   
    Mostly because of my partly success in making proper patch for all Radeon R9 270 Series GPU-s described in Radeon R9 270X FrameBuffer issue topic, but also because I see that many of you are still searching for some sort of help, I was coming to an idea to share some of my conclusions via this tutorial, in hope that it will resolve all of your current troubles. Once when you check this tutorial and you use it, you will understand better where is the problem and eventually, after you determinate what is what you will be able to fix it. It is important to say, that this tutorial is universal and it can be used for any AMD GPU.
    So lets start… 
    Modifying the AMD driver is one of the advanced hacker's technique, however, recently with clover in combination, the whole process can be reduced to a decent minimum. This tutorial aims to discover what specific digits in the code do and basically to educate so that everyone can make necessary modification alone and w/o further assistant. All you need is a bit of good will and some patience.
    Extracting ROM file - Step 1 involves extraction of the original ROM file from your graphics card. This could be done from Windows by applications such as GPU-Z or some other similar, or from Mac OS X via DPCIManager application. Extracted ROM file you’ll need to save and then switch again in your Mac OS X.
    Finding proper FB - Step 2 involves finding proper frame buffer that can be used by your GPU. In order to do this properly, we will need a terminal and corresponding ATI FrameBuffers script. We need this one to extract FB code inside AMDXXXXControllers.kexts. 
    Download ATI FrameBuffers php scripts by Pavo. Unpack the zip file on the desktop, then switch to terminal. Type php then simply drag the script in the terminal and press enter.
    What you’ll get is a long series of codes together with the exact names of the frame buffers inside certain AMD Controller kexts.
    Although by using this patching method we can modified any FB, it is recommended that you find the proper one for your GPU, which might already work with your card. The point with this is to locate those that contain the same number of connectors, so per example:   My GPU has 4 connectors: 2xDVI, 1xHDMI and 1xDP  -  so this means that I need to use FB with 4 connectors.   In the AMD personality dump file, just under the first line with FB name, we can find info that we need.   Personality: Futomaki ConnectorInfo count in decimal: 4   So this means that I should check those FB-s first.    Copy the code from the terminal in the Text Editor and save it on the desktop. Then take a look carefully extracted code, and write all frame buffers from the AMD Controller kext that drives your video card. For example, Radeon R9 270X that I’m using, is driven by AMD7000Controller.kext which containing the following list of frame buffers: MaguroS, Maguro, KaniS, Kani, Junsai, IkuraS, Ikura, OPM, Hamachi, Futomaki, Gari, Ebi, Dashimaki, Chutoro, Buri, Aji. For Radeon 6850HD it is necessary to look at the list of FB extracted from AMD6000Controller.kext, etc. ...
    Now that you have the names of FB-s you will need to determine which of them your card can use. The simplest way of doing this is Clover, although it is possible to do the same thing with Chameleon boot loader, but I'll be focusing exclusively this time on Clover.
    So open Clover Configurator and in the Graphics section of the FB Name field, type the first FB from your list. Then restart computer and reboot again in OS X. If all goes well, your graphics will work immediately (with or without GL quartz enabled), however, there are two more situations that may occur.
    First one is a situation where you will get a black screen, but the monitor will stays on. This also means that assigned FB works, but the connectors code inside dedicated AMD Controller kext is mismatched. In this situation pressing the ALT+CMD+Eject buttons on Apple keyboards and WIN+ALT+F12 on PC keyboards will simply sleep your computer. After waking from sleep your computer will activate the screen again. Basically, this is the one of the most common situation which requires further patching.
    In all other situations, most likely your monitor will automatically be switched off. This means that the assigned FB does not work, or another word that is not compatible with your GPU. In this situation my recommendation would be that you simply restart your computer. The best way to do that is to implement the software restart by pressing CTRL+CMD+Eject buttons on Apple keyboards or for PC keyboards that would be CRTL+ALT+F12, after which the computer will just restart immediately.
    By modifying Clover Boot options from its menu, where you can rename assigned FB or simply remove all enabled Graphics options that you are previously assigned, you will be able to re-boot OS X normally again. Basically, this is the part that will certainly take you some time before you discover which FB best suits to your card, but when you do this, you're ready for the next step.
    FB Code Construction - Step 3 is the most important and involves modifying the original driver or more precisely, it considers changing hexadecimal values inside the driver that are defining the connector output signal from your graphic card.
    For this maneuver we will need correct values extracted from the existing ROM file, and that can be done through the two scripts: radeon_bios_decode  and redsock_bios_decoder scripts. It is necessary to use both because they are giving different results. Basically only with both results we can collect all the necessary data that we need.
    Scripts can be used in a similar way. You’ll need to open the terminal, drag the first script in a terminal then press once space, than type  <  than once space again and now drag your ROM file in the terminal and simply hit Enter. The obtained result will look something like this (example R9 270X)
    localhost:~ Vladimir$ /Users/Vladimir/Developer/Ati\ Workbench/AMD\ Graphics\ tool/Radeon\ BIOS\ decoders/radeon_bios_decode < /Users/Vladimir/Developer/Ati\ Workbench/AMD\ Graphics\ tool/AMD\ BIOS/Pitcairn.rom
    radeon_bios_decode will give the following result:

    ATOM BIOS Rom:   SubsystemVendorID: 0x148c SubsystemID: 0x2336   IOBaseAddress: 0x0000   Filename: E8B11LCC.HHW   BIOS Bootup Message: C63101 CURACAO XT 2GB GDDR5 64Mx32 E8B11LCC.HHW 2013 PCI ID 1002: 6810 Connector at index 0   Type [offset 43522]: DisplayPort (10)   Encoder [offset 43526]: INTERNAL_UNIPHY2 (0x21)   i2cid [offset 43632]: 0x90, OSX senseid: 0x1 Connector at index 1   Type [offset 43532]: HDMI-A (11)   Encoder [offset 43536]: INTERNAL_UNIPHY2 (0x21)   i2cid [offset 43659]: 0x92, OSX senseid: 0x3 Connector at index 2   Type [offset 43542]: DVI-I (2)   Encoder [offset 43546]: INTERNAL_UNIPHY (0x1e)   i2cid [offset 43696]: 0x95, OSX senseid: 0x6 Connector at index 3   Type [offset 43552]: DVI-I (2)   Encoder [offset 43556]: INTERNAL_KLDSCP_DAC1 (0x15)   i2cid [offset 43696]: 0x95, OSX senseid: 0x6 Connector at index 4   Type [offset 43562]: DVI-D (3)   Encoder [offset 43566]: INTERNAL_UNIPHY1 (0x20)   i2cid [offset 43723]: 0x94, OSX senseid: 0x5 redsock_bios_decoder will give the following result:
    E8B11LCC.HHW: C63101 CURACAO XT 2GB GDDR5 64Mx32 E8B11LCC.HHW 2013 Subsystem Vendor ID: 148c   Subsystem ID: 2336 Object Header Structure Size: 355 Connector Object Table Offset: 48 Router Table Object Offset: 0 Encoder Object Table Offset: fd Display Path Table Offset: 12 Connector Object Id [19] which is [DISPLAY_PORT]   encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x12 [duallink 0x2] enc 0x4)] linkb: false Connector Object Id [12] which is [HDMI_TYPE_A]   encoder obj id [0x21] which is [INTERNAL_UNIPHY2 (osx txmit 0x22 [duallink 0x2] enc 0x5)] linkb: true Connector Object Id [2] which is [DVI_I]   encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false Connector Object Id [2] which is [DVI_I]   encoder obj id [0x15] which is [INTERNAL_KLDSCP_DAC1 (osx txmit 0x00 0x10 enc)] linkb: false Connector Object Id [4] which is [DVI_D]   encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Copy and paste the results into Text Editor and save it. Then extract the following items from both results like in this example by following the color order:
    01 [DISPLAY_PORT] 
    redsock_bios_decoder :
    enc obj 0x21 transmitter 0x12 dual link 0x2 enc 0x4
    Connector at index 0
    Type [@offset 43522]: DisplayPort (10)
    Encoder [@offset 43526]: INTERNAL_UNIPHY2 (0x21) 
    i2cid [@offset 43632]: 0x90, OSX senseid: 0x1
    Code construction: 12 04 01 01
    02 [HDMI_TYPE_A] 
    redsock_bios_decoder :
    enc obj 0x21 transmitter 0x22 dual link 0x2 enc 0x5
    Connector at index 1
    Type [@offset 43532]: HDMI-A (11)
    Encoder [@offset 43536]: INTERNAL_UNIPHY2 (0x21)
    i2cid [@offset 43659]: 0x92, OSX senseid: 0x3
    Code construction: 22 05 02 03
    03 [DVI_I] 
    redsock_bios_decoder :
    enc obj 0x1e transmitter 0x10 dual link 0x0 enc 0x0
    Connector at index 2
    Type [@offset 43542]: DVI-I (2)
    Encoder [@offset 43546]: INTERNAL_UNIPHY (0x1e)
    i2cid [@offset 43696]: 0x95, OSX senseid: 0x6
    Code construction: 10 00 03 06
    04 [DVI_I] 
    redsock_bios_decoder :
    enc obj 0x15 transmitter 0x00 enc 0x10
    Connector at index 3
    Type [@offset 43552]: DVI-I (2)
    Encoder [@offset 43556]: INTERNAL_KLDSCP_DAC1 (0x15)
    i2cid [@offset 43696]: 0x95, OSX senseid: 0x6
    Code construction: 00 10 04 06
    05 [DVI_D] 
    redsock_bios_decoder :
    enc obj 0x20 transmitter 0x11 dual link 0x1 enc 0x2
    Connector at index 4
    Type [@offset 43562]: DVI-D (3)
    Encoder [@offset 43566]: INTERNAL_UNIPHY1 (0x20)
    i2cid [@offset 43723]: 0x94, OSX senseid: 0x5
    Code construction: 11 02 05 05
    Now let's look at the original source code extracted from the original driver for the FB Futomaki that activates R9 270X:
    Personality: Futomaki 10.9.2
    ConnectorInfo count in decimal: 4
    Disk offset in decimal 811280
    00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01
    00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02
    04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06
    00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03
    Each row represents definition for the one connector. In this case we have 4 of them.
    In order to better understand what is what I will separate first line from the code as an example:
    00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01
    Divided into segments:
    00 04 00 00 / Connector type
    04 03 00 00 / ATY, ControlFlags
    00 01 01 01 / Features
    12 / Transmitter
    04 / Encoder
    04 / hotplug ID
    01 / Sense ID
    What this means?
    First I’ll put the list of all types of connectors:
    Connector Type LVDS 0 × 00000002 = 02 00 00 00 Note: Laptop Monitor
    Connector Type DVIDL 0 × 00000004 = 04 00 00 00 Note: Dual Link DVI
    Connector Type VGA 0 × 00000010 = 10 00 00 00
    Connector Type SV 0 × 00000080 = 08 00 00 00
    Connector Type DP = 0 × 00000400 00 04 00 00
    Connector Type HDMI 0 × 00000800 = 00 08 00 00
    Connector Type DVISL 0 × 00000200 = 00 02 00 00 Note: Single Link DVI
    So now it's clear that first 4 pair of numbers represents the type of connector in the code:
    00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 / Display Port
    00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02 / Display Port
    04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06 / DVI-D
    00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03 / HDMI
    Constructed FB is made this way, mostly due to the fact that Apple monitors are using DP as the primary connection and then we have beneath in order all others.
    In the vast majority of cases there, you will need to change only the last 4 digits, which are also the most important for proper connector injection, or eventually you will need to assign further a DVI-I (SL) connection for your monitor. In this case, it is basically a mandatory thing mostly because the original code does not have it. Therefore, we will need to change the second row from DP into DVI-SL.  The initial input of first four pairs of digits we will need to change from 00 04 00 00 to 00 02 00 00, which is the proper input for DVI-SL.
    00 02 00 00
    Then follows the explanation of the second set of digits:
    0×0002 : LVDS               ControlFlag : 0×0040 and 0×0100
    0×0004 : DVI                  ControlFlag : 0×0016, 0×0014, and 0×214
    0×0010 : VGA                ControlFlag : 0×0010
    0×0080 : S-Video           ControlFlag : 0×0002
    0×0200 : DVI                  ControlFlag : 0×0014, 0×0214, and 0×0204
    0×0400 : DisplayPort     ControlFlag : 0×0100, 0×0104, 0×0304, 0×0604, and 0×0400
    0×0800 : HDMI               ControlFlag : 0×0200 
    0×1000 : DVI                   ControlFlag : 0×0016
    Translated in to:
    Connector Type DP 04 03 00 00
    Connector Type DP 04 03 00 00
    Connector Type HDMI 00 02 00 00
    Connector Type DVIDL 14 02 00 00
    Connector Type_DVISL C 04 02 00 00
    Connector Type_DVISL 04 02 00 00
    From this example it is clear that in the modified row we should add further 04 02 00 00 according to the matched connector name. So after first 00 02 00 00 we will need to add the following 4 pair of digits 04 02 00 00 and all together it looks like this:
    00 02 00 00 04 02 00 00
    The following is the part that relates to the ATY,Features (hex digits):
    The first pair of numbers:
    0 × 0002: LVDS * 0x09 = 09
    0 × 0004: DVI 0x00 = 00
    0 × 0010: VGA 0x00 = 00
    0 × 0080: S-Video 0x04 = 04
    0 × 0200: DVI 0x00 = 00
    0 × 0400: Display Port 0 × 00 = 00
    0 × 0800: HDMI 0 × 00 = 00
    0 × 1000: DVI 0x00 = 00
    The second pair of numbers:
    Use Internal * 0 × 01 = 01
    Use RGB YUV On 0 × 04 = 04
    Use Backlight * 0 × 08 = 08
    Backlight Inverted 0 × 10 = 10
    Use Clamshell 0 × 20 = 20
    A third pair of numbers represents the order of connector activation
    01 = first active connector
    02 = second active connector
    03 = third active connector
    etc. ...
    I suggest that you mark as first, connector raw that your monitor will use it as primary. 
    The fourth two numbers are listed as Unknown:
    You can leave the same like in the original code (usually stands 01 or 00) or simply replace it with zeros - 00. I will in this demonstration left the original values:
    Finally, we add the following digits:
    00 02 00 00 04 02 00 00 00 01 01 01
    Last four digits simply rewrite from the above constructed table:
    03 [DVI_I] 
    redsock_bios_decoder :
    enc obj 0x1e transmitter 0x10 dual link 0x0 enc 0x0
    Connector at index 2
    Type [@offset 43542]: DVI-I (2)
    Encoder [@offset 43546]: INTERNAL_UNIPHY (0x1e)
    i2cid [@offset 43696]: 0x95, OSX senseid: 0x6
    Code construction: 10 00 03 06
    I will explain in short, what is what here, but that would not be important much anyway. The only one thing important it is the order of digits that we need to use and the patch will work. So here it is:
    Transmitter - the first two digits
    Encoder - the second two digits
    Hotplug ID - third two digits
    Sense ID - Fourth two digits
    So that was detail explanation, however, we can simplify this procedure by using next basic code schematics per connector:
    LVDS / 02000000 40000000 08010000 / + (add your code construction)
    VGA / 10000000 10000000 00010000 / + (add your code construction)
    DP / 00040000 04030000 00010000 / + (add your code construction)
    DVI-SL / 00020000 04020000 00010000 /  + (add your code construction)
    DVI-DL / 04000000 14020000 00010000 /  + (add your code construction)
    HDMI / 00080000 00020000 00010000 / + (add your code construction)
    As you can see, all you have to do is to add the last 8 digits which you need to construct by yourself (see example above)
    Sierra is using additional digits in the code, so you'll need to add extra zero segments in front of your code construction and after it. Check example bellow:
    00080000 00020000 00010000 00000000 + (add your code construction) 00000000
    So this is it, and here we have final construction.
    00 02 00 00 04 02 00 00 00 01 01 01 10 00 03 06
    Except for the above modification, like I said, in most cases you will need to replace only the last four values:
    Original code:
    00 04 00 00 04 03 00 00 00 01 01 01 12 04 04 01 - DP
    00 04 00 00 04 03 00 00 00 01 02 01 22 05 05 02 - DP
    04 00 00 00 14 02 00 00 00 01 03 00 00 00 06 06 - DVI-DL
    00 08 00 00 04 02 00 00 00 01 04 00 11 02 01 03 - HDMI
    Modified code:
    00 04 00 00 04 03 00 00 00 01 02 01 12 04 01 01 - DP
    00 02 00 00 04 02 00 00 00 01 01 01 10 00 03 06 - DVI-I
    04 00 00 00 14 02 00 00 00 01 03 00 11 02 05 05 - DVI-D
    00 08 00 00 00 02 00 00 00 01 04 00 22 05 02 03 - HDMI
    With this, the whole thing is completed and you are now ready for the final step.
    Clover Injection - Step 4 involves injection of the code and its activation.
    This can be done in several ways: kext patching by some hex tool or making the Binary patch, however, none of these methods are sufficiently elegant, mostly because in this case we will need to patch driver every time when we make system upgrade.
    Luckily we have a Clover, which is able to apply such modification "on the fly" which is ideal concept, or other words, this method represents a permanent solution that does not depend from the future system upgrades.
    Open Clover Configurator, and go to the Kernel & Kext patches. Click on the plus sign in the KextsToPatch field :

    Then type the name of the kext you want to patch, in this case this is AMD7000Controller. In the next field, enter the original hex code extracted from the driver, and next to it write a new one that you have created. Eventually, you can add notes in the next field (par example: Connectors patch) and that was it. You are ready for testing.

    If you are all done properly everything will work from the first attempt. If not you will need to work further on it. But if something goes wrong, you can always change the name of the FB or simply to uncheck the options that you have activated in the Graphics panel and thus everything will be back to its initial state.
  20. Like
    angelol reacted to Allan in How To Install The Official Spotify App in Ubuntu   
    Now Spotify upgrade for a new version:

    Very Beautiful!!
  21. Like
    angelol reacted to Allan in How To Install The Official Spotify App in Ubuntu   
    If you want to hear several songs without having to be worry about illegal downloads.
    I recommend this app. 
    Spotify is the king of music streaming. Every day tens of millions of users listen to thousands of tracks using it through a variety of different ways.
    How to Install Spotify in Ubuntu
    Spotify for Linux can be installed on Ubuntu 12.04, 12.10 and 14.04 LTS straight from the Spotify repository. This method is the recommended way to install the player as it allows you to get automatic upgrades to new releases of Spotify through Ubuntu’s Software Updater/Update Manager tool.
    The first step is to open Software Sources via the Unity Dash:

    Select the ‘Other Software’ tab in Software Sources [1]

    Click ‘Add’ [2] and paste the following the entry field of the box that appears:
    deb http://repository.spotify.com stable non-free
    Click ‘Add Source’ to confirm the change, then close Software Sources.
    Add The Spotify Repository Key
    The next step is to add the repository key. This allows Ubuntu to verify that packages installed from the repository are made by who they say they are.
    Open a new Terminal window, paste the following command, and then hit return/enter:
    sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 94558F59
    That’s that! You can now install Spotify through the Ubuntu Software Center (after checking for software updates first) or by running the following command in the Terminal window:
    sudo apt-get update && sudo apt-get install spotify-client Once installed you can launch Spotify from the Unity Dash.
     Have Fun!! 
    Credits: OMG Ubuntu
  22. Like
    angelol got a reaction from jbuttonfan in No HDMI Sound through HD Radeon 6770   
    I'm really happy you got it to work with my DSDT. But at the same time,I can't even remotely think of a reason the SMBIOS was causing troubles. 
  23. Like
    angelol got a reaction from verleihnix in ATI Radeon HD 5000 instead of ATI Radeon HD 6770   
    Hello guys, been a while since my last post in here.
    I came up with a thought while trying to make my HDMI port on my MSI 6770 1gb while at the same keeping ATI Radeon HD 6770 1024 MB in the about this mac window.
    Skip to the end if you are in a hurry
    I found that if I inject my "@0-2" framebuffer names as "Hoolock" in my DSDT per Rampagedev's instruction in http://www.insanelymac.com/forum/topic/282687-radeon-hd-6770-full-qeci-mlmavericksyosemite/page-2?do=findComment&comment=1902721, my card was recognised as 6770 and VGA and DVI worked, but the HDMI didn't.
    If, on the other hand I, don't fiddle with them in my DSDT, DVI and HDMI works(video only) (i really forgot to test VGA at that point) but in ioreg, the chosen framebuffer would be "ATI_Framebuffer" or something like that.
    At the same time, in "About this Mac" the card was recognised as  ATI Radeon HD 5000 1024 MB.

    Hold my (that) though.

    After bumping in this and this tutorials, again by Rampagedev, whom I respect for this guy is tremendously btw, I noticed that Hoolock that it has wrong port types. In detail:
    Personality: Hoolock ConnectorInfo count in decimal: 3 Disk offset in decimal 166176 0000000 00 04 00 00 04 06 00 00 00 01 00 00 21 03 05 01 // 0x400 means Display Port 0000010 00 04 00 00 04 06 00 00 00 01 00 00 11 02 04 02 // 0x400 means Display Port 0000020 04 00 00 00 14 02 00 00 00 01 00 00 02 04 01 03 // 0x4 means DVI-Dual Link port 0000030 Connector Type LVDS 0x00000002 = 02 00 00 00 Note: Laptop Monitor Connector Type DVIDL 0x00000004 = 04 00 00 00 Note: Dual Link DVI Connector Type VGA 0x00000010 = 10 00 00 00 Connector Type S-V 0x00000080 = 08 00 00 00 Connector Type DP 0x00000400 = 00 04 00 00 Connector Type HDMI 0x00000800 = 00 08 00 00 Connector Type DVISL 0×00000200 = 00 02 00 00 Note: Single Link DVI On the contrary, Vervet had 2 of my connector types correct:
    Personality: Vervet ConnectorInfo count in decimal: 4 Disk offset in decimal 166224 0000000 00 04 00 00 00 04 00 00 00 71 00 00 12 04 04 02 // 0x400 means Display Port 0000010 04 00 00 00 14 00 00 00 00 71 00 00 01 12 01 04 // 0x4 means DVI-Dual Link port 0000020 00 02 00 00 14 00 00 00 00 71 00 00 00 00 06 03 // 0x200 means DVI-Single Link port 0000030 00 08 00 00 00 02 00 00 00 71 00 00 22 05 05 01 // 0x800 means HDMI 0000040  So I thought hey what the hell, I'll try it ,and to my blame-my-genius type of shock, it finally has worked.Video worked through HDMI and my card had the so crazily desired correct/corrected name.
    Gonna update the post after I used these chaned Vervet framebuffer and in order to make the 3rd port,by swapping  the Single Link DVI, with the working VGA from Baboon. This is how it looks:
    0000000 10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 02 // ex-Displayport, now VGA from Baboon Framebuffer 0000010 00 08 00 00 00 02 00 00 00 71 00 00 22 05 05 01 // ex-DVI-Dual Link, now HDMI 0000020 04 00 00 00 14 00 00 00 00 71 00 00 01 12 01 04 // ex-Single Link, now 0000030 00 04 00 00 00 04 00 00 00 71 00 00 12 04 04 02 // ex-HDMI type, now Display Port and the reason for using Display Port, 0000040 // was to preserve the framebuffer's port symmetry,weight. edit 1:
    Didn't do much.. VGA got recognized only if I use an HDMI to DVI adapter and a VGA cable but I didn't got the right resolution on that screen. Still a bit better than before.
    Im gonna continue tomorrow, I had an all-nighter and it's 8 am already..
    edit 2: (The Last Edit)          
    Curtesy of Antien's post here,behold a patched Vervet FrameBuffer that HDMI and DVI works perfectly.
    I added VGA from Baboon which I know is working and voilà, fully working DVI+HDMI(audio too)+VGA ports on MSI 6770 1Gb.
    I hope this will help present and future, 6770 owners. 
    0000000 10 00 00 00 10 00 00 00 00 01 00 00 00 10 00 02 // VGA from Baboon 0000010 04 00 00 00 14 02 00 00 00 01 00 00 11 02 03 03 // DVI-Dual Link from Antien 0000020 00 02 00 00 04 02 00 00 00 01 00 00 00 10 04 03 // Display Port from Antien 0000030 00 08 00 00 04 02 00 00 00 01 00 00 22 05 02 04 // HDMI from Antien 0000040
  24. Like
    angelol reacted to IIIdefconIII in Beginners guide to UEFI Triple/Dual boot OS X, Windows and Linux (Kali) on an single true-gpt ssd   
    Installing Windows 8.1 UEFI Mode

    Boot the Windows 8 usb installer
    Once in the setup it's almost straight forward:

    1. Select unallocated space
    2. Click "New", and choose partition size for windows (keep in mind you need to keep 5Gb for manual Recovery partition, and more for all extra operating systems you wanne install. You will see that windows need to add extra partitions, click "OK" to continue.
    4. Again, click unallocated space and create a Recovery partition (5GB). (Only if windows didn't create it automaticly, otherwise skip this step) (i never used it, cause i image my notebook)
    5. Now select youre first Primary partition after the MSR (Reserved) and click "Next" to install windows.
    Be aware! READ this post till the end before continuing.
    The computer can start Windows automaticly without giving you an option to boot OS X from Clover. Read the next post to fix this.
    Finish the recovery partition and make it active (Only if windows didn't created it automaticly) again, im not using this im just making a disk image if all is setup correct.
    Once booted in Windows 8.1 deskstop.Hit the Winkey +R, and run "diskmgmt.msc"; Here you will see youre earlier created Recovery disk, it RAW data though, so right mouse click on it and format it to NTFS; Right-click the partition, and then click Change Drive Letter and Paths; To change a drive letter, click Change, click Assign the following drive letter, click the letter that you want to use, and then click OK; Create a folder called Recovery on youre recovery partition; Insert the windows usb installer and copy /Sources/install.wim to the recovery folder on the recovery partition; Now run cmd in administrator mode and type: "reagentc /setosimage /path d:\recovery\install.wim /index 1". Verify that it works, so remove the usb (neccecairly step cause windows also search for the install.wim on the usb);
    1. Move your mouse cursor to top-right corner to show Charms Bar. Alternatively, you can press Win+C keys together to access it;
    2. Now click on "Settings" and then click on "Change PC settings" option;
    3. It'll open new Metro Control Panel screen. Click on "General" tab and in right-side pane, you'll see "Remove everything and reinstall Windows" option;
    4. Click on "Get started" button and Windows will show you Reset PC wizard. If it loads without an error that windows cannot find the recovery file, youre good and you can cancel the Reset your PC wizard.
    Keep note that the computername cannot be the same as the username, so DON'T enter you're wanted username in step 1 of the Windows personalization setup. I also recommend that you do NOT connect Windows with you're wifi network in the Windows personalization setup, otherwise you'll need a Microsoft Hotmail/Outlook/Live account to login, you can only create a local account if you skip the wifi handshake. If you want to read the OS X hfs drive from Windows, use MacDrive If you have a SSD, then Enable TRIM, after windows has booted, create a shurtcut to cmd.exe on the desktop. Right mouse click on it and click  "run as Administrator" now type:
    fsutil behavior set DisableDeleteNotify 0
  25. Like
    angelol got a reaction from fantomas in Radeon HD 6770 FULL QE/CI ML/Mavericks/Yosemite/ElCapitan/Sierra   
    Sure mate..I'll pm you sometime tomorrow cause it's getting late and I need to wake up early for uni!