Kernel missing binder_linux and ashmem_linux modules

[stephenjamieson]

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="21.10"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 21.10"
VERSION_ID="21.10"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=impish
UBUNTU_CODENAME=impish
LOGO=distributor-logo-pop-os 

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

apt policy linux-generic
linux-generic:
  Installed: 5.15.11.76051511.202112220937~1640185481~21.10~b3a2c21
  Candidate: 5.15.11.76051511.202112220937~1640185481~21.10~b3a2c21
  Version table:
 *** 5.15.11.76051511.202112220937~1640185481~21.10~b3a2c21 1001
       1001 http://apt.pop-os.org/release impish/main amd64 Packages
        100 /var/lib/dpkg/status
     5.13.0.25.36 500
        500 http://us.archive.ubuntu.com/ubuntu impish-security/main amd64 Packages
        500 http://us.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages
     5.13.0.19.30 500
        500 http://us.archive.ubuntu.com/ubuntu impish/main amd64 Packages

Issue/Bug Description:

Pop OS Kernel does not have binder_linux nor ashmem_linux enabled

Steps to reproduce (if you know):

Expected behavior:

Modules should be compiled as they are in the default ubuntu kernel, otherwise software like anbox cannot be utilized on Pop OS

Other Notes:

[KameiKojirou]

I'd like to second this.

[Fuseteam]

this seems to be duplicate of #39

[User8395]

This is a problem that I have had for a long time. Is there a link where one can download a kernel with those modules?

[KameiKojirou]

Right now you have to use an different kernel like https://xanmod.org/ that has support for those modules and at that point you still have to install and setup the modules.

[User8395]

at that point you still have to install and setup the modules.

Is there a guide on how to do that?

[KameiKojirou]

Sort of... but not really, I used this guide to do it for Waydroid a few months back, which I was able to make some adjustments when I got stuck to make it work. Ultimately it didn't do much for me anyways since Wayland still isn't there yet, Waydroid itself worked fine though. Just a heads up and a word of caution, this can mess up your OS and I don't recommend doing this unless you have a good understanding of how it all works. Otherwise you might end up with a borked OS.

https://www.youtube.com/watch?v=SfK4PBcFq0w

[User8395]

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:11.0pt; font-family:"Calibri",sans-serif;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} -->Ok 

[JamiKettunen]

ASHMEM was dropped from mainline kernel in 5.18, but BINDERFS appears to be enabled even on the v6.2 kernel of the 22.04-based live ISO. I think all needed Waydroid options are now enabled by default?

[Fuseteam]

this can confirmed with grep -E '(MEMFD)' /boot/config-$(uname -r) for MEMFD (ASHMEM's successor) and grep -E '(BINDER)' /boot/config-$(uname -r) for BINDERFS

[9thyear2]

andrew@pop-os:~$ grep -E '(MEMFD)' /boot/config-$(uname -r)
CONFIG_MEMFD_CREATE=y
andrew@pop-os:~$ grep -E '(BINDER)' /boot/config-$(uname -r)
# CONFIG_ANDROID_BINDER_IPC is not set