Asahi Linux - krun + FEX + Steam

README.md

Nothing to see here.

What you want is https://asahilinux.org/2024/10/aaa-gaming-on-asahi-linux/

But if you have previously followed this guide, use the following to switch:

Cleanup

rm -rf ~/.fex-emu
rm ~/.local/bin/{asahi-krun-overlay-fex-rootfs,FEXBash,krun,krun-guest,steam}
rm ~/.local/share/applications/steam.desktop
rm -rf ~/.local/share/asahi-krun
DBX_CONTAINER_MANAGER=podman distrobox rm asahi-krun

Install Steam (on the host)

sudo dnf upgrade --refresh
sudo dnf install --best --setopt=allow_vendor_change=true steam
sudo dnf remove dhcpcd

You might have to reboot the system.

coffee.md

If this guide was useful to you, please feel free to tip me.

• https://buymeacoffee.com/teohhanhui
• https://github.com/sponsors/teohhanhui

Help me find a job. I'm looking for a job in @rust-lang 🦀

Box64 is working on something called box32 which should be kinda like wow64 for Linux I would try packaging steam like you did for wine to use with box64 only 64 bit games would work until proton is updated to use wow64

I’m also tracking this here ptitSeb/box64#1780

Seems to be steam doesn’t boot with this setup anymore for me. Tried even a full reinstall with no fix. I tried to see if it was SElinux or steam runtime but couldn’t get it going.

run.sh[376]: steam-runtime-identify-library-abi --ldconfig-paths failed, falling back to ldconfig run.sh[376]: Warning: An unexpected error occurred while executing “/sbin/ldconfig -XNv”, the status was 139
mkdir: /home/asahiuser/local/share/Steam/ubuntu12_32/steam-runtime/lib/x86_64-linux-gnu/libselinux.so.1: no version information available (required by mkdir)

@Spidy123222 Is that a copy and paste error in the error output? It's supposed to be ~/.local/share/Steam, not ~/local/share/Steam 🤔

By the way, did you make sure to use the updated versions of all the wrapper scripts from this gist? (e.g. ~/.local/bin/steam)

Hi,thank you for doing a lot for us!
When I installed box64 and wine and try to install a windows version steam,it says

0024:err:environ:init_peb starting L"Z:\\home\\orange\\SteamSetup.exe" in experimental wow64 mode
wine: failed to load L"\\??\\C:\\windows\\syswow64\\ntdll.dll" error c0000135

And I found there is no file generated in .wine/drive_c/windows/syswow64
What should I do? I regenerated wineprefix but it does not work.

@orange200213 I'm not sure, but the file is there for me. Anyway, I didn't manage to get the Windows version of Steam working.

@orange200213 I'm not sure, but the file is there for me. Anyway, I didn't manage to get the Windows version of Steam working.
I tried wine-9.17-wow64, steam can be installed but when steam upgrades, it seems that it can not find ProgramData so it can not be upgraded.But I think we will soon play steam games on asahi in the future.Thank you!

"No IPv6 nameserver available for NDP/DHCPv6
Using default interface naming scheme 'v255'.
INFO sommelier-scope-timer.cc:30 ~ScopeTimer: configure event loop: 0.000354208 seconds
INFO sommelier-scope-timer.cc:30 ~ScopeTimer: drm device: 0.0461986 seconds
INFO sommelier-scope-timer.cc:30 ~ScopeTimer: connect display: 2.0542e-05 seconds
INFO sommelier-scope-timer.cc:30 ~ScopeTimer: client create: 1.7083e-05 seconds
INFO sommelier-scope-timer.cc:30 ~ScopeTimer: display implementation: 2.209e-06 seconds
INFO sommelier-scope-timer.cc:30 ~ScopeTimer: spawn xwayland: 0.000210708 seconds
Failed to execute "FEXRootFSFetcher" as child process: No such file or directory (os error 2)
The XKEYBOARD keymap compiler (xkbcomp) reports:

Warning: Unsupported maximum keycode 708, clipping.
X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
FATAL sommelier.cc:2960 sl_handle_x_connection_event: got error or hangup (mask 5) on X connection, exiting"
I get this error when running the rootfs command
I cannot do the RootFS step, and this command worked before but not anymore.

• Phoronix article: "Fedora 42 On 64-bit ARM Might Make It Seamless To Run x86/x86_64 Programs"
• https://fedoraproject.org/wiki/Changes/FEX
• https://pagure.io/fedora-asahi/fex-emu-overlay-mesa/tree/main

but how to follow this guide?

@jih9uhuuh9 Read from top to bottom (sometimes there are links that jump you back to a previous section because I don't want to repeat myself). Run one command at a time. You can stop when you come to the optional sections.

Thank you for writing this guide ! I succeeded to run steam and games using it a few weeks ago.
But now i'm unable to complete the FEX RootFS step on a new install of Asahi Fedora Remix.

krun FEXRootFSFetcher -y -x --distro-name=fedora --distro-version=40 returns

Failed to execute "FEXRootFSFetcher" as child process: No such file or directory (os error 2)
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
FATAL <sommelier.cc:2960> sl_handle_x_connection_event: got error or hangup (mask 5) on X connection, exiting

Should I use an older version of FEX ?
@jih9uhuuh9 Have you found a solution for that error ?

EDIT:
It worked with that version of fex-emu

If you end up here while fex-emu is not in the Fedora stable repo yet, you can download fex-emu-2408-1.fc40.aarch64.rpm from https://koji.fedoraproject.org/koji/buildinfo?buildID=2537498 and do

sudo dnf install ~/Downloads/fex-emu-2408-1.fc40.aarch64.rpm --exclude erofs-fuse --exclude erofs-utils

You have to install fex-emu-utils.

krun seems to be packaged in fedora now

I just tried to follow this guide in a fedora toolbox using the packaged krun but I get /home/alex/.local/bin/krun: line 25: exec: distrobox-host-exec: not found is there any reason why it couldn't be shouldn't be compatible with toolbox as well? I think it has a similar command called toolbox run

To get it to use version 40 you need to do -r 40 because for some reason toolbox is stuck on 38 on asahi linux

📦[asynth@asahi-krun krun]$ krun FEXRootFSFetcher -y -x --distro-name=fedora --distro-version=40
thread '<unnamed>' panicked at src/vmm/src/builder.rs:361:49:
called `Result::unwrap()` on an `Err` value: TooLarge
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 4282217296
Aborted (core dumped)

I'm getting an error on the Set up FEX RootFS step.

Hi

Running Fedora/Plasma/FEX. Install through two errors - filesystem and dbus. I get a dbus error on steam startup. Is there anything i can do apart from start again?

(zenity:392): Gtk-WARNING **: 19:52:42.824: Unable to acquire session bus: Error spawning command line ?dbus-launch --autolaunch=1a6323469f774f3286abe8442f995381 --binary-syntax --close-stderr?: Child process exited with code 1

Gareth

@garethwebber:

I get a dbus error on steam startup.

That's "normal". If Steam is not running for you, you'd have to find the relevant error messages... (You can check in the Steam logs to see more of what's actually going on.)

Side note: I haven't been updating this guide lately, so YMMV.

Thanks for coming back.

I see a window open and show it downloading updates. I then get a white W in yellow in my launcher bar but no Steam main window appear. Will keep digging.

Gareth

Removed :3

Unfortunately the recent change of adding the new muvm method from asahi. It doesn’t install the rootfs or socat. I got socat but rootfs is a mystery as I’ve tried 7 times to reinstall it.

@Spidy123222 Follow the cleanup steps, then sudo dnf upgrade --refresh && sudo dnf install steam

(FEX RootFS will be installed as a dependency.)

Then just run steam (or look for the steam train icon from the launcher lol)

@Spidy123222 Follow the cleanup steps, then sudo dnf upgrade --refresh && sudo dnf install steam

(FEX RootFS will be installed as a dependency.)

Then just run steam (or look for the steam train icon from the launcher lol)

These steps were already used with no difference. Couldn’t I just install the rootfs separately.

@Spidy123222 Then I'm afraid you'll need to share more details. Please help us help you.

@Spidy123222 Then I'm afraid you'll need to share more details. Please help us help you.

I already told details in fex-emu discord but I’ll show it here. When booting the steam train thing from terminal it specified it cannot find the rootfs /home/asahiuser/•fex-emu/RootFS/Fedora_40-asahi-krun

the fex-emu directory is very empty and there is no RootFS folder.

image of the messages. https://media.discordapp.net/attachments/702130548419723294/1294214612358791220/Screenshot_from_2024-10-11_01-25-48.png?ex=670a32c8&is=6708e148&hm=7dbf68c39f35e49f3a0e70725cc8c59fe654a10157ee4b29d30c790bc02706dc&

@Spidy123222 Can you confirm you've run

rm -rf ~/.fex-emu

The only explanation for why it's trying to look for that RootFS is because you have leftover fex config from my guide.

@Spidy123222 Can you confirm you've run

rm -rf ~/.fex-emu

The only explanation for why it's trying to look for that RootFS is because you have leftover fex config from my guide.

Same results after reinstalling steam rpm.

@Spidy123222 Can you run all of the commands in the cleanup steps please? (I see you were still trying to use the asahi-krun container. It should not be used anymore.)

And then run:

sudo dnf upgrade --refresh
sudo dnf install --best --setopt=allow_vendor_change=true steam

@Spidy123222 Can you run all of the commands in the cleanup steps please? (I see you were still trying to use the asahi-krun container. It should not be used anymore.)

And then run:

sudo dnf upgrade --refresh
sudo dnf install --best --setopt=allow_vendor_change=true steam

That fixed it. Interesting. Also btw for the distrobox removal. Do --force at end as it fails if not.