Jump to content
Mieze

IntelMausiEthernet.kext for Intel onboard LAN

896 posts in this topic

Recommended Posts

Provided the BIOS updates also contain a ME firmware update, have you chosen to update the ME firmware too while installing the BIOS update?

 

I don't think that a Lilu plugin is causing the driver failure, at least I have no reason to assume it might be but, as not all of them are open source, it's hard to rule out completely.

 

Please post an IOReg dump. Use version 3.0.2 of IORegistryExplorer to create the dump.

 

Mieze

 

dump attached

iMac.zip

Share this post


Link to post
Share on other sites
Advertisement

@Mieze

May be you already know this, may be no

LAN Disable register A0h, bit0=1 -> disable LAN controller

Is it causing such error?

Share this post


Link to post
Share on other sites

@Mieze

May be you already know this, may be no

LAN Disable register A0h, bit0=1 -> disable LAN controller

Is it causing such error?

 

The driver fails with "Failed to get adapter data with error -3." which means that the NIC's flash region isn't mapped but I have no idea why.  :unsure:

 

Mieze

 

EDIT: Have you enabled FixRegions in your Clover config file?

Edited by Mieze

Share this post


Link to post
Share on other sites

The driver fails with "Failed to get adapter data with error -3." which means that the NIC's flash region isn't mapped but I have no idea why.  :unsure:

 

Mieze

 

EDIT: Have you enabled FixRegions in your Clover config file?

I blocked in the BIOS the option "IOAPIC 24-119 Entries" error was - "failed to get adapter data with error -2"

Share this post


Link to post
Share on other sites

I blocked in the BIOS the option "IOAPIC 24-119 Entries" error was - "failed to get adapter data with error -2"

The screenshot you posted yesterday shows error -3 but error -2 means that there is a problem with the PHY which is most likely still under control of the management engine (ME). 

Share this post


Link to post
Share on other sites

There is no need to make anything because you can use the debug version of the driver as it logs such events in detail. If there was a problem with link state detection, you should find some related log messages in the kernel logs when you plug/unplug the cable.

 

Mieze

 

@Mieze

I tried to trace the process of plug and unplugged cable and found that 'Cable Unplugged' is caused by the following code:
IntelMausiEthernet.cpp
....
bool IntelMausi::checkForDeadlock()
{
.
.
.
    if ((txDescDoneCount == txDescDoneLast) && (txNumFreeDesc < kNumTxDesc)) {        // <====This condition
        if (++deadlockWarn >= kTxDeadlockTreshhold) {
            mbuf_t m = txBufArray[txDirtyIndex].mbuf;
            UInt32 pktSize;
            UInt16 i, index;
            UInt16 stalledIndex = txDirtyIndex;
            //UInt8 data;
.
.
.
 
 
So I commented above code, the status of the interface is no longer toggle between 'Cable Unplugged' and 'Not Connected', but still can not send / receive data. It seems that the bottom cause is that the "initialization" process triggered by the plug of the network cable is not intact?
In addition, I found that let the laptop sleep and then wake up when the status of the interface toggle between 'Cable Unplugged' and 'Not Connected', the network will work fine.

Share this post


Link to post
Share on other sites

 

@Mieze

I tried to trace the process of plug and unplugged cable and found that 'Cable Unplugged' is caused by the following code:
IntelMausiEthernet.cpp
....
bool IntelMausi::checkForDeadlock()
{
.
.
.
    if ((txDescDoneCount == txDescDoneLast) && (txNumFreeDesc < kNumTxDesc)) {        // <====This condition
        if (++deadlockWarn >= kTxDeadlockTreshhold) {
            mbuf_t m = txBufArray[txDirtyIndex].mbuf;
            UInt32 pktSize;
            UInt16 i, index;
            UInt16 stalledIndex = txDirtyIndex;
            //UInt8 data;
.
.
.
 
 
So I commented above code, the status of the interface is no longer toggle between 'Cable Unplugged' and 'Not Connected', but still can not send / receive data. It seems that the bottom cause is that the "initialization" process triggered by the plug of the network cable is not intact?
In addition, I found that let the laptop sleep and then wake up when the status of the interface toggle between 'Cable Unplugged' and 'Not Connected', the network will work fine.

 

Just for your information: the code you commented out is part of the watchdog which causes a chip reset when packet transmission hangs. Really bad idea!

 

Mieze

Share this post


Link to post
Share on other sites

Hey,

I have an Intel I219V2 Dual Ethernet board, the Gigabyte Z270N-WiFi. Using your driver, only one port works, both should work, as they aren't different chipsets, right?

 

I had a system cleanup courtesy of Pavo, and while trying to figure it out, my previous fix, which was basically, two kexts (AppleIGB), no longer works. IORegistryExplorer only shows en0. If I plug the cable in the other port and reboot into Windows, it's functional, in the chat they thought of network configuration issues and suggested an OS reinstall, also to clean everything up OS wise that may have been done, but from the first day I managed to boot with ethernet, the second port never worked. Any ideas on where to start looking? The lights at the back even light up, but no activity.

Share this post


Link to post
Share on other sites

Hey,

I have an Intel I219V2 Dual Ethernet board, the Gigabyte Z270N-WiFi. Using your driver, only one port works, both should work, as they aren't different chipsets, right?

 

I had a system cleanup courtesy of Pavo, and while trying to figure it out, my previous fix, which was basically, two kexts (AppleIGB), no longer works. IORegistryExplorer only shows en0. If I plug the cable in the other port and reboot into Windows, it's functional, in the chat they thought of network configuration issues and suggested an OS reinstall, also to clean everything up OS wise that may have been done, but from the first day I managed to boot with ethernet, the second port never worked. Any ideas on where to start looking? The lights at the back even light up, but no activity.

You are wrong, on your board there is only one I219V2 (two would be impossible) because it's just a PHY which is combined with the MAC integrated into the Z270 chipset and only this ethernet adapter is supported by the driver. The other NIC must be something else, for example an I210 or I211 which isn't supported. Sorry!

 

Mieze

Share this post


Link to post
Share on other sites

You are wrong, on your board there is only one I219V2 (two would be impossible) because it's just a PHY which is combined with the MAC integrated into the Z270 chipset and only this ethernet adapter is supported by the driver. The other NIC must be something else, for example an I210 or I211 which isn't supported. Sorry!

 

Mieze

Mieze actually his system only has Intel I219V2 with 2 physical ports, have looked at his system manual.

Share this post


Link to post
Share on other sites

Mieze actually his system only has Intel I219V2 with 2 physical ports, have looked at his system manual.

No, the manual is wrong because the chipsets only have 1 integrated MAC. It's impossible to build a board with two I219s.

 

Mieze

Share this post


Link to post
Share on other sites

Guess the only way to tell is look in windows and see what each ethernet port is.

Please take a look at the chipset's datasheet and you will see that I'm right. I219 is not a full NIC but just a PHY which must be combined with the chipsets's integrated MAC and there is only one integrated MAC in the chipsets.

 

Mieze

Share this post


Link to post
Share on other sites

Hi MaLd0n says maybe you can help me:

"u can post problem in Mieze's topic, She is amazin' and developed amazin' drivers.
I no have more idea. ;)"

alladyn21, on 23 Dec 2017 - 9:36 PM, said:
buu 
 
the same situation...
2017-12-23 21:34:17.980132+0100  localhost kernel[0]: (AppleACPIPlatform) Wake reason: PEG1 PEGP PEG2 PEGP PXSX RP10 PXSX RP11 PXSX RP12 PXSX RP13 PXSX RP02 PXSX RP04 PXSX RP05 PXSX RP06 PXSX RP07 PXSX RP08 PXSX P

When wol is off all is ok

I have z170 pro gaming and intel i210 in pecie because (onboard lan don't have wol in osx drivers) when wol is on (wake from pcie) pc itself wake up after a one second of sleep :(

Share this post


Link to post
Share on other sites

I have z170 pro gaming and intel i210 in pecie because (onboard lan don't have wol in osx drivers) when wol is on (wake from pcie) pc itself wake up after a one second of sleep :(

What exactly are you talking about? The onboard I219V or the I210 add-in card? Only the I219V is controlled by my driver while the I210 uses a native driver from Apple.

 

By the way, you should be aware of the fact that macOS only supports WoL from S3. WoL from S5 isn't supported at all and that's the reason why my driver doesn't support it. Also keep in mind that the wakeup event settings in BIOS refer to WoL from S5.

 

Mieze

Share this post


Link to post
Share on other sites

So I will not be able to run the wol on i210 or the i219v ethernet card. It's just that the computer wakes up and I do not know why this is happening. If I turn off wol everything is ok. But when wol is on i dont have sleep.

So I will not be able to run the volt on one or the other ethernet card

Share this post


Link to post
Share on other sites

@Mieze

I encounter a problem with the driver v2.3.

When I send 1Gb file to another Mac by local LAN then the adapter stalls/freezes. I see internet stop working too.

Then I enter sleep and wake again. This helps and Safari works again.

So this is a problem with IntelMausi.

0:102  0:000  PCI (00|00:1F.06) : 8086 15B8 class=020000

What should I do? Make a dump?

Share this post


Link to post
Share on other sites

@Mieze

I encounter a problem with the driver v2.3.

When I send 1Gb file to another Mac by local LAN then the adapter stalls/freezes. I see internet stop working too.

Then I enter sleep and wake again. This helps and Safari works again.

So this is a problem with IntelMausi.

0:102  0:000  PCI (00|00:1F.06) : 8086 15B8 class=020000

What should I do? Make a dump?

Did you enable TSO? In case of yes, I know why it freezes because there is a well known hardware issue which causes trouble with OS X's transmit packet buffer layout.

 

Mieze

Share this post


Link to post
Share on other sites

All is fine. I just has loaded 2.2 version from cache while 2.3 version was bad compiled (with 10.13SDK while I am on 10.12 system).

I recompiled 2.3 with 10.12SDK and copied 400Mb file during few seconds.

Great!

Ethernet [IntelMausi]: TCP/IPv4 segmentation offload disabled.
..
Ethernet [IntelMausi]: Link up on en0, 100-Megabit, Full-duplex, Rx/Tx flow-control

Share this post


Link to post
Share on other sites

First of all, happy new year to all of you! I just wanted to let you know that I started to work on an update for the driver in order to support the Coffee Lake generation of I219.

 

Mieze

Oh yeah, that's a good news, and I hope my problem will be repaired accidentally in this update. :P

Share this post


Link to post
Share on other sites

Anybody out there with a Coffee Lake hackintosh equipped with an I219 NIC who is willing to test the first development version 2.4.0d0 which adds support for Coffee Lake? In case you are interested, please send me a PM!

 

Mieze

Share this post


Link to post
Share on other sites

This is the first test build of version 2.4.0 of IntelMausiEthernet which updates the underlying Linux sources and adds official support for Coffee Lake. All users are encouraged to test it thoroughly. Although I tested it successfully on my I218V, you should keep in mind that this is work in progress which can't be expected to be 100% stable. In case things go wrong and you end up with a kernel panic, you should be prepared to recover your system from that situation.

 

Here is a short list of things to test:

1.) Boot

2.) IP address acquisition via DHCP.

3.) Cable unplug and replug. (Test several times!)

4.) Sleep/wake cycles (Test several times!).

 

In any case, please report back with attached kernel logs of the test run including the boot sequence. In case you need instructions how to retrieve them, please refer to post#1 of the driver's thread in the forum.

 

Good luck!

 

Mieze

IntelMausiEthernet-V2.4.0d0.zip

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   0 members

    No registered users viewing this page.

  • Similar Content

    • 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
       

    • By Angelo_
      Just recently installed Mojave on my yoga 730(i5-8250u, 8gb of ram and 1080p 13.3" touchscreen) and got many features working, now the only issues are that my igpu is shown as only 7mb(and not metal capable, not sure whether it is or not) even tho I should've changed it from 5917 to 5916 (added both EFI folder and send me), the screen is shown as a 30.5" in system information and the cpu even tho I extracted the ssdt for it with ssdtPRGen.sh and appleintelinfo.kext to get low frequency info (ssdt was done with info 15,400,1600,3400 so it should go between 16-3400mhz and down to 400 in idle), idk what is wrong with my installation, can you guys help me or linke me something to fix those issues?
       
      Ps thunderbolt shows as no device found, is it regular for hackintoshes to be that way or do I need something for that too? Laptop has 2 tb3 ports as x4 pcie 3
      EFI.zip
      Send me Angeloss-MacBook-Pro.zip
    • By Gymnae
      Introduction
      The H370 chipset powers 8th generation Intel Core-i CPUs. Even though the name H370 rings comparable to Z370, the H370 is based on newer silicon. This it also requires some new approaches compared to the Z370. An example would be on-die USB 3.1 and WiFi support.
       
      Since this guide is not a "hold-your-hand-every-step" guide, I assume you know:
      Clover installation and configuration How to create an install medium for MacOS Access and configure the BIOS Have heard of ACPI patching (I'm a newb at this myself)  
      What works
      Sleep (via DSDT edits and emulated NVRAM) On-board Audio (via AppleALC and native AppleHDA) Native power management (without any kext or patch) All USB ports (and only those present are active) iGPU for both acceleration and display dGPU (I'm running an Nvidia GTX 1080)  
      Untested
      NIC --> I'm using WiFi only  
      What doesn't work
      Native NVRAM via AptioMemoryFix.efi DMVT Pre-alloc higher than 64MB (but not necessary)  
      Community additions
      User @Panzerschiffe added a helpful post, altering this guide for user with AMD cards and not needing on-board sound.
      He also runs Mojave, which I don't run yet.
       
       
      Changes to the guide:
      22.5.18: Added SSDT hot-patching to enable sleep, replacing DSDT static patching as an alternative.
      23.5.18: Add iMac18,1 as alternative SMBIOS config for those relying on the iGPU for output
      25.6.18: Added update info
      28.8.18: Small changes for clarity, changed info for afps loading & updated USB patch for 13.6
      04.10.18: Update to Mojave will come once Mojave is more mature
      02.12.18: Removed unnecessary patches, fakepciid and audio patch method & linked to AMD post & added whatevergreen.kext as replacement for previous GPU kexts
      02.03.19: Removed unnecessary fakeid and ig_platform_id injections, ACPI patches - this is all handled by whatevergreen & lilu. In testing is a Framebuffer patch, see this post.
      04.03.19: Added Germany keyboard layout and updated pre-patched DSDT.aml removed DSDT patching
       
       
      1. Installation
      This guide heavy inspired by the work of /u/corpnewt of /r/hackintosh and his (sorta) Vanilla guide
       
      1.1 Create the install media for MacOS
      Follow this, if you are using a Mac to start off with. If you are totally new to MacOS, then please check the basic guide Creation of an installer media in windows or linux
       
      1.2 Install Clover on the install media
      Using the Clover installer, ensure you are installing to the USB medium you are using for the installer.
      Chose the following options, leaving the others on default: 
       
      UEFI driver: AptioMemoryFix UEFI driver: ApfsDriverLoader UEFI booting only Install to ESP  
      You have to get your hands on an apfs.efi. A google search can help, or extracting it from the Installer package. Make sure you procure a version matching the MacOS version you are about to install. Place the apfs.efi in drivers64UEFI.
       
      1.2 Adjust the config.plist for the installer
      You can use the config.plist attached as a guideline, but take a look at it before and at least adjust the SMBIOS - otherwise it won't boot.
      Attention: The attached plist contains audio patches introduced by a post-install step. If you run into problems, you might remove those. It also contains a manual slide value, which should normally not be needed, but works fine for me. It is also tuned for usage with an Nvidia Pascal dGPU as main GPU.
       
      The config you create now should serve you nicely for install and running the system.
       
      Take care of adding the following basics:
      SMBIOS: iMac18,3 - You can generate a serial number via Clover Configurator. The creation of a proper SMBIOS is covered in many guides to good extend Note: If you aim at using the iGPU for output, a user reported that iMac18,1 works better - since iMac18,3 produces severe flicker. I'm now also testing 18,1 Look at the graphics section and adjust the injection for Intel to your situation  
      Fixes

      Patches

      Devices

      Graphics
      Important:
      Change 0x59120003 to 0x59120000 if you don't use a dGPU as your main display Driver and instead use the iGPU for output.
      Also note. SMBIOS iMac18,1 has been reported to work better in this configuration. But 18,3 works fine for me.

      Kernel and Kext patches
       
      1.3 kexts and friends
      Add the supplied SSDT-UAIC.aml to "patched" - it limits the injected USB Ports to the actual number and ports valid for this board.
       
      Required kexts on "Other":
      FakeSMC.kext Whatevergreen.kext Lilu.kext AppleALC.kext IntelMausiEthernet.kext in case you're running Ethernet USBInjectAll.kext with the HCI-300-series-injector.kext --> These two should be installed to /L/E after install  
      We are leaving sound out at the moment, this is something for post-install.
       
      1.4 Check BIOS and install
      You should be ready for install. But before you reboot, please take a look at your BIOS and set it up accordingly (copied from the aforementioned guide and adapted):
      Load Optimized Defaults Disable VT-d setting If your system has Secure Boot Mode, disable it Enable CSM - This is sometimes needed to dual screens to work Set OS Type to Windows 8/10 or OtherOS - I have not seen a difference Turn off internal Serial and Parallel port Turn off Network stack for boot Turn off wake-on-lan (for now) Set XHCI Handoff to enabled Don't enable decode over 4G Depending on your GPU, set priority for boot Set internal GPU (iGPU) to enable - not auto or disabled Set DMVT pre-alloc min to 64MB and max to 128MB. For this selection to appear you might need to reboot after setting iGPU to enable Set USB legacy to enabled Activate XMP profile 1 f your Ram has it (mine doesn't and I added the timings manually) Set ERP to enable, disable platform power management (I need to do more research if this could be enabled)  
      I've attached my current BIOS config "hack2". You can place that on a fat32 drive (the EFI partition of your install USB drive might be an idea) and see if it loads. It's made for and with the F2 BIOS.
       
      The install itself should be like other MacOS Hackintosh installs with it several reboots and ensuring to select the correct boot device in Clover.
       
      2. Post-install
       
      2.1 Install clover on target
      This is a no-brainer, but install a fresh copy of Clover on your target medium.
       
      During install select again AptioMemoryFix but also additionally
      EmuVariableUefi-64.efi Install RC scripts on target volume because otherwise NVRAM doesn't seem to work
       
      After the install, copy
      config.plist contents of "Other" content of "patched" to your new clover install.
       
      2.2 Edit ACPI for slumber
      Choose one option, not both. The hot-patch is experimental, but for the moment it is stable.
       
      2.2.1 Edit DSDT
      No more need for manual DSDT patching. If you still do it, you might run into unstable sleep. SSDT hot-patching + sane clover.config edits are enough
       
      This is necessary only once on initial install and every time, you edit or upgrade the BIOS. The DSDT.aml attached to this post might work for your system or give you a file to compare to. Don't expect it to work for you, though.
      EDIT: Since moving from F2 BIOS to F12 I did not repatch and sleep is still somewhat reliable. But to be 100% sure, you can still follow these steps.
      I won't go into the details of DSDT extraction and patching. There are better guides (the linked guide is a rip-off of rehabman's guide from a different forum). Please follow such a guide to extract your ACPI data.
       
      Locate and disassemble the DSDT with the newest iasl binary you can put your hands on, then open it with MacIASL in its newest version you can find (Hint: Here is a good source) You can check if the version is new enough if MacIASL doesn't throw error upon compiling a freshly extracted DSDT.aml or DSDT.dst
       
      Add rehabmans repo (as per linked guide) and apply the following patches:
      Rename _DSM to _XDSM Fix _WAK Arg0 v2 USB3 _PRW 0x6D Skylake (instant wake) Find the CNVW device and remove the _PWR function there.
       
      Compile the DSDT and place it in "patched".
       
      2.2.2 Use SSDT hot-patching
      Instead of having to re-extract and re-patch the DSDT on every BIOS change or update, Hardware change one can also use ACPI hot-patching.
      It's a combination of config.plist patches and an SSDT, which is hot-patched into the ACPI (if I understand the process correctly)
       
      You need to add this SSDT-GPRW.aml to your Clover folder in the designated position at Clover/ACPI/patched You need to add this patch to your config.plist. It goes into the DSDT patch section  
      Note: This works for me, but the patch removes the _PRW method from all devices in the DSDT. This could have side-effects. So far, I have seen none. At the moment I'm also not applying any other patch, compared with the additional edits I made to the DSDT method before.
       
      2.3 Install kexts to system
      As mentioned in the install section, it's better to follow rehabman's instruction and install USBinjectAll.kext to /L/E:
      sudo cp -R Release/USBInjectAll.kext /Library/Extensions sudo touch /System/Library/Extensions && sudo kextcache -u / 2.4 Enable onboard Audio - Install AppleALC kext
      Make sure your EFI partition is mounted and that you have a vanilla AppleHDA kext available. See below for a guide how to get a vanilla AppleHDA if needed
      Note: Our Audio codec is ALC887 and it's running with layout ID 1.
      Download the newest AppleALC kext from here and install it together with lilu.kext from here into your usual /clover/kexts/others location. Done. No scripts or config.plist patches necessary.
      Add layout ID 1 to config.plist, if it's not there yet:
      <key>Audio</key> <dict> <key>Inject</key> <integer>1</integer> <key>ResetHDA</key> <true/> </dict> If you previously  installed any  audio patches, please follow this guide to "vanilla-ize" your install.
       
      2.5 Optional steps for Graphics
      If you have a dGPU, now it's the time to install its drivers and adjust the config.plist for it. The detaisl are specific to your GPU and thus of scope of this guide. Yet, my supplied config.plist is ready to be used with Nvidia Pascal cards and using the Nvidia web driver.
      Whatevergreen.kext helps with Intel iGPU and NVIDIA dGPU fixes.
       
      At the moment I'm also testing out a special bootflag: 'shikigva=12' to enable faster rendering in Final Cut Pro X. Without whatevergreen.kext and a shikigva bootflag, rendering in final cut seem very slow.
       
      2.5.1 Framebuffers
      If you're facing problems with output from your internal GPU, you can try the framebuffer patches listed by @BackwardMac:
       
      2.6 Install a proper keyboard layout
      You might not be using a fancy Apple branded keyboard. If you use a PC keyboard, you might be annoyed by the differing layout and usage of keys. As a German, you might find yourself quitting applications, since alt gr + Q won't add an @, but quit your current application. To fix this, you can simply install a different keyboard layout. Copy it to /Library/Keyboard Layouts/ and chose the layout in System Preferences, Keyboard in the section "Other". Deleting the previously selecting layout makes sure that only this one is used. Nice little trick.
       
      A keyboard layout for German keyboards is attached and works wonders
       
      3. Updating
      Updating inside 10.3.x/ 10.4.x point updates doesn't require much attention:
      Download the update from the AppStore as any Mac would do Allow the system to reboot Before booting MacOS with Clover, make sure to disable extra drivers for dGPUs which require non-native support. If using an Nvidia dGPU: Remove "nvda_drv=1"  from your boot arguments and disable Nvidia injection If using a non natively supported AMD card, do the same for AMD (I'm not using AMD, thus I cannot be specific) Boot into the newly created Install MacOS partition Repeat this process until the Install partition is gone Boot MacOS again, still following 3., and potentially install updated drivers Your Audio might require re-patching  
      4. ToDo
      Move away from static DSDT patching to SSDT hotpatching --> requires my work Native NVRAM --> requires developer work Audio without AppleHDA patching --> requires developer work  
      5. Thanks to
      @MaLd0nfor helping finding the right way with the DSDT
      @RehabMan, for being a legend and helping me out patching
      @toleda, for audio patches for the 300 series
      /u/corpnewt, for his superb vanilla guide
      @wmchris for his super XPS 9550 guide and introducing me to hot-patching
      @Panzerschiffe for his addition to this guide
      all the developers of clover and it's awesomeness
       
      SSDT-UIAC.aml
       
       
       
      win-germany.keylayout
       
    • By PixelLover
      I'm in the middle of my first hackintosh (High Sierra) on my ZenBook Pro UX501VW-US71 laptop using the Vanilla Install. I've tried using different config.plst files and I've gotten the furthest with RehabMan's own (linked here). It hangs at error message IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0.   Can anyone help me figure out what changes to make to the config.plst file for my specific laptop (which is where I assume the problem lies)   System Specs: Intel Skylake Core i7­-6700HQ 2.6 GHz Quad­core
      Intel® HD Graphics 530 Nvidia GTX 960M 2G 15.6" Touch IPS 4K Ultra­-HD display, 3840 x 2160 resolution   Kexts: AppleALC.kext FakeSMC.kext Lilu.kext USBInjectAll.kext WhateverGreen.kext  
    • By grisno
      Hi people,
       
      Installer to activate the sound card REALTEK ALC282-v2 (10ec:0282) with LayoutID 1 or 3 in MacOS. This installer does not contain AppleHDA patched Kext. To work properly, it must be installed over vanilla AppleHDA.kext.
       
      I want to thank the whole community for their efforts and content provided, because without these it would not be possible to create this installer.
       
      I would appreciate comments and suggestions!!
       
      Status:
      Speakers : OK Headphones : OK HDMI Audio : OK (Intel HD4K Tested) LineIn : N/A (Model Without LineIn) MicInt : OK MicIntNoiseReduction : OK MicExt : N/A (Model Without MicExt) AutoDetectLineIn : N/A (Model Without LineIn) Sleep : OK WakeUp : OK AutoSleep : OK Hibernate : OK Siri : OK   Tested Laptops:
       
      - HP Pavillion 15-D002SS
       
      Coming Soon:
       
      - Unified installer for the different supported operating systems.
      - Support model with LineIn jack.
       
      Modified Verbs:
      01271C20 01271D00 01271EA0 01271F90 01471C10 01471D00 01471E17 01471F90 01871CF0 01871D00 01871E00 01871F40 01E71CF0 01E71D00 01E71E00 01E71F40 02171C30 02171D10 02171E21 02171F00 01470C02   DSDT:
       
      Patch to apply with MaciASL in your DSDT
      ######################################### HDEF v1.00######################################## into method label _DSM parent_label HDEF remove_entry;into device label HDEF insertbeginMethod (_DSM, 4, NotSerialized)\n{\n If (LEqual (Arg2, Zero)) { Return (Buffer() { 0x03 } ) }\n Return (Package()\n {\n "layout-id", Buffer() { 0x01, 0x00, 0x00, 0x00 },\n //"layout-id", Buffer() { 0x03, 0x00, 0x00, 0x00 },\n "hda-gfx", Buffer() { "onboard-1" },\n "PinConfigurations", Buffer() { },\n })\n}\nend;  
×