Hervé

What do you mean by system stopped at login screen? Is it like frozen and you cannot type your password because system is not responding to your keyboard? Or were you expecting auto login? Clearly that is not enabled...

Ha ok, sorry for my misunderstanding about HD3000... Regarding AMD platforms, I can recommend you look at Shaneee's AMD site: https://forum.amd-osx.com Bronya is ace developer when it comes to AMD kernels.

Your link to HP specs indicate an AMD based computer so it needs special attention since OS X/macOS does not natively support AMD platforms. These usually require a specific modified kernel. NB: There can be no HD3000 on an AMD platform... Or maybe you posted incorrect specs.

Check our FAQ section.

As a newcomer, please consult our forum rules + FAQ section where you'd find this: https://osxlatitude.com/forums/topic/8696-is-my-wireless-card-compatible-with-os-x/ leading you to this section where you can consult our non-exhaustive wireless cards inventories: https://osxlatitude.com/forums/forum/104-wireless-and-bluetooth/

Did you rebuild your cache after moving the kexts to Clover/kexts/Other? It's necessary, otherwise those kexts remain in the cache (assuming they were cached of course...).

You're not installing Sierra but High Sierra. You're experiencing a Kernel Panic (KP) which appears related to the VoodooPS2Controller kext, i.e. the driver for your Keyboard and Mouse/TouchPad. Make sure to use the proper kext available here. Use latest version compiled by Bronxteck.

Pretty much the norm on a traditional mechanical HDD...

https://osxlatitude.com/forums/topic/8238-unsupported-gpu-graphics-cards/

No need to copy that file, no.

1st of all, let me state that antennas connection bear no relation whatsoever to hardware detection. This being cleared out of the way, did you check if your DSDT would not already inject properies for a totally different wireless card? Very common, especially as one re-uses existing files from another installation. 'been there myself too in the past.

Afaik, you either live with it or you opt for a different wireless card of Apple origin. Eg: Apple's own Broadcom BCM94360CD or related. These support all features 100% and OOB.

These features frequently fail to work well or even at all with non-Apple hardware.

Don't duplicate kexts; if you must copy them anywhere, stick to /L/E. Don't go off scale in desperation. Obviously, the patched DSDT goes to the patched folder, unzipped as "DSDT.aml". If the DSDT device id injection does not work, try to add your card id 14e4:43b1 in the Broadcom kext. What SMBIOS do you use by the way? Everything is explained in this thread.

It's HD4600 graphics (4th gen Haswell Intel graphics), not HD4000 (3rd gen Ivy Bridge Intel graphics). Are you attempting installation in BIOS legacy mode of UEFI mode?

Ok, try this revised DSDT: DSDT2.aml.zip

The "compatible" statement does not change the device id of the card it relates to; it only declares the card compatible with a model that is natively supported, i.e. it allows to load the relevant driver/kext for it. Bottom line is: do you now have wireless working or not?

Rami's gone; won't reply. I guess I'm overdue for an update of my E6440 guide. Outside sheer laziness, one of the reasons for not doing it was that I used a hybrid method to install High Sierra and retained that hybrid method for updates. By hybrid, I mean that, since Enoch did not support High Sierra installation and/or updates, I use Clover for initial installation and all subsequent updates. But for regular use, I still boot and run High Sierra with Enoch.

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.

@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... 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

DW1820A is "just" subject to whitelisting and that particular aspect was not clear before... It's not different that a DW1520 in that respect and the necessary patch or workaround is known.

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.

Use macIASL app.

You're not wasting my time, it's just that I'm a great believer of educating/experimenting/failing/retrying/succeeding, not of spoon-feeding... DSDT/Brcm4360 patch means exactly that: you either patch your DSDT or the Brcm4360 kext. If you read the inventory further down, you'll see what patching the DSDT or the kext means: NB: Patching means adding the PCI ids of the listed card to the Info.plist file found inside the listed kext. In rare cases, binary patching may also be necessary. For some cards, DSDT Patching can be a suitable and permanent alternative to kext patching (no need to repatch a kext after OS X updates and upgrades or new installations). Further down the post, there is an example of DSDT patching for Broadcom cards. That's what you could do for your AW-CE123H (and what I would advocate you do), the alternative being to patch the Brcm4360 kext as listed in the various BCM4352 threads found in our wireless forum section. This kext patching may also be done through Clover.

Picture not necessary, I got it 1st time... I'm sure you'll find a few pointers in the inventory's entry for that model (I believe it says a little more than just plain "supported"...). Then I invite you to consult the many threads related to BCM4352/BCM94352/AW-CE123H you'll find in the Wireless section of the forum. You can do it!