Waydroid/Kernel Modules Failing to Load on Standard Kernel (binder_linux "busy", ashmem_linux "not found")

General system Kernel, boot, graphics & hardware
1

Hello,

I am trying to get Waydroid running on my EndeavourOS system and am running into a very strange issue with the required kernel modules. Even after extensive troubleshooting, I am stuck.

My System

  • Operating System & Version:NAME="EndeavourOS" PRETTY_NAME="EndeavourOS" ID="endeavouros" ID_LIKE="arch" BUILD_ID=rolling
  • Linux Kernel Version:6.14.11-x64v3-xanmod1-1(Note: I have also installed and am currently testing with the standard linux kernel, version 6.15.2-arch1-1)
  • GPU & Graphics Drivers:00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: Fujitsu Limited. Device 17aa Kernel driver in use: i915

The Problem

I cannot load the binder_linux and ashmem_linux modules required by Waydroid.

What I Have Tried

  1. I installed the standard linux and linux-headers packages to replace my xanmod kernel for this test.
  2. Running sudo modprobe binder_linux on the standard kernel failed with the error: FATAL: Module binder_linux not found.
  3. To fix this, I forced a complete reinstall with sudo pacman -Syu linux linux-headers. After rebooting into the standard kernel again, the problem remained.
  4. I then tried to build the modules via DKMS by installing the binder_linux-dkms package from the AUR.

Current State (after DKMS install and reboot)

This is where it gets very strange. The system is now in a contradictory state:

  • Running sudo modprobe binder_linux gives the error: ERROR: could not insert 'binder_linux': Device or resource busy.
  • However, running lsmod | grep binder_linux shows that the module is not loaded.
  • Running sudo modprobe ashmem_linux still results in: FATAL: Module ashmem_linux not found.

A reboot does not clear this “stuck” state for the binder_linux module. It seems the DKMS installation failed and has left the module system in a broken state.

I would be very grateful for any help on how to debug this system-level configuration issue. Thank you.

2

Bump - any ideas? I would be really happy to find a solution to that problem.

3

Try specifying ibt=off on your kernel command line.

4

i removed this since it made my system crash on file transfers it did not break my system but froze it and caused a memory leak for me i think this might be to do with kernel module