Osxfuse: Benjamin Fleischer Extension Won't Install on M1 MacBook Pro

[markbyrn]

I'm running the 11.1 Beta (20C5048k) on a M1 Macbook Pro. When installing MacFuse 4.0.4, the Benjamin Fleischer extension is blocked and so use the Security & Privacy preference to allow it. After allowing, the OS wants a reboot to rebuild the extension library, and about 80% through the reboot process, a silent failure occurs and the system reboots by itself. Head back to the Security & Privacy preference pane and it's still asking to allow the Benjamin Fleischer extension. Rinse & repeat; then uninstall MacFuse to get it to stop asking to allow the Benjamin Fleischer extension.

[djkcel]

I'm running the same os on an M1 MacBook Air.

I had to boot into recovery mode and then launch the "Startup Security Utility." From here I enabled kernel extensions and rebooted, after which I was able to "allow" in the security prefpane. However it still doesn't work. When I try to actually mount a volume in terminal I get

"kext load failed: -603947007"

After trying to manually load the kext, I get:

Executing: /usr/bin/kmutil load --bundle-path /Library/Filesystems/osxfuse.fs/Contents/Extensions/10.11/osxfuse.kext
Error Domain=KMErrorDomain Code=71 "Incompatible architecture: Binary is for x86_64, but needed arch arm64e" UserInfo={NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e}

I fear that this software may not be compatible with the new Apple M1 ARM chips but I'll look around a little more.

[vijaynr]

@djkcel are you sure you are loading the correct kext? I can see osxfuse is renamed to macfuse in versions 4+.
The kext path would be something like this /Library/Filesystems/macfuse.fs/Contents/Extensions/11/macfuse.kext

The one you are trying to load might have Intel only support. Please check.

[bfleischer]

@djkcel The version of FUSE you are using is not compatible with Apple Silicon Macs. Please upgrade to macFUSE 4

[tommythorn]

UPDATE 2: I don't know what I did wrong butkmutil unload --bundle-path /Library/Filesystems/macfuse.fs/Contents/Extensions/11/macfuse.kext _does_ work and will carry me over until the next version (now to see if I can make Keybase work with it).

[NewAlexandria]

I have this issue, but with version 4.0.4. I am testing on a new MacBookPro (silicon / M1), Big Sur (obviously).

• I tried installing normally + security panel to accept. (not-working)
• I also tried csrutil disable after an uninstall of macfuse, then reinstalling, security panel allow, and related requisite reboots (not-working)
• I tried manually loading the kext via the terminal. This worked to stop the security panel alerts (the 'allow app'), but my normal client apps (Keybase) still won't run.

How can I confirm if MacFUSE is working correctly? I don't normally use this library otherwise, and there's no 'hello world' that I see in docs. Thanks

[veganmaister]

@djkcel The version of FUSE you are using is not compatible with Apple Silicon Macs. Please upgrade to macFUSE 4

I’m experiencing the same problem with 4.0.4 which has subsequently broken pCloud.

[veganmaister]

Is there any way we can help fast track the resolution here? I find it astounding how a little OS extension has completely broken productivity on M1 Macs.

[bfleischer]

macFUSE 4 is required on M1 Macs. Older releases of FUSE do not support the new processor architecture. Please keep in mind that Rosetta, which translates old Intel apps to run on M1 Macs, does not support translating kernel extensions. That's why you will need to upgrade to macFUSE 4.

@veganmaister There is no need downvote this. It's a matter of fact.

In macOS 11 Apple completely rewrote the Kext Manager component of macOS. Unfortunately, with all new software there are bugs. Since the first release of macOS 11, I raised 11 issues with Apple. Four of the issues have been addressed in the meantime. Seven are currently open. For three of these seven remaining issues, FUSE contains workarounds. This leaves 4 issues that can prevent third-party kernel extension from being loaded. This is true for macFUSE and pCloud.

[tommythorn]

@bfleischer Thanks for the informative update. This is the kind of things we should expect with the M1 transition and I'm glad progress is being made. Is subscribing to this bug the best way to monitor the progress?