Kprao-kgp-keyboard-layout-for-mac/readme.md At Master

Kprao-kgp-keyboard-layout-for-mac/readme.md At Master Average ratng: 4,5/5 5930 reviews

I tried some hours getting iMessage to work, after updating to 10.13.5. After many testing, i found that CLOVER was to blame.

Before i updated to 10.13.5, i installed CLOVER 4498 (coming from 4428). Any CLOVER Version i tried prevented activating i Message (iMessage Error in systemlog: 13) I tried 4497, 4509, 4458 and 4522. Rolling back to CLOVER 4428  brought back the capability to activate iMessage. IMessage is set up correctly regarding ROM and MLB and never was a issue before. I too have the same issue, I was trying to find the culprit. I'll take a look at it on the weekend. I too have the same issue, I was trying to find the culprit.

I'll take a look at it on the weekend. Right about June 6 my Messages/Facetime, which have been working for many years, just stopped working. It wouldn’t activate. I spent at least eight hours on Monday trying to figure out why. I deleted pref files, even changed my rock solid config file with new serial number, board serial, ROM, MLB, etc. I even called Apple which I know was a stupid idea.

Popular Alternatives to Seil for Windows, Mac, Linux, BSD, Web and more. Explore 12 apps like Seil, all suggested and ranked by the AlternativeTo user community. I have just installed a PC keyboard on my Mac Mini, everything is looking good, I swapped the keys Alt and Windows so that it's more natural for a Mac keyboard but I just can't get used to Alt Gr. I have just installed a PC keyboard on my Mac Mini, everything is looking good, I swapped the keys Alt and Windows so that it's more natural for a Mac keyboard but I just can't get used to Alt Gr. I need to use some Alt Gr + keys to get some specific keys on a non English keyboard.

So others are having this same issue? I tried to go back to version 4497 but it didn't work. I think I've screwed something up with Apple activation servers now.

Right about June 6 my Messages/Facetime, which have been working for many years, just stopped working. It wouldn’t activate. I spent at least eight hours on Monday trying to figure out why. I deleted pref files, even changed my rock solid config file with new serial number, board serial, ROM, MLB, etc. I even called Apple which I know was a stupid idea. So others are having this same issue? I tried to go back to version 4497 but it didn't work.

I think I've screwed something up with Apple activation servers now. I am not alone!!!

Right, something like that. Yesterday I tried to fix but. Following the discussion from the separate topic (good investigation, guys!), it seems that the iMessage problem originates from the change at. Before this commit, built-in property injection for LAN was being made by default. Starting with 4497, an option to control this feature was added, with its default being set to FALSE (so built-in property is being injected only when LANInjection setting is activated). And as we already confirmed in the past, iMessage activation is insisting on the built-in property to exist on some device in order to activate, even if the actual connection is from a different network device. Perhaps we could consider setting LANInjection default to TRUE, to avoid breaking iMessage for people that are relying on this.

Edited June 20 by Pene. And how much VBofHFS is slower? Did you notice?

It is better supported links and listings. You're right. Last time I used it, and that was a long time ago, no, I can't say I've noticed any huge difference.

I just went for what I thought it would be the better option. But no, I can't say it's noticeable. Can't really test that right now, since all my drives are using APFS now. I guess I could try that with a USB drive, right? Since those are formatted HFS by default, for as far as I know. Anyway, thank you very much for your feedback. Update: yep, same thing with or without HFSPlus.

Also tried AptioMemoryFix. And.so far so good. At least on this system. Thank you guys for your feedback. Edited June 22 by arsradu. Weird issue with the vboxhfs-64.efi I created 3 striped array.

5x 1TB I get a bootloop on the 2 and 3. No issues on 1. Clover doesn't even display the volume/HDD selection screen. Bootloops immediately before it gets to this screen. As a test, I replaced vboxhfs with hfsplus and and I can finally boot on 3.

I'm guessing 2 shouldn't be a problem anymore. Does this mean vboxhfs has some sort of storage limit?

- Another question please: Is it advisable to install all the provided drivers? I'm not installing anything extra for drivers64. Just the already selected options. For drivers64UEFI, I'm adding AptioMemoryFix and EmuVariableUefi-64.

Thanks again. Edited June 22 by mrjayviper. Hi guys, Are the drivers that Clover proposes for installation documented anywhere? I know some of them are.

Kprao-kgp-keyboard-layout-for-mac/readme.md At Mastercard

But I couldn't find a proper description for most of them. And the description within the installer itself is far from being.descriptive enough.:)) So, unless you used them before, or you somehow know what they are good for, it's very hard to choose the right ones. Rule of thumb is usually start with only a few ones. But how do you know WHICH ones? Especially since they're not grouped in any way. You don't know which ones are good for what. Some of them are documented, for as far as I could see. Some of them are in Clover Change Explanations thread.and some others probably scattered throughout the forum.

I can collect them in a single thread, that's not a problem (in case nobody did that already). Although, in my opinion, the first place where they should be documented, is on the Clover Wiki. After that, they should be in the actual description box of the installer itself. Still, in order to do that, I would still need a good description for each one of them, in terms of what they are, and what are they good for.

Also, whether or not they create conflicts with other drivers. I totally agree on the lack of proper documentation on the drivers, I'll be more than happy to help on creating a thread with you but if some of our streamed coders and devs can point us in the right direction. I tested latest ApfsDriverLoader.efi with latest AptioMemoryFix.efi and PartitionDxe-64.efi. But i can't see apfs partition entry in GUI. There is no problem in v1.0.2 since v1.1.0, i never get entry in GUI. Thanks I had the same problem with legacy booting of apfs Mojave partition on my GA-P55aUD3 (system 2 in signature). ApfsDriverLoader.efi v1.0.2 works but not 1.1.0 or newer (even with PartitionDxe-64.efi in /drivers64).

No problems with UEFI booting apfs volumes on my NUC6i5SYH however, using ApfsDriverLoader.efi v1.1.0 & newer, no PartitionDxe-64.efi. In /drivers64UEFI. Clover r4747 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation. Tested with unlocked Workstation 15 running OSX 10.9 -10.14 guest in Windows X64 host.

Installation 1. Download and unzip 'EFICloverr4747 for VMware.zip'. Mount Clover-v2.4k-4747-X64 by double clicking on it. Mount your VM's EFI System Partition eg in terminal sudo diskutil mount disk0s1 3. Copy EFI folder from step 1 into the EFI partition 4.

Shutdown the VM, add bios.bootDelay = '3000' to your VM's vmx file 5. Reboot your VM, press to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu. Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM. Hi all, I hope someone can help me as I am struggling with this bloody installation.

IntelGraphicsFixup, NvidiaGraphicsFixup, and Shiki are now officially dead and are part of WhateverGreen. Using them together is not supported and will lead to undefined behaviour. New WhateverGreen features should improve the maintainability, compatibility and performance of the overall solution, as well as simplify the installation. For the time being the latest versions of Lilu, AppleALC, and WhateverGreen are only available in source and are recommended for trying. Intel GuC firmware loading caused random freezes and kernel panics as well as no visible performance boost (aside different numbers in sensors) and was removed as harmful. The rest of the functionality is mostly intact.

@ vit9696 I've just replaced the NvidiaGraphicsFixup kext with the new version of WhatEverGreen and I think I found a bug. So far I've been using NvidiaGraphicsFixup + ngfxpatch=pikera boot arg that solved a High Sierra black screen after wake-up problem. Now, after replacing NvidiaGraphicsFixup with WhatEverGreen, the screen does not wake up properly after sleep. No matter is it auto-sleep or manual sleep (chosen from the Apple menu). I see that ngfxpatch=pikera became agdpmod=pikera - I tried both, just in case, but it doesn't help. // EDIT: I've just found some weirdness.

When I use the agdpmod=pikera flag (which, I assume, is a replacement for the ngfxpatch=pikera flag) then, on a log-in screen I have full HD resolution instead of 4K res. When I use the ngfxpatch=pikera (which is deprecated, I guess) then the log-in screen resolution is fine. macOS 10.13.6, MSI GTX960 running 4k res, Nvidia Web Driver 387.10.10.10.40.105, Z87M-PLUS Clover config: Kexts: AppleALC.kext FakeSMCCPUSensors.kext FakeSMCLPCSensors.kext RealtekRTL8111.kext WhateverGreen.kext FakeSMC.kext FakeSMCGPUSensors.kext Lilu.kext Lilu.kext SATALegacy.kext All kexts up to date. Including Lilu. I'd like to confirm that the wakeup issue is gone after updating WhateverGreen to v1.2.1, but the login screen resolution issue still remains. With the latest WhateverGreen1.2.1 there is no use in CoreDisplay Fix with high resolution support. I downgrade the WhateverGreen to 1.2.0 and get the CDF Patched support again.

Update: Now i tried to add bootarg with -cdfon and the cdf patch come back and works well. Can confirm the same happens on my 2017 15' HP Spectre X360. With WEG 1.2.0 installed the 4K display on my laptop was 60Hz, after updating to WEG 1.2.1 the 4K refresh rate was down to 40Hz Added the -cdfon boot flag and rebooted and the refresh rate was back to 60Hz Maybe this change is by design? @headkaze, I'm still unable to use WhatEverGreen on my desk top system that has a single Nvidia 980 TI GPU. Detailed report of the issue is in Since then I've tried building WEG from the source's as suggested by pavo but it gave the same result as both official release versions 1.2.0 and the recently released 1.2.1. As stated in that post using NvidiaGraphicsFixUp works fine. Deleting it and installing WEG results in a KP, I am using the latest Lilu kext (1.2.6) Have not had any issues with WEG on all my other systems but those are using Intel IGPU.

Nvidia HDMI Audio is working via AppleALC so i don't think its a frame buffer issue. Do you have any thoughts on the issue or how best to go about debugging the problem? @headkaze, I'm still unable to use WhatEverGreen on my desk top system that has a single Nvidia 980 TI GPU.

Detailed report of the issue is in Since then I've tried building WEG from the source's as suggested by pavo but it gave the same result as both official release versions 1.2.0 and the recently released 1.2.1. As stated in that post using NvidiaGraphicsFixUp works fine. Deleting it and installing WEG results in a KP, I am using the latest Lilu kext (1.2.6) Have not had any issues with WEG on all my other systems but those are using Intel IGPU. Nvidia HDMI Audio is working via AppleALC so i don't think its a frame buffer issue.

Do you have any thoughts on the issue or how best to go about debugging the problem? Cheers Jay This might not be the case but with all the issues you have been having with using WEG, AppleALC and among other things, it might be best to wipe your system and start from scratch. It sounds like you have done to many changes for anything to actually work. This might not be the case but with all the issues you have been having with using WEG, AppleALC and among other things, it might be best to wipe your system and start from scratch. It sounds like you have done to many changes for anything to actually work. @Pavo, Two completely different systems buddy. The AppleALC issues have been on my laptop which is Intel IGPU.

And those where specifically to do with getting audio working with the Mojave beta, which is booted on a external SSD and a completely different build to the stable 10.13.6 build that i run on it. Its my daily driver so it has to be 100% stable. The WEG issue that I is on my Desktop Video Editing System running High Sierra 10.13.6. Its a very stable system used for video editing and content creation, I will not be testing Mojave beta on this system. I will only update it to Mojave when the final release is made in September and Nvidia get around to releasing web drivers for Mojave.

I might even wait until 10.14.2. However as i have migrated my other Hackingtosh systems (I have 4 in total) successfully to WEG I decided to give WEG ago on my video editing system, all i did was update Lilu to 1.2.6, remove NvidiaGraphicsFixUp and install WEG which resulted in the KP.

Removing WEG and re-installing NvidiaGraphicsFixUp and the system is fine (with Lilu 1.2.6 installed) Its not critical to get WEG running on this system right away for the reasons i mentioned above, I just thought it would be good to migrate it to WEG as you've dropped all development on NvidiaGraphicsFixUp and having WEG working on it should help when the time does come to update to Mojave. I t seemed odd that simply replacing NvidiaGraphicsFixUp with WEG did not work on this system as all the WEG install criteria have been met as such I reported it here as I would have thought many users who are currently using NvidiaGraphicsFixUp will be doing the same in anticipation of Mojave and due to NvidiaGraphicsFixUp being depreciated. Cheers Jay Update: Problem now solved, found a rouge copy of NvidiaGraphicsFixUp in Clovers Kext folder.

My bad Edited August 23 by jaymonkey. Hi, my specs are i5 2500S 8GB RAM GTX 950 1TB HDD I'm on 10.13.6, all I have now is able to boot to desktop with integrated graphics(8mb vram) not acceleration obviously. When using Latest Lilu 1.2.6 and WhatEverGreen 1.2.1 with Web drivers installed and turned on it just gives me this screen here during the part where the login should appear. I can see my cursor move in that garbled screen and blindly logging in would bring me to a garbled desktop.

(I've searched a bit on this and no it's not the Wallpaper too). Using whatevergreen doesn't seem to support clover's edid patch. Not sure if it is more of clover issue or whatevergreen, it might have something to do with clover 'inject intel' being unselected, the system failed to recognize a patched edid ('horizontalsync pulsewidth') which results in a garbled screen (on my hd4600) I can do manually inject a patched edid using properity or dsdt apporach, however I don't think hard coding it is the best way to go. I have no idea why did horizontalsync pulsewidth make such differences, but it is indeed effective. I'm not skilled enough to dig into framebuffer file and reverse engineer so I'll have to count on you talented people. Attached is my display properity file, notice the edid are different P.S. The default device id:0x0D26 from the patcher also gives me a garbled screen (much server than the one without edid patch), with unpatched edid, I can still use vnc and see a perfectly fine screen, with 0x0D26 deviceid, even vnc connected remote desktop is garbled for some reason.

Device id that worked for me is. If you need to patch DVMT pre-alloc to 32 MB then add the following to your config.plist/Devices/Properties for IGPU: framebuffer-patch-enable AQAAAA framebuffer-fbmem AACQAA framebuffer-stolenmem AAAwAQ Thanks for your help. I use IntelGraphicsDVMTFixup to fix the DMVT problem and now this kext was replaced by WhateverGreen but test failed. When i get back to the IntelGraphicsDVMTFixup and it works well with no problem. So i supposed that the WhateverGreen have problem in DVMT patch so we still need IntelGraphicsDVMTFixup to solve the DVMT problem.

Hi, I've met a problem that I the monitor which rotates 90º would not display properly about the computer boots. It can be seen that there are strange black blocks on the left screen. The image is not rotated, but the mouse moves normally. It seems that the screen is not rotated even if the system regards it as rotated screen. After I come to the preferences and set the rotation again, it becomes normal.

But if I reboot the computer, this issue would happen again. I wonder if this is a bug since whatevergreen v1.2.0.

It works well before this version. My graphic card is ASUS RX 580. Kexts: AppleALC Lilu Whatevergreen XHCI-200-series-injector USBInjectAll RealtekRTL8111 FakeSMC Edited September 1 by hguandl.

Hey, I need some help. I am dealing with a head scratcher.

So my laptop uses an AMD R9 375 (firepro w5170m)(device ID 6820, native in AMD7000Controller). And I am having some issues with ssdt patching with whatevergreen. So I am trying to inject an EDID, model name, and custom connectors because my laptop uses eDP not LVDS. On my ssdt my graphics card is at sb.pci0.peg0.pegp not sb.pci0.peg0.gfx0.

Well whenever I use whatevergreen it changes pegp to gfx0. Which I think is causing issues when I try to modify my ssdt. If I use the path sb.pci0.peg0.pegp, the model name will change to what I set it, but EDID and the connectors will not change. IOREG will say the connecter type is still 0x2 (LVDS), and the EDID is incorrect which causes low color depth for my system. If I use path sb.pci0.peg0.gfx0 nothing will apply in my patch. Also I thought maybe it's not getting my video bios. So I extracted the.rom file (62kb, so I know I need to pad at the end 2kbs of zeros) but I am unsure on how to get it in the correct format for the SSDT patch, the.rom is thousands of lines; I doubt it all goes into the SSDT patch.??

Any help would really be awesome, thanks in advance. Edited September 1 by yamahahornist. Hello, I am the owner of the motherboard socket 775 ga-ep35ds3l and AMD RX560, I get a black screen when I try to boot to the desktop in High Sierra 13.4-13.6.  Please, tell me if I can make a video card on my motherboard? Is there anyone who managed to get AMD RX560 and socket 775?

Hi, i use LILU+WEG since long time with mx RX 460 (similar to RX 560). In MB-BIOS AMD GPU should be primary. Which port do you use for monitor?

Sometimes not all ports (DVI, DP, HDMi) works out of the box, even with WEG. First try change to other port (if you can) to verify if its an port problem and WEG works in general. Also check if you have any DSDT /SSDT files in use wich belong to the GPU (for naming, setting ports etc.) can interfernence to WEG. Also check if you use RADEINIT (an clover option, i think in the gpu section) if set, disable that. Hi, i use LILU+WEG since long time with mx RX 460 (similar to RX 560).

Kprao-kgp-keyboard-layout-for-mac/readme.md At Master

In MB-BIOS AMD GPU should be primary. Which port do you use for monitor? Sometimes not all ports (DVI, DP, HDMi) works out of the box, even with WEG. First try change to other port (if you can) to verify if its an port problem and WEG works in general. Also check if you have any DSDT /SSDT files in use wich belong to the GPU (for naming, setting ports etc.) can interfernence to WEG. Also check if you use RADEINIT (an clover option, i think in the gpu section) if set, disable that. Radeon will not work on 775 socket (chipset) on system 10.13.

Whatever options you use. The help may be in replacing graphics kexts. Hi, i use LILU+WEG since long time with mx RX 460 (similar to RX 560). In MB-BIOS AMD GPU should be primary. Which port do you use for monitor?

Sometimes not all ports (DVI, DP, HDMi) works out of the box, even with WEG. First try change to other port (if you can) to verify if its an port problem and WEG works in general. Also check if you have any DSDT /SSDT files in use wich belong to the GPU (for naming, setting ports etc.) can interfernence to WEG. Also check if you use RADEINIT (an clover option, i think in the gpu section) if set, disable that. Its an newer socket for ix-3xxx Cpu.

So SLICE post about Chipset (Socket / minimum CPU type) may avoid running that AMD gpu on 775 Socket / Chipset for that type. But i think you may get answer by google about that, because then the no go for that GPU type would bei also for WIN / LINUX 775-socker- systems EDIT I started for my own interest a bit googling. Nothing real found. Lot people talk about PCIE Slot Version / UEFI BIOS vs Leagancy BIOS. In case running newer gpus. But no real 'valide' answer found. Maybe its not the 775 Socket / CPU itself, its perhaps missing UEFI BIOS and/or some PICE Slot Version (to old) problem which cam from Chipset and, because of age, no UEFI BIOS.

EDIT2: If you cold boot, do you have the BIOS Bootscreen (from mainboard)? If not then i think card has no dual bios (legancy + UEFI). EDIT3: maybe its UEFI problem, like posts here: And it may that some vendors (Saphhire) put dual bios ons some newer AMD cards. In general non UEFI system seems to be a problem.

Kprao-kgp-keyboard-layout-for-mac/readme.md At Masterbuilt

As practice shows with the installation of macOS 10.14 Mojave, official cakes from previous, previous versions of the OS sometimes help. So, I pulled out folders /System/Library/Extensions /Library/Extensions from different versions of MacOSX and uploaded on Yandex.Disk and Mediafire.

I hope someone will help. ► 10.4.11 ► 10.5.8 ► 10.6.7 ► 10.7.5 ► 10.8.5 ► 10.9.5 ► 10.10.5 ► 10.11.6 ► 10.12.6 ► 10.13.6 ► 10.14.1.

EDIT: MacOS Mojave 10.14 ONLY I didn’t test 10.14.1! The EFI folder is compatible with High Sierra. Guide to installing 10.14 Mojave on a ASUS X555L What Works: -WiFi -Sound -Graphics (Intel) What doesn't Work: -Bluetooth -NVidia Web Drivers -Battery Indicator Used Kexts: Picture Clover setup: Clover plist is downloadable in this topic.

Let's start Step one: First get a USB with 8+ GB of storage and a MacOS Mojave 10.14 installer from the AppStore. Partition the USB in a GUID style and 2 partitions, one partition HFS+ and one partition FAT32. In the FAT32 partition put the EFI Folder there. On the HFS+ partition get the MacOS Mojave.app using this command: sudo /Applications/Install macOS Mojave.app/Contents/Resources/createinstallmedia -volume /Volumes/USBNAME -applicationpath /Applications/Install macOS Mojave.app -nointeraction Lets install! Put the USB in a 3.0 port on the LEFT side of the Notebook. In the BIOS follow the default Hackintosh settings, do NOT forget to put Memory allocation to 64MB (Otherwise you won't boot) Boot into the Installer and install MacOS Mojave.

Boot into MacOS. Now your Graphics are working but your WiFi and Sound are not!

For the WiFi follow this video: Once rebooted WiFi is working! For sound get the VooDooHDA.kext and place it into /Library/Extensions Reboot once again and your sound is now working flawlessly!

My EFI Folder is downloadable config.plist EFI.zip. Hi guys, stuck on problem of switching on my TV back from off state. I have asus H270f strix mobo with i7-6700K CPU (HD530), Clover 4722 and latest whatevergreen and lilu. I installed 10.14.1 on it and it works fine. The m/b has dp, hdmi and dvi on board.

Kprao-kgp-keyboard-layout-for-mac/readme.md At Masters

I'm using dp + dphdmi adapter to connect my mac to 4k tv which I'm using as a primary monitor. This connection supports 4k@60hz and I'm happy with the detailed and sharp picture I see on my tv. The problem is that when I get out for a while then, when I come back, I see my tv turned off by timeout and when I turn it back on, I see only the black screen. The computer works, I prevented it from going to sleep. To see the picture again on my tv I have to go to another computer, then, using screen sharing, I have to connect to my computer and then I have to choose couple of times different refresh rates in System Preferences - Displays. After that I go back to my tv, see the picture and can continue to work.

I made a edid report for my tv. May be somebody knows how to use this data to make my mac to wake up the tv correct way?

Thank you, Dmitry 43UHDLCDTV.txt.zip. WhatEverGreen Support Topic.