Jump to content


Popular Content

Showing content with the highest reputation on 12/13/2018 in all areas

  1. 3 points
    TLDR, a lot of Corsair HID peripherals are now supported. I know there were other solutions like CKB-Next that got some things working but now we have a more streamlined experience. I hope this was the proper place to post this. Link below and the post it refers to. http://forum.corsair.com/v3/showthread.php?p=982647#post982647 Hi everyone, It has been a long time coming but I am happy to finally announce the beginning of our OPEN BETA for iCUE on MacOS! Link: http://downloads.corsair.com/Files/CUE/iCUE-3.10.125-release.dmg Some of you may remember that I was beta testing a macOS version of CUE2 about a year ago. Since we were planning to launch iCUE in early 2018, I made the hard decision to stop development on macOS for CUE2 because I did not want two different experiences on both platforms. We used this time to accomplish a few tasks: 1.) Ensure that almost all of our CUE2 products will be supported on the macOS platform. 2.) Complete iCUE for Windows and then port it over to macOS. 3.) Validate it for MacOS on desktop and laptop models to ensure a clean transition. The difficulty of implementing iCUE on macOS wasn’t so much the software but the firmware. Due to architectural changes, existing firmware on our devices would not properly be detected in macOS iCUE. Those who tested CUE2 would be familiar with this issue. To resolve this problem, we had to implement a new protocol for firmware. This means that most users will have to update the devices on their Windows machine first, if you have a legacy product, while users with our newest keyboard (K68 RGB and newer) can actually use their devices out of the box without any update. For reference, here are all of the devices that will support iCUE without requiring a firmware update: K68 RGB K70 RGB MK.2 SE K70 RGB MK.2/RAPIDFIRE K70 RGB MK.2 LP Strafe RGB MK.2 M65 RGB Elite M65 PRO RGB K70 RGB LUX K70 RGB RAPIDFIRE SCIMITAR PRO STRAFE RGB HARPOON RGB All VOID headsets (except Stereo) All HS headsets (except Stereo) ST100 MM800 (All versions) To prevent any potential issues with deploying firmware updates, we decided to stagger out firmware releases this time in batches for macOS compatibility. Therefore, the first batch of legacy products that will support macOS will be the following and are live already: K95 RGB PLATINUM K55 RGB K63 WIRELESS/SE DARK CORE RGB/SE Users should use iCUE (Windows) to update their hardware. You will know you’re on the proper firmware if you are on version 3.XX for the legacy devices (STRAFE MK.2 and K68 RGB will show 1.XX but already use the new protocol). For users who don’t have an access to a Windows machine, we are in the process of documenting how to do a manual firmware update with a Mac so you can do the update without iCUE. However, I advise using iCUE is the best method when possible. I hope you all enjoy iCUE on a new platform as we’ve been working on this for more than a year and a half. We will start to deploy more and more firmware updates so if your product isn’t support yet, it will be by sometime in December. If any of you have any questions, feel free to PM me anytime. And as always, thank you for your support with our CORSAIR products! Regards, James FAQ: 1.) What products are supported in iCUE for macOS? iCUE for macOS will only support HID products (keyboards, mice, headset, headset stand, and mousepads). 2.) Why does iCUE for macOS not support DIY products? We use Windows Service to control DIY products and we also use CPUID SDK to do so. Unfortunately, neither of these are compatible with macOS at this time. We are looking at alternative methods but as most people are using macbooks and mac desktops, we don’t think there is a strong enough demand yet to support DIY with users who have Hackintosh’s. However, we are carefully monitoring feedback as well as investigating how to improve the overall experience when it comes to device support. 3.) Is it possible to update firmware on iCUE macOS in the future? Yes but we have not uploaded any firmware for this platform yet. We will do so soon so we can continually monitor people’s experiences during the open beta. 4.) Is there anything missing from iCUE macOS from Windows besides device support? We currently support all the features (Actions, Lighting Effects, Surface Calibration, Performance, Hardware Playback, Surround Sound, etc.) but one known issue is OSD. We are still working on that for macOS but do not have an ETA for now. However, all the main features of iCUE supported with your peripheral are available now. 5.) Will we be able to update iCUE versions on macOS? Yes, when we deploy a new version on the mac, you’ll be prompted to update it through the software just like we do on Windows. 6.) Is there anything special I need to do in macOS? If you want key repeat enabled in macOS, you will need to enable this through the terminal. This is the command to enable press and hold: Enable: defaults write -g ApplePressAndHoldEnabled -bool true <return> Disable: defaults write -g ApplePressAndHoldEnabled -bool false <return> (Thanks Manofclay) After you enable this, you will need to restart your system. 7.) Is this an official release for macOS? No, this is just an Open Beta so we can gather bugs and feedback. However, this can be shared with anyone you desire. 8.) What version of macOS does this support? We are supporting High Sierra and newer but we recommend using the latest if possible.
  2. 2 points

    [pre-release] macOS Mojave 10.14.3

    I think I'll stay for 14.3 beta! How fast to install and to work... I do not know what they did, but in fact the speed with which the system runs is impressive!
  3. 1 point
    Being asked to add support for Realtek's Fast Ethernet PCIe NICs to my RTL8111 driver I got tired of answering the same old question again and again so that I finally decided to write a separate driver for these chips and to make a few of you guys and gals happy. As of now the driver supports the following members the RTL810X Fast Ethernet family: RTL8101E RTL8102E RTL8103E RTL8401E RTL8105E RTL8402 RTL8106E RTL8106EUS RTL8107E Here is a list of the driver's basic features: Supports Sierra (maybe El Capitan). 64 bit architecture only. Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). TCP segmentation offload under IPv4. Support for TCP/IPv6 and UDP/IPv6 checksum offload. Supports Wake on LAN. Support for Energy Efficient Ethernet (EEE) which can be disabled by setting enableEEE to NO in the drivers Info.plist without rebuild. The default is YES. The driver is published under GPLv2. Built using Xcode 4.6.3. Changelog Version 2.0.1 (2018-05-10): Fixes a problem with retrieval of the permanent MAC address on some chips. Version 2.0.0 (2017-04-04): Uses Apple's private driver interface introduced with 10.8. Adds support for the RTL8107E. Supports packet scheduling with QFQ. Adds support for flow control and EEE. Version 1.0.0 (2014-05-24): First offical release. Installation Before you install the driver you have to remove any installed driver for RTL810X. Goto /S/L/E and delete the old driver. Recreate the kernel cache. Open System Preferences and delete the corresponding network interface, e. g. en0. If you forget this step you might experience strange problems with certain Apple domains, iTunes and iCloud later. Install the new driver and recreate the kernel cache. Reboot Open System Preferences again, select Network and check if the new network interface has been created automatically or create it manually now. Configure the interface. Troubleshooting Make sure you have followed the installation instructions especially when you have issues with certain domains while the others are working fine. Use the debug version to collect log data when trying to track down problems. The kernel log messages can be retrieved with "grep kernel /var/log/system.log" in Terminal. Starting from Sierra use "log show --predicate "processID == 0" --debug" in order to retrieve kernel logs. Include the log data when asking for support or giving feedback. I'm an engineer, not a clairvoyant. Don't copy and paste large amounts of log data to your post. Create an archive with the log data and attach it to your post. In case you don't want to make your log data publicly accessible, contact me via PM and I will provide you a mail address to send it directly to me.  Check your BIOS settings. You might want to disable Network Boot and the UEFI Network Stack as these can interfere with the driver. Double check that you have removed any other Realtek kext from your system because they could prevent the driver from working properly. Delete the following files: /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist /Library/Preferences/SystemConfiguration/preferences.plist Verify your bootloader configuration, in particular the kernel flags. Avoid using npci=0x2000 or npci=0x3000. In Terminal run netstat -s in order to display network statistics. Carefully examine the data for any unusual activity like a high number of packets with bad IP header checksums, etc. In case auto-configuration of the link layer connection doesn't work it might be necessary to select the medium manually in System Preferences under Network for the interface. Use Wireshark to create a packet dump in order to collect diagnostic information. Keep in mind that there are many manufacturers of network equipment. Although Ethernet is an IEEE standard, different implementations may show different behavior causing incompatibilities. In case you are having trouble try a different switch or a different cable. Getting the driver There is a prebuilt binary in the Download section of this site: http://www.insanelymac.com/forum/files/file/259-realtekrtl8100-binary/ The source code can be found on Github: https://github.com/Mieze/RealtekRTL8100 Mieze
  4. 1 point

    Version 10.14.x


    Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+ partition. To use those patched files you must follow HowTo to create an USB installer. You can't just run the app downloaded from Mac App Store. The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.14 HFS Firmware check by crazybirdy. What is this patched OSInstaller doing? 1. Patch the MBR check, allow macOS 10.14 installation on MBR partition. 2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware". 3. Patch to stop auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.14. 4. This patched MBR OSInstaller will never convert to APFS, and will always install as HFS+ partition. 5. This patched MBR OSInstaller method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery). No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch. What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method? As the following.... 1. createinstallmedia method, needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format. 2. MBR-Manual-Method (same as 10.12), install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format. We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12. We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now. Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so. It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version. 3. MBR-Automatic-Method (new for 10.13+), install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format. It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version. How to make 10.14 installer for MBR (MBR-Manual-Method)? Just use MBR-EasyInstallerMaker to make installer, it works with both MBR and GPT. Read HowTo inside the dmg first, same as 10.12. Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave? Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store? Read HowTo Q/A Q7. How to update 10.14.x combo-update to MBR and GPT with installScript directly? How to make 10.14 installer for MBR (MBR-Automatic-Method)? Just use 14MBRinstallerMaker to make installer, it works with both MBR and GPT. Read HowTo inside the dmg first, sam as 10.13. Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave? Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store? Read HowTo Q/A Q9. How to update 10.14.x combo-update to MBR and GPT with installScript directly? And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist. Q6. How to download the full installer app via swscan.apple.com, instead of App Store? A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_1014fullapp to download the full installer app via swscan.apple.com.
  5. 1 point
    Hmm... I did not think of it, I currently have the High Sierra 10.13.3 installed and functional with the HD 7770, however I believe the problem is in my UEFI BIOS, my motherboard ends up not supporting uefi bios, I will having to be absent in the project until there is a solution hahaha, thanks for the tips!
  6. 1 point
    rimetti il tuo config,rimuovi usbinjectall, sostituisci ssdt SSDT-4-A M I.aml.zip Non perdi nulla con aggiornamenti...anzi sei in linea con apple riguardo le usb per la mappatura se vuoi approfondire c'è la mia guida
  7. 1 point

    Clover Themes

    @Badruzeus hi, Thanks, theme Mojave OK.
  8. 1 point
    CLOVER.zip Nvidia Web Driver, use it https://olarila.com/files/Utils/nvidia-update.command.zip
  9. 1 point

    Hackintool v2.0.4

    @headkaze, really amazing app
  10. 1 point
    prova SSDT-4-A M I.aml 2.zip
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up