Input driver uses deprecated KPIs, won’t load in macOS Big Sur

[Potassium Ion]

EDIT 2: This issue is due to the use of KPIs which have been deprecated for a year. This support article contains more details and transition guidance for developers:

https://developer.apple.com/support/kernel-extensions

Users can work around this temporarily by disabling SIP (Google it), but this weakens the security of your Mac. Make frequent backups and be extra vigilant. Only do this if you know what you’re doing. It should also be noted that this will only work up until the release of Big Sur, so you should set a reminder to re-enable SIP in September. Hopefully Valve will come up with a permanent fix soon.

Post edited to reflect later findings, deletions are in strikethrough and additions are underlined.

On macOS Big Sur (dev beta 1) running the Steam beta built on Jan 29, the Steam Input kext doesn't appear to work correctly.

In Big Picture with a controller connected via Bluetooth, Steam prompts the user to update the gamepad driver. This installation says it fails even though the kext appears to be installed and but not loaded correctly. Either way, something goes wrong.

The following behavior is observed with a Steam controller, and the kext is loaded installed (allowed in System Preferences, and shown by the "kextfind" command after a reboot):

Via the dongle, the controller connects to the computer but remains in "lizard mode." The controller and Steam client don't seem to know about each other's existence.

Via Bluetooth, the controller connects and appears to work at first. It works within the Big Picture controls (I can tell it's not "lizarding" and emulating the arrow keys because the right touch pad doesn't move the mouse). Steam recognizes the controller and allows me to access, modify, and save controller configurations.

Disclaimer: I can't test within games due to the platform detection issue also reported here, so instead I created a shortcut to launch Kerbal Space Program directly within Steam. The overlay and configuration still work this way.

Input from the game configuration has no affect. The controller HUD overlay shows keypresses that should be happening, but they don't register in KSP. Additionally, emulating a joystick has no effect, even though it's also visible in the controller HUD (tested by trying to assign an axis control in the KSP settings, which does work when an xbox controller is used).

It seems that the controller input works and is recognized throughout the system, however no emulated input is actually sent anywhere outside of steam.

I've enabled all of the privacy settings available for Steam in my security preferences, including accessibility control. So Steam should have permission to control other apps.

As it turns out, this was a result of System Integrity Protection being enabled. Disabling it, rebooting, and installing the gamepad driver loads it successfully, although the installer still says it failed.

[Potassium Ion]

After doing some more digging around, I figured out that the kext was installed, but not loaded (as indicated by kextstat), even though I had approved of it via System Preferences and rebooted multiple times.

The fix was to disable System Integrity Protection, and then go through Steam and update the gamepad driver again. The installer still says it failed, but after approving in system preferences and rebooting, it works fine. The controller works perfectly and the gamepad driver message goes away.

[Potassium Ion]

I’ve identified the issue. It’s because, as noted in the beta release notes, kexts that use deprecated KPIs (deprecation announced a year ago at WWDC19) don’t load unless SIP is disabled. This article contains more details for the developers, including information on how to transition to more supported APIs.

https://developer.apple.com/support/kernel-extensions

[BaconShrimpEyes]

After disabling SIP the install says it finishes successfully and (sometimes) prompts me to restart my system (not always, otherwise I relaunch Steam), but after doing so I still find my controllers don't work in-game where they used to in MacOS Catalina, and I'm still prompted to update the controller drivers every time Steam enters Big Picture mode.

[BaconShrimpEyes]

Originally posted by BaconShrimpEyes:

After disabling SIP the install says it finishes successfully and (sometimes) prompts me to restart my system (not always, otherwise I relaunch Steam), but after doing so I still find my controllers don't work in-game where they used to in MacOS Catalina, and I'm still prompted to update the controller drivers every time Steam enters Big Picture mode.

update: after installing beta 6 (which was released to the public beta a few days ago) it seems to be working as intended. I would like to re-enable SIP if possible so I'll probably do that at some point but my controller is working with Steam games again for now.

The install was more or less concurrent with a Steam beta client update. I can't say for certain which one caused the fix.

[robhearn]

Hi Potassium Ion. I've seen you respond a few times of the various discussions around this problem that I seem to be having too. I have the official release of Big Sur and have tried to update the input drivers by disabling SIP as in your instructions but still get no control in game, just in Big Picture Mode. Is this cos its the final release and not the beta as I inferred from your post? Bit disappointed. any other suggestions?

[Larothus]

I'm running it in Big Sur final release too (Steam stable, not beta). I gave up already with steam detecting and applying the right config for each game so I moved to configure a different desktop profiles instead. To make it work I had to disable SIP and leave it off. After that I installed everything, restart, and the desktop configs work once again.

I'm scared ♥♥♥♥♥♥♥♥ that Steam won't support steam input for mac in the future and that I'll lose the way 'm used to playing games.

[Cristian (CAZ)]

Hi.

I'm just stepping in because I have the same problem, exactly as described by Potassium Ion. I tried disabling SIP but the issue is still there.

Actually, I have observed a very intriguing situation. SIP is enabled:

1. I launch the installation of the Steam controller driver.
   
2. I never get prompted for the authorization in System Preferences.
   
3. The installation seems to complete correctly but the controller does not work with games.
   
4. I reboot in recovery mode and disable SIP
   
5. I reboot in normal mode <-- At this moment, the pop-up requesting authorization for the kext to be allowed in System Preferences, magically appears. I have not launched the installation or anything other than logging in. Anyway, even clicking "allow" still not solve the problem.

Repeating the installation with SIP disabled does not make the authorization request to pop-up and the loop repeats.

I have contacted Steam support and they just told me to watch for beta releases where maybe they would try to solve this issue. To me, it is still unsolved.

Bye.

[Charmander]

Just chiming in that I have exactly the same issue as described above. Consequence is that I basically just stopped playing games on Steam until it is fixed... hope Steam is able to fix it soon.

[ujimaflip]

I also have the same problem.. big sur has been out for a while now....

[kefyras347]

still a problem.

[emeralddaisy23]

Still a problem for me as well, I've submitted a support claim but I suspect that the issue cannot be fixed in Big Sur public release without Steam updating.

[florean]

I posted a workaround that's cleaner than just disabling SIP with some more details in a new discussion thread: https://steamcommunity.com/discussions/forum/2/3004429475624592660/.

[Cristian (CAZ)]

Thank you florean. Your workaround just makes it work again. It is very well explained and will be our solution until Steam corrects this error.

[Aenect]

Still an issue! Please fix valve!

[javiesg]

When will this be fixed? Is there anyone there at Valve reading this?