Jump to content

Nameless One

  • Content Count

  • Joined

  • Last visited

About Nameless One

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Not Telling
  1. Nameless One

    [RELEASE] Open-source Clover fork with Ryzen support

    What flag are you referring to for testing when things don't work? Currently when I use the above cloverx64.efi to boot 10.12.5 I need to use -v in order to reach the desktop, without it the system just hangs part way through. Also I need to include busratio=37 or else the clock and all animations run way too fast and also Sierra will not load the Nvidia drivers at all (I don't use nvda_drv=1 but my previous cloverx64.efi didn't need it). I have forgotten which kernel version I am using, it has been a few weeks since I got my system installed and working but rc4 sounds familliar, is there anything within the files installed with the kernel to indicate which version it is?
  2. Nameless One


    I'm using this with my Asrock X370 Gaming K4 Ryzen motherboard (i211), it's fine provided I don't do anything that tries to write to a network share, doing that kills all traffic outright.
  3. Nameless One

    HELP TOPIC - [RYZEN] macOS 10.12.x (Sierra)

    AND THERE WAS MUCH REJOICING! I had 10.12.0 on and working this morning, but after upgrading to 10.12.5 and applying the Ryzen patching etc. it failed again. Then, having seen Gigamaxx' updated auto kernel, I made a fresh 10.12.5 install, ran the Ryzen patcher, applied the auto kernel files, and ran Kext Wizard. Presto! a working system, just need to sort USB (nothing shows in the USB section of System Information), make it say something other than "Generic AHCI Controller" for SATA, and get rid of the Orange drive icons. Also need to figure out why My Ryzen system doesn't like an identical install on a 64GB thumb drive, selecting it in the UEFI boot menu results in a blank screen rather than Clover and if I have the drive plugged in and try to use Clover on something else it plays up too, wasn't always playing up, just during the last few days which means I'll have to find another HDD to act as a backup system. Many, many thanks to Gigamaxx
  4. Nameless One

    HELP TOPIC - [RYZEN] macOS 10.12.x (Sierra)

    I've tried the auto kernel (assuming there has only been one version of it), what is "16.5"?
  5. Nameless One

    HELP TOPIC - [RYZEN] macOS 10.12.x (Sierra)

    That made no difference, it'll boot on my old hardware (i5 4670, H87 mobo) just fine but not on Ryzen.
  6. Nameless One

    HELP TOPIC - [RYZEN] macOS 10.12.x (Sierra)

    Hardware now in signature, and and what should be the original config.plist from my original successful install but which won't successfully boot my current attempt is attached, I am currently using the 10.12.4_auto kernel but I have tried others including whatever is the RyzenPatcher default, Sierra is at version 10.12.5 boot args=-v nvda_drv=1 busratio=30 fsb=100 kext-dev-mode=1 rootless=0 npci=0x2000 slide=0 config.zip
  7. Nameless One

    HELP TOPIC - [RYZEN] macOS 10.12.x (Sierra)

    Having struggled to find anything useful, what exactly is happening when booting via Clover UEFI, it prints its line of "++++" and then drops monitor sync and reboots?
  8. Nameless One

    HELP TOPIC - [RYZEN] macOS 10.12.x (Sierra)

    Sadly not me, I have an Asrock X370 Gaming K4, I had Sierra installed booting via Clover with everything except some of the USB ports working fine. I wanted to install a newer kernel from the dev thread, not sure what was newer, and ultimately hosed things since by that time I hadn't seen the one tiny mention almost hidden away that you need to merge the framework files rather than simply replace them. Subsequently starting again from a clean slate NOTHING works not even trying to redo my previous steps copying what Gigamaxx listed in the patcher thread. Why oh why can't we have all the important information (such as the need to merge rather than replace the frameworks) CLEARLY displayed somewhere prominent along with the latest files (for both Chameleon and Clover) also displayed prominently. I cannot get it past the line of "+++++++++", it just loses monitor sync and reboots every ****ing time. I have searched and gone through the various threads page by page looking for anything obvious but there is nothing, I vaguely remember someone else being stuck at this point and receiving help but I'll be buggered if I can find it.
  9. Nameless One

    HELP TOPIC - [RYZEN] macOS 10.12.x (Sierra)

    I Managed to get my setup working Yesterday (R7 1700, Asrock X370 Gaming K4) thanks to Gigamaxx' instructions in the patcher thread, had to reconstruct my old Intel setup first, most of the marathon effort was after I got it up and running. Somewhere early on the "a" key on my Apple aluminium keyboard failed and I had to copy and paste it, only just managed to get an old PS/2 keyboard working. I haven't tried much USB stuff, no info at all in system report for USB, for large USB 3.1 port only USB 2 devices re detected. I can't find drivers for the ALC 1220 audio and can't seem to get HDMI (Nvidia) audio working as a stopgap. Also need to find a link for the latest kernel, one that doesn't play with the CPU clock speeds so I don't lose my overclock under macOS *edit* upon reboot the PS/2 keyboard was no longer working, fortunately was able to dig up a USB keyboard hidden away somewhere.
  10. Sadly no one appears either interested in putting up something clear and concise or is sufficiently skilled to do so. As an aside, I also find it a very frustrating when someone uses a thread title that makes it look like the thread is itself a guide when it is not, you had my hopes up there for a moment. At least if a question is being asked then put a question mark (or two or three) on the end of the title.
  11. Nameless One

    R9 290X graphics card, Yosemite and Dual Screen?

    At this time, without a CPU/motherboard combo that provides onboard graphics, there is nothing that you can do to get multiple monitors working as far as I know. I tried the things done by others like using other framebuffers such as Baladi and patching them but nothing worked for me. I have: <key>FakeID</key> <dict> <key>ATI</key> <string>0x67B01002</string> </dict> in Clover Devices section, but this is no use to you as your card is a real 290X. I have: <key>Graphics</key> <dict> <key>FBName</key> <string>Hawaii</string> <key>Inject</key> <dict> <key>ATI</key> <true/> </dict> <key>InjectEDID</key> <true/> <key>PatchVBios</key> <false/> <key>VRAM</key> <integer>4096</integer> </dict> but none of that has any effect for dual monitor purposes, if I disable onboard graphics in the BIOS I have the same problem as you, one monitor only working and plugging in others makes the first one go black. If your card is working properly with one monitor without parts of the above Graphics section then you don't need the bits you are missing. I think that either the Intel kexts are setting something that the AMD ones should but aren't or one of the generic kexts is doing something when it sees the Intel hardware that it should do for the AMD hardware but doesn't. It is the enabling of the HD4600 GPU built into my Intel CPU that allows me to run my three monitors, even when none of them are plugged in to the HD4600.
  12. Nameless One

    R9 290X graphics card, Yosemite and Dual Screen?

    The only difference between getting a 290X going and a 290 is that you don't need to modify anything for the 290X. From my personal experience (as a 290 owner injecting the 290X ID via Clover so that OS X thinks I have a 290X) the only reliable way to do multi monitor with these cards at this time is to enable Intel onboard graphics in the BIOS. You don't need a monitor plugged in to the onboard although you are unlikely to see anything until the OS X desktop is drawn if you don't have a monitor using onboard. I have successfully had three monitors running off my 290 (2x23" on DVI, 1x30" on DP) with the Intel onboard enabled although I've moved one of the 23" to the onboard DVI so I can see BIOS and Clover info during boot. If you have the card fully working (opengl games, smooth video, desktop etc) with no modifications and one monitor then it will be using the Hawaii framebuffer since that is the only one which contains the device ID for the 290X when no user modifications have been made.
  13. Nameless One

    Multi Monitors on Yosemite

    With Intel onboard enabled, and Clover injecting the R9 290X ID in place of R9 290, no kexts modified, I have a 30" and a 23" monitor attached to the R9 290 (DVI & DP) and a 23" to the Intel onboard (DVI) everything working fine. If I didn't want to mess with the BIOS or fiddle with Clover during boot I could attach the second 23" to the second DVI on the R9 290 and boot blind. Rather disappointingly I get 86.82 fps (the fans don't ramp up at all and it labels the card as some Hawaii prototype) and 547 cb in Cinebench R15 (for some reason it says the CPU has 2 cores, 4 threads) 75.79 fps with the window on the display plugged into the onboard Intel HD4600 Intel i5-4670 Asrock H87 Fatal1ty Pro 16GB DDR3 1600MHz Powercolor PCS+ R9 290 4GB
  14. Nameless One

    Woke Up to Find Yosemite Unbootable

    I've had some issues with Clover the last time or two that I have updated it, it removed OsxAptioFixDrv-64.efi from the drivers64UEFI folder on the EFI partition. Once I had put it back in place (having a fully working USB installer to fall back on is very handy) it booted fully.
  15. Nameless One

    R9 and R7 support in 10.10 (Finally)

    With onboard graphics (Intel HD4600) enabled in the BIOS (and VRAM for the onboard set to the lowest value for it 32MB) I have three monitors working all plugged into my R9 290, a 30" via DP and two 23" via DVI. No special stuff in Clover other than injecting the 290X dev-id to avoid modifying kexts. With this approach my system (Asrock H87 Fatal1ty motherboard + i5 4670) boots blind until OS X starts to draw the desktop which makes changing BIOS settings or selecting other Clover settings difficult, need to plug one of the monitors into the onboard to change settings. For me having one of the 23" monitors plugged into the onboard permanently is functionally the same as having all on the 290 and allows me to see the entire boot process.