Jump to content

c_g_f

Members
  • Content Count

    5
  • Joined

  • Last visited

About c_g_f

  • Rank
    InsanelyMac Protégé
  1. c_g_f

    [HOW TO] Modification of AMD FB + Clover injection

    I've been doing some testing to see if I can finally boot using the DP port of my 390.. some very weird things happen.. and now I realise this frame buffer issue might be more complicated than I thought.. IF I USE BALADI... I'm unable to boot directly to any of the ports of my 390. The only way to boot is using igpu and unhooking every cable from my 390. Once a have the login image I can hook cables to the 390, the system treats them as secondary displays. In system report I can see the card as AMD Radeon 290/390 with 8192 ram. Latest patch used 00040000 04030000 00010101 00000000 12040101 00000000 DP (WORKS but only if the dvi that works is hooked first) 00080000 00020000 00010200 00000000 22050203 00000000 HDMI (WORKS) 04000000 14020000 00010300 00000000 10000406 00000000 DVI-DL (DOESN'T WORK) 04000000 14020000 00010400 00000000 11020304 00000000 DVI-DL (WORKS) 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 The fact that the DP port is recognised by the system only if the DVI is hooked first is what amazes me. That's actually why I filled the 2 last ports with zeroes but it did change anything. I read in rampage site something about dependency between some of the bits.. this has to do with that.. IF I USE RADEON FRAME BUFFER.. I'm still unable to boot directly to the 390. Same method as before, waiting for the login image and plugging the cables then. BUT.. every port is recognised and when I plug the DP cable the system makes the DP display primary.. system says that I'm using a AMD Radeon HD 8xxx 8192 MB I have notice a very small difference with IOJones regarding the way the DP port is recognised with each buffer I don't know the differences between the 2 buffers. Do I loose performance or functionality by using radeon's? how can I test? Concerning my freeze at booting with the 390 I'm pretty sure is one of 2 things. My bios, in which case I could try older versions, but the latest is the only one that has CSM feature that I can disable. Or it's maybe my boot arguments or ACPI patches. I have left all those by default but maybe I should uncheck some of them. The only thing I changed was adding verbose (without verbose no boot either in case you're wondering) but there are a lot of arguments. I hope someone will be able to help.. Thanks to all for the information shared. I thought I would share my findings as well. EDIT: booting directly to DP at last!!! I just don't understand this, before my first installation I've read "disable CSM" in each guide I came across. In my case it has to be enabled.. maybe it's because I'm using a patched bios?
  2. c_g_f

    [HOW TO] Modification of AMD FB + Clover injection

    @ Loco Massa, I have to try it, but I'm trying to make the DP to work, otherwise I'm stuck at 30hz since my monitor is 3440x1440. I'm pretty sure the patch I have now is the right one, IOJones matches the entries for the 4 ports. I had to install the whole thing again because my boot or my bios became corrupt. Redownloaded bios, repatched it, reformated disk, etc. Now when I select iGPU as primary the image goes to the monitor hooked to the iGPU and I get full resolution with igpu (injecting fake intel id with some other buffer patch) but when I hooked a DP cable on the 390, boot stops at the end. Maybe it has to be with HDMI audio? something is preventing the thing to work. I've been reading about DSDT and SSDT but now I just have an horrible headache. When no cable is hooked to the 390 and I boot to igpu the system detect the intel card but also the 390 (I injected 0x67B01002) with all its memory but when I hook the cable I just dont see a second monitor and the system refuses to boot with a cable hooked to the 390 (I tried DP and DVI-DL) If somebody has an idea please help. I've been praying like for a week but it doesn't seem to help
  3. c_g_f

    [HOW TO] Modification of AMD FB + Clover injection

    Yes I did.. my bios settings for the graphics are: Primary graphics: onboard Multi monitor iGpu: disable Shared memory: 32 Render standby: disable I've tried with other values for shared memory and enabling multi monitor and render standby but same result. I have the DP cable linking the 390 to my monitor and a hdmi cable linking the onboard graphics to the same monitor. But there's a strange behaviour of my motherboard: if the 390 is in the system, when I enter the bios the signal goes to DP even if in bios the onboard is set as primary. The clover page also goes to DP. In windows I can actually see the second monitor, the one hooked to onboard hdmi, so I know it's working but it seems that selecting onboard as primary doesn't do what it is supposed to. I'll try with other bioses versions. I'm almost sure the problem is with my bios. Thanks for replying!
  4. c_g_f

    [HOW TO] Modification of AMD FB + Clover injection

    Hello everybody! First of all, Vlada, thanks a lot for your guide which has helped me a lot to understand the connectors issue. I feel so close to get it working and at the same time I feel really close to jump out of the window so... PLEASE HELP ME My system: -Motherboard: Asrock Z68 Extreme3 Gen3 (flashed with patched 2.31 bios) -CPU: i5 2500k -GPU: MSI R9 390 Gaming 8G -Display: Samsung S34E790C 3440x1440 -Bios set to Onboard Graphics as primary + AHCI + CSM disabled Configuration: -macOS 10.12 Sierra + clover bootloader (uefi only + ESP + osxaptiofix2drv as the only driver installed) -FakeSMC + ethernet in kexts/other Clover Configurator changes: -SMBIOS iMac 12,2 -Verbose boot Extensions Folder changes: -added 0x67B11002 into AMD8000Controller and AMDRadeonX4000 kexts and fixed permissions Framebuffer Info Personality: Baladi ConnectorInfo count in decimal: 6 Disk offset in decimal 1928240 00040000 04030000 00010300 00000000 12040303 00000000 00040000 04030000 00010100 00000000 11020101 00000000 00040000 04030000 00010200 00000000 21030202 00000000 00040000 04030000 00010400 00000000 22050404 00000000 00040000 04030000 00010500 00000000 10000505 00000000 00040000 04030000 00010600 00000000 20010606 00000000 My codes in order: 12040101 DP 22050203 HDMI 11020304 DVI-DL 10000406 DVI-DL Patch 1 not working 04000000 14020000 00010300 00000000 11020304 00000000 00040000 04030000 00010100 00000000 12040101 00000000 00080000 04020000 00010200 00000000 22050203 00000000 04000000 14020000 00010400 00000000 10000406 00000000 00040000 04030000 00010500 00000000 10000505 00000000 00040000 04030000 00010600 00000000 20010606 00000000 Patch 2 not working 00040000 04030000 00010300 00000000 12040101 00000000 00080000 00020000 00010100 00000000 22050203 00000000 00040000 04030000 00010200 00000000 21030202 00000000 04000000 14020000 00010400 00000000 11020304 00000000 00040000 04030000 00010500 00000000 10000505 00000000 04000000 14020000 00010600 00000000 10000406 00000000 WHAT WORKS: Setting 1920x1080 in GUI section in CC without ATI injection gives me native 3440x1440 resolution but the GPU shows as having 18MB Ram.. and well there are glitches galore. THE PROBLEM: When I inject my GPU ID 0x67B11002 and tick ATI injection (before patching the kexts in S/L/E I tried with 0x67B01002, the one for 390X cards, but same result) I have a BLACK SCREEN and then display goes off. disconnecting and reconnecting the cable does nothing MY QUESTIONS: 1. Could somebody tell me what is wrong with my patches. Vlada says we should order by senseID but how exactly? 2. I read somewhere that the HDMI kext causes trouble? 3. Maybe Im just unlucky and my mobo/GPU is a bad combination? Thanks in advance for your help.
  5. c_g_f

    AMD R9 390 Framebuffer issue on 10.12 Sierra

    Hi Loco.. I'm kinda of a noob on hackintoshes so please be patient. I'm trying to get my MSI 390 (non-X) to work on my newly Sierra installation but I'm kinda new to this patching world. Also I do my plist edits with CC. I'm very interested in this line of your post I am using AtiInjection, injected DeviceID 0x67B11002 in AMD8000Controller and AMDX4000 under Hawaii and patched Baladi framebuffer In clover plist I have put the same fake ID and have ticked ATI injection and that get my card recognised by the system but with 5 MB of memory, I cannot change the resolution and there's tearing everywhere. If you could please explain how you did it I'd be really thankful. The patching is done in Clover? why do you say you inject the ID into 2 kexts? Maybe there's a tutorial you can point me to. Thanks
×