Jump to content
Mieze

IntelMausiEthernet.kext for Intel onboard LAN

896 posts in this topic

Recommended Posts

At the moment I have not worked on my MB intel DP55WB when i try Mavericks and it generates this error. I need a hand, thank you.

post-203539-0-28821900-1484758605_thumb.png

Share this post


Link to post
Share on other sites
Advertisement

At the moment I have not worked on my MB intel DP55WB when i try Mavericks and it generates this error. I need a hand, thank you.

The UEFI network stack or some kind of remote management software is still in control of the NIC preventing the driver from taking control. Check you UEFI settings and disable it.

 

Mieze

Share this post


Link to post
Share on other sites

Dp55WB isn't uefi

 

Sent from my SM-G930F using Tapatalk

It doesn't make a difference if it's UEFI or BIOS, at least with regard to the NIC.

 

Mieze

Share this post


Link to post
Share on other sites

I have strange issue. I have an intel Nic flashed with AppleDevID so there was no need to use your kext. When I encountered issues lately( It hink its since 10.12.3) I turned on the Nic of the motherboard which is supported by your kext and is also working. The issue I encounter is that those Nics both initiates very slow. I was indeed thinking it was caused by DHCP at my router so I decided to make a new location in the network settings with a fixed IP address and removed the automatic profile. After a reboot (my network drives are mounted) I receive errors that there is no network. I see NIC as disconnected and with location profile automatic again. After a few sec it becomes green and its working normal. This is an issue cause with different SMBIOS types (MacPro5,1|iMac 14&17 etc). Any ideas?

Share this post


Link to post
Share on other sites

I'm only able to get 100baseTX speed on an i219. If I go into the network options and select "Advanced", and "Hardware", then change the settings from "Automatic" to "Manual" to force 1000baseTX, the network will not connect.

 

Is there any established fix?

Share this post


Link to post
Share on other sites

I'm only able to get 100baseTX speed on an i219. If I go into the network options and select "Advanced", and "Hardware", then change the settings from "Automatic" to "Manual" to force 1000baseTX, the network will not connect.

 

Is there any established fix?

Yes, fix your hardware as this is a hardware issue.

 

Mieze

Share this post


Link to post
Share on other sites

Hi Mieze

 

Could you add Intel i211 Gigabit Connection into the kext? I tried all the methods I can find, nothing work

 

THX

I'm sorry but this is impossible because I211 has a completely different device architecture. Basically the I211 is a stripped down low cost version of the I210 which lacks support for advanced features like multiple transmit queues.

 

Mieze  :cat:

Share this post


Link to post
Share on other sites

Hi, I get Kernel Panic. Shutdown and restart. In the Apple log appear:

 

com.insanelymac.IntelMausiEthernet(2.2.1d1)[EB3195B7-9B0D-35C9-B97F-724349AEF72C]@0xffffff7f82fed000->0xffffff7f83000fff

 

Do you have experience with this? can you recommend me other version?

 

Sierra 10.12.4

Maximus Hero VIII

IntelMausiEthernet.kext Version March 21

 

Thank you.

Share this post


Link to post
Share on other sites

Hi, I get Kernel Panic. Shutdown and restart. In the Apple log appear:

 

com.insanelymac.IntelMausiEthernet(2.2.1d1)[EB3195B7-9B0D-35C9-B97F-724349AEF72C]@0xffffff7f82fed000->0xffffff7f83000fff

 

Do you have experience with this? can you recommend me other version?

 

Sierra 10.12.4

Maximus Hero VIII

IntelMausiEthernet.kext Version March 21

 

Thank you.

First of all, why are you using a development version instead of the official release?

 

Second, kernel panics are usually the result of a messed up system, at least I haven't seen a reported kernel panic which could be tracked down to a driver bug for the last 2 years so that it's unlikely that there is a problem with the driver. Try to reset system caches, in case it doesn't help you might want to restore to a known working state from a Time Machine backup or reinstall.

 

Mieze

Share this post


Link to post
Share on other sites

 

On I217V, Asrock MB:

 

Latest stable version (2.2.0) loses network after some sleep/wakeup cycles. I can recover connectivity by disabling/reenabling the interface in Network Prefs, but doing it 3 times a day hurts.

 

Version 2.1.0d3 doesn't suffer from this, but network goes down and autorecovers under high transfer load. Even after applying the SSDT patch.

 

In the end, I've downgraded to 2.1.0d3 as I find it less obstructive for daily usage. I haven't tested versions between 2.1.0d3 and 2.2.0

Share this post


Link to post
Share on other sites

I really ignore wich is the difference between development or official.

Don't take it personal but I really hate ignorance as it's stealing my time, in particular when users are asking for help without having their homework done. Development versions are only for testing, they still contain bugs which have been resolved in the official release and it's really wasted time to deal with things over and over again. I'm spending my spare time in order to update and support the driver but I might rethink my commitment to the project in case I get tired because of the lack of cooperation from users.

 

On I217V, Asrock MB:

 

Latest stable version (2.2.0) loses network after some sleep/wakeup cycles. I can recover connectivity by disabling/reenabling the interface in Network Prefs, but doing it 3 times a day hurts.

 

Version 2.1.0d3 doesn't suffer from this, but network goes down and autorecovers under high transfer load. Even after applying the SSDT patch.

 

In the end, I've downgraded to 2.1.0d3 as I find it less obstructive for daily usage. I haven't tested versions between 2.1.0d3 and 2.2.0

 

Have you tried to disable WoL in System Preferences -> Network? You might also want to select the medium manually (one without EEE) as it seems to help sometimes.

 

By the way, version 2.1.0d3 suffers from data corruption when the link gets lost.

 

In case you want further assistance, please send me your kernel logs showing one of these incidents.

 

Mieze  :cat:

 

PS: I'm working on an update for the driver to support Kabylake and maybe also to add support for jumbo frames.

Share this post


Link to post
Share on other sites

After receiving positive feedback from crashmaster4999 (Thank you for your priceless support!) who ran first tests, I just wanted to give you a chance to participate in testing. Besides jumbo frame support, I also added initial support for the new I219 chips found on Kabylake boards. Source code can be found on GitHub.

 

In case you experience any problems, please report back with kernel logs showing the issue.

 

Good luck!

 

Mieze  :cat:

IntelMausiEthernet-V2.3.0d0.zip

Share this post


Link to post
Share on other sites

After receiving positive feedback from crashmaster4999 (Thank you for your priceless support!) who ran first tests, I just wanted to give you a chance to participate in testing. Besides jumbo frame support, I also added initial support for the new I219 chips found on Kabylake boards. Source code can be found on GitHub.

 

In case you experience any problems, please report back with kernel logs showing the issue.

 

Good luck!

 

Mieze  :cat:

 

So, Mieze:

 

I would like to ask for your help.  I have upgraded to 10.12.4, but none of wired ethernet cards are working.   That includes the internal port, which is an Intel I218 chip, and an add-in card (Realtek 811 chip).  I've tried drivers from various sources, including your Intel drivers (September 2016 and March 2017 releases), Apple1000e, AppleIGB, and for the Realtek card, several different Realtek drivers.  Nothing works.  Clover version is r4049

 

None of the cards will accept DHCP. You can manually address them, and they do respond to a self ping, but they cannot ping anywhere else. Not to my local router, (or any local IP addresses), and not to the Internet.
 
Most everything else works, including Wifi and Bluetooth (BCM4360 PCIe card).
 
This shows that the kext is loading: 
$ kextstat | grep Mausi
 
64 0 0xffffff7f83ac3000 0x24000 0x24000 com.insanelymac.IntelMausiEthernet (2.2.1) 43B3C3B1-E032-3C2B-8598-320889964F57 <53 12 5 4 3 1>
 
Typical Ping response (no matter what card/chip is used, no matter what driver is used):
ping 8.8.8.8
 
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
Request timeout for icmp_seq 0
ping: sendto: No route to host
Request timeout for icmp_seq 1
ping: sendto: No route to host
Request timeout for icmp_seq 2
ping: sendto: No route to host
Request timeout for icmp_seq 3
ping: sendto: No route to host
 
(but adding a default route doesn't work either, as the route shows as already added (or the Wifi card wouldn't be able to get to the Internet).
 
I did try deleting all of the network interfaces and the associated networkininterfaces plist, rebooting and that didn't work either.
 
my hardware: Asus X99-A II, 64 GB of DDR4 RAM, NVMe Samsung drive, GTX 980 TI with the latest drivers from NVidia, for 10.12.4.
 
Your driver worked with my internal Ethernet chip on 10.12.3, but I have some reasons for upgrading to 10.12.4 (GTX 1080 support is one, for instance).
 
I appreciate how valuable your time is.  I hope I am not wasting it with this post.
 
Thanks!

Share this post


Link to post
Share on other sites

FIXED!

10.12.4 has some new features that can cause trouble with your build. One is that you need a newer copy of Clover to boot with (I used r4049). The other is that I had a lot of trouble with Ethernet drivers that had worked fine with 10.12.3.

Fortunately though, I was on insanelymac, and Mieze had posted a new version of his IntelMausi Ethernet driver, and it worked!!

Version is: IntelMausiEthernet-V2.3.0d0      

 

Thank you, Mieze!

Share this post


Link to post
Share on other sites

After receiving positive feedback from crashmaster4999 (Thank you for your priceless support!) who ran first tests, I just wanted to give you a chance to participate in testing. Besides jumbo frame support, I also added initial support for the new I219 chips found on Kabylake boards. Source code can be found on GitHub.

 

In case you experience any problems, please report back with kernel logs showing the issue.

 

Good luck!

 

Mieze  :cat:

I want to thank you for your hard work to bring kext for everyone.

Share this post


Link to post
Share on other sites

 

FIXED!

 

10.12.4 has some new features that can cause trouble with your build. One is that you need a newer copy of Clover to boot with (I used r4049). The other is that I had a lot of trouble with Ethernet drivers that had worked fine with 10.12.3.

 

Fortunately though, I was on insanelymac, and Mieze had posted a new version of his IntelMausi Ethernet driver, and it worked!!

 

Version is: IntelMausiEthernet-V2.3.0d0      

 

Congratulations for fixing the issue but I can definitely rule out, that it was the new driver version which solved the problem. Neither Apple changed the driver interface in 10.12.4, nor did I change support for the I218 in the new version and I can confirm that version 2.2.1 is working perfectly with the I218. Version 2.3.0d0 of IntelMausiEthernet only adds support for Kabylake and jumbo frames, that's all. You probably had a messed up system (system caches, network configuration or something like that) which has been fixed by the installation procedure.

 

Mieze

Share this post


Link to post
Share on other sites

Danke Mieze! :-)

 

I just successfully installed my first Hackintosh (Gigabyte Z170X-Designare mobo) and used IntelMausiEthernet v2.2.0 with [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] and I get Ethernet connectivity!

 

Unfortunately I only get 50MB/s to our NAS, other machines with the same connections get full gigabit speed. Any clue what I can do to get full gigabit speed?

 

Best,

Chris

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   1 member

  • Similar Content

    • By Mieze
      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.   Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      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
    • By Mieze
      A New Driver for Realtek RTL8111
       
      Due to the lack of an OS X driver that makes use of the advanced features of the Realtek RTL81111/8168 series I started a new project with the aim to create a state of the art driver that gets the most out of those NICs which can be found on virtually any cheap board on the market today. Based on Realtek's Linux driver (version 8.035.0) I have written a driver that is optimized for performance while making efficient use of system resources and keeping the CPU usage down under heavy load.

      Key Features of the Driver
      Supports Realtek RTL8111/8168 B/C/D/E/F/G found on recent boards. 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. Fully optimized for Mountain Lion (64bit architecture) but should work with Lion too. As of now there is no support for Snow Leopard but it can be added if someone will create the necessary patches. 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.  
      Limitations
      As checksum offload doesn't work with jumbo frames they are currently unsupported and will definitely never be. No support for 32bit kernels.  
      Installation
      Before you install the driver you have to remove any installed driver for RTL8111/8168.
      Goto /S/L/E and delete the old driver (Lnx2mac, AppleRealtekRTL8169, etc.). 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. Reboot. Install the new driver and recreate the kernel cache. I recommend to use Kext Wizard or a similar utility for the installation. 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.  
      Help - I'm getting kernel panics!
      Well, before you start complaining about bugs after you upgraded macOS and ask me to publish a driver update, you should first try to resolve the issue on your own by cleaning the system caches.
      As the driver uses macOS's private network driver interface, which is supposed to be used by Apple provided drivers only, you might run into problems after an OS update because the linker may fail to recognize that IONetworking.kext has been updated and that the driver needs to be linked against the new version (Apple provided drivers avoid this problem because they are always updated together with IONetworking.kext). As a result, the linking process produces garbage and the driver may call arbitrary code when trying to call functions from IONetworking.kext. This usually results in unpredicted behavior or a kernel panic. In order to recover from such a situation, you should clean the System Caches forcing the linker to recreate it's caches:
      Delete all the files in /System/Library/Caches and it's subdirectories but leave the directories and the symbolic links intact. This is very important! Reboot. Recreate the kernel cache. Reboot again.  
      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 found in /var/log/system.log. For Sierra and above 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. 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. 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.  
      FAQ
      How can I retrieve the kernel logs? In Terminal type "grep kernel /var/log/system.log". I want to disable Energy Efficient Ethernet (EEE) but I don't know how? Take a look at the driver's Info.plist file. There you will find an option named <key>enableEEE</key>. Change its value from <true/> to <false/>. Don't forget to recreate the kernel cache after changing the value. WoL from S5 doesn't work with this driver but under Windows it's working. Is this a driver bug? No it isn't, the driver is working as it should because OS X doesn't support WoL from S5.  
      Current status
      The driver has been successfully tested under 10.8.x and 10.9 with the B, C, D, E, F and G versions of the RTL8111/8168 and is known to work stable on these devices.  
      Changelog
      Version 2.2.2 (2018-01-21) Force ASPM state to disabled/enabled according to the config parameter setting. Requires 10.12 or newer. Version 2.2.1 (2016-03-12): Updated underlying linux sources from Realtek to 8.041.00. Added support for RTL8111H. Implemented Apple’s polled receive driver model (RXPOLL). Requires 10.11 or newer. Support for older versions of OS X has been dropped. Version 2.0.0 (2015-06-21): Uses Apple's private driver interface introduced with 10.8. Supports packet scheduling with QFQ. Please note that 2.0.0 is identical to 2.0.0d2. Only the version number has changed. Version 1.2.3 (2014-08-23): Reworked TSO4 and added support for TSO6. Version 1.2.2 (2014-08-44): Added an option to disable Active State Power Management (ASPM, default disabled) as ASPM seems to result in unstable operation of some chipsets. Resolved a problem with Link Aggregation after reboot. Added a workaround for the multicast filter bug of chipset 17 (RTL8111F) which prevented Bonjour from working properly Version 1.2.0 (2014-04-24): Updated underlying linux sources from Realtek to 8.037.00. Improved interrupt mitigate to use a less aggressive value for 10/100 MBit connections. Version 1.1.3 (2013-11-29): Improved transmit queue handling made it possible to reduce CPU load during packet transmission. Improved deadlock detection logic in order to avoid false positives due to lost interrupts. Version 1.1.2 (2013-08-03): Improved SMB performance in certain configurations. Faster browsing of large shares. Version 1.1.0 (2013-06-08): Support for TCP/IPv6 and UDP/IPv6 checksum offload added (can be disabled in Info.plist). Maximum size of the scatter-gather-list has been increased from 24 to 40 segments to resolve performance issues with TSO4 when offloading large packets which are highly fragmented. TSO4 can be disabled in Info.plist without rebuild. Statistics gathering has been improved to deliver more detailed information (resource shortages, transmitter resets, transmitter interrupt count). The interrupt mitigate settings has been changed to improve performance with SMB and to reduce CPU load. Configuration option added to allow for user defined interrupt mitigate settings without rebuild. Version 1.0.4 (2013-05-04): Moved setLinkStatus(kIONetworkLinkValid) from start() to enable(). Cleaned up getDescCommand(). Version 1.0.3 (2013-04-25): The issue after a reboot from Windows has been eliminated. Version 1.0.2 (2013-04-22): Added support for rx checksum offload of TCP and UDP over IPv6. Version 1.0.1 (2013-03-31): Improved behavior when rx checksum offload isn't working properly. Adds the chipset's model name to IORegistry so that it will show up in System Profiler.  
      Known Issues
      There are still performance problems with regard to SMB in certain configurations. My tests indicate that Apple's Broadcom driver shows the same behavior with those configurations. Obviously it's a more general problem that is not limited to my driver. WoL does not work in certain configurations. Old systems with 3 and 4 series chipsets exhibit performance issues in recent versions of macOS because there is no optimized power management for these systems in macOS anymore as Apple dropped support for the underlying hardware a long time ago. In case you are affected, please upgrade your hardware or find an alternative solution because I have no plans for a workaround. Sorry, but I don't think that it's worth the effort.  
      Getting the driver
      The source code can be found here: https://github.com/M...driver_for_OS_X There is also a pre-build binary for Mavericks and Yosemite: http://www.insanelym...n-and-wireless/  
      Building from Source
      I'm using XCode 4.6.3 for development. You can get a free copy of XCode after becoming a member of the Apple developer program. The free membership is sufficient in order to get access to development tools and documentation.
    • By End3rPower50
      Hi, i've installed on my pc MacOS Mojave but after installation my pc, sometimes, crash giving kernel panic.
      I came to the conclusion that it is a random kernel panic because sometimes it starting up and other times it isn't starting up
       
      My PC:
      CPU: Intel i7 6500U
      LAN: RTL8100
      Wi-Fi & Bluetooth: Dell DW1820A
      USB 3.1
       
      CLOVER.zip
    • By Angelo_
      Hi, I followed the rehabman guide (linked in the vanilla guide on the side of r/Hackintosh, not sure if I can link it) for laptops for my yoga 730ILW13 with an 8265u, Conexant 11870, 8gb of ram, 13.3" fhd and I found that upon booting the installer usb I get this weird issue where the screen displays what it should but the screen is incredibly dim (though it was off before using a flashlight on it) and it flashes every few seconds for a few milliseconds to the correct brightness, I used the plist for hd615-650 (including my 620), not quite sure what could be the culprit, first time hackintoshing a laptop so it might be a stupid brightness kext I forgot but didn't find any in that post or in this forum :c 
      Attached the clover zip so that anyone with more experience than me might give an idea in what could be a way to fix this.
      Thank you in advance 
       
       
       
      CLOVER.zip
    • By Bahaa
      Need help here
      My graphic card is detached 7mb
      and I try a lot of solution and no one work 
      can any one help
       

×