Commit Graph
845 Commits
Author SHA1 Message Date
The412Banner a99843e326 Merge remote-tracking branch 'org/main' into feat/x86-64-steam-client 2026-10-02 19:50:02 -04:00
The412Banner 9ca4adc9c6 Lossless: also take Lossless.dll from the x86-64 client's library
Lossless Scaling installed from the x86-64 client lands in its own
Steam folder, so LSFG stayed greyed out ("Install Lossless Scaling in
Steam") although it was installed.
2026-10-02 19:42:51 -04:00
The412Banner fd1d9de636 Progress log: L4D2 on the GPU, 51 fps, official VAC-secured server 2026-10-02 19:37:53 -04:00
The412Banner d5b766d26c x86-64 client: no 32-bit controller reader in games, for real; game-gpu.local
The preload line used $LIB, so 32-bit programs still got libfakeinput:
FEX falls through to the session's own i386 copy when the rootfs has
none. Its fake devices reach the game's SDL2 through udev with a missing
attribute and SDL strdup()s the NULL - the Left 4 Dead 2 crash right
after GL start-up, in software and on the GPU alike (found with the
segvlog diagnostic). The line now names the x86_64 copy. DroidDeck
direct also reads game-gpu.local after the generated game-gpu.env.
2026-10-02 19:33:54 -04:00
The412Banner 8ecadacd12 Diagnostics: SIGSEGV logger also lists code addresses on the stack 2026-10-02 19:31:24 -04:00
The412Banner 5f4b62fc8b Diagnostics workflow: also on push of its files 2026-10-02 19:29:01 -04:00
The412Banner 43da1b8d1f Diagnostics: SIGSEGV logger preload for x86 guest programs
Writes the fault address, the instruction pointer and a backtrace with
module offsets to SEGVLOG_FILE; built by its own small workflow.
2026-10-02 19:28:49 -04:00
The412Banner 8589951aea x86-64 client: the GPU for games only, client in software
With FEX's thunks on for every x86 process the client's browser GPU
process gets the host drivers even under -cef-disable-gpu, fails and
dies, and the client never opens a window. The client keeps the
software setup that works; the launcher saves the session's GPU
settings and DroidDeck direct hands them and the thunks to the game.
2026-10-02 19:16:52 -04:00
The412Banner 0b3bc31397 x86-64 client: browser in software, games on the GPU
On the GPU the client's browser GPU process needs libgbm, which FEX does
not thunk; the guest GBM cannot export buffers on the Adreno and the GPU
process restarts forever (no first frame). Games keep the thunked GL and
Vulkan. BL_X64_CEF_GPU=1 still tries the GPU browser.
2026-10-02 19:05:42 -04:00
The412Banner 4374d6c7d7 Progress log: x86-64 client runs L4D2 online, thunks, launch path (2026-10-02 evening) 2026-10-02 18:57:46 -04:00
The412Banner fccb48773f DroidDeck direct: -condebug for Source games
Their console then lands in console.log, which says which server they
joined and whether it is VAC secure.
2026-10-02 18:57:08 -04:00
The412Banner a1bb788fa7 bannerlator-steam-x64: no 32-bit controller reader yet; no GL threading in software
The i386 libfakeinput crashes Left 4 Dead 2 right after its GL start-up
(device: with it removed the game loads and joins an online game); only
the session shim for 32-bit programs until it is fixed. DroidDeck direct
turns the session's mesa_glthread off when GL is software.
2026-10-02 18:56:36 -04:00
The412Banner f65e6e72d6 bannerlator-steam-x64: a launch client that runs the command here
The x86 client, believing itself inside the SteamRT container, starts
games through steam-runtime-launch-client --alongside-steam -- COMMAND.
Valve's needs a launcher service on the session bus (none: the game ended
at once); none on PATH fails the launch (No such file). The shim's own
runs the command (honouring --directory/--env) - L4D2's launch chain then
starts (device, 18:48).
2026-10-02 18:48:19 -04:00
The412Banner 0c0bcb49a4 bannerlator-steam-x64: steam-runtime-launch-client off the PATH again
Found, it made the client hand L4D2 to pressure-vessel's launcher service
over a session bus that is not there, and the game ended at once
(device, 18:45). Not found, the client runs the game itself.
2026-10-02 18:46:41 -04:00
The412Banner c36d38b267 bannerlator-steam-x64: FEX fex-2609-r3 (with host thunks)
The x86-64 client then draws on the GPU (Vulkan/GL thunked to Turnip
and Mesa); BL_X64_SOFTWARE=1 keeps it in software.
2026-10-02 18:45:37 -04:00
The412Banner 9c2f75f7f2 session: hand the running client a steam:// URL from the launch dir
A URL written to $BL_LAUNCH_DIR/steam-url goes to the running client, as
the stop request does: a game can be started (steam://rungameid/...)
without touching the screen, for either client.
2026-10-02 18:45:28 -04:00
The412Banner 48a1a4517a x86-64 client: draw on the GPU when FEX has its host thunks
With FEX's host thunks installed, the client runs with a ThunksDB of GL
and Vulkan (FEX_THUNKCONFIG): its Vulkan and GL calls go to the runtime's
own Turnip and Mesa with the session's settings for them, and it gets the
arm64 client's Chromium flags (-cef-force-gpu, ANGLE on Vulkan). Without
the thunks, or with BL_X64_SOFTWARE=1, software rendering as before.
'bannerlator-steam-x64 --gpu' answers for the session.
2026-10-02 18:37:43 -04:00
The412Banner 8f3d8d0afa FEX build: the x86 sysroot for the guest thunks' toolchains
The guest halves linked without it on the arm64 builder (no crtbeginS.o,
no libgcc).
fex-2609-r3
2026-10-02 18:36:41 -04:00
The412Banner 4ee3463c20 FEX build: create the x86 sysroot's package cache 2026-10-02 18:31:41 -04:00
The412Banner 7b836d52c3 fastpath: stand down in FEX only for 32-bit programs
libblfastpath broke FEX's 32-bit mode (SIGILL at start), so the x86-64
client ran with PROOT_FP_OFF=1 and every one of its syscalls went the
slow ptrace way. In a FEX process it now reads the program FEX is about
to run and stays on for a 64-bit ELF only. bannerlator-steam-x64 drops the
blanket switch (BL_X64_FP_OFF=1 brings it back).
2026-10-02 18:31:31 -04:00
The412Banner 5530d8aa70 FEX build: optional host thunks
FEX_THUNKS=1 (build-fex.yml 'thunks' input) builds FEX's host thunks: the
arm64 half against the runtime's graphics dev packages, the x86 and i686
guest halves with clang against a sysroot of Arch Linux x86_64 and
multilib packages unpacked by pacman (not run). With them an x86 program's
Vulkan, GL, X11, Wayland and DRM calls reach the runtime's own libraries -
Turnip and Mesa on the GPU - instead of llvmpipe.
2026-10-02 18:30:29 -04:00
The412Banner 822ca6405f build: the i386 preloads at the very end of the preload step
The step also builds libtracefs with the aarch64 cross compiler after the
first move; gcc-multilib must come after all of them.
2026-10-02 18:20:48 -04:00
The412Banner cca4ff3746 build: the i386 preloads after every aarch64 one
gcc-multilib conflicts with the aarch64 cross compiler and removed it, so
the next aarch64 build in the step failed (exit 127).
2026-10-02 18:20:10 -04:00
The412Banner 49f1ceaadc x86-64 client: run native Linux games, 32-bit preloads, no Deck flags
- DroidDeck direct: a compatibility tool the x86 client gets in its own
  compatibilitytools.d, running a native Linux game with Valve's scout
  library runtime under FEX instead of the Steam Linux Runtime container
  (pressure-vessel, which needs bwrap). Left 4 Dead 2 (BL_X64_DIRECT_APPS)
  is mapped to it in the x86 config while that client is not running.
- The session shim and the controller reader are also built for i386 and
  preloaded through glibc's $LIB, so 32-bit games get them too.
- The runtime's bin/ on the client's PATH (steam-runtime-launch-client).
- No -steamdeck -steamos3 for the x86 client yet: its SteamOS audio
  manager aborts on the runtime's PulseAudio 13 (pa_operation_get_state).
2026-10-02 18:16:17 -04:00
Kurt Himebauch 7b20b70c6b Merge pull request #151 from Droid-Deck/feat/android-clipboard 2026-10-02 17:47:25 -04:00
xXJsonDeruloXx 86207f9d0e Record visible Android copy and Steam paste test on Thor 2026-10-02 17:38:16 -04:00
xXJsonDeruloXx eda5ece382 Add Android clipboard text paste into Steam sessions 2026-10-02 17:29:41 -04:00
The412Banner 2d2ffd9d05 Progress log: x86-64 client controllers, online, Play-button choice 2026-10-02 17:28:49 -04:00
The412Banner 05d74c8a1f Steam session: choose the ARM64 or the x86-64 client
A Steam setting (Client > Steam client: ARM64, the default, or x86-64
under FEX, experimental) sent as BL_STEAM_CLIENT_ARCH. With x86_64 the
session starts Valve's x86-64 client through bannerlator-steam-x64 in its
own home instead of steamrtarm64/steam, so the Play button gets every fix
the session has (system bus and NetworkManager stand-in, gamescope, Deck
and Big Picture UI, stale locks, branch sync, restart loop, stop watcher,
logs, core pinning); what is only for the arm64 client (ARM64 Proton and
its mapping, redist seeding, Decky, the steamclient.so probes) is skipped.
bannerlator-steam-x64 gains --prepare and --exec for that; its own library
replaces the shared steamapps link.
2026-10-02 17:28:00 -04:00
The412Banner cb2334da4e bannerlator-steam-x64: the app's FEX preset for the client
The client ran on FEX's defaults (half-barrier TSO, full-precision x87).
Use the app's default game preset, PERFORMANCE_TSO (WinNative's), as the
FEX_* variables both FEX builds read; values already set win.
2026-10-02 17:24:24 -04:00
The412Banner 8a89387ef8 x86-64 client: the session's fixes for the arm64 client
From an audit of bannerlator-session against bannerlator-steam-x64:
- a system bus and the NetworkManager stand-in when none is up, stopped
  with the client: the client showed no connection on the desktop
- stale .crash/steam.pid/htmlcache Singleton* cleared before a start
- package/beta matched to -clientbeta before every start (rc=42 loop)
- BL_CLIENT_CPUS re-pinning of the client and its web helper every 5 s
- pathcache.c and perms.c also recognise steamrt64 (the path cache saved
  most of the arm64 client's start-up; the write override covers its
  self-update)
2026-10-02 16:59:56 -04:00
The412Banner 47e528102d x86-64 client: the controller reader for x86 programs
The session's pads exist for a guest program only through libfakeinput
(the FAKE_EVDEV_* rings), which was built for arm64 alone, so the x86
client saw no controller. Build it natively for x86-64 too, stage it, and
preload it through the FEX rootfs next to the session shim.
2026-10-02 16:52:53 -04:00
The412Banner 1d90448924 Progress log: the x86-64 Steam client under FEX (2026-10-02) 2026-10-02 16:52:01 -04:00
The412Banner 131ba72ee5 x86-64 client: hide the tracer only from tier0's status reads
Hiding it from the whole x86 web helper got it past tier0 (message loop,
BrowserCreated) but then Chromium trapped on the status descriptor it
opened itself, now a memfd copy - which is the other reason the shim
leaves the web helper alone. With BL_WEBHELPER_HIDE_TRACER=1 only opens
called from libtier0_s.so get the copy; Chromium's get procfs.
2026-10-02 16:28:43 -04:00
The412Banner b2e3a3a5ea x86-64 client: hide proot's tracer from the web helper too
Traced per process through FEXServer: every x86 web helper read
/proc/self/status (the string sits in libtier0_s.so) and died of SIGTRAP
right after. proot is a tracer, so tier0 believes a debugger is attached
and breaks into it with int3 on the first failed assertion. The arm64
build only issues a stray svc there, which is why the session shim leaves
the arm64 web helper reading the real TracerPid. BL_WEBHELPER_HIDE_TRACER=1,
set by bannerlator-steam-x64, serves the x86 one TracerPid 0 as well.
2026-10-02 16:17:55 -04:00
Kurt Himebauch 3404bbc128 Merge pull request #150 from Droid-Deck/feat/steam-native-network
Show Android Wi-Fi and cellular networks in Steam BPM
2026-10-02 16:16:46 -04:00
The412Banner 254e1db969 bannerlator-steam-x64: BL_FEXSERVER_LOG for pid-tagged FEX logs
A diagnostic: FEX's file log is opened without O_APPEND, so each process
overwrites the last. Through a foreground FEXServer every line carries
the pid and tid it came from.
2026-10-02 16:14:31 -04:00
xXJsonDeruloXx b5a431aa3c Merge remote-tracking branch 'origin/main' into feat/steam-native-network 2026-10-02 16:11:04 -04:00
xXJsonDeruloXx 49249f6541 Add optional Wi-Fi discovery permission flow in Steam settings 2026-10-02 16:05:47 -04:00
The412Banner 34e7191e02 bannerlator-steam-x64: BL_FEX picks the FEX build that runs the client
For diagnostics: a DEBUG_STRACE build traces the client and everything it
starts.
2026-10-02 15:49:32 -04:00
The412Banner 5dfa6f43ed bannerlator-steam-x64: webhelper on Wayland
On X11 Chromium sets up GBM on the render node Xwayland hands out over
DRI3 even with the GPU disabled, loops on KMS dumb-buffer ioctls against
the KGSL device, and never creates the SteamUI browser; the client
restarted it every 10 s. Without a GPU, Chromium's Wayland backend draws
to shared-memory buffers.
2026-10-02 15:46:35 -04:00
The412Banner 2ff30ab4bb bannerlator-steam-x64: no DRI3 for x86 Mesa
Hiding /dev/dri was not enough: Xwayland hands the render node out over
DRI3, and llvmpipe then loops on KMS dumb-buffer ioctls against the KGSL
device. LIBGL_DRI3_DISABLE=1 presents through plain X.
2026-10-02 15:44:41 -04:00
The412Banner aa27921dee bannerlator-steam-x64: hide the GPU node from x86 programs
x86 Mesa and the Vulkan loader still enumerated /dev/dri, found the
session's KGSL node and looped on it (KMS dumb-buffer ioctls), and the
webhelper never brought a browser up; the client restarted it every
10 s. FEX resolves paths in the rootfs first, so an empty /dev/dri there
leaves llvmpipe and lavapipe.
2026-10-02 15:43:52 -04:00
xXJsonDeruloXx 5614621d6e Expose Android Wi-Fi names and nearby networks to Steam 2026-10-02 15:39:49 -04:00
The412Banner 581a7d1557 bannerlator-steam-x64: software GL and the rootfs's Vulkan for the x86 client
The desktop exports zink over the arm64 Turnip ICD (GALLIUM_DRIVER,
MESA_LOADER_DRIVER_OVERRIDE, VK_ICD_FILENAMES); x86 Mesa found no driver
and the client died on glXChooseVisual. Clear them and use llvmpipe.
2026-10-02 15:31:02 -04:00
The412Banner e07e436857 bannerlator-steam-x64: SteamRT libraries only where the rootfs has none
LD_LIBRARY_PATH beats the system folders regardless of order, so the
platform's own older libc.so.6 shadowed the rootfs's (GLIBC_2.38 not
found). Keep only the libraries the rootfs lacks.
2026-10-02 15:29:19 -04:00
The412Banner e0348adc02 bannerlator-steam-x64: soname links for the SteamRT platform libraries
Valve's platform runtime files carry each library under its full version
only; pressure-vessel makes the soname links when it builds a container.
Link them into a folder of our own and run the rootfs's ldconfig -n there,
so libgtk-x11-2.0.so.0 and the rest resolve.
2026-10-02 15:28:46 -04:00
The412Banner a7b4d79c15 bannerlator-steam-x64: the SteamRT platform libraries after the rootfs's
steamui.so needs GTK 2 (libgtk-x11-2.0.so.0), which the SteamRT container
provides and FEX's Ubuntu 24.04 rootfs does not. Append Valve's own
steamrt3c platform library directories to the client's library path,
after the rootfs.
2026-10-02 15:27:38 -04:00
The412Banner ae96d7fdaf bannerlator-steam-x64: stay out of pressure-vessel, restart on request
After its self-update the x86 client re-executes itself in the SteamRT
container through pressure-vessel-wrap, which needs bwrap. The FEX rootfs
with the client's steamrt64 libraries is the container here, as proot is
for the arm64 client: set the client's recursion guard. Restart on exit
code 42 the way steam.sh does.
2026-10-02 15:26:34 -04:00
The412Banner e5145bfad5 x86-64 client: System V IPC shim for x86 programs, and staging
The x86 client stops at start on a tier0 assertion: semget answers ENOSYS,
as Android kernels have no System V IPC (traced with a DEBUG_STRACE FEX).
The session shim that gives the arm64 client its semaphores is now also
built as native x86-64 and preloaded through the FEX rootfs's own
ld.so.preload. SessionFiles stages it and bannerlator-steam-x64 into
installed runtimes.
2026-10-02 15:16:24 -04:00