search

OpenIntelWireless / itlwm

Intel Wi-Fi Drivers for macOS
https://OpenIntelWireless.github.io/itlwm/
GNU General Public License v2.0
6.94k stars 667 forks source link

[Intel AC-7260] Wifi is not working on Windows after using itlwm or AirPortItlwm (problem only with OC) #329

Closed kushwavez closed 4 years ago

kushwavez commented 4 years ago

Have You Read Our Docs

Are You Reporting A Bug

Environment

Description

Nothing helped unfortunately.

Bug Report Archive itlwm_debug.zip

2020-09-26 11:25:14.793510+0200 0x159 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000021.681610 IOUSBHostDevice@14500000: IOUSBHostDevice::updateIdlePolicyGated: IOUSBHostInterface@1 [] has an idle policy of 500ms

2020-09-26 11:25:14.803814+0200 0x159 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000021.691917 IOUSBHostDevice@14500000: IOUSBHostDevice::updateIdlePolicyGated: consensus idle policy timeout 500ms

2020-09-26 11:25:15.371240+0200 0xe9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.259334 IOUSBHostDevice@14500000: IOUSBHostDevice::forcePowerGated: kPowerStateSuspended timeout 1000ms

2020-09-26 11:25:15.384485+0200 0x159 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.272584 IOUSBHostDevice@14500000: IOUSBHostDevice::powerStateWillChangeToGated: kPowerStateSuspended

2020-09-26 11:25:15.394805+0200 0x159 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.282900 IOUSBHostDevice@14500000: IOUSBHostDevice::setPowerStateGated: kPowerStateOn -> kPowerStateSuspended

2020-09-26 11:25:15.408088+0200 0x159 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.296179 IOUSBHostDevice@14500000: IOUSBHostDevice::setPowerStateGated: suspending pipes

2020-09-26 11:25:15.417802+0200 0xe9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.305900 IOUSBHostDevice@14500000: IOUSBHostDevice::forcePowerGated: allowing power level to float

2020-09-26 11:25:15.426889+0200 0xe9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.314991 IOUSBHostDevice@14500000: IOUSBHostDevice::forcePowerGated: kPowerStateSuspended completed with 0x00000000 after 33ms

2020-09-26 11:25:15.437064+0200 0x159 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.325164 IOUSBHostDevice@14500000: IOUSBHostDevice::powerStateWillChangeToGated: kPowerStateOn

2020-09-26 11:25:15.446150+0200 0x159 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.334247 IOUSBHostDevice@14500000: IOUSBHostDevice::setPowerStateGated: kPowerStateSuspended -> kPowerStateOn

2020-09-26 11:25:15.455587+0200 0x159 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.343674 IOUSBHostDevice@14500000: IOUSBHostDevice::setPowerStateGated: resuming pipes

2020-09-26 11:25:15.464684+0200 0x74 Default 0x0 0 0 kernel: (IOUSBHostFamily) 000022.352786 IOUSBHostDevice@14500000: IOUSBHostDevice::powerChangeDone:


![Képernyőfotó 2020-09-30 - 15 03 14](https://user-images.githubusercontent.com/33935034/94694709-66eead00-0335-11eb-9e7e-2bf099730d9c.png)

- It's going on infinitely until I shut down the computer
- The IOReg shows that "IOUSBHostDevice@14500000" is the Bluetooth device.

**Kext Download Source**
- From OpenIntelWireless's GitHub release page.

**SOLVED!**
See this comment:
https://github.com/OpenIntelWireless/itlwm/issues/329#issuecomment-763545680

EDIT: Not solved. Still not working with OC. Changed card to BCM94352Z
AJoshSims commented 4 years ago

This is happening with my Intel AC 8265 as well.

kushwavez commented 4 years ago

This is happening with my Intel AC 8265 as well.

One thing I got in my mind, try a CMOS reset then boot right into Windows and let's see if it's working or not. still not a convenient way to use Wifi on Windows tho.

AJoshSims commented 4 years ago

This is happening with my Intel AC 8265 as well.

One thing I got in my mind, try a CMOS reset then boot right into Windows and let's see if it's working or not. still not a convenient way to use Wifi on Windows tho.

Okay, I reset the CMOS and now I can use wifi on Windows 10 as well as Catalina. How long did this solution work for you?

kushwavez commented 4 years ago

I didn't actually try that, was just an idea. Glad it's worked. Now I'm using a TP-Link USB wifi, so I'll do the same soon. That is my 2nd notebook and I rarely use it (usually only for betas like Big Sur, etc., my father uses it more often on Windows) so I can't really tell you how long will it last.

seungjunProgramming commented 4 years ago

My laptop works fine (Using OC0.6.1 Big Sur Beta 9 with windows10)

kushwavez commented 4 years ago

Okay so here is some news:

EDIT: I changed to Clover v5123 from OpenCore and it's working now on macOS and Windows too. on macOS IOUSBHostFamily still spamming the same thing like in the log over and over.

With itlwm + HeliPort on Catalina I've had exactly the same issue, worked with Clover, not with OpenCore.

williambj1 commented 4 years ago

@vaczi001

reinstalled AirPortItlwm to L/E and updated persmissions & kextcache

You should never do that.

I double-checked, moving to OpenCore and booting with that to macOS breaks Windows wifi

We don't have any Bootloader specific code. Based on your description, the issue is our of our control. If you have solid evidence (Bootloader Logs, Windows Driver Debug Logs, etc) of OpenCore putting your card into a bad state, you should report them to Acidanthera.

ghost commented 3 years ago

Hi, this is quite a serious behavior. I am another one that set up dual boot with macOS and Windows. After using AirPortItlwm the device is reported as broken in Windows. image

It's the same scenario in my case T450s/OpenCore/BigSure 11.1

kushwavez commented 3 years ago

@drinvincibilis I looked a bit into it and what I learned is that OpenCore is injecting all the SSDT/DSDT/other modified data to Windows too while Clover is running Windows native with native unmodified DSDT/other UEFI data, so maybe that's why it's not working with OpenCore and working on Clover.

One thing I still don't understand is that why did it work before using AirPortItlwm, and why not after using it. Somehow it's related to OpenCore, but also to AirportItlwm too, idk, I collected all the logs and attached, I can't do anything about that (I can do tests tho if someone ask me).

Boot Windows directly (not with OpenCore, but with Windows's own loader, you have to disable OpenCore's bootstrap for that), it'll start working again. It's pretty annoying tho.

ghost commented 3 years ago

Hi @vaczi001 thanks for the feedback. I did a step further and mixed the hard drive EFI from both macOS/OpenCore and Windows so it does dual boot. I will revert to Windows original EFI contents and boot macOS with the installer USB stick EFI.

ghost commented 3 years ago

@vaczi001 I can confirm. Reverting to original Windows EFI partition and booting restored the Wi-Fi huh

kushwavez commented 3 years ago

EDIT: Still not solved, after some restarts it's just stopped working again. No idea why OpenCore is injecting SSDTs and all other data to Win too The bluetooth still spamming me the same errors I wrote in the first post in macOS. I gave up and changed the wifi card to BCM94352Z.

(SOLVED! So I was right, OpenCore is injecting SSDTs and all other patches for Windows too, so that's why it isn't working with OpenCore. So we need OSI patches to prevent injecting data for Windows by checking what is the OS. If Windows, do not inject patches. Here, just put this file to ACPI folder and add to your config.plist 1st column: https://github.com/tylernguyen/x1c6-hackintosh/blob/master/EFI-OpenCore/EFI/OC/ACPI/SSDT-Darwin.aml)

zen3gr commented 3 years ago

Hello, link for the solution is dead? Would you be kind enough to update it and maybe write the basic steps of making opencore not inject data to Windows? FYI, I've got a thinkpad x240 with intel 7260 wireless; wifi is working fine on hackintosh (catalina) but got error "this device cannot start (code 10)" on windows 10.

Thanks!

EDIT: Still not solved, after some restarts it's just stopped working again. No idea why OpenCore is injecting SSDTs and all other data to Win too The bluetooth still spamming me the same errors I wrote in the first post in macOS. I gave up and changed the wifi card to BCM94352Z.

(SOLVED! So I was right, OpenCore is injecting SSDTs and all other patches for Windows too, so that's why it isn't working with OpenCore. So we need OSI patches to prevent injecting data for Windows by checking what is the OS. If Windows, do not inject patches. Here, just put this file to ACPI folder and add to your config.plist 1st column: https://github.com/tylernguyen/x1c6-hackintosh/blob/master/EFI-OpenCore/EFI/OC/ACPI/SSDT-Darwin.aml)

kushwavez commented 3 years ago

I forgot to update on this, but it didn't work even with that SSDT-Darwin.aml. You cannot make OC to disable patching on Windows, so you have to workaround it by using Refind or RefindPlus as a 2nd bootloader. So you have to boot OC first, then Refind, then Windows.

It is really quirky "solution" so I just decided to not use OC and use Clover instead.

Or my next idea is to select Windows Boot Manager with F12 when booting, that will boot Windows directly if I'm correct.

zen3gr commented 3 years ago

Thank you very much!

Stevemoretz commented 2 years ago

Still happens, migrating to clover is not really a solution :)

kushwavez commented 2 years ago

I did not say that, read again. The solution is to use Refindplus