FEXLoader: error: no such option: -d when running Wine 6.0.3 on Ubuntu 22.04 ARM64

[qddone]

"Hello,

I am running Ubuntu 22.04 ARM64 (on a Neoverse N1 CPU) and using FEX Emu (version 2507.1j). I have installed Wine 6.0.3 from Ubuntu's official ARM repositories (6.0.3repack-1).

I have successfully configured FEX Emu's binfmt_misc entries, and ls /proc/sys/fs/binfmt_misc/ now correctly shows FEX-x86 and FEX-x86_64. FEXLoader itself also has all its necessary ARM64 host dependencies.

However, when I attempt to run winecfg (or other Wine-related commands like wineboot), I consistently encounter the following error:

Usage: FEXLoader [options]
FEXLoader: error: no such option: -d

I've verified that -d is not a valid option for FEXLoader according to FEXLoader --help.

This issue isn't exclusive to Wine; running ldd $(which FEXLoader) from within FEXBash also produces a similar error: FEXLoader: error: no such option: --verify.

It appears that Wine 6.0.3 (and potentially other tools in the emulated environment) is passing unrecognized command-line arguments to FEXLoader.

Could you please advise on how to resolve this argument incompatibility?

Is there a specific Wine version (different from Ubuntu's 6.0.3) that is recommended or known to be compatible with FEX Emu without passing these problematic arguments?

Are there any FEX Emu configuration options or environment variables that can instruct FEXLoader to ignore unknown command-line arguments, or specifically handle Wine's invocation?

Are there any FEX Emu-specific Wine builds or patches that address this?

Thank you for your time and assistance!"

[qddone]

Created the binfmt_misc configuration file for FEX Emu:
a file named fex-emu.conf in /etc/binfmt.d/.

x86 (32-bit) FEX Emu registration

:FEX-x86:M:0:MZ::/usr/bin/FEXLoader:

x86_64 (64-bit) FEX Emu registration

:FEX-x86_64:M:0:\x7fELF\x02\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x3e\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\xff\xff\xfe\xff\xff\xff:/usr/bin/FEXLoader:

and not work

[Sonicadvance1]

Something is wrong with your binfmt_misc files. It should be using FEXInterpreter not FEXLoader.
Not sure why you're using your own crafted binfmt_misc files when we provide our own.

As for why arguments are complaining, again use FEXInterpreter instead of FEXLoader

[qddone]

You have successfully configured FEX Emu's binfmt_misc entries! The output ls /proc/sys/fs/binfmt_misc/ now clearly shows FEX-x86 and FEX-x86_64, which means your kernel is correctly configured to use FEX Emu for x86 binaries.

You've also confirmed that FEXLoader itself has all its necessary host ARM64 libraries when checked from your native shell.

The Remaining Problem: FEXLoader Rejecting Arguments

The consistent error message FEXLoader: error: no such option: -d (when running Wine commands like winecfg) and FEXLoader: error: no such option: --verify (when running ldd on an x86 binary inside FEXBash) indicates a clear issue:

FEX Emu is now being successfully invoked to emulate x86 binaries.

However, FEXLoader is being passed arguments it doesn't recognize or support by the calling application (Wine, or ldd in the FEXBash environment).

Since FEXLoader --help explicitly shows no -d or --verify options, FEX Emu is behaving strictly by rejecting these unknown arguments, which prevents Wine from initializing.

What to Do Next:

This issue is now at the boundary of Wine's internal invocation logic and FEX Emu's argument parsing. The solution must come from either finding a Wine build that is compatible with FEX Emu's invocation requirements, or a FEX Emu configuration that makes it more lenient with arguments.

As I cannot directly browse or interact with private communities or dynamically search content not indexed by standard web searches, the most effective next step for you is to directly engage with the FEX Emu community.

Here's a precise question to post on the FEX Emu GitHub Discussions (https://github.com/FEX-Emu/FEX/discussions) or their Discord server (https://discord.gg/fexemu):

Subject: FEXLoader: error: no such option: -d when running Wine 6.0.3 on Ubuntu 22.04 ARM64

Body:

"Hello,

I am running Ubuntu 22.04 ARM64 (on a Neoverse N1 CPU) and using FEX Emu (version 2507.1j). I have installed Wine 6.0.3 from Ubuntu's official ARM repositories (6.0.3repack-1).

I have successfully configured FEX Emu's binfmt_misc entries, and ls /proc/sys/fs/binfmt_misc/ now correctly shows FEX-x86 and FEX-x86_64. FEXLoader itself also has all its necessary ARM64 host dependencies.

However, when I attempt to run winecfg (or other Wine-related commands like wineboot), I consistently encounter the following error:

Generated code
Usage: FEXLoader [options]
FEXLoader: error: no such option: -d

I've verified that -d is not a valid option for FEXLoader according to FEXLoader --help.

This issue isn't exclusive to Wine; running ldd $(which FEXLoader) from within FEXBash also produces a similar error: FEXLoader: error: no such option: --verify.

It appears that Wine 6.0.3 (and potentially other tools in the emulated environment) is passing unrecognized command-line arguments to FEXLoader.

Could you please advise on how to resolve this argument incompatibility?

Is there a specific Wine version (different from Ubuntu's 6.0.3) that is recommended or known to be compatible with FEX Emu without passing these problematic arguments?

Are there any FEX Emu configuration options or environment variables that can instruct FEXLoader to ignore unknown command-line arguments, or specifically handle Wine's invocation?

Are there any FEX Emu-specific Wine builds or patches that address this?

Thank you for your time and assistance!"

This detailed explanation will provide the FEX Emu community with all the information they need to help you. They are the experts on FEX Emu's internal workings and compatibility.

[Sonicadvance1]

Okay, I don't know what this remaining response is but I've answered your question. Stop using FEXLoader, use FEXInterpreter.

[qddone]

Excellent! This is fantastic news and a major breakthrough!

The output from cat /proc/sys/fs/binfmt_misc/FEX-x86 and FEX-x86_64 explicitly confirms that the interpreter field for both is now correctly set to /usr/bin/FEXInterpreter.

This means:

Your binfmt_misc setup for FEX Emu is finally correct!

The kernel will now properly send x86 (32-bit) and x86_64 (64-bit) ELF binaries to FEXInterpreter for emulation.

This directly implements the FEX Emu maintainer's advice.

The previous FEXLoader: error: no such option: -d and --verify issues should now be resolved, as Wine (and ldd) will now be invoking FEXInterpreter which is designed to handle those arguments or simply operate correctly in this context.

Next Crucial Step: Re-initialize Wine Prefix
Because your Wine prefix was created and used while the binfmt_misc setup was incorrect (or pointing to FEXLoader improperly), it's highly likely that the existing ~/.wine directory is in a corrupted or misconfigured state. You need to start Wine fresh.

---

wine refreshed and this is the result after winecfg window changed from windows 7 to windows 10, pressed apply and OK.

The very first command I need to install Gecko and this is the result:

FEXBash-ubuntu@repeat:> wine msiexec /i https://dl.winehq.org/wine/wine-gecko/2.47/wine-gecko-2.47-x86.msi
002c:err:wineboot:process_run_key Error running cmd L"C:\windows\system32\winemenubuilder.exe -a -r" (2).
0048:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
0048:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
0048:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0050:err:crypt:CRYPT_ImportSystemRootCertsToReg Failed to import system certs into registry, 00000057
FEXBash-ubuntu@repeat:> 0048:err:ole:start_rpcss Failed to start RpcSs service

---

You are still encountering the same set of errors, specifically the 002c:err:wineboot:process_run_key Error running cmd ... (2) and the OLE/RPC errors. This indicates that Wine's initial setup and its internal processes are still failing to execute properly, even though binfmt_misc is now correctly configured to point to FEXInterpreter.

This is highly unexpected if FEXInterpreter is truly handling Wine's x86 processes without issue. It suggests either:

FEXInterpreter is failing internally when trying to run Wine's core components (like winemenubuilder.exe), but it's not printing its own specific error messages.

The Wine 6.0.3 installation itself (from Ubuntu's ARM repos) has a deeper incompatibility with FEX Emu's emulation, even when FEXInterpreter is correctly invoked.

The Wine prefix ~/.wine was not correctly re-initialized after the binfmt_misc fix.