Hervé

You've always got the option of an NGFF/M.2 adapter + Apple's own Broadcom BCM94360xx/BCM94331xx. Adapters cost as little as $5 and an Apple card can be obtained for as little as $10. Look these up on well-known auction sites. Those get my vote!

There's nothing else anyway, so...

It's useless without graphics acceleration.

Which kext are you running? What's the LAN card on this laptop? Intel 82579LM GigEthernet?

No need to quote every post you reply to; it's quite annoying actually... It sounds that you neither have HDMI audio set properly, nor graphics acceleration.

Make sure you select the HDMI output in the Audio PrefPane. It's not automatic...

Try this revised Clover config: config.plist.zip

Yeah, I saw the video but it wasn't clear to make things out... Try and boot with nVidia disabled. Once back into the system, grab a copy of your Clover EFI folder and zip it in order to post it. You could also try to set automatic login and see how your system then behaves on next reboot.

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?