Jump to content
ManiaKsLV

ASUS K55Vm - Help with High Sierra Install

Recommended Posts

Why on earth would you re-install High Sierra? Clearly you just have to adjust the code a little so that you can patch your DSDT...

 

Your IOREg shows that your wireless card appears to be attached to device called WLAN, itself located under parent device RP02; so that your target device for patching. Then you simply don't just copy paste the sample I posted, especially the "..." lines! They're meant to summarize code to ignore.

 

Instead, under the device called WLAN, copy/paste the _DSM method, adjusting the name of the model to AW-CE123H, instead of what's provided in my sample code.

 

You won't be able to recompile your DSDT properly until you do that. But, by all means, post your initial DSDT file for patching.

 

Share this post


Link to post
Share on other sites

Try adding this to FakeID Wifi 0x43A014E4 in the Config file under Devices

Add these kexts to Clover kext folder

Lilu + AirportBrcmFixup.kext

FakePCIID.kext + FakePCIID_Broadcom_WiFi.kext

Share this post


Link to post
Share on other sites

@Jake Lo So..... i will try explain what i did step by step...

 

So i downloaded Lilu.kext 1.3.4 + AirportBrcmFixup.kext 1.1.9

and RehabMan-FakePCIID-2018-1027.zip who contains FakePCIID.kext + FakePCIID_Broadcom_WiFi.kext

i used this folders

1913423386_InkedScreenShot2019-03-11at20_27.48_LI.thumb.jpg.2867694a1ed5efa05f103b672fb1cf4a.jpg

then i add fake id

1321107625_InkedScreenShot2019-03-11at20_16.13_LI.thumb.jpg.f1adfd73ba0a9c46eecef5513a9a0e01.jpg

then copy files in CLOVERS kext folder

1968292209_InkedScreenShot2019-03-11at20_26.32_LI.thumb.jpg.f2d06e9a54501118aa42d69f5b9b780d.jpg

then for no reason i rebuild S/L/E folder cache and premisions 

and restarted PC

954655485_InkedScreenShot2019-03-11at20_27.11_LI.thumb.jpg.d8a452f5eaa6f8fbd5622d5603f3f522.jpg

Did i do something wrong? or all i mention is right.

Share this post


Link to post
Share on other sites

@ManiaKsLV, can you please confirm what wireless card is currently fitted in your laptop?

 

Reason I ask is because, on looking at your DSDT, I could not help but notice the following DSM method under device WLAN which basically injects properties of an Atheros AR9285 card! So... :blink:

                    Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                 0x03                                           
                            })
                        }
                        Return (Package (0x0E)
                        {
                            "device-id", 
                            Buffer (0x04)
                            {
                                 0x30, 0x00, 0x00, 0x00                         
                            }, 
                            "name", 
                            "pci168c,30", 
                            "AAPL,slot-name", 
                            Buffer (0x08)
                            {
                                "AirPort"
                            }, 
                            "device_type", 
                            Buffer (0x08)
                            {
                                "AirPort"
                            }, 
                            "model", 
                            Buffer (0x33)
                            {
                                "Atheros 9285 802.11 b/g/n Wireless Network Adapter"
                            }, 
                            "subsystem-id", 
                            Buffer (0x04)
                            {
                                 0x8F, 0x00, 0x00, 0x00                         
                            }, 
                            "subsystem-vendor-id", 
                            Buffer (0x04)
                            {
                                 0x6B, 0x10, 0x00, 0x00                         
                            }
                        })
                    }

 

If you wish to inject properties for the AzureWave AW-CE123H, the above has to be replaced! By something like the following...

                    Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
                    {
                        If (LEqual (Arg2, Zero))
                        {
                            Return (Buffer (One)
                            {
                                 0x03                                           
                            })
                        }
                        Return (Package ()
                        {
                            "compatible",
                            Buffer ()
                            {
                                "pci14e4,43a0"
                            },
                            "model", 
                            Buffer ()
                            {
                                "AzureWave AW-CE123H 802.11b/g/n/ac Wireless"
                            }
                        })
                    }

 

Faking Broadcom device 14e4:43a0 whilst retaining your current Atheros properties injection will not work... Remove the Clover faking and try the DSDT attached below.
DSDT.zip

Share this post


Link to post
Share on other sites

@Hervé Now it's AzureWave AW-CE123H previous one was DW1702.... that mean something left from previous patching while DW1702 were in.

I should use macIASL app for this yes? i should find lines in first row and then replace them with second row? 

Share this post


Link to post
Share on other sites

It would have been useful to remember that in the fist place! You would have saved yourself some time...

 

For your AW-CE123H, just follow the instructions at the end of my previous post. You may also cleanup your kexts folder and remove all those related to Atheros hardware. If you also update to the latest Lilu + WhateverGreen + AppleALC, you should no longer need those old Shiki + IntelGraphicsFixup kexts that are now outdated.

 

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

×