Closed zxystd closed 10 months ago
Works with Sonoma 14.0 (23A339) RC version as well. Configuration:
Works with Sonoma 14.0 (23A339) RC version as well. Configuration:
pardon my asking man but how'd you get the RC? i don't see where to grab it i looked on the apple dev center in my account and other sites online, nada.
I'm using the dev channel within macOS and it just offered me (23A339), right after yesterday's keynote.
I wonder if the latest commit feature of the main branch can be compiled into the Sonoma version?
I wonder if the latest commit feature of the main branch can be compiled into the Sonoma version?
It's 2 days before Sonoma release, so I hope it will be updated soon
I updated all my kexts and Opencore version to support sonoma. I was using it for sometime but noticed that iMessage,Facetime,Handoff doesn't work. I know many people have listed it here, but hear me out. When I connect to VPN or connect my iPhone as hotspot via USB, suddenly all of the things start to work. Thought to share the logs but i quickly downgraded back to Ventura as I use iServices very often. I just posted this in the hopes of sharing this weird VPN behaviour which might help someone.
使用preview5版本的时候会出现2.4Gwifi连接多次才能连接上的情况,而且断开了也要多次才能连接上,我的路由器是红米的AC2100,2.4Gwifi开的是40MHz,笔记本网卡是Intel AC9461
Stable release used to work well on Monterey and Ventura Preview 05 Keep connected and disconnecting simultaneously. Official Sonoma release. Intel 7265 Log_2023-09-29_10-08-43.log
Log_2023-09-28_22-23-08.log work fine Official Sonoma first release Log_2023-09-28_22-23-08.log
Preview 05 Intel AX210 Official Sonoma Release Airpods Pro 2 - connected but generally no sound, but when sound is coming it's very choppy, was working perfectly before
Preview 05 Imtel AX210 (Aorus X570) Sonoma 14.0
Wifi speeds; (openspeedtest selfhosted) Bluetooth connects to my android phone. So pretty stable here 👍 .
Auto Unlock: Supported
Status: Connected
Current Network Information:
hallo:
PHY Mode: 802.11ac
Channel: 36 (5GHz, 80MHz)
Country Code: DE
Network Type: Infrastructure
Security: WPA2 Personal
Signal / Noise: -33 dBm / 58 dBm
Transmit Rate: 867
MCS Index: 9
I updated all my kexts and Opencore version to support sonoma. I was using it for sometime but noticed that iMessage,Facetime,Handoff doesn't work. I know many people have listed it here, but hear me out. When I connect to VPN or connect my iPhone as hotspot via USB, suddenly all of the things start to work. Thought to share the logs but i quickly downgraded back to Ventura as I use iServices very often. I just posted this in the hopes of sharing this weird VPN behaviour which might help someone.
I can confirm that iServices work when a VPN is enabled, I am using PIA
Intel AX201 on Sonoma and Ventura download speeds for me are about 120Mbps while in Windows I get 490Mbps on going through an AC router. Is that expected - slower download speed in macOS for Intel AX201?
Interfaces:
en1:
Card Type: Wi-Fi (0x8086, 0x74)
Firmware Version: itlwm: 2.3.0 fw: 68.01d30b0c.0
MAC Address:
Locale: FCC
Country Code: US
Supported PHY Modes: 802.11 a/b/g/n/ac
PHY Mode: 802.11ac Channel: 161 (5GHz, 20MHz) Country Code: US Network Type: Infrastructure Security: WPA2 Personal Signal / Noise: -61 dBm / 58 dBm Transmit Rate: 144 MCS Index: 7
currently in Sonoma
hello so i am in the normal version of macos sonoma, but the wifi disconnects after a little bit, so i restarted my hack but it did it again, i reinstalled the beta kext but it did it again.
HP Elitebook 840 G5
Sonoma 14.1 Beta
using latest Airportitwn beta kext
flawless
wondering if anyone have encountered a situation like mine, the model identifier got suddenly changed to SLIC-BPC0,0 after I did some changes, but I never change the smbios part, before it was Macbookpro16,4
Dell 7560 (Wireless 3165) Sonoma 14.0 AirportItlwm-Sonoma-Preview05 TP-Link Archer A6 v2 (OpenWRT, Qualcomm Atheros QCA956X ver 1 rev 0) 2.4G and 5G OK for WPA2-PSK ONLY Other Protocol (WPA2-PSK+XXXX, XXXX) not work
2.4G and 5G OK for WPA2-PSK ONLY Other Protocol (WPA2-PSK+XXXX, XXXX) not work
I am not a dev but I am also using OpenWrt (Dynalink DL-WRX36). Can you please elaborate on what you mean by "WPA2-PSK+XXXX, XXXX" does not work?
2.4G and 5G OK for WPA2-PSK ONLY Other Protocol (WPA2-PSK+XXXX, XXXX) not work
I am not a dev but I am also using OpenWrt (Dynalink DL-WRX36). Can you please elaborate on what you mean by "WPA2-PSK+XXXX, XXXX" does not work?
Like this
Kext seems to load, but no Wi-Fi and cannot enable it. :( Log_2023-10-16_17-34-31.log
EDIT: Attached the .log
@Stonemage
[ 4.689798]: itlwm: iwx_enable_fwload_interrupt
[ 5.690840]: itlwm: SecBoot CPU1 Status: 0x71a6, CPU2 Status: 0xb03
[ 5.690843]: itlwm: UMAC PC: 0x804804ae
[ 5.690846]: itlwm: LMAC PC: 0x4d13d6
[ 5.691033]: itlwm: : could not load firmware
[ 5.691320]: itlwm: : failed to load init firmware
[ 5.691321]: itlwm: iwx_stop_device
[ 5.728492]: itlwm: iwx_check_rfkill RF_KILL hw: 0
The card is on invalid state, please check your EFI, especially the ACPI/PCIE/BIOS settings.
Hi! So I was just wondering, why it takes long to connect to my wifi. It takes atleast 1-2 minutes to connect. I have a stable connection btw.
The card is on invalid state, please check your EFI, especially the ACPI/PCIE/BIOS settings.
@zxystd I don't understand how that could be. Nothing in the config.plist has changed since the upgrade from Monterey, and the BIOS has no settings to adjust for the Wi-Fi card. The only thing that has changed is the upgrade to Sonoma, and the new .kext.
New install of Sonoma on a new, clean SSD. Copied the original entire EFI over... and then replaced AirportItlwm.kext and that was the only change.
Are you sure that the .kext is actually resetting and initialising the card properly?
The card is on invalid state, please check your EFI, especially the ACPI/PCIE/BIOS settings.
@zxystd I don't understand how that could be. Nothing in the config.plist has changed since the upgrade from Monterey, and the BIOS has no settings to adjust for the Wi-Fi card. The only thing that has changed is the upgrade to Sonoma, and the new .kext.
New install of Sonoma on a new, clean SSD. Copied the original entire EFI over... and then replaced AirportItlwm.kext and that was the only change.
Are you sure that the .kext is actually resetting and initialising the card properly?
You can try the following, had to do it on one of my machines to get it working. - https://github.com/OpenIntelWireless/itlwm/issues/905#issuecomment-1666804937
You can try the following, had to do it on one of my machines to get it working. - #905 (comment)
@diepeterpan I think this proves right here that the .kext isn't initialising the card properly, at least in some cases such as mine and yours.
The fact that the card works without intervention in another OS, but not with this .kext without a physical mod shows that the card isn't being addressed correctly or something. Any ideas, @zxystd ?
You can try the following, had to do it on one of my machines to get it working. - #905 (comment)
@diepeterpan I think this proves right here that the .kext isn't initialising the card properly, at least in some cases such as mine and yours.
The fact that the card works without intervention in another OS, but not with this .kext without a physical mod shows that the card isn't being addressed correctly or something. Any ideas, @zxystd ?
It is not isolated to MacOS and this driver, even Linux, and certain Windows installations experience this problem, that's if this is the same problem you experience.
You hace yo make sure you got the correct sip/car config (enabled) and secure boot model configured (default... I guess on this, got to check mine) here is working flawless, it takes some time to connect to my 5ghz network, but the wireless N works like a charm, actually I was aggravated by the length of time it would take so I installed the realtek driver and followed the instructions, when I used the OC version I regretted it because my computer got stuck at boot, good thing I had the setup USB with Sonoma 14.1B3 right there (I also did a clean install) and after I got it to boot again (had to manually remove them realtek drivers from efi kext folder) and then it booted again using my previous working config.plist kept going through the instruction and got done reason it feels it connects faster. So, I wouldn't recommend it but it worked for me. And since I'm on Hackintosh, i'm used at finding my own answers, and apply them or even try stuff I've not it anyone else haven't (I'm guessing here since there has been very little info found sometimes, but don't others there is just plenty of information, so I would tell you to finish this lecture to go and research on what I just mention in the beginning of this long ash text. 🌹
On Mon, Oct 16, 2023, 5:50 PM Stonemage @.***> wrote:
You can try the following, had to do it on one of my machines to get it working. - #905 (comment) https://github.com/OpenIntelWireless/itlwm/issues/905#issuecomment-1666804937
@diepeterpan https://github.com/diepeterpan I think this proves right here that the .kext isn't initialising the card properly, at least in some cases such as mine and yours.
The fact that the card works without intervention in another OS, but not with this .kext without a physical mod shows that the card isn't being addressed correctly or something. Any ideas, @zxystd https://github.com/zxystd ?
— Reply to this email directly, view it on GitHub https://github.com/OpenIntelWireless/itlwm/issues/896#issuecomment-1765331996, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZABHXLB7DVXD2RYSU4XXQLX7WTYZAVCNFSM6AAAAAAZ5I753OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGMZTCOJZGY . You are receiving this because you commented.Message ID: @.***>
@diepeterpan Having to hardware-mod a device just to get it to work is not normal, period. It's not expected behaviour.
And my point still stands - if the exact same hardware works in another OS without adjusting a single setting, then it is this implementation that isn't working. So, again I ask if there are any ideas about why this would be happening?
@diepeterpan Having to hardware-mod a device just to get it to work is not normal, period. It's not expected behaviour.
And my point still stands - if the exact same hardware works in another OS without adjusting a single setting, then it is this implementation that isn't working. So, again I ask if there are any ideas about why this would be happening?
We don't have all the answers, for pete'sake, you are working on OSX, and the hardware you are running on is not intended for MacOS, you have to make it work, the thread cannot fix everyone's problems. So try things, see if they fix your problem, and continue. This driver is adapted from Linux, Linux experiences the same problems, and the adaptation is not going to resolve everyone's problems. People are going to ignore you if you continue being stubborn and just moaning.
Another option is to try to disable secure boot in BIOS/EFI if enable - https://askubuntu.com/questions/1422166/ax210-with-jammy-wifi-stopped-working
You're such a dick
On Tue, Oct 17, 2023, 1:17 AM Stonemage @.***> wrote:
@diepeterpan https://github.com/diepeterpan Having to hardware-mod a device just to get it to work is not normal, period. It's not expected behaviour.
And my point still stands - if the exact same hardware works in another OS without adjusting a single setting, then it is this implementation that isn't working. So, again I ask if there are any ideas about why this would be happening?
— Reply to this email directly, view it on GitHub https://github.com/OpenIntelWireless/itlwm/issues/896#issuecomment-1765683882, or unsubscribe https://github.com/notifications/unsubscribe-auth/AZABHXOJPFMENX7RVZ6UABLX7YIGNAVCNFSM6AAAAAAZ5I753OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRVGY4DGOBYGI . You are receiving this because you commented.Message ID: @.***>
Already merged into main branch 306562e4925bee0917ac367a091e305f63ab205e, now we can download from alpha version release page. Thanks for everyone.
Everything works fine with AX211 intel Wireless
![]()
![]()
![]()
in which mac os ?
Just a question. The driver works with AX? AC has worked well. But at all good job :)
Airdrop is NOT working on last beta. iphone e 13 does not see Hackintosh, while Hackintosh sees iphone but not transferring anything. Intel AC-9560 on Z390 Designare.
A correct issue should contains the running log or panic log.
for running log:
DebugEnhancer.kext
.Run the following commands in terminal to gather logs:
A log file will then be created on your Desktop.
for panic log:
System info
->logs
, and you may find some files ended with.panic
.