Jump to content


  • Content count

  • Joined

  • Last visited

About haegar33

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
  • Interests
    My Hackintosh: GA-Z97X-UD7-TH | i7 4790K | Radeon R9 290x

Recent Profile Visitors

829 profile views
  1. haegar33

    Still black boot with R290X on Sierra

    Ok, tried with the Lilu Patcher and Whatsevergreen (hard to find compiled kext version for these..) Still black screen with some flicker after boot which can be removed by shortly unplugging the monitor cable. Only difference with Whatevergreen: The system info now shows the correct GPU name
  2. haegar33

    "new" ATI Clover patching with Sierra?

    Yes might be an option. But I cannot find any instructions or pre-compiled Lilu.kext and WhateverGreen.kext. Looks like I have to compile from source code???
  3. haegar33

    Gigabyte R9 390 in High Sierra

    I thought these patches are included in Clover Version 4418 and above? its a flag called RadDeInit.
  4. haegar33

    Still black boot with R290X on Sierra

    I have browsed thru all forums and all threads for this card but apparently my system is still something special. With some cumbersome effort (none of the simple one-click ##### and other USB-Installers methods ever worked for me) I managed to install Sierra 10.12.5. However when booting is nearly finsihed I get the famous black screen which can be recovered by quickly unplug/plug the DP monitor cable leading finally to a proper initialisation of my 290X. 1.) RadeoDeInit is on, without this patch the screens stays dark forever2.) Booting with iGFX never works for me, I always get memory allocation errors during boot until I disable the Intel graphics completely.3.) I am on Clover 4318, newer version do not make any differences. 4.) I am using a System Configuration for an Imac 14,2. Most other configs do not make difference either.I have not started again the nightmare of Framebuffer patching (as I remember from Yosemite) and I think it will not help as the card is recognised by Sierra but just not initialised.
  5. haegar33

    "new" ATI Clover patching with Sierra?

    Quick general question on patching with the Clover configurator: Shall I still use the specific patch fields called "ATI Connectors" or shall I use the generic kext patch GUI with the "Find" and "Replace" entries? I see some hints with both methods. In old Yosemite days always used the ATI Connectors. Has the kext patch method something to do with the new longer frame buffer contents in Sierra and above?
  6. haegar33

    [HOW TO] Modification of AMD FB + Clover injection

    Quick general question on patching with the Clover configurator: Shall I still use the specific patch fields called "ATI Connectors" or shall I use the generic kext patch GUI with the "Find" and "Replace" entries? I see some hints with both methods. In old Yosemite days always used the ATI Connectors. I got a 90% successful update to Sierra with my R9 290X but still get the "black on boot" problem. All available hints (RadeonDeInit, iGFX enabled etc.) where not successful so far so I am afraid I am back in the "patching business"
  7. Thanks @wastez but I am using the ATI R290X graphics card. I cannot enable the internal HD4600 graphics as I always get "memory allocation" errors during the Clover boot. I spend millions of hours searching the boards for the best Framebuffer patch. I now have one which is reasonable stable (with 2 monitors) but still shaky as described above. Anyway, I replaced the AppleIntelE1000 with the IntelMaus Kext. It works but no difference to my problem. The search goes on... @Mieze: Because I see more freezes when connected to my LAN.. @MacUser: Even if it would be a "GUI Problem" I have to search for the cause. I am not building a Hackintosh for working from the command line.
  8. I am jumping on this topic as I am still investigating my unstable Yosemite Hackintosh. The main suspect for hundreds of error messages in the logs .. (from Windows_Server: surface testing not allowed, from iconserviceagent: crashes, from spinball-daemon: numerous messages indicating freezing of several apps for seconds) ... was always my frame buffer patches for my ATI RX290 graphics card. However I am observing a particular unstable system when I have mounted one or several disk shares (AFS) from my NAS or other network sources. Thus I wonder whether the LAN driver AppleIntelE1000e.kext might be the culprit? To be clear, booting is fine, OSX 10.10.5 works but from time to time it gets very laggy for no apparent reason.
  9. haegar33

    Is there real documentation for clover

    I have no touched the BIOS settings for a long time (always set to my "working" SSD with OS X 10.10). However since I fiddle with a test installation of 10.11 on HD2 this disk often, not always, becomes the default boot disks. And yes indeed, Clover seems to follow the BIOS boot order settings. this appears to overrule all boot settings inside clover config.plist: specifying a disk name for DefaultVolume has never an effect setting DefaultVolume to "LastBootedVolume" works sometimes, specially when the PVRAM value has been set (OS X PrefPane "Startup Volume")
  10. haegar33

    Is there real documentation for clover

    Thanks, that was already good information. I am aware of the Wiki, its a good starting point but it appears not be updated with each new Clover release. For example a parameter like rootless=0 is not explained. For the multi boot disk question the confusion might arise from the parameters which control the kext patching (or not). I am sometimes not sure whether my kext was now patched properly or not. It should also be documented that you can always review the boot log with 'sudo /sbin/dmesg' so people don't need a screenshot from a "verbose" boot screen. with manual overwrite I mean the "Options" menu in clover. It is clear that this is temporary. But again, with a multi boot disk setup (in my case 3 different EFI partitions all with Clover) there must be "default read" of one of these config.plist files just to present the Clover GUI. I might do a simple test by choosing three different GUI themes in all the different config.plist files. Then I now exactly which one has been chosen to present me the GUI selection screen..
  11. Hello, being the most important tool for a Hackintosh I am surprised how sparse and scattered the information is about Clover. You got to dig into a (not up to date) wikis, threads with 1400 entries, confusion about keywords and parameters which are introduced (or abandoned) but hardly nowhere documented etc... I am using Clover now for 2 years and I am still not sure about the basic principles: - when I do have several boot disks which clover config is actually used? Sometimes I have the impression I am selected HD 1 for boot but config.plist from HD 2 is used....?? - Specifying the default boot HD in (any) config.plist seems never to be obeyed. The default Boot HD seems to be randomly selected..? - manual overwriting of parameter settings seems to work. Although again I wonder which config.plist is actually presented in the Clover menu to be modified? The one from the last boot? the one from a default boot...? Finding the proper configuration is hard enough for a certain hardware and Clover is excellent for trying different boot configs. Please could someone point me to a good documentation site so I and all user can use this tool more efficiently? Thanks, Haegar
  12. haegar33

    Which configuration file is Clover loading?

    I am confused with this explanation. It would mean that the boot configs for several disks are not predictable... I got 4-5 different disks, all with an EFI partition, one main Yosemite Disk, one Windows disk and experimental EL Capitan Disk (plus recovery HD etc..) When in Clover boot menu I always wonder which config.plist is actually loaded and presented in the GUI for temporary modification? The config.plist from my previous boot? from my default boot HD...? When I select one HD (or USB) for booting are the temporary mods merged with the config.plist on that HD or are they ignored? I browsed thru the numerous clover forum articles but I could not find any description how clover actually works..? Any hints appreciated.. Thanks!
  13. I have the same problem but I wonder whether this will work in my case. I have a AMD R9 290X card installed and always disable the internal Intel HD graphic in bios (otherwise I get the "cannot allocate memory" error) I assume these kernels have to be removed from the USB stick only?
  14. haegar33

    Infinite Gray Screen Error

    Same for me. At tony86 there are some hints about FakeSMU Kext as the culprit. Did not help for me either. I have a perfect Yosemite install but EL Capitan Installer stops with a grey screen.
  15. haegar33

    290X/390X 10.12 FB patch thread

    Hi wardoc, I tested your patch on my system with Yosemite (10.10.5) and had the same mixed results as we many other patches: it works with 2 DVI screens but I get random freezes with always the same error message in the log: WindowsServer: Surface testing not allowed for ....... I patch with Clover, Card ID etc. is well recognised, graphic accelerations is working fine. Can I expect an improvement with El Capitan for my card? thanks, Haegar. My config: Saphire RX290 4GB, Board: Gigabyte Z87X-UD7-TH redsock_bios_decoder < Hawaii.rom 289X0500.X4F: E289 Hawaii XT TRIX A0 GDDR5 4GB 64Mx32 300e/150m Subsystem Vendor ID: 174b Subsystem ID: e289 Object Header Structure Size: 271 Connector Object Table Offset: 3e Router Object Table Offset: 0 Encoder Object Table Offset: ce 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 [4] which is [DVI_D] encoder obj id [0x20] which is [INTERNAL_UNIPHY1 (osx txmit 0x11 [duallink 0x1] enc 0x2)] linkb: false Connector Object Id [4] which is [DVI_D] encoder obj id [0x1e] which is [INTERNAL_UNIPHY (osx txmit 0x10 [duallink 0x0] enc 0x0)] linkb: false