Mac os intel wifi kext

Mac os intel wifi kext

Please note: this project is now unsupported. Please go to itlwm if you would like a supported kext.

This is a kext which aims to provide support for Intel wireless devices on MacOS. It is intended to provide similar support with MacOS as a native AirPort device (via the IO80211Controller private IOKit class).

This kext does not function yet. Do NOT install this into Clover, or /S/L/E. You WILL ruin your system.

Card Name PCI ID Supported Planned Support Relevant Threads
Intel(R) Dual Band Wireless AC 3160 8086:08B4, 8086:0B83 No (LMAC scanning) Yes
Intel(R) Dual Band Wireless AC 3165 8086:3165, 8086:3166 No (LMAC scanning) Yes device-logs#6
Intel(R) Dual Band Wireless AC 3168 8086:24FB Unknown (CNVi card) Unknown device-logs#8
Intel(R) Dual Band Wireless AC 4165 8086:24F5, 8086:24F6 Unknown (similar to 8xxx series) Unknown
Intel(R) Dual Band Wireless AC 7260 8086:08B1 Yes (confirmed) Yes
Intel(R) Dual Band Wireless N 7260 8086:08B2 Unconfirmed Unknown
Intel(R) Dual Band Wireless AC 7265 8086:095A, 8086:095B Unconfirmed Unknown device-logs#12
Intel(R) Wireless N 7265 8086:095A, 8086:095B Unconfirmed Unknown
Intel(R) Dual Band Wireless AC 8260 8086:24F3 Yes (confirmed) Yes device-logs#7 device-logs#11 device-logs#13
Intel(R) Dual Band Wireless AC 8265 8086:24F3, 8086:24FD Yes (confirmed) Yes device-logs#9
Intel(R) Dual Band Wireless AC 8275 8086:24FD Yes (confirmed) Yes
Intel(R) Dual Band Wireless-AC 9162 Unknown Unknown (CNVi card) Unknown
Intel(R) Dual Band Wireless-AC 9260 8086:2526, 8086:0000 8086:0010, 8086:0014 8086:0018, 8086:0210 8086:0214, 8086:4010 8086:8014, 8086:a014 Support varies Yes
Killer (R) Wireless-AC 1550 Wireless Network Adapter (9260NGW) 8086:2526, 1a56:1550 Unknown (rebrand) Unknown
Intel(R) Dual Band Wireless-AC 9270 8086:1410, 8086:1610 Unknown Unknown
Intel(R) Dual Band Wireless-AC 9461 8086:0060, 8086:0064 8086:0260, 8086:0264 Unknown (CNVi card?) Unknown
Intel(R) Dual Band Wireless-AC 9462 8086:00a0, 8086:00a4 8086:02a0, 8086:02a4 8086:40a4, 8086:42a4 Unknown (CNVi card?) Unknown device-logs#14
Intel(R) Dual Band Wireless-AC 9560 8086:0030, 8086:0034 8086:0038, 8086:003c 8086:0230, 8086:0234 8086:0238, 8086:023c 8086:2030, 8086:2034 8086:4030, 8086:4034 8086:4234 Mixed results (some are CNVi, some are PCIe) Yes device-logs#1
Killer(R) Wireless-AC 1550s Wireless Network Adapter 1a56:1551 Unknown (rebrand) Unknown
Killer(R) Wireless-AC 1550i Wireless Network Adapter 1a56:1552 Unknown (rebrand) Unknown
Intel(R) Dual Band Wireless-AC 19560 8086:1030 Unknown (gigabit card?) Unknown

If your card is not listed here (or does not have an open issue), please open an issue here: https://github.com/AppleIntelWifi/device-logs

NOTE: AX-series cards are currently NOT supported, and are very likely to never be supported.

Apple for making macOS, and all of the glorious awful APIs that I use

@zxystd for writing the initial base code for this kext

Intel for the cheap wireless devices

@acidanthera for the CI configuration

@comex for this amazing gist which contains several structs I didn’t want to RE

@rpeshkov for paving the way initially with IntelWifi/Black80211

About

Kext providing initial support for Intel wireless devices

Источник

AppleIntelWifi

Releases

Debug

Release

Why this kext?

Well, we’re working on a full implementation with IOKit. This means that macOS will handle all WPA2 handshaking, key management, and the rest. This significantly reduces the amount of work that we have to do, and is a massive plus for the security (and I’m generally uncomfortable writing any crypto code, as that is far from my expertise). As well, it should be measurably more performant, due to avoiding a second 802.11 stack. In fact, the majority of wireless kexts (including the realtek USB adapters) implement dual 802.11 stacks, and are often a mess to debug and fiddle with when things go wrong, with homebrewed implementation of WPA. Approaching wireless devices via this method requires either a massive department staffed with cryptographers, wireless experts, and potentially linux kernel developers, or entails a duct taped job where you merely strap IEEE80211 from OpenBSD to your driver, and call it a day. I’m simply not satisfied with the latter, and sadly do not have a department at a billion dollar company, and frankly, I’m sick of having a dongle strapped to my laptop.

Will AirDrop ever be supported?

It is definitely possible with all of the discoveries that I have made, however, I’m uncertain entirely on whether or not I want to subject myself to the pain and torture that implementing AWDL will cause. It is a possibility.

What devices are supported?

Unfortunately, due to a massive architectural change (and a lack of development devices), AX-series devices are unsupported. However, all 802.11 AC devices are planned to be supported (316x, 7xxx, 8xxx, 9xxx).

I found a bug! How can I report it?

Run the logging script, and create a new issue on the repo with your log file attached.

I’d like to help! How can I help?

We’re crowd-sourcing testing to the community. We’ve found it to be significantly effective in determining compatibility with wireless devices, and I would love to continue that trend as much as we can. If you have Xcode installed, and can run a simple shell scripts, please upload your log file to the repo here. There are a significant number of devices which have been unaccounted for, as well as some devices having unknown compatibility. A sample size of n=500 is bounds better then a sample size of n=5.
In addition, if you are technically minded and don’t mind reading and writing C/C++, I am ALWAYS accepting of pull requests and contributions. This is not a one-man effort, and my C++ knowledge is only so vast. We have adopted the Google coding style to the entire repo, and request that you format and lint your code before submitting a PR.

Copyright В© 2020 IntelWifi for MacOS authors. All rights reserved.

Источник

Mac os intel wifi kext

The goal of this project is to create an OS X driver for those Intel WiFi cards based on the MVM firmware (basically, the current and previous generations).

The following Intel WiFi cards/chips are supported:

  • Intel® Wireless 3160
  • Intel® Wireless 3165
  • Intel® Wireless 4165
  • Intel® Wireless 7260
  • Intel® Wireless 7265
  • Intel® Wireless 8260
  • NUC on-board wireless for NUC 5i*RY*
  • NUC on-board wireless for NUC 6i*SY*

This driver is still in the «can it be done?» stage.

As of this writing the driver recognizes the appropriate hardware and loads a matching firmware file, but does not yet send the firmware to the hardware.

Now I’m in the process of trying to get all the Linux driver code to build on Mac OS X. This will be a very long process. Work is currently happening on the «Porting» branch, but only a small subset of the code even compiles right now.

Long story short, this driver does not yet actually connect to wireless networks.

If you’re interested in helping, it would be great to have more people try test builds just to ensure it accurately identifies all the hardware I don’t have on hand to try.

There are notes on the project wiki. If you’re interested in helping out at the code level, that would be super.

Right now all the action is on the «Porting» branch.

Typical third-party driver kexts should be installed to /Library/Extensions, but that’s not recommended for this driver yet. Even in this initial work I’ve managed to craft a bug that crashed my machine when the driver loaded. If the driver was installed system-wide, that would happen on every boot, which seems rather unfortunate. So the manual loading process is recommended for now.

  1. Download the latest AppleIntelWiFiMVM.kext.zip (or build from source)
  2. Unzip if needed
  3. From Terminal, go to where the kext is and run:
  1. Run Console.app and scroll to the bottom of the system log (usually displayed by default) or search it for AppleIntelWiFiMVM. You should see output such as:

You’ve been warned!

But to install system-wide, use your favorite kext installer tool to install the kext to /Library/Extensions. It should load automatically, and generate the same output as above that you can view in Console.app

In building this driver, I’m relying on:

  • The iwlwifi Linux driver
  • The Intel firmware releases for this hardware (probably largely due to the Linux drivers)
  • Mieze’s IntelMausiEthernet OS X driver for wired Ethernet adapters
  • RehabMan and the-darkvoid’s BrcmPatchRAM OS X driver for USB Bluetooth adapters

This driver (including any code I used in it from the projects above) is covered by the GPL v2

The Intel firmware is covered by the firmware license

Источник

Intel Wi-Fi Kext w/ Auto-connect tools [Catalina]

paox2za

6 series:
#define PCI_PRODUCT_INTEL_WL_22500_1 0x2723 /* Wi-Fi 6 AX200 */ (ver 1.8.1)

9000 series:
#define PCI_PRODUCT_INTEL_WL_9260_1 0x2526 /* Dual Band Wireless AC 9260 */
#define PCI_PRODUCT_INTEL_WL_9560_1 0x9df0 /* Dual Band Wireless AC 9560 */
#define PCI_PRODUCT_INTEL_WL_9560_2 0xa370 /* Dual Band Wireless AC 9560 */

8000 series:
#define PCI_PRODUCT_INTEL_WL_8260_1 0x24f3 /* Dual Band Wireless AC 8260 */
#define PCI_PRODUCT_INTEL_WL_8260_2 0x24f4 /* Dual Band Wireless AC 8260 */
#define PCI_PRODUCT_INTEL_WL_8265_1 0x24fd /* Dual Band Wireless-AC 8265 */

7000 series:
#define PCI_PRODUCT_INTEL_WL_7260_1 0x08b1 /* Dual Band Wireless AC 7260 */
#define PCI_PRODUCT_INTEL_WL_7260_2 0x08b2 /* Dual Band Wireless AC 7260 */
#define PCI_PRODUCT_INTEL_WL_7265_1 0x095a /* Dual Band Wireless AC 7265 */
#define PCI_PRODUCT_INTEL_WL_7265_2 0x095b /* Dual Band Wireless AC 7265 */

3000 series:
#define PCI_PRODUCT_INTEL_WL_3165_1 0x3165 /* Dual Band Wireless AC 3165 */
#define PCI_PRODUCT_INTEL_WL_3165_2 0x3166 /* Dual Band Wireless AC 3165 */
#define PCI_PRODUCT_INTEL_WL_3160_1 0x08b3 /* Dual Band Wireless AC 3160 */
#define PCI_PRODUCT_INTEL_WL_3160_2 0x08b4 /* Dual Band Wireless AC 3160 */
#define PCI_PRODUCT_INTEL_WL_3168_1 0x24fb /* Dual Band Wireless-AC 3168 */

As suggested by shuhung, if you want the wifi switching feature, please use the ver 1.2.5 instead of ver 1.2.3 which I found more stable.

Before starting the installation, please uninstall all previous Intel Wi-Fi kext and make sure that they are not being loaded before installation by checking it in terminal as example below

Источник

[Success] WORKING Intel Wifi Drivers for 7265AC on Catalina

Hasmade

johnnyx86

Hi I tried. But seems like the kext loaded well but not internet connection established.iwlwifi-8000C-36

I followed your instruction. Downloaded iwlwifi-8000C-36 and i renamed it to iwm-8000C-34 and did chmod -R 755 to make it unix executable. After which i copied into the AppleIntelWiFi.kext to replace the existing unix executable.

Still don’t understand why unable to established internet connection.

shuhung

Hi I tried. But seems like the kext loaded well but not internet connection established.iwlwifi-8000C-36

I followed your instruction. Downloaded iwlwifi-8000C-36 and i renamed it to iwm-8000C-34 and did chmod -R 755 to make it unix executable. After which i copied into the AppleIntelWiFi.kext to replace the existing unix executable.

Still don’t understand why unable to established internet connection.

Make AppleIntelWiFi.kext executable again after iwm-module replaced.

sudo chown -R root:wheel AppleIntelWiFi.kext
sudo chmod -R 755 AppleIntelWiFi.kext

hackslashX

johnnyx86

Make AppleIntelWiFi.kext executable again after iwm-module replaced.

sudo chown -R root:wheel AppleIntelWiFi.kext
sudo chmod -R 755 AppleIntelWiFi.kext

As below. I still couldn’t get the WiFi connected.

loaded the kext.

The wireless card AC8260 detected correctly with the correct MAC address and my network SSID is listed correctly.

shuhung

As below. I still couldn’t get the WiFi connected.

View attachment 470292
Renamed iwlwifi-8000C-36.ucode to iwm-8000C-34 and replaced with the previous one. Info.plist, changed the BSSID & PW to my network SSID.
View attachment 470293
loaded the kext.

The wireless card AC8260 detected correctly with the correct MAC address and my network SSID is listed correctly.

After iwm-module replaced
IOModel is xxxx-17, IORevision is 16.xxxx

If your result show as below then new firmware is loaded but not working correctly with wifi model, new firmware may be buggy.
For 8260, last bug fix version from Intel is iwlwifi-8000C-16.ucode, not sure still work or not, try older version like iwlwifi-8000C-31.ucode.
IOModel is xxxx-34
IORevision is 36.xxxx

johnnyx86

Check IORevision with IORegistryExplorer.
Before replacing iwm-module
IOModel is xxxx-17, IORevision is 17.xxxx
View attachment 470299

After iwm-module replaced
IOModel is xxxx-17, IORevision is 16.xxxx
View attachment 470300

If your result show as below then new firmware is loaded but not working correctly with wifi model, new firmware may be buggy.
For 8260, last bug fix version from Intel is iwlwifi-8000C-16.ucode, not sure still work or not, try older version like iwlwifi-8000C-31.ucode.
IOModel is xxxx-34
IORevision is 36.xxxx

After replacing with iwlwifi-8000C-16.ucode WiFi is working:

After replacing with iwlwifi-8000C-36.ucode WiFi not working:

After replacing with iwlwifi-8000C-31.ucode WiFi is Working:

Maybe what you said iwlwifi-8000C-36.ucode is buggy??

Источник

Читайте также:  Windows 7ni aktivatsiya qilish
Оцените статью