Jump to content
Onestyle

El Capitan - Sierra - High Sierra - Sony Vaio E Series (2012) - SVE1712W1EB - AMD Radeon HD 7650M

59 posts in this topic

Recommended Posts

15 hours ago, Bananz0 said:

Any Updates to Mojave?

I’ve done some tests, small changes are needed but I won’t be fully updating to it until it’s final as I need a stable Mac OS.  Then I’ll update the first post too. 

Share this post


Link to post
Share on other sites
Advertisement
On 8/13/2018 at 6:08 AM, Onestyle said:

I’ve done some tests, small changes are needed but I won’t be fully updating to it until it’s final as I need a stable Mac OS.  Then I’ll update the first post too. 

I'm doing some tests as well. My model is slight different, but your tips work in the past and our systems are fairly similar. I can't make my radeon fully work. If you are getting same trouble, please let me know. 

Share this post


Link to post
Share on other sites
On 8/20/2018 at 2:05 AM, vanantonietti said:

I'm doing some tests as well. My model is slight different, but your tips work in the past and our systems are fairly similar. I can't make my radeon fully work. If you are getting same trouble, please let me know. 

What seems to be the problem? QE/CI, full resolution support, weird artefacts?? 

Share this post


Link to post
Share on other sites

A little update. Just tested Mojave latest beta, almost everything from the first post works ( some things need small fixes) , but there are some issues with the Radeon card. Since Mojave dropped certain kexts that were used since El Capitan to High Sierra, almost out of the box solution ( with clover and WhateverGreen) isn't possible at the moment. I've managed to get Mojave to read the gpu as AMD Radeon HD 7650M Series 2048 MB by using the kexts from High Sierra ( the ones that Mojave dropped). But unluckily, no QE/CI at the moment due to Mojave not wanting to load AMDRadeonX3000.kext for some reason ( need to investigate why it's unwilling to load it, as that's the key of getting QE/CI) .

 

The kexts that were dropped in Mojave  and are used to get this GPU running in older Mac OS's are AMDLegacySupport, AMDLegacyFramebuffer, AMDRadeonX3000 and AMD6000Controller.

This is a long shot thought, considering the fact that Mojave is full on Metal, and this gpu isn't playing well with Metal. The laptop I'm using needs to be stable, so Mojave will get a certain amount of attention, basically I'll be playing around with it since it's worth trying. If anyone ends up having some progress on this matter, finds something that might be worth trying, I welcome anyone willing to help. :)

Share this post


Link to post
Share on other sites

 

On 8/28/2018 at 6:14 PM, Onestyle said:

A little update. Just tested Mojave latest beta, almost everything from the first post works ( some things need small fixes) , but there are some issues with the Radeon card. Since Mojave dropped certain kexts that were used since El Capitan to High Sierra, almost out of the box solution ( with clover and WhateverGreen) isn't possible at the moment. I've managed to get Mojave to read the gpu as AMD Radeon HD 7650M Series 2048 MB by using the kexts from High Sierra ( the ones that Mojave dropped). But unluckily, no QE/CI at the moment due to Mojave not wanting to load AMDRadeonX3000.kext for some reason ( need to investigate why it's unwilling to load it, as that's the key of getting QE/CI) .

 

The kexts that were dropped in Mojave  and are used to get this GPU running in older Mac OS's are AMDLegacySupport, AMDLegacyFramebuffer, AMDRadeonX3000 and AMD6000Controller.

This is a long shot thought, considering the fact that Mojave is full on Metal, and this gpu isn't playing well with Metal. The laptop I'm using needs to be stable, so Mojave will get a certain amount of attention, basically I'll be playing around with it since it's worth trying. If anyone ends up having some progress on this matter, finds something that might be worth trying, I welcome anyone willing to help. :)

 

Yes, I read something on reddit that some kext and framebuffer support was removed, someone propose the same solution you said, use older kext from High Sierra. I'll wait the final release a try again in a different drive, but I'm already accepting the fact that the update might not be possible, but I'm Willing to help and try to make it work. 

Share this post


Link to post
Share on other sites
On 9/23/2018 at 7:43 AM, vanantonietti said:

 

 

Yes, I read something on reddit that some kext and framebuffer support was removed, someone propose the same solution you said, use older kext from High Sierra. I'll wait the final release a try again in a different drive, but I'm already accepting the fact that the update might not be possible, but I'm Willing to help and try to make it work. 

Using simple kext copy and paste doesn't seem to do much good, it reads the gpu well but doesn't give QE/CI. My guess is that additional steps are required, like copy pasting some other stuff from High Sierra.
First test that I'm going to do with the final release version that's available now, after I download it and install it, is copy pasting framework related stuff like user nmano did for his Nvidia card : 

 CoreDisplay from 10.13.4 to 10.14

⁨System⁩  ⁨Library⁩  ⁨Frameworks⁩  ⁨CoreDisplay.framework⁩  ⁨Versions⁩  ⁨A⁩ Doesn't work 
This again is a longshot, but worth trying as the gpu is metal capable to an extent since it worked well and was supported in High Sierra. Plus, this isn't the first time framework related stuff had to be copied to get Radeon GPUs  working, similar thing happened when certain GPUs support was dropped after Lion. So, there's still hope :) . But at the moment I'm busy with my personal life, so Mojave testing will have to wait a bit. 

Edited by Onestyle

Share this post


Link to post
Share on other sites

@vanantonietti   Made some progress, still no QE/CI, but at least all Radeon kexts are loaded that are needed for QE/CI. (As shown in the screenshot)  Next step, figure out why QE/CI won't activate(what else needs to be copied from HS to Mojave to force it to work) . Whole progress so far includes a dirty solution that involves adding High Sierra kexts that AMDRadeonX3000.kext depends on to Mojave ( weird thing is, seems that Mojave doesn't complain about High Sierra kexts, so thats a big plus). To test if QE/CI works one simply needs to open dashboard and try to add a new widget, if it's fast and smooth, it works, if not, it doesn't.  

Screenshot.png

Edited by Onestyle

Share this post


Link to post
Share on other sites
On 9/25/2018 at 5:18 PM, Onestyle said:

@vanantonietti   Made some progress, still no QE/CI, but at least all Radeon kexts are loaded that are needed for QE/CI. (As shown in the screenshot)  Next step, figure out why QE/CI won't activate(what else needs to be copied from HS to Mojave to force it to work) . Whole progress so far includes a dirty solution that involves adding High Sierra kexts that AMDRadeonX3000.kext depends on to Mojave ( weird thing is, seems that Mojave doesn't complain about High Sierra kexts, so thats a big plus). To test if QE/CI works one simply needs to open dashboard and try to add a new widget, if it's fast and smooth, it works, if not, it doesn't.  

Screenshot.png

 

@Onestyle Great to know that you are achieving progress. I'm changing my approach, I'm stopping playing games on my PC, so I decided to make a hackintosh on my main desktop. I installed Mojave yesterday, I'll prepare backups HD and after everything is ok I'll try the dirty solutions you mentioned on my notebook, without any fear, I'm already reading about the problem and will try something soon. It's noticeable when QE/QI is working, even opening launchpad folders is slow

Share this post


Link to post
Share on other sites
Posted (edited)
 

@Nonta97, as u requested :)

 

Clover configuration-Graphics : 

 

set Dual Link : 0 , FB Name : Pondweed , Vram : 1,024 , Video Ports : 3 , Check Load Vbios ,Inject Edid , Inject ATI .
3. Clover configuration- Kernel and Kext Patches : 
Name : AMD6000Controller

use AMDFramebufferUtilty to get best result.

 

 

And @Onestyle y is ur Fake ID : ATI : 0x67411002 instead of 0x68411002

1002_6841.rom.zip

Hey where can I get the ati connectors data, I tried frame buffer utility and generated the cfg bin file and gave it as an input to AMD frame buffer utility. But it doesn't show any data. I also have the same graphics card amd 7650m (1gb) and core i3  cpu Sony Vaio 2012 model. I have installed macos seiraa  on it. Is the connector data same for each device?

Waiting for your reply.

Edited by anmols

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By fantomas1
      Hi InsanelyMacaholics   

      Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
       
      10.12.6
      Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs) New!
      Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
      Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
      Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo) 
      Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
      Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
      Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
      Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
      Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
      Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
       
       
      10.12.5
      Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
       
       
      10.12.4
      Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
      Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr)  Pascal support!!!
      Nvidia Web Driver - 367.15.10.45f01 --> build 16E195 (thanks to Lanc)
       
       
      10.12.3

      Nvidia Web Driver - 367.15.10.35f01 --> build 16D32 (thanks to shatterhenner)
       
       
      10.12.2
      Nvidia Web Driver - 367.15.10.25f02 --> build 16C68 (see this post)
      Nvidia Web Driver - 367.15.10.25f01 --> build 16C67 (see this post)
      Nvidia Web Driver - 367.15.10.25b06 --> build 16C60b/16C63a (see this post)
       
       
      10.12.1
      Nvidia Web Driver - 367.15.10.15f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
      Nvidia Web Driver - 367.15.10.15f01 --> build 16B2555 (thanks to Moviemakergr)
       
       
      10.12.0
      Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
       
       
      GM
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
       
       
      DP/PB
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
      Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun) 
      Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
      Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
       
    • By MaLd0n
      ---INSTALLATION TUTORIAL---
       
      ---Original Post---
      https://olarila.com/forum/viewtopic.php?f=45&t=9172
       
      ---CLOVER FOLDER---
       
      CLOVER.zip
       
       
      --MOBO
      GigaByte Z390 M Gaming



      --PROCESSOR
      Intel Core i9-9900K


      --COOLER
      CoolerMaster MasterLiquid ML120R RGB


      --MEMORY
      Corsair Dominator Platinum 16GB (2 x 8GB)


      --GPU
      Sapphiretech Radeon RX 590 8 GB GDDR5


       
      --SSD
      Samsung 970 EVO NVMe M2 Flash Drive


      --POWER SUPPLY
      EVGA 750 N1, 750W


      --WIRELESS
      TP-Link Archer T9E


      --BLUETOOTH
      Orico BTA-403


      --CASE
      Thermaltake View 21 Tempered Glass Edition


      --DSDT Patches--
      -FIX ERRORS AND WARNINGS -FIX ACPI ERRORS -REMOVE UNUSED SCOPES / DEVICES -HIGH PRECISION EVENT TIMER -SATA SERIE 10 ID -DMAC -REMOVE 22K LINES, PROBLEMATIC and UNUSED -FIX K.P in REBOOT -NVRAM / REAL TIME CLOCK -SLPB -DARWIN / WINDOWS 2015 -XHCI -PLUGIN TYPE -HDAS to HDEF -HDEF -REAL TIME CLOCK -ARTC -IRQs -SBUS -MIKEY -BUS1 -MCHC -ALS0 -SHUTDOWN -UAR1 -LAN -FWHD -USBX -PMCR -PPMC -XSPI -GMM -IMEI -EC -PNLF -ARPT -GFX0 -NVME -DTGP -ACQUIRE MUT0 0XFFFF -OPERATION REGION GPIO -MUTEX MUT0 0x00 -EXTERNAL REFERENCES -UNKNOWNOBJ -HDMI / HDAU -FULL RENAMED DEVICES  
      --SCREENSHOTS--





























      --BruceX--
       
      --USB-C-- test with SanDisk Ultra USB-STICK 128gb


       
      -Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
      Slice, Kabyl, usr-sse2, jadran, Blackosx, dmazar, STLVNUB, pcj, apianti, JrCs, pene, FrodoKenny, skoczy, ycr.ru, Oscar09, xsmile, SoThOr, RehabMan, Download-Fritz, Zenit432, cecekpawon, Intel, Apple, Oracle, Chameleon Team, crazybirdy, Mieze, Mirone, Oldnapalm, netkas, Elconiglio, artut-pt, ErmaC, Pavo, Toleda, Master Chief and family, bcc9, The King, PMheart, Sherlocks, Micky1979, vit9696, vandroiy2013, Voodoo Team, Pike R. Alpha, lvs1974, Austere.J, CVad, Sampath007, onemanosx, erroruser, Jenny David, Olarila Facebook Community, Hackintosh Facebook Community and many others!
      We're all here to have fun and learn from each other!
    • By Candrahm
      Hi everybody,
       
      I'm new here and French. 
      I success to hack my Asus X751LJ and pass it to High Sierra 10.13.6, not easily, and everything works except the keyboard and the touchpad.
      I tried VoodooPS2Controller, ApplePS2SmartTouchpad, even VoodooI2C, but nothing works...
      Could someone help me? Is there a DSDT problem? Witch kext should I use?
      I post my ACPI and Kexts folders and my IOReg.
      Please... Help me. I'm desperate...
      MacBook Pro de Candrahm.ioreg
      Archive.zip
    • By blxkspell
      Hey!
      As I have 3 Monitors connected, my RX 570 gets arround 50°C while ideling/ web browsing etc. The problem is, that this temp is apparently just the threshold, when the fans start to spin. So the fans start spinning for a minute then they stop for a while again... This is very annoying for me as the rest of my hackintosh is nearly quiet (SSD, 120mm low RPM cpu fan, nearly silent PSU,...), especially when Im using the pc to revise for school. Does somebody know wether its possible to "change" the threshold till the fans start spinning? Like it would probably not be a problem for the gpu at all, if the temp rises to 55°C but therefore be soundless....
       
       
    • By penghubingzhou
      URL:https://github.com/penghubingzhou/VoodooI2C-DSDT
       
      VoodooI2C-DSDT is a repository that is aiming at collecting various successful DSDTs for Voodoo I2C.
      Purpose
      The purpose of this repository is to provide some useful code examples for people who haven't yet make Voodoo I2C work. Maybe It don't have your model of laptop, but code in this repository may have some help and references for you.
      Note that the code in this repository is ONLY FOR REFERENCES and it can‘t replace your own work!
      For Submission
      This repository welcomes everyone to submit DSDT code examples that have successfully made VoodooI2C work by PR. To submit your example, please put the DSDT file (or Hotpatch SSDT file), an ioreg without Voodoo I2C installed, and Info.txt in a folder named by your laptop model. Info.txt should include:
      Your CPU model (better for including CPU platform)
      Your touchpad Device ID
      The mode you use (GPIO interrupt or polling)
      Satellite Driver You Use
      Then, fork this repository and clone it, put your file in and commit it to your repository. After checking the conflicts, you can send your commit as a PR to me.
      An example for submitting can be found in Lenovo Xiaoxin Chao 7000-14.
      Credits
      @Alexandred for VoodooI2C @daggeryu for the idea in this repository @penghubingzhou and @williambj1 for maintaining
×