OpenIntelWireless
Please add AirportItlwm support for macOS 15 Sequoia 15.4
Please If you have found a way to get Airportitlwn.kext on Macos sequoia share it with us. I can help here for testing if you need to or put us on the way or mention the tools so we can help out . or Let us know if this project is dead or what
i am trying to build it using this guide on YouTube
https://www.youtube.com/watch?v=_CaCxPV1GHo but it's difficult because it's a very old video
i am trying to build it using this guide on YouTube
https://www.youtube.com/watch?v=_CaCxPV1GHo but it's difficult because it's a very old video
@Blu-Dread Have you checked the very first issue that was created requesting the developer to work on making Airportitlwm kext to work on macOS Sequoia? https://github.com/OpenIntelWireless/itlwm/issues/983 here various hackintosh enthusiasts and devs talked about the changes made by Apple which caused the kext to not work in Sequoia. If you haven't looked at it, maybe the discussion in issue #983 will represent additional context that is relevant to work on a kext version that works in Sequoia.
i am trying to build it using this guide on YouTube
https://www.youtube.com/watch?v=_CaCxPV1GHo, but it's difficult because it's a very old video
Hi Blue-Dread
Thank you for your reply, but for your knowledge, this is the old way that we still use up to Sonoma, which is fine for Old Mac OS Version too, but from Mac OS Sequoia and up and Apple has changed the game and she is using DriverKit SDK to build drivers for wifi, and I believe this is the issue, I have rebuilt several times just trying to load the kext, but I haven't succeeded till now because its need also trusted developer certificate
i am trying to build it using this guide on YouTube
https://www.youtube.com/watch?v=_CaCxPV1GHo, but it's difficult because it's a very old video
@Blu-Dread Have you checked the very first issue that was created requesting the developer to work on making Airportitlwm kext to work on macOS Sequoia? #983 Here, various hackintosh enthusiasts and devs talked about the changes made by Apple, which caused the kext to not work in Sequoia. If you haven't looked at it, maybe the discussion in issue #983 will represent additional context that is relevant to work on a kext version that works in Sequoia.
Hi jzrodriguez98
Thank you for your reply, but I have seen no update on it since October 2024, and [#983] most of their comments are talking about itilwm + hillop what whatever the name, and they forgot to focus on our main goal, which is getting the Airportitlwm project to continue again ( the native wireless connection way ), that way I had to create this threat to give attention to that project and alot of us here ready to help
@Blu-Dread It's great that you are trying to make the Airportitlwm kext working in Sequoia. As @mishealgo said, the main issue is what Apple did, using DriverKit SDK to build drivers for wifi, which is what some of the devs and other users mentioned in issue 983. You're right, since then users have been focused on either leveraging OCLP to use in Sequoia the old Airportitlwm kext created in Ventura or setting up itlwm+heliport for use in Sequoia.
Apple not leave the interface that communicates to user space in IO80211Family framework, their programers hardcode the implementation class for Broadcom driver. tired to hack their shit(maybe use Lilu).
Apple not leave the interface that communicates to user space in IO80211Family framework, their programers hardcode the implementation class for Broadcom driver. tired to hack their shit(maybe use Lilu).
So for sequoia we need to completely recode the whole codebase? to not use IO80211 and use Lilu instead?
So for sequoia we need to completely recode the whole codebase? to not use IO80211 and use Lilu instead?
no, just the IOCTL section, for now we use virtual table to implement the actual communication, see here https://github.com/OpenIntelWireless/itlwm/blob/master/AirportItlwm/AirportItlwmSkywalkInterface.hpp
but Apple not provide thirdparty driver to link the methods at all, so we have no way to communicate with user space application.s There may have a chance to use Lilu to hook every ioctl methods and replace to our drivers code.
So for sequoia we need to completely recode the whole codebase? to not use IO80211 and use Lilu instead?
no, just the IOCTL section, for now we use virtual table to implement the actual communication, see here https://github.com/OpenIntelWireless/itlwm/blob/master/AirportItlwm/AirportItlwmSkywalkInterface.hpp
but Apple not provide thirdparty driver to link the methods at all, so we have no way to communicate with user space application.s There may have a chance to use Lilu to hook every ioctl methods and replace to our drivers code.
I think that there's 2 approach that can be taken in order to get it working
The first one is to create a driver that exposes IOCTL methods so that other kexts can use it like the old way. This approach would remove the need to recode the whole IOCTL part and (perhaps) makes it easier to update in the future
The second approach is the one you've said earlier, where we directly link all the IOCTL methods with itlwm
Which method do you think fits this the best? also do you think the first method is possible to implement?
no, just the IOCTL section, for now we use virtual table to implement the actual communication, see here https://github.com/OpenIntelWireless/itlwm/blob/master/AirportItlwm/AirportItlwmSkywalkInterface.hpp
but Apple not provide thirdparty driver to link the methods at all, so we have no way to communicate with user space application.s There may have a chance to use Lilu to hook every ioctl methods and replace to our drivers code.
@zxystd Would it be worth skipping over sequoia entirely now that Tahoe is said to be the last Intel supported macOS? It'd make sense for that last hackintoshable version to be the main focus, right? (Although I know the whole system can change with it being early dev build/previews, seems it needs more tweaks than usual across the board)
